Add support for open source VSX registries

This extension is not available in open source VSX registries like openvsx making it not possible to use vscodium which is an open source editor, can you upload it to openVSX registry?

Done! And from b6cb3aa20c5952309e86ce117c095e4def2f80ef all releases will be published to both!
Thanks for the idea!


Transferwise payment screen showing erroneous fee text

When you go through the process of paying an expense via Transferwise, you see a screen instructing you to add fees. But there is no way to add the fees, and it's not clear what such fees would be for.

If there is a need to be able to add fees, it should appear here. However, I don't think there is a need so actually everything about fees should just be removed from this screen.

To add some context on this, we still need to implement the "estimated fees" for this screen, which should look like the screenshot below. I however agree with what's reported here, we shouldn't say Please add the corresponding fees... when an "Automatic" payout method is selected.

Will be resolved by https://github.com/opencollective/opencollective-frontend/pull/4328
Estimated fees will be implemented with https://github.com/opencollective/opencollective/issues/3089


Filter out package references for the dependency testing for core pipelines

Fixes https://github.com/Azure/azure-sdk-for-net/issues/32785

Does this also add back in the project reference pipelines, so we have those to detect breaks?

Does this also add back in the project reference pipelines, so we have those to detect breaks?

Yes this should make all the dependency tests use project references and no package references in that set of tests.

/azp run net - resourcemanager - mgmt - ci

/azp run net - resourcemanager - mgmt

/azp run net - resourcemanager - mgmt

/azp run net - resourcemanager - mgmt

Test failure is being fixed by https://github.com/Azure/azure-sdk-for-net/pull/33078 and is unrelated.


An unexpected error happened - Error: Minified React error #301

Installed last version of Grafana(10.3.3)
Installed last version of LLM plugin(0.6.0)
Enabled "dashgpt" Feature.
Configured the plugin with Azure OpenAI:

How to recreate the problem:

Open a dashboard
Go to dashboard settings
Press "Auto Generate"

An unexpected error happened. Screenshot below:

Full error message below:
An unexpected error happened
Details
Error: Minified React error #301; visit https://reactjs.org/docs/error-decoder.html?invariant=301 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

    at Q (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:1976:7196)
    at m (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:1984:69)
    at div
    at div
    at o (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:211:47906)
    at g (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:211:48262)
    at div
    at http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:192:134859
    at div
    at http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:211:45043
    at div
    at div
    at div
    at div
    at div
    at X (http://hostname:3000/public/build/1663.190becda783f60342f79.js:124:36505)
    at m (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:192:29691)
    at div
    at W (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:404:21349)
    at Jt (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:1966:1003)
    at Vt (http://hostname:3000/public/build/1663.190becda783f60342f79.js:183:66201)
    at gr (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:1974:3599)
    at vn (http://hostname:3000/public/build/DashboardPageProxy.dbec33b5fdad6d16d25e.js:407:474)
    at DashboardPage
    at Vt (http://hostname:3000/public/build/1663.190becda783f60342f79.js:183:66201)
    at So (http://hostname:3000/public/build/DashboardPageProxy.dbec33b5fdad6d16d25e.js:407:6597)
    at Suspense
    at o (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:192:118866)
    at bo (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:349:10002)
    at be (http://hostname:3000/public/build/1663.190becda783f60342f79.js:228:23522)
    at uo (http://hostname:3000/public/build/1663.190becda783f60342f79.js:209:4728)
    at Jn (http://hostname:3000/public/build/1663.190becda783f60342f79.js:209:10219)
    at el (http://hostname:3000/public/build/1663.190becda783f60342f79.js:228:11773)
    at be (http://hostname:3000/public/build/1663.190becda783f60342f79.js:228:25717)
    at div
    at div
    at main
    at div
    at Ji (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:349:2441)
    at uo (http://hostname:3000/public/build/1663.190becda783f60342f79.js:209:4728)
    at Jn (http://hostname:3000/public/build/1663.190becda783f60342f79.js:209:10219)
    at Cn (http://hostname:3000/public/build/1663.190becda783f60342f79.js:209:9608)
    at Dl (http://hostname:3000/public/build/1663.190becda783f60342f79.js:228:12072)
    at be (http://hostname:3000/public/build/1663.190becda783f60342f79.js:228:19694)
    at div
    at i (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:212:13890)
    at d (http://hostname:3000/public/build/1663.190becda783f60342f79.js:41:13951)
    at p (http://hostname:3000/public/build/1663.190becda783f60342f79.js:683:233964)
    at d (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:700:21358)
    at o (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:192:118866)
    at g (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:192:119375)
    at Ae (http://hostname:3000/public/build/1663.190becda783f60342f79.js:187:530)
    at Br (http://hostname:3000/public/build/8291.c757e598a21c790323c9.js:360:127)

Thank you for the report! @SandersAaronD could you investigate this? I am not sure if the error is from the Dashboard code or our plugin. I think it might be the dashboard code though?

This is almost certainly the dashgpt code, Grafana versions after 10.2.0 have produced dependency and build problems for them. I will make sure this gets linked to efforts around that so that we don't consider them fixed until this is fixed.

I met the same issue.  thanks @SandersAaronD


Global replace support

When editing, it would be nice if changes to the contract text (e.g., name of a party) could be replaced everywhere in the contract.
This might require some level of UI tooling (e.g., a 'search/replace' button) but also require improvements to the template support in Cicero (e.g.,: https://github.com/accordproject/cicero/issues/4)

This issue has been moved to https://github.com/accordproject/template-studio-v2/issues/7


MSVC & SDK dirs suddenly hidden from compiler.include_dirs

#153 broke the pywin32 builds by incompatibly hiding the MSVC & SDK dirs from compiler_instance.include_dirs - and decent public access at all. Same for libs.
The problem happened at
https://github.com/mhammond/pywin32/blob/fc69a1ecc150a13433a7a71d61bac52a5f3df42b/setup.py#L695
/ https://github.com/mhammond/pywin32/commit/fc69a1e) ( @zooba )
(And further problems would also occur later in _why_cant_build_extension() at least.)
The VC & SDK dirs are needed for inspection in complex projects.
At best in a compatible way again.
#153 uses (hidden) class vars  compiler_instance.__class__.include_dirs which though are set only after instance.initialize() .
PR #172 (tested with pywin32) suggests a potential way of solution and tests - see further comments and commit comments there.
Without solution, strange application code / workarounds like this would be required:
https://github.com/mhammond/pywin32/blob/b52884ae5417fd2f857007ae1c74d4f753591d36/setup.py#L688
https://github.com/mhammond/pywin32/pull/1936/commits/b52884ae5417fd2f857007ae1c74d4f753591d36
https://github.com/mhammond/pywin32/pull/1936

Thanks kxrob for the report, and specifically for what's needed. I think I understand now.
I'm unsure why the initialization is deferred, but the include/lib dirs are dependent on the plat_name indicated by .initialize(plat_name), so it's necessary to initialize before accessing those dirs. That's no different than before.
I think I agree that a compiler should expose the include/lib dirs as they would resolve when compiling, rather than hiding them in _fix_compiler_args. And maybe they shouldn't be stored in class attributes, but that's an implementation detail if we can expose the full set through an API.

I think I agree that a compiler should expose the include/lib dirs as they would resolve when compiling, rather than hiding them in _fix_compiler_args.

Are you going to do the same for gcc? Because I bet you're not ;)
Hiding the default arguments is just trying to give both gcc and MSVC an equivalent API. If that API is "distutils knows what the default compiler paths will be", you'll likely need to do more work to extract those paths from gcc to provide them. Otherwise, you're just entrenching different APIs for different platforms.
The pywin32 need for this part of the API was to work around the underlying issue, which is now fixed. With the fix in place, they don't need it anymore. (They were also previously using it to guess where certain other headers and libraries might be, but that logic is wrong and I already replaced it with a more robust option that doesn't rely on being able to read out the runtime include/lib dirs.)

If that API is "distutils knows what the default compiler paths will be", you'll likely need to do more work to extract those paths from gcc to provide them.

I don't think its about knowing all that behind the curtain for abstract reasons - but simple knowing what the MSVC / gcc ... is fed with by distutils.
So that e.g. we can use the same paths compatibly for _build_scintilla() - which uses a makefile of a sub-project outside of distutils.

pywin32 need for this part of the API was to work around the underlying issue, which is now fixed. With the fix in place, they don't need it anymore.

Well, the _fixup_sdk_dirs() and its digging mechanism find_platform_sdk_dir() (competing with distutils and actually finding a different kit version on github CI) for the VC/SDK dirs can now be removed - but only when so far the above PR also peeks the hidden VC&SDK dirs out of distutils - which are still needed, see below.
These dirs should be better exposed "public".
And why not simply in the .include_dirs itself - complete ?

They were also previously using it to guess where certain other headers and libraries might be, but that logic is wrong and I already replaced it with a more robust option that doesn't rely on being able to read out the runtime include/lib dirs.

Well, actually your own (!) last changes there
https://github.com/mhammond/pywin32/blob/fc69a1ecc150a13433a7a71d61bac52a5f3df42b/setup.py#L695
/ https://github.com/mhammond/pywin32/commit/fc69a1e) ( @zooba )
introduced, not removed the inspection of compiler.include_dirs .
And that is even exactly where the crash occurred first after the setuptools version stepped up on github CI.
(Besides that there is another use case in _why_cant_build_extension() at least, used for every extension - which wants to know beforehand via that inspection which of the extension builds need to be skipped when certain special libs are not present. )
And there may be many other reasons for other users to simply know "how the cow is fed" . Why hide important things?
And also to replace dirs in special cases - e.g. the SDK dirs for choosing a preferred version.   (The effect is achieved also by searching the alternative user provided dirs first (which is the case), but produces absurd and sometimes conflicting command lines - which we have currently on CI logs until the above PR)
Besides: You also introduced another maybe competing mechanism (vswhere) in find_visual_studio_file(). Don't know if that is meant to find ATLMFC dirs even outside of the VC dirs which distutils uses, or not? In the latter case (otherwise there could be library conflicts?) that would compete with the different mechanism in distutils._msvccompiler and might potentially find a different VC installation. That finder would probably also better replaced by using distutils defaults as a starting point for search in the same tree as "...VC\INCLUDE" or so? (Not so far in the above PR.)

different APIs for different platforms

There are many platform specific functions in standard Python - and needed. But generally trying to make it as similar as practically possible.
Here so far there is no extra API needed when e.g. simply all dirs are exposed.
Or as a second-best compiler.default_cmdline_include_dirs or so are exposed for all platforms, sometimes empty (but why?).
Or third-best compiler.default_msvc_cmdline_include_dirs (double why??).
Just like for example getcwd() returns a path with drive letter in front on Win, but we don't have os.ms_getcwd() ...
pywin32 of course needs to do Windows specific things - but still produce distutils / Python compatible extensions, wheels, ...

Yep. How do you think I knew where setuptools needed to be fixed, and also that the bit I added would stop working after it was fixed upstream? I'm not magic, I'm just trying to be both the cause and the solution! 😆

There doesn't seem to be a warning comment at that code position and/or hint for resolution, your https://github.com/mhammond/pywin32/issues/1897 says: I haven't tried, but I believe the code in your setup.py will still work, and none of the asserts will trigger. So you may not notice anything at all ...
How should that be solved there best without getting the dirs out of distutils - using one of the distutil's spawn()'s  to call nmake or so? (kind of public API?)
And in _why_cant_build_extension() ?

The ATLMFC redistributable libraries are separate from UCRT and WinSDK, which is what vcvarsall will configure by default.

But in case its compatible, are those dirs usually near the corresponding VC? Did not see anything else so far. And had no problem so far as long as the ATL stuff was clicked for installation.

vswhere is also the official way to find VS installs these days. The registry keys haven't been reliable since VS 2017. And yeah, it'll find different versions at times - a fundamental problem with distutils is ...

In the end distutils should do the "probably best" / offical base search, whatever it is, and pywin32 probably just follow without (1st priority) risking a completely incompatible dir for ATL. So I guess it should remain a goal to get rid of a completely independent search mechanism "from bottom up" - just do some search from a distutils provided start?

Except UnixCCompiler won't expose the directories.

It just inherits and exports the empty list - trivially. And in a similar use case as above: the extra makefile sub-project for gcc e.g. could be fed the same way.

you have to find them yourself

With an independent often incompatible search mechanism again?  That would be back to square one.
Think it would still be better to hack peek into the "top secret" distutils private internals and fixup every few years ...

I think I agree that a compiler should expose the include/lib dirs as they would resolve when compiling, rather than hiding them in _fix_compiler_args.

Are you going to do the same for gcc? Because I bet you're not ;)

You're correct. I was not explicitly planning to do the same, in part because it's not obvious to me what that would entail. It seems to me the difference here is that gcc infers the default libs for the platform but Windows requires them to be supplied explicitly. If so, then the path to convergence is for distutils to supply those defaults. I was not intending to extract those and present them for a downstream consumer.
What I do believe is valuable to convey is "what behavior does distutils add" or "how does distutils configure a compile operation", so a consumer could reasonably infer how an operation (compile, link) is going to behave on any platform.

What you probably want is to add a new setuptools feature to allow running an arbitrary command as if it's the compiler (same environment, basically). It's already inherited a number of helper methods for certain types of commands (static lib, preprocess, etc.), but adding a new one for any command would satisfy the need for building Scintilla, and could also be implemented consistently across all platforms.
Jason owns distutils now as far as I'm concerned, but I'd expect it to be deprecated across the board now with the intent to merge all the functionality into setuptools APIs over the next couple of years (and likely tidy some up along the way). That's why I say it's probably a setuptools feature.

But in case its compatible, are those dirs usually near the corresponding VC? Did not see anything else so far. And had no problem so far as long as the ATL stuff was clicked for installation.

One day soon you will have a problem, because I encountered the problem while cross-compiling for a platform that you don't support yet 😉 With the fixes I contributed (and the later fixes for the distutils change), it'll be trivial for you to support Windows ARM64 devices once you decide it's worthwhile (hopefully during CPython 3.11, which has an ARM64 installer). But I acknowledge that you likely haven't seen that issue before, even though I think that's due to luck rather than any intentional design on the part of the MSVC installer.

In the end distutils should do the "probably best" / offical base search, whatever it is, and pywin32 probably just follow without (1st priority) risking a completely incompatible dir for ATL. So I guess it should remain a goal to get rid of a completely independent search mechanism "from bottom up" - just do some search from a distutils provided start?

As I mentioned above, setuptools may choose to expose more information or access to the compilation environment. But distutils never did it on purpose (and never provided enough to be accurate, unless you got lucky, as you apparently have been), and it's unlikely to get new features to provide it now.
In this particular case, you'd only get a mismatch if the build was going to fail anyway, so nothing breaks that was already working. But the point is true that in more complex cases, there may be components installed in a newer VS instance that "shadow" the one that included MSVC and cause problems. It won't be ATLMFC though (which has a dependency on MSVC in VS).


[WiP] Test with prom volume label set to small

What this PR does
Tests the changes in https://github.com/giantswarm/cluster-standup-teardown/pull/22 to ensure that reducing the prom volume size doesn't impact the tests.
Checklist

[ ] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

/run cluster-test-suites


street: investigate performance

Core i9 1060 laptop is expereincing performance issues.
It's unclear if it is CPU/GPU bound, need a Performance tab sample for analysis.

Might have just been the laptop.

Might have just been the laptop.


Add png support

add the libraries png and zlib; see README.md for details
The actual code is not changed in function, but additionally provides a png picture in addion to the jpg picture.
Further to do:

write proper solution to switch between jpg and png format
output rawdata in png format.

Note:

png lib was edited to remove conversion warning. The original code was good ingeneral but a bit sloppy. Only slight modificatins where made.
zlib is much harder to fix. I see some danger to alter functionality if concersions are changed. In general I would not trust the software for big files > 2GByte on 32 bit machines because of problematic conversions between usigned ans signed integer

after fixing the code coverage Comit is OK


Add link to "go back to competition" on competition edit form

Somewhere, maybe in a button along with the group on the bottom, or as a text link in the top left.

NOTE! German is starting on this task today, so we don't step on each other's toes :)


Stream the response in okcurl.

Beneficial for this website in particular:
https://http2.golang.org/clockstream

neat!

What was the behavior before? It would only emit after 2048?

@JakeWharton I guess the trick is pulling until exhausted is true. I'm guessing the former code would only read the first chunk.

suppose we could start adding mws tests for things like this in the future..

Previous behavior emitted every 2048 bytes. This emits more frequently.


Add support for declared authors for various package managers

This is based on #3627 and WIP.

This is obsolete now; single PRs have been created for the package managers covered here.


remove the prod tag when running build in pipeline

@wanwiset25 We only need to run the env=production when we build the image. for the test env it's ok to run with dev dependency in it.

@wanwiset25 We only need to run the env=production when we build the image. for the test env it's ok to run with dev dependency in it.

wouldn't that cause a problem in prod? test passes but prod doesn't have all deps. I guess this only applies to the current unconventional deployment style.

@wanwiset25 We only need to run the env=production when we build the image. for the test env it's ok to run with dev dependency in it.

wouldn't that cause a problem in prod? test passes but prod doesn't have all deps. I guess this only applies to the current unconventional deployment style.

Correct. We can improve it as we go.


Add LG Styler Support

Which device do you want to add? Please describe:
LG Styler S3BF
Describe the solution you'd like:
Remote control it like LG app does; and check its status e.g. how long the course will be completed.
Device Data:
[2/20/2022, 3:20:08 PM] [LGThinQ] Device data:  {"deviceId":"a02e96b2-41b3-1088-9000-acf108c5ab18","deviceType":203,"modelName":"S3BF_POD_DN4","subModelNm":null,"sensorType":null,"alias":"Styler","deviceCode":"LA04","networkType":"02","tftYn":"N","guideTypeYn":"Y","guideType":"TYPE1","pccModelYn":"N","autoOrderYn":"N","drServiceYn":"N","ssid":"XXX","timezoneCode":"Asia/Hong_Kong","timezoneCodeAlias":"Asia/Hong_Kong","sdsGuide":"{"deviceCode":"LA04"}","newRegYn":"N","remoteControlType":"","fareTarget":null,"area":"1123411","sleep":null,"deviceState":"E","rmsClientId":null,"regDtUtc":"20210101112528000","regIndex":0,"blackboxYn":"Y","groupableYn":"N","controllableYn":"N","combinedProductYn":"N","masterYn":"Y","snapshot":{"mid":93499558,"online":true,"styler":{"initialBit":"INITIAL_BIT_OFF","buzzer":"NOT_DEFINE_VALUE value:69","reserveTimeMinute":0,"initialTimeMinute":30,"preState":"POWEROFF","energyMonitoring":452,"error":"ERROR_NO","nightDry":"NIGHTDRY_OFF","remainTimeMinute":30,"reserveTimeHour":0,"smartCourse":"NONE","currentDownloadCourse4":0,"childLock":"CHILDLOCK_OFF","remainTimeHour":1,"remoteStart":"REMOTE_START_ON","currentDownloadCourse1":"PANTS","course":"DRYING_NORMAL","currentDownloadCourse3":0,"currentDownloadCourse2":66,"state":"INITIAL","endMelody":"END_MELODY_1","currentDownloadCourseCount":1,"initialTimeHour":1},"static":{"deviceType":"203","countryCode":"HK"},"meta":{"allDeviceInfoUpdate":false,"messageId":"nuj2ON7eQCK3Jnf9M8uOFQ"},"timestamp":1645341557315},"manufacture":null,"online":true,"platformType":"thinq2","homeDeviceOrder":1,"roomDeviceOrder":-1,"ownershipYn":"N","modelJsonVer":"51.6","modelJsonUri":"https://objectcontent.lgthinq.com/1762d6bf-d076-43d1-97f6-6f7bb89fd2b2?hdnts=exp=1675997742~hmac=f7ea2c55ad32ca82c79a7aa32bc766cd1f57b64231319d39ae6de5515f345a4a","appModuleVer":"6.21","appModuleUri":"https://objectcontent.lgthinq.com/ea54eb02-d923-4bf8-b6b7-6cef48783849?hdnts=exp=1705894666~hmac=da9f0fcb47f96863814304ec250639c83e7b3b5400ff0e84e7be0162df4c2f6a","appRestartYn":"Y","appModuleSize":"10013123","langPackProductTypeVer":"54.02","langPackProductTypeUri":"https://objectcontent.lgthinq.com/946096ff-33e5-4b2d-b7de-9150e5b62aca?hdnts=exp=1708050397~hmac=4b033e20ce9f69a31ff141d3a85b144a2dfe0e87ead3e399da65d771d29ac66f","langPackModelVer":null,"langPackModelUri":null,"roomId":"","fwInfoList":[{"checksum":"000046E3","partNumber":"SAA37569132","order":2},{"checksum":"00001678","partNumber":"SAA37569015","order":1}],"modemInfo":{"modelName":"S3BF_POD_DN4","appVersion":"clip_hna_v1.9.116","modemType":"QCOM_QCA4010","ruleEngine":"y"},"existsEntryPopup":"N","fwVer":null,"modemVer":null,"subDeviceCount":0,"firebaseLogKey":"T:ST-S:ST-U:SLIM-P:ESSENCE","cardType":"Small","cardControl":"Base","detailDeviceCode":null,"upgradableYn":"N","autoFwDownloadYn":"N"}
[2/20/2022, 3:20:08 PM] [LGThinQ] [Styler] Setting up device!
[2/20/2022, 3:20:08 PM] [LGThinQ] Device not supported: a02e96b2-41b3-1088-9000-acf108c5ab18: Styler (STYLER S3BF_POD_DN4)

I just added Styler support in latest version
open new issue if you got any related error


Add slides of SM3 talk to main readme

http://cgmartini.nl/images/stories/workshop2021/lectures/second/riccardo/2021-09-02_MartiniWorkshop2021_Small_molecules-vFINAL.pdf

Added 9b8521d209e9743280b1ecbd43af7d99e486c9af.


Make 0th power of a sparse array/matrix return the identity with the same dtype

Reference issue

gh-15224
What does this implement/fix?

This PR fixes spmatrix.__pow__ to return the identity of the same dtype with self for 0th power.
Additional information

N/A

Sure. I've fixed the test.

Merged, thanks @takagi !


[GPII-4058]: Fix sensitive data filtering

This is a regression, introduced in https://github.com/gpii-ops/gpii-infra/pull/420/files#diff-e0a4c9132be9f827cd9f13dc69eaceedR72
String comparisons looks pretty ugly, but so is the way rake task arguments work.

Btw, optional output stream merging for sh_filter was added in #135 per @stepanstipl request, and I still have doubts that we need it.

Thanks for looking into this @natarajaya, LGTM 👍, and sorry as it seemed to be introduced by my change.
I think that as the rake tasks are currently written/used is quite confusing and will bite us back (it was my change, but 3 people reviewed without noticing the issue -> shouts unclear code to me), but that's probably out of scope here, but perhaps something to remember when we discuss the technical debt.
It would be good to fix the underlying problem of not filtering sensitive data in stderr stream. Going over the conversation from #135 - there's one thing that I didn't realize then: from a developer's perspective this is highly unexpected. If I enable preserve_stderr, I would not expect that sensitive output filtering would suddenly stop working. And I still believe that deliberately merging streams is undesirable, again something non-standard and unexpected. So in long-term IMHO it would be best to remove that preserve_stderr option and fix filtering for both streams (without merging them).

LGTM

@stepanstipl

3 people reviewed without noticing the issue -> shouts unclear code to me

This is not the kind of error I expect code review to catch. Code review is not designed to be, and will never be, a replacement for thorough testing.


Urdu text

Description of the new feature / enhancement
Urdu Text Copy feature
Scenario when this would be used?
Urdu Text Copy feature
Supporting information
Urdu Text Copy feature

Hi @Liaqatofficial
Can you please elaborate on the request?
Isn't this something you can already do with Windows Character Map?
/needinfo

Windows supports Urdu font but copy feature does not support copy urdu from the screen

what copy feature? Can you help us understand this a bit more?  /needinfo


[Azure.Core] Remove PrettyPrint from ModelSerializerOptions

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Core


Cannot save bad channels

Originally had the issue that I couldn't open a nwb file without a "bad" channel column, but it looks like that has been addressed in #85 , so I installed the newest version of ecogVIS using the "setup.py" file. Is there a way of saving bad channels without having an existing bad channels column?

hi @cbin-cnl , did the problem of opening a file get solved on your end?
Do you get any specific error when trying to save a new file? If yes, can you copy the error track (printed in the terminal)?

Hi Luiz,
Yes I can open the file and add channels, but the gui crashes once I try to save. The error message is below:
Traceback (most recent call last):   File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/ecogvis-1.0.1-py3.6.egg/ecogvis/ecogvis.py", line 530, in save_badchannel     self.model.BadChannelSave()   File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/ecogvis-1.0.1-py3.6.egg/ecogvis/functions/subFunctions.py", line 748, in BadChannelSave     self.nwb.electrodes['bad'].data[indices] = aux   File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/hdmf/common/table.py", line 504, in __getitem__     raise KeyError(key) KeyError: 'bad'

thanks for the report! I'll check it

@cbin-cnl it seems like you're not using the most updated code, could you please try installing the current repo version of EcogVIS in your working environment?
$ pip uninstall ecogvis
$ git clone https://github.com/catalystneuro/ecogVIS.git
$ cd ecogVIS
$ pip install .

I couldn't reproduce the error locally, this is probably because of some changes in ecogvis that were not published to pypi yet. If it's not urgent, you can also wait a couple of days max and I'll be releasing a new version, so you can upgrade through pip.

Hi Luiz, thanks for the quick response.
Unfortunately updating the code did not work, I still get the following error:
File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/ecogvis/ecogvis.py", line 530, in save_badchannel
self.model.BadChannelSave()
File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/ecogvis/functions/subFunctions.py", line 744, in BadChannelSave
self.nwb.electrodes['bad'].data[:] = aux
File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/hdmf/common/table.py", line 504, in __getitem__
    raise KeyError(key)
KeyError: 'bad'

To clarify, I can open the file fine, but cannot save the channels unless the NWB file already has a "bad" electrodes column.
Thanks again

of course, I can see it now
I'll put a fix for this in the current PR and let you know once it's merged!

Great thanks so much!

@cbin-cnl it took a bit, sorry, the merge is in place.
could you please confirm this solved the problem on your end?

Hi Luiz,
Unfortunately it still looks like there is a problem with adding a column to an existing Electrode table. I'm getting the following error:
    self.model.BadChannelSave()
  File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/ecogvis-1.1.0-py3.6.egg/ecogvis/functions/subFunctions.py", line 765, in BadChannelSave
    data=aux,
  File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/hdmf/utils.py", line 483, in func_call
    return func(args[0], **parsed['args'])
  File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/pynwb/file.py", line 494, in add_electrode_column
    call_docval_func(self.electrodes.add_column, kwargs)
  File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/hdmf/utils.py", line 364, in call_docval_func
    return func(*fargs, **fkwargs)
  File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/hdmf/utils.py", line 483, in func_call
    return func(args[0], **parsed['args'])
  File "/home/cbin-user/tdt2nwb/ecogvis/lib/python3.6/site-packages/hdmf/common/table.py", line 462, in add_column
    raise ValueError("column must have the same number of rows as 'id'")
ValueError: column must have the same number of rows as 'id'
Aborted (core dumped)

However, I think I can just ensure I have a "bad" channels column in my electrode table. Thank you.

I'll get this fix, thanks for reporting it

@cbin-cnl I managed to reproduce your error now
is it the case that your electricalseries is mapped to a subset of electrodes smaller than the total number of electrodes? Just to make sure we found the same problem
I'll fix it


Publish the API builds somewhere

[ ] Publish at least Windows builds.
[ ] Add link to the files to README.

ok so I can do that also with a bit more travis magic, principle is each build uploads to a different branch instead of gh-pages, then we link the artifacts using ...?/raw/ in the url to the file and people can download it. I'll build a PR with it when the doxygen thing is stable.

That would be very cool, thank you! :)
But which place should be used to store the data? This is the main problem which stoped me from implementing this feature. As far as I understood GitHub actions doesn't provide storage unfortunately.
We may ask AIArena devs for hosting but I am not sure.

they go to github, into branches that only contain the artifact, the links I posted use this to build the osx artifact : https://github.com/lip6/libDDD/blob/master/.travis.yml#L65 this sets the deploy to go to another branch than gh-pages (the default)

Git is pretty bad at storing binary artefacts. It would be much better to put those file on some kind of storage.

well we don't keep history of the binaries, the point is mostly to host everything in the same place on github. Git is not great at binaries, but Github is great at providing us scaleable storage/distribution platform. They put a limit on artifact size at 100 MB files/1 GB total, which is enough for this easily.
We could publish an archive like the one that existed in "Precompiled libs" of https://github.com/Blizzard/s2client-api readme, for each OS. These would be snapshots, in sync with latest "master".
I believe there is also a way to deploy to github "releases" for longer term storage, but perhaps this can be done manually after tagging the release.

I understand, but if we simply 'commit' new data, the repository will bloat. If we do things like rebase+force-push, it could be better, but we will lost possibility to provide different versions of the API for different game clients. I would like to support this feature and let developer decide which version he want to use. Such approach also allows us e.g. to keep several branches (one branch per game version) and do specific fixes there. As a result, it is more flexible.

I'll prototype a version on my fork, that provides Release versions for the three platforms. We can always  store artifacts on a named branch like 1.1_win to keep versions or use the "release" feature of gh.

i'll build artifacts with a time stamp cpp-sc<IP_ADDRESS>.201909101240 as snapshots we can discuss how to archive the versions that are considered stable

first attempt visible here https://github.com/yanntm/cpp-sc2/tree/linux, by browsing linux or osx branches. The deployment for win is still failing (some / or \ path issue it seems).
I just dumped the whole build/ folder to gh in this version.
Is there a "make install" or "make dist" we can invoke to package the headers and stuff into a folder structure like the artifact/zip blizz distributed ?

Is there a "make install" or "make dist"

Unfortunately, no, it should be implemented in cmake by hand.
To be honest I am not fan of storing binary data in git as git is for code, not for artifacts. I would rather pay for files hosting instead or host it on my machine. So I suggest not hurry on implementation of this ticket.

Also, in case of Linux it would be much better to provide a RPM package.

so there is this CPack tool for building distributions apparently as msi/rpm if that is what we want to go for.
https://gitlab.kitware.com/cmake/community/wikis/doc/cpack/PackageGenerators
but it is not configured currently, and I've no familiarity with it (I use automake not cmake)
Still, it seems pretty easy to set up, just basically cite what files you want to grab (for us we want include/ lib/ and the simple bot example with sources).
The hosting and the building of a package are two different issues, travis has many other deployment adapters if you really don't like leveraging gh to host us in this manner.

cmake shouldn't trigger neither msi, nor rpm builds, although it is possible, but some third-party build system should. Also, manual publishing of packages could be an option, too, as we don't build packages each night.

But I've been using this branches mechanism to hold my artefacts for at least a couple years now, with history crushing activated, there is no bad bloating issue for the repo imho.

There is nothing that could broke, it just increases the size of your repo, as every version of binary is stored somewhere as is and there is no way to transfer only changes like git usually do with the text files. I got nice experience of conversion of SVN repos with binary files to git repo. A single repo could be like 200 MB during checkout. Of course there are several ways to decrease the size, including aggressive history modification, but I would rather avoid it.
I need to think more about it, that's why I suggest to postpone further activity in this issue.

We may ask AIArena devs for hosting but I am not sure.
No problem, you could also automate the deploy using scp or something.

Fixed in add73174331da797e808c37b2c96933e8153e5cf


3.5.3 wont build memory heap error

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x ] 3.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

When trying to build --prod I get memory heap error
Expected behavior:

App should build.
Steps to reproduce:

Related code:
insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
I already rolled back so not relevant to the issue but here is my info.
Cordova CLI: 6.5.0
Ionic Framework Version: 3.4.2
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.7
ios-deploy version: 1.8.6
ios-sim version: 5.0.13
OS: macOS Sierra
Node Version: v6.9.2
Xcode version: Xcode 8.0 Build version 8A218a

This issue was moved to ionic-team/ionic-app-scripts#1125


Move type based functions into type folders

Cozy up. Going to get Comfy!

This PR is the second in a series focused on moving onto a more mono-repo friendly structure. This PR takes care of moving the Type-specific functions into their respective Type folders. Shared or non-specific functions stay where they are.

Coverage remained the same at 100.0% when pulling 54ce21211081ded4898ab83bc87de365319c97cd on move-type-funcs into e2b5f5999f28bd6e8799350b97a31f21fe759167 on master.

Coverage remained the same at 100.0% when pulling 54ce21211081ded4898ab83bc87de365319c97cd on move-type-funcs into e2b5f5999f28bd6e8799350b97a31f21fe759167 on master.


Copy&Paste causes daemon panic

Pasting a longer string into the daemon console causes the daemon process to panic, closing all csshw windows.
Example string: abcdefghijklmnopqrstuvwxyz
It panics at line 136 in src/daemon/main.rs.

With change https://github.com/whme/csshw/commit/fa162bd2a6a4e90d656b9968272f31d5c483dffd it looks like the daemon isn't the one panicking anymore. Copying smaller amounts of data works but when copying larger amounts, more often than not only a few clients die while the daemon remains active as long as one client survives.
Indicating that the problem might have been fixed from daemon side but another problem still persists on client side.

With 0.9.4 we might get logs of the panic and be able to figure out whats wrong.

With change 5787428e8e9018e1e6c510d8b974b4de42f39852 the previous daemon side "fix" (fa162bd2a6a4e90d656b9968272f31d5c483dffd) has been reverted.
Copying up to 500 words works consistently now, larger texts still causes crashes.

Fixed with 0.13.0


Transform and Matrix UI elements get out of sync

Godot version:

a71a5fc0c3f5d487d3f18c3b9e9a768052795e86
OS/device including version:

Linux
Issue description:

Steps to reproduce:
Change the Transform and Matrix values, move the 3D gismo.
Minimal reproduction project:

2018-08-09-transform-ui.zip

The issue is that moving gizmos only update translation/rotation/scale, but not the transform matrix. You need to reselect node to update matrix.

Changing transform in the inspector works fine now, gizmo still doesn't update transform in 15a9767

Fixed in 5d9cab3


Bnewbold/rainbow safe account fix2

fixes and rebase from #845

the indexer/metrics.go usersAddedToCatchupQueue addition is unused; gonna drop that.
iirc @ericvolp12 wrote these change initially, @bnewbold posted them as a PR, so I should LGTM them :-D
when it's green again after the dead code drop I'll merge.


[feature] Adding analysis items from the perspective of license

When we analyze open source projects, we rarely analyze it from the perspective of licenses. We can even add ONE module to discuss licenses. For example, the relationship between the repo owner’s working time zone and the repo’s license.

Good idea and actually license information is already in the records and we can use it directly.


Add Swift toggle to deploy.sh

This is introduced so that swift can be disabled for a ceph gate scenario
/etc/openstack_deploy/conf.d/swift.yml is removed if swift is
disabled so that it's containers are not created. The swift playbooks will
still run, but no hosts will match so the tasks will be skipped.
Related: #732
(cherry picked from commit 2060c4c69586e0de3925a450f65570b2a11c4de8)

:+1:

:+1:


JS: add verifyTransactionSyntactic() and blockBytes() utils methods

Description of change
Add verifyTransactionSyntactic() and blockBytes() utils methods
I decided to go for blockBytes() instead of blockHashWithoutNonce() so one can also get the byte length of the block which is also needed to know the required difficulty for the PoW and hashing can be done just with other Blake2b libraries. Also being able to get the full block bytes might be useful for other things unrelated to PoW.
        const blockBytes = Utils.blockBytes(block);
        // -8 to remove the nonce bytes
        const hash = Blake2b.sum256(blockBytes.slice(0, blockBytes.length - 8));

Links to any relevant issues
Closes #1786
Type of change

Enhancement (a non-breaking change which adds functionality)

How the change has been tested
const console = require('console');
const { Utils } = require('../node/lib');

async function run() {
    try {
        let block = { "protocolVersion": 2, "parents": ["0x2d86df699d2e0bb47a970911f7793333e876b845ed6079bc51ea113ccf76ffe7", "0xd89f65a6a0d2a44e75e63cb615327e722ba5eae0b20bf71ed5abba11913adc09"], "payload": { "type": 5, "tag": "0x484f524e4554205370616d6d6572", "data": "0x57652061726520616c6c206d616465206f662073746172647573742e0a436f756e743a20373035393434360a54696d657374616d703a20323032342d30312d31375430393a32313a33305a0a54697073656c656374696f6e3a20383037c2b573" }, "nonce": "755469" }

        console.log(Utils.blockBytes(block))

        const protocolParameters = {
            version: 2,
            networkName: 'testnet-2',
            bech32Hrp: 'rms',
            minPowScore: 1500,
            belowMaxDepth: 15,
            rentStructure: {
                vByteCost: 100,
                vByteFactorData: 1,
                vByteFactorKey: 10,
            },
            tokenSupply: '288230376151711743',
        };

        const transaction = {
            type: 6,
            essence: {
                type: 1,
                networkId: '7784367046153662236',
                inputsCommitment:
                    '0xa1278d9142ea91a18ed304e42f89a1a9ced4d95f3c9f2912e13836584a7b43f0',
                inputs: [
                    {
                        type: 0,
                        transactionId:
                            '0xa892f30f1180515c7dd7578c54cc9dcaf0f707ea1eb44e74587a9d9924593eee',
                        transactionOutputIndex: 1,
                    },
                ],
                outputs: [
                    {
                        type: 3,
                        amount: '1000000',
                        unlockConditions: [
                            {
                                type: 0,
                                address: {
                                    type: 0,
                                    pubKeyHash:
                                        '0x194eb32b9b6c61207192c7073562a0b3adf50a7c1f268182b552ec8999380acb',
                                },
                            },
                        ],
                    },
                    {
                        type: 3,
                        amount: '1',
                        unlockConditions: [
                            {
                                type: 0,
                                address: {
                                    type: 0,
                                    pubKeyHash:
                                        '0x7ffec9e1233204d9c6dce6812b1539ee96af691ca2e4d9065daa85907d33e5d3',
                                },
                            },
                        ],
                    },
                ],
            },
            unlocks: [
                {
                    type: 0,
                    signature: {
                        type: 0,
                        publicKey:
                            '0x67b7fc3f78763c9394fc4fcdb52cf3a973b6e064bdc3defb40a6cb2c880e6f5c',
                        signature:
                            '0x900d31c0a0a63be73ae8b88f47be6fc3aade566774f8a53fbd8393ba43945c26197aa61de923d375bbf47dca54134bdc26dcdc4d7a815fedc7d54298d400ae0c',
                    },
                },
            ],
        };

        console.log(Utils.verifyTransactionSyntactic(transaction, protocolParameters))

    } catch (e) {
        console.error(e)
    }
}

run();

@schierlm are you fine with blockBytes() for the reason mentioned in the PR description?

@schierlm are you fine with blockBytes() for the reason mentioned in the PR description?

Yes, that's fine. I was trying to keep the API consistent with other utils functions that rather return the hash than the raw data. Also, while another dependency like https://github.com/mafintosh/blake2b-wasm is not large, it is obviosuly larger than not using a dependency, especially since the huge WASM blob from iota-sdk includes a blake2b implementation anyway.


Fix for UserAgent.h issues

Identical to https://github.com/FirebaseExtended/flutterfire/pull/2099 but with the firebase_crashlytics CHANGELOG merge issue and analyzer warnings fixed.
Remove the UserAgent.h header in favor of defining LIBRARY_VERSION and LIBRARY_NAME in the GCC_PREPROCESSOR_DEFINITIONS in the podspec.
Fixes https://github.com/FirebaseExtended/flutterfire/issues/2087
Fixes https://github.com/FirebaseExtended/flutterfire/issues/1858
Fixes https://github.com/FirebaseExtended/flutterfire/issues/2084

New analyzer warning for change introduced in #1686.  Fixing in this PR.  I guess the analyzer options aren't pegged to a version in this repo?
\cc @collinjackson

Manually merged with https://github.com/FirebaseExtended/flutterfire/commit/4d7b2bdd7fbdee65551754968b140653ea16128f to maintain authorship.  Closing.

0.15.5+3 not published yet, can you publish it ? @collinjackson

Besides firebase_auth, I seem to also still have an issue with firebase_storage:
    /Users/anthony/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_storage-3.1.3/ios/Classes/FLTFirebaseStoragePlugin.m:6:9: fatal error: 'UserAgent.h' file not found
    #import "UserAgent.h"
            ^~~~~~~~~~~~~
    1 error generated.

@jmagman
Thanks, the build error was fixed 👍
But, after this change, bitcode_strip started failed on iOS project which bitcode enabled.

2020-03-16 02:13:56.970 xcodebuild[26510:54603] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/Runner_2020-03-16_02-13-56.965.xcdistributionlogs'.
error: exportArchive: bitcode_strip failed
Error Domain=IDEFoundationErrorDomain Code=1 "bitcode_strip failed" UserInfo={NSLocalizedDescription=bitcode_strip failed}

@mono0926 please file a new issue at flutter/flutter and fill out the template so we can take a look.

so which version should I use? 0.15.5+2 still seeing same issue.

Same UserAgent.h issue on version 0.15.5+2, when 0.15.5+3 will be released?

finally it's released now firebase-auth: 0.15.5+3


Certain PDFs return errors requiring poppler-utils to be installed in base image

When processing certain PDFs, I encounter the following error.  I've forked the repo and added these dependencies as well as the separate fixes from @harun27 (which fixes the errors below).

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/cli.py", line 89, in <module>
    sys.exit(main())  # pragma: no cover
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/cli.py", line 79, in main
    res = run_mode(mode, tag)
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/ocr_joplin_notes.py", line 79, in run_mode
    return full_run(tag)
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/ocr_joplin_notes.py", line 91, in full_run
    return perform_on_tagged_notes(perform_ocr_for_note, tag_id)
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/joplin_api.py", line 75, in perform_on_tagged_notes
    usage_function(note.get("id"))
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/ocr_joplin_notes.py", line 146, in perform_ocr_for_note
    result_tag = ocr_resources(note)
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/ocr_joplin_notes.py", line 160, in ocr_resources
    data = ocr_resource(resource, ADD_PREVIEWS and note.markup_language == 2)
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/ocr_joplin_notes.py", line 225, in ocr_resource
    ocr_result = extract_text_from_pdf(full_path, language=LANGUAGE)
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/file_ocr.py", line 80, in extract_text_from_pdf
    extracted_image = pdf_page_as_image(filename, i)
  File "/usr/local/lib/python3.9/site-packages/ocr_joplin_notes/file_ocr.py", line 30, in pdf_page_as_image
    pages = convert_from_path(filename, dpi=600, grayscale=True)
  File "/usr/local/lib/python3.9/site-packages/pdf2image/pdf2image.py", line 98, in convert_from_path
    page_count = pdfinfo_from_path(pdf_path, userpw, poppler_path=poppler_path)["Pages"]
  File "/usr/local/lib/python3.9/site-packages/pdf2image/pdf2image.py", line 484, in pdfinfo_from_path
    raise PDFInfoNotInstalledError(
pdf2image.exceptions.PDFInfoNotInstalledError: Unable to get page count. Is poppler installed and in PATH?
Starting OCR for tag ojn_yes.

The key error above is this one:
raise PDFInfoNotInstalledError(
pdf2image.exceptions.PDFInfoNotInstalledError: Unable to get page count. Is poppler installed and in PATH?
This is fixed by installing the poppler-utils in the Dockerfile.

Thanks for reporting this. It has been fixed in the latest release, 0.3.3


NIFI-10785 Allow publishing AMQP message with null header value

Summary
NIFI-10785
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 8
[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

The branch name was correct, but I mistyped the ticket name in the commit message, hence the force push.

Will review

Thanks Nandor, I verified PublishAMQP can publish null header values and then ConsumeAMQP will retrieve them an interpret them correctly. I also verified that a warning is thrown when 'Ignore Null Header = true' but suggested a change to the naming and usage. Otherwise, looks good to me.

Thank you @thenatog and @turcsanyip for your reviews! I've implemented the requested changes.

+1 will merge


Forum page doesn't support dark mode

Is your feature request related to a problem? Please describe.

When switch to dark mode on home page, it automatically gets to light mode in forum page.
Describe the solution you'd like
I can add a similar button on the forum page for changing between dark and light modes.
Describe alternatives you've considered
The state from the home page can be kept when switching to the forum page.
Additional context
NA

Assigned!

BTW, I really liked your initiative towards sex edi\ucation in India by creating this website.

Thank you❤

Can you assign this to me too?


Support serialized defaults

Sometimes it is useful to set default serialized attributes in db level. Rails caches this nicely, but deep clone fails. This is bugfix.

In essence, you've replaced write_attribute by raw_write_attribute, right? I'll check out your code later so I can test the differences. Unfortunately the Travis build fails now, do you think you can fix that?

@moiristo yes, seems like default attributes saved in raw format in table definition and cannot be written as is in general. The fails can be rails issue - the modern versions 4.1, 4.2 works fine, The workaround can be just not specifying attribute type for serialization, as I done here

I tried the code and it works fine for me. As you suggested, I removed the attribute type to keep Travis happy. Thanks for the PR!


Fix AWS request validations which are always validating true

The AlexaRubyKit::valid_alexa? implementation was broken, and failing open due to a glitch in the boolean logic. This addresses that bug, and adds a specific test for it.
The bug was a bit obscured in the should raise an exception when an invalid request is sent test, because it was matching on any error — in this case, #<NoMethodError: undefined method []' for nil:NilClass>` was firing and passing the test.
Rspec was raising a warning about the unclear matching, which this also addresses.

WARNING: Using the raise_error matcher without providing a specific error or message risks false positives, since raise_error will match when Ruby raises a NoMethodError, NameError or ArgumentError, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<NoMethodError: undefined method `[]' for nil:NilClass>. Instead consider providing a specific error class or message.

Oh my, thanks for catching that!


Infinispan + Jakarta fixes

Convert to Jakarta. This fixes most of the failures, but there are 3 remaining broken tests that will need further adjustments.

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I formatted the code using mvn -Pformat,fastinstall install && mvn -Psourcecheck

Should we merge this so next CI build have this included, we have next week to continue fixing tests

Should we merge this so next CI build have this included, we have next week to continue fixing tests

Yes, let's merge this one even though it's not 100% complete (there's 3 tests failing). The remaining ones need to be analyzed more carefully.


white list not working? tineye.com

firefox v54
Skip Redirect v2.2.0
reference page:
http://www.news.com.au/travel/travel-updates/incidents/old-us-naval-intelligence-photo-said-to-show-amelia-earhart-her-copilot-and-the-wreck-of-her-aircraft/news-story/c0d11fb1d75b1996033716145af63185
i have an extension installed that allows reverse image searching - when i try to do a reverse image search for the first photo in the reference page on tineye.com, the redirect is always cleaned despite tineye.com being whitelisted
things i've tried in the whitelist include...
http://www.tineye.com/* *://*.tineye.com/* http://www.tineye.com/search/?url=http%3A%2F%2Fcdn.newsapi.com.au%2Fimage%2Fv1%2F8794938b88e8f3427bf8c78df804b0d3

You have to use the blacklist.

The white list and the black list do seem to be reversed from what I would assume theoy do upon first hearing the name.


Parameters in the Docker container settings are not taken into account

Simple docker app created as shown above

Parameters are not serialized in the container's configuration, whereas volumes and ports behave as expected.
Tested on Marathon 0.11.0, Mesos 0.24.1, bento/centos-7.1 bare image with vagrant.

This is fixed by the recent UI modal refactor (https://github.com/mesosphere/marathon-ui/pull/209)
It is an existing bug in Marathon 0.11.0

Hi @heyMcFly, thanks for your detailed bug report! We have fixed in an extensive refactoring exercise recently. We just tagged a new release of the UI so we hope to have that out for our users soon.
This bug only seems to affect cases where a Docker application is used. You can work around this limitation by using the edit button to add environment variables.
In the meantime I'll close this ticket as a known issue.

You're welcome, and thanks for the heads up.
Cheers

We're able to supply a fix to this in the forthcoming 0.11.1, so reopening on that basis.

Fixed in mesosphere/marathon-ui#290

Hey @heyMcFly we fixed that issue. There is an RC version 0.11.1-RC1 which includes the fix. Would be cool, if you could try that version. If everything goes well, we will do the 0.11.1 release tomorrow.


Ibid. ambiguity

When using a citation style that supports "Ibid." (I am using "chicago-fullnote-bibliography") I have noticed that pandoc-citeproc produces ambiguous or wrong results. Consider this example:
Sentence 1. [@a]
Sentence 2.^[Many examples can be found in the Babylonian Talmud.]
Sentence 3. [@a]
After Sentence 3 the source is rendered as "Ibid.". It should print the normal citation instead since after sentence 2 we have another footnote. (A similar example in LibreOffice with Zotero works just fine. Is it possible that pandoc-citeproc does not take "near-note" into account?)
The same also applies for author-date styles that use "Ibid." if we enter a manual citation from a classical source like the bible between two identical sources:
Sentence [@a]. Sentence (see Exodus 1:1). Sentence 3 [@a].
==> Sentence (a). Sentence (see Exodus 1:1). Sentence 3 (ibid.).
In BibLaTeX there is a command "\mancite" that prevents the wrong "ibid.". Perhaps it might be feasible to implement something like this in pandoc-citeproc?

I would guess that this is almost certainly related to #53 and #53

Just in case, someone has the same problem. This filter is not a official solution, but it helps a bit.


Vscode cannot authenticate with github, cannot use code tunnel

Does this issue occur when all extensions are disabled?: Yes/No
Yes

VS Code Version: code-insiders_1.78.0-1682055632_amd64.deb, as well as default code install (using installation instructions)
OS Version: Ubuntu 22.04 LTS

I am trying to use code server to setup a code tunnel, and the server will not start. I have uninstalled and reinstalled code several times. I am currently using the GUI version, but would like to use the cli to start a code tunnel. This behavior was previously working, nothing changed with my setup. (As far as I know.)
I think the issue is that I cannot get github to authenticate my account, no matter what I do.
Maybe there is an answer online, but I cannot find anything after several hours of looking. It seems like something changed with the authentication, but I am not sure.
Steps to Reproduce:

open fresh vscode install
click on "Turn on remote tunnel access"
Try to authenticate github, brings up a blank wepbage, every time.

Alternatively:

run "code tunnel --verbose"
see "*

Visual Studio Code Server

By using the software, you agree to
the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).

[2023-04-22 21:33:54] debug starting as new singleton
"
and it hangs here forever.

Both those problems would hint to me there's some network issue preventing authentication with Github, since the GUI and CLI use two distinct authentication paths. Are you able to curl https://github.com from the command line?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Cannot click "View all"

Cannot click on these buttons labled "View all" in The Listen Now and Browse tab.

62b2f4c7c3b3f4a4e896f4647ddd5e5c866c041f fixes this


Retry ElasticSearch queries on timeout

We've been having some transient issues where Cabot alerts time out connecting to ES. Reading through the docs, timeouts are considered a special case and do not retry by default. This PR turns on retries.
This could have bad effects - if ES is down, this could leave a ton of tasks hanging...maybe lower the timeout from 30s to 15s?

trigger build

I talked to @elainearbaugh about this, and she had a few concerns:

This is a client-side timeout, so queries don't get cancelled on retry. If the cause of the timeout is a bad query that is taking forever to finish, this will just put triple the load on the ES cluster as it tries again.
The problem might just be that the timeout isn't long enough. We can bump this through the Django admin panel.

For now, we just increased the timeout for the problem ES cluster. If that doesn't fix the problem, we'll revisit this PR.


[stable/jenkins] spec.resources.requests.storage: Forbidden: field can not be less than previous value

helm upgrade jenkins failed
[root@master01 ~]# helm -n jenkins upgrade  --set agent.runAsGroup=docker jenkins-blueocean stable/jenkins
Error: UPGRADE FAILED: cannot patch "jenkins-blueocean" with kind PersistentVolumeClaim: PersistentVolumeClaim "jenkins-blueocean" is invalid: [spec: Forbidden: is immutable after creation except resources.requests for bound claims, spec.resources.requests.storage: Forbidden: field can not be less than previous value]

[root@master01 ~]# helm version
version.BuildInfo{Version:"v3.3.0", GitCommit:"8a4aeec08d67a7b84472007529e8097ec3742105", GitTreeState:"dirty", GoVersion:"go1.14.7"}

📢 stable/jenkins has moved to https://github.com/jenkinsci/helm-charts. If still applicable, please reopen the issue there. Thanks!


firebase.messaging().onMessage fires on each opened tab

Hi. When one of several tabs is focused and then new push message is came, messaging.onMessage fires on each tab. I think, it will be useful when messaging.onMessage fires only on currently focused tab

I found the solution).  Using service worker 'push' event handler with custom behavior logic instead of using firebase messaging inside service worker.


Dataset random invariant ID not unique

Multiple submissions by the same contributor can have the same Dataset random invariant ID in the output excel file (cell C12 in the "submission" sheet). Shouldn't this ID be unique to each excel file?

Hi Andy,
I am not sure exactly how this is happening and would need visibility on how people are using the tool to be sure. At the moment, the "Dataset random invariant ID" is created by the tool when the Dataset Configuration (and therefore the associated xml file) is first saved. As such, if the user edits an existing dataset configuration to set up other datasets (as opposed to using the "New" button) it would result in the same "Dataset random Invariant ID" being submitted twice.
This ID was implemented as the "Dataset Reference" and "Timeseries Reference" would change if the dataset configuration xml or timeseries data file respectively were changed at all. This could lead to a situation whereby changes immaterial to the data or the analysis (eg - changing a column header) would lead to different references and so an ID tied to the dataset configuration file was felt to be useful. However, given this is being replicated across submissions for presumably different datasets we may need to rethink how this is being handled.
Thanks,
Lee.

@peterdougstuart instead of a random integer, which can remain the same if people edit the xmls through a text file. Perhaps something related to the time of the files creation might prove more useful? If the time is always the same across different datasets in a submission (see Andy's inital post), we can infer that the contributor is editing a previous xml to create new datasets instead of using "New" in the UI.

what about using the hash() function? Will give you a unique, but consistent, number for a string. It's used for dictionary keys, for example if you want your class to be able to be a dictionary key you have to define the .__hash__(self) method.

Hi Joe,
We use a hash of the contents of the xml to provide an ID that corresponds to the dataset config at the time it is run (code here). The ID we are discussing is a simple 6 digit random number that is created at the time the user first saves the xml through the UI. The intention is different from the hash of the file contents; we do not want it to change every time the user makes a change to the config. It is intended to be a simple check that the user is not submitting the same dataset twice with changes to the analysis/dataset configuration (in this case the hash would change, but the random invariant ID would be the same).
I think the problem is that some users have probably created config xmls for a new dataset by simply editing old ones, and so the ID is the same for different submissions. If the ID inferred the datetime of the file initial creation we could see if that was the case.

We are no loner actively using this concept as our users are too clever and manually editing the xml configs. As such the dataset invariant random ID is often replicated within a submission.

Before we close this, do we actually need to migrate this to a different issue that says "generate unique identifier for each dataset somehow so that contributions can be told apart"?The data processing is muuuch easier when the data each have unique IDs. I could add these at run time I suppose during the analysis process, but it's helpful to have something that goes right the way back to the contributor. On 17 May 2017 17:49, Lee Cameron<EMAIL_ADDRESS>wrote:We are no loner actively using this concept as our users are too clever and manually editing the xml configs. As such the dataset invariant random ID is often replicated within a submission.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

We will still have a unique identifier for each submission (the full hash of the contents of the configuration) which we can use for this purpose. It is not currently written out in the summary document (Summary.xls in the .zip file) but is the name of the detailed report for each individual dataset (looks something like 47d623e20be8b22bda6af97bd15b1fad45693a0e for example) and is given as Dataset Reference on the cover sheet of the detailed reports. Is that OK for your purposes?
I will open a new issue (referencing this one) to ensure we put the dataset unique ID the Summary.xls workbook.


Ship should persist terraform state

Expected behavior
Terraform state is contained within ship state
Actual behavior
Terraform state is contained within a file in the relevant folder
Information

Ship version: 0.20.0

+1 on this. The feature wont really be ready for production use until this is done.

I see three ways to do this:

The terraform lifecycle step writes the tfstate to the relevant folder before Terraform runs, and backs it up afterwards
We implement an HTTP backend for Terraform and use that
We implement a custom backend of some sort (I am not positive Terraform supports custom backends)


[ace] tao windows arm

246>CustomBuild:
         This version of C:\v\vcpkg4\buildtrees\ace\arm64-windows-rel\bin\tao_idl.exe is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.
   248>CustomBuild:
         This version of C:\v\vcpkg4\buildtrees\ace\arm64-windows-rel\bin\tao_idl.exe is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.
         Invoking ""..\..\..\bin\tao_idl" on Compression_include.pidl"
   246>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(249,5): error MSB8066: Custom build for 'TC_IIOP.idl' exited with code 1. [C:\v\vcpkg4\buildtrees\ace\arm64-windows-rel\TAO\tao\TransportCurrent\TC_IIOP_Idl.vcxproj]
   246>Done Building Project "C:\v\vcpkg4\buildtrees\ace\arm64-windows-rel\TAO\tao\TransportCurrent\TC_IIOP_Idl.vcxproj" (Rebuild target(s)) -- FAILED.

You can only build this feature on windows arm if you are using an arm windows version.

This could be supported when there you would build a host version of tao_idl which you use in the cross compile, tao_idl is a code generator used by the build which must run on the host system.

This could be supported when there you would build a host version of tao_idl which you use in the cross compile, tao_idl is a code generator used by the build which must run on the host system.

How to pass host tao_idl to build system?

You need to build tao_idl first in a second tree, on linux I set HOST_ROOT as environment variable pointing to the second tree but I don't know if this is fully working yet on Windows, haven't done a cross compilation on Windows for a long time now. Will need someone to try this, but it should be possible but maybe requires some minimal changes


Newsletters: add 253 (2023-05-31)

[ ] Lede, releases/RCs, topic links on Tuesday @harding
[ ] Notable changes section ASAP @harding
[ ] Waiting for confirmation: practical strategies when bidding for blockspace: fee bumping, size efficiency, fee-sensitive coin selection @Xekyo
[ ] Bitcoin SE @bitschmidty

I have a draft for the series, will wait for Gloria to give it a read over and then add it here tomorrow morning.

Great newsletter, team! Thank to @harding @Xekyo @glozow @LarryRuane for your contributions!


Example formatting flash_attention.py with black.

I found that autopep8 is not wrapping lines (which to me feels like the
most basic purpose of an autoformatter) even with -aaa, so I wanted to
try other formatters.  (The autopep8 issue may be a known bug?
https://github.com/hhatto/autopep8/issues/497)
The main concern I heard from other contributors seemed to be that we
don't want to put every function param/arg on its own line, because
Triton functions frequently have many params.  Instead, we want to be
able to group arguments together in a logical way using linebreaks.
I first tried yapf, which can be configured to mush all arguments
together onto one line. Great!  Unfortunately I don't see how to get it
to allow you to configure where the linebreaks go in function arg lists.

If you put a trailing # in any line in the arg list, then it puts
all args on their own line. :(

Worse, it seems to ignore its own yapf: enable/disable comments, so
you can't get it to leave your arg lists how you want.

Because this wasn't working well, I tried Black.  Black does by default
put every argument on its own line, but at least it respects its own
fmt: on/off comments.
Black has the further advantage that there's a reimplementation that
runs extremely fast, namely ruff.

Going to close this since we've agreed on formatting with black at line-length 120.  Will set up proper pre-commits.


Remove broken link

I don't think this link is meant to be broken. We should probably fix it instead of removing it.

Actually, this fix is correct. I was going to do a jasmine guide, but there's not really anything specific for jasmine that needs to be done. It's more the bundlers + environments that are the issue.

Seems like it'd still be useful to have a guide there that says "nothing needs to be done!" so Jasmine users don't think their tool is omitted.

@ljharb fair enough. PRs welcome :)
I think there are a couple of the enzyme-example-* projects that are using jasmine already. we could potentially rename them to include jasmine in the name... although the names of these projects are going to get a bit crazy :)


Add Affable class

I didn't add the various division between Affable and MonadAff as I guess we should come up with laws for them, but I've not figured out what they should be yet as I'm shaky on the monad morphism stuff even.
This is a breaking change so will need a version bump again.

When I see this, I can't help but think of the classic Larry David / Curb Your Enthusiasm line, “I was just trying to be Affable!”

I guess FunctorAff's law would be that it forms a natural transformation of the proper forall f g a. (Functor f, Functor g) => f a -> g a type (we usually ignore the functor constraint).

@jonsterling I don't remember who suggested Affable, I thought it might have been you actually, but it's genius anyway :smile:. Effable likewise if/when we introduce it.

:+1:

Although I am curious why fromAff and not liftAff.
Also, would it be a good idea to imply MonadAff from any Monad which is Affable? This would basically ensure no one can implement MonadAff directly, rather, any Monad which is Affable automatically gets a MonadAff.

I wasn't sure if we wanted to keep the same function to work for both, that's fine by me too. I figured liftAff implies something more lawful than just toAff?
For the latter thing, do you mean including an instance like this?
instance impliedMonadAff :: (Monad m, Affable e m) => MonadAff e m where
  liftAff = fromAff

I'm actually not sure if that works, I can give it a try, but also I thought tit's maybe possible to implement an instance where the Affable for a Monad without making it a monad morphism? If we're just using MonadAff to imply both constraints it seems a bit unnecessary and we could just use both constraints at the definition site instead.

OK, good to ship as is (I still go back and forth on the name, but I'm good with trying this).

I went back to just providing liftAff under Affable and not having a separate function for MonadAff, I think it will be less confusing this way. Added some minimal comments to the meaning of the classes too, but I'm not exactly sure how to state the mmorph laws for MonadAff so just left the specifics unstated.

I realised that a fairly important thing was missing: an instance for Free, which was pretty much the motivating case in the first place. I had to add the dependency for that to make it possible, but I think it's worth it.
I also updated the build to use pulp, added auto-publish to pursuit, fixed the license description in bower.json, added a dependency status badge, and moved the "examples" into the test suite which will ensure they run as part of Travis.

👍

A class for types that can carry an Aff value by some means.

Is the goal here to use MonadAff with Free f when f is Affable but not a Monad?
What are the laws for Affable? If it's that liftAff is a monad morphism, then is something like liftAff _ = throwError "explode" a valid instance, for example? Or is it that liftAff identifies Aff as a a summand of m as a coproduct? In which case the instances for the transformers seem off.

Affable is lawless, it's basically a specialised inject. When it is also MoandAff then it's a monad morphism.

I should think the laws could be something like:
liftF (liftAff (pure a)) = pure a
liftF (liftAff (aff >>= f)) = liftF (liftAff aff) >>= (liftF (f >>> liftAff))

So the laws are relative to Free? That seems a bit specialized to me. Aff doesn't really have anything to do with Free in general.
It might also be interesting to try coming up with a class with the Aff operations, rather than lifting everything at once. Then you could talk about morphisms between Affable things using the type class morphisms approach. I dunno.

So the laws are relative to Free? That seems a bit specialized to me. Aff doesn't really have anything to do with Free in general.

It's true, we could put this into purescript-aff-free or something. The question is, do the above Free-based laws imply the monad transformer laws when m is a monad? That might be an argument for Affable being a superclass of MonadAff (though I need to think about it more).

It might also be interesting to try coming up with a class with the Aff operations, rather than lifting everything at once.

Yeah, I like that approach. Though I wonder what laws one could state with such an approach, without assuming that f is a monad...

It's true, we could put this into purescript-aff-free or something.

Perhaps that would be a good approach. My only concern is that aff is a core part of the "real world PureScript" ecosystem, whether or not it's part of the core/contrib libraries. It's really useful for beginners who want to create their first real project, and it would be a shame to make the API more confusing with something which seems primarily motivated by a need in Halogen-style apps.

Perhaps that would be a good approach.

I'm good with that. @garyb? The main thing it changes is that Affable is not a superclass of MonadAff. However, a MonadAff could imply Affable, and we could go back to the old fromAff name.

That's fine by me. Do we need a separate library, I could just split Affable out within purescript-aff?
I'm not too sure about the free-based laws holding the way we use it either, as we can have nested Frees, the Aff inside a Coproduct, etc.

Do we need a separate library, I could just split Affable out within purescript-aff?

I think that's fine for now (in its own separate module, separate doc, etc.). We can move it to a new library if it seems the approach is working and generally useful (and do the same for Eff).

I'm not too sure about the free-based laws holding the way we use it either, as we can have nested Frees, the Aff inside a Coproduct, etc.

The laws should hold no matter the nesting, so long as they hold individually at each level. Right?


[1.6.10-beta02][Android] Compose Multiplatform isn't working on mobile web

Describe the bug
Compose Multiplatform (up to inclusive 1.6.10-beta02) isn't working on mobile Chrome portrait.
You repro with https://github.com/Ivy-Apps/learn/tree/ef45c76c8d6b3b2e1c205fa112cf3fa8fd8d028d
Test the website live at:
https://ivylearn.app/
More info at this Kotlin "#compose-web" Slack thread:
https://kotlinlang.slack.com/archives/C01F2HV7868/p1714135737642379
Portrait - not working
https://github.com/JetBrains/compose-multiplatform/assets/5564499/70651fc1-870d-4248-9367-1696014dd352
Portrait (Fold4 opened) - working
https://github.com/JetBrains/compose-multiplatform/assets/5564499/7bbb0602-6f53-497a-8b20-e4809318bf8e

Note: It woks well on Desktop Chrome.

Affected platforms

Desktop (Windows, Linux, macOS) - works ✅
iOS - haven't tested
Web (K/Wasm) - Canvas based API - broken ❌
Web (K/JS) - Canvas based API - broken ❌
Web (K/JS) - HTML library - haven't tested

Versions
https://github.com/Ivy-Apps/learn/blob/ef45c76c8d6b3b2e1c205fa112cf3fa8fd8d028d/gradle/libs.versions.toml

Kotlin version*: 1.9.23
Compose Multiplatform version*: 1.6.10-beta02
OS version(s)* (required for Desktop and iOS issues):
OS architecture (x86 or arm64):
Device (model or simulator for iOS issues): Android, Fold4 but can repro on S24 and all Android devices
JDK (for desktop issues):

To Reproduce
Steps and/or the code snippet to reproduce the behavior:

Open https://ivylearn.app/ on a mobile Android device
Try to click a Button - it won't work.
See error

Expected behavior
It renders at the center of the screen and UI interactions work like on desktop.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Also related:
https://github.com/JetBrains/compose-multiplatform/issues/2785

As for other people looking for a workaround until maybe you can try to add
<meta name="viewport" content="width=device-width, initial-scale=1.0">
and maybe adjust the CanvasSize in maybe:
`

`

I can confirm the workaround proposed by @TomislavMladenov worked for me 💯

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Opened .ipynb files don't switch from JSON to Webview after extension install

Testing Codespace Scenario: 1791
Environment data

VS Code version: 1.52.0-insider (Codespace)
Jupyter Extension version (available under the Extensions sidebar): 2020.12.1
Python Extension version (available under the Extensions sidebar): 2020.11.2
OS (Windows | Mac | Linux distro) and version: Linux Codespace
Python and/or Anaconda version: 3.8.6
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: Local

Expected behaviour
Opened .ipynb files automatically switches from JSON view to Notebook after installing the Python and Jupyter extensions (wasn't prompted for a reload).
Actual behaviour

.ipynb file opened.
Prompted to install Python extension (no indication of Jupyter - we should be more clear about that dependency for now).
Finished installing and not prompted for a reloaded - extension commands work.
Opened .ipynb file remains in JSON form.

Steps to reproduce:
[See above and reproduce in Codespace]
Logs

@SiddhanthUnnithan, since you were using vscode-insiders, you should be defaulting to vscode native notebooks when opening any ipynb. You should never see JSON or the old notebook UI. Can you try with the latest insiders?
Also, if we ever break the dependency between Python and Jupyter extension, we'll consider re-messaging then. :)

@SiddhanthUnnithan, since you were using vscode-insiders, you should be defaulting to vscode native notebooks when opening any ipynb. You should never see JSON or the old notebook UI. Can you try with the latest insiders?
Also, if we ever break the dependency between Python and Jupyter extension, we'll consider re-messaging then. :)


How do you open a docx file?

If you pass a docx file into PandocRuby, e.g.:
PandocRuby.convert('./file.docx', :S, from: :docx, to: :html)

It errors with RuntimeError: pandoc: Cannot read archive from stdin

This is a problem in Pandoc itself:
https://github.com/jgm/pandoc/issues/3383
It is fixed in Pandoc 2.0.x.  Just upgrade your Pandoc binary and it'll work.

gem 'pandoc-ruby', '2.0.2'
same error raising RuntimeError: pandoc: Cannot read archive from stdin

@agiratech-reddysai - pandoc-ruby is just a wrapper gem around a system call, i.e. it runs the pandoc(1) binary on your system, so what matters is what version of pandoc is installed.  Try running pandoc --version from the command line, and upgrade pandoc, not pandoc-ruby, if necessary.

I'm running pandoc 2.2.1 and pandoc-ruby 2.0.2 and I'm having trouble getting a docx to convert to html as well (although obviously for a different reason).
The command line works. I'm using example_29.docx from the pandoc demos. Running docker-compose exec web pandoc -f docx -t html tmp/example29.docx yields

Synopsis

pandoc [options] [input-file]…

Description

Pandoc is a Haskell library for converting from one markup format to another, and a command-line tool that uses this library.

...

From the console however:
irb(main):001:0> PandocRuby
=> PandocRuby
irb(main):002:0> PandocRuby.convert("tmp/example29.docx", from: :docx, to: :html)
Traceback (most recent call last):
        1: from (irb):2
RuntimeError (couldn't parse docx file)

Sorry for my absence, and I'm glad you were able to find a workaround. As of the latest version, 2.1.0, docx files can be converted by specifying the file path as an array:
PandocRuby.new(['/path/to/example.docx'], from: 'docx', to: 'html').convert

Please let me know if you run into additional issues related to this!


Parallel Bible :The color tray that displays for highlighting in the first pane is still visible upon selecting another book in the parallel Bible view

Issue description:
The color tray that displayed for highlighting in the single pane , is still visible, upon selecting a new book in the parallel Bible view
Steps:
From the App, select a verse from a Bible passage
Now the color tray displays for the purpose of highlighting.
Select the parallel Bible option, choose another book in the second pane.
Observation : The color tray that displayed for highlighting in the first pane is still visible upon selecting another book in the parallel Bible view
Expected result:  Since the highlight option is not functional in the parallel view, t

he color tray should not be visible in the parallel Bible view

Fixed


Museum page/parser improvements

Uploading a save file now marks artifacts/minerals
Museum parser now includes artifact/mineral donated count
Museum achievements are now correctly toggled based on total values
File upload is now abstracted to a function to be used in sidebar/index page

lgtm


naga internal error: entered unreachable code when attempting to run shader

Bevy version
13.2
The release number or commit hash of the version you're using.
13.2
Relevant system information
Windows 11
AdapterInfo { name: "NVIDIA GeForce RTX 3080 Ti Laptop GPU", vendor: 4318, device: 9248, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "551.23", backend: Vulkan }

What you did
Working on height map renderer... no problem in the bevy examples directory
What went wrong
thread 'Async Compute Task Pool (2)' panicked at .cargo\registry\src\index.crates.io-6f17d22bba15001f\naga-0.19.2\src\back\glsl\mod.rs:1183:44:
internal error: entered unreachable code
Additional information
I put a minimal version with full cargo.toml here:
https://github.com/00alia00/bevy_unreachable

unreachable!() code in naga:
https://github.com/gfx-rs/wgpu/blob/87576b72b37c6b78b41104eb25fc31893af94092/naga/src/back/glsl/mod.rs#L1182-L1183
    /// # Panics
    /// If the global has type sampler
    fn write_global(
        &mut self,
        handle: Handle<crate::GlobalVariable>,
        global: &crate::GlobalVariable,
    ) -> BackendResult {
        [...]
       match global.space {
            [...]
            // Textures and samplers are handled directly in `Writer::write`.
            crate::AddressSpace::Handle => unreachable!(),
        }
    }

the function is marked as panicking if a global variable is a sampler

@mockersf Looks like same problem with this issue, but it is marked as solved


Features Request: Elapsed Time Clock and Scripting

It would be great to have an elapsed time readout on the looping memory tests.
Even better would be a scripting function.  For example, set up an ATK run that tests all found memory for 10 rounds, does a read test on the floppy drive, and checks the RTC time.
Not asking for much.  :-)

Wow this was a long time ago. That would be great.


Whonix Documentation

This ticket is a request for https://docs.featherwallet.org/ to be updated with a section describing how to use Feather Wallet on Whonix.

https://en.wikipedia.org/wiki/Whonix

Specifically, I use Whonix on QubesOS, but I think the documentation should be written to apply on all platforms that Whonix runs-on.

Some references:
https://forums.whonix.org/t/install-feather-by-default/18403/7
https://forums.whonix.org/t/feather-monero-wallet-in-whonix-workstation/12958/4


ViveNavMesh will still try to render a mesh with no material.

ViveNavMesh will still try to draw its mesh even if GroundMaterial is null, which crashes the engine.

This is obviously an oversight, but I believe the engine crash is only present in Unity beta version 5.4b18 and earlier.  I reported the issue to Unity a few days ago (pertaining to the mesh being null, not the material, see 5bd718c2000274cb15dac37abdcda19ca03863eb) and they fixed it in 5.4b19.  I'll add a quick null check to ViveNavMesh for earlier betas of course.

Fixed in version 2.0.0.


s/scan/select in bluetooth article

See https://twitter.com/janoszen/status/828538801358266368

Just created a patch, I hope I didn't miss anything:
google-web-fundamentals-4140.patch.txt
Note that I don't have the build setup, I just modified the markdown file so please test it before you apply. Also, the screenshot could do with a better resolution, that's not included in the patch.

@janoszen Here's https://github.com/google/WebFundamentals/pull/4141 that hopefully addresses your concerns.


Incorrect cursor position on full lines

Windows Terminal version
1.7.11461.0
Windows build number
10.0.22621.0
Other Software
No response
Steps to reproduce
Create a character string which is one character short of the full line width:

Add the final character and note the cursor appears one character left of where it should:

Expected Behavior
Cursor should appear at the end of the line when the line is full.
Actual Behavior
Cursor appears one character before the end of the line. Operationally the cursor functions according to the correct position ("delete" does nothing and "backspace" removes the "L"). This is an off-by-one error on just the display side.

Thanks for reporting this!
You'd be surprised -- this is actually working as intended! Applications are allowed to write text all the way to the edge of the screen without incurring line wrapping. However, the cursor cannot go off the edge of the screen to indicate that the next character will go into outer space.
Different terminal emulators handle this differently:

It looks funny when the default cursor is set to the vertical bar... but the cursor technically occupies a cell, and not a place between cells.
/cc @j4james, as I am probably getting some details wrong 😄

Hi, i wonder if this is the same issue i'm having with vim on windows terminal, where cursor always appears one character to the left from the end on line?

In your case (@pere3), the position of the cursor is controlled by vim. :smile:

Hey DHowett, thanks for taking the time to respond and spread some knowledge 😊:

You'd be surprised -- this is actually working as intended! Applications are allowed to write text all the way to the edge of the screen without incurring line wrapping. However, the cursor cannot go off the edge of the screen to indicate that the next character will go into outer space.
Different terminal emulators handle this differently:
It looks funny when the default cursor is set to the vertical bar... but the cursor technically occupies a cell, and not a place between cells.

Hmm that's fair. I guess I was just used to the behavior of the original console where even the full sized cursor would wrap:

If I remember the console APIs correctly this is a behavior the app can choose to override but idk, to me it makes more sense for the cursor to always display where it is but maybe there is nothing saying that's how it's supposed to be.
There is another inconsistency I've noticed with the way the end of line is handled. If you type to the end of a line like this:

You can press the right arrow and nothing happens, as would be expected given the current positioning logic. If you instead press left the right the cursor moves to the next line anyways:

I'm not sure if this behavior is inherent to the way the line wrapping logic is supposed to work with the current behavior but it certainly feels inconsistent nonetheless.
@DHowett I'll leave it up to you to divine if this second behavior would be categorized as a bug or not. In either scenario, I'd like to make the case that it (feels) more consistent to just wrap the cursor to the next line as the default behavior, if both are valid, but agree that may not fit under the "bug" tag.

You'd be surprised -- this is actually working as intended! Applications are allowed to write text all the way to the edge of the screen without incurring line wrapping. However, the cursor cannot go off the edge of the screen to indicate that the next character will go into outer space.

@DHowett I think there's more to this, though, because it works differently in conhost. I had a brief look at what was going on and it appears that pwsh is using a mix of VT and legacy APIs. When you type a character at the end of the line, it redraws the line in VT mode, leaving the cursor in the last column. But it also then calls SetConsoleCursorPosition to manually reposition the cursor on the next line. That final cursor position doesn't seem to be forwarded over conpty. So I think there is likely a genuine bug here.

Huh! Thanks for looking, James. :smile:

I was looking through other issues and couldn't find an answer to that, so...
If we ever move the rendering of the viewport margins into the renderers, could we perhaps draw the cursor inside the margin (if the margin is >0)? That would be different to other terminals, but would pretty cool.
BTW while writing this I just noticed that our margins aren't quite uniform...

could we perhaps draw the cursor inside the margin (if the margin is >0)?

If we do, it should definitely be an option, preferably off by default, because from a standards point of view that's just wrong. When the terminal is in this state, the cursor position is explicitly defined as the last column. The reported position is going to be the last column. Any movement operation is going to be relative to the last column. If you're rendering the cursor somewhere else, it's going to appear broken. Maybe it's a personal preference, but if I saw a terminal doing this I'd assume it was a bug.


Incorrect Artist added in Metadata Field in Emby

Hi,
I am having some issues with Music Videos and incorrect artist values being populated.. I have my Library settings like this:

For some reason, every music video is populated with the artist SZA. I can not find references to this artist in the corresponding info.json files so I am not sure where this is coming from.  Any help is greatly appreciated.
Also attaching a random info.json file for one of the affected videos.
[(3CxtK7-XtE0)].info.json
And I have the emby log file as well if desired.

Hi, Thanks for your report, can you go to the item and click the edit metadata and post screenshot of the data there?

Sure can, thanks for your hard work!

Thanks, it seems i have to add fallback to artist field incase it's Emby to use the channel name

I think that should work well for most cases.

@cscattaglia917 please download v<IP_ADDRESS> and see if it fixes your problem and report back pls

Looks good and works well for most cases! The cases where it doesn't work are more of an issue with the uploader being named something that doesn't match the artist name, so thank you!

Looks good and works well for most cases! The cases where it doesn't work are more of an issue with the uploader being named something that doesn't match the artist name, so thank you!

You can manually edit the channel name in .info.json file to something suitable, The fallback is as i described if artist property is found it will use that, if not it will fallback to channel property which should always exists.
Sadly, the only other workaround i can think of is you can alter the channel or add artist field into the .info.json file and it should be reflected in your emby/jf.
Happy watching.

Oh interesting, I didn't know that .info.json had an artist property ever(I have not seen one personally.) Good to know! Thank you!

Oh interesting, I didn't know that .info.json had an artist property ever(I have not seen one personally.) Good to know! Thank you!

youtube-dl used to have them and i assume yt-dlp does too along side album and track properties. Not sure on what logic they add the fields though.


Ingest UI stuck in Loading state when trying to Edit a Project from the Project Information page in Safari

Describe the bug

When I try to Edit a Project from the Project Information page in Safari, the UI gets stuck in the Loading state.

To Reproduce
Steps to reproduce the behaviour:

Go to 'All Projects'
Select one project and Click on 'View Project'
In the Project Information tab, scroll down to 'Edit'
Click 'Edit'

Expected behaviour

The page loads in Edit mode and you can start editing the Project Information.

Screenshots / Logs

Environment

[ ] prod

Browser

[ ] Safari

In prod now!