WorldObjects need some form of grouping.

More complex objects might require multiple parts. We need a variation of a WorldObject that can act in unison with all of its subobjects. Implementation-wise it would be the same; processing functions will be activated for the parent first before processing the children, events would be activated on the offending object before the parent is notified about the event (e.g. collisions), etc. Useful for either animations written in code, or large enemies that have multiple segments (like one of neutral run's bosses).

This may not be actually needed. The idea behind this was to make it easier to keep control over certain objects' hitbox and animation positions since they're recorded separately. For an Undertale game, however, this shouldn't be necessary, as in most combat the hitbox of entities within the combat space is usually just reserved when the combat has a gimmick (a-la Mad Dummy's fight). Even when it does, the object is likely to be calm enough in its positional state that a single hitbox would be sufficient to encompass the entirety of the object.
Advantages of the sub-object system would be

Animations and hitboxes are grouped together into one subobject.
Easier control for when animations and hitboxes work in unison to keep in sync (for large complex objects that may require separate boxes, so a bullet doesn't "hit" a target despite being nowhere near the target object visually)

Implementation of subobjects need to store the following data.

Local position relative to the current position of the parent object.
Rotation about the point relative to the current position of the parent object.
Singular hitbox and/or animation data. Generation is handled by functions in the subobject metatable.
Z-priority for rendering the subobject's current animation in a specific order, as opposed to depending on registration order.

Animations and hitboxes will always be offset relative to the active position of the subobject.
As an example, at default positions with no offsets set for either animations or hitboxes, the position of the subobject is dependent on the set offset for the entire object and rotation. At the point resulting from processing the offset and rotation of the subobject is where animations and hitboxes will have their offset and rotation relative to. Say an animation is offset and has a set rotation, the resulting position will be around the final position of the parenting subobject, and not based off the position of the master world object.


Fixed mapCoordsToPixel twitching occasionally when zoom is less than 1.f

mapCoordsToPixel does not round up properly due to floating point inaccuracies due to the explicit floor from the int cast. Adding 0.5f rounds the numbers, fixing the problem.
Here's the bug in action (view is centered on character and the text is placed above it): http://img.cleroth.com/2016-02-04_18-10-50.webm
For some reason it seems to mostly only be vertical twitching... I'm not sure why.

This should be discussed on the forum first, as stated in our contribution guidelines. Also, this is an approximate fix anyway.

True, I guess it should just use round.

No, it should not. SFML uses C++98, std::round() is introduced in C++11.

OK, just delete it and leave it broken then.

Well, you know more about what you can use in your project. It's a really relatively simple change. You tell me what I can't use but you don't tell me what to do, so I'm not just going to keep asking what I can do when you could just tell me what to do.
Even with the approximate 0.5f fix, it's still way better than the twitchy horror that it is right now.

I don't like the ignorance in your answer "leave it broken then", I hope you understand that we can't use std::round().
We should ask ourselves if the limitations mentioned in the StackOverflow thread are actually a problem in our case, or if std::floor(x + 0.5f) (or with static_cast) just works fine. What about negative numbers, have you tested the code for negative coordinates?
Also, could you share the most simple code that reproduces the problem? Ideally with shapes, so we don't need external resources.

Well, that's more the kind of answer I was looking for. I mean I guess it's not such a big deal, but honestly every time I've tried to help SFML it usually results in what appears as carelessness.
Here are the possible solutions I can think of:

Use a custom round function (this is the most accurate): float round(float number) {   return number < 0.0f ? ceil(number - 0.5f) : floor(number + 0.5f); }
Use the same method as what I committed, but using -0.5f for negative numbers. This is the most efficient as it doesn't need calls to ceil/floor—the cast to int already truncates towards zero. The only downside of this I think is that the lack of round might resurface again in other parts of SFML, so using a custom round for the entire library might be a better option.

The way it is my commit right now is that negative numbers will be off by at most 1 pixel, but at least calling the function with the same input will always map to the same output (means it won't twitch).
The problem is really easy to reproduce. Set the view zoom to 0.5f, move a rectangle shape around while keeping the view center on it. The rectangle should twitch. If you really need it I guess I can write that up.

I'm struggling to reproduce the issue. I put some code together according to your instructions, but I can't see any twitch. The position visually doesn't change at all. I added a background sprite hoping to see something, but couldn't. Can you point out what's missing?
Regarding rounding, do we even want to round towards or away from zero? This means that there will be a discontinuity at -0.5 and 0.5 (see table). This could lead to problems when objects are moved pixel-wise at half-integral coordinates.

x
static_cast<int>(x)
x < 0 ? ceil(x-0.5) : floor(x+0.5)

-2.5
-2
-3

-1.5
-1
-2

-0.5
0
-1

0.5
0
1

1.5
1
2

2.5
2
3

So, is rounding towards positive or negative infinity (e.g. floor(x+0.5)) not better suited?

Before I apply it wrong again, could you show with a code how you used it exactly? You can base your code on my Gist if you like.

https://gist.github.com/Cleroth/5dbf5c4c03ddee9e59ef

I made a compilable example to reproduce the problem. I added some inertia to the shape in order to make it have a wide range of non-integer positions. I set the zoom factor to 0.25 so the problem is even more visible.

Thanks for that. I was having trouble reproducing the problem on my application again. I realized it's because it never seemed to happened on position values below 10 or so.
Regarding how to round, Bromeon, rounding towards negative infinity gives you less accuracy inbetween whole numbers. Your table isn't exactly fair, as I don't think that if you're going to zoom closer than 1.f, then you probably aren't dealing in terms of only half pixels. Round away from zero still gives 0.5 > x < 0.5 for where you can round to 0, so it's not like the value 0 is lost. And floating points are already 'inaccurate' by definition anyway.
I've updated the code to round away from 0. and this will give the most accuracy if you were slowly 'passing' by 0.

Uh... there's still a problem with it. It seems if the viewport size is odd, it'll start twitching in that axis. I'm not really sure why yet.

Rounding with 0.25f instead of 0.5f fixes the issue, although I admit I'm not really sure why. I'm guessing it's something to do with the normalized point being halved for some reason.

So how should we proceed with this, @SFML/sfml?

My attempt:
Vector2i RenderTarget::mapCoordsToPixel(const Vector2f& point, const View& view) const
{
    // First, transform the point by the view matrix
    Vector2f coordinate = view.getTransform().transformPoint(point);

    // Then convert to viewport coordinates
    IntRect viewport = getViewport(view);
    coordinate.x = ( coordinate.x + 1.f) / 2.f * viewport.width  + viewport.left;
    coordinate.y = (-coordinate.y + 1.f) / 2.f * viewport.height + viewport.top;

    Vector2i pixel;

    // Our replacement for the lack of std::round in C++98
    // Round Half Away From Zero
    if (coordinate.x < 0.f)
    {
        pixel.x = static_cast<int>(-(std::floor(std::abs(coordinate.x) + 0.5f)));
    }
    else if (coordinate.x > 0.f)
    {
        pixel.x = static_cast<int>(std::floor(std::abs(coordinate.x) + 0.5f));
    }

    if (coordinate.y < 0.f)
    {
        pixel.y = static_cast<int>(-(std::floor(std::abs(coordinate.y) + 0.5f)));
    }
    else if (coordinate.y > 0.f)
    {
        pixel.y = static_cast<int>(std::floor(std::abs(coordinate.y) + 0.5f));
    }

    return pixel;
}

As the comment says, this implements Round Half Away From Zero i.e. the same as std::round would do albeit we don't use built-in functions.
Nice picture from en.cppreference.com:

I'll leave this justifying quote from Wikipedia here:

This method, also known as commercial rounding, treats positive and negative values symmetrically, and therefore is free of overall bias if the original numbers are positive or negative with equal probability.
It is often used for currency conversions and price roundings (when the amount is first converted into the smallest significant subdivision of the currency, such as cents of a euro) as it is easy to explain by just considering the first fractional digit, independently of supplementary precision digits or sign of the amount (for strict equivalence between the paying and recipient of the amount).

If there are people whose maths we should take seriously, it's the ones dealing with money. :wink:

This would do the same thing:
if (coordinate.x < 0.f)
{
    pixel.x = static_cast<int>(std::ceil(coordinate.x) - 0.5f);
}
else if (coordinate.x > 0.f)
{
    pixel.x = static_cast<int>(std::floor(coordinate.x) + 0.5f);
}

if (coordinate.y < 0.f)
{
    pixel.y = static_cast<int>(std::ceil(coordinate.y) - 0.5f);
}
else if (coordinate.y > 0.f)
{
    pixel.y= static_cast<int>(std::floor(coordinate.y) + 0.5f);
}

However, rounding isn't the problem here, as even using std::round still makes it glitchy.

So... if rounding isn't the full extent of the problem in your opinion what is? The reason why the drawable isn't moving in a continuous motion is because the float to int conversion currently performed isn't monotonic. Depending on whether the current floating point value is interpreted as a whole number or not, either the higher int or the lower int is returned. This is the effect of a plain old int to float cast. If you make sure that the floating point value on its own is representable without without decimal places it will always be cleanly cast to an int. This doesn't mean that floating point arithmetic itself will always produce clean results.
Yes... I think by now we all know that floats lose precision the larger they get, but why are you making this general problem into one that is SFML specific? There is no solution for this problem that can be applied in every scenario, otherwise the IEEE would have added it to the specification when they wrote it all those years ago. If you need to use such large floating point values, you'll need to jump to double precision, and quadruple precision after that. Even if you used more precision in your code, you are still going to be limited by the OpenGL pipeline which still operates in single precision for the most part. I just don't see where you are trying to go with this observation...
I tested the code I posted with the only complete example provided here from @kimci86. If you say that it doesn't fix the problem in your case, I'll have to have something that I can build which represents it as well.

The float precision thing isn't a problem with how floats are defined, it's a problem with how you're doing the rounding. Sure, you can say rounding with 0.5f is 'good enough', but it wouldn't be as accurate as the proper std::round.
As for a replicable case, I mentioned higher up that it breaks when the either of the viewport's size is an odd number (I seem to remember it happening more on a particular axis). You might say there's not much reason for this, but the reason I did it because I had to make the window slightly larger than native resolution in order to have real borderless mode in SFML, otherwise the application is considered to be in fullscreen for some reason.
IIRC there also were issues depending on how much you zoomed.
I could delve deeper into this, but I'll be very busy for the next 2-3 weeks.

std::round will only provide as much accuracy as the compiler is willing to give you. Depending on the compiler flags you use, the compiler will typically be pessimistic and allow for slight errors in order to keep your code running with acceptable performance because it has to assume that SSE isn't available on the target platform. You can alleviate this problem a bit by convincing the compiler to use the biggest registers it can get (either double or extended double precision) to store the intermediate result which you extract your int out of:
float f = 8388609.f;
int i = static_cast<int>(static_cast<long double>(f) + 0.5l);

This will yield the expected result, will probably work for any input representable by a single precision float but might rarely lead to (unmeasurable?) performance penalties on systems that don't have wide enough registers.
I don't know if everybody is willing or cares enough about this kind of precision to build in something like this. The step before something like this would be to make sure the right compiler options are used.

So how should we move forward with this issue?

I'd say, if the only problem is the precision of the rounding, then we don't care that much (and this can be "improved" in SFML 3 if std::round were to offer better resolution) and use one the two fixes proposed above (which I haven't double checked).

But it isn't the only problem.

But it isn't the only problem.

Care to elaborate?
The only other "problems" I've noticed in this thread are 1) an application-specific issue with odd-sized view, which is a special case and obviously cannot be addressed in a general fix, and 2) a concern about the precision of this hand-made round operation with big floating point number, which I consider to be an edge case not worth more than a minor note in the doc -- in any case the user would have other issues in his/her own code because of that.
Or did I miss something else? If so, could you succinctly explain what I've missed instead of a leaving an answer full of mystery. Thanks.

It's because this thread is going round and round (no pun intended).
So yes, the other problem is the viewport thing. Why can't it be addressed with a general fix? Also I do think there were other problems apart from the odd-sized viewport, I seem to remember it not snapping properly depending on zoom values, but I can't be sure about that until I have time to retest it again.
So, to be succinct, these are options this issue:

Someone here figures out how the function works and solves the snapping to pixel 'grid' properly.
We wait 2-3 weeks when I'll have free time and can take a better look at the code, to solve it for every case.
Ignore the odd-sized viewport problem. It could be fixed from user code, but this isn't really ideal... considering the user would have to know what the problem is to begin it. It probably took me a few hours to realize what the culprit was.

Any updates @Cleroth?


Fixes for SCR test in CI

PR needed to trigger GitLab pipeline
Since we've run into this before, would it be worth extending axom_add_test as follows (pseudocode)?
if not num_mpi_tasks and enable_mpi:
  num_mpi_tasks = 1

See the current definition of axom_add_test below:
https://github.com/LLNL/axom/blob/f7d112c808e0a2767e57e6055c05d934c9538cca/src/cmake/AxomMacros.cmake#L118-L155

Thanks @joshessman-llnl for taking initiative to figure this out.


Updated implementation of query named parameters

Hello!
I saw a previous pull request about the named parameters. Since there is no activity for 3 years now, I took the liberty to make my own implementation and update the unit tests.
It allows:
$connection->query('SELECT * FROM my_table WHERE foo = :param', ['param' => 'bar']);

$connection->query('SELECT * FROM my_table WHERE foo = :param', [':param' => 'bar']);

$connection->query('SELECT * FROM my_table WHERE foo = :param AND param2 = ?', ['param' => 'bar', 'param2Value']);

Of course, all the previous ways of querying still work.
I can update the README if needed.

@Divi Thanks for looking into this, would love to get this in!
The additional tests are much appreciated, definitely helps to get some certainty with this feature. It looks like some cases aren't covered right now, can you add some additional tests to ensure this works properly when using the same placeholder name multiple times (SELECT * FROM user WHERE name = :name OR email = :name) and also what happens if the placeholder value contains strings that look like placeholders (['name' => 'is :this a placeholder?']).

Just to let you know, I've not forgotten you, I just don't have enough time for now but I keep in mind your request :)


Feature Request: Multiple Mappings from 1 Metric

Hi,
I have 1 Metric which returns a table of information, an example below:
Name, Status, uptime
I would love to be able to match objects automatically based on the "Name" column in my metric. This would save a lot of time in creating individual metrics and mappings manually for each object.

see https://github.com/algenty/grafana-flowcharting/issues/232


VS2019    Error C2664    copy example code to main()

Hello
when i copy example code to main() you can see this :

i have to do this
but why the code at example.c can run?   thank u

@txp666
Because C and C++ are different. (The 'main' function is in the C++ source file, and LVGL examples are C source files.)
Kenji Mouri

thanks!


Fixes typo in getting-started.md

Removes invalid comma in JSON configuration after ReverseProxy.Routes.route1.Match.

Was this causing an issue for you? I think the .NET Json config reader tolerates these trailing commas. Removing it is fine though.


Cleanup encryption dialog

We generally shouldn't be making injected services optional - especially when we don't then also update the class to handle the service potentially not being there. It's simple and low-cost to just pass in all the services and makes things much more consistent across the application

(if you wanted to do something like that then it'd be better to make a common abstract class that both can inherit from and just exclude the services that aren't needed by both)

Also removed some uses of null - we should prefer to use undefined but in this case they're optional anyways so we can just completely remove them.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 41.96%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-bindings/src/common/azureFunctionsUtils.ts
1
80.65%

extensions/machine-learning/src/common/processService.ts
2
81.48%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
28915

Relevant Lines:
64014

💛  - Coveralls


Automated cherry pick of #9140: fix(keystone): not allow to disable sql driver

Cherry pick of #9140 on release/3.5.
#9140: fix(keystone): not allow to disable sql driver

Codecov Report

Merging #9142 (5abf887) into release/3.5 (6a15e02) will decrease coverage by 1.77%.
The diff coverage is 5.88%.

@@               Coverage Diff               @@
##           release/3.5   #9142       +/-   ##
===============================================
- Coverage         5.98%   4.21%    -1.78%
===============================================
  Files              796     163      -633
  Lines           125693   24889   -100804
===============================================
- Hits              7522    1048     -6474
+ Misses          117504   23749    -93755
+ Partials           667      92      -575

Flag
Coverage Δ

aFlag
4.21% <5.88%> (-1.78%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/cloudcommon/db/jointbase.go
0.00% <ø> (ø)

pkg/cloudprovider/objectstore.go
2.57% <ø> (ø)

pkg/compute/regiondrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/hostman/hostinfo/hostovn.go
27.45% <0.00%> (-2.03%)
:arrow_down:

pkg/multicloud/esxi/host.go
0.77% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/manager.go
0.70% <0.00%> (-0.01%)
:arrow_down:

pkg/util/netutils2/netutils.go
21.62% <100.00%> (+0.35%)
:arrow_up:

pkg/baremetal/tasks/base.go

pkg/compute/models/scaling_activity.go

pkg/multicloud/aws/reservedinstance.go

... and 598 more

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 a638781...5abf887. Read the comment docs.


chapter 4 only the crud on products part

Chapter 0-4

I like the name of the commit, it includes the chapter and a description of what it contains but I would have liked you to commit more often. This is a good practice advice, try to do small and often commits.

I see that you also have an .idea folder at the same level with the root project folder. That was pushed by mistake because the .gitignore within the project only ignores the .idea from within the project iself. You should delete that .idea folder, then stage it in git (cd .. to get to it and then git add . after you have manually deleted it). After follows of course a new commit and push. We should not see in this PR that .idea folder anymore


I get "Failed to load any lstm-specific dictionaries for lang ea!!" when predicting with fintuned model

I am trying to finetune a model with a hundreds of images.
I am using the ara model as the START_MODEL running this command:
make training MODEL_NAME=ea START_MODEL=ara TESSDATA=data/ara
The new model is supposed to perform better than the base model (ara). But I am getting bad results
Example:

With ara best model I get:
بن عثمان بِن الهادي _
with the finetuned model I get:
ﻦﻴﻣﺟﺟﺟﺟ_ﺎﻟﺒﻟﻤﻟﻟﺍﻣ

Two very different things in one issue.

Failed to load any lstm-specific dictionaries for lang ea

This expected since dictionaries are not carried over to the finetuned model (on purpose). Using dictionaries is not recommended in general for LSTM-based OCR.

The new model is supposed to perform better than the base model

Not necessarily. This very much depends on your training and especially on the images you feed into it. Your example has a very bad line segmentation. Are you using PSM=7 or PSM=13?

This expected since dictionaries are not carried over to the finetuned model (on purpose). Using dictionaries is not recommended in general for LSTM-based OCR.

Thank you for your response. I'm not using dictionaries, IS this acceptable as a warning? Could it affect my trained model?

Not necessarily. This very much depends on your training and especially on the images you feed into it. Your example has a very bad line segmentation. Are you using PSM=7 or PSM=13?

I am using PSM=13 for the training and prediciton.

Thank you for your response. I'm not using dictionaries, IS this acceptable as a warning? Could it affect my trained model?

Yes. Definitely. No worries.

I followed the documentation . I prepared 350 one line Arabic images (xx.png) and their transcript (xx.gt.txt) and starting training with START_MODEL=ara.

make training MODEL_NAME=elda START_MODEL=ara TESSDATA=data/ara_best

I am getting 100% as error rate.

I there something I am missing?

What is ara_best? The TESSDATA parameter should direct to your Tesseract model directory (e.g. /usr/local/share/tessdata in most cases).


Try using connection candidates with wg before starting a proxy

Currently, all Wireguard data is passed through the Wireguard proxy even though the connection candidates could be directly passed as peers to Wireguard. I think we only really need the proxy if a TCP TURN relay is used.

Thanks, @stv0g for the suggestion.
It is generally a good idea to avoid using a local proxy for the Wg traffic, however, in our case it won't be a quick change.
Let me explain why.

We allow each peer to have multiple connections simulteniously.
We use plain pion/ice that has a hole punching logic embedded and handled by the framework. And it is always a new random UDP port.

So, we would always need to update the Wireguard listen port with a new port (from #2), this will interrupt other connections (#1) and the logic becomes quite complex.
We had an idea of taking control of a socket used by pion/ice and completely getting rid of a local proxy. We will be looking into that.
For now, what we have implemented so far was the quickest (implementation-wise) and quite a good solution.
We will be also posting some benchmarks Pure Wireguard vs Wiretrustee.

Hi @braginini
thanks for the detailed explanation.

So, as I understood you correctly, we would always need to update the Wireguard listen port with a new port (from #2), this will interrupt other connections (#1) and the logic becomes quite complex.

I agree. Maybe AgentConfig.PortMin and AgentConfig.PortMax could be used to restrict pion/ice to a single port which is used as Wireguards ListenPort?
pion/ice will probably fail as the port is already bound by Wireguard.
So Wireguard would need to be stopped during the connectivity checks and hole punching.
Indeed not a trivial change.
I thought about using iptables/netfilter with a redirect rule pointing to the chosen candidate pair.
But that wouldnt be portable :/

We will be also posting some benchmarks Pure Wireguard vs Wiretrustee.

I would be very much interested in that!


Fix collapsing/expanding layout when it already in that state.

Add checking for current state before collapsing or expanding.

Thx


Wrong handling of nested optional arguments

Suppose we have optional start and end args, so as if 2 args are specified 1st is start and 2nd is end, but if only one arg is specified it means end.
doc = '''
usage:
    app [<start> [<end>]]
'''
from docopt import docopt

import sys
sys.argv = ['app', 'arg']
opts = docopt(doc)
print(opts)

It prints {'<end>': None, '<start>': 'arg'}, the expected result being {'<end>': 'arg', '<start>': None}

This works: main (<end> | <start> <end>)


Speed up wallet creation

Description of PR...
Changes

Item 1
Item 2

API Updates
New Features (required)
This section should include details regarding new features added to the library.
This should include both open and private APIs. If including both, create two
sub headers underneath this one to label updates accordingly.
Deprecations (required)
All deprecations should be listed here in order to ensure the reviewer understands
which sections of the codebase will affect contributors and users of the library.
Enhancements (optional)
The enhancements section should include code updates that were included with this
pull request. This sections should detail refactoring that might have affected
other parts of the library.
Checklist

[ ] Unit tests
[ ] Documentation

References
(optional)
Include important links regarding the implementation of this PR.
This usually includes and RFC or an aggregation of issues and/or individual conversations
that helped put this solution together. This helps ensure there is a good aggregation
of resources regarding the implementation.
Fixes #85, Fixes #22, Fixes username/repo#123
Connects #123

Total Coverage: 0 %
Coverage report

File
% Stmts
% Branch
% Funcs
% Lines
Uncovered Line #s

All files
67.53
45.23
54.36
68.82

src
100
100
0
100

index.ts
100
100
0
100

src/crypto/bip32
72.22
100
50
72.22

hd-wallet.ts
66.66
100
50
66.66
6-10,22

hdwallet-token.ts
83.33
100
50
83.33
24

src/crypto/bip39
83.33
100
62.5
83.33

bip39-token.ts
100
100
100
100

bip39.ts
75
100
50
75
5,8,11

src/crypto/ecc
85.71
20
60
84.61

secp256k1.ts
85.71
20
60
84.61
13,28

src/crypto/hashes
77.77
100
0
71.42

hashes.ts
77.77
100
0
71.42
10,14

src/encryption-utils
100
75
100
100

encryption-utils.ts
100
75
100
100
50-66

src/key
53.43
22.41
53.48
55.26

eth-wallet.ts
43.52
30
36.84
46.83
39,93-164

wallet-utils.ts
96.77
76.92
100
96.66
43

wallet.ts
47.72
0
57.89
48.14
32-71,132-168

src/keychain
69.03
59.72
54.54
71.14

keychain.ts
69.03
59.72
54.54
71.14
36,69,77,132,163-199,222-252,321

src/storage
100
100
100
100

storage-layer.ts
100
100
100
100

src/types
100
100
100
100

keychain.ts
100
100
100
100

src/utils
65.51
42.85
50
65.45

bech32-address-converter.ts
100
100
100
100

correct-mnemonic.ts
66.66
100
0
100

encode-signature.ts
88.88
80
100
88.88
6

encoding.ts
88.88
0
100
87.5
3

get-hdpath.ts
100
50
100
100
1

init-crypto.ts
66.66
100
0
66.66
12-16

serialize-signdoc.ts
25
0
0
25
5-18,22-23,27

tests
100
100
100
100

mockdata.ts
100
100
100
100


Shell script does not pass args correctly

The your_grep.sh is not passing arguments with spaces correctly to stack.
Suppose our app is just this little program:
module Main where

import System.Environment

main :: IO ()
main = do
  args <- getArgs
  putStrLn $ show args

With the current your_grep.sh we'll get the following output:
> ./your_grep.sh -E "b r"
["-E","b","r"]

If we change your_grep.sh from...
exec stack run --silent -- $@

...to (note the double quotes)...
exec stack run --silent -- "$@"

...then we get something more useful:
> ./your_grep.sh -E "b r"
["-E","b r"]

The current reference solution has a little unwords hack to deal with this after the fact. The above change would not cause the reference solution to fail, though. The unwords call would just be redundant.
@rohitpaulk what do you think?

@bert2 ah, yeah quoting makes sense! Want to open a PR? I'll also check to see if we're doing this wrongly for other languages.

All the other languages in the grep challenge use "$@" instead of<EMAIL_ADDRESS>I didn't check any other challenges.

Closed by #26.


Update javascript-framework-extensions.md

Inside documentation we use react, but package installation uses angular libraries

@AaronMaxwell
Can you review 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


fix actions/setup-java parameters

Release Note
NONE

@christophd the install-it failure seems to be unrelated


Fake resolver: Added ability to specify response upon error

Extracted from @AspirinSJL 's PR https://github.com/grpc/grpc/pull/13671

Closing, @AspirinSJL will create a separate one.


Fix Ubuntu-only test flakiness

This problem may be in TestHost; assuming it's a test issue for now.
Affected builds
Working backward through Travis builds:
https://travis-ci.org/aspnet/Mvc/jobs/215670472 (today)
15 failures due to IOException from TestHost. Details at the bottom of this issue.
https://travis-ci.org/aspnet/Mvc/jobs/215670049
5 failures, 4 due to IOException from TestHost. Mostly a subset of the above (and Details below) but adds Microsoft.AspNetCore.Mvc.FunctionalTests.CompilationOptionsTests.CompilationOptions_AreUsedByViewsAndPartials and fails in Microsoft.AspNetCore.Mvc.FunctionalTests.RazorViewLocationSpecificationTest.PartialLayoutPaths_SpecifiedInPage_GetResolvedByViewEngine(actionName: "LayoutSpecifiedWithPartialPathInPageWithPartialPat"...) instead of PartialLayoutPaths_SpecifiedInPage_GetResolvedByViewEngine(actionName: "LayoutSpecifiedWithPartialPathInPageWithPartialPat"...).
https://travis-ci.org/aspnet/Mvc/jobs/215661887
8 failures due to IOException from TestHost. Breaks a slightly different set of tests, some overlapping those listed below.
https://travis-ci.org/aspnet/Mvc/jobs/215618686
26 failures, 25 due to IOException from TestHost.
https://travis-ci.org/aspnet/Mvc/jobs/214120356
10 failures, 9 due to IOException from TestHost.
https://travis-ci.org/aspnet/Mvc/jobs/213952543
11 failures, 10 due to IOException from TestHost.
https://travis-ci.org/aspnet/Mvc/jobs/213843173
15 failures due to IOException from TestHost.
https://travis-ci.org/aspnet/Mvc/jobs/213542244 (6 days ago)
24 failures, 23 due to IOException from TestHost.
Details
Failed tests

Microsoft.AspNetCore.Mvc.FunctionalTests.ViewEngineTests.RazorViewEngine_RendersPartialViews(actionName: "ViewWithoutLayout", expected: "ViewWithoutLayout-Content")
Microsoft.AspNetCore.Mvc.FunctionalTests.RequestServicesTest.RequestServices(url: "http://localhost/RequestScopedService/FromViewComp"...)
Microsoft.AspNetCore.Mvc.FunctionalTests.RazorPagesWithBasePathTest.IndexAtBasePath_IsRouteableAtRoot
Microsoft.AspNetCore.Mvc.FunctionalTests.LinkGenerationTests.GeneratedLinks_AreNotPunyEncoded_WhenGeneratedOnViews
Microsoft.AspNetCore.Mvc.FunctionalTests.TagHelpersTest.CanRenderViewsWithTagHelpersAndUnboundDynamicAttributes_Encoded
Microsoft.AspNetCore.Mvc.FunctionalTests.RazorPagesTest.PageModel_Handler_ReturnTypeImplementsIActionResult
Microsoft.AspNetCore.Mvc.FunctionalTests.UrlResolutionTest.AppRelativeUrlsAreResolvedAndEncodedCorrectly
Microsoft.AspNetCore.Mvc.FunctionalTests.RazorPageExecutionInstrumentationTest.InstrumentedViews_RenderAsExpected
Microsoft.AspNetCore.Mvc.FunctionalTests.RazorViewLocationSpecificationTest.PartialLayoutPaths_SpecifiedInPage_GetResolvedByViewEngine(actionName: "LayoutSpecifiedWithPartialPathInPageWithPartialPat"...)
Microsoft.AspNetCore.Mvc.FunctionalTests.MvcSandboxTest.RazorPages_ReturnSuccess
Microsoft.AspNetCore.Mvc.FunctionalTests.DirectivesTest.ViewAndViewComponentsReplaceTModelTokenFromInheritedBasePages
Microsoft.AspNetCore.Mvc.FunctionalTests.BasicTests.CanRender_ViewsWithLayout(url: "Home/Index")
Microsoft.AspNetCore.Mvc.FunctionalTests.HtmlHelperOptionsTest.OverrideAppWideDefaultsInViewAndPartialView
Microsoft.AspNetCore.Mvc.FunctionalTests.RemoteAttributeValidationTest.RemoteAttribute_LeadsToExpectedValidationAttributes(areaName: "Area1", pathSegment: "/Area1")
Microsoft.AspNetCore.Mvc.FunctionalTests.HtmlGenerationTest.HtmlGenerationWebSite_GenerateEncodedResults(action: "Order", antiforgeryPath: "/HtmlGeneration_Order/Submit")

Sample stack trace below. Many traces are consistent up to ViewExecutor.cs(259,0). Occasionally that line is called from /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.RazorPages/Internal/PageActionInvoker.cs(383,0).
System.IO.IOException : The request was aborted or the pipeline has finished
Stack Trace:
     at Microsoft.AspNetCore.TestHost.ResponseStream.CheckNotComplete()
     at Microsoft.AspNetCore.TestHost.ResponseStream.Write(Byte[] buffer, Int32 offset, Int32 count)
     at Microsoft.AspNetCore.TestHost.ResponseStream.WriteAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)
     at Microsoft.AspNetCore.WebUtilities.HttpResponseStreamWriter.<FlushInternalAsync>d__26.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.ViewFeatures/ViewFeatures/ViewExecutor.cs(259,0): at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.<ExecuteAsync>d__22.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.ViewFeatures/ViewFeatures/ViewExecutor.cs(193,0): at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.<ExecuteAsync>d__21.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.ViewFeatures/PartialViewResult.cs(76,0): at Microsoft.AspNetCore.Mvc.PartialViewResult.<ExecuteResultAsync>d__26.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ResourceInvoker.cs(148,0): at Microsoft.AspNetCore.Mvc.Core.Internal.ResourceInvoker.<InvokeResultAsync>d__15.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ControllerActionInvoker.cs(860,0): at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextResultFilterAsync>d__19.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ControllerActionInvoker.cs(976,0): at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ResultExecutedContext context)
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ControllerActionInvoker.cs(680,0): at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ControllerActionInvoker.cs(907,0): at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeInnerFilterAsync>d__21.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ResourceInvoker.cs(527,0): at Microsoft.AspNetCore.Mvc.Core.Internal.ResourceInvoker.<InvokeNextResourceFilter>d__18.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ResourceInvoker.cs(560,0): at Microsoft.AspNetCore.Mvc.Core.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ResourceInvoker.cs(487,0): at Microsoft.AspNetCore.Mvc.Core.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ResourceInvoker.cs(134,0): at Microsoft.AspNetCore.Mvc.Core.Internal.ResourceInvoker.<InvokeFilterPipelineAsync>d__13.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
  /home/travis/build/aspnet/Mvc/src/Microsoft.AspNetCore.Mvc.Core/Internal/ResourceInvoker.cs(92,0): at Microsoft.AspNetCore.Mvc.Core.Internal.ResourceInvoker.<InvokeAsync>d__11.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
     at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
     at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.<Invoke>d__4.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
     at Microsoft.AspNetCore.Hosting.Internal.RequestServicesContainerMiddleware.<Invoke>d__3.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
     at Microsoft.AspNetCore.TestHost.ClientHandler.<>c__DisplayClass3_0.<<SendAsync>b__0>d.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
     at Microsoft.AspNetCore.TestHost.ClientHandler.<SendAsync>d__3.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
     at System.Net.Http.HttpClient.<FinishSendAsyncUnbuffered>d__59.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
     at System.Net.Http.HttpClient.<GetStringAsyncCore>d__27.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
  /home/travis/build/aspnet/Mvc/test/Microsoft.AspNetCore.Mvc.FunctionalTests/ViewEngineTests.cs(243,0): at Microsoft.AspNetCore.Mvc.FunctionalTests.ViewEngineTests.<RazorViewEngine_RendersPartialViews>d__19.MoveNext()

I removed all lines matching
     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

One of the simpler stack traces, again removing the "I rethrew frames", was
 System.IO.IOException : The request was aborted or the pipeline has finished
Stack Trace:
   at Microsoft.AspNetCore.TestHost.ResponseStream.CheckNotComplete()
   at Microsoft.AspNetCore.TestHost.ResponseStream.Flush()
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.IO.StreamWriter.Dispose(Boolean disposing)
   at RazorPageExecutionInstrumentationWebSite.Startup.<>c.<<Configure>b__1_0>d.MoveNext() in /home/travis/build/aspnet/Mvc/test/WebSites/RazorPageExecutionInstrumentationWebSite/Startup.cs:line 40
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.TestConfiguration.CultureReplacerMiddleware.<Invoke>d__3.MoveNext() in /home/travis/build/aspnet/Mvc/test/WebSites/Microsoft.AspNetCore.Mvc.TestConfiguration/CultureReplacerMiddleware.cs:line 36
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Hosting.Internal.RequestServicesContainerMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.TestHost.ClientHandler.<>c__DisplayClass3_0.<<SendAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.TestHost.ClientHandler.<SendAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at System.Net.Http.HttpClient.<FinishSendAsyncUnbuffered>d__59.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at System.Net.Http.HttpClient.<GetStringAsyncCore>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.FunctionalTests.RazorPageExecutionInstrumentationTest.<InstrumentedViews_RenderAsExpected>d__5.MoveNext() in /home/travis/build/aspnet/Mvc/test/Microsoft.AspNetCore.Mvc.FunctionalTests/RazorPageExecutionInstrumentationTest.cs:line 33

// @Tratcher

@dougbu - can you take a first stab at investigating these?

After talking with @Tratcher, I'll focus on HttpClient timeout settings and long-running tests.
Tried to reproduce the issue on various Linux machines (local VM, Azure F4, and Azure D15) without seeing it at all. Ran the functional tests at least 40 times per machine. But, it's possible the Travis VMs are substantially slower than anything I was using.
However, problems have not been corrected with newer CLI et cetera. Recent failed Travis builds include:

https://travis-ci.org/aspnet/Mvc/jobs/220776056 (14 days ago)
https://travis-ci.org/aspnet/Mvc/jobs/220629441
https://travis-ci.org/aspnet/Mvc/jobs/219006235
https://travis-ci.org/aspnet/Mvc/jobs/218719082
https://travis-ci.org/aspnet/Mvc/jobs/218629141
https://travis-ci.org/aspnet/Mvc/jobs/218342982 (21 days ago)

3 tests failed in https://travis-ci.org/aspnet/Mvc/jobs/219006235, the least of the Travis runs listed in my previous comment. The tests were in 3 different classes and each is the slowest test in those classes when run in VS. The next-slowest test in each class is at least an order of magnitude faster. But, the failing tests take only 5 seconds in local testing -- not the 100 seconds required for HttpClient to time out.

Microsoft.AspNetCore.Mvc.FunctionalTests.AntiforgeryTests.SetCookieAndHeaderBeforeFlushAsync_GeneratesCookieTokenAndHeader
Microsoft.AspNetCore.Mvc.FunctionalTests.DirectivesTest.ViewInheritsBasePageFromViewStarts
Microsoft.AspNetCore.Mvc.FunctionalTests.ViewEngineTests.RazorViewEngine_UpdatesViewsReferencedViaRelativePathsOnChange

HttpClient.Timeout is not referenced anywhere in the MVC repo. I suspect we're dealing with a somewhat-random slowdown that's specific to Ubuntu on Travis, not Travis in general.

f68bea235

@dougbu - please add a note explaining why.

Made f68bea235 after trying unsuccessfully to reproduce the problem locally. While Travis VMs start slower than their containers, we see failures often enough when using containers that they are not an option for this repo. (Others have reported container-specific Travis issues e.g. travis-ci/travis-ci#4691.)


corrects broken composer palette icon for Artemis

The Artemis logo on the composer palette was a hotlink from the ActiveMQ site. The link was no longer valid. Added static image to brooklyn-library and adjusted path.

I guess we should use the same log for all the activemq entites?  So might be better to update the existing one?

I guess we should use the same log for all the activemq entites? So might be better to update the existing one?

Done!

I'd be inclined to remove artemis-logo.png and simply reference the updated activemq for that one.
@frogfather do you have an Apache ICLA?
i'll update the notice metadata to note we are including that file in our source dist.

looks good.  i've added a comment to our notices about use of logos, in a separate PR.
as soon as @frogfather has an ICLA approved i think this can be merged

@frogfather you're listed with an ICLA, so merging


[comet-parquet-exec] Merge upstream/main and resolve conflicts

This reflects a merge of upstream/main (as of this morning) and then a resolution of the conflicts. This catches up comet-parquet-exec feature branch on about a month of changes, including a release.
COMET_FULL_NATIVE_SCAN_ENABLED:
Tests: succeeded 728, failed 64, canceled 2, ignored 52, pending 0
COMET_NATIVE_RECORDBATCH_READER_ENABLED :
Tests: succeeded 722, failed 70, canceled 2, ignored 52, pending 0
These new test failures are mostly converting timestamps to timestamps, for example: Cause: org.apache.comet.CometNativeException: Cannot cast file schema field _19 of type Timestamp(Microsecond, Some("UTC")) to required schema field of type Timestamp(Microsecond, Some("America/Los_Angeles"))
@andygrove understands the issue, so we'll fix it after this PR merges.

See https://github.com/apache/datafusion-comet/pull/1182 to see the diff of this branch versus upstream/main, which should give an idea of what comet-parquet-exec feature branch's diff against upstream/main is after this merges.


Performance Discrepancy Between SAM Model Demo and GitHub Code

Hi, I am working on segmenting car bodies in images using the Meta SAM model. I am facing a significant difference in performance between the UI demo on the official website and the code provided on the GitHub repository. UI demo performed remarkably well with just 1-2 clicks, however, when I attempted to use the code, results are very different and bad. Despite of  providing multiple points, the results were not up to the mark as compared to the demo.
Using SAM Model Version:- "vit_h"
Used predictor_example file:- notebooks/predictor_example.ipynb
Examples:
Image 1:
Original Image:

UI Demo Segmentation: - Performed well with 4 foreground points and 3 background points.

My Code Segmentation: - Poor results with the same point placement.

Image 2:
Original Image:

UI Demo Segmentation: - Good results with 4 foreground points and 4 background points.

My Code Segmentation: - Poor results with the same point placement.

I would appreciate any insights into why this discrepancy is happening.
Could it be related to hidden hyperparameter settings, optimizers, or learning rates used in the UI demo that aren't included in the GitHub code?
If this is the case, would it be possible to provide some guidance.

I have the same question.

same problem

The online and library versions are probably using different hyperparamters. Checkout this notebook: https://github.com/facebookresearch/segment-anything/blob/main/notebooks/automatic_mask_generator_example.ipynb

Cell 24 indicates the config options. The parameter names are mostly self
explanatory.
El mar, 17 de sept de 2024, 15:36, Ted Wong @.***>
escribió:

What exactly to check in the notebook?
—
Reply to this email directly, view it on GitHub
https://github.com/facebookresearch/segment-anything/issues/762#issuecomment-2356635060,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMA6BZXPR7CVK7JPAT2Z6DZXBZD3AVCNFSM6AAAAABJPURO5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJWGYZTKMBWGA
.
You are receiving this because you commented.Message ID:
@.***>

same question.


Custom Icons

Library looks great! One question, is there a way to have custom icons / components for the copy, edit, or delete actions?

Owo, I will.

I have simply added custom copy/copied icon property at the latest canary version. Please check it.

Works well; might be a typo with "CopidComponent" instead of "CopiedComponent".

@YYsuni Great Library!
Can we also add the same for other icons Edit, Confirm Edit, and Cancel Edit?
Thanks!

@kirillbashtenko ❤ Lastest canary version released.

Closing as its available in canary; thanks!


feat: add mattn/zig-update

mattn/zig-update:
$ aqua g -i mattn/zig-update

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well. Please confirm if this package works well yourself as much as possible.
Command and output
$ mkdir ~/zig
$  zig-update aarch64-macos ~/zig/ # if  you use apple sillicon. check https://github.com/mattn/zig-update#usage

If files such as configuration file are needed, please share them.

Reference

https://github.com/mattn/zig-update

Sorry I found my mistakes
let me fix it


Help me

Hello this I obfusque a code for a client and I obfusca for something then I forgot to save the src https://pastebin.com/JDysh3Fn

I need yes or yes to recover that code I can even pay if you can call me at md

There's no way to recover the original code.

Okey.

 Sadly you can't revert obfuscated code


Only install pytest-runner if needed

Only add pytest-runner to setup_requires if doing a test invocation.
Fixes #2677.

LGTM. One suggestion, but it's optional.


Kafka tutorial

@travisturner I think this has the same fixes from your PR. This was actually based of cluster-resize-support, and not master - master is compatible with v0.8.x, and cluster-resize-support is of course tracking cluster-resize

Thanks @jaffee. I confirmed that the tests in this PR pass. I'll close my related PRs and work from this branch.

@travisturner I've removed references to cluster-resize from the dep files and the kafka tutorial - This PR includes cluster-resize support, and is probably less broken that PDK master at this point.

merging this so we have master compatibility


i3 compat dropped?

I suspect this commit drops i3 compatibility:
$ sway-overfocus split-rt float-rt output-rw
swayipc error: unknown variant `changed`, expected `fresh` or `none` at line 1 column 2380

$  i3 -v
i3 version 4661e74+ © 2009 Michael Stapelberg and contributors

Running sway-overfocus v0.2.4. Downgrading back to sway-overfocus v0.2.3-fix works fine.
Note i3 is built from this commit

That's odd. Part of the reason for the upgrade was to get better compatibility with i3 from swayipc-rs.
Can you send the output of i3-msg -t get_tree when you get this error?

Seems likely to be https://github.com/JayceFayne/swayipc-rs/commit/2ef86da3b0f1448e0ecf5e5d55f3f7b2a5ca0ba7 missing a changed variant.

Can you send the output of i3-msg -t get_tree when you get this error?

https://gist.github.com/laur89/d9d84d1bb7c40aa9f06a4b58ca4a5b80

Yup, 5b03dca fixes it. Cheers!


/startup-report Not working

I am trying this out and gone through readme twice to confirm if I have missed something. However, I am not getting anything on /startup-reports

I am getting this above error. I am using Gitpod workspace with java 11.0.17. Any suggestions what I might be doing wrong?

I believe you need to remove optional element from dependency.

Or perhaps it had test scope in example. I just hit the same problem. It is fixed now.


[*.py] Rename "Arguments:" to "Args:"

I've written custom parsers and emitters for everything from docstrings to classes and functions. However, I recently came across an issue with the TensorFlow codebase: inconsistent use of Args: and Arguments: in its docstrings. It is easy enough to extend my parsers to support both variants, however it looks like Arguments: is wrong anyway, as per:

https://google.github.io/styleguide/pyguide.html#doc-function-args @ ddccc0f

https://chromium.googlesource.com/chromiumos/docs/+/master/styleguide/python.md#describing-arguments-in-docstrings @ 9fc0fc0

https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html @ c0ae8e3

Therefore, only Args: is valid. This PR replaces them throughout the codebase.
PS: For related PRs, see tensorflow/tensorflow/pull/45420

As a general convention, use fully-spelled out names rather than abbreviations, since it is more user-friendly. "Args" is not a dictionary word. We could simply standardize on "Arguments".

@fchollet As a general convention following the formal specification is recommended; to take your advice to its logical extreme, using function_definition rather than def in Python code would be warranted! In this circumstance though, there is no formal specification, however the references shown from Google indicates official use of Args:—rather than Arguments:—and sphinx is following suite.

@fchollet Did you see my comment? - Happy to merge master and redo sed (or fastmod -F)…


Support of default value for parameter in Kotlin

Current Behavior
When we use the annotations to set argument, the default value from kotlin declaration is not supported.
With the current system, the command bellow cannot be  executed when the player doesn't define the values for args :
@CommandMethod("test [x] [y] [z]")
@CommandDescription("Test command")
suspend fun testCmd(
        player: Player,
        @Argument("x") x: Double = player.location.x,
        @Argument("y") y: Double = player.location.y,
        @Argument("z") z: Double = player.location.z
) {
 println("parameters : $x $y $z")
}

If the user doesn't add an argument, a null value will be used to set the arguments.
Effectively, in the @Argument, there is a String to define the default value, but in the most cases, it's not enough.
Expected Behavior
The command defined above can be used if the user writes :
/test
/test 1
/test 1 2
/test 1 2 3

When we use the annotations to set argument, the default value from kotlin declaration is not supported.

Default arguments in Kotlin just end up generating overloaded methods. So, in order to support these default arguments we'd have to support overloaded methods. While possible, I am not entirely convinced that this is something we want.
A strategy for implementing this system would be to find all methods with identical @CommandMethod annotations and then pick the most verbose method and infer argument types from that one. We'd also have to have to add support for multiple methods in the command executor.

I don't know if this can help you for the implementation, but with the kotlin reflection, you can call a function using the default variable (if you put not enough  parameters) through the method KFunction.callBy.
This is an exemple :
class A {

    fun myMethod(
        value1: Int,
        value2: String = "test"
    ) {
        println("$value1 : $value2")
    }

}
fun main() {
    val instance = A()
    val kfun = instance::class.functions.find { it.name == "myMethod" }!!
    val parameters = kfun.parameters
    kfun.callBy(mapOf(parameters[0] to instance, parameters[1] to 1))
}

The console will be print 1 : test.
So if you use the KFunction instance, you can directly call the function with default parameter. And for the suspending method, you can use the method  KFunction.callSuspendBy.

To add on to this:
As per the docs, you can check if it's optional by checking KParameter#isOptional. If it is optional, then it can be omitted when invoking KFunction#callBy.
It seems there is no way to get what the default value is via the kotlin reflection api, however you can still use the default without knowledge of what it is.

Perhaps a new execution handle, similar to SuspendingExecutionHandler could be introduced for this.
It could be added to a module with a name like kotlin-core, perhaps?
Of course, the SuspendingExecutionHandler would also need to be reworked to incorporate these changes as well, as you'd want feature parity for suspending and non suspending functions.
It may be possible to just have it extend this theoretical KotlinExecutionHandler. (Any better ideas for names?)

Apparently overloads are only generated if you use @JvmOverloads. I was under the impression that this was the default behaviour 🥴
If someone wants to go ahead and implement this, then it could probably become a part of cloud. It would have to go in some new module cloud-kotlin/cloud-kotlin-default-annotations or something (similar to the couroutine support module)

Have you any clue  to give us in order to start ? Which type of class must have a new implementation for that for example (I'm not fluent source code of cloud)

If someone wants to go ahead and implement this, then it could probably become a part of cloud. It would have to go in some new module cloud-kotlin/cloud-kotlin-default-annotations or something (similar to the couroutine support module)

That's why I proposed something like cloud-kotlin/cloud-kotlin-core (in hindsight, I wasn't that clear about it)
Ad, @Distractic, look at SuspendingExecutionHandler and its references.


How to show SQL script?

I would like to ask how to print the execution of the SQL script?
console.log()  or  sails.log()...?
Mysql...

On the current version of the sails-mysql adapter you can pass an environment variable LOG_QUERIES=true to log the queries to stdout.

@devinivy do you think it could be possible to do this on waterline level, so its not up to the adapters to expose logging?

We can't log SQL queries on the waterline-level, since waterline doesn't run those queries (the adapter does).  What we could do is create an adapter spec for logging low-level database instructions, then allow waterline to aggregate those logs in a way that's convenient for the developer.


[snowpack build]: import.meta.env is missing when @snowpack/plugin-webpack plugin is used

Original Discussion: https://github.com/pikapkg/snowpack/discussions/1011
/cc @ralphtheninja
Minimal test case repository by @ralphtheninja (thanks!): https://github.com/ralphtheninja/snowpack-test
Next step would be to create a test in  test/build to reproduce the error. Maybe test/build/html-environment-variables) might be a good starting point? Would you like to give that a go and start a pull request with a failing test?

I have a bit of knowledge here! I believe this was introduced by a bad TODO comment that led to this PR: https://github.com/pikapkg/snowpack/pull/846
We actually should have kept using our fork this loader, since env had been added to it. By moving back to the official open-wc package, we lost env support. Reverting that PR (and handling any merge conflicts) would be the solution to this issue.
This is only an issue for the webpack plugin, and not Snowpack's build command.
@gr2m one of the reasons I'd like to tackle "new plugin tests" separately from any one PR is that there are some questions lurking that a maintainer should really address first (so that everyone else can copy from). For example, how are plugin tests organized? Can they live in each plugin's sub-directory? Can they share a runner? Etc. Etc.
@gr2m Lets spin up a thread to focus only on "how to test plugins", come up with a plan, come up with a few example tests for contributors to use as reference, and then go forward expecting all plugin changes to come with tests.

@FredKSchott I could try an earlier version of snowpack before that change was introduced to verify regression.

I can confirm that downgrading @snowpack/plugin-webpack to version 2.0.4 fixes the problem, so indeed it seems #846 broke it.

@ralphtheninja thank you for confirming!
Are you okay with using version 2.0.4 until we resolve this issue?
It would be helpful if you could try to narrow down the problem further, while we work on replicating the bug with a test for @snowpack/plugin-webpack on our side
@FredKSchott I've added it to the contribution friction thread: https://github.com/pikapkg/snowpack/discussions/958#discussioncomment-72307 I'll try to create a test to @snowpack/plugin-webpack

Are you okay with using version 2.0.4 until we resolve this issue?

Absolutely. It bundles the files and environment variables are working, which is the most important thing for me right now. Are there any important updates to the plugin that I'm missing out on? Will get them later after fix anyway.

@FredKSchott I've added it to the contribution friction thread: #958 (comment) I'll try to create a test to @snowpack/plugin-webpack

@gr2m Feel free to ping me in related issues if you don't mind. I'd like to learn more about snowpack internals.


AAAAAAAAAAAAAAAA

          Note: the above code is also good because it clearly states *at the declaration* point that the return type of `Copy` depends on the containing type.  So if you call through a derived type, you get a derived type back from the `Copy` method in a *completely* typesafe fashion.

If this was just looking up by name, the new method might return some other type entirely, which could break all successive code in the method.  For example;
    public void New_Copy(out int vertex_pro)
    {
        vertex_pro = 0;
    }

Uh oh!  Now instead of having a Vertex at the callside, you have an int, which will certainly break most code that follows that was trying to use that value.
Originally posted by @CyrusNajmabadi in https://github.com/dotnet/csharplang/issues/8115#issuecomment-2106709408

This is caught at the compilation stage since the methodpublic void New_Copy(out int vertex_pro){vertex_pro = 0;} with an int parameter does not exist.

@AlexeyZBest Stop spamming random repos.  Your post on csharplang was discussed and the reasoning was communicated to you as to the decision making here.  It was locked due to substantive progress being made on any points.  Leaking thing out to multiple different repos in response is not acceptable.


Portia has no support for Basic Auth

This isn't that common on the internet, but it's super common on internal networks that users might want to scrape. scrapy supports it via HttpAuthMiddleware, but Portia doesn't appear to be able to use it currently. There should be an option in the UI to enable Basic Auth on requests.

I added this in my fork, but I'm a bit new to Ember and Python. I tweaked a few pieces of the build process in order to get a Docker container that I could easily tweak without rebuilding for 15 minutes, but it's not required for my additions.


Msys64 Nuitka FATAL: Error, cannot add data file with 'foldr1/folder2/text.txt' path, as 'contains illegal character '/''

                                              Issue Description, Examples and Instructions

I am developing Python and wxPython Embedded Systems software for Windows 10  using the msys64 Environment.
I would like to use Nuitka for the distribution of the software.
I am experiencing the following problems in doing this 👎
1.    See Issue #3112 for the details.
This example is a very minimal wxPython GUI "Hello World" called wxhello.py and demonstrated with wxhello.sh Bash Script
This Issue is now fixed with nuitka version 2.5rc6.
I would like to contribute it as  another Nuitka Test example
  2.    This New New issue which occurs when I include sub folders with the " --include-data-dir=folder1=foldr1/" option
         Nuitka is rejecting the forward clash folder separator "/" as illegal.
         My understanding of "msys64" Environment is that a Forward Slash "/" is the default and as such should be legal

To demonstrate things I have created three Bash Scripts 👎
1    msys64setup.sh
This Bash Script sets up a msys64 Development Environment and installs Nuitka 2.5rc6.
2    wxhello.sh
This Bash Script creates whhello.py test program, builds wxhello,exe and the executes wxhello.exe.
It is using the command "nuitka --standalone wxhello.py --python-flag=-O"
This should display a wxPython GUI  as Issue #3112 problem has been resolved. Thank you.
3    include-data-dir.sh
This Bash Script creates wxhello.py test program and tries to build wxhello.exe, but fails.
It is using the command "nuitka --standalone --include-data-dir=folder1=folder1/ wxhello.py --python-flag=-O"
The problem is demonstrate as follows :-
extract the attached Nuitka.zip below to "C:"
This creates the following folder structure
c:\Nuitka
|____msys64nuitkatest
|             |____folder1
|             |          |folder2
|             |                     |text.txt
|             | include-data-dir.sh
|             | wxhello.py
|             |____wxhello.sh
|____msys64setup
|             |____msys64setup.sh
|____NuitkaTest-Output-Log.txt
Install msys64 as follows 👎
Goto https://www.msys2.org   and download the installer by clicking "msys2-x86_64-20240727.exe" link.
Install "msys2-x86_64-20240727.exe" to C:\Nuitka\msys64.
When the msys64 terminal runs execute the following Bash commands to initialise msys64👎
$ cd /c/Nuitka
$ ./msys64setup/msys64setup.sh
Restart the msys64 terminal by executing "c:\Nuitka\msys64\ucrt.exe"
When the msys64 terminal runs execute the following Bash commands to setup the Environment and install Nuitka 2.5rc6 👎
$ cd /c/Nuitka
$ ./msys64setup/msys64setup.sh
All is now ready to do the Nuitka testing
Test 1 create and execute wxhello.py by using the following commands 👎
Nuitka commandline     "nuitka --standalone wxhello.py --python-flag=-O"
Restart the msys64 terminal by executing "c:\Nuitka\msys64\ucrt.exe"
When the msys64 terminal runs execute the following Bash commands to setup msys64 and install Nuitka 2.5rc6 👎
$ cd /c/Nuitka
$ ./msys64nuitkatest/wxhello.sh
A wxPython GUI should be successfully displayed.
   Test 2 create and execute wxhello.py by using the following commands 👎
          Nuitka commandline    "nuitka --standalone --include-data-dir=folder1=folder1/ wxhello.py --python-flag=-O"
           Restart the msys64 terminal by executing "c:\Nuitka\msys64\ucrt.exe"
           When the msys64 terminal runs execute the following Bash commands to setup msys64 and install Nuitka 2.5rc6 👎
           $ cd /c/Nuitka
           $ ./msys64nuitkatest/wxhello.sh
           A wxPython GUI should be successfully displayed.
See    NuitkaTest-Output-Log.txt  whis my output log from using the attached  zipfile.

Attachment:-
Nuitka.zip

Your understanding might be wrong, though. I think some MSYS2 programs might be doing stuff. Trailing slashes are not necessary as an aside. Using the MinGW variant of MSYS2, for Nuitka, this is Win32 and the forward slash is not allowed in file paths. However, I am not sure, if we don't normalize paths for other options, in which case forward slashes would work on other platforms. I am usually using git bash, which converts slashes for me, so some testing will be needed here.

I am pretty sure this works:
nuitka-project: --include-data-file={MAIN_DIRECTORY}/example.avi=example.avi

And this works with standard Python:

python3.12 bin/nuitka --standalone --include-data-dir=doc/=doc/ tests/basics/AssertsTest.py
Nuitka-Options: Used command line options: --nofollow-imports --standalone --include-data-dir=doc/=doc/ tests/basics/AssertsTest.py

As can be seen, my git bash doesn't handle those trailing slashes as an error, so is this MSYS2 specific?

Indeed it is, which is very strange, since that is the Flavor: MSYS2 MinGW according to my help output and honestly, I find that very confusing, how this could be handled differently somewhere. Does it patch normpath to not do things, I am confused now.

So, I feel MSYS2 Python is doing it wrong, very wrong, to be incompatible with Windows there, apparently trying hard to avoid legal filenames to be used inside of Python.

Should Nuitka really have a replacement for this:
    # This changes the '/' to '\' on Windows at least.
    value = os.path.normpath(value)

I don't know, but a couple of places in Nuitka expect normalized paths to be easy for comparison. So, e.g. this one:
def areSamePaths(path1, path2):
    """Decide if two paths the same.

    Args:
        path1: First path
        path2: Second path

    Returns:
        Boolean value indicating if the two paths point to the
        same path.

    Notes:

        Case differences ignored on platforms where that is the
        norm, and with it normalized, and turned absolute paths, and
        even short paths, it then becomes a mere string compare after that.
    """

    if path1 == path2:
        return True

    path1 = os.path.abspath(os.path.normpath(path1))
    path2 = os.path.abspath(os.path.normpath(path2))

    if os.path.exists(path1) and os.path.exists(path2):
        path1 = getExternalUsePath(path1)
        path2 = getExternalUsePath(path2)

    path1 = os.path.normcase(path1)
    path2 = os.path.normcase(path2)

    return path1 == path2

Be my guest if anybody wants to create a getNormPath in nuitka.utils.FileOperations and make Nuitka code use in appropriate places. Until such time, with MSYS2, congratulations on using such a crappy platform. I will only consider it myself after a 2.5 release which is overdue, but still far away and 3.13 perfection.

I added said function and make use of it in the places I noticed, but it would have to be done everywhere to be sure it doesn't cause other issues.

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
Feedback on whether this is working is very welcome. Please do not share plans to do it; only confirm or deny that it is working.

Hello Kay.
I have installed nuitka version 2.5rc8 and ran my build again .
Command line is  "nuitka --standalone --include-data-dir=folder1=folder1/  wxhello.py --python-flag=-O"
Sadly the results are the same. Nuitka is rejecting the forward slash "/".
The build output is a follows
Quote:-
Creating wxhello.py
Creating msys64nuitkatest/wxhellp.py
Building wxhello.exe
changing directory to /c/Nuitka/msys64nuitkatest
Nuitka-Options: Used command line options: --standalone --include-data-dir=folder1=foldr1/ wxhello.py --python-flag=-O
Nuitka:WARNING: Using very slow fallback for ordered sets, please install 'ordered-set' PyPI package for best Python compile time
Nuitka:WARNING: performance.
Nuitka: Starting Python compilation with Nuitka '2.5rc8' on Python '3.11' commercial grade 'not installed'.
FATAL: Error, cannot add data file with 'foldr1/text.txt' path, as 'contains illegal character '/''
Unquote.
Regards Noel

Seems I noticed a problem in my testing and then forgot to push it, should be good now.

The fix for your usage is part of the 2.4.10 hotfix I just made, the wider change, that probably means to audit other os.path.normpath usages or to replace them is not done and needs help.

Hello Kay.
I have installed nuitka version 2.5rc9 and ran my build again .
Command line is "nuitka --standalone --include-data-dir=folder1=folder1/ wxhello.py --python-flag=-O"
Almost there !! Attaching nuitka-crash-report.xml as a zip file
nuitka-crash-report.zip
The build output is a follows
Quote:-
Creating wxhello.py
file wxhello.py does not exist
Creating msys64nuitkatest/wxhellp.py
Building wxhello.exe
changing directory to /c/Nuitka/msys64nuitkatest
Nuitka-Options: Used command line options: --standalone --include-data-dir=folder1=foldr1/ wxhello.py --python-flag=-O
Nuitka:WARNING: Using very slow fallback for ordered sets, please install 'ordered-set' PyPI package for best Python compile time
Nuitka:WARNING: performance.
Nuitka: Starting Python compilation with Nuitka '2.5rc9' on Python '3.11' commercial grade 'not installed'.
Nuitka-Plugins:anti-bloat: Not including '_bisect' automatically in order to avoid bloat, but this may cause: may slow down by using
Nuitka-Plugins:anti-bloat: fallback implementation.
Nuitka-Plugins:anti-bloat: Not including 'socket' automatically in order to avoid bloat, but this may cause: can break calls of
Nuitka-Plugins:anti-bloat: 'email.utils.make_msgid()'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Non downloaded winlibs-gcc 'C:/Nuitka/msys64/ucrt64/bin/gcc.exe' is being ignored, Nuitka is very dependent on the precise
Nuitka-Scons: one.
Nuitka-Scons: Backend C compiler: gcc (gcc 13.2.0).
Nuitka-Scons: Backend linking program with 15 files (no progress information available for this stage).
Nuitka-Scons: Compiled 15 C files using ccache.
Nuitka-Scons: Cached C files (using ccache) with result 'cache hit': 14
Nuitka-Scons: Cached C files (using ccache) with result 'cache miss': 1
Traceback (most recent call last):
File "C:/Nuitka/Nuitka/nuitka/main.py", line 206, in
main()
File "C:/Nuitka/Nuitka/nuitka/main.py", line 188, in main
MainControl.main()
File "C:/Nuitka/Nuitka/nuitka/MainControl.py", line 1159, in main
_main()
File "C:/Nuitka/Nuitka/nuitka/MainControl.py", line 1056, in _main
copyDataFiles(standalone_entry_points=getStandaloneEntryPoints())
File "C:/Nuitka/Nuitka/nuitka/freezer/IncludedDataFiles.py", line 629, in copyDataFiles
_handleDataFile(
File "C:/Nuitka/Nuitka/nuitka/freezer/IncludedDataFiles.py", line 582, in _handleDataFile
_checkPathConflict(included_datafile.dest_path, standalone_entry_points)
File "C:/Nuitka/Nuitka/nuitka/freezer/IncludedDataFiles.py", line 542, in _checkPathConflict
assert os.path.normpath(dest_path) == dest_path
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError
Nuitka-Reports: Compilation crash report written to file 'nuitka-crash-report.xml'. Please include it in your bug report.
Line  108   msys2.bash    All done              Nuitka test is complete
Unquote.
Hope this helps
Noel

Yes, I guess, you found another spot, where that function is expected to produce proper "native" paths.

Now time ti test version 2.4.9.
First I will build the simple wxPython "Hello World" with "nuitka --standalone wxhello.py --python-flag=-O"
Quote:-
Building wxhello.exe
changing directory to /c/Nuitka/msys64nuitkatest
Nuitka-Options: Used command line options: --standalone wxhello.py --python-flag=-O
Nuitka:WARNING: Using very slow fallback for ordered sets, please install 'ordered-set' PyPI package for best Python compile time performance.
Nuitka: Starting Python compilation with Nuitka '2.4.9' on Python '3.11' commercial grade 'not installed'.
Nuitka-Plugins:anti-bloat: Not including '_bisect' automatically in order to avoid bloat, but this may cause: may slow down by using fallback implementation.
Nuitka-Plugins:anti-bloat: Not including 'socket' automatically in order to avoid bloat, but this may cause: can break calls of 'email.utils.make_msgid()'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Non downloaded winlibs-gcc 'C:/Nuitka/msys64/ucrt64/bin/gcc.exe' is being ignored, Nuitka is very dependent on the precise one.
Nuitka-Scons: Backend C compiler: gcc (gcc 13.2.0).
Nuitka-Scons: Backend linking program with 15 files (no progress information available for this stage).
Nuitka-Scons: Compiled 15 C files using ccache.
Nuitka-Scons: Cached C files (using ccache) with result 'cache hit': 1
Nuitka-Scons: Cached C files (using ccache) with result 'cache miss': 14
Nuitka: Keeping build directory 'wxhello.build'.
Nuitka: Successfully created 'wxhello.dist/wxhello.exe'.
Unquote.
Success !! I am looking at a nice wxPython "Hello World" GUI'
Now for the big test "nuitka --standalone --include-data-dir=folder1=folder1/ wxhello.py --python-flag=-O"
Quote
Creating wxhello.py
file wxhello.py does not exist
Creating msys64nuitkatest/wxhellp.py
Building wxhello.exe
changing directory to /c/Nuitka/msys64nuitkatest
Nuitka-Options: Used command line options: --standalone --include-data-dir=folder1=foldr1/ wxhello.py --python-flag=-O
Nuitka:WARNING: Using very slow fallback for ordered sets, please install 'ordered-set' PyPI package for best Python compile time performance.
Nuitka: Starting Python compilation with Nuitka '2.4.9' on Python '3.11' commercial grade 'not installed'.
FATAL: Error, cannot add data file with 'foldr1/text.txt' path, as 'contains illegal character '/''
Line  108   msys2.bash    All done              Nuitka test is complete
Unquote.
Alas a forward slash "/"   problem is still here .
Hope this helps .
Noel

I do not recall claiming that 2.4.9 has it fixed, but 2.4.10, you probably misread that.

how do I download hotfix/2.4.10 ??
I have failed so far
Thanks Noel

I had seen that one before, and it's actually on factory already. I do of course not reproduce these things, but I found this and another similar assertion, so your chances are increasing.

Part of the current pre-release and will be in 2.5 once released.

Hello Kay.
I see quite a lot of activity but sadly I cannot run Nuitka in a Windows 10 msys64 environment.
I would very much to help in resolving this issue as I want to be able to use your commercial version for
my Embedded Systems Development Environment.
So I have created the following  bash scripts to create a msys64 test environment and tests as follows 👎
nuitka-2.4.10.sh                         For testing nuitka version 2.4.10
nuitka-2.4.11.sh                          For testing nuitka version 2.4.11
nuitka-2.5rc11.sh                        For testing nuitka version 2.5rc11 factory dev
nuitka-msys64-setup.sh              For setting up a suitable msys64 test environment
nuitka-msys64-user-manual.txt   How to setup and use the scripts
When the scripts are executed a failure will generate a "nuitka-crash-report,xml"
I am unable to attach ".xml" files
I am attaching the above scripts and the User Manual as  "nuitka.zip"
Extract "nuitka.zip"  to "C:"
nuitka.zip
I hope this helps
Cheers Noel Diviney

While I appreciate the scripts, I think I can do without. I have doubts about --python-flag=-O working for your software necessarily, you ought to remove them first thing when reporting and checking without them, to make sure it's not causing issues. If found, we fix them, but e.g. numpy used to crash with it on occasions in new releases, a lot of software doesn't like it and has no testing coverage for that mode.

As an aside, XML files fit in zip files too, you can attach them that way.

I am not sure, but are you expecting data files to be included magically, without specifying anything like that? I am very confused about that. I will try to compile wx hello world with MSYS2, but this leaves me very puzzled, what you actually mean to show.

Hello Kay.
Thank you for responding. Wit reference to the scripts I am just trying to ensure that we are on the same wavelength.
The scripts allow one to do everything in a Posix environment on Windows 10. That entails that Python,, Pip, Ide's and
all pogramming tools operate in the msys64 environment. I have taken your advice and stopped using the
"--python-flag=-O" and the results are the same. I have also run the same scripts for building and executing the nuitka
executeables on Linux with successful results. The build command lines I am using are 👎
"nuitka --standalone wxhello.py" to test that a very simple "Hello Word" GUI can be built and executed successfully.
"nuitka --standalone --include-data-dir=folder=folder/ wxhello-data.py" to test the inclusion of a data file located in a subfolder.
I notice that in msys64 nuitka version 2.4.10 the GUI is built correctly using both command lines but I get a "crash report"
using "nuitka --standalone --include-data-dir=folder=folder/ wxhello-data.py, whereas, I get a "crash report" when using
both command lines and version 2.4.11 and version 2.5rc11.
So as far as msys64 environment is concerned nuitka has taken a backward step.
I will do some more testing tomorrow and upload the resulting build logs. Delayed today due to family commitments.
As an aside it is my belief that the problem is associated with the proverbial "" backward slash folder separator in paths.
Cheers Noel Diviney.

The scripts are still great for reference, don't get me wrong. And reproducibility is a great trait of them.
I think my tests of including data files with MSYS2 were working, your example looks trivial, but of course, you lacked those options, so I assume your script doesn't actually reproduce an error at all?
I am totally convinced I might have "overseen" more slash issues in more cases, or maybe in some packages, data files via yaml config could trigger it too.
I think within the fact of having those script, the point of the report may have been missed though.

I decided to change the strategy on this one. Until proven otherwise, I will assume it works properly, which of course it may not, but nobody is going to do the work of auditing all of Nuitka for MSYS2 corner cases.

Part of the 2.5 release I just made.


pip install failed

Env

anaconda2
ubuntu 14.04

error log:
with open('HISTORY.rst') as history_file:
IOError: [Errno 2] No such file or directory: 'HISTORY.rst'

The pip repo is not updated yet. The version is 0.4

HI
Please try pip install tensorboard-pytorch --no-cache-dir to get newest version.
As for python2, it will be supported in next version.

Just made a python2 version on PyPI and tested with travis CI.
enjoy:)


UnsupportedCharsetException: cp65001 with vs code

I was trying out this library in an empty java + maven project in vs code on windows 10, upon running any simple application i get this:
Exception in thread "main" java.nio.charset.UnsupportedCharsetException: cp65001
        at java.base/java.nio.charset.Charset.forName(Charset.java:526)
        at picocli.CommandLine.getStderrEncoding(CommandLine.java:14531)
        at picocli.CommandLine.getErr(CommandLine.java:1236)
        at picocli.CommandLine.handleUnhandled(CommandLine.java:2097)
        at picocli.CommandLine.execute(CommandLine.java:2083)
        at com.example.App.main(App.java:24)

The command line of the vs code java extension when launching as debug is the following:
cmd /C "C:\Users\<username>\.vscode\extensions\vscjava.vscode-java-debug-0.36.0\scripts\launcher.bat "C:\Program Files\OpenJDK\bin\java.exe" -agentlib:jdwp=transport=dt_socket,server=n,suspend=y,address=localhost:54512 -XX:+ShowCodeDetailsInExceptionMessages -Dfile.encoding=UTF-8 @C:\Users\<username>\AppData\Local\Temp\<random name>.argfile com.example.App <actual application arugments>"

The cause seems to be the default launcher.bat which does:
REM Change code page to UTF-8 for better compatibility.
@chcp.com 65001 > NUL

The only other reference to this problem is in #1457 but it's related to argument files while it's not the case here (at least i think, the argfile here seems to be used only for vm args).
The fix proposed in that PR doesn't work as the command line already includes -Dfile.encoding=UTF-8.
I tried adding several options such as -Dsun.stdout.encoding=UTF8 -Dsun.err.encoding=UTF8 to the vmargs and none worked, ultimately the the only workaround to get it working for me was changing code page to 850 (cmd's default one) in launcher.bat which is not desirable as it will be overwritten when the extension updates and i don't know if it may break other projects.
Is there anything i'm missing ? Guess even if it's not a problem on your end it's worth noting it in the docs.

Minimal way to reproduce this without vs code:
Build anything with picocli, then in a cmd run the follwing
chcp 65001
java -jar demo.jar
REM Won't work either:
java -DFile.encoding=UTF8 -jar demo.jar

@epuni Thank you for raising this!
Are you also seeing this error with the previous version: picocli 4.6.1?
It is likely that this is caused by a recent change in the 4.6.2 release (https://github.com/remkop/picocli/releases/tag/v4.6.2).

Just tested 4.6.1 and it works as expected.

Thank you for the confirmation.
This looks like a regression introduced by #1320 #1321.
I will add some code to set UTF-8 instead when the String cp65001 is specified.

Does anyone have any idea how to add a unit test for this? :-)

I pushed a fix that should address this issue. Thank you again for raising this!
(Ideas for unit testing this still welcome. 😅 )

I've just had the same problem in Cygwin with cp20127:
Exception in thread "main" java.nio.charset.UnsupportedCharsetException: cp20127

        at java.base/java.nio.charset.Charset.forName(Charset.java:528)
        at picocli.CommandLine.getStderrEncoding(CommandLine.java:14531)
        at picocli.CommandLine.getErr(CommandLine.java:1236)
        at picocli.CommandLine.handleUnhandled(CommandLine.java:2097)
        at picocli.CommandLine.execute(CommandLine.java:2093)
  ...

Downgrading to 4.6.1 fixed the problem.

@Druckles Thank you for raising this!
would you mind raising a separate ticket for this?

I've just had the same problem in Cygwin with cp20127:
Exception in thread "main" java.nio.charset.UnsupportedCharsetException: cp20127

        at java.base/java.nio.charset.Charset.forName(Charset.java:528)
        at picocli.CommandLine.getStderrEncoding(CommandLine.java:14531)
        at picocli.CommandLine.getErr(CommandLine.java:1236)
        at picocli.CommandLine.handleUnhandled(CommandLine.java:2097)
        at picocli.CommandLine.execute(CommandLine.java:2093)
  ...

Downgrading to 4.6.1 fixed the problem.

It is unclear whether this is a Cygwin issue, or what else is going on... (potentially related: https://github.com/rubygems/rubygems/issues/4871, which mentions "Platforms   ruby, x64-mingw32": also cygwin)
Unclear how to remediate this in picocli (if we wanted to): what Java encoding should be used when system property sun.stderr.encoding has value cp20127?
(And for bookkeeping purposes, if further action is required, we need to create a new ticket.)


Resolve Version PR

The simplified version finder still makes sense, but the packages have changed, so the merge is ugly. Need to get through that merge and resubmit: https://github.com/touchlab/KMMBridge/pull/78

Resolved


Add version: pnpm.pnpm.6 version 6.32.3

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.1 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot waivers Add Validation-Executable-Error


Fixes #43200 - TensorBoard histogram breaks on unsupported weight dtypes

43200
Explicit weight.dtype check was added into TensorBoard callback _log_weights.
Weights with unsupported dtypes are skipped from summary histogram and warning is logged.
One thing to note is I wasn't able to finds explicit python list of supported dtypes, so had to hard-code one, which is not ideal. Left a comment in source code.
Similarly there is a list of unsupported dtypes hard-coded into test code.

@googlebot I signed it!

@unsatcore Can you please check @omalleyt12's comments and keep us posted ? Thanks!

@unsatcore  Can you please resolve conflicts? Thanks!

Will take a look on weekend
чт, 5 нояб. 2020 г. в 17:12, gbaned<EMAIL_ADDRESS>
@unsatcore https://github.com/unsatcore Can you please resolve
conflicts? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/43418#issuecomment-722403063,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWN34RR55SUMBFPBG7NDUDSOKXGDANCNFSM4RUHB3MQ
.

--
С уважением,
Пашков Александр

@gbaned, @omalleyt12 let me know if you need any changes

@unsatcore Can you please address Ubuntu Sanity errors? Thanks!

@unsatcore  Can you please check @fchollet's comments and keep us posted ? Thanks!

@unsatcore Any update on this PR? Please. Thanks!

Closing due to lack of activity -- feel free to reopen the PR in the future (with recommended style fixes), this time targeting the new repo, keras-team/keras: https://github.com/keras-team/keras


Discrete fa dynobench

I convert robots into res version, in order to support dynamics with an augmented state.

pre-commit auto fixes I guess, sorry for that. I will enable local pre-fix for dynobench as I do for dynoplan.


[excel] (File storage) Conditional Access policies and Office Scripts

This PR documents the effects of Conditional Access on Office Script. Mainly, that they won't work from unmanaged devices if those policies are in place.

Thanks @lindalu-MSFT!


Language Server Roadmap

Currently, the language server only enables a very small subset of features. Features such as hover, rename, go_to definition, and highlight were disabled before #2121 was recently merged. However, as a result of that PR we now have the infrastructure in place to move ahead with a plan for properly supporting them again. I wanted to open an issue that outlines the order of tasks that we have planned for better LSP support.
As more issues are created I will update this list to reflect them.

[x] Create a pipeline allowing the client to request custom data from the server
[x] #2318
[x] #2319
[x] #2286
[ ] #324
[x] #2259
[ ] #2408
[ ] #1418
[ ] #2258
[ ] #2261
[x] #2260
[ ] #111
[ ] #1864

Closing in favor of using the new LSP + IDEs project view https://github.com/orgs/FuelLabs/projects/21/views/1


SMTP Mail CreateMessage Method overload

Hello,
i want to use the function
procedure CreateMessage(FromName: Text; FromAddress: Text; Recipients: List of [Text]; Subject: Text; Body: Text; HtmlFormatted: Boolean)
but if I call the function with this parameters
lcuSMTPMail.CreateMessage(
  "Sender Name",
  "Sender Mail",
  RecipientMailAddrList,
  MailSubject,
  BodyText,
  true);

The compiler get's an Error and thinks, that I want to use function
procedure CreateMessage(FromName: Text; FromAddress: Text; Recipient: Text; Subject: Text; Body: Text; HtmlFormatted: Boolean)
So the compiler shows me the error "Argument 3: cannot convert from 'List of [Text]' to 'Text' AL(AL0133)
5. Versions:

AL Language:  4.0.206840

Business Central: DE Business Central 15.2 (Platform 15.0.38951.0 + Application 15.2.39040.0)

@kalberes

@esbenk

Any news?

This should be fixed in the latest CU. Pls try to upgrade compiler and platform.

@FSchneiderYav the fix should definitely be part of Wave 1 2020 CU1. If you have access to the insider builds, you can give it a try.

It works. Thank you for your help 👍


Wins/losses against echoes are potentially duplicated

Hello, myself! Just sort of realised this.
If combine_echoes is on, then a set with e.g. Samus game 1 and Dark Samus game 2 will count as 2 wins or 2 losses for Samuses.
No wonder my stats there seem out of whack… I don't think it affects the overall Elo change though. But basically I need to redo the logic and think more.

Although it also might make more sense to consider a 0-2 loss where Character X was only used game 1 to be 0.5 losses, etc.

Actually, that has nothing to do with the number of matches in a set, so if I want to use the same logic as that I just add (1 / len(characters used)) instead of 1. Seems simple enough. Just need to finish caffeinating and I'll do that.


[HM] Crash when replacing face_spellCallB.png

With how much the file replacement code changed since this issue, I feel confident in saying that it have been fixed (and also I could not reproduce it).


Use CMake to detect if std format is available

This PR changes the way how std::format is consumed, instead of setting a specific compiler version in CMake, it uses CheckIncludeFileCXX to detect if format can be imported from system (the compiler is configured already). In case finding #include <format> available, CMake will define HAS_STD_FORMAT and this variable will be used to define the logic of using libfmt or std format.
The advantage here is keeping the feature compiler agnostic, so in case the compiler X supports std format already, it will be used by default always.
Second, the logic is centralized, CMake will check and define the state, so the header c++ has no double check for compiler version, etc.
I also replaced CMAKE_CXX_STANDARD by target_compile_features to indicate about C++20 be needed by the target only (public, so tests will use C++20 too). This replacement gives the option of overriding the definition with newer C++ standard like C++23 via CMake definition.
fixes #541

@cieslarmichal Tests consume the internal formartter header, so HAD_STD_FORMAT need to be passed to tests too. That was the bug, it's fixes now.

I think apple-clang pipeline fails in building main library code, not tests

@cieslarmichal I'll take a look!

Ok thanks! :)

I added gcc v12 additional pipeline

Nice! Thank you, this will give another insight relate to build results.


Ensure that we don't have dupes in branches list

After converting an SVN repo to Git and importing it into GitLab a few of the branches were duped in the branches list. Doing git branch -a showed that my repo didn't have any duped branches so it seemed like the issue was in GitLab somewhere. Adding the uniq check solved the issue for me.
As a note: GitLab v6.9 didn't have any branch dupes. v7.0+ did.

Project migrated to gitlab.


Decorators in traceback?

I noticed that tracebacks can contain a lot of lines like File "<decorator-gen-238>", line 12, in __init__, as demonstrated e.g. in #12425:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/clemens/Projects/mne-python/mne/io/eeglab/eeglab.py", line 332, in read_raw_eeglab
    return RawEEGLAB(
           ^^^^^^^^^^
  File "<decorator-gen-238>", line 12, in __init__
  File "/Users/clemens/Projects/mne-python/mne/io/eeglab/eeglab.py", line 505, in __init__
    self.set_annotations(annot)
  File "<decorator-gen-225>", line 12, in set_annotations
  File "/Users/clemens/Projects/mne-python/mne/io/base.py", line 734, in set_annotations
    new_annotations.crop(
  File "<decorator-gen-38>", line 12, in crop
  File "/Users/clemens/Projects/mne-python/mne/annotations.py", line 636, in crop
    absolute_onset = timedelta(seconds=onset) + offset
                     ^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: cannot convert float NaN to integer

This has cropped up for some time now (probably a long time), but I've only recently noticed it. Since these lines are rather distracting, I was wondering if there was a way to suppress this output.

I've tried a couple of times to figure out a way to remove them and never did find a way

It seems like you shouldn't really do this (for obvious reasons), but since almost all our functions are decorated, it gets a little out of control in the traceback. Since this is mainly the verbose decorator, I was wondering if there was a decorator-less alternative to achieve the same thing. It's probably not worth it, but out of curiosity, we're "just" adding behavior to an existing verbose parameter, right?


Basic mean-field functionality with current TEMPO and PT implementations

New classes TimeDependentSystemWithField, DynamicsWithField, TempoWithField, TensorNetworkTempoWithFieldBackend (TEMPO) and function compute_dynamics_with_field (PT) implementing (PT)-TEMPO with coherent field evolution as described in [Reference pending].
Work to be done in refactoring additions to avoid duplicate code and make maintenance easily. New tests and documentations are also Todo.

The contribution has been discussed and agreed on in the [offline]
Code contributions do its best to follow the zen of python [questions remain over LSP principle].
The automated test are all positive
[x] Added test for changed/added code [Todo].
[x] API code contributions include input checks [Todo].
[x] API code contributions include helpful error messages [Todo].
[x] The documentation has been updated [Todo]

Codecov Report

Merging #42 (278f183) into OQuPy-dev (10af1b1) will decrease coverage by 8.22%.
The diff coverage is 15.65%.

@@              Coverage Diff              @@
##           OQuPy-dev      #42      +/-   ##
=============================================
- Coverage      84.20%   75.98%   -8.23%
=============================================
  Files             23       24       +1
  Lines           2552     2890     +338
=============================================
+ Hits            2149     2196      +47
- Misses           403      694     +291

Impacted Files
Coverage Δ

oqupy/config.py
100.00% <ø> (ø)

oqupy/contractions.py
34.10% <3.31%> (-16.78%)
:arrow_down:

oqupy/tempo/tempo.py
82.04% <14.70%> (-17.96%)
:arrow_down:

oqupy/dynamics.py
78.04% <18.18%> (-21.96%)
:arrow_down:

oqupy/system.py
75.55% <26.66%> (-24.45%)
:arrow_down:

...ackends/tensor_network/tempo_with_field_backend.py
42.85% <42.85%> (ø)

oqupy/__init__.py
100.00% <100.00%> (ø)

oqupy/tempo/backends/backend_factory.py
100.00% <100.00%> (ø)

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 10af1b1...278f183. Read the comment docs.

Documentation, input checks and tests have been added for new Dynamics, System and Tempo classes. Leaving docs/tests for PT implementation for now since contractions.py is a WIP and code may be changed significantly here. Note main other mean-field todos: more thorough testing for a physical system, two-time correlations, example notebook.

I merge this onto a mean-field-dev branch to continue working on it.


Can't regonize argent X class

When using starkli account fetch, it output:
0x029927c8af6bccf3f6fda035981e765a7bdbf18a2dc0d630494f8758aa908e2b is not a known account class hash
It's in fact the argent X account class

Related to #82
Adding a flag for custom class hashes when using starkli account fetch, bypassing the KNOWN_ACCOUNT_CLASSES array would be a great workaround in between updating the array.

Hi, I am facing the same issue. Using ArgentX wallet in starkli fetch and getting the error 0x029927c8af6bccf3f6fda035981e765a7bdbf18a2dc0d630494f8758aa908e2b is not a known account class hash.
Would be helpful if this could be resolved on priority

Same issue with Braavos Wallet. Opened issue here #84

@swetshaw What Starkli version are you using? This class hash should be present on any version since v0.2.5.

Hi! the problem still remains, when I run
'''
starkli account fetch 0x0416575467BBE3E3D1ABC92d175c71e06C7EA1FaB37120983A08b6a2B2D12794 --output ~/.starkli-wallets/deployer/account.json
'''
Got the error:

My starkli version is 0.3.2 (89690d4)

Same issue with version 0.3.5