Add vim help file

created vim help file for #83 . I hope everything is correct.
If I should add more things to the help file please tell me.

vimhelplint reports some issues:
% VIMHELPLINT_VIM="nvim --headless" vimhelplint doc/deoplete-jedi.txt
doc/deoplete-jedi.txt:3:1:Warning:1:The width of a line should be no longer than 78.
doc/deoplete-jedi.txt:10:1:Warning:1:The width of a line should be no longer than 78.
doc/deoplete-jedi.txt:22:13:Error:2:A tag "deoplete-jedi" is duplicate with another in this file.
doc/deoplete-jedi.txt:41:1:Warning:1:The width of a line should be no longer than 78.
doc/deoplete-jedi.txt:56:1:Warning:1:The width of a line should be no longer than 78.
doc/deoplete-jedi.txt:65:41:Error:2:A tag "deoplete-jedi" is duplicate with another in this file.
doc/deoplete-jedi.txt:92:1:Warning:1:The width of a line should be no longer than 78.
doc/deoplete-jedi.txt:103:45:Error:4:A link "nvim-python-quickstart" does not have any corresponding tag.

vimhelplint is from https://github.com/neomake/neomake/blob/master/contrib/vimhelplint.
With Neomake you can run :Neomake vimhelplint on the file (after make build/vimhelplint in Neomake's plugin dir).

I removed the error message but the warnings about the long lines are wrong.
The longest line in the file is 77 but vimhelplint still shows the warnings.

I do not get your last comment.
Are you saying that vimhelplint installed/used through Neomake's contrib script would get line lengths wrong?

You might have been fooled by Vim's conceal feature to make *foo* into foo in help files (and therefore getting two columns less visually).

@blueyed Sorry for the late reply.
BTW, user is deleted account. but I think this pull request is very great work. So I want to merge, and fix your suggested point after the merge.
What do you think?

@zchee
Yes, go ahead - but why not fix them by amending the commit right away then?

@blueyed Yeah, good idea.
But sorry... I don't have knowledge of vim help yet...😱
What meaning that warning result? https://github.com/zchee/deoplete-jedi/pull/119#issuecomment-297542725

@blueyed Ah, sorry. ghost said

I removed the error message but the warnings about the long lines are wrong.

So, now you suggested point is only of this?

You might have been fooled by Vim's conceal feature to make foo into foo in help files (and therefore getting two columns less visually).

Remaining warnings are only about length:
doc/deoplete-jedi.txt:3:1:Warning:1:The width of a line should be no longer than 78.
doc/deoplete-jedi.txt:41:1:Warning:1:The width of a line should be no longer than 78.
doc/deoplete-jedi.txt:56:1:Warning:1:The width of a line should be no longer than 78.
doc/deoplete-jedi.txt:92:1:Warning:1:The width of a line should be no longer than 78.

Make sure to set conceallevel=0 when viewing those lines.
I would also use spaces instead of tabs throughout the file.

@blueyed

Remaining warnings are only about length:
Make sure to set conceallevel=0 when viewing those lines.

I see, Thanks. So, I should fix only of column length to less than 78, right?

I would also use spaces instead of tabs throughout the file.

got it.
BTW, Do we need magic comment such as these?
https://github.com/neomake/neomake/blob/43e6a4577aaa6e2fec0edc5ddf02180f9d574656/doc/neomake.txt#L697

Not sure about the modeline ("magic line") - let's keep it.

Why it is suspended?


Added check to only process ARP packets from the same network

We should not update our ARP table based on ARP packets coming from the network other than IoT-Inspector's network.

Thank you for catching this bug @viz-prakash !


[4.0.0] Carthage installation fails with Xcode 13.3

Environment details
Google-Maps-Utils 4.0.0
Xcode 13.3
Carthage 0.38.0
We don't want to use Google Maps Utils 4.0.0 since it contain a reference to the beta version of Google Maps. Maybe you could release a version that references the release version of 6.0.1.
Steps to reproduce
Create the following Cartfile in an empty folder:
github "googlemaps/google-maps-ios-utils" == 4.0.0

and run:
carthage bootstrap --use-ssh --platform iOS --cache-builds --use-xcframeworks --no-use-binaries

the output will be:
*** No Cartfile.resolved found, updating dependencies
*** Fetching google-maps-ios-utils
*** Fetching ocmock
*** Downloading binary-only framework GoogleMaps at "https://dl.google.com/geosdk/GoogleMaps.json"
*** Checking out ocmock at "v3.9.1"
*** Checking out google-maps-ios-utils at "v4.0.0"
*** No cache found for GoogleMaps, building with all downstream dependencies
*** No cache found for ocmock, building with all downstream dependencies
*** Downloading binary-only framework GoogleMaps at "https://dl.google.com/geosdk/GoogleMaps.json"
*** xcodebuild output can be found in /var/folders/s8/6bfvlm916_94n26jl90s1tmw0000gn/T/carthage-xcodebuild.86fzjI.log
*** Downloading GoogleMaps binary at "6.1.1"
*** Building scheme "OCMock iOS" in OCMock.xcodeproj
*** Building scheme "GoogleMapsUtils" in GoogleMapsUtils.xcodeproj
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /private/var/folders/s8/6bfvlm916_94n26jl90s1tmw0000gn/T/tmp.WxelOGYn/Carthage/Checkouts/google-maps-ios-utils/GoogleMapsUtils.xcodeproj -scheme GoogleMapsUtils -configuration Release -derivedDataPath ~/Library/Caches/org.carthage.CarthageKit/DerivedData/13.3_13E113/google-maps-ios-utils/v4.0.0 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive VALIDATE_WORKSPACE=NO -archivePath /var/folders/s8/6bfvlm916_94n26jl90s1tmw0000gn/T/google-maps-ios-utils SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO FRAMEWORK_SEARCH_PATHS=$(inherited)\ /var/folders/s8/6bfvlm916_94n26jl90s1tmw0000gn/T/carthage-xcframework-Ok4c (launched in /var/folders/s8/6bfvlm916_94n26jl90s1tmw0000gn/T/tmp.WxelOGYn/Carthage/Checkouts/google-maps-ios-utils)

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/s8/6bfvlm916_94n26jl90s1tmw0000gn/T/carthage-xcodebuild.86fzjI.log

@stherold Please take a moment to fill out this short survey. Thank you!
This is an automated message, feel free to ignore.

@stherold Thank you for opening this issue. 🙏
Please check out these other resources that might be applicable:

Support Console - If you have a support contract.
Discord - chat with other developers
StackOverflow - use the google-maps tag
Google Maps Platform issue trackers

This is an automated message, feel free to ignore.

I'm assuming you are on an M1 machine? Version 4.0.0 of the utility library depends on Maps SDK version 5.1.0 (see https://github.com/googlemaps/google-maps-ios-utils/compare/v3.10.3...v4.0.0) which does not have the binaries for arm64-sim support. I recommend using 4.1.0 which depends on on 6.0.1-beta which has arm64-sim support if you are on an M1 machine.

We don't want to use Google Maps Utils 4.0.0 since it contains beta references of Google Maps. When is the time come that this is not marked as beta or asking differently is it sdafe to use the version 6.0.1-beta of Google Maps and is it only beta because of the xcframeworks?

Yes, it is marked as beta because it is an xcframework and will be considered stable once xcframeworks are distributed across all the supported package managers (CocoaPods and Carthage).

Gotcha. Let's keep it open for a bit in case anyone else runs into this. I was not able to repro this but I'm on Xcode 13.2.1

For us it runs again, we now use version 4.1.0


Disable update check in dev

https://github.com/ipfs-shipyard/ipfs-desktop/pull/1414/files#diff-a35e38cd4254c7195bafd538c087d2e5L73  was removed in #1414, and now every time we run npm start during development it pings the update server(?) on each run:
$ DEBUG='desktop' npm start                                                                                ... feat/ipfsd-ctl-update

><EMAIL_ADDRESS>start /home/lidel/project/ipfs-desktop
> cross-env NODE_ENV=development electron src/index.js

2020-04-18T14:12:11.054Z info: [meta] logs can be found on /home/lidel/.config/Electron
Checking for update
Generated new staging user ID: bde5278b-16e6-55f6-8b5d-777509b33c87
Update for version 8.2.3 is not available (latest version: 0.10.4, downgrade is disallowed).
2020-04-18T14:12:14.118Z info: [updater] update not available

cc @hacdias – thoughts?

Ah. I (enabled) it on dev so I could test the different dialogs. I can disable it again, of course.


Application Insights automatically injecting Javascript into

See also post on Stackoverflow - not by me - the only answer did not work for me.
https://stackoverflow.com/questions/47681778/controlling-application-insights-javascript-injection
Repro Steps

In program.cs, add .UseApplicationInsights("YOUR KEY HERE")

Actual Behavior
Observe the following fragment is now automatically output in your  section, before the closing
<script type="text/javascript">
        var appInsights=window.appInsights||function(config){
            function i(config){t[config]=function(){var i=arguments;t.queue.push(function(){t[config].apply(t,i)})}}var t={config:config},u=document,e=window,o="script",s="AuthenticatedUserContext",h="start",c="stop",l="Track",a=l+"Event",v=l+"Page",y=u.createElement(o),r,f;y.src=config.url||"https://az416426.vo.msecnd.net/scripts/a/ai.0.js";u.getElementsByTagName(o)[0].parentNode.appendChild(y);try{t.cookie=u.cookie}catch(p){}for(t.queue=[],t.version="1.0",r=["Event","Exception","Metric","PageView","Trace","Dependency"];r.length;)i("track"+r.pop());return i("set"+s),i("clear"+s),i(h+a),i(c+a),i(h+v),i(c+v),i("flush"),config.disableExceptionTracking||(r="onerror",i("_"+r),f=e[r],e[r]=function(config,i,u,e,o){var s=f&&f(config,i,u,e,o);return s!==!0&&t["_"+r](config,i,u,e,o),s}),t
        }({
            instrumentationKey: 'YOUR GUID'
        });

        window.appInsights=appInsights;
        appInsights.trackPageView();

    </script>

In addition to this, my ASPNETCORE_ENVIRONMENT variable is set to Development, which I would have thought would stop all AI telemetry.
Expected Behavior
Per documentation, I should be able to control injection of the JavaScript snippet with
@using Microsoft.ApplicationInsights.AspNetCore
@inject JavaScriptSnippet snippet
....
 @Html.Raw(snippet.FullScript)
</head>

Version Info
SDK Version : Reproducible with metapackage and also after adding Microsoft.ApplicationInsights.AspNetCore 2.2.1
.NET Version : NET Core 2.0.5 (using Metapackage Microsoft.AspNetCore.All)
Hosting Info (IIS/Azure WebApps/ etc) : Visual Studio / Kestrel

Obviously I'm not the only one having some struggle with this.
It seems there are two options to stop AI telemetry as you can see here:

by setting environment variable ASPNETCORE_preventHostingStartup to true
by altering TelemetryConfiguration within the Configure method of Startup class

Both have there own drawbacks as you can read in the link above. There you will also find some information that AI is tightly coupled with VS. So from my understanding VS itself places the javascript snippet by its own as soon as you add the AI InstrumentationKey to your appsettings.json.
A third options seems to be in the latest preview of VS (15.6) where you can disable AI locally within the tools option.
Nevertheless I think the documentation is pretty misleading. I would almost say it's complete useless....

@knightmeister ApplicationInsights does not inject Javascript snippet itself. Its injected by  Visual Studio if you launch the app from within Visual Studio. You can always control JavaScript snippet injection yourself.

@knightmeister

In addition to this, my ASPNETCORE_ENVIRONMENT variable is set to Development, which I would have thought would stop all AI telemetry.

@bjr001 As mentioned in the linked issue, VS is tightly integrated with application insights experience - based on user feedback, however VS is providing new feature to disable application insights locally.
Can you point me to the documentation which is misleading. I am more than happy to correct the documentation.
The following 2 are the documentation I am aware of. Please let me know if you find misleading information here.
https://github.com/Microsoft/ApplicationInsights-aspnetcore/wiki/Getting-Started-for-a-ASP.NET-CORE-2.0-WebApp
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-asp-net-core

@cijothomas asp.net core SDK injects JavaScript snippet. See the use of https://github.com/Microsoft/ApplicationInsights-aspnetcore/blob/12cb0cd96c83115eeb16d7b2711c5ddb73c9e69c/src/Microsoft.ApplicationInsights.AspNetCore/ApplicationInsightsJavaScript.cs#L12 in the code

@SergeyKanzhelev I meant SDK does not do this part by itself:
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-asp-net-core#page-view-load-time
user has to manually modify the cshtml to get the snippet (which is made available by sdk). but if you launch app from VS, then the snippet is inserted automaticaly.

Note that if the app is deployed to Azure Web App, and then AI is enabled from WebApp - in this scenario also entire AI (including javascript) is 'lightup' automatically. (this is only if AI extension is installed in WebApp)

@cijothomas I followed the github guide (https://docs.microsoft.com/en-us/azure/application-insights/app-insights-asp-net-core#page-view-load-time), without adding the javascript snippet, and when my app is on azure the AI javascript snippet is still being injected. Do you have any advice on how to disable it? I did not enable AI from the web app in azure.

@cjnaude Can you list the exact steps you followed?
Do you see javascript snippet when you run locally (outside of visual studio) ? Or do you see it only when running on Azure Web Apps?

@cijothomas 1. Created the Application Insights resource on Azure
2. Already had the package included through
3. Added the instrumentation key to appsettings.json
4. Added UseApplicationInsights to the WebHostBuilder instance
5. Deployed to Azure
The javascript does not appear when I run locally (through VS Code) and it has not been added to the published view, so its definitely being injected by Azure.
I've tried adding APPINSIGHTS_JAVASCRIPT_ENABLED = false to the web app, but that made no difference.

@cijothomas:

entire AI (including javascript) is 'lightup' automatically. (this is only if AI extension is installed in WebApp)

As far as I saw AI is indirectly referenced when using Microsoft.AspNetCore.All, no?
An working way to disable the AI JavaScript from being injected when deploying to Azure was setting 'Prevent Hosting Startup' to true, like:
WebHost.CreateDefaultBuilder(args)
    .UseSetting(WebHostDefaults.PreventHostingStartupKey, "true")

@p- That did the trick, thanks!

Ok so I'm a bit confused here.  Is there a way to have your cake and eat it too?

I like that it gets auto injected.
I hate that I can't control what order it gets injected in so I can add configuration after init.

How can I simply tell Visual Studio not to add this when I launch it?

This env variable, ASPNETCORE_PREVENTHOSTINGSTARTUP=true, will prevent VS auto 'onboarding' application insights when running from VS.

@cijothomas what other consequences arise by doing that?

I'd like to chime in and say this really needs to be fixed. I just lost a morning to it and I'm not very happy about it. Magically injecting a script tag into an application but only in certain weird circumstances and then having the only way to turn it off be through a weird, seemingly unrelated configuration value? Not great.

@philwade Can you describe exactly whats the issue you are facing? Did you publish asp.net app to Azure Web App and see tht js snippet is injected automatically?  That is not the expected behavior. jssnippet or sdk is injected in App Service only if you enable application insights in webapp explicitly - nothing is turned on by default. If you experienced otherwise, I can investigate.

@cijothomas I have an azure app service with insights turned on, so it sounds like I'm seeing the expected behavior. However, I don't like the magic injection of the script tag. If you're going to do something automatically for people, you should make it very clear in the documentation and make it super obvious how to turn it off. As it is, this bug report is the only place I could find any information about this behavior and the only place that I could find that told me how to disable it. Additionally, WebHostDefaults.PreventHostingStartupKey is seemingly unrelated to what it's actually doing and I'm afraid that setting it to true will cause additional side effects that won't rear up until later on in the application's life. This whole feature needs a rework.

@philwade The documentation was already updated to describe this behavior. If you don't want injection of scripts - you can turn off application insights in app service, and onboard via nuget in build time.
https://docs.microsoft.com/en-us/azure/azure-monitor/app/azure-web-apps
WebHostDefaults.PreventHostingStartupKey - this is unrelated to azure web apps scenario. its for visual studio.

@cijothomas I do not see where in that page of documentation it says anywhere "we will inject a script tag into the head of your documents". On the contrary, it links to this page: https://docs.microsoft.com/en-us/azure/azure-monitor/app/javascript which instructs you to manually insert the same javascript into your application. If you followed the directions on the initial page then tried to add the javascript, you would end up with two instantiations of app insights and questions about where the script tag was coming from, like I did.

I was referring to the above section:
I agree that js injection should back off, if snippet is already detected. This is a bug. (for server side telemetry, extension detects the existing presence of application insights, and backs-off. similar should be done for js snippet as well. I will open an issue tracking it.)

btw - if you find issues in docs, pleae feel free to open issue about the docs. there is a active team looking at those issues and addressing them.

CLosing this as new docs cover how to turn on and off js snippet injection.


current_best now reports weighted standard deviation

The average test score reported from osprey is weighted by the number of samples used for testing. This PR now has the current_best command reporting a weighted standard deviation instead of an unweighted one.

lgtm


Profile search keeps searching for first search term entered, even after deleting it and entering new search term

Checklist

[X] I am able to reproduce the bug with the latest version.
[X] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
[X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
[X] This issue contains only one bug, that only occurs in Squawker

Affected version
v3.8.0+300015543
Steps to reproduce the bug

Tap the magnifier icon to go to search
Enter "her", wait for results to show up
Delete "her" from the search field, type "elon" (or any other search term really). Wait for results to show up.

Expected behavior
Search results related to the term "elon" (or other alternative search term) should be displayed.
Actual behavior
Search results appear to be identical to when searching for "her". Nothing related to the term "elon" can be found even when scrolling far down.
Screenshots/Screen recordings

Logs
No response
Affected Android/Custom ROM version
Android 13
Affected device model
Sony Xperia 10 III
Additional information
No response

Thank you for the information on this issue, I'll look into it.
For now to make it work, instead of deleting the search text by hitting backspaces, simply tap on the X icon (at the end of the search bar). This erases all the text in the search bar.
Then any new search will work.

Version v3.8.1 should fix it.


Instructions for "Getting devicekey manually" doesn't apply for Sonoff Micro

The instructions for Getting devicekey manually doesn't work for the Sonoff Micro Smart USB Adapter.
If you put the device in pairing mode, connect to the WiFi SSID and browse to http://<device IP>/device it will return a long JSON string as below, not the expected devicekey. note: the SSID and pairing mode IP on this device also differs from the documentation. http://<IP_ADDRESS>/device results in timeout
{"data":"D+JsM5lCJRA7ntdGjue74kqRt0e+YdmJynJI9hfmEYSARk/y7h6j3Xpewsqzyzd/3BjRXOyU23Ou6K1zmUKFBAk2WrWTDasdfMvdb/WXbZas9Cq6eGXykhH5ixsmEolyv2uihV5oAHMetQy7hu5n6Q9ewT7XGjkCKqqu2phtyoj/Yxpew"}
Sonoff's developer site doesn't mention this device at all, so I'm not sure if there's another URL which provides the devicekey. http://<device ip> returns nothing.
The only way to get the devicekey for local use was to create a eWeLink account, add the device in the app, and load a cloud config in this component which writes the key to .sonoff.json, but at that point there's no need for the key in yaml.
I'll be glad to submit a PR on README.md to update the documentation if this is confirmed by anyone else.
This was tested on:

Sonoff Micro firmware 3.7.1
Home Assistant 2021.11.5
SonoffLAN v2.4.6 - 2021-05-14

Getting local keys makes no sense. Integration can load all useful data automatically.

@AlexxIT Hi, I had the same problem with kylehase. After many trials while searching on the web I came across this issue. Info in the readme would have been quite useful. May I ask why did you remove that part from readme?
As a reply to your comment above: I didnt want to install and register to another automation app. It was nice to see alternative setup process.

This information is not needed for my users. I make solutions for people who like plug and play :)


First pass at adding encrypted streams.  This uses openssl as

installed on FreeBSD, this may need to change.  (The path, I mean.)
It also currently hardcodes the encryption scheme, which should also
change.

I fixed the two things above in my branch (the HOST one was supposed to be removed, it doesn't work with boto2).

Is there any progress on this? This tool seems awesome, but lack of encryption is a dealbreaker at the moment.


Add Events For particular day

Your are doing a great job thank you for your valuable complement ,I need to know that Is there any provision to add events for dates like the image above
Thanks,
Rix

I do not have plans as we mostly use the calendar component as a date selector. However, if you want to build the feature and submit a PR, I'll be happy to look at it.


fix: typo

Hi, @up2dul thank you for your effort, but the issue has been resolved by @haikelz. #28


Loudness range quartiles

Hi,
Is it possible to get not only the LRA, but also the actual high and lows? (I see they are computed in ebur128_loudness_range_multiple(), but then immediately subtracted.) I assume calling ebur128_loudness_global() and adding/subtracting half of the LRA won't give the correct range?
The reason I'm asking is that I'd like to visualize the range, similar to what ebumeter does (middle row of http://kokkinizita.linuxaudio.org/linuxaudio/ebumeter-doc/ebumeter.png), and I can't find a way to extract this information currently.
Thanks!

It should not be too hard to add a new API for this use case. How does the LRA visualization of ebumeter work exactly? Is it controlled with the Start/Stop/Reset buttons?

FWIW, I solved my problem just by embedding ebumeter. It is >10x as fast for my use case anyway. Closing this as I don't need it anymore.


Get nan loss during training

❓ Questions and Help
I am training a model modified from  maskrcnn-benchmark. When the model is trained using single GPU , the loss is correctly, but when trained using 4 gpus the model is quite easy get nan. How to solve this problem?

try lowering the learning rate

just lower your learning rate or augment your training set

or to adjust your batch size and make it larger

I met the same problem. Trained with 4 GPU, the loss is nan from the first few iterations.

This problem is solved by set the parameter WARMUP_ITERS to 1000.


fix returning from rmw_wait while any samples have not been taken yet

The patch currently only fixes the subscriptions. The same fix is needed for services as well.
This makes the new tests from ros2/system_tests#20 pass: http://ci.ros2.org/job/ros2_batch_ci_linux/106/

+1


BSOD after sysmon installed

BSOD upcoming just after sysmon installed. Sysmon drive name is "psav3cld.sys"
I can provide the full memory dump if you need it ?
SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD (d4)
A driver unloaded without cancelling lookaside lists, DPCs, worker threads, etc.
The broken driver's name is displayed on the screen and saved in
KiBugCheckDriver.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
An attempt was made to access the driver at raised IRQL after it unloaded.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8075e1abae0, memory referenced
Arg2:<PHONE_NUMBER>000002, IRQL
Arg3:<PHONE_NUMBER>000000, value 0 = read operation, 1 = write operation
Arg4: fffff8074eb48200, address which referenced memory
Debugging Details:
DUMP_CLASS: 1
DUMP_QUALIFIER: 402
BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434
SYSTEM_MANUFACTURER:  HP
SYSTEM_PRODUCT_NAME:  HP Pro x2 612 G2
SYSTEM_SKU:  X4C20AV
BIOS_VENDOR:  HP
BIOS_VERSION:  P86 Ver. 01.16
BIOS_DATE:  03/29/2018
BASEBOARD_MANUFACTURER:  HP
BASEBOARD_PRODUCT:  828B
BASEBOARD_VERSION:  KBC Version 48.61
DUMP_TYPE:  0
BUGCHECK_P1: fffff8075e1abae0
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff8074eb48200
FAULTING_IP:
psav3cld.sys+1bae0
fffff807`5e1abae0 ??              ???

Could you contact me offline at<EMAIL_ADDRESS>and I will provide you with a location to upload the dump file.
Thanks for reporting this and for offering to assist in tracking down the cause
MarkC (MSFT)

Hello MarkC,
thank you for your answer.
In the sysmon command line options, you're able to specify a driver name, that's what we do: sysmon -accepteula -d psav3cld -i config.xml.
I'm contacting you offline.
Best regards

Hello MarkC,
As I said on GitHub, we had specify a driver name in the sysmon install
command line:
sysmon -accepteula -d psav3cld -i config.xml
That's why you will see psav3cld.sys in the dump file as the sysmon driver.
I can eventually share dump on my web server if you want to, or I can
upload wherever you want.
Many Thanks
Best regards,
Yoann W.
Le jeu. 11 juil. 2019 à 17:28, analyze-v<EMAIL_ADDRESS>a
écrit :

Hmm the sysmon driver is called sysmondrv.sys so it's not directly
referenced but that doesn't mean it's innocent and it seems a coincidence
that this occurred during the uninstall.
Could you contact me offline at<EMAIL_ADDRESS>and I will provide
you with a location to upload the dump file.
Thanks for reporting this and for offering to assist in tracking down the
cause
MarkC (MSFT)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/sysinternals/issues/223?email_source=notifications&email_token=ADROHS2VXCTMZOAEXAPTNHDP65GTBA5CNFSM4H6JRUF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZXCIAI#issuecomment-510534657,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADROHS32DPYYS7TT5R3RKLDP65GTBANCNFSM4H6JRUFQ
.

For anybody else who sees this, it was a known issue in Sysmon 9 that has been resolved in Sysmon 10 and later.
MarkC (MSFT)


Update mission statement to be inclusive

Updated the mission statement from "...standardizing feature flagging for developers" to "...standardizing feature flagging for everyone". Everyone is more inclusive but more vague. However, I believe that standardizing various aspects of feature flagging will benefit more than just developers. For example, a DevOps engineer could build tooling around the OpenFeature standard to automate feature testing in their pipeline.

Approved, but I think we also need to think about what it means to improve feature flags for product folks. They are now in scope. :)


feat: Use sellerName instead sellerId

I need the sellerName to set up the jsonLD correctly, but Offer.seller returns the sellerId instead of the sellerName
I don't know if replacing sellerId with sellerName is the best way, but I haven't found another way that follows schema.org

This week I am going deep thinking if we should add "no schema.org props". It's not about your PR, but the decision will impact here.


Build and install "gflags_catkin" error

when i bulid and install "gflags_catkin", I get the following error:
==> ninja -j1 -l1 in '/home/robot/catkin_ws/build_isolated/gflags_catkin'
ninja: error: '/home/robot/catkin_ws/devel_isolated/gflags_catkin/lib/libgflags.so', needed by '/home/robot/catkin_ws/devel_isolated/gflags_catkin/lib/libgflags_catkin.so', missing and no known rule to make it
<== Failed to process package 'gflags_catkin':
Command '['/home/robot/catkin_ws/install_isolated/env.sh', 'ninja', '-j1', '-l1']' returned non-zero exit status 1
Reproduce this error by running:
==> cd /home/robot/catkin_ws/build_isolated/gflags_catkin && /home/robot/catkin_ws/install_isolated/env.sh ninja -j1 -l1
Command failed, exiting.

Same error here.

Works fine without the --use-ninja flag, though.

There are unused repos in the rosinstall file that do not build with Ninja. This is addressed by #42. You'll have to remove those repos manually or start a new workspace from scratch.

Fixed by #42.


Getting typescript error upon installation

><EMAIL_ADDRESS>tsc /Users/tgautier/src/angular2-json-schema-form
> tsc

../../node_modules/@types/protractor/index.d.ts(11,34): error TS2304: Cannot find name 'webdriver'.
../../node_modules/@types/protractor/index.d.ts(12,27): error TS2304: Cannot find name 'webdriver'.
../../node_modules/@types/protractor/index.d.ts(13,32): error TS2304: Cannot find name 'webdriver'.
../../node_modules/@types/protractor/index.d.ts(14,27): error TS2304: Cannot find name 'webdriver'.
...

Darwin Kernel Version 16.3.0, node version 7.4.0, npm version 4.0.5

Hmmm. I don't think this is a problem with Angular2 JSON Schema Form. I just ran the example playground on an identical configuration (same Darwin, node, and npm versions), and it worked fine. This library doesn't use Protractor or Selenium WebDriver, so I don't see any way Angular2 JSON Schema Form itself could cause those errors.
Based on the error messages, it looks like its a problem with the TypeScript definition files for Selenium WebDriver. The first thing I would check is to make sure you're using the latest versions of Selenium and Protractor, and the latest @types type definitions for them.
My best guess is that Angular2 JSON Schema Form is calling the TypeScript compiler (TSC), and the compiler can't find the type definitions it needs, so it throws those errors. To fix it, I suspect you just need to make sure you have the correct TypeScript definitions for the versions of Selenium and Protractor you're using. I don't have much experience with Selenium or Protractor though, so if it's more complicated than that, you should Google Angular2 Selenium Protractor TypeScript configuration (or some variation) for more information.
If you determine that the problem really was caused by Angular2 JSON Schema Form, post again with instructions about how to recreate the problem, and I'll re-open this issue and look into into it more.
Thanks!
-David


MINIFI-224 - fixes for locating ZLIB on Ubuntu 16.10 devices

reviewing

Hey @jdye64,
I was unable to recreate this using the Ubuntu 16.10 Docker image before patch.  Could you specify some additional information concerning the environment that triggered it?  Additionally,  it looks like there was a build issue https://s3.amazonaws.com/archive.travis-ci.org/jobs/205337185/log.txt in Travis.

@apiri The environment where I was experiencing these issues was a niche environment really outside of the normal setup. Also I have found a better way to handle this situation in that specific environment. I'm going to close this PR as I do not think it is needed any longer.

Okay, going to also close the associated JIRA.


Adding custom libraries

This might be the noobest question in git issues history, but I cant for the life of me figure out how to add libraries apart from the default.
For example, before using lua-dev I had something like this in "regular" sumneko, and it worked correctly.
settings = {
                Lua = {
                    runtime = {version = "LuaJIT", path = vim.split(package.path, ";")},
                    diagnostics = {globals = {"vim", "pd"}},
                    workspace = {
                        library = {
                            [vim.fn.expand("$VIMRUNTIME/lua")] = true,
                            [vim.fn.expand("$VIMRUNTIME/lua/vim/lsp")] = true,
                            ["/usr/lib/pd/extra/pdlua"] = true,
                            ["/some/other/libraries"] = true,
                        }
                    }
                }
            }

I have tried adding the same in libraries = {}  section like this
 local luadev =
         require("lua-dev").setup(
         {
             libraries = {
                 ["/usr/lib/pd/extra/pdlua"] = true,
             },
             lspconfig = {
                 on_attach = custom_attach,

and I have also tried in the same's lspconfig like this
settings = {
                  Lua = {
                         runtime = {version = "LuaJIT", path = vim.split(package.path, ";")},
                         diagnostics = {globals = {"vim", "pd"}},
                         workspace = {
                             library = {
                                 ["/usr/lib/pd/extra/pdlua"] = true
                             }
                         }
                     }
                 }

But with either setup, the libraries wont get picked up. I dont get any lsp features like hover, autocompletion, nothing at all.

Can you please help?

@folke
I just tried your gist article which preceded this plugin. Putting the desired paths in that setup's add("/usr/lib/pd/extra/pdlua")
works perfectly
Is there anything that I am doing syntactically wrong in what in my previous post

Update to the latest version and do something like:
local lspconfig = require('lspconfig')

local luadev = require("lua-dev").setup({
  -- add any options here, or leave empty to use the default settings
  -- lspconfig = {
  --   cmd = {"lua-language-server"}
  -- },
})

table.insert(luadev.settings.Lua.workspace.library, "/usr/lib/pd/extra/pdlua")

lspconfig.sumneko_lua.setup(luadev)

Thanks for your response and the qucik change! appreciate it
I get the following error
E5100: Cannot convert given lua table: table should either have a sequence of positive integer keys or contain only string keys
Error executing vim.schedule lua callback: /usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:399: error converting argument 1

Sorry, should be:
luadev.settings.Lua.workspace.library["/usr/lib/pd/extra/pdlua"] = true

Either way, please just check the docs for lua-language server. You can change whatever you want on the condig returned by lua-dev.

Thanks. That works.

Either way, please just check the docs for lua-language server. You can change whatever you want on the condig returned by lua-dev.

Only recently setting up sumneko. Still learning. Thank you for your help and patience.

Is there a way to do this with the current state of Neodev? It would be great if there was an option in the setup function to add more library folders to include when setting up the library. Not sure if there is a way to do it with the override function. I can see that I can modify the setup options there like enable/disable the library or plugins, but is there a way to add a specific folder to the workspace library list?

You should just add any custom libraries to the settings for lspconfig. No need to change anything in Neodev for that

Thanks for the quick reply, I am doing that currently but I am wondering if neodev provides an easy way to only add the library when neodev is active. Since it's a folder in my Neovim runtime path but it's not getting access to variables defined in my ~/.config/nvim folder

I'm not sure if Neodev should be giving access to these things automatically when it sets up the lbrary runtime path. I can see the folder in my runtime path and Neodev is correctly enabling the runtime so I can get auto complete for vim types as well as plugins, but it's not properly adding the other folders in the runtime path as part of the library. So I can't get auto complete for the other variables that I have defined in other runtime path folders. So in this case I want it to automatically add runtime path folders to the workspace library and only when neodev has detected that it should be enabled. So  adding it to my global lspconfig settings for sumneko_lua isn't really an appropriate place since it's only related to my neovim configuration files/folders
Sorry I'm continuing this on this issue, I just didn't want to open a new issue if it was related to this one and decrease clutter on the repo. It seems like if it's not supposed to be automatically detected, I would want to be able to add it to the override function to include my config folder and other runtime path folders.

I have ~/.config/separate_folder in my RTP and investigating the workspace settings that are set with vim.lsp.get_active_client() I see that it's correctly adding the neodev stable types, my user/share/nvim/runtime/lua and ~/.config/separate_folder/lua but it's not adding ~/.config/nvim/lua which is still in my RTP and should be getting checked
workspace = {
  checkThirdParty = false,
  ignoreDir = { "types/nightly", "lua" },
  library = { "/home/micah/.local/share/nvim/lazy/neodev.nvim/types/stable", "/usr/share/nvim/runtime/lua", "/home/micah
/.config/separate_folder/lua" }
}

The config folder is never added to the workspace outside of the config folder, since in most cases (like when developing a plugin) that's not wanted.
If you still need that for a certain folder, then just add it only for that project.
You could use a luarc.json file in that folder, to add in your config as a workspace folder.


Associate WAF variable

Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

No 🛑: please wait to file a request until the functionality is avaialble in the AWS provider
Yes ✅: please list the AWS provider version which introduced this functionality

Is your request related to a problem? Please describe.
I am working on updating to use a WAF on an existing LB. However, if the WAF is not already created I get the invalid count error.
846:   count        = var.web_acl_arn != null ? 1 : 0

The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many instances will be created. To work
around this, use the -target argument to first apply only the resources that the count depends on.

Describe the solution you'd like.
I would like to see if it would be within standards for this project to switch to an "associate_waf" variable similar to the "create_*" variables in this and other aws modules. The reason for this is so that count is no longer dependent on a value and therefore not cause multiple plan and applies.
Describe alternatives you've considered.
I have not been able to think of anything beyond not using the module which I would like to avoid.

Hi,
Run exactly in the same issue.
Here is a valid use case that cause trouble:
terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">=5"
    }
  }
}

variable "my_condition" {
  type = bool
}

locals {
  my_condition = var.my_condition
}

resource "aws_wafv2_web_acl" "this" {
  for_each = local.my_condition == true ? { 0 = 0 } : {}

  name        = "test"
  description = "test"
  scope       = "REGIONAL"

  default_action {
    block {}
  }

  visibility_config {
    cloudwatch_metrics_enabled = false
    metric_name                = "not-used-but-required-by-tf"
    sampled_requests_enabled   = false
  }
}

data "aws_availability_zones" "default" {
  state = "available"
}

data "aws_vpc" "default" {
  default = true
}

data "aws_subnets" "default" {
  count = length(data.aws_availability_zones.default.names)

  filter {
    name   = "vpc-id"
    values = [data.aws_vpc.default.id]
  }

  filter {
    name   = "availability-zone"
    values = [element(data.aws_availability_zones.default.names, count.index)]
  }
}

data "aws_security_group" "default" {
  vpc_id = data.aws_vpc.default.id
  name   = "default"
}

module "hooks_alb" {
  source  = "terraform-aws-modules/alb/aws"
  version = ">= 8"

  for_each = local.my_condition == true ? { 0 = 0 } : {}

  name               = "test"
  subnets            = flatten(data.aws_subnets.default[*].ids)
  internal           = false
  load_balancer_type = "application"
  vpc_id             = data.aws_vpc.default.id

  web_acl_arn = aws_wafv2_web_acl.this["0"].arn

  security_groups = [data.aws_security_group.default.id]
}

What is this for_each = local.my_condition == true ? { 0 = 0 } : {}

It comes form an option I put in a module that have this usecase. You can also replace by count = local.my_condition == true ? 1 : 0

This issue has been resolved in version 9.0.0 :tada:


Query data source for glob patterns

EXPERIMENTAL and horribly work-in-progress.
When a glob is given to IdentifiableCollection#[], query the data source and glob efficiently.
No visible speed improvement so far.

Benchmark.bmbm do |x|
  x.report('select') do
    10000.times { @items.select { |i| i.identifier =~ '/doc/*' } }
  end
  x.report('glob') do
    10000.times { Dir.glob('content/doc/*') }
  end
end

Rehearsal ------------------------------------------
select   3.390000   0.010000   3.400000 (  3.404135)
glob     0.220000   0.260000   0.480000 (  0.486837)
--------------------------------- total: 3.880000sec

             user     system      total        real
select   3.230000   0.010000   3.240000 (  3.238574)
glob     0.240000   0.280000   0.520000 (  0.526747)

GitHub developer site doesn’t have a significant speed-up. Three test runs:
Without globbing:
  Site compiled in 14.29s.
  Site compiled in 14.16s.
  Site compiled in 14.58s.

With globbing:
  Site compiled in 14.19s.
  Site compiled in 14.02s.
  Site compiled in 14.00s.

The preprocessor complicates this, because it can generate items/layouts just like data sources do. Perhaps it makes sense for the preprocessor to be backed by a data source. (But since the preprocessor can also delete items/layouts, this might become tricky too.)

Will close this for now. Needs more work.


Decide if we need a better name than LSDB

We will soon change the name hipscat (see https://github.com/astronomy-commons/hipscat/issues/332).
That is a chance to change the name LSDB if wanted. The issue is that LSDB stands for Large Survey DataBase, and it is explicitly not a database. This is confusing and we have received a feedback about it (notably from @lokizg)

After consideration and talking with Mario, Andy, we decided it is best to keep the name. The change would be disruptive; it is ``database'' of sorts and we feel it is sufficiently removed from any negative connotations of LSD, if there were any to start with.


style: add _ to local functions

Codecov Report

Merging #16 (d249700) into master (0315fa2) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #16   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          113       113
  Branches        20        20
=========================================
  Hits           113       113

Impacted Files
Coverage Δ

solutions/adv_2022_00.py
100.00% <100.00%> (ø)

solutions/adv_2022_01.py
100.00% <100.00%> (ø)

solutions/adv_2022_02.py
100.00% <100.00%> (ø)

solutions/adv_2022_03.py
100.00% <100.00%> (ø)

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


Manipulation handler moves object slower in vertical axis

Overview
When using manipulation handler on an empty object, the user can move it freely in the scene. However moving object in vertical axis seems to be slower than moving it in horizontal axis. This problem occurs only when I build the app on Hololens, in Unity editor it works well.
Expected Behavior
Object should move with the same speed in all directions when using manipulation handler.
Actual Behavior
Object moves slower when moved vertically then horizontally
Steps to reproduce
Add Manipulation handler to an object with collider. Build on Hololens.
Unity Editor Version
2019.2.6f1
Mixed Reality Toolkit Release Version
2.0.0

Duplicate of #5896


Fix the doc test for src/controller/mod.rs

Problem
The sample rust code in src/controller/mod.rs does not compile with a fresh clone of loco because it is using some methods and imports that are only available when the channels feature is enabled.
Solution
Update the sample code to guard the offending blocks of code with a cfg guard.

Nvm, I was using just cargo test, but I see CI is using cargo test --all-features --all, which allows the doc tests to pass.


chore: restructure submission status tests

This PR resolves []
Description

Restructure submission status tests
Follow up on https://github.com/artsy/eigen/pull/10733
PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

restructure submission status tests -daria

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (restructure submission status tests -daria)

  Generated by :no_entry_sign: dangerJS against b99dadd7de008e997ebb49149231d4a9f6a3785c


Projects that use spin (previously devpy)

We gather project names here so we can let them know in case of particularly disruptive changes, or make PRs to their repos to facilitate API transitions.

numpy
scikit-image
solcore5
skmisc
PyFVS
sktree

Dipy (work in progress)

python-mumps (if you're still collecting input).

python-flint is using spin/meson now although not fully migrated from setuptools yet (gh-182).


extended_text_field: 4.0.0 at pubspec.yaml brings compile error

extended_text_field: 4.0.0 at pubspec.yaml brings compile error, need to change to extended_text_field: 5.0.0

can we see the compile error please.?


Failures on Mac (Mono master) and Max/Linux (Mono 4.05)

I've enabled a build matrix in #476 but there are failures
https://travis-ci.org/fsharp/FSharp.Compiler.Service/jobs/94301490

@rneatherway If you get a chance to look that would be awesome.  The Mac+mono master  failure is in a recently adjusted part of the code

I think this is because the Mac version and old Mono are still populating the ChildProjectReferences correctly, so they now get duplicated. I can easily filter those out.


RewriteUnsafeSelect has bugs

Two issues.
First, the rewriter might contradict with previous rewriting rules, since it is the last rewriter.
A simple example is using Pad and vectorize it, and codegen will trigger a llvm assertion.
RewriteUnsafeSelect happens after Vectorizer, but not consider Vectorizer's rewriting.
Second, UnsafeExprDetector in RewriteUnsafeSelect seems too conservative.
Pad is still a good example.
I saw TODO there, so it might be unfinished work.
A precise detector might be difficult.
IMO, RewriteUnsafeSelect is totally unnecessary, if semantics of select is well-defined in tvm's programming model.
-L

Thanks for bringing this up. Can you elaborate a bit on what is going on here? The second issue sounds like an overly conservative detection.
Most normal user will use select as if_then_else and they are error-prone in the context of padding(depending on whether the device support OOB read, we want to be safe on it). So this rewriting is to support this semantics here. You can also think this as a rewriting if_then_else back to select.

Yes, the second issue is about overly conservative detection.
The detector classified non-OOB to OOB. It might because  it failed to simplifying one branch of stmt. (The root reason I am not sure.)
In the current situation with Pad op test case, tvm rewrote select to if_then_else under vectorization, and failed llvm.
Fundamentally, it is not about OOB access.
IMO, OOB shouldn't be involved in the programming model.
It is more about semantics of select.
IMO, the good semantics of select for general modern architectures will be something like this.
Both true and false stmt will executed before the condition stmt in arbitrary order.
If there are exceptions or side-effect on those stmts, use as your risk.
(We could further say one stmt could be eliminated as one optimization. but that didn't impact the semantics)
This is similar to CUDA's definition for branch.
With this definition, users guard their safety for using select.
Then, if a user has its own lower pass with particular hw support, and they can use unsafe select.
Then they can use unsafe one.
Then, we can put that currently overly conservative UnsafeDetector to debug mode.
When you want to refine it, you refine later. :)

I agree that this might be a better choice for performance. However, as select has also been extensively used for OOB read(padding),
The main problem is most high-level languages don't have select at all and it is usually a low-level construct. But people tend to use select in the place which they actually want if_then_else. Given this situation, we take a compromise by using unsafe-select rewriter to rewrite the un-safe ones.
We will likely need to keep this behavior for this compatibility reason. We can, however, introduce an new intrinsic e.g. branch which the unsafe rewriter ignores if necessary

After thinking a bit more about this, I think I agree with you on pin down the semantics of Select. This, however, would involve an upgrade of most code since many users assumed the semantics of if_then_else when using select. So it is more of matter of a safe upgrade and when to do so, one possible way to is:

introduce tvm.if_then_else, which serves as original select
migrate the code to use if_then_else
Keep the current UnsafeSelectDetector and throw an error to the user, to tell them to use if_then_else instead, this will at least give users a head up about this case
allow to optionally turn the unsafe detector off

Thanks, love you.
Let me confirm 1) Select will be kept.
and we will have 2) capability of disabling RewriteUnsafeSelect.
This will work.
BTW, I need to correct one thing.
Pad I mentioned is the Pad op, topi's or defined in onnx.
It doesn't rely on OOB read.
If i remember correctly in topi, you shift OOB read to edge read, so OOB won't happen.


Refactor logger.py: see extended desc

remove redundancy
refine type annotations
add logical spacing

now, the last few functions are still redundant. i think we should collapse them all into one function, with an added parameter mode which specifies whether it's debug, info, success, warning etc. but that's a pretty big change that'll change its functionality, so i'm asking y'all if we should do it

@Kronifer most of the lint errors are from other files. I'm only working on this one.

Lint fails are from other files which is NOT the purpose of this PR... sure, I can fix a few bare excepts, but that would make this PR messy, and it's bad practice
Also, don't merge this yet, I'm drafting, gotta refactor some more stuff

@Kronifer @dawnofmidnight Lint fails are from other files which is NOT the purpose of this PR... sure, I can fix a few bare excepts, but that would make this PR messy, and it's bad practice

Someone could open a PR to fix that then

@Kronifer @dawnofmidnight There have been new changes, please re-review.


Add my pictures and more features to make my portfolio more personal.

So this pull request contains 4 commits, is that intended?
Also, the description indicates it's only a simple change to README, but actually it contains more involved changes. Consider sending pull requests for each separate commits.

Do you know there is a way for us to view your portfolio page? Screenshot maybe if it's not deployed anywhere yet.

@Cayle I think the workflow we're going to try is always add both Ray and I as Reviewers on each PR, then one of us will Assign ourselves to do the actual review. I'll unassign myself and let you and Ray finish out the review.

@Cayle I think the workflow we're going to try is always add both Ray and I as Reviewers on each PR, then one of us will Assign ourselves to do the actual review. I'll unassign myself and let you and Ray finish out the review.

Okay, thanks. I will do that next time


Compat w/ Block Carpentry

Block Carpentry is a new mod recently released for 1.15.2 that adds a slab that can be placed horizontally or vertically and take on the texture of any block when right-clicked with said block. Is support for this mod possible?

Added in the latest version :)

The mod update their slab placement logic and is now crashing in the latest version according to this bug report: PianoManu/BlockCarpentry#12

Hello there! I'm still getting this crash with version 2.11.8 of Double Slabs and 0.8.1 of Block Carpentry
Report: https://paste.ee/p/tBH73


Update Deprecated Ubuntu Executor

Orb version
0.2.0
What happened
CircleCI have deprecated use of older Ubuntu executors, including ubuntu-1604:201903-01 which is presently set as the default executor for this orb. Below image shows the message that appears in any CircleCI pipeline that makes use of azure-acr-orb:

Expected behavior
Migrate to a newer Ubuntu executor as per the above CircleCI notice, so that come late-May, the orb can continue to be used.

I Have same issue , anyone has a solution for it ? or the orb wil be upgraded ?

I have the same issue as well. I'm getting this for all my jobs because of this!

Can this PR be expedited, as this orb is functionally broken now.

Hi @findyourexit,
There are other issues we are looking to resolve before the PR can be merged. As a workaround, you can specify a image like in the example below:
version: 2.1
orbs:
  azure-acr<EMAIL_ADDRESS>
jobs:
   build:
    machine: true
    steps:
    - azure-acr/build-and-push-image:
        login-server-name: "my_server"
        registry-name: "registry_name"
        repo: "repo_name"

workflows:
  my_workflow:
    jobs:
      - build

Hi @findyourexit @AlaaNabil26 @findyourexit , There are other issues we are looking to resolve before the PR can be merged. As a workaround, you can specify a image like in the example below:
version: 2.1
orbs:
  azure-acr<EMAIL_ADDRESS>
jobs:
   build:
    machine: true
    steps:
    - azure-acr/build-and-push-image:
        login-server-name: "my_server"
        registry-name: "registry_name"
        repo: "repo_name"

workflows:
  my_workflow:
    jobs:
      - build

Unbelievable! Thank you very much for your assistance with the workaround @HennaAbbas, this worked a treat 💯

Merged in #23.


Figure out what's up with zelda's intro

there are a bunch of graphical glitches in all implementations, so it seems like I got something wrong in interpreting the hardware docs
opus5 also shows very similar issues if anyone wants a free rom to test with

scroll-y is handled much better now, most games are good... zelda's intro still has a couple of glitches though :(

I read in some blog somewhere (Can't remember or find it :( ) somebody posted "you'll get glitches like this if you aren't careful to accurately emulate sub-pixel CPU timings", with an image of what looks like the glitches I'm seeing.
Drawing one row of pixels at a time is about as complicated as I imagine rosettaboy getting, so I'd say we just need to live with this (unless somebody comes up with a pixel-perfect GPU implementation, which is also simple to understand and maintain, and implement across languages)


pango: devdoc target is not reproducible

Describe the bug
Building the devdoc output of pango does not produce the exact same output each time it is build.
Having bit-by-bit reproducible derivations makes auditing build processes easier. This package is especially interesting since it is part of the milestone tracked by https://r13y.com
To Reproduce
Steps to reproduce the behavior:
nix-build "<nixpkgs>" -A pango.devdoc --check
Expected behavior
Success!
Additional context
There is an upstream patch to gi-docgen at https://gitlab.gnome.org/GNOME/gi-docgen/-/merge_requests/53/diffs.patch that might help, but doesn't seem to completely fix the issue yet. Starting point:
diff --git a/pkgs/development/tools/documentation/gi-docgen/default.nix b/pkgs/development/tools/documentation/gi-docgen/default.nix
index 72b5364eb45..57dbe62a667 100644
--- a/pkgs/development/tools/documentation/gi-docgen/default.nix
+++ b/pkgs/development/tools/documentation/gi-docgen/default.nix
@@ -61,6 +61,11 @@ python3.pkgs.buildPythonApplication rec {
       url = "https://gitlab.gnome.org/jtojnar/gi-docgen/commit/08dcc31f62be1a5af9bd9f8f702f321f4b5cffde.patch";
       sha256 = "vAT8s7zQ9zCoZWK+6PsxcD5/48ZAfIOl4RSNljRCGWQ=";
     })
+    # make DevHelp sections & index.json have stable ordering
+    (fetchpatch {
+      url = "https://gitlab.gnome.org/GNOME/gi-docgen/-/merge_requests/53/diffs.patch";
+      sha256 = "sha256-nG0Dt///w7agXAvWNtGdBQSaKMXNHraGO1svmn9FynI=";
+    })
   ];

   nativeBuildInputs = [

The lastest commit should address all issues, but I need help reproducing the (lack of) reproducibility. Can anyone check compiling pango before/after patching, to confirm the devhelp and index.json diffs are now gone? Thanks.

OK managed to reproduce pango not being reproducible at HEAD. With the patch, I cannot get it to fail after multiple attempts event under stress(1) load.

Now waiting for upstream to merge.

Can confirm this fixes it here as well!
PR'ed as #118978 to get the patch in for 21.05

Maybe this can be closed now?


Integration Test - Release - 2020/10/20 23:12:20

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

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


Need a "Create An Issue" button next to "Edit" button

Issue type: Feature enhancement
Complexity: Easy
Issue description:
https://docs.openebs.io/ pages have "Edit" button on the top right position of the page that links to the corresponding github page.
This issue is about the need to have a new button called "Create An Issue" next to or before the edit button which when clicked will start the process for creating a github issue related to that page
As an example, refer to https://kubernetes.io/docs/user-journeys/users/application-developer/foundational/#section-2

Can I give it a try?

@Akash4927 - I added translation for "Create An Issue" in website/i18n/en.json (pages-strings) but on doing npm start it is removing that line thus giving error. Other than that, I have added the button for
"Create An Issue"

@Akash4927 - figured it out! Creating a PR

@aakash2602 website/i18n/en.json is an autogenerated file.


PASSWORD LENGTH PROMPT

User Story
AS AN employee with access to sensitive data
I WANT to randomly generate a password that meets certain criteria
SO THAT I can create a strong password that provides greater security
Acceptance Criteria
GIVEN I need a new, secure password
WHEN prompted for the length of the password
THEN I choose a length of at least 8 characters and no more than 128 characters

Completed in series of latest commits.


https traffic is not proxied

After the error fix from #56 I'm still not able to catch https traffic, firefox is responding with a Secure Connection Failed error. Http traffic is working as expected. The code is still the same:
var port = 46769;
var proxy = hoxy.createServer({
    certAuthority: {
        key: fs.readFileSync('f:/ssl/key.pem'),
        cert: fs.readFileSync('f:/ssl/cert.pem')
    }
}).listen(port);

proxy.intercept({
    phase: 'request'
}, function(req, resp, cycle) {
    console.log(123);
});
console.log('tunnel through', port);

No console logging happens when requesting through https and the error in firefox happens as a timeout. (I've tried it in Chrome with no difference in behaviour)

Can you verify that your cert has been added to Firefox's list of trusted authorities? (http://greim.github.io/hoxy/#intercept-https)
Also, can you verify OpenSSL is in your path? (https://github.com/andris9/pem/issues/58)

Creating the ssl files using your examples did not work at first so I created them with other commands, I noticed your creating a certificate using rather specific settings, so that went wrong.
let { clientKey: key, certificate: cert } = yield create({
    country: 'US',
    state: 'Utah',
    locality: 'Provo',
    organization: 'ACME Tech Inc',
    commonName: serverName,
    serviceKey: rootKey,
    serviceCertificate: rootCert,
    serial: Date.now(),
    days: 500,
})

I finally found what went wrong with creating the files usiong your example so I created them that way.
(BTW, adding a second argument to the above function with a callback handling some error logging helped a lot, I'd think adding it would be a good addition
let { clientKey: key, certificate: cert } = yield create({
    country: 'US',
    state: 'Utah',
    locality: 'Provo',
    organization: 'ACME Tech Inc',
    commonName: serverName,
    serviceKey: rootKey,
    serviceCertificate: rootCert,
    serial: Date.now(),
    days: 500,
}, function(err, data) {
    if(err) console.log('err: ', err);
    console.log(data);
})

)
So currently I have created the my-private-root-ca.key.pem and my-private-root-ca.crt.pem exactly via the commands you used. This yields no errors from the above mentioned callback.
I have added the following before creating the hoxy server:
// not really needed, openssl can be found on my path
process.env.OPENSSL_BIN = 'C:\\Program Files (x86)\\Git\\bin\\openssl.exe';
// this was not found by default in my setup
process.env.OPENSSL_CONF = 'C:\\Program Files (x86)\\Git\\ssl\\openssl.cnf';

The errors there are solved when I run the scenario now it still does not respond to ssl traffic, the data log returns the certificates and keys and stuff but still no logging from the interceptor nor the page getting a response.
The certificate is added to the firefox trusted authorities.

Rats. I was hoping there would be an easy fix :( I'll have to try to replicate this on Windows, which takes a bit of effort since I have to do it in VirtualBox.

Funny thing is, if I do not have the callback function with the error and data logging in it, I get another EADDRNOTAVAIL error.
Error: connect EADDRNOTAVAIL
    at exports._errnoException (util.js:746:11)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)

When the callback is there, the error is empty and the data consists of an object with csr, clientKey, certificate and serviceKey keys.

let create = adapt.part(pem.createCertificate)

Adding a callback to the create() call will likely cause incorrect behavior, since create() returns a promise. To properly listen for errors on it, maybe wrap yield create(...) in a try/catch and then re-throw the error from the catch.

Alright, when doing it with a try/catch block I get the EADDRNOTAVAIL error, when I try it like this:
return create({
    country: 'US',
    state: 'Utah',
    locality: 'Provo',
    organization: 'ACME Tech Inc',
    commonName: serverName,
    serviceKey: rootKey,
    serviceCertificate: rootCert,
    serial: Date.now(),
    days: 500
}).then(function(data) {
    console.log('success', arguments);
    return data;
},function() {
    console.log('err', arguments);
});

I get the EADDRNOTAVAIL error, when I leave out the return data; I get no error. So basically the error is happening after the create call if it receives data.

Since you're able to replicate this directly, in your environment, in proxy.js line 218, can you try changing:
let serverSocket = net.connect(addr.port, addr.address, () => {

...to this:
let serverSocket = net.connect(addr.port, 'localhost', () => {

...and see if that fixes the error?

Tried that to no avail... however in the process I did find the answer a bit lower.
On line 235 I added a log of addr resulting in the following:
{ address: '::', family: 'IPv6', port: 46769 }

Not sure if you've tested the ssl methods with IPv6 yet? Anyway, besides that, I don't think the address of :: is valid it's either ::1 or localhost and preferably the latter since that is IPv4 compatible.
so changing the address did the trick!
let toServer = http.request({
  host: 'localhost',
  port: addr.port,
  method: fromClient.method,
  path: fullUrl,
  headers: fromClient.headers,
}, fromServer => {
  toClient.writeHead(fromServer.statusCode, fromServer.headers)
  fromServer.pipe(toClient)
})

I'm getting https pages now as well as intercepts being handled.

Sorry, accidentally closed the issue while it's not fixed in Hoxy yet...

Was that in addition to my suggested fix above, or instead of?

I tested it with and without your fix, so far it made no difference so I
think it's not needed.
On 27 Aug 2015 16:36, "Greg Reimer"<EMAIL_ADDRESS>wrote:

Was that in addition to my suggested fix above, or instead of?
—
Reply to this email directly or view it on GitHub
https://github.com/greim/hoxy/issues/57#issuecomment-135454496.

Just pushed this fix to master. https://github.com/greim/hoxy/commit/1e7d50ae833d1358bf1cf2e24daad9694d9b3a68 Do you want to verify it works, or are you confident it will solve this issue?

Just verified, https pages coming through and are intercepted!

I just installed newest hoxy (3.1.2) and for that code:
var hoxy = require('hoxy');
var fs = require('fs');

var PROXY_PORT = 8001;

var proxy = new hoxy.createServer({
	certAuthority: {
		key: fs.readFileSync('./my-private-root-ca.key.pem'),
		cert: fs.readFileSync('./my-private-root-ca.crt.pem')
	}
}).listen(PROXY_PORT, function() {
	console.log('proxy listens on: ' + PROXY_PORT);
});

proxy.intercept('request', function(req, resp, cycle) {
	console.log('req');
    console.log('resp');
});

proxy.log('error warn debug info');

i'm getting errors in terminal:
28 Aug 08:58:55 - [nodemon] restarting due to changes...
28 Aug 08:58:55 - [nodemon] starting `node run-hoxy.js`
28 Aug 08:58:55 - [nodemon] restarting due to changes...
28 Aug 08:58:55 - [nodemon] restarting due to changes...
28 Aug 08:58:55 - [nodemon] restarting due to changes...
28 Aug 08:58:56 - [nodemon] starting `node run-hoxy.js`
proxy listens on: 8001
INFO: generated fake credentials for localhost
INFO: generated fake credentials for ssl.gstatic.com
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: connect EADDRNOTAVAIL
    at exports._errnoException (util.js:746:11)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)
28 Aug 08:59:13 - [nodemon] app crashed - waiting for file changes before starting...

am i missing something?

3.1.2 does not have the fix in it yet, you need to build the project yourself if you want to test it.

Thanks, I will check it.

Upgrade resolved problem with EADDRNOTAVAIL, but now I'm getting:
28 Aug 14:53:21 - [nodemon] v1.4.1
28 Aug 14:53:21 - [nodemon] to restart at any time, enter `rs`
28 Aug 14:53:21 - [nodemon] watching: *.*
28 Aug 14:53:21 - [nodemon] starting `node run-hoxy.js`
proProxy API listens on: 8002
proProxy listens on: 8001
INFO: generated fake credentials for www.google.pl
INFO: generated fake credentials for debug.mms.localhost
INFO: generated fake credentials for ssl.gstatic.com
INFO: generated fake credentials for clients4.google.com
INFO: generated fake credentials for clients1.google.com
INFO: generated fake credentials for localhost
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: socket hang up
    at createHangUpError (_http_client.js:215:15)
    at Socket.socketOnEnd (_http_client.js:300:23)
    at Socket.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickCallback (node.js:355:11)
28 Aug 14:55:39 - [nodemon] app crashed - waiting for file changes before starting...

Error occurs when Chrome fails to load a page (https://debug.mms.local) and:
No data received
ERR_EMPTY_RESPONSE

error page shows up.
I added certificates to chrome.
My code:
var hoxy = require('hoxy');
var _ = require('lodash');
var fs = require('fs');

var PROXY_PORT = 8001;
var proxy = new hoxy.createServer({
	certAuthority: {
		key: fs.readFileSync('./my-private-root-ca.key.pem'),
		cert: fs.readFileSync('./my-private-root-ca.crt.pem')
	}
}).listen(PROXY_PORT, function() {
	console.log('proProxy listens on: ' + PROXY_PORT);
});

proxy.intercept({
	phase: 'response',
	url: '/api/mms/login',
	method: 'POST',
	mimeType: 'application/json',
	as: 'json'
}, function(req, resp, cycle) {
	console.log(resp.json.response);
});

proxy.intercept({
	phase: 'response',
	url: '/api/v1/login',
	method: 'POST',
	mimeType: 'application/json',
	as: 'json'
}, function(req, resp, cycle) {
	console.log(resp.json.response);
});

Could you help me with this?

Can you reach https://debug.mms.local without the proxy? I think you're not running a server on that address or it's not responding. If I call https://some.local.address that's not directing anywhere listening I get the same error. So I'd say, try it without proxy first.
Note: the part that It's actually crashing shouldn't happen though.
Technically it should be returning a 504 Gateway Timeout.

Yeah, i can reach it without proxy. I got apache server running on <IP_ADDRESS>, it's mapped in hosts to debug.mms.local.

I see debug.mms.localhost mentioned in one place and debug.mms.local in another place. Could there be a wrong url or misconfig somewhere?

Regular https calls are working as expected, I think this is a different issue. I've run into something similar and created a new issue #60 for it. So I'm closing this one.


test: add a few more simulator tests

Hey, I've went ahead and added a few more simulator tests before I commit to refactoring. Just to make sure I don't accidentally break anything.
Something of note is that as you can probably see from the jump nz test the simulator speed is just fine. It loops in less than 100ms on my machine.
The issue with the web version is likely that it's limited by setInterval(sim, 0) in footer.js. Browsers usually throttle the intervals to at least 4ms per tick.

I must say I am a bit confused. Why are you writing simulator tests if you are about to rewrite them anyway?

It's generally regarded as good practice write tests before touching something to prove that working code keeps working and no new bugs get introduced.
Makes it much easier to refactor later on as you can have a larger degree of confidence when making changes.
It's called TDD and there's plenty online, basically boils to start the development loop by writing tests first.

If it's existing code you write a test that passes on the existing code.
Then write tests that work over your expected changes (which must fail).
Finally write the code and run the tests again.

If it's new code.

Write the test. Test must fail
Then write the code which should now pass the test.

It's generally regarded as good practice write tests before touching something to prove that working code keeps working and no new bugs get introduced.
Makes it much easier to refactor later on as you can have a larger degree of confidence when making changes.
It's called TDD and there's plenty online, basically boils to start the development loop by writing tests first.

If it's existing code you write a test that passes on the existing code.
Then write tests that work over your expected changes (which must fail).
Finally write the code and run the tests again.

If it's new code.

Write the test. Test must fail
Then write the code which should now pass the test.

Yeah, I remember that from my Object Oriented Development classes. I hated my Object Oriented Development classes. I failed my Object Oriented Development written exam 3 times. It made me hate the C# programming language, which we used in our Object Oriented Development classes.

It's not really related to Object Oriented (or any language). It's just a different way to organize the development loop.
Instead of code, test (manually) then repeat. You write the tests first, then you code agaisnt those tests and then repeat.
You get the benefits of well tested code and because you are forced to test first you get testable code for free.
Why would you want well tested code is another discussion but boils to generally easier to reason about and mantain. You can refactor away knowing that you won't break an unrelated part of the project.
Finally having a test suite running those tests (like github actions in this case) makes so that as long as the code is covered by a test it's impossible to merge code that breaks a test.

The issue with the web version is likely that it's limited by setInterval(sim, 0) in footer.js. Browsers usually throttle the intervals to at least 4ms per tick.

I don't think that's what's going on. I think that it's the DOM manipulation (particularly SVGs) that are slowing it down. I think the proper way to speed it up would be to enable the user to hide SVGs and the tables with registers, memories and flags in case he or she is running a program that doesn't require those things.

Hmm I'm pretty positive that's not the case but I'd love to back it up with an example.
Once I'm done with the globals I'll show you we can massively speed up the execution by simply changing the setInterval for something else like a simple while loop or requestAnimationFrame.


Allow changing default Test Explorer suggestion for additional test extensions

We are using the vscode testing api to populate and run the tests for our app.
However, when the test(s) are not defined or not found because of other issues, the user mostly clicks the "Install Additional Test Extensions..". And they often end up in a more messy situation since no other extension supports our domain specific language.
Can we disable this button or show a different message? Would be great if you support this.

The recommended solution here is to contribute to the welcome view.
Here's how the Python extension does it, for example. You can set context keys so that the view is only shown at relevant times (e.g. when a workspace has code in the language your test runner is interested in) https://github.com/microsoft/vscode-python/blob/e40fe9d8f3a56aa003272aa6acf9ad081d60207b/package.json#L1924-L1928


Fix consumer context bug in Kafka PubSub

Signed-off-by: Joni Collinge<EMAIL_ADDRESS>Description
Fixes a bug in the Kafka PubSub component where it does not handle the consumer context or the subscription context correctly.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

this looks to be partially fixed in https://github.com/dapr/components-contrib/commit/dd4db996c6a449ef513fec9ca78dc5cf91afd718

Can you open this against 1.13? Main branch is not up to date with the latest changes

Yes let me rebase on 1.13 and resolve the conflict.

closing as does not appear to exhibit different behavior to existing fix.


Updated the README about supported docker versions

Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

Funnily enough this was already like this in the gh-pages branch.


feat: anymaniax#352 support allOf

Status

READY
Description
fix allOf type definition
e.g. https://github.com/anymaniax/orval/issues/352
Related PRs
https://github.com/anymaniax/orval/pull/503
Change
before
export type GetPets200PetsItemAllOf = {
  /** required name */
  name?: unknown;
  /** @deprecated */
  owner?: unknown;
};

export type GetPets200PetsItem = Pet & unknown & GetPets200PetsItemAllOf;

export type GetPets200 = {
  pets?: GetPets200PetsItem[];
};

/**
 * default Person description
 */
export interface Person {
  id: string;
  /** default Person name */
  name?: string;
}

export type PetOwnerAllOf = {
  /** required name */
  name?: unknown;
};

export type PetOwner = Person & PetOwnerAllOf;

/**
 * default Pet description
 */
export interface Pet {
  id?: string;
  /** default Pet name */
  name?: string;
  owner: PetOwner;
}

after
/**
 * default Person description
 * @deprecated
 */
export type GetPets200PetsItemOwner = {
  id: string;
  /** required name */
  name: string;
};

/**
 * default Pet description
 */
export type GetPets200PetsItem = {
  id?: string;
  /** required name */
  name: string;
  /**
   * default Person description
   * @deprecated
   */
  owner: GetPets200PetsItemOwner;
};

export type GetPets200 = {
  pets?: GetPets200PetsItem[];
};

/**
 * default Person description
 */
export interface Person {
  id: string;
  /** default Person name */
  name?: string;
}

/**
 * default Person description
 */
export type PetOwner = {
  id: string;
  /** required name */
  name: string;
};

/**
 * default Pet description
 */
export interface Pet {
  id?: string;
  /** default Pet name */
  name?: string;
  /** default Person description */
  owner: PetOwner;
}

@anymaniax  Resubmitted a fix pull request for allOf. I have rewritten it to a simpler code, so please consider it.

I did other test with more complex specification. I got a RangeError: Maximum call stack size exceeded.

@anymaniax Can I have the Swagger file that I tested here?

I cannot share it but will try to do a reproduction of the issue

@anymaniax In specs where the elements of objects and arrays are cyclically referenced, as expected. I wonder if the recursive function never ends. Is that API realistic?


commands are not executed

Just installed nsp. When running nsp audit-package or nsp version no results are printed. Even with the version command.
Debugging the code shows that the action callback in the celery.option is never called.
Do others have the same issue?

I just did a fresh install on 0.10.36 and I'm getting the same result. I'm guessing one of our dependencies changed out from under us. :/

@jkaizer I pushed a version to master with a npm-shrinkwrap.json that has the proper and working dependencies. We decided internally that we are going to dump celeri as it's way to complex and isn't being actively maintained well enough.
Can you install<EMAIL_ADDRESS>and let me know if it's resolved for now?

Yes, this works!
Thanks very much for the quick response.


PageHeader: Add component and documentation

New PageHeader cmp
Test Plan

Tests still need to be added

For the page header, we're using heading md in the designs. Heading lg is very, very big.
We may want to do a background wash of grey just to be able to see the full header component. Right now it is 80px high in spec and 32px of padding left and right.


API rate limit when control-clicking progress bar

should be a rare case, but should be fixed anyway

Fixed in #19


Karma Debug

Karma debugging.  The tests pass in phantomjs if you use the --debug flag.

Looks good! Ready for merge? Sorry I took so long getting to reviewing your stuff, been a pretty hectic week so far.


Allow HACV LL CI to fail

synced local file(s) with worgarside/github-config-files.

This PR was created automatically by the repo-file-sync-action workflow run #10636495941

This PR is empty, closing it. :no_good:


Avalonia.MonoMac NSFileManager GetAttributes & SetAttributes segfaults no matter what I do.

var attrs = NSFileManager.DefaultManager.GetAttributes(filePath); results in an immediate "Segmentation fault: 11".
Same with SetAttributes.
No matter what voodoo I try, nothing works, wrapping it in a NSAutoreleasePool, using InvokeOnMainThread, or invoking GC.KeepAlive(NSFileManager.DefaultManager). I looked into Avalonia.MonoMac's source and didn't see any major deviations from the standard MonoMac; so I have no idea what is going on here.
If I feed it an invalid path name I don't get a segmentation fault, and instead get a path not found error in NSError; so clearly it's finding the file, but something is over-releasing.
In Xamarin it works without any special considerations but .NET Core support is only planned for 2021 so that's not exactly a viable option for me.

I suspect that "standard MonoMac" has the same issue.
Our fork simply provides a netstandard build and a nuget-package, don't expect it to be really maintained.
We are currently using an ObjectiveC/C++ native library for native interop on OSX, so I'd suggest to either do the same or P/Invoke libobjc directly


📚 -

What is the affected URL?
https://taiga-ui.dev/getting-started
Description
Need to add command for install taiga-ui in nx workspaces
nx g @taiga-ui/cdk:ng-add
Which browsers have you used?

[X] Chrome
[X] Firefox
[X] Safari
[X] Edge

Which operating systems have you used?

[X] macOS
[X] Windows
[X] Linux
[X] iOS
[X] Android

fixed by next
https://taiga-ui.dev/next/


Clipping planes interfere with lines

renderTubes: false
lineWidth: 5
startLayer: 1
endLayer: 2

expected:


Svelte language server

Hi, this is my fist PR to any project so I'm sorry if I'm doing some basics wrong.
I tried to add the svelte server exactly like the others and tested it by adding "additional_languages" in my lspcontainers.nvim config. It is working for me. I can also create a PR on the lspcontainers.nvim repo to add svelte to the supported languages.

This is great! I should be able to take it from here! Thank you!


ISPN-6182 Scala blueprint generator does not work on JDK 1.9

https://issues.jboss.org/browse/ISPN-6182

Looking...

hey @mgencur, I get this error: https://gist.githubusercontent.com/anistor/ba7e4dab3ca2d71f3131/raw/01a8d2f338ed51aaa96188a23dfe5572b6debce3/gistfile1.txt
I have Java "9-ea", maven 3.3.3.
Ever seen something similar?

Sure. It's the same problem I'm solving here. I got rid of scala where I could. But for Hotrod modules there is no workaround. See the jira and the referenced jira in it.

Updated the jira description

Understood. thanks!

merged! thanks
I updated the JIRA description to make this task as "build infinispan-core successfully on JDK9" as we still have the problem with other modules.

@mgencur Thanks for fix :smile:


Adding Azure France regions

Adding Azure France regions

Can this PR be approved and deployed to production please.

Thanks for contributing. The effect to enable speed test on new region is more than one line code change. Additional infrastructure works like setup storage account are required.
Since I France central is already added, I will close this PR.
Thanks all the same


Memory Leak

Today, I've seen Whatsie to occupy 10 gigs of RAM. I killed the process. I restarted it and then I got 5 gigs after 20 minutes of usage.
Something is causing the memory to leak.

Environment

Fedora 36
Snap

I will check. Can you provide the debug info from about section of app?

@keshavbhatt
whatsie -b spits out below:
Gtk-Message: 12:56:41.578: Failed to load module "colorreload-gtk-module"
Gtk-Message: 12:56:41.578: Failed to load module "appmenu-gtk-module"
Feature rich WhatsApp web client based on Qt WebEngine
 version: 4.8, branch: main, commit: d03e9fc, built_at: 2022-08-30T15:43:06UTC

As for runtime logs, I have logged out and logged back in and problem solved itself. If I ever have it again, I will provide it.
BTW, where is "about" section? Whatsie does not have any native menu, so I couldn't find it.

Whatsie have system tray support if your desktop have a system tray, which has a context menu with lots of entries. If you dont have system tray on your desktop you can access them from Desktop actions, right click on whatsie icon in your taskbar to access few options.

Whatsie have system tray support if your desktop have a system tray, which has a context menu with lots of entries. If you dont have system tray on your desktop you can access them from Desktop actions, right click on whatsie icon in your taskbar to access few options.

"About > Show Debug Info" displays below:
WhatSie
Version: 4.8
Source Branch: main
Commit Hash: d03e9fc
Build Datetime: 2022-08-30T15:43:06UTC
Qt Runtime Version: 5.15.4
Qt Compiled Version: 5.15.4
System: Ubuntu Core 20
Architecture: x86_64

Also, Whatsie stucks on "Organizing Messages" as seen below:

This might be related to #72 because I get the same high CPU usages and it leaks memory after a while up to 10 gigs.

Yeah the problem of loading sticking at organizing messages is known. Strange part is, the issue is not reproducible and I am not able to detect what is causing it. Memory leaks is happen in the webengine side since the page is stuck doing something that is not progressing. I am not doing anything from the code its just a simple page load event. So, i have no control atm on it. I will try to debug it when i will get a chance to see it on my install.
Thanks for reporting.

Also, It seems like a known problem with whatsapp web since they rolled out new version, a quick google search returns lot of results. Anyway i will try my best to fix it on Whatsie.

We will track this issue here https://github.com/keshavbhatt/whatsie/issues/58


Performance - defer loading and evaluating 3rd party scripts

According to PageSpeed Insights, we need to optimize loading third party code.

Using async instead of defer because I imagine that the page load event is important to event trackers

Loading third-party JavaScript

Also note https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript says:

In Blink-based browsers, async and defer currently lower the priority of the network request for resources so it can cause it to load significantly later than it would as a blocking script. This is useful to know in particular for analytics scripts.

Also note https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript says:

In Blink-based browsers, async and defer currently lower the priority of the network request for resources so it can cause it to load significantly later than it would as a blocking script. This is useful to know in particular for analytics scripts.


Update dependencies

Updated python to 3.12.1
Updated prometheus-client to 0.19.0
Updated asterisk-ami to 0.1.7
Updated jsonschema to 4.20.0
Updated Docker image to use python:3.12.1-alpine
Updated Flake8 to run on ubuntu-22.04
Updated Flake8 to use python version 3.12.1

On Python version 3.12.1, Python issues the following warnings in the asterisk-ami library:
asterisk-prometheus-exporter/.venv/lib/python3.12/site-packages/asterisk/ami/client.py:52: SyntaxWarning: invalid escape sequence '\.'
  asterisk_start_regex = re.compile('^Asterisk *Call *Manager/(?P<version>([0-9]+\.)*[0-9]+)', re.IGNORECASE)
asterisk-prometheus-exporter/.venv/lib/python3.12/site-packages/asterisk/ami/response.py:7: SyntaxWarning: invalid escape sequence '\-'
  key_regex = re.compile('^[a-zA-Z0-9_\-]+$')

According to the website https://adamj.eu/tech/2022/11/04/why-does-python-deprecationwarning-invalid-escape-sequence/ this is a warning that future Python versions may change to a syntax error. However, this is a bug that needs to be fixed in the asterisk-ami library. I'll leave the PR open until the warning is fixed.

The syntax warning in the asterisk-ami library was fixed with version 0.1.7.


Adding observation about accepted types in attributes

We should add a little phrase warning the clients about not using nested values in the attributes key in evaluate options :)

Thank you for your contribution!


Replace synchronization by Lock in FutureImpl

This one is a little more tricky, because of synchronization in a constructor, but works fine.

Similar to https://github.com/vavr-io/vavr/pull/2845
I replaced synchronized blocks by Lock because of virtual threads. More details: https://docs.oracle.com/en/java/javase/21/core/virtual-threads.html#GUID-04C03FFC-066D-4857-85B9-E5A27A875AF9

It's ok for now, but I'd definitely revisit the design of Vavr's Future. That locking in constructor feels excessive - I believe that immutable objects can be actually mutable inside as long as this this doesn't leak. It also feels that the current implementation tries to be overly smart by inducing happens-before using synchronized instead of plain volatile


Update gemspec; does not support Sidekiq 3.0, only 3.1+

Tested this on 3.0.0, 3.0.1 and 3.0.2, neither of them worked, so I figured the gemspec should be changed accordingly :)
PS. Tests fail because TravisCI runs them against latest Sidekiq version and the fix for #1 is not in this branch.

I believe I just looked for anything relevant in the changelog when trying to find the lowest version supported.  Glad to see you pegged down an exact version :thumbsup:


Adopt packages orphaned

Description of changes

Tracking parts of https://github.com/NixOS/nixpkgs/issues/266901
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@peterhoeg @fgaz


loadinFeature/panda Merge 3176 customer coupon component into PANDA-3170 (#…

…3026)
We merge PANDA-3175(customer-coupon service) into PANDA-3176(customer-coupon component) , so that Customer-Coupon feature finished.
And then merge PANDA-3177(claim customer coupon) and PANDA-3178(find product) into PANDA-3176.
Now PANDA-3170 finished.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Node Debugger not working

Issue Type: Bug
The built in Node.js debug extension says it's enabled and I don't see any errors in the output window related to it, but "type": "node" is not recognized in my .vscode/launch.json files and the menu which helps create new launch.json files does not list "Node.js" as an option. I've tried searching existing issues and googling but there's too much vscode debugging or general nodejs debugging noise .
OS: Arch Linux, installed VSCode and Node using the main AUR packages.
VS Code version: Code 1.24.1 (24f62626b222e9a8313213fb64b10d741a326288, 2018-06-13T17:47:35.732Z)
OS version: Linux x64 4.14.52-1-lts

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: unavailable_softwarevideo_encode: enabledvpx_decode: unavailable_softwarewebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
15.39GB (2.95GB free)

Process Argv
/opt/visual-studio-code/code

Screen Reader
no

VM
0%

Extensions (15)

Extension
Author (truncated)
Version

vscode-markdownlint
Dav
0.18.0

EditorConfig
Edi
0.12.4

html-css-class-completion
Zig
1.17.1

project-manager
ale
8.0.0

npm-intellisense
chr
1.3.0

vscode-npm-script
eg2
0.3.5

prettier-vscode
esb
1.5.0

file-icons
fil
1.0.12

vscode-firefox-debug
hbe
1.4.1

language-haskell
jus
2.5.0

vsliveshare
ms-
0.3.379

debugger-for-chrome
msj
4.7.0

ide-purescript
nwo
0.19.0

language-purescript
nwo
0.1.2

vim
vsc
0.14.2

(1 theme extensions excluded)

Please make sure that the built-in node-debug extensions are enabled:

Ah, legacy was disabled. It seems to work now.. wasn't expecting them to be connected like that (also not sure how the legacy one got disabled in the first place)


Add a license please

HI @gobwas , I would like to use a few examples in some OSS I am building. Would it possible for you to add a license so that I can make use of the code ?
I am mostly interested in the goroutine pool implementation https://github.com/gobwas/ws-examples/tree/master/src/gopool
Thanks !

Hi @darxtrix!
Sorry for a such huge delay. Added license just now.


ideas

i would suggest you two useful alternatives:

instead of open and fill the login form, just POST the form action url
if available, prefer and act as a mobile request, often mobile version are way easier

keep on improving this tool, would be nice to have the leaks without popping out a web browser
regards

Thank you for the ideas but for the first idea not all the websites I can post to it !
Some websites action url randomly generated for every session so the page have to be loaded.


No more S20 on aliexpress - B25 support?

Hi
As there is no more EU S20 on aliexpress, do you plan to support the successor B25 soon? Thanks.

Yes, it would be great to be able to manipulate the S25 here in the US from code!


Has this been tested to work with Chocoloatey?

Has this been tested to work with Chocolatey?
According to the Chocolatey Docs, Chocolatey "is compatible everywhere you can put a NuGet package".
Thoughts?

@dougthor42, I am using it with chocolatey since a year now and have had no issues.

Awesome, thanks @helge000! I hope to set it up by the end of this week. If there are any caveats that I find I'll be sure to record them here.

Just throwing this out there as @helge000 found this - We made some new optimizations to Chocolatey for 0.10.12+ - these optimizations mean we are using the Packages() url with a filter. It appears some repositories do not support this. We've put out a beta for folks to shut off the optimizations by affected repositories (0.10.14-beta).
References

Package Querying Optimizations - https://github.com/chocolatey/choco/issues/1397
New Feature to Disable the optimizations for 0.10.14 (including instructions) - https://github.com/chocolatey/choco/issues/1770

Should have been a bit more clear - Simple NuGet Server doesn't yet support those optimizations.


Changing border_width in YAML theme file has no effect on admonition block borders

Version
$ asciidoctor-pdf -V
Asciidoctor PDF 1.5.0.alpha.11 using Asciidoctor 1.5.4 [http://asciidoctor.org]
Runtime Environment (ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]) (lc:UTF-8 fs:UTF-8 in:- ex:UTF-8)

My Wish
I want to add a border (and background colour) to the admonition blocks in my PDF output.
What I've Tried
The admonition section of my YAML theme file looks like this:
admonition:
  background_color: f5f5f5
  border_color: 7d7d7d
  border_width: $base_border_width
  padding: [0, $horizontal_rhythm, 0, $horizontal_rhythm]

background_color has no effect (I added that).
changing border_colorchanges the colour of the vertical separator line between the icon and the text.
changing border_width doesn't have the desired effect. I've altered this value to 5but:

no external border appears around the admonition block and
the width of the vertical separator line between the icon and the text doesn't change either.

The only way I've managed to achieve anything near to what I'm hoping for is by enclosing my admonitions in a sidebar block as such:
****
[NOTE]
====
This is a note admonition block enclosed in a sidebar block +
which seems like a bit of a hack to achieve my wish.
====
****

Question
Any tips on how to achieve my wish?

Going through the Ruby code it seems this is the offending line:
https://github.com/asciidoctor/asciidoctor-pdf/blob/master/lib/asciidoctor-pdf/converter.rb#L433
The bounding box border is set to 0:
bounding_box [0, cursor]

From the comments in the code it looks like the admonition block formatting is filled with FIXME HACKs so I tentatively ask whether this change is wise?
I'll give it a whirl on my side and see how it goes.

I tried adding [stroke_bounds](http://www.rubydoc.info/github/sandal/prawn/Prawn%2FDocument%3Abounding_box) at various points in the [def convert_admonition node](https://github.com/asciidoctor/asciidoctor-pdf/blob/master/lib/asciidoctor-pdf/converter.rb#L411) function but only weird stuff happened.
As this is my first foray into Ruby and Prawn I'll wait for some wiser folk to chirp up and maybe pluck up the courage to dig a bit deeper.

We should also add the option to set a background color, which happens to be part of the same implementation.
Being about to set a surrounding border and background color is closely related #362 and #259.

It's now possible to control the width of the vertical line between the label / icon and the content.
https://github.com/asciidoctor/asciidoctor-pdf/blob/master/docs/theming-guide.adoc#keys-admonition
It's now called column_rule so as not to confuse it with a border around the block, which is not yet implemented.

The focus of this issue is to add a border around the whole block.


Bug ? Door fully open when scrolling down to close it

Hi, I just installed the module and test it and found out what I think may be an issue :
When a player slowly open a door by scrolling up and then close it by scrolling down fast the door will close and then fully open itself without me left clicking.

That might be a desynch problem, i will look into it.

(I'm testing with two browser tab one for gm and one for player) I will try to find someone to test

The bug should be fixed with v3.1.14