DSC, DSCI: add validating webhook (#711)

Jira: https://issues.redhat.com/browse/RHOAIENG-4268
This patch reverts
528801571f00 ("Revert "DSC, DSCI: add validating webhook (#711)"")

Description

How Has This Been Tested?
Tested:

deployed catalog
installed operator
created DSCI
created another DSCI with another name, got message that it's prevented

Screenshot or short clip

Merge criteria

[ ] You have read the contributors guide.
[ ] Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
[ ] Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

/retest-required

Hmm, reconciliation loop in the logs

/retest-required

/retest-required

/test rhods-operator-e2e

@ykaliuta I think this needs a rebase

@ykaliuta I think this needs a rebase

I'm afraid, it has some other problems as well, I did rebase several times. But I did not manage to debug it yet.

@VaishnaviHire @zdtsw I'm afraid to touch it after it passed e2e-test :)

we will need get this in before merge ModelReg piece in downstream

/retest-required

and it's passed e2e again! :)

/lgtm
Tested by trying to create multiple DSCI and DSC
Deleting DSCI before DSC worked. But I guess it is expected with current set of changes

/lgtm
Tested by trying to create multiple DSCI and DSC
Deleting DSCI before DSC worked. But I guess it is expected with current set of changes

should we get  https://github.com/opendatahub-io/opendatahub-operator/pull/1094 in after this PR is merged?


chore: update v8-versions file for 3.3 (next)

Nice catch, I forgot to update it along with the package.json version bump!


Add more player-facing information about fish abilities

Right now, players can't possibly know why they should choose a sea slug or a mudfish.
Consider improving descriptions dramatically, or adding a unit-info popup card which exposes all their abilities.

I've added baseball-style stat cards to the bottom right

All fish descriptions could be improved still


Better expose and document batch prediction from dataloaders

The current API prioritizes simple functions over performance. In cases where we have lots of images already yielded from a dataloader, its quite annoying to either save them to file to use main.predict_file, or to manipulate the dataloader to get the images preprocessed as expected. We could loop through them individually and call predict_image, but that is really wasteful given modern GPU memory.
for batch in test_loader:
    for image_metadata, image, image_targets in batch:
        # preprocess that image, for example Deepforest likes 0-255 data, channels first
        pred = m.predict_image(channels_first)

not great.
Instead a batch prediction mechanism is just sitting there, already in the codebase, but its not quite clear.
for idx, batch in enumerate(test_loader):
    metadata, images, targets  = batch
    # Preprocessing here
    predictions = m.predict_step(images,idx)

where predictions is a list of results that have been formatted into dataframes from tensors, like the other predict family of functions. predict_step is a pytorch ligthning method and reserved for trainer.predict it can't be renamed, but it can be wrapped into some other function if we wanted to.
This pathway isn't really in docs and it would take an astute user to recognize it. It should be much faster since the batches might be quite large if you have a big GPU
Next steps

Document this behavior

Consider a predict_batch function that mirrors the format of predict_file, predict_image, predict_tile to help guide users through this.

hey @bw4sz  i would like to solve this issue if its still unassigned!

Great!
Ben Weinstein, Ph.D.
Research Scientist
University of Florida
On Wed, Dec 11, 2024 at 1:08 PM RohitP2005 @.***> wrote:

hey @bw4sz https://github.com/bw4sz i would like to solve this issue if
its still unassigned!
—
Reply to this email directly, view it on GitHub
https://github.com/weecology/DeepForest/issues/849#issuecomment-2537184926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJHBLAE7TOUBIXBPPENCMD2FCSUHAVCNFSM6AAAAABTOFMJVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXGE4DIOJSGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Fine, then i will start to work on it.

PR is here https://github.com/weecology/DeepForest/pull/856


Maintenance status

Hello,
Out of curiosity: is your project still maintained, but hasn’t seen updated because it just works or has it been abondened?

Hi. I didn't use the project myself in a while but had no major issues. So i "assume" it just works. ;-)
If needed and time allows, i am still willing to jumo into the code again.

Good to hear, thank you for your quick response


How to initialize part of a model in Flax?

Suppose you have a model called BigModel. You want to load part of the weights of this model from a checkpoint, and you want to initialize the rest of the weights randomly. For instance, you may want to use BERT-encoded text as input.
You can do this by initializing the entire model with random weights, and then replacing the subtree of parameters corresponding to the parameters from your checkpoint. In Flax, (immutable) parameters are represented as a nested FrozenDict. So before you can modify the parameters, you have to make sure you "unfreeze" them, and "freeze" them again after modification.
Pseudo-code:
from flax.core import freeze, unfreeze

bert_params = load_bert_params()  # These are the params you want to load.
params = BigModel(...).init(...)['params']
params = unfreeze(params)
params['bert'] = bert_params
params = freeze(params)

Suppose you have a model called BigModel. You want to load part of the weights of this model from a checkpoint, and you want to initialize the rest of the weights randomly. For instance, you may want to use BERT-encoded text as input.
You can do this by initializing the entire model with random weights, and then replacing the subtree of parameters corresponding to the parameters from your checkpoint. In Flax, (immutable) parameters are represented as a nested FrozenDict. So before you can modify the parameters, you have to make sure you "unfreeze" them, and "freeze" them again after modification.
Pseudo-code:
from flax.core import freeze, unfreeze

bert_params = load_bert_params()  # These are the params you want to load.
params = BigModel(...).init(...)['params']
params = unfreeze(params)
params['bert'] = bert_params
params = freeze(params)


Updating meeting times

What type of PR is this?
/kind documentation
What this PR does / why we need it:
This updates the meeting times based on the results of the earlier StrawPoll. This corresponds with https://github.com/kubernetes/community/pull/5764.
Does this PR introduce a user-facing change?:
NONE

Relevant deploy preview link: https://deploy-preview-650--kubernetes-sigs-gateway-api.netlify.app/contributing/community/

/lgtm
/approve


bump google.golang.org/grpc to v1.62.1 and google.golang.org/protobuf to v1.33.0

What does this PR do?
This PR bumps the grpc and protobuf dependencies to latest version
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Include Python 3.8 support

In tox.ini
In .travis.yml
In setup.py
Throughout the docs wherever other versions are mentioned
Anywhere else that should be included

appveyor/ci #3142

🚀 Python 3.8 is now available on AppVeyor:

https://github.com/appveyor/ci/issues/3142#issuecomment-552049896

Found 2 other places 3.8 needed to be added so included this as a part of PR https://github.com/audreyr/cookiecutter-pypackage/pull/543


HDDS-11872. Disable Apache snapshots repo

What changes were proposed in this pull request?
CI build sometimes times out fetching information from snapshot repository, e.g.:
[INFO] --- cyclonedx-maven-plugin:2.9.1:makeAggregateBom (default) @ ozone-main ---
[INFO] CycloneDX: Resolving Aggregated Dependencies
[WARNING] Could not transfer metadata org.apache.ozone:hdds-interface-client:2.0.0-SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): transfer failed for https://repository.apache.org/content/repositories/snapshots/org/apache/ozone/hdds-interface-client/2.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] org.apache.ozone:hdds-interface-client:2.0.0-SNAPSHOT/maven-metadata.xmlfailed to transfer from https://repository.apache.org/content/repositories/snapshots during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of apache.snapshots.https has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.ozone:hdds-interface-client:2.0.0-SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): transfer failed for https://repository.apache.org/content/repositories/snapshots/org/apache/ozone/hdds-interface-client/2.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] org.apache.ozone:hdds-interface-client:2.0.0-SNAPSHOT/maven-metadata.xmlfailed to transfer from https://repository.apache.org/content/repositories/snapshots during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of apache.snapshots.https has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.ozone:hdds-interface-client:2.0.0-SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): transfer failed for https://repository.apache.org/content/repositories/snapshots/org/apache/ozone/hdds-interface-client/2.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata org.apache.ozone:hdds-hadoop-dependency-test:2.0.0-SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): transfer failed for https://repository.apache.org/content/repositories/snapshots/org/apache/ozone/hdds-hadoop-dependency-test/2.0.0-SNAPSHOT/maven-metadata.xml
...

Ozone does not use snapshot dependencies.  The only snapshot artifacts are Ozone's own modules, which are created by the build, not available from from remote Maven repositories.
Snapshot repo usage was inherited from Hadoop, which does (used to?) publish snapshot artifacts (MAPREDUCE-3003).
So I propose disabling snapshots.
https://issues.apache.org/jira/browse/HDDS-11872
How was this patch tested?
First removed all Ozone snapshot artifacts from local Maven repo:
find ~/.m2/repository/org/apache/ozone -name '*SNAPSHOT*' | xargs rm -fr

Tried to build some Ozone module without its dependencies.  Maven failed as expected, but did not mention remote repositories (apache.snapshots...), and did not save any information about update attempts to local repo:
$ mvn -pl :hdds-common -DskipTests clean package
...
[ERROR] Failed to execute goal on project hdds-common: Could not resolve dependencies for project org.apache.ozone:hdds-common:jar:2.0.0-SNAPSHOT: The following artifacts could not be resolved: org.apache.ozone:hdds-hadoop-dependency-client:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-annotation-processing:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-config:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-interface-client:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-interface-admin:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-hadoop-dependency-test:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-test-utils:jar:2.0.0-SNAPSHOT: Could not find artifact org.apache.ozone:hdds-hadoop-dependency-client:jar:2.0.0-SNAPSHOT
...
[INFO] Total time:  0.714 s

$ find ~/.m2/repository/org/apache/ozone -name '*SNAPSHOT*' | wc -l
0

$ mvn -pl :ozone-manager -DskipTests clean package
...
[ERROR] Failed to execute goal on project ozone-manager: Could not resolve dependencies for project org.apache.ozone:ozone-manager:jar:2.0.0-SNAPSHOT: The following artifacts could not be resolved: org.apache.ozone:hdds-annotation-processing:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-client:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-common:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-config:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-interface-server:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-managed-rocksdb:jar:2.0.0-SNAPSHOT, org.apache.ozone:ozone-interface-client:jar:2.0.0-SNAPSHOT, org.apache.ozone:ozone-common:jar:2.0.0-SNAPSHOT, org.apache.ozone:ozone-client:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-docs:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-interface-client:jar:2.0.0-SNAPSHOT, org.apache.ozone:ozone-interface-storage:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-server-framework:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-hadoop-dependency-server:jar:2.0.0-SNAPSHOT, org.apache.ozone:rocksdb-checkpoint-differ:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-rocks-native:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-common:jar:tests:2.0.0-SNAPSHOT, org.apache.ozone:hdds-hadoop-dependency-test:jar:2.0.0-SNAPSHOT, org.apache.ozone:hdds-server-scm:jar:tests:2.0.0-SNAPSHOT, org.apache.ozone:hdds-test-utils:jar:2.0.0-SNAPSHOT: Could not find artifact org.apache.ozone:hdds-annotation-processing:jar:2.0.0-SNAPSHOT
...
[INFO] Total time:  1.834 s

$ find ~/.m2/repository/org/apache/ozone -name '*SNAPSHOT*' | wc -l
0

For reference, failure in same case on master (with "normal" download speed):
$ mvn -pl :ozone-manager -DskipTests clean package
...
[ERROR] ... Could not find artifact org.apache.ozone:hdds-annotation-processing:jar:2.0.0-SNAPSHOT in apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots)
...
[INFO] Total time:  5.697 s

$ find ~/.m2/repository/org/apache/ozone -name '*SNAPSHOT*' | wc -l
58

CI:
https://github.com/adoroszlai/ozone/actions/runs/12202358564

Found that cyclonedx-maven-plugin is downloading from repository.apache.org even if our POM has not defined and/or disabled these repos.

Tested with:
mvn --batch-mode -Pdist -Drocks_tools_native eu.maveniverse.maven.plugins:toolbox:list-repositories

On master:
$ grep 'repository.apache.org.*snapshot' HDDS-11872-master.txt | sort -u
[INFO]  * apache.snapshots (http://repository.apache.org/snapshots, default, snapshots)
[INFO]  * apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots, default, releases+snapshots)
[INFO]  * apache.snapshots (https://repository.apache.org/content/repositories/snapshots/, default, snapshots)
[INFO]  * apache.snapshots (https://repository.apache.org/snapshots, default, snapshots)

With the fix, all repository.apache.org snaphots are disabled:
$ grep 'repository.apache.org.*snapshot' HDDS-11872-patch.txt | sort -u
[INFO]  * apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots, default, disabled)
[INFO]  * apache.snapshots (https://repository.apache.org/snapshots, default, disabled)


⚠ Bofrost.at has degraded performance

In c27cb3c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1345 ms

Resolved: Bofrost.at performance has improved in e7be95b after 6 minutes.


Added emojies, lines diff checker, app name

Problem solved:

added emojies to highlight comment with red/green colour for diff
added possibility to show details only for changed lines , please note, that this will work only if you have base lcov file, if not previous code will work without changes
added possibility to add app-name (needed mostly for singe repo with diff siblings)

Looks great again, I've seen it in action :)

I already have some improvements ideas, how to show only changed lines without having a base file. :)


How to call something like Powershell from the CLR?

This library seems amazing, I would like to know how (if possible) I can use it to:
• Load the System.Management.Automation library.
• Create a runspace and invoke powershell commands/scripts

I have no experience with System.Management.Automation, but in principle you should be able to do basically everything you can do in a normal .NET program.

I think the easiest solution is to write a library youself that then uses the Microsoft library.

@OpenByteDev I did but I can't dynamically link it(?) Without touching the disk

I dont know if there is an API for manual dll loading, but if there is it is currently not covered by this crate.

Ok then, thank you.


REST API for profile

Story #3 Profile
Sub-Tasks:

[x] Get player GET /players/{playerId}
[x] Edit player PUT /players/{playerId}
[x] Constraint editing profiles of other players
[x] Error exceptions and messages

Estimate: 2h

b9c31e0182a2090ff5054988b970e7666980b3f4

425c63759ff4f33647d9fb83e6d0233b1e7b8264


Fix keypress rebinding

Fixed bug: https://github.com/excalidraw/excalidraw/issues/2074

Works great, thanks!


CI containerd-integration-tests FAIL

https://github.com/containers/youki/actions/runs/4070667793/jobs/7012040270
    container_test.go:717: runc did not terminate successfully: exit status 1: [ERROR crates/youki/src/main.rs:138] 2023-02-02T03:01:24.333744089+00:00 error in executing command: failed to delete container TestKillContainerDeletedByRunc

        Caused by:
            0: failed to remove cgroup /testing/TestKillContainerDeletedByRunc
            1: could not delete "/sys/fs/cgroup/testing/TestKillContainerDeletedByRunc"
        Error: failed to delete container TestKillContainerDeletedByRunc

        Caused by:
            0: failed to remove cgroup /testing/TestKillContainerDeletedByRunc
            1: could not delete "/sys/fs/cgroup/testing/TestKillContainerDeletedByRunc"

--- FAIL: TestKillContainerDeletedByRunc (0.44s)

@lengrongfu Thanks for your report :heart_eyes:

I think we have to check the following things:

Verify if this error can reproduce local or VirtualBox
Make sure that runc doesn't happen this error

Verify in the centos runc not fail.

containerd

[root@localhost containerd]# ./bin/containerd -h
NAME:
   containerd -
                    __        _                     __
  _________  ____  / /_____ _(_)___  ___  _________/ /
 / ___/ __ \/ __ \/ __/ __ `/ / __ \/ _ \/ ___/ __  /
/ /__/ /_/ / / / / /_/ /_/ / / / / /  __/ /  / /_/ /
\___/\____/_/ /_/\__/\__,_/_/_/ /_/\___/_/   \__,_/

high performance container runtime

USAGE:
   containerd [global options] command [command options] [arguments...]

VERSION:
   v1.7.0-beta.3-50-g3d32da8f6

Verify in the centos runc not fail.

containerd

[root@localhost containerd]# ./bin/containerd -h
NAME:
   containerd -
                    __        _                     __
  _________  ____  / /_____ _(_)___  ___  _________/ /
 / ___/ __ \/ __ \/ __/ __ `/ / __ \/ _ \/ ___/ __  /
/ /__/ /_/ / / / / /_/ /_/ / / / / /  __/ /  / /_/ /
\___/\____/_/ /_/\__/\__,_/_/_/ /_/\___/_/   \__,_/

high performance container runtime

USAGE:
   containerd [global options] command [command options] [arguments...]

VERSION:
   v1.7.0-beta.3-50-g3d32da8f6


docs: rework documentation

This PR reworks the documentation of the codebase as a whole. The aim is to:

Instil as much confidence as possible in the reader to use this module.
Clarify any concerns regarding the inner workings of this module.

A review of all documentation after the merge would be much appreciated, @kt3k and @lino-levan.

The CI failure on macOS 12 is unrelated to this change, as other PRs failed the same way before this was merged. This issue will be tackled in #87.

Nice!

Nice docs!


iBooks compatibility

Hi,
Thanks for the lib, great work 👍
I'd like to access my documents stored in iBooks to retrieve their own path. My goal is to access saved pdf on the device and being able to upload them from my app to my server using react-native-fetch-blob.
Does this lib support iBooks files ? Any restrictions from Apple ?
Thanks ;)

I'm pretty sure you are not allowed to access your iBooks content from React native nor Objective-C See: https://www.quora.com/IOS-development-Is-it-possible-to-access-iBooks-from-an-app


Altering the page size of an existing database

Is there an (offline) mechanism for translating an existing database file from one page size to another?

This is not easily possible today.  The very ugly workaround is this:

xcopy esent.dll to esent-alt.dll.
LoadLibrary( "esent-alt.dll" )
Fetch only the functions you need to set page size param and read data.
Set old page size in esent-alt.dll.
Set new page size normally (implicitly against esent.dll that loaded automatically)
Read data out of originaly DB attached to esent-alt.dll, and insert it into a newly created DB with the implicit esent.dll.

Hope that made sense.
BrettSh [MSFT]

This is not easily possible today.  The very ugly workaround is this:

xcopy esent.dll to esent-alt.dll.
LoadLibrary( "esent-alt.dll" )
Fetch only the functions you need to set page size param and read data.
Set old page size in esent-alt.dll.
Set new page size normally (implicitly against esent.dll that loaded automatically)
Read data out of originaly DB attached to esent-alt.dll, and insert it into a newly created DB with the implicit esent.dll.

Hope that made sense.
BrettSh [MSFT]


Call to undefined method FFMpeg\Media\Frame::frame()

I get this error message if I try to run the 'getFrameFromSeconds' method more than once on the media object. It seems that the assignment $this->media could cause this issue. If you try to open the file in the for loop anew for every iteration you will get the same error message (maybe this happens because of caching?). This is even true, if you create multiple copies of the .mp4 file and open each and every one separately. After the first run you get the above stated message. I was trying to make a timelapse and for this I need some frames from the video, am I using the wrong method?
This is the loop (this is the version where it opens separate files):
for ($i = 1; $i < 4; $i++){
                $y++;
                FFMpeg::fromDisk('videos')
                    ->open($y.$videoNameToStore)
                    ->getFrameFromSeconds($i)
                    ->export()
                    ->toDisk('thumbnails')
                    ->save($i.$thumbnailNameToStore);
}

I'm using PHP 7.2.24-0ubuntu<IP_ADDRESS>
Stack Trace:
ProtoneMedia\LaravelFFMpeg\Drivers\PHPFFMpeg::frame
vendor/pbmedia/laravel-ffmpeg/src/Drivers/PHPFFMpeg.php:113

        $this->mediaCollection = $mediaCollection;

        $localPaths = $mediaCollection->getLocalPaths();

        if (count($localPaths) === 1 && !$this->forceAdvanced) {

            $this->media = $this->ffmpeg->open(Arr::first($localPaths));

        } else {

            $this->media = $this->ffmpeg->openAdvanced($localPaths);

        }

        return $this;

    }

    public function frame(TimeCode $timecode)

    {

        $this->media = $this->media->frame($timecode); //->this is the place where it happens!

        return $this;

    }

    public function concatWithoutTranscoding()

    {

        $localPaths = $this->mediaCollection->getLocalPaths();

        $this->media = $this->ffmpeg->open(Arr::first($localPaths))

            ->concat($localPaths);

        return $this;

    }

    /**

Did you update to the latest version? I released a patch yesterday and I think it fixes this issue as well.

@pascalbaljet you are right, updating to the latest version makes it possible to run the code if you duplicate the file and open separate files to get frames from them. Though if I revert the my code to what it was before:
$media = FFMpeg::fromDisk('videos')->open($videoNameToStore);
            $durationInSeconds = $media->getDurationInSeconds();

            for ($i = 1; $i < $durationInSeconds; $i+=5){
                $media->getFrameFromSeconds($i)
                    ->export()
                    ->toDisk('thumbnails')
                    ->save($i.$thumbnailNameToStore);
            }

I get this error message:
Opened media is not a video file.
And again the first iteration of the loop passes without a problem. The second though cannot be executed due to the above stated error message.
Stack trace:
ProtoneMedia\LaravelFFMpeg\Drivers\PHPFFMpeg::frame
vendor/pbmedia/laravel-ffmpeg/src/Drivers/PHPFFMpeg.php:125

        $localPaths = $mediaCollection->getLocalPaths();

        if (count($localPaths) === 1 && !$this->forceAdvanced) {

            $this->media = $this->ffmpeg->open(Arr::first($localPaths));

        } else {

            $this->media = $this->ffmpeg->openAdvanced($localPaths);

        }

        return $this;

    }

    public function frame(TimeCode $timecode)

    {

        if (!$this->isVideo()) {

            throw new Exception('Opened media is not a video file.');

        }

        $this->media = $this->media->frame($timecode);

        return $this;

    }

    public function concatWithoutTranscoding()

    {

        $localPaths = $this->mediaCollection->getLocalPaths();

        $this->media = $this->ffmpeg->open(Arr::first($localPaths))

            ->concat($localPaths);

        return $this;

If I reopen the file in every iteration it works though. Would you consider this issue than solved?

You need to leverage the save method of the exporter to get a fresh instance of the MediaOpener.
$mediaOpener = FFMpeg::open('video.mp4');

foreach ([5, 15, 25] as $key => $seconds) {
    $mediaOpener = $mediaOpener->getFrameFromSeconds($seconds)
        ->export()
        ->save("thumb_{$key}.png");
}

I've added an each method to the MediaOpener to simplify this a bit more. Currently, the tests are running. Once they're completed I'll tag v7.0.4.
FFMpeg::open('video.mp4')->each([5, 15, 25], function ($ffmpeg, $seconds, $key) {
    $ffmpeg->getFrameFromSeconds($seconds)->export()->save("thumb_{$key}.png");
});

v7.0.4 has been tagged, also added to the docs


Only Download Newest Chapters

Is there a flag that will allow us to only download the newest "n" chapters?
I would like to run this script automatically once a week, and download the newest, say 5, chapters from each release I'm following. Right now I only see how to download a set number range which wouldn't work as you need to know the chapter number and change it each time.

Main point of this would be to avoid hitting every file on a large series each time, otherwise I'd just run it open

Main point of this would be to avoid hitting every file on a large series each time, otherwise I'd just run it open

Did you mean, avoid "checking every file if it's exist or not " ?
i'm pretty sure the application can check if the chapters is exist or not, if exists then it would be simply skipped (unless you're using raw format, it would be verify each images and has higher chance to get rate limited).

Main point of this would be to avoid hitting every file on a large series each time, otherwise I'd just run it open

Did you mean, avoid "checking every file if it's exist or not " ?
i'm pretty sure the application can check if the chapters is exist or not, if exists then it would be simply skipped (unless you're using raw format, it would be verify each images and has higher chance to get rate limited).

Sorry, you're correct. I think i was on an old version that checked each file, but since updating it only checks that the volume is downloaded so all good.


td-chip's handleAdd and handleRemove functions doesn't call when selecting a chip that was already selected

Bug Report
td-chip's handleAdd and handleRemove functions doesn't call when selecting a chip that was already selected.
What is the expected behavior?
I would expect handleAdd and handleRemove to be fire each time the chips is selected.
if a user clicks any ui element, I think you would like to know it. (for statistics reports, or for any other implementations)
What is the motivation / use case for changing the behavior?
For example, I would like to set a chip, with how many times it was selected from the dropdown list, something that will be shown like this:
stepper(3 times) expension-panel(1 time)
Which version of Angular and Material, and which browser and OS does this issue affect?
angular: 4.4
covalent: 1.0.0-beta.8
Did this work in previous versions of Angular / Material?
No.

closing as duplicate of #711


Consume new binding.json with parametername setting

Related to https://github.com/Azure/azure-webjobs-sdk-templates/issues/159

This will need to be coordinated with Naren to make sure we ship the bindings.json changes before we ship the new portal update.


1.3.6: Reactivity not working properly and more

Hi,
I am using Angular Meteor quite extensively in the current building of a prototype for a financial company.
During development I ran into a couple of issues, which have been addressed quickly by Urigo ( many thanks for that).
But still I think some things of the new API are not working 100% and I am running into issue which cost me a lot of time to track down or work around.
Just for the sake of reporting, I am going to list them down here. Please feel free to respond or give constructive feedback on how to better do it, if it is not a bug.
edit: Actually it is one big story holding probably multiple issues but mainly it is related to reactivity.
* 1) Reactivity with an object: not autorunning after setting of new value*
I have a simple sort scenario where I have a list of invoices and I have a header with columns. Clicking on the columns need to trigger a sort. For this I created a directive that will capture the click on a specific column and update the scope value of sortColumns in the main dashboardController (which holds the invoice list subscription).
This scope value is the one that should be watched.
  updateSort( sortValue: any ): void {

    console.log( "updating sort", sortValue);
    this.sortColumns.__currentColumn  = sortValue;
    this.sortColumns[ sortValue ]     = 1;
    this.$scope.$digest();
  }

In BLAZE, I would create a ReactiveVar and that would be it. But unfortunately in Angular I need to watch this variable change somewhere.
Because I want to filter on my subscription, a template Helper would make sense to me.
I create a helper invoices, which will just return a Find() on the invoices subscription.
In the helper I add
trigger = this.getReactively( 'sortColumns'.__currentColumn );
sort =  angular.copy( this.sortColumns );
delete sort.__currentColumn;
return Invoices.find( {}, { sort: sort } );

The updateSort function is the one I call from the directive because directly accessing the sortColumns object and updating did not result in a reactive update in Autorun OR the helper.
However, just updating the object with new key/values did not work either, because watching sortColumns alone did not result in a reactive update.
Only looking specifically looking at sortColumns.__currentColumn and updating this property only to trigger the update seems to work.
So I have to remove the property in my sort object so that I can pass the sort object directly to the Mongo Find().
With the $digest call, I wouldn't get the update of my sortColumns. Why is this necessary?
Expected behaviour:
If I update the object, with whatever content and I am watching the object and not a specific property, I expect a reactive Update, right?
2) Updating controller variable directly from directive not triggering reactive update
So I used the updateSort function in the first reported issue, but at first I wanted to directly update that value from the directive. I gave the directive an isolated scope but I assume the value in the directive is always a copy of the value from the controller. So Autorun or ReactiveContext would never watch that copy. So I called a function that updates the value IN the controller.
This does make sense, so maybe not a bug but I want to validate if this is the best way.
3) Running in a $digest error
When I try to set the initial sorting from my column directive I do it like this: By giving on column a attribute direction="desc" and while looping through my columns I look at the one that has a direction attribute and then call the updateSort function with the correct column in my dashboardController.
On first page run, I get a $digest is already running error. I intentionally call the $digest function in my updateSort to make sure during runtime, when a user clicks on the column, a reactive update takes place.
I guess this issue is related to the above mentioned reactive issues and I could remove $digest in the future.
4) Subscription stopped issue
I still run into the subscription stopped issue once in a while. Especially during my issues with the sorting directive, on application auto reload by Meteor I see an empty invoice list. Then reloading by clicking in the address bar and hitting enter a several times work. Or go to another view and go back always seem to work. Not sure what triggers this issue.
5) Helper reactive reRun returns empty collection for a instant and then normal collection
I have a helper in my DashboardController that returns all invoices. As mentioned above, I have a reactive Sort object. When I do sort, the helper does a return of Invoices.find( selector, { sort: sort } );
This would renew the invoices in my template which it does.
However, there is an instant where the results flicker from an empty collection to a full collection. When I console.log the invoices with sort and filter
        console.log( "length", Invoices.find( selector, { sort: sort } ).fetch().length);
        return Invoices.find( selector, { sort: sort } );

it always shows 27, when I sort like a madman.
However when I print the same collection length in my template, the result goes from [] to 27 in an instant.This triggers a flickering effect of my 'There are no invoices in your account' to the list of invoices.
Is this something that can be prevented? Only return the helper collection to the template when it's done and not empty?
Of course it doesn't always do it. When I click on 3 columns to sort, it might happen at the third one...
Summary: It took me most of the day to figure out how to get this working and in the end it still feels like a hack. And some fixes trigger errors in other situations, like described in issue 3.
I think it would be nice to make a bigger list of examples for all kind of scenario's with ReactiveContext, Helpers etc.. That way people can safe time and we are sure noone is hacking the system.

I had similar issues in a fairly large project with angular-meteor. I eventually had to give up or take some quite hacky routes to get things to work and I'm still not sure why my eventual solution worked. I'd be keen to see or work on some meteor pen's that can accurately reproduce these bugs.

I'm running into a similar problem as described in 4) Subscription stopped issue.
Basically, in the page immediately after login, my collection that should have one item after the subscription has none. If I refresh the page, everything goes back to normal.

I'm with 1.3.7 and got the same problem as described in 4

@plraphael No, your comment is not irrelevant. I reckon version 1.3.6 and version 1.3.7 shared much code and it is important to know if an issue is still relevant for an even newer version.

thank you for those reports.
It will be great if you could reproduce a separate isolated repo with the problem.
It can help me solve it and help you isolate and understand it

also, just to make sure, please check your code while doing deep watch in getReactively instead of regular by providing true to the objectEquality parameter - http://www.angular-meteor.com/api/1.3.6/get-reactively#arguments

Mate,
I am just testing with 1.3.7 on my girlfriends macbook (I didn't want to upgrade on my production macbook just yet).
I checked all items that I posted above and how they work at this version.
** 1) Reactivity with an object: not autorunning after setting of new value**
This still seems to be an issue, unless I am not using it correctly.
The code below has the updateSort function triggered by a directive and provides a value like { column: 'Total', direction: 'desc' }.
This is set in the private variable sortColumns which is being watched (the whole variable).
 this.helpers( {

  invoices: () => {
    var sort;

    // this is purely to make sortColumns reactive
    //
    sort = this.getReactively( 'sortColumns' );
    return Invoices.find( {}}, { sort: sort } );
  }
} );

updateSort( sort: any ): void {

   this.sortColumns[ sort.column ]  = sort.direction === 'desc' ? -1 : 1;
  this.$scope.$digest(); // still necessary to make the reactive update work
 }

Updating the object with another key doesn't trigger the watch on the object itself. Maybe this is because that is not how the watch should work. However with Meteor Blaze ReactiveVar (if I am remembering correctly) it DOES work.
I only get the situation working if I add  this.sortColyms = {} to the updateSort function and reset the object on each column order. That works but feels like a hack if the reactivity should work on an object.
The $DIGEST is still necessary. Other wise the Helper will not reRun.

@mattiLeBlanc it looks like you haven't read my comment.

Please check your code while doing deep watch in getReactively instead of regular by providing true to the objectEquality parameter - http://www.angular-meteor.com/api/1.3.6/get-reactively#arguments

Please provide a separate repo with a reproduction

If you haven't found the time to share a reproduction it will be hard for me to find the time to solve the problem

@Urigo Yes, I did but I was just in the process of writing a report :). I have updated my findings in the above post and I have emailed you about access to the repo.

@mattiLeBlanc I'm happy the deep watch parameter solved one of your issues.
@sean-stanley @plraphael @ThomsC did it solve yours as well?
About the second problem - private repo won't help me.   If you haven't found the time to go into your code and isolate the problem, it's not a good idea that I will go into your private code, try to isolate your business logic with the problem and share a reproduction.
Please go into your code and isolate the problem.
I hope you understand my logic and it makes sense.  I want to help you solve the problem.
About the digest thing, something I would start with if I had a reproduction is if it's an Angular or Angular-Meteor problem.
I would put a regular Angular $watch on sortColumns and see if it fires

@Urigo
What if the problem is that it doesn't happen in an isolated situation? Maybe something breaks, timing issues etc because it starts to grow? I am happy to try to isolate it, just thought it would be easier if I give you access to the full app and tell you where to look.
I will try your watch, however if the updateRow function is executed (which it is, I consoled logged it and it does update the this.sortColumn object, the Helper doesn't fire unless I call a $digest, wouldn't it the issue be the combination of Angular and Meteor?

not for sure because $digest just call the Angular's digest loop so the question is why Angular doesn't fire it by itself when you change a scope variable

@Urigo, rather than using a deep watch I watched the individual parameters e.g. getReactively('object.property') and that implementation works well and I like.
My problem couldn't be well isolated as it only happened when I was logging in, then changing routes in Meteor.call's callback. The auth service would then from ng-if call the link function of a custom directive that had a subscribe call. If I remove the subscribe call in the directive everything worked fine and my subscriptions in the new route weren't stopped. I fixed that particular issue by wrapping my route change in a 10ms $timeout. hacky but no noticable UI problems at least.
That said if you really want I can try to reproduce it in an as isolated event as possible.
I am using angular 1.5 component syntax for parts of my app if that matters at all.

@sean-stanley I might know your problem, have you tried this.call? http://www.angular-meteor.com/api/1.3.6/call
this will wrap the callback in a digestion cycle.
Then also, if it's something else from Meteor that is outside of Angular's scope, you can use $bindToContext - http://www.angular-meteor.com/api/1.3.6/reactive-context#dbindtocontext
(scroll down for an example)

also, make sure you are using the angular-meteor-auth package as a separate package and in the latest version 0.2.1

@urigo thanks for the tip about this.call it seems like that would be part of the issue you're right. I guess I missed that part of the docs I'll make that change now.
I do use $auth as a seperate package. That was a good decision breaking it up I think and I've had no problems switching from the old to new api for that except sometimes it's unclear in a controller when to use $auth.currentUser or just plain ole Meteor.user() but that's probably a discussion for another place and another time.

@Urigo
I have removed everything that is not relevant and the result you can get from here:
https://github.com/mattiLeBlanc/invoiceList
So, I am not seeing the publication stop issue right now. The reason could be that I removed the user and the ui-router resolve of currentUser.
I will add that in now into a different branch so that I can test if I can get this issue to be reproduced too.
I have added the issues in the readme file in the repo.
Hope you can have a look and find the same results.

For me the publication stop issue seems to be resolve when I use :
resolve: {
                    currentUser: ($q) => {
                        if (Meteor.userId() == null)
                            return $q.reject('AUTH_REQUIRED');
                        if (Roles.userIsInRole(Meteor.userId(), ['user', 'sub-user']))
                            return $q.resolve();
                        else {
                            return $q.reject('AUTH_REQUIRED');
                        }
                    }
                }

Instead of
$auth.requireUser()

Let me explain what is happening in my case.
After a successful login, the user is redirected to a page with a subscription. A normal subscription, that does not have any parameters (hence, does not use getReactively). What I'm getting on my logs is that the subscription gets "ready" and after some time, gets "stopped". If I refresh the page, the subscription does not get stopped, and everything is fine.
I tried what @ThomsCass suggested, but got the same result.

can we see your resolve function and the part of the controller where you do the subscription with the helpers?

Just a hint on issue 4 with subscriptions stopping. I noticed that this happened to me when Meteor.user() return undefined for some short time before (I assume) the Meteor.users collection is populated. By installing the fastrender package the logged in users is always available which seemed to solve the problem. Not sure why, but it also made the routing with the ui router stop functioning.

@mattiLeBlanc Can we catch up on hangouts or something? I'm currently working on these issues.

@kamilkisiela I have send you an email (the the email address in your git account).
I have also added a 6th helper reactivity issue about a helper not updating after mongo document change.

@mattiLeBlanc could you please update about the current situation of the issues you specified?
thanks

These issue have all been resolved.

Hi there,
are there still people using angular-meteor?
I started a project and ran into the same issues as you guys.
Thank you @mattiLeBlanc for posting the github repo invoiceList, but in the readme also questions arose.
Anyone on this right now?
(I am utilizing angular-meteor 1.3.11)

Hi,
This thread was created 6 months ago or so and i must say that most issue
where resolved. Some were related to architecture and some were bugs.
Which issues are you running into right now?
On Thu, 19 Jan 2017 at 10:05 pm, der-ede<EMAIL_ADDRESS>wrote:

Hi there,
are there still people using angular-meteor?
I started a project and ran into the same issues as you guys.
Thank you @mattiLeBlanc https://github.com/mattiLeBlanc for posting the
github repo invoiceList, but in the readme also questions arose.
Anyone on this right now?
(I am utilizing angular-meteor 1.3.11)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-273746554,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFCkqzImzDg_ca2LJDMM5-mFszyf8OiGks5rT0N7gaJpZM4HqiQC
.

Hi @Matti LeBlanc,
thank you for responding.
The issue of the reactivity not functioning properly almost subsided in the meantime when I played around with the resolve a bit.
But sometimes it still just does not get the changes in $scope.helpers({}), although no „deep“ reactivity.
But also in general I was wondering whether the whole angular-meteor project is obsolete and gone.
Explanation:
Over the past 1 1/2 years or so I accompanied some projects with meteor and the question of the ui-framework was just costly since it changed a lot, from fame.us to meteoric-ionic to angular-meteor and now everyone seems to be wanting react.
So angular-meteor is still maintained and will be in the future?
Regards
Thorsten

Am 20.01.2017 um 14:25 schrieb Matti LeBlanc<EMAIL_ADDRESS>Hi,
This thread was created 6 months ago or so and i must say that most issue
where resolved. Some were related to architecture and some were bugs.
Which issues are you running into right now?
On Thu, 19 Jan 2017 at 10:05 pm, der-ede<EMAIL_ADDRESS>wrote:

Hi there,
are there still people using angular-meteor?
I started a project and ran into the same issues as you guys.
Thank you @mattiLeBlanc https://github.com/mattiLeBlanc for posting the
github repo invoiceList, but in the readme also questions arose.
Anyone on this right now?
(I am utilizing angular-meteor 1.3.11)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-273746554,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFCkqzImzDg_ca2LJDMM5-mFszyf8OiGks5rT0N7gaJpZM4HqiQC
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274071402, or mute the thread https://github.com/notifications/unsubscribe-auth/AHwdR3L3BN91miLXjlrKqke4EcXr2ZJ9ks5rULXTgaJpZM4HqiQC.

Well looping at the code base it is still actively being maintained.
There must be a lot of people considering angular 2 , react or Vue over
angular 1.5 so I guess eventually it will become stale.
Not saying you can't keep using it as long as you freeze your code base at
work.
For now I think it is still fine and allows for rapid development
especially with angulars 1.5 components.
On Sat, 21 Jan 2017 at 12:56 am, der-ede<EMAIL_ADDRESS>wrote:

Hi @Matti LeBlanc,
thank you for responding.
The issue of the reactivity not functioning properly almost subsided in
the meantime when I played around with the resolve a bit.
But sometimes it still just does not get the changes in
$scope.helpers({}), although no „deep“ reactivity.
But also in general I was wondering whether the whole angular-meteor
project is obsolete and gone.
Explanation:
Over the past 1 1/2 years or so I accompanied some projects with meteor
and the question of the ui-framework was just costly since it changed a
lot, from fame.us to meteoric-ionic to angular-meteor and now everyone
seems to be wanting react.
So angular-meteor is still maintained and will be in the future?
Regards
Thorsten

Am 20.01.2017 um 14:25 schrieb Matti LeBlanc<EMAIL_ADDRESS>

Hi,

This thread was created 6 months ago or so and i must say that most issue

where resolved. Some were related to architecture and some were bugs.

Which issues are you running into right now?

On Thu, 19 Jan 2017 at 10:05 pm, der-ede<EMAIL_ADDRESS>wrote:

Hi there,

are there still people using angular-meteor?

I started a project and ran into the same issues as you guys.

Thank you @mattiLeBlanc https://github.com/mattiLeBlanc for posting
the

github repo invoiceList, but in the readme also questions arose.

Anyone on this right now?

(I am utilizing angular-meteor 1.3.11)

—

You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub

<
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-273746554
,

or mute the thread

<
https://github.com/notifications/unsubscribe-auth/AFCkqzImzDg_ca2LJDMM5-mFszyf8OiGks5rT0N7gaJpZM4HqiQC

.

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub <
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274071402>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/AHwdR3L3BN91miLXjlrKqke4EcXr2ZJ9ks5rULXTgaJpZM4HqiQC
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274077483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFCkq5gk-9C-_6VNAjwmgf1d0HYt914Hks5rUL0KgaJpZM4HqiQC
.

Ok thank you, in js 2 years has become one whole generation...

Am 21.01.2017 um 00:41 schrieb Matti LeBlanc<EMAIL_ADDRESS>Well looping at the code base it is still actively being maintained.
There must be a lot of people considering angular 2 , react or Vue over
angular 1.5 so I guess eventually it will become stale.
Not saying you can't keep using it as long as you freeze your code base at
work.
For now I think it is still fine and allows for rapid development
especially with angulars 1.5 components.
On Sat, 21 Jan 2017 at 12:56 am, der-ede<EMAIL_ADDRESS>wrote:

Hi @Matti LeBlanc,
thank you for responding.
The issue of the reactivity not functioning properly almost subsided in
the meantime when I played around with the resolve a bit.
But sometimes it still just does not get the changes in
$scope.helpers({}), although no „deep“ reactivity.
But also in general I was wondering whether the whole angular-meteor
project is obsolete and gone.
Explanation:
Over the past 1 1/2 years or so I accompanied some projects with meteor
and the question of the ui-framework was just costly since it changed a
lot, from fame.us to meteoric-ionic to angular-meteor and now everyone
seems to be wanting react.
So angular-meteor is still maintained and will be in the future?
Regards
Thorsten

Am 20.01.2017 um 14:25 schrieb Matti LeBlanc<EMAIL_ADDRESS>

Hi,

This thread was created 6 months ago or so and i must say that most issue

where resolved. Some were related to architecture and some were bugs.

Which issues are you running into right now?

On Thu, 19 Jan 2017 at 10:05 pm, der-ede<EMAIL_ADDRESS>wrote:

Hi there,

are there still people using angular-meteor?

I started a project and ran into the same issues as you guys.

Thank you @mattiLeBlanc https://github.com/mattiLeBlanc for posting
the

github repo invoiceList, but in the readme also questions arose.

Anyone on this right now?

(I am utilizing angular-meteor 1.3.11)

—

You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub

<
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-273746554
,

or mute the thread

<
https://github.com/notifications/unsubscribe-auth/AFCkqzImzDg_ca2LJDMM5-mFszyf8OiGks5rT0N7gaJpZM4HqiQC

.

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub <
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274071402>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/AHwdR3L3BN91miLXjlrKqke4EcXr2ZJ9ks5rULXTgaJpZM4HqiQC
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274077483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFCkq5gk-9C-_6VNAjwmgf1d0HYt914Hks5rUL0KgaJpZM4HqiQC
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274209131, or mute the thread https://github.com/notifications/unsubscribe-auth/AHwdR1ldfOxQmahZTD9iUqyoQqWHwNyDks5rUUY5gaJpZM4HqiQC.

So, just to make sure:
In the helpers, I have to use find() instead of findOne(), since only find() will be treated reactively, right?
And in terms of getreactively: any variable can be made reactive, also variables from services for example?
Regards

Am 21.01.2017 um 00:41 schrieb Matti LeBlanc<EMAIL_ADDRESS>Well looping at the code base it is still actively being maintained.
There must be a lot of people considering angular 2 , react or Vue over
angular 1.5 so I guess eventually it will become stale.
Not saying you can't keep using it as long as you freeze your code base at
work.
For now I think it is still fine and allows for rapid development
especially with angulars 1.5 components.
On Sat, 21 Jan 2017 at 12:56 am, der-ede<EMAIL_ADDRESS>wrote:

Hi @Matti LeBlanc,
thank you for responding.
The issue of the reactivity not functioning properly almost subsided in
the meantime when I played around with the resolve a bit.
But sometimes it still just does not get the changes in
$scope.helpers({}), although no „deep“ reactivity.
But also in general I was wondering whether the whole angular-meteor
project is obsolete and gone.
Explanation:
Over the past 1 1/2 years or so I accompanied some projects with meteor
and the question of the ui-framework was just costly since it changed a
lot, from fame.us to meteoric-ionic to angular-meteor and now everyone
seems to be wanting react.
So angular-meteor is still maintained and will be in the future?
Regards
Thorsten

Am 20.01.2017 um 14:25 schrieb Matti LeBlanc<EMAIL_ADDRESS>

Hi,

This thread was created 6 months ago or so and i must say that most issue

where resolved. Some were related to architecture and some were bugs.

Which issues are you running into right now?

On Thu, 19 Jan 2017 at 10:05 pm, der-ede<EMAIL_ADDRESS>wrote:

Hi there,

are there still people using angular-meteor?

I started a project and ran into the same issues as you guys.

Thank you @mattiLeBlanc https://github.com/mattiLeBlanc for posting
the

github repo invoiceList, but in the readme also questions arose.

Anyone on this right now?

(I am utilizing angular-meteor 1.3.11)

—

You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub

<
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-273746554
,

or mute the thread

<
https://github.com/notifications/unsubscribe-auth/AFCkqzImzDg_ca2LJDMM5-mFszyf8OiGks5rT0N7gaJpZM4HqiQC

.

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub <
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274071402>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/AHwdR3L3BN91miLXjlrKqke4EcXr2ZJ9ks5rULXTgaJpZM4HqiQC
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274077483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFCkq5gk-9C-_6VNAjwmgf1d0HYt914Hks5rUL0KgaJpZM4HqiQC
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274209131, or mute the thread https://github.com/notifications/unsubscribe-auth/AHwdR1ldfOxQmahZTD9iUqyoQqWHwNyDks5rUUY5gaJpZM4HqiQC.

Ok, got it, getReactively just takes the place of the Session variables in Blaze.
thx

Am 26.01.2017 um 14:25 schrieb Thorsten Seckert<EMAIL_ADDRESS>So, just to make sure:
In the helpers, I have to use find() instead of findOne(), since only find() will be treated reactively, right?
And in terms of getreactively: any variable can be made reactive, also variables from services for example?
Regards

Am 21.01.2017 um 00:41 schrieb Matti LeBlanc<EMAIL_ADDRESS><EMAIL_ADDRESS>Well looping at the code base it is still actively being maintained.
There must be a lot of people considering angular 2 , react or Vue over
angular 1.5 so I guess eventually it will become stale.
Not saying you can't keep using it as long as you freeze your code base at
work.
For now I think it is still fine and allows for rapid development
especially with angulars 1.5 components.
On Sat, 21 Jan 2017 at 12:56 am, der-ede<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:

Hi @Matti LeBlanc,
thank you for responding.
The issue of the reactivity not functioning properly almost subsided in
the meantime when I played around with the resolve a bit.
But sometimes it still just does not get the changes in
$scope.helpers({}), although no „deep“ reactivity.
But also in general I was wondering whether the whole angular-meteor
project is obsolete and gone.
Explanation:
Over the past 1 1/2 years or so I accompanied some projects with meteor
and the question of the ui-framework was just costly since it changed a
lot, from fame.us http://fame.us/ to meteoric-ionic to angular-meteor and now everyone
seems to be wanting react.
So angular-meteor is still maintained and will be in the future?
Regards
Thorsten

Am 20.01.2017 um 14:25 schrieb Matti LeBlanc<EMAIL_ADDRESS><EMAIL_ADDRESS>

Hi,

This thread was created 6 months ago or so and i must say that most issue

where resolved. Some were related to architecture and some were bugs.

Which issues are you running into right now?

On Thu, 19 Jan 2017 at 10:05 pm, der-ede<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:

Hi there,

are there still people using angular-meteor?

I started a project and ran into the same issues as you guys.

Thank you @mattiLeBlanc <https://github.com/mattiLeBlanc https://github.com/mattiLeBlanc> for posting
the

github repo invoiceList, but in the readme also questions arose.

Anyone on this right now?

(I am utilizing angular-meteor 1.3.11)

—

You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub

<
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-273746554 https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-273746554
,

or mute the thread

<
https://github.com/notifications/unsubscribe-auth/AFCkqzImzDg_ca2LJDMM5-mFszyf8OiGks5rT0N7gaJpZM4HqiQC https://github.com/notifications/unsubscribe-auth/AFCkqzImzDg_ca2LJDMM5-mFszyf8OiGks5rT0N7gaJpZM4HqiQC

.

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub <
https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274071402 https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274071402>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/AHwdR3L3BN91miLXjlrKqke4EcXr2ZJ9ks5rULXTgaJpZM4HqiQC https://github.com/notifications/unsubscribe-auth/AHwdR3L3BN91miLXjlrKqke4EcXr2ZJ9ks5rULXTgaJpZM4HqiQC
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274077483 https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274077483>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFCkq5gk-9C-_6VNAjwmgf1d0HYt914Hks5rUL0KgaJpZM4HqiQC https://github.com/notifications/unsubscribe-auth/AFCkq5gk-9C-_6VNAjwmgf1d0HYt914Hks5rUL0KgaJpZM4HqiQC>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-274209131, or mute the thread https://github.com/notifications/unsubscribe-auth/AHwdR1ldfOxQmahZTD9iUqyoQqWHwNyDks5rUUY5gaJpZM4HqiQC.

I think FindOne() and Find().fetch() both give the same reactivity. FindOne just returns one and Find() returns a cursor.

ok, then it was about the getReactively() why it didn’t work. thx.

Am 27.01.2017 um 11:07 schrieb Matti LeBlanc<EMAIL_ADDRESS>I think FindOne() and Find().fetch() both give the same reactivity. FindOne just returns one and Find() returns a cursor.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/Urigo/angular-meteor/issues/1264#issuecomment-275630775, or mute the thread https://github.com/notifications/unsubscribe-auth/AHwdRz1f0XAd-sY0jNcH2WRdZ9152vKkks5rWcH-gaJpZM4HqiQC.


Create README for project [#13]

Closes #13

{
"changes" [
{
"path": "/coco-toolbox/README.md",
"action": "update",
"content": "# Coco-ToolBox\n\nThis repository contains a collection of utilities and modules used throughout the Twin Digital organization.\n\n## Installation\n\nTo install the coco-toolbox, run the following command:\n\nsh\nnpm install\n\n\n## Usage\n\nTo use any of the utilities or modules in the coco-toolbox project, simply import them into your Typescript project like this:\n\nts\nimport { UtilityName } from 'coco-toolbox'\n\n\n## Contributing\n\nTo contribute to the coco-toolbox project, please follow our development guidelines as outlined in CONTRIBUTING.md\n",
"description": "Create README.md"
}
]
}

Deleting progress on issue because: Issue was edited, and I don't know how to reconcile changes with existing work..
Closing.


after htmlClass is added the fields becomes unclickable

When bootstrap classes are added using htmlClass to the form json for layout. The field becomes unclickable only keyboard tab works.
{
"key": "requester",
"type": "text",
"placeholder": "Full Name",
"htmlClass": "col-md-10",
"feedback": false
 }

@navjinder What version of schemaForm are you using?

Hi
I am using the latest version I downloaded it yesterday from GitHub.. THere is no version number in the file header. Thanks.

Hi @navjinder,
Its a CSS problem. I tried it on the demo page and indeed it got unclickable, what happens is that  the class  col-md-10 adds the style rule float: left; which caused the next form field to surrounding div to overlap and take all the events. You can see this if you use "inspect element" in the developer tools.
One solution for you is to just apply "col-md-10" on the next field as well. Closing since its not a bug in schema form

Hi @davidlgj  thanks for the info yes I was able to see that float was causing the issue. So what I did was I have created a special class which do not have the float in it and I have applied it to the last form field which has fixed the error for me.


Fix modified user/pass as part of preseed

Currently it has been left with a hardcoded ubuntu/ubuntu user


(GH-1) Allow for large package sizes

Set maxRequestLength to 2GB (2,147,482,548) based on
https://msdn.microsoft.com/en-us/library/e1f13641(v=vs.100).aspx
Set maxAllowedContentLength to 2GB (2,147,482,548) based on
https://msdn.microsoft.com/en-us/library/ms689462(v=vs.90).aspx

This will be great!


An error is reported when exiting the electron application

macOS: 12.3.1 arm64
Electron: 18.2.0
I generated the prebuild on my own macOS arm64 computer and then tried to use it in my electron project in the main process, and when I quit the application, electron reported the following error:
FATAL ERROR: uiohook_to_js_event napi_define_properties
 1: 0x111e2e09c node::FatalException(v8::Isolate*, v8::TryCatch const&) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 2: 0x111e2e21c node::OnFatalError(char const*, char const*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 3: 0x111e2e0b4 node::OnFatalError(char const*, char const*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 4: 0x111de76d4 napi_open_callback_scope [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 5: 0x10bee9e90 tsfn_to_js_proxy [/Users/myproject/node_modules/uiohook-napi/prebuilds/darwin-arm64/node.napi.node]
 6: 0x10bee9ecc tsfn_to_js_proxy [/Users/myproject/node_modules/uiohook-napi/prebuilds/darwin-arm64/node.napi.node]
 7: 0x111de9f58 node_api_get_module_file_name [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 8: 0x10c4202dc uv_async_send [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 9: 0x10c4310d0 uv_free_interface_addresses [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
10: 0x10c4206f0 uv_run [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
11: 0x111dceffc node::EmitAsyncDestroy(node::Environment*, node::async_context) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
12: 0x111dcf330 node::EmitAsyncDestroy(node::Environment*, node::async_context) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
13: 0x111d9d274 node::FreeEnvironment(node::Environment*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
14: 0x10c506210 heap::base::Stack::SetStackStart(void const*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
15: 0x10c4f2820 v8::internal::compiler::RawMachineAssembler::TargetParameter() [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
16: 0x10dfc86c0 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
17: 0x10dfc9d4c v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
18: 0x10dfc61ac v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
19: 0x10c6a7bbc v8::internal::compiler::BasicBlock::set_loop_header(v8::internal::compiler::BasicBlock*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
20: 0x10c6a8bdc v8::internal::compiler::BasicBlock::set_loop_header(v8::internal::compiler::BasicBlock*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
21: 0x10c6a8778 v8::internal::compiler::BasicBlock::set_loop_header(v8::internal::compiler::BasicBlock*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
22: 0x10c6a7280 v8::internal::compiler::BasicBlock::set_loop_header(v8::internal::compiler::BasicBlock*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
23: 0x10c6a774c v8::internal::compiler::BasicBlock::set_loop_header(v8::internal::compiler::BasicBlock*) [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
24: 0x10c431688 ElectronMain [/Users/myproject/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
25: 0x10488d088
/Users/myproject/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron exited with signal SIGABRT

iohook also has this problem, but I can fix it by uninstalling .node before exiting the app:
app.on('will-quit', () => {
  iohook.unload()
})

This problem can probably be solved by upgrading libuiohook to the latest version.

I tried to upgrade libuiohook to the latest version and then I don't have this problem. The steps I used were as follows:
git clone https://github.com/SnosMe/uiohook-napi.git
cd uiohook-napi/libuiohook
git pull
cd ..
yarn
yarn prebuild
cp -r prebuilds/drawin-arm64 ../myproject/node_modules/uiohook-napi/prebuilds

But I'm not familiar with Node.js native addons and I don't know how to write C/C++ code, so I'm not sure if this upgrade will cause other problems (for example, I noticed that you should have modified the libuiohook code with libuiohook.patch), so I'd like you to upgrade the version of libuiohook, thanks!


假名转换

It seems like there are several JavaScript solutions online to convert from Kanji, Romaji, Hiragana and Katakana. Check these out and see if they work for you:

JQuery Auto Kana Input
Kuroshiro
jp-conversion
WanaKanaJS

来源: https://stackoverflow.com/questions/39830530/how-to-translate-japanese-kanji-to-katakana

最简单的库, 源码最易参考: https://github.com/Pomax/node-jp-conversion


Adding support for Threshold, Limit, and Order Arguments

This pull request adds 3 keyword arguments to the nearest_neighbor method. They are:
order
movie = Movie.find_by(name: "Star Wars (1977)")
# Order all results by the neighbor_distance column in descending order
movie.nearest_neighbors(:factors, distance: "inner_product", order: { neighbor_distance: :desc })

limit
movie = Movie.find_by(name: "Star Wars (1977)")
# Limit the results to 3 records
movie.nearest_neighbors(:factors, distance: "inner_product", limit: 3)

threshold
movie = Movie.find_by(name: "Star Wars (1977)")
# Only return records where the neighbor_distance is greater than or equal to 0.9
movie.nearest_neighbors(:factors, distance: "inner_product", threshold: { gte: 0.9 })

Multiple Options
All options can be used at the same time or separately.
movie = Movie.find_by(name: "Star Wars (1977)")

# Only return 5 records where the neighbor_distance is greater than or equal to 0.9 in descending order
movie.nearest_neighbors(
  :factors,
  distance: "inner_product",
  limit: 5,
  threshold: { gte: 0.9 },
  order: { neighbor_distance: :desc }
)

These options manipulate the SQL statement generated by ActiveRecord. All original test suits are intact and passing, and the new tests were written with the new options.

Hi @sebscholl, thanks for the PR.

nearest_neighbors currently returns a relation, so you can limit with limit(n) or first(n).
Results are currently ordered by distance. However, if you have a default scope on the model, that'll take precedence.
For thresholds, you can use where("(embedding <#> ?) * -1 > ?", vector, 0.9) or filter in memory with select { |v| v.neighbor_distance > 0.9 }. I may add an option for this at some point, but want to think more about the design.

Makes sense. Do you believe it would be helpful to add this info to the docs (e.g, where("(embedding <#> ?) * -1 > ?", vector, 0.9)) or prefer to sit tight until you feel you have more clarity on the design? Lmk, and I can make an update if it would help.

@ankane I believe in the case of using class method like Movie.nearest_neighbor(embedding, my_gen_embedding, ...) the ordering is not set by distance. Instead I'm getting ORDER BY "text_nodes"."id" ASC LIMIT $1 on these queries. I'm encountering this exact problem and so i'll implement the query manually as a workaround for now.

@ankane Any thoughts on how best to support ordering by distance?

@vestedpr-dev thanks for writing that out!  I wasn't able to get this line to work in rails 8, pg 17:
"((#{@params[:search_vector_column]} #{operator} '[?]') * -1) < ?"

My actual command:
m.nearest_neighbors(:embeddings, distance: "cosine").where("embeddings <=> '[?]' <= ?", m.embeddings, 1 - 0.9).first(3)

error:
exec_params': ERROR:  invalid input syntax for type vector: "[$2, $3, $4]" (PG::InvalidTextRepresentation)
LINE 1: ...nts"."embeddings" IS NOT NULL AND (embeddings <=> '[$2, $3, ...

I tried various ways of casting and finally got this way to work, but this feels very inefficient:
    # Convert embeddings array to a parameterized string safely
    embeddings_array = self.embeddings.map { |v| ActiveRecord::Base.sanitize_sql(v) }.join(', ')

    # Safely bind parameters to avoid SQL injection
    return MyModel
      .where.not(id: self.id)
      .where.not(embeddings: nil)
      .where(Arel.sql("embeddings <=> ARRAY[#{embeddings_array}]::vector <= ?"), 1 - threshold)
      .order(Arel.sql("embeddings <=> ARRAY[#{embeddings_array}]::vector"))
      .limit(3)

This seems to work for me using Postgres.
Model
  .nearest_neighbors(:embedding, embedding, distance: 'cosine')
  .where(
    "(embedding <=> ARRAY[#{embedding.join(', ')}]::vector) < ?",
    0.2
  )

I wasn't able to get the '[?]' syntax working either.


consistent badge design - using .svg

Sorry for the noise. Didn't catch this with django-extensions/django-extensions#956.

Coverage remained the same at 37.518% when pulling<PHONE_NUMBER>10a3ddab02597461d96007a4d90110 on gesellc:consistent-badge-design into 39153ad862c77cd89a3480951bd74b86001cdfd6 on django-extensions:master.

No problem, thanks ! all help is appreciated 👍


Comply with stylizing guides

Comply with airbnb styling for CSS and JS and PSR 2 for PHP.

Two of the recent branch merges fixes this a lot.


Setup bladestan?

I am looking for bladestan use-cases to measure for perf bottlenecks.
i don‘t have any laravel project, so maybe we can use this one?
Alternatively maybe someone can give me access to a project which uses bladestan extensively, so I can do some measuring…?

Hi, I'm going through forgotten issues and questions :)
I personally don't have any big Laravel-template project to provide. I think it would have to be a private one, as that's the best source of any dirt :)


Changed exit to be on pointerdown, not click

This changes how the mouse-based exit detection works for both edit mode and color picker.
If you mouse-down inside the component, but subsequently mouse-up outside the component, the component should not treat this as an exit signal.
This is done by changed the listener to be a pointerdown listener rather than a click listener in both instances (and nothing else actually).
This might have unexpected consequences, so heavy testing is required.
Fixes #1186.
Demo
Text edit

Before
After

Color picker

Before
After

@barklund Tested and didn't notice any issues so far.
Should this be applied also to the calendar? And dropdown selection?

@barklund @miina do you think it's possible to move this to the Popup component for the calendar and color picker (since we have #1060 )?

LG, should we also change dashboard/utils/useFocusOut.js?

Let's just ping @carlos-kelly for now and leave it up to him.

@barklund @merapi This seems like a reasonable change we can make since if they do mouse-up outside then the event won't fire.


Travis CI support

Hi guys,
I've heard that you're working on adding support for Travis CI and was wondering how that's going. Like many other Nativescript developers I am currently dependent on cloud builds so to be totally honest it's already a bit of an inconvenience to have to move away from that within two weeks.
But as someone who has worked with Travis CI before that would be something I'd be a lot more comfortable switching to than Circle CI at the moment. So do you guys have an idea on when support for Travis CI will be completed? Can I wait for Travis support to migrate or should I really just migrate to Circle CI first and then switch to Travis later? (Which would be a bit of a pain)
Thanks for hearing me out and have a nice day.

+1

@babarinde Well as you can no one ever replied and to be honest I think they've abandoned this repository.
We tried to work around it by setting up and MacOS VM at first. But that didn't really work that well and in the end we just bought an Mac mini and set it up for remote access so we can build on that. For us it was worth the cost.


Add CORS policy

Subtask to set up CORS (Cross-Origin Resource Sharing) for the backend endpoints related to the user story defined at #5
In order to facilitate the frontend to be able to use the backend endpoints, it is imperative to establish proper CORS configuration for the backend endpoints.
[Story Points: 1]
[Priority: High]
[Risk: Low]

Add-cors-policy-demo.webm


'rez build --install --prefix' error

Hi there!
We encountered the following error while deploying a library of ours in a specific directory with rez on a python's docker image through Gitlab CI/CD.
We'd be grateful if you could tell us how to resolve this issue by ourselves or if you could fix it!
We might have missed some context or information in this comment; please tell us so if necessary.
Many thanks in advance.
rez build --install --prefix /mnt/rnd/PIPELINE/USER/HC
Building into: '/mnt/rnd/PIPELINE/USER/HC'

--------------------------------------------------------------------------------
Building smurfs-0.0.27...
--------------------------------------------------------------------------------
Resolving build environment: ellipsanime '~maya==2018.6' '~houdini==17.0.352' '~nuke==11.3.4' ellipsanime rez_utils-1
resolved by root@runner-c392f0d9-project-56-concurrent-0, on Mon Feb 24 17:08:30 2020, using Rez v2.40.4

requested packages:
ellipsanime
~maya==2018.6
~houdini==17.0.352
~nuke==11.3.4
ellipsanime
rez_utils-1
~platform==linux    (implicit)
~arch==x86_64       (implicit)
~os==debian-10      (implicit)

resolved packages:
ellipsanime-0.0.3  /mnt/rnd/PIPELINE/__PACKAGES__/project/ellipsanime/0.0.3
python-3.7.6       /mnt/rnd/PIPELINE/__PACKAGES__/app/python/3.7.6
rez_utils-1.0.3    /mnt/rnd/PIPELINE/__PACKAGES__/int/rez_utils/1.0.3

Invoking custom build system...
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/rez/serialise.py", line 71, in open_file_for_write
    f.write(content)
  File "/usr/local/lib/python3.7/contextlib.py", line 119, in __exit__
    next(self.gen)
  File "/usr/local/lib/python3.7/site-packages/rez/vendor/atomicwrites/__init__.py", line 154, in _open
    self.commit(f)
  File "/usr/local/lib/python3.7/site-packages/rez/vendor/atomicwrites/__init__.py", line 185, in commit
    replace_atomic(f.name, self._path)
  File "/usr/local/lib/python3.7/site-packages/rez/vendor/atomicwrites/__init__.py", line 92, in replace_atomic
    return _replace_atomic(src, dst)
  File "/usr/local/lib/python3.7/site-packages/rez/vendor/atomicwrites/__init__.py", line 50, in _replace_atomic
    _sync_directory(os.path.normpath(os.path.dirname(dst)))
  File "/usr/local/lib/python3.7/site-packages/rez/vendor/atomicwrites/__init__.py", line 44, in _sync_directory
    _proper_fsync(fd)
OSError: [Errno 22] Invalid argument

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/rez", line 8, in <module>
    sys.exit(run())
  File "/usr/local/lib/python3.7/site-packages/rez/cli/_main.py", line 153, in run
    returncode = run_cmd()
  File "/usr/local/lib/python3.7/site-packages/rez/cli/_main.py", line 145, in run_cmd
    return opts.func(opts, opts.parser, extra_arg_groups)
  File "/usr/local/lib/python3.7/site-packages/rez/cli/build.py", line 170, in command
    variants=opts.variants)
  File "/usr/local/lib/python3.7/site-packages/rezplugins/build_process/local.py", line 41, in build
    install=install)
  File "/usr/local/lib/python3.7/site-packages/rez/build_process_.py", line 203, in visit_variants
    result = func(variant, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/rezplugins/build_process/local.py", line 280, in _build_variant
    variant.install(install_path)
  File "/usr/local/lib/python3.7/site-packages/rez/packages_.py", line 402, in install
    overrides=overrides)
  File "/usr/local/lib/python3.7/site-packages/rezplugins/package_repository/filesystem.py", line 625, in install_variant
    variant = _create_variant()
  File "/usr/local/lib/python3.7/site-packages/rezplugins/package_repository/filesystem.py", line 618, in _create_variant
    overrides=overrides
  File "/usr/local/lib/python3.7/site-packages/rezplugins/package_repository/filesystem.py", line 1077, in _create_variant
    dump_package_data(package_data, buf=f, format_=package_format)
  File "/usr/local/lib/python3.7/contextlib.py", line 119, in __exit__
    next(self.gen)
  File "/usr/local/lib/python3.7/site-packages/rez/serialise.py", line 73, in open_file_for_write
    except WindowsError as e:
NameError: name 'WindowsError' is not defined
ERROR: Job failed: exit code 1

I haven't seen this error, have you determined that it's related to running within a container?
The second stacktrace looks like it's simply caused by a missing import for the WindowsError, I will look into that. In the meantime perhaps if you could narrow down the repro, if possible.
Cheers!
A

Hit a simillar problem: NameError: name 'WindowsError' is not defined
https://github.com/nerdvegas/rez/blob/master/src/rez/serialise.py#L76

The first thing I'd investigate is whether a newer version of
atomicwrites is necessary.
A
On Tue, Sep 22, 2020 at 9:56 AM alexxbb<EMAIL_ADDRESS>wrote:

Hit a simillar problem: NameError: name 'WindowsError' is not defined
https://github.com/nerdvegas/rez/blob/master/src/rez/serialise.py#L76
http://url
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/issues/858#issuecomment-696441525, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSVPYAXLA4MRSP5J4JDSG7R25ANCNFSM4K2MWD2Q
.

Wonder why is this windows-specific WindowsError in the code in the first place? I'm getting errors on Linux with Python2.

Oh, I haven't seen failures with atomiwrites on linux before, I'd assumed you were on Windows.
Would it be possible to isolate this to a small repro using atomicwrites only? I am assuming this is an edge case we've not seen before - if this were failing in the general case, I'd have gotten loads of bug reports.

rez-pip --install --release --python-version=2.7 python-gitlab
Traceback (most recent call last):
  File "/usr/bin/rez-pip", line 8, in <module>
    sys.exit(run_rez_pip())
  File "/opt/rez/lib/python2.7/site-packages/rez/cli/_entry_points.py", line 188, in run_rez_pip
    return run("pip")
  File "/opt/rez/lib/python2.7/site-packages/rez/cli/_main.py", line 152, in run
    returncode = run_cmd()
  File "/opt/rez/lib/python2.7/site-packages/rez/cli/_main.py", line 144, in run_cmd
    return opts.func(opts, opts.parser, extra_arg_groups)
  File "/opt/rez/lib/python2.7/site-packages/rez/cli/pip.py", line 67, in command
    extra_args=opts.extra)
  File "/opt/rez/lib/python2.7/site-packages/rez/pip.py", line 404, in pip_install_package
    pkg.is_pure_python = metadata["is_pure_python"]
  File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__
    self.gen.next()
  File "/opt/rez/lib/python2.7/site-packages/rez/package_maker.py", line 217, in make_package
    variant_ = variant.install(path)
  File "/opt/rez/lib/python2.7/site-packages/rez/packages.py", line 413, in install
    overrides=overrides)
  File "/opt/rez/lib/python2.7/site-packages/rezplugins/package_repository/filesystem.py", line 655, in install_variant
    variant = _create_variant()
  File "/opt/rez/lib/python2.7/site-packages/rezplugins/package_repository/filesystem.py", line 648, in _create_variant
    overrides=overrides
  File "/opt/rez/lib/python2.7/site-packages/rezplugins/package_repository/filesystem.py", line 1114, in _create_variant
    dump_package_data(package_data, buf=f, format_=package_format)
  File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__
    self.gen.next()
  File "/opt/rez/lib/python2.7/site-packages/rez/serialise.py", line 74, in open_file_for_write
    except WindowsError as e:
NameError: global name 'WindowsError' is not defined

Without --release it installed locally just fine. Hope this helps.
Thanks.

I have encountered the same issue using debian.
I tried to install a pip package on a rez repository mounted from my network.
This seems to happen because some fs don't handle sync for directories (used to ensure atomicity) : https://github.com/untitaker/python-atomicwrites/issues/17
my current workaround is to call rez pip on a local directory and use rsync before and after the call to transfert the newly installed package
Since atomicity can't be guaranteed within Network repositories, it would be nice to use a simple (non atomic) method if atomicwrites fail with this error (OSError: [Errno 22])

fixed in https://github.com/nerdvegas/rez/pull/998


Publish on crates.io

Tracking ticket for publishing on crates.io:
src/common - pelikan-common - "Common internal libraries for Pelikan"
src/config - pelikan-config - "Component configuration for Pelikan"
src/core/admin - pelikan-core-admin - "Admin components for Pelikan"
src/core/proxy - pelikan-core-proxy - "Proxy components for Pelikan"
src/core/server - pelikan-core-server - "Server components for Pelikan"
src/core/waker - pelikan-core-waker - "Cross-thread wakers for Pelikan"
src/entrystore - pelikan-entrystore - "Maps protocol commands to Pelikan storage operations"
src/logger - pelikan-logger - "Logging framework for Pelikan"
src/net - pelikan-net - "Networking components and abstractions for Pelikan"
src/protocol/admin - pelikan-protocol-admin - "Admin protocol for Pelikan"
src/protocol/common - pelikan-protocol-common - "Shared protocol traits for Pelikan"
src/protocol/http - pelikan-protocol-http - "HTTP protocol for Pelikan"
src/protocol/memcache - pelikan-protocol-memcache - "Memcache protocol for Pelikan"
src/protocol/ping - pelikan-protocol-ping - "Ping protocol for Pelikan"
src/protocol/resp - pelikan-protocol-resp - "Redis serialization protocol for Pelikan"
src/protocol/thrift - pelikan-protocol-thrift - "Thrift binary protocol for Pelikan"
src/proxy/momento - pelikan-momento-proxy - "Pelikan proxy which allows Memcache and Redis clients to communicate with Momento" - build target: momento_proxy
src/proxy/ping - pelikan-pingproxy (?) - "Pelikan proxy which uses the ping protocol" - build target: pelikan_pingproxy
src/proxy/thrift - pelikan-thriftproxy - "Pelikan proxy which uses the Thrift binary protocol" - build target: pelikan_thriftproxy
src/queues - pelikan-queues - "Queues for cross-thread communication in Pelikan"
src/server/pingserver - pelikan-pingserver - "A simple ASCII ping/pong server" - build target: pelikan_segcache
src/server/segcache - pelikan-segcache - "A Memcache compatible server which uses segment-structured storage" - build target: pelikan_segcache
src/session - pelikan-session - "An abstraction on-top of streams for buffered bi-directional communication"
src/storage/bloom - pelikan-storage-bloom - "Pelikan bloom filter storage"
src/storage/datapool - pelikan-storage-datapool - "An abstraction which provides byte-addressable storage"
src/storage/seg - pelikan-storage-seg - "Pelikan segment-structured storage"
src/storage/types - pelikan-storage-types - "Typed storage for use in Pelikan"

Open questions/observations:

do we want to publish the thrift proxy? (thinking no)
should src/queues move to rustcommon? (thinking yes)
should we use pelikan_ping_proxy or pelikan_pingproxy for "generic" proxy naming patterns?
I believe we do want to use pelikan_segcache for the binary name (note: dropping "_rs" suffix) and allow install via cargo install pelikan-segcache
should src/net or src/session move out to rustcommon? They feel like they could be useful in projects like rpc-perf, though we can depend on them through the pelikan- crates.
Momento proxy may

And some hazards to consider:

crates cannot be deleted, if we want to rename we will pollute our "namespace"
namespaces do not exist, anybody could write and publish a pelikan- crate
while the crate name (used for cargo install) does not need to match the name of the binary(s) that it provides, we should strive to make it easy for users

Some additional notes on this:
src/core/waker - moved to rustcommon, published as awaken

Some additional questions/notes:

Do we want to version all of the related pelikan-* crates in lockstep? If not, what is the versioning policy?
We should probably reserve the pelikan crate too - maybe as a virtual "install all the binaries" crate
Do we intend for the various storages to be useful as standalone libraries? (e.g. for segcache) If so, we'll probably want to do a second pass over them so they are useful.
With this many crates being managed in the repo we will probably want some automation to handle the publishing work. There are tools for this and we should look into using them.
Owner on crates.io - we should probably make a crates.io user for the pelikan foundation, that way we can either have publishing go through github actions or have a team with publishing permissions.

@swlynch99 - great questions

I think we should move from the unified version for the workspace back to version per crate. It's going to make the version number meaningful for the individual binaries. We'll do semver for everything, current plan would be to release each as 0.3.2 (next up from current 0.3.1). https://semver.org/#semantic-versioning-specification-semver
great idea, i'll grab that now with a 0.0.0 namesquatting crate
yes, individual storage libraries should be useful in other projects. eg 'seg' storage should be usable within another application or library. I believe the 'seg' crate is already in good shape for this, but we'll take another pass across everything and improve docs/ergonomics
if you have suggestions, please share. I personally didn't love cargo-release when I last used it to contribute to an org repo. If we don't know yet, I'll try to see what other large projects are doing.
yes, we'll also want to figure a plan for RPMs, DEBs, etc where appropriate

This work would make it easier to embed Pelikan (and especially segcache) in other services! 👍  Thank you so much for considering that!
When you get to this work, could you please consider reviewing the dependency chains in Pelikan? Namely, today: seg depends on (pelikan-)common which depends on boring (--> boring-sys) and (pelikan-)net. These introduce indirect dependencies that shouldn't be required to use segcache

segcache storage crate has been published


[BugFix] CMake build on Windows and Ninja build on all platforms

This pull request is ready to be merged, pending regression and unit test checks.
Feature or improvement description
This pull request fixes a recent bug which caused CMake projects generated on Windows to fail to build. It also fixes a long standing issue where Ninja builds generated by CMake (-G Ninja) also failed to build. A minor change was to use CMake's FindPython to locate the Python interpreter. I larger change was to use CMake's FindLAPACK to locate the MKL and set the appropriate linker flags, which resolved the Windows build issue. The LAPACK/BLAS vendor can be specified when running CMake as explained at https://cmake.org/cmake/help/latest/module/FindBLAS.html#blas-lapack-vendors.
Related issue, if one exists
#1523
Impacted areas of the software

/CMakeLists.txt
/unit_tests/CMakeLists.txt
/unit_tests/*/CMakeLists.txt
/reg_tests/CTestList.cmake

I can see there is a small SubDyn fix in there, it's fine by me to keep it in this pull request

I can see there is a small SubDyn fix in there, it's fine by me to keep it in this pull request

I put that SD fix in this one as well: https://github.com/OpenFAST/openfast/pull/1534


configuration file path information to terminal

Description

Fixes pyrsia/pyrsia#1190
This PR implements the functionality to show the location of the config file along with the content of the config file. You can test using pyrsia config --show and it should show something like following.
Config file path: /Users/manasd/Library/Preferences/rs.pyrsia-cli/default-config.toml
host = '<IP_ADDRESS>'
port = '7888'
disk_allocated = '10 GB'

Information to Config file path: has been added in this PR.
Screenshots (optional)
PR Checklist

[ ] I've read the contributing guidelines.
[ ] I've read "What is a Good PR?"
[ ] I've included a good title and brief description along with how to review them.
[ ] I've linked any associated an issue.

Code Contributions

[ ] I've built the code cargo build --all-targets successfully.
[ ] I've run the unit tests cargo test --workspace and everything passes.
[ ] I've made sure my rust toolchain is current rustup update.

Test case failing while trying to run pyrsia CLI from pyrsia/target/debug/pyrsia using Command::cargo_bin.
test tests::test_config_show_file_path_info_availability ... FAILED

 failures:
---- tests::test_config_show_file_path_info_availability stdout ----
 thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: CargoError { cause: Some(NotFoundError { path: "/pyrsia/target/debug/pyrsia" }) }', pyrsia_cli/src/main.rs:85:52
 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Test case failing while trying to run pyrsia CLI from pyrsia/target/debug/pyrsia using Command::cargo_bin.
test tests::test_config_show_file_path_info_availability ... FAILED

 failures:
---- tests::test_config_show_file_path_info_availability stdout ----
 thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: CargoError { cause: Some(NotFoundError { path: "/pyrsia/target/debug/pyrsia" }) }', pyrsia_cli/src/main.rs:85:52
 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Root cause is cargo tarpaulin is not generating the following. Due to that CLI unit testing using command is failing.
`-- target
    |-- debug
    |   |-- libpyrsia.d
    |   |-- libpyrsia.rlib
    |   |-- libpyrsia_blockchain_network.d
    |   |-- libpyrsia_blockchain_network.rlib
    |   |-- pyrsia
    |   |-- pyrsia.d
    |   |-- pyrsia_node
    |   `-- pyrsia_node.d


Basic type can not be assigned to its alias type

Id is an alias of int. But it cannot be assigned with int value.
type Id int

func main() {
    var i Id
    var k int = 10
    iv := reflect.ValueOf(&i).Elem()
    kv := reflect.ValueOf(k)
    if kv.Type().AssignableTo(iv.Type()) {  // condition is false
	    iv.Set(kv)
    }
    fmt.Print(i)  // output 0
}

Right.  int is not assignable to Id.

@mdempsky Thanks for your reply. So how to assign int value to Id variable with reflect?

You'll need to convert the int value to an Id value (e.g., using reflect.Value's Convert method).  However, if you have further questions, the best place to ask them is golang-nuts, not the issue tracker.  Thanks!


[💡 FEATURE REQUEST]: Add syntax validation of .rr.yaml on server startup

Plugin
JOBS
I have an idea!
Please, add full syntax validation of config file .rr.yaml on server startup. Without this feature, server behavior may be unpredictable.
For example, if syntax error (typo) exists in the first line of .rr.yaml:
durabversion: "2.7"

then no errors are occurs and no warnings in the log. AMQP driver successfully connects to correct RabbitMQ server, specified by parameter addr: of file  .rr.yaml, but driver connects to incorrect default queue default (parameter queue: is ignored).

Hey @andrey-tech 👋🏻
RR has a backward-compatible configuration. That means if you run RR version 2.11.4 on the configuration without the version, RR assumes you're running an unversioned version and automatically updates your configuration.
For example: durabversion: "2.7". RR will not read this key in any way and assumes you're running an old configuration version.
Also, queue, addr, and other args have default values (you may have a look and the rr.yaml in the repo root). If you provided an address like tcp://foo.bar. It's a valid address (imagine you're running RR in the docker and have a container with that name (DNS))
Thus, I'm not sure what exactly RR should validate.

Hi @rustatian
I would like to have .rr.yaml file specification similar to Docker Compose specification.
For example, fragment from Compose specification:
Version top-level element

Compose implementations SHOULD validate whether they can fully parse the Compose file.
If some fields are unknown, typically because the Compose file was written with fields defined
by a newer version of the specification, Compose implementations SHOULD warn the user.

So, if I run Docker Compose with syntax error (typo) in first line of Compose yaml-file durabversion: "2.7", then I got an error: (root) Additional property durabversion is not allowed . I would like to have same predictable behavior from RR.

Yeah, this would be nice to have such a document. We have a RR2 schema in the [schemastore]<EMAIL_ADDRESS>as the first step to the formal specifications.
I would appreciate a PR or any help in that direction.

Thanks for the FR @andrey-tech 👍🏻

RR configuration plugin validates YAML.
All plugins validate their configuration and report errors if you use an incorrect address or for example instead of int you use string.
Additionally you may also validate your schema for correctness with the following tool: https://github.com/roadrunner-server/roadrunner/tree/master/schemas


Make a new release

Make a new release and publish it to NuGet.

New release with v0.8.0 published to NuGet


https://ep2017.europython.eu/en/find-out-whos-coming/ doesn't work

Page not found (404)
Request Method: 	GET
Request URL: 	https://dev.europython.eu/en/find-out-whos-coming/
Raised by: 	cms.views.details

Using the URLconf defined in pycon.urls, Django tried these URL patterns, in this order:

    ^accounts/
    ^admin/filebrowser/
    ^admin/rosetta/
    ^admin/
    ^comments/
    ^p3/
    ^conference/
    ^conference/talks/(?P<slug>[\w-]+)$ [name='conference-talk']
    ^conference/speakers/(?P<slug>[\w-]+) [name='conference-speaker']
    ^hcomments/
    ^i18n/
    ^markitup/
    ^login/(?P<backend>[^/]+)/$ [name='begin']
    ^complete/(?P<backend>[^/]+)/$ [name='complete']
    ^disconnect/(?P<backend>[^/]+)/$ [name='disconnect']
    ^disconnect/(?P<backend>[^/]+)/(?P<association_id>[^/]+)/$ [name='disconnect_individual']
    ^login/$ [name='login']
    ^logout/$ [name='logout']
    ^password_change/$ [name='password_change']
    ^password_change/done/$ [name='password_change_done']
    ^password_reset/$ [name='password_reset']
    ^password_reset/done/$ [name='password_reset_done']
    ^reset/(?P<uidb64>[0-9A-Za-z_\-]+)/(?P<token>[0-9A-Za-z]{1,13}-[0-9A-Za-z]{1,20})/$ [name='password_reset_confirm']
    ^reset/done/$ [name='password_reset_complete']
    ^media/(?P<path>.*)$
    ^en/ ^ ^cms_wizard/
    ^en/ ^ ^(?P<slug>[0-9A-Za-z-_.//]+)/$ [name='pages-details-by-slug']
    ^en/ ^ ^$ [name='pages-root']

The current URL, /en/find-out-whos-coming/, didn't match any of these.

https://ep2016.europython.eu/registration/

Fixed by adding the page to the CMS.