0.4 stable

Fix for#165 and #271 - Android 6.0 crashing on devices such as Xperia Z5 Compact, Z5 Bond and others.
It passes the activity to the package, manager and view so that it can be used in place of the app context when initialising the MapView component.
The new code as also been tested on the following devices to ensure it continues to work as before:
Nexus 4 (Android 5), Nexus 5 (Android 6), Nexus 6P (Android 6)
It requires a change to an app's MainActivity.java to pass this when creating the AirPackage: new AirPackage(this) rather than new AirPackage() in the current version.

Thanks for finding the issue and fixing it! I think the example app will need to be updated too.

@locly Nice! Yea, could you update the example to pass this when declaring the package. Thanks!

Yes - have updated the example to declare the package with new AirPackage(this)

@locly looks good! thanks for the PR merging

@locly just realized this was for the 0.4-stable branch. I think this should also work for master, any reason not too?
I can do it for master unless you want to tackle this.


No function clause matching in Wallaby.Query.ErrorMessage.method/2

When I call assert_has(session, Query.text("my text")) and Wallaby doesn't find an element with the text, I see this error:
** (FunctionClauseError) no function clause matching in Wallaby.Query.ErrorMessage.method/2
     stacktrace:
       (wallaby) lib/wallaby/query/error_message.ex:81: Wallaby.Query.ErrorMessage.method(:text, false)
       (wallaby) lib/wallaby/query/error_message.ex:65: Wallaby.Query.ErrorMessage.found_error_message/1
       (wallaby) lib/wallaby/query/error_message.ex:12: Wallaby.Query.ErrorMessage.message/2

When I change the call to:
# the same xpath used by Query.text
assert_has(xpath(".//*[contains(normalize-space(text()), 'my text')]"))

I see the expected error message:
** (Wallaby.ExpectationNotMet) Expected to find 1, visible element that matched the xpath './/*[contains(normalize-space(text()), 'my text')]' but 0, visible elements were found.

Seems like lib/wallaby/query/error_message.ex is lacking these:
def method(:text, true), do: "texts"
def method(:text, false), do: "text"

Thanks @viniciussbs. I've submitted a PR which fixes this.


CAMEL-10958 camel-scala-starter starter module removed but references to it still exist

https://issues.apache.org/jira/browse/CAMEL-10958
Remove references to camel-scala-starter.

Thanks for the PR it has been merged. Do you mind closing this?


DCOS-14911: Universe package grid update

This PR...

Adjusts the styling on the packages grid
Adjusts the styling on the package detail view
Renames "Selected" to "Certified"
Changes the packages table into a second grid of packages (now called "Community")
Adds .badge--primary
Removes icon size overrides and updates the icon size in the service create modal

Checklist

[x] Did you add a JIRA issue in a commit message or as part of the branch name?
[ ] Did you add new unit tests?
[ ] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

run integration tests

run unit tests

run unit tests

run unit tests

run unit tests

run integration tests

LGTM 💯 👍  :shipit:

This looks good to me, please rebase so we can merge!


Respawn timers added to the slayer plugin

Is your feature request related to a problem? Please describe.
Currently the slayer plugin has the options to highlight npc's in the same fashion as the NPC indicator plugin, it has most of the features except respawn timers. so if I want respawn timers I have to use npc indicators AND slayer indicators at the same time.
Describe the solution you'd like
Adding the respawn timer functionality to the slayer plugin.
Describe alternatives you've considered
Just use the Npc indicators and remember to untag the mob after im done.
Additional context
Not a big deal at all, would just be a nice QOL change. As it would only highlight mobs and show its respawn timers when im on task, makes it so I dont have 10 billion skeletons, dwarfs and other stuff tagged when im off task. Also is a nice way to see when I finish a task with the indicators disappearing.
Kinda similar to this issue, https://github.com/runelite/runelite/issues/3730, but its rather old so not sure if the slayer plugin even had highlight functionality back then

Duplicate of #3730


Support nested filter object

There are two problems when a deep property is specified in Filter like:
const MyFilter = props => (
  <Filter {...props}>
    <TextInput source='foo.bar' label='Foo' />
  </Filter>
);

const MyList = props => (
  <List {...props} filters={<MyFilter />}
    ...
  </List>
);

Invalid query string (E.g. "foo=%5Bobject%20Object%5D") is generated for json server. This should b flatten like "foo.bar=val".
When the text input value is cleared, the filter value is not removed from filter parameters.

Thanks!


API Page / Documentation Missing and/or Inaccurate

On this page: https://github.com/ncuillery/angular-breadcrumb/wiki/API-Reference
This documentation states one thing, and it just doesn't look like compilable javascript. I added it to my code and it doesn't work. I've tried the documented way as well as similar (non-syntax erroring) ways to handle this to no avail.  Any help on how to actually write this out would be great.
There is a statement: Both declarations (string or function) accept url params. The syntax is the same as the UI-router uiSref directive :
$stateProvider.state('product.detail', {
  url: '/{productId}',
  views: [...],
  ncyBreadcrumb: {
    parent: 'category.list({cat: 'product'})'
  }
})

Maybe you are disturbed by the [...]: Of course it's not compilable javascript, it's an ellipsis for the views definition.
You must include the real views definition here (or a couple controller / view). See the UI-Router doc for details.

Okay. I guess you caught me not being specific enough. I'm actually talking about the specific line:
parent: 'category.list({cat: 'product'})'

I'm not disturbed at all. I like your library, but the documentation is off. And personally, the views has nothing to do with ncyBreadcrumb at all, unless I'm mistaken.

My bad !
I didn't see the mistake with the single quote.
I fix it,
Thanks


AGPUSH-2201 remove support from MPNS and SimplePush

Remove support for MPSN and SimplePush from the server. Tests that still relied on one of those variants were modified to use different ones.

Has been merged to master: https://github.com/aerogear/aerogear-unifiedpush-server/commit/d747cd9d3d804fd411f448e95bd8467f42edfb8f
@pb82 I did release the new UI, and was updating its usage here:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/d747cd9d3d804fd411f448e95bd8467f42edfb8f/dependencies/server-dependencies/pom.xml#L166


ActiveMQArtemis CRDs v1.0.0 are not backward compatible with v0.20.1

The redeliveryDelayMultiplier and RedeliveryCollisionAvoidanceFactor fields are *float32 in v2alpha5/v0.20.1 and they are *string in v2alpha5/v1.0.0.

in the absence of a webhook conversion, supporting both types is not an option. further more, the inability to parse the v2alpha5 causes all operator watches to fail, leading to a head of the queue blocking problem, and the operator cannot get notification of further cr changes. Given that there is an alternative way to configure address settings in v1beta1 via broker properties and given that we don't yet have webhook conversion, and even that would have trouble with the type variance, the best option is to ignore these fields going forward.

with this change, it won't be possible to create new cr's with redeliveryDelayMultiplier or redeliveryCollisionAvoidanceFactor AddressSettingsType fields in yaml:
$ kubectl apply  -f ./examples/artemis-basic-address-settings-deployment.yaml
error: error validating "./examples/artemis-basic-address-settings-deployment.yaml": error validating data: ValidationError(ActiveMQArtemis.spec.addressSettings.addressSetting[1]): unknown field "redeliveryDelayMultiplier" in io.amq.broker.v1beta1.ActiveMQArtemis.spec.addressSettings.addressSetting; if you choose to ignore these errors, turn validation off with --validate=false

If necessary, they will have to be in
Spec.BrokerProperties:
 - "addressesSettings.#.redeliveryDelayMultiplier=2.1"
 - "addressesSettings.#.redeliveryCollisionAvoidanceFactor=1.2"


include CSS reference in index.html

Not an issue with the code, but the README omits any mention of including the CSS references in index.html. I spent a couple hours trying to figure out why, after including the 'rzModule' dependency in my app module and the rzslider.js script file reference in index.html per the Project Integration instructions, the sliders were not actually showing up in browser. Turns out all it was was the missing link to the CSS file. Excellent work, though, thanks!

Indeed, thanks for reporting.


FunctionalTests not running on command line build or CI

The functional test project https://github.com/microsoft/reverse-proxy/blob/main/test/ReverseProxy.FunctionalTests/Yarp.ReverseProxy.FunctionalTests.csproj isn't running when testing from the command line or CI. It's built but not executed.
I noticed because Yarp.ReverseProxy.HttpProxyCookieTests_Http2.ProxyAsync_RequestWithCookieHeaders started failing in VS after a recent SDK update. We need to react to a aspnetcore bugfix.

The functional test project https://github.com/microsoft/reverse-proxy/blob/main/test/ReverseProxy.FunctionalTests/Yarp.ReverseProxy.FunctionalTests.csproj isn't running when testing from the command line or CI. It's built but not executed.

dotnet test in test/ReverseProxy.FunctionalTests seems to run them just fine for me. Are you using a different workflow?

Oh, I see. build.[cmd|sh] -test doesn't discover them.

lol
https://github.com/dotnet/arcade/blob/e7ede87875f41a9b3df898ae08da5ebc96e24f56/src/Microsoft.DotNet.Arcade.Sdk/tools/Tests.props#L17


Add pkr.is-local.org

Requirements

[/] You have completed your website.
[/] The website is reachable.
[/] The CNAME record doesn't contain https:// or /.
[/] There is sufficient information at the owner field.
[/] Your website is not hosting on the following due to SSL issues: Vercel, Netlify

Description

A github repository for polygon native token project.
Link to Website

https://pkr-polygon.github.io/PKR

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

What are your reasons  for using a wildcard?


Error when using user field of tracking_codes

When using the the command
box users list --fields id, name,status,tracking_codes will return an error of Error reading string. Unexpected token: StartObject. Path 'tracking_codes[0]', line 1, position 693..  Any variation of fields that include the tracking_codes will result with the error.
Using boxcli 1.1.1 on macOS 10.13.2

Hi Eric,
There actually have been some issues with retrieving tracking_codes from the API itself. I currently don't have any users with tracking_codes assigned. Would you mind trying to use a tool like Postman or Curl to see if you can pull a user with a tracking_code directly from the API and what results you get? You can use box tokens get to return a token to use with either of those tools.

Just as a word of warning, please don't post the actual user details to this issue. I just want to confirm that you are able to retrieve tracking codes from the API. I'll take a look at the .Net SDK if you can successfully pull that info. You can use something like the following:
curl https://api.box.com/2.0/users?fields=id,tracking_codes -H "Authorization: Bearer $token"

The API is returning the tracking codes for me.  With the command curl "https://api.box.com/2.0/users/me?fields=id,tracking_codes" -H 'Authorization: Bearer ***** Hidden credentials *****' I get a response like
{   "type": "user",   "id": "****",   "tracking_codes": [     {       "type": "tracking_code",       "name": "ERP-ID",       "value": "******"     }   ] }

Perfect! The issue then is with the underlying .Net SDK not having a correct model for tracking codes. I think right now it's just a string[], so I think the JSON converter can't handle the more complex type getting returned. I'll work with that team and keep you updated. Thanks for the confirmation!

I opened a pull request to the .Net SDK that you can watch. As soon as it's pulled in and a new SDK version is added to Nuget, I can update the CLI package.

This issue should be fixed with this current release v1.2.0 @ericallen


[FLINK-3719][web frontend] Moving the barrier between graph and stats

Added a moving split barrier between graph and stats.
It looks like this:

Bottom part becomes scrollable if a user makes it too small, the top part is never scrollable.

[x] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[x] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

This is a useful extension.
I have pinged someone with more web UI experience to take a look at how it is implemented.
Concerning licenses: Where are the png images for the sliders from? Were they self-created?
In the case of other binary files, we usually left a text file in the directory stating the origin and license of the files.

Hi @StephanEwen
All images are coming from this repo: https://github.com/nathancahill/Split.js
It has a very permissive license: https://github.com/nathancahill/Split.js/blob/master/LICENSE.txt

The license is MIT, so that is fine.
Can you update the LICENSE file with the dependency?

Piotr (who wrote most of the web ui) also wants to leave some comments. Let's wait for him.

@mushketyk thanks for this feature, very useful indeed.
I'd like to ask you to reconsider some things:

First of all, I think it would be good to wrap split.js in an Angular directive
I think the style attribute could be replaced by CSS
I think there is a typo in the port numer (80801)

Let me know your thoughts.
Thanks,
Piotr

Hi @iampeter
Thank you for your review.
I'll update the code according to your suggestions.
Best regards,
Ivan.

Hi @iampeter @StephanEwen
I've fixed the PR according to your review. I've added new license, introduced a new directive, and updated CSS.
Could you please review it once again?

Thanks, that's better @mushketyk, but I think would be even better if you did not identify the elements explicitly by ids ('#canvas', '#job-panel'), but have the directive contain the two splitable parts, i.e.:
<split>

Upper part

Lower part

</split>

and just use the first and second child to identify them. This way the directive would be reusable and also could be used in other parts of the dashboard.

Hi @iampeter,
Sorry for the delay in response. I'll take a look at this on Sunday.

Hi @iampeter
I've updated the PR according to your comments. Could you please review it again?
Best regards,
Ivan.

Hi @iampeter
I've updated the PR according to your review.

@iampeter Is there anything else that I should change?

@mushketyk do make sure that the generated files are up-to-date (if they're not)

Merging this ...


How does "use_local_timezone" work? Seems that it's not using the local timezone

How should use_local_timezone work in cron method?
scheduler.cron(
    cron_string,                # A cron string (e.g. "0 0 * * 0")
    func=func,                  # Function to be queued
    args=[arg1, arg2],          # Arguments passed into function when executed
    kwargs={'foo': 'bar'},      # Keyword arguments passed into function when executed
    repeat=10,                  # Repeat this number of times (None means repeat forever)
    queue_name=queue_name,      # In which queue the job should be put in
    meta={'foo': 'bar'},        # Arbitrary pickleable data on the job itself
    use_local_timezone=False    # Interpret hours in the local timezone
)

From what I understand the docs it should use the server timezone (TZ env variable) to interpret the scheduled task. But when I look into the code it seems that it is using UTC even if the setting is set to True. Relevant code:
https://github.com/rq/rq-scheduler/blob/c79288c1046e5e4e79a46cba2bb6dc035250ff84/rq_scheduler/utils.py#L26
I read the above code as: Use get_utc_timezone if use_local_timezone else  use datetime.utcnow() <- look like UTC in both situations.
Am I correct?
My case:
I have a task that I want to fire daily at midnight (00:00) California time. Unfortunatelly California has 2 timezones that change (PDT and PST). My workaround was to schedule the task at 8am UTC time which will be 01:00am PDT and 00:00 PST. But maybe there is a better way to solve it with rq-scheduler

[edit] miss click

@Eugeny maybe you could help out here?

 I'm passing a TZ-aware date to croniter when local time is enabled, so get_next_scheduled_time() will either return TZ-aware date or "UTC-assumed" objects, but the TZ info is simply ignored by to_unix afterwards
Fixed in the PR: https://github.com/rq/rq-scheduler/pull/248

Will this make it to a release in a reasonably near future?

Will this make it to a release in a reasonably near future?

I'm not sure I understand how this is supposed to work. With the (supposedly fixed) rel 0.11.0, I have the following cron line:
"0 5 * * *"

with use_local_timezone=True.
I'm in CEST timezone (currently UTC+2), and I see the job is running every day at 7 am my time. Shouldn't it be running at 5 am my time instead?


docs: update tool-calling how-to

There are two ways to do this in LangGraph:
implement a custom tool-calling node
use LangGraph's prebuilt ToolNode

This would benefit from a very slight paraphrasing to emphasize that:

custom tool calling node is possible if you need flexibility / customization
2.The pre-built tool node is good and has a bunch of optimizations

This information appears as part of the admonition, but phrased in "negative" language (YOU DO NOT NEED), instead can present this as part of the bullet points and use positive language (you have the option to implement a custom thing)

If you have cycles:
import json
from langgraph.graph import MessagesState

def call_tools(state: MessagesState):
    tools_by_name = {tool.name: tool for tool in tools}
    messages = state["messages"]
    last_message = messages[-1]
    output_messages = []
    for tool_call in last_message.tool_calls:
        # call the tools
        tool_result = tools_by_name[tool_call["name"]].invoke(tool_call["args"])
        output_messages.append(
            # wrap the tool call results in a ToolMessage.
            # model providers like OpenAI and Anthropic expect any AIMessages with
            # tool calls to be followed by ToolMessages with the tool call results.
            ToolMessage(
                content=json.dumps(tool_result),
                name=tool_call["name"],
                tool_call_id=tool_call["id"],
            )
        )
    return {"messages": output_messages}```

I'd recommend pushing code blocks like that through an llm to add brief documentation between most lines -- we have wide readership:

These snippets can be less obvious for folks unfamiliar with what's going on:

tools_by_name = {tool.name: tool for tool in tools}
messages = state["messages"]
last_message = messages[-1] # Why last message?

for tool_call in last_message.tool_calls: # Why multiple?

Why so many `[` / `.invoke`

  tool_result = tools_by_name[tool_call["name"]].invoke(tool_call["args"])


Update: Removed log4j properties from quick start application

Summary

Removing log4j properties from quick start application for now.

Test plan
All fsc and unit tests should pass.

Pull Request Test Coverage Report for Build 1913

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.733%

Totals

Change from base Build 1910:
0.0%

Covered Lines:
4866

Relevant Lines:
5363

💛  - Coveralls


Broke my app on production

Any ideas how I may debug this one?
Only receiving the following error after building for production,
but not locally on debug mode.

Hey @ChenMorSays,
I think it would be better if you'd reproduce it in codesandbox.io, I think it will be hard to understand the issue without seeing the code.

How would you recommend reproducing it in production mode, on codesandbox.io?

Let's start by having the problematic code, there are some ways to make codesandbox to compile code :)

I have the very same problem. By invoking: yarn encore production my application won't start as soon as I add the line import { Chart } from 'react-charts'; anywhere in my application. No other code is needed to replicate the problem.
yarn encore dev works, though.

@EladBezalel trying to replicate on codesandbox but no success yet.
@githubjonas good news (that I'm not alone here).
Any ideas?

@EladBezalel trying to replicate on codesandbox but no success yet.
@githubjonas good news (that I'm not alone here).
Any ideas?

I'll clone the react-charts code and start debugging. No luck yet. I'll keep you posted. Right now I need to revert to get production working again! :-D

Ok I gave up for now and intermittently went back to react-google-charts, but it would be nice to find some solution for this. Sorry I could not give you any more clues, @ChenMorSays .

@githubjonas that's a bummer.
Did you try a specific version? Perhaps 2.0.7 beta is not a good release

If anyone else comes across this issue, try yarn add<EMAIL_ADDRESS>instead.
Worked for us.

+1 I'm having the same issue

Closing this since there is not a reproduction case. Please reopen your issue with a codesandbox that illustrates the bug.


Create Explanation of HUBCONF.PY Code

This code defines functions for creating linear classifiers using the DINOv2 architecture, which is a type of Vision Transformer (ViT) that has been trained on large-scale image datasets using a method called Data-Instance Normalization (DINO). The linear classifiers can be used for image classification tasks.

I am afraid the proposed additional documentation is neither necessary nor particularly helpful. I will thus close this PR.
Feel free to help improve the inline documentation of the model functions exposed via PyTorch Hub and thanks for your interest!


[Web]: Using tooltip with long press causes issue with web across all browsers.

I changed the longpress to ontap in tooltip.dart and everything is functional. It doesn't seem like the hover approach mentioned in there is working either, let me know if I need to open a separate issue.
  @override
  Widget build(BuildContext context) {
    assert(Overlay.of(context, debugRequiredFor: widget) != null);
    Widget result = GestureDetector(
      behavior: HitTestBehavior.opaque,
      onTap: _handleLongPress,
      excludeFromSemantics: true,
      child: Semantics(
        label: widget.excludeFromSemantics ? null : widget.message,
        child: widget.child,
      ),
    );

@MichealReed What the issue exactly it causes? Is it reproducible using current flutter stable or master?

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


3D custom data format

Hi,
I am trying to run inference on 3D detection data, I have the body coordinates of people. What preprocessing do I need to do for inference? I normalised the data wrt the hip centre. I tried to visualise prepared data and the person was upside down, I am little confused.

Hi @CloudedLeopard17 , thank you for your focus.
Do you mean that you want to inference your own dataset? If so, you can follow the instruction here to make your own dataset. If you only want to inference the prepared data, just follow the instruction here.
For the upside-down human, we didn't deliberately place the human body like that. It is probably because the estimator's output is original upside down, and we simply copy it into our data. DeciWatch is not sensitive to the person's orientation, so if you need to generate your own dataset, you do not need to turn it to specific orientation.

Hi @juxuan27  thanks for the reply, I tried to do inference on my custom data but I am getting empty predicted_pos, denoised_pos outputs in visualize.py. I am passing joints_3d inputs normalized by the hip centre.

@juxuan27 I was able to run inference on my custom data. Thanks for the great work.


Exceptions list only changing font size?

Hey, I had some problems with the post editing page on Tumblr and LiveJournal, and the coding (HTML/CSS) editing page on Neocities when this add-on was installed (on Tumblr the very top of your post disappears and on LJ the buttons in the "smart text editor" entirely seem to have disappeared and turned into the default background colour of the add-on. On Neocities the text totally disappeared...).
So I wanted to make exceptions, and I tried to follow what I thought was the exception pattern. However when it seems like it should be working, it only resets the font size to the site's original, it doesn't give me back the original site colours/layout.

Exceptions aren't for telling NoSquint what it shouldn't try to zoom; they're more like ways to divide domains into separate 'sites' that can each be zoomed independently.
Does the problem still happen when NoSquint is disabled?

Hey, yeah by now I've noticed that part. It's not really the zooming that's the problem but the background colour. For example, on Facebook, if you click an image that someone has posted and it goes to a sort of full-screen-ish view where you get their comments on the side and then the picture on the other side, due to how the site shows the picture, it gets covered up completely by the background colour from NoSquint and you have to right-click and select "view image"  and view it outside of the page, using the plain image URL. For another example, on Google's search bar it also gets filled in with the background colour that you've chosen, but the text inside the search bar isn't affected by NoSquint, so if your background colour is black then Google's text is dark grey and it's impossible to read. There's just several sites where this sort of thing causes some problems and I know it's not really NoSquint's fault, but it is really annoying since the addon helps so much otherwise.
So in order to stop the accidental image overlay, I have to disable the global settings just for the site I happen to be on at the time, which may or may not require also disabling the site-specific settings on top of that, and then enable them again a short while later when I move away from the site (or the one specific problem page). For example, an entire site may work fine until it comes time to type in a text box. Disabling it doesn't sound like much work, but when you go on the internet a lot and switch between sites a lot...

Does this explain why the NoSquint option is greyed out on Facebook? It works on other sites. I'm running FF 38.0.1 and NoSquint <IP_ADDRESS>.


White background flashes before dark one

Something I noticed and did not confirm or look into further.
Could be that if the stylesheet is loaded synchronously prior to the content, this would possibly be prevented.

In theory, JavaScript is not necessary. Can be purely CSS.
https://css-tricks.com/dark-modes-with-css/
https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme

Then I would load that JavaScript synchronously in the HEAD element. According to what you're describing I would expect that to be the recommendation.

You are right. I just looked at the source code of the bootstrap docs. There you can find the script in the head of the page. See line 17 view-source:https://getbootstrap.com/docs/5.3/customize/color-modes/#sass-usage

fixed in d9bcf84


[R5K7] Pipeline reproduction (SPM - raw)

Replaced by #168 (with all the predefined info from issue template for reproductions)


Change class of robust_lm

robust_lm currently takes the class of lm, but that means broom's tidy and output mechanisms that rely on it like huxreg will just read the normal SEs and forget about the whole thing. We need to change the class to something else like robuse_lm.

Added in https://github.com/Ottawa-EPRI/EPmisc/commit/ef6708362e264e1cd57dd402616b7120c0ba27cc.


Building a proper Dockerfile and natively supporting ARM images

👋 Thanks for building JATOS!
I was looking around for a Dockerfile, only to find it defined in Scala. 😕 (If it were built in a traditional Dockerfile, I could've submitted a PR that adds support for ARMv8.)
https://github.com/JATOS/JATOS/blob/4466ce747ed585f56bfc298b4cb4442622ae8e71/build.sbt
I've never used Scala, but imagine it has templating to support variable changes (to reduce need for manually updating the Dockerfile).
I'm happy to contribute a Dockerfile/whatnot to support this – but wanted to open an issue to check if that's something JATOS is open to. 🙂

I vaguely remember that once I did a release with 'mutli-arch' docker images. Something like described in this blog post: https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/. It's still available on docker hub: docker pull jatos/jatos:multi-arch. It was a one-time thing and I can't really remember how I did it - but if I did it once I can probably do it again (and make it part of every release).

EDIT: Is this 'multi-arch' approach something that suits your needs?

Do you mean this particular multi-arch image? If so, then I don't think so, as it's not up-to-date.
If you're asking "would a multi-arch image suit my needs?" Then yes, that's exactly what I'm looking for.
Some naïve perusing of the build.sbt file I linked above gives me the impression that there's nothing variable in the Dockerfile? If so, I can probably knock this out tonight. (Not my first time doing a multi-arch Docker image.)

The latter one, in general :)
And you are right: there is nothing variable in the Dockerfile. Please knock it out :+1:

Is the build process for JATOS documented somewhere? (I see a reference to ./opt/, which I presume is generated during the build, but I don't actually know where to find and/or how to source that.)
Furthermore, are you open to using GitHub Workflows to build/push these? (I've set these up in the past, but since I don't see a .github/workflows folder, I'm guessing you either manually build or use Jenkins/equivalent.)
(If you don't wanna use GitHub Workflows, should I write-up a [bash] script that allows for building/tagging/pushing?)

So far we only use sbt for the jatos.zip and then I bundle them by hand with Java and upload the zips by hand to GitHub.
For the docker images I use sbt-native-packager and push them to Docker Hub. I always wanted to further automate the build process but never found the time.

Is the build process for JATOS documented somewhere?
Nope. So far it's really just a couple of sbt commands and the build config in the build.sbt. But I can describe it more in detail.

I guess GitHub Actions would be fine. But somehow I think a simple shell script would do the same job (and keep it simple).

Okay. Cool. Do you mind walking me through the build process and/or linking some resources on how to build them? (I've never used Scala before, so I'm not sure what to do here. 😅)

Sorry for the late reply. I tried for the last couple hours to change the build.sbt to automatically build docker in multi-arch ... and failed. But this is just an inconvenience. The docker building works and the multi-arch building can be done in a separate step.
I used the following command to push a multi-arch image to Docker Hub (it's a pre-release - don't use it in production).
docker buildx build --platform=linux/arm64,linux/amd64 --push -t jatos/jatos:test .

My docker multi-arch experience is pretty non-existent. Do you agree with this command? Can you try this image on an arm processor? Do you think we need a special build for armv8, the one you mentioned before?

Do you agree with this command?

Looks correct at first glance.

Can you try this image on an arm processor?

Just did. It works! 🙂

Do you think we need a special build for armv8, the one you mentioned before?

I don't think so. I believe that linux/arm/v8 is just the latest release of the ARM instruction set. But I'm honestly not sure. I mostly know "how to build" multi-platform images, not necessarily "why this version and not that other one". 😅

Nice. So I'll do a multi-arch docker image from now on :tada:
And since we are talking about docker. What do you think about this Dockerfile? I'm using it since a while now. Maybe you see something we can improve?
FROM openjdk:11-jre
MAINTAINER Kristian Lange
WORKDIR /opt/docker
ADD opt /opt
EXPOSE 9000 9443
RUN apt update -y && apt install vim -y
RUN ["mkdir", "-p", "/opt/docker/logs"]
RUN ["chown", "-R", "daemon:daemon", "."]
RUN ["chmod", "u+x", "loader.sh"]
VOLUME /opt/docker/logs
RUN bash -l -c 'echo export JATOS_SECRET=$(LC_ALL=C tr -cd '[:alnum:]' < /dev/urandom | fold -w128 | head -n1) >> /etc/bash.bashrc'
USER daemon
ENTRYPOINT ["./loader.sh", "start"]

👋 sorry for the slow reply! I forgot that I didn't answer you. 😅
So, I'm curious why the ... export JATOS_SECRET=... line exists in the Dockerfile. How is that any different from this line in ./loader.sh?
https://github.com/JATOS/JATOS/blob/b5fe354ed3e891837dc91e7c4cec6ae8a62bf0c4/loader.sh#L33
I don't see any functional reference to JATOS_SECRET throughout JATOS.
I saw this: https://github.com/JATOS/JATOS/blob/9f261beadf5a9ce51da12ef247f016cd7d4e3db7/conf/application.conf#L192-L204
but it's unclear if declaring JATOS_SECRET in the Docker container will override the secret=$(...) statement in ./loader.sh. Furthermore – is it ideal to have all Docker containers specify the same secret? Anyone who pulls, say, the image tagged 3.7.3 will have the same secret (to my knowledge). That seems like a security risk. (This would be because JATOS_SECRET is generated at build-time, rather than runtime. The latter is what I would think the intended behavior is.
Though, of course, I concede most of these points to you, since you're the primary maintainer of this. 😅

So, I'm curious why the ... export JATOS_SECRET=... line exists in the Dockerfile. How is that any different from this line in ./loader.sh?

You are right. It's not needed in the Dockerfile. The one in loader.sh (and loader.bat) do the job. I can't remember why I put it there - maybe I was experimenting with starting JATOS without the loader.sh. Anyway I'll remove it. Thanks for pointing this out.

but it's unclear if declaring JATOS_SECRET in the Docker container will override the secret=$(...) statement in ./loader.sh. Furthermore

JATOS has multi-arch Docker images now, with amd64 and arm64 (https://hub.docker.com/r/jatos/jatos/tags).


Luarocks issue

There is a mistake in luarocks package (luarocks install luasocket), it installs luasocket with outdated http.lua which has TIMEOUT in global scope.
"apt-get install lua-socket" works well.
luarocks show luasocket:

LuaSocket 3.0rc1-2 - Network support for the Lua language
LuaSocket is a Lua extension library that is composed by two parts: a C core
that provides support for the TCP and UDP transport layers, and a set of Lua
modules that add support for functionality commonly needed by applications that
deal with the Internet.
License: 	MIT
Homepage: 	http://luaforge.net/projects/luasocket/
Installed in: 	/usr/local
Modules:
ltn12 (/usr/local/share/lua/5.1/ltn12.lua)
mime (/usr/local/share/lua/5.1/mime.lua)
mime.core (/usr/local/lib/lua/5.1/mime/core.so)
socket (/usr/local/share/lua/5.1/socket.lua)
socket.core (/usr/local/lib/lua/5.1/socket/core.so)
socket.ftp (/usr/local/share/lua/5.1/socket/ftp.lua)
socket.headers (/usr/local/share/lua/5.1/socket/headers.lua)
socket.http (/usr/local/share/lua/5.1/socket/http.lua)
socket.serial (/usr/local/lib/lua/5.1/socket/serial.so)
socket.smtp (/usr/local/share/lua/5.1/socket/smtp.lua)
socket.tp (/usr/local/share/lua/5.1/socket/tp.lua)
socket.unix (/usr/local/lib/lua/5.1/socket/unix.so)
socket.url (/usr/local/share/lua/5.1/socket/url.lua)

Confirmed.  The package being served by the LuaRocks server is quite old (and confusing, as they label it v3.0-rc2 but ship a file called v3.0-rc1.zip).
We'll get it sorted out with this upcoming release if not sooner.  I've registered with LuaRocks to streamling pushing a package to them when one is ready.
Also leaving this issue open for now for LuaRocks-specific release updates.


output: don't move hidden cursors

When using the DRM backend and multiple outputs, that reduces the
number of commits.
Test plan: check that cursors aren't broken on a multi-monitor setup

On startup rootston sets the cursor on the top left corner of the output.
With this, that only changes once the pointer enters the relevant output, which makes this behaviour look rather weird.
It should probably set up the cursor in the virtual layout properly at startup.
It also updates all outputs when a client cursor is set.
Can we just upload the new texture without updating the output?

Fixed the trailing cursor bug on startup.

It also updates all outputs when a client cursor is set.
Can we just upload the new texture without updating the output?

I'll try to fix this in an upcoming PR taking care of #581, because this needs to change how the cursor position is cached in the DRM backend.

Oops, missed that @acrisci was assigned. Let me know if you want to revert. Sorry about that.


feat(rootGroup): make the rootGroup for crds configurable via prepare.sh

Description of your changes

Fixes #17
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

generated one provider out of it https://github.com/haarchri/provider-testhub


style(api-reference): search modal deprecated endpoint

Before:

After:

awesome work @Edgaraszs !!!

Love to contribute to this repo


Support file: for [metadata]version declarative config

[metadata]version currently supports attr: and literal strings, but it would be super handy to support file: so that I can have a mypkg/version.txt file containing my version number.

A bit more context. Obviously, one could put the version in mypkg/version.py and include it via attr: mypkg.version, except if there's something in mypkg.__init__ that's going to fail to import before the package's dependencies have been loaded.
@idlesign Any reason you can think the declarative config shouldn't support a file: for version number?

In addition to the proposed solution, I can imagine another solution -- what if attr: mypkg.version loaded the version statically, without importing the module, but only be loading it and parsing out the value from the module directly, similar to how rwt loads package names without executing the script? Such an approach would only work if the attribute was always a literal string (and not a calculation like __version__ = '.'.join(map(str, (1, 2, 0))); trust me it happens).

I suspect this issue would be a fairly accessible one, as it extends existing functionality to other existing fields.

Not that it's entirely useful, but in the past I've used my setuptools_helpers script, which just reads a file and applies a regexp to dig out the version number.

Hi,

In addition to the proposed solution, I can imagine another solution -- what if attr: mypkg.version loaded the version statically [...]

On initial implementation I was thinking about a fallback for ImporError which ought to use pure parsing (something similar to https://github.com/idlesign/makeapp/blob/v0.12.1/makeapp/app_templates/default/setup.py#L19), but I resisted the temptation due to this parsing approach is too error prone for something that generic as setuptools (especially since we have a bunch of widely used approaches as where, how and what format to use to store version number).

Any reason you can think the declarative config shouldn't support a file: for version number?

No, I think Barry's proposal it quite reasonable. Text files with just a single version line are quite common and can be easily generated by build tools. The only thing might be that in such a case the most reasonable way to get get version number will be using package data extraction facilities (which imposes some limitations).

EIBTI!

#1359 has been merged, so I think it should be ok to close this.


[PowerToys Run] Which files/directories are indexed?

I think it would be really helpful to have some more info on what directories & files are actually indexed for the search.
I.e. I have a folder D:/PortableApps in which there are many subdirectories & executables which I'd like to be able to access via the launcher. ATM the launcher does not show those exes and I'm not quite sure whether this is by design or a bug...
FYI: I'm a long term (happy) Launchy user and I'm currently considering switching to PowerToys run mostly out of curiosity & because the PowerToys project in general feels like there's a lot more "niceness" to come in the future ;)

@CombeeMike is your D: drive indexed? You can see what is currently being indexed by searching for "Indexing Options" in Control Panel. We have #2041 in progress to fix it and this is related to #3230.

As a user, I think that all indexed drives/folders should be available to Run, but I should be able to add some other locations for Run that are not indexed. (I'm a longtime Launchy user as well.)

@asherber We are tracking the suggestion in #3311
Closing this issue. Please feel free to reopen if you have any other issues related to this.


Make constant names more obvious

While explaining the CLI parsing to fellow teammates I found the names of these constants were confusing.

Dup of #476


[BAT]update drone yml to remove listen on drone branch

Coverage remained the same at 57.138% when pulling fa166a15e676de9138481867a2b510c3b0dc1d58 on wy65701436:drone-test into 031350645e8ed294731598cb21a45b38d0c7606a on vmware:drone.


docs(popup): increased js readability

While reading the docs, I noticed that the example code was hard to read due to lack of spacing.

This spacing was also inconsistent with other examples, which are more readable; for example, from popover:

Also, added a missing semicolon to line 46.

Thanks! Will fix the jshint error


Improve ImGui shaders reflection in GLSL

imGui shaders in glsl produce wroing stride of 32 because the color is supplies as U32 but we have vec4 on the glsl side and it returns a format R32G32B32A32_UNORM instead of R8G8B8A8_UNORM.

Workaround : currently we check for the shader name and this is hardcoded(stride and format). A general solution must be designed for this


aspnet project not responding in VS 2015

There is a serious performance problem with asp.net mvc 6 project running inside VS 2015.
To reproduce, keep the aspnet mvc 6 project open in the VS 2015. Then run a javascript package manager in the command line in the project folder. For example, I ran jspm install react. Then switch back to the VS 2015 from the command line, and you will see NOT RESPONDING message in the title of the VS 2015. It took at least 30 minutes or so for the VS 2015 to release the UI.
I assume VS 2015 was adding all the files from the jspm_packages folder to the project. This operation is required to add the files to the project. But I don't know why it should that long. I also experience VS 2015 not responding when browsing files in the solution folder.
My configuration:

Resharper is active

Moved to https://github.com/aspnet/Tooling/issues/152


Reset fixed guard conditions

Should fix #125.
CI jobs (connext-only) are in the queue.

http://ci.ros2.org/job/ci_linux/944/
http://ci.ros2.org/job/ci_osx/790/
http://ci.ros2.org/job/ci_windows/1035/

CI on Linux and OSX are green. Windows has 6 fewer tests than last time (I can't promise that this change had that effect, but it's possible).

lgtm


[RFC] Add the "subscribeImmediately" parameter to the ObservableAsPropertyHelper class

When this parameter is set to true, the ObservableAsPropertyHelper
immediately subscribes to the source sequence.

I know it's a big, scary breaking change and all, but my inclination would be to default subscribeImmediately to true (or - even better - rename the parameter to delaySubscription or deferSubscription and default it to false). That way, people aren't trolled by the default, and if/when they discover performance issues with OAPH they can dig deeper and move away from the default behavior. The pit of success with OAPH is way too narrow atm. This PR will allow people to widen the pit, but I'd rather just have the pit wider by default.

I would agree with that. deferSubscription would be my choice, since "delay" indicates you're waiting on some sort of timespan to pass.

The reason I think that delaying the subscription by default is good, is because I think that the constructor of an object shouldn't fire off any work on other threads.
Take the following class for example:
public class MyViewModel : ReactiveObject
{
    private readonly ObservableAsPropertyHelper<int> myProperty;

    public MyViewModel()
    {
        this.myProperty = CalculateAsync().ToProperty(this, x => x.MyProperty);
    }

    public int MyProperty => this.myProperty.Value;

    public IObservable<int> CalculateAsync()
    {
        // Calculate something expensive here
    }
}

If myProperty would subscribe to the source immediately, the construction of MyViewModel now fire of some potentially expensive work on another thread, while the current behavior would subscribe when accessing MyProperty the first time

Isn't this a case of catering the esoteric scenario at the expense of the common?
I don't think it's a stretch to say that most OAPH usage will simply be massaging existing properties into new ones. And to have those scenarios constantly require that people remember to specify deferSubscription = false seems backwards to me. After all, the people who are kicking off expensive work in a ctor are likely to notice and immediately remember that they should defer that particular subscription (or, if it's the first time they've come up against the problem, look into OAPH a bit and find the solution).

Yeah, you're probably right that my use case isn't very common.
Maybe @paulcbetts also has some input on this?

cc @niik for feels on this change

Doesn't seem to be any further feedback on this and I would :heart: for this to get into the 7 branch ASAP so people can start banging on it.
@flagbug could you please change the argument name to deferSubscription and default it to false?

@kentcb Sure! I'll open a new PR for that change, because I deleted my fork where this PR is based :see_no_evil:

Just did a quick scan of GitHub Desktop's code - we have 66 .ToProperty() methods, and only 10 of those set scheduler: Scheduler.Immediate to address this issue. I can look into why we've done that where we have, but I still favour lazy for our scenarios - even when in tests.
Not sure how flipping the default behaviour here from lazy to eager will impact us, but I suspect it will. I don't want to hold this up this PR from being merged (I like this being exposed directly, and it's more clearer than using Scheduler.Immediate), but I'm curious about whether this is the right defaults (because I'm a fan of being lazy in general when programming).

Isn't scheduling a different issue entirely? The purpose of the deferSubscription parameter is to facilitate a lazy subscription, whereas scheduling just dictates where the target property will be scheduled to update. Scheduling is of no consequence if the property is lazy and nothing ever connects to it.

@shiftkey also, allow me to flip the question around a little: what negative consequences could there be from making the default behavior a hot observable? To me, this aligns the feature far more with people's expectations. We've seen that time and again through support questions and (certainly for me anyway) our own experiences using OAPH.
The only possible argument I see against making it hot is performance, and I would consider that a poor argument because:

If you really want lazy, you can still get it simply by passing deferSubscription: true
Why are people defining these properties if nothing is actually observing it? Surely that's the exception rather than the norm.
Performance at the expense of usability is a poor trade-off, imo, especially when that performance can be reinstated per (1)

@kentcb I shall check the history on these changes to understand why we've done the Scheduler.Immediate thing. I believe this is the same issue, but perhaps viewed from two different perspectives...

@kentcb

To me, this aligns the feature far more with people's expectations. We've seen that time and again through support questions and (certainly for me anyway) our own experiences using OAPH.

I'm probably missing some anecdotes on this, as aside from this Scheduler.Immediate thing our usage of OAPH has been largely conventional. Do you have a good example of newbies running into this so I can get some extra context?

If you really want lazy, you can still get it simply by passing deferSubscription: true

This is true - and I'm not afraid of writing our own extension methods over this to ensure we do it by default.

Why are people defining these properties if nothing is actually observing it? Surely that's the exception rather than the norm.

Perhaps this is the issue at hand. Something definitely necessitated us doing this, which made us feel bad at the time. I'll let you know what I find out.

Performance at the expense of usability is a poor trade-off, imo, especially when that performance can be reinstated per (1)

For most of the usages as I see it we're not talking about expensive operations. So it's gotta be something else.

One common example that just came to my mind is the Android RecyclerView. RecyclerView list items are virtualized, so only items that come into the view are actually used. This means that with deferred OAPH subscription, most of the ViewModel properties are never subscribed to, because the ViewModel never actually comes into view.
With the new behavior of immediate subscription, all the properties are loaded at once, as soon as the ViewModels for the RecyclerView are created, which can potentially bog down performance with a lot of items (e.g if the ViewModels also load images)

@flagbug: interesting. My approach to such a scenario would be to only load the image if the VM is activated.
Here are some other examples:

testing. Often I've run into issues testing because an assertion is being made against a property that is using OAPH. Of course, if nothing is subscribed to it then the test will fail, but it's not always simple to track down
non-binding scenarios. For example, a VM exposes a property A that the view binds to. It derives a property B from A using OAPH (to do some further munging of the value). It wants to pass the value of B into the service layer whenever a command executes. But nothing is subscribed to B, so the value is unset.
non-RxUI binding scenarios. For example, your VM uses OAPH and your iOS version uses RxUI binding. All is well. Then you do a WPF port (or whatever) and for perf reasons you have to use native bindings for a particular view. Things don't work because there are no subscriptions.

I've created the new PR at https://github.com/reactiveui/ReactiveUI/pull/1061
@kentcb Don't get me wrong, I don't like the current behavior, especially the switch where in unit tests, OAPH immediately subscribes to the source, which makes unit tests behave different than production code.
I just wanted to show a case where the current behavior is beneficial, if you have a VM with 10 properties times a list with 100 items, that's at least 1000 calls to Subscribe, which is suuuuuuuuper slow, especially on Android. So I guess what I want to say is that we have to make sure that people are aware of this and aren't blaming RxUI on the slowness, since they now can use the deferSubscription parameter

Closing in favor of https://github.com/reactiveui/ReactiveUI/pull/1061


[0.8.14] Conditional Array Properties are Not Validated Correctly

This appears to be a new bug introduced in version 0.8.14.
Basically, if you have an array property in your schema, and that property is conditional, the form is not being validated correctly.
Here is a reduced example showing it working with version 0.8.13.
Here is the exact same example NOT working with version 0.8.14.
In both examples, if you check the "Show Array Elements" checkbox, the array section appears. If you provide at least a value for Field 1 and submit, the form validates for 0.8.13, but not for 0.8.14.
In 0.8.14, the form has the following $error:
"$error": {
  "schemaForm": [
    {
      "$viewValue": [
        {
          "Field1": "My Test Value for Field1"
        }
      ],
      "$modelValue": [
        {
          "Field1": "My Test Value for Field1"
        }
      ],
      "$validators": {},
      "$asyncValidators": {},
      "$parsers": [
        null
      ],
      "$formatters": [
        null
      ],
      "$viewChangeListeners": [],
      "$untouched": true,
      "$touched": false,
      "$pristine": false,
      "$dirty": true,
      "$valid": false,
      "$invalid": true,
      "$error": {
        "schemaForm": true
      },
      "$name": "",
      "$options": {}
    }
  ]
}

@json-schema-form/angular-schema-form-lead

@rthaut wow, that's an interesting case. No doubt plenty of users have it. Thanks for the demos, it does seem related to the condition as removing the condition it works in both, I suspect it was related to some fo the array changes that went into the branch mid last year.

@Anthropic Using the Bootstrap Decorator from 0.8.13 with ASF 0.8.14 does indeed work correctly, at least for this scenario. Here's a demo: https://codepen.io/rthaut/full/qMWpaV/


ReactWebViewManager error after upgrading to 0.60.5

After upgrading from react-native 0.59.10 to 0.60.5 we are getting this error when building Android:
/workspace/mobile-custom-webview/mobile-custom-webview/android/src/main/java/invisionapp/customwebview/CustomWebViewManager.java:27: error: package com.facebook.react.
views.webview does not exist
import com.facebook.react.views.webview.ReactWebViewManager;
                                       ^
/workspace/mobile-custom-webview/mobile-custom-webview/android/src/main/java/invisionapp/customwebview/CustomWebViewManager.java:36: error: cannot find symbol
public class CustomWebViewManager extends ReactWebViewManager {

The custom webview is created according to the documentation: https://facebook.github.io/react-native/docs/custom-webview-android
Excerpt from CustomeWebViewManager.java:
...
import com.facebook.react.views.webview.ReactWebViewManager;
import javax.annotation.Nullable;

import java.util.Map;

@ReactModule(name = CustomWebViewManager.REACT_CLASS)
public class CustomWebViewManager extends ReactWebViewManager {
...

React Native version:
  info Fetching system and libraries information...
System:
    OS: macOS 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 37.35 MB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 8.16.1 - ~/.nvm/versions/node/v8.16.1/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v8.16.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
    Android SDK:
      API Levels: 23, 24, 25, 26, 27, 28
      Build Tools: 23.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.0, 28.0.0, 28.0.1, 28.0.2, 28.0.3
      System Images: android-25 | Google APIs Intel x86 Atom, android-25 | Google Play Intel x86 Atom, android-26 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.4 AI-183.6<IP_ADDRESS>92245
    Xcode: 10.1/10B61 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: 0.60.5 => 0.60.5

In package.json we have:
 "dependencies": {
    "react": "16.8.6",
    "react-native": "0.60.5",
    "react-native-webview": "6.8.0"
  },

Steps To Reproduce

Create an Android CustomWebView following the documentation: https://facebook.github.io/react-native/docs/custom-webview-android
try to build Android by doing react-native run-android

Describe what you expected to happen:
Android app should build and run just like before (0.59.10)
0.60 react-native doc page:

Update: I tried to replace:
import com.facebook.react.views.webview.ReactWebViewManager;

to
import com.reactnativecommunity.webview;

I'm getting the same error:
/workspace/mobile-custom-webview/mobile-custom-webview/android/src/main/java/invisionapp/customwebview/CustomWebViewManager.java:27: error: package com.reactnativecomm
unity does not exist
import com.reactnativecommunity.webview;
                                       ^
/workspace/mobile-custom-webview/mobile-custom-webview/android/src/main/java/invisionapp/customwebview/CustomWebViewManager.java:36: error: cannot find symbol
public class CustomWebViewManager extends RNCWebViewManager {
                                          ^
  symbol: class RNCWebViewManager
/workspace/mobile-custom-webview/mobile-custom-webview/android/src/main/java/invisionapp/customwebview/CustomWebViewManager.java:71: error: cannot find symbol
    protected ReactWebView createReactWebViewInstance(ThemedReactContext reactContext) {

We were able to fix this issue. Here are a few pointers:

read the Autolinking doc carefully!
if it is a stand-alone module (like it is the case for us) then you
need to inlude react-native-webview in:
the build.gradle of the module

implementation project(":react-native-webview")

and in the settings.gradle of the consuming app
include ':react-native-webview'
project(':react-native-webview').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-webview/android')

even if in the consuming app, it is supposed to be autolinked.
also, you need to add a file called react-native.config.jsin the
consuming app:
const path = require('path');

  module.exports = {
   dependencies: {
     'mobile-custom-webview': {
       root: path.resolve('../mobile-custom-webview'),
     },
   },
 };

in the Java file that defines the CustomWebView:
replace:
import com.reactnativecommunity.webview.RNCWebViewPackage;

with
import com.reactnativecommunity.webview.RNCWebViewManager;

and then finally, a few methods have different signatures, for example: ReactWebView --> RNCWebView


[BUG] Removing a dataset in onClick causes an error if the mouse is moved right after clicking

The problem happens because the lastActive array which is set here contains the active element which is removed in the onClick, so in the following mousemove event happening after the mouseup event fails because this line contains the removed element, and the call to updateHoverStyle() fails because the dataset is not present anymore.
Expected Behavior
It should be possible to remove a dataset within onClick() and move the mouse just after without any error.
Possible Solution
Update lastActive in the top of handleEvent so that it only includes elements which are still present on the chart.
This hack is a temporary workaround:
                   onHover: function(event, elements) {
                        if (self.chart.data.datasets.length === 0) {
                            this.active.length = 0;
                            this.lastActive.length = 0;
                        }
                    }

@rmja can you post a fiddle that reproduces this?

I'm experiencing this as well. Here's a demo. To reproduce it, open your JavaScript console (not the one that comes with Codepen), then click on one of the bars. You'll see the second dataset disappear. If you then move your mouse, you'll see your console flooded with errors.


Implement C Declarations7 package

Description
Decl7 package
Change request type

[ ] Release or process automation (GitHub workflows, internal scripts)
[ ] Internal documentation
[ ] External documentation
[x] Query files (.ql, .qll, .qls or unit tests)
[ ] External scripts (analysis report or other code shipped as part of a release)

Rules with added or modified queries

[ ] No rules added
[x] Queries have been added for the following rules:

RULE-8-12
RULE-18-8
DCL36-C (wont implement decision - pls verify if agreed - notes on justification below

[ ] Queries have been modified for the following rules:

rule number here

Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:

The structure or layout of the release artifacts.
The evaluation performance (memory, execution time) of an existing query.
The results of an existing query in any circumstance.

If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?

[ ] Yes
[x] No

🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.

[ ] Confirmed

Reviewer: Confirm that either a change note is not required or the change note is required and has been added.

[ ] Confirmed

Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author

[ ] Have all the relevant rule package description files been checked in?
[ ] Have you verified that the metadata properties of each new query is set appropriately?
[ ] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[ ] Are the alert messages properly formatted and consistent with the style guide?
[ ] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[ ] Does the query have an appropriate level of in-query comments/documentation?
[ ] Have you considered/identified possible edge cases?
[ ] Does the query not reinvent features in the standard library?
[ ] Can the query be simplified further (not golfed!)

Reviewer

[ ] Have all the relevant rule package description files been checked in?
[ ] Have you verified that the metadata properties of each new query is set appropriately?
[ ] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[ ] Are the alert messages properly formatted and consistent with the style guide?
[ ] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[ ] Does the query have an appropriate level of in-query comments/documentation?
[ ] Have you considered/identified possible edge cases?
[ ] Does the query not reinvent features in the standard library?
[ ] Can the query be simplified further (not golfed!)

Notes omit DCL36-C
compiler checked by clang (and according to wiki, gcc) but not MVSC
verified with:
testcase non compliant example from the wiki
as well as this testcase built upon the table depicted in the wiki (except if the "no linkage" header actually said "no specifier" which I think is what is it is meant to say - to be confirmed)
////TABLE - specifiers

static int i1; //internal linkage
static int i1; //COMPLIANT - internal linkage

int i2; //no linkage
static int i2; //NON_COMPLIANT - undefined - compiler detected

extern int i3; //external linkage
static int i3; ///NON_COMPLIANT - undefined - compiler detected

//-----
static int i11; //internal linkage
int i11; //NON_COMPLIANT - undefined - compiler detected

int i22; //no specifier
int i22; //COMPLIANT - no specifier

extern int i33; //external linkage
int i33; //NON_COMPLIANT - undefined according to table - but not compiler detected - so... COMPLIANT?

//-----
static int i111; //internal linkage
extern int i111; //COMPLIANT - internal linkage

int i222; //no specifier
extern int i222; //COMPLIANT - external linkage

extern int i333; //external linkage
extern int i333; //COMPLIANT - external linkage


(Azure CXP Team) resolves MicrosoftDocs/azure-docs#92902

@Karishma-Tiwari-MSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@alkohli  - Can you review the proposed changes?
IMPORTANT: 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.
Thanks!
#label:"aq-pr-triaged"

#sign-off Looks good.


Greenlight: close channel

we need to be able to close channels to redeem onchain funds
This needs to be implemented in glalby first, and then we can consume them in nwc through glalby-go

PRs are up:

glalby: https://github.com/getAlby/glalby/pull/10
glalby-go: https://github.com/getAlby/glalby-go/pull/6
nostr-wallet-connect-next: https://github.com/getAlby/nostr-wallet-connect-next/pull/138


Market creation mobile - styling issues

Fix header
Build

Design

Reduce font size of radio buttons to 14px:

closing this, market creation redesign has changed and has new responsive designs


Failed to load image

version - v1.0.17 27715147a0b49abebf2f5a3826aff413636c3b4a
When attempting to img2img or inpaint getting this errors

payload: {'init_image_name': 'img_31_46791.png'}
exception:fail to read an image file ./init_images/img_31_46791.png, will try again 0 of 3
exception:fail to read an image file ./init_images/img_31_46791.png, will try again 1 of 3
exception:fail to read an image file ./init_images/img_31_46791.png, will try again 2 of 3
←[32mINFO←[0m:     <IP_ADDRESS>:52058 - "←[1mPOST /getInitImage/ HTTP/1.1←[0m" ←[32m200 OK←[0m

dupe of #6

Hi @NeuroNormal, what photoshop version do you have?  you can check that in UXP while photoshop is running.
also did you follow the steps here: https://github.com/AbdullahAlfaraj/Auto-Photoshop-StableDiffusion-Plugin/issues/6#issuecomment-1364951594

hi @NeuroNormal, the last update should have fixed this problem.
#42

yep, fixed, thanks!


Category lists outdated

I think we should remove the folder, it hasn't been updated in 4 years and we have a JSON dump here: https://www.yelp.com/developers/documentation/v2/all_category_list
@mittonk thoughts?

Yep, my plan is to remove this directory and supply a direct link to the JSON dump on that page.  (That download URL is still in some flux).
(I also half-remember this being a code dependency for something, tracking that down.)

Dup of #14 .


Credit Card Payment creates one 'Invalid' payment and one 'Completed' payment.

When a customer checks out using a credit card and confirms their order, two payments seem to be created in Spree; one 'Invalid' and one 'Completed'.

I must add, this happens when entering a New credit card and using an Existing card.

This is apparently a spree issue, not a spree_komoju issue: https://github.com/spree/spree/issues/6499
I'm guessing upgrading to 3.1.0.beta should fix it.


Install Composer Dependencies fails with Rsync error when running deployment

Before submitting your issue, please make sure that you've checked all of the checkboxes below.

[x] You're running the latest release version of Deployer.
[x] Ensure that you're running at least PHP 5.5.9, you can check this by running php -v
[x] You've ran composer install --no-dev from the root of your installation.
[x] You've ran npm install --production from the root of your installation.
[x] You've ran rm -rf bootstrap/cache/* from the root of your installation.
[x] You have restarted the queue listener and node socket server.

To help us better understand your issue, please answer the following.
Expected behaviour
Deployment should run, set up directories as expected, then move on to installing composer dependencies.
Actual behaviour
Deployment is failing at Install Composer Dependencies.
Errors in the "view the output" logs are:
rsync: change_dir#3 "/home/innocentorders/container/application/releases/20160820142357" failed: No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(712) [Receiver=3.1.0]
[<IP_ADDRESS>]: rsync: change_dir#3 "/home/innocentorders/container/application/releases/20160820142357" failed: No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(712) [Receiver=3.1.0]

Connection to the server appears correct (Clicking Test the server connection from the servers tab)
On the server, the application directory looks like:
drwxr-x--- 3 innocentorders innocentorders    4096 Aug 20 14:28 ./
drwxr-xr-x 6 root           root              4096 Jul 20 10:15 ../
-rw-r--r-- 1 innocentorders innocentorders 1481332 Aug 20 14:26 3_20160820142638.tar.gz
drwxr-x--- 2 innocentorders innocentorders    4096 Jul 20 10:15 public/

Looks like the releases directory is unable to be created, then rsync fails? However I am not sure where to see any errors on the failure in the logs.
Steps to reproduce

Set up project in Deployer
Set up server for project, click test connection button (passes)
Click deploy
Create New Release passes
Install Composer Dependencies fails, with message above.

Environment info
Operating System: Ubuntu 14.04.3 LTS
PHP Version: PHP 7.0.8 (cli)
Node Version: v4.4.4
Database System: mysql
Database Version: 5.6.30
Logs (see storage/logs/) or other output that would be helpful
Attached.
cli-2016-08-20.log.zip

Hmm, this is odd. Did that the entire log for 2016-08-20? The error is for 14:23:57 but the logs seem to be a path for 14:38:38

Ah - I may have copied the wrong log from the UI. On my install there are a number of deploys that all failed with the same error.
I cleaned the server logs before rerunning a deploy to be sure I was sending the right lines from there.

Sorry for the late reply. I see you have a .env file being created, that is where it appears to be failing looking at those logs.
Can you try removing that from the files tab?

Thanks, that has stopped the deployment failing - all steps show up as completed. The actual deployments themselves are not running correctly - but I can now confirm this is likely to do with the environment the app is running in.
From my tests, any script running remote commands over SSH (RunScriptOverSSH.sh etc) is connecting - but no commands from the script are run, and no output is returned. I have been able to reproduce this by running the SSH scripts manually. My hosting provider is using a docker container based setup, so I will follow up with them, and also set up the app on a separate server to retest.

Hmm, that is very odd. Not sure all the scripts running remote commands are failing though, otherwise the create new release step would fail as it transfers an archive to the server, oddly enough using the same script as it used to create the .env file (line 59-70 of your log file but that is successful, line 102-113 is the same command creating the .env file and that fails because the next step is to remove the archive and release directory which is the cleanup that happens on failure).
I will have to try setting up a docker container myself, will have to be on sunday though. Don't suppose you have the dockerfile used to create it?

Quick update for reference. Isolated a test case and send to my hosting provider who confirmed this was an edge case with their containers. They fixed the issue and now the deployments run as expected. I don't have access to the dockerfile - this is abstracted away as part of their platform.
Thanks for your help!


Study Mobile Device Security

https://github.com/lawgimenez/h4cker/tree/master/mobile_security

[ ] Read The OWASP Mobile Application Security Verification Standard (MASVS)
[ ] Read The OWASP Mobile Application Security Testing Guide (MASTG)
[ ] Read The Mobile Application Security Checklist


To call the hook at the time of git merge message.

I want to restrict the GitHub merge message with no leading special character. Is there is any hook we can call at the time of git merge ?

If you are talking about the hub merge <URL> command: this calls git merge internally and you can read git help githooks for information about how to set up a pre-merge-commit hook. A git hook needs to be set up individually for every local clone of the repository.
If you are talking about the Merge button functionality in GitHub.com web interface, then no; there is no hook that can be configured there.


add package based installation for ubuntu 16.04

Add instructions about installing rackhd packages on ubuntu 16.04.
Move the "touch /etc/default/$service" before installing rackhd package.
Remove "start service" after rackhd packages are installed and change the log path to /var/log/rackhd.
Because Rackhd services are already started after installed.
The logs of rackhd services are placed under /var/log/rackhd.

@pscharla @RackHD/corecommitters

@anhou @panpan0000 @changev @iceiilin

:+1:


Migrate data loaders and related functions from pyfolio

See this comment https://github.com/quantopian/alphalens/pull/183#issuecomment-321880108 and PR for context on this PR. Also this empyrical issue https://github.com/quantopian/empyrical/issues/55

@jameschristopher Thanks! Can you add the symbol lookup too?

This should also allow pandas_datareader to be removed from the explicit pyfolio install reqs.

Looks great, thanks @jameschristopher! Want to do the PR to remove them from pyfolio?

already working on it :)

@twiecki @jameschristopher it may be better to simply deprecate the data loaders from pyfolio, instead of removing them without warning. Easier for our open source users to pick up.

Removal will only affect new installations or updates, and as long as we
bump the empyrical version in the requirements this shouldn't introduce any
breaking changes
On 14 August 2017 at 18:44, George Ho<EMAIL_ADDRESS>wrote:

@twiecki https://github.com/twiecki @jameschristopher
https://github.com/jameschristopher it may be better to simply
deprecate the data loaders from pyfolio, instead of removing them without
warning. Easier for our open source users to pick up.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/quantopian/empyrical/pull/56#issuecomment-322354827,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANMm6JFrx91qaZb2Ng1ZnQDqZe4ItSMpks5sYPgEgaJpZM4O1i7C
.

--
James Christopher
509.540.2772
https://github.com/jameschristopher

I agree that it's a concern, however, we can just from empyrical import ... for the functions we moved and change the requirements.

Can we release a new version of empyrical so I can add that to the pyfolio requirements?

I'll also need a new version of empyrical for my alphalens PR @richafrank


0.76.1 auth script, first user not owner?

Home Assistant release with the issue:
0.76.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian
Component/platform:
auth
Description of problem:
I added users with the script (hass --script auth --config /home/homeassistant/.homeassistant add) instead of the UI, which I saw after HASS has booted, but I already added them using the script. Now I seem unable to configure the users from the UI. I have already tried to remove the users (adapted the script, calling async_remove_auth), but the UI won't ask for registering users anymore.
So my guess is that the script does not add the "is_owner" tag. What to do now? Where are the credentials and user info saved so I can change it myself?
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Traceback (if applicable):
Additional information:

Sounds like you have the skill need, then you should be able to edit [config_folder]/.storage/auth file by yourself.
At least, delete [config_folder]/.storage folder will clean up all new auth stuff.
Closing this issue since it is a support question, not a bug.


Livewire 3

hay @timvandijck ,
I am getting the following error after this PR.
Target class [Spatie\LaravelIgnition\ContextProviders\ComponentRegistry] does not exist.

Dang an import was missing?.. Yikes.


fix bug in homophones.py that was forgetting all the homophones

Previously homophones.py was conditionally reading homophones.csv, but unconditionally updating all_homophones and ctx.lists["self.homophones_canonical"], which meant that updates that didn't change homophones.csv would wipe the homophones list.

🤦 , thanks for fixing this


put-file -r regression

What happened?:
put-file -r ... puts the contents of all the underlying files into a single file (the name of the lexigraphically last child file under the directory)
ubuntu@ip-10-74-68-193:~/Pachyderm$ mkdir bar
ubuntu@ip-10-74-68-193:~/Pachyderm$ echo 'hai' > bar/a
ubuntu@ip-10-74-68-193:~/Pachyderm$ echo 'bai' > bar/b
ubuntu@ip-10-74-68-193:~/Pachyderm$ pachctl create-repo bar
ubuntu@ip-10-74-68-193:~/Pachyderm$ pachctl start-commit bar master
ea38878829d84b96b577c20814c84b41
ubuntu@ip-10-74-68-193:~/Pachyderm$ pachctl put-file -r bar master rows/bar -f bar
ubuntu@ip-10-74-68-193:~/Pachyderm$ pachctl finish-commit bar master
ubuntu@ip-10-74-68-193:~/Pachyderm$ pachctl list-file bar master
NAME TYPE SIZE
rows dir  8B
ubuntu@ip-10-74-68-193:~/Pachyderm$ pachctl list-file bar master /rows
NAME      TYPE SIZE
/rows/bar dir  8B
ubuntu@ip-10-74-68-193:~/Pachyderm$ pachctl list-file bar master /rows/bar
NAME        TYPE SIZE
/rows/bar/b file 8B
ubuntu@ip-10-74-68-193:~/Pachyderm$ pachctl version
COMPONENT           VERSION
pachctl             1.7.6
pachd               1.7.3-748b08baf176d585f23c4f63d362fb008e0180a1
ubuntu@ip-10-74-68-193:~/Pachyderm$
ubuntu@ip-10-74-68-193:~/Pachyderm$ pachctl get-file bar master /rows/bar/b
bai
hai

What you expected to happen?:
In 1.7.3 this behaved differently:
18-08-22[12:31:11]:Pachyderm:0$mkdir foo
18-08-22[12:31:18]:Pachyderm:0$echo 'hai' > foo/a
18-08-22[12:31:23]:Pachyderm:0$echo 'bai' > foo/b
18-08-22[12:31:27]:Pachyderm:0$
18-08-22[12:31:28]:Pachyderm:0$
18-08-22[12:31:28]:Pachyderm:0$pc version
COMPONENT           VERSION
pachctl             1.7.3
pachd               1.7.3-748b08baf176d585f23c4f63d362fb008e0180a1
18-08-22[12:31:31]:Pachyderm:0$pc create-repo foo
18-08-22[12:31:41]:Pachyderm:0$pc start-commit foo master
241186ef0ab34e32ad23e08e7c1160ad
18-08-22[12:32:24]:Pachyderm:0$pc put-file -r foo master /rows/foo -f foo
18-08-22[12:33:00]:Pachyderm:0$pc finish-commit foo master
18-08-22[12:33:07]:Pachyderm:0$pc list-file foo master
NAME TYPE SIZE
rows dir  8B
18-08-22[12:33:11]:Pachyderm:0$pc list-file foo master /rows
NAME      TYPE SIZE
/rows/foo dir  8B
18-08-22[12:33:14]:Pachyderm:0$pc list-file foo master /rows/foo
NAME        TYPE SIZE
/rows/foo/a file 4B
/rows/foo/b file 4B
18-08-22[12:33:17]:Pachyderm:0$pachctl version
COMPONENT           VERSION
pachctl             1.7.3
pachd               1.7.3-748b08baf176d585f23c4f63d362fb008e0180a1

The issue here is that you're using 1.7.6 pachctl with a 1.7.3 series pachd. One has #3118 while the other does not, that PR changed around how PutFileRequests are sent, such that when you do a put-file -r all of the files get sent in the same stream, 1.7.3 interprets this as appending all of the data to a single file.
I just did a test to confirm that this does indeed produce the right results with pachd and pachctl at master.

Ok cool. Good to see it wasn't a regression.
I have had customers explicitly ask if it's ok to use a newer client than server version. (This happens easily as their team members start using pachyderm long after the cluster has been deployed). Generally I think we say its fine. Maybe we need to change our response, or perhaps in the changelog list when there are breaking changes? That can be tricky to estimate / catch in the changelog though.


Unable to install scipy in the python:3 image

I'm trying to install some libraries on top of the python:3 image but it isn't working due to some missing libraries, e.g. openblas, mkl, vml, guide, lapack.
Maybe they have been removed during the purge. Any ideas on how to solve it other than reinstalling them by hand?
Here's the terminal output:
$ docker run -it python:3 bash
Unable to find image 'python:3' locally
3: Pulling from library/python

Digest: sha256:d4e91d39a14154f5d5cb33048e3a8f03d3316e1acf585383519bd89a0611d3d7
Status: Downloaded newer image for python:3
root@3b9e3eb5d1d6:/# pip install scipy
Collecting scipy
  Downloading scipy-0.17.0.tar.gz (12.4MB)
    100% |████████████████████████████████| 12.4MB 37kB/s
Collecting numpy>=1.6.2 (from scipy)
  Downloading numpy-1.10.4.tar.gz (4.1MB)
    100% |████████████████████████████████| 4.1MB 118kB/s
Installing collected packages: numpy, scipy
  Running setup.py install for numpy
  Running setup.py install for scipy
    Complete output from command /usr/local/bin/python3.5 -c "import setuptools, tokenize;__file__='/tmp/pip-build-e9cx2_9t/scipy/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-gxr2_g9y-record/install-record.txt --single-version-externally-managed --compile:
    lapack_opt_info:
    openblas_lapack_info:
      libraries openblas not found in ['/usr/local/lib', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
      NOT AVAILABLE

    lapack_mkl_info:
    mkl_info:
      libraries mkl,vml,guide not found in ['/usr/local/lib', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
      NOT AVAILABLE

      NOT AVAILABLE

    atlas_3_10_threads_info:
    Setting PTATLAS=ATLAS
      libraries tatlas,tatlas not found in /usr/local/lib
      libraries lapack_atlas not found in /usr/local/lib
      libraries tatlas,tatlas not found in /usr/lib
      libraries lapack_atlas not found in /usr/lib
      libraries tatlas,tatlas not found in /usr/lib/x86_64-linux-gnu
      libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
    <class 'numpy.distutils.system_info.atlas_3_10_threads_info'>
      NOT AVAILABLE

    atlas_3_10_info:
      libraries satlas,satlas not found in /usr/local/lib
      libraries lapack_atlas not found in /usr/local/lib
      libraries satlas,satlas not found in /usr/lib
      libraries lapack_atlas not found in /usr/lib
      libraries satlas,satlas not found in /usr/lib/x86_64-linux-gnu
      libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
    <class 'numpy.distutils.system_info.atlas_3_10_info'>
      NOT AVAILABLE

    atlas_threads_info:
    Setting PTATLAS=ATLAS
      libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib
      libraries lapack_atlas not found in /usr/local/lib
      libraries ptf77blas,ptcblas,atlas not found in /usr/lib
      libraries lapack_atlas not found in /usr/lib
      libraries ptf77blas,ptcblas,atlas not found in /usr/lib/x86_64-linux-gnu
      libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
    <class 'numpy.distutils.system_info.atlas_threads_info'>
      NOT AVAILABLE

    atlas_info:
      libraries f77blas,cblas,atlas not found in /usr/local/lib
      libraries lapack_atlas not found in /usr/local/lib
      libraries f77blas,cblas,atlas not found in /usr/lib
      libraries lapack_atlas not found in /usr/lib
      libraries f77blas,cblas,atlas not found in /usr/lib/x86_64-linux-gnu
      libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
    <class 'numpy.distutils.system_info.atlas_info'>
      NOT AVAILABLE

    lapack_info:
      libraries lapack not found in ['/usr/local/lib', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
      NOT AVAILABLE

    lapack_src_info:
      NOT AVAILABLE

      NOT AVAILABLE

    /usr/local/lib/python3.5/site-packages/numpy/distutils/system_info.py:1552: UserWarning:
        Atlas (http://math-atlas.sourceforge.net/) libraries not found.
        Directories to search for the libraries can be specified in the
        numpy/distutils/site.cfg file (section [atlas]) or by setting
        the ATLAS environment variable.
      warnings.warn(AtlasNotFoundError.__doc__)
    /usr/local/lib/python3.5/site-packages/numpy/distutils/system_info.py:1563: UserWarning:
        Lapack (http://www.netlib.org/lapack/) libraries not found.
        Directories to search for the libraries can be specified in the
        numpy/distutils/site.cfg file (section [lapack]) or by setting
        the LAPACK environment variable.
      warnings.warn(LapackNotFoundError.__doc__)
    /usr/local/lib/python3.5/site-packages/numpy/distutils/system_info.py:1566: UserWarning:
        Lapack (http://www.netlib.org/lapack/) sources not found.
        Directories to search for the sources can be specified in the
        numpy/distutils/site.cfg file (section [lapack_src]) or by setting
        the LAPACK_SRC environment variable.
      warnings.warn(LapackSrcNotFoundError.__doc__)
    Running from scipy source directory.
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-e9cx2_9t/scipy/setup.py", line 265, in <module>
        setup_package()
      File "/tmp/pip-build-e9cx2_9t/scipy/setup.py", line 262, in setup_package
        setup(**metadata)
      File "/usr/local/lib/python3.5/site-packages/numpy/distutils/core.py", line 135, in setup
        config = configuration()
      File "/tmp/pip-build-e9cx2_9t/scipy/setup.py", line 182, in configuration
        config.add_subpackage('scipy')
      File "/usr/local/lib/python3.5/site-packages/numpy/distutils/misc_util.py", line 1002, in add_subpackage
        caller_level = 2)
      File "/usr/local/lib/python3.5/site-packages/numpy/distutils/misc_util.py", line 971, in get_subpackage
        caller_level = caller_level + 1)
      File "/usr/local/lib/python3.5/site-packages/numpy/distutils/misc_util.py", line 908, in _get_configuration_from_setup_py
        config = setup_module.configuration(*args)
      File "scipy/setup.py", line 15, in configuration
        config.add_subpackage('linalg')
      File "/usr/local/lib/python3.5/site-packages/numpy/distutils/misc_util.py", line 1002, in add_subpackage
        caller_level = 2)
      File "/usr/local/lib/python3.5/site-packages/numpy/distutils/misc_util.py", line 971, in get_subpackage
        caller_level = caller_level + 1)
      File "/usr/local/lib/python3.5/site-packages/numpy/distutils/misc_util.py", line 908, in _get_configuration_from_setup_py
        config = setup_module.configuration(*args)
      File "scipy/linalg/setup.py", line 20, in configuration
        raise NotFoundError('no lapack/blas resources found')
    numpy.distutils.system_info.NotFoundError: no lapack/blas resources found

Have the same issue here, although all of those are installed on my system or in the virtualenv I am using. Somehow it doesn't find the libraries.

I have the same issue with virtualenvwrapper.

Turns out it all worked when I created a new virutalenv. The other one was created by anaconda and that's why the dependencies couldn't be found by pip.

I managed to do the install by preinstalling some debian packages before:
RUN apt-get update -qqy && apt-get install -qqy libopenblas-dev gfortran

I think this is fixed now! :smile:
$ docker run -it --rm python:3 bash
root@a31adf41234d:/# pip install scipy
Collecting scipy
  Downloading scipy-0.18.0-cp35-cp35m-manylinux1_x86_64.whl (42.0MB)
    100% |████████████████████████████████| 42.0MB 58kB/s
Installing collected packages: scipy
Successfully installed scipy-0.18.0
root@a31adf41234d:/#

I found a local, portable install was helpful for tricky situations, winpython for example. You keep all the packages in there as well and can just travel with your full Python install. I had good luck with enthought, but when a tricky issue came up, winpython was the answer.

I've retested it and it's working now. Great! Not sure how it was fixed, though.


feat: add gitea remote driver.

Since Gitea already supports status API. https://github.com/go-gitea/gitea/pull/1332 It is time to create a new remote driver for Gitea.
cc @tboerger @lunny @bkcsoft
ref: https://github.com/drone/drone/issues/1978

@tboerger @lunny Fix testing first.

Very nice, when this can be merged ?=)

@bradrydzewski @lunny @bkcsoft @tboerger @DblK
https://github.com/drone/drone/pull/2017/commits/7641092070c4588eb3c80bb74d82e3b3e84645b7
I already finished the implements of deactivate and refactor the file method finally. Please help to review again. Please make sure you need to update some changes from https://github.com/go-gitea/gitea/pull/1755 before testing this PR.


Unwanted typescript errors when dev server is started

Describe the bug
Note that I am running vite under a monorepo setup, specifically using pnpm workspaces. I just bootstrapped the app with react-ts and vite-plugin-checker is the only plugin installed. I can see the following error
5:27:36 AM [vite] vite.config.ts changed, restarting server...
5:27:36 AM [vite] server restarted.

 ERROR(TypeScript)  Duplicate identifier 'Prepend'.
 FILE  /home/<USER>/project/node_modules/.pnpm/@types+eslint@7.29.0/node_modules/@types/eslint/helpers.d.ts:1:6

  > 1 | type Prepend<Tuple extends any[], Addend> = ((_: Addend, ..._1: Tuple) => any) extends (..._: infer Result) => any
      |      ^^^^^^^
    2 |     ? Result
    3 |     : never;
    4 |

 ERROR(TypeScript)  Duplicate identifier 'Prepend'.
 FILE  /home/<USER>/project/node_modules/.pnpm/@types+eslint@8.4.1/node_modules/@types/eslint/helpers.d.ts:1:6

  > 1 | type Prepend<Tuple extends any[], Addend> = ((_: Addend, ..._1: Tuple) => any) extends (..._: infer Result) => any
      |      ^^^^^^^
    2 |     ? Result
    3 |     : never;
    4 |

[TypeScript] Found 2 errors. Watching for file changes.

Screenshot:

This is my config file:
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import checker from 'vite-plugin-checker'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react(), checker({
    typescript: {
      root: '.', tsconfigPath: 'tsconfig.json'
    }
  })],
  server: {
    host: '<IP_ADDRESS>',
    port: 3000,
  }
})

Reproduction

add new module under a pnpm monorepo (with eslint being a dependency in other workspace packages)
start the dev server with the vite-plugin-checker plugin added

Expected behavior
The plugin should only typecheck source folder contents
System Info
System:
    OS: Linux 5.4 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (2) x64 DO-Regular
    Memory: 482.94 MB / 3.84 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.17.0/bin/yarn
    npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm
  npmPackages:
    vite-plugin-checker: ^0.4.4 => 0.4.4

Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

any issues reported by running tsc --noEmit?

I got a similar issue with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Turns out it was because skipLibCheck was set to true in my project tsconfig.json file.

@val1984 I think setting skipLibCheck to true can eliminate this report. And could you run tsc --noEmit in your project to verify is it a right report from tsc?

Sorry, I wasn't clear in my previous message but it definitely fixed the issue for me.
@smtrd3 Can you try this solution?

For anyone who encounters similar issues. You can run tsc --noEmit or vue-tsc --noEmit under your project. If the command reports the same issues, then there's nothing to do with vite-plugin-checker cause it just forwards the issues. If not, please leave a comment below.

I am having the same problem, in my case I am getting way more erros from node_modules libs:

@guiphc add skipLibCheck: true to tsconfig

@guiphc add skipLibCheck: true to tsconfig

this did not work, for some reason looks like the plugin did not respect my tsconfig.

@guiphc Provide a stackblitz link please

I'm kind of experiencing this as well, though it's more of a bonus than a bug for me. If I run tsc --noEmit the errors that are being reported by the plugin are indeed picked up by TypeScript, but these errors aren't reported in the IDE (VS Code). I know Vite doesn't really care, but they're of course not reported during the vite build process as well, meaning I probably never would have caught these if I wasn't using the plugin (❤).
Is this a TypeScript bug, a VS Code bug or? Any hints on how I can make sure that these bugs are reported in the IDE as well?

same issue +1.
If I run tsc --noEmit, there are no errors.
But when I use this plugin, it report errors from node_modules folder.
It maybe caused by monorepo


Update Set-SPExcelFileLocation.md

Updated example. Filled in placeholder text.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Set-SPExcelFileLocation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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


move lib/*-functions ./

The directory root is now clean and simple. Yay.
I'm still very drawn to the idea of putting the resource-functions scripts in the top level dir.
This would mean they're listed when someone hits the project page or checks out directory.
I feel like this would make them more accessible.
What do you think @jonhiggs ?
bash-my-aws(dev)$ ls
LICENSE   Makefile  README.md bin       doc       lib       test

I feel that it's self-explanatory and well documented the way that it is. If you feel strongly I won't object to changing it.


Setting ssh-port = 22 in config file results in error

Setting ssh-port = 22 results in the following error:
 » transient run -config test/config-files/comprehensive-config
Finished preparation. Starting virtual machine
qemu-system-x86_64: Could not set up host forwarding rule 'tcp::22-:22'
2020-07-23 09:25:35:ERROR:QEMU Process has died

Since transient sets the ssh port to 22 by default, manually setting the default in the configuration file should not result in an error.

As we discussed, this is because the ssh-port is the port the client connects to and the port QEMU binds to. QEMU cannot bind to a low port as an unprivileged user, so this fails as expected. Also, port 22 is not the default. The default is a random high port.
I'm going to go ahead and close this, as I think it's working as expected (I don't think it's worth the added complexity to try to detect this situation and print a clearer error. That seems like something QEMU should be doing).


Connection Pooling / Persistent HTTP Conns

Hello,
I looked through parts of the code and the docs, but couldn't find anything. Does RestClient support either conn pools or otherwise holding a persistent, reusable connection?
It looked to be using raw Net::HTTP, which does not do these things natively (although a community supported persistent variant does exist)
Thanks

It doesn't currently do these things, though it's possible that it will do so especially for Ruby 2.0, where I think Net::HTTP implements keepalive requests. (Pull requests welcome.)


Tooltip documentation?

First off, fantastic work!
I love the simplicity of this "framework". :smile: My HTML is so clean and pretty now.
This is not really a bug, but I noticed that there is a tooltip plugin, which seems to be included in the minified copy available here, but it seems to be missing from the current documentation page.
Is this intended, like a feature not ready for production?

Totalolly agree, I made a mistake and forgot to change src/plugins/tooltip/documentation.md into src/plugins/tooltip/readme.md so it's not picked up by the new build system.


Refactor Waze Travel Time & Update Requirements

Refactored Waze Travel Time to contain a data object.
Changed error retrieving data to a warning.
Added distance conversion depending on region.
Removed dependency on TRACKABLE_DOMAINS list.
Update to use WazeRouteCalculator 0.10
3rd time's a charm.  Deleted fork, caused last PR to screw up.  So here we are.
Breaking Change:

Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Deleted fork because of unrelated issues.  Unable to update https://github.com/home-assistant/home-assistant/pull/22226 because of the missing fork.  Created this PR instead.

Any idea when this is going to be merged? This is a breaking fix right, I can't get travel times now with the waze_travel_time component.

No clue.  You can add it as a custom component and it will overwrite what you have.

No clue. You can add it as a custom component and it will overwrite what you have.

How should i add it? custom_components/waze/sensor.py?

custom_components/waze_travel_time/sensor.py

any estimate to merge?

If all checks passed, why is there conflicts?

Because this sat here for 3 months.  I'm going to create a new PR sometime in the near future.  At that point, I'm going to add a few new functions and I'm going to ping the devs to take a look at it.  As for this PR, it looks like it has been ignored.


Update AutoRest C# version

Update AutoRest C# version to 3.0.0-beta.20211102.1

Closing this PR in favor of https://github.com/Azure/azure-sdk-for-net/pull/25090.