Version 1.1.x causes "Unable to resolve path to module" errors

When I allow npm to upgrade this package beyond 1.0.2 I get the following error output:

myfile.test.js
1:1   error  Resolve error: Unexpected token )                                     import/no-unresolved
1:1   error  Resolve error: Unexpected token )                                     import/no-extraneous-dependencies
4:34  error  Unable to resolve path to module './myfile'  import/no-unresolved

where myfile is a typescript module and myfile.test is a javascript unit test file.
This is what my .eslintrc.json looks like
{
    "parser": "babel-eslint",
    "env": {
        "jasmine": true,
        "es6": true,
        "browser": true,
        "node": true,
        "mocha": true
    },
    "settings": {
        "import/resolver": {
          "node": true,
          "eslint-import-resolver-typescript": true
        }
      },
    "plugins": ["jasmine", "react", "chai-friendly"],
    "extends": ["airbnb", "plugin:react/recommended"]
}

Let me know if you need more info.  We don't use webpack as this is a node app that serves static HTML via React components

Does babel-eslint actually support typescript yet?

Regardless, unless you have an explicit need for the babel parser, I would suggest switching to @typescript-eslint/parser, it's built to properly integrate eslint and typescript.

as per the readme, config with the new version should be:

 "settings": {
   "import/resolver": {
     "node": true,
-    "eslint-import-resolver-typescript": true
+    "typescript": {}
   }
 },

Does babel-eslint actually support typescript yet?

I don't know actually.  We use tslint for for our typescript files and eslint for javascript. Come to think of it, I don't know why that is in there at all.  We don't use any language features in this project that would require it.  I can remove it and our linting works just fine.
If I update the config to match the readme I still get the same errors.
{
    "env": {
        "jasmine": true,
        "es6": true,
        "browser": true,
        "node": true,
        "mocha": true
    },
    "settings": {
        "import/resolver": {
          "node": true,
          "typescript": {}
        }
      },
    "plugins": ["jasmine", "react", "chai-friendly"],
    "extends": ["airbnb", "plugin:react/recommended"]
}

You need to use a typescript parser if you've got typescript code that will at some point be run through eslint.
ESLint has no concept of typescript language features, and its parser will crash on them.
Similarly eslint-plugin-import requires a typescript parser if you're importing typescript files.
What is your myfile.test.js? What is the imported file './myfile'?
If you're only running eslint over your javascript code, how come you're using this plugin?

What is your myfile.test.js? What is the imported file './myfile'?

The test file is importing the module under test like so:
const myfile = require('../../src/myfile')
myfile is typescript and exports some consts and a class like so
export const MY_CONST = '';
export class MyFileClass {}

If you're only running eslint over your javascript code, how come you're using this plugin?

If we don't use this plugin then eslint does not know that the imported typescript class is a real module.  We get the "Unable to resolve path to module" error.  Adding this plugin (v1.0.2) fixed this  for us.

If you're using babel-eslint with TypeScript together, make sure you're enabled TypeScript related babel plugin(s) correctly, close for now.
Please try the latest babel, or with<EMAIL_ADDRESS>or you should use @typescript-eslint/parser for .tsx? actually. Feel free to open a new issue if I'm incorrect.

same issue 🫤

@stoplion please don't necro old, closed issue unless you have a solid repro or information to add.


The separator doesn't look good

how to fix this?

The fallback highlight group for WhichKeySeparator used to link to DiffAdded, which does not exist. I merged a PR to fix this to DiffAdd, which yields your result.
I've just pushed a new update that changes the fallback to Comment, which should be better suitable.

yeah thats way better, what i did was just changed the color of the separator from my catppuccin colorscheme


-i (--input) does not work with wildcards when using in path to folder: /path/to/folder/*.js

Hi Gerben, I hope you're well :)
I found a small issue in -i option. When I pass as an argument a path to the folder with JavaScript files using wildcard:
$ ./linkfinder.py -i ~/hacking/bugbounty/Valve/store.steampowered.com/*.js

I get the following error:
linkfinder.py: error: unrecognized arguments:
/Users/bl4de/hacking/bugbounty/Valve/store.steampowered.com/dynamicstore.js
/Users/bl4de/hacking/bugbounty/Valve/store.steampowered.com/home.js
/Users/bl4de/hacking/bugbounty/Valve/store.steampowered.com/jquery-1.8.3.min.js
/Users/bl4de/hacking/bugbounty/Valve/store.steampowered.com/main.js
/Users/bl4de/hacking/bugbounty/Valve/store.steampowered.com/shared_global.js
/Users/bl4de/hacking/bugbounty/Valve/store.steampowered.com/shared_responsive_adapter.js
/Users/bl4de/hacking/bugbounty/Valve/store.steampowered.com/tooltip.js

When I call single file from this folder, LinkFinder works like a charm:
$ ./linkfinder.py --input ~/hacking/bugbounty/Valve/store.steampowered.com/cluster.js

Running against: /Users/bl4de/hacking/bugbounty/Valve/store.steampowered.com/cluster.js

Let me know if you need any additional information about this issue
Regards,
bl4de

Hi bl4de,
Im aware of this issue. LinkFinder has been written in such a way that you need to use single quote when referencing an asterisk like: ./linkfinder.py -i '~/hacking/bugbounty/Valve/store.steampowered.com/*.js'. If you know a way to fix this I'd be happy to implement it, but else I would suggest you to use this method.
Regards,
Gerben

Hi Gerben,
I'll try to take a look at this issue, maybe I will find a way to fix this.
If yes, I'll send a PR :)
Regards,
bl4de

Thanks! Also for being alert on issues and reporting them.

We should help each other, I think.
Especially, if we use tools made by them :)


Update Ubuntu/Debian installation instructions to use Signed-By option

This updates the kubectl/kubeadm installation instructions on Ubuntu/Debian to:

Replace the use of apt-key to install the Kubernetes package signing key with a simple wget. apt-key has been deprecated and will be last available in Debian 11 and Ubuntu 22.04.
Writes the package signing keys to /usr/share/keyrings/kubernetes-archive-keyring.gpg as per https://wiki.debian.org/DebianRepository/UseThirdParty. Note that it is no longer recommended to write or add keys to /etc/apt/trusted.gpg or /etc/apt/trusted.gpg.d/
Makes use of the signed-by option to the repo /etc/apt/sources.list.d/kubernetes.list

This PR also updates the containerd.io / docker-ce (Container runtimes) repository setup instructions. The instructions which previously duplicated an outdated set of instructions from Docker now refer to the respective OS distribution instructions at https://docs.docker.com/engine/install/ which has already been updated to best practice.
Note that I have left the CRI-O Installation instructions as the installation instructions at https://cri-o.io still makes use apt-key add -.
Resolves #26906
References:

https://wiki.debian.org/DebianRepository/UseThirdParty
https://askubuntu.com/questions/1286545/what-commands-exactly-should-replace-the-deprecated-apt-key/1307181#1307181
https://www.linuxuprising.com/2021/01/apt-key-is-deprecated-how-to-add.html
https://github.com/docker/docker.github.io/issues/11625#issuecomment-751388087

If this gets an LGTM from SIG Cluster Lifecycle I'm pretty sure I'll be happy to approve it (same for other SIG Docs approvers).

/sig cluster-lifecycle


Make ask available via brew

Can now be done by tapping the repo and then installing
brew tap damoonrashidi/homebrew-ask https://github.com/damoonrashidi/homebrew-ask
brew install ask


Preview Tool Source Code

Thanks for making this great library! Is the source code for the preview tool available anywhere?
I was hoping to poke around in it to help me understand how the settings for Gradient Perturb work.

I'm also curious about how to replicate the results of Gradient Perturb.

same here :) Great library by the way!

I'm currently working on a better noise preview tool that will have a real 3D output and multi-platform. I don't want to to put the effort into getting the current noise preview tool in a state to release, but here is a Gist of the main cpp

I’ve been reading your source code and   Noticed it was not possible to
generate a periodic (tileable) Perlin/Cellular noise... did I miss
something?
If not, I am planning in extending your code with that feature ( needed by
our project and fastNoise seems to be the most appropriate).
Would you be interested by such a feature if I can make something decent? I
would fork and pull request the modifications.
Have a good day and cheers for your great work.
Le sam. 3 févr. 2018 à 08:15, Jordan Peck<EMAIL_ADDRESS>a
écrit :

I'm currently working on a better noise preview tool that will have a real
3D output and multi-platform. I don't want to to put the effort into
getting the current noise preview tool in a state to release, but here is a
Gist https://gist.github.com/Auburns/6c26380869f99e998c5122d044036f2c
of the main cpp
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Auburns/FastNoise/issues/13#issuecomment-362805203,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANFRieFJa8r1FmSvFdApaHuLfx2i_1Ffks5tRFwAgaJpZM4PaQ_9
.

--
-Po

Please create a new issue for this, but yes I think it is a desired feature.


Mod not supported in newest BG version Hotfix #18

The recent hotfix for Baldur’s Gate 3 made the mod stop working again :(
could we get another update please?

When I find the time...
But to be honest, Ersh, Norbyte and me are not really motivated to support Hotfix 18. Supposedly, it was only a teeny tiny fix for trading, but they messed up the entire binary file.
I'm pretty sure they built the file with the wrong compiler settings. This happened once before. This causes a lot of work on the modders end, for nothing.
I recommend you to roll back your game version for now. This should be possible on both GOG and Steam.

Oh! That must stink... :(
I'll end up rolling back the game then, thank you anyway for letting me know! :)

Late reply. Hotfix 19 fixed the issue.


OLS-409: Evaluation - standalone script & f1 score

Description
Make evaluation a standalone script.
Use f1 score for evaluation.
Ability to use additional QnA from a parquet file.

/lgtm

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

Project coverage is 95.42%. Comparing base (9addeb3) to head (92139ae).
Report is 14 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1191   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files          56       56
  Lines        2381     2381
=======================================
  Hits         2272     2272
  Misses        109      109

/approve


Write inline documentation for src/syft.js

Where?
src/syft.js
Who?
Any developer who wants to work on syft.js should be able to read inline documentation for this file, as well as any file in the project.
What?
We need to go "line-by-line" and create inline documentation for this file. Please try to use proper punctuation and English grammar to the best of your ability.
Additional Context
None

Hey guys, per Vova's suggestion I'll take on this and check if it's properly documented.

🎉


Build a Snap package

Dunner should be packaged and distributed as a Snap Package.
Anyone should be able to install Dunner as snap install dunner

I'm working on this

Fixed by #60


Update all gems to latest versions

Changes

Update capistrano3-puma from 5.1.1 to 5.2.0.
Update httpi from 2.4.5 to 2.5.0.
Update i18n from 1.8.10 to 1.8.11.
Update marcel from 1.0.1 to 1.0.2.
Update mini_mime from 1.1.1 to 1.1.2.
Update parallel from 1.20.1 to 1.21.0.
Update puma from 5.5.1 to 5.5.2.
Update racc from 1.5.2 to 1.6.0.
Update rack-cache from 1.12.1 to 1.13.0.
Update redis from 4.4.0 to 4.5.1.
Update rspec-support from 3.10.2 to 1.20.0.
Update rspec-support from 3.10.3 to 1.23.0.
Update rubocop-ast from 1.11.0 to 1.13.0.
Update rubocop-rails from 2.12.1 to 2.12.4.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1358

Relevant Lines:
1382

💛  - Coveralls


Permissive licensing

Discussion with JK Weiss, TESCAN:
If LiberTEM was under a permissive license like MIT, it would allow integration in TESCAN's software. That would be of concrete interest for TESCAN.
Since we have a lot of code contributed by a small number of contributors, and we can probably contact a large percentage of our contributors, re-licensing would be a realistic option.

Assigning to the next milestone to make sure we follow up in a timely manner.

    install_requires=[
        "numpy", # 3-Clause BSD
        "scipy>=1.4.1", # 3-Clause BSD
        "sparse", # 3-Clause BSD License
        "distributed>=2.19.0", # 3-Clause BSD License
        "dask!=2023.6.1",  # 3-Clause BSD License
        "click", # 3-Clause BSD License
        "tornado>=5", # Apache 2.0
        "matplotlib", # Matplotlib only uses BSD compatible code, and its license is based on the [PSF](https://docs.python.org/3/license.html) license
        "pillow", # Like PIL, Pillow is licensed under the open source HPND License (permissive)
        "h5py", # 3-Clause BSD License
        "psutil", # 3-Clause BSD License
        # https://github.com/LiberTEM/LiberTEM/issues/763
        # https://github.com/LiberTEM/LiberTEM/issues/783
        "numba>=0.51", # BSD 2-Clause "Simplified" License
        "ncempy>=1.10", # !!!  EMPyRe is licensed under [GPLv3](https://iffgit.fz-juelich.de/empyre/empyre/-/blob/master/LICENSE).
        'defusedxml', # Python Software Foundation License (PSFL)
        'typing-extensions',  # Python Software Foundation License
        'opentelemetry-api', # Apache 2.0
        'tblib', # BSD 2-Clause License
        'tomli', # MIT License
        'sparseconverter>=0.3.3', # MIT License
        'numexpr!=2.8.6',  # MIT License
        'jupyter_ui_poll',  # MIT License
        'ipympl',  # 3-Clause BSD License
    ],
    extras_require={
        # NumPy interfacing issue on Win 11, Python 3.10
        # Likely caused by other packages constraining NumPy version to <1.23
        # FIXME recheck later again
        'torch': 'torch<1.12', # 3-Clause BSD License
        # Typing issue in hdbscan, maybe
        # https://github.com/scikit-learn-contrib/hdbscan/issues/600
        # FIXME check if error in tests\test_fullmatch.py persists in a later
        # hdbscan release
        'hdbscan': [
            "hdbscan<=0.8.30;( python_version=='3.11' and platform_system=='Windows')", # 3-Clause BSD License
            "hdbscan;( python_version!='3.11' or platform_system!='Windows')",
        ],
        'cupy': 'cupy', # MIT License
        'bqplot': [
            'bqplot', # MIT License
            'bqplot-image-gl', # MIT License
            'ipython'], # 3-Clause BSD License
        'hdf5plugin': 'hdf5plugin', # MIT License It's complicated https://github.com/silx-kit/hdf5plugin/blob/main/LICENSE
        'tracing': [
            'opentelemetry-distro', # Apache 2.0
            'opentelemetry-exporter-otlp', # Apache 2.0
        ],
    },

empyre and ncempy are GPL, the rest is permissive. Looks feasible!

Discussion with @sk1p: We could use this opportunity to spin out the web GUI and perhaps other parts in separate modules.

Btw. this also concerns the LiberTEM-live repo, but there it is much easier because of the lower number of contributors.
@matbryan52 what do you think about this? Your opinion is very important for deciding if we want to go forward with re-licensing or not, before contacting other individual contributors. Both Dieter and me would vote to go forward with the re-licensing, if there aren't any show stoppers.

ncempy [is] GPL

The io part of ncempy is MIT licensed, by the way!

@matbryan52 what do you think about this? Your opinion is very important for deciding if we want to go forward with re-licensing or not, before contacting other individual contributors. Both Dieter and me would vote to go forward with the re-licensing, if there aren't any show stoppers.

Absolutely, I've always assumed this would happen one day with the push to put things into libertem.common where possible.
Sorry for the slowness replying!

Absolutely, I've always assumed this would happen one day with the push to put things into libertem.common where possible.

Thanks for the reply! @uellue I'll assign the issue to you if you don't mind - of course I'll help wherever I can.

Sorry for the slowness replying!

No worries!

List of contributors, tracking agreement with MIT relicensing:

[x] Alexander Clausen
[x] Dieter Weber
[x] Matthew Bryan
[ ] Karina Ruzaeva
[ ] Vadim Migunov
[ ] Sivert J.V. Dagenborg
[ ] Anand Baburajan
[ ] Abijith Bahuleyan
[ ] Jan Caron
[ ] Rahul Chandra
[ ] Shankhadeep Dey
[ ] Sayandip Halder
[ ] Daniel S. Katz
[ ] Barnaby D.A. Levin
[ ] Magnus Nord
[ ] Colin Ophus
[ ] Simon Peter
[ ] Levente Puskás
[ ] Jay van Schyndel
[ ] Jaeweon Shin
[ ] Sai Sunku
[ ] Håkon Wiik Ånes
[ ] Knut Müller-Caspary
[ ] Rafal E. Dunin-Borkowski

Hi @kruzaeva @woozey @sivborg @anandbaburajan @twentyse7en @jan-car @irahulcse @iamshankhadeep @sayandip18 @danielskatz @bdalevin @magnunor @cophus @probonopd @DYVZ8X @ozej8y @jaewshin @saisunku @hakonanes @rafaldb
I'm contacting you since you contributed to the LiberTEM project. Many thanks for being a part of this project! If you are wondering what your contribution was you can have a look at our acknowledgments or ask us.
From several companies, including Direct Electron, Nanomegas and TESCAN, we received feedback that they would be very interested to use LiberTEM if it was MIT licensed. That would be very much in line with our goal to make electron microscopy software and hardware more open and interoperable, and to provide and maintain a shared infrastructure to make life easier for everybody.
Since most of LiberTEM, including your contributions, were previously licensed under the GPL-3, I'd like to ask for your consent to re-license your contributions to any of the repositories in the LiberTEM organization under the MIT license. A very simple "yes" comment or e-mail would be sufficient if you agree.
If you don't agree or if you have further questions, you are very welcome to comment here or contact me at<EMAIL_ADDRESS>Again, many thanks for your contribution, and I hope to hear back from you!
Dieter

Yea
On Thu, Sep 12, 2024 at 13:54 Daniel S. Katz @.***>
wrote:

yes
—
Reply to this email directly, view it on GitHub
https://github.com/LiberTEM/LiberTEM/issues/1649#issuecomment-2345586653,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF4BBDOF2KTCZFAT56X7MBLZWFFSLAVCNFSM6AAAAABI6ZL6NOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBVGU4DMNRVGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes
Regards,
Rahul Chandra
Email: @.** @.**>
On Thu, Sep 12, 2024 at 10:21 AM Dieter Weber @.***>
wrote:

Hi @kruzaeva https://github.com/kruzaeva @woozey
https://github.com/woozey @sivborg https://github.com/sivborg
@anandbaburajan https://github.com/anandbaburajan @twentyse7en
https://github.com/twentyse7en @jan-car https://github.com/jan-car
@irahulcse https://github.com/irahulcse @Iamshankhadeep
https://github.com/Iamshankhadeep @sayandip18
https://github.com/sayandip18 @danielskatz
https://github.com/danielskatz @bdalevin https://github.com/bdalevin
@magnunor https://github.com/magnunor @cophus
https://github.com/cophus @probonopd https://github.com/probonopd
@DYVZ8X https://github.com/DYVZ8X @ozej8y https://github.com/ozej8y
@jaewshin https://github.com/jaewshin @saisunku
https://github.com/saisunku @hakonanes https://github.com/hakonanes
@rafaldb https://github.com/rafaldb
I'm contacting you since you contributed to the LiberTEM project. Many
thanks for being a part of this project! If you are wondering what your
contribution was you can have a look at our acknowledgments
https://libertem.github.io/acknowledgements.html#creators or ask us.
From several companies, including Direct Electron, Nanomegas and TESCAN,
we received feedback that they would be very interested to use LiberTEM if
it was MIT licensed. That would be very much in line with our goal to make
electron microscopy software and hardware more open and interoperable, and
to provide and maintain a shared infrastructure to make life easier for
everybody.
Since most of LiberTEM, including your contributions, were previously
licensed under the GPL-3, I'd like to ask for your consent to re-license
your contributions to any of the repositories in the LiberTEM organization
https://github.com/LiberTEM/ under the MIT license. A very simple "yes"
comment or e-mail would be sufficient if you agree.
If you don't agree or if you have further questions, you are very welcome
to comment here or contact me at @.***
Again, many thanks for your contribution, and I hope to hear back from you!
Dieter
—
Reply to this email directly, view it on GitHub
https://github.com/LiberTEM/LiberTEM/issues/1649#issuecomment-2345580535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIFCCDQETVQPXZMKHTKR6SDZWFFIBAVCNFSM6AAAAABI6ZL6NOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBVGU4DANJTGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

YesSent from my jPhoneOn 12 Sep 2024, at 6:21 PM, Dieter Weber @.> wrote:
Hi @kruzaeva @woozey @sivborg @anandbaburajan @twentyse7en @jan-car @irahulcse @Iamshankhadeep @sayandip18 @danielskatz @bdalevin @magnunor @cophus @probonopd @DYVZ8X @ozej8y @jaewshin @saisunku @hakonanes @rafaldb
I'm contacting you since you contributed to the LiberTEM project. Many thanks for being a part of this project! If you are wondering what your contribution was you can have a look at our acknowledgments or ask us.
From several companies, including Direct Electron, Nanomegas and TESCAN, we received feedback that they would be very interested to use LiberTEM if it was MIT licensed. That would be very much in line with our goal to make electron microscopy software and hardware more open and interoperable, and to provide and maintain a shared infrastructure to make life easier for everybody.
Since most of LiberTEM, including your contributions, were previously licensed under the GPL-3, I'd like to ask for your consent to re-license your contributions to any of the repositories in the LiberTEM organization under the MIT license. A very simple "yes" comment or e-mail would be sufficient if you agree.
If you don't agree or if you have further questions, you are very welcome to comment here or contact me at @.
Again, many thanks for your contribution, and I hope to hear back from you!
Dieter
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Yes
On Thu, 12 Sept, 2024, 1:51 pm Dieter Weber, @.***>
wrote:

Hi @kruzaeva https://github.com/kruzaeva @woozey
https://github.com/woozey @sivborg https://github.com/sivborg
@anandbaburajan https://github.com/anandbaburajan @twentyse7en
https://github.com/twentyse7en @jan-car https://github.com/jan-car
@irahulcse https://github.com/irahulcse @Iamshankhadeep
https://github.com/Iamshankhadeep @sayandip18
https://github.com/sayandip18 @danielskatz
https://github.com/danielskatz @bdalevin https://github.com/bdalevin
@magnunor https://github.com/magnunor @cophus
https://github.com/cophus @probonopd https://github.com/probonopd
@DYVZ8X https://github.com/DYVZ8X @ozej8y https://github.com/ozej8y
@jaewshin https://github.com/jaewshin @saisunku
https://github.com/saisunku @hakonanes https://github.com/hakonanes
@rafaldb https://github.com/rafaldb
I'm contacting you since you contributed to the LiberTEM project. Many
thanks for being a part of this project! If you are wondering what your
contribution was you can have a look at our acknowledgments
https://libertem.github.io/acknowledgements.html#creators or ask us.
From several companies, including Direct Electron, Nanomegas and TESCAN,
we received feedback that they would be very interested to use LiberTEM if
it was MIT licensed. That would be very much in line with our goal to make
electron microscopy software and hardware more open and interoperable, and
to provide and maintain a shared infrastructure to make life easier for
everybody.
Since most of LiberTEM, including your contributions, were previously
licensed under the GPL-3, I'd like to ask for your consent to re-license
your contributions to any of the repositories in the LiberTEM organization
https://github.com/LiberTEM/ under the MIT license. A very simple "yes"
comment or e-mail would be sufficient if you agree.
If you don't agree or if you have further questions, you are very welcome
to comment here or contact me at @.***
Again, many thanks for your contribution, and I hope to hear back from you!
Dieter
—
Reply to this email directly, view it on GitHub
https://github.com/LiberTEM/LiberTEM/issues/1649#issuecomment-2345580535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOHUM6YUXW25ZIEHPMZYJ3LZWFFIBAVCNFSM6AAAAABI6ZL6NOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBVGU4DANJTGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Knut agreed by personal e-mail, thx! :-)

Yes
On Thu, Sep 12, 2024 at 4:21 AM Dieter Weber @.***>
wrote:

Hi @kruzaeva https://github.com/kruzaeva @woozey
https://github.com/woozey @sivborg https://github.com/sivborg
@anandbaburajan https://github.com/anandbaburajan @twentyse7en
https://github.com/twentyse7en @jan-car https://github.com/jan-car
@irahulcse https://github.com/irahulcse @Iamshankhadeep
https://github.com/Iamshankhadeep @sayandip18
https://github.com/sayandip18 @danielskatz
https://github.com/danielskatz @bdalevin https://github.com/bdalevin
@magnunor https://github.com/magnunor @cophus
https://github.com/cophus @probonopd https://github.com/probonopd
@DYVZ8X https://github.com/DYVZ8X @ozej8y https://github.com/ozej8y
@jaewshin https://github.com/jaewshin @saisunku
https://github.com/saisunku @hakonanes https://github.com/hakonanes
@rafaldb https://github.com/rafaldb
I'm contacting you since you contributed to the LiberTEM project. Many
thanks for being a part of this project! If you are wondering what your
contribution was you can have a look at our acknowledgments
https://libertem.github.io/acknowledgements.html#creators or ask us.
From several companies, including Direct Electron, Nanomegas and TESCAN,
we received feedback that they would be very interested to use LiberTEM if
it was MIT licensed. That would be very much in line with our goal to make
electron microscopy software and hardware more open and interoperable, and
to provide and maintain a shared infrastructure to make life easier for
everybody.
Since most of LiberTEM, including your contributions, were previously
licensed under the GPL-3, I'd like to ask for your consent to re-license
your contributions to any of the repositories in the LiberTEM organization
https://github.com/LiberTEM/ under the MIT license. A very simple "yes"
comment or e-mail would be sufficient if you agree.
If you don't agree or if you have further questions, you are very welcome
to comment here or contact me at @.***
Again, many thanks for your contribution, and I hope to hear back from you!
Dieter
—
Reply to this email directly, view it on GitHub
https://github.com/LiberTEM/LiberTEM/issues/1649#issuecomment-2345580535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALIYKEJJCPSWR2FWZ2XLIQLZWFFIBAVCNFSM6AAAAABI6ZL6NOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBVGU4DANJTGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes

Yes

yes
On Thu, 12 Sept 2024 at 10:21, Dieter Weber @.***>
wrote:

Hi @kruzaeva https://github.com/kruzaeva @woozey
https://github.com/woozey @sivborg https://github.com/sivborg
@anandbaburajan https://github.com/anandbaburajan @twentyse7en
https://github.com/twentyse7en @jan-car https://github.com/jan-car
@irahulcse https://github.com/irahulcse @Iamshankhadeep
https://github.com/Iamshankhadeep @sayandip18
https://github.com/sayandip18 @danielskatz
https://github.com/danielskatz @bdalevin https://github.com/bdalevin
@magnunor https://github.com/magnunor @cophus
https://github.com/cophus @probonopd https://github.com/probonopd
@DYVZ8X https://github.com/DYVZ8X @ozej8y https://github.com/ozej8y
@jaewshin https://github.com/jaewshin @saisunku
https://github.com/saisunku @hakonanes https://github.com/hakonanes
@rafaldb https://github.com/rafaldb
I'm contacting you since you contributed to the LiberTEM project. Many
thanks for being a part of this project! If you are wondering what your
contribution was you can have a look at our acknowledgments
https://libertem.github.io/acknowledgements.html#creators or ask us.
From several companies, including Direct Electron, Nanomegas and TESCAN,
we received feedback that they would be very interested to use LiberTEM if
it was MIT licensed. That would be very much in line with our goal to make
electron microscopy software and hardware more open and interoperable, and
to provide and maintain a shared infrastructure to make life easier for
everybody.
Since most of LiberTEM, including your contributions, were previously
licensed under the GPL-3, I'd like to ask for your consent to re-license
your contributions to any of the repositories in the LiberTEM organization
https://github.com/LiberTEM/ under the MIT license. A very simple "yes"
comment or e-mail would be sufficient if you agree.
If you don't agree or if you have further questions, you are very welcome
to comment here or contact me at @.***
Again, many thanks for your contribution, and I hope to hear back from you!
Dieter
—
Reply to this email directly, view it on GitHub
https://github.com/LiberTEM/LiberTEM/issues/1649#issuecomment-2345580535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKAOE4WJ3N3A4XHRP3RYEK3ZWFFIBAVCNFSM6AAAAABI6ZL6NOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBVGU4DANJTGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes yes

Yes
On Thu, Sep 12, 2024 at 9:56 AM kruzaeva @.***> wrote:

yes
On Thu, 12 Sept 2024 at 10:21, Dieter Weber @.***>
wrote:

Hi @kruzaeva https://github.com/kruzaeva @woozey
https://github.com/woozey @sivborg https://github.com/sivborg
@anandbaburajan https://github.com/anandbaburajan @twentyse7en
https://github.com/twentyse7en @jan-car https://github.com/jan-car
@irahulcse https://github.com/irahulcse @Iamshankhadeep
https://github.com/Iamshankhadeep @sayandip18
https://github.com/sayandip18 @danielskatz
https://github.com/danielskatz @bdalevin https://github.com/bdalevin

@magnunor https://github.com/magnunor @cophus
https://github.com/cophus @probonopd https://github.com/probonopd
@DYVZ8X https://github.com/DYVZ8X @ozej8y https://github.com/ozej8y
@jaewshin https://github.com/jaewshin @saisunku
https://github.com/saisunku @hakonanes https://github.com/hakonanes
@rafaldb https://github.com/rafaldb
I'm contacting you since you contributed to the LiberTEM project. Many
thanks for being a part of this project! If you are wondering what your
contribution was you can have a look at our acknowledgments
https://libertem.github.io/acknowledgements.html#creators or ask us.
From several companies, including Direct Electron, Nanomegas and TESCAN,
we received feedback that they would be very interested to use LiberTEM
if
it was MIT licensed. That would be very much in line with our goal to
make
electron microscopy software and hardware more open and interoperable,
and
to provide and maintain a shared infrastructure to make life easier for
everybody.
Since most of LiberTEM, including your contributions, were previously
licensed under the GPL-3, I'd like to ask for your consent to re-license
your contributions to any of the repositories in the LiberTEM
organization
https://github.com/LiberTEM/ under the MIT license. A very simple
"yes"
comment or e-mail would be sufficient if you agree.
If you don't agree or if you have further questions, you are very
welcome
to comment here or contact me at @.***
Again, many thanks for your contribution, and I hope to hear back from
you!
Dieter
—
Reply to this email directly, view it on GitHub
<
https://github.com/LiberTEM/LiberTEM/issues/1649#issuecomment-2345580535>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AKAOE4WJ3N3A4XHRP3RYEK3ZWFFIBAVCNFSM6AAAAABI6ZL6NOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBVGU4DANJTGU>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/LiberTEM/LiberTEM/issues/1649#issuecomment-2346362589,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5VXBIYXSRKYYYXRXDEWA3ZWGMQ7AVCNFSM6AAAAABI6ZL6NOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWGM3DENJYHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes
Great job pushing it forward 👍🏻👍🏻

Yes2024. szept. 12. dátummal, 17:07 időpontban Vadim Migunov @.***> írta:
Yes
Great job pushing it forward 👍🏻👍🏻
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Rafal agreed in personal communication. :-)

Sayandip agreed in personal communication

Colin agreed in personal communication

Barnaby agreed in personal communication. That means we have consent from all creators. I'm currently working on the empyre dependency.


[test] Update MpiCheck for Alps

Codecov Report

Merging #1664 (4f3d20f) into master (01d7efc) will decrease coverage by 0.29%.
The diff coverage is 45.28%.

@@            Coverage Diff             @@
##           master    #1664      +/-   ##
==========================================
- Coverage   87.54%   87.24%   -0.30%
==========================================
  Files          45       45
  Lines        7492     7545      +53
==========================================
+ Hits         6559     6583      +24
- Misses        933      962      +29

Impacted Files
Coverage Δ

reframe/core/modules.py
56.62% <45.28%> (-1.21%)
:arrow_down:

Continue to review full report at Codecov.

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

@jenkins-cscs retry dom


V2 -> can't resolve 'gatsby-link'

After trying to clone, npm install and running gatsby develop I run into this issue:
PS C:\Users\user\Desktop\Blog_Test\my-blog> gatsby develop success open and validate gatsby-config — 0.009 s success load plugins — 0.243 s success onPreInit — 1.073 s success delete html and css files from previous builds — 0.251 s success initialize cache — 0.154 s success copy gatsby files — 0.190 s success onPreBootstrap — 0.002 s success source and transform nodes — 0.123 s success building schema — 0.317 s success createPages — 0.031 s success createPagesStatefully — 0.037 s success onPreExtractQueries — 0.003 s success update schema — 0.156 s warning Using the global graphqltag is deprecated, and will not be supported in v3. Import it instead like:  import { graphql } from 'gatsby' in file: C:/Users/user/Desktop/Blog_Test/my-blog/src/pages/index.js warning Using the globalgraphql` tag is deprecated, and will not be supported in v3.
Import it instead like:  import { graphql } from 'gatsby' in file:
C:/Users/user/Desktop/Blog_Test/my-blog/src/templates/blog-post.js
success extract queries from components — 0.135 s
success run graphql queries — 0.198 s — 7/7 36.50 queries/second
success write out page data — 0.009 s
success write out redirect data — 0.003 s
success onPostBootstrap — 0.001 s
info bootstrap finished - 7.647 s
here ./.cache/gatsby-browser-entry.js
Module not found: Error: Can't resolve 'gatsby-link' in 'C:\Users\user\Desktop\Blog_Test\my-blog.cache'
resolve 'gatsby-link' in 'C:\Users\user\Desktop\Blog_Test\my-blog.cache'
Parsed request is a module
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./.cache)
resolve as module
looking for modules in C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./src//node_modules)
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./src/node_modules/gatsby-link)
no extension
C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link doesn't exist
.js
C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link.js doesn't exist
.jsx
C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link.jsx doesn't exist
as directory
C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link doesn't exist
C:\Users\user\Desktop\Blog_Test\my-blog.cache\node_modules doesn't exist or is not a directory
C:\Users\user\Desktop\Blog_Test\node_modules doesn't exist or is not a directory
C:\Users\user\Desktop\node_modules doesn't exist or is not a directory
C:\Users\node_modules doesn't exist or is not a directory
C:\node_modules doesn't exist or is not a directory
looking for modules in C:\Users\user\node_modules
No description file found
looking for modules in C:\Users\user\Desktop\Blog_Test\my-blog\node_modules
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./node_modules)
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./node_modules/gatsby-link)
no extension
C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link doesn't exist
.js
C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link.js doesn't exist
No description file found
.jsx
C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link.jsx doesn't exist
no extension
C:\Users\user\node_modules\gatsby-link doesn't exist
as directory
C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link doesn't exist
.js
C:\Users\user\node_modules\gatsby-link.js doesn't exist
.jsx
C:\Users\user\node_modules\gatsby-link.jsx doesn't exist
as directory
C:\Users\user\node_modules\gatsby-link doesn't exist
[C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link]
[C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link.js]
[C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link.jsx]
[C:\Users\user\Desktop\Blog_Test\my-blog.cache\node_modules]
[C:\Users\user\Desktop\Blog_Test\node_modules]
[C:\Users\user\Desktop\node_modules]
[C:\Users\node_modules]
[C:\node_modules]
[C:\Users\user\node_modules\package.json]
[C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link]
[C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link.js]
[C:\Users\user\node_modules\gatsby-link\package.json]
[C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link.jsx]
[C:\Users\user\node_modules\gatsby-link]
[C:\Users\user\node_modules\gatsby-link.js]
[C:\Users\user\node_modules\gatsby-link.jsx]
@ ./.cache/gatsby-browser-entry.js 3:0-74 28:0-29:48 28:0-29:48 28:0-29:48 28:0-29:48 28:0-29:48
@ ./node_modules/gatsby-plugin-feed/gatsby-ssr.js
@ ./.cache/api-runner-ssr.js
@ ./.cache/develop-static-entry.js
error There was an error compiling the html.js component for the development server.
See our docs page on debugging HTML builds for help https://goo.gl/yL9lND
Error: ./.cache/gatsby-browser-entry.js
Module not found: Error: Can't resolve 'gatsby-link' in 'C:\Users\user\Desktop\Blog_Test\my-blog.cache'
resolve 'gatsby-link' in 'C:\Users\user\Desktop\Blog_Test\my-blog.cache'
Parsed request is a module
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./.cache)
resolve as module
looking for modules in C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./src//node_modules)
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./src/node_modules/gat  sby-link)
no extension
C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link doesn't exist
.js
C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link.js doesn't exist
.jsx
C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link.jsx doesn't exist
as directory
C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link doesn't exist
C:\Users\user\Desktop\Blog_Test\my-blog.cache\node_modules doesn't exist or is not a directory
C:\Users\user\Desktop\Blog_Test\node_modules doesn't exist or is not a directory
C:\Users\user\Desktop\node_modules doesn't exist or is not a directory
C:\Users\node_modules doesn't exist or is not a directory
C:\node_modules doesn't exist or is not a directory
looking for modules in C:\Users\user\node_modules
No description file found
looking for modules in C:\Users\user\Desktop\Blog_Test\my-blog\node_modules
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./node_modules)
using description file: C:\Users\user\Desktop\Blog_Test\my-blog\package.json (relative path: ./node_modules/gatsby-  link)
no extension
C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link doesn't exist
.js
C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link.js doesn't exist
No description file found
.jsx
C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link.jsx doesn't exist
no extension
C:\Users\user\node_modules\gatsby-link doesn't exist
as directory
C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link doesn't exist
.js
C:\Users\user\node_modules\gatsby-link.js doesn't exist
.jsx
C:\Users\user\node_modules\gatsby-link.jsx doesn't exist
as directory
C:\Users\user\node_modules\gatsby-link doesn't exist
[C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link]
[C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link.js]
[C:\Users\user\Desktop\Blog_Test\my-blog\src\node_modules\gatsby-link.jsx]
[C:\Users\user\Desktop\Blog_Test\my-blog.cache\node_modules]
[C:\Users\user\Desktop\Blog_Test\node_modules]
[C:\Users\user\Desktop\node_modules]
[C:\Users\node_modules]
[C:\node_modules]
[C:\Users\user\node_modules\package.json]
[C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link]
[C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link.js]
[C:\Users\user\node_modules\gatsby-link\package.json]
[C:\Users\user\Desktop\Blog_Test\my-blog\node_modules\gatsby-link.jsx]
[C:\Users\user\node_modules\gatsby-link]
[C:\Users\user\node_modules\gatsby-link.js]
[C:\Users\user\node_modules\gatsby-link.jsx]
@ ./.cache/gatsby-browser-entry.js 3:0-74 28:0-29:48 28:0-29:48 28:0-29:48 28:0-29:48 28:0-29:48
@ ./node_modules/gatsby-plugin-feed/gatsby-ssr.js
@ ./.cache/api-runner-ssr.js
@ ./.cache/develop-static-entry.js
PS C:\Users\user\Desktop\Blog_Test\my-blog>`

I hit this same problem. It looks like this occurs on a machine where yarn is not available and the gatsby CLI uses npm instead.
After running npm i -g yarn and then starting over with gatsby new, I was able to use gatsby develop to run the site.
But this should work regardless of whether yarn is used or not.

It seems the real cause of the problem here is that the v2 branch of this template is package locked to only use beta 1 of gatsby 2.
Once I noticed that, I was able to resolve this with just npm present (no yarn). If I gatsby new this template, cd into the dir, and then npm install gatsby@next to get the latest gatsby beta, then gatsby develop works. So I think the root cause of the bug is that the v2 template is using an old gatsby beta.
But I'm bothered that adding yarn "fixed" the problem. I've noticed that, with yarn present on my system, the result of gatsby new for this template produces a local directory which has an additional, local yarn.lock file. It looks like the package-lock.json checked into source control is ignored and, instead, a new yarn.lock is created, and yarn will use that when present. This seems like a problem with the gatsby CLI.

@acooper-accusoft  Thanks for the info. Manually installing beta version of gatsby solved the issue.

@Polcius Could you please try @acooper-accusoft solution and report if it also worked for you?

Make sure to upgrade to the latest RC plus you should import Link from the gatsby package now
https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/#import-link-from-gatsby


[Typescript][Callbacks][4/n] Add Callback events to OpenAI Model Parser

[Typescript][Callbacks][4/n] Add Callback events to OpenAI Model Parser

Stack created with Sapling. Best reviewed with ReviewStack.

#198
-> #116
#113
#112
#111
#115

https://linear.app/lastmile-ai/issue/LAS-454/callback-handler-improvements


Option to additionally write to a log file (or to stderr)

Is your feature request related to a problem? Please describe.
It would be nice to be able to write logs to a file too (in addition to writing to the unified log). For everyday macOS users, the unified log is very hard to comb through, so giving them an option to just open a regular log file would be a plus.
Describe the solution you'd like
Add either an -f or an -r option to flog, so we can additionally either write directly to a file, e.g. with
flog -f "$HOME/Library/Logs/uk.co.fidgetbox.log" -l fault -s uk.co.fidgetbox -c general 'unrecoverable failure'

…or tell flog to write to standard error, so we can redirect that to a file, e.g. with
flog -r -l fault -s uk.co.fidgetbox -c general 'unrecoverable failure' 2>> "$HOME/Library/Logs/uk.co.fidgetbox.log"

Describe alternatives you've considered
(none come to mind)
Additional context
The macOS-built-in logger program does not have an option to write to a file directly, but it has an option (-s) to write to stderr, so the user can redirect.

It's a feature that I'd considered adding, and something I may revisit in the near future. In the interim however, you can achieve the desired behaviour using tee. The message string is read from the standard input stream in this scenario, though it's not as neat as having an explicit option for it as you describe:
echo "unrecoverable error" | tee -a output.log | flog -l fault -s uk.co.fidgetbox -c general

Which sends the log message to Apple's unified logging system and also appends it to the output.log file.
There are likely other possible variations of this that may read better syntactically, though some may depend on the shell being using. For example, we can drop the echo command in favour of a here-string:
tee -a output.log <<< "unrecoverable error" | flog -l fault -s uk.co.fidgetbox -c general

This would be a trade-off in portability however, and would be limited to shells like bash that have support for here-strings.
Regardless, keep an eye on the project board or this issue page for updates, and thanks for the suggestion. 👍🏻

@JayBrown Release 1.3.0 introduces a new -a, --append option to optionally append the log message to a file, in addition to sending it to the unified logging system. Any feedback would be appreciated.

It seems to work so far… need to do more RL testing from within shell scripts.
Additionally, you could also mimic the way logger writes to log files, i.e. not just the log message, but additional info too, e.g.
Jan 19 10:24:11  uk.co.fidgetbox[72161] <fault>: foo

So you'd have the date followed by two whitespaces, then the process ID (the subsystem from -s), flog's PID in square brackets without whitespace in front, then a whitespace and the log level (from -l) in angle brackets, a colon + whitespace, and then the log message proper.
You could also add the category (from -c), but I can't say how that should be done best. Maybe one of these:
Jan 19 10:24:11  uk.co.fidgetbox[72161] <fault:general>: foo

Jan 19 10:24:11  uk.co.fidgetbox[72161] <fault/general>: foo

Jan 19 10:24:11  uk.co.fidgetbox[72161] <fault|general>: foo

Addendum: you could also introduce -A for that, so -a would retain its current functionality. Because in some cases it is better to just log the message to a file as is. (As it stands now, I personally wouldn't need such a verbose logging functionality at the moment, but other users might.)


Using Session & Cookies in auth_request backend

Hello,
I do not seem to be able to use session and cookie in auth_request back end (PHP). How do I  configure so that session and cookies are available?
NGINX Configuration:
location /restricted-resource {
alias restricted-resource;
auth_request /validate;
index index.html index.htm;
error_page 403 /403.html;
}
location ~ .php$ {
root php;
fastcgi_pass <IP_ADDRESS>:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
include fastcgi_params;
}
location /validate {
proxy_pass http://<IP_ADDRESS>/validate.php;
proxy_pass_request_body off;
proxy_set_header Content-Length ';
proxy_set_header X-Original-URI $request_uri;
}
PHP Back end (Example):

Thanks,
Satheesh

Hi, were you able to get it working? I'm dealing with this at this moment!! :'(

Hi. We have the samé problém on auth_request sessions - please do you have solution ?


nz-checkbox-group add ng-template for options

What problem does this feature solve?
I want to add an attribute in every option. More specifically I want to add a data-cy attribute for my cypress tests.
In addition this feature will help us override the default template of options.
Another great addition would be to add options using the template instead of ngModel i.e. using ContentChildren
What does the proposed API look like?
<nz-checkbox-group
  [(ngModel)]="options"
  [optionTemplate]="template"
></nz-checkbox-group>

<ng-template #template let-option>
    {{option.label}}
</ng-template>

Or the implementation with contentChildren with an element nz-checkbox-group-option or a directive
<nz-checkbox-group>
    <nz-checkbox-group-option *ngFor="let option of options" [value]="option.value">
        {{ option.label }}
    </nz-checkbox-group-option>
</nz-checkbox-group>
```

thanks @zapatel I missed that out


Injecting LogPlugin twice causes a panic

Bevy version
Main branch (0.9-dev)
[Optional] Relevant system information
Specs: 14-in M1 Macbook Pro running 12.6 Monterey, with 32 GB Ram
What you did
Injecting DefaultPluigins while also modifying the LogPlugin, works as expected.
DefaultPlugins
            .set(WindowPlugin {
                window: WindowDescriptor {
                    width: WINDOW_WIDTH,
                    height: WINDOW_HEIGHT,
                    title: String::from(LAUNCHER_TITLE),
                    // present_mode: bevy::window::PresentMode::AutoVsync,
                    ..default()
                },
                ..default()
            })
            .set(ImagePlugin::default_nearest())
            .set(bevy::log::LogPlugin { ..default() });

Injecting a second LogPlugin causes a panic for bevy::log/src/lib.rs:118:27
app.add_plugin(bevy::log::LogPlugin { ..default() });

Only when I disable the log plugin from the initial DefaultPlugins does it actually allow me to inject a second context.
defaults.build().disable::<bevy::log::LogPlugin>()
...

// Yay this works :)
app.add_plugin(bevy::log::LogPlugin { ..default() });

Additional information
Here is the full stack trace:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: SetLoggerError(())', /Users/elkxj/.cargo/git/checkouts/bevy-f7ffde730c324c74/7540328/crates/bevy_log/src/lib.rs:118:27
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

related to #1969
panic would change with #6411

Fixed by #6411.

You guys are the best! Thanks!


Updates container image used by Dataflow Runner in unreleased SDKs.

R: @boyuanzz

@boyuanzz Could you help merge this please? Python PreCommit tests are still running, but they are not affected by this change.

And, thanks for quick review, @boyuanzz .

LGTM.


feat(hikari): adding hikari configuration

Description
adding Hikari connection pool configuration to change the default connection pool configuration.
this will allow us to have more flexibility on how should we handle the number of connections being used.
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Hikari will not introduce anything new but instead will configure the connection pool of our application.

[ ] Check the session/connection on the database before starting the app. Should not have any connection open from our app.
[ ] Spin the app and check the session/connection, it should have a single one
[ ] Execute a few requests and check the session/connection, it should have at most 3 connections
[ ] Stop de application and check the session/connection, it should have no more connections from our app pending

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have already been accepted and merged

Further comments
The provided values are just for reference and can be changed/tweaked if required. It can also be replaced by external parameters in order to allow per-environment configuration.

Great job Paulo! Thanks. Before getting this merged I want to team up with DBAs and check for the man-in-the-middle possibility that may be occurring.


re-introducing column-view

code for column-view and pages
Resolved / Related Issues
Itemize resolved / related issues by this PR.
Added code relevant to Column View.
Details of Changes
Add details of changes here.

added Column View to LayoutModes enums
added ColumnView seitch commands

Validation
How did you test these changes?

[X] Built and ran the app

Screenshots (optional)
Add screenshots here.

Re-implementation of #2500

Ok cool.
There's like only a couple things that I need help with to make it ready to ship.

How do I reopen this PR

@TyJOrtiz I think you need to open a new one since this was already merged.

Done
Sent from my iPhone
On Mar 31, 2021, at 9:33 AM, Yair Aichenbaum @.***> wrote:

@TyJOrtizhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTyJOrtiz&data=04|01||8eb32bf3959d4a54ad1b08d8f462b273|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637528052025072212|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=WGvQJ9JUOoU%2FvdHu%2FKgm2ALn92MWIGroPKmmqgh%2BfDM%3D&reserved=0 I think you need to open a new one since this was already merged.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffiles-community%2FFiles%2Fpull%2F4176%23issuecomment-811219496&data=04|01||8eb32bf3959d4a54ad1b08d8f462b273|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637528052025082162|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=47LQo60E8ZHWTAg33RfYfbqJ9T9rt5Wa3jNMTU7PZAQ%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGBFXDHIXOZJP2KJBPHVI4TTGNFFBANCNFSM4ZPAZPVQ&data=04|01||8eb32bf3959d4a54ad1b08d8f462b273|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637528052025082162|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Q1%2FZkiKb1TezVKoLeQZn7pA31dhaNeWtJ2Mq6%2FDS2pQ%3D&reserved=0.


README.md Formatting & Spelling

Update the formatting of the links in the readme and the spelling of the word 'Black'.
Files changed:

readme.md

Thanks @willtheorangeguy :)

Your welcome!


merge from arlac77/template-github,arlac77/template-kronos-module

package.json

chore(package): add ^3.5.2 remove ^3.5.1 (devDependencies.ava)

Codecov Report

Merging #1282 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1282   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files           1       1
  Lines          28      28
  Branches        1       1
======================================
  Hits           28      28

Continue to review full report at Codecov.

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

:tada: This PR is included in version 3.0.17 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


pull request for e2e test at 01/04/2017 08:45:12

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Is hooks an antipattern within the context of Redux?

Hi,
This issue is not meant to start a flamewar or to bash this wonderful library. Also, I do not intend to disrespect the contributors of it, but I am looking for some insight and for an open discussion about the usage of hooks in the context of redux.
I'm a huge proponent of hooks as a replacement of the old React class state + lifecycle methods. It's IMO way easier to reason about the flow of data, to identify bugs and to reuse and compose state / functionality with this API.
Regarding react-redux I've always liked the usage of a HoC (connect) to inject state to props as it nicely decouples the implementation (redux) from the application (accessing data). Now, I understand that the hooks provided by react-redux aren't supposed to be a replacement for connect but the usage of hooks within the context of Redux feels almost like an antipattern to me.
Hooks does (subjectively) provide a nicer API and reduces boilerplate, but it - IMO - encourages bad design decisions that leads to a more tight coupling of redux and components that reduces usability, testability and violates the SRP. Also, hooks comes with a few potential pitfalls that aren't obvious.
The mitigating factor to the tight coupling is that there often is a de-facto coupling to redux even if there isn't a programmatic one. Also, there is nothing stopping you from creating a hooks based HoC (something like https://github.com/reduxjs/react-redux/pull/1065 (which i really like BTW)), but since there is already connect, what's the point?
I really want to like react-redux hooks and given the widespread adoptation of it amongst my peers I guess there's something I'm missing. So if anyone of you would like to enlighten me and have a productive (though late) discussion regarding this it would be awesome.
Thanks for maintaining this awesome lib!

The easiest thing you could do, if coupling is such a concern, is to just break out the Redux hooks to a separate component that wraps a component with the non-Redux stuff in it.
Otherwise, you can just stick with connect. There's no plans to ever get rid of it and it still works perfectly fine.

@timdorr
Thanks for your answer.

The easiest thing you could do, if coupling is such a concern, is to just break out the Redux hooks to a separate component that wraps a component with the non-Redux stuff in it.

Yeah, as I outlined I already reached this conclusion;

Also, there is nothing stopping you from creating a hooks based HoC (something like #1065 (which i really like BTW)), but since there is already connect, what's the point?

but I was hoping to have a discussion regarding this on a theoretical level since I have a few reservations regarding the recent adoptation of hooks as a de-facto replacement of connect, even though it's not.
If you think such a discussion is valuable, please re-open this issue, othervise thanks for your time and interest.

We've already had these discussions. Check out #1252 and #1179.

@timdorr
Thanks again.
I did read those and other issues before opening this one, but did not catch the "should we use hooks" discussion, but rahter the ones focusing on "how should we use hooks", which is actually where my original concern comes from, that this pattern is being accepted as a must-have on face value, while I'm arguing it might actual be harmful and an architectural regression.
I understand I'm a bit late to the party and that there will be no significant changes to your API. I was hoping at most to get educated and for some clarifications in your documentation regarding when it's appropriate to use hooks and what potential issues there might be inm addition to the technical ones.
Are there any agreement with these sentiments and is there any interest for such documentation changes?

Not really. You don't have to use hooks if you don't want. That choice is up to you.

Alright. Thanks for the conversation :+1:

I specifically addressed this kind of question in my blog post Thoughts on React Hooks, Redux, and Separation of Concerns, and again in my recent React Boston 2019 talk on Hooks, HOCs, and Tradeoffs (which is based on the blog post).  Please read through those.

@markerikson thanks for the additional info. I will read and watch those!

@markerikson I've read your first blogpost and it echoes my thoughts almost to the letter! Good write-up, and I guess it boils down to making a conscious tradeoff, just as you and @timdorr pointed out.
Very weird I did not find it while googling though, I searched quite a lot. If it isn't already, I think you should link to it from the docs.
The only thing I disagree with you about is that I (possibly misinterpreted you) took it that you somehow equated usage of react hooks (which I in general promote over the old state) to usage of react-redux hooks which I think is quite different.

I just put up the post a few weeks ago, so who knows how much SEO juice it has.
I was generally equating React-Redux hooks to React hooks in general, and especially with any custom data management hooks.
Overall, any use of a useContext() will effectively couple that component to the corresponding <Context.Provider>.  That includes useSelector(), or a roll-your-own state+context combo.
Similarly, useEffect() directly pushes you towards handling data fetching inside a component, vs separating that out to another component.
So yes, I'm making the point that hooks push you towards "do it all in one place", vs separating that into multiple components, and React-Redux hooks are a specific example of that behavior.

Alright, fair enough, I see your point. PR will follow (tomorrow probably)

PR is here: #1405
Thanks for the conversation. I feel that I acheived both my objections as I now have a better understanding of the trade offs when using hooks and that the docs might reflect these concerns in some manner. Thanks for taking your time.


Nuxtjs: OrbitControls.js encountered an unknown camera type

Describe the bug
I added OrbitControls, and when scrolling I get the following error
WARNING: OrbitControls.js encountered an unknown camera type - dolly/zoom disabled.

Make it impossible to scroll to zoom in/out.

Reproduction
https://stackblitz.com/edit/nuxt-starter-3nnslu?file=package.json
Steps to reproduce
No response
System Info
See https://stackblitz.com/edit/nuxt-starter-3nnslu?file=package.json

Used Package Manager
npm
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

Potentially fixed by #47

Reproduction link is using v1.1.9 so it's still an issue.

Seems like it only happens in dev mode, similar issue on R3F . @HuakunShen when you build and preview the error is gone 🤔

Possible work-around is to import anything from three in your project.
import { Vector3 } from 'three'

That seems to force the deduping of three, I will try to find a better solution

Possible work-around is to import anything from three in your project.
import { Vector3 } from 'three'

That seems to force the deduping of three, I will try to find a better solution

@alvarosabu Import something from 'three' doesn't seem to work. But in production mode it works fine.

@HuakunShen are you sure? https://stackblitz.com/edit/nuxt-starter-mt4nkb?file=app.vue

@HuakunShen are you sure? https://stackblitz.com/edit/nuxt-starter-mt4nkb?file=app.vue

It is weird. I did line by line comparison, the bug may come from lang="ts".
In the example you provide, if you add lang="ts" to script, and remove node_modules and reinstall dependencies. It should reproduce the error.

I'm afraid typescript has nothing to do with the actual issue.

Is a duplicate on three imports

@alvarosabu Right, when i use typescript I see a warning of duplicate three imports.
In my own app, if I remove typescript from the component, the problem is solved. But no idea why this happens. Still hope there is a proper fix.

@alvarosabu The problem seems to be gone. The same reproduction https://stackblitz.com/edit/nuxt-starter-3nnslu?file=package.json works in development mode. I didn't upgrade any package.


agm/snazzy-info-window AOT Runtime Issue

Getting error in @agm/snazzy-info-window/directives/snazzy-info-window.js
ERROR Error: Uncaught (in promise): TypeError: System.import is not a function

TypeError: System.import is not a function
at snazzy-info-window.js:85
at ZoneDelegate.invoke (zone.js:391)
at Object.onInvoke (core.es5.js:3890)
at ZoneDelegate.invoke (zone.js:390)
at Zone.run (zone.js:141)
at zone.js:831
at ZoneDelegate.invokeTask (zone.js:424)
at Object.onInvokeTask (core.es5.js:3881)
at ZoneDelegate.invokeTask (zone.js:423)
at Zone.runTask (zone.js:191)
at snazzy-info-window.js:85
at ZoneDelegate.invoke (zone.js:391)
at Object.onInvoke (core.es5.js:3890)
at ZoneDelegate.invoke (zone.js:390)
at Zone.run (zone.js:141)
at zone.js:831
at ZoneDelegate.invokeTask (zone.js:424)
at Object.onInvokeTask (core.es5.js:3881)
at ZoneDelegate.invokeTask (zone.js:423)
at Zone.runTask (zone.js:191)
at resolvePromise (zone.js:783)
at resolvePromise (zone.js:754)
at zone.js:831
at ZoneDelegate.invokeTask (zone.js:424)
at Object.onInvokeTask (core.es5.js:3881)
at ZoneDelegate.invokeTask (zone.js:423)
at Zone.runTask (zone.js:191)
at drainMicroTaskQueue (zone.js:595)
at

Package Version
"angular/core": "~4.3.1",
"agm/core": "1.0.0-beta.2",
"agm/snazzy-info-window": "1.0.0-beta.2",
"snazzy-info-window": "^1.1.0"

The error has nothing to do with AOT. It has something to do with Systemjs. Can you provide more details?

Moved my project to @angular/cli and is working fine now.


Problem with self-signed/fabric fortigate SSL certificate

Error: API connectivity test failed, Get "https://router:8443/api/v2/monitor/system/status": x509: certificate is not valid for any names, but wanted to match router
Probe of "https://router:8443" failed, took 0.114 seconds

This is an issue with your system setup.


fusera 0.0.15 Segementation Violation

From Adam Tebbe<EMAIL_ADDRESS>[ec2-user@ip-10-66-48-122 ~]$ fusera mount --token /home/ec2-user/prj_16421.ngc --accession "SRR8003979" --location s3.us-east-1 ~/studies -v
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x95bc7d]
goroutine 1 [running]:
github.com/mitre/fusera/cmd.mount(0xfe5420, 0xc00002e400, 0x1, 0x8, 0x0, 0x0)
/home/travis/gopath/src/github.com/mitre/fusera/cmd/mount.go:158 +0x1cd
github.com/mitre/fusera/vendor/github.com/spf13/cobra.(*Command).execute(0xfe5420, 0xc00002e380, 0x8, 0x8, 0xfe5420, 0xc00002e380)
/home/travis/gopath/src/github.com/mitre/fusera/vendor/github.com/spf13/cobra/command.go:762 +0x473
github.com/mitre/fusera/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xfe5680, 0xc0001b7f88, 0x407440, 0xc000094058)
/home/travis/gopath/src/github.com/mitre/fusera/vendor/github.com/spf13/cobra/command.go:852 +0x2fd
github.com/mitre/fusera/vendor/github.com/spf13/cobra.(*Command).Execute(0xfe5680, 0x0, 0x0)
/home/travis/gopath/src/github.com/mitre/fusera/vendor/github.com/spf13/cobra/command.go:800 +0x2b
github.com/mitre/fusera/cmd.Execute()
/home/travis/gopath/src/github.com/mitre/fusera/cmd/root.go:63 +0x2d
main.main()
/home/travis/gopath/src/github.com/mitre/fusera/main.go:36 +0x20

Dear fusera team,
I have similar problem with both fusera 0.0.15 and 0.0.16. When I run fusera mount --token prj_19780.ngc --accession "SRR8228298" --location s3.us-east-1 -f "cram,crai" ~/studies I get the following error:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x95bc7d]

goroutine 1 [running]:
github.com/mitre/fusera/cmd.mount(0xfe5420, 0xc000165320, 0x1, 0x9, 0x0, 0x0)
	/home/travis/gopath/src/github.com/mitre/fusera/cmd/mount.go:158 +0x1cd
github.com/mitre/fusera/vendor/github.com/spf13/cobra.(*Command).execute(0xfe5420, 0xc000165290, 0x9, 0x9, 0xfe5420, 0xc000165290)
	/home/travis/gopath/src/github.com/mitre/fusera/vendor/github.com/spf13/cobra/command.go:762 +0x473
github.com/mitre/fusera/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xfe5680, 0xc00019bf88, 0x407440, 0xc000076058)
	/home/travis/gopath/src/github.com/mitre/fusera/vendor/github.com/spf13/cobra/command.go:852 +0x2fd
github.com/mitre/fusera/vendor/github.com/spf13/cobra.(*Command).Execute(0xfe5680, 0x0, 0x0)
	/home/travis/gopath/src/github.com/mitre/fusera/vendor/github.com/spf13/cobra/command.go:800 +0x2b
github.com/mitre/fusera/cmd.Execute()
	/home/travis/gopath/src/github.com/mitre/fusera/cmd/root.go:63 +0x2d
main.main()
	/home/travis/gopath/src/github.com/mitre/fusera/main.go:36 +0x20

I have followed the installation guideline and installed v0.0.16 with the provided script. I tried to run the command with v0.0.15 downloaded from releases page but I got the similar error, and older versions don't seem to have --token option. Is it a bug or I'm doing something wrong? I am using AWS ec2 and I've tried different accession IDs, but I couldn't mount any of them.
I appreciate your help,
Mehrdad

Hi Mehrdad,
Assuming you are on aws, please send output of:
curl -s -X POST -F<EMAIL_ADDRESS>" "https://www.ncbi.nlm.nih.gov/Traces/sdl_test/1/retrieve?acc=SRR8228298&location=s3.us-east-1&meta-only=no"
Assuming you are on GCS, use location=gs.us, and send results.
Also,  please download/try version v0.0.14. v15 and v16 have seen very little action.  In lieu of –token use –ngc.
Regards,
Saul
From: Mehrdad Bakhtiari<EMAIL_ADDRESS>Reply-To: mitre/fusera<EMAIL_ADDRESS>Date: Sunday, March 31, 2019 at 10:10 PM
To: mitre/fusera<EMAIL_ADDRESS>Cc: "Kravitz, Saul A."<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: [EXT] Re: [mitre/fusera] fusera 0.0.15 Segementation Violation (#135)
Dear fusera team,
I have similar problem with both fusera 0.0.15 and 0.0.16. When I run fusera mount --token prj_19780.ngc --accession "SRR8228298" --location s3.us-east-1 -f "cram,crai" ~/studies I get the following error:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x95bc7d]
goroutine 1 [running]:
github.com/mitre/fusera/cmd.mount(0xfe5420, 0xc000165320, 0x1, 0x9, 0x0, 0x0)
    /home/travis/gopath/src/github.com/mitre/fusera/cmd/mount.go:158 +0x1cd

github.com/mitre/fusera/vendor/github.com/spf13/cobra.(*Command).execute(0xfe5420, 0xc000165290, 0x9, 0x9, 0xfe5420, 0xc000165290)
    /home/travis/gopath/src/github.com/mitre/fusera/vendor/github.com/spf13/cobra/command.go:762 +0x473

github.com/mitre/fusera/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xfe5680, 0xc00019bf88, 0x407440, 0xc000076058)
    /home/travis/gopath/src/github.com/mitre/fusera/vendor/github.com/spf13/cobra/command.go:852 +0x2fd

github.com/mitre/fusera/vendor/github.com/spf13/cobra.(*Command).Execute(0xfe5680, 0x0, 0x0)
    /home/travis/gopath/src/github.com/mitre/fusera/vendor/github.com/spf13/cobra/command.go:800 +0x2b

github.com/mitre/fusera/cmd.Execute()
    /home/travis/gopath/src/github.com/mitre/fusera/cmd/root.go:63 +0x2d

main.main()
    /home/travis/gopath/src/github.com/mitre/fusera/main.go:36 +0x20

I have followed the installation guideline and installed v0.0.16 with the provided script. I tried to run the command with v0.0.15 downloaded from releases page but I got the similar error, and older versions don't seem to have --token option. Is it a bug or I'm doing something wrong? I am using AWS ec2 and I've tried different accession IDs, but I couldn't mount any of them.
I appreciate your help,
Mehrdad
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mitre/fusera/issues/135#issuecomment-478411783, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ajfik11v6ZZLxLvCMBZB3paIFvaeqqa0ks5vcWpPgaJpZM4cMBOK.

This is the output of the curl command:
[
    {
        "accession": "SRR8228298",
        "status": 200,
        "message": "ok",
        "files": [
            {
                "objectId": "14393373",
                "objectType": "remote",
                "name": "GTEX-PW2O-0526-SM-2I3DX.Aligned.sortedByCoord.out.patched.cram",
                "size": "3987118900",
                "md5": "20686cf92b43b17ba28112bc7b1cbc96",
                "type": "cram",
                "service": "s3",
                "link": "https://nih-nhgri-datacommons.s3.amazonaws.com/gtex_v7/rnaseq/GTEX-PW2O-0526-SM-2I3DX.Aligned.sortedByCoord.out.patched.cram?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJBXEMGZZHIM6WKMQ%2F20190401%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190401T030914Z&X-Amz-Expires=216000&X-Amz-SignedHeaders=host&phid=CC9523F0CA17F6510000000000020002&project_id=19780&x-amz-request-payer=requester&X-Amz-Signature=1677ecfe4e05f0eb91fcfd789553a4f3ab0883512a4dd86e180e2154d8fa1238",
                "region": "us-east-1",
                "expirationDate": "2019-04-01T05:09:12Z"
            },
            {
                "objectId": "14393374",
                "objectType": "remote",
                "name": "GTEX-PW2O-0526-SM-2I3DX.Aligned.sortedByCoord.out.patched.cram.crai",
                "size": "167683",
                "md5": "190b102bed27a64241971ccbb808739b",
                "type": "crai",
                "service": "s3",
                "link": "https://nih-nhgri-datacommons.s3.amazonaws.com/gtex_v7/rnaseq/GTEX-PW2O-0526-SM-2I3DX.Aligned.sortedByCoord.out.patched.cram.crai?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJBXEMGZZHIM6WKMQ%2F20190401%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190401T030914Z&X-Amz-Expires=216000&X-Amz-SignedHeaders=host&phid=CC9523F0CA17F6510000000000020002&project_id=19780&x-amz-request-payer=requester&X-Amz-Signature=cec0d25330a49497dd7c2c45b11682e604c5f2fefdabb2af4a37c25e710a024c",
                "region": "us-east-1",
                "expirationDate": "2019-04-01T05:09:12Z"
            }
        ]
    }
]

@saulakravitz
I just found that if I launch my instance on us-east-1, I can mount the data if I don't specify --location. If I use --location s3.us-east-1 I get the error.

I do sincerely apologize for this. Location has now been fixed in v0.0.17. Alternatively, v0.0.14 is also still a valid version of Fusera as v0.017 was not suppose to affect users...


Update dependencies and migrate to null-safety

I was able to successfully migrate the latest version of the plugin to null-safety and confirmed that I was able to upload without issue. However, I am not familiar enough with the plugin itself so I am not sure if the classes and fields I set as non-null will hold with the android and iOS platform interface. Additionally, I had to remove the integration_test dependency used for testing because it currently does not support null-safety. Finally, I was unable to migrate the example app to null-safety because of strange import issues with VSCode, so I only changed a few items.
The changes I made definitely need to be reviewed for consistency and maintainability.

@aaqibism Thank you for the PR. Could you possibly add instructions how to access the fork within the description of the PR so users can fetch it until it's merged.
We have to wait for integration_test to be ready and reactivate it. The test suite is essential for this project.


Convert string formatting to f-strings

Since this project is Python 3.6+, string formatting could just as well use the faster and more convenient f-strings.
This was a mechanical conversion with pyupgrade and flynt, followed up by some manual fixups.

merging, thank you


Template update to restructure postActions

This updates the templates so that dependencies like ASP.NET Core integration are implicit in project file scaffolding and are not handled via postActions.
Diff gist

Converting to draft as we need to fix some things in the templates first.


Rename CRD

Before the first release, we should rename our CRD to RuntimeComponent.

@arthurdm The 'base' library/interface is called BaseApplication. Should we also change that to BaseComponent?

good idea @leochr - I think we should.

Done


Efficient WuHostServe is buggy

If you call WuHostServe with -1 for the timeout, the most efficient mode where the thread sleeps when there is nothing to do, it's buggy. It results in pruning clients too early, because the dt delta time can end up very large, far larger than the 8s max-ttl set for a client.
It should be documented that the sleep should be below the heartbeat time (4s), as outgoing heartbeats don't flow either in the efficient mode.

(the lib is also not thread-safe, but I have local mods for that)


Blip radar_centre is flipped in-game

This is an original bug that's present in all 3 games.
Actual texture:

In-game:

I'll have to check in the code but could it not be a design decision? Does it result in quality degradation or something? I'm asking because this is the one thing that's rather easy to account for in mods, so maybe it's a complete non-issue.

I'll have to check in the code but could it not be a design decision? Does it result in quality degradation or something? I'm asking because this is the one thing that's rather easy to account for in mods, so maybe it's a complete non-issue.

I think it's just an oversight, which never got caught because the original texture was just white. But as far for quality degradation? I can hardly see any if it all tbh, but still would be a nice fix.


Update tools - Use Latest Gluegun

Dependency updates and now use pluralize from inside gluegun instead (thanks @ryanlntn)
https://github.com/infinitered/gluegun/pull/289

Looks to me like latest gluegun works great.


adds homegrow2 (improved)

improved version of homegrow that allows client to use a string pool, which leads to significant performance improvement

I guess it's time for me to take a look at this repo again!

Thanks for the contribution and I'll get back to you soon.


Can't get indexed on Google

Hello Fruition lovers!
I've recently tried to add a new Frutionized website (royangenda.fr) to Google Search Console, but can't get my website indexed for unknown reasons… I already have two Fruitionized websites running with the same hosting provider, and have managed to index them without any issue. I don't understand what is causing trouble here.
Would you have any hint or clue?
Many thanks in advance!
Kind regards,
Philip

Hey @Ph15 any update on this? Did you manage to fix it?
I have the same issue..

Hi cyrilf!
No news on my end...!
— Phil

Le 26 août 2022 à 13:00, cyrilf @.***> a écrit :

Hey @Ph15 any update on this? Did you manage to fix it?
I have the same issue..
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

👍🏾, same issue here.

Hello, May 2023. The same problem. Does anyone have a solution?

Is anyone getting the same error in English?
It seems the AFFICHER button in the original error message might be offering to try again and show more info about the attempt. Does it?

Кто-нибудь получает ту же ошибку на английском языке?
Похоже, что AFFICHERкнопка в исходном сообщении об ошибке может предлагать повторить попытку и показывать дополнительную информацию о попытке. Имеет ли это?

AFFICHER  button. These are the results of the check

AFFICHER  button. These are the results of the check

?

@gojomo I just wanted to write that the button offers to try scanning again. But indexing still doesn't work.


Remove some "good words"

They don't make sense in the context or they actually mean the opposite
to a good word.

Thank you!


Analyzer Feedback from IntelliJ

Analyzer Feedback from IntelliJ
Version information

IDEA IC-191.6183.87
2.2.0-edge.0a7dcf17eb5f2450480527d6ad1e201fb47f1e36
IC-191.6183.87, JRE 11.0.2+9-b159.30x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14.4, screens 2560x1440  Retina

Exception
Dart analysis server, SDK version 2.2.0-edge.0a7dcf17eb5f2450480527d6ad1e201fb47f1e36, server version 1.23.0, error: Captured exception
NoSuchMethodError: The method 'refresh' was called on null.
Receiver: null
Tried calling: refresh(Instance of 'DeclarationsContext')
#0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:50:5)
#1      DeclarationsTracker._performChangeFile (package:analyzer/src/services/available_declarations.dart:611:15)
#2      DeclarationsTracker.doWork (package:analyzer/src/services/available_declarations.dart:473:7)
#3      CompletionLibrariesWorker.performWork (package:analysis_server/src/domains/completion/available_suggestions.dart:177:13)
<asynchronous suspension>
#4      AnalysisDriverScheduler._run (package:analyzer/src/dart/analysis/driver.dart:2125:35)
<asynchronous suspension>
#5      AnalysisDriverScheduler.start (package:analyzer/src/dart/analysis/driver.dart:2075:5)
#6      new AnalysisServer (package:analysis_server/src/analysis_server.dart:213:29)
#7      SocketServer.createAnalysisServer (package:analysis_server/src/socket_server.dart:86:26)
#8      StdioAnalysisServer.serveStdio (package:analysis_server/src/server/stdio_server.dart:37:18)
#9      Driver.startAnalysisServer.<anonymous closure> (package:analysis_server/src/server/driver.dart:526:21)
#10     _rootRun (dart:async/zone.dart:1124:13)
#11     _CustomZone.run (dart:async/zone.dart:1021:19)
#12     _runZoned (dart:async/zone.dart:1516:10)
#13     runZoned (dart:async/zone.dart:1463:12)
#14     Driver._captureExceptions (package:analysis_server/src/server/driver.dart:605:12)
#15     Driver.startAnalysisServer (package:analysis_server/src/server/driver.dart:524:7)
#16     Driver.start (package:analysis_server/src/server/driver.dart:427:7)
#17     main (file:///b/rr/tmpgY2JrN/w/src/third_party/dart/pkg/analysis_server/bin/server.dart:12:11)
#18     _AsyncAwaitCompleter.start (dart:async/runtime/libasync_patch.dart:49:6)
#19     main (file:///b/rr/tmpgY2JrN/w/src/third_party/dart/pkg/analysis_server/bin/server.dart:10:10)
#20     _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:298:32)
#21     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

For additional log information, please append the contents of
file:///private/var/folders/s3/_qlthkg52_qgmsknpmdwx9yh0000gp/T/report.txt.

Duplicate of https://github.com/dart-lang/sdk/issues/36522


LICENCE

It will be very much appreciated if you could add a Licence to this project. Thank you.

Hello @faresbs
I have added an MIT License. I hope that is satisfactory.

Hi @tamerthamoqa,
Yes, thank you.


Permission is set but, not working

I set the worldedit permission to true for the WildHearts rank and its not working. Also tp/eco  isnt working for any rank for Mod+

I am having the same  issue on my server as well!

Use the verbose command to debug further.
https://github.com/lucko/LuckPerms/wiki/Verbose

Funny. Verbose didn’t help me. My server host helped me better on this. They said to do /lp user instead of group which it worked. and do permissions individually on each player. I don’t fully get or understand verbose on how it’s supposed to help me and my server


odafileconverter: <IP_ADDRESS> -> <IP_ADDRESS>

updated the package
migrated to qt6 since the upstream now uses it
moved version inside mkDerivation and made it recursive - should allow to overrideAttrs properly and not break build (previous approach still used the old version so the whole installPhase needed to be overridden)
added myself as a maintainer (if ok with you @nagisa ?)
moved to by-name in a separate commit

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 366159

x86_64-linux

:white_check_mark: 1 package built:

odafileconverter


[chore] update ember-auto-import@1 -> ember-auto-import@2

I followed the guide https://github.com/ef4/ember-auto-import/blob/main/docs/upgrade-guide-2.0.md to update properly.
This should fix https://github.com/TryGhost/Admin/pull/1965 and also help us bump other major versions of deps that are using ember-auto-import@2.
Please include a description of your change & check your PR against this list, thanks!

[x] There's a clear use-case for this code change
[x] Commit message has a short title & references relevant issues
[x] The build will pass (run ember test from the repo root - will be core/client if working from the submodule in Ghost).

More info can be found by clicking the "guidelines for contributing" link above.

Ooh, that required less to get upgraded than I was expecting, thanks!
Unfortunately it's hit the main problem with this upgrade which is how our custom dev/prod setup works and possibly how Ghost serves the admin files. When running in dev we now get a lot of 404 errors because files aren't copied into the right places

I'll try and dive into this when I get a moment

@kevinansfield how did you test the dev/prod setup? You just linked to the main ghost-cli instance right?

Hey @gabrielcsapo 👋 Apologies, I missed your last message here. The way I hit the problems in dev was running yarn dev to get Ghost w/ Admin started up locally. Are you working with a local source install following these docs?
We're back to our more regular development cycle now so I'll be able to help with progress and merge. If we can keep the migration PRs smaller/more focused that will help with testing as we go - our test coverage in Admin still isn't great for some areas so I'll be testing manually/adding tests where needed.

I am following those instructions, I will look into the failures today.

The way Ghost serves the Admin is by serving static files from the /assets folder and selecting a dev vs prod template:

https://github.com/TryGhost/Ghost/blob/main/core/server/web/admin/app.js#L19-L22
https://github.com/TryGhost/Ghost/blob/main/core/server/web/admin/controller.js#L32

My assumption is that we'll want to change this so we have separate dev and prod folders that contain the full build output. That way we could drop the custom "minifiedInProductCss"/"minifiedInProductionJs" content blocks and adjust the asset-delivery postBuild hook to copy the whole build folder across to the correct dev/prod folder inside Ghost.

Codecov Report

Merging #2252 (0a504cf) into main (880bd1c) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2252      +/-   ##
==========================================
- Coverage   39.27%   39.25%   -0.03%
==========================================
  Files         615      615
  Lines       24702    24702
  Branches     4319     4319
==========================================
- Hits         9702     9697       -5
- Misses      15000    15005       +5

Impacted Files
Coverage Δ

app/components/gh-site-iframe.js
46.00% <0.00%> (-4.00%)
:arrow_down:

app/controllers/offer.js
44.23% <0.00%> (-0.93%)
:arrow_down:

app/components/gh-image-uploader.js
94.66% <0.00%> (-0.67%)
:arrow_down:

app/helpers/event-name.js
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


chore: update gelato key

Description

Rotate 1balance key
Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[ ] Refactoring
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)
Fixes
Related pull request(s)

Handled in https://github.com/connext/monorepo/pull/6215


Problem using camera

Hi
Just working through changing our bottom sheets to use this. Looks really good, but just have a small sticking point at the moment with iOS only (works fine in Android).
Our use of this bottom sheet allows the user to take a photo. What I found was that I had to dismiss the bottom sheet for the camera to work (which makes sense). But, I am having trouble showing the bottom sheet again after the photo is taken. I have tried a few different things but here is my current code:
        bool hidden = await ClosePostBottomSheet();

        bool photoTaken = await TakePhoto();

        if (photoTaken)
            _ = await ShowPostBottomSheet(true);

ShowPostBottomSheet just has this:
 _postPage = new SocialPostBottomSheet(PageUtil.PageBindingContext);
await   _postPage.ShowAsync(Window);
return true; // <- Never reaches this line

So even with all these awaits in place it refuses to show. Or to be more precise, it shows for a split second then vanishes again.
If I wait a couple of seconds and tap the button to show the sheet again then it shows, but this involves user input.
Any thoughts on what I should be doing?
Thanks

I'm not too sure about this one. What do you use to pick the photo?
My guess is that there may be another presented view controller used for the camera and it causes issues with the controller of the sheet. But hard to investigate more just from that

Just using MediaGallery to take photos. I think you are right about another view controller being launched for this...

Looks like a new problem in .NET 8. I have a bottom sheet which has a button which shows a popup (DisplayAlert). Used to work in .NET 7 but in .NET 8 the popup doesn't show. The code just hangs. I suspect (wild guess) that it is for the same reason.


Zulip tray icon gone (on Manjaro Linux using XFCE)

Since a few days back, Zulip no longer displays any tray icon when running. This makes it hard to remember that it's still running when minimized and easy to miss important notifications.
I'm using package zulip-desktop 5.0.0-1 on Manjaro Linux with XFCE.
I tried clicking "View -> Toggle Tray Icon" in the menu, toggling "Desktop Settings -> General -> Show app icon in system tray", and also manually changing the "trayIcon" flag in .config/Zulip/config/settings.json, but none of this made any difference either immediately or after a restart (both of Zulip or of my whole machine). I've also tried starting zulip with dbus-lunch but that didn't make a difference either. I looked in the Dev Tools console, but didn't find anything that seems related to this problem.
So what can I do to bring back the Zulip tray icon?

@catalin-hritcu This is occuring due an upstream electron issue which occurs in some Linux distros.
The fix for Manjaro XFCE is given here . Please try that out and if it works for you please let us know.

@abhigyank Thanks a lot, this worked like a charm for me.

Good to know.
This issue can be closed.

This comment has some more fixes for other distros (such as Mint, which solved the issue for me). Just leaving it here for people who look for a fix.


Feature: Show weapon skills and spell school hit values in UI

Completed. Can be viewed by hovering "Melee Hit"


maybe add pandas-profiling

Hi, there is also another popular Python package which is hard to find due to "interesting" naming :D
https://github.com/pandas-profiling/pandas-profiling

Done, thanks.


iPhone sometimes freezes when rearranging icons in jailbroken state

This happens intermittently when I'm moving an app icon a great distance, like from the last page (I have around 10 pages of apps) to the first. Once it gets to the first page, the system locks up and I have to do a forced-restart of the phone and rejailbreak.
At this point I'm only rearranging icons while in a jailed state to get around this issue.
No tweaks installed so this is definitely an Undecimus issue.
iPhone X on 12.1.1 b3.

My device resprings if i try to move an icon while jailbroken


ValueFormat uses most copied stack exchange code in the world, which also has a bug

Bug details
The human-readable byte size converter function in ValueFormat uses the most popular stack exchange code snippet in the world, but close to (but not exceeding) boundary thresholds it tends to perform incorrectly due to precision errors in the math involved.
The fix
The original author (Andreas Lundblad) has posted explanations of the issue and the fix here: https://programming.guide/worlds-most-copied-so-snippet.html

For a potential fix see #2148