Google Map's camera is not positioned correctly at initialization.

This is a follow-up ticket for https://github.com/flutter/flutter/issues/24806.
The original issue is fixed by a temporary workaround https://github.com/flutter/plugins/pull/1157.
We suspect the bug is in the iOS Google Maps SDK. We will use this ticket to track the status of the Goole Maps SDK fix; and once it is fixed, we can remove the temporary workaround.

@iskakaushik Since you are working on the new map plugin, maybe it can be solved after your work.

The workaround creates some visual jarring - is there a way to avoid it? I am creating a GoogleMap with an initialPosition and the map renders initially with the position in the top left corner, as per the original bug. But it stays that way until the user moves the camera, at which point the workaround code kicks in and the map suddenly jumps to the correct location.
I suspect the underlying issue is that the initial frame passed to GMSMapView mapWithFrame has zero size, which I observed in Xcode while debugging. Probably there is some code in the iOS Maps SDK that recomputes view bounds when the frame is resized, to keep the camera centered on the target, and that code breaks (understandably) when the old size is zero. So this could possibly also be fixed in Flutter's PlatformView by postponing initialization until the final RenderBox size is known.

Any update on this?

Hi @cyanglaz
Are you still experiencing this issue?
Thank you

@TahaTesser There is currently no behavior issue. We implemented a workaround. However, I opened this ticket to track the workaround, in case it is fixed in GoogleMap sdk, we can remove the workaround.
It is probably a low priority issue.

The workaround does not work unfortunately. Problem persists. Using version 0.5.25+3.

just wrap GoogleMap with Padding and set top to MediaQuery.of(context).padding.top
Padding(
          padding: EdgeInsets.only(top: MediaQuery.of(context).padding.top),
          child: GoogleMap(...),
)

The issue of visual jarring should be fixed in 0.5.25+3 @matthewlloyd

Any update on this? This is breaking all our apps running on iOS 17+ ...

Same problem

We are seeing if this is resolved with the latest version of the Maps SDK for iOS (potential underlying issue is fixed) and will update this issue if an upcoming release is able to fix it.

I'm also experiencing this issue on iOS 17. It's not happening every time but it happens.
I found a workaround : change the padding of the map after a short delay in onMapCreate callback. But this is an ugly workaround. I hope you will be able to fix this issue soon.


ulauncher: 5.7.3 -> 5.7.5

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Ulauncher/Ulauncher/releases.
meta.description for ulauncher is: "A fast application launcher for Linux, written in Python, using GTK"
meta.homepage for ulauncher is: "https://ulauncher.io/"
Updates performed

Version 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

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 5.7.5 with grep in /nix/store/bi286dpzkcl7n7fvgsjip15rafwqb8a6-ulauncher-5.7.5

directory tree listing: https://gist.github.com/0034519feb1c3330f53601e4403c51d5

du listing: https://gist.github.com/95ff43fbb9fd1a721155dda4b45ecef5

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

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
ulauncher

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bi286dpzkcl7n7fvgsjip15rafwqb8a6-ulauncher-5.7.5 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's 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 ulauncher https://github.com/r-ryantm/nixpkgs/archive/259d24a884451c3e78136ea024205dd1d28efae2.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/bi286dpzkcl7n7fvgsjip15rafwqb8a6-ulauncher-5.7.5
ls -la /nix/store/bi286dpzkcl7n7fvgsjip15rafwqb8a6-ulauncher-5.7.5/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 1

1 package built:
- ulauncher

Maintainer pings
cc @aaronjanse @worldofpeace for testing.

Broken. I'm working on a fix


New feature: calibrating between two points (home and max position)

I am trying to calibrate between two points, so limit switches on both sides. This means I will first be calibrating on the home position (which you do have a function for), and then move to the other side, until the limit switch hits, and setting that as MAX_STEPS, so it cannot move any further than that point.
That means if you try to do an absolute or relative-move, and that comes above MAX_STEPS, it will just stop at MAX_STEPS.
You can now use the limit switch feature to get around this nonexistent feature, but the following functions could be implemented:
void startHomeAndLimitCalibration(int beginLimitSwitch, int EndLimitSwitch)
(maybe an extra callback function for when this is finished)
int getMaxSteps()
void setMaxSteps(int maxSteps)
void moveToMaxSteps()
bool isHomeAndLimitCalibrated()
There could be something I am forgetting, but I think this gets you a good idea of what I mean

Hi Firstly thank you for the work you are doin got this software. We are using it at an Aviation museum to drive a model of a Link Trainer.
Added to the above..
It would be useful to know when the limit switch (Min || Max) is activated. If I do not know which switch is activated (eg at power on) I could try drive the stepper in the wrong direction which would result in some very bent metal!
Is some work on this problem being contemplated? possible timing?

Hi Frank,
You could call Arduinos digitalRead(...) function to check which limit switch is triggered after booting. Then you need to set the direction of the initial move accordingly to move in the opposite direction.

Hi Paul,
Thanks for the quick response and excellent solution.
Frank

On 7 Apr 2024, at 6:08 PM, Paul @.***> wrote:
Hi Frank,
You could call Arduinos digitalRead(...) function to check which limit switch is triggered after booting. Then you need to set the direction of the initial move accordingly to move in the opposite direction.
—
Reply to this email directly, view it on GitHub https://github.com/pkerspe/ESP-FlexyStepper/issues/6#issuecomment-2041328624, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACTMFCKZC74IJ5WTBEB6TO3Y4DPHJAVCNFSM4VUVOLEKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBUGEZTEOBWGI2A.
You are receiving this because you commented.


.Ids seems to be needed in rules now

In https://github.com/kframework/k/tree/master/k-distribution/tutorial/1_k/2_imp/lesson_4 we say:
The use of the .Ids in the second rule is not necessary. We could have written int; S instead of int .Ids; S and the K tool would parse it and kompile the definition correctly, because it uses the same parser used for parsing programs also to parse the semantics.

It turns out, though, that now we do need to add the .Ids in the second rule for variable declarations.  The parser does not complain if you don't, but the programs fail with int .Ids on top of the k cell when you run them.  We may continue to argue whether we want lists to be automatically associative or not and whether we want the . units to be explicit in the rules, but whatever we decide, we cannot have the parser not complain and let the program kompile, only to fail to match at runtime.

But this is a really really old text. git blame tells me you wrote this in 2012.
I think this is what used to happen in K2, but we found that we don't want to allow terms which match on 'nothing' in rules because we may be able to write unreadable stuff like rule X =>.
In this case, to parse int ; S, we would have to add a term Ids ::= "", but something like this will produce unmanageable ambiguities, and malformed rules.
I think the text should be updated.

Maybe I should change the readme text, indeed, but I will only do it after the parser rejects int ; S.  It currently does not, as I said above.

That's interesting. I tried to parse this: rule int ;   [structural], and works!!!!
Something is very, very, VERY wrong in kompile.
How did this pass through our tests?

Isn't that the same I said?  :)

This has nothing to do with parsing. I'm looking into it with @dwightguth.

Ah, and please don't merge anything until we have this fixed!


dump-autoload error

hi
when run this code:
php composer.phar dump-autoload
This error is displayed:

In Factory.php line 321:
"./composer.json" does not match the expected JSON schema:

name : Does not match the regex pattern ^a-z0-9/a-z
0-9$

dump-autoload [-o|--optimize] [-a|--classmap-authoritative] [--apcu] [--apcu-prefix APCU-PREFIX] [--dev] [--no-dev] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--strict-psr]

open composer.json file and change the name="TAD-PHP" to "name": "tag/php",
Now it will be work


Comments for device type and iOS version

So I screwed up somehow on https://github.com/kpwn/yalu102/pull/275 so i made a new PR with fewer commits.

Wait. Line 56 and 72 refers to A10. Does this have support for i7 at this stage?

Not that I know of but it should one day so the offsets might as well be there...

Oh ok.


Make the default entry_point a valid URL

Otherwise the server crashes when trying to construct a URL object out of it

Ah, yeah, sucks that new URL works like this. Thanks for the patch :)


eature `interpolated strings' cannot be used because it is not part of the C# 4.0 language specification

Imported the unity package into Unity 2018.1.2.f1 and got the error Assets/ProceduralLevelGenerator/Scripts/GeneratorPipeline/DungeonGenerators/GraphBasedGenerator/GraphBasedGeneratorTask.cs(71,16): error CS1644: Feature interpolated strings' cannot be used because it is not part of the C# 4.0 language specification`
The error also appears in other files.

Hey!
Please make sure that you have Scripting runtime version in Unity set to .NET 4.X equivalent or .NET Standard 2.0.


NLU FallbackClassifier should have some measure of a confidence of fallback

Right now, FallbackClassifier substitute intent with nlu_fallback with confidence 1, however its confidence value should mimic the fact how confident we are that it is indeed fallback.

It could be inversely proportional to the confidence for the original predicted intent?

by inversely do you mean 1-...?

I was thinking the same

Yep.

I'll keep this in mind for https://github.com/RasaHQ/rasa-nlu-examples/pull/50 too.

@koaning but in your case you actually have confidence in your fasttextclassifier, no?

@koaning but in your case you actually have confidence in your fasttextclassifier, no?

FastText does supply some numbers but they aren't properly added yet to the message. This is a reminder for me to make sure that before I merge that it is consistent with the implementation here.

but I think it is independent, e.g. in nlu fallback classifier we have confidence, it is just 1

Isn't this issue about changing that?

I think there is some misunderstanding here. What I mean is that I don't see how changing this 1 will affect your custom component


PA3005: "Group control x state refers to non-existent child"

Top errors are showing multiple results that seem like it is detecting a runtime error. This should not prevent pack\unpack from completing successfully. Should also evaluate other PA3005 to determine if there are other scenarios like this one which we can avoid.
Solution:
Remove exception throw for relevant errors.

These changes look good, are we planning to handle other runtime validation errors too in this PR?
Like I see there are other areas in the repo throwing exception for the same error as src\PAModel\SourceTransforms\ComponentDefinitionTransform.cs: BeforeWrite()

These changes look good, are we planning to handle other runtime validation errors too in this PR?
Like I see there are other areas in the repo throwing exception for the same error as src\PAModel\SourceTransforms\ComponentDefinitionTransform.cs: BeforeWrite()

These changes look good, are we planning to handle other runtime validation errors too in this PR?
Like I see there are other areas in the repo throwing exception for the same error as src\PAModel\SourceTransforms\ComponentDefinitionTransform.cs: BeforeWrite()

Actually, on second thought those exceptions might be necessary (template finding/updating in component errors). Approving the changes in this PR so far.


feat(expr): to_jsonb

https://www.postgresql.org/docs/16/functions-json.html#FUNCTIONS-JSON-CREATION-TABLE

Converts any SQL value to jsonb.

Arrays and composites are converted recursively to arrays and objects (multidimensional arrays become arrays of arrays in JSON).
Otherwise, if there is a cast from the SQL data type to jsonb, the cast function will be used to perform the conversion;
otherwise, a scalar JSON value is produced.

For any scalar other than a number, a Boolean, or a null value,
the text representation will be used, with escaping as necessary to make it a valid JSON string value.

to_json('Fred said "Hi."'::text) → "Fred said \"Hi.\""
to_jsonb(row(42, 'Fred said "Hi."'::text)) → {"f1": 42, "f2": "Fred said \"Hi.\""}

Note:

This should be the basis of existing jsonb_agg and jsonb_object_agg, which currently relies on Into<serde_json::Value>.
None of our data type is allowed to cast to jsonb. The crossed PostgreSQL rule is for hstore type.
Strictly speaking, to_jsonb(1::bigint << 55) is better encoded as json string rather than json number (rfc or proto3). But we can keep it PostgreSQL-compatible.
Strictly speaking, nan and inf are not allowed. But PostgreSQL encodes them as string, and refuses to decode them back:

test=# with t(v) as (values (1.5::real), ('nan')) select (jsonb_agg(v) -> generate_series(0, 0))::real from t;
 float4
--------
    1.5
(1 row)

test=# with t(v) as (values (1.5::real), ('nan')) select (jsonb_agg(v) -> generate_series(0, 1))::real from t;
ERROR:  cannot cast jsonb string to type real

Strings are escaped, but jsonb is not double encoded:

test=# select to_jsonb('{"a":1}'::varchar);
  to_jsonb
-------------
 "{\"a\":1}"
(1 row)

test=# select to_jsonb('{"a":1}'::jsonb);
 to_jsonb
----------
 {"a": 1}
(1 row)

test=# select to_jsonb(array['{"a":1}']);
   to_jsonb
---------------
 ["{\"a\":1}"]
(1 row)

test=# select to_jsonb(array['{"a":1}'::jsonb]);
  to_jsonb
------------
 [{"a": 1}]
(1 row)

reference

Finished in https://github.com/risingwavelabs/risingwave/pull/13161.
Here' the summary of converting rules:

bool

converts to jsonb bool trivially

int16 / int32

converts to jsonb number trivially

float32 / float64

converts to jsonb number except for nan / inf / -inf

int64 / decimal

may not fit into IEEE 754 double, but PostgreSQL uses number (backed by decimal); we can report out-of-range error

int256

converts to jsonb string trivially. Since int256 is usually used for blockchain addresses, which use all the 256-bits. We convert it to string directly.

varchar

converts to jsonb string trivially

interval / date / time / bytea

converts to jsonb string using ToText

timestamp

converts to jsonb string using a new format, with T as separator (to be aligned with PostgreSQL)

timestamptz

converts to jsonb string using a new format, with T as separator. Currently session timezone is ignored.

jsonb

to_owned

list

convert recursively

struct

convert recursively

serial

currently jsonb string using ToText, but we provide no semantic guarantee on it and may change it freely in the future.

Check the PR for more details.

After https://github.com/risingwavelabs/risingwave/pull/13198, int64 is now directly stored and printed as i64 to avoid the overhead of conversion to IEEE 754 double.


Support more formats for duration comparison

Missing:

documentation
tests

I believe that for now, this is an unnecessary feature - the current implementation of the [CERTIFICATE_EXPIRATION] placeholder you've worked on is perfectly usable, and while it'd be a nice feature to add, I'd rather keep it simple and have the string be supported by time.ParseDuration(s) out of the box.
I do appreciate the idea, though :)


Fix link to past alerts

👋🏻

Thanks for spotting this @timwis.

We will merge this PR from https://github.com/alphagov/notifications-govuk-alerts/pull/109 so that our test suite runs properly ☺ . Thanks a lot for your contribution @timwis !


TypeError downloading from Ensembl

I am getting an error when I try to download genomes from Ensembl (version 0.5.2 from bioconda)
Human:
$ genomepy install -g data/genomes --annotation GRCh38.p12 Ensembl
/home/s1437643/conda/lib/python3.6/site-packages/norns-0.1.2-py2.7.egg/norns/cfg.py:72: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
Traceback (most recent call last):
  File "/home/s1437643/conda/bin/genomepy", line 11, in <module>
    load_entry_point('genomepy==0.5.2', 'console_scripts', 'genomepy')()
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/s1437643/conda/lib/python3.6/site-packages/genomepy/cli.py", line 38, in install
    regex=regex, invert_match=not(match), annotation=annotation)
  File "/home/s1437643/conda/lib/python3.6/site-packages/genomepy/functions.py", line 197, in install_genome
    invert_match=invert_match)
  File "/home/s1437643/conda/lib/python3.6/site-packages/genomepy/provider.py", line 132, in download_genome
    dbname, link = self.get_genome_download_link(name, mask=mask, version=version)
TypeError: 'NoneType' object is not iterable

Mouse:
$ genomepy install -g data/genomes --annotation GRCm38.p6 Ensembl
/home/s1437643/conda/lib/python3.6/site-packages/norns-0.1.2-py2.7.egg/norns/cfg.py:72: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
Traceback (most recent call last):
  File "/home/s1437643/conda/bin/genomepy", line 11, in <module>
    load_entry_point('genomepy==0.5.2', 'console_scripts', 'genomepy')()
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/s1437643/conda/lib/python3.6/site-packages/genomepy/cli.py", line 38, in install
    regex=regex, invert_match=not(match), annotation=annotation)
  File "/home/s1437643/conda/lib/python3.6/site-packages/genomepy/functions.py", line 197, in install_genome
    invert_match=invert_match)
  File "/home/s1437643/conda/lib/python3.6/site-packages/genomepy/provider.py", line 132, in download_genome
    dbname, link = self.get_genome_download_link(name, mask=mask, version=version)
TypeError: 'NoneType' object is not iterable

Zebrafish:
$ genomepy install -g data/genomes --annotation GRCz11 Ensembl
/home/s1437643/conda/lib/python3.6/site-packages/norns-0.1.2-py2.7.egg/norns/cfg.py:72: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
Traceback (most recent call last):
  File "/home/s1437643/conda/bin/genomepy", line 11, in <module>
    load_entry_point('genomepy==0.5.2', 'console_scripts', 'genomepy')()
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/s1437643/conda/lib/python3.6/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/s1437643/conda/lib/python3.6/site-packages/genomepy/cli.py", line 38, in install
    regex=regex, invert_match=not(match), annotation=annotation)
  File "/home/s1437643/conda/lib/python3.6/site-packages/genomepy/functions.py", line 197, in install_genome
    invert_match=invert_match)
  File "/home/s1437643/conda/lib/python3.6/site-packages/genomepy/provider.py", line 132, in download_genome
    dbname, link = self.get_genome_download_link(name, mask=mask, version=version)
TypeError: 'NoneType' object is not iterable

Ensembl might have changed something on their end?

Thanks for reporting! I get the same error, I'll investigate.

It is fixed in the current release. It's available on pypi, however, it will take a little time before the conda package is available.

Great thank you very much, any estimated time I should check back on bioconda?

As soon as I get the build to work on bioconda! Hopefully somewhere this week. I'll inform using this issue (and close it) once it's ready.

It's now on bioconda as well.


VisIt not compatible with latest CMake (2.8.12)

From Philip Blakely's email: I believe that I've found an incompatibility between VisIt and CMake2.8.12 (latest release). If I try to manually make the Silo plugin (orany other plugin), I get the following: (VisIt 2.7.0 was installed into /usr/local/visit from thevisit2_7_0.linuxx86_64ubuntu11.tar.gz download.) pmblakely@localhost:/data/visit2.7.0/src/databases/Silo$/opt/cmake-2.8.12/bin/cmake . CMake Error at /usr/local/visit/2.7.0/linux-x86_64/include/PluginVsInstall.cmake:416(LIST): list GET given empty listCall Stack (most recent call first): CMakeLists.txt:75 (ADD_TARGET_DEFINITIONS) CMake Error at /usr/local/visit/2.7.0/linux-x86_64/include/PluginVsInstall.cmake:416(LIST): list GET given empty listCall Stack (most recent call first): CMakeLists.txt:81 (ADD_TARGET_DEFINITIONS) Configuring incomplete, errors occurred! However, using CMake <IP_ADDRESS> (or any earlier version) I get no problems. (I've attached a full terminal log for complete context.) The issue seems to be that at line 412 of PlusinVsInstall.cmake: GET_TARGET_PROPERTY(currentDefs ${target} COMPILE_DEFINITIONS) is expected to set currentDefs = NOTFOUND but as of CMake 2.8.12 itsets it to an empty string. I'm not sure whether this is a wrong assumption in VisIt or aregression in CMake. The error seems to occur for VisIt 2.6.3 as well,but I haven't checked earlier versions.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 1644
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: VisIt not compatible with latest CMake (2.8.12)
Assigned to: -
Category: -
Target version: -
Author: Kathleen Biagas
Start: 11/05/2013
Due date:
% Done: 0%
Estimated time:
Created: 11/05/2013 11:14 am
Updated: 11/06/2013 12:06 pm
Likelihood: 3 - Occasional
Severity: 2 - Minor Irritation
Found in version: 2.6.3
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
From Philip Blakely's email: I believe that I've found an incompatibility between VisIt and CMake2.8.12 (latest release). If I try to manually make the Silo plugin (orany other plugin), I get the following: (VisIt 2.7.0 was installed into /usr/local/visit from thevisit2_7_0.linuxx86_64ubuntu11.tar.gz download.) pmblakely@localhost:/data/visit2.7.0/src/databases/Silo$/opt/cmake-2.8.12/bin/cmake . CMake Error at /usr/local/visit/2.7.0/linux-x86_64/include/PluginVsInstall.cmake:416(LIST): list GET given empty listCall Stack (most recent call first): CMakeLists.txt:75 (ADD_TARGET_DEFINITIONS) CMake Error at /usr/local/visit/2.7.0/linux-x86_64/include/PluginVsInstall.cmake:416(LIST): list GET given empty listCall Stack (most recent call first): CMakeLists.txt:81 (ADD_TARGET_DEFINITIONS) Configuring incomplete, errors occurred! However, using CMake <IP_ADDRESS> (or any earlier version) I get no problems. (I've attached a full terminal log for complete context.) The issue seems to be that at line 412 of PlusinVsInstall.cmake: GET_TARGET_PROPERTY(currentDefs ${target} COMPILE_DEFINITIONS) is expected to set currentDefs = NOTFOUND but as of CMake 2.8.12 itsets it to an empty string. I'm not sure whether this is a wrong assumption in VisIt or aregression in CMake. The error seems to occur for VisIt 2.6.3 as well,but I haven't checked earlier versions.
Comments:
I updated severity here to 4 'cause it means we cannot build external plugins with CMake 2.8.12

Closing because we now we require CMake 3.8 at a minimum.


Cannot exclude file imported in entrypoint from bundle

Describe the bug
For my use case I copy my .env into a JS file after I build my app. This way I can achieve a build-once-run-anywhere flow.
With CRA I achieved this simply by including a line like <script src="%PUBLIC_URL%/runtime-config.js"></script> in my index.html, and swapping the contents of public/runtime-config.js at run time.
Vite does not currently allow this, even with options like explicit-url-imports, optimizedeps-exclude, optimizedeps-entries, and assetsinclude as all of these options (appear) to only work with code referenced from anywhere except the entrypoint.
I would expect some/all of those options to extend to code imported in entrypoint itself.
For example, an index.html with
<script type="module" src="/src/index.js"></script>
<script type="module" src="/src/donotbundle.js?url"></script>

should result in something like
<script type="module" crossorigin src="/assets/index-b2d2ecc0.js"></script>
<script type="module" src="/src/donotbundle.js?url"></script>

rather than just
<script type="module" crossorigin src="/assets/index-b2d2ecc0.js"></script>

Reproduction
https://stackblitz.com/edit/vitejs-vite-krdfwv?file=index.html
Steps to reproduce
No response
System Info
System:
    OS: macOS 13.2.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 240.21 MB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 14.18.2 - ~/.nvm/versions/node/v14.18.2/bin/node
    Yarn: 1.22.17 - ~/.yarn/bin/yarn
    npm: 6.14.15 - ~/.nvm/versions/node/v14.18.2/bin/npm
  Browsers:
    Chrome: 110.0.5481.177
    Safari: 16.3
  npmPackages:
    @vitejs/plugin-react: ^3.1.0 => 3.1.0
    @vitejs/plugin-react-refresh: ^1.3.6 => 1.3.6
    vite: ^4.1.4 => 4.1.4

### Used Package Manager

npm

### Logs

_No response_

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitejs/vite/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitejs.dev/guide).
- [X] Check that there isn't [already an issue](https://github.com/vitejs/vite/issues) that reports the same bug to avoid creating a duplicate.
- [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to [vuejs/core](https://github.com/vuejs/core) instead.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vitejs.dev/).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

If you are importing assets from public, do not start with public path, you can find the warn in above demo when running npm run dev
files in the public directory are served at the root path.
Instead of /public/donotbundle.js?url, use /donotbundle.js?url.

After changing it to /donotbundle.js?url, the script is reserved as-is in the build artifacts which meets your requirement even without ?url


[url_launcher] canLaunch returns false when launch works fine

Steps to Reproduce

Provide email  or phone scheme
Run canLaunch(uri)
Get false
Run launch(uri)
Get all working fine

  final mail = Uri(
    scheme: 'mailto',
    path<EMAIL_ADDRESS>  );
  print('mail test: ${await canLaunch(mail.toString())}');
  final tel = Uri(
    scheme: 'tel',
    path: '88005553535',
  );
  print('tel test: ${await canLaunch(tel.toString())}');

Prints
mail test: false
tel test: false

But running launch(mail) or launch(tel) runs gmail or phone apps respectively

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.4, on Linux, locale ru_RU.UTF-8)
    • Flutter version 2.0.4 at /opt/flutter
    • Framework revision b1395592de (7 days ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /data/nikto_b/Android/SDK/
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /data/nikto_b/Android/SDK/
    • Java binary at: /opt/android-studio/jre/bin/java
    • Java version openjdk version "1.8.0_242-release"
    • All Android licenses accepted.

[✓] Android Studio
    • Android Studio at /opt/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version openjdk version "1.8.0_242-release"

[✓] IntelliJ IDEA Community Edition (version 2020.3)
    • IntelliJ at /usr/share/idea
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (1 available)
    • Pixel 4 XL (mobile) • ############## • android-arm64 • Android 11 (API 30)

• No issues found!

Hi @niktob560
Did you try adding the queries element?
Which SDK you're targeting?

Hi @TahaTesser
targetSdkVersion is 30
Fixed by adding queries element
Duplicate of #63727, closing, thx


Stuff to do

There are some CORS issues when fetching locally (just tested now).
Also, how are we rendering the tsv data?

You're taking care of that :P


Capitalization Collation Tests

Why make this change?
Solves issue #2350, to add collation tests related to capitalization.
What is this change?
Added capitalization collation tests for MSSQL, MYSQL, & POSTGRESQL by creating a new GraphQLCollationTests file under SQLTests that will have all the tests related to collations for SQL databases.
How was this tested?


Slow descrambling with certain cd-rom

Version
Latest, 20220909
Describe the bug
Cd-rom gets dumped succesfully and normally but then the descrambling process always takes a lot of time, about a hour or two. It does descramble succesfully, it's just very slow. It does have some filedate issues in the bin/cue, not sure if related. Restarted pc, tried it several times but the descrambling stays slow with only this cd-rom. My computer is a highend pc, with other cd-roms it goes much faster.
The 71041TWAV01_mainError.txt file is very big, more than 1gb.
I'm not sure if this is a bug or not, but maybe the process can become quicker.
Screenshots
https://user-images.githubusercontent.com/96270929/206045509-0aefa962-69ce-4121-8975-1a1c625ad9c3.mp4
Disc title
NTI Skill Builder Microsoft PowerPoint 97
Disc ringcode
Dawidisc/ 22000 / NTI/ MS PP 97 / 06-01
URL
https://archive.org/details/nti-pp97 (.scm file is there too)
Log file
Too big, see url above

Unfortunately, this is not bug.
Scrambled image of this disc is not normal (some bytes are scrambled but some bytes are not scrambled). For this reason, _mainError.txt is very big size.

Thanks.
Would it be possible to speed up the process?
I have no technical knowledge but someone told me it's just some XOR-ing and using a highend pc with quick ssd/cpu I somewhat expected a quicker process. Any chance there is a little bottleneck in the code that can be fixed?

This can definitely be fixed - the problem is that there is absolutely no output buffering in OutputLog, and OutputMainChannel generates the hex dump view mostly one char at a time, meaning one WriteFile call per byte. 99.99% of the time is wasted in WriteFile calls.

Just did a quick test:
Before:
StartTime: 2023-12-27T17:09:54+0100
EndTime: 2023-12-27T18:29:37+0100

Commented out the OutputLogs in OutputMainChannel:
StartTime: 2023-12-27T18:40:32+0100
(.scm capture from drive was done at 18:52:16)
EndTime: 2023-12-27T18:52:39+0100


Function called outside component initialization (spaces in directory name)

This bug presents on *nix systems if there is a space in one of the directory names of your project tree.

I think there's a pending PR on Vite for that https://github.com/vitejs/vite/pull/2614

Closing as duplicate of https://github.com/vitejs/vite/issues/2585, thanks!
Until the PR to fix that is merged, try

Workaround: try again in a path with no spaces in any folder names


Update next.js

When do you plan to update next.js to 2.3.4 ?

When do you plan to update ?

I updated all the dependencies and everything works for me. Be sure to add the last 3 dependencies for proper operation.

You can try the next branch.

2.0 has been released!


refactor: correct hard coding in several shell script

Signed-off-by: zhuangqh<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Correct hard coding in several shell script, using configurable variable instead.
Fix a minor bug in #1447
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

It happens to be error exists in critools testing, @Starnop . Actually it says that there is one failure in the critools testing. However, I think it is quite hard for me to judge which one is failing. Is there any way for the critools to show explicit error case.
In addition, I retrigger the critools testing to check if this is a flaky test. I have to say in the future we need to pay more attention on the flaky test in CRI part. It is quite important to be related with the stability of Pouchd.

Codecov Report

Merging #1452 into master will decrease coverage by 1.5%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1452      +/-   ##
==========================================
- Coverage   40.05%   38.54%   -1.51%
==========================================
  Files         249      250       +1
  Lines       16179    17057     +878
==========================================
+ Hits         6480     6575      +95
- Misses       8880     9635     +755
- Partials      819      847      +28

Impacted Files
Coverage Δ

apis/server/container_bridge.go
53.8% <0%> (-29.01%)
:arrow_down:

daemon/mgr/container_utils.go
51.07% <0%> (-28.32%)
:arrow_down:

apis/server/volume_bridge.go
63.1% <0%> (-23.38%)
:arrow_down:

apis/server/network_bridge.go
44.87% <0%> (-18.44%)
:arrow_down:

daemon/mgr/container.go
36.27% <0%> (-13.73%)
:arrow_down:

apis/server/utils.go
49.09% <0%> (-12.03%)
:arrow_down:

ctrd/image.go
76.57% <0%> (-2.86%)
:arrow_down:

daemon/containerio/container_io.go
57.79% <0%> (-1.95%)
:arrow_down:

pkg/system/cgroup.go
87.09% <0%> (ø)

daemon/mgr/network.go
69.28% <0%> (+0.49%)
:arrow_up:

LGTM


Allow max Keep-Alive requests to be configurable

Description
Enables the maximum number of subsequent Keep-Alive requests to be specified when creating an HTTP server.  A value of zero disables Keep-Alive.  A negative value allows unlimited requests, and is the default.
Resolves #1125
Note that IBM-Swift/Kitura-net#216 is a prerequisite to this one and describes the motivation and context.
How Has This Been Tested?

See IBM-Swift/Kitura-net#216
Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

Hi!
I am neither much of a user of nor contributor to Kitura, but I was looking at the project and stumbled upon this pull request and had some feedback that I thought may be of value. But since I haven't spent much time with the project, I readily acknowledge that I may be totally naïve to best practices, standards, or precedent for this project that may totally invalidate what I would like to say. I am offering this feedback from only the perspective of a general Swift developer.
This pull request (and the one it depends upon) introduces the concept of a configurable number of requests to be permitted per Keep-Alive connection. There are three ways it can be configured: with Keep-Alive disabled, Keep-Alive enabled and allowing a finite number of requests, or Keep-Alive enabled and allowing an unbounded number of requests. The configuration is made with an Int. A sentinel value (negative numbers) is used to indicate unlimited requests. A value of 0 is sort of a sentinel value in how it's used to disable Keep-Alive entirely, though it's also kind of intuitively reasonable when one thinks of what 0 implies.
Swift in general seems to try to move away from sentinel values—as can be seen in APIs like index(of:), which returns nil instead of a sentinel value if an element is not found. I feel that -1 indicating "unlimited" is a bit atypical for Swift API design, and so I offer two alternatives, and would like your feedback if you think either of them is reasonable.
If either of these alternatives are adopted, they would also need to be expressed in the parent pull request.
Alternative 1: An Optional
In this design maxRequests is of type Int?, where nil indicates "no limit", and a non-nil value indicates "this is the maximum permitted", with 0 indicating that Keep-Alive should be disabled.
Alternative 2: An Enum
In this design maxRequests is not an Int at all, and is rather an enum with two or three cases, e.g.:
enum KeepAliveMode {
  case disabled
  case enabled(maximumNumberOfRequests: Int?)
}

or
enum KeepAliveMode {
  case disabled
  case unlimited
  case limited(maximumNumberOfRequests: Int)
}

@youming-lin This should be ready to go once IBM-Swift/Kitura-net#216 has been tagged.

Codecov Report

Merging #1148 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1148      +/-   ##
==========================================
+ Coverage   90.05%   90.06%   +<.01%
==========================================
  Files          36       36
  Lines        1780     1781       +1
==========================================
+ Hits         1603     1604       +1
  Misses        177      177

Flag
Coverage Δ

#Kitura
90.06% <100%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

Sources/Kitura/Kitura.swift
100% <100%> (ø)
:arrow_up:

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 084bf19...3f63c2b. Read the comment docs.


github download

just to let ya know it comes conveniently with its own virus with no extra charge, so download at your own risk........

https://www.virustotal.com/en/file/43aabdc035abdc9f367659c17a8f4f532c9dc467e28213f2097507573e6f5d48/analysis/1461654917/


Loopfunc fixes

[[FIX]] use of params is not capturing loopfunc
Previously the scope manager only considered the function body for usages
that went outside scope, indicating "capturing" that should trigger
loopfunc. This corrects that.
Also affected are function names, but in the case of declarations there is
a different warning and in the case of expressions the name available to
the function will be correct even within a loop.
Note - see this code
var a = function b(arg) { if (!arg) { b(true); } else console.log("first"); }, c = function b(arg) { if (!arg) { b(true); } else console.log("second"); }; a(); c();

[[FIX]] Report loopfunc for all function types
Previously only function expressions caused loopfunc, meaning arrow
functions that captured variables were not warned.
Fixes #2153
Note: if you consider this breaking code because it will start warning about loopfunc's (I think it is enough within the spirit of the option and obscure enough that its okay in a minor release) then I'll split into 2 PR's as the first commit should really go in asap.

Minor nit: You should add a space after for.

It was in the test fixture file so it mattered very little, but I fixed it for consistency.

@jugglinmike the first commit here fixes a regression and should go in before any release.

rebased on master and added a commit (the fixup! one)

This patch no longer applies cleanly, but the resolution is trivial. I think the "proper" way to handle this mid-review is to use a merge commit that can be squashed prior to landing. I've never done that before, though, so if it's wrong or too much of a hassle, feel free to simply rebase (but please keep non-conflict-related changes in separate commits).

I think the "proper" way to handle this mid-review is to use a merge commit that can be squashed prior to landing. I've never done that before, though, so if it's wrong or too much of a hassle, feel free to simply rebase (but please keep non-conflict-related changes in separate commits).

I think that would work as long as you squash before rebasing. In the past I've had a branch with merges and wanted to keep the commits and rebased, but then you find you have to re-do the conflicts with each commit.

I think that would work as long as you squash before rebasing. In the past I've had a branch with merges and wanted to keep the commits and rebased, but then you find you have to re-do the conflicts with each commit.

I just noticed it is two Fix commits for seperate issues - I think you'll have trouble rebasing them now without squashing them together. The merge conflict is quite trivial - the incoming conflict is just a rename of _currentFunct to _currentFunctBody

Squashed, rebased, and merged to master at the following commits:

827e335b29f402ccc8dc2260a82d5df4c071329b
4d4cfcdfbd97adbe93e044e67bfa3bc81bd128af

For posterity, the rebased commits produce an equivalent trees:
$ git diff 4d4cfc 91356b9
$

Thanks, Luke!


add noexcept to QueryHandle move constructors

Pull Request Test Coverage Report for Build 7736d036e77a749b57a0499ade87c1402a84c96c-PR-5

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 81.421%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/QueryHandle.cpp
2
3
66.67%

Totals

Change from base Build 9d3c20d5f768da74d1ea9c1be914f0b9c3b35404:
0.0%

Covered Lines:
298

Relevant Lines:
366

💛  - Coveralls


#9 Use a C* build from the source as the target cluster image

┆Issue is synchronized with this Asana task by Unito

I have some serious concerns about bringing all this code into the code base rather than referencing external sources

I tried to address that concern in the comments above, but simply put the idea is that IMO Adelphi should own the image building process and we can't use the referenced resources directly because they do other things that we don't want to do. We have modified versions.

I think I have an even larger concern about the increase in work that we're now asking the k8s cluster to do; we're now adding logic to download, build and package C* into Docker containers. This cost is paid every time we run the Helm chart

For serious testing, most people will run this on some cloud environment. In my GKE test, it took 4 minutes to build C* from the source and 3 minutes to build the C* Management API, I think that's mostly negligible for workload generation tests that will run for maybe 30min on each anonymized schema (so it could be a few hours total in CI).
The image has to come from somewhere before running the workflow and it has to be built from the source since we'll want to test trunk or a dev branch. In a follow-up work we can let the user specify a pre-built tarball for local testing (let's investigate that in #32), but I still think there's value in building C* in the k8s cluster for real testing for the following reasons:
1- it guarantees reproducibility (we know what's inside the tarball and we'll have a git hash)
2- makes it easy to test with different JDK versions - Adelphi should be able to test C* compiled with JDK 8 and run with both JDK 8 and 11; and compiled and run with JDK 11.
3- the management of the custom image is transparent, otherwise each cloud vendor has its way to publish an image. Also, the image is destroy when the k8s cluster is destroyed, we don't have to worry about cleaning things up.
4- we make no assumptions about the user environment. We want this to be as simple as possible to execute, if everything is self-contained inside the workflow/k8s, we don't have to worry about the user's operating system, git, java version, ant, etc.
@absurdfarce Let me know if that clarifies things a bit or if you still have any questions or suggestions for improvement.

@absurdfarce I just fixed a conflict with the base branch (it turns out I had also added that same -DskipTests option at the same line you did).
Please, let me know if you have any other feedback, otherwise we should merge this.

Thanks @absurdfarce.
For future reference, these are the follow-up improvement tickets:
https://github.com/datastax/adelphi/issues/32
https://github.com/datastax/adelphi/issues/39


tests: volumes: add missing test

The test volumeMountTestCasesNonRecursive was defined but never executed. Add it in the list of tests to execute.
Also, rename variable names: camelCase.
This is a cleanup before #3154.

/cc @steveeJ @iaguis

LGTM


Add livereload for prod and dev

Fix for #41
@ludohenin would you take a look and merge if you think its fine.

@mgechev looks great


Link workflows.md badge to schedule runs

In workflow MD, currently each record has two identical links (Workflow name, Cron Status). This PR changes the latter one to show only cron results.
It also fixes a few typos in current table
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @andreydevyatkin

This PR has been updated. R: @andreydevyatkin @volatilemolotov

LGTM, thanks

Looks like the induced merge commit message was wrong possibly due to rebase -- nevertheless the content of the commit was correct

Yeah it got me confused also but its clear in the diff what is actually changed


etcdserver: initialize raftNode with constructor

raftNode was being initialized in start(), which was causing
hangs when trying to stop the etcd server since the stop channel
would not be initialized in time for the stop call. Instead,
setup non-configurable bits in a constructor.
Fixes #7668

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8fdf8f7). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master    #7757   +/-   ##
=========================================
  Coverage          ?   75.94%
=========================================
  Files             ?      331
  Lines             ?    26062
  Branches          ?        0
=========================================
  Hits              ?    19794
  Misses            ?     4847
  Partials          ?     1421

Impacted Files
Coverage Δ

etcdserver/server.go
80.02% <100%> (ø)

etcdserver/raft.go
88.39% <100%> (ø)

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 8fdf8f7...714b48a. Read the comment docs.

lgtm


[ENH][RFC] Add deprecation helper

Changing the render class would lead to deprecate lots of parameters (#5822).
Therefore, with @GuillaumeFavelier we came up with this decorator.
I guess it would be good to integrate all the deprecation objects etc..
but this is a first step (and we think it would do the job).
WDYT??
cc: @mne-tools/contributors

Hey @massich @GuillaumeFavelier this is pretty cool, not sure how you kept the code compact, will study and learn!
I think instead of using keyword args old_parameter, new_parameter, the function should accept a dict of them, such as
`{old_param0: new_param0, old_param1: new_param1, old_param2: new_param2}'.
This way one can deprecate multiple parameters in a function if needed and seems cleaner to me.

I mean I wrote a decorator for the same purpose but it is not so compact as this one. And I haven't adapted it as a utility function yet, I will in time.

What do we do here? @GuillaumeFavelier are you still interested in this one? If so I can finish it quickly.
@larsoner 	thoughts?

We have also implemented this functionality in Nilearn & Nistats and it is recurringly useful, currently being used in 5 places..

In the end, we came up with a different strategy and the deprecation was not needed anymore in #5822
I still think it could be useful in some cases or even just for maintenance reasons.

@GuillaumeFavelier So Sicch tried so hard and got so far, but in the end it doesn't even matter??

Which PR is that? I would like to see the approach you used to solve the root thing.

I wouldn't say it doesn't matter because as I told you I think the value of our efforts can be leveraged somewhere else hopefully.
The deprecation matter arose as I tried to replace the figure parameter but during the discussion, we decided not to deprecate at all.

decorator is necessary for Python 2. Is that still supported?
On Tue, May 28, 2019, 17:04 Eric Larson<EMAIL_ADDRESS>wrote:

@larsoner commented on this pull request.
Other than needing a rebase and wraps not being sufficient, I'm fine with
putting this in
In mne/utils.py
https://github.com/mne-tools/mne-python/pull/5844#discussion_r288153417:

"""

_MSG_KEYS = {'old_param': old_param,

            'new_param': new_param,

            'deprecated_in': deprecated_in,

            'removed_in': removed_in,

            'old_param': old_param,

            'new_param': new_param,

            'details': details}

_MSG = ('{old_param} is deprecated and will be replaced by {new_param}'

       ' in {deprecated_in}. `{old_param}` will be no longer present'

       ' starting in {removed_in}. {details}').format(**_MSG_KEYS)

XXX: version should be tested

def true_decorator(f):

   @wraps(f)

wraps is not be enough to get the docstring correct here. You need to use
the externals/decorator functionality.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/5844?email_source=notifications&email_token=AB6SXRANZDYZXQPMFACC5BTPXVCYFA5CNFSM4GRANMS2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOBZ35ANA#pullrequestreview-242733108,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6SXRB74OEMN3S77QAV4PTPXVCYFANCNFSM4GRANMSQ
.

IIRC even in Python 3 wraps does not fix all problems with wrapping and docstring parsing

@massich think this is worth coming back to, or should we close?

I took part of it for my PR depreciating montage, but it was hard to review
and we took a diferent approach.
If guillaume still needs it I'll finish it. Otherwise I think I'll close
it.
On Tue, Jul 9, 2019, 17:41 Eric Larson<EMAIL_ADDRESS>wrote:

@massich https://github.com/massich think this is worth coming back to,
or should we close?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/5844?email_source=notifications&email_token=ABVX5Y5KZVS2HN5ADISQAKLP6SWT3A5CNFSM4GRANMS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZQVQDQ#issuecomment-509696014,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVX5YYMHV5B6XEHJTWSEVDP6SWT3ANCNFSM4GRANMSQ
.

I don't need it for now @massich , feel free to close it. we can still reopen later if the situation changes


error TS4023: Exported variable '_sfc_main' has or is using name 'CarouselConfig' from external module ".../node_modules/vue3-carousel/dist/carousel" but cannot be named.

Similar to https://github.com/ismail9k/vue3-carousel/issues/227.

This semmed to me a different issue, could you provide a minimal working example that generates this issue, so that I can deep look into it?

Closing this issue due to inactivity


Compile problem.

Hey, I have a little problem, the program says that the archive was compiled but they doesn't.

Hi,
Please try running the program with Administrator rights (Run as Administrator).


removing single file append changelist

Signed-off-by: David Lawrence<EMAIL_ADDRESS>(github: endophage)

Removing code: Love it.
LGTM


Update README.md

@TrickJoker312 add

mind sharing your discord username? need to contact you about something.

mind sharing your discord username? need to contact you about something.

what is discord brother

mind sharing your discord username? need to contact you about something.

what is discord brother

who gave you that link? link leaking isn’t allowed,  and we need to know who gave you it so we can get in contact so we can get in contact with them

mind sharing your discord username? need to contact you about something.

what is discord brother

who gave you that link? link leaking isn’t allowed, and we need to know who gave you it so we can get in contact so we can get in contact with them

a comment on 3kh0 youtube

mind sharing your discord username? need to contact you about something.

what is discord brother

who gave you that link? link leaking isn’t allowed, and we need to know who gave you it so we can get in contact so we can get in contact with them
can you send a link to that video? i’ll ask 3kh0 to take it down

mind sharing your discord username? need to contact you about something.

what is discord brother

who gave you that link? link leaking isn’t allowed, and we need to know who gave you it so we can get in contact so we can get in contact with them can you send a link to that video? i’ll ask 3kh0 to take it down
it was in persian and i don't remember the name but it gave me so many proxies


Vim9: E1028 when checking if the GUI is running

Describe the bug
In Vim9 script, Vim fails to compile a function which returns when the GUI is not running.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Func()
        if has('gui_running')
            return
        endif
    enddef
    defcompile
EOF
)

E1028 is raised:
E1028: Compiling :def function failed

Expected behavior
E1028 is not raised.  The compilation succeeds.  If for some reason, the compilation cannot succeed, then a more specific error is given.
Environment

Vim version: 8.2 Included patches: 1-1959, 1959-1961
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(361)

Additional context
Regression introduced in 8.2.1528.

In Vim9 script, Vim fails to compile a function which returns when the GUI is not running.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Func()
        if has('gui_running')
            return
        endif
    enddef
    defcompile
EOF
)

E1028 is raised:
E1028: Compiling :def function failed

Expected behavior
E1028 is not raised.  The compilation succeeds.  If for some reason, the compilation cannot succeed, then a more specific error is given.

There is a todo item for this:
- has() is compiled as a constant, but some checks are dynamic.
  Check for dynamic values, such as "gui_running".

--
"You mean there really is an answer?"
"Yes! But you're not going to like it!"
"Oh do please tell us!"
"You're really not going to like it!"
"but we MUST know - tell us"
"Alright, the answer is...."
"yes..."
"... is ..."
"yes... come on!"
"is 42!"
(Douglas Adams - The Hitchhiker's Guide to the Galaxy)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Delete SNS subscriptions in queue cleaner tool

Turns out we left behind SNS subscriptions along with queues, so this removes them too in the cleaner tool.

awesome, thanks!

Not perhaps relevant here but there are also a lot of buildkite-AgentLifecycleTopic subscriptions left behind ...


[Enhancement] TableReader remote multiget support

What type of PR is this：

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

Which issues of this PR fixes ：

Fixes #17266
Problem Summary(Required) ：

This PR adds multi-tablet & remote support for TableReader's mult_get internal API. It uses similar util classes in TabletSink(like OlapTableSchemaParam/OlapTablePartitionParam/OlapTableLocationParam/StarRocksNodesInfo) to route PKs to different partitions/buckets/tablets, batch get requests by tablet, and uses RPC to call multi_get on remote tablets, get all the results and then merge them into a single response.
Note: partition with expression is not supported yet
Checklist:

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

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

Bugfix cherry-pick branch check:

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

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_fe_unittest

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

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

run starrocks_fe_unittest

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

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

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

bugfix: show put rpc implementation in BackendInternalServiceImpl

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_admit_test

run starrocks_admit_test

run starrocks_fe_unittest

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

@mergify backport branch-3.0


Refactoring

Changed explicitly binded functions to arrow functions. (arrow functions automatically bind this)
Changed component structure for easier additions in the future:
index.js exports all components to app.js
Moved components inside ExpenseList.js to their own files

Thank you for the PR and refactoring – I really like the arrow functions used like that, but is it part of the ES6 standard or is it an experimental syntax? The ES Lint is complaining about the syntax. Would you mind sharing some links about it?

Yes, it'd a part of ES6 syntax. I don't know why it would be complaining though :/
Here's the article that I learned from -
https://medium.com/m/global-identity?redirectUrl=https://medium.freecodecamp.com/react-binding-patterns-5-approaches-for-handling-this-92c651b5af56

Alright. After googling I see that it's a proposed feature, but a standard in React development if you're using create-react-app.


Update embedded-login.md

Added line 76 to add restriction on domain name length.
B2C won't allow uploading the custom policy if that criteria aren't met.

@kengaderdus
Thanks for reviewing the proposed changes.
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

#sign-off

@Court72
I can't sign-off PRs?
I see this response:
Invalid command: '#sign-off'. Only Microsoft employees can use this command.


Search domain by name fails

Affected module
Backend / ingestion (Python SDK)
Describe the bug
An error is thrown when trying to search for a domain by name. It appears that the routes.py file is missing the Domain class as a route.
in get_suffix     raise MissingEntityTypeException( metadata.ingestion.ometa.ometa_api.MissingEntityTypeException: Missing <class 'metadata.generated.schema.entity.domains.domain.Domain'> type when generating suffixes
To Reproduce
from metadata.generated.schema.entity.domains.domain import Domain

domain: Domain = metadata.get_by_name(entity=Domain, fqn="test")

Expected behavior
Searching for a domain by name returns the relevant domain without error.
Version:

OS: Windows 10
Python version: 3.10.11
OpenMetadata version: 1.2.0
OpenMetadata Ingestion package version: openmetadata-ingestion==<IP_ADDRESS>

Additional context
My goal is to update the table domain with a patch request.

as part of this ticket, let's prepare the method patch_domain to the given entity, similar to patch_description or patch_tags


Add keyboard shortcuts and remove selected tasks from state

This PR got away from me a little bit, I can split it into two PRs if it is too much code to review.
I :heart: the ideas from https://github.com/cheshire137/gh-notifications-snoozer/pull/109/files, but it has become too hard to merge. So I added those keyboard shortcuts to this PR.
This PR also:

Based on some feedback from @cheshire137, this removes the ability to select multiple tasks. After trying this out I feel like the app is much easier to use!

It gets rid of the hidden task components and moves that logic into TaskList. I did this because they started to feel so similar. The downside to this is TaskList has become too big, but I have plans to fix that in a follow-up PR.

Closes #50

FYI: There are still a few bugs I'm working out here.

@cheshire137 the bugs are worked out and I think this is good to go. I started to implement menu based keyboard shortcuts too, but it started to become a lot of extra code. So I think that could be done in a separate PR.


yourdomain.com

First off, I love this theme. The issue I am having relates to clicking on the about page or articles page and then when I click the home button, it takes me to your domain.com every time. I even set it to my github url and am getting no luck. I've tried for hours and have gotten nothing butt error page not found pages and your domain.
Can you help me figure out why the template doesn't return to the homepage like I want it to?

you can see my page here https://rollonbears234.github.io

Hey! really glad that you liked the theme 👍
There was a error in Gravity's header.html in master branch, this is the branch which is used when the repo is a user website repo.
I have solved the navigation issue in this PR, you just need to merge this with your master branch
https://github.com/rollonbears234/rollonbears234.github.io/pull/1
If there's any other issue, feel free to get in touch 😄
Cheers & Happy Coding!


ImageDataGenerator class_mode='raw' functionality

System information

OS Platform and Distribution ( Linux Ubuntu 16.04):
TensorFlow backend (yes):
TensorFlow version (1.14):
Keras version (2.2.4-tf):
Python version (3.6):

Describe the current behavior
I'm trying to generate raw, one-hot class vectors for a set of images.
import os
from PIL import Image
from tensorflow.keras.preprocessing.image import ImageDataGenerator
os.mkdir('images')

N=10
for i in range(N):
    image = Image.new('RGB', (10, 10))
    image.save(f"images/{i}.jpg")

df = pd.DataFrame.from_dict([{'filePath': f'images/{i}.jpg'.format(i),'y':[1.,0.,0.]} for i in range(N)])

Giving:

Next I make a data generator:
datagen = ImageDataGenerator()

train_generator = datagen.flow_from_dataframe(
        dataframe=df,
        directory=None,
        x_col="filePath",
        y_col="y",
        target_size=(10,10),
        batch_size=3,
        class_mode='raw',
        shuffle=False)

out = next(train_generator)

This is where the issue arises. Notice that the target part of out is not a 2-D array, but a 1-D array of list objects. Running a direct np.array function on the list gives the desired result.

Is there any fix for this, aside from making a custom generator?

can i work on this issue

Hi!! Any update about this issue?

@tinder-arozinov We see that you are using old version of tensorflow which is officially considered as end of life, We recommend that you upgrade to 2.4 or later version and let us know if the issue still persists in newer versions .Please open a new issue in case you face any errors, we will get you the right help .Hence moving this to closed status.Thanks!

@tinder-arozinov We see that you are using old version of tensorflow which is officially considered as end of life, We recommend that you upgrade to 2.4 or later version and let us know if the issue still persists in newer versions .Please open a new issue in case you face any errors, we will get you the right help .Hence moving this to closed status.Thanks!

No, this issue still exists in the new version 2.5.0.
I tried to convert each row in "y" column as "numpy array" but still got the error "Failed to convert a NumPy array to a Tensor (Unsupported object type numpy.ndarray)."

I found the solution, instead of usinf a list of arrays, you can break it into multiple cols.
My solution:

I have the same problem !!


Destiny of Spirits [PCSF00352]

App summary

App name: Destiny of Spirits
App serial: PCSF00352
App version: 1.00

Vita3K summary

Version: v0.1.6

Build number: 3041

Commit hash: https://github.com/Vita3K/Vita3K/commit/c70d526

CPU backend: Dynarmic

GPU backend: Vulkan

Test environment summary

Tested by: elPrimoDorado
OS: Windows 10
CPU: AMD Ryzen 3 2200G
GPU: NVIDIA GTX 1050TI
RAM: 32 GB

Issues

Failed to connect to server

Screenshots

Log
Recommended labels

Menu

Vita3K summary

Version: v0.2.0
Build number: 3691
Commit hash: https://github.com/vita3k/vita3k/commit/31826697
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Slade
OS: Microsoft Windows 10 Professional (build 19045)
CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
GPU: NVIDIA GeForce GTX 1060 6GB
RAM: 16 GB

Issues

This game is an online only game, the servers have been closed / shutdown since 2015, and as such, the game will never run without access to the server code.

Screenshots

Log
vita3k.log
Recommended labels

Menu
online-only


Use Trial to Extract Information from Custom Documents with Generative AI and Document Information Extraction

Tutorials: https://developers.sap.com/tutorials/cp-aibus-dox-ui-gen-ai.html
Hello,
I'm attempting to select the auto "Setup Type" as shown in Step 2 of this tutorial. However, I encounter an error ("Failed to add schema field. Please try again later."):

Interestingly, I can successfully create the data type when I opt for a manual setup. Is there anything specific I should check to resolve this issue when using the auto setup?
Thank you.
Rafael

Hello,
Issue solved itself. Now everything works as expected.
Best regards,
Rafael


Timeout earlier on SQLITE_BUSY when deleting wallets in tests

Issue Number
ADP-827
Overview

[x] Set CARDANO_WALLET_INTEGRATION env var in integration tests
[x] Change timeout to close all connections from 60s to 2s if CARDANO_WALLET_INTEGRATION is set.

Comments

Workaround that should make CI faster (and perhaps a bit more stable), until we have time to investigate and address the underlying issue and its effects in production. The problem in production is likely much less serious, as users likely don't create and delete wallets as often as in our integration tests.
Locally, running stack test cardano-wallet:integration --ta '-j 6' I get:

2s -> 335s
5s -> 380s
60s (without the setEnv) -> 1190s

So that's why I went with 2s rather than 5s.

bors r+


Optimize Mersenne31 Field

Optimize Mersenne31 Field
Description
In this PR we improve the Mersenne31 field operations and add the extensions of degree 2 and 4.
Type of change
Please delete options that are not relevant.

[ ] Optimization

Codecov Report
Attention: Patch coverage is 89.51782% with 50 lines in your changes missing coverage. Please review.

Project coverage is 73.51%. Comparing base (11f6846) to head (c8c92b8).
Report is 3 commits behind head on main.

Files with missing lines
Patch %
Lines

math/src/field/fields/mersenne31/extension.rs
85.71%
50 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #921      +/-   ##
==========================================
+ Coverage   73.31%   73.51%   +0.20%
==========================================
  Files         155      155
  Lines       35283    35898     +615
==========================================
+ Hits        25868    26391     +523
- Misses       9415     9507      +92

Flag
Coverage Δ

73.51% <89.51%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Recharts supporting radix color, add event triggers

depends on #3227 for proper rx.color serialization for fill and stroke props.


Upstream to Rust?

This completion needs to replace the original completion file, and adding this feature to Rust upstream can make this completion file updated in a timely manner.

not a bad idea


Make codebase go fmt compliant

Most editors reformat Go code to the canonical style and Goofys uses its own style which makes it hard to contribute to.  We should also flag the build on style errors via Travis.  References #5.

fixed by 2d959c485ae238bf6e66ba489848e3a1afd41ae7 . PR for travis check welcomed


test: handle spaces in paths better on macOS tests

Ensure that we quote the path to the SDKROOT which may contain spaces.
Failure to so will break the path into multiple components (split on
spaces) and generate an invalid command.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @edymtt @shahmishal

@swift-ci please test


HAR format should be optional

We'd like to use this with an existing service to mock new features in the API under development, but we don't use HAR format.
It would be ideal if the WHOLE body and content type could be specified rather than just the 'content' portion.

so with minimal requirements it would look like this:
{
  "content": {
    "mimeType": "text/plain",
    "text": "Hello"
  }
}

status, and statusText, will default to 200 & OK.
Content-Type header will default to mimeType

Well our API responses typically look like:
{
    success: true,
    payload: ['array of stuff']
}

So we're hoping to have a way to directly return a body like that, with payload in the root and containing JSON. The additional HAR headers aren't the problem so much as that my body ends up nested inside 'content' as text even if I say the content type is application/json
So I was hoping there was maybe a way to either select HAR and get this format or maybe a raw where i can indicate the content type and dump a stringified JSON body
If there's some way we can help with the feature, we're not afraid to roll our sleeves up

oh ... methinks we are talking about two different things and perhaps you are using this wrong ...
after creating a bin, accessing it will give you the response body directly:
curl mockbin.org/bin/create -H "Content-Type: application/json" --data '{"status": 200,"statusText": "OK","httpVersion": "HTTP/1.1","headers": [{"name": "content-type","value": "application/json"}],"cookies": [],"content": {"mimeType": "application/json","text": "{\"success\": true, \"payload\": [\"array of stuff\"]}","size": 0},"redirectURL": "","bodySize": 0,"headersSize": 0}'

curl -v http://mockbin.com/bin/8fbdd762-3c3e-4429-8ab1-2338b594b705

result
> GET /bin/8fbdd762-3c3e-4429-8ab1-2338b594b705 HTTP/1.1
> User-Agent: curl/7.35.0
> Host: mockbin.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Mon, 13 Apr 2015 21:00:30 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 48
< Connection: keep-alive
< Set-Cookie: __cfduid=df778ad7ddd1adf14c39590ccb5ade4041428958830; expires=Tue, 12-Apr-16 21:00:30 GMT; path=/; domain=.mockbin.com; HttpOnly
< Etag: W/"30-e5878040"
< Vary: Accept-Encoding
< Via: 1.1 vegur
* Server cloudflare-nginx is not blacklisted
< Server: cloudflare-nginx
< CF-RAY: 1d6a19d186810d8b-SJC
<
{"success": true, "payload": ["array of stuff"]}

I was definitely using it wrong! Okay I see it working as expected now. I was confused by the /bin/xxx/view page and thought it was my final output.
Thanks!

perhaps better documentation is needed then :)


Fix staggering of social media icons

https://github.com/cagov/design-system/pull/409
@todo

[ ] Figure out why it happens on designSystem but not drought and cannabis
[ ] Visual regression tests

This is done for the design system website but there are things that need to happen to the component before we change the issue status.

Done in https://github.com/cagov/design-system/pull/471 and https://github.com/cagov/design-system/pull/409


Not backward-compatible with actual spotipy

I saw your repo is being discussed in https://github.com/plamere/spotipy/issues/387 as a spotipy alternative.
I started importing it in my project in order to use playlist_cover_image_upload but then I realised that your version has nothing in common with the original spotipy.
If this repo is backward-incompatible with spotipy, I don't think it should be named spotipy as it can be misleading (mainly because the name is already used on PyPI, and the doc is already a top result on google https://spotipy.readthedocs.io/

Just saw that this has been mentioned here already https://github.com/plamere/spotipy/issues/387#issuecomment-520859488
+1 for spotipy3!

Thank you for the feedback, have a look at #22 for the rationale behind this change and voice your opinions about them, please! I'd love to hear your thoughts as well. We have plans of updating the package and documentation gracefully. But I'll close this issue as a duplicate.
To paraphrase, in addition to this really being based on the original spotipy, the old one is also quite broken. So I don't see any value in keeping it. Creating a new version would solve issues for lots of users. And, I think the original repository has no playlist_cover_image_upload... I'm not sure what you mean.

My app uses Spotipy to do a bunch of things, everything works!
I want to add a quick feature to upload thumbnails but spotipy does not have this endpoint
I upgrade spotipy to this/your "new version" that seems to have the thumbnails endpoint
I notice that my app breaks on initialising spotipy, it's unclear why at first, everything was working fine before, what happened? I was hoping that this new version would benefit me, but it is in fact requiring me to modify most parts of my app. I give up because it adds unnecessary risks:

losing development time,
adding bugs to my own code,
expect possible regressions in the new library itself. Should I trust it? it doesn't seem very used nor have a lot of contributors, how do I know it will do the job?

I find that a more efficient alternative for me is to rather fork the original spotipy and implement the thumbnail endpoint on my own.

Basically as a user, I am looking for a solution to a specific problem, not for a solution to a problem I don't have.
I hope this clarifies the importance of backward-compatibility?

That's not really a surprise, is it :D You must have gotten here from some of the initial discussions, read them, seen the readme and documentation, and concluded that it is not just a fork with a couple of typos fixed. After that you surely have considered is modifying your code worth it for you or should you use some other fork like Harrison's, not blindly just dropped my version in. I'm sorry if this all seems aggressive, but I can't imagine you just seeing a link to this repository, cloning it and installing it, and never being informed that it's not exactly a drop-in replacement. If that was the case, did you look for information? If you did, where did you not find it? Maybe the information could be there in the future.
You could trust my version, based on running your own tests, my tests, examining the code coverage and reading example scripts. But yes, a more efficient alternative for you is writing the endpoint on your own, if you are simply interested in having one endpoint more and keeping to the old version. I'm interested in providing an improved solution.


when i run: python camera_demo.py --gpu='0'

Traceback (most recent call last):
File "camera_demo.py", line 16, in
from libs.networks import build_whole_network
File "../libs/networks/build_whole_network.py", line 19, in
from libs.detection_oprations.anchor_target_layer_without_boxweight import anchor_target_layer
File "../libs/detection_oprations/anchor_target_layer_without_boxweight.py", line 15, in
from libs.box_utils.cython_utils.cython_bbox import bbox_overlaps
ImportError: dynamic module does not define module export function (PyInit_cython_bbox)

you need to compile the module. @ZhangHe95


test: add test for boilerplate

more a test for the CI service really...

Codecov Report

Merging #29 into master will increase coverage by 0.35%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #29      +/-   ##
==========================================
+ Coverage   89.78%   90.14%   +0.35%
==========================================
  Files           1        1
  Lines         284      284
==========================================
+ Hits          255      256       +1
+ Misses         29       28       -1

Impacted Files
Coverage Δ

sdp.js
90.14% <0%> (+0.35%)
:arrow_up:

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 5b82282...d239e69. Read the comment docs.


Move phantomJs to devdependencies

Hello,
for now phantomJs is set as a depdency. So that when we install svg-sprite it will download PhantomJS binary (and we dont need it).
I would like to propose to move to devDependency.
Best regards,
Pierre

Duplicate of #254


Office to pdf

How to convert office file to pdf, suppose I have a docx file, I want to convert it to pdf. I have tried many ways but without success, do you have any suggestions?

Hi, there is no such functionality available as part of Apache POI, thus this project also does not offer any support.
There are multiple related questions about this on StackOverflow, see https://stackoverflow.com/search?q=apache+poi+pdf&s=b342371a-c57f-4203-89d9-b23f14cba828 please review those and discuss further there if necessary as this is outside of what this project tries to provide.


Feat/validate refer reward

Updates:
-Inside the actAcceptEntry action, add a new row in the reward table.
As it stands, for every one entry that is accepted, the reward points increases by 1.
-Add code format instructions to Readme.
This PR lean on the approval of PR nº5

The basic.messages test just tests one referral and reward. We need a multi.messages test (create the test file and copy the setup for basic.messages) that tests multiple users making multiple referrals. We will also need to handle the case were a referral is sent to the same person (perhaps use a conflict.messages for that to keep it separate)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 99.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.4%

Covered Lines:
182

Relevant Lines:
184

💛  - Coveralls


Cherry pick to master - Update PAI version

This PR will be merged into master after v1.0.0 is formally released.

Close to use another pr because readme is changed


AutoFocus On Debit Card Page

Details

Fixed Issues

$  https://github.com/Expensify/App/issues/21587
PROPOSAL:   https://github.com/Expensify/App/issues/21587#issuecomment-1607963168
Tests

log in to ND -> go to settings
Navigate to payments
Press on Add payment method -> Select debit card
Verify on navigating to debit card page Name on card should be autofocus

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

Offline tests

Same as above
QA Steps

log in to ND -> go to settings
Navigate to payments
Press on Add payment method -> Select debit card
Verify on navigating to debit card page Name on card should be autofocus

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

PR Author Checklist

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

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

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

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

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

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

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

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

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

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

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/47522946/1ad157a3-8d7e-40d2-9e68-0de5d600e60d

Mobile Web - Chrome
https://github.com/Expensify/App/assets/47522946/6caefc99-3351-445e-95d2-a943655dfb6d

Mobile Web - Safari
https://github.com/Expensify/App/assets/47522946/3830b40c-6377-4c75-b931-c326f6bfa569

Desktop
https://github.com/Expensify/App/assets/47522946/3270fa06-4af4-4b2f-aff0-e503da915c95

iOS
https://github.com/Expensify/App/assets/47522946/d6dc6425-a464-4fc0-96be-061a5a3183b6

Android
https://github.com/Expensify/App/assets/47522946/04563a2f-ee74-4ffa-a986-84c8e550bc0c

Sorry @dhairyasenjaliya , Missed this since the PR didn't auto assign me and hence didn't come up in my K2.
Will review this now. Thanks for the bump

Reviewer Checklist

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

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

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

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

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

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

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

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

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

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

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

https://github.com/Expensify/App/assets/46707890/0b05ea08-4d50-473e-9e5e-a2cd378cea89
https://github.com/Expensify/App/assets/46707890/2367dceb-598d-4a15-a499-9e350a5111ee
https://github.com/Expensify/App/assets/46707890/ae9cbbd3-eba5-45c4-a760-2a7373e7b759
https://github.com/Expensify/App/assets/46707890/9f1bb0ba-408e-4004-a741-e1643ec83104
https://github.com/Expensify/App/assets/46707890/293e4922-b62a-4f2b-8a6f-0f534f0e0ec0

@dhairyasenjaliya Can we fix the merge conflicts?

recheck

recheck

It is not re-running the checks for some reason. There is something weird with this PR.
First it didn't auto-assign properly and not re-running the checklist.
I think the internal engineers would be able to rerun the checklist manually when the review.
@Gonals / @roryabraham

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/roryabraham in version: 1.3.44-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Add construction tests for Vector2, Vector3, Vector4, Quaternion, and Pose

The classes are already moveable. The error reported in the issue comes from the fact that the operation is a copy assignment to unique_ptr, and not a move assignment.
Closes #76
Signed-off-by: Nick Lamprianidis<EMAIL_ADDRESS>

Should these tests be replicated for the rest of the classes?

Should these tests be replicated for the rest of the classes?

That would be great if you're up for it. Hopefully you won't find any classes that aren't movable. And having the tests in place will make sure we don't break this usage in the future.
But when it comes to #76, I think this is enough to address those concerns, so we can close it.


get a formal url

cc @tburdett

Options:

https://www.ebi.ac.uk/fairplus/fair-wizard (or similar)
https://fairplus-project.eu/resources/fair-wizrd (needs PM team to help)
https://fairplus.github.io/the-fair-wizard (reflects https://fairplus.github.io/the-fair-cookbook/)

Not sure which of these are technically feasible or desirable. Is the current instance running inside EBI infrastructure, Embassy, or somewhere else?

@tburdett its running on Embassy

@FuqiX  once we confirm the URL we want we can request it

Once you have decided, let me know if I can help! I can approve the request for an EBI domain URL, or I can liaise with the FAIRplus PM team for the fairplus-project.eu domain URL if needed. I don't think you need me at all for the third one :)