Value of Info.plist[Fabric][Kits] should be a NSArray

Indeed, installing a plugin doesn't add kit list to iOS Info.plist.
https://fabric.io/kits/ios/crashlytics/install

Expanding config-file section in plugin.xml seems to take care of warning:
        <config-file target="*-Info.plist" parent="Fabric">
            <dict>
                <key>APIKey</key>
                <string>$FABRIC_API_KEY</string>
				<key>Kits</key>
				<array>
					<dict>
						<key>KitInfo</key>
						<dict/>
						<key>KitName</key>
						<string>Crashlytics</string>
					</dict>
					<dict>
						<key>KitInfo</key>
						<dict/>
						<key>KitName</key>
						<string>Answers</string>
					</dict>
				</array>
            </dict>
        </config-file>

I'm also getting this error message. Has that commit been merged and included in the latest release?

@Iyashu5040 nope

You should open a PR with that commit so it can get merged.

PR submitted: https://github.com/sarriaroman/FabricPlugin/pull/111


beef up getting started

While on the nit train, I noticed a sneaky "be" on line 62:
LangChain exposes a standard interface for both, but it's useful to understand this difference in order to be construct prompts for a given language model.

I think was meant to be:
LangChain exposes a standard interface for both, but it's useful to understand this difference in order to construct prompts for a given language model.


Support Chai@4 - Fix assertions broken by Chai 4.0

This PR addresses https://github.com/chaijs/chai/issues/723. To summarize:

A change in Chai 4.0 causes assertions to lose their promiseness unless the promisified assertion object is explicitly returned
A single test started failing with Chai 4.0 due to the replacement of .deep with .nested
With this PR, chai-as-promised should now work with Chai 4.0 while continuing to work with older versions of Chai

Awesome work!
I just got to the bottom of this and this is what I found out: on the doAsserterAsyncAndAddThen function we have a single argument, as you can see here, this single argument for then will only be called if the promise gets resolved, if it gets rejected it should call the second argument, which doesn't exist in this case, so we don't do any assertion at all.
As a proof of concept, I changed that method to this:
function doAsserterAsyncAndAddThen(asserter, assertion, args) {
    // Since we're intercepting all methods/properties, we need to just pass through if they don't want
    // `eventually`, or if we've already fulfilled the promise (see below).
    if (!utils.flag(assertion, "eventually")) {
        return asserter.apply(assertion, args);
    }
    var derivedPromise = getBasePromise(assertion).then(function (value) {
        // Set up the environment for the asserter to actually run: `_obj` should be the fulfillment value, and
        // now that we have the value, we're no longer in "eventually" mode, so we won't run any of this code,
        // just the base Chai code that we get to via the short-circuit above.
        assertion._obj = value;
        utils.flag(assertion, "eventually", false);

        return args ? chaiAsPromised.transformAsserterArgs(args) : args;
    }, function(value) {
        // Here I'm doing the same thing as if the method got resolved, but this will be called if it gets rejected
        assertion._obj = value;
        utils.flag(assertion, "eventually", false);

        return args ? chaiAsPromised.transformAsserterArgs(args) : args;
    }).then(function (args) {
        asserter.apply(assertion, args);

        // Because asserters, for example `property`, can change the value of `_obj` (i.e. change the "object"
        // flag), we need to communicate this value change to subsequent chained asserters. Since we build a
        // promise chain paralleling the asserter chain, we can use it to communicate such changes.
        return assertion._obj;
    });

    chaiAsPromised.transferPromiseness(assertion, derivedPromise);
}

As you can see above I just added a second argument which does the same thing as the first one, but this will be called whenever the promise gets rejected.
Now every test is passing.
I'm just wondering why these tests weren't failing before, because the promise should've been getting rejected before that commit on Chai too.
Well, now we know what is causing the problem maybe we should check why this was working before.
Let me know if you need any help with this @meeber, you've been doing great commits 😄
Extra note: Isn't this line error prone? What if something that is not a promise has a then method?

@lucasfcosta Thanks for reviewing this!
I wonder the same thing about how those two tests were passing before. Would be interesting to dig deeper. Good job finding a solution!
However, I'm still not sure I understand why they are meant to pass in the first place? Why should performing a second assertion on the rejected promise result in a fulfilled promise?

.rejected.and.eventually.equal(42) is a valid test. rejected effectively just swaps the resolved/rejected values around so that you can assert on the error.
To give a recent concrete example I've had: I've been using chai-http+chai-as-promised to assert on failed http requests like so:
it('should reject unauthed request with 401', () =>
  chai.request('http://foo...').should.eventually.be.rejected.and.eventually.have.status(401)
});

@keithamus Ahh I understand now. Thanks! :D

@meeber you're welcome!
I think this behavior, as @keithamus explained, is totally valid.
And I'd also like to point that my solution was just a PoC, we can have a cleaner and more beautiful implementation of that instead of repeating code inside both functions hahaha
Let me know if you need anything 😄

@lucasfcosta I just pushed an updated PR. Turns out the promiseness was getting lost at .eventually for the same reason it was getting lost at .fulfilled, .rejected, and .rejectedWith, so merely having .eventually return this did the trick.
The reason it works without that extra code in .doAsserterAsyncAndAddThen is because .rejected handles the rejected promise and returns a non-promise value here, in this case 42.

@meeber Ah, makes total sense! Yeah, I've seen that that line returns the value the promise was rejected with, but I haven't tought about this. Adding a property which turns on a flag must return this too in order to be caught on that if we've got in the addProperty util.
This LGTM.
Thoughts @keithamus and @domenic?

Just updated this PR to accommodate for additional changes in Chai v4.0. Specifically, every assertion now needs to explicitly return the promisified assertion object or else the promise will be lost.
Also a breaking change in Chai 4.0 caused a single test to start failing because the old deep.property behavior has moved to nested.property. This PR fixes the broken test (although that test now fails in Chai v3.5), which is why Travis says the build is failing. Will update this PR to bump the Chai version once v4.0 is officially released.

FYI chai@4 was just released

@domenic I've updated this PR to support the Chai v4 release.

@meeber is this also compatible with the old chai releases or only with v4?

@Turbo87 It's my belief that this is still compatible with older versions of Chai. I base that only off of running the test suite against older versions. One test fails in older versions of Chai, but it's not a compatibility issue; that test just happens to be using a flag that changed names while testing some other concept.

Hi everyone, I've been getting lots of questions about when this is going to be released and it seems ready to me.
This module is pretty important for our users, so I'd like to ping everyone, especially @domenic to see if we can get this released in a near future.
Sorry to bother you all, I certainly don't want you to rush or feel pressured, I'm just aiming on sending you a notification so that we can decide what our next steps are going to be.
Thanks everyone (especially @domenic) for the hard work and all the effort you've put in this module.

I've been sick recently, and have a lot of work to catch up on as a result of that, so the very earliest this will be addressed is this weekend, but perhaps not even then. I understand a lot of people use this, but my free time is limited, so hopefully people can be patient.

@domenic they sure can. Sorry for bothering you.
Thank you very much for your help and for these awesome plugins ❤

@domenic sick is no excuse!! 😉Be well.

How are things going with this merge? We are currently downloading & working on version from this PR, but we need it on npm to pass the project to the customer.

Just noting here that Chai 4's proxy protection feature doesn't work with this PR. I don't have time to look at it in detail right now. Should be a matter of adding util.proxify on a few return values. I think that could be added later in a separate PR with tests.


Required Attribute not respected

I've a request class like this:
public class CreateTransactionCommand : CommandBase<Guid>
{
    /// <summary>
    /// The number of passengers
    /// </summary>
    [Required]
    public int NumberOfPassengers { get; set; }

But what the documentation generated

NumberOfPassengers (integer, optional): The number of passengers

Why am I doing wrong ? or is it a bug ?

Sorry just found out that i had wrong namespace of the attribute (so it wa sthe wrong attribute which only had same simple typename)


Using SSH client type: external
About to run SSH command:
if ! type docker; then curl -sSL https://get.docker.com | sh -; fi
&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i /Users/russ/.docker/machine/machines/proto/id_rsa -p 22<EMAIL_ADDRESS>if ! type docker; then curl -sSL https://get.docker.com | sh -; fi] []  <nil> <nil> <nil> [] <nil> <nil> <nil> ?reflect.Value? false [] [] [] [] <nil>}
^C
$

Versions
Host: OSX
$ docker --version
Docker version 1.7.0, build 0baf609
$ docker-machine --version
docker-machine version 0.3.0 (0a251fe)

The default ami for eu-west-1  ubuntu-trusty-14.04-amd64-server-20150603 (ami-45d8a532)
Diagnosis
The following steps performed directly on the remote machine allowed curl get.docker.com | sh to complete:
Aborted the create on OSX with ^C, then
$ docker-machine ssh proto
$ sudo  "$(curl -sSL https://get.docker.com | sh)"
modprobe: FATAL: Module aufs not found.   << =============================
+ sudo -E sh -c sleep 3; apt-get update
Ign http://eu-west-1.ec2.archive.ubuntu.com trusty InRelease
Ign http://eu-west-1.ec2.archive.ubuntu.com trusty-updates InRelease
.
.
Hit http://security.ubuntu.com trusty-security/universe Translation-en
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

$ sudo lsof | grep lock
apt-get   2136           root    4uW     REG              202,1        0     149723 /var/lib/dpkg/lock
apt-get   2136           root   18uW     REG              202,1        0     269138 /var/cache/apt/archives/lock

$ sudo kill 2136

$ sudo apt-get install -y linux-image-extra-$(uname -r) << =====================

$ sudo "$(curl -sSL https://get.docker.com | sh)"
+ [ https://get.docker.com/ = https://get.docker.com/ ]
+ sudo -E sh -c apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9
gpg: requesting key A88D21E9 from hkp server p80.pool.sks-keyservers.net
gpg: key A88D21E9: public key "Docker Release Tool (releasedocker<EMAIL_ADDRESS>imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
+ sudo -E sh -c echo deb https://get.docker.com/ubuntu docker main > /etc/apt/sources.list.d/docker.list
+ sudo -E sh -c sleep 3; apt-get update; apt-get install -y -q lxc-docker
+ sudo -E sh -c docker version
$

Conclusion
Must install linux-image-extra prior to installing docker.
Open question
Why was I able to successfully run the same command successfully yesterday, using the same AMI, under what I think are the same conditions?

Related to #1324?
Note: sudo apt-get install -y linux-image-extra-$(uname -r) when carried out as shown above is very slow (> 8 mins).
It's consistently failing for me today, but succeeded several times yesterday. Several comments on #1324 point to intermittent failure.
Race condition?  Repo availability issue?

Could be related to the region as well. The same thing that fails on eu-west-1 successfully completes on us-east-1

The provisioner code and default AMI have changed quite a bit since july.
I'm going to close this, if you feel like this is still happening  with the 0.5.3  feel free to re-open.


Namespace dropdown (in header) use on all pages

With the namespace dropdown moving to the header so that it is globally available on all pages, we need to think how this will impact other pages (like listing and detail pages). And more specifically, how the use of the 'All' namespace is relevant to those pages.

UxD document: https://docs.google.com/document/d/1ca9ug0U0InEPSNjGvu4AEZBRJVVeIItvDjRFn62laHU/edit?ts=5b1f27b7
Jira adding namespace to header: https://issues.jboss.org/browse/KIALI-943

It was not my understanding that the namespace dropdown is expected to be available and visible at all times at the main toolbar while the other pages can be navigated (from graph to services and etc.)
But I might have misunderstood.
@cshinn @serenamarie125 was this the intent? Is this the standard in other apps too that the namespaces dropdown is always at the top?
If that is the case, then services list filter should be changed not to include the namespace, and if user selected namespace X in the graph, navigating to other pages should "respect" that selection.
That also means that if some screens have less relevance to a specific namespace (maybe Istio Config? @lucasponce ) , something has to be done about it.

Technically, Istio configuration items are "namespace-bound" - by that I mean, these configurations like Virtual Services, Destination Rules, and the like are stored in namespaces. Its just the Istio Config section of the UI has its own namespace filter in place (by default it shows all istio configs in all namespaces) - you can filter these by namespace though:

@jmazzitelli indeed, so how would Istio Config be handled? reset the namespace in the main panel when navigated there? otherwise in a lot of cases user will have to reset it manually every time they navigate there. And also they will need to know to which namespace it should be reset to view Istio Config.

The thought is that it will be available at all times, and that you would remove the Namespace dropdown from your filter panel.  We would have an "All Namespaces" item as well.
This is consistent with what we are doing in OpenShift, and it's working very well.

2 use cases that need to be solved if the namespace selector is visible at all times and influences all screens (@cshinn this is what I brought up during our meeting)

the overview page which reflects all namespaces. If a single namespace is selected, only one card will show on that page.
the Istio Config screen. This screen reflects some Istio specific configuration which is typically deployed in a very specific namespace (for example istio-system). So if another namespace is selected to view the workloads/services of the user's apps, navigating to this page will almost always display as empty and require from user resetting the namespace to the istio namespace.

@cshinn please update the design changes that we discussed in today's meeting to this issue (or at least some relevant links).

@abonas are we able to tell which namespace(s) the istio config stuff is displayed in? or is it just a matter of the user knowing and switching to the appropriate one?

@jotak @lucasponce see ^^ - We had an issue open about Istio deploy location iirc. Is there any setting which we can retrieve this info from? Or only the user would know?

There is a config variable that sets the "istio-system" namespace, and I guess that can be used to show where istio is deployed.

@abonas I'm just chiming in about Istio Config screen

if another namespace is selected to view the workloads/services of the user's apps, navigating to this page will almost always display as empty

I'm not sure about that: if it's true that "istio-system" holds all the global istio configuration, afaik when we create virtual services / destination rules / etc. we do it in our application namespace, not in istio-system (at least this is how I do when i'm playing with demoes). So even for this screen I would say it still makes sense to follow the global namespace selected.

@jotak's comment is right.
I understood that @abonas asked where the Istio where installed (i.e. istio-system) which will hold part of the configuration, but yes regular Istio config objects belongs to a specific namespace.
Also, as I think I commented before, there are some objects that are in both, some templates will hold in the istio-config namespace and others in the users namespace (i.e. bookinfo).

For me it's not clear to be honest.
It's clear that when we are located under a single entity (service, workload, istio object) that belongs to one and single one namespace, so in that case, select that namespace in the widget proposed by UX makes sense.
But multi-namespace filtering is something that is going to be used by users (this also requires some sync with the multitenancy efforts) BUT in any case, a user with admin privileges to see all namespace will like to filter by multiple-namespaces.
So in that cases (the list views), I don't see the suggestion to maintain the namespace selected. So, the widget should maintain a list IMO.

Indeed the list views offer multi-selection on namespaces right now, so ignoring it would be a regression in that regard.
But we could use the patternfly's "checkbox filter" ( https://www.patternfly.org/pattern-library/forms-and-controls/filter/ ) and that would make it, no?

@jotak I think that multi selection on namespaces should not be available at the moment, please see this discussion on multi selection of services, I think this is similar:
https://github.com/kiali/kiali-ui/pull/534#issuecomment-408090706
in any case we can clarify it again with @serenamarie125 and @cshinn

Why multiselection on services and namespaces is not available ?
That is clearly a regression.
I start to see a recurrent concern that we introduce these regression on the existing logic.
We may have multiple productpage-* and details-* elements and we may want to group them multi selecting "product" and "details". A similar scenario happens with namespaces.
I wasn't aware of the PR discussion of 534 but I would not approve that if I could it reviewed.

@lucasponce we need first user stories for the multi-X approach. When you are allowing selection of multiple, there should be strong use cases for it.
Do we have today a use case for selection of more than 1 entity? We can support for example "abc*" to see all services that have 'abc' in their name for quick search. But selecting several at once - what use case? (I'm not saying there aren't, but I can't provide any myself)
And if user selects 10 namespaces and 10 services at once, this is very hard to manage from UX perspective - you need to show in the filter all the selections together.

@lucasponce we need first user stories for the multi-X approach.

We have a current implementation with some functionalities in place.
As commented, I want to select "productpage" and "details" in my service list to compare.
That's implemented.
It's quite normal that a user will select in Istio Config "istio-config" and "bookinfo" namespaces and it will select "details" to take:

all details-* VirtualServices / DestinationRules for details.
all quota templates objects that are defined between both namespaces.
select just those that are relevant for the "details" scenario.

So, the use case is valid. Indeed, that is how user works using text files, and that's what we brought in the initial implementations.
Removing them just from UX perspective is a regression.

Just FYI:
Here is Chris's new namespace design from the meeting:

@cshinn I'd like to make sure everyone are on the same page about this change - the beginning of this thread shows a screenshot where namespace selector is visible at all times at the top header.
Here in the comment above mine, there is a slightly different design where the namespace selector is in the lower panel, seems that it should be readded at each page separately?
What is the correct one to implement?

We are holding on this until we have a finalized direction.
As we discussed @mwringe in our meeting on Friday.

@abonas I apologize for the confusion. The image at the top of the PR is incorrect. The one in @mtho11's comment just above is the right one. I have a PR documenting this and the breadcrumbs almost ready and it should be showing up in the near future.

@mtho11 this should be addressed in #32 - please confirm, so we can close this

@abonas yes this can be closed since #32 supersedes it.


Update directory to have filter sidebar and use nextJs image

Also created new components to be used on the directory page

This looks really good! To be sure I understand, this PR also changes the implementation of the grid used in the directory, in addition to moving it into a reusable component?

Additionally, if react-simple-flex-grid can be removed with this change then that may resolve some of the additional issues we've been running into.

Yeah, we can use tailwind for most of our styling needs. We can eventually migrate to not using any outside CSS and then remove the dependency if the team feels that that would be good

Let me know if that looks a bit better. I added a border around each card so they would be easier to tell apart.


[Feature Request] Add arrow symbol when accepting input

Summary

Added arrow symbol (↳) when reading input from the user
Added .github folder for containing GitHub related assets
Added updated example screenshots
Referenced README to the raw github content URLs for the screenshots

Failed build is caused perhaps by the travis configuration. Let me know your thoughts.

The feature(s) are fine. However, I question having image assets showing what the program looks like via a Markdown interpreter (which is usually done via a browser) that are possibly going to change frequently inside of the repo.
The PNGs will most likely continue to change each time we have a new feature, and these are not easily compressible via git since they are binary object blobs. This means that git operations, such as clone, will increase, as well as the repo size. Rather, I think it is more prudent in the long run to have these solely hosted on GitHub's CDN.
In the extreme case, it would cause the image links to break when interpreting the Markdown if GitHub is down or there's no access to the Internet. That, to me, is a more of a minor inconvenience and worth dealing with vs the inverse effects of having possibly hundreds of PNGs in git's history that don't do much more than show what the program looks like when viewing this project a few years down the road.
I'm more than welcome to hear a counter argument to this and why placing image assets inside a folder that stays with the repo is a good idea, though. I am simply basing this off of years of experience at my current workplace which tends to have heavily firewall'd and slower Internet connections, as well as having to do everything on SMB shares - both of which increase the length of time it takes for git to perform its operations.

Double-checked this feature request. The ↳ symbol appears to be missing from my default font on my WSL instance. It makes me weary that U+21B3 may not be visible on all shell instances by default using certain fonts. There seems to be an ongoing issue with WSL and UTF-8 in general, but it may persist on other, older *nix distros which might not have this symbol immediately available and cause some users to think this could be a bug. A previous pull request is utilizing the > symbol as an alternative which is available in ASCII and other character encoding standards. Thoughts?

Thanks for looking into this, will have to check a viable character for this PR.

Good point, but let me check how far I could optimize the images to conform with slow networks. Otherwise, will remove it and lean towards Github's CDN urls generate here automagically. :)

The layout and presentation of this pull request was great, and there were some solid features suggested in here. Thank you! :)
However, I'm going to close this pull request for now for a few reasons. Normally, the .github folder is for issues and pull request templates, so I'm not sure if this is the appropriate place for images (if it is, feel free to reference documentation as I'm more than happy to revert my decision). The other is the Unicode issue mentioned earlier when I ran this in WSL. #65 has a good alternative solution to the Unicode issue, in my opinion, and I think we will go with that because the greater than symbol (>) is an ASCII symbol and backwards compatible with almost all character encoding sets.


Fix nested & named outlet route paths

resolves #917
resolves #914
@rajinder-yadav While addressing this I noticed that we were also not computing the path properly for named outlet routes. What was previously /parks/park3 should be /parks/(parkit:park3), where parkit is the outlet name. This PR fixes that too.
Edit: I've added the fix for #914 here also.

:shipit:


PlaceHolder not working

Describe the bug
PlaceHolder does not work with /cal which comes from animated texture pack (For No Plugin), the placeholders of the 5th and 6th days of the seasons that are affected. Spring, autumn and winter, since summer has no modified GUI items
How to reproduce
^^
Screenshots / Videos
No response
Server Log
No response

Which placeholders doesn't work?

Calendar placeholders only works on the SPRING - SUMMER - WINTER - FALL sections below settings section by the moment:


⚠ Bofrost.be has degraded performance

In 0c44c52, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 868 ms

Resolved: Bofrost.be performance has improved in 1ab9597 after 13 minutes.


mdp: disable tests

Motivation for this change
Disable tests because it has dependencies that aren't in nixos (shogun, pp, etc...)
Related to #28643
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Pushed 140136ad9567a23b0d88ca014b2604e1820d74f2


bblayers.conf: remove meta-qt5 unless QtAS

We only need meta-qt5 in our bblayers.conf if we want to build with Qt,
meaning that we want to build the QtAS variant of PELUX. In all other
cases we don't need any Qt support.
Closes #51
Signed-off-by: Tobias Olausson<EMAIL_ADDRESS>

@DunderRoffe updated


Отказывается устанавливать script Run code in Atom!

script
Run code in Atom!
Installing<EMAIL_ADDRESS>failed.Show output…

I had the same issue...
The error message reads:
"Some installed packages could not be loaded because they contain native modules that were compiled for an earlier version of Atom."


Start preliminary work on providers

add an sqh_provider g: var
call this for all the functions instead of the hardcoded mysql
document it

https://github.com/joereynolds/SQHell.vim/commit/c1cc1cb1a458f926cbb2abe65187c9f044b663ea


Add vocab slides

Here's an experiment using the video:

The issue is that I couldn't find a way to programmatically embed the video from Google Drive (I had to manually download and use the local file). We might need a different way to get the video directly, or perhaps get the vocab helper slides in a different format (images, or computer-parsable text file)

Hi Levente! Thanks for developing this transcript player. I'm interested to contribute somehow to this project, which I find to be interesting as I'm also one of Easy German patreon.
On integrating the Vokabelhilfe, wouldn't it actually be an easier solution to use the CSV file instead of the video and embed that into the line which contains that word itself? That, in my opinion, can be on top of the translation feature or in place of it.

Hi @natashaw – Thanks for the idea. It would be easier to parse the CSV, but I think it would be too difficult to match it to the correct word, since most of the time they're used in a different form than the "dictionary" version, e.g. in plural, in declined form, separated, etc.

People are asking specifically for a combined transcript scroller and vocabulary helper. I'm not sure how to solve the problem, but here are some ideas/questions:

If the video can't be pulled from Google Drive, can we just upload it somewhere else? The video files are between 50 and 200 MB each, so we'd need 1 GB of storage per month max. I'm unsure how much traffic there would be. What about a dedicated YouTube account for this, where we publish the videos as "unlisted"? (Unlisted videos can be embedded on websites.) We'd still want people to be able to download them, thought, so we'd have to do both.

Maybe the same functionality can be achieved with other files/data instead of the video? Maybe it would even be better, since the square aspect ration of the Vokabelhilfe is really meant for podcast apps? (How would the example Levente posted above fit on a mobile screen?)
Here are some of the other files and more info from our production workflow in case any of this helps (this is all from EGP 30):

The Vokabelhilfe.txt file has all of the vocabulary and translations, formatted as Photoshop variables. (We import this file into Photoshop to generate the chapter files.)
The image changes every full minute, with minor exceptions: The first one starts after the intro (around minute 0:14 usually) and when a new segment begins almost on the minute-mark, we  move the switching of the image to that mark, so the regular chapter mark (for the segment) doubles as the chapter mark for the new Vokabelhilfe image. For example, on episode 30, the image for Vokabelhilfe 49 comes in at 00:47:52.569 already instead of 00:48. Also, since there is no Vokabelhilfe for the Bonus at the end, it goes back to the cover there. Here is the chapter file for EGP 30 (this is automatically generated for each episode):
egp30_Chapters-File.chapters.txt
(For simplicity's sake, it would also be "good enough" if a new image comes in at each full minute, starting with image 1 at minute 0:00, image 2 at minute 1:00 and so on.)
Here are the raw chapter images as PNGs for episode 30:
egp30_images.zip

Thanks! Manuel

@EasyGerman
I managed to get images and chapter timings out of the mp3 file, so we can either display the image or display the words from the plain text using the chapter timings from the mp3.
For mobile, I think we can add a button to toggle between the transcript scroller and the vocabulary helper.
I also plan to do some experimentation on locating the words in vocabulary helper in the transcript based on part of the word.

@bagilevi If you can pull the chapter images from the mp3, that's probably the easiest in terms of our workflow, since we won't have to upload the plain text anywhere. Your second idea might require that file though? A toggle to switch between with and without vocabulary helper sounds great!

Done

I know this issue was closed but I feel the same as @natashaw that having the vocable help in a text could better improve the experience and I think images are ok for a podcast app but not for this interactive transcript app.
I played a little with this idea, what happens to me is that when reading the translations I can not keep good track of the vocable words when they are used in the text. It would be great to have them like in bold or somehow bigger fonts, so I can see when it used and what it means without having to stop/pause stop/pause.
I find it challenging because you have the whole list of vocabulary words, not the timestamps...if the file that contains the vocabulary would have the times that functionality would be possible. The images are not useful in this interactive transcript (they are useful in the podcast apps but not here).
Something like this would help:
[00:00] der Korken - the cork
[00:00] mitbringen - bring along
....
...
[00:59] hilfe - help
[00:59] hilfe - help
[00:59] hilfe - help
[00:59] hilfe - help
[00:59] hilfe - help
....
....
[03:00] hilfe - help
[03:00] hilfe - help

This way we know the exact 9-10 or more words that are in each minute, having the whole list we can not say what is currently going on.
I played with this idea, so I am doing bold in words that are in the vocabulary but I can not mark only words that are present in the current minute but I compare with the whole list of words in the vocabulary (not ideal by performance and not the context - maybe the word appears in this moment but the vocable Hilfe was 3 minutes ago).
@bagilevi @natashaw @EasyGerman Not sure what do you think about it, I think it could be very useful at least for me.
I would attach a gif of what I am thinking about.

This is just an idea, we could improve, of course, there is the limitation you mentioned that some times words do not appear in the text exactly as in the vocabulary list but this can be solved easily by just adding this in the file (like the word as it appears, is just a matter of adding a little more information to that text or rtf file)

I will create a new issue so maybe it gets noticed by you guys.


Inactivity in regards to link cable support and save backups

Not a bug.

for reference https://github.com/gameplaycolor/gameplaycolor/issues/55


sentinel config problem

code like this:
\Predis\Autoloader::register();
$sentinels = ['tcp://<IP_ADDRESS>:10005', 'tcp://<IP_ADDRESS>:10006'];
$options = [
    'replication' => 'sentinel',
    'service' => 'mymaster',
];
$client = new \Predis\Client($sentinels, $options);
$client->set('foo', 'bar');
$value = $client->get('foo');

then cause an error:
An instance of type 'Predis\Connection\Aggregate\ReplicationInterface' was expected.
FILE: /home/tellmewhy/www/ThinkPHP/Library/Predis/Configuration/ReplicationOption.php 　LINE: 49
I read part of the relevant code,seems $value eq sentinel can`t be the right config.poor english,sry!

You should at leat indicate which version of Predis you are using.

1.0.4 from predis\VERSION file,

Predis v1.0.4 does not support sentinel, you should upgrade to v1.1.

thx very much.


Setup CI and publish artefact

automatic build (incl. coverage)
publish jar to maven central etc.

travic CI and coveralls set up, producing artefacts and publishing to maven central pending (https://issues.sonatype.org/browse/OSSRH-14097)

available on maven central


Email validation for team contact

For payment process, we need to provide to third party payment an email.
problem: the team email contact is not verified.
add a property email verified to team
add a flag "mail no verified" in UI when we need this team email (like paied subscription)
add the entire process to verify the email

first step

[x] flag team as validated or not
[x] handle validation on team creation (create a token, save it & send by mail)
[x] handle validation back by mail

second step

[x] write an evolution to flag 'no verified' all created teams
[x] display state in UI
[x] display a button to re-send a verification mail (create an API to do this)

third step

[x] handle mail update

https://github.com/MAIF/daikoku/pull/524


Update trusting self-signed certificate docs

Summary Of Issue
On Office for Mac 2016 (v16.21), when trying to sideload an add-in, you have the ability to trust the certificate without having to manually add it to your keychain. You should describe this as it is a much easier, method if it is possible on all versions of MacOS or Word. I am running on MacOS Mojave, though it could be possible that older versions of MacOS do not support adding trusted certificates this easily.
The bullet point 4 from the link below is the specific instruction step to be updated.
Article URL
https://docs.microsoft.com/en-us/office/dev/add-ins/tutorials/word-tutorial#create-your-add-in-project

Hi @Alex-Mann I created a PR to update the page with simpler steps. Details at https://github.com/OfficeDev/generator-office/pull/423
However I noticed you got this to work without using the keychain. I couldn't find a way to do that. Can you provide more info on how to do that? Thanks!

Hi @Alex-Mann
Closing this issue, however if you have more information to share let me know and I’ll be glad to re-open it. Thanks!


[WIP] Externalize CommandLine and maybe wildmenu (?)

This is the initial work I've done so far. I kind of just took bits and pieces and threw things at the wall to see what stuck. I'm sure this is going to need a ton of revision and a ton of extra work.

[ ] Handle recursion with the CommandLine

[ ] Handle the cursor/position within CommandLine

[ ] Find out what values should be configurable

[ ] Determine what CommandLine should look like/ where it should be placed.

Sorry this is super bare in terms of commits, I very nearly deleted all of the changes I made... :man_shrugging:

Wow, excellent progress @Bretley ! Looking really cool from the gif.
And the code changes look great so far. I like the way you wired everything up - looks like you have a good handle on React + Redux 😉 Left a few minor comments.
I saw the cases for wildmenu_show, wildmenu_select, and wildmenu_hide - are you planning on including the wildmenu externalization in this change too? I'm okay either way.

@bryphe Wildmenu might or might not get done depending on how your vision of this looks. There are three ways I could see this going:

CommandLine becomes a Menu: Neovim sends over a cmdline event and the wildmenu functionality is instead replaced by fuzzy-style completion based on some list of keywords we have. This keeps 95% of the work in Oni and only requires that we have some precomputed list of help terms.

We keep neovim's version and have it in the usual spot, but instead it's a cool little textbox instead of a part of the actual neovim screen. Even if we don't do much, externalizing the 'static' parts of the neovim screen is a step we need to take in order to get more advanced scrolling/ externalize the actual text display.

Some hybrid of these two. It would be pretty easy to make cases for search vs ex mode vs. whatver ? means because neovim lets us know which commandline functionality is being used

Personally, I don't want the search to be over the screen because it might be covering up text,
but I do think that a popup commandline would be cool.
This is really a design choice for you.

Cool, nice summary @Bretley !
Initially, I think it makes sense to keep the command line separate (implementation-wise) from the quick open / command palette menu. There's two 'classes' of users I want to appeal to - Vim veterans who expect/know the command line, and new users who want to get start with modal editing - may be more comfortable in the quick open/command palette. Keeping that distinction now can satisfy both 'classes' of users, and then we can look towards ways to reconcile them later, if it makes sense.
I do like the way you've structured the UI right now - having the command line pop in an overlay is really nice! Good point about the search, though. I wonder if, in that case, we could put it in the corner - sort of like how in Chrome it pops up in the corner?
Regarding the wildmenu, if we use the UI-overlay like you've structured it, we could make the look and feel similiar to the quick open / command palette menu (even if the implementation is different) - I think it would help both classes of our users (for the vim veteran, getting adjusted to some of the new UX paradigms in Oni, and for the new user, it won't feel that different / scary from quick open or command palette).
Hope that helps and wasn't too vague... Great work so far!

Hope we can have a configuration to disable this without the overhead of it's implementation.
Although I think this is a great feature it's very obstrusive visually for the edititing flow.

I'll try to smoothen this out so that it can be merged. First need to see I can get it working.

I'll close this out since we have #1177 and #1179 in now


Remove '

Not sure why but the faq file was ending with a '

Coverage remained the same at 39.68% when pulling ef03160d5e8e0a054cc021ab509698f107dc71d9 on remove-' into 46c30a88bf1577ca80ac2f1b56ebf87c30088d03 on dev.


why does roi_data_layer forward twice in one solver step?

I tried to train rfcn_end2end_ohem.
In /roi_data_layer/layer.py , I added  print "forward RoiDataLayer" in forward() (line 146).
In fast-rcnn/train.py, I added
for layer_name, blob in self.solver.net.blobs.iteritems():
print layer_name+'\t'+ str(blob.data.shape)
in train_model() (line 148).
The output is
forward RoiDataLayer
forward RoiDataLayer
I1110 11:00:53.827004 25709 solver.cpp:228] Iteration 0, loss = 3.86447
I1110 11:00:53.827035 25709 solver.cpp:244]     Train net output #0: accuarcy = 0
I1110 11:00:53.827045 25709 solver.cpp:244]     Train net output #1: loss_bbox = 0.0267997 (* 1 = 0.0267997 loss)
I1110 11:00:53.827050 25709 solver.cpp:244]     Train net output #2: loss_cls = 3.04452 (* 1 = 3.04452 loss)
I1110 11:00:53.827055 25709 solver.cpp:244]     Train net output #3: rpn_cls_loss = 0.693147 (* 1 = 0.693147 loss)
I1110 11:00:53.827060 25709 solver.cpp:244]     Train net output #4: rpn_loss_bbox = 0.111002 (* 1 = 0.111002 loss)
I1110 11:00:53.827067 25709 sgd_solver.cpp:106] Iteration 0, lr = 0.001
data	(1, 3, 600, 943)
im_info	(1, 3)
gt_boxes	(1, 5, 1, 1)
data_input-data_0_split_0	(1, 3, 600, 943)
data_input-data_0_split_1	(1, 3, 600, 943)
im_info_input-data_1_split_0	(1, 3)
im_info_input-data_1_split_1	(1, 3)
gt_boxes_input-data_2_split_0	(1, 5, 1, 1)
gt_boxes_input-data_2_split_1	(1, 5, 1, 1)
It seems that it runs forward twice in one solver step, besides I'm sure IMS_PER_BATCH: 1.  why is that ?

Because I use iter_size: 2 in end2end training. Since RPN only supports IMS_PER_BATCH: 1, we usually use this way to support batch_size = 2. Please check Caffe's code for more detail.


if I can run it under fabric 1.4?

I got the master branch of marbles,and when i run it under fabric1.4,here are some problems

in fabric1.4,/fabcar/hfc-key-store has been replaced as /fabcar/javascript/wallet, and I fixed this problem by modifying connection_profile_lacal.json.

but here is new problem,when I try to run node install_chaincode.js,it shows

---------------------------------------
info: Lets install some chaincode - marbles v4
---------------------------------------
info: First we enroll
debug: loading pem from a path<EMAIL_ADDRESS>debug: loading pem from a path: /home/cyan1/go/src/github.com/hyperledger/fabric/fabric-samples/basic-network/crypto-config/peerOrganizations/org1.example.com/users/Admin<EMAIL_ADDRESS>info: [fcw] Going to enroll with admin cert!  peer_urls=[grpc://localhost:7051], channel_id=mychannel, uuid=marblesDockerComposeNetworkmychannelOrg1MSPfabricpeerorg1, orderer_url=grpc://localhost:7050, msp_id=Org1MSP
debug: added peer grpc://localhost:7051
debug: [fcw] Successfully got enrollment marblesDockerComposeNetworkmychannelOrg1MSPfabricpeerorg1
---------------------------------------
info: Now we install
---------------------------------------
debug: [fcw] Installing Chaincode
debug: [fcw] Sending install req targets=[grpc.http2.keepalive_time=300, grpc.keepalive_time_ms=300000, grpc.http2.keepalive_timeout=35, grpc.keepalive_timeout_ms=3500, grpc.max_receive_message_length=-1, grpc.max_send_message_length=-1, grpc.primary_user_agent=grpc-node/1.10.1, _url=grpc://localhost:7051, addr=localhost:7051, , _request_timeout=90000, , _name=null], chaincodePath=marbles, chaincodeId=marbles, chaincodeVersion=v4
info: [packager/Golang.js]: packaging GOLANG from marbles
error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: 14 UNAVAILABLE: EOF
    at new createStatusError (/home/cyan1/go/src/github.com/marbles-master/node_modules/grpc/src/client.js:64:15)
    at /home/cyan1/go/src/github.com/marbles-master/node_modules/grpc/src/client.js:583:15
error: [fcw] Failed to obtain endorsement for transaction. code=14, , details=EOF
error: [fcw] Error in install catch block object code=14, , details=EOF
---------------------------------------
info: Install done. Errors: parsed=Blockchain network error - EOF, raw=[code=14, , details=EOF]

and how can I fix it?

I have the same problem as you，How did you solve it？

sorry @aonoa but this marbles repo is unsupported these days. it was archived and moved to the IBM-Blockchain-Archive org.  unless this project gets rejuvenated, I wouldn't expect any help.  you may want to check out the other Fabric example in fabric-samples. fabcar is pretty popular.

sorry @aonoa but this marbles repo is unsupported these days. it was archived and moved to the IBM-Blockchain-Archive org. unless this project gets rejuvenated, I wouldn't expect any help. you may want to check out the other Fabric example in fabric-samples. fabcar is pretty popular.

Thank you for your reminder，I saw that some people have successfully configured it, I have tried many versions, but also encountered more problems, I can not solve them, can you tell me a method that can be successfully configured, such as marbles, fabric-samples , Node version combination, I think it may be caused by this reason failed.

对不起，@ aonoa，但是最近这些弹珠储存库已不受支持。它已存档并移至IBM-Blockchain-Archive组织。除非这个项目恢复活力，否则我不会期望任何帮助。您可能想查看fabric-samples中的另一个Fabric示例。fabcar非常受欢迎。

Thank you for your advice. I was forced to use the older version and successfully run marbles,


Controlling the swipe threshold for delete

My users are telling me that the swipe action doesn't trigger easily enough the delete action. As an example they show me the Gmail app. It is true that just a small swipe is enough to trigger the complete swipe of the item in this app. Would it be possible to control the sensitivity of the swipe to trigger the action attached (in my case a delete)?

Hi. Thanks for the suggestion 👍  I will make it configurable, so please wait for a few days.
NOTE: Current threshold is hard coded on the following line;
https://github.com/h6ah4i/android-advancedrecyclerview/blob/0.9.1/library/src/main/java/com/h6ah4i/android/widget/advrecyclerview/swipeable/RecyclerViewSwipeManager.java#L413

Hi. I have introduced the void setSwipeThresholdDistance(int distanceInPixels) method to RecyclerViewSwipeManager in develop branch code. This improvement will be included in the next release, or you can try it now via JitPack.
repositories {
    maven { url "https://jitpack.io" }
}

dependencies {
    compile 'com.github.h6ah4i:android-advancedrecyclerview:69dced818128e2a3380de8a69478aa431edbc5ab'
}

Hi, Thanks a lot for that very fast improvement :) I saw that threshold constant in the source but was not sure it matched this behavior. I will test it in my app and include it in my next release once it gets in yours :)

@OzTK Hi. The setSwipeThresholdDistance() method is now available in the v0.9.2. Thanks!


Dovecot quota_max_mail_size to use the Chatmail max_message_size value

for consistency with the limit applied to Postfix

on main it seems to work :)


[core] Pin GitHub Action to digests

The idea is to follow https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions

You can help mitigate this risk by following these good practices: Pin actions to a full length commit SHA

It uses: https://docs.renovatebot.com/modules/manager/github-actions/. If it works well, we need to apply it to all the other repositories.

Does it work with GitHub Actions? The docs for pinDigests mention Docker images only.
The doc you linked offers an alternative config setting:
{
  "extends": ["helpers:pinGitHubActionDigests"]
}

Does it work with GitHub Actions? The docs for pinDigests mention Docker images only.

@michaldudak The support for GitHub Actions was added in https://github.com/renovatebot/renovate/pull/10835.

The doc you linked offers an alternative config setting:

These two are equivalent. I went with the lower level primitives

https://github.com/renovatebot/renovate/pull/18578 got merged, so we are likely good. We will see how this goes in the next Renovate PR update cycle.


Problem with get_historical_quotes in tradier.py

Function cannot return 'weekly' data. It can only return daily data over specified interval.
Example:
quotes.get_historical_quotes('CF', interval = 'weekly')
Error message:
ValueError                                Traceback (most recent call last)
Cell In[20], line 1
----> 1 quotes.get_historical_quotes('CF', interval = 'weekly')
File ~\OneDrive\Documents\Tradier\tradier\tradier.py:357, in Quotes.get_historical_quotes(self, symbol, interval, start_date, end_date)
344 	start_date = last_monday(tmp).strftime('%Y-%m-%d');
346 r = requests.get(
347 	url 	= '{}/{}'.format(self.SANDBOX_URL, self.QUOTES_HISTORICAL_ENDPOINT),
348 	params 	= {
(...)
354 	headers = self.REQUESTS_HEADERS
355 );
--> 357 return pd.DataFrame(r.json()['history']['day'])

GPT Explanation:
The error message indicates that the datetime module does not have an attribute today. This is likely because the datetime module indeed does not have a today function at the top level; instead, the today function is a class method of the date class within the datetime module.
To fix this issue, you should make sure that you are importing the date class from the datetime module correctly at the beginning of your script. The correct way to access the today method is through the date class like so: datetime.date.today().
Here's how the import statement should look:
python
Copy code
from datetime import datetime, timedelta
And when you want to call the today method, you should use:
python
Copy code
end_date = datetime.date.today().strftime('%Y-%m-%d');


[SLD-Parser] Complex Polygons are not parsed

Currently the sld-parser only parses the fill and stroke property of the polygons in a sld rule and doesn't  consider other cssParameters such as stroke-dasharray or GraphicFill. In addition the parser fails to consider multiple PolygonSymbolizers.
Example Sld is a sample SLD that the parser needs to be able to parse.

This should be split into sub-issues and related issues:

https://github.com/terrestris/geostyler/issues/214
https://github.com/terrestris/geostyler/issues/248
https://github.com/terrestris/geostyler/issues/249

The sub-issues will be listed as TODO-list in this issue's description.


Bugfix/td 1565 dark mode model button overlay

Contributes to TD-1565
Changes
The previous implementation used a sudo element to sit over the bottom right corner of the model button, and replace the standard corner border with a cutout corner border.

This worked well where the background was a consistent and known colour as shown here in light mode. However, in dark mode the background colour could differ, especially when the ModelButton sat in a Paper panel with a hover effect that modified the elevation. In dark mode that changes the background colour (https://mui.com/material-ui/react-paper/#elevation) unlike light mode. Hence the overlay became the wrong colour and you could see it.
https://github.com/IPG-Automotive-UK/react-ui/assets/27866636/323ea2c4-26fd-418e-a028-a0fb8da8d936
The solution to this was to change our approach entirely. The new implementation uses two SVG representations of a button when it has children and when it doesn't. These SVG components are wrapped in a MUI SvgIcon component, and take in the borderColor and backgroundColor properties. This allows the parent button to control how it is displayed. This SVG is displayed within the Button, with the button icon displayed absolutely over the top. This solves the original issue, and now exactly matches the Figma design in terms of shape.

Then I noticed that in Figma, the icon displayed within the button should also change its hover color. This proved more difficult. Since the svg icons are hosted externally to the services using this component, we display these SVG icons in an <img /> tag. This means that we cannot use the SVG fill property, or CSS fill property to colour it.
Instead I've adopted a CSS filter approach using some of the learning described here: https://stackoverflow.com/a/43960991. Assuming that the original icon is black, it converts the target colour to a set of CSS filters in the format filter: invert(a%) sepia(b%) saturate(c%) hue-rotate(θdeg) brightness(e%) contrast(f%);. This can then be used to style the <img /> tag.
Additionally I have introduced a cache to the color2filter utility function so that we need not recalculate the transform repeatedly.

While here I also converted these components to Typescript. I had to correctly type SVG imports for use in Typescript files. See here for a description of the problem.
UI/UX
I have created integration branches for VIRTO.BUILD and VIRTO.MODEL that you could spin up to test.
I have also given @Sowbhagya-ipg a brief demo, but for the sake of completeness, here are some screenshots.

Testing notes

I have updated the stories to use more representative icons.
I have added a story showing a ModelButton on top of a Paper card. The story allows you to modify the Paper elevation to prove that it works as expected in dark mode.
I have added a test to ensure that a ModelButtonImage shows the correct colour when requested.

Release Notes

Updated ModelButton to correctly render the corner cut-out when the button has children. Previously this could show a mask in a different colour than the background colour upon which the ModelButton sat.
Updated ModelButton and ModelButtonImage image so that the ModelButtonImage changes to the primary palette colour on hover.

[x] Relevant labels added to the PR.
[x] Appropriate tests have been added.
[x] Lint and test workflows pass.

Looks Good! @mattcorner

If I hover over the dropdown button, it just highlights the dropdown, which makes sense.
If I hover over the main button it highlights both the main button and the dropdown button. Should it not really only highlight the main button because they are two separate buttons with two separate actions? I see Figma is also implemented like you have here so I just want to confirm this with @Sowbhagya-ipg.
No hover.

Hover on dropdown button.

Hover on main button.

status prop in Storybook should be a dropdown not text field.

Missing prop descriptions in Storybook.

I notice that the ModelButton doesn't appear in the coverage report on the GitHub action. Potentially a few components are missing actually. Is this a result of the migration to Typescript?

If I hover over the dropdown button, it just highlights the dropdown, which makes sense.
If I hover over the main button it highlights both the main button and the dropdown button. Should it not really only highlight the main button because they are two separate buttons with two separate actions? I see Figma is also implemented like you have here so I just want to confirm this with @Sowbhagya-ipg.
No hover.
Hover on dropdown button.
Hover on main button.

You may be right @dmbarry86. Now, I checked with other sites for this type of button behavior, and some have used this way and most others have hover interaction separately for each button. @mattcorner Can you keep it the same way as it is devel now, please?


API is down

Attempting to use this for a bootcamp project, but it seems to be down. Will it be coming back up soon?

Duplicate of https://github.com/lukePeavey/quotable/issues/143.
Also can confirm that the API is down for me.

Fixed


ApplePay Show [General] Connection to remote alert view service failed

When I try to pay with ApplePay it shows the following error:
[General] Connection to remote alert view service failed
ApplePay is Active on PayTabs:

Also, Apple Pay works on the website but not on the app
startApplePayPayment method:
FlutterPaytabsBridge.startApplePayPayment(configuration, (event) {

        if (event["status"] == "success") {
          successPayment();
        } else if (event["status"] == "error") {
          // Handle error here.
          _Result =  'An Error Has Occurred, Please try again later';
        } else if (event["status"] == "event") {
          // Handle events here.
          _Result = "Something went wrong";
        }
    });

Note: I removed setState because it shows another error #10

We will check it and back to you tomorrow ISA

Hi @ibrafayez
If you are using StatefulWidget so you should use setState() to update your widget state, And regarding the issue, it is not related to ApplePay functionality, please try to print the event in your startApplePayPayment or try to run our sample app just to make sure the issue not related to PayTabs flutter plugin.
Waiting for your reply
Thanks

I updated flutter_paytabs_bridge to 2.0.4 👍
I added "print(event)" in startApplePayPayment and I got:
[General] Connection to remote alert view service failed
flutter: {status: event, code: 0, message: Cancelled}

I also tried your sample app:
On the simulator it works fine (It made me happy at first), but not when I build the app on my phone.
on my phone I got same error as my project.

Kind Regards

did you configure your app for apple pay and merchant id?

Yes for my app I configured for ApplePay and added the apple pay id

configuration:

send me a message to muhamedadly AT gmail.com or m.adly At paytabs.com to arrange a technical support call.

Sent,
Thank you

Any updates on this? I'm having the same error.

Yes for my app I configured for ApplePay and added the apple pay id

configuration:

Hello @MuhamedAdly I'm having the same issue
everything is all set, normal payment is working smoothly
but having 'cancelled' in response on Apple Pay

Did you follow the steps in the guide to setup Apple Pay certificate:
https://github.com/paytabscom/flutter-sdk-bridge/blob/pt2/ApplePayConfiguration.md

Thanks for the fast response, actually I was just verifying all parameters.
I've found that 'Apple Pay' is not enabled from the paytab dashboard, I've
enabled it, but I think it will take some time.
If that will work or not, I'll get back to you
Thankss
On Thu, Nov 11, 2021 at 2:39 PM Mohamed Adly @.***>
wrote:

Did you follow the steps in the guide to setup Apple Pay certificate:
https://github.com/paytabscom/flutter-sdk-bridge/blob/pt2/ApplePayConfiguration.md
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/paytabscom/flutter-sdk-bridge/issues/11#issuecomment-966152499,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBHUDUJZ2HIMRDQYVHPMXLULOFMDANCNFSM43GMBTYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Assalam-o-Alaikum Adly,
yes i've followed the guide
got merchant id, passed all the values, apple pay is now enabled on my
paytab account.
same as this:
[image: image.png]
but still having the same response:
{status: event, code: 0, message: Cancelled}
Can you please guide me further
Thanks.
On Fri, Nov 12, 2021 at 3:25 PM Musaddiq Ahmed Khan <
@.***> wrote:

Thanks for the fast response, actually I was just verifying all parameters.
I've found that 'Apple Pay' is not enabled from the paytab dashboard, I've
enabled it, but I think it will take some time.
If that will work or not, I'll get back to you
Thankss
On Thu, Nov 11, 2021 at 2:39 PM Mohamed Adly @.***>
wrote:

Did you follow the steps in the guide to setup Apple Pay certificate:
https://github.com/paytabscom/flutter-sdk-bridge/blob/pt2/ApplePayConfiguration.md
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/paytabscom/flutter-sdk-bridge/issues/11#issuecomment-966152499,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBHUDUJZ2HIMRDQYVHPMXLULOFMDANCNFSM43GMBTYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

atlast.. fixed 😌
Apple pay was disabled on XCode -_-


[FLINK-14208][python] Optimize Python UDFs with parameters of constant values

What is the purpose of the change
This pull request optimize Python UDFS with parameters of constant values.The constant parameters are not needed to be transferred between the Java operator and the Python worker.
Brief change log

Adds Constant message in flink-fn-execution.proto
Adds translate rexLiteral object to python object logic

Verifying this change
This change added tests and can be verified as follows:

Added test test_udf_with_constant_param

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@flinkbot run travis

@dianfu  Thanks for your review! I have addressed the comment in the latest commit.

@HuangXingBo I find that there are problems for supporting the time Interval type in Python due to the equals method of TimeIntervalTypeInfo. The equals method use == to compare the two serializers.
This is ok for java because the INTERVAL_MILLIS in TimeIntervalTypeInfo is a static variable.  However for python, we serialize the INTERVAL_MILLIS type in PythonFunctionCodeGenerator using EncodingUtils.encodeObjectToString and deserialize it later. This makes the two objects can not compare with == anymore.
I'm not sure if we can change the compare method in TimeIntervalTypeInfo, i.e., change == to equals. But definitely, it's not a good idea to solve the problem in this PR. We can discuss the problem of the equals method in another jira and support time Interval type later.
What do you think?
Best, Hequn

@HuangXingBo I find that there are problems for supporting the time Interval type in Python due to the equals method of TimeIntervalTypeInfo. The equals method use == to compare the two serializers.
This is ok for java because the INTERVAL_MILLIS in TimeIntervalTypeInfo is a static variable. However for python, we serialize the INTERVAL_MILLIS type in PythonFunctionCodeGenerator using EncodingUtils.encodeObjectToString and deserialize it later. This makes the two objects can not compare with == anymore.
I'm not sure if we can change the compare method in TimeIntervalTypeInfo, i.e., change == to equals. But definitely, it's not a good idea to solve the problem in this PR. We can discuss the problem of the equals method in another jira and support time Interval type later.
What do you think?
Best, Hequn

@hequn8128 LGTM,  we can support interval type in another pr later. And I have addressed the comment in the latest commit.

I have created a new jira(FLINK-14383) for the time interval types.

@HuangXingBo Thanks a lot for the update. LGTM, will merge this when Travis passed.


ran into an error when using "not ie <= 7"

Hi, I've tried the config as followings several times for webpack and it seems just doesn't work for me, and there was no error threw out when i ran webpack. What does it mean by "not ie <= 7"?  I expect it to be all browsers except IE 6 and 7.  Looking forward to your reply.  Thank you!
postcss: [ autoprefixer({ browsers: [
        'not ie <= 7'
] }) ]

not X queries remove versions from left part of query.
Correct query for your choice: > 0%, not ie <= 7. But it will be very bad query. You really don’t need Chrome 5. With this query your CSS will contains completely outdated prefixes.
Use defaults query ;)


Remove the asset-id attribute from style/link tags

I'm fairly certain these are not necessary any more, because the CSS plugin uses the URL to determine if a resource has already been loaded.

Closed by #598


Error if use together with @vue/compat mode (Slider v-model must be a Number or Array)

When using the Slider together with vite and the @vue/compat package, the binding of the value model will always throw an error.
We created an example on stackblitz where the error happens. It seems like this is related to the vue compat package, as this error is only shown, when the compat mode is enabled.

The example no longer working. Feel free to reopen if the issue is still relevant.


MatSelectItem throws an error and the same error appears in the demo in fiddle but does not appear in the main demo page !!!

Hi.
I am using MatSelectItem in my project and it throws an error:
Uncaught (in promise) Error: System.FormatException: Input string was not in a correct format.
  at (wrapper managed-to-native) System.Reflection.RuntimeMethodInfo.InternalInvoke(System.Reflection.RuntimeMethodInfo,object,object[],System.Exception&)
  at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) <0x1b0b8f0 + 0x000ce> in <f9608672e47645719a06b8553bcb8b5a>:0

So I checked the examples on the demo page and opening the example in Fiddle threw me the same error:
https://blazorfiddle.com/temp/1a3e8675-0e34-4f65-b628-fa4fb567bd74

But I detected that the error does not appear on the Demo site !!!! !!!

So I exclude some syntax problem or misuse of the component.
Any ideas what may be happening?
Maybe some library version problem?
Thanks in advance.

Same

Thanks for using MatBlazor, I'll take a look at it tomorrow.

Hello there.  Thanks for the awesome product.  Any luck with a workaround or fix for dropdown preselection?  My client seems to be raising a stink about it but everything else seems clean and awesome. Lmk please .  Also are you on Patreon?

@allnet Hi, will take a look at it over the weekend and hopefully fix. Could not find the time yet.
The author of this repository @SamProf has a Patreon page https://www.patreon.com/SamProf
Btw this one is related to #524 (Probably the same issue)

I've identified the issue and will submit a PR in the near future.

Awesome.  Thanks so much. Really need this last piece to know this project out of the park. Lol
On May 7, 2020, at 2:32 PM, Victor Lindespång<EMAIL_ADDRESS>wrote:
I've identified the issue and will submit a PR in the near future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/SamProf/MatBlazor/issues/494#issuecomment-625508458, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA3MO4LBQSXNV3PV66MNXU3RQMSG5ANCNFSM4MFX4OCQ.

(Copying from previous closed issue)
Seems as there was a problem with the MDC select Component that was recently fixed https://github.com/material-components/material-components-web/pull/5870
Unfortunately it just missed the 6.0.0 release.
I think this will solve the issue and don't think I want to do apply my hack in MatBlazor until I can see how this fix turns out.

... Hmm but I think I found something that looks weird anyway in MatSelect, reporting back shortly..

Will wait until new MDC Select, sorry.
The workaround is to have your collection initialized before supplying it to the MatSelect since this problem appears if you change the collection after the component has been rendered. So if you have async calls to another API then wait until you have your results before you render your MatSelect.
Why it works in some places and/or sometimes is since there may be (depending on implementation) a race condition between the async service call and the rendering of the MatSelect.
The reason for the FormatException is since we are parsing a JS string representing the index on change returned from the MDCSelect which in this case is an empty string => crash.

Thanks so much.  Got it working.  Looks great!!
Do you do any work for hire on the side?
On May 9, 2020, at 6:39 AM, Victor Lindespång<EMAIL_ADDRESS>wrote:
Will wait until new MDC Select, sorry.
The workaround is to have your collection initialized before supplying it to the MatSelect since this problem appears if you change the collection after the component has been rendered. So if you have async calls to another API then wait until you have your results before you render your MatSelect.
Why it works in some places and/or sometimes is since there may be (depending on implementation) a race condition between the async service call and the rendering of the MatSelect.
The reason for the FormatException is since we are parsing a JS string representing the index on change returned from the MDCSelect which in this case is an empty string => crash.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/SamProf/MatBlazor/issues/494#issuecomment-626177713, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA3MO4N2YMAFT3HSWGAUJV3RQVMH5ANCNFSM4MFX4OCQ.

This is unfortunatelly not a workaround for me. As I mentioned in my original issue, I need to change the bound collection in runtime based on user interaction, after the component is first rendered.

@doyce I understand. Depending on the frequency of the user interaction it might be feasible to re-render the component?
@allnet Glad to hear it. Not at the moment since I have a 7 week old kid that is in the centre of attention at the moment :)

Also one last question,  how do I set a background color for MatTableRow?   I want it to be based on evaluating a simple method to determine the color.
I’m sure there is probably some convention I could apply when I need to override the theme.  Let me know even if you just point me to a link.  Couldn’t really find anything when I looked but I’m an experienced developer but somewhat new to web development.
Thanks
On May 9, 2020, at 6:31 PM, Darryl Hill<EMAIL_ADDRESS>wrote:
Thanks so much.  Got it working.  Looks great!!
Do you do any work for hire on the side?
On May 9, 2020, at 6:39 AM, Victor Lindespång<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Will wait until new MDC Select, sorry.
The workaround is to have your collection initialized before supplying it to the MatSelect since this problem appears if you change the collection after the component has been rendered. So if you have async calls to another API then wait until you have your results before you render your MatSelect.
Why it works in some places and/or sometimes is since there may be (depending on implementation) a race condition between the async service call and the rendering of the MatSelect.
The reason for the FormatException is since we are parsing a JS string representing the index on change returned from the MDCSelect which in this case is an empty string => crash.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/SamProf/MatBlazor/issues/494#issuecomment-626177713, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA3MO4N2YMAFT3HSWGAUJV3RQVMH5ANCNFSM4MFX4OCQ.

@allnet It's not supported in the MatBlazor API, but you can alter the <td> elements with Blazor syntax to get what you want.
https://blazorfiddle.com/s/fffkrbjd
In my example it's inline style but you can do conditional css classes aswell.
Please acknowledge when you have read this and I will delete both our comments to keep this issue nice and tidy. In the future please create new issue to help us keep this repo clean 😉

@lindespang What exactly do you mean by re-rendering the component?

Is there any progress with the bug? I noticed that MatBlazor version 2.6.0 includes MDC components 6.0.0 but the bug is still there.

Just donated some more cash to your PayPal.
Quick question,  how did you get the color selector widget that you use in the demo for MatBlazor ?
Would love to implement something similar in the setup of one of my apps.   You also have this implemented in the top bar with a tear drop color selector.
I would take either one or both if possible .  Hopefully you can just copy and paste from the razor file or send me both html/razor files and I’ll find it.
Just cant seem to figure out how you did it. Thanks so much.

Would love to have both snippets.
Thanks

I wonder if this bug will ever be fixed. It can sure be workarounded but I need to workaround it everywhere I use MatSelect component which is pretty annoying. In one case I even needed to replace the component completely because the workaround doesn't work.

Hi any word on the issue, i found a workaround for Blazor Server but struggling to wait on async tasks when using WebAssembly. Currently the issue is holding back a prod release.

Hi any word on the issue, i found a workaround for Blazor Server but struggling to wait on async tasks when using WebAssembly. Currently the issue is holding back a prod release.

Hi any updates on this issue

I got this error and switched over to use MatSelect instead. No error when using that component
https://www.matblazor.com/Select#MatSelectGuid


SWAG not routing to homer or other services

The issue I am facing is that SWAG is serving the its default welcome page (the one mentioning linuxserver.io), either when going to 192.168.1.x or using its public address (or name). I see that the two docker networks (internal and public) are created, all docker services are joined accordingly to one docker network or the other. Subdomain configurations are copied and loaded by SWAG. I don't get the reason or where to look deeper.
Some info:
$ docker network inspect swag_internal_network
---
...
            "1dffff2839ec87b3287634735ae2da7574dde6bc34913a625f12c30ee4b8e6f9": {
                "Name": "homer",
                "EndpointID": "9cdc8d599f26ca01e11dc1472bf70440295b3655fe3b4dfb3548172b43590b49",
                "MacAddress": "02:42:ac:12:00:08",
                "IPv4Address": "<IP_ADDRESS>/16",
                "IPv6Address": ""
            },
            "39b227b6a17ec4f898f1cad059d897cf6774707e47814ef11aa60e46ea9521a3": {
                "Name": "radarr",
                "EndpointID": "594c489df6e30d1302e625d15eb6654a293fc5f3d570e6ff4db44c8265f77c2b",
                "MacAddress": "02:42:ac:12:00:03",
                "IPv4Address": "<IP_ADDRESS>/16",
                "IPv6Address": ""
            },
...

$ docker logs swag_internal
---
...
**** The following reverse proxy confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare them to the samples in the same folder to make sure you have the latest updates. ****
/config/nginx/proxy-confs/sonarr.subdomain.conf
/config/nginx/proxy-confs/radarr.subdomain.conf
/config/nginx/proxy-confs/photoprism.subdomain.conf
/config/nginx/proxy-confs/jackett.subdomain.conf
/config/nginx/proxy-confs/homer.subdomain.conf

[cont-init.d] 70-templates: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Server ready
...

I don't want to bother much here, I think it's something specific to my setup, I am just asking here maybe a little hint where I should look closely to debug this issue. Is there a default access log for swag?
EDIT: I found an hint. Basically, 192.168.1.x is served by swag_public. I don't think that is expected, isn't it?
...   ghcr.io/linuxserver/swag             "/init"         ...         80/tcp, <IP_ADDRESS>:443->443/tcp   swag_public
...   ghcr.io/linuxserver/swag             "/init"         ...         80/tcp, 443/tcp                swag_internal

Ok I understood a bit more. Now I realized that the public SWAG lives on a bridge-like swag_network, of class 172.19,0.x and on the default bridge (i.e. 172.17.0.x). On the contrary SWAG internal lives on a separate macvlan docker network (in my case it got <IP_ADDRESS>), but also on the bridge swag_internal_network of class 172.18.0.x and on the default bridge 172.17.0.x as the public one. So in order point to the internal SWAG I need to go to <IP_ADDRESS>. Not sure why this is secure since they all share the same class 172.17.0.x but this is way beyond my skills.
Now the original issue holds. In both cases (internal and public) I am seeing the original SWAG welcome page, like the https call is not propagated downstream. Again, subdomain confs are loaded according to the swag logs, so they're either wrong in some way or I have something else which silently breaks things.

I found the origin of the issue. DNS! On my workstation I needed to add all DNS accordingly. I am not really sure why pointing to the IP does not work, while fixing all names and then pointing to {{ host_local }} it works. Sorry to have added a bit of entropy, but I hope it can be of any help to other people.


Dockerization

Fixes: Shape Ingestion
Major Changes:
Dockerize the deployment of production plenario
Plenario had been unable to ingest shape datasets for a while now, this was due to a failing subprocess call made to ogr2ogr. The failures were a result of an outdated GDAL package running on Amazon Linux. "But why not just update GDAL?" you ask, making a very reasonable point. oh we tried.
Minor Changes:
Removal of eb-init scripts
The setup of plenario's runtime environment is now handled by the Dockerfile.
Update log methods to write to stderr
Logs can now be tailed in the containers folder that Docker maintains. Prevents the creation of massive log files.
Update to _make_call_sign_wban_map
If it fails it will now helpfully tell you where it was running from.
@WillEngler
@pbeckman

Nice! Where is the source for the jesseb954/plenario Dockerfile?


Alert firing continuously

Home Assistant release with the issue: 0.90.3

Last working Home Assistant release (if known): 0.90.1
Operating environment (Hass.io/Docker/Windows/etc.): Hassio/Raspberry

Component/platform: Alerts

Description of problem: Alert firing continuously very fast. When condition for alert is met alerts starts firing (emails in my case) maybe every second.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
kontrola_vstupni_dvere:
  name: Dveře do bytu otevřené! Okamžitě zavřít!!
  done_message: Dveře opět zavřeny
  entity_id: binary_sensor.cidlo_dvere
  state: 'on'
  repeat: 3
  can_acknowledge: True
  skip_first: True
  notifiers:
    - oba

Traceback (if applicable):

Additional information:
This behavior stared after fresh HA installation and restore of previous fully functional configuration. Maybe fresh install + restore set something wrong but i don't know what. I see some closed tickets about timezones/DST. I see correct zone on info page: "timezone | Europe/Prague"

I have the same issue; If I understand correctly HassOS is running in UTC timezone by design (which can not be configured or changed easily), but for the Alert component needs the time zone used for Home Assistant and the underlying operating system to be the same (see docs Alert component).

I think this issue is related https://github.com/home-assistant/home-assistant/issues/21860 and merged, so then this can be closed as well :)


Create logging-lite chart from solas-chart

Create logging-lite Helm Chart (fluent-bit -> elasticsearch)

[ ] Following the instructions at https://github.com/samsung-cnct/solas-container, create a new repo named chart-xxx

[ ] Create a chart

[ ] Verify the Jenkinsfile in the repo tags an app and uploads it to quay.io

See conversation: https://github.com/samsung-cnct/k2-charts/issues/119

As per discussion here, please use https://github.com/samsung-cnct/chart-elasticsearch for dependency.

How are users going to get access to their data? an ELB? or should we be including kibana in this logging-lite to give users an easy way to see their logs?

One vote for including Kibana.

Chart now includes kibana, but there are blockers to getting this to actually run. Here is the main problem: https://github.com/app-registry/appr-helm-plugin/issues/3#issuecomment-302701693
Currently working to vendor the deps and push that to quay

For future reference - I initially set up the chart repo as detail in the above comment ^^, using the appr field , but that isn't actually working yet apparently. To make it functional, I had to go into that chart and run helm registry dep --overwrite, and then helm dep build. That turned my requirements.yaml into something that  helm registry could work with. Unfortunately, it built it in a location that was not super useful.  It changed requirements.yaml, and also vendored the deps into appr_charts/, but that directory needed to get moved into logging/ along with the requirements.yaml and requirements.lock.  So for future work, anyone wishing to update this will need to follow those steps of those helm commands, and then moving the created directories into the right place.

 Just have to make sure the cluster is big enough and your cluster storage class is correct.


refactor CalendarAgenda so that it uses Luxon date functions

Right now the agenda component is using a mix of Quasar date functions and Luxon functions (via mixins). Let's standardize on Luxon to keep it consistent with everything else.

Should also change the recently updated parseDateEvents function in CalendarEventMixin.js to use Luxon as well.


Run code on data of other 'image_size', not (128,128,128)

Thanks for sharing your work in this field.
I run the provided code on the MRI data of size (160, 192, 224) and before that, I have carefully modified the corresponding image_size. It gives results as:
"Assign requires shapes of both tensors to match. lhs shape= [3,3,4,512,9] rhs shape= [2,2,2,512,9]
[[{{node save/Assign_20}} = Assign[T=DT_FLOAT, _class=["loc:@gaffdfrm/affine_stem/conv7_W/W"]"
I wonder does the data size has to remain (128, 128, 128) to run the code. If so, could you provide some suggestions about how to resample my data (volume and segmentation map) to (128, 128, 128) properly?
Ps: I have tried to resample with the scipy.ndimage.zoom() function, but it results in poor Dice scores.
Thanks a lot.

Running on a different size requires retraining; using the pretrained models would not work. When resampling the images, using scipy.ndimage.zoom with order=1 is fine. Care should be taken when resampling the segmentation maps since from my experience order>1 would lead to terrible results. Please also make sure that the your data is correctly preprocessed; for MRIs, skulls should be removed before feeding into the network.

Thank you very much for your reply. The information about resampling is very helpful, also thanks for the hints about data preprocessing, my problem has been solved.


Renamed 'curly bracket' to 'curly brace'. Fixes #989.

We will need to move the documentation for these diagnostics into the documentation folder of this repository at the same time.

Blocked on #1183.

@EdwinEngelen This would need to be updated across the recently included documentation as well (#1183).

I'm going to redo this since we had to refactor the code base so much (for other reasons), plus we added all the documentation files.


Deployment

Where? How? When?
What we know:
Postgres
Rackspace Cloud
What we don't know:
Settings configs
Traffic/load balancing
Users and authentication (another issue)

Swapping to mongo.
Early app should be fairly low traffic, so we can mark this closed for now.  This will need to be a larger discussion if this ever becomes popular or important.


My post_conversion.sh hook is not being called

I've been unsuccessful in getting my hook to run after conversion
Here is a ls of my /config/hooks directory:
$@/tmp # ls -al /config/hooks
total 20
drwxr-xr-x 1 app app  252 Jan  2 20:56 .
drwxr-xr-x 1 app app  108 Jan  2 20:07 ..
-rwxr-xr-x 1 app app 1784 Jan  2 20:56 download_processor
-rwxr-xr-x 1 app app   52 Jan  2 20:57 post_conversion.sh
-rwxr-xr-x 1 app app  959 Jan  2 20:07 post_conversion.sh.example
-rwxr-xr-x 1 app app  318 Jan  2 20:07 post_watch_folder_processing.sh.example
-rwxr-xr-x 1 app app  589 Jan  2 20:07 pre_conversion.sh.example

My image is based on jlesage/docker-handbrake but adds ruby.
Heres my Dockerfile:
FROM jlesage/handbrake
MAINTAINER Rick DeNatale<EMAIL_ADDRESS>
RUN apk update && apk upgrade & apk add \
  curl \
  wget \
  bash \
  ruby \
  ruby-dev \
  ruby-ffi \
  ruby-bundler

RUN rm -rf /var/cache/apk/*

After initially having the Dockerfile copy the shell and Ruby scripts to /config/hooks, I noticed that they weren't there at run time so I manually copied them there from the host.
post_conversion.sh invokes a ruby program:
/tmp # cat /config/hooks/post_conversion.sh
! /bin/sh

ruby /config/hooks/download_processor $@/

The ruby script logs it's arguments to a log file and exits unless the first argument is "0" indicating a successful conversion. Otherwise it moves the converted file to a location based on the filename.  But the otherwise is moot right now since I can't get it executed.
I can run the hook manually and it logs correctly:
/tmp # /config/hooks/post_conversion.sh
/tmp # /config/hooks/post_conversion.sh one two three four
/tmp # cat /downloads/file_processor.log
starting with arguments []
starting with arguments ["one", "two", "three", "four"]

But when I do a conversion the hook doesn't get called.
What could I be doing wrong. I can provide logs if needed.
FWIW here's the Ruby code
#! /usr/bin/ruby
require 'fileutils'
# The first parameter is the status of the conversion.
# A value of 0 indicates that the conversion terminated successfuly.
# Any other value represent a failure.
# The second argument is the path to the converted video (the output).
# The third argument is the path to the source file.
# Finally, the fourth argument is the name of the Handbrake preset used to convert the video.

return_code, converted_file, source_file, preset = *ARGV

def log(str)
    File.open('/downloads/file_processor.log', 'a+') do |log_file|
        log_file.puts(str)
    end
end

def mv(from, to)
    log("moving #{from.inspect} to #{to.inspect}")
    begin
        FileUtils.mv(from_to)
    rescue StandardError => ex
        log(ex.message)
    end
end

def process_tv_episode
    if season_episode =/\.s(?<season>\d+)e(?<episode>\d+)\./i.match(converted_file)
        season = season_episode[:season]
        episode = season_episode[:episode]
        if show_name_match = Regexp.new("/(?<show_name>.*)#{season_episode[0]}").match(converted_file)
            show_name = show_name_match[:show_name].tr('.', ' ')
            directory = "/volume1/video/TV Show/#{show_name}/season #{season}"
            mkdir_p(result)
            mv(converted_file, File.join(directory, "#{show_name}.s#{season}.e#{episode}.#{File.extension(converted_file)}" ))
        else
            log("'#{converted_file}' could not be matched for show name")
        end
    else
        log("'#{converted_file}' could not be matched for season and episode")
    end
end

log("starting with arguments #{ARGV.inspect}")

if return_code == "0"
    if source_file.include?('/tvshows/')
        process_tv_episode
    else
        mv(converted_file, "/volume1/video/movie")
    end
end

What the heck, here are the log files:
conversion.log
handbrake.debug.log

Can you also provide the container's log (docker logs <container name>)?  Also, how did you create the container (your docker run  command)?

Can you also provide the container's log (docker logs <container name>)? Also, how did you create the container (your docker run  command)?

Thanks for the question. The container log revealed that it was a permission problem trying to write the log file.


Slider -  Label visualisation  🐛

Should be a background on the label and the font color for light mode is wrong.

Please, fill the issue template.

Can you reopen this one?


Tests failing with error: SyntaxError: Cannot use import statement outside a module after upgrading to 2.0.0

My tests start failing once I upgrade my react-router-transition package to version 2.0.0 version.
But it is well in production build.

my devDependencies are:
    "@babel/core": "^7.7.4",
    "@storybook/addon-actions": "^5.2.4",
    "@storybook/addon-links": "^5.2.4",
    "@storybook/addons": "^5.2.4",
    "@storybook/react": "^5.2.4",
    "@testing-library/jest-dom": "^4.0.0",
    "@testing-library/react": "^9.0.2",
    "@testing-library/react-hooks": "^2.0.1",
    "axios-mock-adapter": "^1.17.0",
    "babel-loader": "^8.0.6",
    "danger": "^9.1.5",
    "eslint-plugin-react": "^7.14.3",
    "flow-bin": "^0.102.0",
    "husky": "^3.0.3",
    "jest": "^24.9.0",
    "jest-axe": "^3.2.0",
    "jest-mock-axios": "^3.1.0",
    "react-test-renderer": "^16.9.0",
    "source-map-explorer": "^2.0.1"

Hi @ashr81 – this is likely a result of Jest configuration. This can be worked around via the transformIgnorePatterns option.  Something like the following should work:
  transformIgnorePatterns: [
    "node_modules/(?!(react-router-transition)/)",
  ],

It also depends on which version of Jest you're using. Let me know if this fixes it for you.

Adding this code into my package.json helped me resolve the issue.
Thank you @maisano for a faster response.
"jest": {
    "transformIgnorePatterns": [
      "node_modules/(?!(react-router-transition)/)"
    ]
  }

With this doc as reference. Isn't the react-router-transition pre-compiled before publishing?

Hi @ashr81 – this is likely a result of Jest configuration. This can be worked around via the transformIgnorePatterns option. Something like the following should work:
  transformIgnorePatterns: [
    "node_modules/(?!(react-router-transition)/)",
  ],

It also depends on which version of Jest you're using. Let me know if this fixes it for you.

I don't think so, @maisano . In my case the error is pretty the same, but I think that the solution is with your configuration. Here is what I got:

This problem is being caused by the Babel configuration added here https://github.com/maisano/react-router-transition/commit/66db97b671c0d04864f1c468f7eacf2614b81f0d#diff-fc10a6682269c1fefc2abe05d1500b8a . The Babel's output begins with:
function _objectWithoutProperties(source, excluded) { [...] }

function _objectWithoutPropertiesLoose(source, excluded) { [...] }

import React, { cloneElement, createElement, useEffect, useRef, useState } from 'react';
import PropTypes from 'prop-types';
[...]

And these imports after the Babel's helpers that cause those errors in Jest. I've just rebuilded the repo with '@babel/preset-env', { modules: 'commonjs' } and the Jest started working fine again. There is a long open conversation about this here https://github.com/vuejs/vue-cli/issues/1584 . Please, consider update the configuration.

@Alynva it's not uncommon to publish components with import declarations (e.g. import React from 'react';) in them; the error that you're seeing from your test code is that your Jest configuration does not natively understand import declarations. as aforementioned, you can account for this with the transformIgnorePatterns property of your Jest configuration, which well allow these statements to be changed to CommonJS style require calls via babel-jest.

I'm using Parcel and TypeScript and was running into this issue (react-router-transition not working in Jest due to "Unexpected identifier" when trying to import React). No solution that I tried worked, but I was able to create a suitable work around:
jest.config.js
{
    ...
    "moduleNameMapper": {
        ...
        "react-router-transition": "<rootDir>/src/test/mock.Switch.tsx"
    },
   ...
}

/src/test/mock.Switch.tsx
import React, { ReactElement, ReactNode } from 'react';
import { Switch } from 'react-router-dom';

const AnimatedSwitch = ({ children }: { children: ReactNode }): ReactElement => <Switch>{children}</Switch>;

export { AnimatedSwitch };

(In OP's case, you would replace Switch with Route, and AnimatedSwitch with AnimatedRoute)

This has the added benefit of removing the transition aspect from the Jest tests (which may or not be a benefit). For my case it's a benefit as my unit tests can run as normal without having to account for transitions .
To clarify, the work around is to swap out the import from react-router-transition with the regular react-router equivalent by using the moduleNameMapper property in your Jest config.


Implementing ColSpec interface in Select and Reject

Codecov Report

Merging #31 (7bf2e88) into master (fcf126b) will decrease coverage by 0.50%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##           master      #31      +/-   ##
==========================================
- Coverage   92.73%   92.23%   -0.51%
==========================================
  Files          16       16
  Lines         413      399      -14
==========================================
- Hits          383      368      -15
- Misses         30       31       +1

Impacted Files
Coverage Δ

src/transforms/colspec.jl
100.00% <ø> (ø)

src/transforms/select.jl
91.30% <90.90%> (-2.21%)
:arrow_down:

src/transforms/filter.jl
100.00% <100.00%> (ø)

src/transforms/quantile.jl
93.33% <0.00%> (-1.12%)
:arrow_down:

src/transforms/scale.jl
92.30% <0.00%> (-1.03%)
:arrow_down:

src/distributions.jl
90.90% <0.00%> (-0.40%)
:arrow_down:

Continue to review full report at Codecov.

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


Typos in #7.1

Instead of creating a bunch of small issues for typos, I'll list them all as separate comments on this one issue.
In the Sharing Startup Logic code block it identifies the wrong file:
//! tests/app/helpers.rs

should be:
//! tests/api/helpers.rs

Another bug in the same section, "Extracting Our Startup Code", src/startup.rs requires an extra use statement that is missing, use crate::configuration::Settings.

In Chapter #6 - Unit Tests we begin writing all of our tests in ./tests (that is a directory named, "tests" in the root of our project. In Chapter #7.1 the directory is referred to as both "./test" and "./tests". cargo is apparently smart enough to pick up on this, but I am not :smiley: . I would suggest picking one convention and sticking to it throughout the book.

In the section step where one is to, "Add three empty files - tests/api/helpers.rs, tests/api/health_check.rs and tests/api/subscriptions.rs", it explicitly states that configure_database isn't public, but it doesn't point out that spawn_app is now public. This is pretty easy to overlook.

In "Testing Hooks in Our Startup Logic" zero2prod::startup::get_connection_pool is imported, but we haven't written it yet.

In the section starting with "Let's deal with the connection pool first:" the code requires use crate::configuration::DatabaseSettings;

tests/api/helpers.rs requires use zero2prod::startup::Application; in the last example before "Build an API Client".

In the last set of examples before "Build An API Client" in src/startup.rs:
    let port = listener.local_addr().unwrap().port;

should be:
    // `port` is a method, not a field
    let port = listener.local_addr().unwrap().port();

Thanks for the detailed feedback - they should all be fixed in the latest release 😁


v2 Docker Compose

hi Mckay,
great work! I wonder about having a docker compose yml to organize the whole package, including Supabase, for a tight delivery solution.
it also would be easy to deploy next to other container stuff in servers.
regards
Bruno Massa

There's currently a community PR being worked on for this!
Keeping my eye on it. Could probably use some extra people contributing to it to speed things up if the demand is there.

any updates on it?


making dos2unix optional

Not exactly sure why we need this dos2unix.
However, I think that on real Linux we can just omit it, what this PR is all about.

Apparently already done...


[MOB-2993]: Retrieve the estimated cancellation fee

JIRA
MOB-2993
DESCRIPTION
Retrieve the estimated cancellation fee - task finished and tests added
Types of changes
What types of changes does your code introduce to the project?
Put an x in the boxes that apply

[ ] Bugfix
[ ] New feature
[ ] Tech Debt
[ ] Breaking change
[ ] Documentation Update
[x] Other: NSDK improvement

CHECKLIST
Put an x in the boxes that apply. You can also fill these out after creating the PR. This is simply a reminder of what we are going to look for before merging code.
Please review the guidelines for contributing to this repository.

[x] All work relating to the ticket is complete (Code complete/Acceptance Criteria met)
[x] Lint and unit tests pass locally (if appropriate)
[ ] Added tests that prove the fix is effective or that feature works (if appropriate)
[ ] Documentation (if appropriate)

SCREENSHOTS
[Add screenshots if any for changes you have made to the App/UI]

Please check any nsdk changes with the uisdk.


[ESLAnchornav] updates

Fixed ESLAnchornavRender signature to have flex possibilities to render item.
Added active-class attribute to have the possibility to customize CSS class marker of active item.

:tada: This issue has been resolved in version 5.0.0-beta.32 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Improve performance in methods for TestFunctions types

The package compiles and runs all the methods for the available benchmark functions of type TestFunctions.
Right now this is fine, but eventually this will be a very large burden on the package, because memory and runtime is spent generating methods for functions that may not be needed.
Some possible solutions include:

Using @generated to check for the specific type and create the methods within the generated function.

Somehow, lazily create the methods by checking the type first, or using a special call from the function the uses these types.

Turns out this is not actually necessary as @eval is run at compile time and all the methods are created quite efficiently.
Nevertheless, if there's a need for this I will address it in a future issue.