Fixed issue where the curdir wasn't in the path so the import wouldn'…

I have been running into the issue where I want a migration to be auto generated for me.
My project layout is as such:
auth/
-auth/
-- __init__.py
--migrations.py
-migrations/
-poetry.lock

I am CDed into the auth/ dir and run this command:
pw_migrate create --database=${DB_URL} --auto --auto-source=auth  -v initial

And it always comes back as
Can't import models module: auth

Ends up, when I placed a pdb in router.py in the create method on the BaseRouter object.. the CURDIR is not in the path. Thus I just added it and now it works. Plus I ran tox to ensure that all tests continued to pass.
Hopeful we can get this change into 1.0.0 so this issue won't plague others.
Context:
I am using python 3.7 in an virtualenv with poetry as my package manager. I am working on writing an AWS Lambda function with the serverless framework and I want to use peewee as my orm, but I needed a package to handle migrations for me. This package is the Bees Knees :D! Thank you friends.

Coverage decreased (-0.1%) to 75.065% when pulling eeb7422ab7e88d9c34351aa728bea4d3ec687206 on Ryanb58:py37-fix-auto-source-not-picking-up-models-in-package into 0052ff8b84fc6e7fea11a8ebb45438b60425f784 on klen:develop.

Thank you sir.


Add flattenEach function and tests

A few todos:

[x] Figure out how to handle geometry collections. turf.js doesn't seem to handle them in flattenEach
[x] Figure out how to properly make a test for the breaking of iteration since the callbacks seem impossible to type together cohesively with the way the .js test implements it with function pointers. Perhaps we just need to break it up into separate tests.

According to the RFC, "To maximize interoperability, implementations SHOULD avoid nested GeometryCollections." src
which means, that we MAY encounter a GeometryCollection returned as the geoJson object in the geomEach callback that flattenEach uses.
Turf.js doesn't support it, but I think we should handle the case. One idea might be to simply recursively call flattenEach with the same arguments, passing it the GeometryCollection which geomEach would iterate through to call the callback for each flattened feature.
Thoughts?

I'll write a test and propose a solution in code so you can see it more clearly.

According to the RFC, "To maximize interoperability, implementations SHOULD avoid nested GeometryCollections." src
which means, that we MAY encounter a GeometryCollection returned as the geoJson object in the geomEach callback that flattenEach uses.
Turf.js doesn't support it, but I think we should handle the case. One idea might be to simply recursively call flattenEach with the same arguments, passing it the GeometryCollection which geomEach would iterate through to call the callback for each flattened feature.
Thoughts?

oh I see, we've actually implemented this to strictly forbid this since a GeometryCollection's geometries are of type GeometryType
with that information then geomEach's return type should probably be a GeometryType rather than a GeoJSONObject and then flattenEach doesn't need to handle the case of if it receives a geom collection from geomEach.

oh I see, we've actually implemented this to strictly forbid this since a GeometryCollection's geometries are of type GeometryType

Yeah, that‘s one of the advantages of my super strict class hierarchy! 😊

with that information then geomEach's return type should probably be a GeometryType

That’s true. Good catch!

Should we add an explicit warning in the deserialization functions for nested GeometryCollections?

I’ll do a full review in the morning

Should we add an explicit warning in the deserialization functions for nested GeometryCollections?

Something in this place? What should do? Throw a hard error? where could we print a warning?
--- a/lib/src/geojson.dart
+++ b/lib/src/geojson.dart
@@ -570,9 +570,13 @@ class GeometryCollection extends GeometryObject {
             : BBox.fromJson(
                 (json['bbox'] as List).map((e) => e as num).toList(),
               ),
-        geometries: (json['geometries'] as List?)
-                ?.map((e) => GeometryType.deserialize(e))
-                .toList() ??
+        geometries: (json['geometries'] as List?)?.map((e) {
+              if (e is GeometryCollection) {
+                // TODO what action should we take here for nested geometry
+                // collections?
+              }
+              return GeometryType.deserialize(e);
+            }).toList() ??
             const [],
       );

Something in this place? What should we do? Throw a hard error? where could we print a warning?

I mean, it will already throw an hard error inside of geometryType.deserialize:
default:
    throw Exception('${json['type']} is not a valid GeoJSON type')

But I thought we could maybe give a little bit more context, like: "This implementation does not support nested GeometryCollections.", similar to the one in the README.
Maybe let's put a case GeoJSONObjectType.geometryCollection: before the default case, with a dedicated warning?

       geometries: (json['geometries'] as List?)?.map((e) {
+              if (e is GeometryCollection) {
+                // TODO what action should we take here for nested geometry
+                // collections?
+              }

We have to be careful here: e is not yet deserialized, so it's still a Map<String, dynamic>.

I'll resolve the conflicts with this branch next week and then we can try and merge it

I want to merge this soon, because #https://github.com/dartclub/turf_dart/pull/49 depends on it.
@baparham is it ok, if I take over? Thanks for the great work already 😄
CC @armantorkzaban

Go for it


cmake version validation is broken

Search before asking

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

Version
unstable, 8ffdfaf2d5caf73977a9855066d7e06ecc93c76f
Minimal reproduce step
% ./x.py build
Traceback (most recent call last):
File "./x.py", line 312, in
args.func(**arg_dict)
File "./x.py", line 95, in build
check_version(cmake_version, CMAKE_REQUIRE_VERSION, "CMake")
File "./x.py", line 80, in check_version
raise RuntimeError(f"{prog_name} {require_version} or higher is required, got: {current}")
RuntimeError: CMake 3.13.0 or higher is required, got: 3.22.2
..
%
What did you expect to see?
cmake 3.22.2 should be accepted
What did you see instead?
cmake 3.22.2 was rejected
Anything Else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Sorry for the false alarm. Issue seems to be addressed already.


Remove fetch from preset, reset, and fetch_key

#189 removes the use of fetch in the main memo_wise logic. We should replicate this removal in #preset_memo_wise, #reset_memo_wise and references to fetch_key.

This was done in the final version of #189.


dev

push some changes to fix the gitignore
(actually what even happened? i don't remember the gitignore to be different than before :thinking: )

actually it's a big mess.
i should clean the project completely and create a fresh dev-godot branch


Changelly exchange inside the app

Add Changelly to the app to enable users to direct buy within the app.
When you have no balance and click send it shows you a card about buying NAV.

[x] Remove card icon
[x] Remove "show address" button
[x] Reword text "To get started, you can buy Nav Coin through our exchange partner Changelly."

Show this card always on the home screen (until we decide on a better UI) as well as on this no nav send screen.
When the "Buy Nav Coin" button is clicked, take them to a new page which shows:

[x] Changelly widget with our referral code and BTC/NAV pair
[x] Latest NAV address that can be clicked to copy, so the user can paste it into the changelly widget. Ideally it would look like the attached NAV Address screen shot but be clickable to copy.
[x] regular navigation at the bottom of the screen.

The rest should be handled by changelly.

 Can't load widget

get iframe to scale to mobile size somehow.


doc: update installation documentation

Fixes #1846
Description of the changes being introduced by the pull request:
Update severely outdated installation documentation.

Simplify "Simple Installation" section
Update "Release Verification" section to actually verify a tuf release and with a key of an active maintainer
Update and simplify section about non-python dependencies (just point to installation instructions for underlying crypto backends, they are up-to-date and have become a lot easier)
Add "Development installation" section

This PR also updates the install section in the contributing doc, plus other small fixes. See commits for details!
Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

See https://theupdateframework--1853.org.readthedocs.build/en/1853/INSTALLATION.html for how the docs look on RTD.

@jku, want to take another look at my latest changes? Or should we just merge?


Don't make clients think our DB is empty

Triggered by discussion: https://github.com/itchysats/maker-automation-rs/pull/124#discussion_r837068347
During startup, it can take a while to load the CFDs from the database.
Instead of lying to our clients during this time and presenting them an
empty list, we:
a) Don't emit the list on the feed
b) We return a 500 from the /cfds endpoint
There is nothing the client can do about this, hence it is not a 400.
Once the CFDs are loaded, the request will be fulfilled properly.
Fixes #1716.

I like this approach. It does seem like we introduce a lot more error paths after adding the None case, but this is more correct.

There is likely some potential for making this cleaner! To be honest, I did not bother much because I prioritized the correctness of the outcome over the implementation :)

bors r+


Fix overall responsiveness

Summary of changes:

Improved BlockiesAvatar by replacing useState and useEffect with useMemo. I also removed Box and extended ImageProps to make it more reusable/maintainable.
Removed the flex order and justifyContent keys in ConnectWallet to fix the swapping of elements in the navbar.
Improved ConnectWalletButton to accept all possible button props and forward them to the underlying button. I also set a default of 200px for its width (was 220px) because that was causing some responsiveness issues on narrow screens.
Made the avatar size responsive in CreatorCardDetails
Made some changes in CreatorCardNumbers to allow wrapping and keep things looking somewhat okay when that happens.
Changed CreatorList from the homepage from a flex-based to a grid-based layout that adapts better to different widths. The "iPad range" is not ideal, with a lot of empty space, but that's what we get with the Chakra's default breakpoints without getting too much into the weeds.
Changed Layout so that the footer remains at the bottom when a view's content doesn't fill a whole viewport height.
Changed the layout of logos on the homepage for better responsiveness.
Changed the layout of [walletId] for better responsiveness.

The diffs include a lot of formatting changes automatically made by Prettier. I think we should probably make sure our Prettier configs are working in the same direction. From the before and afters I think mine is working fine, but let me know if you think otherwise. We would probably benefit from making a big reformatting commit once that is established, so that actual code changes are easier to glean in future PRs.
The layout is still not worthy of a webby award, specially at some viewport widths, but it's an improvement from what we had and the most painful issues (overflows on narrow screens) should be fixed.
Let me know if you find any remaining glaring issues and feel free to raise any points with the implementation.

two quick things i noticed (i'm sure you are aware of both) :)

Nice, @raulrpearson. Some pretty good changes here. Works very well :)
Some things I just did:

fix: validateDOMNesting(...): <div> cannot appear as a descendant of <p> in CreatorsList
change: refactored Footer in own component and gave it the same max-width responsive wrapper as the Navbar
change: shortened "unsupported chain" in navbar
change: added hover-tooltip for supporter avatars with their address
change: shortened "staked {currency}" label in CreatorCardNumbers on mobile

One more thing we should consider:

I see a lot of "prettifier-related" changes your editor probably does. We should set up unified tooling regarding this, soon. If you want, we can merge and handle this in a separate ticket :)

Thanks, @wottpal.


Add an aria-lable so a screen reader will understand the sup tag

Can you s/lable/label/ in the commit message as well?

d'oh!  sorry, missed @mjgiarlo's comments.

Is the tabIndex="0" not needed?

i had the same question originally, but then i figured if the component was repeated, having a hardcoded tab index wouldn't be useful?
apologies if i jumped the gun on this merge!

I talked to @metageeky on slack and she pointed me in this direction.

I talked to @metageeky on slack and she pointed me in this direction.

ah, ok.  if the community's accessibility expert approves, that's good enough for me! 😁


Mousemove-effect

Project title
Mousemove effect by javascript
Project Description
Whenever mouse will move , small colourful circular particle s will follow it.
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS
[x]JavaScript

/assign


Update to megaparsec-7.0

Description:
Update to megaparsec-7.0. The change didn't break any test.
@juanpaucar Could you take a look please?

@juanpaucar Megaparsec-7 dropped the support for GHC 7.8.4. Should we also remove the support for that version of GHC?

@CristhianMotoche We will have to drop support for 7.8.4 if we plan to keep megaparsec. You could still use some CPP annotations to distinguish between ghc or megaparsec versions. But, I don't it's worth it. WDYT?

I don't like the idea of using CPP. We can close this PR for now and still use megaparsec-6.
Thanks @juanpaucar

@juanpaucar I reopened the PR. I suppose we will need it for later (when megaparsec-7 is updated in the stackage nightly).


Error In asynchronous Encrypt File Corrected

Error "Unhandled exception:
FileSystemException: An async operation is currently pending, path = '*.aes'
" Fixed.

Thanks!


Log file for indent

https://github.com/cereda/arara/blob/79092ab4302168913852f108d4ef82cdccfceb82/rules/indent.yaml#L42
@cmhughes Chris, I noticed this line and I think it does not look correct. I think it should be:
@{[ '-g', parameters.logfile ]}

Or something along those lines (untested). Thoughts?

Your proposal sounds good to me, although I don't have a way to test it.
latexindent can be called with, for example,
latexindent.pl -g=mylogfile.log
On Wednesday, February 7, 2018, Paulo Cereda<EMAIL_ADDRESS>wrote:

https://github.com/cereda/arara/blob/79092ab4302168913852f108d4ef82
cdccfceb82/rules/indent.yaml#L42
@cmhughes https://github.com/cmhughes Chris, I noticed this line and I
think it does not look correct. I think it should be:
@{[ '-g', parameters.logfile ]}
Or something along those lines (untested). Thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cereda/arara/issues/100, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACHxYNekQf_LzZ3JxmMR2w1jPtRuYmE_ks5tSZFwgaJpZM4R8mdv
.

Nice, Chris! Should I adopt the = sign or leave it as two parameters, as it is?

There should be no need for the = sign, as we can also call it simply as
latexindent.pl -g mylogfile.log
Thanks for all of your work here!
On Wednesday, February 7, 2018, Paulo Cereda<EMAIL_ADDRESS>wrote:

Nice, Chris! Should I adopt the = sign or leave it as two parameters, as
it is?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cereda/arara/issues/100#issuecomment-363765403, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACHxYO2NGa2vSO8_cIlJQ9Svd5xiAePOks5tSaIfgaJpZM4R8mdv
.

Done, Chris! Thank you!

Thanks, Paulo, I appreciate your work on this :)
On Wednesday, February 7, 2018, Paulo Cereda<EMAIL_ADDRESS>wrote:

Done, Chris! Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cereda/arara/issues/100#issuecomment-363798827, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACHxYGnZhOICj1HQg_6b8pV3K1g1lgxWks5tSbzzgaJpZM4R8mdv
.


feat: add Header,Footer,Content to Dialog

At first, thanks everyone to everyone for releasing version 3 and great improvements.
but I think there is more complexity for dialog component.
I suggest to add three property to dialog, so this is becomes more simpler to use
something like this
[Parameter]
public RenderFragment Header{get;set;}
[Parameter]
public RenderFragment Content{get;set;}
[Parameter]
public RenderFragment Footer{get;set;}
so we could add everything to header, content and footer of dialog
BR

You can already completely customize what is shown in Dialog content. See https://www.fluentui-blazor.net/#dialog-content
Header and Footer are underway. See PR #717


a.toLowerCase is not a function

My search doesn't work. Its shown this erro in console a.toLowerCase is not a function
Thie is the search code in the page
$('#filtrar_tree').keyup(function () {

	if(to) { clearTimeout(to); }

	to = setTimeout(function () {

		var v = $('#filtrar_tree').val();
		tree.jstree(true).search(v);

	}, 250);
});

An another page with the same code work perfectaly

Please provide a demo (jsfiddle for example) or at least - more information:

which version are you using
where is the error - which file, which line
how do you create the tree - what is your data source, maybe provide a sample

I will reopen on more information.


use git-cliff to generate CHANGELOG

What this PR does:
Which issue(s) this PR fixes:

Closes #559
Special notes for your reviewer:
use the git-cliff tool to replace changelogs.
Does this PR introduce a user-facing change?:

NONE

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

稍等，我们现在已经有发版记录，这个不一定要

OK. You can turn off the PR if you don't need it.

sorry ,感谢pr,目前还是手动发版

Codecov Report

Merging #560 (081be97) into master (8e89c54) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master     #560   +/-   ##
=======================================
  Coverage   36.99%   36.99%
=======================================
  Files         160      160
  Lines       11154    11154
=======================================
  Hits         4126     4126
  Misses       6681     6681
  Partials      347      347


Setting wallet servers from command line doesn't work

Supplying a list of wallet servers on the command line fails silently:
./lbrynet start --lbryum-servers='["spv9.lbry.com:50001"]'
No error message is output and the wallet component doesn't start.

what about:
./lbrynet start --lbryum-servers=spv9.lbry.com:50001


Make disabling reminders more obvious

We should make it even more obvious how to disable reminders.  It's anchored as "project_disabled_reminders".  We could make it much easier to find by including, in various messages, the hypertext link that jumps users specifically to the checkbox.  E.g.:
https://bestpractices.coreinfrastructure.org/en/projects/1#project_disabled_reminders
If we enabled redirection and logging in when going to an edit page, per #1118, we direct people directly to the edit page version of the checkbox.  E.g.,
https://bestpractices.coreinfrastructure.org/en/projects/1/edit#project_disabled_reminders
We could include this URL in both the initial "new project" email and also in the reminder email.
On the checkbox text itself, we could add text that says, "You must edit the project to change this" in the text about that.  That is true for anything on a project page, but if that helps people, great.
On the text that says, "You may select from one of your GitHub repos OR provide information about some other project." We could also add text like this: "If the project hasn't earned a passing badge and there have been no edits for at least 30 days, we'll send you a reminder email (you can disable reminders at any time if you want to)."  I don't think reminder emails are "spam" or anything like it; we only send them if people don't achieve the badge after a lengthy period of time, and people have taken actions to try to get one.

As related issue, we could make clearer in "create account" that one of those badge-related functions is sending reminders to non-passing project owners.

Even easier would be linking to the edit version (automatically enabling edit).  That would require code changes to enable automatic login and redirection on the way to an edit screen.


ModuleNotFoundError: No module named '_raymarching'

While running
!python main_nerf.py data/specs1light2 --workspace data/specs1light2 --iters 15000 --num_steps 128 --upsample_steps 128 --fp16 --bound 1.0 --scale 0.8 --dt_gamma 0 --tcnn
This issue occured.
Traceback (most recent call last):
  File "/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/raymarching.py", line 10, in <module>
    import _raymarching as _backend
ModuleNotFoundError: No module named '_raymarching'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/cpp_extension.py", line 2100, in _run_ninja_build
    subprocess.run(
  File "/usr/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

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

Traceback (most recent call last):
  File "/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/main_nerf2.py", line 85, in <module>
    from nerf.network_tcnn import NeRFNetwork
  File "/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/nerf/network_tcnn.py", line 9, in <module>
    from .renderer import NeRFRenderer
  File "/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/nerf/renderer.py", line 9, in <module>
    import raymarching
  File "/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/__init__.py", line 1, in <module>
    from .raymarching import *
  File "/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/raymarching.py", line 12, in <module>
    from .backend import _backend
  File "/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/backend.py", line 31, in <module>
    _backend = load(name='_raymarching',
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/cpp_extension.py", line 1308, in load
    return _jit_compile(
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/cpp_extension.py", line 1710, in _jit_compile
    _write_ninja_file_and_build_library(
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/cpp_extension.py", line 1823, in _write_ninja_file_and_build_library
    _run_ninja_build(
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/cpp_extension.py", line 2116, in _run_ninja_build
    raise RuntimeError(message) from e
RuntimeError: Error building extension '_raymarching': [1/3] /usr/local/cuda/bin/nvcc  -DTORCH_EXTENSION_NAME=_raymarching -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -isystem /usr/local/lib/python3.10/dist-packages/torch/include -isystem /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.10/dist-packages/torch/include/TH -isystem /usr/local/lib/python3.10/dist-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/include/python3.10 -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_75,code=compute_75 -gencode=arch=compute_75,code=sm_75 --compiler-options '-fPIC' -O3 -std=c++14 -U__CUDA_NO_HALF_OPERATORS__ -U__CUDA_NO_HALF_CONVERSIONS__ -U__CUDA_NO_HALF2_OPERATORS__ -c '/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/raymarching.cu' -o raymarching.cuda.o
FAILED: raymarching.cuda.o
/usr/local/cuda/bin/nvcc  -DTORCH_EXTENSION_NAME=_raymarching -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -isystem /usr/local/lib/python3.10/dist-packages/torch/include -isystem /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.10/dist-packages/torch/include/TH -isystem /usr/local/lib/python3.10/dist-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/include/python3.10 -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_75,code=compute_75 -gencode=arch=compute_75,code=sm_75 --compiler-options '-fPIC' -O3 -std=c++14 -U__CUDA_NO_HALF_OPERATORS__ -U__CUDA_NO_HALF_CONVERSIONS__ -U__CUDA_NO_HALF2_OPERATORS__ -c '/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/raymarching.cu' -o raymarching.cuda.o
In file included from /usr/local/lib/python3.10/dist-packages/torch/include/c10/util/string_view.h:4,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/c10/util/StringUtil.h:6,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/c10/util/Exception.h:5,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/Generator.h:11,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/CPUGeneratorImpl.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/Context.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/cuda/CUDAContext.h:18,
                 from /content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/raymarching.cu:5:
/usr/local/lib/python3.10/dist-packages/torch/include/c10/util/C++17.h:27:2: error: #error You need C++17 to compile PyTorch
   27 | #error You need C++17 to compile PyTorch
      |  ^~~~~
In file included from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/torch.h:3,
                 from /content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/raymarching.cu:6:
/usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/all.h:4:2: error: #error C++17 or later compatible compiler is required to use PyTorch.
    4 | #error C++17 or later compatible compiler is required to use PyTorch.
      |  ^~~~~
In file included from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:4,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/all.h:9,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/torch.h:3,
                 from /content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/raymarching.cu:6:
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/ATen.h:4:2: error: #error C++17 or later compatible compiler is required to use ATen.
    4 | #error C++17 or later compatible compiler is required to use ATen.
      |  ^~~~~
[2/3] c++ -MMD -MF bindings.o.d -DTORCH_EXTENSION_NAME=_raymarching -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -isystem /usr/local/lib/python3.10/dist-packages/torch/include -isystem /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.10/dist-packages/torch/include/TH -isystem /usr/local/lib/python3.10/dist-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/include/python3.10 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++17 -O3 -std=c++14 -c '/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/bindings.cpp' -o bindings.o
FAILED: bindings.o
c++ -MMD -MF bindings.o.d -DTORCH_EXTENSION_NAME=_raymarching -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -isystem /usr/local/lib/python3.10/dist-packages/torch/include -isystem /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.10/dist-packages/torch/include/TH -isystem /usr/local/lib/python3.10/dist-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/include/python3.10 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++17 -O3 -std=c++14 -c '/content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/bindings.cpp' -o bindings.o
In file included from /usr/local/lib/python3.10/dist-packages/torch/include/torch/extension.h:5,
                 from /content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/bindings.cpp:1:
/usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/all.h:4:2: error: #error C++17 or later compatible compiler is required to use PyTorch.
    4 | #error C++17 or later compatible compiler is required to use PyTorch.
      |  ^~~~~
In file included from /usr/local/lib/python3.10/dist-packages/torch/include/c10/util/string_view.h:4,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/c10/util/StringUtil.h:6,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/c10/util/Exception.h:5,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/c10/core/Device.h:5,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/TensorBody.h:11,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/Tensor.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/Tensor.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/autograd/function_hook.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/autograd/cpp_hook.h:2,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/autograd/variable.h:6,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/autograd/autograd.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/autograd.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/all.h:7,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/extension.h:5,
                 from /content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/bindings.cpp:1:
/usr/local/lib/python3.10/dist-packages/torch/include/c10/util/C++17.h:27:2: error: #error You need C++17 to compile PyTorch
   27 | #error You need C++17 to compile PyTorch
      |  ^~~~~
In file included from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:4,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/all.h:9,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/extension.h:5,
                 from /content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/bindings.cpp:1:
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/ATen.h:4:2: error: #error C++17 or later compatible compiler is required to use ATen.
    4 | #error C++17 or later compatible compiler is required to use ATen.
      |  ^~~~~
In file included from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/ivalue.h:1499,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/List_inl.h:4,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/List.h:490,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/IListRef_inl.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/IListRef.h:632,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/WrapDimUtils.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/TensorNames.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/NamedTensorUtils.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/autograd/variable.h:11,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/autograd/autograd.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/autograd.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/all.h:7,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/extension.h:5,
                 from /content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/bindings.cpp:1:
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/ivalue_inl.h: In lambda function:
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/ivalue_inl.h:1061:30: error: ‘is_convertible_v’ is not a member of ‘std’; did you mean ‘is_convertible’?
 1061 |         if constexpr (::std::is_convertible_v<typename c10::invoke_result_t<T &&, Future&>, IValueWithStorages>) {
      |                              ^~~~~~~~~~~~~~~~
      |                              is_convertible
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/ivalue_inl.h:1061:91: error: expected ‘(’ before ‘,’ token
 1061 |         if constexpr (::std::is_convertible_v<typename c10::invoke_result_t<T &&, Future&>, IValueWithStorages>) {
      |                                                                                ^
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/ivalue_inl.h:1061:111: error: expected primary-expression before ‘>’ token
 1061 |         if constexpr (::std::is_convertible_v<typename c10::invoke_result_t<T &&, Future&>, IValueWithStorages>) {
      |                                                                                ^
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/ivalue_inl.h:1061:112: error: expected primary-expression before ‘)’ token
 1061 |         if constexpr (::std::is_convertible_v<typename c10::invoke_result_t<T &&, Future&>, IValueWithStorages>) {
      |                                                                                ^
In file included from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/boxing/KernelFunction_impl.h:1,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/boxing/KernelFunction.h:251,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/op_registration/op_registration.h:11,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/library.h:68,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/autograd/autograd_not_implemented_fallback.h:3,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/autograd.h:4,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/csrc/api/include/torch/all.h:7,
                 from /usr/local/lib/python3.10/dist-packages/torch/include/torch/extension.h:5,
                 from /content/drive/MyDrive/Colab Notebooks/nerf2/torch-ngp/raymarching/src/bindings.cpp:1:
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/boxing/impl/boxing.h: In static member function ‘static Result c10::impl::BoxedKernelWrapper<Result(Args ...), typename std::enable_if<((c10::guts::conjunction<c10::guts::disjunction<std::is_constructible<c10::IValue, typename std::decay<Args>::type>, std::is_same<c10::TensorOptions, typename std::decay<Args>::type> >...>::value && c10::guts::conjunction<c10::guts::disjunction<c10::impl::has_ivalue_to<T, void>, std::is_same<void, ReturnType> >, c10::guts::negation<std::is_lvalue_reference<_Tp> > >::value) && (! c10::impl::is_tuple_of_mutable_tensor_refs<Result>::value)), void>::type>::call(const c10::BoxedKernel&, const c10::OperatorHandle&, c10::DispatchKeySet, Args ...)’:
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/boxing/impl/boxing.h:229:25: error: ‘is_same_v’ is not a member of ‘std’; did you mean ‘is_same’?
  229 |     if constexpr (!std::is_same_v<void, Result>) {
      |                         ^~~~~~~~~
      |                         is_same
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/boxing/impl/boxing.h:229:35: error: expected primary-expression before ‘void’
  229 |     if constexpr (!std::is_same_v<void, Result>) {
      |                                   ^~~~
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/boxing/impl/boxing.h:229:35: error: expected ‘)’ before ‘void’
/usr/local/lib/python3.10/dist-packages/torch/include/ATen/core/boxing/impl/boxing.h:229:18: note: to match this ‘(’
  229 |     if constexpr (!std::is_same_v<void, Result>) {
      |                  ^
ninja: build stopped: subcommand failed.

**Even after verifying the gcc version , cudnn version , gpu version ,python and pyTorch compatibilities , the issue is not getting resolved .
import torch
print(torch.version)
!g++ --version
2.1.0+cu118
g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
import torch
print(torch.backends.cudnn.version())
8700**
Can anyone help with the debugging of this issue?

I have the exact same issue too.
I run the code on colab and it returns this error.

I have the exact same issue too. I run the code on colab and it returns this error.

You need to rebuild raymarching from scratch and then run the env again after installing packages, it will work , there might be some new version issues / compatibility issues because of which this issue occured

Same issue too, I noticed that "error: #error C++17 or later compatible compiler is required to use PyTorch.", and I am trying to resolve it

Change raymarching/backend.py, Line 7 & 13 and raymarching/setup.py, Line 8 & 14, "c++14" -> "c++17", and recompile it by  python setup.py build_ext --inplace && pip install .
Same operation for gridencode, shencoder, and freqencoder

Change raymarching/backend.py, Line 7 & 13 and raymarching/setup.py, Line 8 & 14, "c++14" -> "c++17", and recompile it by  python setup.py build_ext --inplace && pip install .
Same operation for gridencode, shencoder, and freqencoder

it works! thanks a lot

Change raymarching/backend.py, Line 7 & 13 and raymarching/setup.py, Line 8 & 14, "c++14" -> "c++17", and recompile it by  python setup.py build_ext --inplace && pip install .
Same operation for gridencode, shencoder, and freqencoder

I searched a lot of web pages to solve this problem, thank you very much for the solution, it works for me!


Bug: Run app crashes when jogging during labware calibration

Currently, the run app sometimes crashes when jogging during labware calibration
Issue
Expected: when calibrating tip to labware, user should be able to jog pipette
Observed: Pipette does not respond to jog buttons. App crashes when closing jog modal.
Environment:
Run App: v3.0.0-mac-2018-02-07_20-18-v3a-3210538
Protocol:
Serial_dilution_OT2_ekker_v2.txt

Unable to recreate


Multibranch Pipeline Jobs

I was looking to use this library for various interactions with Multibranch Pipeline Jobs in Jenkins.  After some initial investigation I haven't been able to get this working.  Is this a supported capability, for example, can I trigger a build of a specific branch?
Happy to create a PR for this if its not currently supported.

Hi Danny - I haven't been doing any work on this repo, so a PR would be welcomed and is really the only way this feature will get added. Cheers!

It'd be great to see multibranch pipeline support.


Add unit tests to increase coverage

Signed-off-by: Jonathan Marcantonio<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/24971
/hold

/unhold


Update dependencies

Update glocaltokens to 0.6.2.
Update minimum required HA version to 2022.2.0.
Remove unused entries from hacs.json.
Update contributing documentation.

Fixes https://github.com/leikoilja/ha-google-home/issues/453

oh wow, amazing stuff going on here. Took the weekends off the laptop, much stuff has happened! :D
Thank you, @KapJI, for holding up the fort and doing all the amazing fixes!


Keep input event as unhandled if they go through a control set to MOU…

I had that issue where I wanted to be able to drag&drop things onto a game view. To do so, I tried put a control set to MOUSE_FILTER_PASS on top of my world, expecting that all unhandled mouse event would end up being processed by _unhandled_event, turned out it wasn't the case. Basically, as soon as an event is given to a Control somewhere, the event would be considered as handled if it went through a control with MOUSE_FILTER_PASS or MOUSE_FILTER_STOP.
However, I think it is not expected that an event which went through Controls set to MOUSE_FILTER_PASS ends up as handled if it wasn't explicitly set as handled.
As a consequence, what this PR does is simply set a mouse event as handled only if it it was stopped by a control. If the event reaches the root going only through controls set to MOUSE_FILTER_PASS or MOUSE_FILTER_IGNORE (and is not set as handled explicitly), then the event is now passed to the _unhandled_event processing.

Obsolete edit
while investigating this issue, I ended up with other problems that I tried to fix too:

There was a mistake in this line of _gui_call_input(...) :

bool ismouse = ev.is_valid() || Object::cast_to<InputEventMouseMotion>(*p_input) != nullptr;

The ev.is_valid() part was always true, which caused all events, even keyboard ones, to be stopped while climbing up the tree if the Control had the filter set to MOUSE_FILTER_STOP. This does not seemed like an intended behavior.

~~Scroll wheel events were unstoppable. It was not much of an issue when those event were not forwarded to _unhandled_input, but with this PR, it became quite annoying. So I removed this special case (as ScrollContainer is already set to MOUSE_FILTER_PASS by default anyway). It is debatable whether or not this change is welcome, as it means that we would need all containers in a hierarchy to be set as to use the MOUSE_FILTER_IGNORE or MOUSE_FILTER_PASS modes so that the event can climb up the tree. Maybe an alternative would be to add another mode, set by default, that would allow those specific events to pass? Like MOUSE_FILTER_STOP_BUT_SCROLLS (bad name, I have to admit ^^)?

Alright, I had to modify a little bit the PR:

Events that are not stopped still correctly go to _unhandled_input. This initial work caused issues, as scroll events were always passed, even with the MOUSE_FILTER_STOP filter. (I had no way to stop those events, thus scrolling in a ScrollContainer caused the event to be handled by _unhandled_input, and, in my case, it caused my camera to zoom in/out)
To solve this, I added a mouse_force_pass_scroll_events. It allows you to still allow scroll events to be passed up the tree even when  using the MOUSE_FILTER_STOP filter. It is enabled by default. The property is grayed out if the mouse filter is not set to MOUSE_FILTER_STOP as it is useless in those other cases.
Still fixed the bug on  that wrong line bool ismouse = ev.is_valid() || Object::cast_to<InputEventMouseMotion>(*p_input) != nullptr;

Might fix https://github.com/godotengine/godot/issues/17326 and https://github.com/godotengine/godot/issues/57349

Ah wait, it seems there's a bug with release events, which might not end up in _unhandled_input in some cases.

Alright, I had to modify the PR to avoid some issues but it made me discovered other. See the original post.

Might fix #17326 and #57349

From what I can see from the code change, I am quite confident, that this PR will not fix #17326.

From what I can see from the code change, I am quite confident, that this PR will not fix https://github.com/godotengine/godot/issues/17326.

Well, I relied on what you said on that PR: https://github.com/godotengine/godot/pull/57894, where you said that "
Since the event is internally marked as handled, _unhandled_input is never called.".  This PR does make it so that event is passed to to _unhandled_input correctly, I supposed it would solve the associated issue.
But maybe I am wrong, I don't know, I haven't checked whether or not the PR solved the issue.

Boolean arithmetic ... You are right, I misread your code. This PR might change the event behavior, so that the symptom which causes #17326, is mitigated.
I believe, that #57894 is still necessary. With your changes applied I can provide a use-case where Mouse-clicks now are used up by a Control-Element, that is located behind a SubViewportContainer, while the user would expect, that it should be consumed inside the SubViewport. After this gets merged, I will have to update the description of my PR.

I believe, that https://github.com/godotengine/godot/pull/57894 is still necessary. With your changes applied I can provide a use-case where Mouse-clicks now are used up by a Control-Element, that is located behind a SubViewportContainer, while the user would expect, that it should be consumed inside the SubViewport. After this gets merged, I will have to update the description of my PR.

Yeah that makes sense.

Thanks!

Does this supersede #54656?
Does this solve any of: #55430, #55432, #54529?
CC @golddotasksquestions

Does this solve any of: https://github.com/godotengine/godot/issues/55430, https://github.com/godotengine/godot/issues/55432, https://github.com/godotengine/godot/issues/54529?

I feel that this PR might fix all of them. Makes me wonder if it would be worth a cherry-pick for 3.x


Minimal dataset to test BUSCO on human test data in --offline mode.

In order to run, BUSCO either downloads large reference data files, or can read from local drive when started in --offline mode.  The purpose of this pull request is to provide a file that allows us to test this offline mode.
BUSCO screens a genome for hits in a "lineage dataset", which have a compressed size of many megabytes.  The human sequence data in this repository (homo_sapiens/genome/genome.fasta) match a single entry of the primate lineage dataset (primates_odb10.2021-02-19.tar.gz).
In the file submitted here, I removed all the non-matching entries of the primate dataset, resulting in final size of 48 KiB.  I have verified that it can be used to test BUSCO modules in less than 2 min.

@charles-plessy you also need to add a description in the README file: https://github.com/nf-core/test-datasets/blob/modules/README.md


BA for Tensorflow

Implementation of BA for TensorFlow

I reverted the merge from main because it presented a new issue with diffsharp?

That's a transient issue with DiffSharp, which is flaky. It's unrelated to any changes in the main branch.

The commit c45de3903c8108d2d0a91ac4640630e5739653ec seems to have messed up the Git history so I'm force-pushing to 437b6de89521974f8b9469aeb554bf068827f0dc.


Need to handle importing raw baker secret keys into Helm more securely

This is especially important for users joining public networks. Standalone Helm does not seem to provide good functionality for this.
See: https://github.com/jkroepke/helm-secrets

https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/
https://blog.aquasec.com/managing-kubernetes-secrets
There are cloud provider encryption tools like for AWS:
https://github.com/kubernetes-sigs/aws-encryption-provider


Remove listener default value for Port

The logic for Set Host checks whether Port has been manually specified. If it has, the port remains unchanged. Unfortunately, it means that a user who specifies Set Host https://<IP_ADDRESS>:443 during new listener creation will always have to specify the Port manually; the default value ensures Port is always set.
This PR removes the :Port from the default value for Host and the default value for Port. Now, by specifying Set Host https://<IP_ADDRESS>:443, both values will be set appropriately.
The only negative outcome of this that I can see is users who are accustomed to not specifying either Host or Port when creating a listener.

@leesoh I see that you've changed the default values for each listener according to your description but you didn't include any logic to handle setting the port

The port would be set as it is now using existing code (set Port 443, set Host https://<IP_ADDRESS>:443), no?

@leesoh Ah, I think I misunderstood what you were trying to do. Thanks for this!


I corrected a mistake in the DCT notebook.

I discovered a mistake in the DCT.ipynb.  Previously, the example of 1-dimension DCT production seems to suggest that higher precision leads to worse approximated function. It turns out that this was due to an error in code. Now, higher precision leads to better approximation of the function.

Seems there is still a problem. Let me further debug it.


Flipped Residual Connection

Hello,
Thank you for your amazing work!
From the paper, the last line in the Vim Alogirthim is as follows:
$T_l$ : (B, M, D) ← $Linear^T$ ( $y_{forward}$ + $y_{backward}$ ) + $T_{l−1}$
From the code the backward process is the same as the forward, just the input sequence is flipped. However, the input token sequence (residual) is added to the forward+backward output, but should the flipped token sequence be added as an residual as well, such as:
$T_l$ : (B, M, D) ← $Linear^T$ ( $y_{forward}$ + $y_{backward}$ ) + $T_{l−1}$ + $T_{l−1 flipped}$

Edit:
I also noticed each "v2" Mamba block contains out_a and out_b, which is both forward and backward, but in the for loop here, we process two Mamba blocks at the same time, each has its out out_a and out_b, but the input for the second Mamba Block is flipped, which is qutie confusing, does that mean the flipped input for the second Mamba Block is not related to Mamba Block itself and mroe of a training mechanisim? Meaning, if the for loop processes one layer at a time, wouldn't a Mamba Block do a forward and backward SSM pass?
Thank you!

I also noticed each "v2" Mamba block contains out_a and out_b, which is both forward and backward, but in the for loop here, we process two Mamba blocks at the same time, each has its out out_a and out_b, but the input for the second Mamba Block is flipped, which is qutie confusing, does that mean the flipped input for the second Mamba Block is not related to Mamba Block itself and mroe of a training mechanisim? Meaning, if the for loop processes one layer at a time, wouldn't a Mamba Block do a forward and backward SSM pass?

From my understanding, the addition of an extra reverse scan for the Vision Mamba is a compromise by the author due to it not being a natural temporal signal. The term "flipped input for the second Mamba Block" refers to this reverse scanning process, while reusing the same block code.
What's truly confusing is the uncertainty surrounding the input and output of the Vision Mamba block. The descriptions in the code seem to contradict those in the paper. The paper mentions two linear transformation layers in the front part of the block (corresponding to lines 3 and 4 of Algorithm 1), but there is no corresponding implementation in the code. If you understand this clearly, perhaps we can discuss it further.
Lastly, the implementation of fused_add_and_norm by the author also adds complexity to understanding the code.

I also noticed each "v2" Mamba block contains out_a and out_b, which is both forward and backward, but in the for loop here, we process two Mamba blocks at the same time, each has its out out_a and out_b, but the input for the second Mamba Block is flipped, which is qutie confusing, does that mean the flipped input for the second Mamba Block is not related to Mamba Block itself and mroe of a training mechanisim? Meaning, if the for loop processes one layer at a time, wouldn't a Mamba Block do a forward and backward SSM pass?

I found the same problem, kick me if you find sth. else

@jsrdcht if_bidirectional is set as False and  flip_img_sequences_ratio is set as -1, thus, the input is process normally as forward and backward "v2" here. Hope that helps!

@jsrdcht if_bidirectional is set as False and flip_img_sequences_ratio is set as -1, thus, the input is processed normally as forward and backward "v2" here. Hope that helps!

Thanks a lot! I think you are right. However, there is still one issue about the depth of the model.
Why the default depth is 24 in the sense of small/tiny model if it's not for bidirection? I mean, considering the ViT/small sets it to 12.

@jsrdcht The model itself is bidirectional, and can be found here. The if_bidirectional  parameter being False just ensures that we do not use this loop. So with if_bidirectional being False and flip_img_sequences_ratio as -1, the input is fed here directly, which goes to v2 (the first link in this comment). The small and tiny do not differ in depth, but differ in the hidden state dimension (3.4. Architecture Details in the paper).

@AliYoussef97 Yeah, I agree with you.

The small and tiny do not differ in depth, but differ in the hidden state dimension (3.4. Architecture Details in the paper).

That's not my point. Based on what you just mentioned, so each Vision Mamba block implements both forward and backward modules internally, can we simply compare each mamba block to a transformer block?
In the configuration of vision transformer small, the depth is 12 (possibly even lower), while for vision mamba it is set to 24. Assuming if_bidirectional is True, 24 can be interpreted as having two types of blocks. How should we understand this default parameter of 24 if if_bidirectional is False?

@jsrdcht The linked repo is not the official implementation, thus I am not quite sure why the depth is 12, but by default, the paper states the difference is in the Hidden state dimension. if_bidirectional  is related to the ablation study in the paper, and should be False from my understanding.


operator: change matchLabels of operator deployment

The matcher includes the label "name: controller-manager". This differs from what we set in MTV (there 'name' is mapped to 'forklift-operator') and this can lead to errors when creating a new release of MTV.
Here we change the aforementioned label to match that of MTV. This change would break upgradea to Forklift 2.7.0, however, there is an easy workaround for this by removing the custom resource 'forklift-controller' of type ForkliftController from the namespace the operator is deployed on.

why not revertin https://github.com/kubev2v/forklift/pull/313 if we go in this direction?

why not reverting #313 if we go in this direction?

it's possible to change the other labels (even though some of them are better be dropped..) but that's a different kind of change, this change solves the misalignment between Forklift and MTV

Is it the only misalignment between the forklift and MTV which requires the forklift-controller recreation?
If we want to unify it and force users to recreate the forklift-controller we should do all possible changes at once.

typo in the commit upgradea -> upgrade

I think this change is still needed but I have no time to work on this anymore, therefore closing


Dev2

features: accounts models and routes
planning to migrate to auth0 for authentication
temporarily disabled auth on route methods

merging. thank you :)


[dev] netlify dev error

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
getting error when running netlify dev
- If the current behavior is a bug, please provide the steps to reproduce.
created a brand new project using the deploy to netlify button. Installed netlify cli using npm install netlify-cli -g
- What is the expected behavior?
run dev server
- Error
◈ Netlify Dev ◈
◈ Starting Netlify Dev with create-react-app
◈ Function builder netlify-lambda detected: Running npm script build:lambda
 ›   Warning: ◈ This is a beta feature, please give us feedback on how to improve at https://github.com/netlify/cli/
yarn run v1.17.3
$ react-scripts start
Error: Command failed with exit code 1 (EPERM): yarn run build:lambda
    at makeError (/usr/local/lib/node_modules/netlify-cli/node_modules/execa/lib/error.js:58:11)
    at handlePromise (/usr/local/lib/node_modules/netlify-cli/node_modules/execa/index.js:112:26)

- Local Environment Information
Paste the results of netlify status --verbose here
──────────────────────┐
 Current Netlify User │
──────────────────────┘
Name:  Rishabh Tayal
Teams:
  Rishabh Tayal's team: Collaborator

────────────────────┐
 Environment Info   │
────────────────────┘

  System:
    OS: macOS 10.15
    CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
  Binaries:
    Node: 10.16.3 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.11.3 - /usr/local/bin/npm
  Browsers:
    Chrome: 76.0.3809.132
    Safari: 13.0

────────────────────┐
 Netlify Site Info  │
────────────────────┘
Current site: brave-agnesi-ba6ba2
Netlify TOML: /project/netlify.toml
Admin URL:    https://app.netlify.com/sites/brave-agnesi-ba6ba2
Site URL:     https://brave-agnesi-ba6ba2.netlify.com
Site Id:      aabafbd2-136e-4492-817a-102b7ccc2658

Does the project have netlify-lambda installed as a dependency?
try
npm install netlify-lambda
netlify dev

I see the dependency in there https://github.com/RishabhTayal/mailgun-dashboard-v2/blob/master/package.json#L29
npm install

Then
netlify dev

Let me know if you are still seeing the issue 😃

nah the issue is that he’s running it twice because of function builders and npm run all and netlify lambda fails when that happens. this is the kind of thing i worry about with function builders. however in this case we can modify netlify lambda to check if it has an instance running already.

Hi, today I run into a similar problem on one of my computer. I can't run ntl dev.
The error is as below:
C:\!Others\netlify-site>ntl dev
◈ Netlify Dev ◈
◈ Starting Netlify Dev with create-react-app
◈ Function builder netlify-lambda detected: Running npm script build:lambda
 »   Warning: ◈ This is a beta feature, please give us feedback on how to improve at https://github.com/netlify/cli/
yarn run v1.22.4
$ react-scripts start
Error: Command failed with exit code 1 (Unknown system error -1): yarn run build:lambda
    at makeError (C:/Users/ikena/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/execa/lib/error.js:59:11)
    at handlePromise (C:/Users/ikena/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/execa/index.js:112:26)
    at async DevCommand.run (C:/Users/ikena/AppData/Roaming/npm/node_modules/netlify-cli/src/commands/dev/index.js:463:9)
    at async DevCommand._run (C:/Users/ikena/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/@oclif/command/lib/command.js:43:20)
    at async Config.runCommand (C:/Users/ikena/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/@oclif/config/lib/config.js:172:9)
    at async Main.run (C:/Users/ikena/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/@oclif/command/lib/main.js:22:9)
    at async Main._run (C:/Users/ikena/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/@oclif/command/lib/command.js:43:20)

After some testing, I found that it is caused by the fact I put my repo in a folder starting with "!".
Actually, yarn duild will reveal this issue:
C:\!Others\netlify-site>yarn build
yarn run v1.22.4
$ run-p build:**
$ react-scripts build
$ netlify-lambda build src/lambda
netlify-lambda: Building functions
WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.context: The provided value "C:\\!Others\\netlify-site\\src\\lambda" contains exclamation mark (!) which is not allowed because it's reserved for loader syntax.
   -> The base directory (absolute path!) for resolving the `entry` option. If `output.pathinfo` is set, the included pathinfo is shortened to this directory.
 - configuration.output.path: The provided value "C:\\!Others\\netlify-site\\built-lambda" contains exclamation mark (!) which is not allowed because it's reserved for loader syntax.

But ntl dev doesn't.
After moving the repo to a different folder, everything works.
I'm not sure if it's related to OP's issue, but regardless I hope this information can help you guys improving Netlify CLI tool.

Closing this as stale.
Regardless, netlify dev used to hide lambda build errors. This was fixed in https://github.com/netlify/cli/pull/988

What about on Android?


Frame didn't arrived within 5000 when datetime is changed

Required Info

Camera Model
D400

Firmware Version
<IP_ADDRESS>

Operating System & Version
Raspbian GNU/Linux 9.6 (stretch)

Kernel Version (Linux Only)
4.14.79-v7+

Platform
Raspberry Pi.

SDK Version
2.12

Language
C

Segment
others

Issue Description
Frame didn't arrived within 5000 when datetime is changed.
when we start the sensor, eg rs-distance and update the RPI datetime, if datetime is drifted and updated, the program crashes.

some one facing same?

for Raspberry Pi, when doing cmake, you need to add the -DFORCE_RSUSB_BACKEND=ON
by the way, the SDK  is pretty old, would suggest you to upgrade SDK and firmware
the latest SDK version is 2.38.1 firmware is <IP_ADDRESS>

Its still crashing when date is changed during streaming with the flag compiled.

@kamadhenu87 How do you change the date? Could you please provide an example? And it seems not normal case to change date time during streaming? Could you please elaborate more why you need such operation during streaming? Thanks!

We have object detection product(device) processing the received frames, but the device has RTC that can be changed? If the device CMOS battery fails the RTC will goto to wrong date, so when we set RTC(date and time) during streaming, the application stops with exception

Same observation with latest SDK librealsense-2.38.1 also on
RPI4 with kernel 5.4.51-v7l+and Raspbian GNU/Linux 10 (buster)

@kamadhenu87 There're error checks in rs-distance such as https://github.com/IntelRealSense/librealsense/blob/master/examples/C/distance/rs-distance.c#L84. When the date changed, error detected and the program crashed.  Is it possible for you to stop the streaming before change the date?  Or you can comment those error checks to get the program running but not suggested as all the errors check also ignored in this case.


Respec not workin (for player or companions)

Description of the bug
Trying to respec any of the characters, the game simply freeze and when you try to click on the plus to re-create the character (player or companion), the game itself seems blocked.
Didn't give trouble until latest release (09/06/23).
Steps To Reproduce

Open Toybox
Go to "Party"
Click on "Respec"

Expected Behavior
When respeccing, the game won't freeze anymore.
Log Files
GameLogFull.txt
Player.log
Save File
Manual_4_Neathholm__16_Arodus__VIII__4715__12_11_44.zip
Screenshots
No response
Settings
Settings.zip
Toybox Version
1.5.3
Operating System
Windows 10 Version 22H2
What game are you using Toybox on?
Pathfinder Wrath of the Righteous
Game Version
2.1.4w
Anything else?
No response

Hi and thank you fo your reply,
I'd like to thank you for your hard work and your assistance, which i think
is not for granted.

The version i'm using is the one that was updated on the 9th of June,
which i presume is the latest; the Unity Mod Manager tells me that it is
the 1.5.3... If there's a new version avaliable, can you please tell me
what's its code and where can i find it? Thank you a lot!
Ok, so how can i help to resolve the issue?

Thank you again and kind regards,
Giovanni Filardi
Il dom 11 giu 2023, 00:43 xADDBx @.***> ha scritto:

1.5.3 is an outdated version and you should update since the newest
Wrath version broke some older builds.
Please confirm whether this also happens on the newest build
2.
I didn't think that was the case but it seems like this might really
be a ToyBox issue[image: image]
https://user-images.githubusercontent.com/62178123/244898113-bf03377c-685a-46b5-bb5c-6b0ef5bb371a.png
—
Reply to this email directly, view it on GitHub
https://github.com/cabarius/ToyBox/issues/977#issuecomment-1585839972,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAO5JRA5UBYLLB65ARICYFTXKTZ7XANCNFSM6AAAAAAZBWAPEA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, thank you, i'll check it first thing in the morning (i'm in Italy
and right now it's 02:32 am) and install it.

Thank you a lot and kind regards,
Giovanni Filardi
Il dom 11 giu 2023, 02:29 xADDBx @.***> ha scritto:

The newest is 1.5.4c, and it's available on Nexusmods.
If it's not working on the newest version, then you'd probably help
by testing builds that we create to try and fix the issue.

—
Reply to this email directly, view it on GitHub
https://github.com/cabarius/ToyBox/issues/977#issuecomment-1585873059,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAO5JRATT6SALQDPQH3M4SDXKUGNLANCNFSM6AAAAAAZBWAPEA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Good morning,
i could download the 1.5.4c version and for the moment, it seems to work
just fine.
Thank you very much and sorry to have wasted your time...
Il dom 11 giu 2023, 02:33 Giovanni Filardi @.***> ha
scritto:

Ok, thank you, i'll check it first thing in the morning (i'm in Italy
and right now it's 02:32 am) and install it.

Thank you a lot and kind regards,
Giovanni Filardi
Il dom 11 giu 2023, 02:29 xADDBx @.***> ha scritto:

The newest is 1.5.4c, and it's available on Nexusmods.
If it's not working on the newest version, then you'd probably
help by testing builds that we create to try and fix the issue.

—
Reply to this email directly, view it on GitHub
https://github.com/cabarius/ToyBox/issues/977#issuecomment-1585873059,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAO5JRATT6SALQDPQH3M4SDXKUGNLANCNFSM6AAAAAAZBWAPEA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Key definitions do not resolve in a topic referenced by the copy-to attribute

Topics inserted into a map for subsequent occurrences using the

attribute do not resolve key definitions contained in the copy-to
topic c_topic_subsequent.html although the key space for the key definitions is properly specified.
The key definitions in the copy-to topic output do not appear in either PDF or webhelp.
Please advise.

This is for DITA OT 1.8, right? Have you tested with DITA OT 2.0?

I thought I reported this issue recently. The problem is that copy-to processing is applied before the key definitions are handled, so the copy-to processor doesn't know that the topicref indirects through a key (or rather, it couldn't resolve the key reference even if it wanted to).
The workaround is to define a separate key definition that specifies the copy-to and then refer to that key from the navigation topicref.
I don't think this is something that can or should be fixed until the preprocessing is completely re-thought to handle DITA 1.3 requirements.

Sounds like a duplicate of #1861.


Speech Rule Engine and Commas

I'm using the AM_SVG configuration with math that is normal numbers with commas as the "thousands" separator.  1,234,567 is read as "one comma two hundred thirty four comma five hundred sixty seven".  I'm surprised that it's not ready "one million two hundred thirty four thousand five hundred sixty seven".  I'm not sure if I should report this here or over at the SRE project (or if I should do this a different way or if it's configurable).

This is the correct rendering for 1,234,567, which MathJax (and TeX) treats as a list of three numbers, 1, 234, and 567.  To get what you are looking for, you must use 1{,}234{,}567 as you would in TeX to get a single number rather than a list.  How that number with commas is actually spoken may depend on the screen reader you are using.  @zorkow, is there anything more to be said, here?

I am locked into AsciiMath.  Is there an AM equivalent to your TeX solution?
On Tue, Nov 6, 2018 at 2:39 PM Davide P. Cervone<EMAIL_ADDRESS>wrote:

This is the correct rendering for 1,234,567, which MathJax (and TeX)
treats as a list of three numbers, 1, 234, and 567. To get what you are
looking for, you must use 1{,}234{,}567 as you would in TeX to get a
single number rather than a list. How that number with commas is actually
spoken may depend on the screen reader you are using. @zorkow
https://github.com/zorkow, is there anything more to be said, here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mathjax/MathJax/issues/2076#issuecomment-436400589,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACdpd7_-kbt1nZeWs4FPzZbxex3PhHV8ks5usfOcgaJpZM4YRNtR
.

Unfortunately, I don't know a good solution in that case.  I gave a partial answer at
https://stackoverflow.com/a/46383402/502334 <https://stackoverflow.com/a/46383402/502334>

that might be sufficient for your purposes.  To do better would require leaving some sort of marker in the math at the place where the number that has had commas removed is, and looking for that to put the comma back in (and remove the marker).  It could be done, but is clunky.
Davide

On Nov 6, 2018, at 5:41 PM, garagebrewer<EMAIL_ADDRESS>wrote:
I am locked into AsciiMath. Is there an AM equivalent to your TeX solution?
On Tue, Nov 6, 2018 at 2:39 PM Davide P. Cervone<EMAIL_ADDRESS>wrote:

This is the correct rendering for 1,234,567, which MathJax (and TeX)
treats as a list of three numbers, 1, 234, and 567. To get what you are
looking for, you must use 1{,}234{,}567 as you would in TeX to get a
single number rather than a list. How that number with commas is actually
spoken may depend on the screen reader you are using. @zorkow
https://github.com/zorkow, is there anything more to be said, here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mathjax/MathJax/issues/2076#issuecomment-436400589,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACdpd7_-kbt1nZeWs4FPzZbxex3PhHV8ks5usfOcgaJpZM4YRNtR
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/mathjax/MathJax/issues/2076#issuecomment-436435940, or mute the thread https://github.com/notifications/unsubscribe-auth/AAaajqGCeFK-06pu6MP_vPqzJj5R0Fl_ks5ushAZgaJpZM4YRNtR.

Unfortunately, I don't know a good solution in that case.  I gave a [partial answer]((https://stackoverflow.com/a/46383402/502334) on StackOverflow that might be sufficient for your purposes.  To do better would require leaving some sort of marker in the math at the place where the number that has had commas removed is, and looking for that to put the comma back in (and remove the marker).  It could be done, but is clunky.
Davide


? and !

Since Nil has a very important role in the language, we were thinking of changing the semantic of the language a bit so dealing with nils is easier and shorter.
The idea is to drop support for method names ending with "?" and "!". Instead, "?" would have the same meaning as the current Object#try, while "!" would have the same meaning as Object#not_nil!.
With this change in place we could have hash[key] always return a nilable value, and then you would write hash[key]! to get a non-nil value, raising if it's nil. So we wouldn't need to have a separate set of #[] and #[]? methods. For Array#[] I think the most reasonable thing would be to make it non-nilable with a possible raise of "index out of bounds", or we can just always stick to the convention and make #[] be nilable so you always know that #[] is nilable and #[]! might raise.
As a replacement for, for example Array#empty?, we can use Array#is_empty. For Array#map and Array#map! we can use Array#map_in_place, etc.
What do you think?

Sorry, but I don't like this at all.
The places where you actually use .not_nil! in application code seem to be rare, it's just writing the standard library were it might feel as noise. is_empty and map_in_place are terrible, verbose names.
Unfortunately I have nothing constructive to add, but I actually think that the current way isn't bad at all.

I agree with @jhass.
 And since one of the stated goals of Crystal is to look as similar to Ruby as possible, I'd keep it that way. I think we already are in the perfect sweet spot of Ruby look and Crystal-specific functionality.

Let's huffmanize this and try to discourage people from using nil and using exceptions :-)

I like this idea very much. It's basically the way Swift deals with Optionals.
If that change is too drastic for people to take, something similar would be great.
Perhaps ! and ? starting the method call?  session.user.?address.?line_one? I'd prefer the original suggestion to that, though.

@Exilor
Perhaps we come to better / different ideas than Ruby and if it fits we should not go the "Ruby Way" just because Ruby does it. Just my two cents.
As @brasten says, the "Swift Way" is nice. We should use it as well after types (prevents Object#not_nil! is spread all over the place).
hash = {} of String => String!
i :: Int!

or like Nim
hash = {} of String => String not nil

Maybe we should start RFCs like Rust ;-)

@akaufmann A big part of the appeal Crystal has is, to put it simply, "it's aaaalmost like Ruby but compiled!". The further it deviates from that, the more that appeal is lost.
It's a slippery slope. And once the language has deviated enough, why bother with yet another language that tries to reinvent the wheel?
It's very easy to pick up Crystal if you know Ruby. It's a ridiculously small learning curve. If that changes I don't know why anyone would choose to invest time in learning it instead of playing it safe and learning a more popular language.

@Exilor Crystal resembles Ruby because we like the design and philosophy of the language, but it doesn't pretend to be in any manner a drop in replacement. There are too many things already that are different and most of the differences come from the fact that Crystal is a compiled and strongly typed language. The treatment for the nilable variables is one of these differences and I believe one of the strongest points in Crystal. So for me it is reasonable that the primitives for handling these values are tight very deep in the language already.

@akaufmann Sort of that feature is already present in Crystal:
getter! foo

When you call foo it will raise if @foo is nil. Of course the difference is that in Swift can access the instance variable and get the assertion anyway.

@waj It may not be intended to be a drop-in replacement but I firmly believe that whatever (modest) interest it has garnered so far is mostly thanks to its similarity to Ruby. Pardon the harshness, but in my opinion it's Crystal's greatest asset and without it there's not much else that makes it stand out.

@Exilor Don't get me wrong. I love Ruby as well Crystal. But I also love other languages (Rust, Swift, ...). They have also good ideas. I don't think a few difference here and there keeps People away. You can say the opposite as well: Why should Ruby Programmer care about Crystal? Just because it is faster (nah, there are great feature in crystal)? If it has some more great features, what ruby does not have, maybe they are more impressed. For example, I don't like Ruby's Object#freeze method. I hope that Crystal don't implement it. I hope let for immutable variables will come.
@waj I know, but not for local variables :-)

To give some more context about this discussion, when we started developing Crystal and decided that we wanted to explicitly deal with Nil, we knew that we would have to have a way to say "this is not nil, raise if so" and "do this only if it's not nil (otherwise do nothing)". But since "!" and "?" were already taken we used "try" and "not_nil!" as the initial placeholders.
Yesterday we were toying with Swift (not because of this), and we learned how they deal with nil. So @waj suggested that we could do the same. I told him that we could maybe do that, but that I wasn't entirely sure. But, we could ask the community to have more opinions and a better way to decide.
As for me, I wouldn't make the change for these reasons:

It's not used enough to justify a whole special syntax for it. In the whole Crystal repository (including src, samples and spec) I find 192 occurrences of not_nil! and 242 of try. The whole repository has 98060 lines of code right now. That's a %0.4. In DeBot I found 18 not_nil! and 9 try! (in about 4000 lines). In prax.cr I found 1 not_nil! and no try (in about 1000 lines). Most of the not_nil! might probably be hidden behind a property!, but that's perfectly fine: an idiom that covers this case, without the need for a special rule in the language. Other nilables might be hidden behind if, but that's again perfectly fine, and a nice way to deal with nil without an explicit syntax. And, as we can see (or at least the numbers say so), nil is not as pervasive as we might think.
It adds more rules to the language. Right now try and not_nil! are regular methods: they have documentation, you can see their implementation. If we want to change the message raised by not_nil! we can go to this line and change it. If it's a rule buried in the language it must be documented somewhere else, and nobody can change it (of course, we could make "!" and "?" rewrite to regular methods, but what would be the point then?). Granted, people will have to learn about try and not_nil! eventually, but they are just regular methods, not something special.
It breaks some of the Ruby feeling that the language has. If I write if array.is_empty it doesn't feel right for me. Maybe it's just because I'm used to that, but so are the many Ruby programmers that might stumble upon this language.
It would make things a bit inconsistent. Right now #[] raises and #[]? returns nil, always. By not having a #[]? method (just #[]) we would have to make it be nilable. But in Swift for arrays it raises, so that's an inconsistency. What if I want to get an element in an index or nil if it's not there? Maybe use another name, like "fetch" or "at", but... I don't like inconsistencies, as they always make you think twice.

In short (well, long), I think the benefits would be very small.
But I was surprised to find out that many actually think that Swift's way can actually be a good thing (that is, for Crystal). So @waj is definitely not alone here.
I guess we can continue discussing until we find more convincing reasons to do or not to do this feature.
@akaufmann I like the idea of RFCs. I think just creating an issue with [RFC] on the title is enough for now :-)

I actually have another reason :-)
Right now if you do hash[key] and the key is not found, you get a "Missing key in hash" error message, which is much more descrptive than "nil assertion failed". That is, one can choose how to implement #[] and #[]? (and other raise/nil method pairs) to provide better error messages, and also giving an opportunity to make the ? method more efficient. For example this method does that, and it could also be improved by not creating a Function object (although in this case there's no difference because Function is a struct).

I'd be very sad to see #empty? and other #blank? or #any? methods go away. It may be my favorite little Ruby tweak :)
I also like the fact that Crystal is more harsh by raising when [] would be nil or is out of bounds. Your code failed because you expected something that wasn't there, instead of failing later because of a nil. I think I like []? too for checking existence, but I never used it yet.

This is a very interesting discussion, but one that seems to assume most crystal code will have to deal with lots of Nil. I think we should try to avoid that :-) (and indeed, @asterite's numbers seem to go that way).
I'm not "in love" with marks in method names, I'm just arguing against it because I'd like Nil to be almost-unexistant in most code bases :) (and so don't want to sacrifice 2 very useful punctuation symbols to it)

Yes, @vendethiel !

As a side note, both @waj and I agree that not_nil! is an ugly name, so any suggestion for a better name (if we finally retain it) is very welcome :smiley:
We thought of unrwap, but that would be more appropriate for an Optional type. Here it's just a union of Nil and other types, so that name probably doesn't make sense.

It adds more rules to the language. Right now try and not_nil! are regular methods: they have documentation, you can see their implementation.

This is probably the best reason not to turn ? and ! into special operators, in my opinion.  I don't love the Ruby-style method? and method! conventions, but I do like the design of having as few keywords as possible and representing everything as objects and methods, including operators.
Also, it seems like disallowing ! and ? in method names would complicate things, considering ! is a method that can be changed to redefine negation.  (Odd thing I noticed:  Crystal only allows calling it as !x, but in Ruby you can call it as !x or x.!.  Is that a bug in Crystal?)

As a side note, both @waj and I agree that not_nil! is an ugly name, so any suggestion for a better name (if we finally retain it) is very welcome

I can't think of anything better; it may be ugly but it's also pretty self-explanatory.  The only other thing I can think of would be to allow ? as a method name and do Object? or Object.? instead of Object.not_nil!.  I think that would look better in code (especially the former), but I have a feeling it would be a bad idea because of things like the ? : operator and maybe a lack of consistency with how ? is used elsewhere.

I think Object? already says that this is a nilable union type: Object | Nil.

I think Object? already says that this is a nilable union type: Object | Nil.

Really?  Didn't see it in the Object API page anywhere, and I got syntax errors when I checked with a quick empty class test, so I thought it was unused.  Tested with this:
class A
end
a = A.new

Trying to use A? gave an unexpected token: EOF message, and a? gave undefined local variable or method 'a?'.

Types have a separate grammar, and that grammar is only available in a few places: type restrictions, generic type arguments and variable declaration. So for example:
Array(String?).new # ok
String? # error

def foo(x : String?) # ok
end

Array(String*) # ok, pointer to string

def foo(x : String*) # ok
end

We could remove this and always use full names everywhere (for example you'd have to write Pointer(Int32) instead of Int32*), but I think that would make C bindings much harder to read and write. Also, | is a "bitwise or" operation, but in the type grammar is a union. So:
String | Int32 #=> undefined method '|' for String:Class
Array(String | Int32) # ok

Again, this could be changed so that you'd have to write Array(Union(String, Int32)), so things are more consistent, but it will greatly affect readability, I believe. There's also the type grammar for Int32 -> Int32, which one can also write as Proc(Int32, Int32). And also {Int32, Char}, which is Tuple(Int32, Char).

I see.  I didn't even think of testing it in types, my head's still in "everything is an object" so I just went looking for methods.  If ? as a method isn't feasible because of that, then I'm at a loss for a better suggestion than not_nil! unfortunately.  Oh well.

As a complete non-Rubyist (@Exilor - Crystal is an excellent language, that's why I like it (C++er)) I've come to really like this style of, "duck-wording", especially dangerous!(foo) is a really smart practise I think. Like @vendethiel mentions: mutation is bad; but sometimes it's a performent necessary evil - and then it's better to have a convention for naming, so the danger is obvious at the call site. I'm very used to foo.is-empty(), foo.isEmpty() and similar wordings from other languages, but same here: must say I like the look of foo.empty?.
As for the foo.not_nil!, it's not impossible to at least shorten it foo.nonil! or something to make it more 'keywordish/operatorish' (compare elsif). It's nice if all "language central" constructs can be free of underscores, or well, as terse as possible, and stay lean and mean. It gets mind share.
And the very important question @jhass already raised, which seems to have its answer in @asterite quick checks: there doesn't seem to be enough actual uses in practise to warrant special syntax.
But for Maybes and Optionals, the questions might be re-raised..
In type annotations ? feels super natural for meaning | Nil, but that's another thing.

As a side note, both @waj and I agree that not_nil! is an ugly name, so any suggestion for a better name (if we finally retain it) is very welcome

Relying on the fact nil value means non-existing value, I propose the next replacement for #not_nil!

#exists!

! symbol is necessary because method can produce exception

perhaps the ActiveSupport idea of #present?
On 25 July 2015 at 11:13, Sergey Kucher<EMAIL_ADDRESS>wrote:

As a side note, both @waj https://github.com/waj and I agree that
not_nil! is an ugly name, so any suggestion for a better name (if we
finally retain it) is very welcome
Relying on the fact nil value means non-existing value, I propose the
next replacement for #not_nil!

#exists!

! symbol is necessary because method can produce exception
—
Reply to this email directly or view it on GitHub
https://github.com/manastech/crystal/issues/406#issuecomment-124831607.

--
<EMAIL_ADDRESS>

or  perhaps:
if val.some?
    p val.some!  # instead of not_nil!
end
p "Has no value (nil)"  if val.none?   # similar to is_empty? (rather is_nil?)

"none" goes with the notion that nil is not really a value, but rather Nil is bottom type.

Ok...
I'm not really a Ruby user, but I love Crystal, and I have come to love the ? and ! characters for method names.
Also:

If something can throw an exception (like not_nil!), I want it to be explicit. Not that short.
The ? suffix is great for boolean attributes.

+1 for #some! and #none?, instead of #not_nil! and #nil?

What about .?
Examples:
foo.?.bar.baz would be equivalent to foo.try &.bar.baz
foo.?.bar.?.baz would be equivalent to foo.try &.bar.try &.baz
Short circuit functionality is required, just like try.  If bar is nil in the first example, baz should never be attempted.

I like @technorama 's idea. Just a small twist, why not skip the dot after question mark:
foo.?bar.baz
foo.?bar.?baz

Pretty much "reverse" of the common a?.b?.c pattern - but works for Crystal, since ? can't be used as initial identifier part.

@ozra It looks like part of the method name.   bar? is a name but ?bar is something else entirely is hard to explain to users.

@technorama - yeah, that's a good point.

Not a ruby user, but I like the ? and ! at the end of method names. Adding custom behavior for these symbols would make the code less readable.
As @sergey-kucher said,

+1 for #some! and #none?, instead of #not_nil! and #nil?

I'm closing this. One problem @waj noted with Swift is that ! ends the program abruptly. Now, we could do the same in Crystal, but maybe a better way, so users can redefine the meaning, is to make ! invoke not_nil!. But if that's the case then it's probably better just to be explicit here and type not_nil!. Also, ! is so easy to type you feel more tempted to use. not_nil! looks ugly, so you are actually tempted to avoid using it, which is good.
Then there's the conflict with current methods ending with ?, so I'm closing this issue for now.


Need 24.2 latest base image update

Latest 24.2 build is released. Could you please update 24.2 LibreOffice base image in Docker file.
I have attached the bug and release link here.
Bug : https://bugs.documentfoundation.org/show_bug.cgi?id=155444
Release link: https://wiki.documentfoundation.org/index.php?title=ReleaseNotes%2F24.2&type=revision&diff=730913&oldid=730903

@vladholubiev could you please help on this.

It would be wonderful to see 24.2 version of Libre Office integrated!

@palanisamy-emis I submitted a PR for Libreoffice 24 + node20 https://github.com/shelfio/libreoffice-lambda-base-image/pull/44 . Hope that helps you out!


update(plugins): deprecate Font Variant Numeric

Name
Link

Font Variant Numeric
https://github.com/philippbosch/tailwindcss-font-variant-numeric

Font Variant Numeric is natively supported since v1.8.0

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] I have read and followed the contribution guidelines

Good looking out, thanks!


overview.html 404 (Not Found)

I`ve added styleguide-generate into my gruntfile as shown in README, but  got 404 on /overview.html and /socket.io/socket.io.js

/socket.io/ client can be fetched here: https://github.com/Automattic/socket.io-client.git

@iegik I'm getting the same error via grunt. Were you able to solve the issue and if you did then can you explain how?

In the documentation there is nothing says about Socket.IO dependency.
About the overflow.html - it seems to be generated by https://github.com/SC5/sc5-styleguide#documenting-syntax ...
I did not complete configuration jet.

I am also getting a 404 on overview.html using gulp

@iegik Did I understand correctly that the problem was missing overviewPath in the config? I fixed the Grunt example in the documentation https://github.com/SC5/sc5-styleguide/pull/732

@varya adding overviewPath worked for me.


Get rid of ELB

I want to use Route 53 for load balancing. And I don't need use ELB for load balancing.  Is it possible ?

Hi @vankhoa011,
What you've described is possible, but slightly out of scope for this particular reference architecture as the goal was to highlight integration between ECS and ELB.
Let me give this some thought and perhaps we can produce a future reference architecture that implements the design you've described.
thanks,
chad


592: Tell users if they enter an invalid age

Worked on https://github.com/google/personfinder/issues/592 ;
It is its most simplest validation form (which doesn't consider the CJK or if the order of the ages is proper (i.e. "34-0" might be considered invalid if the database doesn't handle that)).

I signed it!

@googlebot I fixed it.

@googlebot I fixed it.


check if data is serializable

This throws an error if a load function in +page.server.js or +layout.server.js returns data that can't be serialized as JSON, so things like /hello/ don't become {}.
Supersedes #5635.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

ObjectIds get blocked despite passing a JSON.stringify({ a: new ObjectId() }). Is this intended?


Disabling "emulate mouse from touch" in android editor makes it unusable upon restart

Tested versions
Godot 4.3.0 stable [Android]
System information
Android 13 (Xiaomi Poco F3) - Godot 4.3 stable
Issue description
After disabling "emulate mouse from touch" in project settings and restarting the editor, it becomes impossible to use the editor with touch.
Steps to reproduce

Disable "emulate mouse from touch" in project settings
Exit Godot editor and remove from recents
Re-open the editor and open your project

Minimal reproduction project (MRP)
N/A

CC @m4gr3d
It's logical that disabling mouse emulation would prevent using it - the solution here is to connect a mouse and re-enable it, if using mouse emulation was needed.
That being said it's a bug that the project setting impacts the editor, so this needs to be changed so that the editor has its own control over the use of mouse emulation from touch.
And to get out of this kind of situation, there should probably be an easy way to reset editor settings if users disable it by mistake (or we prevent disabling it altogether).

Also, it's odd that prior to restarting the editor, the setting only applies to the project and does not impact the editor itself (which is how it should be).


Noise suppression functionality

I'm implementing the SDK and I noticed that it doesn't have noise suppression functionality, will it be implemented?

It does have it, it's enabled automatically all the time.

Thanks for your feedback, I'm asking because I'm using SDK version 0.1.9 and it seems that noise suppression isn't working, does this version also have the functionality automatically activated?

There was a problem with duplicated audio which was fixed in the latest release, are you able to test that one?

ok, I'll check, as I had some conflict problems with the last version so I kept version 0.1.9 I'll come back here during the week and it will be resolved, thank you.

👍


[REQUEST] Support TinyMCE

Request you support TinyMCE as well as ProseMirror (and maybe Markdown too?). Prosemirror still is not nearly in feature parity with TinyMCE, so still using Tiny.
Thanks for a GREAT mod!

Thanks for the note!  TinyMCE now supported in v1.0.0.
I'm going to close this issue to separate Tiny from others, but if you need Markdown (or something else), just open a new one with the editor needed and ideally a module that uses it so I can make sure I'm testing it correctly.


Add PursuedPyBear

Add templating for PPB.
A few things:
Technically, v0.8 isn't actually released. It's currently rc1, so this won't work until next week or so. PPB is semver, so ~= is the appropriate version descriptor.
I noticed that briefcase has support for a splash. PPB does have a loading screen feature, but I'm not familiar if/how that data would get added to the application.
I have no idea how to test that I did this right.
cc @pathunstrom

Ah, splash screens are only for mobile. They are not packaged as part of desktop.

@astronouth7303 Correct- they're currently added as part of the platform template, and aren't currently being used as part of desktop deployments. However, I'm definitely interested in proposals for how to integrate them.
On first inspection, this all looks good; I'll take it for a spin myself when I get a chance.
In terms of personal testing - best approach is to use cookiecutter directly. If that works, then Briefcase will work too.

I'll try it out using cookie cutter sometime this week.

Ok, actually tested it. My testing process:
🐚 cookiecutter ~/src/briefcase-template/
🐚 cd helloworld/
🐚 # Fix pyproject.toml to ppb~=0.8.0rc1
🐚 briefcase dev

Should see a window with the title of the human name (formal name) and a bee in the middle of the screen.

Confirming this worked for ppb on windows.

And v0.8.0 is out and on PyPI.


Debugger Map Scope

User story
As a developer, I want to be able to use the Map Scopes feature, so I can view variables from the original source.
Acceptance criteria
What can be verified to be sure that this user story is completed?

[ ] New section added to Debugger documentation that describes the process
[ ] New section reviewed
[ ] Feature added to 67 release notes

This page was created a while back as a placeholder so that the developers could use it as a target from the UI: Map Scopes


update current year

resolve https://github.com/OpenFunction/openfunction.dev/issues/322

cc @benjaminhuo

@Arhell Now you're the admin of this repo


"Waiting for server reply" when trying to connect with openvpn for android

hey guys i cant seem to connect to the pihole. doesnt matter if im using tcp or udp or if its split or full. it always says waiting for server reply while trying to connect

are you on a network that blocks OpenVPN connections? are there any detailed logs you can share from the app? can you share screenshots of your configurations on your phone and the contents of the configuration files on the pi-hole server? (feel free to redact/obscure sensitive information, like public IP addresses and keys)

@stiboan are you able to try this solution instead?
https://github.com/rajannpatel/Pi-Hole-on-Google-Compute-Engine-Free-Tier-with-Full-Tunnel-and-Split-Tunnel-Wireguard-VPN-Configs