Sample category pictures make structure unclear

In the Projects pages, categories and sub-categories are shown with a name and also an image. When the image is one of the actual projects, it can look to the user like just a gallery with only one item in it rather than a category. I suggest more abstract images for categories, or perhaps no images.
For example, on the starting Projects page, there appears at first glance to be just the little race car. If you make it past this, the next choice of hubs is more clear, but then inside Inventor it again looks like few choices, and you have to be persistent to make it all the way to seeing the Mini Loader sample for example.
A related issue is to consider whether the sub-category structure is more complex than necessary for now.

Thanks for the input!
It is currently structured like this because the tutorial pages are generated in the same way as the sets pages.
I feel like the whole site could use some work, but I went ahead and added the tutorial section recently anyway because we shouldn't hold back writing stuff in the mean time.
It should be easy enough to move things around later, so let's keep writing :)


cleanup(ci): split a driverkit workflow from main ci workflow.

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area CI
Does this PR require a change in the driver versions?
What this PR does / why we need it:
The PR extracts a driverkit workflow from the main ci workflow (that is indeed getting too big).
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc @Molter73

/milestone 0.11.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, Molter73
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,Molter73]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, Molter73
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,Molter73]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Implement search feature

Search from the current 20 stocks displayed on the home page

calculate missing field values on the fly or store in db (later)


150 n320 callback number of pixels used by datashader

PR to fix https://github.com/ecmwf/anemoi-training/issues/150
Propose change - make the 'n_pixels' more flexible so that  when using finer resolutions (like n32),  500 as n_pixels should be enough, but for hidden grid plots and coarser ones then we need to use way less, so the other condition would apply.
Note - Regarding the proposed change n_pixels = min(int(np.floor(data.shape[0] * 0.004)), 500). This has been found by testing different values, so it's fair to say that 0.04% could be better tweaked in the future if needed.
This PR also includes contributions from @mpvginde who developed the code to ensure common color map ranges
Closes #150

Example plots o96 - https://mlflow.ecmwf.int/#/experiments/5/runs/000304c17e304ac9bc353a7d0931d884/artifacts
Example plots n320 - https://mlflow.ecmwf.int/#/experiments/5/runs/f13f771ed2ac43268a75471093d71889

Has this been tested at a few resolutions?

Has this been tested at a few resolutions?

Worked with @JPXKQX on this and should be now working fine for LAM


rules-complete.toml: add some more example rules for RulesBasedSampler.

The example sampler rules in rules_complete.toml cover some of the basic boolean operators, but miss things like contains, starts-with, etc that are pretty useful and powerful. It's easy enough to look at the code and figure out which rules actually exist (so I would totally understand if you don't want to go down the path of enumerating every rule type in the example config), but I would have found it helpful to have a more complete set of examples to work off of so I made this PR.

Oops, looks like some tests are failing here. I'll reopen once I fix those.


⚠ Secret Website 3 has degraded performance

In d6e0b7e, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 3064 ms

Resolved: Secret Website 3 performance has improved in 7099e48.


first build

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f33nh55pij/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: /tmp/abs_f33nh55pij/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_f33nh55pij/clone/recipe/meta.yaml:26: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_f33nh55pij/clone/recipe/meta.yaml:35: http_url: http://github.com/msoulier/tftpy is not https
WARNING: /tmp/abs_f33nh55pij/clone/recipe/meta.yaml:35: missing_description: The recipe is missing a description
ERROR: /tmp/abs_f33nh55pij/clone/recipe/meta.yaml:35: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_f33nh55pij/clone/recipe/meta.yaml:35: missing_dev_url: The recipe is missing a dev_url
WARNING: /tmp/abs_f33nh55pij/clone/recipe/meta.yaml:35: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_16jh1mm0e6/clone/recipe/meta.yaml:1: missing_test_requirement_pip: pip is required in the test requirements.
ERROR: /tmp/abs_16jh1mm0e6/clone/recipe/meta.yaml:38: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_16jh1mm0e6/clone/recipe/meta.yaml:38: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_16jh1mm0e6/clone/recipe/meta.yaml:38: missing_description: The recipe is missing a description
WARNING: /tmp/abs_16jh1mm0e6/clone/recipe/meta.yaml:38: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_69po1m6g8o/clone/recipe/meta.yaml:1: missing_test_requirement_pip: pip is required in the test requirements.
ERROR: /tmp/abs_69po1m6g8o/clone/recipe/meta.yaml:39: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_69po1m6g8o/clone/recipe/meta.yaml:39: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
WARNING: /tmp/abs_69po1m6g8o/clone/recipe/meta.yaml:39: missing_description: The recipe is missing a description
ERROR: /tmp/abs_69po1m6g8o/clone/recipe/meta.yaml:39: missing_dev_url: The recipe is missing a dev_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_3a7qcr6pqw/clone/recipe/meta.yaml:41: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: /tmp/abs_3a7qcr6pqw/clone/recipe/meta.yaml:41: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_3a7qcr6pqw/clone/recipe/meta.yaml:41: missing_description: The recipe is missing a description
ERROR: /tmp/abs_3a7qcr6pqw/clone/recipe/meta.yaml:41: missing_dev_url: The recipe is missing a dev_url
Errors were found


nombre: Configurar Java JDK   usos<EMAIL_ADDRESS>

Description:
A clear and concise description of what the bug is.
Task version:
Specify the task version
Platform:

[ ] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[ ] Hosted
[ ] Self-hosted

Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
Expected behavior:
A description of what you expected to happen.
Actual behavior:
A description of what is actually happening.

Hello @Jhonnimil. I'm closing the issue for now, because it looks like a spam. If you have any concerns feel free to feel the issue and reopen it.


Implementing PixelArt scaling mode in ImageSampler

What problem does this solve or what need does it fill?
Right now we have two options for scaling with pixel art: Nearest and Linear. Nearest is great for integer scaling, Linear has the trademark blurriness that accompanies Bilinear filtering.
What solution would you like?
Cole Cecil has come up with an innovative way to take advantage of bilinear filtering using a custom vertex and fragment shader to implement arbitrary scaling factors with a minimal amount of blurriness:
https://colececil.io/blog/2017/scaling-pixel-art-without-destroying-it/
I think it would be great to implement on the 2D camera as a scaling method.
What alternative(s) have you considered?
I'm currently using nearest using only integer scaling factors. This would enable arbitrary scaling factors.
Additional context
I'd really like to help implement this because it'd be a great learning exercise. I'm just not sure where I'd start to implement a custom set of shaders into the pipeline.

Previous discussion on a pixel perfect shader: https://github.com/bevyengine/bevy/issues/1856
Seems like there is a pixel camera plugin here: https://github.com/drakmaniso/bevy_pixel_camera


Empty ignore_php_platform_requirements does not disable PHP 8.0 default behavior

Bug Report

Q
A

Version(s)
1.11.5

Summary

When I've impelemented the ignore_php_platform_requirements feature, the main idea was to get rid of the old and yet deprecated ignore_platform_reqs_8 feature, which defaulted to true.
I was assuming (and thought I've implemented it that way 😅) that when adding an empty ignore_php_platform_requirements object to the .laminas-ci.json, we do not explicitly mark PHP 8.0 as true.
Sadly, it does and thus, I'd like to either change this and/or remove ignore_platform_reqs_8 entirely.
ignore_php_platform_requirements option is available since v1.9.0 (released in 08/2021)
Current behavior

Adding an empty ignore_php_platform_requirements does not prevent ignoring platform reqs for PHP 8.0.
How to reproduce

Add an empty ignore_php_platform_requirements to the .laminas-ci.json in a project with PHP 8.0 support and check matrix output. It contains ignore_php_platform_requirement: true for PHP 8.0.
Expected behavior

ignore_php_platform_requirement should be false for PHP 8.0.

Well, since we do validate project configs with the laminas-ci.schema.json and disallow additional properties, projects containing ignore_platform_reqs_8 won't work anymore.
So we can safely remove ignore_platform_reqs_8 but we still should provide some information to the CHANGELOG that platform requirements for PHP 8 are not ignored by default anymore.

Input handling will be removed with #83, matrix output stays the same for now.
Disabled PHP 8.0 default ignore behavior.

I have similar issues related to this (this comment is just informational):

https://github.com/Roave/BackwardCompatibilityCheck/runs/6661744285?check_suite_focus=true
https://github.com/Roave/BackwardCompatibilityCheck/runs/6661746931?check_suite_focus=true

They lead to https://github.com/Roave/BackwardCompatibilityCheck/pull/529 failing
The .laminas-ci.json is as follows:
{
    "extensions": [
        "bcmath"
    ]
}

The generated argument for a "latest dependencies" build:
"{\"command\":\"./vendor/bin/phpunit\",\"php\":\"8.0\",\"extensions\":[\"json\",\"bcmath\"],\"ini\":[\"memory_limit        = -1\"],\"dependencies\":\"latest\",\"ignore_platform_reqs_8\":true,\"ignore_php_platform_requirement\":true,\"additional_composer_arguments\":[]}"

More specifically:
\"dependencies\":\"latest\",\"ignore_platform_reqs_8\":true,\"ignore_php_platform_requirement\":true


Fix typo in HtmlToken.cs

Types of Changes
Prerequisites
Please make sure you can check the following two boxes:

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project

Contribution Type
What types of changes does your code introduce? Put an x in all the boxes that apply:

[x] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[ ] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Description
The sentence:

Removes the a new line in the beginning, if any.

Should not have the word "a":

Removes the new line in the beginning, if any.

Can you make 1 PR with all these tiny updates? Thanks.

Was thinking the same thing. You can leave this one open so I can push other commits to it (as I keep reviewing the docs), then when done I will let you know to review all of them in one go :+1:

@FlorianRappl that's all the fixes for now. If I find any others in the future I will batch them like these ones. Thanks for following up and for all your hard work on this library!


Error while converting mrcnn to tf dialect

Actually I wanted to convert mrcnn model to tf dialect .I downloaded model from TensorFlow Hub. and I tried adding signatures to model using import tensorflow.compat.v2 as tf
loaded_model = tf.saved_model.load(’/maskedrcnn’)
call = loaded_model.call.get_concrete_function(
tf.TensorSpec(shape=(1, 1024, 1024, 3), dtype=tf.uint8))
signatures = {‘predict’: call}
tf.saved_model.save(loaded_model,’/ex’, signatures=signatures)
I got warning as Found untraced functions such as restored_function_body, restored_function_body, restored_function_body, restored_function_body, restored_function_body while saving (showing 5 of 125). These functions will not be directly callable after loading.
If I use tensorflow/bazel-bin/tensorflow/compiler/mlir/tf-mlir-translate --savedmodel-objectgraph-to-mlir  /data/maskedrcnn -o sample.mlir
I am getting error as tensorflow/bazel-bin/tensorflow/compiler/mlir/tf-mlir-translate: Symbol _ZN10tensorflow35_DeviceAttributes_default_instance_E' has different size in shared object, consider re-linking tensorflow/bazel-bin/tensorflow/compiler/mlir/tf-mlir-translate: Symbol _ZN10tensorflow43_ConfigProto_Experimental_default_instance_E' has different size in shared object, consider re-linking
tensorflow/bazel-bin/tensorflow/compiler/mlir/tf-mlir-translate: Symbol `_ZTVN10tensorflow4data11DatasetBaseE' has different size in shared object, consider re-linking
tensorflow/bazel-bin/tensorflow/compiler/mlir/tf-mlir-translate: symbol lookup error:tensorflow/bazel-bin/tensorflow/compiler/mlir/tf-mlir-translate: undefined symbol: _ZN10tensorflow28CollectiveParamResolverLocal22GetOrCreateInstanceRecEPKNS0_8GroupRecEPNS_16CollectiveParamsEPb

@ArunaKote ,
Can you please try the code in latest tensorflow v2.5 or v2.6 and let us know if the issue still persists.Thanks!

I am using tensorflow v2.6.
I am getting error as:
tf_out.mlir:289:102: error: tf dialect has no types, potentially meant !tf_type.string
%cst_284 = "tf.Const"() {value = dense<"Incorrect field size: actual vs expected."> : tensor<!tf.string>} : () -> tensor<!tf.string>

@ArunaKote ,
Code shared is full of indentation errors, please share a colab gist with issue reported or simple stand alone indented code with all dependencies such that we can replicate the issue reported.Thanks

pip install tensorflow-hub
pip install tensorflow
I have attached python file
model.zip

@ArunaKote ,
I was able to execute the mentioned code in tf v2.6 without any error.Please find the gist of it here.Please try to test the code in new virtual environment.Thanks!

Thank You.I able to run the above code.I used tf  2.7.0-dev20210831.I able to save mlir into tf.mlir
Then I used tensorflow/bazel-bin/tensorflow/compiler/mlir/tf-opt -canonicalize  --tf-shape-inference -xla-legalize-tf  --print-ir-before-all &>1  tf.mlir
Got Error as:
ex_13_09.mlir:3:3: error: The following operations cannot be legalized: tf.Const (count: 1); tf.CropAndResize (count: 2); tf.NonMaxSuppressionV5 (count: 91); tf.Placeholder (count: 1); tf.ResizeBilinear (count: 1); tf.Squeeze (count: 4); tf.TopKV2 (count: 4); tf.Where (count: 3). These legalization failure(s) may be due to missing TF to HLO lowerings and/or unsupported attributes, etc.
builtin.func @main() {
^
ex_13_09.mlir:3:3: error: Emitting more detail about one op that failed to legalize...
builtin.func @main() {
^
ex_13_09.mlir:289:16: error: 'tf.Const' op is not legalizable
%cst_284 = "tf.Const"() {value = dense<"Incorrect field size: actual vs expected."> : tensor<!tf_type.string>} : () -> tensor<!tf_type.string>
^
ex_13_09.mlir:289:16: note: see current operation: %704 = "tf.Const"() {value = dense<"Incorrect field size: actual vs expected."> : tensor<!tf_type.string>} : () -> tensor<!tf_type.string>

@ArunaKote ,
Please feel free to move this issue to closed status and please submit a new issue from this link and fill in the template, so that we can track the issue there. Thanks!


RouDi terminating application not via SIGTERM (because of EINTR)

Brief feature description
When roudi is terminating applications it sends a SIGTERM to the application.
This comes with the following problems:

When the application does not have a signal handler registered it is terminated without cleaning up its resources. Resources like named semaphores, shared memory, files are then remaining and may lead to misbehavior when the application is restarted
When the application has registered a signal handler it can happen that the application is waiting in a blocking call. This blocking call is returning then with EINTR but since the common suggestion is to recall the posix call when this signal comes, the application remains in that blocking call.  So RouDi will kill the application after 30 seconds with SIGKILL which again may lead to resource leaks or even worse, the application continues after the blocking call and access non available shared memory resources which lead to a segfault or undefined behavior.

Detailed information
When one thinks about it, RouDi does not need to terminate the application but it has to ensure that the applications runtime is destroyed. One could rewrite the posh runtime so that the user is informed that RouDi requests a termination and only when this request is ignored RouDi calls SIGKILL.
It could look like:
auto runtime = iox::posh::createRuntime();
// ...
while( !runtime.isTerminationRequested() ) {
  // do sending and receiving stuff
}

// here the runtime could be recreated if a reconnect to roudi is wished.

// as alternative, useful when one uses the listener
runtime.waitForTerminationRequest();

cc @elBoberido

@elfenpiff this goes into the direction @budrus and me once had in mind https://github.com/eclipse-iceoryx/iceoryx/issues/615#issuecomment-815636049
The big question would be how this is communicated. Via a flag in shared memory? Via an IPC channel? If the latter, then we need a maintenance thread, which we currently also have because of the keep alive and the unblocking of the potentially blocked publisher.


[Stable Diffusion] Add Stable Video Diffusion export and inference support

Export

optimum-cli export neuron --model stabilityai/stable-video-diffusion-img2vid-xt --task stable-video-diffusion --batch_size 1 --height 576 --width 1024 --auto_cast matmul --auto_cast_type bf16 sd_video_neuron/

Inference on Inf2

from diffusers.utils import load_image, export_to_video
from optimum.neuron import NeuronStableVideoDiffusionPipeline

pipe = NeuronStableVideoDiffusionPipeline.from_pretrained("Jingya/stable-video-diffusion-img2vid-xt-neuronx")

image = load_image("https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/diffusers/svd/rocket.png?download=true")
image = image.resize((1024, 576))

frames = pipe(image, decode_chunk_size=8, motion_bucket_id=180, noise_aug_strength=0.1).frames[0]
export_to_video(frames, "generated.mp4", fps=7)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!


deleted old graphs, renamed low, edited accessibility graph, and crea…

…ted new graph

Looks good.


how to ignore a catch statement?

try {

} /* istanbul ignore next */ catch (err) {

}

Not sure if this is a question or a statement. Closing, please re-open if there is an issue.

I think it was a question - how do you ignore a catch statement?  The posted code doesn't work.

Got it - you ignore the code within the catch statement, not the catch statement itself. So:
try {
    //...
} catch (error) {
    // istanbul ignore next
    //...
}

@rpaterson This gets a bit tedious if I have for example a pattern to log and throw the error. I have to add a comment before both lines, instead I could say // istanbul ignore catch to ignore the catch altogether.

That sounds great - could you post a code example?

@rpaterson Sorry I confused you with with the collaborator, there is more recent issue with more details. #361

try {
//...
} catch (error) /* istanbul ignore next */ {
//...
}


Add Reverse Text Block

This PR adds a new Reverse block to the text section of the built-in blocks.
Demonstration of the block using the Do It function:

@conorshipp Do you want to resolve the conflicts here and provide the test so that we can get this merged?

@ewpatton sure. I've been having issues with the unit tests on my PC (as you saw on the community) and haven't had the chance to look into it yet. Still need to test the combining characters you mentioned too.

@conorshipp I must have missed it. Can you point me in the right direction?

@ewpatton here's the community topic. You did reply :smiley:

@conorshipp #2044 has been merged and we have merged master into ucr. You should be able to rebase this change to bring it current.

@ewpatton please look at the unit test and let me know if that's what you're looking for. I'm not very familiar with unit tests so I'm not exactly sure how to write them but it was successful so I think it's right 🤷♂

@conorshipp Yeah that's good enough for now. We'll probably need to add more if issues crop up (especially around multiple code point characters).

@ewpatton can you think of any way to make this work with Emojis? If not, would it make sense to update the documentation to state that Emojis won't work properly?

@conorshipp I'll need to do some experimentation to find out.

@conorshipp The commit I just pushed implements a unicode-aware string->list function*. Because the emojis are in the part of Unicode plane that needs code surrogates to encode them, reversing puts all the pairs in the wrong order. This new string->list function swaps the surrogates so that when they are reversed the chars will be in the correct order.

@ewpatton @conorshipp Put an additional set of eyes/tests on the unicode-aware change, and it looks good to me.


python27Packages.hdbscan: 0.8.24 -> 0.8.25

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python2.7-hdbscan/versions.
meta.description for python27Packages.hdbscan is: "Hierarchical Density-Based Spatial Clustering of Applications with Noise, a clustering algorithm with a scikit-learn compatible API"
meta.homepage for python27Packages.hdbscan is: "https://github.com/scikit-learn-contrib/hdbscan"
Updates performed:

Version update

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.8.25 with grep in /nix/store/cxc9g2jaf58r7jwy62ckdmqq3khbph3y-python2.7-hdbscan-0.8.25

directory tree listing: https://gist.github.com/40407efaf5e7fbb4b3fa8d164fd99f8b

du listing: https://gist.github.com/568977082dd153765ea7b4830b5257d5

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)
3 package rebuild(s)
3 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
python27Packages.hdbscan
python37Packages.hdbscan
python38Packages.hdbscan

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cxc9g2jaf58r7jwy62ckdmqq3khbph3y-python2.7-hdbscan-0.8.25 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python27Packages.hdbscan https://github.com/r-ryantm/nixpkgs/archive/ab30516fec2d0f51859156ae92121f013855710c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cxc9g2jaf58r7jwy62ckdmqq3khbph3y-python2.7-hdbscan-0.8.25
ls -la /nix/store/cxc9g2jaf58r7jwy62ckdmqq3khbph3y-python2.7-hdbscan-0.8.25/bin

cc @ixxie for testing.

@GrahamcOfBorg eval


Prepare rollouts for 2024-02-21

Azure Boards WorkItem

helix-machines rollout is still in progress as we are waiting for increase quota requests to be approved

Ricardo is giving follow up in: https://github.com/dotnet/dnceng/issues/1850


Fix moditect and jar building for module enhancements

all tests passing hmm
only linux vs windows paths in tests

remember if jdk 15 is JAVA_HOME then --preview won't work for a jdk 14 profile -
That's why i created the JDK 15 one as well

pls merge so i can delete the fork - need the fork for some other things on the project :)


Allow this to be installed on python3.7

Summary
The tooling appears to work fine on python3.7 and the tox / github actions tests target 3.7 so this should be "safe". As currently published, you cannot install this package on python3.7 environments:
$ pip install aws-msk-iam-sasl-signer-python==1.0.0
ERROR: Ignored the following versions that require a different python version: 1.0.0 Requires-Python >=3.8
ERROR: Could not find a version that satisfies the requirement aws-msk-iam-sasl-signer-python==1.0.0
ERROR: No matching distribution found for aws-msk-iam-sasl-signer-python==1.0.0

Testing Done
Verified producing and consuming works from py3.7
$ cat confluent_msk_producer.py
from aws_msk_iam_sasl_signer import MSKAuthTokenProvider
from confluent_kafka import Producer
import time

producer = Producer({"bootstrap.servers": "the-bootstrap-server-string", "security.protocol": "SASL_SSL", "sasl.mechanism": "OAUTHBEARER", "oauth_cb": lambda x: MSKAuthTokenProvider.generate_auth_token("us-west-2")})
while True:
 msg = "Sending from py3.7"
 print(msg)
 producer.produce('dpopes-iam-1', msg)
 time.sleep(1)
 producer.flush()

[...]

$ python confluent_msk_producer.py
Sending from py3.7
Sending from py3.7
Sending from py3.7
Sending from py3.7
Sending from py3.7
^CTraceback (most recent call last):
  File "confluent_producer.py", line 10, in <module>
    time.sleep(1)
KeyboardInterrupt

$ cat confluent_msk_consumer.py
from aws_msk_iam_sasl_signer import MSKAuthTokenProvider
from confluent_kafka import Consumer
import time

consumer = Consumer({"bootstrap.servers": "the-bootstrap-server-string", "security.protocol": "SASL_SSL", "sasl.mechanism": "OAUTHBEARER", "oauth_cb": lambda x: MSKAuthTokenProvider.generate_auth_token("us-west-2"), "group.id": "mygroupid"})
consumer.subscribe(['dpopes-iam-1'])
while True:
 msg = consumer.poll(1)
 if msg:
  print("running on py37 received: {}".format(str(msg.value())))

[...]
$ python confluent_msk_consumer.py

running on py37 received: b'Sending from py3.7'
running on py37 received: b'Sending from py3.7'
running on py37 received: b'Sending from py3.7'
running on py37 received: b'Sending from py3.7'
running on py37 received: b'Sending from py3.7'
^CTraceback (most recent call last):
  File "confluent_consumer.py", line 8, in <module>
    msg = consumer.poll(1)
KeyboardInterrupt

Related Issues
https://github.com/aws/aws-msk-iam-sasl-signer-python/issues/20
PR Overview

[ n ] This PR requires new unit tests [y/n] (make sure tests are included)
[ n ] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[ y ] This PR is backwards compatible [y/n]
[ n ] This PR changes the current API [y/n]

Check https://github.com/aws/aws-msk-iam-sasl-signer-python/issues/20
Marking this as closed. Please re-open if there are concerns


[Refactor] Input class breakup

RTCV.UI.Input.Input is a class which has some types/classes defined inside of it. This generally isn't in good form, and violates CA1034.
This change moves some types/classes defined inside of RTCV.UI.Input.Input to their own files.
This change will likely break dependants, so I'm listing this as a draft until we have a stronger CI validation pipeline.

RTC input is only used for hotkeys so I don't think this'll actually cause any issues.


Fix typo in getFavicon docs

Description
This PR fixes a typo in the getFavicon docs page.

Thanks for the fix, could you open the PR against main instead 🙂

@pernielsentikaer my bad! not sure why GitHub decided to use gh-pages as the base branch by default. Here's it is https://github.com/raycast/extensions/pull/8687


create more first class sync protocol that should improve speed, logging, and allows for a progress bar CORE-6063

Patch does the following:
1.) Adds two new NotifyRouter RPCs, ChatInboxSynced and ChatInboxSyncStarted. ChatInboxSyncStarted lets all listeners know that the service is going to sync against the server. This allows the UI to render a blue bar.
2.) ChatInboxSynced sends up a result similar to what Gregor gives the service, with three possible states given the outcome: CLEAR, CURRENT, or INCREMENTAL. CLEAR and CURRENT are implemented straightforwardly in JS, and INCREMENTAL triggers a new action inboxSynced.
3.) inboxSynced causes the JS to run GetInboxNonblock in a special mode where it does not deliver the untrusted inbox, since that data is already available from the ChatInboxSynced call.  It then updates the inbox in the normal way, and marks any affected threads as stale for the purposes of calling GetThreadNonblock on them.
The main tangible result here is that now when foregrounding the mobile app, we get a nice blue bar indicating that the sync is happening, so there is less confusion form the user foregrounding.

@chrisnojima ok PTAL, thanks!


Unexpected behaviours during startup

Description:
When you set the game to use Borderless Fullscreen and close the game, the window's behaviour during startup is a bit annoying. It cannot be minimized, it takes a long time before it responds, and your screen becomes locked to it. Would it be possible to disable Borderless Fullscreen during startup? :)
Steps to reproduce:

Start Minecraft, enable Fullscreen
Exit Minecraft
Start Minecraft

Versions:

Minecraft Version: 1.15.2
Forge Version: 1.15.2-31.1.63
Mod Version: borderless-1.15.2-1.0.0

Actually this might be default Minecraft behaviour, my bad ^^' The fullscreen behaviour is exactly the same with the mod as without.

Yeah, I think this is something related to Minecraft or Forge when a lot of mods are loaded. The window just hangs up and does not respond, even the native fullscreen will crash if you tab out or try to interact with the window.
I will have a look at it anyway and try if there is something I can do to avoid this problem.

The update made the window behaviour more consistent imo, thank you :)


Switch endpoint is now DRM encrypted

Describe the bug
Not properly a bug, the streams now available on the /console endpoint is now DRM encryped
To Reproduce
Download a video or audio and enjoy beautiful rainbow flashes
Client (please complete the following information):

OS: Windows
Version: crunchy-cli 3.6.6

Additional context
The problem is that program not support self-providing a wvd so now is unusable

Duplicate of #438

@hajimekun I'm sorry for changing the title/text, I thought OMA was a type. Apparently not, I just never heard of it


GPU Memory-Usage Control

Refering to the issue in Project mmdetection-to-tensorrt Multiple batch for one inference was support now. cool ~
However, GPU Memory-Usage will be increased when using multiple batch ( GPU Memory Usage is a tough problems in some project ) . So,  how to control the Memory-Usage and then  keep  GPU Memory-Usage As low as possible ?
is it any params could be set in it ?

Dynamic input shape did need more memory. If your input image have a fix shape, such as 800*1088, set the opt_shape_param as  follow should reduce memory usage:
    opt_shape_param=[
        [
            [1,3,1088,800],
            [2,3,1088,800],
            [4,3,1088,800],
        ]
    ]

max_workspace_size is the temporary space used to do the inference. Some tactics might need a large workspace. Reduce it can also save some memory with the cost of potential accelerate.
I will try optimize my plugin see if I can use less workspace.


License Requirements

You mentioned Microsoft 365 Business and other which now have Conditional Access. And all now have access to Preview Baselines for Conditional Access. So this wording and guidance should change. In reality, this portal should be merged to AAD if possible.

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

ID: 4cb129d2-9594-bf0c-5946-982f0ed0d888
Version Independent ID: 6522b038-6853-3552-55c8-f174cf56573d
Content: Azure Multi-Factor Authentication user states - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-userstates.md
Service: active-directory
Sub-service: authentication
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@MicrosoftGuyJFlo Could you please provide your thoughts on this , if we can update the article or add a small note to reflect the licenses section since the feature is in Preview at the moment ?

And Microsoft 365 Business now have full Conditional Access policies now, not even the baselines.

It is still a method people can use so the doc will remain. The doc references the Conditional Access method and links to the doc for that.

@MicrosoftGuyJFlo: It is correct that this content is still there. Because lot of people does not understand the states. But the wording should be changes in some places. Like: "This is the method used for those with either Office 365 or Microsoft 365 Business licenses as they do not include Conditional Access features. which is not correct these days, because Microsoft 365 Business contain Conditional Access.

Done. PR should publish later this afternoon.

#please-close


build task

Checks and bundles all configured modules (bundles option).
Implementation tasks:

[x] rename check to build
[x] rename --ci to --check
[x] add bundle option to build task
[x] bundle all bundles, unless --ci is used
[ ] if --check is used, do these steps:

ensure the cwd is a clean git repository
run the build task
check git for changes
if repository is clean, succeed
else reset and fail

#55 now tracks the final part and this can be closed.


Create Bundles of Products

When a Bundle is added to an Order, the Order creates OrderItems with the
appropriate product/project pair.

Add admin API for create/update of Bundles

 Code Climate has analyzed this pull request.

@sonejah21 It sounds like you might be the person to chat with about the front end for this. Is there anything obviously missing here?

@calebthompson - looks good to me!

Cool. @stackus care to take another glance? I'm adding API docs for BundlesController now.


🐛 Bug Report: Unable to use the Helm chart to deploy an instance

📜 Description
I'm trying to setup Backstage on a Kubernetes cluster, using this documentation : https://demo.backstage.io/docs/default/Component/backstage/getting-started/deployment-helm/
The Helm chart for the PostgreSQL dependency doesn't seem to exist anymore.
From what I've seen in the git history (more specifically here : https://github.com/backstage/backstage/commit/0e91c38450d1190fba36dcd355b53221ae8b238d), the version of the PostgreSQL instance was rolled back from a 11.x version to the current version specified in the backstage Chart (11.2.4 => 9.8.12), because of

I am reverting this because this was a breaking change and needs more work and testing.

I tried on the master branch of the backstage repository, and also on the latest tag (v1.14.0), and the behavior is the same.
👍 Expected behavior
The helm dependency update should complete successfully :
➜  backstage git:(v1.14.0) ✗ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ingress-nginx" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈

➜  backstage git:(v1.14.0) ✗ helm dependency update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ingress-nginx" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading postgresql from repo https://charts.bitnami.com/bitnami
Deleting outdated charts

👎 Actual Behavior with Screenshots
Result when executing helm dependency update :
➜  backstage git:(v1.14.0) ✗ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ingress-nginx" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈

➜  backstage git:(v1.14.0) ✗ helm dependency update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ingress-nginx" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
Error: can't get a valid version for repositories postgresql. Try changing the version constraint in Chart.yaml

As we can see, this version of the postgresql Helm chart doesn't exist anymore :

➜  backstage git:(v1.14.0) ✗ yq -P '.dependencies[] | select(.name=="postgresql")' Chart.yaml
name: postgresql
condition: postgresql.enabled
version: 9.8.12
repository: https://charts.bitnami.com/bitnami

➜  backstage git:(v1.14.0) ✗ helm search repo 'bitnami/postgresql' --version 9.8.12

No results found

👟 Reproduction steps
git clone https://github.com/backstage/backstage.git
cd contrib/chart/backstage
helm dependency update

📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Hi @Seb147, sorry you ran into problems. I would highly recommend using the Documentation from https://backstage.io/ and not the Demo site. This is the current docs for Kubernetes deployment but it doesn't use Helm: https://backstage.io/docs/deployment/k8s. There is now an official Helm chart here though: https://github.com/backstage/charts

I wonder if we should move this issue to the charts repo instead? :pray:

Thanks for your reply @awanlin, I have other issues with this one, but at least I'm able to deploy an instance :)

You're welcome. I'm a little confused, what does"I have other issues with this one" mean?


<EMAIL_ADDRESS>results in a "register is not a function" error on page load

Reproduction
see #Reproduction section
Describe the bug
When upgrading or installing @formkit/nuxt to a server-side rendered nuxt project, I get following error:
[nuxt] [request error] [unhandled] [500] __vite_ssr_import_9__.register is not a function   at Module.defaultConfig (./node_modules/@formkit/vue/dist/index.mjs:2106:27)     at ./virtual:nuxt:/project-dir/.nuxt/formkitPlugin.mjs:12:46     at ./node_modules/nuxt/dist/app/nuxt.js:114:60     at fn (./node_modules/nuxt/dist/app/nuxt.js:162:44)     at Object.callAsync (./node_modules/unctx/dist/index.mjs:68:55)     at ./node_modules/nuxt/dist/app/nuxt.js:164:56     at Object.runWithContext (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3855:18)     at callWithNuxt (./node_modules/nuxt/dist/app/nuxt.js:164:24)     at Object.runWithContext (./node_modules/nuxt/dist/app/nuxt.js:34:29)     at applyPlugin (./node_modules/nuxt/dist/app/nuxt.js:114:39)
Reproduction
Currently I tried to reproduce it in a new project, but it feels like it has to do with SSR.
When the error page is rendered, and I click on a client-side redirect link, everything works good.
Solution
When I remove line

node_modules/@formkit/vue/dist/index.mjs:2089
node_modules/@formkit/vue/dist/index.cjs:2109
node_modules/@formkit/vue/dist/formkit-vue.js:10167

The problem does not occur anymore.
Environment
• OS: macOS
• Browser Chrome
• Version any

FormKit package: formkit/nuxt
Affected versions: 1.2.0 - 1.2.2

Hmm. im unable to duplicate this issue. Anything else you can provide reproduction wise?


feat: TFRecords for Pets.

As a first step for #35 we need the TFRecords first.

The TFRecords are here: gs://pets-tfrecords/pets-tfrecords.
@deep-diver could you review the latest changes once?

Sure! Expect a bit of delay on my side (a day or so)

@deep-diver can we merge this?


Switching  to  and then using  does not work well

Replicate:
Neotree buffers: shows buffers, this is ok.
Neotree toggle: does not toggle, instead it opens the filesystem view, not ok.
Alternative:
Neotree buffers
Neotree close
Neotree show: does not open back in buffers, it opens in filesystem.

Closing this as solved.


Heroku client internal error

Just trying to simply login to heroku on the command line and create an app.  When typing "heroku login" on the command line, I'm asked for my email and password, and then I get the error below.  I have installed the Heroku Toolbelt and I'm using a mac osx 10.8.2.  I also noticed that I am unable to access these 2 pages on Heroku in my browser:  https://api.heroku.com/login and https://help.heroku.com/.  I'm sure it's a simple problem, but any help would be greatly appreciated.  Thanks.
$ heroku login
Enter your Heroku credentials.
Email: xxxxx
Password (typing will be hidden):
!    Heroku client internal error.
!    Search for help at: https://help.heroku.com
!    Or report a bug at: https://github.com/heroku/heroku/issues/new
Error:       Connection refused - connect(2) (Errno::ECONNREFUSED) (Excon::Errors::SocketError)
Backtrace:   /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/socket.rb:41:in `connect'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/socket.rb:41:in `block (2 levels) in connect'
             /usr/local/heroku/ruby/lib/ruby/1.9.1/timeout.rb:68:in `timeout'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/socket.rb:40:in `block in connect'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/socket.rb:29:in `each'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/socket.rb:29:in `connect'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/ssl_socket.rb:77:in `connect'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/socket.rb:16:in `initialize'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/ssl_socket.rb:8:in `initialize'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/connection.rb:364:in `new'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/connection.rb:364:in `socket'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/connection.rb:192:in `request_kernel'
             /usr/local/heroku/vendor/gems/excon-0.16.10/lib/excon/connection.rb:103:in `request'
             /usr/local/heroku/vendor/gems/heroku-api-0.3.7/lib/heroku/api.rb:74:in `request'
             /usr/local/heroku/vendor/gems/heroku-api-0.3.7/lib/heroku/api/login.rb:9:in `post_login'
             /usr/local/heroku/lib/heroku/auth.rb:80:in `api_key'
             /usr/local/heroku/lib/heroku/auth.rb:189:in `ask_for_credentials'
             /usr/local/heroku/lib/heroku/auth.rb:221:in `ask_for_and_save_credentials'
             /usr/local/heroku/lib/heroku/auth.rb:84:in `get_credentials'
             /usr/local/heroku/lib/heroku/auth.rb:41:in `login'
             /usr/local/heroku/lib/heroku/command/auth.rb:31:in `login'
             /usr/local/heroku/lib/heroku/command.rb:207:in `run'
             /usr/local/heroku/lib/heroku/cli.rb:28:in `start'
             /usr/bin/heroku:24:in `<main>'

Command:     heroku login
Version:     heroku-toolbelt/2.33.5 (x86_64-darwin10.8.0) ruby/1.9.3

Error:       Connection refused - connect(2) (Errno::ECONNREFUSED) (Excon::Errors::SocketError)
Command:     heroku login
Version:     heroku-toolbelt/3.42.20 (x86_64-darwin10.8.0) ruby/1.9.3
Let you know if you guys can help please...

@gsanjeevkumar are you able to visit https://api.heroku.com/login ?  It sounds like the user that previously reported this issue may have had network problems.

@ransombriggs I can login to the URL you sent. what are the settings for the network are necessary/required i am behind a fire-wall.
Thanks in advance.

Export HTTP_PROXY and HTTPS_PROXY then try again.

@gsanjeevkumar ^^^ (just making sure you get notified)


Cannot find implementation of Algorithm 1 and sensing matrices

I have read the Deep Compressed Sensing paper and the TensorFlow implementation of it in the csgan folder, but I was not able to find the implementation of Algorithm 1 from the paper. I want to reproduce the results of Table 2 and 3, but I cannot find a sensing matrix anywhere in the implementation, I can only find a neural network being used to measure the signal. Could you let me know where can I find the random sensing matrix and how can I reproduce the results reported in Table 2 and 3?

Hi, the random sensing matrix is not here, but you can easily write one. For example,
sensing_matrix = snt.TrainableVariable(
shape=mat_shape,
initializers={'w': tf.initializers.random_normal},
name='F_matrix')() / self._output_size
You can then control whether to further train this matrix or not from downstream to reproduce all the results in Table 2 and 3.

This worked, thank you!


base-files: sync default smack rules with tizen

Tizen development added these rules.
Applications running with label System should have
accesses to user areas protected by labels User::Home
and User::App:Shared.
Change-Id: I30d4654f0d3354bfd960421e0131449db86f434a
Signed-off-by: José Bollo<EMAIL_ADDRESS>

Instead of closing one PR and creating another, please force-push new commits onto the same branch.
Regarding the "transmute" flag: how does that interact with the corresponding flag on the actual directories? Do home directories already have it (haven't checked) or don't need it?

About the push force, yes, I recalled me that it could be used but too late.
About directories, yes, they should have the transmute flag.
/home/user should be labelled User::Home with Transmute = TRUE
Please check the spec file of tizen-platform-config: https://review.tizen.org/gerrit/gitweb?p=platform/core/appfw/tizen-platform-config.git;a=blob;f=packaging/tizen-platform-config.spec;h=f00316f01ecec3826182f091b1f94809bca9452d;hb=860acd4ba5fc945b102ec925e0e243e1092a721b

On Tue, 2016-01-05 at 07:24 -0800, jobol wrote:

About directories, yes, they should have the transmute flag.
/home/user should be labelled User::Home with Transmute = TRUE

Then please augment your PR so that it extends
meta-security-smack/recipes-core/base-files/base-files_%.bbappend
accordingly. The transmute flag is currently missing there.

Keeping PRs that are WIP slow down CI. I'm closing it for now. @jobol please reopen before force-pushing any commits, otherwise Github will not allow you to reopen.

Bad news: I made a push force.... I had not really understood the issue thus I'll rework on it now.


[WIP] Temp change to get output html zip

Summary
THIS IS JUST FOR DEBUGGING
I have temporarily disabled Warnings being treated as errors in order to have it create the doc artifacts here so I can see what is coming out from CI.
Details and comments

The artifact here shows the generated is being all lower case now with hypens replacing non-alpha chars so links do not match. Also as it now lowercase's Table of Contents to table-of-contents it triggers a css style to hide such a section. In the end, for reasons that we already have a TOC in the right sidebar and that refs to title text are discouraged (fragile around any edits to title text and keeping all refs uptodate with that) #1180 sorts things out better. As this was just to see the outcome of CI to guide things forward it has served its purpose so closing.


Formatting option on data label

After #33  is implemented using chartjs-plugin-datalabels plugin it seems i am now missing an option to format the data label.
It seems to be supported by the plugin itself : https://chartjs-plugin-datalabels.netlify.app/guide/formatting.html#multiline-labels
I can workaround this need currently by truncating the data itself , but not it is not always to workaround this way, so it should be possible with this package someday.
Thanks in advance.

I know that because I'm trying to implement this functionality. I'll keep you posted.

I added a callbacks for Title and Labels. You can see the demo page here
I'll release the NuGet package tomorrow

Is it working? Can I close the issue?

Hi , Can't check it now ,  I will check it on the start of next week and let you know.
Thanks for your efforts so far.

Hi
Just tested the new nuget (6.0.40) and i think there a little mistunderstanding.
It Seems you handled the tooltip data , while i was referring to the the label on the graph it self, here is a screenshot of my graph :

As you can see i want to format the label on the bar graph it self , not the tooltip.
Let me know if i missed something.
Thanks again for your time and efforts.

I need this change too, for the DataLabels object.
Thanks!

const workingHoursSummaryChart = new Chart(workingHoursSummaryEle.getContext('2d'), {
type: 'bar',
data: {
labels: ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'],
datasets: [{
label: 'Month',
data: [80, 60, 70, 140],
borderRadius: 8,
borderWidth: 1,
barPercentage: 1.15,
borderSkipped: false,
backgroundColor: ['#E8ECF1', '#E8ECF1', '#E8ECF1', '#1A4573', ],
borderColor: ['#E8ECF1', '#E8ECF1', '#E8ECF1', '#1A4573', ],
datalabels: {
color: ['#0B1D30', '#0B1D30', '#0B1D30', '#1A4573'],
anchor: 'end',
align: 'top',
font: {
size: '12px',
weight: '600',
family: 'Nohemi'
},
},
}]
},
plugins: [ChartDataLabels],
options: {
responsive: false,
maintainAspectRatio: false,
plugins: {
legend: {
display: false
},
datalabels: {
display: false,
formatter: (value) => {
return value + 'hrs';
}
}
},
layout: {
padding: {
top: 30,
}
},
scales: {
y: {
display: false,
offset: true,
},
x: {
reverse: false,
grid: {
display: false
}
}
}
}
});

This code in JavaScript


Bypass Local IP

Hello,
If "bypass Chinese IPs" option is turned off, I can not access local IPs such as:
192.168../16 and etc.

it need to be on.

it need to be on.

I am not in China. So I don't need to bypass Chinese IPs.


ReconciliationApi: make fromScheme optional

At https://github.com/gbv/cocoda-sdk/blob/6f48fce4b4c174b4f6355d55ae50c97c21e8f2cc/providers/reconciliation-api-provider.js#L55 we could remove testing from fromScheme. Setting from.inScheme to [ {} ] works anyway, so there is no reason to have fromSchem except for copying it into the result mappings.
We could further make to.inScheme optional and set it to schemes[0] if the registry has exactely one scheme, so this should work:
const registry = cdk.initializeRegistry({
  provider: "ReconciliationApi",
  reconcile: "...",
  schemes: [ theScheme ]
})
registry.getMappings({ from: { prefLabel: { en: "label" } } })

toScheme will already fall back to schemes[0]. I can remove the check completely, but if someone did something like you described, the resulting mappings would basically be invalid (no fromScheme).
I will also take a closer look at the code, I'm not sure whether it needs to be as complicated as it is.


Econnfrefused for Signal Notification

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem

I have the latest uptime-kuma and signal-cli-rest-api versions both installed with docker.
I successfully linked my signal device by scanning the qr code from curl http://localhost:8080/v1/qrcodelink?device_name=signal-api --output $HOME/signal/signal_qr_code.png
I get a successful response from running curl -X POST -H "Content-Type: application/json" 'http://localhost:8080/v2/send' -d '{"message": "Test via Signal API!", "number": "+NUMBER", "recipients": [ "+NUMBER" ]}' amd I even get the message on my signal app.
However, in the Uptime-Kuma interface, when I add the Signal notification with POST URL http://localhost:8080/v2/send I get a pop-up saying Error: Error: connect ECONNREFUSED <IP_ADDRESS>:8080

The uptime-kuma instance runs on the same server as the site. I did this in the past, on the same VPS, and it worked. So if running curl from the VPS works, it's strange that uptime-kuma does not.
📝 Error Message(s) or Log
Error: Error: connect ECONNREFUSED <IP_ADDRESS>:8080
🐻 Uptime-Kuma Version
1.23.1
💻 Operating System and Arch
Ubuntu 22.04
🌐 Browser
LibreWolf
🐋 Docker Version
Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1
🟩 NodeJS Version
n/a

You need to put both containers into a same network.
https://stackoverflow.com/questions/42385977/accessing-a-docker-container-from-another-container

@louislam
I don't recall doing that on the previous install I did 6 months ago, but I just gave that a shot. I have run,
sudo docker network create uptime_kuma_network
sudo docker network connect uptime_kuma_network e77588d929bc
sudo docker network connect uptime_kuma_network c0a70ce03240
sudo docker container restart e77588d929bc c0a70ce03240

, then refreshed the webpage, and I get the same error.

I think using localhost would only work if you are using the host networking mode in docker. Have you tried using <IP of the Signal container>:8080 instead?

@chakflying
Thanks a ton!
I replaced the POST URL with the signal-api container's IPv4 address, 172.X.X.X, gotten from sudo docker network inspect uptime_kuma_network and it works!

Hello,
You could use your docker container name
http://signal-cli-rest-api:8080/v2/send


DD-356: Log unrecognized srsName

Fixes DD-356
Description of changes

adds error handling for addCompoundFieldMultipleValues in DepositToDataverseMapper
spatial scheme is validated for spatial elements

How to test

run dd-dans-deposit-to-dataverse with a spatial element where the spatial scheme is erroneous.  There should be error logged and the element does not come into Dataverse.

Related PRs
(Add links)
*
Notify
@DANS-KNAW/dataversedans

Closing PR; I'll review the logging approach more broadly.


Move knowledge of last accessed prefs to LastAccessedPrefManager

Refactoring only.
I moved all knowledge of "last accessed" preferences into a private class inside LastAccessManager, cleaning up all the places that were setting the last accessed preference, as well as removing unnecessary methods from PrefManager.
I also auto-formatted these files, ignore whitespace: https://github.com/edx/edx-app-android/pull/775/files?w=1
Reviewers
If you've been tagged for review, please check your corresponding box once you've given the :+1:.

[ ] Code review: @BenjiLee
[ ] Code review: @mdinino

Is this a pre cursor to any ticket in this sprint? jw

Is this a pre cursor to any ticket in this sprint?

Nope, feel free to consider this low priority.  Last updated by [00a1787...40a463b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/edx/edx-app-android/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/edx/edx-app-android/compare/00a178714798807708b44440f388dab1f9aeea49...40a463bd54664af4416654a8bbf85f8d8fe91e87?src=pr
[cc-pull]: https://codecov.io/gh/edx/edx-app-android/pull/775?src=pr

What sort of manual tests did you do to prove that there were no regressions? What tests should I do?

👍

👍

@bguertin I tried rebasing but there were some conflicts. I think all of your changes is what we want, but I'm not comfortable with doing the rebase myself.

Updated / rebased, going to merge if tests still pass


[MINOR] Remove unused guava import

What changes were proposed in this pull request?
PR #181 removed guava dependency in LivyServer, but it still left unused guava import. Here in this minor fix, removed this unused import.
How was this patch tested?
Existing UTs.

Codecov Report

Merging #191 into master will decrease coverage by 0.24%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #191      +/-   ##
============================================
- Coverage     68.71%   68.47%   -0.25%
+ Complexity      908      906       -2
============================================
  Files           100      100
  Lines          5674     5674
  Branches        854      854
============================================
- Hits           3899     3885      -14
- Misses         1219     1231      +12
- Partials        556      558       +2

Impacted Files
Coverage Δ
Complexity Δ

...ala/org/apache/livy/utils/LineBufferedStream.scala
80.48% <ø> (ø)
5 <0> (ø)
:arrow_down:

...ain/scala/org/apache/livy/utils/SparkYarnApp.scala
73.23% <0%> (-6.34%)
33% <0%> (ø)

...in/java/org/apache/livy/rsc/driver/JobWrapper.java
82.85% <0%> (-5.72%)
8% <0%> (-1%)

...cala/org/apache/livy/scalaapi/ScalaJobHandle.scala
52.94% <0%> (-2.95%)
7% <0%> (ø)

.../scala/org/apache/livy/sessions/SessionState.scala
58.33% <0%> (-2.78%)
2% <0%> (ø)

...ain/java/org/apache/livy/rsc/driver/RSCDriver.java
77.96% <0%> (-0.85%)
41% <0%> (ø)

...main/scala/org/apache/livy/server/LivyServer.scala
35.46% <0%> (+0.49%)
11% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

CC @runzhiwang


Error "Unexpected error fetching multimatic_facility_detail data: list index out of range"

Hi,
I've been succesfully using your Multimatic integration for several months. Yesterday, I noticed that the integration did show only 2 entities (quick mode and holiday). I checked the Multimatic app on my phone to confirm the problem is not on the Vaillant side.
In the system log, I found the error message in the title.
Below is the full detail of the error.
There haven't been any changes on my setup or configuration. My HASS system is fully up to date.
Can you please advise what I can do.
Thanks and best regards.
Kristiaan
Logger: custom_components.multimatic.coordinator
Source: custom_components/multimatic/coordinator.py:97
Integration: Multimatic (documentation, issues)
First occurred: 20:02:05 (1 occurrences)
Last logged: 20:02:05
Unexpected error fetching multimatic_facility_detail data: list index out of range
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 283, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 242, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/multimatic/coordinator.py", line 566, in _first_fetch_data
result = await self._fetch_data()
^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/multimatic/coordinator.py", line 554, in _fetch_data
return await getattr(self.api, self._method)()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/multimatic/coordinator.py", line 97, in get_facility_detail
detail = await self._manager.get_facility_detail(self.serial)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pymultimatic/systemmanager.py", line 261, in get_facility_detail
return mapper.map_facility_detail(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pymultimatic/model/mapper.py", line 273, in map_facility_detail
facility = [
^
IndexError: list index out of range

Another error, occuring every 2 minutes (=update frequency), and I guess it is the consequence of the above issue, is:
Unexpected error fetching multimatic_quick_mode data: Cannot get https://smart.vaillant.com/mobile/api/v4/facilities/##MYSERIALNUMBERr##/systemcontrol/v1/configuration/quickmode, status: 400, response: {"errorCode":"INVALID_PARAMS"},payload: None

Hi there, I have a similar error. I´m using a dedicated user for Home Assistant.

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.multimatic.coordinator
Source: custom_components/multimatic/coordinator.py:158
Integration: Multimatic (documentation, issues)
First occurred: 03:01:23 (10 occurrences)
Last logged: 03:19:50
Unexpected error fetching multimatic_hvac_status data: Cannot get https://smart.vaillant.com/mobile/api/v4/facilities/2122290020260962093XXXXXXXXX/hvacstate/v1/overview, status: 503, response: Service Unavailable,payload: None
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 283, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 242, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/multimatic/coordinator.py", line 562, in _fetch_data_if_needed
return await self._fetch_data()
^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/multimatic/coordinator.py", line 554, in _fetch_data
return await getattr(self.api, self._method)()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/multimatic/coordinator.py", line 158, in get_hvac_status
return await self._manager.get_hvac_status()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pymultimatic/systemmanager.py", line 43, in wrapper
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pymultimatic/systemmanager.py", line 252, in get_hvac_status
return mapper.map_hvac_status(await self._call_api(self.urls.hvac))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pymultimatic/systemmanager.py", line 84, in wrapper
raise ex
File "/usr/local/lib/python3.11/site-packages/pymultimatic/systemmanager.py", line 80, in wrapper
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pymultimatic/systemmanager.py", line 902, in _call_api
response = await self._connector.request(method, url, payload)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pymultimatic/api/connector.py", line 181, in request
raise ApiError(
pymultimatic.api.error.ApiError: Cannot get https://smart.vaillant.com/mobile/api/v4/facilities/2122290020260962093XXXXXXXXX/hvacstate/v1/overview, status: 503, response: Service Unavailable,payload: None

Hello, vaillant server was not recheable this night (on my side) from 3:00 to 4:54

no problem with integration i think

Update:

I uninstalled and reinstalled the integration, with the same results.
The unavailability of the Vaillant server as mentioned by lecocqe is certainly not the reason for the issue I logged.
I'm not sure that the reaction by 85Kid above is the same issue.
Hopefully Thomas Germain can clarify the issue and indicate how to resolve.

Hello @kverbeke, did you try to reload the integration ?
Do you have any other errors ? The error you mentioned only affect few entities, so you should definitely have other entities if this is the only error you have.
The error means there is no installation for your serial number. Did you provide your serial number or did you let the integration find it ?

@lecocqe having the same error today.

You think it was down again?

@thomasgermain :
I've now readded the hub WITHOUT filling in the serial number, and this works correctly.
Thanks for your support!


Changed the  Charset from WebUtils.DEFAULT_CHARACTER_ENCODING to Charset.defaultCharset() to support UTF-8

Currently this is not supporting the special characters as the default encoding is ISO-8859-1.
Changed the default charset from WebUtils.DEFAULT_CHARACTER_ENCODING to Charset.defaultCharset() to include support for UTF-8.

@chsraju Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@chsraju Thank you for signing the Contributor License Agreement!

Mater is not in compile state


Added Python Dockerfile

Congrats on taking the first step to contributing to the Sample Programs in Every Language repository!
For simplicity, please make sure that your pull request includes one and only one sample program and language.
Please Complete the Following

[ ] I would NOT like credit for my contribution in the article (credit will be included otherwise)
[ ] I plan to write the article for this code snippet
[ ] I named the pull request using <Sample Program> in <Language> format
[ ] I created/updated the language README

[ ] I added the sample program name to the README
[ ] I added fun facts (i.e. debut, developer, typing, etc.)
[ ] I added reference link(s) to the README

[x] I fixed #285

Notes
@nicovillanueva, I was wondering if you could help me understand Dockerfiles a little bit. I've grabbed the Python file from https://github.com/dockerfile/python, and I was wondering what else I might need to do to get this working.

Sure!
Think of Dockerfiles as Chef cookbooks, or Ansible playbooks. They define how the environment inside an image should look, and therefore, how containers should come up. They allow scripts/apps to run with the exact same environment in your machine, as in mine.
The Dockerfile you copied installs Python within an Ubuntu. In the resulting image, you have a working Python installation, ready to run your scripts.
Say you do a docker build -t jrg94/my-python $locationOfDockerfile. You'll then have an image called jrg94/my-python:latest (if you don't specify a version, it defaults to latest). To run your scripts, you should give them to the container. One simple way is to do: docker run -i -t --volume $whereTheScriptsAre:/data/ --entrypoint bash jrg94/my-python:latest
This means: Run my image, with a pseudo-tty attached (-t), attach my stdin to it (-i), mount this folder in my machine into /data in the container (--volume) and drop me into a bash session in it --entrypoint). Then, you'll be able to run them via terminal as usual, but from within a container.
That is the manual, non-automatizable way. There are loads of ways to achieve this, and optimizations to do. For example, Dockerfiles support what you could call "inheritance" (you can build upon previously built images, as to reuse code); or you could bake the scripts into the image, and run them upon creation (instead of dropping interactively into a shell, just run them directly).
Dockerfiles are super powerful, while being relatively simple. They support only 17 instructions, but for example, one of the newest is HEALTHCHECK: For long running apps, you can define how to determine if your app is up or not, and if it should be restarted after N seconds/retries.
Want to give it a shot and tell me how it goes/ask me any doubts you may have?

Sure, I'll give it a shot. I'd be interested in automating the testing a little bit, so they Dockerfile would essentially build an image that would run on the scripts in the same folder. That way, people could quickly see the output.

Maybe I'm missing something here, but why is Docker even required here? Isn't it enough to just run the scripts directly?

Of course! That said, I'm interested in creating sort isolated environments. If you have to use Python 2 on your machine or whatever but you still want to play around with the solutions in this repo, you can launch a Docker image to keep your system clean.
Obviously, it doesn't make a ton of sense with Python, but this is a change I'd like to make repo-wide.

Alright, I managed to get Docker running successfully after a couple tweaks (running Windows 10).
docker run -i -t --volume /e/Projects/sample-programs/archive/p/python/:/data/ --entrypoint bash jrg94/my-python:latest
I don't see my files, however.

Hmm, it seems the mounting is working, but my files aren't showing up.

Apparently, my e drive wasn't mounted properly. The solution works as expected! :) Now, my problem is with the Game of Life solution:
root@90e5c148cdf6:/data# python3 game-of-life.py
Traceback (most recent call last):
  File "game-of-life.py", line 2, in <module>
    from tkinter import *
ModuleNotFoundError: No module named 'tkinter'


renderRichText() not working

Describe the issue you're facing
I have simply a blok, that has a content, markdown input, when i debug this, it returns the classic markdown like this: # Some random md. I want to pass the content to the renderRichText(), but it keeps to showing me the Cannot read properties of undefined (reading 'some') error. Maybe i'm doing something wrong, please correct me if thats the case. I always want to write code as much clean as possible. I minimalized the error on stackblitz.
Reproduction
https://stackblitz.com/edit/nuxt-starter-pxajvf?file=pages%2Findex.vue
Steps to reproduce
Just call the renderRichText(), with some text markdown.
System Info
System:
    OS: Linux 6.2 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
    Memory: 6.64 GB / 15.37 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
    npm: 10.0.0 - ~/.nvm/versions/node/v18.17.1/bin/npm
  Browsers:
    Chrome: 118.0.5993.88

Used Package Manager
npm
Error logs (Optional)
500
chunk-UJJZ7LWV.js:1552 [Vue warn]: Error in mounted hook: "TypeError: Cannot read properties of undefined (reading 'some')"

found in

---> <Article> at /path_to_the_project/storyblok/Article.vue... (1 recursive calls)
       <Anonymous>... (1 recursive calls)
         <AsyncComponentWrapper>
           <Anonymous>... (1 recursive calls)
             <RouteProvider>... (1 recursive calls)
               <NuxtPage>
                 <NuxtLayoutProvider>
                   <NuxtLayout>
                     <App> at /path_to_the_project/app.vue
                       <Root>

Validations

[X] Follow our Code of Conduct

I just tried doing so with <StoryblokComponent :blok="blok.content" /> ,it does not return the error, but the markdown is still not loaded.

Oh, my mistake, i mistook markdown with richtext.


feat!: Java 8 breaking generator changes

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/d9958105-2c81-4042-8726-6edc37113f51/targets

[ ] To automatically regenerate this PR, check this box. (May take up to 24 hours.)

PiperOrigin-RevId: 388535346
Source-Link: https://github.com/googleapis/googleapis/commit/d9eaf41de44d953458b18712a3f240bb4c564e48
PiperOrigin-RevId: 388499329
Source-Link: https://github.com/googleapis/googleapis/commit/bb0a090d9204110042ab5dee2ce9e06e8071ce54

Fixed various clirr breakages.


Split out terminal printing code for third party subcommands

It'd be great if the terminal printing code were extracted to a separate crate so that third-party Cargo subcommands could have consistent output with mainline Cargo.

This looks nice and straightforward (on paper at least).
How happy are we extract out this API?

From #6079

Hej there
I recently extracted the shell API into its own repo at ysndr/shell-rs for easier usage in my own projects.
I wonder if it's desired to maintain cargo's shell API externally as well in this repo as part of the rust-lang-nursery to offer the advantages of a multiplatform, colored, customizable stdoutwrapper to the whoel community.
Please excuse if this is the wrong place to ask for this I just did'nt know a better place.

Oh that has been quite a while ago though I'm happy it seems getting noticed finally.
I don't even know if that approach is still compatible with the current state of cargo, but happy to take a look as time permits.

Cargo is now a Cargo workspace, so perhaps it doesn't need to be an external repo but a workspace member!


A way to reject partial parses

Some rules in my grammar have constraints that there should be no whitespace between adjacent elements (some also have the constraint that there should be no newlines, but we can ignore that for now).  Is there a good way to handle that sort of thing with Marpa?  If there was a way to reject the completion of certain rules during parsing that would be simple.
The first alternative I see is to explicitly represent the possibility of whitespace in the grammar, but to do that without introducing huge ambiguity seems to mean I have to do the Aycock & Horspool nihilist normal form (NNF) transformation on my raw grammar, so I don't introduce whitespace recognition on both sides of a nulling symbol.  Since Marpa is surely already doing that analysis, it feels wasteful to implement it myself.
The second alternative is to ignore the whitespace constraints until the parse forest is complete and then reject any complete parses that violate the constraints, but that seems inefficient, since many parses may be explored that could have been rejected earlier, and there's no way, once a constraint violation is detected in a complete parse, to avoid checking other complete parses that contain the same partial parse that violated the constraint.

For context, the EBNF source of my grammar (which I'm converting mechanically into MARPA rules) is in the ebnf markdown blocks here—search for the string "(no-" to find the special rules that don't implicitly allow whitespace.
Regarding the whitespace-preceded lexemes idea:

I don't understand “when these are recognized they can be treated as you ish, for example as an error.”  I certainly don't want to cause an error when they are recognized by the lexical analyzer.  Where and how do you propose I treat them as an error?

In most places I need to accept the lexemes whether or not they're preceded by whitespace, so I'd end up defining nonterminals like
 colon -> ws-colon
 colon -> no-ws-colon

and using “colon” almost everywhere.  Not the end of the world, but not great either.

If you look at  the places where  these constraints are expressed, it's not in terms of lexemes at all, and it's not in terms of what-precedes, but what's-between.  Automatically rewriting the rules in terms of these ws-prefixed lexemes is as much work as the NNF transformation I'd have to do to avoid ambiguity with my current strategy, and I've already coded the NNF transformation once—I don't even know what the rewrite for your suggestion would look like.

With regard to explicit representation of whitespace: no, it needn't be ambiguous, but the naïve approach I currently have of interjecting optional space tokens into the rules between every symbol does cause a lot of ambiguity in fact.  Any nullable symbol surrounded by a pair of "any amount of whitespace" (AAoW) symbols will cause whitespace to be parsed ambiguously in that position, as either part of the first AAoW symbol or the second.  That's why I would need the NNF transformation; to avoid adding these AAoW symbols around nullable symbols.
I don't think I understand what your experience suggested.  Is there an automated transformation for it that I can apply to my specification?

I did my work on explicit whitespace as research, possibly toward an automated transformation, but I abandoned the idea in favor of the "discard" lexeme approach.
My idea was, for those lexemes which do not allow preceding whitespace, to define "error lexemes", which consist of that lexeme preceded by whitespace.  If you see one of these, you know someone has put whitespace in the wrong spot and handle it accordingly.  You only need define such "error lexemes' for the cases where whitespace is, indeed, an error.
In correct input, you won't see any "error lexemes".

Sure… but I don't have any lexemes that are defined to not allow preceding whitespace, and it's not clear to me that the grammar I am encoding can be represented in those terms.

Re "I don't have any lexemes that are defined to not allow preceding whitespace" in https://github.com/jeffreykegler/libmarpa/issues/117#issuecomment-1155651116, my comments were attempting to be responsive to this from https://github.com/jeffreykegler/libmarpa/issues/117#issue-1271065763:

Some rules in my grammar have constraints that there should be no whitespace between adjacent elements

I understand that.  What I'm saying is that the whitespace restrictions in my grammar rules are expressed in terms of the LHS nonterminal being recognized, not in terms of the participating lexemes.  You could of course rewrite the grammar to attach those restrictions to lexemes, but that would be a massive rewrite that I don't know how to do mechanically.
At this point it is starting to look like I should switch to my own implementation of the algorithms, because I can easily add the necessary functionality.

Any objection to closing this issue?

🤷 I don't think my problem's been addressed; in case it wasn't clear, I think the fact that I don't have a solution means I'm going to stop using MARPA. The only reason I can see for leaving the issue open would be if you intended to do something about it, but it sounds as though you don't.  If I've understood correctly, closing it would be appropriate.

Tomorrow I'll look this issue over and try to see what  I have missed.  Is there a write-up somewhere of your requirement or something similar?
The decision which parser to use belongs to the users, and I try to take from these choices what I can for Marpa, and otherwise to respect the user's choice and not to take it personally.
In case I don't get another opportunity, I want to thank you for all these issues.  They include insightful editing suggestions and the detection of an obscure but serious bug.  It will take me weeks to work through all these.  The API doc will be significantly better.  Marpa will be significantly improved by the time you've spent here.

You're welcome, and thank you for the work you've done here.  If it turns out I switch implementations I hope I can keep asking you questions?  If so, what's the best medium?

Best to communicate via a Github issue where it's a specific issue on a repo, and via the IRC channel otherwise.
One reason I may have seemed reticent is that I am avoiding the issue of "futures".  I do have my own ideas for new directions, which may include things like undoing bits of parsing already done.  None of these are things you'll see in the next few weeks.

I mean questions regarding what MARPA does internally, and why, rather than anything about its future direction.
I'd particularly like an answer to the first question in this comment.

I took a closer look at the Val doc.  What does the (no-whitespace) signify in the following?
module-definition ::= (no-whitespace)
  whitespace-opt module-body whitespace-opt

It's an EBNF notation I have not seen before.  Naively, it seems to say "no whitespace, but yes optional whitespace at the beginning".

Is it a meta-notation saying that the lines are not tokenized, but neither is the lexical whitespace in the text to be taken literally, instead it is indicated via symbols like whitespace-opt?

Yes exactly. The name is badly chosen; it should be (no-implicit-whitespace)
Sent from my iPhone

On Jun 15, 2022, at 8:03 PM, Jeffrey Kegler @.***> wrote:

Is it a meta-notation saying that the lines are not tokenized, but neither is the lexical whitespace in the text to be taken literally, instead it is indicated via symbols like whitespace-opt?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

On Jun 17, 2022, at 8:51 AM, Jeffrey Kegler @.***> wrote:
@dabrahams https://github.com/dabrahams OK. I looked over the Val doc.
Re the "go ambiguous then prune" approaches. I've done some work in creating tools for these, but the IF is not documented in Libmarpa, although it is in Marpa::R2 (as the ASF interface) for Perl users. I'm not enthusiastic about its chances because my work with general parsing has given me an enormous respect for exponential growth --- creating an ambiguous ASF, then pruning, is likely to be expensive.

ASF?
I don’t think that’s true for my particular case, because of both top-down parsing and where the ambiguity occurs in my grammar.  However, I wouldn’t dare make such a claim for the general case, which is what you must be concerned with as the library maintainer.

I'll say more if you want, but here I'll move on to an approach that does not exploit ambiguity.
Reading the Val doc, I see its EBNF as having two kinds of rules -- tokenized and explicit (the (no-whitespace) rules). That EBNF could be translated for Marpa by making every rule "explicit". This might be done automatically by inserting optional whitespace between every symbol in the tokenized rules.

That’s what my EBNF->BNF translator already does.  You can see that if you look for “spacer” in https://github.com/val-lang/val/blob/parser/Sources/ParseGen/BNF.swift https://github.com/val-lang/val/blob/parser/Sources/ParseGen/BNF.swift
As mentioned several times earlier, however, this creates ambiguity when optional whitespace is inserted around nullable symbols.  That’s why I keep mentioning doing the nihilist normal form (NNF) transformation; it would allow me to avoid inserting optional whitespace on both sides of a nullable symbol.
Moreover I very strongly suspect that in the case of my grammar, even if I continue with this transformation, the amount of overall processing caused by treating whitespace as a token, and nearly doubling the length of most rules’ right-hand sides, would far outweigh the cost of rejecting a possible scan here and there.

Some notes:
1.) To reduce ambiguity, non-medial (initial and final) whitespace should be avoided in the explicit rules.

That won’t help with the problem I’m seeing; only the very top-level rule has non-medial whitespace in it and I could easily eliminate that by pre-trimming whitespace on the input.  That’s not what’s causing the issue in my case.

I'd be tempted to outright ban non-medial whitespace in explicit rules, but introduce a (raw) meta-notation to override the ban for those users who believe that they know what they are doing.
2.) The top rule obviously requires some sort of special treatment, because initial and final whitespace is necessary to express many useful grammars, and no ambiguities arise.
3.) Then there is the "weeknights" problem. How to avoid the ambiguity with reading it as the two identifiers "wee knights"? The longest acceptable token method, which always goes for "weeknights" is the naive approach, is native to Marpa::R2, and will cover almost all cases. But there may be corner cases, and useful apps for which hacks are needed.

I don’t think I’m having that problem.  My tokenizer (https://github.com/dabrahams/citron/blob/master/Sources/CitronLexerModule/Scanner.swift https://github.com/dabrahams/citron/blob/master/Sources/CitronLexerModule/Scanner.swift) currently already takes the longest acceptable token (it’s the standard lexer approach for programming languages).

This is like the approach I was investigating when I decided to go with the "discard symbols" alternative. I did this because:
1.) I thought the "discard" approach would be easier to explain. I didn't have the idea of mixing explicit and tokenized rules, which does make things more natural on the notation side.
2.) I thought working out all the corner cases, and providing workarounds, might be quite the project, possibly aggravating 1).
3.) I was nearly 100% sure the discard approach would work -- it was very closely related to what lexers had been doing for decades. The explicit whitespace approach had fewer parallels in practical experience. Those who pioneer unsuccessful approaches in a sense contribute as much as those who try the successful approaches, but I was not eager to be one of the former.
I hope you find this useful.

It gives me a more detailed understanding of why you don’t want to change libmarpa APIs to help solve my problem.  I hope it’s clear that’s a choice I never begrudged you in the first place, though!  In terms of helping me actually solve the problem I have, I’m afraid it doesn’t do much: unless I’m misunderstanding, you’re still catching up with the essential nature of the problem I’m having.
What would be really helpful to me, at this point, is if you would let me take you on a walkthrough of my implementation of MARPA’s essentials—as I understand them—so I can see what I’ve missed.  It’s only a few hundred lines of code in Swift (https://github.com/val-lang/Lotsawa https://github.com/val-lang/Lotsawa) and I can explain anything you may not understand.

ASF = Abstract Syntax Forest.  This is an alternative evaluation interface developed under Marpa::R2 which uses the bocage to directly traverse the forest of parses.  The standard valuator allows parses to be iterated one by one, but if you want to deal with all of an exponential number, that's often not adequate.  The ASF allows you to prune the forest, elimnating potentially huge numbers of possibilities with each step.
To implements its ASF, Marpa::R2 violates the Libmarpa API, using Libmarpa calls which are currently not documented.

This discussion meandered quite a bit, and has gone off line.  @dabrahams: Do you have any objection to my closing this?

none

Absent feedback to the contrary, and as per https://github.com/jeffreykegler/libmarpa/issues/117#issuecomment-1172931615, I will close this issue after a couple of days.

Closed per https://github.com/jeffreykegler/libmarpa/issues/117#issuecomment-1172985511.


Bounding boxes are not coming accurate

Hi,
I'm getting the following image as the result on visualizing 3D bounding boxes after evaluation using pretrained models. I've used car_lite. I've evaluated the model on the training set itself. Is there anyone facing similar issues or has anyone come across with a possible workaround? Thanks!

@themousepotato
Check your coordinate system transformation, including the lidar, camera and vehicle local system by visualization before training.
From the pic you shared, the problem should be on the training side, not just the inference side.

@xmyqsh sure, will do. But, I'm not doing any training. I've used the pretrained models given in the README which reproduces the published results. I downloaded from this link from that description.

@themousepotato You can solve this problem with your toe :)

@xmyqsh I'm really sorry. I couldn't get much info from your statements. Do you mean that it is a bug in the codebase, I need to fix it and train from scratch? Also, I didn't quite get the testing coordinate system part. Kindly elaborate. That would help me a lot. Thanks.

Also, is there any chance that the spconv module is not working properly (at least in my local setup)?

ping @xmyqsh

I have a similar issue when using the nuscenes dataset #350
How can I improve this this?

Looking from the image, The coordinate system of the training data is not same as the inference data


GPLv2 license compatibility

Apache is incompatible with GPLv2. Could you dual license it under GPLv2 or MIT?

Yes, that's doable. How would I do that? Can you show me an example repo with dual license?

Found this.
https://github.com/sfackler/rust-postgres-macros/issues/19
https://github.com/sfackler/rust-postgres-macros/pull/20/files

Thanks, will change to dual license soon.

And done. Dual licensed under Apache v2 or LGPL v2.1.


Language Mismatch in Dispatch Section Popup Notifications After Status Update

Describe the bug
When changing the language on the Enatega Food Delivery site and navigating to the dispatch section to update the status of an order, the popup notifications continue to appear in the previous language. This inconsistency can lead to confusion for users, as notifications should reflect the selected language throughout the entire user journey.
To Reproduce
Steps to reproduce the behavior:

Change the language setting on the Enatega Food Delivery site.
Navigate to the dispatch section.
Update the status of any order.
Observe the language of the popup notification.

Expected behavior
Popup notifications in the dispatch section should be displayed in the currently selected language, providing a consistent user experience.
Screenshots
https://github.com/ninjas-code-official/food-delivery-multivendor/assets/152266796/d16a2408-aef4-4536-a4dc-40949003ca43
Desktop:

Browser: chrome

GitHub repository "food-delivery-multivendo" is not publicly accessible due to a 40x error, I will provide a general step-by-step guide to help you address the language settings issue in an open-source project like the Enatega Food Delivery site. Here is a generic approach you can follow:
Step-by-Step Guide to Address Language Settings Issue:
Identify Language Configuration Files:
Locate the files responsible for managing language settings in the project. These files typically contain language translations and configurations.
Check Language Change Functionality:
Verify that the language change functionality is correctly implemented and triggers the necessary updates throughout the application.
Inspect Popup Notification Component:
Examine the component responsible for displaying popup notifications, ensuring it retrieves and displays text based on the selected language.
Update Language in Popup Notifications:
Modify the code within the popup notification component to dynamically update the language of notifications based on the user's language selection.
Testing:
Test the application thoroughly after making changes to ensure that popup notifications now reflect the selected language consistently.
Localization Testing:
Conduct localization testing to confirm that all text elements, including popup notifications, are correctly translated and displayed in the chosen language.
User Feedback:
Gather feedback from users to validate that popup notifications now align with their selected language preference.

It's working fine from our side as repo is publically available so anyone can clone and contribute with us. And secondly you can also tell us the error you are facing and we will help you with that.

GitHub repository "food-delivery-multivendo" is not publicly accessible due to a 40x error, I will provide a general step-by-step guide to help you address the language settings issue in an open-source project like the Enatega Food Delivery site. Here is a generic approach you can follow: Step-by-Step Guide to Address Language Settings Issue: Identify Language Configuration Files: Locate the files responsible for managing language settings in the project. These files typically contain language translations and configurations. Check Language Change Functionality: Verify that the language change functionality is correctly implemented and triggers the necessary updates throughout the application. Inspect Popup Notification Component: Examine the component responsible for displaying popup notifications, ensuring it retrieves and displays text based on the selected language. Update Language in Popup Notifications: Modify the code within the popup notification component to dynamically update the language of notifications based on the user's language selection. Testing: Test the application thoroughly after making changes to ensure that popup notifications now reflect the selected language consistently. Localization Testing: Conduct localization testing to confirm that all text elements, including popup notifications, are correctly translated and displayed in the chosen language. User Feedback: Gather feedback from users to validate that popup notifications now align with their selected language preference.

It's working fine from our side as repo is publically available so anyone can clone and contribute with us. And secondly you can also tell us the error you are facing and we will help you with that.

Tested by QA.


Added safe method for PID file creation

This PR adds a safe method for handling PID file creation in the edge worker provider packages.
It ensures that in the edge worker CLI ...

.... orphaned PID files are removed before writing the current PID file
... two EdgeWorker instance that are miss-configured with the same PID file path are overwriting each others PID information

Uuups it seems the PR was closed implicitly because I deleted the MVP Branch... was not my intent to close the PR :-D
Maybe as we are on apache/airflow: main now we need to make the branch -> PR to apache upstream directly?

Hello @jscheffl , based on the closing of this PR, I already anticipated your suggestion and did a direct upstream PR:
https://github.com/apache/airflow/pull/43153


Add "get folio payment report" endpoint.

Also, some attempt to normalize the request/response types for the various
folio reports: charge/credit, payments.
[#133973615]

Self-reviewing due to Patrick's weekend


Vibrate for duration (Android)

Change vibrate({Duration duration : _DEFAULT_VIBRATION_DURATION}) to accept optional parameter duration for Android devices. Throw UnsupportedError on iOS if duration has been passed.
Dart 2.0 compatibility
Add custom duration to example app

Sorry, didn't check the existing pull requests.
As well I changed Platform.operatingSystem == "ios" to Platform.isIOS in my fork. In case you accept the pull, please change that as well. Thanks.


Migration to Typescript & ES6 Classes

This library rocks. ❤
I've been using voxel.js for a while now but it seems to be abandonware at this point. Noa is absolutely amazing and has a lot of potential.
In my opinion the only thing holding this project back is lack of documentation & examples. I hope to contribute in this area over the next few months.
Step 1: Migrate & add jsdocs to main lib files [This PR]
Step 2: Add dat-gui
Step 3: Migrate & add jsdocs to component files
Step 4: Establish some build tooling like a code formatter, tests, and using github actions to deploy noa-examples on each commit
Step 5+: Add to existing markdown docs to live playground examples using codesandbox.io
I've spent the last few weeks converting the main library code over to ES6 classes and typescript.
You will see a night and day difference in IntelliSense. I've been using this typescript version for the past few weeks and the development experience is amazing.
I've updated a large number of jsdoc comments and documented some undocumented features/options along the way. Also fixed a few dozen bugs that came up when type checking was enabled. A large number of any types are still being used, these can be iterated on in the future. Some of these are because implicit typing is lacking due to dependent libraries not having types (integrating work like Miguel's would be helpful here).
Here are some of the changes in this PR:

lib files are now in typescript
now that a build tool is being used es6+ features can be used while still supporting legacy browsers
latest module support. This library is now compatible with tree shaking
added a large number of new jsdocs, updated existing docs (they will only appear in editors when comments start with /**, some instances were using /*)
documented all options for each library component. This includes the default options
documented emit/on handlers
converted some modules to use local class property settings instead of settings in the constructor. The advantage of this is it allows usage of tools like dat-gui without having to reset the engine

Please let me know of any feedback.
Closes #85

Is there an ETA on when this will be merged with the dev branch? I have been converting a project that uses this to typescript and this would be super useful.

Hi, sorry for the delay on this. Have a lot going on currently, and I have not yet done all the work that would be needed for me to try out this work. I'll merge it into its own branch instead, so that people can build against if if they like, and so that I can eventually test it side-by-side with the develop branch.
(always nervous about editing PRs, hopefully this works as expected..)