Improving resting-state segmentation for EEGIP.

@gabe33033 @Scott-huberty Please have a look at this PR. Specifically, have a look at functions acareeg.eegip.process_events_london_resting_state
https://github.com/christian-oreilly/acareeg/blob/35b8c61baf8a0f23846846274887278eabb19187/acareeg/eegip.py#L156-L232
and acareeg.eegip.process_events_london_resting_state
https://github.com/christian-oreilly/acareeg/blob/35b8c61baf8a0f23846846274887278eabb19187/acareeg/eegip.py#L235-L279
Try to make sure you understand the logic of this code and agree with it. Feel free to ask me questions for what is not clear. We can have a call if you need me to walk you through it.

Actually, I forgot to add the description of the logic for the London case, so I will add it shortly.

OK. I added the doc.  @scott-huberty, you should find the description necessary to comment this in the MOP. I"ll prepare histograms of trial durations and post them here shortly.

@scott-huberty Regarding the impact of epoch duration on losing data, the following code shows you how to computes the total durations of available data when using epochs of 2s and 4s using acareeg.
import acareeg
from tqdm.notebook import tqdm
import pandas as pd
from pathlib import Path
import mne
import numpy as np

mastersheet = acareeg.eegip.get_mastersheet()
mastersheet = mastersheet.reset_index()[["Site", "ID", '6m_EEGLAB_QCR_File', '12m_EEGLAB_QCR_File', '18m_EEGLAB_QCR_File']]
mastersheet = mastersheet.dropna(how="all")
mastersheet["subject_no"] = [int(subject[-3:]) if isinstance(subject, str) else subject for subject in mastersheet["ID"]]

duration2 = []
duration4 = []
subjects = []
datasets = []
ages = []
for index, row in tqdm(list(mastersheet.iterrows())):
    dataset = row.Site.lower()
    for age in [6, 12, 18]:
        file_name = row[f"{age}m_EEGLAB_QCR_File"]
        if isinstance(file_name, str) and "qcr.se" in file_name:  # because .set is currently truncated for Washington
            subject = int(row.subject_no)
            age = int(age)
            bids_root="/media/christian/seagate/eegip/"
            eeg_path = Path(bids_root) / dataset / "derivatives" / "lossless" / f"sub-s{subject:03}" / f"ses-m{age:02}" / "eeg"
            eeg_path = list(eeg_path.glob("*_qcr.set"))
            if len(eeg_path) == 0:
                continue
            eeg_path = eeg_path[0]

            montage = mne.channels.make_standard_montage("GSN-HydroCel-129")
            raw = acareeg.eegip.preprocessed_raw(eeg_path, acareeg.eegip.line_freqs[dataset], montage,
                                                 apply_ica=False, verbose=False)

            events4 = acareeg.eegip.process_events_resting_state(raw, dataset, age, tmax=4)
            if events4 is None:
                continue
            epochs4 = acareeg.eegip.process_epochs(raw, dataset, age, events4, tmin=0, tmax=4, verbose=False)

            events2 = acareeg.eegip.process_events_resting_state(raw, dataset, age, tmax=2)
            epochs2 = acareeg.eegip.process_epochs(raw, dataset, age, events2, tmin=0, tmax=2, verbose=False)

            duration2.append(len(epochs2)*2)
            duration4.append(len(epochs4)*4)
            assert(duration4[-1] <= duration2[-1])

            subjects.append(subject)
            ages.append(age)
            datasets.append(dataset)

durations_df = pd.DataFrame(dict(duration2=duration2, duration4=duration4, subject=subjects, age=ages, dataset=datasets))

Now, the interval of confidence for a normally distributed variable is proportional to the standard error (se) around the mean, which is defined as follows:
se = std/sqrt(N)

with N being the sample size.
Thus, to reduce the interval of confidence (i.e., the level of noise on an averaged variable) by a proportion a,
you need to increase the sample size by a proportion b such that
a = se_2/se_1 = (std/sqrt(b*N))/(std/sqrt(N))  = 1/sqrt(b)

So that to cut the interval of confidence in 2, you need a sample size 4 time larger; to cut it in 3, you need a sample size 9 times larger, ...
Thus, if we apply this to our dataset:
print(f"Mean recording duration available with 2s epochs: {durations_df.duration4.mean():.4}")
print(f"Mean recording duration available with 4s epochs: {durations_df.duration2.mean():.4}")
print(f"Average loss by using 4s epochs instead of 2s: {((durations_df.duration2 - durations_df.duration4)/durations_df.duration2*100).mean():.4}%")

beta = durations_df.duration2.mean()/durations_df.duration4.mean()
print(f"How much (in %) can the interval of confidence on the mean be reduced by using 2s epochs instead of 4s? In average {(1-1/np.sqrt(beta))*100:.4}%")
print(f"{np.sum(durations_df.duration4 == 0)} records get dropped with 4s because they have no epochs of that size.")

we get
Mean recording duration available with 2s epochs: 107.9
Mean recording duration available with 4s epochs: 121.9
Average loss by using 4s epochs instead of 2s: 16.15%
How much (in %) can the interval of confidence on the mean be reduced by using 2s epochs instead of 4s? In average 5.927%
6 records get dropped with 4s because they have no epochs of that size.

@scott-huberty For the MOP... histograms of the trial duration before applying thresholds at 10 and 50s:

I think my job is done on that. I let you and @gabe33033 have a look at the code and when you are ok with it I can merge the PR so that we can all use this new segmentation.

@scott-huberty Regarding the impact of epoch duration on losing data, the following code shows you how to computes the total durations of available data when using epochs of 2s and 4s using acareeg.
import acareeg
from tqdm.notebook import tqdm
import pandas as pd
from pathlib import Path
import mne
import numpy as np

mastersheet = acareeg.eegip.get_mastersheet()
mastersheet = mastersheet.reset_index()[["Site", "ID", '6m_EEGLAB_QCR_File', '12m_EEGLAB_QCR_File', '18m_EEGLAB_QCR_File']]
mastersheet = mastersheet.dropna(how="all")
mastersheet["subject_no"] = [int(subject[-3:]) if isinstance(subject, str) else subject for subject in mastersheet["ID"]]

duration2 = []
duration4 = []
subjects = []
datasets = []
ages = []
for index, row in tqdm(list(mastersheet.iterrows())):
    dataset = row.Site.lower()
    for age in [6, 12, 18]:
        file_name = row[f"{age}m_EEGLAB_QCR_File"]
        if isinstance(file_name, str) and "qcr.se" in file_name:  # because .set is currently truncated for Washington
            subject = int(row.subject_no)
            age = int(age)
            bids_root="/media/christian/seagate/eegip/"
            eeg_path = Path(bids_root) / dataset / "derivatives" / "lossless" / f"sub-s{subject:03}" / f"ses-m{age:02}" / "eeg"
            eeg_path = list(eeg_path.glob("*_qcr.set"))
            if len(eeg_path) == 0:
                continue
            eeg_path = eeg_path[0]

            montage = mne.channels.make_standard_montage("GSN-HydroCel-129")
            raw = acareeg.eegip.preprocessed_raw(eeg_path, acareeg.eegip.line_freqs[dataset], montage,
                                                 apply_ica=False, verbose=False)

            events4 = acareeg.eegip.process_events_resting_state(raw, dataset, age, tmax=4)
            if events4 is None:
                continue
            epochs4 = acareeg.eegip.process_epochs(raw, dataset, age, events4, tmin=0, tmax=4, verbose=False)

            events2 = acareeg.eegip.process_events_resting_state(raw, dataset, age, tmax=2)
            epochs2 = acareeg.eegip.process_epochs(raw, dataset, age, events2, tmin=0, tmax=2, verbose=False)

            duration2.append(len(epochs2)*2)
            duration4.append(len(epochs4)*4)
            assert(duration4[-1] <= duration2[-1])

            subjects.append(subject)
            ages.append(age)
            datasets.append(dataset)

durations_df = pd.DataFrame(dict(duration2=duration2, duration4=duration4, subject=subjects, age=ages, dataset=datasets))

Now, the interval of confidence for a normally distributed variable is proportional to the standard error (se) around the mean, which is defined as follows:
se = std/sqrt(N)

with N being the sample size.
Thus, to reduce the interval of confidence (i.e., the level of noise on an averaged variable) by a proportion a,
you need to increase the sample size by a proportion b such that
a = se_2/se_1 = (std/sqrt(b*N))/(std/sqrt(N))  = 1/sqrt(b)

So that to cut the interval of confidence in 2, you need a sample size 4 time larger; to cut it in 3, you need a sample size 9 times larger, ...
Thus, if we apply this to our dataset:
print(f"Mean recording duration available with 2s epochs: {durations_df.duration4.mean():.4}")
print(f"Mean recording duration available with 4s epochs: {durations_df.duration2.mean():.4}")
print(f"Average loss by using 4s epochs instead of 2s: {((durations_df.duration2 - durations_df.duration4)/durations_df.duration2*100).mean():.4}%")

beta = durations_df.duration2.mean()/durations_df.duration4.mean()
print(f"How much (in %) can the interval of confidence on the mean be reduced by using 2s epochs instead of 4s? In average {(1-1/np.sqrt(beta))*100:.4}%")
print(f"{np.sum(durations_df.duration4 == 0)} records get dropped with 4s because they have no epochs of that size.")

we get
Mean recording duration available with 2s epochs: 107.9
Mean recording duration available with 4s epochs: 121.9
Average loss by using 4s epochs instead of 2s: 16.15%
How much (in %) can the interval of confidence on the mean be reduced by using 2s epochs instead of 4s? In average 5.927%
6 records get dropped with 4s because they have no epochs of that size.

This is awesome, it will be extremely useful!

@scott-huberty Regarding the impact of epoch duration on losing data, the following code shows you how to computes the total durations of available data when using epochs of 2s and 4s using acareeg.
import acareeg
from tqdm.notebook import tqdm
import pandas as pd
from pathlib import Path
import mne
import numpy as np

mastersheet = acareeg.eegip.get_mastersheet()
mastersheet = mastersheet.reset_index()[["Site", "ID", '6m_EEGLAB_QCR_File', '12m_EEGLAB_QCR_File', '18m_EEGLAB_QCR_File']]
mastersheet = mastersheet.dropna(how="all")
mastersheet["subject_no"] = [int(subject[-3:]) if isinstance(subject, str) else subject for subject in mastersheet["ID"]]

duration2 = []
duration4 = []
subjects = []
datasets = []
ages = []
for index, row in tqdm(list(mastersheet.iterrows())):
    dataset = row.Site.lower()
    for age in [6, 12, 18]:
        file_name = row[f"{age}m_EEGLAB_QCR_File"]
        if isinstance(file_name, str) and "qcr.se" in file_name:  # because .set is currently truncated for Washington
            subject = int(row.subject_no)
            age = int(age)
            bids_root="/media/christian/seagate/eegip/"
            eeg_path = Path(bids_root) / dataset / "derivatives" / "lossless" / f"sub-s{subject:03}" / f"ses-m{age:02}" / "eeg"
            eeg_path = list(eeg_path.glob("*_qcr.set"))
            if len(eeg_path) == 0:
                continue
            eeg_path = eeg_path[0]

            montage = mne.channels.make_standard_montage("GSN-HydroCel-129")
            raw = acareeg.eegip.preprocessed_raw(eeg_path, acareeg.eegip.line_freqs[dataset], montage,
                                                 apply_ica=False, verbose=False)

            events4 = acareeg.eegip.process_events_resting_state(raw, dataset, age, tmax=4)
            if events4 is None:
                continue
            epochs4 = acareeg.eegip.process_epochs(raw, dataset, age, events4, tmin=0, tmax=4, verbose=False)

            events2 = acareeg.eegip.process_events_resting_state(raw, dataset, age, tmax=2)
            epochs2 = acareeg.eegip.process_epochs(raw, dataset, age, events2, tmin=0, tmax=2, verbose=False)

            duration2.append(len(epochs2)*2)
            duration4.append(len(epochs4)*4)
            assert(duration4[-1] <= duration2[-1])

            subjects.append(subject)
            ages.append(age)
            datasets.append(dataset)

durations_df = pd.DataFrame(dict(duration2=duration2, duration4=duration4, subject=subjects, age=ages, dataset=datasets))

Now, the interval of confidence for a normally distributed variable is proportional to the standard error (se) around the mean, which is defined as follows:
se = std/sqrt(N)

with N being the sample size.
Thus, to reduce the interval of confidence (i.e., the level of noise on an averaged variable) by a proportion a,
you need to increase the sample size by a proportion b such that
a = se_2/se_1 = (std/sqrt(b*N))/(std/sqrt(N))  = 1/sqrt(b)

So that to cut the interval of confidence in 2, you need a sample size 4 time larger; to cut it in 3, you need a sample size 9 times larger, ...
Thus, if we apply this to our dataset:
print(f"Mean recording duration available with 2s epochs: {durations_df.duration4.mean():.4}")
print(f"Mean recording duration available with 4s epochs: {durations_df.duration2.mean():.4}")
print(f"Average loss by using 4s epochs instead of 2s: {((durations_df.duration2 - durations_df.duration4)/durations_df.duration2*100).mean():.4}%")

beta = durations_df.duration2.mean()/durations_df.duration4.mean()
print(f"How much (in %) can the interval of confidence on the mean be reduced by using 2s epochs instead of 4s? In average {(1-1/np.sqrt(beta))*100:.4}%")
print(f"{np.sum(durations_df.duration4 == 0)} records get dropped with 4s because they have no epochs of that size.")

we get
Mean recording duration available with 2s epochs: 107.9
Mean recording duration available with 4s epochs: 121.9
Average loss by using 4s epochs instead of 2s: 16.15%
How much (in %) can the interval of confidence on the mean be reduced by using 2s epochs instead of 4s? In average 5.927%
6 records get dropped with 4s because they have no epochs of that size.

This is awesome, it will be extremely useful!

FYI, here is a visual display of the distribution of the duration of resting-state when epoching with 1s windows

Same figure can be produced for other duration or for the raw duration (before rejection due to epoching or lossless artifacts).


Feature/add client tester

@arik-dig Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


Don't show error message if unable to load ayarc

ayarc is almost always expected to be loaded, error should be included if unable to load ayarc


Getting the element name from a collection

How do I extract Performance from the following?
var performances: Set<Performance>?

I have learned that {{ variable.typeName }} is not the answer.

How do I handle an array?


if child crashes then we should redo the stuff we did on first init

Specifically send it updated text again in case the file isn't saved on disk yet.

I'll close this if nothing weird happens anymore

will be done as a part of #51


[Doc] add table links to Information Schema

Signed-off-by: amber-create<EMAIL_ADDRESS>Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

@mergify backport branch-3.1

@mergify backport branch-3.0

@mergify backport branch-3.0

@mergify backport branch-2.5

@mergify backport branch-2.5


Cur Query Library - New Query - Top 50 Resource Movers

*Description of changes:
This query produces the top 50 moving resources by 1/ cost delta and 2/ change in percentage. The parameters have been adjusted for comparison of resources from three days prior and two days prior as CUR may take up to 48 hours to update all estimated charges. Additionally, this query pulls only resources with greater than $5 in unblended cost in order to reduce noise from resources which did not exist in one of the look back periods or spun up at the end of one of the look back periods. Adjust these parameters to suite your needs.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Taking a look


[release] Prepare v0.16.0-rc2

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Looks good - Thanks @oliviertassinari 👍


Internal resolution, add render distance, fog density

There's another fix available for this game (http://ps2wide.net/pc.html#sh3) which includes some configurable options for internal resolution + render distance  + fog density:
[MAIN]
int_width = 1280
int_height = 720

[MISC]
add_render_distance = 0.0 // original value 0.0;

[FOG]
fog_density = 672.0 // original value 448.000000;

I was wondering if these are features worth adding to sh3proxy if possible.

They can be added, although I am not sure whether they make sense:

All sane internal resolutions are provided by the game (having non power of two resolutions is an interesting idea, didn't test if d3d8 supports them properly though)
Render distance seems to be optimal, not sure why change it except for debugging
Fog density is adjusted automatically based on aspect rate (CorrectFog option)

I would like to see what other users think about adding these features.

I've been messing around with this fix. As a simple player I wouldn't know how to benefit from the first two option but fog adjust is interesting. I think he tried to have a better fog (by better I mean more complex fog like in SH2) by multiplying it's layers density. And it works. But there is a big catch: the thicker the fog gets the lesser you will see. First I've tried the fix's own values without touching anything. I couldn't see anything, in that kind of fog you will lose your sense of direction and get lost. I couldn't even see the road line I've been onto and I lost Heather herself completely in the fog when camera zoom out :) That's simply unplayable. Then I lower the values as much as I could -it seems he'd multiplied fog layers with 3, I tried with 2 and so on to get an acceptable rate; but when I did, it didn't look any different than the original fog. So I come to conclusion that the fog's problem is not it's density but it's quality. Otherwise the original fog is perfectly and cleverly calculated so you can have enough fog and you will be able to see what you need to see, nothing more, nothing less. The problem is it just looks pixelated and very square-ish on PC on high res monitors. I wonder if fog has it's own resolution like shadows and FOV?  That would be the real answer to fog problem.
I like how this fix renders the static elements in their correct aspect ratio instead of stretching the image. Things like title menu, inventory screen and FMV's are all 4:3. It was a nice feature to add to sh3proxy imo.

Yeah, the author of the fix released some videos demonstrating what can be done with the fog, which is quite interesting (particularly the No Fog seems helpful in some ways):
Silent Hill 3 No Fog Test
Silent Hill 3 Custom Fog Test
Silent Hill 3 Custom Fog Test №2

I wish this was for SH2. It is known that SH2 PC has way less fog than the original PS2 version. It could use that.

Hey, Markeron, there is a ps2 version available on his website.
http://ps2wide.net/pc.html#sh2

Yeah, I've seen that. He added it later. It's great.

Note that the fog fix is also compatible with other SH2 patches (e.g. sh2proxy).


Having a dropdown with the buttons

Hi,
I have a map application with several 'jump to [city]' buttons. Is there a way I can combine these into a dropdown menu? So the user will see a 'cities' button, hover or click on it and then be presented with a list of cities.
Thanks

that's outside the scope of this plugin, but the source for the easyBar could be a decent jumping off point.

I'll put a bounty on this if it helps.  I want to give the user the ability to export the data in multiple formats, and having mutliple buttons is ugly.  A dropdown, or a fan-out (similar to drawing tools) would be ideal.


Progress bar shown when internet connection off in attendee fragment

Describe the bug

The progress bar is shown even before clicking on the register button when the internet connection is off.
To Reproduce

Keep the internet connection off.
Go to the attendee fragment.

Expected behavior

A Snackbar or toast to be displayed showing "Please check your internet connection".
Logs

Screenshots

Smartphone Info:

Device
Lenovo P2

Android Version
Nougat 7.0

Additional context

@nikit19 @liveHarshit @iamareebjamal  your views?
Would you like to work on the issue?

[x] Yes
[ ] No
Other:

Are you still working on this?

Yes @angmas1


Php 7.4 - Class 'ScraperAPI\Exception' not found - Undefined index headers

Error 1:
Class 'ScraperAPI\Exception' not found
Class 'ScraperAPI\Exception' not found {"exception":"[object] (Error(code: 0): Class 'ScraperAPI\Exception' not found at /vendor/scraperapi/sdk/src/Client.php:106)
Error 2:

Any updates on this issue, is it fixed?

Same problem.


Add a quicklab readme

test this please

CI is failing

test this please

ok to test

test this please


Removing expvar keys since it's heart performance and it's unused.

benchmark                               old ns/op       new ns/op     delta
Benchmark_T1000_P5000_Matches-4<PHONE_NUMBER>      10704746      -99.59%
Benchmark_T1000_P5000_NoMatches-4<PHONE_NUMBER>      10024400      -99.60%
Benchmark_T100_P5000_Matches-4          33235249        13528192      -59.30%
Benchmark_T100_P5000_NoMatches-4        35301480        2377025       -93.27%
Benchmark_T10_P5000_Matches-4           3999232         2545317       -36.35%
Benchmark_T10_P5000_NoMatches-4         4069072         2356547       -42.09%
Benchmark_T10_P500_CountTask-4          4308417         556166        -87.09%
Benchmark_T10_P500000_CountTask-4       171780120       154546757     -10.03%
Benchmark_T1000_P500-4<PHONE_NUMBER>2     15440082      -99.91%
Benchmark_T1000_P500000_CountTask-4<PHONE_NUMBER>4     318064303     -98.35%

benchmark                               old allocs     new allocs     delta
Benchmark_T1000_P5000_Matches-4         12084          10060          -16.75%
Benchmark_T1000_P5000_NoMatches-4       12083          10061          -16.73%
Benchmark_T100_P5000_Matches-4          1264           1073           -15.11%
Benchmark_T100_P5000_NoMatches-4        1266           1055           -16.67%
Benchmark_T10_P5000_Matches-4           179            155            -13.41%
Benchmark_T10_P5000_NoMatches-4         178            155            -12.92%
Benchmark_T10_P500_CountTask-4          388            336            -13.40%
Benchmark_T10_P500000_CountTask-4       428            385            -10.05%
Benchmark_T1000_P500-4                  32184          27166          -15.59%
Benchmark_T1000_P500000_CountTask-4     32253          27199          -15.67%

benchmark                               old bytes     new bytes     delta
Benchmark_T1000_P5000_Matches-4         1818384       1752617       -3.62%
Benchmark_T1000_P5000_NoMatches-4       1818384       1752675       -3.61%
Benchmark_T100_P5000_Matches-4          1413715       1408155       -0.39%
Benchmark_T100_P5000_NoMatches-4        1413848       1406806       -0.50%
Benchmark_T10_P5000_Matches-4           1373087       1372209       -0.06%
Benchmark_T10_P5000_NoMatches-4         1372988       1372138       -0.06%
Benchmark_T10_P500_CountTask-4          157302        155606        -1.08%
Benchmark_T10_P500000_CountTask-4       149610906     149609495     -0.00%
Benchmark_T1000_P500-4                  1433632       1272199       -11.26%
Benchmark_T1000_P500000_CountTask-4     150886920     150723879     -0.11%

Tested against master, with edgeBufferSize of 1000 (default value)

@nathanielc As written in #360 -

I think there is something strange with the updateKeys/benchmark, it's only callers are NewStatistics and DeleteStatistics, and the benchmark shouldn't time them.
But I will submit PR to remove it, the only usage of the keys is in doLocked:
func (v *Map) doLocked(f func(expvar.KeyValue)) {
    for _, k := range v.keys {
        f(expvar.KeyValue{k, v.m[k]})
    }
}

I don't understand why not to use "m" already?

I didn't find any good reason for not using v.m for iterating the map in doLocked, so I switched to iterating the map directly.
I still don't understand why this change caused a dramatic change in this benchmark, since updateKeys shouldn't be called unless it's NewStatistics/DeleteStatistics

It's breaking becuase:
3310 tick/cmd/tickdoc/main.go:133: not enough arguments in call to markdown.NewRenderer^M

@nathanielc  ?

And it looks that updateKeys is called a lot in this profile because of Drain - whom calls DeleteStatistics eventually.

@yosiat I fixed the build failure, rebase and it should pass.
+1 on green.

@nathanielc done ;)


Platform: make stdint module implicit on Windows

This makes the stdint module implicit which repairs the ability to build some components.  In order to accomplish this, we need to potentially break the fragile Swift build system.  Due to the incorrect handling of compilers we need some workarounds to support cross-compilation.  This removes the injected system header paths when building on Windows to ensure that the clang resource headers are not following the system headers which breaks the modules as the clang resources are dependent on the system headers when running in hosted mode.

@swift-ci please smoke test


Update papers to 3.4.16,555

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

sorry I miss typed the version in the previous one... big fingers. I think I need a coffee.


use version from package.json

Can't we just use the version directly from package.json or am I missing something?

Good point! Could make this remove any -... suffix of the version? Sometimes if a release fails we'll publish a new one called 0.27.2-1 or 0.27.2-2 for example.

the reasoning behind the current system is that its simple and explicit. and the goal is to automate it away anyway. but i'm not opposed to this -- as long as it's still easy to understand so we don't publish a broken version to npm accidentally (e.g. one that parses the version wrong at install time and can't find installation candidates)

Updated and rebased onto latest master

I merged this on my fork while working on https://github.com/atom/electron/issues/1488; only needing to touch one file makes the automating a little easier.

@ralphtheninja THANKS!

:+1: My pleasure!


feat(testing): Add GCE Metadata Server component

Adds a testing component for a GCE Metadata Server.
This will enable the integration testing of GCP platform bootstrapping for VMs. Right now, there is no configurability provided, but this can be expanded in the future to provide configuration of the test server to match testing needs.
This is a follow-on PR to: https://github.com/istio/istio/pull/25264. Future PRs will include the use of this component in the setup, etc.
[ X ] Test and Release

@douglas-reid: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
f273bcc3f897f447014d0b784945935a2301dd3d
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
f273bcc3f897f447014d0b784945935a2301dd3d
link
/test lint_istio

unit-tests_istio
f273bcc3f897f447014d0b784945935a2301dd3d
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
f273bcc3f897f447014d0b784945935a2301dd3d
link
/test unit-tests_istio

lint_istio
4ea9124933604554995322ff496588ee2f53ad34
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
4ea9124933604554995322ff496588ee2f53ad34
link
/test lint_istio

unit-tests_istio
4ea9124933604554995322ff496588ee2f53ad34
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
4ea9124933604554995322ff496588ee2f53ad34
link
/test unit-tests_istio

lint_istio
36cca3600c7b52465c6d918616c6eb2fccd94365
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@douglas-reid: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
f39b02ceaa9e4d1abeac4d0f9bb1adff84c19bc7
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-distroless-k8s-tests_istio


[Font] Implement get_char_from_glyph_index function.

Usually unnecessary, but might be useful for CharFX in some cases. See https://github.com/godotengine/godot/issues/73985

Thanks!


paddle.ex: fix get/1 and get!/1 specs

Add clauses accepting and returning Paddle.Class.t to avoid Dialyzer warnings
Dialyzer was giving me this warning:
ElixirLS Dialyzer: The function call will not succeed.

Paddle.get(%LDAP.User{
  :cn => nil,
  :displayName => nil,
  :dn => nil,
  :givenName => nil,
  :mail => _,
  :objectClass => nil,
  :sn => nil,
  :uid => nil,
  :userPassword => nil
})

breaks the contract
(dn()) :: {:ok, [ldap_entry()]} | {:error, search_ldap_error()}

Where %LDAP.User{} is a struct implementing the Paddle.Class protocol.
This PR fixes that warning.

Looks good to me, thank you :heart:


Mergeability for shapetrackers

Functions to convert a shapetracker to a tensor of indices + Boolean tensor of masks.  In this representation, it's easy to check if the shapetracker is single-view:

Check if the mask is rectangular (only 1's in a region of the form $\prod_i [a_i, b_i]$ and 0's elsewhere)
Calculate the strides by shifting by 1 in each direction in the mask=1 region, and then  the offset is also determined.
Check if the strides are consistent by checking equality between your shapetracker's tensor rep and the tensor rep corresponding to the single-view shapetracker with those strides, offset, and mask.

Next steps:

Add rectangular mask check
Fix errors showing up when checking for equality of tensors
Clean up code + typing
Figure out whether this representation is better computationally than existing shapetracker class

This should be a provably correct version of merge_views (modulo figuring out offsets, and testing).  The only problem is that it depends on contiguous Tensors, so I can't just replace the existing merge_views impl (would create a circular dependency).
One other interesting thing -- to_tensor is really a function of a Node, so probably useful elsewhere if we keep using symbolic.

Seems to be an improvement over existing merge_view code.  No known merge-view regressions, although running the fuzzer is slightly slower.    Also, I haven't checked Tensors with symbolic values or bounds.   Example regression fuzz test output showing improvements:

new simplify better than old
OLD: ShapeTracker(views=(View(shape=(6, 6, 4), strides=(24, -8, 1), offset=28, mask=((0, 6), (1, 4), (0, 4)), contiguous=False), View(shape=(14,), strides=(1,), offset=86, mask=None, contiguous=False)))
NEW: ShapeTracker(views=(View(shape=(14,), strides=(1,), offset=78, mask=((0, 2),), contiguous=False),))
new simplify better than old

new simplify better than old
OLD: ShapeTracker(views=(View(shape=(5, 6, 7, 7), strides=(30, 5, 0, 1), offset=0, mask=((0, 5), (0, 6), (1, 5), (0, 5)), contiguous=False), View(shape=(5, 35, 2), strides=(294, 7, 1), offset=12, mask=None, contiguous=False)))
NEW: ShapeTracker(views=(View(shape=(5, 35, 2), strides=(0, 0, 0), offset=0, mask=((0, 0), (0, 0), (0, 0)), contiguous=False),))

new simplify better than old
OLD: ShapeTracker(views=(View(shape=(3, 5, 6), strides=(0, 40, 1), offset=0, mask=((2, 3), (0, 5), (0, 6)), contiguous=False), View(shape=(1, 30), strides=(0, 1), offset=30, mask=None, contiguous=False)))
NEW: ShapeTracker(views=(View(shape=(1, 30), strides=(0, 0), offset=0, mask=((0, 0), (0, 0)), contiguous=False),))

new simplify better than old
OLD: ShapeTracker(views=(View(shape=(9, 4, 6), strides=(6, 0, 1), offset=0, mask=((0, 9), (1, 2), (0, 6)), contiguous=False), View(shape=(18, 3, 1, 6), strides=(12, 0, 0, 1), offset=0, mask=None, contiguous=False)))
NEW: ShapeTracker(views=(View(shape=(18, 3, 1, 6), strides=(0, 0, 0, 0), offset=0, mask=((0, 0), (0, 0), (0, 0), (0, 0)), contiguous=False),))

simplify2 better than simplify 0.40%
simplify2 worse than simplify 0.00%

Bad running time, going to reopen this as a reference implementation for the fuzzer.

Bad running time, going to reopen this as a reference implementation for the fuzzer.

I would expect this depending on the complexity of the mask. In the worst case scenario you are essentially copying (n+(n-1)/2) elements with this approach.
You could improve the average case by representing contiguous elements and masks in compressed form with slicing.
It does seems useful for a correctness proof though.


Fix order of arguments for container entrypoint

The arguments for the container entrypoint need to be appended
rather than prepended.  Otherwise they get reversed in config.json
and the container fails to start.
Signed-off-by: Rob Woolley<EMAIL_ADDRESS>

wrong meta-overc.


About RPC over HTTP and *.proto

Why was RPC over HTTP chosen in proto files?
I ask because I'm not able to connect to faraday with generated client. I tried C# and also JavaScript. And I tried same way as it is described here: https://github.com/lightningnetwork/lnd/blob/master/docs/grpc/javascript.md but of course with proto for faraday.
Exception is thrown on any RPC method call. E.g.
client.ChannelInsights({}, new Metadata(), {}, function (response) {
	console.log(response)
})

For JS the error is:

For C# the error is:

And it is not connectivity issue because from client (my PC) I can see opened port 8465:

Or if I'm using proto files incorrectly then please show me how to generate client in languages such as JS or C#. Thank you.

This should work the same way as in lnd. Can you post the full JS code, especially the part where you load the TLS certificate and create the connection?

It is in TypeScript but TS is compiled into JS anyway.
import { credentials, Metadata, loadPackageDefinition } from 'grpc';
import * as fs from 'fs';
import Description from './src-gen/grpc-node'
import * as protoLoader from '@grpc/proto-loader';

process.env.GRPC_SSL_CIPHER_SUITES = 'HIGH+ECDSA'

const loaderOptions = {
	keepCase: true,
	longs: String,
	enums: String,
	defaults: true,
	oneofs: true
};

const packageDefinition = protoLoader.loadSync('faraday.proto', loaderOptions);

const macaroonFile = fs.readFileSync('faraday.macaroon');
const macaroon = macaroonFile.toString('hex');

const cert = fs.readFileSync("tls.cert");
const sslCreds = credentials.createSsl(cert);

const macaroonCredenetials = credentials.createFromMetadataGenerator(function (_, callback) {
	const metadata = new Metadata()
	metadata.add("macaroon", macaroon)
	callback(null, metadata)
})

const combinedCredentials = credentials.combineChannelCredentials(sslCreds, macaroonCredenetials);

const descriptor = loadPackageDefinition(packageDefinition) as Description

const client = new descriptor.frdrpc.FaradayServer("IP:PORT", combinedCredentials);

client.ChannelInsights({}, new Metadata(), {}, function (response) {
	console.log(response)
})

I can prepare repo with my solution, if you wish, so you can see the behavior.

Sorry for the delay on this. I just tried this myself and ran into the same error.
Debugging this a bit further (running GRPC_VERBOSITY=DEBUG node index.js), I found out it's a problem in the grpc NodeJS library:
D1130 11:16:11.730372465   18690 security_handshaker.cc:176] Security handshake failed: {"created":"@1606731371.730356864","description":"Cannot check peer: missing selected ALPN property.","file":"../deps/grpc/src/core/lib/security/security_connector/ssl_utils.cc","file_line":118}
I think we've run into this as well somewhere, but I don't know if we ever found a fix for it. Will see if I can find out more.

c# client has the same issue.

I tried switching from Grpc.Core to Grpc.Net.Client in an attempt to get this working but no joy. With that client I get:

Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while server offers only version fallback

I also tried upgrading faraday's grpc server to google.golang.org/grpc v1.35.0 but also no joy.
Something seems up with the faraday gRpc setup because the exact same code works fine with the lnd grpc server, with both  Grpc.Core and Grpc.Net.Client but in neither case can I connect to the Faraday gRPC interface.

Thank you for further investigating on this!
The hint that it works with the same version on lnd but doesn't on faraday was what gave me the idea what the problem could be.
Was able to reproduce the error and then fix it by switching over TLS handling to gRPC instead of using the default library's TLS listener: #106.


Feature/strictly separate unit and integration tests

Coverage increased (+0.1%) to 98.225% when pulling cbb4d0229ad4b215ba7287e34e6377e6ba4063ef on feature/strictly-separate-unit-and-integration-tests into d7f836a8367d9e22938845a4095acf85695c025d on master.


Add foundations for CMake support

We start by creating the top-level CMakeLists.txt file, following the
modern CMake guide (https://cliutils.gitlab.io/modern-cmake/).
We already have a build/ directory, so we'll use cmake/build for our
build folder.  We add this to .gitignore (using a * so as to support
multiple build folders).
We update the release instructions so as to keep the version number in
sync, and the installation instructions so as to explain how to use
CMake.
Helps #215.

@geoffviola, see review comment from @Cazadorro.


FIX: Make scipy.optimize.zeros run under PyPy

This is a bugfix to support scipy.optimize.zeros under PyPy.
As described in http://doc.pypy.org/en/latest/cpython_differences.html#c-api-differences,
in PyPy "assignment to a PyTupleObject is not supported after the tuple is used internally,
even by another C-API function call."
The type of the scipy_zeros_parameters::args field is therefore changed from
tuple to list in PyPy.

thanks, merged


Add CoC page

@argyleink I totally winged the look of a content page here. PTAl and let me know what you’d wanna change (or put something into XD and I will adjust accordingly).
This is pretty high priority.

@jakearchibald I did the move. I guess this is good to go?


Hikvision binary sensor alarm pir not working

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.51.2
Python release (python3 --version):
Python 3.5.2
Component/platform:
Hikvision binary sensor
Description of problem:
It won't add the sensor for alarm in I/O
Expected:
Add a new binary sensor when alarm is triggered on the camera.
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:
Sensor for motion works OK.
Error inte HA log.
2017-08-26 23:42:39 ERROR (Thread-23) [pyhik.hikvision] Problem finding attribute: 'IO'
2017-08-26 23:42:39 ERROR (Thread-23) [pyhik.hikvision] Problem finding attribute: 'IO'
2017-08-26 23:42:40 ERROR (Thread-23) [pyhik.hikvision] Problem finding attribute: 'IO'
2017-08-26 23:42:40 ERROR (Thread-23) [pyhik.hikvision] Problem finding attribute: 'IO'
2017-08-26 23:42:40 ERROR (Thread-23) [pyhik.hikvision] Problem finding attribute: 'IO'
2017-08-26 23:42:41 ERROR (Thread-23) [pyhik.hikvision] Problem finding attribute: 'IO'
2017-08-26 23:42:41 ERROR (Thread-23) [pyhik.hikvision] Problem finding attribute: 'IO'
2017-08-26 23:42:41 ERROR (Thread-23) [pyhik.hikvision] Problem finding attribute: 'IO'

IO is not currently a supported sensor type.  During original testing I found that IO sensors were reported differently across different camera types and as a result were difficult to properly track in the underlying library.
It's something i'd be open to looking into again if you have a specific use case.  Please open a issue on my pyHik repository with your feature request and we can talk more there.

Sounds Good. Just opened an issue. =)

Me too!


Add "Open in Orchest" button

Hi! Juan Luis from Orchest here 👋🏽 Just adding an "Open in Orchest" button so folks can easily import this cool example to their instances (same as https://github.com/rsesha/deep_autoviml_pipeline/pull/2 😄)

Thanks for the input Juan!


Getting Error: Usage of<EMAIL_ADDRESS>is no longer supported

I recently upgraded to Ghost V5. SInce then, I am getting this error while trying to install liebling.

I'm wondering what version of the theme you have installed? The theme replaced those helpers since version 2.0.0 (June, 2022), if you search in the latest version you can see the new helpers.
I would suggest you to download the latest version from the releases page.

I will close this issue for now, please feel free to reopen it if needed.


Cannot find name 'require'

Hi, angular-cli update to @angular/cli: 1.0.0-rc.1      An error has occurred .  pls help
npm
npm install crypto-js
npm install @types/crypto-js
typings install dt~crypto-js
app.component.ts
import { Component } from '@angular/core';
var CryptoJS = require('crypto-js');
ng serve
ERROR in C:/Users/Jino/Documents/ngProject/slb/src/app/app.component.ts (3,16): Cannot find name 'require'.)

I wouldn't encourage importing packages using require, but if you need to make sure you've added node to the types array in .angular-cli.json.

@filipesilva
I can not find any information about an types array in .angular-cli.json
Did you mean the types array in tsconfig.json or do you have any further information?

@sven42 types goes in the tsconfig.json

Why not copy an example of what you mean exactly for those of us getting the same error? Have no idea what you are talking about but getting the same error

Apologies, it indeed meant tsconfig.json instead of .angular-cli.json. More specifically, src/tsconfig.app.json. It has a "types": [] entry, where you can add more types (such as "node"). Again though, I don't suggest doing it.

I don't want to use require either. Is there a better way for importing a localization-file (.json), which is included in a npm-package?

@filipesilva Why do you recommend against using require and what is a better alternative ?

in src folder open tsconfig.app.json and add
"compilerOptions": {
...
"types": [
"node"
]
},


Drop Python 2.6 support

Yesterday marks 3 years since the last release of Python 2.6! 🎉
To celebrate, I'm attempting to drop support for it from 156 prominent Python packages (one for every week it's past end-of-life)--including this one!
I've tried my best to remove as much 2.6-specific cruft as I can, but at the very least, this PR will remove the 'Programming Language :: Python :: 2.6' trove classifier from this projects setup.py.

As much as I think Python 2.6 needs to die, there is absolutely no gain from doing this except locking out users.

@di , I suggest you change your strategy. If you dont know why people are still using Python 2.6, you are hurting open source users by removing Python 2.6 support from libraries such as this. Most end-users dont install itsdangerous, or even know it exists.

I'm leaning more towards removing support tbh, though there should be a reasonably long deprecation phase (previously announced) instead of a spontaneous reaction to the anniversary of its death.

@jayvdb I think you're right, thanks for the comments, and sorry for the noise!

Comments welcome on https://github.com/pallets/itsdangerous/issues/93.


Orphan blocks are leaked on flush

The blocks which are not yet a part of the chain are considered orphan and stored in mapOrphanBlocks which is periodically flushed during sync. The problem is that it's storing naked pointers which aren't deleted on flush which should cause a memory leak (haven't checked in Valgrind yet).
Change this to store a shared pointer until the block has been serialized to disk and detached from the orphan map.

@tomasbrod @skcin I'm torn between the following fixes:

shared_ptr: Correct and safe implementation but the change is larger and sticks out like a sore thumb compared to all the raw pointers in the system.
raw ptr: Matches current implementation, small and isolated fix but still using unsafe raw pointers.

Thoughts?

but the change is larger and sticks out like a sore thumb compared to all the raw pointers in the system.

Would this introduce instability?

@grctest I'd say no and that we want to move towards shared_ptr anyway, but implementing it in just one spot makes that particular spot not behave the way you have come to know or expect. For example:

void getValue1(string name, string& value)`
void getValue2(string name, string& value)`
void getValue2(string name, string& value)`

Hypothetical refactoring of getValue3 into:

string getValue3(const string& name)`

makes it correct, but now it's inconsistent. It's pretty much the same here :)
I'm leaning towards making the small implementation now and doing a more broad switch to shared_ptr "in the future".

This is still issue.

Submitted a pull requests.
I'm just getting started with Github so I messed up with the first commit which included more than it should have. I think I successfully removed it.

#261

https://github.com/gridcoin/Gridcoin-Research/pull/609

Fixed.


Egg 'docker_image' Blank

The docker_image variable of an Egg resource is blank. I found that renaming the variable to dockerImage fixed the issue.

Thank you for your feedback,


Generate a sitemap.xml file automatically

What should change
Adds logic to create a sitemap.xml file automatically from the source files, respecting the noindex page data setting.
Identifying a user need
Search engine optimisation and navigation support for a sitemap for documentation sites.

Raised in wrong repo


Stump: Add new data structure called Stump

Stump is a minimum required data needed for validating the accumulator
proofs. The advantages after that it doesn't have any of the
complexities that pollard has and is much simpler code-wise.
It seems that a user can keep track of proofs separately while using
stump to verify and update the accumulator state. Worth looking at as
it'll be much simpler than pollard.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

77 of 88 (87.5%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+8.3%) to 77.48%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

stump.go
77
88
87.5%

Totals

Change from base Build<PHONE_NUMBER>:
8.3%

Covered Lines:
1359

Relevant Lines:
1754

💛  - Coveralls


Set MYSQL_HOST and MYSQL_PORT in environment.yml

This was missing even though it was already documented in DOCKER-INFO.md.

Do we need these env vars? Maybe users are thinking about changing them and do not realise that they are not changing anything.

Yes I need them, that's why I made the PR :-)

Should we add a comment above these variables? just a hint that these variables are just for the application and doesn't change anything?

I don't see what you mean. The same applies for all MYSQL_* env variables. What's special about MYSQL_HOST and MYSQL_PORT?

See https://hub.docker.com/_/mysql/
These variables controls the mysql container.

What's special about MYSQL_HOST and MYSQL_PORT?

As far as i understand @mblaschke, the problem with the MYSQL_HOST env variable is, that changing it wouldn't affect anything, the mysql container is still only reachable by using the host name mysql, as far as you do not change its container service name in the docker-compose.yml accordingly.
Users could oversee this easily and think of a faulty behaviour.
Apart from that, when changing the container service name of e.g. the mysql container, some of the helper scripts would break currently, while they use the hardcored service name mysql.
In case of MYSQL_PORT I don't see a use case why this would/should change. What's your use case?
A reason of defining this variables would be to use env vars in the TYPO3 config all the way and not having a mix of variables (db, password, user) and hardcoded settings (host, port).
But nevertheless I wouldn't recommend defining this two variables in the environment.yml without further handling of the mentioned concerns.

Thanks, I see. Was not even aware of this, but it looks like an interesting feature, so we should not touch it! :-)
The reason why I came up with this suggestion is because I'm thinking about using Helmuts dotenv-connector in my projects.
So how about this: We add new variables which are not parsed anywhere (so they are in fact read-only). Suggestion:
DATABASE_USER=$MYSQL_USER
DATABASE_PASSWORD=$MYSQL_PASSWORD
DATABASE_NAME=$MYSQL_DATABASE
DATABASE_HOST="mysql"
DATABASE_PORT=3306

@hhoechtl Nope please don't merge this! Like I wrote above, it should be solved using additional environment variables. My suggestion for this is DB_* but let me know what you prefer...

(Reopening after I accidentially deleted the feature branch.)


Antipodes don't match when calculated numerically

import scipy.optimize as opt
import pyproj
g = pyproj.Geod(ellps='WGS84')

latlona = 52.5252, 13.37173, 43.85

def antipods(dst):
    # positive branch
    antipods.a1 = g.fwd(latlona[1], latlona[0], latlona[2], dst*1e3)
    # negative branch
    antipods.a2 = g.fwd(latlona[1], latlona[0], latlona[2], -dst*1e3)
    (az12, az21, dist) = g.inv(antipods.a1[0], antipods.a1[1], antipods.a2[0], antipods.a2[1])
    antipods.dist = dist*0.001
    return dist*0.001

r = opt.minimize_scalar(antipods,bounds=[15000,25000],method="bounded",tol=1e-6)

print("Great Circle Distance to Antipodes:",r['x'])
print("Distance between calculated Antipodes",antipods.dist)

print("Antipode Positive",antipods.a1[1], antipods.a1[0])
print("Antipode Negative",antipods.a2[1], antipods.a2[0])
print("Antipode Analytic",-latlona[0],",",-180+latlona[1])

Problem description
When calculating the antipodes numerically, there's quite a huge gap between the two numerically calculated Antipodes. In the specific example above it's about 25 km. That's only about 0.12% of the great circle distance, but in absolute numbers I still found it quite a big distance.
Is this "just" a numerical accuracy lack?
Or is it a systematic modelling error?
Expected Output
I'm not aware of the exact modelling, but I expected that the two antipodes match within reasonable accuracy, and here I mean something like much less than 1 km to the analytical one.
The error varies slightly with the azimuth, but in all cases it is still visible.
My original goal was to plot a full 360° great circle, and there I figured out that after a full circle the great circle doesn't match the start point anymore, but has a decent offset.
Environment Information
pyproj info:
pyproj: 3.3.0
PROJ: 8.2.1
data dir: /usr/share/proj
user_data_dir: ~/.local/share/proj
PROJ DATA (recommended version): 1.8
PROJ Database: 1.2
EPSG Database: v10.041 [2021-12-03]
ESRI Database: ArcMap 12.8 [2021-05-06]
IGNF Database: 3.1.0 [2019-05-24]
System:
python: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
executable: /usr/bin/python3
machine: Linux-5.15.0-107-generic-x86_64-with-glibc2.35
Python deps:
certifi: 2020.06.20
pip: 22.0.2
setuptools: 59.6.0
Cython: None
Installation method
Ubuntu 22.04 python3-package

@cffk, apologies for bothering you. However, I think you are best suited to answer this question. Thank you!

With a few exceptions, geodesics are not closed curves on an ellipsoid.  If you follow a geodesic a full circuit around the world, you arrive at a point that falls short of the starting point by a distance on the order of f a where f is the flattening of the ellipsoid and a is its equatorial radius.
Naturally, there's a similar offset following a geodesic halfway around the world in opposite directions.
The simplest way to compute the antipodal point is to add ±180° to the longitude and to change the sign of the latitude.  But I understand that this probably isn't your goal.

@cffk does it mean that the shortest distance between a point and its antipode in an ellipsoid is not a geodetic?

Then, if I understand correctly, the problem is the azimuth of both geodesics, one going through the north pole and another going through the south pole, are not the same. In the example it is using the same azimuth, 43.85, in both directions. Am I right? (Because both geodesics must have the same length)

"Up to a point, Lord Copper!"  For an oblate ellipsoid, the two shortest geodesics connecting antipodal points have azimuths 0deg and 180deg.  These geodesics over of the poles (obviously).  There are two shortest geodesics connecting some points which are nearly antipodal (the points have to be on opposite circle of latitude) and, in this case, the two azimuths are supplementary angles.  (In general, these geodesics do not go over the pole.)


clean up GLAccountBuilder, following SpotBugs (FINERACT-702)

Which one are you merging first. This or #682 ?
@vorburger thanks very much for taking the time to review and augment the spotbug integration work. I am grateful.

Which one are you merging first. This or #682 ?

#682 just merged, this one was actually just an extension with 1 more additional commit over that one. There's no real good way to do this better in GitHub (that I know of), so what I "imply" (but should say more clearly?) when I raise a PR like this one for review is to manually click on the last commit of such a PR (in the Commits tab) in review that, instead of everything on the Files changed tab (or use that Changes from drop down on Files changed to review only last commit instead of from all commits).

@vorburger thanks very much

You are the one to thank, this (that we've finally properly adopted SpotBugs here) is amazing!
If this small PR is OK with you, just go ahead and merge it (use Rebase and merge to avoid the merge commit, because #684 is "parallel"). -- PS: I hope this doesn't fail in Integration Test again due to FINERACT-820 - as it's Sunday...  if it does, we really should figure out how to fix that problem.. or ask on list if anyone would like to take that on.

PS: I hope this doesn't fail in Integration Test again due to FINERACT-820 - as it's Sunday... if it does, we really should figure out how to fix that problem.. or ask on list if anyone would like to take that on.

It did, this is really annoying.. are you willing to just review and merge this ignoring that LoanReschedulingWithinCenterTest failure? Or motivated to investigate how that could be fixed properly once and for all? I'll drop an email to the list as well.

This looks good merging now.


materialgram: init at <IP_ADDRESS>

Description of changes
Add https://github.com/kukuruzka165/materialgram

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] Fits CONTRIBUTING.md.

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

 @Aleksanaa

Okay but I may not update it often. Durov told me my telegram account is very precious and fragile 😅

Sorry I forgot this. I've lost my telegram account. @NickCao could you help with this?

@Aleksanaa, Are you going to merge or not? Almost two months passed

@incycledream

Are you going to merge or not? Almost two months passed

it is currently broken with latest nixpkgs master branch, maybe locked with #331396 afterwards

While at it could fellow telegram users test https://github.com/NixOS/nixpkgs/pull/331396 out? Especially around voice/video calling since I've reworked tg_owt a bit.

Knock-knock, where's the merge? Telegram Desktop got already merged, I can't wait for materialgram in Nix to ditch Flatpak (Even considering that fact I was the person who got materialgram into Flathub). By the way, I can also be a co-maintainer of this package if required

@incycledream could you help me to test it? I'm a little afraid of my telegram account disappearing again. Just nixpkgs-review pr 321531 and run the executable.

@Aleksanaa

@incycledream could you help me to test it? I'm a little afraid of my telegram account disappearing again. Just nixpkgs-review pr 321531 and run the executable.

I got an error while building
warning: The interpretation of store paths arguments ending in `.drv` recently changed. If this command is now failing try again with '/nix/store/dnc2xnz6d2279iiaalx9bsysd1hwb2dd-materialgram-<IP_ADDRESS>.drv^*'
Running phase: qtPreHook
@nix { "action": "setPhase", "phase": "qtPreHook" }
Running phase: unpackPhase
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking source archive /nix/store/kf7na7f3lymipzbirhnpyf4s9dbqj7kv-source
source root is source
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "patchPhase" }
applying patch /nix/store/3irbx4ih9kcwwfdpsv9i6n96dn0pa1q2-macos.patch
patching file Telegram/SourceFiles/platform/mac/overlay_widget_mac.mm
patching file Telegram/lib_base/base/platform/mac/base_battery_saving_mac.mm
patching file Telegram/lib_webrtc/webrtc/platform/mac/webrtc_environment_mac.mm
patching file Telegram/lib_webview/webview/platform/mac/webview_mac.mm
Hunk #1 succeeded at 342 with fuzz 2 (offset 28 lines).
Hunk #2 succeeded at 702 (offset 42 lines).
applying patch /nix/store/8paj2qx3abvp2mpd1y0llbknqir6ssvf-scheme.patch
patching file Telegram/SourceFiles/core/application.cpp
Hunk #1 FAILED at 421.
1 out of 1 hunk FAILED -- saving rejects to file Telegram/SourceFiles/core/application.cpp.rej

Here's the rej file:
--- Telegram/SourceFiles/core/application.cpp
+++ Telegram/SourceFiles/core/application.cpp
@@ -421,7 +421,6 @@ void Application::run() {

 void Application::autoRegisterUrlScheme() {
 	if (!OptionSkipUrlSchemeRegister.value()) {
-		InvokeQueued(this, [] { RegisterUrlScheme(); });
 	}
 }

Here's the application.cpp:
https://snips.sh/f/j4SnXH2nVY?r=1

Even with removed patch, building fails with 300 000 lines of log.
/nix/store/lbk30k56awz9vz9qpid93fkjns0xwlhd-gcc-wrapper-13.3.0/bin/g++ -DBWE_TEST_LOGGING_COMPILE_TIME_ENABLE=0 -DHAVE_WEBRTC_VIDEO -DNDEBUG -DNO_MAIN_THREAD_WRAPPING -DQT_DEPRECATED_WARNINGS_SINCE=0x051500 -DQT_IMPLICIT_QCHAR_CONSTRUCTION -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_KEYWORDS -DRTC_DISABLE_TRACE_EVENTS -DRTC_ENABLE_H265 -DRTC_ENABLE_VP9 -DTGCALLS_USE_STD_OPTIONAL -DWEBRTC_APM_DEBUG_DUMP=0 -DWEBRTC_APP_TDESKTOP -DWEBRTC_DUMMY_AUDIO_BUILD -DWEBRTC_ENABLE_PROTOBUF=0 -DWEBRTC_HAVE_DCSCTP -DWEBRTC_HAVE_SCTP -DWEBRTC_INCLUDE_INTERNAL_AUDIO_DEVICE -DWEBRTC_LIBRARY_IMPL -DWEBRTC_LINUX -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=1 -DWEBRTC_OPUS_SUPPORT_120MS_PTIME=1 -DWEBRTC_OPUS_VARIABLE_COMPLEXITY=0 -DWEBRTC_POSIX -DWEBRTC_USE_BUILTIN_ISAC_FLOAT -DWEBRTC_USE_H264 -DWEBRTC_USE_PIPEWIRE -DWEBRTC_USE_X11 -I/build/source/Telegram/ThirdParty/tgcalls -I/build/source/Telegram/ThirdParty/tgcalls/tgcalls -isystem /nix/store/2bw54660ndcc79c6zjm5g98slkpks814-tg_owt-0-unstable-2024-08-02-dev/include/tg_owt -isystem /nix/store/2bw54660ndcc79c6zjm5g98slkpks814-tg_owt-0-unstable-2024-08-02-dev/include/tg_owt/third_party/libyuv/include -O3 -DNDEBUG -std=gnu++20 -Wno-deprecated-volatile -Wno-ambiguous-reversed-operator -Wno-deprecated-declarations -Wno-unqualified-std-cast-call -fPIC -fno-strict-aliasing -pipe -Wall -Wextra -Wno-unused-parameter -Wno-switch -Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-sign-compare -Wno-deprecated -MD -MT Telegram/CMakeFiles/lib_tgcalls.dir/ThirdParty/tgcalls/tgcalls/LogSinkImpl.cpp.o -MF Telegram/CMakeFiles/lib_tgcalls.dir/ThirdParty/tgcalls/tgcalls/LogSinkImpl.cpp.o.d -o Telegram/CMakeFiles/lib_tgcalls.dir/ThirdParty/tgcalls/tgcalls/LogSinkImpl.cpp.o -c /build/source/Telegram/ThirdParty/tgcalls/tgcalls/LogSinkImpl.cpp
In file included from /build/source/Telegram/ThirdParty/tgcalls/tgcalls/LogSinkImpl.cpp:3:
/build/source/Telegram/ThirdParty/tgcalls/tgcalls/Instance.h:17:7: error: conflicting declaration of template 'template<class T> struct rtc::scoped_refptr'
   17 | class scoped_refptr;
      |       ^~~~~~~~~~~~~
In file included from /nix/store/2bw54660ndcc79c6zjm5g98slkpks814-tg_owt-0-unstable-2024-08-02-dev/include/tg_owt/rtc_base/checks.h:59,

log

@oluceps @Aleksanaa
Here you go, it works! I'm so happy that I've even made a selfie with materialgram on NixOS. I need to propose some changes though (thanks to @dvtfl and her friend),  but I'm gonna do that tomorrow

@oluceps @Aleksanaa package.nix
this version works, I think the only changed part is the version
tested on x86_64-linux (cc @dvtfl @incycledream), aarch64-darwin

why does this pr has 11.by: package-maintainer label?

@oluceps can you update pr name?

why does this pr has 11.by: package-maintainer label? does this

That may bcz I'm a package maintainer

https://github.com/NixOS/nixpkgs/pull/334732 whoops

Result of nixpkgs-review pr 321531 run on x86_64-linux 1

1 package built:

materialgram

I'll test voice+video+screenshare calls on aarch64-darwin
[546/1410] Building CXX object Telegram/CMakeFiles/td_ui.dir/SourceFiles/statistics/chart_widget.cpp.o
[547/1410] Building CXX object Telegram/CMakeFiles/td_ui.dir/SourceFiles/ui/boxes/auto_delete_settings.cpp.o

Result of nixpkgs-review pr 321531 run on x86_64-linux 1

1 package built:

materialgram


Proposal: do not bind mount /etc/hosts, /etc/hostname and /etc/resolv.conf --net=host or add support for --add-hosts when --net=host

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->
Output of docker version:
Client:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:40:36 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:40:36 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 17
 Running: 3
 Paused: 0
 Stopped: 14
Images: 505
Server Version: 1.11.0
Storage Driver: btrfs
 Build Version: Btrfs v3.19.1
 Library Version: 101
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 4.4.4-1.el7.elrepo.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 31.29 GiB
Name: ceph-master
ID: EMX6:4HDA:SBCH:VKGA:5E3M:S3JX:F24B:NTQM:ASFX:DDGG:A57H:GXRR
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.):
physical
Steps to reproduce the issue:

docker run --rm -it --net=host busybox mount | grep /etc/hosts
docker run --rm -it --net=host --add-host test:<IP_ADDRESS> busybox grep test /etc/hosts

Describe the results you received:

output: "/dev/sdb2 on /etc/hosts type btrfs (rw,seclabel,relatime,ssd,space_cache,subvolid=257,subvol=/root/var/lib/docker/containers/a46f7eb4e109b6736ba18c4a04bff662c85aff594b837b564793b158fd981148/hosts)"
/etc/hosts is a bindmount to a docker managed host file.

output:"docker: Error response from daemon: Conflicting options: custom host-to-IP mapping and the network mode."

Describe the results you expected:

/etc/host is not a bind mount
or
--add-hosts work if docker bind mounts /etc/hosts when --net=hosts

Additional information you deem important (e.g. issue happens only occasionally):
binding mounting /etc/hosts is required for docker managed networking but is not a requirement when
when host networking is used. bind mounting /etc/hosts prevents many tools such as sed and ansible which do atomic file updates by creating an temp file and then preform an atomic rename as this action is not supported for bind mounted files.
when in --host=net mode the expected behavior is that all docker networking is disabled for this container and host networking is used. in this case ideally  /etc/hosts, /etc/hostname and /etc/resolv.conf  would not be bind mounted into the container so that they can be configured externally using tools such as sed/ansible. this is a problem when using docker to test
deployment scripts that are intended to run on physical machines where the script is expected to update these files.

See a related discussion on this PR https://github.com/docker/docker/pull/22408 (https://github.com/docker/docker/pull/22408#issuecomment-220082584)

Looks like this should be fixed by #22408 (I haven't tried it)

In my opinion bind-mounting /etc/resolv.conf is wrong in all cases. You might always want to change the contents of the file which is generally done by replacing, not rewriting, as rewriting doesn't ensure consistency at all times. In many systems /etc/resolv.conf is a symlink and it works well. The best way would be to either bind-mount or copy the docker resolv.conf elsewhere in the system, preferably read-only, and just symlinked.
That way you would (1) allow detection that /etc/resolv.conf is still linked to the docker-originated resolv-conf file, (2) allow replacing of /etc/resolv.conf properly with another symlink or a new regular file in the standard atomic way, and (3) keep the original contents available.

For those man who searched and jumped here, after I check Docker related docs, I have to say, Unfortunately, Docker doesn't support disable this behaviour, you might need to use Podman.
Check: https://github.com/containers/podman/pull/2747


Update Linode LKE driver 0.0.3 -> 0.0.4

Is your feature request related to a problem? Please describe.
There is a new release of this driver.  I have personally tested it and can create a 1.23 cluster with it.  (note that I was trying to work around creating a 1.22 cluster in #37372 )
Describe the solution you'd like
Simply bump version assuming it passes any tests you have.
Describe alternatives you've considered
I guess waiting for 0.0.5?

@jaredkipe I'm still waiting on this too, but I did figure out a workaround that might help. If you go to the Cluster Drivers page, you can edit the Linode LKE driver under the actions menu and change the following:
Download URL: https://github.com/linode/kontainer-engine-driver-lke/releases/download/v0.0.4/kontainer-engine-driver-lke-linux-amd64
Checksum: 5609314fe7ff7339a7c8292738d36ccf5a25460f79ca094db72eb6ccf722bc27
I pulled those values from here, and once it finished downloading and activating I was able to create LKE clusters on v1.22+

@jaredkipe I'm still waiting on this too, but I did figure out a workaround that might help. If you go to the Cluster Drivers page, you can edit the Linode LKE driver under the actions menu and change the following:
Download URL: https://github.com/linode/kontainer-engine-driver-lke/releases/download/v0.0.4/kontainer-engine-driver-lke-linux-amd64
Checksum: 5609314fe7ff7339a7c8292738d36ccf5a25460f79ca094db72eb6ccf722bc27
I pulled those values from here, and once it finished downloading and activating I was able to create LKE clusters on v1.22+

It's worked!


Cant see any upcoming dates/events

System Information:

Version: 2.6
Language: sv
Timezone Offset: +01:00
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36

What steps will reproduce the problem?

Installed the plugin
Conected with google

What is the expected result?
See coming events in the app.
What happens instead?
Just show if something happends today
Screenshot URL:
Logs:

[2016-02-24T17:15:25.101Z] Creating bug report.

https://github.com/manastungare/google-calendar-crx/wiki/Troubleshooting


The new official update 212 broken this mod

Hello,
My game updated to receive Mistland and the mod no longer works at all, I think you already know, it needs to be updated, thanks :)

When you open an issue you need to provide a detailed description of the problem including error messages, screenshots, and any other relevant info like what version of the game you are using and what mods and what versions of those you are using.

Ok thank you :D


Colors are wrong.

Maybe this theme depends on a specific terminal theme?

+1

Erm, maybe colors are not that right at all but your issue isn't that. Please take a look at this vi.stackexchange thread:
http://vi.stackexchange.com/questions/2436/why-does-the-same-color-scheme-look-better-in-gvim-than-cygwin/2451#2451
And as I said on this repo description, it works only on GVim (and maybe on MacVim), and you shouldn't expect it to work on terminal Vim. But hey, PR are welcome if you want to make it work! :smiley:


No file data passed when using multipart/form-data file upload

Attempting to upload files via a POST request no file data is passed.
Expected outcome
What should happen?
Would expect to see the boundary data and content-length for the attached files, e.g.
content-type: multipart/form-data; boundary=----WebKitFormBoundaryNnwvcXQcxXlK1Cng--
content-length: XX
------WebKitFormBoundaryNnwvcXQcxXlK1Cng--
Actual outcome
What happened?
Get no file/boundary data, e.g.
content-type: multipart/form-data
content-length: 0
Versions
App: <IP_ADDRESS>6-stable
Chrome: 56.0.2924.87
Platform: Mac OS X (10_12_3)
Steps to reproduce

Create a POST request
Attach a file or files to the request
Hit send and check the request headers

Ah my bad, I see it is an issue with chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=688100

Hi,
Thank you for issue report.
That's right. I reported this bug some time ago. However, I started working on a workaround. I think it will be beneficial for you because you'll have more control over multipart data.
As soon as I finish it I'll make a new release. Unfortunately, it requires changes in the core of the application and the way how the app handing and sending data so It's not that simple to change it.
I'm doing my best to make it as soon as possible. But at the same time, I don't want to break the app.
Expect update rather sooner than later.
Thanks

Please refer to #945 for more information.
I am closing this as a duplicate.


failed to load dll error

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/create
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Please provide more information about yout issue


Update codelists fields.json and schematrons

Various updates to codelists, fields.json, schematron rules, and corresponding adjustments in notice examples.
See individual commits for details.
SDK Analyzer fails because it needs to be updated for the new properties in fields.json.

SDK Analyzer has been updated, it now reports errors related to things that have not been updated yet (notice types, labels, ...).
So to be expected for now.


Monorepos 2/2

For full monorepo support we don’t only need to handle repositories that are monorepos themselves with multiple package.jsons. we also need to better support the releases of monorepos into Greenkeeper. We do support it already, but each monorepo-sub-package creates its own issue/PR. Each of which could fail until the last sub-package gets merged.
Instead, we should open a single issue/PR per set of monorepo-sub-packages for a single package.json file.
The strategy here should be the following:

we detect that a given registry-change is for a package that is part of a monorepo
if we don’t already have a registry-change doc in our npm database for all other packages in that monorepo: do not do anything.
if we already have a registry-change doc for the same version for all other monorepo-sub-packages: create a branch or group branches for all packages in that monorepo release version.

First stab at an implementation here: https://github.com/greenkeeperio/greenkeeper/compare/feat/monorepo-receive

What is the current strategy to detect packages that are published from a monorepo? I didn't find the current state of that discussion, sorry.

Sorry, I failed to explain that here :) — The proposal for now is to hardcode this. (sketch here): https://github.com/greenkeeperio/greenkeeper/compare/feat/monorepo-receive#diff-b57a797b16d6e2c1e52ec7e5ada1e205R55
This would make it easy for the community to help keep this up to date.

Bit of an update on the sketch implementation:

we decided to make the decision whether to run create[-group]-version-branch in handle-registry-change, that way we avoid making that decision N times.
we need to handle an error condition where a monorepo group changed (and we wait in vain for the update of a package that got deleted), before we had a chance to update our definitions. To resolve this case, we deploy the new definitions and issue a mock registry-change event to hooks, that then runs the happy path.

maybe we just give ourselves a setInterval job of “current monorepo releases”, that get retried every hour or so, in case of an error, so we don’t have to do anything manually. Would also help with GKE, which needs to run hands-off cc @rmehner.

we outsource the monorepo definitions into its own module, say greenkeeperio/monorepo-definitions, that the community can help contribute to going forward.

it’d be nice if we maybe can deploy this separately, so that we don’t have to restart our service to get the new definitions live, but that can wait for a later iteration.

Closing in favour of https://github.com/greenkeeperio/greenkeeper/pull/760


Check Attestations indexing on the frontend

We have Karma adopting the DAO-IP3 and we need to make sure we have that indexing working
This was previously worked on for ONTOCHAIN

From today: when we submit an attestation, it does work, but the API server that was pulling the attestations was hosted by Mendes, and that server is not returning anything, and Rashmi has no way to debug it. On the backend server though, the flow for submitting reputation attestations does currently work.
Do we need the frontend? YES. The 3rd and final milestone of #100 requires having a frontend.
Next step: copy the current frontend, deploy a DAOIP-3 compliant schema(s), and add ability to display EAS attestations. That should satisfy the milestone for #100.

Sure feel free to move issue to #100 and close it. If you want this to be
reviewed in the strike team calls make sure to move to high priority.
On Mon, Dec 11, 2023 at 12:11 PM amanwithwings @.***>
wrote:

For future reference, this doc has the schemas used by Karma:
https://docs.google.com/document/d/1jSAZV8mnjdyYFtH5XH6aRN9hVIbY5hdyHCdZIYlDqS4/edit#heading=h.67m9i8ttvdpu
I don't think they were deployed with DAOIP-3 in mind so we will need to
suggest upgrades. Let's start the review process.
TO-DO: Disco has a "Drops" feature, which comes with a set of predefined
schemas (attendance, beta user, certificate of completion,, etc.)
corresponding to DAO contributions. We need to check with them to
understand where these attestations are written, whether they are intended
for public consumption, etc. I will take the initiative.
@thelastjosh https://github.com/thelastjosh, since this issue comes
under #100 https://github.com/metagov/daostar/issues/100, maybe we
should move this discussion there?
—
Reply to this email directly, view it on GitHub
https://github.com/metagov/daostar/issues/179#issuecomment-1850507436,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHA5PBBL6FYPIBT5XFIXN3YI45FTAVCNFSM6AAAAAA7WLFCC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJQGUYDONBTGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
http://www.joshuatan.com/research/

Moved to issue #100


Slow scrolls ignore last item in list

This will likely be resolved when NodeListManager tests are added.
Update: This appears to be a problem with the addNodes method

This is fixed, but not very elegantly. Once the tests are done, I can refactor it to be nicer.


Updated version in podspec and changelog

Description
Updated version in podspec and changelog for the 1.0.0 release
How to test
Nothing to test
Merging
Automatic
Issues

 Release


Update data-classification-overview.md

Edited prerequisites based on https://opdhsblobprod04.blob.core.windows.net/contents/e0993bf6e82e4fa8ac18b48839521869/2ce5e803079c3427c011efbce08b900a?sv=2018-03-28&sr=b&si=ReadPolicy&sig=KAG1lGSeWNpMVjfNAkfb1pKjGDpk8kuCyiMNPbZE%2BpA%3D&st=2020-08-10T19%3A40%3A49Z&se=2020-08-11T19%3A50%3A49Z

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/2568

@chrfox Please merge this PR. Thanks.

@msbemba - The link you included at the start of this PR is bad, I don't know where you got your information from.  I have queried the owning PM and will update as necessary

Thank you @chrfox I got it from docs.microsoft.com - https://docs.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance
The link that has a PDF file for Detailed Microsoft 365 Compliance Licensing Comparison
Thanks
Sri


filter arg not supported by Relays variables

example query
  initialVariables:{
    userSearch: 'user@email'
  },
  fragments: {
    query: () => Relay.QL`
      fragment on Viewer{
        userSearch(filter: {EmailSearch: $userSearch}, limit: 5) {
          firstName
          lastName
        }
      }
    `,
  }

This will not work as Relay variables are only supported as top-level arguments.
This would work:
  initialVariables:{
    userSearch: 'user@email'
  },
  fragments: {
    query: () => Relay.QL`
      fragment on Viewer{
        userSearch(email: $userSearch, limit: 5) {
          firstName
          lastName
        }
      }
    `,
  }

Should the filter params be moved to top level and mark sort and limit as specials.. ?

Nope. It should be in filter! It is clear, and avoid mess of args.
Use filter in such way.
  initialVariables:{
    filter: {
       userSearch: 'user@email'
    }
  },
  fragments: {
    query: () => Relay.QL`
      fragment on Viewer{
        userSearch(filter: $filter, limit: 5) {
          firstName
          lastName
        }
      }
    `,
  }

Ah! Why did i not think of that! :O


Short circuiting invalid context file in context.go

Does above
Removes old fix for component list as this covers that
more easily
Does some breakup of functions of context.go along the way.

Signed-off-by: Mohammed Zeeshan Ahmed<EMAIL_ADDRESS>What is the purpose of this change? What does it change?

Was the change discussed in an issue?
#1486

How to test changes?

Go into a directory where there is no .odo file and try odo app list or odo component list

/meow

Will add more tests once people are ok with flow

@cdrage it seems to be like it already is as far as context.go is concerned. What is important is shifting to making use of it

/cc @anmolbabu @girishramnani
Anything else?

Could we have e2e tests with the new framework? Suggestions @kadel

I am not sure if we want to do this right now. Lets setup separate prs to move all the tests over properly

Could we have e2e tests with the new framework? Suggestions @kadel

I am not sure if we want to do this right now. Lets setup separate prs to move all the tests over properly

Anyway we have stable e2e test and only effort will be migrate them to new structure. So separate pr would be fine.

/retest

Interesting fail
/retest

Cluster problem
/retest

/retest

/lgtm

/retest

/hold Ci failure needs to be fixed

/hold

there was an actual issue in the test
/cc @girishramnani

/hold cancel

/lgtm


Home APP cannot find the server

Hey,
Now we have begun the broker as well as the server. Unfortunately, ext. with the Devices cannot combine the Home. We have added the sample Devices in accordance with sample to project. In the NodeJs log we receive mistake that the need "Debug". . . is not found. If you can give us here please a tip, or to the test her complete project Folder as a high-level store ZIP. Thank you very much!
Best regards
Frank

It will be great if you could attach some screens and more detailed log

First error on MAC if i run the command "make install":

I fixed this in the guide:
make install-mac
will work :-)

Thank you for quick reply :) this works!

Could you please send the link, where I could download the current Hap-JS Version, which you already test ?

Your next step is :
make configure
https://github.com/netonjm/HapSharp/#setup-guide

okay, I get the following error:

Could we continue the conversation over:
https://gitter.im/mono/HapSharp

Ok, the problem was you were downloading the project and not cloning the solution, then git was not detecting your folder synching submodules. I will add this to the guide


Query a binary format (BSON, CBOR, MessagePack, UBJSON)

Is it possible to serialize a json document as, say, a BSON document and then extract fields out of the BSON document directly?
For example, the mongodb c++ driver offers functions for getting fields out of BSON documents. Is there something similar?

Right now, you first need to parse the binary value before you can access a specific value:
auto j = json::from_bson(x);
auto v = j["my_key"];


Setup CI server

Would be really nice to have travis CI, shippable, circle CI, appvovey, or anything that build this project upon pull request

agreed :)

done


Updating for Modules

This is tied to https://github.com/prebid/Prebid.js/pull/1177 -- updates the "how-to" adapter docs for the new approach.
Also converted 'adaptor' to 'adapter' and changed the jekyll {site.github.url} to {site.baseurl}, which makes running jekyll locally much better.

Updated with the comments from the review.

Hey @bretg, this is great stuff! Thanks for writing this up.  Really appreciate it.


[ADAM-1328] Rename Transform to TransformAlignments.

Resolves #1328.

Coverage decreased (-0.1%) to 81.784% when pulling 12d624cb75f413debf6c67df46bc5b1cef50aa5c on fnothaft:issues/1328-rename-transform-alignments into 0dd09b258dda051dea7b10d2e79658fafd235197 on bigdatagenomics:master.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1991/Build result: FAILURE[...truncated 16 lines...] > /home/jenkins/git2/bin/git rev-parse origin/pr/1521/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a --contains 689e93078b8ef1991429f3457a569e05c1a3e02b # timeout=10 > /home/jenkins/git2/bin/git rev-parse remotes/origin/pr/1521/merge^{commit} # timeout=10Checking out Revision 689e93078b8ef1991429f3457a569e05c1a3e02b (origin/pr/1521/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f 689e93078b8ef1991429f3457a569e05c1a3e02bFirst time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result SUCCESSADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result SUCCESSNotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Jenkins, retest this please.

Coverage decreased (-0.1%) to 81.784% when pulling 12d624cb75f413debf6c67df46bc5b1cef50aa5c on fnothaft:issues/1328-rename-transform-alignments into 0dd09b258dda051dea7b10d2e79658fafd235197 on bigdatagenomics:master.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1992/Build result: FAILURE[...truncated 16 lines...] > /home/jenkins/git2/bin/git rev-parse origin/pr/1521/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a --contains 689e93078b8ef1991429f3457a569e05c1a3e02b # timeout=10 > /home/jenkins/git2/bin/git rev-parse remotes/origin/pr/1521/merge^{commit} # timeout=10Checking out Revision 689e93078b8ef1991429f3457a569e05c1a3e02b (origin/pr/1521/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f 689e93078b8ef1991429f3457a569e05c1a3e02bFirst time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result SUCCESSADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result SUCCESSNotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

https://github.com/bigdatagenomics/adam/blob/master/scripts/jenkins-test#L221 also needs a change

Thanks @heuermh ; just fixed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1994/Build result: FAILURE[...truncated 16 lines...] > /home/jenkins/git2/bin/git rev-parse origin/pr/1521/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a --contains 0b21d34cad7c8be40c8918101a7f7fbed4b0a7b7 # timeout=10 > /home/jenkins/git2/bin/git rev-parse remotes/origin/pr/1521/merge^{commit} # timeout=10Checking out Revision 0b21d34cad7c8be40c8918101a7f7fbed4b0a7b7 (origin/pr/1521/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f 0b21d34cad7c8be40c8918101a7f7fbed4b0a7b7First time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILURENotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Coverage decreased (-0.2%) to 81.823% when pulling 0f9f2910ea11d31681f57dbc5aada89bc56657a5 on fnothaft:issues/1328-rename-transform-alignments into 18191f95fed08ed952dd6d96f8dea620e1449cfc on bigdatagenomics:master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1995/
Test PASSed.

@heuermh can you merge?

I was thinking of pinging folks downstream about this one and #1532 to make sure the CLI changes don't cause too much trouble.  I'll do that tomorrow.

Thank you, @fnothaft!


Create Posts “20220920-infix-to-postfix-conversion”

Automatically generated by Netlify CMS

👷 Deploy Preview for monetaboot processing.

Name
Link

🔨 Latest commit
33f1a08b31ea54247036dd2047ae29fde83aedc1

🔍 Latest deploy log
https://app.netlify.com/sites/monetaboot/deploys/63292d575bc79f000856c912


Add cross-var package and use in example-install command

Use cross-var to make this running on Windows and macOS both.
Resolve: #128

Codecov Report

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

@@          Coverage Diff          @@
##           master   #127   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files         116    116
  Lines        2184   2184
  Branches      408    408
=====================================
  Hits         2184   2184

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 18d71fb...176f757. Read the comment docs.


[BUG]: How to use wistia link in react native video?

Version
6.1.2
What platforms are you having the problem on?
Android
Architecture
Old architecture
What happened?
https://alcatrazz-627.wistia.com/medias/42nh9qefdc
how do use this Wistia link in React native video?
will it work if I pass the source?
Reproduction
repository link
Reproduction
Step to reproduce this bug are:
pass above link in source

https://googlethatforyou.com?q=How to use wistia link in react native app%3F
Seriously, I think you need to integrate this API to retrieve video url https://docs.wistia.com/reference/get_medias


New dice stay visible after moving mouse "through" the notch (often and) quick enough

I have a dual monitor setup where my MacBook is in Front of a bigger external display. Thus the arrangement has the MacBook's display on the bottom and the external display at the top - allowing the mouse to move "through" the notch when transitioning to the external display.
When doing this a few times quickly with the dice model (in the TestFlight 1.0.4 (36) build), the dice will stay on screen.
https://github.com/chockenberry/Notchmeister/assets/1689782/a85f4f48-247b-4220-883d-2ab138c42d4d

Oh, ok. Just found it strange that the other effects didn't seem to suffer from this. Or are they implemented differently?

Very differently - the previous ones used simple Core Animation. This new one uses a Metal scene with shaders, physics, etc. in a separate window that you can't click on, while another window tracks the mouse and clicks.

Interesting! Thanks for explaining!

I can't reproduce this issue with the 1.0.5 (40) TestFlight build.  Wonder if the #25 fix also fixed this...

Yea, same here. Seems to be fixed!


--dependency_mode LOOSE does not work

Consider the following files:
greet.js:
function greet(msg) {     console.log(msg); } exports.greet = greet;
hellogreet.js:
function hellogreet(msg) {     console.log("Hello " + msg); } exports.hellogreet = hellogreet;
entrygreet.js:
const greetmod = require("./greet.js"); const myname = "John Doe"; greetmod.greet(myname);
Compile the files with the following command line:
java -jar closure-compiler.jar --formatting PRETTY_PRINT --compilation_level SIMPLE_OPTIMIZATIONS --process_common_js_modules --dependency_mode LOOSE entrygreet.js greet.js hellogreet.js
Expected behaviour: The output should only include contents of files entrygreet.js and greet.js.
Acutal behaviour: The output includes contents of all 3 files, including hellogreet.js.
--dependency_mode LOOSE should add all files that do not goog.provide a namespace and are not modules as --entry_point entries. In this case it is file entrygreet.js. This file depends only on greet.js and nothing depends on hellogreet.js. Therefore the generated output should definitely not include contents of hellogreet.js. So it seems --dependency_mode LOOSE is broken and acts just like --dependency_mode SORT_ONLY.
Can you please investigate and fix the problem?

--dependency_mode=LOOSE considers every file without a goog.provide or goog.module statement to be an implicit entry point, in addition to the explicit entry points given by the --entry_point flag. If you want --entry_point to be your only entry point, use --dependency_mode=STRICT.
Note: LOOSE and STRICT are deprecated synonyms for PRUNE_LEGACY and PRUNE, respectively. Their behavior is documented in the flags wiki page.

@tjgq Thanks, but actually that's not the whole truth. The flags wiki page you referenced says:

PRUNE_LEGACY same as PRUNE but files that do not goog.provide a namespace and are not modules will be automatically added as --entry_point entries.

Furthermore the Managing Dependencies wiki page makes it clear that:

--dependency_mode=LOOSE will keep any files that do not goog.provide symbols (whereas --dependency_mode=STRICT will drop them). ES6 and CommonJS modules are rewritten to always have goog.provide statements.

The file hellogreet.js in my above testcase is a CommonJS module (as determined by the exports.hellogreet = hellogreet; statement. It's also not a dependency of any other file in my testcase. So it should definitely not be included in the compiler output.
The option --dependency_mode LOOSE currently does not work correctly and that's causing us some headaches at the moment. Switching to --dependency_mode=STRICT and specifying all possible entry points manually in the --entry_point option is a possible workaround. Nevertheless I'd prefer to be able to just use --dependency_mode LOOSE because this is the easier approach for us and would work perfectly in our environment.
Thanks for your note regarding the deprecation of LOOSE and STRICT in favor of PRUNE_LEGACY and PRUNE. The above testcase also fails with PRUNE_LEGACY so this doesn't male any difference.
By the way: The help page of the compiler and also the flags wiki page states that the default dependency mode in the absence of --entry_point is NONE. This is not correct. The compiler defaults to --dependency_mode=SORT_ONLY in this case. This is also implied by the section Using Closure Compiler to auto-sort files of the wiki page Managing Dependencies.
It would be very helpful if both the option --dependency_mode LOOSE and the documentation could be fixed.
Thanks!

Created internal issue - b/145155120


Inspector - Enable DriveSpace module to run more frequently than once a day

Starting with the drive space module I will be removing the once a day collection restriction so that the drive space can be monitored at a chosen intervals rather than being forced to once a day.

As we will be potentially increasing the volume of data in the DriveSpace table will need to optimise the code to accommodate large data so will be swapping the CTEs for temp tables and comparing the results after bloating out the DriveSpace table locally.


Fix Markdown lint errors and enhancement in README

Prerequisites
Put an x into the box(es) that apply:

[ ] This pull request fixes a bug.
[ ] This pull request adds a feature.
[ ] This pull request introduces breaking change.

For more information, see the Contributing Guide.
Description
There are minor Markdown lint issues in README (according to these rules) which this pull request fixes them.
Issues Resolved
List any existing issues this pull request resolves.
Checklist
Put an x into all boxes that apply:

[x] I have read the Contributing Guidelines.

Tests

[ ] I have added tests to cover my changes.
[ ] All tests pass when I run make test.

Documentation

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Code Style

[ ] My code follows the code style of this project.

@metmajer the last two commits are essentially my personal opinion and they can be reverted if you think they shouldn't be here.

Oh nice, I didn't know. I've rebased and readjust the content of this PR.
Also still included "Table of contents". So please feel free to decide to keep that or not.

Awesome, thanks!