Microsoft.Cosmos.Database.Emulator.exe error generating new SSL Certificate

Issue seen: CosmosEmulatorSecrets is missing in LocalComputer\My and LocalComputer\Root and error 0x8009000f is throwin when attempting to generate the new certificate with the steps listed below. Running the emulator inside the Docker container works.
Following items that I have attempted:
Attempt A:
1. Open cmd.exe with Administrator
2. Navigate to CosmosDB Install folder with this command
C:\Program Files\Azure Cosmos DB Emulator
3. Run this command to ensure the CosmosDB Emulator is shutdown
Microsoft.Azure.Cosmos.Emulator.exe /Shutdown
4. Run this command to generate the missing certificates:
Microsoft.Azure.Cosmos.Emulator.exe /GenCert
Attempt B:
1. Uninstall Azure CosmosDB Emulator
2. Remove all instances of the Emulator from any Docker containers
3. Remove all instances of CosmosEmulatorSecrets, DocumentDbEmulatorCertificate, and CosmosEmulatorContainerCertificate from LocalComputer > Personal > Certificates and LocalComputer > Trusted Root Certification > Certificates
4. Remove any existing folders named CosmosDBEmulator from C:\Users$username\AppData\Local
5. Remove any remnants of containers that utilized the emulator
6. Ensure OneDrive is not backing up C:\Users$username\AppData or any root folders of the user account
7. Restart the computer
8. Install the latest version of CosmosDB Emulator from this link: https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator?tabs=ssl-netstd21
9. Verify existence of the CosmosEmulatorSecrets and DocumentDbEmulatorCertificate in LocalComputer\My
With a clean install of Windows 10, the CosmosDB Emulator appears to work as expected, but as time goes on and more updates are installed, the system gets back to a similar state as reported where it throws the 0x8009000f error when attempting to load the browser or generating a new certificate. These systems also have the ServiceFabric application installed, but this doesn't appear to be the main cause as I can still utilize the CosmosDB /GenCert command without issue.

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

ID: 109ed3f8-faf1-92b9-bf50-4be52e9099d4
Version Independent ID: ebc5326a-46da-6bc1-1f47-01a8e16d11fb
Content: Install and develop locally with Azure Cosmos DB Emulator
Content Source: articles/cosmos-db/local-emulator.md
Service: cosmos-db
GitHub Login: @StefArroyo
Microsoft Alias: esarroyo

@morris-richard Thank you for the detailed feedback. This is being assigned to the content author to evaluate as appropriate.

#assign:seesharprun

Thanks @morris-richard for taking the time to report this issue.
Unfortunately, this is the GitHub repo for documentation. If you have a product question or bug, you should give your feedback using the Microsoft Q&A site for Azure Cosmos DB.
Since there's no action item here in docs, I will go ahead and close the issue here.
#please-close


when the code will be released？

Hi, thank you for the great work. I'm wondering when the code will be uploaded.

me too

I'm waiting, too. Looking forward to uploading soon.

I'm so sorry for the late response.
(It seems github doesn't remind me,
you may consider to send me an email if I don't reply immediately, I check email every day.)
As the paper has been submitted to TIP and under review,
I plan to release the code after the first round of review is ready.
It should be a long-time for several months.

Ok, thank you for reply,good luck.
------------------ 原始邮件 ------------------
发件人: "Jie<EMAIL_ADDRESS>发送时间: 2019年9月19日(星期四) 上午6:07
收件人<EMAIL_ADDRESS>抄送: "liuhaojie"1356280370<EMAIL_ADDRESS>主题: Re: [kakaxi314/GuideNet] when the code will be released？ (#2)
I'm so sorry for the late response.
(It seems github doesn't remind me,
you may consider to send me an email if I don't reply immediately, I check email every day.)
As the paper has been submitted to TIP and under review,
I plan to release the code after the first round of review is ready.
It should be a long-time for several months.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@kakaxi314  Is the code available now?

I just visited this link（https://github.com/kakaxi314/GuideNet） and still can't get the code.
------------------ 原始邮件 ------------------
发件人: "Chengqi<EMAIL_ADDRESS>发送时间: 2019年12月27日(星期五) 中午11:48
收件人<EMAIL_ADDRESS>抄送: "liuhaojie"<1356280370<EMAIL_ADDRESS>主题: Re: [kakaxi314/GuideNet] when the code will be released？ (#2)
@kakaxi314  Is the code available now?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

ur code does not seem to be publicly available now


Add support for Firefox OS (updated)

This is a resubmission of PR #93, rebased against a more recent master branch.
Looks like @mwbrooks and/or @timkim might be interested in these changes?
(FWIW, I'm starting to take some baby steps in picking up things rodms10 was working on. Any feedback is very welcome, since I'm totally new on this stuff.)

Rebased against master branch and resolved conflicts

I assume this pr is dead along with Firefox OS. Please close.

Firefox OS isn't actually dead, but this PR's pretty bit rotted & I'm no longer on the team working on this so might as well


[FEATURE] DlSmartSearch - Value Aliasing

Is your feature request related to a problem? Please describe.
Many times when we query resources, they are connected to other resources only by ID. For example, searching for an execution by pipeline ID. For better UX, we would like to allow the user to search by name (which makes sense in cases where the name is unique), for ease of use, yet the actual value that will be sent in the query is the ID.
Describe the solution you'd like
Allow aliasing values of specific fields using a dictionary (key is the alias, value is the actual value), and allow the user to input "value" that matches the key aliases.
Should support auto-suggest, should be strict (because an unknown alias can't be converted)

Progress:
https://github.com/dataloop-ai/components/assets/146977958/8f15f463-5fe0-433d-86a5-64da53350b00


Oculus Rift DK1: The image looks shifted or cross-eyed

I'm trying to setup Oculus Rift DK1 to work in SteamVR through OSVR as well as SteamVR-OSVR. It took a few days of searching and trying with no success. The image looks OK in OSVR test, but in SteamVR it looks like eyes are swapped or something.

Graphics card(s):
AMD R7 265, Driver Version 16.40.2311-160916a-307259E
Operating system:
Win 10
Version of SteamVR:
Latest,<PHONE_NUMBER>
Version of SteamVR-OSVR:
SteamVR-OSVR-Win-Build-v0.1-344-g52bd105-core-v0.6-2080-g8a0429a4-buildid-212.7z

Please find some data from logs that might be useful:
vrcompositor.txt
vrserver.txt

I believe I'm having the same issue. I'll try to post my logs and configs when I get to my computer. If someone could point me in the direction of where the problem might be, I'd be more than willing to do some development to fix this issue.

has there been any progress on this issue? I've been searching forever and there's been no hope.

Same issue with SteamVR-OSVR-Win-Build-v0.1-344-g52bd105-core-v0.6-2080-g8a0429a4-buildid-212.7z
I'll try compile from master but I kinda doubt it's fixed there.

it seems this actually works. I grabbed this guys dll, but afaik he simply compiled it:
https://www.reddit.com/r/OSVR/comments/7maypm/driver_fix_for_dk1diy_headsets/


[kf5codecs] add explicit gperf dependency

Describe the pull request

What does your PR fix?
This prevents built failures on macOS with its outdated GNU gperf 3.0.3 that chokes on kf5codec's 'register' specifiers.
Also wraps paths in quotes and removes the line deleting /etc, which isn't being populated.

Which triplets are supported/not supported? Have you updated the CI baseline?
No change.

Does your PR follow the maintainer guide?
No change.

Yes

/azp run

Please get failure logs here.

@JackBoosY I addressed @BillyONeal concern, all issues are fixed now.

@wrobelda Yes, we are handling this.


Bug Fix

Thanks for this. I assume it wont take before @kooimens and @henkjanvries start asking for personalized dashboard order etc so i gonna see if i cant find a way to do that.

I think is just a matter of add in @require(member_of(htpc.role_user)) to save_menu & save_dash functions on root.py

ha @Hellowlol i don't really mind! but it does look good @wmariz!
i just have 1 practical question, ive made personalised adjustments to files for the auth of users. if i want this, ill probably have to that again won't i?

Yes, you have to do it again for each update. If i where you id fork the project. git checkout -b modauth. Do your changes and push them to github.
So after each upgrade you can:
git checkout master2
git merge modauth

@wmariz I wish it was that simple.. :P the pain is the db, the rest is easy.
I find it every hard to do even trivial stuff in sqlobject (like adding columns later etc)


Add hw event schema

Signed-off-by: Jack Ding<EMAIL_ADDRESS>

@aneeshkp correct me if I am wrong, we would want to update the event_spec.json per the updates to the document spec?
As indicated here: The Redfish data should be validated with https://redfish.dmtf.org/schemas/v1/Event.v1_4_1.json schema
https://github.com/redhat-cne/spec/pull/4/files#diff-de0aff663d1e0e4dc52f62e92afaf220b02b0ea4735d41ecc40a33c2aadd409cR507

We have an open issue in sdk-go for consolidating event and hw-event: https://github.com/redhat-cne/sdk-go/issues/24
I'm thinking we can have a consolidated schema like the following by introducing an object type for ValueType.
// ValueType ...
type ValueType string

const (
	// ENUMERATION ...
	ENUMERATION ValueType = "enumeration"
	// DECIMAL ...
	DECIMAL       ValueType = "decimal64.3"
	// OBJECT contains JSON formatted structure
	OBJECT ValueType = "object"
)

{
  "id": "5ce55d17-9234-4fee-a589-d0f10cb32b8e",
  "type": "event.redfish-event",
  "time": "2021-02-05T17:31:00Z",
  "data": {
    "version": "v1.0",
    "values": [
      {
        "resource": "/cluster/node/node1/redfish/event",
        "data_type": "notification",
        "value_type": "object",
        "value": {
<EMAIL_ADDRESS>"/redfish/v1/$metadata#Event.Event",
<EMAIL_ADDRESS>"/redfish/v1/EventService/Events/5e004f5a-e3d1-11eb-ae9c-3448edf18a38",
<EMAIL_ADDRESS>"#Event.v1_3_0.Event",
          "Context": "any string is valid",
          "Events": [
            {
              "Context": "any string is valid",
              "EventId": "2162",
              "EventTimestamp": "2021-07-13T15:07:59+0300",
              "EventType": "Alert",
              "MemberId": "615703",
              "Message": "The system board Inlet temperature is less than the lower warning threshold.",
              "MessageArgs": [
                "Inlet"
              ],
<EMAIL_ADDRESS>1,
              "MessageId": "TMP0100",
              "Severity": "Warning"
            }
          ],
          "Id": "5e004f5a-e3d1-11eb-ae9c-3448edf18a38",
          "Name": "Event Array"
        }
      }
    ]
  }
}

@aneeshkp correct me if I am wrong, we would want to update the event_spec.json per the updates to the document spec?
As indicated here: The Redfish data should be validated with https://redfish.dmtf.org/schemas/v1/Event.v1_4_1.json schema
https://github.com/redhat-cne/spec/pull/4/files#diff-de0aff663d1e0e4dc52f62e92afaf220b02b0ea4735d41ecc40a33c2aadd409cR507

@aneeshkp correct me if I am wrong, we would want to update the event_spec.json per the updates to the document spec?
event_spec show the message schema received  by the consumer, in case of HW events , Consumer has two schema to  validate


Adding Vulnerability ID to the HTML page title

It would be a neat quality-of-life feature to have the vuln ID appear in the title, for easier navigation between browser tabs.
A quick look at the app routes shows that the vuln_view.html could be changed to update the document title, possibly inside the

Thanks a lot for reaching out hazimeh, that's a good point!
I'll address this as soon as possible.

Thanks again for filing this. I've fixed this in (https://github.com/google/vulncode-db/commit/6baaa0d58e3e667052eac6787e05ecdc7fe03baf) and this is live. For example, see the page title on https://www.vulncode-db.com/CVE-2014-0160 :).


code of yolo

Hi, twangh! Do you have plan to release the code of YOLO?

Hi, yolo distillation is third party implementaion,  we dont have the code yet

Oh, thanking for your reply!


Don't offer completions / auto-imports for class/function/parameter names

Describe the bug
For tests automatically adds import for fixture. Pytest know where find out fixture(conftest.py), not required make auto import for it.
To Reproduce

install pytest
create conftest.py with that example code:

import pytest

@pytest.fixture()
def ExampleFixture():
    return ['This', 'is', 'example', 'fixture']

create test_example.py with that code:

import pytest

def test_is_instance_list(ExampleFixture):
    assert is instance(ExampleFixture, list)

Expected behavior
Import for ExampleFixture is not added
VS Code extension or command-line
VS Code extension
Version: v2020.7.3

Hey @anatoly-kor!
Just to be clear, what you're describing is that you are seeing a completion that auto-imports the fixture and you wouldn't expect this behaviour?

Hi @savannahostrowski. Yes! I mean when test(with fixture) is wrote, auto-import add imports, but doesn't must because for pytest not required import fixture modules.
Quote from docs:

You don’t need to import the fixture you want to use in a test, it automatically gets discovered by pytest.

Thanks for confirming. In this case, the problem is that completions are offered in some contexts where they don't make sense (parameter, function, and class names). If you're defining a function, we shouldn't try to autocomplete a parameter name (because we would never know what the right names are for a brand new function).

Seeing the same issue here. Maybe a context could be added to the auto-import feature to disable it when a conftest.py file is in the same directory.
Overall I must say I've found the auto-import feature to be more of a hurdle than anything else. When an auto-import gets added is usually a duplicate or something I didn't really want, and in most case the module from which I'm adding a class or function is not discovered. It would be nice if the feature could be disable completely.

If you have feedback about what could be improved with auto-imports in general, we'd appreciate those in a separate issue. If we are offering something that's a duplicate or something you don't want, then that's something to solve. This specific issue is about offering completions for names we can't actually know (brand new funcs/classes/parameters) and would be hit regardless of the auto-import setting.

It would be nice if the feature could be disable completely.

That is #64, which we plan to do.

Right, I didn't want to confuse the issue and #64 sounds good.
To avoid auto-importing fixtures, something that could be checked is if the object has the attribute _pytestfixturefunction and if so not offer auto-import.

I like the solution proposed in #178. Today, the setting python.analysis.autoImportCompletions allows either true or false, but instead it could be always, ask or never. That way we don't need special rules for specific test libraries such as pytest.

That level of control over completions is not possible in VS Code as it stands now. We return a list of completions given a location in the code, and VS Code displays it. We can't defer this or ask for user input if they want to expand some extra stuff, because this is effectively a request for state where there's only once answer given the current document and location.

The auto import feature is really useful in most scenarios, however as stated in this issue, it can be a little inconvenient with pytest when you're entering a fixture into your test function's signature and it auto-imports. Pytest does not require you to import its fixtures from a conftest.py file since its test discovery process looks for that filename.
By the design of the pytest library, users use a filename that is always called conftest.py and can be at different directory levels within a project directory structure to indicate the scope of the contained fixtures.
Is it possible to create an array or object setting to be used in the workspace's settings.json that takes a glob pattern to ignore a certain directory and/or filename?
For example, VS Code's seach.exclude setting is one of many examples using this.
The setting might look something like:
    "python.analysis.autoImportExclusions": {
        "conftest.py": true,
        "**/conftest.py": true,
        ...
    },

Before we add any settings, we need to fix this completion context issue and not offer completions in conditions where we can't actually know a name. I wouldn't want to add a setting to work around an issue that we're going to end up fixing anyway (and that setting in particular is not as simple as you might think).

OK, if PyLance doesn't add auto-imports for pytest fixtures once you've put in the fix, then I'm not worried how that's achieved. If a setting isn't required, then even better!

This issue has been fixed in version 2020.11.1, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#2020111-11-november-2020


Added the Detector response file change to omit fitting PSF of bins not used in analysis

Changed HAL to read and fits PSFs of the bins specified in the fit during an analysis

@rishibbdb almost all the CI tests are failed. Can you take a look and try to solve them?


use port 4000 instead of 80 on host

Proposed changes
I changed the docker-compose.yml example to map port 4000 to the host, as described later in the tutorial:

"Map port 4000 on the host to web’s port 80."

Thanks for the great tutorial!
Ryan

Deploy preview for docsdocker ready!
Built with commit bcd571efffaacc837751ba15f0b5f4a80b657125
https://deploy-preview-7867--docsdocker.netlify.com

LGTM


[SPARK-12536] [SQL] Added "[]" in Explain Outputs For Empty LocalRelation and LocalTableScan

The filter Filter (False) generates an empty LocalRelation in SimplifyFilters. In the current Explain, the optimized and physical plans look confusing.
For example,
val df = Seq(1 -> "a").toDF("a", "b")
df.where("1 = 0").explain(true)

== Analyzed Logical Plan ==
a: int, b: string
Filter (1 = 0)
+- Project [_1#0 AS a#2,_2#1 AS b#3]
   +- LocalRelation [_1#0,_2#1], [[1,a]]

== Optimized Logical Plan ==
LocalRelation [a#2,b#3]

== Physical Plan ==
LocalTableScan [a#2,b#3]

After the fix, the Optimized Logical Plan and Physical Plan are changed to
== Optimized Logical Plan ==
LocalRelation [a#2,b#3] []

== Physical Plan ==
LocalTableScan [a#2,b#3] []

The original PR is: https://github.com/apache/spark/pull/10494

@cloud-fan @marmbrus Hopefully, my understanding is right. Feel free to let me know if the fix needs any change. Thank you!

Test build #48946 has started for PR 10646 at commit 3ac9735.

Test build #48946 has finished for PR 10646 at commit 3ac9735.

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/48946/
Test PASSed.

Test build #49091 has started for PR 10646 at commit 4ae1ce7.

Test build #49091 has finished for PR 10646 at commit 4ae1ce7.

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/49091/
Test FAILed.

Test build #49092 has started for PR 10646 at commit 18091f7.

Test build #49092 has finished for PR 10646 at commit 18091f7.

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/49092/
Test FAILed.

Merged build finished. Test FAILed.

retest this please.

Test build #49152 has started for PR 10646 at commit 18091f7.

Test build #49152 has finished for PR 10646 at commit 18091f7.

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/49152/
Test PASSed.

LGTM

Thank you for your help! Sorry for wasting you a lot of time on it! @cloud-fan

@gatorsmile I'm actually not sure whether the new format is more clear. Do you mind closing this? Thanks.

Sure, let me close it.


New custom 404 page

@garaynakca here is the draft pull request for the 404 page. The branch is called new-404-page.

:books: Documentation preview :books:: https://civicactions-handbook--1043.org.readthedocs.build/en/1043/

Crossing-linking comments https://github.com/CivicActions/guidebook/commit/98c8dc1f1021f37d755b77d84beac113035b318f#comments

@dmundra The preview for this branch displays the readme/homepage rather than the 404.  Is there a way to preview the 404?

@dmundra The preview for this branch displays the readme/homepage rather than the 404. Is there a way to preview the 404?

Ya try this URL https://civicactions-handbook--1043.org.readthedocs.build/en/1043/not-found (I just put random text at the end to try a page that doesn't exist).

Hi, @dmundra .  Does the CSS also update with the commits?  I made a change to the leadtext class, but don't see it displaying here: https://civicactions-handbook--1043.org.readthedocs.build/en/1043/not-found
Thanks!

Hi, @dmundra . Does the CSS also update with the commits? I made a change to the leadtext class, but don't see it displaying here: https://civicactions-handbook--1043.org.readthedocs.build/en/1043/not-found Thanks!

Hey @garaynakca, it does. You might need to do a cache clear. This is what I am seeing:

Is that match what you are seeing?

@dmundra Got it!  Thank you...  starting to look closer.

@garaynakca Would like us to close out the 2 PRs related to the designs you created for the 404 and home page. Is there anything @dmundra or I can do to help you?


Consider migration to MMD6

MultiMarkdown 6 offers faster parser with some amount of changes to parsing. Considering migrating to the new engine would potentially be useful.

This is currently limited by fletcher/MultiMarkdown-6#38, which is required for many scriptorium documents using raw LaTeX source for fine-grained control of formatting issues. Other features have been issues as PR's or are awaiting in relevant branches.


Disabled flaky test: test_mkldnn.test_activation

Description
Disable flaky test: test_mkldnn.test_activation. Tracked in https://github.com/apache/incubator-mxnet/issues/12377

Please refer the RCA in #12377 and wait a moment for the merge.
We need a better solution :)

@pengzhao-intel Sure) But it's better to disable a flaky test first and so that PR's from others are not blocked and then add it again with a proper fix.

We have continues failures on the CI for that:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/master/1534/pipeline
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/master/1533/pipeline/
We need an urgent merge for this.

@lebeg please see my comments on #12377.
Could you try to change eps number and run these cases again?

Would that be alright with you @pengzhao-intel @luobao-intel?

It's fine for us. Please go ahead.