why organization licensing is listed as required along with per-user licensing for standard ediscovery

[Enter feedback here]
Licensing for eDiscovery (Standard) requires the appropriate organization subscription and per-user licensing.
In this article Get started with eDiscovery (Standard) cases in Microsoft Purview - Microsoft Purview (compliance) | Microsoft Docs it is also indicated that there needs to be two licenses (requires the appropriate organization subscription and per-user licensing. Can this be corrected as well? I understand that my company could potentially have only exo plan 2 to use edisocvery standard and no e3 is needed across the org – correct? If so, this article contains incorrect information (organization subscription and per-user licensing)
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1da8786f-5fa8-8787-045b-5ca68d9749b5
Version Independent ID: 9cf12db3-4a79-62d2-2ef3-bf565fd53a6d
Content: Get started with eDiscovery (Standard) cases in Microsoft Purview - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/get-started-core-ediscovery.md
Service: o365-seccomp
GitHub Login: @v-tophillips
Microsoft Alias: v-tophillips

@bozenektoja Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/8898
Once the author approves, the changes will be live.
Thanks
Sri

hello,
apologize, i dont see that as completed - organization licensing with minimnum e3 is still listed alongside per-user subscription:
[cid:4b02e855-c54b-4fae-ae12-d5b81787a4dd]
Best regards/Pozdrawiam,
Bozena Hutyra

Od: Yogesh Kumar @.>
Wysłane: wtorek, 14 czerwca 2022 10:28
Do: MicrosoftDocs/microsoft-365-docs @.>
DW: bozenektoja @.>; Mention @.>
Temat: Re: [MicrosoftDocs/microsoft-365-docs] why organization licensing is listed as required along with per-user licensing for standard ediscovery (Issue #8813)
Closed #8813https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8813 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/8813#event-6802172840, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ5463OR7KAZNWGKPI4CRT3VPA7DFANCNFSM5X63YN4Q.
You are receiving this because you were mentioned.Message ID: @.***>

yes thank you, but it still says that organizational licenisng with E3 is needed besider the er user licensing.
it says "Licensing for eDiscovery (Standard) requires the appropriate organization subscription and per-user licensing."
so the company would need not only e1 with eop plan 2 and spo plan 2 but also some e3 in the organization. it clearly says "organization subscription AND per-user licensing". will this be corrected as well, please?
Best regards/Pozdrawiam,
Bozena Hutyra

Od: Sriraman M S @.>
Wysłane: wtorek, 14 czerwca 2022 14:43
Do: MicrosoftDocs/microsoft-365-docs @.>
DW: bozenektoja @.>; Mention @.>
Temat: Re: [MicrosoftDocs/microsoft-365-docs] why organization licensing is listed as required along with per-user licensing for standard ediscovery (Issue #8813)
@bozenektojahttps://github.com/bozenektoja We have updated the per-user licensing via PR##8912https://github.com/MicrosoftDocs/microsoft-365-docs/pull/8912
Thanks
Sri
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/8813#issuecomment-1155136090, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ5463NSZH5MUIIECBAM6KDVPB5ATANCNFSM5X63YN4Q.
You are receiving this because you were mentioned.Message ID: @.***>

@bozenektoja The per-user licensing is not updated as the PR is not merged. But yes, the document will be corrected once the PR is merged.

PR is Pull request. I have made the changes via PR and once the author approves, the changes will be live.

awesome thank you for explanation!
Best regards/Pozdrawiam,
Bozena Hutyra

Od: Sriraman M S @.>
Wysłane: wtorek, 14 czerwca 2022 17:54
Do: MicrosoftDocs/microsoft-365-docs @.>
DW: bozenektoja @.>; Mention @.>
Temat: Re: [MicrosoftDocs/microsoft-365-docs] why organization licensing is listed as required along with per-user licensing for standard ediscovery (Issue #8813)
PR is Pull request. I have made the changes via PR and once the author approves, the changes will be live.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/8813#issuecomment-1155389737, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ5463KCDPF3KUH4LZZVMSDVPCTK5ANCNFSM5X63YN4Q.
You are receiving this because you were mentioned.Message ID: @.***>

@msbemba Thank you very much for the contribution and updating the documentation with PR. @bozenektoja Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Hello,
Can you please confirm one more thing: SharePoint Online Plan 2 under organizational subscription is not enough?
Organization subscription: To access eDiscovery (Standard) in the Microsoft Purview compliance portal and use the hold and export features, your organization must have an Exchange online Plan 2 or Microsoft 365 E3 or Office 365 E3 subscription or higher. Microsoft 365 Frontline organizations must have an F5 subscription.
Best regards/Pozdrawiam,
Bozena Hutyra

Od: Yogesh Kumar @.>
Wysłane: czwartek, 16 czerwca 2022 07:06
Do: MicrosoftDocs/microsoft-365-docs @.>
DW: bozenektoja @.>; Mention @.>
Temat: Re: [MicrosoftDocs/microsoft-365-docs] why organization licensing is listed as required along with per-user licensing for standard ediscovery (Issue #8813)
Closed #8813https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8813 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/8813#event-6818028106, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ5463O6MFPPWIRRYOAB2ULVPKY6NANCNFSM5X63YN4Q.
You are receiving this because you were mentioned.Message ID: @.***>


Can't seem to use invoke

So I extended the built in Mixpanel adapter (just to override 1 method, nothing big) but when I do invoke I get this error:
TypeError: t[e] is not a function
    at index.js:133
    at Array.forEach (<anonymous>)
    at o.invoke (index.js:133)
    at login.js:104

from the line of code:
          get(this, 'metrics').invoke('opt_out_tracking', 'ExpelMixpanel', {});

If I literally just get the service, raw, for ember inspector and do $E.invoke() I get the same error

Unminified error seems to be:
metrics.js:135 Uncaught TypeError: adapter[methodName] is not a function
    at selectedAdapterNames.map.forEach.adapter (metrics.js:135)
    at Array.forEach (<anonymous>)
    at Class.invoke (metrics.js:135)
    at <anonymous>:1:4

@rstudner I'm running into this exact thing. Would you mind sharing your solution?

@rstudner I run into the same error, what was the error?

@monsha we ran into this too. The issue for us was that we were missing the fact that the second argument to #invoke is optional.
invoke(method, [analyticsName], options)

thanks @livfwd, I tried it with/without second arg and nothing. The problem was that the adapter didn't have the function implemented

Yeah, the entire function was simply missing / should have been caught by tests.


Possible typo in documentation  init.py vs initi.py

See test "Update the Python code file init.py"
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d955d169-8fb8-c511-8911-3e49f95c5ce6
Version Independent ID: 8a3d927c-51ce-d7d4-e5d1-acd928826db2
Content: Python developer reference for Azure Functions
Content Source: articles/azure-functions/functions-reference-python.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@asset-web Thanks for your feedback. We will review and update as appropriate.


Let program admins specify "state" for applications

Let them specify whether or not an application is:

Not looked at
Ineligible
Eligible, not reviewed yet
In review
Approved
Rejected
Need to follow up

This will help the program admin track which ones they still need to review, and which ones they're done with.
This can feed into the filtering UI so that admins can, for instance, download a CSV containing just the applications they haven't looked at yet.
We can also surface this information to the applicant, so they can see the status of their application.

#1008 is a clone of this. Before I close that one, here's notes from it:

e.g. "I have reviewed this", "this one is incomplete". Let admins place these labels on people's applications directly within the program admin interface. Perhaps let admins store free-form notes about each applicant too, so they can add more information than just our labels. Would be ideal if applicants could see this status too (though probably not the free-form notes).
Then be able to sort/filter by people's stages in the application process.
This lets us build a lightweight CRM. We should make sure we don't go overboard and recreate Salesforce; just use this so simple information can be stored directly in CiviForm.

Relative to #975 and some already touched upon.

Found this old mock (not officially set in stone but just for reference). It also includes a "notes" column to each application that is invisible to the applicant but can be used for internal tracking (e.g. 'Sent to Steve for income verification').
This is also not important in the immediate term to Rochester, but P0 overall

I believe this is already done, right @shanemc-goog ?

Yep as part of Status Tracking!


Chip control dev branch - work in progress

Can I have a screenshot?

...pull the branch...it's in an early state though.

@ButchersBoy Nice +1

Awesome !!


Show mean throughput in command line report

With this commit Rally shows also the mean throughput in the command
line report. The mean is useful e.g. for calculating summary statistics
across several races or for conducting statistical significance tests.

since means will almost always be greater than median, I'd suggest either putting it above min (as its own "class") or between median and max. in fact I think I'd prefer the former (put it into its own)
Edit: actually I guess I don't know for sure which way the mean will go

Yes, the mean can either be smaller or larger than the median, depending on how the distribution is skewed. I am fine either way but I propose that we leave it as is, indicating at least that mean and median are in between min and max.
Also one integration test has failed. In the Elasticsearch log we see:
[2021-01-12T10:22:39,196][ERROR][o.e.b.Bootstrap          ] [rally-node-0] Exception
org.elasticsearch.http.BindHttpException: Failed to bind to [39200]
	at org.elasticsearch.http.netty4.Netty4HttpServerTransport.bindAddress(Netty4HttpServerTransport.java:487) ~[?:?]
	at org.elasticsearch.http.netty4.Netty4HttpServerTransport.createBoundHttpAddress(Netty4HttpServerTransport.java:384) ~[?:?]
	at org.elasticsearch.http.netty4.Netty4HttpServerTransport.doStart(Netty4HttpServerTransport.java:361) ~[?:?]
	at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:72) ~[elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.node.Node.start(Node.java:809) ~[elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:269) ~[elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:342) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) [elasticsearch-cli-6.8.0.jar:6.8.0]
	at org.elasticsearch.cli.Command.main(Command.java:90) [elasticsearch-cli-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:116) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93) [elasticsearch-6.8.0.jar:6.8.0]
Caused by: java.net.BindException: Address already in use

i.e. this is unrelated to this PR and considered transient. @elasticmachine test this please

since means will almost always be greater than median, I'd suggest either putting it above min (as its own "class") or between median and max. in fact I think I'd prefer the former (put it into its own)
Edit: actually I guess I don't know for sure which way the mean will go

Yes, the mean can either be smaller or larger than the median, depending on how the distribution is skewed. I am fine either way but I propose that we leave it as is, indicating at least that mean and median are in between min and max.
Also one integration test has failed. In the Elasticsearch log we see:
[2021-01-12T10:22:39,196][ERROR][o.e.b.Bootstrap          ] [rally-node-0] Exception
org.elasticsearch.http.BindHttpException: Failed to bind to [39200]
	at org.elasticsearch.http.netty4.Netty4HttpServerTransport.bindAddress(Netty4HttpServerTransport.java:487) ~[?:?]
	at org.elasticsearch.http.netty4.Netty4HttpServerTransport.createBoundHttpAddress(Netty4HttpServerTransport.java:384) ~[?:?]
	at org.elasticsearch.http.netty4.Netty4HttpServerTransport.doStart(Netty4HttpServerTransport.java:361) ~[?:?]
	at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:72) ~[elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.node.Node.start(Node.java:809) ~[elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:269) ~[elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:342) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) [elasticsearch-cli-6.8.0.jar:6.8.0]
	at org.elasticsearch.cli.Command.main(Command.java:90) [elasticsearch-cli-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:116) [elasticsearch-6.8.0.jar:6.8.0]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93) [elasticsearch-6.8.0.jar:6.8.0]
Caused by: java.net.BindException: Address already in use

i.e. this is unrelated to this PR and considered transient. @elasticmachine test this please


File picker uses wrong scaling factor on additional monitors

Issue Type: Bug
Get a laptop and hook two monitors to it. Make sure that laptop screen is the main one and it has 150% scaling. Open Visual Studio Code and drag it to one of the monitors. It correctly changes the scaling factor. Try to open a folder. The file picker (with VSC logo) will use the laptop's scaling factor and look huge. I cannot paste the screenshot in this tool.
VS Code version: Code 1.62.2 (3a6960b964327f0e3882ce18fcebd07ed191b316, 2021-11-11T20:56:38.428Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2208)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.85GB (17.09GB free)

Process Argv
--crash-reporter-id d62a64d4-5e65-4241-abcd-c883e5c89fbd

Screen Reader
no

VM
0%

My scaling factor is actually 125% but it is enough to look weird.

My bad, nothing to see here.


[flutter_tools] improve log output from bash entrypoint

Fixes https://github.com/flutter/flutter/issues/122047

closing per @christopherfujino


[+] Provide alternative LSH backends for dknn

I propose to replace falconn with faiss. It speeds up an index construction as well as a search.
There's no mentioning of falconn in Docker file nor in .sh script related.
I'm using the following to install faiss with gpu speed up on Ubuntu container with Conda.
conda install -c pytorch faiss-gpu

I've disabled random samples shuffling upon the index construction in faiss.
But multiple runs for me given different dknn_preds.
Is it supposed to be deterministic?
I can't check it with falconn since it's too slow.

Thank you for the PR. I'm all for extending the code base to include new knn libraries but in order to keep the archival status of the dknn example, could you add a flag that specifies which library to use for nearest neighbor search (e.g., falconn, fais, ...) and then keep the falconn code as the default library? I'll take a look at the code afterwards. Thanks!

Yeah, sure.

Here is the output of multiple runs of dknn_tutorial with
lsh_backend: FAISS
number_bits: 64
1.

(9250, 10)
0.9742702702702702
Saving reliability diagram at: /tmp/dknn_test.pdf
(9250,) (9250,)
[0.7891816920943134, 0.9473684210526315, 0.9841269841269841, 0.9921798631476051, 0.992822966507177, 0.9989868287740629, 1.0, 0.9987293519695044, 1.0, 1.0]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[721, 1007, 1071, 1023, 836, 987, 890, 787, 955, 973]
9250
(9250, 10)
0.24010810810810812
Saving reliability diagram at: /tmp/dknn_adv.pdf
(9250,) (9250,)
[0.19800498753117207, 0.24965197215777263, 0.2377963737796374, 0.2912621359223301, 0.2860824742268041, 0.41605839416058393, 0.43790849673202614, 0.39361702127659576, 0.36633663366336633, 0.08695652173913043]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[4010, 2155, 1434, 618, 388, 274, 153, 94, 101, 23]
9250

2.
(9250, 10)
0.9712432432432433
Saving reliability diagram at: /tmp/dknn_test.pdf
(9250,) (9250,)
[0.7699248120300752, 0.9310344827586207, 0.9861386138613861, 0.988056460369164, 0.9905123339658444, 0.99625, 0.9969666329625885, 1.0, 1.0, 1.0]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[665, 1044, 1010, 921, 1054, 800, 989, 814, 1059, 894]
9250
(9250, 10)
0.20724324324324325
Saving reliability diagram at: /tmp/dknn_adv.pdf
(9250,) (9250,)
[0.16778523489932887, 0.1879507848960543, 0.2251759186864738, 0.2509157509157509, 0.2660753880266075, 0.3191489361702128, 0.2916666666666667, 0.42105263157894735, 0.37583892617449666, 0.34782608695652173]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[3725, 2357, 1279, 546, 451, 282, 240, 152, 149, 69]
9250

3.
(9250, 10)
0.9704864864864865
Saving reliability diagram at: /tmp/dknn_test.pdf
(9250,) (9250,)
[0.7744565217391305, 0.9344422700587084, 0.9823651452282157, 0.9885974914481186, 0.9950207468879668, 0.9957310565635006, 0.9987864077669902, 1.0, 0.9978991596638656, 1.0]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[736, 1022, 964, 877, 1205, 937, 824, 925, 952, 808]
9250
(9250, 10)
0.22086486486486487
Saving reliability diagram at: /tmp/dknn_adv.pdf
(9250,) (9250,)
[0.1705937794533459, 0.20517316966242877, 0.24709042076991944, 0.3304042179261863, 0.2962962962962963, 0.3632286995515695, 0.3732394366197183, 0.48214285714285715, 0.6052631578947368, 0.6296296296296297]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[4244, 2281, 1117, 569, 459, 223, 142, 112, 76, 27]
9250

4.
(9250, 10)
0.9726486486486486
Saving reliability diagram at: /tmp/dknn_test.pdf
(9250,) (9250,)
[0.7360655737704918, 0.9472318339100346, 0.9815005138746146, 0.9922737306843267, 0.9954285714285714, 0.9988385598141696, 1.0, 0.9987966305655837, 1.0, 1.0]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[610, 1156, 973, 906, 875, 861, 1018, 831, 957, 1063]
9250
(9250, 10)
0.21275675675675676
Saving reliability diagram at: /tmp/dknn_adv.pdf
(9250,) (9250,)
[0.17803138373751784, 0.19968429360694553, 0.1963470319634703, 0.20314735336194564, 0.27111111111111114, 0.34576271186440677, 0.45535714285714285, 0.49137931034482757, 0.4842105263157895, 0.5]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[3505, 2534, 1314, 699, 450, 295, 224, 116, 95, 18]
9250

5.
(9250, 10)
0.9713513513513513
Saving reliability diagram at: /tmp/dknn_test.pdf
(9250,) (9250,)
[0.7933673469387755, 0.9353876739562624, 0.9821605550049554, 0.9936775553213909, 0.9954389965792474, 0.9903381642512077, 0.9973992197659298, 1.0, 1.0, 1.0]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[784, 1006, 1009, 949, 877, 828, 769, 1128, 948, 952]
9250
(9250, 10)
0.2427027027027027
Saving reliability diagram at: /tmp/dknn_adv.pdf
(9250,) (9250,)
[0.21751896256422804, 0.2397935241670577, 0.2147458840372226, 0.26194690265486725, 0.33424657534246577, 0.336, 0.4476744186046512, 0.4166666666666667, 0.4166666666666667, 0.2903225806451613]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[4087, 2131, 1397, 565, 365, 250, 172, 168, 84, 31]
9250

6.
(9250, 10)
0.9695135135135136
Saving reliability diagram at: /tmp/dknn_test.pdf
(9250,) (9250,)
[0.8133472367049009, 0.928150765606596, 0.9755813953488373, 0.9896421845574388, 0.995945945945946, 0.9971428571428571, 0.9947229551451188, 0.9991721854304636, 1.0, 1.0]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[959, 849, 860, 1062, 740, 700, 758, 1208, 1166, 948]
9250
(9250, 10)
0.25113513513513513
Saving reliability diagram at: /tmp/dknn_adv.pdf
(9250,) (9250,)
[0.20701592430186938, 0.23297297297297298, 0.2720465890183028, 0.3031161473087819, 0.3413333333333333, 0.3561643835616438, 0.35784313725490197, 0.5049019607843137, 0.49056603773584906, 0.39215686274509803]
[0.05, 0.15, 0.25, 0.35, 0.45, 0.55, 0.65, 0.75, 0.85, 0.95]
[4333, 1850, 1202, 706, 375, 219, 204, 204, 106, 51]
9250

Regarding the non-deterministic results on FAISS, I have never used the library so I can't really comment on  that

Regarding the non-deterministic results on FAISS, I have never used the library so I can't really comment on that

Could you please provide multiple runs output with falconn?
Just to compare.

The code I've been using is the one you are editing in this example

The code I've been using is the one you are editing in this example

How many cores are needed for falconn to perform reasonably well?
With 2x2.4 GHz it takes 20 minutes or more per run.

I think in couple hours I'll provide falconn runs as well here.

1.

1.
 Just wait for the travis script?

Yes I am just waiting on Travis, thanks a lot for the PR. The results are sufficiently consistent between FALCONN and FAISS for us to merge the PR. There is not much value in tuning the individual parameters of each approach given that optimal values of these parameters will depend on the model architecture and dataset too.

@npapernot Do you know any practical application of dknn for big enough models?

I have only applied to CNNs with <= 10 layers, but I don't think more layers should be a problem as long as the FALCONN/FAISS implementation can handle the nearest-neighbor search in each layer.


animationDelay taken away from RoughAnnotationConfigBase ?

I noticed that animationDelay has been taken away fron config object. Any particular reason for that ?  README might need an updated in that case.

The reason was that users can call show when they want on the annotation. Adding the artificial delay didn't seem essential to the core of the lib. If the caller wants to. delay the animation, they can call it after that interval.
For chaining animations, animationgroup already provides that.
Still a pre 1.0 release so hoping to hash out the lightest API
You're correct I may have missed updating readme.

Readme updated https://github.com/pshihn/rough-notation/commit/e1d7e1b930dde4fa26455918712a35d5daf901f6


SerializedConfigValue.writeExternal and readExternal are inconsistent

See https://github.com/typesafehub/config/issues/461 for details.

Thanks for your reviewing my PR!
Wrt your first question, I'm not quite sure I understand what type of unit test you have in mind. Could you please elaborate?
As for your second question, the answer is "No, I don't think so". In fact, skipField() is altogether redundant in SerializedConfigValue.readExternal(ObjectInput). If you look carefully at
SerializedConfigValue.writeExternal(ObjectOutput), you'll see that it only ever writes 2 fields: SerializedField.ROOT_VALUE and SerializedField.ROOT_WAS_CONFIG, as well as SerializedField.END_MARKER. It basically means that the corresponding SerializedConfigValue.readExternal(ObjectInput) will only ever have to read the two fields followed by the end marker. There is simply no way there will be any "unknown" fields in the input stream.
Finally, please note that only the top-level object's SerializedConfigValue.readExternal(ObjectInput)/writeExternal(ObjectOutput) are invoked by the serialization framework. Once inside, the rest of the Config hierarchy (de)serialization is entirely handled by SerializedConfigValue.readValue()/writeValue(), and readExternal()/writeExternal() are never called again. This is the reason why fieldIn() is only required in the top level readExternal().
I've updated the PR with a slightly simplified version of readExternal() that no longer calls skipField().
Please review. Thanks!

Hello! Is there any chance this PR will be reviewed and hopefully merged any time soon? This is about to become a showstopper for me.
Thanks!

Hi, I will do my best, not at a computer right this second and always swamped!
I would feel better about this if we had a test (see the current test suite for a lot of example tests covering this file already) which would break if someone regressed this again. Otherwise I would not be shocked to see it regress again ...

I definitely see your point, but implementing such test would require an external serializer library (in this case it would be Apache Ignite) as a dependency. I'm not sure if it's ok, but if you feel it's worth the trouble, then I'd gladly do it. Cheers!

No, let's not do anything over the top. I haven't read the docs about how to override the serializer but was hoping it could be done in toy form for the scope of a test or two.

@2m @patriknw or others, do you want to look this over? inclined to merge soon

@havocp Added a small unit test that demonstrates the fix. The test fails if run against the original code in com.typesafe.config.impl.SerializedConfigValue. Please let me know if you have any questions. Thanks!

Thanks for tracking down this issue and for the PR. Apologies for my slowness!


Update user-consent.md with with the information related to the CAMARA APIs access flows

What type of PR is this?
Add one of the following kinds:

documentation

What this PR does / why we need it:
This PR includes:

Document cleanup and general housekeeping.
Includes references to open discussion in the WG.
Included the information related to the CAMARA APIs access flows. Frontend flow (Auth code) and backend flow (CIBA).
Included draft technical ruleset for each flow.

Which issue(s) this PR fixes:

Fixes #46 so CIBA flow can be referenced from the the AuthN-AuthZ document.
Fixes #52 including technical ruleset draft for frontend and backend flows.
Fixes AP 20230712-02: MOM-2023-07-12.md && MOM-2023-07-26.md

Special notes for reviewers:

The document will be renamed to CAMARA-API-access-and-user-consent.md, but we should do this in another PR (or just before MERGE) to better track changes to the document.

Changelog input
N/A
Additional documentation
documentation/CAMARA-AuthN-AuthZ-Concept.md

@jpengar : Frontend, backend flow description looks fine for me.
Added a comment for ruleset https://github.com/camaraproject/IdentityAndConsentManagement/pull/54/files#r1302861238

@rartych Please could you give it a second review. Thanks!

Adding @sebdewet in the loop for Orange review.

@AxelNennker Thanks for your comment!
PKCE is already mentioned and documented in CAMARA-AuthN-AuthZ-Concept.md but I don't see it as something specific to the front-end flow included here.
https://github.com/camaraproject/IdentityAndConsentManagement/blob/9274170941557188f9fd23a3466e168e70a77e5b/documentation/CAMARA-AuthN-AuthZ-Concept.md?plain=1#L147

As agreed in yesterday's (24/08) follow-up call, the deadline for merging this PR will be 30/08. Reviewers and CAMARA participants are therefore requested to provide their comments (if any) before this date.

As agreed in 23/08 follow-up meeting this PR is MERGED as there are no further comments regarding the content of this PR and no further objections.
P.D: PKCE topic will be discussed separately if needed @AxelNennker

@jpengar I understood we have still today (Aug 30) to review this document.
Is it possible to re-open this PR?
@sebdewet plans to review it and from my perspective we are not comfortable in all diagram with the use of the purpose wording in the /authorize while we prefer to keep it simple with use of scope wording. I understood we were aligned on this.

@bigludo7 @sebdewet If the PR is MERGED, I don't think it can be reopened (a new PR is needed). Sorry about that. If your concern is about using the purpose wording in /authorise instead of the standard scope. You are right, and we are fine with changing it (it is just a legacy from the past and it only represents that purpose must be declared in the access). What we can do is create a new PR once we get agreement on issue #32. This new PR will correct the flow accordingly, and include the information about the agreed solution in the relevant doc sections. Is that OK with you guys?


Block login attempts to gchr.io

gchr.io appears to be someone typosquatting ghcr.io. We should block users from accidentally sending their credentials there.

Ready for QA on main. This is what I get when testing it:
❯ acorn login gchr.io
  ✗  ERROR:  blocking login attempt to gchr.io (did you mean to type ghcr.io?)


Added repo & homepage info to package.json

This fixes the absence of repo link in npm package's page.

Codecov Report

Merging #13 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #13   +/-   ##
=======================================
  Coverage   96.51%   96.51%
=======================================
  Files           4        4
  Lines         172      172
  Branches       37       37
=======================================
  Hits          166      166
  Misses          5        5
  Partials        1        1

Continue to review full report at Codecov.

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


Rename section to aspect and change where snapshots are stored

@AlexGilleran I'm PRing this so you can confirm the new snapshot location is ok on your system.


[POC] Slots using render props

Let's discuss the render props API for slots.
The implementation is quick and dirty and is there only to enable us to play with the new API.
Following up on the discussion we had on the Monday meeting, I prepared a version of the MenuButton with the added renderRoot prop. It's called with the props the root component should receive and the ownerState. Developers can override the component or modify the props in one place (so it's like slot and slotProps combined).
Codesandbox playground: https://codesandbox.io/s/heuristic-hodgkin-74mlzx?file=/Demo.tsx
🥇 The upsides:

Props are strongly typed and depend on the type of the slot component (unlike slotProps).
The need for polymorphism is essentially eliminated, leading to much more performant code (at design time).
It's possible to add arbitrary data attributes to elements.

👎 The downsides:

Custom event handlers or class names overwrite the built-in ones (whereas slotProps merge them). This could be solved by a function that merges both sets of props.
Simple cases (such as adding a class name) require more code.

Is the render prop option different from this?:
<MenuButton
  slots={{
    root: (props) => (
      <IconButton data-testid="hamburger-menu" {...props}>
        <MenuIcon />
      </IconButton>
    ),
  }}
/>

I remember we had a similar discussion when working on Fleunt UI (apparently 5 years ago 🤯). Some of the things discussed are very well summarized in https://github.com/microsoft/fluent-ui-react/pull/199#issuecomment-419433206. It is definitely not a silver bullet. We must be careful around performance with this one too or at least to check if it will regress compared to plain components.

Is the render prop option different from this

@DiegoAndai, yes, there is a subtle but very important difference. A render prop is a function that returns JSX (it's called by us), while slots.* are components (called by React). Defining a component during rendering can have pretty bad performance implications and cause unexpected behavior (such as state being lost between renders).

I remember we had a similar discussion when working on Fleunt UI (apparently 5 years ago 🤯). Some of the things discussed are very well summarized in https://github.com/microsoft/fluent-ui-react/pull/199#issuecomment-419433206. It is definitely not a silver bullet.

Thanks for referencing this. I'll analyze what you found back then.
I'm aware this solution has drawbacks. I've listed the ones I could think of. Let's focus on finding others and comparing them to the advantages this would give us.

We must be careful around performance with this one too or at least to check if it will regress compared to plain components.

Is there something in particular that you are concerned with? I don't think performance will be much different between these solutions. When using slots and slotProps, we read the slots, read slotProps, detect whether it's a function and if so, call it with the ownerState. In the case of render props, we'd always call them with ownerState. Since render props are functions, not components, no new instances will be created on each render.
But then, I may be missing something, so I'll profile both solutions.

One more thing, if this component is later exported from a UI library like a component, the merging of all props and event handlers would be nightmare

For creating reusable libraries with Base UI, we recommend using hooks. Even today it's hard to create components that can be customized further with Base UI's components (merging ownerStates of different shapes is one example of why it's hard).

It would be great if we can create a fully featured introduction demo and see how it would look like.

Do you mean a demo of the MenuButton integrated with a Dropdown and a Menu?

For creating reusable libraries with Base UI, we recommend using hooks. Even today it's hard to create components that can be customized further with Base UI's components (merging ownerStates of different shapes is one example of why it's hard).

I thought the point of the hooks is to have more freedom in how the DOM tree is rendered & structured. If we truly think that the unstyled components are not suitable for creating UI libraries, then what's the use-case for them? I mean even if I am not creating a UI library, but I need to have two buttons in my app, and I wrap the ButtonUnstyled once, for sure I would like to reuse this component in the other place - this doesn't mean that I shouldn't have access to slots & slotProps in this other instance. I don't think we should box ourselves like this honestly, otherwise, we may be wasting time with the components.

It would be great if we can create a fully featured introduction demo and see how it would look like.

Do you mean a demo of the MenuButton integrated with a Dropdown and a Menu?

It's connected to the previous point, maybe our components are not tested well enough for us to know if the API works. The hooks are used in both Joy UI and Material UI so we can  tell if they work or not, the demos are the only way how we can test the unstyled components. This is why I said, maybe we should have a fully featured Introduction demo - create a component that can be used in multiple places based on the unstyled component - this will show us if the API works.

Instead of supporting all the possible ways of achieving something, should we be more opinionated?

FWIW, this is a common complaint with regards to customization in Material UI. Because there are so many different ways to do it (and our docs don't explicitly teach one way as the best option), devs feel major "analysis paralysis" and have a hard time deciding which to choose. I could imagine similar situations here.

I don't think we should box ourselves like this honestly, otherwise, we may be wasting time with the components.

Components can be easily customized as long as you don't add anything to ownerState - then it becomes cumbersome. We can discuss use cases for both separately, not to divert from the original topic of this discussion.

This is why I said, maybe we should have a fully featured Introduction demo - create a component that can be used in multiple places based on the unstyled component - this will show us if the API works.

All right, I'll work on it.

Having the components, and the hooks, and slots, and renderProp we might be creating decision hell for our users.

@DiegoAndai, @samuelsycamore, I'm not considering adding render props to the existing features but replacing slots and slotProps with them.

@DiegoAndai, @samuelsycamore, I'm not considering adding render props to the existing features but replacing slots and slotProps with them.

That makes more sense. In that case, I agree with @DiegoAndai 's other point, that it kind of muddies the concept of slots. It's not necessarily a bad thing, but it would require a shift in how we present the mental model of component structure and customization. Maybe it's just a matter of naming, but if I'm understanding it correctly, it seems to add an extra layer of abstraction on top of our already abstracted concept of slots.

React Aria went the hook route and stuck with it, Radix went the component route and stuck with it.

@DiegoAndai React Aria is adding unstyled components, they are in alpha.

Two more things to be considered for the callback scenario:

Base UI's unstyled components are higher level components. This means that if we go with the render props paradigm, on some components we may have multiple render* props, which may make the usage of the component a bit awkward. I feel like the render* paradigm works much better with lower level components, where mostly the child can be a render callback, for e.g. for the input we would have:

<Input
  renderRoot={() => {}}
  renderInput={() => {}}
  renderTextarea={() => {}}
 />

Render callbacks makes the components pretty much not usable in RSC as the functions won't be serializable

I'm not considering adding render props to the existing features but replacing slots and slotProps with them.

The drawbacks I see:

Passing extra props to the inner slot would be a lot harder.
It's no longer easy to replace the inner slot's component. e.g. <Menu slotProps={{ list: { component: 'div' } }}>

I would stay with the current API (slot, slotProps) and live with the trade-off (maybe 10% of the use cases which is fine to me).
What we need is to document them and teach the community when to use those props.


New version: TrafficAssignment v0.6.4

Registering package: TrafficAssignment
Repository: https://github.com/chkwon/TrafficAssignment.jl
Created by: @chkwon
Version: v0.6.4
Commit: 40a56d4b41b04ea798b4ba8de90a906c3b85aece
Reviewed by: @chkwon
Reference: https://github.com/chkwon/TrafficAssignment.jl/commit/40a56d4b41b04ea798b4ba8de90a906c3b85aece#commitcomment-39395341

Please ignore this request.  Updated in #15262


NormalizeEmail returns invalid data

v = require 'validator'

v.isEmail<EMAIL_ADDRESS>true

v.normalizeEmail<EMAIL_ADDRESS><EMAIL_ADDRESS>

I don't think that's a valid Gmail address. Gmail strips the part after + when determining the destination mailbox, e.g. email to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>both get delivered to me at<EMAIL_ADDRESS>

@chriso yes that isn't a valid address. But the problem here is, normalizeEmail is not working as intended. It is removing the local part altogether.


Python Wrapper: Simple readline

Closes #7066

Would suggest taking a look at python's io.BufferedReader - it maintains the buffer for you as well as handles the scanning required for readline/readlines.
It could be made to natively wrap an ObjectReader by having it implement readinto.


Third slug is same as second

It seems the MySql LIKE operator won't properly handle input.
After some troubleshooting I encountered, that with the JSON operator -> it will select the value with "-marks surrounded.
So having the column slug with content {"en":"a-slug-1"} the line ->orWhere($attribute, 'LIKE', $slug.$separator.'%') won't match as mysql selects slug->en as "a-slug-1" and not as a-slug-1.
As I suppose this has been working some time (or with other Databases) I just added one additional line which resolves this issue but won't break anything for everyone not having this (strange) issue.

@tabacitu this one is ready and it would be nice if we could have it in the next update :)

Sure, thank you @OliverZiegler and @tswonke ! Merged, will be tagged in a few hours.
Cheers!


Server  crashes on world save

We had some server-crashes, it stopped since we disabled save_on_world_save.
Could u pls look into that?
Crash reports and additional information:
https://github.com/PurpurMC/Purpur/issues/1391
https://github.com/PaperMC/Paper/issues/9528

I think it's caused by the way Purpur offloads certain functionality on world save to different threads.

@WiIIiam278 We have verified the issue on both paper and Purpur

Fixed in #153


Browser error self-signed

After installation all of my browsers are in error because of self-signed certificate.

Please check #2


[Bug]: RBAC UI issues

Is there an existing issue for this?

[X] I have searched the existing issues

Description

The search component has a shadow.

Irrelevant tooltip observed for the Groups column in Users screen. Also this tooltip does not follow the design system

When we rename a new group and press Enter, the page refreshes but the name is not saved. It only save after we press Enter the second time.
https://www.loom.com/share/cbda20fcd75849eb841f32cba8eab70a

Dropdown for adding Users does not behave like it does everywhere else in the platform.
https://www.loom.com/share/39591cfd5bb043d798f36543a596920e

On hover cursor turns into a CTA even when the icon is not clickable.
https://www.loom.com/share/48d77545c90e4e338a654b7bf58951eb

Steps To Reproduce

Go to the Access Control page

Public Sample App
No response
Issue video log
No response
Version
Cloud

@shadabbuchh  For point 4, the dropdown showing 3 selected instead of tag names was part of the design. Plus it won't make sense for a user to scroll and read the content, instead, it's better we tell them how many options are selected and they can open the dropdown and check which ones are selected.
Will look into other things pointed out by your here.

Point 2 needs to be handled in design-system repo. Will do the needful.

@shadabbuchh For point 4, the positioning works fine on GSheets because the container is the full height of that page. While this doesn't work on the invite modal which cannot be of full height. This will require some help from the design-system team and this positioning of the dropdown on the invite modal is a known issue to the design-system team.
cc: @albinAppsmith

Verified the above issues in release. All seem to be working fine.
Will raise a separate issue for #4.

Closing this issue as only 1 issue is pending from the list this will be filed seperatly


Add JSDoc

I think it would be useful to add JSDoc to the project. It would be easier to contribute and you could generate documentation automatically. What do you think?

Was just about to raise an issue for this. Yes it would be great to add this to the project; I imagine more people would be willing to contribute to the repo if this were in place.


Audio issue - Amazon Prime and Spotify

Describe the bug or issue
Running the web apps seems to skip tracks or only play for a few seconds ....probably and audio issue or DRM?
Describe your setup

Pi-400
chromiumos_image_r86r2-rpi4b

To Reproduce
Open spotify or amazon music and it won't play after a few seccionds.

@timbo1975
if you are confirm with linux then you can try this:
https://github.com/FydeOS/chromium_os-raspberry_pi/issues/130

@timbo1975
if you are confirm with linux then you can try this:
https://github.com/FydeOS/chromium_os-raspberry_pi/issues/130

@timbo1975 : Taskmanager tells me it uses widevine.

@timbo1975 : Taskmanager tells me it uses widevine.


html/xml tags

Do you strip html tags from the documents before embedding them into vectors?
And if so do you support this stripping of xml tags also?

Hi @pedrocr83 we use html2text to parse the html into text before embedding -- I think the library works with XML tags as well!


Grabseqs error

Hi,
I met this problem when I used grabseqs.

Traceback (most recent call last):
File "/media/home/user05/anaconda3/envs/python36/bin/grabseqs", line 11, in
sys.exit(main())
File "/media/home/user05/anaconda3/envs/python36/lib/python3.6/site-packages/grabseqslib/init.py", line 58, in main
acclist, metadata_agg = get_sra_acc_metadata(sra_identifier, args.outdir, args.list, not args.SRR_parsing, metadata_agg)
File "/media/home/user05/anaconda3/envs/python36/lib/python3.6/site-packages/grabseqslib/sra.py", line 52, in get_sra_acc_metadata
run_col = lines[0].index("Run")
ValueError: 'Run' is not in list
Could you please tell me how to solve this problem? Thanks.

same

same problem than Nov 2022:
(grabseqs) ant@hillary:~/LemonSharkGSS$ grabseqs sra SRR23340818 -t 12
Traceback (most recent call last):
File "/home/ant/miniconda3/envs/grabseqs/bin/grabseqs", line 11, in
sys.exit(main())
File "/home/ant/miniconda3/envs/grabseqs/lib/python3.7/site-packages/grabseqslib/init.py", line 58, in main
metadata_agg = process_sra(args, zip_func)
File "/home/ant/miniconda3/envs/grabseqs/lib/python3.7/site-packages/grabseqslib/sra.py", line 31, in process_sra
metadata_agg)
File "/home/ant/miniconda3/envs/grabseqs/lib/python3.7/site-packages/grabseqslib/sra.py", line 97, in get_sra_acc_metadata
run_col = lines[0].index("Run")
ValueError: 'Run' is not in list
(grabseqs) ant@hillary:~/LemonSharkGSS$
At that time, I followed your (below) suggestion and it went back to work:
Try replacing /usr/local/lib/python3.6/site-packages/grabseqslib/sra.py line 94 with
metadata = requests.get("https://trace.ncbi.nlm.nih.gov/Traces/sra-db-be/sra-db-be.cgi?rettype=runinfo&term="+pacc)
Any new suggestion? Thank you!

It didn't work.

sra.txt
rename this txt with sra.py and copy it to /yourpathto/grabseqslib/. replacing the former one will solve the problem for now. It is caused by the replacement of trace.ncbi I suppose. If it doesn't work again, just check whether the path https://trace.ncbi.nlm.nih.gov/Traces/sra-db-be is still working and find a new one.

doesn't work again

metadata = requests.get("https://trace.ncbi.nlm.nih.gov/Traces/sra-db-be/runinfo?acc="+pacc)

seems work

Thank you chansigit, it is working again

if someone is facing this issue now, then try replacing
/usr/local/lib/python3.6/site-packages/grabseqslib/sra.py line 45 with
metadata = requests.get("https://trace.ncbi.nlm.nih.gov/Traces/sra-db-be/sra-db-be.cgi?rettype=runinfo&term="+pacc)


Is it possible for this local search plugin to implment the facetfilter settings of the algolia search plugin

Hi!
The local search plugin is very good enough for us to implement local searches!
However, I have tried to tweak the plugin options to achieve separation of the results from different versions but with no luck.
Is it possible for this local search plugin to implement such separation, or how?
The following is my setting right now:
  themes: [
    [ '@easyops-cn/docusaurus-search-local', {
      hashed: true,
      indexBlog: false,
      language: ['en', 'zh'],
      docsDir: ['docs', 'reference'],
      docsRouteBasePath: 'docs',
      highlightSearchTermsOnTargetPage: true,
      searchContextByPaths: ['/docs/tutorials', '/reference/api'],
      explicitSearchResultPath: true,
    }],

and no matter what, the search results contain items from both versions

Separation of the results from different versions is already supported.
Try our demo https://easyops-cn.github.io/docusaurus-search-local/ , switch between next and 1.0.0, and enter style in the search bar.
Though I noticed we have to refresh the page after switch versions to make it work, so try refresh to see if it works for you. This problem maybe introduced by Docusaurus v3, but not sure, will look into it later.

That works! Thanks very much.
Manually refreshing the page after version switch brings the search context back on track. Although trivial but still hope the implementation of an automatic restoration of the search context after version switches.

Hi any updates on this?

Separation of the results from different versions is already supported.
Try our demo https://easyops-cn.github.io/docusaurus-search-local/ , switch between next and 1.0.0, and enter style in the search bar.
Though I noticed we have to refresh the page after switch versions to make it work, so try refresh to see if it works for you. This problem maybe introduced by Docusaurus v3, but not sure, will look into it later.

HI, I encountered the same problem, are there any updates on this?


Bold text in markdown indistinguishable

If you zoom in really close, you can see a difference between bold and non-bold text, but it's not noticeable normally. Lora's bold and regular versions are quite different, so don't know what the issue is.

"time series" is bold

Ok guess what, I found a solution. My knowledge in this area is pretty basic, but the issue gets fixed if you add this to the CSS files. 👍
@font-face {
 font-family: 'Lora';
 font-weight: bold;
 font-style: normal;
 src: local('Lora'), url('fonts/Lora-Bold.ttf') format('truetype');
}


Fixing a Kotlin Multiplatform issue

The lwjglImplementation method accesses the wrong repository, for example, trying to access lwjgl 3_3_2 instead of 3.3.2 where the repository actually lives.

Thanks


[Feature Request] Basic open enclosure

Hello
Explicit title: even if we can use/mod the original xg mobile enclosure, it would be nice to have a basic open enclosure provided as a STL/step/other format so we could 3d print or order it from somewhere else by providing the enclosure file.
I don't think people would expect specific enclosure for their GPU, that's why I'm talking about an open one.
1/ Are you planning on providing one in here?
2/ Can someone else could create a PR with it? (not me, I'll take months if I do)

I have no plans to do anything beyond what you see here and any bugs that may come up.


Right Space Fixed + CSS relayout

Fix for [task] Fix Map CSS #20
First of all this pull request fixes the extra space to the right but by fixing that it created problems with having to set the height of the map to a semi-fixed height. (e.g. parks to 600px,map container 90vh )
So I have done a simple re-layout of turning the display into a grid with 2 rows. Top row is for the header, the bottom row is for the content/view, this makes it possible for everything to be responsive within the viewport.
Improvements

More responsive Design
Map fits within viewport
No extra white/scroll right and bottom
Parks Container scroll point and Map Container Bottom Point line up

Suggestions

Map has slight padding around it, this can be removed if requested

Pull request can be pulled back to the commit where only the right side space was fixed, if requested

Actually this Pull Request isint complete scroll on the park cards has to fixed sorry


Some UI docs

A bunch of things have changed so I will need to rebase your docs when done. Hope I finish my refactorings over the weekend and we can get Substance Beta 3 out at the beginning of next week.

Note that I did sync with master.
On Sat, Dec 12, 2015, 02:42 Michael Aufreiter<EMAIL_ADDRESS>wrote:

A bunch of things have changed so I will need to rebase your docs when
done. Hope I finish my refactorings over the weekend and we can get
Substance Beta 3 out at the beginning of next week.
—
Reply to this email directly or view it on GitHub
https://github.com/substance/substance/pull/323#issuecomment-164069266.

Talking about these changes here: https://github.com/substance/substance/pull/334

I'm not sure what could intersect here, so do what you want.
What I really did not like that part of commits came from master or other branches, so it's not really possible to work only with api-docs branch.

Hey I've synced latest stuff with master. Can you clean this up a bit.. like just squashing the commits? I will merge it into master then. Thanks a lot!

mmm... it's hard to rebase, I did merge in the middle of the process...

It's rebased now. Please review and push merge button :)

Oh oh.. broken tests. Don't merge!

Now looks good. Gosh.. rebasing... but more and more I'm understanding it. Needs practice. Please check and merge.

@michael what changed in commit history?

I left commits the same - just edited some using the rebase workflow. It's similar to resolving merge conflicts.

Should we sync api-docs again?

sync api docs?

yes, this branch or maybe it's better to create a new one...

ah for more docs... create new one yes.


Inconsistency between "GET /tasks" description and response definition

Description
There is a minor inconsistency in the definition of the GET /tasks endpoint: the responses section for a 200 response expects a tesListTasksResponse object, which is itself an array of tesTask objects. Now, tesTask objects require the property executors, an object of type tesExecutor. But the description of the view query parameter in the same endpoint definition states that for view type MINIMAL only the Task.id (should perhaps be tesTask.id) and Task.status (tesTask.status) are to be returned. This makes automatic schema-based validation of the response impossible for that endpoint.
Proposed solution
This is perhaps not quite easy to resolve, especially in Swagger 2.0, which does not allow defining different schemas for a response body. In OpenAPI 3.0, the anyOf and oneOf keywords can be used for that purpose (see here, here and here), although, unfortunately, not conditionally dependent of a request parameter (see here, bottom of page).
Perhaps the cleanest thing to do will be to define different schemas for POSTing and GETting tasks, then set different requirements for the latter (e.g., tesTaskResponse.id and tesTaskResponse.state, but not tesTaskResponse.executors). This would also allow the POST-specific schema to get rid of the id property, which is anyway pointless to include, as it is, according to its description, expected to be generated by the implementation. Setting id as required in the response will allow a client or automatic validation framework in the service to ensure that the service, in fact, did generate (and store!) a task ID and avoid potentially empty entries in a MINIMAL representation of the listed tasks (and elsewhere). Finally, once switching to OpenAPI 3.0, the tesTaskResponse schema could be decomposed into separate subschemas for the different views.
Other possible solutions:

Make executors an optional parameter in tes.Task
Make executors part of the MINIMAL response

I'm of course aware that all of the proposed solutions constitute breaking changes that would require any existing implementations to update their code, so I am not hoping for an immediate fix.

Perhaps related: https://github.com/ga4gh/workflow-execution-service-schemas/pull/172


keep original layers when exiting edition

iD could memorize the layers you have before editing.
For example, if you have the transport layer and the note layer when clicking edition, this will be lost when you're done, as you will have default layer (mapnik) and note layers masked.

Thank you.


[WIP] U2 commands for the CLI

Still a work in progress.
To Do:

Unit tests:

Testing command line arguments
Testing file parsing
Testing JSON parsing
Testing HTTP calls

Better / more usable output
Different output for non Enterprise clusters.

Done:

Initial implementation of the CLI commands
Modification of http.py to talk to Cosmos.
Tested with Cosmos on DC/OS cluster

@nickbp and @benclarkwood: pinging you here for early review. Still a WIP.


Early encrypted download heuristic (single share)

IF the following conditions are met :

mobile X has uploaded a single encrypted resource R, and hasn't scanned QR yet,
a client Y is currently open and listening to a channel C,
we think there is high probability that X will scan Y  (e.g. because it has already scanned Y 2mn ago)

THEN Y may start downloading the encrypted resource R.
This will speed up the subsequent "download" step when X does scan Y, typically shaving 300ms for a small (resized) photo.
This is a backend & client concern, the mobile apps (Android and iOS) probably don't need to care at all about it.

This optimization may be implemented ONLY for encrypted resources. The client must not have the decryption key until it has been properly provided, after X has scanned Y.

See also #60 and #94

For a multiple share action, see #515


Redo Login Page

Stack the fields.
Make the primary action to login.
The register should be a secondary action.
You buttons are aligned with fields that make them feel associated. They are also all visually the same weight.
You probably can copy the hierarchy of literally any login screen.
https://www.thumbtack.com/register

Fixed with #488


Translation - Turkish

This issue was created to track progress and discussions for the Turkish translation.

Awesome! Very excited for this!

@jimbobbennett should we rename file references as per the translations guideline.
For example in the README.md there is a reference to TRANSLATIONS.md file, should we change the reference file name to TRANSLATIONS.tr.md or keep it as is.

tr is the iso 2 letter code for Turkish

If there is a translated version, then yup, we should link to it - all the translated files should link to translated files where available.

Greetings! Is there a team ready, working on the Turkish translation? I would love to join and work together. Could you please walk me through the process?

Hi @buseorak,
Currently I'm the only one woking on the Turkish translation. I'll get in touch with you as soon as possible and see if we can form a team.

I'm creating Turkish version of README.md

See https://github.com/microsoft/IoT-For-Beginners/issues/230

I'm creating Turkish version of README.md

Hi, I've already translated README and other files in the root folder. Lesson-1 readme also translated and other files in lesson 1 are in progress. I think we should get in touch and coordinate our efforts.

I'm creating Turkish version of README.md

Hi, I've already translated README and other files in the root folder. Lesson-1 readme also translated and other files in lesson 1 are in progress. I think we should get in touch and coordinate our efforts.

I'm creating Turkish version of README.md

Hi, I've already translated README and other files in the root folder. Lesson-1 readme also translated and other files in lesson 1 are in progress. I think we should get in touch and coordinate our efforts.

What about accelerating the task by using translator which mentioned in #230

Hi, if it is still open, I would like to contribute

I saw a lot of weird sentence in Turkish translation. It seems it has been translated by automatic tool. I would like to edit these sentences

@smalcakmak would love your contributions! Please fork and raise a PR with improvements to the existing translations and any other translations you have time to work on.

@smalcakmak . I am the author of the Turkish translations. Machine translation is not used. Weird sentences are a drawback of that language of the source and the translated language are from different language families. Sentences are seem to be weird because I conserved the original structure. Various grammar structures of English enable us to create complex sentences. However, when we try to translate them into Turkish, nested linkers and relative clauses seem to weird. One of the solution of this problem is splitting into each clause and converting them into different sentences. However, resultant text is inherently different from the source. If you can provide another solution or mitigation of drawbacks of the sentence splitting method, those effects will no longer present.

However, when we try to translate them into Turkish, nested linkers and relative clauses seem to weird.

Fakat, onları Türkçeye çevirmeye çalışırsak, iç içe geçmiş bağlaçlar ve cümlecikler garip görünür.


Incidence Angle Modifier zero instead of np.nan (#338)

This PR changes the three IAM-models to return 0 instead of np.nan for aoi >= 90 (ashraeiam, physicaliam) and <0 (sapm_aoi_loss).
I also updated the tests to account for the changes. The test for physicaliam now shows, that angles of -90 and 90 return 0, whereas an angle of 0 returns 1, in accordance to the model description in De Soto et al..
Comments are welcome!

Could we have the identical code in each of the three functions to do the same thing?  That is, to deal with the negative values and the larger than 90 angles?  I don't know whether np.maximum, np.where or np.clip is better, but I would lean toward clip.
The SAPM model doesn't like negative angles, the others are fine because of the cosine.  That should be handled consistently as well.

@adriesse brings up a separate but closely related point regarding the meaning of negative values of aoi in pvlib. I tend to agree that the aoi loss functions should all start with something like aoi = np.abs(aoi), but that's open for discussion. I thought that we had previously discussed this elsewhere, but I can't find the discussion. If we're going to change it, now is the time.

If there are negative values for AOI, that indicates a problem elsewhere.  I’m not in favor of using abs(aoi) to address it.
From: Will Holmgren<EMAIL_ADDRESS>Sent: Wednesday, June 14, 2017 9:30 AM
To: pvlib/pvlib-python<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [EXTERNAL] Re: [pvlib/pvlib-python] Modelchain zero instead of npnan (#338) (#339)
@adriessehttps://github.com/adriesse brings up a separate but closely related point regarding the meaning of negative values of aoi in pvlib. I tend to agree that the aoi loss functions should all start with something like aoi = np.abs(aoi), but that's open for discussion. I thought that we had previously discussed this elsewhere, but I can't find the discussion. If we're going to change it, now is the time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/pvlib/pvlib-python/pull/339#issuecomment-308468474, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFJNL29f2zq0pqCBj7rcY8UTYqkKP4-Zks5sD_yFgaJpZM4N5lZB.

I vote for IAM=0 where AOI>=90, which is consistent with its definition and its use in the modeling process.
Where AOI=0 (or very close to 0) in the physical IAM model the formula needs to switch to the limit expression in my earlier comment. That switch should be the use of zeroang.
Sent from my iPhone
On Jun 30, 2017, at 3:20 PM, Anton Driesse <notifications<EMAIL_ADDRESS>wrote:
@adriesse commented on this pull request.

In pvlib/pvsystem.pyhttps://github.com/pvlib/pvlib-python/pull/339#discussion_r125122764:

@@ -811,6 +812,10 @@ def physicaliam(aoi, n=1.526, K=4., L=0.002):
spa
ashraeiam
'''

zeroang = 1e-06

aoi = np.where(aoi == 0, zeroang, aoi)

I am surprised that the model would not work for an angle of exactly zero degrees. Could this have something to do with the equation discrepancy mentioned in the comments further above?

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/pvlib/pvlib-python/pull/339#discussion_r125122764, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFJNLz8zdW2NpTqkrWLEcSArCsXj8LFmks5sJVh5gaJpZM4N5lZB.

I would also prefer IAM to return zero for angles outside -90/90 degrees.

Another observation: contrary to the statement in ref [1] the default value of 2 mm for the glass thickness is definitely at the thin extreme.  The value I currently see most often is 3.2 mm. Previously I believe 4 mm was more common.

I agree with the default value, but I could not find any sources on it. Do you think, we should change the default nevertheless?

The source for the 2mm default has no sources either...

If it helps, the model output is essentially insensitive to the thickness parameter.  You can double from 0.002 to 0.004 and the IAM changes very slightly.
For myself, I'd prefer the default to remain the value in the reference paper, simply for traceability back to literature.  I do see merit in changing to 3.2mm, though.

I suggest keeping the default set to 2 mm. I'll merge tomorrow unless there are objections.


Feature: Assets/Component Library

A good feature might be to have a component library to choose from, not just shapes. While having default components could be nice, I'm specifically thinking of my own components that I could reuse.
For example, I could have buttons, cards, image containers, etc that match the actual components I develop with. When I start a fresh Excalidraw session, I could immediately start using these to build my interface.
As far as how these are stored, the creators would have more insight, but here's my thoughts:

Update the import tool to specify you are importing components (which accepts multiple files) - this way the existing canvas is not overridden; this would also mean that no persistent storage method is needed; to make updates to components, it has to be edited individually and then saved again; potentially a component could be updated in existing canvases if the same component is re-imported (based on name/id)
Allow for categories (perhaps a part of the component metadata?) so that a popover drawer is easily usable
Component instances could be individually modified as needed
If a new component is added to a canvas, the easiest way to add it to existing components may be to select it with mouse and then export it (this is also the reason for using multiple files instead of one file to house all components)

Thanks for such a fantastic tool!

This was discussed a few times, but it seems no tracking issue has been yet created. :+1:

Maybe some sort of plugin directory where people could add some info

Author
Component name
Bunch of links to Excalidraw scenes

In Excalidraw app, we should be able to import to the existing scene other scenes via an Excalidraw link :)
Somehow integrate a plugin search and adding stars to the ones that we use the most or something among those lines. All data stored locally.. assuming that we don't want to build a backend for it just yet.

@lipis While that sounds great and you would know more than me, would it make more sense to start with local components? Then build on top of that after for a community "store"?
I would not likely go for many components from others because my team has specific design requirements for our sites.

It would be nice to have a preset of icons to use on our diagrams. Some examples could be:

a user icon
a data store icon
a server icon
a cog icon
etc

Next step could be to have icons of existing services, like AWS/GCP icons to use while drawing such architectures.
Now for the first set of icons, in order to make them feel more hand-drawn we could do some of our own (using rough.js) and have them as presets. For the second set of existing services could be trickier but something for the future maybe.
If we do predefine the first of set of icons on our own, we could even have them respect current font, so a user icon could be drawn with the current scene font style.
What do you think?
Example:

I have a working prototype of this locally, but I'm not happy about the UX I came up with.
Here's a sketch of how it currently works. Definitely looking for feedback on how it could be better.
https://excalidraw.com/#json=4859963037974528,ZVR_UO8h1E-fRBM2wGX19g

I think the popup menu should open to the right, similar to our shape-properties menu that opens to the left. This way, you can keep it open while you arrange/modify the components you drop on the canvas.
For the same reason, it might also be a good idea not to make the asset into another tool, so that you can keep the menu open for a longer period of time (that is, if your prototype currently works in a way so it closes when you change tools).

A easier way to handle component imports would be amazing.
I see this feature has two aspects which would make it useful:

Allow the community to create and share polished templates (probably there would be a page or multiple with excalidraw components very soon) e.g. there is https://tailwindcomponents.com/ and https://www.tailwindtoolbox.com/ for community made resources for tailwindcss.

Miro has launched Miroverse a while ago: https://miro.com/miroverse/ and it is incredible useful to be able to "import" something over and over again.

Have my own coponents.

Also interesting is how draw.io (now diagram.net) handles components. You can create a component from any group of elements (very similar to figma) and store them as a component to reuse it later. You can then load multiple component libraries (default or own ones).
https://www.diagrams.net/blog/custom-libraries

For @pA1nD and someone interested, I made an experimental external tool for this purpose in mind (but not yet really usable for this purpose).
Repo: https://github.com/dai-shi/excalidraw-gallery
Tool: https://dai-shi.github.io/excalidraw-gallery/
How to use: https://twitter.com/dai_shi/status/1266309261316943873

A related feature would be to have a templates gallery so you can start drawing with a template instead of starting from scratch.
Related to: #1863

Apart from how we would share the templates, how would it be different from loading a file (or a link)?
Ex: https://excalidraw.com/#json=5079026368512000,ZEdA1CP3wBBhG-MT0NgstQ Is this a template you imagine?

Yes something like that and we have a gallery full of templates similar to those, now I think this might overlap with components gallery...

Closing as implemented. For follow ups, see https://github.com/excalidraw/excalidraw/issues/1904


Authentication error

seems function validateaddress is still not working properly to authenticate users
zen address: zniRkSMLUggnBDqe9DRYMym5rKSv7EntDx3.RED is authenticating
altough zniRkSMLUggnBDqe9DRYMym5rKSv7EntDx3 isnt, so it has to do with workers names
This must be resolved, because it wil lcause payment errors!!

testing a fix in testnet now..

see PR 178, need to be checked by other people before it gets merged!!

Bug is NOT fixed, i now how people with short adddresses in the payment link, like: 1080ti

fixed by hellcatz commit


Custom interface extending TaskProvider<T> fails to be converted to a task in dependsOn

I have a custom TaskProvider that is enriched by some metadata:
class SomeMetadataTaskProvider<T : Task>(taskProvider: TaskProvider<T>, val someMetadata: String) : TaskProvider<T> by taskProvider

Gradle fails to understand it should be a valid candidate for dependsOn as it is a TaskProvider.
Expected Behavior
class SomeMetadataTaskProvider<T : Task>(taskProvider: TaskProvider<T>, val someMetadata: String) : TaskProvider<T> by taskProvider

val t = tasks.register("task1")
val metadataT = SomeMetadataTaskProvider(t, "some metadata")

val t2 = tasks.register("task2") {
    dependsOn(metadataT) // expected to work seemlessly
}

Current Behavior
Fails with:
Could not determine the dependencies of task ':task2'.
> Cannot convert Build_gradle$SomeMetadataTaskProvider@15b07421 to a task.
  The following types/formats are supported:
    - A String or CharSequence task name or path
    - A Task instance
    - A TaskReference instance
    - A Buildable instance
    - A TaskDependency instance
    - A Provider that represents a task output
    - A Provider instance that returns any of these types
    - A Closure instance that returns any of these types
    - A Callable instance that returns any of these types
    - An Iterable, Collection, Map or array instance that contains any of these types

Context
So far, we are working around the issue by referring it by name dependsOn(metadataT.name).
Steps to Reproduce
# build.gradle.kts
class SomeMetadataTaskProvider<T : Task>(taskProvider: TaskProvider<T>, val someMetadata: String) : TaskProvider<T> by taskProvider

val t = tasks.register("task1")
val metadataT = SomeMetadataTaskProvider(t, "some metadata")

val t2 = tasks.register("task2") {
    dependsOn(metadataT) // expected to work seemlessly
}

and run ./gradlew task2.

We don't support custom implementations of Provider-types. Most Gradle types are not intended to be implemented in plugins or build scripts.
Your SomeMetadataTaskProvider could implement Callable and return the underlying TaskProvider, but there might be other ways of accomplishing what you're trying to do.


Set block-size for a file before creation

I would like to create an HDFS file with custom "dfs.blocksize". Is there any way to override the default block-size for a file before it is written? Thank you very much in advance.
My first try is something like this:
private final OutputStream getHdfsOutputStream(final java.nio.Path hdfsPath, final Long blockSize) {
    if ("hdfs".equals(outputPath.toUri().getScheme()) {
        hdfsPath.getFileSystem().provider().setAttribute(hdfsPath, "hadoop:blockSize",  blockSize);
    }
    return Files.newOutputStream(hdfsPath);
}

But it's not working because the setAttribute implementation only allows to set lastModifiedTime, lastAccessTime or creationTime. I need to create in a Java application different files with different block-sizes, but without touching the configuration file or modifying the Hadoop cluster. At the same time, I have to deal with non-Hadoop paths, so that's why I'm checking for hdfs URIs.
I would appreciate if someone could help me :)

@magicDGS the concept of attribute in this Java API is to define existing files. For example the attribute haddop:blockSize tell you the configuration about an existing file (in this implementation).
I don't know if it's possible to change bloc size of an existing file in current version of HDFS (2.x).
To do what you want to do (specify dfs.block.size BEFORE creating the files) you have 2 solutions:

change dfs.block.size value of the file site-hdfs.xml loaded in you application
change this implementation to implement some parameter mechanism

Something that will let us customize the configuration of the provider.

Changing the site-hdfs.xml is not an option for my use case, because my block-size is going to change for every file, so it is not using the default. I also do not think that changing the provider configuration should be changed, because I want to modify the block-size in a per-Path basis.
Maybe adding a new class with HDFS-specific OpenOption to jsr203-hadoop and consider that in the HadoopFileSystem class may be useful. Let me know if this option works for you and I can submit a patch. Thank you in advance!

@magicDGS hello, I'm restarting the maintenance on this package. any patch is welcome.


best isrc result match url

Requested Feature
Can you please add a feature to get only best isrc result match url without dowloading song with yt-dlp
Possible implementation
No response

that's already possible check spotdl url you can combine that with --search-query {isrc}


User Login

[ ] Add Devise Development Mode
[ ] Email/Password support
[ ] OAuth for Facebook, Google, LinkedIn
[ ] Obtain auth key from each service and implement
[ ] Signup
[ ] Login


added google sign in

Feature https://github.com/sitamadex11/CovidHelp/issues/19

Please give me some time. I will check it soon.


TRƯỜNG ĐẠI HỌC SƯ PHẠM THỂ DỤC THỂ THAO HÀ NỘI

Hanoi University Of Physical Education and Sports

Hello @lasdc23,
Thanks for your pull request. Could you please provide us with a URL of a page on the official website where the school offers an IT-related long-term (>1 year) course?
Thanks!

@lasdc23 You might miss the comment above. Please reply.

@lasdc23 You might miss my previous comment. Please react.

@lasdc23 I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Fix creation of virtualenv using mkvirtualenv

See issue reported in #630
I have tested that you can move around virtualenvs with workon <virtualenv> and that you can make develop and make doc without any errors.
It was almost fixed in #632 but I hadn't created and linked to the .virtualenv directory which broke make doc.  @waveform80 could you please check this PR as @bennuttall is concerned about adding the lines to .bashrc (see https://github.com/RPi-Distro/python-gpiozero/pull/632#issuecomment-376183461).

Also removed > from apt install command to make cutting and pasting easier.

Codecov Report

Merging #636 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #636   +/-   ##
=======================================
  Coverage   85.58%   85.58%
=======================================
  Files          36       36
  Lines        7258     7258
=======================================
  Hits         6212     6212
  Misses       1046     1046

Continue to review full report at Codecov.

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

Ah, that makes sense. Would hash -r fix it like with the pip upgrade thing?

Dave says no. I'm closing this PR as it's not the right solution but let's address in the original issue by correcting the docs :+1:
See #630


Add files via upload

Please excuse me if this was not done correctly, this is my first pull request.
Related to issue #18
Seems to fix the issues with the Videos and Files not starting which hangs the program. It also seems to fix the timeout issues with courses failing to complete due to timeouts. The first issue is a workaround for the download library not recognizing that the API did not start and the other is just changing the timeout for retrying the download. Have not had a failure since I made these changes. There are probably better ways to do this but I am just learning JS and electron.
You can also get rid of the console.log() if you do not want them.
Thanks for contributing!
Please be sure you are following the guidelines at
https://github.com/FaisalUmair/udemy-downloader-gui/blob/master/CONTRIBUTING.md

Hi, Thank you so much for the contribution.
I see that you have updated the set retry timeout so that the downloader gets some more time to resume the download in case of network failure.
But whats up with decreasing the number of threads? Have you experienced any issues like Udemy dropping the requesting due to multiple threads? And for the other changes you made, can you please share an example which can reproduce the issue that you fixed.
Thanks :)

I wrote a longer response but the reply address was not the same so Git tossed it.
First preference this with I am just learning Javascript and App Development, the last real code work I did was in 8080 assembler to remove floppy based copy protections in the 80's.
The First issue I tried to address were where the Udemy API did not start the download or did not respond to the download request. The status returned was 0 and the error returned by the library did not return until after the timeout which caused a failed download and everything stopped. Re-issuing the dl.start() after 15 seconds is probably overkill since in all the courses that I watched the console either started in the first 3 seconds or never started. Probably the less hacker method would be to wait for the error and restart the download but this was quicker and worked every time.
Another issue was the timeout interval where the download would start and then just pause, timeout and fail. Increasing the timeout and the retry interval took care of this. The lib would return an error ( self.callback is not a function ) There is a pull request to fix this but the library has not been touched in 3 years. Just ignoring it an retrying worked.
There is another issue I did not address. In that case the program hangs at gathering course info and requires restarting the program. It only happens in courses where  the data from udemy has "is_practice_test_course: true" in the course data. I would probably suggest just disabling downloads on these courses since what you may get from them might not be usable anyway.
Other than the one practice exam course the 120 other courses downloaded without a hitch after these changes, the definitely could be tuned a bit..
Ron

Hi Ron, Thank you so much for your great work. Since you have already tested it and you believe it improves the download functionality by a lot. I guess it doesn't need a second thought, I will soon merge this. I am currently working on a new update. I will make sure the changes you made are available in next release.
Thanks


Provide Vault content to Joanna

We need to make sure Joanna has access to the content being created for MediaVault in #321.

Sent Joanna a link to the doc.


Components Library

Create a Bee React Components library to easily integrate the chat in third party dashboards and tools
Description
Quite often within FlowPilot (cc @mmurad2 ) we were asked for the ability to embed the chat in third party applications, referencing the "agent" configured beforehand
I think having this ability will make it much easier to distribute research technology though bee to final users, instead of creating custom UIs each time or iframes
Proposal
It would be awesome to be able to do something like
import { BeeChat } from "bee-agent-framework/react"

function App(){
  return <BeeChat agent="agent_id" allowFilesUpload  />
}

e.g. random dashboard with component integrated

Hi @tonxxd thanks for the proposal! This has been something we have been thinking about but unfortunately we do not have bandwidth to look into for the next couple of sprints. We're considering some alternatives between creating our own components vs adopted existing ones. I will close for now and re-open once bandwidth permits!
cc: @geneknit


autoFixOnSave does not work

Moved from the TSLint extension marked deprecated to this extension and the autoFixOnSave is not supported or does not work. If it is supported how do I enable it?

See instructions and documentation here: https://github.com/Microsoft/vscode-typescript-tslint-plugin#auto-fix-and-auto-fix-on-save

Thanks! I looked at 3 different posts about the fix on save and this link was not given in any of the responses that I saw.


Update FURY.legacy token

The cw20 version of the FURY token has been labelled as FURY.legacy as there now a new Native version of the FURY token on Furya chain.

This is a generated file. Please update the Chain Registry instead and then it will be reflected here. https://github.com/cosmos/chain-registry/blob/e41431c5974bec44c46d70de972a110f3c241d96/juno/assetlist.json#L656


Possible UX optimisations

Consider me a beginner but you are right, thanks ! I found gcsa incredibly easy to use, it is well documented and the example you gave is very helpful. These are the obstacles I faced:

I had to work my way around authenticating multiple Google Calendars, it turns out that a tab opens in the browser if you create a new token, so maybe an example that shows authentication of multiple Google Calendars would be helpful
I had to use dir to figure out the methods and attributes of the Event object, I found them later on "Read the docs"
I had to calculate "Duration", having a duration attribute could be helpful

I hope this helps, great job on gcsa !
Originally posted by @msulaim in https://github.com/msulaim/API-and-REST/issues/3#issuecomment-806330467

I'm not sure having a duration attribute on the event would make sense, it would allow one to modify the duration without modifying the start and end attributes of an event.

@joshsny Not sure if I want to have it yet. But it could be that you need to specify any two (and only two) of start, end, and duration from which you can calculate the start and end.


[AMBARI-23108] Upgrading commons-collections dependency to 3.2.2 due to security concerns

What changes were proposed in this pull request?
Per CVE-2015-6420

Serialized-object interfaces in certain Cisco Collaboration and Social Media; Endpoint Clients and Client Software; Network Application, Service, and Acceleration; Network and Content Security Devices; Network Management and Provisioning; Routing and Switching - Enterprise and Service Provider; Unified Computing; Voice and Unified Communications Devices; Video, Streaming, TelePresence, and Transcoding Devices; Wireless; and Cisco Hosted Services products allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections (ACC) library.

'Vulnerable software and versions' contains cpe:2.3:a:apache:commons_collections:*:*:*:*:*:*:*:*    versions up to (including) 3.2.1

Per CVE-2017-15708

In Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version.

So that we need to upgrade commons-collections to at least 3.2.2; at the time of this issue is being fixed there are more recent versions in org.apache.commons:commons-collection4 (v4.1) but it would require code modification due to package name changes
How was this patch tested?
After updating the affected pom.xml files I've done the following:
1.) Checking Maven's dependency resolution:
ambari-funtest smolnar$ mvn dependency:tree -Dverbose=true -Dincludes=commons-collections

[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Ambari Functional Tests <IP_ADDRESS>.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ ambari-funtest ---
[INFO] org.apache.ambari:ambari-funtest:jar:<IP_ADDRESS>.0
[INFO] \- org.apache.ambari:ambari-server:jar:<IP_ADDRESS>.0:compile
[INFO]    \- commons-collections:commons-collections:jar:3.2.2:compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.090 s
[INFO] Finished at: 2018-02-28T16:28:41+01:00
[INFO] Final Memory: 41M/1007M
[INFO] ------------------------------------------------------------------------

2.) I executed mvn clean install ambari-funtest:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.832 s
[INFO] Finished at: 2018-02-28T16:29:51+01:00
[INFO] Final Memory: 46M/511M
[INFO] ------------------------------------------------------------------------

As far as I know this project is out of use currently.

@rlevas @adoroszlai @zeroflag @dlysnichenko Please review this PR. Thanks!

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/869/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/870/
Test PASSed.


[languages] Understanding and implementing cookies in JSP

Proposed title of the article
[languages] Understanding and implementing cookies in JSP
Proposed article introduction
Cookies, which are little text files kept on the client computer, are used to monitor a variety of actions such as login credentials, file transfers, and other similar activities. Cookies may also be seen in debug mode by selecting "Application ->Storage ->Cookies" in web browsers and web-based apps, among other options. In web browsers and web applications, we can see whatever is in the cookies column, and we can delete it.
When it comes to cookies, we deal with the topic of cookie management in the JSP programming language. A number of cookie handling solutions are provided as presets in JSP, which makes use of HTTP cookies in a transparent manner to support cookies and offers various other features. Interactions between clients and servers, such as those involving requests, make significant use of request and response protocols to facilitate communication. The array of cookies associated with the cookie instance was returned by the get cookies() function. In this tutorial, we will understand the cookies concept in JSP in detail.
Key takeaways
The article will cover

An introduction to cookies, types, and how they work
How to create cookies in JSP/ Send cookies to the client
JSP Cookies API
Servlet Cookies Methods
How to handle cookies in JSP (reading and deleting cookies)
Implementing cookies in JSP

Article quality
This article will cover as much to help the reader not only understand the concept of cookies in JSP and its relevance but also how we can implement cookies in JSP.
References
N/A

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentations.
We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic, it has to serve value to the larger developer community at large.
An option and a great way to write this as an in-depth article and make it more add value to the greater developer community at large would be to walk the reader through the USE of methods and functions by building a unique, different, useful project.

We would love to learn your thought process behind the solution you arrived at using these concepts and topics.

That way a developer could see them in action.
As mentioned above - we believe this topic is widely covered on other blog sites.
The best way for students to build a great portfolio is by building what does not exist and what can provide the most value.


[wip] Added qps and burst to server's client

Signed-off-by: Darko Radisic<EMAIL_ADDRESS>Fixes https://github.com/heptio/ark/issues/109

Hi @ffd2subroutine - thanks for the PR!  I noticed you marked this as work-in-progress.  Is there anything in particular you're still planning to do or is this ready for review from someone from the Ark team?

Hi @rosskukulinski, yeah it's ready for review, maybe @ncdc can take a look at this one.

Thanks for the PR @ffd2subroutine. I'll give this a read and test and get back to you.

I think upping the defaults makes sense. I just looked at Kubernetes 1.11, and it looks like the controller-manager's defaults are qps=20, burst=30. I like those values - what do you all think?

@ncdc going with controller-manager's defaults sounds reasonable to me!

@skriss @nrb should we try wordsmithing the flag help text a little bit?

@ncdc Probably worth doing, yeah.

@ncdc @Bradamant3 would like to get this into v0.10, so we just need to finalize help text. WDYT about these:
client-burst: maximum number of requests by the server to the Kubernetes API in a short period of time
client-qps: maximum number of requests per second by the server to the Kubernetes API once the burst limit has been reached

Sounds good enough for now!

@ffd2subroutine if you can update the help text to what I proposed just above, we should be good to merge - thanks!

@ffd2subroutine thanks - would you mind rewording the commit message so it doesn't have [wip] in it any more?

LGTM, thanks @ffd2subroutine!