Handle bad portfolio review format

Like this one: https://www.bogleheads.org/forum/viewtopic.php?t=407996

Another one: https://www.bogleheads.org/forum/viewtopic.php?t=408492

Bad account headers: https://www.bogleheads.org/forum/viewtopic.php?t=402999

https://www.bogleheads.org/forum/viewtopic.php?t=408538
Ticker fund xx%

https://www.bogleheads.org/forum/viewtopic.php?t=408562
Approximate Size Size of Retirement Portfolio: $419,000
Current retirement assets
Taxable - $143,000
23.9% SPDR SP1500 Composite ETF (SPDR) (0.03%)
7.1% Cash (I normally don’t hold cash, planning to invest)
3.0% Individual Stocks (Unrealized Gain of $1,400)
Old 401k - $169,000
22.3% State Street SP 500 Index (N/A) (0.02%)
9.6% State Street International (N/A) (0.08%)
5.0% State Street Russell Sm/Mid (N/A) (0.05%)
3.4% State Street US Bonds (N/A) (0.05%)
Current 401k - $33,000
4.9% JH Variable Insurance Trust 500 Index (JFIVX) (0.05%)
2.0% JH Variable Insurance Trust Intl Equity (JIEQX) (0.16%)
0.7% JH Variable Insurance Trust MidCap Index (JECIX) (0.15%)
0.3% Vanguard Small Cap Growth Index (VSGAX) (0.07%)
Roth IRA at Vanguard - $74,000
15.7% Vanguard Total Stock Market Index (VTSAX) (0.04%)
2.0% Vanguard Emerging Markets Index (VEMAX) (0.14%)


ScriptBlock looks like unused variable

This is what debugger shows:

This is what inline shows:

It would seem ScriptBlock is showing like nothing is set

so basically it's calling .ToString() on your ScriptBlock. I don't do this, the PowerShell extension does I'm pretty sure.

The problem is... if that has new lines in it, it gets cut off. You know what... now that I look at it, it looks like it also happens in hover:

vs

it looks like hover works in the string case though so now I'm confused...

hmm @weinand what do you think? The inline value is still cut off in the 3rd image so I feel like there's room for improvement there (a hover maybe with all of the text?)
The second image might mean it's an issue in the PowerShell extension... but I'm not 100% sure yet.


Avalonia Desktop example

any thoughts of doing an example using avalonia .net desktop gui? it also uses xaml.

You mean providing .NET Core Hosting to Avalonia desktop GUI?  I am not familiar with this framework. Also currently I am pretty busy on an ongoing project and no time to add new features  or examples.


Add to hacs

cool project....  It would be great if this were available via HACs

Im not using hacs. If you like please prepare PR.


[stable/kong] Added PodDisruptionBudget for Kong and its ingress

Signed-off-by: Felippe Mendonça<EMAIL_ADDRESS>
What this PR does / why we need it:
In order to prevent unavailability during voluntary disruptions such as node drains, this PR adds PodDisruptionBudget (PDB) objects associated with Kong deployment and its ingress controller.
More details about PDB: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#how-disruption-budgets-work
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[x] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @shashiranjan84

Please rebase on master.
Once you have disabled the value by default, please update one of the test case to enable PDB to test in CI once.
Thanks!

/ok-to-test

lint-charts has failed. Do I need to bump the version? @hbagdi

@felippe-mendonca Please rebase on master branch and bump up the version to fix the lint error.

/lgtm

@felippe-mendonca Thank you for your contribution!

/test pull-charts-e2e


Allow Start of Week to be Designated

I needed to set the start of the week to monday (since this is the standard here), and thought I'd post the changes I made to get this working in case they're usefull to anyone else:
calendars.js:96
const end = day === 0 ? 0 : days.length - day;

calendars.js:120+
const startDay = new Date(Date.parse(current.parsed)).getDay();
const endDay = new Date(Date.parse(`${months[current.month]} ${current.days}, ${current.year}`)).getDay();
current.start = startDay == 0 ? 6 : startDay - 1;
current.end = endDay == 0 ? 6 : endDay - 1;

Haven't been able to test it extensively, but it seems to be working fine.

Please feel free to open up a PR for this with tests so we can get this integrated!

On Oct 18, 2017, at 9:45 AM, Knut Svangstu<EMAIL_ADDRESS>wrote:
I needed to set the start of the week to monday (since this is the standard here), and thought I'd post the changes I made to get this working in case they're usefull to anyone else:
calendars.js:96
const end = day === 0 ? 0 : days.length - day;
calendars.js:120+
const startDay = new Date(Date.parse(current.parsed)).getDay();
const endDay = new Date(Date.parse(${months[current.month]} ${current.days}, ${current.year})).getDay();
current.start = startDay == 0 ? 6 : startDay - 1;
current.end = endDay == 0 ? 6 : endDay - 1;
Haven't been able to test it extensively, but it seems to be working fine.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


[Metrics] Enable user-defined metrics

We shouldn’t just let user define how the metric is computed via a configuration file.
Following that main idea, here are three approaches:

Pass in a queue/pipe entry point to the specific model function. For example:

def sum_model(xs, metric_queue=None)

Let the model return prediction + metric.
(My vote): expose the metric “queue” through http endpoint, let the model container post this data to the metric end point. This does not require any code changes in RPC logic.

e.g. http://localhost: 1391
in the model, the user can post any metric they want. (for example, the covariance, the categorical result histogram, …)
in the rpc.py metric server loop, we have another thread to setup a simple http server, check the posted result and move it inside the metric pipe/queue.
The idea is: don’t let the user mess with the metric pipe/queue. We handle the parsing and metric forming for the user.
Caveat: this might require user to both update their model and the metric_config.yaml.

For performance: we might be able to change http server to

zeromq (since they just need to expose tcp port)

@simon-mo just to clarify, this is for users to export metrics from their own models right?
For option 3, can you spec out a in a little more detail an example of what this would look like? This seems more complicated than letting the model return any additional metrics (option 2). Is the advantage that it doesn't require changing the RPC code?

Yep. The example use case I have in mind is

A classification model, the count for each categories.
Some metrics of input data: variance, image histogram (concept drift detection)
Time metric for long running model. (layer-wise latency for each layer in CNN).

Users should be responsible exporting, Clipper should be responsible handling the metric and integrat them into prometheus.
Option 3 indeed seems complicated. My main issue with option 2 is that it returns unpredictable result. Option 2 will actually require more changes to rpc code because the (a high performance) zeromq parsing code need to take into account for both returned data and returned metrics. I would rather let the metric be independent of the prediction process such that if the metrics go down, the prediction model is still serving.
For more detail on option3,  I believe it looks something like this:

RPC now has three process

The main process running zeromq and communicates between query frontend and the model. This process will aggregate some metrics (Clipper defined, like prediction latency etc) and put inside a queue for process 2 to pickup.
The prometheus metrics exporter process responsible for aggregate all the metrics coming from the queue and export the a /metrics page for prometheus main worker to scrape
The user defined metrics server that takes in json object and put it inside a queue for process 2 to pick up

On the user side, the user just need:

request.post('http://localhost:1391', json=USER_METRICS)

The code change is just another block of code in rpc.py.

Performance Caveat:

request module is blocking. The overhead need to be measured. Several possible solutions

Use async request (requires python3)
Bind socket and send raw data
Use zeromq to pass data around.

Another note:

I did consider passing the python queue directly to the model's predict function. But I don't know if it's doable or not. Plus, this seems to require even more changes.

Examples to be added:

Time metrics for preprocessing step and prediction step.
Result count for each classification (concept drift)

Closed via #440


First impression

I like it a lot and gonna try to use it for an app I am building, replacing  tachyons (which is also very good but more general and maybe less opinionated). Setting / unsetting state such as is-active is done via my own react-based app internals.
I am using ButtonGroups to create a toolbar. I need each button also being able to display a tooltip. So I had to add some CSS to make it work (otherwise ALL buttons have borderRadius), see below:
.ButtonGroup .ContextContainer::before,
.ButtonGroup .ContextContainer::after  {
  z-index: 100;  /* did not find a "modular" way to style pseudo elements */
}
.ButtonGroup .ContextContainer .Button  {
  border-radius: 0;
  box-shadow: var(--shadow-100), inset 0 1px 0 0 var(--gray400), inset 0 -1px 0 0 var(--gray400), inset 1px 0 0 0 var(--gray400);
}
.ButtonGroup .ContextContainer:first-child .Button  {
  border-radius: var(--borderRadius-200) 0 0 var(--borderRadius-200);
}
.ButtonGroup .ContextContainer:last-child .Button {
  border-radius: 0 var(--borderRadius-200) var(--borderRadius-200) 0;
  box-shadow: var(--shadow-100), inset 0 0 0 1px var(--gray400);
}

Could that be integrated into the modulz codebase ?
The other thing which caused a bit of headache, I need circular icon buttons, which modulz does not provide out of the box. So I applied modulz Avatar class to a button (that makes it look as needed), plus a custom class AvatarExtensionCircularButton which was basically copy-paste of hover / active state from the  modulz Button to make its behaviour more or less consistent with the modulz buttons.
.AvatarExtensionCircularButton {
  border: none;
  background-color: transparent;
  cursor: pointer;
  outline: none;
  user-select: none;
}
.AvatarExtensionCircularButton:hover {
  box-shadow: var(--shadow-200), inset 0 0 0 1px var(--gray500);
}
.AvatarExtensionCircularButton:active {
  box-shadow: inset 0 0 0 1px var(--gray500);
}
.AvatarExtensionCircularButton.is-active {
  background-color: var(--gray300);
  color: var(--gray500);
  box-shadow: inset 0 1px 1px 0 rgba(0,0,0,.1), inset 0 0 0 1px var(--gray400);
}
.AvatarExtensionCircularButton.is-active:hover {
  box-shadow: inset 0 1px 1px 0 rgba(0,0,0,.1), inset 0 0 0 1px var(--gray500);
}
.AvatarExtensionCircularButton.is-active:active {
  box-shadow: inset 0 1px 1px 0 rgba(0,0,0,.1), inset 0 0 0 1px var(--gray500);
}

is there a better way in modulz to create circular icon buttons ?

Hey, thanks for the feedback, I'm really glad to hear you like it :)
I'm already working on integrating both of your suggestions. The Button component will have a left, middle or right modifier for editing border-radius and shadow when in a button group.
I'm also working on a FloatingButton which will be a circular button, which you can put an icon inside.
I'll try to ship both of those updates this week.
Regarding tooltips, they are on the roadmap for JS components, but I'm not sure when they will be implemented.

Great, and thanks a lot.
I also needed to align Context different than the default left.
E.g. when button is positioned aligned to right of the viewport. Here the custom classes I added:
.Context.AlignCenter {
  left: 50%;
  transform: translateX(-50%) !important;
}
.Context.AlignRight {
  left: unset;
  right: 0;
}

I hope this kind of input is useful for you.

This kind of input is awesome, really. Keep it coming 💯
I've added support for button groups.

The new button groups utilities work great and helped me to get rid of some custom CSS (as mentioned above). Gonna close this.


sequelize sqlite -> slonik postgre

Introduces migrations and more low-level sql queries. The downside is that it locks the db to postgre, on the upside no more painful sequelise magic.

[ ] Add documentation

On mainnet it took ~3 hours to sync up from the start of the mary era. The DB currently takes up ~3.5GB which is acceptable. Although the graphql requests are slower than expected ~120ms for some queries. Also there seems to be something wrong with the forging.


Update evaluate-attack-surface-reduction.md

adding Warning for Server 2016 as ASR rules can have unexpected results on this unsupported platform

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks


Error in Teku: "Failed to send validator registrations to the builder network via the Beacon Node"

Sorry in advance for this question, which might not be a problem of mev-boost at all.
I have set up mev-boost as explained on Coincashew and added the appropriate settings in the Teku service file. But Teku gives me this error message:
2022-10-24 14:49:23.006+00:00 | validator-async-7 | INFO  | ValidatorRegistrationBatchSender | 0 out of 1 validator(s) registrations were successfully sent to the builder network via the Beacon Node.
2022-10-24 13:49:35.003+00:00 | validator-async-10 | ERROR | teku-validator-log | Validator   *** Failed to send validator registrations to the builder network via the Beacon Node
java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to register validators: builder not available
at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332) ~[?:?]
at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:347) ~[?:?]
at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1141) ~[?:?]
at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) ~[?:?]

The journalctl from mev-boost looks clean:
Oct 24 14:45:19 renes-server systemd[1]: Started mev-boost ethereum mainnet.
Oct 24 14:45:19 renes-server mev-boost[301697]: time="2022-10-24T14:45:19Z" level=info msg="mev-boost v1.3.2" module=cli
Oct 24 14:45:19 renes-server mev-boost[301697]: time="2022-10-24T14:45:19Z" level=info msg="using genesis fork version: 0x00000000" module=cli
Oct 24 14:45:19 renes-server mev-boost[301697]: time="2022-10-24T14:45:19Z" level=info msg="using 3 relays" module=cli<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Oct 24 14:45:20 renes-server mev-boost[301697]: time="2022-10-24T14:45:20Z" level=info msg="listening on localhost:18550" module=cli

Any idea what I could have done wrong? Thanks in advance for your time!

I had a syntax error in the Teku systemd service file (forgotten the backslashes at the end of the newly added configurations). Everything seems to be working now.


Add xcode article link

As a react-native newbie, that section wasn't clear.
That article was super helpful

Thx!


Weird wrapping with if let statement

@@ -418,8 +418,8 @@ impl<'conn> Statement<'conn> {
                             Ok(n) => data = &data[n..],
                             Err(e) => {
                                 loop {
-                                    if let backend::Message::ReadyForQuery { .. } =
-                                           try!(info.conn.read_message()) {
+                                    if let backend::Message::ReadyForQuery { .. } = try!(info.conn
+                                        .read_message()) {
                                         return Err(Error::Io(e));
                                     }
                                 }

Seems weird to break at that . and not double-indent the second line.

Yeah, would be better to break at the =, in fact, I think we might do this on master now?

Done


[monorepo] need build-only builder for the web engine

In the monorepo world we need to be able to just build the engine without running tests to support the following:

PRs and post-submit: immediately after the engine is built we can schedule framework tests without waiting for engine tests to complete.
Merge queue: build the engine without tests quickly so that framework hackers can iterate on the framework without building the engine locally.

To do that we need to split linux_web_engine.json into two files:

linux_web_engine_build.json: just build the web engine and upload the artifacts to the GCS buckets.
linux_web_engine.json: build and test the web engine (do not upload artifacts to GCS).

@eyebrowsoffire is looking into this now. It's mostly landed already, it seems.

This is done.


Pfam links to update

update Pfam links from
https://pfam.xfam.org/family/PF00069
to
https://www.ebi.ac.uk/interpro/entry/pfam/PF00069
remove
http://pfam.xfam.org/protein/P04551 (there is no Pfam gene specific view in Interpro)
Do I need to get the GO DB xrefs file updated for this?

remove
http://pfam.xfam.org/protein/P04551 (there is no Pfam gene specific view in Interpro)

I've changed the code.  The link will be gone on Wednesday morning.

Do I need to get the GO DB xrefs file updated for this?

Yep, xrefs needs changing.  I've made a pull request: https://github.com/geneontology/go-site/pull/1899

I've made a pull request: https://github.com/geneontology/go-site/pull/1899

That has been merged.  I'll check the main site in the morning.

I'll check the main site in the morning.

The main file at GO hasn't been updated yet:
http://current.geneontology.org/metadata/db-xrefs.yaml
I'm guessing it is updated only when the main GO pipeline runs.  I'll close this issue when the change comes through.

The main file at GO hasn't been updated yet:

It's now updated in the snapshot version:
http://snapshot.geneontology.org/metadata/db-xrefs.yaml
So I assume it will be in the "current"/release version soon.

This is finally fixed.


clarify self-describing

Some binary formats like Protocol Buffers are not self-describing. So without a schema, you have some ambiguity of what the wire format actually represents. This is different from something like JSON, where you have full information about the data and structure of the data.
I think it would be helpful to clarify in the docs if Muon is self-describing, as personally I will not use anything like ProtoBuf, because it is not self-describing.

Thanks!

Much thanks. I wish you luck and success with your project. Good day!


Statically link vips?

Is this something you would be open to a PR for sometime? I'm building my app as an artifact (bundling all node_modules, etc) on a build server (same architecture as web server), zipping it up, and having web servers unzip it and start up the app. It's been fine for awhile, but when I spun up a new web server recently it hit "cannot find libvips.so.38" errors, which I assume is due to slightly different libvips versions on the boxes. Obviously "lock down libvips" is a solution, but (imo) it would be ideal if a npm install would package up everything it needed.

Hi Brian, might https://github.com/lovell/sharp/issues/42#issuecomment-121893131 have the potential to provide what you're looking for?

Ah perfect! Sorry for the issue noise – should have run across that :)

For anyone coming across this, here's an adaption of @lovell's script for installation of an exact version of libvips: https://gist.github.com/brianreavis/b0e1141453e616f1b990


Cannot find module '../blockchain-js-core', Cannot find module 'blockchain-js-core'

build blockchain-js-ui error using "build.sh", not familiar with angular
ng version v1.65
npm version  v8.9.4
macOS High Sierra
thanks

not run "./install-link.sh"


Cannot update from 0.7.9 to 0.9.2

I tried installing the new version but the old version keeps popping up instead. Not really sure what more to say about the issue.

Yeah, the new installer doesn't detect the old installer script but it should overwrite it, so if you restart explorer windows should load the new version. If that doesn't work then uninstalling the old version first should get rid of it.
I'll update the text to clarify.


Fixed dl issue

Title
Author: oshaboy
Date: 2022-11-17
What I added
A cmake option
Why I added it
It didn't compile on WSL
Why it couldn't be done with a module
You need to compile MeowScript to use modules
How I added it
vim

Looks good to me!
But please add a little bit more information on the "How I added it" section. I meant more a explanation what you did exactly and why. But not that necessary for such a small (yet not unimportant!) commit.
Thank you ~
\(^ヮ^)/


Request signing OCB MacOS binary with Apple Developer credentials

Currently, the macOS opentelemetry collector builder (ocb) binary is not signed with an Apple Developer account. This adds another layer of friction to running the binary on current MacOS systems, as a security/malicious software popup requires heading to settings to override it.

OCB is released with GoReleaser; it currently supports notarizing/signing MacOS binaries using anchore/quill: https://goreleaser.com/customization/notarize/
This would require having an OpenTelemetry Apple account and paying the fee per year, of course. Thought it might be worthwhile discussing adding this feature to make ocb easier to use. Thanks.

I think there might be other related issues, especially around the main Collector binaries as well. While this sounds like a good idea, I don't think we have the means to pay for this yearly fee, and the benefits seem small for us: I believe our users are savvy enough to get their binaries from trusted sources and allow an exception for this binary. For automated usage in servers or CI/CD, I believe we provide attestations, which can be used to ensure the binary comes from us.
Unless a maintainer commits to maintaining this specific part, like we do for Windows (thanks @pjanotti!), I'd rather not have this.


Clearing the clipboard history

There was a problem clearing the clipboard history. Since I use the auto setting and the standard clipboard manager as far as I understand it is 'Clipster', how do I clear the history? The 'Clipster' package is not installed in the system (and I also do not want to install it, I use the gnome extension for the buffer) so the keys for cleaning type '--erase-entire-board' do not work. I see Clipster is in the folder with the extension Ulauncher, but where the file with the saved history contains I do not know.

I don't support that feature. You can install clipster and run the command to erase it, then uninstall. Or you can delete, ~/.local/share/clipster/history or set up clipster config to flush it regularly https://github.com/mrichar1/clipster#config-file.
Maybe a future version of ulauncher-clipboard will, but I don't aim to support all clipboard manager features. This extension is just for integrating the most convenient clipboard history functionality with Ulauncher.

I don't support that feature. You can install clipster and run the command to erase it, then uninstall. Or you can delete, ~/.local/share/clipster/history or set up clipster config to flush it regularly https://github.com/mrichar1/clipster#config-file.
Maybe a future version of ulauncher-clipboard will, but I don't aim to support all clipboard manager features. This extension is just for integrating the most convenient clipboard history functionality with Ulauncher.

It is clear, but cleaning or deleting the history file, for some reason does not clear the history. Let's just move past this area. Are you planning to support the 'Clipboard Indicator' gnome extension as a clipboard manager?

I don't plan to add support for anything. Just fixing bugs if reported. If people want to submit pull requests for new managers I will accept them though.


Translate main pages to all languages

@awennersteen I got you meant by only the EN and FR pages working, it is now fully translated 😉

hahaha,
I had planned to do this first thing in the morning, but I see that I'm already way too late


My Profile in opendota doesn't work.

I'd like to see my stats at opendota, because I'm already level 40 and I can't see any of my statistics. I hope that this issue can be resolved by the community.
Thanks for the attention. Hope that you read my message.
M. Cunha - Hidalgo

Have you enabled "Expose Public Match Data" in the client?


Fix merging devDependency from package.json

I noticed that the devDependency section of package.json was not being merged into the thirdPartyModules object correctly.
I added a unit test for the module, as well as changed the test for transform.js to use a mocked package.json for better test isolation, and updated the test fixtures to exercise the code with that mocked data.  Additionally, I have updated the README to specify that dev dependencies are included alongside the normal dependencies.
Let me know if there's anything else you'd like to see included in this pull request.

Thanks!


Xplat

Hi @honza1313, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

We can't do this until we've completed the work tracked in https://github.com/Microsoft/msbuild/milestone/6. It will be a glorious day.


Repeat Alerts

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
New Notification
🔖 Feature description
We really need a way to test every X seconds and get an alert for each one.
✔ Solution
Allow a monitor to be repeatedly monitored and alerted when it is still down.
❓ Alternatives
Other tools - one alert can be missed or ignored.
📝 Additional Context
No response

This option is confusingly hard to find, but it exists.

Well I don't have that Resend option at all.  Am I using an older version or did you enable that somehow? Thanks!

I'm using the latest version. No idea when it was enabled, but I think it's been here for quite some time.

Thanks - newest version has it! Would be nice to see a release notes on this thing, perhaps there is one on this github I'm just too dumb to find it

Hi, this option is available since 1.18.0 you can find the release note that indicates it here https://github.com/louislam/uptime-kuma/releases/tag/1.18.0

Im confused - just tell me how to get a repeating alert if something remains down.  Because putting 100 in there does nothing.

nevermind changing it to 1 seems to work


Fix pdftk version parsing problem in 3.0.2

When doing a pdftk --version command, version 2.02 gives pdftk 2.02 a Handy Tool but version 3.0.2 gives pdftk port to java 3.0.2 a Handy Tool. Hence the old regex wouldn't work on the newer version.
Updating the regex so that it'll work on both versions.

Yes, we need it!

please merge.. we need this

Is there somewhere an other gem witch is more active then this active_pdftk?


Pagination not working for POST /search if datetimes not the same for all items (pgstac)

When the limit is less than the total number of items in a collection in a POST request to /search with the pgstac backend, the total number of items returned if you loop through search.get_items() or search.get_all_items() is incorrect. This is not happening with the joplin test data and a relevant test (test_pagination_item_collection) because all of the items in both those instances have the same datetime.
I found when I ran the service locally (up-to-date repo) and copied the joplin data to a new collection but varied the dates, this issue exists. Here is the code I used to do that in case anyone wants to duplicate. Note that while I did you pystac_client in my example below, I confirmed it is not in issue with that library - the same thing happens with just requests.
import requests
from pystac_client import Client
import uuid

host = "http://<IP_ADDRESS>:8082"
collection = "joplin"
new_collection = "joplin-diff-dates"

# Create a new collection
resp = requests.get(f"{host}/collections/{collection}")
col = resp.json()
col.pop("links")
col["id"] = new_collection
resp = requests.post(f"{host}/collections", json=col)

# Copy items from existing to new collection with different dates
cat = Client.open(host, ignore_conformance=True)
search = cat.search(collections=[collection])
for idx, i in enumerate(search.get_items()):
    i.id = str(uuid.uuid4())
    i.collection_id = new_collection
    d = i.to_dict()
    d.pop("links")
    d["properties"].update(datetime=f"2020-01-{idx+1:02d}T00:00:00")
    resp = requests.post(f"{host}/collections/{i.collection_id}/items", json=d)
    resp.raise_for_status()

Then when you search the collection, you get different results back (should be 30):
search = cat.search(collections=[new_collection], limit=10)
len(list(search.get_items()))

limit of 10 yields 11 results
limit of 15 yields 22 results
limit of 20 yields 29 results
limit of 50 yields 30 results
I am also able to break the test_pagination_item_collection collection in the test_item.py file if I add this line in the ingest five items portion:
      test_item["properties"]["datetime"] = f"2020-01-0{idx+1}:T00:00:00Z"
I realize this may be an issue with pgstac and not stac-fastapi but haven't been able to confirm that yet.

Oh, also confirmed this isn't an issue with sqlalchemy backend.

cc @bitner

This was fixed with pgstac v3.3 and stac-fastapi now points to that version. Closing issue!


Ensure all special cases for ops (weird strides) are tested and handled in new code

Example:
public class Temp {
    public static void main(String[] args){
        List<Pair<INDArray,String>> list = NDArrayCreationUtil.getAll3dTestArraysWithShape(123,3,4,5);
        for(Pair<INDArray,String> p : list){
            System.out.println(Arrays.toString(p.getFirst().stride()));
        }
    }
}

Note that a number of these arrays have strides that are not strictly ascending or descending (hence aren't strictly speaking c or f order):
[20, 5, 1]
[1, 3, 12]
[20, 5, 1]
[45, 5, 1]
[40, 10, 1]
[90, 10, 1]
[3, 9, 36]
[1, 1]
[1, 3, 12]
[60, 1, 12]   *****
[1, 45, 3]    *****
[1, 15, 3]    *****
[20, 5, 1]

This is out of date now.


Separate "diagnostics" or "debugging" section in docs sidebar?

Really excited to have https://github.com/dask/dask/pull/8648, but I found it odd that it's sitting in the sidebar between DataFrame and Delayed:

Should we have either a sub-heading, or an entirely separate heading, for things like this? I'd probably include:

https://docs.dask.org/en/latest/how-to/debug.html
https://docs.dask.org/en/latest/dashboard.html
https://docs.dask.org/en/latest/understanding-performance.html
https://docs.dask.org/en/latest/diagnostics-local.html (I can no longer figure out how to easily get to this page)
https://docs.dask.org/en/latest/diagnostics-distributed.html (I can no longer figure out how to easily get to this page)

(I also find it very confusing that all these things about distributed diagnostics/dashboard are in the dask/dask docs, not dask/distibuted, but that's its own can of worms we don't need to get into right now.)
cc @ncclementi @scharlottej13 @ian-r-rose @jsignell @jacobtomlinson

Yeah I think it should go near "Deploying Clusters" - no strong preference about before or after. Bigger picture the plan is to absorb all of the narrative-style distributed docs into dask.

I think this issue has 2 parts.

Moving "Dashboard DIagnostics" above Deploying Clusters
Design a heading/subheading that includes the links mentioned in the original comment.

I think we should put some thought and go for 2, but do we create a separate heading call "Diagnostics and Performance" and put in there all the links mentioned above. Should we have debug in how-to and also in this new heading? Any opinions?

I like "Diagnostics and Performance" as a heading name. I think debug can move out of how-to and into that new heading.

We used to have "Understanding Performance" as a header and I referred to
it often.  Nowadays I find that I have to use the searchbox to get to those
pages.  +1 generally on this approach.
On Fri, Mar 25, 2022 at 3:29 PM Gabe Joseph @.***>
wrote:

I like "Diagnostics and Performance" as a heading name. I think debug can
move out of how-to and into that new heading.
—
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/8841#issuecomment-1079411177, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTB2E4DU3RO25CUISIDVBYO37ANCNFSM5RSC7HAA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add files via upload

Hacktoberfest! 🎊🎈
🎉 Have you read the Contributing Guidelines? 🤔
Yes.
📝 Description
(Write your answer here.)
Fixes #issue_no 🔧

✅ Checklist

[ .] I've read the contribution guidelines. 📚
[ ] I've checked the issue list before deciding what to submit. 🔍
[ ] I've edited the README.md and linked to my code. 📄

🔗 Related Issues or Pull Requests
(Write your answer here.)

Hi there!
Although this repo is not part of Hacktoberfest 2024, we have some great alternatives for you. Welcome to SkillShow, a repository focused on skill enhancement!
Guidelines:

Please adhere to the existing guidelines.
No additional rules, thanks!
Check it out here: SkillShow.

Note: Start by creating an issue. Once it’s assigned to you, feel free to open a pull request (PR). Directly opening a PR will lead to an invalid label.
Looking forward to your contributions!


⚠ Samsung has degraded performance

In e1ecca6, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2506 ms

Resolved: Samsung performance has improved in 16518aa.


Display memory pool

Add ability to display memory pool not only heap and non heap memory usage.

Links that can help:
http://jansipke.nl/getting-metrics-from-the-java-virtual-machine-jvm/
https://github.com/stagemonitor/stagemonitor/blob/master/stagemonitor-jvm/src/main/java/org/stagemonitor/jvm/JvmPlugin.java

Thx. I will also migrate com.codahale.metrics to io.dropwizard.metrics version 3.1.2

Finally I decided to gather not only usage metrics but rather dedicated values (max and use). What I would like to propose is to get rid of heap non heap and instead use this new (or at least add this new):

New Generation values (jvmPoolNewGenUsed, jvmPoolNewGenMax) combined with GC values (jvmGcNewCount, jvmGcNewTime) on one graph.
Old Generation values (jvmPoolOldGenUsed, jvmPoolOldGenMax) combined with GC values (jvmGcOldCount, jvmGcOldTime) on one graph.
Survivor Space values (jvmPoolSurvivorSpaceUsed, jvmPoolSurvivorSpaceMax) on one graph.
Perm Generation values (jvmPoolPermGenUsed, jvmPoolPermGenMax) on one graph (if java < 1.8).
Metaspace values (jvmPoolMetaspaceUsed, jvmPoolMetaspaceMax) on one graph (if java >= 1.8).
CodeCache values (jvmPoolCodeCacheUsed, jvmPoolCodeCacheMax) on one graph.

@denzelsN do you think gui part will be complecated? Backend part is already merged.

sorry. I'll check. and discuss with UX designers.

@dawidmalina It looks like the code for storing (collector) and reading (web) from hbase is not implemented yet.
There's a plan to overhaul AgentStat after 1.5.2 is released (within a week or two). It will be a good idea to implement the backend code then as well.

Backend + API implemented in 1.6.0 - #1533


Do not require {} around content to right of match case.

I believe @yunxing was pushing for this. I did some experiments and it turns out this save us a ton of both horizontal space (because less indentation) and also vertical (because less indentation triggers fewer wrappings).
So we can just assume there's already an "implicit" wrapping {} around each match case to the right of =>. This works very well in the switch statements because we are already guarded by | tokens, so there shouldn't be any conflicts/downsides. It's also more familiar to people who have used case/switch statements in other languages.

Done


Running emcee with mpi and openmp

I am trying to run emcee with MPI, but my model in lnlike function is a C code runs with openmp. The code works faster if openmp is off. Is there anyway to make use of MPI and openmp together?. Any suggestions to include in the python script or Slurm script is appreciated. Thanks.

I can't give you very specific suggestions, but if you can get slurm to run just one MPI job per machine (but treat it as occupying all cores on that machine) then the openmp should handle filling all the cores of the machine.

@sultanier If you are running on a supercomputer cluster, then you will need to follow the instructions on how to submit a MPI + OpenMP job. For instance, on our local supercomputer running the slurm scheduler, this link explains how to submit such a job.
The key is to convey the OpenMP intent within the MPI script, and then this line
export OMP_NUM_THREADS=$SLURM_CPUS_PER_TASK, that says to use as many OpenMP threads as you have requested within the slurm script. What happens is that frequently OMP_NUM_THREADS is set to 1, and unless you specifically alter that in the slurm script, you can not use the OpenMP threads.


Using props results in multiple duplicate classes.

Assuming that I'm doing it wrong or this is expected behavior.
When I use a callback for a property:
export default theme => ({
  button: {
    backgroundColor: props => props.color,
  },
});

I get multiple classes for button console.log(props.classes):
{
  button: "button-0-31 button-0-22",
}

But when the page renders only a single of the classes is available such as "button-0-22".
Everything works fine, I just find it odd that there are multiple classes which are unused or rendered to the page.

You seem to be doing all right, but what does this mean?

But when the page renders only a single of the classes is available such as "button-0-22".

You would expect to find .button-0-31 and .button-0-22 in either the inspector's styles or in the document <head>, but only .button-0-22 exists. Here are some screenshots doing the same thing (Column instead of Button):

You can see multiple classes are rendered:

But the inspector only sees one of them:

It's missing from any of the relevant <style> tags:

So the problem is that you don't see that css rule in the style tag, right?

I'm really asking if this is a problem, I guess. I just find it strange to have multiple classes generated and then it doesn't use them 😅 .

If it doesn't use them, why is it working as expected?
It think you just got trapped into the fact that insertRule CSSOM API which is used for dynamic styles is not visible in style tag text content representation, you need to go into style.sheet.rules to see it or to see it applied on the element in the styles panel.

Thank you
Keep up the good work 👍

@kof But that duplication sucks in SSR mode. For example if we want to create Grid.Column class using dynamic props doing something like it:
baseClass: props => ({width: $(props.size * 100)%})
and calling it like it:
<Grid size={1/10} />
<Grid size={1/10} />
<Grid size={1/10} />
<Grid size={1/10} />
<Grid size={1/10} />

react-jss will produce 5 classes with the same style, yes?

Yes, that's correct.
On 15.  For example if we want to create Grid.Column class using dynamic props doing something like it:
baseClass: props => ({width:$(props.size * 100)%})
and calling it like it:

react-jss will produce 5 classes with the same style, yes?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

yeah, that can be optimized potentially https://github.com/cssinjs/jss/issues/501
for now you could generate the class in a parent component and pass it to all children

@kof wow, thx for fast reponse! So for now it will be faster to not use dynamic classes in heavly exploated components. When do you want to introduce suggested feature?


Fixed typo in readme

Fixed a typo.
From ...we assume that you serving the page... to ...we assume that you **are** serving the page....

Thanks for contributing!


student/instructor views

students should see their progression through the material
Instructors should see problem data submitted by students

In Sidebar:

Instructors :"x%" next to each item indicating the average percentage complete of each item across the enrolled students. If the item has no problems this is not displayed
Students: "a/b" next to each item indicating the number of complete problems in each item. If the item has no problems this is not displayed. If a section is complete it changes color to green with a tick instead.

On Problem:

Instructors: eye icon that opens a dialog showing full list of responses
Instructors:  tick icon and "a/b" indicating number of students who have completed this problem
Instructors:  easy / average / hard colored amber / green / red with tooltip showing "a/b" difficulty

api enpoints needed:

/event/[eventid]/problems: if you are an instructuro on this event returns all the problems that are in tags in eventItems for this event, for all students enrolled on this event. If you are a student on the event only returns your own problems.


server: Add support for hostPorts

This fixes #560, mostly. The common cases of connecting to the port via the host's IP both locally and remotely does work. Connecting locally by 'localhost:port' doesn't work, as that requires the interface which can reach the container to be known. It wasn't obvious to me on how to get that out of the netplugin.
@rajatchopra PTAL.

Can we add an integration test? Thanks!

Yep, test coming soon. Need to get them running on my system first.

It wasn't obvious to me on how to get that out of the netplugin.

It seems impossible without enforcing a new interface API. We will ultimately have to rely on the network plugin to do all the work anyway and this code will go away. Until then, we can examine the option of enforcing an API that will return the device name used by the netplugin (and in case there is none, then the localhost access will not work).
This work looks good at a glance. Will review again at next chance. Thanks.

@rajatchopra @mrunalp This has tests now and is passing. Please take a look when you get a chance.

@apilloud Yeah, I will take a look.
@runcom e2e tests haven't run on this one :/

/retest

retest

Tests still haven't returned on this one :/

kicked in CI directly now...

This has been sitting around for a while, so I rebased.

Mmm something has failed in RHEL

The test is failing in rhel:
not ok 42 Connect to pod hostport from the host

More output from failing test:
 Ncat: You must specify a host to connect to. QUITTING.
RHEL

A few lines up: Error: either "dev" is duplicate, or "proto" is a garbage. Something about looking up the default gateway failed. Added some debug output, as I don't have a RHEL system.

retest

Everything's OK here, LGTM

LGTM


solution: i have the same question, use the command not works,please help me,thank you very much!

cleos set account permission gushi active '{"threshold":1,"keys":[{"key":"EOS7nLRAheR7tYMiTiCA2ry2vW2Yh4LKoMUsxiE6YcxSCh2nS8tq4","weight":1}],"accounts":[{"permission":{"actor":"eosio","permission":"eosio.code"},"weight":1}]}' owner -p gushi@owner
Very good! it works!
Originally posted by @lingyiliu016 in https://github.com/EOSIO/eos/issues/4432#issuecomment-401523179

cleos set account permission yucheng22222 owner '{"threshold":1,"keys":[{"key":"EOS5MiseD8XwNUb5QkSUMjgn1kacQZ4GhicR5Rp89xiXk1tcEsMk3","weight":1}],"accounts":[{"permission":{"actor":"eosio","permission":"e
osio.code"},"weight":1}]}' owner -p yucheng22222@owner

Error 3090003: Provided keys, permissions, and delays do not satisfy declared authorizations
Ensure that you have the related private keys inside your wallet and your wallet is unlocked.
Error Details:
transaction declares authority '{"actor":"yucheng22222","permission":"owner"}', but does not have signatures for it.

Did your wallet have owner key?

You must have the current owner key for the yucheng22222 account in an unlocked wallet accessible to cleos.
If you still have problems and wish to discuss further, please post in https://eosio.stackexchange.com. To keep things organized, Github issues are intended for bugs reporting and features tracking, and Stack Exchange is the right place for any technical support discussions. Thanks!

tks, i solve the question!

I will adopt your opinion. post in https://eosio.stackexchange.com.


Problem with Angular 1.4.8

I update my project with angular 1.4.8 and have a problem on this module
Thank you

@popzadid ,
Can you please replicate the problem on JsFiddler or Plunker? That'll help in debugging.


Quote arguments in .vscode/tasks.json incase of spaces in expanded paths

PR Summary
Add quoting to the file path arguments in the VS Code Tasks.JSON file, so that if the paths contain spaces when VS Code expands them, they will not become multiple arguments to the command.
PR Context
This supports building the project in user instances where spaces may be contained in the path to the repository on the users system.
Fix #10199.
PR Checklist

[X] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[X] Summarized changes
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[X] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[X] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[X] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[X] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@PoshChan Please retry macos

@TravisEz13, successfully started retry of PowerShell-CI-macOS

@PoshChan Please remind me in 20 hours

@TravisEz13, this is the reminder you requested 20 hours ago


Deploy holiday overlay and updates to GA tracking

First there are three pull requests for branches that need to be merged in:
https://github.com/creativecommons/creativecommons.org/pull/512
https://github.com/creativecommons/new-www-theme/pull/12
https://github.com/creativecommons/new-creativecommons.org/pull/32
Then we can deploy the code to prod and make the necessary changes in the CMS.

All merged.
Thank you!


Need orWhereNotInJoin()....!!

I want's to use like $user->whereNotInJoin('roles.id', [1, 2, 3, 4, 5, 6, 7, 8])
thanks

working on it ...

merged! 4.0.5 version ....


Disabled not necessary msgno getting procedure.

Hi @Webklex
I've increased the performance of message fetching procedure.
In the setUid method was (from my point of view) not necessary line getting msgno.
So I decided to remove it - because when we get messages via UID (and it's been checked before, e.g. in setSequenceId()), there is no need in using msgno. Could you validate whether it makes sense?
Result: (in my case) reduced 6 seconds to 0.8s
Greetings!

Hi @szymekjanaczek ,
it's fixed :)
https://github.com/Webklex/php-imap/commit/95925dad6a86936253dba82a22a7d267d951878c
Best regards,


UI crash in /chat page if user has no visible name

Describe the bug
If a member of a chat has visible_name set to null, it does not appear in members list, causing the endpoint /api/chats to return empty members list. Ui is epecting at least 1 user in the member list, so the UI crashes. In this particular case it is good to have a crashing UI (it hits an unimplemented!) because this is not expected to happen.
[{"chat":{"id":"8301116d-6c26-489e-82cf-e5768c8cf783","members":[]},"unread_messages":1,"members":[]}]

To Reproduce
Steps to reproduce the behavior:

Create a new user, without setting a visible name
Start a chat with someone
Go to /chat page
See javascript console

It may be due to a db query failing: it expects a String, but find a NULL. We can enforce the visible_name to be not null and copy from username when registering a new user.


Implement Game.swift to represent current game state

Class Specification
Attributes

Instance of a Server.swift class to handle connections to the server
List of player on map
List of dots on map
Pacman's current state

Get

List of visible dot coordinates
List of visible player coordinates

Set

Request updated information from server
Check for pellet/dot collision (to see if the player has scored a point or should have a power up)

For reference and clarification:

The server is located at http://pacmacro.herokuapp.com.
Pacman's current state will be a combination of the GameState and the PacmanState.
The application will send information to the server about whether collision has occurred.


Added description of the provisioning manifest

Added description of the contents of the provisioning manifest.
Clarifies why I should be interested, the fact that what is described below are fields not other files and the general target of the manifest within CodeZero.

Removed explicit documentation about appspec, as developers should focus on Application Manifest instead.


Improve consistency with official controller spec style

Some feature specs use a controller spec style that is not the "official" one.
# bad?
describe "GET #index" do
  subject { get :index }

  it "renders the index template" do
    expect(subject).to render_template(:index)
  end
end

# vs.

# good?
describe "GET #index" do
  it "renders the index template" do
    get :index

    expect(response).to render_template(:index)
  end
end

Looking at the code base, subject { get :index } is not used anywhere else. It seems to me that this style has questionable semantics, so aligning the the feature spec content with the common approach for controller specs makes sense to me.
In general, I'd like to hear your opinion on using the get, post, patch call as a subject.

I don’t quite see the problem here. What do you mean by questionable semantics?

As I understand subject, it should be an object that you test. Controller tests usually test response or side-effects of invoking a controller action. Thus putting get, post, patch might be a misuse of subject as you are interested more in side-effects, as if calling subject here is like calling a before action.
Also, I did not find many uses of this pattern, which made me wonder why.
Having said that, I do not have a strong opinion and created this PR basically to find out what is wrong and what is right. However I lean towards eliminating the discrepancy in styles.

I see.
Rails bends typical RSpec patterns to its needs. Do we test the response, or the interaction here, where the response is the returned result?
Styles of writing specs differ, and we don’t want to impose any specific style as one and only.
I like your suggested change, and I’m inclined to merge it.
However, none of the docs here dictate the style on how to write specs.

Thank you!

Reverted because as above:
If you want to name the subject here I'm on board with it but otherwise I think it should be closed to avoid churn.


Element should have a "design discussion" section talking about build order

We should document some of our design decisions about how widgets build:

The framework guarantees that ancestors build before descendants.
The framework does not guarantee anything about the order other than this.
Some widgets might in rare cases build twice, this is considered an aberration to be avoided (layout builder that ends up dirty both at the widget layer and the layout layer is the example).
One pass build.

Maybe point to "Inside Flutter" (https://flutter.dev/docs/resources/inside-flutter).

cc @rrousselGit @goderbauer

Can't find any reference about the topics mentioned above in the Inside Flutter link, so I assume this still valid.


Show tooltip only when cursor is present

Details

This PR will fix the tooltip showing on touchscreens without mouse/pointer. A condition for pointer is added in filed Tooltip/index.js that show Tooltip only when there is pointer present otherwise don't show the Tooltip.
Fixed Issues

$ https://github.com/Expensify/App/issues/9737
Tests

Open any report in mWeb.
Long press back button in report screen and see the when navigated back back tooltip is not shown.

[x] Verify that no errors appear in the JS console

PR Review Checklist

Contributor (PR Author) Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] Any functional components have the displayName property
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
The Contributor+ will copy/paste it into a new comment and complete it after the author checklist is completed

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

QA Steps

Launch the app on mWeb.
Press on any report to open it.
Long press back button in report screen header.
Navigated back and back tooltip is not shown.
Repeat the above steps multiple times to verify that tooltip doesn't appear on Touchscreens

[x] Verify that no errors appear in the JS console

Screenshots

Web

Mobile Web

https://user-images.githubusercontent.com/36359331/190351463-0bdc655d-6e44-40e0-9dbf-971564714cc7.mp4
Desktop

https://user-images.githubusercontent.com/36359331/190360386-39cb83da-b34c-431a-b666-706f3c5050cc.mov
iOS

https://user-images.githubusercontent.com/36359331/190366748-2ec299ac-6d9a-4dd5-bce8-866f0b632f54.mov
Android

https://user-images.githubusercontent.com/36359331/190363103-8468e16c-33ae-4760-997e-adde5e39a5d2.mov

This is failing for me on the web resized to a small screen
https://user-images.githubusercontent.com/85645967/194640724-ab0e29c9-2293-40fd-9893-4504cdc44918.mov

@Santhosh-Sellavel The tooltip will always show when there is a mouse/cursor present and in this case that you mentioned there is a mouse/cursor present that's why it's showing tooltip.

Yeah that's fine, but should not show on chat list

@Santhosh-Sellavel, I debugged the case where tooltip was shown on chat list and this is what i found.
Tooltip not hiding root cause.

showTooltip function was invoked onHoverIn and after navigation to back screen hideTooltip function is not called as mouse is still and onHoverOut is not triggered to run the hideTooltip function(console.logs can be seen in the video below to support and explain what i just said)`

https://user-images.githubusercontent.com/36359331/195046456-156e0383-ad00-4e13-8333-f1abb530c3ff.mov
Solution

As componentDidUpdate lifecycle method runs and that is the place in my opinion to add a condition that if TooltipSense.isActive()  and this.state.isRendered is true execute the hideTooltip function which will handle the tooltip case itself.

 componentDidUpdate(prevProps) {

         if(TooltipSense.isActive() &&  this.shouldStartShowAnimation) {    //Added code
            this.hideTooltip()
        }

        if (this.props.windowWidth === prevProps.windowWidth && this.props.windowHeight === prevProps.windowHeight) {
            return;
        }

Video after fix:
https://user-images.githubusercontent.com/36359331/195055297-8abd9b98-ba3f-4a80-8402-a38a0e509892.mov
Note:

I didn't push the code cuz i think it would be much better if someone who has worked on this tooltip can give
this fix a quick look so that nothing breaks or unexpected happens. Thanks
cc: @parasharrajat

Could you please explicitly state the reason for tagging and ask questions? That user may not have the full context of the issue and also not enough time to go through it all.

I didn't push the code cuz i think it would be much better if someone who has worked on this tooltip can give
this fix a quick look so that nothing breaks or unexpected happens. Thanks

It doesn't matter at this point, but that's the issue we are trying to address here

##Action Performed:
Go to chat with someone
Go back from chat using back button and open chat again and go back.
Repeat this process sometimes and a tool tip will appear when back on chat screen
##Expected Result:
No tootip should appear on chats list screen.
##Actual Result:
Tooltip appear on chat list screen

I'm able to still see tooltip appears on the chat list. I think we should solve this here.

@Santhosh-Sellavel Fixed the issue, had to add the condition to checks if tooltip is active and didn't hide.
The reason for tagging explicitly is that i saw this tooltip components logic was mainly written and changed/refactored over time by you(now I'm afraid to tag again) and you might have the most knowledge about this component.
Apologies if this isn't the right way to approach someone who is not assigned to the issue.

@aneequeahmad did you mean to close this PR?

@roryabraham no i didn't, actually there were merge conflicts and sync the fork option here removed the 3 commits.
Resolved the merge conflicts just now, was testing before pushing. Pushing in a moment and reopening the the PR. Is this flow ok to resolve conflicts ?

It seems this PR removed a bunch of commits from the history and overwrite them.

@parasharrajat

😄 I have no issues with that. Sorry if I sounded rude.
I meant to say that asking direct questions while tagging can help the person easily catch up. Additionally, you can summarize the things which might be relevant to the question that you asked.

Oh i guess i didn't get it right at first, my mistake apologies.
Also, there were some merge conflicts in package.json and package-lock.json and the github resolved them by removing my own commits. I then just pulled and merged the latest Expensify:main branchin this PR.
You're right maybe cuz i fixed the other commented issues but after the merge the fix for tooltip hot hiding bug seems not to be working.

If you get stuck, you might be able to ask for help in #expensify-open-source

@roryabraham Thank you for mentioning the issue this PR is facing. I totally agree with you that internal resources are wasted like this in these simple kind of git things. This is the first PR of all my career(Startup career) that is facing these kind of unexpected issues. I'll later explain in depth why these issues occurred from the very start of this PR.
Having said that I would like to mention some points(also answers your query as well) that i noticed caused the delay for merging this simple PR. Please correct me if i'm wrong. Thanks

Only be a reasonable number of commits (somewhere between 1 and 5, probably)

There were only 2 commits that fixes the Bug: tooltip should only appear when there is mouse/cursor attached. All tooltips(almost all of them) were appearing.

Only be a small number of changed files

3 files were changed including package-json but now due to merge there are more than 100 files.

No conflicts with the main branch

There were no conflicts with the main when i requested review. As you know code is pushed daily and most prolly multiple people are working on the same file

All commits are signed

All commits are signed.

Automated tests to cover your changes

Added TooltipTest.js file that covers changes

Screen recordings to prove that you've manually re-tested the PR on all platforms

The PR fixes the problem described in the issue

Will add new screen recording for these.

@roryabraham Thank you for mentioning the issue this PR is facing. I totally agree with you that internal resources are wasted like this in these simple kind of git things. This is the first PR of all my career(Startup career) that is facing these kind of unexpected issues. I'll later explain in depth why these issues occurred from the very start of this PR.
I would like to mention some points(also answers your above comment as well) that i noticed caused the delay for merging this simple PR. Please correct me if i'm wrong. Thanks

Only be a reasonable number of commits (somewhere between 1 and 5, probably)

There were only 2 commits that fixes the Bug: tooltip should only appear when there is mouse/cursor attached. All tooltips(almost all of them) were appearing.

Only be a small number of changed files

3 files were changed including package-json but now due to merge there are more than 100 files.

No conflicts with the main branch

There were no conflicts with the main when i requested review. As you know code is pushed daily and most prolly multiple people are working on the same file

All commits are signed

All commits are signed.

Automated tests to cover your changes

Added TooltipTest.js file that covers changes

Screen recordings to prove that you've manually re-tested the PR on all platforms

Have to update screenshots.

The PR fixes the problem described in the issue

The PR fixed the issue that was 15 days ago like i mentioned here above in commit no be11bee

@roryabraham Thank you for mentioning the issue this PR is facing. I totally agree with you that internal resources are wasted like this in these simple kind of git things. This is the first PR of all my career(Startup career) that is facing these kind of unexpected issues. I'll later explain in depth why these issues occurred from the very start of this PR.
I would like to mention some points(also answers your above comment as well) that i noticed caused the delay for merging this simple PR. Please correct me if i'm wrong. Thanks

Only be a reasonable number of commits (somewhere between 1 and 5, probably)

There were only 2 commits that fixes the Bug: tooltip should only appear when there is mouse/cursor attached. All tooltips(almost all of them) were appearing.

Only be a small number of changed files

3 files were changed including package-json but now due to merge there are more than 100 files.

No conflicts with the main branch

There were no conflicts with the main when i requested review. As you know code is pushed daily and most prolly multiple people are working on the same file

All commits are signed

All commits are signed.

Automated tests to cover your changes

Added TooltipTest.js file that covers changes

Screen recordings to prove that you've manually re-tested the PR on all platforms

Have to update screenshots.

The PR fixes the problem described in the issue

The PR fixed the issue that was 15 days ago like i mentioned here above in commit no be11bee

Looks like we moved over here now

@roryabraham yes, that's correct clean PR like the requirements that you just mentioned above. Thank you for closing this one and mentioning the other


how to find the distance between two locations(lat,lng) in realm?

Questions:  How to find the distance between two location in realm?

Unfortunately this question is not related to Realm, but you can find an answer here: https://google.com/search?q=distancefromlocation


fix: decode string type for events

What I did
fixed string decoding in data for event logs
How I did it
removed the incorrect assumption that all dynamic types should be treated as bytes32
How to verify it
registry = Contract('0x50c1a2eA0a861A967D9d0FFE2AE4012c2E053804')
next(registry.NewVault.range(12_000_000, chain.blocks.height, 100_000)).event_arguments

before
{'token': '0x0bc529c00C6401aEF6D220BE8C6Ea1667F6Ad93e',
 'vault_id': 0,
 'vault': '0xE14d13d8B3b85aF791b2AADD661cDBd5E6097Db1',
 'api_version': HexBytes('0x0000000000000000000000000000000000000000000000000000000000000040')}

after
{'token': '0x0bc529c00C6401aEF6D220BE8C6Ea1667F6Ad93e',
 'vault_id': 0,
 'vault': '0xE14d13d8B3b85aF791b2AADD661cDBd5E6097Db1',
 'api_version': '0.3.2'}

Checklist

[x] All changes are completed
[x] New test cases have been added
[x] Documentation has been updated

Approved by @banteg


How to  add a new planner?

hi, i want to add my own planner to apollo planning module, is there some help documents about how to add new planner?

Currently two planners are supported in planning module. Please refer to how lattice planner is added.

@schietau  Hi ,Do you have any reference document to understand how to add new planner ?


NO-ISSUE: Version bump

This PR updates v1.0.11 version, adds new tag and bumps to v1.0.12-SNAPsHOT.
Change type

[ ] New feature
[ ] Bug fix
[ ] Unit tests
[ ] Integration tests
[x] CI
[ ] Documentation
[ ] Auto-generated SDK code

Impacted services

[x] Workflow Service
[x] Notification Service

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

@RichardW98 please take a look

looks good to me, Thank you Piotr!


Insufficient contrast ratio from dark theme

Insufficient text contrast ratio on text and components when browser using dark theme as Mistral is light theme only.
Example
ProseImg.vue from @bloggrify/core , see diff below.
Potential Fix
Override the prose components to remove the dark theme css classes.
<EMAIL_ADDRESS>See updated version in https://github.com/bloggrify/bloggrify-mistral/issues/3#issuecomment-2525028634

New potential fix:
Override app.vue with patch @bloggrify__core.patch:
diff --git a/app.vue b/app.vue
index 339a1b1dc243c8301739b71765794ee8260434a9..3d499934a5dac0813939de79d081cc615cce1e70 100644
--- a/app.vue
+++ b/app.vue
@@ -4,6 +4,7 @@
     </div>
 </template>
 <script setup lang="ts">
+import { useColorMode, useDark } from '@vueuse/core'
 import {useAnalytics} from '~/composables/useAnalytics'

 const config = useAppConfig()
@@ -47,6 +48,9 @@ useHead({
         },
     ],
 })
+
+useColorMode({initialValue: 'light'})
+useDark().value = false
 </script>
 <style lang="scss">
 @tailwind base;

I used lighthouse to understand the problem and apparently there is a problem of contrast in the footer.
I modified the footer to increase the level of gray and now it's 100 on lighthouse.
It should be ok now

Thank you, @hlassiege, for your fix implementation.
Unfortunately https://github.com/bloggrify/bloggrify-mistral/commit/c3bc9f85d2c2768fa185b10eacd76156eecef8c3 only treats one of the symptoms.
Request issue be re-opened by @hlassiege.
See opening comment's example https://github.com/bloggrify/bloggrify-mistral/issues/3#issue-2722363554, ProseImg.vue from @bloggrify/core is inherited as a layer. Therefore extended components and other components with dark css theming are still impacted.
Additional Examples

Change browser / OS to use dark mode
Open https://mistral.bloggrify.com/features
Run lighthouse report

See section Accessibility > CONTRAST

Background and foreground colors do not have a sufficient contrast ratio.

Failing Elements:

div.text-sm.text-center.text-gray-600.dark:text-gray-300.mt-1 × 2

Resulting component isProseImg

ProseCode's copy to clipboard is also impacted in page section #choose-your-language with dark theme copy button on the normally dark code area.

Table of contents:

Potential fix
Extending on from https://github.com/bloggrify/bloggrify-mistral/issues/3#issuecomment-2525028634, overriding app.vue has already proved to work. It can be implemented within this repo rather than as a patch.
While a potential fix for this theme may work, other themes that are missing a dark theme implementation will still be impacted. This may be a core module issue.
Conclusion
While the potential fix sheds some light on the situation, it raises the point that this issue may be outwith the theme's responsibility.
General Notes
I recommend implementing the fix in a PR rather than a direct commit. This approach allows for greater flexibility and ensures that the changes can be peer-reviewed. 😊

Ok. There is something I don't understand. I can't reproduce the issue.
I did switched my browser to dark mode

but the application is still in light mode and I don't have more contrast issue with and without this setting.
On your screenshot however, I see it's full dark. I suppose there is something different ?
About the fix itself, I'm not sure to understand exactly the code
useColorMode({initialValue: 'light'})
useDark().value = false

I understand the initial value will be light.
But does this mean that the dark mode is always disabled then ? That would be a problem for themes using dark mode

Ok. There is something I don't understand. I can't reproduce the issue. I did switched my browser to dark mode (I'm on Chrome, MacOS)
but the application is still in light mode and I don't have more contrast issue with and without this setting. On your screenshot however, I see it's full dark. I suppose there is something different ?

It appears the browser's theme does not update prefers-color-scheme, looks like the browser uses the OS theme mode. Emulate CSS media features will force regardless of OS theme but may not apply in lighthouse.

About the fix itself, I'm not sure to understand exactly the code
useColorMode({initialValue: 'light'})
useDark().value = false

The useColorMode tries to prevent the initialValue being 'auto' which will switch to 'dark'.
The useDark().value = false sets the the inverse of the 'dark' theme which is 'light'. This is the theme value until changed by a useDark() or equivalent.

I understand the initial value will be light. But does this mean that the dark mode is always disabled then ? That would be a problem for themes using dark mode

It does not prevent the dark mode pre se, but it does set it initially. This may be an unexpected behaviour as it will require to be change to take advantage of the user's preferred theme. As mistral has no dark theme this makes sense.
In the case of the patch / override, it only applies in the project that the patch / override originates from or is extended. For example, if mistral patches or overrides the core module, the core project is altered only when using the mistral theme or the mistral theme is also extended as it is not in itself extended also.

On your screenshot however, I see it's full dark. I suppose there is something different ?

@hlassiege, that is the :toc example in https://mistral.bloggrify.com/features#table-of-content-with-a-shortcode.

I tried the suggested fix

on epoxia and theme using dark mode. It's ok. The dark mode is still supported
on mistral. The problem with ProseImg is gone

I also fixed the table of content issue in dark mode


Improve Makefile

add more utilities to the "make analyze" command for analysis on all platforms

added .PHONY targets and fixed make test target for ARM arch


proposal: net: support Linux vsock sockets

Proposal Details
There exists basic support for AF_VSOCK sockets implemented in #19434.
Could support for such sockets please be added to the net module? For example net.FileListener can operate on TCP and UNIX sockets, but fails on vsock sockets.

What API would need to be added to the net package?  Thanks.

Sorry, I can't answer this. I don't know enough about how this should work.
I see separate implementations of sockaddr structs in syscall and x/sys/unix. So I assume right now, it would need the ones from syscall?
This means:

src/syscall/types_linux.go: map struct sockaddr_vm to RawSockaddrVM
src/syscall/syscall_unix.go (or _linux.go?): add SockaddrVM struct
src/syscall/syscall_linux.go: implement AF_VSOCK support in anyToSockaddr function.
src/net/file_unix.go: implement support in newFileFD and fileListener
src/net/vmlistener.go: implement a separate listener for vsock connection

Problem I see: vsock is linux specific, the net package code is unix specific.

Thanks.  The way the proposal process is intended to work is that people work out the details of how the libraries should change and open a proposal for that.  It doesn't work to ask us to figure things out--we don't know what you need.  I'm going to take this out of the proposal process.  Perhaps interested parties can work out the API changes, and then we can open a proposal for that.


layers: Remove redundant validation

Remove redundant validation from ValidateOrIncrementBoundObjects.
Change-Id: I98f9de491d83788cf0b19d4c606d239e1a915e58

Good call, Tony. I've made the change you suggested.

Took Chris' PR instead.


Rename examples.py to samples.py?

Naming consistency with the /sample directory?

Renamed to sample.py


Generic Host and Entity Framework Logging Configuration

I'm not sure if this is the proper place to log the issue...
I'm using the generic host builder to construct a host for my local service. Logging is configured with a logging level of Error across the board. This is working except in EF Core which is still logging at the info level. I suspect that EF is using a separate logger. Is there something different I need to do to tell EF to use the same log configuration as the rest of the application. Below is the code for my host:
        public static async Task Main(string[] args)
        {
            var host = new HostBuilder()
                .ConfigureHostConfiguration(configHost =>
                {
                    configHost.SetBasePath(Directory.GetCurrentDirectory());
                    configHost.AddJsonFile("hostsettings.json", optional: true);
                    configHost.AddEnvironmentVariables(prefix: "PREFIX_");
                    configHost.AddCommandLine(args);
                })
                .ConfigureAppConfiguration((hostContext, configApp) =>
                {
                    configApp.AddJsonFile("appsettings.json", optional: true);
                    configApp.AddJsonFile(
                        $"appsettings.{hostContext.HostingEnvironment.EnvironmentName}.json",
                        optional: true);
                    configApp.AddCommandLine(args);
                })
                .ConfigureServices((hostContext, services) =>
                {
                    // register ABS data context
                    var configuration = hostContext.Configuration;
                    services.AddDbContext<AbsContext>(options =>
                    {
                        options.UseSqlServer(configuration.GetConnectionString("AbsConnection"));
                    });

        <--- omitted for brevity --->

                    // register hosted applications
                    services.AddHostedService<ProviderUpdateService>();
                })
                .ConfigureLogging((hostContext, configLogging) =>
                {
                    configLogging.AddConsole();
                    configLogging.AddDebug();
                    configLogging.AddEventLog();
                })
                .Build();

            await host.StartAsync();
            await host.StopAsync();
            host.Dispose();

        }

Here is the logging level configuration from both of my appsettings.json files:
{
  "Logging": {
    "LogLevel": {
      "ARA":  "Information",
      "Default": "Error",
      "System": "Error",
      "Microsoft": "Error"
    }
  }
}

Finally here is what is getting logged.  Notice ARA is logging at info level like it should, but EF is also logging at info when it should be logging at error:

Firstly, make sure the appsettings are being picked up.
But if you want to test log levels pass these settings into AddConsole
            var settings = new ConsoleLoggerSettings();             settings.Switches.Add("Microsoft", LogLevel.Error);             settings.Switches.Add("Default", LogLevel.Information);

@dallancarr Thanks.  I have been able to verify that my appsettings are being picked up.  I'll try your suggesting about configuring within the AddConsole() call to see if the behavior is the same..

Found it...
needed to add
            builder.AddConfiguration(context.Configuration.GetSection("Logging"));
to my ConfigureLog() call.
Looks like the sample project for Generic Host needs it too...

There is the culprit
https://github.com/aspnet/Logging/blob/master/src/Microsoft.Extensions.Logging/LoggingServiceCollectionExtensions.cs#L45


Shortcut doesn't work when the checkbox or switch is focused

It's caused by the actual implementation of such components are input:
https://github.com/mui-org/material-ui/blob/6d62842d6f53c1726fc688131af0a16d561e3bd1/packages/material-ui/src/internal/SwitchBase.js#L33

Fixed d85f8a9194ed8c146666975d489bd335363fc391


How can I get a files list of last commit  by nodegit ?

In git command  I do such as
 git diff —name-only SHA1 SHA2

so how can I do the same thing by nodegit

Please have a look at this #861

I see  ( ^ - ^ )


Normalize data on initial load

In order to lookup a merchant by network_id, we have to do two types of checks (https://github.com/hackclub/yellow_pages/blob/main/lib/yellow_pages/merchant.rb#L9-L12):

String comparison
Array includes

This is because the YAML schema for network_id can be either a string or an array: https://github.com/hackclub/yellow_pages/blob/main/lib/yellow_pages/merchants.schema.json#L6-L7
To make lookups faster, we should normalize this data when initially loading it. Ideally, we have one giant hash with the keys being a single network_id. This means we may have duplicate hash values. We're trading space (memory) for performance.

Let's get rid of network_id https://github.com/hackclub/yellow_pages/issues/9

The schema is consistent now. network_ids is the only option

To make lookups faster, we should normalize this data when initially loading it. Ideally, we have one giant hash with the keys being a single network_id. This means we may have duplicate hash values. We're trading space (memory) for performance.

Can we also do this? I'd like to make lookups O(1) rather than O(n). lmk if you've got any questions here

Done!