Install ios-webkit-debug-proxy

Hi, when I try to install ios-webkit-debug-proxy I'm getting this error
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\Ricardo> scoop install ios-webkit-debug-proxy
Installing 'ios-webkit-debug-proxy' (1.8).
Linking ~\scoop\apps\ios-webkit-debug-proxy\current => ~\scoop\apps\ios-webkit-debug-proxy\1.8
Creating shim for 'ios_webkit_debug_proxy'.
Can't shim 'ios_webkit_debug_proxy.exe': File doesn't exist.
PS C:\Users\Ricardo>

The instructions I followed were
scoop bucket add extras
scoop install ios-webkit-debug-proxy

The first command worked okay.
After running scoop install ios-webkit-debug-proxy I noticed that the folders 1.8 and current inside scoop\apps\ios-webkit-debug-proxy are empty.
Can anyone help me installing this kit?
Thanks in advance.

Sorted :)
https://github.com/lukesampson/scoop-extras/issues/678


fix simple channel: return on push when cancelled

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (master@003cb1c). Learn more about missing BASE report.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##             master     #315   +/-   ##
=========================================
  Coverage          ?   77.79%
=========================================
  Files             ?      108
  Lines             ?     8115
  Branches          ?        0
=========================================
  Hits              ?     6313
  Misses            ?     1802
  Partials          ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Chunk Borders and SEUS Shaders

Mod Version:
DynamicSurroundings-1.12.2-<IP_ADDRESS>
Forge Version:
forge-1.12.2-<IP_ADDRESS>78
Link to crash log (if applicable):
No Crash
Description:
Using SEUS Shaders and preview_OptiFine_1.12.2_HD_U_D3_pre the Chunk Borders are not shown

You mean F9?  That is actually Minecraft code.  All DS does it turn it on/off.

i'll try and upload some images, yes the thing that says [Dynamic Surroundings] Chunk Border Display ON/OFF
at certain angles the border lines appear, and most times they dont
The MoreOverlays mod works ok - prefer everything in one mod like DS

http://ni750123-1.web18.nitrado.hosting/2018-05-05_14.51.25.png
http://ni750123-1.web18.nitrado.hosting/2018-05-05_14.51.33.png
http://ni750123-1.web18.nitrado.hosting/2018-05-05_14.51.40.png

Understand.  But my point is that it is Minecraft that is doing the rendering, not Dynamic Surroundings.  The chunk border fencing is a debug tool built into Minecraft.  All DS does is turn the fencing on/off at a keypress.

well I got 4 arguments for it

It keeps it all in 1 mod
It would be Shaders Compatible
It seems in keeping with the mod
You could link in with FTB and show different colours for claimed areas/loaded areas

but of course it depends on how difficult it is to write the code etc
just a thought


[#142503647] Monitor TLS Certificate Validity

What
We want a monitor that will alert us if any of our public-facing TLS certs are invalid, or due to expire soon.
paas-metrics is extended to accept a list of domains for which you want to check the validity of SSL certificates for, and emit metrics for the number of valid days remaining. This is done via environment variable:
TLS_DOMAINS=x.example.com,y.example.com

A datadog monitor is created to emit WARNINGs at < 7 days and critical alerts at < 1 day.
The metrics also catch some misconfigurations (like incorrect common name, untrusted CA) by marking the cert as invalid (0days validity).
We want these checks in staging too, so have removed the ENABLE_METRICS pipeline flag so that deployment is soley based on the ENABLE_DATADOG flag.
How to review

Code review
Deploy this branch to dev with ENABLE_DATADOG=true
Setup valid certs for your ELBs in aws console
Watch the datadog monitor

Additional
There is a sibling PR for the team-manual: https://github.com/alphagov/paas-team-manual/pull/171
Who can review
Not @chrisfarms
that can't review, because they worked on it.

Should deploy cleanly now... and resolved the grammer in readme.

I've been caught out again by the need to set SELF_UPDATE_PIPELINE=false :(


Add "^15.4.0-0" to compatible react peerDeps

In order to satisfy a prerelease version, the major/minor/patch versions must match exactly. This change makes react-redux yarn friendly when used with<EMAIL_ADDRESS>


Bulk validation fixes for col HTML tags

Docs Build status updates of commit a1a18df:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/SDN/articles/useragenttype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/via-element-startpropertiestype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'VGAQualityRatio element (QualityPropertiesType complexType)' is duplicated in: 'SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(2,8), SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(2,8)'. Titles must be unique within a docset.
Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'VGAQualityRatio element' is duplicated with other articles: 'SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(13,1), SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/useragenttype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/via-element-startpropertiestype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8ea3400:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/SDN/articles/useragenttype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/via-element-startpropertiestype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'VGAQualityRatio element (QualityPropertiesType complexType)' is duplicated in: 'SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(2,8), SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(2,8)'. Titles must be unique within a docset.
Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'VGAQualityRatio element' is duplicated with other articles: 'SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(13,1), SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/useragenttype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/via-element-startpropertiestype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit cd5fbe3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/SDN/articles/useragenttype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/via-element-startpropertiestype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'VGAQualityRatio element (QualityPropertiesType complexType)' is duplicated in: 'SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(2,8), SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(2,8)'. Titles must be unique within a docset.
Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'VGAQualityRatio element' is duplicated with other articles: 'SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(13,1), SDN/articles/vgaqualityratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/useragenttype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/via-element-startpropertiestype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Properly handle error codes when downloading the run artifact

This task is automatically imported from the old Task Issue Board and it was originally created by Michał Urbańczyk.
Original issue is here.

Fix on our side or in the octocrab.
The issue is that error code is not checked, just html streamed as zip.

This is handled by our fork of octocrab, was also fixed upstream.


remove tools/replay/unlog_ci_segment.py

This is still needed until the CI segments can be accessed with the Route class.


Fix test failure due to incorrect locale

Summary
The last 13 TerasologyLauncherPRs builds have not been stable due to a test failure, which was caused by an improper state of Languages.java before running the test. This PR fixes things by resetting the state of that class after running TestLanguages.java. It also fixes some test names in the same class.

Hooray Jenkins reported success with all tests good!


Fix AWS QueryPages backoff logic

Fixes part of #516 - continue would skip pages instead of backing off.
Also include maxRetries in the QueryPages retry logic.

Too clever for me in my current condition. Will look at tomorrow.


[AutoDiff] Add forward mode differentiation control flow support (conditionals)

Add support forward mode control flow differentiation: br and cond_br instructions.
Design is based on the pseudocode algorithm by @bartchr808.
Swift statements that are lowered to SIL instructions br and cond_br are now supported (e.g. if and guard statements).
Loops are not yet fully supported (for requires handling SIL switch_enum instruction).

Pseudocode algorithm and WIP code adapted from @bartchr808.

@swift-ci Please smoke test

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)

Added a Control flow support in forward-mode AD in Swift doc explaining this approach and its issues in a bit more detail. @saeta, @marcrasi, @dan-zheng


add SPIR-V version testing

This PR adds basic testing for each of the SPIR-V versions supported by an OpenCL device.  It queries which SPIR-V versions are supported (using CL_DEVICE_IL_VERSION), and then compiles a SPIR-V program and executes a simple kernel for each of the reported versions.  Note that none of the new features for each SPIR-V version are tested, but this PR does include infrastructure that could be (and hopefully will be!) used to add targeted testing for version-specific SPIR-V features in the future.
fixes #1069
see also #1639

@bashbaug, could you please offer run command for added tests? I am not familiar with CTS and having a try to verify it on intel OCL CPURT. Thanks very much.
[haonanya@ spirv_new]$  ./test_spirv_new basic_versions
Reading SPIR-V files from default 'spirv_bin' path.
In case you want to set other directory use '--spirv-binaries-path' argument.
To skip the SPIR-V version check use the '--skip-spirv-version-check' argument.
Initializing random seed to 0.
Requesting Default device based on command line for platform index 0 and device index 0
Compute Device Name = Intel(R) FPGA Emulation Device, Compute Device Vendor = Intel(R) Corporation, Compute Device Version = OpenCL 1.2 , CL C Version = OpenCL C 1.2
Supports single precision denormals: YES
sizeof( void*) = 8  (host)
sizeof( void*) = 8  (device)
This device supports SPIR-V offline compilation. SPIR-V version is 1.4
basic_versions...
testing SPIR-V_1.0...
File spirv_bin//basic.spv64 not found
File /basic not found
ERROR: Unable to build SPIR-V program! (CL_DEVICE_NOT_FOUND from /export/users/haonanya/OpenCLCTS/OpenCL-CTS/test_conformance/spirv_new/test_basic_versions.cpp:92)
basic_versions FAILED
PASSED sub-test.
FAILED test.

Sure - I always forget how to do this so I have a text file with my notes.  Here's what I do:
Step 1: Build the spirv_new tests:
make -j20 test_spirv_new

Step 2: Assemble SPIR-V files:
This needs to be done once, or whenever SPIR-V files are added.
pushd ../test_conformance/spirv_new/ && python3 ./assemble_spirv.py && popd

Step 3: Run the tests:
Be sure to point to the SPIR-V binaries!
./test_conformance/spirv_new/test_spirv_new --spirv-binaries-path ../test_conformance/spirv_new/spirv_bin/

I'd like to add more testing for newer SPIR-V features and I'm going to need some of this infrastructure, so adding "focused review".

basic_versions

Thank you @bashbaug! Test pass with intel OCL CPURT. Is supported SPIRV-V version is up to 1.4 according to https://github.com/KhronosGroup/SPIRV-LLVM-Translator/blob/main/docs/SPIRVVersionsAndExtensionsHandling.rst?plain=1#L68? Thanks very much.


Brfryeet patch 1

a URL of a page on the official website where a long-term (>1 year) IT related course is offered by the university https://www.ibo.org/programmes/diploma-programme/curriculum/sciences/computer-science/ <-- long Trail is an IB school, but its curricula are not publicly available online
a URL of a page or some other proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the enrolled students. <-- They are pretty reticent about student emails on the public web site, but they do document that faculty emails are in the domain at https://www.longtrailschool.org/77448-2/

@brfryeet First stage of verification passed, official domain is longtrailschool.org as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@brfryeet Thank you for your patience while waiting for a review and processing your request. Pull request merged.

Thanks, Philip! You're the best.


Impelment GraphML for DiGraph

Contributor Checklist

[ ] Did you add Scaladoc to every public function/method?
[ ] Did you update the FIRRTL spec to include every new feature/behavior?
[x] Did you add at least one test demonstrating the PR?
[x] Did you delete any extraneous printlns/debugging code?
[ ] Did you specify the type of improvement?
[x] Did you state the API impact?
[x] Did you specify the code generation impact?
[ ] Did you request a desired merge strategy?
[ ] Did you add text to be included in the Release Notes for this change?

Type of Improvement

new feature/API

API Impact
Extends API of DiGraph, if T implements trait of GraphMLVertex, it is can emit a GraphML string with toGraphML
Desired Merge Strategy
Release Notes
Add GraphML generation
Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (1.2.x, 1.3.0, 1.4.0) ?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you mark as Please Merge?

Sure, working on it.


Update Composer dependencies (2021-01-07-00-04)

Visual regression test passed!
View the visual regression test report

Visual regression test passed!
View the visual regression test report


Upgrade php 5.3 -> 5.4 memory issue (cache related)

After upgrading from PHP 5.3 to PHP 5.4 vice versa, SilverStripe generates an out-of-memory error, that can be fixed by doing a /dev/build?flush=1 or by emptying the cache by hand. Versions 3.1.2 and 3.1.3. Happened on a nix hosting platform and can be reproduced on MAMP.
Not so much of an issue if only you know in advance. Unfortunately I'm not fluent enough to come up with an answer nor where it comes from, SilverStripe or Zend.

I got the same problem today after upgrading from php 5.5 to php 5.6, while using SilverStripe 3.1.8. All 7 sites on my server displayed the out-of-memory error (in Core.php I believe), which I could solve for 4 by flushing, and for the other 3 I had to manually delete the cache folder (because flushing didn't work).
Could we please invalidate all cache when a major php upgrade is detected?
(or perhaps dig into which single piece needs to be invalidated, but I'm sure it wouldn't hurt to just remove the whole cache folder's contents to be sure)

I'm leaning towards agreeing with @stevie-mayhew. Detecting major upgrades (or any upgrade) of PHP seems like a lot of work to protect against an edge case.
Production environments should be stable and rarely the subject of upgrades.
I acknowledge that with shared hosting you rarely get any warning or, if you do, you definitely have no specific time for when it'll happen but that's the compromise you make when you get shared hosting over a stand-alone server (be it Virtual or not).

It wouldn't be that hard to include the PHP version in the name of the default cache directory, like the UID already is. I sometimes run into this when testing in 5.3 & 5.4 on my dev machine, and currently solve it by just constantly rm -rf silverstripe-cache which can get pretty annoying.

I like @hafriedlander 's idea! So I went ahead and implemented it.

Fixed with #3882 https://github.com/silverstripe/silverstripe-framework/commit/047fe3a410624f34d617e4577669c4c7db52613b


docs($http): specifies that url is the cache key

When using a custom cache, it may be handy to clear some cached data. For instance, when you have a sequence of GET, POST and then GET on the same URL, the second GET must not use a cached data. Using a custom cache object from $cacheFactory, cached data can be cleared with myCache.remove(url).
This works but uses an undocumented feature: the fact that $http use the required url as cache key. This change specifies that point.
Hope this helps

Mon company (HP) has a corporate agreement. My work address is dominique.dumont at hp.com

As far as I understand the code, the url passed to $http() or $http.get() is not the actual key of the cache. The key is the url of the config followed by the query string built from the parameters:
var url = buildUrl(config.url, config.paramSerializer(config.params));

So I think the suggested addition would make things more confusing: readers might fear that parameters are not taken into account, or might expect a cached response to be evicted if they don't take parameters into account.

So, if I understand correctly, there's no simple way to clean up the cache passed to $http.get except by calling removeAll() (which clean all cache entries instead of just one).
Is this assessment correct ?

@dod38fr, there is indeed no simple way to know the key if you are using query parameters.
It's not super complex or impossible to build the key yourself (you have all necessary pieces (url, params, paramSerializer) and the implementation of buildUrl() is really simple), but I definitely wouldn't recommend it.
Depending on your usecase, you might be able to create a very simple wrapper around a cache that does what you want.

BTW, I agree with @jnizet - the suggested docs addition is inaccurate and could prove misleading.

@gkalpak , the use case is: I have a remote storage that I mostly read from and sometimes write to. When I write to this remote storage, the next read should contain the data that was just written.
This is currently not possible using the simple cache facility provided by $http.
BTW, I agree with both of you. The doc modif I suggest is not good currently. I'll amend it or close this PR.
I just wish there was a simple way to know the cache key used by $http. Would it be possible to modify $http to provide this cache key in the then callback ? With this information, managing the cache content would then be possible.

There are several ways to achieve the same I guess, but off the top of my head, I would try something that.
(I.e. augment the cache used by $http to store the key somewhere.)

There's also a more simple (even if more resource consuming) way: use one cache object per API endpoint and use removeAll on this object when the cache needs to be flushed.
This avoid adding more complexity in my project for a problem that should be handled by AngularJS framework.
I agree that the augment trick may not be much by itself, but it adds up with other workarounds and make on-boarding of new developers much more difficult.

Ok, it looks like the docs changes are not really correct. I am gonna close this then. Still, @dod38fr, thanks for contribution - you can open a new issue that addresses the problem with getting the cache key and / or another PR that correctly explains what the cache key is for $http is.


Laravel 11 compatibility

Laravel 11 depends on "symfony/mime": ^7.0 however the Mailtrap package currently only supports ^5.0|^6.0.
I have only very briefly tested a fork updating to ^7.0 which seems to work as expected with only some type setting needed.
https://github.com/railsware/mailtrap-php/compare/main...hempsworth:mailtrap-php:main
It will need more testing, but hopefully, this helps somebody upgrading to Laravel 11!

@hempsworth Thank you for the feedback.
We will check and release a new release soon


deliverLatestCacheToView delivers all previously emitted items

RxTiPresenterUtils.deliverLatestCacheToView caches and re-delivers all items emitted by the source.
Look at this log output. When the view is detached, several items are emitted by the source, but not delivered. This is correct so far.
After the view is reattached, all of the items are delivered again, including those which had already been delivered (c9915aa) and those which should have been dropped (6b60904).
11-02 12:45:45.392 D: Emitting c9915aa
11-02 12:45:45.421 I: Delivering c9915aa
11-02 12:46:02.199 D: Emitting 75d8118
11-02 12:46:02.210 I: Delivering 75d8118
11-02 12:46:02.211 D: Emitting a0e7956
11-02 12:46:02.255 I: Delivering a0e7956

VIEW DETACHED

11-02 12:46:44.932 D: Emitting 6b60904
11-02 12:46:45.052 D: Emitting 27a3122
11-02 12:46:45.668 D: Emitting 50cb170
11-02 12:46:45.682 D: Emitting 1ae3d6e
11-02 12:46:46.478 D: Emitting efbdc0f
11-02 12:46:46.493 D: Emitting b085ea5

VIEW REATTACHED

11-02 12:47:09.806 I: Delivering c9915aa
11-02 12:47:09.807 I: Delivering 75d8118
11-02 12:47:09.807 I: Delivering a0e7956
11-02 12:47:09.808 I: Delivering 6b60904
11-02 12:47:09.809 I: Delivering 27a3122
11-02 12:47:09.809 I: Delivering 50cb170
11-02 12:47:09.810 I: Delivering 1ae3d6e
11-02 12:47:09.811 I: Delivering efbdc0f
11-02 12:47:09.812 I: Delivering b085ea5
11-02 12:47:15.458 D: Emitting 4cdffd
11-02 12:47:15.459 I: Delivering 4cdffd

Here is the code:
val subscription =
        Observable.just(/* some object */)
                .doOnNext { c -> Timber.d("Emitting %x".format(c.hashCode())) }
                .delaySubscription(5, TimeUnit.SECONDS)
                .subscribeOn(Schedulers.io())
                .observeOn(AndroidSchedulers.mainThread())
                .compose(RxTiPresenterUtils.deliverLatestCacheToView<Object>(this))
                .subscribe { c ->
                    Timber.i("Delivering %x".format(c.hashCode()))
                    view.showData(c)
                }
rxHelper.manageSubscription(subscription)

Is this the expected behaviour?

There is similar strange behaviour with deliverLatestToView (the variant without the caching).
Again, this delivers all of the items which should have been dropped while the view was detached, but it delivers them in a different order. Is this a threading bug?
11-02 13:53:57.080 D: Emitting 21ea0e8
11-02 13:53:57.086 D: Emitting 207a5a6
11-02 13:53:57.956 D: Emitting 1b0e394
11-02 13:53:57.973 D: Emitting 9f87632
11-02 13:53:58.746 D: Emitting 182a500
11-02 13:53:58.759 D: Emitting 3b3c37e
11-02 13:54:06.459 I: Delivering 21ea0e8
11-02 13:54:06.460 I: Delivering 1b0e394
11-02 13:54:06.461 I: Delivering 182a500
11-02 13:54:06.462 I: Delivering 207a5a6
11-02 13:54:06.463 I: Delivering 3b3c37e

The deliverLatestCacheToView behavior is correct. All items, including the already delivered ones will be emitted again.
Can you post the code for your deliverLatestToView example. These must be multiple Observables because deliverLatestToView emits only the latest item. Neither the Observables nor the operators know each other. The order between emissions of different Observables cannot be guaranteed.

If the cache behaviour is intentional, then I think it doesn't match the documentation:

If the transformer receives a next value while the previous value has not been delivered, the previous value will be dropped.

You are right about the deliverLatestToView variant. There were multiple Observables involved - sorry for the noise. :)

[ ] update documentation


Cannot register any adapters.

This error happens before I even create a polly instance. When I'm just registering adapters...

Unfortunately, my stack trace and sourcemaps are worthless because webpack, karma, and typescript are apparently not friends with each other...
So, with no registered adapters, I can create a Polly instance.
  import { Polly } from '@pollyjs/core';
// import XHRAdapter from '@pollyjs/adapter-xhr';
import FetchAdapter from '@pollyjs/adapter-fetch';

// Polly.register(XHRAdapter);
// Polly.register(FetchAdapter);

// creating poly instance omitted, because it doesn't matter here :)

When I try to register an adapter, I get an error:
  import { Polly } from '@pollyjs/core';
// import XHRAdapter from '@pollyjs/adapter-xhr';
import FetchAdapter from '@pollyjs/adapter-fetch';

// Polly.register(XHRAdapter);
Polly.register(FetchAdapter);

// creating poly instance omitted, because it doesn't matter here :)

This error happens when I don't even specify what adapters to use in the configuration object. (adapters: []);
So, I think this may be a problem with register?

Ok, here is the problem.
apparently the adapter I'm passing to register is undefined..

makes me wonder if this is a weird behavior with however the core module is built and how it interacts with typescript.

Yup, that was it.

code to discover this:
import FetchAdapter from '@pollyjs/adapter-fetch';
import * as FA from '@pollyjs/adapter-fetch';

console.log('Fetch Adapter default: ', FetchAdapter);
console.log('Fetch Adapter *: ', FA);

ok, so here is the working adapter registration.
import { Polly } from '@pollyjs/core';
import * as XHRAdapter from '@pollyjs/adapter-xhr';
import * as FetchAdapter from '@pollyjs/adapter-fetch';

/*
  Register the adapters and persisters we want to use. This way all future
  polly instances can access them by name.
*/
Polly.register(XHRAdapter);
Polly.register(FetchAdapter);

// inspiration from:
// https://github.com/Netflix/pollyjs/blob/master/packages/%40pollyjs/core/src/test-helpers/mocha.js
export function setupRequestInterceptor(config: any = {}) {
  beforeEach(function() {
    const name = generateRecordingName(this);
    const pollyConfig = {
      mode: 'passthrough',
      adapters: ['fetch', 'xhr'],
      logging: true,
      recordIfMissing: false,
      matchRequestBy: {
        order: false,
        url: {
          port: false,
          hostname: false,
          protocol: false,
        }
      },
      ...config
    };

    this.polly = new Polly(name, pollyConfig);

    const { server } = this.polly;
    // ...

This turned out to be an issue with Typescript and ambient modules. :-\


fix: remove kubectl from Dockefile

This isn't used by flux-local

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.77%. Comparing base (05de0c9) to head (c8eacad).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #822   +/-   ##
=======================================
  Coverage   93.77%   93.77%
=======================================
  Files          21       21
  Lines        2314     2314
=======================================
  Hits         2170     2170
  Misses        144      144

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fix: modal not allowing for internal scrolling

fix: modal not allowing for internal scrolling
fix: formatting
docs: changeset

#136  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @kylemcd and the rest of your teammates on  Graphite


Index changes 5

OPS Build status updates of commit 5a50e6d:
:clock10: Preparing: average preparing time is 38 sec(s)

OPS Build status updates of commit 5a50e6d:
:clock10: Incremental building: average incremental building time is 19 sec(s)

OPS Build status updates of commit 5a50e6d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

enterprise-graph/index.yml
:warning:Warning

Details

enterprise-graph/index.yml

[Warning] Author Stephen Flanagan cannot be recognized in GitHub.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Schema] Add metalink mode to hashmode

Schema is missing property for metalink
See: https://github.com/lukesampson/scoop/blob/57b0b0e1eb2c946ca74541b2464d3e61e195e979/lib/autoupdate.ps1#L213-L218

Also added sourceforge and fosshub, and matched their code to follow others.


Docs site contains inconsistent references to both flk and bud

I haven't yet got up and running with DevOS, and part of the reason for that was some contradictions in the documentation site.
For example, "Quick Start" references the core branch and flk, while the next "ISO" page references bud, and the "From NixOS" page after that refers to flk again.
Discussed in https://github.com/divnix/devos/discussions/361

Originally posted by cwhy September 14, 2021
Hi I am new to NixOS and want to try a friendly setup. I am quite confused at this page, which is a essential page for setup the system: https://devos.divnix.com/start/iso.html. The page requires me to install bud but I see no documentation for how to install bud from https://devos.divnix.com/bud/index.html or the repo.
Any help?
Thanks~

I would gladly open a pull request, but I'm not sure how to proceed – is there a guide somewhere for the project's branching/release workflow? Is the guide (on GitHub Pages) supposed to reference the state of things on core or master?

Very sorry about this. The DevOS docs are getting to be quite stale and I haven't had time to update them. I thought we did away with core entirely. The latest state of development should be master.

It's all good, thanks for the clarification. For this particular thing on the quick start page, I can open a PR to update the reference if that would be helpful.

yes that'd be great, documentation PRs are greatly appreciated :slightly_smiling_face: