Composer require from readme fails for L4.2

I've noticed the readme in the Laravel 4.2 branch of this package states:
"composer require barryvdh/laravel-ide-helper"
But that will pull in the latest version, which is incompatible from what i've seen. Putting a version constraint in there will fix it though.

Fixed

Ehm, this commit should only be applied in the 1.11 branch right? ... In the 2.0 branch readme.md you do not want the constraint right?

Whoops, it's late already ;)


Custom font text not searchable or able to copy

Are you using the latest version of jsPDF?
Have you tried using jspdf.debug.js?
Yes to both, I am using version 1.4.1 jspdf.debug.js (https://cdnjs.cloudflare.com/ajax/libs/jspdf/1.4.1/jspdf.debug.js)
Steps to reproduce
Two examples:

see: /examples/basic.html -> tab: "Using Fonts" -> run code
Generates this pdf:
test.pdf

see: jsbin link
Generates this pdf:
Testy.pdf

What I saw
Text does use the custom font, but now I also can't:

search inside the text that has a custom font;
copy the text with a custom font to a different program (like Word);

What I expected
I expected the text to change, but to keep the copy/search functionality. This expectation was based on these two examples:

https://codepen.io/bocko/pen/RyGBKg
Generates this pdf:
test.pdf

I do realise this uses:

https://cdn.rawgit.com/sphilee/jsPDF-CustomFonts-support/bcc544cd/dist/jspdf.customfonts.min.js
https://cdn.rawgit.com/sphilee/jsPDF-CustomFonts-support/bcc544cd/dist/default_vfs.js

But from what I understand, the sphilee code has been added to jspdf? So by using the newest version + using the fontconverter, I would expect the same result?

https://codepen.io/stuehler/pen/pZMdKo
Generates this pdf:
customFonts.pdf

Again uses these files:

https://cdn.rawgit.com/sphilee/jsPDF-CustomFonts-support/bcc544cd/dist/jspdf.customfonts.min.js
https://cdn.rawgit.com/stuehler/jsPDF-CustomFonts-support/master/dist/default_vfs.js

Basically the same as example 1, but just using different fonts. Both these examples support searching in and copying of the text with the custom font.
I did see custom fonts get discussed in the draft release notes of jspdf 1.4.2 (https://github.com/MrRio/jsPDF/issues/1819), but as far as I can see I can't use those fixes yet? Is there any way for me to fix this now or is my only option going back to the original sphilee code (or wait for the 1.4.2 release)?
Any help is greatly appreciated, because I have tried everything I could find online and here in the issues, but I just can't figure it out.
Thanks in advance.
Casper

But from what I understand, the sphilee code has been added to jspdf? So by using the newest version + using the fontconverter, I would expect the same result?

We adapted the code, but it is different from customFonts. customFonts from sphilee is incompatible with jsPDF.

I did see custom fonts get discussed in the draft release notes of jspdf 1.4.2 (#1819), but as far as I can see I can't use those fixes yet? Is there any way for me to fix this now or is my only option going back to the original sphilee code (or wait for the 1.4.2 release)?

You can always build the project with npm run-script build.
Here is a snapshot/nightly build of the project, which was created with npm run-script build:
https://github.com/MrRio/jsPDF/issues/1819#issuecomment-448051429
I hope to convince MrRio for a release this week. But for now, you can use the nightlybuild.
Is this issue solved?

Is this issue solved? :)

Yes, I'll use the snapshot build for now and wait for the new release. Thanks for the quick response and all the work you do (In my searching I saw your name a lot ;) ).


Reciprocity in intersect in version bedtools-2.25.0

Hi guys,
I'm getting an odd result in bedtools intersect version bedtools-2.25.0.  I expect -f 0.5 -F 0.5 to give the same answer as -f 0.5 -r. This happens in version 2.24 but it doesn't seem to force the -r in version 0.25.  "Use" is how we call the versions at the Broad.
e.g.
4:11pm mbusby@node1749 myDir/ $ use .bedtools-2.24.0                                                                                Prepending: .bedtools-2.24.0 (ok)
4:12pm mbusby@node1749 myDir/ $ bedtools intersect -a file1.bed -b file2.bed -f 0.5 -r -wa -wb | wc -l
9829
4:12pm mbusby@node1749 myDir/ $ use .bedtools-2.25.0
Prepending: .bedtools-2.25.0 (ok)
4:12pm mbusby@node1749 myDir/ $ bedtools intersect -a file1.bed -b file2.bed -f 0.5 -r -wa -wb | wc -l
10825
4:12pm mbusby@node1749 myDir/ $ bedtools intersect -a file1.bed -b file2.bed -f 0.5 -F 0.5 -wa -wb | wc -l
9829

Hi Michele,
I believe this bug was fixed in this commit (https://github.com/arq5x/bedtools2/commit/78d74e99a81b1f6537c7e2d97592ebe0e25600cd). Unfortunately, I am not yet ready for a new formal release, but if you build from the repo source, I think you should be back in business.

OK, thanks!


Steps to run incomplete?

git clone https://github.com/FrostTheFox/ptc-acc-gen
cd ptc...
npm install
(no errors, mainly few warns about<EMAIL_ADDRESS>No repository field.  and No license field.)
Little fiddling with index.js var's (like setting nicknames.json true etc)
node index.js ->
x@ubuntu:~/ptc-acc-gen$ node index.js
Creating account 0 of 10
[DEBUG] Handle first page #0
x@ubuntu:~/ptc-acc-gen$
if I run makeaccounts.sh it just makes the same and then tells me that generated accounts can be viewed from the PogoPlayer/accounts.csv file (which is there - but it's empty)
So, what am I missing (running under 16.04 LTS ubuntu with 6.x nodejs)

(Arh. Nevermind. Noticed another open issue and statement that this thing doesnt work in cli.. Shame..)

Yep, unfortunately does not work in cli.


[Payment card / Subscription] Implement UpdateSubscriptionAddNewUsersAutomatically API command

Complete this backend section of the design doc: Implement UpdateSubscriptionAddNewUsersAutomatically API command

Auth and Web PRs are in review

Auth PR deployed to prod; Web PR merged and should be on staging later today

Confirmed Web PR is now on staging

Web PR deployed to prod 🎉


[Question] About How to deploy the project

Hello, is there any deployment operation document in the project, how should I deploy correctly and how to verify in the end? I look forward to your reply. Thank you very much

it requires too use the code here as just another exercise from the p4lang/tutorials while using their VM.


Not working in 8GB sized img

Not working in 8GB sized img. Showing:
pishrink.sh v0.1.2
pishrink.sh: Gathering data...
Creating new /etc/rc.local
pishrink.sh: Checking filesystem...
MoodleBox_by_NMA: 124844/475200 files (0.3% non-contiguous), 1608430/1947392 blocks
resize2fs 1.44.1 (24-Mar-2018)
pishrink.sh: ERROR occured in line 269: Image already shrunk to smallest size

How much free space is left on the image? Especially on smaller images some times we can't shrink any smaller which is unfortunately out of my control since PiShrink relies on resize2fs for that


Groups cluster updated. Test suite added.

Problem
The Groups cluster server is currently implemented using the bindings table, and lacks unit tests.
Change overview

Groups cluster server is now implemented using non-persistent C++ containers.
Unit tests added.

Testing

Unit tests executed successfully, including the new GroupCluster suite.
Groups cluster manually tested on the EFR32 platform.

@ricardo-casallas Sorry conflicts ;(

@ricardo-casallas Can you please rebase and resolve conflicts?


Added a check for metamask on page load

Added a check for metamask on page load
Added a simple loader to show while the check is being performed
Also fixed an issue with the challengeTransformer that was introduced in a rebase

connects #151


Ghostrunner: Project Hel - Reflex greyed out

Hi,
first of all this is such a wonderful piece of code. I really enjoy it in Apex Legends and the old version of Ghostrunner.
Now since the Project Hel DLC update for Ghostrunner, the Reflex option that was working right before the update (I replayed it a day ago) is now greyed out. There hasn't been a proton update inbetween, and I double checked that the .so and .dll files are in place. reflex still works for me in Apex Legends.
I checked the logs as per your troubleshooting guide:

There are no DXVK_NVAPI Device, Output, Version and Initialize messages at all.
This is also missing: trace:loaddll:build_module Loaded L"C:\\windows\\system32\\latencyflex_layer.dll" at <address>: builtin
This is missing too: Loading latencyflex_layer.dll failed with error code: 1114

I can confirm that the update seems to have broke LFX support. For me, I have all the NVAPI logs and the layer module is properly loaded, so you might have something wrong in the setup nevertheless.
My guess is that they started requiring several functions that are not strictly necessary and omitted in LFX implementation, but it's time for me to sleep today. I'll investigate tomorrow and keep you updated.

any updates?

I've got it to the point where the button is no longer grayed out but I simply can't get the relevant callbacks to be called if it says "enabled" in the settings screen. Just in case if the devs ended up wiring the Reflex option to nothing, I'd appreciate if anyone with Nvidia on Windows can check if the Reflex option in the latest patch makes a difference with the GFE overlay.

I debugged the game and I'm pretty sure the dev just forgot to wire the option to execute the correct UE command. The Reflex plugin is still registered so you might be able to enable by using some cheat / console unlocker then set ReflexMode=1 in console.


ec2_iam_role doesn't seem to work

I created a role using IAM called "cfnc-user"
part of the policy attached to cfnc-user is this bit:
    {
        "Sid": "IAMModify",
        "Action": [
            "iam:PassRole"
        ],
        "Effect": "Allow",
        "Resource": "arn:aws:iam::176086582871:role/cfnc-user"
    }

then in my ~/cfncluster/config file I do not list credentials except specifying ec2_iam_role = cfnc-user
However, running cfncluster create xyz seems to pull my credentials from ~/.aws/credentials whether I specify an ec2_iam_role or not. For example, changing the credentials in ~/.aws/credentials changes the behavior of cfncluster create.
I've also tried editing the policy Resource to "*"
Am I doing something wrong here? Thx!

In here you confuse between cluster instance role and cfncluster aws credential for orchestration.

ec2_iam_role --> Existing EC2 IAM Role that will be attached to all instances in the cluster.
AWS credential section in cfncluster configuration is required. If not defined, boto will attempt to use a) environment (which is your case) or b) EC2 IAM role.


Hierarchical pkg_filegroup implementation mockup (try 2)

This change is intended to start a discussion on how we might make a "nestable" pkg_filegroup rule, as @aiuto mentioned in the review for pkg_mklinks.
The mechanism for calling rules out in other rules was tested and is known to work, but I wonder about what to do with the name attribute.
A thought that comes to mind is that pkg_file could emit a specification that a (currently nonexistent) pkg_filegroup rule could use to provide a name to a "real" pkg_file rule (or however it is implemented).
This is a duplicate of #212 that could not be reopened or edited after the master branch was deleted.

Transplanting the last major discussion point:
@aiuto in https://github.com/bazelbuild/rules_pkg/pull/212#issuecomment-698093662 said:

Collisions to the final destination path of a package should fail hard. It is the most straightforward thing we can do.
A single input, however, can be mapped to multiple destination paths in the enclosing package.
You're right that pkg_filegroup is a strange name. bug pkg_dir is a misnomer too, because it can include things globed in from subdirs. It is occuring to me that we should brainstorm on this in a shard document rather than trying to make code work. A meeting room and a whiteboard would help too.
The big questions.
* what expresses existing use cases in an easy to understand way

* how do we re-root things in a natural manner

* is the pkg_file inside the pkg_filegroup too extreme.   I would like to show that to a broader community than just us.
  pro:  It is a readable way of expressing a structured attribute.
  con: no one else does this.  It means pkg_filegroup MUST be a macro rather than a rule.

I think the pro outweighs the con, but I am not sure. This might not even be legal syntax for Starlark.

Discarding in favor of #273 and future related changes


Claiming authorship

Need to add the ability for users to claim authorship of papers/posters, so that they will automatically join the chat
associated with their work, and see notifications when people comment on it or ask questions
The posters/demos chairs should have a special role that allows them to associate "ownership" of the posters to specific email addresses. From then on, the users with those email addresses will have write permissions on the posters. (This is one-off procedure  for ICSE that should be generalized later for future conferences: track chairs should have special roles that allows them to set things up)

Current status: Users can now choose their own authorship. If this is OK, we can close this for now.

IMO this is fine for the moment.


Add worker client relogin

Currently only master client does relogin when needed. There is a slight chance that worker client will run into credential expiration therefore the same relogin logic should be also in the worker client. In the future we should unify the two clients.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8285/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8291/
Test PASSed.

@bf8086 Thanks! I'm assuming this is similar to what the other client does for retries?
Yes it is a shrinked down version for only relogin purpose. It should be refactored to use AbstractClient logic in the future.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-2.2 please


feature: kubectl plugin manager (krew) app

what

Addition of the excellent kubectl plugin manager, krew

why

Because its is a not so hidden gem of useful kubectl plugins for additional kubernetes functionality.

/codefresh run apk

/codefresh run docker


Why does featuretools use first column as an index but not the pandas index field?

Hi,
Pandas creates an implicit index if one isn't specified as a column. What I want to achieve is to use the pandas' index in featuretools but it can't be passed as a name in index argument. featuretools uses first column by default and that part is not clear to me. Why does featuretools use first column as an index but not the pandas index field? How to let featuretools use the index field instead?
The code:
https://github.com/Featuretools/featuretools/blob/906777bbafc18892a927dfdc5ac3f3b8d40de1b5/featuretools/entityset/entityset.py#L441-L459

@alexandrnikitin to integrate your data with Featuretools, simple call .reset_index() on your dataframe. This will turn the index into a regular column in your dataframe. See the pandas documentation here for an example of how this works.
We treat index in the same way as other columns because it can be used just like any other columns when it comes to feature engineering. For example, we may want to apply the Count primitive to it.
Another more technical reason is that pandas indices can be a little idiomatic (e.g they supports things like multiple levels) compared to the concept of a primary key in other tabular data system such as databases. To make our implementation map more generally, we made the design decision to keep it as a normal column.
I'm going to close this for now. If you have further questions on how to get this to work feel free to post on stackoverflow with the featuretools tag.


custom init method

From attrs docs:

Create a __init__ method that initializes the
attrs attributes.  Leading underscores are stripped for the
argument name.  If a __attrs_post_init__ method exists on the
class, it will be called after the class is fully initialized.

attrs inject init method directly to class and provide only __attrs_post_init__ hook for customization, so we can't use method overriding (inheritance), this behavior make customization of __init__ method very limited.
attrs must be able to inject __init__ method with different name, as an example:
@attrs
class Example:
    def __init__(*args, **kwargs):
       # do something before or after call
        self.__attrs_init__(*args, **kwargs) # created by attrs
        # equal to super().__init__(*args, **kwargs) in inheritance method overriding

So we can add custom logic before or after attrs init.
There are two options how this behavior can be added
1 - Add new attrs boolean parameter i.e. attrs_init or custom_init, if set to True, attrs will inject __attrs_init__ instead of default __init__ method.
2 - inject __attrs_init__ automatically if class has __init__ method.
This feature will resolve:
#342
#354

This won't resolve #342 or #354, it just creates a different way to work around them.

I am not entirely opposed to add more control to __init__ generation. I just woke up but the proposed inversion of control might even be a better approach than __attrs_post_init__. 🤔

I read the whole #68 thread in looking for hints on how to proceed with an attrs-styled VIMscript OO library. I like how you made the __attrs_post_init__ method only a completely-after-the-fact hook, everything else would have meant problems with going a step further, like the suggestion is in this thread. And yes, I am of the strong opinion that the attrs-generated __init__ method should be just the lightest-possible shim generating to the real business logic monster which should be appropriately far out of sight, i.e. the proposed __attrs_init__.
I don't see any drawbacks actually. Other than, you gain increased flexibility in what users can do with attrs, will attract a lot of unpleasant head-in-the-clouds FP people asking for more meta-programming-support and typing support and get pissy if you don't want to (and no, this is not in the slightest exaggerated.. ^^)

I don't see any drawbacks actually.

Just to be clear, you’re making the case for __attrs_init__ that is called from a custom __init__ written by the user?

If you now arrive at that step in consulting the docs,

Oh sweet summer child. ;)

Yep, I am for the attrs_init.
And if you have already overridden init, not knowing the implications, with or without this change, you will only be the wiser once you consult the docs, or stackoverflow, right? But the jest is appreciated ;)

And… are we settling on the mechanism for enabling this?  I think I prefer option two, where attrs notices that you've defined __init__ and therefore writes __attrs_init__ instead.
The parameter to attrs has the advantage of being explicit, but I think that defining your own __init__ is sufficiently explicit, and in that case it's rather obvious (I think) that you'd need to explicitly call attrs' generated init yourself, since you've taken over control.

what does this add that cant be done by say a named ctor?

@RonnyPfannschmidt: What a named constructor doesn't let you do is… change the behavior of the default constructor.
I get the argument that named constructors are cool and may be generally preferable, but that's not always an option, and attrs probably shouldn't make it impossible to use it if direct control of __init__ is a requirement (eg. porting an exciting class and you need compatibility), right?

@wsanchez but its still not clear to me why its valuable to have that capability - in particular its not clear if its worth the complexity

to elaborate more - my personal experience is that smart ctors have a tendency to eventually be too smart to sanely debug and/or refactor - im facing that issue now with pytest nodes for example

Sure, but that's your experience and YYMV.
Customization of __init__ is a pretty common thing in Python and compatibility with an API you don't necessarily control is a common requirement.  I don't think this is an unreasonable request, even if I wouldn't recommend doing this in most cases.

I'm mostly with Ronny on this issue however I keep running into legit uses for this kind of behavior, especially if I need attrs classes to integrate with other stuff.
So yeah, Ronny is 💯 right, but it looks like there's enough edge cases that would warrant the complexity. Although I'd totally have to see it first.
BTW with Wilfredos suggestion this became related to #324 and #416 should be taken into account. I'm not positive we should make auto-detection opt-out since it would cause potential breakage.
It might become opt-out in “Project import attrs” but I doubt anybody is gonna step up and implement it by then. 🤔

@hynek I want to start by saying, thanks for making such a useful library! That said, I find myself in the camp where I need the ability to call the super class's __init__ before setting attributes (in conjunction with Pytorch). I've read through #68 and it seems you all did consider enabling this usecase at one point, but it got lost in the fold. I'm sure you'll continue to get asked questions about supporting it.
I came up with a workaround to the issue without needing to modify the library. It  seems to support my usecase well and is reasonably flexible. I figured I would at least document it in this comment in case others want a similar workaround (or in case it inspires a solution that can be incorporated into attrs). Here's a minimal working example showing the approach in action:
from attr import attrs, attrib

def attrs_wrapper(maybe_cls=None, super_init=None, **kwargs):
    '''
    Decorator that wraps attrs to allow calling a super class initializer. Note
    that super_init must return the args and kwargs that should be passed to the
    underlying __init__ that attrs automatically creates.
    '''
    def wrap(cls):
        ''' The internal wrapper method for the decorator. '''
        new_cls = attrs(**kwargs)(cls)
        if super_init is not None:
            __init__ = getattr(new_cls, '__init__')

            def __super_init__(self, *args, **kwargs):
                '''
                This is a version of __init__ that calls the user defined super
                class initializer, which may consume some args and kwargs as
                needed.
                '''
                args, kwargs = super_init(super(new_cls, self), *args, **kwargs)
                __init__(self, *args, **kwargs)

            setattr(new_cls, '__init__', __super_init__)

        return new_cls

    if maybe_cls is None:
        return wrap

    return wrap(maybe_cls)

# an example when called without arguments
@attrs_wrapper
class BaseClass(object):
    ''' A base class '''
    foo = attrib(type=int, default 1)

def child_base_init(_super, *args, foo=1, **kwargs):
    ''' A method to call the initializer of child's super class '''
    _super.__init__(foo=foo)

    # return the args and kwargs not consumed by the base class
    return args, kwargs

# an example with arguments
@attrs_wrapper(auto_attribs=True, super_init=child_base_init)
class ChildClass(BaseClass):
    ''' A child class '''
    bar: int = 2

BaseClass()  # BaseClass(foo=1)
BaseClass(2)  # BaseClass(foo=2)
ChildClass()  # ChildClass(foo=1, bar=2)
ChildClass(3)  # ChildClass(foo=3, bar=2)
ChildClass(3, 4)  # ChildClass(foo=3, bar=4)
ChildClass(bar=4)  # ChildClass(foo=1, bar=4)

I'm not entirely sure that this makes the case for __attrs_init__ but I've come here looking for a solution to somehow prevent attrs from removing leading _ from an attribute in the auto generated __init__.
For whatever reason, I really need __init__ to accept underscored argument as it is.:(

For whatever reason, I really need __init__ to accept underscored argument as it is.:(

perhaps init=... can take either a boolean or a string (which will become the arg name for __init__), similar to what i did to the repr=... arg recently in #568 fo fix #212 / #567.

I don’t think I’m comfortable for another ad-hoc solution like this. The repr thing was just very obvious and pragmatic.
This one seems more like an candidate for pluggable method makers plus metadata. 🤔

I have found another instance where the idea of __attrs_init__ would make sense: https://stackoverflow.com/questions/58571329/attrs-library-and-super/58581192#58581192
When you subclass Tensorflow models, it will intercept __setattr__ and raise Runtime errors when attrs tries to set an attribute. It enforces that you run super() first.

@hynek This is likely a similar issue to the one I reported above using Pytorch. I wonder if my workaround would help for Tensorflow as well.

Ohhh, maybe?  But I suspect it wouldn't be very convincing to someone without any buy in so far. 🤔 But I'll link it, thanks for pointing it out!

Also thanks for the kind words above, currently there seems to be some law of physics that whenever someone asks an attrs question on SO, someone will suggest to use dataclasses instead 🙄

@hynek I'm trying to do the opposite whenever I have an opportunity:)
Lang lebe attrs!

Hi all,
To add food for thought, I have found the following behavior when using attrs with mixin classes.
The behavior is different when subclassing directly (case Data1 below) vs using a dummy class to preserve calling __init__ (case Data2, below). That's somehow breaking my expectations.
import attr

class Mixin(object):  # just a humble mixin providing orthogonal functionality
    def __init__(self, *args, **kwargs):
        self.param = []
        super().__init__(*args, **kwargs)

# Inheritance case 1
@attr.s
class Data1(Mixin, object):
    value: int = attr.ib(default=1)

# Inheritance case 2
@attr.s
class Base2(object):
    value: int = attr.ib(default=1)

class Data2(Mixin, Base2): pass

# make instances
d1 = Data1()
d2 = Data2()

assert isinstance(d1, Mixin)
assert isinstance(d2, Mixin)

assert not hasattr(d1, "param")
assert     hasattr(d2, "param")   # < - extra whitespace for emphasis

It does make sense though:

Data1 is an attrs class with an attrs-made __init__, so self.param is never set.
Data2 is not and attrs class and you mix in your Mixin in a way, that Mixin is before Base2 in the MRO and therefore its __init__ is called (which calls super()).

It is somewhat unintuitive, but that's not really attrs' fault and more a property of multiple inheritance/mixins. :|

I understand how the MRO differs in both cases. As a new user of attr, I was surprised that defining a class using attr.s implicitly changes the behavior of __init__. I note that when reading the class definition of Mixin, one expects it to provide a param attribute.
I was expecting a call to super given it's the standard procedure in python. Also because I read this bit in the attrs docs: The class belongs to the users. (emphasis not mine). Actually, the whole "Philosophy" section is golden. Sadly, as I understand it the __init__ written by attr.s breaks points 2, 3 and 5.
https://www.attrs.org/en/latest/overview.html#philosophy
Multiple inheritance has the drawback that it is highly sensitive to the MRO, it is easy to get wrong and is often brittle. One of the safer use cases is to mix classes with orthogonal functionality and short disjoint MROs. In the example provided above, the pitfalls of the MRO can be safely avoided in most cases (one exception is attrs!). I note that traitlets preserves the expected behavior, despite it's addiction to heavy stuff.
My use case seems closely related to other use cases in this thread. I am working on a library to notify GUI widgets (Pyside2) whenever an attribute changes. This accomplishes the very important task of keeping multiple independent widgets in sync with the underlying data, cutting on the boilerplate code, and without forcing the user to rewrite their entire codebase when they decide they want a GUI for their task (go read the docs about Qt Model/View, I'll wait...). To minimize potential conflicts, I add a single attribute, a single method, and intercepting calls to __setattr__ to notify widgets (if necessary). So far this seems to work with vanilla classes, when using properties and with traitlets. For attrs one has to be careful with the MRO (and we don't like that, do we?).
Finally, here is one more example to ponder:
import attr

class Mixin(object):  # test mixin please ignore
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.param = []

@attr.s(auto_attribs=True)
class Data1(Mixin):
    value: int = 1

class Data2(Mixin):
    value: int = 1

d1 = Data1()
d2 = Data2()

assert not hasattr(d1, "param")  # I think that qualifies as a surprise!
assert     hasattr(d2, "param")

This has been fixed by #750 and #731.

This has been fixed by #750 and #731.


Article is missing implicit conversions from char

See specs, which includes the implicit conversions from char. While the article doesn't.

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

ID: 7fbe6892-5258-ab87-cb9e-7372e43835d4
Version Independent ID: 071fccf4-f7d2-23dc-fba0-c2c54efac225
Content: Built-in numeric conversions - C# reference
Content Source: docs/csharp/language-reference/builtin-types/numeric-conversions.md
Product: dotnet-csharp
Technology: csharp-language-reference
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

I think the article should also include native ints.

@Youssef1313 as far as I understand,  char is omitted intentionally as it's not considered as a numeric type, while the article is about conversions between numeric types. The docs not always follow the spec structure. The article about char mentions implicit conversions to numerics.

@pkulikov What about having a link somewhere pointing to the char article (or specifically the "Conversions" section of it).

@Youssef1313 I think it's the spec material and the article already has the link to the spec. I'm afraid linking char can be confusing.  At least, It confuses me: why to consider char as numeric (even if it technically can be)?

That sounds reasonable. Let's drop the "char" part and only add native integers conversions.

@Youssef1313 then could you please rename the issue?

Thanks for all the discussion. I agree with this resolution.
Adding to our backlog.


Update readme.md (Grammar)

Added '.' between "AutoRest AutoRest"

This was a fairly trivial update. Any reason it didn't get reviewed and approved or denied?


Temporary removal of this instantiating test, as we do not currently …

…instantiate with projects

I'd prefer we just delete the code instead of commenting it out

I removed this in https://github.com/rode/rode/pull/15

Fixed in #17

Fixed in #17


Add crypto engine mock

Summary
Add a mocked crypto engine, instead of relying on a real implementation in the tests.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[x] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 39.732% (+0.03%) from 39.703%
when pulling 3201f8a3f759b2788783ef5f25bc2caa1f7e53ce on eleftherias:crypto-mock
into 04a80024d07ea82122a106962134e6d0afeff57a on stacklok:main.


Update supplier find command

Find command now can search by either name OR item. Choose with prefix n/ or i/
Will add more test cases later

Codecov Report

Merging #127 (8c489d5) into master (a6e6fbc) will decrease coverage by 0.61%.
The diff coverage is 34.78%.

@@             Coverage Diff              @@
##             master     #127      +/-   ##
============================================
- Coverage     71.69%   71.07%   -0.62%
- Complexity      532      596      +64
============================================
  Files            89       98       +9
  Lines          1745     2026     +281
  Branches        197      234      +37
============================================
+ Hits           1251     1440     +189
- Misses          428      506      +78
- Partials         66       80      +14

Impacted Files
Coverage Δ

...ss/model/person/ItemContainsKeywordsPredicate.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/FindCommandParser.java
62.50% <45.45%> (-37.50%)
:arrow_down:

...java/seedu/address/logic/commands/FindCommand.java
75.00% <60.00%> (-25.00%)
:arrow_down:

...rc/main/java/seedu/address/model/ModelManager.java
79.26% <0.00%> (-16.12%)
:arrow_down:

...ain/java/seedu/address/storage/StorageManager.java
86.84% <0.00%> (-9.59%)
:arrow_down:

.../java/seedu/address/model/util/SampleDataUtil.java
10.00% <0.00%> (-3.05%)
:arrow_down:

...rc/main/java/seedu/address/logic/LogicManager.java
70.83% <0.00%> (-1.90%)
:arrow_down:

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/model/Model.java
100.00% <0.00%> (ø)

... and 17 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


can't use GPU resourece in training

Thank you for sharing your project. As a college student, there was a problem while trying to use the training code you provided. I turned the training code on both Google colab and the local environment, but the learning process is not progressing because the GPU is not used in the learning process. I'd like to a

sk you for a solution in this regard.
code according to git read me file

As the log showing, the reason is that it can't find the image to load for training.
You need to properly set the path of each dataset to enable training.
For instance, please properly set the path to the folder of Relative Human at
https://github.com/Arthur151/ROMP/blob/12a624f00be92d1f7195f24106d151d2f26961f4/romp/lib/dataset/relative_human.py#L20
Please let me know if the same errors keep showing.

Thank you for your answer. however still my dataset root set that follow your git .md,
my critical problem is when training dataset, all dataset trained by cpu not gpu. if you can watch my screen image, when train dataset computer only uses cpu memory. ans does not use gpu memory and resource. i don't understand how can use gpu memory & resource.


feat(projects): add assets collections in the CMS

So titles can be managed via the CMS. And the image CDN directory is something the contents editor knows about.
Also adds a sorting JSON to control their screen appearance

Current dependencies on/for this PR:

main

PR #116   👈

This stack of pull requests is managed by Graphite.


Deliverables Milestone-1

deliverable milestone 1 - W3F grant

[x] pallets

[x] #64

[x] code
[x] #69
[x] documentation. --> guidelines

[x] #65

[x] code
[x] unit-testing
[x] documentation

[x] #66
[x] Article milestone-1 Mahir & Ilhan
[x] #67
[x] Dockerfile. + Instructions
[x] Licensing
[x] #68
[x] place to publish ? Medium? Subsocial?  Github ?
[x] grants delivery repo:

[x] https://github.com/Fair-Squares/Grant-Milestone-Delivery/blob/fs-m1/deliveries/fair_squares-milestone-1.md

[x] Update how to run all the tests.

Everything is done, this can be closed


Make PWA

Make word master a PWA for offline play

👋Hi.. I've done some research on PWA for React apps. It seems to be done with service workers, which can cache the resources required for the app, making them available offline. Based on my research, this is what I think the necessary steps are

update the manifest to contain fields name, short_name, start_url and scope
Register the service-worker which can be done directly in public/index.html as shown here or call a similar function from src/index.js as followed in cra-template-pwa
Then add the service-worker itself in the public folder, which should handle fetch and install events to enable the offline mode

This is what the dev tools showed when I tried this with the current manifest,  ⚠s on Installability of PWA

The third ⚠ says no service worker found, even though an SW is active. It has something to do with scope and start_url in the manifest.

So updating the manifest seems to be the first step. Since in index.html, all resources are hardcoded to be pulled from this repo. So, updating that would make it easier to work on service-worker and test rapidly in dev env.
Let me know what you think.


[wip] add kernels page

Problem
Using the kernels wiki page is very manual, not very compelling, and liable to get spammed at some point.
Proposed
This adds a curated, data-driven kernel page to jupyter.org, as requested from here.

original mockup
current demo (will always be the current state of this PR!)

Feedback welcome! Let's make something really great!
Data Model
Because of the interconnected, extensible nature of what we are trying to represent (kernels, features, language versions, actions for a kernel project, etc.) the data in kernels.json is captured as JSON-LD, which is just JSON, but every key means an URI, and some values are treated as URIs. I am not actually using jsonld.js yet, anyway.
I would be open to being convinced of not thinking about this data this way, but I'll fight you for it!
Content
I pulled what I could from the wiki page, but there is definitely going to be some data collection effort! However, it should really be a one-time big push, and could likely be crowdsourced with a google spreadsheet. Future changes would become the responsibility of the kernel authors!
Everything is in one file, which obviously doesn't need to be that way, but for the time being it was easy. Eventually, things like the specific features implemented should be created in a reproducible manner, as discussed here, and as such would live in a separate file.
Libraries
Because of the data-driven angle, I have used d3. It's a bit overkill for what is currently being done, i.e. the page could be pre-generated by Jekyll, and search implemented more simply, but it helps me build quickly while staying true to the data.
I am open to suggestion of some other framework (considered backbone initially), but I think d3 actually fits the bill pretty nicely. It's not commented very well either, which I will fix at some point.
CDN vs Bower
I have moved away from relying on CDN to bower... mostly for my sanity coding with spotty connectivity. If we're serious about performance, we should eventually do a build of CSS and JS, as one or two big files is almost always going to be a better optimization. The bower components are submoduled in at present... I imagine eventually that they would live right in master, and that we would build from separate branch... potentially deployed via travis, but I haven't set this up before.
Visual Design
I haven't strayed much from the bootstrap baseline, so it should be easy to add a bootstrap theme. Obviously, this would best be done site-wide. Here are some I liked:

http://www.bootstrapzero.com/bootstrap-template/clean
http://www.bootstrapzero.com/bootstrap-template/insight

...but really anything other than vanilla bootstrap, :pray:.

Yes, I agree with all of the motivational points!
Some other comments:

A simple button indicating "Magics" is not enough. These perhaps should be a link to a page/section that indicates more information. For example, many kernels have magics, but exactly how and which ones is an important point.
Popular/maintained/updated? How can we distinguish between those that work well, and those that don't? Crowd-sourcing here (eg, a "like" button) may be useful.
Sort order? Some that I would like: name, popularity, language, recently updated

I generally agree with @dsblank comments... also, this is really nice @bollwyvl!

:+1: Love this direction, thanks for taking the time to do it.
I'm a bit lost on what the colors mean here:

This will sound petty but I don't think we should show BrainFuck in the list (either that or censor out the F word).

Wnated to get some stuff out before :baby:.

A simple button indicating "Magics" is not enough.

Hadn't done a hierarchical feature, but sounds reasonable. I think "which magics" is a valid, question, but maybe buried under a link, or on a kernel-specific page.

Popular/maintained/updated?

Yeah, we're going to need some Github integration... otherwise this becomes a maintenance nightmare. I really don't want to be running another server for this, so client-side API calls might be the best way, but I am open to suggestion.

Sort order? Some that I would like: name, popularity, language, recently updated

Added. Updated and popularity are another story. I really think we'll have to go to pulling this off a repo (i.e. most recent tag), as I really don't want people to have to dink with this every day.

I'm a bit lost on what the colors mean here:

Sorry, left this in without meaning to before cleaning it up some more.
Related to the discussion of automated kernel feature tests, I want to visually depict for a given kernel/feature:

this kernel originated this feature (blue)
this kernel claims to implement this feature (yellow)
this kernel feature's test was successfully executed (green)
this kernel feature's test was not successfully executed (red)

This will sound petty

Removed. This, for example, would never have passed the PR process!

This is great! I probably wouldn't include 'magics' on the index at all. It's not something that anything in Jupyter is aware of. I think the only way it's useful is as a bool meaning 'extends the language syntax in some way', which I'm not sure is the most useful.

I would also remove the parallel computing piece as a feature mark. IPython.parallel is not planned to be extended to other Jupyter kernels.

@minrk I disagree about not listing magics... I think these can be an important component of a Jupyter kernel. It may be that a language has a method of performing such functionality, but to bring them out of the language and create a standard API is something that is quite useful.
And I see some very clever magic systems being developed (for example, some Javascript-based magics). I also see some that I'd love to see IPython adopt.
Seeing that you just added parallel to the suggestions of removing... I also disagree with the removal of that. There are a few kernels that implement parallel processing, and that can be an important feature.

I agree that BrainF@#k should be sanitized. I think it would be perfectly fine to use a better/different name. I have use BrainScrew in the past.
This does suggest just a couple of rules: no offensive or sexist language; probably a standard "code of conduct" statement should be linked to:
https://www.python.org/psf/codeofconduct/

I see your point about magics. If 'magic' is defined as 'extends the language in any way', a link to a URL explaining what a kernel adds to the respective language is appropriate. I would actually avoid the use of the term 'magics' in that case, though. That's what IPython happens to call its extensions to Python, but I think it indicates an intent to standardize language extensions across languages that we do not have.
I think including parallel computing is confusing, though. Going forward, for instance, the IPython kernel itself won't provide any parallel computing. A separate, derivative project called 'IPython parallel' does.

And almost all serious languages have some kind of functionality for parallelism, which you should be able to use from a Jupyter kernel for that language. The only particular integration with Jupyter, as far as I know, is the support for starting and stopping clusters using IPython parallel - and we should probably aim to justify that.

@takluyver I've thought about that, too, and I think we should remove the clusters panel from the notebook, and move it to IPython parallel as an nbserver extension.

Wow, thanks for all the feedback! Some good soul searching happening here.
I've made features into a filter, and added tooltips, but have downplayed them by removing the colors and moving them below the description. Also removed the offending parallel feature, and renamed "magic" to "language extension". I guess the best way to add "this is tested" is as an action (like docker, github or try.j.o), calling out to travis.
Additionally, I've tightened up the copy a bit, and would consider most of that no longer FPO: any additional insight welcome.
Finally, design: I've removed as many lines/borders as I could, hopefully this doesn't make it unclear what can be clicked. Now, really only the kernels themselves get a border, which seems like a good choice.
remaining tasks:

[ ] add github (anything else?) integration

[ ] stars/forks
[ ] most recent update (tags? master commit?)

[ ] tests (travis) action
[ ] tons of data entry
[ ] start applying themes?

remaining questions:

What else is missing from the feature list?
Should I just start trying out bootstrap themes? I don't want to bite off the whole build chain thing yet, though, so would be open to punting the themeing to a later date if we want to do a proper job of it.

I've tried added bootstrap material design! Obviously, we'll want to do a bit of color work, but I like what it does out of the box.
Also more copy changes etc.

I've tried added bootstrap material design!

Nice!

@damianavila thanks, and sorry about the typo! I had a whole thing expounding on why material was a good choice, but it is probably widely known enough now that it needs no introduction. Of course, one does simply add some drop shadows and square corners and call it Material Design, as I have, but it seems like a great springboard without having to use polymer.
@dsblank Thanks for that... as the wise man said, "I heard you like PRs in your PR". What are your thoughts on the data format? I have been wrestling with that in my mind: I like how Chef documents its cookbooks with a Markdown template from which data can be extracted, but I also like the universality of JSON... or YAML. Either way, we should probably provide markdown parsing inside the descriptions.

[ ] add markdown parsing to descriptions

I think to further streamline the process we'll want a JSON schema (whether it comes from Markdown or YAML)... then someone should be able to make the PR right from their browser, and an (unimplemented) travis script can check it out before a j.o person has to review it.

@dsblank I changed the URL to point at rawgit. I would indeed prefer to not force people to add logos to the repo, but we perhaps need to blacklist domains that don't like hotlinking. This was part of the original intent of tying all of this to the try.jupyter.org/docker-demo-images repos.

[ ] once validating data, blacklist hotlinking to rawgithubcontent

As an additional, nitpicky aside: does there exist a better version of that logo? It looks very pixelated at 64x64. Here, as well, in the original proposal, I'd really like to have big, background-agnostic SVGs... while these are not appropriate all over the place (in the notebook, etc... @minrk replied someplace to that effect) I think for a "marketing" site we should try to present the most polished face possible.

For sorry, there will be lots of criticism, but I really like it. Pretty in much in random order.
1 -  Features legend are I think too big, should be at the bottom IMHO
2 -  the layout has a lot of whitespace, I would use something like massonry.js if you want something more compact better on filtering.
3 - The "versions" number in blue are distracting/too big.
4 - the "computing" search field seems weird (I know Google Paper)
5 - "Shadow" inconsistent
Otherwise it's really nice.

I feel like I'm going to sound like such a curmudgeon but this bootstrap material design theme does not seem nearly as close to the material design spec as I read it and I :heart: the material design spec.
In particular, I think kernels being cards is a bit heavy. They've got a lot of the interactive bits right, but static layouts weren't given the same amount of emphasis.
They leave me at a disconnect because the cards all stand alone, floating in space.

@Carreau:
Thanks for the very precise, actionable feedback! I am not a graphic designer, so I don't have the "just make it look right" kung-fu down quite yet, and these help a lot.

1 - Features legend are I think too big, should be at the bottom IMHO

That answers my question if it was clear that they were also filters. Smaller and more button-y.

2 - the layout has a lot of whitespace, I would use something like massonry.js if you want something more compact better on filtering.

Looked at masonry... even went so far as to install it... brought in a ton of stuff. Also looked at isotope (hooray GPL'd JS). I rolled my own out of d3, and don't find it too crap... aside from the ragged bottom "row", but unless we control the height more rigorously, that's going to happen... and i might be able to work something out with a second pass. Regarding height: I would treat all of the copy about kernels as FPO... really, they should be limited to a tweet... or slightly more.

3 - The "versions" number in blue are distracting/too big.

I don't think they're smaller, but they are now much less pronounced. Feels okay.

4 - the "computing" search field seems weird (I know Google Paper)

Erm... yeah. I think so too, I guess once you get material design (or, have it forced on you), you'd know to look, or at least not be surprised. I've added a light yellow highlight.

5 - "Shadow" inconsistent

Using panels all over, should be more consistent. Also hit the front page.
@rgbkrk:
Thanks for the designerly feedback! You basically dropped the rant I didn't earlier.

I feel like I'm going to sound like such a curmudgeon but this bootstrap material design theme does not seem nearly as close to the material design spec as I read it and I :heart: the material design spec.

materialize would be another option, which I would happily explore if nobody is :trollface: BAH NO MATERIAL DESIGN. If so, we could give up the material design and go with primer but we're not entirely a subsidiary of github, even though all our stuff is built and half our data will come from there...

In particular, I think kernels being cards is a bit heavy. They've got a lot of the interactive bits right, but
static layouts weren't given the same amount of emphasis.

Another treatment would be what bs-md calls list groups and materialize calls collections. This would end up being more like bower.io. It would be simpler.
However i like the cards, and would rather we find a way to make them work...
materialize's cards are :100:x better... for example, their card reveal would be lovely: have the "front" be that big logo art I still want, and the structured data, then the unstructured data on the back (hide the logo).
Of course, for the pixel price of one button, we could toggle between card view and list view.

They leave me at a
disconnect because the cards all
stand alone, floating in space

There, fixed the haiku.
We can fix some stuff to the top... collapse and combine the search box, filters, and sorts into a full-bleed toolbar.... this would work (and likely be nice) for either cards or lists. I am wary of going with a sidebar for controls...

omg, I'm trying man. I love how much work you put into this.

@rgbkrk here's a shot at more motion (kinda that, WE NEED KERNELS. LOTS OF KERNELS feel) as well as a fixed header which will try to make better use of the screen, as well as give some context to what one is looking at.

mmm... I don't like how the jupyter icon goes small... if you want to include motion, I will delete the icon when you go down... that will give you more space for the text.... additionally, the transition is done by steps, I think a smooth transition would be a better fit...

I think the
[logo] Kernel

Kernel blahblah....

Is too much.
You could remove the H1 completly potentially having the logo float-right, and disapear on -sm or -xs.
Header should not have rounded corner on bottom if width 100%.

I think the feature and sort h4 are unnecessary.

@damianavila:

I don't like how the jupyter icon goes small..

I hope this new treatment is better?
@Carreau

You could remove the H1 completly potentially having the logo float-right, and disapear on -sm or -xs.

I think the logo is important: that space still needs something, perhaps a little architecture cartoon or something. Either way, it gets out of the way in a hurry. I've tested on ios and android, and it's almost feeling right...
I think the design is getting more robust. I am not sure if it has quite the impact yet that it should.
in trying to get an overall feel, I've done as much automated data collection as i can thus far: basically finding all the github projects :) I don't know how we want to maintain this "scraped" information: it seems like a periodic build will be better than making the client do all the API calls... or setting up an actual server, but nobody's looking for Another Thing to Maintain.
Which brings me to the build... on the one hand, i'd like jekyll to do it all, because it's just there. But it doesn't do bower or less, so maybe that's a non-starter. On the other, I think a node-based workflow is the best way to get to a production-quality site: all the image optimization, etc. So i guess i'll start meandering towards that (starting with a LESS build), and eventually get to something that Travis can do automatically?

I hope this new treatment is better?

Yep... btw... I see the logo and Kernel at the top and I like the idea to have it there, but I think they have to be centered. Not left-aligned.
Also, I think the cards is a better default than cells or list...

@bollwyvl Is this better?
https://cdn.rawgit.com/Calysto/calysto_scheme/a54ed235416d8f778253f7ece3a4e2f6ef4a4f41/calysto_scheme/images/logo-64x64.png

Do you want to list every implementation of an IPython kernel that there is around there (even the most hacky ones?)
Would it make sense to have a separation between certain certified  implementations that meet a certain quality, and the other ones?

I think we need to have some way of indicating quality. As @minrk mentioned the other week, though, it's probably tricky to do that with a manually maintained whitelist, because it's always going to be contentious for things that fall near the line.
I'm thinking more along the lines of an automatically calculated score, which could be based on things like Github stars, results of automatic testing, possibly download counts (though they're probably hard to compare for different kernels).

Sorry, I haven't touched this in a while.
Yeah, the original proposal on the linked issue included automated tests,
but there hasn't been much discussion around a formal approach to doing it.
Scores are tough, and can be gamed... not super worried about that.
Perhaps the good ol TRL scale:
https://en.wikipedia.org/wiki/Technology_readiness_level
Each has a type of information needed, from, say a gist up to membership in
the the particular kernel's inclusion in a package manager and use in other
packages. Again, hard to automate.
On Tue, Jun 16, 2015 at 1:55 PM Thomas Kluyver<EMAIL_ADDRESS>wrote:

I think we need to have some way of indicating quality. As @minrk
https://github.com/minrk mentioned the other week, though, it's
probably tricky to do that with a manually maintained whitelist, because
it's always going to be contentious for things that fall near the line.
I'm thinking more along the lines of an automatically calculated score,
which could be based on things like Github stars, results of automatic
testing, possibly download counts (though they're probably hard to compare
for different kernels).
—
Reply to this email directly or view it on GitHub
https://github.com/jupyter/jupyter.github.io/pull/7#issuecomment-112513847
.

Closing here to to keep a small number of PR openend that are actually worked on
fell free to reopen. You can also ping Brian if you want him to work on that with Auberon.
Thanks !

Agree with the queue gardening intent, and it would take a bit of work to rebase, but I still feel strongly about having a data-driven listing of (initially) kernels, and would be happy to work on this, especially with some guidance on the presentation!
I think prior to re-proposing this, we would need to figure out the build story... I'll go create a ticket!

I certainly still want a kernel listing.


[Feature Request] Skip ten pages button in reader

Why/User Benefit/User Problem
In EH in large CG collections, many almost identical images appear one after the other. A button to go through several pages at once would help to get to the next section more easily, especially since navigating with the scrollbar in very large collections is often very inaccurate.
What/Requirements
A new button in the reading view, next to the scroll bar, which advances 10 pages (or a configurable amount) when pressed.

Instead of skip ten pages, could maybe do jump to page xxx instead. Ten pages seems to specific and random.


Forcing dependencies in log files

It seems like our repo only had one log file that did not already have a target dependency: p3_wqp_ind_csv. For that target, the previous target name was p2_wqp_SC_csv, which was not a target name in our pipeline. I changed it to p2_wqp_SC_data.
Closes #91

Thanks for checking on this and catching the dependency issue with p2_wqp_SC_data. The code changes look good and the pipeline builds (and creates a non-empty ind file for that target), so I think this PR is ready to merge.
As an aside, I think the log files will be more useful once we're using a shared data cache instead of local copies of tar_meta(). Here's the outcome when I built the pipeline using your PR branch:

I think this small PR is helpful for illustrating that.


Rspec not including helpers after update

Hey, I updated rspec from 3.1.0 to 3.4.0 in my project and after that, I dont have access to helpers methods in views rspecs. Is it possible to include all helpers for all rspec test?

Can you provide more detail? We haven't changed anything specifically related to this.

While running spec I am getting sth like this:
ActionView::Template::Error:undefined method `search_fields_for' for #<#<Class:0x0000000b6725e0>:0x00000007e44e48>
When I will back to version 3.1.0 everyhing works.
maybe my gemfile is the cause.
group :test do
  gem "ammeter" , "~> 1.1.3" # specs for generators
  gem "capybara", "~> 2.4.4"
  gem "chromedriver-helper", github: "mars/chromedriver-helper", branch: "download-via-bucket-xml"
  gem "ci_reporter_rspec"    # XML output for Jenkins
  gem "ci_reporter_cucumber" # XML output for Jenkins
  gem "cucumber-rails", "~> 1.4.0", require: false
  gem "cucumber-timed_formatter", require: "timed" # Cucumber timings
  gem "database_cleaner", "~> 1.0.1", require: false
  gem "diff_matcher" # rspec hash_matching
  gem "email_spec"
  gem "execjs"

  gem "ffaker" # generate (Fake) data for seeds

  #=======
  # Guard
  #=====
  gem "guard"
  gem "guard-cucumber"
  gem "guard-rspec", require: false

  gem "kopflos", github: "niklas/kopflos" # eliminates browser window during cuke tests
  gem "launchy" # save_and_open_page
  gem "libnotify", require: false
  gem "pickle", git: "git://github.com/tbuehl/pickle.git"
  gem "rb-inotify", require: false
  gem "rb-fsevent", require: false

  #=======
  # RSpec
  #=====
  gem "rspec-rails", "~> 3.4.2"
  gem "rspec-its", "~> 1.1.0"
  gem "rspec-collection_matchers"

  gem "term-ansicolor" # Coloring for ScenarioTodo
  gem "timecop"
  gem "selenium-webdriver"
  gem "simplecov", require: false
  gem "slop" # for option-parsing in CI-script
  gem "zeus", require: false
end

Thank you for interest!

also when I add
 include CheckoutHelper
tests are working. But I cant include each helper manually. Is is possible to include them all?

/cc @samphippen

@gajewsky
Thanks for the issue. We need a little more detail to be able to reproduce this.
Could you please provide us with a rails app that we can clone that demonstrates the issue. Specifically it'd be great if

you could rails new an application and commit
make all the changes necessary to reproduce the issue and commit

then, provide us with a description of how to clone your application and reproduce the issue.
Thanks 👍 :)

Hey,
I'm a collegue of @gajewsky and have created a sample app where the application helpers are (sometimes) not available in view specs.
https://github.com/niklas/rspec-rails-3.4-helpers-notfound-views-example
The culprit seems to be the ammeter gem. It seems that the require 'rspec/rails in its init.rb causes that behaviour - some way.

@niklas since the problem is ammeter gem, can this issue be closed now?

@JonRowe I feel like we can close this because the cause is ammeter. Do you agree?

I think the cause is rails code loading, the trigger is just ammeter...

Closing as duplicate of #1644


pypi release not tied to rdflib==6.0.0 ?

I'm using rdflib 6.0.2, and I cannot pip install pyLODE because it requires rdflib==6.0.0. Could a new pypi release be pushed that works with rdflib>6.0.0? (it also could drop the rdflib-jsonld requirement if if requires rdflib>6.0.0, but that's a separate issue.)

I'm working on updating and making a release now. This should bypass PR #154

I think it will be fixed in version 2.13.0, but it hasn't been released yet.

I've pushed a very minor 2.13.0 to specifically deal with this issue. Apologies for the delay: time has been diverted to rdflib 6.1.0 release!

Fixed in 2.13.1


Adding Contributor section in readme ( Automatically )

This will add contributors' names automatically in the CONTRIBUTORS.md file. I will start working on this as soon I get assigned.

this is not required


Analyzer: no error when constant constructor redirects to non-constant

Consider the following program:
class A {
  final int i;
  const A(): this._(1);
  A._(this.i);
}

With dartanalyzer version 0.2.1-dev.4.0 this yields 'No issues', but it is a compile-time error for a constant constructor to redirect to a non-constant constructor (section 'Redirecting Generative Constructors'):
When $\ConstMetavar$ is \CONST{},
it is a compile-time error if the redirectee is not a constant constructor.

As an aside, the vm says 'A constant constructor can't call a non-constant constructor', so I believe that there is no need to create an area-meta issue for several tools.

An error is now reported:

error • Constant redirecting constructor can't redirect to a non-constant constructor. • 34509.dart:3:19 • redirect_to_non_const_constructor


fix: use DatabaseRef impl when fetching overriden account

Closes #3583
account needs to be fetched via databaseref trait

Oh man - this seems like a big footgun? How can we avoid this in the future?


Update concept-system-preferred-multifactor-authentication.md

Changed System preferred order for Certificate based from last option to be the 2nd as mentioned on wiki doc: https://supportability.visualstudio.com/AzureAD/_wiki/wikis/AzureAD/857237/Azure-AD-System-Preferred-MFA-Method-Policy?anchor=order-of-authentication-methods

@Justinha
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@miguel-s-ferreira @Court72 we confirmed a fix is planned soon. Let's close this PR for the time being and re-open it next week after fix is deployed.


Dept. Head Dresser + Locker Fixup

About the PR

Ever notice that your employees as a head of a department get guaranteed access to winter coats, but you don't? Ever notice for some reason the RD has their over ear headset spawn in their dresser and not their locker, and the QM gets an extra cargo headset, not qm headset, in their dresser? Not to worry, this PR is here to fixup all that
Why / Balance

A command headset for starts, should not be in an unprotected dresser, secondly the heads should have access to their winter coats incase it gets cold and or they want to look cool. I also saw the RD has free medical comms in their locker from the sci-med comms headset ( and they already get the extra channel of silicon! ) so I took that away from them too. I see no reason for the RD to get free med comms when the CMO gets no free research comms and also they shouldn't be double dipping comms anyways. Also the CMO spawns with their lab coat on, and has a spare in their dresser. If the map uses the hardsuit locker, that would spawn a third lab coat! Insanity!
Technical details

Added appropriate winter coats to the dressers of all the dept. heads
removed the spare cargo headset from the QM dresser
moved the over-ear headset from the RD dresser to the RD locker
removed the medical-science headset from the RD locker
added glasses to the HoP, CMO and RD dressers (nerds)
removed the CMO lab coat from the CMO locker
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Dept. Heads are now guaranteed to have their respective winter coats in their dressers
tweak: Standardized the contents of Dept. Heads dressers and lockers

good pr

can you please look up on this #25186

can you please look up on this #25186

That is what inspired me to do this in the first place, I am drafting up new items for the RD already, as well as for the HoP and the CMO seeing as the other command member have significantly more options than them.


[FEATURE] Memory Limits

What
Docker based memory limit per node container. Separate limits for servers and agents. Also, per single node limiting is possible when creating nodes one after another using k3d node create.
Why
See issue #491 and mentions.
This is an implementation of docker-based memory limiting per node type (server/agent) that tries to make those limits also visible to kubelet via cadvisor, so that kubectl describe node gives proper (limited) memory capacity and does not schedule pods when limits are reached.
In my tests it works as expected, below is a simple demonstration:
Create a cluster:
$ ./k3d cluster create test --no-lb --servers-memory 1g --agents 1 --agents-memory 1.5g

Docker stats:
$ docker stats
CONTAINER ID   NAME                CPU %     MEM USAGE / LIMIT   MEM %     NET I/O          BLOCK I/O         PIDS
0b2607a587b2   k3d-test-agent-0    186.49%   138.3MiB / 1.5GiB   9.00%     68.4MB / 919kB   57.3kB / 33MB     73
7d0f1e5f289e   k3d-test-server-0   28.14%    465.2MiB / 1GiB     45.43%

Nodes description (memory fragment):
$ kubectl describe nodes | grep memory
  MemoryPressure       False   Fri, 12 Feb 2021 21:16:59 +0100   Fri, 12 Feb 2021 21:16:28 +0100   KubeletHasSufficientMemory   kubelet has sufficient memory available
  memory:             1073741Ki
  memory:             1073741Ki
  memory             0 (0%)    0 (0%)
  MemoryPressure       False   Fri, 12 Feb 2021 21:17:09 +0100   Fri, 12 Feb 2021 21:16:38 +0100   KubeletHasSufficientMemory   kubelet has sufficient memory available
  memory:             1610612Ki
  memory:             1610612Ki
  memory             70Mi (4%)  170Mi (10%)

Here, provision something that will surely reach the limits. I deployed 10 replicas of a service that needs 100m CPU and 300Mi memory. The 8th replica is in a pending state due to lack of memory:
$ kubectl get pods
static-file-server-statefulset-0   1/1     Running   0          57s
static-file-server-statefulset-1   1/1     Running   0          49s
static-file-server-statefulset-2   1/1     Running   0          47s
static-file-server-statefulset-3   1/1     Running   0          44s
static-file-server-statefulset-4   1/1     Running   0          38s
static-file-server-statefulset-5   1/1     Running   0          35s
static-file-server-statefulset-6   1/1     Running   0          33s
static-file-server-statefulset-7   1/1     Running   0          30s
static-file-server-statefulset-8   0/1     Pending   0          28s

$ kubectl describe pod static-file-server-8
...
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  54s   default-scheduler  0/2 nodes are available: 2 Insufficient memory.
  Warning  FailedScheduling  54s   default-scheduler  0/2 nodes are available: 2 Insufficient memory.

Let's see the resources:
$ kubectl describe nodes | grep memory
  MemoryPressure       False   Fri, 12 Feb 2021 21:18:39 +0100   Fri, 12 Feb 2021 21:16:38 +0100   KubeletHasSufficientMemory   kubelet has sufficient memory available
  memory:             1610612Ki
  memory:             1610612Ki
  memory             1570Mi (99%)  1670Mi (106%)
  MemoryPressure       False   Fri, 12 Feb 2021 21:18:58 +0100   Fri, 12 Feb 2021 21:16:28 +0100   KubeletHasSufficientMemory   kubelet has sufficient memory available
  memory:             1073741Ki
  memory:             1073741Ki
  memory             900Mi (85%)  900Mi (85%)

Look good I guess? 😉
Implications
The route taken was vastly different from what was previously tried. After investigating cadvisor source code it seems that it uses /proc/meminfo to read the available total memory and swap. The main idea behind this implementation is to simply create a minimal, fake meminfo file and mount it as read-only to the node containers.
Other stuff worth mentioning in a "tldr" version below:

this of course breaks parts free, top as well as for example prometheus node exporter etc. but those were already "broken" for k3d as they showed host, not container resources
serversMemory, agentsMemory options under "runtime" yaml conf
servers-memory, agents-memory cli args under cluster create
memory arg under node create
valid values and units are the same as for docker limits
fake meminfo is created during the creation of any node that has limits. It is a file in a hidden folder placed in ~/.k3d as it needs to persist across reboots potentially. It is (the folder) made unique per node using the name of the node for which it was created.
removal is performed during the node (or cluster) removal
even in the case of manual container removal when the folder cannot be cleaned, it simply either won't be taken into consideration in the case of no-limited new nodes or the files will be overwritten when the same named node is created in the future
fake meminfo is truly minimal, it contains only swap and total memory info

Further work
Potentially TODO is a check that someone wants to create containers that have larger memory limit (in total) than the current machine allows. This is not validated currently but maybe should not be checked in the first place? When creating servers and agents without limits, the total memory limit is always larger than the memory of the host.
CPU limits need a little bit more work but I'm pretty sure they can be implemented in a very similar way. I can start doing this after receiving positive feedback on this one
Seems like cores number is read from cpuinfo as a last resort. First, the topology of the cpu is built based on the sysfs. Minimal mocking and mounting cpus under sysfs crashes k3s, so full-fledged solution would be needed. In short, cpu seem like a no-go at the moment, unless something comes to my mind along the way.
Edit 1:
Moved from singular files to a folder for easier further mocking.
Currently working on a "edac" folder mock. The above solution for memory limit works on a non-ecc memory. I cannot test, but I think it won't work on ecc memory, as the true, larger capacity will be read from the "edac" folder. We cannot just mount fake edac always because when it does not exist on the host (for example my macbook) it will fail. Sysfs is read only in docker, so docker cannot create this folder if it does not exist in the system. The solution is to check if it exists but this gets tricky on docker for mac and docker for windows.
Edit 2:
Mocking edac to force using meminfo is now working (checked on linux with existing edac folder, but no ecc memory) and is made through an in-container directory existence check so it is universal and should work across linux, windows and mac.

Also, this may be interesting for you: https://github.com/k3s-io/k3s/pull/3005

Also, this may be interesting for you: k3s-io/k3s#3005 (good progress lately: https://twitter.com/AkihiroSuda/status/1366689973672402945)

Thanks, I'll follow and investigate this one. It seems it requires running systemd inside the container... we'll see.

LGTM!
I'll test it a bit on my systems now and then will go ahead and merge it, if everything's fine :+1:

Hi @konradmalik , I just tested this on my Linux machine and it seems to fail :thinking:
$ kubectl get nodes -o go-template='{{range $index, $item := .items}}{{ $item.metadata.name }}{{ ":"}}{{ $item.status.capacity.memory }}{{ "\n" }}{{ end }}'
Alias tip: kgno -o go-template='{{range $index, $item := .items}}{{ $item.metadata.name }}{{ ":"}}{{ $item.status.capacity.memory }}{{ "\n" }}{{ end }}'

k3d-memtest-agent-0:32475116Ki
k3d-memtest-server-0:32475116Ki

$ docker inspect k3d-memtest-server-0 | jq '.[0].HostConfig.Memory'
1073741824

$ docker inspect k3d-memtest-agent-0 | jq '.[0].HostConfig.Memory'
1610612736

Note: edac folder is present on my machine.

ha, no wonder it did not work. Volume binding was reversed :smile:  any idea what could cause the order to change? For sure was working before :thinking:
    {
        "Type": "bind",
        "Source": "/proc/meminfo",
        "Destination": "/home/konrad/.k3d/.k3d-memtest-server-0/meminfo",
        "Mode": "ro",
        "RW": false,
        "Propagation": "rprivate"
    },

anyway, the newest commit fixes this

Hi @konradmalik , finally I found some time to get back to this :)

Volume binding was reversed smile any idea what could cause the order to change?

Nothing changes afaik and the order should always have been src:dest (hostpath:containerpath) :thinking:


Email templates

Would be great to have one example at least of the email templates.

For instances
{% load i18n %}{% blocktrans %}Hello!

You're receiving this e-mail because you or someone else has requested a password for your user account.
It can be safely ignored if you did not request a password reset. Click the link below to get the token.{% endblocktrans %}

{{ reset_password_url }}

Then, if you go to /test_app/reset-password/confirm/, you can paste the token and the new password.

{% if email %}{% blocktrans %}In case you forgot, your email is {{ email }}.{% endblocktrans %}

{% endif %}{% blocktrans %}Have a great day!
{% endblocktrans %}

Thank you for your comment. Yes, that surely would be helpful for new users! However, the template belongs to the users project tree, the template-example should be mentionend in the readme in the email-section. Can you create a pull request for your example, so we can add it to the repository?
To do this, first you have to fork our repo and create a new branch. Then add your example-template to the README.md under the subsection "Example for sending an e-mail". Next, you start a pull-request from your repo to our (upstream) repo via the github-interface, see this guide for more information: https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork
Let me know if you need help with this!

I think this could go hand in hand with https://github.com/anexia-it/django-rest-passwordreset/issues/103 (Creating an example project).
I believe it would be easier to have a full example project (with templates, etc...) as a separate repository and just link to this project.

I have some questions. from the email template what I have understood is we have to provide two links in the email. One is to generate the token One is to add the token and a new password to reset the password. if yes I am right? then it is not better to just send the token to the user on his email and provide only the link to reset the password? Please let me know thanks

Quick question, where should the templates live? I placed them in the template folder in the main directory (where asgi.py and url files are) and it couldnt find them. However it only searched other 3rd party packages as can be seen here:

Any advice would be super helpful. For reference there are no other templates in this project because of a React Frontend.


CI-CD_dhairya branch

CI-CD Reasearch documents for Onprem and Azure

PDFs should not be uploaded unless directly referenced for download or viewing through embedding or markdown. Please convert the PDFs to Markdown.


How to compare each member of two identical structure values?

I'm writing a Settings feature for my program. After the members are modified at runtime and committed, I need to compare them and call the member handler for each modified member.
A simplified short example: https://godbolt.org/z/Y7PKbrqe5
pfr::get only accepts an index as a non-type template parameter, so I obviously can't enumerate at runtime with fields_count.
I didn't find a solution from the docs, am I missing something?
Any help would be appreciated.

Oh, I found an existing issue #69, sorry to open this new one.


needs the wrapper

either tristate, or use the JTAG idea. needs more research

closed with https://github.com/mattvenn/scan_wrapper


Schema commands error out with 'The "maxTimeMs" option does not exist.'

Bug Report

Q
A

BC Break
yes

Version
2.0.0-beta1

Summary
When trying to execute doctrine:mongodb:schema:create, doctrine:mongodb:schema:update or doctrine:mongodb:schema:drop from DoctrineMongoDBBundle an error 'The "maxTimeMs" option does not exist.' is printed out and the command fails.
Current behavior
Changes introduced in this commit introduced common options for schema related commands in \Doctrine\ODM\MongoDB\Tools\Console\Command\Schema\AbstractCommand::configure(). However, since parent::configure() call is missing from the configure() method in all of \Doctrine\ODM\MongoDB\Tools\Console\Command\Schema\UpdateCommand, \Doctrine\ODM\MongoDB\Tools\Console\Command\Schema\CreateCommand and \Doctrine\ODM\MongoDB\Tools\Console\Command\Schema\DropCommand, the options are not present and trying to use them causes an error.
How to reproduce
Install and configure doctrine/mongodb-odm-bundle in dev-master version in any Symfony project and execute any execute one of the mentioned commands.
Expected behavior
The command should not fail.
I guess adding the parent::configure() call to AbstractCommand will fix the problem. I can prepare a PR if that's the only required fix here. Also, I don't think \Doctrine\ODM\MongoDB\Tools\Console\Command\Schema\ValidateCommand or \Doctrine\ODM\MongoDB\Tools\Console\Command\Schema\ShardCommand use the new common schema command options anywhere and they don't really make much sense for them, so they should not be changed.

Thanks for the report. I'll prepare a fix shortly 👍

I can prepare a fix, it's not a problem. Just let me know if the solution I suggested is ok.

The solution is good. ValidateCommand doesn't need any of the options, that is correct. For the ShardCommand, we can pass a write concern to the respective schema manager methods and runShardCollectionCommand as shardCollection takes a write concern (see https://docs.mongodb.com/manual/reference/command/shardCollection/#dbcmd.shardCollection). I forgot about that when adding the options. We can also add that in a separate PR if you want to leave it out.
Either way, a PR with fixes is highly appreciated 👍

@alcaeus Ok, a PR is ready - https://github.com/doctrine/mongodb-odm/pull/1918 .


Nd4j.pullRows() -> Nd4j.pull()

Since we already have TAD-based native pullRows impl, it would be nice to have it universal in terms of source dimensions.

pullRow -> pullColumn was added, at next pass generic tad should be added

Time to do this would be now. Next release will be 0.8.0


Update hosted virtual staining config files for 0.3.0

#153 introduces breaking changes that requires the virtual staining configs hosted on the public HTTP server to be updated. We currently point reviewers to v0.2.1 so we should probably update them later, or we can host configs for both versions?

we will make a new folder under the examples/configs. We will add a text file that ask the users to use the ones in the repo.


Download videos from likee.com

Checklist

[ ] I'm reporting a new site support request

Example URLs

Single video: https://likee.com/@Inayat95/video/6792552721999608595

Description

please support download videos from likee.com

I'll take this!

The video can be downloaded using the generic extractor:
python youtube_dl/main.py --verbose https://likee.com/@Inayat95/video/6792552721999608595
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'https://likee.com/@Inayat95/video/6792552721999608595']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2020.03.24
[debug] Git HEAD: 049c0486b
[debug] Python version 2.7.17 (CPython) - Linux-5.3.0-42-generic-x86_64-with-Zorin-15-bionic
[debug] exe versions: ffmpeg 3.4.6, ffprobe 3.4.6
[debug] Proxy map: {}
[generic]<PHONE_NUMBER>999608595: Requesting header
WARNING: Falling back on generic information extractor.
[generic]<PHONE_NUMBER>999608595: Downloading webpage
[generic]<PHONE_NUMBER>999608595: Extracting information
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on u'https://video.like.video/in_live/2nu/18WqFM_4.mp4?crc=361017319&type=5'
[download] Destination: Mr.Aayat🐰(Inayat95) on Likee Mobile - chand bhi h dewana tera😉 #BroomChallenge #WeeklyHighlights #HiLikee #VideoTalent @Likee Official -18WqFM_4.mp4
[download]  19.2% of 4.42MiB at 97.02KiB/s ETA 00:37^C
@dstftw , should I nevertheless implement an extractor?

thanks my problem is with when add -j and in json the format id is not in fomats:
{"id": "18WqFM_4", "uploader": "likee.com", "title": "Mr.Aayat\ud83d\udc30(Inayat95) on Likee Mobile: chand bhi h dewana tera\ud83d\ude09 #BroomChallenge #WeeklyHighlights #HiLikee #VideoTalent @Likee Official ", "age_limit": 0, "url": "https://video.like.video/in_live/2nu/18WqFM_4.mp4?crc=361017319&type=5", "extractor": "generic", "webpage_url": "https://likee.com/@Inayat95/video/6792552721999608595", "webpage_url_basename": "6792552721999608595", "extractor_key": "Generic", "playlist": null, "playlist_index": null, "display_id": "18WqFM_4", "requested_subtitles": null, "format_id": "0", "format": "0 - unknown", "ext": "mp4", "protocol": "https", "http_headers": {"User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3723.0 Safari/537.36", "Accept-Charset": "ISO-8859-1,utf-8;q=0.7,*;q=0.7", "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8", "Accept-Encoding": "gzip, deflate", "Accept-Language": "en-us,en;q=0.5"}, "fulltitle": "Mr.Aayat\ud83d\udc30(Inayat95) on Likee Mobile: chand bhi h dewana tera\ud83d\ude09 #BroomChallenge #WeeklyHighlights #HiLikee #VideoTalent @Likee Official ", "_filename": "Mr.Aayat\ud83d\udc30(Inayat95) on Likee Mobile - chand bhi h dewana tera\ud83d\ude09 #BroomChallenge #WeeklyHighlights #HiLikee #VideoTalent @Likee Official -18WqFM_4.mp4"}

so i found out later


Python protoc compiler plugin segfaults

The Python protoc compiler segfaults with grpc compiled from trunk at 5ac82e2 (protobuf at 39f9b43)
I debugged a bit and the cause seems to be https://github.com/grpc/grpc/commit/d953959e2bafd645b6ed674861a310daba5f80ae#commitcomment-19947519
This happens on Ubuntu 16.04, but I suspect it would be the same on all platforms.
Repro:
/usr/local/bin/protoc --python_out=. --grpc_out=. --plugin=protoc-gen-grpc=/usr/local/bin/grpc_python_plugin foo.proto

Pasting from the commit comment, as linking to a commit comment doesn't seem to work:

Duplicate of #8753.


⚠ Fortnite has degraded performance

In cfe23db, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1611 ms

Resolved: Fortnite performance has improved in b0b9db2.


Source related to 2.13.2

Hi,
This is not an issue but more related to 2.13.2 source, I did not find this source anywhere, and also there is no place I can request for it, hence raising an issue, hoping to get some help here.
We are using Media element player 2.13.2, there are few issues reported on this player, which we would like to fix, as the customer is not willing to move to latest version, where we might leverage the the latest Media element player.
Can you please point us to 2.13.2 source code along with flash plugins, so that we can work on a fix and ship it to our customer.
Regards
Srinivas Masam

Here's the link: https://github.com/mediaelement/mediaelement/releases/tag/2.13.2. Hope that helps you. Please star the project so we continue maintaining it. Thanks

Thank you


Geocoder produces PG::SyntaxError on rails 4.1 for count queries

After upgrade to rails 4.1 Geocoder fails to count the number of results when searching by distance. I have reproduced it with a very simple example:
> Place.all.near([0.05, 0.1], 10, units: :km).count
SELECT COUNT(places.*, 6371.0 * 2 * ASIN(SQRT(POWER(SIN((0.05 - places.latitude) * PI() / 180 / 2), 2) + COS(0.05 * PI() / 180) * COS(places.latitude * PI() / 180) * POWER(SIN((0.1 - places.longitude) * PI() / 180 / 2), 2))) AS distance, CAST(DEGREES(ATAN2( RADIANS(places.longitude - 0.1), RADIANS(places.latitude - 0.05))) + 360 AS decimal) % 360 AS bearing) FROM "places"  WHERE (places.latitude BETWEEN -0.039932160591873045 AND 0.13993216059187305 AND places.longitude BETWEEN 0.010067805164487686 AND 0.18993219483551232 AND 6371.0 * 2 * ASIN(SQRT(POWER(SIN((0.05 - places.latitude) * PI() / 180 / 2), 2) + COS(0.05 * PI() / 180) * COS(places.latitude * PI() / 180) * POWER(SIN((0.1 - places.longitude) * PI() / 180 / 2), 2))) <= 10)
PG::SyntaxError: ERROR:  syntax error at or near "AS"
LINE 1: ...((0.1 - places.longitude) * PI() / 180 / 2), 2))) AS distanc...

In Rails 4.0.4 was
SELECT COUNT(*) FROM "places" WHERE (places.latitude BETWEEN -0.039932160591873045 AND 0.13993216059187305 AND places.longitude BETWEEN 0.010067805164487686 AND 0.18993219483551232 AND 6371.0 * 2 * ASIN(SQRT(POWER(SIN((0.05 - places.latitude) * PI() / 180 / 2), 2) + COS(0.05 * PI() / 180) * COS(places.latitude * PI() / 180) * POWER(SIN((0.1 - places.longitude) * PI() / 180 / 2), 2))) <= 10)
=> 0

Normal query work still in 4.1.0:
> Place.all.near([0.05, 0.1], 10, units: :km)
SELECT places.*, 6371.0 * 2 * ASIN(SQRT(POWER(SIN((0.05 - places.latitude) * PI() / 180 / 2), 2) + COS(0.05 * PI() / 180) * COS(places.latitude * PI() / 180) * POWER(SIN((0.1 - places.longitude) * PI() / 180 / 2), 2))) AS distance, CAST(DEGREES(ATAN2( RADIANS(places.longitude - 0.1), RADIANS(places.latitude - 0.05))) + 360 AS decimal) % 360 AS bearing FROM "places"  WHERE (places.latitude BETWEEN -0.039932160591873045 AND 0.13993216059187305 AND places.longitude BETWEEN 0.010067805164487686 AND 0.18993219483551232 AND 6371.0 * 2 * ASIN(SQRT(POWER(SIN((0.05 - places.latitude) * PI() / 180 / 2), 2) + COS(0.05 * PI() / 180) * COS(places.latitude * PI() / 180) * POWER(SIN((0.1 - places.longitude) * PI() / 180 / 2), 2))) <= 10)  ORDER BY distance ASC
=> #<ActiveRecord::Relation []>

Model:
class Place < ActiveRecord::Base
  reverse_geocoded_by :latitude, :longitude
end

Schema:
ActiveRecord::Schema.define(version:<PHONE_NUMBER>2943) do
  # These are extensions that must be enabled in order to support this database
  enable_extension "plpgsql"

  create_table "places", force: true do |t|
    t.datetime "created_at"
    t.datetime "updated_at"
    t.float    "latitude"
    t.float    "longitude"
  end
end

Tested with
ruby 2.1
rails 4.1.0 (worked with rails 4.0.4)
geocoder 1.1.9 and master @2a29613acda2468e23056921cc257252d2128ea8
postgresql 9.1

I just want to point the next googler to the Readme - https://github.com/alexreisner/geocoder#rails-41-note

Link moved to: https://github.com/alexreisner/geocoder#using-count-with-rails-41

I'm getting this same error in rails 4.2 even with the argument as suggested.

I have this (or related) issue when i upgrade from rails 5.1 to 5.2 or higher, and the count(:all) solution does not work, because a call limit after the near statement:
locations.near(current_location, radius).limit(100).count(:all)
*** ArgumentError Exception: wrong number of arguments (given 0, expected 1)

nil


#TS91-project card display on the UI after selecting the project

User Story
Project Creation
Type of change

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

Change Description
Once the project UI card is clicked you will be navigating to the next page with project name and description

Merging the code after approval.


CUDA driver version is insufficient for CUDA runtime version

face_recognition version:
Python version:3.6.3
Operating System:Ubuntu 16.04
CUDA: 9.1.85
NVIDIA-driver: 390.25

Description
Describe what you were trying to get done.
Tell us what happened, what went wrong, and what you expected to happen.
IMPORTANT: If your issue is related to a specific picture, include it so others can reproduce the issue.
I just executed first command from the documentation
$ sudo face_recognition ./i_know ./identify
but it throws me an error like this:
Traceback (most recent call last):
File "/usr/local/bin/face_recognition", line 7, in
from face_recognition.cli import main
File "/usr/local/lib/python2.7/dist-packages/face_recognition/init.py", line 7, in
from .api import load_image_file, face_locations, batch_face_locations, face_landmarks, face_encodings, compare_faces, face_distance
File "/usr/local/lib/python2.7/dist-packages/face_recognition/api.py", line 24, in
cnn_face_detector = dlib.cnn_face_detection_model_v1(cnn_face_detection_model)
RuntimeError: Error while calling cudaGetDevice(&the_device_id) in file /tmp/pip-build-IQQgTo/dlib/dlib/dnn/gpu_data.cpp:178. code: 35, reason: CUDA driver version is insufficient for CUDA runtime version
What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

Typically that means the video driver module that is running doesn't match the version of the CUDA library on disk.
Maybe you applied an automatic Ubuntu update or something that got things out of sync. You might try just rebooting or worst case, re-installing the NVIDIA video driver and CUDA.

@manu310397 , I also encountered this issue, it could caused by the automatic driver installation mismatch.
Normally you need to download the latest CUDA toolkit run file from nvidia develop website, if your video card is new, then you can found the driver number (say 418.56) in the first character screen.
After adding nvidia ppa source, and updating, you can find the driver list with key "TAB" after sudo apt install nvidia-, you will find relevant driver number (418 as example) in the list, then you can run command sudo apt install nvidia-*-418.
Then you can install CUDA, CUDNN, DLIB.
Eventually, you will find something like following output using nvidia-smi:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.56       Driver Version: 418.56       CUDA Version: 10.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 105...  Off  | 00000000:01:00.0  On |                  N/A |
|  0%   40C    P8    N/A /  80W |    935MiB /  4038MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1022      G   /usr/lib/xorg/Xorg                            26MiB |
|    0      1134      G   /usr/bin/gnome-shell                          47MiB |
|    0      1325      G   /usr/lib/xorg/Xorg                           204MiB |
|    0      1458      G   /usr/bin/gnome-shell                         196MiB |
|    0      2433      C   /usr/bin/python3.6                           455MiB |
+-----------------------------------------------------------------------------+

I got same issues and solved refer to #1205

@ageitgey @Professor-Paradox now 440 driver is not working anymore


How To Pass Props in Actions.Push?

Hi
I try Pass Props in Actions Push but does not work .
my code is :
onPress={()=>Actions.push('blogDetail',{Blog:BlogDetail})}

Please, when opening a ticket, provide the information that is asked in the template. Without knowing that - it's not possible to help you.


etcd_additional_envvars changed names

The env vars variable name changed. The one in the template no longer matches the one in defaults/main.yml or what it was before. I reverted it to the old name to maintain backward compatibility.

I feel like I'm being such a nag these last few days, but thank you for working so hard on this repo.


1.16.5] Warforged Tools are unusable with intigration

when you warforge a tool, you hold right-click to charge it up. but when this addon is added, this feature breaks (note: it can only be done in mining mode ftr)
can you please look into this?

I can look into this, but I'm not sure if I will fix it if it proves to be complex. This mod is mainly intended for Tetra integration, but I've written it carefully so that it doesn't focus on it, but rather allows for any mod that uses NBTs to fit into the mod. I don't want to focus on just Tetra integration.

the main issue is that its not charging up for some reason, and for it to work (and I'm not expecting you to fix this part in particular) only can be done in miner mode, due to shielding in combat mode

It has something to do with epic fight thinking it is a guard even if you are out of combat and don't have a guard skill. Might not be possible to fix without change on epic fight or tetras side.
throwing a throwing knife works with a bit of a jank animation but it works and setting the weapon to be a dagger makes it function because daggers can't guard.
A workaround I just found is to set warforged things to be pickaxes as they can't block and have closer animation than daggers, this allows them to function in combat mode and out.


Set up physical device

Met with Veli-pekka and waiting for his reply on the availability of the device
-> Alternative option is to order the motor and encoder and DIY


Comma between tags is inside inline code box, instead of between boxes

Please ensure:

[X] The bug is caused by Refined GitHub. It doesn't happen if I disable the extension.
[X] The bug happens after clearing extension cache. The "Clear cache" button below can also be found at the bottom of the options page.

Example URLs
https://github.com/jakebailey/pyright-action/commits/v1.0.4
Extension version
22.3.3
Browser(s) used
Chrome
Description
Have two tags on the same commit, like:

Include in this issue:

[X] Screenshots/video/gif demonstrating the bug, if it’s visual
[ ] Console errors, if any

This already works correctly, you'll see the fix in the next release
Latest release

Unreleased version:

Tested on https://github.com/fregante/daily-version-action/commits/master

Thanks; I can see that it was fixed in #5416.


razzle\config\jest\babelTransform.js doesn't pickup babel config and don't respect modified paths

🐛 Bug report
Current Behavior
if babel config file is anything besides default .babelrc (let's say .babelrc.json as I prefer extensions) then it will not be picked up by razzle test command as razzle\config\jest\babelTransform.js checks only for default .babelrc.
Using modifyPaths also doesn't work as it result is not passed to razzle\config\jest\babelTransform.js.
Expected behavior
Any valid default locations of babel config is picked up by razzle test.
Using modifyPaths also should work with razzle test.
Your environment

Software
Version(s)

Razzle
^4.2.13

Razzle Plugins

Node
v16.13.2

Browser

npm/Yarn
8.1.2

Operating System

TypeScript

React

Not sure if that is doable. Maybe using env vars somehow..