console.log output is buffered during a run through the node debugger

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When running a test via the node debugger (node debug ./node_modules/.bin/jest -i), when we encounter a breakpoint and attempt to run a console.log in the REPL, the output gets buffered until the test runs have completed.
While this behavior is desired for running tests normally, I don't think it's particularly useful with the runInBand CLI option, specifically when run under a debugger.
The reason console.log appears to be useful is that by default the node debugger will truncate lines to 80 characters, and a console.log statement will print the whole thing out.
node debug test.js
< Debugger listening on [::]:5858
connecting to <IP_ADDRESS>:5858 ... ok
break in test.js:2
  1
> 2 });
repl
Press Ctrl + C to leave debug repl
> var x = 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'
> x
'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa... (length: 103)'
> console.log(x);
< aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Can be reproduced by

running any test via the node debugger (node debug ./node_modules/.bin/jest -i <testname>)
setting a breakpoint in a test
Typing repl to drop into the interactive REPL
Running console.log('test')
Ctrl+C to exit the repl
cont to finish execution

What is the expected behavior?
Output the console statement immediately rather than buffer it when being debugged.
Running:

Jest 17.0.3
Node 6.7.0
NPM 3.10.7

@maher-stripe Does it happen in Jest 19?

No it does not! \o/ That's exciting.

This seems to be an issue again in Jest 23. Very confusing.


tensorflow resize_image_with_crop_or_pad for whole batch

Currently there exists tensorflow.image.resize_image_with_crop_or_pad() that works well, but for me it would be very beneficial to have also something that would be able to perform crop on whole batch of images or even conv2d or conv2d_transpose outputs.
In other words it should work on Tensor of shape [batch, height, width, channels].
So far I have found this mentioned here http://stackoverflow.com/questions/33944683/tensorflow-map-operation-for-tensor
And for now I'd probably go with the tf.while_loop, but general built in function in tensorflow would be helpful.

If you have a batch of images in a [batch, height, width, channels], can't you just use tf.slice() to crop the whole batch?

Closing for now, since slice does seem to be a good solution.  @ziky90: Please comment if slice doesn't fit your use case.

@mrry How would you use slice to accomplish this?

@cancan101 Assuming the crop region should be at the same location in each image, you would just take images[:, y_start:y_end, x_start:x_end, :] where x_start, x_end, y_start, and y_end define the corners of the crop region.

okay, but then need to copy over logic like:
  width_diff = target_width - width
  offset_crop_width = max_(-width_diff // 2, 0)
  offset_pad_width = max_(width_diff // 2, 0)

  height_diff = target_height - height
  offset_crop_height = max_(-height_diff // 2, 0)
  offset_pad_height = max_(height_diff // 2, 0)
...

to get those values.

Sure, but you don't need to use a tf.while_loop(), which was suggested in the original issue.
I don't feel strongly either way adding such a function in image_ops.py... feel free to open a new issue with the proposed interface if you'd like!


Active Directory with seamless Windows EC2 join (from ASG)

Please include the following in your PR:
Please also note that these are not hard requirements, but merely serve to define
what maintainers are looking for in PR's.  Including these will more likely lead
to your PR being reviewed and accepted.

[x] Update the changelog
[x] Make sure that modules and files are documented. This can be done inside the module and files.
[x] Make sure that new modules directories contain a basic README.md file.
[ ] Make sure that the module is added to tests/main.tf
[ ] Make sure that the linting passes on CI.
[x] Make sure that there is an up to date example for your code:
- For new modules this would entail example code for how to use the module or some explanation in the module readme.
- For new examples please provide a README explaining how to run the example. It's also ideal to provide a basic makefile to use the example as well.
[ ] Make sure that there is a manual CI trigger that can test the deployment.

@ketzacoatl Proof that it actually works is documented on the README (with snapshots): https://github.com/fpco/terraform-aws-foundation/blob/6fd06a686c6f17f27d3374e3207523f499ce14fe/examples/ad-asg/README.md


feat - Add class prop to DateInput wrapper

Fixes #48
A remake of #51 with better Typescript support
Adds an explicit class string prop which gets added to the DateInput wrapper.

Thanks!


Replace German Umlaute in slug

German Umlaute in the automatically generated slug should be replaced by the following pattern:
ü = ue
Ü = Ue
ä = ae
Ä = Ae
ö = oe
Ö = Oe
ß = ss

We might consider using this library.


Debug tests are not deleting the binary and the C file after usage

Description of the issue: After running make test-frontend either test_executable_generation or test_executable_generation_without_precompiled_function from test_debug.py are leaving two ghost files undeleted: f.out and main.c

Expected behavior: There shouldn't be any new files in the Catalyst root folder after running  make test-frontend.

Actual behavior: (What actually happens) The two mentioned files are there in the Catalyst root folder.

Reproduces how often: (What percentage of the time does it reproduce?) Always.

Catalyst commit: https://github.com/PennyLaneAI/catalyst/commit/b95d8622b133071d02a08783ccba4f736d4d43f9

Ahh, so that's what those two are...

Closing as fixed


[New Feature] Add SwapArrayControl and MoveArrayControl actions (Updated)

Since the original PR for SwapArrayControl and MoveArrayControl has remained open and not updated even with the many comments made on it, I thought I'd take a stab at getting this across the line. I tried to interpret what was needed, but I probably made some mistakes.

Updated branch to cover requested changes

Thanks for the update. The only thing still missing are the negative index checks for the swap operation (you only added them for move). Once that is done I will happily merge the PR.

ah, github had hidden some of the conversation and I didn't expand them. Resolved the swap-control negative index check and improved the error message that was there for out of bounds index check to reference the from and to indexes so the user knows which param was incorrect.


fix: allow values to be 0

:tada: This PR is included in version 1.10.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Consider using signed commits

See: https://blog.github.com/2016-04-05-gpg-signature-verification/
It's pretty easy to integrate seamlessly into your workflow and provides at least some level of added security.

Thanks! I've set mine up and will be pushing only signed commits from now on.


Hotfix/373 higher priority osx installer tweaks

Summary

still a WIP
fixes #373
fixes #370 - the "Stopped" notification during initial application load - specifically, https://github.com/learningequality/installers/issues/370#issuecomment-193492995

TODO

PR is considered WIP (work in progress), until all TODOs are marked.

[x] Launch the KA Lite app as soon as the installer finishes.
[x] Auto-start the server whenever the KA Lite app is loaded.
[x] Have the default behavior be to auto-launch the KA Lite app at boot
[ ] At the end of the beautiful installer GUI wizard, tell the user what to do next.
[ ] Added/updated the documentation.

Reviewer guidance

Use the latest build of the OS X Installer (.pkg) at Bamboo to test this PR at http://dungeon.learningequality.org/browse/KL-MT16 -- build must be > 77.

Hi @radina - I'm done with functionalities on this PR and it can now be tested.  Sadly the dungeon server is still down and hopefully @aronasorman can help fix it so you can download a .pkg to test.
I will follow working on the documentation after our team Alpha tests here in the office. :smile_cat:

I've finally managed to customize the Summary step of the OS X GUI installer.  Here's a screenshot:

Please test the build 85 at http://dungeon.learningequality.org/browse/KL-MT16-85 for the latest updates.

This PR now also fixes #369 by:

showing a "NOTE: Make sure that the KA Lite application is not loaded before continuing." at the Introduction section;
failing the install process if we find a loaded "KA Lite" application.

/cc: @radinamatic

Thanks @cpauya, I'll download the latest build as soon this is merged to try it out! :+1:

Hi @radinamatic - build 87 on Bamboo should include the fix for #369.
Although the .pkg is still pointed to our repo's hotfix branch, once this is merged, I'll point it back to this repo's develop branch before building a .pkg that you can test.
Can I ask who should check and merge this?  Or should I still be the one to do it? :smile_cat:
/cc: @aronasorman


Allow Native Client connections on premium SKU and add error handling…

… block for JSON decode

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.


Deployment modal - update button disabled bugfix

The deployment dialog now shows Registries and the update button is active.
However, on the preview instance at the CloudFlare there are two issues:

The Destination is "spinning"

On clicking "force update" I get

Apart from the issues due to CloudFlare the PR LGTM. Merging.


Acceptance of ' in identifier name

In  txs-compiler/src/TorXakis/Parser/Common.hs is written
identLetter     = alphaNum <|> oneOf "_'"

However the character ' should not be accepted by TorXakis.
One reason is that Xml also doesn't accept ' and we are using the constructor and field names in the toXml conversion.

See Xml
' (#x27) and explicitly NOT allowed in names.


Implement multi-year (2010, 2020) scraping for the censusdp1tract scraper

Currently the US Census DP1 scrape is hard-coded to obtain the 2010 data, and label the output file as such, and then this data is packaged for Zenodo using an annual datapackager, which reads the year from the filename.
However, with the release of the 2020 DP1 data, we'll need to update the scraper to get both 2010 and 2020 data, and automagically label the resulting downloaded files accordingly, for consumption by the zenodo storage module.

2020 DP data supposedly not slated for release until May 2023: https://www2.census.gov/programs-surveys/decennial/2020/program-management/glance_data_products.pdf


v1.9 backports 2022-02-14

#18777 -- Fix bug where Cilium drops traffic from remote nodes in etcd mode, despite policy that allows the traffic (@joestringer)

Once this PR is merged, you can update the PR labels via:
$ for pr in 18777; do contrib/backporting/set-labels.py $pr done 1.9; done

or with
$ make add-label branch=v1.9 issues=18777

/test-backport-1.9


[WIP] kwm: handle display status changes better

Just pushing this here so I can get feedback more easily.

Looks good, great work!


Incrementally improve the ways to get to the (wiki) documentation

The idea would be that on every page, the page title box includes a "?" (like GOOSE) that takes the user to the wiki page (as defined by the current help link).
This should be rolled out to production ASAP (maybe with the fix to #198, if viable).

Tagging @cmungall and @monicacecilia

Actually a fair amount of farfing around to get everything pointed more-or-less the same place--I had forgotten how many customs one-offs there were in there.


youtube-dl: 2019.03.01 -> 2019.03.18

Motivation for this change
Good to stay up-to-date with this one.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Change backported in

19.03 https://github.com/NixOS/nixpkgs/commit/7228ac327d6e5cd77f1e64ad331979d11d6f690b
18.09 https://github.com/NixOS/nixpkgs/compare/918bc442802b78e41998b327348c6a7d3b1c9038...2d656a9729739e8ca5486058a76669d0ea4442df (wasn't done recently)


fix: bootstrap

What this PR does / why we need it

JIRA ID: [XX-XX]

Notes for your reviewers

:tada: This PR is included in version 1.9.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


⚠ Bofrost.lu has degraded performance

In bade099, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1616 ms

Resolved: Bofrost.lu performance has improved in aee6004 after 13 minutes.


Regenerate 4096-bit RSA keys

The command service sshd keygen does not take into consideration the option -b, which specifies the number of bits in the key to create.
For RSA, 2048-bit keys are generated by default on FreeBSD 12.2 and 13.0 (OpenSSH 7.9), and 3072-bit on FreeBSD 14.0 (OpenSSH 8.7).
Fix it by using the full command, just like the other guides.

Note to self: FreeBSD 12.3-RELEASE & 13.1-RELEASE, when released should generate a 3072-bit by default, hence making this PR less relevant.


add agreement to tenant code

Purpose of the pull request
#783

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

currently, it is submitted to the main branch, and it should be submitted to the dev branch


Fix new Clippy warnings as of Rust 1.49

[ ] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Updated CHANGELOG.md

Codecov Report

Merging #766 (a6edf22) into master (a117871) will decrease coverage by 0.0%.
The diff coverage is 83.3%.

@@           Coverage Diff            @@
##           master    #766     +/-   ##
========================================
- Coverage    50.6%   50.6%   -0.1%
========================================
  Files         197     197
  Lines       13570   13567      -3
  Branches     3249    3249
========================================
- Hits         6872    6869      -3
  Misses       6336    6336
  Partials      362     362

Impacted Files
Coverage Δ

testgen/src/commit.rs
83.4% <0.0%> (ø)

tendermint/src/vote/sign_vote.rs
87.0% <100.0%> (-0.3%)
:arrow_down:

rpc/src/result.rs
27.6% <0.0%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #766 (a6edf22) into master (a117871) will decrease coverage by 0.0%.
The diff coverage is 83.3%.

@@           Coverage Diff            @@
##           master    #766     +/-   ##
========================================
- Coverage    50.6%   50.6%   -0.1%
========================================
  Files         197     197
  Lines       13570   13567      -3
  Branches     3249    3249
========================================
- Hits         6872    6869      -3
  Misses       6336    6336
  Partials      362     362

Impacted Files
Coverage Δ

testgen/src/commit.rs
83.4% <0.0%> (ø)

tendermint/src/vote/sign_vote.rs
87.0% <100.0%> (-0.3%)
:arrow_down:

rpc/src/result.rs
27.6% <0.0%> (ø)

Continue to review full report at Codecov.

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


Header Function does not catch response exceptions

On this line:
https://github.com/guzzle/guzzle/blob/c2c9d72f8ba225b585351bbe4922255837ddbd80/src/Handler/CurlFactory.php#L584
Exceptions are not caught, this then leads to a catastrophic error and intermittent failures of Guzzle Pools. When using this with unknown endpoints that may generate non-conforming status codes the PSR7 Response exceptions are thrown which causes cURL and therefore Guzzle to act in odd ways.
The solution is straightforward - catch the exception and return -1 - as has been done for the header callback just below this method call.
Related Pull Request from 6.5 that is still a relevant fix for 7.x: https://github.com/guzzle/guzzle/pull/2591
This is a blocking bug for Guzzle pools for anyone doing crawling and is an incredibly simple fix. Can we get this merged so we don’t need to continue patching Guzzle?

+1, this is a debilitating bug. When an API sends a HTTP response with untypical HTTP status code, the whole thing just crashes.

This was fixed in #2591 and will be released in 7.2.0


R1 Feedback: responsiveness and multiplayer features

In games like Artemis Bridge Simulator and Space Team multiplayer interactions create a base level of responsiveness by chaining 3-5 work tasks.
If interaction loops have feedback between a similar 3-5 tasks 1 second could be closer an upper limit of interactivity. 50-350ms is typical for real-time multiplayer games, and competitive fps's predict motion and interactions over similar periods.
In a game with a determined rate of play, commands should be queued and rate-limited in order to simplify interactions. Commands should be promptly acknowledged even if the simulation does not update to reflect them for 100's of ms.

It's so great to know some gaming industry professionals.
Certainly the UI should respond instantly if someone flips a switch or drags a slider to acknowledge the input. In writing R1 I had in mind the power level increasing after actuating a control rod. 50 ms would be excellent for response but I'm just totally unaware of what's possible given the slow Python stack I'm currently envisioning so I went with a easy bar. Sounds like shooting for 350ms would be a more appropriate goal.
This thing won't be much different from a game. It is a game, really.

With SVG.js examples I've been playing with you get near instantaneous feedback. I think we'll be good once we hook the backend (which is still in its pre-infancy)


Adds support to "mute" attribute to be set by default.

Today there is no way to mute videos by default.
To do that a workaround is needed to set the volume to "0" on the "ready" event. It causes some unwanted noises if the browser performance is not good.
If this pull request is accepted, developers can set the video to be muted by default.
Besides, I changed the volume icon to mute/unmute the video and added a volume range on the user interface to control the volume level.
This feature will be very useful to me in particular and hope this can help others too.

I signed it!


Setting a JRUBY_HOME environment variable prevents plugin from working.

During usage of this plugin we discovered that if an environment has a set JRUBY_HOME value (the version might matter, not sure), the plugin outputs an error message similar to the following:
`require': no such file to load -- rubygems (LoadError)
I would be willing to propose a solution if you believe, that the issue is worth solving in this plugin.  Let me know.
Thanks,
Dan P. Smith

A PR would be welcome, I've not run into this, but I think it would be possible to force the JRUBY_HOME to point to the jar or to unset the value.
I guess th ebest place to do this would be in the executeSassScript(final String sassScript) method.

Removing the environmental variable has three approaches from what I have read and tried today:

Use something like the code on this stack overflow post (not the accepted answer, but the hacky version below it): http://stackoverflow.com/questions/318239/how-do-i-set-environment-variables-from-java
Use JRuby directly instead of through the ScriptEngineManager abstraction so that the environmental variables and/or JRUBY_HOME can be set directly.
Use a ProcessBuilder and a forked thread to create a new environment, and start the execution of the JRuby script in that.  (This is how surefire sets its environmental properties)

My preference would be for #2.  I already implemented #1 but it is not pretty.  If I put together an implementation of the second approach, would you be willing to incorporate it into the project?  I can also attempt #3, but it is quite a bit more work to do the compilation in another thread (especially when it would be to solve this issue).

Not sure if using System.setProperty("JRUBY_HOME", "......"); wouldn't be enough? (or jruby.home)
As long as we keep using the resources in the plugin jar without specifying the path ourselves and there isn't a huge performance hit I'm OK with 2.
I don't see any advantage in 3; it would probably cause problems using the watch goal.

I tried using System.clearProperty() first.  Those methods appear to have no effect because the property is read from System.getenv which is not modifiable without that hack.
I will see if I can get a version of approach two working.  Thank you.

I put together the pull request.  Feel free to let me know if you want me to make any changes to it.
Thanks again.


What is "labelOrientation" in annotation's LinePath.js file?

LinePath.js has a parameter labelOrientation = 'horizontal' that doesn't seem to do anything. Can we remove it?
EDIT: Also "labelVerticalAlign", and "labelHorizontalAlign" are not used.

Yup, these are TODOs for me.

TODO's to remove or TODO's to do something with them? I can remove them and submit a PR if you'd like.


Update opennic-fvz-rec- servers in dnscrypt-resolvers.csv

Hi,
can you please update my listed servers in dnscrypt-resolvers.csv?
You can find an exported list of my servers here:
https://scr.meo.ws/paste/2015-08-02-05-57-10-6ix09oX9.txt
I had a couple of issues with all my DNSCrypt installations which forced me to rebuild my entire configuration and with that all the keys and certs.
Thanks in advance!
Regards,
Fusl

Hi,
Looks like none of them work any more :(
Trying any of them results in
[ERROR] Unable to retrieve server certificates

Even with the ones that used to work.
Is the provider name correct?
For example, this should return the TXT record with the certificates but it doesn't:
$ drill -p 443 txt 2.fvz-rec-at-vie-01.dnscrypt-cert.meo.ws @<IP_ADDRESS>
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 38879

Hi,
you were right, the provider name was incorrect in the exporter template, sorry for that.
Here is the updated list: https://scr.meo.ws/paste/2015-08-02-13-23-19-Fyr5mhlJ.txt
Thanks!
Regards,
Fusl

Done!
Everything looks great now!
Thanks!

+ fvz-rec-at-vie-01 - OK
+ fvz-rec-au-nsw-01 - OK
+ fvz-rec-au-sa-01 - OK
+ fvz-rec-au-vic-01 - OK
+ fvz-rec-au-wa-01 - OK
+ fvz-rec-be-vwv-01 - OK
+ fvz-rec-ca-on-01 - OK
+ fvz-rec-ch-zu-01 - OK
+ fvz-rec-de-fra-01 - OK
+ fvz-rec-de-fra-02 - OK
+ fvz-rec-de-sn-01 - OK
+ fvz-rec-fr-rbx-01 - OK
+ fvz-rec-fr-sxb-01 - OK
+ fvz-rec-gb-eng-01 - OK
+ fvz-rec-hk-nt-01 - OK
+ fvz-rec-hu-bu-01 - OK
+ fvz-rec-ie-du-01 - OK
+ fvz-rec-im-dgl-01 - OK
+ fvz-rec-is-hf-01 - OK
+ fvz-rec-jp-tk-01 - OK
+ fvz-rec-li-ba-01 - OK
- fvz-rec-lv-rix-01 - Failed
+ fvz-rec-nl-fl-01 - OK
+ fvz-rec-nl-nh-01 - OK
+ fvz-rec-nz-auk-01 - OK
+ fvz-rec-ru-mow-01 - OK
+ fvz-rec-se-ab-01 - OK
+ fvz-rec-sg-ea-01 - OK
+ fvz-rec-us-ca-01 - OK
+ fvz-rec-us-ca-02 - OK
+ fvz-rec-us-fl-01 - OK
+ fvz-rec-us-ga-01 - OK
+ fvz-rec-us-nj-01 - OK
+ fvz-rec-us-tx-01 - OK
+ fvz-rec-us-tx-02 - OK
+ fvz-rec-us-wa-01 - OK
- fvz-rec-za-wc-01 - Failed

Hi,
thanks for letting me know.
Seems the default dnscrypt-wrapper on fvz-rec-lv-rix-01 crashed, I switched this to my kernel module implementation which should be more stable.
fvz-rec-za-wc-01 is currently being rebuilt after the disk RAID died a few hours ago.
Mind telling me what you have used for checking these? Would be useful for me to monitor all my instances.
Thanks!
Regards,
Fusl

Do you have a kernel module implementation of dnscrypt-wrapper? o_O
There is a simple script in the dnscrypt-proxy source tree that checks the health of all the listed resolvers:
https://github.com/jedisct1/dnscrypt-proxy/blob/master/resolvers-check.sh
I have this run in a cron job to keep the CSV file clean with only working resolvers.
You can also just use dnscrypt-proxy --test=... in a cron job. This will alert you not only when it doesn't work but also when the current certificate is about to expire.
There is also this Docker image you can use: https://github.com/jedisct1/dnscrypt-server-docker
It set ups everything including scripts that constantly check the health of the cache and the proxy, and restart the services if required. No need to worry about expiring keys and having to generate new keys either, it's done automatically.


Thanks for the review, @scottn12!


add test utils to Makefile

@kflynn merging this, need this for faster iteration of unit tests. Lmk if you see something wrong.


The package "esbuild-linux-64" could not be found, and is needed by esbuild.

Describe the bug
This Vite project seems to fail startup in a Node.js container, as shown in the terminal log below. The error is the same one from https://github.com/vitejs/vite/issues/5187, and installing<EMAIL_ADDRESS>(as a workaround) does resolve the error, but then it runs into #351.
~/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found
❯ npm install && npm run serve
warn preInstall No description field
warn preInstall No repository field
warn preInstall No license field
┌ [1/3] 🔍  Resolving dependencies
└ Completed in 0.209s
┌ [2/3] 🚚  Fetching dependencies
│ info pruneDeps Excluding 2 dependencies. For more information use `--verbose`.
└ Completed in 0.819s
┌ [3/3] 🔗  Linking dependencies
└ Completed in 0.877s
info security We found `install` scripts which turbo skips for security reasons. For more information see https://turbo.sh/install-scripts.
├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>
success Saved lockfile "package-lock.json"
success Saved lockfile "yarn.lock"
success Updated "package.json"

success Install finished in 2s
$ vite preview
failed to load config from /home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/vite.config.js
error when starting preview server:
Error: The package "esbuild-linux-64" could not be found, and is needed by esbuild.

If you are installing esbuild with npm, make sure that you don't specify the
"--no-optional" flag. The "optionalDependencies" package.json feature is used
by esbuild to install the correct binary executable for your current platform.
    at generateBinPath (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/esbuild/lib/main.js:1643:15)
    at esbuildCommandAndArgs (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/esbuild/lib/main.js:1699:11)
    at ensureServiceIsRunning (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/esbuild/lib/main.js:1856:25)
    at Object.build (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/esbuild/lib/main.js:1749:26)
    at bundleConfigFile (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/vite/dist/node/chunks/dep-be032392.js:68624:34)
    at loadConfigFromFile (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/vite/dist/node/chunks/dep-be032392.js:68601:35)
    at Object.resolveConfig (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/vite/dist/node/chunks/dep-be032392.js:68151:34)
    at CAC.eval (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/vite/dist/node/cli.js:781:36)
    at CAC.runMatchedCommand (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/vite/dist/node/cli.js:633:34)
    at CAC.parse (/home/projects/stackblitz-bug-esbuild-linux-64-could-not-be-found/node_modules/vite/dist/node/cli.js:560:12)

Link to the blitz that caused the error
https://stackblitz.com/edit/stackblitz-bug-esbuild-linux-64-could-not-be-found?file=package.json
Steps to reproduce

Import this Vite project from GitHub into a Node.js container.
Install deps and start the dev server: npm install && npm run serve
Observe the error

Expected behavior
The blitz starts without error
Screenshots
No response
Platform
Browser name  = Chrome
Full version  = 94.0.4606.81
Major version = 94
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 89984606,
  "usedJSHeapSize": 62801150,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = c39325dd3d976e6d2170e0078ef1d9bb3de015b9

Additional context
No response

This started happening to me today. Was previously ok in this project a couple of weeks ago with no changes to build script or other versions.
I'm using node:18-alpine


Adjust repository following branch renaming

Some changes are purely cosmetic but the changes in the workflows are strictly necessary.

Awesome, thanks a lot for this!


feat: added bengali translation

Please go the the Preview tab and select the appropriate sub-template:

General PR: for all other PRs, including bug fixes, adding features etc.
Translation PR: specifically to be used for translation PRs

Thanks, I'm pleased to contribute.


[Improvement] Configuring Trino Engine heap memory and java opts

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
Introduce

kyuubi.engine.trino.memory

default 1g
The heap memory for the trino query engine

kyuubi.engine.trino.java.options

default optional
The extra java options for the trino query engine

kyuubi.engine.trino.extra.classpath

default optional
The extra classpath for the trino query engine, for configuring other libs which may need by the trino engine =

How should we improve?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

I am willing to do it.


[Map] CTF-Susurrous

Duplicate of https://unrealarchive.org/maps/unreal-tournament/capture-the-flag/S/ctf-susurrous_4b8f9c7e.html

URL: https://unrealarchive.org/maps/unreal-tournament/capture-the-flag/S/ctf-susurrous_62f98122.html
Hash: 62f98122da88f1842142516240d8f8561a6b7de4
Current name: CTF-Susurrous

Updated, marked as variation


Go tests are failing

https://github.com/MakeContributions/DSA/actions/workflows/go.yml

https://github.com/MakeContributions/DSA/actions/workflows/go.yml

Ok, would you like to help me on this ?

Hi @cclauss or @atin,
Could you help me with this issue?

Not sure what is the issue with golang-ci? maybe this https://github.com/golangci/golangci-lint/issues/825
But using this https://github.com/reviewdog/action-golangci-lint works


(BKR-1132) adds concept of manual_test and manual_step

Adds an option --exec-manual-tests
adds manual_tests. This allows use to do some automated setup for manual
test cases, but also skips them when run in CI
adds manual_step. This allows us to pass or fail a test after prompting
the tester

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4061/

LGTM, yardoc failures need fixed before this can be merged.
Two comments:

Should this be in subcommands and not the main beaker program? I think it should be in the main beaker execution - I think users of this will run an entire beaker suite from their workstation. They won't necessarily want to pick out particular subcommands.
This deserves a how_to document; but I think time should only be spent on that after the feature is approved

what kinds of things need manual verification, requiring a person to say y/n in a beaker test?

@kevpl - we forwarded you an email with some internal discussion for context.
To record some of the context in this PR as well, a couple of categories of tests we'd use this for are:

Tests that are temporarily manual because they don't get priority to be implemented as automated tests before the product release they're first needed for.
Visual tests that need human eyes. These can eventually be automated, there's tools for this; but we have product releases we need to do before we can set that tooling up.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4074/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4081/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4082/

The checks seem to have passed. Except for an unrelated windows issue.

@puppetlabs-jenkins retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4090/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4105/

last comment still current

@kevpl - one of your comments is hidden against an old commit, but is still valid.
You asked about the environment for running these:
I think the environment/context for running these will be executing beaker on a laptop/workstation; using rake tasks that are as close as possible to the rake tasks that run the executed tests in CI (use the same vmpooler hosts, use the same package installation, run some or all of the automated tests as well as these special manual tests).
We haven't considered results storage - the workflow for manual testing today is that we generally do not store manual test results; we file tickets for anything that's not right; and everything else has implicitly passed. Maybe in future we would want a results store.

Regarding the suggestion to make pry available at this point: that would be a good subsequent update to this. It wouldn't be useful in all cases; but it would be a handy option for immediate investigation.
You can also mix this new option with the --debug-errors options and mark this test failed then immediately drop into pry. Though it may be nice to have the option to debug an unexpected failure when you did not expect to have to set the --debug-errors option

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/4132/


prevent sb-admin-2 from 4.0.0 upgrade

See #867

too late for #swag reward ?

@h00die never to late for that. Hit me up on slack with your address and we'll get some swag sent over, Thanks for helping to make DefectDojo better.


Mount propagation fixes (and also oomd)

ugh.

The /dev/shm dance is lifted from https://github.com/arkane-systems/bottle-imp/blob/master/binsrc/imp-executor/main.py#L28


⚠ Bofrost.at has degraded performance

In d936e0f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2231 ms

Resolved: Bofrost.at performance has improved in bf96ee6.


fix(deps): upgrade http2 to v0.24. Fixes CVE-2023-45288

Fixes CVE-2023-45288
This fixes the failing Snyk check on main branch.

This fixes the failing Snyk check on main branch.

Snyk is still failing after this merge. Follow-up PR in #12921, which causes a diff in the go.sum and so should fix the issue

Backported to release-3.5 cleanly as 1c3401dc68236979fc26b35c787256fcb96a7d1f

Needed to get this in so that #12921 won't have merge conflicts (which makes things simpler)


ONNX failures in cadene models

This issue documents the models that fail "read_onnx" when ONNX files are exported from the cadene pretrained repository (these might be known issues, so can resolve as duplicate when fixed, but leave as documentation until they are fixed):
nasnetalarge: operators.hpp:334: Non-axis dimensions should match
nasnetamobile: operators.hpp:334: Non-axis dimensions should match
pnasnet5large: operators.hpp:334: Non-axis dimensions should match
Symptoms and naming of the files suggest these are likely the same issue.
This issue also documents the models that fail "perf_onnx" at runtime when ONNX files are exercised:
dpn107, dpn131, dpn68b, dpn92, dpn98, resnext101_32x4d, resnext101_64x4d -
Memory access fault by GPU node-2 (Agent handle: 0x1882a50) on address 0x5048ea0
00. Reason: Page not present or supervisor privilege.
fbresnet152 -
terminate called after throwing an instance of 'migraphx::version_1::exception'
what():  /data/repo/AMDMIGraphX/src/program.cpp:310: Invalid program from comp
ilation at instruction 1028
inceptionresnetv2 -
terminate called after throwing an instance of 'migraphx::version_1::exception'
what():  /data/repo/AMDMIGraphX/src/program.cpp:310: Invalid program from comp
ilation at instruction 2020
Separate from that there are a few models that fail to export due to a pytorch/onnx issue unrelated to migraphx (https://github.com/pytorch/pytorch/issues/2898).  These include: bninception, squeezenet, xception, senet, se_resnet, se_resnext, cafferesnet.  Included here for completeness.

Cadene models now all pass (at least the ones I can export).  Closing this issue.


Docs: Installing dependencies for MacOSX: sudo brew cask install java8 does not work

Installing dependencies for MacOSX on: https://github.com/Microsoft/malmo/blob/master/doc/install_macosx.md
sudo brew cask install java8
cannot work (except if homebrew itself is owned by root). The reason is that homebrew does not allow sudo for security reasons.
I was able to install java8 with:
brew tap caskroom/versions
brew cask install java8

the second step will invoke sudo and ask for your password.

Removed sudo from instructions thanks.


⚠ Bofrost.gr has degraded performance

In e1bac34, Bofrost.gr (https://www.bofrost.gr) experienced degraded performance:

HTTP code: 200
Response time: 1809 ms

Resolved: Bofrost.gr performance has improved in 29bb01e after 9 minutes.


Support CredentialName configuration in DR for sidecars

Signed-off-by: Faseela K<EMAIL_ADDRESS>RFC: Simplify sidecar egress mTLS
Currently egress mTLS configuration on sidecar does not allow supplying credentialName. This PR
tries to allow the same, provided the credentials are available in the same namespace as the workload with
proper RBAC.
Phase 2 of the solution would allow cross namespace access of secrets, which would be pursued later.
I had pursued the work in a previous PR at https://github.com/istio/istio/pull/36746.
However there were comments from the maintainers about performance concerns on the PR, as the changes introduced
would delay the pod bring up time for pods who are not having access to the secrets specified in the DR.
A suggestion was given to implement workloadSelector in DR, so that the above mentioned problem can be resolved.
Now that workload selector implementation is completed for DR, trying to enhance the above work by making use of the DR workload selector concept.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@kfaseela: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
582d1fa51a68887add7738ef8710dc8a38a5fbf4
link
true
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio

@kfaseela: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
d3f4e6a73dd0ce6c31dd55e106d7dc11a4f6ed45
link
unknown
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster_istio


Deploy Script to generate sitemap.xml

Context
We need to generate sitemaps on deploy.
Problem or idea
We essentially want to have this script from the older version of refinebio-frontend but we should use refinebio-js for fetching the results.
Solution or next step

Add an updated version of the script
Add it to the deploy process of refinebio-web
Note: we should remove this from the deploy process on staging because this adds a considerable amount of time to the build step (~5m). We should first test this on staging and then in a future issue / PR remove it and only have it run on production deploys.

NOTE: This feature branch will be created based on the latest PR #119 (114 - Clean up Sample Details Page Code).


Global caches in ProfileSupport should be tenant-specific

Describe the bug
Global caches in ProfileSupport are not currently tenant-specific which means that tenant-specific profiles acquired through the ServerRegistryResourceProvider may be visible globally. Instead, these caches should be tenant-specific.
Environment
Which version of IBM FHIR Server?
To Reproduce
Steps to reproduce the behavior:

Enable ServerRegistryResourceProvider on a server with two tenants (A and B)
As a user of tenant A, create a StructureDefinition that defines an extension
As a user of tenant A, validate a resource that contains this extension (loading this StructureDefinition and its generated constraints in our caches)
As a user of tenant B, validate a resource that contains this extension

Note that the extension is validated with the constraints from tenant A even though tenant B may have a different version of the extension definition.
Expected behavior
Users on tenant B should not have visibility into any conformance resources posted to tenant A.
Additional context
Very similar to #2256.
I hope there's not more of these hiding, but we should consider advising users to avoid multiTenant deployments with serverRegistryResourceProvider enabled (unless they control who is allowed to create conformance resources).

QA: Passed
I ran with two different datastores (Postgres and Db2). One for default and one for tenant1.
I created a StructureDefinition, I showed that the cache'd rule was not applicable for the default tenant and available for the tenant1 and failed.
Negative tests showed the only way to screw this up is to misconfigure the data store so they share the tenants share the same exact schema.


Consuming REST API in Flutter: Building a weather App that makes a network call to a backend Server.

Proposed title of article
Consuming REST API in Flutter: Building a weather App that makes a network call to a backend Server.
Proposed article introduction
This article is teaches how to consume a REST API in a flutter application using the Dio package. We will be building a weather app that provides real-time weather information by making a network call to a weather API. Users can enter the name of a city and get the weather report of city. Flutter GetX package will be used for state management.
Key takeaways
How to use the Dio package for network calls.
How to build a real-time weather app.
Understand how to throw exception during network calls.

Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

@Lekwacious Please ensure that you focus more on the Dio package rather than Flutter GetX which you already covered in your previous tutorials. Thanks


Updated Theme: Internet Weblog

Theme submission
This theme was already on the hugoThemes repository but was recently removed due to an issue. The issue has been resolved and I'd like to have it added back to the list.
Link to my theme repository: https://github.com/jnjosh/internet-weblog
I made sure that...

[X ] the repository contains a good README.md describing my theme
[ X] an open source license has been added to LICENSE.md
[ X] all metadata have been added to theme.toml
[ X] screenshots have been added in the images/ folder with the required dimensions
[ X] in case I'm using a customized demo via the exampleSite folder that

[X ] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[ X] the site's content is as neutral as possible (contains no ads etc.) and reflects the features of my theme

[ X] I tested my theme against the gohugoio/HugoBasicExample

[X] I've checked the developer tools' console in my browser for error messages

[X] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

Feel free to ask questions. We're glad to help.

Hello @jnjosh
Thank you for fixing the issue! :+1
I confirm that your theme’s demo now works.
However I noticed that your theme’s screenshots have transparency. Also I understand that these have been like that for the past 2 years or so.
But thumbnails with transparency don’t look good on the Themes Showcase list.
Can you please remove the transparency and the drop shadow effect from your theme’s screenshots while keeping the correct dimensions mentioned in the repository’s README?
Please do the above and I will send a PR to have your theme re-added.
PS You can keep the screenshot with the drop shadow in your theme’s README if you want.
CC / @digitalcraftsman

@jnjosh You also need to remove the transparency and the browser chrome from the thumbnail: https://github.com/jnjosh/internet-weblog/blob/master/images/tn.png
Thanks.

@onedrawingperday Oops, sorry about that. I saw screenshot and just fixed it without thinking that it was named differently for the showcase. It's updated now.

Hey Josh,
thank you for fixing the issues in the theme so quickly.
I don't want to nag on the screenshots but could you add them in the required dimensions? You can find them in the README. Otherwise, everything looks great.

@digitalcraftsman Oops, too focused on removing the transparency and forgot about the size requirements. Done.

No problem Josh. You theme has been added again and should appear soon on our theme site. Have a nice weekend :smiley:


Charsets .json files

Hey @cmang , love using durdraw! Noticed one curiosity. Indurdraw.ini I see the following stanza:
;[Charset]
;charset-file-utf8: durdraw/charsets/unicode-legacy-computing.json
;charset-file-cp437: durdraw/charsets/cp437-ibmpc.json

What are these files? I see they're not in the distribution so I'm really more curious than anything else. Thanks!

Hey @ryanfantus . Thank you! Those are an unimplemented feature. I was sketching around some ideas for storing character sets, but the code to access them does not exist yet. Sorry for the confusion, to get your hopes up. :)
Version 0.29 might have it as a feature. I'm not sure yet. But it is pretty high on the agenda.

Just to elaborate... the idea is that eventually you will have a Code Page 437 character set that you can load, and get access to a fully IBM-PC compatible character set. Or you would be able to make your own custom character set files for F1, F2, etc. with your own Utf-8 characters.  Instead of having to switch between Unicode blocks, etc.


[Question] Multiple prompts/batches

❓ General Questions
Hi, is it possible to input multiple prompts or batches when running CLI? Is there any reference code? Thank you!

Hi @bethalianovike, thanks for the question! We are actively developing the batching and serving support, and it is expected to be released in the soon future. You can refer the branch https://github.com/mlc-ai/mlc-llm/tree/serving and the PRs https://github.com/mlc-ai/mlc-llm/pulls?q=is%3Apr+[serving] for the current status. Please stay tuned :-)

Hi @bethalianovike thank you for following up. The serving branch is still under development, and the file you ran is very likely outdated (sorry for not maintaining that file, perhaps I should check and remove it), but I'm happy to share some commands that you can use to run some of the tests or set up the server right now.
There are a few steps to follow:

build TVM from source with FlashInfer enabled (only available for CUDA right now), by adding set(USE_FLASHINFER ON) in under path/to/tvm/build/config.cmake. (Following this section to build TVM from source https://llm.mlc.ai/docs/install/tvm.html#option-2-build-from-source)
compile model with the command

python build.py --model=Llama-2-7b-chat-hf \
    --quantization=q0f16 \
    --sep-embed \
    --enable-batching

then you would be able to run tests like tests/python/serve/test_serve_async_engine.py or tests/python/serve/server/test_server.py.

It is possible that I missed a few steps here (apologize in ahead if that happens). We are actively working on the serving branch, and will post detailed documentation once ready.

Hi @MasterJH5574
Thank you for your response!
test_serve_async_engine.py runs well in my environment. Thank you for your help!


[Bug] Clarify 404 error when default namespace doesn't exist

I have getting 404 flash messages in the web gui until i gave it this
./tctl --namespace default namespace register

maybe worth explaining this in the README for other newbies like me ?

@gedw99 thanks for filing!
moved it under the UI repo for addressing

Awesome, thanks! We have adding a number of classes of errors to the UI on our roadmap for the next 2 weeks. This is a super helpful callout that I didn't have on that list.

@feedmeapples You solved this #260, right?

not exactly, we could show for example a message saying run tctl --namespace <name> namespace register next to the 404. @canvanooo thoughts?


bufr->prepbufr in acft file path

maybe path should be /noaa-reanalyses/pds/observations/reanalysis/conv/prepbufr/2019/08/prepbufr.acft_profiles (everything up to prepbufr.acft_profiles is the same as for prepbufr)

@jswhit i will take your lead on this suggestion. It will be a massive rename but if we are doing it, might as well.

another idea would be just have one directory  /noaareanalyses/pds/observations/reanalysis/conv/prepbufr/YYYY/MM/DD with both the prepbufr and prepbufr.acft_profiles bufr files in there.

i like the first option more. that will be more in line how we handle other types of data,


Mathematical Function Calls

Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: Mathematical Function Calls
Document link: mathematical-function-calls.md
My Issue/Suggestion
The pow function behaves very differently in Nanoflows, due to the use of big.js. The pow function in big.js requires an integer as the exponent, which is not clearly documented, neither here in the documentation, nor in the modeler itself (allows decimal values to be used in the pow function, which leads to runtime errors).

@NatasaKralj please work with @Yiyun333 to resolve this issue.
9.17 had an update for pow: https://docs.mendix.com/releasenotes/studio-pro/9.17/#fixes

Yes, we have changed this in 9.17. When a decimal is used an exponent, we don't use Big.js but fallback to inprecise calculation using regular JavaScript. The same happens in the runtime (but with Java).

Verified with @Robinfr , added alert and Javascript (instead of just Java) to function information. See commit add3ead


Upgrade bundler to fix platform resolution issue on arm64

Bundler 2.3.3 has a bug that fails to resolve platforms https://github.com/rubygems/rubygems/issues/5088. This issue occurs on Mac and Debian arm64, and this patch to upgrade bundler resolves it by upgrading to the latest bundler.

Hi,
Thanks for the PR. To produce that new lock file did you do anything besides deleting the existing Gemfile.lock and then rebuilding the image from scratch?

Hi! 👋 I didn't delete the existing lock file, I just ran bundle install after installing bundler 2.3.6.
gem install bundler -v 2.3.6
bundle install

I don't see a trace of updating bundler to 2.3.6 in this PR.

@nickjj this PR resolves the issue with Bundler < 2.3.6 that caused a fatal error trying to resolve platforms that weren't already listed in the Gemfile.lock. There's nothing special about this except that the bundler version currently recommended in the Gemfile.lock has a fatal error on arm64 platforms, like a Raspberry Pi or a Mac M1.
The solution is:

Recommend the latest bundler 2.3.6 that does not include this issue:
https://github.com/nickjj/docker-rails-example/blob/f1fbcbce58c913f794e60ac339bc62a405ef6161/Gemfile.lock#L256-L257
This will output a warning when someone uses an older version of bundler. Unfortunately because of the way bundler works, this is the best you can do to "require" a bundle version. This isn't "fixing" anything, except ensuring that there's a warning if someone tries to use a bundler version that has above linked bug.
It uses this latest version of bundler to bundle install and successfully resolve the platform that is missing for aarch64. This is the specific fix for your package that allows it to run on arm64 platforms.
https://github.com/nickjj/docker-rails-example/blob/f1fbcbce58c913f794e60ac339bc62a405ef6161/Gemfile.lock#L136-L142

Gotcha, thanks. It was this part that was throwing me for a loop: "This will output a warning when someone uses an older version of bundler". I didn't think it would even run if it were bundled with a different version that's defined in the lock file.
I wonder tho, maybe we should explicitly update bundler to 2.3.6 in the Dockerfile to avoid the warning.

Gotcha, thanks. It was this part that was throwing me for a loop: "This will output a warning when someone uses an older version of bundler". I didn't think it would even run if it were bundled with a different version that's defined in the lock file.

I wish, or that we could say BUNDLED_WITH: > 2.3.3 but bundler doesn't have that feature.

I wonder tho, maybe we should explicitly update bundler to 2.3.6 in the Dockerfile to avoid the warning.

Yeah, that makes sense. I just checked and the image will automatically install the latest version:
#13 [assets 4/8] RUN bundle install --jobs "$(nproc)"
#13 0.318 Bundler 2.3.3 is running, but your lockfile was generated with 2.3.6.
    Installing Bundler 2.3.6 and restarting using that version.

Not sure why it doesn't do that for me locally, maybe it's a setting.
We could do it explicitly, like:
diff --git a/Dockerfile b/Dockerfile
index 9165f47..fe306fb 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,6 +1,8 @@
 FROM ruby:3.1.0-slim-bullseye AS assets
 LABEL maintainer="Nick Janetakis<EMAIL_ADDRESS>
+ARG BUNDLE_VERSION=2.3.6
+
 WORKDIR /app

 RUN bash -c "set -o pipefail && apt-get update \
@@ -17,7 +19,7 @@ RUN bash -c "set -o pipefail && apt-get update \
 USER ruby

 COPY --chown=ruby:ruby Gemfile* ./
-RUN bundle install --jobs "$(nproc)"
+RUN gem install ${BUNDLE_VERSION} && bundle install --jobs "$(nproc)"

 COPY --chown=ruby:ruby package.json *yarn* ./
 RUN yarn install

I'm happy to add that to this PR.

What do you think about using bundle update bundler 2.3.6? This way it's more clear that Bundler is already available in the base Docker image and we're updating it instead of installing it for the first time?
I'm also ok with hard coding the value to drop the extra Docker layer. Since it's not something that would change we don't need to introduce a new build arg. I know you likely wanted to put it there because having magic numbers floating around the middle of the file is bad but I think it's ok here.
Also in theory this problem should self resolve in the next version of the Docker Ruby image. Also have you tried https://github.com/docker-library/ruby/issues/374? Maybe we can get past this without modifying the lock file. Basically it comes down to setting the platform at build time, or do you think that wouldn't apply here since it's fundamentally a bundler issue?

What do you think about using bundle update bundler 2.3.6? This way it's more clear that Bundler is already available in the base Docker image and we're updating it instead of installing it for the first time?

That seems like an idea, but where would you put the bundle update bundler 2.3.6? Bundler isn't included in the Gemfile, so there wouldn't be anything to update with bundler that I can think of.

I'm also ok with hard coding the value to drop the extra Docker layer. Since it's not something that would change we don't need to introduce a new build arg. I know you likely wanted to put it there because having magic numbers floating around the middle of the file is bad but I think it's ok here.

Yeah, I don't think it's as important to do that as to get the fix in. Seems fine without the ARG, I just usually default to options!

Also in theory this problem should self resolve in the next version of the Docker Ruby image. Also have you tried https://github.com/docker-library/ruby/issues/374? Maybe we can get past this without modifying the lock file. Basically it comes down to setting the platform at build time, or do you think that wouldn't apply here since it's fundamentally a bundler issue?

I believe that it is fundamentally a bundler issue related to building native gems. The ruby docker image has been working fine for me without specifying platform until I ran into this bundler version issue 🤷🏻. Even if you embed the platform in the docker-compose.yml file or manually run docker build --platform every time before docker compose up, I think that nokogiri and friends will still fail to build on arm64 with the broken bundler version.

I haven't forgotten about this btw. Just still letting this percolate before moving forward with a mergeable solution. I also haven't seen anyone else report this and I don't have an M1 or another ARM64 device to test things on.

Hey, I think we have a built in solution now. Let me know if this commit from the main branch fixes things for you out of the box https://github.com/nickjj/docker-rails-example/commit/f7cafb54ac4854322cf76080ba32112aa4af22a8.
The Ruby 3.1.1 image is using Bundler 2.3.7. It's been pushed to this repo's main branch with a new Gemfile that shows it's been bundled by 2.3.7. I didn't apply any patches other than re-building things.

Yep, it's working great now! No need for the patch. Cheers! 🍻


Running MSBuild.exe /version (or solution file) in terminal is ok:
Microsoft (R) Build Engine version 14.0.25420.1 Copyright (C) Microsoft Corporation. All rights reserved.
Running the same MSBuild.exe (or any other exe) inside emacs (25, 26.2) hangs and doesn't return anything:

At the same time, executing all linux specific binaries works just fine.

What's wrong / what should be happening instead:

Running the same MSBuild.exe (or any other exe) inside emacs shell, eshell or compilation buffer (25, 26.2) hangs and doesn't return anything.
The problem repeats itself in ConEmu, new Windows Terminal, and simple instances of wsl Debian, Ubuntu distros (default cmd line) on default emacs 25 installed from apt, and 26.2 src builded.
Before Windows 1903 update running exe inside emacs shell, eshell or compilation buffer was right.
MSBuild.exe or any other command line exe program must run inside emacs shell, eshell or compilation buffer correctly.

Strace of the failing command, if applicable:
ms_build_err.txt
ms_build_ok.txt

Update: Christopher Crawford on [https://devblogs.microsoft.com/commandline/whats-new-for-wsl-in-windows-10-version-1903] talks about the same problem, but in his case, its resolved by update KB4512508 which already installed for me. After deleting this update through settings menu on my computer and reinstalling it in automatic mode problem persist,

Update: Installed KB4517211 update. Problem persists.

Update: KB4517389 also doesn't fix the problem.

This breaks my workflow as well, any known workarounds? emacs settings or bash that can be done?

I am looking at this bug. However, until it is fixed, the workaround seems to be using term instead of shell or eshell. I am able to run windows binaries via term from within emacs without any issues.

Thanks for the workaround.
FYI the same things happens when invoking "M-x compile" with default 'make' when 'make' does the call to the window executable.

I think I hit this bug when my corp upgraded Win10 last month.  Looked into it and it seems to only be triggered when Emacs attempts to start a Windows console executable as an asynchronous process.  If you interrupt the process from eshell, then the ~conhost~ instance that seems related to it suddenly maxes out a single core and you must kill in manually from task manager.  It seems to be tied to some issue with setting up the file streams in the sub-process, or at least that is my best guess.
I found a workaround that actually works with my work-flow.  I created a program (at end) which will create a child process, read all of its stdout and stderr output and send it back out on the parent's stdout and stderr.  Why this is necessary, not sure, but it seems to do the trick.
If you customize shell-file-name to point to this executable and async-shell-commad and compile will start working.  Eshell does its async stuff differently and ignores the value of shell-file-name, so you will need to patch it to make it work as expected.
--- esh-proc.el	2020-03-30 22:43:46.532596300 -0500
+++ esh-proc.el.new	2020-03-30 22:49:19.360686600 -0500
@@ -283,7 +283,8 @@
 	      (apply 'start-file-process
 		     (file-name-nondirectory command) nil
 		     ;; `start-process' can't deal with relative filenames.
-                     (append (list (expand-file-name command)) args))))
+                     (append (list shell-file-name "-c")
+                             (list (mapconcat 'identity (cons command args) " "))))))
       (eshell-record-process-object proc)
       (set-process-buffer proc (current-buffer))
       (if (eshell-interactive-output-p)

Source of wsl-proxy (this is mostly taken from this howto)  Probably has bugs, but it seems to work for me.
/* This program is to work around some bug in the way WSL console handling works
 * with async processes launched from Emacs.
 *
 * Currently, processes launched in an asynchronous way cause the sub process to
 * hang and, if killed, produces a run-away conhost process which must be killed
 * from the task manager.  This seems tied to the way input/output streams are
 * handled, so we do them manually in this program and it seems to work. */

#include <stdio.h>
#include <stdint.h>
#include <stdlib.h>
#include <unistd.h>
#include <errno.h>
#include <string.h>
#include <sys/types.h>
#include <sys/wait.h>
#include <poll.h>

int main(int argc, char *argv[])
{
   int fd_out[2];
   int fd_err[2];
   if (pipe(fd_out) == -1)
   {
      perror("stdout pipe");
      exit(1);
   }
   if (pipe(fd_err) == -1)
   {
      perror("stderr pipe");
      exit(1);
   }

   pid_t pid = fork();
   if (pid == -1)
   {
      perror("fork");
      exit(1);
   }
   else if (pid == 0)
   {
      while ((dup2(fd_out[1], STDOUT_FILENO) == -1) && (errno == EINTR)) {}
      while ((dup2(fd_err[1], STDERR_FILENO) == -1) && (errno == EINTR)) {}

      close(fd_out[1]);
      close(fd_out[0]);
      close(fd_err[1]);
      close(fd_err[0]);

      argv[0] = "/bin/sh";
      execvp(argv[0], &argv[0]);
      perror(argv[0]);
      _exit(1);
   }
   close(fd_out[1]);
   close(fd_err[1]);

   uint8_t buffer[4096];
   int keep_going[] = {1, 1};
   while (keep_going[0] || keep_going[1])
   {
      struct pollfd fds[] = {
         {
            .fd = fd_out[0],
            .events = POLLIN,
            .revents = 0
         }, {
            .fd = fd_err[0],
            .events = POLLIN,
            .revents = 0
         }
      };

      if (poll(fds, 2, -1))
      {
         for (int i = 0; i < 2; i++)
         {
            if (fds[i].revents & POLLHUP)
            {
               keep_going[i] = 0;
            }
            if (!(fds[i].revents & POLLIN))
            {
               continue;
            }

            ssize_t count = read(fds[i].fd, buffer, sizeof(buffer));
            if (count == -1)
            {
               if (errno == EINTR)
               {
                  continue;
               }
               else
               {
                  char *stream_names[] = {"stdout", "stderr"};
                  perror(stream_names[i]);
                  exit(1);
               }
            }
            else if (count == 0)
            {
               break;
            }
            else
            {
               FILE *output_streams[] = {stdout, stderr};
               fwrite(buffer, 1, count, output_streams[i]);
            }
         }
      }
   }

   int child_status;
   if (wait(&child_status) == -1)
   {
      perror("wait");
   }

   if (WIFEXITED(child_status))
   {
      close(fd_out[0]);
      close(fd_err[0]);
      exit(WEXITSTATUS(child_status));
   }

   close(fd_out[0]);
   close(fd_err[0]);
   exit(0);
}

One trick that seems to work is to redirect all outputs to /dev/null (for example by appending 2>&1 > /dev/null to the command). See this "hack" that I use.

@nidrissi Thanks a lot for the tips quite functional even though clearly a hack.
Allow me to add to your advice the following alternative that preserve output log: 2>&1 | tee or simply | tee seems to work too.
Enjoy

Had the same problem with emacs 27.1 on WSL1 (downgraded from WSL2).
Setting process-connection-type to nil fixed the problem for me.


Need to improve network Speed

Expected behavior

Actual behavior

To reproduce

System information

when the miner getmore efficent of mining computatuional network speed is low, capability of 3000 kH/s is working speed is  CPU #0: 75 H, 183.78 H/s only so we need to speed up core server. that make more solution of this network


Install Error "use of undeclared identifier 'LZMA_OK'"

hi,

Mac OS 10.12
Xcode8

Command history:
~ gem install shenzhen
or
~sudo ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future gem install shenzhen
Building native extensions.  This could take a while...
ERROR:  Error installing shenzhen:
ERROR: Failed to build gem native extension.
/Users/leihuo/.rvm/rubies/ruby-2.2.4/bin/ruby -r ./siteconf20161116-41730-16zdzaw.rb extconf.rb

checking if the C compiler accepts ... yes
checking if the C compiler accepts -Wno-error=unused-command-line-argument-hard-error-in-future... no
Building nokogiri using packaged libraries.
Using mini_portile version 2.1.0
checking for iconv.h... yes
checking for gzdopen() in -lz... yes
checking for iconv using --with-opt-* flags... yes

IMPORTANT NOTICE:
Building Nokogiri with a packaged version of libxml2-2.9.4.
Team Nokogiri will keep on doing their best to provide security
updates in a timely manner, but if this is a concern for you and want
to use the system library instead; abort this installation process and
reinstall nokogiri as follows:
gem install nokogiri -- --use-system-libraries
    [--with-xml2-config=/path/to/xml2-config]
    [--with-xslt-config=/path/to/xslt-config]

If you are using Bundler, tell it to use the option:
bundle config build.nokogiri --use-system-libraries
bundle install

Note, however, that nokogiri is not fully compatible with arbitrary
versions of libxml2 provided by OS/package vendors.

Extracting libxml2-2.9.4.tar.gz into tmp/x86_64-apple-darwin15.6.0/ports/libxml2/2.9.4... OK
Running 'configure' for libxml2 2.9.4... OK
Running 'compile' for libxml2 2.9.4... ERROR, review '/Users/leihuo/.rvm/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>/ext/nokogiri/tmp/x86_64-apple-darwin15.6.0/ports/libxml2/2.9.4/compile.log' to see what happened. Last lines are:
unsigned short* in = (unsigned short*) inb;
                     ^~~~~~~~~~~~~~~~~~~~~

encoding.c:815:27: warning: cast from 'unsigned char ' to 'unsigned short ' increases required alignment from 1 to 2 [-Wcast-align]
unsigned short out = (unsigned short) outb;
^~~~~~~~~~~~~~~~~~~~~~
4 warnings generated.
CC       error.lo
CC       parserInternals.lo
CC       parser.lo
CC       tree.lo
CC       hash.lo
CC       list.lo
CC       xmlIO.lo
xmlIO.c:1450:52: error: use of undeclared identifier 'LZMA_OK'
ret =  (__libxml2_xzclose((xzFile) context) == LZMA_OK ) ? 0 : -1;
^
1 error generated.
make[2]: *** [xmlIO.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.
Provided configuration options:
--with-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/Users/leihuo/.rvm/rubies/ruby-2.2.4/bin/$(RUBY_BASE_NAME)
--help
--clean
--use-system-libraries
--enable-static
--disable-static
--with-zlib-dir
--without-zlib-dir
--with-zlib-include
--without-zlib-include=${zlib-dir}/include
--with-zlib-lib
--without-zlib-lib=${zlib-dir}/lib
--enable-cross-build
--disable-cross-build
/Users/leihuo/.rvm/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:366:in block in execute': Failed to complete compile task (RuntimeError) 	from /Users/leihuo/.rvm/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:337:in chdir'
from /Users/leihuo/.rvm/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:337:in execute' 	from /Users/leihuo/.rvm/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:111:in compile'
from /Users/leihuo/.rvm/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/mini_portile2-2.1.0/lib/mini_portile2/mini_portile.rb:150:in cook' 	from extconf.rb:365:in block (2 levels) in process_recipe'
from extconf.rb:258:in block in chdir_for_build' 	from extconf.rb:257:in chdir'
from extconf.rb:257:in chdir_for_build' 	from extconf.rb:364:in block in process_recipe'
from extconf.rb:263:in tap' 	from extconf.rb:263:in process_recipe'
from extconf.rb:556:in `'
extconf failed, exit code 1
Gem files will remain installed in /Users/leihuo/.rvm/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS> for inspection.
Results logged to /Users/leihuo/.rvm/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-15/2.2.0/nokogiri-<IP_ADDRESS>/gem_make.out
✘ hanliu@leihuodeMac-mini  ~ 

I have the same error,if you solve it ,please help me,Thx

@mattt Can you help us?

Your mac lack of Command Line Tools, go to https://developer.apple.com/download/more/ download the “command line tools” and install, and you will fix it.

Thanks @QinYaffeei -- your suggestion solved the issue for me (macOS 10.11 el capitan)

I faced the same issue while installing nokogiri,
Installing with system libraries ( gem install nokogiri -- --use-system-libraries ) solved it


Add cli support for choices and default

Extending leapp command to support traditional argparse-style choices
and default arguments.

Can one of the admins verify this patch?

/rerun

/rerun

/rerun


Writer does not write strings with leading blanks

A cell set with
lo_worksheet->set_cell( ip_column = 'B' ip_row = 2 ip_value = ' b' ).
! ip_value is filled with a leading blank !
will be output by the writer w/o the leading blank.

Solved with revision 432


[tvla] Reading of CW databases broken

Currently, our tvla script seems to only extract the first 20k traces of a CW database. I have several databases holding 2M and 10M AES traces but only the first 20k traces are effectively read out.
Does anyone know why this is the case and how to fix it? @nasahlpa @vrozic ?

oh, back in October/November when I last used the script, it reported on stdout that it would use larger numbers. Does it report 20k on stdout now?

I am not aware of such a limit - could you please provide me with the DB file and I try to reproduce & fix it.

Hm, this is strange. I've now switched to an old version and it still just takes the first 20k traces. I am wondering if maybe the database is actually broken.

A quick investigation of the generated CW project files reveals that all but the last two 10k segments are "disabled". When storing the segments or at the very end of the capture, we have to enable them. This seems to have gone wrong when reworking the capture setup. I'll adjusted the title accordingly and will file a PR.


Update README.md

Poortego has a brand new codebase in Python, replacing original ruby version.

Brand new is a big word, but you're right ;-)


The terminal are closed when I try to close the window and click Cancel button.

VSCode Version: 1.17.2
OS Version: macOS High Sierra 10.13

Steps to Reproduce:

Create a new file and type something but do not save the file
Click new terminal
Click the button on the left-top corner of the window to close the window
Click 'Cancel' button to stop closing the window.
The terminal is already closed.

Reproduces without extensions: Yes
When I opened too many of code windows, I close them one by one by click the button on the left-top corner. But I made a mistake that I tried to close a window which should not be closed. Something important was on the terminal and something not saved yet. I click the cancel button but the terminal  has gone.

Doesn't seem to repro on Windows 10, vscode 1.17.2
Is it Mac only issue?

Same Here, on macOS Sierra 10.12.5

I expect this to happen on all platforms.

@Tyriar  Ubuntu 14.04 and code 1.17.2 not reproduce. Maybe  the problem is only on macOS

This should be fixed in the upcoming version


[incubator/ibm-blockchain-chaincode] Add IBM Blockchain Chaincode

Source code located in the following repository:

https://github.com/IBM-Blockchain/ibm-container-service

@unguiculus, changes have been added.

Please consider my comment regarding namespacing and best practices. Once you have your templates namespaced, follow this example for naming resources and labels:
name: {{ template "ibm-blockchain-chaincode.fullname" . }}
labels:
  app: {{ template "ibm-blockchain-chaincode.name" . }}
  chart: {{ .Chart.Name }}-{{ .Chart.Version }}
  release: {{ .Release.Name }}
  heritage: {{ .Release.Service }}

@unguiculus, I've added the namespaces.

Let me point out our best practices again. And please read our review guidelines which give you a good overview across what we expect.
https://github.com/kubernetes/charts/blob/master/REVIEW_GUIDELINES.md

@unguiculus, the templates should be namespaced now.

@unguiculus, this PR should be up-to-date with the requested changes.  Please let me know if additional changes are required.


Update grpc_release_schedule.md

To match go/grpc-oss-release-dates (shift 1.31.x and higher by 2 weeks)

Known failures: https://github.com/grpc/grpc/issues/23466


copy & paste will add extra %20 to clipboard

sometime i ask gpt to give the code. directly copy & paste is ok, but some time format need readjust in the destination editor
click copy button at the output, and paste in the target editor, i see all [SPACE] are replaced with %20 as well as other ESCAPE code. for / \ and etc.
Hope we can fix that.

The UI has been redesigned, transitioning from Ant Design to Material Tailwind. Consequently, the markdown code copy feature, which was nice to have but not essential, has not been included in the new UI. Therefore, this bug is no longer applicable.


Adaptive time-stepping

Due to the non-disipative nature of the shallow water equation, the time scale soley depends on input parameters containing a dimension of time ($\gamma$ and $\mu$), but not on the relaxation time $\tau$. That allows for cheap addaptive time-stepping like so:
Write a new presssure and friction force function
function filmpressure_dt!(state::LBM_state_1D, sys::SysConst_1D, dt::Float64)
    # println("This is the pressure I am using!")
    hip, him = viewneighbors_1D(state.dgrad)
    # Straight elements j+1, i+1, i-1, j-1
    circshift!(hip, state.height, 1)
    circshift!(him, state.height, -1)

        if sys.n==9 && sys.m==3
                state.pressure .= -sys.γ*dt*dt .* (1 .- cospi.(sys.θ)) .* (sys.n - 1) .* (sys.m - 1) ./ ((sys.n - sys.m) * sys.hmin) .* Swalbe.fast_disj_93.(sys.hmin./(state.height .+ sys.hcrit))
        elseif sys.n==3 && sys.m==2
                state.pressure .= -sys.γ*dt*dt .* (1 .- cospi.(sys.θ)) .* (sys.n - 1) .* (sys.m - 1) ./ ((sys.n - sys.m) * sys.hmin) .* Swalbe.fast_disj_32.(sys.hmin./(state.height .+ sys.hcrit))
        else
                throw(DomainError((sys.n,sys.m), "This disjoining pressure is not implemented, Options currently are (n,m)=(9,3) or (n,m)=(3,2). Use those or implement a new option."))
        end
        state.pressure .-= sys.γ*dt*dt .* (hip .- 2 .* state.height .+ him)
    return nothing
end

and
function slippage_dt!(state::LBM_state_1D, sys::SysConst_1D, dt::Float64)
    state.slip .= (6*sys.μ*dt .* state.height .* state.vel) ./ (2 .* state.height.^2 .+ 6*sys.δ .* state.height .+ 3*sys.δ^2 )
    return nothing
end

With those function a minimalistic siumlation run has to look like this:
using Pkg

Pkg.activate(".")

using Swalbe

function run(;
    h=2,
    eps=0.001,
    Tmax=Int(1e8),
    dumps=100,
    tdump=Int(floor(Tmax/dumps)),
    L=2^8,
    delta=0.0,
    n=9, m=3,
    gamma=0.01,
    theta=1/9,
    data=dataall,
    plot=true,
    run=true,
    hmin=0.2,
    mu=1/6,
    dt_init=1.0,
    F_max=1e-4,
    relax_F=1e-3,
    dt_max=100
    )

    #Setup system
    sys = Swalbe.SysConst_1D(L=L, Tmax=Tmax, tdump=tdump, γ=gamma, δ=delta, n=n, m=m, hmin=hmin, θ=theta,  μ=mu)
    state = Swalbe.Sys(sys)
    state.height .= Swalbe.randominterface!(state.height, h, eps, L/2-L/10)
    println("Starting LBM time loop")
    t=0.0
    dt=dt_init
    i=0
    while t<=sys.Tmax
        if (t % sys.tdump + dt) >= sys.tdump
            #Store data

            #Plot data
            if plot

            end
            #status report
            println("Time step t=$(round(t,sigdigits=3)), mass m=$(round(sum(state.height),sigdigits=5)), diff d=$(round(maximum(state.height)-minimum(state.height), sigdigits=7)),dt=$(round(dt, sigdigits=3))")
            i+=1
        end
        if run
            Swalbe.filmpressure_dt!(state, sys, dt)
            Swalbe.h∇p!(state)
            Swalbe.slippage_dt!(state,sys, dt)
            state.F .= -state.h∇p  .-  state.slip
            Swalbe.equilibrium!(state)
            Swalbe.BGKandStream!(state)
            Swalbe.moments!(state)
            dt = min(dt*(1+relax_F*(F_max - abs(maximum(state.F)))/F_max),dt_max)
        end
        t+=dt
    end
end

run()

The idea is that numerical instability always comes from to high forcing, while to small forcing means that the code could be run faster. Thus setting a optimal force, that is numerically stable but not to small, and going up or down in the time step when the force becomes to small or to high will let the code run with the biggest possible time step without leading to too high forces. Then we have to multiply $\gamma$ by $dt^2$ and $\mu$ by $dt$ for dimensional reasons.
Tests
The insight is pretty new so I havn't tested much, but equilibrium properties of films should not be effected by $\gamma$ and $\mu$. Concerning time evolution the LSA of spinoidal rupture is fulfilled on small wavenumbers, there is just a lot more noise on the high wavenumbers. That was to be expected as we are permanently running at boaderline high forcing:
top left: film height, top right: FFT of filmheight vs LSA, bottom left: friction force, bottom right: pressure

After Film rupture of course the LSA is not expected to fit the data anymore, but we can see how the firction force is kept at a level that is close to creating numerical problems but is still tolerable

Time steps
Here is a plot of $dt$ indicating a speed up of factor almost 15 before film-rupture and 1.5 after film rupture for the parameters I have chosen

F_max
It seems like $F_{\max}=10^{-4}$ seems to be the most that is feasible. Above the code crashes or produces unphysical output. But playing arround with paramaters one can try to figure out what works and what doesn't.

@Zitzeronion

That looks like a very powerful feature for future versions.
Of course, we have to make sure that it works as intended. Would you mind (@aedolfi) compiling a PR with a short section of this in the docs?
Thanks!


Onboarding Settings: create a prototype with the graphs we will use

Create two Jupiter notebooks:

For the Issuance app
For the Conviction Voting app

For CV, make sure to see: https://hackmd.io/Hj7pp7ZTQGmROC6zNDD1tg
And
https://sim.commonsstack.org

Here are the models:

Conviction Voting
Dynamic Issuance


[dtests] Added few Negative tests

Added few of the negative scenarios as part of HIP dtests.

This is updated version of #1728.  Hence closing it.


yml-style config?

my-paper.yml
stories:
  weather:
  	zipcode: 99999
  twitter:
    accounts:
      - j6m8
      - associatedpress
  rss:
  	feeds:
    	- https://pluralistic.net/feed/
  reddit:
  	subreddits:
    	- news

goosepaper --config my-paper.yml

Closed in #11!


Publishing on F-Droid store

Hi,
this might not be the right place where to ask this, I'm about to install your app on my Android phone and I'll probably download it straight from github, although it would be nice to have it published on F-Droid if that could be possible
thanks

see #566


How to show speeds from different speedtest servers

I have the SPEEDTEST_SERVER_ID environment variable empty, so I assume it will just choose the best server but Grafana looks like this

with the server and location fields empty

What are you setting for INFLUX_DB_TAGS? I believe you need server_name, server_location, server_host, and speedtest_url at a minimum, for the included dashboard.

just set it to * as a wildcard and works perfectly. Thanks!


Add CA Workload Automation CA 7® (API Mediation Layer ZOWE V1)

Signed-off-by: John Mertic<EMAIL_ADDRESS>

Goes live 9/18


Problem acquiring iSCSI volumes with new Bosh VSIs

When attempting a Bosh-based deployment, the following error is seen when provisioning VSIs:
Started updating job core-node > core-node/0 (fda10350-e343-4946-9127-f5ca02bebcb5) (canary). Failed: Attaching disk '24867541' to VM '32489483': Granting volume access to virtual guest 32489483: IBM02SVC421436_31 is not yet ready for mount, please try again after Volume Provisioning is complete. (00:02:11)
Error 100: Attaching disk '24867541' to VM '32489483': Granting volume access to virtual guest 32489483: IBM02SVC421436_31 is not yet ready for mount, please try again after Volume Provisioning is complete.
This has been happening fairly consistently at various times of the day over the last couple of days.
It seems the trouble is possibly with the create_disk() method in the Bosh SoftLayer CPI not calling "getVolumeStatus()" on newly-provisioned iSCSI volumes and waiting until their status is "PROVISION_COMPLETED".

It's better to check the property "isReadyToMount" (== 1) on the SoftLayer Network_Storage volume, and use that as the determining factor for whether the volume is ready to have disks attached via the SoftLayer API.

Hi. This issue is blocking a critical customer deployment for us. Would it be possible to get an ETA for a fix? Thanks.

@nihillno Which version of CPI release are you using? The latest one v12 should have already fixed this problem.

Ooh, it's pretty old - 3.0.5. It was updated to 12.0.1 on the environment in question - D_CIO - 25 minutes ago, as it happens. We'll see if that improves things. Many thanks!

This is now working nicely. Thanks all!


CONTRIBUTING.md e2e instructions are out of date

Description
CONTRIBUTING.md includes information about running end-to-end (e2e) tests as follows:
https://github.com/jupyterlab/retrolab/blob/9010ff543538dd6b15d647dd38ce44626095db84/CONTRIBUTING.md?plain=1#L81-L95
This information is out of date. The app/test folder no longer exists in the retrolab package. There is a ui-tests folder with a test subdirectory, but I'm not sure whether this contains the e2e tests to which CONTRIBUTING.md currently refers.
Reproduce
Attempt to follow the instructions in CONTRIBUTING.md listed above
Expected behavior
Nonexistent directory app/test

Thanks @jweill-aws for catching this.
There were couple of changes in https://github.com/jupyterlab/retrolab/pull/273. Will update with the new instructions.


[stable/elasticsearch-curator] Remove @desaintmartin from OWNERS/maintainers

What this PR does / why we need it:
Remove @desaintmartin from OWNERS/maintainers as he requested to do so in #23383
Special notes for your reviewer
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

Why didn't you approve my PR?
But for the fun, I'm going to approve my own removal myself:
/ok-to-test
/lgtm


Feature/update resharper annotations

Part of #2952

@304NotModified , could you please re-run travis build? I could not see build log, however build of my next PR #2975 was succeeded.

@304NotModified , could you please re-run travis build? I could not see build log, however build of my next PR #2975 was succeeded.

restarted!

merged :) THX!


Admin login broken when proxying Grav on alternative port

I have a certain environment where I'm running Grav on port 8080, everything works fine but the admin login doesn't work because when logging in it redirects me to:
http://localhost/admin
When it should be:
http://localhost:8080/admin

I run my main development site on port 8080, so it's not a scenario I can reproduce / it's not a known issue within Grav. Grav picks up the port it's running on.
I don't have an immediate answer at what could be the problem, which web server are you using?

Sorry haven't answered before, actually I haven't explained this properly, I'm not really running on port 8080, I'm proxying port 80 to 8080 with HAproxy, I guess that is why this different to your scenario.

Ok in this case you need to enable reverse_proxy_setup in user/config/system.yaml, did you try already?

Thanks for the response @flaviocopes
Today I've played around with the settings, I've tried reverse_proxy_setup: true  but it still makes no difference to me, I'm getting same results.
I've also tried specifying the port in the custom URL like this:
custom_base_url: http://localhost:8080

But then all links look liked:
<link rel="icon" type="image/png" href=":8080/user/plugins/admin/themes/grav/images/favicon.png">
Which was incorrect since it translates to a URL with the port repeated twice:
http://localhost:8080/:8080/user/plugins/admin/themes/grav/images/favicon.png
I attempted to work around that error by using
absolute_urls: true

Which would then print the absolute URL correctly, this is so far the closest to working I have, but there are still some other errors: I was seeing a red 'Invalid security token' error on the dashboard and login panel, and when I click on logout there seems to be a loop error in the URL, making the URL look like:
http://localhost:8080/admin/task:logout/:8080/admin/logout/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/:8080/admin
Any ideas?
Thanks!

I've been browsing through the code a bit and I've found out that it picks the login URL from this line of code:
/user/plugins/admin/themes/grav/templates/partials/login.html.twig:19
The {{uri.url}} var will render an absolute URL, e.g:
<input type="hidden" name="redirect" value="http://localhost/admin">

I think my problem would be fixed if it rendered either:
<input type="hidden" name="redirect" value="/admin" />

or
<input type="hidden" name="redirect" value="http://localhost:8080/admin">

I'd do a pull request but I'm not entirely sure how to achieve this.

I have setup a reverse proxy configuration locally, but I have no issues in using Grav Admin. I used this very simple nginx reverse proxy https://gist.github.com/natchiketa/987524a561e892924e81 and tried both with Apache running in a subdirectory (localhost:8009/grav/), or Caddy running in the domain root (localhost:8009/) and in both cases, no issues.
I guess the problem is in the HAproxy config, but no idea what it might be. If you can try the above nginx setup to isolate the problem, would be 👍

custom_base_url is meant to be used in other scenarios, mainly when you want Grav to respond on the root but be physically located in a subfolder, with htaccess redirects in place.

Closing to due to inactivity


Creation of custom objects fails even when they are registered/created with new_class

Which project are you reporting a bug for?
kr8s
What happened?
>>> from kr8s.objects import new_class
>>> StorageClientNS = new_class(
...     kind="StorageClient",
...     version="ocs.openshift.io/v1alpha1",
...     namespaced=True,
... )
>>> sc = StorageClientNS("temp-client", "default")
>>> sc.create()
[...]
  File "/root/.virtualenvs/update-416/lib/python3.12/site-packages/kr8s/_api.py", line 158, in call_api
    raise ServerError(kr8s._exceptions.ServerError: the object provided is unrecognized (must be of type StorageClient): Object 'Kind' is missing in '{"metadata": {"name": "temp-client", "namespace": "default"}}' ({"metadata": {"name": "temp-cl ...)
>>> sc.raw['kind'] = sc.kind
>>> sc.raw['apiVersion'] = sc.version
>>> sc.create()
>>> sc.raw
{'apiVersion': 'ocs.openshift.io/v1alpha1', 'kind': 'StorageClient', 'metadata': {'creationTimestamp': '2024-06-11T05:19:11Z', 'generation': 1, 'name': 'temp-client', 'namespace': 'default', 'resourceVersion': '133029', 'uid': '33b37505-cd5d-4a92-baac-05e8c81dbcbb'}}

However, pre-created APIObjects doesn't have this issue. Returning to python after sometime and not able to debug (my knowledge is from pre-asyncio 😅), I believe the type creation type(name, base, attrs) seems to be working (untested) in async context but when sync is derived out of it, above issue might be hit.

Another small unrelated one, let me know if you need a new issue, during creation of objects from files auto creation of classes always set namespaced=True is it possible to infer the namespace from the marshalled spec and set accordingly?
Thanks a lot for the project, I wanted something more that kubectl and less (in the sense of verbosity) than client-go and kr8s hits the sport, is helpful so far.
Anything else?
No response

Thanks for raising this. I'm not sure this has anything to do with asyncio.
It looks to me like Kubernetes is more strict around validating the spec of custom resources being passed to it than it is for core objects.
For example I can create a Pod where the raw spec doesn't include the kind or apiVersion and it creates just fine.
from kr8s.objects import Pod

po = Pod({'metadata': {'name': 'foo'}, 'spec': {'containers': [{'name': 'foo', 'image': 'nginx'}], 'restartPolicy': 'Always'}})
po.create()  # Works!

However for custom resources those values need to be explicitly set.
from kr8s.objects import new_class

Sidecar = new_class("Sidecar", "networking.istio.io/v1beta1")
sc = Sidecar({'metadata': {'name': 'default', 'namespace': 'prod-us1'}, 'spec': {'egress': [{'hosts': ['./*']}]}})
sc.create()

---------------------------------------------------------------------------
HTTPStatusError                           Traceback (most recent call last)
File ~/Projects/kr8s-org/kr8s/kr8s/_api.py:145, in Api.call_api(self, method, version, base, namespace, url, raise_for_status, stream, **kwargs)
    144 if raise_for_status:
--> 145     response.raise_for_status()
    146 yield response

File ~/miniconda3/envs/kr8s/lib/python3.11/site-packages/httpx/_models.py:761, in Response.raise_for_status(self)
    760 message = message.format(self, error_type=error_type)
--> 761 raise HTTPStatusError(message, request=request, response=self)

HTTPStatusError: Client error '400 Bad Request' for url 'https://<IP_ADDRESS>:34993/apis/networking.istio.io/v1beta1/namespaces/prod-us1/sidecars'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400

The above exception was the direct cause of the following exception:

ServerError                               Traceback (most recent call last)
Cell In[13], line 1
----> 1 sc.create()

File ~/Projects/kr8s-org/kr8s/kr8s/_async_utils.py:110, in run_sync.<locals>.run_sync_inner(*args, **kwargs)
    108 if inspect.iscoroutinefunction(coro):
    109     portal = Portal()
--> 110     return portal.call(wrapped)
    111 raise TypeError(f"Expected coroutine function, got {coro.__class__.__name__}")

File ~/Projects/kr8s-org/kr8s/kr8s/_async_utils.py:90, in Portal.call(self, func, *args, **kwargs)
     88 while not self._portal:
     89     pass
---> 90 return self._portal.call(func, *args, **kwargs)

File ~/miniconda3/envs/kr8s/lib/python3.11/site-packages/anyio/from_thread.py:288, in BlockingPortal.call(self, func, *args)
    273 def call(
    274     self,
    275     func: Callable[[Unpack[PosArgsT]], Awaitable[T_Retval] | T_Retval],
    276     *args: Unpack[PosArgsT],
    277 ) -> T_Retval:
    278     """
    279     Call the given function in the event loop thread.
    280
   (...)
    286
    287     """
--> 288     return cast(T_Retval, self.start_task_soon(func, *args).result())

File ~/miniconda3/envs/kr8s/lib/python3.11/concurrent/futures/_base.py:456, in Future.result(self, timeout)
    454     raise CancelledError()
    455 elif self._state == FINISHED:
--> 456     return self.__get_result()
    457 else:
    458     raise TimeoutError()

File ~/miniconda3/envs/kr8s/lib/python3.11/concurrent/futures/_base.py:401, in Future.__get_result(self)
    399 if self._exception:
    400     try:
--> 401         raise self._exception
    402     finally:
    403         # Break a reference cycle with the exception in self._exception
    404         self = None

File ~/miniconda3/envs/kr8s/lib/python3.11/site-packages/anyio/from_thread.py:217, in BlockingPortal._call_func(self, func, args, kwargs, future)
    214         else:
    215             future.add_done_callback(callback)
--> 217         retval = await retval_or_awaitable
    218 else:
    219     retval = retval_or_awaitable

File ~/Projects/kr8s-org/kr8s/kr8s/_objects.py:274, in APIObject.create(self)
    272 async def create(self) -> None:
    273     """Create this object in Kubernetes."""
--> 274     async with self.api.call_api(
    275         "POST",
    276         version=self.version,
    277         url=self.endpoint,
    278         namespace=self.namespace,
    279         data=json.dumps(self.raw),
    280     ) as resp:
    281         self.raw = resp.json()

File ~/miniconda3/envs/kr8s/lib/python3.11/contextlib.py:204, in _AsyncGeneratorContextManager.__aenter__(self)
    202 del self.args, self.kwds, self.func
    203 try:
--> 204     return await anext(self.gen)
    205 except StopAsyncIteration:
    206     raise RuntimeError("generator didn't yield") from None

File ~/Projects/kr8s-org/kr8s/kr8s/_api.py:158, in Api.call_api(self, method, version, base, namespace, url, raise_for_status, stream, **kwargs)
    156 if e.response.status_code >= 400 and e.response.status_code < 500:
    157     error = e.response.json()
--> 158     raise ServerError(
    159         error["message"], status=error, response=e.response
    160     ) from e
    161 elif e.response.status_code >= 500:
    162     raise ServerError(
    163         str(e), status=e.response.status_code, response=e.response
    164     ) from e

ServerError: the object provided is unrecognized (must be of type Sidecar): Object 'Kind' is missing in '{"metadata": {"name": "default", "namespace": "prod-us1"}, "spec": {"egress": [{"hosts": ["./*"]}]}}' ({"metadata": {"name": "default ...)

I think we should be able to fix this by updating the .raw property to always include those values.

Also could you open a separate issue for the namespaced=True issue. Thanks for the kind words about the library, glad it's useful for you.

This should now be fixed in v0.16.0

I'm not sure this has anything to do with

ack, pls excuse, partially a human tendency to point onto something new that I don't know as a reason 😅

This should now be fixed in v0.16.0

superfast, pulled it, it works.

Also could you open a separate issue

done #404