removed unnecessary Content-Type default. #3256

removed unecessary .contentTypeHeader("") and generates header method for each interaction properly.

@t-takatsuru Actually, the issue lays way upstream, here.
I don't know if things were different in older Chrome versions, but it seems postData.mimeType is now always defined, yet possibly empty.
I've fixed it and will push the fix soon.
Thanks a lot for your effort! Please keep those issue reports and PR coming!


Unable to strace tini's children processes

Hi,
I am trying to profile containers using strace. The command I use is: strace -ff -o /log/trace.log tini -- /entrypoint-wrapper.sh /original-entrypoint.sh (note -ff which follows fork calls). As you can imagine, /entrypoint-wrapper.sh calls /original-entrypoint.sh using an exec call. Both of the scripts are Bash.
Looking at the output of the command, I can see strace attaching only to the tini process, but to none of its children. Moreover, the /log directory contains only a single log file for the tini process. The file has a bunch of wait4 and rt_sigtimedwait, which I imagine to be signal handling calls used by tini.
Running the above command without tini works as expected. How can I strace tini's children?
Thank you!

I wonder if the -g flag would help here?


include last register in i2cdump output

ipctool i2cdump will now also output the last register (to_reg_addr).
closes #113

thanks, exactly what was needed

My pleasure, Sir.  :)   Something similar (for i2cdetect) is fixed here #116


React.PropTypes to prop-types

This PR replaces React.PropTypes references with prop-types.  These changes will remove deprecation warnings and prep for react 16.

amazing! thanks for this :)

published 1.2.7 with your changes.


type_of_data - validate required time selection

time selections - supports daily,weekly, year_and_month, last_30_days,last_7_days, last_day and overall.
Note - Main ticket #585

This is related to cQube v4.1 beta and not implemented in the current version


fix incorrect result of right anti join with nullable

Proposed changes
If the probe column on the left side is not nullable and the build column on the right is nullable, the anti join's result is incorrect.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall


https://actrons.info/

Juuuust under 1MB as my browser shows it.

Lol... 1019001 bytes loaded...
Nicely squeaked under.


[TA] Enable healthcare again, update pii tests, and more

Enable healthcare now that it has been deployed, which means re-recording Fixes: https://github.com/Azure/azure-sdk-for-net/issues/20982
Services fixed bug, so remove our hack in the sdk. Fixes: https://github.com/Azure/azure-sdk-for-net/issues/20991
PII is returning more entities, so I updated our tests

/azp run net - textanalytics - tests


Vagrant bootstrap script should run update-database on both process and views tables

 Kingfisher Vagrant Issues raised during docs work

Think now done


Are there plans to support python after 3.9? e.g. 3.12?

Overview
Running with python 3.12 runs into an issue with pysha.
Description
Error:
pip install pysha3==1.0.2

Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting pysha3==1.0.2
  Using cached pysha3-1.0.2.tar.gz (829 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: pysha3
  Building wheel for pysha3 (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for pysha3 (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [18 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-aarch64-cpython-312
      copying sha3.py -> build/lib.linux-aarch64-cpython-312
      running build_ext
      building '_pysha3' extension
      creating build/temp.linux-aarch64-cpython-312
      creating build/temp.linux-aarch64-cpython-312/Modules
      creating build/temp.linux-aarch64-cpython-312/Modules/_sha3
      gcc -pthread -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -fPIC -DPY_WITH_KECCAK=1 -I/home/umbrel/metaculus/metEnv/include -I/home/umbrel/.pyenv/versions/3.12.4/include/python3.12 -c Modules/_sha3/sha3module.c -o build/temp.linux-aarch64-cpython-312/Modules/_sha3/sha3module.o
      In file included from Modules/_sha3/sha3module.c:20:
      Modules/_sha3/backport.inc:78:10: fatal error: pystrhex.h: No such file or directory
       #include "pystrhex.h"
                ^~~~~~~~~~~~
      compilation terminated.
      error: command '/usr/bin/gcc' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pysha3
Failed to build pysha3
ERROR: Could not build wheels for pysha3, which is required to install pyproject.toml-based projects

Note also that even on python 3.9.19 I got this message (although everything works):
DEPRECATION: pysha3 is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559

BTW, just as feedback on using the api, it's quite cumbersome right now. The docs aren't clear on where an api key is needed for requests and where not. So I went all the way through getting a private key to make api keys to query open markets. I think the onboarding could be simplified a lot.

Same issue for me

Install python 3.9.10 specifically. Solved for me.

Fixed by https://github.com/Polymarket/py-clob-client/pull/85


Implement Shanghai

What was wrong?
Shanghai Hardfork not implemented
How was it fixed?
Implemented EIP-4895, EIP-3651, EIP-3860 and EIP-3855
Cute Animal Picture

Currently in draft because the tests for some EIPs are in Merge+EIP phase rather than Shanghai


[validation] Handle provide withPaths() on demo page which pointed to invalid paths

Before

After

I wonder, if there should be allowed any paths at all, as we only run single file.

is error message needs to be changed? whats better wording for it?

I'd forbid running withPaths() completelly, as no paths except provided file are used.

The issue seems due to too early usage of $rectorConfig->import() on HasRectorRule
https://github.com/rectorphp/getrector-com/blob/91a12c0444d59acdd271a1705309b2468bc93a16/src/Validation/Rules/HasRectorRule.php#L71
so override by path command is not yet executed.

The Assert::filexists on rector-src seems need to be moved to resolving
https://github.com/rectorphp/rector-src/blob/0beeb6fa8beb9fd3833c7de4ba3b3a0cdd408c3b/src/Configuration/ConfigurationFactory.php#L120

It seems verbose:
throw new ShouldNotHappenException($t->getMessage());

On fatal error is better on this case, as it may various kind of different message, user will already clear see what needs to do.

I updated to use its fatal error mesaage into display message https://github.com/rectorphp/getrector-com/pull/2454/commits/4eea5b0c2c8b2d9feb872f7558f5bc0fb29bf1d6

use verbose message pulled from the throwable error seems naturally better 👍

That could lead to people fixing the path to another. But there is only single file path that is being processed. We create it in the background. The withPaths() should never be used in our demo.
E.g. that's why there are no paths in PHPStan demo: https://phpstan.org/try

I will check if that possible, for that, we may need a "filter" instead of "validation", eg: FilterPaths that clean withPaths() from RectorConfigBuilder or paths() from RectorConfig, as in current implementation of HasRectorRule, the $ $rectorConfig->import($configFile);  is called too early

closing for now.


What distinguishes this from symbols-tree-view and its derivatives?

Compared to the (seemingly original) symbols-tree-view package, I'm not sure if I can see any obvious differences in functioonality, besides the fact that the other package might take another package that fixes some issues with it. (I don't eve know if these are necessary anymore)
So why structure-view over the alternatives? Even if it's just the code owners personal opinion.
Don't want to come off entitled, I like both packages and just am obsessed with details when things are forked or accomplish the same goal #

@cucumbur Hi. Not only the main functionality is same between these two packages, you can also find the similar package in other IDEs like Eclipse, WebStorm. The most important thing of these packages is the parsing quality, which means package can recognize the type of language, know its grammar and display the structure meaningfully and beautifully. symbols-tree-view is the original one as well as the abandoned one, you can evaluate its parsing quality by yourself.
The alternatives mostly use ctags to parse source code, which recognize popular languages by .ctags config file, but it's hard to parse the tags or symbols of language completely, and it's also hard to tell the relationship between the tags.
strcuture-view learns from symbols-tree-view, it uses ctags for unsupported languages. At same time, structure-view uses specified language parser to achieve good quality goal, where are the supported languages from.
As you can see, using different parsers to support different languages is a huge project, contributors are the key to this project, I hope people can use it and enhance it! So I designed structure-view for good extensibility, just add AST parser for the language under lib/tag-generators/ folder and this language is supported.

Ah, I see. I happen to be a frontend compiler nerd outside of my professional interests so maybe I can be a contributor soon, once I get familiar with the Atom extension API and the many many parsers out there

@cucumbur Cool~ just do it. Atom extension APIs are all about UI stuffs, so it's unnecessary for parser or parser wrapper.


Add collection subtitle

We need a subtitle style field for collection names to display names across 2 lines.
I updated the database, updated the form and added the field to the api.

Coverage remained the same at 93.75% when pulling a50b9f3f7f370cf13a022046051cd67aea7b816c on add-collection-subtitle into 39009373ae16573bc746208d6d8a3d393f220d72 on master.

:+1:

Coverage remained the same at 93.75% when pulling 70c1eb22513258f60fa656454974e8bdbf7899eb on add-collection-subtitle into 39009373ae16573bc746208d6d8a3d393f220d72 on master.

Coverage increased (+0.03%) to 93.78% when pulling b8d94e927ba6bf36a00d9938a062cb2a505bba06 on add-collection-subtitle into 39009373ae16573bc746208d6d8a3d393f220d72 on master.

Coverage increased (+0.03%) to 93.78% when pulling b8d94e927ba6bf36a00d9938a062cb2a505bba06 on add-collection-subtitle into 39009373ae16573bc746208d6d8a3d393f220d72 on master.

Other than the one hound message, :+1:


Scrolling animations: annoying?

If you click an anchor link on the same page (“#” in URL) and have JavaScript enabled, the website “scrolls” around instead of instantly jumping to the ancor.
This seems to be a trend/hype in modern webdesign, and I hate it very much, as it is irritating to me. Who thinks the same way?
I want to have it disabled.

I honestly don't care whether it scrolls or not.

Animations are fine as long as they're fast enough, and this animation is fast enough. In fact, animations make experience better.
To compare, try playing Unvanquished as an alien with "Instant" wall-walking camera change. You'll get dizzy in seconds.

Animations are fine as long as they're fast enough, and this animation is fast enough.

By extension, the fastest “animation” is an instant change in location, which is of course no animation at all. :P
Haha, but now for reals:

In fact, animations make experience better; they help you know where you are and what's happening.

Not for me, I find this very irritating.
Also, you are forgetting that the animation delays the user interaction, so there is also a clear downside. It is this which ticks me off.
But whatever, I see that our opinions differ here. We are different users who like to use the web differently.
And this is a feature which could be perfectly well implemented by web browsers or at least one of their add-ons. If your browser is lacking such a feature, request it from the browser vendor.
This would also have the benefit that different web users (like you and me) can use the web they way they want to, and not the way the server operator wants to (what you are proposing).

To compare, try playing Unvanquished as an alien with "Instant" wall-walking camera change. You'll get dizzy in seconds.

Calinou, you are comparing a website with a fast-paced first-person shooter.  And the good message: we even support it. On firefox, you can access the feature with:

press alt to get the old menu bar on the top (I think this feature has been removed from the new design as firefox had their "design update" to make place for more important "features" like pocket)
go to View->Page Style->No Style

Then the website even works without any pesky javascript, and there are no scrolling animations reducing your productivity.

This feature also disables all stylesheets whatsoever. That's not exactly what I've asked for.
So this is a hack, but not a solution. :-(

There are addons for finer control.

I find the animations fine, although I'd probably be O.K. with a speed increase.

I'm fine with the # animations, just as long as it doesn't completely take over scrolling (sort of like what Google's "inbox" demo page thing does).

est31: Ideally, websites just work without having to use any browser add-ons …
Heck, there are even browsers without any add-on support.
As I said, the scrolling animation is a non-standard feature. It is harder to disable a non-standard server-side imposed feature afterwards than to manually add a desired feature with add-ons.
There is another reason why I think this is a bad idea: What about browsers or browser add-ons which already implement this kind of scrolling when you click on any # anchor? There is no reason why a browser or browser add-on should not implement such a feature. As I said, such a thing would be a nice-to-have feature on the client side. It just does not go into my head why you insist this must be on the server-side.
But those browsers or browser add-ons are likely to fail on minetest.net because there would be now two “scrolling algorithms” competing against each other. So the safest approach is to leave scrolling entirely up to the browser and not mess around with it on the server-side.
Therefore, anyone who argues that this feature should be kept on minetest.net because they like it personally is missing the point.

That's not how it would work, Wuzzy. When clicking the anchor link it calls some Javascript code which scrolls. The default browser action is disabled.
That is, the javascript script overrides the links to call JS code rather than to scroll.

@rubenwardy That sounds entirely too much like reinventing the wheel there. "Instead of letting the browser scroll, we'll block it and scroll the page ourselves"

Browsers don't scroll, they jump. I've never used a browser which scrolls.

Scrolling animations are a violation of native browser functionality. Don't interfere with browser functionality.

Ummh. I don't have any animation on the site.

Scrolling should stay in place.  It is very common to override functions like scrolling via JavaScript, and there is nothing wrong with it whatsoever. All of you seem to have completely ignored the fact that JavaScript is client side, and runs on the browser. For this reason, it is perfectly fine to do things like this and is in no way a "violation of native browser functionality."
For that matter, literally, any browser has an option somewhere in advanced settings that let you disable JavaScript and therefore disable the far nicer scroller used on minetest.net. And if you don't mind installing a plugin, there are many available that will allow you to disable JavaScript just for specific websites.

I say we write a chrome patch that introduces smooth scrolling as native functionality

@tobyhinloopen: Exactly. This scrolling nonsense must be a client-only feature, the website should not touch scrolling at all. Asking users to disable JS for this website is admitting that it is broken by default.
Firefox has this feature included already, is even enabled by default. Which makes including it on a server-side script even more pointless.
Please don't dictate the client how to behave. At least not like that. And as you can see, there is clear evidence that my opinion that this is a bad feature is not just a fringe opinion. Quite the contrary.

I say we write a chrome patch that introduces smooth scrolling as native functionality

I'm not against such a patch, but in order for this to be a solution, you have to remember the other browsers that exist today. And also remember, that not all of them are open source so you couldn't necessarily write patches for all.
Therefore the JavaScript implementation is best, as it will work for all Browsers, including those on mobile. My theory is that functionality on a website is best implemented so that it will be functional in the same way on all browsers, which sometimes means that what could be native to the browser will be overridden with JavaScript.

Firefox has this feature included already, is even enabled by default. Which makes including it on a server-side script even more pointless.

I used Firefox for 2+ years before switching to Chrome about 8 months ago and never saw this feature. Is this something new?

Asking users to disable JS for this website is admitting that it is broken by default.

Nobody asked you to disable JavaScript, only suggested that it is a possible solution if you are not interested in many of neat things that can be done using JavaScript. If some extra functionality is added using an optional language like JavaScript is added and somebody does not like that functionality, asking them to disable JS is not saying that the extra functionality is broken, it is simply giving them a method to avoid using the extra functionality which they do not like.
Yes, I'm aware that this does not yet directly apply to the Minetest website as JavaScript is required for the menu to work. However, this is theoretically applicable and once I have completed my pull request to retain full functionality without JavaScript, this will be directly applicable.

Also, the problem is, this is a sever-side script...

JavaScript is stored on the server and sent to the client for execution. JavaScript can also be run strictly from the client, without being sent from the server. In the same manner, specific scripts from specific servers can on many browsers be ignored/disabled.

How could this possibly harm usability? Sure, instantly jumping from place to place does mean that you get there quicker, but by the time you get there you have no clue as to whether you jumped up or down without looking at the scrollbar. In other words, you entirely lose your sense of where you are on the page.
Until most browsers support smooth scrolling entirely client side, I will not support the removal of smooth scrolling from the minetest.net website, however, I would be perfectly happy to see smooth scrolling sped up a bit.

Citing Jakob Nielson in https://www.nngroup.com/articles/scrolling-and-scrollbars/:

The main guideline for a scrollbar's look-and-feel is simple: Use your platform's standard scrollbar, which is what users know and expect.

Scrollbars are easy to get right. In fact, the less work you do, the better your scrollbar. Usability is almost always enhanced when you use the built-in scrollbars rather than design your own.

Thus, intentionally deviating from the user expectations is bad.

I'm not against such a patch, but in order for this to be a solution, you have to remember the other browsers that exist today. And also remember, that not all of them are open source so you couldn't necessarily write patches for all.

You are missing the point. At the end of the day, the user decides which browser to use.

How could this possibly harm usability? Sure, instantly jumping from place to place does mean that you get there quicker, but by the time you get there you have no clue as to whether you jumped up or down without looking at the scrollbar. In other words, you entirely lose your sense of where you are on the page.
Until most browsers support smooth scrolling entirely client side, I will not support the removal of smooth scrolling from the minetest.net website, however, I would be perfectly happy to see smooth scrolling sped up a bit.

Because it breaks with user expectations. User expectation is, when you click on an anchor link (i.e. a link inside the same webpage), it behaves however the browser behaves by default in this situation. Which is “jumping”.
And I dislike the tendency of websites trying to “fix” perceived browser problems. Just fix the browsers. Websites also have no say over where the URL bar or the back button is located. So why should they have any control over the scroll bar?

I'm not against such a patch, but in order for this to be a solution, you have to remember the other browsers that exist today. And also remember, that not all of them are open source so you couldn't necessarily write patches for all.

I was joking.

Therefore the JavaScript implementation is best, as it will work for all Browsers, including those on mobile. My theory is that functionality on a website is best implemented so that it will be functional in the same way on all browsers, which sometimes means that what could be native to the browser will be overridden with JavaScript.

Why not introduce an onscreen keyboard as well, in case you don't like the standard keyboard layout? Why let users have a standardised experience when you can override build-in behaviour without any obvious gain? I'd say, disable their keyboard and introduce an onscreen keyboard, just because you feel it is better that way. You can do that in Javascript as well, so it is still not interfering with native functionality, right?

l can't reproduce the smooth scrolling.
l hate smooth scrolling because it delays interaction. l always disable them on android devices.
Smoothly scrolling down/up after clicking a hyperlink should be a browser setting. Otherwise it would be inconsistent, even here on buhtig
there's no smooth hyperlink scrolling.

FYI: If you use firefox and a touchpad, you can enable pixel fine scrolling (linux):
Add export MOZ_USE_XINPUT2=1 to ~/.profile
Open firefox and adjust scrolling speeds: in about:config set mousewheel.min_line_scroll_amount to 50, mouseWheel.durationMinMS to 5 and mouseWheel.durationMaxMS to 40.

Smoothly scrolling down/up after clicking a hyperlink should be a browser setting.

No browser I know of supports this out of the box.

They don't yet support it.

This should be fixed or closed

This no longer happens


Delete ignored key from config.json

Since the exercise implementations are all in the exercises directory
we no longer need to ignore any non-exercise directories in the root
of the track.
See https://github.com/exercism/meta/issues/3 for context.

I've created another PR, #55, which normalizes all of the whitespace in the config.json so
that the change in this PR is minimized and easier to see.
If you merge the other PR first, I'll go ahead and rebase this one onto master.
Sorry about the noise!


Charm fails to compile on BGQ and Cray XE giving an error in TopoManager.C

Original issue: https://charm.cs.illinois.edu/redmine/issues/1405

Machine: Vesta
Latest commit: 22035bcbda2e7987ee429d586243a90b35f4a8b7 (Bug #815: Add OPTS to hybrid API makefile)
Possible suspects: fa88d7f97cc947105af60fdb7e3dd60f1c65b705 (Bug 337) & 7f661eec7733721c6977c329f0976b715ee65c34 (TopoManager Cleanup)
Command and Error with xlc compiler: (./build charm++ pamilrts-bluegeneq --with-production -j16)
"TopoManager.C", line 193.8: 1540-0218 (S) The call does not match any parameter list for "rankToCoordinates".
"BGQTorus.h", line 75.17: 1540-1283 (I) "BGQTorusManager::rankToCoordinates(int, int &, int &, int &, int &)" is not a viable candidate.
"TopoManager.C", line 193.3: 1540-1289 (I) The implicit object parameter of type "BGQTorusManager &" cannot be initialized with an implied argument of type "const BGQTorusManager".
"BGQTorus.h", line 89.17: 1540-1283 (I) "BGQTorusManager::rankToCoordinates(int, int &, int &, int &, int &, int &, int &)" is not a viable candidate.
"TopoManager.C", line 193.8: 1540-0215 (I) The wrong number of arguments has been specified for "BGQTorusManager::rankToCoordinates(int, int &, int &, int &, int &, int &, int &)".
"TopoManager.C", line 228.8: 1540-0218 (S) The call does not match any parameter list for "rankToCoordinates".
"BGQTorus.h", line 75.17: 1540-1283 (I) "BGQTorusManager::rankToCoordinates(int, int &, int &, int &, int &)" is not a viable candidate.
"TopoManager.C", line 228.8: 1540-0215 (I) The wrong number of arguments has been specified for "BGQTorusManager::rankToCoordinates(int, int &, int &, int &, int &)".
"BGQTorus.h", line 89.17: 1540-1283 (I) "BGQTorusManager::rankToCoordinates(int, int &, int &, int &, int &, int &, int &)" is not a viable candidate.
"TopoManager.C", line 228.3: 1540-1289 (I) The implicit object parameter of type "BGQTorusManager &" cannot be initialized with an implied argument of type "const BGQTorusManager".
"TopoManager.C", line 268.15: 1540-0218 (S) The call does not match any parameter list for "coordinatesToRank".
"BGQTorus.h", line 109.16: 1540-1283 (I) "BGQTorusManager::coordinatesToRank(int, int, int, int)" is not a viable candidate.
"TopoManager.C", line 268.10: 1540-1289 (I) The implicit object parameter of type "BGQTorusManager &" cannot be initialized with an implied argument of type "const BGQTorusManager".
"BGQTorus.h", line 138.16: 1540-1283 (I) "BGQTorusManager::coordinatesToRank(int, int, int, int, int, int)" is not a viable candidate.
"TopoManager.C", line 268.15: 1540-0215 (I) The wrong number of arguments has been specified for "BGQTorusManager::coordinatesToRank(int, int, int, int, int, int)".
"TopoManager.C", line 285.15: 1540-0218 (S) The call does not match any parameter list for "coordinatesToRank".
"BGQTorus.h", line 109.16: 1540-1283 (I) "BGQTorusManager::coordinatesToRank(int, int, int, int)" is not a viable candidate.
"TopoManager.C", line 285.15: 1540-0215 (I) The wrong number of arguments has been specified for "BGQTorusManager::coordinatesToRank(int, int, int, int)".
"BGQTorus.h", line 138.16: 1540-1283 (I) "BGQTorusManager::coordinatesToRank(int, int, int, int, int, int)" is not a viable candidate.
"TopoManager.C", line 285.10: 1540-1289 (I) The implicit object parameter of type "BGQTorusManager &" cannot be initialized with an implied argument of type "const BGQTorusManager".
Command and Error with gcc: (./build charm++ pamilrts-bluegeneq gcc --with-production -j16)
Command /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ -Wno-deprecated -I../bin/../include -I/bgsys/drivers/ppcfloor/comm/include -I/bgsys/drivers/ppcfloor/spi/include -I/bgsys/drivers/ppcfloor -I/bgsys/drivers/ppcfloor/spi/include/kernel/cnk -I/soft/libraries/alcf/current/gcc/ZLIB//include -D__CHARMC__=1 -O3 -U_FORTIFY_SOURCE -fno-stack-protector -std=c++0x -c global-elfgot.C -o global-elfgot.o returned error code 1
charmc exiting...
TopoManager.C: In member function 'void TopoManager::rankToCoordinates(int, int&, int&, int&, int&) const':
TopoManager.C:193: error: passing 'const BGQTorusManager' as 'this' argument of 'void BGQTorusManager::rankToCoordinates(int, int&, int&, int&, int&)' discards qualifiers
TopoManager.C: In member function 'void TopoManager::rankToCoordinates(int, int&, int&, int&, int&, int&, int&) const':
TopoManager.C:228: error: passing 'const BGQTorusManager' as 'this' argument of 'void BGQTorusManager::rankToCoordinates(int, int&, int&, int&, int&, int&, int&)' discards qualifiers
TopoManager.C: In member function 'int TopoManager::coordinatesToRank(int, int, int, int) const':
TopoManager.C:268: error: passing 'const BGQTorusManager' as 'this' argument of 'int BGQTorusManager::coordinatesToRank(int, int, int, int)' discards qualifiers
TopoManager.C: In member function 'int TopoManager::coordinatesToRank(int, int, int, int, int, int) const':
TopoManager.C:285: error: passing 'const BGQTorusManager' as 'this' argument of 'int BGQTorusManager::coordinatesToRank(int, int, int, int, int, int)' discards qualifiers
Fatal Error by charmc in directory /gpfs/vesta-home/nbhat/software/changa/changa_reg/charm/pamilrts-bluegeneq-gcc/tmp/topomanager
This happens with cray compilers on bluewaters as well.

Original date: 2017-02-10 15:52:06

~~https://charm.cs.illinois.edu/gerrit/#/c/2233/~~ https://github.com/UIUC-PPL/charm/commit/242927800ad0039cba771e84846a6cb2c777eae1

Original date: 2017-02-10 17:39:39

Related fix for Cray XE: ~~https://charm.cs.illinois.edu/gerrit/#/c/2234/~~ https://github.com/UIUC-PPL/charm/commit/5d9a7e7c9783df1188ca7a9420ea19191e533fc2

Original date: 2017-02-10 21:24:00

Both fixes (BGQ, Cray XT/XE) merged


Running Vite fails with ERR_CHILD_PROCESS_STDIO_MAXBUFFER on very large public directory

Description
I have a very large number of files in my public directory (>16k) - the project is a pre-rendered data visualisation web app with numerous small CSV files to be loaded from a static hosting during usage.
After running vite in my project directory, I get a Bun/Node-related error due to ERR_CHILD_PROCESS_STDIO_MAXBUFFER. A similar error occurs when running vite build.
bun run dev
$ vite
3:13:13 PM [vike][config][Error] An error was thrown:
RangeError: stdout maxBuffer length exceeded
    at Socket.onChildStdout (node:child_process:487:14)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Socket.Readable.push (node:internal/streams/readable:392:5)
    at Pipe.onStreamRead (node:internal/stream_base_commons:189:23) {
  code: 'ERR_CHILD_PROCESS_STDIO_MAXBUFFER',
  cmd: 'git -c core.quotepath=off ls-files --exclude="**/node_modules/**" --exclude="**/*.telefunc.*" --exclude="dist/**" --others --exclude-standard --cached --stage',
  stdout: '.vscode/launch.json\n' +
    'public/data/fact-tables/Transport1B/34432.csv\n' +
[MORE LINES - TRUNCATED]
    'public/data/fact-tables/Transport1B/44211.csv\n' +
    'public/data/fact-tables/Transport1B/44212.cs'... 1038576 more characters,
  stderr: ''
}

It seems that in both Bun and Node, the default maxBuffer for child_process.exec is 1024 * 1024 and vike does not explicitly pass maxBuffer so this will fail for a large number of files and/or long paths?

Have you tried NODE_OPTIONS? Closing but I'll re-open if it turns out to be somewhat related to Vike.

I've done a bit of research on this, and it's possible I missed something, but so far I don't think this is possible to solve with a command line option but rather needs to be handled in the library code (see SO link at the end of this comment). But maybe you have some particular option in mind that you think I should pass through NODE_OPTIONS?
This is specific to the child_process module - see the docs for exec, and specifically the maxBuffer option: https://nodejs.org/api/child_process.html#child_processexeccommand-options-callback
Vike runs git ls-files through child_process, and from what I saw in the source code, doesn't pass a maxBuffer option - which means that if the output from git ls-files is larger than the default 1024 * 1024 bytes, the process will error.
More discussion of the nature of the problem: https://stackoverflow.com/a/63304039

Judging by the error output, the problem arises when running this line, and based on my basic research so far, perhaps it would be enough to pass a maxBuffer: Infinity option in this function

:+1: Makes sense, let's try this.

Fix pre-released as 0.4.204-commit-386d2d8.

Thanks a lot! I tried to test it but I ran into https://github.com/vikejs/vike/issues/1986 (I was on 0.4.199 before and that new issue appears on every version starting from 0.4.200, including the pre-release above). I can test again once https://github.com/vikejs/vike/issues/1986 is resolved

I ran into #1986

Fix released in<EMAIL_ADDRESS>Update your lock file.

I can confirm the issue described here is fixed. Thanks again!


Networktracker fixes for Linux compilers

Trying to compile this with LLVM/Clang 12 with -Werror,-Wall and the symbol stderr couldn't be found because it lives in stdio.h that wasn't #include'd. Also the data structure NetworkTrackeris originally defined as a class, but then in networkTracker.cpp it is referred to as a struct. The course of action for that issue is to remove the struct keyword so it is treated as a class.
This PR fixes these two issues.

@kesheldr great to hear, I have been testing against Clang/LLVM 12.x


Fix git protocol for pip

Use git+https instead of git+git

Confirmed here this fixes the issues
https://github.com/MiczFlor/RPi-Jukebox-RFID/pull/1790#issuecomment-1078259326

This issue currently breaks installation on the master branch. Shouldn't master also get updated?


Bug: DictWrapper should fully implement Mapping interface

Expected Behaviour
DictWrapper and all of its subclasses should fully implement the Mapping interface so that it can be used interchangeably with code that expects the event to be a dictionary. This helps Powertools Middleware play nicely with existing middleware.
Current Behaviour
DictWrapper does not implement the abstract __iter__ and __len__ methods from the Mapping interface. Currently, client code cannot iterate over any subclass of DictWrapper, nor can it use the dictionary built-ins keys, values, or items.
Code snippet
from aws_lambda_powertools.utilities.data_classes.common import DictWrapper

event = DictWrapper({'foo': 'bar'})

[k for k in event]  # raises KeyError: 0
# all of the following raise AttributeError: 'DictWrapper' object has no attribute '...'
event.keys()
event.items()
event.values()

Possible Solution
DictWrapper should subclass either Mapping or Dict, for example:
class DictWrapper(Mapping):
    """Provides a single read only access to a wrapper dict"""

    def __init__(self, data: Dict[str, Any]):
        self._data = data

    def __getitem__(self, key: str) -> Any:
        return self._data[key]

    def __eq__(self, other: Any) -> bool:
        if not isinstance(other, DictWrapper):
            return False

        return self._data == other._data

    def get(self, key: str) -> Optional[Any]:
        return self._data.get(key)

    @property
    def raw_event(self) -> Dict[str, Any]:
        """The original raw event dict"""
        return self._data

    # missing methods
    def __iter__(self) -> Iterator:
        return iter(self._data)

    def __len__(self) -> int:
        return len(self._data)

Steps to Reproduce
see comment above
AWS Lambda Powertools for Python version
latest
AWS Lambda function runtime
3.9
Packaging format used
PyPi
Debugging logs
No logs here. I'm happy to submit the PR to fix this. This should be a non-breaking change.

Hi @Tankanow thank you for the very clear explanation! Would you mind opening a PR with the changes, together with a couple of tests? We will be thrilled to review it and include it in our next release.

@rubenfonseca, happy to do so. I'll get to it this week. 👍🏽


[RFC] Test coverage

Description
This PR describes a solution for measuring test coverage on protocol level.

Thank @dkijania, but I think it is now supposed to land under the https://github.com/o1-labs/rfcs

Oh right! closing then.


fix: Use selected JDK if it is JBR

Installed plugin from this PR and nothing changed:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (g1CollectedHeap.cpp:3100), pid=49127, tid=19459
#  Error: ShouldNotReachHere()

The JBR crash is not really related to using the project version, if such has been set


Have a possibility to label different instances of same service

We need an instance tag that would set by default and which would report the instance id of the running service. In the future, we can read this information from the env vars if a service run on a specific could platform or service.
OpenCensus already has some means of reading the env information from AWS, k8s and Azure, maybe we could pull this in as well. However, this information is not related to the instance id, but more to region, etc.

This functionality can be achieved using the common tag feature.
https://inspectit.github.io/inspectit-ocelot/docs/metrics/common-tags


Deprecate oldMerge usage and add a function overload to make the new …

…merge the new merge API
As suggested by @diogob in #66 I added an overload to the merge function (previously called combine in #66).
When using the old api the function will go through the oldMerge method.
Also, with the TS deprecation message the DX is as good as expected, you'll see a line-through on the merge function when trying to use the old API but every test and type test will keep succeeding.

I'm just merging this onto #66 to review everything in one shot


feat: remove useless code

Description

Issues Resolved

Screenshot

Testing the changes

Check List

[x] All tests pass

[x] yarn test:jest
[x] yarn test:jest_integration
[x] yarn test:ftr

[x] New functionality includes testing.
[x] New functionality has been documented.
[x] Update CHANGELOG.md
[x] Commits are signed per the DCO using --signoff

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

Project coverage is 55.17%. Comparing base (4eb3548) to head (8d6222d).

Additional details and impacted files
@@              Coverage Diff              @@
##           workspace     #258      +/-   ##
=============================================
- Coverage      55.60%   55.17%   -0.43%
=============================================
  Files           2260     1193    -1067
  Lines          42470    24235   -18235
  Branches        7539     4086    -3453
=============================================
- Hits           23616    13372   -10244
+ Misses         17394    10191    -7203
+ Partials        1460      672     -788

Flag
Coverage Δ

Linux_2
55.17% <ø> (ø)

Linux_4
?

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

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


[Bug]: span tags of type int64 may lose precision #3958

Avoid value precision loss
Signed-off-by: Shubham Sawaiker<EMAIL_ADDRESS>Which problem is this PR solving?

Resolves #3958

Short description of the changes

avoid display value precision loss in case of value overflow Number.MAX_VALUE

@yurishkuro Could you please check this draft pull request?  I suppose the types in domain_01.json and ui_01.json are to be different in case of large integer values.

please make sure commits are signed (git commit -s), see CONTRIBUTING.md

Thanks!

Do I need to make more changes? I saw that some tests related to docker are failing.

probably spurious failures. I have the auto-merge enabled, will keep an eye on the CI

ah, I just realized the issue - your PR is opened from the main branch of your fork, this is why the CI is failing. Please create another branch and open a new PR.

replaced by #4034


Flutter 3.10.0-11.0.pre

Looks like some new analyzer assists on master break the tests.

Looks like some new analyzer assists on master break the tests.

Fix is in flight. I'll add you as reviewer on a PR shortly.


Deploy the SAP SuccessFactors Extension Database to SAP HANA Cloud

Tutorials: https://developers.sap.com/tutorials/cap-extend-sfsf-deploy-hc.html
When I reach the step to deploy the hdb via "cds deploy –-to hana" i get the error "Error: no service definition found; there must be at least one service definition for the deployment target"
Note:

using BAS from trial account

When I execute "cds add hana" my package.json shows dependencies.hdb = "^0.19.0" and db.kind = "hana-cloud" (attached)package-json.txtterminal.txt

thanks
package_json.txt
terminal.txt

I did some testing in my own base project and found that @sap/cds CLI node module after version 6.2.2 are broken for the HANA deployment process (some previous versions - e.g. 6.1.3 - had other issues as well). This includes the latest cds version: 6.5.0. When it starts to create the service instance for the HDI container it, somehow, does not find the CAP service definition (.cds file in the srv folder) whilst previous steps of the process (e. g. source code generation of the HDB artifacts) do find it. So, it's clearly a bug of the cds CLI. Please, check the cds version in your terminal with: cds --version.
I recommend you raise an incident ticket to the CAP product team reporting this issue. Meanwhile you can "downgrade" your cds CLI version to 6.2.2 (this one I tested and it seems to work fine). To do it, just change the @sap/cds version in the dependencies of your package.json (which is currently "^6") to "6.2.2". BAS will raise an "unsatisfied dependency" problem in that line, so just click on it and it will show a tiny lightbulb on the left. Click there and select "fix all dependency issues". Then, check your cds version again in the terminal to make sure it's 6.2.2.
However, that version won't update default-env.json as explained in the tutorial. Therefore, to overcome it just run cds watch --profile hybrid whenever you want to access your data from HANA. If you switch back your db.kind to "sql" then you can keep using the usual cds watch command.
As it's not a problem of the tutorial itself I'm closing this issue.
Best Regards,
Alessandro

Understood, thank you
From: Alessandro Biagi @.>
Sent: Thursday, February 2, 2023 1:43 PM
To: sap-tutorials/Tutorials @.>
Cc: Fisher, Todd @.>; Author @.>
Subject: Re: [sap-tutorials/Tutorials] Deploy the SAP SuccessFactors Extension Database to SAP HANA Cloud (Issue #22780)
I did some testing in my own base project and found that @sap/cds CLI node module after version 6.2.2 are broken for the HANA deployment process (some previous versions - e.g. 6.1.3 - had other issues as well). This includes the latest cds version: 6.5.0. When it starts to create the service instance for the HDI container it, somehow, does not find the CAP service definition (.cds file in the srv folder) whilst previous steps of the process (e. g. source code generation of the HDB artifacts) do find it. So, it's clearly a bug of the cds CLI. Please, check the cds version in your terminal with: cds --version.
I recommend you raise an incident ticket to the CAP product team reporting this issue. Meanwhile you can "downgrade" your cds CLI version to 6.2.2 (this one I tested and it seems to work fine). To do it, just change the @sap/cds version in the dependencies of your package.json (which is currently "^6") to "6.2.2". BAS will raise an "unsatisfied dependency" problem in that line, so just click on it and it will show a tiny lightbulb on the left. Click there and select "fix all dependency issues". Then, check your cds version again in the terminal to make sure it's 6.2.2.
However, that version won't update default-env.json as explained in the tutorial. Therefore, to overcome it just run cds watch --profile hybrid whenever you want to access your data from HANA. If you switch back your db.kind to "sql" then you can keep using the usual cds watch command.
As it's not a problem of the tutorial itself I'm closing this issue.
Best Regards,
Alessandro

Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsap-tutorials%2FTutorials%2Fissues%2F22780%23issuecomment-1414198951&data=05|01|todd.fisher%40sap.com|b401c309969f4991046308db054d5169|42f7676cf455423c82f6dc2d99791af7|0|0|638109601906915550|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=EOXDYalJaYSHvFMWhcnxwue58Xefk5hhSmgAA2db2Jg%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMD3GYBH4C2NOEGZQ2PJIXLWVP53PANCNFSM6AAAAAAUMTAFBY&data=05|01|todd.fisher%40sap.com|b401c309969f4991046308db054d5169|42f7676cf455423c82f6dc2d99791af7|0|0|638109601906915550|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Mcgw9pov7qXAGAggzdyKszcAR3NpmQ8h7Tuf%2F32n%2FzI%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


JS: Operators in JavaScript

Operators in JavaScript
Directory
Topics/5.Syntax/2.Operators

Description

Talk about the various operators in JavaScript.
Arithmetic, Assignment, Increment and Decrement, Comparison, Logical, Bitwise.
Explain operators types through examples.

Hints

Check out the W3C tutorial

Hello Mentor, Can I work on this issue.

@paramsiddharth please label this issue I want to work on it.

I also want to contribute on this issue. @paramsiddharth Can you please assigned me this issue?

Can I try this?

I can also want to work it on.Can you please assigned me this issue?

Issue updated. You may proceed with the contribution.

i can also want to work it on. Can you please assigned me this issue?

@paramsiddharth sir why my PR is not merged yet


feat(python): add writer_properties to all operations

Description
I've changed the API to consolidate that how we use writer properties. You now need to instantiate a WriterProperties class and then pass it to the writer, merge, delete, update, optimize operations.
wp = WriterProperties(compression='gzip', compression_level=1)
dt.optimize.z_order(['foo'], writer_properties=wp)

A potential idea I had is to allow users to set the write properties in the DeltaTable class once, so the properties can be grabbed from the tableclass so you don't have to provide them to each method.

@roeap I am not sure if it's worth the effort,  setting the storage options is quite clear since many other libraries share the same setup.


Must clean before changes are applied for another runIde task

I notice I need to run the clean task after some modifications on the plugin.
For example the source code is not up to date when debugging the plugin.
This is painful, especially if the plugin needs some configuration, we have to redo it every time.
The problem appears since I've updated the platform version from 2022.1 to 2022.1.1

Alexandre, thanks for raising this issue!
Do I understand it correctly – if you fire the runIde task, the plugin gets compiled and run; then you change, i.e., the platformVersion, and the plugin isn't recompiled, but it should, right?

@hsz, since I've updated to platform version 2022.1.1 the plugin is not up to date in the IDE, the I have to run gradle :clean before gradle runIde. Also, running compilation task does not solves the problem anymore.

I'm not sure if I reproduce that issue. When invoking the runIde on a clean project, we can see:
19:14:54: Executing 'runIde'...

> Task :setupDependencies
> Task :patchPluginXml
> Task :processResources
> Task :compileKotlin
> Task :compileJava NO-SOURCE
> Task :classes
> Task :instrumentCode
> Task :postInstrumentCode
> Task :inspectClassesForKotlinIC
> Task :jar
> Task :prepareSandbox

> Task :runIde

So sources were compiled and IDE run. Then I update intellij.version to 2022.1.1 from any other version and refresh Gradle (we can see this elephant refresh icon in editor):
19:19:02: Executing 'setupDependencies'...

> Task :setupDependencies

BUILD SUCCESSFUL in 254ms
1 actionable task: 1 executed
19:19:03: Execution finished 'setupDependencies'.

And then runIde again:
19:19:49: Executing 'runIde'...

> Task :setupDependencies
> Task :patchPluginXml
> Task :processResources
> Task :compileKotlin
> Task :compileJava NO-SOURCE
> Task :classes
> Task :instrumentCode
> Task :postInstrumentCode
> Task :inspectClassesForKotlinIC
> Task :jar
> Task :prepareSandbox

> Task :runIde

As you can see, compileKotlin was triggered successfully. Any further run skips such a task due to no changes available, like:
19:22:06: Executing 'runIde'...

> Task :compileKotlin UP-TO-DATE
> Task :compileJava NO-SOURCE
> Task :setupDependencies
> Task :patchPluginXml UP-TO-DATE
> Task :processResources UP-TO-DATE
> Task :classes UP-TO-DATE
> Task :instrumentCode UP-TO-DATE
> Task :postInstrumentCode
> Task :inspectClassesForKotlinIC UP-TO-DATE
> Task :jar UP-TO-DATE
> Task :prepareSandbox UP-TO-DATE

> Task :runIde

Maybe you have skipped the Gradle refresh part?

Mote feedback about the problem, the code changes is updated

Change on line 40, "test" -> "test_run_after_code_change"

First run

The inline variable is not correct

Second run (with clean)

My code is here on branch 221-dev
https://github.com/ng-galien/idea-plpgdebugger/tree/221-dev

I also have this problem,https://github.com/JetBrains/gradle-intellij-plugin/issues/973  and I have been waiting for the author to update and solve it. It seems that the hot update does not work. When you modify the plug-in code, execute runide, but sandbox ide has not changed, that is, your The modification didn't work. Using the clean runide command can do it, but it doesn't make sense to start over every time
I hope the author can solve this problem as soon as possible, the development progress has been stagnant,thank you

@mdddj
I did not check the closed issues before, the problem looks similar for sure

What version of the plugin do you use?
Could you please try the latest 1.6.0-SNAPSHOT release?
How-to: https://github.com/JetBrains/gradle-intellij-plugin#snapshot-version

@hsz thanks, will try out
plugins {
    // Java support
    id("java")
    // Kotlin support
    id("org.jetbrains.kotlin.jvm") version "1.6.20"
    // Gradle IntelliJ Plugin
    id("org.jetbrains.intellij") version "1.5.3"
    // Gradle Changelog Plugin
    id("org.jetbrains.changelog") version "1.3.1"
    // Gradle Qodana Plugin
    id("org.jetbrains.qodana") version "0.1.13"
}

@hsz  1.6.0-SNAPSHOT Thanks, everything works fine with this version

Thanks for the confirmation!
It'll be publicly released next week.

@hsz The problem is solved! Thanks for your hard work on it, especially today.


Cisco OSPF model

Pull Request summary:
Cisco OSPF model
Description of changes:
[Add more in depth analysis of what changed, provide logs, examples of usage]
Checklist:

[x] Make sure to run pre-commit before commiting changes
[x] Make sure all checks have passed
[x] PR description is clear and comprehensive
[x] Mentioned the issue that this PR solves (if applicable)
[x] Make sure you test the changes

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/363


Unable to acces android editor  while in play mode

Tested versions
Reprocible in godot 4.3 beta 1 and most likely the older versions
System information
Sansung s23+ qualcom adreno 740
Issue description
(Putting as bug, because it does not look intended at first glance)
It seems when trying to run  the game in play mode while you can play it alright on android, in the moment when you want to make any changes in games or lets say debug the  errors you had or profiling, it turns out theres no editor window, when usually on pc you have both the editor and game window to adjust your stuff etc..

This makes it  way harder to know  what may  cause the error in your code or  not know where to optimized, because you can't really set things up  before game window pops out, and while clicking the right arrow for returning to editor mode(closing the game window in the process), sometimes in larguer project( 200mb) it can quit the whole app itself.
Steps to reproduce
Open the project
Set play mode
Notices how you can"t  edit anything in editor as there is no window for it.
Minimal reproduction project (MRP)
tests-android.zip

Have you tried remote debugging? if not you can enable it from from Debug -> Deploy with Remote Debug and make changes while the app runs on your phone

Have you tried remote debugging? if not you can enable it from from Debug -> Deploy with Remote Debug and make changes while the app runs on your phone

WDYM? The main issue is that thre´s only one window and that only for the ingame one, which means theres only ingame window  , you can´t profile or anything just by code and if some code has an error you would have to close the window, because it not letting do anything.

just like how you would during the pc play mode so I don't see what's the problem.

Um doesn't seem to work , eanbled it first and then tried, with the same results and then with the reduced one and it kind of the same in my bigger project.

ohh you are developing on android itself? yeah that's an issue. sorry about the misunderstanding

ohh you are developing on android itself? yeah that's an issue. sorry about the misunderstanding

It alright, though that was on the title itself 😅, i can't on pc , becajse mine is dead.

I think it might be fine to close this or stay it open as m4gr3d mentioned tyou can do it on phones on editor/run/window_placement and select side by skde or editor( though this seems more unstable as it can sometimes not show up), though take into account that on big project ( as my experience statement) it can  take minutes to just go from play window to editor as it might be a bug or an android scoped storage issue.

multi-window support already seems to be included when debugging is activated in the GdScript. Perhaps it could also be made configurable for Play Mode
https://godotengine.org/article/android_godot_editor_play_store_beta_release/
 Screenshot

Note: The debugger functionality is only available on large form factor Android devices with multi-window support, due to the need to have the running project [side-by-side]

That what i'm doing on my s23+ and it works well, what does not is the same as editor  option , that sometimes doesn't work, or the editor get frozen due to a bug  prob related to this https://github.com/godotengine/godot/issues/94416#issue-2409969513

Its ACTUALLY easy to solve this problem i had it before you and took me too long to find the way out so i ll just share it with u first click on Editor then Editor setting then under the run group click on the window placement android window should be showing in front of u click on its property and chose side by side ..

In case its didn't work try to activate the developer options on your device (you can watch shot video in yt if u don't know how to activate it)
From the developer options u need to go to the apps group and activate two options the first one is (Force activities to be resizable) and the second one is(enable non-resizable in multi window)
This two developer options with the Editor setting side by side should make the game testing when click play split the screen in two halfs one for the Editor and one for the game
!!!(For me the Editor show only half of it i didn't find solution to make it show fully on the half of the screen)
Last thing this should shows the changes happening in the Editor like moving object in Editor will change its place in the game played too
But i am not sure about the play test sending the informations to the Editor (u can print the any thing and check your self if its work probably or not)

Example for the Editor ahowing only half of it

See when i gave it larger amount of the screen its show more of my Editor

The issue should be mitigated by https://github.com/godotengine/godot/pull/95700 which will be available in the next 4.4 and 4.3 releases.


Switched the OPDS2 feed pagination to be sortkey based

Description
This is to overcome the 10K limitation elasticsearch has on index based pagination.
As a result the "currentPage" is no longer tracked in the OPDS2 feed

Motivation and Context
When trying to inspect and test the feed, the “next” link in the page metadata stopped at about the 200th page or 10,000 publication mark.
If changing the url query parameter ?after=50 to ?after=9950, the query returns the page.  However, following the next link results in an “internal error” message.   Sometimes the query has functioned upto setting ?after=9990 but anything more results in an internal error.
Notion

How Has This Been Tested?
Unit tests have been updated
The local feed was pulled till it's end, which exceeded 54K entries

Checklist

[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

@RishiDiwanTT Can you tell me bit more how this SortKeyPagination works? I don't have much elastic search experience so I'm kind of guessing from the code how it works. Also, will this also work with Opensearch?
PR seems solid, I only have few comments/questions.

Elasticsearch has a limitation where the offset pagination stops at 10K records. This is because deep offsets are very inefficient due to the DB being sharded across machines.
To solve this ES provides a "sort key", which is like a cursor, but not quite. Rather than freezing a result to a cursor, the sort key simply defines the offset of the records based on certain sort criteria, there by allowing sharded indices to be paged efficiently.
https://www.elastic.co/guide/en/elasticsearch/reference/current/paginate-search-results.html


Fastlane metadata for F-Droid should be in root path

Describe the bug
Currently F-Droid can only find the fastlane metadata in the root path. Could you please move it back to root path? Thanks!
To reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

Expected behavior
The fastlane metadata need to be put in root path.
Screenshots
No response
Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional context
No response

Done

Thanks! Since reproducible build is enabled we can't simply use the latest commit. Could you please provide a commit cherry-picking the commit to the 1.12.0 tag or update your apk to it?

Hi, does https://github.com/localsend/localsend/commits/v1.12.0-fdroid work?
Here is the commit hash: deb36ea5461d1217b60ebacf75c47bf7e8e7e9d4

Updated in https://gitlab.com/fdroid/fdroiddata/-/merge_requests/13933. Thanks!

Thank you!


Support migrating arbitrary time ranges of data

Right now the influxd migrate tool only supports migrating entire shards of 1.x data into a 2.x OSS instance.
The PR for the tool is here: https://github.com/influxdata/influxdb/pull/17016
We should support arbitrary time ranges of data, so that a user can decide how much data they want to migrate from 1.x to 2.x.
I have already done the work to add the flags to support this: --from and --to. Those flags will expect the user to provide RFC3339Nano formatted timestamps. Currently those flags will cause an error if used, so that needs to be rectified.
Secondly, the processTSMFile method will need to be implemented. Unlike the processTSMFileFast method the processTSMFile needs to look at the time range of blocks within each TSM file, and compare that to the from and to flag values.
If a block is completely overlapped by the desired time range then it can be completely migrated over. However if a block is only partially covered then it will need to be decoded, chopped up appropriately, and then encoded again before migration. If a block is not overlapped at all it should be excluded from the migration.
It is important that index entries for blocks excluded from the migration are omitted from the 2.x file, and that index entries for partially overlapped blocks are updated appropriately (e.g., updating the start and end times).
Definition of Done

[ ] from and to flags don't return an error;
[ ] processTSMFile implemented;
[ ] Test cases for processTSMFile (hint - consider accepting an interface that can write and seek, and then using buffers in tests to write into).
[ ] ensure from and to flag documentation is clear. Right now it doesn't mention the format the flag values need to be in for example.

@sebito91 might also be relevant to migrate-o-tron phase 1


Schema for questionnaire defintion files

Is there a schema xsd or something similar @jenit for the certificate.xml files? Some of the translators have been editing it and naturally it's ended up in a invalid state and I just discovered a line duplication bug I probably introduced when merging.
It would be good to be able to run schema checks on the files as part of the test suite.

Examples of where correctly formed tags is unclear
<yesno required="required"/>
<yesno required="required" yes="open data sources" />
<yesno required="pilot" yes="anonymised" />

closing unless something specifically actionable to do here? cc @JeniT


Allow user specified additional 'parallel' suffix

Is your feature request related to a problem? Please describe.
I've noticed that when running coverage in parallel mode on containerized CI systems with heavy concurrency it happens sometimes that the generated suffix is not unique (depleted entropy pool would be my guess).
Describe the solution you'd like
A simple solution would be to allow the user to specify an optional additional suffix (either via cli flag or environment variable) since most CI systems already provide a unique job-id (or similar).
Describe alternatives you've considered
More elaborate schemes of automatically generating the suffix (e.g. taking a hash of the environment, incorporating date/time). But those seem either a bit too complicated or could also suffer from the same problem in high concurrency situations.

see: https://github.com/nedbat/coveragepy/pull/802


Request reviewers automatically

This PR makes the action request reviewers for the newly created backport PRs. For this it uses the same reviewers as the PR that is backported.
closes #2

Test in automation lab successful
source PR: https://github.com/zeebe-io/automation-lab/pull/47
created backport PR: https://github.com/zeebe-io/automation-lab/pull/48
request for reviewers: https://github.com/zeebe-io/automation-lab/pull/48#event-4046885226

@pihme Please have a look

I think we should also start implementing tests going forward.

@pihme I agree we should add tests. Should we do that before merging this or do you think it's out of scope? After applying the review hints I now still need to do an additional manual test to see that it still works. 😞

@korthout Let's add the tests for the next change.


Wrong outcome printing for optional labeled args

Example:
let f = (~x=?, ~y as _) => x

f's type is printed like
(~?x: 'a, ~y: 'b) => option<'a>

I think it should be like below, is that right?
(~x: 'a=?, ~y: 'b) => option<'a>

Yes, it seems so. Will submit a fix.

Self reminder: sync up into the editor after the last outcome printer fix.

Submitted a fix.
Interesting note, the compiler hardcodes the optional label in the string…
https://github.com/ocaml/ocaml/blob/4.06/typing/printtyp.ml#L146-L149


[Bug]: Danger Zone does not delete all data related to the Resource

Description
When you create a resource in an environment and delete it before it is deployed (just create and delete right away) it leaves a docker network or a volume data around in the system that did not get deleted.
Minimal Reproduction (if possible, example repository)
I found two cases where some data is left on the host machine when you click the Delete button in the Danger Zone section.

As soon as you create a new Resource on a environment it creates the docker network for that resource (deployment has not yet happen) and in that network is the coolify-proxy added by default.

It may be fixed on delete handler:

disconnect coolify-proxy from the network on this resource.
then delete the network. ( docker network prune would work as well but since is just one network at the moment of deletion target it directly would be more direct )

As soon as you create a new Resource on a environment with the option Based on a Docker Compose it will create a directory here /data/coolify/services/<app-id>/, there will be the docker-compose.yml and any volume if specified there. This time there's no network created before the deployment is done.

Issue here is that if you delete the resource the directory will stay there /data/coolify/services/<app-id>/ (with any volume data previously there ?)
Maybe fixed by rm -rf /data/coolify/services/<app-id>/ ? (or is it too extreme/danger 😅, like the button says)
Exception or Error
No response
Version
v4.0.0-beta.239

Not related to the issue but I think this network that gets created on resource initialization, is the one for connecting to the preferred network (the one with the proxy) ?


Persist theme of the website

Right now if we reload the website reloads with the default config i.e. with the light mode.
We can persist the theme of the website by storing the theme of the page in local storage/cookie so that on the reload or revisits the user sees the website with the persisted theme. On the initial render we can use the system theme mode as the default theme for the website.

@git-anurag-hub
Hi. Looks like I can have a solution for this. Can you please get me started?
Thanks

@git-anurag-hub  @uniqueg
Hi Folks,
I have my PR ready, I want to push my code. How Can I get the access to  push my code to this repository?

@pandyamarut Open a new pr from the branch you are on to the dev & tag me or Alex for the code review!

Resolved by #86


add more tests

Coverage remained the same at 52.362% when pulling 1a6df41e58716639e0b281539c1294013550cf9b on even-more-tests into d7fa235856019add325365d06bc9de7ec6c47229 on master.


[BEAM-6668] Use add experiment methods

Use ExperimentalOptions.addExperiment(...)
instead of getExperiments(), modify, setExperiments() pattern.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

XLang
---
---
---

---
---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

retest this please

beam_PreCommit_Java_Examples_Dataflow

Run Java PreCommit

retest this please

Run Java PreCommit

Run Java_Examples_Dataflow PreCommit

Thanks for the cleanup. Looks like there's some merge conflicts.


Dismissible widget gets stuck when resetting position

Reproduction code
In order to reproduce the bug you have to pull the red box all the way to the bottom/top and hold it there for a while. Then release your finger and the box wont reset its position. However, the hitbox is already reset. It works fine when u dont drag all the way to the end.

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: Dismissible(
            direction: DismissDirection.vertical,
            key: UniqueKey(),
            confirmDismiss: (_) => Future.sync(() => false),
            child: Container(
              color: Colors.red,
              height: 200,
              width: 200,
            ),
          ),
        ),
      ),
    );
  }
}

https://user-images.githubusercontent.com/68549184/127986040-8e377398-8792-43b4-8d1f-cc743d081d39.mp4
Expected results: When you swipe either up or down and hold it, it should reset to its original position.
Actual results: The widget gets stuck, however the hit box itself is back to its original position.

Logs
Flutter doctor
[√] Flutter (Channel stable, 2.2.3, on Microsoft Windows [Version 10.0.18363.1679], locale en-MY)
    • Flutter version 2.2.3 at C:\scr\flutter
    • Framework revision f4abaa0735 (5 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\Samuel\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.58.2)
    • VS Code at C:\Users\Samuel\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.25.0

[√] Connected device (3 available)
    • SM G885F (mobile) • <IP_ADDRESS>:5555 • android-arm64  • Android 10 (API 29)
    • Chrome (web)      • chrome             • web-javascript • Google Chrome 92.0.4515.107
    • Edge (web)        • edge               • web-javascript • Microsoft Edge 92.0.902.62

Hi @Mayb3Nots
Thanks for filing the issue, I can reproduce it on multiple channels and platforms (mobile, web, desktop)

stable
master

❌
❌

Check flutter doctor -v outputs for each channel below

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on Linux, locale en_US.UTF-8)
    • Flutter version 2.2.3 at /home/taha/Code/flutter_stable
    • Framework revision f4abaa0735 (5 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /home/taha/Code/android-sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_SDK_ROOT = /home/taha/Code/android-sdk
    • Java binary at: /home/taha/Code/android-studio-preview/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 12.0.0-3ubuntu1~21.04.1
    • cmake version 3.18.4
    • ninja version 1.10.1
    • pkg-config version 0.29.2

[✓] Android Studio (version 2020.3)
    • Android Studio at /home/taha/Code/android-studio
    • Flutter plugin version 58.0.2
    • Dart plugin version 203.8292
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] Android Studio (version 2020.3)
    • Android Studio at /home/taha/Code/android-studio-preview
    • Flutter plugin version 58.0.2
    • Dart plugin version 203.8292
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.58.2)
    • VS Code at /usr/share/code
    • Flutter extension version 3.24.0

[✓] Connected device (3 available)
    • Redmi K20 Pro (mobile) • def0ad20 • android-arm64  • Android 11 (API 30)
    • Linux (desktop)        • linux    • linux-x64      • Linux
    • Chrome (web)           • chrome   • web-javascript • Google Chrome 92.0.4515.107

• No issues found!

[✓] Flutter (Channel master, 2.5.0-2.0.pre.128, on Pop!_OS 21.04 5.11.0-7620-generic, locale en_US.UTF-8)
    • Flutter version 2.5.0-2.0.pre.128 at /home/taha/Code/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 08320a8dc4 (6 hours ago), 2021-08-03 01:05:02 -0400
    • Engine revision eb1d87d805
    • Dart version 2.14.0 (build 2.14.0-372.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /home/taha/Code/android-sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_SDK_ROOT = /home/taha/Code/android-sdk
    • Java binary at: /home/taha/Code/android-studio-preview/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 12.0.0-3ubuntu1~21.04.1
    • cmake version 3.18.4
    • ninja version 1.10.1
    • pkg-config version 0.29.2

[✓] Android Studio (version 2020.3)
    • Android Studio at /home/taha/Code/android-studio
    • Flutter plugin version 58.0.2
    • Dart plugin version 203.8292
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] Android Studio (version 2020.3)
    • Android Studio at /home/taha/Code/android-studio-preview
    • Flutter plugin version 58.0.2
    • Dart plugin version 203.8292
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.58.2)
    • VS Code at /usr/share/code
    • Flutter extension version 3.24.0

[✓] Connected device (3 available)
    • Redmi K20 Pro (mobile) • def0ad20 • android-arm64  • Android 11 (API 30)
    • Linux (desktop)        • linux    • linux-x64      • Pop!_OS 21.04 5.11.0-7620-generic
    • Chrome (web)           • chrome   • web-javascript • Google Chrome 92.0.4515.107

• No issues found!

✅: No Issue ❌: Issue reproduced
Thank yiu

/cc @Piinks


Bug - TypeError: Client is not a constructor

Hi,
I just ran into an issue with the new version where the following error occurs: TypeError: Client is not a constructor.
Looking at census.client.ts the export class is in fact CensusClient.
I fixed this issue by doing the following:
import census from 'ps2census';
const { CensusClient, Events } = census;

const subscriptions = [{
    // Connery, Miller, Cobalt, Emerald, SolTech
    worlds: ['1', '10', '13', '17', '40'],
    characters: ['all'],
    eventNames: ['MetagameEvent'],
    logicalAndCharactersWithWorlds: true,
}];

// Initalise ps2census event stream client
const client = new CensusClient(serviceID, 'ps2', {
    streamManager: {subscriptions}
});

I forgot to update the examples again. As there are now 2 clients I renamed the Stream client to avoid conflict.

I can submit a PR if you would like to fix the README example 😃


ComboBox Design Time Spacing

Using VS2017 on Windows 7 the ComboBox control spacing at design time is correct but when using a Windows 10 and VS2017 the spacing around the ComboBox at design time is expanded but looks OK when the application runs.  If you make the space equal at design time then at run time it is not correct.
See screenshot of how this looks at design time to get equal spacing at run time, clearly not so easy to position controls at design time due to this issue.

I suspect it is the theme that is being used at design time is different from the one used at runtime, especially if it based on system.

I have tried using various global palettes and ensured that I am using the same at design and run time but it makes no difference.
This was all fine when using a Windows 7 laptop for my development system so it seems to be something about the way that they are rendered in design time on Windows 10.
From: Simon Coghlan<EMAIL_ADDRESS>Sent: 18 July 2019 15:14
To: Wagnerp/Krypton-NET-5.470<EMAIL_ADDRESS>Cc: Andrew Matthews<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Wagnerp/Krypton-NET-5.470] ComboBox Design Time Spacing (#211)
I suspect it is the theme that is being used at design time is different from the one used at runtime, especially if it based on system.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Wagnerp/Krypton-NET-5.470/issues/211?email_source=notifications&email_token=AMFO36NL5NDWTKWWEMNH6M3QAB3BZA5CNFSM4IEXRJIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2ITQZY#issuecomment-512833639, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMFO36PV5PHALT6MJO6K3I3QAB3BZANCNFSM4IEXRJIA.

Left is the app running with the Global Palette set to Sparkle,
Right is the designer with the default blue theme.

It appears that it is the Text Box that is not "Drawing as High"

So from the pictures that you are inferring, and the Theme that I am using, that it is theme problem!

KryptonManager theme to Professional -System gives this:

Which on Zoom gives this:

Workaround:
Place controls into a Table and set the Row's To AutoSize, and then "Shrink the table in the designer down a little" (See right). Now the Runtime has even spaced controls

I get the same result if the palette used in design and run time is the same so not sure why you say that it is the palette that is causing this issue.  Anyway, with the info you have established about the text box I have found another (probably easier) solution and that is to set the minimum height of the text box to 23 and that seems to fix the issue.
From: Simon Coghlan<EMAIL_ADDRESS>Sent: 25 July 2019 13:46
To: Wagnerp/Krypton-NET-5.470<EMAIL_ADDRESS>Cc: Andrew Matthews<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Wagnerp/Krypton-NET-5.470] ComboBox Design Time Spacing (#211)
Left is the app running with the Global Palette set to Sparkle,
Right is the designer with the default blue theme.
[image]https://user-images.githubusercontent.com/2418812/61875162-f141b280-aee1-11e9-9bfc-65b92a0e9847.png
It appears that it is the Text Box that is not "Drawing as High"
[image]https://user-images.githubusercontent.com/2418812/61875392-6c0acd80-aee2-11e9-90a5-3d3a9afc94ee.png
So from the pictures that you are inferring, and the Theme that I am using, that it is theme problem!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Wagnerp/Krypton-NET-5.470/issues/211?email_source=notifications&email_token=AMFO36IGKO2D5VSDPC3HJPTQBGOALA5CNFSM4IEXRJIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2ZLPGI#issuecomment-515028889, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMFO36LH6PFOMEPXDHWTRFTQBGOALANCNFSM4IEXRJIA.


Feature/surrender game

Description

Changed design of website not to use dapp-styles anymore
Added adaptive navigation for mist browser
Implemented ability to play against yourself by only displaying half of the accounts in Mist and the other half in Firefox
Implemented surrender button and reacted on emitted gameEnded events

Related Issue
#42 Implement an end game / surrender button
How Has This Been Tested?

Created several games in msit and firefox and surrendered

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist contributor:

[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[X] All new and existing tests passed.

Checklist reviewer:

[ ] The code has been peer-reviewed by @YourNameHere

Looks good, much better than before. We can discuss more about the design later, for now this is a good step in the right direction.
My only suggestion would be, to hide the "Surrender" button (for both participants) when the game has ended.

@graup Thank you for reviewing. Didn't hiding the surrender button work? I already implemented it in https://github.com/ise-ethereum/on-chain-chess/commit/0ae6cc19a3cea51f576df8c5b24848f92d884efc ...

You are right, it works. I think I pulled before you pushed these changes.
LGTM


Bump to 0.2.38

Codecov Report

Merging #431 (23c9ceb) into main (f32c6ef) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #431   +/-   ##
=======================================
  Coverage   90.03%   90.03%
=======================================
  Files          23       23
  Lines        9101     9101
=======================================
  Hits         8194     8194
  Misses        907      907

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Lib does not identify device locale

When i set my device to e.g. French locale, the lib still yields the following (attached device-info library for comparison):
import ReactNativeI18N from 'react-native-i18n'
import DeviceInfo from 'react-native-device-info'

console.log(DeviceInfo.getDeviceLocale()) // fr-US
console.log(ReactNativeI18N.currentLocale()) // en
console.log(ReactNativeI18N.locale) // empty

"react-native": "0.41.2",
"react-native-i18n": "^1.0.0",

Might be related to #61. Feel free to re-open if it is not the same issue :)


Webpack-Plugin breaks doctype

The webpack plugin breaks the doctype of the documents:
With given input <!DOCTYPE html> it only returns <!DOCTYPE >, which results in quirks-mode in the browser.
In the method serializeDom() instead of calling return this.$.html(); it should be calling return this.$.root().html(); to preserve the doctype.

Workaround until the issue is fixed:
const strictCspLib = require('strict-csp')
strictCspLib.StrictCsp.prototype.serializeDom = function () {
  return this.$.root().html()
}

Just fixed the issue. Thank you very much for reporting!

Thank you for fixing!


[BUG] operationsmanagement@2015-11-01-preview: Solutions_CreateOrUpdate returned HTTP 200 without definition

API Spec link
https://github.com/Azure/azure-rest-api-specs/blob/20e26266be77e6da4321259fb79e51e8281e48b2/specification/operationsmanagement/resource-manager/Microsoft.OperationsManagement/preview/2015-11-01-preview/OperationsManagement.json#L74
API Spec version
2015-11-01-preview
Describe the bug
the Swagger does not defined HTTP 200 response but returned it.
Expected behavior
The Swagger should be consistent with the service.
Actual behavior
The Swagger does not define HTTP 200 response but returned it.
Reproduction Steps
sending creating solution we got a direct HTTP 200 response
Environment
No response

@LinglingTong Please help have a look, thank you.


App crash when deleting a file/store

APP Crashes when call store.delete() function from the lib see logs.
I think the recent update to the temp file system is causing this.
Expected work for the delete fun should be to delete the original file/store.
Looks like the system is trying to find a file that is generate and deleted in the writing process.
 java.io.FileNotFoundException: File does not exist: /data/user/0/au.com.gridstone.pscore.demo/files/devices.json.temp     	at kotlinx.io.files.FileSystemJvmKt$SystemFileSystem$1.delete(FileSystemJvm.kt:61)     	at kotlinx.io.files.FileSystem.delete$default(FileSystem.kt:50)     	at io.github.xxfast.kstore.file.FileCodec.encode(FileCodec.kt:68)     	at io.github.xxfast.kstore.KStore$write$2.invokeSuspend(KStore.kt:56)     	at io.github.xxfast.kstore.KStore$write$2.invoke(Unknown Source:8)     	at io.github.xxfast.kstore.KStore$write$2.invoke(Unknown Source:4)     	at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:42)     	at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:164)     	at kotlinx.coroutines.BuildersKt.withContext(Unknown Source:1)     	at io.github.xxfast.kstore.KStore.write(KStore.kt:55)     	at io.github.xxfast.kstore.KStore.set(KStore.kt:73)     	at au.com.gridstone.pscore.app.android.background.FirebaseCloudMessagingService$onNewToken$1.invokeSuspend(FirebaseCloudMessagingService.kt:65)     	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)     	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101)     	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113)     	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)     	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589)     	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823)     	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720)     	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:707)     	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@72ffb53, Dispatchers.IO]

Hi @SultanArshad Thanks for opening the issue. I think we should check if the file exists before deleting it, or just set mustDelete = false
Feel free to PR a fix in. Otherwise I can fix this over the weekend 👍

Fyi: Had tested the proposed fixed in local project works perfect.

Fixed in 0.9.1-SNAPSHOT. Thanks for your contribution! 🙌


Use an argument parsing library

Would you be opposed to me adding another dependency (https://github.com/tailhook/rust-argparse) and cleaning up the argument handling in main.rs ?

Sounds good. Is it the code you want to clean up, or were you thinking of
changing the arguments? If the latter we will need to make sure plugins
remain compatible
On Fri, Aug 7, 2015 at 1:18 AM, marvelm<EMAIL_ADDRESS>wrote:

Would you be opposed to me adding another dependency (
https://github.com/tailhook/rust-argparse) and cleaning up the argument
handling in github.com/phildawes/racer/blob/25150ce/src/bin/main.rs ?
—
Reply to this email directly or view it on GitHub
https://github.com/phildawes/racer/issues/326.

Sorry for not responding sooner.
I tried to use rust-argparse, but it didn't seem to improve the code quality. I think we should use Docopt (https://github.com/docopt/docopt.rs) instead. It takes a usage string, a struct, and decodes args into the struct. I have an example of this at https://github.com/marvelm/racer/blob/effe804/src/bin/main.rs#L188
I don't think the commands/arguments will change.

I suggest using github.com/kbknapp/clap-rs. It has the best API I've seen so far and is very well maintained by @kbknapp

Thanks for the kind words! I've put together a gist of what main.rs would look like using clap at https://gist.github.com/kbknapp/f71a574d89abbe966d8d
This is truly a one-for-one port, all functionality should be exactly the same, plus all the extras added by clap for free, so to speak (Noted below).
A few things to note about this:

There are some oddities when using the first argument after complete as either a line number or a fully-qualified-name. This one-for-one port says, "The first argument is required (either line number or FQN), and only if a second argument is found (charnum) then a third argument also becomes required (fname)" There is probably a cleaner way to do this, but not without changing the interface in some manner (such as adding flags, or changing subcommand names, etc.)
You get suggestions for free; say a user types racer compete std::io::B (note the missing L in complete) they would see an error saying, "the subcommand 'compete' isn't valid, did you mean 'complete'?"
You get "smart usage strings" or what I sometimes call "context aware" usage strings. For example, if you were to run racer complete 250 20 you'll get an error saying fname wasn't provided but is required, in the suggested usage string, the user will see racer complete <fqn or linenum> [charnum] [fname] even though charnum and fname are technically optional, they aren't in this context so they are included.
I work pretty hard to keep clap efficient, so you get all the above with very, very few allocations.

I'd recommend trying it out, playing with some errors, testing speed / efficiency, etc. If you'd like, I can put in a PR.
No pressure to use clap, by they way! It's totally your project, and you're free to use whatever you choose :) In fact, I'll be the first to say, Docopt does some thing better than clap, and vice versa. Sometimes when all tests that matter to you come out equal, it comes down to personal taste!

:+1:

I took a look at clap and .
The one obvious disadvantage of Docopt is that code using an invalid usage can be compiled with no error. The author has a compiler plugin and macro to check the usage string and generate a config struct at compile time, but it only works on a nightly compiler. This can be mitigated by writing a test to create an instance of Docopt with the usage string and catching parsing errors.

@marvelm thanks! Also, to be fair, it's somewhat possible to do the same with clap. Although it's trivial to test against. With clap if you have a test that builds the valid command line arguments in the same way, and you call App::get_matches() with no panic! you're good. But this still won't fix a user typo, only verifies a working App struct with valid arguments.
While testing I became curious about speed, as I'm assuming racer needs to complete the matches as fast as possible. I've put together some (very) naive tests comparing vanilla racer to those using clap and docopt. The gist can be see here:

I updated the branch in my fork. The timings and allocations are now
$ python -m timeit -n 1 -r 200 -s 'import os' 'os.system("target/release/master complete std::io::")'
1 loops, best of 200: 9.36 msec per loop
$ valgrind target/release/master complete std::io:: > /dev/null
==15544==   total heap usage: 7,205 allocs, 7,205 frees, 1,574,929 bytes allocated

$ python -m timeit -n 1 -r 200 -s 'import os' 'os.system("target/release/clap complete std::io::")'
1 loops, best of 200: 9.42 msec per loop
$ valgrind target/release/clap complete std::io:: > /dev/null
==15565==   total heap usage: 7,364 allocs, 7,364 frees, 1,808,937 bytes allocated

@birkenfeld That prompted me to update to the latest master here (since there have been massive performance improvments) and update clap as well. The gist posted above has been updated, but here's the relevant data:
Vanilla phildawes/master#ebc55c07bb
    Number of Allocs: 1,192
    Bytes Allocated: 486,449
    Python: best of 100: 5.17 msec per loop
    Average time: r 0.01, u 0.00, s 0.007

clap v1.2.5 kbknapp/clap-update#744313c512
    Number of Allocs: 1,345 (+153 over latest vanilla)
    Bytes Allocated: 634,521 (+148,072 over latest vanilla)
    Python: best of 100: 5.07 msec per loop
    Average time: r 0.01, u 0.00, s 0.07

Because clap came out faster using python, that prompted me to up the iterations. When using -r 1000 (1,000 iterations instead of 100) the results are:
vanilla: best of 1000: 4.98 msec per loop
clap:   best of 1000: 5.05 msec per loop

Which makes more sense, but I'm glad to see see clap keeping up :smile:

Yeah, 9.36 vs 9.42 is basically noise. As for docopt, I think it proved to have a nontrivial cost that should be avoided for this use case.
@kbknapp a few observations:

is it possible to print the entire help text when no subcommand is given? It only tells me

error: 'racer' requires a subcommand but none was provided

USAGE:
        racer <SUBCOMMAND>

For more information try --help

which is not so helpful (sure, --help is advertised so no big problem, but it it seems like this should be in the message already).

racer complete --help is not the same as racer --help complete which may be confusing to people.

this help doesn't really tell me much about the two possible syntaxes:

USAGE:
        racer complete [FLAGS] [ARGS] <fqn or linenum>

FLAGS:
    -h, --help       Prints help information
    -V, --version    Prints version information

ARGS:
    fqn or linenum     complete with a fully-qualified-name (e.g. std::io::) or line number
    charnum            The char number
    fname              The function name to match
    substitute_file    An optional substitute file

Especially [ARGS] <fqn or linenum> is strange, since <fqn or linenum> is already in ARGS.

@birkenfeld

is it possible to print the entire help text when no subcommand is given?

Yes. Just change these lines to:
.global_version(true)
.subcommand_required_else_help(true)

OR use the new syntax which is a little prettier (but does the same thing)
.settings( &[AppSettings::GlobalVersion,
             AppSettings::SubcommandRequiredElseHelp])

racer complete --help is not the same as racer --help complete which may be confusing to people.

I agree. But I think after making the change described above to give the full help on lack of a command it's almost a non-issue. Since at the bottom it says For more information about a specific command try 'racer <command> --help'

this help doesn't really tell me much about the two possible syntaxes:

This part I totally agree with, which is what I was eluding to earlier when I said there are probably better ways to structure the CLI in general (as in the interface, not code itself). There are some new-ish features of clap which can help but it's not perfect. It breaks down to 3 options without having a breaking CLI change:

Lie about the arg name which gets displayed to the user. You tell clap the arg name is [<fqn> | <lineno>] which gets displayed to the user in that format in the usage string. This is the easiest method, and least breaking.
Use FQN and LINENO as separate args, but part of an ArgGroup so they're mutually exclusive with each other. You then make the group required, but not the args. This means one of the args must be present, but not both. The hard part is, because they're just free floating positional args, you have to manually determine which one the user used, because to clap they look the same.
Use a custom usage string (clap allows you define whatever usage string you want instead of auto generating it), which entirely solves the problem. The only downside is usage strings on errors aren't dynamic at that point. Meaning, typically when you make an error, clap will take whatever args you were trying to use, and stick them in the usage string displayed at error regardless if they were actually required or not (unless there is some conflict, which it determines as well). This is nice if you have a ton of args you're passing in, and you make an error with one of them, you see how the command should have actually been called giving all the options you were trying to use, and not just a static usage string.

[ARGS]  is strange, since  is already in ARGS.

I see what you mean. What it's trying to convey though is that [ARGS] are optional positional free floating args. But <fqn or lineno> is required. Hence the [] and <> but you're right, that could be confusing. Although I think the user would figure it out quite quickly.
Sorry for the long reply, I can be long winded! :smile: And those are all great points you brought up, I can update the branch I was using for testing to demo some of these options/changes if you like! :smile:

@birkenfeld I've made some of those changes so you can see what it looks like. See clap-update#6b4ff42f to test. This is using the second method described above.

@birkenfeld based off some of the changes in clap I updated the gist and branch in my fork (based off the latest master here). Results are somewhat strange as the clap version comes out faster than vanilla and shows way fewer allocations...I'm not really sure why that would be.
For the interested the branch update and gist

Hm, I could not reproduce this exactly; for me both master and clap-update show the same number of allocs as your clap-update measurement (13 allocs, 67k bytes). Timing goes from 2.56 to 2.63 ms with clap, which is fine.
At this point, I would recommend opening a pull request!

May have been a typo or mis-test on my part...because I'm getting the same now :confounded: Oh well! Gist is updated :smile:

v1.5.3 has some pretty major improvements both in terms of performance and features, so I'll try to update the gist shortly...

I think you can close this issue, now :+1:


stm32h7 ethernet dma pointer width

Fields TDELSA, TDESLA, TDT, RDT are 32-bit pointers, but are defined in the SVD and RM as [31:2] with 30 bit width. The two LSBs of the register are described as ready-only.
The equivalent registers in F4/F7 ethernet dma definitions have full 32-bit width. Should we change these fields to be the same? I'd say 32-bit width is closer to expected behaviour, but it is technically different to the RM.
Current workaround is just to write/read from the whole register
unsafe {
  eth_dma.dmactx_dlar.write(|w| {
    w.bits(&buf as *const _ as u32)
  });
}

In both cases you would still have to manually guarantee alignment. That doesn't change.
The alternative would be:
let addr = &buf as *const _ as u32;
assert_eq!(addr & 0x3, 0);
eth_dma.dmactx_dlar.write(|w| w.dlar().bits(addr >> 2));

No unsafe but instead shifting gymnastics which makes it harder because they can be forgotten.
Personally I'd rather not have to see the shifting.

This is the same issue as #195 raised about BTABLE, which also has alignment requirements which ST (well, Synopsys, who do both the USB and the Ethernet..) address by making a short and shifted field in the register.
On the one hand I agree that the shifting is annoying and prone to mistakes; on the other hand it seems like it would lead to surprising disagreements with the reference manual if we made the field wider ourselves. I sort of like just writing the address to the whole register instead of to the field (though you can move the unsafe to inside the closure which is neater I think, just use .write(|w| unsafe {).
Maybe there's an argument to be made that writing a memory address (which you can get safely) to a hardware register which is then going to start reading/writing that address should be unsafe anyway.

I think I agree (with the .write(|w| unsafe { w.bits(addr) }) being idiomatic in terms of unsafety and register interpretation).

Thanks both for the discussion - this is really useful for my understanding of what is/isn't idiomatic. I'm happy that the unsafe write to the whole register is acceptable here, so closing issue.


Variable Explorer context menu

Also added set directory commands as in RS per users request and re-worded message when R is not found.

I think I'd leave alone for now plumbing command target up to the pane, it will be bigger change I think,


(Low) Broaden knowledge about end2end tests

(LOW) End-to-end tests - do research and try to implement. Link to the explanation of end2end tests. https://katalon.com/resources-center/blog/end-to-end-e2e-testing

This is the next and important step of our project so please get used to end2end testing. In my job we are using them a lot. We test if the end user sees what we want him to see and not just single particular function returning sth that we want. Thanks to end2end tests we are sure that side works


[vSphere] Update machine-controller version to include datastore cluster support

This issue is to bump machine-controller version used in kubeone to at least v1.10.2 in order to have datastore cluster support for vSphere provider.

/reopen
Will keep this issue open until we don't cherry-pick the PR to the release/v0.11 branch.