pex.resolver.Untranslateable exception in pex>=1.4.0

I'm building PEX for my project with the following sh script:
#!/bin/bash

PEX_VERBOSE=5 \
    pex \
    -r requirements-pex.txt \
    -o "mycmd.pex" \
    -c mycmd \
    -i "http://my.devpi.index/mycmd/dev" \
    --python="python2.7" \
    --python-shebang="/usr/bin/env python" \
    --platform="macosx-10.10-x86_64" \
    --platform="linux-x86_64" \
    -v

Contents of requirements-pex.txt:
backports.ssl-match-hostname==<IP_ADDRESS>  # via docker
blindspin==2.0.1
botocore==1.8.19
certifi==2<IP_ADDRESS>      # via requests
chardet==3.0.4            # via requests
docker-pycreds==0.2.1     # via docker
docker==2.7.0
docopt==0.6.2
docutils==0.13.1          # via botocore
idna==2.5                 # via requests
ipaddress==1.0.18         # via docker
jinja2==2.10
jmespath==0.9.0           # via botocore
markupsafe==0.23          # via jinja2
psutil==5.4.2
pymongo==3.6.0
python-dateutil==2.6.0    # via botocore
pyvmomi==<IP_ADDRESS>7.5-1
pyyaml==3.12
requests==2.18.4
six==1.10.0               # via docker, docker-pycreds, python-dateutil, pyvmomi, websocket-client
termcolor2==0.0.3
termcolor==1.1.0          # via termcolor2
texttable==1.1.1
urllib3==1.22             # via requests
websocket-client==0.44.0  # via docker
wrapt==1.10.11
mycmd==1.2.3

Using pex 1.4.0 or pex 1.4.1 having the following issue (everything works fine with pex 1.3.2):
$ ./build_pex.sh
pex: Constructed RequestsContext context <pex.http.RequestsContext object at 0x106060790>
/usr/local/var/pyenv/versions/2.7.14/envs/pex-build-May22/lib/python2.7/site-packages/urllib3/connection.py:344: SubjectAltNameWarning: Certificate for my.devpi.index has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
  SubjectAltNameWarning
  backports.ssl-match-hostname <IP_ADDRESS>
  termcolor2 0.0.3
  mycmd 1.2.3
  jmespath 0.9.0
  botocore 1.8.19
  docker-pycreds 0.2.1
  wrapt 1.10.11
  six 1.10.0
  termcolor 1.1.0
  docutils 0.13.1
  certifi 2<IP_ADDRESS>
  pymongo 3.6.0
  websocket-client 0.44.0
  blindspin 2.0.1
  urllib3 1.22
  MarkupSafe 0.23
  pyvmomi <IP_ADDRESS>7.5.post1
  python-dateutil 2.6.0
  texttable 1.1.1
  ipaddress 1.0.18
  docker 2.7.0
  PyYAML 3.12
  psutil 5.4.2
  chardet 3.0.4
  Jinja2 2.10
  requests 2.18.4
  docopt 0.6.2
  idna 2.5
pex: Target package WheelPackage('file:///private/var/folders/cc/5p9wct3j6xqgzk0r_lhb68nxjhps7j/T/tmpyKWJej/wrapt-1.10.11-cp27-cp27m-macosx_10_10_x86_64.whl') is not compatible with [('cp27', 'cp27m', 'manylinux1_x86_64'), ('cp27', 'cp27m', 'linux_x86_64'), ('cp27', 'none', 'manylinux1_x86_64'), ('cp27', 'none', 'linux_x86_64'), ('py2', 'none', 'manylinux1_x86_64'), ('py2', 'none', 'linux_x86_64'), ('cp27', 'none', 'any'), ('cp2', 'none', 'any'), ('py27', 'none', 'any'), ('py2', 'none', 'any')]
Traceback (most recent call last):
  File "/usr/local/var/pyenv/versions/pex-build-May22/bin/pex", line 11, in <module>
    sys.exit(main())
  File "/usr/local/var/pyenv/versions/2.7.14/envs/pex-build-May22/lib/python2.7/site-packages/pex/bin/pex.py", line 694, in main
    pex_builder = build_pex(reqs, options, resolver_options_builder)
  File "/usr/local/var/pyenv/versions/2.7.14/envs/pex-build-May22/lib/python2.7/site-packages/pex/bin/pex.py", line 624, in build_pex
    for dist in resolveds:
  File "/usr/local/var/pyenv/versions/2.7.14/envs/pex-build-May22/lib/python2.7/site-packages/pex/resolver.py", line 525, in resolve_multi
    use_manylinux=use_manylinux):
  File "/usr/local/var/pyenv/versions/2.7.14/envs/pex-build-May22/lib/python2.7/site-packages/pex/resolver.py", line 451, in resolve
    return resolver.resolve(resolvables_from_iterable(requirements, builder))
  File "/usr/local/var/pyenv/versions/2.7.14/envs/pex-build-May22/lib/python2.7/site-packages/pex/resolver.py", line 248, in resolve
    dist = self.build(package, resolvable.options)
  File "/usr/local/var/pyenv/versions/2.7.14/envs/pex-build-May22/lib/python2.7/site-packages/pex/resolver.py", line 321, in build
    dist = super(CachingResolver, self).build(package, options)
  File "/usr/local/var/pyenv/versions/2.7.14/envs/pex-build-May22/lib/python2.7/site-packages/pex/resolver.py", line 206, in build
    raise Untranslateable('Package %s is not translateable by %s' % (package, translator))
pex.resolver.Untranslateable: Package SourcePackage('file:///Users/me/.pex/build/wrapt-1.10.11.tar.gz') is not translateable by ChainedTranslator(WheelTranslator, EggTranslator, SourceTranslator)

it looks like what's happening here is that pex is attempting to translate wrapt 1.10.11 from sdist -> wheel (via e.g. python setup.py bdist_wheel) but that ends up with a platform native wrapt-1.10.11-cp27-cp27m-macosx_10_10_x86_64.whl (presumably because you're doing that step on OSX?) which does not satisfy the linux platform requirement (i.e. cross compilation is not a thing here).
pex usually falls back to this mode only if no linux-compatible bdists are found in the resolver path. it does not look like wrapt provides platform specific wheels on pypi for this version: https://pypi.org/project/wrapt/1.10.10/#files
does your custom index provide a linux-compatible bdist for wrapt-1.10.11 to support this build?
if so, does this improve if you pass an extended platform of --platform="linux-x86_64-cp-27-mu"?

(and if so, it seems we could improve the behavior here by widening the ABI permutations generated for non-specific platform specifications. IIRC, right now that keys off of the currently executing interpreters ABI, which would be different from OSX (cp27m) -> Linux (cp27mu) - hence the reason explicit specification helps.)

I think I may be experiencing a similar issue, although I'm using pants. I've opened a pants issue and have a small, self-contained example with debug output.
Apologies if I shouldn't be cross-posting here; the pantsbuild.slack.com folks thought it may be an ABI issue so I figured it was relevant.
This works fine if I build a wheel out of my package, add it to /wheelhouse and requirements.txt and then run pex -f wheelhouse --no-build --platform=linux-x86_64-cp-27-mu --platform=macosx-10.13-x86_64 -r requirements.txt -o my_pex.pex -m my_entry_point:main but it would be great to continue using pants and avoiding to have to pre-build the wheel.
Here is some additional relevant output after setting PEX_VERBOSE=5:
~/sandbox/pex_example (master) $ ./pants binary my_pkg

10:37:15 00:00 [main]
               (To run a reporting server: ./pants server)
10:37:15 00:00   [setup]
10:37:15 00:00     [parse]
               Executing tasks in goals: jvm-platform-validate -> bootstrap -> imports -> unpack-jars -> deferred-sources -> gen -> resolve -> resources -> pyprep -> compile -> binary
10:37:16 00:01   [jvm-platform-validate]
10:37:16 00:01     [jvm-platform-validate]
10:37:16 00:01   [bootstrap]
10:37:16 00:01     [substitute-aliased-targets]
10:37:16 00:01     [jar-dependency-management]
10:37:16 00:01     [bootstrap-jvm-tools]
10:37:16 00:01     [provide-tools-jar]
10:37:17 00:02   [imports]
10:37:17 00:02     [ivy-imports]
10:37:17 00:02   [unpack-jars]
10:37:17 00:02     [unpack-jars]
10:37:17 00:02   [deferred-sources]
10:37:17 00:02     [deferred-sources]
10:37:17 00:02   [gen]
10:37:17 00:02     [antlr-java]
10:37:17 00:02     [antlr-py]
10:37:17 00:02     [jaxb]
10:37:17 00:02     [protoc]
10:37:17 00:02     [ragel]
10:37:17 00:02     [thrift-java]
10:37:17 00:02     [thrift-py]
10:37:17 00:02     [wire]
10:37:17 00:02   [resolve]
10:37:17 00:02     [ivy]
10:37:17 00:02     [coursier]
10:37:17 00:02   [resources]
10:37:17 00:02     [prepare]
10:37:17 00:02     [services]
10:37:17 00:02   [pyprep]
10:37:17 00:02     [interpreter]
10:37:17 00:02     [build-local-dists]
10:37:17 00:02     [requirements]
10:37:17 00:02     [sources]
10:37:17 00:02   [compile]
10:37:17 00:02     [compile-jvm-prep-command]
10:37:17 00:02       [jvm_prep_command]
10:37:17 00:02     [compile-prep-command]
10:37:17 00:02     [compile]
10:37:17 00:02     [zinc]
10:37:17 00:02     [jvm-dep-check]
10:37:17 00:02   [binary]
10:37:17 00:02     [binary-jvm-prep-command]
10:37:17 00:02       [jvm_prep_command]
10:37:17 00:02     [binary-prep-command]
10:37:17 00:02     [py]
10:37:17 00:02       [cache]
                   No cached artifacts for 1 target.
                   Invalidated 1 target.pex: Constructed RequestsContext context <pex.http.RequestsContext object at 0x10e43a3d0>
pex: Constructed RequestsContext context <pex.http.RequestsContext object at 0x10e43a6d0>
pex: crawling link i=0 link=Link(u'file:///Users/Nakis/sandbox/pex_example/.pants.d/python-setup/resolved_requirements/CPython-2.7.10') follow_links=False
pex: crawling link i=0 link=Link('file:///Users/Nakis/sandbox/pex_example/wheelhouse') follow_links=False
pex: crawling link i=1 link=Link('https://pypi.python.org/simple/requests/') follow_links=False
pex: Constructed RequestsContext context <pex.http.RequestsContext object at 0x10e43acd0>
pex: crawling link i=0 link=Link('file:///Users/Nakis/sandbox/pex_example/wheelhouse') follow_links=False
pex: crawling link i=1 link=Link('https://pypi.python.org/simple/shapely/') follow_links=False
pex: Fetching file:///Users/Nakis/sandbox/pex_example/.pants.d/python-setup/resolved_requirements/CPython-2.7.10/requests-2.18.4-py2.py3-none-any.whl :: Fetching file:///Users/Nakispex: Fetching file:///Users/Nakis/sandbox/pex_example/.pants.d/python-setup/resolved_requirements/CPython-2.7.10/requests-2.18.4-py2.py3-none-any.whl: 2.0ms
pex:   Fetching file:///Users/Nakis/sandbox/pex_example/.pants.d/python-setup/resolved_requirements/CPython-2.7.10/requests-2.18.4-py2.py3-none-any.whl: 0.9ms
pex: Translating /private/var/folders/mk/bz4w0f3505190h3n4x21_jlc0000gn/T/tmpPZgn59/requests-2.18.4-py2.py3-none-any.whl into distribution: 3.6ms
pex: Fetching file:///Users/Nakis/sandbox/pex_example/.pants.d/python-setup/resolved_requirements/CPython-2.7.10/Shapely-1.6.4.post1.tar.gz :: Fetching file:///Users/Nakis/sandbox/ppex: Fetching file:///Users/Nakis/sandbox/pex_example/.pants.d/python-setup/resolved_requirements/CPython-2.7.10/Shapely-1.6.4.post1.tar.gz: 2.0ms
pex:   Fetching file:///Users/Nakis/sandbox/pex_example/.pants.d/python-setup/resolved_requirements/CPython-2.7.10/Shapely-1.6.4.post1.tar.gz: 1.3ms
pex: Translating /private/var/folders/mk/bz4w0f3505190h3n4x21_jlc0000gn/T/tmpz5YUtt/Shapely-1.6.4.post1.tar.gz into distribution :: Packaging Shapely :: Installing /var/folders/mk/bpex: Target package WheelPackage('file:///private/var/folders/mk/bz4w0f3505190h3n4x21_jlc0000gn/T/tmpZu724w/Shapely-1.6.4.post1-cp27-cp27m-macosx_10_13_intel.whl') is not compatible with CPython-2.7.10 / linux-x86_64-cp-27-mu
pex: Translating /private/var/folders/mk/bz4w0f3505190h3n4x21_jlc0000gn/T/tmpz5YUtt/Shapely-1.6.4.post1.tar.gz into distribution: 5057.5ms
pex:   Packaging Shapely: 4983.4ms
pex:     Installing /var/folders/mk/bz4w0f3505190h3n4x21_jlc0000gn/T/tmpM9WhBC: 4982.2ms

               Waiting for background workers to finish.
10:37:22 00:07   [complete]
               FAILURE
Exception caught: (<class 'pex.resolver.Untranslateable'>)

Exception message: Package SourcePackage(u'file:///Users/Nakis/sandbox/pex_example/.pants.d/python-setup/resolved_requirements/CPython-2.7.10/Shapely-1.6.4.post1.tar.gz') is not translateable by ChainedTranslator(WheelTranslator, EggTranslator, SourceTranslator)

pants does not yet consume pex 1.4.x, so there's no way these two particular issues could be related.  but in general, https://github.com/pantsbuild/pants is the best place to file and work on pants related tickets.

Sorry about that; comment deleted.
Well, that explains why pants hates my manylinux wheel. Thanks for the heads-up

@DrumMachineLearning no worries. 1.4.x was just released and contains a pretty invasive change to the way bdist resolution works, so we're letting that bake/stabilize upstream (here) first - then should be pulling that into pants shortly (sometime in the 1-2 weeks).

@kwlzn sorry for delay, here is more info.
I was inspecting this issue at OSX, but initially it started failing at our "build server" (container based on alpine linux) where pex version was not pinned in requirements.txt 🤦♂
At my custom index I have pre-built wheels for OSX and Ubuntu 16.04 (the intention is to run resulted pex application at both systems):

wrapt-1.10.11-cp27-cp27m-macosx_10_10_x86_64.whl
wrapt-1.10.11-cp27-cp27mu-linux_x86_64.whl

I've replaced --platform="linux-x86_64 with --platform="linux-x86_64-cp-27-mu" and it helped. Build was successful using pex==1.4.2 👍
Thanks!

@pavdmyt no worries! that's great - thanks for confirming.
I have a fix in mind to improve the ergonomics here so that it works as it did in 1.3.x for improved backward compatibility - will try to circle back to that within a week to cut 1.4.3.
until then, would use the extended platform form above as a workaround.

pex 1.4.3 is now cut, so the behavior here should be back to what you'd see with 1.3.x. let me know if you hit any further issues and I'd be happy to take a look.

FYI we had a similar issue and bumping the version from 1.4.1 to 1.4.3 fixed the problem for us. Thanks!


Annotation rule throws IllegalStateException

Two tests added to the AnnotationRuleTest.kt. The first one failed, the second one succeeds.

com.pinterest.ktlint.core.RuleExecutionException: java.lang.IllegalStateException: Annotations list should not be empty

@Test
fun `no annotation present fails`() {
    val code =
        """
        package com.example.application.a.b

        data class FileModel(val uri: String, val name: String)
        """.trimIndent()
    assertThat(AnnotationRule().format(code)).isEqualTo(
        """
        package com.example.application.a.b

        data class FileModel(val uri: String, val name: String)
        """.trimIndent()
    )
}

@Test
fun `no annotation present succeeds`() {
    val code =
        """
        package com.example.application.a

        import android.os.Environment

        class PathProvider {
            fun gallery(): String = Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_PICTURES).path
        }
        """.trimIndent()
    assertThat(AnnotationRule().format(code)).isEqualTo(
        """
        package com.example.application.a

        import android.os.Environment

        class PathProvider {
            fun gallery(): String = Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_PICTURES).path
        }
        """.trimIndent()
    )
}

Included the above two examples in the AnnotationRuleTest in the PR

The PR for this issue has been merged. But just now noticed that in the StandardRuleSetProvider, the rule is disabled due to this issue. Can the rule be re-enabled and this issue closed ?

Disabling that rule predates us taking over this project, but I can verify that all checks pass once it's re-enabled.

Sure ! Noticed all the rules disabled earlier have been re-enabled in this open PR.

It's a bit confusing - some of the disabled ones are still disabled, but the disabling is moved into the .editorconfig file. I'll add a comment into the StandardRulesetProvider in that PR to clarify.


chore: fix renovatebot

Changes proposed in this pull request

Fixing renovatebot via update of renovate.json file: instead of using
"ignorePaths": ["!test/**"]

(which was causing only renovatebot to check the integration test folder),
we duplicate the rule in the default config:base preset to
  "ignorePaths": [
    "**/node_modules/**",
    "**/bower_components/**",
    "**/vendor/**",
    "**/examples/**",
    "**/__tests__/**",
    "**/tests/**",
    "**/__fixtures__/**"
  ]

making sure to not include "/test/".
Context

Fixes #3056
Checklist

[x] Related issues linked using fixes #number
[ ] Tests added/updated
[ ] Make sure that all checks pass
[ ] Bruno collection updated (if necessary)
[ ] Documentation issue created with user-docs label (if necessary)
[ ] OpenAPI specs updated (if necessary)


Input out put problem from HackerRank

@Suganthb  , sorry that's not a code solving a problem it has to be a problem with description and solution for it


Add include hidden option to gitignore_path_array command

@Blightbuster thanks a lot! Any chance we can make the command accept --no-hidden flag instead of true/false?
also worth having few tests. there are duckscript based tests available so it should be easy to setup. wdyt?

@Blightbuster thanks a lot! Any chance we can make the command accept --no-hidden flag instead of true/false? also worth having few tests. there are duckscript based tests available so it should be easy to setup. wdyt?

Done so, hopefully CI passes 😄 Will try to add some tests now.

Btw. with the current implementation, the old gitignore_path_array command is now equal to the new gitignore_path_array --no-hidden command as it previously did exclude hidden files already. Or did I misunderstand your proposal for the flag?

Btw. with the current implementation, the old gitignore_path_array command is now equal to the new gitignore_path_array --no-hidden command as it previously did exclude hidden files already.

right, my mistake!!! so lets make the param as --include-hidden which is false by default if not defined. make sense?

Afaik adding actual tests would require me to add some test files e.g. folders, a gitignore as well as some hidden files (not sure how git even handles those).

you can create those files as part of the test. you can look at other fs tests i have (ds files) that do that and create a dir based on command name and so on....
naturally do it only for non windows as its simpler to do hidden file by just adding the dot at the start. you can also look at examples of me doing is_windows in some tests.

Codecov Report

Merging #236 (61aa1cc) into master (237123c) will decrease coverage by 2.74%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #236      +/-   ##
==========================================
- Coverage   93.62%   90.88%   -2.75%
==========================================
  Files         452      452
  Lines       16156    16156
==========================================
- Hits        15126    14683     -443
- Misses       1030     1473     +443

Impacted Files
Coverage Δ

...ipt_sdk/src/sdk/std/fs/gitignore_path_array/mod.rs
61.53% <0.00%> (-5.13%)
:arrow_down:

duckscript_sdk/src/utils/annotation.rs
0.00% <0.00%> (-90.00%)
:arrow_down:

.../src/sdk/std/env/set_current_directory/mod_test.rs
10.34% <0.00%> (-86.21%)
:arrow_down:

duckscript_sdk/src/sdk/std/json/encode/mod.rs
9.02% <0.00%> (-70.84%)
:arrow_down:

duckscript_sdk/src/sdk/std/test/test_file/mod.rs
16.66% <0.00%> (-61.54%)
:arrow_down:

...kscript_sdk/src/sdk/std/test/test_directory/mod.rs
25.00% <0.00%> (-61.54%)
:arrow_down:

...ckscript_sdk/src/sdk/std/var/unset_all_vars/mod.rs
48.14% <0.00%> (-51.86%)
:arrow_down:

...cript_sdk/src/sdk/std/var/get_all_var_names/mod.rs
48.14% <0.00%> (-51.86%)
:arrow_down:

...t_sdk/src/sdk/std/env/set_current_directory/mod.rs
45.71% <0.00%> (-51.43%)
:arrow_down:

duckscript_sdk/src/lib_test.rs
52.63% <0.00%> (-47.37%)
:arrow_down:

... and 87 more

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 237123c...61aa1cc. Read the comment docs.

Just tried making a test for it and some test (file based ones) fail on both windows and linux for me:
failures:
    sdk::std::fs::append::mod_test::run_not_exists
    sdk::std::fs::mv::mod_test::run_directory_to_directory
    sdk::std::fs::mv::mod_test::run_file_to_directory
    sdk::std::fs::mv::mod_test::run_file_to_file
    utils::io::io_test::create_empty_file_exists
    utils::io::io_test::create_empty_file_not_exists
    utils::io::io_test::write_to_text_file_not_exists

test result: FAILED. 804 passed; 7 failed; 4 ignored; 0 measured; 0 filtered out; finished in 1.85s

error: test failed, to rerun pass '-p duckscriptsdk --lib'

@Blightbuster thanks for the PR. lets ignore the test for now as the change is pretty simple one.
Feel free to push more PRs if you need more features :)


Im gonna make the FormAPI menu

I will make if its okay for you

sure, as long as it follows the existing code style. it should be switchable (enable it or disable) via the configuration file


Running on two 3090s?

Hi authors, I do not have access to solid hardware. What I have for now is two 3090s (24GB each). I am planning I run/debug the code with this setup and then move experiments to A100s. On these two 3090s, I have CUDA 12.4. Torch version 2.0.0 (in the requirements) does not support CUDA 12.X. I found that torch 12.1.1 support CUDA 12.1. This is the only change I have made in the requirements, otherwise the setup is as suggested.
When I run
torchrun --nproc_per_node=2 --master_port=6000 train.py ...

I am the code is getting stuck at the following progress step,
LlamaTokenizerFast(name_or_path='meta-llama/Llama-2-7b-hf', vocab_size=32000, model_max_length=32, is_fast=True, padding_side='right', truncation
_side='left', special_tokens={'bos_token': '<s>', 'eos_token': '</s>', 'unk_token': '<unk>', 'pad_token': '</s>'}, clean_up_tokenization_spaces=F
alse),  added_tokens_decoder={
        0: AddedToken("<unk>", rstrip=False, lstrip=False, single_word=False, normalized=False, special=True),
        1: AddedToken("<s>", rstrip=False, lstrip=False, single_word=False, normalized=False, special=True),
        2: AddedToken("</s>", rstrip=False, lstrip=False, single_word=False, normalized=False, special=True),
}
/mnt/shared_home/vdeshpande/miniconda3/envs/env_spag/lib/python3.9/site-packages/accelerate/accelerator.py:457: FutureWarning: Passing the follow
ing arguments to `Accelerator` is deprecated and will be removed in version 1.0 of Accelerate: dict_keys(['dispatch_batches', 'split_batches']).
Please pass an `accelerate.DataLoaderConfiguration` instead:
dataloader_config = DataLoaderConfiguration(dispatch_batches=None, split_batches=False)
  warnings.warn(
Installed CUDA version 12.2 does not match the version torch was compiled with 12.1 but since the APIs are compatible, accepting this combination
Using /mnt/shared_home/vdeshpande/.cache/torch_extensions/py39_cu121 as PyTorch extensions root...
Installed CUDA version 12.2 does not match the version torch was compiled with 12.1 but since the APIs are compatible, accepting this combination
Using /mnt/shared_home/vdeshpande/.cache/torch_extensions/py39_cu121 as PyTorch extensions root...
Detected CUDA files, patching ldflags
Emitting ninja build file /mnt/shared_home/vdeshpande/.cache/torch_extensions/py39_cu121/cpu_adam/build.ninja...
Building extension module cpu_adam...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
ninja: no work to do.
Loading extension module cpu_adam...
Loading extension module cpu_adam...
Time to load cpu_adam op: 3.3634016513824463 seconds
Time to load cpu_adam op: 3.0814285278320312 seconds
Parameter Offload: Total persistent parameters: 532480 in 130 params                                                                             [2024-09-04 15:34:07,215] torch.distributed.elastic.multiprocessing.api: [WARNING] Sending process 50337 closing signal SIGTERM
[2024-09-04 15:34:22,297] torch.distributed.elastic.multiprocessing.api: [ERROR] failed (exitcode: -9) local_rank: 0 (pid: 50336) of binary: /mnt
/shared_home/vdeshpande/miniconda3/envs/env_spag/bin/python

Any insights on resolving this issue?

It looks like your CUDA, accelerate, and pytorch versions are incompatible.
Also, I'm not sure whether 3090 can run the training... A possible solution might be using Lora to train your model.


Utils menu doesnt allow the toolkit to exit in all scenarios

I've just noticed I appear to have broken the Utils menu where it doesn't exit correctly in certain scenarios.
I'll get this fixed ASAP.
Sorry for any inconvenience

This should now be resolved.

Still appear to be having a few issues with this. I'll try and get this sorted.

I'm going to close this as I can't replicate it at all at the moment. I think its possibly when the script fails somewhere (which it obviously shouldn't do!) so happy to forget about it for now.


[Network] Address apiview review comments

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.Network


METAMODEL-140 Elasticsearch support complex mappings

My addition to #23 by @maphysics

added an exclusion of a unittest on Java 6 / ES 0.x.
did a basic code formatting.

If travis build is working based on this, then I thing we're ready to merge.

Seems to have fixed the build issue. I'll merge it in.


improve performance of agency cache

Scope & Purpose
Improve the performance of read operations of the agency cache, by not copying the hierarchical Node tree result for serialization, but by directly serializing the nodes to VelocyPack.
A quick benchmark with lots of cluster DDL operations showed good improvements for latency (faster), CPU time (lower) and the metrics for time spent in loadPlan and loadCurrent (lower).

[x] Bug-Fix for devel-branch (i.e. no need for backports?)
[x] Strictly new functionality (i.e. a new feature / new option, no need for porting)
[x] The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)

Testing & Verification
This change is a trivial rework / code cleanup without any test coverage.
http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/11121/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/11150/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/11155/

Tests blue.


docs: add how to view logs

@angiie should not merge the PR by your self, should be approved by reviewers before merging.


Add IpcRenderer

add ipcRenderer event

While I'm thinking of alternative ways to integrate preloads, I'll close it


Time out and Connection Alive properties

I set connection alive property less than the connection time out. But still connection is getting timed out. Pics attached

it seems that it can not connect to server... which branch you are using?
and also is it the same "error" that #17 ?

@moperacz No this is not the same error. I updated to Kafka_10 and let me try this connection time out  and update.

@moperacz kafka_10 branch is working fine now . Closing this issue.


TypeError: obj.hasOwnProperty is not a function #48

The 0.5.0 version results in bug.
In utils.js function convertNodeToObject results error above.
There is bug in different module, it uses xml2js.parseStringPromise
Previous version is fine.

I am a bit confused what this is referring to, since node-xml2js does not have a utils.js file nor does it have a convertNodeToObject function. I am assuming the bug you see is due to the backwards-incompatible change in node-xml2js 0.5.0 and whatever code uses it needs to be updated.

Sorry, I was too fast. Not util.js (it is different module, whic uses xml2js)
The problem is that parseStringPromise now returns object without prototype and function hasOwnProperty fails, but this is already in different module.  My opologizes. I will check in different place


Build and Deploy SAPIG 4.0.0

Build and deploy to relenvs SAPIG 4.0.0

Parent
Release Action
NOTE: Needed to manually change the pom.xml to get the release to work, need to revisit
Common
PR for Parent
Release Action
Core
PR for Parent & IG
Release Action
TTD

Issues so far
OB is showing an error on start up, likely missing config
RCS is not building on PR when removing the variables, Common didn't have this issue so need to investigate
Can't complete RS until RCS is building


[DOC]Need to add another model information in the pre-trained model listing

What do you want to do?

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
We recently published torchscript version of distiluse-base-multilingual-cased-v1 model. So we need to update this table
Expected row should be:
Model name: sentence-transformers/distiluse-base-multilingual-cased-v1
vector dimension: 512-dimensional dense vector space.
auto truncation: yes
torch script artifact:
model url:
https://artifacts.opensearch.org/models/ml-models/huggingface/sentence-transformers/distiluse-base-multilingual-cased-v1/1.0.1/torch_script/sentence-transformers_distiluse-base-multilingual-cased-v1-1.0.1-torch_script.zip
config url:
https://artifacts.opensearch.org/models/ml-models/huggingface/sentence-transformers/distiluse-base-multilingual-cased-v1/1.0.1/torch_script/config.json
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

This looks like it's already addressed:

I will close this issue. Please reopen if there are any issues. Thanks!
https://opensearch.org/docs/latest/ml-commons-plugin/pretrained-models/#supported-pretrained-models


Add CI for Android

We should set up CI for the Android targets so regressions like #571 can be catched.

I have a proposal to fix this. As I saw the "help wanted" tag and I have already set an Android CI for my own purpose (here, if you're curious) I thought I could help a bit.

Fixed in #649, ported to GHA and merged in #667

Fixed in #649, ported to GHA and merged in #667


Dark mode

Will add a dark mode toggle switch to switch between light mode and dark mode.
Pls assign it to me under LGM-SOC'21

@you ccan work on this issue but after changing share the link here first.

Okay! 👍

@TheArushiSingh any update ?


delete x-ms-identifiers that causes autorest fails

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

When I "autorest --powershell .\readme.md" locally:
I got this error:
ERROR: Schema violation: Additional properties not allowed: x-ms-identifiers (definitions > SqlDbMigrationStatusDetails > properties > listOfCopyProgressDetails)
- https://github.com/Azure/azure-rest-api-specs/blob/e8c359d8821038f133695c9b1f4cf40d330cbc80/specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:2871:4
Process() cancelled due to failure
" x-ms-identifiers" is the only appearance on this line. I think it should not be here.

latest autorest version can solve this error


B:18830 - Add Office Account Request Form

B-18830
MERGE AFTER B-19465 - Currently in Integration
Summary
This MR introduces functionality that will allow a user to request an office account by filling out a form.
Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the Office Sign In Page
Select the Request Account tab in the top right corner of the navigation bar
Fill out the required information on the form then select Request Account Button
Check database table office_users. You should see the record with a REQUESTED status. You can also check the network tab for a 200.

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Screenshots

Still a ton of commits in this that aren't yours

Warnings

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

:warning:
This PR does not include changes to storybook, even though it affects component code.

  Generated by :no_entry_sign: dangerJS against 0d884f8d9ab87efc73396af5354553d26a2fe995

Still a ton of commits in this that aren't yours

@danieljordan-caci  Yes that is because I have 2 different branches merged into mine. That commit history comes with it.

Still a ton of commits in this that aren't yours

@danieljordan-caci Yes that is because I have 2 different branches merged into mine. That commit history comes with it. My B-19465 and Camerons B-18823 I needed those main branches to develop in main because that code is not in main. By merging those branches into mine it comes with their commit history. Merging my main into my int branch brings all of that over. Main -> Does Not have 18823 and 19465. Int has both of those. But we develop off of main. My 18830 branch needs work from 18823 and 19465. Those branches were merged into my branch so I can complete the work on main. Only thing is the commit history comes with it. Created an Int branch off integration. Merge 18830 main branch into int branch. That git history comes with it. That is why this PR has all those commits. Only other way around that is to wait for the dependant stories to get to main then cherry pick my commits.

I think in situations (when there are multiple main branch dependencies that aren't in main yet) like this it might be best to base your INT branch off of integrationTesting and then cherry-pick the commits from your main branch into that and open the PR.
The commit history just seems very polluted and it's atypical to see it like this. I understand why they are there, but it just seems a little off.

Still a ton of commits in this that aren't yours

@danieljordan-caci Yes that is because I have 2 different branches merged into mine. That commit history comes with it. My B-19465 and Camerons B-18823 I needed those main branches to develop in main because that code is not in main. By merging those branches into mine it comes with their commit history. Merging my main into my int branch brings all of that over. Main -> Does Not have 18823 and 19465. Int has both of those. But we develop off of main. My 18830 branch needs work from 18823 and 19465. Those branches were merged into my branch so I can complete the work on main. Only thing is the commit history comes with it. Created an Int branch off integration. Merge 18830 main branch into int branch. That git history comes with it. That is why this PR has all those commits. Only other way around that is to wait for the dependant stories to get to main then cherry pick my commits.

I think in situations (when there are multiple main branch dependencies that aren't in main yet) like this it might be best to base your INT branch off of integrationTesting and then cherry-pick the commits from your main branch into that and open the PR.
The commit history just seems very polluted and it's atypical to see it like this. I understand why they are there, but it just seems a little off.

@danieljordan-caci That would cut down the commits on the int branch but that main branch will still have those commits from the other branches.

It would not because those specific commits that are related to main are already in main so they would not show up.
The reason why we are seeing all of these commits is because they are commits from main and not integrationTesting

Still a ton of commits in this that aren't yours

@danieljordan-caci Yes that is because I have 2 different branches merged into mine. That commit history comes with it. My B-19465 and Camerons B-18823 I needed those main branches to develop in main because that code is not in main. By merging those branches into mine it comes with their commit history. Merging my main into my int branch brings all of that over. Main -> Does Not have 18823 and 19465. Int has both of those. But we develop off of main. My 18830 branch needs work from 18823 and 19465. Those branches were merged into my branch so I can complete the work on main. Only thing is the commit history comes with it. Created an Int branch off integration. Merge 18830 main branch into int branch. That git history comes with it. That is why this PR has all those commits. Only other way around that is to wait for the dependant stories to get to main then cherry pick my commits.

I think in situations (when there are multiple main branch dependencies that aren't in main yet) like this it might be best to base your INT branch off of integrationTesting and then cherry-pick the commits from your main branch into that and open the PR.
The commit history just seems very polluted and it's atypical to see it like this. I understand why they are there, but it just seems a little off.

@danieljordan-caci That would cut down the commits on the int branch but that main branch will still have those commits from the other branches.

It would not because those specific commits that are related to main are already in main so they would not show up.
The reason why we are seeing all of these commits is because they are commits from main and not integrationTesting

No these commits are not in Main. 18823 and 19465 is not in Main. That is why In had to merge the main working branches for those stories into mine.

Commits based off of main* my bad

Okay, I believe I have all of my suggestions in.
I'm going to defer to @deandreJones on how to handle the merge because with the number of commits listed from you merging other branches into yours and then merging your main branch into this one, it just seems a little off.
We can either wait for those dependent PRs to be merged into main and then handle this or I'll follow Dre's direction on if it's safe to approve or not.

Okay, I believe I have all of my suggestions in.
I'm going to defer to @deandreJones on how to handle the merge because with the number of commits listed from you merging other branches into yours and then merging your main branch into this one, it just seems a little off.
We can either wait for those dependent PRs to be merged into main and then handle this or I'll follow Dre's direction on if it's safe to approve or not.

@danieljordan-caci The cleanest and low risk way from a commit history and best practices stand point is probably to wait until the dependents are in Main. Only thing is I would have to do what I did yesterday with 18828 which is create another branch, cherry pick my changes into it but there will be no need to merge in the dependent branches because those changes will be in main. Commit history will only have my commits then. In this case our branching strategy is to merge the main branch of needed work into our working main to complete the story then merge our main into our int. This brings all the commit history with it. We may need to discuss cherry-picking further and make adjustments in cases like this but I do not think cherry-picking should be a normal thing from a best practices point of view. We may need to discuss further on cases like this. Overall the cleanest way is to wait for the dependent stories to finish though.

One file requiring a merge conflict resolution at the time I write this
Compared the commit history from Cameron's main 18823 branch: main...B-18823-GHC-Create-Requested-Office-User and your 19465 branch: https://github.com/transcom/mymove/pull/12439/commits and see matching commits in this branch.
I noticed the Request Account button is touching the bottom of the page. Could you add some spacing around it?

@traskowskycaci Done

Okay, I believe I have all of my suggestions in.
I'm going to defer to @deandreJones on how to handle the merge because with the number of commits listed from you merging other branches into yours and then merging your main branch into this one, it just seems a little off.
We can either wait for those dependent PRs to be merged into main and then handle this or I'll follow Dre's direction on if it's safe to approve or not.

@danieljordan-caci The cleanest and low risk way from a commit history and best practices stand point is probably to wait until the dependents are in Main. Only thing is I would have to do what I did yesterday with 18828 which is create another branch, cherry pick my changes into it but there will be no need to merge in the dependent branches because those changes will be in main. Commit history will only have my commits then. In this case our branching strategy is to merge the main branch of needed work into our working main to complete the story then merge our main into our int. This brings all the commit history with it. We may need to discuss cherry-picking further and make adjustments in cases like this but I do not think cherry-picking should be a normal thing from a best practices point of view. We may need to discuss further on cases like this. Overall the cleanest way is to wait for the dependent stories to finish though.

IF there are dependencies necessary for this BL- then those need to be move along first- so please wait to merge this- until the depencies have been resovled(merged)


Moving the template file location

see https://github.com/appsmithorg/appsmith/issus/826#issuecomment-703093426 for details

Not sure how that will change the behavior, but let's see.

me too, but I can't experiment without PRs for it :-(


Having function to keep variadic parameter when c async call.

Having a build in function to save reference to the variadic parameters from function call such setTimeout(callback, time, args1, arg2, ..) then beeing able to push this parameters back to the the callback stack.
reference MUST be persisted among ASYNC call and eventually preventing the args to beeing garbage collected.
duk_spnapshot_t  s = duk_snapshot(ctx, idx, count);
...
duk_restore(ctx,s);

The normal way to do that would be to store the arguments e.g. as an array of values as part of the callback state (timer or such).
There are internal drafts for duk_pack() and duk_unpack() which would convert a sequence of values on the value stack into an array and vice versa. These should work for this purpose.


Stan should allow user defined clientId

When using stan broker and setting durable name there is no way to set the client id as well which is important when you use durable.
clientID := uuid.New().String()
Also I have noticed that if nats streaming goes down or network connection is lost stan plugin does not reconnect instead just complains that connection is down over and over, restarting the service re-connects fine.
2019/08/03 11:04:58 Accept error: nats: connection closed

do you try https://godoc.org/github.com/micro/go-plugins/broker/stan ?

strange I ran glide update and I don't have that in my version, will try to install again and see if it pulls it down. Thanks

@mti-adapter can you close the issue if all ok


Fail to delete the function in a function app which created with Flex Consumption (Preview) hosting plan

OS: All
Build Version: v1.14.1-alpha.0
Regression: Not a Regression
Repro Steps:

Create a python project with Http Trigger function.
Create a python function app with Flex Consumption (Preview) hosting plan and East US 2 EUAP location.
Deploy the python project to the above function app.
Expand the above function app -> Expand the "Functions" node -> Right click the function and execute "Delete Function..." action.
Check whether succeeds to delete the function.

Expect:
Succeed to delete the function.
Actual:
Fail to delete the function with an error.

More Info:
Another error occurs when deleting the function for the same function app in portal.

Similar to https://github.com/microsoft/vscode-azurefunctions/issues/4067, might be a different endpoint now.

I believe that this is fixed. Could it be reverified?

Verified

I believe that this is fixed. Could it be reverified?

Verified this bug on the latest main branch Functions extension build, this bug still reproduces.


[Bug] Fix onboarding image padding

This PR updates the image padding for different screen sizes during the onboarding flow.

Looks good.


Amend TDD calculation to respect 24 hours and 14 days

Modify weighted_average to respect the 24 hours of data and 14 days of total TDD.

I‘m genuinely confused. This was brought up as a topic of discussion and is now PR‘d with any further conversation about it or its side effects.

@dnzxy Sorry if the PR is too quickly. I noted the PR interested more than discussion in GitHub ;-)
@MikePlante1 :

10 or 14 days : just to be compliant with the TDD algorithm. Perhaps not useful but in this case, it will be better to rename variable and update the documentation if necessary !
2 hours or 24 hours : I did the mistake to believe each value is the eventual insulin value during 5'... and not the total previous 24h. Thanks!

I close the PR and update the discussion.

Oh, please don’t close, let’s just make it a draft for now. You did the work already, let’s not waste it 😊 Is that okay with you? I‘ll re-open and change to draft, if so 🤔

I could be wrong but I think I recall Tim Street commenting somewhere that in AAPS they found two hours unsafe.

Oh, please don’t close, let’s just make it a draft for now. You did the work already, let’s not waste it 😊 Is that okay with you? I‘ll re-open and change to draft, if so 🤔

Don't worry. it is more the argument of Mike than your remark 😂


"@code context provider" doesn't work.

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: macOS 14.5
- Continue: v0.9.168
- IDE: VS Code, Cursor, IntelliJ IDE

Description

To reproduce
N/A
Log output
No response

https://github.com/continuedev/continue/pull/1785  helps to reindex on file saves then update the UI synchronously, but I suspect there might be a handful of edge cases left.

Any updates on this? I'm experiencing this as well on a fresh install


[Webview2 Microsoft Windows] Drag and Drop files from Windows to Webview2

Ref issue: https://github.com/react-native-webview/react-native-webview/issues/1848
We need Webview2 to forward file drop events to the Webview2 content, so it can handle the file reception. Those files will be dragged from Windows.

still searching for solutions

@david-risney is there something in wv2 that makes this possible already today?
cc @chiaramooney

WebView2 has drag and drop APIs (for the composition controller that WinUI2 and WinUI3 WebView2 controls use) but I don't offhand know the state of them or if WinUI2 or WinUI3 WebView2 controls use those APIs. I'll need to get more info.

Talking with folks, it sounds like WebView2 drag and drop should be working, but there are still issues specifically with the WinUI2/3 WebView2 drag and drop support that are in progress. I couldn't find a corresponding github issue (if you're interested in that you might ping the WinUI folks)

Hello,
is there some progress on this issue?


systemctl commands need superuser access [ minor correction ]

The code in Create the service file needs a minor fix.
systemctl enable kestrel-hellomvc.service
must be updated to :
sudo systemctl enable kestrel-hellomvc.service

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dcdd2c35-bf2b-2673-d150-303a8aaa54d2
Version Independent ID: 815fe034-c9fc-aee3-a8b5-f2e860b30302
Content: Host ASP.NET Core on Linux with Nginx
Content Source: aspnetcore/host-and-deploy/linux-nginx.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@shirhatti

@Praveen-Rai Were you also required to sudo ...
systemctl start kestrel-hellomvc.service
systemctl status kestrel-hellomvc.service

@guardrex Yes, all systemctl commands require sudo access.

@guardrex Sure , Meanwhile i am struggling to get the app hosted using SSL and will put up the info as soon as i get clarity. That portion is badly missed in the hosting topics. So, please expect another issue from my end ;-)

Sure thing ... yes, it's best in a new issue. That might take longer to resolve than these few simple things here and on #7641. I hope I can knock these two little items out today.

Yeah. Looks like all these calls to systemctl require sudo


Update st-payment.tsx

Add buttonLabel property

First of all thanks for the PR 😄 😄
About the PR, the changes are right, now the user can pass the label as an attribute.
👍


Update data-options.md - Increase readability

Increase readability

Thanks for raising these articles to our attention. Unfortunately, copy edits need to be done internally to ensure that articles follow Microsoft style and formatting guidelines. We'll close this PR and submit the file for an internal copy edit.
#please-close


Add clippy to CI

Closes #236
#![deny(clippy::pedantic)] is too agressive and we have to switch off a lot of lints from pedantic groups like:
error: item name starts with its containing module's name
  --> src/randombytes.rs:25:1
   |
25 | / pub fn randombytes_into(buf: &mut [u8]) {
26 | |     unsafe {
27 | |         ffi::randombytes_buf(buf.as_mut_ptr() as *mut _, buf.len());
28 | |     }
29 | | }
   | |_^
   |
note: lint level defined here
  --> src/lib.rs:62:9
   |
62 | #![deny(clippy::pedantic)]
   |         ^^^^^^^^^^^^^^^^
   = note: #[deny(clippy::module_name_repetitions)] implied by #[deny(clippy::pedantic)]
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#module_name_repetitions

error: aborting due to 204 previous errors

So I decided not to include pedantic lints. Because we will have to either switch pedantic lints off or fix 204 errors and break the API.
Unresolved issue: https://github.com/sodiumoxide/sodiumoxide/issues/338

Pull Request Test Coverage Report for Build 965

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 94.668%

Files with Coverage Reduction
New Missed Lines
%

lib.rs
1
83.33%

Totals

Change from base Build 961:
0.0%

Covered Lines:
2912

Relevant Lines:
3076

💛  - Coveralls

bors: r+


How do you know if the magic packet is sent or not ?

Info:

PHPWakeOnLan version: #.#.#
PHP version: #
Operative system: #
Execution environment: Web or CLI

Description:
If the machine is connected the response is :
" Response :  OK  Magic packet sent to MAC:Address through <IP_ADDRESS>  bytes_sent 102  "
the same message is for a disconnected machine
Include issue description here.
Steps to reproduce:

Send WAL request to a disconnected machine
Expecting an error code or something like

I have to do further investigation to see if it's possible to acknowledge if the magic packet has been received and how to do it, but it would be a nice enhancement.


postcss-assign-layer usage in Vite

Hello
This is in with reference to issue: https://github.com/vitejs/vite/issues/3924
As mentioned, we can use this plugin to avoid the css module order issue.
So to solve this, how to give preference order with same component layer
Lets say there are 2 module.css in same component layer and there orders seems to be incorrect sue to vite issue.
how we can define the preference order using this plugin?
Thanks for the help!

Can you give an example of when this situation might occur?  I would suggest that normally if you're mixing CSS into a component, it should be at a separate layer, with either a higher or lower priority in the stack.

Hey @IanVS , thanks for the reply.
For example, I have 2 components:
Text.tsx and ErrorText.tsx
Text component has some styling like text color. ErrorText uses text component and also override the text color property to other color via classname prop: ErrorMessage
Both are in same components folder.
ErrorText:

        {errorMessage}

Now ideally ErrorText property should take the precedence as we have mentioned the error text style class in the end. But in Vite the order gets changed.
( same issue which other people facing)
So here , I should assign Text and ErrorText different layer?
There are many other such cases in our app.
Also there is one more query:
Any idea if I just define the import order of styles in ErrorText component like this, this may solve the css order issue without postcss layer?
import textStyles from '../Text/Text.module.css';
import styles from './ErrorText.module.css';

import textStyles from '../Text/Text.module.css';
import styles from './ErrorText.module.css';

This works fine as long as you're not using code splitting / lazy loading in your app.  If you are, then you'll likely hit the Vite issue.
Another way you could solve this would be to ensure that ErrorText is not actually overriding any of the properties of Text, but rather adding additional ones.  So maybe Text gets its color from a base/default style with a low-priority level, and ErrorText sets the color in the component.
Another thing we have done, if we have common patterns that we want to re-use across different components, is to create a layer for patterns, which we import into our base css file.  So, for example, we have a border-focusable class that we can then use on any form elements that need to have a particular border color when they are focused.  In this way, you could identify the parts of <Text> that should be shared with <ErrorText>, and extract those into a separate CSS file with a lower-priority layer.  Then you wouldn't need to import multiple component styles, you could instead use those shared styles.
I haven't tried it myself, but you could also try setting a higher-priority layer like overrides, and then in your <ErrorText> css, whatever properties are intended to override the base Text properties, you could assign them that layer.
FWIW, here's our base-css file, to give an idea of how it could be structured:
/* establish a layer order up-front, from lowest to highest priority */
@layer defaults, theme, libraries, patterns, components, utilities, overrides;

/** Defaults */
@import url('defaults.css');

/** Theme */
@import url('theme/colors.css');
@import url('theme/typography.css');

/** Patterns */
@import url('../../components/atoms/forms/border-focusable.css');
@import url('../../components/patterns/menus/menu.css');

/** Components are assigned by a PostCSS plugin for all `*.module.css` files */

/** Utilities */
@import url('utilities/layout.css');
@import url('utilities/color.css');
@import url('utilities/borders.css');
@import url('utilities/typography.css');

Thanks @IanVS  for the detailed explanation. Yeah we want to use css code split. After that only we face this issue. We will try to structure our styles in different layer so that we can set the priority accordingly.


[W5][T12-1]Sreyans Sipani

Extended Find command for all fields

@tejas2805, can you help me review this PR?

Very handy improvement. The search command is more powerful now


unrecognized node type For PG10 and PG11

postgres=# \d+ test_tt
Did not find any relation named "test_tt".
postgres=# LOAD 'pgtt';
LOAD
postgres=# \d+ test_tt
Unlogged table "pgtt_schema.test_tt"
Column |  Type   | Collation | Nullable | Default | Storage  | Stats target | Description
--------+---------+-----------+----------+---------+----------+--------------+-------------
id     | integer |           |          |         | plain    |              |
lbl    | text    |           |          |         | extended |              |
postgres=# INSERT INTO test_tt VALUES (1, 'one'), (2, 'two'), (3, 'three');
ERROR:  unrecognized node type: 375
postgres=# select * from test_tt;
ERROR:  unrecognized node type: 375
postgres=# select version();
version
PostgreSQL 11.11 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39), 64-bit
(1 row)
This is the problem I encountered during my test. Could you tell me how to solve it？
It looks like there is a problem with "PGTT provide a query string".

Well, It is ok in 10.5 ……
Maybe there is a problem with the non-release version code.
Thank you anyway.

I can reproduce the problem on 11 and 10, I will fix that it should work from 9.5 to 13 the same way.

Commit 0e13898 fix this portability problem. Thanks for the report.

Thank you for your reply.
I have another question, why can't "pgtt.so" be preloaded? If it can, what should I do?

This is because pgtt need to be loaded in a real session, when used through GUC session_preload_libraries it is loaded too early some information are not yet available and especially when the extension is trying to force the search_path. This is why it must be loaded using LOAD, but this can be done immediately after your application is opening a connection.


Github Actions: Add jobs running in Ubuntu 20.04 Focal

Following the addition of Ubuntu Focal Docker container, it's time to start adding a CI pipeline that may run over it as well.

I think we could even add it and fix any possible but unlikely breakage along the way 👍

Seems like we have a limitation in the matrix size - Github automatically cancels the rest of the jobs of the matrix. I guess it's reasonable to keep the Nuttx builds only in 18.04 for now, and gradually move some targets to 20.04.

Here are the container changes that go with this pr:
https://github.com/PX4/containers/pull/256
https://github.com/PX4/containers/pull/257
https://github.com/PX4/containers/pull/258
Could you please add them next time for completeness?

Here are the container changes that go with this pr:
PX4/containers#256
PX4/containers#257
PX4/containers#258
Could you please add them next time for completeness?

You mean referene them? That's fine.

Fine with me. But now we don't test 16.04 anymore, right? If so we should remove in the docs that it is supported. Otherwise, we should still keep one test.

Fair enough. I will add it to the SITL tests job matrix in a new PR.

@jinger26 this is worth sharing, we now support Ubuntu 20.04 (Focal) 🎉

FYI, docs updated to reflect this: https://github.com/PX4/Devguide/pull/998

FYI, docs updated to reflect this: PX4/Devguide#998

Thank you @hamishwillee!

Just a note here as exciting as this might be Ubuntu 20.04 is not released yet but planned for April 23, 2020 so I'd be more careful with "supporting". We're using the beta/daily to do our testing.

Just a note here as exciting as this might be Ubuntu 20.04 is not released yet but planned for April 23, 2020 so I'd be more careful with "supporting". We're using the beta/daily to do our testing.

I would say that considering we are safely running in beta, we can say with 99% certainty this will run in the official release.


[FEATURE] Set different shares for different engines

Code of Conduct

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

Search before asking

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

Describe the feature
We hope that spark can be shared at the use level, and trino can be shared at the pool level, but kyuubi has not yet provided the setting for configuring the sharing level according to the engine type
"kyuubi.engine.share.level" is globally effective, and session conf is only for sessions alone. It is hoped to add different sharing levels according to engine settings. For example: "kyuubi.engine.{spark|trino|flink}.share.level"
The priority is :  session conf > kyuubi.engine.{spark|trino|flink}.share.level > kyuubi.engine.share.level
Motivation
No response
Describe the solution
No response
Additional context
No response
Are you willing to submit PR?

[x] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

Sounds like an interesting idea. The only concern on my side is the priority.
I propose to keep consistent with the existing behavior in Kyuubi project.

session conf > kyuubi-defaults.conf
kyuubi.engine.{spark|trino|flink}.share.level > kyuubi.engine.share.level

That means if the administrator set the kyuubi.engine.spark.share.level=GROUP in kyuubi-defaults.conf, and the user who wants to override it must use kyuubi.engine.spark.share.level=USER instead of kyuubi.engine.share.level=USER
What do you think about this idea?

If kyuubi.engine.share.level is disabled on the client side, it will be difficult to be compatible with the historical version. On the kyuubi Server side, we may change kyuubi.engine.share.level = user to kyuubi.engnie.{spark|trino|...}.share.level = user according to the engine type, which may be a better way

I see your point, but sorry, I oppose it.
From the community perspective, this is a brand-new feature to allow configuring engine share in fine-grained, if we follow the design you proposed, we need to explain every time, to users who are new to Kyuubi, that due to historical reasons, the behavior is not intuitive ... balabala. That's indeed the origin of technical debt.

Ok, I try to submit a pr according to your idea

thank you @ASiegeLion


KeyError: 'MirusMCP'

Traceback (most recent call last):
File "PIGv.py", line 338, in
ncldv_out=ncldv_out[ncldv_out['MirusMCP']>=1]
File "/home/xiaomeng/miniconda3/envs/PIGV/lib/python3.7/site-packages/pandas/core/frame.py", line 3458, in getitem
indexer = self.columns.get_loc(key)
File "/home/xiaomeng/miniconda3/envs/PIGV/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 3363, in get_loc
raise KeyError(key) from err
KeyError: 'MirusMCP'
:Hello, thank you for writing such excellent software, but I have encountered the above problems when running, may I ask how to solve this?

This usually comes up when you have a bin that has another mirusvirus
marked gene but no MCP. It shouldn't affect other outputs as mirusviruses
are resolved at the end.
On Thu, Jun 6, 2024, 3:33 AM Xiaomeng Wang @.***> wrote:

Traceback (most recent call last):
File "PIGv.py", line 338, in
ncldv_out=ncldv_out[ncldv_out['MirusMCP']>=1]
File
"/home/xiaomeng/miniconda3/envs/PIGV/lib/python3.7/site-packages/pandas/core/frame.py",
line 3458, in getitem
indexer = self.columns.get_loc(key)
File
"/home/xiaomeng/miniconda3/envs/PIGV/lib/python3.7/site-packages/pandas/core/indexes/base.py",
line 3363, in get_loc
raise KeyError(key) from err
KeyError: 'MirusMCP'
:Hello, thank you for writing such excellent software, but I have
encountered the above problems when running, may I ask how to solve this?
—
Reply to this email directly, view it on GitHub
https://github.com/BenMinch/PIGv/issues/3, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUT6BLJZ7XXKHJRZ37IUZWDZGAGD5AVCNFSM6AAAAABI4EUGP6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZTONJUHA4TSMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Cast explicitly to c_long which is the underlying type

I just copied the type from the underlying struct but if you prefer I'm happy to use the rust types and do some target_pointer_width shenanigans.

Or I guess thinking about this more I can just cast to  FT_Pos and FT_Fixed and let freetype deal with it. I don't have strong opinions so let me know if you'd prefer I did this some other way!

Casting to the freetype types makes more sense to me.

Updated, thankyou! A test fails on my arm machine but I'm not sure if that's a regression or it never worked.

Please run cargo fmt to make CI happy :)


Update copyright 2023

Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 98.238%. Remained the same when pulling e24b3620b0ac4c10e21284d43befae1322298118 on copyright into 4f1d9a0dbeda4d7eb88b9948e6d2cc503f8ecf9f on main.


Rubicon: Move user.consent

Hard times create strong developers,
strong developers create good frameworks,
good frameworks create weak developers,
weak developers create this....,
this... creates hard times

Hard times create strong developers, strong developers create good frameworks, good frameworks create weak developers, weak developers create this...., this... creates hard times

So inspired :muscle:


Can't download caddy with selected options

1. What version of Caddy are you using (caddy -version)?
0.10.3, trying to update to 0.10.4
2. What are you trying to do?
Download caddy
3. What is your entire Caddyfile?
N/A
4.
N/A
5. Please paste any relevant HTTP request(s) here.
N/A
6. What did you expect to see?
Caddy to download
7. What did you see instead (give full error messages and/or log)?
Resolving caddyserver.com (caddyserver.com)... <IP_ADDRESS>, 2604:a880:2:d0::1145:e001
Connecting to caddyserver.com (caddyserver.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2017-06-29 14:49:27 ERROR 500: Internal Server Error.

8. How can someone who is starting from scratch reproduce the bug as minimally as possible?
wget 'https://caddyserver.com/download/linux/amd64?plugins=dns,http.authz,http.awslambda,http.cgi,http.cors,http.datadog,http.expires,http.filemanager,http.filter,http.git,http.grpc,http.hugo,http.ipfilter,http.jwt,http.login,http.mailout,http.minify,http.prometheus,http.proxyprotocol,http.ratelimit,http.realip,http.reauth,http.upload,tls.dns.cloudflare'
This seems to be a repeat of #1712, but i can remove all but http.authz and the issue continues.
Thanks!

If one plugin fails to build, the build will fail -- and there are known issues with a couple plugins right now and the authors are working on them. (Do you really use all those? Wow! If not, download only the plugins you need. This is good practice in general.)

i was downloading with a far smaller set of plugins (read: not all of them) and was also seeing the 500 errors, but wanted to try out a few things, so tried downloading all at the same time to avoid excessive timeouts over time, but alas, no dice.
I have been using this script (janky python) in the past to download builds, but even that small set is failing:
#!/usr/bin/env python
import urllib
import tarfile
import os

configuration = {
    'architecture': 'amd64',
    'os': 'linux',
    'http_plugins': [
                        'cors',
                        'expires',
                        'filemanager',
                        'filter',
                        'git',
                        'ipfilter',
                        'mailout',
                        'minify',
                        'ratelimit',
                        'realip',
                        'prometheus',
                     ],
    'dns_plugins': [
                    'cloudflare',
                   ]
    }
plugins = ['%s%s' % ('http.', plugin) for plugin in configuration['http_plugins']]
plugins += ['%s%s' % ('tls.dns.', plugin) for plugin in configuration['dns_plugins']]
url = 'https://caddyserver.com/download/%s/%s?plugins=%s' % (
    configuration['os'],
    configuration['architecture'],
    ','.join(plugins)
)

urllib.urlretrieve(url, '/tmp/caddy_latest.tar.gz')
tar = tarfile.open('/tmp/caddy_latest.tar.gz')
tar.extract('caddy', '/tmp')
os.system('mv /usr/local/bin/caddy /tmp/caddy-previous')
os.system('cp /tmp/caddy /usr/local/bin/caddy')
os.system('chown www-data.www-data /usr/local/bin/caddy')
os.system('chmod +x /usr/local/bin/caddy')
os.system('setcap cap_net_bind_service=+ep /usr/local/bin/caddy')

One of the plugins that's currently being fixed by the author is the filemanager plugin. Sorry the error messages aren't more helpful; it would involve parsing log output which varies depending on where the error occurred...

Anyway, don't mind me -- I'll close this issue though since it's not an actionable item for Caddy itself. And it's being worked on by the right people. :+1:

@mholt is there anything secret in the build logs? I'm thinking you could return the build logs, or at least the part near the error. Probably not really needed to parse it, it would at least give people who run into errors something to go on as to which plugin is failing.

@francislavoie Possibly? I haven't guaranteed that there won't be, so to be conservative I'm not revealing build logs to the public. Maybe in the future.
@tnwhitwell The broken plugins should be working again, except for hook.service which should be working as soon as the author deploys it.


url for attachaments should use file basename instead of id

otherwise, replacing a file with the a new version with the same name require edit the document to change ids.
the changes should be backward compatible

Hello, I just installed Waliki from git tarball and on python 3 :-)
I tried to copy a "slide page" from Hovercraft! and I run into a few problems with attachment naming: if you have a :css: directives, it needs the actual filename on disk, if instead you refer to an image you can simply attach it and use the :image: command created by the attachment manager.
IMHO the only decent solution is to use the same relative path for both the web and the filesystem and avoid the id component: if a user re-saves another file with the same name, it'll be overwritten and eventually it can be recovered from git's repo.
Having the same relative paths is also in the interest of reusing the .rst documents "alone" without waliki (I had a tiny but useful wiki in Zope and I'll never use something else that can't allow me easy replication and independent access to my files ;-) )

Hello @RobertoMaurizzi, I completely agree with your arguments.  I have a branch started but a bit outdated
https://github.com/mgaitan/waliki/compare/96_attachment_no_id
I would like to have this for the next version, but my daughter was born few days ago and my "open source time" decreased a lot for obvious reasons :baby_bottle:
do you feel confident to continue/redone that ?


Switch bitcoin core rpc wallet from legacy to descriptor

Legacy wallets will be discontinued, this disables importaddress which has to be replaced by importdescriptor in register_address

Fixed


Support IQMClient circuits batch submissions

Currently pytket-iqm.IQMBackend.process_circuits takes in multiple circuits, but executes them through an IQMClient one by one. Starting with version 4.0 IQMClient supports batch circuits submission, if certain requirements are met:

every circuit to be run with the same amount of shots
measuring same qubits in every circuit

If circuits not matching those requirements are submitted, IQM backend will return an error.
While this might look like a very limited use-case it is useful for submitting similar circuits for execution as it provides a significant execution performance boost reducing transport and conversion overhead and allows to use quantum computer hardware more efficiently.
We suggest to improve process_circuits by submitting the circuits for execution as a batch if the requirements are met, while keeping one-by-one execution as a fallback.

Thank you for this suggestion and making us aware of this functionality. We will keep that in mind to add that!


Test with python 3.8 and 3.9

Builds on #179 as the build is otherwise broken. Might be wise to drop a few python versions to speed up testing.

I prefer to go with https://github.com/dropbox/sqlalchemy-stubs/pull/186 instead, that I just merged. We can revisit Python 3.9 a bit later.

I prefer to go with https://github.com/dropbox/sqlalchemy-stubs/pull/186 instead, that I just merged. We can revisit Python 3.9 a bit later.


Master task list

[x] DOM event model:

[x] (implemented in v1 series) Decouple message processing and event processing and make event processing asynchronous.
[x] Make native JS objects extendable.
[x] EventTarget and Event

[x] Basic module support

[x] Backend support
[x] Basic built-in module support
[x] PoC modules:

[x] fb:playback
[x] fb:selection

[ ] Core API

[x] Input interaction

[x] MouseEvent
[x] WheelEvent
[x] KeyboardEvent

[ ] Graphics/Canvas API:

[ ] ???

[ ] Reimplement fb2k API

[ ] ???

[ ] Reimplement utils API

[ ] ???

[ ] drag-n-drop
[ ] Basic external module support
[ ] JSON config

[ ] Backend
[ ] API
[ ] UI

[ ] Broadcast Channel API
[ ] CustomEvent
[ ] fs module
[ ] Local file storage (Web Storage API?)
[ ] Clipboard API (module or part of window)
[ ] TODO cleanup
[ ] v1 shim
[ ] TS bindings
[ ] docs

[ ] API
[ ] Site

@TheQwertiest <3, it's nice and refreshing to see you back =)

Thanks :)
I'm not back yet though, but it's mostly the only hobby that's available for me right now...

Happy to see your update.


typo in nearest_neighbour function

the nearest_neighbour function in vision.py called idx.arr, but the array initialized is index

@vincentme do you want to send a PR or do you want me to fix it?

Please go ahead do that. This is my first time report a bug, and not really sure how to fix it.

@vincentme I am going to fix this, but for future reference you can follow this guide:
https://github.com/arrayfire/arrayfire/wiki/Contribute-code-using-github
It was written for arrayfire library, but the same workflow applies to arrayfire-python as well.

This has been fixed in devel.


notification filter message should include filter name

tried it both ways, think it looks better with minimal text, you'll see the full filter message if you tap and view the post


No supported encrypter found. The cipher and / or key length are invalid.

Hallo,
on Ubuntu 14.04 LTS, using Apache2 and PHP5, I get this error message:
"No supported encrypter found. The cipher and / or key length are invalid. "
I am using a fresh Cachet Version 1.1 with sqlite as database.
Mebus

Ah you'll need to run php artisan key:generate followed by php artisan config:cache.


Documentation link for API examples(404 not found)

The API examples link in the README.md on the homepage of repository i.e
https://github.com/shogun-toolbox/shogun
seems to be not working(error code 404 not found) i.e
https://www.shogun.ml/examples/latest/index.html
and needs to be changed.

i'd like to solve this but there is no file existing as index.html

Shogun comes with automatically generated API examples. How to use them is provided here
https://github.com/shogun-toolbox/shogun/blob/develop/doc/readme/EXAMPLES.md#meta_examples.
Should we just remove that API examples link from README.md or we can replace it with the above link.
@vigsterkr @gf712 thoughts?

Yes even on the official website https://www.shogun-toolbox.org/
"examples"  button in navigation bar doesn't work and gives out a 404 error.

fixed


mAP of CenterNet with HarDNet68

Hi, CenterNet with your HarDNet as the backbone worked well on COCO!
Have you tried HarDNet68? If yes, could you provide mAPs of that variant?
Thank you and sorry if I missed something.

Hi, sorry that we haven't had a chance to train CenterNet-HarDNet68, but I will definitely share it once we have it.

Hi, sorry that we haven't had a chance to train CenterNet-HarDNet68, but I will definitely share it once we have it.

Thank you! Looking forward to your results!


Combine alternate type rules

Hi,
Springfox: 2.8.0
Spring Boot: 1.5.9.RELEASE
Vavr: 0.9.2
Is it possible to "combine" alternate type rules?
Example:
I have an alternate type rule for Vavr's Option:
newRule(
    typeResolver.resolve(Option.class, WildcardType.class),
    typeResolver.resolve(WildcardType.class)
    ),

The way I understand it, whenever Springfox sees an Option<Whatever>, then it will instead consider it as a Whatever, am I right? (I know I could use .genericModelSubstitutes(Option.class) but I had exactly the same problem with it)
Then I have a second alternate type rule for other types (e.g. LocalDateTime, even though AFAIK it should be supported by default by Springfox):
newRule(
    typeResolver.resolve(LocalDateTime.class),
    typeResolver.resolve(Date.class)
),

What I was expecting is, when I have a model (either as parameter, body, or return type) which contains a field of type Option<LocalDateTime>, first it's considered as a LocalDateTime (thanks to first rule), which is then considered as a Date (thanks to second rule).
However, this doesn't work.

In "example value", the field is not displayed.
In "model", the field is displayed, but is empty:

And at the top of the Swagger UI, I get an error:

Resolver error at paths./bla.post.parameters.0.schema.properties.optionLDT.$ref
Could not resolve reference because of: Could not resolve pointer: /definitions/LocalDateTime does not exist in document

However, if I "hardcode" the type and generic type as such in my alternate rule:
newRule(
    typeResolver.resolve(Option.class, LocalDateTime.class),
    typeResolver.resolve(Date.class)
),

Then the field works just fine.
But this solution doesn't fit/scale well for my needs, because we have plenty of generic types (Vavr's structures like List, Option, Seq, Set, etc.), sometimes combined together (just like a List<Set> or an Option<LocalDateTime>).

Have I misunderstood how the "combination" of alternate rules works?
If yes, is my need possible with Springfox? (Without hardcoding all possible combinations)
If not, is it a bug? If it looks like a bug, I can try to setup a small repo to reproduce the issue.

Thanks for any help!
Cheers

Great question @Sir4ur0n!
I know its kind of cumbersome, but the way its was designed is for it to be a dumb substitution rule based on a certain priority of rules. The idea being given a set of types springfox will find the highest priority rule to match the source type and provide an alternate for it. It is not meant to be recursive mainly because:

For some cases you may not want to substitute the type, i.e. leave it as Optional<LocalDateTime> but convert Optional<LocalDate>
Sometimes there might be complex substitution rules especially related to nested generics, the engine might end up spinning its cycles till it reaches a stack overflow exception.

One way to address it is possibly to try and implement your own https://github.com/springfox/springfox/blob/6ff10f818ecda34913edc17e7cb501f48d756fc7/springfox-core/src/main/java/springfox/documentation/schema/AlternateTypeRuleConvention.java#L27, where you register wildcard rules, but give higher priority to ones that are exceptions to the convention.

Thank you for your answer @dilipkrish!
I took a look at AlternateTypeRuleConvention but I don't see how I can fix my problem with it since it only takes a list of AlternateTypeRule and an order. The recursion problem remains the same?
I also considered writing a custom WildcardType which would recursively not only collectReplaceables of current wildcard, but also recursively reapply springfox.documentation.schema.AlternateTypeRule#alternateFor to the replaced type, unfortunately it looks like WildcardType cannot be extended.
Have I misunderstood your idea?
Also, I definitely understand your point about not doing recursion "by default", however, could we imagine an additional method in Docket that would take alternate types and apply all other alternate types on the result?
Something like
.recursiveAlternateTypeRules(recursiveTypeRules())
.genericModelSubstitutes(...)
.alternateTypeRules(alternateTypeRules());

private AlternateTypeRule[] recursiveTypeRules() {
    return new AlternateTypeRule[]{
newRule(
            typeResolver.resolve(io.vavr.collection.List.class, WildcardType.class),
            typeResolver.resolve(java.util.List.class, WildcardType.class)
        )
    };
  }

private AlternateTypeRule[] alternateTypeRules() {
    return new AlternateTypeRule[]{
newRule(
            typeResolver.resolve(LocalDateTime.class),
            typeResolver.resolve(Date.class)
        )
    };
  }

Thus if you had a io.vavr.collection.List<io.vavr.collection.List<LocalDateTime>> this would first be converted to a java.util.List<io.vavr.collection.List<LocalDateTime>> which would then be converted to a java.util.List<java.util.List<LocalDateTime>> which would then become java.util.List<java.util.List<Date>>.
Does that make sense? ^^'

Thank you @dilipkrish
In case anyone is interested in this, I managed to make it work using this:
// Docket configuration
.alternateTypeRules(new RecursiveAlternateTypeRule(typeResolver, List.of(
    new AlternateTypeRule(
        typeResolver.resolve(Option.class, WildcardType.class),
        typeResolver.resolve(WildcardType.class)
    ),
    new AlternateTypeRule(
        typeResolver.resolve(LocalDateTime.class),
        typeResolver.resolve(Date.class)
    )
)))

// RecursiveAlternateTypeRule.java
public class RecursiveAlternateTypeRule extends AlternateTypeRule {

  private List<AlternateTypeRule> rules;

  public RecursiveAlternateTypeRule(TypeResolver typeResolver, List<AlternateTypeRule> rules) {
    // Unused but cannot be null
    super(typeResolver.resolve(Object.class), typeResolver.resolve(Object.class));
    this.rules = rules;
  }

  @Override
  public ResolvedType alternateFor(ResolvedType type) {
    ResolvedType newType = rules.flatMap(rule -> List.of(rule.alternateFor(type))
        .filter(alternateType -> alternateType != type))
        .getOrElse(type);

    if (appliesTo(newType)) {
      // Recursion happens here
      return alternateFor(newType);
    }

    return newType;
  }

  @Override
  public boolean appliesTo(ResolvedType type) {
    return rules.exists(rule -> rule.appliesTo(type));
  }
}

This is a tiny bit hacky because I use a custom AlternateTypeRule to store a list of AlternateTypeRules for which it should be recursively managed, but it seems to work like a charm.
I used this dummy model to test my APIs:
// MyModel.java
@Data
public class MyModel {
  private String name = "";
  private Option<String> maybeName = none();
  private Option<Option<String>> maybeMaybeName = none();
  private Integer number = 42;
  private Option<Integer> maybeNumber = none();
  private Option<Option<Integer>> maybeMaybeNumber = none();
  private LocalDateTime date = LocalDateTime.now();
  private Option<LocalDateTime> maybeDate = none();
  private Option<Option<LocalDateTime>> maybeMaybeDate = none();
}

And swagger seems happy with it:

@dilipkrish Should we keep this issue open for Springfox Swagger to support recursive alternate type rules? If you don't want Springfox Swagger to support them, then feel free to close this issue.
Thanks again!

Thanks awesome @Sir4ur0n ! thanks for sharing your solution


Applications page

Page to list applications.
Still have to implement pagination.

@tuler,
I am getting an Application error: a client-side exception has occurred (see the browser console for more information). when accessing the /applications.  Also, it needs a rebase since it's set up on pnpm.

Hey @tuler , @brunomenezes , I rebased the branch, fixed the client side error happening in Address component and implemented pagination.

LGTM. Can we have another review?


Less janky code for string writes

https://github.com/Owez/clonk/blob/15e8676fe218f63a4f6ca36f4f33300161f9c2d3/src/lib.rs#L293
Self-explanatory once you read the rest of it; the current .push_str() and format!() system isn't the best and should be replaced by a write!() macro.
The reason why the function itself returns String is to simplify the logistics of getting it's length compared to writing directly to the buffer, due to how the tab_to function works to format help (currently, see #2).

Seems like this was already done, seems good to me with write_fmt for io::Write


Upgrading from version 3 to 4 breaks the application

**
I have tried to upgrade from version 3 to 4 to use the EVENT CALENDAR and now I get error on field that don have a arefrance anymore
for example
                <views:CalendarView x:Name="xCalendar" Grid.Row="6" SelectionType="Single"                                       DayRangeMinimumDate="{Binding Today}" IsVisible="false"  SelectionAction="Modify"   />
while I have this import as required:
    xmlns:views="clr-namespace:XCalendar.Maui.Views;assembly=XCalendar.Maui"
will yield error on:

ItemPage.xaml.cs(55, 27): [CS1061] 'CalendarView' does not contain a definition for 'SelectedDates' and no accessible extension method 'SelectedDates' accepting a first argument of type 'CalendarView' could be found (are you missing a using directive or an assembly reference?)

and so does DayRangeMinimumDate and SelectionAction with the same error
**
Everything needs to be working, the upgrade alone breaks the application, when I change the nugget back to version 3 everything works ok
the problem is on .NET MAUI app
running on m1 MacBook Pro and 2 different pc's trying to build with rider on Mac and visual studio on pc
thanks in advance

Hi David,
Thanks for providing details for the issue!
Yes, with each new major version (x.o.o) there are a large amount of breaking changes from the previous version. With each minor version (o.x.o) there may or may not be breaking changes, and with each bug fix version (o.o.x) there are no breaking changes.
To see what changes were made you can view the Releases page. The changes from 3.x.x to 4.x.x can be found here.
You can also view the wiki for guides and documentation for the most recent version of the plugin.
In short, all the properties that define the Calendar's behaviour have moved to the class 'Calendar' in namespace 'XCalendar.Core'. Make an instance of this class in your ViewModel and bind its values to the CalendarView.
The Getting Started page is super useful for identifying how to migrate to the current version. You only need to bind the properties specified in the examples of that page.

thank you, can you please provide a good explanation of how to use the event calendar, the sample app is not working and the documentation is not very helpful in this particular calendar

What happens when you try to run the sample app on your machine? I know some people have had problems because they had installed earlier versions of MAUI.
While you can't run the sample app, you can still view the code for the EventCalendar example here
The Calendar class uses generics to determine what the type of each day should be.
By default this is a CalendarDay but it could be any class that implements the ICalendarDay interface. In the example, there is a class called EventDay which has a list of [Event] which is what is bindes to in the XAML to make the dots for each day.
The example uses the CollectionChanged event of the calendar's SelectedDates collection to update the list of events for each day, but you can also use  Calendar's DateSelectionChanged event to get the previous selected dates.
It also uses the DaysUpdated event to respond to any changes caused by the Calendar, most notably navigation, and again update the days' list of events based in what is selected.

Hi @ddavid-son, are you still experiencing this issue?

Closed due to inactivity.


Fixed depency issue for lingui extract

caused by commit 0baadc8e7330f0aa3b05f24ef7d1254aad7c7bc0

Now that I think about it, maybe this should be dev dependencies


move read_evidence module and Locus class to varlens

varcode is cleaner if the functionality for reading BAM files is in another library, and I think the library I'm developing called varlens is a reasonable place for that (https://github.com/timodonnell/varlens -- soon to be in hammerlab once it's cleaned up a bit). It will also hopefully lead to a less convoluted implementation of read_evidence.
This will also mitigate the absurd situation where varcode uses 1-based inclusive coordinates but varcode.read_evidence uses interbase coordinates.

:+1:

If you end up needing to parse Cufflinks tracking files, you can use https://github.com/hammerlab/topiary/blob/master/topiary/rna/cufflinks.py and if you need to parse GTFs (e.g. to pull out novel gene annotations) there is now https://github.com/hammerlab/gtfparse/tree/master/gtfparse


leaderboard: Setup file

In this pull request, I added the following:

Created an npm project with webpack.
Used ES6 modules, with import and export.
Used Gitflow.

Thank you for reviewing my PR👍🏽 and have a good day 😎


[Question]: How to use markNonNullableTypeAsRequired

What are you wanting to achieve?
I am trying to mark non nullable properties as marked
What code or approach do you have so far?
builder.Services.AddSwaggerGen(o =>
{
...
o.NonNullableReferenceTypesAsRequired();
});
Additional context
It doesn't seem to mark properties as required in the spec

Please provide a minimal reproducible example as a GitHub repository that demonstrates the issue you're experiencing so we can look into this further.


Deprecate navidrome

Official support for GHCR was added and the image is sound.
https://github.com/navidrome/navidrome/pkgs/container/navidrome
Currently waiting on a release or images to be migrated over
https://github.com/navidrome/navidrome/discussions/2257

Done in https://github.com/onedr0p/containers/commit/1783fb24474980ae68040a549cc95d1f5010f816


Skin changer

Anyone have an ideea how i can put only the community skins for every weapon? I mean For example: AK47 -> Only the community skins for AK47. Thank you very much guys.

Now you can search skins for certain weapon.


JWK validation fails when x5ts256 value is missing from original JWK

When building a JWK from NewJWKFromMarshal, validation fails when the unmarshalled key (key from a remote host) does not contain an x5ts246 value and the x5c is present. This appears to be due to building the x5ts256 in the keyMarshal logic, resulting in a mismatch when DeepEqual the structs:
https://github.com/MicahParks/jwkset/blob/b7c3a1fee993c0149ac519fa77197f97370c4a62/marshal.go#L195-L206
This is a behavioral difference between<EMAIL_ADDRESS>and<EMAIL_ADDRESS>I'm curious if this would be expected behavior in the upgrade?

This is due to the updated JWK Set package being used. Are you able to provide the JWK Set you are working with? Ensure there is no private key material in it before passing it along.

Thank you for making this issue.
I think this feature branch commit will likely solve the problem. I'll make a test, then confirm that it matches your original problem. Could get a release out tonight.

I think this program would reproduce the error experienced. The upcoming changes should fix that.
package main

import (
	"encoding/json"
	"log/slog"
	"os"

	"github.com/MicahParks/jwkset"
)

const (
	logErr = "error"
)

func main() {
	l := slog.Default()
	const rawJWKSet = `{"keys":[{"kty":"OKP","alg":"EdDSA","kid":"my-key-id","x5c":["MIIB8TCCAaOgAwIBAgIUa/7hf5yVjhXwYLaT38DE5+y06PkwBQYDK2VwMG4xCzAJBgNVBAYTAlVTMREwDwYDVQQIDAhWaXJnaW5pYTERMA8GA1UEBwwIUmljaG1vbmQxFDASBgNVBAoMC01pY2FoIFBhcmtzMQ0wCwYDVQQLDARTZWxmMRQwEgYDVQQDDAtleGFtcGxlLmNvbTAeFw0yNDAxMDQwMDE2MDVaFw0yNDAyMDMwMDE2MDVaMG4xCzAJBgNVBAYTAlVTMREwDwYDVQQIDAhWaXJnaW5pYTERMA8GA1UEBwwIUmljaG1vbmQxFDASBgNVBAoMC01pY2FoIFBhcmtzMQ0wCwYDVQQLDARTZWxmMRQwEgYDVQQDDAtleGFtcGxlLmNvbTAqMAUGAytlcAMhAKD0un1323TTlTlFUs5VWb+JvlToR5hMAWPfqLi4Wybpo1MwUTAdBgNVHQ4EFgQUOcvkrHIL2s+C+jq+y2V04rn1D3swHwYDVR0jBBgwFoAUOcvkrHIL2s+C+jq+y2V04rn1D3swDwYDVR0TAQH/BAUwAwEB/zAFBgMrZXADQQAHgsrxSTTK/K4hOeEldhsXooONdLR49kM/TtBqJEScxskFo51MEBRzydjwkiI7isPRgyy838Mvv9VS+nij1EAI"],"x5t":"RTwmBuuqX7XB6UlVXVck9scuJSM","x5t#S256":"bRkXmcs_Kvo6nQrYE7ZWpvDtyoI5Hj_82ASr4eauTV8","crv":"Ed25519","x":"oPS6fXfbdNOVOUVSzlVZv4m-VOhHmEwBY9-ouLhbJuk"}]}`

	var marshal jwkset.JWKSMarshal
	err := json.Unmarshal([]byte(rawJWKSet), &marshal)
	if err != nil {
		l.Error("Failed to unmarshal JWK set.",
			logErr, err,
		)
		os.Exit(1)
	}

	marshal.Keys[0].X5TS256 = ""

	jwk, err := jwkset.NewJWKFromMarshal(marshal.Keys[0], jwkset.JWKMarshalOptions{}, jwkset.JWKValidateOptions{})
	if err != nil {
		l.Error("Failed to create JWK.",
			logErr, err,
		)
		os.Exit(1)
	}

	println(jwk.Marshal().KID)
}

I've fixed the identified bug in v0.5.5. Please let me know if I identified the bug you were expecting @joshkaplinsky and if the fix is to your expectations.
Thank you again for reporting this issue :tada:

Thanks for the fast turnaround! Yes, this addresses my issue. Much appreciated!


Update s3, sdk-core, sqs to 2.20.12

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

from 2.17.295 to 2.20.12.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #575.


fix: update the repository path in the package links

Type of change

[ ] New sample
[ ] New feature
[ ] Bug fix
[x] Documentation

Summary
This PR updates the repository path for certain links in the package.json
Requirements

[x] I’ve checked my submission against the Samples Checklist to ensure it complies with all standards
[x] I have ensured the changes I am contributing align with existing patterns and have tested and linted my code
[x] I've read and agree to the Code of Conduct

@hello-ashleyintech appreciate all of the reviews! 🚀


Disallow defining non-unique index on key properties

With #700, every key will have explicit index object defined over same set of properties. Since keys are unique, setting unique=false on associated index should be blocked or setting uniqueness of index to false should remove conflicting keys.

This goes away with the design @bricelam sent out yesterday