single file option for run doesn't work anymore

I tried deploying just a single file (with the -s flag) and the CLI sent the entire bundle.

I'm afraid our existing tests might not have been sufficient for this path :angry:
I'll get this resolved asap.

When I tested this just now, only the single file was sent.
mkdir tessel-init; cd tessel-init;
t2 init;
npm install math-euler;
echo "var Euler = require('math-euler');" > index.js;
t2 run index.js -s;

Result:
INFO Looking for your Tessel...
INFO Connected to bishop.
INFO Building project.
INFO Writing project to RAM on bishop (2.048 kB)...
INFO Deployed.
INFO Running index.js...
module.js:339
    throw err;
    ^

Error: Cannot find module 'math-euler'
    at Function.Module._resolveFilename (module.js:337:15)
    at Function.Module._load (module.js:287:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/tmp/remote-script/index.js:1:69)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:467:10)

Confirmed by ssh to board:
$ ssh<EMAIL_ADDRESS>-i ~/.tessel/id_rsa

BusyBox v1.23.2 (2015-12-16 06:42:04 UTC) built-in shell (ash)

Tessel 2  /  Built on OpenWrt
root@bishop:~# cd /tmp/remote-script/ && ls
index.js

I did discover that -s isn't ignoring .tesselinclude matches.

Also, binary modules are incorrectly included as well. Fix coming.


build time takes too long after update  version 1.4.10 to 1.4.13

Description
build time takes too long after update  version 1.4.10 to 1.4.13
How to reproduce
update version as 1.4.13
What do you expect
on my machine the build with 1.4.10 takes near to 35.645 s and  build with 1.4.13 takes   01:39 min
What happened instead
build time 4 times longer than before
Software:

docker version:

Client: Docker Engine - Community
Version:           18.09.1
API version:       1.39
Go version:        go1.10.6
Git commit:        4c52b90
Built:             Wed Jan  9 19:34:26 2019
OS/Arch:           windows/amd64
Experimental:      false
Server: Docker Engine - Community
Engine:
Version:          18.09.1
API version:      1.39 (minimum version 1.12)
Go version:       go1.10.6
Git commit:       4c52b90
Built:            Wed Jan  9 19:41:49 2019
OS/Arch:          linux/amd64
Experimental:     false

docker-maven-plugin version: 1.4.13
maven version:
pache-maven-3.6.0
Java version: 11.0.1, vendor: Oracle Corporation, runtime:  Java\jdk-11.0.1
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Full backtrace
https://github.com/ibrahimkarayel/message-post
clone project update

<spotify.docker.version>1.4.10</spotify.docker.version>

build project with :  mvn clean install -Pdocker
[build with version: 1.4.13
[INFO] Total time:  01:39 min
[INFO] Finished at: 2019-10-19T11:23:56+02:00

build with version:: 1.4.10
[INFO] Total time:  35.645 s
[INFO] Finished at: 2019-10-19T11:18:42+02:00]

+1

+1
when the console print "[INFO] Image will be built as xxxxx/xxx"
It wastes too much time to step build

+1, seems that the plugin is doing something that takes ~1 minute before actually starting a Docker image build. I tried debugging with -X -e, and nothing is printed to console during this ~1 minute.
This makes the plugin fully unusable, it provides just slowdown and no benefits over simple Docker client execution via Maven exec plugin.

@mcekovic thanks for mentioning the log messages you see, that sounds like a good clue.
Do you see a similar pause if you run echo strangeforest | docker-credential-desktop get at the command line?
You can also run it like time (echo strangeforest | docker-credential-desktop get) to measure the time it takes for the command to run and return.

echo strangeforest | docker-credential-desktop get
credentials not found in native keychain
You probably meant I should execute:
echo https://index.docker.io/v1/ | docker-credential-desktop get
{"ServerURL":"https://index.docker.io/v1/","Username":"mcekovic","Secret":"***"}
The command exits immediately. I tried using image name mcekovic/hello-docker (with my DockerHub username) and behavior of Spotify plugin is the same:
[INFO] Image will be built as mcekovic/hello-docker:spotify
[INFO]
[DEBUG] Executing "docker-credential-desktop get"
Pause of 1 minute is still there and during the pause 4 CPU cores are at 100%.

I came here fromhttps://github.com/spotify/dockerfile-maven/issues/337
This is still an issue with 1.4.13
Downgrade to 1.4.10 + exposing localhost:2735 serves as a workaround.
On my machine, the call
C:\Users\ddroppelt>echo https://index.docker.io/v1/ | docker-credential-wincred get
credentials not found in native keychain

Resolves immeadiatly.

Same problem here, sometimes it take 4 minutos for complete build.

+1

+1

Yes, the issue still exists for 1.4.13.  Take around 5 mins to build an image even the base image does exist on the box.

Same problem
Executing "docker-credential-desktop get" takes too time

I am hoping this is gonna get addressed in 1.4.14 release ;)

I'm facing the same issue and tried to debug the plugin during the maven build. I got to the point where the build process hangs on writing to the output stream at:
com/spotify/docker-client/8.16.0/docker-client-8.16.0-shaded.jar!/com/spotify/docker/client/shaded/org/glassfish/jersey/message/internal/ReaderWriter.class:53
when sending an application/tar request to the npipe://localhost:80/build... endpoint.
This lasts for like 20-30 seconds for a really small docker build context and then the build proceeds.
Hopefully, this will be useful for someone familiar with this plugin internals.

I have the same issue. With 1.4.10 it works fine but not with 1.4.13.

Any news with this one?

Usually I would not go around and promote a different project in a ticket, but since this is the official stance and nothing is happening here:

At this point, we're not developing or accepting new features or even fixing non-critical bugs.

I had followed the issue too, but meanwhile switched to a maven-plugin that still has active development and works similarily (at least for my usecase): "docker-maven-plugin" by frabic8 (https://dmp.fabric8.io)
<properties>
  <!-- fabric8 docker-maven-plugin config : https://dmp.fabric8.io  -->
  <docker.push.registry>your.custom.registry.io</docker.push.registry>
  <docker.verbose>true</docker.verbose><!-- make progress during build visible, sample:"INFO] DOCKER> Step 4/6 : ADD target/${JAR_FILE} /app/app.jar"-->
</properties>

<plugin>
  <groupId>io.fabric8</groupId>
  <artifactId>docker-maven-plugin</artifactId>
  <version>0.38.1</version>
  <configuration>
    <sourceDirectory>${project.basedir}</sourceDirectory>
    <images>
      <image>
        <name>%g/%a:%v</name><!-- default is "%g/%a:%l", g: last element of grouIp, a: artifactId, l: project.version, unless -SNAPSHOT then it is latest. v (unlinke l) has no fallback to latest if *-SNAPSHOT -->
        <build>
          <dockerFile>Dockerfile</dockerFile>
          <args>
            <JAR_FILE>${project.build.finalName}.jar</JAR_FILE>
          </args>
          <!-- when doing multiple snapshot-builds, the cache wont register changes to the contents of a JAR.
          So the jar changes, but the image may be rebuild from cache with the older jar -> snapshot builds are not predictable with cache -->
          <noCache>true</noCache>
        </build>
      </image>
    </images>
  </configuration>
</plugin>

mvn docker:build  builds the image and mvn docker:push pushes it. Here the plugin is not bound to a lifecycle and explicitly called after a mvn package
The plugin can do a bunch of other stuff, but this here replaced what I used the spotify one for

Since we already started to evaluate alternatives, I would also suggest here https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin. I used it in my projects and it worked very well.

One thing to keep in mind with jib: it is dockerfile-less (and no daemon too) and therefore might not be a 1:1 migration (or just not possible) if anything more fancy than "copy my jar into the image" happens. Things such as "apk add " or "add following custom CA to my cacerts" do not work in jib.


pace-progress does not have pace listed as a dependency

When importing pace-progress in Angular, an error is produced because 'pace' cannot be resolved.
Statement
import 'pace-progress';

Error
Module not found: Error: Can't resolve 'pace' in '/home/[directories]/node_modules/pace-progress'

Edit:
The NPM listing points to this repo but it looks as though this is incorrect.

Same problem here. Any solutions?
     Npm install pace-progress

inside node_modules
      pace-progress
           docs
           templates
          ...
          pace.js

Now tried to include in a file
      require('pace-progress/pace.js');

Comes with error
       This dependency was not found:

       * pace in ./node_modules/pace-progress/pace.js


[DNM] it's a test commit, needed to troubleshoot content-provider errors

Depends-On: https://github.com/openstack-k8s-operators/ci-framework/pull/621

recheck
testing ci-framework pr

this PR has served its purpose.


refactor: rename data folder and configuration file

The default configuration file and data folder must be renamed to navcoin.conf and navcoin8 / Navcoin8 respectively.
References in the documentation must be updated.

This is covered by PR #29

This is covered by PR #29

This is going to be re-done with a less invasive PR that changes minimal code to avoid large conflicts with upstream as per discussed with @aguycalled

This is now covered by #37


Drivers Code Cleanup

Goals:

Remove code duplication
remove drivers framework
completely drop IOCTLs https://github.com/PX4/Firmware/issues/8891
base class for each driver type (accel, baro, differential pressure, etc)
support multiple instances of each driver https://github.com/PX4/Firmware/issues/8813

use the Device library to keep track of all instances and deconflict

drivers ModuleBase equivalent https://github.com/PX4/Firmware/issues/9143
port all nuttx drivers to linux and qurt https://github.com/PX4/Firmware/issues/8963, https://github.com/PX4/Firmware/issues/8315
split CDev (system block device) from Device hierarchy https://github.com/PX4/Firmware/pull/8317 (partial step)
run drivers in a work_queue per bus https://github.com/PX4/Firmware/issues/8814
split rc.sensors per board

think about board manifest https://github.com/PX4/Firmware/issues/8812

generalize serial port configuration https://github.com/PX4/Firmware/issues/8302
drivers should apply their own temperature compensation (not the sensors module)
merge DriverFramework (https://github.com/PX4/Firmware/issues/10607)
[please extend list]

There's quite a lot that could be discussed here. For me the worst part is that man of drivers appear to have been developed largely by copy and paste. New drivers are added by duplicating something close, then making a few changes. Huge portions of near boilerplate code and duplicated multiple times. This has resulted in a large sprawling code base that's difficult to maintain and uses significantly more flash than is necessary.
For example here's a relatively simple pull request that changed the way raw/unfiltered IMU was published. https://github.com/PX4/Firmware/pull/8517
Every single accel and gyro driver in the official repo does the same filtering, integration, scaling, publication, etc. This could easily be pushed into a base class (PX4Accel, PX4Gyro) instead of making the same identical change many times.

I agree with the comments above.

@thomasgubler , @dagar , We are working on a basic driver parent class to begin unifying driver construction and are interested in your input.  Recent work on the lis3mdl driver and current work on the batt_smbus and mpu9250 driver represents some of the structure we have implemented, however, there might still be better architectures we haven't identified.  If you have opinions you would like to see implemented please let me know.
-Mark

I'm excited to see interest here. From a code maintenance, platform scalability, and developer sanity standpoint I think abstracting the common pieces of each driver type is long overdue. As a start take a look at the Airspeed class used by all differential pressure sensor drivers. https://github.com/PX4/Firmware/tree/master/src/lib/drivers/airspeed
As much as I love to eliminate code bloat and make things as simple as possible, the most valuable changes we need really are in the sensor pipeline. In terms of system capabilities I view this as an opportunity to implement some of the core improvements that are particularly important for racers and system integrators right now. The most important is splitting the IMU drivers into a high rate publication path to the rate controller (400 Hz - 2 kHz), and a separate delta angle and delta velocity publication (250 Hz) for the EKF. We also need to increase the sampling rate as much as possible (>= 4 kHz) and do all of the filtering PX4 side to help with aliasing and clipping. This will require getting the drivers out of ISRs and enabling SPI DMA.

Notes

Virtually all code used to manage the IMU drivers (start, stop, status, test, calibration) should be the same. Integration and publication should also be something common provided by the base class.
All IOCTL code except for applying calibration and getting the device id could be gutted immediately. Eventually I want to get rid of it entirely (calibration).
the current Ringbuffers aren't needed at all (CDev read)
for the most part nearly all drivers should be independent of the physical interface (I2C or SPI). Other than the unnecessary use of CDev (eg /dev/bmp280_i2c_int) the way this is handled now is actually pretty good. I'd also like to see this extended so that simulation data can enter the driver at this level.
properly hanlde multiple instances of each driver (eg this must stop https://github.com/PX4/Firmware/blob/master/src/drivers/imu/mpu9250/main.cpp#L121-L137)
the split between mpu6000 and mpu9250 likely shouldn't exist, unless we get to a point where the actual specific driver code is so minimal it makes more sense to have separate mpu6000, mpu6500, icm20602, icm20689, mpu9250, etc
calibration (a longer discussion)
split CDev from the Device driver base class (I'll explain separately)
depending on the calibration discussion we may not need CDev at all for drivers. At a minimum we definitely don't need a CDev per driver interface (eg /dev/mpu9250_accel1).
NuttX SPI DMA can only be enabled across all SPI simultaneously are we might be short on DMA channels (especially with interest in DSHOT)
synchronization of IMU. We want a synchronized IMU message for the EKF (easy with most sensors we support), but also have to support synchronizing completely separate accel + gyro.
PX4 side something like a high priority work queue per sensor bus is needed
mechanism for syncing the entire rate pipeline with output (50-400 Hz PWM ESCs, oneshot, dshot, UAVCAN, etc). I want to the entire block (gyro sample -> rate controller -> output) synchronized with effectively all latency and jitter removed.
support data ready interrupts
regardless of the specific usage all drivers should build on all platforms. PX4 I2C and SPI already support the differences across NuttX, Linux, QuRT

Relevant issues/PRs

https://github.com/PX4/Firmware/pull/7446 (in particular https://github.com/PX4/Firmware/pull/7446#issuecomment-354678120)
https://github.com/PX4/Firmware/pull/8731
https://github.com/PX4/Firmware/pull/8317
https://github.com/PX4/Firmware/issues/8813

Distance sensor drivers are progressing, see #11891, #11853, #11859, et. al.

Believe it or not nearly all of this has been done.


feat(Algebra/Homology/Embedding): dualise extend

When e is an embedding of complex shapes, we obtain an isomorphism extendOpIso : K.op.extend e.op ≅ (K.extend e).op.

LGTM, I think the import increase is probably fine. This is not a leaf file, but there is also not a lot depending on it.
maintainer merge?


Remove if False blocks

They are remnants of the first version of the script and could stay inside that script if you want, but not throughout the library modules.

I have addressed this in a pending pull request.


Update overlay code to compile with iced master

Update to make things compile again after this iced change.
I'm unfamiliar with how to create widgets in iced, to be honest I changed things following a bit blindly iced's official widgets changes, so please be skeptical of this PR 😅  The widgets appear to be working correctly and the changes are almost all trivial, but I'm still not 100% sure if it doesn't introduce problems in the modal position for example.

have you run all of the examples to ensure they all run?
also what was the model p[position issues? I already know they are not perfectly centered since the last changes atm just dont know how to go about getting the correct yet.

Yes, the examples work (the grid needs an additional change, the checkbox message is now set on the "on_toggle" function, and there's a panic related to glyphon while setting the horizontal alignment to center or right, but seems unrelated).
I mentioned the modal because the position isn't being explicitly set anymore, so I don't know if this will cause issues.

could you fix the clippy and formating issue. I can then merge it and take over any needed changes to fix any issues.


Fix bottom links on home page

These bottom cards should go to the correct route.

All of these issues can be solved ASAP

what are the routes for 'Buy bitcoin' and 'Inscription' ?

i have changed the routes for 'Event' and 'Register'
if you want i can raise a pull request for that

i have changed the routes for 'Event' and 'Register' if you want i can raise a pull request for that

Ok great.  Yes please

what are the routes for 'Buy bitcoin' and 'Inscription' ?

/about/buybitcoin
/inscriptions
Those should do for now


profile/edit/about

Subject: profile/edit/about
Description:
edited the profile
Results:
missing a way to save the edits (like a save button)
Backend version: develop-7c33e18d
Frontend version:
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/profile/edit/about
User: muin (6968)

it's at the bottom


Build: add MIMA exclusions to by-pass known bug

The build for the versions 5.2.0 has been failing because of a bug in MIMA, described  in https://github.com/lightbend/mima/issues/423.
To avoid falling into that bug, we add exclusion filters.

In my eyes it's not a "bug in MiMa"... It's a bug fix in the compiler that MiMa doesn't have custom logic (i.e. an enhancement, in my eyes).
MiMa's new IncompatibleSignatureProblem-based logic is making an attempt at catching potential issues, but it's not water-tight - in fact, adding exclude[IncompatibleSignatureProblem]("*") can be a reasonable thing to do, to avoid spending time on any noisy false positives.
(Actually... maybe we should change the default behaviour...)


Exception while trying to run Cake.MinVer with minver-cli installed as global tool

I have been using the Cake.MinVer as local tool without problems, but today decided to give a try as a global tool and cannot run it.
What did I do?

make sure there is no version of minver installed at all
install minver as global tool

dotnet tool install --global cake.tool
dotnet tool install --global minver-cli

init a repository

mkdir test
cd test
git init .

add a cake file with the example project in the readme of the repo named build.cake

#addin "nuget:?package=Cake.MinVer&version=0.1.0"

var version = MinVer();

Task("Example")
    .Does(context =>
{
    context.Information($"Version: {version.Version}");
    context.Information($"Major: {version.Major}");
    context.Information($"Minor: {version.Minor}");
    context.Information($"Patch: {version.Patch}");
    context.Information($"PreRelease: {version.PreRelease}");
    context.Information($"BuildMetadata: {version.BuildMetadata}");
});

RunTarget("Example");

create first tag

git add .
git commit -m"test"
git tag 0.1.0

run minver to check all is good

minver

Result
MinVer: Using { Commit: 2d5413e, Tag: '0.1.0', Version: 0.1.0, Height: 0 }.
MinVer: Calculated version 0.1.0.
0.1.0

run cake

dotnet cake

Result:
Could not execute because the specified command or file was not found.
Possible reasons for this include:
  * You misspelled a built-in dotnet command.
  * You intended to execute a .NET program, but dotnet-minver does not exist.
  * You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.
Error: One or more errors occurred. (MinVer: Process returned an error (exit code 1).)
        MinVer: Process returned an error (exit code 1).

change the cake file to be
Task("Example")
    .Does(context =>
{
    context.Information("Hello");
});

RunTarget("Example");

run cake

dotnet cake

Result:
========================================
Example
========================================
Hello

Task                          Duration
--------------------------------------------------
Example                       00:00:00.0136457
--------------------------------------------------
Total:                        00:00:00.0136457

install minver cli as local tool

dotnet new tool-manifest --force
dotnet tool install minver-cli

now revert the file to the version with Cake.MinVer and run cake again
it works

I wonder is this is more a cake issue...

@dario-griffo-cko Thanks for reporting this and for the detailed repro! I see the same error on my end.
I'll investigate this over the weekend and see if there's an easy fix, but at first glance it seems that the issue is on my end. I think I missed the difference between running global tools and local tools and I'm always assuming it's a local tool.
When installing MinVer as a local tool, you can only run it using either dotnet minver or dotnet tool run minver
However, when installing MinVer as a global tool, you can only run it using minver
In Cake.MinVer, I'm running dotnet minver and that's why it fails if MinVer is installed as a global tool.

@dario-griffo-cko I've just released a pre-release package on NuGet that should fix the issue of running MinVer as a global tool. If you have a chance, could you take it for a spin?
I'd also appreciate any feedback on the implementation, if you think there's room for improvement.
#addin "nuget:?package=Cake.MinVer&version=0.2.0-preview&prerelease=true"

var version = MinVer();

Task("Example")
    .Does(context =>
{
    context.Information($"Version: {version.Version}");
    context.Information($"Major: {version.Major}");
    context.Information($"Minor: {version.Minor}");
    context.Information($"Patch: {version.Patch}");
    context.Information($"PreRelease: {version.PreRelease}");
    context.Information($"BuildMetadata: {version.BuildMetadata}");
});

RunTarget("Example");

I'll do some more tests and I'm planning to release an RTM version some time tomorrow.

Implementation
I tried to do what I thought Microsoft was doing for me automatically (but as you found out, they weren't) of using the tool that is closer to the project, i.e.:

If MinVer is installed as a local tool in the repo, use that local tool (closer is better)
If MinVer is not installed as a local tool in the repo, but a global tool is, then use the global tool

It's easy to detect if MinVer is installed as a global tool (or is in the path), but it doesn't seem very easy to detect if MinVer is installed as a local tool - which makes giving priority to the local tool a little challenging.
I considered a few different approaches:

:disappointed: Running dotnet tool list and parsing the result, in an attempt to detect if the local tool is there
:nauseated_face: Running dotnet minver on a try/catch, and if it doesn't work assume local tool is not there, and try minver next
:no_good_man: Parsing the .config\dotnet-tools.json and look for minver-cli in the list of commands (probably a bad idea as I can't guarantee the working directory is the same where the tool manifest is...)
:hiking_boot: Use Cake.DotNetTool.Module to run the dotnet tool instead (also probably a bad idea as it requires manual bootstrapping of the Cake script right now, until Cake v1.0.0 is out...)

Whilst I didn't particularly love any of these approaches, I ended up going with number 2. Number 1 seemed cleaner than all of them at first but, again, because I believe this tool is going to be used as a local tool most of the time, I didn't want to add the overhead of dotnet tool list if it's going to hit the majority of users.
Thus, in a nutshell, I am running dotnet minver first, and if that doesn't work I fallback to running minver and see if that works, before giving up and throwing an error.
I added a couple of more settings to tweak this behavior, so that if you know you're running a global tool in the path, or if you are running a global tool from a specific known location (tool-path), you can tell Cake.MinVer to skip trying to run the local tool, and run the global tool first, and you can also disable the fallback as well:
var settings = new MinVerSettings
{
    // Runs global tool first, fallback to local tool (unless NoFallback = false)
    PreferGlobalTool = true,

    // Disable fallback in case of errors (i.e. only run one of the tools, either local or global. Defaults to false.
    NoFallback = true,
};

var version = MinVer(settings);

or the same thing but with the extension methods:
var version = MinVer(settings => settings
    .WithPreferGlobalTool()
    .WithNoFallback());

I'll update the README after PR #7 is merged and before an RTM version is released:

@dario-griffo-cko FYI stable version v0.2.0 released to nuget.org (release notes).


creating an fsl startup script and an entry point in dockerfile in or…

…der to get environmental variable when running docker without bash, e.g. docker run image python
This solves my problem with running pytest docker run -it -v $PWD:/home myimage_test  pytest.
Without creating the entry point you have to run pytest command from bash like that docker run -it -v $PWD:/home myimage_test bash -c ". /etc/profile.d/fsl.sh; pytest /home/tests_regression/test_spm_realign_regr.py"
Startup scripts might be needed for another packages.

Hi @djarecka - I had a fix for this in mind (#19) which would allow users to add arbitrary Dockerfile instructions. I am hesitant to apply an entrypoint specifically for FSL because it might interfere with other software that is installed.
I will try to implement #19 today.

Hi @djarecka - I implemented this. It's in the arb-instruct branch. The instructions are always added at the end of the Dockerfile (I don't think I'll change that behavior).
Let me know if that doesn't work for you.
Here is a command-line example:
neurodocker -b ubuntu:17.04 -p apt \
    --fsl version=5.0.10 \
    --instruction='RUN echo "Hello, World!"' \
    --instruction='ENTRYPOINT ["entrypoint.sh"]'

returns...
FROM ubuntu:17.04

ARG DEBIAN_FRONTEND=noninteractive

#----------------------------
# Install common dependencies
#----------------------------
RUN apt-get update -qq && apt-get install -yq --no-install-recommends bzip2 ca-certificates curl unzip \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

#------------------
# Install FSL 5.0.10
#------------------
RUN curl -sSL https://fsl.fmrib.ox.ac.uk/fsldownloads/fsl-5.0.10-centos6_64.tar.gz \
    | tar zx -C /opt \
    && cp /opt/fsl/etc/fslconf/fsl.sh /etc/profile.d/ \
    && FSLPYFILE=/opt/fsl/etc/fslconf/fslpython_install.sh \
    && [ -f $FSLPYFILE ] && $FSLPYFILE -f /opt/fsl -q || true
ENV FSLDIR=/opt/fsl \
    PATH=/opt/fsl/bin:$PATH

#--------------------------
# User-defined instructions
#--------------------------

RUN echo "Hello, World!"

ENTRYPOINT ["entrypoint.sh"]

@djarecka - (sorry for all the messages) I fixed the real problem with the FSL installation (changes are now in master). Before the fsl.sh script was being copied to /etc/profile.d, which I thought would be sourced each time the container is run. It turns out that this is not the case, so now the installation sources fsl.sh directly.
Let me know if you are still having issues.

@djarecka - the issue with FSL's environment variables should be fixed now. Neurodocker creates a bash script used as the default entrypoint (/neurodocker/startup.sh), and FSL's bash file is sourced in that entrypoint script. Let me know if you are still running into issues.

Nice!


i18n(zh-cn): Update overrides.md

Description

Update overrides.md
#1923

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
reference/overrides.md
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Align Status in dashboard with designs in application

User Story
As an analyst
I want the statuses on the dashboard to match the colours of what's in the application
so that things are consistent and I have a visual (colour-based) indication of the status.
Acceptance Criteria

[ ] Dashboard pills match colour scheme in #669
[ ] On hold & conditionally approved currently display in the dashboard as "On_hold" & "Conditionally_approved". They shouldn't have the underscore
[ ] Conditionally approved pushes into the other column. It could be wrapped in 2 lines.

Fixed


the question about "coors_inv_last" in 2DPASS/spvnn.py

Thank you for your great work! But I have a small question. In 2DPASS/spvnn.py, I think you use "coors_inv_last" to devoxelization in the line 92, so in 2DPASS/arch_2dpass.py/xModalKD.forward(), should voxelize it with "coors_inv_last" in the line 101?

Thank you for your great work! But I have a small question. In 2DPASS/spvnn.py, I think you use "coors_inv_last" to devoxelization in the line 92, so in 2DPASS/arch_2dpass.py/xModalKD.forward(), should voxelize it with "coors_inv_last" in the line 101?

Hi! Have you try to solve the problem and did the performance improved? I have the same question with you and I modify the code to use coors_inv_last to devoxelization pts_pred_full. The code is shown as follow:
        for idx, scale in enumerate(self.pooling_scale):
            img_feat = data_dict['img_scale{}'.format(idx)]  # img_scale0 correspond to img_scale2 in the original code and so on
            pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat']
            coors_inv = data_dict['scale_{}'.format(scale)]['coors_inv']

            # 3D prediction
            pts_pred_full = self.multihead_3d_classifier[idx](pts_feat)

            # correspondence
            pts_label_full = self.voxelize_labels(data_dict['labels'], data_dict['layer_{}'.format(idx)]['full_coors'])
            pts_feat = self.p2img_mapping(pts_feat[coors_inv], point2img_index, batch_idx)
            pts_pred = self.p2img_mapping(pts_pred_full[coors_inv], point2img_index, batch_idx)

where self.pooling_scale=[1,2,4,8] but finally get a result of 65.288 at mIoU on SemanticKITTI, which is 0.6 lower than original code.

Thank you for your great work! But I have a small question. In 2DPASS/spvnn.py, I think you use "coors_inv_last" to devoxelization in the line 92, so in 2DPASS/arch_2dpass.py/xModalKD.forward(), should voxelize it with "coors_inv_last" in the line 101?

Hi! Have you try to solve the problem and did the performance improved? I have the same question with you and I modify the code to use coors_inv_last to devoxelization pts_pred_full. The code is shown as follow:
        for idx, scale in enumerate(self.pooling_scale):
            img_feat = data_dict['img_scale{}'.format(idx)]  # img_scale0 correspond to img_scale2 in the original code and so on
            pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat']
            coors_inv = data_dict['scale_{}'.format(scale)]['coors_inv']

            # 3D prediction
            pts_pred_full = self.multihead_3d_classifier[idx](pts_feat)

            # correspondence
            pts_label_full = self.voxelize_labels(data_dict['labels'], data_dict['layer_{}'.format(idx)]['full_coors'])
            pts_feat = self.p2img_mapping(pts_feat[coors_inv], point2img_index, batch_idx)
            pts_pred = self.p2img_mapping(pts_pred_full[coors_inv], point2img_index, batch_idx)

where self.pooling_scale=[1,2,4,8] but finally get a result of 65.288 at mIoU on SemanticKITTI, which is 0.6 lower than original code.

I made a similar change to you, and it didn't improve

Thank you for your great work! But I have a small question. In 2DPASS/spvnn.py, I think you use "coors_inv_last" to devoxelization in the line 92, so in 2DPASS/arch_2dpass.py/xModalKD.forward(), should voxelize it with "coors_inv_last" in the line 101?

Hi! Have you try to solve the problem and did the performance improved? I have the same question with you and I modify the code to use coors_inv_last to devoxelization pts_pred_full. The code is shown as follow:
        for idx, scale in enumerate(self.pooling_scale):
            img_feat = data_dict['img_scale{}'.format(idx)]  # img_scale0 correspond to img_scale2 in the original code and so on
            pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat']
            coors_inv = data_dict['scale_{}'.format(scale)]['coors_inv']

            # 3D prediction
            pts_pred_full = self.multihead_3d_classifier[idx](pts_feat)

            # correspondence
            pts_label_full = self.voxelize_labels(data_dict['labels'], data_dict['layer_{}'.format(idx)]['full_coors'])
            pts_feat = self.p2img_mapping(pts_feat[coors_inv], point2img_index, batch_idx)
            pts_pred = self.p2img_mapping(pts_pred_full[coors_inv], point2img_index, batch_idx)

where self.pooling_scale=[1,2,4,8] but finally get a result of 65.288 at mIoU on SemanticKITTI, which is 0.6 lower than original code.

I made a similar change to you, and it didn't improve too._
for idx, scale in enumerate(self.scale_list):
img_feat = data_dict['img_scale{}'.format(scale)]
pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat']
scale_last = self.scale_list[idx-1] if idx != 0 else 1
coors_inv = data_dict['scale_{}'.format(scale_last)]['coors_inv']

Thank you for your great work! But I have a small question. In 2DPASS/spvnn.py, I think you use "coors_inv_last" to devoxelization in the line 92, so in 2DPASS/arch_2dpass.py/xModalKD.forward(), should voxelize it with "coors_inv_last" in the line 101?

Hi! Have you try to solve the problem and did the performance improved? I have the same question with you and I modify the code to use coors_inv_last to devoxelization pts_pred_full. The code is shown as follow:
        for idx, scale in enumerate(self.pooling_scale):
            img_feat = data_dict['img_scale{}'.format(idx)]  # img_scale0 correspond to img_scale2 in the original code and so on
            pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat']
            coors_inv = data_dict['scale_{}'.format(scale)]['coors_inv']

            # 3D prediction
            pts_pred_full = self.multihead_3d_classifier[idx](pts_feat)

            # correspondence
            pts_label_full = self.voxelize_labels(data_dict['labels'], data_dict['layer_{}'.format(idx)]['full_coors'])
            pts_feat = self.p2img_mapping(pts_feat[coors_inv], point2img_index, batch_idx)
            pts_pred = self.p2img_mapping(pts_pred_full[coors_inv], point2img_index, batch_idx)

where self.pooling_scale=[1,2,4,8] but finally get a result of 65.288 at mIoU on SemanticKITTI, which is 0.6 lower than original code.
I made a similar change to you, and it didn't improve too._
for idx, scale in enumerate(self.scale_list):     img_feat = data_dict['img_scale{}'.format(scale)]     pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat']     scale_last = self.scale_list[idx-1] if idx != 0 else 1     coors_inv = data_dict['scale_{}'.format(scale_last)]['coors_inv']

Thank you for your great work! But I have a small question. In 2DPASS/spvnn.py, I think you use "coors_inv_last" to devoxelization in the line 92, so in 2DPASS/arch_2dpass.py/xModalKD.forward(), should voxelize it with "coors_inv_last" in the line 101?

Hi! Have you try to solve the problem and did the performance improved? I have the same question with you and I modify the code to use coors_inv_last to devoxelization pts_pred_full. The code is shown as follow:
        for idx, scale in enumerate(self.pooling_scale):
            img_feat = data_dict['img_scale{}'.format(idx)]  # img_scale0 correspond to img_scale2 in the original code and so on
            pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat']
            coors_inv = data_dict['scale_{}'.format(scale)]['coors_inv']

            # 3D prediction
            pts_pred_full = self.multihead_3d_classifier[idx](pts_feat)

            # correspondence
            pts_label_full = self.voxelize_labels(data_dict['labels'], data_dict['layer_{}'.format(idx)]['full_coors'])
            pts_feat = self.p2img_mapping(pts_feat[coors_inv], point2img_index, batch_idx)
            pts_pred = self.p2img_mapping(pts_pred_full[coors_inv], point2img_index, batch_idx)

where self.pooling_scale=[1,2,4,8] but finally get a result of 65.288 at mIoU on SemanticKITTI, which is 0.6 lower than original code.

I made a similar change to you, and it didn't improve too.
for idx, scale in enumerate(self.scale_list):
img_feat = data_dict['img_scale{}'.format(scale)]
pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat']
scale_last = self.scale_list[idx-1] if idx != 0 else 1
coors_inv = data_dict['scale_{}'.format(scale_last)]['coors_inv']

Thank you for your great work! But I have a small question. In 2DPASS/spvnn.py, I think you use "coors_inv_last" to devoxelization in the line 92, so in 2DPASS/arch_2dpass.py/xModalKD.forward(), should voxelize it with "coors_inv_last" in the line 101?

Hi! Have you try to solve the problem and did the performance improved? I have the same question with you and I modify the code to use coors_inv_last to devoxelization pts_pred_full. The code is shown as follow:
        for idx, scale in enumerate(self.pooling_scale):
            img_feat = data_dict['img_scale{}'.format(idx)]  # img_scale0 correspond to img_scale2 in the original code and so on
            pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat']
            coors_inv = data_dict['scale_{}'.format(scale)]['coors_inv']

            # 3D prediction
            pts_pred_full = self.multihead_3d_classifier[idx](pts_feat)

            # correspondence
            pts_label_full = self.voxelize_labels(data_dict['labels'], data_dict['layer_{}'.format(idx)]['full_coors'])
            pts_feat = self.p2img_mapping(pts_feat[coors_inv], point2img_index, batch_idx)
            pts_pred = self.p2img_mapping(pts_pred_full[coors_inv], point2img_index, batch_idx)

where self.pooling_scale=[1,2,4,8] but finally get a result of 65.288 at mIoU on SemanticKITTI, which is 0.6 lower than original code.

I made a similar change to you, and it didn't improve too. for idx, scale in enumerate(self.scale_list): img_feat = data_dict['img_scale{}'.format(scale)] pts_feat = data_dict['layer_{}'.format(idx)]['pts_feat'] scale_last = self.scale_list[idx-1] if idx != 0 else 1 coors_inv = data_dict['scale_{}'.format(scale_last)]['coors_inv']

Thanks for your reply! It's somewhat strange.

Hi! I also found this problem. But I think it is not enough to just change here. Another place should also be changed.
"network/spvcnn.py" in the line 126, should be changed to
self.strides = [int(scale) for scale in self.scale_list]

Hi! I also found this problem. But I think it is not enough to just change here. Another place should also be changed. "network/spvcnn.py" in the line 126, should be changed to self.strides = [int(scale) for scale in self.scale_list]

I think you are right. Do you get any positive results after change this line?

Hi! I also found this problem. But I think it is not enough to just change here. Another place should also be changed. "network/spvcnn.py" in the line 126, should be changed to self.strides = [int(scale) for scale in self.scale_list]

I think you are right. Do you get any positive results after change this line?

Thank you for your quick reply! I haven't done the experiment yet. I may do it soon.

Hi! I also found this problem. But I think it is not enough to just change here. Another place should also be changed. "network/spvcnn.py" in the line 126, should be changed to self.strides = [int(scale) for scale in self.scale_list]

I think you are right. Do you get any positive results after change this line?

Thank you for your quick reply! I haven't done the experiment yet. I may do it soon.

I see. Thanks for your sharing!

Hi! I also found this problem. But I think it is not enough to just change here. Another place should also be changed. "network/spvcnn.py" in the line 126, should be changed to self.strides = [int(scale) for scale in self.scale_list]

I think you are right. Do you get any positive results after change this line?

Thank you for your quick reply! I haven't done the experiment yet. I may do it soon.

I see. Thanks for your sharing!

I have changed the above two places. As a result of the experiment, miou decreased by about 1%. This is strange!

I am doing this experiment, too. Which dataset do you train the network on? I got 0.6% mIoU decrease on semanticKITTI but 0.1% mIoU increase on nuScenes when only change the line in xModalKD.

Hi! I also found this problem. But I think it is not enough to just change here. Another place should also be changed. "network/spvcnn.py" in the line 126, should be changed to self.strides = [int(scale) for scale in self.scale_list]

I think you are right. Do you get any positive results after change this line?

Thank you for your quick reply! I haven't done the experiment yet. I may do it soon.

I see. Thanks for your sharing!

I have changed the above two places. As a result of the experiment, miou decreased by about 1%. This is strange!

I am doing this experiment, too. Which dataset do you train the network on? I got 0.6% mIoU decrease on semanticKITTI but 0.1% mIoU increase on nuScenes when only change the line in xModalKD.

I did this experiment on the semanticKITTI dataset. Judging from the results recorded by the tensorboard, I suspect that the change in indicators may be caused by randomness.🤣

Hi! I also found this problem. But I think it is not enough to just change here. Another place should also be changed. "network/spvcnn.py" in the line 126, should be changed to self.strides = [int(scale) for scale in self.scale_list]

wow, I think this is a big problem because it affects the backbone of the network ---- SparseCNN. It resulted in a mismatch between indices and spatial_shape in the SpaeseConvTensor in 2DPASS/spvnn.py lines 101 through 106

Hi, sorry for the late response.  After checking the original codes of paper submission, I find out that the error occurs when we reorganize the codebase. In the original codes, spvcnn.py and arch_2dpass.py are in the same function, which is messy to read them. This error does not affect the results in the paper, but it is also strange to me that the misaligned features still improve the performance of baseline. I will re-train the codes this week and give feedbacks. Sorry for the bug and inconvenience again.

Hi! I also found this problem. But I think it is not enough to just change here. Another place should also be changed. "network/spvcnn.py" in the line 126, should be changed to self.strides = [int(scale) for scale in self.scale_list]

I think you are right. Do you get any positive results after change this line?

Thank you for your quick reply! I haven't done the experiment yet. I may do it soon.

I see. Thanks for your sharing!

I have changed the above two places. As a result of the experiment, miou decreased by about 1%. This is strange!

I am doing this experiment, too. Which dataset do you train the network on? I got 0.6% mIoU decrease on semanticKITTI but 0.1% mIoU increase on nuScenes when only change the line in xModalKD.

I did this experiment on the semanticKITTI dataset. Judging from the results recorded by the tensorboard, I suspect that the change in miou may be caused by the randomness.🤣

Hi, my experiment is done. It grow from 65.3@mIoU to 65.9@mIoU and keep the same performance as the original github version.

Thank you for your great work! But I have a small question. In 2DPASS/spvnn.py, I think you use "coors_inv_last" to devoxelization in the line 92, so in 2DPASS/arch_2dpass.py/xModalKD.forward(), should voxelize it with "coors_inv_last" in the line 101?

hello,I would like to ask why coors_inv_last here does not perform feature aggregation on the voxel of the previous scale based on the index of the current voxel but devoxelization. This question has been bugging me for days, I would be very grateful if I could get your answer.
  v_fea_inv = torch_scatter.scatter_mean(v_fea.features[coors_inv_last], coors_inv, dim=0)

Hi! I also found this problem. But I think it is not enough to just change here. Another place should also be changed. "network/spvcnn.py" in the line 126, should be changed to self.strides = [int(scale) for scale in self.scale_list]

I think you are right. Do you get any positive results after change this line?

Thank you for your quick reply! I haven't done the experiment yet. I may do it soon.

I see. Thanks for your sharing!

I have changed the above two places. As a result of the experiment, miou decreased by about 1%. This is strange!

I am doing this experiment, too. Which dataset do you train the network on? I got 0.6% mIoU decrease on semanticKITTI but 0.1% mIoU increase on nuScenes when only change the line in xModalKD.

I did this experiment on the semanticKITTI dataset. Judging from the results recorded by the tensorboard, I suspect that the change in miou may be caused by the randomness.🤣

Hi, my experiment is done. It grow from 65.3@mIoU to 65.9@mIoU and keep the same performance as the original github version.

hello,I would like to ask why coors_inv_last here does not perform feature aggregation on the voxel of the previous scale based on the index of the current voxel but devoxelization. This question has been bugging me for days, I would be very grateful if I could get your answer.
  v_fea_inv = torch_scatter.scatter_mean(v_fea.features[coors_inv_last], coors_inv, dim=0)


Version 1.9.0 has a "warning: string literal in condition" warning message

Subject of the issue
On the latest new version of Ruby git gem, I see this message:
/Users/emmasax/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/git-1.9.0/lib/git/lib.rb:663: warning: string literal in condition

This error is pointing to this line: https://github.com/ruby-git/ruby-git/blob/07a1167d4706ba4a66ab3025229ca4ed844a934d/lib/git/lib.rb#L663
Looking at the error (StackOverflow describes what the warning message means here), it seems the easiest way to fix it is to change that line to:
arr_opts << '--gpg-sign' if opts[:gpg_sign] && (opts[:gpg_sign] == true || opts[:gpg_sign] == "--gpg-sign=#{opts[:gpg_sign]}")

Your environment

Ruby git gem 1.9.0
Ruby version 3.0.1 installed with rbenv

Steps to reproduce
Using the newest version of the git Ruby gem with Ruby 3.0.1:
$ irb
irb(main):002:0> require 'git'
/Users/emmasax/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/git-1.9.0/lib/git/lib.rb:663: warning: string literal in condition
=> true

Expected behaviour
$ irb
irb(main):002:0> require 'git'
=> true

Actual behaviour
See the Steps to reproduce section.

Thank you for the great error report.  I noticed the same warning and added a fix for it in PR #525.  I'll cut a new release soon.

This has been fixed this in git-1.9.1:
$ gem install git -v 1.9.1
Fetching git-1.9.1.gem
Successfully installed git-1.9.1
Parsing documentation for git-1.9.1
Installing ri documentation for git-1.9.1
Done installing documentation for git after 0 seconds
1 gem installed
 $ irb
3.0.1 :001 > require 'git'
 => true
3.0.1 :002 >

Thank you @jcouball!


Shift+Alt+O does not organize imports into single line (regression)

VSCode Version: 1.51.1
OS Version: Windows 10 2004

Steps to Reproduce:

Have npm project TS

Split single import into 2 lines

Hit shift+alt+o

Previous expected behaviour: import is organized into single line
Actual behaviour: import is organized through multiple lines

Does this issue occur when all extensions are disabled?: Yes
Strange thing is, I only noticed this after update to 1.51.1 (from 1.48.2). I tried reinstalling 1.48.2 only to find out that it has exact same behaviour. I then tried 1.45.1 and it was back to how I used to.
Event stranger thing is that I have another laptop (Windows 10 1909) with 1.48.2 installed and shift+alt+o would organize imports into single line. I then updated to 1.51.1 and it would still do single line organize.
I am not sure what is going on, but I asked a few colleagues about this and they too noticed that after recent update imports are not organized into single line.
All behaviours were observed with and without extensions.

Please share a project that demonstrates this issue

It is not project specific, reproduced on this very repo:
v1.45.1

v1.51.1

Please share a minimal project that demonstrates this issue

@mjbvz
Repro steps as steps are in the issue description. I am using VSCode because this issue is about it. Issue is reproducible in any project, as example you can repro it in VSCode project codebase.

This looks expected to me. If you disagree, please file an issue against typescript: https://github.com/microsoft/TypeScript/issues/

Not sure how it is related to typescript directly rather than vscode


Where is the Onsearch property?

I'm trying to follow the example (https://learn.microsoft.com/en-us/power-platform/guidance/creator-kit/peoplepicker#office-365-users-connector) to create this component and under step 2
Assign the below Power Fx formula to the On Search property of the control to create a collection called UserCollection.
Where is the On Search property?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: fa54fe95-e7b1-6e7e-331e-7fcf7fdbca3b
Version Independent ID: fa54fe95-e7b1-6e7e-331e-7fcf7fdbca3b
Content: PeoplePicker control reference (preview) - Power Platform
Content Source: power-platform/guidance/creator-kit/peoplepicker.md
Service: power-platform
Sub-service: guidance
GitHub Login: @denisem-msft
Microsoft Alias: demora

Thanks for your comment, @waiholiu. This issue has been assigned to the doc author for review.


remove (unnecessary) recursive dependency involving ghcPath

This should fix the issues we've been talking about in #599. Let's see what CI says.

@alpmestan Thanks! I love commits with such stats: +0 -8 :-)

Merged!


Check how validator-config.toml is used and if we still need it

It doesn't seem to be used anywhere. I think we can simply remove it.

Was removed


fix: dispose all task executor when exit or refresh

Types

[x] 🐛 Bug Fixes

Background or solution
Changelog

dispose all task executor when exit IDE

/publish


config/ APP_HOST

Codecov Report

Merging #70 (04825da) into main (cc31134) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 04825da differs from pull request most recent head 0487dc8. Consider uploading reports for the commit 0487dc8 to get more accurate results

@@            Coverage Diff            @@
##              main       #70   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           18        18
  Lines          145       149    +4
  Branches        20        20
=========================================
+ Hits           145       149    +4

Impacted Files
Coverage Δ

src/core/middlewares/poswares/errors.js
100.00% <100.00%> (ø)

src/core/utils/app.js
100.00% <100.00%> (ø)


created front page

added background for front-page
button to get started
added title

looks good! Merging this in :)


i found the device,but the uuid is incorrect?

this is correct data
{ranged: [{ uuid: "74278BDA-B645-4520-8F0C-720EAF059935", major: 10, minor: 10, rssi: -60, power: -59 }]}
and your lib cordova-ble on iphone5s 7.01 got this data
{"scanRecord":"","rssi":-46,"name":"HMSensor","address":"097B6444-8691-5631-20DB-E56886D373CD"}

This is not an iBeacon plugin; that would be https://github.com/evothings/cordova-plugin-ibeacon. Closing issue.


MeeShop 0.2.0 stucks at "building databases..." or "Importing necessary modules..."

Installing Meeshop 0.2.0 everything goes ok.
When launching I get:
Setting up workspace...
Done!
Testing internet connection...
Done!
Building databases...

And it doesn't go further most of times.
Other times:
Setting up workspace...
Done!
Testing internet connection...
Done!
Building databases...
Done!
Importing necessary modules...

And it doesn't go further.
Early versions seem to work better

@ferlanero Hmm. Installed with aegis-dpkg? I just removed all cached XMLs from my device and ran MeeShop v0.2.0, works fine.
Importing modules and building databases often take much time.

Thanks for your quickly answer! Uninstalling Meeshop 0.2.0 and reinstaling it again seems to fix the problem. Now everything is working as expected!

@ferlanero Great! Glad it works for you now.


Update release tests

Add checks to ensure private data indexes are copied to the release dir
Contributes to https://github.com/hyperledger-labs/fabric-builder-k8s/issues/106

Hi
I think that we can't hardcode the private data collection name. This will depend on the collection configuration.

Superseded by https://github.com/hyperledger-labs/fabric-builder-k8s/issues/106


Xcode 10.2

it's really strange but Xcode 10.2 freeze on HTMLString during a creation of the archive.

I have the same issue, though archiving continues after a very long time.

I could resolve this issue by removing 'armv7' from Valid Architectures in the Build Settings of the HTMLString target.
If you do this you will loose support for iPhone 4S (according to this Stackoverflow answer: https://stackoverflow.com/a/52436173/7990095)
Also remove 'armv7' from the project/target that is using HTMLString.

Hello, can you check by using the swift5 branch? This should improve compilation times.

Archiving time with swift5 branch is as expected.
Though it may be possible that this issue only occurs when installed via cocoapods (see https://stackoverflow.com/questions/55376236/xcode-10-2-hangs-during-archive-on-arbitrary-task)

I could resolve this issue by removing armv7 from Valid Architectures in the Build Settings of the HTMLString target.
If you do this you will loose support for iPhone 4S (according to this Stackoverflow answer: https://stackoverflow.com/a/52436173/7990095)
Also remove armv7 from the project/target that is using HTMLString.

Hi, I removed arm7 like you said, but nothing changes. The archive process is very long. What do you suggest me?

@pLembo90 Did you try using the swift5 branch?

Hi Alex, thanks for your answer.
My project is write in swift 4.0. The only thing I did was update the pod to 4.0.2.

@pLembo90
I am using the Swift 5 branch without any problems though my project is also written in Swift 4.

@pLembo90 Did you try using the swift5 branch?

Swithing to swift5 branch helps, thank you!

I have solved the problem by setting 'build_settings / Swift Compiler - Code Generation / Optimization Level' to 'No Optimization'
And I put automation script into Podfile
post_install do |installer|
installer.pods_project.build_configurations.each do |config|
config.build_settings.delete('CODE_SIGNING_ALLOWED')
config.build_settings.delete('CODE_SIGNING_REQUIRED')
#puts "set pod build settings. target[#{config.build_settings['MODULE_NAME']}] config[#{config.name}]"
end
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      if target.name == 'HTMLString' and config.name == 'Release' #settings only HTMLString/Release
        puts "set swift optimization level for release > none. target[#{target.name}]" #you can see this log when run 'pod update'
        **config.build_settings['SWIFT_OPTIMIZATION_LEVEL'] = '-Onone'** #this code
      end
    end
  end

end
But, I want to make the script more short.
Please anyone let me know how can I get target.name from config

Swift 5 branch helped a lot too! Thanks, hope it will soon be released as 5.0 :)

Compiling on swift5 also worked for me, but it isn't the most feasible thing long-term because I need to depend on it from another CocoaPod, and the podspec stuff doesn't allow me to specify a branch to compile from. It'd be great if swift5 could be merged into master and issue #21 could be addressed so I can depend on this library from my podspec

The release with the fix should be out now, as 5.0.0. Please open another issue if you still encounter the crash.


Discussion: client option with / without style

Currently, when we choose a front, we have the possibility to choose:

empty home page
home page with minimal css

In my opinion, maintaining both option is not good to add more features.
For example, if we want to add login page (like it's done for Angular), we need to take care of 2 initial options:

without css
with minimal css

So I have several ideas:
1st solution:

stay like this, I'll let the stream lead to decide and maintain future options

2nd solution:

add front framework, with minimal home page in pure html -> the current existing API
add a real css framework -> the API is optional
add login page (like it's done with Angular), and there should be 2 possible login.html (1 without css, 1 with css)
add health check page (same: 2 possible pages: without css, with css)
etc

3rd solution:

add front framework + css framework at the same init
add login page (which will use component, class etc of the initial css framework)

Don't know what is the right way to do.
cc @qmonmert : what do you think? as Angular is the most advanced front in JHipster Lite

@pascalgrimaud I agree that maintaining two options is not a good idea. The third option seems to be good 🙂

I think about the 3rd option too, and I'll let the stream lead to decide which css framework to use
We could use the same way than what is done in generator-jhipster:

generate home page with bootstrap, including minimal navbar
so it will be easier to add item in navbar, etc.

@pascalgrimaud totally agree

Can I put you as the stream lead of Angular part @qmonmert ?

@pascalgrimaud yes!

not sure you can maintain both: Angular and React, but I'll let you choose :)
Ok thanks, then, I'll create more ticket to improve Angular part

The idea behind this is to split correctly all generation part in the DomainService
So if someone is not happy with this, he/she can code his/her own domain service, using the existing files etc

There are already 2 dedicated tickets to finish this:

already done for Angular and Vue
needed to be done for React and Svelte

So let's close this one


Ignore missing root message in relatedMessages()

Prior to this PR, if you ran relatedMessages() on a msg-id that's not present†, but which does have present messages linking to the root, then relatedMessages() would call the cb() with an error message, and, in some cases, would call the cb twice, resulting in a backend crash (cb called twice error).
This PR does two things:

Guards against the double cb-call
Ignores a root-not-found error, so that the rest of the thread can be assembled

† present: saved in the local database

:clap:

awesome, merged into 15.0.5
On Fri, Apr 1, 2016 at 7:12 AM, Charles Lehner<EMAIL_ADDRESS>wrote:

[image: :clap:]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ssbc/secure-scuttlebutt/pull/146#issuecomment-204060986


formats: use a simple non-nested regexp for uuids

Also no need for the length check this way.
Tests will be introduced with updated JSON Schema Test Suite.

Codecov Report

Merging #100 into master will increase coverage by 0.06%.
The diff coverage is 100.00%.

Impacted Files
Coverage Δ

src/formats.js
96.06% <100.00%> (+0.71%)
:arrow_up:


zinc.rs uses expired certificate

The certificate for https://zinc.rs/ expired on September 10th.

I totally remember discussing this a week ago at RustConf, but I don't remember fixing it >_(\
Thanks!


Feature/repository datastax migration performance

Batch assignment flow optimizations...

Coverage increased (+0.02%) to 73.62% when pulling 3c030591c4c4579f4fafa1ac78ed03314c55b2f3 on feature/repository-datastax-migration-performance into 169002b6450190616621d2b810cb1e532803d781 on feature/repository-datastax-migration.

Coverage increased (+0.02%) to 73.62% when pulling fffdf08eb07d8f202658f01677efd7953f0f6e82 on feature/repository-datastax-migration-performance into 169002b6450190616621d2b810cb1e532803d781 on feature/repository-datastax-migration.

Thanks @felixgao and @mans4singh for reviewing the code... I have addressed comments, kindly let me know if you have any further comments...

Coverage increased (+0.02%) to 73.62% when pulling e36d662b1d1dd1cfa4bf98c20399237f803c43bd on feature/repository-datastax-migration-performance into 169002b6450190616621d2b810cb1e532803d781 on feature/repository-datastax-migration.

Coverage increased (+0.02%) to 73.62% when pulling e36d662b1d1dd1cfa4bf98c20399237f803c43bd on feature/repository-datastax-migration-performance into 169002b6450190616621d2b810cb1e532803d781 on feature/repository-datastax-migration.


[discuss] Discussion of executing a single server under multiple nodes

I am thinking that in the actual project application scenario, our cron actually runs under multiple nodes.
I was wondering if I could provide an independent way to support the multi-node guarantee of single-node operation.

I am thinking that in the actual project application scenario, our cron actually runs under multiple nodes.
I was wondering if I could provide an independent way to support the multi-node guarantee of single-node operation.

Through a distributed lock to ensure that only one of the multiple nodes can perform tasks?
If you use this scheme, you need to ensure that the time of multiple nodes is consistent.

I am thinking that in the actual project application scenario, our cron actually runs under multiple nodes.我在想，在实际的项目应用场景中，我们的cron实际上是在多个节点下运行的。
I was wondering if I could provide an independent way to support the multi-node guarantee of single-node operation.我想知道我是否可以提供一种独立的方式来支持单节点操作的多节点保证。

Through a distributed lock to ensure that only one of the multiple nodes can perform tasks?通过分布式锁来保证多个节点中只有一个可以执行任务？ If you use this scheme, you need to ensure that the time of multiple nodes is consistent.如果使用此方案，则需要保证多个节点的时间一致。
Do you have a better plan? Look forward to further communication with you你有更好的计划吗？期待与您的进一步沟通

I wrote a Mutex to implement a distributed single server to run. This is my implementation on go-kratos.
https://github.com/go-kratos-ecosystem/components/tree/2.x/crontab

PS: I don't think it's optimal, there's room for improvement, but I haven't had time to think about it. If you have any better suggestions, I'd love to hear them.

I am thinking that in the actual project application scenario, our cron actually runs under multiple nodes.
I was wondering if I could provide an independent way to support the multi-node guarantee of single-node operation.

Through a distributed lock to ensure that only one of the multiple nodes can perform tasks? If you use this scheme, you need to ensure that the time of multiple nodes is consistent.
Do you have a better plan? Look forward to further communication with you你有更好的计划吗？期待与您进一步沟通

I implemented a package to solve this problem, the address of the package is: https://github.com/go-kratos-ecosystem/components/tree/2.x/crontab/jobwrapper/mutex
How to use it: https://github.com/go-kratos-ecosystem/components/blob/2.x/crontab/README.md


react-router-redux is deprecated

Hi @supasate !
now when react-router-redux is deprecated you proably would be the best alternative
https://github.com/ReactTraining/react-router/commit/b1a77bceaf972dddb557b7ddd52131df91e15d14
the main concern about this project - it was not updated for a long time. please tell us about your plans? is this project still alive? can we expect updates?
PS and if yes, it would be good to have SSR because its the only thing missinng from RRR functionality

The world now lacks any maintained solution for binding the router to redux? Angular has one via ngrx despite the react community popularizing the redux pattern, surprising it fell behind.

I'll be back to start maintaining it again. But, my time is quite limited, so, if anyone is interested to help maintain the project, please let me know!

I’m not very experience on maintaining an GitHub project, but I would be very glad helping somehow!

@brneto Thanks! Can you connect with me via my public email?

hi @supasate I can help a bit too

@supasate is there any plans to add Readme section about migrating from react-router-redux?

@supasate good to hear
I'd like to help as I can
It would be good to make a realease soon, so these are my thoughts on what should be done (read: people want to see)

[ ] bump, check and fix peer deps for redux 4 (redux, react-redux, redux-devtools, redux-devtools-extension)'

[ ] fix SSR, use MemoryHistory or HashHistory (history, react-router-dom)

for example simple hack will work
import {createBrowserHistory, createMemoryHistory} from "history";

const canUseDOM = !!(typeof window !== "undefined" && window.document && window.document.createElement);

export default canUseDOM ? createBrowserHistory() : createMemoryHistory();

For the next major update

[ ] think about smoth migration from RRR by changing API to what it was in RRR. this is kinda tricky but rematch users already complaining

also idk what to do if I want to connect router to my custom component?
should i do something like this?
const App = ({ history }) => {
  return (
    <MyCustomConnectedRouter history={history}>
      <ConnectedRouter history={history}>
        { routes }
      </ConnectedRouter>
    </MyCustomConnectedRouter>
  )
}

Hi there, I would also be willing to help with merging PRs

Do you plan to release a migrating guide?  react-router-redux -> connected-react-router

Do you plan to release a migrating guide? react-router-redux -> connected-react-router

I have a fairly complicated setup - I'm going through the conversion today - I use redux-persist and redux-saga as well.
I'll document the code I have to change - it might be a good base to start something from.

Was fairly straight - forward - he's my steps:
(Old code is commented out)
yarn add connected-react-router
// import { routerMiddleware } from 'react-router-redux';
import { routerMiddleware } from 'connected-react-router';
// import { push } from 'react-router-redux';
import { push } from 'connected-react-router';
// import { ConnectedRouter } from 'react-router-redux';
import { ConnectedRouter } from 'connected-react-router';
// import { routerReducer as routing } from 'react-router-redux';
import { connectRouter } from 'connected-react-router';
const combinedReducers = persistCombineReducers(persistConfig, {
...baseReducers,
...customReducers,
form,
orm,
// routing,
router: connectRouter(history),
});
yarn remove react-router-redux

@jmcpeak Where does the history argument come from?

@ralphicus you need to add these two lines in that file
import { createBrowserHistory } from 'history' const history = createBrowserHistory()

Can I in some way use the history object from react-router, or is the separate history package required?


Permission issue on OSX and sudo problem

Trying to enable any alias getting the permission error:

2016-02-14 12:05:50 ☆  Vlads-MBP in ~
○ → bash-it enable alias git
mkdir: /Users/vinchi007/.bash_it/aliases/enabled: Permission denied
ln: /Users/vinchi007/.bash_it/aliases/enabled/git.aliases.bash: No such file or directory
git enabled.

When running as sudo, bash-it function does not pass off to sudo environment:

2016-02-14 12:05:56 ☆  Vlads-MBP in ~
○ → sudo bash-it enable alias git
Password:
sudo: bash-it: command not found

When I did

git clone
it required to use sudo. Once I used sudo it created ~/.bash_it dir with root permission "root:group" instead of "myuserid:group". To fix it I did:
chown -R myuserid:group ~/.bash_it

Can we add some login into bash-it so it checks permissions of the dir?

Thanks for the detailed analysis. The issue was caused by the wrong ownership of the Bash-it directory. The question is why you had to use sudo to clone the repo in the first place...
I'm not sure whether we need to add a check for that - in theory, this could happen with any project, and the general expectation is that you have write permissions in your own home directory. If you use sudo to write stuff to your home directory, it's pretty much always going to end up in tears.

agree, this is local permission issue. However, I think the status should properly reflect that the action failed (enabling an alias) - instead it misleads by stating "git enabled"

Good point - that's probably worth fixing.

I tried to manage this issue in #832, can you test it @vinchi007?
Thanks!

This issue is very stale, so I close it. Thanks for contributing and posting!


feat: introduce scaffold admission-request command

This command creates a Kubernetes AdmissionRequest object starting from a Kubernetes Resource definition.
The following command:
kwctl scaffold \
  admission-request \
  --operation CREATE \
  --object ingress.yaml

produces an AdmissionRequest CREATE event for the given Ingress object.
Currently, only the CREATE operation is supported. The other operations will be added in the future.

Depends on https://github.com/kubewarden/policy-evaluator/pull/548

LGTM. But I have a question in mind, what happens if the user has multiple contexts in the kubeconfig? Will the catalog contains the kinds from the default context? I'm wondering about the UX for the user which is building a request for a CRDs which is not in the "default" context.

The catalog will be built from the default context.

If this is an issue at all, I don't think this is a huge issue as well and we do not need to fix it now. But if it is, is there an easy workaround for it? Like defining the context to be used or fetch resources from all the contexts ( I'm not sure if this is a good idea in end end as well ) .

Going through all the contexts would take time and also possible timeouts because maybe some of the clusters are not reachable.
It's good that you pointed out this possible limitation, but I would not focus on that right now. The scaffold code always generate something that will work for 99.9% of the policies.
We can find a solution to this corner case situation if someone complains about that.


[move framework][move-prover] Some specs from LIP-6, refactoring of initialization in Genesis

Changes to a bunch of .move files related to LibraAccount and LibraSystem.
Added specification that every account has a role in LibraAccount.
Refactored Genesis and LibraAccount some to make this easier to prove,
and to clean up initialization.  Specifically, roles for libra root
and treasury compliance were added in Genesis separately from the
account creation functions.  So, I moved role creation into the account creation functions. Genesis was also creating the libra root and treasury compliance accounts directly, so I moved those into LibraAccount::initialize, which simplifies the Genesis code and eliminates some dependencies.
In various places, I renamed accounts to reflect their roles, if
known.  I also added some assertion checks in SlidingNonce, which was
getting errors from unchecked aborts.

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

Is this a breaking change? It certainly changes genesis a bit, but I'm not sure if anything needs to change if you don't rebuild genesis.

/land

:broken_heart: Test Failed - commit-workflow

There's probably some trailing whitespace issue that needs to be resolved XD

/land

:exclamation: Land has been canceled due to this PR being updated with new commits. Please issue another Land command if you want to requeue this PR.

/land

:exclamation: Land has been canceled due to this PR being updated with new commits. Please issue another Land command if you want to requeue this PR.

/land

:broken_heart: Test Failed - commit-workflow

/land

:lock: Merge Conflict

/help

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
This project requires PRs to be Reviewed and Approved before they can be queued for merging.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

/priority high
/land

/priority high

/land

:broken_heart: Test Failed - commit-workflow

/priority high

/land


Asking postgres user password

Hi,
When I adding
add gtm master gtm_m_1 postgresql-1-gtm-m-1 5432 /var/lib/postgres/data/gtm
Docker container asking me postgres user password.
PGXC add gtm master gtm_m_1 postgresql-1-gtm-m-1 5432 /var/lib/postgres/data/gtm Initialize GTM master The authenticity of host 'postgresql-1-gtm-m-1 (<IP_ADDRESS>)' can't be established. ECDSA key fingerprint is da:a7:5c:53:dd:39:a6:57:6a:50:09:06:6c:83:95:f3. Are you sure you want to continue connecting (yes/no)? yes postgres@postgresql-1-gtm-m-1's password:

Hi @mustafayildirim. Sorry, I missed this message. Sounds like an SSH key problem. Does the connection work outside of pgxc_ctl, e.g. ssh postgres@postgresql-1-gtm-m-1?

I haven't heard back about this, so I'm going to presume it's sorted. If not, feel free to say. But I recommend you use 0.2.0, if possible, which completely redesigns the approach and doesn't require SSH at all. :)


Default behavior when an entity is not found

For some store methods (and that are also surfaced in Client APIs), we are returning errors when a specific ID is not found. For example, searching for an account ID or a single Note ID results in an error.
A perhaps more usable alternative could be to return an Option<> that determines whether the entity was found or not.

Related:

Also, the behavior of NoteFilter::Unique seems a bit unintuitive to me. Specifically, why not return an empty vector if the note with the specified ID could not be found? This would be much more consistent with the behavior of all other filters. Let's create an issue to discuss this.

Originally posted by @bobbinth in https://github.com/0xPolygonMiden/miden-client/pull/508#discussion_r1740180867


Fix memory leak bug in RCTModalHost

This PR addresses issue #9265.
Negated the condition that checks if _hostViews exists so that _hostViews will be allocated only if it doesn't exist

By analyzing the blame information on this pull request, we identified @javache and @jemise111 to be potential reviewers.

@facebook-github-bot shipit

Thanks for importing.If you are an FB employee go to Phabricator to review internal test results.

@ide: I see that facebook-github-bot-3 closed this PR. I couldn't understand what this meant. Could you please shed some light in to this?

It means your PR was merged, see the commit hash in the message.

Awesome 🎉 . Thank you @ide


Rest endpoints: Get transactions from collectives and Get transactions from payment methods

This PR contains 2 new REST endpoints:
GET /v1/collectives/:collectiveSlug/transactions
This query requires the collective slug of. It also allows the following query parameters:
- type - If Transaction is DEBIT or CREDIT
- limit - the number of records to be returned
- offset - the number that determines offset of the query
- dateFrom - the start date(format YYYY-MM-DD) to be considered when returning the data
- dateTo - the end date(format YYYY-MM-DD) to be considered when returning the data
Example:
Open Collective(a collective that has slug opencollective-company) wants to see his last 3 CREDIT transactions:
curl "http://localhost:3060/v1/collectives/opencollective-company/transactions?limit=3&type=CREDIT" \
  -H "Content-Type: application/json"\
  -H "Client-Id: ${clientId}"

This returns the following json JSON:
{
   "result":[
      {
         "id":9047,
         "uuid":null,
         "type":"CREDIT",
         "amount":500,
         "currency":"USD",
         "hostCurrency":"USD",
         "hostCurrencyFxRate":1,
         "hostFeeInHostCurrency":-25,
         "platformFeeInHostCurrency":-25,
         "paymentProcessorFeeInHostCurrency":-45,
         "netAmountInCollectiveCurrency":405,
         "createdAt":"Sun Apr 30 2017 22:33:49 GMT-0400 (Eastern Daylight Time)",
         "updatedAt":"Thu Mar 08 2018 15:24:33 GMT-0500 (Eastern Standard Time)",
         "host":{
            "id":8686,
            "slug":"opencollectiveinc"
         },
         "createdByUser":{
            "id":3605,
            "email":null
         },
         "fromCollective":{
            "id":4505,
            "slug":"christinabowen"
         },
         "collective":{
            "id":1,
            "slug":"opencollective-company"
         },
         "paymentMethod":{
            "id":2198
         }
      },
      {
         "id":7698,
         "uuid":null,
         "type":"CREDIT",
         "amount":500,
         "currency":"USD",
         "hostCurrency":"USD",
         "hostCurrencyFxRate":1,
         "hostFeeInHostCurrency":-25,
         "platformFeeInHostCurrency":-25,
         "paymentProcessorFeeInHostCurrency":-45,
         "netAmountInCollectiveCurrency":405,
         "createdAt":"Fri Mar 31 2017 22:25:57 GMT-0400 (Eastern Daylight Time)",
         "updatedAt":"Thu Mar 08 2018 15:23:18 GMT-0500 (Eastern Standard Time)",
         "host":{
            "id":8686,
            "slug":"opencollectiveinc"
         },
         "createdByUser":{
            "id":3605,
            "email":null
         },
         "fromCollective":{
            "id":4505,
            "slug":"christinabowen"
         },
         "collective":{
            "id":1,
            "slug":"opencollective-company"
         },
         "paymentMethod":{
            "id":2198
         }
      },
      {
         "id":7322,
         "uuid":null,
         "type":"CREDIT",
         "amount":500,
         "currency":"USD",
         "hostCurrency":"USD",
         "hostCurrencyFxRate":1,
         "hostFeeInHostCurrency":-25,
         "platformFeeInHostCurrency":-25,
         "paymentProcessorFeeInHostCurrency":-45,
         "netAmountInCollectiveCurrency":405,
         "createdAt":"Mon Mar 20 2017 20:20:24 GMT-0400 (Eastern Daylight Time)",
         "updatedAt":"Thu Mar 08 2018 15:24:47 GMT-0500 (Eastern Standard Time)",
         "host":{
            "id":8686,
            "slug":"opencollectiveinc"
         },
         "createdByUser":{
            "id":3605,
            "email":null
         },
         "fromCollective":{
            "id":4505,
            "slug":"christinabowen"
         },
         "collective":{
            "id":1,
            "slug":"opencollective-company"
         },
         "paymentMethod":{
            "id":2198
         }
      }
   ]
}

GET /v1/payment-methods/:uuid/transactions
This query requires the uuid of a payment method. It also allows the following query parameters:
- type - If Transaction is DEBIT or CREDIT
- limit - the number of records to be returned
- offset - the number that determines offset of the query
- dateFrom - the start date(format YYYY-MM-DD) to be considered when returning the data
- dateTo - the end date(format YYYY-MM-DD) to be considered when returning the data
Example:
A Backer wants to see his last 5 DEBIT transactions using his credit card(payment method uuid XXXX-XXXX):
curl "http://localhost:3060/v1/payment-methods/XXXX-XXXX/transactions?limit=2&type=DEBIT" \
  -H "Content-Type: application/json"\
  -H "Client-Id: ${clientId}"

This returns the following json JSON:
{
   "result":[
      {
         "id":115811,
         "uuid":null,
         "type":"DEBIT",
         "amount":-142,
         "currency":"USD",
         "hostCurrency":"USD",
         "hostCurrencyFxRate":1,
         "hostFeeInHostCurrency":-10,
         "platformFeeInHostCurrency":-10,
         "paymentProcessorFeeInHostCurrency":-38,
         "netAmountInCollectiveCurrency":-200,
         "createdAt":"Fri Sep 07 2018 17:53:44 GMT-0400 (Eastern Daylight Time)",
         "updatedAt":"Fri Sep 07 2018 17:53:44 GMT-0400 (Eastern Daylight Time)",
         "host":{
            "id":11004,
            "slug":"opensourcecollective"
         },
         "createdByUser":{
            "id":15873,
            "email":null
         },
         "fromCollective":{
            "id":58,
            "slug":"mochajs"
         },
         "collective":{
            "id":18520,
            "slug":"marcogbarcellos"
         },
         "paymentMethod":{
            "id":15032
         }
      },
      {
         "id":115809,
         "uuid":null,
         "type":"DEBIT",
         "amount":-142,
         "currency":"USD",
         "hostCurrency":"USD",
         "hostCurrencyFxRate":1,
         "hostFeeInHostCurrency":-10,
         "platformFeeInHostCurrency":-10,
         "paymentProcessorFeeInHostCurrency":-38,
         "netAmountInCollectiveCurrency":-200,
         "createdAt":"Fri Sep 07 2018 17:50:50 GMT-0400 (Eastern Daylight Time)",
         "updatedAt":"Fri Sep 07 2018 17:50:50 GMT-0400 (Eastern Daylight Time)",
         "host":{
            "id":11004,
            "slug":"opensourcecollective"
         },
         "createdByUser":{
            "id":15873,
            "email":null
         },
         "fromCollective":{
            "id":11885,
            "slug":"mongoose"
         },
         "collective":{
            "id":18520,
            "slug":"marcogbarcellos"
         },
         "paymentMethod":{
            "id":15032
         }
      }
   ]
}

fixes https://github.com/opencollective/opencollective/issues/1307

Coverage decreased (-0.2%) to 71.124% when pulling b333a79910cfbf22dcb0d6d46ceea80c73101910 on 1307-get-pm-transactions into 723d443d97b8d2314c5970f1cb12da8db6645758 on master.


Article publication (from WordPress) broken?

If I try to create a new DPS article from the 'Add new article' page in WordPress itself (with the plugin installed - /wp-admin/post-new.php?post_type=dpsfa_article) the published article seems quite broken. It looks ok in WordPress, but if I go into the plugin's Articles view, the recently created article has no title or name

Hi @toby1kenobi,
We're working on either redirecting those options into the plugin or removing them until we implement the "normal" support we have in the General tab in settings. For now just click Digital Publishing and once in the plugin you can then choose Articles and make an article inside of the plugin.
Thank you,
-Studio Mercury

Ok, thanks for the update


#324-version id must not be blank

fixes #324

Current coverage is 41.69%

Merging #325 into master will decrease coverage by -0.01% as of 936af18

@@            master    #325   diff @@
======================================
  Files          121     121
  Stmts         2496    2499     +3
  Branches       208     211     +3
  Methods          0       0
======================================
+ Hit           1041    1042     +1
- Partial         40      42     +2
  Missed        1415    1415

Review entire Coverage Diff as of 936af18

Powered by Codecov. Updated on successful CI builds.


Add Task and TaskList Models

Task: isSameTask() checks for similarity irrespective of isDone flag
TaskList: add() checks for similarity with isSameTask() whereas remove() checks for exact match with equals()

Codecov Report

Merging #93 (9b76392) into master (d64522b) will decrease coverage by 4.60%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #93      +/-   ##
============================================
- Coverage     72.15%   67.55%   -4.61%
  Complexity      399      399
============================================
  Files            70       74       +4
  Lines          1232     1316      +84
  Branches        125      143      +18
============================================
  Hits            889      889
- Misses          311      395      +84
  Partials         32       32

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/task/Task.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/model/task/TaskList.java
0.00% <0.00%> (ø)

.../model/task/exceptions/DuplicateTaskException.java
0.00% <0.00%> (ø)

...s/model/task/exceptions/TaskNotFoundException.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


AMQP Output - Batched Messages are sent to wrong topics

Hello,
Using the AMQP output and batching, there is a small defect.
https://github.com/Jeffail/benthos/blob/07e31971131b33a7131ecf1084d60c94fc696956/lib/output/writer/amqp.go#L216
The topic is set once per message, not per part. Looks like that code just needs to move into the iterator function.
Benthos: 3.12

Hey @kozelok, I should be able to tackle this today.

Fixed, https://github.com/Jeffail/benthos/commit/f1b14dd23cd1ef51cc3da9029678233353516a9a I'll add this to tomorrows release.


Missing the forward slash in the instructions for the lesson

Challenge http://www.freecodecamp.com/challenges/waypoint-use-a-css-class-to-style-an-element has an issue. Please describe how to reproduce it, and include links to screen shots if possible.
What I see:
You can apply a class to an HTML element like this:
CatPhotoApp
What I expected to see:
You can apply a class to an HTML element like this:
CatPhotoApp

Markdown's getting in the way, see screenshot.


QuickExplorer Collision / Feature Request

Quick explorer sometimes collides with titlebar as #20 notes, it can also sometimes conflict with themes that move the statusbar to the titlebar, like sanctum

I was also thinking that this might be solvable with a setting in for QE to only show current level + 2 or 3 levels higher, and then perhaps a [. . . . .]?

Perhaps you should contact the author(s) of the relevant themes to suggest something be done in the theme, as I'm unlikely to add any settings to QE in the near future, and fixing this seems very theme-dependent.  Alternately, you can use some of the CSS snippets posted in these issues that allow hiding QE items or making them opaque.


bonus points

The dev tools on chrome crash with this setup.
Could be an interesting 'security feature' on a website.

It might be because of each document being connected to the dev server :/
I don't think it would work the same way on a production environment (fortunately ?)


Future Bug with RAJA Code in Mint

In Mint, at the line sampled below, RAJA::statement::tile_fixed is used. At the moment, and for an indeterminate amount of time, this is the correct usage for RAJA, but the commit
https://github.com/LLNL/RAJA/commit/ad3f19678b24e440bd4ba9c61641d06db9ebf5e7 on the RAJA develop branch moves tile_fixed from the RAJA::statement namespace to the RAJA namespace. Thus, at some point in the future, once this change in RAJA moves to release, the use in Mint will need to change.
This isn't exactly a problem that exists for Axom at the moment, but I wanted to document this, so the problem and solution are known when it arises naturally.
https://github.com/LLNL/axom/blob/c3a64b372d25e53976b3ba8676a25acc49a9a6cd/src/axom/mint/execution/internal/structured_exec.hpp#L112

Thanks @Parqua -- I am aware of the namespace changes in RAJA and I plan to make this change after RAJA is released at which point we can proceed with updating RAJA (as well as, Umpire) in Axom and making an Axom release.
This is needed by downstream host applications that rely on RAJA, Umpire, Axom etc.

@gzagaris @Parqua FYI: here is a link to the release notes for the upcoming RAJA release. The "API Changes" section contains namespace changes we have made.

Thanks @rhornung67 -- you forgot the link, but we can figure that out 😄

Is a RAJA release in the plans for this week? next week?
Is another Umpire release also in the works?

I am just trying to put the timelines in to perspective, since we would have to get a corresponding Axom release for the host code I am working on.

RAJA release will be in 2-3 weeks, hopefully. We’re trying to get our remaining PRs in.  I think the plan is to have RAJA, Umpire and CHAI all be released around the same time so we’re all using the same versions of BLT and camp. We have to coordinate with those other projects.
--Rich
From: George Zagaris<EMAIL_ADDRESS>Reply-To: LLNL/axom<EMAIL_ADDRESS>Date: Monday, July 27, 2020 at 11:08 AM
To: LLNL/axom<EMAIL_ADDRESS>Cc: "Hornung, Rich"<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [LLNL/axom] Future Bug with RAJA Code in Mint (#314)
Thanks @rhornung67https://github.com/rhornung67 -- you forgot the link, but we can figure that out 😄

Is a RAJA release in the plans for this week? next week?
Is another Umpire release also in the works?

I am just trying to put the timelines in to perspective, since we would have to get a corresponding Axom release for the host code I am working on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/LLNL/axom/issues/314#issuecomment-664553661, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADBVDHEYO34HHXQVGIJ4H6LR5W7B5ANCNFSM4PHRXDNA.

RAJA release will be in 2-3 weeks, hopefully. We’re trying to get our remaining PRs in. I think the plan is to have RAJA, Umpire and CHAI all be released around the same time so we’re all using the same versions of BLT and camp. We have to coordinate with those other projects.

Yup -- that is primarily why I was inquiring about this.

I will be doing another BLT release today that will fix the blocking problem for umpire

Great -- thanks @white238
By "blocking problem" you mean do not require CUDA_TOOLKIT_ROOT_DIR correct?

Great -- thanks @white238
By "blocking problem" you mean do not require CUDA_TOOLKIT_ROOT_DIR correct?

yepp! It's been fixed in develop but i just need to go through the whole set of release PR's.


FileLocator should support finding "child" locators.

The FileLocator trait supports finding a parent locator, and finding a 'relative' child locator, but it doesn't support enumeration of all children relative to the given FileLocator.
This is needed to support (say) a parquet 'multi-loader', which enumerates all the parquet files in a given directory and then reads them all.

Closing as work on FileLocator has stopped.


Uncaught TypeError: Cannot read property 'repo' of undefined

Hey I'm really excited about this package.  Unfortunately when I first installed it, I got the below stack trace every time I clicked on the visualization.  After further investigation, this seems like it may be an issue with multiple folders in a project, since when I open a single folder, it works.
I'm happy to do more testing or answer any questions if it would help, since I love the idea.
Atom Version: 1.3.2
System: Mac OS X 10.11.2
Thrown From: git-time-machine package, v1.0.1
Other possibly relevant packages used: I use Project Manager to quick setup a project that contains multiple repositories and excludes some files.  Each file I'm looking at is in a git repository though, and the package is able to correctly visualize its commits, and show commit summaries on hover.
Stack Trace
Uncaught TypeError: Cannot read property 'repo' of undefined
At /Users/ben/.atom/packages/git-time-machine/lib/git-revision-view.coffee:52

TypeError: Cannot read property 'repo' of undefined
    at Function.module.exports.GitRevisionView._loadRevision (/Users/ben/.atom/packages/git-time-machine/lib/git-revision-view.coffee:52:11)
    at Function.module.exports.GitRevisionView.showRevision (/Users/ben/.atom/packages/git-time-machine/lib/git-revision-view.coffee:42:6)
    at GitTimeplot.module.exports.GitTimeplot._viewNearestRevision (/Users/ben/.atom/packages/git-time-machine/lib/git-timeplot.coffee:210:20)
    at later (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/underscore-plus/node_modules/underscore/underscore.js:724:25)

Commands
     -2:47.8.0 fuzzy-finder:toggle-file-finder (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -2:43.8.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -2:43.8.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -2:41.3.0 tree-view:toggle (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -2:36.4.0 project-manager:list-projects (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -2:35.6.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -2:27.6.0 git-time-machine:toggle (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -1:50.4.0 vim-mode:reset-normal-mode (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:04.7.0 window:toggle-dev-tools (a.btn-issue.btn.btn-error)

Config
{
  "core": {
    "ignoredNames": [
      ".git",
      ".DS_Store",
      "*.pyc"
    ],
    "followSymlinks": true,
    "disabledPackages": [
      "autocomplete-plus-python-jedi"
    ],
    "themes": [
      "nucleus-dark-ui",
      "atom-dark-fusion-syntax"
    ]
  }
}

Installed Packages
# User
atom-dark-fusion-syntax, v1.1.0
atom-ternjs, v0.12.2
autocomplete-python, v1.2.4
cursor-history, v0.5.9
editorconfig, v1.2.2
git-time-machine, v1.0.1
highlight-selected, v0.11.1
language-babel, v2.7.0
linter, v1.11.3
linter-eslint, v5.2.7
linter-less, v2.3.3
minimap, v4.19.0
minimap-highlight-selected, v4.3.1
nucleus-dark-ui, v0.7.3
pigments, v0.19.5
project-manager, v2.6.5
vim-mode, v0.64.0
vim-surround, v0.8.1

# Dev
vim-mode, v0.62.0

Hi Ben, thanks for the report.   I just pushed a fix for that issue.  I have to be honest a say that I stole the code for that part from git-history - don't completely understand why it doesn't work, but it was for an unused option that's not needed, so I removed it.  Let me know if you still see the problem and I'll reopen the issue.

I experienced this yesterday. But all other Git integration in Atom stopped working at the same time. I have my Git repo in a symlink, that could be the reason maybe.
Restarting Atom worked for me.

@littlebee perfect, works great now thanks.
Thanks for making this package, one of the coolest editor extensions I've ever seen.  Great work!