Aggregating MMTEB datasets

Some MMTEB datasets include only some of their respective many languages.
For example Multilingual Miracl in MMTEB contains only German and Spanish although it has many more.   Others like Korean Mr.TyDI are included even though it is multilingual. Same with Korean Miracl which is included separately from the multilingual Miracl.
These should be consolidated into multilingual datasets with all their available languages (18 in Miracl and 11 in Mr. TyDI).
I can start working on this next week, unless someone beats me to it.

Assuming @KennethEnevoldsen agrees

Nandan Thakur may have started   https://github.com/embeddings-benchmark/mteb/issues/198#issuecomment-2050189570 on Miracl
Merging Mr.TyDI seems like a good idea. I think we would prefer not to run these massive retrieval tasks too many times...

Assuming @KennethEnevoldsen agrees

Completely agree, we should merge the relevant datasets. Feel free to merge Mr.TyDI

I think we would prefer not to run these massive retrieval tasks too many times...

If the dataset is massive we might consider reducing the size as well.

On a closer reading of the MiRACL paper, it seems like they expanded the Mr. TyDi work with more annotations.  Assuming that is true and they have the same query set (@thakur-nandan) I would suggest we remove any Mr. TyDi datasets and only include MiRACL.

Hi @orionw and others, I wasn't aware of this issue thread. including @crystina-z to the thread as well.
Yes, My suggestion is what @orionw suggested. MIRACL was built on top of Mr. TyDI. MIRACL covers more languages, and denser annotations and queries present in Mr. TyDI are already available within MIRACL. So, include MIRACL instead of Mr. TyDI in MMTEB.
@orionw instead of the MIRACL Arxiv, you can read the latest paper on TACL with more information:
https://direct.mit.edu/tacl/article/doi/10.1162/tacl_a_00595/117438/MIRACL-A-Multilingual-Retrieval-Dataset-Covering

heyy! glad to see both datasets are considered! Yes MIRACL is expanded on Mr. TyDi so it makes sense to only include MIRACL for the evaluation.

Assuming that is true and they have the same query set

Just to add on this: although MIRACL includes most (> 90% for most languages) of the dev queries in Mr. TyDi, they are not completely identical: some queries were skipped since we couldn't find positive passage for them in the MIRACL corpus. Here's the stats (number of queries in the dev set):
| MIRACL (dev) | MrTyDI (dev) | Percentage
-- | -- | -- | --
ar | 2,896 | 3,115 | 93.0%
bn | 411 | 440 | 93.4%
en | 799 | 878 | 91.0%
fi | 1,271 | 1,738 | 73.1%
id | 960 | 1,224 | 78.4%
ja | 860 | 928 | 92.7%
ko | 213 | 303 | 70.3%
ru | 1,252 | 1,375 | 91.1%
sw | 482 | 526 | 91.6%
te | 828 | 983 | 84.2%
th | 733 | 807 | 90.8%

I think we would prefer not to run these massive retrieval tasks too many times...

If the dataset is massive we might consider reducing the size as well.

I can run some filtering to find how many docs are considered by most embedding models to be irrelevant to any query.
I think maybe  we can remove these docs and create a slim version of collection (corpus).

Thanks @izhx!
I think I missed some of the earlier conversations about MMTEB, but in my experience removing passages that are non-relevant will greatly change the difficulty of the retrieval task (removing difficult non-relevant documents).  AFAIK, the tasks in MTEB still have the same corpus size, even in the millions for some.
If we need to remove something from retrieval datasets to make it run faster I would suggest the queries.  MiRACL has ~1k or less queries per lang, IDK if that's too large for our usage but it's on par with many in MTEB. Did we decide on some threshold for size earlier?

@orionw No, we do not have some threshold to the corpus size. It's just a random thought of mine.
I apologize if I haven't made myself clear. What I intend to do is eliminate the documents that are least relevant (very low embedding dot score, e.g. ranked 5M of all 8M docs) to any query (for most models). I suppose this might not touch the hard-negative docs, so it might not affect the difficulty (too much) of the task.
Currently, in retrieval evaluator, we first encode a small number of queries (seconds), then encode and search through a massive corpus in chunks (which is the most expensive part, up to hundreds of minutes). Reducing these easy negative docs could be an effective way to enhance efficiency without minimal impacts of other parts.
This is just my initial understanding. Welcome further discussion

I'm not sure how many of these seemingly dispensable (in my intuition) docs there are, probably not many.

Hi @izhx @orionw! me and @thakur-nandan had a quick discussion, and we'll vote for not touching the size of the corpus or queries, as that would cause the evaluation scores to no longer be comparable to the current MIRACL benchmark.
How do you think an alternative solution that we only include the languages with a large corpus (e.g., en, fr, es, ru, ja, zh) in the reranking but not the retrieval task? so we'll save time on retrieval, but still have the full language coverage on reranking.

I would also prefer not changing them, if possible, for the same reasons. Maybe we add them all for now and if inference is too slow once the benchmark is complete it’s easy to remove them from retrieval?

Yup that sounds good to us

Thanks, I agree!

I fully agree with the integration of Korean Miracl into MMTEB's Multilingual Miracl.

Miracl and Mr.TyDI's documentation had a lot of duplication because they use almost the same wikipedia snapshot. I haven't seen the full MTEB source code yet, so I don't know if it's something that already exists, but if we implemented a caching mechanism for document and query, I wonder if it wouldn't cost almost as much to run two datasets as it would to run one, rather than the sum of their parts.
If implemented, I think it would be ideal to use a key-value store like redis, where the key would be the hash value of the document and the value would be the vector of the embedding model. For simplicity of implementation, diskcache might also be worth considering.

Great idea @taeminlee! I wonder if there are other datasets with similar redundancies we might be able to take advantage of as well. Probably worth making a separate issue and we can track them down there!

I have created an issue over at #375

Brilliant idea! If the cache could be made, we'll save over 90% space for Mr. Tydi and MIRACL.


Test failures with -Duselongdouble

Statistical analsysis shows a high probability of test failures with perls compiled with -Duselongdouble: http://analysis.cpantesters.org/reports_by_field?distv=App-Sqitch-0.9993;field=conf%3Auselongdouble

Thanks. Merijn helped me sort this out a while ago, and I fixed it in dcbbe6da. Yes, I'm overdue for a release. :-)


Port Document search API for Elasticsearch 6.x

For Document search functionality, there are already an API exist in readthedocs-ext repository.
As we upgrade the search as part of GSOC project, that API need to be ported ported to work with the new search infrastructure. The search API should be rewritten by using the PageDocument class but the API schema should not be changed. That will be a complex work to do as the API schema need to be kept same.
Before starting work, there should be good amount of test in the current API schema because if API schema is changed, document search will be broken in the frontend and it will have major effect. See #4197 for ongoing tests.
@ericholscher @agjohnson Do you think the API schema should be kept same or we should design a new Document Search API which mataches with the new search upgrade code?

I don't think we need to heavily change the API, but we are able to if we want. We control the client code, so we can easily deploy new client code that works with the new API, if we need to.
@safwanrahman you should discuss any specific changes you think we should make, and we can talk about them specifically, instead of in the abstract.

Currently the API returns nested structure! There are a lot of information that is not needed actually. we only need some of the information like title, link, highlight and number of results. So I was thinking to design a API that provide only the needed values.
{
  "results": {
    "hits": {
      "hits": [
        {
          "_type": "page",
          "_index": "readthedocs-20150526133301",
          "_score": 0.014734331,
          "fields": {
            "project": [
              "kuma"
            ],
            "path": [
              "index"
            ],
            "version": [
              "latest"
            ],
            "link": "https://kuma.readthedocs.io/en/latest/index",
            "title": [
              "Kuma"
            ]
          },
          "highlight": {
            "content": [
              "Kuma\nKuma is the platform that powers MDN (developer.mozilla.org)\nDevelopment\nCode:\nhttps://github",
              ".com/mozilla/kuma\nIssues:\nP1 Bugs (to be fixed in 90 days)\nP2 Bugs (to be fixed in 180 days)\nAll",
              " developer.mozilla.org bugs\nPull Request Queues\nDev Docs:\nhttps://kuma.readthedocs.io/en/latest",
              "/installation.html\nCI Server:\nhttps://travis-ci.org/mozilla/kuma\nForum:\nhttps://discourse.mozilla.org/c/mdn",
              "\nIRC:\nirc://irc.mozilla.org/mdndev\nhttp://logs.glob.uno/?c=mozilla%23mdndev (logs)\nServers:\nWhat’s"
            ]
          },
          "_id": "4ad0a08beb6ae308b1737f4c943e5210"
        },
      ],
      "total": 8,
      "max_score": 0.014734331
    },
    "_shards": {
      "successful": 1,
      "failed": 0,
      "total": 1
    },
    "took": 39,
    "facets": {
      "project": {
        "_type": "terms",
        "total": 8,
        "terms": [
          {
            "count": 8,
            "term": "kuma"
          }
        ],
        "other": 0,
        "missing": 0
      },
      "taxonomy": {
        "_type": "terms",
        "total": 0,
        "terms": [

        ],
        "other": 0,
        "missing": 8
      },
      "version": {
        "_type": "terms",
        "total": 8,
        "terms": [
          {
            "count": 8,
            "term": "latest"
          }
        ],
        "other": 0,
        "missing": 0
      }
    },
    "timed_out": false
  }
}

@safwanrahman I agree, we are returning too much data (and very Elastic Search specific data) from the API. We should condense it down.
I believe the original intent was to be able to build a "full" search client with the API. So you could offer faceting and other data in the API, so that the user could build a nicer interface for it than just a search box with results. I think for now, we can simplify the API down to what we need for documentation pages. We can then extend it in the future if we need to.

The JS client that might need updating is here: https://github.com/rtfd/readthedocs.org/blob/master/readthedocs/core/static-src/core/js/doc-embed/search.js#L25

Fixed with #4340


TypeError: can't multiply sequence by non-int of type 'float'

raceback (most recent call last):
File "/code/opendm/remote.py", line 386, in monitor
task.download_assets(self.project_path, progress_callback=print_progress)
File "/usr/local/lib/python2.7/dist-packages/pyodm/api.py", line 651, in download_assets
zip_path = self.download_zip(destination, progress_callback=progress_callback, parallel_downloads=parallel_downloads, parallel_chunks_size=parallel_chunks_size)
File "/usr/local/lib/python2.7/dist-packages/pyodm/api.py", line 531, in download_zip
class nonloc:
File "/usr/local/lib/python2.7/dist-packages/pyodm/api.py", line 533, in nonloc
merge_chunks = [False] * num_chunks
TypeError: can't multiply sequence by non-int of type 'float'
File "/usr/lib/python2.7/threading.py", line 774, in __bootstrap
self.__bootstrap_inner()
File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File "/code/opendm/remote.py", line 410, in monitor
traceback.print_stack()
Seems to happen with downloads from S3.

Actually this is just due to Python 2 vs Python 3 differences.

Hello @pierotofy
How do you solve it?
Should I update my python 3 ?
I am in production so I prefer to ask before backing up and trying it which would cut the workers' access to the server in the meantime

Should already have been fixed, just make sure you are running the latest version of PyODM.

Hello @FlyingPigSolutions
Just in case you don't know, maintenance of Python 2.7 will stop by the end of the year.


Add support for Heiman HS3MS, HS3WL, HS3DS

Hi
I'm new to this and spent a lot of time adding these devices.  All devices are under //HEIMAN section. They all work with the alterations to this file and the converter(s).  The only issue I had was the HS3WL, HS3DS coming up as ModelID 'undefined' when adding?  HS3WL, HS3DS use the same converters as the HS1WL and HS1DS models.
Also the HS3MS needs a converter which I will add to the node_modules/zigbee-shepherd-converters/converters/fromZigbee.js
Regards
Quinn

Can you also add the converter which needs to be added?

NVM just saw #452


[C-Api] Revert fill dim (default 1) commit

Because of native TC failure, this patch reverts the fill dim (default 1) commit.

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #288. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @again4you, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/288-202304130925170.18064403533936-7538b7e21b71cee3c7daf90129832423cc764882/.


Investigate a way to remove special members from eTD after they are removed from LP

Right now, special members are imported the first time they show up in the import file and are not imported again after that.  Therefore, they are not subject to the cleaning job that removes expired committee members.  The reasoning for this isn't entirely clear.  The requirements around special members from LP have shifted multiple times since the feature was release, so it makes it difficult to pinpoint what this reasoning.  There may be a way to tweak this so special members can atleast continue to update their lionpath_updated_at timestamp while the fields are still blank (and make them subject to deletion).  Then, if the member's metadata is filled out, stop deleting them.

The new import data we are getting from LP should fix this.  Special Members will just be treated like regular committee members after that.


Fixing calculation of size of minimap when drawing for small files

Summary
Fixes issue described by https://github.com/godotengine/godot/issues/95727
This issue attempts to fix an error which occurs when loading small files and drawing the minimap in the text editor. See the linked issue for more details on how to get the error message to occur.

Fix
The changes in this PR adjust the conditions for which an index is modified when computing the size of the minimap. That modification causes the index to fall out of bounds (-1).

This fixes the error and shouldn't cause issues.
There are deeper issues here, since values like control_height should never be negative.

This fixes the error and shouldn't cause issues.
There are deeper issues here, since values like control_height should never be negative.

@kitbdev Do you think separate issues should be opened up for things like that?


Attempt at a very simple sharding protocol

Goal:

[x] simple sharding protocol with two message types: Status (for handshake) and Collations (to send collations)
[x] peers that listen to collations, add them to their local DB, and relay them to their peers
[x] peers that propose collations in random time intervals
[ ] tests
[ ] implement remaining suggestions in #570

For the tests I've tried to setup two local nodes that are connected to each other (https://github.com/ethereum/py-evm/compare/master...jannikluhn:sharding-protocol?expand=1#diff-f7c78d280d6b0f400c831d798adf0781R152), but I didn't manage to do that (the assert checking if the nodes are connected fails). Since I've been stuck for quite some time on that and haven't made much progress, could someone who's familiar with the networking code could have a quick look?
Cute Animal Picture

Seems to work now, so this would be ready for a preliminary review.
The tests pass at least locally. There might be timeout issues on CircleCI though because calculating the chunk root takes a lot of time.
Stuff I still on my todo list:

there's some logic in ShardingPeer which should probably be done in ShardSyncer, if only for consistency with the rest of the p2p codebase.
add some more elaborate tests (more peers, not directly connected peers, more shards)
make tests a little clearer by looking at the received/proposed collations


Fix multiple read attempts in fetch client

Fix multiple read attempts in fetch client. I caught this while working on https://github.com/connectrpc/examples-es/pull/1075. The fix similar to how we read the iterable: https://github.com/connectrpc/connect-es/blob/51470ebc229130150d5ba4147fe32b9c142cb83f/packages/connect/src/protocol/universal-fetch.ts#L129-L130

Seems like some code is calling [Symbol.asyncIterator]() twice. If this is in our code base, it would be great to understand where this happens, and avoid it. Did you take a look at how the duplicate call occurs?

It seems to be this line: https://github.com/connectrpc/connect-es/blob/e0bffbab4e75e19fd7eeb9eadabe050941d39e5f/packages/connect/src/protocol/async-iterable.ts#L596-L599 in pipe.

Yeah, looks like that line in async-iterable.ts would do it. I believe we should avoid that.
If you iterate over an Array or Map, you would expect a second iteration to restart from the first entry. Under the hood, [Symbol.iterator] is called once per iteration. I would expect [Symbol.asyncIterator] to have the same semantics. By calling it twice for what is effectively a single iteration, we dip out toes into undefined behavior.


No html is generated

Exporting multipage or single file does not generate the .html file in the export folder.
Operating System
Windows 10
Obsidian 1.4.12
Web HTML Export 1.7.2
To Reproduce
Steps to reproduce the behavior:

Export HTML
Define output folder
Single Page or multipage
Export

Single page -> the folder is empty
Multipage -> the folder contains the lib folder but no html
IMPORTANT: Error Log
loading markdown-table-editor plugin
Error with Permissions-Policy header: Unrecognized feature: 'ch-ua-form-factor'.
plugin:webpage-html-export:57355 loading webpage-html-export plugin
plugin:webpage-html-export:56603 Uncaught (in promise) TypeError: Failed to set the 'value' property on 'HTMLProgressElement': The provided double value is non-finite.
at Object._reportProgress (plugin:webpage-html-export:56603:25)
4plugin:webpage-html-export:56567 failed to find render leaf

plugin:webpage-html-export:56567 failed to find render leaf
plugin:webpage-html-export:56603 Uncaught (in promise) TypeError: Failed to set the 'value' property on 'HTMLProgressElement': The provided double value is non-finite.
at Object._reportProgress (plugin:webpage-html-export:56603:25)
_reportProgress @ plugin:webpage-html-export:56603
await in _reportProgress (async)
progress @ plugin:webpage-html-export:56725
createWithFiles @ plugin:webpage-html-export:55691
await in createWithFiles (async)
processTicksAndRejections @ node:internal/process/task_queues:95
await in processTicksAndRejections (async)
exportFiles @ plugin:webpage-html-export:57250
eval @ plugin:webpage-html-export:57396
await in eval (async)
e.handleEvent @ app.js:1
plugin:webpage-html-export:57324 (12) [_Path, _Path, _Path, _Path, _Path, _Path, _Path, _Path, _Path, _Path, _Path, _Path]
33plugin:webpage-html-export:56567 failed to find render leaf

This issue is closed but I still have this exact problem with 1.7.3 (Obsidian 1.4.14) - see https://github.com/KosmosisDire/obsidian-webpage-export/issues/204#issuecomment-1751993629


Loose version constraint for gem unicode-display_width

Unless it's incompatible

This is required to get Unicode v7.0.0 support.
It break on the Turkish lira sign, which we absolutely us.


raycast: 1.72.0 -> 1.73.0

Changelog: https://www.raycast.com/changelog/1-73-0

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 310094 run on aarch64-darwin 1

1 package built:

raycast


gitlab.liip.ch got a new ssh key

gitlab.liip.ch got a new ssh key

This PR is a : Bugfix

[ ] Documentation is written
[ ] parameters.yml.dist is updated
[ ] playbook.yml.dist is updated
[ x] Changelog was updated

Thanks! Merged in https://github.com/liip/drifter/commit/438627e94f95a2e274b9d77691b2dbd895437ed6.


CAB-3484 - Disable Search table autoupdate

Coverage remained the same at 83.474% when pulling 39e7374ffe07824fd607f76ef8d1ed4277f77dc2 on feature/CAB-3484 into 0168e76744a9800cf27a652f85f2c60add143f75 on develop.


[macOS SDK] Update macOS minimum version to 10.15

Proposed changes
Update macOS minimum version to 10.15
Type of change

[x] Feature work
[ ] Bug fix
[ ] Documentation
[ ] Engineering change
[ ] Test
[ ] Logging/Telemetry

Risk

[ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes)
[ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features)
[x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes)

Additional information
Updated unit tests to work for macOS 10.15

Similar to the MSAL repo, can you please remove the check "if (@available(macOS 10.15, *))" given than now they're not needed anymore?

Similar to the MSAL repo, can you please remove the check "if (@available(macOS 10.15, *))" given than now they're not needed anymore?

Removed all if (@available(macOS 10.15, *)) (or versions of it) and also standalone instances of #if __MAC_OS_X_VERSION_MAX_ALLOWED >= 101500\

If I search the following terms in IdentityCore, we still have some lines where they are present:
API_AVAILABLE(macos(14.0))
API_AVAILABLE(macos(13.0)

__MAC_OS_X_VERSION_MAX_ALLOWED >= 120000
@available(macOS 12.0, * -> (better to search for "macOS 12.0" as there are more results)

__MAC_OS_X_VERSION_MAX_ALLOWED >= 130000
macOS 13.0

__MAC_OS_X_VERSION_MAX_ALLOWED >= 140000
macOS 14.0

I'm not sure if the Objc folks may be better suited than us to solve them, but maybe we can sync?

If I search the following terms in IdentityCore, we still have some lines where they are present:
API_AVAILABLE(macos(14.0))
API_AVAILABLE(macos(13.0)

__MAC_OS_X_VERSION_MAX_ALLOWED >= 120000
@available(macOS 12.0, * -> (better to search for "macOS 12.0" as there are more results)

__MAC_OS_X_VERSION_MAX_ALLOWED >= 130000
macOS 13.0

__MAC_OS_X_VERSION_MAX_ALLOWED >= 140000
macOS 14.0

I'm not sure if the Objc folks may be better suited than us to solve them, but maybe we can sync?

So these checks are still ok, we are updating to macOS 10.15 minimum version not to macOS 15.0. So there should still be checks above 10.15 like __MAC_OS_X_VERSION_MAX_ALLOWED >= 120000 or API_AVAILABLE(macos(13.0).
The ones equal to 10.15 / 105000  or below should be removed

Added one comment, otherwise looks good

@spetrescu84, it seems the [MSAL C++]  Common core subtree update check macOS is failing with this error:
[msalobjc] Compiling MSAIMSIDWorkPlaceJoinUtilBase.m
❌ ***/s/deps/msalobjc/IdentityCore/src/workplacejoin/MSAIMSIDWorkPlaceJoinUtilBase.m:246:62: 'kSecUseDataProtectionKeychain' is only available on macOS 10.15 or newer [-Wunguarded-availability-new]
        [mutableCertQuery setObject:@YES forKey:(__bridge id)kSecUseDataProtectionKeychain];

https://identitydivision.visualstudio.com/IDDP/_build/results?buildId=1343056&view=logs&j=d46b93ad-1be7-5eab-6980-c78d65372179&t=0153d404-5636-5846-4ebd-361eb75124ec&l=572
can you please take a look?

@spetrescu84, it seems the [MSAL C++] Common core subtree update check macOS is failing with this error:
[msalobjc] Compiling MSAIMSIDWorkPlaceJoinUtilBase.m
❌ ***/s/deps/msalobjc/IdentityCore/src/workplacejoin/MSAIMSIDWorkPlaceJoinUtilBase.m:246:62: 'kSecUseDataProtectionKeychain' is only available on macOS 10.15 or newer [-Wunguarded-availability-new]
        [mutableCertQuery setObject:@YES forKey:(__bridge id)kSecUseDataProtectionKeychain];

https://identitydivision.visualstudio.com/IDDP/_build/results?buildId=1343056&view=logs&j=d46b93ad-1be7-5eab-6980-c78d65372179&t=0153d404-5636-5846-4ebd-361eb75124ec&l=572
can you please take a look?

The MSAL C++ Minimum version has to be updated to 10.15. This was discussed with @Veena11


Update SQL schemas

Deleted entities table, added columns to storage_key, and a few
other missing columns.
Now we'll be able to store collections of primitives and singletons.

It's possible I went a tad overboard with extension functions...


Add possibility to configure always enabled regex

Hello,
When I want to copy something from terminal (like a part of some output) I always use regex in search.
I believe many people also does this.
I thought it'd be really nice to be able to configure regex in search so it's always enabled.

Would you consider changing it to just remember the search options instead? I think that's more flexible than just having a setting for this one option.

I adjusted it so the search options are saved without settings.

:+1:
@allcontributors please add @matishadow for code


[Issue 349] Test failed on some locale environment

This patch makes test to work on some locale environment (e.g. Japanese)

Sorry, you've already added your name to the AUTHORS file in a different pull request. So we'll just take this one as is and move the setDefault ourselves.


ledger: investigate slow performance under contention

On current master (a092861e47331a2cbd19e98dd69eb34d19196d2d), run the following:
rm -rf cockroach-data; ./cockroach start --alsologtostderr # separate terminal
go run $GOPATH/src/github.com/cockroachdb/examples-go/ledger/main.go --concurrency 5 --sources 0 --destinations 1 postgres://root@localhost:26257?sslmode=disable

Note that this is a contended workload (on account_id=0), essentially five writers running the following:
SELECT causality_id, balance FROM accounts `+
		`WHERE account_id = 0 ORDER BY causality_id DESC LIMIT 1;
INSERT INTO accounts (
  posting_group_id,
  amount,
  account_id,
  causality_id, -- strictly increasing in absolute time. Only used for running balance.
  balance
) VALUES (/* touching both account_ids */);

You should (or rather, are forced to) see the following type of performance:
2017/03/17 02:22:04 5 postings/sec
2017/03/17 02:22:05 0 postings/sec
2017/03/17 02:22:06 0 postings/sec
2017/03/17 02:22:07 7 postings/sec
2017/03/17 02:22:08 48 postings/sec
2017/03/17 02:22:09 28 postings/sec
2017/03/17 02:22:10 36 postings/sec
2017/03/17 02:22:11 39 postings/sec
2017/03/17 02:22:12 8 postings/sec
2017/03/17 02:22:13 0 postings/sec
2017/03/17 02:22:14 0 postings/sec
2017/03/17 02:22:15 0 postings/sec
2017/03/17 02:22:16 0 postings/sec
2017/03/17 02:22:17 0 postings/sec
2017/03/17 02:22:18 0 postings/sec
2017/03/17 02:22:19 0 postings/sec
2017/03/17 02:22:20 0 postings/sec
2017/03/17 02:22:21 0 postings/sec
2017/03/17 02:22:22 0 postings/sec
2017/03/17 02:22:23 1 postings/sec
2017/03/17 02:22:24 0 postings/sec
2017/03/17 02:22:25 0 postings/sec
2017/03/17 02:22:26 0 postings/sec
2017/03/17 02:22:27 0 postings/sec
2017/03/17 02:22:28 0 postings/sec
2017/03/17 02:22:29 0 postings/sec
2017/03/17 02:22:30 0 postings/sec
2017/03/17 02:22:31 0 postings/sec
2017/03/17 02:22:32 0 postings/sec
2017/03/17 02:22:33 0 postings/sec
2017/03/17 02:22:34 0 postings/sec
2017/03/17 02:22:35 0 postings/sec
2017/03/17 02:22:36 0 postings/sec
2017/03/17 02:22:37 0 postings/sec
2017/03/17 02:22:38 0 postings/sec
2017/03/17 02:22:39 0 postings/sec

Lowering --concurrency I think avoids these really bad stalls, but may only exhibit them less frequently.
I assume these recover, but I haven't checked and am running out of juice. @petermattis for triage.

Moved to https://github.com/cockroachdb/cockroach/issues/14670.


Failed after max attempts: CaptureFailedError: [Errno 2] No such file or directory

Hello,
I've installed dpxdt, ran the initial test run with:
./run_url_pair_diff.sh
--upload_build_id=1
http://www.google.com
http://www.yahoo.com
It returns:
Creating release 2014-11-21 14:11:23.111688
Requesting captures
Marking runs as complete
Results viewable at: http://localhost:5000/release?id=1&name=2014-11-21+14%3A11%3A23.111688&number=1
But I get an error "Needs retry: CaptureFailedError: [Errno 2] No such file or directory":

Do I need to change permissions on a directory somewhere?
Thanks in advance.

Sorry for the delay. Do you have phantomjs installed properly? My guess is that's your problem.

I added some double-checks in 6fe0d173e29e5319d3a34b3903ecfd703306f96e


Adding more description on how teams approach reviews

Adding description on how teams approach code reviews and what an effective code review is

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@tktgius thanx for your contribution :balloon:


#1865 bug fixs

Fixes #ISSUSE_ID.
Changes proposed in this pull request:

Pull Request Test Coverage Report for Build 6685

12 of 12 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 73.365%

Totals

Change from base Build 6683:
-0.002%

Covered Lines:
10580

Relevant Lines:
14421

💛  - Coveralls


Filter result cleared after using search

When I filter a table using the filter of a column and use the search afterwards, it will remove the filter of the column and only filter using the text in the search field.
Look at this example: https://stackblitz.com/edit/react-sc5gme?file=index.js
If you search for 'Peter' in the 'First Name' column filter and then search for 'Parker' in the Search Text it will  show 'Lisa Parker' and 'Peter Parker'. But I would actually thing that it would combine both filters and only show 'Peter Parker'.
Used version:
react-bootstrap-table-next: 2.2.0
react-bootstrap-table2-filter: 1.1.4
react-bootstrap-table2-toolkit:  1.3.0

@Stefan-Reimer I will check this, thanks

Fixed: https://react-bootstrap-table.github.io/react-bootstrap-table2/blog/2019/02/24/version-bump.html


Report creation error

Installed grafana enterprise Version 11.2.0 (commit: c57667e4481563f5e6cf945b03bc0626caa4dbeb, branch: HEAD, enterprise-commit: 62cabea77752ae7ad849ef033952828565c4971b0c).
Installed grafana-image-renderer plugin v.3.11.4.
Installed Grafana Dashboard Reporter plugin v.1.6.0.
Created a service account and token.
Set up a link to the dashboard - http://<IP_ADDRESS>:3000/api/plugins/mahendrapaipuri-dashboardreporter-app/resources/report?dashUid=edwsangm9l8n4d/url-003-10-2-0-85?apitoken=.
When I try to create a report, I get an error - error generating report
In the log grafana messages:
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T15:55:26.78676079+03:00 level=info msg="generate report using config: Theme: light; Orientation: portrait; Layout: simple; Dashboard Mode: default; Time Zone: ; Encoded Logo: ; Max Renderer Workers: 2; Max Browser Workers: 2; Remote Chrome Addr: ; App URL: unset; TLS Skip verifiy: false; Included Panel IDs: all; Excluded Panel IDs: none" endpoint=callResource pluginID=mahendrapaipuri-dashboardreporter-app
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T15:55:26.787374763+03:00 level=info msg="generate report using local chrome" endpoint=callResource pluginID=mahendrapaipuri-dashboardreporter-app
logger=context userId=2 orgId=1 uname=sa-1-sa-dashboard t=2024-09-09T15:55:26.917542976+03:00 level=info msg="Request Completed" method=GET path=/api/dashboards/uid/edwsangm9l8n4d/url-003-10-2-0-85 status=404 remote_addr=[::1] time_ms=129 duration=129.837502ms size=24 referer= handler=notfound status_source=server
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T15:55:28.732443158+03:00 level=warn msg="error fetching dashboard from browser, falling back to API" error="error fetching dashboard from browser: javascript did not return any dashboard data" pluginID=mahendrapaipuri-dashboardreporter-app endpoint=callResource
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T15:55:28.732722188+03:00 level=warn msg="error(s) fetching dashboard model and data" dash_uid="edwsangm9l8n4d/url-003-10-2-0-85?apitoken=<token>" endpoint=callResource err="error fetching dashboard: error fetching dashboard from API: dashboard request does not return 200 OK: URL: http://localhost:3000/api/dashboards/uid/edwsangm9l8n4d/url-003-10-2-0-85?apitoken=<token>. Status: 404 Not Found, message: {\"message\":\"Not found\"}\n" pluginID=mahendrapaipuri-dashboardreporter-app
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T15:55:28.732926659+03:00 level=error msg="error generating report" endpoint=callResource err="error fetching dashboard edwsangm9l8n4d/url-003-10-2-0-85?apitoken=<token>: error fetching dashboard: error fetching dashboard from API: dashboard request does not return 200 OK: URL: http://localhost:3000/api/dashboards/uid/edwsangm9l8n4d/url-003-10-2-0-85?apitoken=<token>. Status: 404 Not Found, message: {\"message\":\"Not found\"}\n" pluginID=mahendrapaipuri-dashboardreporter-app
logger=context userId=1 orgId=1 uname=admin t=2024-09-09T15:55:28.733604553+03:00 level=error msg="Request Completed" method=GET path=/api/plugins/mahendrapaipuri-dashboardreporter-app/resources/report status=500 remote_addr=<IP_ADDRESS> time_ms=2098 duration=2.098309795s size=24 referer= handler=/api/plugins/:pluginId/resources/* status_source=downstream
logger=context userId=0 orgId=0 uname= t=2024-09-09T15:55:29.535347652+03:00 level=info msg="Request Completed" method=GET path=/favicon.ico status=302 remote_addr=<IP_ADDRESS> time_ms=0 duration=114.015µs size=29 referer= handler=public-assets status_source=server

Please help me understand the problem.

Hey @AndryAsh
You are not supposed to send API token from query parameters. You need to configure the token in the plugin's confirguration Service Account Token in Grafana UI. More details in docs.
As you are using more recent version of Grafana, you can skip this step by enabling externalServiceAccounts feature flag. Please check this section on how to do it.

Yes, that's how it's done, but it's giving an error in the log:
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09-09T17:17:58.887727259+03:00 level=error msg=“error generating report” endpoint=callResource err=“error fetching dashboard edwsangm9l8n4d: error building dashboard model: browser: no dashboard data found” pluginID=mahendrapaipuri-dashboardreporter-app
It looks like the plugin can't find the dashboard by UID.
I found the UID of the dashboard in the JSON Model dashboard:
  “timepicker": {},   “timezone": {}, ‘browser’,   “title": “URL-003 (<IP_ADDRESS>)”,   “uid": ‘edwsangm9l8n4d’,   “version": 19,   “weekStart": “”

Could you please set Grafana in debug mode, restart Grafana and share the logs right from the point where plugin is loaded till the report generation error?

You will need to find [log] section in grafana.ini, if already exists or add the section if it doesnt with following:
[log]
level= debug

Here are the docs

Here is grafana's log from the time it was loaded until the end of the plugin execution
logger=settings t=2024-09-09T17:58:20.782471324+03:00 level=info msg="Starting Grafana" version=11.2.0 commit=c57667e4481563f5e6cf945b03bc0626caa4dbeb branch=HEAD compiled=2024-09-09T17:58:20+03:00 logger=settings t=2024-09-09T17:58:20.784065913+03:00 level=info msg="Config loaded from" file=/usr/share/grafana/conf/defaults.ini logger=settings t=2024-09-09T17:58:20.784238132+03:00 level=info msg="Config loaded from" file=/etc/grafana/grafana.ini logger=settings t=2024-09-09T17:58:20.784386491+03:00 level=info msg="Config overridden from command line" arg="default.paths.data=/var/lib/grafana" logger=settings t=2024-09-09T17:58:20.784634018+03:00 level=info msg="Config overridden from command line" arg="default.paths.logs=/var/log/grafana" logger=settings t=2024-09-09T17:58:20.784815144+03:00 level=info msg="Config overridden from command line" arg="default.paths.plugins=/var/lib/grafana/plugins" logger=settings t=2024-09-09T17:58:20.78497767+03:00 level=info msg="Config overridden from command line" arg="default.paths.provisioning=/etc/grafana/provisioning" logger=settings t=2024-09-09T17:58:20.785137654+03:00 level=info msg=Target target=[all] logger=settings t=2024-09-09T17:58:20.785310794+03:00 level=info msg="Path Home" path=/usr/share/grafana logger=settings t=2024-09-09T17:58:20.785484882+03:00 level=info msg="Path Data" path=/var/lib/grafana logger=settings t=2024-09-09T17:58:20.78564378+03:00 level=info msg="Path Logs" path=/var/log/grafana logger=settings t=2024-09-09T17:58:20.785828161+03:00 level=info msg="Path Plugins" path=/var/lib/grafana/plugins logger=settings t=2024-09-09T17:58:20.786007079+03:00 level=info msg="Path Provisioning" path=/etc/grafana/provisioning logger=settings t=2024-09-09T17:58:20.78616456+03:00 level=info msg="App mode production" logger=featuremgmt t=2024-09-09T17:58:20.78748767+03:00 level=info msg=FeatureToggles cloudWatchCrossAccountQuerying=true externalServiceAccounts=true addFieldFromCalculationStatFunctions=true nestedFolders=true panelMonitoring=true cloudWatchNewLabelParsing=true prometheusConfigOverhaulAuth=true alertingNoDataErrorExecution=true idForwarding=true logsContextDatasourceUi=true groupToNestedTableTransformation=true logsExploreTableVisualisation=true tlsMemcached=true formatString=true ssoSettingsApi=true dashgpt=true publicDashboards=true alertingInsights=true kubernetesPlaylists=true prometheusAzureOverrideAudience=true prometheusMetricEncyclopedia=true recoveryThreshold=true exploreMetrics=true angularDeprecationUI=true lokiMetricDataplane=true lokiQuerySplitting=true annotationPermissionUpdate=true logsInfiniteScrolling=true recordedQueriesMulti=true influxdbBackendMigration=true correlations=true lokiStructuredMetadata=true alertingSimplifiedRouting=true logRowsPopoverMenu=true prometheusDataplane=true autoMigrateXYChartPanel=true lokiQueryHints=true accessControlOnCall=true dataplaneFrontendFallback=true awsAsyncQueryCaching=true transformationsRedesign=true transformationsVariableSupport=true managedPluginsInstall=true topnav=true cloudWatchRoundUpEndTime=true logger=sqlstore t=2024-09-09T17:58:20.787685942+03:00 level=info msg="Connecting to DB" dbtype=sqlite3 logger=migrator t=2024-09-09T17:58:20.80856908+03:00 level=info msg="Locking database" logger=migrator t=2024-09-09T17:58:20.808636812+03:00 level=info msg="Starting DB migrations" logger=migrator t=2024-09-09T17:58:20.853452881+03:00 level=info msg="migrations completed" performed=0 skipped=689 duration=2.673491ms logger=migrator t=2024-09-09T17:58:20.855323791+03:00 level=info msg="Unlocking database" logger=licensing t=2024-09-09T17:58:20.856823125+03:00 level=info msg="Validated license token" appURL=http://localhost:3000/ source=disk status=NotFound logger=secrets t=2024-09-09T17:58:20.856961884+03:00 level=info msg="Envelope encryption state" enabled=true currentprovider=secretKey.v1 logger=plugins.registration t=2024-09-09T17:58:25.838439015+03:00 level=info msg="Plugin registered" pluginId=grafana-image-renderer logger=plugin.angulardetectorsprovider.dynamic t=2024-09-09T17:58:25.843577545+03:00 level=info msg="Restored cache from database" duration=3.590406ms logger=plugin.store t=2024-09-09T17:58:25.85040583+03:00 level=info msg="Loading plugins..." logger=plugins.registration t=2024-09-09T17:58:25.947624283+03:00 level=error msg="Could not register plugin" pluginId=xychart error="plugin xychart is already registered" logger=plugins.initialization t=2024-09-09T17:58:25.947723079+03:00 level=error msg="Could not initialize plugin" pluginId=xychart error="plugin xychart is already registered" logger=plugins.registration t=2024-09-09T17:58:27.338290116+03:00 level=info msg="Plugin registered" pluginId=alexanderzobnin-zabbix-app logger=plugin.alexanderzobnin-zabbix-datasource t=2024-09-09T17:58:27.351150825+03:00 level=info msg=Profiler enabled=false logger=plugins.registration t=2024-09-09T17:58:27.353817033+03:00 level=info msg="Plugin registered" pluginId=alexanderzobnin-zabbix-datasource logger=plugins.registration t=2024-09-09T17:58:27.353949067+03:00 level=info msg="Plugin registered" pluginId=alexanderzobnin-zabbix-triggers-panel logger=plugin.signature.validator t=2024-09-09T17:58:27.359821345+03:00 level=warn msg="Permitting unsigned plugin. This is not recommended" pluginId=mahendrapaipuri-dashboardreporter-app logger=plugins.registration t=2024-09-09T17:58:27.436234642+03:00 level=info msg="Plugin registered" pluginId=mahendrapaipuri-dashboardreporter-app logger=plugin.store t=2024-09-09T17:58:27.436328153+03:00 level=info msg="Plugins loaded" count=58 duration=1.585925786s logger=caching.service t=2024-09-09T17:58:27.439549505+03:00 level=info msg="Caching service is disabled" logger=query_data t=2024-09-09T17:58:27.448221478+03:00 level=info msg="Query Service initialization" logger=live.push_http t=2024-09-09T17:58:27.460322327+03:00 level=info msg="Live Push Gateway initialization" logger=ngalert.notifier.alertmanager org=1 t=2024-09-09T17:58:27.467181171+03:00 level=info msg="Applying new configuration to Alertmanager" configHash=d2c56faca6af2a5772ff4253222f7386 logger=ngalert.state.manager t=2024-09-09T17:58:27.475896209+03:00 level=info msg="Running in alternative execution of Error/NoData mode" logger=infra.usagestats.collector t=2024-09-09T17:58:27.482359669+03:00 level=info msg="registering usage stat providers" usageStatsProvidersLen=3 logger=server t=2024-09-09T17:58:27.482532425+03:00 level=info msg="Writing PID file" path=/run/grafana/grafana-server.pid pid=3023 logger=provisioning.alerting t=2024-09-09T17:58:27.484971159+03:00 level=info msg="starting to provision alerting" logger=provisioning.alerting t=2024-09-09T17:58:27.485029338+03:00 level=info msg="finished to provision alerting" logger=grafanaStorageLogger t=2024-09-09T17:58:27.485725369+03:00 level=info msg="Storage starting" logger=ngalert.state.manager t=2024-09-09T17:58:27.485901529+03:00 level=info msg="Warming state cache for startup" logger=provisioning.dashboard t=2024-09-09T17:58:27.487985365+03:00 level=info msg="starting to provision dashboards" logger=provisioning.dashboard t=2024-09-09T17:58:27.488097663+03:00 level=info msg="finished to provision dashboards" logger=http.server t=2024-09-09T17:58:27.494004643+03:00 level=info msg="HTTP Server Listen" address=[::]:3000 protocol=http subUrl= socket= logger=ngalert.multiorg.alertmanager t=2024-09-09T17:58:27.494742213+03:00 level=info msg="Starting MultiOrg Alertmanager" logger=report t=2024-09-09T17:58:27.501991363+03:00 level=warn msg="Scheduling and sending of reports disabled, SMTP is not configured and enabled. Configure SMTP to enable." logger=ngalert.state.manager t=2024-09-09T17:58:27.557617273+03:00 level=info msg="State cache has been initialized" states=0 duration=71.707977ms logger=ngalert.scheduler t=2024-09-09T17:58:27.55775571+03:00 level=info msg="Starting scheduler" tickInterval=10s maxAttempts=1 logger=ticker t=2024-09-09T17:58:27.557886311+03:00 level=info msg=starting first_tick=2024-09-09T17:58:30+03:00 logger=grafana.update.checker t=2024-09-09T17:58:27.594013913+03:00 level=info msg="Update check succeeded" duration=107.321619ms logger=plugins.update.checker t=2024-09-09T17:58:27.594024664+03:00 level=info msg="Update check succeeded" duration=108.296504ms logger=grafana-apiserver t=2024-09-09T17:58:28.059912834+03:00 level=info msg="Adding GroupVersion playlist.grafana.app v0alpha1 to ResourceManager" logger=grafana-apiserver t=2024-09-09T17:58:28.061197825+03:00 level=info msg="Adding GroupVersion featuretoggle.grafana.app v0alpha1 to ResourceManager" logger=context userId=1 orgId=1 uname=admin t=2024-09-09T17:58:32.544858814+03:00 level=info msg="Request Completed" method=GET path=/api/live/ws status=-1 remote_addr=<IP_ADDRESS> time_ms=19 duration=19.1931ms size=0 referer= handler=/api/live/ws status_source=server logger=live t=2024-09-09T17:58:32.551109554+03:00 level=info msg="Initialized channel handler" channel=grafana/dashboard/uid/edwsangm9l8n4d address=grafana/dashboard/uid/edwsangm9l8n4d logger=context userId=1 orgId=1 uname=admin t=2024-09-09T18:00:06.468886402+03:00 level=info msg="Request Completed" method=GET path=/api/live/ws status=-1 remote_addr=<IP_ADDRESS> time_ms=7 duration=7.056901ms size=0 referer= handler=/api/live/ws status_source=server logger=infra.usagestats t=2024-09-09T18:00:12.501297497+03:00 level=info msg="Usage stats are ready to report" logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T18:00:13.349446791+03:00 level=info msg="new instance of plugin app created" endpoint=callResource pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T18:00:13.350720216+03:00 level=info msg="starting plugin with initial config: Theme: light; Orientation: portrait; Layout: simple; Dashboard Mode: default; Time Zone: ; Encoded Logo: ; Max Renderer Workers: 2; Max Browser Workers: 2; Remote Chrome Addr: ; App URL: unset; TLS Skip verifiy: false; Included Panel IDs: all; Excluded Panel IDs: none" endpoint=callResource pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T18:00:14.478069198+03:00 level=info msg="generate report using config: Theme: light; Orientation: portrait; Layout: simple; Dashboard Mode: default; Time Zone: ; Encoded Logo: ; Max Renderer Workers: 2; Max Browser Workers: 2; Remote Chrome Addr: ; App URL: unset; TLS Skip verifiy: false; Included Panel IDs: all; Excluded Panel IDs: none" endpoint=callResource pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T18:00:14.478482901+03:00 level=info msg="generate report using local chrome" endpoint=callResource pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T18:00:16.284539586+03:00 level=warn msg="error fetching dashboard from browser, falling back to API" endpoint=callResource error="error fetching dashboard from browser: javascript did not return any dashboard data" pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T18:00:16.285399321+03:00 level=warn msg="failed to get panels from browser data" endpoint=callResource error="browser: no dashboard data found" pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T18:00:16.285564688+03:00 level=warn msg="error(s) fetching dashboard model and data" dash_uid=edwsangm9l8n4d endpoint=callResource err="error building dashboard model: browser: no dashboard data found" pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T18:00:16.28569275+03:00 level=error msg="error generating report" endpoint=callResource err="error fetching dashboard edwsangm9l8n4d: error building dashboard model: browser: no dashboard data found" pluginID=mahendrapaipuri-dashboardreporter-app logger=context userId=1 orgId=1 uname=admin t=2024-09-09T18:00:16.28681032+03:00 level=error msg="Request Completed" method=GET path=/api/plugins/mahendrapaipuri-dashboardreporter-app/resources/report status=500 remote_addr=<IP_ADDRESS> time_ms=3013 duration=3.013886833s size=24 referer= handler=/api/plugins/:pluginId/resources/* status_source=downstream logger=context userId=0 orgId=0 uname= t=2024-09-09T18:00:17.239909536+03:00 level=info msg="Request Completed" method=GET path=/favicon.ico status=302 remote_addr=<IP_ADDRESS> time_ms=0 duration=514.639µs size=29 referer= handler=public-assets status_source=server logger=server t=2024-09-09T18:00:34.085254397+03:00 level=info msg="Shutdown started" reason="System signal: terminated" logger=ticker t=2024-09-09T18:00:34.085442021+03:00 level=info msg=stopped last_tick=2024-09-09T18:00:30+03:00 logger=tracing t=2024-09-09T18:00:34.086388536+03:00 level=info msg="Closing tracing" logger=grafana-apiserver t=2024-09-09T18:00:34.087457442+03:00 level=info msg="StorageObjectCountTracker pruner is exiting" logger=plugin.alexanderzobnin-zabbix-datasource t=2024-09-09T18:00:34.098207524+03:00 level=error msg="plugin process exited" plugin=/var/lib/grafana/plugins/alexanderzobnin-zabbix-app/gpx_zabbix-plugin_linux_amd64 id=3036 error="signal: terminated" logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-09T18:00:34.101247083+03:00 level=error msg="plugin process exited" plugin=/var/lib/grafana/plugins/mahendrapaipuri-dashboardreporter-app/gpx_dashboardreporter-app_linux_amd64 id=3045 error="signal: terminated" logger=plugin.grafana-image-renderer t=2024-09-09T18:00:34.11918568+03:00 level=error msg="plugin process exited" plugin=/var/lib/grafana/plugins/grafana-image-renderer/plugin_start_linux_amd64 id=3057 error="signal: terminated"

I dont see any obvious errors. Did you install chromium on Grafana server? If not, could you try installing chromium and retry?

Here is the log file with debug mode enabled.
Uploading grafana.log…

Yes, I have installed chromium:
`
apt install chromium
dpkg -l | grep chromium
ii  chromium                      90.0.4430.212-1~deb10u1             amd64        web browser
ii  chromium-common               90.0.4430.212-1~deb10u1             amd64        web browser - common resources used by the chromium packages
ii  chromium-sandbox              90.0.4430.212-1~deb10u1             amd64        web browser - setuid security sandbox for chromium
`

Here is the log file with debug mode enabled. Uploading grafana.log…

The log file is not available. Please reupload it.

grafana.log

Can you share your dashboard JSON model?

dashboard.json

I imported Test Dashboard Collapsed and started creating the report. Result: error generating report
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T16:22:53.047723142+03:00 level=info msg="generate report using config: Theme: light; Orientation: portrait; Layout: simple; Dashboard Mode: default; Time Zone: ; Encoded Logo: ; Max Renderer Workers: 2; Max Browser Workers: 2; Remote Chrome Addr: ; App URL: unset; TLS Skip verifiy: false; Included Panel IDs: all; Excluded Panel IDs: none" endpoint=callResource pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T16:22:53.04810095+03:00 level=info msg="generate report using local chrome" endpoint=callResource pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T16:22:54.664209474+03:00 level=warn msg="error fetching dashboard from browser, falling back to API" endpoint=callResource error="error fetching dashboard from browser: javascript did not return any dashboard data" pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T16:22:54.665693464+03:00 level=warn msg="failed to get panels from browser data" endpoint=callResource error="browser: no dashboard data found" pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T16:22:54.665913156+03:00 level=warn msg="error(s) fetching dashboard model and data" dash_uid=e472bbf0-140c-4852-a74b-1a4c32202659 endpoint=callResource err="error building dashboard model: browser: no dashboard data found" pluginID=mahendrapaipuri-dashboardreporter-app logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T16:22:54.666079324+03:00 level=error msg="error generating report" pluginID=mahendrapaipuri-dashboardreporter-app endpoint=callResource err="error fetching dashboard e472bbf0-140c-4852-a74b-1a4c32202659: error building dashboard model: browser: no dashboard data found" logger=context userId=1 orgId=1 uname=admin t=2024-09-10T16:22:54.667312359+03:00 level=error msg="Request Completed" method=GET path=/api/plugins/mahendrapaipuri-dashboardreporter-app/resources/report status=500 remote_addr=<IP_ADDRESS> time_ms=1782 duration=1.782890583s size=24 referer= handler=/api/plugins/:pluginId/resources/* status_source=downstream logger=context userId=0 orgId=0 uname= t=2024-09-10T16:22:55.501304133+03:00 level=info msg="Request Completed" method=GET path=/favicon.ico status=302 remote_addr=<IP_ADDRESS> time_ms=0 duration=231.465µs size=29 referer= handler=public-assets status_source=server

Hey, I am out of ideas. Seems like the issue is with chromium on your server. Maybe uninstall and reinstall it again?

I am also having a similar issue. It works on my local but not on our server. I added the sample dashboard and get errors like this:
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T19:58:15.025917223Z level=warn msg="error fetching dashboard from browser, falling back to API" endpoint=callResource error="error fetching dashboard from browser: javascript did not return any dashboard data" pluginID=mahendrapaipuri-dashboardreporter-app
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T19:58:15.027070068Z level=warn msg="failed to get panels from browser data" endpoint=callResource error="browser: no dashboard data found" pluginID=mahendrapaipuri-dashboardreporter-app
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T19:58:15.02710253Z level=warn msg="error(s) fetching dashboard model and data" dash_uid=e472bbf0-140c-4852-a74b-1a4c32202659 endpoint=callResource err="error building dashboard model: browser: no dashboard data found" pluginID=mahendrapaipuri-dashboardreporter-app
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T19:58:15.027124077Z level=error msg="error generating report" pluginID=mahendrapaipuri-dashboardreporter-app endpoint=callResource err="error fetching dashboard e472bbf0-140c-4852-a74b-1a4c32202659: error building dashboard model: browser: no dashboard data found"
logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-09-10T19:58:15.027150817Z level=debug msg="Plugin Request Completed" duration=3.692396905s endpoint=callResource pluginID=mahendrapaipuri-dashboardreporter-app status=ok statusSource=plugin
logger=context userId=32 orgId=1<EMAIL_ADDRESS>t=2024-09-10T19:58:15.02751837Z level=error msg="Request Completed" method=GET path=/api/plugins/mahendrapaipuri-dashboardreporter-app/resources/report status=500 remote_addr=<IP_ADDRESS> time_ms=3703 duration=3.703377052s size=24 referer= handler=/api/plugins/:pluginId/resources/* status_source=downstream
logger=context userId=0 orgId=0 uname= t=2024-09-10T19:58:15.062016468Z level=info msg="Request Completed" method=GET path=/favicon.ico status=302 remote_addr=<IP_ADDRESS> time_ms=0 duration=418.009µs size=29 referer=https://charting.dev.mosaic.hart

Ok, that is worrying. Could you please share your full environment details? OS, Chromium and Grafana versions? I will try to reproduce it on containérised environment.

Your documentation says that when installing from the git repository the plugin already includes chromium, but after installing it I didn't find it. Can you give me a link to get the version of chromium with which the plugin works normally?

Your documentation says that when installing from the git repository the plugin already includes chromium, but after installing it I didn't find it. Can you give me a link to get the version of chromium with which the plugin works normally?

No, the plugin does not ship any chromium with it. So, not sure where you found this doc. It should work with any chromium.
Could you share your environment details? Your OS version and chromium version. I will try to reproduce it in a container.

OS Debian GNU/Linux 10 (buster)
Chromium 90.0.4430.212 built on Debian 10.9, running on Debian 10.13

Our environment is pulled from the grafana 11 Dockerfile, so it looks like alpine 3.19.1 with Node 20
Checking in the Github Workflow it looks like chromium 124.0.6367.78-r0 is installed.
I should note that this runs fine on my local

Well, the plugin uses Grafana's base Dockerfile as well to test in CI and we add chromium using apk add chromium not really controlling the version.
If it is not working on server, I suspect it can be only due to some missing dependencies for chromium. I will try to find to debug with the environment posted @AndryAsh

I can reproduce this issue on Chromium 90 in Debian 10. Not sure why Chromium does not execute JS properly. Anyways I found there is a small regression as well. #109 should fix the regression and when Chromium fails to fetch dashboard, the plugin should go ahead using dashboard from API request.
@AndryAsh Could you please test the patch? You can download plugin artifacts here. Ensure to add execute bits (+x) on gpx_* files in artifacts. I made a test with your environment and it works now. I will try to make a release tmrw!!

I installed the patch, everything works fine - the report is generated
Thank you very much!

@AndryAsh Thanks a lot for testing. I will make a release today!!

This fixed ours too! Thanks so much!


Future Minimum Price

Closes mikebryant/ac-nh-turnip-prices#43

Ah, this seems to be sort of a duplicate of #55. Sorry about that

Sort of, yes, but the contributor of that one has been inactive for about a week and their PR has conflicts and cannot be merged. So, your work is still viable!

Another question... Should the maximum column just show future prices too? Then the two columns would be consistent. Also, a user might see the the potential maximum price and try holding out for it, not realizing that perhaps that price was in the past.

Yes, no problem. That's a lot better @theRTC204

If this merges, it also Closes #55
(Not sure if the auto link works from PR to PR, but I wanted to find out, hah)


Missing end of line semicolons - "Differences Between Type Aliases and Interfaces"

Under "Differences Between Type Aliases and Interfaces" > "Interface" > "Extending an interface", the last three lines are missing semicolons.
I'm not yet super technically proficient - and it seems semicolons are optional more than I expected. But I'd imagine the 'extending an interface' on the left should have a parallel structure to the 'Extending a type via intersections' on the right in all ways not relevant to the point that's being made. I initially wondered if it was trying to make some comment about semicolon use for interfaces.
Thanks!

There's a PR for this: https://github.com/microsoft/TypeScript-Website/pull/2435
Semis are optional in types, but we use prettier on all code samples to make them consistent


[integration-cli] [--net none] Fix TestSearchOnCentralRegistry

Fix TestSearchOnCentralRegistry so it will still be a functional test, but will pass when the test container has --net none.
Use the local registry in the container to pull an image. Change the name of the test to reflect it is no longer pulling from the central registry.
Error output when tests are run with --net none:
--- FAIL: TestSearchOnCentralRegistry (0.08s)
	docker_cli_search_test.go:14: failed to search on the central registry: time="2015-02-11T23:25:57Z" level="fatal" msg="Error response from daemon: Get https://index.docker.io/v1/search?q=busybox: dial tcp: lookup index.docker.io on <IP_ADDRESS>:53: dial udp <IP_ADDRESS>:53: network is unreachable"
		, exit status 1

#dibs


O9s triggers

Added some logic for phase/path tracking in here.

Sorry, I'm still confused about the initial phase trigger.
It looks like your patch is:
long => fire
lat => water
And I think it's supposed to be?
long => water
lat => water
damning edict => fire
Am I mistaken?

My understanding of what the timeline file is and what it should be is what I listed in my previous comment above: https://github.com/quisquous/cactbot/pull/239#issuecomment-426904086

Ok no worries. I might be confused on that I  suppose


Fix: set enable-kube-api-proxy to false.

Signed-off-by: xuezhaojun<EMAIL_ADDRESS>

/hold
Wait for cluster-proxy (midstream) to sync the changes.

/assign @skeeey

/lgtm

/unhold


Added institutional affiliations of Board members

Addresses comment to pull-request #20

Thanks! UV refers to a faculty, while IBV and IFI refer to institutes. Maybe use (MN) for me instead?

It's the one abbreviation I didn't change. Will do that later.


Can't disable battery optimizations (conflict w/ MicroG core)

Having MicroG core and Vanced MicroG installed conflicts in the battery optimizations settings on Huawei.
Meaning you can't disable battery optimizations, so notifications aren't working despite everything else being set up and connected.
Huawei P40

Fixed on <IP_ADDRESS>218

Finally fixed! Thank you!

Fixed!


delete files and directories

create this as a new subsection under basic commands

reference to the corresponding chapter in The Linux Command Line

describe a simple example

write down concrete tasks which has to be performed by the student

provide sample solutions in a *.sh file

Würde Issue #5 und #6 zu einem Kapitel über File Operations bündeln


Update PPP

Codecov Report

Merging #235 (4ad15ce) into master (d4882a3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #235   +/-   ##
=========================================
  Coverage     68.98%   68.98%
  Complexity      896      896
=========================================
  Files           116      116
  Lines          3186     3186
  Branches        402      402
=========================================
  Hits           2198     2198
  Misses          859      859
  Partials        129      129

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 d4882a3...4ad15ce. Read the comment docs.


Correct several issues with selection ranges.

I found that selecting blocks was pretty buggy on Chrome. When poking around I discovered several assumptions that were causing the selections to get randomly removed and corrected them. I'm confident there are more issues out there but I haven't had a chance to dig deeper yet.

@nathanfaucett No worries man! And I apologize if I'm not dropping these changes in the right place. I'm relatively new to both Svelte and Slate so I'm sure I'll make some mistakes hahaha


Significant concerns regarding the ranking methodology and evaluation results reported by ParsBench

Hi,
Thank you for your effort and benchmarks. I just want to mention couple of things.
There are significant concerns regarding the ranking methodology and evaluation results reported by ParsBench, which I will outline below.
Ranking Methodology Issues:
ParsBench ranks models based on the average accuracy across several benchmarks without considering the differing difficulty levels and validity of these benchmarks. For example, they average results from datasets like Khayyam, where model performance is generally below 50%, with benchmarks like ParsiNLU and Persian Math, where performance hovers around 70-80%. This method disregards the differences in difficulty and data quality between these datasets, leading to potentially misleading rankings. Additionally, the datasets used in the evaluation have varying levels of difficulty and data cleanliness, which are not accounted for in the ranking process. Some datasets might not be well-curated, further affecting the reliability of the results.
Inconsistent Persian MMLU Results:
The results reported for Persian MMLU are inconsistent with other evaluations. For instance, GPT-4 surprisingly scores only 31%, which is unexpectedly low. Moreover, the recent evaluation of JabirLLM-400B on Persian MMLU resulted in an accuracy of about 29%, while LLaMA 3 (70B) scored 37%. This suggests that the model’s understanding of Persian may have been compromised, assuming the evaluation is correct.
Anomalous Results with Qwen Models:
A particularly strange finding is that the Qwen 2 (7B) model outperforms the Qwen 2 (70B) model on the Persian MMLU benchmark, which contradicts the expectation that a larger model would generally perform better.

Dear MoSunny,
Since answered your message in the HuggingFace discussion. I will close this issue here.
Thanks once again for sharing your concerns.


[3117] Show provider name in record card and record when signed in as an admin

Context
Showing provider name / provider name and code
Changes proposed in this pull request
Showing provider name for application record card
Showing provider name and code for record details
Guidance to review

 Show provider name in record card and record when signed in as an admin


fixed typo in Specify observables in the Pauli basis

fixes #2172

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you! @lucachiese25 can you please sign the contributor license agreement from the comment up above?

Thank you! @lucachiese25 can you please sign the contributor license agreement from the comment up above?

I did, I don't know why it seems I didn't it.


Incomplete manpage for cjxl

Describe the bug
doc/man/cjxl.txt seems to be missing several of the options described in tools/cjxl.cc's AddCommandLineOptions function. I noticed this problem when looking for how to use --resampling.
I am used to thinking a manpage should show all options and provide more explanation on them than --help.
To Reproduce
Run cjxl -v --help. I suppose the verbosity-gate is what caused the original man-writer to omit these options. I guess the gate can be reflected in the man by putting them in an "Advanced Options" section.
Wait, cjxl -v -v --help reveals more? Time for a "Professional options" section.
Environment
It's not useful here, but I'll do it.

OS: macOS
Compiler version: Apple clang version 12.0.5 (clang-1<IP_ADDRESS>)
CPU type: x86_64
cjxl/djxl version string: cjxl [v0.3.7 | SIMD supported: AVX2,SSE4]

Additional context
None for now.

I will try and handle this myself. (Copy-and-pasting documentation should be relaxing, right?) If you don't hear from me in two weeks, feel free to take over.

are photon noise and how to use/force 8, 10 bits written in the manpage?

Not currently, no. --override_bitdepth=8 is a thing, so it will be added. From what I can tell it is per-channel

and whatever iulia comsa added to delta, i don't think there are instructions how to use l 1 p 0 s 1    that short of thing, which parameter are needed, which you can avoid and what are the best to combine.

One of the reasons we didn't put many of the encode options in the manpage is that they are still experimental and subject to change. For example for the delta palette approach to near lossless: it is still evolving, including possibly the command line syntax for it. There might also be options that will disappear once we make cjxl libjxl-based (internally using the encode api, instead of directly calling encode functions), since some experimental things will not be worth exposing to the api if we have good enough defaults/heuristics for them.

@jonsneyers, is it okay to put the "verbose" -v thing in only instead? That set feels generally less experimental and more useful. Or we can wait till PR time to figure that out.

Yes, makes sense to start with the options in the default help screen and the -v one, and wait with the -v -v ones...

Interesting what -E 3 does and why it is effective.
https://github.com/libjxl/libjxl/blob/2f872a190f79390ba27a66b2ecb14d51114c12ef/tools/cjxl.cc#L441-L443

I think we have now all stuff with -v -v -v -v, please reopen if something is missing..


[vSphere]: After fresh install: bad certificate, all pods are running, no access to console

Hi,
a few minutes ago I created a new cluster on vSphere from
https://origin-release.svc.ci.openshift.org/releasestream/4.4.0-0.okd/release/4.4.0-0.okd-2020-03-21-112849
Everything went fine during the installation. But I couldn't open the console.
The console pods and authentication pods showed "bad certificate" errors. The link to the console only showed the 'Application is not available' message.
The time between openshift-install create ignition-config and the installation was < 1 hour.
Here's the must-gather tarball:
https://drive.google.com/file/d/1kmG7_HE3XjUO68vIs45tkL5HUfsoY8zb/view?usp=sharing
I reinstalled the cluster afterwards exactly the same way: this time everything worked. I didn't even recreate the ignition files. I reused the same ignition files that resulted in this error here.
Greetings,
Josef

Did you try restarting the console pods?
Just glancing at the openshift-console-operator pod logs I saw this (not sure if related):
2020-03-22T21:03:59.839432928Z E0322 21:03:59.837094       1 controller.go:129] {Console Console} failed with: route is not available at canonical host []
2020-03-22T21:04:00.3844661Z E0322 21:04:00.384431       1 status.go:73] OCDownloadsSyncDegraded FailedCreate ConsoleCLIDownload.console.openshift.io "oc-cli-downloads" is invalid: spec.links.href: Invalid value: "": spec.links.href in body should match '^https://'

Also seeing this in the openshift-console pod logs:
2020-03-22T21:21:22.008293745Z 2020-03-22T21:21:22Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.c1.okd4.cloud.rsint.net/oauth/token failed: Head https://oauth-openshift.apps.c1.okd4.cloud.rsint.net: x509: certificate signed by unknown authority

Is this the specific cert error you're referring to @jomeier?
Has this error happened more than once (anyone else)?

Yes. I restarted them.

I installed a nightly were no upgrade tests habe been running. Did not happen between the updates of the Betas.


[Discussion] Per-segment performance analysis

I've been interested in making my ZSH a little snappier, and so I did some performance analysis on how each segment effects the total time to display a fresh prompt. You can see a summary here on the wiki. It's all rough numbers, but I think it gives a good starting point.
One of the things I find interesting here that I'd like to improve, if feasible, is the amount of time it takes to display the current directory, as it's the 3rd most expensive segment I analysed. Curious what the rest of the community thinks about this, other segments, additional statistics, plan of attack, etc.

This is awesome. Thanks @Maxattax97 . I recently thought about this as well (https://github.com/bhilburn/powerlevel9k/issues/374#issuecomment-438872132). But first some questions about your method:

You measure the whole prompt rendering, right? Do you have configured all segments?
The 100 percent distribution is for all segments configured, so the point of this measurement is to say segment A is more expensive as segment B, no matter how fast segment A renders, right?
Identifying the dir segment as one of the most expensive, did you use a truncation strategy?

I thought about a bit different approach:
We could measure the timings of each segment by its own, by calling the segment function directly (like I did here). So why not triggering this on every build, or as a cron job (travis FTW). These would be not super scientific as well, because Travis builds are executed on VMs, so IOPS would be on the floor. But we would get a prediction if the performance of Segment A got worse or better. To be able to compare the numbers, we would need to calculate a baseline anyway.
Other downsides would be:

We cannot test all segments (the VMs won't have a battery..)
We won't measure other P9K crucial code (e.g. multiline output of segments)
Some segments depend on external things (like the performance of the VCS depends on the size of the repo)
Some segments are especially slow on certain OSes (like on Windows with WSL)

But I think this would be worth it. Having a grip on how the individual segments perform is a plus. And creating a nice graph on a website is another.
// cc @robobenklein and @Erowlin who helped on performance testing the VCS segment
// cc @ijoseph for his awesome graphs in #374 (see here)

Addressing specifically the current directory segment, I actually use my own custom shortening function that I updated.
I don't call it 'truncating' though, I use 'reverse tabbing' (the tab-expanded result is unique to that dir): https://github.com/robobenklein/configs/blob/master/zsh/plunks/rtabfunc.zsh
@Maxattax97 Could you see if that function is either worse or better than the current implementation? If better, I could make a PR for it. It only uses one subshell call for the path exploration step, and would need to be changed from zstyle config to P9K vars.
As for the VCS segment, I gave up on improving the vcs_info zsh autoload any more and just ended up making that asynchronous. (I wanted to make anything involving an external call async.)
As for performance testing in Travis, I would recommend using the zsh profiler builtin. I use it often enough that I have a var ZSHRC_ZPROF that I can use to profile my personal configs.
(( ${+_ZSHRC_ZPROF} )) && zmodload zsh/zprof
# do stuff
zprof | head -30

My requirements to the graphs are:

They should be easy to read (like a simple bar graph, showing performance gets "better" or "worse", whatever that means in real time; maybe a "+2 seconds compared to last datapoint").
Should be triggered for every build/branch. That should be doable in Travis. After generating the charts, it could update the wiki (probably with the help of a GitHub bot.

Shimming some of the functions is a trade-off. It could be worth to know how long our own code runs, but it makes it a bit comparing apples to bananas (if we compare a shimmed segment with a not shimmed one, if that makes any sense "Segment A is 4 times slower than Segment B"). That is why I think we can only compare segment timinig across different runs/branches/ZSH versions.
Not sure if we need to fire up the whole zprof. On one hand, it would be interesting to see what exact function call takes up the most time, on the other hand, all that we need to generate a simple, easy readable graph is a timing of segment as a whole.
@Maxattax97 It would be awesome, if you could go ahead and produce some code!

It might be a little while before I can push code, finals week is coming up here at University, but I'm intrigued by this. Especially since it's a tool I'm using daily.
I've never used Github bots but if we could get at least a rough idea on paper of how to move data/graphs from Travis to the Wiki, I think that'd help in planning out some of the code.


Render figure numbers in DRAFT.rmd

Rendering rmd's using the template.rmd doesnt produce figure numbers (just figure captions).

This is just how it is.


feature(mycollection): add sort and filter in header

The type of this PR is: TYPE

This PR resolves CX-2136
Description
This PR basically gets rid of some old headers and separators, and replace with the newest one. Then it adds the ability for filters to work with a local setup.
Disclaimer: This code is just a patch on top of the filter store. I tried to not refactor anything to simplify. I tried to keep the same "api" for the sortOptions and filterOptions.
Happy to pair to explain further if needed.

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

sort and filter in mycollection (behind flag) - pavlos

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 3d6f06daa9f1d9eb33ec370d27419f2a244868d4

we do have pagination in the end, so i think increasing the page size is the easiest solution right now. removing the pagination seems counter-productive. in order for the local processing to work we need to pull all (or as much as possible) data so that we have values to give to the filters.
So I ended up doing something like this https://github.com/artsy/eigen/pull/5742/files#diff-711500e0a24b1933f2661d17ecef6a7f95dc64efda954f07f2917d9116211ce0R321.
Weird? Yes. Best we can do for now? I guess.

we do have pagination in the end, so i think increasing the page size is the easiest solution right now. removing the pagination seems counter-productive. in order for the local processing to work we need to pull all (or as much as possible) data so that we have values to give to the filters.
So I ended up doing something like this https://github.com/artsy/eigen/pull/5742/files#diff-711500e0a24b1933f2661d17ecef6a7f95dc64efda954f07f2917d9116211ce0R321.
Weird? Yes. Best we can do for now? I guess.

Oof, I thought for sure we checked that, so on the UX side if a user has more than 100 artworks and tries to filter?

another test fixed.

For the 100 artworks, since we dont have people with that many yet, let's not block, and put a ticket on jira and schedule it soon/high prio, so we can take a look before we get there?

as I'm off this whole week, if we need this soon, everyone feel free to rename things etc. otherwise I can work on this next week.


java.net.MalformedURLException: no protocol

Hi,
Was wondering if anybody had come across this issue:

Exception in thread "main" java.util.concurrent.ExecutionException: java.net.MalformedURLException: no protocol:
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at PublicClient.getAccessTokenFromUserCredentials(PublicClient.java:55)
at PublicClient.main(PublicClient.java:27)
Caused by: java.net.MalformedURLException: no protocol:
at java.base/java.net.URL.(URL.java:627)
at java.base/java.net.URL.(URL.java:523)
at java.base/java.net.URL.(URL.java:470)
at com.microsoft.aad.adal4j.HttpHelper.openConnection(HttpHelper.java:119)
at com.microsoft.aad.adal4j.HttpHelper.executeHttpGet(HttpHelper.java:48)
at com.microsoft.aad.adal4j.HttpHelper.executeHttpGet(HttpHelper.java:42)
at com.microsoft.aad.adal4j.WSTrustRequest.execute(WSTrustRequest.java:82)
at com.microsoft.aad.adal4j.AuthenticationContext.processPasswordGrant(AuthenticationContext.java:990)
at com.microsoft.aad.adal4j.AuthenticationContext.access$000(AuthenticationContext.java:69)
at com.microsoft.aad.adal4j.AuthenticationContext$1.call(AuthenticationContext.java:178)
at com.microsoft.aad.adal4j.AuthenticationContext$1.call(AuthenticationContext.java:168)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.base/java.lang.Thread.run(Thread.java:844)

I've change the the CLIENT_ID to match the ApplicationId for the service that I registered, provided my username and password when prompted and got the error above.
Do I need to create a special/service account to use the sample ?
Any thoughts ?
Thanks

Ok so made a little headway..
So I was using the credit on my MDSN account, which meant it was hooking into our corporate directory.  As there doesn't seem to be way to create your own :(
So I signed up a trial account and setup an Azure AD there..  So no longer get a corporate a malformed url..  But getting:

{"error_description":"AADSTS65001: The user or administrator has not consented to use the application with ID 'xxxxxxxxx' named 'Native'. Send an interactive authorization request for this user and resource.\r\nTrace ID: 70d302b6-e22a-4817-b905-6ddd3ded2d00\r\nCorrelation ID: ccfc3572-7a82-435b-a278-672ca8e9764b\r\nTimestamp: 2018-04-09 20:59:30Z","error":"invalid_grant"}

So will now look into how to solve this 2 issues..  Any help or suggestion would be appreciated :)

Hi @whgibbo did you click on "Grant Permissions" in the "Required Permissions" blade in the registered application settings?

Yes I think that was the missing step :)  Thanks..
So now I have it working for the a personal azure account, but wanted to try on MSDN account, which is hooked to the corporate directory.
But this yields the following:

Exception in thread "main" java.util.concurrent.ExecutionException: java.net.MalformedURLException: no protocol:
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at PublicClient.getAccessTokenFromUserCredentials(PublicClient.java:74)
at PublicClient.main(PublicClient.java:39)
Caused by: java.net.MalformedURLException: no protocol:
at java.net.URL.(URL.java:593)
at java.net.URL.(URL.java:490)
at java.net.URL.(URL.java:439)
at com.microsoft.aad.adal4j.HttpHelper.openConnection(HttpHelper.java:119)
at com.microsoft.aad.adal4j.HttpHelper.executeHttpGet(HttpHelper.java:48)
at com.microsoft.aad.adal4j.HttpHelper.executeHttpGet(HttpHelper.java:42)
at com.microsoft.aad.adal4j.WSTrustRequest.execute(WSTrustRequest.java:82)
at com.microsoft.aad.adal4j.AuthenticationContext.processPasswordGrant(AuthenticationContext.java:990)
at com.microsoft.aad.adal4j.AuthenticationContext.access$000(AuthenticationContext.java:69)
at com.microsoft.aad.adal4j.AuthenticationContext$1.call(AuthenticationContext.java:178)
at com.microsoft.aad.adal4j.AuthenticationContext$1.call(AuthenticationContext.java:168)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

So when I step thru the code, I can see with the MSDN account that the userDiscoveryResponse is a Federated account (AuthenticationContext.java - Line 989).  It then appears to obtain the getFederationMetaDataUrl, which is returning an empty string.  Which is causing the MalformedURLException..
So will keep searching.

Hi @whgibbo
The federated account isn't able to perform the authentication through Azure AD. The federated account store the User Credential into the OnPremisse directory.
I hope help you.

This sample has been archived.
The newer one can be found at: https://github.com/Azure-Samples/ms-identity-java-desktop/tree/master/Username-Password-Flow


how to use that?

can i have ur discord plz

the code is quite old and just for reference, it is not intended to be used


reservation: fix user and dir permission on device creation

What this PR does / why we need it:
Fix the user for the pr-helper container and fixes the directory permission on device creation.
This PR contains should be merged after #10186.
See comment about the directory permission and comment for the user.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cc @vasiliy-ul

Hm... Even with root user, I still get:
$ k exec -ti -n kubevirt virt-handler-gdxxh -c pr-helper -- bash
bash-5.1# /usr/bin/qemu-pr-helper -k /var/run/kubevirt/daemons/pr/pr-helper2.sock
^Cqemu-pr-helper: Failed to unlink socket /var/run/kubevirt/daemons/pr/pr-helper2.sock: Permission denied
bash-5.1#
bash-5.1# ls -la /var/run/kubevirt/daemons/pr/
total 0
drwxr-xr-x. 2  107  107 80 Aug  7 08:21 .
drwxr-xr-x. 3 root root 16 Aug  7 07:53 ..
srwxr-xr-x. 1 root root  0 Aug  7 07:53 pr-helper.sock
srwxrwxrwx. 1 root root  0 Aug  7 08:21 pr-helper2.sock

I'm not sure what is happening, but don't get the unlink error message you reported here.

Probably you need to run a VM with reservation first, so the device plugin allocates the resource and chown's the directory to 107:107.

I'm not sure what is happening, but don't get the unlink error message you reported here.

Probably you need to run a VM with reservation first, so the device plugin allocates the resource and chown's the directory to 107:107.

Ok, the issue happen when the directory /var/run/kubevirt/daemons/pr/ is owned by users 107, if it belongs to root then the issue doesn't occurs and the pr-helper successfully unlinks the socket

Correct, that is what I observed as well.

/cherry-pick release-1.0


[Async Broker] Add netty connection related metrics

Added metrics for requests sent, bytes sent/received for netty connections
Added gauge for connect time for netty connections
(Similar to NettyClientMetrics in Sync Broker Scatter-Gather)

Codecov Report

Merging #3268 into master will decrease coverage by 10.42%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             master    #3268       +/-   ##
=============================================
- Coverage     69.95%   59.53%   -10.43%
  Complexity        4        4
=============================================
  Files           972      972
  Lines         44560    44570       +10
  Branches       5975     5975
=============================================
- Hits          31174    26533     -4641
- Misses        11305    16069     +4764
+ Partials       2081     1968      -113

Impacted Files
Coverage Δ
Complexity Δ

...com/linkedin/pinot/common/metrics/BrokerMeter.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...inkedin/pinot/core/transport/DataTableHandler.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...com/linkedin/pinot/common/metrics/BrokerGauge.java
90.9% <100%> (+10.9%)
0 <0> (ø)
:arrow_down:

.../linkedin/pinot/core/transport/ServerChannels.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...lection/iterator/FloatSelectionColumnIterator.java
0% <0%> (-100%)
0% <0%> (ø)

...ion/iterator/LongArraySelectionColumnIterator.java
0% <0%> (-100%)
0% <0%> (ø)

...com/linkedin/pinot/minion/metrics/MinionMeter.java
0% <0%> (-100%)
0% <0%> (ø)

...nion/events/DefaultMinionEventObserverFactory.java
0% <0%> (-100%)
0% <0%> (ø)

...ection/iterator/DoubleSelectionColumnIterator.java
0% <0%> (-100%)
0% <0%> (ø)

...executor/ConvertToRawIndexTaskExecutorFactory.java
0% <0%> (-100%)
0% <0%> (ø)

... and 309 more

Continue to review full report at Codecov.

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


Update Cypress command

Changes

Update Cypress command to match that in cfgov.

Testing

yarn cy should run Cypress.
yarn cy open should open Cypress.

We should prob wait until https://github.com/cfpb/design-system/pull/1916 is merged to verify our node_modules dir behaves the same way.


IndexError: list index out of range

# test on different driver number
driver_coefficients = [0.1, 0.25, 0.5]

for d in driver_coefficients:
    city = City(g_line, call_generator, driver_initializer, total_driver_number_per_time=total_driver_number_per_time,
            speed_info = speed_info, name='real_city_with_speed', driver_coefficient=d, consider_speed = True)

    test_all_for_city(city, "real_city_with_driver_%.2f" % d)

When I run the last part of the code, I get an error. I don't know if it's a code problem or a data problem. This question has been bothering me for a long time. I am looking forward to your answer. Thank you very much. The error message is as follows：
E:\try-delete\TaxiSimulatorOnGraph-master -aa\TaxiSimulatorOnGraph-master\call_generator.py in generate_call(self, city, is_initialize, seed)
72
73     def generate_call(self, city: City, is_initialize=False, seed=None):
---> 74         call_at_t = self.day_orders[city.city_time]
75         # generate call objects to each road of the city.
76         for call in call_at_t:
IndexError: list index out of range

Hi, first thank you for showing interest in my code.
The length of self.day_orders is self.total_time_step which should be always larger than city.city_time.
Please check total_time_step (I used 1 minute as a unit step so 60 min x 24 hours = 1440) is always larger than city.city_time during the simulation.
If you are simulating multiple days, you have to explicitly renew city.city_time to zero.


Upgrade Navie UI

:tada: This PR is included in version 0.75.0 :tada:
The release is available on:

v0.75.0
GitHub release

Your semantic-release bot :package::rocket:


Bump dependecies

Everything is now using the latest upstream release, except libass which is using latest master, and HarfBuzz due to problems with building newer commits. See commit msg for more details.
I briefly went to the beginning of all track+player combos from the gh-pages-branch with a locally built JSO to rule out obvious major regressions.
Regardless of HarfBuzz lacking a bit behind I think overall merging this bump as is should still be useful.
I'm not familiar enough with how pthreads with emscripten is supposed to (not) work to resolve the pthreads/mutex related build problem with newer HarfBuzz-commits.

To build harfbuzz in single thread you can use this commit here

To build harfbuzz in single thread you can use this commit here

Thanks! New version, now HarfBuzz is updated to the latest release as well.


Run ELK reasoner for Travis checks

We use the HermiT reasoner for OBI since it supports a wide range of OWL features, but reasoning with HermiT takes too long for the free continuous integration service offered by Travis CI.
ELK only supports a subset of OWL features, but it's fast and could catch some problems. (Unfortunately it didn't seem to catch the problem with #947 when I tested that locally.)
We should enable ELK reasoning in our Travis checks.

Closed by #959


Location of project.assets.json

The documentation states that project.assets.json file is stored in obj folder of the project. How can I change the path in case I want to separate my code folders from artifacts created by build process?

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

ID: 68d87097-68a1-cdd2-edfc-93fd2366fd0a
Version Independent ID: b7d27caf-5476-2315-f4dc-e413b1be0726
Content: NuGet Package Dependency Resolution
Content Source: docs/consume-packages/Dependency-Resolution.md
Service: unspecified
GitHub Login: @kraigb
Microsoft Alias: kraigb

Agree. These files are polluting my source repo, and I don't want to add another entry to my .gitignore file.


Php + Ruby

Adding two languages at once

https://github.com/scottrogowski/code2flow/blob/ddcae9b2b083d0381f4d8ecad75c766bc3e1759f/code2flow/python.py#L1
as ast is redundant and can be removed.

https://github.com/scottrogowski/code2flow/blob/3150e087ebb3e004a50824aba2c8a9b6716d29bc/code2flow/engine.py#L575
'rb' and 'php' are missing in choices.

https://github.com/scottrogowski/code2flow/blob/3150e087ebb3e004a50824aba2c8a9b6716d29bc/code2flow/engine.py#L575
'rb' and 'php' are missing in choices.

@suetsuguk fixed


Add catches

@LienReyserhove, @peterdesmet, I would like to have your review from at least one of you for this PR which aims to add VMM rattenapp catches I got yesterday from Dan (VMM). By publishing them, it will be easier for @LienReyserhove to write the metadata as big chunks of metadata of MICA - Muskrat occs dataset can be reused.
Catches have a slight different structure and so I preferred to first make some join operations in R.
I reused samplingProtocol  value rat trap for the catches as this is the value in use in MICA - Muskrat occs.

I had a glance, looks good! I have a two remarks:

The field language is missing, should be set en (see https://github.com/riparias/vmm-rattenapp-occurrences/pull/8/commits/5e99c78a5b06779ac8856dced0ef9d06be0fe04f)
establishmentMeans =  introduced for 1 record only (Sporen Waarnemingen Naam=Koe gered uit dyle). A cow is not introduced but native. Many other species could receive the status of introduced, such as Ondatra zibethicus,  Impatiens glandulifera, Fallopia japonica, etc. Not sure why this particular record is introduced`

@peterdesmet: I remember you set it introduced to the cow record 😄 the idea behind was to flag it as a bred animal (for plants we would say that it is cultivated). But as @LienReyserhove noticed I think we misused the field.
My idea: remove field establishmentMeans field for all records and remove the cow record as well as it is a captive organism. For instance, iNaturalist doesn't push such observations to GBIF.
@peterdesmet, @LienReyserhove: do you agree?

Sounds good to me.

ok for me!

Thanks. I will apply this change.