Negative time value in analysis

It shouldn't really happend, but some people are seeing negative time value in reports:
e.g.
benchmarked xxx
time                 136.9 ms   (-340.9 ms .. 511.1 ms)
                     0.063 R²   (0.000 R² .. 0.999 R²)
mean                 1.010 s    (425.0 ms .. 3.335 s)
std dev              1.833 s    (12.24 ms .. 3.048 s)```

It looks like this is an analysis problem and not a measurement problem. I saw this:
analysing with 1000 resamples
bootstrapping with 3 samples
benchmarked compose/mapM/list-transformer
time                 857.6 ms   (-7.8041e15 s .. 3.9813e15 s)
                     1.000 R²   (-Infinity R² .. 1.000 R²)
mean                 874.2 ms   (866.4 ms .. 880.1 ms)
std dev              8.968 ms   (0.0 s .. 10.16 ms)
variance introduced by outliers: 22% (moderately inflated)
iters                2          (1 .. 3)
time                 874.2 ms   (866.4 ms .. 884.0 ms)
cycles<PHONE_NUMBER><PHONE_NUMBER> ..<PHONE_NUMBER>)
cpuTime              873.9 ms   (866.3 ms .. 884.1 ms)
maxrss               3548501    (3543040 .. 3551232)
nivcsw               163        (150 .. 179)
allocated<PHONE_NUMBER><PHONE_NUMBER> ..<PHONE_NUMBER>)
numGcs               2663       (2663 .. 2663)
bytesCopied          1016694    (1016411 .. 1017208)
mutatorWallSeconds   862.5 ms   (855.3 ms .. 872.1 ms)
mutatorCpuSeconds    862.5 ms   (855.3 ms .. 872.1 ms)
gcWallSeconds        5.659 ms   (5.539 ms .. 5.724 ms)
gcCpuSeconds         7.067 ms   (6.926 ms .. 7.143 ms)

The measured values of time seem ok and mean also seems to be in line with that. However, the time reported by analysis and R^2 seems to have some anomaly. Look at that range, both min and max seem to be totally out of the whack (-7.8041e15 s .. 3.9813e15 s). I am tempted to take a look at this but am resisting myself because of the other pressing work.

My guess is that it is due to insufficient number of samples. To confirm the hypothesis I looked at the benchmarks in which this problem was seen and all of them are the ones in which the benchmark took too much time and because of that the total number of samples were reduced to 2-3.

It confirmed, the problem is due to the number of samples, you can reproduce it by passing --time-limit 0 --min-samples 3. If you use 3 or less samples you will see strange numbers. With 4 samples NaN is seen. With 5 samples there are no big numbers but still the resampled range is outside the normal measured range. Only when the number of samples are sufficiently large e.g. 10 then the numbers look all close to normal. Need to understand how the statistical analysis is working.

Without understanding the statistical analysis deeply ot fixing it, a cheap and quick way to avoid this is to provide a warning when the number of samples is less than 8 that the number of samples are insufficient and the analysis may not be correct.

the R^2 coefficient measures the average slope of the linear regression, and in the limit of few samples this is basically meaningless. Any model is plagued by high variance predictions when the samples are too few w.r.t the model complexity. There are two ways forward as I see it: warn the user about the limitations of the model or implement a more realistic model, that takes into account the actual data distribution etc.

Thanks for the insight @ocramz ! Warning looks like the way to go for now. Tweaking the model and specially getting it right and stable may be a bigger effort and someone has to take that up.

We need to decide the constant for warning, how many samples are sufficient? Currently the default limit that we have set in the measurements is 10 samples, that is the max we get by default. I am wondering if that itself is low?

The R^2 coefficient improves quite a bit if I increase the sample duration from the default 5 seconds to 10 seconds:
cutlass:/vol/hosts/cueball/workspace/github/hs-gauge  (help)$ stack bench --benchmark-arguments "--min-bench-duration 1"
gauge-0.2.1: benchmarks
Running 1 benchmarks...

Benchmark self: RUNNING...
benchmarked identity
time                 54.46 ns   (53.31 ns .. 55.73 ns)
                     0.997 R²   (0.995 R² .. 0.999 R²)
mean                 54.28 ns   (53.67 ns .. 54.95 ns)
std dev              2.562 ns   (2.166 ns .. 3.036 ns)
variance introduced by outliers: 33% (moderately inflated)

benchmarked slow
time                 184.5 ns   (182.0 ns .. 187.6 ns)
                     0.999 R²   (0.998 R² .. 0.999 R²)
mean                 184.8 ns   (183.1 ns .. 187.7 ns)
std dev              8.629 ns   (5.787 ns .. 15.28 ns)
variance introduced by outliers: 33% (moderately inflated)

Benchmark self: FINISH

Should we consider increasing the default a little bit more? It will make the measurement slower though.

Sorry, it was 1 sec vs 10 sec and not the default (5s) vs 10 sec. I did a few more experiments and it seems upto sample duration of 2 seconds the R^2 is ok below that it degrades rapidly in this particular benchmark.

This seems to happen also with larger sample sizes when variance is high:
benchmarking difference-disj_tn_swap ... took 22.83 s, total 420091 iterations
benchmarked difference-disj_tn_swap
time                 -297.0 ns  (-2.343 μs .. 558.6 ns)
                     0.019 R²   (0.000 R² .. 0.700 R²)
mean                 2.823 μs   (2.307 μs .. 3.623 μs)
std dev              1.184 μs   (715.8 ns .. 1.452 μs)
variance introduced by outliers: 89% (severely inflated)

So just increasing the sample time will not guarantee that this doesn't happen.

Just noticed the same thing! Also with a function taking only a very small amount of itme.
benchmarked micro/subscribeMerge(10000)
time                 -322.9 ns  (-1.290 μs .. 308.3 ns)
0.053 R²   (0.000 R² .. 0.519 R²)
mean                 12.38 μs   (5.727 μs .. 22.08 μs)
std dev              16.73 μs   (10.19 μs .. 21.62 μs)
variance introduced by outliers: 94% (severely inflated)


[MCOMPILER-592] - IndexOutOfBoundsException when project.build.output…

…Timestamp is empty
Following this checklist to help us incorporate your
contribution quickly and easily:

[x] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without
pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [MCOMPILER-XXX] - Fixes bug in ApproximateQuantiles,
where you replace MCOMPILER-XXX with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the
commit message.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
[ ] You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[ ] In any other case, please file an Apache Individual Contributor License Agreement.

From JIRA issue:
Due to a combination of plugins, it is possible for the project.build.outputTimestamp property to have an empty string as a value. This causes an IndexOutOfBoundsException on line 1242 when it tries to access the first character in the string.
This can be fixed by doing an isEmpty check before doing the charAt check. I will create an PR for this.
While this bug is caused by another plugin, I think this should be fixed in the compiler because the error returned (IndexOutOfBoundsException), is vague and hard to debug.
The workaround for this issue is setting the project.build.outputTimestamp property with an arbitrary value.


"make" fails

Hi,
I'm trying to build & install scalpel 0.5.2 on Ubuntu 15.10
running Terminal from the unpacked source folder
when using "sudo make", I get an error message about missing BamReader.h
the file is there (in scalpel-0.5.2/bamtools-2.3.0/src/api)
plz see attached screedshot
what do I do?

Install the lib:
On ubuntu:
apt-get install libbamtools-dev


Fix crash on smooth shading for meshes with no index buffers.

Overview
When forceSharedVertices is called on a mesh that does not have a index buffer, the forceSharedVertices will create empty arrays for its positions and normals vertex attributes. This will result in a NativeEngine::RecordVertexBuffer been called with undefined arguments been passed as VertexBuffer* argument.
A similar behavior happens on the Web engine; however, the web engine creates vertex attribute arrays of size zero, which results in no rendering for those meshes. By simply returning from NativeEngine::RecordVertexBuffer we get the same behavior on the Native engine.
Issues

Fixes #1108

This fix was moved to the JS side and should be solved with PR https://github.com/BabylonJS/Babylon.js/pull/12781


Noise model

In recent discussions and even implementations the idea of a noise model came up. Maybe even with separate parameters similar to the model_error.
Main purpose:
The multiple model errors of an inference problem currently return the individual model error contributions as a nested dictionary like {experiment_key : {sensor : vector_of_numbers}}. We now need a way to further adapt this output:

VB: define N "noise groups" - e.g. N lists of tuple(experiment_key, sensor) - that ends up with N individual vectors.
sampling: define the individual terms of the loglikelihood function also based on some data structures of exp_key, sensor-pairs

The main interface would be like
class NoiseModel:
    def define_parameters(self):
        pass

    def vector_contribution(self, raw_model_error_output, prm):
        pass

    def loglike_contribution(self, raw_model_error_output, prm):
        pass

Benefits:

The importance of the noise is elevated, somewhat to the same level as the model error. This is purely psychological though ;)
Provide reasonable, well defined default values like

class SingleNoiseForEverything:
    def define_parameters(self):
        p = ParameterList()
        p.define("sigma")
        return p

    def vector_contribution(self, raw_model_error_output, prm):
        # just concatenate _all_ outputs
        vector_terms = []
        for exp_me in raw_model_error_output.values():
            for sensor_me in exp_me.values():
                vector_terms.append(sensor_me)
        return np.concatenate(vector_terms)

    def loglike_contribution(self, raw_model_error_output, prm):
       error = self.vector_contribution(raw_model_error_output, prm)
       return - 0.5 * (len(error) * np.log(2.0 * np.pi *prm["sigma"]**2) + np.sum(np.square(error / prm["sigma"]**2))

Also allow for more complex noise patterns for individual sensors or even exp_key - sensor pairs. Side effect: This lets the user conveniently control which contributions of the many model error outputs he wants to include in the inference problem.

class NoiseBySensor
    def __init__(self, sensor):
        # ... later only returns the model_error contributions of "sensor"

Dealing with more complex noise models:

class SensorOffsetModel # parameters: sigma, offset

Dealing with correlations. Even tough we have not completely figured that out, I think something like

class FixedCorrelatedNoiseModel:
    def __init__(self, sensor, exp_key, cov_matrix):

or even
class CorrelatedNoiseModel:
    def __init__(self, sensor, exp_key, distance):
   # distance (time or space) between correlated measurements
   # parameters would be: sigma, correlation_length

could work.

The whole "the model error must return a dict  {sensor: values}" is practical for complex cases, but pointless for models like "ax+b". A ModelHasSingleOutputNoise could deal with that case - mainly in test files - where it skips the loop over sensors in its evaluation.

User experience:
problem = InferenceProblem()
key_me1 = problem.add_model_error(me1, me1.define_parameters())
key_me2 = problem.add_model_error(me2, me2.define_parameters())

# similar pattern for noise!
noise_model = SingleNoiseForEverything()
key_noise = problem.add_noise_model(noise_model, noise_model.define_parameters())

# assign the shared parameter "A" to the latent parameter "latentA"
problem.latent("latentA", "A", key_me1)
problem.latent("latentA", "A", key_me2)

# similar API for the noise
problem.latent("latentSigma", "sigma", key_noise)

# the following is yet to be discussed and (please) not part of this issue/discussion:
vb_prior = VBPrior(problem.latent)
vb_prior.set("latentA", Normal(...))
vb_prior.set("latentSigma", Gamma(...)) # well actually it should be "precision" for VB...

with pm.Model:
    pm_priors[problem.latent["latentA"].idx] = pm.Normal("latentA", ...)
    ...

As for the very simple case with a single model, I would say there is no need to define a multimodel error, but maybe have a specific inference problem that has the same functions (e.g. noise models), but just works with vectors (no keys, just pure np.arrays). But maybe that's something we can decide later on. Similar with the definitions of the priors (decide later). But I think on the other hand we should also allow the user to define the loglike individually (just as an alternative) by providing the option of easily defining user-specific noise models (I see no reason why this whould not work) or directly the complete loglike. So thumbs up from my point of view.


Compilation error. Cannot find WIFI library v1.0.0

Got error while compiling:
Library Manager: Installing arduino-libraries/WiFi @ 1.0.0
Error: Could not find the package with 'arduino-libraries/WiFi @ 1.0.0' requirements for your system 'windows_amd64'

The last version and only one is 1.2.7
https://github.com/arduino-libraries/WiFi/releases
Changing WiFi lib version to 1.2.7 occurs the error:
Compiling .pio\build\esp32dev\src\wifi.cpp.o
In file included from .pio/libdeps/esp32dev/ESP32 BLE Arduino/src/BLEAdvertising.h:15,
                 from .pio/libdeps/esp32dev/ESP32 BLE Arduino/src/BLEServer.h:19,
                 from .pio/libdeps/esp32dev/ESP32 BLE Arduino/src/BLEDevice.h:18,
                 from src/bluetooth.cpp:12:
.pio/libdeps/esp32dev/ESP32 BLE Arduino/src/FreeRTOS.h:61:28: error: 'ringbuf_type_t' has not been declared

@VadimIzmalkov
Please update your build environment. I have no issue with the compilation.

@VadimIzmalkov
Meanwhile I got the issue in my environment too.
Try to find the solution

@VadimIzmalkov
The issue has been fixed.
Sorry for the delay. Thank you for the report.


Set up a component playground experience

A long text file is a poor way to show all variants of a component. Especially given that all these variants can also be applied simultaneously in any permutation.
An interactive playground where toggles can be turned on/off and variants can be chosen from a list of checkboxes would make it easy to mix and match and overlay variations.
This is offered to some extent by Storybook, but integrating it with Styleguidist is not straightforward. Also I'm inclined towards presenting this interface within the style guide rather than another completely different ecosystem. Storybook has a documentation system coming up so that might bridge the gap or replace Styleguidist entirely.
Anyway Storybook does have some features that Styleguidist lacks (you have to type out code snippets to see them in action, no UI or knobs) so initiating it is nevertheless a step towards the positive direction.

A part of this interface can be an interactive color and shade experience, that allows the user to select colors and shades using SelectFields and toggle inverted mode using a SwitchField.
Something along these lines has been implemented in the documentation for the Header.

As Storybook comes closer and closer to providing the features afforded by Styleguidist, and then more of its own, it has been added to the project as of d3b8612 and can be seen at this link. Work remains on adding components to this Storybook and documenting their common and edge cases.

Storybook 5.2.0 adds support for :books: DocsPage and :framed_picture: Design System. This is relevant because it means Storybook is officially in Styleguidist territory.

I am Ify an Outreachy Intern, I would like to resolve this issue. kindly assign it to me.

@ifylala I should point out that this is a long-term issue and thus you should either break it down into smaller logical parts before getting to coding. Also from the point of view of your Outreachy application and your newness to the codebase, you should check out good-first-issue to get familiar with the code.

@ifylala Any updates on this?

@ifylala any updates on this?

No update yet @dhruvkb , like you said earlier it's best if it is done in bits. Can you help me in breaking it down? Because I am a bit confused.

@ifylala any updates on this?

No update yet @dhruvkb , like you said earlier it's best if it is done in bits. Can you help me in breaking it down? Because I am a bit confused.

@ifylala let’s start with elements, that too the first one which is <Button/>. Can you convert the styleguide for Button into an interactive storybook? By interactive I mean like instead of coding in every prop, use “knobs”.

@dhruvkb please explain what you mean by "knobs"

Storybooks has been updated to version 5.2, with documentation addon and JSX support. @chidexebere is taking on this issue for week#1 of Outreachy.


Some text in filetype.vim is incorrectly highlighted

Steps to reproduce
In $VIMRUNTIME\filetype.vim the text augroup END in lines 2738 and 3008 is highlighted in vimAugroupError, which seems to be incorrect.
Expected behaviour
.
Version of Vim
9.1.296
Environment
.
Logs and stack traces
No response

That is probably because the list of autocommands is so huge. I think a :syn sync fromstart fixes it.

I am closing this as not a bug.


🛠 Tooling: Migration end-to-end tests are failing on main

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
I pushed things directly to the main branch and this is my punishment.
https://github.com/JoshuaKGoldberg/create-typescript-app/actions/runs/6085593506/job/16510050783:
Run pnpm run migrate:test
  pnpm run migrate:test
  shell: /usr/bin/bash -e {0}
  env:
    PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin

> create-typescript-app@1.[2](https://github.com/JoshuaKGoldberg/create-typescript-app/actions/runs/6085593506/job/16510050783#step:5:2)9.[3](https://github.com/JoshuaKGoldberg/create-typescript-app/actions/runs/6085593506/job/16510050783#step:5:3)2 migrate:test /home/runner/work/create-typescript-app/create-typescript-app
> node script/migrate-test-e2e.js

(node:191[4](https://github.com/JoshuaKGoldberg/create-typescript-app/actions/runs/6085593506/job/16510050783#step:5:4)) ExperimentalWarning: Import assertions are not a stable feature of the JavaScript language. Avoid relying on their current behavior and syntax as those might change in a future version of Node.js.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:1914) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
┌  Welcome to create-typescript-app ! 🎉
│
│  ⚠ This template is early stage, opinionated, and not endorsed by the TypeScript team. ⚠
│  ⚠ If any tooling it sets displeases you, you can always remove that portion manually. ⚠
│
◇  Migrating repository structure...
│   - Clearing unnecessary files.│   - Clearing unnecessary files ✔
│   - Writing structure.│   - Writing structure..│   - Writing structure ✔
│   - Writing README.md.│   - Writing README.md ✔
│   - Updating local files.│   - Updating local files ✔
│   - Updating all-contributors table.│   - Updating all-contributors table..│   - Updating all-contributors table│   - Updating all-contributors table..│   - Updating all-contributors table│   - Updating all-contributors table..│   - Updating all-contributors table│   - Updating all-contributors table..│   - Updating all-contributors table│   - Updating all-contributors table..│   - Updating all-contributors table│   - Updating all-contributors table..│   - Updating all-contributors table│   - Updating all-contributors table..│   - Updating all-contributors table│   - Updating all-contributors table..│   - Updating all-contributors table│   - Updating all-contributors table..│   - Updating all-contributors table ✔
│
◇  ✅ Passed migrating repository structure.
2[5](https://github.com/JoshuaKGoldberg/create-typescript-app/actions/runs/6085593506/job/16510050783#step:5:5)l│

...what's the failure?!
Additional Info
No response

Well, the CLI output in GHA seems to be timing out, but:
Oh no! Running the migrate script modified some files:
 - .github/workflows/build.yml
 - .github/workflows/lint-markdown.yml
 - .github/workflows/lint-package-json.yml
 - .github/workflows/lint-packages.yml
 - .github/workflows/lint-spelling.yml
 - .github/workflows/post-release.yml
 - .github/workflows/prettier.yml
 - .github/workflows/tsc.yml

That likely indicates changes made to the repository without
corresponding updates to templates in src/.

Please search for those file(s)' name(s) under src/migrate for
the corresponding template and update those as well.
 ELIFECYCLE  Command failed with exit code 1.
joshgoldberg ~/repos/create-typescript-app $


health_checker: Add request header options to GRPC health checker.

Upstream GRPC hosts may categorize requests by request headers. This change exposes
request_headers_to_add and request_headers_to_remove options to GrpcHealthCheck in
a way similar to HttpHealthCheck.
Signed-off-by: Wanli Li<EMAIL_ADDRESS>
Commit Message: health_checker: Add request header options to GRPC health checker.
Additional Description: Upstream GRPC hosts may categorize requests by request headers. This change exposes
request_headers_to_add and request_headers_to_remove options to GrpcHealthCheck in
a way similar to HttpHealthCheck.
Risk Level: Low
Testing: Performed manual test, a new unit test is added to cover the new code path.
Docs Changes: None
Release Notes: Added to "Minor Behavior Changes" section.
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest

/retest

ping for another look.

/assign-from @envoyproxy/first-pass-reviewers

ping for another look.


Fix WalletSimple sequenceID handling

The WalletSimple multisig contract validates a sequence ID with each
signature to protect against signature replays. In the previous version
of the contract, this sequenceId was validated against a moving window
of the last 10 ids. This allowed for some flexibility with transaction
ordering, while avoiding the same id being used twice, and avoiding
keeping much state around. In the new version, we deemed this
unnecessary and simplified it to a purely increasing value. However,
it turns out that the ordering flexilibity is actually desirable and
worth the cost. This commit brings back the original moving window
implementation.


Cannot download the config file created for Service providers in the registry

Type: Bug
Priority: High
Severity: Major
Release: wso2is-5.4.0-update1
Steps

Create a SP
Go to the registry and download the created file

Issue
Cannot download the file. Tried with chrome and firefox

This is because the resource doesn't have any content. It only has properties.


Error calculation query

Hello, I am running the pipeline on a protein-lipid system (one chain). I get very different information flow values if I run the protocol with all 5 repeats vs running on individual repeats and averaging post-processing (for the protein and the ligands).
I guess my question really relates on how best to report error. Ideally I'd like to report the values calculated using all replicates as these are probably more reasonable - I was running on individual repeats in order to get the standard deviation/standard error between repeats but now I am concerned by the change in the mean information flow values.
For reference the simulation length is comparable to those reported in your paper. Any advice here would be appreciated.

Hello,
Then I would suggest, as you mentioned, to run each simulation replicate in the analysis pipeline independently and calculate the mean and standard deviation on the obtained profiles afterwards.
Best,
Annie

Dear Annie,
How is the information flow being averaged when all repeats are provided? Why do I get different mean information flows between the individual and combined means? Is it something to do with how the values are normalised?
Best,
Bertie

From: anniewesterlund @.>
Sent: Thursday, September 9, 2021 3:03 PM
To: delemottelab/allosteric-pathways @.>
Cc: Bertie Ansell @.>; Author @.>
Subject: Re: [delemottelab/allosteric-pathways] Error calculation query (#2)
Hello,
Then I would suggest, as you mentioned, to run each simulation replicate in the analysis pipeline independently and calculate the mean and standard deviation on the obtained profiles afterwards.
Best,
Annie
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/delemottelab/allosteric-pathways/issues/2#issuecomment-916128070, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AN6N2Z5HAQMDCRJJYKCGK63UBC5DBANCNFSM5DVBEMFA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi Bertie,
This depends a little on what your system is, and how you specify input paramters.
Essentially, no averaging over different information flows is done unless you input a homomer with multiple chains and specify n_chains (> 1). In that case, the averaging is done across subunits in your protein. Otherwise, your entire dataset is treated as one dataset which gives rise to measurement written to:
self.out_directory_ + 'current_flow_betweenness_' + self.file_end_name_ + '.npy'
What we did in this paper: https://doi.org/10.1063/5.0020974 on the single-chained GPCR, was to divide the simulations into three chunks and compute average and stddev using the resulting three information flow profile afterwards. I would not be surprised if there is some difference between using the full dataset to get one point estimate of the information flow compared to using three and averaging (sampling effects etc. which may be more prominent).
Hope this helps,
Annie

Dear Annie,
Ok thanks you for your help. Interpretation of the information flow for the bound ligand differs quite substaintaing between the two analyses but I will take you word for it and use the individual replicates.
Best wishes,
Bertie

From: anniewesterlund @.>
Sent: Thursday, September 9, 2021 4:02 PM
To: delemottelab/allosteric-pathways @.>
Cc: Bertie Ansell @.>; Author @.>
Subject: Re: [delemottelab/allosteric-pathways] Error calculation query (#2)
Hi Bertie,
This depends a little on what your system is, and how you specify input paramters.
Essentially, no averaging over different information flows is done unless you input a homomer with multiple chains and specify n_chains (> 1). In that case, the averaging is done across subunits in your protein. Otherwise, your entire dataset is treated as one dataset which gives rise to measurement written to:
self.out_directory_ + 'current_flow_betweenness_' + self.file_end_name_ + '.npy'
What we did in this paper: https://doi.org/10.1063/5.0020974 on the single-chained GPCR, was to divide the simulations into three chunks and compute average and stddev using the resulting three information flow profile afterwards. I would not be surprised if there is some difference between using the full dataset to get one point estimate of the information flow compared to using three and averaging (sampling effects etc. which may be more prominent).
Hope this helps,
Annie
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/delemottelab/allosteric-pathways/issues/2#issuecomment-916181577, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AN6N2Z6TEYIXL2ESDECPWSLUBDD7TANCNFSM5DVBEMFA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hm, ok. Just a final note: The individual replicate analysis should in principle be better in such a case, since you also get the error estimate which could help removing focus from uncertain residues.
Closing issue :)


Navigation - 'Back' button should always bring you to 'Home'

The intended behavior of the 'Back' button in the navbar intends to return the user always to the 'Home' screen (MainScreenWithTabs), even if the user have navigated from one narrow to another. We even use some custom logic for that.
This mostly works, except in few cases that may confuse our current logic. One such case:

go to a stream narrow
open the list of topics
navigate to a topic
go Back

Expected behavior - you are in 'Home'. Current behavior - you are in the TopicsScreen.

Why is this the intended behaviour? The user when pressing the back button expects to go back one navigation level, i.e. where they arrived on the current screen from.
Infact I thought there might have been a bug where clicking back from the topic screen doesn't take me back to the stream where it came from, which is why I filed #3455. There has been a discussion (well, sort of) on this too.

That is a good point. We used to have this behavior in the past. I actually thought this to be the default sensical behavior.
Sometimes though you might go several levels deep but apparently people still want to go back to the Home/Root screen so they navigate elsewhere. Enough users complained about it.
At least currently this is the intended behavior (likely to not change soon without a redesign of the UI, which itself is not a priority) I did file the issue because I already had the commit that fixes it.

I basically agree with @ishammahajan -- to the extent that the code currently does successfully have this behavior, I usually find it annoying and not what I wanted.
Good to have this issue to discuss it on! And thanks @ishammahajan for the links to previous discussions. I just went looking to see if we have an older issue thread on this subject; I didn't find one.

Enough users complained about it.

I haven't really thought this through, but if there are enough users on both sides of the argument we could have a setting which changes the behaviour dynamically. I've seen some apps that do this (albeit IIRC, they were Reddit apps). Just a thought.

could have a setting which changes the behaviour dynamically

Death by a thousand app settings?

The decision was made a long time ago but people used to complain and now they don't. @timabbott might have thoughts on this (or not, has been a while).
Switching to the granular back behavior is straight-forward so this is not a technical problem.

As an additional data point: the current behavior (and additional behavior suggested by this thread) seems to be in contradiction to Google's Android navigation guidelines.


allow arbitrary metric prefixes

#1433

@songy23 Done

Please rebase and remove the merge commit (https://github.com/census-instrumentation/opencensus-java/pull/1440/commits/8b1d24d055c5455e9187156d9a70651c63a318b1) from PR.


vertx-sync

Synchronous but non-OS-thread-blocking verticles
Github Project: https://github.com/vert-x3/vertx-sync

We should provide a way to configure Vert.x distribution


Fix architecture doc

Network namespace is created before the pause container.

/lgtm

/ok-to-test


Restore the original resolution.

The script successfully change the resolution of the host to the device I am connecting but failed to restore the resolution after I terminated the connection.

This should be fixed in latest release, assuming you were also a Parsec user

Unfortunately, I am not a Parsec user and this is a new clean PC only with Steam, games, and moonlight installed.
What information can I offer to help to solve the situation?

You would basically need to debug it on your side, so realistically without programming skills that will be difficult.
As a workaround I would suggest changing the Set-ScreenResolution call when the stream ends to use hardcoded values instead, such as instead of referencing $hostResolution.CurrentHorizontalResolution you would change that to 1920 for example.

Thank you for your help, I will try you solution once I got a chance.
Love.

Hello there,
Juste to let you know I have the same problem, using sunshine too as server

Hello there,
Juste to let you know I have the same problem, using sunshine too as server
EDIT : to give more information, I test from android moonlight client and from another pc, both on disconnected do not put back the original resolution.
I also replace the line 250 of GS_SS-MatchResolution.ps1 and reinstall the task with the above
Set-ScreenResolution -Width 2560 -Height 1440 -Freq $hostResolution.CurrentRefreshRate
it seems like this line is not triggered on the client disconnect

You need to hard code the refresh rate too, basically don’t reference the variable at all.

I tried but no change unfortunatly :/

I'm dealing with the same issue right now, I hard coded the values into line 250 but no success.

I changed the logic of the resolution swap in this pre-release, let me know if it works for you or not.
https://github.com/Nonary/ResolutionAutomation/releases/tag/precommand_beta

I removed the latest release and ran this pre-release but I'm still getting the same issue unfortunately. The resolution doesn't switch back. Anything else I should give a shot?

I removed the latest release and ran this pre-release but I'm still getting the same issue unfortunately. The resolution doesn't switch back. Anything else I should give a shot?

Yes, please download the release again. I added logging, can you upload that log if it failed to work for you?

Tried again but still no change. Where can I find the logs at?

Tried again but still no change. Where can I find the logs at?

It's in the same folder as the script, named log.txt

@AbrahamHuitron Remember to install it again, if you don't it will not have the correct paths.

I have veen overwriting the previous files and running the files again. I will try again in a few hours. One question though, when right click and run with PowerShell it runs quick but closes. Is that the normal expectation?

I have been overwriting the previous files and running the scripts again fresh. I will try again in a few hours. One question though, when right click and run with PowerShell it runs quick but closes. Is that the normal expectation?

For the ResolutionMatcher.ps1 script yes, that is launched before you start streaming and will hide in the background.
The installer script should not be closing out.

Yeah when I'm right clicking on the install script it opens up a Powershell script but really quickly closes it out. The latest version you uploaded, not sure if it's running or not, but doesn't change the resolution anymore.

Also, I have your AutoHDR script active and it's requirements set at the moment too by the way, i.e. Windows Console Host, etc. so not sure if any of those are clashing with these prerelease requirements. AutoHDR is working fine by the way.

Hey there, I came back and wanted to let you know I figured out the issue. For some reason everytime I was running your prerelease version through the PowerShell (I was following your steps to run To install, right click the Install_as_Precommand.ps1 file and select "Run With Powershell".). The PowerShell window would just open then immediately close. I'm an admin on my computer but what I ended up doing was just right clicking and editing the file, which then defaulted it to open PowerShell completely.
Within here I was able to see the error message the script was giving me forcing the close. the .ps1 file is not digitally signed. So I used this to temporarily bypass and run the script.
https://caiomsouza.medium.com/fix-for-powershell-script-not-digitally-signed-69f0ed518715
All went through, the script works great and the resolution matching is working now!
The only other thing I would suggest is maybe you could set the script to revert back to the original resolution not when we CLOSE out the application we are running on Moonlight, but when we actually QUIT the application from the Moonlight interface. I'm playing on my Android handheld and when I close the app out to go to another task the resolution reverts back to my PCs but streaming is still essentially "happening". Just a thought. Thanks!

@AbrahamHuitron I forgot I had developer mode enabled in Windows, which is why the script didn't work for regular users. I have fixed this now, the new releases now include a batch file which launches the powershell window with the correct parameters needed.
As for your second question, you would need to setup your application in Sunshine with a command if you want it to automatically terminate the session or revert back after that. Otherwise, ending the stream in Moonlight will revert resolution regardless.

Awesome, I will update when I get home.
Oh that's right. I'm using Playnite launcher only as the my single app in
Moonlight and it was giving me issues whenever I set the commands to
monitor it. Mainly if the app is already running or not. So yeah I guess
it's not an issue on your end you're right thanks!
On Tue, Apr 25, 2023, 7:16 PM Chase Payne @.***> wrote:

@AbrahamHuitron https://github.com/AbrahamHuitron I forgot I had
developer mode enabled in Windows, which is why the script didn't work for
regular users. I have fixed this now, the new releases now include a batch
file which launches the powershell window with the correct parameters
needed.
As for your second question, you would need to setup your application in
Sunshine with a command if you want it to automatically terminate the
session or revert back after that. Otherwise, ending the stream in
Moonlight will revert resolution regardless.
—
Reply to this email directly, view it on GitHub
https://github.com/Nonary/ResolutionAutomation/issues/2#issuecomment-1522665526,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFB3EVPWRAJVYO7LLV53KGDXDCARBANCNFSM6AAAAAAV2NPPNE
.
You are receiving this because you were mentioned.Message ID:
@.***>

As far as I am aware the recent changes to my script should have resolved all the edge cases where it was not properly pulling the client resolution to restore. I am going to close out this issue as resolved at this point.


go.min.js:1 Uncaught ReferenceError: hljs is not defined

Can't seem to get the lib working.

<script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.4.0/languages/go.min.js"></script>
<script>hljs.initHighlightingOnLoad();</script>

<script>
    $(document).ready(function() {
        $('pre').each(function(i, block) {
            hljs.highlightBlock(block);
        });
    });
</script>

Right now you included the language but not the core library. You also only need to choose one initialization function, because initHighlightingOnLoad and the jQuery $(document).ready(function() { ... }) are essentially the same thing. So change your example to:
<script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.8.0/highlight.min.js"></script>
<script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.8.0/languages/go.min.js"></script>
<script>hljs.initHighlightingOnLoad();</script>

@sourrust I forgot I created this issue, I found it out myself already, Only thing I can say is that the docs are not very clear in that case.


Refined GitHub

Does the Refined GitHub extension have a place on this cheat sheet in the GitHub section? It tries to enhance features or highlights features already available from GitHub, remove some clutter and even add some additions.
I encourage you to read its highlights and install it to try it out.
To give some examples:

it enhances emoji reactions by showing avatars of people
it shows patch and diff links on commit pages (it also works arounds https://github.com/tiimgreen/github-cheat-sheet/pull/155#issuecomment-206402858)
when using blame in GitHub it takes advantage of GitHub support for blaming parent commits with ^ and adds links to blame the parent commit

I think GitHub power users looking for more tips in the cheat sheet would find it useful.
It has a Safari port and soon it could be cross-browser with the Web Extensions API.

This does look like a useful tool however I don't think I should include it in the main body of the cheat sheet.
There are hundreds of tools out there that make using GitHub easier and more streamlined - I use a few myself - however I have purposefully left these out of GHCS. If I started adding everything that I thought people would find useful it would soon become a convoluted document.
For that reason I have limited everything in GHCS to Git/GitHub native functionality (I know Travis CI isn't native but I thought that was a reasonable exception to the rule).
However, I would be happy for you to create a PR adding a table at the bottom of the GitHub section with something along the lines of 'Extensions you might find useful', under the 'GitHub Resources' header.


Investigate why in some cases two workers get the same validation message

Related to https://github.com/azavea/raster-foundry/issues/318
We fixed the issue in which multiple EMR jobs were being created because we accidentally validated the same image multiple times but we don't know why that happened in the first place. Investigate to see if this is still possible.

May have been fixed by #322.


would you like provide some demo dataset like train.txt, dev.txt, text.txt, input.txt?

or the URL of those resource

same question

https://github.com/glample/tagger/issues/2

Fixed in 3b2fc49fcc510d7a86a7848cd01fe11c2ee5b75b

@glample
is this reasonable like
python train.py --train dataset/eng.train --dev dataset/eng.testb --test dataset/eng.testa
?

eng.testa is the dev
eng.testb is the test

Hi @glample @loveJasmine   i am trying to train the model using
python train.py --train dataset/eng.train --dev dataset/eng.testa --test dataset/eng.testb  --lr_method=adam --tag_scheme=iob
but i got the following error. Can you please help me resolve that error?I am stuck...
46533/51362 (90.59811%)
Traceback (most recent call last):
File "train.py", line 220, in
dev_data, id_to_tag, dico_tags)
File "C:\Users\Acer\Anaconda2\tagger\utils.py", line 282, in evaluate
return float(eval_lines[1].strip().split()[-1])
IndexError: list index out of range


Separate Framework-Agnostic CUDA Implementation

Hi,
I see there are a few SDTW implementations around. I'm mainly using Keras right now, and there are a few implementations there too. The one I have used thus far is very slow to run, as I reckon it is jumping back into the CPU to interface with portions in Cython; and the rest is not very accessible to the graphcompiler, so the loops aren't unrolled in the GPU. It has to be executed eagerly.
I don't have any experience thus far in interfacing directly with CUDA, but I was wondering how possible it would be to separate out the CUDA implementation of the algorithm from the particular framework that is using it, and then just interface in, be it from Torch or Tensorflow - or potentially some other usecase. As they say, Don't Repeat Yourself.
This would probably apply to CPU use too. I have worked with Pybind11 a few times, and I don't know how well this would interface with either libTorch or tensorflow tensors, but, I presume if in CPU land whatever the graphcompilers can come up with is probably no better than a hand-rolled version in C++, if such a thing is around.
I'm guessing the differentiability would be the main thing - do you know if something like this would be possible? I'm not exactly experienced with neural networks, but I guess if I can use CudNN there must be some way to perform the backpropagation within the same kernel. In Ceres we can use expression templates to differentiate automatically, so I guess something must exist.
Any thoughts? I don't have time for sideprojects right now - but if this ends up making my network learn better, then it may well be worth the time put in.
Thanks

hello again @stellarpower,
the meat of pysdtw really is the two CUDA kernels: functions compute_softdtw_cuda and compute_softdtw_backward_cuda.
If you check the code, they only depend on cuda and math. The rest of the library is just a bunch of convenience code: pytorch integration as nn.module, support for packed sequences and availability on pypi.
After a quick googling, it appears that pytorch has a good integration with cuda, especially in python - and that is what is leveraged in pysdtw. On the other hand, I could not find any examples of calling python cuda kernels with tensorflow - only C++ (https://www.tensorflow.org/guide/create_op#use_the_op_in_python).
So, a framework agnostic python cuda implementation already exists (compute_softdtw_cuda and compute_softdtw_backward_cuda) but wrapping those might not be easy for other framework than pytorch.

Hi,
Right, yes, that's more or less what I mean - there are several versions out there and, be it in python or something else, I think it might be nice to separate the kernel into a separate package, for CPU and GPU, that implements the algorithm; then torch or tensorflow or some other bindings can live in their own package or repository and call in.
I have been looking and it seems there may be some ways to integrate the numba JIT code into tensorflow, but it's not looking that likely, and the standard way does seem to be in compiling an Op from C++ rather than using the ptx output and pulling that in at runtime.
Currently I'm seeing if implementing the backward pass specifically in the Keras version improves performance, as I expect the autodifferentiation is going to be the problem, but if not, it might be that I implement the algorithm in C++ and also write a kernel for it, with the aim of allowing calling in from other languages/frameworks.. Will keep you posted.
Thanks


HHH-14407 NPE in AbstractMultiTableBulkIdStrategyImpl for column 'hib_sess_id' of PersistentTableBulkIdStrategy

https://hibernate.atlassian.net/browse/HHH-14407
The NPE was introduced by https://github.com/hibernate/hibernate-orm/pull/3498. Specifically, the following new line introduced in that PR didn't take into consideration that some Column has null value (like the 'hib_sess_id' column in PersistentTableBulkIdStrategy) so it would trigger NPE:

The fix is simple as the following two steps:

set the sql code type of the 'hib_sess_id' to Types.VARCHAR;
in the above highlighted line, the Column#getSqlTypeCode(Mapping mapping) method is only invoked when Column#getSqlTypeCode() returns null; otherwise simply return the internal sqlTypeCode value directly, which is in line with the Javadoc of the method:

Thanks for the fix!

Thanks for the fix!

great, thanks @NathanQingyangXu !

great, thanks @NathanQingyangXu !


fix: prevent duplication of Monaco webpack plugin

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

It seems that adding it during the 'build-html' stage meant it was creating new, unminified, versions of the scripts and overwriting the existing, minified, ones.  I guess this is a peculiarity of that stage, though I'm not sure.
On my local tests it works for both develop and build so, all being well, it shouldn't break anything.
Related to #37742

@ojeytonwilliams, just to clarify, the loaded editor.worker.js should be minified with this pr?

@ahmadabdolsaheb everything editor related should be minified, so if you're on a javascript page it should minify typescript.worker.js and if you're on an html page it should do the same for html.worker.js.  And, yes, editor.worker.js for sure.
I think, with this change, every js file we produce should be minified.


fix(list-key-manager): prevent the default keyboard actions

Calls preventDefault when handling keyboard events in the ListKeyManager. This avoids the user scrolling the page when using the arrow keys to navigate.
Relates to #1999.

R: @kara


Better installation instructions

The current installation instructions are not sufficient for making ttx work. To illustrate the issue:
$ pip install fonttools
Requirement already satisfied: fonttools in /Library/Python/2.7/site-packages (3.32.0)
$ ttx
-bash: ttx: command not found

Or:
$ pip install -e .
Obtaining file://~/Repositories/GitHub/fonttools
    Complete output from command python setup.py egg_info:
    error in fonttools setup command: 'extras_require' must be a dictionary whose values are strings or lists of strings containing valid project/version requirement specifiers.

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in ~/Repositories/GitHub/fonttools/

Try to upgrade pip then retry to install fonttools. Pass —upgrade option

Before you upgrade pip, what version of pip do you have that raises that error?

Also the version of setuptools may be relevant. Try do pip list to see what version is installed in your env.

Reopening this issue, because (re)installation of fonttools remains a painful experience on macOS. Still no help in the readme, no useful help in a Google search. So, unless there is a requirement to keep fonttools inaccessible, please reconsider improving the installation instructions, or find a better way of installing fonttools.
Running sudo pip install fonttools gives me either:
Requirement already satisfied: fonttools in /Library/Python/2.7/site-packages (3.44.0)

or:
ERROR: Could not install packages due to an EnvironmentError: [Errno 1] Operation not permitted: '/System/Library/Frameworks/Python.framework/Versions/2.7/share'

I have no idea what that means, and there is no further help provided on what can be done to get fonttools installed. Googling the error message brings up this article which recommends the --user flag, which I do, and which results in another:
Requirement already satisfied: fonttools in /Library/Python/2.7/site-packages (3.44.0)

And alas, trying ttx returns the familiar:
-bash: ttx: command not found

And when I try pip install -e . in the fonttools directory, I finally get a different error message:
ERROR: Package 'fonttools' requires a different Python: 2.7.10 not in '>=3.6'

Which leads me to think it may be a Python version issue. However, I have not found the documentation for installing and running fonttools in a different Python version than the system default, which is a frequent case on macOS.
IOW: installing and running fonttools/ttx on macOS Mojave in late 2019 is not possible with the current instructions.

Running sudo pip install fonttools

sudo is the problem, you should not be doing that in the first place. The OS python should not be modified by the user. If you want to use the system's python distribution and extend it with third party packages from PyPI, you have to use the --user flag, which will install it in the /Users/Library/Python... folders.

also, python 2.7 is no longer supported. I strongly recommend you install python3 using homebrew if you are on MacOS, or simply download one of the official installers from Python.org website. These will not require you to use sudo. You can simply pip install --upgrade fonttools and they will do the right thing. The scripts will be in /usr/local/bin which is already in the $PATH so everything will work as expected.

for homebrew the command is brew install python which will install Python 3.

I have Python 3 installed. The --upgrade flag is still working into Python 2.7:
mekkabook-air:fonttools mekka$ pip install --upgrade fonttools
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Requirement already up-to-date: fonttools in /Library/Python/2.7/site-packages (3.44.0)

What worked eventually was cd’ing into the fonttools folder and running:
python3 setup.py install

Also undocumented, but now ttx gives me the command help.

sudo is the problem

Also without sudo, with and without the --user flag, the pip installation did not work. Same results as above. I tried uninstalling & reinstalling fonttools, uninstalling & reinstalling pip, all to no avail.

no, please don't use setup.py install which triggers the use of deprecated setuptools easy_install functionality. Always use pip to install, even from a local source checkout: pip install -e . with . meaning the current directory where the setup.py script is located.
You probably have pip installed for both the python2.7 and the python3 distributions on your local macine.
Check if you have pip3 command which is linked to it. Try to run pip3 --version and verify that it is linked with the correct python3's site-packages directories.
Or alternatively call pip with the fully qualified command name as in python3 -m pip or python3.7 -m pip so that you are certain that you are installing to the right pythons.

Check if you have pip3 command which is linked to your python3. Try to run pip3 --version and verify that it is linked with the correct python3's site-packages directories.

mekkabook-air:fonttools mekka$ pip3
-bash: pip3: command not found

🤷♂

Or alternatively call pip with the fully qualified command name as in python3 -m pip or python3.7 -m pip so that you are certain that you are installing to the right pythons.

This works:
python3 -m pip uninstall fonttools
python3 -m pip install fonttools

After the first command ttx stopped working as expected (=making sure no other fonttools installation was interfering), and after the second line, I got ttx to output the command help again.
Can we add this to the installation instructions in the readme?

For severals year I had terrible python setups on OS X. It would usually end up with dependency hell as I installed everything to the system Python and neglected virtualenvs.
For the installation notes in the readme, it may be a really nice idea to link to an article such as Digital Ocean's on setting up Python for OS X. It covers installing xcode, brew, creating a virtualenv and pip.
I feel this is needed because many folks use Python in font editors so their understanding of it on a system may be more limited.

Can we add this to the installation instructions in the readme?

yes and no. I mean, all this is generic python setup info that is available online, e.g. the official Python documentation or https://packaging.python.org/. Fonttools is not different from any other python package. I don't think we need to tell people how to set up their python environment.
For example, suggesting people to call python as python3 will work for your setup on MacOS or most Linuxes, but on Windows all pythons are simply caled python.exe and you call different versions using the py.exe launcher with some option to select the major.minor version.
I know, at the beginning this all looks complicated. But you can ask here, or on the Gitter fonttools chat for support and somebody will always be available to answer.
Ok, if you insist and want to send a PR, we can review it.

It boils down to: the installation instructions provided will not work on macOS. Currently, the instructions is doing a good job on excluding Mac users. I assume this is not intended.

The FontTools readme contains extra hints for Windows users, but not for Mac users.

Most type designers working with a Mac will try to install it and give up after the first error message. If they dare to ask, and are lucky, they get your attention right away.

More advanced users (=occasional CLI users) will try around until something works, googling, trying things they find on stackoverflow, on the way messing up their environment variables and installations/dependencies.

Likely better as another issue, but this speaks to needing some better docs for fontTools. Both an overview of what the package is for (see the many issues opened by folks thinking it does one thing where other packages are a better fit), install instructions, and an overview of the different modules/functions in fontTools. So much has been added in the last couple of years, little documented beyond release notes and GitHub issues.
Trust me, I know how hard it is to write good documentation, keep it up-to-date, and the like (see fontParts), but this could be a really good summer of code project or the like.

brew install python; python3 -m pip install --user --upgrade fonttools

I've made this
https://github.com/twardoch/fontsurgery-tools/
Time to update it. I've also made
https://github.com/twardoch/fonttools-py27
I’ll kill the commandline tools there, so it’s
lib-only. I plan to keep it with some occasional fixes for cases where Py3 is not usable. And I’ll switch my fontsurgery tools installer to do Py3-only first.
Maybe I'll do a convenience metapackage on pypi that’ll just install assorted packages. In most cases, inexperienced users are better served with “a bundle”.

(you don't need --user with brew python)

https://github.com/twardoch/fonttools-py27

you are welcome to "upstream" those backported changes if you like. We have py27 branch, but nobody was interested in updating that.

brew install python; python3 -m pip install --user --upgrade fonttools

For that to work, users would need to install Homebrew first. Does it have any advantage for a normal user over using the official Python installer from python.org? For me, Homebrew is just another easy way to mess up your system ...
python3 -m pip install --user --upgrade brotli zopfli fonttools

for me ;)

python.org installer are ok too.
@jenskutilek to install all the extra requirements you can do pip install fonttools[all]

similarly, for the python.org distributions, you don't need --user flag because the site-packages folder under /Library/Frameworks/Python... is not write-protected like the one under /System hence it does't require sud (well, unless you're sharing your machine with other users)

Also note when installing with --user the executable scripts are not placed under /usr/local/bin, but under the user's bin directory (in my case /Users/clupo/Library/Python/3.7/bin). This is not already in the $PATH, so you will have to append to it in your shell config file (e.g. .bashrc).
So --user adds a further layer of complexity.
Whereas /usr/local/bin/ is already in the default executable $PATH.

So, a better guide to this would be good. I'll make a PR tomorrow.

Cosimo, you're right. I started doing --user because of the built-in Python 2.7. But since Mac does not include Py3, simplest is best, and no --user is simpler for Py3.

So, to sum things up, my current Mac installation instructions for Catalina, July 2020:

Install Homebrew: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
Install Python3 through homebrew: brew install python
Install fonttools: python3 -m pip install --upgrade brotli zopfli fonttools

Please CMIIW

Is Homebrew still necessary to install Python 3? I used it in the past but found it hard to upgrade to newer Python versions.
On my current Mojave machine I installed Python 3.8.2 with the official installer from Python.org. Seems to work fine.

Homebrew had significant issues with the 3.8.x rollout.  3.8 just landed as the default python3 on my Catalina system in the last ~ week.  While it is not required to have the latest/greatest python3 for a fonttools install, it is possible that many on macOS have been moving away from Homebrew as a py3 package manager for this reason.  When CI services can land a Py version earlier than a local desktop package manager it is generally a bad sign... :)
FWIW, builds / installs from the cPython source works fine on macOS too.  I am building the 3.9 branch on Catalina without issues using the README docs.

Catalina also has /usr/bin/python3 stub that will prompt the user to install command line tools on first call, so that might be a more convenient way to install Python 3 as well.

This might not be relevant if you don't use asdf, but this has bitten me in the arse often enough that I need to leave a comment for my future self:
If you're using the asdf version manager, be sure to run asdf reshim python after installing through pip, otherwise it will not find the ttx executable.

Anything actionable here?


Exclude modules

When I tried to exclude modules in the "Code exclude patterns" it didn't seem to work for multiple modules when entered on 1 line. I then tried it like this:
^Module1::|^Module2::|^Module3::
which seems to work.
Maybe update the manual on this?

I think the comment in the system configuration is quite clear on this, it states that it should be one module per line;

Translation codes matching these regex patterns will be excluded. One pattern per line. Leave empty to include all untranslated strings. PROTIP: use "^MODULE_NAME::" pattern to match an entire module.


fix(compiler-sfc): ignore style comment in tranform stage

Fix #6807

The behavior of the compile seems like it's not a bug.
I think it would be better to fix it here:
https://github.com/vuejs/core/blob/85af1398637ee91c6ebabb73bf42250320311e19/packages/runtime-dom/src/modules/style.ts#L40-L66

The behavior of the compile seems like it's not a bug.
I think it would be better to fix it here:
https://github.com/vuejs/core/blob/85af1398637ee91c6ebabb73bf42250320311e19/packages/runtime-dom/src/modules/style.ts#L40-L66

Thanks, it's a good point. But I still think the compiler should know this is a comment, not a property of style.


[WIP] Feature/remove contributors multiple components

Purpose
Give users the choice to remove a user from either the current node or from the current node and all its children.
Current:

Proposed:

Changes:

Delete the user from the given node as a default with a modal.
If the Admin wants to remove the Contributor from the node AND its children, Open a second modal view, and use the API V2 to list of every component associated with the Contributor to remove.
If the Admin clicks "Remove" on the second view, use the API v2 to delete those contributors from all child nodes previously listed.

TODO

Use the new Embed feature of the API to get the list of nodes so we can delete the Contributor from all the relevant children, then delete those dogs.

Currently blocked by #4600


Add version: JetBrains.Kotlin.Compiler version 1.1.4-3

Pull request has been created with Komac v1.9.1 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116333&drop=dogfoodAlpha

@wingetbot waivers Add Validation-Executable-Error


Error when using multiple Elysia instances

elysia-ip version: 1.0.0
So you get this error whenever you write something sane like this (e.g. to separate route definitions).
const app = new Elysia()
  .use(cors())
  .use(login)
  .listen(envs.PORT);

const login = new Elysia()
    .use(ip())
    .post('/login', async ({ body, ip }) => {
        console.log(ip);
        ...
    });

export default login;

You will have to call the plugin for each Elysia instance. This is how plugins in Elysia work.
For every instance where you want to use this plugin you will have to call .use(ip())

I can't figure this out either, You will probably have to use the plugin in the main instance i.e. where you call .listen()

Hmm...I'm thinking how it would be usable for any moderately serious application.
The elysia-ip source code is only 60 lines currently so I'll see if I could fix it for my app and perhaps make a PR later.

I have a similar issue.
When I register the plugin on the main instance, all sub-instances (in separate files) return null for the IP.
To take the example above:
const app = new Elysia()
  .use(cors())
  .use(ip())
  .use(login)
  .listen(envs.PORT);

const login = new Elysia()

    .post('/login', async ({ body, ip }) => {
        console.log(ip); // null
        ...
    });

Do you think this is related, or should I open a new issue? That new as: global thing is messing things up ^.^
I'm using v1.0.11 of Elysia.

This is different because you should be instantiating the plugin/middleware wherever you intend to use it. My issue was despite using it syntactically correct, it would error out on requests because of limitations of the Elysia API. Plan to look into how to hook into the bun API under the hood without needing Elysia to start listening first. But I'm busy currently so I won't get back to it in a bit

https://elysiajs.com/essential/plugin#service-locator
The docs say this to be a Typescript limitation so i really don't think i can do anything on my part

@justin13888 After investigating this issue, I have found that this should work just fine for your case:
import Elysia from "elysia";
import { ip } from './src/';

const login = new Elysia()
    .post('/login', async ({ body, ip }) => {
        console.log(ip);
// ...
    });

const app = new Elysia()
  .use(cors())
  .use(ip())
  .use(login)
  .listen(envs.PORT);

export default login;

You will have to call the plugin in the instance where .listen() is called.

@Extarys I'm sorry but i am unable to reproduce your issue. it works just fine on my machine.

thanks for taking the time to test on your end. I'll keep testing on mine, maybe my setup is different... somehow :P

I am closing the issue. Feel free to open a new one if something doesn't work again


Doc or docx format

Hi, for our internal review process, I am getting feedback that they would like a Word format to review.  Is it possible for this github action to produce a doc or docx format?  Or if not that, is it possible some other way like through the container?  Thank you!

You can now use -o docx to generate that format. The document uses pandoc's default template, so it is not styled like a JOSS paper.


Replacing API response test logic with responses syntax

Replacing  other test logic with responses? It seems neater
Originally posted by @DiamondJoseph in https://github.com/DiamondLightSource/blueapi/pull/409#discussion_r1636259471

@responses.activate
@pytest.mark.handler
@patch("blueapi.service.handler.Handler")
@patch("blueapi.cli.cli.sleep", return_value=None)
def test_env_endpoint_interaction(
    mock_sleep: MagicMock, mock_handler: Mock, handler: Handler, runner: CliRunner
):
    # Setup mocked responses for the REST endpoints
    responses.add(
        responses.DELETE,
        "http://localhost:8000/environment",
        status=200,
        json=EnvironmentResponse(initialized=False).dict(),
    )
    responses.add(
        responses.GET,
        "http://localhost:8000/environment",
        json=EnvironmentResponse(initialized=False).dict(),
        status=200,
    )
    responses.add(
        responses.GET,
        "http://localhost:8000/environment",
        json=EnvironmentResponse(initialized=False).dict(),
        status=200,
    )
    responses.add(
        responses.GET,
        "http://localhost:8000/environment",
        status=200,
        json=EnvironmentResponse(initialized=True).dict(),
    )

    # Run the command that should interact with these endpoints
    result = runner.invoke(main, ["controller", "env", "-r"])

    # Check if the endpoints were hit as expected
    assert len(responses.calls) == 4  # Ensures that all expected calls were made

that is the syntax brought up there


add new line to trigger rebuild

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance.

cc @conda-forge/core
@conda-forge/staged-recipes I have no idea what's causing this error; the recipe is unchanged from the original PR but the original PR passed all tests while this one if failing


Spaces in WebHook URL cause controller calls to fail

While I get that this is operator error, it would be helpful if when entering a WebHook URL the Web UI stripped any starting or trailing whitespace that may come from a copy-and-paste error. They cause controller calls to fail and also are hard to catch and debug.

https://github.com/bcgov/traction/pull/1199 merged


feat: added boilerplate code for next.js + tailwind

🛠 Fixes Issue
Closes #27
👨💻 Changes proposed
#Added boilerplate code for the next.js + tailwindCSS
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
It's a boiler plate code for the next.js + tailwindcss
link - https://github.com/vercel/next.js/tree/4d4f3093019179b1928ec07c16f38882241c0375/examples/with-tailwindcss
📷 Screenshots

Thank you!
Any chance you could add documentation on setting it up / running it?

Thank you!
Any chance you could add documentation on setting it up / running it?

yeah nice idea, do you want me to add it into existing readme.md file?

yeah nice idea, do you want me to add it into existing readme.md file?

yes I think that's the right approach here

hi @ykdojo i've updated the readme.md file. please have a look at it. Thanks

Thank you! Looks good to me


bug(*): fix mobile view using wrong viewport + other minor issues..

browser
Brave
bug description
barmenu centering on... what?! clearly not on viewport size.
https://github.com/cyperdark/osuck-skins/assets/107962621/01c2e17f-464b-4172-b78c-aa3de8f312a6
scroll randomly stops?! scroll stutter?
https://github.com/cyperdark/osuck-skins/assets/107962621/299469c4-a79e-4fd2-b35a-42b2915bd0b1
here's a more obvious video from a skin page:
https://github.com/cyperdark/osuck-skins/assets/107962621/cba1e7e4-a58a-4d67-9459-8b8d49946356
also, skin properties
(HD, SD, ANIMATED) are being covered by the quick link button? and they are not horizontally scrollable.

and image view is... weirdly not scaling to the screen width... again viewport issue.
https://github.com/cyperdark/osuck-skins/assets/107962621/af0b9443-8279-4e31-b8c5-bd08e8ceb2bb

Check image view and bar menu in current version

The navbar is still not fitted into the viewport

it's because there is too much things in navbar, but overall better than before?

it's because there is too much things in navbar, but overall better than before?

Yeah the overall viewport is back to normal. Just the navbar being weird

about weird scroll shutter, does your phone have any scroll smoothing things?

about weird scroll shutter, does your phone have any scroll smoothing things?

Has this:
https://github.com/cyperdark/osuck-skins/assets/107962621/e42961df-facb-4970-9e80-4aa70ca4b85c
But apparently the scroll shutter is gone!?

huh, nice but how

huh, nice but how

I don't know? it does not happen anymore? probably was a browser issue? which I wouldn't really rely on because I've checked the issues on multiple browsers & devices.

Another one :D


Tutorial ambiguity

I am relatively new to python and am having trouble following the tutorial provided. In bash I load the (metaseq-test) environment, downloaded the example data to ~/metaseq-example/data. At this point the tutorial confueses me. I can set the variable data_dir = 'metaseq-example/data' if I switch to python, but then commands like "ls" and "head" don't work. If you switch to bash, it doesn't know the python variables, and you cannot set them in bash like you show in the tutorial.
Sorry to complain about what I am sure is an elementary issue, but I feel the tutorial could be a bit more clear in this regard. Thank you! -Keller

It is in bash. The tutorial should read [ data_dir='metaseq-example/data' ]. i.e. omit the spaces. Like I said an elementary issue, but it trips up young greenears like me. -Keller

The beginning is in bash. The tutorial should read [ data_dir='metaseq-example/data' ]. i.e. omit the spaces. Then it looks as if you switch over to python when we [ import os ]. Am I missing something? Would you please provide a bit of an explanation on the swapping of shells, and how it should be managed? Thank You!

 My understanding in this context is that !{string} will search your bash history for a line beginning with that string and print the line. I have been omiting it.

That's IPython notebook syntax (and IPython interpreter syntax as well), where you use the "!" for one-line system calls. Otherwise, Python is expected.  I've updated the docs in the source to clarify this, but the PyPI docs server is down so I can't upload the new version.


log content when subprocess.Popen another Python code file

logzero version: 1.5.0
Python version: 3.6.5
Operating System: Windows 7 Professional

Similar issues: #57 #222
Description
In code file pgm_a.py, I use subprocess.Popen to execute python.exe with code file pgm_b.py. Both pgm_a.py and pgm_b.py use logzero (default logger with logfile setup).
The log file pgm_b.log for pgm_b.py looks fine.
The log file pgm_a.log for pgm_a.py includes two copies of log content for pgm_b.py, which is not I expected.
My understanding is, default logger configuration have log content to standard output (screen) and output to file with same content. Even log content of pgm_b.py were generated by another python.exe executed from subprocess.Popen, logzero still collect them (both of them) into pgm_a.log.
What I Did
I tried to set up logger for pgm_b.py using
mylogger=logzero.setup_logger(name="mylogger", logfile=mylog, disableStderrLogger=True)
It looks mylogger has different data structure than logger_default, which may affect other part of code.
[I 190806 17:31:43 process:613] General information:

    CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
    C
    C    COMPUTERNAME: ********
    C
    CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC

[I 190806 17:31:43 process:210]  NOTICE:::*** Processing Started for Client 000.

[D 190806 17:31:43 process:430] Start sending email with Subject: NOTICE:::*** Processing Started for Client 000....
[D 190806 17:31:43 process:435] Sent email successfully

[I 190806 17:31:43 process:247] Start 1-th Python process pgn_b.py test 3 arg.
[D 190806 17:31:43 process:464] ***\python.exe -B ***\pgm_b.py test 3 arg
[D 190806 17:31:43 process:475]
[D 190806 17:31:43 process:477] '***'

    CMD.EXE was started with the above path as the current directory.

    UNC paths are not supported.  Defaulting to Windows directory.

    [I 190806 17:31:43 startup:10] AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

    [I 190806 17:31:43 startup:11] Auto code file: ***\startup.py

    [I 190806 17:31:43 startup:12] AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
[I 190806 17:31:43 process:479] python code file pgm_a.py result is '***'

    CMD.EXE was started with the above path as the current directory.

    UNC paths are not supported.  Defaulting to Windows directory.

    [I 190806 17:31:43 startup:10] AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

    [I 190806 17:31:43 startup:11] Auto code file: ***\startup.py

    [I 190806 17:31:43 startup:12] AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
[I 190806 17:31:43 process:260] result:NO Issues:

[I 190806 17:31:43 process:363] *** pgm_a.py finished at 20190806 17:31

Is there a way in logger_default to switch disableStderrLogger to be True/False directly, instead of using logzero.setup_logger?

Found reason.
When we use subprocess.Popen to submit python.exe with pgm_b.py, the logger statement in pgm_b.py will output to both pgm_b.log file and standard output (screen). Then subprocess.Popen just collect the standard output as stderr. My pgm_a.py forcely shows stderr twice.
After I comment out command of showing stderr, it works as I expected.


Custom Host Node RFC

This is just an idea and not likely to land any time soon.
Summary
This is an alternative idea to useMutationEffect that was originally part of the hooks RFC but since removed.
Basic example
import {createManualDOMNode} from "react-dom";
let CustomDOMNode = createManualDOMNode(props => {
  // create
  let node = document.createElement('div');
  node.style.color = props.color;
  return node;
}, (props, node) => {
  // update
  node.style.color = props.color;
}, (props, node) => {
  // clean up
});

function Component(props) {
  return
<CustomDOMNode color={props.color} />
;
}

Rendered text

I like the API. But excluding the advantage of cleaner API, Why not using component with shouldComponentUpdate: () => false + ref for creating something similar? The "updates" callback seems cleaner, but I'm not sure if this API, is really must

What about memoization? Or rather firing update callbacks only when inputs has changed? To some extent it can be done inside the update callback itself, but it's hard (impossible?) to store some previous state in order to do the comparison.

What about memoization? Or rather firing update callbacks only when inputs has changed? To some extent it can be done inside the update callback itself, but it's hard (impossible?) to store some previous state in order to do the comparison.

@Andarist do you mean "impossible" to do self-contained—or strictly impossible? Is it not possible to use a collection-type instance to memoize in a closure around the result of createManualDOMNode due to some arcane detail of the Hooks API?

With HOC approach we lose access to the component's closure (unless we do some hoops to create that HOC with useMemo or smth), with hook approach we'd have to store previous values on the ref or node and do custom inputs check in the updater (instead of relaying on the input array and react doing that work for us like when dealing with all the other hooks)


Autocrafting with Artisan's Worktable tools consumes full tool.

Issue description: Autocrafting with a tool from Artisan's Worktable's consumes the entire tool instead of using durability, using an entire tool for each crafting operation.
What happens: Tool is used entirely in a single crafting operation instead of durability used.
What you expected to happen: Tool's durability should be used instead of the entire tool.
Steps to reproduce:

Autocraft a recipe that uses Artisan's Worktable tools in a pack that uses them. (Dungeons and Dragons and Space Shuttles is a good example.)

Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: <IP_ADDRESS>22
Refined Storage: 1.6.14

Does this issue occur on a server? yes
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

This is the intended behavior. Not a great solution to just delete the item but if it was easy to detect such things, making them work would be easy...
1.13/1.14 will change the way reusable items work completely and as such implementing a solution for 1.12 that needs to be ripped out right after is not something people want to spend their time on.


folder_branch_ops: support partial syncs

Any time folderBranchOps learns about a newly merged revision, and the TLF is configured in partial-sync mode, kick off a partial sync. Also, kick one off when the sync config is changed.
For each partially-synced path, do a solo-sync-fetch of each parent block, and then deep-sync the final element in the path.
Deleting blocks from unsynced paths will happen in a future PR.
Issue: KBFS-3523

Note: this PR now depends on #1943, so you might want to review that one first.


Correct rviz model location

Description of changes:
In the install folders, the .rviz file under the hello_world_robot package are under the rviz directory, when it should be under the share/rviz directory to be consistent with the hello_world_simulation package of the simulation workspace.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The confusion has been cleared up. The directories are different between ROS1 and ROS2 because of differences between rospack find and ros2 pkg prefix.


Can pm2 auto start MagicMirror2 on startup in node serveronly mode?

Platform: RPi3 B, Chromium Browser, Raspbian Jessie Stretch Full Version
Node Version:  v9.11.1
MagicMirror Version: MagicMirror v2
Description: I want to run MM2 from the Chromium browser on my RPi3-B, since I can then be logged into my google account and display my Google Calendar (via MMM-iFrameReload...it works) without having to add in OAuth2.0 support to the module myself. I have used pm2 to autostart the MagicMirror app and that is nice....but my Google account info will not show on the MM this way.
How can I have the node serveronly command automatically start then stay running? I am connecting (currently) via SSH (PuTTy) but have also been directly at the RPi3 running MM2 and same result. As soon as I close the terminal window, the server hangs up and can no longer refresh/display from Chromium browser. I have also tried starting like this...
nohup node serveronly &
same thing...as soon as the terminal window is closed, node shuts down.
Configuration: Configuration is fine

SOLVED (And sorry for the inconvenience).
Here is the link to the original issue and the solution...
https://stackoverflow.com/questions/12701259/how-to-make-a-node-js-application-run-permanently#comment73761740_12701259
As you will see from the post in the above link, the answer was to run it like this:
node ~/MagicMirror/serveronly > stdout.txt 2> stderr.txt &
Thanks to DogNibbler on StackDriver.

ISSUE 2 SOLVED
From terminal, typed:
netstat -np to get the PID of my node process then typed: kill12345 //where 12345 is the PID of your nodeinstance
also can find PID of node instance with this command:
ps `-A
but that does not return as much information in case you need to verify the IP:port of the node instance before killing it.
NOW...to run MagicMirror2 as a server only using pm2....
in the terminal, enter the following:
pm2-runtime ~/MagicMirror/serveronly > stdout.txt 2> stderr.txt &
then enter:
pm2 list

Isn't that gorgeous!!!
Now to autorestart the serveronly after a crash or pi reboot.... enter:
pm2 save

Before finding this post (I was actually looking for something else), I solved this problem by not using 'pm2' at all, and instead created 'systemd' services. This way there is full control over start, stop, restart. Note that this is for using MM as 'serveronly' and not the electron app. Combined with other tools, such as 'supervisor' for example, you can get more granularity and even have the client browser to refresh the page after the service restarts. This solution was based on work created by another MM user, which can be found here: https://github.com/alexiri/MagicMirror/compare/master...alexiri:reload


How can we have the cardstack effect like tinder or kikoso cardview

Hi How can we have the z index of the cardview having the next cards(At least stack effect of 3-4 cards) showing like the stack effect is there any solution which is already implemented please share the code snippet.

@Diolor can you take a look at this issue.

@alexwalterbos can you check out this issue please

I'm working on a branch that incorporates this. I don't know when that'll be done, as I'm busy otherwise.

@alexwalterbos Thanks man :+1:  please get that feature asap possible and let us know thanks a ton.

@alexwalterbos please take a look at this lib this lib dont support prior to API level 19 other than that this is good example https://github.com/wenchaojiang/AndroidSwipeableCardStack

You do realize that this feature has no priority to me whatsoever, so I can make no promises regarding when it will be finished (even if I finish it at all)?

This would actually be a very nice effect if done

Stack effect would be nice!

I would love it too!

Same there

You can do something like this in your Adapter when you have set app:max_visible="3":
`
@Override
public void onLayoutChange(View v, int left, int top, int right, int bottom, int oldLeft, int oldTop, int oldRight, int oldBottom) {
final float scalingFactor;
float translationFactor;
    switch (mCurrentPosition) {
        case 0:
            scalingFactor = 1f;
            translationFactor = v.getMeasuredHeight()*scalingFactor-v.getMeasuredHeight();
            break;
        case 1:
            scalingFactor = 0.9f;
            float topPosition = v.getTop();
            translationFactor = v.getMeasuredHeight()*scalingFactor-v.getMeasuredHeight();
            break;
        case 2:
            scalingFactor = 0.8f;
            translationFactor = v.getMeasuredHeight()*scalingFactor-v.getMeasuredHeight();
            break;
        default:
            scalingFactor = 1;
            translationFactor = 0;
    }

    v.setScaleX(scalingFactor);
    v.setScaleY(scalingFactor);
    v.setTranslationY(translationFactor);
}`

I'm still trying to figure out animations ;)

If someone still need this, please check my fork: https://github.com/antonkrasov/Swipecards
Demo: https://youtu.be/yi7OXnJvUXE

@antonkrasov, Great solution, thank you!

@antonkrasov Thanks a lot, How can we put the cards stack visible in bottom instead of top?

@antonkrasov may be a noob question, but HOW do i use your fork instead of the diolor branch?


Add action to push to GHCR on release

Add GitHub action to push to GitHub Container Registry on release
In reviewing some of our code, I noticed that we have a dependency on the config transpiler container that is published by redhat on quay.io.  I'd like to use the flatcar version instead, so I prepared this PR to use github actions to publish this on rel
How to use
Continue producing releases and let GitHub Actions take care of the rest.
Testing done
I tested this in my fork.

:) Hi @invidian , thanks for quickly reviewing my PR.  I appreciate your feedback.  Please let me know if you'd like me to switch to tags.

Hello there, I had the same idea today before seeing this PR, see here https://github.com/flatcar-linux/container-linux-config-transpiler/pull/18. The differences are that I prefer to keep the name ghcr.io/flatcar-linux/ct and that I added multi-arch build. I'd rather keep the short versions names though, since we only consume trusted actions from the docker org.
Also already published an image for v0.9.2/latest/latest-dev so you can consume.


PersistedClaims and AlwaysUseDefaultValue?

Does PersistedClaims support AlwaysUseDefaultValue as does the OutputClaims?
The documentation does not indicate that, but in my own testing it does seem to take effect in custom policies.
Is the documentation missing that or am I exploiting a bug that might get fixed?
Specifically, I am using this in a migration scenario as outlined in the azure-ad-b2c/user-migration repo

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

ID: 388cccb2-2f58-b0fb-fc2f-1828e35e431c
Version Independent ID: c3ca0abf-ae09-e109-8376-01c086ba5abc
Content: TechnicalProfiles - Azure AD B2C
Content Source: articles/active-directory-b2c/technicalprofiles.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@TheUniquePaulSmith
Thanks for your feedback! We will investigate and update as appropriate.

@TheUniquePaulSmith
Thanks for your feedback! We will investigate and update as appropriate.

@JasSuri would you be able to confirm whether Persisted Claims is supposed to support AlwaysUseDefaultValue? It seems like this is was accidentally left out of the document, unless it is not supposed to support this.
I reached out to someone on my team as well.

@JasSuri would you be able to confirm whether Persisted Claims is supposed to support AlwaysUseDefaultValue? It seems like this is was accidentally left out of the document, unless it is not supposed to support this.
I reached out to someone on my team as well.

The product team confirmed that yes, it seems to be a miss in the documentation. Just like OutputClaims, PersistedClaims also supports the AlwaysUseDefaultValue. It should be included in the documentation.
I made a pull request to add this. https://github.com/MicrosoftDocs/azure-docs-pr/pull/144802

The product team confirmed that yes, it seems to be a miss in the documentation. Just like OutputClaims, PersistedClaims also supports the AlwaysUseDefaultValue. It should be included in the documentation.
I made a pull request to add this. https://github.com/MicrosoftDocs/azure-docs-pr/pull/144802


feat: add function to format date without milliseconds

This commit adds a function to convert Date objects into ISO strings without milliseconds. This function is then used to format the 'published', 'reviewedDate', 'versionDate', and 'statusDate' fields in the 'reviewedPreprintSnippet' function.

We should followup with a test but as this is causing issues I'm keen to get this live.


Fix conv5 in Discriminator definition of CycleGan_solution.ipynb

It seems that the original def. of conv5 outputs Tensor:(7,7,1) whereas the diagram above indicates it should be Tensor:(1,1,1).  Accordingly this fix is proposed.  I'd appreciate your looking into it.

Since I found other cyclegan implementations use the same type of non-1D tensor as the final output of Discriminator, I chose to close this pr. Thanks.


Known Issue List

All issues in this list are planned to fix(not listed in order):

[ ] Comments are not formatted
[x] Blank can be more than one between Name and Path in an import block #108
[x] Blank can be more than one between Path and Comment in an import block #108
[ ] Miss imports completion
[ ] Miss imports deduplication
[x] Cannot handle multiple imports group #106

The conflict with goimports like https://github.com/daixiang0/gci/issues/76 only provides a workaround now.

Since #43, the design is extremely complex and it's not really Go idiomatic (it feels more like Python/JS program).
I think that global design can and must be simplified.

https://github.com/daixiang0/gci/pull/70 has simplified some parts of it. If you have some ideas about it, feel free to share them here or post a PR directly :)

Any plans to support removal of unused imports similar to goimports?

Any plans to support removal of unused imports similar to goimports?

Add TODO list.


FEATURE - Make an App Intent for Adding an Odometer Reading with Shortcuts

Describe the feature you want the app to have that it currently doesn't

Use App Intents to create a shortcut to add a new OdometerReading

Describe alternatives you've considered

N/A

Additional context

Here's one of the App Intent WWDC videos to help get started
This is part of a bigger idea with automatic odometer readings, see this discussion, but don't do this whole feature, with the automatic logging, this issue is only for making a shortcut with App Intents
I haven't used this yet, but if any entitlement things or targets need to be added, let me know and I can add that, and then you can continue on this (rather than you adding anything), because of signing issues and merge conflicts that can happen

@OmarHegazy93 you said you wanted to work on this, please comment below and I can assign it to you!

Hi Mikaela, yes please assign it to me. Thanks!

@mikaelacaron So far I gathered the basic idea to do that, but based on the resources you mentioned and some other investigations, I've some concerns I want to share with you to have the big picture.
The way I see it is about two approaches
If the shortcut is intended to be used without opening the app
Concerns

Currently, to add a new Odometer reading, we have a dependency for the Vehicles as we need to expose the list of the vehicles to the user to select the desirable one
The only way to have those vehicles right now is by fetching them from Firestore

Possible solutions

To persist the vehicles locally before sending them to Firestore, and we'll need to keep both of them in sync to make sure that what we have is what already exists in Firestore.

⚠ The Apple tutorials I've seen so far are relying on singletons to access their data (like database and navigation), so that might require a change for the app architecture
⚠ If that works, not sure yet if we will be able to upload the reading through the shortcut or not due to authentication, but it think this can be addressed later

If the shortcut requires the app to be opened

Most likely it will be strait forward, because we already have the shared instance from the ActionService which we can rely on to open the view in the app

That's what's in my mind, please let me know which one you're planning to go for, or of course if you have any questions.

If the shortcut is intended to be used without opening the app

This is not the intention. That isn't possible because there would be no way to enter the number of miles / km for the odometer reading, as of how the app is built right now
You should be able to run the shortcut (in the shortcut we could select which vehicle to use) and then you'd be able to enter an odometer reading, and that would save to Firebase
Is what I'm imaging, I haven't created shortcuts so I'm not 100% sure that is the best way for it to work, but that's what I'd like. A simple way to add an odometer reading, from a shortcut

This is not the intention. That isn't possible because there would be no way to enter the number of miles / km for the odometer reading, as of how the app is built right now

Not sure also, but I think it's doable using the @Parameter property wrapper to get it as an input from the user.
You should be able to run the shortcut (in the shortcut we could select which vehicle to use) and then you'd be able to enter an odometer reading, and that would save to Firebase

I still can't imagine how we can select a vehicle while we don't have a direct access to them to be listed in the shortcut, unless you're planning to use the ViewModel itself but this will add another complexity as we will need to save user's login information. Do I understand your point correctly?

I still can't imagine how we can select a vehicle while we don't have a direct access to them to be listed in the shortcut

So, first thing, it's not possible to fetch any data from any network inside a shortcut, or (what I imagine with this app) set the shortcut up with any information that comes from a network?
It has to use information that's local??


Water and lava pillars not high enough

I understand why, I understand how, but they're not high enough all the time, especially in those high caves we currently have.
#71 will decrease the occurrence of this, but it will likely still happen regardless.

If we could choose objects to be placed on the top of a cave, we could stilt it down easily. Would be a plugin thing though: Iris plugin issue request

Ceiling decorator  needs to be implemented, and it will be easier


Improve keystore generation

Describe the feature here
Http-grouped: It should be possible to generate keystore and truststore during build. (if not disabled)

The feature for generating the certificates could be created in a general way, so other modules can re-use it

One way of general solution might be adopting the Quarkus way by using https://github.com/cescoffier/certificate-generator

One way of general solution might be adopting the Quarkus way by using https://github.com/cescoffier/certificate-generator

Yeah, I saw that project mentioned on Quarkus Zulip some time ago and wondered whether we could start using it.
If possible, I think it'd be good to try and use a single tool for cert generation in the project. Currently we've got a mix of shell scripts, maven plugins etc which becomes a bit of a maintenance pain.

Indeed https://github.com/cescoffier/certificate-generator would be great to replace them all. I did not know it exist, thanks for the pointer. IIRC, we were forced to use openssl for writing PKCS12 stores, because Java's java.security.KeyStore did not support some sort of store encoding required by FIPS. Looking at https://github.com/cescoffier/certificate-generator/blob/main/certificate-generator/src/main/java/me/escoffier/certs/CertificateUtils.java#L200-L270 it seems that it is using java.security.KeyStore for writing the stores. But you mentioned recently @JiriOndrusek that JKS works on FIPS too? I wonder whether we need to try to fix certificate-generator's PKCS12 impl to comply with FIPS?

With one of the recent java updates (I'm not sure which concrete build it was), certificates generated by the java keystore  work in FIPS environment. (I noticed it several weeks ago) Therefore the certificate-generator project should cover all our needs.
I'm currently trying to solve FIPS for kafka tests and I'm using the certificate-generator, which seems to be easily usable. Once I'm sure that all works, I'll ping you on the PR to discuss whether we want to use such approach on the whole project.

I tried generator-projext in kafka and all looks good.
My second attempt would be cxf-soap to see whether the complex generation can be achieved by the project.