Add Llama2

Added the easy way via Cloud Groq API but will probably need to come back for real local implementations with other abstractions, closing for now as initial requirement met.


How to route .html url extension

Code like this:
 get("/article/:id.html", (request, response)->{     return request.params(":id"); });

I guess you will have to use wildcard pattern and extract that id from url manually (like using regex group).

Why not use the static file handler?

Because the .html is dynamic page :-)
Some search engines prefer url end with .html, and give the domain a higher weight.

I have the same problem. For REST


gnutls: 3.6.12 -> 3.6.13 [security]

Motivation for this change
Fixes CVE-2020-11501.
Changes: https://lists.gnupg.org/pipermail/gnutls-help/2020-March/004642.html
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I plan to test backports later today.

In any case, to me DTLS feels rarely used.  After quic stabilizes and gets more "popularity" through http/3, I expect DTLS usage to wane even more.

Now it's in staging-{19.09,20.03} as well.


🚀 Feature Request: Update the Framework Starter CLI of Svelte

Describe the solution
When using the command npm create cloudflare@latest and choosing the Svelte Framework Starter, it uses the old npx<EMAIL_ADDRESS>but now Svelte has a new CLI that is npx sv create for new versions of Svelte.

Duplicate of #7029


nil pointer panic happens in updateClusterTaints()

What happened:
run clusternet-controller-manager built from main  happens paic, the error log as bellow

acctually, this failure is indruced from PR #673
What you expected to happen:
updateClusterTaints()  will run normally when managed cluster's status is true or the managed cluster is  a new cluster
How to reproduce it (as minimally and precisely as possible):
build  image with PR #673, and run clusternet-controller-manager

the cluster object could be nil from https://github.com/clusternet/clusternet/blob/4e77b70d8ecf900330b982764c9a3cc8e4379d4a/pkg/controllers/clusters/clusterlifecycle/clusterlifecycle_controller.go#L177
so it should return cluster, nil to replace nil, nil


Machine Learning Project Review

You need to create 3 repositories i.e

Machine Learning Projects (Learning),
Machine Learning projects(Capstones)
Machine Learning projects (Personal Practice)
Within each repository, you will need a folder for each of the projects, have a standard way of naming them i.e

Week 1 Boston Regression
Week 2 Credit Risk Classification etc.
Within each week, have a readme of the project, detail what you did, what was the outcome and what were the key concepts/lessons learnt.

The Readme here is incomplete. Your readme needs to have the following sections

Title and Description (What the project is about and what it seeks to solve, i.e the objectives)
Data Source
Insights about the data (Key ones only, accompanied with some charts)
The product, what was the ML development steps and the outcomes to the same (output can be a graph eg a confusion matrix plot, with explanations below it)
Acknowledgments

Notebook Structure is not okay. You need to have a structured way of modelling, ie,

Give background (Done)
Data Context (When was the data collected, from where have you obtained it)
Problem Statement (What are you trying to predict)

EDA Steps

When doing EDA, I would advice against splitting the data first before exploring it, as some features would need to be explored in the context of the independent variable y
What is the full meaning of this "OOPs for plots"
For each plot you have to note what you have observed
This step 'Summary statistics for each numerical feature' can easily be done by the .info() method
Are your features linearly separable, that should be intention of this plot : sns.pairplot(Clients,vars=['Age', 'AnnualIncome','FamilyMembers'], hue='TravelInsurance')
This step (Converting the categorial features into binary) can easily be done by an encoder - use that.

Feature Engineering

There are no derived features in your dataset, which would help with improving the prediction.

Data pre-processing

You need to have a section title for this.
There is no need for this "To check if the spread of splits"

Modelling

You data is so small relatively speaking, thus instead of going with hold out sets, I would advice that you do cross val scores which give a realistic value for the model performance

Model evaluation

There is no tuning of parameters that you have done here, so the section " Defining models while tuning their hyperparameters" is misleading
This model evaluation metric selected is not the best, you need to use a more balance metric eg F1_score
Your model performance on train data is wanting, remember, I mentioned you need to aim for 90% and above, given this work has been done in many platforms.

You need to post the score you got on Kaggle.


no where to link to get-started?

Hi, I googled elm make, and find http://elm-lang.org/get-started , that is great place for elm tools introduction.
But from http://elm-lang.org/docs there seems to be no link to get-started page. maybe the link is in some other place I don't know?

No, there is no such link at present (only one from http://elm-lang.org/install). I have several issues/PRs open to provide better linking to the get-started page, but they remain unprocessed.

There's a link now.

Oops, maybe not. Will check again.

There isn't.

Still no link :) I started learning today and it's not obvious at all Where you should start. Fortunately, the gitbook links to it. It's really confusing to see examples but not obvious explanation of how to run them locally.

Okay, now it's on /docs


Debugger: Put "Run To Cursor" Into Breakpoint Context Menu

Currently, "Run To Cursor" is in a very long context menu:

I think it would make sense to add "Run To Cursor" to the context menu for adding breakpoints:

This new entry should be called "Run To Line".
Pro:

That context menu is already strictly debugging related
If a user does not know about "Run To Cursor" and manually places a breakpoint to the target location, they might discover this functionality in that context menu

Contra:

"Run To Line" is not a breakpoint

@hediet thanks for this suggestion, however please note that we show the Run To Cursor and Add Inline Breakpoint in the editor context menu only while a user is debugging. So it is not always there.
I understand you are always in debugging mode and I think we should improve the experience for "Always Debugging" mode. For this I have created https://github.com/microsoft/vscode/issues/123873
For now I would probably not change this to not anger some users that are used to it. Especially since I hope we will have customisable context menus in the future. However I am open for ideas.
fyi @connor4312 @weinand

however please note that we show the Run To Cursor and Add Inline Breakpoint in the editor context menu only while a user is debugging. So it is not always there.

I wouldn't neccessarily remove it from the editor context menu, but just add it to the breakpoint context menu to improve its accessibility.
I use that feature quite often (and should probably assign a keybinding to it), but the very long context menu makes it hard to quickly execute that action (especially when my focus is on debugging the problem, not finding that context menu entry).
The Chrome dev tools have an even more efficient approach - while debugging, you can simply Ctrl-Click on a statement to continue to it.

@hediet oh you would simply add it to the other context menu.
Yeah this could work for me.
Let's see what @connor4312  and @weinand think

Adding it to the breakpoint (gutter) context menu sounds good to me. Honestly I didn't even know that context menu entry existed, I never right click in the editor 😛

If we were to add it, I would put a separator after the breakpoint actions. And have the "Run to Line" at the bottom.
Let's assign to this milestone and if Andre does not object I can add it next week.

I can also try to implement it if we go for it! Shouldn't be that hard.

Code pointer:
https://github.com/microsoft/vscode/blob/1ccd6a079463a635756f35308e290551ca135241/src/vs/workbench/contrib/debug/browser/breakpointEditorContribution.ts#L317

Do you think the logic in RunToCursorAction should be moved to IDebugService and its implementation (and there renamed to RunToPosition)?
Then there could be both a RunToCursorAction and RunToLineAction.

@hediet that might work. However I try to keep the IDebugService as thin as possible. So I would personally just use the  commandService.executeCommand to execute one command from the other.
Though feel free to move the logic to the IDebugService if you prefer that

Leaving this assigned to you @hediet as you plan to do a PR.
Feel free to ping me on a PR for a review or let me know if I can help in any way.

consider add a decorate for user to click run to here, like VS2019?

There's a bit of breakpoint flashing when you do run to line but the context menu appears to work so marking this as verified


Environment variable to mute the macOS warning

Is there an existing proposal for this?

[X] I have searched the existing proposals

Is your feature request related to a problem?
https://github.com/bloomberg/memray/blob/ab31d4c995e83b0bf6020958d2a12903d2b322db/src/memray/_memray.pyx#L374-L376 writes to stderr when running on macOS
My tests monitor stderr and fail when running with memray because stderr has unexpected output (the warning message)
Describe the solution you'd like
The ability to have a flag/environment variable to mute this warning message
Alternatives you considered
No response

Duplicate of #194 (which has #250 as a proposed solution).
We're trying to avoid adding an environment variable for suppressing warnings, since it requires manual steps to avoid the problem from the part of people using pytest-memray. That said, there are some drawbacks to just moving where we print the warning, too...


docs: Provide more structured API docs for Workflow API

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
Provide more structured API docs for Workflow API to make clear what is required and expected.
Issue reference
N/A

Good feedback and updated the PR - Let me know what you think @cgillum!

Oh hello my good old DCO friend.

@tomkerkhove were you planning on making that last change related to the sentence starting with "In the request you can pass along..."?

@tomkerkhove were you planning on making that last change related to the sentence starting with "In the request you can pass along..."?

Yes I was, but I was sleeping :D
Done now!


Alda/universal fix user profile refactor

LGTM

TRAVIS TEST REPORT
xcodebuild: error: Unable to find a destination matching the provided destination specifier:
{ platform:tvOS Simulator, OS:10.2, name:Apple TV 1080p }
The requested device could not be found because no available devices matched the request.
Available destinations for the "OptimizelySDKTVOS-Universal" scheme:
	{ platform:tvOS Simulator, id:2FCBFEBA-910F-4BBA-B357-C48DBC169944, OS:9.0, name:Apple TV 1080p }
	{ platform:tvOS Simulator, id:86534800-B2FE-41D6-92B9-1689582B744F, OS:9.1, name:Apple TV 1080p }
	{ platform:tvOS Simulator, id:85AC2440-CEB5-44FF-BD7B-5C4A0F9E4DE1, OS:9.2, name:Apple TV 1080p }
	{ platform:tvOS Simulator, id:F7EAE05E-9661-43EC-8348-713F6FF49AB9, OS:10.0, name:Apple TV 1080p }
	{ platform:tvOS Simulator, id:C12DA372-F96C-4CD0-BEF4-63EC1182DBD2, OS:10.1, name:Apple TV 1080p }

I tested "OptimizelySDKTVOS-Universal" scheme against "Apple TV 1080p (10.2)" in the Xcode IDE 8.3.2 myself, and the test PASSED.  Therefore, I suppose we should tweak our local_travis.sh script to avoid Travis' limitation "Unable to find a destination matching the provided destination specifier: { platform:tvOS Simulator, OS:10.2, name:Apple TV 1080p }" sometime in the future.  However, I don't consider this a P.R. 140 showstopper and I still recommend merge.


Text fields don't render on Linux

I'm having an issue where text fields from my csv seem to be importing properly, but the text in the csv does not render on the exported images or in the WYSIWYG Canvas panel.  I can see the values of each row in the Element Control panel table, which seems to be working as expected.  I don't see anything strange in the on screen log.  I've tried multiple common fonts (e.g. Ariel).
I'm running CardMaker_<IP_ADDRESS> on a Debian Linux with mono-complete installed.
Any idea for what could be causing this problem or things I could try to fix it?

I've only really tried with ubuntu unfortunately. Can you try running with one of the newer releases (pre-releases) and see if it makes any difference? Is there anything displayed in the console/terminal window when running? Sometimes there can be interesting extra information logged there.
I am guessing the included sample project also does not work at all...

I installed Debian 10.5.0 in a VirtualBox VM. I only had access to certain fonts so CardMaker switched over to the Liberation Sans (...) fonts. This is running with CardMaker <IP_ADDRESS> A13. It still rendered though...

Hmm, it still doesn't work for me.  I'm on a custom Linux distribution that is based on Debian though, so I might be missing a certain package that will make it work.  I'll update this bug if I figure it out.

Actually i'm having the same problem on windows now too!  Perhaps my project/csv files are the culprits?  Can you reproduce with them?
repro_data.zip

Actually i'm having the same problem on windows now too! Perhaps my project/csv files are the culprits? Can you reproduce with them?
repro_data.zip

Thanks for the data! It appears you need to configure your definitions on the elements to associate with the column from the resources.csv
In your case the element named name should have this definition value: @[name]
tier should have this definition value: @[tier]
The same is true for the rest of the elements and columns. You can also have other characters in the definition as necessary.
Take a look through the Basic Deck for some more information too.
I hope that helps!

Ah yes that was my problem, this all makes much more sense now.  Thanks for all the help, and sorry for not reading the documentation more closely : ).


[azk shell logs] Showing logs when building an image

I complemented the #211 feature to show log messages when azk is building an image. This happens when Azkfile.js uses a Dockerfile as an image.
$ azk shell
azk: ⇲ building `azkbuild/a4746dc0a9-my_app:6651ddff6eb82c840ced7c1dddee15c6e1913dd4` image...
root@241746bb3d60:/azk/docker-registry-downloader#

Now, it shows log messages when downloading or building an image.

Very nice @lucasfais

LGTM

LGTM :+1:


Fix max server timeout for batch queries

This PR fixes NPE when there are batch queries that have server timeout configured.
Fixes https://github.com/Azure/azure-sdk-for-java/issues/29339

API change check
API changes are not detected in this pull request.


face liveliness test by blinking eye

I am looking at this demo - https://storage.googleapis.com/tfjs-models/demos/face-landmarks-detection/index.html
How can i get a trigger when eye is blinked ?
If you can provide me any direction , it will be very helpful.

I am sorry for that, I tried to tell you what i am doing and what i need to achieve. I came to mediapipe from here- https://blog.tensorflow.org/2020/11/iris-landmark-tracking-in-browser-with-MediaPipe-and-TensorFlowJS.html
I just need help , want to catch when eye blinks, if possible. If not , you can close this
Regards

I would recommend you to use face mesh Javascript solution. Eye blinking you can notice this point  regarding the face mesh. Let us know if you are looking for anything more.

Hey @ersaurabh101,

I tried to use this code but it doesnt trigger any message in console, if you can help and get it to work or something similar - https://gist.github.com/kleysonr/d75494f239ad0dce561a55a624920693

Unfortunately, I can't help you with other person's code. Please, contact that person directly to get a fix

How can i get a trigger when eye is blinked ?

That can be done using MediaPipe JS solution mentioned by @sgowroji (please, explore the links in https://github.com/google/mediapipe/issues/2313#issuecomment-883153031). To detect if someone blinked, you probably need to work with landmarks from the FACEMESH_LEFT_EYE  and FACEMESH_RIGHT_EYE contours. For each eye, please pick face mesh landmarks on both vertical and horizontal edges of the eye. Then, compute the distance ratio between the vertical / horizontal edge segments - that ratio will be a good target for thresholding in a heuristic. I can't tell you specifics now as I didn't play with exact values, but there will probably be a different confidence interval of the horizontal_edge_segment / vertical_edge_segment expression value when an eye is closed and it is open - you can use that to detect whether there was a blink or not.
Sorry for the lack of specifics, hopefully this rough outline of one possible algorithm is a good starting point for your project!


[postgres] Multiple entry in cache

Hello,
When I look in scan_results table in my ortdb postgres, I can see some multiple entry for the same identifier.
Do you know how can it happen ? Concurrent scanner phase ?
Regards

I believe this might happen due to the issue @fviernau did put a stop-gap in at https://github.com/oss-review-toolkit/ort/pull/2850.

I'm aware of the following scenario where this happens:

You trigger a scan let's say passing an analyzer result
The scanner at the very beginning look-up scan cache entries for all packages and enqueues only the packages with no cache entry for scanning
The actual scan for each package takes place which involves writing to the scan cache at the end.

In above scenario the time interval between (2) and the storing of the cache entries in (3) might be large, e.g. even hours.
If during that time that same scenario is run in parallel, you'd end up with duplicate cache entries.

Hi @fviernau
Yes in some rare cases, this scenario happens when I do tests in // with the jenkins pipeline. But we have normaly only 1 job running for OSS analysis
But I think, more oftens it's due to a crash/failure in CI when the scanner write in cache

If no parallelism is involved I don't see how scan results could be duplicated. What kind of crash do you mean? I haven't seen any crashes while reading from or writing to the database so far.

I run ORT with docker in a K8S infrastructure. Sometimes K8S kill the pod for cpu or memory constraints.

Since #4496 duplicate entries in the PostgresStorage are prevented by an index. For existing databases this index needs to be manually added after removing any duplicates, see: https://github.com/oss-review-toolkit/ort/blob/cef3f17fd000cd77c8e041e5381878d215460110/scanner/src/main/kotlin/storages/PostgresStorage.kt#L124-L131


Proposal: Onboarding Builders Series Space Support

Description

It focuses on introducing the Kaia chain to builders.
Open developer's workshop.
Training sessions on how to build on Kaia using solidity and foundry.
and How to build on Line.

Bounty track

[add the name of the bounty track here]

You should amend this issue for each session/workshop you want to run.

You should amend this issue for each session/workshop you want to run.

Okay.

https://dorahacks.io/buidl/16795
https://x.com/paulelishaa/status/1840466012317294658

Approved for 200 KLAY bounty. Closing for payout.


Crafting Table - Serverside Crash?

Industrial Foregoing Version: 2.2.2 (mc1.15)
TeslaCoreLib Version: N/A
Crashlog (If Any): https://pastebin.com/W8sLSjkg
Description: An apparent issue with Industrial Foregoing when using related items in a crafting table (this also includes crafting terminals from RS). This results in a server crash, a reboot will fix it until the same instance happens again. Any ideas?

Having same issue, blamed morph-o-tool for it, not sure whats the correct issue
https://github.com/Vazkii/Morph-o-Tool/issues/54


Integration for Phelia framework

Phelia, the React-integrated framework for Slack Block Kit, has become popular suddenly in spite of the newcomer. Surprisingly it has amassed many stars than Bolt, the official framework by Slack.
It has unique components to build Block Kit JSON, with an awesome React-style event handler. However, React-style HTML tags cannot use in the content.
On the other hand, jsx-slack has a stable ergonomic templating and HTML rendering that had taken a year to reach. And we're still catching up Slack's update rapidly.
One of the crazy ideas is to provide jsx-slack integration to Phelia through another render function of JSX. Wisely merging of Phelia's awesome event handling (such as <Button onClick={}>) and jsx-slack's ergonomic Block Kit template would make the wonderful experience to create the Slack app and would grow the value of both libs more.
/* @jsx JSXSlack.h */
import React from "react";
import {
  JSXSlack, // JSXSlack.h is a render function for Phelia
  Message, // <Message> is inherited from Phelia
  Actions,
  Button,
} from "@speee-js/jsx-slack/phelia";
import randomImage from "../utils";

export function RandomImage({ useState }: PheliaMessageProps) {
  const [imageUrl, setImageUrl] = useState("imageUrl", randomImage());

  return (
    <Message text="Choose a dog">
      {/* Can use jsx-slack style templating that is familiar to HTML */}

      <Actions>
        <Button
          style="primary"
          actionId="randomImage"
          onClick={() => {
            // Handle event by Phelia
            setImageUrl(randomImage())
          }}
        >

            New doggy

        </Button>
      </Actions>
    </Message>
  );
}

I'm closing this because Phelia framework looks like not to be supported by community well. A lot of stargazers don't mean many users :)

I'm closing this because Phelia framework looks like not to be supported by community well. A lot of stargazers don't mean many users :)


Doesn't support django generic views?

Docs state to use @settings.AUTH.login_required how would this be used in generic views?
@settings.AUTH.login_required
class `IndexView(generic.ListView):
...
I would also like to add the route to all views, is there a generic way to do this other than adding the decorator everywhere?

Docs state to use @settings.AUTH.login_required how would this be used in generic views?
@settings.AUTH.login_required class `IndexView(generic.ListView): ...

I haven't tried that myself. You may try to see whether Decorating class-based views helps.

I would also like to add the route to all views, is there a generic way to do this other than adding the decorator everywhere?

This library does not provide such a way out of the box, but perhaps you can look into How to apply a decorator to all views (of a module) in django.
Caveat: Only decorate the views that really need authentication, rather than blindly decorate ALL requests. There used to be a troubleshooting case where the reporter managed to incorrectly decorate both /index and /images/logo.jpg. The latter was also used in their login template`. That setup ended up having their login page triggered another login session which caused the original login session to always fail. It was difficult to debug.


Add support for Cassandra timeuuid functions

I'm trying to select data from a range of dates in a Cassandra table. The table has a timeuuid PK column.
When trying to use the following query with a CQL timeuuid method, I get the error Function 'dateof' not registered.
SELECT * FROM cassandra.default.table WHERE dateOf(column) > timestamp '2020-01-01 00:00:00';

Presto v338
Cassandra v3.11.3

Could you share the exact requirements because the page has more than 10 functions?
off-topic: The dateOf function is deprecated since Apache Cassandra 3.3.0.

All these time-conversion-functions. My current use case is with the toTimestamp, since I'm trying to select data above a specific date, when the only date field is of TIMEUUID type.


AEMEnvironmentIndicatorFilter breaks Felix WebConsole in AEM 6.5

Required Information

AEM Version, including Service Packs, Cumulative Fix Packs, etc: 6.5.0
ACS AEM Commons Version: 4.0.1-SNAPSHOT
Reproducible on Latest? yes

Expected Behavior
The web console is still working
Actual Behavior
The web console is no longer working and brings the browser tab to a freeze (in Google Chrome). Also there is duplicate content like outlined in the following screen:

Steps to Reproduce
Configure the AEM Environment Indicator like outllined in https://adobe-consulting-services.github.io/acs-aem-commons/features/environment-indicator/index..html and open
/system/console/configMgr afterwards.
This does not happen with ACS AEM Commons 4.0.0 so this seems like another regression in 4.0.1-SNAPSHOT.

The reason for that is that the actual HTML response is duplicated, because it is given out first via the contents and then implicitly via the close().


Dependency resolutions installs unneeded packages

[x ] I am on the latest Poetry version.

[x ] I have searched the issues of this repo and believe that this is not a duplicate. (I didn't find a good woring to search)

OS version and name: Debian unstable

Poetry version: Poetry 0.11.3

Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/apollo13/ce86e80d1152a24d6b53486b79c08b1a

Issue
Poetry installs futures in a python3.6 environment and I do not understand why:
Creating virtualenv bap-services-py3.6 in /tmp/testing/.venv
Installing dependencies from lock file

Package operations: 50 installs, 0 updates, 0 removals

  ...
  - Installing futures (3.1.1)
  ...

According to show -t only isort uses it:
 48 isort 4.3.4 A Python utility / library to sort Python imports.
 49 `-- futures *

But according to isort's setup.py https://github.com/timothycrosley/isort/blob/develop/setup.py#L57 it should only be required for python versions < 3.2

Explanation from #328:

Declaring Python version specific packages is no longer the recommended way and it should use the environment markers for this purpose.
Poetry never executes the setup.py file for security reasons and as such relies on the package metadata available in the JSON API: https://pypi.org/pypi/grpcio/json
There, futures is declared as a non-conditional dependency and as such is picked up by Poetry.
The issue should be reported upstream.

@cauebs So which data does get used? The metadata of the wheel file has:
    "requires_python": ">=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*",
    "run_requires": [
        {
            "environment": "python_version==\"2.7\"",
            "requires": [
                "futures"
            ]
        }
    ],

Running poetry debug:resolve -vvv I see that poetry downloads the wheel for py2:
PyPI: Downloading wheel: isort-4.3.4-py2-none-any.whl
   1: fact: isort (4.3.4) depends on futures (*)
   1: selecting isort (4.3.4)
   1: derived: futures (*)

That seems wrong to me.

Okay, this definitely seems to be a bug in poetry. The main issue seems to be that the wheels are not universal, which is why poetry falls back to use the first url available which makes no sense given that the pyproject.toml specifies 3.5 as minimal version.

Output on poetry version 0.11.2:
PyPI: Getting info for isort (4.3.4) from PyPI
PyPI: No dependencies found, downloading archives
   1: selecting isort (4.3.4)

and no dep on futures.

I can not reproduce on my end with your pyproject.toml:
Resolution results:

  - markupsafe (1.0)
  - certifi (2018.4.16)
  - chardet (3.0.4)
  - idna (2.7)
  - jinja2 (2.10)
  - six (1.11.0)
  - urllib3 (1.23)
  - atomicwrites (1.1.5)
  - attrs (18.1.0)
  - colorama (0.3.9)
    - platform: win32
  - coreschema (0.0.4)
  - itypes (1.1.0)
  - more-itertools (4.2.0)
  - pluggy (0.6.0)
  - py (1.5.4)
  - requests (2.19.1)
  - uritemplate (3.0.0)
  - coreapi (2.3.3)
  - pytest (3.6.3)
  - pytz (2018.5)
  - appdirs (1.4.3)
  - click (6.7)
  - coverage (4.5.1)
  - django (2.0.7)
  - djangorestframework (3.8.2)
  - future (0.16.0)
  - inflection (0.3.1)
  - jsonschema (2.6.0)
  - mccabe (0.6.1)
  - openapi-codec (1.3.2)
  - pycodestyle (2.3.1)
  - pyflakes (1.6.0)
  - pytest-metadata (1.7.0)
  - pyyaml (3.13)
  - ruamel.yaml (0.15.45)
  - toml (0.9.4)
  - wheel (0.29.0)
  - black (18.6b4)
  - drf-yasg (1.9.1)
  - flake8 (3.5.0)
  - isort (4.3.4)
  - msgpack (0.5.6)
  - pex (1.4.4)
  - pygments (2.2.0)
  - pytest-cov (2.5.1)
  - pytest-django (3.3.3)
  - pytest-html (1.19.0)
  - pytest-mock (1.10.0)
  - swagger-spec-validator (2.3.1)
  - whitenoise (3.3.1)

You may be hitting a cache problem. Can you try clearing the cache?
Only the isort cache:
poetry cache:clear pypi:isort:4.34

or the complete cache:
poetry cache:clear pypi --all

I tried with a clean cache every time; which python & os versions are you using?
Can you post poetry debug:resolve -vvvv so we can compare? Here is mine:
➜  testing poetry cache:clear pypi --all

Delete 160 entries? (yes/no) [no] yes

➜  testing rm -rf ~/.cache/pypoetry
➜  testing poetry debug:resolve -vvv
Resolving dependencies...
   1: fact: bap-services is 0.1.0
   1: derived: bap-services
   1: fact: bap-services depends on msgpack (^0.5.6)
   1: fact: bap-services depends on Django (^2.0)
   1: fact: bap-services depends on whitenoise (^3.3)
   1: fact: bap-services depends on Pygments (^2.2)
   1: fact: bap-services depends on drf-yasg (^1.9)
   1: fact: bap-services depends on swagger-spec-validator (^2.3)
   1: fact: bap-services depends on black (=18.6b4)
   1: fact: bap-services depends on pex (^1.4)
   1: fact: bap-services depends on pytest-mock (^1.10)
   1: fact: bap-services depends on pytest-html (^1.19)
   1: fact: bap-services depends on pytest-cov (^2.5)
   1: fact: bap-services depends on pytest-django (^3.3)
   1: fact: bap-services depends on pytest (^3.6)
   1: fact: bap-services depends on coverage (^4.5)
   1: fact: bap-services depends on isort (^4.3)
   1: fact: bap-services depends on flake8 (^3.5)
   1: selecting bap-services (0.1.0)
   1: derived: flake8 (^3.5)
   1: derived: isort (^4.3)
   1: derived: coverage (^4.5)
   1: derived: pytest (^3.6)
   1: derived: pytest-django (^3.3)
   1: derived: pytest-cov (^2.5)
   1: derived: pytest-html (^1.19)
   1: derived: pytest-mock (^1.10)
   1: derived: pex (^1.4)
   1: derived: black (=18.6b4)
   1: derived: swagger-spec-validator (^2.3)
   1: derived: drf-yasg (^1.9)
   1: derived: Pygments (^2.2)
   1: derived: whitenoise (^3.3)
   1: derived: Django (^2.0)
   1: derived: msgpack (^0.5.6)
PyPI: 1 packages found for flake8 >=3.5,<4.0
PyPI: 5 packages found for isort >=4.3,<5.0
PyPI: No release information found for coverage-2.5, skipping
PyPI: No release information found for coverage-2.6, skipping
PyPI: No release information found for coverage-2.75, skipping
PyPI: No release information found for coverage-2.76, skipping
PyPI: No release information found for coverage-2.77, skipping
PyPI: No release information found for coverage-2.78, skipping
PyPI: No release information found for coverage-2.8, skipping
PyPI: No release information found for coverage-2.80, skipping
PyPI: No release information found for coverage-2.85, skipping
PyPI: 3 packages found for coverage >=4.5,<5.0
PyPI: 4 packages found for pytest >=3.6,<4.0
PyPI: 3 packages found for pytest-django >=3.3,<4.0
PyPI: 2 packages found for pytest-cov >=2.5,<3.0
PyPI: 1 packages found for pytest-html >=1.19,<2.0
PyPI: 1 packages found for pytest-mock >=1.10,<2.0
PyPI: 5 packages found for pex >=1.4,<2.0
PyPI: 1 packages found for black 18.6b4
PyPI: No release information found for swagger-spec-validator-2.0.3, skipping
PyPI: 2 packages found for swagger-spec-validator >=2.3,<3.0
PyPI: 3 packages found for drf-yasg >=1.9,<2.0
PyPI: 1 packages found for pygments >=2.2,<3.0
PyPI: 7 packages found for whitenoise >=3.3,<4.0
PyPI: No release information found for django-1.0.1, skipping
PyPI: No release information found for django-1.0.2, skipping
PyPI: No release information found for django-1.0.3, skipping
PyPI: No release information found for django-1.0.4, skipping
PyPI: No release information found for django-1.1, skipping
PyPI: No release information found for django-1.1.1, skipping
PyPI: No release information found for django-1.1.2, skipping
PyPI: 11 packages found for django >=2.0,<3.0
PyPI: 1 packages found for msgpack >=0.5.6,<0.6.0
PyPI: Getting info for flake8 (3.5.0) from PyPI
   1: fact: flake8 (3.5.0) depends on pyflakes (>=1.5.0,<1.7.0)
   1: fact: flake8 (3.5.0) depends on pycodestyle (>=2.0.0,<2.4.0)
   1: fact: flake8 (3.5.0) depends on mccabe (>=0.6.0,<0.7.0)
   1: selecting flake8 (3.5.0)
   1: derived: mccabe (>=0.6.0,<0.7.0)
   1: derived: pycodestyle (>=2.0.0,<2.4.0)
   1: derived: pyflakes (>=1.5.0,<1.7.0)
PyPI: No release information found for mccabe-0.0.0, skipping
PyPI: 2 packages found for mccabe >=0.6.0,<0.7.0
PyPI: No release information found for pycodestyle-0.0.0, skipping
PyPI: 5 packages found for pycodestyle >=2.0.0,<2.4.0
PyPI: No release information found for pyflakes-0.2.0, skipping
PyPI: No release information found for pyflakes-0.2.1, skipping
PyPI: 2 packages found for pyflakes >=1.5.0,<1.7.0
PyPI: Getting info for pytest-html (1.19.0) from PyPI
   1: fact: pytest-html (1.19.0) depends on pytest-metadata (*)
   1: fact: pytest-html (1.19.0) depends on pytest (>=3.0)
   1: selecting pytest-html (1.19.0)
   1: derived: pytest-metadata (*)
PyPI: 9 packages found for pytest-metadata *
PyPI: Getting info for pytest-mock (1.10.0) from PyPI
   1: fact: pytest-mock (1.10.0) depends on pytest (>=2.7)
   1: selecting pytest-mock (1.10.0)
PyPI: Getting info for black (18.6b4) from PyPI
   1: fact: black (18.6b4) depends on toml (>=0.9.4)
   1: fact: black (18.6b4) depends on appdirs (*)
   1: fact: black (18.6b4) depends on attrs (>=17.4.0)
   1: fact: black (18.6b4) depends on click (>=6.5)
   1: selecting black (18.6b4)
   1: derived: click (>=6.5)
   1: derived: attrs (>=17.4.0)
   1: derived: appdirs (*)
   1: derived: toml (>=0.9.4)
PyPI: 4 packages found for click >=6.5
PyPI: 2 packages found for attrs >=17.4.0
PyPI: 7 packages found for appdirs *
PyPI: 1 packages found for toml >=0.9.4
PyPI: Getting info for pygments (2.2.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: Pygments-2.2.0-py2.py3-none-any.whl
   1: selecting pygments (2.2.0)
PyPI: Getting info for msgpack (0.5.6) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: msgpack-0.5.6-cp27-cp27m-manylinux1_i686.whl
   1: selecting msgpack (0.5.6)
PyPI: Getting info for toml (0.9.4) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading sdist: toml-0.9.4.tar.gz
   1: selecting toml (0.9.4)
PyPI: Getting info for pytest-cov (2.5.1) from PyPI
   1: fact: pytest-cov (2.5.1) depends on coverage (>=3.7.1)
   1: fact: pytest-cov (2.5.1) depends on pytest (>=2.6.0)
   1: selecting pytest-cov (2.5.1)
PyPI: Getting info for swagger-spec-validator (2.3.1) from PyPI
   1: fact: swagger-spec-validator (2.3.1) depends on six (*)
   1: fact: swagger-spec-validator (2.3.1) depends on pyyaml (*)
   1: fact: swagger-spec-validator (2.3.1) depends on jsonschema (*)
   1: selecting swagger-spec-validator (2.3.1)
   1: derived: jsonschema (*)
   1: derived: pyyaml (*)
   1: derived: six (*)
PyPI: 21 packages found for jsonschema *
PyPI: No release information found for pyyaml-3.01, skipping
PyPI: No release information found for pyyaml-3.02, skipping
PyPI: No release information found for pyyaml-3.03, skipping
PyPI: No release information found for pyyaml-3.04, skipping
PyPI: No release information found for pyyaml-3.05, skipping
PyPI: No release information found for pyyaml-3.06, skipping
PyPI: No release information found for pyyaml-3.07, skipping
PyPI: No release information found for pyyaml-3.08, skipping
PyPI: No release information found for pyyaml-3.09, skipping
PyPI: 9 packages found for pyyaml *
PyPI: 23 packages found for six *
PyPI: Getting info for mccabe (0.6.1) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: mccabe-0.6.1-py2.py3-none-any.whl
   1: selecting mccabe (0.6.1)
PyPI: Getting info for pyflakes (1.6.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: pyflakes-1.6.0-py2.py3-none-any.whl
   1: selecting pyflakes (1.6.0)
PyPI: Getting info for attrs (18.1.0) from PyPI
   1: selecting attrs (18.1.0)
PyPI: Getting info for coverage (4.5.1) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: coverage-4.5.1-cp26-cp26m-macosx_10_10_x86_64.whl
   1: selecting coverage (4.5.1)
PyPI: Getting info for pytest-django (3.3.3) from PyPI
   1: fact: pytest-django (3.3.3) depends on pytest (>=3.6)
   1: selecting pytest-django (3.3.3)
PyPI: Getting info for drf-yasg (1.9.1) from PyPI
   1: fact: drf-yasg (1.9.1) depends on Django (>=1.11.7)
   1: fact: drf-yasg (1.9.1) depends on djangorestframework (>=3.7.7)
   1: fact: drf-yasg (1.9.1) depends on uritemplate (>=3.0.0)
   1: fact: drf-yasg (1.9.1) depends on six (>=1.10.0)
   1: fact: drf-yasg (1.9.1) depends on future (>=0.16.0)
   1: fact: drf-yasg (1.9.1) depends on inflection (>=0.3.1)
   1: fact: drf-yasg (1.9.1) depends on ruamel.yaml (>=0.15.34)
   1: fact: drf-yasg (1.9.1) depends on openapi-codec (>=1.3.2)
   1: fact: drf-yasg (1.9.1) depends on coreschema (>=0.0.4)
   1: fact: drf-yasg (1.9.1) depends on coreapi (>=2.3.3)
   1: selecting drf-yasg (1.9.1)
   1: derived: coreapi (>=2.3.3)
   1: derived: coreschema (>=0.0.4)
   1: derived: openapi-codec (>=1.3.2)
   1: derived: ruamel.yaml (>=0.15.34)
   1: derived: inflection (>=0.3.1)
   1: derived: future (>=0.16.0)
   1: derived: six (>=1.10.0)
   1: derived: uritemplate (>=3.0.0)
   1: derived: djangorestframework (>=3.7.7)
PyPI: 2 packages found for six >=1.10.0
PyPI: No release information found for coreapi-0.1, skipping
PyPI: 1 packages found for coreapi >=2.3.3
PyPI: 1 packages found for coreschema >=0.0.4
PyPI: 1 packages found for openapi-codec >=1.3.2
PyPI: 11 packages found for ruamel.yaml >=0.15.34
PyPI: 1 packages found for inflection >=0.3.1
PyPI: 1 packages found for future >=0.16.0
PyPI: 1 packages found for uritemplate >=3.0.0
PyPI: No release information found for djangorestframework-2.4.7, skipping
PyPI: 4 packages found for djangorestframework >=3.7.7
PyPI: Getting info for coreapi (2.3.3) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: coreapi-2.3.3-py2.py3-none-any.whl
   1: fact: coreapi (2.3.3) depends on coreschema (*)
   1: fact: coreapi (2.3.3) depends on requests (*)
   1: fact: coreapi (2.3.3) depends on itypes (*)
   1: fact: coreapi (2.3.3) depends on uritemplate (*)
   1: selecting coreapi (2.3.3)
   1: derived: itypes (*)
   1: derived: requests (*)
PyPI: 2 packages found for itypes *
PyPI: No release information found for requests-0.0.1, skipping
PyPI: No release information found for requests-0.12.01, skipping
PyPI: No release information found for requests-2.15.0, skipping
PyPI: 131 packages found for requests *
PyPI: Getting info for coreschema (0.0.4) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: coreschema-0.0.4-py2-none-any.whl
   1: fact: coreschema (0.0.4) depends on jinja2 (*)
   1: selecting coreschema (0.0.4)
   1: derived: jinja2 (*)
PyPI: 31 packages found for jinja2 *
PyPI: Getting info for openapi-codec (1.3.2) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading sdist: openapi-codec-1.3.2.tar.gz
   1: fact: openapi-codec (1.3.2) depends on coreapi (>=2.2.0)
   1: selecting openapi-codec (1.3.2)
PyPI: Getting info for inflection (0.3.1) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading sdist: inflection-0.3.1.tar.gz
   1: selecting inflection (0.3.1)
PyPI: Getting info for future (0.16.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading sdist: future-0.16.0.tar.gz
   1: selecting future (0.16.0)
PyPI: Getting info for uritemplate (3.0.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: uritemplate-3.0.0-py2-none-any.whl
   1: selecting uritemplate (3.0.0)
PyPI: Getting info for six (1.11.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: six-1.11.0-py2.py3-none-any.whl
   1: selecting six (1.11.0)
PyPI: Getting info for itypes (1.1.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading sdist: itypes-1.1.0.tar.gz
   1: selecting itypes (1.1.0)
PyPI: Getting info for pytest (3.6.3) from PyPI
   1: fact: pytest (3.6.3) depends on colorama (*)
   1: fact: pytest (3.6.3) depends on pluggy (>=0.5,<0.7)
   1: fact: pytest (3.6.3) depends on atomicwrites (>=1.0)
   1: fact: pytest (3.6.3) depends on more-itertools (>=4.0.0)
   1: fact: pytest (3.6.3) depends on attrs (>=17.4.0)
   1: fact: pytest (3.6.3) depends on six (>=1.10.0)
   1: fact: pytest (3.6.3) depends on py (>=1.5.0)
   1: selecting pytest (3.6.3)
   1: derived: py (>=1.5.0)
   1: derived: more-itertools (>=4.0.0)
   1: derived: atomicwrites (>=1.0)
   1: derived: pluggy (>=0.5,<0.7)
   1: derived: colorama (*)
PyPI: No release information found for py-0.8.0-alpha2, skipping
PyPI: No release information found for py-0.9.0, skipping
PyPI: No release information found for py-1.4.32.dev1, skipping
PyPI: 4 packages found for py >=1.5.0
PyPI: 4 packages found for more-itertools >=4.0.0
PyPI: 3 packages found for atomicwrites >=1.0
PyPI: 4 packages found for pluggy >=0.5,<0.7
PyPI: 37 packages found for colorama *
PyPI: Getting info for atomicwrites (1.1.5) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: atomicwrites-1.1.5-py2.py3-none-any.whl
   1: selecting atomicwrites (1.1.5)
PyPI: Getting info for click (6.7) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: click-6.7-py2.py3-none-any.whl
   1: selecting click (6.7)
PyPI: Getting info for djangorestframework (3.8.2) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: djangorestframework-3.8.2-py2.py3-none-any.whl
   1: selecting djangorestframework (3.8.2)
PyPI: Getting info for py (1.5.4) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: py-1.5.4-py2.py3-none-any.whl
   1: selecting py (1.5.4)
PyPI: Getting info for more-itertools (4.2.0) from PyPI
   1: fact: more-itertools (4.2.0) depends on six (>=1.0.0,<2.0.0)
   1: selecting more-itertools (4.2.0)
PyPI: Getting info for pluggy (0.6.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: pluggy-0.6.0-py2-none-any.whl
   1: selecting pluggy (0.6.0)
PyPI: Getting info for isort (4.3.4) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: isort-4.3.4-py2-none-any.whl
   1: fact: isort (4.3.4) depends on futures (*)
   1: selecting isort (4.3.4)
   1: derived: futures (*)
PyPI: 21 packages found for futures *
PyPI: Getting info for pex (1.4.4) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: pex-1.4.4-py2.py3-none-any.whl
   1: fact: pex (1.4.4) depends on wheel (>=0.26.0,<0.30.0)
   1: selecting pex (1.4.4)
   1: derived: wheel (>=0.26.0,<0.30.0)
PyPI: 5 packages found for wheel >=0.26.0,<0.30.0
PyPI: Getting info for pycodestyle (2.3.1) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: pycodestyle-2.3.1-py2.py3-none-any.whl
   1: selecting pycodestyle (2.3.1)
PyPI: Getting info for wheel (0.29.0) from PyPI
   1: selecting wheel (0.29.0)
PyPI: Getting info for whitenoise (3.3.1) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: whitenoise-3.3.1-py2.py3-none-any.whl
   1: selecting whitenoise (3.3.1)
PyPI: Getting info for appdirs (1.4.3) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: appdirs-1.4.3-py2.py3-none-any.whl
   1: selecting appdirs (1.4.3)
PyPI: Getting info for pytest-metadata (1.7.0) from PyPI
   1: fact: pytest-metadata (1.7.0) depends on pytest (>=2.9.0)
   1: selecting pytest-metadata (1.7.0)
PyPI: Getting info for pyyaml (3.13) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: PyYAML-3.13-cp27-cp27m-win32.whl
   1: selecting pyyaml (3.13)
PyPI: Getting info for django (2.0.7) from PyPI
   1: fact: django (2.0.7) depends on pytz (*)
   1: selecting django (2.0.7)
   1: derived: pytz (*)
PyPI: 91 packages found for pytz *
PyPI: Getting info for ruamel.yaml (0.15.45) from PyPI
   1: selecting ruamel.yaml (0.15.45)
PyPI: Getting info for jsonschema (2.6.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: jsonschema-2.6.0-py2.py3-none-any.whl
   1: selecting jsonschema (2.6.0)
PyPI: Getting info for futures (3.2.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: futures-3.2.0-py2-none-any.whl
   1: fact: futures (3.2.0) requires Python >=2.6, <3
   1: derived: not futures (3.2.0)
PyPI: 20 packages found for futures !=3.2.0
PyPI: Getting info for futures (3.1.1) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: futures-3.1.1-py2-none-any.whl
   1: selecting futures (3.1.1)
PyPI: Getting info for jinja2 (2.10) from PyPI
   1: fact: jinja2 (2.10) depends on MarkupSafe (>=0.23)
   1: selecting jinja2 (2.10)
   1: derived: MarkupSafe (>=0.23)
PyPI: 2 packages found for markupsafe >=0.23
PyPI: Getting info for markupsafe (1.0) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading sdist: MarkupSafe-1.0.tar.gz
   1: selecting markupsafe (1.0)
PyPI: Getting info for colorama (0.3.9) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: colorama-0.3.9-py2.py3-none-any.whl
   1: selecting colorama (0.3.9)
PyPI: Getting info for pytz (2018.5) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: pytz-2018.5-py2.py3-none-any.whl
   1: selecting pytz (2018.5)
PyPI: Getting info for requests (2.19.1) from PyPI
   1: fact: requests (2.19.1) depends on certifi (>=2017.4.17)
   1: fact: requests (2.19.1) depends on urllib3 (>=1.21.1,<1.24)
   1: fact: requests (2.19.1) depends on idna (>=2.5,<2.8)
   1: fact: requests (2.19.1) depends on chardet (>=3.0.2,<3.1.0)
   1: selecting requests (2.19.1)
   1: derived: chardet (>=3.0.2,<3.1.0)
   1: derived: idna (>=2.5,<2.8)
   1: derived: urllib3 (>=1.21.1,<1.24)
   1: derived: certifi (>=2017.4.17)
PyPI: 3 packages found for chardet >=3.0.2,<3.1.0
PyPI: No release information found for idna-0.1, skipping
PyPI: 3 packages found for idna >=2.5,<2.8
PyPI: No release information found for urllib3-0.3, skipping
PyPI: No release information found for urllib3-0.3.1, skipping
PyPI: No release information found for urllib3-0.4.0, skipping
PyPI: No release information found for urllib3-0.4.1, skipping
PyPI: 3 packages found for urllib3 >=1.21.1,<1.24
PyPI: No release information found for certifi-0, skipping
PyPI: 6 packages found for certifi >=2017.4.17
PyPI: Getting info for chardet (3.0.4) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: chardet-3.0.4-py2.py3-none-any.whl
   1: selecting chardet (3.0.4)
PyPI: Getting info for idna (2.7) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: idna-2.7-py2.py3-none-any.whl
   1: selecting idna (2.7)
PyPI: Getting info for urllib3 (1.23) from PyPI
   1: selecting urllib3 (1.23)
PyPI: Getting info for certifi (2018.4.16) from PyPI
PyPI: No dependencies found, downloading archives
PyPI: Downloading wheel: certifi-2018.4.16-py2.py3-none-any.whl
   1: selecting certifi (2018.4.16)
   1: Version solving took 23.961 seconds.
   1: Tried 1 solutions.

Resolution results:

  - markupsafe (1.0)
  - certifi (2018.4.16)
  - chardet (3.0.4)
  - idna (2.7)
  - jinja2 (2.10)
  - six (1.11.0)
  - urllib3 (1.23)
  - atomicwrites (1.1.5)
  - attrs (18.1.0)
  - colorama (0.3.9)
    - platform: win32
  - coreschema (0.0.4)
  - itypes (1.1.0)
  - more-itertools (4.2.0)
  - pluggy (0.6.0)
  - py (1.5.4)
  - requests (2.19.1)
  - uritemplate (3.0.0)
  - coreapi (2.3.3)
  - pytest (3.6.3)
  - pytz (2018.5)
  - appdirs (1.4.3)
  - click (6.7)
  - coverage (4.5.1)
  - django (2.0.7)
  - djangorestframework (3.8.2)
  - future (0.16.0)
  - futures (3.1.1)
  - inflection (0.3.1)
  - jsonschema (2.6.0)
  - mccabe (0.6.1)
  - openapi-codec (1.3.2)
  - pycodestyle (2.3.1)
  - pyflakes (1.6.0)
  - pytest-metadata (1.7.0)
  - pyyaml (3.13)
  - ruamel.yaml (0.15.45)
  - toml (0.9.4)
  - wheel (0.29.0)
  - black (18.6b4)
  - drf-yasg (1.9.1)
  - flake8 (3.5.0)
  - isort (4.3.4)
  - msgpack (0.5.6)
  - pex (1.4.4)
  - pygments (2.2.0)
  - pytest-cov (2.5.1)
  - pytest-django (3.3.3)
  - pytest-html (1.19.0)
  - pytest-mock (1.10.0)
  - swagger-spec-validator (2.3.1)
  - whitenoise (3.3.1)

This is the json in question:
[{'comment_text': '',
  'digests': {'md5': 'f0ad7704b6dc947073398ba290c3517f',
              'sha256': 'ec9ef8f4a9bc6f71eec99e1806bfa2de401650d996c59330782b89a5555c1497'},
  'downloads': -1,
  'filename': 'isort-4.3.4-py2-none-any.whl',
  'has_sig': False,
  'md5_digest': 'f0ad7704b6dc947073398ba290c3517f',
  'packagetype': 'bdist_wheel',
  'python_version': '2.7',
  'size': 45393,
  'upload_time': '2018-02-12T15:06:38',
  'url': 'https://files.pythonhosted.org/packages/41/d8/a945da414f2adc1d9e2f7d6e7445b27f2be42766879062a2e63616ad4199/isort-4.3.4-py2-none-any.whl'},
 {'comment_text': '',
  'digests': {'md5': 'fbaac4cd669ac21ea9e21ab1ea3180db',
              'sha256': '1153601da39a25b14ddc54955dbbacbb6b2d19135386699e2ad58517953b34af'},
  'downloads': -1,
  'filename': 'isort-4.3.4-py3-none-any.whl',
  'has_sig': False,
  'md5_digest': 'fbaac4cd669ac21ea9e21ab1ea3180db',
  'packagetype': 'bdist_wheel',
  'python_version': '3.6',
  'size': 45352,
  'upload_time': '2018-02-12T15:06:20',
  'url': 'https://files.pythonhosted.org/packages/1f/2c/22eee714d7199ae0464beda6ad5fedec8fee6a2f7ffd1e8f1840928fe318/isort-4.3.4-py3-none-any.whl'},
 {'comment_text': '',
  'digests': {'md5': 'fb554e9c8f9aa76e333a03d470a5cf52',
              'sha256': 'b9c40e9750f3d77e6e4d441d8b0266cf555e7cdabdcff33c4fd06366ca761ef8'},
  'downloads': -1,
  'filename': 'isort-4.3.4.tar.gz',
  'has_sig': False,
  'md5_digest': 'fb554e9c8f9aa76e333a03d470a5cf52',
  'packagetype': 'sdist',
  'python_version': 'source',
  'size': 56070,
  'upload_time': '2018-02-12T15:06:16',
  'url': 'https://files.pythonhosted.org/packages/b1/de/a628d16fdba0d38cafb3d7e34d4830f2c9cb3881384ce5c08c44762e1846/isort-4.3.4.tar.gz'}]

From the debug log it enters this part:
https://github.com/sdispater/poetry/blob/490ddf00c3f1c8790399c6ba55b9f4abc9a7f26d/poetry/repositories/pypi_repository.py#L270
It also doesn't register the bdist_wheel in the first run because it continues due to (see above json):
https://github.com/sdispater/poetry/blob/490ddf00c3f1c8790399c6ba55b9f4abc9a7f26d/poetry/repositories/pypi_repository.py#L292
It then continues to just take the first bdist url it finds:
https://github.com/sdispater/poetry/blob/490ddf00c3f1c8790399c6ba55b9f4abc9a7f26d/poetry/repositories/pypi_repository.py#L307-L316
This might be the reason why it works for you.

I can reproduce the issue, I had to clear the cache.
So, to fix this we actually have to pick up a wheel that is compatible with the Python versions declared in pyproject.toml. And if there is none default to the sdist.

What does the sdist help? To quote you:

Poetry never executes the setup.py file for security reasons

How are you going to get the dependencies if you are not executing setup.py to run egg_info or something?
That said; while your proposed solution is a good solution for most cases; it will still fail where a project supports py2 and py3. In this case you'd technically seem to have to pick both wheel files to actually determine all dependencies. Same goes theoretically for py3.3 vs py3.4 etc…

Most sdists have a *.egg-info/requires.txt which contains the raw dependency information.
Also, from inspecting a lot of packages the wheels have all the dependency information regardless of its version compatibility.
In this case it fails because the py2 wheel declares futures as a dependency twice:
Requires-Dist: futures
Requires-Dist: futures; python_version=="2.7"
```

As you can see there is the correct line with the appropriate environment marker but also a "wildcard" dependency. When that happens, Poetry actually merges the constraint leading in this case to `futures (*)`

Yeah, I saw the duplicate futures dependency, do you have any idea where it is coming from? https://github.com/timothycrosley/isort/blob/develop/setup.py looks good… The requires in the sdist also looks good ;)

To be honest, I don't really know. It depends on which tool they use to build their wheels.

Added a POC PR, lets see how it goes (#346 )

I can confirm that 0.11.4 fixes this for me. resolve for isort now uses the sdist istead.


Add deployment process

fixes issue #26

there is a script which can be executed on travis and locally to push a build tag
I documented the deployment process in the developing.md file
tag v0.0.7 was created this way.

When this is merged, we can rename the 2.x branch to a 2.0 branch and every commit to this branch will create a tag and a deployed version on pypi.
@artemrizhov What do you think?

Awesome!


Bad interaction between test files

10:25:30 Failures:
10:25:30
10:25:30   1) Carto::Api::OrganizationUsersController user creation correctly creates a user
10:25:30      Failure/Error: last_user_created.username.should == username
10:25:30      NoMethodError:
10:25:30        undefined method `username' for nil:NilClass
10:25:30      # ./spec/requests/carto/api/organization_users_controller_spec.rb:75:in `block (3 levels) in <top (required)>'
10:25:30
10:25:30   2) Carto::Api::OrganizationUsersController user creation assigns soft_geocoding_limit to false by default
10:25:30      Failure/Error: last_user_created.soft_geocoding_limit.should == false
10:25:30      NoMethodError:
10:25:30        undefined method `soft_geocoding_limit' for nil:NilClass
10:25:30      # ./spec/requests/carto/api/organization_users_controller_spec.rb:94:in `block (3 levels) in <top (required)>'
10:25:30
10:25:30 Finished in 6 minutes 30.02 seconds
10:25:30 258 examples, 2 failures, 1 pending
10:25:30
10:25:30 Failed examples:
10:25:30
10:25:30 rspec ./spec/requests/carto/api/organization_users_controller_spec.rb:62 # Carto::Api::OrganizationUsersController user creation correctly creates a user
10:25:30 rspec ./spec/requests/carto/api/organization_users_controller_spec.rb:81 # Carto::Api::OrganizationUsersController user creation assigns soft_geocoding_limit to false by default
10:25:35 Coverage report generated for specs_15070, specs_18225, specs_24259, specs_24307 to /home/ubuntu/workspace/CartoDB-master-testing/coverage. 16323 / 40027 LOC (40.78%) covered.
10:25:40 make: *** [check-4] Error 1
10:25:40 Build step 'Execute shell' marked build as failure
10:25:40 Finished: FAILURE

How to reproduce:
RAILS_ENV=test bundle exec rspec --fail-fast spec/rspec_configuration.rb spec/requests/carto/api/organization_users_controller_spec.rb spec/requests/carto/api/imports_controller_spec.rb

(similar to what make check-4 does)

Seems to be solved with @rafatower commit


Fix for geolocation/exif data

Two part pull req:

Currently, if the options include geolocation, i.e.:

<preference name="CameraUsesGeolocation" value="true" />

Then the plugin drops into a method that doesn't actually contain any data. This fixes the flow so that data is supplied with geo

This pull req also attaches GPS, Exif, and RAW data to the metadata. Previously, no Exif data was actually written back to the image.

This looks good.  Can you fix the white-space additions?
Also, I don't see you listed on https://people.apache.org/committer-index.html
Can you submit an ICLA? We can pull this with just the whitespace fix, but will need the ICLA for future pulls. details here: http://cordova.apache.org/#contribute

@auser, ping

@auser @purplecabbage when is this issue going to be fixed? I'm happy to redo the pull request if I can be added the list of committers.

@AllenConquest if you have a cla on file then feel free to redo this and send a pr
@auser do you have a cla on file?
http://cordova.apache.org/contribute/contribute_guidelines.html


Provides a Demo Extension

... to combine different services in both server and client sides.

Codecov Report

Merging #14 into master will not change coverage.
The diff coverage is 0%.

@@         Coverage Diff          @@
##           master   #14   +/-   ##
====================================
  Coverage       0%    0%
====================================
  Files           9    10    +1
  Lines         122   130    +8
  Branches        2     3    +1
====================================
- Misses        122   130    +8

Impacted Files
Coverage Δ

rpc/src/main/scala/server/package.scala
0% <ø> (ø)
:arrow_up:

.../main/scala/greeting/service/GreetingService.scala
0% <ø> (ø)

...ng/src/main/scala/greeting/runtime/implicits.scala
0% <0%> (ø)
:arrow_up:

...ng/src/main/scala/greeting/GreetingClientApp.scala
0% <0%> (ø)
:arrow_up:

.../src/main/scala/greeting/service/EchoService.scala
0% <0%> (ø)

Continue to review full report at Codecov.

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


State of Scala 3 support?

Hi there,
I'm strugging to get scala_proto_library rules working with Scala 3, and before I go digging into the errors I'm seeing I wanted to ask in general what the state of Scala 3 support in rules_scala is, especially with regard to scala_proto_library rules? I have noticed that, by default, it looks like the Scala 2.13 libraries are being used for ScalaPB, so I am wondering if this is something that has been tested?
Thanks for your help! ✌
https://github.com/bazelbuild/rules_scala/blob/71d7135808750623b2c9340704a23384de0caefd/third_party/repositories/scala_3_1.bzl#L317-L328

I'll just leave here a set of settings that made scala_proto_library work in a cross-compilation setup.
The goal is basically to define @io_bazel_rules_scala//scala_proto:toolchain_type for each Scala version (controlled by target_setting parameter of toolchain definition).
To define this toolchain we need to declare some dependency providers:

scalapb_worker_deps - for the worker that will invoke scalapbc and generate scala classes from proto files. Worker code is written in 2.13, so dependencies should be of 2.13 version as well.
scalapb_compile_deps - these will be put into a classpath of scala_proto_library
scalapb_grpc_deps - these will also be put into a classpath of scala_proto_library if  with_grpc = True in a toolchain definition

Preparing toolchains
# Some .bzl file

load("@io_bazel_rules_scala//scala:scala_cross_version.bzl", "version_suffix")

scalapb_runtime_213 = [
    ...
]

scalapb_runtime_3 = [
    ...
]

scalapb_worker_213 = [
    # Make sure to include `compilerplugin` dependency
    "@maven//:com_thesamet_scalapb_compilerplugin_2_13",
]

grpc_213 = [
    ...
]

grpc_3 = [
    ...
]

def setup_scala_proto_toolchain(scala_version):
    scala_version_suffix = version_suffix(scala_version)

    scalapb_runtime_deps = scalapb_runtime_213 if scala_version.startswith("2") else scalapb_runtime_3
    grpc_runtime_deps = grpc_213 if scala_version.startswith("2") else grpc_3

    declare_deps_provider(
        name = "scalapb_compile_deps_provider" + scala_version_suffix,
        deps_id = "scalapb_compile_deps",
        visibility = ["//visibility:public"],
        deps = scalapb_runtime_deps + [
            "@io_bazel_rules_scala//scala/private/toolchain_deps:scala_library_classpath",
        ],
    )

    declare_deps_provider(
        name = "scalapb_grpc_deps_provider" + scala_version_suffix,
        deps_id = "scalapb_grpc_deps",
        visibility = ["//visibility:public"],
        deps = grpc_runtime_deps,
    )

    declare_deps_provider(
        name = "scalapb_worker_deps_provider" + scala_version_suffix,
        deps_id = "scalapb_worker_deps",
        visibility = ["//visibility:public"],
        deps = scalapb_worker_213,
    )

    scala_proto_deps_toolchain(
        name = "scala_proto_deps_toolchain_impl" + scala_version_suffix,
        dep_providers = [
            ":scalapb_compile_deps_provider" + scala_version_suffix,
            ":scalapb_grpc_deps_provider" + scala_version_suffix,
            ":scalapb_worker_deps_provider" + scala_version_suffix,
        ],
    )

    native.toolchain(
        name = "scala_proto_deps_toolchain" + scala_version_suffix,
        toolchain = ":scala_proto_deps_toolchain_impl" + scala_version_suffix,
        toolchain_type = "@io_bazel_rules_scala//scala_proto:deps_toolchain_type",
    )

    scala_proto_toolchain(
        name = "scala_proto_toolchain_impl" + scala_version_suffix,
        with_flat_package = False,
        with_grpc = True,
        with_single_line_to_string = False,
    )

    native.toolchain(
        name = "scala_proto_toolchain" + scala_version_suffix,
        target_settings = ["@io_bazel_rules_scala_config//:scala_version" + version_suffix(scala_version)],
        toolchain = "scala_proto_toolchain_impl" + version_suffix(scala_version),
        toolchain_type = "@io_bazel_rules_scala//scala_proto:toolchain_type",
    )

Defining toolchains
# BUILD
load("//your/file_with_proto_setup.bzl", "setup_scala_proto_toolchain")

[
    setup_scala_proto_toolchain(
        scala_version = scala_version,
    )
    for scala_version in SCALA_VERSIONS
]

Registering toolchains
# some .bzl file
def scala_register_proto_toolchains():
        native.register_toolchains(
            "//settings:scala_proto_deps_toolchain" + version_suffix(scala_version),
        )
        native.register_toolchains(
            "//settings:scala_proto_toolchain" + version_suffix(scala_version),
        )

# WORKSPACE
load("...", "scala_register_proto_toolchains()")

scala_register_proto_toolchains()

Testing
After this juggling scala_proto_library should work and respect scala_version param (see cross-compilation docs)


update llama attention casting

updated scaled_dot_product_attention middle cast and removed hard-coded half in llama attention.

changed mid cast behavior in #5100 with its own tests


Add Instructions for using QFSAE Altium Library to README

Added instructions specifically for setting up the JLCPCB library in #12 since we are primarily using that over the QFSAE library this year.


Zooming and Sliding function in V2

in V1, the zoom function is double click and then can slide to right or left. however, in V2, the zoom is alt+mouse, and can't slide once zoom in.
I really like the slide function after zooming in. I don't know if the same function exists in V2. if so, could anyone share an example?
thanks,
Sam

I checked out the new version, with the sliding function without alt key. however, it didn't work. even I setup pan: false. in fact, I checked the LineChart.js and found out the pan value is false by default.

You probably checked v1 then. Here's an example of what you're trying to achieve with v2 : http://codepen.io/anon/pen/JXWavo

I run "npm install n3-charts" and I believe it will retrieve the latest V2, am I right?
also, in my case, there is y2, maybe which caused the issue?

also here, a codepen would greatly help to solve this issue. Maybe start with editing http://codepen.io/chaosmail/pen/zrPJYb
Thanks a lot for filing all the issues, it helps a lot to improve n3-charts

Any updates on this ?

Using latest version (installed manually w/o npm or anything like that) and zoom is not working. Using d3 v3. Found a plunker from this github where zoom is working but when I copied the code into my js & gave it a new html file to work from, it causes several errors & doesn't work. Including the errors below:
Error: datasets.sets[key] is undefined
Error: this.sets[series.dataset] is undefined
TypeError: this._scale is undefined
If anyone has any suggestions or needs further information, contact me at<EMAIL_ADDRESS>Thanks,
-S.K.


add SlingTV and Workiva case studies

@kbarnard10 @KimMcMahon
here are the Sling TV and Workiva case studies!

/approved


Small UX Fix.

"Personal Info" was going off the cliff, just FTFY.

Haven't been able to reproduce the issue. Screenshots?

this is how it looks from here..


fix: ensure tests use staging API to prevent production impact

Date: 13 Nov 2024

Developer Name: @AnujChhikara

Issue Ticket Number

Closes #908

Description
This PR updates the application's test configuration to ensure that all test API requests are directed to the staging environment instead of the production API. This change prevents potential impacts on production behavior during testing.
Changes

Updated API base URL in the test environment to use the staging endpoint.
Modified the loadENV configuration to ensure that the application defaults to the staging API when running on localhost, aligning both local development and test environments with the staging setup.

Documentation Updated?

[ ] Yes
[x] No

Under Feature Flag

[ ] Yes
[x] No

Database Changes

[ ] Yes
[x] No

Breaking Changes

[ ] Yes
[x] No

Development Tested?

[x] Yes
[ ] No

Screenshots

Screenshot 1

Test Coverage

Screenshot 1

Additional Notes

Please resolve merge conflicts


License/ use in research

Hi, I'm interested in using this implementation for a research project. Would that be alright?

Go ahead.
I wrote this for practice when I read the paper. It should only be used as startup code.
If you find any bugs, appreciate if you could contribute back.


[CFP]: Measuring the Business Impact of Open Source

Session Title
Measuring the Business Impact of Open Source
Session Description
As much of the open source story focuses on community and public commons, organizations are not always financially aligned towards these goals alone. Successfully pitching the value of open source to an organization requires a focus beyond the bottom line, as well as identifying the appropriate analogues for your organizational stakeholder. In this talk, we share what we have learned about demonstrating the value of open source, working with stakeholders to identify their needs, and how to define success metrics for open source within an organization.
Benefits to the Ecosystem
Outcomes

Audience will learn about the evolving needs of businesses in relation to their open source organizational life cycle
Audience will walk away with a framework to identify stakeholders to open source in an organization
Audience will get a high level overview of how to define success metrics for open source, along with a few specific use cases which walk through applying the method to demonstrate sample metrics

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.
Becoming Strategic Decision-Making Partner
What level of experience should the audience have to best understand your presentation?
Advanced OSPO (Advanced)
Speaker Name
amanda casari
Speaker Bio
Amanda Casari is an open source scientist in the Open Source Programs Office at Google, where she is co-leading research and engineering to better understand risk and resilience in open source ecosystems. She was named an External Faculty member of the Vermont Complex Systems Center in 2021. Amanda is persistently fascinated by the difference between the systems we aim to create and the ones that emerge, and pie.
Speaker preferred pronouns
she/her

+1 LGTM
On Tue, Dec 21, 2021 at 7:45 AM amcasari @.***> wrote:

Session Title
Measuring the Business Impact of Open Source
Session Description
As much of the open source story focuses on community and public commons,
organizations are not always financially aligned towards these goals alone.
Successfully pitching the value of open source to an organization requires
a focus beyond the bottom line, as well as identifying the appropriate
analogues for your organizational stakeholder. In this talk, we share what
we have learned about demonstrating the value of open source, working with
stakeholders to identify their needs, and how to define success metrics for
open source within an organization.
Benefits to the Ecosystem
Outcomes

Audience will learn about the evolving needs of businesses in
relation to their open source organizational life cycle
Audience will walk away with a framework to identify stakeholders to
open source in an organization
Audience will get a high level overview of how to define success
metrics for open source, along with a few specific use cases which walk
through applying the method to demonstrate sample metrics

Help us narrow down the focus a bit more. Please choose the OSPO related
topic that best describes your proposal.
Becoming Strategic Decision-Making Partner
What level of experience should the audience have to best understand your
presentation?
Advanced OSPO (Advanced)
Speaker Name
amanda casari
Speaker Bio
Amanda Casari is an open source scientist in the Open Source Programs
Office at Google, where she is co-leading research and engineering to
better understand risk and resilience in open source ecosystems. She was
named an External Faculty member of the Vermont Complex Systems Center in
2021. Amanda is persistently fascinated by the difference between the
systems we aim to create and the ones that emerge, and pie.
Speaker preferred pronouns
she/her
—
Reply to this email directly, view it on GitHub
https://github.com/todogroup/ospology/issues/37, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPSII66M5ULUHZHJCRSFLUSCAIXANCNFSM5KQGY3YA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Cheers,
Chris Aniszczyk
https://aniszczyk.org

+1, so interested~


deps: bump stellar-sdk to 8.1.0

Codecov Report

Merging #40 (443c061) into develop (8b88829) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #40   +/-   ##
========================================
  Coverage    79.20%   79.20%
========================================
  Files           12       12
  Lines         2328     2328
========================================
  Hits          1844     1844
  Misses         484      484

Flag
Coverage Δ

unittests
79.20% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


How can I monitor other logical methods in execution in netty http tracing?

Now there is only one span in ui.

if you are using NettyHttpTracing there's currently only a server handler available. When fireChannelRead is fired, a span will be current, which means that you can connect this to something downstream with Tracer.currentSpan. If fireChannelRead results in something run on a netty executor, you might need to wrap that with Tracing.currentTraceContext().
In any case you probably need to describe what precisely you are doing. this netty instrumentation is very low level, there are other netty based tools like ratpack and armeria which have more complete instrumentation


monitor "highres" can't work after update to v0.29

Hyprland Version
Hyprland, built from branch  at commit 0a78f6031c8fcc6773f136fccde3d560aaac239d dirty (). Tag: v0.29.0  flags: (if any) debug
Bug or Regression?
Bug
Description
when set monitor config to:
monitor=,highres,auto,1

it can't enter hyprland
when set monitor config to:
monitor=,1920x1080,auto,1

it work.
Are there something wrong about "highres"?
How to reproduce
1.set monitor config to
monitor=,highres,auto,1

reboot your pc

Crash reports, logs, images, videos
No response

Thanks for the hint. Im also having the same issue.
Hyprland, built from branch main at commit 0a78f6031c8fcc6773f136fccde3d560aaac239d dirty (props: bump ver to 0.29.0). Tag: v0.29.0 flags: (if any)
My config before:
monitor=,preferred,auto,1
Needs to be changed as monitor=,1366x768,auto,1

can you post a crash report

can you post a crash report你能发布一份事故报告吗

I haven't seen any crash report under ~ /. hyprland. This problem is more likely a code logic error, rather than a program crash

send the tty error or hyprland log then

hyprland log:
hyprland.log

everything looks in order, tbh

I'd request a git bisect on this as it's a regression, I can't repro this.

I also have the same problem, my crash log shows:

[LOG] Set a custom mode<EMAIL_ADDRESS>(mode not found in monitor modes)
[LOG] Monitor eDP-1 -> destroyed all render data
The "preferred" refresh rate of my monitor is 120Hz, but this setting previously worked just fine and didn't crash hyprland. The bug was introduced 1-2 days (commits?) before v0.29 I think. As the "highres" setting tends to lower the refresh rate, I guess it has something to do with that.

thats a dupe of #3083 it seems

thats a dupe of #3083 it seems

Unlikely, the patch upstream or reverting wlroots/e85c7905 does not affect this behaviour.

In #3083 Hyprland will abort outright, and this abort is only triggered if you are using a resolution that is not defined by your monitor. But this is not the case here. The event loop is still works normally.
epoll_wait (@epoll_wait:25)
wl_event_loop_dispatch (/usr/src/debug/wayland/wayland-1.22.0/src/event-loop.c:1004)
wl_display_run (/usr/src/debug/wayland/wayland-1.22.0/src/wayland-server.c:1493)
CCompositor::startCompositor() (/home/arthur/src/tmp/hyprland/src/Compositor.cpp:505)
main (/home/arthur/src/tmp/hyprland/src/main.cpp:105)
___lldb_unnamed_symbol3190 (@___lldb_unnamed_symbol3190:29)
__libc_start_main (@__libc_start_main:44)
_start (@_start:15)

This is the summarised behaviour table with different resolution and scaling parameters

resolution
scaling
behaviour

highres
1
freeze

highres
auto
normal

preferred
1
freeze

preferred
auto
normal

defined(e.g. 1920x1080)
1
normal

defined(e.g. 1920x1080)
auto
normal

likely related: #3079
wlroots first bad commit: 717ded9b (currently subproject HEAD)
diff --git a/backend/drm/drm.c b/backend/drm/drm.c
index a012e678..9f9a105b 100644
--- a/backend/drm/drm.c
+++ b/backend/drm/drm.c
@@ -692,11 +692,6 @@ bool drm_connector_commit_state(struct wlr_drm_connector *conn,
 		return false;
 	}

-	if ((base->committed & COMMIT_OUTPUT_STATE) == 0) {
-		// This commit doesn't change the KMS state
-		return true;
-	}
-
 	bool ok = false;
 	struct wlr_drm_connector_state pending = {0};
 	drm_connector_state_init(&pending, conn, base);

can yall check with 423b129b24a0ff14c5e2898a748b916f892cc0b9


[Feature request] Save links from right click menu

It would be nice to be able to save links without opening them first, e.g. by right clicking on them and choosing save via linkding.

Hey @arvaid, #46 adds an entry to the context menu to quick-add a link, and shows a notification when added. I'd really appreciate your thoughts on it!

Thanks, that's great!


Language Issues (Spanish)

Showing HTML codes rather than the actual values. Is this a polyglot issue?

Fixed by #294


Refactor built-in app providers

Fixes #202

Codecov Report

Merging #201 into master will decrease coverage by 0.02%.
The diff coverage is 96.96%.

@@            Coverage Diff            @@
##           master    #201      +/-   ##
=========================================
- Coverage   98.12%   98.1%   -0.03%
=========================================
  Files          24      24
  Lines        1013    1053      +40
  Branches       97     101       +4
=========================================
+ Hits          994    1033      +39
  Misses         11      11
- Partials        8       9       +1

Impacted Files
Coverage Δ

bocadillo/compat.py
100% <100%> (ø)
:arrow_up:

bocadillo/injection.py
100% <100%> (ø)
:arrow_up:

bocadillo/applications.py
98.39% <96.66%> (-0.56%)
:arrow_down:

bocadillo/websockets.py
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Windows Terminal freezes when running npm

Windows Terminal version
1.17.11461.0
Windows build number
10.0.22621.2134
Other Software
No response
Steps to reproduce
Run Windows terminal.
Go to a project that uses npm.
Run npm ci.
Windows terminal freezes.
Expected Behavior
To finish ok.
Actual Behavior
Windows terminal freezes when it reaches a certain dependency.

Can you share a specific project that repros this/? This sounds pretty bad, so I'd be surprised that we'd never heard about it before if it was widespread.
When the Terminal freezes, how does it freeze? Does the output stop, but the rest of the Terminal UI remain responsive? (i.e. can you open other tabs?) Or does the app become fully unresponsive, like when the OS fades the window out and forces you to force-kill it? If it's that second one, a grabbing a dump while it's frozen might be enlightening.
Does this repro on Terminal Preview? I think there were some changes in 1.18 that might help. Can't be sure.

It happens on the vscode-python project.

Duplicate of https://github.com/npm/cli/issues/4028.


[plugin/html] Links are not kept when there is no link text inside

In the html plugin documentation it's write

Note: This returns ALL links from the page so you need to configure some filters to match only to desired content.

http://flexget.com/wiki/Plugins/html#Example
but in the code, links without link text are not kept
for link in soup.find_all('a'):
	# not a valid link
	if not link.has_attr('href'):
		continue
	# no content in the link
	if not link.contents:
		continue

https://github.com/Flexget/Flexget/blob/develop/flexget/plugins/input/html.py#L168
I suggest to remove this part
if not link.contents:
	continue

How is this an issue? And feel free to open a pr

Link like this are not detected

The html plugin was build in order to ignore links that not contains elements used to create a title entry.
For example with a link like that we can't find a title.

The process is logical but not flexible.
I suggest to let the plugin detect this type of link.
Here is my solution https://gist.github.com/revsee65/dc4999f02daaffbe244f391238a8c7a4


Create secure Databricks instance within VNET via terraform

Description
We should create a private Databricks instance within the VNET via terraform in order to securely work with PHI data
Specific Requested resources
We can call it "pitestdatabricks"
Existing Resources?
We already have "phdi_databricks" which is configured as we would want it, but this is for test data, we do not want to intermix test and prod data, and does not exist within the VNET
Additional Context
N/A

(Note from Devops sync just now: we can equivalently secure our resources by means of a separate VNET; this has the added benefit of not consuming precious IP addresses)

Will also need to use ACLs to give access to the storage account.


Added perfromance to exceptions

Signed-off-by: Christian Kreuzberger<EMAIL_ADDRESS>In PR https://github.com/keptn/keptn/pull/3452 I also needed to add performance to exceptions

I tried to address this here: https://github.com/keptn/keptn/blob/master/.github/actions/spelling/patterns.txt#L79
But I botched writing out the typo 🤦


Blocking Improvements

It's neat that you can block with certain weapons like battleaxes and katanas but I feel like with the current implementation, you can have an infinite shield, at least on the 1.12.2 verison.

A different block sound would be nice for the weapons, you could take the unused zombie iron door attack and higher pitch it maybe.
Could change the mechanic to be similar to pre-1.9 where only 50% of damage is negated. If done this way durability does not need to be taken like shields do.

you can have an infinite shield

Are you sure? I was of the impression that it was only a visual.
If it really works and deflects damage, then indeed, your suggestions make sense :)

Interesting. Yes, in that case, some nerfing needs to take place. Just wondering: Which version is that? Probably 1.12.2 or something like that?

Perfect, thanks for the feedback :)
In case you are wondering how I found out: It was not magic - that's just the most popular version before the new textures ;)


setting to bring the selected option to top of list or create grouping based on selected and unselected options

Hi
Can you please include a setting to bring the selected option to top of list or create grouping based on selected and unselected options?
Thanks,
Adhaar

This has been implemented in v2.0.0-beta.1


[BUG] Not able to load eva_giant_patch14_560.m30m_ft_in22k_in1k model

I think there is a split function in the reading of the model name that doesn't read the full name of the model.
To Reproduce
import timm

model = timm.create_model("hf_hub:timm/eva_giant_patch14_560.m30m_ft_in22k_in1k")

Error
RuntimeError: Unknown model (eva_giant_patch14_560)

@MohamedAliRashad you need a version of timm with that model, recent 0.8.x pre-releases / main branch have it.


Problem importing VMware VMs with EFI boot option.

When importing a VMware VM which boots with EFI, the VM in harvester does not start with EFI enabled.  It has to be enabled after the import manually from the VM's Advanced Options.   Can the EFI option be added to the vmware import yaml file?

@bk201 we should may be add this to list of improvements for vm-import-controller for v1.4.0

Duplicated, https://github.com/harvester/harvester/issues/5758


Fix client plugins crashing hoodie server in Windows

In Windows, adding a client plugin as described in http://docs.hood.ie/en/latest/guides/plugins.html will crash hoodie server with error:

Error: Cannot find module 'C:UsersUserdevhoodie-serverhoodieclient'

as backslashes in Windows paths are collapsed when building the string hoodieBundleSource.
The fix replaces backslashes in the client plugins paths with forward slashes, which work both in Linux and Windows.

Thanks David!


Undocumented LogFilter feature

LogFilter supports comma separated values for accept and reject (and possibly wipe) values. However, this feature is not documented. Since this feature isn't stated, it's easy to assume that you'd want to attach multiple filter.accept(..)s onto a log object to achieve the same effect. However, attaching multiple accept filters does the opposite of what you'd think.
If, for example, we had 2 accept log filters, each disjoint from the other, nothing will ever get logged on the given log object.
Here is an example of the undocumented feature in action: https://github.com/apache/trafficserver/blob/master/proxy/config/logging.config.default#L115

Want to suggest an update to
https://docs.trafficserver.apache.org/en/latest/admin-guide/files/logging.config.en.html#admin-custom-logs-filters ?

Yes, after I get a chance to test out the csv feature. Just wanted to make sure this find isn't lost to oblivion if I forget.

Looks like this has been documented


Support generic type modifiers

Fixes #2.

I canceled the duplicative builds (both travis-ci.org and travis-ci.com were running against the repo).


offest can't be higher than max integer value for viewing messages

Get below error when trying to read messages  "Failed to convert property value of type [java.lang.String] to required type [java.lang.Integer] for property offset; nested exception is java.lang.NumberFormatException: For input string: "5659373885" "

Hey @doug2525 , we have some changes coming soon (this week hopefully) that change the internal data type of the offset field inside the MessageInspectorForm class to long, which should solve this.

@michael-pratt That is great!! thanks for the quick response.

@doug2525 We just pushed the latest version of code out on master, give it a try and let us know if it resolves your issue.

@michael-pratt that seems to have corrected the issue. Thanks. Is there a list of updates for this version somewhere?

@michael-pratt I found a bit of an issue with this new version. Any topics that have names that end in .json when you click them to get the topic details it shows json for the topic details. Other topic names seem fine.

Here is an example of what I'm seeing when I click on the topic name

@doug2525 This is a spring artifact. By default it uses the URL to try and determine what content type to send back. With the .json extension on some of your topic URLs, Spring thinks you want JSON back, and we now have endpoints that provide that (previously there was only one mapping).
Can you try adding this snippet in the Kafdrop.java and let me know if it helps?
@Bean
public WebMvcConfigurerAdapter webConfig()
{
   return new WebMvcConfigurerAdapter()
   {
      @Override
      public void configureContentNegotiation(ContentNegotiationConfigurer configurer)
      {
         super.configureContentNegotiation(configurer);
         configurer.favorPathExtension(false);
      }
   };
}

@michael-pratt not much of a java developer so it could be me not doing something correctly but anywhere I add the snippet into the KafDrop.java maven can't resolve the objects.

@doug2525 My guess is you were missing the import statements. You can try this branch if you want:
https://github.com/HomeAdvisor/Kafdrop/tree/json_topic_fix
I tested locally with a test topic that ended in .json and it appears to fix the problem. We'll try and work the permanent fix into an upcoming unit of work, but that branch should work in the meantime.

@michael-pratt ya the import statements did the trick. The issue appears to be resolved with the snippet. Definitely let me know once you have the permanent fix in place and thanks.


[stable/kube-state-metrics] Add variable to optionally set priorityClassName

Signed-off-by: Chris O'Brien<EMAIL_ADDRESS>@fiunchinho
What this PR does / why we need it:
Allow priorityClassName to be set for kube-state-metrics podSpec.
Which issue this PR fixes

fixes #9425

Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @viglesiasce

/lgtm


Check for overlapping components in static fonts

While generated ttf static binaries, Fontmake decompose mixed-composites and merge overlapping contours, but don't do this with overlapping components (for good reasons related to variable fonts I guess).
After the meeting this afternoon, we agreed it would be better to remove overlapping components from source files (mostly because of rendering issues in some environments). Underneath are some of the ressources @arrowtype gave to corroborate this point.
Would be nice if remaining overlapping components in static ttf fonts would raise a WARN in fontbakery.

wikipedia article about rasterizing strategies
https://cdn2.glyphsapp.com/content/2-tutorials/86-creating-a-variable-font/overlaps-before.png
https://cdn2.glyphsapp.com/content/2-tutorials/86-creating-a-variable-font/overlaps-after.png

Can someone (@arrowtype ?) identify specific environments that still have trouble with overlapping contours (presumably because of the use of the even-odd rule)? Or is this just old history that is no longer relevant?

Overlapping contours are still an issue in some environments, that is why we continue to generate static ttf with merged outlines in upstream repositories.
This is a gathering of issues brought up by users:

3D modelling in Affinity Publisher: https://github.com/google/fonts/issues/4818
Outlined contours: https://github.com/google/fonts/issues/4212
macOS Catalina 10.15.6: https://github.com/google/fonts/issues/2602
post script printers: https://github.com/google/fonts/issues/4076

These are issues about overlapped contours, so it applies to overlapped components as well.
Since GF decided to distribute static TTF with overlapping contours for hinting reasons; this should be a warn, not a fail.

@RosaWagner Hi Rosa, I am finding this to be the case on several fonts beyond just Montserrat apart from the single post: https://github.com/googlefonts/Montserrat/tree/master/fonts/ttf to redownload some of the Montserrat fonts.
And you had previously commented about that link I believe:
You can workaround this by downloading a static version of the font with merged contours and self host it: https://github.com/googlefonts/Montserrat/tree/master/fonts/ttf
You said: "Since GF decided to distribute static TTF with overlapping contours for hinting reasons"
So does this mean these static TTF files are available somewhere?
Currently, I am seeing the issue on many other fonts beyond just Montserrat.  Is there a place where one can just download all static/overlapping versions of GF or no?
Thanks!

@RosaWagner Thank you Rosa!  I ended up just using a CSS hack to emulate the stroke which has been working fine for me.  I really appreciate you taking a moment to respond on this. :)


[Blackhole bringup] Pass get_pcie_base_addr_from_device as define for kernels

with IOMMU enabled, this value is generated at runtime and unique per device

@pgkeller get_pcie_base_addr_from_device is determined at runtime and could be unique per device when IOMMU is enabled.
We use this value to compute NOC_XY_PCIE_ENCODING.
We pass this value to device land via NOC_PCIE_ADDR_BASE but this isn't seen by all processors
Related to #9813


Is Non Blocking Retry (@Retryable) intended to be combined with Kafka Transactions (consumer initiated) ?

Discussed in https://github.com/spring-projects/spring-kafka/discussions/2918

Originally posted by PaulFert December  1, 2023
Hello,
I wanted to use both features for consume -> process -> produce applications
When i use Transaction with Blocking Retry, DLT Recover the flow is :

When exception is raised from the listener, the transaction is rollback and then a new transaction is created for the send to DLT, OK fine.
On the oher side, when i use Transaction with Non Blocking Retry the flow is more like that :

When exception is raised from the listener, the transaction is not rollback, the message is send to retry topic and finally the transaction is comited.  If an exception is raised i want my messages out to be not comited.
It's not what i expected, i expected a flow like that :

Did i miss something with the configuration ? I use standard configuration, with one kafkatemplate, with transactional producer
Or maybe did i misunderstood the Non Blocking Retry pattern,  Transactions are not intended to be combined with ?
Sorry for my poor english...
Testing with 'org.springframework.boot' version '3.1.1-SNAPSHOT', spring-kafka version 3.0.8
Thanks

Use @RetryTopic, DeadLetterPublishingRecoverer will inject CommonErrorHandler. RuntimeExceptioncatch byCommonErrorHandler`  in transaction, but not throw RuntimeException again.

exception catch by CommonErrorHandler
https://github.com/spring-projects/spring-kafka/blob/e7e77b9830578d689321acf16b6b57f3c22449de/spring-kafka/src/main/java/org/springframework/kafka/listener/KafkaMessageListenerContainer.java#L2889-L2907

CommonErrorHandler call DeadLetterPublishingRecoverer, see DeadLetterPublishingRecoverer.publish, only log not threw again.
https://github.com/spring-projects/spring-kafka/blob/e7e77b9830578d689321acf16b6b57f3c22449de/spring-kafka/src/main/java/org/springframework/kafka/listener/DeadLetterPublishingRecoverer.java#L684-L706

not use @RetryTopic, will throw exception to transaction and rollback, Then AfterRollbackProcessor catch the exception.
AfterRollbackProcessor also inject DeadLetterPublishingRecoverer

Hi, @artembilan @sobychacko @PaulFert for this scenario(enable listener transaction and retry topic),  retry topic break the kafka transaction atomicity, move retry topic logic to AfterRollbackProcessor feelings can be resolved this question.
WDYT?


Add default behaviour for converting dbt Source nodes into Airflow tasks

As of Cosmos 1.2.1, it does not render dbt Source nodes as Airflow tasks by default.
Since Cosmos 1.2.0, we've introduced support for customizing how the library converts any dbt node into Airflow:
https://astronomer.github.io/astronomer-cosmos/configuration/render-config.html#customizing-how-nodes-are-rendered-experimental
This means users can already customise the desired behaviour for Source nodes, using something like:
https://github.com/astronomer/astronomer-cosmos/blob/11ce2d718483f1d4eb1bfdac659417fb66a1492e/dev/dags/example_cosmos_sources.py#L63
The open questions are:

Do we want Cosmos to have a default behaviour for dbt Source nodes and automatically generate tasks for nodes of this type?
If the answer to (1) is yes, what do we want the behaviour for those nodes to be? Should we run:

dbt source freshness

In addition to freshness checks users can also (and sometimes do) add standard tests to their sources, i.e. unique, not_null, etc. I think a good default behaviour would be to display sources as a task in the Airflow UI as this provides an Airflow DAG to the end user familiar with dbt that is most similar to dbt's DAG, thereby enabling Cosmos adoption. These tasks can use EmptyOperator and therefore have no impact on compute usage or scheduler resources.
One small note, DummyOperator has been deprecated in favour of EmptyOperator in Airflow 2.4 (see here).

+1 to this issue as this is something I'm interested in.

Do we want Cosmos to have a default behaviour for dbt Source nodes and automatically generate tasks for nodes of this type?

I'm in support for having each source render as an Airflow task, and running all tests attached to it. This improves the visibility of a source and whether a model update failure is due to an upstream failure.

If the answer to (1) is yes, what do we want the behaviour for those nodes to be?

dbt test --select source:jaffle_shop.orders
This command should run all the tests associated to a source. I'm not sure how we should handle dbt source freshness though.
Add on questions:
3. How do we handle models that share the same source? Should we render 2 source nodes or should the models share the same source node?

Look like we have a PR https://github.com/astronomer/astronomer-cosmos/pull/661 from @arojasb3 to fix it


Alexa does not finish her outputspeech when shouldendsession is set to false

When I set shouldendsession to false. The response speech was cut off abruptly

I think it's because of this that shouldendsession has been implemented. @renekliment am I wrong?
Why do you want to disable it?
Emerick

I don't know what this is. Closing. Feel free to reopen.


编译安装时报错

Before Asking 在提问之前

[X] I have read the README carefully. 我已经仔细阅读了 README 上的操作指引。

[X] I have pulled the latest code of main branch to run again and the problem still existed. 我已经拉取了主分支上最新的代码，重新运行之后，问题仍不能解决。

Search before asking 先搜索，再提问

[X] I have searched the Data-Juicer issues and found no similar questions. 我已经在 issue列表 中搜索但是没有发现类似的问题。

Question
基于NPU编译安装时出现以下问题，是否是设备问题？
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Installing build dependencies ... done
Running command Getting requirements to build wheel
/tmp/pip-build-env-suyjv95d/overlay/lib/python3.10/site-packages/torch/_subclasses/functional_tensor.py:258: UserWarning: Failed to initialize NumPy: No module named 'numpy' (Triggered internally at /pytorch/torch/csrc/utils/tensor_numpy.cpp:84.)
cpu = _conversion_method_template(device=torch.device("cpu"))
Traceback (most recent call last):
File "/root/miniconda3/envs/datajuicer/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in
main()
File "/root/miniconda3/envs/datajuicer/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/root/miniconda3/envs/datajuicer/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
return hook(config_settings)
File "/tmp/pip-build-env-suyjv95d/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 334, in get_requires_for_build_wheel
return self._get_build_requires(config_settings, requirements=[])
File "/tmp/pip-build-env-suyjv95d/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 304, in _get_build_requires
self.run_setup()
File "/tmp/pip-build-env-suyjv95d/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 320, in run_setup
exec(code, locals())
File "", line 487, in
File "", line 394, in get_vllm_version
RuntimeError: Unknown runtime environment
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
full command: /root/miniconda3/envs/datajuicer/bin/python /root/miniconda3/envs/datajuicer/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py get_requires_for_build_wheel /tmp/tmpf0wp8kc5
cwd: /tmp/pip-install-iwibg5im/vllm_1db146cd6afa4d3cb15da9a4ea4713ac
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Additional 额外信息
No response

Close this stale issue.