remove clientLoader refs

End-user friendly description of the problem this fixes or functionality that this introduces

[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below
no changelog

Give a summary of what the PR does, explaining any non-trivial design decisions
These loaders were just being used to get the github token, but appear to cause extra calls to the API

Link of any specific issues this addresses

To run this PR locally, use the following command:
docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:dad3c0c-nikolaik   --name openhands-app-dad3c0c   docker.all-hands.dev/all-hands-ai/openhands:dad3c0c

No longer needed I think


Compilation error

I tried to run steve but I encountered a problem.

It is written that there are files missing in the directory where there are the demonstration videos.
So I manually added fake videos to see if the code compiles and I got this (My fake videos are simply videos that I renamed with the missing file names in the error message ):

The code compiles but I still have a problem.
Even when I drag and drop a video it does not work, could you help me pls?

Ah, thanks for pointing this out. There are two issues at hand:

The first is the build failure. I've pushed an update that resolves this. There were a number of samples that were left out of this published repo (only because they require a lot of space.) I have simply removed their references from the Xcode project.

This is a documentation issue (which I will correct soon.) A quick solution is to simply run these two commands from the project's root folder:

$ cp decks.json ~/.decks.json
$ cp whisper.conf ~/.whisper.conf

I've updated the documentation with further clarification, explaining the cascading loading process of those configuration files. For Steve, the update is here:
https://nettlep.github.io/magic/#gettingupandrunning/meetsteve:thetestbed

@Chtwin  - did you get it working? And if so, were there other issues you needed to work through in order to get it up and running? You're officially the first person to run this besides myself (that I'm aware of) and I want to make sure there aren't further issues/oversights on my part.

@Chtwin - did you get it working? And if so, were there other issues you needed to work through in order to get it up and running? You're officially the first person to run this besides myself (that I'm aware of) and I want to make sure there aren't further issues/oversights on my part.

I pulled and executed the commands and everything works with steve. I plan to use all the features because I was working on exactly the same project for a few days but you have already done almost everything. I ordered the camera for my pi zero and I will use everything. I also plan to add features to the application if you are interested in sharing.
I will also 3D print modules to hide the camera in different objects!
If there is any problem I will make reports. I think there is a problem with CardBars on mac M1 but I'm not sure, I'll let you know if there is a problem.

Note that Cardbars will require the same configuration files setup. So if it wasn’t working before, the work you did to get Steve running should resolve any issues with Cardbars.

I ran carbars without any other modification and it shows me this

This is expected. Select a code from the Codes menu. Use the Image menu to perform operations on that code.
If you have Abra running on a device (with a local server enabled) you can use Abra to scan the code right out of the window.
Also, if you have Steve running and Abra running, you can use Abra to "remote view" the scans from Steve. Just make sure they're on the same network and Abra does not have a local server running.

Thank you very much. I haven't had time to read everything yet but I will read all the docs and test with the camera on the rapsberry pi. I'll let you know if I have any problem

I successfully compile Steve, but there are two issues.

Xcode console log prints out error info.
There is no window shown when I tap Steve app.


[Improvement] Should use the same the decimal places format for currencies display

Is your feature request related to a problem? Please describe.
We should use the same the decimal places format for currencies display
Describe the solution you'd like

Describe alternatives you've considered
Ref PR: https://github.com/CasperDash/casperdash-client/pull/132/files (Extensions is using 4 decimal places)
Additional context
Add any other context or screenshots about the feature request here.

We should handle the decimal place case by case.
e.g if price of CSPR is too low, we need to add more decimal place to the price vice versa with balance


Can an AutoParcelGson class be extended?

In my case, both classes have the @AutoParcelGson annotation. When I attempt to extend an AutoParcelGson class, I get an error:
One AutoParcelGson class may not extend another.
Is there a way to extend a class?

This is a feature not a bug :wink:
If you have common fields, you can put them in an interface that both implementations implement.

Ah yes, of course, thanks!


Always bind invalidHandler, do so anonymously

This pr allows changing of invalidHandler after initialisation, and setting of invalidHandler if initialised without.
Fiddle:
https://jsfiddle.net/YodaDaCoda/fonmoyck/
Note that it's the initial invalidHandler that fires, not the replacement.
Fiddle with this patch:
https://jsfiddle.net/YodaDaCoda/Lugjrgge/
Note that the replacement invalidHandler fires.

Whats your use case that requires this change?

I use the validator as part of a package which is deployed to clients with some default settings (the deployed code can't be changed, only added to). When clients want something that requires a modified invalidHandler, I encounter difficulty as I'm not able to change or remove the default action.

Sorry, but I dont think this change will progress the library into a good direction.

Will close for now. Feel free to ask further questions regarding this topic here. We can re-open if required.


Remap can create unsorted unique labels

Various accessors should be able to detect when they are unsorted and compensate by scanning the entire list.
The header format field can use 1 bit to note this unsorted state.
There should be a function to sort a remapped binary and restore it to efficient functioning.

This is mostly fixed in the python end of things. It could use that condensing function though.

Condensing function was written.


Added a tutorial on how to run "two-mappers" example

This PR adds a README.md to examples/pipelines/two-mappers that can be used as a walk-through guide on how to build a similar pipeline or even to run that pipeline. Also, adds a pipeline_lazy.js that is intended to provide a solution to the proposed challenge in the README.md.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   80.64%   80.64%
=======================================
  Files          36       36
  Lines         806      806
  Branches       99       99
=======================================
  Hits          650      650
  Misses        156      156

Continue to review full report at Codecov.

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


androidenv: fix NDK toolchains

Description of changes
This fixes https://github.com/NixOS/nixpkgs/issues/298285. Wrab executables in toolchains.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3725

LGTM. FYI https://github.com/NixOS/nixpkgs/pull/300407

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3769

I'm a nix newbe on NixOS, trying to get Tuari in the android emulator to work.
Before this PR:
/nix/store/clnxi2n37rwxrp47nnv3ajrfwkrva7ih-androidsdk/libexec/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang: error while loading shared libraries: libc++.so.1: cannot open shared object file: No such file or directory

After this PR - I'm not getting this error anymore :)

Its alternative PR got merged, so I assume the problem is fixed and we don't need this one.


Generate polygons for rings

From @sindizzy on August 15, 2018 0:49
As always thank you so much for a great product!
When we generate ellipses, circles, range rings I would vote for them to be created as a polygon rather than a polyline. Quite often I need to add a fill to the ellipse and as a polyline you can't do that. I believe the reason for this was so all geometry could be saved to one feature class. I think, as a user I would not mind one feature class for polylines and one feature class for polygons. Another reason I think polygons are a good idea is that post-processing like unionization of multiple polygons is possible.
Copied from original issue: Esri/military-tools-desktop-addins#65

Giving the user the ability to choose the geometry output for circles, ellipses, and polygons could be the path forward for this issue. For ease of use each ring would be a single feature. No unionization of features would happen automatically.

That's great.

This is something that will make #438 doable as well

Yes my use case is aviation. We generate what's called Area of Operations circles and other similar features. They essentially show a geoelllipse from a center (an airport or a waypoint) at a specified distance (typically a radius in NM). We then use a fill color to denote where operations are allowed. The fill makes them stand out as opposed to just a perimeter.

@saip is awaiting response about what final implementation would look like for this fix. I think we may need to do better design on this one before we hand it over

@sindizzy your use case is pretty clear. One question for you. In your case is there a requirement to continue to draw rings as polylines? The change we are considering in this case is to switch rings entirely from polyline to polygon instead of offering an option to draw rings as polylines or polygons

For my case I generate range rings only as polygons. This is something that the Military Analyst did before it was sunsetted. In the past we did generate the rings as polylines ONLY because you couldn't label the polygon on the perimeter. The workaround was to generate them as polylines. With Maplex now being part of ArcMap and possibly Pro there is no need for me to create the rings as polylines.

@sindizzy thanks for the response. Good feedback to know you need to be able to label on the perimeter of the polygons. Will keep this in mind as we proceed with design for this

Can we get this in the ArcMap extension as well?


Cloud Apps mattermost-redux feature branch

Summary
This PR is a base for the cloud apps feature branch. It contains:

@larkox's POC Plugin Integrations redux PR
additions for interactive dialogs

Related Pull Requests
https://github.com/mattermost/mattermost-server/pull/15530
https://github.com/mattermost/mattermost-webapp/pull/6490

@mickmister and here


Image struct refactor

This make Construct handle image compression internally as part of parsing and building. Allows a lot of random code from throughout the repo to be gathered in one place.
This needs testing, specifically wrt #9 which it may have either fixed or regressed.

Pull Request Test Coverage Report for Build 502507888

0 of 0   changed or added relevant lines in 0 files are covered.
77 unchanged lines in 7 files lost coverage.
Overall coverage increased (+1.03%) to 70.531%

Files with Coverage Reduction
New Missed Lines
%

ttblit/asset/builder.py
2
96.97%

ttblit/core/struct.py
2
93.55%

ttblit/core/tool.py
3
87.5%

ttblit/tool/packer.py
4
95.92%

ttblit/tool/cmake.py
9
84.93%

ttblit/core/palette.py
14
73.28%

ttblit/tool/metadata.py
43
65.0%

Totals

Change from base Build 477686008:
1.03%

Covered Lines:
876

Relevant Lines:
1242

💛  - Coveralls

Pull Request Test Coverage Report for Build 502507888

0 of 0   changed or added relevant lines in 0 files are covered.
77 unchanged lines in 7 files lost coverage.
Overall coverage increased (+1.03%) to 70.531%

Files with Coverage Reduction
New Missed Lines
%

ttblit/asset/builder.py
2
96.97%

ttblit/core/struct.py
2
93.55%

ttblit/core/tool.py
3
87.5%

ttblit/tool/packer.py
4
95.92%

ttblit/tool/cmake.py
9
84.93%

ttblit/core/palette.py
14
73.28%

ttblit/tool/metadata.py
43
65.0%

Totals

Change from base Build 477686008:
1.03%

Covered Lines:
876

Relevant Lines:
1242

💛  - Coveralls

I think this is about ready. I'm not super happy about adding those classes with only static methods, but it is entirely encapsulated at least. Nothing should ever need to call them outside that file.

I think this is about ready. I'm not super happy about adding those classes with only static methods, but it is entirely encapsulated at least. Nothing should ever need to call them outside that file.

Closing in favour of Click refactor PR, as I found a bug in this one

Closing in favour of Click refactor PR, as I found a bug in this one


Strange calibration of gains only updating the last few in array (in ravel order).

I notice that only last calibration solutions are being updated.

I notice that time_idx=array([-1, -1, -1, ..., -1, -1, -1]) in vis_coords.


Update IdContronller.java

There is no need to define another variable.

Written for the internal code checking tool...


Remove positionCount, from Registry, and add missing Distrust Posi…

…tion Event

Looks good. nit - spelling mistake in your commit.


The AUR package doesn't work

The main.sh specifies relative paths
case $choice in
  1) ./scripts/mirror_optimize.sh
    ;;
  2) ./scripts/cleanup.sh
    ;;
  3) ./scripts/update.sh
    ;;
  4) echo "Exiting..."
    exit 0
    ;;
  *) echo "Invalid option"
    ;;
esac

and in PKGBUILD all scripts are in a different location
  install -Dm755 "$srcdir/$pkgname/main.sh" "$pkgdir/usr/bin/pacsaviour"
  install -Dm755 "$srcdir/$pkgname/scripts/mirror_optimize.sh" "$pkgdir/usr/lib/pacsaviour/mirror_optimize.sh"
  install -Dm755 "$srcdir/$pkgname/scripts/cleanup.sh" "$pkgdir/usr/lib/pacsaviour/cleanup.sh"
  install -Dm755 "$srcdir/$pkgname/scripts/update.sh" "$pkgdir/usr/lib/pacsaviour/update.sh"

Hi @Ved-un
Thank you for reporting the issue! The reason main.sh initially specified relative paths was because it was used during local development and testing.
Fix:
Updated the main.sh script to determine the correct path for the scripts directory:
./scripts when run locally during development or testing from the cloned repository.
/usr/lib/pacsaviour when installed as an AUR package.
if [[ -d "./scripts" ]]; then
    SCRIPT_DIR="./scripts"
else
    SCRIPT_DIR="/usr/lib/pacsaviour"
fi

Also verified that the PKGBUILD installs the scripts into /usr/lib/pacsaviour and the main executable (pacsaviour) into /usr/bin, which aligns with the updated main.sh.   I hope this resolves the issue!


out-file producing weird characters

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
When using out-file with or without specifying any encoding the file has some weird characters at the beginning of the file
 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName
 ------    -----      -----     ------      --  -- -----------
I've tried this on different computers all using ps 7.2.1, windows 10, server 2016 etc. When using the same get-process |out-file with powershell 5.1 it works as expected without those characters.
Expected behavior
NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName

Actual behavior
 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName

Error details
No response
Environment data
7.2.1

Visuals

/cc @SteveL-MSFT

& {
 $PSStyle.OutputRendering = 'Host'    # or PlainText
 Get-Process | Out-File gps.txt
 $PSStyle.OutputRendering  = 'Ansi'
 }

I tried something else
Get-process |write-output > process.txt
It will also add the same characters to the output file as well.
Ted Reichelt
From: vexx32 @.>
Sent: Tuesday, January 11, 2022 7:33 AM
To: PowerShell/PowerShell @.>
Cc: Ted Reichelt @.>; Author @.>
Subject: Re: [PowerShell/PowerShell] out-file producing weird characters (Issue #16730)
/cc @SteveL-MSFThttps://github.com/SteveL-MSFT
—
Reply to this email directly, view it on GitHubhttps://github.com/PowerShell/PowerShell/issues/16730#issuecomment-1010022160, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKMYWOAFFO7734PUS2LA6ITUVQ5TTANCNFSM5LWOETCQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

That produced a clean output in the file
ted
From: 237dmitry @.>
Sent: Tuesday, January 11, 2022 7:48 AM
To: PowerShell/PowerShell @.>
Cc: Ted Reichelt @.>; Author @.>
Subject: Re: [PowerShell/PowerShell] out-file producing weird characters (Issue #16730)
& {
$PSStyle.OutputRendering = 'Host'    # or PlainText
Get-Process | Out-File gps.txt
$PSStyle.OutputRendering  = 'Ansi'
}
—
Reply to this email directly, view it on GitHubhttps://github.com/PowerShell/PowerShell/issues/16730#issuecomment-1010035277, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKMYWOG7P5CEHSYMF7Q5XATUVQ7IVANCNFSM5LWOETCQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

This is a pretty major breaking change. This doesn't happen with other ANSI shells, such as Bash:

This is because ls itself knows when it is being redirected and omits the VT.  PS7.2 handles this at the shell level due to things like formatting which happens within the PS engine.  If you run ls -G > out.txt within PS7.2, you'll still see that VT is omitted because ls decided to omit it.
I think the way to address this issue while addressing https://github.com/PowerShell/Announcements/issues/28 is to change the current regex for removing VT to have a fixed list of known VT codes that will be removed.  This would still need to go through a security review to ensure spoofing doesn't happen.

@SteveL-MSFT this is particularly annoying when $PSStyle is doing full filename coloring and piping the output to clip.exe. It seems like I'm doing that with increasing frequency and pasting into Teams... 😔

Still happening in v7.4.2
Any suggestions other than always using a replace filter before the Out-File ?

You may find some success using ascii as the default encoding for the entire session.
$OutputEncoding = [Text.Encoding]::ASCII
Sorry if this was already tried, it helped with my out-file encoding in pwsh 7

@JasonDTX - I just tried that and it did not alter the output (meaning the output still included escape characters).

@SteveL-MSFT, @PaulHigin - This still happens in 7.2.5 on Windows 11

@JohnMarkHowell Sorry, I pasted an older attempt! Too many tabs open. This one is the one that fixed me.
$PSStyle.OutputRendering = [System.Management.Automation.OutputRendering]::PlainText
Out-File takes the format of the input object, so this strips any escape sequences out of my psobjects.

That is awesome, @JasonDTX ! That fixed it! Thank you!!!!!!!


It should be possible to pin Flutter Projects to a specific Flutter version

Use case
As its part of the Flutter philosophy to allow breaking changes between version to keep the framework improving you immediately get the problem how to ensure that your app is build with a compatible version.
Adding the whole Flutter repository to each project seems sub-optimal.
Proposal
When defining a specific flutter version in pubspec flutter should automatically checkout/download the correct version and build the app.
Ideally in a separate folder so that after the build the latest selected version is active again.

You can use flutterw to achieve this.

@passi I know, but if I understand it correctly it adds the whole Flutter framework as gut submodule to your project.
This should be directly in the tooling by setting a Flutter version in the pubspec and the tooling automatically checks out the correct Flutter version.

A similar PR #26577 was closed with

@Hixie https://github.com/flutter/flutter/pull/26577#issuecomment-456220568: I think it would make sense to make this available to people as an independent package that they can use with Flutter, but I think if we want to make this be part of Flutter itself, the way to do it is to have flutter run notice that the pubspec.yaml has a Flutter SDK constraint in its environment section, and then have it automatically check out the most recent appropriate version based on that, then re-run itself.

Pretty much what you're suggesting. I personally don't like having flutter installed on my system which then automatically changes its version based on the project I'm running it. I keep a flutter copy per project.

I agree with the above comments - this is unlikely to be a feature we would implement in the tool, or one that we would accept as a contribution.


CVE-2021-23814 Unrestricted Upload of File with Dangerous Type

https://github.com/advisories/GHSA-f8x6-m9f5-ffp8
Surprisingly can't find anything about this in the issues here yet, is this something that's gonna be addressed soon?
Thanks a lot!

Yeah, I noticed it before: https://github.com/Roave/SecurityAdvisories/issues/89 but it's not linked to the repo apparently.

v2.5.1 has been released to fix this issue.

I am still able to do this in 2.6

Thanks @deanzod . v2.6.1 has been released to check file extension.


Update nunjuck paths

Closes #923
Done when…

[x] Imports within nunjucks code blocks updated to e.g. {% from "govuk/components/button/macro.njk" import govukButton %}
[x] Examples on https://design-system.service.gov.uk/get-started/production/ updated
[x] Guidance on https://design-system.service.gov.uk/styles/page-template/ updated

You can preview this change here:
Built with commit f46daad5723cb4d82f331d456a1e394ce424441f
https://deploy-preview-974--govuk-design-system-preview.netlify.com


betterlockscreen: 3.0.1 -> 3.1.0

Motivation for this change
Updates to latest version that has some bugfixes.
Changes introduced (diff)
Things done
Note: new version of betterlockscreen uses i3lock-color directly, so the relevant patch was removed.

[x] 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)
[x] 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/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 123457 at d1a2274f run on x86_64-linux 1

2 packages built successfully:

betterlockscreen
tests.trivial

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/misc/screensavers/betterlockscreen/default.nix:19:3:
   |
19 |   installPhase =
   |   ^


Access Denied Errors

Tests affected: Multiple tests in test_users_api.py (e.g., test_create_user_access_denied, test_retrieve_user_access_denied, etc.)
Error type: Access Denied (Permission-related issues)
Potential cause: This could be an issue with how permissions are set up for the user roles in your API. The tests are expecting a certain role or authorization token, but it's not being provided or is being rejected by the API.

These last 3 errors were the most complicated ones for me. In the test_user_api.py there was the error messages above and in order to make the fix I had to login_request_data in conftest.py to send the pytest the right data.


Update trivy command

Codecov Report

Merging #142 (1b35a46) into main (9a3ecbd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #142   +/-   ##
=======================================
  Coverage   88.98%   88.98%
=======================================
  Files          35       35
  Lines         899      899
=======================================
  Hits          800      800
  Misses         52       52
  Partials       47       47

Continue to review full report at Codecov.

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


Find Moldovan border guard website links

https://www.google.com/maps/d/u/0/viewer?mid=1S38hHlp67u7UoFgVGFC-GCU2Efsn6WeC&ll=46.97765775468629%2C28.393133849999998&z=8
there is an option to download as KML, we could then parse that

to get to the above link, visit https://www.border.gov.md/harta-punctelor-de-trecere-ale-frontierei-de-stat and click "view larger map" in the upper right corner of the interactive map

Ukraine-specific info: https://www.border.gov.md/ro/ucraina


PHP 7.x compatiblity

Hi,
is <IP_ADDRESS>/10 compatible with recent PHP 7.1/7.2 versions?
We are currently using the <IP_ADDRESS> version, and when using with PHP 7.1/7.2, a few less files will fail to compile with the following:
ErrorException: count(): Parameter must be an array or an object that implements Countable in lib/less.php/Less.php:9320
Stack trace:
#0 lib/less.php/Less.php(9320): exception_error_handler(2, 'count(): Parame...', 'lib/les...', 9320, Array)
#1 lib/less.php/Less.php(4390): Less_Visitor_toCSS->visitRuleset(Object(Less_Tree_Ruleset), false)
#2 lib/less.php/Less.php(9326): Less_VisitorReplacing->visitObj(Object(Less_Tree_Ruleset))
#3 lib/less.php/Less.php(4390): Less_Visitor_toCSS->visitRuleset(Object(Less_Tree_Ruleset), false)
#4 lib/less.php/Less.php(9326): Less_VisitorReplacing->visitObj(Object(Less_Tree_Ruleset))
#5 lib/less.php/Less.php(4390): Less_Visitor_toCSS->visitRuleset(Object(Less_Tree_Ruleset), false)
#6 lib/less.php/Less.php(4414): Less_VisitorReplacing->visitObj(Object(Less_Tree_Ruleset))
#7 lib/less.php/Less.php(6814): Less_VisitorReplacing->visitArray(Array)
#8 lib/less.php/Less.php(9370): Less_Tree_Ruleset->accept(Object(Less_Visitor_toCSS))
#9 lib/less.php/Less.php(9312): Less_Visitor_toCSS->visitRulesetRoot(Object(Less_Tree_Ruleset))
#10 lib/less.php/Less.php(4390): Less_Visitor_toCSS->visitRuleset(Object(Less_Tree_Ruleset), false)
#11 lib/less.php/Less.php(9228): Less_VisitorReplacing->visitObj(Object(Less_Tree_Ruleset))
#12 lib/less.php/Less.php(286): Less_Visitor_toCSS->run(Object(Less_Tree_Ruleset))
#13 lib/less.php/Less.php(200): Less_Parser->PostVisitors(Object(Less_Tree_Ruleset))
#14 lib/less.php/Cache.php(170): Less_Parser->getCss()
#15 lib/less.php/Cache.php(106): Less_Cache::Cache(Array, Array)
#16 lib/helper.php(70): Less_Cache::Get(Array, Array)
#17 index.php(211): handle_lesscss_request('configs/confere...', '../../configs/c...')
#18 {main}

Running the same with 7.0 works fine.
Thanks,
derchris

As far as I debug this application it is NOT compatible.
Maybe using nightly version? I found it resolves some PHP7 issues.
https://github.com/oyejorge/less.php/commit/669acc51817a8da162b5f1b7137e79f0e4acc636#diff-56cf4fc3cb1ede7b9ea0952085171a02


Stale OSDU schema source

I saw recent activity - I am publishing the OSDU schemas for each milestone. The URL mentioned in the README is a copy.

The resources in that copy are based on local file references instead of schema ids
The resources to register the schemas in the OSDU core Schema service might be better, and reflect the latest version.
OSDU treats "status": "PUBLISHED" as read-only. As a consequence, there are a growing number of higher minor or patch schemas - for the ontology, I would assume only the latest version should be used. Such a list of the latest versions is available in reports, but could be generated as another artefact, easy to consume by the ontology creator.

If you are interested in a collaboration, please submit an issue on the public OSDU GitLab and assign it to me (Thomas Gehrmann [slb] @gehrmann).

I appreciate you telling us about the best resource to use, Thomas. The README indicates that the current version of the ontology is based on the 3rd release of OSDU. On the next version of the ontology, the code will be updated based on the given resource, and the README will refer to the new resource. Upon receiving your approval, I will submit a request for sharing this work on the OSDU GitLab.

Thanks for the feedback - I wonder what 'knowledge' we can inject from the schema generation perspective. I don't think you need my approval, assuming that this work here is under a OSDU compatible license.


How to collect sub-elements from nested vectors?

For example
(sp/transform [ALL (collect-one FIRST) LAST]
              (fn [k _] (k 0))
              {[:a :b] 1 [:c :d] 2})
## {[:a :b] :a, [:c :d] :c}

Is there a way to achieve the same by collecting only the first element of the key? Something like
(sp/transform [ALL (collect-one ????) LAST]
              (fn [k _] k)
              {[:a :b] 1 [:c :d] 2})
## {[:a :b] :a, [:c :d] :c}

Thanks.

collect-one accepts an entire path. Here's how to implement your example:
(transform [ALL (collect-one FIRST FIRST) LAST]
              (fn [k _] k)
              {[:a :b] 1 [:c :d] 2})


Release management

Once we reach Phase 4 in the roadmap, we'll be looking to start including maintenance as an active part of how the containerd project operates.  https://containerd.io/ currently has the following text:

containerd will be released with a 1.0 when feature complete with Linux and Windows parity and this version will be supported for 1 year with security and bug fixes applied and released.
The upgrade path for containerd is that the 0.0.x patch releases are always backward compatible with its major and minor version. Minor (0.x.0) version will always be compatible with the previous minor release. i.e. 1.2.0 is backwards compatible with 1.1.0 and 1.1.0 is compatible with 1.0.0. There is no compatibility guarantees with upgrades from two minor relases. i.e. 1.0.0 to 1.2.0.
There are no backwards compatibility guarantees with upgrades to major versions. i.e 1.0.0 to 2.0.0. Each major version will be supported for 1 year with bug fixes and security patches.

While we don't need to settle on everything yet, it'd be good to discuss and get feedback on what the community needs for a maintained version of containerd as well as how we might organize contributors to manage the work required for maintenance.
Some starter questions:

Is the 1-year term the right length of time?  Docker has announced that they'll be doing 1-year terms for Docker EE and 4-month terms for Docker CE.  Is this too long or too short for other higher-level integrators with containerd?
What do we need to do to maintain backwards compatibility between minor versions?  Are we considering only API structure compatibility or also the semantics of fields passed through those APIs?  Is the API maintained separately from the containerd version like the Docker Remote API version is separate from Docker's version?
Are higher-level integrators expected to depend on a specific version of containerd (like 1.2.3), a specific minor version (1.2.x), or a specific major version (1.x.y)?  What guarantees do higher-level integrators need in order to receive the benefits of a maintained major version without too much overhead?
Are there SLAs or even guidelines that we should create for how long it takes to backport bugfixes/security patches?
Are contributors expected to backport their own bugfixes or are maintainers planning to do this?
How frequently should new patch/minor versions of containerd be released?

We also need to create a checklist of the release project and criteria.  Things like tags should be signed etc...

Most of this was set in https://github.com/containerd/containerd/blob/master/RELEASES.md.
Please open an issue if there are gaps or a policy change is required to meet your needs.


Reuse clamp util

@glennreyes could you pull the latest changes and make a PR again?

Fixed in 6f3413940509ba94d80108af09073ab8e898fa47

Totally missed it, do you still need it?


org.openrewrite.java.security.UseFilesCreateTempDirectory asserts

The org.openrewrite.java.security.UseFilesCreateTempDirectory recipe attempts to remove unnecessary assertions as a cleanup step, but when run on https://github.com/broadinstitute/picard it's not cleaning up asserts here: https://github.com/broadinstitute/picard/blob/master/src/test/java/picard/illumina/CollectIlluminaBasecallingMetricsTest.java#L23
this is because the RemoveUnneededAnnotations visitor only removes junit asserts and these are from testng. The result is
        rootTestDir = Files.createTempDirectory("cibm." + ".tmp").toFile();
        Assert.assertTrue(true);
        Assert.assertTrue(true);

RemoveUnneededAnnotations should probably handle testng asserts as well.

This Github issue should be moved to rewrite-java-security as this is where the mentioned code resides now:
https://github.com/openrewrite/rewrite-java-security/issues/11


Move funding widget below first content block

Trello card
Trello-3451
Context
We want the funding widget to appear below the first block of text on the Scholarships and Bursaries page. The easiest way to do this is to put the content into the funding widget partial, which is only used on this page.
Changes proposed in this pull request

Move funding widget below first content block

Guidance to review

Looks good to me too @gemmadallmandfe. Just trying to figure out how to approve.


Git Commit causes tab change

Every time I do a commit, the current tab is set to the leftmost open tab. Can Git Plus be modified to not change the current tab?  TIA.

Would it be possible to show me a clip of this? Also are there any errors in the dev console?
The package tries to go back to your active tab before the commit message

Hi akonwi,
I'm attaching a clip. Note that there are no console messages - not even an info message.
badtab.zip

Actually, it turns out that there is a console message that appears immediately after I open Atom:
/Users/wolfy/.atom/packages/tree-view-git-branch/lib/main.js:66 Cannot read property 'classList' of null TypeError: Cannot read property 'classList' of null
at getProjectRootEl (/Users/wolfy/.atom/packages/tree-view-git-branch/lib/main.js:65:12)
at /Users/wolfy/.atom/packages/tree-view-git-branch/lib/main.js:54:29
at process._tickCallback (node.js:368:9)(anonymous function) @ /Users/wolfy/.atom/packages/tree-view-git-branch/lib/main.js:66

The error in the console is coming from the tree-view-git-branch package.
That behavior is really odd though. There isn't anything that changes the tab. It simply saves a reference to the current pane. Which version of atom are you using?

Version 1.3.2

It looks to be some sort of conflict with another package: tab-smart-sort - if I disable that package, the tab change does not occur. As to which of the two packages is actually changing the tab, though ... Git-Plus processes all the modified files, but probably shouldn't need to change the tab, and the tab sorter is only supposed to do something when opening a file. I'll report the issue to that package's maintainer too.

Interesting. I don't see anything in that package's code that could conflict with mine. I do notice that it makes a slight change to the prototype of atom's Pane class but it doesn't seem to be at all related to changing the active tab.
I installed that package myself and this 'bug' only happens when the Place Special Tabs On Right setting is set to true.

I tried turning off that setting, and the only difference I see is that the first tab I opened gets selected, not the left-most tab. Weird.

Confirming that this fix seems to the trick. Thank you

Glad to hear it! :+1:


Dependency injection

I wish I could your package as DI, but because of this:
final protected function __construct
...
return new static(

Is not possible.
Do you think there's a way to turn it compatible with CI?

nikolaposa/version provides a Value Object that is meant to be created on demand.
It's a newable class in contrast to a injectable class like a service or repository etc.
The following blog post has a nice explanation: https://qafoo.com/blog/111_injectables_newables.html

💯 what @bcremer said. Version is a value object, just like DateTime for example, it's not a service that you register with your DI container.


Translated up to (but not including) the credits.

Needs to be edited further to fit the available space and to match with the already translated parts.
You can just leave this open until I've proof read everything and fixed the layout issues. I just wanted to get the pull request out early so that the work I did is visible to you and anyone else that might want to chip in.
(I also have some fixes and suggestions for the already translated parts, but I'll create a different pull request for those once I'm done with this one.)

Cool, thanks for helping out!

You can just leave this open until I've proof read everything and fixed the layout issues. I just wanted to get the pull request out early so that the work I did is visible to you and anyone else that might want to chip in.

Ok, I'll do that. I don't expect to be able to do any active translating in the coming week, but I'll make sure to at least proof-read your contributions :-)

(I also have some fixes and suggestions for the already translated parts, but I'll create a different pull request for those once I'm done with this one.)

Separate PR/included here is fine, whatever suits you :-) You may have noticed that I systematically omitted the "ß" -- that's because I'm Swiss and don't know where to put them. If you could fix those issues, that'd be great! Also, feel free to mess with anything I translated. This is the first time I'm translating a text and I'm sure there's lots of space for improvement. Also, I don't really care for having my name up there in the credits; so feel free to replace mine with yours.

I'll try answer to your suggestions  and finish this sometime during the week, thanks for the feedback so far!

@jkoelling I might be able to continue working on this tomorrow... Have you made any progress that is not yet pushed? Just asking so I don't cause conflict and duplicate work.


Both Modal windows after Submit in Private Cloud show the information about the Public Cloud

Describe the bug/ Actual behaviour
Both Modal windows after Submit in Private Cloud show the information about the Public Cloud. - Urgent. Priority: H, Size: S. Assignee: Christopher
Definition of done:
Bug is fixed and software behaves as expected.

I see Private Cloud info in Modal Window 1:

However, I see wrong email in Modal Window 2:

Now second modal window is fixed:

The Public Cloud shows Public Cloud info.

@calbertan Sorry, opening it again. I found that info about Public Cloud is shown on Submit of Edit Request as well.


adding django-dynamic-fixtures

Story / Bug id: not story
Reference person: @riv2q
Description:
Adding django-dynamic-fixtures to requirements
Documentation: http://django-dynamic-fixture.readthedocs.io/en/latest/overview.html
Main features: http://django-dynamic-fixture.readthedocs.io/en/latest/ddf.html
New imports / dependencies:

django-dynamic-fixtures

Any reason to commiting it without usage?

It's relevant to comment on https://github.com/CodeForPoznan/volontulo/pull/497/files

Yeah, cool, good stuff 👍

I guess we could merge it. @magul, any objections? ;-)


bug: missing input for environment type github action

Hi,
first, runme is a really nice young tool. Just want to report a bug when I run it inside vscode for github action.
for one of my github action, I have one input as "environment" type.
workflow_dispatch:
    inputs:
      environment:
        description: 'Environment to run Deployment'
        type: environment
        required: true
        default: stage
      synthetic_test_status:
        description: 'Status of Datadog Synthetic test'
        type: choice
        default: live
        options:
          - live
          - paused
 ...

however, it can't shown in vs code plugin

So seems this is bug in vs code plugin.

Hi @qweasd1! Thanks for reporting this issue. We'll take a look and let you know if we have any questions.

@sourishkrout  thanks! I also test some other input type like "boolean", it can't shown. Seems only "string" input are shown. Not sure whether this is a incomplete feature.

Good to know! We'll check into the non-string types, too.

here is the source code I think https://github.com/stateful/vscode-runme/blob/f5aa15b5e1765a2420110659ee4d1da8b245d773/src/client/components/github/workflowViewer.ts#L175 I think we just don’t include other types and also don’t know why limit choice options to 3

Thanks and nice work! Will check and leave feedback!

work as expected!


GpyOpt_SVM_parameters.py run time and 'set cost function is ignored!'

Hi all,
total beginner here, thank you for providing this code. i've been evaluating a few models I'm building that all begin with GpyOpt_SVM_parameters.py, however that ends up slowing me down because even small data sets (~300-600 entries) take several hours to complete, usually overnight. I have access to a computing cluster, but from what I understand there isn't GPU support for this calculation because of sci-kit learn. Is there anyway to speed up these calculations?
Additionally, I get this "error" everytime, though I do eventually get the desired C and Gamma values out.
warning in stationary: failed to import cython module: falling back to numpy
warning in coregionalize: failed to import cython module: falling back to numpy
warning in choleskies: failed to import cython module: falling back to numpy
regress
The set cost function is ignored! LCB acquisition does not make sense with cost.

feel free to ignore the warning, like you see it is just it, the warning.
as for the computation speed up, that is true, GPyOpt and GPy rely on numpy for all linear algebra operations, so there is no GPU support in there. one obvious approach would be to do parallel computations, if your use case allows it. you can learn more about it here


about usage

Hi, @hehefan ,
Thanks for releasing the package. Would you also release a basic step-by-step guide for the usage of PSTConv? e.g, data preparation, training steps and prediction steps...
Thanks~

Hi @amiltonwong ,

Data preparation. You can follow MeteorNet to generate the MSR-Action3D and Synthia 4D data. Here is my processed MSR-Action3D.  For NTU RGB+D 60/120, please refer to scripts.
Training and prediction. Please run the train-msr.py script.

Best.


it should be possible to pass params to the query

https://github.com/harvesthq/api/blob/master/Sections/Invoices.md
usage example
harvest.Invoices.list({query: '?from=20150101&to=20151231'}, (err, data)=>{})

maybe we can integrate https://github.com/hapijs/qs to support object params
{
   query: {
       from: '20150101',
       to: '20151231'
   }
}

i dug deeper and it's now possible to make requests like:
harvest.Invoices.list({
      from: `${year}0101`,
      to: `${year}1231`,
      status: ['open', 'paid'],
      page: page
    }, cb);

the only thing i couldn't make work is status: ['open', 'paid']
the array get translated by qs (in restler) as status[0]=open&status[1]=paid
while harvest API wants status[]=open&status[]=paid

I see that you opened https://github.com/harvesthq/api/issues/144, but it was promptly closed. That's too bad they don't want to support multiple values. The change is straightforward, but before merging this, will you want to squash your commits to keep the update clean?

actually since api#144 was closed my PR is invalid.
we have to make something like:
var qs = require('qs');
Invoices.prototype.list = function (options, cb) {
     var url = '/invoices';
     if(!_isUndefined(options)){
          url += '?' + qs.stringify(options, {arrayFormat: 'brackets'});
     }
     this.client.get(url, {}, cb);
 };

this makes qs a requirement.
if this doesn't bother you i'll make another PR


[OpenSearch Vector Search] Add Method for approximate_search_query_match_text_with_boolean_filter

Replace this entire comment with:

Description:
I added a function '_approximate_search_query_match_text_with_boolean_filter' at opensearch_vector_search.py.

Issue:
To improve search performance of OpenSearch vector search, it should be possible to compare the similarity with the vector embedding as well as with the text field. I'm developing Chatbot with Langchain based on Opensearch index as a vectorDB now and it helped to improve the search performance.

Dependencies: any dependencies required for this change -> NO,

Tag maintainer: for a quicker response, tag the relevant maintainer (see below),

Twitter handle: we announce bigger features on Twitter.

Please make sure your PR is passing linting and testing before submitting. Run make format, make lint and make test to check this locally.
See contribution guidelines for more information on how to write/run tests, lint, etc:
https://github.com/langchain-ai/langchain/blob/master/.github/CONTRIBUTING.md
If you're adding a new integration, please include:

a test for the integration, preferably unit tests that do not rely on network access,
an example notebook showing its use. It lives in docs/extras directory.

If no one reviews your PR within a few days, please @-mention one of @baskaryan, @eyurtsev, @hwchase17.

@hwchase17
Hi Team,
I'm working on it recently and I need to improve the query to OpenSearch asap, I hope you check the commit soon :)
Thanks,
Minjee Woo (freemjstudio)

cc @naveentatikonda

@baskaryan
I fixed the bug in L625. Could you take a look at it?
Thanks,
Minjee Woo


[Bug]: Result set missing content

ODC version
odc423
OB version

What happened?

What did you expect to happen?

How can we reproduce it (as minimally and precisely as possible)?
View result set
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit d159ed302f3b0dc56ea571c7166e65cf8a72ae94
------
咏和
Sun Dec 10 10:59:51 2023 +0800

pass


Build fails with error[E0658]: let...else statements are unstable when the correct error message should be that rustc 1.65.0 is required

Bevy version
0.9.0
[Optional] Relevant system information
I have rustc 1.64.0 on Ubuntu 20.04. Since I updated the Rust compiler a month or so ago, the first I heard about that no longer being the "latest stable release" was when Bevy failed to build while following the tutorial.
What you did

Create a new project with cargo init
Add a Bevy dependency on 0.9.0 in Cargo.toml
Run cargo run

What went wrong
I got an error from the compiler (error[E0658]: `let...else` statements are unstable) pointing to a usage of that construct in bevy_render_macros-0.9.0/src/as_bind_group.rs.
The Rust compiler is usually quite good at hinting what to do about problems, but in this case it sent me to a closed Github issue.
The real answer is that this feature came out in rustc 1.65.0, which was released since I last updated Rust, is now the latest stable Rust, and is now what Bevy needs, Bevy presumably also having released since then, or at least allowed its dependencies to release and get pulled in.
But since the Rust developers don't personally notify me, @interfect, a hobbyist Rust programmer, every time they make a release, nor do I follow Rust with enough enthusiasm to check every few days to see if there's a new release, I didn't know I didn't have the latest stable Rust, so I tried to install Bevy anyway, and got confused.
(It looks like rustc might make new "stable" releases every month, which seems highly unusual for a language. It might be worth emphasizing that people in general will not already have the latest stable Rust in the Bevy documentation, unless they are actively starting new Rust projects more than once a month.)
Solution proposal
I think that Bevy should use the rust-version field of Cargo.toml to articulate the version of Rust that was the latest stable version at the time of each Bevy release. This would allow Cargo to work out for me that Rust has released an update, instead of attempting to build Bevy with a Rust that everyone but me knows is too old for Bevy to work.
It would also be good to put the latest stable Rust at the time of writing into the tutorial, near the Bevy version that is recommended. It's all well and good to say "the latest stable" Rust, but my Rust has no idea whether it is the latest stable one or not, and it would be very helpful to have the actual version in there for when twenty years form now someone is trying to build an old game that only ever worked with Bevy 0.9.0.
The downside is that bumping these to change the Bevy version would also need to involve bumping them to plug in the then-current latest stable Rust release.

This is an error message from rust. i dont think bevy can do anything here. but when you read the README, you would know that the MSRV is the latest stable.

Yes. But knowing that the latest stable is the MSRV is insufficient to know whether I have the MSRV or not. If I update to Rust 1.65 now, There could be a 1.65.1 release at any moment after that, whereupon I would no longer have the MSRV anymore.
I want the build system to know whether or not I have the MSRV, and to complain at me specifically if I do not. Since I don't think Cargo.toml will let you say rust-version = latest-stable, that might involve some manual version bumping.

I think that setting the MSRV is probably the right call.
To do so, we need to add a CI job that automatically attempts to build Bevy under the MSRV.

Related to:

#288
#4274
#5188


BinsFormer for KITTI

Hello, thank you for open-sourcing BinsFormer.
Are there any model parameters/hyperparameter changes that need to be made on the NYU BinsFormer config to be adapted to the KITTI dataset?
Will logs/models for KITTI dataset be released?

I will release configs for BinsFormer on KITTI soon, and I would like to release all the trained models and logs. Thanks for your attention.

Sorry for the late. I have updated the Binsformer config on KITTI. Close this issue for now.


Run e2e tests against a deployed operator

This change makes a few fixes to allow running E2E tests against a live/deployed operator, and this capability is added through the --live-operator flag.
Notable changes include:

The operator typically runs on gmp-system. Users don't typically deploy resources on the operator namespace, so the tests were updated to put custom resources in a custom namespace and access the operator resources from the operator namespace.
The operator currently has 6 webhooks but the tests create 2. More were dynamically added so they match up when run on a deployed operator.
Minor typos and fixes.

Hey @TheSpiritXIII - just cleaning out old review requests for myself. Is this still relevant? If we want to merge, feel free to rebase and update.
Otherwise, I vote either closing or moving to draft.

Converted to a draft. There is still some value in this change but it's gonna be some effort to rebase.


Rename default branch from master to main

Let's rename default branch to main

If no one objects, we can make this change around the same time we do the next release - which I'm thinking we'll do as soon as @jlovejoy pull requests are tested and merged.

I just renamed the default branch from master to main - be sure to update your local repos!


[Kernel] Catch on type variable doesn't work

The test tests/language/generic_field_mixin4_test.dart seems to treat the type variable in catch as dynamic.
I've attached the compiled file: generic_field_mixin4_test.dart.dill.zip

I'll take a look.


sBTC smart contract wrapper in stacks.js

add a smart contract wrapper (similar to @stacks/stacking), which doesn't really add groundbreaking stacks.js functionality, but makes it easier for users to use the sbtc contract, without know a lot about stacks/stacks.js

Code interface TBD (potentially inspired by StackingClient)

@smcclellan: It would be helpful if you can also update the description with the context and/or other background.

Closing, not needed since these functions are only called by sbtc itself


Update CI workflow to not run tests when only rs comments changed

Overview
This partially addresses https://github.com/roc-lang/roc/issues/6276, in that it adds checks for *.rs changes and, specifically, whether those are comments only or not.
If you find the pattern acceptable, the same logic analogously translates to other file types, including *.roc files, as requested in the corresponding issue.
Rationale and pseudo code
Rationale
The check-changes job still outputs only one result, namely run_tests: ${{ steps.filecheck.outputs.run_tests }}, but the steps are refactored in to work together in a map-reduce kind of a manner. There are individual steps for:

checking whether there are any files we'd like to ignore or not (which is the already existing logic);
checking whether there are any .rs file changes and whether those contain only comments or not;
a "reduce" step which determines what subset of tests (amongst the original subsets, namely none and full) should be run, based on the results from the "map" steps.

Pseudo code
Check for ignored files (the existing logic remains unchanged):

If there exist changes to files whose names don't match the pre-defined pattern (for capturing ignored files),

return an indication that the full set of CI tests may need to be run, based on this check.

Otherwise,

return an indication that no CI tests may need to be run, based on this check.

Check for .rs file changes:

If there have been changes involving filenames other than those which match the pre-defined pattern (for capturing ignored files) and other than .rs files,

return an indication that the full set of CI tests may need to be run, based on this check.

Otherwise, if there have been any changes to any .rs files, check if those changes involve only comments.

If yes,

return an indication that no CI tests may need to be run, based on this check.

Otherwise,

return an indication that no CI tests may need to be run, based on this check.

Otherwise,

return an indication that no CI tests may need to be run, based on this check.

Perform a "reduce" step to determine what subset of tests to run:

If both the "ignore" and the "rs files" step return an indication that the full set of CI tests may need to be run,

then do run the full set of CI tests may need to be run.

Otherwise, do not run any CI tests.

Notes
Please, note the following:

The script ignores changes to *.rs file lines containing only whitespace, i.e., those are treated - in terms of deciding whether to run tests or not - as if they were comment-only lines.
The script is able to handle comments involving multi-line comment symbols, when they are utilised on a single line (e.g., /* This is a comment on a single line. */).

For a more elaborate treatment of multi-line comments, perhaps some sort of static code analysis should be employed instead.

The script intentionally (for the purpose of its own readability as well as not concealing possibly not very meaningful comment lines) doesn't handle lines involving multi-line comment symbols, optionally followed by whitespace and followed by single-line comment symbols, i.e., /* ... */ // comment.

This is a case which one shouldn't expect to see in any codebase, I believe.

Unit tests
These were run firstly locally, as per these instructions on my own fork.
Once the desired results were observed, the unit tests were run as workflow jobs on my own fork. The results are listed in the following table.

Class
Test Case
Expected
Actual
Diff

No files changed
No files changed
none
✅ none
diff

No .rs files changed
A single ignored file
none
✅ none
diff

No .rs files changed
Multiple ignored files
none
✅ none
diff

No .rs files changed
A single non-ignored file
full
✅ full
diff

No .rs files changed
Multiple non-ignored files
full
✅ full
diff

No .rs files changed
One ignored and one non-ignored file
full
✅ full
diff

No .rs files changed
One ignored and multiple non-ignored files
full
✅ full
diff

No .rs files changed
Multiple ignored and one non-ignored file
full
✅ full
diff

No .rs files changed
Multiple ignored and multiple non-ignored files
full
✅ full
diff

.rs files changed, comment vs non-comment changes
A single .rs file with comment changes only
none
✅ none
diff

.rs files changed, comment vs non-comment changes
A single .rs file with non-comment changes only
full
✅ full
diff

.rs files changed, comment vs non-comment changes
Multiple .rs files with comment changes only
none
✅ none
diff

.rs files changed, comment vs non-comment changes
Multiple .rs files with non-comment changes only
full
✅ full
diff

.rs files changed, comment vs non-comment changes
One .rs file with comment changes and one with non-comment changes
full
✅ full
diff

.rs files changed, comment vs non-comment changes
Multiple .rs files with comment changes and one with non-comment changes
full
✅ full
diff

.rs files changed, comment vs non-comment changes
One .rs file with comment changes and multiple with non-comment changes
full
✅ full
diff

.rs files changed, comment vs non-comment changes
Multiple .rs files with comment changes and multiple with non-comment changes
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes
A single .rs file with both comment and non-comment changes
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes
One .rs file with both comment and non-comment changes and one with comment changes
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes
One .rs file with both comment and non-comment changes and multiple with comment changes
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes
One .rs file with both comment and non-comment changes and one with non-comment changes
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes
One .rs file with both comment and non-comment changes and multiple with non-comment changes
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes
Multiple .rs files with both comment and non-comment changes and one with comment changes
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes
Multiple .rs files with both comment and non-comment changes and multiple with comment changes
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes
Multiple .rs files with both comment and non-comment changes and one with non-comment changes
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes
Multiple .rs files with both comment and non-comment changes and multiple with non-comment changes
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored files changed as well
A single .rs file with comment changes only, ignored files changed as well
none
✅ none
diff

.rs files changed, comment vs non-comment changes; ignored files changed as well
A single .rs file with non-comment changes only, ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored files changed as well
Multiple .rs files with comment changes only, ignored files changed as well
none
✅ none
diff

.rs files changed, comment vs non-comment changes; ignored files changed as well
Multiple .rs files with non-comment changes only, ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored files changed as well
One .rs file with comment changes and one with non-comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored files changed as well
Multiple .rs files with comment changes and one with non-comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored files changed as well
One .rs file with comment changes and multiple with non-comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored files changed as well
Multiple .rs files with comment changes and multiple with non-comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored files changed as well
A single .rs file with both comment and non-comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored files changed as well
One .rs file with both comment and non-comment changes and one with comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored files changed as well
One .rs file with both comment and non-comment changes and multiple with comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored files changed as well
One .rs file with both comment and non-comment changes and one with non-comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored files changed as well
One .rs file with both comment and non-comment changes and multiple with non-comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored files changed as well
Multiple .rs files with both comment and non-comment changes and one with comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored files changed as well
Multiple .rs files with both comment and non-comment changes and multiple with comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored files changed as well
Multiple .rs files with both comment and non-comment changes and one with non-comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored files changed as well
Multiple .rs files with both comment and non-comment changes and multiple with non-comment changes, ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; non-ignored files changed as well
A single .rs file with comment changes only, non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; non-ignored files changed as well
A single .rs file with non-comment changes only, non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; non-ignored files changed as well
Multiple .rs files with comment changes only, non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; non-ignored files changed as well
Multiple .rs files with non-comment changes only, non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; non-ignored files changed as well
One .rs file with comment changes and one with non-comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; non-ignored files changed as well
Multiple .rs files with comment changes and one with non-comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; non-ignored files changed as well
One .rs file with comment changes and multiple with non-comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; non-ignored files changed as well
Multiple .rs files with comment changes and multiple with non-comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; non-ignored files changed as well
A single .rs file with both comment and non-comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; non-ignored files changed as well
One .rs file with both comment and non-comment changes and one with comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; non-ignored files changed as well
One .rs file with both comment and non-comment changes and multiple with comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; non-ignored files changed as well
One .rs file with both comment and non-comment changes and one with non-comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; non-ignored files changed as well
One .rs file with both comment and non-comment changes and multiple with non-comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; non-ignored files changed as well
Multiple .rs files with both comment and non-comment changes and one with comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; non-ignored files changed as well
Multiple .rs files with both comment and non-comment changes and multiple with comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; non-ignored files changed as well
Multiple .rs files with both comment and non-comment changes and one with non-comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; non-ignored files changed as well
Multiple .rs files with both comment and non-comment changes and multiple with non-comment changes, non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored and non-ignored files changed as well
A single .rs file with comment changes only, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored and non-ignored files changed as well
A single .rs file with non-comment changes only, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored and non-ignored files changed as well
Multiple .rs files with comment changes only, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored and non-ignored files changed as well
Multiple .rs files with non-comment changes only, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored and non-ignored files changed as well
One .rs file with comment changes and one with non-comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored and non-ignored files changed as well
Multiple .rs files with comment changes and one with non-comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored and non-ignored files changed as well
One .rs file with comment changes and multiple with non-comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, comment vs non-comment changes; ignored and non-ignored files changed as well
Multiple .rs files with comment changes and multiple with non-comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored and non-ignored files changed as well
A single .rs file with both comment and non-comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored and non-ignored files changed as well
One .rs file with both comment and non-comment changes and one with comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored and non-ignored files changed as well
One .rs file with both comment and non-comment changes and multiple with comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored and non-ignored files changed as well
One .rs file with both comment and non-comment changes and one with non-comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored and non-ignored files changed as well
One .rs file with both comment and non-comment changes and multiple with non-comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored and non-ignored files changed as well
Multiple .rs files with both comment and non-comment changes and one with comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored and non-ignored files changed as well
Multiple .rs files with both comment and non-comment changes and multiple with comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored and non-ignored files changed as well
Multiple .rs files with both comment and non-comment changes and one with non-comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

.rs files changed, mixed comment and non-comment changes; ignored and non-ignored files changed as well
Multiple .rs files with both comment and non-comment changes and multiple with non-comment changes, ignored and non-ignored files changed as well
full
✅ full
diff

Can you merge this @rtfeldman?


Does Lightgbm support multi-class inference?

Description
The multi-classification model encounters an error during the inferenceMat lightgbmlib.delete_doubleArray() stage, while binary classification and others can execute normally.

This sounds like a bug in lightgbm. You might want to create an issue in https://github.com/microsoft/LightGBM


pull request for e2e test at 01/29/2017 20:45:10

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


where is your code

I really really really want to reproduce the experimental results of your paper, since your paper has been published for a long time. Could you please update your code one day.

I'm really sorry I forgot to upload the code, it has been updated.


Update for Elixir 1.4

Hi, @tsharju .
Thanks for this useful library, and I updated some code for latest version of Elixir (and Erlang/OTP :) ).

At transcoder.ex, Now Behaviour module  is duplicated, so I replaced @callback annotations for transcoder interface.
See this : https://hexdocs.pm/elixir/Behaviour.html

Updated travis otp version, 17 to 19.

At mix.exs, Updated versions of mix package.

Added () for missing parens warnings of Elixir 1.4, (e.g. packages -> package(), deps -> deps(), self -> self())

@kdxu Thanks for the pull request. I'll check it asap. Sorry for the delay.


Truncate excessive aggregate records

This PR is a part of https://github.com/SpineEventEngine/core-java/pull/1083.
The ability to delete excessive aggregate event records has been implemented for JdbcAggregateStorage.
The Spine version has been updated to 1.0.0-SNAPSHOT.

@armiol PTAL. The build will pass once the PR to core-java is merged.

@armiol PTAL again.


:help lspconfig-server-configurations doesn't actually exist

Description
The help tag lspconfig-server-configurations doesn't actually exist in the documentation
Neovim version
Not relevant
Nvim-lspconfig version
f183d35725264d6184146eebcef1ba8338ddbc83
Operating system and version
Not relevant
Affected language servers
Not relevant
Steps to reproduce

Browse https://github.com/neovim/nvim-lspconfig/tree/master/doc
Try to find lspconfig-server-configurations mentioned in the docs as a help tag

Actual behavior
lspconfig-server-configurations is not listed
Expected behavior
lspconfig-server-configurations is listed in the documentation
Minimal config
Not relevant

LSP log
Not relevant

Yes, it does. Try :help lspconfig-server-configurations. We use some trickery to get it to refer to the txt file.

I did, and it says it's not found. I wouldn't have filed the bug otherwise. Your response is extremely dismissive and discourages me from wanting to help further.

And it wasn't dismissive, because your reproduction steps:

Browse https://github.com/neovim/nvim-lspconfig/tree/master/doc
Try to find lspconfig-server-configurations mentioned in the docs as a help tag

Do not involve :help at all. If you want the raw URL to the file its https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.txt.


Should Ratio of Means take question_no as input?

Should the ratio of means funcntion take question number as an input.
Currently to produce outputs we need to groupby question_no in order to run for each question.
We can either filter results before running the function to only run on specific questions or provice this as an input for functions down the line.
Join manual constructions might need to be updated to take question_no as input to correctly join values.

Think we can just add question as an option in the config. Where does the groupby need to happen? As we might need to edit the function to add that. And are there any other functions we need to check/edit?

I think the only function which will need to be updated will be the join_manual_constructions on the main branch as this has question_no set as a default argument as a temporary work around.
The groupby runs as a Lambda function on the testing_outputs branch L39 in testing_main.py, It will probably need another pull request to make any changes to the testing outputs as these are not in the main package.

@sarahcollyer @shilohd Sorry I replied to this before but forgot to tag you both


Test

Summary
Provide a general description of the code changes in your pull request... were there any bugs you had fixed? If so, mention them. If these bugs have open GitHub issues, be sure to tag them here as well, to keep the conversation linked together.
Other Information
If there's anything else that's important and relevant to your pull request, mention that information here. This could include benchmarks, or other information.
If you are updating any of the CHANGELOG files or are asked to update the CHANGELOG files by reviewers, please add the CHANGELOG entry at the top of the file.
Thanks for contributing!

Codecov Report

Merging #2 (9fbe5f9) into master (00a5f37) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #2   +/-   ##
=======================================
  Coverage   92.29%   92.29%
=======================================
  Files          69       69
  Lines        1025     1025
  Branches      187      187
=======================================
  Hits          946      946
  Misses         75       75
  Partials        4        4

Continue to review full report at Codecov.

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


use Application Insights API-Keys instead of AAD authentication

Currently, a user must be granted 'Reader' RBAC access in order to read application insights data - whether it be through the portal directly or through CLI commands like onefuzz debug logs query'.
With the alternate tenant migration underway, it is necessary to move away from this approach, as most users will not have alternate tenant credentials and can therefore not be granted access (you cannot grant primary tenant creds access to alternate tenant resources).

This is captured in #1428


Is the event field indexedKey supposed to be indexed?

The field from the event appears that it is supposed to be indexed, but it isn't:
https://github.com/ensdomains/resolvers/blob/f0ef9c989195d610773d6c493eda394508a32ba3/contracts/profiles/TextResolver.sol#L8
Also, it appears it was indexed long ago in the past, as seen by this event:
https://etherscan.io/tx/0xf49facd89a265d0bc2a8ea79965b48dd577fbafc2e355905e41492e17656b086#eventlog
I can across then when updating the ENS subgraph - https://github.com/graphprotocol/ens-subgraph/tree/master-backup
Seems like the word indexed might have been removed when upgrading the contract?

Good catch. Looping in @ricmoo, who wrote https://eips.ethereum.org/EIPS/eip-634.
One problem with indexing the keys here is that you can't index variable length types; if you specify string indexed in an event, Solidity hashes it, making it impossible to recover the plaintext.

Oh, that is why it was both indexed and repeated as a non-indexed, so it can be filtered and fetched. Although, wondering now if that is still the best course of action?
I will take a look into this shortly. :)

The tricky part for changing the graph node is that these two events have the exact same signature, but because one string is indexed, the event logs have different data types. And since we are looking for all resolver events on any contracts, both indexed and non-indexed versions can be out there.
A rare occurrence, but nonetheless something we need to support. We will have to look at event signatures, while also checking the ABI for any variable length types that are indexed, and then treat them as bytes32.

@ricmoo In this case I don't think it's the same parameter - the first argument is the namehash, the second is the text field.
@davekaj Good point. If we change the event, then, we should change the name as well.

Here was the original commit, which passes the key in twice after the namehash for both an indexed and non-indexed value:
https://github.com/ricmoo/ens/commit/ee93577fbee59f35aafca16b0667c064f6882792
I'm wondering if in general many of these sorts of things should instead be a Bytes32String instead, since 31 bytes should be enough for most keys? It's non trivial to change now, but would at least result in a different signature.
The indexed looks like it was dropped when the repo was migrated...

@ricmoo I'd rather not hard code in a max string length (and assumption of null-termination) just because ABI encoding is inefficient. :)


Improve opentypes maps for RFC3709, RFC6402, RFC7191, and RFC8226

Automatically update the maps for use with openTypes for RFC3709, RFC6402, RFC7191, and RFC8226 when the module is imported.  Adjust the tests to match.

Codecov Report

Merging #57 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #57      +/-   ##
==========================================
+ Coverage   99.19%   99.19%   +<.01%
==========================================
  Files          56       56
  Lines        4610     4616       +6
==========================================
+ Hits         4573     4579       +6
  Misses         37       37

Impacted Files
Coverage Δ

pyasn1_modules/rfc6402.py
100% <100%> (ø)
:arrow_up:

pyasn1_modules/rfc3709.py
100% <100%> (ø)
:arrow_up:

pyasn1_modules/rfc8226.py
98.03% <100%> (+0.08%)
:arrow_up:

pyasn1_modules/rfc7191.py
97.1% <100%> (+0.08%)
:arrow_up:

Continue to review full report at Codecov.

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

Thank you!


Config file bug. Single item list interpreted as the item itself.

Here is a self contained example to reproduce:
guild.yml
test:
  main: test
  flags-dest: config:test.yaml
  flags-import: all

test.py
import yaml

with open("test.yaml") as f:
    params = yaml.full_load(f)

print(params["a_list"])

test.yaml
a_list:
- single value

or
a_list: [single value]

Guild output
$ guild run test -y
Resolving config:test.yaml dependency
'single value'

Python output
$ python3 test.py
['single value']

The bug here is that these two disagree. When I'm coding I test my scripts withoout guild first. For example I might not know all the parameters to an experiment or what source code is invlolve (all things required to set up a proper guild.yml). But having different behaviour between running it directly and through guild is a code breaking issue.
The only work around I can think of is to add it to a list if the type of the loaded value is not a list. Which essentially ammounts to maintaining two versions of the code. One for guild, one for regular python execution. In my case this should be fine but could be prohibatively expensive to convert code if there are many parameters like this.
Currently on guild version 0.7.2
Update
After investigating other workarounds. Lists all together seem to be broken.
Changing test.yaml to:
a_list:
  - single value
  - second value

And the output is:
$ guild run test -y
Resolving config:test.yaml dependency
'single value' 'second value'
$ python3 test.py
['single value', 'second value']

Guild seems to convert the list to a string space separated with single quotes around each element.

Great report - thanks for the detail! I created a resolution doc here:
https://github.com/guildai/issue-resolution/tree/master/271-config-file-bug-single-item-list-interpreted-as-the-item-itself-
There's unfortunately no good workaround at this time. The above resolution doc proposes using a string to encode a list but that's disruptive to your code, which we want to avoid.
I'll update here with progress.

This is resolved in master and will be available in the next pre-release (0.7.3.rc2). We can keep this issue open until you have a chance to verify. Thanks again!

Great! any idea when rc2 will hit pypi? I can see rc1 is already on there. I'll install from source for now!

Just installed from source (master branch) and I can confirm this is fixed.

Great! This will be available in 0.7.3, which is due out today or tomorrow. Closing but if there's a regression we can reopen. Thanks again!


IrodsPath.parent should be calculated from absolute path

My irods_home is "/nluu12p/home/research-test-christine" and I can instantiate it in three ways.
In [5]: print(IrodsPath(session).parent)
/nluu12p/home/research-test-christine
In [6]: print(IrodsPath(session, "~").parent)
/nluu12p/home/research-test-christine
In [7]: print(IrodsPath(session, session.home).parent)
/nluu12p/home
But only the last one will give me the correct parent.

It's the old pathlib doing it's things again. I guess we're going to move further and further away from copying its behavior..
Will fix after #169 is merged.


Release under an open source license

Currently the repository is released under a CC BY-NC-SA 4.0 License as per LICENSE.md.
This is a very restrictive license that is incompatible with other licenses and is not designed for software.
If the goal is to create an open source software package that researchers can use and improve upon, then I'd recommend an OSI-approved license at https://opensource.org/licenses.
For Python packages, the BSD Licenses are popular. I personally use the BSD-2-Clause Plus Patent License. This license is OSI-approved and rated highly for its simplicity, compatability, and effectiveness.
Happy to answer any license questions.
As a potential user of this package, I am wary to consider it further until it has a license to ensure a sustainable future and open exisitence!

@dhimmel Thanks for bringing this up. We would very much like to create an open-source software package that researchers can use and improve upon. So, I would like to change the license appropriately. Do you have an example LICENSE.md file that I can look at to change our license?

@dhimmel Actually, I think I fixed this (and decided to go with BSD-3-Clause).
Hope this LICENSE works.

Code now released under BSD-3-Clause


PEM doesn't recognise FASTLANE_PASSWORD through Ansible

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
I'm trying to run Fastlane through Ansible. The goal is to have a single source of information regarding my projects and having different playbooks to accomplish different tasks for these projects. One of these tasks is updating push provisioning profiles with Fastlane.
I have a dictionary of projects, which I use with this Ansible Playbook:
# Create all PEMs #
- name: create push profile for all fastlane projects
  shell: "pem --username '{{ item.value.ios_developer }}' \
               --app_identifier '{{ item.key }}' \
               --p12_password '{{ p12_password }}' \
               --output_path '{{ local_push_profiles_folder }}' \
               --verbose"
  connection: local
  with_dict: "{{ fastlane_push_projects }}"
  environment:
    FASTLANE_PASSWORD: "{{ item.value.developer_pass }}"

To validate that Ansible is working properly, I've tried this variation (notice the echo before pem):
# Create all PEMs #
- name: create push profile for all fastlane projects
  shell: "echo $FASTLANE_PASSWORD; pem --username '{{ item.value.ios_developer }}' \
               --app_identifier '{{ item.key }}' \
               --p12_password '{{ p12_password }}' \
               --output_path '{{ local_push_profiles_folder }}' \
               --verbose"
  connection: local
  with_dict: "{{ fastlane_push_projects }}"
  environment:
    FASTLANE_PASSWORD: "{{ item.value.developer_pass }}"

Complete output when running fastlane, including the stack trace and command used
The output of the last playbook is this:
{
  "changed": true,
  "cmd": "echo $FASTLANE_PASSWORD; pem --username '<REDACTED_IOS_DEV_USERNAME>' --app_identifier '<REDACTED_BUNDLE_IDENTIFIER>' --p12_password '<REDACTED_P12_PASSWORD>' --output_path '/certificates/push_profiles' --verbose",
  "delta": "0:00:03.475554",
  "end": "2016-05-31 14:07:24.901470",
  "failed": true,
  "invocation": {
    "module_args": {
      "_raw_params": "echo $FASTLANE_PASSWORD; pem --username '<REDACTED_IOS_DEV_USERNAME>' --app_identifier '<REDACTED_BUNDLE_IDENTIFIER>' --p12_password '<REDACTED_P12_PASSWORD>' --output_path '/certificates/push_profiles' --verbose",
      "_uses_shell": true,
      "chdir": null,
      "creates": null,
      "executable": "/bin/bash",
      "removes": null,
      "warn": true
    },
    "module_name": "command"
  },
  "item": {
    "key": "<REDACTED_BUNDLE_IDENTIFIER>",
    "value": {
      "developer_pass": "<REDACTED_IOS_DEV_PASSWORD>",
      "ios_developer": "<REDACTED_IOS_DEV_USERNAME>",
      "name": "My App - App Store",
      "type": "appstore",
      "ua_key": "<REDACTED_URBAN_AIRSHIP_KEY>"
    }
  },
  "rc": 1,
  "start": "2016-05-31 14:07:21.425916",
  "stderr": "stty: stdin isn't a terminal\nstty: stdin isn't a terminal\nstty: stdin isn't a terminal\n/Library/Ruby/Gems/2.0.0/gems/highline-1.7.8/lib/highline.rb:961:in `get_response': \u001b[31m[!] undefined method `chr' for nil:NilClass\u001b[0m (NoMethodError)\n\tfrom /Library/Ruby/Gems/2.0.0/gems/highline-1.7.8/lib/highline.rb:264:in `ask'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/highline-1.7.8/lib/highline.rb:227:in `agree'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/credentials_manager-0.16.0/lib/credentials_manager/account_manager.rb:39:in `invalid_credentials'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/client.rb:229:in `rescue in login'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/client.rb:224:in `login'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/client.rb:88:in `login'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/portal/spaceship.rb:22:in `login'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/portal/spaceship.rb:77:in `login'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/lib/pem/manager.rb:35:in `login'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/lib/pem/manager.rb:10:in `start'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/bin/pem:33:in `block (2 levels) in run'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.45.0/lib/fastlane_core/ui/fastlane_runner.rb:26:in `run!'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/bin/pem:39:in `run'\n\tfrom /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/bin/pem:45:in `<top (required)>'\n\tfrom /usr/local/bin/pem:23:in `load'\n\tfrom /usr/local/bin/pem:23:in `<main>'",
  "stdout": "<REDACTED_IOS_DEV_PASSWORD>\n\n+------------------+---------------------------------------------+\n|                     \u001b[32mSummary for PEM 1.3.1\u001b[0m                      |\n+------------------+---------------------------------------------+\n| username         | <REDACTED_IOS_DEV_USERNAME>                        |\n| app_identifier   | <REDACTED_BUNDLE_IDENTIFIER>          |\n| p12_password     | <REDACTED_P12_PASSWORD>                                |\n| output_path      | /certificates/push_profiles |\n| development      | false                                       |\n| generate_p12     | true                                        |\n| force            | false                                       |\n| save_private_key | true                                        |\n+------------------+---------------------------------------------+\n\nINFO [2016-05-31 14:07:21.84]: Starting login with user '<REDACTED_IOS_DEV_USERNAME>'\n\u001b[31mThe login credentials for '<REDACTED_IOS_DEV_USERNAME>' seem to be wrong\u001b[0m\nDo you want to re-enter your password? (y/n)",
  "stdout_lines": [
    "<REDACTED_IOS_DEV_PASSWORD>",
    "",
    "+------------------+---------------------------------------------+",
    "|                     \u001b[32mSummary for PEM 1.3.1\u001b[0m   |",
    "+------------------+---------------------------------------------+",
    "| username         | <REDACTED_IOS_DEV_USERNAME>                 |",
    "| app_identifier   | <REDACTED_BUNDLE_IDENTIFIER>                |",
    "| p12_password     | <REDACTED_P12_PASSWORD>                     |",
    "| output_path      | /certificates/push_profiles                 |",
    "| development      | false                                       |",
    "| generate_p12     | true                                        |",
    "| force            | false                                       |",
    "| save_private_key | true                                        |",
    "+------------------+---------------------------------------------+",
    "",
    "INFO [2016-05-31 14:07:21.84]: Starting login with user '<REDACTED_IOS_DEV_USERNAME>'",
    "\u001b[31mThe login credentials for '<REDACTED_IOS_DEV_USERNAME>' seem to be wrong\u001b[0m",
    "Do you want to re-enter your password? (y/n)"
  ],
  "warnings": []
}

The pretty formatted output of stderr is:
  stty: stdin isn't a terminal
  stty: stdin isn't a terminal
  stty: stdin isn't a terminal
  /Library/Ruby/Gems/2.0.0/gems/highline-1.7.8/lib/highline.rb:961:in `get_response': \u001b[31m[!] undefined method `chr' for nil:NilClass\u001b[0m (NoMethodError)
    from /Library/Ruby/Gems/2.0.0/gems/highline-1.7.8/lib/highline.rb:264:in `ask'
    from /Library/Ruby/Gems/2.0.0/gems/highline-1.7.8/lib/highline.rb:227:in `agree'
    from /Library/Ruby/Gems/2.0.0/gems/credentials_manager-0.16.0/lib/credentials_manager/account_manager.rb:39:in `invalid_credentials'
    from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/client.rb:229:in `rescue in login'
    from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/client.rb:224:in `login'
    from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/client.rb:88:in `login'
    from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/portal/spaceship.rb:22:in `login'
    from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.27.1/lib/spaceship/portal/spaceship.rb:77:in `login'
    from /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/lib/pem/manager.rb:35:in `login'
    from /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/lib/pem/manager.rb:10:in `start'
    from /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/bin/pem:33:in `block (2 levels) in run'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
    from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.45.0/lib/fastlane_core/ui/fastlane_runner.rb:26:in `run!'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
    from /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/bin/pem:39:in `run'
    from /Library/Ruby/Gems/2.0.0/gems/pem-1.3.1/bin/pem:45:in `<top (required)>'
    from /usr/local/bin/pem:23:in `load'
    from /usr/local/bin/pem:23:in `<main>'

Issue description (continued)
When I run Fastlane PEM in terminal, without using Ansible, these commands work perfectly:
export FASTLANE_PASSWORD='REDACTED_IOS_DEV_PASSWORD';
pem --username '<REDACTED_IOS_DEV_USERNAME>' --app_identifier '<REDACTED_BUNDLE_IDENTIFIER>' --p12_password '<REDACTED_P12_PASSWORD>' --output_path '/certificates/push_profiles' --verbose

However, when I run the same command through Ansible, my password is not recognised. Using echo I can see the environment I'm working in does have the correct variable and value. It seems that Ruby / Fastlane is not able to get this variable from the environment.
I am aware that I can login once and store my username and password in my OS X keychain, after which PEM wil use the stored credentials. However, this requires me to run my commands directly in terminal each time an account is added or its password changed, which I would like to avoid.
Configuration Files
I used no other configuration files.
Environment
fastlane version (run fastlane -v):
fastlane 1.91.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
no
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
no

This is not something on our radar. I'll keep this open for any upvotes.

I am very, very sorry. This is not a bug in Ansible, Ruby or Fastlane - it is a bug between my ears. I had two different iTunes developer accounts in my config and I switched the passwords.


Problem installing on Debian Wheezy

See https://github.com/sdelements/lets-chat/issues/548 - fails when doing node-gyp rebuild while npm install.

My mistake, problem was a stray old version of node (0.5.3) in /usr/local/bin/node. Removed that and then it worked.


the config get more and more complex

the configuration for webpack get more and more complex in the template projects
it become harder and harder to understand the structure of the configuration
and harder and harder to try to modify it when needed

Please, make sure to read our Contributing Guide. Issues are for bug reports and feature requests only.
We encourage you to ask questions on the forum , Stack Overflow or on gitter and are happy to help you out there. Come back open a new issue if you find out there's a real issue.


Automated reporting matrix testing

Left a question re a file that looks like a duplicate.  Otherwise :+1:, this is a good first step.