[Overlay] Use standing space

We had changes in https://github.com/SlimeVR/SlimeVR-OpenVR-Driver/pull/24 that switched the tracking space from raw to "standing". We need to account for this change in the overlay.

Mentioning @kitlith

some of the PRs made to ovr_overlay are necessary for this. (you may as well just assign me for this)
overlay has already been switched to standing, but everything else is now using a variant that ignores playspace movement, which is why changes are still necessary

some of the PRs made to ovr_overlay are necessary for this.

Working on reviewing them. Could you link the ones that block this issue?

https://github.com/TheButlah/ovr_overlay/pull/8 and https://github.com/TheButlah/ovr_overlay/pull/9, though the first one needs to be rebased and worked on a bit now that you merged https://github.com/TheButlah/ovr_overlay/pull/11
I'll get that rebased now.


Test Case for Lab8 Level 4

Hi All! Am at Lab8, Level 4 and I am currently inputting differently for a test case.
I know that when I go back(), I shouldn't update tick() if there are no previous rooms before this. Could there be any other things that could be missing when implementing the back() function? Thanks for your time!

Hi @kayyenl, I've faced a similar issue as well. You might want to check if you've removed the sword from the old room when moving to the next room if the sword is taken.

Hi @feederalert! I haven't thought of that case yet. Thanks for the suggestion! That should solve the problem.


[Bug]: Cargo failling to compile v4l-sys

Steps for reproducing the issue
run make build on Fedora aarch64
What is the buggy behavior?
I'm getting the following error code:
[dxwil@asahi wluma]$ make build
cargo build --locked --release
Compiling v4l-sys v0.3.0
error: failed to run custom build command for 'v4l-sys v0.3.0'
Caused by:
process didn't exit successfully: '/home/dxwil/Build/wluma/target/release/build/v4l-sys-c55733300b09fa98/build-script-build' (exit status: 101)
--- stdout
cargo:rustc-link-lib=v4l1
cargo:rustc-link-lib=v4l2
cargo:rustc-link-lib=v4lconvert
--- stderr
/usr/include/stdio.h:33:10: fatal error: 'stddef.h' file not found
thread 'main' panicked at /home/dxwil/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v4l-sys-0.3.0/build.rs:14:10:
Failed to generate bindings: ClangDiagnostic("/usr/include/stdio.h:33:10: fatal error: 'stddef.h' file not found\n")
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
make: *** [Makefile:15: build] Error 101
What is the expected behavior?
For it to compile
Logs
RUST_LOG=debug wluma

Version
4.0.4
Environment
LSB Version:	n/a
Distributor ID:	Fedora
Description:	Fedora Linux Asahi Remix 39 (Thirty Nine)
Release:	39
Codename:	n/a
Linux asahi 6.8.7-402.asahi.fc39.aarch64+16k #1 SMP PREEMPT_DYNAMIC Wed Apr 24 00:11:34 UTC 2024 aarch64 GNU/Linux
bash: pacman: command not found
bash: dpkg: command not found

Hello, it looks like a missing -dev package with necessary headers, but more importantly you should know that asahi doesn't support vulkan yet, nor is there access to light sensor, so there isn't much sense to compile wluma yet (I'm also eagerly awaiting vulkan support to be able to use wluma on my asahi 😜)

Oh I see :). I saw an issue about OpenGL support and Vulkan, but I guess I didn't think twice about only Vulkan support. I know there is an ambient light sensor in the macbook (what macOS uses), but does asahi not have drivers and support for it yet?

I'd be glad to be wrong, but per my current knowledge there is indeed no driver for it yet

hah, marcan himself has confirmed this an hour ago: https://www.reddit.com/r/AsahiLinux/s/viG3TAHA7i

Oh that's my reddit post asking that, and I still somehow missed his answer. Well good to know anyways


test: decouple pins for pwm test with gpio test

Description
Why: The pwm input pin is also used by gpio test on the rpi before. It is better to separate from each other.

Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Please help for code review. @vjjunnut @cobusve @brianfr @dongh @qiutongs @lundinc2 @haipengd

Qiutong is switching to master branch. Need Qiutong to merge this one first and pick it to his PR.

Ok, I will do that.

/bot run checks


change rules name from babel/* to @babel/*

this package only covers rules babel/*, provided by the discontinued package eslint-plugin-babel
the rule names of the new package @babel/eslint-plugin is @babel/*
https://github.com/babel/eslint-plugin-babel#note-eslint-plugin-babel-is-now-babeleslint-plugin-and-has-moved-into-the-babel-monorepo

Thanks for the heads up!
I think we should support both for a while to make it easier for folks to upgrade.

Released in v8.3.0.


"9" and "g" are hard to distinguish in poll codes

Describe the bug
The font weight/contrast/family choice makes it hard to distinguish between the digit 9 and the letter g, especially on a projector screen.
To Reproduce
Create a poll that contains a 9 and g in its code.
Expected behavior
The two characters should look different enough to be easily read.
Screenshots
The following poll code starts with 9g, however you cannot tell which is which without some very close analysis of the shape.
Apologies for the low-quality picture.

lol interesting.
Proposed solution? Use a different font?

could avoid ambiguous characters, 0/o is another likely one

Sticking to numbers only or letters only is the lazy solution, but it would surely work.
Alternatively we could capitalize all letters which would make most letters easier to differentiate (with the exception of 0/O, but we could avoid 0).
But I would still to change the font if it were up to me.
We could also make the code much larger.
Or we could implement a multitude of these solutions but thats all I can come up with at the moment.

If the plan is to stick to numbers and letters, erhaps we can colour code numbers and alphabet differently?
Otherwise, sticking to just numbers or just letters is a good idea, in my opinion.

I would definitely change the font to something more readable. Someone told me a while ago Helvetica is good for this kind of thing because its glyphs are fairly distinguishable.

I think the 9 and g are still a bit indistinguishable with Helvetica. Perhaps a font like Calibri?

Typeface image from freefonts.io

Helvetica is will definitely help but it wont completely solve the issue

We should do the math; perhaps dropping numbers from codes entirely doesn't reduce the entropy that much.

Any font we choose wont work with 0 and O, or l and 1, or j and i etc...
I think the best way is to go numbers only or letters only.

Implementing a custom generator for non-colliding poll code with a character length of 6 is beast on its own. So we ended up using a library called nanoid. There is some collision probability involved. Even though its minimal we don't want to take a chance :) (just as @embeddedt pointed out)
So using this id probability calculator I found out the following:

using just alphabets we will have a 1% chance of collision in a day if we were to produce 100 poll ids per hour
using just numbers we will have a 1% chance of collision in an hour if we were to produce 100 poll ids per hour

For reference with current character set (both numbers and alphabets) we will have a 1% chance of collision in 3 days if we were to produce 100 poll ids per hour
So I am comfortable with changing our character set to just alphabets. But for future reference for any changes to poll code please you math to justify your changes. Choosing a character set for poll codes isn't as straightforward ;)

This issue if up for grabs. Let me know if you want to submit a PR for it

I'm down, assign me if possible.

Should I also change the font?

Uh lets first just change the character set. Make a PR i will ping everyone involved here to check it


BLD: simplify pythran version requirement in meson

For a find_program() invocation, the version check can be inlined into the lookup. This is different from cc / cython, where version_compare is used because the list of project languages is internally responsible for finding the compiler object and doesn't have a side channel for compiler-versions-per-compiler-id.
Follow-up for #19738

there are Pythran failures in one CI job that are new - no idea why, I'll look into it.

also happening on other PRs now, so unrelated. So this is good to go.

The duplicate version number does look weird, yeah. I can take a look next week (currently getting ready to go out of town for a family celebration).

Sure, no worries at all - enjoy the celebration!


double brackets in build/generate.sh

Ubuntu 16.04 (and i think few over old LTS distros) doesn`t support double squre brackets [[ instead of [.
I think it`s not so big script and supporting old systems is more important than better readability.

@mr-tron , Can you pull a request to fix it? Thanks.


[stable/logstash] Add loadBalancerSourceRanges

What this PR does / why we need it:
Adds the ability to specify which CIDRs can access the logstash LoadBalancer service, if enabled, to help maintain a least privilege security posture.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @rendhalver

Ping @rendhalver @christian-roggia
(Hopefully this will make the PR not be stale)

tap tap. Is there anybody out there?

/lgtm

/ok-to-test
Conflicts should be solved with the upstream branch.

/lgtm cancel

/retest

/assign christian-roggia

/lgtm


Boolean validation ignores values

params do
  requires model_name do
      requires :params1, type: Boolean,allow_blank: false, desc: "params1",values: [true]
  end
end

When this API is called with params1 value as false should return an exception. But grape doesn't returns exception and the API  is successfully executed.

@sureshprasanna70 … what for exception did you expect?

@LeFnord The exception I had expected was "params1 has invalid value"

Hi @sureshprasanna70 … you are submitting a value for the param params1, with value false, so no exception is raised as expected, for this data type, it should only be raised, if the parameter is missing.

@dblock suggest to close it

@LeFnord This doesn't address the issue. Let me explain the exception I was expecting. If the value passed for the said params doesn't matches anyone of the values in the values option array then grape is expected to throw an error. In this case, when params1  of the type Boolean is passed with false as value, grape should be throwing params1 is invalid, params1 does not have a valid value. This is what I was expecting. Yeah as you said allow_blank doesn't make sense here. But the above said behavior is expected.

Oh I missed the values part. That does look like a bug, @sureshprasanna70 maybe try to write a spec. I'll reopen.

ah yeah, that makes sense, sorry overlooked the values part

It currenly throws an exception, if you try to define values for Boolean type:
Grape::Exceptions::IncompatibleOptionValues: type: Virtus::Attribute::Boolean is incompatible with values: [false]
  grape-0.19.2/lib/grape/validations/params_scope.rb:384:in `validate_value_coercion'
  grape-0.19.2/lib/grape/validations/params_scope.rb:244:in `validates'
  grape-0.19.2/lib/grape/validations/params_scope.rb:147:in `validate_attributes'
  grape-0.19.2/lib/grape/dsl/parameters.rb:107:in `requires'

@ktimothy try to contribute a spec, maybe even a fix?

@dblock I found a bug in virtus, even suggested a fix, but it doesn't look like they will ever merge it and release new version of gem: last virtus release was over 2 years ago.

It looks like there're recent commits, so I wouldn't be so sure.

@dblock

@dblock Are we open to fixing this issue?. I could contribute a spec if so..

Yes, we are open to fixing this issue.

Do note https://github.com/solnic/virtus/commit/a6f8969841247462bb05c456458baa66fce29ed8. I think this means Grape should move on to a new library. I hope someone in the community picks it up! Thanks @solnic for providing a valuable project to us for all the years.

Do note solnic/virtus@a6f8969. I think this means Grape should move on to a new library. I hope someone in the community picks it up! Thanks @solnic for providing a valuable project to us for all the years.

Dry-rb maybe?

Dry-rb maybe?

Looking for PRs!


Question/Enhancement : Does the http post object include device info( ex. uuid ) ?

What is the structure of http post object . that is sent to the server ? I went through the documentation , but it seems like it does not send anything except location details.
It would make sense if it sends device details like device model and device uuid (universally unique identifier)
. I am moving my logic from client ( i had my own async task with custom logic , so i don't know how does the object look like )  to server side , so sending only location object does not help.  I am sure people are using some sort of hacks to do so :p
Am i missing something ? Currently , any config parameter to post data like device info ? Thanks.

The HTTP body is location data only. You can add your own HTTP headers, ex a x-uuid-token or any other token you'd like to identify your users with the httpHeaders options. Headers are set as keys and values on the httpHeaders object. Content type is automatically set to application/json.

Yeah ! I know , it can be passed in header. But , headers don't seem to be the right place to do so. Currently , I am using headers though. Passing as body parameter seems better.

Another option is request url. In fact I'm using it for matching location with user in db.

Oh yes , I  never thought of that. I will try. can be closed.

@mauron85 Is it possible to change Content-Type? It seems that httpHeaders: {'Content-Type': 'application/x-www-form-urlencoded'} does not work.

May I ask @smchae with which device type and iOS version? I noticed that ajax requests got problems since iOS 10.3.1 on REAL devices only...

@smchae no content-type is hardcoded to json. Even if it would be possible to change content-type, body would be json string and not urlencoded.
https://github.com/mauron85/cordova-plugin-background-geolocation/blob/master/ios/CDVBackgroundGeolocation/Location.m#L218

@mauron85 Thank you!

Notice: this issue has been closed because it has been reported for branch 2.x or later. It could be already fixed in v3 or is not relevant anymore. You may reopen this issue if it has been closed in error.


Make it easier to know if addon plane / Show which airplane on initial edit

Is your feature request related to a problem? Please describe.
A lot of people will come to me for help with their configurations. After looking, I'll notice most of their things are configured for ZIBO 737, or other random addon airplanes.
Describe the solution you'd like
I'd like the aircraft to be shown when you select a preset. It only shows when you close and reopen the config... but by then it's too late for some...
I searched "Landing"  without filtering the data
Clicking a config that looks like it should be generic because it displays no addon airplane name

Closing and reopening shows it belongs only to an addon airplane

Describe alternatives you've considered

Default to "Generic" aircraft. The presets might work for add-ons too and is the best starting place. I find myself nearly always clicking "Microsoft Generic" to par down the results, it would be nice if this was the default. (I know this is controversial)
Show a message (not a popup) that the preset is for an addon aircraft and will not necessarily work for every aircraft. This message could be auto displayed in the description field

Additional context
Stay Spicy! 🔥

That is issue you brought up is one reason I always try to include the name of the aircraft in every event name.  At some point about a year and a half ago, we were trying to make friendlier names, but I think it is a good practice to keep the airplane name as a prefix in the event name.  So in the dropdown menus you clearly see which events belong to a particular airplane.


feat: improve block hashes fetching

feat: improve block hashes fetching
Issue: https://github.com/0xPolygonZero/zero-bin/issues/10

@praetoriansentry simple_test.sh is failing for this PR, do you know what could be the reason... I try to run it locally and witness.json.bz2 has zero size.

@praetoriansentry simple_test.sh is failing for this PR, do you know what could be the reason... I try to run it locally and witness.json.bz2 has zero size.

I would guess there was some issue with pulling the witness temparily. I re-ran and it seems ok for now:

Curious about the double log Proof verified successfully 👀  (though orthogonal to this PR)

Curious about the double log Proof verified successfully 👀 (though orthogonal to this PR)

can't make it pass locally, maybe because of mac m1, and figure it out why is that :(

@vladimir-trifonov I think you just need to change nproc, it's not supported on Apple chips (cf my comment in #69)

@vladimir-trifonov I think you just need to change nproc, it's not supported on Apple chips (cf my comment in #69)

nproc returns 8 on my Apple M1 machine, so I think it works fine, but the simple_test.sh is still failing locally.

What's your error?

What's your error?

 ./simple_test.sh
Pulling sample witness

bunzip2: Compressed file ends unexpectedly;
        perhaps it is corrupted?  *Possible* reason follows.
bunzip2: No such file or directory
        Input file = witness.json.bz2, output file = witness.json

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

bunzip2: Deleting output file witness.json, if it exists.
   Compiling rpc v0.1.0 (/Users/vladimirtrifonov/src/rnd/polygon-zkevm/zero-bin/rpc)
   Compiling leader v0.1.0 (/Users/vladimirtrifonov/src/rnd/polygon-zkevm/zero-bin/leader)
    Finished release [optimized] target(s) in 2m 47s
./simple_test.sh: line 63: witness.json: No such file or directory
Error: EOF while parsing a value at line 1 column 0

Stack backtrace:
   0: std::backtrace::Backtrace::capture
   1: verifier::main
   2: std::sys_common::backtrace::__rust_begin_short_backtrace
   3: _main
there was an issue with proof verification

it looks like it is mac specific, or the way it saves the data and reads it, I'm looking in it...

@Nashtare I managed to run it locally and this is the output:
2024-05-08T10:54:35.809263Z  INFO common::prover_state: initializing verifier state...
2024-05-08T10:54:35.809281Z  INFO common::prover_state: attempting to load preprocessed verifier circuit from disk...
2024-05-08T10:54:35.809677Z  INFO common::prover_state: successfully loaded preprocessed verifier circuit from disk
2024-05-08T10:54:35.814027Z  INFO verifier: Proof verified successfully!

INFO verifier: Proof verified successfully! exists just once...

INFO verifier: Proof verified successfully! exists just once...

What do you mean by this? The output looks fine to me

INFO verifier: Proof verified successfully! exists just once...

What do you mean by this? The output looks fine to me

I meant that because of:
Curious about the double log Proof verified successfully 👀 (though orthogonal to this PR)

I saw that it is doubled in the github output, but locally it is not.

Ah sorry I had forgotten about this old comment. Hmm yeah maybe logging is a bit messed up on the CI. Not a big deal probably!

@Nashtare @BGluth do you guys think this PR is still relevant, after looking into #78? cc: @atanmarko

CC: @muursh
Also taking into account https://github.com/0xPolygonZero/zero-bin/issues/86 maybe we need more general approach to block ranges

This is covered with #90. Block hash optimization needs to be ported to alloy

@atanmarko The issue is different here. It was about reducing the number of RPC calls to get the 256 previous hashes needed for a block payload. This isn't tackled by #90, which calls block_prover_input() for every single block in the sequence, while once we fetched the initial 256 previous block hashes, we only need one more RPC call per following block, instead of the current 128. But this is a minor optimization.

EDIT: I wrote this while you were creating the issue, all good then :)
@atanmarko The issue is different here. It was about reducing the number of RPC calls to get the 256 previous hashes needed for a block payload. This isn't tackled by #90, which calls block_prover_input() for every single block in the sequence, while once we fetched the initial 256 previous block hashes, we only need one more RPC call per following block, instead of the current 128. But this is a minor optimization.

Right, this PR also introduced block ranges, that part has different implementation with #90. Hash retrial optimization is yet to be implemented(ported)


fix compilation issues with Rust 1.79

This PR comes in support to fix issue #221. It has been tested against various versions of Rust: 1.79, 1.75, 1.66 and 1.80.
It just adds two use std::mem::size_of statements.

is there any issue with the approval process? It seems like this has been approved by two people. What am I missing here?

It must be reviewers with Write access :disappointed: I will add some more!


MWPW-148028 | Change bg remove launch load in deps js

Change bg remove launch load in deps js
Resolves: MWPW-148028
Test URLs:
Before: https://main--cc--adobecom.hlx.live/drafts/mathuria/performance/remove-background?martech=off
After: https://mwpw-148028--cc--adobecom.hlx.live/drafts/mathuria/performance/remove-background?martech=off

Validation done on the below pr :
https://mwpw-148028--cc--adobecom.hlx.live/products/photoshop/remove-background
config is seen of stage:

analytics calls are rendered as choice

Closing this PR as Jeff will share a different dependency file with only launch loading fix


[SPARK-39394][SPARK-39253][DOCS][FOLLOW-UP] Fix the PySpark API reference links in the documentation

What changes were proposed in this pull request?
This PR is a followup of https://github.com/apache/spark/pull/36782 and https://github.com/apache/spark/pull/36647. Both PRs missed changing the URLs in other places in the documentation.
Why are the changes needed?
To fix the broken links so users can read the correct documentation.
Does this PR introduce any user-facing change?
Yes, it fixes the broken links in the Spark documentation.
How was this patch tested?
Manually tested.

Could you make a backport to branch-3.3?


Norwegian Bokmål translation

I don't want this in Crowdin, and I am hoping you can be convinced to use Weblate instead :)
Edit: I can help set it up, and will fix the source strings if it is done.

I don't want this in Crowdin, and I am hoping you can be convinced to use Weblate instead :)
Edit: I can help set it up, and will fix the source strings if it is done.

You don't necessary need to use Crowdin. I actually only care about the pull requests. It's up to the translator to decide the tool to use.

well :point_up:  - you dont have to use it ...
And I'm aware of the Crowdin downsides - my main problem is: Weblate has an UI, non-programers can use, if it got better I'll migrate all projects to it ...
tldr: sadly if you try to convince e.g. your sister to translate stuff it wont work with weblate well :(

@6543 If you mean keep drive-by translators out, it isn't much of an issue with the level of overview offered. Try the Zen mode if you want something more functional.
My problem is I can't do good work on Crowdin, and even if I am alone there, it is a lot more work than it needs to be.

ok I'll exclude Norwegian for crowdin - and what do you rever to by "Zen mode" ?

@6543 Zen mode in Weblate is the one I use. Similar to Pootle if you used that.
https://docs.weblate.org/en/latest/user/translating.html?highlight=zen#zen-mode

@comradekingu Is the PR ready to merge?

@helloworld1 I'd rather sink the effort.
For the month in passing, the source strings aren't fixed, no strings have changed on Crowdin, and I made
https://github.com/andOTP/andOTP/pull/942/files

Closing for no additional actions.


fix return position in regionfuse.py

I move the "return"  out of   the  "for loop " of batch_size.

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


[WIP] Implement gcd and lcm

This PR adds the functions gcd and lcm for cupy.
Currently lcm is using gcd in the kernel itself. I want to test more to see if this is necessary or calling it externally provides the same performance.

While implementing this I came across some strange behaviour,
simple_ufunc = cupy.core.create_ufunc(
    'simple_ufunc',
    ('b->b', 'h->h', 'i->i', 'l->l'),
    'out0 = in0')

a = cupy.array([True, False, False])
b = cupy.array([False, False, True])
simple_ufunc(b)

The above works even though we never specify bool in the accepted types list, instead it permits it by typecasting it to the first type in the list(if we had written, h->h before b->b it typecasts to int16 instead of int8). Is this a bug or expected behaviour?

This is the expected behavior.
create_ufunc is undocumented, but for example cupy.subtract raises TypeError for bool inputs. Please check its implementation.

The performance benchmark for gcd and lcm are as follows
gcd

size = 100000
numpy
gcd                 : 13360.778 us   +/-687.684 (min:12873.837 / max:16644.847) us
cupy
gcd                 :    11.630 us   +/- 0.938 (min:   11.008 / max:   17.261) us    348.258 us   +/- 2.270 (min:  344.192 / max:  356.928) us

size = 1000000
numpy
gcd                 : 131831.420 us   +/-1681.092 (min:129864.742 / max:137775.571) us
cupy
gcd                 :    23.921 us   +/-22.992 (min:   12.101 / max:  148.400) us   3245.719 us   +/-20.154 (min: 3233.440 / max: 3344.928) us

size = 10000000
numpy
gcd                 : 1327643.797 us   +/-16034.114 (min:1319980.853 / max:1446820.613) us
cupy
gcd                 :    22.656 us   +/-16.292 (min:   13.221 / max:   73.323) us  32120.730 us   +/-18.294 (min:32102.047 / max:32217.663) us

and for lcm

size = 100000
numpy
lcm                 : 14097.452 us   +/-669.122 (min:13646.137 / max:17272.843) us
cupy
lcm                 :    11.926 us   +/- 3.329 (min:   10.634 / max:   32.183) us    366.765 us   +/- 3.625 (min:  362.912 / max:  386.304) us

size = 1000000
numpy
lcm                 : 140687.834 us   +/-4234.880 (min:137613.297 / max:154011.181) us
cupy
lcm                 :    17.377 us   +/-13.136 (min:   12.605 / max:   88.989) us   3433.353 us   +/-12.278 (min: 3425.824 / max: 3500.032) us

size = 10000000
numpy
lcm                 : 1395407.041 us   +/-11416.222 (min:1389399.977 / max:1476812.210) us
cupy
lcm                 :    21.779 us   +/-10.210 (min:   13.778 / max:   71.256) us  34041.828 us   +/-10.758 (min:34025.921 / max:34093.697) us

This averages at a 40 times speed up for both lcm and gcd compared to numpy

@asi1024 can you please review ?

Jenkins, test this please.

Jenkins CI test (for commit f874420b30e0bc9a7e4a4b0b34add9e4d1aa71cb, target branch master) succeeded!

LGTM. Thanks for your contribution!


Is there a way to package executable files?

I'm trying to use compose desktop to build app on windows.
As so far, it works pretty well.
But I found I can only get a installer file after packge with the targetFormats as follows.
 targetFormats(TargetFormat.Exe, TargetFormat.Msi)
Is there a way to get an executable file?

Can anyone answer it?

It would be great to have this ability!..

Am I correct, that the question is about the possibility of creating portable apps?
This is not possible at the moment, as far as I know.

Okay thank you!
Then, are there plans for future support?

No, no such plans at the moment

Using a "createDistributable" might solve your problem

Using a "createDistributable" might solve your problem

Thanks for your reply.
I got executable files in binaries folder.
Although it requires resources in folder to run, but it that's also better than an installer file.

Hello,
At this day, is there still no plan for that?

Until now, it's not built-in in jpackage as far as I know
It's possible using third party tools that create exe, like launch4j
The Gradle plugin
https://github.com/TheBoegl/gradle-launch4j

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Page with actors and roles

Is your feature request related to a problem? Please describe.
I remember us having a page dedicated to list the actors and roles that interacts with Compliant Kubernetes and now it is not accessible/available?
This makes it strange to reference things like "super application developer" which used to have a defined meaning but now it just looks a bit weird. (And it would be beneficial to us to have clear target audiences for when we write docs or similar.)
Describe the solution you'd like
Either dedicated page or parts of a page that describes the roles that interact with CK8s.

@aarnq We now have a Glossary page and the roles were updated accordingly. Can we close this issue?

Yes :+1:


Network-topology independent consensus configuration

At the moment, our network topology leaks into consensus. The user passes the list of addresses on the command line when starting the replica, and the length of that list determines the quorum. That has the following problems:

Operator errors can be devastating: making an error when starting a node (as opposed to formating the data file) can lead to data loss
Not enough flexibility --- we want things like "a cluster is identified by a DNS record which holds superset of replica IPs"

To fix this, we need to do two things:

persist configuration (just the replcia_count at the moment) into the superblock  (idea for the cli: --replica 1/6, first out of six).
change MessageBus such that it doesn't assume that nth replcia is nth IP.

What if we separated these?
--addresses is a pool of at least replica_count + standby_count addresses (but there can be more).
--listen is a single address/port for the replica itself to listen on.
--addresses are in no particular order — the address:replica mapping is determined by the header.replica of the first message received. Eventually when we support dns, addresses can be one or more dns record, each of which can correspond to one or more addresses.
(And we could add in a unique identifier in the replica's data file when it is formatted to guard against multiple replicas sharing the same index).

Yeah, that’s roughly the plan we discussed on the serverless meeting today!

At the moment, our network topology leaks into consensus.

@matklad great insight—gets to the heart of it.

--addresses is a pool of at least

@sentientwaffle great proposal overall. Also for the SuperBlock to know the replica's identity (and cluster quorum size).
I think we could allow --addresses to be less than replica_count + standby_count, provided all replicas share some "superhub" address that they can gossip through.

from chat with joran:
If we don't say that ith address is the ith replica, we need either:

an explicit handshake message on connection
a "broadcast" API for message bus to send the initial ping without knowing recepients

Adding a "broadcast" capability to a MessageBus seems like a good idea for a different reason -- some message busses might support native broadcast/multicast capabilities.

Closed by this pair of PRs:

https://github.com/tigerbeetledb/tigerbeetle/pull/546
https://github.com/tigerbeetledb/tigerbeetle/pull/554

If the operator messes up the order/quantity of IPs, they:

can't cause a data loss
would get a bunch of errors in the log about misconfiguration

We still require to pass IPs in the correct order, but fixing that adds a bunch of complexity, which seems rather fundamental!


Checking project activation criteria for ODP Project

Based on https://finosfoundation.atlassian.net/wiki/spaces/FINOS/pages/75530376/Activation , the following items need to be provided in order to request project activation for ODP.
I've added notes close to each item
QUALITY & SECURITY

[ ] Development Process - Repo Permissions are configured according to FINOS guidance. CI/CD is applied (where possible). TODO - manage and document versioning
Build & Release	- TODO - create 0.9 tag and release in GitHub . Add docs in README re. versions
[ ] Security - ODP uses WhiteSource integration to run continuous scanning. TODO - No OWASP Top 10 warnings are present in the code (maybe use barista?)
[x] Documentation - Check https://github.com/finos/open-developer-platform/ and http://odp.finos.org/docs/what-is-odp

DIVERSITY & VIABILITY

[ ] Community - Vendors, project leads and DevOps specialists are the profiles that compose the ODP team; although alternating, vendors (like WhiteSource, RedHat and Fossa) keep a constant presence. Several FINOS projects rely on ODP collaboration tools (ie meeting attendance tracking, website automated publishing, artifact release automation, etc). TODO - validate this with PMC - would be great to ask for a testimonial from FDC3, Plexus, Alloy and Perspective projects, that can be published on odp.finos.org
[ ] Project Team - ODP works closely with the OSR initiative to advance the FinServ Delivery acceleration. TODO - validate this with PMC
[x] License - ODP does not ship any runtime binary; outbound licenses are documented on github.com/finos/open-developer-platform
[x] Trademark - Trademark is enforced in odp.finos.org and github.com/finos/open-developer-platform
[x] Progress - Roadmap is available on odp.finos.org/docs/roadmap and can be tracked on https://github.com/finos/open-developer-platform/milestones
[ ] Versioning - TODO Release 0.9 (cleanup actions code first)
[ ] FINOS Support - The ODP Team have always managed and executed on their backlog independently - TODO - validate this with PMC

GROWTH & ADOPTION

[ ] Usefulness - TODO - similar to the Community item above
[x] Status Badging - Check badge in README.md , currently stating INCUBATING
[ ] Compliance - TODO - enforce license in file headers
[x] Transparency - Done, read more on http://odp.finos.org/docs/team

A new issue have been created to walk through the checklists, see https://github.com/finos/open-developer-platform/issues/107 .
Closing this as dup, but some content here may still be useful.


Allow use of SEED when creating local wallet DID

Update the /wallet/did/create endpoint to allow the use of an optional SEED when creating a new local DID
Add a new startup parameter --allow-insecure-seed-local-did to enable the use of this new SEED parameter (if the option is not provided on startup then the SEED parameter will not be available when creating a local DID.
Consider as well providing a way to import an explicit public/private key pair (vs. indirectly via a seed) so that an existing key pair can be imported into an Aries Wallet.
See Issue #1657  for the background discussion

#606 may also be related

@ianco this has been resolved

@DaevMithran please show how this can now be done

@tdiesler
I added wallet startup parameter: --wallet-allow-insecure-seed which will support for seed in wallet/did/create route
The seed is not added in schema of wallet/did/create route as it can create confusion.

... "seed" as top level attribute or as an option?

Just as a reference for others, it seems the change has been merged in PR #1705

@tdiesler seed is a top level attribute


Change license from CC-BY-SA to CC-BY

Motivation (discussion on the Carpentries mailing list): https://carpentries.topicbox.com/groups/discuss/Td64229aeb252a027
In short, the motivation is to simplify reuse for those who wish to take parts of our lessons and remix them into material which is CC-BY.
At the team meeting 2019-08-12 we have decided to change the license to CC-BY provided that all contributors to this lesson material agree to this change.
This issue will track the progress of this change.

@janusvm @Vathasav @wikfeldt can you please comment whether you agree to this change?

I agree to a license change to CC-BY. Richard agrees via https://github.com/coderefinery/git-intro/issues/192#issuecomment-521359880.

I agree to a license change to CC-BY :+1:

I agree to a license change to CC-BY

I agree to a license change to CC-BY.


Add patch as suggestion to PR

When the build breaks, add patch as suggestion

It looks totally possible to do with review comments: https://docs.github.com/en/rest/reference/pulls#review-comments
FUN!

This seems very straightforward. This little code snippet posts a review comment with a suggestion.
  const octokit = new Octokit({ auth: `SUPER_SECRET_TOKEN` });
  const response = await octokit.rest.pulls.createReviewComment({
    owner: 'spoonlabs',
    repo: 'sorald',
    commit_id: 'f88c94e4697bbfb40f782a3c6365861db3db0d71',
    pull_number: 534,
    body: '```suggestion\nthis is better\n```',
    path: 'src/main/java/sorald/Main.java',
    start_line: 7,
    line: 12,
    start_side: 'RIGHT'
  });
  console.log(response);

Here's the comment that was actually posted: https://github.com/SpoonLabs/sorald/pull/534#discussion_r633542017

So, I'm satisfied in that this is totally doable in terms of the GitHub API features. Before we can make this happen, we need a way to extract some more information from diff hunks, opening a new issue for that.

Sounds like a good idea! The implementation is also nice. But I am assuming that the POST request would require some kind of token in case the repository with which buildbreaker is integrated is private?

A GitHub API token is always available to workflows. When a PR comes from a fork, that token is however read-only, which may pose problems for external pull requests, but I think it should still allow to post a comment. Haven't tried it yet though. But this is a prototype at this stage, so it doesn't really matter too much, we'll figure it out as we go along.
As for private repositories, the same things apply there. And we aren't really concerned with private repos at this point, if there's anything in particular we need to add for private repos and someone actually requests it, we'll consider it then.

external pull requests

What do you mean by "external pull requests"?

if there's anything in particular we need to add for private repos and someone actually requests it, we'll consider it then.

Yeah, sure. I was just curious about the GitHub APIs functioning. I worked with them 2 years ago.

external pull requests

What do you mean by "external pull requests"?

PR from a fork, i.e. not from within the same repository. The API token is then limited to read-only, and secrets are unavailable.

Oh, okay. Yeah, I think it should allow to post a comment. The APIs should replicate the GitHub's interface behaviour in my opinion.

The APIs should replicate the GitHub's interface behaviour in my opinion.

They do, and more to boot. But it's a matter of permissions: can a read-only token write a comment?
After briefly trying it out, it appears that it cannot. Which is reasonable, considering it being read-only. It's possible sorald-buildbreaker will have to be turned into a GitHub bot to fully realize it, but we can still continue with this prototype.

It's possible sorald-buildbreaker will have to be turned into a GitHub bot to fully realize it

Oh, okay. I was quite looking forward to the patches when I break build in diffmin. 😅

Oh, okay. I was quite looking forward to the patches when I break build in diffmin. sweat_smile

That will still work, because your PRs are internal to the repository. They don't come from forks.

Oh, right. I lost track that we were talking about the external pull requests only.


Example Project Deprecated

I downloaded the code to see how this works and got this message.
Your Flutter application is created using an older version of the Android
embedding. It's being deprecated in favor of Android embedding v2. Follow the
steps at
https://flutter.dev/go/android-project-migration
to migrate your project.

Fixed by #62


HV-540 removing the repository settings from the pom.

adding a sample settings.xml to make it easier to get started. The settings file comes from the jboss wiki - http://community.jboss.org/wiki/MavenSettingsExample-Users
Not sure whether we should really have all these examples in the settings.xml or whether only what's needed for the JBoss repo. Thoughts?

I'm fine that! Advanced users can copy the needed parts and beginners the whole file and keep the builtin examples.


Can I change the response language to something other than English?

I want to output the language of a country other than English (e.g. Japanese, Korean, etc.) in the bot's pull request comment responses.

https://github.com/Codium-ai/pr-agent/pull/732#issuecomment-1975099159

I can't seem to find it in the environment configuration, is there any way to change the output language?

https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml

use the 'extra_instructions' field of each tool
https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L38

/review --pr_reviewer.extra_instructions="answer in zh-tw"

How about something like this?
in pr_agent.toml
[pr_custom_prompt]
prompt = """\
The description of 'code suggestions', 'pr description', and 'code review' should be in the Japanese language.
"""

you are using the wrong configuration. Use "extra_instructions" for the relevant tool
anyway, the field names are defined in the prompt (in English). So you cant change them (the left column)
But the answers (right column) can be given in Japanese. give a clear coherent prompt.

you are using the wrong configuration. Use "extra_instructions" for the relevant tool
anyway, the field names are defined in the prompt (in English). So you cant change them (the left column) But the answers (right column) can be given in Japanese. give a clear coherent prompt.

@mrT23
Thank you for your response. I resolved the issue using extra_instructions. I appreciate you for creating such a wonderful product.

p.s
https://github.com/Codium-ai/pr-agent/pull/1355#issuecomment-2483338247

@mrT23
Does extra_instructions configuration only allows at Pro license like you said at this #1355 issue?
I tried to change language but it only applies to /describe command.
I'm currently using github action code below.
on:
  pull_request:
    types: [opened, reopened, ready_for_review]
  issue_comment:
jobs:
  pr_agent_job:
    if: ${{ github.event.sender.type != 'Bot' }}
    runs-on: ubuntu-latest
    permissions:
      issues: write
      pull-requests: write
      contents: write
    name: Run pr agent on every pull request, respond to user comments
    steps:
      - name: PR Agent action step
        id: pragent
        uses: Codium-ai/pr-agent@main
        env:
          OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          CONFIG.MODEL: "gpt-4o-mini"
          CONFIG.MODEL_TURBO: "gpt-4o-2024-08-06"
          CONFIG.FALLBACK_MODELS: "gpt-4o-mini-2024-07-18"
          pr_reviewer.extra_instructions: "Answer in korean" # /review
          pr_description.extra_instructions: "Answer in korean" # /describe
          pr_questions.extra_instructions: "Answer in korean" # /ask
          pr_code_suggestions.extra_instructions: "Answer in korean" # /improve

Does configuration setting wrong? 😢

@haesungJoo
correct. use good models


el-select is not able to collapse when click some where other than the component itself

Issue Type:

[x] Bug
[ ] Feature
[ ] Help

Version & Environment:
0.7.4
Description:
click el-select to expand the options. not choose any option but click some where else in the page. the select is not auto collapsed.

it look normal here in me, can you upload some code on stackblitz.com ?


Keep selected Properties Panel Tab when switching element

Currently the Prperty Panel is always reseted to the first tab when clicking on a different diagram element. It should keep the tab is applicable to the element type selected.
Example: I want to check formKey for all User Tasks on a BPMN Model. I select the "Form" tab and after that I can select every User Task. Currently this is annoying as always the Tab "General" is selected (and mouse way is long)

Implemented with the following commits:
bpmn-js-properties-panel:
https://github.com/bpmn-io/bpmn-js-properties-panel/commit/f3e2e16046e5ec82b7250cc10a8b18f5de144111
cmmn-js-properties-panel:
https://github.com/bpmn-io/cmmn-js-properties-panel/commit/666974a9e146198635208a577c3da41e9ec414d6


Module/controlfreec/1.2

Pull Request Checklists
Important: When opening a pull request, keep only the applicable checklist and delete all other sections.
Checklist for New Module
Required

[x] I used the cookiecutter template and updated the placeholder rules.

[x] The snakemake rules follow the design guidelines.

[x] All references to the rules object (e.g. for input files) are wrapped with str().

[x] Every rule in the module is either listed under localrules or has the threads and resources directives.

[x] Input and output files are being symlinked into the CFG["inputs"] and CFG["outputs"] subdirectories, respectively.

[x] I updated the final target rule (*_all) to include every output rule.

[x] I explained important module design decisions in CHANGELOG.md.

[x] I tested the module on real data for all supported seq_type values.

[x] I updated the default.yaml configuration file to provide default values for each rule in the module snakefile.

[x] I ensured that all symbolic links are relative and self-contained (i.e. do not point outside of the repository).

[x] I replaced every value that should (or might need to) be updated in the default configuration file with __UPDATE__.

[x] I recursively searched for all comments containing TODO to ensure none were left. For example:
grep -r TODO modules/<module_name>/1.0

If applicable

[x] I added more granular output subdirectories.

[x] I added rules to the reference_files workflow to generate any new reference files.

[x] I added subdirectories with large intermediate files to the list of scratch_subdirectories in the default.yaml configuration file.

[x] I updated the list of available wildcards for the input files in the default.yaml configuration file.

Checklist for Updated Module
To be completed.

@Kdreval @lkhilton I've updated the module. Also included unmatched/matched rule separation for running controlfreec.

Ah shoot - I just made a tiny edit to my snakemake and it cancelled the merge approval. Could someone approve it so I could merge my updated version into master?


Not all text showing in issue 'Edit'-mode

Gitea server: Codeberg
Gitea version (or commit ref): v1.12.6

Description
This is a minor issue. I keep track of delightful-funding resources in an issue that I regularly update with new entries.
Recently when clicking 'Edit' the text-entry window no longer shows the full text. The full text only appears after a click inside the input area. After this a subsequent Save or Cancel and pressing Edit again will yield all text as expected, but after reloading the page the issue can again be reproduced.
I am using Firefox 73.0.1 on Ubuntu 18.
(Note: I created an issue at Codeberg that points to this: https://codeberg.org/Codeberg/Community/issues/338 )
Screenshots

Probably another one of those EasyMDE/SimpleMDE bugs. Long term solution will be https://github.com/go-gitea/gitea/issues/10729 and I plan to take a shot at that soon.

Thanks for working on a long term solution @silverwind - what do you estimate the timeline to be?
Is there a short-term solution for fixing SimpleMDE bugs? Why did you give up on EasyMDE?

This issue seems pretty old, maybe it has been fixed?
And the edit mode has been switched to editable content mode and deployed on try.gitea.io
Feel free to try it and report bugs.

Thank you. Yes, this is the right action. I have not experienced the issue anymore and also closed the downstream Codeberg issue that is related.


do not copy object directly

Link to bug or description of what is the issue fixed is helpful in a PR especially when someone visits this PR later

i'd like to but actaully i don't know the bug detailly. behaviors is sometimes ladder players got others code saved. i don't find the exact bug code now , and this is just an attempt fixing.
and i think the don't copy object describe what i changed 😂


Updated the iOS documentation

This PR updates the getting started documentation for the users.

Its merged into the master in the form of fixup patch


rtl8821au: unstable-2022-12-22 -> unstable-2023-03-22; fix build on kernel 6.3

Description of changes
ZHF: https://github.com/NixOS/nixpkgs/issues/230712
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

2 packages marked as broken and skipped:

linuxKernel.packages.hardkernel_4_14.rtl8821au
linuxPackages_hardkernel_latest.rtl8821au

1 package failed to build:

linuxPackages_5_4_hardened.rtl8821au (linuxKernel.packages.linux_5_4_hardened.rtl8821au)

20 packages built:

linuxKernel.packages.linux_4_14.rtl8821au
linuxPackages_4_14_hardened.rtl8821au (linuxKernel.packages.linux_4_14_hardened.rtl8821au)
linuxKernel.packages.linux_4_19.rtl8821au
linuxPackages_4_19_hardened.rtl8821au (linuxKernel.packages.linux_4_19_hardened.rtl8821au)
linuxKernel.packages.linux_5_10.rtl8821au
linuxPackages_5_10_hardened.rtl8821au (linuxKernel.packages.linux_5_10_hardened.rtl8821au)
linuxKernel.packages.linux_5_15.rtl8821au
linuxPackages_5_15_hardened.rtl8821au (linuxKernel.packages.linux_5_15_hardened.rtl8821au)
linuxKernel.packages.linux_5_4.rtl8821au
linuxPackages.rtl8821au (linuxKernel.packages.linux_6_1.rtl8821au)
linuxPackages_hardened.rtl8821au (linuxPackages_6_1_hardened.rtl8821au)
linuxKernel.packages.linux_6_2.rtl8821au
linuxPackages_latest.rtl8821au (linuxKernel.packages.linux_6_3.rtl8821au)
linuxPackages_latest-libre.rtl8821au (linuxKernel.packages.linux_latest_libre.rtl8821au)
linuxPackages-libre.rtl8821au (linuxKernel.packages.linux_libre.rtl8821au)
linuxPackages_lqx.rtl8821au (linuxKernel.packages.linux_lqx.rtl8821au)
linuxPackages_testing_bcachefs.rtl8821au (linuxKernel.packages.linux_testing_bcachefs.rtl8821au)
linuxPackages_xanmod.rtl8821au (linuxKernel.packages.linux_xanmod.rtl8821au)
linuxPackages_xanmod_latest.rtl8821au (linuxKernel.packages.linux_xanmod_latest.rtl8821au ,linuxPackages_xanmod_stable.rtl8821au)
linuxPackages_zen.rtl8821au (linuxKernel.packages.linux_zen.rtl8821au)


Is there any place where we catalog snabbdom-compatible UI components?

I'm starting to build up a catalog of pure snabbdom based UI elements, and I'm wondering if:
a) we have any place where we collect/share these
b) anyone else out there building snabbdom elements that are shareable
to give an example, here is one I've been working on very recently, exposing a chrome devtools inspired, re-usable timeline component:
https://github.com/mreinstein/snabbdom-timeline
If we don't have one, maybe something like https://bit.dev/ could be used to curate a collection of high quality ui components?  Thoughts?

some more modules:
https://github.com/mreinstein/snabbdom-drawer
https://github.com/mreinstein/snabbdom-property

https://github.com/mreinstein/snabbdom-tabs

https://github.com/mreinstein/snabbdom-valve

Those can be added to the readme in this section. It would probably be a good idea to re-structure that section with a few sub-sections etc.

How about in a wiki here in the repo?

The github wikis don't get much traffic and they often end up being neglected. It might be better to just put them in a markdown file in the project root.

https://github.com/mreinstein/snabbdom-knob


six six six

Old iron, six six six :trollface:

https://github.com/RosenLo/elasticsearch-agent/blob/master/es-agent#L100  not pythonic enough.

Yeah, this is my first project when I was learning Python. it can be better. when I'm free, I'll consider improving it.
Old iron, six six six  :joy:


Fix HTMLImage calling setState in Image.getSize callback after component unmount

This is a fix for https://github.com/archriss/react-native-render-html/issues/183. Just setting a property unmounted on componentWillUnmount and checking if it's true inside Image.getSize callback and if it is, then it exists immediately without executing setState.

Hello @Exilz,
The reason I changed the HTMLStyles, is because the component crashes the entire app if an element has a css function inside the style prop, for example something like this <div style="width: calc(100% - 80px)">; something like this made a live app fetching pages to crash when trying to display them. I had to create a fetcher and apply a filter to fix it before I change this plugin to change the calc function to 100%. Really it's serious; you should either leave it as it is and change it to 100% or remove it completely. Check the code:
if (value.search('calc') !== -1) {
    return [key, '100%'];
}

I know there are more css function and maybe a more complete solution would be more suitable, but that was argent and fixed a terrible crash when trying to load html using this component.
Maybe the component use is not intended for live site pages and dynamic code, but that was my case and it was a terrible crash.

Hello,
I have no doubt this change is needed and I plan on taking a look at it really soon.
It's just that I wished that a single PR would only fix a single bug. Could you please extract this commit and open a fresh PR with your previous explanation ? It would be easier for me to maintain the module.
I'm currently reviewing lots of commits and various issues, a new version should be out soon.

OK, I'll do it. Do you want to also create an issue about it or just a PR? I'll think for better solution to catch that cases and maybe we'll have to disqus about it, so maybe a bug report would be better so we can settle with a fix before we write any code for solving this.

I've created a new issue about the css functions crash https://github.com/archriss/react-native-render-html/issues/225


Should I still use babel-plugin-relay/macro?

Should I still use babel-plugin-relay/macro? Will the plugin replace it with its own version? Or should I do something different?

This project replaces the babel plugin with its own code. So you don't need to setup the babel plugin or babel macros.

Thanks, what should I import in order to use the graphql tagged function then?

Ah I guess I have to use it from react-relay?
import { graphql } from 'react-relay';

const GetPostQuery = graphql`
  query AppGetPostQuery($id: ID!) {
    Post(id: $id) {
      id
      title
      views
      user_id
    }
  }
`;

Well, no matter what it is from, any tag with the name graphql will be handled


feat: Support for relative paths

Is your feature request related to a problem? Please describe.
I have "liberated" many images from the public web to make my dashboard look awesome. I feel I should be serving those images directly from my host for bandwidth / privacy reasons.
I have a proxy that sits in front of my Argus installation and redirects /images to be served via the proxy and everything else from Argus. In the configuration, I call the images absolute under service.name.dashboard.icon e.g. icon: 'https://my.example.com/images/service.png'
Describe the solution you'd like
I would like the capability to utilize relative paths in the icon declaration ie icon: /images/service.png
Additional context
I have tested and noted that there are tags in source for %PUBLIC_URL% which do not work in the configuration, which I had hoped would allow me to bypass the need for this feature request.
This is an issue for me as I am running an implementation, logging the configuration in a git repository and launching a development branch before promoting to main/production. I am currently doing some hacky CI/CD build script magic to the files on each launch, and is not optimal.
Thanks again for the tool.

I'll definitely look into implementing this 👍

If I added support for relative URLs, they'd work in the browser, but any images e.g. notify.X.params.avatar would require me to add a var for the base URL in config, e.g. settings.web.base_url. I'll start work on this in the next few days


Feat/install and style button

installed button from https://ui.shadcn.com/docs/components/button
updated styles for button to match figma. Since we did not have design for all button variants I improvised following the pattern from replacing the other color values. I will follow up with Chiali to review and confirm.
Note: the primary button background is vd-text-blue. using this var as the background could be confusing.

Note: the primary button background is vd-text-blue. using this var as the background could be confusing.

@CJ-Rose can we update the token to be something else? I'd prefer if colors were named neutrally (not text or component based)

Note: the primary button background is vd-text-blue. using this var as the background could be confusing.

@CJ-Rose can we update the token to be something else? I'd prefer if colors were named neutrally (not text or component based)

yep. originally i gave them different names bc the text color is "Cloud burst" while the accents are all named as degrees of "Gothic" in the figma. but since the darkest "Gothic" shade being used is 700, i think its fine to change vd-text-blue to vd-blue-900

Sounds good. I'm happy to make that change in this PR.


When Levels are re-defined, Levels not cleared from objects

When a user re-defines a level to be a different start and end value, the Level assignment batch goes through and assigns all records to the new levels. However, if a record has an old level field populated and it now meets no level definition, it retains the old information. This can cause confusion by mis-labeling records. The level field should be cleared for records which no longer meet any level criteria.

**lurch: add

Tracking W-017872

Included in beta release 3.94 (Beta 12)

Included in production release rel/3.94


Fix bug with timeclash and editm

Codecov Report

Merging #183 (ee2c624) into master (73cce49) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #183      +/-   ##
============================================
- Coverage     53.06%   53.04%   -0.03%
  Complexity      525      525
============================================
  Files           113      113
  Lines          2186     2187       +1
  Branches        258      259       +1
============================================
  Hits           1160     1160
- Misses          948      949       +1
  Partials         78       78

Impacted Files
Coverage Δ

...edu/address/logic/commands/EditMeetingCommand.java
0.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
60.71% <0.00%> (-0.74%)
:arrow_down:

Continue to review full report at Codecov.

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


regbot: 0.4.4 -> 0.4.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/regclient/regclient/releases.
meta.description for regbot is: "Docker and OCI Registry Client in Go and tooling using those libraries"
meta.homepage for regbot is: "https://github.com/regclient/regclient"
meta.changelog for regbot is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.5 with grep in /nix/store/57rrgwx2zal6znnif84qb4m978b1r9fv-source

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
regbot
regclient
regctl
regsync

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/57rrgwx2zal6znnif84qb4m978b1r9fv-source \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A regbot https://github.com/r-ryantm/nixpkgs/archive/c79ebd3a9d8105191b3f063f6aad967ca1fbf2a5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/57rrgwx2zal6znnif84qb4m978b1r9fv-source
ls -la /nix/store/57rrgwx2zal6znnif84qb4m978b1r9fv-source/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

regbot
regclient
regctl
regsync

Maintainer pings

Duplicated of: #192358

Shell completion is missing. (for the many packages included here) (I may fix it but in another PR but not now.)


Raspberry Pi 3 and Adafruit_Python_DHT

Greetings.
I'm having a problem with the Adafruit DHT Python code.

Installed all the required packages.
sudo python setup.py install
Connected the DHT11 signal to GPIO04 (pin 7).
Tried to run:
sudo ./AdafruitDHT.py 11 4
and (after a few seconds) got:
Failed to get reading. Try again!

The DHT11 sensor is working with C and the WiringPi library.
This is a Raspberry Pi 3, fresh Raspbian install, and all the latest software updates.

pi@PI3:~/src/DHT11 $ uname -a
Linux PI3 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux

Thanks.

I have the same problem. Any plans to support pi 3?

Hrm I can't repro any issues on the Pi 3, just tried reading an AM2302 and it works great with the current lib and the latest Raspbian Jessie.  Try installing a fresh SD card image and the library again to check there isn't something else going on.
Also make sure you don't have a lot of CPU intensive things running the background.  The library works by trying to very quickly read the output of the sensor but it can get tripped up if the kernel is interrupting it to let processor intensive tasks run.
And one last little thing to check is how you're powering the device.  Give it 3.3V power from the Pi instead of 5V power--the signal line has a pull-up resistor so you don't want to have it pull up to 5V and then feed that into an input on the Pi.

I'm getting on raspberry pi 3:
  File "dht11_test.py", line 21, in <module>
    umid, temp = Adafruit_DHT.read_retry(sensor, pino_sensor);
  File "/home/pi/scripts/Adafruit_DHT/common.py", line 92, in read_retry
    humidity, temperature = read(sensor, pin, platform)
  File "/home/pi/scripts/Adafruit_DHT/common.py", line 78, in read
    platform = get_platform()
  File "/home/pi/scripts/Adafruit_DHT/common.py", line 53, in get_platform
    from . import Raspberry_Pi_2
  File "/home/pi/scripts/Adafruit_DHT/Raspberry_Pi_2.py", line 22, in <module>
    from . import Raspberry_Pi_2_Driver as driver
ImportError: cannot import name Raspberry_Pi_2_Driver````

even using --force-pi2 on setup

In fact it just my low knowlegde on python.. some related to folders and files locations... :(

I'm working on RPi3 support here https://github.com/yangl1996/Adafruit_Python_DHT/tree/rpi3-support, stay tuned ;)

@TiagoGouvea  How did you manage to resolve this? I am also getting the exact same error.

@TiagoGouvea i also have similar issue, how to solve it?

For anyone else facing the same issue that @TiagoGouvea mentioned.
Try to run your program from outside the Adafruit_DHT directory that was cloned.
It happens because when you run -
import Adafruit_DHT
It imports the Adafruit_DHT folder in your current directory instead of the one installed in your site-packages directory.
When run from anywhere else, it is working fine.
Hope this helped.

How exactly do I do this @Cartmanishere ?

I had this issue running a Raspberry Pi using resin.io
I was running python setup.py install --force-pi instead of python setup.py install --force-pi2 even though I am using a Raspberry Pi 3.
Very poor documentation for this adafruit library

@LucasAmos What issue are you alluding to? I have yet to see any issues loading and running this library on an RPi2 or RPi3? You mention using resin.io which has nothing to do with this library and then say it's poorly documented?

Thank you! This worked for me.

I got the same error in my R Pi 3 and I found a fix for it after some research.
So for those getting an error such as this one:
Traceback (most recent call last):
File "simpletest.py", line 39, in
humidity, temperature = Adafruit_DHT.read_retry(sensor, pin)
File "/home/pi/Adafruit_Python_DHT/Adafruit_DHT/common.py", line 94, in read_retry
humidity, temperature = read(sensor, pin, platform)
File "/home/pi/Adafruit_Python_DHT/Adafruit_DHT/common.py", line 80, in read
platform = get_platform()
File "/home/pi/Adafruit_Python_DHT/Adafruit_DHT/common.py", line 55, in get_platform
from . import Raspberry_Pi_2
File "/home/pi/Adafruit_Python_DHT/Adafruit_DHT/Raspberry_Pi_2.py", line 22, in
from . import Raspberry_Pi_2_Driver as driver
ImportError: cannot import name Raspberry_Pi_2_Driver
Here is the fix(as per a comment by Mr Bogd):
1. Use `sudo python3 setup.py` install during the setup installation as you are more likely to be running Python 2 but the codes require Python 3.

2. After the setup, run your .py file in any directory(home or any other) apart from the Adafruit_Python_DHT directory.
   (Use the command `cp yourpythonfilename.py yourdirectoryname/` to copy the file to your desired directory where yourpythonfilename is the name of your python file and yourdirectoryname is the name of your directory you wish to copy the file to).
   This is because the python file imports the Adafruit_DHT directory(through this line: `import Adafruit_DHT`) so it should not be in the same directory.

this error is annonying ..... I have to my project tommorow morning!!!!!


Feature/android media session

Describe the changes
Added mediaSession for Android ExoPlayer to let device know about currently used player. With this in place you can use some native features like pause/play using HW buttons on any compatible headset connected to the device, displaying playback buttons in PIP window (previous, play/pause, next), etc..
Currently using the simplest solution with usage of external ExoPlayer mediaSession extension library, which takes care of all needed mediaSession callback, and the session it self. To support more advanced features, full implementation may be needed.
Since I'm not an Android expert, it's possible that some things, or additional metadata are missing. Please consider this as MVP which is currently implemented mainly to support PIP player controls. Feel free to suggest any change or pick deeper implementation if needed.
Also added onExternalPauseToggled  event prop, which notifies client about new play/pause state, so JS can perform needed actions based on this information. For example change UI state.

Hi, what is the state with this pull request? 😊 Would be very grateful if it got merged. We are using picture in picture on Android through another library, but since current version of react-native-video doesn't have media session, there are no playback buttons :(

Just a heads up if this ever gets merged:
onExternalPauseToggled is not necessary, there is already the prop onPlaybackRateChange that should be able to do the same. I just stumbled onto this PR, I did not test it.


Include Performance evolution of netcore versions on readme or related wiki/site

Could we have in readme a table follow up the performance evolution of all netcore frameworks 1.x, 2.1.x, 2.2, 3.0?
This would provide a public overview of netcore performance improvements.
It can also help us justify a netcore migration in our companies and encourage IT to update netcore frameworks.
In this public readme we could show speed for some common use cases as presented by @stephentoub, available here.

@juniormayhe aren't the blog posts sufficient? Or TechEmpower benchmarks?
The problem is that everyone uses different benchmarks, or cares about different things, so it is EXTREMELLY hard to provide anything super-useful.
cc @adamsitnik @billwert @brianrob

No response, closing

@juniormayhe aren't the blog posts sufficient? Or TechEmpower benchmark results? ... or blog post like this one: https://www.ageofascent.com/2019/02/04/asp-net-core-saturating-10gbe-at-7-million-requests-per-second/
The problem is that everyone uses different benchmarks, or cares about different things, so it is EXTREMELLY hard to provide anything super-useful.
cc @adamsitnik @billwert @brianrob

Yes, I understand this might be hard. Every benchmark will care more or less about some aspects. I picked a sample of Steve Gordon to evaluate netcore performance on string manipulation and first runs on 3.0 were slower but after couple of executions it got similar to 2.2 and 2.1. Hope netcore 3.0 performance won't decrease!
Thanks for the heads up Karel

@juniormayhe you can also run all the benchmarks we have for testing .NET Runtimes performance in the dotnet/performance repository
the docs that explain how to do it:
https://github.com/dotnet/performance/blob/master/docs/benchmarkdotnet.md#Multiple-Runtimes
the benchmarks: https://github.com/dotnet/performance/tree/master/src/benchmarks/micro
it's more or less a single command:
dotnet run -c Release -f netcoreapp2.1 --filter * --runtimes netcoreapp2.1 netcoreapp3.0


docs: Change rabbitmq:3.13-management by rabbitmq:4.0.2-management

Changed the name of image to rabbitmq:4.0.2-management
because the page describes the version 4 of RabbitMQ and not the version 3

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

We should link to the 4.0 tag, I will make the edit.

@Abdelkrim Thank you for signing the Contributor License Agreement!

Thank you.


Remove JavaMoney From java-ilp-core

Any JavaMoney implementation should be moved to a separate library. For example, a converter between liquidity curves and a JavaMoney ExchangeRateProvider should not be part of java-ilp-core, but could be a useful standalone library.
This issue supersedes #70.

Fixed by #84


Define security contact for git plugins

Description
This PR defines security contact on two plugins:

https://github.com/jenkinsci/git-plugin
https://github.com/jenkinsci/git-client-plugin

Please approve this @MarkEWaite
cc @rsandell @fcojfernandez
Thanks!

Submitter checklist for changing permissions

Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

[ ] Make sure the file is created in permissions/ directory
[ ] artifactId (pom.xml) is used for name (permissions YAML file).
[ ] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[ ] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[ ] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[ ] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[ ] All newly added users have logged in to Artifactory at least once

Merge permission to GitHub repository

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo. If needed, it can be done using an IRC bot command. Make sure to check that the $pluginId Developers team has Write permissions or above while granting the access.

Thanks @MarkEWaite !


ios : Unable to add Events listener

Hello
With last version of plugin + last version of Cordova.
Capacitor.Plugins.AdMob is found and i can display Ads, it works.
But, i need to have some Events about ads loaded/dismissed/errors. And InterstitialAdPluginEvents is undefined.
How can we manage events ?
npm install @capacitor-community/admob
import { AdMob, AdOptions, AdLoadInfo, InterstitialAdPluginEvents } from './@capacitor-community/admob';
Best regards

How are you setting your listeners?

I tried that.
Capacitor.Plugins.AdMob.addListener(InterstitialAdPluginEvents.Dismissed,
function() {
alert('test');
});
But InterstitialAdPluginEvents is not defined.
Le mer. 3 juil. 2024 à 19:51, Saninn Salas Diaz @.***>
a écrit :

How are you setting your listeners?
—
Reply to this email directly, view it on GitHub
https://github.com/capacitor-community/admob/issues/327#issuecomment-2206895880,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJN5KOQJBLRBO6EJY7PGDW3ZKQ22NAVCNFSM6AAAAABKJ4M55OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBWHA4TKOBYGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


How to use onMouseEnter() in ag-grid?

How to use onMouseEnter() in ag-grid?

this questions isn't formed correctly. there is no onMouseEnter event in ag-Grid. if you are looking how to do onMouseEnter in the browser, then this isn't an ag-Grid questions really.


argo lint accept templates from stdin

Summary
argo lint accepts templates from stdin
Use Cases
When I use helm to deploy a template, I would like to lint the template after it has been through Helm's value interpolation and any post-processors I've defined. Tested with 2.9.4

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Care to submit a PR for this?

I would love to @simster7 but I don't know Go and I don't have the time to learn it right now. If it's still here when I get round to it then...

Can you do this?
argo lint /dev/stdin < examples/hello-world.yaml

/assign

I've actually started on a PR for this: #3734

@alexec I'll be happy to submit a PR for this feature, and also for #4981  if you want.

@alexec I'll be happy to submit a PR for this feature, and also for #4981  if you want.

@alexec we can close this I guess


Conceivable extensions and applications

I recently had another look at f3 and wondered about conceivable extensions and applications.
Is it possible to calibrate the C5, C16, C18 FFIs in the same way as the Kepler prime mission?
As it stands, f3 is not equipped for this task, since it is A) hardcoded to Kepler prime, and B) many of the "ubercalibration"-style likelihood assumptions require a large enough sample of FFIs to break significant degeneracies.
Applications to non-solar-like stars, and non-stars in general
Kepler Prime observed Active Galactic Nuclei (AGN, Smith et al. 2018), and it'd be meaningful to constrain the long-term behavior of this AGN sample.
Joint modeling the long- and short- timescales in Kepler prime?
Imagine a likelihood function consisting of a flexible Gaussian Process with many tuning parameters that fits all Q1-17 long cadence data and simultaneously fits the F3-derived photometry.  You could then warp the mean model of the long cadence similar in spirit to forward modeling spectral continuum normalization (e.g. Czekala et al 2015, Figure 3).
Is it worth investing in modernization?
Could porting some parts of the code to lightkurve alleviate the  brittle dependency of kplr?  Could recent innovations in gradient-based methods help with the large number of parameters for joint modeling projects described above?  Could some tutorials for more objects and application be helpful to expand the usefulness of f3?  Could recently released and reformatted thermal telemetry data help as regressors for long term systematics?  These modernization steps could help, but are they worth the investment?

Hey,
Thanks for writing this up! I have lots of thoughts. There's still so much low-hanging fruit in the FFIs, I really want me or a student to go back and dig in deeply.
I had an undergrad last summer automate all the hand-holding I had to do previously (which was mostly in aperture selection, trying to pick something big enough to encompass the entire PSF but small enough to not include any other stars) and we have light curves from that for the full 200,000 star sample. They're a little noisier than the artisanal light curves one might create doing aperture selection by hand, but they do decently well and exist for everything. I want to do something with those! Which might be using some population-level information or additional housekeeping data that we didn't have previously to do better detrending, as you mentioned in your final point.
To your specific questions:
Is it possible to calibrate the C5, C16, C18 FFIs in the same way as the Kepler prime mission?
I think this is really going to be a challenge. The reason that this is a tractable problem in the first place is because every year the star comes back and lands on the same pixel. We then have a free parameter which is the offset between the four orientations, which in practice matters at the 1-2 percent level. Just having the one visit in the C16 orientation means there will be an offset that should be hard to correct for in that visit. C5 and 18 might be doable. FFIs at the start of campaigns rather than the end will have thermal issues that will be challenging, and it is better if the pointing is consistent between the two, rather than just before and just after a thruster fire, for example. But maybe! From my perspective it's more work for less effort than mining the Kepler field further.
Applications to non-solar-like stars, and non-stars in general
I want to do non-solar-like stars very much, and also look at the effects of e.g. metallicity on photometric variability (see Karoff et al. 2017 for example). Krista Smith and a student are looking at AGN in the FFIs with a different tool. We compared ~10 targets, five which I selected and five which they selected. I was happy with the performance of f3 for bright stars from that comparison; they might be doing better on very faint objects, which is perhaps not surprising given that's where their science is and ours isn't. But I definitely want to go back at hit up the rest of the stars. I'm imagining something like a random forest classifier that gives the relative importance of various stellar parameters on observed variability.
Joint modeling the long- and short- timescales in Kepler prime?
You've hit on another of my dreams. I would like to be able to do this. The main issue is that our errors are largely dominated by systematics in our uncertainties of the detectors, rather than in photon noise (which we know at the 10ppm level, since Kepler works!) So writing down a likelihood function is challenging. I think you'd also have to go back to the pixel-level data and try to build your own light curve, since the smaller apertures for PDC will have smaller contamination so your astrophysical signals (eg from an EB) will look different in the FFIs than in the long cadence data. I've not quite been convinced by any of the science cases that a probabilistic light curve at the 30-minute level that treats all that and incorporates the FFIs leads to an interesting science result that we don't have now---but I'm open to being convinced that one exists and it's worth pursuing!
Is it worth investing in modernization?
I think it depends on the ultimate userbase. It might be 2 people plus their students, in which case a lot of the ease of use things become less important. But I think gradient based methods/GPU computing could be a useful thing to get the best photometry out of the FFIs---if we can model all the stars in the detector simultaneously, that might give us a big gain! Similarly housekeeping data, especially on pointing, might give us the opportunity to have a big gain.
There's another problem I'm interested in. Luan Ghezzi in Brazil has a Master's student working on this a bit, but he's also applying for phd programs and might leave. There are 200,000 stars observed by Kepler but 4.5 MM in the FOV. Many of the other 4.3 million we will be sensitive to them as long-term variables, eclipsing binaries, or in some cases hot Jupiters. Something in a 3 day orbit should randomly catch a couple points in transit, which could be followed up with TESS data in other special cases (or eventually with PLATO). I think there are ways to efficiently find the stars with outliers and then categorize them. It'll get complicated with SPSDs, but I think they're separable from astrophysics at the pixel level.
Also, I'm sure you're trying to limit your travel right now but if you wanted at some point to come down for extended time and hack on some of this we have the resources to make that happen!

Great food for thought here, thanks!!
One admittedly niche science case stems from the desire to register ancillary (e.g. ground-based spectroscopic) observations to space-based photometry, as in the case of RV jitter, or starspot spectral decomposition.  Having a probabilistic lightcurve would inform both the stellar rotation phase, and total spot coverage, assuming the ancillary data were spread over timescales comparable to stellar activity cycles.  Again, niche.  I know of a handful of stars where this registration is interesting.
I computed coarse zero-points for the K2 FFIs for C5/16/18, for which we have some of these ancillary observations in hand.  I used sep rather than mahotas, did not tune aperture choice, and ran for entire channels rather than localized postcard regions.  Here is a first pass of the zero points of C16 and C18 relative to C5 for the channel possessing M67:

Indeed, your 1-2% level channel differences are conspicuous in C16, as well as the ~1% / year throughput loss (your Figure 2) by the time we get from C5 to C18.
As a double check, I ran the same custom machinery on Kepler prime, and applied it to KIC 4863614, which appears in your Figure 10, third panel from the top.  Its 10% amplitude should be conspicuous, even with my crude zero-pointing strategy.  I get about the same trend as what f3 measures (yay).  I arbitrarily assigned 1% errors, showing how much better f3 does in precision.

Re: Joint modeling the long- and short- timescales in Kepler prime---I think I can write down that likelihood function!  The key is putting in smooth functions---like low order Chebyshev polynomials---as the mean model, and then including GP kernels with comparable power on long timescales: nearly degenerate, but the mean model must also pass through the rigid FFI anchors.  The GP or mean-model also contains the physics of interest (e.g. high frequency sine waves).  Indeed, sketching this on a board in Sydney would be easier than writing out here, but I think it can be done.  Folks here at Kepler GO have emphasized the prospect for making (what I'm calling) "accuracy lightcurves" from the long-cadence data.  Effectively, repeat the coarse zero-pointing for each TPF slice and then get a really imprecise-albeit-accurate lightcurve, which can be used to penalize the likelihood if the Chebyshevs get too big.  I don't think this step is required, but it's possible so why not use it.  You're right about asking what's the science case for this tech.  I guess it comes back to registering ground-based observations to the photometry.  At a given epoch you get a rotational-phase corrected estimate for the Kepler-band flux.  This value and uncertainty are only interesting in narrow contexts such as large-amplitude variables with large long-term trends, which indeed was not Kepler's bread and butter.
Re: the 4.3 million other sources.  I guess it comes down to how much better f3 does than ground-based?  PanSTARRS, ASAS-SN, and other programs have (or will have) many more data points, but (I think) have higher point-to-point uncertainty than what f3 can achieve?  The discussion of classifying variables with sparse photometry reminds me of the PLASTICC competition ran on Kaggle.  The winning result has a slick paper.

This is all really cool!
The point about being able to register spectroscopic information to the longer-term variability observable over Kepler timescales is well-taken. Even if we could only do an exceptional job for a subsample of stars, perhaps the most well-isolated and bright ones, that could be useful for understanding the evolution of what spots can and cannot do over stellar ages. I still have concerns about dilution and turning the 30-minute data and FFI data into the same scale. Maybe a few eclipsing binaries could be used to calibrate to make sure the depths are right.
I'm always happy to see repeatability! That light curve you made looks really nice, and it's neat to see that you find similar behavior in the K2 data as we saw in Kepler, which gives me confidence the explanations we have for everything we see are about right (never bet against Doug Caldwell!) These stars that vary by 10% are incredible, aren't they? Some must be young and active. Certainly many contact binaries also show similar behavior, which I've seen in the FFIs and the Catalina Sky Survey people folks have written several papers about in their data. I would love to do a better job quantifying how much variability we see is intrinsic to the star and how much is changes in the line-of-sight extinction due to ours and those stars' proper motions against an anisotropic galactic dust distribution, a la eg Smith et al. 2012 (arXiv:1210.8136) who note a 15 AU change in position over six years is enough to produce quite a change in dust extinction, and that's reasonable for at least some of the Kepler targets.
Did you happen to do the same for 8462852 by chance? :)
I think your explanation of a likelihood function makes sense, but I need to sit down and work through the math. I'm happy to team up to think about this more!
I think we do a lot better in the FFIs for the 4.3 million targets than ground-based surveys just because they are so faint, point-to-point scatter is so high. These targets are almost all fainter than Kp=16 (Kp=14 if they're giants) and the ground-based surveys just don't have 1% photometry at that level, while we have a 2-5 mmag for many of them. I'm inspired by a really nice paper by Laszlo Molnar last year that used the FFIs to show just from those data you can measure RR Lyrae periods correctly to the 5th decimal place and did some validation of the Gaia DR2 catalog (arXiv:1805.11395). If those big amplitudes do well with these surveys relative to the ground, then surely the few percent EBs or the hot Jupiters are more detectable! I have less of a compelling science case that hinges on finding these, but I really like this search as a student project that will teach all the skills someone needs to do more photometric work.

Agreed to the themes here, and the point is taken about dilution--subtle aperture affects will matter, and EBs and other benchmarks would be great calibrators to spot-check.
That's Tabby's star isn't it?  I didn't try-- I expect the constraints from my coarse calibration to be... well coarser than yours, so it's a no contest at the moment.
The differential extinction from proper motion is both worrisome (how to disambiguate long term stellar signals faithfully) and neato (AU-scale tomography of cluster environments?).  I suppose Gaia proper motions for nearby objects should be good enough to inform to what extent long term trends arise from intrinsic and extrinsic flux changes.

Yeah, apertures will be the biggest thing to get right! But we have EBs. And we can do pixel-level analyses in theory to try to understand how important dilution is, both in the 30-minute data and in the FFIs.
Yeah, Tabby's star! It was the first thing we did with the FFIs so I always like to see others reproduce it, make sure we're not standing on a table of misunderstood systematics (or at least that we're all standing on the same table). I asked Krista and her student to run that one in our comparisons too (they got similar results, which was comforting!)
Yeah, you've hit on my thoughts too---if we have variability that is correlated with the amplitude of a star's proper motion and/or galactic position then we should be working out ways to account for it. It would be a super neat result! I think there are somewhat more long-term trends in the FFIs than I would naively expect, which could be extinction. Although I talked to Greg Feiden (and I think you?) at one point, and he thought close binarity might be sufficent to explain it. Now that we have DR2 and lots of photometry from all the FFIs I should go back and see if the stars with long-term trends are also brighter in the way you'd expect if they were binaries!

Demo of Tabby's star with custom and crude FFI zero point calibration:

You can see the conspicuous channel-level offsets imperfectly corrected in at least one channel group.  The overall dip trend at BKJD = 1200 remains, albeit spuriously amplified by the channel-group offset in the custom reduction.

Yeah, sweet! Thanks for running that. I think I see the long-term signal too, at least looking at just the groupings of points on the same channel seems to have a small year-to-year change.
We haven't talked about the Golden FFIs yet, but there's something to do with those as well for calibration purposes, I think. The telescope is so stable over those images, they are telling us something about the astrophysical scatter over day-long timescales. Of course the regular 30-minute data tells us that too. But I think there's something more to learn from those.


WIP [YUNIKORN-2562] Nil pointer panic in Application.ReplaceAllocation()

What is this PR for?
Application.placeholderData is not populated properly during recovery. Panic occurs when placeholder allocations are restored and a new placeholder is added with a new taskgroup.
What type of PR is it?

[x] - Bug Fix
[ ] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2562
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.01%. Comparing base (55e9fe6) to head (6b48aa0).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #846      +/-   ##
==========================================
+ Coverage   76.99%   77.01%   +0.02%
==========================================
  Files          97       97
  Lines       12035    12037       +2
==========================================
+ Hits         9266     9270       +4
+ Misses       2428     2427       -1
+ Partials      341      340       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.