Unable to run the example code from musicgen fine tune in Colab

Hi, I am very new to deep learning and want to run the example code first. After running this command:
!python3 -m pip install -U git+https://github.com/facebookresearch/audiocraft#egg=audiocraft
I then run the dora run command. However, I encountered the following error:

What did I do wrong? Also, what should I do to apply LoRa to fine tune musicgen with my own dataset?

After I run %cd /content/src/audiocraft/ the fatal error disappeared, but another long error message came up:
WARNING[XFORMERS]: xFormers can't load C++/CUDA extensions. xFormers was built for:
PyTorch 2.1.0+cu121 with CUDA 1201 (you have 2.1.0+cu118)
Python  3.10.13 (you have 3.10.12)
Please reinstall xformers (see https://github.com/facebookresearch/xformers#installing-xformers)
Memory-efficient attention, SwiGLU, sparse and more won't be available.
Set XFORMERS_MORE_DETAILS=1 for more details
2023-10-31 04:46:00.182805: E tensorflow/compiler/xla/stream_executor/cuda/cuda_dnn.cc:9342] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2023-10-31 04:46:00.182875: E tensorflow/compiler/xla/stream_executor/cuda/cuda_fft.cc:609] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2023-10-31 04:46:00.182924: E tensorflow/compiler/xla/stream_executor/cuda/cuda_blas.cc:1518] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2023-10-31 04:46:00.192581: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-10-31 04:46:01.938557: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
Traceback (most recent call last):
File "/usr/local/bin/dora", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.10/dist-packages/dora/main.py", line 158, in main
main = get_main(args.main_module, args.package)
File "/usr/local/lib/python3.10/dist-packages/dora/_utils.py", line 48, in get_main
module = import_or_fatal(module_name)
File "/usr/local/lib/python3.10/dist-packages/dora/utils.py", line 77, in import_or_fatal
return importlib.import_module(module_name)
File "/usr/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/content/src/audiocraft/audiocraft/train.py", line 131, in
def main(cfg):
File "/usr/local/lib/python3.10/dist-packages/dora/hydra.py", line 308, in _decorator
return HydraMain(main, config_name=config_name, config_path=config_path,
File "/usr/local/lib/python3.10/dist-packages/dora/hydra.py", line 163, in init
dora = self._get_dora()
File "/usr/local/lib/python3.10/dist-packages/dora/hydra.py", line 173, in _get_dora
update_from_hydra(dora, self._base_cfg.dora)
File "/usr/local/lib/python3.10/dist-packages/dora/conf.py", line 35, in update_from_hydra
dct = OmegaConf.to_container(cfg, resolve=True)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/omegaconf.py", line 573, in to_container
return BaseContainer._to_content(
File "/usr/local/lib/python3.10/dist-packages/omegaconf/basecontainer.py", line 292, in _to_content
value = get_node_value(key)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/basecontainer.py", line 244, in get_node_value
conf._format_and_raise(key=key, value=None, cause=e)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/base.py", line 231, in _format_and_raise
format_and_raise(
File "/usr/local/lib/python3.10/dist-packages/omegaconf/_utils.py", line 899, in format_and_raise
_raise(ex, cause)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/_utils.py", line 797, in _raise
raise ex.with_traceback(sys.exc_info()[2])  # set env var OC_CAUSE=1 for full trace
File "/usr/local/lib/python3.10/dist-packages/omegaconf/basecontainer.py", line 242, in get_node_value
node = node._dereference_node()
File "/usr/local/lib/python3.10/dist-packages/omegaconf/base.py", line 246, in _dereference_node
node = self._dereference_node_impl(throw_on_resolution_failure=True)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/base.py", line 277, in _dereference_node_impl
return parent._resolve_interpolation_from_parse_tree(
File "/usr/local/lib/python3.10/dist-packages/omegaconf/base.py", line 584, in _resolve_interpolation_from_parse_tree
resolved = self.resolve_parse_tree(
File "/usr/local/lib/python3.10/dist-packages/omegaconf/base.py", line 769, in resolve_parse_tree
raise InterpolationResolutionError(
File "/usr/local/lib/python3.10/dist-packages/omegaconf/base.py", line 764, in resolve_parse_tree
return visitor.visit(parse_tree)
File "/usr/local/lib/python3.10/dist-packages/antlr4/tree/Tree.py", line 34, in visit
return tree.accept(self)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/grammar/gen/OmegaConfGrammarParser.py", line 206, in accept
return visitor.visitConfigValue(self)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/grammar_visitor.py", line 101, in visitConfigValue
return self.visit(ctx.getChild(0))
File "/usr/local/lib/python3.10/dist-packages/antlr4/tree/Tree.py", line 34, in visit
return tree.accept(self)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/grammar/gen/OmegaConfGrammarParser.py", line 342, in accept
return visitor.visitText(self)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/grammar_visitor.py", line 301, in visitText
return self._unescape(list(ctx.getChildren()))
File "/usr/local/lib/python3.10/dist-packages/omegaconf/grammar_visitor.py", line 389, in _unescape
text = str(self.visitInterpolation(node))
File "/usr/local/lib/python3.10/dist-packages/omegaconf/grammar_visitor.py", line 125, in visitInterpolation
return self.visit(ctx.getChild(0))
File "/usr/local/lib/python3.10/dist-packages/antlr4/tree/Tree.py", line 34, in visit
return tree.accept(self)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/grammar/gen/OmegaConfGrammarParser.py", line 1041, in accept
return visitor.visitInterpolationResolver(self)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/grammar_visitor.py", line 179, in visitInterpolationResolver
return self.resolver_interpolation_callback(
File "/usr/local/lib/python3.10/dist-packages/omegaconf/base.py", line 750, in resolver_interpolation_callback
return self._evaluate_custom_resolver(
File "/usr/local/lib/python3.10/dist-packages/omegaconf/base.py", line 694, in _evaluate_custom_resolver
return resolver(
File "/usr/local/lib/python3.10/dist-packages/omegaconf/omegaconf.py", line 445, in resolver_wrapper
ret = resolver(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/omegaconf/resolvers/oc/init.py", line 38, in env
raise KeyError(f"Environment variable '{key}' not found")
omegaconf.errors.InterpolationResolutionError: KeyError raised while resolving interpolation: "Environment variable 'USER' not found"
full_key: dora.dir
object_type=dict

I got exactly the same error. Did you solve it?

I solved it by setting a USER environment variable before the dora command like so:
USER=root dora run <...>


Support firmware UUID generation

Problem:
The version number field is not trusted to unambiguously represent the firmware that's running on a device. The vcs_identifier can be used, but isn't guaranteed to be populated. The solution of running a SHA-256 over the .fw file after it has been generated is not desirable since things like signing .fw files would change the computed hash but not alter the contents.
Proposed solution:
Add a virtual meta-uuid field that can be deterministically calculated based on the contents of the .fw file. This could be based on the meta.conf file since that file contains hashes of all of the constituent files. If meta-uuid is calculated rather than stored, it will work on .fw files created with older versions of fwup.

This is partially supported by v1.2.0. You can see the UUID by dumping the .fw file's metadata using fwup -m. Storage of the firmware UUID on the target can't be automated using only fwup and additions to the fwup.conf, though.


⚠ Samsung has degraded performance

In f564572, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2108 ms

Resolved: Samsung performance has improved in 349376c.


The Cancel step is now optimised in one job

The cancel steps were tried in separate jobs but it causes
an unnecessary increase in the number of jobs blocking the queue
even if we limited parallelism. This PR combines all the cancel
actions into a single job with multiple steps.
While this is a bit more copy&pasting and less DRY it is also
far more optimised and "aggressive" - i.e. once any cancel
job starts to be running it will immediately cancel all duplicates
for all workflows.

Example here: https://github.com/potiuk/skywalking/runs/1346617869?check_suite_focus=true

It takes 15 s to run all the cancel steps in a single job.


QG X checks (Release 24.03)

QG checks
Please keep this issue open until QG is concluded and will be managed by the Issue Creator!
We will inform you about finding and proposals in separated issues, this issue here is for the Overview of the Checks!
Please keep this issue open until QG is concluded!
Product Owner: @jjeroch
Dev SPOC: @evegufy
Portal:

Portal Chart Version: portal-1.8.0(-RC8)

QG Checklist Leading Repo

Portal Frontend: v1.8.0(-RC6)

QG Checklist Frontend

Portal Backend: v1.8.0(-RC7)

QG Checklist Backend

Portal Assets: v1.8.0(-RC5)

QG Checklist Portal Assets

Portal Frontend Registration: v1.6.0(-RC5)

QG Checklist Portal Frontend Registration

IAM:

CentralIdP Chart Version: 2.1.0(-RC1)
SharedIdP Chart Version: 2.1.0(-RC1)

QG-Checklist

Release Management Reference Issue: https://github.com/eclipse-tractusx/sig-release/issues/499
Check of Tractus-X Release Guidelines

Currently implemented automatic checks can be found under your product on our Release Guidelines Checks Board
This QG Check is depending on the mandatory information from our current Release Guidelines

TRG 1 Documentation

[x] TRG 1.01 appropriate README.md
[x] TRG 1.02 appropriate install instructions either INSTALL.md or in README.md
[x] TRG 1.03 appropriate CHANGELOG.md
[x] TRG 1.04 editable static files

TRG 2 Git

[x] TRG 2.01 default branch is named main
[x] TRG 2.03 repository structure
https://github.com/eclipse-tractusx/portal-assets/issues/210 --> implemented since 23.12
https://github.com/eclipse-tractusx/portal-cd/issues/131 --> implemented since 23.12
https://github.com/eclipse-tractusx/portal/issues/205
[x] #208
[x] TRG 2.05 .tractusx metafile in a proper format

TRG 3 Kubernetes

[x] TRG 3.02 persistent volume and persistent volume claim is used when needed

TRG 4 Container

[x] TRG 4.01 semantic versioning and tagging
--> implemented since 23.12
https://github.com/eclipse-tractusx/portal-assets/issues/206
https://github.com/eclipse-tractusx/portal-frontend/issues/381
https://github.com/eclipse-tractusx/portal-frontend-registration/issues/83
https://github.com/eclipse-tractusx/portal-backend/issues/358
https://github.com/eclipse-tractusx/portal-iam/issues/36
[x] TRG 4.02 base image is agreed
[x] TRG 4.03 image has USER command and Non Root Container
[x] TRG 4.05 released image must be placed in DockerHub, remove GHCR references
[x] TRG 4.06 separate notice file for DockerHub has all necessary information

TRG 5 Helm

[x] TRG 5.01 Helm chart requirements
[x] TRG 5.02 Helm chart location in /charts directory and correct structure
[x] TRG 5.03 proper version strategy
[ ] #207
[x] TRG 5.06 Application must be configurable through the Helm chart
[x] TRG 5.07 Dependencies are present and properly configured in the Chart.yaml
[x] TRG 5.08 Product has a single deployable helm chart that contains all components
[x] TRG 5.09 Helm Test running properly
[x] TRG 5.10 Products need to support 3 versions at a time
[x] TRG 5.11 Upgradeability

TRG 6 Released Helm Chart

[x] TRG 6.01 Released Helm Chart

TRG 7 Open Source Governance

[x] TRG 7.01 Legal Documentation
[x] #206
[x] TRG 7.03 IP checks for project content
[x] TRG 7.04 IP checks for 3rd party content
[x] TRG 7.05 Legal information for distributions
[x] TRG 7.06 Legal information for end user content
[x] TRG 7.07 Legal notice for documentation
[x] TRG 7.08 Legal notice for KIT documentation

Hints
Information Sharing

Hi @evegufy, TRG Check for leading repo done.
Please recheck the findings and we will update the issue.
Thanks in advance.

Closing the QG issue, with the default CPU and memory requests for the Chart missing.

Clarification: CPU and memory requests are set. CPU and memory requests limits are configured but commented out in the values.yaml but can be set at all times when using the chart. Setting the limits in the values.yaml will be addressed in the next release.


Available fonts

Fantastic library!
I wanted to use on a project tall but condensed font (http://www.1001fonts.com/attentica-4f-font.html#license) but is not available on your web converter.
I've manage to convert it with fontconverter from Adafruit_GFX, but they have a different format than your fonts. Is there a way to convert from one format to the other?

I just added it to the converter. Please check and close the issue if you agree it has been resolved:-)

You are the man!
Works great thanks!
On a display here:[http://imgur.com/a/vtXzz]


[reconfiguration] supporting removing validators

Added removals field to the LibraSystem.ValidatorSet resource
Added LibraSystem.remove_validator(addr), which adds addr to removals. This procedure can only be called by the Association, and only on an existing validator that has not already been added to removals.
LibraSystem.reconfigure() now removes each address in removals from the validator set
New E2E tests for happy path, authentication, error cases

Motivation
Final kind of reconfiguration that  we need to support!
Have you read the Contributing Guidelines on pull requests?
Yes!
Test Plan
New E2E tests.
Related PRs
Stacked on https://github.com/libra/libra/pull/1867 and https://github.com/libra/libra/pull/1832

:umbrella: The latest upstream changes (presumably 119ed015f0be04971d3e36caeb65a4c7ea057f6d) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r+

:pushpin: Commit 121de5f has been approved by sblackshear

:lock: Merge conflict

:umbrella: The latest upstream changes (presumably 7288d8bf47f55d7a4fa0c90cb7ae0fc026cc7558) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r+

:pushpin: Commit fc31822 has been approved by sblackshear

exciting milestone :)

:umbrella: The latest upstream changes (presumably a5f74d6721326455a400e22f32d3cd343e172677) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r+

:pushpin: Commit 819ef91 has been approved by sblackshear

:hourglass: Testing commit 819ef913bb38f2088d4ab7f350500cc64bb1706d with merge 18fd0506b9c9e85947b6cc882055e4bf3ac909bb...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: sblackshear
Pushing 18fd0506b9c9e85947b6cc882055e4bf3ac909bb to master...


Refactor pass - soundwave audio + CLI component

Tasklist

[x] Move CLI wrapper and new cli base component into separate module
[x] Add a PCM -> Wav -> Soundwave conversion inside piper component to de-couple from socket.io
[x] Compiles
[x] Runs with no regressions

refactor complete in v0.4


auro-menu: multiselect

Is your feature request related to a problem? Please describe.
As a business I want to give users the ability to select multiple options from menu items
So that users can select multiple options in the UI.
Blueprint:
https://www.figma.com/file/yMshXAiKZrkLDdiX8N4GKQ/Multi-Select-Combo-Box?type=design&node-id=114-3745&mode=design&t=R007FIBn8d6HGOOY-11
Describe the solution you'd like
A menu with checkboxes so users can select as many as they want.
Describe alternatives you've considered
No response
Additional context
No response
Exit criteria

Auro-menu feature matches the blueprint.
Create refinement meeting team on next step to align on implementation of next step.
As an outcome of the refiement a new issue is created to implement this as either <auro-multiselect> or <auro-combobox multiselect>
When Menu is Multiselect, value is an Array containing all selected menu options.

This work has been moved to auro-formkit and will be completed in https://github.com/AlaskaAirlines/auro-formkit/issues/123


xmlsec: 1.2.25 -> 1.2.26

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/xmlsec/versions.
These checks were done:

built on NixOS
/nix/store/y5z1vxy9v75bpsjl4z3xg1l4m0d8iqg1-xmlsec-1.2.26/bin/.xmlsec1-wrapped passed the binary check.
/nix/store/y5z1vxy9v75bpsjl4z3xg1l4m0d8iqg1-xmlsec-1.2.26/bin/xmlsec1 passed the binary check.
2 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 1.2.26 with grep in /nix/store/y5z1vxy9v75bpsjl4z3xg1l4m0d8iqg1-xmlsec-1.2.26
directory tree listing: https://gist.github.com/35b63e4ccf9a1df1b167177e91716a4e
du listing: https://gist.github.com/d45eba60006ba229e2682ff2db682d96

meta.description for xmlsec is: '"XML Security Library in C based on libxml2"'.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 0800c9e60b86032ed7cd898bb81f3e824331e9c8 && nix-shell --pure -I nixpkgs=. -p xmlsec

Success on x86_64-linux (full log)
Attempted: xmlsec
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/y5z1vxy9v75bpsjl4z3xg1l4m0d8iqg1-xmlsec-1.2.26/lib  /nix/store/y5z1vxy9v75bpsjl4z3xg1l4m0d8iqg1-xmlsec-1.2.26/bin
patching script interpreter paths in /nix/store/y5z1vxy9v75bpsjl4z3xg1l4m0d8iqg1-xmlsec-1.2.26
checking for references to /build in /nix/store/y5z1vxy9v75bpsjl4z3xg1l4m0d8iqg1-xmlsec-1.2.26...
shrinking RPATHs of ELF executables and libraries in /nix/store/pqmgk8hyiysrdr02di6xn0kdd661dram-xmlsec-1.2.26-dev
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/pqmgk8hyiysrdr02di6xn0kdd661dram-xmlsec-1.2.26-dev/lib  /nix/store/pqmgk8hyiysrdr02di6xn0kdd661dram-xmlsec-1.2.26-dev/bin
patching script interpreter paths in /nix/store/pqmgk8hyiysrdr02di6xn0kdd661dram-xmlsec-1.2.26-dev
/nix/store/pqmgk8hyiysrdr02di6xn0kdd661dram-xmlsec-1.2.26-dev/bin/xmlsec1-config: interpreter directive changed from " /bin/sh" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/pqmgk8hyiysrdr02di6xn0kdd661dram-xmlsec-1.2.26-dev...
/nix/store/y5z1vxy9v75bpsjl4z3xg1l4m0d8iqg1-xmlsec-1.2.26

Success on aarch64-linux (full log)
Attempted: xmlsec
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/p5d2k8sq5i8v639jwvg5q38hqxy5v114-xmlsec-1.2.26/lib  /nix/store/p5d2k8sq5i8v639jwvg5q38hqxy5v114-xmlsec-1.2.26/bin
patching script interpreter paths in /nix/store/p5d2k8sq5i8v639jwvg5q38hqxy5v114-xmlsec-1.2.26
checking for references to /build in /nix/store/p5d2k8sq5i8v639jwvg5q38hqxy5v114-xmlsec-1.2.26...
shrinking RPATHs of ELF executables and libraries in /nix/store/q107h9qg5ykia49na67bjkqjkwqzpcdy-xmlsec-1.2.26-dev
strip is /nix/store/qg2agrqkf240s656d207zqhipl0bc2id-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/q107h9qg5ykia49na67bjkqjkwqzpcdy-xmlsec-1.2.26-dev/lib  /nix/store/q107h9qg5ykia49na67bjkqjkwqzpcdy-xmlsec-1.2.26-dev/bin
patching script interpreter paths in /nix/store/q107h9qg5ykia49na67bjkqjkwqzpcdy-xmlsec-1.2.26-dev
/nix/store/q107h9qg5ykia49na67bjkqjkwqzpcdy-xmlsec-1.2.26-dev/bin/xmlsec1-config: interpreter directive changed from " /bin/sh" to "/nix/store/9rv2bzx7jz6wjbaxij5qq580qvzksj4i-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/q107h9qg5ykia49na67bjkqjkwqzpcdy-xmlsec-1.2.26-dev...
/nix/store/p5d2k8sq5i8v639jwvg5q38hqxy5v114-xmlsec-1.2.26

Success on x86_64-darwin (full log)
Attempted: xmlsec
Partial log (click to expand)
Patching '/nix/store/93xrgiy622xk24jsvxka9n42ay1mrv96-xmlsec-1.2.26-dev/lib/pkgconfig/xmlsec1.pc' includedir to output /nix/store/93xrgiy622xk24jsvxka9n42ay1mrv96-xmlsec-1.2.26-dev
gzipping man pages under /nix/store/8bffn4axrs79b4sbghknj3cq0khh05gh-xmlsec-1.2.26/share/man/
strip is /nix/store/yyak5sjv68n9vdgnkd2cb5djk1l9sqj5-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/8bffn4axrs79b4sbghknj3cq0khh05gh-xmlsec-1.2.26/lib  /nix/store/8bffn4axrs79b4sbghknj3cq0khh05gh-xmlsec-1.2.26/bin
patching script interpreter paths in /nix/store/8bffn4axrs79b4sbghknj3cq0khh05gh-xmlsec-1.2.26
strip is /nix/store/yyak5sjv68n9vdgnkd2cb5djk1l9sqj5-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/93xrgiy622xk24jsvxka9n42ay1mrv96-xmlsec-1.2.26-dev/lib  /nix/store/93xrgiy622xk24jsvxka9n42ay1mrv96-xmlsec-1.2.26-dev/bin
patching script interpreter paths in /nix/store/93xrgiy622xk24jsvxka9n42ay1mrv96-xmlsec-1.2.26-dev
/nix/store/93xrgiy622xk24jsvxka9n42ay1mrv96-xmlsec-1.2.26-dev/bin/xmlsec1-config: interpreter directive changed from " /bin/sh" to "/nix/store/9gghkkqhn6v7dvpf2319qvrxkkw03vwr-bash-4.4-p19/bin/sh"
/nix/store/8bffn4axrs79b4sbghknj3cq0khh05gh-xmlsec-1.2.26

Reverted in https://github.com/NixOS/nixpkgs/commit/31b4bfe649ce92b1a74dbc464f16c542c32e9043 because this update broke libreoffice: https://github.com/NixOS/nixpkgs/issues/37619#issuecomment-397309605.


Fixed NPE

Fixed two issues described below:

Described here
NPE while scheduling job with time that is never going to come.

Due to below error I couldn't run the tests, kindly consider this recommendation
Compilation failure
/Users/mehul/projects/redisson/redisson/src/test/java/org/redisson/RedissonLiveObjectServiceTest.java:[57,5] error: cannot find symbol
  symbol:   class REntity
  location: class RedissonLiveObjectServiceTest

    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1161)
    at org.apache.maven.plugin.compiler.TestCompilerMojo.execute (TestCompilerMojo.java:176)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)

Why would you even schedule a job thats never going to be executed?

@Flyffies
Whether anyone does that or not it should be properly handled in library. Anyway the other fix os more sensible.

@Flyffies
Also look into this for more clarity.

@arpit728 Yea, I read that, thanks.
And regarding that, why don't just calculate the time difference between now and the desired execution time when scheduling the job? That way you wouldn't need to pass the Cron Expression (or use it to calculate the time difference).
No offense, but I feel like you missuse the system a bit.

@Flyffies @mrniko
Thanks for the feedback, but the only point what I am trying to make is that, if library claims to support the cron expression then it should support cron expression in general (without giving any error for one time cron as well). May be I am wrong, but I feel the issue that I figured out is clearly a bug.

And regarding that, why don't just calculate the time difference between now and the desired execution time when scheduling the job? That way you wouldn't need to pass the Cron Expression (or use it to calculate the time difference).

Can you please elaborate this hack in more details, I didn't get you?

No offense, but I feel like you missuse the system a bit.

I appreciate your feedback, but how did I misuse it ? The things which I tried seemed quite obvious when we talk about scheduler. And redisson being a great library, I strongly felt should be able to support that.

Of course, that NPE shouldn't be thrown, I agree with you there.
Cron Expressions are generally used to schedule a repeating task, not a one time job.

Can you please elaborate this hack in more details, I didn't get you?

I proposed, for a one time running job to just calculate the delay and then schedule it with the appropiate method. Here:
`public static void main(String[] args) {
RedissonClient client = Redisson.create();
    RScheduledExecutorService service = client.getExecutorService("serviceId");

    // Calculate delay
    LocalDateTime dateTime = LocalDateTime.of(2018, Month.JUNE, 15, 10, 23, 25);
    Duration delay = Duration.between(LocalDateTime.now(), dateTime);

    // Schedule
    Runnable someTask = () -> System.out.println("Some Task");
    service.schedule(someTask, delay.getSeconds(), TimeUnit.SECONDS);

}`
That way it will be executed at a specific time and date, without trying to reschedule it afterwards.

@Flyffies

I proposed, for a one time running job to just calculate the delay and then schedule it with the appropiate method. Here:

Thank you so much for this.
I am completely fine in using this approach for scheduling one time job, I am completely okay with this.

Cron Expressions are generally used to schedule a repeating task, not a one time job.

I totally agree with this.
But I feel, since library claims to support the cron expression compatible with quartz it should support it without giving any trouble to the developer using this library.
and also I strongly feel, library should not behave in the way it is behaving now when provided with one time cron expression. Because anyone using the library wouldn't want to dwell into the implementation details and figure out that one time crons will not be supported.
And also if someone uses my service to schedule the job just provides the cron expression and I obviously would now want to refrain him from providing any specific case of cron( one time cron expression in this case). and I feel that case should also be handled by the library gracefully.
Thank you so much for your feedback, you are doing great work.

Happy I could help you.
I haven't worked with the quartz library, so I don't know how its handled there, but yea, this should still be catched.

@mrniko @jackygurui
To rephrase the issue more generically,
The last execution of any Cron Schedule will fail.
I think one point that we are missing out here, is that, a repeatable Cron schedule can repeat for finite number of times. Not Every schedule is infinitely repeated (For Eg. Run this job every monday at 2 PM in April 2018, its very difficult to schedule this as a NON Cron schedule)
Taking few specific use cases of above issue and explaining further.

A Cron that represents no execution in future, (As discussed already, this can be handled by application before submitting the job)

A Cron that represents a single execution in future (As discussed this can be handled in library as well)

A Cron that represent 1'st day of every month in 2018, in this case 12th execution will always fail.

As fixing this bugs will greatly increase user friendliness of the library so, kindly consider this fixes.

Thank you for suggested code, but I think right solution is validate cron exception during task submission. I'm closing this task.

@mrniko
Kindly review this two points in above comment more carefully, the real issue is with the finite cron expression, in this case last job would be always missed.

A Cron that represents a single execution in future (As discussed this can be handled in library as well)

A Cron that represent 1'st day of every month in 2018, in this case 12th execution will always fail.

Kindly go through last comment on this issue, it will make the things more clear.
May be fix I have suggested is inappropriate, but we should definitely fix this in some other way.


Add view that list user's campaigns

I noticed we don't have a page listing the campaigns a user has created.

This will be the new default when logging in in the new design. I'll be closing this because i'll be making a more detailed issues for the upcoming sprint


Project Status

Hi,
Is this project still active?

No, unfortunately not. I will set its status to archived.


[BUG]: The load list commands increase memory footprint indefinetely.

The load list commands:
memtier_benchmark-1Mkeys-load-list-with-1KiB-values
memtier_benchmark-1Mkeys-load-list-with-100B-values
memtier_benchmark-1Mkeys-load-list-with-10B-values
keep growing in memory capacity. If multiple memtier runs are specified, this would result in consuming more memory than specified.

Ideally we should move away from memtier and use a specific tool or ingesting this type of datatypes that keep growing indefinitely ( like we have in https://github.com/redis-performance/redis-zbench-go for sorted sets )


Correct AsciiDoc.ImageContainsAltText criteria

If there are multiple entries in the raw array, they are concatenated into one large regular expression.  In this case, this meant that we were searching for the regular expression image::.*\[\]image:.*\[\], which doesn't find images without alt text.
In this commit, we use a single regular expression that will match both cases: image with one colon, and image with two colons.
closes #829

/lgtm

Thank you for the PR @sandbergja :partying_face:


Primary lab

Add tiny plastic primary lab. It has no visible Enchantments. If they fix that, we'll have to update.
Add support for Choice Adventure 1461 in the Site Alpha Primary Lab.
Note that option #5 is "Grab the Cheer Core". If I recall, you get that once - and it is your only choice.
Therefore, if you are automating and that choice comes up and that option is present, we select it, regardless of how you have the choice configured.
Note also that this choice adventure does not have a blue "Encounter" when you find it.
I bug reported it to KoL. Surely they'd prefer to have something funny, rather than nothing.
Also added two properties:
primaryLabGooIntensity (default 10)
primaryLabCheerCoreGrabbed (default false)

Thanks V. We could use deriving the current intensity from the construct names too.

Thanks V. We could use deriving the current intensity from the construct names too.

Well, if it says 10-ton, that means intensity is no greater than 10, but it could be less.
Do I need to do this before you'll approve? :)

Also added the name change: inert grey goo ring -> ert grey goo ring.
Without this, cannot do mall search for it.

Thanks V. We could use deriving the current intensity from the construct names too.

Well, if it says 10-ton, that means intensity is no greater than 10, but it could be less. Do I need to do this before you'll approve? :)

Of course not!


type name breaking

Using "Intelligent Cooperation Tech" as one of the types broke - too long or too many spaces? not sure, switched to IC Tech on that repo for now

Looks like this also happens with axis names


Fix MultiHeadAttention docs

Docs on the site look weird due to formatting issues: https://www.tensorflow.org/addons/api_docs/python/tfa/layers/MultiHeadAttention
This PR tries to fix the formatting and also improves parts of the text a bit.

I'll go back to the listing style if it works, thought it might screw the format.

I think this looks better, is there a way to check how the page will look now?

I think this looks better, is there a way to check how the page will look now?

Hi, maybe you can follow the instructions here.
https://github.com/tensorflow/addons/tree/master/docs


Default Subnets not creating

Having an issue creating the default subnets as introduced in 35603a76287d20b5626323edf5a25c8353e7d4f7
Strangely, it will create some of the subnets but not all. The error reported is
Error: Default subnet not found

  on main.tf line 47, in resource "aws_default_subnet" "default":
  47: resource "aws_default_subnet" "default" {

my provider is set to
provider "aws" {
  region = "ap-northeast-2"
}

for local testing.
I've tried terraform 13 and terraform 14 with no luck.
If I figure out what's causing the issue, i'll submit the PR.

FWIW, the current created state is
❯ terraform-14 state list
data.aws_availability_zones.all
aws_default_network_acl.default[0]
aws_default_route_table.default[0]
aws_default_security_group.default[0]
aws_default_subnet.default[0]
aws_default_subnet.default[1]
aws_default_subnet.default[2]
aws_default_vpc.default[0]

I've disabled flow log creation to narrow the scope of troubleshooting

Failing pattern seems to be

Default Subnets created (by terraform?)
Subnets deleted (by anything not terraform)
Terraform can't put them back (even when state does not exist)
Put them back via AWS CLI
Terraform can regain control

Unsure what caused the deletion of these default subnets in the first place. But at this point I'll attribute this to something in our account setup, not this module. I'll close this issue.

@dad264 Sorry for being late here. Yes, currently this module throws an error when a default subnet does not exists in any availability zones. The workaround would be to create missing default subnets.
Please check #198 for further information!


Autolayout

Autolayout seems to break the slider 😞. I have tried setting height constraints, but the outcome is the same. I think this is due to how the control draws RangeSliderTrackLayer.

I have this too.... autolayout completely hides the slider...


Supporting filtering criteria in apt-sm-plugin list output

Is your feature improvement request related to a problem? Please describe.

Depending on your setup the tedge-apt-plugin can return a large list of packages, sometimes > 256 packages. The large list can effect other related Cumulocity IoT processes on the server side (e.g. Cumuloity Datahub offboarding of the data to a data lake).
A large number of packages (e.g > 50) generally has very limited value for users as the list is too big to get a good overview over.  Instead people are more interested in selected packages related to their use case (e.g. users care more about their user applications rather than which libc package is installed).
Describe the solution you'd like

The tedge-apt-plugin should support the following filtering criteria:

name (regex pattern)
maintainer (regex pattern)

In addition, the max number of packages should be configured to prevent large number of packages from being sent to the cloud

Add configuration to set the max number of software packages reported by each software management (sm) plugin (configurable via tedge.toml). The limit should be applied to each sm-plugin so that one rogue plugin producing 1000's of entries does not bump the output of other sm-plugins.

Describe alternatives you've considered

Additional context

Maybe switching from using the apt list --installed command, we could use the dpkg-query command. For example you can list the package, version and maintainer using:
dpkg-query -f '${Package}\t${Version}\t${Maintainer}\n' -W

Though more investigation is needed to see if it returns the appropriate data.

We can replace apt list --installed with slight modification (dpkg-query does not support the --installed flag, but we can check package status and then grep all that are installed but print them without status information). We will also need to use grep when filtering by maintainers as dpkg-query filters only by names. However, I have a few questions:

Should we apply a maximum number of displayed packages when using a filter?
Should we set a maximum number of displayed packages by default? If so, what should be a default number?
How do we want to provide filtering options? Initially, I wanted to add two flags: --name and --maintainer, but maybe you have a better suggestion.

Should we apply a maximum number of displayed packages when using a filter?

The maximum number of items should be applied by the tedge component that runs the plugin filters (not the plugin itself), as this will be common logic which can be applied across different software management plugins.

Should we set a maximum number of displayed packages by default? If so, what should be a default number?

Use a default of 1000 items. This limit should always be applied to the software management list.

How do we want to provide filtering options? Initially, I wanted to add two flags: --name and --maintainer, but maybe you have a better suggestion.

The filter options should be provided by the plugin configuration and not as command line parameters as there is no common command line interface which can be provided.
Instead specific plugins should have their own configuration which controls how they work. e.g. the tedge-apt-plugin could read in configuration which reads the name and maintainer settings.

A new setting has been added to tedge config to limit the number of software packages forwarded to the cloud.

software.plugin.max_packages gives the maximum number of packages to be listed per software type.
The default is 1000 packages
0 means no limit.
This affects only what is transmitted to the cloud. tedge-apt-plugin list lists all the installed packages.

Two settings have been specifically added to tedge-apt-plugin.

tedge-apt-plugin list --name $PATTERN lists the packages which name matches the regular expression $PATTERN.
tedge-apt-plugin list --maintainer $PATTERN lists the packages which maintainer matches the regular expression $PATTERN.
If both --name and --maintainer patterns are provided, tedge-apt-plugin lists packages which either the name or the maintainer matches.
These two settings  can stored in /etc/tedge/tedge_config.toml in an apt table.
If stored in /etc/tedge/tedge_config.toml, then the apt.name and apt.maintainer settings are used to filter packages listed to the cloud.
No support is provided by tedge config so store apt.name and apt.maintainer.

A new setting has been added to tedge config to limit the number of software packages forwarded to the cloud.

software.plugin.max_packages gives the maximum number of packages to be listed per software type.
The default is 1000 packages
0 means no limit.
This affects only what is transmitted to the cloud. tedge-apt-plugin list lists all the installed packages.

Two settings have been specifically added to tedge-apt-plugin.

tedge-apt-plugin list --name $PATTERN lists the packages which name matches the regular expression $PATTERN.
tedge-apt-plugin list --maintainer $PATTERN lists the packages which maintainer matches the regular expression $PATTERN.
If both --name and --maintainer patterns are provided, tedge-apt-plugin lists packages which either the name or the maintainer matches.
These two settings  can stored in /etc/tedge/tedge_config.toml in an apt table.
If stored in /etc/tedge/tedge_config.toml, then the apt.name and apt.maintainer settings are used to filter packages listed to the cloud.
No support is provided by tedge config so store apt.name and apt.maintainer.

When tedge-apt-plugin is installed it will be installed as apt inside /etc/tedge/sm-plugins. So, for testing purposes use /etc/tedge/sm-plugins/apt instead of tedge-apt-plugin as the binary name.

FYI: Just an example showing how useful this feature is:
Using the following package name and maintainer filter on a Raspberry Pi 3 returns 41 packages instead of 920 (unfiltered list). This enables me to concentrate on the packages which I am interested in monitoring.
/etc/tedge/sm-plugins/apt list --name '(vim|docker|nano).*' --maintainer '.*(raspberry|thin-edge.io).*'

The above filter will includes any packages matching any of the following:

packages which start with, vim, docker or nano
packages which include either raspberry or thin-edge.io in the maintainer property

QA has thoroughly checked the feature and here are the results:

[x] Test for ticket exists in the test suite.  tests/RobotFramework/tests/tedge/call_tedge_config_list.robot and tests/RobotFramework/tests/tedge/apt_plugin.robot
[x]  Documment corrected: typo on ../../docs/src/tutorials/send-thin-edge-data.md
[x] QA has tested the feature and it meets the required specifications.

QA has thoroughly checked the feature and here are the results:

[x] Test for ticket exists in the test suite.  tests/RobotFramework/tests/tedge/call_tedge_config_list.robot and tests/RobotFramework/tests/tedge/apt_plugin.robot  and tests/RobotFramework/tests/cumulocity/software_management/sm-plugin.robot
[x] QA has tested the feature and it meets the required specifications.
[x] PR created: https://github.com/thin-edge/thin-edge.io/pull/2006 and https://github.com/thin-edge/thin-edge.io/pull/2198


How to open discovery service automatically in every boot

Each time I boot the OS, I need to open MeasurementLink Editor fist and then open my measurement service. Else, it could say no discovery service. But this is not elegantly enough. It makes no sence as you are not planning to edit UI but still have to open Editor..... But after discovery service opened, could close Editor, thus I guess discovery service may could open independently.
Is it way I can open discovery service automatically(like set services startup type as automatic)?
AB#2386429

We are planning to address this in AB#2305696: Launch Discovery Service before registering a Measurement Service when running from a python or LabVIEW development environment.


Mac Plus write error: Not able to receive 512 bytes of data

I have tried a Pi 4/4gb and a 3B+
both Jan release and feb release fullspec
2.4a 68klma
Mac plus 4gb

Describe the issue
I have tried all of the boot images supplied in the repo as well as manually created system (6.0.8, 7.0.1, 7.5.3)
I have tried booting the pi from USB and from SD
I have tried both 32 and 64 bit rpi os
I have tried multiple scsi cables.
Voltage is ok.
I am able to boot the macplus from all/any rascsi system to a functional desktop HOWEVER when i try to perform any operation that requires writing to the scsi disk the mac freezes after ~10 seconds of data transfer.
with the log set to TRACE, the rascsi/macplus hangs reliably on these two lines:
Feb  7 19:45:31 max RASCSI[484]: [2022-02-07 19:45:31.429] [error] virtual void SCSIDEV::Receive() Not able to receive 512 data, only received 2. Going to error
Feb  7 19:45:31 max RASCSI[484]: [2022-02-07 19:45:31.429] [trace] virtual void SCSIDEV::Error(ERROR_CODES::sense_key, ERROR_CODES::asc) Error (to status phase)

the only difference with each hang being that:
only received 2
varies numerically  in each case.
i am able to boot the mac from a system floppy with zero errors but as soon as i write to scsi, i get maybe 10 seconds of transfer before hanging with the same errors
advice, instructions, etc ?
m

@edgeux Does other SCSI storage devices work well with your Plus? Have you tried using contact cleaner on the SCSI port on the computer?

Thanks for the reply, I have performed contact tests with every pin board to board. I have no other scsi devices to test unfortunately.

@edgeux Is your SCSI chain properly terminated? The physical ends of the chain have to be terminated, i.e. if the RaSCSI board is your only device it definitely must be terminated.
Considering that your problem are very obvious, but there are no reports of similar errors by error users (at least not tickets), indicates that your problem is very likely related to your specific hardware setup (including termination).

It is the only scsi device and the jumpers are terminated on the rascsi. I think I will have to get my hands on some other scsi equipment to test further. Is there any other useful information that can be derived from the error itself? It means nothing to me.

@edgeux I'm afraid there is no further information the error message provides. It just indicates a basic SCSI communication/protocol issue.

I'm seeing the exact same error with my Mac Plus. I'm using a Raspberry Pi 3b, RaSCSI board v2.4, 4MB RAM installed on the Mac Plus, and the RaSCSI is the only device connected to the SCSI bus, with termination enabled. The Mac Plus boots fine from floppy, a FloppyEmu (either configured as either a floppy drive or HD20), and from a SCSI Zip drive. The RaSCSI works completely fine on a Mac Classic II.

@uweseimet Yes. I'm seeing the same things in my logs. I'll post my logs as soon as I get a chance if that would help.

@supercompman If your trace logs shows do same you don't have to spend on posting it. I just wanted to ensure from the logs your issue is the same, and not just a similar problem with different logs.

I also stumbled upon this error message (with various counts for the received data), but it is not reproducable.
[2022-02-25 13:12:23.845] [error] void SCSIDEV::ReceiveBytes() Not able to receive 512 data, only received 446. Going to error

After experimenting on and off for a few months, I finally found a solution that worked for myself. I have no idea if it will work for anyone else. Using Silverlining 5.31 for the driver and partitioning worked well. Previously, I had been using the Apple tools and driver. With Silverlining, I have the option of selecting the method used by the driver for reading and writing data. Any of the "Blind" methods would not work at all, while all of the "Handshake" methods worked perfectly. I reviewed my RaSCSI logs and I'm not seeing any errors when using the Silverlining driver.

@supercompman
Thank you!  I started using the Silverlining driver a few weeks ago and so far the SCSI errors and freezes on my mac plus have disappeared.

Same here!
On Sat, Jul 30, 2022 at 1:41 PM jcres69 @.***> wrote:

@supercompman https://github.com/supercompman
Thank you! I started using the Silverlining driver a few weeks ago and so
far the SCSI errors and freezes on my mac plus have disappeared.
—
Reply to this email directly, view it on GitHub
https://github.com/akuker/RASCSI/issues/656#issuecomment-1200263377, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AZ6U46LBAZEEVV6THLAIAFTVWVSM5ANCNFSM5NYOM54Q
.
You are receiving this because you commented.Message ID:
@.***>

I've documented in wiki the fact that only Silverlining drivers are known to work properly with the Plus. https://github.com/akuker/RASCSI/wiki/Drive-Setup#initializing-a-new-disk-on-classic-mac-os
In the long term it'd be great to have a workaround in RaSCSI code, so let's keep this ticket open.

@rdmark It will be very hard to find out what's wrong because these errors are spurious and we do not know how to reproduce them. This might be a timing issue, or even a general (not by board, but by design) hardware issue.

@uweseimet On my Mac Plus, the issue is anything but spurious. If there's any information that I can gather or testing I can do to help understand this issue better, just let me know. I'm not a C/C++ or Python developer, but I am a  software developer by trade and I'm pretty comfortable working with Linux.

@supercompman I'm afraid I cannot provide further support in this case. I think that this particular issue needs to be debugged and resolved by somebody who has a setup where this problem happens frequently. Somebody like you ;-). A try-and-error approach may be needed.
it's interesting that even though the Mac Plus is not the only platform where this issue can be observed, it appears to be the platform affected most, while the effect on other platforms is neglectable. Whatever it is, there must be a reason for this.

@supercompman I think Uwe's point is that the Receive() error is a red herring, and the actual issue lies elsewhere.
@uweseimet Yes fair point, I can see how the issue is likely not driver specific. We have also observed issues with Lido drivers, RaSCSI, and the Mac Plus in the past. However, using Apple drivers is the sure way to trigger the most severe effect, so it's still worth mentioning as a reproduction path.
As a side note, in order to use a SCSI2SD with the Mac Plus, you need to configure the device with the following compatibility settings:

SCSI Selection Delay = 0 (default:255)
Respond to short SCSI selection pulses = True (default:False)

No idea if this helps. I couldn't find the source code for scsi2sd-util v5.x to see what this actually does.

To all of you who have had issues on your Mac Pluses: Please try the new 22.10 release. From our testing, the stability on the Plus is much improved in this version. https://github.com/akuker/RASCSI/releases/tag/v22.10.01

@uweseimet I would like to revisit this issue. I have a Mac Plus myself now and am able to assist with debugging.
To remove all other factors, I followed these test steps:

Created blank 20MB disk image with the "Miniscribe" profile in order to HD SC Setup to recognize it.

{
    "device_type": "SCHD",
    "vendor": "MINSCRIB",
    "product": "    M8425 - SCSI",
    "revision": "209A",
    "block_size": 512,
    "size": 20994048,
    "name": "Miniscribe M8425",
    "file_type": "hds",
    "description": "Recognized by unpatched Apple HD SC Setup.",
    "url": ""
},

Booted the Plus from System Tools floppy disk (System 6.0.0)
Launched HD SC Setup v2.0
Initialized the disk image (this creates the partition map, injects the disk driver, creates a file system, and mounts it)
Turn on trace level logging in rascsi
Copied the contents of the System Tools floppy disk (800k worth of data) onto the initialized disk image
Observe file transfer errors
With 100% repro rate, a write error will occur for at least one file (sometimes multiple files; it's not deterministic)
Leading up to the error, the file transfer process will pause for 20-30s before throwing the error in the OS, at which time a huge amount of logs are repeatedly output (the majority of attached logs)

pluslog.txt

@rdmark It appears as if the bus signals say that the DATA OUT phase is over before a full sector has been transferred. This is not an issue with the SCSI command implementations, but something that happens during the data transfer. Saying that I am not surprised that despite all of my changes the issue is still there, because my changes do not deal with the low-level signal handling and/or timing. The problem could also be a general RaSCSI hardware issue. If I remember correctly @akuker mentioned that he has some bus signal analyzer hardware. This might be what's needed in order to find out more.
It's amazing that since I also stumbled upon this issue early this year it has never happened again.

For the record, if someone reads this trying to get their Plus working, I prepared a modified MacPack image that uses Silverlining drivers and posted it here:

@uweseimet Unfortunately I had to give away both my Mac Pluses when I relocated internationally last month.
Is there anyone else subscribing to this thread who would test on their Plus? It'd be valuable to hear if the behavior has changed in any way in the branch that Uwe refers to.

One problem with this ticket appears to be reproducability. I have not seen this error with my setup for ages, but this does not mean that the problem is gone. It would be good if somebody had a setup where this error is quite reproducable, now that @rdmark does not have his hardware anymore.

I can confirm the issue exists on
PiSCSI Software-Version: 23.11.1, Hardware und OS: Raspberry Pi 3 Model B Rev 1.2, Linux 6.1.21-v7+ armv7l
actually.
I downloaded HD20_512-1GB-MacPlus-6+7.hda from somewhere as my 6.0.8 bootdisk had no tools to initialize the disk.
The image booted with 6.0.8, but Silverlining from that image was unhappy to start. So I used HD SC Setup to initialize a 200MB image. When trying to copy the system 7 folder from the image to the new disk I had the mentioned log entries:
Mar  3 17:40:08 raspi-rascsi PISCSI[457]: [2024-03-03 17:40:08.379] [error] (ID 5) - Not able to receive 512 byte(s) of data, only received 97
The last number changes with every line.
PiSCSI is the only device on the bus, it ran flawlessly on a Mac Classic last time I used it. That's a year ago however.
Both switches are on the "on" position.
I have an oszilloscope if that helps ...


Bring our maint branch for r15 up to the latest patches for Riak 1.4.x

Looks like this branch didn't get the scheduler patch, though the main motivation for this was to get the POODLE fix in.

These changes are included in commits 1921bef75700a85b5e7e0fba546e646e1be9af66 and 87663e4fe9154a99fda1824b4dd5dfd1b84c4987


ENTESB-10894, ENTESB-10896

BTW, this does not affect any of UI code.

@shawkins I have updated the code per your suggestions.

Merged this with additional changes to consolidate down to a single map of sources.  Also adding better handling of the openshift client in a follow-on commit to help with the integration test.


New functionality, schedule

Is it possible to somehow add a work schedule for android?
For example, turn off gps at night, but do not turn off the service.

Whats the usage of turning off the GPS and not the service? service has nothing to do when GPS is off.

Closing due to lack of response, feel free to open in anytime;


FTP/SFTP support for loading data (JSON, CSV, XML)

 Issue by aethant
Wednesday Feb 22, 2017 at 01:49 GMT
Originally opened as https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/292

Not sure whether this is a bug report, or a feature request or a request for clarification - is it possible to do an apoc.load call, using FTP/SFTP as a url? If so, how would you pass in the username and password?
I'm not really fluent in Java to delve into the code myself, but I'd imagine the underlying mechanics would involve opening the stream and reading it, just like any other file. Perhaps username and password could be passed in with the options object, just like the separator?
If it is currently possible, can someone point me in the right direction of how? If not, can I please officially request support for this? It'd save like 3 steps on a project I'm currently working on.

 Comment by abhishekunotech
Wednesday Feb 22, 2017 at 10:54 GMT

@aethant : If you do want to delve into the Java of this, Current implementation of apoc.load eventually traces back to creation of a HTTPClient Instance in Java using the URL you pass to apoc.load()...,
You can use an FTPClient instance of Java, in its place, if you have the resources to implement that and re-compile APOC locally.

 Comment by sarmbruster
Wednesday Feb 22, 2017 at 11:03 GMT

I think it should be easy to change https://github.com/neo4j-contrib/neo4j-apoc-procedures/blob/3.1/src/main/java/apoc/export/util/FileUtils.java#L18 to also check for ftp. By default the JVM does have URLStreamHandlers for http, https and ftp aboard. For any other protocols it is possible to supply additional URLStreamHandlers to the JVM, see https://docs.oracle.com/javase/8/docs/api/java/net/URL.html#URL-java.lang.String-java.lang.String-int-java.lang.String-
I think it's actually a good idea to change apoc code to be agnostic of url schemes and leave it up to the JVM if it can be loaded or not.

 Comment by jexp
Thursday Jun 29, 2017 at 07:45 GMT

FTP at least should be easy to check via ftp:// URLs
Not sure about URL-Handlers for sftp


[5.6] [ShrinkBorrowScope] Fixed assert.

Previously, it was asserted that hoisting over a terminator succeeded (because it is previously checked that it can be done).  That was erroneously done by putting the call to hoist within an invocation of the assert macro.  The result was that in release builds, the call was not made.  Here, that is fixed by just calling the hoist function and, in debug builds, asserting its return.
rdar://86809882

@swift-ci please test

@swift-ci please clean test windows platform

Will cherry-pick the NFC cleanup commit in a subsequent PR.


Like to donate but therfore like to see support for Kibana 7th Series

Hi mate,
I teseted your Radar Plugin, like it and personally willing to drop a donation.
However do to navtive support of "Show values on chart" in bar diagrams up now in kibana 7.3.0 i switched to it to have this comfortable view.
This is just one point why I realy appreciate your efforts for a longterm support the 7th/8th series instead of 6 anylonger (a bit outdated :o)
Maybe you can give us an Idea how much efforts it will need to made this plugin work with the 7th Series and to increase the chance someone is able to catch and support your great PlugIn.
Cheers

The plugin has not a version for Kibana 7 for now. It is my highest priority task.
Thanks for the understanding

Hi dlumbrer,
any news for the 7th series support?
You did it for the Network (thank you so much) and hopefull your next update is Radar.
Your Plugins are the Top5 for Kibana and helps me a lot.
Thanks for your great work

Can you please provide any update on the plugin for 7.x version?

hello dlumbrer
any update on kibana 7.xx?


fix(ci): Remove PAT_TOKEN ref

Overview
Removes the PAT_TOKEN requirement, which should re-enable CI for external contributors.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#494  👈
#493
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @clabby and the rest of your teammates on  Graphite

Ah nice, since we don't have submodules anymore this should work!


[TE] frontend - harleyjj/screenshot - update screenshot route to matc…

…h new Anomalies route
Please note that the file thirdeye/thirdeye-pinot/src/main/resources/scripts/getGraphPnj.js must be updated for the screenshot to function with the upgrades in this PR.  getGraphPnj.js updates will be in a separate pull request

Updates screenshot graph to new format consistent with the rest of Thirdeye
Updates comments in Anomaly Summary component

@harleyjj  Can you attach a screenshot of what the screenshot looks like?


Change the max network protocol version in the DNS seeder to 170_015 for NU5 testnet

See #1841 for details.
Second NU5 Testnet Activation

Set the max network protocol version to 170_015

For confirmation, see the corresponding zcashd PR:
https://github.com/zcash/zcash/pull/5330/files#diff-e04cb1e9f29f76897c6b84334238f621ff45ba13cf180ad1d0d442d50ebe51f7R40

Fixed by https://github.com/ZcashFoundation/dnsseeder/pull/13


GH-419: Pass unstable builders also into GitHubPrScheduler

This is needed to support triggering unstable builders using !buildbot PR comment
Pass GitHubPrScheduler a set of "known stable builders" to it can avoid triggering unstable builders unless it's a comment-based trigger

I merged your PR, thanks @itamaro.


Fix certain level sequence issues

The skippable and previewFirstShooterColor fields don't work.
If waitUntilFinished is set to false, some stuff like delays may break and the step might not be fully executed "in background".

previewFirstShooterColor fixed: https://github.com/jakubg1/OpenSMCE/commit/1902b545fc268e60c22649709b939c7643dc2fe6


Fix EdgePropertyList construction via _from_object_info

Fixes #561
The EdgePropertyList retains the same list instance during its lifetime
for containing the edge property wrappers. This is done so that references
user code might hold to its items to correctly update its contents.
In contrast to other types, it means that the state is not re-fetched from
the _pb_object if it were to change outside of the EdgePropertyList's
control.
This led to a bug when constructing objects via _from_object_info, which
first default-constructs the object (in the process creating the EdgePropertyList)
and then modifies the _pb_object.
To fix this, the EdgePropertyList now stores whether its parent object was
stored when this list was last accessed. If it changes from unstored to stored,
the following logic is applied:

If the current list is already populated (the "regular" case), only a sanity check
for matching length is performed
If the current list is empty, it is re-fetched from the parent object. This is the
case which occurs during construction with _from_object_info

This PR also fixes a bug in tree_object_from_resource_path, where the channel
argument was still used instead of server_wrapper.

@roosre this is a fairly significant bugfix, I'd suggest we do a 0.1b2 release for it.

Still figuring out some edge cases when the cloned object is accessed before storing.


_nuxt/empty.js was blocked with vite:true and ssr:false

Environment

Operating System: Linux
Node Version:     v14.19.3
Nuxt Version:     2.16.0-27720022.54e852f
Nitro Version:    0.5.4
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      bridge, ssr, serverHandlers, devServerHandlers, buildModules
Runtime Modules:  -
Build Modules<EMAIL_ADDRESS>

Reproduction

Open the default CodeSandbox template: https://codesandbox.io/p/github/nuxt/starter/tree/v2-bridge-codesandbox
Replace nuxt.config.js with this:

import { defineNuxtConfig } from "@nuxt/bridge";

export default defineNuxtConfig({
  bridge: {
    vite: true
  },

  ssr: false
});

(or open this CodeSandbox where I already replaced the config: https://codesandbox.io/s/nuxt-bridge-vite-empty-error-ee3gjg?file=/nuxt.config.js)

In Firefox, open the console (the error does not show in the sandbox console) and see the error:

Loading module from “https://ee3gjg.sse.codesandbox.io/_nuxt/empty.js” was blocked because of a disallowed MIME type (“text/html”).
Loading failed for the module with source “https://ee3gjg.sse.codesandbox.io/_nuxt/empty.js”.

In Chrome open the console and see the error:

empty.js: Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.

See that the page does not load

Describe the bug
When using vite: true and ssr: false in Nuxt/bridge, the page does not load and in your browser console you find an error telling that the file empty.js was blocked because it has the wrong MIME-type.
Additional context
No response
Logs
No response

👍 , facing the same issue

We are facing the same issue too.

Facing the same issue.

Facing the same issue.

same here

Same here, setting ssr:false gives this error.

@danielroe Any ideas here? Happy to look into it otherwise

Same issue here.

Would welcome it, thank you @joel-wenzel 🙏

I just ran into this same issue

Why does nuxt bridge have this problem with ssr false? it is not suposed to work with ssg?

I am also experiencing this. The workaround from @AndreyYolkin did not work for me.

I am also experiencing this. The workaround from @AndreyYolkin did not work for me.

Do you have nitro enabled? And also: webpack or vite? Will try to help

Yes I have nitro enabled. In my bridge options I set vite: true. Everything works if I set vite: false

I just created an empty repo with just nuxt and nuxt bridge installed.
This is all that is in the nuxt config. If I set SSR to true the problem goes away.
`import { defineNuxtConfig } from '@nuxt/bridge'
export default defineNuxtConfig({
bridge: {
nitro: true,
vite: true,
},
ssr: false,
})
`

https://github.com/AndreyYolkin/nuxt-bridge-app-spa this seems to be ok (despite the ENOENT error, which I've already submitted as https://github.com/nuxt/bridge/issues/734)

thanks @AndreyYolkin I'm one step closer. Now experiencing the same ENOENT issue.

The issue has been resolved in https://github.com/nuxt/bridge/pull/775.
cc: @danielroe


Widen docs content on wide screens

This adds a breakpoint that expands content for DSL reference
and user manual on wide screens.
Content copy is also made smaller and larger to fit smaller and
larger screens.

Context
We got feedback that we should allow a wider content area.
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commmits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

Can we have the single TOC with this one?

@lptr This is a pretty cheap change to get in for Gradle 4.5. Injecting the TOC elsewhere will require either JS or some gnarly Docbook sorcery.
I'd need to discuss the design with @aweida if we want to go with a single navbar, though I agree it could be "interesting".

I got a verbal 👍  from @aweida

@eriwen I think this looks fantastic, the responsive behavior spot on.

Can we have the single TOC with this one?

@lptr One of the primary objectives of the design is to allow a user to better understand "where they are" at any given point in time. With information as dense as ours, the concern is that jamming everything into a single nav element will push the elements out of view and perhaps make for a cluttered and overwhelming expereience.
The intent behind the second TOC is to provide a bit more context, structure and focus. Because of its effectiveness, it's becoming a common design pattern. A few relevant examples in our space

Docker
Google

I think we should leave it as is for now. If we see a recurring theme of feedback that it's not effective we can revisit. Also if there is a use case or something im missing please let me know.


Add ability to reference older versions of a table

Some kind of a SELECT * FROM [table_name] AS OF [timestamp] syntax.

I see a couple of options for making this work.
In terms of trying to abide by the AS OF syntax the options are:

Given that AS OF SYSTEM TIME is part of ANSI/ISO standard since 2011, which sqlparser conforms to, it would make sense to open a PR to sqlparser that would add this capability. This should be pretty straightforward:

add a if self.parser.parse_keywords(&[Keyword::AS, Keyword::OF, Keyword::SYSTEM, Keyword::TIME]) ... here
try to parse the time expression using parse_expr or something new
don't forget to append AS to RESERVED_FOR_TABLE_ALIAS, so that it doesn't get interpreted as a table alias while processing FROM targets. This is potentially a breaking change, as someone may be relying on using as as the table alias.
add a couple of tests

Copy into Seafowl codebase the relevant sqlparser's functions, and apply change from #1. This would become very verbose and cumbersome for maintenance, as we'd need to copy parse_query, parse_query_body and parse_select at the minimum (if we intend to support CTEs + time-travel SELECTs), and potentially more stuff to resolve RESERVED_FOR_TABLE_ALIAS.
Flip the syntax over, and use something like AS OF timestamp SELECT * FROM table. This would entail minimal code changes on our side, but has a number of downsides:

it's ugly
it's not aligned with the standards
we still wouldn't be able to support CTEs + time-travel

I'll still need to think about approaches not relying on AS OF, and see what we can do there.

As for the non-AS OF alternatives here are two:

Abuse the compound identifier syntax - SELECT * FROM test_table.'2022-01-01 20:01:01Z'. The parsed timestamp String is then available as the last element of the table name ident vector.
Abuse the table-valued functions - SELECT * FROM test_table(at => '2022-01-01 20:01:01Z'). The parsed timestamp String is then available as the (potentially named) element of the table args vector. This would also allow for additional flexibility, as we could specify some particular keywords that can be passed to fine-tune the version selection (e.g. at for the latest version at the given time, at_epoch for the given time in Unix epoch, before so that one pass an interval with time unit ((before => 3h), (before => 2d)), or simply earliest/oldest without anything else to get the oldest available version etc.). This is conditional on us not planning on exploiting table-valued functions for something else.


Can't get Biome to organize imports on save

These are my current language settings but I've tried a bunch of variations:
  "languages": {
    "TypeScript": {
      "language_servers": [
        "!typescript-language-server",
        "!eslint",
        "vtsls",
        "biome"
      ],
      "preferred_line_length": 88,
      "wrap_guides": [88],
      "format_on_save": "on",
      "formatter": {
        "language_server": {
          "name": "biome"
        }
      },
      "code_actions_on_format": {
        "source.fixAll.biome": true,
        "source.organizeImports.biome": true
      }
    }
  }

I've tried on Zed Preview 0.146.1 and also Zed 0.145.1.
I can trigger the code action inside the editor so I believe the LSP is set up properly:

Also formatting seems to work. Any suggestions would be appreciated.

Does the CLI work? If it is, then I think the issue is Zed. Maybe try to check the Daemon logs and see if Biome actually calls the import sorting.

I realized this thing, most likely related to this issue #26, where I thought the issue was already fixed, but apparently something else happen.

@ematipico  Yep biome check --write . does sort the imports for me. I don't see anything relevant in the Zed logs, not sure how to check the Biome LSP logs tbh.
@chungweileong94 I saw that issue which is why I tried the Zed Preview. Unfortunately it didn't fix it for me.

I pretty sure this is cause by Zed, as I haven't update my Biome version for a long time. The only thing that changed is Zed and Biome extension, even if I downgrade the extension, the issue still persist.

Ok makes sense. I created an issue there and I'll close this one. Thanks!

That's where the logs are stored: https://biomejs.dev/guides/editors/create-a-plugin/#daemon-logs

FYI after some trial and error, I was able to get sorting to work on save.
Had to add source.organizeImports below.
// settings.json
"code_actions_on_format": {
    "source.fixAll.biome": true,
    "source.organizeImports.biome": true,
    "source.organizeImports": true
  },

Had to add source.organizeImports below.

I don't think so though, this is to tell Zed to use the TypeScript LSP organizer import action. So even though it will be sorted, but it is not Biome import sorting.

Looks to be fixed now. See https://github.com/biomejs/biome-zed/issues/46#issuecomment-2365207074


1.20.1 compatibility

Checklist

[X] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
[X] I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
[X] This issue contains only one feature request/enhancement.

Description
The mod exists only on version 1.21.1
Additional information

I currently have no plans to do so as it requires a lot of work to backport since the code is different in older versions.
Also

mod that backports server performance improvements for the latest release from the latest snapshots


Some background colors are changing the foreground color

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.74.2
OS Version: Windows 11 version 10.0.22621

Steps to Reproduce:

Run PowerShell in Windows Terminal and VSCode integrated terminal side-by-side.
In both, type "`e[38;2;247;246;245mwhite`e[0m" and you'll see white foreground text.
In both, type "`e[48;2;5;163;226m`e[38;2;247;246;245mwhite on blue`e[0m".

Notice how the colors are not correct in VSCode.
Note: this is a simplified repro of my OMP prompt, which you can also see the discrepancy in the screenshots. It works with some colors, though, such as white on purple.

This is an accessibility feature, see https://code.visualstudio.com/docs/terminal/appearance#_why-are-the-colors-in-the-terminal-not-correct


Updated data for frontend testing in data/frontend directory

@Mhtaba76 use this data to test out the frontend, let me know if you have any questions. It contains information for two models, which can be used to mock up multiple template models! See below for the contents:

Bill of Materials
Template Model Impacts
Prebuilt Scenarios
Project Metadata


no MidasDetector export

i want to use MidasDetector, but it failed:
from controlnet_aux import OpenposeDetector, MLSDdetector, MidasDetector, CannyDetector, HEDdetector
ImportError: cannot import name 'MidasDetector' from 'controlnet_aux'

@junjiexv
try installing by
pip uninstall controlnet_aux
pip install git+https://github.com/patrickvonplaten/controlnet_aux.git

thinks, it works!


Add script to collect logs

Looks like I copied over an old version of the script. Let me fix that

Okay. This should be up to date with the latest script that accounts OpenShift.


[code health] Tighten up client status_request processing

Instead of making a positive comparison against the invalid value
that our server would send, make a negative check against the only
value that is not an error.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Description of change

Pushed.


ETH Transection issue

When we generate new address endpoint for ETH we will not receive "wif" key.
Then how will we make transaction with java-client as
// WIF Format of your private Key
String myPrivateKey = "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa";
myPrivateKey must be in wif format.

I have found the solution for eth and beth transactions
Just replace
SignUtils.signWithBase58KeyWithPubKey(unsignedTx, myPrivateKey);
with
SignUtils.signWithHexKeyWithPubKey(unsignedTx, myPrivateKey);
and use eth or beth private key instead of wif.


ENH: implemented to_moltype method in core.sequence.Sequence, fixes #247

Thanks Gavin!
I tried new.add_annotation(ann.__class__, ann.type, ann.name, ann.map) but it isn't working very well, so I implemented the pattern below and added corresponding tests.
For some convenience, I also added some functions in cogent3/core/annotation._Annotatable class, please have a look and let me know if any unsuitable codes!
Many thanks!

There is a problem with this approach -- it adds methods onto _Annotatable that all sub-classes inherit. That's a problem because the method names are a bit confusing in those contexts. For instance, Alignment.add_simple_variable() does not have an obvious meaning.
I think I get what the issue was with my original approach (some of the extra arguments to the constructor). Here's an alternate approach.
a new method _Annotatable.copy_to_seq()
Creates a new annotation with identical type, name, position etc.. on a new sequence.
_Annotatable.copy_to_seq(new_seq). The method should check that the incoming sequence has exactly the same length as self.parent. To be safe, the method should be able to just use the contents of the anno._serialisable dict, (possibly need to do a deepcopy?), which contains all the construction arguments.

Many thanks Gavin! I will implement this new approach as soon as possible!


add github actions file

This is working but service-parent is failing because of service parent, that should be another PR

LGTM.

@yma96 can we merge this now?

I need to do tests with the new tag yesterday, so updated the GitHub actions and @ you on the related commits, you could check and update if you want. @shokakucarrier


Add custom domains to edgeIngress CRD

Description
This PR update edgeIngress CRD to support customDomains edition.
Related to this and this PR

We wait the next version of the agent to merge this PR


fix: migrate from babel-eslint

babel-eslint is deprecated now:  babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
migrated by https://babeljs.io/blog/2020/07/13/the-state-of-babel-eslint#the-future

Thank you! Released at 1.2.1 version)


JAVA_HOME points to sdkman jdk home instead of microsoft Java home

Migrated from https://github.com/microsoft/vscode-dev-containers/issues/1646
//cc @samruddhikhandale

@dashorst said

VSCode Version: Version: 1.71.2 (Universal) Commit: 74b1f979648cc44d385a2286793c226e611f59e7
Local OS Version: macOS Monterrey 12.6
Local chip architecture: Apple Silicon
Reproduces in: Remote - Containers
Name of Dev Container Definition with Issue: Java (no qualifiers)

The devcontainer.json points to this URL:
https://github.com/microsoft/vscode-dev-containers/tree/v0.245.2/containers/java
The Dockerfile points to this parent container:
ARG VARIANT="17-bullseye"
FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}

Steps to Reproduce:

add remote container files to project
select java
select maven (no node or gradle)
select java 17 (bullseye)
no other extensions
start mvn in the terminal
get error that JAVA_HOME is invalid

$ mvn help:help
The JAVA_HOME environment variable is not defined correctly,
this environment variable is needed to run this program.

JAVA_HOME points to this:
$ echo $JAVA_HOME
/usr/local/sdkman/candidates/java/current

However when I run java --version:
$ java --version
openjdk <IP_ADDRESS> 2022-08-12 LTS
OpenJDK Runtime Environment Microsoft-40354 (build <IP_ADDRESS>+1-LTS)
OpenJDK 64-Bit Server VM Microsoft-40354 (build <IP_ADDRESS>+1-LTS, mixed mode)

And look where it gets its cup of Java from:
$ which java
/usr/lib/jvm/msopenjdk-current/bin/java

This says to me that the configuration of the Java image is not correct.
Literally a week ago this worked without any problems.

@Danielv123 said
I had the same issue with java 11, added the following to .devcontainer.json to fix it.
	"containerEnv": {
		"JAVA_HOME": "/usr/lib/jvm/msopenjdk-current"
	}

@nielspardon said
It seems JAVA_HOME is still correctly set in the following container image tags: 0.205.4-${VARIANT}. If you change your Dockerfile in the following way it should work properly again:
-FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}
+FROM mcr.microsoft.com/vscode/devcontainers/java:0.205.4-${VARIANT}

Just adding the manual JAVA_HOME env variable was not enough for me since VS Code could not communicate with the Gradle server properly.
@joshspicer since you are the one who last touched containers/java/definition-manifest.json can you help to get this fixed or find the right person who can fix this?

@samruddhikhandale Given the above comment - it looks like this is a problem with the updated image since 0.205.5 is when it switched.  Can you take a look?

My original message might have been a bit imprecise. I just picked 0.205.4 because it seemed to be the previous version referenced in the definition-manifest.json and that did work for me. I did some further testing and 0.205.5 also works for me. After that version 0.205.6, 0.205.7, 0.205.8 and 0.205.9 all have various different issues for me. I did test with the 17-bulleye variant.

Looks like a bug in the java template/definition in microsoft/vscode-dev-containers

Looks like a bug in the java template/definition in microsoft/vscode-dev-containers.
We are currently working on changing the Add Dev Container Configuration files command to dynamically pull templates from https://containers.dev/templates. Once the changes are released, it should help fix this bug as the Java template will be built from devcontainers/templates repository.

Validated that the bug does not appear in https://github.com/devcontainers/templates/tree/main/src/java

We are currently working on changing the Add Dev Container Configuration files command to dynamically pull templates from https://containers.dev/templates. Once the changes are released, it should help fix this bug as the Java template will be built from devcontainers/templates repository.

ℹ  Update - It is now available in Dev Containers extension: Pre-release version

Closing as the issue is fixed with the updated contents of the Java Template (here) - which is available with Add Dev Container Configuration Files cmd.


Deleting project.json didn't update references

This may only be an issue for built-in references.
Add and run this code in a manual trigger:
#r "Microsoft.Azure.Documents.Client"

using System;
using Microsoft.Azure.Documents;

public static void Run(string input, TraceWriter log)
{
    log.Info(typeof(Document).Assembly.Location);
}

You'll see the location: D:\Program Files (x86)\SiteExtensions\Functions\1.0.10690\bin\Microsoft.Azure.Documents.Client.dll
Add this project.json and run again:
{
  "frameworks": {
      "net46": {
        "dependencies": {
          "Microsoft.Azure.DocumentDB": "1.13.1"
        }
      }
   }
}

You can see logs that it was installed: D:\home\data\Functions\packages\nuget\Microsoft.Azure.DocumentDB\1.11.1\lib\net45\Microsoft.Azure.Documents.Client.dll
Delete the project.json (and project.lock.json) and run again: D:\home\data\Functions\packages\nuget\Microsoft.Azure.DocumentDB\1.11.1\lib\net45\Microsoft.Azure.Documents.Client.dll
It's still referencing the old assembly.
If you restart the site, it'll go back to the original.

@brettsam have you tested this on the most recent version of the runtime? After the restart/assembly watch changes, it looks like this might have been resolved. I can't repro this with your steps using the current bits.

It's entirely possible that you've fixed it already. I'll give it another shot. What about #1260?

No, I still see it. I've updated the project.json above to be a higher version than we have built-in (1.13.1). Maybe that's the trick. I've seen a couple of people (back when I filed this) get into a state where they'd pulled in a newer version that had some breaking change, then they couldn't figure out why it still didn't work after the project.json was deleted.

I have used 1.13.1 and did see the correct behavior. Can you detail the sequence of events? Did you delete the project or the lock file first?

And I'm looking at this issue because of #1260


Retrieve certificate details such as subject, serial, SAN

I can't seem to find a way to retrieve certificate information such as subject name, serial number, subject alternative names.
I can see how to get Azure-specific info but not what I mentioned above. Is there a way to do it using Python SDK?

Could you tell us which Python SDK library are you using?
It looks to me you are looking for parsing certificate using Python.
Maybe this can help? https://stackoverflow.com/questions/16899247/how-can-i-decode-a-ssl-certificate-using-python

I apologize for the lack of information and thanks for the quick response.
I'm using azure.keyvault.certificates modules. What I'm looking to retrieve is blanked out. I can see how I can get name, tag, created_on, vault_url, etc. But the fields in my screenshot do not appear to be accessible via API calls using the library.

Thanks for the information. We will take a look ASAP.

Thank you for the clarification. I was really looking forward to being able to retrieve serial number via Python SDK. It would be really nice to have that option added to Python SDK.

But in the meantime, your suggestion will work for me.

After looking into this a little more, it looks like Powershell must get the certificate's serial number from the X509 certificate -- which is part of a KeyVaultCertificate. You can get the serial number via the cryptography package by using the code below:
from cryptography import x509

client = CertificateClient("https://{vault-name}.vault.azure.net", credential)
x509_bytes = client.get_certificate("cert-name").cer
x509 = x509.load_der_x509_certificate(x509_bytes)
serial = x509.serial_number  # the serial number as an int
serial_hex = hex(serial)  # the serial number in hex (as it appears in the Portal)

I hope this helps!

This is great! That solves my problem. Much appreciated.

@mccoyp's solution works great!
note: if you happen to see this error
TypeError: argument 'data': 'bytearray' object cannot be converted to 'PyBytes'
then you'll want to use bytes() like this
x509  = x509.load_der_x509_certificate(bytes(x509_bytes))


server.info.uri vs hostname issue

We have issues due to request.server.info.uri ( https://github.com/glennjones/hapi-swagger/commit/39b7173d802ff954d29e39d57f246e7d93f82c12#diff-6d186b954a58d5bb740f73d84fe39073L135 )
(In our case) Swagger links are broken since server.info.uri returns http://dev-useast-example:3000/ and we expose swagger interface via different hostname (http://example.com) (it runs behind load balancer) Is there any way to get around?

Same here, app exposed behind a nginx reverse proxy, with 0.7.2 release, swagger is broken, reporting
Unable to read api '' from path http://localhost:3000/docs?path= (server returned undefined)

This is not OK. You can't make braking changes in the patch part of your version number. You are on npm so please use http://semver.org/ correctly.

Hi Pierre,
This was an honest mistake which I am now spending my afternoon fixing when I should be doing paid work. If I had understood the outcome of this change  I would not have deployed it. It is taking a little longer than I would like to post up a fix as I needed to take into account some changes around server.connections I was half way through.
I do understand semantic version numbers, in this case I did not foresee the change would be breaking. As I said a mistake on my part.
I known a lot of people now rely on this project, but it is just an unpaid side project for me.
Your tone came across as bit off and unhelpful.
Glenn

@glennjones : We (at our company) extremely appreciate your effort and contribution. I just want to let you know. Thanks :)

I appreciate the work and understand that you can't expect perfect from open source. I was merely trying to be terse while pointing out the seriousness of the issue. We solved it by forcing version 0.7.1. A general guideline is that every time you remove something it is a breaking change.
Since a breaking change was able to get deployed there might be issues with the tests. I will see if I can contribute with something in that area in the future.

cmfatih Thanks for words much appreciate
As the commit v0.7.2 broke the functionality for people I have reverted the code back and released it as v0.7.3  Hopefully others just about to update the packages will now not have the same problem as you if they use basePath - not good, but practical
So you should be able to move to v0.7.3 and start using basePath again with reverse proxy etc
The updates for 'routes.prefixwhich cause this issue and pending update aroundserver.connectionscannot be made without changingbasePath`. So I am taking that problem away to come up with a solution, at which point I will move to the whole thing to v0.8.0 I will make sure that there the reverse proxy use case is covered in the new solution.
Hope that gets everyone backup and running


d3-selection enter() selection/Enter Nodes changes

@mbostock I know you are extremely busy finalizing the major release of the modules and the related documentation.
As I was drawing up some typescript definition files to go along with your new and wonderful modules, I noticed the following.
In the documentation for changes to how d3-selection selections now work, you point out that, enter() selections are now full selections of Enter Nodes:

There is now only one class of selection. 3.x implemented enter selections using a special class with different behavior for enter.append and enter.select; a consequence of this design was that enter selections in 3.x lacked certain methods. In 4.0, enter selections are simply normal selections; they have the same methods and the same behavior. Enter nodes now implement node.appendChild, node.insertBefore, node.querySelector, and node.querySelectorAll.

Some of the methods defined on general selections (of existing nodes), e.g. .on(...) would, it appears, create errors if called on an enter() selection, prior to appending materialized elements. E.g. the required .addEventListener(...) method would not yet be defined on the this context.
So, from your perspective, would it be worthwhile to simply add some comments to the documentation?
As far as the related draft typescript definitions for d3-selection are concerned, I could simply create a separate interface to describe the limited scope of 'viable' methods on the enter() selection. This was the previous practice for the D3 3.x typescript definitions.
Your insight would be most appreciated.

I think it’s sufficient to explicitly list the methods that enter nodes implement; adding caveats on selection.on and other methods that are nonsensical on enter nodes would be distracting. And I don’t think it’s a good idea to imply there is a separate interface for the enter selection. That would have made sense for 3.x, but unlike 3.x, 4.0’s enter selection is the same class as selection; the only difference is that it contains enter nodes (placeholders) rather than elements. A better analogy is in terms of generics, as in Java; say Selection<Element> vs. Selection<EnterNode>.
More generally, you’re allowed to create selections of things (Selection<T>) that are not elements using d3.select(T) and d3.selectAll(Array<T>). As long as you don’t try to treat non-elements as elements, the selection and any operations on it are valid. For example OMG Particles II selects a plain object for the purpose of creating a transition that is then rendered to Canvas. That’s a bit of an edge case, and rarely needed, but I don’t want to strictly limit selections to DOM elements.


Have a default user logged in amp in travis build for test

For now we need to sign and log a user in amp at each tests on cli or api travis is executing.
Could be good to have one created by default

@freignat91 I think it can be closed since 0.10.0

@freignat91 closing this one, but feel free to reopen if needed


sip: adds checks for stat code keyword

Ticket
Redmine ticket: https://redmine.openinfosecfoundation.org/issues/7295
Fixed by https://github.com/OISF/suricata/pull/11846

Merged in #2136, thanks!


[T3A4][T17-A3]Abdul Rahman

Add new exception to handle the case of missing file. Ready for review!~

[T3A5][T17-A3]Abdul Rahman

@arshrahman Some comments added. Please close the PR after reading comments. Good job!

@JoelT-92 Thanks Joel for your valuable comments.
Will take note of them and apply them in future learning activities.
Made a mistake by committing to the same branch. Won't happen again. Sorry!


Add support for all array elements

When defining type traits we needed a way to match all arrays indexes to access arrays struct's fields.
As an example why this change is needed and how it will be used I added Backend Service support where Backends, an array which is required, has some optional fields.

/assign @bowei
/cc @yazanri

split off the change for backendservice into a separate commit

split off the change for backendservice into a separate commit

done, I will post PR with BS changes after this one is closed.

Make sure you update your commit comment to match the updated code

Make sure you update your commit comment to match the updated code

done

@bowei I added support for Map indices. At first I thought that I will do this in new PR but since you mentioned it in some comment I added functions + tests for that. PTAL

/lgtm
/approve


Cyrilic font issue in ohmyzsh

I set Zsh as my default shell for bash for Windows after that I installed "oh my zsh" as default theme for Zsh https://github.com/robbyrussell/oh-my-zsh
I am using default theme "rubyshell" for command prompt  but I have some issue with the unicode characters and me unable to set "Ubuntu" as default font for the bash for windows

https://github.com/robbyrussell/oh-my-zsh/blob/master/themes/robbyrussell.zsh-theme

You can't use opentype fonts in conhost right now.

You can change the default font in CMD with fonts here https://github.com/powerline/fonts

This issue was moved to Microsoft/console#90


HHH-9979 : Merged transient entity may not contain some associations …

…when passed to PrePersist/PostPersist callbacks

A new pull request will be created when OperationContext has been introduced for 5.1.


Add filter to optional parameters for service definitions

Note:
If you have a feature request, you should contact support so the request can be properly tracked.
Is your feature request related to a problem? Please describe.
Point me to the right place If I've missed it as getting familiar with Go myself, but It would be super useful to add some supporting attributes to the service definition endpoint like you have on other endpoints so we can filter the service definitions.
The API Keys has an incredible amount of support, which allows a great amount of support in the terraform provider.
https://github.com/DataDog/datadog-api-client-go/blob/master/api/datadogV2/api_key_management.go
https://github.com/DataDog/terraform-provider-datadog/blob/master/datadog/fwprovider/data_source_datadog_api_key.go#L86
Describe the solution you'd like
The use case for us would be great to have filters to support getting all service definitions by team, tier, type, tag etc, combined or singular filter arguments.
Describe alternatives you've considered
Currently I have a powershell script in my Terraform code that uses the external provider to query the datadog API for all service definitions and filters though them by the filter passed in.

Hello, I have passed the request along to the API owners and will followup if there are any updates. Thanks!


How to bind a crystal closure to c library

Hello:
Using DukTape (Javascript embedded engine):
dependencies:
  duktape:
    github: jessedoyle/duktape.cr
    version: ~> 0.7.0

I tested this code:
  sbx = Duktape::Sandbox.new

  sbx.push_global_object

  test = 10
  sbx.push_proc(2) do |ptr| # 2 stack arguments
    env = Duktape::Sandbox.new ptr
    a = env.get_number 0
    test = env.get_number 1
    env.push_number a + test
    env.return 1 # return success
  end

  sbx.put_prop_string -2, "adder"
  sbx.eval! "print(adder(2, 3));" # => 5

this returns
passing a closure to C is not allowed

Any help on how can i achieve the closures usage i a c binding?

Closures can't be passed as function pointers to external libraries, because in order to invoke the function, a context must be passed as argument.
C libraries that requires a function pointer often receives a void *data as well, and they send this data back to the function. You can decompose a proc (http://crystal-lang.org/api/Proc.html) using pointer and closure_data, and reconstruct the Proc once the callback is executed.
Anyway, this seems to be an issue in Duktape shard. Please, open an issue in the project: https://github.com/jessedoyle/duktape.cr

Thanks, waj. I'm closing the issue.
I'll love to see an example with this kind of behavior (decomposing proc and reconstructing it), for replicating it in the duktape shard. Maybe there's some code already doing this in the standard library?

@raydf We should probably document that in Proc's docs.
Right now you can try something like this:
a = 1
proc = ->{ a }
pp proc.closure?

ptr = proc.pointer
data = proc.closure_data

a = 2

# Or Proc(Int32).new(ptr, data)
proc2 = typeof(proc).new(ptr, data)
pp proc2.call

But that's something that duktape must do with the proc you pass it to push_proc.

Thanks asterite. +1 for adding to Proc's docs.

@raydf I just added docs for Proc and Box, together with an example of how to pass a Proc to C. In the end there's no need to decompose a Proc into function pointer + closure data.

@asterite: Thanks for adding great documentation (I wasn't even aware of Box - it seems useful)!
After reading over the updated docs, I just want to ask a quick question:

If the c function that we are binding to (link) doesn't accept a void* data argument, then it is not possible to pass the closure data to the function as described in the docs, correct?

@jessedoyle Exactly.
I thought that since others have probably written bindings to duktape they must have ran into this issue. I found this and this, which feel kind of hacky, but, well, seem to be the only way to do what you (and others) want.

Great - I just wanted to make sure I didn't misread the docs (which were very clear). Thanks!

Thanks @asterite for the added docs. Sorry that i'm a noob to C, so i'm learning a lot from your comments and docs and also from @jessedoyle duktape binding source code.
Right now i'm more like a tester and not contributing too much. But i have in my plans to implement some kind of smtp shard and a complete library with bindings to libuuid.