docs(new): Add TSDoc to Coverage class

Please re-review :)

@hashseed LGTM! I think after you merged in main you need to re-generate the docs and then CI will be happy.


lz4w does nothing for file names/paths that contain a capital letter

I was wondering why it worked when rescomp called it and not when I did from a Makefile. Turns out that's because "pack.in" is all lowercase. This only effects OS/filesystems with case sensitive names, probably.
$ java -jar ~/mars/bin/lz4w.jar p res/Stage/Almond.pxm test.cpxm
res/stage/almond.pxm
$ mv res/Stage res/stage
$ mv res/stage/Almond.pxm res/stage/almond.pxm
$ java -jar ~/mars/bin/lz4w.jar p res/Stage/Almond.pxm test.cpxm
Packing res/stage/almond.pxm...
Stats:
  Num segment = 160 - 30 long match(s) - 0 miss(es)
  Mean literal size = 1.6
  Mean match size = 6.0
Initial size 2408 --> packed to 882 (36%)

oh indeed, stupid bug i wasn't aware because of windows OS doesn't take care of it. Thanks for reporting, will be fixed soon !


[Docs]: Add tracking pixel to Documentation

Is there an existing issue for this?

[X] I have searched the existing issues

Engineering Ticket Link
NA
Release Date
NA
Release Number
NA
First Draft
No response
Loom video
No response
Discord/slack/intercom Link if needed
No response
PRD
No response
Test plan/cases
No response
Use cases or user requests
Add tracking pixel.

Fixed as part of PR - #1030


AMBARI-24648. Log Search: add simple file based authorization.

What changes were proposed in this pull request?
Add new simple file based authorization. Implemented in RoleDao (currently only contains that file based authorization), can be used only with file based or JWT authentication.
How was this patch tested?
UTs passed.
FT: with new docker env. if role is changed, login fails with 403 status code.
Please review @g-boros @kasakrisz @swagle

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

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


Cloning injectors with registered services

Cloning dependency container would be useful for unit testing.
User can reuse production service registrations and replace some service to mock service.
example:
var injector *do.Injector;
func init() {
    do.Provide[Service](injector, func (i *do.Injector) (Service, error) {
        return &RealService{}, nil
    })
    do.Provide[*App](injector, func (i *do.Injector) (*App, error) {
        return &App{i.MustInvoke[Service](i)}, nil
    })
}

func TestService(t *testing.T) {
    i := injector.Clone()
    defer i.Shutdown()
    // replace Service to MockService
    do.Provide[Service](i, func (i *do.Injector) (Service, error) {
        return &MockService{}, nil
    }))
    app := do.Invoke[*App](i)
    // do unit testing with mocked service
}

This usecase is relying on service-overriding behavior and inconsistent with https://github.com/samber/do/issues/1 , so it would be nice if service-overriding behavior is officially supported.

Hi @suzuki-safie and thanks for your contribution.
I like the idea of cloning+overriding injectors for tests, especially for mocks!
But I'm not really sure service overriding should be enabled by default. Such a design might lead to dangerous behavior for lazy loaded services.
I'm thinking about 2 alternatives:

A do.Replace[T](*do.Injector, func (*do.Injector) (T, error)) helper, similar to do.Provide
An option to injector constructor: do.NewWithOpts(&do.InjectorOpts{ AllowServiceOverride: true })

The second option seems better.
WDYT?

Codecov Report

Merging #6 (d1b50dd) into master (7a2ab9a) will decrease coverage by 0.53%.
The diff coverage is 80.76%.

@@            Coverage Diff             @@
##           master       #6      +/-   ##
==========================================
- Coverage   88.10%   87.57%   -0.54%
==========================================
  Files           6        6
  Lines         328      354      +26
==========================================
+ Hits          289      310      +21
- Misses         31       35       +4
- Partials        8        9       +1

Flag
Coverage Δ

unittests
87.57% <80.76%> (-0.54%)
:arrow_down:

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

Impacted Files
Coverage Δ

service.go
88.88% <ø> (ø)

service_eager.go
65.21% <0.00%> (-6.22%)
:arrow_down:

injector.go
87.80% <81.25%> (-0.71%)
:arrow_down:

service_lazy.go
89.85% <100.00%> (+1.33%)
:arrow_up:

Continue to review full report at Codecov.

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

A do.Replace[T](*do.Injector, func (*do.Injector) (T, error)) helper, similar to do.Provide
I like this option. I think do.Replace(...) expresses it's intent more clearly.

@samber
Sorry, I didn't have enough time to do this PR.
Thank you for merging!


[Other issue]: Could not install dependecies using rosdep

Before proceeding, is there an existing issue or discussion for this?

[X] I have done a search for similar issues and discussions.

Description
I try to install ros humble dependecies using this command "rosdep install --from-paths src --ignore-src --rosdistro humble -y"
but i got this error again.
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
rmf_robot_sim_gz_plugins: Cannot locate rosdep definition for [gz_transport_vendor]
rmf_building_sim_gz_plugins: Cannot locate rosdep definition for [gz_transport_vendor]
rmf_building_map_tools: Cannot locate rosdep definition for [gz_fuel_tools_vendor]
rmf_demos_gz: Cannot locate rosdep definition for [gz_sim_vendor]
"  i searched this error but humble does  not have a this type of vendor packages.

Please re-open a ticket with the bug report template and fill out all details of your setup in the form.
My guess would be that you're trying to build packages with main branch checked out on Ubuntu 22.04. We have migrated main to Ubuntu 24.04 with support for Rolling and Jazzy distros. If you're building with Humble, please checkout the humble branches for each repo.


Choma similarity_search_with_score (and similar methods) don't populate the document.id property of the returned documents.

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
I want to get the document id from the documents I find with similarity_search_with_score but the id's aren't being set to the documents when they are created.
Here is my test code:
def test_basic_operations_with_langchain():
    token = os.environ.get('CHROMA_TOKEN')
    client = chromadb.HttpClient(
        settings=Settings(chroma_client_auth_provider="chromadb.auth.token_authn.TokenAuthClientProvider",
                          chroma_client_auth_credentials=token))
    test_collection_name = "test_collection"

    try:
        client.delete_collection(test_collection_name)
    except:  # noqa: E722
        pass

    collection = client.get_or_create_collection(test_collection_name)
    assert collection.name == test_collection_name
    assert collection.count() == 0

    EMBEDDING_MODEL_NAME = "sentence-transformers/all-mpnet-base-v2"
    EMBEDDING_MODEL_CHUNK_SIZE = 384

    embedding_model = HuggingFaceEmbeddings(
        model_name=EMBEDDING_MODEL_NAME,
        # multi_process=True,   # I found this causes crashes and slowness
        model_kwargs={"device": "cuda" if torch.cuda.is_available() else "cpu"},
        encode_kwargs={
            "normalize_embeddings": True
        },  # set True for cosine similarity
    )
    vector_db = Chroma(
        embedding_function=embedding_model,
        client=client,
        collection_name=test_collection_name,
        collection_metadata={"hnsw:space": "cosine"},
    )
    # Make new uid
    id = str(uuid.uuid4())
    test_doc = Document("hello world")
    test_doc.id = id
    test_doc.metadata["test"] = "test"
    vector_db.add_documents([test_doc])
    assert collection.count() == 1

    docs = vector_db.similarity_search_with_score("hello world", 1)
    assert len(docs) == 1
    assert docs[0][0].page_content == "hello world"
    assert docs[0][0].id == id

    client.delete_collection(test_collection_name)

Error Message and Stack Trace (if applicable)
Test output:
=================================== FAILURES ===================================
_____________________ test_basic_operations_with_langchain _____________________

    def test_basic_operations_with_langchain():
        token = os.environ.get('CHROMA_TOKEN')
        client = chromadb.HttpClient(
            settings=Settings(chroma_client_auth_provider="chromadb.auth.token_authn.TokenAuthClientProvider",
                              chroma_client_auth_credentials=token))
        test_collection_name = "test_collection"

        try:
            client.delete_collection(test_collection_name)
        except:  # noqa: E722
            pass

        collection = client.get_or_create_collection(test_collection_name)
        assert collection.name == test_collection_name
        assert collection.count() == 0

        EMBEDDING_MODEL_NAME = "sentence-transformers/all-mpnet-base-v2"
        EMBEDDING_MODEL_CHUNK_SIZE = 384

        embedding_model = HuggingFaceEmbeddings(
            model_name=EMBEDDING_MODEL_NAME,
            # multi_process=True,   # I found this causes crashes and slowness
            model_kwargs={"device": "cuda" if torch.cuda.is_available() else "cpu"},
            encode_kwargs={
                "normalize_embeddings": True
            },  # set True for cosine similarity
        )
        vector_db = Chroma(
            embedding_function=embedding_model,
            client=client,
            collection_name=test_collection_name,
            collection_metadata={"hnsw:space": "cosine"},
        )
        # Make new uid
        id = str(uuid.uuid4())
        test_doc = Document("hello world")
        test_doc.id = id
        test_doc.metadata["test"] = "test"
        vector_db.add_documents([test_doc])
        assert collection.count() == 1

        docs = vector_db.similarity_search_with_score("hello world", 1)
        assert len(docs) == 1
        assert docs[0][0].page_content == "hello world"
>       assert docs[0][0].id == id
E       AssertionError: assert None == '808971a7-f042-4306-864b-97af29c4837d'
E        +  where None = Document(metadata={'test': 'test'}, page_content='hello world').id

code/tests/test_basic_chroma_setup.py:99: AssertionError
=============================== warnings summary ===============================
<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.MessageMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.ScalarMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

code/tests/test_basic_chroma_setup.py::test_basic_operations_with_langchain
  /projects/myproj/.venv/lib/python3.12/site-packages/transformers/tokenization_utils_base.py:1601: FutureWarning: `clean_up_tokenization_spaces` was not set. It will be set to `True` by default. This behavior will be depracted in transformers v4.45, and will be then set to `False` by default. For more details check this issue: https://github.com/huggingface/transformers/issues/31884
    warnings.warn(

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================
FAILED code/tests/test_basic_chroma_setup.py::test_basic_operations_with_langchain
======================== 1 failed, 3 warnings in 6.21s =========================
Finished running tests!

I would expect the result:
=============================== warnings summary ===============================
<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.MessageMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.ScalarMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

code/tests/test_basic_chroma_setup.py::test_basic_operations_with_langchain
  /projects/myproj/.venv/lib/python3.12/site-packages/transformers/tokenization_utils_base.py:1601: FutureWarning: `clean_up_tokenization_spaces` was not set. It will be set to `True` by default. This behavior will be depracted in transformers v4.45, and will be then set to `False` by default. For more details check this issue: https://github.com/huggingface/transformers/issues/31884
    warnings.warn(

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
======================== 1 passed, 3 warnings in 7.26s =========================
Finished running tests!

Description
I am using:
langchain==0.2.15
langchain-chroma==0.1.3
langchain-community==0.2.15
langchain-core==0.2.37
langchain-huggingface==0.0.3
langchain-text-splitters==0.2.2
chromadb==0.5.3

I am calling vector_db.similarity_search_with_score(...) or vector_db.similarity_search(...) and the documents returned never have an id.
I can't see a way of getting the documents give me an id. I though about adding a kwargs include ids. But the documentation for the underlying query says it always returns ids.  I think the issue is in your method:
def _results_to_docs_and_scores(results: Any) -> List[Tuple[Document, float]]:
    return [
        # TODO: Chroma can do batch querying,
        # we shouldn't hard code to the 1st result
        (Document(page_content=result[0], metadata=result[1] or {}), result[2])
        for result in zip(
            results["documents"][0],
            results["metadatas"][0],
            results["distances"][0],
        )
    ]

from: https://github.com/langchain-ai/langchain/blob/51c4393298801b75f98cf8a060376237a734eac1/libs/partners/chroma/langchain_chroma/vectorstores.py#L43-L53
It doesn't use the id.
This fix should be very easy:
def _results_to_docs_and_scores(results: Any) -> List[Tuple[Document, float]]:
    return [
        # TODO: Chroma can do batch querying,
        # we shouldn't hard code to the 1st result
        (Document(id =result[0], page_content=result[1], metadata=result[2] or {}), result[3])
        for result in zip(
            results["ids"][0],
            results["documents"][0],
            results["metadatas"][0],
            results["distances"][0],
        )
    ]

System Info
System Information

OS:  Linux
OS Version:  #1 SMP Fri Mar 29 23:14:13 UTC 2024
Python Version:  3.12.4 (main, Jul 19 2024, 17:20:16) [GCC 11.4.1 20231218 (Red Hat 11.4.1-3)]

Package Information

langchain_core: 0.2.37
langchain: 0.2.15
langchain_community: 0.2.15
langsmith: 0.1.108
langchain_chroma: 0.1.3
langchain_huggingface: 0.0.3
langchain_text_splitters: 0.2.2

Optional packages not installed

langgraph
langserve

Other Dependencies

aiohttp: 3.10.5
async-timeout: Installed. No version info available.
chromadb: 0.5.3
dataclasses-json: 0.6.7
fastapi: 0.112.2
httpx: 0.27.2
huggingface-hub: 0.24.6
jsonpatch: 1.33
numpy: 1.26.4
orjson: 3.10.7
packaging: 24.1
pydantic: 2.8.2
PyYAML: 6.0.2
requests: 2.32.3
sentence-transformers: 3.0.1
SQLAlchemy: 2.0.32
tenacity: 8.5.0
tokenizers: 0.19.1
transformers: 4.44.2
typing-extensions: 4.12.2

Until there is a fix I am patching my code with this helper method that has my fix in it:
####################################################################################################
# This is PATCHED code from the original langchain_chroma module
####################################################################################################
# See bug: https://github.com/langchain-ai/langchain/issues/26860

def similarity_search_with_score_with_id(
    vector_db: Chroma,
    query: str,
    k: int = DEFAULT_K,
    filter: Optional[dict[str, str]] = None,
    where_document: Optional[dict[str, str]] = None,
    **kwargs,
) -> list[tuple[Document, float]]:
    if vector_db._embedding_function is None:
        results = vector_db._collection.query(
            query_texts=[query],
            n_results=k,
            where=filter,                   # type: ignore
            where_document=where_document,  # type: ignore
            **kwargs,
        )
    else:
        query_embedding = vector_db._embedding_function.embed_query(query)
        results = vector_db._collection.query(
            query_embeddings=[query_embedding], # type: ignore
            n_results=k,
            where=filter,                       # type: ignore
            where_document=where_document,      # type: ignore
            **kwargs,
        )

    return _results_to_docs_and_scores(results)

def _results_to_docs_and_scores(results) -> list[tuple[Document, float]]:
    return [
        # TODO: Chroma can do batch querying,
        # we shouldn't hard code to the 1st result
        (Document(id =result[0], page_content=result[1], metadata=result[2] or {}), result[3])
        for result in zip(
            results["ids"][0],
            results["documents"][0],
            results["metadatas"][0],
            results["distances"][0],
        )
    ]
####################################################################################################
# End of PATCHED code
####################################################################################################

Incase anyone finds it useful

Not all vectorstores currently support this. Someone can make a PR to add support for returning the ID as part of the document.
The ID in documents was added only a few months ago, and it still considered optional

Hi @eyurtsev,
Thanks for your reply. Are you suggesting "someone" is me? I am happy to do it. But I don't want to break things, the code I highlighted is specifically in chroma, so I am guessing my suggested change would be ok. But I would need more info to do a better / more complete job.
Thanks
Kris

@KrisTC ha sorry i didn't mean to imply that. This was for anyone in the community who wants to tackle this. I should read more carefully what I write :)

@eyurtsev We are looking to contribute to this issue. Since @KrisTC already provided a fix for Chroma, we can potentially write test cases for it and also investigate the remaining vectorstores and add support for the ones that are missing this functionality. I believe we are targeting only vectorstores with similarity search, would that be correct? If you have more detailed information on which vectorstores need an update, that would be greatly appreciated.

There's a standard test suite in the standard tests package that covers a lot of the relevant edge cases. You can git grep through the codebase to find example usage
git grep "standard_test"

Some update, any suggestions are appreciated:

We looked through langchain/libs/partners and found these vectorstores also not do populate Document's id: q_drant, couchbase, mongodb. We haven't fully checked langchain/libs/community. We will focus on partners first, if there's no preference.

Applying the above fix by OP for chroma does not fail any test. We are planning to add some unit test cases to ensure Document's id is populated and returned correctly.

Hello, @eyurtsev  We have the fix and test cases for ChromaDB. Should we create a pull request for Chroma DB first and work on the other vector stores later on other pull request only or should we create a pull request after fixing other vector stores altogether

Individual PRs would be great

Just created a PR #27366


Update led_strip.py

Added the ability to use RGBW Neopixels. When defining strip use NEOPIXELW instead of NEOPIXEL
Example:
STRIP_TYPE = LEDStripModule.NEOPIXELW
assign a colour to a RGBW pixel, the below example turns on the white element.
strip.pixels[px] = (0, 0, 0, 255)

Thank you for this. Seeing as it uses the same Neopixel class as regular strips, I am wondering if it would be better to have an extra parameter that denotes if it is RGBW rather than it being a completely new type of strip

That would make sense and basically what the 'pixel_order' parameter is, when working out what was happening, I just added to the setting up of the Neopixels with no issues, I have come across Neopixels where the order of the channels are different.


ARROW-10693: [Rust] [DataFusion] Add support to left join

This PR adds support to the left join in DataFusion.
The PR is divided in two:

the first commit extends MutableDataArray with an API to allow itself be extended by null values.
the second commit uses this new API to add enable left joins in DataFusion

fyi @alamb @andygrove :)

I haven't reviewed in detail yet but LGTM

Awesome that the "main" join support is now in!


Add before/after events to Generator class

As per the documentation here https://www.tapestry.cloud/documentation/events/#step-events

Implemented by 6c123de3ffbd0d6acb12c15874129fab90c127b2


Question: what's the difference between r (replace) and s (sync all)?

👋🏻
Excellent plugin by the way. Really slick and good user experience 👍🏻 Thank you for building this!
Quick question (as per the title): it seems like <leader>r replaces all instances, but that sounds a lot like <leader>s (sync all). What am I missing?

Thank you! Am happy you are enjoying the plugin! 😄
You are correct that replace and sync are exactly the same if you don't edit the results list, except for one case. When you do multi-line replace --multiline and --multiline-dot-all flags, sync won't work so you have to use replace.
Maybe we could update the README.md to mention that at some point, haha

Yeah that's would be good 👍
Thanks for clarifying!

hi @GitMurf

yes
It is mentioned here: https://github.com/MagicDuck/grug-far.nvim?tab=readme-ov-file#syncing-results-lines-back-to-originating-files , but if you feel like it can be improved, I am more than happy to accept a PR :). Documentation is definitely an area that could be improved. I think it's outgrown the README.md somewhat and something similar to kuala's docs would be good (https://kulala.mwco.app/docs/usage), but am daunted by the amount of work it would be to do that, haha
no, I think that would be difficult to implement and would not really provide much utility since you can just use Sync if you want that kind of behaviour

@MagicDuck thanks for the quick response! I will think about how the readme could be clearer.


Fix typo in title

Quick removal of 'r' in 'manager' from header title property and link title property so it reads "Discover and manage Shadow IT" instead of "Discover and manager Shadow IT".
From
<meta property="og:title" content="Discover and manager Shadow IT" />
<title>Discover and manager Shadow IT | Microsoft Docs</title>
To
<meta property="og:title" content="Discover and manage Shadow IT" />
<title>Discover and manage Shadow IT | Microsoft Docs</title>

@tehmichael : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks for this fix.


Backport: Content-Type application/x-gzip when change password

Backport for https://github.com/rancher/rancher/issues/19553

can be tested in rc8

Version: v2.2.3-rc8
POST to change password is now like prior method, is of Content-Length 0 bytes and is application/json instead of gzip. This works correctly now.


ng-repeat-start

Is there a way to get this to work with elements that are part of a ng-repeat-start / ng-repeat-end block? If I'm understanding the code correct, it's looking for "ng-repeat" specifically, and it bombs out if it doesn't find that specific attribute with this error (line 99 of unminified v1.0.0-rc5 js):
TypeError: Cannot read property '1' of null

I don't know enough to submit a PR but just want to say +1 as it would be very useful

Works since angular-vs-repeat v1.0.1-beta.2


Dart SDK roll PR presubmits queueing for too long

https://github.com/flutter/engine/pull/29225
@godofredoc I see this happening every few days. Is there some way to make the jobs fail or retry them when they queue for too long?

Not sure if this one is in the abnormal range yet, but the queue times on this role are up to 90 minutes: https://github.com/flutter/flutter/pull/92146

The current version does not include my fix. Deploying a new version.

The new version of the backend has been released. The expectation is that most of the builds will get updated in a few mins.


Don't assume rspec-mocks when stubbing Selinux

Try to stub Selinux with rspec-mocks if available, otherwise mocha. If neither are available, just don't do anything.

Coverage decreased (-0.08%) to 91.986% when pulling c76cf02130a006da62a0e6c7e4a79a047918e7f4 on selinux_stub_regression into 9f5c3a8e219a1166e75e2c18f4bf5d178ee93996 on master.


The contents of 'Release Notes' are not localized

Storage Explorer Version: 1.10.1
Build: 20190926.4
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
Architecture: ia32/x64
Language: Chinese (zh-TW) / Chinese (zh-CN)
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer using the command 'StorageExplorer.exe --lang=zh-CN'.
Go to localized 'Help' menu -> Select the localized 'View Release Notes'.
Check whether the contents of 'Release Notes' are localized or not.

Expect Experience:
The contents of 'Release Notes' are localized.
Actual Experience:
The contents of 'Release Notes' are not localized.

We're choosing to not translate the release notes.


Generated samples were never landed for Secret Manager

It doesn't look like we ever managed to land generated samples for Secret Manager.
We should check and make sure this was an anomaly.

Looks like they were added, haven't seen it in any other APIs but I will make sure to keep an eye out!


[KYUUBI #5937][Bug] PVM cause cache table not work

:mag: Description
Issue References 🔗

This pull request fixes #5937
Describe Your Solution 🔧
If we cache a table with persist view in the query, since cache table use analyzed plan, so in kyuubi authz we will use PVM to wrap the view, but cache table use canonicalized plan, so we need to implement the doCanonicalize() method to ignore the impact of PVM, or it will cache cached table can't be matched.
Types of changes :bookmark:

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[ ] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (3915fe8) 61.20% compared to head (c504103) 61.18%.
Report is 1 commits behind head on master.

Files
Patch %
Lines

...authz/rule/permanentview/PermanentViewMarker.scala
77.77%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5982      +/-   ##
============================================
- Coverage     61.20%   61.18%   -0.03%
  Complexity       23       23
============================================
  Files           622      622
  Lines         36897    36905       +8
  Branches       5016     5018       +2
============================================
- Hits          22583    22580       -3
- Misses        11877    11886       +9
- Partials       2437     2439       +2

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


Theme submission: toha

Theme submission
Please make sure that you have read the theme submission guidelines before submitting a theme. The guidelines provide all relevant information and requirements that have to be fulfilled before the submission. We strongly suggest that you test your theme with the Hugo Themes Build Script before submitting the theme for review. If a submission does not meet the criteria mentioned in the README it will be closed. You may re-submit once you fix the problems with your submission. However, please note that we have limited resources and can not provide help for general web development issues. For Hugo support questions please refer to the dedicated support forum.
Please tick the relevant boxes for your theme in the checklist below:
Link to my theme repository: https://github.com/hossainemruz/toha
I made sure that...

[x] the repository contains a good README.md describing my theme
[x] an open source license has been added to LICENSE.md
[x] all metadata have been added to theme.toml
[x] screenshots have been added in the images/ folder with the required dimensions
[x] in case I'm using a customized demo via the exampleSite folder that

[x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[x] I tested that my theme's demo works with the content directory of gohugoio/HugoBasicExample

[x] I tested my theme against the gohugoio/HugoBasicExample

[x] I've checked the developer tools' console in my browser for error messages

[x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

N.B. By submitting a theme to the Hugo Themes Showcase you understand that you need to maintain your theme. If a theme demo breaks and remains broken then at some point it will be removed from the list without prior warning. If you no longer wish to maintain a theme please let us know.
New themes will usually be promoted on Hugo's official Twitter account. If you would like to be mentioned in the tweet please add your Twitter username to this submission.
Link to my Twitter account (optional): https://twitter.com/Emruz_Hossain
Feel free to ask questions. We're glad to help.

Hello @hossainemruz,
thank you for sharing this theme with the Hugo community. While reviewing your theme I noticed a few smaller issues:

please make sure that the thumbnail and screenshot in the images folder have the right dimensions. You can find them in the README.
Consider to use .site.Params.mainSections when listing pages on the homepage. Regular pages still contain the archive and about page that should listed among the actual posts in your blog. .site.Params.mainSections is a list populated with the content types that have the most content files. This simple heuristic excludes our unwanted pages. Users can overwrite this array at any time.

@digitalcraftsman Thank you for reviewing the theme. I have fix the screenshot dimension and used .site.Params.mainSections according to your review. Please, take a look again.

Your theme should appear soon on Hugo's theme site. Next, I'll promote your theme on Hugo's official Twitter account.

Small update: right now your theme isn't showing up on the homepage of https://themes.gohugo.io, even though a demo of your theme has been deployed and the   build logs don't show any anomalies (regarding your theme). I'm investigating this right now.


fix: indentation in code sample of split-chunks-plugin

It would be better if the markdown linter can detect such error, @EugeneHlushko you know why my CLA not signed, I had signed already

Agree with @EugeneHlushko, I guess linter scripts have to be revised since it's not the first time formatting is broken in the examples.
I've created an issue for this one #2151

Good point, yeah we should try to actually update the linter and run it on all the content.

@jeremenichelli does it mean we can start on #2151? Please check my comment there with a suggested approach.

Thanks!


solve issues Incorrect cursor positioning on Samsung devices #176

This put the cursor at the start of input in IONIC applications

Anyone knows when this issue will  be released?

I believe this solves it in a more elegant way https://github.com/angular-ui/ui-mask/pull/200. I included a description of what was causing this issue when I debugged the problem. Please let me know if my solution solves this problem which would end up being a MUCH easier pull request for the maintainers to accept (since it is only a single line change).

As soon as possible I check the report the result .


devtool does not appear

Vue devtools version
6.6.0
Link to minimal reproduction
https://github.com/PabloBagliere/vue2-error-devtool-quasar
Steps to reproduce & screenshots
to execute the problem is:

install dependeny (pnpm i)
run (pnpm dev)

What is expected?
It is expected to show the vue devtool option.
Example:

What is actually happening?
Does not display the vue devtool

System Info
System:
    OS: Linux 6.5 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz
    Memory: 19.58 GB / 31.21 GB
    Container: Yes
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.10.0 - ~/.nvm/versions/node/v18.10.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.10.0/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.10.0/bin/npm
    pnpm: 8.7.3 - ~/.local/share/pnpm/pnpm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 121.0.6167.184

Any additional comments?
I use google chrome
I use quasar version 1 since the project at work is old. Vue already comes in quasar and uses vue 2.7.15.
The packages I have installed are in the image

I tried to use legacy but it does not work well because the project uses the setup method in many components and legacy does not show the setup.

This is happening for myself and my coworker all of a sudden. It was working before my last meeting and now its not working. I think the latest update broke something

me also - since 14 Feb v6.6.0.
Broken?

I can't reproduce with the provided repo on Chrome/Linux.

This isn't a solution but the Standalone version does work:
https://devtools.vuejs.org/guide/installation.html#standalone
I'm running Chrome 121.0.6167.184 on Mac OS with Vue.js devtools 6.6.0 installed from the Chrome Web Store and I'm not seeing the Vue Dev Tools tab either.

Also here. Looks like something was broken after the last update (14/2)

I've disabled the latest version and reinstalled the the legacy version which seems to be working for now - Legacy v5

I've disabled the latest version and reinstalled the the legacy version which seems to be working for now - Legacy v5

Thanks, worked for me.
Still it is truly necessary to fix the latest version.

Since last version I see the Vue tab but every time the page gets refreshed the plugin stops working and I have to close and reopen the tab. This didn't happen with legacy version.

@Akryum I don't know how else to help you to reproduce the error. When I click on the vue logo it does not open the dialog box in the new version.
In the video you can see that the dialog box does not open and the devtool does not appear and I use the example repository that I gave you.
Grabación de pantalla desde 15-02-24 09:04:38.webm

Can you try:

restarting chrome
restarting the computer
another browser such as Firefox or Edge

and report back?

I'm having the same issue on mac and chrome

I found out that using the incognito mode of chrome if the devtool appears, I tried other browsers and it works fine. I tried rebooting, reinstalling and it still doesn't work in normal mode. What could be the problem?
attached pictures
Incognito mode

Standard mode

It detects that vue exists but when selecting the devtool icon it does not open the tool, nor does it appear in the header.
Also try disabling all browser extensions.

Check that the extension has 'Site access' setting set to 'On all sites':

Could you try clearing the extension storage?
Make sure to have 'Developer mode' enabled in the Extensions page:

Open the extension menu and click on 'Inspect Popup':

In the Chrome devtools that opens, go to the 'Application' tab and right-click on the item below 'Local storage' and click on 'Clear':

Could you try clearing the extension storage?
Make sure to have 'Developer mode' enabled in the Extensions page:

Open the extension menu and click on 'Inspect Popup':

In the Chrome devtools that opens, go to the 'Application' tab and right-click on the item below 'Local storage' and click on 'Clear':

This didn't work for me. I also installed the 6.6.1 and it still didn't resolve it. In fact, now I can't inspect the popup anymore

It didn't work, directly the localstorage is empty, maybe the error is there because the localstorage is never filled with any value.
image of how I have the localstorage

Does it work in edge?

Yes in edge and breave (firefox did not update the version) that seems to me the strangest thing so I started the issues.
Example photo
edge:

Brave:

Same here, doesn't work on brave.
Version 1.62.165 Chromium: 121.0.6167.184

Same here, doesn't work on brave. Version 1.62.165 Chromium: 121.0.6167.184

This didn't work for me. I also installed the 6.6.1 and it still didn't resolve it. In fact, now I can't inspect the popup anymore

Same, can't inspect the popup
EDIT: downgrading to 6.5.1 works 👍 nhdogjmejiglipccpnnnanhbledajbpd-6.5.1.zip (rename to crx)

I tried everything because the 'pinia' option didn't appear, but this is the only thing that has worked for me

@skjnldsv Thank you for this, v6.6.0 broke most of the stuff and slow compared to v6.5.1, only solution was to rollback to a previous version for me

The extension randomly stopped working for me using Brave. Was using it for years with no issues. I also tried re-installing the legacy version and that also wouldn't work. I cleared every setting I could in Brave and neither would work. I did notice it worked in incognito, however.
I restarted my computer. No effect.
I uninstalled and re-installed Brave. No effect.
I uninstalled and purged everything Brave on my computer. On Mac this was /Users/{user}/Library/Application Support/BraveSoftware, then reinstalled Brave and installed the extension. This worked. However, I've lost all my browser preferences, settings etc., which I was prepared for. Quite a damper on my workflow. I'd suggest at least exporting your bookmarks before you do a fresh re-install.
Not sure if a Brave or extension issue.

Maybe it's somehow caused by the migration to Manifest V3...

Hey guys, it seems that FORCE REFRESH can be helpful. My setps are:

closing the chrome developer tools,
FORCE REFRESH (Ctrl + F5 or Ctrl  + Shift + F5 depends on your setting) the page,
open chrome devtools again. Finally, I got the Vue DevTools again.

Hope this trick can inspire somebody to resole this. @Akryum are there something wrong with extension initilization lifecycle?
Version 1.62.165 Chromium: 121.0.6167.184 on Windows 11.  Vue 2.7 load from cdn.

Nothing is helping from the extension to work. it just died. 6.6.1 doesn't work. Someone in Vue is awake?
Only the legacy version is working

vue-dev tools not working any more

I have the same problem, it does not work in normal chrome profiles.
It actually works and appears in Incognito tabs.
Maybe it's helpful for debugging the problem.

Maybe try exporting your bookmarks and reseting the Chrome profile

@Akryum That's not really acceptable imho. I have many other extensions using manifest v3 :)
Please note that the extension DOES show up in the toolbar, and the logo is green.
But clicking on it does not show the usual Vue is detected, it does nothing.
I think this is really a problem with the extension itself

It's not a matter of it being acceptable, it's all about trying to find the cause of the issue. This is all made extra difficult because I can't reproduce it myself and neither can a lot of people.

Maybe you can try to create a new profile.

All right I was faffing around a bit - same train of thought.
With the chrome devtools for the devtools open, and reloading it with 'cmd r' the vue devtools show up and the console logs:

Maybe you can try to create a new profile.
Could anyone also try to right-click in the blank extension drop-down and paste the console content?

Tried it, and - at least for me - it seemed to work for now.
Also the errors above does not appear with the new profile.
Will investigate further :)

@vogtm Those warnings can be safely ignored

I tried my laptop and devtools is working on it, but not on my desktop. Both are running the same version of Chrome, both on up to date Windows 11, both signed into the same Google account. Same code, same version of node.

I work in a team with three other developers. All of us are using the same computers, the same version of OS, the same browsers (same version, Chrome Version 121.0.6167.184 (Official Build) (arm64)), and the same projects from the same repo. They aren't having any issues with the extension whereas I am.
I installed the DevTools extension on Firefox and was able to get it to load, however, it wouldn't register Pinia. This feels like a cache issue related to the browser at the OS level or something beyond my ability to diagnose.

It's not a matter of it being acceptable, it's all about trying to find the cause of the issue.

Sorry, should I been more clear :see_no_evil:
The bug is fine, it happens! What is not acceptable is "creating a new profile" as a workaround :)

After trying more stuff yesterday evening I have found nothing obvious.
But to summarize my observations:
It works in newly created chrome profiles.
It works in incognito tabs
It works in "broken" profiles when:

open your page with vue code (e.g. localhost:8080)
open chrome devtools (⌘ ⌥ i )
with the chrome devtools in focus open the chrome devtools for the chrome devtools (⌘ ⌥ i )  -> I call them internal devtools in the next step
with the internal devtool in focus refresh (⌘ r) -> a new normal tab opens with devtools://devtools/bundled/device_mode_emulation_frame.html?...
the (normal) chrome devtools also reload and the vue devtools show up and are useable
(Maybe someone with the bug can check if they can reproduce the steps above with the same results)

My assumption would be similar to @woodinteractive that there is a weird chrome caching / extension thing going on.
Are there other extensions that recently shown the same problems? Maybe there are people from the chrome devtools team we can reach out to that might have a rough idea what could be the problem? By now, it seems more like a chrome bug to me than a vue devtool bug.

Here are the steps that worked for me:
Update Chrome to the latest version.
Completely remove the previous Vue DevTools installation.
Install Vue DevTools version 6.6.1.
Right-click on the Vue DevTools icon at the top and select 'Inspect popup,' then proceed to clear all storage applications

@mohamad68  Thanks, that worked for me too.
I had it running in incognito mode, but even after unregistering all service workers, it still didn't work.
I also had to remove the "update on reload" check from the service workers, then it started working.

I also had to remove the "update on reload" check from the service workers, then it started working.

That seems to be it. Disabling it makes the vue dev tools appear. Rechecking makes them disappear again.

i followed @mohamad68 which did not work but after following @urbgimtam it started working, thanks everyone

I also got it working after following the steps by @mohamad68  and @urbgimtam. The Chrome update put me on version 122.0.6261.58.

Worked too! Thanks @mohamad68 !

A note for those using Vue 3 and Vite, you can use this plugin or app instead:
https://devtools-next.vuejs.org/

I also had to remove the "update on reload" check from the service workers, then it started working.

That seems to be it. Disabling it makes the vue dev tools appear. Rechecking makes them disappear again.

This 100% fixed it for me.

The solution of @urbgimtam works for me on MacOS Chrome 🙌🏻

Worked too! Thanks @mohamad68 !
When Vue DevTools cannot be opened, it may cause some other extensions to fail to popup. Restarting the browser is required for them to popup again.

I cleared all the storage but the "Update on reload" checkbox was not checked for me so that hasn't solved it in my case.
I can right-click on Vue DevTools and choose "Reload Frame" which saves me having to close and re-open the Developer Tools window completely. Still not ideal but it is faster.

Hello, is there any update? Does the newest version work?

For me the "Update on reload" fix is only temporary, and I have to toggle it on and back off to get devtools to reload again after a while.

This issue is affecting many users and can be easily reproduced. The label should be updated.
Unchecking the Service Workers' "Update on reload" is the only temporary fix that worked for me.

I had  the same problem on Edge browser, react devtool will add options here, but vue devtool can't find any entry.
react devtools

vue devtools

Unchecking the Service Workers' "Update on reload" worked for me too.

I had the same problem on Edge browser, react devtool will add options here, but vue devtool can't find any entry.
react devtools  vue devtools

Mine can be displayed, but once I use the middle of the mouse to close the vue devtools TAB, I won't be able to find any entry to re-add it, only to reopen the console

Unchecking the Service Workers' "Update on reload" worked for me too.

Worked for me too

Unfortunately, I can't see it anymore, even after unchecking the Service Workers' "Update on Reload", when using Nuxt > 3.10.x. and VueDevtools 6.6.1.
It works with Vue directly (maybe some of the latest updates of both Nuxt and Vue Devtools created the issue?).
In any case, even when using the Vue Devtools standalone, it errors out saying:
Uncaught Error:  Dynamic require of "crypto" is not supported
Anyone found out more?

Unchecking the Service Workers' "Update on reload" worked for me too.
But tools behaves strange and sometimes couldn't shows updated information

Ok, another weird behaviour that could help tracking this.
On an existing project with Nuxt 3.10.3 and Vue 3.4.20 (don't remember the Nitro version), Vue devtools was detected and its tab appeared on Chrome Devtools.
Updating the project to Nuxt v3.11/Vue 3.4.21 without closing the Chrome DevTools allowed to use it without problems.
As soon as I closed and reopened the Chrome Devtools, Vue Devtools doesn't show anymore.
Funny thing is created new Nuxt project with Nuxt 3.10.3, Vue 3.4.20 and even downgraded Nitro to 2.9.0, removed node modules/ and package-lock.json, and still I can't get Vue Devtools to show up again.
Could it be one of the dependencies?

Downgrading nuxt devtools to 1.8.0 seems to allow VueDevtools to work again. https://github.com/nuxt/devtools/issues/634

Also vue-devtools can be downgraded to 5.6, but for me it isn't comfortable

Downgrading nuxt devtools to 1.8.0 seems to allow VueDevtools to work again. nuxt/devtools#634

Thanks. Disabling Nuxt Devtools made Vue Devtools panel appear again.

I have same problem on macOS using Chrome.

Fixed in @nuxt/devtools 1.1.5.

The same issue:
Since the latest 2 Chrome updates.
Chrome:
Version 123.0.6312.87 (Official Build) (arm64)
DevTools:
Version
6.6.1
macOS Sonoma
Version 14.4.1

Thanks. Disabling Nuxt Devtools made Vue Devtools panel appear again.

This worked for me as well, thank you!


Ambigious information provided

In the section https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments the following is stated:
The FQDNs sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com, and sip3.pstnhub.microsoft.com are resolved to IP addresses from the following subnets:

<IP_ADDRESS>/14
<IP_ADDRESS>/15

In the section https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments-1 the following is stated:
In the Microsoft 365, Office 365, and Office 365 GCC environments, the IP address ranges are:

<IP_ADDRESS>/14 (IP addresses from <IP_ADDRESS> to <IP_ADDRESS>)
<IP_ADDRESS>/14 (IP addresses from <IP_ADDRESS> to <IP_ADDRESS>)

According to Office 365 URLs and IP Addresses (https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide#skype-for-business-online-and-microsoft-teams), <IP_ADDRESS>/15 is correct and <IP_ADDRESS>/14 is incorrect.

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

ID: 3d964547-6b38-cc5f-6b2b-7a50a1c7dae9
Version Independent ID: fa5850f9-1b92-9727-c344-bcffc227cbd6
Content: Plan Direct Routing - Microsoft Teams
Content Source: Teams/direct-routing-plan.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

Hello @KennethMLdk
I checked internally and I was let known that the PSTN ranges used won’t exactly match up with the other Office client ranges. This is why we need the full <IP_ADDRESS>/14 in the documentation. The Teams client or any customer will only connect directly to endpoints in the <IP_ADDRESS>/15 range, but the customer-hosted backend components (SBCs) will need to be able to talk to the whole <IP_ADDRESS>/14 range – so that is the correct one and should be left in the documentation as is.
Thank you,


Inventory UC01.03.01 - AddInventoryService

[Link to use case] (https://github.com/CMPUT301F15T02/Xperts/wiki/Use-Case:-Inventory#inventory)

As an owner, I want to remove, edit, or add an item to my inventory that I want to share. It will have a name, quantity, quality, category, if I want to share it with others, and comments.

Presently adding a service works when all fields are filled. The service is uploaded to elastic search. Presently there is no way to view that service on the app since the profile/inventory isn't implemented yet.


Fixed hover effect on empty date blocks - Issue #1

Removed styles from empty blocks for a cleaner and more consistent look.
Eliminated the outline color from the year input box to enhance visual coherence.
Aligned the active day color with the hover color and default color schemes for improved consistency.
Adjusted hover colors for better user experience.
Utilized the "Live Sass Compiler" to monitor Sass files, ensuring real-time style updates.
Incorporated "Prettier" for consistent and well-formatted code.
Thoroughly followed the contribution guide to ensure compliance with project standards.
The live deployed link is: https://devbytemehedi.github.io/calendar-generator/

By making these changes, your website should appear cleaner, more consistent, and easier on the eyes. The alignment of active day color with hover color and the removal of unnecessary styles from empty blocks will contribute to a more visually appealing user experience.

@devbytemehedi Hey, you did a great job by looking into it. But you've also deployed a version of your own on your github,  take a look and remove the .github/workflow file from your repository. Also this issue #1 Defines only hover effect on empty blocks. Other issues will be open soon for other fixes.  You can replace the hover styling as it was before. I will merge as soon as you remove the hover styling.
And please do not use ChatGPT!.

@jahir-raihan Okay i will remove the  .github/workflow and only fix #1 . i will create a separate  pull request for visual improvements. I used chatgpt for bulletpoints, description was one big paragraph.

@jahir-raihan hey i remove hover styling and .github folder

@devbytemehedi I think you've used prettier on Javascript as well by accident. Can you fix that please.

hey @jahir-raihan  how about i add .prettierignore file in the root of the project with index.js inside and remove prettier formating will it okay ?

@devbytemehedi Sure!

is everything okay now ?

@devbytemehedi let me check.

@devbytemehedi  Great work. I'm merging it. Keep up the good work.

@devbytemehedi For your information,  emojis in commit messages are a not a good thing.

@jahir-raihan  thanks bro, i think emojis makes commit message more visually appealing.

@jahir-raihan  bro i wanted you opinion on this vscode-theme i made

@devbytemehedi Oh hey, I was wrong , you should keep the .github/workflow file, as it is responsible for deployment. Any way good work. Next time if you contribute, make sure to fetch commits from the master branch.  I will check your theme right away.

@devbytemehedi Would be great if you reduce the contrast ratio on colors. But thats a great work you've done.

@jahir-raihan thanks for your review bro. If you like this theme please recommend others.


Fix a P1 accessibility bug: screen reader announces background contents even though a modal is displayed.

Please note that this change has one consequence for sighted users: the contents of the question area are wiped before the modal animates down. (This wiping is needed because otherwise the screen reader will read background components that are not visible to sighted users.) However, there is some code complexity involved in introducing an additional timeout before wiping the background, so I wanted to check if the current implementation looks OK from a UI perspective.

Thanks for working on this, seanlip. From a UI/UX standpoint, I think it would be better to not make content visibly disappear; the reason we have a modal that float in is to assure the user that the feedback didn't just disappear. This looks like feedback does disappear in addition to a modal that floats in. Also, when dismissed, the modal suddenly disappears rather than float back up, which makes it look glitchy/buggy/janky.

Superseded by #532. It took a while to figure out how to handle this properly because the CSS animations and timeouts lead to race conditions, so I eventually went with a different approach.


Add volume / mute toggle button instead of text label

This commit depends on new functionality in pychromecast (https://github.com/balloob/pychromecast/commit/83aa115ab4e538c5bb96d96650c282e202ede331)
Also I made the power button the only accented button. We can still think about it to make that button a floating action button (see https://elements.polymer-project.org/elements/paper-fab?view=demo:demo/index.html)

I have just pushed PyChromecast 0.6.3 to PyPi with the muted command. Can you update requirements.txt ?

There is still a minor bug in the mute button behavior - the first two taps the volume is muted / unmuted, but the icon is not updated correspondingly. After that the icon is updated well.

And another step closer to awesomeness :dancers:


Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962709,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"6bf90c79-32f4-47ad-959c-8fff723fe744","name":"Meeting","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"a32316b8-dc8c-48c5-b12b-71c1b2a080bf","name":"Referenceable"},"description":"Two or more people come together to discuss a topic, agree and action or exchange information.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"title","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Title of the meeting.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"startTime","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"1bef35ca-d4f9-48db-87c2-afce4649362d","name":"date","primitiveDefCategory":"OM_PRIMITIVE_TYPE_DATE"},"attributeDescription":"Start time of the meeting.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"endTime","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"1bef35ca-d4f9-48db-87c2-afce4649362d","name":"date","primitiveDefCategory":"OM_PRIMITIVE_TYPE_DATE"},"attributeDescription":"End time of the meeting.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"objective","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Reason for the meeting and intended outcome.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"minutes","attributeType":{"class":"CollectionDef","version":1,"versionName":"1.0","category":"COLLECTION","guid":"0428b5d3-f824-459c-b7f5-f8151de59707","name":"array<string>","description":"An array of Strings.","collectionDefCategory":"OM_COLLECTION_ARRAY","argumentCount":1,"argumentTypes":["OM_PRIMITIVE_TYPE_STRING"]},"attributeDescription":"Description of what happened at the meeting.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962709,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"93dbc58d-c826-4bc2-b36f-195148d46f86","name":"ToDo","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"a32316b8-dc8c-48c5-b12b-71c1b2a080bf","name":"Referenceable"},"description":"An action assigned to an individual.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"name","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Name or title of the todo/action.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"description","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Description of the required action.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"creationTime","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"1bef35ca-d4f9-48db-87c2-afce4649362d","name":"date","primitiveDefCategory":"OM_PRIMITIVE_TYPE_DATE"},"attributeDescription":"When the requested action was identified.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"priority","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"7fc49104-fd3a-46c8-b6bf-f16b6074cd35","name":"int","primitiveDefCategory":"OM_PRIMITIVE_TYPE_INT"},"attributeDescription":"How urgent is this action?","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"dueTime","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"1bef35ca-d4f9-48db-87c2-afce4649362d","name":"date","primitiveDefCategory":"OM_PRIMITIVE_TYPE_DATE"},"attributeDescription":"When the requested action needs to be completed.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"status","attributeType":{"class":"EnumDef","version":1,"versionName":"1.0","category":"ENUM_DEF","guid":"7197ea39-334d-403f-a70b-d40231092df7","name":"ToDoStatus","description":"Progress on completing an action (to do).","elementDefs":[{"ordinal":0,"value":"Open","description":"No action has been taken."},{"ordinal":1,"value":"InProgress","description":"Work is underway to complete the action."},{"ordinal":2,"value":"Waiting","description":"Work is blocked waiting for resource of another action to complete."},{"ordinal":3,"value":"Complete","description":"The action has been completed successfully."},{"ordinal":99,"value":"Abandoned","description":"Work has stopped on the action and will not recommence."}]},"attributeDescription":"How complete is the action?","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"completionTime","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"1bef35ca-d4f9-48db-87c2-afce4649362d","name":"date","primitiveDefCategory":"OM_PRIMITIVE_TYPE_DATE"},"attributeDescription":"When the requested action was completed.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"fbd42379-f6c3-4f08-b6f7-378565cda993","name":"Community","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"a32316b8-dc8c-48c5-b12b-71c1b2a080bf","name":"Referenceable"},"description":"A group of people with a common interest or skill.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"name","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Name of the community.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"description","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Description of the community.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"mission","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Purpose of the community.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"fbd42379-f6c3-4f09-b6f7-378565cda993","name":"CommunityMember","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"ac406bf8-e53e-49f1-9088-2af28bcbd285","name":"PersonRole"},"description":"A person who has joined a community.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE"}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"7299d721-d17f-4562-8286-bcd451814478","name":"Rating","version":1,"versionName":"1.0","category":"ENTITY_DEF","description":"Quantitative feedback related to an item.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"anchorGUID","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Optional identifier of the referenceable that this rating is connected to (either directly or indirectly).","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"stars","attributeType":{"class":"EnumDef","version":1,"versionName":"1.0","category":"ENUM_DEF","guid":"77fea3ef-6ec1-4223-8408-38567e9d3c93","name":"StarRating","description":"Level of support or appreciation for an item.","elementDefs":[{"ordinal":0,"value":"NotRecommended","description":"This content is not recommended."},{"ordinal":1,"value":"OneStar","description":"One star rating."},{"ordinal":2,"value":"TwoStar","description":"Two star rating."},{"ordinal":3,"value":"ThreeStar","description":"Three star rating."},{"ordinal":4,"value":"FourStar","description":"Four star rating."},{"ordinal":5,"value":"FiveStar","description":"Five star rating."}]},"attributeDescription":"Rating level provided.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"review","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Additional comments associated with the rating.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"1a226073-9c84-40e4-a422-fbddb9b84278","name":"Comment","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"a32316b8-dc8c-48c5-b12b-71c1b2a080bf","name":"Referenceable"},"description":"Descriptive feedback or discussion related to an item.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"anchorGUID","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Optional identifier of the referenceable that this comment is connected to (either directly or indirectly).","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"text","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Feedback comments or additional information.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"type","attributeType":{"class":"EnumDef","version":1,"versionName":"1.0","category":"ENUM_DEF","guid":"06d5032e-192a-4f77-ade1-a4b97926e867","name":"CommentType","description":"Descriptor for a comment that indicated its intent.","elementDefs":[{"ordinal":0,"value":"GeneralComment","description":"General comment."},{"ordinal":1,"value":"Question","description":"A question."},{"ordinal":2,"value":"Answer","description":"An answer to a previously asked question."},{"ordinal":3,"value":"Suggestion","description":"A suggestion for improvement."},{"ordinal":4,"value":"Experience","description":"An account of an experience."},{"ordinal":99,"value":"Other","description":"None of the above."}]},"attributeDescription":"Type of comment.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"deaa5ca0-47a0-483d-b943-d91c76744e01","name":"Like","version":1,"versionName":"1.0","category":"ENTITY_DEF","description":"Boolean type of rating expressing a favorable impression.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"anchorGUID","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Optional identifier of the referenceable that this comment is connected to (either directly or indirectly).","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"ba846a7b-2955-40bf-952b-2793ceca090a","name":"InformalTag","version":1,"versionName":"1.0","category":"ENTITY_DEF","description":"An descriptive tag for an item.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"isPublic","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"3863f010-611c-41fe-aaae-5d4d427f863b","name":"boolean","primitiveDefCategory":"OM_PRIMITIVE_TYPE_BOOLEAN"},"attributeDescription":"Is the tag visible to more than the originator?","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"tagName","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Descriptive name of the tag.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"tagDescription","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"More detail on the meaning of the tag.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"3a84c94c-ac6f-4be1-a72a-07dcec7b1fe3","name":"CrowdSourcingContributor","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"ac406bf8-e53e-49f1-9088-2af28bcbd285","name":"PersonRole"},"description":"Person contributing new content.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE"}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"2a84d94c-ac6f-4be1-a72a-07dcec7b1fe3","name":"NoteEntry","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"a32316b8-dc8c-48c5-b12b-71c1b2a080bf","name":"Referenceable"},"description":"An entry in a note log.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"title","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Title of the note entry.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"text","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Text of the note entry.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"isPublic","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"3863f010-611c-41fe-aaae-5d4d427f863b","name":"boolean","primitiveDefCategory":"OM_PRIMITIVE_TYPE_BOOLEAN"},"attributeDescription":"Is the note visible to more than the note log authors?","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"646727c7-9ad4-46fa-b660-265489ad96c6","name":"NoteLog","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"a32316b8-dc8c-48c5-b12b-71c1b2a080bf","name":"Referenceable"},"description":"An ordered list of related notes.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"name","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Name of the note log.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"description","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Description of the note log.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"isPublic","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"3863f010-611c-41fe-aaae-5d4d427f863b","name":"boolean","primitiveDefCategory":"OM_PRIMITIVE_TYPE_BOOLEAN"},"attributeDescription":"Is the note log visible to more than the note log authors?","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"3a84d94c-ac6f-4be1-a72a-07dbec7b1fe3","name":"NoteLogAuthor","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"ac406bf8-e53e-49f1-9088-2af28bcbd285","name":"PersonRole"},"description":"A person adding notes to a note log.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE"}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"114e9f8f-5ff3-4c32-bd37-a7eb42712253","name":"Connection","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"a32316b8-dc8c-48c5-b12b-71c1b2a080bf","name":"Referenceable"},"description":"A set of properties to identify and configure a connector instance.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"displayName","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Consumable name for the connection, suitable for reports and user interfaces.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"description","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Description of the connection.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"securedProperties","attributeType":{"class":"CollectionDef","version":1,"versionName":"1.0","category":"COLLECTION","guid":"8fa603dd-c2c5-43fc-8ff4-92141f2414ad","name":"map<string,object>","description":"A map from String to Object.","collectionDefCategory":"OM_COLLECTION_MAP","argumentCount":2,"argumentTypes":["OM_PRIMITIVE_TYPE_STRING","OM_PRIMITIVE_TYPE_UNKNOWN"]},"attributeDescription":"Private properties accessible only to the connector.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"configurationProperties","attributeType":{"class":"CollectionDef","version":1,"versionName":"1.0","category":"COLLECTION","guid":"8fa603dd-c2c5-43fc-8ff4-92141f2414ad","name":"map<string,object>","description":"A map from String to Object.","collectionDefCategory":"OM_COLLECTION_MAP","argumentCount":2,"argumentTypes":["OM_PRIMITIVE_TYPE_STRING","OM_PRIMITIVE_TYPE_UNKNOWN"]},"attributeDescription":"Specific configuration properties for the underlying technology.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"userId","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"User identity that the connector should use.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"clearPassword","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Password for the userId in clear text.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"encryptedPassword","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Encrypted password that the connector needs to decrypt before use.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"954421eb-33a6-462d-a8ca-b5709a1bd0d4","name":"ConnectorType","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"a32316b8-dc8c-48c5-b12b-71c1b2a080bf","name":"Referenceable"},"description":"A set of properties describing a type of connector.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE","propertiesDefinition":[{"attributeName":"displayName","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Consumable name for the connector type, suitable for reports and user interfaces.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"description","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Description of the connector type.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"connectorProviderClassName","attributeType":{"class":"PrimitiveDef","version":1,"versionName":"1.0","category":"PRIMITIVE","guid":"b34a64b9-554a-42b1-8f8a-7d5c2339f9c4","name":"string","primitiveDefCategory":"OM_PRIMITIVE_TYPE_STRING"},"attributeDescription":"Name of the Java class that implements this connector type's open connector framework (OCF) connector provider.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"recognizedAdditionalProperties","attributeType":{"class":"CollectionDef","version":1,"versionName":"1.0","category":"COLLECTION","guid":"0428b5d3-f824-459c-b7f5-f8151de59707","name":"array<string>","description":"An array of Strings.","collectionDefCategory":"OM_COLLECTION_ARRAY","argumentCount":1,"argumentTypes":["OM_PRIMITIVE_TYPE_STRING"]},"attributeDescription":"List of additional connection property names supported by the connector implementation.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"recognizedSecuredProperties","attributeType":{"class":"CollectionDef","version":1,"versionName":"1.0","category":"COLLECTION","guid":"0428b5d3-f824-459c-b7f5-f8151de59707","name":"array<string>","description":"An array of Strings.","collectionDefCategory":"OM_COLLECTION_ARRAY","argumentCount":1,"argumentTypes":["OM_PRIMITIVE_TYPE_STRING"]},"attributeDescription":"List of secured connection property names supported by the connector implementation.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false},{"attributeName":"recognizedConfigurationProperties","attributeType":{"class":"CollectionDef","version":1,"versionName":"1.0","category":"COLLECTION","guid":"0428b5d3-f824-459c-b7f5-f8151de59707","name":"array<string>","description":"An array of Strings.","collectionDefCategory":"OM_COLLECTION_ARRAY","argumentCount":1,"argumentTypes":["OM_PRIMITIVE_TYPE_STRING"]},"attributeDescription":"List of secured connection property names supported by the connector implementation.","valuesMinCount":0,"valuesMaxCount":1,"attributeCardinality":"AT_MOST_ONE","indexable":true,"unique":false}]}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab
Mon Jun 17 19:59:26 BST 2019 cocoMDS1 OMRS-AUDIT-0101 Unable process an incoming event {"class":"OMRSEventV1","protocolVersionId":"OMRS V1.0","timestamp":1560797962710,"originator":{"metadataCollectionId":"aa87d340-16e8-42ed-829b-21f83956de7f","serverName":"cocoMDS2","serverType":"Open Metadata and Governance Server"},"eventCategory":"TYPEDEF","typeDefEventSection":{"typeDefEventType":"NEW_TYPEDEF_EVENT","typeDef":{"class":"EntityDef","guid":"82f9c664-e59d-484c-a8f3-17088c23a2f3","name":"VirtualConnection","version":1,"versionName":"1.0","category":"ENTITY_DEF","superType":{"guid":"114e9f8f-5ff3-4c32-bd37-a7eb42712253","name":"Connection"},"description":"A connector for a virtual resource that needs to retrieve data from multiple places.","origin":"bce3b0a0-662a-4f87-b8dc-844078a11a6e","createdBy":"ODPi Egeria (OMRS)","createTime":1516313040008,"validInstanceStatusList":["ACTIVE","DELETED"],"initialStatus":"ACTIVE"}}} due to exception java.lang.UnsupportedOperationException from listener org.odpi.openmetadata.accessservices.securityofficer.server.admin.listener.SecurityOfficerOMRSTopicListener@40954cab

Thank you Daniela for fixing this :)


fastlane "download_all" doesn't include mac profiles :(

New Issue Checklist

[ ] Updated fastlane to the latest version
No, but basing this off master commit source code
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
We have a scheduled job to download all the provisioning profiles from the Apple Developer Portal and we are just now noticing none of the Mac profiles have been downloaded. We are running as follows:
Command executed
fastlane sigh download_all --readonly --skip_install --output_path /tmp/profiles/
Complete output when running fastlane, including the stack trace and command used
The output of the command is not necessary as it is just a huge list of our profiles and this would mean nothing to you, but looking through the output I am searching for a profile that I generated for macOS and it is nowhere to be found. After looking at the source code: https://github.com/fastlane/fastlane/blob/master/sigh/lib/sigh/download_all.rb I can see why! I have been playing around with Spaceship and I know that in order to download mac specific stuff you need to pass mac: true as such:
Spaceship.provisioning_profile.all(mac: true) but this is for all of the mac profiles, this doesn't include the ios ones. So the source code would have to be updated to combine the two collections of profiles
Environment
🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.14.5

Ruby
2.2.3

Bundler?
false

Git
git version 2.20.1 (Apple Git-117)

Installation Source
~/.rbenv/versions/2.2.3/bin/fastlane

Host
Mac OS X 10.14.5 (18F132)

Ruby Lib Dir
~/.rbenv/versions/2.2.3/lib

OpenSSL Version
OpenSSL 1.0.2p  14 Aug 2018

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
10.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.126.0
🚫 Update available

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

terminal-table
1.8.0

CFPropertyList
3.0.0

multipart-post
2.0.0

word_wrap
1.0.0

public_suffix
2.0.5

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

faraday
0.15.4

unf
0.1.4

domain_name
0.5.20180417

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.5

gh_inspector
1.1.3

mini_magick
4.5.1

multi_xml
0.6.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

bundler
1.14.6

naturally
2.2.0

simctl
1.6.5

jwt
2.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

mime-types
3.2.2

multi_json
1.13.1

signet
0.11.0

memoist
0.16.0

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

tty-cursor
0.7.0

tty-spinner
0.9.1

tty-screen
0.7.0

json
2.2.0

excon
0.64.0

rubyzip
1.2.3

plist
3.5.0

atomos
0.1.3

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.10.0

faraday_middleware
0.13.1

unicode-display_width
1.6.0

addressable
2.6.0

os
1.0.1

psych
2.0.8

retriable
3.1.2

mime-types-data
3.2019.0331

uber
0.1.0

generated on: 2019-07-23

About to try and make a PR: https://github.com/nancy-gomez/fastlane/commit/cfd71daef589a9fe0ebbe8caa857cb11c8a4eb6b
But I got dependency issues 😭 Will deal with it tomorrow I guess

I have submitted a Pull Request with this adjustment: https://github.com/fastlane/fastlane/pull/15091 🙏 pls helppp

I have submitted an additional PR based off feedback from the new one. Opened up a new one as the overall feature was a smidge different (make download_all include mac profiles vs make download_all support the platform flag)

Closing this stale issue as https://github.com/fastlane/fastlane/pull/15175 got merged and released a long time ago 😊

Closing this stale issue as https://github.com/fastlane/fastlane/pull/15175 got merged and released a long time ago 😊


audio output selection

By default the audio output selection is earpiece.
Need a selection option like other platforms to output the audio through speaker as well

duplicate

@davidliu Thanks for implementing it very quickly.


Show the debugger survey banner for only a subset of users.

(fixes #2300)

[x] Title summarizes what is changing
[x] Includes a news entry file (remember to thank yourself!)
[x] Unit tests & code coverage are not adversely affected (within reason)
[x] Works on all actively maintained versions of Python (e.g. Python 2.7 & the latest Python 3 release)
[x] Works on Windows 10, macOS, and Linux (e.g. considered file system case-sensitivity)
[x] Dependencies are pinned (e.g. "1.2.3", not "^1.2.3")
[x] package-lock.json has been regenerated if dependencies have changed

I am against designing for the future when we don't even know what we need. Hence the constant mentioning of YAGNI, personally I think it's unnecessary and we can always add the one liners via refactoring. Else we have more coffee paths to be tested.
Also with all the names we have had in the past, I see no reason for some of the proposed changes. We only need sampling %, shock could be 100% if it applies to everyone.
So technically the randomizer function will also never change.
I don't see us ever creating different functions to generate random numbers for different banners!!

I'm closing this in favor of #2425.