Unnecessary dependency on OpenCV

I'm trying to export a non-image spark dataset to the petastorm format, and when I import the petastorm codecs, I get this:
~/.conda/envs/stb2/lib/python3.5/site-packages/petastorm/codecs.py in <module>()
     25 from io import BytesIO
     26
---> 27 import cv2
     28 import numpy as np
     29 from pyspark.sql.types import BinaryType, LongType, IntegerType, ShortType, ByteType, StringType

ImportError: No module named 'cv2'

It doesn't make sense to keep opencv as a dependency, it seems unnecessary.

So we actually define opencv as an extra dependency in the setup.py however you are correct that it isnt really extra since we force it as a dependency (we mainly defined it as extra in case people want to install older versions as a debian package instead of through pip).


[1.3] RVC RUN Mode Cluster XML has to be updated as per spec

Description:

[ ]  "OnMode"  is OnOff Feature dependent attribute. This feature is marked as X in conformance. (X means -   This is disallowed for the cluster derivation),  but it is reflecting in XML file.

Screenshot:

Spec Reference:
https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/device_types/RoboticVacuumCleaner.adoc#element-requirements
XML Reference:
https://github.com/project-chip/connectedhomeip/blob/master/src/app/zap-templates/zcl/data-model/chip/rvc-run-mode-cluster.xml

@Ashwinigrl The text above does not match the screenshot.... Which is correct?

The required change in the spec to address this issue was made in this PR.
The required changes to the SDK following this spec change PR are tracked by this issue.


Port parallel LU benchmark from OCaml's Sandmark benchmark suite

Does this benchmark do anything interesting memory wise?

Closing it since it has a fairly small GC percentage. We can re-open in in the future if needed.


Change default sort order

This PR changes the default sort order to be descending.  This means that when viewing metrics they are shown from highest values to lowest by default.
This is however problematic as the initially selected 'order by' is for the name (of the dept or service). We want to view the names in alphabetical order by default, unalphabetical is just weird.  If we default to ascending here then it will be carried across to the metrics when the user changes a different field to order by. This would enforce ordering by ascending value, which isn't what we want.
Having checked that sort by name is required (via a detour in 74a6a76
which removed the option) , we now treat name as with all the metrics, but reverse it at the last second before use in the presenter.

I've reworked it a little to make sure we only reverse at most once, and hopefully it's a little clearer.


ENH: get coordinates + offset arrays for "ragged array" representation

Context: the "spatialpandas" project is trying to define a representation of geometries based on "ragged arrays" (nested arrays where subarrays can have varying length). This can give a representation of geometries that is independent of GEOS, and can have a faster access to the coordinates (as the coordinates of all geometries are stored as a flat array). The driving use case for this is in the datashader project (https://github.com/pyviz/datashader/), that is adding support for plotting polygons and other geometry types. Datashader is especially targetting visualizing big datasets, and then fast access to the coordinates is important.
@jonmmease is implementing such a "ragged array" representation in https://github.com/jonmmease/spatialpandas/pull/2 (pandas ExtensionArrays (to store it in a dataframe) based on pyarrow's ListArrays). I am partly involved in that effort in giving feedback from a geopandas viewpoint (also for visualizing large geodataframes, datashader can be a very interesting approach).
PyGEOS is of course tied to GEOS, and other representations as described above are clearly out of scope.
But, I think it would be useful to have a fast conversion from a GEOS-based representation to such a "flat array + offsets"-based representation. And to have such conversion fast, it is probably easiest to have this live in PyGEOS (or at least provide all necessary building blocks to construct it).
We already have a pygeos.get_coordinates, which gives you access to the flat coordinates array, but in addition to that we would also need functionality to build up the offsets arrays.
Below follows an example of how to create such a "flat array + offsets" representation with the current pygeos API for the countries dataset of geopandas (mixture of polygon and multipolygons, but I first convert them to all multipolygons):
import geopandas
import shapely.geometry
import pygeos

def ensure_multipolygon(geom):
    if isinstance(geom, shapely.geometry.MultiPolygon):
        return geom
    elif isinstance(geom, shapely.geometry.Polygon):
        return shapely.geometry.MultiPolygon([geom])
    elif geom is None:
        return geom
    else:
        return ValueError

df = geopandas.read_file(geopandas.datasets.get_path('naturalearth_lowres'))

# create pygeos array with all MultiPolygons from geopandas/shapely
arr = pygeos.from_wkb([ensure_multipolygon(geom).wkb for geom in df.geometry])

# the flat array of coordinates
coords = pygeos.get_coordinates(arr)
coords_flat = coords.ravel()

# the offsets into the multipolygon parts
offsets1 = np.insert(pygeos.get_num_geometries(arr).cumsum(), 0, 0)

# the offsets into the exterio/interior rings of the multipolygon parts
def flatten_multipolygons(arr):
    res = []

    for geom in arr:
        for i in range(pygeos.get_num_geometries(geom)):
            poly = pygeos.get_geometry(geom, i)
            res.append(poly)

    return np.array(res, dtype=object)

arr_flat = flatten_multipolygons(arr)
offsets2 = np.insert((1 + pygeos.get_num_interior_rings(arr_flat)).cumsum(), 0, 0)

# the offsets into the coordinates of the rings
def flatten_polygons(arr):
    res = []

    for poly in arr:
        res.append(pygeos.get_exterior_ring(poly))
        for i in range(pygeos.get_num_interior_rings(poly)):
            res.append(pygeos.get_interior_ring(poly, i))

    return np.array(res, dtype=object)

arr_flat2 = flatten_polygons(arr_flat)
offsets3 = np.insert(np.cumsum(pygeos.get_num_coordinates(arr_flat2)*2), 0, 0)

# flat array + offsets
(coords_flat, offsets3, offsets2, offsets1)

Some general notes / remarks:

Specifics of this representation / approach:

This only works with a uniform geometry type (as from the offsets you can't see which geometry type is being represented)
The number of offsets arrays (the level of nesting) depends on the geometry type. The MultiPolygons gives the most nested (3 levels: list of MultiPolygon parts -> each part has list of rings -> each ring has list of coordinates). But eg LineStrings would give 1 level of nesting.

It is already somewhat possible with the current APIs to get the number of geometries, of inner rings, of coordinates, .. (see the above code). But, currently we need to "explode" the array of MultiPolygons to use those APIs (which is probably a useful functionality anyway).
Right now this creates python overhead (as this flattening is done in python loops), but even if there were pygeos functions for it, would give the overhead of creating a full arrays of those multipolygon parts / linearrings, while it is not needed to created full arrays for them.
Having a dedicated function for it instead of providing the building blocks could also be done in a single pass over the geometries (or one pass to get the size of the arrays + one pass to fill in the arrays), instead of multiple passes for each of the flats coords arrays + offsets.

@jonmmease to convert the set of (coords_flat, offsets3, offsets2, offsets1) arrays produced by the above code efficiently into a pyarrow.ListArray (I think in your PR you only create such ListArray from actual nested python lists of lists arrays?), I didn't find a one liner for it. But with ListArray.from_arrays it is possible to create the different levels of nesting consecutively:
_parr3 = pa.ListArray.from_arrays(pa.array(offsets3), pa.array(coords_flat))
_parr2 = pa.ListArray.from_arrays(pa.array(offsets2), _parr3)
parr = pa.ListArray.from_arrays(pa.array(offsets1), _parr2)


Cal/display creation type

Blocked, I can no longer access the databases
api_1  | 225 static files copied to '/api/staticfiles', 695 post-processed.
api_1  | [2022-01-15 12:15:56 +0000] [105] [INFO] Starting gunicorn 20.1.0
api_1  | [2022-01-15 12:15:56 +0000] [105] [INFO] Listening at: http://<IP_ADDRESS>:8000 (105)
api_1  | [2022-01-15 12:15:56 +0000] [105] [INFO] Using worker: sync
api_1  | [2022-01-15 12:15:56 +0000] [107] [INFO] Booting worker with pid: 107
api_1  | [2022-01-15 12:15:56 +0000] [108] [INFO] Booting worker with pid: 108
api_1  | [2022-01-15 12:15:56 +0000] [109] [INFO] Booting worker with pid: 109
api_1  | Unauthorized: /api/scanreports/

ScanReports page is stuck on loading
Failed to load resource: the server responded with a status of 401 (Unauthorized)

Same with connections to model-test-db, as well as prod & dev db.

Could be my IP?
Could be an undocumented change needed in the .env file?


Type 'string[]' is missing the following properties from type '[string, string]': 0, 1

type A = [string, string]
type B = string[]

const a = ["a", "b"]

function test(a: A) { }
function test2(a: B) { }

//works
test([a[0],a[1]])

//error ; even if 'a' is [string, string]
test(a)

//works
test2(a)

error:
Type 'string[]' is missing the following properties from type '[string, string]': 0, 1
view on Typescript playground

The type of a is string[], not [string, string].  #3369
If you want a to be [string, string] you need to annotate it as such: const a: [string, string] = ["a", "b"].  Or use something like const assertions (which makes the tuple readonly as well, which you might not want here), etc.


logging out with draft boardings

If a user clicks 'Log Out' while they have draft boardings a modal should appear warning that drafts will be deleted - as per the design at https://mongodb.invisionapp.com/share/M6YN2Y77B8E#/screens/430515895_Modal-Logout

This should use the cascading delete function being added under https://github.com/WildAid/o-fish-android/issues/323

The customer has requested that drafts be able to be saved across mobile to web - that is, a SAVED draft boardings that hasn't been submitted, should NOT be deleted.
I apologize for the change in functionality; this reverses what we were told earlier.

closing; this is no longer an issue.


Wrong link on page "Promises benutzen"

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details
The "async/await" link at the end of the German MDN article "Using Promises" links to an English "queueMicrotasks" article instead of async/await. See this screenshot:

This is the wrong link:
❌ https://developer.mozilla.org/en-US/docs/Web/API/queueMicrotask
I used the English "Using Promises" page to find the correct link for async/await. This would be the correct link for the German version:
✔ https://developer.mozilla.org/de/docs/Web/JavaScript/Reference/Statements/async_function

Hi @Skasi! This repository (mdn/sprints) isn't really used to track MDN issues any longer. If this is still an issue, please scroll down to the "Found a content problem with this page?" section and use the "Report the content issue" link to report the issue on the appropriate repository (mdn/content) so that the appropriate team can resolve your issue quickly. Thank you in advance!


Avoid infinite loops from symlinks cycles

The semenatics of using kqueue are already slightly different than
inotify, specifically that inotify will give you events for the symlink
itself whereas kqueue will only give events for the target of the
symlink. This preserves that behaviour, that symlinks don't get notified
on, but ensures that circular symlinks don't recurse forever.
This change pushes the resolved filename up through the stack so that
the fileExists map can be properly populated; not doing so would mean
that deleting a cyclical symlink and then replacing it with a file of
the same name would not notify for that file's creation (or subsequent
events) because we would believe that the file already existed.

Fixes https://github.com/go-fsnotify/fsnotify/issues/96

I'm not sure why that second commit made the linux CI fail; none of the tests failed, and running the tests on a Linux machine I have they all pass and exit 0 :S

Thanks for the PR.
Regarding the Linux test failure, I've triggered a rebuild, so we'll see if Travis is just being flaky.

Merged as https://github.com/go-fsnotify/fsnotify/commit/2cdd39bd6129c6a49c74fb07fb9d77ba1271c572 and released as 1.2.5. Thanks!


Star models in the model list

For those of using openrouter, there are A LOT of models. Would be nice to favorite some of them and have them show up at the top of the list.

#53


Error Failed to import project

I set up everything like it is in docs and on screencast. I use Bitbacket. I push my docs that are built locally no problems to bitbuket. It is public repo I can see source as public user. I set up Service hook as well, but even if I trigger build manually it always gives me this error

I read FAQ but I am not sure i understand if suggestion

If you see ImportError messages for custom Python modules, you should enable the virtualenv feature in the Admin page of your project, which will install your project into a virtualenv, and allow you to specify a requirements.txt file for your project.

is correct for my case. And anyway there is not link to read about  requirements.txt configuration and how to configure it.

The suggestion won't help, as there is no ImportError thrown. This is failing on the initial checkout of your repository, which usually signifies a problem with the URL used for the project repo.
What's your project name?

What's your project name?

You mean in package.json?
ula-docs

No, you're RTD project name.

Pardon? RTD?

Your Read the Docs project name, I can't help any further without looking at the project configuration.

Unfortunately this issue was critical for me and I could not wait, so I use other solution now, but I wanted you to know for future customers.

I am with the same problem. @Serhioromano, you didn't show your project configuration for @agjohnson help us. And, what you did to solve the problem? @agjohnson, which file you need to see to help me? I am new with RTD.

I had this problem and the cause was a typo in the repo url. It appears that "Failed to import project" is returned for failed repo pulls. Makes sense in retrospect, but a more straightforward error message would help.

@leoheck

I am with the same problem. @Serhioromano, you didn't show your project configuration for @agjohnson help us

I had no longer that file by the time I was asked for it.
@leoheck

And, what you did to solve the problem?

I am using Mkdocs instead. Completely different solution.

@reece I need to know the name of, or link to, your project on RTD, to be able to see your configuration

@agjohnson I should have been clearer. I had the same error as the OP, but discovered that the cause was my own typo in the URL. When I fixed the typo, everything worked fine.
In my case at least, the only outstanding issue that "Failure to import project" is not as transparent as, say, "Could not clone or update repo from https://...".
While you're at it, you might offer a help message that suggests trying on the command line and including a copy-pastable command line (e.g., "git clone https://...").

Very good guys! Now you solved my problem. Thank you. I put my docs folder somewhere inide a repo and I though that I should all the path in link. I was wrong. Thank you.

@reece sorry, the above was meant to be in reply to @leoheck
agreed the messages could be clearer for this case though. i'll leave this open in case anyone wants to grab this.


[Bug] Read-only combo box is interactive

Interacting with a read-only combo box can make the selected empty. The data (selectedItem) is changed on the front end, however the source data is not impacted. The expected action is that users cannot interact with comboboxes etc when in read only mode

Adding this to blocked, couldn't reproduce the issue...

Not able to reproduce it here too.

we can't reproduce so this ticket can be closed


File change detection is flaky at times

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.2.0 (b3fe652 2022-04-17T23:07:33.947066+00:00)
What command(s) is the bug in?
forge test
Operating System
macOS (M1)
Describe the bug
Sometimes I will change a file and that edit is not picked up by forge test which will then not recompile that contract. I have no reliable way to reproduce this, but was asked to open as issue just to track :)

Ref https://github.com/foundry-rs/foundry/discussions/1299

And #1244 -- I think this is the very same problem.

Consolidated into https://github.com/foundry-rs/foundry/issues/1666


SiteURL

Commits on Apr 06, 2019
@MicahMcKittrick-MSFT
MicahMcKittrick-MSFT
SiteURL
Verified
16c7760
Unified Split
Showing  1 changed file  with 0 additions and 0 deletions.
BIN  articles/cloud-services/media/cloud-services-custom-domain-name-portal/5678.jpg

@MicahMcKittrick-MSFT : Thanks for your contribution! The author, @, has been notified to review your proposed change.

✌🏼

@eyzx7x, is the Subscription ID or any other information in the graphic personally identifiable info that needs to be replaced with a placeholder? Thanks.

Hi @jpconnock - As listed author of articles/cloud-services/cloud-services-custom-domain-name-portal.md, would you review this image submission? Note that per the internal cloud style guide, the subscription ID is private information that should be replaced with fictitious, agnostic, or placeholder content. Thanks!

@eyzx7x - Thanks for your contribution. The updates submitted in the PR appear to now be reflected in the current version of the article. We'll close this PR.


Wrong version on stats-page?

I'm pretty sure I'm using rtmp-module v.1.2.2, but the stats page says 1.1.4? In older versions as well ...
https://gyazo.com/69def65b3bb97dc342fab7bff9680696
(Generated by nginx-rtmp-module 1.1.4 ...)
Has this info just not been updated since v1.1.4? :D

邮件已经收到

Yeah looks like version number it take from here: https://github.com/arut/nginx-rtmp-module/blob/master/ngx_rtmp_version.h#L12


SQL packaging

The 0.6.0 package creates a SqlDataProviders folder in the root of the website
with all of the PolyDeploy SQL scripts.  This PR updates the packaging to put them in DesktopModules/Cantarus/PolyDeploy/SqlDataProviders

Thanks for bringing this to our attention Brian, I had absolutely no idea that PolyDeploy was dropping its SqlDataProviders folder at the root of the website.
I've been trying to test this today but unfortunately I receive an installation error. I did a little trial and error and found that by replacing the / with \ in the basePath that everything runs smoothly and as expected.
Have you encountered anything similar?

Weird, I don't think I've ever run into the slashes making a difference in a .dnn file, but if it works the other way, that sounds good to me

Yeah I thought it was weird too.
I did a little more digging and I think I've found the problem. It's not actually to do with whether forward or backward slashes are used although the use of backward slashes will mitigate the issue seemingly. The problem is actually that if the basePath features a trailing forward slash DNN will replace it with two back slashes in addition to the two back slashes it has already appended because it thought there was no trailing back slash.
I've opened an issue with DNN dnnsoftware/Dnn.Platform#2059. Not critical but might avoid others tracing the same problem through the source.
We'll just omit the trailing forward slash.

@can-anierzad thanks for tracking that down.  I've made the requested change.  Let me know if there's anything else.


inline_javascript should not inline scripts with a defer-attribute

If a webpage has a list of javascript script-tags with the 'defer' attribute, and the mod_pagespeed 'inline_javascript' filter inlines some but not all of the scripts, then the execution order of the scripts will change, which may lead to error messages such as 'jQuery is not defined'.
The inline_javascript filter should not inline scripts with the 'defer' attribute (or at the very least there should be an option for the filter to control this behaviour)

@morlovich left a relevant comment in the filter:
https://github.com/apache/incubator-pagespeed-mod/blob/master/net/instaweb/rewriter/js_inline_filter.cc#L120


Add GitHub integration to new Slack "team".

Using unauthed mode in order to have manual control over settings.

Completed and testing now.


Apply semver via git tags

We should probably get the ball rolling on this discussion. As it stands, we're probably at 0.1.0.
However, semver is kind of hard to apply to websites so maybe we should pick and choose what we need out of it? Or perhaps combine it with a different versioning scheme like a serial build number or date?
Like, how do these changes fall into a version change:

CSS change
Controller code change
A model field is changed

Since nobody is affected by these changes then it doesn't neatly fall into semver. Major version changes would be arbitrarily defined since nothing would 'break.' Backwards compatible change means nothing because a website isn't a library that is being loaded as part of a dependency tree.
Maybe each MVP feature set correlates to a minor version increase and a ticket within the aforementioned feature set can correlate to a patch version increase?
Maybe, for now, just have versioning be defined by completed work? Major version (product presentation milestone), minor version (feature set milestone), patch version (a ticket completed as part of a feature set).
I'm curious because I'm going to be finishing the blog feature set soon and when those commits go in it may be a good idea to git tag a release.

It's true that for SF, this is "only a site," but for any other brigade forking the repo to build their own site, it works like any other dependency, and breaking changes are definitely possible if other sites choose to upgrade.  I think standard semver would meet the needs of other brigades well.  I also think any version not ready for adoption by other brigades should be v0.x.x.

@verythorough @therebelrobot If our repo is forked then it's not a dependency; it's the head of a dependency tree. Now, if we packaged brigadehub in a way so that its internal functionality is exposed and can be mounted as express middleware (eg, require('brigadehub')) then the software falls under the purview of what semver is trying to accomplish. Something similar to including ghost or keystone.js in effect. The truth is that semver was designed for a specific type of software and a website and derivations thereof don't fit that type of software. The more we move towards what keystone does the more we 'snugly' we can apply semver as a versioning system - if we choose to do that since that would be a pretty hefty design decision.

and breaking changes are definitely possible if other sites choose to upgrade.

Yeah, and other versioning systems can handle tracking breaking changes. The point of the ticket isn't to dismiss semver out of hand but instead evaluate compromise in its doctrine. If we continue to use it then we should look at conflicts in the semver documentation and either choose our middle ground, use a different versioning scheme, or mix and match.
An example of mixing and matching would be that everything that quacks like an API is versioned under semver (maybe a git submodule or something) but everything that is content related, like a CSS document, is marked as a change in build serial.
That's probably too complex but it's worth mentioning. I think my aforementioned suggestion (attaching semver to features and hotfixes and 'product' releases) is a good start... anyway, this probably needs to be concretely defined because it's good start versioning software earlier than later.

one possible packaging method is via the npm network

Yeah, I was semi-hinting that when I mentioned ghost and keystone. Also to note is that a lot of modules on npm don't strictly follow semver - they follow a three digit versioning scheme that looks like semver. I mean, in my opinion, we should really just get loose outline of what we're doing with versions... try a few releases... and see what works for us.
And if we really do turn out to suck at versioning, we'll hear it from downstream and react accordingly when that time comes.


How to solve when the reCaptcha (v2) is within an iFrame?

Getting "playwright_recaptcha.errors.RecaptchaNotFoundError: The reCAPTCHA was not found." due to the reCaptcha being inside of an iFrame.
Tried to solve this issue by passing the iframe context instead of the page context into the SyncSolver function such that
captcha_iframe = await page.query_selector('iframe[title="reCAPTCHA"]')
if captcha_iframe:
     frame = await captcha_iframe.content_frame()
     recaptchav2.SyncSolver(page=frame, capsolver_api_key="CAP-123") as solver:
          token = solver.solve_recaptcha(wait=True, image_challenge=True)
          print(token)

but run into the error 'Permission denied to access property "docShell" on cross-origin object'.
Has anyone had similar issues?

Could you please provide the full traceback of the error as this appears to be a bug with Playwright, similar to one that I've experienced: https://github.com/microsoft/playwright/issues/21780.

Yup same issue. Have you found a work-around? Turning headless mode off doesn't work for me either.
Error Traceback when trying to access the iframe contextawait captcha_iframe.content_frame():
Traceback (most recent call last):
  File "/Users/jackjack/Documents/code/scrapers/vidburg/upload_puppet.py", line 77, in <module>
    asyncio.run(upload('bshhjsbd', 'kjbndskbsd', 'ksdbhsjhsbkh.mp4'))
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/asyncio/runners.py", line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/Users/jackjack/Documents/code/scrapers/vidburg/upload_puppet.py", line 65, in snap_upload
    captcha_iframe = await captcha_iframe.content_frame()
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/playwright/async_api/_generated.py", line 1773, in content_frame
    return mapping.from_impl_nullable(await self._impl_obj.content_frame())
                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/playwright/_impl/_element_handle.py", line 68, in content_frame
    return from_nullable_channel(await self._channel.send("contentFrame"))
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/playwright/_impl/_connection.py", line 62, in send
    return await self._connection.wrap_api_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/playwright/_impl/_connection.py", line 492, in wrap_api_call
    return await cb()
           ^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/playwright/_impl/_connection.py", line 100, in inner_send
    result = next(iter(done)).result()
             ^^^^^^^^^^^^^^^^^^^^^^^^^
playwright._impl._errors.Error: Protocol error (Page.describeNode): error in channel "content::9/14/2": exception while running method "describeNode" in namespace "page": Permission denied to access property "docShell" on cross-origin object _describeNode@chrome://juggler/content/content/PageAgent.js:416:62
_onMessageInternal@chrome://juggler/content/SimpleChannel.js:237:37
_onMessage@chrome://juggler/content/SimpleChannel.js:194:12
bindToActor/actor.receiveMessage@chrome://juggler/content/SimpleChannel.js:39:44

Well, the only way around this error is to simply use either WebKit or Chromium instead of Firefox.

:( I get reCAPTCHA rate limit errors when I use WebKit... Here is my current implementation:'
captcha_iframe = await page.query_selector('iframe[title="reCAPTCHA"]')
   if captcha_iframe:
       print("reCAPTCHA detected. Solving reCAPTCHA...")
       captcha_iframe = await captcha_iframe.content_frame()
       with recaptchav2.SyncSolver(page, capsolver_api_key=CAPSOLVER_API_KEY) as solver:
           token = solver.solve_recaptcha(attempts=5, wait=True, image_challenge=True)
           print(token)

You could try using Botright, which uses Chromium or preferably Ungoogled Chromium with stealth capabilities.


Please move the iOS devices to the non-guest network in CI

Until we have the native layers back we are going to test using the wifi based mock. So we need to move all the iOS devices over to the non-guest network in CI so that the wifi based mock will work.

iOS devices moved to non-guest network.

@artemjackson With this fix you should be able to submit https://github.com/thaliproject/Thali_CordovaPlugin/issues/914 plus https://github.com/thaliproject/Thali_CordovaPlugin/issues/915 (I would join them into a single PR) to CI And have them pass on both Android and iOS.


Getting microseconds error

Hello, I am trying to integrate ex_audit wit my application using more or less the default configuration.
However when I try to save a model with changes I get the following error:
:utc_datetime expects microseconds to be empty, got: #DateTime<2019-05-02 05:19:39.935000Z>
Use `DateTime.truncate(utc_datetime, :second)` (available in Elixir v1.6+) to remove microseconds.

lib/ecto/type.ex
  end
  defp check_no_usec!(%{microsecond: {0, 0}} = datetime, _kind), do: datetime
  defp check_no_usec!(%struct{} = datetime, kind) do
    raise ArgumentError, """
    #{inspect(kind)} expects microseconds to be empty, got: #{inspect(datetime)}
    Use `#{inspect(struct)}.truncate(#{kind}, :second)` (available in Elixir v1.6+) to remove microseconds.
    """
  end

Any suggestions on how to fix ?
Here are the versions I use:
...
  ecto 3.1.1
  ecto_sql 3.1.1
  ex_audit 0.6.0
  phoenix 1.4.3
  phoenix_ecto 4.0.0

Also here's the whole ST:
 ecto lib/ecto/type.ex:1224 Ecto.Type.check_no_usec!/2
 ecto lib/ecto/type.ex:412 Ecto.Type.dump_utc_datetime/1
 ecto lib/ecto/type.ex:817 Ecto.Type.process_dumpers/3
 ecto lib/ecto/repo/schema.ex:925 Ecto.Repo.Schema.dump_field!/6
 ecto lib/ecto/repo/schema.ex:109 anonymous fn/5 in Ecto.Repo.Schema.init_mapper/3
 elixir lib/enum.ex:1437 anonymous fn/3 in Enum.map_reduce/3
 stdlib maps.erl:257 :maps.fold_1/3
 elixir lib/enum.ex:1956 Enum.map_reduce/3
 ecto lib/ecto/repo/schema.ex:81 anonymous fn/5 in Ecto.Repo.Schema.extract_header_and_fields/5
 elixir lib/enum.ex:1431 Enum."-map_reduce/3-lists^mapfoldl/2-0-"/3
 ecto lib/ecto/repo/schema.ex:80 Ecto.Repo.Schema.extract_header_and_fields/5
 ecto lib/ecto/repo/schema.ex:44 Ecto.Repo.Schema.do_insert_all/6
 ex_audit lib/repo/schema.ex:34 anonymous fn/4 in ExAudit.Schema.update/4
 ex_audit lib/repo/schema.ex:155 ExAudit.Schema.run_in_multi/4
 ecto lib/ecto/multi.ex:579 Ecto.Multi.apply_operation/5
 elixir lib/enum.ex:1940 Enum."-reduce/3-lists^foldl/2-0-"/3
 ecto lib/ecto/multi.ex:563 anonymous fn/5 in Ecto.Multi.apply_operations/5
 ecto_sql lib/ecto/adapters/sql.ex:874 anonymous fn/3 in Ecto.Adapters.SQL.checkout_or_transaction/4
 db_connection lib/db_connection.ex:1415 DBConnection.run_transaction/4
 ecto lib/ecto/repo/transaction.ex:15 Ecto.Repo.Transaction.transaction/4

Thanks !

Please notice that this issue can be resolved by changing line 56 of tracking.ex:
from
now = DateTime.utc_now()
to
now = DateTime.utc_now() |> DateTime.truncate(:second)

I see, the problem is it needs to be configurable because some people are using the _usec variants of the datetimes.

Hello @narrowtux, do you have any timeline on when will this bug be fixed?
TIA

You can solve this by migrating your recorded_at to :utc_datetime_usec

Thanks @aerosol ... I was solving it till now by actually implementing the solution I described in my previous comment (https://github.com/ZennerIoT/ex_audit/issues/14#issuecomment-488563208)

@spapas - @aerosol suggestion required no code change at all. As was noted in https://github.com/ZennerIoT/ex_audit/issues/14#issuecomment-488592623 this needs to be configurable. I.e some people will want microseconds others will not (although, I think a smart thing to do here is to stick with as much precision as possible).

Well at least you need to add a small clarification in the README to help any new users having this issue.


bf:cartographicAttributes and bf:Cartographic issues

Because of the duplication of cartographic information in MARC, in BIBFRAME examples you can clearly see the duplication and it causes problems converting back to MARC since the parts are all spilt up and indistinguishable so it is hard to cram back into the right 034 or 255 subfield without a lot of regexes, handwaving or guessing.
Example Work
This work has 3 cartographic attributes and 2 scales because of the conversion from the 034 and the 255.
		<bf:cartographicAttributes>
			<bf:Cartographic>
				<bflc:relief>
					<bflc:Relief rdf:about="http://id.loc.gov/vocabulary/mrelief/spot">
						<rdfs:label>spot heights</rdfs:label>
					</bflc:Relief>
				</bflc:relief>
			</bf:Cartographic>
		</bf:cartographicAttributes>
		<bf:cartographicAttributes>
			<bf:Cartographic>
				<bf:coordinates>E0152500 E0285000 N0562000 N0474000</bf:coordinates>
			</bf:Cartographic>
		</bf:cartographicAttributes>
		<bf:scale>
			<bf:Scale>
				<rdf:value>600000</rdf:value>
				<rdfs:label>linear horizontal</rdfs:label>
			</bf:Scale>
		</bf:scale>

 		<bf:scale>
			<bf:Scale>
				<rdfs:label>Scale 1:600,000. 1 cm = 6 km</rdfs:label>
			</bf:Scale>
		</bf:scale>
		<bf:cartographicAttributes>
			<bf:Cartographic>
				<bf:coordinates>E 15°25ʹ--E 28°50ʹ/N 56°20ʹ--N 47°40ʹ</bf:coordinates>
			</bf:Cartographic>
		</bf:cartographicAttributes>

This converts to these 034 and 255 fields, note the 4 255 fields:
034 1  $a a $b 600000
255    $a linear horizontal
255    $a Scale 1:600,000. 1 cm = 6 km
255    $c E0152500 E0285000 N0562000 N0474000
255    $c E 15°25ʹ--E 28°50ʹ/N 56°20ʹ--N 47°40ʹ

It is supposed to look like this Marc Record:
034 1  $a a $b 600000 $d E0152500 $e E0285000 $f N0562000 $g N0474000
255    $a Scale 1:600,000. 1 cm = 6 km $c (E 15°25ʹ--E 28°50ʹ/N 56°20ʹ--N 47°40ʹ).

You can't easily distinguish between the coded coordinates from the 034$defg and the coordinate statement from the 255$c.  I think this could be remediated with a subtype of bf:Cartographic - _:CodedCartographic & _:MathematicalCartographic and a new property _:coordinateStatement. For a more precise conversion, you need something like westCoordinate, eastCoordinate, northCoordinate and southCoordinate. The 034 form is a specific type of coordinate so maybe you could use a datatype? I think for now you could tweak bibframe2marc to regex it into the right subfields.
The scales probably should be in cartographicAttributes instead of linked off the Work so this probably needs some analysis for the 034$a and 255$a. The label "linear horizontal" generates a 255$a when you convert to MARC so it needs to be fixed somehow. It is more of a subproperty - it indicates which subfield in MARC this should go in, so maybe it more sense to make either subtypes of bf:Scale for the MARC subfields like bf:Note or just make subproperties of bf:scale and change it so they are datatype properties instead of object properties. Similar to coordinates, the 255$a scale is a statement so I suggest adding _:scaleStatement.
Relief is a 008/18-21 code - I suggest using a bf:code and it seems like something which is CodedCartographic reducing one of the cartographicAttributes. Another possibility is a third type of bf:Cartographic since it could repeat more than once.
So the end result is something like this:
<bf:cartographicAttributes>
	<_:CodedCartographic>
		<bflc:relief>
			<bflc:Relief rdf:about="http://id.loc.gov/vocabulary/mrelief/spot">
				<bf:code>g</bf:code>
				<rdfs:label>spot heights</rdfs:label>
			</bflc:Relief>
		</bflc:relief>
		<bf:coordinates>E0152500 E0285000 N0562000 N0474000</bf:coordinates>
		<bf:scale>
			<bf:Scale>
				<rdf:type rdf:resource="_:LinearHorizontalScale/>
				<rdf:value>600000</rdf:value>
			</bf:Scale>
		</bf:scale>
	</_:CodedCartographic>
 </bf:cartographicAttributes>
<bf:cartographicAttributes>
	<_:MathematicalCartographic>
		<_:scaleStatement>Scale 1:600,000. 1 cm = 6 km</_:scaleStatement>
		<_:coordinatesStatement>E 15°25ʹ--E 28°50ʹ/N 56°20ʹ--N 47°40ʹ</_:coordinatesStatement>
	</_:MathematicalCartographic>
</bf:cartographicAttributes>

For blank node reduction and simplicity, I think we could describe this without bf:cartographicAttributes and Cartographic resources so those would be deprecated. I don't remember why we chose that pattern - it seems like based on current modeling we don't need them anymore?
<bf:Work>
	<rdf:type rdf:resource="http://id.loc.gov/ontologies/bibframe/Cartography" />
	<bflc:relief>
		<bflc:Relief rdf:about="http://id.loc.gov/vocabulary/mrelief/spot">
			<bf:code>g</bf:code>
			<rdfs:label>spot heights</rdfs:label>
		</bflc:Relief>
	</bflc:relief>
	<bf:coordinates>E0152500 E0285000 N0562000 N0474000</bf:coordinates>
	<bf:scale>
		<bf:Scale rdf:about="_:LinearHorizontalScale">
			<rdf:value>600000</rdf:value>
		</bf:Scale>
	</bf:scale>
	<_:scaleStatement>Scale 1:600,000. 1 cm = 6 km</_:scaleStatement>
	<_:coordinatesStatement>E 15°25ʹ--E 28°50ʹ/N 56°20ʹ--N 47°40ʹ</_:coordinatesStatement>
</bf:Work>

This seems, at least for now, more a conversion issue than an ontology issue, hence the move.
Your "blank node reduction" idea is attractive but 034 and 255, from which this info comes, are repeatable.  Q: How do you resolve that then?
I see three options, or so:

Continue to segregate the info as seen in your penultimate example.
Confirm that, despite the fields repeatability, they are never used that way and any loss is OK.
Determine that 034/255 pairs represent different Instances, which has a bunch of implications.
Maybe there is a fourth option.  Go with your 'blank node reduction' idea but if there are multiple 034/255 pairs, then segregate them.

Thoughts?

There's a whole bunch of ontological and conversion ideas in this section - it's hard to pin down where it goes exactly.
This whole thing with paired fields in MARC was a bad idea - display-wise they might keep the entry order but indexing isn't going to know about this - both 255$abcde and 034$bcdefgz3 are both indexed in the keyword index in WC. I think I had forgotten 007, which probably also would follow with the 034/255 pairs.
Option 3 is the one that kind of blows all this up but probably makes more sense along with option 1; I was hoping like OLAC there were some good examples gathered by magirt in a document. This isn't quite what I was looking for: Best Practices (2020) I'll keep looking.


Increase GABLS dt

Based on https://github.com/CliMA/ClimaAtmos.jl/pull/1182 we should be able to run GABLS with 100x dt

bors r+

bors r-

bors r+

bors r+

Seems like this was actually merged?

Yeah, not sure why it didn't get closed.


Add option to find menu for matching whole words

This adds the Whole Words option to the find menu. This depends on https://github.com/google/xi-editor/pull/711 and https://github.com/google/xi-mac/pull/203

@scholtzan Are there any changes in this PR not present in #207 ? If 207 is up to date I may just merge that as is.

You can just merge it. All the changes are present in #207


V1 - Create Subnet Miner

Implement Twitter Data Endpoints (MVP) Subnet Miner Code
Tasks:

[x] #17
[x] #18
[x] #19

Objective:
Develop a subnet miner within the Bittensor network that interfaces with the Masa Protocol worker node API to retrieve Twitter data. The miner will provide endpoints for three specific Twitter-related queries: profile information, recent tweets by keyword, and a user's followers list.
Acceptance Criteria:

Miner code can accurately fetch and return Twitter profile information.
Miner code successfully retrieves recent tweets based on a provided keyword.
Miner code can fetch a user's followers list upto the maximum number specified in the query parameter
All miner endpoints are registered and served using the Bittensor API.
The miner adheres to the Masa Protocol worker node API's rate limits and handles exceptions properly.
Documentation is provided for each miner function, detailing inputs, outputs, and behavior.

Resources:

[Bittensor API Documentation](https://docs.bittensor.com/python-api/html/autoapi/bittensor/index.html)
[Masa Protocol Worker Node API](http://localhost:8080/swagger/index.html#/)

Development Steps:

Set up a Bittensor wallet and neuron using the Bittensor API.
Register the miner's endpoints with the Bittensor network.
Implement the Twitter data retrieval logic using the Masa Protocol worker node API.
Serve the miner's endpoints using Bittensor's Axon server.
Test the miner's functionality and handle edge cases.
Document the miner's code and usage instructions.

Closing as not relevant anymore


Cannot create host-only adapter with VBox 5 on Windows 10 (using administrative shell)

Environment:

Windows 10 build 10162 (basically the RC1)
VirtualBox 5.0 (final)
docker-machine latest as of 2015-07-13 (downloaded from the nightly builds, because VBox 5 needs this fix)

In an administrative command prompt (Win-X -> Command Prompt (Admin)), trying to create a VirtualBox boot2docker vm fails when attempting to create a host-only adapter:
C:\Users\myuser\Downloads>docker-machine_windows_amd64.exe create --driver virtualbox dev -D
Creating CA: C:\Users\myuser\.docker\machine\certs\ca.pem
Creating client certificate: C:\Users\myuser\.docker\machine\certs\cert.pem
executing: c:\Program Files\Oracle\VirtualBox\VBoxManage.exe
STDOUT: Oracle VM VirtualBox Command Line Management Interface Version 5.0.0
(C) 2005-2015 Oracle Corporation
All rights reserved.

Usage:

  VBoxManage [<general option>] <command>

[... snip entire VBoxManage syntax help ...]

STDERR:
Image cache does not exist, creating it at C:\Users\myuser\.docker\machine\cache...
No default boot2docker iso found locally, downloading the latest release...
Downloading https://github.com/boot2docker/boot2docker/releases/download/v1.7.0/boot2docker.iso to C:\Users\myuser\.docker\machine\cache\boot2docker.iso...
Creating VirtualBox VM...
Creating SSH key...
Creating disk image...
Creating 20000 MB hard disk image...
Converting from raw image file="stdin" to file="C:\Users\myuser\.docker\machine\machines\dev\disk.vmdk"...
Creating dynamic image with size<PHONE_NUMBER>0 bytes (20000MB)...
executing: c:\Program Files\Oracle\VirtualBox\VBoxManage.exe createvm --basefolder C:\Users\myuser\.docker\machine\machines\dev --name dev --register
STDOUT: Virtual machine 'dev' is created and registered.

Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp

Error creating machine: exit status 1
You will want to check the provider to make sure the machine and associated resources were properly removed.

Thanks for reporting this issue.  I'll look into it.

I'm having the same issue with Windows 10 build 10240 and VirtualBox 5.0. It seems to be a VirtualBox issue though, since just running VBoxManage.exe hostonlyif create alone errors.
I have been able to bypass the issue by setting the IP address on the adapter manually to match the HostOnlyCIDR value.

Yeah, that's similar to how I've been solving it, too.
I'm also having occasional routing errors (the correct routing entries disappear) with the host-only adapter, which might be related to all of this.

Thanks for sharing your solution @sakai135, I was having the same problem. :)
I also had to enable DHCP server on the network interface to get it up and running.

I can also confirm this, on Win 10, build 10240
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp
This is fixed when, as above, I input the expected IP address in the Host-Only NIC configuration. I did not have to do anything with DHCP.

Possible cause in VirtualBox 5.0: https://www.virtualbox.org/ticket/14040

Hi, I'm new to all these "docker things" and have some troubles here. I'm using Windows 10x64 10162 build
I did everything as you said:

downloaded new version of docker-machine
Ran docker-machine_windows_amd64.exe -D create -d virtualbox --virtualbox-hostonly-cidr <IP_ADDRESS>/24 dev
I did nothing with DHCP server as @henriiik mentioned above

Then it was fine until
`STDERR:
Error dialing TCP: ssh: handshake failed: WSARecv tcp <IP_ADDRESS>:49751: An existing connection was forcibly closed by the remote host.
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: WSARecv tcp <IP_ADDRESS>:49803: An established connection was aborted by the software in your host machine.
Error dialing TCP: ssh: handshake failed: EOF
SSH returned: 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:41:85:25 brd ff:ff:ff:ff:ff:ff
inet6 fe80::a00:27ff:fe41:8525/64 scope link
valid_lft forever preferred_lft forever
END SSH
.....
.....
.....
ERROR getting IP: No IP address found 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:41:85:25 brd ff:ff:ff:ff:ff:ff
inet6 fe80::a00:27ff:fe41:8525/64 scope link
valid_lft forever preferred_lft forever
Error creating machine: Maximum number of retries (5) exceeded You will want to check the provider to make sure the machine and associated resources were properly removed.
However, VM boots good and
$ docker version from VM command line gives me next
Client version: 1.7.1
Client API version: 1.19
Go version(client): go1.4.2
Git commit(client): 786b29d
OS/Arch(client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit(server): 786b29d
OS/Arch(server): linux/amd64
But when i'm running
$ eval "$(docker-machine_windows_amd64.exe env dev)
> docker ps
>
from my msysgit 1.95 nothing happens
Have i something misunderstood?
Help me please
Thanks in advance

@levgaas Yours seems like a separate issue. Install build 10240 and see what happens. 10162 is pretty outdated.

I'm using Vagrant, not Docker, but my workaround was to assign a static IP
on the bridged interface and explicitly specify the correct adapter in the
public network section of the Vagrantfile.
Storm Chaser Scott Roberts
KSStorm.info
-- from mobile device
On Jul 28, 2015 17:12, "Keiichi Shimamura"<EMAIL_ADDRESS>wrote:

@levgaas https://github.com/levgaas Yours seems like a separate issue.
Install build 10240 and see what happens. 10162 is pretty outdated.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/issues/1521#issuecomment-125767935.

Finally got it running by manually setting up the host-only-network on my Windows 10 machine. The init script for boot2docker calls "VBoxManage.exe list hostOnlyifs". It searches for a host only interface matching parameters set up in $HOME/.boot2docker/profile. For convenience you can access these with:
"boot2docker config"
All you have to do is create a hostonlyInterface configuration matching these parameters. As an example, here was mine:
Init = false
Verbose = false
Driver = "virtualbox"
Clobber = false
ForceUpgradeDownload = false
SSH = "ssh"
SSHGen = "ssh-keygen"
SSHKey = "C:\Users\Yakubu\.ssh\id_boot2docker"
VM = "boot2docker-vm"
Dir = "C:\Users\Yakubu\.boot2docker"
ISOURL = "https://api.github.com/repos/boot2docker/boot2docker/releases"
ISO = "C:\Users\Yakubu\.boot2docker\boot2docker.iso"
DiskSize = 20000
Memory = 2048
CPUs = 4
SSHPort = 2022
DockerPort = 0
HostIP = "<IP_ADDRESS>"
DHCPIP = "<IP_ADDRESS>"
NetMask = [255, 255, 255, 0]
LowerIP = "<IP_ADDRESS>"
UpperIP = "<IP_ADDRESS>"
DHCPEnabled = true
Serial = false
SerialFile = "\\.\pipe\boot2docker-vm"
Waittime = 300
Retries = 75
If all goes well, the init script wouldn't bother attempting to create a host-only adapter and you shouldn't run into this error
Failed to create the host-only adapter

@sakai135 After upgrading to 10240 build.
docker-machine_windows_amd64.exe -D create -d virtualbox --virtualbox-hostonly-cidr <IP_ADDRESS>/24 dev gives me author`s error
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp
I have the adapter with specified IPv4 address(<IP_ADDRESS>) but every time when i run docker-machine_windows_amd64.exe -D create -d virtualbox --virtualbox-hostonly-cidr <IP_ADDRESS>/24 dev new adapter is created with different ip

@cyclonebt How did you specify the already-existing adapter in the Vagrant config? I'm having the same issue and believe you solution will fix it.

Bring it up once with bridged networking, and it will show you the name of
the adapters when it asks you to select which one to use. Copy/paste the
name into the spec. Here's what mine looks like:
config.vm.network "public_network", bridge: "Realtek PCIe GBE Family
Controller", ip: "<IP_ADDRESS>"
On Wed, Jul 29, 2015 at 3:40 PM, Matt Janssen<EMAIL_ADDRESS>wrote:

@cyclonebt https://github.com/cyclonebt How did you specify the
already-existing adapter in the Vagrant config? I'm having the same issue
and believe you solution will fix it.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/issues/1521#issuecomment-126088967.

--
Scott Roberts, KB5TOR
http://ksstorm.info/KSStorm.Info http://kstorm.info/ - Severe Storm
Outlooks, Safety Information and Video
Follow Storm Chaser Scott Roberts:
http://facebook.com/chasersroberts http://twitter.com/KSStormInfo
http://plus.google.com/+KSStormInfo http://youtube.com/ksstormmedia
Video/Photo Licensing: (844) KS-STORM

Hi all, just some update on this:
I have reproduced the issue around VBoxManage hostonlyif create on Windows 10 and can confirm that command is failing.
I've made a comment on the Virtualbox ticket tracker here: https://www.virtualbox.org/ticket/14040
I can't really think of any way to work around it until upstream fixes this bug, so I'm all ears if anyone has suggestions.

Update:  We've reached out to some folks at Oracle to hopefully move this along as fast as we can.

@nathanleclaire , thank you =) we appreciate it

Thank you very much @nathanleclaire!

A short-term working patch was released last night. Tested and it works. https://www.virtualbox.org/ticket/14040#comment:36

Update for everyone: I have this working again with the latest VirtualBox test build.  Now we just have to wait for the patch to land in a release.

:joy: Thanks @nathanleclaire

@hheimbuerger @sakai135 @henriiik can you try with docker-machine 0.5.6 and tell us if it's better?

This is fixed in https://github.com/docker/machine/pull/2797. Failed to create the host-only adapter is Virtualbox own way to tell us that the adapter is created but not yet listed. We now have a series of workarounds to fix this issue

not fixed at all...
tried VB 5.0.14, and different 5.0.15.xxxxxx.
same shit happening.

I'm unable to get this working as well.
λ docker-machine create --driver virtualbox default
Running pre-create checks...
(default) Default Boot2Docker ISO is out-of-date, downloading the latest release...
(default) Latest release for github.com/boot2docker/boot2docker is v1.10.1
(default) Downloading C:\Users\Tyler Hampton\.docker\machine\cache\boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v1.10.1/boot2docker.iso...
(default) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
Error with pre-create check: "VirtualBox is configured with multiple host-only adapters with the same name \"HostInterfaceNetworking-VirtualBox NDIS 6.0 Miniport Driver\". Please remove one."

Windows 10
docker-machine 0.6.0
docker 1.10.0
VirtualBox 5.0.14

Not fixed.

@frankbolviken Please file an issue with clear steps to reproduce and information about your host system, Machine version, and so on -- without any information issues cannot be fixed.

@nathanleclaire see also https://github.com/docker/machine/issues/2972#issuecomment-183755968.
is in fact not related to Docker per se, but maybe someone might get somewhat tired of the Oracle shit...

Scratch my comment. Turns out that Cisco VPN client totally borks up all network stuff, and renders docker-machine useless after use. Have to reboot computer.

It occured on upgrade virtualbox.
Work around:
uninstall virtualbox and install virtualbox again.

Same issue here.
The virtualBox comes with Docker toolkit is 5.0.14 at this moment then after I upgraded it onto 5.0.16 error appears.

Check comment #76 from the following - this worked for me.
https://www.virtualbox.org/ticket/14040
I was able to workaround by setting the following .exe's to Windows 8 compatibility mode:
Virtualbox.exe
VBoxManage.exe
VBoxHeadless.exe


Packet s3.xlarge.x86 instances can't provision flatcar OS

Description
Provisioning failures of Flatcar OS (Alpha, Beta, Stable, and Edge) on the s3.xlarge. Suspect issue is related to installing on NVMe disks in BIOS mode (not UEFI/EFI).
Impact
Flatcar Container is not working on these instances.
Environment and steps to reproduce

Set-up: Select Flatcar for a s3.xlarge instance on Packet
Task: Provisioning
Action(s): Attempt to provision Flatcare OS (Alpha, Beta, Stable, or Edge) on s3.xlarge
Error: Provisioning failure

Expected behavior
Provision successful
Additional information
Flatcar for s3.xlarge is currently toggled off. When there is a desire to test, let me know and I'll turn it back on.
@marga-kinvolk Happy to provide any additional detail.

Hello,
thanks for creating the issue here. Can you tell which Alpha version got installed?
The latest Alpha has a fix for the c3.medium and some m2.xlarge instances which probably is relevant:
The first update happens after a couple of minutes, so either be fast or disable updates with the following user-data:
{
  "ignition": {
    "version": "2.2.0"
  },
  "systemd": {
    "units": [
      {
        "mask": true,
        "name": "update-engine.service"
      }
    ]
  }
}

Thanks, we have confirmed we have the latest releases for all versions with @t-lo
Some more detail that may be helpful:
We see it get this far:

Flatcar Container Linux by Kinvolk stable (2512.2.1)
Update Strategy: No Reboots
Failed Units: 1
tcsd.service
core@localhost ~ $
core@localhost ~ $

Then it reboots again and never loads an OS
Ends with:

Reboot and Select proper Boot device
or Insert Boot Media in selected Boot device and press a key

Ah, I see, the GRUB menu never showed up for me and it's only trying FlexBoot.
What I did was booting via iPXE: https://alpha.release.flatcar-linux.net/amd64-usr/current/flatcar_production_packet.ipxe
with this user-data:
{
  "ignition": { "version": "2.2.0" },
  "storage": {
    "links": [{
      "filesystem": "root",
      "path"<EMAIL_ADDRESS>      "target"<EMAIL_ADDRESS>    }]
  }
}

and then installing to disk with: sudo flatcar-install -o packet -s
This chose the an NVMe block device for installation. You said it works with UEFI but not BIOS? Then the block device would be ok and maybe GRUB is missing something. But I wonder why I didn't get the GRUB menu – is there something in the BIOS which configures not to boot from that drive?

To install to a /dev/sdX device add the -e MAJOR flag with the major device number of the NVMe disk.

Hi Kelsey!
Were you able to work around the problem with the information we provided?
Do you need any more information from the flatcar side?
Cheers!

@kgwaters6 This was resolved recently by excluding the NVMe drives' major device numbers from the installation, or was this for another instance type?

@pothos https://github.com/tinkerbell/boots/pull/86 accomplished this goal, I believe this issue can be resolved

Thanks


Serialise COVID-19 table as JSON

Users have requested that the OT table with target information related to COVID-19 (see #1032) is made available as JSON.

First attempt by @DSuveges was to serialise the pandas dataframe directly as JSON but this does not work as expected for a number of columns that have lists in there and that are saved as strings by default. We're now working on a better solution that requires making some changes to the parsers and the integrator

PR #25 fixes this. The columns that contain lists are now JSON lists as seen in the example below:
{
  "ensembl_id": "ENSG00000196639",
  "biotype": "protein_coding",
  "name": "HRH1",
  "description": "histamine receptor H1 [Source:HGNC Symbol;Acc:HGNC:5182]",
  "uniprot_ids": "C9J2E6,P35367",
  "COVID-19 UniprotKB": false,
  "Implicated_in_viral_infection": null,
  "Covid_direct_interactions": null,
  "Covid_indirect_interactions": null,
  "is_abundance_reg_on_covid": null,
  "abundance_reg_on_covid": null,
  "invitro_covid_activity": "LORATADINE weakly active and cytotoxic (ELLINGER);CETIRIZINE inactive (TOURET);DOXYLAMINE inactive (TOURET);DESLORATADINE inactive (TOURET);OLOPATADINE inactive (TOURET);PHENIRAMINE inactive (TOURET);DIMENHYDRINATE highly active (TOURET);TRIPELENNAMINE highly active (TOURET);ANTAZOLINE inactive (TOURET);METHAPYRILENE inactive (TOURET);DIPHENYLPYRALINE inactive (TOURET);LEVOCABASTINE inactive (TOURET);MECLIZINE inactive (TOURET);CLEMASTINE inactive (TOURET);TERFENADINE inactive (TOURET);BETAHISTINE inactive (TOURET);ASTEMIZOLE inactive (TOURET);CINNARIZINE inactive (TOURET);CHLORPHENIRAMINE inactive (TOURET);PYRILAMINE inactive (TOURET);CYPROHEPTADINE inactive (TOURET);KETOTIFEN inactive (TOURET);EMEDASTINE inactive (TOURET);AZELASTINE inactive (TOURET);PROMETHAZINE inactive (TOURET);TRIMIPRAMINE inactive (TOURET);CYCLIZINE inactive (TOURET);DIPHENHYDRAMINE inactive (TOURET);TOLAZOLINE inactive (TOURET);BROMPHENIRAMINE inactive (TOURET);METHYLPROMAZINE inactive (TOURET);TRIPROLIDINE inactive (TOURET);CARBINOXAMINE inactive (TOURET);HYDROXYZINE inactive (TOURET);HISTAMINE inactive (TOURET);ORPHENADRINE inactive (TOURET);FEXOFENADINE inactive (TOURET);AZATADINE inactive (TOURET);LORATADINE inactive (TOURET);PROMETHAZINE highly active (WESTON);ASTEMIZOLE highly active (RIVA)",
  "has_invitro_covid_activity": "5/41",
  "has_drug_in_covid_trials": null,
  "drugs_in_covid_trials": null,
  "max_phase": 4,
  "drugs_in_clinic": 46,
  "hpa_subcellular_location": [
    "Plasma membrane",
    "Cytosol"
  ],
  "hpa_rna_tissue_distribution": "Detected in many",
  "hpa_rna_tissue_specificity": "Low tissue specificity",
  "hpa_rna_specific_tissues": null,
  "respiratory_system_is_expressed": true,
  "respiratory_system_expressed_tissue_list": [
    "lung",
    "tonsil"
  ],
  "immune_system_is_expressed": true,
  "immune_system_expressed_tissue_list": [
    "alternatively activated macrophage",
    "bone marrow",
    "CD14-positive, CD16-negative classical monocyte",
    "CD34-negative, CD41-positive, CD42-positive megakaryocyte cell",
    "CD4-positive, alpha-beta T cell",
    "CD4-positive, alpha-beta thymocyte",
    "CD8-positive, alpha-beta T cell",
    "central memory CD4-positive, alpha-beta T cell",
    "class switched memory B cell",
    "conventional dendritic cell",
    "EBV-transformed lymphocyte",
    "effector memory CD4-positive, alpha-beta T cell",
    "granulocyte monocyte progenitor cell",
    "inflammatory macrophage",
    "leukocyte",
    "lymph node",
    "macrophage",
    "mature neutrophil",
    "memory B cell",
    "neutrophilic metamyelocyte",
    "segmented neutrophil of bone marrow",
    "small intestine Peyer's patch",
    "spleen",
    "tonsil"
  ],
  "has_safety_risk": true,
  "safety_info_source": [
    "known_target_safety",
    "experimental_toxicity"
  ],
  "safety_organs_systems_affected": [
    "immune system",
    "cardiovascular system",
    "nervous system",
    "gastrointestinal system"
  ],
  "Tractability_Top_bucket_(sm)": "Targets with drugs in phase IV",
  "Tractability_Top_bucket_(ab)": "Targets located in the plasma membrane ",
  "Tractability_Top_bucket_(other)": null,
  "scientificName": "Homo sapiens",
  "FILTER_network": false,
  "FILTER_network+drug": false,
  "FILTER_network+covid_tests": true
}


BUG: fixing circular import in daal4py/sklearnex device_offloading

Description
Fixing circular import in daal4py/sklearnex device offloading.
The best way to resolve the issue here is to refactor the code to avoid it. This PR rethinking the design of sklearnex/daal4py/onedal4py import modules and their dependencies.
Changes proposed in the PR:

adding _config for onedal4py, just for exposing some sklearnex's config settings into onedal4py level
remove circular import in daal4py/onedal4py/sklearnex:

removing _device_offloading module from daal4py, since after #1770 and adding #1843 there is no need for GPU offloading via daal4py syc_context.
most of device_ofloading functionality moved to onedal4py level.
created _config module in onedal4py, for exposing some sklearnex config setting into onedal4py level, reused it on sklearnex level
sklearnex depends on onedal4py _config and _device_oflload modules.

Note: It is expected that it will not offload GPU validation Kmeans on main branch, since they are using daal4py GPU offloading, that is removed to call.
#1770 is considered fixe for this.
TODO

create sklearnex estimators, that uses daal4py backend

https://github.com/intel/scikit-learn-intelex/pull/1832#discussion_r1648578243

[x] I have reviewed my changes thoroughly before submitting this pull request.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation to reflect the changes, if necessary (updated in # - add PR number)
[x] The unit tests pass successfully.
[X] I have run it locally and tested the changes extensively.
[x] I have resolved any merge conflicts that might occur with the base branch.
[x] Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details)
[x] I have added a respective label(s) to PR if I have a permission for that.

/intelci: run

/intelci: run

In the case we drop in the daal4py oneapi interfaces, is this movement of device_offload to daal4py necessary? Couldn't we just delete the sklearnex import of various aspects in daal4py/sklearn/_device_offload.py and it would remove the circular import problem? If true, how far away are we from being able to do that. As far as I see, none of the imported estimators from daal4py in sklearnex outside of Ridge can offload to GPU via daal4py. Its a question over aspects of: Ridge Lasso ElasticNet PairwiseDistances train_test_split roc_auc_score
or am I missing something?
In general just some minor naming convention stuff. Would like the thoughts of other reviewers on that.

In the case we drop in the daal4py oneapi interfaces, is this movement of device_offload to daal4py necessary? Couldn't we just delete the sklearnex import of various aspects in daal4py/sklearn/_device_offload.py and it would remove the circular import problem? If true, how far away are we from being able to do that. As far as I see, none of the imported estimators from daal4py in sklearnex outside of Ridge can offload to GPU via daal4py. Its a question over aspects of: Ridge Lasso ElasticNet PairwiseDistances train_test_split roc_auc_score
or am I missing something?
In general just some minor naming convention stuff. Would like the thoughts of other reviewers on that.

@icfaust Thank you for the review!
I think there are several things mixed up here.
Perhaps this is a lack of of my PR description. I want to bring some clarity.

This PR tries to keep everything as it is. It does not imply changing anything in flow device offloading.
For oneapi iface we have onedal4py+sklearnex. If we drop daal4py, then all these necessary things will simply be transferred to the sklearnex _device_offload module, since daal4py will no longer be needed.

Some minor updates are required, but overall PR is ready

As far as I see, none of the imported estimators from daal4py in sklearnex outside of Ridge can offload to GPU via daal4py. Its a question over aspects of: Ridge Lasso ElasticNet PairwiseDistances train_test_split roc_auc_score
or am I missing something?

If I understood the question correctly, and if you asking why we need daal4py sycl_context, so then actually Kmeans and other estimators from daal4py.sklearn that is used on sklearnex main branch does GPU offloading via sycl_context. so that is why we need to leave it as is.
If anything requires drop I would like to do this reduction in the next steps.

Dear reviewers.
In my PR, I tried to get rid of circular imports. so I slightly changed the import hierarchy in daal4py/onedal4py/sklearnex namespaces.
But @icfaust raised an interesting question.
If we look at this issue more broadly, should we generally retain the support_usm_ndarray functionality for daal4py in general?
Which estimator with daal4py backend do we use for GPU offloading? correct me if nothing other than Kmeans. Kmeans is in the active phase of moving out preview #1770, which should happen in the near future, perhaps already before the next release. In that case, does it make sense to support daal4py for usm_ndarray interop at all? if not, then it makes sense to make changes in my PR and transfer the necessary things for device offloading to onedal4py backend and reuse it in sklearnex.
Removing this from daal4py._device_offloading and adding it to onedal4py._device_offloading also solves the circular imports problem.
After the discussion we will decide to integrate is as is, or update it for onedal4py backend only.

Dear reviewers,
I am returning this PR to development.
I will remove all usm_ndarray support from daal4py. All device_offload primitives will be located in the onedal4py module.
Since Kmeans only uses daal4py's GPU offloading, it is only expected that these tests will fail until Kmeans with onedal4py is integrated #1770

/intelci: run

/intelci: run

/tests/daal4py/sycl/gradient_boosted_regression.py
FAILED	gradient_boosted_regression.py	with errno	-9

Internal CI is green.
Only fail is not related with the changes from this PR.

/intelci: run

/intelci: run

@ethanglaser @icfaust thank you for the review!
I have addressed almost to all comments.
I am pleased to invite you to the second round of reviews. Please mark comments as resolved if any.

/intelci: run

/azp run CI

/azp run CI

/intelci: run

@ethanglaser @icfaust @Alexsandruss thank you for the review!
Dear reviewers I have addressed all your comments. Please mark comments as resolved if any.

No major objections from my side at this point, looking good, seems like the queue/device offload will functionally remain the same. One remaining question I have is what separates functionality defined in onedal/_device_offload.py vs. sklearnex/_device_offload.py at this point? Seems like maybe these could all be moved to onedal4py. But if there is functionality in sklearnex for a reason then I guess not.

No major objections from my side at this point, looking good, seems like the queue/device offload will functionally remain the same. One remaining question I have is what separates functionality defined in onedal/_device_offload.py vs. sklearnex/_device_offload.py at this point? Seems like maybe these could all be moved to onedal4py. But if there is functionality in sklearnex for a reason then I guess not.

Thank you!
sklearnex specific functional I left in sklearnex._device_offload module. I think it should be ok now.

/intelci: run

/intelci: run

/intelci: run

Last CI run: http://intel-ci.intel.com/ef3451eb-4a87-f13b-98de-a4bf010d0e2e

/intelci: run

CI looks good. Fails are not related with changes on current PR. Merging it
Many thanks to the reviewers for the excellent work done.


GEODE-3543: refactor ExpiryTask to not call GemFireCacheImpl.getInstance

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>@nreich @agingade

The if (!isEntryExpiryPossible()) check could be combined with the  if (!isInitialized()) just above it, but otherwise, looks good to me.

Nick you are correct that those two conditions could be combined into one but I'm not sure that would make the code better. Michael Feathers convinced me that the code is easier to understand if you keep the conditions simple.
So:
if A return;
if B return;
is preferred over:
if A || B return;
Sometimes A and B are logically connected to it would make more sense to have them in the same condition. In that case you should consider turning them into a single logical method instead of using an expression.
In this case I also prefer keeping them separate because "if A return" already existed. So adding "if B return" allowed my to not change the original code.


subscriber api

subscribe to all or some events by implementing an UnleashSubscriber
improved support for supplying a custom UnleashScheduledExecutor through UnleashConfig
default UnleashScheduledExecutor is instantiated lazily
isolate periodical task from one-off tasks
adding assert4j for more fluent assertions
bugfix in FeatureToggleRepository.updateToggles() - do not log error
when status=NOT_CHANGED

targets issue #51

Coverage decreased (-0.4%) to 94.43% when pulling 3893bfa7aede05d5cfc30094c20ec9d75c46c8af on jan-berge-ommedal:subscriber-api into 0e5bd6068a21172810ce0515903ea7266a915c27 on Unleash:master.

All in all great work! Could you make sure that the first line in the commit use semantic syntax, for example feat: Subscriber API

Sorry been a bit occupied last week. What's left to make this one mergable?

Sorry been a bit occupied last week. What's left to make this one mergable?

There was a conflict with #69 since both PRs actually fixes the same bug. Since the error logging now is performed in the subscriber, this PR effectively negates #69. Oh well.
As far as I can see, this PR is now ready unless you want me to rebase this https://github.com/Unleash/unleash-client-java/pull/67/commits/063e8cba488cb29cf93cc5c80d7e11f242ee68a9

Please revise ;)
I think you should be allowed to merge it yourself ;)


[Proposal] Add support for lazy eager loading

Hi,
As describe here: https://laravel.com/docs/master/eloquent-relationships#lazy-eager-loading, it would be nice to be able to do something like:
$repository->findAll()->load(['comments', 'comments.user']);

Thanks,
Kind regards.

Well I don't know how we could implement this since findAll returns cached results. Embedding data after could be tricky.
@Omranic thoughts on this one?

Sorry, didn't catch this issue. Anyway I guess I agree with @ionut-tanasa
@gaillafr Unless you've other thoughts it's really tricking to deal with this sort of things. Remember that you still have the ability to use the with method to retrieve relations on demand, but that will be considered a different query & cached separately.


Markdown renderer caused the string in { xxx } lost

Markdown renderer caused the string in { xxx } lost.
When I try to convert the following markdown to HTML:
{ HTTP_HOST }

Markdig will give me the following result:
<p http_host>
</p>

But it seems other markdown converter will produce the following result:
<p>
  { HTTP_HOST }
</p>

So how to make markdig to remain the content in the braces?

My source code is
var pipeline = new MarkdownPipelineBuilder()
                .UseAdvancedExtensions()
                .Build();
// Convert from HTML to markdown
vm.Data.Content = Markdown.ToHtml(vm.Data.Content, pipeline);

It seems that I am using UseAdvancedExtensions extensions.

That's the attribute extension causing this, you should not use it if you are using things like { xxx }

Changed the code snippet
   var pipeline = new MarkdownPipelineBuilder()
                .UseAutoLinks()
                .UseBootstrap()
                .UseGridTables()
                .UsePipeTables()
                .Build();
            // Convert from HTML to markdown
            var result = Markdown.ToHtml(mymarkdown, pipeline);

Thank you very much for solving this problem


Glob added to pattern matching

I also added an ILIKE example with ESCAPE. Thanks for adding that in @Mytherin!
This is ready to review.


Update visual-studio-code-overview.md

The instructions for trusting a cert also works for Edge Chromium, so I added it.

Docs Build status updates of commit 5c4d6d8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:warning:Warning
View
Details

msteams-platform/toolkit/visual-studio-code-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 37, Column 0: [Warning-hard-coded-locale] Link 'https://partner.microsoft.com/en-US/support/v2/?stage=1' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Thanks, @msftjayongg!


Update SECURITY.md

Description

A clear and concise summary of the change and which issue (if any) it fixes. Should also include relevant motivation and context.
Resolved or fixed issue:
Affirmation

[ ] My code follows the CONTRIBUTING.md guidelines

testing


nodePackages: springclean

Motivation for this change
first batch of deprecations from https://github.com/NixOS/nixpkgs/pull/50003
cc @shlevy @svanderburg @rbvermaa @peterromfeldhk @therealpxc
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

post-merge reviews welcome.


Add pull request template

Discussed at #44, Added a new pull request template.

This is great, thanks @avinoth.  I left some feedback for you.

@doomspork It's so embarrassing with the mistakes. I've corrected it, take a look at it when you have a chance.
Oh, and also please squash and merge to make sure the last commit message doesn't go into history :blush:

Good morning @avinoth!  No need to be embarrassed, I really appreciate you taking the initiative to do this.
This looks good to me, thank you again :+1:


Expanding a folder or opening a file gives "Cannot read property toString of undefined"

Steps to Reproduce:

Join a collaboration session
Try to open any file or expand any folder

||Version Data||-:|:-||extensionName|VSLS||extensionVersion|1.0.1377||protocolVersion|2.2||applicationName|VSCode||applicationVersion|1.27.2||platformName|MacOS||platformVersion|17.7.0|

Trying to open any folder in a live session introduces this issue:

After some inspection, I found the stacktrace for the error in the renderer logs (some file paths are obfuscated with * on purpose):
[2019-12-15 13:59:09.108] [renderer1] [error] cannot open vsls:/**********/index.js. Detail: Cannot read property 'toString' of undefined: Error: cannot open vsls:/**********/index.js. Detail: Cannot read property 'toString' of undefined
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:4281:662
    at Object.v [as _notify] (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:155:302)
    at Object.enter (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:158:568)
    at n.Class.derive._creator._run (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:902)
    at n.Class.derive._creator._chainedError (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:261)
    at n (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:157:40)
    at n.Class.define.cancel.then (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:160:736)
    at Object.enter (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:157:109)
    at n.Class.derive._creator._run (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:902)
    at n.Class.derive._creator._setCompleteValue (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:596)
    at Object.v [as _notify] (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:155:284)
    at Object.enter (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:158:568)
    at n.Class.derive._creator._run (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:902)
    at n.Class.derive._creator._chainedError (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:261)
    at n (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:157:40)
    at n.Class.define.cancel.then (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:160:736)
    at Object.enter (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:157:109)
    at n.Class.derive._creator._run (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:902)
    at n.Class.derive._creator._setCompleteValue (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:596)
    at Object.v [as _notify] (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:155:284)
    at Object.enter (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:158:568)
    at n.Class.derive._creator._run (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:902)
    at n.Class.derive._creator._chainedError (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:261)
    at n (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:157:40)
    at n.Class.define.cancel.then (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:160:736)
    at Object.enter (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:157:109)
    at n.Class.derive._creator._run (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:902)
    at n.Class.derive._creator._setCompleteValue (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:596)
    at Object.v [as _notify] (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:155:284)
    at Object.enter (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:158:568)
    at n.Class.derive._oncancel._run (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:902)
    at n.Class.derive._oncancel._error (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:419)
    at l (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:162:962)
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:163:70
    at Object.v [as _notify] (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:155:302)
    at Object.enter (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:158:61)
    at n.Class.derive._oncancel._run (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:902)
    at n.Class.derive._oncancel._completed (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:159:343)
    at e.resolveOk (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3166:685)
    at e._receiveReply (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3234:965)
    at e._receiveOneMessage (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3233:645)
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3232:74
    at e.fire (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:175:76)
    at a (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:311:740)
    at Socket.n._socketDataListener (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:311:959)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at Pipe.onread (net.js:594:20)

Looks like the issue was that I was using an older version of VSCode, i.e. 1.27.2.


Adds the ability for collections to not be indexed by Lunr by adding 'search: false' to _config.yml

This is an enhancement or feature.
Summary
I've implemented the ability for collections to be searchable by configuring the 'search' setting under collections on _config.yml. I've maintained the same pattern used for defining searchable docs on lunr-store.js.
Context
Although this is not related to any open GitHub issue, it was a very needed feature on a project of mine, and since it does not represent a major change on the code, and it seems like an useful feature for the average user, I've thought about sharing my simple code.

If you set search: false for your entire collection using Front Matter Defaults, you don't need a separate key for collection themselves.

If you set search: false for your entire collection using Front Matter Defaults, you don't need a separate key for collection themselves.
For example:
defaults:
  - scope:
      path: ""
      type: my_collection_name
    values:
      search: false
# job done :)

Oooooooh, now I get it!
Thanks, that's it...


[SPARK-13343] speculative tasks that didn't commit shouldn't be marked as success

Description
Currently Speculative tasks that didn't commit can show up as success of failures (depending on timing of commit). This is a bit confusing because that task didn't really succeed in the sense it didn't write anything.
I think these tasks should be marked as KILLED or something that is more obvious to the user exactly what happened. it is happened to hit the timing where it got a commit denied exception then it shows up as failed and counts against your task failures. It shouldn't count against task failures since that failure really doesn't matter.
MapReduce handles these situation so perhaps we can look there for a model.

How can this issue happen?
When both attempts of a task finish before the driver sends command to kill one of them, both of them send the status update FINISHED to the driver. The driver calls TaskSchedulerImpl to handle one successful task at a time. When it handles the first successful task, it sends the command to kill the other copy of the task, however, because that task is already finished, the executor will ignore the command. After finishing handling the first attempt, it processes the second one, although all actions on the result of this task are skipped, this copy of the task is still marked as SUCCESS. As a result, even though this issue does not affect the result of the job, it might cause confusing to user because both of them appear to be successful.
How does this PR fix the issue?
The simple way to fix this issue is that when taskSetManager handles successful task, it checks if any other attempt succeeded. If this is the case, it will call handleFailedTask with state==KILLED and reason==TaskKilled(“another attempt succeeded”) to handle this task as begin killed.
How was this patch tested?
I tested this manually by running applications, that caused the issue before, a few times, and observed that the issue does not happen again. Also, I added a unit test in TaskSetManagerSuite to test that if we call handleSuccessfulTask to handle status update for 2 copies of a task, only the one that is handled first will be mark as SUCCESS

Can one of the admins verify this patch?

cc @tgravescs

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Test build #92425 has started for PR 21653 at commit 8f7d981.

Test build #92425 has finished for PR 21653 at commit 8f7d981.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92425/
Test FAILed.

Test build #92426 has finished for PR 21653 at commit 980a933.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92426/
Test PASSed.

+1, changes look good to me.
@squito   see any problems with this approach?

@hthuynh2  can you fix the description "as success of failures" , this is just a copy of my typo in the jira.  Can you just change to be "as success"

I updated it. Thanks.

IIUC this speculative task is not really killed right ? It is actually ignored. Does that worth it to add a new TaskState for this case ?

@jiangxb1987 yes, you are correct that it is actually ignored. I think it doesn't worth to add a new TaskState because we might need to add changes in many places but does not add much benefit. Instead, I think we can add some message to the kill message to differentiate it from task that is actually killed and to inform the user.

Test build #92688 has started for PR 21653 at commit f66fcab.

Test build #92688 has finished for PR 21653 at commit f66fcab.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92688/
Test FAILed.

@squito Thanks for the suggestions. I updated it. Could you please have a look at it to see if there is anything else I need to change? Thanks.

Test build #92690 has started for PR 21653 at commit 3c655f2.

Test build #92690 has finished for PR 21653 at commit 3c655f2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92690/
Test PASSed.

lets review https://github.com/apache/spark/pull/21729 before this since its changing the type on killedByOtherAttempt

#21729 has been merged @hthuynh2  can you update this one?

Test build #93302 has started for PR 21653 at commit 2c7d33d.

@tgravescs I updated it. Can you please have a look at it when you have time. Thank you.

Test build #93302 has finished for PR 21653 at commit 2c7d33d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93302/
Test PASSed.

Test build #93418 has started for PR 21653 at commit b6585da.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93418/
Test FAILed.

Merged build finished. Test FAILed.

@tgravescs Can you please run the test again, thank you.

test this please

Test build #93447 has started for PR 21653 at commit b6585da.

Test build #93447 has finished for PR 21653 at commit b6585da.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93447/
Test FAILed.

Merged build finished. Test FAILed.

test this please

Test build #93474 has started for PR 21653 at commit b6585da.

Test build #93474 has finished for PR 21653 at commit b6585da.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93474/
Test FAILed.

test this please

test this please

test this please

test this please

Test build #4222 has started for PR 21653 at commit b6585da.

I kicked off the test manually at https://spark-prs.appspot.com/users/hthuynh2.  I dunno why the test triggering via comments stops workign on some prs

I kicked off the test manually at https://spark-prs.appspot.com/users/hthuynh2.  I dunno why the test triggering via comments stops workign on some prs

Test build #4222 has finished for PR 21653 at commit b6585da.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

merged to master, thanks @hthuynh2


I'm getting a weird error which says something about a pattern

Because you are using old version. 😭


added youtube video link and github organization link

I've added youtube video link and VueJS Projects organization url. VueJS projects organization https://github.com/vue-project
Always updated

@nickmessing I changed my PR

LGTM, but need to get approved by @kazupon

@nickmessing Thanks!


Unix socket binding - Errno::EADDRINUSE

Originally found in Puma:
https://github.com/puma/puma/issues/1521
Offending code in Ruby:
https://bugs.ruby-lang.org/issues/16277
require 'socket'

path = File.expand_path('listen.sock')
backlog = 5

s = UNIXServer.new(path)
if backlog
  s.listen backlog
else
  s.listen
end

File.delete(path) if File.exists?(path)

Listening twice does not throw Errno::EADDRINUSE in Linux but it does in WSL.

Spiritually #2915 (TCP over there).


Add test that starts server with file system backing

We recently had a bug that prevented the server from starting: #897
Let's add a test to start the server up and shut it down with a file system backing to prevent these errors in the future.

Fixed in #900


Upgrade to bevy 0.12

Updated the bevy and bevy_egui dependencies.
Also fixed several typos and #7.
All tests are green. Examples also work :)

Oh, I forget, I'm not sure how to handle the new AssetEvent::LoadedWithDependencies event. At the moment it's being handled the same way as the Added and Modified events. Any thoughts on this?

Details
    let mut changed = HashSet::default();
    let mut removed = Vec::new();
    for event in shader_events.read() {
        match event {
            AssetEvent::Added { id }
            | AssetEvent::Modified { id }
            | AssetEvent::LoadedWithDependencies { id } => {
                changed.insert(id.clone());
            }
            AssetEvent::Removed { id } => {
                changed.remove(id);
                removed.push(id.clone());
            }
        }
    }

https://github.com/Zheoni/bevy_pixel_buffer/pull/8/commits/0884571fed6d53445691832ef3269177dcade4a0#diff-31a275d3425f4b01b1b738927e79db292fc85fdde740a246db7d41bc515ed59cR244-R256
    // Update image bind group cache
    let mut invalid = HashSet::default();
    for event in image_events.read() {
        match event {
            AssetEvent::Added { id }
            | AssetEvent::Modified { id }
            | AssetEvent::Removed { id }
            | AssetEvent::LoadedWithDependencies { id }
                if buffer_images.contains(id) =>
            {
                invalid.insert(id.clone());
            }
            _ => {}
        }
    }

https://github.com/Zheoni/bevy_pixel_buffer/pull/8/commits/0884571fed6d53445691832ef3269177dcade4a0#diff-31a275d3425f4b01b1b738927e79db292fc85fdde740a246db7d41bc515ed59cL265-R281

Thank you so much! I did not have time to update to this release. About the new asset event, I honestly don't know either. We can leave it like this and hope it's the correct decision 😅
I also have a question. What GPU do you have? Since the last update I have swapped my GPU from nvidia to amd, and now I'm getting this error printed every frame, everything works though. It also prints in the old version, so it's not your update.

Opened an issue for this #9

I have an Nvidia GPU, have no idea what the problem might be :(
Maybe you should create a new issue in the bevy repo


Compiler: missing support for CANCEL, IOSIGNAL, POINTERFILTER?

Looking at the compiler code, it seems that the following EPOC32 keywords are not handled:

CANCEL
IOSIGNAL
POINTERFILTER

I swear, every time I think I’ve gone through the whole list…

Hehe. The list of OPL opcodes is such a mess…
I’ve compared with my own referential, it should be comprehensive (for EPOC32) with these 3 additions.
I’ll now compare the return value types and number of parameters for each command and their data types.