[documentation] Please, stop saying everywhere what cargo goes with rust

Many texts on Rust documentations sites misleads newcomers with information on installation of Cargo. I've just built rustc from tarball and started reading https://doc.rust-lang.org/book/ . I know what rustc tarball provides rust-gdb, rustc and rustdoc executables, and when in section https://doc.rust-lang.org/book/crates-and-modules.html I've suddenly encountered mysterious "cargo new phrases" line.
At least following pages saying what "Cargo goes with Rust":
1.
"Cargo comes installed with Rust itself, if you used the official installers."
https://doc.rust-lang.org/book/getting-started.html
2.
"Rust comes with Cargo by default"
https://crates.io/install
This forced Me search rustc tarball contents for Cargo, but no traces of Cargo on the first look (except, as I've discovered farther, of tiny note in readme saying "This install does not include [Cargo]").. So I've had to use ddgo to find rust cargo. Search gave Me this page: http://doc.crates.io/index.html - and there is no fast documentation on how to get cargo tarballs. And I don't want to use Your rustup, to not make garbage in My system because of not using package manager.
I've started searching how to obtain cargo tarballs. Why You, ppl, do not making cargo tarballs? While rustc tarballs goodly enough distributed on https://static.rust-lang.org/dist/ , cargo's https://static.rust-lang.org/cargo-dist/ suddenly replies with 404.

please,

fix documentations;
provide cargo tarballs or include it with rustc tarballs.

The line in Rust's docs says "if you used the official installer." Given that Rust is not in most package ma garment systems yet, it's the suggested way to install Rust.
I do agree that the Cargo docs should use the same phrasing, though.
On Jun 13, 2016, 12:28 +0200<EMAIL_ADDRESS>wrote:

Many texts on Rust documentations sites misleads newcomers with information on installation of Cargo. I've just built rustc from tarball and started readinghttps://doc.rust-lang.org/book/. I know what rustc tarball provides rust-gdb, rustc and rustdoc executables, and when in sectionhttps://doc.rust-lang.org/book/crates-and-modules.htmlI've suddenly encountered mysterious "cargo new phrases" line.
At least following pages saying what "Cargo goes with Rust":
1.
"Cargo comes installed with Rust itself, if you used the official installers."
https://doc.rust-lang.org/book/getting-started.html
2.
"Rust comes with Cargo by default"
https://crates.io/install
This forced Me search rustc tarball contents for Cargo, but no traces of Cargo on the first look (except, as I've discovered farther, of tiny note in readme saying "This install does not include [Cargo]").. So I've had to use ddgo to find rust cargo. Search gave Me this page:http://doc.crates.io/index.html- and there is no fast documentation on how to get cargo tarballs. And I don't want to use Your rustup, to not make garbage in My system because of not using package manager.
I've started searching how to obtain cargo tarballs. Why You, ppl, do not making cargo tarballs? While rustc tarballs goodly enough distributed onhttps://static.rust-lang.org/dist/, cargo'shttps://static.rust-lang.org/cargo-dist/suddenly replies with 404.
please,

fix documentations;
provide cargo tarballs or include it with rustc targalls.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly,view it on GitHub(https://github.com/rust-lang/cargo/issues/2784), ormute the thread(https://github.com/notifications/unsubscribe/AABsio73wEi7G1j8mx9z6obtOQf75Gw3ks5qLTC8gaJpZM4I0MTF).

"if you used the official installer."
Tarballs' "make install" provided by https://static.rust-lang.org/dist/ is official enough, omho.

It's official, but it's not an installer. Those are linked from the
"Install" page.
On Mon, Jun 13, 2016 at 7:26 AM, Alexey<EMAIL_ADDRESS>wrote:

"if you used the official installer."
Tarballs' "make install" provided by https://static.rust-lang.org/dist/
is official enough, omho.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/cargo/issues/2784#issuecomment-225555154,
or mute the thread
https://github.com/notifications/unsubscribe/AABsiqclNYQvSW54IY6EFHDucH3US9rpks5qLT5bgaJpZM4I0MTF
.

Yeah for now the tarballs aren't considered the "official installer" as it's just getting the compiler, not the rest of the ecosystem.

The OP is now gone, and a lot of this has changed. Closing!


Typescript typings. Use polymirphic this.

Enable usage of polymirphic this type if applicable.
Remove /*this*/ comments from places, where this type is not applicable.

Documentation generator fails on this, could someone help?

I feel bad that we didn't help better, but honestly I cannot figure out what the heck is going wrong here. I'm going to close this under the theory that it is abandoned but if you're still interested in working on this please feel free to reopen. Sorry!

I am not close to documentation generator, unfortunatelly. I just migrate typedefinitions to latest version of typescript.


Panic on modules containing an anyref local

Given an input module such as:
(module (func (local anyref)))

this will fail with:
$ cargo run foo.wat
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/wasmtime ./foo.wat`
thread 'main' panicked at 'reference types were found but safepoints were not enabled.', /home/alex/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.56.0/src/regalloc/context.rs:219:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

@yurydelendik is this perhaps a bug in wasmparser where an anyref local is accepted, despite validation not having reference types enabled?

is this perhaps a bug in wasmparser where an anyref local is accepted, despite validation not having reference types enabled?

"reference types were found but safepoints were not enabled" comes from cranelift -- the safepoints needs to be enabled for function with reference types. See also https://github.com/bytecodealliance/cranelift/pull/1073#issuecomment-534955132

That's true yeah, but we shouldn't support reference types at all right now in theory. I would have expected that wasmparser's validation of the module would fail since an anyref local was used, but we didn't enable reference types in the list of features


feat: Add specific needs script to generate RBAC Deamonsets/Node APIs report

Description
This PR adds a script for a script need which generates reports with some criteria based on RBAC
It is stored only in case we need to look for this script in the future.
However, it also might be removed in the long way.

/hold

We need to fix the lint ci.
It only stores the script used to build some specific needs reports so I am moving forward with this one.


Warning: Please use require("history").createBrowserHistory instead of require("history/createBrowserHistory").

Warning: Please use `require("history").createBrowserHistory` instead of `require("history/createBrowserHistory")`. Support for the latter will be removed in the next major release.

Seems to me, that routing module is build as esm but WebPack messes up the serving.
Considering to give a shoot for the WebPack 5

IRC this was merged in the upstream so it should be fixed now.

IRC this was merged in the upstream so it should be fixed now.


What is your roadmap for Cognitive Speech Services?

Hi there! I integrated text-to-speech and speech-to-text into our product and I'm happy with the results. I am especially fond of how many different languages you support and the quality of the speech synthesis is also still quite impressive.
With that being said, I do wonder if there is any place where you share your plans for the future? I check the news page regularly, but it would be really helpful to have an idea of what you are planning to extend on in the coming months. In my case, i'm specifically curious about:

There is some pressure to migrate speech detection to Whisper. I do believe that giving a prompt with the speech recognition is incredibly useful, and so much harder with just phrase lists. I saw that Whisper technology is starting to be used by batch transcription, and i would love to see it in regular speech recognition too. What are your plans here?
Do you have plans do support more languages in your pronunciation assessment? I would love to integrate the service, but it is hard to know if you will eventually extend the supported languages (so that it makes sense for me to build the feature).

Thank you!

Right now Whisper isn't optimized for real-time scenarios that the speech service targets, so there aren't any plans I can share about making it an option for real-time speech.
I've asked someone from our pronunciation assessment team about their language plans.

On a language support, there will be new languages announced soon, with more in development and private preview. If you'd like to reach out directly to the team at<EMAIL_ADDRESS>and ask about particular languages or share ones you'd be interested in.

I'm going to close this as I think the questions have been answered, if not, comment / reopen. Thanks!


xl_chart_type_column_clustered with maximum_scale produces unexpected y axis issue

when using the following code
`
chart_data.categories = titles
chart_data.add_series('percentiles', tuple(values))
chart = slide.shapes.add_chart(
XL_CHART_TYPE.COLUMN_CLUSTERED, x, y, cx, cy, chart_data).chart
v_a = chart.value_axis
v_a.maximum_scale = float(values[8])`
with the following data:
titles [90, 80, 70, 60, 50, 40, 30, 20, 10]
values [271, 887, 1541, 2332, 3188, 4074, 5049, 6299, 19891]
the y axis starts from a negative number
when i am not using the maximum scale, the y axis starts from 0 as it should.

Thanks!

Does the same thing happen when you create a chart like that in PowerPoint by hand?
I note that -109 is 5000 less than 4891, so it's setting 19891 as the top and the other horizontal grid lines 5000 apart.
It strikes me as PowerPoint's idea of the best idea it can figure out to display what you've asked for.
If you want the Y-axis to start at 0, you should tell PowerPoint so using the Axis.minimum_scale property.
I don't see any insubordinate behavior here yet (maybe a little surprising though until you think it through) :)

Well when you say it like that it is logical in some way... :-)
But axis minimum scale doesnt do anything abd hence the problem i was
talking about.
Any idea why minimum scale does not work for me here?
בתאריך 12 בספט׳ 2016 23:09, "Steve Canny"<EMAIL_ADDRESS>כתב:

Does the same thing happen when you create a chart like that in PowerPoint
by hand?
I note that -109 is 5000 less than 4891, so it's setting 19891 as the top
and the other horizontal grid lines 5000 apart.
It strikes me as PowerPoint's idea of the best idea it can figure out to
display what you've asked for.
If you want the Y-axis to start at 0, you should tell PowerPoint so using
the Axis.minimum_scale property.
I don't see any insubordinate behavior here yet (maybe a little surprising
though until you think it through) :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scanny/python-pptx/issues/229#issuecomment-246475229,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANMVatE4kgivk9dhYFdOdhxDZ_RpXPu-ks5qpbFogaJpZM4J298t
.

Ah, now that is interesting :)
Can you produce a chart that looks the way you want by hand in PowerPoint by setting only those max and min values?
If so, an inspection of the XML is likely to be revealing.

well, i will do my best, i never did much with power point itself.
how do i produce the xml for inpection?
shai
On Tue, Sep 13, 2016 at 8:34 AM, Steve Canny<EMAIL_ADDRESS>wrote:

Ah, now that is interesting :)
Can you produce a chart that looks the way you want by hand in PowerPoint
by setting only those max and min values?
If so, an inspection of the XML is likely to be revealing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scanny/python-pptx/issues/229#issuecomment-246579157,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANMVakgolXB_elrRm9V3BFLw3YO28WKAks5qpjXzgaJpZM4J298t
.

It's easy from inside python-pptx. The other way is with opc-diag.
From python-pptx you just get the lxml element for the object in question and then use its .xml property. So say from an axis object:
print axis._element.xml

Using opc-diag would be something like this:
opc browse my-test-file.pptx chart1.xml

But I think in the end you'll find here that python-pptx is setting the XML in the intended way, just that PowerPoint interprets the XML in an unexpected way in this case.
But if you can make one by hand that looks the way you want, one can often discover the hidden mechanism at work by comparing the XML of the python-pptx generated .pptx and the one built by hand.

@thebeancounter: did you get this working?

we decided to plot the graph by creating an image in pyplot and then
pasting it as image in the pptx,
the plotting capabilities are not quite sufficient for what we need right
now.
On Sun, Oct 9, 2016 at 9:11 PM, Steve Canny<EMAIL_ADDRESS>wrote:

@thebeancounter https://github.com/thebeancounter: did you get this
working?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scanny/python-pptx/issues/229#issuecomment-252505886,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANMVantVqF14A0AlYavYtIBbX4jr6iEzks5qyTxLgaJpZM4J298t
.


Update version of jQuery

jQuery is currently being included as a sub-dependency of this component via openregister-picker-engine which includes corejs-typeahead.
As jQuery 3.2.1 has reported medium severity vulnerabilities, jQuery should be updated to the latest version 3.6.0 which has no reported vulnerabilities.
The compiled files in dist/ should then be re-built and a new version released.

Any update on when this change might be approved? We're getting a security alert for this when running ZAP checks on PPT.


[RU] Update of ALTER MODIFY description

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Note: you have not updated your branch.


SAK-50244 Portal site overview blockquoted text does not display

Jira: https://sakaiproject.atlassian.net/browse/SAK-50244

Renaming the variable to "cdnVersion" makes sense to me. New commit incoming soon.


undocumented align_arrays keyword parameter in array.blockwise()

I'm not sure if this is by design or an oversight, but the align_arrays keyword parameter in array.core.blockwise() is missing its docstring.  See this link.
I feel it's useful enough to deserve a description/comment.
Incidentally, there is a description of the same parameter in array.map_overlap() which I think can be copied and pasted into array.core.blockwise().

@ParticularMiner Thanks for catching this! I don't think it is by design, and I agree that the description in map_overlap can be directly copied. :)

Thanks for your reply @pavithraes !
I’ll open a PR.


Implement Proxy-Status HTTP Response Header fields

Description:
Envoy should implement the new Proxy-Status HTTP Response Header.
This new proposal "defines the Proxy-Status HTTP field to convey the details of intermediary response handling, including generated errors." Proxy-Status is meant to be generally applicable to many kinds of proxies. This response header has an error field and a more general details field.
Proposal:
Envoy should generate and attach this new header to traffic.
Implementing this new web standard will help people who use Envoy (and people who use tools which use Envoy) better understand the state of each intermediate proxy along a connection.
Some notes:

I don't have an opinion w/r/t whether it is enabled or disabled by default.
I do not think that this enum should replace any existing Envoy-internal error enums.
The RFC is expected to be approved with minimal content changes within the next few weeks. We should not submit any changes until it is approved.
I'm not sure whether or not we want to populate the details field with Envoy's existing response code status details. This might be useful.

One simple implementation would be to provide a translation mapping from ResponseFlag to Proxy-Status error, as in the table below.

ResponseFlag
Proxy-Status

FailedLocalHealthCheck = 0x1
2.3.4. destination_unavailable

NoHealthyUpstream = 0x2
2.3.4. destination_unavailable

UpstreamRequestTimeout = 0x4
2.3.9. connection_timeout

LocalReset = 0x8
(this probably needs to be traced back to the original reason)

UpstreamRemoteReset = 0x10
2.3.8. connection_terminated

UpstreamConnectionFailure = 0x20
2.3.7. connection_refused

UpstreamConnectionTermination = 0x40
2.3.8. connection_terminated

UpstreamOverflow = 0x80
2.3.12. connection_limit_reached

NoRouteFound = 0x100
2.3.6. destination_not_found

DelayInjected = 0x200
?

FaultInjected = 0x400
?

RateLimited = 0x800
2.3.12. connection_limit_reached

UnauthorizedExternalService = 0x1000
?

RateLimitServiceError = 0x2000
2.3.12. connection_limit_reached

DownstreamConnectionTermination = 0x4000
2.3.8. connection_terminated

UpstreamRetryLimitExceeded = 0x8000
2.3.7. connection_refused

StreamIdleTimeout = 0x10000
2.3.26. http_response_timeout

InvalidEnvoyRequestHeaders = 0x20000
2.3.16. http_request_error

DownstreamProtocolError = 0x40000
2.3.16. http_request_error or 2.3.28. http_protocol_error

UpstreamMaxStreamDurationReached = 0x80000
2.3.26. http_response_timeout

ResponseFromCacheFilter = 0x100000
?

NoFilterConfigFound = 0x200000
2.3.31. proxy_configuration_error or 2.3.30. proxy_internal_error

DurationTimeout = 0x400000
?

UpstreamProtocolError = 0x800000
2.3.28 http_protocol_error

NoClusterFound = 0x1000000
2.3.6 destination_ip_unroutable

LastFlag = NoClusterFound
n/a

One caveat: ReponseFlag is a bit field, and responses can have multiple flags set. Proxy-Status is not a bit field. We might need to look at different situations where we have many bits set and decide which of them to use when generating a Proxy-Status header.

I think something like this can be implemented as an encoder filter to add this header in the encodeHeaders callback based on the response flag in the StreamInfo.
I think there might be some cases where this filter is bypassed, such as buffer overflow triggered by some other encoder filter.

@mattklein123 @alyssawilk for any comments

It can be a filter, but if it's effectively an RFC standard for how proxies should behave, there's a case to be made for putting it in HCM. I've tended to advocate that we push more out of HCM over time, but this is so trivial (it's just a map from response flags to header), it feels to me like batteries included, and @yanavlasov makes the point that there are paths that might bypass if it's a regular filter.

I think optional HCM is fine. ideally we should configure it so one can send the set either simple status, or send response code details in the details field for rich debug info.

Hi folks, I have an impl PR for this proposal in https://github.com/envoyproxy/envoy/pull/17638. PTAL.


[BUG]: In iOS, seek is working perfect in portrait mode but when i rotate my device in landscape then on seek i am getting JSON value '0' of type NSNumber cannot be converted to NSDictionary

Version
v5 (Stable)
What platforms are you having the problem on?
iOS
Architecture
Old architecture
What happened?
I am working on project which includes video player, orientation and many more integrations. In portrait mode when i click on seek then it's working fine but when in rotate my device in landscape and then try to seek then i am getting JSON value '0' of type NSNumber cannot be converted to NSDictionary and app get crashed.
ref.current.seek(parseInt(progress.currentTime) - 10);
this is my code for backword which works fine in android in both modes but in iOS it's getting crashed in landscape mode
Reproduction
Step to reproduce this bug are:
Open app-> go to play list -> click on any video -> click on rotate device -> click on seek (forword/backword) . It's getting crashed

Hey @GuruReactDev, cloud you check if this issue is also in v6 (beta) ?

I tried v6(beta) but here i am getting error before app splash screen.

Hey @GuruReactDev, if I forcefully change the orientation of the app and play a video in fullscreen, it still remains in portrait mode. It should remain landscape. I'm facing this issue on the iOS side. If you have any clues, please suggest them to me.

Hey @GuruReactDev, if I forcefully change the orientation of the app and play a video in fullscreen, it still remains in portrait mode. It should remain landscape. I'm facing this issue on the iOS side. If you have any clues, please suggest them to me.

@CodeBrewLabs7 i am facing the same issue with orientation in iOS and trying to find a way to do it but didn't find any solution yet

I wasn't able to reproduce issue with seek and with installation on v6

Hey @GuruReactDev, cloud you check if this issue is also in v6 (beta) ?

I am build a TV app that uses React Native Video testing in Android, having issues, with the seek operation.
On V5 after some seek operations, the video freezes and the audio continues.
On V6 after some seek operations, the frame jumps back then forward, creating some distortions on the image.
On V6 works everything well on the Android Emulator, but on real AndroidTV this issues happen.
I will be opening a ticket with more information.

I wasn't able to reproduce issue with seek and with installation on v6

I have installed this packages in my project, Maybe any package conflict
"dependencies": { "@joaosousa/react-native-progress-steps": "^0.4.0", "@miblanchard/react-native-slider": "^2.2.0", "@react-native-async-storage/async-storage": "^1.17.11", "@react-native-camera-roll/camera-roll": "^7.4.1", "@react-native-clipboard/clipboard": "^1.11.1", "@react-native-community/netinfo": "^9.3.7", "@react-navigation/native": "^6.1.1", "@react-navigation/native-stack": "^6.9.7", "apisauce": "^2.1.6", "lodash": "^4.17.21", "moment": "^2.29.4", "react": "18.1.0", "react-native": "0.70.6", "react-native-awesome-alerts": "^2.0.0", "react-native-calendars": "^1.1293.0", "react-native-circular-progress-indicator": "^4.4.2", "react-native-device-info": "^10.3.0", "react-native-document-picker": "^8.1.3", "react-native-gesture-handler": "^2.9.0", "react-native-image-picker": "^5.0.2", "react-native-indicators": "^0.17.0", "react-native-keyboard-aware-scroll-view": "^0.9.5", "react-native-keyboard-aware-view": "^0.0.14", "react-native-linear-gradient": "^2.6.2", "react-native-orientation-locker": "^1.6.0", "react-native-pell-rich-editor": "^1.9.0", "react-native-popover-view": "^5.1.7", "react-native-progress": "^5.0.1", "react-native-progress-steps": "^1.3.4", "react-native-reanimated": "^2.14.4", "react-native-reanimated-carousel": "^3.3.0", "react-native-render-html": "^6.3.4", "react-native-responsive-dimensions": "^3.1.1", "react-native-responsive-screen": "^1.4.2", "react-native-safe-area-context": "^4.4.1", "react-native-screens": "^3.18.2", "react-native-step-indicator": "^1.0.3", "react-native-svg": "^15.0.0", "react-native-toast-message": "^2.2.0", "react-native-vector-icons": "^9.2.0", "react-native-video": "^5.2.1", "react-native-video-controls": "^2.8.1", "react-native-video-player": "^0.14.0", "react-native-view-pdf": "^0.14.0", "react-native-walkthrough-tooltip": "^1.5.0", "react-native-webview": "^13.6.2", "react-native-youtube-iframe": "^2.3.0", "rn-fetch-blob": "^0.12.0" }, "devDependencies": { "@babel/core": "^7.12.9", "@babel/runtime": "^7.12.5", "@react-native-community/eslint-config": "^2.0.0", "babel-jest": "^26.6.3", "eslint": "^7.32.0", "jest": "^26.6.3", "metro-react-native-babel-preset": "0.72.3", "react-test-renderer": "18.1.0" },

Hey @GuruReactDev, cloud you check if this issue is also in v6 (beta) ?

I am build a TV app that uses React Native Video testing in Android, having issues, with the seek operation. On V5 after some seek operations, the video freezes and the audio continues. On V6 after some seek operations, the frame jumps back then forward, creating some distortions on the image.
On V6 works everything well on the Android Emulator, but on real AndroidTV this issues happen.
I will be opening a ticket with more information.

I had similar issue yesterday on a real device. I fixed it by disabling texture View:
useTextureView={false}
Let me know if it is better with that please ?

@GuruReactDev were you able to upgrade to V6.0.0 ?


Actions defaults to enabled=false

I have updated to 2.1.0 recently and im experiencing that some actions not enabled by default.
This means i immediately get an error notEnabled, but the work factory seems to execute. Theres never a call back to my subscription on elements.
I looked around in the recent changes and this seems peculiar:
    public init(
        enabledIf: Observable<Bool> = Observable.just(true),
        workFactory: @escaping WorkFactory) {

        self._enabledIf = enabledIf
        self.workFactory = workFactory

        let enabledSubject = BehaviorSubject<Bool>(value: false)
        enabled = enabledSubject.asObservable()

I'm not 100% sure whats going on, but it seems to me _enabledIf defaults true and enabled defaults to false?

Hi @floskel,
As the test case indicates, the default value of enabled is true.
The initial value false of enabledSubject means that disable action until enableIf receives true. So if enabledIf is Observable.just(true), the initial value is true. It is derived from combineLatest(executing, enabledIf) { !$0 && $1 }.
let enabledSubject = BehaviorSubject<Bool>(value: false)
enabled = enabledSubject.asObservable()

...

executing = Observable
    .of(executionStart.map { _ in true }, executionEnd.map { _ in false })
    .merge()
    .startWith(false)

Observable
    .combineLatest(executing, enabledIf) { !$0 && $1 }
    .bindTo(enabledSubject)
    .addDisposableTo(disposeBag)

However, you're experiencing weird behavior of Action actually.
I'd happy to find out what's happening.
Could you tell me more detail of the situation?

enabledIf and workFactory of initializer
Executed via execute() or inputs
debug() of executing, enabled and elements.

In addition, please push a test case that reproduces this issue to some branch if you could.

Yes, makes more sense. I will look into replicating the issue.

I'm also seeing a similar issue with an Action in our codebase after updating from 2.0.0 to 2.1.x, including the current HEAD of the repo... I instrumented the action in question a bit, and here's the debug output I ended up with:
2017-01-05 11:53:51.273: enabled -> subscribed
2017-01-05 11:53:51.273: enabled -> Event next(true)
2017-01-05 11:53:51.274: inputs -> subscribed

** tapped button here  **

2017-01-05 11:53:55.239: enabled -> Event next(false)

** log output generated by work factory being invoked here **

2017-01-05 11:53:55.247: inputs -> Event next([...])

Note that enabled goes to false before we see the .next from inputs, and yet the workFactory is invoked in between the two... I'm not entirely sure where to go from here, but happy to help if I can.

Worth noting that I do see an element emitted on elements as a result of the work factory being executed. I've also just verified that this occurs with both RxSwift 3.0.1 and 3.1.0.

Confirming that 2.2.1 has fixed the issues i experienced. Appreciate the good work!


[ENH] Built-in job scheduling in runners

Is there an existing issue for this?

[X] I have searched the existing issues

New feature

Somewhat related to #227
Add a flag to nipoppy run (and nipoppy bidsify) which will make it submit jobs instead of actually launching Boutiques
Look into using https://github.com/pyiron/pysqa which seems to support both Slurm and SGE. Based on Jinja templates and should have some flexibility

Unclear documentation
No response

@jacobsanz97

:)

Add an init argument hpc in BasePipelineRunner (here) and store it as instance attribute

Modify run_main() to have different behaviour if flagged
https://github.com/nipoppy/nipoppy/blob/379ace12e40369af0655670a63553cad942a2d50/nipoppy/workflows/pipeline.py#L394-L408
^ only do above if hpc is False

If hpc is True, call PySQA

Jinja templates should be stored here, in hpc_templates

On nipoppy init (nipoppy/workflows/dataset_init.py), copy the Jinja template files to <DATASET_ROOT>/proc/hpc_templates

Update ProcPipelineConfig (here) to have HPC_CONFIG field which will be a dict[str, Any]

Add test(s) with mocker checking for PySQA call: https://github.com/nipoppy/nipoppy/blob/main/tests/test_workflow_pipeline.py


Fixes inline link for Controbitors in Readme

I just noticed the link wasn't working for contributors (I assume because of the emoji).

Thanks @sneakycrow!


fix issue #30, take care of uppercase

I'm not sure about why we use this function to compare:
/**
 * This function uses case-sensitive logic if a second argument has an upper case. Otherwise, uses case-insensitive logic.
 */
export function caseIncludes(one: string, other: string): boolean {
  const lowerOther = other.toLowerCase();
  return lowerOther === other
    ? one.toLowerCase().includes(lowerOther)
    : one.includes(other);
}

I think it will get some confused results, for example in demo gif:

When we input a word in lowercase, some capitalized candidate will come out, that's usually not we wanted.
A consistent behavior is, when we input capitalized prefix, candidates should be all in capitalized, when we input lowercase prefix, candidates should be in lowercase prefix. Make candidate list short and accurate will help on speed up input.
Maybe others may have different preference on this, so adding an option is also helpful.

In my local, I actually change caseIncludes to this:
export function caseIncludes(one: string, other: string): boolean {
    return one.startsWith(other);
}

This will complete in strict prefix.
Otherwise, we may have such kind of scenario:
I input a prefix some', candidate list contains 'handsome', I only want words starting with some` ...
Any special reason we use includes instead of startwith?

I'm not sure about why we use this function to compare:

Because I am inspired by Vim search mode. Vim search works as the caseIncludes function.
On the other hand, This plugin is for complements, not search. There are many different complements logics, but famous editors and IDEs suggest first what we input. (ex: a -> [aaa, AAA], A -> [AAA, aaa])
However, Obsidian is not IDE for a coder. Therefore, I think it would be suitable as you said.

Maybe others may have different preference on this, so adding an option is also helpful.

I agree. It is a bit of another issue, so I might implement it after merging your PR.

Any special reason we use includes instead of startwith?

I think it depends on how we use it or who uses it.
However, now I think they might be noisy in most cases. So I'll try it soon, thanks! :)

By the way, this issue includes breaking changes as I didn't expected. So I'll merge it and then release v3.0.0 :)

I'm not sure about why we use this function to compare:

Because I am inspired by Vim search mode. Vim search works as the caseIncludes function.
On the other hand, This plugin is for complements, not search. There are many different complements logics, but famous editors and IDEs suggest first what we input. (ex: a -> [aaa, AAA], A -> [AAA, aaa])
However, Obsidian is not IDE for a coder. Therefore, I think it would be suitable as you said.

Maybe others may have different preference on this, so adding an option is also helpful.

I agree. It is a bit of another issue, so I might implement it after merging your PR.

Yes, if we want to execute a command line, fuzzy search is fine. Like VSCode, it also use 'includes' to match:

If we use to typing text, strict prefix matching will be better.

As an exception, It would be better for Internal Link Search to use insensitive-match. (at least in my case..)

As an exception, It would be better for Internal Link Search to use insensitive-match. (at least in my case..)

Yes, in this scenario it may useful. But I think we can control it only do fuzzy match if word is internal link, starts with [[.


Encode nil slices as empty arrays

By default, the json package marshals zero-valued (nil) slices as null, whereas merely empty slices are marshalled as []:
var s []int
json.Marshal(s) // -> null
s = []int{}
json.Marshal(s) // -> []

If the JSON is later consumed by a Go client, this generally isn't an issue, since both null and [] will be decoded as a slice with no elements, and Go code typically doesn't distinguish between nil and empty slices. However, clients in other languages may choke on null, e.g.:
let arr = request(endpoint)
let len = arr.length // invalid if arr === null

To avoid this, zero-valued slices should be replaced with empty slices prior to encoding. There are a few ways to do this, but unfortunately none of them are trivial. Perhaps the best approach for Rosetta would be to use a JSON codegen tool such as easyjson, which supports a NilSliceAsEmpty option. This would also improve encoding/decoding performance.

Thanks for posting this issue @lukechampine. Definitely something we need to fix!

Read more


[WIP] Spectral normalization layer

Implements SpectralNormalization layer [1].
This is still work in progress, but would be great to get some feedback on this. Things that still need to be done:

[ ] Make sure that the data shapes and axes are handled correctly
[ ] Make sure that the u and layer.kernel assignments are handled correctly
[ ] Test the wrapper

[1] Miyato, T., Kataoka, T., Koyama, M., & Yoshida, Y. (2018). Spectral normalization for generative adversarial networks. arXiv preprint arXiv:1802.05957.

Hey @hartikainen thanks for the contribution. The code looks great so far. Just a reminder, you'll need to update BUILD, __init__.py and README.md as well.

How about the spectral normalization implementation that is in tf-gan? https://github.com/tensorflow/gan/blob/master/tensorflow_gan/python/features/spectral_normalization.py

How about the spectral normalization implementation that is in tf-gan? https://github.com/tensorflow/gan/blob/master/tensorflow_gan/python/features/spectral_normalization.py
I think that implementation is straight forward compatible with tf.keras layers and also tf2.0
What happened with this PR?

Closing as this pull request had no activity for a while.


Testing coveralls fix

This pull request tests the fix for coveralls to return the coverage status after each PR

Coverage increased (+0.05%) to 29.185% when pulling 28f0f0574c45cbd468d4a1103280ba0d4530334d on feature/testing-coveralls into b70b3d1296c9519046a91048b202426f253f9ad5 on develop.

Coverage increased (+0.05%) to 29.185% when pulling 28f0f0574c45cbd468d4a1103280ba0d4530334d on feature/testing-coveralls into b70b3d1296c9519046a91048b202426f253f9ad5 on develop.


Error when install numba by pip

I have the following error when trying to install by pip install numba on Ubuntu 16.04. Could you show me how to fix it.
  ERROR: Command errored out with exit status 1:
   command: /usr/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-eulNd9/llvmlite/setup.py'"'"'; __file__='"'"'/tmp/pip-install-eulNd9/llvmlite/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-U3yvuq
       cwd: /tmp/pip-install-eulNd9/llvmlite/
  Complete output (7 lines):
  running bdist_wheel
  /usr/bin/python /tmp/pip-install-eulNd9/llvmlite/ffi/build.py
    File "/tmp/pip-install-eulNd9/llvmlite/ffi/build.py", line 122
      raise ValueError(msg.format(_ver_check_skip)) from e
                                                       ^
  SyntaxError: invalid syntax
  error: command '/usr/bin/python' failed with exit status 1
  ----------------------------------------
  ERROR: Failed building wheel for llvmlite
  Running setup.py clean for llvmlite
Failed to build llvmlite
Installing collected packages: llvmlite, numba
    Running setup.py install for llvmlite ... error
    ERROR: Command errored out with exit status 1:
     command: /usr/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-eulNd9/llvmlite/setup.py'"'"'; __file__='"'"'/tmp/pip-install-eulNd9/llvmlite/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-rUBf7g/install-record.txt --single-version-externally-managed --user --prefix= --compile --install-headers /home/lva/.local/include/python2.7/llvmlite
         cwd: /tmp/pip-install-eulNd9/llvmlite/
    Complete output (10 lines):
    running install
    running build
    got version from file /tmp/pip-install-eulNd9/llvmlite/llvmlite/_version.py {'version': '0.32.1', 'full': 'aa11b129c0b55973067422397821ae6d44fa5e70'}
    running build_ext
    /usr/bin/python /tmp/pip-install-eulNd9/llvmlite/ffi/build.py
      File "/tmp/pip-install-eulNd9/llvmlite/ffi/build.py", line 122
        raise ValueError(msg.format(_ver_check_skip)) from e
                                                         ^
    SyntaxError: invalid syntax
    error: command '/usr/bin/python' failed with exit status 1
    ----------------------------------------
ERROR: Command errored out with exit status 1: /usr/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-eulNd9/llvmlite/setup.py'"'"'; __file__='"'"'/tmp/pip-install-eulNd9/llvmlite/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-rUBf7g/install-record.txt --single-version-externally-managed --user --prefix= --compile --install-headers /home/lva/.local/include/python2.7/llvmlite Check the logs for full command output.

Thanks for the report. The latest Numba requires Python >= 3.6. I would guess that your system Python is 2.7 as it doesn't support the raise <Exception> from <Exception> syntax (Introduced in PEP 3134, here https://www.python.org/dev/peps/pep-3134/#explicit-exception-chaining). I'd suggest getting newer version of Python, which is >= 3.6, would solve your problems. If this isn't possible, the last version of Numba that supports Python 2.7 is Numba version 0.48, explicitly installing this could also work but you'd miss new features.

@stuartarchibald Wouldn't it be better if the error message would say exactly what you said instead of failing with a syntax error?

@alexkreimer yes, definitely, @eric-wieser also suggested similar (but can't find a xref) as IIRC NumPy did something along these lines and then switched to explicit rejection of unsupported pythons. Pull requests are welcomed.
Thanks.

The relevant numpy commit is https://github.com/numpy/numpy/commit/dabf31c74f6f3153ef4e7c72ad969c37f8652c8a#diff-2eeaed663bd0d25b7e608891384b7298

unable to uninstall numba on ubuntu 18.04

@arjunskumar thank you for adding to this issue. Since this issue has been closed and resolved, please do open a new issue with the details of your problem:
a) What did you do?
b) What did you expect to happen?
c) What happened instead?
And please include relevant commands and any tool output of error messages that you encounter, thanks.

@esc I was trying to run Voxelnet ROS package. Numba was one of the package dependencies.
My python version is 3.6.9 so run
pip3 install numba
add encountered with this error  "Failed building wheel for numba"
As per my understanding numba depends on llvmlite, I was able to install llvmlite 0.32.0 version separately but when installing numba it creates problem.

@arjunskumar as I wrote above: please open a new issue.

Collecting numba
Using cached numba-0.51.2.tar.gz (2.1 MB)
Requirement already satisfied: numpy>=1.15 in c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\site-packages (from numba) (1.19.4)
Requirement already satisfied: setuptools in c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\site-packages (from numba) (51.0.0)
Collecting llvmlite<0.35,>=0.34.0.dev0
Using cached llvmlite-0.34.0.tar.gz (107 kB)
Building wheels for collected packages: numba, llvmlite
** On entry to DGEBAL parameter number  3 had an illegal value
** On entry to DGEHRD  parameter number  2 had an illegal value
** On entry to DORGHR DORGQR parameter number  2 had an illegal value
** On entry to DHSEQR parameter number  4 had an illegal value
Building wheel for numba (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: 'c:\users\abhiram shetty\appdata\local\programs\python\python39\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0\setup.py'"'"'; file='"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d 'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-wheel-3ecop48g'
cwd: C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0
Complete output (11 lines):
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0\setup.py", line 354, in
metadata['ext_modules'] = get_ext_modules()
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0\setup.py", line 87, in get_ext_modules
import numpy.distutils.misc_util as np_misc
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\site-packages\numpy_init_.py", line 305, in
win_os_check()
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\site-packages\numpy_init.py", line 302, in _win_os_check
raise RuntimeError(msg.format(file)) from None
RuntimeError: The current Numpy installation ('c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\site-packages\numpy\init.py') fails to pass a sanity check due to a bug in the windows runtime. See this issue for more information: https://tinyurl.com/y3dm3h86
ERROR: Failed building wheel for numba
Running setup.py clean for numba
** On entry to DGEBAL parameter number  3 had an illegal value
** On entry to DGEHRD  parameter number  2 had an illegal value
** On entry to DORGHR DORGQR parameter number  2 had an illegal value
** On entry to DHSEQR parameter number  4 had an illegal value
ERROR: Command errored out with exit status 1:
command: 'c:\users\abhiram shetty\appdata\local\programs\python\python39\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0\setup.py'"'"'; file='"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' clean --all
cwd: C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0
Complete output (11 lines):
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0\setup.py", line 354, in
metadata['ext_modules'] = get_ext_modules()
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\numba_0261f68d3cdd4dddaf6b2c592c3e42b0\setup.py", line 87, in get_ext_modules
import numpy.distutils.misc_util as np_misc
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\site-packages\numpy_init_.py", line 305, in
win_os_check()
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\site-packages\numpy_init.py", line 302, in _win_os_check
raise RuntimeError(msg.format(file)) from None
RuntimeError: The current Numpy installation ('c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\site-packages\numpy\init.py') fails to pass a sanity check due to a bug in the windows runtime. See this issue for more information: https://tinyurl.com/y3dm3h86
ERROR: Failed cleaning build dir for numba
Building wheel for llvmlite (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: 'c:\users\abhiram shetty\appdata\local\programs\python\python39\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\setup.py'"'"'; file='"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d 'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-wheel-k7jqb0y5'
cwd: C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6
Complete output (24 lines):
running bdist_wheel
c:\users\abhiram shetty\appdata\local\programs\python\python39\python.exe C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py
Trying generator 'Visual Studio 15 2017 Win64'
Traceback (most recent call last):
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 191, in
main()
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 179, in main
main_win32()
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 88, in main_win32
generator = find_win32_generator()
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 76, in find_win32_generator
try_cmake(cmake_dir, build_dir, generator)
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 28, in try_cmake
subprocess.check_call(['cmake', '-G', generator, cmake_dir])
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\subprocess.py", line 368, in check_call
retcode = call(*popenargs, **kwargs)
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\subprocess.py", line 349, in call
with Popen(*popenargs, **kwargs) as p:
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\subprocess.py", line 947, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
error: command 'c:\users\abhiram shetty\appdata\local\programs\python\python39\python.exe' failed with exit code 1
ERROR: Failed building wheel for llvmlite
Running setup.py clean for llvmlite
Failed to build numba llvmlite
Installing collected packages: llvmlite, numba
Running setup.py install for llvmlite ... error
ERROR: Command errored out with exit status 1:
command: 'c:\users\abhiram shetty\appdata\local\programs\python\python39\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\setup.py'"'"'; file='"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record 'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-record-384f6zsx\install-record.txt' --single-version-externally-managed --compile --install-headers 'c:\users\abhiram shetty\appdata\local\programs\python\python39\Include\llvmlite'
cwd: C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6
Complete output (27 lines):
running install
running build
got version from file C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\llvmlite/_version.py {'version':
'0.34.0', 'full': 'c5889c9e98c6b19d5d85ebdd982d64a03931f8e2'}
running build_ext
c:\users\abhiram shetty\appdata\local\programs\python\python39\python.exe C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py
Trying generator 'Visual Studio 15 2017 Win64'
Traceback (most recent call last):
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 191, in
main()
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 179, in main
main_win32()
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 88, in main_win32
generator = find_win32_generator()
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 76, in find_win32_generator        try_cmake(cmake_dir, build_dir, generator)
File "C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\ffi\build.py", line 28, in try_cmake
subprocess.check_call(['cmake', '-G', generator, cmake_dir])
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\subprocess.py", line 368, in check_call
retcode = call(*popenargs, **kwargs)
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\subprocess.py", line 349, in call
with Popen(*popenargs, **kwargs) as p:
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\subprocess.py", line 947, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "c:\users\abhiram shetty\appdata\local\programs\python\python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
error: command 'c:\users\abhiram shetty\appdata\local\programs\python\python39\python.exe' failed with exit code 1
----------------------------------------
ERROR: Command errored out with exit status 1: 'c:\users\abhiram shetty\appdata\local\programs\python\python39\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\setup.py'"'"'; file='"'"'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-install-npqmg67r\llvmlite_8a3a37d3d0dd4fe2a83f6f0abd50c1a6\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record 'C:\Users\Abhiram Shetty\AppData\Local\Temp\pip-record-384f6zsx\install-record.txt' --single-version-externally-managed --compile --install-headers 'c:\users\abhiram shetty\appdata\local\programs\python\python39\Include\llvmlite' Check the logs for full command output.

@Aldurine thank you for submitting this. I can see from the log that you are trying to install Numba on Python 3.9 -- however, this Python version is currently not supported. Please try to use 3.6/3.7/3.8. Thank you for using Numba.

I have tried this to solve this issue.
$pip install wheel (or pip3 install wheel)
This made some more progress.  But the final solution I found was below.
$sudo apt install python3-numba


Specify "not final evolution" for all Gen 9 pokemon

Marks all new and returning pokemon with the nfe attribute.  This is required for eviolite to function correctly.

thanks


Validation error of type FieldUndefined: Field 'syncNotes' in type 'Query' is undefined @ 'syncNotes'

I followed every steps on https://amplify.aws/learn/courses/Fullstack-for-Frontend-Developers-e7319/lessons/8, note list is empty.
Graphql post request's reqsponse is:
{
    "data": null,
    "errors": [
        {
            "path": null,
            "locations": [
                {
                    "line": 1,
                    "column": 61,
                    "sourceName": null
                }
            ],
            "message": "Validation error of type UnknownType: Unknown type AWSTimestamp"
        },
        {
            "path": null,
            "locations": [
                {
                    "line": 2,
                    "column": 3,
                    "sourceName": null
                }
            ],
            "message": "Validation error of type FieldUndefined: Field 'syncNotes' in type 'Query' is undefined @ 'syncNotes'"
        }
    ]
}

any solution?


Add support for aggregations to search request/response classes

This PR adds an optional "aggs" field that provides supports for aggregations ("metrics" aggregations in the terminology of Elasticsearch/Opensearch) to the search request and response classes.
The structure of the search request is modeled after the ES/OS query DSL for metrics aggregations (edit: this was updated by https://github.com/slackhq/kaldb/pull/395/commits/96c78068c751219fe5fcbecbcc1dc1bbcf8074c1 to a bucket aggregation with auto-interval date histogram):
GET /my-index-000001/_search
{
  "aggs": {
    "my-first-agg-name": {
      "min": {
        "field": "my-field"
      }
    },
    "my-second-agg-name": {
      "avg": {
        "field": "my-other-field"
      }
    }
  }
}

For the sake of simplicity, the request structure is designed to handle only the aggregations that are currently planned for KalDB. These include sum, min, max, avg, value_count, and percentile_ranks.
We may want to refactor the top-level request after this work is completed. Some of this refactoring was done in https://github.com/slackhq/kaldb/pull/395/commits/96c78068c751219fe5fcbecbcc1dc1bbcf8074c1.

As of commit https://github.com/slackhq/kaldb/pull/395/commits/96c78068c751219fe5fcbecbcc1dc1bbcf8074c1 above, the request/response format would support the rough equivalent of an ES aggregation with auto-interval date histogram bucketing. As an illustration, consider the following ES query annotated with the values from the KalDB's search request:
POST /[SearchRequest.dataset]/_search?size=0
{
  "query": {
    "bool": {
      "filter": [
        //SearchRequest.query_string goes here
      ]
    }
  },
  "aggs": {
    "your_aggregation_name_here": {
      "auto_date_histogram": {
        "field": "_timesinceepoch",
        "buckets": SearchRequest.bucket_count
      },
      "aggs": {
        "your_aggregation_name_here2": {
          "avg": {
            "field": "desired_field_here"
          }
        },
        "your_aggregation_name_here3": {
          "min": {
            "field": "another_field_here"
          }
        }
      }
    }
  }
}

The query above would apply the Lucene query, divide matching documents in the specified number of buckets and then perform the avg and min aggregations for each bucket.
One current limitation is that HistogramBucket supports only date-based buckets. We would need to generalize it to support term or range-based buckets.

Work-in-progress rebased and merged into branch dhermann_aggs_request


#3004 VS progress bar hang when connecting to remote

Use Win32 message box and force it topmost.

Also update version to 1.0

Ping so i can merge for tomorrow BB

👍


remove tests for virtual reflections with strings

Rails doesn't allow associations to be defined with string names (you
will get an exception), so we should follow suit in virtual reflections.
In Rails 4, we've changed virtual reflections to create real Rails
reflections, then wrap and extend them.  In Rails 4, you'll get an
exception when creating virtual associations with string names, so lets
remove or fix these tests

Oh nice, I didn't know that. :+1:


Having issues with post json or array

I had this old code that worked
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $notificationURL);
curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type:application/json'));
 curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, Json::encode($json));
 curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 0);
curl_setopt($ch, CURLOPT_TIMEOUT, 400);

 $response = curl_exec($ch); // execute!
curl_close($ch);

i tried changing it to use this library, here is my code
$curl2 = new Curl();
$curl2->setOpt(CURLOPT_HTTPHEADER, ['Content-Type:application/json']);
$curl2->setOpt(CURLOPT_RETURNTRANSFER, true);
$curl2->setOpt(CURLOPT_POSTFIELDS, Json::encode($json));
$curl2->setOpt(CURLOPT_TIMEOUT, 0);
$curl2->post($notificationURL,[
    'data' => Json::encode($json)
]);

but the output adds data
data[success]=1&data[data][results]....

instead of just the
[success]=1&[data][chassis]=&[data][results]....

how do i just post the array or json without the data key?

Hi, I have a few questions...

What is the value of $json?
The POST data mentioned [success]=1&[data][chassis]=&[data][results].... doesn't appear to be json. Is that the expected POST data?

Maybe try to not json-encode the data since the header is already set:
$curl = new Curl();
$curl->setHeader('Content-Type', 'application/json');
$curl->post($notificationURL, $json);

View what will be sent in the request:
var_dump($curl->buildPostData($json));


set modified property of buffer in lua

Description of the problem or steps to reproduce
As I develop a plugin to open .gzip files in lua, I uncompress the .gzip file. I then replace the contents of the buffer with the decompressed text:
micro.CurPane().Buf:Replace(x, y, decompressed_text)
Afterwards I need to set the "isModified" property of that buffer to "false". That is, I want to change the output of
micro.CurPane().Buf:modified().
How do I change the output of micro.CurPane().Buf:modified()?
Specifications

Version: 2.0.10
Commit hash: b976385
Compiled on August 07, 2021
OS: Linux
Terminal: gnome-terminal

I worked around the issue by creating a new buffer and opening it.


⚠ ClamAV has degraded performance

In 7e46b20, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 124 ms

Resolved: ClamAV performance has improved in feae5e3.


Add payouts

This PR enables payouts via the Swish API (see #7).
Might require a major semver update depending on how the certificates and signing processes are handled.

Great work Marcus 🔥
I highly recommend releasing this under a branch alias, then we can test it out and fix any quirks before releasing a new stable version.

@vinkla Yep, will do – and/or possible publish a pre-release. Still a few quirks to iron out, will ping when something is available to test.

@vinkla You should now be able to require the development-branch with:
"repositories": [
        {
            "type": "vcs",
            "url": "git@github.com:olssonm/swish-php.git"
        }
    ],

And running composer require olssonm/swish-php:dev-dev/payouts

Thanks! I'll test this as soon as possible.


Workers are reused to serve multiple requests but terminated on timeout

Bug report

[X] I confirm this is a bug with Supabase, not with my own application. (the issue even happens with the example "hello" function provided by supabase)
[X] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
From my understanding, when a worker is spawned it always lives for workerTimeoutMs to serve requests and will then be terminated.
This causes functions executing on a previously started worker to randomly fail when the timout happens while they are executed.
To Reproduce

Set workerTimeoutMs in index.ts to some value like 10 seconds
Set up a simple longer running function like this:serve(async (req) => {
  await new Promise(r => setTimeout(r, 5_000));
  return new Response(`"Hello from Edge Functions!"`, { headers: { "Content-Type": "application/json" } });
});

Repeatedly call this function
When a request is started eg. 8 seconds after the first one, it will crash with the following log

2023-10-28 01:20:45 main function started
2023-10-28 01:21:24 [Info] Listening on http://localhost:9999/
2023-10-28 01:21:24 [Info] start
2023-10-28 01:21:32 [Info] end
2023-10-28 01:21:33 [Info] start
2023-10-28 01:21:34 wall clock duration reached. isolate:<PHONE_NUMBER>123966400
2023-10-28 01:21:34 failed to send request to user worker: connection closed before message completed
2023-10-28 01:21:34 Error: InvalidWorkerResponse: user worker failed to respond
2023-10-28 01:21:34     at async UserWorker.fetch (ext:sb_user_workers/user_workers.js:52:15)
2023-10-28 01:21:34     at async Server.<anonymous> (file:///home/deno/functions/main/index.ts:79:16)
2023-10-28 01:21:34     at async Server.#respond (https://deno.land/std@0.131.0/http/server.ts:219:24)

Expected behavior
Either workers should not be reused to serve multiple requests or their timeout should reset if they receive a new request.
PS: Also, there does not seem to be a way to adjust allowed CPU-time which is also a dealbreaker for long running workers like generating AI embeddings.

I investigated this a bit more and my only realization that the functions host is pretty much unusable to run any longer tasks or stuff that has to be executed reliably.
For now I have created a simple deno server to replace the edge-runtime.


Change icon import names to have a prefix e.g.

It's not all the time I run into this issue but I often find myself having to use different icons or renaming components within React projects so that they don't clash with the imports.
E.g. if I want to use <Login /> Lucide icon but I have a <Login /> functional component.
A suggestion would be to prefix the imports so <Camera /> would become <LcCamera /> or similar.

Hmm, I understand the issue. I think it is a bit hard to change. Because it is a breaking change for everyone. But we are thinking of adding aliases in the future, maybe we can think of a solution as well.

It would be a nice solution to have multiple names for the same export but I can't think of a nice way to do this without module / function duplication.

I disagree with this suggestion. Renaming imports is trivial and more flexible than introducing some arbitrary prefix that would be a breaking change.
Assuming you're using Typescript/Javascript, a suggestion for how to handle it could for instance be to create something like components/icons/index.[ts|js] and do
export {
  Camera as CameraIcon,
  LogIn as LoginIcon,
  // and whatever other icons you need with whatever pre-/postfix you prefer
} from "lucide-react";

They may then be imported as import { CameraIcon } from "/components/icons".

I can agree with you that this would work.
It is a workaround however, not a solution.
There needs to be a bigger change here to prevent collisions?
On Mon, 24 Oct 2022, 08:48 Erik André Jakobsen, @.***>
wrote:

I disagree with this suggestion. Renaming imports is trivial and more
flexible than introducing some arbitrary prefix that would be a breaking
change.
Assuming you're using Typescript/Javascript, a suggestion for how to
handle it could for instance be to create something like
components/icons/index.[ts|js] and do
export {
Camera as CameraIcon,
LogIn as LoginIcon,
// and whatever other icons you need with whatever pre-/postfix you prefer} from "lucide-react";
They may then be imported as import { CameraIcon } from
"/components/icons".
—
Reply to this email directly, view it on GitHub
https://github.com/lucide-icons/lucide/issues/806#issuecomment-1288564198,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWYSVGKHEZDQBB6PSWRHEYLWEY5NPANCNFSM6AAAAAAQ7MAGVU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Another way you could do it is to import as
import * as Lucide from "lucide-react";

and then render components as
<Lucide.Camera />

I think namespacing imports properly should be the responsibility of the app developer, not the library developer, and therefore disagree that this is something that needs a solution from Lucide's or @ericfennis' end.

We have a plan to support aliases in all our packages that uses lucide icons as components.
I was thinking to add an aliases.js file with all the icons aliases. and export them in the main index.ts.
import { Camera } from "lucide-react"; or `import { CameraIcon } from "lucide-react"; will lead to the same icon file. This only will working nicely with ESModules.
If you want to have all the icons you can then still do import * as icons from "lucide-react/icons";
But importing icons this way is not recommended and bad practice if you are bundeling your application for browsers. This way of importing breaks the tree-shaking ability in bundlers. So your bundled app will include all 800+ icons.

import {CameraIcon} from "lucide-react";

would be ideal imo.
Will aliases like you mention above also be added to other language packages like Svelte and Vue? And would it still cause issues if I had a local component named Camera?
For example:
import {Camera} from "./src/CustomButtons"

@Snailedlt yess, we want to implement it in all packages.

@ericfennis Neat!
What about my second question?

And would it still cause issues if I had a local component named Camera? For example:
import {Camera} from "./src/CustomButtons"

We have a plan to support aliases in all our packages that uses lucide icons as components. I was thinking to add an aliases.js file with all the icons aliases. and export them in the main index.ts. import { Camera } from "lucide-react"; or `import { CameraIcon } from "lucide-react"; will lead to the same icon file. This only will working nicely with ESModules.
If you want to have all the icons you can then still do import * as icons from "lucide-react/icons"; But importing icons this way is not recommended and bad practice if you are bundeling your application for browsers. This way of importing breaks the tree-shaking ability in bundlers. So your bundled app will include all 800+ icons.

I can understand where some may think this is the responsibility of the developer, your application, your job sort of thing.
On the other side, packages are meant to make life simpler, without having to make unecessary accommodations, whilst also maintaining a small bundle size.
I raised this issue initially, and although biased, I do think it's the best approach to just simply rename them completely and announce a breaking change.
Maintaining an aliases.js would work, but adds more room for potentially forgetting an icon and it not being supported with that naming convention.
I'd propose to simply change the naming to LucideCamera or LICamera.
https://react-icons.github.io/react-icons/icons?name=fi React icons has this exact setup, although it's due to it having multiple icon packages and it needs to distinguish between them, it does work really well.

@jakobsen I completely agree.
Maintaining aliases.js is not a problem. I already started on this feature in #899. The aliases file is completely rendered on build time so no SVG icon will be missed that is in the icons directory.
I did already some tests and it works great.
You can import each icon in three ways:
import { Camera } from  'lucide-{packageName}'  import { LucideCamera } from  'lucide-{packageName}'
`import { CameraIcon } from  'lucide-{packageName}'
It will point all to the same module. So tree-shaking is still working.
See the linked draft PR #899

This is still not ideal IMO as the icons pollute the component name scope quite a bit.
For example if I want to import the NextJS Link component, the IDE automatically suggests Link icon from Lucide which is not ideal.

@piotrkulpinski: I'm afraid for the time being the old, unprefixed names will have be kept for backwards compatibility, although I do agree that using a prefixed version from the start would have been ideal. Maybe we can drop the unprefixed names in v1.0.

This is IMO a ts-server issue.
https://github.com/microsoft/TypeScript/issues/51155

@jguddas solving it in ts-server is super super complex though.
I would love to see prefixes. Ideally we can have prefixed react components in a separate package like
import { LIconCamera } from 'lucide-react/prefixed'
? Introducing it like this would not break anyone's existing code.

@capaj We do already have prefixed components, the issue is no longer with that, but dropping support for the unprefixed ones.

@karsa-mistmere what do you mean?
Where? I may be stupid, but I don't see how to import them. Are you suggesting I use
https://lucide.dev/guide/packages/lucide-react#one-generic-icon-component
? I could, but I don't like that solution, because I bundle with Vite and it would force all the icons into my bundle.

I'm not quite sure what generic components have to do with prefixed component names.
This issue has to do with adding prefixes to icon component names, which has already been implemented via alias exports, e.g. in lucide-react ArrowUpSquare is exported as both ArrowUpSquare and ArrowUpSquareIcon as well as LucideArrowUpSquare.

Thanks!
I was just trying it wrong

I think we should write something about these prefixes and suffixes in our documentation.

Adding my two cents here: I often end up with this auto import:
import { Link } from 'lucide-react';

Instead I am always in need for this one:
import Link from 'next/link';

And I guess there a re more conflicts like this. Because Lucid has the alias with *Icon I always use icons like this:
<LinkIcon />

Then it gets the import right for obvious reasons. However, I would also like to avoid it the other way around as mentioned above. I know it's a breaking change, but what if Lucide would only enable *Icon, e.g. LinkIcon imports (so not exporting the Link equivalent from the library)?

Agreed. I think my suggestion was more towards removing the exports in Lucid that do not have a prefix/suffix, such as Link.

Thanks for your view on this!
We have a related discussion in #1830.
I've also written a proposal in #1830, so let me know what you think.


Update uuid-creator to 4.4.0

Updates com.github.f4b6a3:uuid-creator from 4.3.2 to 4.4.0.
Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.f4b6a3", artifactId = "uuid-creator" } ]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Codecov Report

Merging #272 (7111db2) into main (c5c0d36) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #272   +/-   ##
=======================================
  Coverage   88.76%   88.76%
=======================================
  Files          91       91
  Lines        2776     2776
  Branches       68       68
=======================================
  Hits         2464     2464
  Misses        312      312

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 c5c0d36...7111db2. Read the comment docs.


AAD filtering module - not using variables

AAD module does not use the input variables. Instead, it is using only the deafult parameters always.
Verify if it is happening with the IAD filtering too.

AAD Image filter module was edited.


Enchance performance of RENDER_GELF

Currently RENDER_GELF fills in GELF_TEMPLATE with chained calls of .replace, which isn't really necessary as render functions are only invoked inside synchronous environments (AFAIK; I may be wrong, but the only place I've found where they are invoked is the Dispatcher object inside individual coroutines), so there isn't a hard requirement for immutability and the functionality can be implemented with StringBuilder or Kotlin string interpolation (which is actually also a StringBuilder), which is better than multiple copyings from a performance perspective
This is a minor issue, but I thought that it would be a good idea to document it

Thanks @GinGin3203 for your issue. I agree it is sub-optimal: it was just a first go to show it can be done.
Please submit a PR if you want to improve RENDER_GELF.


[todo] test the domain in domain_list.txt

> python -m dns_observe google.com
Time: 2024-11-20 21:46:22.634388, Name: google.com, Other Type!

521aab0d2b181aa774b121eea5b7254ceadabe39 fix it


lazy loading implemented

Related Issue

Closes: #57
Description of Changes

Implemented Lazy loading for all the pages and images in this project due to which whenever the website loads initially then only the content that is visible to the user are loaded instead of the whole content. This reduces the initial loading time making the user experience better.
Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] My changes have not introduced any new warnings.

Check for merge conflicts @Avinash905


uchiwa version is out-of-date

#defaults/main.yml
uchiwa_pkg_version: 0.14.2-1
uchiwa_pkg_deb_download_url: http://dl.bintray.com/palourde/uchiwa/uchiwa_{{ uchiwa_pkg_version }}_amd64.deb
uchiwa_pkg_rpm_download_url: http://dl.bintray.com/palourde/uchiwa/uchiwa-{{ uchiwa_pkg_version }}.x86_64.rpm

Hard-coding uchiwa version is not ideal here. Question is why don't we simply download uchiwa package directly from sensu repo?
[root@haphan-sensu cloud-user]# yum  info uchiwa | grep Version
Version     : 0.23.1

I think it was only shortly after the release 0.14 that it was added to the sensu repos, good catch.


sql error not show while "execute sql in new tab"

System information:

Win10

Describe the problem you're observing:
when run some sql in new tab, it won't show the error msg.
Steps to reproduce, if exist:

connect a database (eg. mysql) ,open an editor.
run select 1 from dual;  with  "execute sql in new tab" twice.  now it shows 2 tabs in result panel .
run select 1 from dualxx;  with  "execute sql in new tab"  twice, first it show error msg in output correctly , but seceond try, it shows Result 2, no error msg .

Include any warning/errors/backtraces from the logs

@metalbreeze Hello
What DBeaver version do you use?

There has been no update for a long time. If the issue is still present, feel free to reopen it.


Quantiphyse Installation problem

After installation in Mac OS, I call "quantiphyse" and get the error message as follows:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/2.7/bin/quantiphyse", line 5, in
from pkg_resources import load_entry_point
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/init.py", line 3095, in
@_call_aside
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/init.py", line 3081, in _call_aside
f(*args, **kwargs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/init.py", line 3108, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/init.py", line 660, in _build_master
return cls._build_from_requirements(requires)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/init.py", line 673, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/init.py", line 851, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (numpy 1.8.0rc1 (/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python), Requirement.parse('numpy>=1.12.0'), set(['pandas']))
Please help!

Looks like the version of numpy you have is too old. Are you using the default Python on a Mac? It does tend to be quite behind the times.
The following may help:
sudo pip install numpy --upgrade

Thanks for your response.  I am using Python 2.7 which I installed.
After upgrading the numpy, I still get the error messages as attached.  Any idea?

On 4 Dec 2019, at 09:59, Martin Craig<EMAIL_ADDRESS>wrote:
Looks like the version of numpy you have is too old. Are you using the default Python on a Mac? It does tend to be quite behind the times.
The following may help:
sudo pip install numpy --upgrade
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ibme-qubic/quantiphyse/issues/33?email_source=notifications&email_token=AHDANQQN4RKEMVJCMVEEPILQW55PZA5CNFSM4JQFOVQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF4M45A#issuecomment-561565300, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDANQUDFCKDH63LO2WV4GLQW55PZANCNFSM4JQFOVQA.

I found a suggestion that the Mac default numpy is not removed when upgrading it and this can be fixed by the following:
cd /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/
sudo rm -r numpy
pip install pandas
It should pull in the version of Numpy that it needs. If this fails I have a Mac that I can try to reproduce this on - what MacOS version are you running?

After "sudo rm -r numpy”, I see "override rw-r--r--  root/wheel restricted,compressed for numpy/distutils/unixccompiler.py”.  What should I do?

On 4 Dec 2019, at 10:18, Martin Craig<EMAIL_ADDRESS>wrote:
I found a suggestion that the Mac default numpy is not removed when upgrading it and this can be fixed by the following:
cd /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/
sudo rm -r numpy
pip install pandas
It should pull in the version of Numpy that it needs. If this fails I have a Mac that I can try to reproduce this on - what MacOS version are you running?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ibme-qubic/quantiphyse/issues/33?email_source=notifications&email_token=AHDANQQHYY7NNVIHUUR65J3QW57WDA5CNFSM4JQFOVQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF4OU2I#issuecomment-561572457, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDANQWOBJNSD57EG4FYFB3QW57WDANCNFSM4JQFOVQA.

Change it to sudo rm -rf numpy
It shouldn't ask you any questions then!

After that, a bunch of lines saying
"rm: numpy/distutils/unixccompiler.py: Operation not permitted
rm: numpy/distutils/numpy_distribution.py: Operation not permitted
rm: numpy/distutils/conv_template.py: Operation not permitted
rm: numpy/distutils/cpuinfo.py: Operation not permitted
rm: numpy/distutils/ccompiler.py: Operation not permitted
rm: numpy/distutils/misc_util.pyc: Operation not permitted
rm: numpy/distutils/npy_pkg_config.py: Operation not permitted
rm: numpy/distutils/config.pyc: Operation not permitted
rm: numpy/distutils/compat.py: Operation not permitted
rm: numpy/distutils/system_info.pyc: Operation not permitted
rm: numpy/distutils/misc_util.py: Operation not permitted
A lot more below…."

On 4 Dec 2019, at 10:23, Martin Craig<EMAIL_ADDRESS>wrote:
Change it to sudo rm -rf numpy
It shouldn't ask you any questions then!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ibme-qubic/quantiphyse/issues/33?email_source=notifications&email_token=AHDANQTWX42BJV3L23CXU3TQW6AKJA5CNFSM4JQFOVQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF4PHYA#issuecomment-561574880, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDANQW7WSVXJGBAPV3LITDQW6AKJANCNFSM4JQFOVQA.

This seems to be extra security on recent Macs... I found an article (linked below) which explains how to get around the problem, however I am wondering at this point if it is more sensible to go down the Anaconda route. The 'official' Mac support for Python has always been very out of date - in the past it wasn't possible to install quantiphyse at all with the standard python - and even if we can get around this issue you might find another similar problem with another package.
My recommendation at this point would be do go to www.anaconda.org, download anaconda (python 3.7) and then follow the instructions here:
https://quantiphyse.readthedocs.io/en/latest/basics/install.html#anaconda-python-3-x-dependencies-from-pip
If you want to press on using the system Python, here is the article on getting around the 'Operation not permitted' problem:
http://osxdaily.com/2018/10/09/fix-operation-not-permitted-terminal-error-macos/
Let me know what you try and how you get on - I am sorry it's not more straightforward unfortunately Python on Mac isn't the easiest environment to support and each new version seems to break the recipe we had working previously!

Thanks a lot for your suggestions.  I will try Anaconda then.
BTW, I have found the Basil (asl_gui) from the FSL package that I installed on my Mac.  How different is it from quantiphyse in terms of ASL data analysis?  FYI, I am going to analyse pCASL data.

On 4 Dec 2019, at 10:36, Martin Craig<EMAIL_ADDRESS>wrote:
This seems to be extra security on recent Macs... I found an article (linked below) which explains how to get around the problem, however I am wondering at this point if it is more sensible to go down the Anaconda route. The 'official' Mac support for Python has always been very out of date - in the past it wasn't possible to install quantiphyse at all with the standard python - and even if we can get around this issue you might find another similar problem with another package.
My recommendation at this point would be do go to www.anaconda.org http://www.anaconda.org/, download anaconda (python 3.7) and then follow the instructions here:
https://quantiphyse.readthedocs.io/en/latest/basics/install.html#anaconda-python-3-x-dependencies-from-pip https://quantiphyse.readthedocs.io/en/latest/basics/install.html#anaconda-python-3-x-dependencies-from-pip
If you want to press on using the system Python, here is the article on getting around the 'Operation not permitted' problem:
http://osxdaily.com/2018/10/09/fix-operation-not-permitted-terminal-error-macos/ http://osxdaily.com/2018/10/09/fix-operation-not-permitted-terminal-error-macos/
Let me know what you try and how you get on - I am sorry it's not more straightforward unfortunately Python on Mac isn't the easiest environment to support and each new version seems to break the recipe we had working previously!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ibme-qubic/quantiphyse/issues/33?email_source=notifications&email_token=AHDANQXEVHAFRHGAA3P4IF3QW6B2ZA5CNFSM4JQFOVQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF4RFHA#issuecomment-561582748, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDANQTR2FLZJFBNURF23UTQW6B2ZANCNFSM4JQFOVQA.

The Basil GUI from FSL delivers a very similar ASL analysis to Quantiphyse. Technically they are using different pipelines, Basil uses oxford_asl whereas Quantiphyse uses our newer Python-based oxasl pipeline. However oxasl has been designed to mimic oxford_asl as closely as possible so you should find very similar results for the two.
oxasl (and hence Quantiphyse) is able to handle some additional ASL data types, such as multiphase and vessel-encoded data. On the other hand oxford_asl has been more extensively used. The Quantiphyse gui offers far more than the Basil GUI which is really just a front end to running the analysis.
Hope this helps!

I've updated the installation instructions on Mac slightly to recommend fslpython or anaconda. I will close this issue now, problems with other installation methods can be raised as new issues.


[core] Add missing unwrap export to test-utils type definition

Adds missing export to unwrap in test-utils/index.d.ts, as requested here.

@kallebornemark Thank you


Indent guide is too bright

The indent guide recently got brighter. How can I dim it more?

Yeah, they now use the "official" color for guides. But you can change it and make it darker by adding something like below in your styles.less file.
atom-text-editor::shadow .indent-guide,
atom-text-editor .indent-guide {
  color: hsl(204, 2%, 25%);
}

Tweaking the last % number (25%) makes it darker or lighter.

@simurai You're the man, thanks!

@simurai Excellent!


[Question] is there any way to optimize the image, crop, compress it before uploading?

is there any way to optimize the image, crop, compress it before uploading? The docs don't mention anything about optimizations. And using it with next.js and making the functions optimize the image with the execution time limitations could be challenging so I wanted to ask about this!
Sorry if this is Unrelated

We don't have any built in methods for doing anything like this, but typically in the past I would do those sort of things in a hidden canvas on the client before uploading my file wherever it was destined to go.
In the future we do want to add the ability to pre- and post-process files, but that is still a ways off for now.

We don't have any built in methods for doing anything like this, but typically in the past I would do those sort of things in a hidden canvas on the client before uploading my file wherever it was destined to go.
In the future we do want to add the ability to pre- and post-process files, but that is still a ways off for now.

Thanks! I hope this feature comes soon since it's crucial to the goal of uploadthing (making it easy for developers to make production ready media uploading without the hassle of aws s3, lambda functions, etc...)

@ig4e check out #194 - i made an example of how you can preprocess images and crop them

@ig4e check out #194 - i made an example of how you can preprocess images and crop them

Thanks I'll definitely check it


Disable the proxy container for now

We can decide later what to do with it.

/retest

/retest

/retest

/retest

/retest