icu: init at 60.2

Motivation for this change
New version.
Should it be the default icu ?

Probably remove 59 and switch to 60 as default, though it's hard to say immediately, as ABI isn't fully compatible.  Still, it's probably nowhere near the change between 58 and 59.

I guess it is safe to merge the PR as it is, and then try icu = icu60; against the staging

@GrahamcOfBorg build icu60

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev/sbin/escapesrc
gzipping man pages under /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev/share/man/
strip is /nix/store/adidfx4pa7vmvby0gjqqmiwg2x49yr27-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev/lib  /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev/bin  /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev/sbin
patching script interpreter paths in /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev
/nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev/bin/icu-config: interpreter directive changed from "/bin/sh" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/sh"
checking for references to /build in /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev...
moving /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev/sbin/* to /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev/bin
Moving /nix/store/lcziznx1z08n00wimzbixxvnaq31w5qs-icu4c-60.2/lib/icu to /nix/store/ccalaabmzaddi59anvwx6aigc6bbsaxm-icu4c-60.2-dev/lib/icu
rmdir: failed to remove '/nix/store/lcziznx1z08n00wimzbixxvnaq31w5qs-icu4c-60.2/lib': Directory not empty

Success on aarch64-linux (full log)
Partial log (click to expand)
gzipping man pages under /nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev/share/man/
strip is /nix/store/skd6ix5ipkyhxzq7naylj4digawakl4j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev/lib  /nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev/bin  /nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev/sbin
patching script interpreter paths in /nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev
/nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev/bin/icu-config: interpreter directive changed from "/bin/sh" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/sh"
checking for references to /build in /nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev...
moving /nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev/sbin/* to /nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev/bin
Moving /nix/store/5840h7qgg38rwad05d5g77lrxa9qsyk2-icu4c-60.2/lib/icu to /nix/store/r1jn0w1xqwr8v2w6rdjsw1rrbnj54f9d-icu4c-60.2-dev/lib/icu
rmdir: failed to remove '/nix/store/5840h7qgg38rwad05d5g77lrxa9qsyk2-icu4c-60.2/lib': Directory not empty
/nix/store/5840h7qgg38rwad05d5g77lrxa9qsyk2-icu4c-60.2

Success on x86_64-darwin (full log)
Partial log (click to expand)
/nix/store/d06fssvy5v61xf101avcpy61rz12f9sy-icu4c-60.2/lib/libicutest.60.2.dylib: fixing dylib
gzipping man pages under /nix/store/4xgg65kb6h66jdpbdhspn6ms4b5gxba0-icu4c-60.2-dev/share/man/
strip is /nix/store/v8ifq0hapblpr2z0hx4wvwg02w4aczqy-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/4xgg65kb6h66jdpbdhspn6ms4b5gxba0-icu4c-60.2-dev/lib  /nix/store/4xgg65kb6h66jdpbdhspn6ms4b5gxba0-icu4c-60.2-dev/bin  /nix/store/4xgg65kb6h66jdpbdhspn6ms4b5gxba0-icu4c-60.2-dev/sbin
patching script interpreter paths in /nix/store/4xgg65kb6h66jdpbdhspn6ms4b5gxba0-icu4c-60.2-dev
/nix/store/4xgg65kb6h66jdpbdhspn6ms4b5gxba0-icu4c-60.2-dev/bin/icu-config: interpreter directive changed from "/bin/sh" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/sh"
moving /nix/store/4xgg65kb6h66jdpbdhspn6ms4b5gxba0-icu4c-60.2-dev/sbin/* to /nix/store/4xgg65kb6h66jdpbdhspn6ms4b5gxba0-icu4c-60.2-dev/bin
Moving /nix/store/d06fssvy5v61xf101avcpy61rz12f9sy-icu4c-60.2/lib/icu to /nix/store/4xgg65kb6h66jdpbdhspn6ms4b5gxba0-icu4c-60.2-dev/lib/icu
rmdir: failed to remove '/nix/store/d06fssvy5v61xf101avcpy61rz12f9sy-icu4c-60.2/lib': Directory not empty
/nix/store/d06fssvy5v61xf101avcpy61rz12f9sy-icu4c-60.2

/cc maintainer @7c6f434c.

Hm, I am the maintainer of that, too? Oh my leaky memory, what I was packaging back in the day that also needed ICU.
On a more serious note, pure addition is definitely a good idea, and switching the default is a thing to try, but LibreOffice, Firefox, TeXLive, WebKit and Qt (and a lot of small stuff like Inkscape) all depend on it. I bet something will break.
On a note that is only tangentially related (via the fact that this PR is a pure addition of a thing we will obviously need soon) and more related to my glancing at the track record: @volth have you considered asking for commit access? I think even 150 PRs ago it was already a good idea…

:+1: for push access from me.

https://github.com/NixOS/nixpkgs/pull/35294#issuecomment-367471966
we guarantee binary INcompatibility across major releases for C++, forward compatibility for C stable APIs ( see http://userguide.icu-project.org/design#TOC-ICU-Binary-Compatibility:-Using-ICU-as-an-Operating-System-Level-Library )
also: ICU 61.1 is out.

binary compatibility isn't so important in nixpkgs, as most packages are source-built and those get rebuilt.

That would suggest to just update the default in nixpkgs and only switch the problematic cases to older version later (if any).


Ignore Columns

English Only
Please check existing issues first to avoid duplication and answer the questions below before submitting your issue.
Use case(s)
(Please state use cases, what problem will this feature solve?)
Sometimes users define a complicate structure but some of its fields should not be inserted into databases. It indicates one thing: some fields can not be mapped to columns.
In some small applications, users do not use entity or PO. They only have one layer named model, and they use models in their business code as well as DAO.
So we need to allow users to declare that they want EQL to ignore some field.
Proposed Solution
(Please describe your proposed design/solution, if any)
We already have a MetaRegistry named tagMetaRegistry, so we can use the syntax: eql:"-" to ignore the columns. Besides, we need to provide an option to ignore some fields when users register models.
Alternatives Considered
(Other possible options for solving the problem?)
Additional Context
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
(If you can, link to the line of code that might be helpful to explain the context)

In the option that ignore some fields, we can compare field name of user input and field name of 'TableMeta' to ignore some fields.
I think i can do it.

Add ignore column examples.


[BUG] Left clicking conduit connector with yeta wrench doesn't remove correct conduit

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When left clicking a conduit connector with a yeta wrench, that is connected to a chest/machine, doesn't remove the connector until the right conduit is getting removed. In this example I used the creative energy source as you can see here when which conduit gets removed best.

after first left click, the redstone conduit is removed:

after second, the fluid conduit is removed:

after third, the item conduit is removed:

and last, the energy conduit is removed:

Expected Behavior
just remove the right conduit, that is attached to that specific conduit connector
Steps To Reproduce

place an energy source
place all 4 conduits in one block
left click with yeta wrench
removes wrong conduit
do left clicks until you removed that conduit you wanted to remove

Environment
- OS: Windows 11
- Java version: Adoptium 17.0.3-hotspot
- Minecraft version: 1.20.1
- Version: 6.0.3

Anything else?
No response

This is the same issue as before, the hitbox of the connector is linked to the wrong conduit.

Should be resolved by #269


resnet 18

@mjason98, let's not delete branches here please.
@mohammadsanaee, I think we could get back to this once we have a better validation dataset and script - try out some other models and fix that bug we had in those notebooks (maybe you already fixed that and it's just me misremembering things).
I recently heard about DINO which looks like a quite promising model that may improve our search results https://huggingface.co/facebook/dinov2-base


[TabBarIOS] Customizing TabBar

Hi guys,
Thanks for the great work!
I've noticed that master includes new useful properties for TabBar.

barTintColor
tintColor

Is there a way to add the following:

Remove the top border
Control the label text size & position
Control Icon size

Can someone point me to the right direction?
Your help is appreciated
Ran.

You can modify all of those properties natively:

http://stackoverflow.com/questions/14371343/ios-uitabbar-remove-top-shadow-gradient-line
*https://developer.apple.com/library/ios/documentation/UIKit/Reference/UITabBarItem_Class/index.html#//apple_ref/occ/cl/UITabBarItem

However, since it sounds like you want a really custom TabBar, I'd probably recommend just building your with a Navigator under a custom View.

You can also use the open source extension of Tab bar such as react-native-icons if you don't want to extend it yourself.

@brentvatne open source solution now exists, and recommendations made. Closeable.

@ranyefet what did you do to solve this problem?  If I create a native component for this, does that mean I have to create an entire UITabBarController natively or can I somehow make a file with just that property?  Thanks!


Global DisableDiff

Is the feature request related to a problem
I would like to be able to globally disable the diff tool from launching, this is currently not possible.
Reason being that I would rather launch it manually, when needed.
When there are many failures it can be annoying to close all the windows.
Describe the solution
Add a DisableDiff method to VerifierSettings.
Describe alternatives considered
I considered using VerifierSettings.AutoVerify(), but I would prefer that accepting would remain a manual action.

https://github.com/VerifyTests/DiffEngine#disable-for-a-machineprocess

When there are many failures it can be annoying to close all the windows

DiffEngineTray makes that easier https://github.com/VerifyTests/DiffEngine/blob/main/docs/tray.md

Awesome stuff!
I'm using the Rider plugin and prefer to accept the changes from the test result tree (it's really nice that accepting works on higher levels of the tree as well).
I must say that I'm quite impressed with all the features of this library. I have worked with snapshot testing within other contexts in the past, but the is definitely the most full-featured and easy-to-use solution I have seen so far.
For me the only thing that was tricky was finding the correct global configuration options, because they live on different classes. For example:

Verifier.DerivePathInfo
DiffRunner.Disabled
VerifierSettings.AutoVerify

Oh, and DiffEngineTray plays nicely with the Rider/R# plugin


CSS Logical Properties - Safari TP 64 changed something

Maybe this pull request should have been an issue, as I'm not quite sure if y is truly correct. So this might be more a reminder to investigate. Feel free to close or change this.

https://webkit.org/blog/8406/release-notes-for-safari-technology-preview-64/

Implemented flow-relative margin, padding, border and sizing properties (r234798)

⇒ https://bugs.webkit.org/show_bug.cgi?id=188386
http://tests.caniuse.com/ seems to show the same result as Chrome Canary (Version 70.0.3535.5), but for some reason the column on the right is empty…

Also in the ticket they mention some caveats, but seem to have achieved parity with Chrome.
Thus not sure about partial or not and the note(s). But at least its unprefixed!
I've gone the optimistic route with the commit 0:-)

Confirmed, thanks!
FYI the reason the column on the right is empty is because the browser-detecting code isn't currently working for TP. You'll see it if you manually select it (or any other webkit browser) from the dropdown though.


Allow replace by empty string

Allow replace by empty string

I have exactly the same requirement.
Do you have an solution or workaround for this? Since your post is from 2018...

This is sort of related, but I would like to pad my replacement text with spaces, but these are seemingly stripped off !
this makes it impossible to replace lines in a .yaml file, as they need proper indentation.
I guess this could be an issue with VSTS tasks?


dracut: FATAL: No or empty root=

I got the following error following the rEFInd screen when I tried a recent ubuntu install.
dracut: FATAL: No or empty root=
I resolved by adding the following to the kernel parameters in refind_linux.conf, where zpool is the name of the pool. Zfsbootmenu then started normally.
root=zfs:zpool/ROOT
https://github.com/openzfs/zfs/blob/master/contrib/dracut/README.md
Does the rEFInd section of the ubuntu install guide need to be updated?

How did you install ZFSBootMenu - from source (via a tagged release, or master) or a prebuilt EFI?

I highly recommend that you use the git branch from which releases are tagged - in this case v2.2.x. master is a moving target that might or might not be fit for consumption.

Thank you Zdykstra. I installed from master as part of testing the Ubuntu zfsbootmenu install script.
What changed to cause the break? Something in upstream dracut?
Thank you for the info on the master vs branches. The Ubuntu zfsbootmenu install script currently installs from master. I’ll have to think through what I should link to in future if the master “might or might not be fit for consumption”. I don’t think I can link to a branch as that might eventually be deleted? Is there a link that will always download the latest branch code that I could use?

The v2.2.x branch will never be deleted.
If you want the latest, you can use https://get.zfsbootmenu.org/, which is just a thin wrapper over the GitHub release query interface.

As a side note, if you're going it query GitHub directly, you should use jq or some other mechanism that understands the structure of the JSON response. Unstructured text processing is bound to fail at some point.


feat(website): Add WAF to dev and stage

Access to the dev and staging site should be restricted.
This PR restricts access to these sites via an IP restriction implemented in WAF.
Logic is added to only add these restrictions to the dev and staging workspaces.

Yeah I'm happy with these changes - Approved


Add the ignoreAnnotated array parameter to the FunctionNaming rule

This is intended to ease the use of Jetpack Compose.
Addresses #2733

Updated the PR based on comments received.

java.lang.ClassCastException: class [Ljava.lang.String; cannot be cast to class java.util.List ([Ljava.lang.String; and java.util.List are in module java.base of loader 'bootstrap')

Have you executed the tests locally?
NamingConventionLengthSpec > should not report underscore variable names FAILED
47810
    kotlin.UninitializedPropertyAccessException: lateinit property annotationExcluder has not been initialized

NamingConventionLengthSpec

I was running them in the wrong location. 👎
I believe I have followed the directions more closely this time around. And I got a successful build after publishing locally.

We use the Kotlin Jsr223 mechanism to ensure valid Kotlin test code snippets. That’s the reason why the build was failing. Thanks again for contributing! Cool stuff..


[c2][memory] Fixed memory leak in InitSession

InitSession will called multiple times, which will cause MFXload to
also be called multiple time. Each call overwrites the previous pointer
that was not freed so it makes a memory leak.
Tracked-On: OAM-102284
Signed-off-by: zhangyichix<EMAIL_ADDRESS>

@dyang23 @TianmiChen @YuanjunHuang @Shao-Feng Could you pls help me to take a review?


Need to clean up queue at init

Don't know if it can cause any problem not doing it but will be good to do it

It's partially done in multiplayer-temp1 branch but still need to better handle game transition in multi. I'm closing this issue in favor of the reopened #27


clientEntry preload cannot handle duplicate slashes in pathname

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
We use Netlify for our builds and I've just been troubleshooting an issue whereby someone had linked to https://moodledev.io//general/releases - not the double forward slash.
When visiting this page the content briefly shows before disappearing.
Originally I thought that this was some kind of Netlify issue, and I looked into writing a rewrite rule to redirect users, but that doesn't seem to be easy/possible in Netlify. However, it occurs to me that this is possibly also a Docusaurus bug.
I've tracked this back to the use of window.location.pathname in https://github.com/facebook/docusaurus/blob/main/packages/docusaurus/src/client/clientEntry.tsx#L34
In this case, the pathname is //docs/releases, which is not an exact match for any of the routes and therefore the Promise is rejected and the 404 page served.
The is of course a valid URL, and I feel that perhaps this kind of issue should either:

just be served; or
the duplicate slashes in the URL rewritten since they are meaningless anyway.

Reproducible demo
No response
Steps to reproduce
Visit a prodcution page (not served by yarn serve) and watch it serve initially, and then turn into a 404, examples include:

https://docusaurus.io//docs/docusaurus-core
https://docusaurus.io/docs//docusaurus-core
https://moodledev.io//docs/releases

Expected behavior
EIther correct the URL, or just serve the content
Actual behavior
404
Your environment

Public source code: https://github.com/moodle/devdocs
Public site URL: https://moodledev.io
Docusaurus version used: latest
Environment name and version Chrome 104
Operating system and version MacOS

Self-service

[X] I'd be willing to fix this bug myself.

The server sends the correct HTML but the router does not recognize this location and hydrates it as a 404 page—that's pretty expected.
Why would you want it to work?

Duplicate slashes are not meaningless in the router—virtually all URLs can have different meanings to the router. You can even have different content for /foo and /foo.html, so any kind of rewrite can only be based on an informed guess. But I think this behavior (namely, duplicate slashes being tolerated) is not consistent between hosting providers?

It's not unexpected for people to make small mistakes like adding an extra / in a URL and we should try hard not to break in these situations.
I'd expect it to at least try and normalise the URL, especially since the correct HTML is indeed returned. If the HTML is returned then surely it should be possible to return the route for that page?

Perhaps it would be possible for the server-rendered HTML to redirect to the correct pathname if it does not match (just pathname, not the canonical).

We are using React-Router
Why not request this behavior for all React apps using React-Router instead of here?
Doesn't it make sense for Remix apps too for example (based on React-Router)?
I'd rather not implement something too fancy that fights against the behavior of our lib. If you can convince React-Router authors that this behavior is worth implementing, we'll benefit from it by simply upgrading.

For now I'll close this issue
Now if you really want this, we can reopen if you do the homework:

show us a file-system structure to adopt for serving static files under //docs/xyz
deploy it to Netlify/Vercel/GitHub Pages and prove that it works consistently
ask to add this to React-Router and if they don't want it, we can consider it for Docusaurus

FWIW, I always like changes that turn more errors into less errors.


Sample solutions for task 1.14 of the Superposition katas.

https://github.com/microsoft/QuantumKatas/blob/cd7b60ea618512b0012f16f631c6c780d623841a/Superposition/Workbook_Superposition_Part2.ipynb?short_path=8af21c1#L622
I am looking at the sample solutions for task 1.14 of the Superposition katas. How about another option:
operation AllStatesWithParitySuperposition (qs : Qubit[], parity : Int) : Unit {
    for i in 1 .. Length(qs) - 1 {
        H(qs[i]);
        CNOT(qs[i], qs[0]);
    }

    if (parity == 1) {
        X(qs[0]);
    }
}

It is simpler than what is suggested and passes the tests. Isn't it correct?

It looks correct, yes! Passing the tests is a good sign, and I think you can also demonstrate its correctness recursively, since the for loop adds one qubit at a time and keeps the parity of the states even.
Do you want to add it to the workbook as an alternative solution? It's harder for me to come up with solutions which use gates with a "later" qubit as control and an "earlier" one as target, so this solution can be interesting for learners who have the same "forward-CNOTs" bias :-)

Thank you @tcNickolas for looking into this. I've created a PR #802


ci: setup danger, add junit report tracking

Add danger to the repo which will run/do the following

tslint and report any comments on the changed files in line in the pr
report test status
dependency changes
link to the build vsix file

Also setup junit reporting that gets tracked in Jenkins.
Going to try see if we can setup coverage reporting too

Messages

:book:

:floppy_disk: Here's the built vsix for this change.

:book:

:white_check_mark: All tests are passing
Nice one! All 25 tests are passing.

New dependencies added: @awam/danger-plugin-tslint, @seadub/danger-plugin-dependencies, @seadub/danger-plugin-junit, danger, mocha-jenkins-reporter and mocha-multi-reporters.
@awam/danger-plugin-tslint
Author: Unknown
Description: Add tslint errors and warnings to your Danger output
Homepage: http://npmjs.com/package/@awam/danger-plugin-tslint

Created5 months agoLast Updated5 months agoLicenseMITMaintainers1Releases1Direct Dependencies@types/node and danger

README
danger-plugin-tslint
Add tslint errors and warnings to your Danger output
Usage
Install the package to your devDependencies
npm install @awam/danger-plugin-tslint --save-dev
# or
yarn add @awam/danger-plugin-tslint --dev

Add the package to your dangerfile
import tslint from '@awam/danger-plugin-tslint';
import { join } from 'path'
async function main() {
  await tslint().
  // supply a tslint file in a different location
  await tslint({ tslintConfigurationPath: join(process.cwd(), 'config', 'tslint.json' )}),
  // supply other file extensions to be linted
  await tslint({ fileExtensions: [ '.ts', '.tsx', '.js' ]}),
}

main()
  .then(() => process.exit(0))
  .catch(err => {
    fail(err.toString());
    process.exit(1);
});

This plugin will leave no output if no errors or warnings exist.
If tslint fails to parse the config file then the error message will be reported as a fail.

@seadub/danger-plugin-dependencies
Author: Chris Williams
Description: Provides dependency information on dependency changes in a PR
Homepage: https://github.com/sgtcoolguy/danger-plugin-dependencies#readme

Created9 months agoLast Updated9 months agoLicenseMITMaintainers1Releases2Direct Dependenciesdate-fns, lodash.flatten, lodash.includes, node-fetch and semverKeywordsdanger, danger-plugin, npm, yarn and dependencies

README
danger-plugin-dependencies

Provides dependency information on dependency changes in a PR

Usage
Install:
npm install @seadub/danger-plugin-dependencies --save-dev
# or
yarn add @seadub/danger-plugin-dependencies --dev

At a glance:
// dangerfile.js
import dependencies from '@seadub/danger-plugin-dependencies'

schedule(dependencies())

Provides 4 separate rules:

checkForRelease - Provides a 🎉 when there's a package version bump.
checkForNewDependencies (async) - Provides npmjs.com (and yarn why, when type is "yarn") metadata about new dependencies.
checkForLockfileDiff - Will warn you when there are dependencies or  devDependencies changes without a package-lock.json or yarn.lock change.
checkForTypesInDeps - Will fail the build if you add any @types/[x] to dependencies instead of devDependencies.

And exports a default function to handle all of them at once.
Note: async functions like the default one have be to schedule'd by Danger.
yarn vs npm usage
By default, the dependencies method will attempt to determine if you are using npm or yarn to manage your dependencies based on sniffing for the lockfiles on disk. If no lockfiles exist, or running on Peril it will fail without an explicitly stated manasger type in the options.
You may explicitly pass one in the options:
// dangerfile.js
import dependencies from '@seadub/danger-plugin-dependencies'

schedule(dependencies({ type: "npm" }))
// or for yarn
schedule(dependencies({ type: "yarn" }))

Private packages
If you want the plugin to find your private packages on npm, you need to provide an npm authentication token:
// dangerfile.js
import dependencies from 'danger-plugin-dependencies'

schedule(dependencies({ npmAuthToken: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' }))

Changelog
See the GitHub release history.
Contributing
See CONTRIBUTING.md.
What does this look like?
The rest of this README is the contents of what it looks like when you add this plugin to your Dangerfile:

Warnings

:warning:

New dependencies added: danger-plugin-yarn.

danger-plugin-yarn
Author: Orta Therox
Description: Provides dependency information on dependency changes in a PR
Homepage: https://github.com/orta/danger-plugin-yarn#readme

Created24 days agoLast Updated3 minutes agoLicenseMITMaintainers1Releases14Direct Dependenciesdate-fns, lodash.flatten, lodash.includes, node-fetch and esdocKeywordsdanger, danger-plugin and yarn

README
# danger-plugin-yarn

Provides dependency information on dependency changes in a PR

Usage
Install:
yarn add danger-plugin-yarn --dev

At a glance:
// dangerfile.js
import yarn from 'danger-plugin-yarn'

schedule(yarn())

Provides 4 separate rules:

checkForRelease - Provides a 🎉 when there's a package version bump.
checkForNewDependencies (async) - Provides npmjs.com and yarn why metadata about new dependencies.
checkForLockfileDiff - Will warn you when there are dependencies or  devDependencies changes without a yarn.lock change.
checkForTypesInDeps - Will fail the build if you add any @types/[x] to dependencies instead of devDependencies.

And exports a default function to handle all of them at once.
Note: async functions like the default one have be to schedule'd by Danger.
Changelog
See the GitHub release history.
Contributing
See CONTRIBUTING.md.

yarn why danger-plugin-yarn output
Has been hoisted to "danger-plugin-yarn"This module exists because it's specified in "devDependencies".Disk size without dependencies: "80kB"Disk size with unique dependencies: "3.98MB"Disk size with transitive dependencies: "4.43MB"Number of shared dependencies: 7

  Generated by :no_entry_sign: dangerJS

@seadub/danger-plugin-junit
Author: Christopher Williams
Description: Add your Junit XML test failures to Danger
Homepage: https://github.com/sgtcoolguy/danger-plugin-junit#readme

Created10 months agoLast Updated7 days agoLicenseMITMaintainers1Releases5Direct Dependenciesfs-extra, glob and xmldomKeywordsdanger, danger-plugin and junit

README
danger-plugin-junit

Add your Junit XML test failures to Danger

Usage
Install:
npm install danger-plugin-junit --save-dev
# or
yarn add danger-plugin-junit --dev

At a glance:
// dangerfile.js
import junit from 'danger-plugin-junit'

async function main() {
	await junit({ pathToReport: './build/reports/**/TESTS*.xml' })
}

main()
	.then(() => process.exit(0))
	.catch(err => {
		fail(err.toString());
		process.exit(1);
	});

The default pathToReport value is './build/reports/**/TESTS*.xml'
The value is a glob string to gather up test result files.
This plugin will only report test failures and errors. If any tests fail, it will report a single fail() message and record a table of the failed tests using markdown().
An example of what is produced is below:

Changelog
See the GitHub release history.
Contributing
See CONTRIBUTING.md.

danger
Author: Orta Therox
Description: Unit tests for Team Culture
Homepage: https://github.com/danger/danger-js#readme

Createdover 3 years agoLast Updatedabout 13 hours agoLicenseMITMaintainers3Releases256Direct Dependencies@babel/polyfill, @octokit/rest, async-retry, chalk, commander, debug, get-stdin, gitlab, http-proxy-agent, https-proxy-agent, hyperlinker, json5, jsonpointer, jsonwebtoken, lodash.find, lodash.includes, lodash.isobject, lodash.keys, lodash.mapvalues, lodash.memoize, memfs-or-file-map-to-github-branch, micromatch, node-cleanup, node-fetch, override-require, p-limit, parse-diff, parse-git-config, parse-github-url, parse-link-header, pinpoint, prettyjson, readline-sync, require-from-string, rfc6902 and supports-hyperlinksKeywordsdanger and ci

README

  Formalize your Pull Request etiquette.

What is Danger JS? •
    Vision •
    Helping Out •
    Plugin Development

What is Danger JS?
Danger runs after your CI, automating your team's conventions surrounding code review.
This provides another logical step in your process, through which Danger can help lint your rote tasks in daily code
review.
You can use Danger to codify your teams norms, leaving humans to think about harder problems.
Danger JS works with GitHub, BitBucket Server, BitBucket Cloud for code review, then with: Travis CI, GitLab CI,
Semaphore, Circle CI, GitHub Actions, Jenkins, Docker Cloud, Bitrise, surf-build, Codeship, Drone, Buildkite, Nevercode,
buddybuild, Buddy.works, TeamCity, Visual Studio Team Services, Screwdriver, Concourse, Netlify, CodeBuild, Codefresh,
AppCenter, or BitBucket Pipelines.

For example?
You can:

Enforce CHANGELOGs
Enforce links to Trello/JIRA in PR/MR bodies
Enforce using descriptive labels
Look out for common anti-patterns
Highlight interesting build artifacts
Give warnings when specific files change

Danger provides the glue to let you build out the rules specific to your team's culture, offering useful metadata and
a comprehensive plugin system to share common issues.
Getting Started
Alright. So, actually, you may be in the wrong place. From here on in, this README is going to be for people who are
interested in working on and improving on Danger JS.
We keep all of the end-user documentation at http://danger.systems/js.
Some quick links to get you started:

Getting Started
Guides Index
DSL Reference

This thing is broken, I should help improve it!
Awesommmmee. Everything you need is down below. You can also refer to CONTRIBUTING file where you'll
find the same information listed below.
git clone https://github.com/danger/danger-js.git
cd danger-js

# if you don't have yarn installed
npm install -g yarn

yarn install

You can then verify your install by running the tests, and the linters:
yarn test
yarn lint

The fixers for both tslint and prettier will be applied when you commit, and on a push your code will be verified that
it compiles.
You can run your dev copy of danger against a PR by running:
yarn build; node --inspect distribution/commands/danger-pr.js https://github.com/danger/danger-js/pull/817

How does Danger JS work?
Check the architecture doc.
What is the TODO?
Check the issues, I try and keep my short term perspective there. Long term is in the VISION.md.
Releasing a new version of Danger
Following this commit as a model:

Checkout the master branch. Ensure your working tree is clean, and make sure you have the latest changes by running
git pull.
Publish - npm run release -- [major/patch/minor] --non-interactive.

:ship:
License, Contributor's Guidelines and Code of Conduct
We try to keep as much discussion as possible in GitHub issues, but also have a pretty inactive Slack --- if you'd like
an invite, ping @Orta a DM on Twitter with your email. It's mostly interesting if you want
to stay on top of Danger without all the emails from GitHub.

This project is open source under the MIT license, which means you have full access to the source code and can modify
it to fit your own needs.
This project subscribes to the Moya Contributors Guidelines which TLDR: means
we give out push access easily and often.
Contributors subscribe to the Contributor Code of Conduct based on
the Contributor Covenant version 1.3.0.

mocha-jenkins-reporter
Author: Juho Vähä-Herttua
Description: jenkins reporter for mocha
Homepage: https://github.com/juhovh/mocha-jenkins-reporter#readme

Createdover 5 years agoLast Updatedabout 2 months agoLicenseMITMaintainers1Releases35Direct Dependenciesdiff, mkdirp, mocha and xmlKeywordsmocha, jenkins and reporter

README
Mocha Jenkins Reporter
This reporter is useful if you want to run Node.js backend tests using mocha and need a nicely formatted Jenkins reports of the test runs. The existing xunit reporter is very similar, but doesn't make it possible to output both XML report and a console output at the same time, which would often be useful with Jenkins.
The xunit reporter also doesn't handle separate tests suites but adds all tests to a single suite instead, this reporter instead combines nested test suites to a single suite and uses that in the reports. As a nice plus, this reporter also shows the running time of each suite separately. All the code is released under the MIT license which can be found from the end of this file.
General Information
First you need to add the library to your package.json, you can use the following setting to get the latest version:
"mocha-jenkins-reporter": "0.4.2"
For the actual test run you can add the following to package.json:
"scripts": {
  "test-jenkins": "JUNIT_REPORT_PATH=/report.xml mocha --colors --reporter mocha-jenkins-reporter"
}

The environment variable JUNIT_REPORT_PATH is used for passing the output filename or directory for the reporter. If an explicit filename is used, any existing reports in the same path will be overwritten, so be careful with it. If an existing directory is used instead, then the output will be in the format "path/to/directory/timestamp.xml" where timestamp is milliseconds since January 1, 1970. If the environment variable is not set, no JUnit style XML report is written and the test results are only printed to the console.
The environment variable JUNIT_REPORT_NAME is used for giving an optional name for testsuites, defaults to "Mocha Tests".
The environment variable JUNIT_REPORT_STACK is used to enable writing the stack trace for failed tests.
The environment variable JUNIT_REPORT_PACKAGES is used to enable package name to be represented by relative path to test.
Example console output of the reporter:
  In test suite number one
      ․ the asynchronous test should work: 47ms

  Suite duration: 0.048 s, Tests: 1

Programmatic Configuration
All of the above config values can be set with options passed in to mocha.
mocha({
            "reporter": "mocha-jenkins-reporter",
            "reporterOptions": {
                "junit_report_name": "Tests",
                "junit_report_path": "report.xml",
                "junit_report_stack": 1
            }
        }

Jenkins Setup
If you use the package.json approach specified in the last section, setting up Jenkins should be pretty straighforward. For the shell execution you can use something like this:
cd $WORKSPACE
npm install
npm run test-jenkins

Make sure to set the Color ANSI Console Output on and use for example xterm for the ANSI color map setting, in order to show the output colors nicely in Jenkins.
After this you should be able to add Publish JUnit test result report in your Post-build Actions and write for example report.xml to the Test report XMLs field if your package.json was exactly as above. You can use your own variations of these commands as you wish, but this should get anyone started.
After all this setting up, just click Save and start building, you should get all errors nicely both to the console log as the tests are being run and finally to the Jenkins reports.
Enabling Jenkins Screenshots
Jenkins screenshot attachments can be written to the report to allow for a screenshot attachment in each test failure. Simply specify a reporterOption of spec or loop. This writes a system-out xml element to the JUnit report, leveraging the Publish test attachments feature of the JUnit Attachments Plugin.
spec will write the full path of the screenshot with a filename consisting of "suitename+classname+test.title+extension". loop pulls and sorts all screenshots with specific filename text from JUNIT_REPORT_PATH and writes them in order according to the names of the files pulled. The imagestring reporterOption can be used to specify what files to pull, allowing for custom screenshot naming conventions on the mocha side, otherwise it defaults to the test suite name.
Screenshot extension defaults to ".png", but can also be passed in with the imagetype reporterOption.
SonarQube Integration
SonarQube is a popular tool for continuous inspection of code quality. You can find documentation for JavaScript language on JavaScript Plugin page.
One aspect of SonarQube analysis is outcome of unit tests. To properly display test results environment variable JENKINS_REPORTER_ENABLE_SONAR must be set to true. By default reporter looks for tests in ./test directory. It can be changed using environment variable JENKINS_REPORTER_TEST_DIR and providing relative path to the directory with tests.
License
Copyright (c) 2015-2016 Juho Vähä-Herttua and contributors
Copyright (c) 2013-2014 Futurice Ltd and contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

mocha-multi-reporters
Author: Stanley Ng
Description: Generate multiple mocha reports in a single mocha execution.
Homepage: https://github.com/stanleyhlng/mocha-multi-reporters#readme

Createdover 3 years agoLast Updatedalmost 2 years agoLicenseMITMaintainers1Releases13Direct Dependenciesdebug and lodashKeywordsmocha and reporter

README
mocha-multi-reporters
Generate multiple mocha reports in a single mocha execution.

Install
npm install mocha-multi-reporters --save-dev

Demo
https://github.com/stanleyhlng/mocha-multi-reporters-demo
Usage
Basic
$ ./node_modules/.bin/mocha --reporter mocha-multi-reporters
  mocha-test #1
    ✓ sample test #1.1
    ✓ sample test #1.2

  mocha-test #2
    ✓ sample test #2.1
    - sample test #2.2

  3 passing (6ms)
  1 pending

<testsuite name="Mocha Tests" tests="4" failures="0" errors="0" skipped="1" timestamp="Sun, 03 Jan 2016 08:15:14 GMT" time="0.005">
<testcase classname="mocha-test #1" name="sample test #1.1" time="0"/>
<testcase classname="mocha-test #1" name="sample test #1.2" time="0"/>
<testcase classname="mocha-test #2" name="sample test #2.1" time="0"/>
<testcase classname="mocha-test #2" name="sample test #2.2" time="0"><skipped/></testcase>
</testsuite>

Advanced

Generate spec and json reports.

// File: config.json
{
    "reporterEnabled": "spec, json"
}

$ ./node_modules/.bin/mocha --reporter mocha-multi-reporters --reporter-options configFile=config.json
  mocha-test #1
    ✓ sample test #1.1
    ✓ sample test #1.2

  mocha-test #2
    ✓ sample test #2.1
    - sample test #2.2

  3 passing (6ms)
  1 pending

{
  "stats": {
    "suites": 2,
    "tests": 4,
    "passes": 3,
    "pending": 1,
    "failures": 0,
    "start": "2015-12-30T22:49:39.713Z",
    "end": "2015-12-30T22:49:39.717Z",
    "duration": 4
  },
  "tests": [
    {
      "title": "sample test #1.1",
      "fullTitle": "mocha-test #1 sample test #1.1",
      "duration": 1,
      "err": {}
    },
    {
      "title": "sample test #1.2",
      "fullTitle": "mocha-test #1 sample test #1.2",
      "duration": 0,
      "err": {}
    },
    {
      "title": "sample test #2.1",
      "fullTitle": "mocha-test #2 sample test #2.1",
      "duration": 0,
      "err": {}
    },
    {
      "title": "sample test #2.2",
      "fullTitle": "mocha-test #2 sample test #2.2",
      "err": {}
    }
  ],
  "pending": [
    {
      "title": "sample test #2.2",
      "fullTitle": "mocha-test #2 sample test #2.2",
      "err": {}
    }
  ],
  "failures": [],
  "passes": [
    {
      "title": "sample test #1.1",
      "fullTitle": "mocha-test #1 sample test #1.1",
      "duration": 1,
      "err": {}
    },
    {
      "title": "sample test #1.2",
      "fullTitle": "mocha-test #1 sample test #1.2",
      "duration": 0,
      "err": {}
    },
    {
      "title": "sample test #2.1",
      "fullTitle": "mocha-test #2 sample test #2.1",
      "duration": 0,
      "err": {}
    }
  ]
}%

Generate tap and xunit reports.

// File: config.json
{
    "reporterEnabled": "tap, xunit",
    "xunitReporterOptions": {
        "output": "xunit-custom.xml"
    }
}

$ ./node_modules/.bin/mocha --reporter mocha-multi-reporters --reporter-options configFile=config.json

1..4
ok 1 mocha-test 1 sample test 1.1
ok 2 mocha-test 1 sample test 1.2
ok 3 mocha-test 2 sample test 2.1
ok 4 mocha-test 2 sample test 2.2 # SKIP -
# tests 3
# pass 3
# fail 0

$ cat xunit-custom.xml
<testsuite name="Mocha Tests" tests="4" failures="0" errors="0" skipped="1" timestamp="Sun, 03 Jan 2016 08:02:24 GMT" time="0.006">
<testcase classname="mocha-test #1" name="sample test #1.1" time="0.001"/>
<testcase classname="mocha-test #1" name="sample test #1.2" time="0.001"/>
<testcase classname="mocha-test #2" name="sample test #2.1" time="0"/>
<testcase classname="mocha-test #2" name="sample test #2.2" time="0"><skipped/></testcase>
</testsuite>

Generate tap and junit reports.

To generate junit report, we are using mocha-junit-reporter.
$ npm install mocha-junit-reporter

// File: config.json
{
    "reporterEnabled": "mocha-junit-reporter",
    "mochaJunitReporterReporterOptions": {
	    "mochaFile": "junit-custom.xml"
    }
}

$ ./node_modules/.bin/mocha --reporter mocha-multi-reporters --reporter-options configFile=config.json

1..4
ok 1 mocha-test 1 sample test 1.1
ok 2 mocha-test 1 sample test 1.2
ok 3 mocha-test 2 sample test 2.1
ok 4 mocha-test 2 sample test 2.2 # SKIP -
# tests 3
# pass 3
# fail 0

$ cat xunit-custom.xml
<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="Mocha Tests" time="0.001" tests="4" failures="0" skipped="1">
  <testsuite name="Root Suite" timestamp="2016-10-30T02:27:54" tests="0" failures="0" time="0">
  </testsuite>
  <testsuite name="mocha-test #1" timestamp="2016-10-30T02:27:54" tests="2" failures="0" time="0.001">
    <testcase name="mocha-test #1 sample test #1.1" time="0.001" classname="sample test #1.1">
    </testcase>
    <testcase name="mocha-test #1 sample test #1.2" time="0" classname="sample test #1.2">
    </testcase>
  </testsuite>
  <testsuite name="mocha-test #2" timestamp="2016-10-30T02:27:54" tests="2" failures="0" time="0">
    <testcase name="mocha-test #2 sample test #2.1" time="0" classname="sample test #2.1">
    </testcase>
  </testsuite>
</testsuites>

When calling Mocha programmatically

Note that when Mocha is called programmatically, it is passed an options object when created.  This object is usually derived from a config file that your mocha test runner reads prior to instantiation.  This is the object that must contain a key reporter with a value of mocha-multi-reporters for this plugin to be used.  You can also pass the key reporterOptions with a value of any of the above listed config files (including the reporterEnabled subkey and any other plugin configuration information.)  This removes the requirement to have an intermediate configuration file specifically for the multireporter configuration.
var mocha = new Mocha({
      reporter: "mocha-multi-reporters",
      timeout: config.testTimeout || 60000,
      slow: config.slow || 10000,
      reporterOptions: {
          "reporterEnabled": "mocha-junit-reporter, tap",
          "mochaJunitReporterReporterOptions": {
              "mochaFile": "junit-custom.xml"
          }
      }
    });
    mocha.addFile(...)
    mocha.run(...)

Note that it will first check if reporterOptions contains a configFile key, and if it does, use that.  That key must not exist in the reporterOptions object in order to pass these values in directly.
License
The MIT License (MIT)
Copyright(c) 2017 Stanley Ng
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

  Generated by :no_entry_sign: dangerJS against 46126437f01f497f5894090fee58a2c7ddab2bd9


Homepage of "." fails in latest version

Using a homepage of "." in the package.json file results in the error:

'render' from react-snapshot was never called. Did you replace the call to ReactDOM.render()?

in react-snapshot 1.1.0, but not 1.0.4.
Perhaps a pkg.homepage value of "." should default to a basename of "/" in cli.js?

I was seeing an issue as well, even without a . value - mine was pointing to a github sites page. Removing the homepage field fixed the issue for me

But what about if I need a homepage value in order to serve assets in the right place?

I had a similar problem with a fully qualified address.
To hotfix it, i had to backport kantenkugel@6a11bee404ab2cbf9c22c14b100f11cbf9bde0ae into my "node_modules\react-snapshot\lib\Server.js"
I also found out an anchor ("#toto") to raise the same error, just prepend "/" to it -> "/#toto"
hope it can help before the next release :)

I am trying to publish to gh-pages, following the guideline here. I am incurring in the same error. My homepage in package.json has the correct value.


filecoin: add CAR generation util

TODO write a description, it's Sunday and i'm lazy

MVP CAR generation tool is nearly done. Triton reported issues generating CARs for epochs larger than 32GB.


Add Automatic-Module-Name to MANIFEST

This adds Automatic-Module-Name to the MANIFEST, using Gradle; for example:
jar {
    manifest {
        attributes(
            "Automatic-Module-Name": "testcontainers.postgresql"
        )
    }
}

Fixes #1523

Hey @heruan, thanks a lot for taking action :slightly_smiling_face:
Stupid question, could we just add
    jar {
        manifest {
            attributes(
                "Automatic-Module-Name": "${project.group}.$project.name"
            )
        }
    }

to the subprojects closure in the root build.gradle file to make this dynamic?

@kiview Yeah, of course, I don't know Gradle much so I wasn't aware that was possible! With ${project.group}.${project.name} we'll get e.g.

org.testcontainers.postgresql instead of testcontainer.postgresql

It's just a choice of naming, some libraries like Spring name modules like spring.core others like Hibernates as org.hibernate.orm.

Great, looks good for me.
Let's see what @rnorth and @bsideup say about this.
Sorry if we don't directly merge this, but since we don't have a lot of experience with JMS, we want to think about breaking changes in the future if we decide on another naming scheme (maybe it's not a real problem, but we have to talk about this).
Thanks for getting the ball rolling :slightly_smiling_face:

Thank you @kiview for the review! Don't worry about the timing, first I understand you have to discuss this; second, this only change doesn't really let to use JMS since there are split packages all around the modules.
As discussed in #1524, to make JMS work I've moved classes in the JDBC and PostgreSQL modules in specific subpackages and finally I got JMS to work; see https://github.com/testcontainers/testcontainers-java/compare/master...heruan:jpms-non-interference
Of course, this is a breaking change but I guess it could be a single PR with this one. If you all agree, I can move all the other module classes to their own subpackages and add the commit to this PR!

Thank you @bsideup for the feedback and as you can read in my previous comment I totally agree: to make sense this should also fix the split packages issue and then it's a breaking change. If you're okay with this I can push the fix for the split packages here so we can further discuss how to shape JMS support.
The fact is that in the current status Testcontainers can't be used in a JMS project, so do you think it could be an option to start a 2.x branch starting with this?

@heruan I just added #1523 to the 2.0 milestone, so that we won't let it be released without a proper JPMS support.
I'm closing this PR but only because we need to perform a bigger change later and since it won't fix the problem. But we're thankful for the time you spent working on it, and hope we can get your help once we will be working on the problem as part of the 2.0 preparations 👍


Task/Updated tests to pass when there are no transactions

Updated tests to pass when there are no transactions.
Added logs and screenshots when this happens but unfortunately doesn't look like there is a way to get visibility on this from Slack integration
Closes #144

Run end-to-end tests - PR Expected — Waiting for status to be reported will never have status reported. Merging.


install YOURLS 1.7 / i have problem

Hi
i'm Try to install YOURLS 1.7
and i have problem :

[ Error creating table 'danaah_url'.
Error creating table 'danaah_options'.
Error creating table 'danaah_log'.
Error creating YOURLS tables.
File .htaccess successfully created/updated. ]
this is my config file :
[
 'max',
	't3ch' => 'max'	// You can have one or more 'login'=>'password' lines
	);

/** Debug mode to output some internal information
 ** Default is false for live site. Enable when coding or before submitting a new issue */
define( 'YOURLS_DEBUG', false );

/*
 ** URL Shortening settings
 */

/** URL shortening method: 36 or 62 */
define( 'YOURLS_URL_CONVERT', 36 );
/*
 * 36: generates all lowercase keywords (ie: 13jkm)
 * 62: generates mixed case keywords (ie: 13jKm or 13JKm)
 * Stick to one setting. It's best not to change after you've started creating links.
 */

/**
* Reserved keywords (so that generated URLs won't match them)
* Define here negative, unwanted or potentially misleading keywords.
*/
$yourls_reserved_URL = array(
	'porn', 'faggot', 'sex', 'nigger', 'fuck', 'cunt', 'dick', 'gay',
);

/*
 ** Personal settings would go after here.
 */

]

help me
thanks

Maybe a problem with MySQL user's rights. Please try using latest master and search closed issues before.
Also, please try to format your issue next time.


Build src for previous commit

Sorry took me some time to find time to build those files !
So those are the compiled files from my previous PR.

great, I will publish soon to npm and bower


Some format strings use decimal for HRESULT

Some  fail display format strings use 0x{}:
https://github.com/ZerothLaw/oaidl-safe/blob/97e9c15605b5c2e9c0bad2b48bb6d9241bc4b7f7/src/errors.rs#L51
while others use the (I believe correct) 0x{:x} to print in hexadecimal:
https://github.com/ZerothLaw/oaidl-safe/blob/97e9c15605b5c2e9c0bad2b48bb6d9241bc4b7f7/src/errors.rs#L16
Another option is to use {:#x}, which includes the 0x.

Ah, I actually resolved this issue with #5! Yay!


Add impersonated account while auto impersonating

Motivation
(Basically https://github.com/foundry-rs/foundry/issues/5732 all over again but with --auto-impersonate)
When getting a signer from an RPC endpoint ethers.js expects any accounts owned by the node (impersonated or otherwise) to be returned when calling eth_accounts. https://github.com/foundry-rs/foundry/pull/5734 fixed that issue for the regular case. However, doing the same thing with anvil --auto-impersonate has the same issue.
Solution
When calling anvil_impersonate the code checks under the hood whether the provided account is already being impersonated. If it is then no state gets modified (i.e. not added to CheatsState::impersonated_accounts) which means it can't be returned by eth_accounts.
To fix that instead of calling is_impersonated() (which returns true when --auto-impersonate is active) we check whether the address is already in the list of impersonated accounts.
To test that behavior I extended the can_auto_impersonate_account test to assert that the impersonated account gets returned by the eth_account handler.

failing test


API and tooling cleanups

Description
This PR includes a few small changes I wanted to get in before release v0.3.3.
Checklist

[x] Trim docs environment
[x] Trim examples environment
[x] Remove stale, private, and untested modules
[x] Make type checkers happy
[ ] Add tests
[ ] Lint
[ ] Update docstrings

I'm not sure how much this affects the examples environment, but it removes about 2 minutes from the docs build times.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

@teshanprasanga please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement


Corresponding HTML end tags can be highlighted as available in Notepad++

Corresponding HTML end tags can be highlighted as available in Notepad++
This feature will be more useful.
Right now I am pasting the html code to notepad++ and finding which of my tags are not closed

@VivekmanikandanD Can you add a screenshot that illustrates what you want?

Note that we already highlight the corresponding end tag in HTML (but not in PHP, that's #2915)


Memory Leak

There is a memory leak when opening the 'Edit Charts' view and rendering the thumbnails.
StreamAsIStream holds the byte[] so the GC cant collect it.
https://stackoverflow.com/questions/44761465/large-amounts-of-byte-kept-in-memory-by-streamasistream-instances

Think I got it.
But I'm not 100% sure...


Add tracking managers with Geant4 11.0

... both for native Geant4 processes and HepEm. Enable them via additional physics list in the TestEm3 application.

Looks good. Go ahead please.

Current performance of TestEm3 for 100k electrons à 10 GeV on 24 threads with this PR and Geant4 11.0 built as static libraries without verbose code:

processes
tracking manager

native Geant4 processes
501s
431s

G4HepEm
466s
375s


Add support for Compress Build Log plugin

https://wiki.jenkins-ci.org/display/JENKINS/Compress+Build+Log+Plugin

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


Fix for stage-2

Just a minor change + renaming one test (stage-2 miscounts number of tests if you have two tests with identical name)

Great, thank you.


Cache the http.Client in the Client object inside of CloudEvent Client

Would it make sense to cache the http.Client in the Client object? Might allow for easier testing if you wanted to replace it.
Originally posted by @evankanderson in https://github.com/knative/pkg/diffs

I think this is now obsolete (didn't the sdk move)?  If not reopen.


fix(combobox): disable openClose button (backport)

Backport of #5148
Signed-off-by: Bogdan Bogdanov<EMAIL_ADDRESS>

#4868


Add type annotation support and mapping info in jd gen

Closes #3 and closes #5
Now requires Java 11 as I wrote the taglet for java 9's taglet api
Generated source code from 20w51a:
20w51atest.zip
Selected generated javadoc from code above (excluded some dir as otherwise the archive would be too large):
test51adoc.zip
Example pic:

Looking at FabricMC/Enigma#321, we might just do the same but go straight to Java 15. However, since the Main is called directly by the buildscript, I think gradle itself should run on newer java unless we change that task to a standalone JavaExec.

I will merge this one for now. Since yarn depends on hardcoded 0.1.0+build.2, if the build fails, it should not hurt yarn. This build should pass; I can then test on yarn.

Hmm, seems Jenkins is not building at https://jenkins.modmuss50.me/job/FabricMC/job/MappingPoet/job/master/
might need some help.

Jenkins is no longer used. I’ll move it over to GitHub actions and make a release. 👍

Done, you can find it here: https://maven.fabricmc.net/net/fabricmc/mappingpoet/0.2.0/

Mixin form should probably be more appropriately named Mixin selector

Mixin form should probably be more appropriately named Mixin selector

Feel free to patch it here https://github.com/FabricMC/MappingPoet/blob/9abf2a8efe35fcad9f54469a1916ff6b96509ecb/src/main/java/net/fabricmc/mappingpoet/jd/MappingTaglet.java#L73 and submit a pr :laughing:


Configurable nginx access logs

What would be the best way to configure application access logs at nginx level? We want to log both the access when passing through the managed nginx and at the application to trace the performance and for debugging purposes.
For now we could edit the nginx configmap to add logging config, for example
log-format-upstream: '{"time": "$time_iso8601", "remote_addr": "$proxy_protocol_addr",
    "x_forwarded_for": "$proxy_add_x_forwarded_for", "request_id": "$req_id", "remote_user":
    "$remote_user", "bytes_sent": $bytes_sent, "request_time": $request_time, "status":
    $status, "vhost": "$host", "request_proto": "$server_protocol", "path": "$uri",
    "request_query": "$args", "request_length": $request_length, "duration": $request_time,"method":
    "$request_method", "http_referrer": "$http_referer", "http_user_agent": "$http_user_agent"
    }'

but it is not supported and will be reconciled/reset following https://github.com/Azure/aks-app-routing-operator/pull/139

To clarify, the default value of log-format-upstream doesn't work for our use case, as we want to collect the host name and use json format.

We will add this to the backlog.


add dolly dataset script

Do you think it would be possible to merge the dolly finetune script with the regular one? I don't see any drastic differences between the two. In https://github.com/Lightning-AI/lit-llama/pull/144 I made the weights path and data path configurable, maybe that's already enough?

Thank you @aniketmaurya! I agree with @awaelchli
Rather than introducing a new script, you could actually add a howto that describes the process end to end.
In the future we will start rely on howto's to describe a complete journey with code that can be cut and pasted.
Of course the current finetuning howto's potentially already cover 90% of it, but it would be great to have a howto dedicated to Dolly. Same goes for future toolformer etc tasks.

thanks @awaelchli @lantiga for the feedback, I will merge the finetuning script. I can add how-to doc in a follow up PR.

The finetuning script should be exactly the same right?

Merging as soon as tests pass

Merged, great job @aniketmaurya !


ReferenceError: process is not defined (Part II)

I'm still getting the process is not defined error using 1.2.5.
Implementing akin to how MarcoRS had proposed fixes for me
          still errors when it tries to access process. This worked for me :

  let debugMode = false;
  try {
    if (process) {
      debugMode = !!process?.env?.REACT_APP_DEBUG_MODE;
    }
  } catch (err) {
    //Your error handling
  }

Originally posted by @MarcosRS in https://github.com/the-bugging/react-use-downloader/issues/17#issuecomment-1936659505

Pull request: https://github.com/the-bugging/react-use-downloader/pull/21#issue-2228728038

Thank you man for looking into it and opening the PR! Really appreciate it. @all-contributors please add @9swampy for bug

Version 1.2.6 is live


feat: restore the user data in the response

I propose restoring the user data in the response of api.signUpEmail to complete the registration flow in my Nest.js application. Without this change, I am restricted to using versions of better-auth prior to v1.0.23.
The issue I am facing is described in #1036. Importantly, this modification does not break any existing functionality. Notably, the api.signInEmail endpoint already includes the user data in its response (which seems to be an oversight).
I kindly request that this PR be merged as a temporary measure.

Hey, thanks for the PR! We can go with this, but could you please add the user data to other endpoints and plugins that generate a new session and only return the token as well?

Sure, happy to help!
By the way, I’d like to discuss something. Based on my understanding of REST API conventions, a POST /sources endpoint typically returns the created resource. Following this logic, signUp creates a user resource, so it makes sense to return the user. Similarly, signIn creates a session resource, so returning the session would be reasonable as well.
Do you agree with this reasoning? If so, I can include the basic session data in the response as part of this PR. If not, I’ll limit this PR to restoring the user data only.
Looking forward to your feedback!

This approach is also reflected in Supabase’s API design. For example, the auth.signInWithPassword API returns both the session and user data: Supabase Auth API Reference.

We used to return the entire object. But, we want to avoid this because users can easily extend the tables and might introduce sensitive data that shouldn't be exposed to the user. Returning only the base session fields we provide may not be a bad idea. But for now let's keep it with the user data.

Hi, @Bekacru
I’ve added the user data to all endpoints and plugins that generate a new session and previously only returned the token, as requested.
Please let me know if there’s anything else to adjust. If everything looks good, I’d appreciate it if you could merge this PR.
Thank you!

In addition to the requested changes, I noticed that in the one-tap plugin, the following section of code:
https://github.com/better-auth/better-auth/blob/cc94e6a7c07c5742938a15e6e340d3dde3de17b3/packages/better-auth/src/plugins/one-tap/index.ts#L110-L113
currently returns the complete session in the main branch. I believe this might be an oversight. I have updated it accordingly in this PR, but I recommend giving this specific change an extra review.
Let me know if this aligns with your expectations!

yeah this looks great. thanks!


missing images

Hey Megsie. Thanks for this. I was able to merge your PR after resolving a strange conflict in a file you wouldn't have touched 🤷🏼.
Re: this commit, I saved the images from your branch, committed them, and rebuilt the site. Everything seems to display just fine now when viewing your slides from the course website.
Also, two notes regarding ~/website/lectures/week_09/lec_25_intro_shiny_1.Rmd:

I changed the course number from 497 to 549, which meant I had to re-knit your .Rmd.

In the process of addressing (1), I had to install the {emo} package, but apparently it no longer installs on recent versions of R. Thus, I switched all of the emo::ji() calls over emoji::emoji().

Thanks Mark! Yes, sorry about the emo package. I had that same issue and found I had to install from Hadley's GitHub using devtools: devtools::install_github("hadley/emo")
Strangely, now that the images I added are working, the gifs and images I linked aren't hot-linking! That shows me for not making permanent images, but the URLs still work on their own so they should be working online. Hmmm.... I'll see if I can download them or something and re-upload. Sorry it's weird. I'll try to add much more leeway for Wednesday's lecture.


DigitalOcean Droplet to support snapshot

What happened?

I am trying to spin up a DigitalOcean droplet with a specified snapshot as the base image.
  Warning  CannotCreateExternalResource  2m33s                   managed/droplet.compute.do.crossplane.io  creation of Droplet resource has failed: POST https://api.digitalocean.com/v2/droplets: 422 (request "c22f1701-7f91-4852-a925-ca5d6400e3fa") You specified an invalid image for Droplet creation.

How can we reproduce it?

What environment did it happen in?
Crossplane version: 1.11.1

Ah, I got this working.
It failed because I was using the actual snapshot name as opposed to the ID, which is specified here.
I found the snapshot ID by inspecting network (using REST will yield the same result).


Travis CI and coverage

Reduces backend tests to under a second. Adds travis ci and coverage badges. Excluding npm test from build process for now because travis can only support headless and phantomjs does not support ES6 Arrays.

Changes Unknown when pulling cbe782cf4bfbf990333cc80b24d17187ac636e4f on travis into ** on dev**.

Changes Unknown when pulling 0bcf2a3ae764a438c74bc64b8fb803336e10aceb on travis into ** on dev**.


feat(Order/Filter/Basic): eventually_iff_all_subsets and specializations

The set {x | p x} belongs to f iff ∀ s, {x | x ∈ s → p x} ∈ f. Specialization for EventuallyEq and Eventually.LE.
Suggested by @urkud.

My apologies that this PR went under the radar for so long. An automated check was failing for no good reason. @grunweg created some infrastructure to catch such cases in the future: https://jcommelin.github.io/queueboard/help_out.html#inessential-CI-fails

bors r+

My apologies that this PR went under the radar for so long. An automated check was failing for no good reason. @grunweg created some infrastructure to catch such cases in the future: https://jcommelin.github.io/queueboard/help_out.html#inessential-CI-fails

Thank you very much!


⚠ SceneTime has degraded performance

In 4a95ba8, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 9935 ms

Resolved: SceneTime performance has improved in dd7c019 after 6 minutes.


🐛 [Stream Firestore to BigQuery] fs-bq-import-collection doesn't recognize partitioned field

[REQUIRED] Step 2: Describe your configuration

Extension name: firestore-bigquery-export (storage-resize-images, firestore-send-email, etc)
Extension version: 0.1.49

[REQUIRED] Step 3: Describe the problem
When I install extension with following configuration, it creates BigQuery table with createdAt partitioned field.

The important thing is its extension project id and BigQuery id is different (Cross-Platform BigQuery).
But When I run fs-bq-import-collection to backfill, it doesn't recognize any partitioned fields. The script shows following debug message.

{"severity":"WARNING","message":"Did not add partitioning to schema: Partitioning not enabled"}

Steps to reproduce:
Create Firestore table with createdAt TIMESTAMP field and Install extension with above configuration.
Expected result
fs-bq-import-collection  recognize createdAt partition field and set it when importing.
Actual result
fs-bq-import-collection  doesn't recognize createdAt partition field and set null to createAt field when importing.

From the POSTINATALL:
Note: To enable partitioning for a Big Query database, the following fields are required:

 - Time Partitioning option type
 - Time partitioning column name
 - Time partiitioning table schema
 - Firestore document field name

`Clustering` will not need to create or modify a table when adding clustering options, this will be updated automatically.

You're expecting the table to be created with partitioning on createdAt, however the configuration doesn't specify that as a Time partitioning column name, the one you have is timestamp.

Having the same issue. The bigquery table is partitioned (see below) but the following warning is thrown at the start of fs-bq-import-collection.
{"severity":"INFO","message":"BigQuery table with name users_raw_changelog already exists in dataset ***!"}
{"severity":"INFO","message":"Clustering removed on users_raw_changelog"}
{"severity":"WARNING","message":"Did not add partitioning to schema: Partitioning not enabled"}

Table Type
Partitioned
Partitioned by
DAY
Partitioned on field
creation_timestamp
Partition expiration
Partitions do not expire
Partition filter
Not required

I think the OP's issue is misconfiguration of the extension, as @pr-Mais mentions.
@KristofSochan are you also using the script cross-project, or from firestore to bigquery on the same GCP project?
Can you provide:
a) your extension configuration
b) the import script command you are using


Error while compiling on Ubuntu

I compiled groestlcoin on UBUNTU, but i receive this error only on: groestlcoind, groestlcoin-qt !
When i launch groestlcoin-qt, i receive this error message:
Cannot start groestlcoin: click-to-pay hander
This as GUI message.
In the console i have this:
Segmentation fault (core dumped)
Here logs:
cd '/home/developer/groestlcoin'
/usr/bin/make -f Makefile
Making all in src
make[1]: Entering directory '/home/developer/groestlcoin/src'
make[2]: Entering directory '/home/developer/groestlcoin/src'
  CXX      crypto/libgroestlcoinconsensus_la-aes.lo
rm: cannot remove 'crypto/.libs/libgroestlcoinconsensus_la-aes.o': Permission denied
Assembler messages:
Fatal error: can't create crypto/.libs/libgroestlcoinconsensus_la-aes.o: Permission denied
Makefile:7489: recipe for target 'crypto/libgroestlcoinconsensus_la-aes.lo' failed
make[2]: *** [crypto/libgroestlcoinconsensus_la-aes.lo] Error 1
make[2]: Leaving directory '/home/developer/groestlcoin/src'
Makefile:8944: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/developer/groestlcoin/src'
Makefile:685: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

BUILD FAILED (exit value 2, total time: 1s)

Follow step by step this tutorial:
https://groestlcoin.org/forum/index.php?topic=97.0
Not sure why you use make -f Makefile but that will not work

It's exacly the same tutorial i followed !
I return the logs there.

Your logs say otherwise.
I recommend you to use ppa for ubuntu:
https://groestlcoin.org/forum/index.php?topic=441.0

The first logs i got them when compiling and run it from console.
The second is from netbeans.

Paste full logs here showing that you followed the tutorial

You did all right.
It seems to me most likey:

Memory issue. Did you try restart?
Missing library. Did you install all dependencies accordingly? What does the debug.log say?
Hardware issue. Can you try on a fresh Ubuntu 16.04.4 x64 droplet?

Hi,
I just tried again and same issue !
Notice that i am using Ubuntu 16.04.4 x64.
I installed all the libraries like you showed us in the tutorial ! I did everything like it was there.
I restartedand there no memory issue.
Can you please install a fresh Ubuntu 16.04.4 x64 and try in your side ? purhapse you missed some libraries to install in the tutorial, since this one is for a old version purhapse, and sinc eGroestlcoin grow each 3 month with new version, you made some changes that are not noticied there.
I used another PC, installed Ubuntu 16.04.4 x64 etc.... same thing.
Your help will be really appreciated.

Just tested on a fresh new Ubuntu 16.04.4 x64 vps and it works for me.
Try doing a git pull and retry. What does debug.log say?

can you try:
groestlcoind -deamon

groestlcoind -deamon  Same Thing ! (Importantly i want use Groestlcoin QT but same result as groestlcoind).
Can you please tell me where i can find debug.log ?


added local docker cp for TA assess

Added Cp command for copying TA Data Collector to the  local docker

Added Cp command for copying TA Data Collector to the  local docker


Changelog for sept 24 release

Codecov Report

Merging #455 into next will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             next     #455   +/-   ##
=======================================
  Coverage   41.58%   41.58%
=======================================
  Files          30       30
  Lines        1128     1128
  Branches      154      154
=======================================
  Hits          469      469
  Misses        653      653
  Partials        6        6


updating the cron job to test non-TRAPI APIs and only APIs we use

brought up convo w/ @tokebe today.
When the cron job is run, we believe the smartapi registry is pinged (for the latest data from there) and the /meta_knowledge_graph endpoints are pinged for all TRAPI apis.
However, perhaps we only need to ping the APIs we actually use (the config file).
Also, if one of the non-TRAPI APIs is down, we wouldn't know it until we saw all the failed/time-outs in sub-queries. It would help debugging, evaluating query runs, and make queries more efficient if we setup a way to ping those APIs during a cron job. Then if that API was unavailable, we'd put it in our logs + wouldn't send sub-queries to that api

may involve adding examples to endpoints (openapi) so then the smartapi registry pull "uptime" property should be an indicator of whether the api is up or not

When the cron job is run, we believe the smartapi registry is pinged (for the latest data from there) and the /meta_knowledge_graph endpoints are pinged for all TRAPI apis.
However, perhaps we only need to ping the APIs we actually use (the config file).

In my mind, this is a low-priority item because the end result is the same.  We currently are just doing a few more calls than necessary, but this happens during the cron job so it doesn't affect query performance.

Also, if one of the non-TRAPI APIs is down, we wouldn't know it until we saw all the failed/time-outs in sub-queries. It would help debugging, evaluating query runs, and make queries more efficient if we setup a way to ping those APIs during a cron job. Then if that API was unavailable, we'd put it in our logs + wouldn't send sub-queries to that api

I'm not sure I like this proposed behavior. If an API went down, I think we'd want to continue to query that API on subsequent queries rather than assume it was down until the next cron job update (on the assumption that the outage was sporadic and temporary).  Now if we had one TRAPI query that would spawn 50 subqueries to a given API, I think it would probably be fine to skip queries 2-50 if the first one failed.  (Or maybe skip 6-50 if the first five failed?)  I might change my opinion here if failed queries were greatly affecting query times...

Summarizing conversation in Slack, a proposed behavior:
During the course of a query, if a sub-query fails due to timeout, that API is marked as 'down' on a 'cooldown' timer, say, for a period of 5 minutes. During this cooldown, any sub-queries to that API will be automatically skipped, only within the execution of the BTE query in which the sub-query failed (so, a per-query cooldown).
This should protect queries with many sub-queries to the same API from enormous delay due to each sub-query having to timeout, without costing other queries in the event the API came back up more quickly than expected.
Tagging @colleenXu @andrewsu @newgene for thoughts and discussion of this proposed behavior.

Yes, I generally agree with this proposed per-query behavior.  Two parameters that could be used to tune -- the number of timeouts observed to trigger the cooldown (let's call this T), and then the length of the cooldown period (L).  @tokebe's proposal corresponds to T=1 and L=5 mins.  I'd be fine with that, or T=1 and L=999 mins (effectively removing that API from that query entirely), or T=5 and L=999 (maybe the API timed out on a particularly lengthy subquery, but otherwise it was fine?)...

If the concern is execution time of a given query, each query times out after 50s, meaning that each failed query is almost another minute on execution time. That being the case I'd propose T=<2.
I just stated an example L=5, in case it's a long query already and there's a chance it'll somehow query that API again, to give the API a chance to return to operation prior to the end of sub-queries, however it makes sense to simply disable that API for the duration of the query -- I have no opinion one way or the other on that.
There's also an argument to be made to do something a bit more fine-grained, such as limiting to smaller sub-queries on first fail, and then disabling after the second, though implementation may be more complicated depending on how we'd want to do that.

Yeah, good points.  I vote T=1 and L=999 (or hard-coded to be indefinite). Agreed that we could have more complex logic, but not necessary at this stage I think...

copying my feedback/testing from Slack:
This is an example query, since SequenceVariant operations use some APIs that get easily overwhelmed/timeout...
However, this query takes > 6 min to run.
{
    "message": {
        "query_graph": {
            "edges": {
                "e01": {
                    "subject": "n0",
                    "object": "n1"
                },
                "e02": {
                    "subject": "n1",
                    "object": "n2"
                }
            },
            "nodes": {
                "n0": {
                    "ids": ["MONDO:0019391"],
                    "categories": ["biolink:Disease"]
                },
                "n1": {
                    "categories": ["biolink:SequenceVariant"]
                },
                "n2": {
                    "categories": ["biolink:Gene"]
                }
            }
        }
    }
}

It looks like the new code does run.....but a careful look at internals/console-logs would be needed to check that (1) no more sub-queries to those apis are made during this query and (2) on the next query, the limits reset...

I see....it looks like the other sub-queries to an API in a "batch" (since sub-queries seem to be sent in sets of 3?) will still run, even if 1 of them hits a failure/timeout.
But subsequently, that API won't be used.
so....I think this PR looks good. But I don't feel like I did a thorough testing.
in order to test this, I think I need to change the timeout parameters for sub-queries and I'm not sure how to do this. Ideally, I think a test would be:

do a multi-hop query where multiple hops involve the same API (that times out easily). Check that the API timeouts during the first executed hop, and then isn't used for the rest of the query (rest of that hop and later hops).
Then run another query that also uses that API, and check that the limit resets.

@tokebe has said that running the query twice to check that the limit resets has been done. Jackson has also done more testing with this by changing the limits
https://github.com/biothings/call-apis.js/blob/73c26ea4200a28c8b165ef56f44e08f0e7da231b/src/builder/trapi_query_builder.js#L84
https://github.com/biothings/call-apis.js/blob/73c26ea4200a28c8b165ef56f44e08f0e7da231b/src/builder/template_query_builder.js#L92
https://github.com/biothings/call-apis.js/blob/73c26ea4200a28c8b165ef56f44e08f0e7da231b/src/builder/query_builder.js#L93

I should note that groups of sub-queries are run nearly simultaneously, so in many cases a couple queries to the same API will happen and fail around the same time before the API is able to be marked as unavailable.

yep, the queries that fail are noted in a separate part of the logs (# of queries for the QEdge that were successfully executed vs failed). which is diff from skipping them.
@tokebe can we close this issue now?


Add options dropdown to violated policies widget

Description
Note that this PR branches off dv/ROX-11130-action-widgets-scope-bar and will retarget to master when that branch is merged
Adds a dropdown menu to the Policy Violations by Category widget to allow sorting by highest severity counts/total violations as well as filtering by policy lifecycle type.
Also makes minor adjustments to the formatting of new dashboard widget cards to better accommodate this menu and clean up unneeded style classes.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
Test that the default options on page load are set to "Sort By: Severity" and "Policy Lifecycle: All"

Test that sorting by volume displays bars in descending order based on total violation counts.

Test that changing the policy lifecycle filter reduces the number of Violations displayed in the chart.

Test that updating the cluster/namespace filters takes these new filter and sorting options into account.

Current dependencies on/for this PR:

master

PR #2029

PR #2033   👈

PR #2057

This comment was auto-generated by Graphite.


Add support for UTCTime

Add support for UTCTime

Implement functions:

toUTCTime :: RDataType -> Maybe UTCTime
fromUTCTime :: UTCTime -> RDataType

Additionally,

Add to RDataType a RUTCTime constructor
Update toRTable and fromRTable functions for CSV data type to incorporate RUTCTime

Created functions:
toUTCTime :: RTimestamp -> UTCTime
fromUTCTime :: UTCTime -> RTimestamp


feat!: fetch and cache chain info on Provider when initialized

Summary
This PR caches the chainInfo for a given Fuel node on the Provider instance whenever a Provider is initialized.

Note: I know this PR has a lot of changes (~ 80 files), but 90% of these changes are changes made to our test files so that they are adapted to the breaking changes. I recommend focusing on reviewing these files: provider.ts, script-invocation-scope.ts, base-invocation-scope.ts.

Motivation
Please see https://github.com/FuelLabs/fuels-ts/issues/1176 for a detailed breakdown of the problem at hand, but tldr: we are currently using a lot of hardcoded values for some constants that we use when creating transactions. These hardcoded values served us well until now, but we now need to fetch them from the chain dynamically. This has been requested as a top priority by the frontend team.
Breaking Changes
Because of the nature of the changes introduced in this PR, and the fact that Provider is used so widely in our SDK, there are multiple breaking changes that we need to be aware of and need to communicate to our users:
1. Initializing the Provider
// Used to be:
const provider = new Provider(url)

// New API:
const provider = await Provider.connect(url)

2. Wallet methods
All of these methods now require a Provider to be passed in:
const provider = await Provider.connect(url);

// Some of these methods used to accept a URL instead of a `Provider` object.
// Note that the `provider` param *has* to be a `Provider` object now.
WalletUnlocked.fromSeed(seed, provider, path);
WalletUnlocked.fromMnemonic(mnemonic, provider, path, passphrase);
WalletUnlocked.fromExtendedKey(extendedKey, provider);
await WalletUnlocked.fromEncryptedJson(jsonWallet, password, provider);

Wallet.fromAddress(address, provider);
Wallet.fromPrivateKey(pk, provider);

Wallet.generate({ provider });

3. Account class
new Account(address, provider);

4. PrivateKeyVault
// these are the options that are accepted by the `PrivateKeyVault` constructor. `provider` is a required input now.
interface PkVaultOptions {
  secret?: string;
  accounts?: Array<string>;
  provider: Provider;
}

5. MnemonicVault
Same as PrivateKeyVault. The constructor requires a provider to be passed in.
6. WalletManager
The VaultConfig now requires a provider to be passed in.
export type VaultConfig = {
  type: string;
  title?: string;
  secret?: string;
  provider: Provider;
};

7. Predicate
// `provider` is no longer optional. there is a change in order of the parameters here.
new Predicate(bytes, chainId, provider, jsonAbi);

We actually no longer need a chainId to be passed in the Predicate constructor since we are now always expecting a provider, but I am not sure if I should include this change in this PR here. This change alone will introduce even more refactors across a whole bunch of tests, so I want to open a follow-up PR for that. I will make sure we merge that PR too before making a release. Just to reduce the clutter in this PR, I think it is a good idea to keep it separate.
Other notes
To demonstrate the fact that we can now use fresh on-chain values for some of the previosuly hard-coded constants, I have refactored the usage of the VM_TX_MEMORY constant. This constant is used to calculate the contract call script's data offset.

A bunch of spaghetti code still, don't review yet pls :P

Marking this as a draft briefly while I make some adjustments and put the PR in a better place to be reviewed.

Also, don't forget to add - close #NNN tags for issues #1050 and #1176 on the PR description.

@arboleya I think we can close #1176 but not #1050 quite yet. I believe #1050 should be closed once we eliminate the usage of all the hardcoded transaction parameter values. This PR only replaces VM_TX_MEMORY as a proof of concept, but doesn't replace all of them. Maybe we should maintain a list of all the hardcoded values in #1050, and then tick them off one-by-one.

@LuizAsFight thanks so much for reviewing again and sharing that gist mate. 🙏🏻
Two things:

We opted against going with the approach you suggested with the create method and avoiding a breaking change on the constructor itself. We opted against this because this won't break existing code for users at compile-time since there are no changes to the constructor's function signature. This will still break their code at run-time, though. For such a significant breaking change, we think this is less ideal than just changing the function signature and signalling that something has changed. If the approach you suggested was avoiding a breaking change altogether, we would go with it but in this case it looks like a breaking change is unavoidable either way - it will just be disguised under something else. We think it's better to just loudly throw and break things now rather than later in this case.

I also saw that you added a helper for gas config. I have already filed a follow-up issue for this and we'll get this added ASAP.

TLDR since you guys last reviewed:

Made the Provider constructor private
Removed chainInfo from the constructor
Renamed connect to create (h/t @LuizAsFight 🙏🏻)
Deleted refreshChainInfoCache, getChainInfoWithoutInstance, getCachedChainInfo
Added a nodeInfoCache on the Provider class
Added fetchChain, fetchNode, getNode
Refactored getChain
Added getGasConfig (h/t @LuizAsFight @Torres-ssf 🙏🏻)
Removed getNodeInfo and the getInfo GQL query as it's not needed anymore. I replaced this with a clearer query for nodeInfo


python311Packages.maison: 1.4.1 -> 1.4.2

Diff: https://github.com/dbatten5/maison/compare/refs/tags/v1.4.1...v1.4.2
Changelog: https://github.com/dbatten5/maison/releases/tag/v1.4.2
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] Fits CONTRIBUTING.md.

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

@ofborg eval


Rust 2020 roadmap

Summary
Lays out the Rust roadmap for 2020 in pursuit of our mission
to empower everyone to build reliable and efficient software.
The roadmap takes the form of the following goals for the project:

Prepare for a possible Rust 2021 Edition
Followthrough on in-progress designs and efforts
Improve project functioning and governance:

Improve visibility into the state of initiatives and design efforts
Increase mentoring, leadership, and organizational bandwidth
Make design discussions more productive and less exhausting

The roadmap this year is different in structure than prior years.  In
particular, we have avoided setting precise goals, in favor of
describing more general mandates and themes.
We chose to take this approach for a few reasons:

The roadmap RFC doesn't seem like an appropriate place to make
decisions on specific solutions. Those should be discussed in their
own, dedicated RFCs.
We wanted to encourage teams and project members to think about how these
mandates apply best to the particular questions that they are working with.

Rendered view
cc @rust-lang/core
--
A note on authorship: This RFC was jointly edited. Particular thanks to @Mark-Simulacrum, @nrc, and @aidanhs for their feedback and edits.

I have pushed up a few new commits which try to incorporate the outstanding feedback, though for all elements I pretty much feel that for the most part it is mostly broadening the RFC into discussion of the general idea rather than scope-setting, i.e., not normative content.

@rfcbot fcp merge
Thanks to everyone for the feedback and participation. This thread seems to have approached a stable state, so I'm moving that we merge this RFC.

Thanks everyone!

The roadmap says that the Rust 2019 survey results will be released in January. Unless someone in the core team has a time machine that seems unlikely 😛

wanna make a PR fixing that?

@Diggsey We have an outline of the post about the survey results, and are actively working on it. It hasn't been forgotten.

Can someone update the Rendered link to point to https://github.com/rust-lang/rfcs/blob/master/text/2857-roadmap-2020.md?

@mikeyhew Done.


[CHORE] Draw up wireframes and sitemap

Chore
Draw up wireframes and sitemap
Why is this important

To ensure all key pages are considered, showing their relationship to each other.

Provide a detailed view of the content that will appear on each page

Additional context

This task has been completed.


Cel Damage HD [PCSE00422]

App summary

App name: Cel Damage HD
App serial: PCSE00422
App version: 1.00

Vita3K summary

Version: v0.1.8
Build number: 3162
Commit hash: https://github.com/vita3k/vita3k/commit/3abd4e36
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Sam
OS: Windows 10
CPU: AMD 5500u
GPU: AMD Radeon Graphics
RAM: 6 GB

Issues

Screenshots

Log

Recommended labels

Intro
unicorn error
C?

Vita3K summary

Version: v0.1.8
Build number: 3212
Commit hash: https://github.com/vita3k/vita3k/commit/7170fc69
CPU backend: Dynarmic
GPU backend: Vulkan

App summary

App name: Cel Damage HD
App serial: PCSE00422
App version: 1.00

Screenshots

Log
vita3k.log
https://github.com/Vita3K/compatibility/labels/Ingame -
https://github.com/Vita3K/compatibility/labels/graphics bug

I believe that it's ingame +, not ingame -


[BUG] Invalid certificate on marcelotrevisani.com/grayskull

Describe the bug
A clear and concise description of what the bug is.
When generating a recipe with https://www.marcelotrevisani.com/grayskull a certificate error is returned.
To Reproduce
Steps to reproduce the behavior:

Go to https://www.marcelotrevisani.com/grayskull
Enter package
See error

Expected behavior
A clear and concise description of what you expected to happen.
The certificate should be generated.
Outputs
If applicable, add the output to help explain your problem.
Safari:
Error - requests
The certificate for this server is invalid. You might be connecting to a server that is pretending to be “marcelotrevisani.info”, which could put your confidential information at risk.
Chrome:
Error - requests
Failed to fetch
Firefox:
Error - requests
NetworkError when attempting to fetch resource.
Environment:

website

Additional context
Add any other context about the problem here.
Hi @marcelotrevisani,
sorry if this is the wrong place to file this. Let me know if I should file it somewhere else or close it entirely.

Hi @BastianZim , that is the right place, don't worry! :)
Yes, it is not working indeed, I believe it is because my SSL certificate has expired, I renewed but it seems I missed something
I will take a look at that, thanks for reporting it!
Any updates I will keep you posted.

Perfect, thank you! :)

I updated the SSL certificates and the configuration on the webserver, it is working now :tada:
Thanks for reporting it! :smiley:
If the problem persists or if you encounter any other problem please let me know

Confirmed working, thanks for the quick fix! 🎉😃


Add topic chip text color

What 🕵 🔍
Add text style for topic chip

Codecov Report
Base: 45.99% // Head: 45.87% // Decreases project coverage by -0.12% :warning:

Coverage data is based on head (c9af7cf) compared to base (e7dea42).
Patch coverage: 0.00% of modified lines in pull request are covered.

:exclamation: Current head c9af7cf differs from pull request most recent head 6b2aaf1. Consider uploading reports for the commit 6b2aaf1 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #126      +/-   ##
==========================================
- Coverage   45.99%   45.87%   -0.13%
==========================================
  Files          58       58
  Lines        2198     2206       +8
==========================================
+ Hits         1011     1012       +1
- Misses       1187     1194       +7

Impacted Files
Coverage Δ

lib/src/linden/xcolors.dart
28.83% <0.00%> (-0.73%)
:arrow_down:

lib/src/linden/xstyles.dart
36.19% <0.00%> (-0.71%)
:arrow_down:

lib/src/widget/button/app_raised_button.dart
80.30% <0.00%> (-0.95%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix: disallow null input value

Disallow null input value by adding nullable argument to variables azuread_administrator_login_username and azuread_administrator_object_id, to catch errors related to these earlier in deployment process.

Tests pass.


Improve prioritization of LZ checklist

Existing LZ checklist has most of the items classified as "Medium". We should probably objectively decide what the three different levels mean, and reclassify the checks.
For example, as description of the levels something like:

High: mandatory recommendation, regardless of customer requirements
Medium: this recommendation can have a large impact in the design, but it is not necessarily mandatory
Low: nice to have

After the meaning of the priorities is decided, we should reprioritize the different checks of the LZ checklist.

The current list does have High, Medium, and Low, but we can still use this item to align.  It might make sense to combine this with other review items.

As part of #792, some of the priorities are adjusted.


runtime: deprecate Func/FuncForPC

Go 1.7 introduced the CallersFrames API:

The new function CallersFrames translates a PC slice obtained from Callers into a sequence of frames corresponding to the call stack. This new API should be preferred instead of direct use of FuncForPC, because the frame sequence can more accurately describe call stacks with inlined function calls.

I understand that in Go 1.9, mid-stack inlining will make the results significantly worse for callers that are still using FuncForPC instead of CallersFrames. However, in the runtime documentation I don't see anything to steer the user towards one or the other.
Should we mark Func and FuncForPC as deprecated? Is there some situation to use them instead of CallersFrames?
@ianlancetaylor @aclements @davidlazar

(I guess that the Callers doc itself does say "To easily look up file/line information for the call sequence, use Frames.")

Yes, the documentation should definitely steer people more strongly in the right direction than it does now. Thanks for creating an issue to track this.

FuncForPC should not in general be used with values returned by Callers or Caller, but it is still meaningful and has no replacement for other uses.  For example, the use in funcName and methodName in reflect/value.go is entirely legitimate.


Bump @auth0/nextjs-auth0 from 2.7.0 to 3.2.0 in /identity/webapp, second try

Reverts wellcomecollection/wellcomecollection.org#10561
So the first merge in made the requests not work (change email and password were trialled and failed). I'm not sure why and not super sure how we could test it properly before merging it. Will need further investigation.
Relates to #10577

Unhelpful logs here

For posterity, looks like it was alright, but we did upgrade identity (to node18) last Friday and no errors since so it was probably linked...?