[FEATURE] Optimization, icons and Font Awesome

I'm not sure how feasible this is to implement, but having to retrieve icons from font awesome adds unnecessary overhead when all we needs is an svg (that we can get from many sources).
More info and demonstration:
Short Youtube Video

As you can see, from the video, getting rid of font awesome is fairly easy, it makes the site faster, and also allows the user to use Iconify which means they will have many more icon libraries to choose from.
The way he does it in the video is an option (svg code), but we can also just download the svg file and just link to it locally.

in this example I'm trying to add Artstation to social.yml but since Font Awesome doesn't include its icon in the free pack, I have no option.
But using the method in that video, I can use iconify and get many icons from many libraries, and without having to change implementation since I would get the actual svg.

https://github.com/iconify

I'm not sure how feasible this is to implement, but having to retrieve icons from font awesome adds unnecessary overhead when all we needs is an svg (that we can get from many sources).

I'll keep to use both Font-Awesome and Simple-Icon for font resources which has lot of icon support. I just wanna avoid lot of request related to the icon implementation (cause of the limitation)
Reducing unused resources are can be done using PurgeCSS. You can use PurgeCSS with post-cli or simplify using PurgeCSS as pre-commit


Main menu focus gets confused on drop-down and menu will stay down

Rancher versions: 2.0 master 5/14
Steps to Reproduce:

Click on one of the menu options that's a drop-down.
Hover over different drop-down menus

Results:  The blue focus box is switching around and at times I can get menu to stay down.

Version - 2.0 master 5/16
Blue focus is still switching around even when I don't click

Version - 2.0 master 6/25
Verified fixed


chore: added url and http method in error message

In large projects it is normal to have many different requests, adding the url and http method to the error message should help identify unmocked requests

Good implementation


train=yes suggestion at public transport platforms is not correct

For almost one year now the OSM database is continuously filled with train=yes tags, where it is completely wrong. All those edits are executed by the iD editor.
As example see this way:
https://preview.ideditor.com/master/#background=none&disable_features=boundaries&id=w137701947
This is a platform for trams, no train is going there.
Instead of adding train=yes automatically it must add one kind of bus/tram/subway/train/...=yes. Adding always train=yes is wrong in many cases.
I suggest to completely delete train=yes from suggestions in iD.
Also see this (german) discussion:
https://forum.openstreetmap.org/viewtopic.php?id=68239

@mapz-sdu Thanks for your concern. If you've been seeing this issue for a year then I wish you'd spoken up sooner.
Also, while we the may be cultural barrier between us, writing "WRONG" like that is rude. Please try to keep things professional in the future.

Sorry, a rude expression was not intended!
I just found this error 2 weeks ago and corrected some of the wrong tags. The first wrong tagging occured about one year ago.
Thanks for looking after this issue.

Sorry, a rude expression was not intended!

@mapz-sdu I was hoping as much! Thanks for reporting and welcome to the repo 👋


UTXO transaction (sent/receive) are missing in the listaccounthistory at Jellyfish addresses (Light-Wallet)

Hello Team,
What happened:
I was about to export my account history and see if all my data is there. The last fix from @bvbfan worked for me.... with the addresses I get all the data even the December 2020.
Unfortunately now when I want to retrieve the data of my light wallet address the complete history of my UTXO transactions are missing. Important would be us sent and receive because these are tax relevant for tracking.
They are also not available as DfTxType... which means that if I use Jellyfish to pull the history of the "old" address (of the desktop wallet) via the RPC CLient, then I do not have these transactions.
Will that come back in the history or do you have to go through all the transactions of the address?
What you expected to happen:
That I have the send & receive transaction in the listaccounthistory again.
How to reproduce it (as minimally and precisely as possible):
Look on the history with listaccounthistory LIGHT_WALLET_ADDRESS
Information is not available.
What are your environment parameters:
Has nothing to do with OS or CPU / disk typerelevant). -->
Anything else we need to know?:
Thanks for your work :-)

Related to https://github.com/DeFiCh/scan/issues/669 and https://github.com/DeFiCh/whale/pull/367
/area transactions
/kind bug


Update abstract for paper_main.415

https://acl2020.rocket.chat/channel/presenter-helpdesk?msg=ojJGg6TF4kZB9DcDA

Hi, same issue as Paul -- for my paper here on the virtual acl website https://virtual.acl2020.org/paper_main.415.html the abstract was updated quite a bit for camera-ready (camera-ready abstract here: https://www.aclweb.org/anthology/2020.acl-main.415/), and also now includes the link to the data and site. It would be awesome if it were possible to update. Thanks!

Close with https://github.com/acl-org/acl-2020-virtual-conference-sitedata/pull/201


Not working with pageloading

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
put the code between

Expected behavior
Vue tour will not show
Desktop (please complete the following information):

This issue doesn't follow the guidelines.
Closing it. Feel free to reopen it if needed with more information.


Use Cyclone & Python-Twisted instead of Tornado

Use Cyclone instead of TornadoWeb, for the front end in the Python prototype.   Cyclone is built over Python-Twisted.
The benefits would be:

The convenience of the twistd driver program.
Improved asynchronicity.

And, by the way, current version of cyclone running with twisted 10x or 11x is actually faster than Tornado.

Thanks, all the more reason to consider Cyclone+Twisted then.


Implement hidden nodes blind

NOT READY FOR MERGE

Please merge https://github.com/KnodesCommunity/typedoc-plugins/pull/88 first
Some of this PR is actually from parent patch 88, and will disappear when it is merged

This is a blind attempt to implement HIDDEN nodes.  It is highly suspect because the author could not build or test the result, and is new to this codebase.
A HIDDEN node is a node which will only render in the page tree if it's currently being viewed.  (This behavior is known to currently be incorrect, and will be repaired before merge once buildable.)
The purpose of a HIDDEN node is to allow a category page to include hundreds of pages underneath, and not flood the index on the right.  HIDDEN nodes must be found from a listing in another page, or through search.
My personal use case is for the documentation for a state machine library.  I want to include more than 200 example state machines, each on their own page, which is prohibitive without a feature like this.

Please rebase your branch. You should be good to go now

@GerkinDev - I might be being dense, but, the repo doesn't show a push in the last couple weeks; maybe something didn't get pushed?  Or maybe I'm not getting it

You're supposed to base features on the develop branch, not main. Main is for released code only.

oh you use git flow, ok, sorry

Sorry, no, the situation is unchanged, I believe.
Because I am noticably bad at things like rebasing and submodules, I established a new clean setup.
In this order, I:

Created a new directory, and worked there
Cloned your repo, instead of my own
Updated submodules
Initialized npm workspaces
Switched to your repo's develop branch, not my PR
Ran npm install
Ran npm run projects:build

The error is the same as previously, I believe.

john@DESKTOP-26H4050 MINGW64 /e/projects
$ mkdir tmp-host-copy

john@DESKTOP-26H4050 MINGW64 /e/projects
$ cd tmp-host-copy/

john@DESKTOP-26H4050 MINGW64 /e/projects/tmp-host-copy
$ git clone https://github.com/KnodesCommunity/typedoc-plugins.git
Cloning into 'typedoc-plugins'...
remote: Enumerating objects: 2026, done.
remote: Counting objects: 100% (470/470), done.
remote: Compressing objects: 100% (170/170), done.
Receiving objects: 100% (2026/2026), 1.22 MiB | 3.40 MiB/s, done.ed 1556

Resolving deltas: 100% (1316/1316), done.

john@DESKTOP-26H4050 MINGW64 /e/projects/tmp-host-copy
$ cd typedoc-plugins/

john@DESKTOP-26H4050 MINGW64 /e/projects/tmp-host-copy/typedoc-plugins (main)
$ git submodule update --init --recursive
Submodule 'typedoc' (https://github.com/TypeStrong/typedoc.git) registered for path 'typedoc'
Cloning into 'E:/projects/tmp-host-copy/typedoc-plugins/typedoc'...
Submodule path 'typedoc': checked out 'abed9a64d674c6c3b20284847c024abd5334547b'

john@DESKTOP-26H4050 MINGW64 /e/projects/tmp-host-copy/typedoc-plugins (main)
$ npm i --workspaces

><EMAIL_ADDRESS>prepare
> npm run prepare:husky

><EMAIL_ADDRESS>prepare:husky
> [ -d ./node_modules/husky ] && husky install || true

added 708 packages, and audited 714 packages in 40s

found 0 vulnerabilities

john@DESKTOP-26H4050 MINGW64 /e/projects/tmp-host-copy/typedoc-plugins (main)
$ git checkout develop
Switched to a new branch 'develop'
M       typedoc
Branch 'develop' set up to track remote branch 'develop' from 'origin'.

john@DESKTOP-26H4050 MINGW64 /e/projects/tmp-host-copy/typedoc-plugins (develop)
$ npm install
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. concurrently provides its own type definitions, so you do not need this installed.
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>Moved to 'npm install @sideway/address'
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>Switch to 'npm install joi'

><EMAIL_ADDRESS>prepare
> npm run prepare:husky

><EMAIL_ADDRESS>prepare:husky
> [ -d ./node_modules/husky ] && husky install || true

husky - Git hooks installed

added 108 packages, removed 51 packages, changed 182 packages, and audited 771 packages in 32s

found 0 vulnerabilities

john@DESKTOP-26H4050 MINGW64 /e/projects/tmp-host-copy/typedoc-plugins (develop)
$ npm run projects:build

><EMAIL_ADDRESS>projects:build
> npm run projects:patch -- apply && node ./tools/s-projects 'npm run build -- --pretty'

><EMAIL_ADDRESS>projects:patch
> node ./tools/typedoc-patcher --no-stash "apply"

Applying patches from packages/plugin-pages/src/theme-plugins/search/default-pages-javascript-index-plugin.GENERATED.ts.patch
node:internal/process/promises:246
          triggerUncaughtException(err, true /* fromPromise */);
          ^

AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

  assert( match && match[1] )

    at E:\projects\tmp-host-copy\typedoc-plugins\tools\typedoc-patcher.js:28:2
    at async E:\projects\tmp-host-copy\typedoc-plugins\tools\typedoc-patcher.js:123:100
    at async Promise.all (index 0)
    at async E:\projects\tmp-host-copy\typedoc-plugins\tools\typedoc-patcher.js:123:31 {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: null,
  expected: true,
  operator: '=='
}

Node.js v17.2.0

You've checked out typedoc before checking out the develop branch. So I'm not sure the typedoc submodule is at the expected commit to apply the patch.

Wait, the ... the git submodules are different according to branches?

So, I totally understand this "patch" thing is a hell.

Honestly it's mostly the submodules that have been causing me trouble

no, the same build failure happens if i check out develop first

You've checked out typedoc before checking out the develop branch. So I'm not sure the typedoc submodule is at the expected commit to apply the patch.

Wait, the ... the git submodules are different according to branches?

Yes, it targets the latest typedoc stable release (currently 0.22.17) in order to avoid possibly regressing release as soon as typedoc updates one of the patched files.
Ok this is strange. I'll check on my windows tonight

ok, that fix appears to work

Hi there;
I'm finally looking for a way to implement this feature.


PoS Deprecate GlobalActiveStakeAmountNanos

Current dependencies on/for this PR:

feature/proof-of-stake

PR #579

PR #583

PR #584   👈

This comment was auto-generated by Graphite.


Update stable version in repo from 1.0.11 to 1.0.12

Think about update stable version to 1.0.12
Version: stable=1.0.11 (39 days old) => latest=1.0.12 (30 days old)
Installs: stable=223 (61.43%), latest=58 (15.98%), total=363
Click to edit

This issue seems to be outdated
This issue suggests to update the stable version of this adapter to 1.0.12 but in meantime an updateto version 1.0.13 is sugested.
So this issue will be closed and repleaced by an updates one.


Snyk upgrade 5a7daa404429185c588f98489f4e1be0

Changes
Please provide a brief description of the changes here.
Merge Requirements
For new features contributions please make sure you have completed the following
essential items:

[x] CHANGELOG.md updated to document new feature additions
[x] Appropriate documentation updates in the docs
[x] Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

@JoKacar would you be able to sign the CLA?


feat: add support to get logged user as json

This PR should be turned down.
It would be an information exposure vulnerability.
Hi, @magikstm.
The same route exposes the user data as text/html. I agree that parsing json is easier, but if someone have a stolen token it is possible to extract the the data using jwt.io, jwtlib or parsing html, even if it is a XSS vulnerability. I've checked and there is no jsonp support, so it is not possible to inject script tags to run malicious code.

I've implemented it because it's really useful to get verified logged user data without need to implement it on my APIs and feel some base basic user data on js web app.

@perenecabuto could you please specify the route that exposes it?
Default template does show it after logon:
https://github.com/tarent/loginsrv/blob/master/login/login_form.go#L56
But, it can be hidden with a template change using -template. Is it this one?
I'll review the PR more thoroughly.

@perenecabuto would PR #96 related to issue #94 help?
Could PR #96 be used in your API to get logged in user?

@perenecabuto Thank you for the feature!
I overworked it a little bit and merged into master.

I changed it to return the JSON if the Accept header is JSON. The Content-Type is not relevant for that.
I have added some doku ..


After verifying an unverified auth0 user it never picks up the roles without signing out / signing in

We can probably do something smart, like if we see a verified email, but no roles, to tell the user to sign out / sign in.

For now, providing minor relief by adding to the warning message.


Homepage doesn't load upon init

When running the app you are led to the landing location page but it just displays 'loading' once you toggle between another page on the scaffold the amplify sync is started and then populated. Sync needs to start right away


Should consider using edge masks on the data during PSF correction

I know its removing data but it could really help clear up some small, irritating artifacts.

I think that it would be most effective to apply this after the finished PSF corrected images have been assembled, and before they are saved. That way the actual saved images will have slices of data missing, but when emosaic adds them together there won't be random hot spots where the dropping off of expmaps causes it to shoot up.


Double-click to "Undo to Here"

What is the feature you'd like to have?
In the History widget, I want to double-click to "Undo to Here" instead of using right-click, which currently does not work.
Is your feature request related to a problem?

Are any alternative solutions acceptable?
Not really, but it also might be cool if hitting "Enter" would also work? Could enable me to use Up + Enter (or, if #5742 exists, Down + Enter!) in order to "step" through undo history, which might be neat?

Added in 4.2.5964-dev


Question: Fill background up to the line

This is more like a question but I am curious how to achieve the following :
Suppose we have the following

I would like the colored areas limited by the line and would like to keep the area above the line as white. Is this doable?

Good question!
The background shapes do not have to be rectangles - the c.shape primitive will fill any polygon you give it - so the way to do this is to generate the points of this background so that it is flat at the bottom, but aligned with the data points at the top.
I added this as a demo: https://compostjs.github.io/compost/demos.html#xchg-under


v3 Update question

As you will use Sponsorware model will this framework available for usage if I have public repo if I am not a sponsor??
Also, I want to know will this package be private for v3?
If you can mention what we will get in v3, it will be really helpful so we can decide if we can use it for open-source projects.
Awaiting your response.

Will be open source like this one but (maybe) I'll release some not-common components (let's say an emoji picker) for sponsors until I reach some amount
So yes The most important components will be open source that's for sure

Will be open source like this one but (maybe) I'll release some not-common components (let's say an emoji picker) for sponsors until I reach some amount
So yes The most important components will be open source that's for sure

@alfonsobries Hi. I'm looking for a component library and yours looks quite good. We just started using Tailwindcss and would love to be able to use that with a component library.  I read what you had written for upcoming changes, but that did not mention when you were planning to release those changes. Do you have a timeline for v3?

@theo333 not yet but I should have a roadmap in the following weeks, almost finish with the POC of the next version and according to that I'll be able to have a timeline
Follow me on Twitter for updates(@alfonsobries)

Will move all discussions related to vue 3 to here https://github.com/alfonsobries/vue-tailwind/issues/214


Cache performance is low when num items is high

Hi, I am using Cachelib to store all items that are requested but missing from underlying layer. So the values of these items are empty. As a result, for 40GB of data, we will end up with around 2e7 items in the cache, which corresponds to the bucket power of 26. I measured the cache hit and cache miss latency. Compared with another cache using cachelib which stores regular items, this cache performance really suffers.

Cache type
Cache hit latency
Cache miss latency
items in cache
cache hit ratio

Cache storing regular items
2us
1us
2^22
7%

Cache storing empty values
5us
4us
2^25
44%

BTW, I set the cache size large enough so no evictions happens.
The increased cache latency actually diluted the value of using cache. Can you give some guidance on this?

Huh can you share your full cache config? (Dump the serialized version of CacheAllocatorConfig).
Other questions:

Are you sending similar load to both caches? (cache operations per sec are similar?)
Does 7% mean 93% are misses in cachelib, or these are misses due to empty values?
Are all empty values of the same size? What about regular items (what's its size distribution?)

Btw for negative cache, CacheLib has this thing called compact-cache that is much more space-efficient than regular cache.
https://cachelib.org/docs/Cache_Library_User_Guides/compact_cache

(1) About the cache config. I only set the cache size and config.setAccessConfig(numCacheItems). All others are default.
(2) I run the benchmark making the same query from the same data source. The benchmark will send workload as fast as possible.
(3) My bad about the hit ratio. Actually, 7% is for the cache storing regular items. The hit ratio for the cache storing empty values is 44%.
(4) All empty values are empty strings "". Key sizes are always identical. For regular items, the average value size is 100B, the key size is 16B.

For the reference, with another query, the empty value cache can have very good performance:

Cache type
Cache hit latency
Cache miss latency
items in cache
cache hit ratio

Cache storing empty values(another query)
1us
1us
2^20
85%

Btw for negative cache, CacheLib has this thing called compact-cache that is much more space-efficient than regular cache.
https://cachelib.org/docs/Cache_Library_User_Guides/compact_cache

Let me try this.

I am trying to use the ccache, but got compilation error:

Here is a snippet of my code:
struct MyKey {
  uint32_t key;
  MyKey(uint32_t from) {
    key = from;
  }

  bool operator==(const MyKey& other) const {
    return key == other.key;
  }

  bool isEmpty() const {
    return key == 0;
  }
};

....
bool getKey() {
    MyKey mykey = 12;
    auto res = cCache_->get(mykey);                           <----- Here is the line where the compiler error is
    return res == facebook::cachelib::CCacheReturn::FOUND;
}

Any hints on this?

The compilation error only occurs when I declare the ccache as NoValue type like CCacheCreator<CCacheAllocator, MyKey>::type. Once I specify the value type, it can compile.

@wenhaocs: huh the compiler errors look like u hit some sort of internal bug in the compiler? (On our end, we have internal use-cases specifying NoType so it should work). What happens if you duplicate the "NoValue" definition and pass in your own "no value" type?

Regarding the slower than expected lookup latency, it may be because all the keys are in the same allocation class. So each lookup (that promotes an item) will hit the same LRU lock. To validate this theory, in your test, can you try sharding your key space into 10 different cache pools?
Something like:
auto poolId = static_cast<PoolId>(hash_func(key) % 10);
auto item = cache->allocate(poolId, ...);
// ... insert into cache.

Hi @therealgymmy Here are a few findings and questions:

The floating point exception is caused by char[0] (let alone the Pedantic Warning from compiler). I copied the NoValue definition into my code. After I changed it into char[1]. The compilation succeeds. My compilers are:
gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
g++ (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0

If I copy the NoValue definition into my code, how can I fake CacheLib to let me pass nullptr value when set? The CacheLib code determines this internally: constexpr static bool kHasValues =    !std::is_same<typename ValueDescriptor::Value, NoValue>::value;

After I change to use CCache to store negative keys. The performance is much better. The cache hit and miss latency are all sub-microseconds. But the overhead is still high if I choose to shard my key space into 10 different cache pools, around 4us for cache hit, 3us for cache miss. A little bit improvement from the original case.

Seems GlobalCacheStats does not contain the stats of CCache.

I know CCache is to be deprecated. Any guidance on my current situation?

The floating point exception is caused by char[0] (let alone the Pedantic Warning from compiler).

Huh. I guess technically char[0] is illegal. But I expected compiler to handle it (giving us a zero-sided structure). We don't see this internally. But we switched to clang a while back.
Code: https://github.com/facebook/CacheLib/blob/main/cachelib/compact_cache/CCacheDescriptor.h#L177
Found this stackoverflow post about zero-sized struct: https://stackoverflow.com/a/47352963
@wenhaocs: for now, you can work around this by using a value structure of 1 byte. U can just choose not to populate it.

But the overhead is still high if I choose to shard my key space into 10 different cache pools, around 4us for cache hit, 3us for cache miss.

This is a bit odd. Do you have any instrumentation on your end that can tell u which code path is taking CPU cycles? Also maybe use perftools to see if we're incurring more cpu cache misses?
My original suggestion for sharding the pool is assuming we have contention on LRU lock. But perhaps it's elsewhere.
What if you size your hashtable bigger even for the workload with fewer items? E.g. Change both workloads to use a very large hashtable e.g. set bucket power to 2^30. (Keep the pools sharded too to rule out possibility of LRU contention). If both workloads are now at similar latency, it's probably due to cpu cache misses from a larger hash table (buckets are more spread out).
You can manually do this: https://github.com/facebook/CacheLib/blob/main/cachelib/allocator/ChainedHashTable.h#L234
config.setAccessConfig({30 /* bucketPower */, 20 /* lockPower */});

Seems GlobalCacheStats does not contain the stats of CCache.

Yeah that's right. CCache is intended to be used orthogonal to regular cachelib. You can get the stats directly from each CCache instance.
https://github.com/facebook/CacheLib/blob/main/cachelib/compact_cache/CCache.h#L384

I know CCache is to be deprecated. Any guidance on my current situation?

It's in "maintenance mode" indefinitely. We have no plan to remove it but also no plan on adding additional features. We still have a few odd usage of this here and there internally.

Hi @therealgymmy Thanks for the reply. Actually, I do not see a big difference when increasing the bucket size (of course if the bucket size is not enough, the performance downgrades a lot). I do not have perf tools on hands, may need help from other teams. Here are some other findings I have:
(1) The put latency of ccache is high compared with regular cache. In one experiment with fixed QPS benchmark, the avg cache put latency for ccache is 88us, and 51ms for regular cache for negative items. I know I can bypass it by putting to cache async, but it may decrease the cache hit ratio when the QPS is extremely high, and may not yield good results as expected. Of course, when the QPS is low, it works perfectly. Is this higher put latency in ccache expected?
(2) Using the regular cache for negative items works badly when I run benchmark as fast as possible, even worse than not using cache. However, if I limit the QPS, the performance is good. For example, for the query that I mentioned early having bad performance, here is a summary of the p95 latency:

w/o cache
regular cache with 10 pools
regular cache with 1 pool
ccache

3575ms
1855ms
1811ms
1699ms

That means if I limit the QPS, not running as fast as possible, the regular cache for negative items is not far from ccache. If running stress test, there is a big difference between regular cache and ccache for negative items.
Do you have any suggestions on the choices of cache for negative items, where storing keys is enough. If using regular cache, what's the guidance of creating pools?

(1) The put latency of ccache is high compared with regular cache

Yeah that's right.  You can tune this by changing the bucket size, but it is expected to be more expensive than evicting a regular item.
Compact cache's read performance is good only for small items because it performs copy-on-read. Object size should typically be less than a cacheline (128bytes)

(2) Using the regular cache for negative items works badly when I run benchmark as fast as possible, even worse than not using cache.

I do not really understand why this is. Let's debug this some more.
In cachebench tests, when I run a miss-only workload, I typically see higher throughput than workloads with high hit rate. Cachebench runs its operations synchronously so higher throughput typically also mean lower latency.
You can try it out by running cachebench with: https://github.com/facebook/CacheLib/blob/main/cachelib/cachebench/test_configs/throughput/miss-workload/ram_cache_get_throughput_all_misses.json

In general, we recommend compact cache for negative caching because it is much more space efficient. This is assuming that your negative cache will need to cache a much larger working set than a non-negative cache. (E.g. there're more "do-not-exists" in your system than "exists") Does this pattern sound like your usage?

Exactly, in our benchmark, "not-exists" can be 8x more than "exists".

@wenhaocs: Did you resolve this issue?

Yes. It can be closed for now. I will dig this further in the future.


More alternates for Layout Elements

The only usable shape alternate for e.g. Projection Element is Elements.Projection.Detail which you can use to override all instances of the element. Now you can combine this with URL alternates, but you're out of luck if you want to override the shape template of multiple elements on the same page.
Apart from introducing some explicit technical name property for all elements (like it is for widgets) we could generate alternates bases on the HTML ID and class names of an element

@sfmskywalker @DanielStolt ?

Although technically it would be fine to add an alternate based on HtmlId, I am not sure that value should be used out of the box for generating alternates because in my opinion that value represents a client-side value, semantically speaking. Adding a technical name property and basing alternates on that feels like a better choice.

I don't see a big issue with have an alternate based on the html id. though it's kind of ugly. I'd rather have a technical name in this case, but the drawback is that we need a new property. Optional value? Could it be used in the UI too?
At the same time what if you want to share the layout between projection elements, would it make sense?
But we definitely want to customize the projections.

What about a display type property?
c.f. https://github.com/OrchardCMS/Orchard/issues/5730

#5801 is kind of related to this in that the field elements need alternates for their discriminators

Display Type is a good idea. Another alternate I think we should add is wether or not the element is sealed. That way we can vary the shape templates for sealed elements.

Sealed elements are elements that come from a layout template. when you create a layout template and add a bunch of columns and content to those columns, those columns become sealed, which means child layouts can no longer add elements to them. To deal with that, you can add placeholder container elements (e.g. Canvas). However, that will render an additional <div> element which you may not want. But if the Canvas element shape has an alternated called something like Elements_Canvas__Sealed, I could override that with a Razor view that doesn't render the surrounding <div> element.


[BUGFIX] _unregister() is an Ember.View method that reclaims memory.

Overriding it causes leaks.
https://github.com/emberjs/ember.js/blob/7c008239182cce203f024768d3df999c2850f66f/packages/ember-views/lib/views/view.js#L1444

:facepalm:

It looks like Travis if failing because now "current release" is Ember 2.0, which lacks former public APIs this library needs. I'm going to go ahead and merge this for now.


feat: Command to cancel a running job from the CLI

Docs: https://github.com/meltano/meltano/pull/7668

@edgarrmondragon what's your plan for docs changes related to this PR?
@pnadolny13 would you do some user acceptance testing on our Squared project for this PR?

@tayloramurphy I opened https://github.com/meltano/meltano/pull/7668 (doesn't make a lot of sense to add them here since they're only deployed from the main branch)

@tayloramurphy @edgarrmondragon I tested this and it worked as expected for me.
Some feedback as a user though:

I got a bit tripped up on the difference between jobs vs schedules vs executions again. I dont necessarily have a recommendation but the workflow of: run schedule, list schedule execution history, print execution logs, stop job using execution id. I think jobs and schedules are the same in this context so it feels like schedule = job and job = execution.
With my previous comment in mind, we might want to consider changing these job command to refer to "job executions" because we're interacting with execution, not jobs themselves. Maybe the help text Interact with Meltano Cloud jobs. to Interact with Meltano Cloud job executions..
The stop help text looks like its wrong. It says  List Meltano Cloud projects. and Commands:  stop  List Meltano Cloud projects.
The history table shows it as FAILED after I stop it. Do we want another result like CANCELED so its clear what happened? Or even clearer CANCELED_BY_USER if we later need other CANCELED_BY_X options. I think this might actually be on the API side though.

The history table shows it as FAILED after I stop it. Do we want another result like CANCELED so its clear what happened? Or even clearer CANCELED_BY_USER if we later need other CANCELED_BY_X options. I think this might actually be on the API side though.

I see in the tests a STOPPED status. We definitely want to make it clear to the user the distinction of a failure vs manual stoppage.

With my previous comment in mind, we might want to consider changing these job command to refer to "job executions" because we're interacting with execution, not jobs themselves. Maybe the help text Interact with Meltano Cloud jobs. to Interact with Meltano Cloud job executions..

+1 to this

We definitely want to make it clear to the user the distinction of a failure vs manual stoppage.

@tayloramurphy ok maybe thats a bug then? 🤔  My test run history looks like this

Does that need to be done before this can be merged or can we accept failed status for the time being?

@edgarrmondragon @magreenbaum we can accept a failed status so we don't block on this PR. @edgarrmondragon can you update your docs PR to reference the issue to update the reasons so we can track and users can see we're planning to update it?

Does that need to be done before this can be merged or can we accept failed status for the time being?

@edgarrmondragon @magreenbaum we can accept a failed status so we don't block on this PR. @edgarrmondragon can you update your docs PR to reference the issue to update the reasons so we can track and users can see we're planning to update it?

@tayloramurphy Done: d1ad7a002be63e844220dcb672bad082e2a2e480. Let me know if that looks ok.

@WillDaSilva Dependency review is failing but I'm not sure if it expects us to just downgrade those deps:

@edgarrmondragon Upgrade requests to version 2.31.0, and the dependency review check should pass. It's failing because of:

Which has been fixed in version 2.31.0: https://requests.readthedocs.io/en/latest/community/updates/

Fossa is timing out 🤔

@tayloramurphy I think Pat's done the UAT, so I'm gonna go ahead and merge tomorrow if there are no objections


✨ Define API for custom cleaning

Summary
This PR proposes an API for custom cleaning.
Related issue(s)
This is the start of addressing #1976 .

@MikeSpreitzer (@pdettori @eaepstein ) I don't understand how we "start addressing" #1976 before we have agreement on what are the requirements.
As we agreed in the call, all items that are marked as "major feature"  should follow the procedure of:

Design document that clearly state the requirements
Review and agreement on the requirements
High level design (proposal) through goggle doc (or detailed slides)

Review of the design through comments

Coding PR

You started directly with (5).  We didn't even have any discussion what's so ever  other than couple of general comment in #1976   on the actual requirements and what is the problem we are trying to solve here.

I wrote one main comment about leveraging the same mechanism not only for cleaning but for add/update/remove.
other than that the api looks good to me.

The force-push to c5aa4680b responds to the recent requirements and naming discussion.

I think this proposal reflects well what we agreed on in terms of simplicity, addressing only the use case at hand as a starting point and supporting future evolution to cover more complex use cases.


Crash when using mirrord in IntelliJ GoLand + NodeJS

Bug Description
When using the GoLand to run a NodeJS configuration, the progressIndicator seems to be null causing a null exception.
Caused by PR #1378
Steps to Reproduce
When using the IntelliJ new UI, the progressIndicator seems to be null causing a null exception.
Backtrace
No response
Relevant Logs
No response
Your operating system and version
n/a
Local process
n/a
Local process version
No response
Additional Info
No response

Also it seems that the UI is stuck while mirrord is loading, I assume because the progress is now not created from invokeLater

I tried fixing it using ProgressManager.progress() - this fixed the error but UI was still stuck so preferred to revert.

I think the buffering can be shifted to Task.Backgroundable task, which is separate from the UI and will prevent from freezing


Add production users list

As discussed in [1] I would like to add a list of production users of
Alertmanager to this repo. On the one hand this would show the level of trust people
put into the project. On the other hand it gives us the ability to reach
out to this user group for advice and experience.
Please suggest other possible metrics that you would be interested in, or mention those that you would rather like to have removed.
Once we have settled on a set of metrics I will reach out to those companies that we are aware of.
[1]
https://github.com/coreos/etcd/blob/master/Documentation/production-users.md
//CC @brancz

As a lot of these questions are about the Prometheus setup I wonder whether we should just have a document in the Prometheus repo regarding this. Or maybe even on prometheus.io, as it might be easier to explain the usage across multiple tools?
If you want to keep it repository focused I'd suggest to scope the questions more towards the actual Alertmanager usage.

There is already a user list on the front page of prometheus.io, and for more detailed reports we have the use case blogs.

Agreed, but I do miss a document that is somewhere in-between those two. Users with a few main bullet points on how their setup looks like, I'm sure we can extract a lot of data from the detailed reports we have in form of blog posts.

I agree with @brian-brazil that we already have a lot of information around production use cases. What I am missing is a simple table or list of use cases where it is easy to compare different setups with a basic set of metrics.
@brancz I am happy to make this more open and move it to a different place. But I would like to keep a basic set of information around Alertmanager in it.

I think it would be great to have a quick concise overview of users' setups.

The users list on the website is merely a very incomplete collection of logos. Anyone seriously about evaluating using Prometheus components will not gain anything from a cloud of images.
In other news, our website should fan in docs from our component repos. I think that is part of the effort @Gouthamve and @grobie are currently doing towards versioned documentation.
The repository itself is the right place for this and a textual overview of users with some background info on deployment size etc. is the right thing as well.

Adding a production users list here which is then displayed on the Prometheus.io website sounds good to me.
@fabxc What do you think of my proposed facts that we would collect from each user? @brancz You said you had some that you would like to add?!
Instead of collection these metrics for each Prometheus project separately, we could have them in one place. Would reduce the amount of repetition. E.g. 'How many nodes are you monitoring?', which is probably interesting for both the Alertmanager production users list, as well as the Prometheus production users list.

I think we'll boil down to Prometheus and Alertmanager for this. Exporters do not need those user summaries.
I think with focus on the right questions, the data we want to gather will have little overlap. E.g. nodes monitored does have little impact on Alertmanager. The performance benchmark is rather sent alerts – even that is probably secondary to across how many teams and channels notifications are organized.
Anyway, the little duplication we'll have doesn't hurt IMO – especially as Prometheus and AM are and always will be relatively independent tools.

What @fabxc mentioned is exactly the data I was thinking of. In general agreed with all what @fabxc said.

If we're going to collect this sort of information, I'd suggest having one central list that covers all the components.
The wiki is probably the best place, as that's the lowest friction.

Nobody watches the wiki – like ever. It's a completely distinct work flow from our usual repositories. I don't know when the last changes to anything in the wiki were made or what they would've been.

People actively watching changes to these docs is not required, people being able to find them and change them easily is what's needed here. It works for the port list, and I think it could also work well here.

All docs should go into the repo – developer as well as user ones.

This is neither user nor developer docs, it's a list of users.

This is neither user nor developer docs, it's a list of users.

I disagree. This is very much user documentation, mainly for people who are evaluating Prometheus and are looking into whether it fits their need and/or whether it works out at other organizations and at which scale. All of that in a simple concise list on the website seems like the best place to me.
I'm not a particularly huge fan of the port list or see it's importance and I am not able to follow the changes that happen to it reliably.

All of that in a simple concise list on the website seems like the best place to me.

The issue with something like this being directly on the website is that we'll get much fewer contributions, as the user has to go to the effort of creating a PR. You'll note how rarely we get new logos on the frontpage.

I'm not a particularly huge fan of the port list or see it's importance and I am not able to follow the changes that happen to it reliably.

It comes from a time when the official components had clashing port numbers, and inadvertently grew from there to a comprehensive list of exporters and integrations. It's useful in practice, and if it ain't broke don't fix it.

Closing here due to missing consensus.


problem with dynamiczone JSON type

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.

Here is the diff that solved my problem:
diff --git a/node_modules/gatsby-source-strapi/lib/index.js b/node_modules/gatsby-source-strapi/lib/index.js
index 30f2f2f..354affc 100644
--- a/node_modules/gatsby-source-strapi/lib/index.js
+++ b/node_modules/gatsby-source-strapi/lib/index.js
@@ -58,14 +58,14 @@ const addDynamicZoneFieldsToSchema = ({
   } = actions; // Search for dynamic zones in all items

   const dynamicZoneFields = {};
-  items.forEach(item => {
+  /*items.forEach(item => {
     _lodash.default.forEach(item, (value, field) => {
       if (_normalize.default.isDynamicZone(value)) {
         dynamicZoneFields[field] = 'JSON';
       }
     });
   }); // Cast dynamic zone fields to JSON
-
+*/
   if (!_lodash.default.isEmpty(dynamicZoneFields)) {
     const typeDef = schema.buildObjectType({
       name: `Strapi${(0, _lodash.upperFirst)((0, _lodash.camelCase)(type))}`,

This issue body was partially generated by patch-package.

Nice!
Are you going to make a PR?


Rework organization creation flow.

First three commits are prep commits for renaming and extracting some common code.
Next commit is to add PreregistrationRealm class.
Next 6 commits are to update the code to use PreregistrationRealm objects for realm creation. These all commits will be squashed, just kept them separate for now so that it is easier to review.
Last commit is for UI changes in the user registration form with realm details pre-filled.

Fixes part of #24307.

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Posting some of the initial questions in case someone sees this today -

How we should handle the existing PreregistrationRealm objects with string_id (subdomain) for which a realm has been created? I guess we would want to revoke them but do we want to revoke even if it was created by some other user or we just want to keep the link active and then prompt user during registration that subdomain is already used.
If user modifies the realm name, type or subdomain in the second form, i.e. the user registration form, then do we want to update the PreregistrationRealm objects with the new fields or we just want to keep the old fields. I have added the created_realm and created_user field to the PreregistrationRealm fields for now to track the object which was used for creating the realm.
How should we handle the already existing PreregistrationUser objects created for realm creation. They may not work now witht the current implementation. Do we just want to revoke them?

Will probably post a couple of more questions regarding code tommorrow.

The screenshots look good!
I'd change the "Email" field label on the first form to "Your email" for clarity, since everything else it's asking is about the org.  Just "Email" seems fine to me for the second form.

I don't have questions in the code currently, but the code in registration_helper is fairly complicated and thus needed to add a few assert isinstance statements to pass lint checks and would be good to probably refactor it a bit in future.
Also, have used a couple of functions for handling both PreregistrationUser and PreregistrationRealm objects currently, which makes code somehwat confusing but since we can change the realm details in second form as well while creating user, it becomes complicated to completely separate the code.
Just to note that I posted a few questions here.
Also, we can now probably remove the realm_creation field from PreregistrationUser class. Can do it separately in a new PR or once this PR is reviewed once.

I'd change the "Email" field label on the first form to "Your email" for clarity, since everything else it's asking is about the org. Just "Email" seems fine to me for the second form.

Updated this.
I am not sure why the production suite is failing though. I already tried rerunning it once.
@alya would be good if you can do a manual testing on this once.

This looks great -- posted everything I noticed in a read through everything. I didn't look at the post-review code for how nice it feels, just the diffs, so there may be things I'm missing. @mateuszmandera can you do a thorough review of this?

How we should handle the existing PreregistrationRealm objects with string_id (subdomain) for which a realm has been created? I guess we would want to revoke them but do we want to revoke even if it was created by some other user or we just want to keep the link active and then prompt user during registration that subdomain is already used.

Good question. I think what I'd expect as a user would be that trying to create the realm in the second form would give an error that the subdomain was taken (it must have been very recently!) and then require them change that error field in the second form. (So we might need an option to have the second form open in the editable state for this error handling case).

If user modifies the realm name, type or subdomain in the second form, i.e. the user registration form, then do we want to update the PreregistrationRealm objects with the new fields or we just want to keep the old fields. I have added the created_realm and created_user field to the PreregistrationRealm fields for now to track the object which was used for creating the realm.

Probably a question to discuss in Zulip, but I think either option is defensible.

How should we handle the already existing PreregistrationUser objects created for realm creation. They may not work now with the current implementation. Do we just want to revoke them?

I'm not sure. Revoking them all is certainly the simplest option. There's a fairly short window around this upgrade during that would have to overlap with when someone was on their way to click the confirmation link for this to come up, so it's possible just doing the deployment for this transition at a weird hour may be good enough. But if we can easily do a temporary commit that we can deploy to Zulip Cloud and drop a week later that just has the second form start in the "Realm creation section open" state for this class of link, or has these old links redirect you to the updated form with the email field prefilled (which at least looks like you made progress), that might be easier to roll out.

Looks good to me in manual testing!

One thing I noticed (not a regression in this PR) is that the thin down-angle in the org type dropdown doesn't look great to me. Is there a better style we use elsewhere that we could apply here?

Updated the PR as per feedback in inline comments and also replied to some of the comments.
Still need to work on (https://github.com/zulip/zulip/pull/24689#discussion_r1139173118) and https://github.com/zulip/zulip/pull/24689#discussion_r1137524561.

One thing I noticed (not a regression in this PR) is that the thin down-angle in the org type dropdown doesn't look great to me. Is there a better style we use elsewhere that we could apply here?

Will look into this but would probably be better to do in a separate PR.

Regarding questions discussed in https://github.com/zulip/zulip/pull/24689#issuecomment-1472514239:

Updated the PR to not revoke the PreregistrationRealm object with same subdomains, but don't think it is trivial to open the form with realm fields in editable state and error shown becasue we pass the realm details to the form as initial data and those values are not considered while validation. And if check the validity of whole form everytime while opening the second form, then it will show errors everytime due to full name field being empty which will be expected. Currently, what I have done is that the form opens with realm fields as non-editable, but when user tries to submit the form with a string_id which is already used, then the realm fields become editable with the error shown.
I will start the discussion about editing PreregistrationRealm objects on CZO.
Will try to do a commit which can be deployed briefly to handle old PreregistrationUser objects.

(I'm assuming @mateuszmandera will do the next review on this.)

The backend code looks good to me now! Haven't review the js changes since I don't feel confident reviewing our javascript

OK; I remember being pretty happy with the JS.  @sahil839 send me a PM when you have this ready for me -- I kinda want to get it integrated while it's fresh in my mind.

Updated the PR. Have also replied some of the comments above already. Other Changes after the last update -

Added code to make the pencil icon focusable and now the edit form is opened on pressing Enter when pencil icon is in focus. Also, the realm name field is now focussed after the realm details form is opened.

I added this docstring for the new class, and also moved it before PreregistrationUser just to keep those closer together:
+    """Data on a partially created realm entered by a user who has
+    completed the "new organization" form. Used to transfer the user's
+    selections from the pre-confirmation "new organization" form to
+    the post-confirmation user registration form.
+
+    Note that the values stored here may not match those of the
+    created realm (in the event the user creates a realm at all),
+    because we allow the user to edit these values in the registration
+    form (and in fact the user will be required to do so if the
+    `string_id` is claimed by another realm before registraiton is
+    completed).
+    """

This is great, merged, thanks @sahil839! @alya where do you think we should post about this change in chat.zulip.org asking for contributors to do some extra manual testing on it in the development environment? The new organization creation experience is one of those things that's pretty impactful if it's got bugs, so I'd love to have a few folks hammer on it over the course of this week before it goes to production.

And yes, we can add a temporary commit for the old PreregistrationUser objects created for realm creation. We would just basically need to alter/remove some assertion statements and some liens of code to show the realm details form always in that

Let's do that in a separate PR, since we won't want to merge it to main, and it'll be nice to let GitHub merge this whole branch.

The test failure looks like an unrelated test flake; I've triggered a rerun in CI and also am running it locally.


doc: give nicer error if env not set up

If one forgets to source the zephyr-env.sh script before starting a doc
build (using the top-level Makefile), a long screenful of error messages
go by and you can miss what the actual problem is.
Check if ZEPHYR_BASE is not set and give a nice short error message.
Signed-off-by: David B. Kinder<EMAIL_ADDRESS>

Codecov Report

Merging #9789 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9789   +/-   ##
=======================================
  Coverage   52.24%   52.24%
=======================================
  Files         212      212
  Lines       25951    25951
  Branches     5593     5593
=======================================
  Hits        13557    13557
  Misses      10159    10159
  Partials     2235     2235

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 af6af0f...6187707. Read the comment docs.

recheck


nodePackages.marked-man: init at 0.7.0

Motivation for this change
Added marked-man, a tool which is needed for building manpages for wluma, as described in https://github.com/NixOS/nixpkgs/pull/156112#issue-1111140392.
Also added marked, pinned to version 0.7.0, linked as a peer dependency. This is required, as the newest version is incompatible and results in an error.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[X] 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/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

@ofborg test thelounge

Adding new packages to nodePackages is highly discouraged because of its size and unmaintainable status. Please use buildNpmPackage instead which is easier and significantly faster to use and does not rely on codegen.


Decentralized peer-to-peer network, Phase 3 roadmap

Description
This is a rough mock of our plans to expand Universe's key recovery service. The recovery service would augment the currently planned Core+API+KeyManager architecture, most likely by adding recovery endpoints to Core.
Network
Using a decentralized peer-to-peer network, keys would be split and distributed among the participants, likely in a threshold-based construction. Retrieval from the network would require the user to provide an authorization token obtained from the KYC process.
Important issues that need to be addressed are arbitrary key storage, figuring out the KYC process, and the degree of decentralization we wish to allow. It would be interesting to allow users to chose their KYC provider out of a set of network-supported providers, allowing for different security models, varying "depths" of KYC, etc.
Experience
The main goal is to achieve the recoverability offered by BIP32-esque constructions that use a mnemonic while providing the user a much more "human-readable" experience. Intuitively, this allows users to recover their cryptographic keys using their tangible, real-world identity, rather than an arcane mathematical process. The identity verification process is already one that consumers are familiar with and are willing to accept at the event that they lose access to their bank or credit card.
Additionally, part of Universe's experience would offer a streamlining of the KYC process meaning that KYC information would already be provided once during the users' onboarding process.

Really great work here @itamarreif!


Add more info to TlsFail error

Hi,
here it is said that Error::TlsFail means we encountered problems during TLS handshake but this error is also returned by other functions e.g one that loads private key
https://github.com/cloudflare/quiche/blob/c726d349120ce72e8f0a00cd5176fd0767325511/src/lib.rs#L475
Will it be a good idea if TlsFail has message indicating what exactly went wrong?

Changing the error type itself would be disruptive. Perhaps instead it would be more ergonomic to just print an error log in these cases before returning?


Handle non-detach connection detach events

When a new connection created is in the UI by dragging a source endpoint, then dropped before it reaches a target endpoint, jsPlumb fires a connection detach event. We need to our connection detach event listeners to ignore this event to avoid us handling it as an ordinary detach.

@SteveBarnett ready for review.

:+1:


Add temp work-around to fix issue with Blizzards API changes.

Ran into the same issue as others: https://us.forums.blizzard.com/en/blizzard/t/upcoming-changes-to-battlenet’s-api-gateway/51561
Temp work until either I can further fix, or anyone else..

See: https://github.com/Adalyia/aiowowapi/issues/1

@Adalyia Hope you're around these days and thanks for your work on aiowowapi, it's been great using it.
I've added some other comments into the issue linked above.


Migrate user's guide to github.io

Now that the github.io site is active, the user's guide should be moved over there.

Done.


Remove ORCID Log In and allow linking to ORCID record through Google created account.

One other alternative is to allow the creation of local accounts. There are some modules for this, but allowing the OAUTH sign in to reconcile by (email address) will take a little bit of time.

Removed the ORCID login. Have to add linking to ORCID


[Bugfix] Fix the frag_b constant for mma rowsum of b16 input data type

We mistakenly fill the same constant value in frag_b of mma rowsum function for both bf16 and fp16. However, we should use different values because 1's binary representation in bf16 & fp16 is not the same.
>>> import torch
>>> x = torch.ones(2).half()
>>> x.view(dtype=torch.int32)
tensor([1006648320], dtype=torch.int32)
>>> x = torch.ones(2).bfloat16()
>>> x.view(dtype=torch.int32)
tensor([1065369472], dtype=torch.int32)

Test passed locally, will establish CI in the future.


Colour schemes are not working

Explain the bug
When I try colour schemes from the themes repository they don't change anything when I apply and restart the app. The restart message also shows it as a language change.
Expected behaviour
The colour scheme is apply and changes the look of the app,
Logfile
debug.txt
debug_fulltrust.txt
System Information

OS Version: Windows 10 20H2 19042.906
App version: v<IP_ADDRESS>

@josh-65 Some themes only have brushes for light or dark mode, can you see if switching the theme solves the issue?

i have try multiple themes file in both light and dark mode I don't see any change however I'm not sure what there support to change to look.

@josh-65 Which themes did you try?

blackpixel, discord purple, midnight, lavender

@josh-65 Can you try black pixel and lavender again?

I tried them nothing changed in dark or light mode even after a restart between them.

@josh-65 Can you upload the theme files you tested with?

These are unmodified versions from the themes repository
Themes.zip

@josh-65 Can you try black pixel and lavender again (you need to download the latest version)?

where are they i downloaded them from the themes repository when you ask me to re try them

just did it again to make sure and there's no change

I just realized lavender wasn't fixed at that time, can you download it again?

sure can i ask what there suppose to change/look like so i know what to look for

There working now. Here a suggestion though add a override app theme option. Since the themes may only work with one and make the app look broken if not set correctly.

@josh-65 Moving forward, we are going to require that custom themes include brushes for all themes.


DOC/STY: add example to scipy.signal.correlate

Reference issue
Closes #12369
What does this implement/fix?
Adds an example to scipy.signal.correlate docstring, minor PEP8 fixes.

Thanks @skresearcher !


Change logo to Pocket's new brand

Uploading the new logo from Pocket's new brand

From reading the docs it looks like I have to set up an ENS domain in order to access the space settings https://docs.snapshot.org/spaces/create#3-setup-your-space-settings
This is a lot of work for me to just update the logo.


Extract Users library

This PR:

Moves UserId and TenantId into the spine/base package.
Removes the users module which code was moved into the Users library.

Spine version advances to 0.9.25-SNAPSHOT

@armiol, PTAL.


[d2l-meter] property for hiding text

Context

circle meter took in a text property like the radial meter, however it only assigned it to the aria text. We'd like the circle meter to be able to behave similarly to the radial meter
https://d2l.slack.com/archives/C0PHG3QB0/p1712758381367159

Implementation Details

add text-hidden prop to meter-mixin
begin using the new prop to dynamically inject text beneath the circle meter

Any objection if we close this PR?

Closing. We can revisit this in the future if required.


add October update

Signed-off-by: Daniel Holbach<EMAIL_ADDRESS>

→ https://deploy-preview-561--fluxcd.netlify.app/blog/2021/10/october-2021-update/


Binding table name in postgres query

I'm trying to bind the table name into a postgres query, but the binding does not seem to complete.
The expected outcome is that the query gets all database contents, however the database errors with:
STATEMENT:  SELECT * from $1
ERROR:  syntax error at or near "$1" at character 15

An example repository with a working example is here: https://github.com/bryncoldwell/sqlx_table_binding
Code of interest:
#[derive(Debug, PartialEq, sqlx::FromRow)]
struct Thing {
    pub id: String,
}

async fn get_all() -> Result<Vec<Thing>> {
    let database_url = "postgres://username:password@localhost:5432/my_database";
    let pool = PgPool::new(&database_url).await?;
    let table_name = "my_table";

    Ok(sqlx::query_as::<_, Thing>("SELECT * from $1")
        .bind(&table_name)
        .fetch_all(&pool)
        .await?)
}

I could not find any examples with the table name as a binding, so I am unsure if this is expected behaviour or not.
Do you have any suggestions/comments? Thanks in advance!

You can't bind identifiers like table names in a query, that's basically SQL injection which parameter binding was designed to prevent: https://stackoverflow.com/a/25631375
You can use format!() to inject the table name into the query but we do not recommend this if table_name is untrusted input as a malicious user could trivially exploit this to do whatever they want with your database:
// the reason `query_as()` takes `&str` is to make this exact thing an obvious code smell
sqlx::query_as::<_, Thing>(&format!("SELECT * from {}", table_name))

If table_name is untrusted input you can wrap it in double-quotes but you then need to escape any double-quote in table_name with an extra double-quote:
sqlx::query_as::<_, Thing>(&format!("SELECT * from \"{}\"", table_name.replace('"', "\"\""))

However, I still don't guarantee that the above will completely prevent SQL injection. I would prefer if table_name is only one of a few possibilities that you just duplicate the query for each table.

Ok, thanks a lot for the explanation!
The table name would be coming from a configuration, which I think would be a trusted source.
It's still probably better to hardcode the table name into the SQL to avoid the code smell.


Add next-head-count & remove next-head class

Fixes #3494
Removes class="next-head" from the children of the <Head> component. Instead, a single sentinel meta element named next-head-count is appended. The content is the number of contiguous elements immediately preceding the sentinel that would have had the class="next-head" attribute.
During an update, instead of searching for class="next-head", the sentinel is located and the N previous elements are considered candidates for oldTags. New elements are inserted before the sentinel, and finally the sentinel is updated to reflect the new count.

Ping @timneutkens. Not sure why these changes would affect the size like that. Any ideas?

@devknoll looks like a polyfill for parseInt is being added.

D'oh... I could also just use the Number constructor, since I'm not relying on any of the other behavior of parseInt.

The diff view from the bot is super handy BTW, thanks!

Thanks for these changes, @devknoll!

This change brings issue https://github.com/zeit/next.js/issues/8220


Add dependabot config for actions & pip

Adds a dependabot config, providing weekly checking of dependency updates via the github-actions and pip package managers

Thanks Garry


AttributeError: type object 'RealtimeModel' has no attribute 'with_azure'

i am using this code from example:
https://github.com/livekit/agents/blob/main/examples/multimodal_agent.py
but when I try to use azure openai I get this error:
2024-10-10 10:52:21,413 - ERROR livekit.agents - unhandled exception while running the job task
Traceback (most recent call last):
File "/Users/arkodeepchatterjee/Desktop/today/agent.py", line 57, in entrypoint
model=openai.realtime.RealtimeModel.with_azure(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: type object 'RealtimeModel' has no attribute 'with_azure' {"pid": 59719, "job_id": "AJ_YSAHD5VcBTuf"}
2024-10-10 10:52:21,419 - ERROR livekit.agents - unhandled exception while running the job task
Traceback (most recent call last):
File "/Users/arkodeepchatterjee/Desktop/today/agent.py", line 57, in entrypoint
model=openai.realtime.RealtimeModel.with_azure(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: type object 'RealtimeModel' has no attribute 'with_azure' {"pid": 59720, "job_id": "AJ_HgwbpMdtmqTU"}

this is added in livekit-plugins-openai 0.10.3, please update and give it another try.

yeah it seems to be working
thanks a lot

also could you guide me on how to give video access to my agent too?
because currently it only has access to audio

Hey, let's not mixup issues. Feel free to create new issues


Feature: clicking on the same element in the hamburger view should re-open that view, like the menu items do

Problem Statement

The pain point is that when opening the hamburger menu, it is unclear what view I am currently on. Re-selecting the same view that I'm already on (e.g. Currency) does nothing. but the menu item registers a click animation. Clicking out of the hamburger menu reveals that I'm already on that view.
Evidence or User Insights

When selecting a menu item that has already been selected (e.g. US Dollars) the menu item closes, even though it has already been selected as a conversion currency. This behavior should be more universal within the app.
Microsoft Outlook, Gmail, and Github desktop allow re-selecting an item from the hamburger menu that is already open and it will return you to the same view while closing the menu. I did some very primitive research and found a paper which concluded that clicking on something  should make progress towards an existing goal according to (Wang 2008, 409) and other criteria such as discover-ability. However, the size of the study was very small (n=5) so the results may not be statistically significant.
Additionally, if the menu item does close when it is clicked and is in the same view, this might not cause the user to perform a needed context switch when they switch to a different view if the view does not change but the menu item closes.
Wang X. (2008) Design and Evaluation of Intelligent Menu Interface through Cognitive Walkthrough Procedure and Automated Logging for Management Information System. In: Shen W., Yong J., Yang Y., Barthès JP.A., Luo J. (eds) Computer Supported Cooperative Work in Design IV. CSCWD 2007. Lecture Notes in Computer Science, vol 5236. Springer, Berlin, Heidelberg
Proposal

This will make the menu items more universal, as they would behave more similar. If someone is converting multiple values with different units, they might forget what the last unit that they converted was; trying to re-select the same menu item will do nothing.
Goals

Goal is for the user to be able to select a menu item and go to that view, even if they are already on that view.
Non-Goals

Right-clicking on a menu item should not close the menu because it could have been an accidental click.
Low-Fidelity Concept

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

Good catch! Just to clarify, there is 2 ways to do it:

simply close the side menu
close the side menu and reset the view (default value, default units, etc...)

1 is IMO the most common solution used in Windows.

Treating this as a bug. Agree with @rudyhuyn here that the expected behavior is that the side menu closes.

@Decagon, do you still have issues some issues to build the app (disk space in my memory)? If you want to work on this fix, let us know!

@rudyhuyn Unfortunately, I won't be able to work on it for another month, however, I was able to get Visual Studio installed


Ability to pass paths on error

vaku version
API: 2.4.5
CLI: 2.4.5

Problem
vault list /foo
Keys
----
bar0/
bar1/
bar2/

if I have list  permission to foo/bar0 and foo/bar2 but no list permission for foo/bar1, running the following command:
vaku folder search foo/ --absolute-path my_secret will fail with a 403 error on listing foo/bar1 and the process will be terminated before attempting foo/bar0 and foo/bar2.
would it be possible to add an option to vaku folder search to bypass the inaccessible folders? e.g.
vaku folder search foo/ --skip-error --absolute-path my_secret

Hello @duxing! I think this is a great idea. A flag would need to be added to the client here with a matching cli flag. I think --ignore-errors would make sense as a flag. Folder search, read, list, etc... all call their equivalent path-based commands read/list/search so the API would just need to ignore errors and return success when that flag is true.
I am very open to this idea but I likely won't have time to work on it anytime in the next few months. If you'd like to try a contribution then I'm happy to review and release a change before then. Thanks!


[1.0.0r8] hatch version stack traces with static version

In my pyproject.toml I have:
[project]
version = '0.1.0'

Subsequently hatch version errors out with:
zsh 3373  (git)-[master]-% hatch version
Traceback (most recent call last):
  File "/home/asmodai/.local/bin/hatch", line 8, in <module>
    sys.exit(main())
  File "/home/asmodai/.local/lib/python3.9/site-packages/hatch/cli/__init__.py", line 202, in main
    return hatch(windows_expand_args=False)
  File "/home/asmodai/.local/lib/python3.9/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/home/asmodai/.local/lib/python3.9/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/home/asmodai/.local/lib/python3.9/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/asmodai/.local/lib/python3.9/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/asmodai/.local/lib/python3.9/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/home/asmodai/.local/lib/python3.9/site-packages/click/decorators.py", line 38, in new_func
    return f(get_current_context().obj, *args, **kwargs)
  File "/home/asmodai/.local/lib/python3.9/site-packages/hatch/cli/version/__init__.py", line 9, in version
    source = app.project.config.version.source
  File "/home/asmodai/.local/lib/python3.9/site-packages/hatch/project/config.py", line 330, in version
    raise ValueError('Missing `tool.hatch.version` configuration')
ValueError: Missing `tool.hatch.version` configuration

However, as I understood it, the tool.hatch.version part is only needed when you use a dynamic version setup, not for a static version assignment.
Edit: This also happens, with the same stack trace, for the case where version is statically set via setup.cfg.

Fixed in https://github.com/ofek/hatch/releases/tag/hatch-v1.0.0rc9

Awesome, thanks! Will give it a spin today.


Change the signature of load and preload to operate on Provider not Handle

Doing this in order to move more functionality out of the Handle class.
This has the additional benefit of making it possible to use normal methods as loaders (i.e. we don't need anonymous closure necessarily) but that's a separate change.

@prbot approve


Artifact can't be generated

Building with maven throw an error, this dependency can't be resolved:
        <dependency>
            <groupId>com.okta.libraries.framework</groupId>
            <artifactId>aperture-reporter</artifactId>
            <version>${aperture-reporter.version}</version>
        </dependency>

@enriquezrene, this is fixed in recent commit c8acbedafeb4ae3187b0c80b668bf816b76f00b3 where we removed an internal dependency you could pull the update and build it again.

Yes, I have removed also and now my app is running


Fix ruby distrib tests

Fixes internal issue b/178200110
Kicked off an artifact build in https://fusion2.corp.google.com/invocations/6ca294e2-2373-4e09-8159-40d6272a0a3c

No ruby failures in distrib tests now (just for FAILED: distribtest.csharp_linux_x64_dotnet5_dotnetcli)

No ruby failures in distrib tests now (just for FAILED: distribtest.csharp_linux_x64_dotnet5_dotnetcli)


Add on to the mitigation in https://github.com/visionmedia/supertest/…

Add on to the mitigation in https://github.com/visionmedia/supertest/pull/728/commits.

As [].every(val => typeof val === 'number')) evaluates to true in legit cases where we expect the body to return empty array the tests will fail.
Change is to also check for array length and defaulting to consider it as body instead of empty list of statues.

v6.1.6 released


Authentication failed

I have a mistake when I changed the  ~/.osmedeus/client.conf username and password
Now I can't start ./osmedeus.py
[-] Authentication failed
[-] Can't login to get JWT
[05/Dec/2019 12:01:27] "POST /auth/api/token/ HTTP/1.1" 401 63

Osmedeus use Django authentication system to mange users detail. That's file just a place to store credentials so you don't have to type it every time.
If you don't know how to change it just delete ~/.osmedeus/ folder and run install.sh again.

Thank u dude


Submit bulk lists to extraction queue

Following #212 (to generate lists) and #213 (to add error queue for recovering failed extractions) the UUIDs should be submitted to RabbitMQ for extraction.
lists to be submitted

[ ] demosaic
[ ] flirIr
[ ] plantCV
[ ] hyperspectral
[ ] ply2las
[ ] netCDF
[ ] canopy cover
[ ] sensorposition (geospatial)
[ ] environmentlogger

we will iterate through each list and submit the dataset/file to Clowder for extraction with a call like:
POST http://terraref.ncsa.illinois.edu/clowder/api/datasets/<UUID>/extractions?key=<SECRET>
data='{"extractor":"terra.environmentlogger"}'

Closing this issue because the Clowder instance rebuild will accomplish this without needing separate lists.


feat(api): Add endpoints to get robot logs

overview
Closes #1349.
changelog

Adds endpoint paths for logs in /health endpoint
Adds endpoint to grab serial.log
Adds endpoint to grab api.log

review requests
Additional implementations needed? More info on 400 status needed?

travis/pr failure due to known break in edge, which has been fixed. Go ahead with merge.


Low FPS on L515 camera

Required Info

Camera Model
L515

Firmware Version
(<IP_ADDRESS>)

Operating System & Version
Ubuntu 20.04

Kernel Version (Linux Only)
(5.8.0-59)

Platform
Intel

SDK Version
2.48

Language
python

Segment
{others}

I have an issue regarding low fps performance of L515.
I've used the same camera with same librealsense setup on two different machines, both with Ubuntu 20.04.
The machine that has low FPS performance issue has kernel: 5.8.0-59-generic.
The other one, on which the camera runs fine has 5.4.0-77.
Also, i mention that both machines kernel has the uvc patch.
I've tried using librealsense 2.47 and 2.48 on the machine running 5.8.0-59-generic.
The only warning that i see on both machines is in dmesg:
Failed to query GET_CUR UVC control 1 on unit 3: -32 ( exp. 1024 )
So, I've tried to disable auto-exposure, but i don't think that's the root cause, because i get the same warning on the machine that is running normal.
My setup is this:
ros2 launch realsense2_camera rs_launch.py color_width:=1920 color_height:=1080 color_fps:=15. depth_width:=1024 depth_height:=768 depth_fps:=$depth. infra_width:=1024 infra_height:=768 infra_fps:=30.
[INFO] [launch]: All log files can be found below /opt/ros/foxy/.ros/ros_log/2021-07-13-13-02-35-98171
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [realsense2_camera_node-1]: process started with pid [54]
[realsense2_camera_node-1] [INFO] [1626181356.270150072] [RealSenseCameraNode]: RealSense ROS v3.2.0
[realsense2_camera_node-1] [INFO] [1626181356.270235202] [RealSenseCameraNode]: Built with LibRealSense v2.48.0
[realsense2_camera_node-1] [INFO] [1626181356.270249215] [RealSenseCameraNode]: Running with LibRealSense v2.48.0
[realsense2_camera_node-1] [INFO] [1626181356.343920549] [RealSenseCameraNode]: Device with serial number f02xxxx \was found.
[realsense2_camera_node-1]
[realsense2_camera_node-1] [INFO] [1626181356.343945963] [RealSenseCameraNode]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:1.0/video4linux/video0 was found.
[realsense2_camera_node-1] [INFO] [1626181356.343949912] [RealSenseCameraNode]: Device with name Intel RealSense L515 was found.
[realsense2_camera_node-1] [INFO] [1626181356.344108165] [RealSenseCameraNode]: Device with port number 4-1 was found.
[realsense2_camera_node-1] [INFO] [1626181356.344114133] [RealSenseCameraNode]: Device USB type: 3.2
[realsense2_camera_node-1] [INFO] [1626181356.345972094] [RealSenseCameraNode]: getParameters...
[realsense2_camera_node-1] [INFO] [1626181356.346539777] [RealSenseCameraNode]: setupDevice...
[realsense2_camera_node-1] [INFO] [1626181356.346547190] [RealSenseCameraNode]: JSON file is not provided
[realsense2_camera_node-1] [INFO] [1626181356.346552631] [RealSenseCameraNode]: Device Name: Intel RealSense L515
[realsense2_camera_node-1] [INFO] [1626181356.346556962] [RealSenseCameraNode]: Device Serial No: f02xxxxx
[realsense2_camera_node-1] [INFO] [1626181356.346561214] [RealSenseCameraNode]: Device physical port: /sys/devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:1.0/video4linux/video0
[realsense2_camera_node-1] [INFO] [1626181356.346565828] [RealSenseCameraNode]: Device FW version: <IP_ADDRESS>
[realsense2_camera_node-1] [INFO] [1626181356.346569913] [RealSenseCameraNode]: Device Product ID: 0x0B64
[realsense2_camera_node-1] [INFO] [1626181356.346573726] [RealSenseCameraNode]: Enable PointCloud: Off
[realsense2_camera_node-1] [INFO] [1626181356.346577554] [RealSenseCameraNode]: Align Depth: Off
[realsense2_camera_node-1] [INFO] [1626181356.346581342] [RealSenseCameraNode]: Sync Mode: Off
[realsense2_camera_node-1] [INFO] [1626181356.346588667] [RealSenseCameraNode]: Device Sensors:
[realsense2_camera_node-1] [INFO] [1626181356.347023769] [RealSenseCameraNode]: L500 Depth Sensor was found.
[realsense2_camera_node-1] [INFO] [1626181356.348161052] [RealSenseCameraNode]: RGB Camera was found.
[realsense2_camera_node-1] [INFO] [1626181356.348235317] [RealSenseCameraNode]: Motion Module was found.
[realsense2_camera_node-1] [INFO] [1626181356.348244727] [RealSenseCameraNode]: (Infrared, 1) sensor isn't supported by current device! -- Skipping...
[realsense2_camera_node-1] [INFO] [1626181356.348250609] [RealSenseCameraNode]: (Infrared, 2) sensor isn't supported by current device! -- Skipping...
[realsense2_camera_node-1] [INFO] [1626181356.348256373] [RealSenseCameraNode]: (Fisheye, 0) sensor isn't supported by current device! -- Skipping...
[realsense2_camera_node-1] [INFO] [1626181356.348261492] [RealSenseCameraNode]: (Fisheye, 1) sensor isn't supported by current device! -- Skipping...
[realsense2_camera_node-1] [INFO] [1626181356.348267924] [RealSenseCameraNode]: (Fisheye, 2) sensor isn't supported by current device! -- Skipping...
[realsense2_camera_node-1] [INFO] [1626181356.348272653] [RealSenseCameraNode]: (Pose, 0) sensor isn't supported by current device! -- Skipping...
[realsense2_camera_node-1] [INFO] [1626181356.348278861] [RealSenseCameraNode]: num_filters: 0
[realsense2_camera_node-1] [INFO] [1626181356.348284455] [RealSenseCameraNode]: Setting Dynamic reconfig parameters.
[realsense2_camera_node-1] [INFO] [1626181356.353021235] [RealSenseCameraNode]: Done Setting Dynamic reconfig parameters.
[realsense2_camera_node-1] [INFO] [1626181356.354068702] [RealSenseCameraNode]: depth stream is enabled - width: 1024, height: 768, fps: 30, Format: Z16
[realsense2_camera_node-1] [INFO] [1626181356.354311670] [RealSenseCameraNode]: infra stream is enabled - width: 1024, height: 768, fps: 30, Format: Y8
[realsense2_camera_node-1] [INFO] [1626181356.356030774] [RealSenseCameraNode]: color stream is enabled - width: 1920, height: 1080, fps: 15, Format: RGB8
[realsense2_camera_node-1] [INFO] [1626181356.356055031] [RealSenseCameraNode]: setupPublishers...
[realsense2_camera_node-1] [INFO] [1626181356.358910295] [RealSenseCameraNode]: setupStreams...
[realsense2_camera_node-1] [INFO] [1626181356.625144922] [RealSenseCameraNode]: SELECTED BASE:Depth, 0
[realsense2_camera_node-1] [INFO] [1626181356.774198356] [RealSenseCameraNode]: RealSense Node Is Up!
[realsense2_camera_node-1] [WARN] [1626181356.854173052] [RealSenseCameraNode]:
[realsense2_camera_node-1] [WARN] [1626181356.854228210] [RealSenseCameraNode]: frame's time domain is HARDWARE_CLOCK. Timestamps may reset periodically.

Here is the performance:
ros2 topic hz /camera/color/image_raw
average rate: 8.837
	min: 0.065s max: 0.199s std dev: 0.04161s window: 10
average rate: 7.738
	min: 0.065s max: 0.267s std dev: 0.05741s window: 17
average rate: 6.604
	min: 0.065s max: 0.336s std dev: 0.08268s window: 22
average rate: 6.690
	min: 0.065s max: 0.336s std dev: 0.08466s window: 29
average rate: 6.221
	min: 0.065s max: 0.336s std dev: 0.08700s window: 34
average rate: 6.339
	min: 0.064s max: 0.336s std dev: 0.08673s window: 41
average rate: 7.168

Also, instead of 30 fps i have much less.
Any suggestions ?
Thanks

Hi @alexandru-oana  There was a case this week involving unstable performance on librealsense 2.48.0 with kernel 5.8.0-59-generic that was resolved by the RealSense user choosing kernel 5.8.0-43-generic instead.
https://github.com/IntelRealSense/librealsense/issues/9346#issuecomment-878534334
Your custom resolution / FPS settings look fine and the launch has accepted them as valid.
Do you see any improvement in performance if you add initial_reset:=true to the launch instruction to reset the camera at launch?

@MartyG-RealSense  Thanks for the fast answer.
No, if i use initial_reset:=true i still get low performance and
Failed to read busnum/devnum. Custom HID Device Path: /sys/bus/platform/drivers/hid_sensor_custom/HID-SENSOR-xxxx
I will try with kernel .8.0-43-generic

Hi @MartyG-RealSense
Didn't manage to test against 5.8.0-43 due to some technical issues, but is somehow irrelevant, at least for me, because compatibility with 5.10 is the one that i need. I've tested against 5.10 and again, same problem with low performance.
Any plans to support 5.10 LTS ?
Thanks

It has been shown to be possible to use kernels newer than the most recent officially supported one (5.8 at the time of writing this).  As you have experienced though, the results may be unpredictable.  It is possible that 5.10 may be officially supported at a future date since the SDK does add support for further kernels over time, though I do not have a time estimate that I can provide for the implementation of such support.
If your computer needs to use kernel 5.10 then an approach that may work for you is to build librealsense from source code with the RSUSB installation method and then build the RealSense ROS wrapper from source code.  The RSUSB installation process requires an internet connection but is not dependent on Linux versions or kernel versions and does not require kernel patching.  This approach would allow you to have kernel 5.10 on your computer for non-RealSense applications that require it whilst still enabling librealsense to work correctly.

Hi @alexandru-oana  Do you require further assistance with this case, please?  Thanks!

Not for the moment. My use case is not very straight forward and i cannot make use of your suggestion that implies compiling librealsense ( is time consuming ).
I appreciate very much you quick responses !
Thanks, please close this issue.

Thanks very much for the update.
I would add that if compile time is a problem for you then you can add a '-j'instruction to the CMake build instruction to speed up the build process by taking advantage of multiple cores in a CPU.  The higher the processor's specification, the higher the j-value it can use.
To work out a suitable j-number, you can find out the number of cores in your CPU and double it.  For example, a good j-value for a common quad-core CPU may be 8, whilst a higher-end processor could use 16.
An example of a build instruction with a j-value of '8' would be as follows:
sudo make uninstall && make clean && make -j8 && sudo make install


prayer times of the month

using FAB
inspire from habous.gov.ma

final work:
https://user-images.githubusercontent.com/2495180/235313670-5aa8391e-d3c3-48a7-8734-5e718277f037.mp4

``


[SMALL] Fix to #3180 - A column has been specified more than once in the order by list. Columns in the order by list must be unique.

Problem happens for specific combination of nested include statements. When we include reference we add a JOIN on the table that is being included. Issue is that QuerySource of the new table is copied from it's parent table. When include collection, we introduce a new query, but also add order by on the previous query. We determine which table to order based on the query source, but since query sources are the same, the choice is ambiguous. This may lead to queries that try to sort the same column twice, or trying to sort based on column that doesn't exist.
Fix is to always apply includes in a deterministic order that would prevent this situation from happening - first include collections, and only then references.

@anpete

:shipit:

merged a9f0dc05f68b926e2a2ef4d7bfd018fa3871699a


Add NuGet config to the repository

We've seen some flaky builds that fail to restore. Wes suggested adding a nuget.config:
Wes Haggard

looking through the repo I don't see a nuget.config explicitly in the repo, I'd suggest adding one to the root of the repo. I'm not sure why this fails sometimes but it is interesting that you are hitting this failure while restoring your autorest projects and it is looking at our blob feed which as far as I can tell isn't configured in that repo. I wonder if the nuget.config is leaking from somewhere else.

As for the blob feeds I've not seen similar issues around them so I wouldn't send much time on that front esspecailly given we are moving away from them and moving to DevOps feeds for our repos.

I'd suggest removing
https://github.com/Azure/autorest.csharp/blob/feature/v3/Directory.Build.props#L7 as well. If you still need a dev package from the language try adding the devops feed to your nuget.config. Like https://github.com/Azure/azure-sdk-for-net/blob/master/NuGet.Config#L8

Closed with https://github.com/Azure/autorest.csharp/pull/823


CLOUDP-74339: Update FileSystemStoreConfiguration to include BackupStore in the ops manager go client

Proposed changes

Jira ticket: CLOUDP-74339

Closes #[issue number]
Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation (if appropriate)
[x] I have run make fmt and formatted my code

Further comments

Codecov Report

Merging #58 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #58   +/-   ##
=======================================
  Coverage   55.08%   55.08%
=======================================
  Files          41       41
  Lines        1770     1770
=======================================
  Hits          975      975
  Misses        401      401
  Partials      394      394

Impacted Files
Coverage Δ

opsmngr/file_system_store_config.go
56.09% <ø> (ø)

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 95bd3ab...9d591f6. Read the comment docs.


Error with chromedriver version. Protractor require 2.31

Bug report

Node Version: v8.1.3
Protractor Version: Version 5.1.2
Chrome version: Google Chrome 59.0.3071.115
Angular Version: 1.5.9"
Browser(s): Chrome
Operating System and Version

Distributor ID:	CentOS
Description:	CentOS Linux release 7.3.1611 (Core)
Release:	7.3.1611
Codename:	Core

Your protractor configuration file:

module.exports = {
    // This will automatically use jasmine latest
    framework: 'jasmine',
    seleniumAddress: 'http://localhost:4444/wd/hub',
    getPageTimeout: 20000,
    allScriptsTimeout: 22000,
    jasmineNodeOpts: {
        showColors: true,
        realtimeFailure: true,
        includeStackTrace: true,
        isVerbose: true,
    },
    capabilities: {
        browserName: 'chrome',
        chromeOptions: {
            args: ['--no-sandbox'],
        },
        loggingPrefs: {driver: 'ALL', server: 'ALL', browser: 'ALL'},
    },
};

protractor status

[root@protractor]# webdriver-manager status
[14:21:22] I/status - selenium standalone version available: 3.4.0 [last]
[14:21:22] I/status - chromedriver version available: 2.30 [last]
[14:21:22] I/status - geckodriver version available: v0.18.0 [last]
[14:21:22] I/status - android-sdk is not present
[14:21:22] I/status - appium is not present

Error
[14:19:22] I/launcher - Running 1 instances of WebDriver
[14:19:22] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[14:19:22] E/launcher - The driver executable does not exist: /root/.npm-global/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.31
[14:19:22] E/launcher - WebDriverError: The driver executable does not exist: /root/.npm-global/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.31
    at Object.checkLegacyResponse (/root/.npm-global/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/error.js:505:15)
    at parseHttpResponse (/root/.npm-global/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/root/.npm-global/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/http.js:440:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:169:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/root/.npm-global/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession (/root/.npm-global/lib/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:709:29)
    at createDriver (/root/.npm-global/lib/node_modules/protractor/node_modules/selenium-webdriver/index.js:167:33)
    at Builder.build (/root/.npm-global/lib/node_modules/protractor/node_modules/selenium-webdriver/index.js:623:16)
    at Hosted.getNewDriver (/root/.npm-global/lib/node_modules/protractor/built/driverProviders/driverProvider.js:53:33)
    at Runner.createBrowser (/root/.npm-global/lib/node_modules/protractor/built/runner.js:195:43)
    at q.then.then (/root/.npm-global/lib/node_modules/protractor/built/runner.js:339:29)
    at _fulfilled (/root/.npm-global/lib/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/root/.npm-global/lib/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/root/.npm-global/lib/node_modules/protractor/node_modules/q/q.js:796:13)
[14:19:22] E/launcher - Process exited with error code 199

Hello,
I think the protractor is looking for the last available version of chromedriver. the 2.31. the version was release the 22th of July 2017, 2 days ago. I cannot use this version because it is not compatible with my centos version (GLIBC_2.18).
Any way the chrome site says that the last release is the chromedriver 2.30.
So why protractor try to use the 2.31 ? This version is not installed.
Is there a way to force the use of a specific version ?
Thanks.

Hi @othke
Your link now directs to 2.31, so I think in the meantime the data has been updated.
I'll check what the reason is, because you are also using a standalone server instead of the directConnect. Get back to you on that

Hi @othke ,
I also saw you placed your question on SO. I think it's also better to continue there in stead of here. I'll still look at it and will react there so it reaches more people.
For now I'm going to close it.

Hi @wswebcreation ,
Thanks for your answer. We will follow it on SO.
But do you know why webdriver-manager don't want to take account of the chromedriver version I specified ?
webdriver-manager update --versions.chrome 2.30
And when run protractor I get this error
E/launcher - The driver executable does not exist: /root/.npm-global/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.31
Even the webdriver-manager conf.json does not refer to the version 2.31.


Fix typo

Fix a fairly obvious typo likely caused by copy-pasting code and only
making one out of two necessary changes.

.


Decompiler does not work in macOS 10.15 due to "dyld: Symbol not found" error

Describe the bug
The decompiler does not work because of a missing C++ symbol when using Ghidra 11.1.2 on macOS 10.15 (Catalina). The error message I get at the command line is

dyld: Symbol not found: __ZNKSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE3strEv
Referenced from: /Users/mac/ghidra_11.1.2_PUBLIC/Ghidra/Features/Decompiler/os/mac_x86_64/./decompile (which was built for Mac OS X 14.0)
Expected in: /usr/lib/libc++.1.dylib
zsh: abort

and within the application is

Decompiler: Unable to initialize the DecompilerInterface: Decompiler process failed to launch (see log for details)

and in the project log is

2024-11-11 13:13:47 ERROR (DecompileProcess) Failed to launch Decompiler process: Decompiler executable may not be compatible with your system and may need to be rebuilt.
(see InstallationGuide.html, 'Building Native Components').
dyld: Symbol not found: __ZNKSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE3strEv
Referenced from: /Users/mac/ghidra_11.1.2_PUBLIC/Ghidra/Features/Decompiler/os/mac_x86_64/decompile
(which was built for Mac OS X 14.0)
Expected in: /usr/lib/libc++.1.dylib

To Reproduce
Run the following command at the command line
/Users/mac/ghidra_11.1.2_PUBLIC/Ghidra/Features/Decompiler/os/mac_x86_64/decompile
Expected behavior
The decompiler application should run without generating any errors.
Environment (please complete the following information):

OS: macOS 10.15.7
Java Version: Eclipse Temurin 21
Ghidra Version: 11.1.2
Ghidra Origin: official GitHub distro (ghidra_11.1.2_PUBLIC_20240709.zip)

Additional context
Although my version of macOS is not recent, it appears to meet the minimum system requirements. I have not attempted to build any native components yet as mentioned in the documents.
Thank you in advance for any help.

Our natives for Mac are currently built with Mac OS 15.x Sequoia.  I recommend you rebuild your natives using the buildNatives script.  You will need gradle installed.  Please see the Installation Guide for more info.

Thank you. I've followed the instructions in the installation guide and the decompiler is now working.

Glad to hear it.