Unable to install in a Vue 3 app

Describe the bug
A clear and concise description of what the bug is.
After,  npm install i try npm i vue-advanced-chat
node_modules/vue
<EMAIL_ADDRESS>from the root project

Could not resolve dependency:
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/vue-advanced-chat
  vue-advanced-chat@"*" from the root project

Steps to reproduce
This is my package.json
    "@popperjs/core": "^2.10.2",
    "@sentry/tracing": "^6.13.3",
    "@sentry/vue": "^6.13.3",
    "@vueform/multiselect": "^2.2.0",
    "@vueform/slider": "^2.0.5",
    "aws-sdk": "^2.1062.0",
    "bootstrap": "^5.1.3",
    "core-js": "^3.6.5",
    "firebase": "^9.0.2",
    "vue": "^3.0.0",
    "vue-router": "^4.0.0-0",
    "vuex": "^4.0.0-0",
    "webpackbar": "^5.0.0-3"
  },```

## Expected behavior

It is mentioned that the chat is compatible with Vue3, so it should be install with `npm i vue-advanced-chat` without any issues

Answering my own question, apparently it works with
    "vue-advanced-chat": "https://github.com/antoine92190/vue-advanced-chat/tarball/next",


e2e: Carve out a helper function creating a source mesh participant

This PR contains a tiny refactors of e2e_pod_client_server_test.go to carve out a function setupSource(), which creates the source pod.
This introduced a boolean flag, which controls whether we create a Kubernetes Service for the source pod (or not).
No functional code changes in this PR (except for the addition of if withKubernetesService {)
This is a step forward towards making an end to end test for https://github.com/openservicemesh/osm/pull/1932

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [X]
CI System              [ ]
Performance            [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?

Codecov Report

Merging #1951 into main will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1951      +/-   ##
==========================================
- Coverage   58.45%   58.44%   -0.02%
==========================================
  Files         131      131
  Lines        5284     5284
==========================================
- Hits         3089     3088       -1
- Misses       2192     2193       +1
  Partials        3        3

Impacted Files
Coverage Δ

pkg/envoy/route/config.go
95.23% <0.00%> (-0.80%)
: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 b45ab46...ba0bb04. Read the comment docs.


As a user I want to be able to have an account that I can log into

@mhmcvay should this be closed since merging #29 ?


Gsoc'21 Fix the bug in changing modes

Related Issue
There was a bug in changing modes like when user switched to dark mode
Light Mode is ok but when i switched to dark mode It creates a problem because i am not able to see the content written in form because it is of black color.
I had solved this issue and added a form tag which was previously missing
Closes: #[84]
Describe the changes you've made
It should change to White color when dark mode is activated and change to black color when light mode is activated so i added some css to it.
I am attaching a video for better understanding my improved code
Type of change
What sort of change have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Mention any unusual behaviour of your code (Write NA if not)
Any unusual behaviour of your code
Additional Info (optional)
Any additional information you want to give
Checklist:

[ x] My code follows the guidelines of this project.
[ x] I have performed a self-review of my own code.
[x] I have commented my code, particularly whereever it was hard to understand.
[x] My changes generate no new warnings.
[ ] Any dependent changes have been merged and published in downstream modules.

I hope Its fine. please add label of gsoc'21 before merging.

@ankitapuri mam please check this I hope It is fine

ok sir let me try..

Hello @adarshvulli sir I had tried to do all the changes you mentioned above
Changes Done.

Light bulb is now in the middle (in perfect position)
The background color is changed a little bit in dark-mode , now its visible perfectly.
Currently i am working on reducing the size of light bulb in phone view but it's very complicated to me as there are a lot of CSS mixing up taking for now i had maintain some margin so that it doesn't look bad

I am attaching a video for better understanding the changes i had done ...Please Review it
https://user-images.githubusercontent.com/55352601/111948323-fd41a580-8b04-11eb-9b68-2477c6d93ede.mp4
**Note: Please ignore the size of light bulb for now i am working on it if i success i will make a PR in future as i created this issue related to the bug in changing modes **

Sir kindly merge this PR then I will Fork the Latest Code and start Working on Reducing size of light bulb because I had also created a issue(#83) about Responsiveness yesterday . So i can also work on this issue under that Issue(#83) if it is assign to me.

Sir Please add labels of gssoc'21 before merging.

@ankitapuri mam sorry to disturb you , but I didn't get any score for it and This issue and PR is not showing in my gssco  profile.
Can you please check it what went wrong so I can take care of it in future.

@ankitapuri mam sorry to disturb you , but I didn't get any score for it and This issue and PR is not showing in my gssco profile.
Can you please check it what went wrong so I can take care of it in future.

I have asked the organizers once . will update u about it


381 Add SLURM + Singularity example link to our document

Fixes #381 .
Description
This PR added the SLURM + Singularity MONAI example link to our document.
Status
Ready
Checks

[ ] Notebook runs automatically ./runner [-p <regex_pattern>]

Hi @rijobro ,
Could you please help review this PR? @wyli is PTO now.
Thanks.


v4 planning

[ ] Make ID generator and validator generic, implement transformer (mirror asgi-correlation-id)
[ ] Split celery functionality into a separate package
[ ] Split sentry functionality into a separate package
[ ] Create extras for both
[ ] Update license
[ ] Update test project to handle Django deprecation warnings
[ ] Update to Poetry v1.2
[ ] Update classifiers
[ ] Rework docs (drop sphinx and just have readmes per module?)

Essentially we want to de-bloat the core a little, making it possible to install the core middleware without anything else. It's possible to install the middleware today, without adding celery as a dependency, but the celery code is still contained in the wheel.
There's also some Sentry + Celery logic to consider @JonasKs. Do we put that in its own third package? Something to think about 🤔

How do you feel about the get_guid, set_guid helpers @JonasKs?

Get rid of them imo

asgi-correlation-id doesn't have a UUID_LENGTH package setting. Instead it's a filter option. Should we do that here as well?


Error due to unicode ?

Hello
I'm unable to run your script, i think is due to characters problem ?
See my attatchment

Windows build version:  18362.295
Thanks

Hello!
Did you save .ps1 file in "UTF-8 with BOM" encoding as I mentioned in the article?

Hmm, yeah okay i miss to change UTF-8-BOM with latest downloaded script.
Thanks you


A fatal exception occurred.

Greetings!
I attempted to use the OPUS-CAT Tool but it seems that something is wrong with the file I have downloaded. Or then again I might be doing something wrong. Do you have any ideas on countering this issue?

Hi,
This is related to the file database that OPUS-CAT uses to cache translated sentences (so that they can be generated in advance). For some reason, the database is in readonly state when OPUS-CAT is trying to edit it. This should normally be resolved by restarting the system, but if it reoccurs, something else is going on. It might be that the user permission setup on your system is somehow strange (the database is stored in your %localappdata% folder, and you should always have permissions for that).
You should be able to bypass the problem by disabling the database caching by editing the config file OpusCatMTEngine.exe.config (in the MT engine folder that you have unzipped). Search for this bit of code:
<setting name="CacheMtInDatabase" serializeAs="String">
               <value>True</value>

and change True to False:
<setting name="CacheMtInDatabase" serializeAs="String">
               <value>False</value>

I'll log this a bug, the caching should probably be disabled automatically in these cases.


Codeigniter example ui fixes

The example had hard coded URL's .
Fixed by using codeigniter's site_url helper. This will make it easier to run the example in MAMP and wamp where the example cannot be in the root

thanks


python312Packages.tencentcloud-sdk-python: 3.0.1253 -> 3.0.1255

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.tencentcloud-sdk-python
python311Packages.tencentcloud-sdk-python.dist
python312Packages.tencentcloud-sdk-python
python312Packages.tencentcloud-sdk-python.dist


Prevent from loading documents that are not images.

If the URL does not return an image do not try to load at all.

Merged! Thanks a lot Damien.


error Conditional Compilation

https://github.com/HaxeFoundation/hscript/blob/master/hscript/Bytes.hx

We've seen this as part of Issue #29.  The current parser strategy is to ignore the preprocessing tokens and expect the rest of the code to be correct.  This is wrong in a number of cases.  However, trying to ignore one half or the other (before or after the #else), also leads to errors with completion, import statements, refactoring, and other places.

BTW, on build <IP_ADDRESS>.TiVo.ClassHierarchy.11, the error is "expected [...] got ;"

Already fixed

Released in 0.11.0


#95: don't load empty staging config file

Closes #95

To my eye it looks like loading an empty staging config file is causing a warning that may become an error down the road. This PR comments out the part that loads this file.
If you have another solution in looking, feel free to adjust.

Do we know whaa the warning is?

Its in the original ticket:
[14-Apr-2023 09:56:10 UTC] PHP Warning:  Use of undefined constant WP_ENVIRONMENT_TYPE - assumed 'WP_ENVIRONMENT_TYPE' (this will throw an Error in a future version of PHP) in /code/wp-content/mu-plugins/the-world-site-config/configs/production/production-config.php on line 19

Pushed up a change that should keep the files being included while fixing the PHP warning.


Add accessibility

https://github.com/openedx/openedx-app-ios/assets/128456094/daad2adb-9237-45fe-93c3-864036ae7f97

Thanks for the pull request, @IvanStepanok!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

Good to merge in imo from product perspective we can do future incremental improvements after deeper reviews

Good to merge for now.
Feedback will be addressed in future PRs.

@IvanStepanok 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


Change v9.0+ to v0.9+

Version 9.0 seems to be too far ahead.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a379fa0). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #245   +/-   ##
=========================================
  Coverage          ?   90.62%
=========================================
  Files             ?       25
  Lines             ?     1450
  Branches          ?        0
=========================================
  Hits              ?     1314
  Misses            ?      136
  Partials          ?        0

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 a379fa0...741e7ce. Read the comment docs.


Fixing Count flag usage string

Previously Count flag usage would look something like this:
  -v, --verbose count[=-1]        verbosity

This is  confusing as it seems that default value would be -1 while in fact -v would result in value 1.
Also I'd argue that -1 as special value meaning "to increment" was just wrong. :-)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Bug in contrib/tensor_forest/python/tensor_forest_test.py

My environment is Win7 x64, python 3.5, tensorflow r1.0 GPU version.
I download contrib/tensor_forest/python/tensor_forest_test.py and run 'python test.py' in console.  Then the following error information shows:
..E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\co
re\framework\op_kernel.cc:943] OpKernel ('op: "BestSplits" device_type: "CPU"')
for unknown op: BestSplits
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "CountExtremelyRandomStats" device_t
ype: "CPU"') for unknown op: CountExtremelyRandomStats
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "FinishedNodes" device_type: "CPU"')
for unknown op: FinishedNodes
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "GrowTree" device_type: "CPU"') for
unknown op: GrowTree
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "ReinterpretStringToFloat" device_ty
pe: "CPU"') for unknown op: ReinterpretStringToFloat
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "SampleInputs" device_type: "CPU"')
for unknown op: SampleInputs
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "ScatterAddNdim" device_type: "CPU"'
) for unknown op: ScatterAddNdim
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "TopNInsert" device_type: "CPU"') fo
r unknown op: TopNInsert
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "TopNRemove" device_type: "CPU"') fo
r unknown op: TopNRemove
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "TreePredictions" device_type: "CPU"
') for unknown op: TreePredictions
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core
\framework\op_kernel.cc:943] OpKernel ('op: "UpdateFertileSlots" device_type: "C
PU"') for unknown op: UpdateFertileSlots
.EEEEE.
ERROR: testInferenceConstruction (main.TensorForestTest)
Traceback (most recent call last):
File ".\test.py", line 90, in testInferenceConstruction
graph = graph_builder.inference_graph(input_data)
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 459, in inference_graph
**inference_args))
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 958, in inference_graph
valid_leaf_threshold=self.params.valid_leaf_threshold)
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\o
ps\gen_tensor_forest_ops.py", line 662, in tree_predictions
name=name)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\op_def_librar
y.py", line 763, in apply_op
op_def=op_def)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
2397, in create_op
set_shapes_for_outputs(ret)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1757, in set_shapes_for_outputs
shapes = shape_func(op)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1707, in call_with_requiring
return call_cpp_shape_fn(op, require_shape_fn=True)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 610, in call_cpp_shape_fn
debug_python_shape_fn, require_shape_fn)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 670, in _call_cpp_shape_fn_impl
status)
File "F:\Anaconda3\lib\contextlib.py", line 66, in exit
next(self.gen)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\errors_impl.p
y", line 469, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.NotFoundError: Op type not registered 'T
reePredictions'
======================================================================
ERROR: testInferenceConstructionSparse (main.TensorForestTest)
Traceback (most recent call last):
File ".\test.py", line 143, in testInferenceConstructionSparse
graph = graph_builder.inference_graph(input_data)
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 459, in inference_graph
**inference_args))
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 958, in inference_graph
valid_leaf_threshold=self.params.valid_leaf_threshold)
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\o
ps\gen_tensor_forest_ops.py", line 662, in tree_predictions
name=name)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\op_def_librar
y.py", line 763, in apply_op
op_def=op_def)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
2397, in create_op
set_shapes_for_outputs(ret)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1757, in set_shapes_for_outputs
shapes = shape_func(op)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1707, in call_with_requiring
return call_cpp_shape_fn(op, require_shape_fn=True)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 610, in call_cpp_shape_fn
debug_python_shape_fn, require_shape_fn)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 670, in _call_cpp_shape_fn_impl
status)
File "F:\Anaconda3\lib\contextlib.py", line 66, in exit
next(self.gen)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\errors_impl.p
y", line 469, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.NotFoundError: Op type not registered 'T
reePredictions'
======================================================================
ERROR: testTrainingConstructionClassification (main.TensorForestTest)
Traceback (most recent call last):
File ".\test.py", line 58, in testTrainingConstructionClassification
graph = graph_builder.training_graph(input_data, input_labels)
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 425, in training_graph
**tree_kwargs))
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 705, in training_graph
regression=self.params.regression))
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\o
ps\gen_tensor_forest_ops.py", line 224, in count_extremely_random_stats
regression=regression, name=name)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\op_def_librar
y.py", line 763, in apply_op
op_def=op_def)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
2397, in create_op
set_shapes_for_outputs(ret)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1757, in set_shapes_for_outputs
shapes = shape_func(op)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1707, in call_with_requiring
return call_cpp_shape_fn(op, require_shape_fn=True)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 610, in call_cpp_shape_fn
debug_python_shape_fn, require_shape_fn)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 670, in _call_cpp_shape_fn_impl
status)
File "F:\Anaconda3\lib\contextlib.py", line 66, in exit
next(self.gen)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\errors_impl.p
y", line 469, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.NotFoundError: Op type not registered 'C
ountExtremelyRandomStats'
======================================================================
ERROR: testTrainingConstructionClassificationSparse (main.TensorForestTest)
Traceback (most recent call last):
File ".\test.py", line 120, in testTrainingConstructionClassificationSparse
graph = graph_builder.training_graph(input_data, input_labels)
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 425, in training_graph
**tree_kwargs))
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 705, in training_graph
regression=self.params.regression))
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\o
ps\gen_tensor_forest_ops.py", line 224, in count_extremely_random_stats
regression=regression, name=name)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\op_def_librar
y.py", line 763, in apply_op
op_def=op_def)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
2397, in create_op
set_shapes_for_outputs(ret)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1757, in set_shapes_for_outputs
shapes = shape_func(op)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1707, in call_with_requiring
return call_cpp_shape_fn(op, require_shape_fn=True)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 610, in call_cpp_shape_fn
debug_python_shape_fn, require_shape_fn)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 670, in _call_cpp_shape_fn_impl
status)
File "F:\Anaconda3\lib\contextlib.py", line 66, in exit
next(self.gen)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\errors_impl.p
y", line 469, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.NotFoundError: Op type not registered 'C
ountExtremelyRandomStats'
======================================================================
ERROR: testTrainingConstructionRegression (main.TensorForestTest)
Traceback (most recent call last):
File ".\test.py", line 75, in testTrainingConstructionRegression
graph = graph_builder.training_graph(input_data, input_labels)
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 425, in training_graph
**tree_kwargs))
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\t
ensor_forest.py", line 705, in training_graph
regression=self.params.regression))
File "F:\Anaconda3\lib\site-packages\tensorflow\contrib\tensor_forest\python\o
ps\gen_tensor_forest_ops.py", line 224, in count_extremely_random_stats
regression=regression, name=name)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\op_def_librar
y.py", line 763, in apply_op
op_def=op_def)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
2397, in create_op
set_shapes_for_outputs(ret)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1757, in set_shapes_for_outputs
shapes = shape_func(op)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line
1707, in call_with_requiring
return call_cpp_shape_fn(op, require_shape_fn=True)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 610, in call_cpp_shape_fn
debug_python_shape_fn, require_shape_fn)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\common_shapes
.py", line 670, in _call_cpp_shape_fn_impl
status)
File "F:\Anaconda3\lib\contextlib.py", line 66, in exit
next(self.gen)
File "F:\Anaconda3\lib\site-packages\tensorflow\python\framework\errors_impl.p
y", line 469, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.NotFoundError: Op type not registered 'C
ountExtremelyRandomStats'

Ran 9 tests in 2.945s
FAILED (errors=5)

Support for the tf.contrib.tensor_forest submodule was not included in TensorFlow 1.0, but it has been fixed at HEAD. Can you try upgrading to a nightly build of TensorFlow and see if the problem persists?

@mrry  well, it is OK using nightly version.
It shows:
DeprecationWarning: Please use assertEqual instead. self.assertEquals(2, hparams.num_classes)
Ran 9 tests in 7.760s
OK
However this nightly version also show these warning info:
2017-03-09 12:45:53.258939: W c:\tf_jenkins\home\workspace\nightly-win\device\gp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE instructions, but these are available on your m
achine and could speed up CPU computations.
2017-03-09 12:45:53.259939: W c:\tf_jenkins\home\workspace\nightly-win\device\gp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE2 instructions, but these are available on your
machine and could speed up CPU computations.
2017-03-09 12:45:53.260939: W c:\tf_jenkins\home\workspace\nightly-win\device\gp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE3 instructions, but these are available on your
machine and could speed up CPU computations.
2017-03-09 12:45:53.261939: W c:\tf_jenkins\home\workspace\nightly-win\device\gp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE4.1 instructions, but these are available on you
r machine and could speed up CPU computations.
2017-03-09 12:45:53.262939: W c:\tf_jenkins\home\workspace\nightly-win\device\gp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE4.2 instructions, but these are available on you
r machine and could speed up CPU computations.
2017-03-09 12:45:53.263939: W c:\tf_jenkins\home\workspace\nightly-win\device\gp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use AVX instructions, but these are available on your m
achine and could speed up CPU computations.
2017-03-09 12:45:53.263939: W c:\tf_jenkins\home\workspace\nightly-win\device\gp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use AVX2 instructions, but these are available on your
machine and could speed up CPU computations.
2017-03-09 12:45:53.264940: W c:\tf_jenkins\home\workspace\nightly-win\device\gp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use FMA instructions, but these are available on your m
achine and could speed up CPU computations.
So I continue to use tf r1.0 and wait for your good news.

It sounds like the issue has been fixed in that case. You can safely ignore the warnings about SSE and AVX in the nightly build...


New package: dustinblackman.oatmeal 0.12.3

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Automated with GoReleaser
Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

With the dependency installed, the application gives this message:

Should "Ollama" be a dependency? We don't currently have a manifest for this package either.

Hi there!
Nope, Oatmeal consumes the Ollama API which just isn't running on the test machine. Expected behaviour.
What changes can I make to fill the initial error?


Add Skip field BotKube Event

Describe the bug
We need to add Skip field in BotKube struct so that if any of filters ask to skip the reporting of the event to slack, we should be able to that.
Filter Engine should not pass event further if it observes Skip fieldset.
Expected behaviour
Filter sets Skip field in BotKube Struct, FilterEngine should stop processing event.
Additional context
We had a use case where a BotKube user reported a lot of pods where getting created through CronJob and he was not interested in Create/Delete events for them. The filter could not allow skipping of events currently.

Fixed with https://github.com/infracloudio/botkube/pull/67


Add linting and formating

Add Black and Pylint in an sh file to format and lint the added code.
Also add instructions on formatting and linting via running the sh file in CONTRIBUTING.md

Hey @alfawal i would like to work on this issue, if its still open

Sure @rexdivakar go aheah


Initial set of text extraction functions

[ ] choose best library for each file type: pdf, docx, ppt, epub, latex, rtf, csv
[ ] python script with functions demonstrating appropriate use of each library
[ ] place in subfolder under 'scripts' in github and submit pull request

https://github.com/MESH-Research/nlp-ml-repo


Be able to provide helpful hints in a contextual, non-intrusive manner using tooltips

Problem you would like to solve
As a user of the modeler I have issues navigating the properties panel and understanding individual items due to the lack or overload of information:

Too little information: In some places, the properties panel showcases a very small amount of information. This leads to me not being able to understand how a certain feature works (https://github.com/camunda/camunda-modeler/issues/3588).
Too much information: In some places we show large amounts of information, specifically in connectors or timer definitions (cf. additional context). Much of that is duplicate and tends to become irrelevant once you know. Such wall of text can distract users from quickly skipping through the properties panel to discover or re-identify relevant information.

Proposed solution
Structure helpful hints in a manner that it is non-intrusive using tooltips:

[ ] Tooltip shows structured information (code snippets, external links)
[ ] Tooltip presence is indicated on the UI (on element/section hover/focus)
[ ] Tooltip displays on demand (when user hovers/focuses a certain section)
[ ] Tooltip can be focused to copy from, but also follow links presented in there
[ ] Tooltips can be populated in different ways:

Baked into core properties panel
(Potentially) embedded into description tags
(Potentially) contributed through element templates to properties, sections, ...

Overall we want to discourage the use of descriptions, unless explicitly desired, in favor of tooltips.
Alternatives considered
None.
Additional context
Current UI in connectors, meant to be user friendly; assistive documentation highlighted:

Current timer definition UI; assistive documentation highlighted:

Depends on https://github.com/bpmn-io/properties-panel/issues/202

A quick sketch on tooltip discovery:

Another one on overall tooltip UI:
https://github.com/bpmn-io/properties-panel/issues/202

Context provided by @YanaSegal: We already have an existing tooltip component in web modeler. To be clarified if we want to use that one, move to a new one (Carbon).
Cf. existing component, used in Web Modeler:

Hello @nikku, Is this issue still open? I wanted to know about this issue can you please tell me, where it is occurring and what adjustments you want. Actually i'm new to opensource contribution, till now i've contributed to my personal repo only.

If you want to contribute @Nitish-u, please checkout issues flagged accordingly as well as our contributing guide.

While https://github.com/bpmn-io/properties-panel/issues/202 is being reviewed, I will try to identify places where we might want to replace the description with a tooltip or add one.
This will also help me figure out if there is a need to allow tooltip population by context/tooltip provider like we do for description for now.

[tooltips via context and tooltips for group headers]
In order to provide tooltip content as context, we need to provide ids for the trigger element. If we combine this with supporting tooltips on group headers, then we need to provide some id. The group id sometimes coincides  with a field id (ex: documentation group and element documentation field; implementations group and field).
A way to avoid potential breaking changes by altering some of the ids so they don't match, is to use the data-group-id which adds the group- prefix. In a tooltip provider, this would look like:
- businessRuleImplementation: (element) => return <TOOLTIP_CONTENT>;

// for implementation field
+ businessRuleImplementation: (element) => return <TOOLTIP_CONTENT>;
// for implementation group
+ `group-businessRuleImplementation`: (element) => return <TOOLTIP_CONTENT>;


Add type traits for search structures

Added two type trait functions for search structure types, datatype and distancetype. These can be useful for pre-allocating arrays, for example.

Oh WOW! I never expected that someone else would use this, much less so actually contribute!!! Thank you so much! Is this good to go from your end?

It should be good, there are a few basic tests for KDTree with it. There are a couple of things I wasn't sure about:

Neither function is exported. They probably won't be needed in basic usage so I think this makes sense.
I didn't add anything about them to the dev section of the docs yet.

I definitely prefer the API in this package to NearestNeighbors, their requirement that data points must be (uniformly-sized) arrays doesn't work for my purposes. It's also really useful to have the skip predicate function.
I was working on adding the skip functionality to VPTrees and thought I might as well try to bring it under this API while I'm at it, if you think that would be useful.

I was working on adding the skip functionality to VPTrees and thought I might as well try to bring it under this API while I'm at it, if you think that would be useful.

Yes, please do! Any contribution of more packages under this API is very welcome!
The original plan was for this package to only provide the API, and not actually implement it for packages, and instead the implementation to be at the specific packages. Alas, this didn't happen in the end, so I made the decision to just add the packages here as dependencies. I mean, it isn't that bad with the new package manager. So yes, if you want to extend VPTrees please go ahead!

I didn't add anything about them to the dev section of the docs yet.

If you are willing to add a few words to the dev docs, I think it is a good idea!

Ok, I've thought about this a bit more and I think this should be modified a bit.
My use case - I wanted to write tests for my additions to VPTrees, but realized that these tests are universal and it would be useful to put them in functions in a submodule of Neighbors so that they could be used for other search structure types. One of these is comparing search results to a brute force search, so I was writing brute force search functions. These require I pre-allocate an array to store distance values.
So basically, given values for metric, data, and query, I need a way to know the type of metric(query, data[i]). There are a few possibilities for this:

Just use Float64. Should work in pretty much all cases, but some metrics may return e.g. Float32 for performance reasons and ideally that should be preserved.
Have the creator/owner of the metric add a method to a function distancetype(::MyMetric, ::Type{DataType}). This is what I did in this PR but using the search structure instead of the metric directly.
Just call metric(query, data[1]) and get the return type. Inelegant but works.
Other Julia type inference magic techniques.

I think I found a better way to do this using a combination of #s 3 and 4, so there's not really a need to add distancetype to the public API at the moment. I removed that and add a getmetric(searchstructure) function, which I think could be useful.
Since neither of the functions introduced in this PR are used for anything yet I haven't written anything about them in the dev docs.

Slack gave me Base.return_types or Core.Compiler.return_type, does this help to not call anything? (i.e. do 4)

Hm then again someone says it is not recommended to use these internal functions, so better just do step 3 instead...

Here's what I've written:
"""
	metricreturntype(metric, x, y=x)

Get the expected return type of `metric(x, y)`. This is inferred statically if
possible, otherwise the function is actually called with the supplied arguments.
Always returns a concrete type.
"""
function metricreturntype(metric, x, y=x)
	# The following should return a concrete type if metric is type stable:
	T = Core.Compiler.return_type(metric, (typeof(x), typeof(y)))
	T isa DataType && T.isconcretetype && return T
	return typeof(metric(x, y))
end

I think this should work in more or less all cases.

yeap seems goot to me!

After spending most of the last 5 hours struggling with this and delving into the Base source code, I finally figured out I have to replace
Core.Compiler.return_type(metric, (typeof(x), typeof(y)))

with
Core.Compiler.return_type(metric, Tuple{typeof(x), typeof(y)})

in order for the result of the function to be inferable. I'll submit it in another PR.

alright, then I'll merge this


lp user  group add/remove

Please add back: "lp user  group add/remove "
It was randomly removed from the newer version of luck perms. I need it because I have a ton of purchases using that command for my global ranks and there is no way I can change it now.

It wasn't randomly removed, it was one of many legacy aliases that shouldn't really have been added in the first place.
Why can't you just change them?

Essentially, if a player has already purchased a global rank and has not joined the server then the command won't process, so those who haven't joined all the servers have commands pending and I don't think I can change pending commands with buycraft

I'd consider contacting their support

An alternative is to downgrade to version 4

There was a reason this alias was undocumented btw. And yes downgrading temporarily to a v4 and then changing the commands and upgrading back should work.


[Question] [ws-sbom-generator] Generate the spdx for a product + viewer

Question
•	What command to use if I want to generate the spdx for a product (containing all residing projects)? Unfortunately, I only found ways to generate either for the whole org, or a specific project.
•	Do you recommend a viewer/reader tool for SPDX format? I know this is the standard for BOM information, but I didn’t find any straightforward tools.
Commands I used:
For all projects in the org:
ws_sbom_generator -u <WS_USER_KEY> -k <WS_ORG_TOKEN> -a URL -t tv -o </path/reports>
For one project:
ws_sbom_generator -u <WS_USER_KEY> -k <WS_ORG_TOKEN> -a app-eu -s URL -o </path/reports>
Environment Details

OS: [Windows 10]
Browser [Chrome]
Version [99.0.4844.82 (Official Build) (64-bit)]

Hi @alalitkdi ,
You can use the following syntax to generate the spdx for a product :
ws_sbom_generator -u <WS_USER_KEY> -k <WS_ORG_TOKEN> -s <WS_PRODUCT_TOKEN> -a saas -t tv -o </path/reports>
As for spdx viewer / reader - you can check https://tools.spdx.org/app/
Thanks,
WhiteSource PS team

Thanks! It starts to create the report but it abruptly stops with an error:
ws_sdk.ws_errors.WsSdkServerGenericError: Generic error on token: 'a2c91221xxxxxxxxxxxxxxxxxxxxxxxx0c77ae3'. Error: {"errorCode":4000,"errorMessage":"Unexpected error"}
The token mentioned here is the product token.
This is the query I run:
ws_sbom_generator -u 3f1dbb992bbxxxxxxxxxxxxxxxfa68ec79293f7 -k 5c987a0cxxxxxxxxxxxxxxxxxxx083f337b499162 -s a2c91221xxxxxxxxxxxxxxxxxxxxxxxx0c77ae3 -a []([](https://app-eu.whitesourcesoftware.com
ws-log.txt
)) -t tv -o C:\Projects\ws-sbom-generator-master\Reports
This redacted output log is attached.

Hi @alalitkdi - I'm checking and will get back to you in advance.

Hi @alalitkdi , there is a pre-release which fix this issue ( pip install ws-sdk==<IP_ADDRESS>a1 ).
I'm doing some additional tests on, once done I will share a new version of the ws-sbom-generator.

Hi @alalitkdi ,
Please check the new version of ws-sbom-generator

Hi @rammatzkvosky, I can confirm the the new version works fine and generates the report. However, the report fails to get validated with the following error:
Analysis exception processing SPDX file: Invalid checksum: SHA1: at line number 23720
Validated at: https://tools.spdx.org/app/validate/
Screenshot attached.

Hi @alalitkdi ,
Please notice that the generated report you mentioned was not in the correct format as we can't merge a specific  WhiteSource product's projects to a single report.
Each WhiteSource project should have its own separate report.
The PR I created will cover the mentioned command + the cases where sha1 is missing.

Thanks @rammatzkvosky! The requirement was to have a product and its projects in a single report, like stated in the original thread. Thanks for resolving it.
How should I use the latest version to regenerate the report?


rectool.py example use

Hi,
i would like to use AaltoASR python to perform a recognition starting from an audio file as input, but i can't figure out how to inizialize some variable of the example bash (as AM, LM and so on...).
Where can i find a detailed documentation or working example?
Thanks in advance.

The AaltoASR speech recognition system needs an acoustic model (AM) trained with AaltoASR and a ngram language model trained with e.g. srilm. Do you have any experience training ASR systems? Also, do you happen to be an Aalto University student, in which case we can see what models we can provide for you?

I'm from Politecnico of Torino (IT), actually working for this research lab https://github.com/netgroup-polito

Unfortunately our external documentation for AaltoASR is not very good. Unless you are specifically interested in the features of our decoder (token-pass, good for deep-context subword models) I can recommend to use a different speech recognition toolkit such as Kaldi or HTK. If you do very much want to use our decoder, let me know and we'll try to get you started.


Does this sample work on windows platform?

I try to build this sample on windows 10 npm 5.3.0 and meteor 1.3-modules-beta.5
it failed.

Frankly, I didn't test this on Windows.
I'm looking for some help on this.

When I try to run this sample on Windows 10 I receive this message ..

This project uses Meteor 1.3-modules-beta.6, which isn't available on Windows. To work with this app on all supported platforms, use meteor update --release<EMAIL_ADDRESS>to pin this app to the newest
Windows-compatible release.

I'm looking for an alternative using Eclipse Che, but I'd no luck on a environment that allows me to build meteor apps.

I created my directory with meteor create --release 1.3-beta.11 myapp and copied all the other files in  and I also tried just cloning the entire thing.
I don't get a Meteor error on Windows 10 but I do get:
Uncaught Error: Cannot find module 'react' install.js:77
Also
router.js:347 There is no route for the path: /
Any help appeciated!

Good news, since 1.3-beta.11, Meteor can run on windows again.
@forcepath The original source works ? For me the 'mantra-sample-blog-app' is working ok now.

Yes! Thanks, I reran the npm install on the dependencies, and it worked, I must have left out something before.


Make QueueSize configurable

We use the OPCPublisher now in production at our customer to read ~16 values from a plc every 50 milliseconds.
We monitor the ingest and everything seems to works fine except for one thing: once every minute (on average) several node values are skipped. We know this because the values produced contain a counter.
We traced this back to the QueueSize:
https://github.com/Azure/iot-edge-opc-publisher/blob/master/opcpublisher/OpcMonitoredItem.cs#L577
If we increase this to 50, we retrieve all data as expected.
Please make this QueueSize configurable.

https://github.com/Azure/iot-edge-opc-publisher/pull/225#issuecomment-517189424
Any updates on this feature ?

Any updates on this feature?

in version 2.8.2 QueueSize is configurable for Standalone mode.
For option syntax please look for DefaultQueueSize in publisher-commandline.md file.


Is this crate still actively developed?

First of all, I would like to make it very clear that I mean no disrespect with this issue. I use paperclip in several of my side projects and I am extremely grateful to its author, maintainers and community. It has served me well and I understand all the work that was needed to get it to this point.
However, my team is now starting a new web project, we opted for actix-web as our base framework, and I am trying to assess what would be the best candidate for documenting it. I tried utoipa but it is not what we are looking for since it mostly relies on endpoint declaration through macros which is probably fine for small projects but it is not what we want to rely on. It is also not as well integrated as paperclip may be.
That leaves us with two main contenders: paperclip an apistos. At first sight paperclip should be a no-brainer given how long it has been around and the size of its user base. But the project has been through some rough patches (with the original author stepping down etc.) and from a technical standpoint the project is still mostly generating swagger (v2) instead of openAPI v3.
In the other hand apistos is still very young. We tested it and were happy with the result. But we are a bit worried it might not have enough traction on the long run.
Ideally we would simply wait a couple months to see what happens. But we need to make a decision in the next few days so that's not an option.
TL;DR here is my, admittedly tricky, questions: What would you do if you had to start a big project today? Do you think that paperclip will remain the go to solution for our use case or is it mostly in maintenance only mode with the community slowly moving away from it maybe to apistos or some other new crate we may have missed?

I was hoping some community member would reply with a more "external" answer, but since there's none I'll give my 2c.
I am the current maintainer and unfortunately due to the lack of time I haven't got around to fix some of the bugs or add some of the features this crate is lacking.
That being said there aren't many if any critical issues that I'm aware of (kinda of expected I guess, since paperclip is not involved in the "live" part, if that makes sense).
I've never used apistos so I can't comment on whether it's a better alternative or not.
Would I use paperclip myself?
Yes and No :)
I haven't been using paperclip in my projects, not because of any issues but simply because I've flipped around and started using api first, so rather than generating openapi from code, I generate code from openapi. Paperclip already supports this but on openapi v2 only. I've tried to bring a new way though stuck atm due to licensing issues of the crate I was trying to use - https://github.com/paperclip-rs/paperclip/pull/506, at least until I find an alternative.
If I was still generating api from paperclip I would probably still use paperclip, unless I needed to generate something openapi3 specific, which this crate is not supporting atm.


thunderbird: 31.7.0 -> 38.1.0

@nbp @edolstra
I have tested on x86_64 platform. Mail, RSS reader, and Calendar seems working like thunderbird-bin.

Updated.

Tested locally, works for me as well.

I've had one freeze during the two hours (roughly), but maybe that was just bad luck.


Set the log file permissions before shutting down

The previous logic was not particularly useful...
Unfortunately this is a bit difficult to automatically test so I tested it manually.

LGTM, thanks


Incompatible version with Strawberry Fields

Describe the bug
antlr4-python3-runtime is incompatible between Braket (and the default simulator) and Strawberry Fields, even though it is pinned because of it:
https://github.com/aws/amazon-braket-default-simulator-python/blob/main/setup.py#L38
However, it is pegged to a different version in Blackbird, which is used internally by SF:
https://github.com/XanaduAI/blackbird/blob/master/requirements.txt#L1
Error discovered by using pip-compile on a simple requirements.in file with pip-compile -r requirements.in
amazon-braket-sdk
strawberryfields

Output:
Could not find a version that matches antlr4-python3-runtime==4.8,==4.9.2 (from quantum-blackbird==0.4.0->strawberryfields==0.23.0->-r req.in (line 2))
Tried: 4.4.0, 4.4.1, 4.5, 4.5.2, <IP_ADDRESS>, 4.5.3, 4.6, 4.7, 4.7.1, 4.7.2, 4.8, 4.9, 4.9.1, 4.9.2, 4.9.3, 4.10, 4.11.0, 4.11.0, 4.11.1, 4.11.1
There are incompatible versions in the resolved dependencies:
  antlr4-python3-runtime==4.9.2 (from amazon-braket-default-simulator==1.9.0->amazon-braket-sdk==1.31.1->-r req.in (line 1))
  antlr4-python3-runtime==4.8 (from quantum-blackbird==0.4.0->strawberryfields==0.23.0->-r req.in (line 2))

The plugin requires the installation of SF: https://github.com/aws/amazon-braket-strawberryfields-plugin-python
This means that blindly installing these with pip can lead to subtle bugs due to differences:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
amazon-braket-default-simulator 1.9.0 requires antlr4-python3-runtime==4.9.2, but you have antlr4-python3-runtime 4.8 which is incompatible.

Hi @ianhellstrom ,
Thank you for logging this issue. We are working on dealing with this dependency conflict. Meanwhile, if you need to unblock yourself, I suggest you run:
pip install amazon-braket-sdk
followed by
pip install amazon-braket-strawberryfields-plugin
as two separate commands.
pip should be able to automatically downgrade antrl to 4.8, which should work for how we currently use it.
Let me know if this helps.

Perhaps a silly question, but why not simply use 4.8?


using apidoclink attribute to refactor wiki  + cleanup

Trying to minimise the use of netbeans.org reference to get wiki more consitent.
As the import quote deprecated wiki.netbeans.org it's now useless.
Fixing bugzilla ref to the apache bugzilla.

@vieiro it's mostly using an attribute to replace bits.netbeans.org/javadoc in all the wiki
also removed the "disclamer to avoir wiki.netbeans.org"
aim is to converge to a grepable base of page to fix remaing glitches.


Should export functions to the shell

NVM suffers from the following:
    $ tail -n +1 entrypoint.sh childscript.sh
    ==> entrypoint.sh <==
    #!/bin/bash
    function inheritedfunction() {
      echo "I am an inherited function"
    }
    exec ./childscript.sh
    ==> childscript.sh <==
    #!/bin/bash
    function localfunction() {
      echo "I am a local function"
    }
    localfunction
    inheritedfunction
    $ ./entrypoint.sh
    I am a local function
    ./childscript.sh: line 8: inheritedfunction: command not found

Essentially if you exec (either explicitly with exec ./childscript or implicitly by ./childscript) then NVM becomes unavailable.
gvm and rbenv solve this by having a shell shim that modifies the path and making sure that the binaries are real binaries, really on the $PATH.
Short term suggestion would be to export -f every_function_in_nvm (it's a long list):
+  export -f nvm
+  export -f nvm_add_iojs_prefix
+  export -f nvm_alias
+  export -f nvm_alias_path
+  export -f nvm_binary_available
+  export -f nvm_checksum
+  export -f nvm_download
+  export -f nvm_ensure_default_set
+  export -f nvm_ensure_version_installed
+  export -f nvm_ensure_version_prefix
+  export -f nvm_find_nvmrc
+  export -f nvm_find_up
+  export -f nvm_format_version
+  export -f nvm_get_arch
+  export -f nvm_get_latest
+  export -f nvm_get_os
+  export -f nvm_has
+  export -f nvm_has_system_iojs
+  export -f nvm_has_system_node
+  export -f nvm_install_iojs_binary
+  export -f nvm_install_node_binary
+  export -f nvm_install_node_source
+  export -f nvm_iojs_prefix
+  export -f nvm_is_alias
+  export -f nvm_is_iojs_version
+  export -f nvm_is_valid_version
+  export -f nvm_ls
+  export -f nvm_ls_current
+  export -f nvm_ls_remote
+  export -f nvm_ls_remote_iojs
+  export -f nvm_ls_remote_iojs_org
+  export -f nvm_match_version
+  export -f nvm_node_prefix
+  export -f nvm_normalize_version
+  export -f nvm_npm_global_modules
+  export -f nvm_num_version_groups
+  export -f nvm_prepend_path
+  export -f nvm_print_implicit_alias
+  export -f nvm_print_npm_version
+  export -f nvm_print_versions
+  export -f nvm_rc_version
+  export -f nvm_remote_version
+  export -f nvm_remote_versions
+  export -f nvm_resolve_alias
+  export -f nvm_resolve_local_alias
+  export -f nvm_strip_iojs_prefix
+  export -f nvm_strip_path
+  export -f nvm_supports_source_options
+  export -f nvm_tree_contains_path
+  export -f nvm_validate_implicit_alias
+  export -f nvm_version
+  export -f nvm_version_dir
+  export -f nvm_version_greater
+  export -f nvm_version_greater_than_or_equal_to
+  export -f nvm_version_path
+}

But, with this childscript is able to at least run nvm. Unfortunately this means that $ env becomes essentially useless, as this export -f  is a bashism which exports the function body as an environment variable with the same name as the function to allow it to pass through man (3) execv

The suggestion to split things up into binaries is in #337.
I wouldn't necessarily say nvm "suffers" here - you can also just rerun the source line (. $NVM_DIR/nvm.sh) and that should cover you without having to export each function, right?

The problem is we're building a CI, and we setup an environment (environment includes nvm, gvm, rbenv, rvm, etc) and then we exec ./the/user/test/script… and we wanted to give them the 100% clean "just run node" experience, if we have to tell them to start sourcing random dot-files, then it takes the shine off the user experience a lot.
I'd be more than happy to let you close this and we can pick up in #337.

Having just read the arguments in #337 it seems people are largely against changing, fear of breaking changes, and how rbenv's shim approach can cause issues (unfortunately two linked tweets are protected/deleted) so I'm not sure what issues that might be, but it's certainly non-trivial.

Right - I'm fine with change, but I'd prefer avoiding breaking changes. The shim approach of rvm and rbenv are very intrusive, and that makes testing and support much harder as well.
Why do you need nvm at all in the exec'd shell? Can you not just do nvm use node first, and then export the PATH down?

We rely on the default, so we don't "nvm use" anything, maybe that would be a workaround.
Regarding the breaking change from the shim, I've always found rbenv's shim approach to be really, really neat - but I suppose it depends a little bit on the entry point, there's another thing here though, what's to stop nvm itself being on the path, working as it does now, but not being a shell function, rather something you can really execute?

If that was the case, nvm.sh would have to be parsed on every invocation of nvm - unless all of its other constituent parts were also separate executables.

If that was the case, nvm.sh would have to be parsed on every invocation of nvm - unless all of its other constituent parts were also separate executables.

This is how rbenv works. That part at least seems to work pretty well, although admittedly the shims are a bit of a mess at times (I hated rbenv rehash(


BLD: switch bluesky dep to bluesky-base

This avoids pulling in additional unused or optional sub-dependencies by default.
It's a small detail we've been updating in some of our other feedstocks that we missed when creating this one.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] ~Reset the build number to 0 (if the version changed)~
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

previous rerender error was a server error, retrying after latest unrelated commit
we messed up the original maintainers on this repo in https://github.com/conda-forge/staged-recipes/pull/27370 so we'll need to ask for some help

@conda-forge-admin, please rerender

@conda-forge-admin, please update team

To simplify things, I will:

close this PR
rebase
open a new PR

superceded by #4


Disable with-dirs cargo feature in rustyline

Disable rustyline with-dirs feature since it is unused in
artichoke-frontend. This change removes some dependencies of
rustyline from the Cargo.lock.
The with-dirs feature of rustyline activates tab completion behavior
for paths that start with ~. airb uses rustyline to input Ruby
source code, not paths, so this optional feature is not being used.

This PR removes 9 deps from Cargo.lock.


Fixed typescript errors. updated package.json

I don't seem to be getting the new version of the package when I do npm install this should fix that hopefully.

Actually this didn't seem to solve the problems. @ascoders do you happen to know why this is happening?

disregard comment from earlier. this pr does in fact fix the issue.

Thanks for fixing the problem, but I'm refactoring the swipeDown, and the old one has been deleted.

@ascoders sounds good! when do you expect for it to be done?

It's will be released the next few days. @ShayanJavadi

@ascoders wonderful! thanks!


CMake samples cleanup

This PR rebases and so replaces #1618, original below:
This PR takes care of a few tasks regarding the samples build system.
Fixes: https://github.com/Microsoft/openenclave/issues/1606
Fixes: https://github.com/Microsoft/openenclave/issues/1588
Fixes: https://github.com/Microsoft/openenclave/issues/1605
Fixes: https://github.com/Microsoft/openenclave/issues/1590
Fixes: https://github.com/Microsoft/openenclave/issues/1357

bors r+

bors r-

bors try

Re-opening since I'm working to fix it.


Add unit testing pipeline for base testing.

Overview/Summary
Add base unit testing pipeline as described in Base E2E testing
This PR fixes/adds/changes/removes

Adds new pipeline to do basic validation testing.

Breaking Changes
None
Testing Evidence
Successful run can be seen here.
As part of this Pull Request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues
[x] (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[ ] Updated tests (if required) Unit - Linting - E2E (End-To-End)
[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
[ ] If relevant, created or updated Code Tours here

/azp run BaseUnit

/azp run E2E

Evidence for last run with hardcoded values for PR, see here

Lint check fails because https://github.com/Azure/ALZ-Bicep/blob/main/tests/pipelines/base-unit-validate.yml doesn't exist yet.

/azp run E2E

/azp run E2E

/azp run E2E


Add required devDependencies for Travis CI build.

Description
Update the package.json file to include the ESLint and ESValidate packages, required for the npm run test tas to run on Travis CI.
Motivation and Context
If we want to implement Greenkeeper.io, we have to have a build pipeline which returns a status when Greenkeeper attempts to update dependencies. Using Travis CI, we are able to clone gulp-wp-toolkit and run the npm run test task.
How Has This Been Tested?
Observed the Travis CI return status when pushing code to branch cs/travis-build.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project (I've run npm run lint).
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

Update the package.json file to include the ESLint and ESValidate packages, required for the npm run test tas to run on Travis CI.

Interesting - the packages already exist locally for me.


TIP-27 IOTA NFT standards

This PR creates a TIP about

IOTA NFT Metadata Standards
Decentralised PolicyID system to prevent fake collections
Defining Creator Royalties

rendered version

Updated a lot of the info by request and also added TIP 33 for the Token Registry

Hey :wave:
im thinking to remove the collectionId from the metadata. This could be used to scam people, if dApps not validate, if the collectionId is valid. So for example the NFT creator can add an collectionId from another NFT collection and copy it. This feature is already solved by the "issuerId" which can not be changed or add manually. Also, we need less data so we need less tokens for storage deposit.
What do you think?

Hey 👋
im thinking to remove the collectionId from the metadata. This could be used to scam people, if dApps not validate, if the collectionId is valid. So for example the NFT creator can add an collectionId from another NFT collection and copy it. This feature is already solved by the "issuerId" which can not be changed or add manually. Also, we need less data so we need less tokens for storage deposit.
What do you think?

As collectionId is optional I think it is ok to keep it. It can be useful sometimes for easier access to the ID but you can always also just ignore it 🤔

I was thinking about adding something 😅 .
What about having an additional data property. And than you either have a uri or data property.
Because otherwise how would you use this standard if you want to store your data on-chain in the output? 🤔

I was thinking about adding something 😅 .
What about having an additional data property. And than you either have to provide an uri or data property.
Because otherwise how would you use this standard if you want to store your data on-chain in the output? 🤔

I wouldn’t complicate. You can always store it within uri. Same way as you would set src attribute in html
for example

I was thinking about adding something 😅 .
What about having an additional data property. And than you either have to provide an uri or data property.
Because otherwise how would you use this standard if you want to store your data on-chain in the output? 🤔

I wouldn’t complicate. You can always store it within uri. Same way as you would set src attribute in html
for example

My bad. I totally forgot the data URI scheme 😅

As collectionId is optional I think it is ok to keep it. It can be useful sometimes for easier access to the ID but you can always also just ignore it 🤔
Yes, the collectionIdis optional in the metadata but required as ìssuerID` on a collection. So its optional to store the data twice :P

And i can add everything i like to the collectionId field - also collectionIds from other existing collections which i could use to scam people on dApps like marketplaces where this collectionId not gets validated.
So why using an extra attribute which information is already present and add an potentially scam potential? Or am I misunderstanding something?

I agree that it does not make sense to include the collectionId. Besides opening the door for scammers, if it is accidentally messed up by the creator of an NFT collection and not noticed in time, there might be invalid NFT collections out there.
So why even make it complicated and give minters another possibility to make an error when we can just check the NFTid of the collection NFT?
No dapps will/should implement relying on the collectionId for verification if it is well known that it can be set as any arbitrary value.

Yeah makes sense thinking about it 👍

An additional use case for the suggested key is a public voting process where one person can vote once.
In these voting scenarios a voting authority is normaly requred present and required to identify the voters and authorize them to partecipate to the pool process. The vote, in most of the cases need to be secret, but this point is out of topic here.
A simple solution to provide an authorization to the voters is to mint and sent to them an NFT that have to send to a final destination address with the vote included in the tx metadata.
So in this case the allowed_address_sequence can be a list of two address: voter's address where the NFT is minted,  pool address where the NFT have to be sent.

Hey Stefano, thanks for your input! This sounds like an ideal use case for Smart Contracts. I see the problem, that all dApps needs to check if the address is valid or not. That means, the protocol could just send the NFT to an address which is not allowed. There is no "if/else" here on protocol level, this needs a smart contract. Because of this reason, i would say this should not be part of the NFT standard. You could extend the standard for your applications. If i miss something, please let me know. Is there anything like that on other NFT standards?

I understand your point. In fact, my first thought was to use a SC for these kinds of scenarios, but objectively for some of these cases it might be too much of a heavy duty.
Instead of modifying the NFT standard, it might make more sense to propose a new Unlock condition so that we can limit the displacement of a genenric token on specific addresses?

On second thought, both Unlock condition and Smartcontract are not safe solutions.
In fact, Unlock conditions, if I have not misunderstood, are related to the individual tx, not to the object being moved. This implies that the next "owner" can freely define his own Unlock condition that replaces the previous one.
More or less the same applies to Smartcontract, which being deplyoed by an owner, can always be replaced.
In my initial idea these validity conditions are to be included in the immutable part of the NFT.
Obviously it would be useful for the network to take them into account by considering invalid a tx that moves an NFT to an address not authorized by its author.

I've spoke with @Phyloiota the other day as he asked me to review Shimmer OG NFT collection. I've provided him with feedback and he asked me to share it here so here it goes:

Alias should have been used to issue NFT collection. We do this because it was suggested by various people from IF after we did many reviews/testing with various parties. It's great suggestion. Alias can be used for various things (i.e. Alias can be transferred to new owner or even to a party that wants temporary do something with the collection). TIP27 does not specify how collections / NFT should be minted and I think it should be more specific!
Collection NFT metadata have "type": "text/html" and "uri": "https://shimmer.network". This is more an additional attribute. Uri should be reserved for preview image so it can show collection banner. Right now, this NFT collection will have no image once it's imported into various NFT marketplaces.
I noticed Shimmer OG NFT has no props/stats. This significantly decrease value of the NFT and it's rarity. Owner will not know anything about the NFT. NFT should always have some stats/props and it should be encouraged.
NFT uri could have just been ipfs://QmPoYcVm9fx47YXNTkhpMEYSxCD3Bqh7PJYr7eo5YjLgiT to save on storage deposit.

I'm not sure if above is something we want to enforce within the specification but it might be worth to consider some of them. Some of them can also be great "suggestions" for artists to follow.

Hey Adam, thanks for you feedback!

TIP27 does not specify how collections / NFT should be minted and I think it should be more specific!

It's defined here - but it should be more specific and the Alias part is missing - https://github.com/Kami-Labs/tips/blob/main/tips/TIP-0027/tip-0027.md#minting-l1-nft-collections

Collection NFT metadata have "type": "text/html" and "uri": "https://shimmer.network". This is more an additional attribute. Uri should be reserved for preview image so it can show collection banner. Right now, this NFT collection will have no image once it's imported into various NFT marketplaces.

Very Good point - so the example is a bit miss leading and we could need something like homepage
"uri": "https://my-awesome-nft-project.com",

I've spoke with @Phyloiota the other day as he asked me to review Shimmer OG NFT collection. I've provided him with feedback and he asked me to share it here so here it goes:

Alias should have been used to issue NFT collection. We do this because it was suggested by various people from IF after we did many reviews/testing with various parties. It's great suggestion. Alias can be used for various things (i.e. Alias can be transferred to new owner or even to a party that wants temporary do something with the collection). TIP27 does not specify how collections / NFT should be minted and I think it should be more specific!
Collection NFT metadata have "type": "text/html" and "uri": "https://shimmer.network". This is more an additional attribute. Uri should be reserved for preview image so it can show collection banner. Right now, this NFT collection will have no image once it's imported into various NFT marketplaces.
I noticed Shimmer OG NFT has no props/stats. This significantly decrease value of the NFT and it's rarity. Owner will not know anything about the NFT. NFT should always have some stats/props and it should be encouraged.
NFT uri could have just been ipfs://QmPoYcVm9fx47YXNTkhpMEYSxCD3Bqh7PJYr7eo5YjLgiT to save on storage deposit.

I'm not sure if above is something we want to enforce within the specification but it might be worth to consider some of them. Some of them can also be great "suggestions" for artists to follow.

Not sure if it has any benefits in this use case. Even an NFT can be transferred. The powerful part of Alias is the unlock conditions with state and governance controller I would say.
And I think if there is a valid case to use that, it should probably be a separate TIP. This one being the easiest Implementation. In the end the NFT has some features of the Alias. So why not use it for some use-cases?
But I have no strong opinion against using an Alias. (Maybe the only one being that maybe collection NFTs are a well known thing, alias NFTs not :trollface: )
What do you mean with TIP27 doesn't specific how it should be minted? What needs to be more specific in your eyes?

NFTs can not just be images. So you could also specify in your guide that if someone wants to host on soonaverse he should add a image to the collection uri as a preview 🤔
In the end the TIP doesn't restrict you in what to put into uri.
I don't think we should add a homepage property tho tbh. You could add such additional properties to attribute to I guess 🤔

The TIP defines optional attributes. I even suggested to use them to define for example why you got the NFT (Won in Giveaway, participated in Singapur...). They didn't do it. And that's fine. we shouldn't force users to use those. But again, any marketplace could give such infos as tips in their guides. Want to increase value for your NFT? Add attributes.
After all again, not all NFTs are "just" images you try to sell.

This is a valid point which was actually also raised internally by @nicole-obrien afaik.

Thanks for your feedback ❤ . I personally think most of this things should be optional.

Thank you to everyone who worked on TIP-27! 💯


ui: Fix netowrkid not passed in deployvm

Description
Fixes the issue of the networkid not being passed when deploying a VM
This is caused when the first template selected is a deploy-as-is one and the nicToNetworkSelection not being reset when selecting a new template

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6711 (SL-JID-2306)


Question in training data label generation code - get_candidates.py

Dear ClairS Team,
While reviewing the code at the following link: https://github.com/HKU-BAL/ClairS/blob/c464c98c61f594489e385b8bb67c32518dce59f8/src/get_candidates.py#L348
I noticed a potential issue related to the find_candidate_match function.
It appears that the function may be utilizing the tumor alt_dict instead of the normal alt_dict.
Could you please take a moment to verify this?
Thank you for your time and support!
Best regards,

Hi, @quito418,
Billions thanks for reporting this! Should be normal alt_dict(paired_alt_dict). I guess it would only exclude a small proportion of candidates in training. We will try to add those candidates to training to further verify the results.
Zhenxian

Thanks, @Zhenxian! Looking forward to the release of the ClairS.


[WIP] closes #1183: exponential storage page size and appropriate sizes in all resolvers and fetchers

What this PR does:
Move away from the crazy storage page size of 1000 when searching for the documents. This PR adds support to increase the page size in the QueryExecutor in the exponential fashion.
Idea is to be able to start fetching matching rows from a reasonably small value, and then increase as we need more. The starting point is usually the requested docs size (increased by 1) as we want to make sure that we don't fetch too many non-needed data from the store.
For the full searches, we adapted and start with a page size equaling to 16 * numberOfDocuments. It's because there we fetch whole documents, so 16 is taken as the dummy number representing average number of leafs in each document. I am open for suggestions and adaptations of this number, or any other ideas. Bottom line is again to avoid fetching too many rows unnecessary from the data store.
For population or queries when we need complete doc or sub-docs, we still go for the max storage page size as we want to take all in one hop to the DB.
This is still a draft and requires some checks and possibly refactoring to:

See if we can avoid the +1 increase of the requested doc size in the document resolver (also min 1 in the Or resolver). This has to be tested against C and DSE, cause DSE could have some advantages here.
Check and confirm performance is way better now

Which issue(s) this PR fixes:
Fixes #1183
Checklist

[ ] Changes manually tested
[ ] Quick performance tests
[ ] More Java docs and clarifications
[x] Automated Tests added/updated

Just did some search performance tests wrt this PR. Seems that this fix will give us massive improvements as expected. I am gonna wrap up and set this up for review.
Setup

Local test
Stargate single node, with DSE single node on same machine
60 nosqlbench threads

Results:

Observations:

As expected huge speed gains in all cases where query storage page size was unnecessary high.
Small speed loss for the Singe in-memory eval can be ignored as this condition matches all documents, thus previous behavior wins as it's needing one query, vs two now. The reason we need two now is that we are guessing that there are 16 fields per document, and in my test there is 25. Thus, we need two hops here to get the document. In case of smaller docs, we would be faster.
ANDs are slower than ORs because:

they select lower amount of documents
they suffer from N+1 described here #1184

Test design has to be improved to select same amount of documents in each case, only then can we compare cases between each other. This is quite hard with nosqlbench.

@EricBorczuk have a look :arrow_up:


GPLv2 Combination Exception for the Apache 2 License

Add an exception to the Apache 2 licence to make it explicitly
compatible with GPLv2.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


ROM/RAM

It would be REALLY cool to have ROM/RAM although it WILL be really hard, it would be cool because you could make rom that writes to a togglable redstone lamp! if you cant do this that is completely fine.

Thanks for the suggestion, I really like it. But how many bits should the ROM have? 1-Bit would be pretty boring in my opinion.

Really sorry for the late response, but anyway i think there should be like a gui that you can set the number of bits and the two options are the data width (that is stored in the rom) and the address bit width (the number of bits the rom can store)
hopefully this isnt too hard to implement
one other suggestion is like d latch sr latch and stuff like that i think you should look into logisim-evolution if you dont already know what that is


Uncaught exception SpeechRecognitionError

How to resolve this error

@msgits2 @msftgits @eanders-MS @billba @danmarshall Can you help me resolving this issue.

Please don't randomly spam people to get help.
Also, a one sentence title isn't a bug report. Please report as many details as possible, sample code, etc.

As mentioned in https://github.com/Microsoft/BotFramework-WebChat/blob/master/samples/speech/index.html, I have used Native browser speech as a speechoption, then I am facing this error, Hope you can help to resolve that.

Hi Akhila, I agree with Bill - the best way to get help is to provide details.
Please see this article: https://docs.microsoft.com/en-us/bot-framework/channel-connect-webchat-speech
The "not-allowed" error usually means:

The user did dot allow the browser access to the microphone
The URL of the page that contains Web Chat begins with http:// instead of https://
The URL is a local file using the file:// protocol instead of http://localhost...

Okk @danmarshall. Thank you for your help,I will try resolving that.

Hi @Akhila9 - hope you got this issue resolved. I am closing for now but you can re-open if you are still seeing issues.


build: explicitly add tsc-wrapped to dev dependencies

The dependency on tsc-wrapped should be added explicitly. Our tooling uses the @angular/tsc-wrapped package directly and it currently only works because the @angular/compiler-cli has a dependency on it.
If not specified explicitly, the @angular/tsc-wrapped dependency might be a local dependency of the compiler-cli and our tooling won't be able to access it anymore.

Needs rebase

@andrewseguin Done.


add template script and documentation

[!NOTE]
We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged.

Description
This pull request includes an example installation script. This script should standardize the structure and best practices for creating installation scripts.
Key updates include:
Installation Conventions:

Added a detailed structure for installation scripts, including sections for file headers, initial setup, standard dependencies, file writing conventions, service management, cleanup, progress messages, version tracking, credentials management, directory structure, error handling, and final setup.

Example Installation Script:

Provided a template script (docs/templates/example-install.sh) that follows the conventions, demonstrating the setup of application variables, installation of dependencies, creation of directories, application installation, configuration, service creation, and cleanup.

[!WARNING]
This is a proposal aimed at simplifying the process of reviewing new scripts submitted by the community. The currently proposed conventions are based on my observations of already uploaded scripts and may not align with the most up-to-date standards. If changes are necessary, please provide your feedback in the comments.

Fixes # (issue)
Type of change
Please check the relevant option(s):

[ ] Bug fix (non-breaking change that resolves an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
[ ] New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed:

[ ] Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
[ ] Testing performed (I have tested my changes, ensuring everything works as expected)
[ ] Documentation updated (I have updated any relevant documentation)

Additional Information (optional)
Provide any additional context or screenshots about the feature or fix here.
Related Pull Requests / Discussions
If there are other pull requests or discussions related to this change, please link them here:

Related PR #

I find the idea of having some examples, as well as some solid documentation great. But i think der also needs to be an example for the corresponding container and json files in /ct and /json. There is an generator for the json files already, wich contains most of the needed informations anyway. It would probably worth it to also generate some sort of „boilerplate“ $APP.sh as well as $APP-install.sh files to reduce the copy and pasting.

will be coming back to this in the future with a better plan.


Compile ron data files into the game

The ron data files located in assets/data should not be able to be accessed and changed after the game is compiled. We should compile these with the rest of the game.

They are compiled into the game. Using include_bytes! puts the literal bytes in the binary.


Oauth Support

From the Wistia Docs.
The wistia-api ruby gem currently does not support oauth. We will be updating this in the future.

Oauth support for this gem would be extremely helpful when building integrations with Wistia.

Any word on this on when it may be available?


Correlation bug fix in variance prediction

The correlation function was not correctly called in the variance prediction of Kriging-based surrogate models: the function call was done on the option value directly, which is a str, resulting in a TypeError exception.

For preventing this kind of stuff in the future, maybe it is a good idea to include unit tests.

Coverage remained the same at 77.615% when pulling 718f2ba9ff3765b895a415840b40fa677e1d8e1c on jbussemaker:patch-1 into c00b9185fd5936eee8cb95159cfb76e4b8a55f78 on SMTorg:master.

Good catch! We definitely need more test coverage! Thanks.


aya,aya-obj: conversion from u32 to prog, map, and link type

I have a usecase that extracts program type information from from bpf_prog_info. 😺
This PR adds conversion from u32 to bpf_prog_type so that the type_ field in bpf_prog_info can map to the program type enum. This also implements Display for bpf_prog_type for condensed output format. 😺
Also, codegen and public-api appears to be acting a little funky for me.

So the scope of this PR expanded to include metadata info from bpf_map_info and bpf_link_info. I'm also planning to info for bpf_link_info__bindgen_ty_1.

I almost accidently deleted this PR bc of the branch name I had. Since the scope of this PR expanded, this will go under a new branch since the one I'm working on locally is wacky.


@salesforce/scv-connector-base or scv-connector-base

Could you please confirm which npm package we should be using for our integration of Service Cloud Voice.

@salesforce/scv-connector-base - https://www.npmjs.com/package/@salesforce/scv-connector-base

We have been using this one historically for the past 3+ Years

or

scv-connector-base - https://www.npmjs.com/package/scv-connector-base

Has been added recently past couple of weeks

Thank you
CC @rjanamanchi-sfdc @dlouvton @vivektikoo-force @rjanamanchi-sfdc @fernomac

Use
@salesforce/scv-connector-base
On Tue, Jan 30, 2024 at 12:28 PM Erik Stodola @.***>
wrote:

Could you please confirm which npm package we should be using for our
integration of Service Cloud Voice.

@salesforce/scv-connector-base -
@.***/scv-connector-base

We have been using this one historically for the past 3+ Years

or

scv-connector-base -
https://www.npmjs.com/package/scv-connector-base

Has been added recently past couple of weeks

Thank you
CC @rjanamanchi-sfdc https://github.com/rjanamanchi-sfdc @dlouvton
https://github.com/dlouvton @vivektikoo-force
https://github.com/vivektikoo-force @rjanamanchi-sfdc
https://github.com/rjanamanchi-sfdc @fernomac
https://github.com/fernomac
—
Reply to this email directly, view it on GitHub
https://github.com/salesforce/scv-connector-base/issues/47, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSWICVOAU54U3SVQOQVTUDYREUUHAVCNFSM6AAAAABCRUYIZ2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYDQMZZGMYTONI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you