API: Handle JS WebSocket's lack of support for auth headers

Is your feature request related to a problem? Please describe.
The native JS WebSocket does not support authentication via the Authorization header. This blocks streaming application and staging logs from the browser

https://developer.mozilla.org/en-US/docs/Web/API/WebSocket
https://stackoverflow.com/questions/4361173/http-headers-in-websockets-client-api

Describe the solution you'd like
There a a number of different ways auth can be handled via socket, many listed here https://websockets.readthedocs.io/en/latest/topics/authentication.html.
Describe alternatives you've considered
I need to discuss with Neil how we handled this in Stratos, I think we manually updated a standard https request to wss in our backend.
Additional context
It doesn't look like this is needed by the CLI - https://github.com/epinio/epinio/blob/6ef5cc0044f71c01cf90ed83bcdda18251c594a7/internal/cli/usercmd/client.go#L799

@richard-cox I'm still experimenting with things but currently the plan is to have each user defined as a BasicAuth Secret. The old secrets will be gone. The new secrets will be labeled with this key and value: https://github.com/epinio/epinio/blob/871-js-compatible-auth/helpers/kubernetes/cluster.go#L54-L55
e.g.
epinio.suse.org/api-user-credentials=true

I hope it not too difficult to change your logic around this.


pulling data from WoS throws an error

Sometimes the code on method-2 to pull metadata from WoS throws an error:
Traceback (most recent call last):
  File "/home/andre/repositories/open-hardware-supply/code/method2-scholarly/1_collect_wos_entries.py", line 37, in <module>
    wosTtr.download_records()
  File "/home/andre/repositories/open-hardware-supply/code/method2-scholarly/get_wos_records_from_api.py", line 175, in download_records
    downloaded_data_keys = set(
  File "/home/andre/repositories/open-hardware-supply/code/method2-scholarly/get_wos_records_from_api.py", line 176, in <genexpr>
    self.data_key(json.loads(x)["scraped"]) for x in mrf.readlines()
  File "/usr/lib/python3.10/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.10/json/decoder.py", line 340, in decode
    raise JSONDecodeError("Extra data", s, end)
json.decoder.JSONDecodeError: Extra data: line 1 column 18904 (char 18903)

Namely the script 1_collect_wos_entries.py
I have dug around a bit to try to find out what is causing it, but failed to do so, as I cannot find anything wrong with the files generated, or with the files used to retrieve data from WoS..

After some digging, I realised that this error occurred when the initial files used to feed this part of the analysis were malformed. This traced back to the stage of using Scholarly for scraping data from Google Scholar.
Practically this means that if 0_collect_gscholar_data.py failed or got interrupted, this generated an entry that was "corrupted" and this would lead to errors when running the next stage of the pipeline.
Given that some keywords lead to a lot of data to be scrapped (which would lead to long scrapping times and increase the chance of bad entries), I broke down the scrapping based on year, so instead of running the code once to get all data from all years to a single file, there is now one file for each year per term. In other words, "open labware" folder has one folder for each year in the interval from 2005-2023.
This led to the scraping code running for a smaller time and therefore having less chances to create entries that would not play well with the next stage of analysis

Interesting. Thanks!
Though I don't see any changes in the latest commits related to years, other than a strange:
-YEARS = tuple(range(2005, 2024))
+YEARS = tuple(range(2017, 2018))

Is this on a different branch?
Looking at the code, it seems to download the data by year since 6a91257b (March 2023)

ah, sorry, not expressing myself properly..
It does have code to segment the query per year... but it was all being put in the same output file, so if it ran from years, 2005 to 2010, and than somewhere along year 2011 something got corrupted, it would make the subsequent routine throw an error...
since running this one script for a long time to scrape all years at once led to a very long run time, it increased the chance for errors.... Given that I wanted to finish collection of this part of the data as soon as possible, I manually ran things to run on a year per year basis (I know not the best approach), but this was only for both terms that had a very large number of hits (Open hardware and Open source hardware)....

I still don't get it. That commit was already storing each month of each year in a different file. See this line: https://github.com/amchagas/open-hardware-supply/commit/6a91257b5712b5f1c7faead6f5db0689f0dec30c#diff-1afc8f2273aece479eb75d16c6127d316bdba61baf91c04885ebc13c027fda97R94

Ni! No prob! This all seems very good, I was just trying to understand what is going on.
So essentially what happened is that you re-downloaded the data (re-queried Google Scholar) and now there is no more malformed data. Is that it?
And perhaps that you believe that downloading with more time passing between each step, by manually intervening for every term or for every year, helped avoid errors and thus malformed data?
Then you also split the data in many folders, but I don't see how this could have helped with the malformed data.


unserialize(): Error at offset 2 of 11 bytes Error in 3.1.1

Not sure what might be causing this. I'm trying to upgrade from 2.3

Full Stacktrace
unserialize(): Error at offset 2 of 11 bytes {"userId":1,"exception":"[object] (ErrorException(code: 0): unserialize(): Error at offset 2 of 11 bytes at /var/www/html/vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php:403)
[stacktrace]
#0 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php(254): Illuminate\\Foundation\\Bootstrap\\HandleExceptions->handleError()
#1 [internal function]: Illuminate\\Foundation\\Bootstrap\\HandleExceptions->Illuminate\\Foundation\\Bootstrap\\{closure}()
#2 /var/www/html/vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php(403): unserialize()
#3 /var/www/html/vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php(123): Illuminate\\Cache\\DatabaseStore->unserialize()
#4 /var/www/html/vendor/laravel/framework/src/Illuminate/Cache/Repository.php(99): Illuminate\\Cache\\DatabaseStore->get()
#5 /var/www/html/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(353): Illuminate\\Cache\\Repository->get()
#6 /var/www/html/vendor/opcodesio/log-viewer/src/Concerns/LogIndex/CanCacheIndex.php(69): Illuminate\\Support\\Facades\\Facade::__callStatic()
#7 /var/www/html/vendor/opcodesio/log-viewer/src/Concerns/LogIndex/CanSplitIndexIntoChunks.php(38): Opcodes\\LogViewer\\LogIndex->getChunkDataFromCache()
#8 /var/www/html/vendor/opcodesio/log-viewer/src/LogIndex.php(41): Opcodes\\LogViewer\\LogIndex->getCurrentChunk()
#9 /var/www/html/vendor/opcodesio/log-viewer/src/Readers/IndexedLogReader.php(107): Opcodes\\LogViewer\\LogIndex->addToIndex()
#10 /var/www/html/vendor/opcodesio/log-viewer/src/Readers/IndexedLogReader.php(27): Opcodes\\LogViewer\\Readers\\IndexedLogReader->scan()
#11 /var/www/html/vendor/opcodesio/log-viewer/src/Concerns/LogReader/KeepsFileHandle.php(55): Opcodes\\LogViewer\\Readers\\IndexedLogReader->onFileOpened()
#12 /var/www/html/vendor/opcodesio/log-viewer/src/Concerns/LogReader/KeepsFileHandle.php(29): Opcodes\\LogViewer\\Readers\\BaseLogReader->openFile()
#13 /var/www/html/vendor/opcodesio/log-viewer/src/Readers/IndexedLogReader.php(72): Opcodes\\LogViewer\\Readers\\BaseLogReader->prepareFileForReading()
#14 /var/www/html/vendor/opcodesio/log-viewer/src/Http/Controllers/LogsController.php(65): Opcodes\\LogViewer\\Readers\\IndexedLogReader->scan()
#15 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(46): Opcodes\\LogViewer\\Http\\Controllers\\LogsController->index()
#16 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Route.php(259): Illuminate\\Routing\\ControllerDispatcher->dispatch()
#17 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Route.php(205): Illuminate\\Routing\\Route->runController()
#18 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(799): Illuminate\\Routing\\Route->run()
#19 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(141): Illuminate\\Routing\\Router->Illuminate\\Routing\\{closure}()
#20 /var/www/html/vendor/opcodesio/log-viewer/src/Http/Middleware/ForwardRequestToHostMiddleware.php(50): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#21 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Opcodes\\LogViewer\\Http\\Middleware\\ForwardRequestToHostMiddleware->handle()
#22 /var/www/html/vendor/opcodesio/log-viewer/src/Http/Middleware/AuthorizeLogViewer.php(13): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#23 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Opcodes\\LogViewer\\Http\\Middleware\\AuthorizeLogViewer->handle()
#24 /var/www/html/vendor/opcodesio/log-viewer/src/Http/Middleware/EnsureFrontendRequestsAreStateful.php(38): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#25 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(141): Opcodes\\LogViewer\\Http\\Middleware\\EnsureFrontendRequestsAreStateful->Opcodes\\LogViewer\\Http\\Middleware\\{closure}()
#26 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php(78): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#27 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Foundation\\Http\\Middleware\\VerifyCsrfToken->handle()
#28 /var/www/html/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(121): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#29 /var/www/html/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(64): Illuminate\\Session\\Middleware\\StartSession->handleStatefulRequest()
#30 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Session\\Middleware\\StartSession->handle()
#31 /var/www/html/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#32 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Cookie\\Middleware\\AddQueuedCookiesToResponse->handle()
#33 /var/www/html/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(67): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#34 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Cookie\\Middleware\\EncryptCookies->handle()
#35 /var/www/html/vendor/opcodesio/log-viewer/src/Http/Middleware/EnsureFrontendRequestsAreStateful.php(31): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#36 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(162): Opcodes\\LogViewer\\Http\\Middleware\\EnsureFrontendRequestsAreStateful->Opcodes\\LogViewer\\Http\\Middleware\\{closure}()
#37 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(116): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#38 /var/www/html/vendor/opcodesio/log-viewer/src/Http/Middleware/EnsureFrontendRequestsAreStateful.php(37): Illuminate\\Pipeline\\Pipeline->then()
#39 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Opcodes\\LogViewer\\Http\\Middleware\\EnsureFrontendRequestsAreStateful->handle()
#40 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(116): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#41 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(798): Illuminate\\Pipeline\\Pipeline->then()
#42 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(777): Illuminate\\Routing\\Router->runRouteWithinStack()
#43 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(741): Illuminate\\Routing\\Router->runRoute()
#44 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(730): Illuminate\\Routing\\Router->dispatchToRoute()
#45 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(200): Illuminate\\Routing\\Router->dispatch()
#46 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(141): Illuminate\\Foundation\\Http\\Kernel->Illuminate\\Foundation\\Http\\{closure}()
#47 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#48 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ConvertEmptyStringsToNull.php(31): Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest->handle()
#49 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Foundation\\Http\\Middleware\\ConvertEmptyStringsToNull->handle()
#50 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#51 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TrimStrings.php(40): Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest->handle()
#52 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Foundation\\Http\\Middleware\\TrimStrings->handle()
#53 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#54 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Foundation\\Http\\Middleware\\ValidatePostSize->handle()
#55 /var/www/html/app/Http/Middleware/CheckForReadOnlyMode.php(51): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#56 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): App\\Http\\Middleware\\CheckForReadOnlyMode->handle()
#57 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php(89): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#58 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Foundation\\Http\\Middleware\\PreventRequestsDuringMaintenance->handle()
#59 /var/www/html/vendor/laravel/framework/src/Illuminate/Http/Middleware/TrustProxies.php(39): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#60 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Http\\Middleware\\TrustProxies->handle()
#61 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(116): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#62 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(175): Illuminate\\Pipeline\\Pipeline->then()
#63 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(144): Illuminate\\Foundation\\Http\\Kernel->sendRequestThroughRouter()
#64 /var/www/html/public/index.php(52): Illuminate\\Foundation\\Http\\Kernel->handle()
#65 /var/www/html/server.php(19): require_once('...')
#66 {main}
"}

hey @Brandutchmen thanks for the report!
First of all, what database are you using? Please include the version as well. I haven't tested the Log Viewer with database as cache driver.
In the meantime, could you switch Log Viewer to one of the other caching mechanisms, such as file or redis ? Just add it to your .env file, like so:
LOG_VIEWER_CACHE_DRIVER=file

I'll test the database cache driver later.

Good call.
Using either redis or file for LOG_VIEWER_CACHE_DRIVER works.
Plus, I should be using Redis for this anyway...
Thank you!

Attached is the error from using the database as a cache driver

@Brandutchmen hey, what database were you using? MySQL, PostgreSQL, MariaDB, SingleStore? And what version? Just so I'm replicating in the similar environment.

@arukompas, Mysql 8.
Docker image mysql/mysql-server:8.0

I was also not able to get database cache driver so I just switched to file.

same issue

hey @Brandutchmen , there were improvements in latest Log Viewer, namely v3.1.8, could you try it again with database cache driver?

i upgrade to newest version 3.1.9 but still have this error
every time  after access to route /log-viewer , and i access to another route after that it happened again.

hey @MNhat0308 , are you using a database cache driver? Which database type and version are you using?
Also, if you switch to a different cache driver, such as file or redis, does it then work properly?

hi @arukompas , so i'm using file cache driver and postgresql version 13

Hello @MNhat0308, I'm facing the same issue. Could you please tell me how you resolved it?

hi @irtzamazhar , i think you should upgrade to last version, i'm not using this anymore, so i don't know how to fix it/

@arukompas could you please help me to resolve this problem?

@irtzamazhar please share the Log Viewer version, PHP version, Laravel version, config/log-viewer.php and what other packages you're using.
Also, which cache driver are you using? If you switch to redis or file driver, does the issue disappear?

@irtzamazhar  If you're not using Sanctum, you have to disable the EnsureFrontendRequestsAreStateful middleware in config/log-viewer.php. This middleware utilizes Sanctum's encrypt_cookies middleware if available; otherwise, it defaults to Laravel's EncryptCookies middleware. In Laravel's EncryptCookies middleware, serialize is false by default.

In middle EncryptCookies file set protected static $serialize = false;  to false and it work well

See https://github.com/opcodesio/log-viewer/issues/346#issuecomment-2293286486
Closing.


iOS : App crash on

crash sigabrt
my application is crashing on runtime for both
Fabric.with([Crashlytics.self])
Fabric.with([Crashlytics()])

There's not enough information to debug this issue. Please share the stack trace and exception message.


chore: Unify test IDs

Fixing my oversight from c46d5b8c8bfbfd4d34972bd65b6b931c4d6d5ef3
CLI actually shows full paths to be close to the actual network call. The pytest plugin should follow the same logic. This use-case is more informational and aims to show the user what the request was to simplify debugging.
However, lookups in the API schema should be relative. Otherwise, if the user sets up some code to add a link, it will depend on the passed --base-url value, which is bad from the UX point of view. This use case aims-to be dependent on the API schema only, which makes it more portable.

Codecov Report

Merging #1092 (8426aa3) into master (3355ce9) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1092      +/-   ##
==========================================
- Coverage   99.40%   99.31%   -0.09%
==========================================
  Files          68       68
  Lines        5025     4980      -45
  Branches      832      832
==========================================
- Hits         4995     4946      -49
- Misses         16       18       +2
- Partials       14       16       +2

Flag
Coverage Δ

unittests
99.31% <100.00%> (-0.05%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/schemathesis/extra/pytest_plugin.py
97.95% <ø> (-2.05%)
:arrow_down:

src/schemathesis/lazy.py
94.38% <100.00%> (-0.07%)
:arrow_down:

src/schemathesis/models.py
99.13% <100.00%> (-0.02%)
:arrow_down:

src/schemathesis/specs/openapi/links.py
100.00% <100.00%> (ø)

src/schemathesis/specs/openapi/schemas.py
100.00% <100.00%> (ø)

src/schemathesis/cli/callbacks.py
98.24% <0.00%> (-1.76%)
:arrow_down:

src/schemathesis/serializers.py
97.82% <0.00%> (-0.16%)
:arrow_down:

src/schemathesis/runner/impl/core.py
97.34% <0.00%> (-0.02%)
:arrow_down:

... and 13 more

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 3355ce9...8426aa3. Read the comment docs.


Switch to new React Native experimental navigation

API is almost done, Hedger changed only names recently.
Waiting for https://github.com/facebook/react-native/releases/tag/v0.28.0-rc.0
The new API is very good, but lack documentation. Fortunately, it's easier than it looks like.
Why swich?

navigator will be obsolete soon
navigation state in redux
better designed

Resources:

https://github.com/ericvicenti/navigation-rfc/tree/master/Docs
http://blog.thebakery.io/react-native-experimental-navigation-with-redux/
https://github.com/jlyman/RN-NavigationExperimental-Redux-Example
https://gist.github.com/brentvatne/52af349a6b6ef2ee1b06
https://github.com/facebook/react-native/tree/master/Examples/UIExplorer/NavigationExperimental
https://github.com/facebook/react-native/tree/master/Libraries/NavigationExperimental
https://blog.nativebase.io/designing-react-native-app-for-multiple-platforms-a2121de42110#.cq975hipa

@grabbou So I investigated new navigation and one thing still isn't clear. Check this article please http://blog.thebakery.io/react-native-experimental-navigation-with-redux, especially
tabs: scopeNavigationReducer(tabs, 'tabs'),

I think it should be added to RN 0.28. Can you ask hedgerwang? WDYT?

https://github.com/facebook/react-native/commit/3a8b50ad550b176bbce5713c5c74e1318c10f2a0
https://github.com/facebook/react-native/commit/67002e8ae3c924bbba2e742dc1292b45f838a004

Yes! https://cloud.githubusercontent.com/assets/165856/16355280/120e7d38-3a67-11e6-9567-51c19c249fdf.png

I see you want to switch because of state in redux and better design.
Have you seen this project? https://github.com/aksonov/react-native-router-flux
It might help with those two issues until the experimental navigation is final. Thoughts @steida?

I know that project. I don't think new native navigation needs another level of abstraction, but I can change my mind later. Este will switch once new navigation will be completed.

I've switched este to use react-native-router-flux, complete with
platformDeps and/or platformReducer injections and I've gotta say I'm
pretty pleased with the results. My two cents.
On Thu, Jul 7, 2016 at 10:27 PM Daniel Steigerwald<EMAIL_ADDRESS>wrote:

I know that project. I don't think new native navigation needs another
level of abstraction, but I can change my mind later. Este will switch once
new navigation will be completed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/este/este/issues/935#issuecomment-231197109, or mute
the thread
https://github.com/notifications/unsubscribe/AAIIvED8Bx_-1TcDMjSpi5cqAWHv9b_mks5qTWE8gaJpZM4IwJIe
.

--
Best Regards,
Adrian Perez
http://adrianperez.org

@blackxored Sure it works somehow. But I think the design is not ideal and a bit overengineered regarding to backward compatibility.

Ok, this is it https://github.com/jmurzy/react-router-native


Add interaction tests for pagelayout sticky

Add a couple of interactive tests
To test this, check PageLayout/interactions.stories

This is great. Thank you for setting this up, @pksjce! A couple of questions:

Do these interaction tests run during CI? Specifically, will CI fail if we accidentally break an interaction?
When I run this locally, is this what we expect the interaction tab to look like?

I kinda messed up this branch badly. So I'll close this PR and open a new one.
@colebemis - Thanks!

Yes they run on CI. On CI, playwright runs these "storybook tests". Will mention it in the new PR.
The interactions for this test don't seem to be very expressive on the addon. There's also the problem that scrollIntoView does not come under any of the "actions" that this addon recognises. As mentioned in this https://storybook.js.org/addons/@storybook/addon-interactions at the very end, its

calls to userEvent., fireEvent, findBy, waitFor* and expect
that get shown in the step by step debugger.

However, I have some hope that this is being improved. In storybook 7.0.0 versions, there's improvements like this https://github.com/storybookjs/storybook/pull/18555 , which help us have more expressive data in that addon. I feel that the addon is still new and not so mature yet.


Create GAP_SampleName_1565085518.md

Thank you for submitting a Governance Action Proposal.
The corresponding wallet address associated with this proposal is 0x12345678901234567890
To qualify this proposal for consideration into the Swarm Network Voting Queue:

[ ] Stake a minimum of 250 SWM
[ ] Post the TxID of your staking transaction in this conversation.

What happens to stakes?
Any Swarm Member may also lend support to this proposal by staking a minimum of 250 SWM to the address above.
What happens next?

Every two months, the five most supported GAPs - by staked SWM - will be elevated to a Governance Action Ballot (GAB).
GABs will be placed in the GABs repository and will be scheduled to be voted on in a referendum by Swarm Members.
GABs that have been approved in a referendum become Governance Actions and will be placed in the Governance Action repository for public viewing.

I have deposited the stake. Here is my TxID: https://etherscan.io/tx/0x530d81a56cf06b7e04aa80b910100bcee8fbc076d2968b5310723545984684b1


add try.haxe.org link to README

to let curious viewers demo test it
also, its a hassle since it's needed to make a new one for every change that adds a feature or changes implementation, so you could add me as a contributor and i do that or do it yourself if you want

That is a good idea 👍


setting fragment depth in shader.

Hi there!
I kinda would like to set the Z-Depth of my pixel directly in my fragment shader.
I know that in regular opengl I can use gl_FragDepth  for that https://www.khronos.org/registry/OpenGL-Refpages/gl4/html/gl_FragDepth.xhtml
What i try right now is to set both frag_color and frag_depth in my FS
out vec4 frag_color;
out float frag_depth;

However I am not quite sure how I should configure my pipeline and pass_action.
I am using a custom pipeline for my fragment shader which consistes of two triangles which strech across the entire screen (a simple SDF shader) and then I use sokol_gl to render 3D geometry.
My idea is to set the z-depth for every pixel in my fragment shader and then draw my regular 3D geometry.

Maybe to make my question a bit clearer, I want to do that https://iquilezles.org/www/articles/raypolys/raypolys.htm

I haven't tried that yet, but I'm not aware of any required changes in the pipeline or pass state. You need to assign to gl_FragDepth though, e.g. a GLSL shader would look like this:
in vec4 color;
out vec4 frag_color;

void main() {
    frag_color = color;
    gl_FragDepth = ...;
}

I tried that in the cube-sapp sample with the D3D11 backend, and SPIRV-Cross seems to understand and translate this properly.
One thing to be aware of is that assigning depth in the pixel shader disabled early-Z optimizations (e.g. normally the pixel shader doesn't even run if the z-test would discard the pixel).
I'm currently not sure if the depth buffer content stays valid between passes on all backends, so when in doubt first try to render depth and color in the same pass first.


No Configuration File Found

Hello,
I recently installed svclone into its own environment using conda as suggested.
Upon attempting to run svclone annotate I get the following error indicating a lack of configuration file:
$ svclone annotate -i SV.vcf -b dedup.bam -s r1-annotate
Traceback (most recent call last):
File "/miniconda3/envs/svclone/bin/svclone", line 10, in
sys.exit(main())
File "/miniconda3/envs/svclone/lib/python3.6/site-packages/SVclone/cli.py", line 187, in main
args.func(args)
File "/miniconda3/envs/svclone/lib/python3.6/site-packages/SVclone/SVprocess/annotate.py", line 510, in preproc_svs
raise ValueError('No configuration file found')
ValueError: No configuration file found
Did I miss something during the setup process describing how to generate this file?
Thanks,
Kevin

The config file needs to be specified by -cfg <config_file> or, by default, SVclone will check the current directory for an svclone_config.ini file. Please download the default config file like so:
wget https://raw.githubusercontent.com/mcmero/SVclone/master/svclone_config.ini

Make sure to check that the settings are appropriate for your sample.
I've now added this information to the README.


Dynamic API Info not propagating

Describe the bug
Following the example for setting API info dynamically, in main.go in main(), the information is not propagating into the generated .json and .yaml files.
func main() {
	docs.SwaggerInfo.Version = "0.0.1"
	docs.SwaggerInfo.Host = "localhost"
	docs.SwaggerInfo.BasePath = "/api/v1"
	// ...
}

To Reproduce
Steps to reproduce the behavior:

Add docs.SwaggerInfo.Version = "0.0.1" to main()
Run swag init

Expected behavior
The swagger.json and swagger.yaml files have the version, host, and base path.
Screenshots

Your swag version
1.7.3
Your go version
1.17.1
Desktop (please complete the following information):

OS: Mac
Browser: Chrome/Firefox
Version: Latest versions

Additional context
When importing the docs package, the readme shows import "./docs", which does not work. I have to import "<full_path>/docs. Not sure if that makes a difference.

@josephzidell, I have no clue what you expect to see in the Readme.md  to clarify this.
Would you mind contributing with a PR regarding this matter?


Windows 2019 Datacenter Error

Please help me to solve the issue.

Some other info:
https://github.com/Wind4/vlmcsd/issues/37


godep introduced

This PR is a work in progress meant to address issue https://github.com/odeke-em/drive/issues/206. It bundles dependencies into drive-gen/Godeps.

Firstly to check out the branch

$ go get -u github.com/odeke-em/drive/drive-gen && cd $GOPATH/src/github.com/odeke-em/drive/drive-gen
$ git fetch --all && git checkout go-deps

Using godep

$ cd $GOPATH/src/github.com/odeke-em/drive/drive-gen && godep save

Unravelling/Restoring dependencies

$ cd $GOPATH/src/github.com/odeke-em/drive/drive-gen && godep restore

Please see file drive-gen/README.md for more information.

@odeke-em thanks for working on it!
i'm on holidays and will look at it in monday

I don't know what it is but when executing "godep save" it tells me:
godep: directory "/usr/lib/go/src" is not using a known version control system
godep: error loading dependencies

Is there something wrong with my setup?

To be honest, I've never used godep so this is all just pure speculation derived from the error reported :)
However,
Probably your Go binary was not built from source, it probably got installed by a download from the website or package. Would you mind trying installing from source but please make sure your GOPATH is well setup, that you can see how to do here https://github.com/odeke-em/drive#requirements. Then install go from source

godep is now working, but rev b1cb1e5a90decb4e0de7fd93b16bf6bc6cc6ecf1 doesn't exsits in the "github.com/odeke-em/google-api-go-client" repository.

Oops, sorry I hadn't pushed up changes from github.com/odeke-em/google-api-go-client. Please try again.

works fine now

Thanks @n4cer for testing it. Now an important question here is how do we package the dependencies in drive for users who don't need them? -- this is because majority of the users have been building drive until now without having to use godeps, plus packages in the project increase the size of the project. Please let me know your thoughts :) Also while we are at it, let me summon @shaggytwodope  @dgvirtual @IS-smcleod plus any other Linux folks to pitch in ideas.
To be honest it is only 772K in drive-gen/ vs 172K in src/ and given that we are still in the KB range this is okay, but just exploring other options

Merging this in since it fits the use case. Thank you for reporting the need for this. I'll try my best to always run Godeps before version release.


APK file not found in s8 oreo

The app can't find the apk on s8 Oreo beta 4.
I don't use Andromeda.

PrivSet_Logs.txt
Added because the mobile version has no upload....

Sorry for the late reply, it seems there are still compilation issues for some devices
I'll implement dynamic switch option between different compilers on next update, stay tuned :+1:


Add Wikipedia integration

E.g. via kiwix or however Internet-In-A-Box is doing it.
Will require installing the Wikipedia reader to the device, adding a redirect to nginx and a link to the webapp.
Discussion on Slack.
Alternatively, integrate with Outernet.

Resolving in favor of https://github.com/ascoderu/lokole/issues/454


Smart Editor - Enforce required fields set by smart editor on save

Enforce required fields set by smart editor on save

Code checked in


POOL 705 Update Form Layout

Added .prettierrc
Updated Builder form layout to match spec
Automatically populating fields based on spec

Looking great so far! Almost ready to deploy to staging 👍


dev: Remove prints in the cairo files

Remove all the prints in the cairo file and switch to logging or any other method to be able to manage verbosity

Hey! I might be able to do this, I can import a logger inside the hint and use that. Maybe that would be a little better


Create noop IPEX using temp folder

Closes #1984

Looks good. I am hoping you've tested it.

Sure! :)


Any Fixes/Improvements before Droidcon London Release?

Droidcon London is around the corner and I was planning to cut an up to date release for the event. My plan was to cut the release once PR https://github.com/openid/OpenYOLO-Android/pull/94 had landed, but wanted to check with everyone before doing so.

Sounds good for Dashlane side, no pending PR.
Le 29 sept. 2017 19:28, David Samuelson<EMAIL_ADDRESS>a écrit :
Droidcon London is around the corner and I was planning to cut an up to date release for the event. My plan was to cut the release once PR #94https://github.com/openid/OpenYOLO-Android/pull/94 had landed, but wanted to check with everyone before doing so.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/openid/OpenYOLO-Android/issues/95, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACGi-wEaRV1Wjr_jwGIWyPDqNb_R7tckks5snSjKgaJpZM4Po-TF.
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

AgileBits is good with this as well.
Cheers,
Michael

On Sep 29, 2017, at 1:30 PM, Stan Kocken<EMAIL_ADDRESS>wrote:
Sounds good for Dashlane side, no pending PR.
Le 29 sept. 2017 19:28, David Samuelson<EMAIL_ADDRESS>a écrit :
Droidcon London is around the corner and I was planning to cut an up to date release for the event. My plan was to cut the release once PR #94https://github.com/openid/OpenYOLO-Android/pull/94 had landed, but wanted to check with everyone before doing so.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/openid/OpenYOLO-Android/issues/95, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACGi-wEaRV1Wjr_jwGIWyPDqNb_R7tckks5snSjKgaJpZM4Po-TF.
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/openid/OpenYOLO-Android/issues/95#issuecomment-333188254, or mute the thread https://github.com/notifications/unsubscribe-auth/AISh76FL2UQLmw8QBQPo2CfO565tQen9ks5snSkagaJpZM4Po-TF.

If anyone else has comments, please feel free to re-open.


[Java] Fixed build errors caused by UFT-8 encoding of source files.

Replaced non-ASCII characters in source files with Unicode escape sequences.

@sigansky,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Don't lowercase URL when those are specified in Brewfile

If a Brewfile defines a specific version of a package and this
package originates form an URL, the name shouldn't be lowercase.
An example of such file could be:
brew "https://raw.githubusercontent.com/Homebrew/homebrew-core/50c928c870001577ce6b7e28edf43e05df699852/Formula/etcd.rb"

Previous to this case this was falling with this error:
curl: (22) The requested URL returned error: 404 Not Found
Error: Failure while executing; `/usr/bin/curl -q --globoff --show-error --user-agent Homebrew/2.2.11\ \(Macintosh\;\ Intel\ Mac\ OS\ X\ 10.15.4\)\ curl/7.64.1 --fail --progress-bar --retry 3 --location --remote-time --continue-at 0 --output /Users/alexandru/Library/Caches/Homebrew/Formula/etcd.rb https://raw.githubusercontent.com/homebrew/homebrew-core/50c928c870001577ce6b7e28edf43e05df699852/formula/etcd.rb` exited with 22. Here's the output:

curl: (22) The requested URL returned error: 404 Not Found

The reason of the failure was due to the name been transformed
to lowercase.

Is there a reason why URL's aren't supported?
My case here is that I need a specific version of etcd installed on the system. From my understanding the way to do that in brew is to install a past formula. (brew install https://raw.githubusercontent.com/Homebrew/homebrew-core/50c928c870001577ce6b7e28edf43e05df699852/Formula/etcd.rb)unless I'm missing something.

Is there a reason why URL's aren't supported?

Run brew install $URL and you'll see the reason 😉.
In short: they will break and when they do they can't be fixed. We provide tooling (brew extract) to make your own specific versions you depend on that can be fixed when they break.

Thanks for point that out.
I know this is not the best place to ask this but I've done exactly what you've said extracted the package and create a new tap. But now it tries to build the package... Since it can't find a pre-build package in:
==> Downloading https://homebrew.bintray.com/bottles-etcd/etcd-3.3.15.mojave.bottle.1.tar.gz
curl: (22) The requested URL returned error: 404 Not Found

Is this expected or did I messed something up?
When installing from an URL I can get the correct version ==> Downloading https://homebrew.bintray.com/bottles/etcd-3.3.15.mojave.bottle.1.tar.gz Is there a way to make my tap install this? Building the package from scratch I don't think should be the desired result since I cannot assume re-building it will generate a replicable build.

If this is not the case I still think URL installs should be allow, if brew install command allows them I see no reason why Brewfile shouldn't. Or at least have a way to specify a version of a package in the Brewfile.

Is this expected or did I messed something up?

Somewhat expected. You'll want to remove the bottle do block. See https://github.com/Homebrew/brew/issues/6059

If this is not the case I still think URL installs should be allow, if brew install command allows them I see no reason why Brewfile shouldn't.

There is a "warning" telling you not to use them. They are likely to be deprecated and removed in future.

Or at least have a way to specify a version of a package in the Brewfile.

This is not how Homebrew works. It's a rolling-release package manager. Read https://docs.brew.sh/Versions

Sorry, passing on this due to reasons above.


Adds an optional TLS check for SimpleMatcher.

A TLS check is needed for protocol handlers that must be secured.
When serve2 detects and passes on a secure connection to an http handler, the TLS information is effectively lost. The http server is not aware of the TLS outer connection and thus does not patch up http.Request.TLS fields in incoming requests.
With http.Request.TLS always unset, http middleware and http handlers are unable to determine if the request is secure.
Ideally, we would find a way to patch up the lost http.Request.TLS but this did not appear trivial.
Instead this minor modification to SimpleMatcher provides a reasonable assurance of TLS before the handler gets the connection.
Serving HTTP and HTTPS
With this change, serve2 can be used to serve both http and https content from the same port.
The code example below creates a serve2 instance that will serve different content depending on the http or https scheme used:
 server := serve2.New()

 http := proto.NewHTTP(securedRouter)
 https := NewHTTPS(router)

 tls, err := proto.NewTLS([]string{"http"}, aCertificateFilePath, aTLSKeyFilePath)
 if err != nil {
	 log.Fatalf("[ERROR] Listen to '%v' failed : ", config.Listen, err)
 }
 server.AddHandlers(tls, http, https)

I have chosen not to include NewHTTPS in this pull request. The comments above NewHTTP hint the code this is based on, NewHTTP, is not best practice or at least likely to be superseded in the near future.
NewHTTPS is implemented in full below:
func NewHTTPS(handler http.Handler) *proto.ListenProxy {
	sm := &proto.SimpleMatcher{Matches: proto.HTTPMethods, RequiresTLS: true}
	lp := proto.NewListenProxy(sm.Check, 10)
	lp.Description = "HTTPS"

	httpServer := http.Server{Addr: ":https", Handler: handler}
	go httpServer.Serve(lp.Listener())
	return lp
}

I definitely agree that being able to set http.Request.TLS would be nice, but as you have noticed, it's a bit tricky. I would in general like for the http library to have much more functionality exported...
Before we continue with this specific PR, are you sure that TLSMatcher wasn't what you wanted to use, which is capable of detecting a TLS connection and checking the requested protocol? Something like:
func NewHTTPS(handler http.Handler) *ListenProxy {
	tm := &proto.TLSMatcher{
		NegotiatedProtocols: []string{"http/1.1"},
		Checks: proto.TLSCheckNegotiatedProtocol,
	}
	lp := NewListenProxy(tm.Check, 10)
	lp.Description = "HTTPS"

	httpServer := http.Server{Addr: ":https", Handler: handler}
	go httpServer.Serve(lp.Listener())
	return lp
}

As a side-note, I believe that HTTP/1.1 is advertised as "http/1.1" normally, not "http", as you wrote in your example.

I have a couple of protocols behind TLS – one is http and the other is a custom protocol that also uses TLS.
I have a modified SimpleMatcher implementation that works but it requires more code than is ideal.
After experimenting, the resulting PR felt like the smallest change for the largest return. :-)

TLS provides a protocol negotiation mechanism, which allows you to tell which specific protocol you want "next" (hence the name "NextProtos"). Browsers use this to request HTTP/1.1 or HTTP/2 using different "NextProto" requests.
If using NextProto (NegotiatedProtocol in Golang-speak) is insufficient, and the protocol can only be detected by reading the first few bytes, then something like the modified simplematcher would be required. I'm not sure if I would personally put it straight into the SimpleMatcher, though, as it was... Well, supposed to be simple.
I have an idea that might simplify something like this in the future, though... What if we had a "ChainMatcher", where you could do something like:
t := proto.TLSMatcher{}
h := proto.NewHTTP(secureRouter)
ch := proto.NewChainMatcher(h.Handle, t.Check, h.Check)

server.AddHandler(ch)

Does that idea sound bad? That way, you can have SimpleMatcher be simple (In the sense that it doesn't have very specific "extra" functionality), but then also require TLSMatcher's check to validate before calling the supplied handler. It should also be very fast for me to implement, while being considerably more flexible. An empty TLSMatcher should just match any TLS connection. I would still suggest adding the NegotiatedProtocol check if you can, though.

Thank you for the insight into TLSMatcher and NegotiatedProtocol.
A chained match approach would be better than this PR.
I wish more SSL/TLS libraries and tools provide easy access to NextProto. :-)

Which TLS library are you using? ALPN ("Application-Level Protocol Negotiation", or "Next Protocol Negotiation" in earlier versions. Yes, I googled the proper name, sue me!) is a relatively new extension, introduced for the purpose of distinguishing between HTTP/1.1 and HTTP/2, but universal so it can be used to request any protocol. Chrome introduced it around 2012. GnuTLS had support for it since 2013, although (libre|open)ssl didn't add support till January this year...
Anyway, the branch "test" includes a ChainMatcher with tests that pass, but it doesn't have examples, comments, or anything like that yet. I'll get that done later today. Feel free to comment on it.

I am investigating if serve2 could help with existing OS X and iOS based clients and services. They use a mix of networking technologies including Apple's CFSockets – so are limited by Apple's historic choices and exposed APIs.
It would be great to have everyone running the latest versions but that is not in my control. :-)
Thank you for sharing serve2 and entertaining this esoteric pull request. I will close #5 and keep an eye on ChainMatcher.

"Chain" added to master. The example just so happens to be a HTTP + TLSMatcher one.


Add Apache Atlas init action with automated tests

@DariuszAniszewski Are you still work on this? I was able to use this to validate with Atlas 1.2.0 RC3. If you can resolve the conflict, I can help do the review and create a bucket for the distro file.

/gcbrun

@roderickyao tests are failing for this init action, may you take a look?

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun


"Periodic" runs when I deploy my rule...

Hi,
So I've created this policy:
policies:
  - name: untagged-offhour-ec2-rule-stop
    resource: ec2
    mode:
     type: periodic
     schedule: "cron(00 20 ? * MON-FRI *)"
     role: [Insert Role Here]
    filters:
     - "tag:OffHour": empty
    actions:
      - stop

and it all works fine, stops untagged ec2's at the right time and all is good... Besides one thing...
When I run this from my terminal to create a Lambda, and then run the lambda, it will stop all untagged ec2's before the time I have set.
Although it will run at the time I set, it also runs when I deploy which is the issue.

i tried your policy, i don't see any extraneous executions either at deploy time from custodian or by the lambda, ie the policy only executes afaics on the cron. That your manually invoking the lambda is why your seeing it execute outside of the schedule. The policy setups a cloud watch event that triggers on the given schedule, if your manually invoking the lambda your bypassing the schedule.


Add json encode filter

I think this can be quite helpful to inline an array for JS usage or stuff like that.. Anyway I was needing it and thought it could have its place in core.

Escaping of forward slashes should be optional if it isn't already for this filter (didn't see it documented, but I may have missed it), since the JSON spec doesn't require escaping of forward slashes.

@mdpatrick, the JSON_UNESCAPED_SLASHES option is only for PHP 5.4.0, besides all decoders should handle this since it's part of the spec, so I would not bother with adding this.

Thank you for the clarification


Ubuntu Unity support

Hi,
I know this is a big ask, but is there any chance or likelihood or hope, that you could add support for the unity desktop as well?
In any case, great idea, great work!
Cheers

Hi,
Gnome Desktop is the priority for now, once the base fundamentals for this extension become stable, expansion to other desktop environments will become possible.


Link to Slides

It would be great to have the link to the slides(https://speakerdeck.com/wojtekmach/building-an-umbrella-project)  and eventually to the video in the readme.

good idea, thanks @buenaventure!


Bump up latest stable versions of OpenSSL

I'll update old versions of JRuby
Verifying checksum for https://s3.amazonaws.com/jruby-org/downloads/1.7.7/jruby-bin-1.7.7.tar.gz
curl: (22) The requested URL returned error: 403
./script/mirror: line 33: /tmp/[90](https://github.com/rbenv/ruby-build/actions/runs/4118510044/jobs/7111174980#step:5:91)7b24578604c3eded40b84a63.0.8c64ab76a6b76b31cf343afdde8dbfeffd4: No such file or directory


How can we delete Result source

[Enter feedback here]
Hi there, I can easily add and modifiy seach result source but I can't find a way to simply delete tests sources that I've made in my tenant.
Thanks.

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

ID: 4072d3b5-45f9-746a-2954-64006add2181
Version Independent ID: 66f9429e-6fd5-500b-048f-add3fdb61b5f
Content: Manage result sources - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/manage-result-sources.md
Service: sharepoint-online
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hello @CarlVerret
You have the option selecting the down arrow next to the result source, for example:

hope this information helps you,

Thanks!  I finally figured it out, problem is that there's no mention of it in doc +  the tiny arrow is quite far away and only appears when you hover over the list items.  Maybe doc can be adujsted to mention it ?

Thanks! I finally figured it out, problem is that there's no mention of it in doc + the tiny arrow is quite far away and only appears when you hover over the list items. Maybe doc can be adujsted to mention it ?

@CarlVerret Carl, will propose it, if it gets approval, it will be published.
Thanks


Single user is broken

With the refactored codebase, single user environments would not instantiate correctly and the user switching keybindings would display an animation when the user didn't actually change. This fixes that and a few small issues I noticed.

Current coverage is 32.94% (diff: 42.85%)

Merging #14 into master will decrease coverage by 0.18%

@@             master        #14   diff @@
==========================================
  Files             1          1
  Lines           166        173     +7
  Methods          40         40
  Messages          0          0
  Branches         13         16     +3
==========================================
+ Hits             55         57     +2
- Misses          111        116     +5
  Partials          0          0

Powered by Codecov. Last update 5c8854d...f1d3d5f


var config = wellknown('Gmail');

Do I need var config = wellknown('Gmail');? I don't really get what this does...?
var nodemailer = require('nodemailer');
var wellknown = require('nodemailer-wellknown');

var doNotReply = nodemailer.createTransport({
  host: 'mail.mydomain.com',
  ssl: true,
  port: 25,
  tls: { rejectUnauthorized: false },
  auth: {
    user<EMAIL_ADDRESS>    pass: '...'
  }
});

module.exports.doNotReply = doNotReply;

var adminEmail = nodemailer.createTransport({
    service: 'Gmail',
    auth: {
      user<EMAIL_ADDRESS>      pass: '...'
    }
});

module.exports.adminEmail = adminEmail;

Nodemailer manages the wellknown handling instead of you so you do not need to include the nodemailer-wellknown module wellknown('Gmail'). Just keep the service option as it is and thats it.


x/tools/cmd/goimports: MergeLine panic on weird input

package m
import("t"
"g"
"_"
"s")

Run goimports on that.
Low priority, but probably an easy fix.
cc @bradfitz

The problem is inside astutil pkg (the DeleteNamedImport function) and can be reproduced by adding a case to tests. It's because it tries to merge a line by assuming the last line of an import declaration is always in form of:
import (
"foo"
)

However in this case it's:
import (
"foo")

After removing foo, we need to check that it's safe to merge. I have a fix for this, should I open a CL directly or do I need to claim this issue before I can open the CL (according to the Contribution Guide)?

Just mail a CL. I'm happy to review.


A.02.IR04

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
The test method should be specified in the same way as the same test in the WFS Download Service, meaning that the references to the relevant schema should be added.
Proposed Change
Add the schema reference.

Proposed resolution:

Implement proposed change

Proposed resolution accepted by default. See call on April 28.


Add IPv4 whitelist/blacklist plugin ip-restriction

Add IP whitelist/blacklist plugin ip-restriction, the code mainly migrate from kong's ip-restriction.
Use lua-resty-iputils check CIDR v4 format as the json-schema cannot check CIDR format.
Now IPv6 doesn't support.

@moonming do you agree we can merge this PR first, and fix those small things with new PR.

@moonming do you agree we can merge this PR first, and fix those small things with new PR.

I will modify this PR directly.

@moonming I have discussed with @membphis, and plan to use another implementation, and add IPv6 support，so I may PR the same plugin soon later.

@chnliyong ok, already merged this PR first.


fix(ui): "sign in" button hidden at small devices

Checklist:

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the main branch of freeCodeCamp.
[x ] I have tested these changes either locally on my machine, or GitPod.

Closes #46534

There's a few failing tests here. Mind taking a look at those @shootermv?

@moT01, thanks for taking a look and finding out where the UI breaks. @shootermv thanks for pushing the fixes.
I will take it from here. In the few days, I will try different UI alternatives, push the changes, and include screenshots.

Looks good @ahmadabdolsaheb 👍

@shootermv, design wise this should be good to go.
Feel free to clean up the pr if necessary and pass the tests.


WSL overload resolution should not be cascading

Migrated from https://bugs.webkit.org/show_bug.cgi?id=176333:
At 2017-09-04T20:31:55Z<EMAIL_ADDRESS>wrote:
Currently WSL resolves overloads by just proceeding through signatures in order, and returning the first one that matches.  That's pretty weird.  For example, it means that if someone uses #include as a mechanism of modularity, then the order in which things are included will determine what gets called.  This is in contrast to C++, which has fairly deterministic overload resolution rules that will often report overload ambiguity errors in cases where things would have gotten weird.  Also, regardless of what you think of cascading overload resolution versus C++ overload resolution, it is a goal of WSL to be similar to C++.  So, this implies having some deterministic rules like C++ does.
I propose the following.  When there are N matches where N is greater than 1, they are ranked according to how they used inferred type variables.  Those are type variables that were not defined by type arguments to the call.  The math for this will be done using rational numbers with bignum numerators and denominators for maximum determinism.  The ranking formula gives each parameter a point.  If the parameter does not mention any inferred type variables, it gets one point.  If it is nothing more than just a reference to a type variable and the type variable has no protocol, then it gets zero points.  In general, we give it points recursively, so that you get more than zero points if the type variable is mentioned in some context like T^ or Foo.  For example:
points(ptrType) = points(ptrType.elementType) * 3/4 + 1/4;

For type variables, we give 1/3 point if it mentions a protocol, and zero points otherwise.
This enables us to do overload resolution in obvious cases:
void foo(int); // Obviously more specific!
void foo(T);
And give errors in cases that feel like they should get errors:
void foo(int, T);
void foo(T, int);
Cases that are more specific by having a more specific protocol will be resolved unambiguously:
void foo<T:numeric>(T); // More specific!
void foo(T);
But we will give errors if things get any weirder:
void foo<T:numeric>(T);
void foo<T:primitive>(T);
This will be an error even though numeric is a more specific protocol than primitive. I think that's the right call just because if we make it any more complicated, then we make our lives a lot harder with probably not a whole lot of benefit for anybody.  I think that a lot of users would expect an error here.

At 2017-09-04T20:33:12Z<EMAIL_ADDRESS>wrote:
Oh and another thing: if you pass IntLiteral, then it should create one more point for itself, which is either 0 or 1 depending on whether it matches an actual int32.
This means that if we pass the literal 0 to:
void foo(int);
void foo(uint);
Then it will match the int.
But if you pass 0 to:
void foo(uint);
void foo(double);
Then you'll get an error.

At 2017-09-07T23:18:17Z<EMAIL_ADDRESS>wrote:
Created attachment 320202
the patch

At 2017-09-08T02:04:53Z<EMAIL_ADDRESS>wrote:
Created attachment 320223
work in progress

At 2017-09-07T22:21:15Z<EMAIL_ADDRESS>wrote:
Actually, I really like the C++ approach, which as I understand it is checking if there is a signature whose types would be accepted by all other signatures but not the other way around.

At 2017-09-09T01:42:47Z<EMAIL_ADDRESS>wrote:
(In reply to Myles C. Maxfield from comment #6)

Comment on attachment 320226 [details]
the patch
View in context:
https://bugs.webkit.org/attachment.cgi?id=320226&action=review
Why no tests?

The hard parts are handled by existing overload resolution scenarios.  Most of the code in this patch was for making TEST_doubleNot happy.
But, I added some new tests.

Tools/WebGPUShadingLanguageRI/CallExpression.js:56

becomeCast(returnType)

But isn't there still a CastExpression class? It doesn't look like you
deleted it

I meant to delete it.  I did remove it from All.js.  I fixed that locally.

Tools/WebGPUShadingLanguageRI/Lexer.js:107

       if (/^(struct|protocol|typedef|if|else|enum|continue|break|switch|case|default|for|while|do|return|constant|device|threadgroup|thread|operator|null|true|false)$/.test(RegExp.lastMatch))

Doesn't this set RegExp.lastMatch? Why doesn't this break things?

I think that lastMatch is set if there is a match.  If there isn't a match, it's not set, and we're OK.

Tools/WebGPUShadingLanguageRI/NameResolver.js:121

       node.becomeCast(type);

But you don't know what |type| is! Won't this break if malformed content is
provided?

NameResolver just needs to know that there is a type by that name.  It knows this at this point.
Note that becomeCast turns this into a TypeRef that incorporates the CallExpression's type arguments.  Later, Checker will give you an error if that TypeRef is invalid for any reason.

Tools/WebGPUShadingLanguageRI/Node.js:-32

   let memoTable = visitor._memoTable;

   if (memoTable.has(this))

       return memoTable.get(this);

👍

Tools/WebGPUShadingLanguageRI/Test.js:100

No new tests?

At 2017-09-08T02:22:59Z<EMAIL_ADDRESS>wrote:
Created attachment 320226
the patch

At 2017-09-08T23:29:54Z<EMAIL_ADDRESS>wrote:
Comment on attachment 320226
the patch
View in context: https://bugs.webkit.org/attachment.cgi?id=320226&action=review
Why no tests?

Tools/WebGPUShadingLanguageRI/CallExpression.js:56

becomeCast(returnType)

But isn't there still a CastExpression class? It doesn't look like you deleted it

Tools/WebGPUShadingLanguageRI/Lexer.js:107

       if (/^(struct|protocol|typedef|if|else|enum|continue|break|switch|case|default|for|while|do|return|constant|device|threadgroup|thread|operator|null|true|false)$/.test(RegExp.lastMatch))

Doesn't this set RegExp.lastMatch? Why doesn't this break things?

Tools/WebGPUShadingLanguageRI/NameResolver.js:121

       node.becomeCast(type);

But you don't know what |type| is! Won't this break if malformed content is provided?

Tools/WebGPUShadingLanguageRI/Node.js:-32

   let memoTable = visitor._memoTable;

   if (memoTable.has(this))

       return memoTable.get(this);

👍

Tools/WebGPUShadingLanguageRI/Test.js:100

No new tests?

At 2017-09-09T02:06:49Z<EMAIL_ADDRESS>wrote:
Created attachment 320330
the patch

At 2017-09-09T01:43:18Z<EMAIL_ADDRESS>wrote:
Created attachment 320327
the patch
Add more tests, address other feedback.

At 2017-09-10T21:49:35Z<EMAIL_ADDRESS>wrote:
Landed in https://trac.webkit.org/changeset/221837/webkit

At 2017-09-27T19:53:06Z<EMAIL_ADDRESS>wrote:
rdar://problem/34694207


Image module CSS fix

The image module was a great contribution, I love having it in my bar. However, it didn't match the style of the rest of the repo and had a few issues that this PR addresses.

The current implementation does not properly attach CSS tags to itself. By running env GTK_DEBUG=interactive waybar one can see that the image module does not populate a name or attach any relevant style classes. This PR fixes that and brings it in parallel with styling of other waybar modules. You can now address it as #image in styles.css, and if you want duplicate modules you can define them as image#img1,image#img2 and address them as #image-img1,#image-img2.
Documentation was not up to speed. The man page has been updated in this PR, and I'm adding the relevant wiki page as we speak.

Thanks!

This works well, many thanks.
I did however notice that defining my module as "image#im1" in config, and then trying to address it as #image-img1 did not work. Instead I defined it as simply #image in css which worked.
Not an issue unless trying to use multiple images.

Hmm, that should work, it’s working for me. Could you send over the version of waybar you are running, and your current config file?

This works well, many thanks.
I did however notice that defining my module as "image#im1" in config, and then trying to address it as #image-img1 did not work. Instead I defined it as simply #image in css which worked.
Not an issue unless trying to use multiple images.

Hmm, that should work, it’s working for me. Could you send over the version of waybar you are running, and your current config file?

Version is current master,
config
"image#gentoo": {         "path": "/usr/share/icons/Papirus/48x48/apps/start-here-gentoo.svg",         "size": 24,         "on-click": "rofi -show drun -theme arthur -icon-theme Papirus -show-icons"  },
style.css
 #image {           margin-left: 8px;  }
If I change style.css to #image-gentoo the css isn't being attached. It works simply with #image.


Is this still a problem with latest version ?

@ricardobranco777 It has been detected that this issue has not received any activity in over 6 months. Can you please let us know if it is still relevant:

For a bug: do you still experience the issue with the latest version?
For a feature request: was your request appropriately answered in a later version?

Thank you!
This issue will be automatically closed in 1 week unless it is commented on.
For more information please refer to https://github.com/docker/libnetwork/issues/1926

I haven't been able to reproduce it using Virtualbox.  Anyway, any status information on /var/lib/docker should be fsync'ed to avoid these issues.


Unable to recursive in laster version

const klawSync = require('klaw-sync');
klawSync(srcPath, {
  nodir: true,
  filter: (item) => path.extname(item.path) === '.md'
})

like directory structure:
https://github.com/cipchk/delon/tree/master/packages/abc
just only get:
./README.md

should be includes like this:
./avatar-list/index.md
...
./README.md

work in 3.0.0.

@cipchk the logic is changed in v4.0.0. You have to use more sophisticated condition for your filter function! I understand that might create some issues for some people, but it is to support easy to understand code and refuse confusion! (I am pointing to noRecurseOnFailedFilter option)

@manidlou thanks for work.
how to get the same result in 3 version. sorry, i tried a lot of filter but wasn't correct.

it depends on your directory structure! not sure if this works but try with this
const klawSync = require('klaw-sync')
const root = 'your root dir'
klawSync(srcPath, {
  nodir: true,
  filter: (item) => item.path !== root && path.extname(item.path) === '.md'
})

a working code:
const klawSync = require('klaw-sync')
klawSync(srcPath, {
  nodir: false,
  filter: (item) => item.stats.isDirectory() || path.extname(item.path) === '.md'
}).filter(item => path.extname(item.path) === '.md');

but i think include bad code for work.
thanks again.


Upgrade core-js to version 3

When installing oidc-client a warning is shown:

<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

This dependency should be updated to avoid future issues.

Any word on this?

PR is pending. Will plan to merge it soon. Sorry for the delays.

as of today, still no fix :(

as of today, no updates still

@brockallen Any updates?

I thought this was merged in


Only studying max_depth hyperparameter when saying "some key hyperparameters" in notebook intro

In https://inria.github.io/scikit-learn-mooc/python_scripts/trees_hyperparameters.html
It is said in the beginning:

In this notebook, we will illustrate the importance of some key hyperparameters on the decision tree

However, by the end of the notebook, only one was seen, max_depth.
It concludes with

The other parameters are used to fine tune the decision tree and have less impact than max_depth.

We should either dedicate this notebook to this parameter, or add information on some others.

Probably the quickest fix is to fix the intro.


importlib-metadata wrong version?

Hi all,
I tested to start the datacube-explorer with docker-compose. The flask application could successfully been started, but an error was shown on the website because the cubedash-gen commands have not been conducted (e.g., please run cubedash-gen --init).
I tried to run these commands within the running docker container, but got the following error:
root@098aa300025e:/code# cubedash-gen -v --init
Traceback (most recent call last):
  File "/env/bin/cubedash-gen", line 33, in <module>
    sys.exit(load_entry_point('datacube-explorer', 'console_scripts', 'cubedash-gen')())
  File "/env/bin/cubedash-gen", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/env/lib/python3.6/site-packages/importlib_metadata/__init__.py", line 833, in distribution
    return Distribution.from_name(distribution_name)
  File "/env/lib/python3.6/site-packages/importlib_metadata/__init__.py", line 448, in from_name
    raise PackageNotFoundError(name)
importlib_metadata.PackageNotFoundError: No package metadata was found for datacube-explorer
I discovered an error within the docker-compose build process
pyppeteer 0.2.5 requires importlib-metadata<3.0.0,>=2.1.1; python_version < "3.8", but you'll have importlib-metadata 3.10.1 which is incompatible.
With installing importlib-metadata with version 2.1.1 I could reinstall the datacube-explorer application (python setup.py develop) in the container. Afterwards I was able to use cubedash-gen within the container and run the following commands:
cubedash-gen -v --init
python -m cubedash.generate --all

Thanks for the report Jonas.
Oddly, I just checked my own container and I'm running the the "wrong" version of importlib_metadata (3.10.1). I'm wonder if something deeper happened -- it looks like Explorer's package may not have been installed at all.  But I haven't been able to reproduce the issue yet.
I had planned to look at freezing our dependencies in the container to avoid quirks like this, as new releases of anything can break our build at unexpected times.


reduce scale of script, use library

uses library for OCUtil
logging instead of print, including verbosity
redundant script args removed
redundant functions removed
testProjects requires no external data so can be unit tested

I: 23, 0: Locally disabling import-error (F0401) (locally-disabled)
F: 18, 0: Unable to import 'openshift_tools.monitoring.ocutil' (import-error)

Not sure why this error exists, I'm happy to commit without tests passing :-)

Fail is accessing a private class member function, I don't yet know how to add this to the library

:+1:


Notebook: tab order is funky

I like the up / down keyboard navigation over notebook cells, but when you try to use tab to navigate the order is very unexpected.

Focus a notebook. I am using my-work.github-issues  my work cell
Press tab -> Focus is on GitHub issues label
Press tab -> focus seems lost
Press tab -> focus is on the start of the document, even though I did not traverse until the end of the docuemnt

Ideally tab should go in visual order. If that is not possible tab should move focus out of the notebook. Similarly tree tab is not used to move focus so users use up / down, but pressing tab focuses out of the tree and does not lead to unexpected jumping of focus.

Fixed in this change

Get rid of output focus sink when cell has no output, to avoid a dead spot when tabbing through cell (step 3 in OP)
Fix the toolbar losing focus shortly after tabbing onto it, by avoid context key churn
Fix domFocus when focus is in a different element from the one that is selected (depends on an earlier PR in listCommands.ts)

Much better now. Thanks for fixing this.


WIP: [OSD-22023] Add new deduplicated metric for vcpus.

This metric is being forwarded, as a deduplicated metrics.
See: OSD-22023 for more information.

for context it requires https://gitlab.cee.redhat.com/service/hypershift-platform-rhobs-rules/-/merge_requests/49 and https://gitlab.cee.redhat.com/service/osd-fleet-manager/-/merge_requests/810 first.

@bergmannf I believe you need to additionally add the metric to the template, see https://github.com/rhobs/configuration/pull/680

/retest

/retest

/retest

@bergmannf @typeid: it seems like the build fails because of an issue we had in the past, which is already fixed in the more recent commits. If you pull-in the latest commits from main it should solve the issue.


Issue with k8s.io/docs/concepts/cluster-administration/networking/

This is a Bug Report
Pod on work-1 can not ping to pod on worker-2 when cluster uses one cidr for all nodes

Problem:
Precondition: the cluster have 1 master, 2 worker. The cluster use one cidr for all nodes. The question is “how to config network to pod on worker-1 ping to pod on worker-2 ?”
Proposed Solution:
Page to Update:
https://kubernetes.io/...

Hello，More advanced features need to rely on network plugins instead of Kubernetes itself.
For network problems you may go to Stack Overflow to ask questions，This can only solve the problem of the document. ;)

/triage support


[epoxy] Specify CBv1 marshalled payloads

Restrict the first version of the Epoxy transport wire format only use
Compact Binary v1 marshalled data for payload and layer. This can be
relaxed in the future, but some handshaking will be needed to do things
like agree on a common protocol, exchanges schemas, &c.

LGTM.


fixed "Wite" typo

Fixed two instances of "DelegatedPermissionGrant.ReadWite.All" -> "DelegatedPermissionGrant.ReadWrite.All"

looks good to me. Thanks.


Remove the legacy Getting Started With MovieLens example notebooks

These notebooks have already been reworked and updated to use more recent versions of Merlin, and the tests for these notebooks are starting to cause maintenance headaches. Seems safe to get rid of them at this point to save ourselves the hassle of continuing to keep them running.
(The failing tests related to this legacy example are blocking the CI container build, which is partially blocking the Models PR to update the input format, which is itself blocking downstream work on session-based serving, so... 🤪 )

@karlhigley thanks for the PR.  I am fine to remove the legacy example nbs. What are the updates required in 02-Deploying-multi-stage-RecSys-with-Merlin-Systems.ipynb nb? I see this nb among the files.


Warning: unable to get metrics for resource cpu: no metrics returned from resource metrics API

NAME          CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%
k8s-master1   162m         8%     2303Mi          59%
k8s-master2   2000m        100%   2324Mi          60%
k8s-master3   2000m        100%   2264Mi          58%
k8s-worker1   842m         10%    8750Mi          13%
k8s-worker2   1090m        13%    41531Mi         64%
k8s-worker3   724m         9%     5703Mi          8%

NAME                          REFERENCE                                TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
camp-dns-unbound-autoscaler   Deployment/camp-dns-unbound-deployment   <unknown>/50%   2         9         3          15m

Name:                                                  camp-dns-unbound-autoscaler
Namespace:                                             default
Labels:                                                app.kubernetes.io/instance=camp-dns
                                                       app.kubernetes.io/managed-by=Tiller
                                                       app.kubernetes.io/name=camp-dns-efk
                                                       app.kubernetes.io/version=latest
                                                       helm.sh/chart=camp-dns-efk-1.0.0
Annotations:                                           <none>
CreationTimestamp:                                     Fri, 06 Sep 2019 06:48:04 +0900
Reference:                                             Deployment/camp-dns-unbound-deployment
Metrics:                                               ( current / target )
  resource cpu on pods  (as a percentage of request):  <unknown> / 50%
Min replicas:                                          2
Max replicas:                                          9
Deployment pods:                                       3 current / 0 desired
Conditions:
  Type           Status  Reason                   Message
  ----           ------  ------                   -------
  AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale
  ScalingActive  False   FailedGetResourceMetric  the HPA was unable to compute the replica count: missing request for cpu
Events:
  Type     Reason                        Age                     From                       Message
  ----     ------                        ----                    ----                       -------
  Warning  FailedGetResourceMetric       9m43s (x2 over 9m58s)   horizontal-pod-autoscaler  unable to get metrics for resource cpu: no metrics returned from resource metrics API
  Warning  FailedComputeMetricsReplicas  9m43s (x2 over 9m58s)   horizontal-pod-autoscaler  failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
  Warning  FailedComputeMetricsReplicas  7m12s (x10 over 9m27s)  horizontal-pod-autoscaler  failed to get cpu utilization: missing request for cpu
  Warning  FailedGetResourceMetric       4m54s (x19 over 9m27s)  horizontal-pod-autoscaler  missing request for cpu

When I deploy autoscaling.yaml in wide-camp-1909/sandbox, get:
(Pod rescaling succeeded)
Name:                                                  sample-hpa
Namespace:                                             default
Labels:                                                <none>
Annotations:                                           kubectl.kubernetes.io/last-applied-configuration:
                                                         {"apiVersion":"autoscaling/v2beta1","kind":"HorizontalPodAutoscaler","metadata":{"annotations":{},"name":"sample-hpa","namespace":"default...
CreationTimestamp:                                     Fri, 06 Sep 2019 07:05:13 +0900
Reference:                                             Deployment/sample-deployment
Metrics:                                               ( current / target )
  resource cpu on pods  (as a percentage of request):  99% (998m) / 50%
Min replicas:                                          2
Max replicas:                                          16
Deployment pods:                                       16 current / 16 desired
Conditions:
  Type            Status  Reason              Message
  ----            ------  ------              -------
  AbleToScale     True    ReadyForNewScale    recommended size matches current size
  ScalingActive   True    ValidMetricFound    the HPA was able to successfully calculate a replica count from cpu resource utilization (percentage of request)
  ScalingLimited  False   DesiredWithinRange  the desired count is within the acceptable range
Events:
  Type     Reason                        Age                    From                       Message
  ----     ------                        ----                   ----                       -------
  Warning  FailedGetResourceMetric       3m44s (x2 over 3m59s)  horizontal-pod-autoscaler  unable to get metrics for resource cpu: no metrics returned from resource metrics API
  Warning  FailedComputeMetricsReplicas  3m44s (x2 over 3m59s)  horizontal-pod-autoscaler  failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
  Warning  FailedGetResourceMetric       2m44s (x4 over 3m29s)  horizontal-pod-autoscaler  did not receive metrics for any ready pods
  Warning  FailedComputeMetricsReplicas  2m44s (x4 over 3m29s)  horizontal-pod-autoscaler  failed to get cpu utilization: did not receive metrics for any ready pods
  Normal   SuccessfulRescale             2m29s                  horizontal-pod-autoscaler  New size: 6; reason: cpu resource utilization (percentage of request) above target
  Normal   SuccessfulRescale             89s                    horizontal-pod-autoscaler  New size: 12; reason: cpu resource utilization (percentage of request) above target
  Normal   SuccessfulRescale             29s                    horizontal-pod-autoscaler  New size: 16; reason: cpu resource utilization (percentage of request) above target


Chrome crashes after reloading a web python plugin for a few times

How to reproduce: install a web python plugin and then reload for 2~3 times, the memory usage of ImJoy.io continuous increases and then crash.
Possibly because the pyodide enviroment is not released correctly when the plugin iframe is closed, and there is a memory leak in Chrome.
For the same plugin, firefox do not seem to crash.

@oeway  现在创建多个 Web Worker 后还会出现 Chrome 浏览器崩溃的情况
系统: Ubuntu 18.04
Chrome: Version 73.0.3683.75 (Official Build) (64-bit)


<IP_ADDRESS> not idempotent if GRUB_CMDLINE_LINUX_DEFAULT is present

Hi,
Some cloud vendors (I'm running on IBM Cloud VPC) include 2 lines that get returned as part of the check for audit_backlog_limit
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0 crashkernel=auto rd.lvm.lv=VolGroup/lv_root rd.lvm.lv=VolGroup/lv_swap rhgb quiet audit=1"
GRUB_CMDLINE_LINUX_DEFAULT="vga=normal console=tty1 console=ttyS0"

If that default parameter exists, then the patching of /etc/default/grub is done incorrectly, and a repeat run actually renders it invalid:
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0 crashkernel=auto rd.lvm.lv=VolGroup/lv_root rd.lvm.lv=VolGroup/lv_swap rhgb quiet audit=1
vga=normal console=tty1 console=ttyS0 audit_backlog_limit=8192"
vga=normal console=tty1 console=ttyS0 audit_backlog_limit=8192"
GRUB_CMDLINE_LINUX_DEFAULT="vga=normal console=tty1 console=ttyS0"

I think adding = or a word boundary to the grep search term would address this (at least would ignore the _DEFAULT parameter)

Hi @andreyzher
Thank you highlighting this and providing a potential solution.
I am hoping that the PR will be raised and pushed into devel later today.
Many thanks
Mark

@andreyzher
With the new devel branch does this now resolve your issue?
Thanks
uk-bolly


make-list-default-element -> default-values

Why not include the defaults for strings, vectors and bytevectors?
There are some pretty interesting cases in the table...

Thank you for the thorough work! Looks good to me.


[Feature Request] Add event when slider value is reset due to invalid value

Existing Component
Yes
Component Name
Slider
Description
When providing a slider with input, if the user types an invalid value into the input, the value gets reset without any warning. We'd like to show some kind of hint as why the value gets reset so the user is not confused. Would you be able to provide an event hook with the reset reason?
Example scenario: I have a slider with minimum value of 1000 and maximum value of 10000, and step set to 1000. The initial value of the input is 1000. User tries to change the value by hitting backspace on the number input, but as soon as the value is changed to 100, it restores itself to 1000. This looks like a buggy experience, and we'd like to let the user know why this is happening.

In this case, I think it's better to tell users about the minimum and maximum value on the UI (a label or hint), so they can get it right at first attempt, instead of correcting them when things goes wrong (they still have to input the correct thing afterwards).

Thanks, that makes sense, but I still wonder if it's the right experience for users who are just trying to clear and type in the right value. e.g. I know the minimum value is 1000 and I'd like to type in 2000, but as soon as I start backspacing to delete the current value, it resets itself without giving me the chance to type in the correct value.

@jiayexie
In my opinion, although the component gives users the chance to manually fix the invalid value, they may still forget to do it.
As @wacky6 said, the better way is clearly to tell users the min and max value on the UI.


Issue with Necropolis overlay

I managed to setup the overlay on the screen-checks section and the tests work well, but when I activate the necropolis mode the overlay just doesn't work.
When I try to change settings on the Necropolis section it gives me a message to "open the overlay before changing settings" regardless of the Necropolis panel being on the screen
Is there anything I am doing wrong?

Screenshot for reference

The "overlay" and the in-game panel are two different things. You generally open the in-game panel, tap the omni-key (default: middle mouse-button), and then the "overlay" opens.

Hey, thanks for the quick reply and for making this amazing tool available.
I am aware of the overlay being a separate thing but in this case I can't make it work while the lantern menu is on the screen. I have already tried to rebind the omni-key but the overlay just doesn't work even though I do get a positive response on the calibration/test.
Other functions such as the item tooltip also work just fine when I press the omni-key

Then it's probably the gamescreen pixel-check. Make sure you close every in-game UI, set the minimap to centered/overlay mode, then recalibrate the pixel-check.
The omni-key isn't searching for the lantern UI because it "thinks" you're on the gamescreen, controlling your character, so it doesn't even attempt to activate the necropolis feature.

I tried to recalibrate the gamescreen check but I still get the same issue.
When I test the active pixel-check while the lantern menu is open I get negative as a result, while the lantern test is positive. If I close the lantern menu and do the same thing I get both the other way around.
Weird thing is that I was able to set up the TLDR overlay just fine

Hmm, I guess we have to test if different features where the omni-key works exactly the same, so gamescreen pixel-check -> feature image-check -> activate feature. That would be Betrayal-Info and the skilltree overlay in the leveling tracker.
Could you enable the leveling tracker, set up the skilltree image-check, then hold the omni-key while the skilltree is open? There will be an error message saying that image-files could not be found (or, if you have used that feature before, the overlay will open).
Other than that, what is your screen-setup? Do you use multiple monitors? What's the game's resolution, and is it running in windowed fullscreen or a different configuration?

There's a slight possibility that the tool can't correctly tell how/why the omni-key is pressed.

One thing that could be the issue is the clipboard. Could you copy a random word/text into clipboard, tab back into the game, press the omni-key while not hovering over an item, then paste the clipboard somewhere? I need to know if the clipboard is blank after pressing the omni-key. If it's not blank, the tool thinks you're pressing the omni-key on items every time.

Have you changed anything in the tool's hotkey section? You mentioned that you had rebound the omni-key.

Another thing you could try is this: There is a work-around for people who have rebound the c-key in game. They need to "create" a secondary omni-key for item-related features. It's an option in the hotkeys section (can't check right now what it's called, something with c-key and character screen). For testing purposes, you can bind the secondary omni-key to an F-Key. We need to check if removing item-related checks from the original omni-key fixes your issue.

I can't explain how, but it is working now
I tried to reconfigure everything before I read your last message, so I didn`t try any of your latest suggestions.
What I did do was the following: I restarted everything, set a new omni-key, recalibrated the pixel check and the lantern check, etc), almost like a fresh new setup.
My guess is that  there was an issue with the omni-key I was using before. I noticed there was something weird with the one I was using when I was setting up the TLDR function. I accidentally pressed the omni-key while I was setting up the hotkey for TLDR and noticed that the input from pressing the omni-key was actually 2 characters (the input was showing up as something like " -© " instead of just " - "). I don't understand why this was happening but the important thing is that it is working now
I would like to thank you very much for your support. If you have any link for donations please share with me because I would like to express my gratitude with a tip (wont be much because my currency is worth nothing, but some is better than none I guess). I looke

I'm glad this issue could be resolved.
I'm currently not taking donations, but that may change in the future. I certainly appreciate the gesture very much.
Just keep using my tool if you find it helpful and recommend it to others if you think it might help them. Maybe there will be a donation button within the tool or on the GitHub page in the future, so you can tip me then if you still feel like it.


Add parameter for driver pod name

Add parameter for driver pod name. #252

This could be handy. One question: IIRC the reason of appending timestamps to driver pod name (as well as the driver service name, we use the same for them) is because pod/service names must be unique within the same k8s namespace and we want to avoid conflictions. So should we check if there is already a pod/service with the same name before launching the driver pod?

If pod name is exist, k8s API server will return error for spark-submit, such as:
Exception in thread "main" io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://test.k8s:6443/api/v1/namespaces/dbyin/pods. Message: pods "spark-pi-001" already exists. Received status: Status(apiVersion=v1, code=409, details=StatusDetails(causes=[], group=null, kind=pods, name=spark-pi-001, retryAfterSeconds=null, additionalProperties={}), kind=Status, message=pods "spark-pi-001" already exists, metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=AlreadyExists, status=Failure, additionalProperties={}).
...

I think this is what we expect. Of course, we can check it before create driver pod, but I think it's unnecessary, k8s API server do this is better when creating pod.

The parameter is currently marked internal in config.scala.
We should probably mark that as not being internal and add documentation if we want to expose it to the user.
  private[spark] val KUBERNETES_DRIVER_POD_NAME =
    ConfigBuilder("spark.kubernetes.driver.pod.name")
      .doc("Name of the driver pod.")
      .internal()
      .stringConf
      .createOptional

Also would need to be added here: https://github.com/apache-spark-on-k8s/spark/blob/branch-2.1-kubernetes/docs/running-on-kubernetes.md#spark-properties

@foxish @lins05 Some updates, PTAL.

LGTM. @lins05/@ash211 any comments?


Add cmake commands and use genhlc to generate HLC as separate step

Signed-off-by: Jeffrey Elms<EMAIL_ADDRESS>

Marking as WIP as it depends on SymbiFlow/vtr-verilog-to-routing#1

LGTM when we land the genhlc command into conda -- I think it should be maybe something like vpr-hlc or something though?

I think we can switch over, but our VPR fork needs to rename current master to something else and then pull in https://github.com/elmsfu/vtr-verilog-to-routing/tree/hlc_min_rebase as the  master. Any objections @litghost @mithro ?
I don't have permissions to do the branch work on our vpr fork.

@elmsfu This is all done now right?


minor improvements

use smaller, faster images for radius test harness
docs: show current duoauthproxy version in readme

https://app.wercker.com/#build/5532d388df510a294a0573d0 and https://circleci.com/gh/jumanjihouse/docker-duoauthproxy/5 are clean.
:ship:


openssl doesn't download intermediate certificate

i open issues in nodejs https://github.com/nodejs/node/issues/16336 maybe need to fix  it in openssl
this site  https://incomplete-chain.badssl.com/ configured without intermediate certificate.
In Google Chrome it work well. because Google Chrome does download the intermediate certificate. Now, the problem is, that since Chrome is by far the most popular browser, website owners configure their website to work in Chrome.
error with openssl  (unable to verify the first certificate)
$ openssl s_client -servername incomplete-chain.badssl.com -connect incomplete-chain.badssl.com:443
output
...
Verify return code: 21 (unable to verify the first certificate)

in .net framework is work well.
example: https://dotnetfiddle.net/Th5M0c (c#)
in curl (base openssl) have error:
curl "https://incomplete-chain.badssl.com/"

curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
More details here: http://curl.haxx.se/docs/sslcerts.html

All errors occur because there is no  intermediate certificate.
I download certificate from website incomplete-chain.badssl.com
$ echo -n | openssl s_client -servername incomplete-chain.badssl.com  -connect incomplete-chain.badssl.com:443 | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > incomplete-chain.badssl.com.crt
I see the details
$ openssl x509 -in incomplete-chain.badssl.com.crt -text -noout
Certificate:
...
    Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA
        Validity
...
            Authority Information Access:
                OCSP - URI:http://ocsp.digicert.com
                CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt

            X509v3 Basic Constraints: critical
....

in first certificate have link to intermediate certificate.
 CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt
I guess. Google Chrome. or .net framework. download this intermediate certificate. and check it.
openssl no download it.
today all major browser download intermediate certificate. chrome, edge , filefox ,explorer.
i checked it with wireshark.
in chrome or edge in windows fetch from link with  this headers
GET /DigiCertSHA2SecureServerCA.crt HTTP/1.1
Connection: Keep-Alive
Accept: */*
User-Agent: Microsoft-CryptoAPI/10.0
Host: cacerts.digicert.com

in chrome on linux
GET /DigiCertSHA2SecureServerCA.crt HTTP/1.1
Host: cacerts.digicert.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36
Accept-Encoding: gzip, deflate

this is url http://cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt

What about openssl s_client, it being "the application", should it handle the intermediate certificates?

Openssl commands are fairly simple tools, not designed to be full fledged http solutions. There are plenty of others that are more feature complete, such as curl, links,...
So s_client currently requires all applicable certificates to exist in a local store. Like is already said above, that could change, but it's not our top priority.

Maybe should add more doc for this.

Hi! Sorry if this is necro-posting, but since the problem is really common, I would like to share my suggestions.
On one hand I agree that OpenSSL should not auto-request intermediate certificates - it is beyond direct responsibility to validate the cert. But on the other hand, it's still OpenSSL's scope to know about root CA's. In other words, it's still OpenSSL who somehow accesses CA-storage, so it could validate the certificate.
Though I'm not really aware of OpenSSL internals, to me the problem here is that the resolution of a parent certificate is tightly coupled to filesystem-storage. In other words, it's not possible to have different certificate resolution mechanisms. But OpenSSL could abstract from this process. Filesystem could be only one of such exact mechanisms. Other mechanisms can either ship with OpenSSL itself, or be externally supplied as arguments, provided they implement an established interface.


[Event Request] codeunit 5880 "Phys. Invt. Order-Finish" OnCreateReservEntriesOnAfterTempPhysInvtTrackingBufferModify

The Publisher OnCreateReservEntriesOnAfterTempPhysInvtTrackingBufferModify requires a var for the parameter MaxQtyToTransfer.
    [IntegrationEvent(false, false)]
    local procedure OnCreateReservEntriesOnAfterTempPhysInvtTrackingBufferModify(AllBufferLines: Boolean; var MaxQtyToTransfer: Decimal; QtyToTransfer: Decimal)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.