[Feature] Option to prompt renaming through nvim's prompt instead of UI

Describe the issue
Great project, I've been looking this type of plugin for a long time!
I personally would like it if there was a option to prompt the rename through the command input (not sure what its called) instead of a popup. It's just a personal thing, as I'm not a huge fan of having the popup.
Proposal
It would be nice to have something like in the screenshot below

Thanks for submitting feedback and for the proposal! I assume you already used vim.lsp.buf.rename() (since it kind does what you want), but would like to also have reference highlighting/the word to be renamed displayed.
Is this right? I am trying to get a better idea as to how this feature should be designed.

I assume you already used vim.lsp.buf.rename() (since it kind does what you want), but would like to also have reference highlighting/the word to be renamed displayed.

No I did not try vim.lsp.buf.rename() because I don't think I saw in the README. But after trying it out, I have confirm that what you have mentioned is the same feature I am requesting :)

Just added your proposed feature to the develop branch (4ef89d5). Feel free to try it out or wait until I publish v2.0.0, around Sunday (or when I finish the remaining 2 issues). Thanks for your patience!

Thank you! I really appreciate you taking the time to implement this feature!!

With pleasure! Thanks for suggesting it!


Add QR code for participants to join via their mobile

This will allow participants to use their mobile to vote

Mobile-friendly means connection-friendly; a bad mobile connection could affect the voting process and thus the poker outcome.

Won't be adding new features for now. Thanks


Create testcase that reproduces wrong distinction.

https://github.com/realm/realm-cocoa/issues/5791

Thanks! With this repro case I was able to track down the problem and made a PR to fix it: https://github.com/realm/realm-core/pull/3102


fix(pay_ios): allow a lower iOS version than 12 to use the plugin

I have a Flutter app that uses iOS 11 as a minimum target.
By adding this plugin I receive a lot of errors about how some parts of the code require iOS 12.
This can be fixed very easily with a bunch of #available checks.
This fixes: https://github.com/google-pay/flutter-plugin/issues/88, https://github.com/google-pay/flutter-plugin/issues/36

@googlebot I signed it!

Also, the target version in the example can be set to anything <12.0 (project.pbxproj). I'd suggest we go with 11.0.

Also, the target version in the example can be set to anything <12.0 (project.pbxproj). I'd suggest we go with 11.0.

FIxed in ca9d1002773af4c7a39cf53dfea224761dbb9d30

@JlUgia pushed fixes addressing your comments

LGTM


Support DBIX

From block 90000 we support eip150,155,158. Please, add DBIX node in the main nodes, dbixAbi.json and dbixTokens.json

mail<EMAIL_ADDRESS>website: https://arabianchain.org

I believe this is outdated, feel free to let me know otherwise


Vagrant salt provisioner is broken

Vagrant's salt provisioner is broken in 14.12. This file:
/nix/store/hash-vagrant-1.6.5/opt/vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/provisioners/salt/bootstrap-salt.sh

Is executed on guest machine, but it has changed path to shell:
#!/nix/store/hash-bash-4.3-p30/bin/sh -

So it fails with error:
bash: /tmp/bootstrap_salt.sh: /nix/store/hash-bash-4.3-p30/bin/sh: bad interpreter: No such file or directory

Auch. Another reason to use /usr/bin/env bash

@iElectric although using /usr/bin/env sh is a good idea, I assume the issue is due to nixpkgs patching a script that it shouldn't ;)

@rbvermaa this is happening again

pkgs.vagrant.overrideDerivation (o: {
  preFixup = ''
    chmod -x $out/lib/ruby/gems/2.4.0/gems/vagrant-2.0.2/plugins/provisioners/salt/bootstrap-salt.sh
  '';
  postFixup = ''
    chmod +x $out/lib/ruby/gems/2.4.0/gems/vagrant-2.0.2/plugins/provisioners/salt/bootstrap-salt.sh
  '';
})


the dependency conflict

Hi! I tried to install library, but I have a problem.

Also I tried resolve this conflict by myself, so I tried to install networkx manualy with specific version, but it is impossible. You can see it on screenshots (python couldn't find new version of networkx).

IDK... may be this problem appears only on my JupyterHub...

I think it resolved
The problem was that I use Python 3.6


Introduce offset for created-timestamp

Hi there,
I'm running into problems where the timestamp used for creating the digest is in the future from the api-server side's perspective.
Even though the client and the server are using the same NTP time synchronization services, sometimes the client is +1 second beyond. This results in an error.
Any chance of introducing a (negative) offset-configuration in your middleware?
I did a quick fix like this, to be sure the client's timestamp is 30s in the past:
$createdAt = date('c', time()-30);

Best regards

Hi,
added a functionality to set the createdAt time by a setter optionally:
$wsse->setCreatedAt(new \DateTime('-30 seconds'));

Best regards
Florian

Created version 4.1.0:
https://github.com/8p/guzzle-wsse-middleware/releases/tag/v4.1.0

Awesome! Thank you!

Hmm. I think the solution still have some problems...
First, I am working with your fantastic https://github.com/8p/GuzzleBundle. Unfortunately there's no easy way to apply the setCreatedAt-call to the embedded wsse middleware.
But I think the bigger problem is this: I would have to call setCreatedAt each time i'm doing a guzzle call. If I dont, and have a somewhat long(er) running process, the timestamp will eventually be quite old, which might cause another server-side exception.
What do you think about setting a "time-expression" instead of the \DateTime object? So when the attached callable is called, you create a new \DateTime()-object based on the expression. Which is "now" by default, but could be "-10 seconds" - and its just a string.
What do you think about it?

Yeah, you are right. The current implementation can lead to this problem. I like the idea of having a expression because you are very flexible with that solution 👍
I'm going to implement that.

Can you give me a hint how I would call the getCreatedAtTimeExpression() with the guzzle-bundle?
I think its not really possible without hacking the bundle: https://github.com/8p/GuzzleBundle/blob/master/DependencyInjection/GuzzleExtension.php#L123
Thanks

Yes, right now it is not supported by this bundle. I will add a possibility to set the expression in the configuration.
It would be great if you can add a feature request in the bundle repository cause the middleware has no relation to the bundle, but the bundle has a relation to this middleware. Just to cleanup everything.

Sure. Will do!


[CRD] Inject CRD version to the Autoscaler sidecar container

Why are these changes needed?
See https://github.com/ray-project/ray/pull/40357 for more details.
Related issue number
#1481
#1492
Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[x] Unit tests
[x] Manual tests
[ ] This PR is not tested :(

cc @gvspraveen


Update README.md

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

upadted the link of my profile

thanks for the merge folks


happy new year 🎉

Codecov Report

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

@@          Coverage Diff           @@
##           master      #7   +/-   ##
======================================
  Coverage    89.1%   89.1%
======================================
  Files           3       3
  Lines         101     101
  Branches       10      10
======================================
  Hits           90      90
  Misses         11      11

Flag
Coverage Δ

#ios
89.1% <ø> (ø)
:arrow_up:

#ios10
89.1% <ø> (ø)
:arrow_up:

#macos
87.12% <ø> (-1.99%)
:arrow_down:

#macos10_12
87.12% <ø> (-1.99%)
:arrow_down:

#tvos
87.12% <ø> (-1.99%)
:arrow_down:

#tvos10
87.12% <ø> (-1.99%)
: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 b6bfa5a...0757825. Read the comment docs.


Recall PreciousStones Integration Not Working

It seems that Recall can no longer take you to your fields. I should look into this.

It's working for me though.


Oracle Definitions Using YAML Schema

Currently, due to its fork of Cairo Hints, Scarb Agent uses protocol buffers to define messages shared between Cairo and an external server.
Now that we're using the YAML schema for the input and output of the Cairo program, I'm thinking of using YAML as well to define oracle requests, responses and services. This way, we have consistency with I/O, it's easier to support more complex data types, better DX, and we keep all cairo serde-related code in cairo-io-serde crate.
Here is an example of the yaml file for an oracle definitions:
schemas:
  Inner:
    fields:
      inner_field:
        type: Primitive
        name: u32
  Request:
    fields:
      w:
        type: Primitive
        name: u64
      x:
        type: Option
        inner:
          type: Message
          name: Inner
      y:
        type: Array
        item_type:
          type: Primitive
          name: i32
  Response:
    fields:
      n:
        type: Primitive
        name: u64

services:
  MyOracle:
    methods:
      oracle:
        input: Request
        output: Response

Wdyt @Gonmeso @EduPonz

I think that this is incredible and that we could also leverage the power of YAML into this to merge the configurations, like servers.json and cairo_input.yaml into a agent_config.yaml.
Also, YAML usually supports anchors (example), which let us easily duplicate data if we need to, like the current url of the Python server.
Another thing is that adding Primitive, Array or Struct its duplicating information, as this can be obtain through the definition of the YAML for example:
Array
  Request:
    fields:
      y:
        - i32

Struct
  Inner:
    fields:
      inner_field: u32 # This is also how we can define a primitive
  Request:
    fields:
      x:
        inner: Inner

Options
  Inner:
    fields:
      inner_field: Option<u32>

Servers.json
schemas:
  Inner:
    fields:
      inner_field: u32
servers:
  - name: apy
    server_url: localhost:3000/apy # Also the name should be a reference, but we should not concatenate `server_url + / + name`
  - name: balance_data
    server_url: localhost:3000/my_balance
  # Also we could make that if url is missing we take the default url plus the name in this case
  - name: ironclad_data # here it whould be `default_url + / + ironclad_data`
options:
  default_url: localhost:3000

Also, is there a possibility to do something with Oracle.lock?

This is definitely the way to go IMO. In fact, we could also provide a YAML schema so we can:

Ease the DX with autocomplete features in editors
Validate input

merge the configurations, like servers.json and cairo_input.yaml into a agent_config.yaml

I think this is something I'd do as a second step, but the less config files the better for sure.

Also, is there a possibility to do something with Oracle.lock?

Again, I'd do this later as it involves updating other projects, but I also think we should look into it.


Docs update 1.6 # 1

Fix for support on Official Repo wording
https://github.com/docker/docker/pull/12993
3efc083d4a785b2c7b1c1f862133167d5618d216
Jess Debian
https://github.com/docker/docker/pull/12801
b6cfe7ca07722cee22345602595fc8fb928dbe79
https://github.com/docker/docker/pull/12484
37b9ce61ac5aa762cf0ad34d84bc1924807a7617

ping @jfrazelle Make sure I have this right for you Jess.
ping @docker/docs-owners

perfect yayyy! thanks!!! LGTM

Checked that the machine/docs branch was present (better be sure), other changes look okay as well, so LGTM
@moxiegirl Waiting for lights to go green for good measure, but feel free to merge if you're in a hurry

For future reference, this is not the first docs update after the 1.6 release, but using the "docs update #xxx" wasn't used in prior merges :smile_cat:

Windows build failed. Windows users will need to get a proper computer to read the docs.
I'm brave; merging :smile:

Thanks @thaJeztah I really hate to merge on a broken build. It is bad practice...but right now bigger fish to fry.

@moxiegirl the broken build seemed really unrelated (iptables running out of memory) and I thought I'd save you the stress. Just blame me in this case!

yeah we should try to get in some docs tests with the apis like we talked about then the broken build would mean something :)

Lordy @thaJeztah did it sound like I was blaming anyone? I'm just bemoaning the bad practice --- mostly cause I'm always willing to slide down a slipper slope to hell.  @jfrazelle I have plans...schemes...and plans.

no worries; I'd like to merge on green lights only as well, but for the docs branch I know that the code will never be used, so....
Some tests for the docs would be great, also; skipping other tests for a docs-only PR would be a big time-saver :)


MAPL is not compiling on Frontera

Describe the bug
The spack-stack is ported to TACC Frontera (https://github.com/JCSDA/spack-stack/pull/1075). All packages are installed without any error except MAPL.
To Reproduce
Tray following steps on Frontera (note, the directories needs to be changed):
git clone -b feature/frontera --recursive https://github.com/oceanmodeling/spack-stack.git spack-stack-dev
module purge
module use /work2/06146/tg854455/frontera/spack-stack/modulefiles
module load ecflow/5.8.4
export SPACK_ROOT=/work2/01118/tg803972/frontera/spack-stack-dev/spack
source setup.sh
spack stack create env --site frontera --template ufs-weather-model --name unified-env --prefix /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install
cd envs/unified-env
spack env activate .
cd ../..
spack --color always concretize
spack --color always install --source -j3

Expected behavior
The MAPL build will fail with following error,
[+] /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/py-pip-23.1.2-wmns5x6
==> Installing mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk [68/99]
==> No binary for mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk found: installing from source
==> Fetching https://mirror.spack.io/_source-cache/archive/4b/4b82a314c88a035fc2b91395750aa7950d6bee838786178ed16a3f39a1e45519.tar.gz
Fetching tags only, you probably meant:
  git fetch --tags
==> Moving resource stage
	source: /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/resource-esma_cmake-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/
	destination: /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/ESMA_cmake
==> Ran patch() for mapl
==> mapl: Executing phase: 'cmake'
==> mapl: Executing phase: 'build'
==> Error: ProcessError: Command exited with status 2:
    'make' '-j3'

6 errors found in build log:
     1804    /opt/apps/cmake/3.24.2/bin/cmake -E touch generic/CMakeFiles/MAPL.generic.dir/AbstractComponent.F90.o.provides.build
     1805    [ 75%] Building Fortran object generic/CMakeFiles/MAPL.generic.dir/AbstractFrameworkComponent.F90.o
     1806    cd /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-
             lab6laq/generic && /opt/intel/oneapi/mpi/2021.9.0/bin/mpiifort -DBUILD_WITH_PFLOGGER -DFORTRAN_COMPILER_SUPPORTS_ASSUMED_TYPE -DFORTRAN_COMPILER_SUPP
             ORTS_FINDLOC -DH5_HAVE_PARALLEL -DHAS_NETCDF3 -DHAS_NETCDF4 -DHAVE_SHMEM -DMAPL_generic_EXPORTS -DNETCDF_NEED_NF_MPIIO -DsysLinux -I/work2/01118/tg80
             3972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/generic -I/work2/01118
             /tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/generic
              -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-
             lab6laq/include/MAPL.generic -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larj
             py2kkusw6we4juk/spack-src/include -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug
             4larjpy2kkusw6we4juk/spack-src/oomph -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhz
             uug4larjpy2kkusw6we4juk/spack-build-lab6laq/oomph -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.4
             0.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.oomph -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_
             stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/base -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/buil
             d_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/base -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-de
             v/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.base -I/work2/01118/tg803972/frontera/s
             pack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/shared -I/work2/01118/tg803972/fronte
             ra/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/shared -I/work2/01118/t
             g803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/M
             APL.shared -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/sp
             ack-src/shared/Constants -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2k
             kusw6we4juk/spack-build-lab6laq/shared/Constants -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40
             .3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.constants -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/bui
             ld_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/profiler -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cac
             he/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/profiler -I/work2/01118/tg803972/frontera/spack-stack/spa
             ck-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.profiler -I/work2/01118/tg80
             3972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/pfio -I/work2/01118/tg
             803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/pfio -I/wo
             rk2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6la
             q/include/MAPL.pfio -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6
             we4juk/spack-src/MAPL_cfio -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy
             2kkusw6we4juk/spack-build-lab6laq/MAPL_cfio_r4 -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3
             -lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL_cfio_r4 -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_s
             tage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/geom -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build
             _stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/geom -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev
             /cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.geom -I/work2/01118/tg803972/frontera/sp
             ack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/gftl-shared-1.6.1-ingeu4y/GFTL_SHARED-1.6/include/v1 -I/work2/01118/tg803972/frontera
             /spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/gftl-1.11.0-gwgzzdr/GFTL-1.11/include/v1 -I/work2/01118/tg803972/frontera/spack-st
             ack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/pflogger-1.12.0-zo4kide/PFLOGGER-1.12/include -I/work2/01118/tg803972/frontera/spack-stack/
             spack-stack-dev/envs/unified-env/install/intel/23.1.0/yafyaml-1.2.0-nkvo44x/YAFYAML-1.2/include -I/work2/01118/tg803972/frontera/spack-stack/spack-st
             ack-dev/envs/unified-env/install/intel/23.1.0/gftl-1.11.0-gwgzzdr/GFTL-1.11/include/v2 -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/e
             nvs/unified-env/install/intel/23.1.0/gftl-shared-1.6.1-ingeu4y/GFTL_SHARED-1.6/include/v2 -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-de
             v/envs/unified-env/install/intel/23.1.0/netcdf-fortran-4.6.1-o5jgqmr/include -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unifie
             d-env/install/intel/23.1.0/netcdf-c-4.9.2-g2tchrd/include -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel
             /23.1.0/esmf-8.6.0-3drpx3z/include -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/parallelio-2.6.
             2-azbavh5/include -O3 -g -march=core-avx2 -fma -align array32byte -traceback -assume realloc_lhs -qopt-report0 -align all -fno-alias -fpe3 -fp-model
             fast -fp-model source -fp-model consistent -ftz -assume noold_maxminloc -align dcommons -module ../include/MAPL.generic -fPIC -qopenmp -c /work2/0111
             8/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/generic/Abstract
             FrameworkComponent.F90 -o CMakeFiles/MAPL.generic.dir/AbstractFrameworkComponent.F90.o
     1807    [ 75%] Building Fortran object generic/CMakeFiles/MAPL.generic.dir/BaseComponent.F90.o
     1808    cd /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-
             lab6laq/generic && /opt/intel/oneapi/mpi/2021.9.0/bin/mpiifort -DBUILD_WITH_PFLOGGER -DFORTRAN_COMPILER_SUPPORTS_ASSUMED_TYPE -DFORTRAN_COMPILER_SUPP
             ORTS_FINDLOC -DH5_HAVE_PARALLEL -DHAS_NETCDF3 -DHAS_NETCDF4 -DHAVE_SHMEM -DMAPL_generic_EXPORTS -DNETCDF_NEED_NF_MPIIO -DsysLinux -I/work2/01118/tg80
             3972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/generic -I/work2/01118
             /tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/generic
              -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-
             lab6laq/include/MAPL.generic -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larj
             py2kkusw6we4juk/spack-src/include -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug
             4larjpy2kkusw6we4juk/spack-src/oomph -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhz
             uug4larjpy2kkusw6we4juk/spack-build-lab6laq/oomph -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.4
             0.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.oomph -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_
             stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/base -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/buil
             d_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/base -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-de
             v/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.base -I/work2/01118/tg803972/frontera/s
             pack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/shared -I/work2/01118/tg803972/fronte
             ra/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/shared -I/work2/01118/t
             g803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/M
             APL.shared -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/sp
             ack-src/shared/Constants -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2k
             kusw6we4juk/spack-build-lab6laq/shared/Constants -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40
             .3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.constants -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/bui
             ld_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/profiler -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cac
             he/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/profiler -I/work2/01118/tg803972/frontera/spack-stack/spa
             ck-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.profiler -I/work2/01118/tg80
             3972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/pfio -I/work2/01118/tg
             803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/pfio -I/wo
             rk2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6la
             q/include/MAPL.pfio -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6
             we4juk/spack-src/MAPL_cfio -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy
             2kkusw6we4juk/spack-build-lab6laq/MAPL_cfio_r4 -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3
             -lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL_cfio_r4 -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_s
             tage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/geom -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build
             _stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/geom -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev
             /cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/include/MAPL.geom -I/work2/01118/tg803972/frontera/sp
             ack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/gftl-shared-1.6.1-ingeu4y/GFTL_SHARED-1.6/include/v1 -I/work2/01118/tg803972/frontera
             /spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/gftl-1.11.0-gwgzzdr/GFTL-1.11/include/v1 -I/work2/01118/tg803972/frontera/spack-st
             ack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/pflogger-1.12.0-zo4kide/PFLOGGER-1.12/include -I/work2/01118/tg803972/frontera/spack-stack/
             spack-stack-dev/envs/unified-env/install/intel/23.1.0/yafyaml-1.2.0-nkvo44x/YAFYAML-1.2/include -I/work2/01118/tg803972/frontera/spack-stack/spack-st
             ack-dev/envs/unified-env/install/intel/23.1.0/gftl-1.11.0-gwgzzdr/GFTL-1.11/include/v2 -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/e
             nvs/unified-env/install/intel/23.1.0/gftl-shared-1.6.1-ingeu4y/GFTL_SHARED-1.6/include/v2 -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-de
             v/envs/unified-env/install/intel/23.1.0/netcdf-fortran-4.6.1-o5jgqmr/include -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unifie
             d-env/install/intel/23.1.0/netcdf-c-4.9.2-g2tchrd/include -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel
             /23.1.0/esmf-8.6.0-3drpx3z/include -I/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/parallelio-2.6.
             2-azbavh5/include -O3 -g -march=core-avx2 -fma -align array32byte -traceback -assume realloc_lhs -qopt-report0 -align all -fno-alias -fpe3 -fp-model
             fast -fp-model source -fp-model consistent -ftz -assume noold_maxminloc -align dcommons -module ../include/MAPL.generic -fPIC -qopenmp -c /work2/0111
             8/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/generic/BaseComp
             onent.F90 -o CMakeFiles/MAPL.generic.dir/BaseComponent.F90.o
     1809    ifort: command line warning #10121: overriding '-march=cascadelake' with '-march=core-avx2'
  >> 1810    /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/gener
             ic/AbstractFrameworkComponent.F90(27): error #6618: The INTERFACE/CONTAINS stack is full. This means that modules are being 'used' in a circular way.
     1811          end function i_AddChildComponent
     1812    ^
     1813    compilation aborted for /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkus
             w6we4juk/spack-src/generic/AbstractFrameworkComponent.F90 (code 1)
  >> 1814    make[2]: *** [generic/CMakeFiles/MAPL.generic.dir/AbstractFrameworkComponent.F90.o] Error 1
     1815    make[2]: *** Waiting for unfinished jobs....
     1816    ifort: command line warning #10121: overriding '-march=cascadelake' with '-march=core-avx2'
  >> 1817    /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-src/gener
             ic/BaseComponent.F90(17): error #6618: The INTERFACE/CONTAINS stack is full. This means that modules are being 'used' in a circular way.
     1818    contains
     1819    ^
     1820    compilation aborted for /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkus
             w6we4juk/spack-src/generic/BaseComponent.F90 (code 1)
  >> 1821    make[2]: *** [generic/CMakeFiles/MAPL.generic.dir/BaseComponent.F90.o] Error 1
     1822    make[2]: Leaving directory `/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2
             kkusw6we4juk/spack-build-lab6laq'
  >> 1823    make[1]: *** [generic/CMakeFiles/MAPL.generic.dir/all] Error 2
     1824    make[1]: *** Waiting for unfinished jobs....
     1825    /opt/apps/cmake/3.24.2/bin/cmake -E cmake_copy_f90_mod include/MAPL.griddedio/mapl_esmffieldbundleread.mod griddedio/CMakeFiles/MAPL.griddedio.dir/ma
             pl_esmffieldbundleread.mod.stamp Intel
     1826    [ 75%] Linking Fortran shared library ../lib/libMAPL.griddedio.so
     1827    cd /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-
             lab6laq/griddedio && /opt/apps/cmake/3.24.2/bin/cmake -E remove /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-st
             age-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-lab6laq/lib/libMAPL.griddedio.so
     1828    cd /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-
             lab6laq/griddedio && /opt/apps/cmake/3.24.2/bin/cmake -E cmake_link_script CMakeFiles/MAPL.griddedio.dir/link.txt --verbose=1
     1829    /opt/apps/cmake/3.24.2/bin/cmake -E touch griddedio/CMakeFiles/MAPL.griddedio.dir/FieldBundleRead.F90.o.provides.build
     1830    /opt/intel/oneapi/mpi/2021.9.0/bin/mpiifort -fPIC -O3 -g -march=core-avx2 -fma -align array32byte -traceback -assume realloc_lhs -qopt-report0 -align
              all -fno-alias -fpe3 -fp-model fast -fp-model source -fp-model consistent -ftz -assume noold_maxminloc -align dcommons  -Wl,--disable-new-dtags -sha
             red -nofor-main -Wl,-soname,libMAPL.griddedio.so -o ../lib/libMAPL.griddedio.so CMakeFiles/MAPL.griddedio.dir/DataCollection.F90.o CMakeFiles/MAPL.gr
             iddedio.dir/DataCollectionManager.F90.o CMakeFiles/MAPL.griddedio.dir/GriddedIOitem.F90.o CMakeFiles/MAPL.griddedio.dir/GriddedIO.F90.o CMakeFiles/MA
             PL.griddedio.dir/FieldBundleRead.F90.o CMakeFiles/MAPL.griddedio.dir/FieldBundleWrite.F90.o CMakeFiles/MAPL.griddedio.dir/TileIO.F90.o  -Wl,-rpath,"/
             work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/mapl-2.40.3-lab6laq/lib:/work2/01118/tg803972/fronter
             a/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/mapl-2.40.3-lab6laq/lib64:/work2/01118/tg803972/frontera/spack-stack/spack-stack-
             dev/envs/unified-env/install/intel/23.1.0/esmf-8.6.0-3drpx3z/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/
             intel/23.1.0/netcdf-c-4.9.2-g2tchrd/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/lz4-1.9.4-rl
             sip6h/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/snappy-1.1.10-lakualg/lib:/work2/01118/tg8
             03972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/zlib-ng-2.1.5-73r2prn/lib:/work2/01118/tg803972/frontera/spack-stack
             /spack-stack-dev/envs/unified-env/install/intel/23.1.0/zstd-1.5.2-bfi5mre/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified
             -env/install/intel/23.1.0/hdf5-1.14.3-e2swa7h/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/li
             bxml2-2.10.3-zoqkxlj/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/libiconv-1.17-sk4clf2/lib:/
             work2/06146/tg854455/frontera/spack-stack/miniconda-3.9.12/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/in
             tel/23.1.0/netcdf-fortran-4.6.1-o5jgqmr/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/parallel
             io-2.6.2-azbavh5/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/parallel-netcdf-1.12.3-d77ldx7/
             lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/perl-5.38.0-2czemf6/lib:/work2/01118/tg803972/fr
             ontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/gdbm-1.23-iwtilmt/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack
             -dev/envs/unified-env/install/intel/23.1.0/readline-8.2-ogycm3p/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/insta
             ll/intel/23.1.0/python-3.10.13-a3mrxft/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/expat-2.5
             .0-oe3qlpy/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/libbsd-0.11.7-3vlnl7h/lib:/work2/0111
             8/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/libmd-1.0.4-rwpgy4c/lib:/work2/01118/tg803972/frontera/spack-st
             ack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/libffi-3.4.4-ukirkmg/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/un
             ified-env/install/intel/23.1.0/libxcrypt-4.4.35-dvotae2/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel
             /23.1.0/util-linux-uuid-2.38.1-xacqijx/lib:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/c-blosc-1
             .21.5-zf4eqpz/lib64:/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/openssl-3.1.3-t22zmpn/lib64:\$OR
             IGIN/../lib64" ../lib/libMAPL.base.so ../lib/libMAPL.pfio.so ../lib/libMAPL_cfio_r4.so /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/env
             s/unified-env/install/intel/23.1.0/esmf-8.6.0-3drpx3z/lib/libesmf.so /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/inst
             all/intel/23.1.0/netcdf-fortran-4.6.1-o5jgqmr/lib/libnetcdff.so /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/i
             ntel/23.1.0/netcdf-c-4.9.2-g2tchrd/lib/libnetcdf.so ../lib/libMAPL.profiler.so ../lib/libMAPL.geom.so ../lib/libMAPL.shared.so ../lib/libMAPL.constan
             ts.so /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/esmf-8.6.0-3drpx3z/lib/libesmf.so -Wl,-rpath,/
             work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/esmf-8.6.0-3drpx3z/lib -Wl,-rpath,/work2/01118/tg8039
             72/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/netcdf-c-4.9.2-g2tchrd/lib -Wl,-rpath,/work2/01118/tg803972/frontera/sp
             ack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/netcdf-fortran-4.6.1-o5jgqmr/lib  -Wl,-rpath,/work2/01118/tg803972/frontera/spack-sta
             ck/spack-stack-dev/envs/unified-env/install/intel/23.1.0/parallelio-2.6.2-azbavh5/lib -Wl,-rpath,/work2/01118/tg803972/frontera/spack-stack/spack-sta
             ck-dev/envs/unified-env/install/intel/23.1.0/esmf-8.6.0-3drpx3z/lib -L/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/ins
             tall/intel/23.1.0/esmf-8.6.0-3drpx3z/lib -L/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/esmf-8.6.
             0-3drpx3z/lib -L/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/netcdf-c-4.9.2-g2tchrd/lib -L/work2/
             01118/tg803972/frontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/netcdf-fortran-4.6.1-o5jgqmr/lib -L/work2/01118/tg803972/fr
             ontera/spack-stack/spack-stack-dev/envs/unified-env/install/intel/23.1.0/parallelio-2.6.2-azbavh5/lib -lrt -ldl -lnetcdf -lnetcdff -lnetcdf -lnetcdf
             -lm -lpioc -m64 -mcmodel=small -pthread -threads -cxxlib -Wl,--no-as-needed  -qopenmp /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/envs
             /unified-env/install/intel/23.1.0/pflogger-1.12.0-zo4kide/PFLOGGER-1.12/lib/libpflogger.a /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/
             envs/unified-env/install/intel/23.1.0/yafyaml-1.2.0-nkvo44x/YAFYAML-1.2/lib/libyafyaml.a /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/e
             nvs/unified-env/install/intel/23.1.0/gftl-shared-1.6.1-ingeu4y/GFTL_SHARED-1.6/lib/libgftl-shared-v2.a /work2/01118/tg803972/frontera/spack-stack/spa
             ck-stack-dev/envs/unified-env/install/intel/23.1.0/gftl-shared-1.6.1-ingeu4y/GFTL_SHARED-1.6/lib/libgftl-shared-v1.a /opt/intel/oneapi/compiler/2023.
             1.0/linux/compiler/lib/intel64_lin/libiomp5.so
     1831    ifort: command line warning #10121: overriding '-march=cascadelake' with '-march=core-avx2'
     1832    make[2]: Leaving directory `/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2
             kkusw6we4juk/spack-build-lab6laq'
     1833    [ 75%] Built target MAPL.griddedio
     1834    make[1]: Leaving directory `/work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2
             kkusw6we4juk/spack-build-lab6laq'
  >> 1835    make: *** [all] Error 2

See build log for details:
  /work2/01118/tg803972/frontera/spack-stack/spack-stack-dev/cache/build_stage/spack-stage-mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk/spack-build-out.txt

==> Warning: Skipping build of ufs-weather-model-env-1.0.0-wvdatstosmrm45pfle6ld4u5jzetp32d since mapl-2.40.3-lab6laqhzuug4larjpy2kkusw6we4juk failed

System:
TACC Frontera using Intel Compiler (intel/23.1.0 using gcc/9.1.0 backend) and MPI (impi/21.9.0). The same configuration is working with spack-stack 1.6.0.
Additional context
None

@climbfuji @matomp4 FYI.

Interesting. @climbfuji Is this seen on any other machine?
I'll also CC in @tclune for thoughts but the code it's dying in hasn't changed in 3 years, so maybe it's something it uses?
Also: I'm not sure we ever tried MAPL with ifort 2021.9. We never had access to it locally due to old OS, and by the time we had SLES15, 2021.10 was around.
I can say 2021.10 and 2021.11 work with current MAPL (and I suspect 2021.12, but haven't tested) but again, this is new compiler and old MAPL so...

Ah - I remember seeing this error when we porting to 2021.10 (or thereabouts).    Unfortunately, I don't immediately remember what the workaround was, but there must have been one.    And, as @mathomp4 indicates, the workaround must be in code that this uses (directly or indirectly) since this bit did not change.
I'll stare at the code a bit and see if memory returns.

@uturuncoglu Do you want to try @tclune 's suggestion?

@uturuncoglu Do you want to try @tclune 's suggestion?

My apologies @uturuncoglu  - did not look back in the thread far enough to see who asked the original question.

@climbfuji @mathomp4 @tclune rhanks for your help. I could try with recent version of MAPL. Do you want me to test any specific version? BTW, I think that the default versions of the libraries are defined in the template section. Right?

@climbfuji @mathomp4 @tclune rhanks for your help. I could try with recent version of MAPL. Do you want me to test any specific version? BTW, I think that the default versions of the libraries are defined in the template section. Right?

Please check envs/name-of-env/spack.yaml and if not hardcoded there, change envs/name-of-env/configs/packages.yaml.

@climbfuji @tclune @mathomp4 I tested MAPL 2.43.0 (it was the most recent version in the package.py - https://github.com/JCSDA/spack/blob/66e9ce432da4a88fe075b9f9a8c3d4fb5e42da73/var/spack/repos/builtin/packages/mapl/package.py#L41C14-L41C20) and it compiled and installed without any issue. I think there is no need to do anything specific in https://github.com/JCSDA/spack-stack/pull/1075 but maybe the default version of the MAPL needs to be upgraded in the next tag to allow work on TACC Frontera. Let me know if you want me to do more test with other versions. Thanks again to all for your help.

@climbfuji Yes, I think we could close it. Thanks.

Thanks @uturuncoglu !


pycodestyle nicery

Please consider adding pycodestyle to the CI

Hmm, thanks, actually, it is already an important thing for me. But it is not included yet in the CI.
Note that I admit having a personal habit that I want to keep of using double ## for english comments, and single # for code that would be commented out. Which is not so out of current PEP8 and has quite a little impact on overall readability (my feeling actually is quite the opposite, I feel the comments are more easy to spot actually, but well). I hope it doesn't hurt too much your eyes as I intend to keep them like that.
I'm thankful for the empty missing empty lines, and the module description in the beginning. And you suggestion is quite right. Let me keep this open to remind me about integrating python codestyle (with my minor alterations) to the CI checks (at least on my end).

The solution is coming...

Yeah, I know about dead code, and no it isn't. I remove dead code and rely on git history to keep it.
The code that remains in comment is rare, but have a definite role in the comment, with the same role as comments: trying to clarify what and why things are written as they are. And sometimes, especially when talking about code, you might want to actually show some code (that could be expected but doesn't work for some commented reason, or should be written once we stop trying to be compatible with old version of python... etc ...).
I'm not trying to convince you to use it, but to leave me continuing to use it. I acknowledge it is my own twist of the rules I happen to fancy, my own space of liberty. I think I'm using all of PEP8 otherwise.
Fun fact, be happy I don't go in using more that 2 dashes:

https://stackoverflow.com/questions/6365334/lisp-commenting-convention
https://mail.python.org/pipermail/python-list/2002-October/120157.html

Or the reverse convention:

http://computer-programming-forum.com/56-python/c5e45f0d4f0dcb53.htm

Also, I got the idea from some bash code in /etc/default/* and elsewhere (you can still find them here in some of the files), a very long time ago. I stuck to it. My bad. I won't change all my projects. I believe it isn't that important. And don't expect me to comment much more on that topic.


dynamodb update item with nested item issue

Hi,
When I update_item with Update expression as
SET #name1.#name2 = :value'
where name1 is a map
When I scan and read the item, I get the result as
'Name1.Name2':
the item is saved as #name1.#name2 instead of a map structure. Is it a known issue

Not a known issue as far as im aware, can you create a simple test case for this and i'll look into it

I have the same issue. It seems UpdateExpression doesn't work with Nested Map Attributes properly. I'm using mock_dynamodb2.
If I run something like this
table.update_item(
            Key={
                'ID': id,
            },
            UpdateExpression='SET ResultMap.#final.#key = :status',
            ExpressionAttributeNames={
                '#final': 'Final',
                '#key': 'Key'
            },
            ExpressionAttributeValues={
                ':status': 'status'
            }
        )

and then read the data with scan, a result item contains a new attribute with the key 'ResultResources.Final.Key' instead of updating a nested attribute. It works properly if I run my function on AWS.

Should fix it. No garuentees but it fixes @VitalyIvanov's example

@terrycain Great! Thank you! My use case now works just fine.

No problem mate. Glad its working, that bit of the code is proper evil :D


Fix badges

Codecov Report

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

@@            Coverage Diff            @@
##             master      #27   +/-   ##
=========================================
  Coverage     50.41%   50.41%
  Complexity      236      236
=========================================
  Files            51       51
  Lines          1200     1200
  Branches        134      134
=========================================
  Hits            605      605
  Misses          538      538
  Partials         57       57

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 5f0e482...4c960d0. Read the comment docs.


#310: Create stub files for all exercises

Stub implementations for a-tasks:

accumulate
acronym
all-your-base
allergies
anagram
atbash

:+1: from me.
Just tiny nit-picking: It might be nice to use commit message like "For #<issue_number>: ". E.g.: "For #338: Add missing stubs for some exercises". It's bit more informative when one is checking commits list.

@dector will adapt my habbits
can you please merge?


fix and testcase wrong compare version "0.0.1" less than "1.0"

@mrackwitz I found that we compare wrong in case "1.0.0" and "0.0.1"

Hi @thinhvoxuan,
This has been fixed in 751b1580fce0198c1ec8db0a8b1d7ce4ec66d421.

Your "fix" of doing …
let lhsValue = lhs.major * 10000 + lhs.canonicalMinor * 100 + lhs.canonicalPatch
let rhsValue = rhs.major * 10000 + rhs.canonicalMinor * 100 + rhs.canonicalPatch

… will inevitably fail for version numbers with unexpectedly large (i.e. > 100) minor or patch components.


System range replication

Update tutorials, training, and production checklist to emphasize the importance of manually increasing the replication factor for system ranges when:

Running a cluster of 5 or more nodes.
Increasing the default replication factor for user data.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8185631ffa82845ba3da404f49352d193e1606a9/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b591dd8d2fba9416234e8b32c69fd153993df64c/

@tschottdorf, should I also add a new section to the Known Limitations page?
I definitely want to write to a deeper page on fault tolerance. We need to help people understand table data ranges vs. system ranges and data unavailability vs. system unavailability. Just scratched the surface in these trainings.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f7f108d2956d976cf9e7a37cc16ece5051a6c6a9/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a7283ab4a8b3cbc68c90d6caeb8048201c186d85/


[DO NOT MERGE, TESTING ONLY] Release Qualification

Trigger release qualification jobs
none

Hi @silverdev. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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


Broker load from http parquet file.   type:LOAD_RUN_FAIL; msg:Init parquet reader fail. Invalid: Parquet file size is -1 bytes, smaller than the minimum file footer (8 bytes)

same setup as https://github.com/StarRocks/starrocks/issues/26058
load label abc(data infile("https://docs.snowflake.com/en/_downloads/0c1e6c4f4140561029eeb20afdd02664/cities.parquet") into table cities (continent, country)) with broker properties("timeout"="3600");

| 10122 | abc   | CANCELLED | ETL:N/A; LOAD:N/A | BROKER | NORMAL   | 0        | 0            | 0              | 0        | NULL    | resource:N/A; timeout(s):3600; max_filter_ratio:0.0 | type:LOAD_RUN_FAIL; msg:Init parquet reader fail. Invalid: Parquet file size is -1 bytes, smaller than the minimum file footer (8 bytes) | 2023-06-27 21:19:47 | 2023-06-27 21:19:51 | 2023-06-27 21:19:51 | 2023-06-27 21:19:51 | 2023-06-27 21:19:53 |             | {"All backends":{"bcd2f509-0198-4127-8911-f1ba74cd7c85":[10006]},"FileNumber":1,"FileSize":-1,"InternalTableLoadBytes":0,"InternalTableLoadRows":0,"ScanBytes":0,"ScanRows":0,"TaskNumber":1,"Unfinished backends":{"bcd2f509-0198-4127-8911-f1ba74cd7c85":[]}} |

related to https://github.com/StarRocks/starrocks/issues/26060


Import issues

I am trying to import torch into my python program and no matter what I do it says that 'Import "torch" could not be resolved'. I've installed the PyTorch Snippets extension, as well as restarted my VS Code. Am I just doing something wrong or am I using the wrong import? Any help would be appreciated, thank you.

hey! , can you solved this problem?,  i have the same issue.


add ci run for main branch

this should create a new release that does not squash existing ones, and has a versioned tag.

fixed by changing how i am managing the branches


fix: Improve character count component's SR experience

Summary
Character count includes a brief pause on input before announcing the status.
Related Issues or PRs
Closes #2509

Related PR in USWDS repo: https://github.com/uswds/uswds/pull/4976
How To Test

Go to http://localhost:9009/?path=/story/components-charactercount--text-input
Open screen reader
Start typing. The SR should announce number of characters left.
Type over limit. The message should be bold and in red. (New invalid styling.)

The SR message for the number of characters left works in:

[x] NVDA
[x] JAWS
[x] Narrator
[ ] VoiceOver

Screenshots (optional)

On mac/firefox, I did not get any announcement of characters left, just the total limit:

On mac/firefox, I did not get any announcement of characters left, just the total limit:

Yeah, still investigating why Voiceover is not reading the updates out here. I can see it working here in the USWDS preview: https://federalist-3b6ba08e-0df4-44c9-ac73-6fc193b0e19c.sites.pages.cloud.gov/preview/uswds/uswds/jm-a11y-character-count/iframe.html?args=&id=components-form-inputs-character-count--character-count&viewMode=story

@werdnanoslen I pushed an update that should now work with VoiceOver. Let me know if you can test it.

huzzah

@werdnanoslen Ah sorry I need another happo approval!


Obtain the SGBs list

Hello,
To be sure that we perfectly understand the Toposcore, we were wondering whether it would be possible to obtain a list of the species-level genome bins used for data analysis?
Thank you in advance.

Hello @TheLokj,
Thank you for your interest in Toposcore usage.
You'll find the data used for the analysis at this link: https://github.com/valerioiebba/TOPOSCORE/blob/main/DS2_oncology_microbiome_data_DiscValid.csv
In this CSV file you'll find the NSCLC patients (n=499) encompassing all the bacterial species (known or at GGB and SGB level).
Best
Valerio

Thanks @valerioiebba for this quick answer.
We are requesting the SGBs lists used to calculate the Toposcore as we are having trouble reproducing the analysis. In fact, despite the use of the modified final_script_paper.ipynb  script induced by the @HuaZou issue, some minor discrepancies remain between the study, between the DS1 and between the R outputs :
For instance, if we take the sample LUM_101, we have :

in the recently updated DS1_oncology_clinical_data_DiscValid.csv : n_SIGB1 = 15 ; n_SIGB2 = 12 ; SCORE = 0.4306306.
in the pred_disc obtained after following the modification of final_script_paper.ipynb : SIGB1 = 10 ; SIGB2 = 6 ; TOPOB01 = 0.4507422.
in the pred_disc_short obtained after following the modification of final_script_paper.ipynb  : SIGB1= 3 ; SIGB2 = 7 ; TOPOB01 = 0.4333333.

These differences are probably induced by the fact that the number of species selected between steps 1 and 1.4 differs between the study and the R output as @HuaZou pointed it out. The initial discrepancies trigger in turn new ones like induce different cut-off thresholds : the final_script_paper.ipynb  leads to 0.5849 and 0.7390 where the script comments and study refers to 0.5351351 and 0.7911411.
Thank you for your time.


Add package.json script for "web" to launch "expo web"

Add package.json script for "npm run web" to launch "expo web"
Motivation
Just for convenience and to show that you can run expo web locally.

@sven09 I guess this is clear enough that this is a command to execute to launch web, isn't it?
Could you please open a PR if so?


Adding collapsible Tabs

Closes https://github.com/adobe/react-spectrum/issues/1117
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

Please address comments from Devon in a follow PR


Support for Swift 3.1

Hey guys, wondering what your timeline is for Swift 3.1

Thanks @Mackarous for submitting the issue that everyone wants to know. Did you already find problems of Swinject with Swift 3.1? I'll try downloading Xcode 8.3 and build Swinject with Swift 3.1 in this week.
I think it's good to release a version fixing #241 in Swift 3.0.x before migrating to Swift 3.1. I have no exact timeline, but I'll support Swift 3.1 soon.

After recompiling Swinject 2.0 with Cartage for Swift 3.1 (still necessary because Swift is not ABI stable yet) it works just fine for me :)

Thanks @basalphenaar👍 I also confirmed building Swinject 2.0 with Swift 3.1 worked for me.
(Only an exception was a log message, which got slightly different to describe type names. However, it doesn't affect users of Swinject.)

Project itself was updated to Xcode 8.3 with Swift 3.1 by #252.


scaffolding change in the name of navigation property since dotnet 8.0 ?

I'm working on a asp.net core backend that was on .net 6 and we're trying to migrate it to .net 8.
We have noticed a change for which we haven't yet found documentation. Given a simple Test database with the following 3 tables:
CREATE TABLE [dbo].[ItemCategory] (
    [Name]                 VARCHAR (25)     NOT NULL,
    [Description]          NVARCHAR (512)   NULL,
    CONSTRAINT [PK_ItemCategory] PRIMARY KEY CLUSTERED ([Name] ASC),
);

CREATE TABLE [dbo].[Item] (
    [Name]                   VARCHAR (40)     NOT NULL,
    [Description]            NVARCHAR (512)   NULL,
    [CategoryName]           VARCHAR (25)     NOT NULL,
    CONSTRAINT [PK_Item] PRIMARY KEY CLUSTERED ([Name] ASC, [CategoryName] ASC),
    CONSTRAINT [FK_Item_ItemCategory] FOREIGN KEY ([CategoryName]) REFERENCES [dbo].[ItemCategory] ([Name]),
);

CREATE TABLE [dbo].[SomeTable] (
    [Id]                   INT              IDENTITY (1, 1) NOT FOR REPLICATION NOT NULL,
    [DetailItemName]         VARCHAR (40) NOT NULL,
    [DetailItemCategoryName] VARCHAR (25) NOT NULL,
    CONSTRAINT [PK_SomeTable] PRIMARY KEY CLUSTERED ([Id] ASC),
    CONSTRAINT [FK_SomeTable_DetailItem] FOREIGN KEY ([DetailItemName], [DetailItemCategoryName]) REFERENCES [dbo].[Item] ([Name], [CategoryName])
);

I can use the following command to generate the c# classes:
dotnet ef dbcontext scaffold "Data Source=localhost\sqlexpress;Initial Catalog=Test;Integrated Security=True;MultipleActiveResultSets=True;TrustServerCertificate=True" Microsoft.EntityFrameworkCore.SqlServer -f

if I use net6.0, namely with exactly this csproj:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="6.0.25">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="6.0.25" />
  </ItemGroup>

  <ItemGroup>
    <Folder Include="Models\" />
  </ItemGroup>

</Project>

I get the following output for the SomeTable C# class:
using System;
using System.Collections.Generic;

namespace ClassLibrary1
{
    public partial class SomeTable
    {
        public int Id { get; set; }
        public string DetailItemName { get; set; } = null!;
        public string DetailItemCategoryName { get; set; } = null!;

        public virtual Item DetailItem { get; set; } = null!;
    }
}

However, if I switch to net8.0, using exactly this csproj:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="8.0.0">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="8.0.0" />
  </ItemGroup>

  <ItemGroup>
    <Folder Include="Models\" />
  </ItemGroup>

</Project>

I get the following output:
using System;
using System.Collections.Generic;

namespace ClassLibrary1;

public partial class SomeTable
{
    public int Id { get; set; }

    public string DetailItemName { get; set; } = null!;

    public string DetailItemCategoryName { get; set; } = null!;

    public virtual Item Item { get; set; } = null!;
}

Notice that with net6.0 and net7.0 we get this:
        public virtual Item DetailItem { get; set; } = null!;

but with net8.0 we get this:
    public virtual Item Item { get; set; } = null!;

When I run the scaffold command in both cases I get the same output in both cases:

We have a lot of existing code and tables and we'd like to be able to use the "old naming scheme" if possible. Is there a way to do that ?
Thanks!

@ajcvickers thanks for the replies. Is there a ready to use T4 template that emulates the old behaviour ? this would be quite useful to have as this is essentially a breaking change, and we would then be able to get around it in an effortless fashion.

@shikamu There is no specific template for this. Start from the default templates and edit the code that writes the navigation names.


Incorrect comparison guide info for "watch mode"

The comparison guide says that Rollup doesn't have a watch mode. It does (https://github.com/rollup/rollup-watch).
To mimic the style of the rest of the table (a link to the plugin if it's not built in), I assume that the entries for Browserify and Rollup should read as watchify and rollup-watch respectively.

seems that it is WIP.

I guess that's a question for @Rich-Harris, my impression is that it's relatively stable/widely used?

Yeah, it is — we should probably update the README on rollup-watch to reflect that. thanks for the prod


chore: typo

PR-Codex overview
The focus of this PR is to update the README file by replacing the backticks with double quotes for better readability.
Detailed summary

Updated the formatting of "sample repositories" from backticks to double quotes.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 9min)


Having to include prefix with login

When trying to login I have to add our domain in front to make it work
protected function bindUsingCredentials($username, $password, $suffix = null)
....
$username = 'blah\'.$username;
...
Any ideas how to fix this so its not required?

Can't you include it yourself manually?
$prefix = 'ACME\\';

if (Adldap::authenticate($prefix.$username, $password)) {
    //
}

Was trying to use the regular auth method , I believe that would work
though
On Monday, March 28, 2016, Steve Bauman<EMAIL_ADDRESS>wrote:

Can't you include it yourself manually?
$prefix = 'ACME\';if (Adldap::authenticate($prefix.$username, $password)) {    //}
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Adldap2/Adldap2-Laravel/issues/77#issuecomment-202604213

You can still perform the same thing using the included auth driver. Unfortunately this is something the developer will have to include since you can use different attributes for logging in through the configuration, and a prefix won't always be needed.

Actually you cant, because the method that goes into the auth looks up the user based on that info. My user doesn't have the prefix but is needed for the actual login part.

Yup you're right, apologies.
Are you not able to utilize the account suffix? If you specify a suffix for your domain then you won't need to use a prefix:
// config/adldap.php
`account_suffix` =><EMAIL_ADDRESS>

The problem then becomes finding users with @corp.acme.org. but not all our users have that same suffix and some none at all (this is most likely an issue with our own server)

The problem then becomes finding users with @corp.acme.org. but not all our users have that same suffix and some none at all (this is most likely an issue with our own server)

Ok, I'll implement a prefix option for authentication. Thanks for creating an issue about this!

Thanks , really appreciate that.

Added in v6:
https://github.com/Adldap2/Adldap2/commit/163c7baee696b2594d6eca2b1dfe721328365b16


Various enhancements

use a seed-able random generator
put the seed as param in the URL, for reproducibility
add a 'repulsing pulse' under mouse when it's clicked
record the FPS
display some parameters on-screen when using the 'f' key as toggle
add various key commands:

'[' and ']' controls the time-scale
'o' will randomize the particles' position
'p' will add some particles
'r' to use random new rules
'm' to print the rules matrix
's' to symmetrize the rules
'1' and '2' to control the cut-off for interaction (??)

Hi!
here are some enhancements i found useful on my local version.
Not sure if you can use them (even partly), but here they are!
That was a fun to toy around with the initial code, thanks for that!
skal/

Thanks! the default rule you put is very interesting! I didn't expect JavaScript to get this far. It may top-up the C++ version at some point.


Play button in subtitle option in windows

Is possible have play button for edit subtitle
And have sync when select subtitle
All this in windows?

Is possible have play button for edit subtitle And have sync when select subtitle All this in windows?

Is this possible for do it?

Should be available in 0.8.4


[discussion]: Split out check functionality to its own package?

What would you like to discuss?
I was struggling to fall asleep last night and one of the many thoughts swirling around was about moving the check functions into another Python package.
The main reasons to do that are that:

Other packages of ours (like flower or propagate) might need some check functionality and it would be nice not to have to depend on the full sprout.
Other developers might have had similar struggles as us with frictionless, so this might be a good alternative for them.
We can use this package as an example to the frictionless group on how to revise their design/incorporate our work into theirs/we could merge in the package with theirs.

Thankfully, this package would be fairly small and very focused, so building it and then publishing to PyPI could be done much sooner than for sprout. It would be nice to be able to show an more tangible output of our work so far, sooner than later.
Some ideas for the name could be: datapackage-lint or datapackage-check.

I think it could work and I can see the reasons justifying it, 1 and 2 very concretely and 3 in a vaguer way.
I feel like once we decide what exactly will be included in the checks and what the API will be, it will be easier for me to imagine how exactly this package would look like.
Based on some initial impressions, I think we could get away with very few dependencies/assumptions if metadata was input to the functions as a dict or JSON (as opposed to a *Properties class). And then we would just need to decide how we want to input the actual data (data frame, from file, etc.) to the functions.

Yea, judging from many of the issues open at frictionless, I can see this being something people might use a lot.

We decided that we will implement within sprout first and if need be, it would be fairly easy to split out into own package.


libc++abi: terminating due to uncaught exception of type std::runtime_error: [Matmul::eval_cpu] Currently only supports float32

Describe the bug
I got libc++abi: terminating due to uncaught exception of type std::runtime_error: [Matmul::eval_cpu] Currently only supports float32 when trying to run mlx-lm on any model
To Reproduce
Include code snippet
from mlx_lm import load, generate

model, tokenizer = load("mlx-community/Qwen1.5-0.5B-Chat-4bit")
prompt = "hello"

messages = [
{"role": "system", "content": "You are a helpful assistant."},
{"role": "user", "content": prompt}
]

text = tokenizer.apply_chat_template(
messages, tokenize=False, add_generation_prompt=True)

response = generate(model, tokenizer, prompt=text, verbose=True, max_tokens=200)

Output
==========
Prompt: <|im_start|>system
You are a helpful assistant.<|im_end|>
<|im_start|>user
hello<|im_end|>
<|im_start|>assistant

libc++abi: terminating due to uncaught exception of type std::runtime_error: [Matmul::eval_cpu] Currently only supports float32.
zsh: abort      python

Expected behavior
model should generate as normal
Desktop (please complete the following information):

OS Version: [e.g. MacOS 14.3.]
Apple M1 Pro 16GB RAM

Looks like it's running on the cpu 🤔 . I have no idea why that is the case..
How did you install MLX? Could you share the output of:
python -c "import mlx.core as mx; print(mx.metal.is_available())"

Looks like it's running on the cpu 🤔 . I have no idea why that is the case..
How did you install MLX? Could you share the output of:
python -c "import mlx.core as mx; print(mx.metal.is_available())"

It's False. Seems metal is not working.
I install it with pip install --upgrade mlx , mx.version== 0.4.0

@awni
Actually, pip install didn't work,
pip install mlx
ERROR: Could not find a version that satisfies the requirement mlx (from versions: none)
ERROR: No matching distribution found for mlx

So I changed to conda install -c conda-forge mlx, then I got that error.

Oh shoot, so the conda install does not have the Metal back-end built... that is not good.

Also why did the pip install not work for you, that is very strange.. and suggests something is off with your environment.
Can you check the install docs. Probably you are using a non-native Python.

Interesting, so if I install with conda it works fine. So conda must have a distribution which does not require metal.. that's a bit of a trap unfortunately.

Also why did the pip install not work for you, that is very strange.. and suggests something is off with your environment.
Can you check the install docs. Probably you are using a non-native Python.

You're right. python -c "import platform; print(platform.processor())" give i386. I will try installing the native python and update with you. Thanks!


docs: improve CodeDocsSearchTool README

Fix tool name in custom model example

Disclaimer: This review was made by a crew of AI Agents.
Code Review Analysis of PR #133
Overview
This pull request addresses an important error in the documentation of the CodeDocsSearchTool within the README.md file by correcting the tool name in an example configuration from YoutubeVideoSearchTool to CodeDocsSearchTool.
Content and Purpose
The README.md file serves a crucial role in guiding users on how to utilize the CodeDocsSearchTool, as it facilitates semantic searches of code documentation. The accuracy of this documentation directly impacts user experience and implementation effectiveness.
Changes Made

Correction of Tool Name: The specific fix involves the line:

From:tool = YoutubeVideoSearchTool(

To:tool = CodeDocsSearchTool(

This correction is essential for ensuring that users do not encounter confusion or make errors when attempting to implement the tool based on the provided examples.
Interaction with Modified Code
The adjustments made in the README directly influence how users interact with and implement the CodeDocsSearchTool. Accurate documentation fosters a smoother onboarding process for users and mitigates potential issues stemming from misleading or incorrect examples.
Suggestions for Further Improvements
While this PR provides a necessary fix, I recommend considering the following enhancements for improved documentation clarity and usability, which can be addressed in future updates:

Add Type Hints to the Example:
tool = CodeDocsSearchTool(
    config: dict = dict(
        llm: dict = dict(
            provider: str = "ollama",  # or google, openai, anthropic, llama2, ...
        )
    )
)

Provide a Complete Example with Realistic Values:
tool = CodeDocsSearchTool(
    config=dict(
        llm=dict(
            provider="ollama",
            model="llama2",
            api_base="http://localhost:11434"
        ),
        embeddings=dict(
            provider="openai",
            model="text-embedding-ada-002"
        )
    )
)

Include Comments Explaining the Configuration Options:
# Available configuration options:
# llm:
#   - provider: The LLM provider (ollama, google, openai, anthropic, llama2)
#   - model: The specific model to use
#   - api_base: API endpoint (for self-hosted models)
# embeddings:
#   - provider: The embeddings provider
#   - model: The embedding model to use

Historical Context and Lessons Learned
While I am unable to fetch historical context due to access limitations, it is essential to ensure that documentation remains accurate and up-to-date alongside code changes. This practice not only improves the user experience but also helps in maintaining project integrity.
From this PR and previous reviews, there is a strong emphasis on:

The critical need for accurate documentation to prevent user errors.
Encouraging continuous improvements in clarity and utility of documentation.

Conclusion
This pull request is valid and plays a vital role in enhancing the clarity and accuracy of the documentation for the CodeDocsSearchTool. I recommend approving this PR with the highlighted suggestions for potential future improvements to enhance documentation comprehensiveness and user understanding.
✅ Approve with suggestions for future improvements to enhance the documentation’s clarity and completeness.


Deprecating long-lived credentials for container repositories for operations-engineering-certificates

Background

To improve the security of services running on the Cloud Platform, we are removing the ability to create and use long-lived credentials, such as IAM access keys, from our modules. These are being replaced by short-lived credentials.
For container repositories, this means utilising native OpenID Connect implementations for GitHub Actions and CircleCI.
You should start using short-lived credentials as soon as you can. Long-lived credentials will be entirely removed from the container repository on Monday, 4th September 2023.

Instructions
https://user-guide.cloud-platform.service.justice.gov.uk/documentation/deploying-an-app/container-repositories/deprecating-long-lived-credentials.html#deprecating-long-lived-credentials-for-container-repositories
Acceptance Criteria:
No longer using long lived creds for container repositories
Assumption
Some refactoring of apps may be required in support of this change.
Notes:
Cloud Platform Comms
Guidance/Instructions

https://user-guide.cloud-platform.service.justice.gov.uk/documentation/deploying-an-app/container-repositories/deprecating-long-lived-credentials.html#migrating-to-short-lived-credentials-for-github-actions
Update the GH Action workflow files to use new short term credentials:
certificate-expiry-check-test-run.yml
certificate-expiry-check.yml

The operations-engineering-certificate CP Namespace is not being used. Should it be deleted from CP environments folder and this ticket closed?

Namespace removed from Cloud Platform environments as it's no longer needed.


Add more applications

You might wanna hold merging this one until this issue here gets fixed

Thanks, looks good!

Btw I'm sorry you are now getting random issues opened here from other people, unintended consequence of the project being used in am I guess lol.
Also Ivan went and forked this to how it was before the recent issue and opened an issue at am without even waiting 24h... sorry about that.


Does NOA support child meshes?

Hello!
Thanks for this great package, I am experiencing an issue where child meshes are not positioned correctly after "checkWorldOffset" completes.
I simply add a text mesh above a simple mash - which works fine, but after player entity gets close enough the child mesh (text above ball) is re-positioned incorrectly.
Thanks! :)

Thanks, that worked! I was trying to add the mesh as an entity
using noa.entities.add instead of using addMeshToScene.
another question - is there a way to add a skybox? /change the sky color?
Appreciate the quick response!
Thanks again for this great package !
On Tue, May 2, 2023 at 6:22 PM Andy Hall @.***> wrote:

Hmm, that should work correctly - the engine repositions meshes when the
player moves a certain distance (25 blocks by default) but it should handle
parented meshes correctly.
It seems to work okay for me with code like this:
var box = CreateBox('', {}, noa.rendering.getScene())box.position.set(1, 1, 1)box.parent = playerMeshnoa.rendering.addMeshToScene(box)
Can you post code that shows the issue?
—
Reply to this email directly, view it on GitHub
https://github.com/fenomas/noa/issues/192#issuecomment-1531669324, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWXQ6QEH3LHGLIJDDDEIF3TXEERDZANCNFSM6AAAAAAXS7XAIA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ah good! entities.add is for when you want to add an "entity" - a thing that can have its own position, mesh, physics and so on.
For the sky color, you can pass the option clearColor: [1,1,1] when creating the engine - this is the color that is drawn to the canvas before meshes are rendered, so it's effectively the sky color.
For a skybox, basically that should work like in any Babylon project; the only noa-specific thing is that you need to call noa.rendering.addMeshToScene so that the mesh will get selected for rendering.


screen ver 1.2

Je viens de regarder ton nouvel code 1.2,
quand on appuis avec le bouton "gaming" l'affichage de l'ecran, est ok
par contre
en tournant la manivelle en arriere, et doucement avec l'ancienne version moteur, l'ecran affiche "la note joué" puis l'ecran fixe ou il y a  les "données de selection"
en tournant dans le bon sens l'ecran des notes jouées s'affiche normalement , mais le moindre rythme un peu plus lent, repasse sur l"ecran de "données selection",  et parfois quand la vitesse est lente, les deux (note et selection  s'affiche en meme temps, je pense que cet ecran de selecrion devrait etre temporisé de quelques seconde, pour eviter  ce cumul, et d'avoir ce desagrement.
j'espere avoir eté clair???

Using Google Translate :-)

By turning the crank back, and gently with the old engine version, the screen displays "the note played" then the fixed screen where there are the "selection data"

By turning in the right direction the screen of the notes played is displayed normally, but the slightest pace a little slower, goes back to the "selection data" screen, and sometimes when the speed is slow, both (note and selection are displayed at the same time

I am not sure if I understand you correctly.  Do you mean that the crank is jittery and only plays very briefly?  It doesn’t stay on consistently at slow cranking speed?  I think that’s what you mean by the note and selection screen coming on “at the same time”.
The motor doesn’t behave equally in both directions, so I would expect it’s more noticeable in one direction than the other.  Am I understanding your question correctly?
You’re using a diode bridge that John mentioned, correct?

for the moment i have no diode  bridge, i  use the old motor version.  in first i try the crank in return way very slowly, the display coming and have two screen "note" and after "selection".
and when i crank slowly the display see the "note", and when we have little stop of crank the "selection" come immediatly, i thinks it's necessary to delay a litlle the "selection"   and  "note"  stay a litle more delay or blank the display.
it's difficult for me to explain rigtly....

When this happens, do you also hear the note playing come on and off quickly?  It sounds like it’s not a problem with the display, but a problem with the settings betting too sensitive for your crank.
If you hear the sound stuttering as well as the screen, then it’s the crank sensitivity.  You can try:

Raising the V_THRESHOLD value to a higher one.  I use 8, which is rather low.  15-25 was the original range John’s code used.  This will make the crank less sensitive at low speeds.  Ideally you want to set this so that the crank doesn’t kick in until you’re spinning it at the lowest speed you’d want to play it, so that instead of “stuttering” out at lower crank speed it simply cuts off.

Increase the MAX_SPIN and SPIN_WEIGHT a bit.  This will make the note stay on longer when the crank voltage momentarily drops, so it will play through the “stuttering” events.  The downside is this also adds a delay to how quickly the sound will stop when you stop cranking, so you only want these values to be high enough to be smooth for your playing, and not any higher than that.

You may also need to raise the BUZZ_SMOOTHING number if that is also too sensitive.

I'm going to close this, because when I re-implement the motor crank (which is my next goal after bringing the Blue OLED back into play, like v2.3), I'll be redesigning it from the ground up.  Same idea, but with a smarter use of timers and hopefully your issue won't come into play there.


Error creating a billing role assignment

When attempting to create a billing role assignment I get the following error.
{
    "errors": {
        "properties.PrincipalId": [
            "PrincipalId or UserEmailAddress/UserAuthenticationType must be specified."
        ],
        "properties.RoleDefinitionId": [
            "The RoleDefinitionId field is required."
        ],
        "properties.UserEmailAddress": [
            "PrincipalId or UserEmailAddress/UserAuthenticationType must be specified."
        ],
        "properties.UserAuthenticationType": [
            "PrincipalId or UserEmailAddress/UserAuthenticationType must be specified."
        ]
    },
    "type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
    "title": "One or more validation errors occurred.",
    "status": 400,
    "traceId": "|4282ee38-43a4536608001b1d."
}

The request I'm using is:
curl --location --request POST 'https://management.azure.com/providers/Microsoft.Billing/billingAccounts/xxx/createBillingRoleAssignment?api-version=2019-10-01-preview' \
--header 'Authorization: Bearer xxx' \
--header 'Content-Type: application/json' \
--data-raw '{
    "principalId": "xxx",
    "billingRoleDefinitionId": "/providers/Microsoft.Billing/billingAccounts/xxx/providers/Microsoft.Billing/billingRoleDefinition/10000000-aaaa-bbbb-cccc-100000000000"
}'

I've tried to tweak the body a number of different ways but with the same error.
I'm able to successfully query the current billing role assignments but am not able to create a new one.
Any thoughts on what I should be trying different?

For --data-raw, can you try passing in the following value?
--data-raw '{
  "properties": {
    "principalId": "xxx",
    "roleDefinitionId": "/providers/Microsoft.Billing/billingAccounts/xxx/providers/Microsoft.Billing/billingRoleDefinition/10000000-aaaa-bbbb-cccc-100000000000"
  }
}'

Note how the properties are wrapped inside a "properties" property, and instead of billingRoleDefinitionId we're using roleDefinitionId.

Thanks Wilco for taking a look.   I tried using the code you provided as shown below but I am getting an error that the resource Id is not valid.  (Though guessing this is cause I had the wrong ID in my example.
{
    "properties": {
        "principalId": "xxx",
        "roleDefinitionId": "/providers/Microsoft.Billing/billingAccounts/xxx/providers/Microsoft.Billing/billingRoleDefinition/10000000-aaaa-bbbb-cccc-100000000000"
    }
}

This is the output:
{
    "code": "BadRequest",
    "message": "InvalidRoleId: Input Role Ids (10000000-aaaa-bbbb-cccc-100000000000) are not valid for the given Commerce Object Type(Organization)."
}

I did some more digging and found the following role IDs.
50000000-aaaa-bbbb-cccc-100000000002 = "Reader"
50000000-aaaa-bbbb-cccc-100000000001 = "Contributor"
50000000-aaaa-bbbb-cccc-100000000000 = "Owner"
Here is my final message body
--data-raw '{
    "properties": {
        "principalId": "xxx",
        "RoleDefinitionId": "/providers/Microsoft.Billing/billingAccounts/xxx/providers/Microsoft.Billing/billingRoleDefinition/50000000-aaaa-bbbb-cccc-100000000002"
    }
}'

Going to submit a request to update the documentation to reflect the roleID and also add the ID's for the various roles since I couldn't find them anywhere else.
Again, Appreciate the help @wilcobmsft Got me pointed in the write direction!!


Map.ofEntries equivalent for fastutil maps

Adding something like Map#ofEntries to the fastutil maps would be neat in my humble opinion.
Right now you gotta do ugly stuff like Int2ObjectMaps.unmodifiable(new Int2ObjectOpenHashMap(Map.ofEntries(...)))
I could make a PR if you don't have time to.
(btw great library much love ❤)

Good point, a PR would be welcome! I have the same problem.

sweet! Should the methods be added in the Map interfaces or Maps (with an s) classes

Good point. I'd follow the JCF and put in in Map. But what concrete class do you intend to return, an Open2OpenHashMap in an unmodifiable wrapper?

Not sure honestly... I'm not the data structure champion. Maybe an array implementation? I heard that it's good when you just access and don't write in it. Did not do a benchmark tho. The implementation of Map#ofEntries is just an array that alternates between key and value. Won't work for most maps (unless it's the same primitive type for the key and value)

Well, if it's immutable and holds at most 10 entries I think an ArrayMap is perfectly fine. It could even be the case of creating an ImmutableArrayMap, but that would mean another 90 classes. Maybe as an internal class of Map, just copying the necessary code from ArrayMap?

What if it's more than 10 entries? HashMap?

Or I could just return an ArrayMap / OpenHashMap in an unmodifiable wrapper depending on the number of entries. That would be the easiest to write.

Oh you're right. Map.of has at most 10 elements, but Map.ofEntries has variable length.
Yes, you could to ArrayMap up to, say, 8 elements, and, an OpenHashMap otherwise.

I'm guessing tests would be wanted? I don't see any test classes for the Map interfaces. Do I create a new one? Do I do it like Primitive2PrimitiveMapTest and Primitive2ObjectMapTest?

Yes, MapTest sounds right. Like Int2IntMapTest and Object2ObjectMapTest should be enough.
Please double check that I didn't put in Maps stuff that in Java is in Map... Or we might have to rethink the position.

Hey having a little trouble compiling a jar... Running ant jar tries to compile the drv files and I don't think that's normal 😅

No, it shouldn't. Did you make -s sources first?

Did not include -s since it isn't specified in the readme but yes I did.

Oh yeah that's just "silent" to avoid the mess. Platform? OS?

Hey it's me again, turns out I just can't read errors. It seems some java files are not getting generated correctly? For example Byte2ByteLinkedOpenHashMap.java gets generated with just OpenHashMap.drv inside of it. It might be more WSL shenanigans but asking nonetheless in case it's a known issue.

That scripting part is for UN*X variants. That's a WSL issue, I'm sorry but I can't help you...

I can't seem to find anywhere in gensources.sh or the makefile how it detects and replaces the drv file that just contains the name of another drv file. Kinda hard to debug when I don't know how it's done

It might be a problem with different treatment of soft links, as the .drv files of non-plain hash maps are just soft links to the real ones.

Hey I made this little workaround and it works great it seems. Should I commit that as well or no?
(The $1 at the end of the file is replaced by $TARGET_DRV_FILE)

TARGET_DRV_FILE=$1

# A workaround for Windows and WSL. Linked files only contain the "target" file's name on windows.
# So we check the first line to see if it contains ".drv". If so replace the target drv file by that.
FIRST_LINE=$(head -n 1 $TARGET_DRV_FILE)
if [[ $FIRST_LINE == *".drv"* ]]; then
  TARGET_DRV_FILE="drv/$FIRST_LINE"
fi

The problem is checking that it works everywhere.


[Map] CTF-Creed-Dumpster

This is a Greed map and should be moved here.

URL: https://unrealarchive.org/unreal-tournament-3/maps/capture-the-flag/C/ctf-creed-dumpster_d7ae3921.html
Hash: d7ae39217ccab92d0e192cd3502a3b662f322dd3
Current name: CTF-Creed-Dumpster

Ideally, Unreal Archive should automatically put maps with Greed prefix into their own dedicated map section.

I got bamboozled by the prefix, it's **C**reed, not Greed. Case closed.


Explicitly document contents of the stable ABI

See also Rings from Steve's "Layers/Rings" sugestion:

repo: https://github.com/zooba/python-api-pep/blob/master/PEP.md
initial mail<EMAIL_ADDRESS>

This is done: https://docs.python.org/3.10/c-api/stable.html#contents-of-limited-api


Use block download when ranking peers

Use both who ever gave us a header first, and who ever provided us with
the block first when ranking peers in deadline mode. For larger blocks
forged far away it is likely that we learned of the header
from a node on another continent, but the node from which we first
downloaded the block is much closer. This change gives both nodes
credit.

bors r+


Refactor piped metrics exporter

What this PR does / why we need it:
Introducing k8s cloudprovider metrics and k8s livestatestore metrics package
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

Nice. Thank you.
/lgtm

nits: how about:

pkg/app/piped/livestatestore/kubernetes/kubernetesmetrics -> pkg/app/piped/livestatestore/kubernetes/metrics
pkg/app/piped/cloudprovider/kubernetes/kubernetesmetrics -> pkg/app/piped/cloudprovider/kubernetes/metrics

I feel a bit redundant

nits: how about:

pkg/app/piped/livestatestore/kubernetes/kubernetesmetrics -> pkg/app/piped/livestatestore/kubernetes/metrics
pkg/app/piped/cloudprovider/kubernetes/kubernetesmetrics -> pkg/app/piped/cloudprovider/kubernetes/metrics

I feel a bit redundant

I get your point, just felt the same before 😅 But since we have cachemetrics already, I think it's better to have a kind of convention: xxxmetrics package means metrics for xxx (parent package) will be implemented here. How do you think? 🤔

I prefer to keep that convention. The metrics package name will be target-package-name + metrics.
This is a special case when 2 target-package-name have the same name. (pkg/app/piped/cloudprovider/kubernetes, pkg/app/piped/livestatestore/kubernetes), but in most cases, this convention helps avoid the need for aliases while importing.
This convention is the same for our test, mock package, redistest, redismock...
and standard go packages are using the same convention for httptest, httputil inside http package.

makes sense. no objection to that 👍
/approve

/changelog


Selenium Hub

I'm trying to run the generated suite_test but I'm using Selenium Hub in a Docker container. I think I need to use NewWebDriver but I can't figure out why I have to pass a command? I already have it running.

Hi @ianwalter, thanks for opening an issue!
agouti.NewWebDriver allows you to start a WebDriver process (specified by command []string) on a free port that Agouti will manage for you. If you already have a WebDriver running, you can use agouti.NewPage to connect to that WebDriver directly.
Let me know if this answers your question,
-Stephen

Oh ok, but then how would I specify the Selenium Hub URL (i.e. http://<IP_ADDRESS>:4444/wd/hub)?

page, err := agouti.NewPage("http://<IP_ADDRESS>:4444/wd/hub")

I get:
cannot use "http://<IP_ADDRESS>:4444/wd/hub" (type string) as type agouti.Option in argument to agoutiDriver.NewPage

You want: https://godoc.org/github.com/sclevine/agouti#NewPage
Not: https://godoc.org/github.com/sclevine/agouti#WebDriver.NewPage

I'm now getting the following error:
<*errors.errorString | 0xc20800b3c0>: {
          s: "failed to connect to WebDriver: unexpected end of JSON input",
      }
      failed to connect to WebDriver: unexpected end of JSON input

Selenium log:
hub_1     | 01:52:38.254 INFO - Got a request to create a new session: Capabilities [{acceptSslCerts=true}]
hub_1     | 01:52:38.254 INFO - Available nodes: [host :http://<IP_ADDRESS>:5555]
hub_1     | 01:52:38.254 INFO - Trying to create a new session on node host :http://<IP_ADDRESS>:5555
hub_1     | 01:52:38.254 INFO - Trying to create a new session on test slot {seleniumProtocol=Selenium, platform=LINUX, browserName=*firefox, maxInstances=1}
firefox_1 | 18:52:38.267 INFO - Checking Resource aliases
firefox_1 | 18:52:38.270 WARN - POST /selenium-server/driver/session HTTP/1.1
firefox_1 | java.lang.NullPointerException: sessionId should not be null; has this session been started yet?
firefox_1 | 	at org.openqa.selenium.server.FrameGroupCommandQueueSet.getQueueSet(FrameGroupCommandQueueSet.java:220)
firefox_1 | 	at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleBrowserResponse(SeleniumDriverResourceHandler.java:187)
firefox_1 | 	at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(SeleniumDriverResourceHandler.java:153)
firefox_1 | 	at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1526)
firefox_1 | 	at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1479)
firefox_1 | 	at org.openqa.jetty.http.HttpServer.service(HttpServer.java:920)
firefox_1 | 	at org.openqa.jetty.http.HttpConnection.service(HttpConnection.java:820)
firefox_1 | 	at org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:986)
firefox_1 | 	at org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837)
firefox_1 | 	at org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.java:243)
firefox_1 | 	at org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:358)
firefox_1 | 	at org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:537)

Not sure if this is due to my set up but seems to work with Capybara.

Hi @ianwalter,
Could you create a gist with some code that replicates this issue? It seems like Selenium is failing to create a session when Agouti POSTs to /selenium-server/driver/session. Are you sure /selenium-server/driver is the correct webdriver hub URL?

Hey @sclevine sorry to be jumping in so late but I'm having the same issue.
I am running a selenium/standalone-chrome instance on <IP_ADDRESS> currently ( https://github.com/SeleniumHQ/docker-selenium )
In my code I have this basically:
page, err := agouti.NewPage("http://<IP_ADDRESS>:4444/wd/hub")
And I get the result:
failed to connect to WebDriver: failed to retrieve a session ID
I was able to verify that the selenium instance is up by using the example from github.com/tebeka/selenium and "http://<IP_ADDRESS>:4444/wd/hub", however the api for the package doesn't work nearly as well as agouti.
Here's the actual code I am running: https://github.com/stuartaroth/testy-mctestface/blob/master/testy-mctestface.go
If you pulled the repo and built it using ./build you would then run ./testy-mctestface example.json to get the same result I'm getting.
If the reason for this has already been answered elsewhere I'd appreciate a link but I didn't find anything yet.
Thanks for your time!!

Ran into this issue and this solved it https://github.com/sclevine/agouti/issues/69#issuecomment-195559479

Re-opened #69 until this is better documented.


Can't get TimePicker to work

Hi, I'm trying to create a time picker component, I have copy-pasted the second example from here and nothing happens when I click. I can confirm that I've correctly set up Tailwind Elements (following the instructions on the website) because I've successfully rendered a date picker that opens the modal on click.
I did notice that the time picker uses the data-mdb-toggle attribute, and I don't have MDB installed.
Thanks in advance for any help.

Hello, I want to add that the same issue is occurred on the stepper components. I already did copy-paste the HTML and using latest tw-elements (1.0.0-alpha12)

@emorevival can you confirm the issue still exists?

Closing due to inactivity.


How long does it take to segment a MIMIC-CXR dataset?

Hello,
thank you for the great work and the great repo.

It takes about 1 month to do MIMIC-CXR dataset segmentation on GPU, I don't know if this is normal？

Hi
Thank you for your interest in our work.
I consider this is not correct. The total time for segmentation is about 5h using Nvidia 3090 GPU, referer here.
I guess you may not use GPU to segment, which will cause time to increase significantly. Please double-check that.
Best regard,
Tiancheng


Document $like operator in query

Relates to prest/adapters#18 and #220.
Documents the newly introduced ´$like` filter operator.
I also had to dig around a bit on the source code to understand how I could use each one of the filters, so I ended up adding some examples to the table (and the generated SQL).

New issue: https://github.com/prest/prest/issues/226