microserver: init at 0.1.8

Motivation for this change
I use this fast and tiny server during development.
Things done

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

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

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

Do not build for me:

@KAction You're right. I'm sorry!

Looks fine to me now:

does not build for me. :(
macOS 10.15.7
nix 2.3.7
my default.nix file:
{ pkgs ? import <nixpkgs> { } }:

pkgs.mkShell { buildInputs = [ pkgs.microserver ]; }

output:
   Compiling tempfile v3.1.0
error: linking with `/nix/store/sw7b2gcklaj3iy5ikv7ag163bpry3ivb-clang-wrapper-7.1.0/bin/cc` failed: exit code: 1
  |
  = note: "/nix/store/sw7b2gcklaj3iy5ikv7ag163bpry3ivb-clang-wrapper-7.1.0/bin/cc" "-m64" "-L" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.0.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.1.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.10.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.11.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.12.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.13.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.14.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.15.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.2.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.3.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.4.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.5.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.6.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.7.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.8.rcgu.o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.build_script_build.1fverjuu-cgu.9.rcgu.o" "-o" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/build/mime_guess-2441a9ba05aecf8b/build_script_build-2441a9ba05aecf8b.1ip2hky8bm5fz0lz.rcgu.o" "-Wl,-dead_strip" "-nodefaultlibs" "-L" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps" "-L" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/libphf_codegen-cc10978227834775.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/libphf_generator-d19ba0836a99459e.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand-c80278d89532d456.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand_xorshift-a9e490ec3e54a30e.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand_pcg-d374910d8ec9fe0d.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand_hc-e7e7024367e450b1.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand_chacha-0e0583ca9ec60169.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand_isaac-c4fe828ee4c345ea.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand_core-3dcf0e027f6ce744.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand_os-9240339bdf4485ee.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand_jitter-0f79a6f6ffdb4a4f.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/liblibc-07960e5d6c915b82.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/librand_core-eb1af1b55a172a20.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/libphf_shared-6e4f8b4b399de620.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/libunicase-ba4907bed8a636d3.rlib" "/private/var/folders/st/n_jym15x12jc_3pqkqb4t1_40000gn/T/nix-build-microserver-0.1.8.drv-0/source/target/release/deps/libsiphasher-8491031c776c5936.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/libstd-f900c16b5f7ca499.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/libpanic_unwind-a7261fee2449241a.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/libhashbrown-a6401e0a1e6e3dff.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/librustc_std_workspace_alloc-729ff2cbee9bdc23.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/libbacktrace-594b043cb032b706.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/libbacktrace_sys-ad779468bf515a8f.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/librustc_demangle-de8e9d4775e49d47.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/libunwind-caa8900842181a36.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/libcfg_if-115396c89bf540a3.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/liblibc-3cd5113a65ba2e5e.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/liballoc-a9b05e1f781b45d0.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/librustc_std_workspace_core-b883374262ffe063.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/libcore-5772b503d5985844.rlib" "/nix/store/3rf1v07d5ikm14532qdwnrd34hnkqd7j-rustc-1.45.2/lib/rustlib/x86_64-apple-darwin/lib/libcompiler_builtins-ff0db0c073b4042c.rlib" "-framework" "Security" "-lSystem" "-lresolv" "-lc" "-lm"
  = note: ld: framework not found Security
          clang-7: error: linker command failed with exit code 1 (use -v to see invocation)

error: aborting due to previous error

error: could not compile `mime_guess`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
builder for '/nix/store/fskac1md3dcf9n1lr59hq4r3hlgvnq0v-microserver-0.1.8.drv' failed with exit code 101
error: build of '/nix/store/fskac1md3dcf9n1lr59hq4r3hlgvnq0v-microserver-0.1.8.drv' failed

please let me know if i'm doing something wrong.


Revert "refactor(fromPromise): expose fromPromise through rxjs export"

Reverts ReactiveX/rxjs#3375
To decrease the API surface area, we shouldn't export fromPromise, as any operator or function that accepts an Observable (such as mergeMap or defer) will include most of from's logic anyhow.

Coverage decreased (-0.0004%) to 97.516% when pulling 5e65d0300dd178ae9f4b5900c5ac39d2518034bb on revert-3375-export_fromPromise into 1e4ca05ab247eedc3d7db233874e650439f09fbd on master.


fix: 返回项目信息

这个 PR 实现什么功能/修复什么问题:
返回项目信息
是否需要 backport 到之前的 release 分支:

release/3.2

/area region
/cc @zexi

Codecov Report

Merging #6549 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

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


Add histogram/bucketing visualization

Either as a new visualization or extended distribution bar chart.

Has histogram been added to caravel ?

@shrk duplicate issue is here: https://github.com/airbnb/caravel/issues/714


NetInfo addEventListener is not working on Android

Description
[My team is working on react-native with redux-saga project.  We tried to register NetInfo.addEventListener at redux-saga code. That means, NetInfo.addEventListener is not called from componentDidMount function and it worked properly on iOS.  However, on Android, this doesn't work as we expected.  On android, it seems like NetInfo event listener only works when we registered it on App.js componentDidMount function. ]
Additional Information

React Native version: [0.33.0]
Platform: [Android]
Operating System: [MacOS]

Can you provide a minimal amount of code to reproduce this on rnplay.org? This is necessary for people to be able to see and debug the issue being reported.
Closing this issue as it is not actionable. Please open a new one with an rnplay link (preferred), or link to a GitHub repo with clear instructions how to repro.


Split README.md into smaller files

The README.md is really long. Considering that it loads every time someone goes to the main page, wouldn't it be better to keep some of it (e.g., the FAQ) in separate files?

Currently everything are in the same file as it's easier to generate the man page.

I feel it's actually easier to search through if they're all on the same page. Just my personal opinion.

Are we going to split the ReadMe or leaving it as it is?

I am available to contribute if you decide on spliting the README.


Expose all BSP messages used by SourceKit-LSP to BSP servers 🚥 #1687

Depends on https://github.com/swiftlang/sourcekit-lsp/pull/1687

The interaction to an out-of-process BSP server still went through the BuildServerBuildSystem, which doesn’t forward all messages to the build system and uses the old push-based model for build settings.
If we discover that the BSP server supports the new pull-based build settings model, we now forward all methods to it directly, without going through BuiltInBuildSystemAdapter, which has been renamed to LegacyBuildServerBuildSystem.
rdar://136106323
rdar://127606323
rdar://126493405
Fixes #1226
Fixes #1173

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test

@swift-ci Please test Windows


Installation Guide

Getting rex set up is still somewhat rough, should we add an install guide here or stick with https://github.com/mechaphish/mecha-docs? Either way, it should be linked to in the REAME.md.
(re: email from @Owlz)

Hey David,
Not a VM specifically for it. I do recall having many-a-issue on it. Two things, the first is the correct (or at least required at the time) order of installing packages to get it to install:
https://github.com/shellphish/shellphish-qemu.git
https://github.com/mechaphish/povsim.git
https://github.com/salls/angrop.git
https://github.com/mechaphish/compilerex.git
https://github.com/shellphish/rex.git
https://github.com/angr/tracer
https://github.com/shellphish/shellphish-afl.git
The second, I have a bash script that will install/compile all of Mechaphish reliably. This would probably be overkill for what you're asking, but you can likely remove unwanted components from the install line and it should still give you a working rex copy. It basically boils down to these two lines (with some bash in-between):
sudo apt-get update
sudo apt-get install -y virtualenvwrapper python2.7-dev build-essential sudo libxml2-dev libxslt1-dev git libffi-dev cmake libreadline-dev libtool debootstrap debian-archive-keyring libglib2.0-dev libpixman-1-dev libpq-dev python-dev libc6:i386 libncurses5:i386 libstdc++6:i386 zlib1g:i386 pkg-config zlib1g-dev libtool libtool-bin wget automake autoconf coreutils bison libacl1-dev qemu-user qemu-kvm socat postgresql-client nasm binutils-multiarch llvm clang
git clone https://github.com/angr/angr-dev.git $MechaPhishDIR
cd $MechaPhishDIR
./setup.sh -p mechaphish -r https://github.com/shellphish -r https://github.com/mechaphish -r https://github.com/salls -D
ana idalink cooldict mulpyplexer monkeyhex superstruct
shellphish-afl shellphish-qemu capstone unicorn peewee
archinfo vex pyvex cle claripy simuvex angr angr-management angr-doc
binaries identifier fidget angrop tracer fuzzer driller
compilerex povsim rex farnsworth patcherex colorguard
common-utils network_poll_creator patch_performance
worker meister ambassador scriba virtual-competition manual-interaction

I've had to update that setup.sh line to remove unicorn given recent changes. unicorn can be pip installed now.

Thank you !


feat: Need to support aync logging in the library to record metadata and logs from execution.

Is your feature request related to a problem? Please describe.
Currently fms-hf-tuning uses transformer logging which can be replaced by async logging library which supports logging metadata  and logs without being tied to upstream modules like tranformers.
Describe the solution you'd like
Replace tranformer logging with asyn logger.
cc @ashokponkumar

related and possibly duplicate of - https://github.com/foundation-model-stack/fms-hf-tuning/issues/195 and https://github.com/foundation-model-stack/fms-hf-tuning/issues/194


Sizes 2 to 128 for divide and conquer

New sizes to add.

SMatrix<double, 4, 4> is duplicated, please fix :)


Adding CSS classes make selecting dropdowns easier

This PR adds classes to the dropdown select elements to aid other software that uses selectors to interact with these elements (like webdriver)

:+1:

Thanks! I'll merge this now but I need to get someone else set up to publish to npm.


Update eslint-config to v1.0.0

Summary
Small PR to update eslint-config-react-native-community to v1.0.0

Test Plan

What's required for testing (prerequisites)?
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅❌

Android
✅❌

Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

thanks!


copyWith method fails to include base class parameters in inheritance

Use case
Hi there !
I’m trying to use the copyWith method in a Dart class hierarchy that involves inheritance. I’m not sure if I'm encountering a real issue or if I'm misunderstanding something. Apologies if it's the latter!
(Edit : Issue is similar to https://github.com/schultek/dart_mappable/issues/215#issuecomment-2260235384 but I believe that the use case is different enough to need a different solution.)
Here's the setup I'm working with:
@MappableClass()
class State with StateMappable {
  final bool aMember;

  State({required this.aMember});
}

@MappableClass()
class InitialState extends State with InitialStateMappable {
  InitialState() : super(aMember: true);
}

void main() {
  State state = InitialState(aMember: true);
  state.copyWith(aMember: false);
}

Expected behavior
I expect the copyWith method to include all parameters from the base class constructor. In this example, it should include aMember.
Actual Issue
The generated copyWith method does not include aMember as a parameter.
Here is a screenshot of the issue :

Here is a test project that recreates this issue : dart-mappable-copy-with.zip
Findings and Workarounds

If I add aMember to the InitialState constructor, the copyWith method works as expected. However, this defeats the purpose of having InitialState with a default value for aMember.

@MappableClass()
class InitialState extends State with InitialStateMappable {
  // Adding the param to the constructor makes the copyWith work, but defeats the purpose of the class
  InitialState({required super.aMember});
}

void main() {
  State state = InitialState(aMember: true);
  state.copyWith(aMember: false); // Works ✅
}

It seems that all subclasses must explicitly declare the aMember parameter in their constructors for copyWith to function correctly. If I add another subclass without aMember, the copyWith method fails again :

@MappableClass()
class OtherState extends State with OtherStateMappable {
  final String otherMember;
  OtherState({required this.otherMember}) : super(aMember: false);

  // Adding aMember to this constructor also makes copyWith work
  // OtherState({required this.otherMember, required super.aMember});
}

void main() {
  State state = InitialState(aMember: true);
  state.copyWith(aMember: false); // Does not work ❌ "The named parameter 'aMember' isn't defined."
}

Questions:

Is this the intended behavior of the copyWith method in this context?
Is there a way to generate the copyWith method correctly without modifying every subclass?

Hi, yes you found the right comment: https://github.com/schultek/dart_mappable/issues/215#issuecomment-2260235384
This is the same case. I would like to improve this, but its a limitation created by the inheritance structure that I cannot fix. All subclasses must have a parameter in their constructor for it to be usable in the superclasses copyWith.
I think the best workaround in your case is to make it a optional parameter with a default value:
class InitialState extends State with InitialStateMappable {
  InitialState({super.aMember = false});
}


Pre_Translation repo changed from upstream repo to forked repo

The change for the pre_translation goes as below.
Initially, we were cloning the main repo (e.g. ansible/galaxy_ng) as per the playbook and the pre_translation script was supposedly be residing in the same repo.
But now, we are cloning the forked repo (e.g. adityamulik/galaxy_ng) and then we are fetching/ rebasing with the main repo here (e.g. ansible/galaxy_ng) and extracting the strings from the forked repo which are later uploaded to Memsource.
This helps us to keep the shell scripts (pre_translation/ post_translation.sh) in the forked repo itself and not in the main repo.
The implementation is already in place for the post_translation role. (Ref: https://github.com/adityamulik/ansible-collection-memsource/blob/367bf266d01f1d6885afade6a61586d70312ace1/roles/post_translation/tasks/move_translated_strings.yml#L22)
Considering the above being done, we would require to add
pre_translation.sh
post_translation.sh
to the ansible/galaxy_ng -> .gitignore
That would help us, when we are pushing back the translated strings once retrieved from memsource, these shell scripts don't get added to the PR which is supposed to push back the strings.

The changes are actively tracked on https://github.com/ansible/ansible-collection-memsource/pull/45


Workaround to display Points on map

Implement workaround to properly display Point geometries in map, while still displaying Polygons properly.
Solves issue https://github.com/Corvince/mesa-geo/issues/17.
Fix was suggested by @JHindelang and @applibres in that issue, with Polygons suggestion by @Corvince .

Thank you for the contribution! Just a quick question: The geojsonMarkerOptions doesn't seem to be used anywhere?

@Corvince , you're right.. I had assumed it was implicitly being used by some of the functions, but I just removed it and everything still works. So, I'll remove it from the PR.


[RESOLVED]

Tried solving issue #345
Variable Names Must Starting with a Letter, Underscore (_), or Dollar Sign ($)
and showing an error when people try to save an environment with an invalid name.

Closing this PR as the latest version of Bruno supports . in variable names


feat: relate for loops over List with foldlM

There are many more lemmas about foldlM, so this may be useful for reasoning about for loops by transforming them into folds.
The transformation includes accounting for monad effects, but does have a mild performance difference in that short-circuiting on ForInStep.done is replaced by traversing the rest of the list with a noop.

Also consider upstreaming batteries#814.


cmake fix typo eigen include dirS

Fix typo in CmakeLists related to eigen include dir variable.
Not sure why but on my machine EIGEN3_INCLUDE_DIR is empty while EIGEN3_INCLUDE_DIRS has the include path properly defined.
Ubuntu 14.04 + ROS Indigo.

Looks like the inverse problem happens on Jenkins.
I'll close this PR in favor of an issue...


Analyzer support for nonfunction type aliases

Main language issue: https://github.com/dart-lang/language/issues/65
Specification: https://github.com/dart-lang/language/blob/master/accepted/future-releases/generalized-typedef-2018/feature-specification.md

We implemented everything we know of, and the feature was released.


wildfly:run failing to deploy

I might be missing something obvious but after cloning https://github.com/wildfly/quickstart, I've done mvn wildfly:run on the helloworld project, which runs WildFly on <IP_ADDRESS>:8080. However, there is nothing deployed on http://<IP_ADDRESS>:8080/wildfly-helloworld, and I get the following error when closing it down:
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:start (default-cli) on project wildfly-helloworld: The server failed to start: Managed server was not started within [60] s -> [Help 1]

If I upgrade the plugin to 1.1.0.Alpha2 I don't need to close Maven, it will just die with that error after 60 seconds have passed.
I've also tried with mvn wildfly:start and even mvn wildfly:start wildfly:deploy with similar results.

Are you running it from the root quickstart directory or from a specific sub-module?

I'm running it from the helloworld directory.
On May 27, 2015 1:29 AM, "James R. Perkins"<EMAIL_ADDRESS>wrote:

Are you running it from the root quickstart directory or from a specific
sub-module?
—
Reply to this email directly or view it on GitHub
https://github.com/wildfly/wildfly-maven-plugin/issues/41#issuecomment-105568526
.

Have you made any changes to the configuration? It seems to work fine for me.
This is what my output looks like:
[jperkins@localhost helloworld]$ mvn wildfly:run
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building WildFly Quickstarts: Helloworld 9.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> wildfly-maven-plugin:1.0.2.Final:run (default-cli) > package @ wildfly-helloworld >>>
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ wildfly-helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ wildfly-helloworld ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ wildfly-helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ wildfly-helloworld ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ wildfly-helloworld ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-war-plugin:2.5:war (default-war) @ wildfly-helloworld ---
[INFO] Packaging webapp
[INFO] Assembling webapp [wildfly-helloworld] in [/home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-helloworld]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/src/main/webapp]
[INFO] Webapp assembled in [40 msecs]
[INFO] Building war: /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-helloworld.war
[INFO]
[INFO] <<< wildfly-maven-plugin:1.0.2.Final:run (default-cli) < package @ wildfly-helloworld <<<
[INFO]
[INFO] --- wildfly-maven-plugin:1.0.2.Final:run (default-cli) @ wildfly-helloworld ---
[INFO] JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>-38.b14.fc21.x86_64/jre
[INFO] JBOSS_HOME=/home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-run/wildfly-8.2.0.Final

[INFO] Server is starting up. Press CTRL + C to stop the server.
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
May 26, 2015 2:12:03 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.2.2.Final
May 26, 2015 2:12:03 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.2.2.Final
May 26, 2015 2:12:03 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.3.Final
14:12:03,991 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
14:12:04,140 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
14:12:04,185 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
14:12:04,813 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
14:12:04,835 INFO  [org.xnio] (MSC service thread 1-14) XNIO version 3.3.0.Final
14:12:04,848 INFO  [org.xnio.nio] (MSC service thread 1-14) XNIO NIO Implementation Version 3.3.0.Final
14:12:04,868 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
14:12:04,871 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
14:12:04,883 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
14:12:04,893 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]
14:12:04,895 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
14:12:04,908 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem
14:12:04,913 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
14:12:04,926 INFO  [org.jboss.as.security] (MSC service thread 1-13) JBAS013170: Current PicketBox version=4.0.21.Final
14:12:04,928 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
14:12:04,933 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:12:04,934 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = h2
14:12:04,948 INFO  [org.jboss.remoting] (MSC service thread 1-14) JBoss Remoting version 4.0.6.Final
14:12:04,962 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting
14:12:04,962 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017502: Undertow 1.1.0.Final starting
14:12:04,984 INFO  [org.jboss.as.naming] (MSC service thread 1-13) JBAS011802: Starting Naming Service
14:12:04,984 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-9) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:12:05,159 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-run/wildfly-8.2.0.Final/welcome-content
14:12:05,169 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017525: Started server default-server.
14:12:05,182 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017531: Host default-host starting
14:12:05,226 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017519: Undertow HTTP listener default listening on /<IP_ADDRESS>:8080
14:12:05,328 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-15) JBAS015012: Started FileSystemDeploymentService for directory /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-run/wildfly-8.2.0.Final/standalone/deployments
14:12:05,367 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-13) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:12:05,499 INFO  [org.jboss.ws.common.management] (MSC service thread 1-10) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
14:12:05,570 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://<IP_ADDRESS>:9990/management
14:12:05,570 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://<IP_ADDRESS>:9990
14:12:05,571 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 1823ms - Started 184 of 234 services (82 services are lazy, passive or on-demand)
[INFO] Deploying application 'wildfly-helloworld.war'

14:12:09,227 INFO  [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-run/wildfly-8.2.0.Final/standalone/data/content/fb/79a988aa2767bb2a55248fca8875fc534134ec/content
14:12:09,241 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015876: Starting deployment of "wildfly-helloworld.war" (runtime-name: "wildfly-helloworld.war")
14:12:09,482 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment wildfly-helloworld.war
14:12:09,533 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.1.3.Final
14:12:09,652 INFO  [org.jboss.weld.deployer] (MSC service thread 1-12) JBAS016005: Starting Services for CDI deployment: wildfly-helloworld.war
14:12:09,682 INFO  [org.jboss.weld.Version] (MSC service thread 1-12) WELD-000900: 2.2.6 (Final)
14:12:09,721 INFO  [org.jboss.weld.deployer] (MSC service thread 1-9) JBAS016008: Starting weld service for deployment wildfly-helloworld.war
14:12:10,439 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017534: Registered web context: /wildfly-helloworld
14:12:10,497 INFO  [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "wildfly-helloworld.war" (runtime-name : "wildfly-helloworld.war")

No, I haven't, except changing the version of the plugin to 1.1.0.Alpha2 to
test, but both versions give me the same problem. I don't get that line
with the "Deploying wildfly-helloworld.war" or any of the next ones.
I'll post my output in a while, but it looks similar to me.
I'm running on OSX 10.9.3, just in case that changes anything.
Also, using mvn wildfly:deploy after running a separate Wildfly
installation works fine.
On May 27, 2015 7:13 AM, "James R. Perkins"<EMAIL_ADDRESS>wrote:

Have you made any changes to the configuration? It seems to work fine for
me.
This is what my output looks like:
[jperkins@localhost helloworld]$ mvn wildfly:run
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building WildFly Quickstarts: Helloworld 9.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> wildfly-maven-plugin:1.0.2.Final:run (default-cli) > package @ wildfly-helloworld >>>
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ wildfly-helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ wildfly-helloworld ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ wildfly-helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ wildfly-helloworld ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ wildfly-helloworld ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-war-plugin:2.5:war (default-war) @ wildfly-helloworld ---
[INFO] Packaging webapp
[INFO] Assembling webapp [wildfly-helloworld] in [/home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-helloworld]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/src/main/webapp]
[INFO] Webapp assembled in [40 msecs]
[INFO] Building war: /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-helloworld.war
[INFO]
[INFO] <<< wildfly-maven-plugin:1.0.2.Final:run (default-cli) < package @ wildfly-helloworld <<<
[INFO]
[INFO] --- wildfly-maven-plugin:1.0.2.Final:run (default-cli) @ wildfly-helloworld ---
[INFO] JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>-38.b14.fc21.x86_64/jre
[INFO] JBOSS_HOME=/home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-run/wildfly-8.2.0.Final
[INFO] Server is starting up. Press CTRL + C to stop the server.
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
May 26, 2015 2:12:03 PM org.xnio.Xnio
INFO: XNIO version 3.2.2.Final
May 26, 2015 2:12:03 PM org.xnio.nio.NioXnio
INFO: XNIO NIO Implementation Version 3.2.2.Final
May 26, 2015 2:12:03 PM org.jboss.remoting3.EndpointImpl
INFO: JBoss Remoting version 4.0.3.Final
14:12:03,991 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
14:12:04,140 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
14:12:04,185 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
14:12:04,813 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
14:12:04,835 INFO  [org.xnio] (MSC service thread 1-14) XNIO version 3.3.0.Final
14:12:04,848 INFO  [org.xnio.nio] (MSC service thread 1-14) XNIO NIO Implementation Version 3.3.0.Final
14:12:04,868 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
14:12:04,871 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
14:12:04,883 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
14:12:04,893 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]
14:12:04,895 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
14:12:04,908 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem
14:12:04,913 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
14:12:04,926 INFO  [org.jboss.as.security] (MSC service thread 1-13) JBAS013170: Current PicketBox version=4.0.21.Final
14:12:04,928 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
14:12:04,933 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:12:04,934 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = h2
14:12:04,948 INFO  [org.jboss.remoting] (MSC service thread 1-14) JBoss Remoting version 4.0.6.Final
14:12:04,962 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting
14:12:04,962 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017502: Undertow 1.1.0.Final starting
14:12:04,984 INFO  [org.jboss.as.naming] (MSC service thread 1-13) JBAS011802: Starting Naming Service
14:12:04,984 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-9) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:12:05,159 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-run/wildfly-8.2.0.Final/welcome-content
14:12:05,169 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017525: Started server default-server.
14:12:05,182 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017531: Host default-host starting
14:12:05,226 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017519: Undertow HTTP listener default listening on /<IP_ADDRESS>:8080
14:12:05,328 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-15) JBAS015012: Started FileSystemDeploymentService for directory /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-run/wildfly-8.2.0.Final/standalone/deployments
14:12:05,367 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-13) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:12:05,499 INFO  [org.jboss.ws.common.management] (MSC service thread 1-10) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
14:12:05,570 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://<IP_ADDRESS>:9990/management
14:12:05,570 http://<IP_ADDRESS>:9990/management14:12:05,570 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://<IP_ADDRESS>:9990
14:12:05,571 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 1823ms - Started 184 of 234 services (82 services are lazy, passive or on-demand)
[INFO] Deploying application 'wildfly-helloworld.war'
14:12:09,227 INFO  [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location /home/jperkins/projects/jboss/wildfly/wildfly-quickstarts/helloworld/target/wildfly-run/wildfly-8.2.0.Final/standalone/data/content/fb/79a988aa2767bb2a55248fca8875fc534134ec/content
14:12:09,241 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015876: Starting deployment of "wildfly-helloworld.war" (runtime-name: "wildfly-helloworld.war")
14:12:09,482 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment wildfly-helloworld.war
14:12:09,533 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.1.3.Final
14:12:09,652 INFO  [org.jboss.weld.deployer] (MSC service thread 1-12) JBAS016005: Starting Services for CDI deployment: wildfly-helloworld.war
14:12:09,682 INFO  [org.jboss.weld.Version] (MSC service thread 1-12) WELD-000900: 2.2.6 (Final)
14:12:09,721 INFO  [org.jboss.weld.deployer] (MSC service thread 1-9) JBAS016008: Starting weld service for deployment wildfly-helloworld.war
14:12:10,439 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017534: Registered web context: /wildfly-helloworld
14:12:10,497 INFO  [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "wildfly-helloworld.war" (runtime-name : "wildfly-helloworld.war")
—
Reply to this email directly or view it on GitHub
https://github.com/wildfly/wildfly-maven-plugin/issues/41#issuecomment-105666870
.

Yeah the output would be helpful. The only reason it wouldn't be able to connect is if the management server isn't listening on the port default which defaults to 9990.

This is my output. I don't have any other services running on ports 8080 or 9990:
In case it helps, I'm using Maven 3.2.5 and Java 1.8.0u45
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building WildFly Quickstarts: Helloworld 9.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> wildfly-maven-plugin:1.1.0.Alpha2:run (default-cli) > package @ wildfly-helloworld >>>
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ wildfly-helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /private/tmp/quickstart/helloworld/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ wildfly-helloworld ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ wildfly-helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /private/tmp/quickstart/helloworld/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ wildfly-helloworld ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ wildfly-helloworld ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-war-plugin:2.5:war (default-war) @ wildfly-helloworld ---
[INFO] Packaging webapp
[INFO] Assembling webapp [wildfly-helloworld] in [/private/tmp/quickstart/helloworld/target/wildfly-helloworld]
[INFO] Processing war project
[INFO] Copying webapp resources [/private/tmp/quickstart/helloworld/src/main/webapp]
[INFO] Webapp assembled in [32 msecs]
[INFO] Building war: /private/tmp/quickstart/helloworld/target/wildfly-helloworld.war
[INFO]
[INFO] <<< wildfly-maven-plugin:1.1.0.Alpha2:run (default-cli) < package @ wildfly-helloworld <<<
[INFO]
[INFO] --- wildfly-maven-plugin:1.1.0.Alpha2:run (default-cli) @ wildfly-helloworld ---
[INFO] JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/jre
[INFO] JBOSS_HOME=/private/tmp/quickstart/helloworld/target/wildfly-run/wildfly-8.2.0.Final

[INFO] Server is starting up. Press CTRL + C to stop the server.
May 27, 2015 9:58:22 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.0.Final
May 27, 2015 9:58:22 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.0.Final
May 27, 2015 9:58:22 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.8.Final
09:58:22,797 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
09:58:22,957 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
09:58:23,017 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
09:58:23,801 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
09:58:23,818 INFO  [org.xnio] (MSC service thread 1-4) XNIO version 3.3.0.Final
09:58:23,825 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.3.0.Final
09:58:23,842 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
09:58:23,842 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
09:58:23,846 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
09:58:23,851 INFO  [org.jboss.as.security] (MSC service thread 1-10) JBAS013170: Current PicketBox version=4.0.21.Final
09:58:23,859 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem
09:58:23,867 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]
09:58:23,874 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
09:58:23,889 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017502: Undertow 1.1.0.Final starting
09:58:23,889 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting
09:58:23,891 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
09:58:23,914 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
09:58:23,917 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
09:58:23,923 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = h2
09:58:23,928 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.6.Final
09:58:23,942 INFO  [org.jboss.as.naming] (MSC service thread 1-15) JBAS011802: Starting Naming Service
09:58:23,942 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
09:58:24,006 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path /private/tmp/quickstart/helloworld/target/wildfly-run/wildfly-8.2.0.Final/welcome-content
09:58:24,113 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-11) JBAS017525: Started server default-server.
09:58:24,128 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-16) JBAS017531: Host default-host starting
09:58:24,185 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017519: Undertow HTTP listener default listening on /<IP_ADDRESS>:8080
09:58:24,314 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory /private/tmp/quickstart/helloworld/target/wildfly-run/wildfly-8.2.0.Final/standalone/deployments
09:58:24,363 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
09:58:24,456 INFO  [org.jboss.ws.common.management] (MSC service thread 1-9) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
09:58:24,491 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://<IP_ADDRESS>:9990/management
09:58:24,492 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://<IP_ADDRESS>:9990
09:58:24,492 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 1969ms - Started 184 of 234 services (82 services are lazy, passive or on-demand)
09:59:22,867 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
09:59:22,868 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017532: Host default-host stopping
09:59:22,870 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-13) JBAS010418: Stopped Driver service with driver-name = h2
09:59:22,872 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017521: Undertow HTTP listener default suspending
09:59:22,872 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017520: Undertow HTTP listener default stopped, was bound to /<IP_ADDRESS>:8080
09:59:22,873 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017506: Undertow 1.1.0.Final stopping
09:59:22,883 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015950: WildFly 8.2.0.Final "Tweek" stopped in 16ms
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:03 min
[INFO] Finished at: 2015-05-27T09:59:22+10:00
[INFO] Final Memory: 22M/367M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Alpha2:run (default-cli) on project wildfly-helloworld: The server failed to start: Managed server was not started within [60] s -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

After thinking about it, this was related to some problems I've been having on my Mac. Java applications sometimes fail to connect to localhost (any other app works just fine, including browsers or native apps, and I've checked /etc/hosts, etc... long story and not the right place) but they can connect to <IP_ADDRESS>. WildFly says it's listening on <IP_ADDRESS>, but the maven plugin tries to connect to localhost instead and that is causing the problem.
Added the "right" hostname to the plugin and everything works. Sorry for the noise (although it will be better to make the listening hosts & hostnames the same)

ah, that makes sense. It's not a problem at all.

@Arcnor  What configuration did you setup?

It's likely the Mac is using the ipv6 address for localhost. If wildfly only binds to the ipv4 address (<IP_ADDRESS>), it won't be able to get the incoming localhost requests (which resolve to the ipv6 address).
As a workaround, you should be able to use the <IP_ADDRESS> address as the hostname.


on ubuntu 15.04 service dioesn't start on server reboot

Hello,
I use this role to provision an ubuntu server, if the server restarts docker doesn't start with it.
Is there a way to setup that in this playbook ?
Thank you

Docker should start, at least it did in my experience.  Perhaps something changed.  I'll take a look at this when I have some time.

ok thank you

Any update on this?
I experience the same issue on 14.04
The service is installed but does not start after reboot

I just found a reference for Ubuntu

That reference is for systems with systemd; you're having issues with sysvinit and upstart.  I think it uses a sysvinit script.
I'd take a PR using the systemd and service modules enabling the docker service with an optional variable override.

This is almost 3 years old, I'm closing.  If it's a real issue let's reopen.


Remove unnecessary print()s

Some of the older prints are no longer helpful or necessary. Remove them.

fixed


RTF-2081 OS support update

@kmendiratta-crm could you approve this once we have released the latest install scripts? The current production appliance supports RHEL 8 already right?

@kmendiratta-crm could you approve this once we have released the latest install scripts? The current production appliance supports RHEL 8 already right?

Sure @jeff-1amstudios, I will approve as soon as we release the latest install scripts. Yes, gravity 5.5.49 appliance (which is what we ship currently 1.1.1593137954-fe02b2c - July 9, 2020) supports up to RHEL 8.1

Already added as part of https://github.com/mulesoft/docs-runtime-fabric/pull/283


Upgrade to latest Spring boot

Spring Boot 1.3.0.M2

completed on Master to 1.2.5.RELEASE - will upgrade to 1.3.0 after it goes general release.


Editing of Member Profile Pages

Hey @roryaronson, what was this about? I think this works now - or is this more specific?

Yep this is now a thing :)


⚠ Bofrost.de has degraded performance

In 977ea9c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 929 ms

Resolved: Bofrost.de performance has improved in 7c314c9 after 7 minutes.


Write an error if argument is a directory in Get-FileHash cmdlet

PR Summary
Fix #11110
If Get-FileHash gets a folder as argument we should write non-terminate error.
PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@SteveL-MSFT If the new test uses $error[0]:
        It "Should write non-terminating error if argument is a folder" {
            $result = $pshome, "${pshome}\pwsh.dll" | Get-FileHash
            $result.Count | Should -Be 1
            $error[0].FullyQualifiedErrorId | Should -BeExactly "UnauthorizedAccessError,Microsoft.PowerShell.Commands.GetFileHashCommand"
        }

it unexpectedly fail with an ConciseView error
MethodInvocationException:
Line |
 127 |                                                     $remainingMessage = $remainingMessage.Substring($substring.Length - $prefix.Length).Trim()

     |                                                     ^ Exception calling "Substring" with "1" argument(s): "StartIndex cannot be less than zero. (Parameter 'startIndex')"

I cannot find simple repo steps.

It would be appreciated if this error could be changed from "Access Denied" to something more useful like "SKIPPED: Invalid path: folder" or something.
I'm trying to recurse through my photo archive to try to find duplicates. For each file, I send FullName to get-filehash. I get a LOT of these errors, which implies a permissions issues, but after finding this pull request, I see that it is working as expected.
Error:
Get-FileHash: Access to the path 'E:\PHOTO\Lightroom CC Library\Lightroom CC\684f1da3ca494b3e854964d66fd6f341\originals\2011\2011-12-22' is denied.
Invocation:
Get-ChildItem -Recurse -path E:\PHOTO\ | Select-Object -ExpandProperty FullName | Get-FileHash | Export-Csv -Append h:\photo_hash_list3.csv


Grunt error

Now I am lost!
sails lift
debug: Deprecation warning: Support for sails.config.sockets.onConnect will be removed in an upcoming release. See the v0.11 migration guide for more information and alternate options.
debug: Deprecation warning: sails.config.sockets.onDisconnect is now sails.config.sockets.afterDisconnect
Setting it for you this time, but note that the new afterDisconnect now receives an additional final argument (a callback).
More info: http://sailsjs.org/#/documentation/reference/sails.config/sails.config.sockets.html
debug: Deprecation warning: sails.config.sockets.authorization is now sails.config.sockets.beforeConnect (setting it for you this time)
error:
grunt-cli: The grunt command line interface. (v0.1.13)
Fatal error: Unable to find local grunt.
If you're seeing this message, either a Gruntfile wasn't found or grunt
hasn't been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:
http://gruntjs.com/getting-started

error: Looks like a Grunt error occurred--
error: Please fix it, then restart Sails to continue running tasks (e.g. watching for changes in assets)
error: Or if you're stuck, check out the troubleshooting tips below.
error: Troubleshooting tips:
error:
error:  *-> Are "grunt" and related grunt task modules installed locally?  Run npm install if you're not sure.
error:
error:  *-> You might have a malformed LESS, SASS, CoffeeScript file, etc.
error:
error:  *-> Or maybe you don't have permissions to access the .tmp directory?
error:      e.g., /Users/test/Documents/Jollyrogers/Sails/passport/.tmp ?
error:
error:      If you think this might be the case, try running:
error:      sudo chown -R 501 /Users/test/Documents/Jollyrogers/Sails/passport/.tmp
error: Trying to use unknown adapter, "sails-postgresql", in model passport.
error: Are you sure that adapter is installed in this Sails app?
error: If you wrote a custom adapter with identity="sails-postgresql", it should be in this app's adapters directory.
error: Otherwise, if you're trying to use an adapter named sails-postgresql, please run npm install<EMAIL_ADDRESS>

Running: npm install

I have the same issue.....please somebody help!


bcrypted tokens ?

The server side token could be produced this way ?
So then there is nothing local on the server

What is the use case you have in mind for this?
The local mode might be workable using bcrypt output, but using just a password to derive key material would open up concerns around brute force that might not need to exist using a CSPRNG generated key instead.


feat: Project initialization

Checklist

[ ] I didn't over-scope my PR
[ ] My PR title matches the commit convention
[ ] I did not include breaking changes
[ ] I included unit tests that cover my changes
[ ] I added/updated the documentation about my changes
[ ] I made my own code-review before requesting one

@shiipou Can you see the Docker login error in the actions. I though that it was because the repo was private so it could not use the organization secrets, but it still failing now that it's public...

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on:

GitHub release
v1.0.0-beta.1

Your semantic-release bot :package::rocket:


minor refactorings in naming conventions

Reference Issues/PRs
Minor Enhancements on naming convension
What does this implement/fix? Explain your changes.
Any other comments?

Extremely hard?! weird!

Extremely hard?! weird! @sadrasabouri

Yes.
BTW, you can merge it anytime. I just stopped merging it due to the several opened PRs originating from the same branch. Please merge them cautiously.

Each PR should definitely get reviewed without relying on anything else.
If it's hard, we can have a meeting to clarify the details. Let me know your time availability.

I've sent you a video regarding this PR, I hope it clarifies it well.
Let me know if you have any other questions.
@sadrasabouri

Extremely hard?! weird! @sadrasabouri

Yes. BTW, you can merge it anytime. I just stopped merging it due to the several opened PRs originating from the same branch. Please merge them cautiously.

Don't worry, after you completely finish your review, I will take care of merging.

I accidentally merged it, I opened a revert branch but you can remove that branch and update other PRs with current dev.

Don't worry pal, We good.
@sadrasabouri


chore(579): Reduce info messages in tests

Co-author: @pawellewandowski98

Pull Request Checklist

[x] 📖 I created my PR using provided  : CODE_STANDARDS
[x] 📖 I have read the short Code of Conduct: CODE_OF_CONDUCT
[x] 🏠 I tested my changes locally.
[ ] ✅ I have provided tests for my changes.
[x] 📝 I have used conventional commits.
[ ] 📗 I have updated any related documentation.
[x] 💾 PR was issued based on the Github or Jira issue.

If redis is locally turned off, tests fails. Redis client can be mocked for such cases or this is a desired behavior ?

It's desired. Maybe we should rethink if these tests are still relevant but it's out of scope of this task


Added model results to repo and updated CLI to create consistent folder structure.

This is a suggested change. The goal is to make it easier to add model evaluations along with a dataset (as a kind of test).
This includes a few changes:

the results folder is now added to contain results using the form results/{model_name}/{task_results}
Changes CLI to follow this format

Additionally also adds a model_meta.json with the model_name, time of run and versions during run.

Yep exactly. This also makes it easier for us to review dataset submissions as they then also include at least 1-3 model which have run on the data.

The assumption is to have the results at least for newly submitted datasets.

Makes sense, should this be specified somewhere e.g. in how to contribute? Also maybe it makes sense to explicitly tell people always to run model X so it's a bit easier to compare if it's always the same model? If it's just 1 model, it should probably be a multilingual one 🤔

Also maybe it makes sense to explicitly tell people always to run model X so it's a bit easier to compare if it's always the same model? If it's just 1 model, it should probably be a multilingual one 🤔

Yep I plan to make a PR with how to add datasets that include some standard models (small and multilingual). I was thinking e5-multilingual-small and the sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2.

Great idea ! Both model are multilingual so yes why not. Just keep in mind that for some languages they may not perform very well.. [under-represented ones in datasets]

I suppose this closes #254 - would add it to the PR description, but can't edit 👍

@MartinBernstorff this is #254

Ah yeah, have updated my comment 👍


low battery option

Hi bro,
i was contempling my bar, but i saw there is no "low" option for the battery, there is a full one, as "full_at", or "format-full-background" for example, but neither "low_at" nor "format-low-*".
 Or  is that lemonbuddy that doesn't support that ? (in this case, is that planned ?)
thx, sorry for my franglish :+1:

Hi
There's no config option for it today. I usually use ramp-capacity-N to display the icon in red when it gets low for example.

Oh good idea, i didn't think about that, thx !

@jaagr do you have an example of this ?

Something like this:
[module/battery]
type = internal/battery
full_at = 98

format-discharging = <ramp-capacity> <label-discharging>

ramp-capacity-0 = 
ramp-capacity-0-foreground = #de0037
ramp-capacity-1 = 
ramp-capacity-2 = 

Closing this issue since the given solution should be enough for customizing the output when the battery level is low.

Assuming ramps are dynamic, if I created 6 instances (ramp-capacity0-5) it would split them at every 16.6~%, correct?
Relevancy of that to this issue is adding more ramps to lower the "low battery" threshold with the forground color on the lowest increment (0).

Yeah, that's correct.


build: Enables FreeBSD support

Changed hardcoded bash shebang to env to support multiple directory
structures (required to build on FreeBSD).
Related to: https://github.com/aspnet/Universe/pull/238, aspnet/dnvm#295 & aspnet/dnx#2066.

Hi @jasonwilliams200OK, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

DNVM in this repo is automatically merged from the DNVM repo. This change would be applied to DNVM there and then automatically updated here. DNVM Install on the other hand lives here. Can you remove the change to dnvm.sh on this PR?

@glennc, done. :)

b00ff9a


Add copyright header

@jonmv please review

I assume you scripted this?

I assume you scripted this?

Yes of course  :-)
I did this for all files before. Now I just re-run it occasionally.


Doc update pg repl identity prop descriptions

Edits for PR review along with additional unrelated language and formatting edits to improve clarity and consistency with other documentation.

@roldanbob as mentioned under original Debezium PR, please send it direcly as a PR to Debezium repo, as this is a better and larger change then my PR. Thanks!


Component children not rendered in contentOverlayView on iOS

Current behavior
The component currently has code for inserting react subviews into the contentOverlayView property on the AVPlayerViewController but they will always be destroyed when the _playerViewController is set to nil and recreated by usePlayerViewController.
Reproduction steps
Render a <Video> component with controls={true} and children.
Expected behavior
Children of the <Video> component should be rendered in the contentOverlayView view between the video and the player controls.
Platform
iOS

Also, I was able to modify the RCTVideo.m code locally to keep a reference to the view from insertReactSubview and re-add it every time the AVPlayerViewController is recreated and that fixes the problem.

hi @maxschmeling . that sounds exactly like what i need for my project. I tried the same but I know very little on obj c/swift. Can you guide me a bit?

@bogdan-vol it's on my todo list to get a PR submitted for this with a better implementation, but this is what I did to get it working for now: https://github.com/react-native-community/react-native-video/compare/master...maxschmeling:1418-render-children?expand=1

Thanks a lot @maxschmeling . this works to a point where, for example, I add a TouchableOpacity as a child and in the fullscreen mode it is visible but it loses the onPress functionality. I'll give it a try and see if i can fix this.

@bogdan-vol the children are set as the contentOverlayView on the AVPlayerViewController. Unfortunately, since this layer is between the video and the player controls layer, it is explicitly "untouchable". The user cannot interact with any of the children.


EDSM only accepts 100 events on single call - and we're sending more!

Merged to master, up for next release


Use python3 interpreter in your path instead of hardcoding /bin/python3

On Debian-based systems, python3 is in /usr/bin.
Signed-off-by: dann frazier<EMAIL_ADDRESS>

@encukou can you please advise if the proposed shebang (#!/usr/bin/env python3) is aligned with the python invocation rules in Fedora and RHEL? Thank you.

The proposed #!/usr/bin/env python3 is the best choice here.

In Fedora/RHEL, you'll get the most robust behavior with %{__python3}, a RPM macro. That is the system Python, regardless of the user's $PATH or virtual environment.
In Fedora, the %py3_shebang_fix macro can switch the shebang(s) for you. The macro is not in RHEL yet, so write it out as /usr/bin/pathfix.py -pni %{__python3} FILE...

@encukou thank you for the help!
I've now reviewed the edk2 package's SPEC file in RHEL8, where this python script is primarily meant to be invoked (down-stream), in the Brew build root. I now remember that we've already been careful enough to invoke the script from the edk2 spec file regardless of the shebang -- because this is what we have in RHEL8:
%{__python3} ovmf-vars-generator --verbose --verbose \
...

In Fedora, we have:
python3 qemu-ovmf-secureboot-%{qosb_version}/ovmf-vars-generator \
...

So the edk2 spec file in RHEL8 already uses the best possible approach. And the Fedora one, while it could be improved, is nonetheless independent of the script's own shebang.
Thus, given

your confirmation that the proposed change is the best for upstream, and

our already ensured downstream independence of the upstream shebang,

I'm going to approve this PR (as soon as I can figure out how to do that on this "modern" UI called "github").
Thanks!

@dannf I have zero clue why this PR is stuck in DCO Expected — Waiting for status to be reported state. I don't know what's missing, sorry.

@dannf ... because your commit message does carry your S-o-b.


Zoomed-out when using RTL

Package
filament/filament
Package Version
v2.0.0
Laravel Version
v9.19
Livewire Version
v2.11
PHP Version
PHP 8.2.1
Problem description
When using a RTL language like Arabic the everything appears smaller.
Arabic

English

The Admin panel in Arabic needs to be zoomed in to 133% to look like the Admin panel in English.
Expected behavior
It should look like the English version.
Steps to reproduce
Change the locale in the app.php config file to ar instead of en.
Reproduction repository
https://github.com/Zacktamondo/filamentIssue
Relevant log output
No response

We don't officially support the RTL version, as none of the core team has RTL experience. It has been built by the community. Feel free to PR to fix this but I'd have no clue where to start 👍


Bump python to 3.11 for serving runtime images and Bump poetry to 1.8.3

What this PR does / why we need it:

Bumps Python version to 3.11 for serving runtime images
Bumps Debian from bullseye  (debian 11) to bookworm (debian 12)
Bumps Poetry version to 1.8.3

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Type of changes
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Bump python to 3.11 for serving runtime images and Bump poetry to 1.8.3

Re-running failed tests

/rerun-all - rerun all failed workflows.
/rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

/approve


rc: pull in sysinit and boot as stacked levels when needed

We need start services from sysinit and boot runlevel, even if the new
runlevel is empty.
This fixes problem introduced with commit 7716bf31 (Fix stacked runlevel
support), at which the start_services list are no longer used to start
the services.
This also make sure that all services in sysinit and boot runlevels are
started before switching to next. This was not guaranteed when switching
to a non-empty runlevel.
Fixes issue #54.

Discussion from the IRC channel:
2015-05-15 11:39:48 < dwfreed> I'm not sure we should be automatically pulling in sysinit and boot runlevels
2015-05-15 11:40:13 < dwfreed> in gentoo, they're started by inittab before entering the default runlevel
2015-05-15 11:40:31 < dwfreed> and I think it's better to be explicit than implicit
2015-05-15 11:41:10 < dwfreed> but I'll leave that to WilliamH to decide
2015-05-15 11:42:04 < dwfreed> at the very least, your changes seem sane enough, and it compiles, and I'm sure you tested it, so if he agrees with your change, it can be merged

2015-05-15 11:39:48 < dwfreed> I'm not sure we should be automatically pulling in sysinit and boot runlevels

It behaved like this pre openrc-0.13. The mentioned commit 7716bf3 introduced this new behavior. Commit message does not say anything about desired new behavior. Nor does any documentation (that i could found) mention new behavior since 0.13.
This new (unintentional?) behavior did break things for Alpine Linux. So I consider this a regression.

2015-05-15 11:40:13 < dwfreed> in gentoo, they're started by inittab before entering the default runlevel

So my proposed patch will not hurt Gentoo users.

2015-05-15 11:40:31 < dwfreed> and I think it's better to be explicit than implicit
2015-05-15 11:41:10 < dwfreed> but I'll leave that to WilliamH to decide

If this is the desired behavior, then please document it so I can point Alpine users who upgrade to it if things break.

2015-05-15 11:42:04 < dwfreed> at the very least, your changes seem sane enough, and it compiles, and I'm sure you tested it, so if he agrees with your change, it can be merged

I have tested it and made sure the order is correct (so services in sysinit gets started before boot).
I would be very happy if it got applied, because I am afraid that this issue will case non-obvious breakages due some of the boot services not starting at boot. For example /tmp no longer getting wiped, and hwclock not being set. Those changes can easily go unnoticed.
Thanks

@ncopa:
I'm curious, if you set up your inittab the way the example in support/sysvinit is set up, do you still have issues?
I'm sitting on the fence on this one, so fill me in on what changed for you.

@ncopa:
I  just did a test here as follows:
I made an empty runlevel, then used openrc  to switch to the new runlevel.
The only services that were stopped during the switch were the ones I have in the default runlevel; the services in sysinit and boot were not affected. Can you confirm this behavior?

@nncopa:
I want to appologise for not looking at this. Can you please rebase it on current master so I can take a look now? Thanks much for your understanding.

Having looked into this further, there is a lot of things OpenRC does in sysinit level only when it is explicitly started, such as printing its version, running init.early.sh, running init.sh, handling softlevel from the kernel command line, etc.  Refactoring that code to allow sysinit runlevel to be implicitly started and work correctly is a lot of work, and very little benefit, and not something I'd like to support.

After speaking with @dwfreed, in a nutshell, we are talking about the do_sysinit function along with running /lib*/rc/init.*. This setup is only done when "openrc sysinit" is run. Your p/r does not make sure those things are run, and it would be difficult to refactor the code to do this. If you can do this refactor, please open another pull request and we'll take a look, but the best bet is to use inittab.


React Testing Library Modifications

Modified wiki page for React Testing Library

Added an introduction section (with key principles)
Added Installation and Setup section
Modified the Writing tests with React Testing Library section to be more detailed
Changed header from Example with React Native to Example (User Login)
Added more useful links to the Official documentation section
Added a short Codesandbox Example section with a codesandbox link
Added a short conclusion section

Looks good so far, but I would recommend explaining what each of the links are for in the documentation section or potentially shifting them to fall under relevant headings or sections. Also, you may want to consider adding imports for the example code snippets. I believe that would make the pseudo code more realistic and give the reader more context.

Good point, planning on changing the section heading to React Testing Library Resources, and I'll provide a more in-depth explanation about each of the links. Will also add improts

Just added the changes you suggested. Do u think I should maybe add a few small examples of Querying, User Interaction, and Matchers under the React Testing Library Resources @jchang0112?

Just added a table of contents and some small examples


(PUP-8029) merge 2 messages for translation

Merge 2 messages to make translation better

CLA signed by all contributors.

I agree that "inlined" is going to be a difficult term for translators to understand. Can we add a translator comment to explain the meaning of that term?


Check if skipping the version in Windows app really works.

There a couple of user reports that its not working.

The hourly check in windows should know if "skip" was pressed

wontfix; will start using silent updates instead


Support iTunes File Sharing

Uploading keys using some web server is a fine option, but I think it would be much more secure to use the file sharing mechanism to get the ssh and gpg keys to the device.

Yes, you are right. I am considering to use other ways to share keys. Current solution is to fill in ASCII armor keys. I plan to support import by file sharing services such as DropBox.

I did try to implement this feature, and it seems to be successful. I will make a PR after doing some clean up of the code.


Update supported versions in PROJECT.md

I’ve updated the current supported versions to be on par on what is sated here https://hub.docker.com/_/swift/.
The rules in the file are stated that only 5.1.1, 5.0.3 and 4.2.4 are the truly one supported, but I prefer to be on par with what the docker hub is showing right now.
But I can obviously update the commit to reflect the rules.

Sorry to ask, but I have to do something else to be merged or is only waiting something else?

@shahmishal can you merge?


Print all registered scheme names in exception message for invalid scheme

To help with issues like this https://github.com/aspnet/Security/issues/1219#issuecomment-337314228.
/cc @HaoK @Tratcher

Here: https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Authentication.Core/AuthenticationService.cs


Refactor (ambience): Move ambience from body element to html element

This is no longer needed, since the problem has been addressed in #261 OP:

Note: On desktop safari, in fullscreen on document.documentElement, document.body's background applies to its actual height (leaving the html element's default white background at the bottom of the remainder of the vertical screen estate). The solution is to use height: 100% for both html and body elements.

closing


ga402: remove useless kernel flags

Description of changes
I previously added those flags but it was an error. The acpi.prefer_micosoft_dsm_guide was handled correctly by the kernel when they fixed the fan behaviour and the pcie_aspm.policy shall be handled by scripts or tools like TLP.
Things done

[X] Tested the changes in your own NixOS Configuration
[X] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

@K900

prefer_microsoft_dsm_guid is definitely unnecessary, forcing ASPM maybe we should leave because it's a setting that's known-good on the hardware so it's basically an unconditional improvement.

Ok. I noticed that tlp was changing this parameter depending on the AC state so I thought it would be better to leave it by default.

You should absolutely not run TLP on these machines anyway.

You should absolutely not run TLP on these machines anyway.

Maybe add this to the README along with a reason why?

power-profiles-daemon

Since I am reviewing quite a few nixos hardware PRs, is there a rule of thumb which laptops work well with power-profiles-daemon?

Not really, you just have to check if the firmware exposes support for it.

corrected the flags


Slider Syncing - slider-current disappears if there are no arrows

Hello
Using slider syncing and when all the nav items are visible, the arrows disappears (that's ok) but the slider-current doesn't update in the nav when we change the for list (slide with the mouse on the pink area on the bottom test)
EDIT: this is the fork jsfiddle: http://jsfiddle.net/gyduxa/g4pcn3tq/1/
Thank you

Hey can you clarify what you're trying to do here?
BTW the reason the arrows aren't visible is because the slider is full width and the arrows are positioned to the left and right. If you add something like:
body{padding20px;background:#ebebeb}
you can see them.

Sure, I can clarify.
The arrows are ok.
I've put two examples in the jsfiddle.
The first one is correct, when you change the slides in the top slider, using the arrows or changing by swipe, the "nav" slider updates and the .slider-current goes to the next or prev item.
The second example, when you swipe the top slider, the "nav" slider doesn't update. So, the .slider-current is always in the same item, and it shouldn't.
Thank you

I've made a fix outside the plugin. In case someone needs this fixed, I'll say it here.
$('.gallery.fixslick').on('beforeChange', function(event, slick, currentSlide, nextSlide){
	$('.gallery-nav .slick-slide').removeClass('slick-current');
	$('.gallery-nav .slick-slide:eq('+nextSlide+')').addClass('slick-current');
});


fix: aligns letter-spacing token schemas to "dimension" for consistency

Description
cjk-letter-spacing & detail-letter-spacing should have the same type schema, this aligns them both to "dimension"
Motivation and Context
Token type consistency.
Types of changes

[x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.


Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames:

Got error while calling api through javascript sdk
Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: api.takeout.io. is not in the cert's altnames: DNS:undeveloped.com, DNS:undeveloped.es, DNS:undeveloped.cn, DNS:undeveloped.uk, DNS:undeveloped.eu, DNS:undeveloped.us, DNS:undeveloped.nl, DNS:undeveloped.be, DNS:undeveloped.co.uk, DNS:undeveloped.domains, DNS:dan.com, DNS:www.dan.com, DNS:undeveloped.fr, DNS:undeveloped.nu
takeout.js version: 1.3.1
nodejs version: v20.3.0

I genuinely have no idea how this issue even occurs, or where “api.takeout.io” even comes from.
Takeout is being shutdown on July 1st, in favor of another platform.
Cheers,
Sourfruit

Thanks for the response!
Can you tell me which platform the takeout is being discontinued in favor of?

Absolutely!
While it’s not ‘polished’ yet, it is moving to Contiguity- a more fully featured communications service that uses what I learned from Takeout.
Currently, you’d only be able to sign up for the free tier and use some basic features— the SDKs aren’t done, the CLI is nearly done, Stripe is still in development mode, custom emails aren’t supported yet, etc.
By June 30th, things will be done and released (ProductHunt, etc)


Add support for documenting HTTP endpoints

Bug/issue #, if applicable: rdar://106389558
Summary
Adds support for documenting HTTP parameters, body, and responses in Markdown. Updated ListItemExtractor to pull documentation to HTTPParameters, HTTPBody, and HTTPResponses from markdown content and updated associated section types to merge those docs with data extracted from the symbol graph files.
Dependencies
None.
Testing
Build documentation using HTTP symbol graphs and verify that documentation from documentation extensions is present in their render nodes.
Checklist

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci please test

@swift-ci please test


Use new website for GE

Use selenium to get XLS links from new website. Not sure if this works on github...
Replaces #1460

It seems to be working... :sweat_smile:


sw_engine fill: fixed radial fill focal issue.

This might be a workaround to correct the issue.
The threshold value comes from the mathematical inaccuracy.
@Issue:https://github.com/thorvg/thorvg/issues/1555

@mgrudzinska hello, please have a look and leave any comments if you have a better solution. thanks!


Feature Request : Option to switch between cameras for Image detection as well

Currently only face detection variant have the camera switching feature, I think It's good to have it for Image detection as well.

It's definitely doable.  Curious about what's the use case though?

I can see this as a useful feature. Say for example an AR experience using a tshirt design as a marker?
Seems like a simple one/two liner to implement. I can do a PR when I find the time. 👍

@akhrarovsaid sounds good. Thanks!

I can see this as a useful feature. Say for example an AR experience using a tshirt design as a marker?
Seems like a simple one/two liner to implement. I can do a PR when I find the time. 👍

This feature has implemented?

Implemented in the latest version - ThreeJS version only though


Simple plaintext / status code url

NetBox HealthCheck Plugin version
Latest?
NetBox version
3.0.12
Feature type
Change to existing functionality
Proposed functionality
I was excited to see this project after seeing https://github.com/netbox-community/netbox/issues/8831.  However I was a bit surprised that the health checking view/url is returning a full webpage intended for humans (which seems to not be the intention of the aforementioned  original issue).
I think the human status page is a great addition but for health checking from health systems for things like load balancers a much more simplistic health check should be done.
I propose that an additional /_health (or similar endpoint) be added with a simple text response of OK (with a status code of 200) or NOT OK (with a status code of 500).  Additional statuses could be added if desired for thinks like DEGRADED (however I fail to see where this could be useful).
Simplest implementation is just to return OK as a string and then later enhancements can be added to include DB and REDIS connection stats and even look at counters of failed responses, etc, but I recommend starting easy unless there is something that is easy to implement to give better signal.
Use case
The intention is to be able to return a small payload to determine the health of a system.   Multi-kilobyte payloads (like one in a fully templated page) are not great for automated systems looking for the health of a system.

The longer it takes to return a response the more delayed and less useful the health check is for determining a healthy node.
A lot of these systems store the response and don't scale well when the response is larger (i.e templated HTML)

This is used for the same scenarios listed in  https://github.com/netbox-community/netbox/issues/8831.

Multi-instance netbox deployments behind a load balancer can route away from unhealthy nodes.
During a deployment with k8s or other systems the health check endpoint is used to determine if the deployment was successful or not.  If not they are automatically rolled back.  This means deployments can be automated.

Although the existing "pretty" page at /healthcheck works for this use-case, it will not work for my environment where health check response size is important.
External dependencies
No response

@nemith did you find an answer for this?  I have the same question.


evaluate querySelector extremely slow on one machine for phantomjs 2.1.1

A few weeks ago my local machine suddenly started taking over 3 hours to run all tests, whereas the Jenkins instance took 20 minutes. It seems the problem lies in the querySelector wrapper, which basically does
exports.querySelector = function(query) {
  return casper.page.evaluate(function (query) {
    return document.querySelector(query);
  }, query);
};

(I am using CasperJS, but the problem persists when calling PhantomJS directly via casper.page as done in the above example.)
I put in some profiling code and tested this on several machines. On an Amazon EC2 instance running Ubuntu (same as Jenkins instance), the results are
[profile] querySelector: 17 calls between 0.001 .. 0.969s, avg = 0.878235294117647s; 1 misses @ avg = 0.001s/call; 16 hits @ avg = 0.9330625s
On my local Mac Mini,
[profile] querySelector: 17 calls between 0 .. 22.454s, avg = 16.966s; 2 misses @ avg = 0.0005s/call; 15 hits @ avg = 19.228066666666667s
On my neighbor's Mac Mini,
[profile] querySelector: 17 calls between 0 .. 0.901s, avg = 0.7819411764705881s; 2 misses @ avg = 0.0005s/call; 15 hits @ avg = 0.8861333333333333s
The problem goes away by downgrading to PhantomJS 1.9.2, the only other version I was able to install via HomeBrew.

Well, returning DOM elements is extremely slow and inefficient due to the Qt<->JSC bridge.

I don't see how that is relevant, considering I am seeing the expected performance by downgrading.

Qt<->JSC is a bit complicated. Perhaps something is slowing it down on you local Mac mini. Could you please check that you're running the same versions across all your environments?

Yeah I was running 2.1.1 on my local Mac Mini (19.2s / call), and my neighbor was running 2.1.1 on his Mac Mini (0.9s / call).
This is definitely not the case for all OS X 2.1.1 installations, but I have no idea what is different on my side. Especially since downgrading to 1.9.2 resolved the issue for me.

Thanks. In this case could you please also write a small example script to reproduce your problem?

var webPage = require('webpage');
var page = webPage.create();

function querySelector(selector) {
    var starttime = new Date().getTime();
    var result = page.evaluate(function(sel) {
        return document.querySelector(sel);
    }, selector);
    var endtime = new Date().getTime();
    console.log("took " + ((endtime-starttime)/1000.0) + "s");
    return result;
}

page.open('http://m.bing.com', function(status) {

    var title = querySelector("title");

    console.log(title.textContent);
    phantom.exit();

});

On my local machine (not the Mac mini at work, but at my home), I get a 10x decrease in performance for PJS 2.1.1 over PJS 1.9.2:
$ phantomjs --version
1.9.2
$ phantomjs pjs.js
2016-03-08 00:01:54.020 phantomjs[11580:2994311] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
took 0.141s
Bing
$ phantomjs pjs.js
2016-03-08 00:02:03.524 phantomjs[11591:2994387] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
took 0.118s
Bing
$ phantomjs pjs.js
2016-03-08 00:02:05.544 phantomjs[11596:2994424] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
took 0.122s
Bing
$ brew unlink phantomjs192
Unlinking /usr/local/Cellar/phantomjs192/1.9.2... 1 symlinks removed
$ brew link phantomjs
Linking /usr/local/Cellar/phantomjs/2.1.1... 2 symlinks created
$ phantomjs --version
2.1.1
$ phantomjs pjs.js
took 1.324s
Bing
$ phantomjs pjs.js
took 1.342s
Bing
$ phantomjs pjs.js
took 1.394s
Bing

This is on the machine at work -- same results:
$ phantomjs --version
1.9.2
$ phantomjs pjs.js
took 0.116s
Bing
$ phantomjs pjs.js
took 0.117s
Bing
$ phantomjs pjs.js
took 0.116s
Bing
$ brew unlink phantomjs192
Unlinking /usr/local/Cellar/phantomjs192/1.9.2... 1 symlinks removed
$ brew link phantomjs
Linking /usr/local/Cellar/phantomjs/2.1.1... 2 symlinks created
$ phantomjs --version
2.1.1
$ phantomjs pjs.js
took 1.36s
Bing
$ phantomjs pjs.js
took 1.299s
Bing
$ phantomjs pjs.js
took 1.315s
Bing
$

This degraded performance is a problem with PhantomJS 2.0.0 (binary from https://github.com/Vitallium/phantomjs/releases/tag/2.0.1). Unfortunately I'm unable to build PJS before that one due to OpenSSL so I can't figure out exactly where this problem started occurring.

@kallewoof How did you configure CasperJS to work with an older version of PhantomJS?
I ran your test script on 1.9.8 and recent PhantomJS and saw the same 10X slow down.

Use PHANTOMJS_EXECUTABLE environment variable, pointing it at e.g. /usr/local/bin/phantomjs.

Returning anything other than plain JavaScript object is not really supported. Even if it seems to work, it's a hit and miss, including a potential performance problem.
From the test case:
    var result = page.evaluate(function(sel) {
        return document.querySelector(sel);
    }, selector);

the problematic part is returning a selector (a DOM element).
Try to change it so that you return the actual title, e.g. return document.querySelector(sel).title and check the performance again.

That worked fine, but aren't you concerned over the 10x increase in execution time? (20x for my original scenario, but I haven't found a reliable way to reproduce that yet.)

If the performance degradation is on plain JS object, we would have been very concerned!
Thanks for the report and the detailed investigation! I'm closing it since not much we can follow up here.

Just to clarify for my future self and others:
$("[aria-hidden='true']:contains('some text')"); // SLOW and possibly not supported?
$("[aria-hidden='true']:contains('some text')").text(); // FAST


Improve developer documentation and experience

Cleans up CONTRIBUTING.md to push even more information into the online/rendered documentation
Improves the makefile error provided when the submodules are missing (similar to https://github.com/stan-dev/cmdstan/pull/1217)
Added a makefile target to format all code
Made the .pylintrc in python/ a bit more useful for our project (we still don't enforce this anywhere)

Sorry--I didn't see @roualdes approving this or I wouldn't have added other picky comments (though I would still prefer to see the syntax of what's included in links be a noun).