[Security] Step by step to security threats of NFTS and possible solutions| hardware wallet

### Proposal Submission
Proposed title of the article
[Security] Step by step to security threats of NFTS and possible solutions| hardware wallet
Proposed article introduction
Whether online or offline, security is one of the major issues that we do have to tackle on our day to day bases.
Both companies and individuals are struggling to protect their individual properties and NFTs. As the metaverse keeps on a flight, the NFT
and digital avatars can be represented by NFTs and moved from one virtual world to another.
Allow me to demystify NFTS.
An NFT (the abbreviation for the non-fungible token ) stands for cryptographically unique tokens that are linked to digital
and sometimes physical contents, by providing proof of ownership.
Fungible means that the token is interchangeable. For example a dollar, you can swap a dollar with another one dollar and still own one dollar.
Non-fungible means they are unique. They cannot be swapped as no two NFTs are alike. A lot of content has seen turned to NFTs, including
digital arts, movies, and music. In 2021 NFTs has exploded to mainstream leading to the creation of DEFI (Decentralised Finance)
and DAO  ( decentralized autonomous organizations). In the future, the NFT could be used to provide deeds to companies,
sell tickets, and provide marriage certificates,
In this article, the reader will learn about the step-to-step threats on NFTs and implement proper possible solutions to protect their NFTs.
### Key takeaways

Understanding NFTs.
Understanding NFT's possible threats.
Possible NFTs security solutions.
What does the future holds for NFT.

Article quality
This in-depth tutorial will add so much value to the reader because along with learning about block chain, security threats of NFTs and possible
solutions, they will also learn about the future of NFTs.
References
N/A

Sounds like a helpful topic - let's please be sure it adds value beyond what is in any official docs and/or what is covered in other blog sites. (the articles should go beyond a basic explanation - and it is always best to reference any EngEd article and build upon it). @Sreign254
Please be attentive to grammar/readability and make sure that you put your article through a thorough editing review prior to submitting it for final approval. (There are some great free tools that we reference in EngEd resources.)
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.
Please be sure to double-check that it does not overlap with any existing EngEd articles, articles on other blog sites, or any incoming EngEd topic suggestions (if you haven't already) to avoid any potential article closure, please reference any relevant EngEd articles in yours. - Approved


Add MongoDB

Some MongoDB lists exist already, but they aren't referenced here, aren't maintained, and aren't complete at all anyway (see #477), so I decided to give it a try. :+1:
https://github.com/ramnes/awesome-mongodb

:+1:

Thanks!


Function prototype call and apply both don't work for a frozen context object

Example:
var obj = {foo: 42};
Object.freeze(obj);
function t() {console.log(this)}
t.call(obj);

As a result we get a runtime error (Uncaught TypeError: object[symbol] is not a function), because function hasn't been added to a context object, because the latter was frozen.

True, but I don't think any JS engine old enough to need this implements Object.freeze. I don't have the tweet at hand, but I did ask someone doing research on these old engines, and try/catch is not a thing. So this needs to be fixed as well, but I didn't get a VM running old Netscape and IE.

True.
Object.freeze has been shipped to Firefox 4 / IE 9 / Chrome 6 / Opera 12 / Safari 5.1, which are not so old enough browsers compared to Netscape.
Yet I think it is a good idea to test if object is immutable (for example, by adding a property to it and checking if it is there afterwards).
There should be another strategy in case of immutable context.
What do you think?

After looking around a bit, and reading the first version of ECMAScript-262 it seems like you can use the typeof operator to figure out if Object.freeze is available.
But according to MDN it was first implemented in JavaScript 1.1, which translates to Netscape 3.0.
Since this project tries to work in those ancient browsers that doesn't work. Both instanceof and try/catch is even younger, introduced in ECMAScript 3.

After reading some more, and finding the changelog for 1.1 I've realized I need 1.1 in order to support Function.prototype at all. So the typeof solution will work.

Not sure though how inheritance helps to resolve a following case:
var obj = {
    prop: 'value'
};

// Freeze the object by some way

function some (param) {
    return this === obj && param === 42;
}

/*
 * In that case this will point to an object inheriting from obj, but
 * that is not something we need
 */
some.call(obj, 42);


[Angular] Server Side Rendering Issue with angular "^4.2.6"

Update to angular 4.2.6 and update server side rendering
System.Exception: Call to Node module failed with error: Prerendering failed because of error: TypeError: Object prototype may only be an Object or null: undefined

I'm not sure what project you're upgrading from, or how exactly you're doing the upgrade, but I just tried it and it worked fine.
Specifically, I started with the version of the template in this repo (which is already on Angular 4.2.5), and then ran:

npm install --save-exact --save<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>webpack --config webpack.config.vendor.js
webpack

Then upon restarting the application, it all worked without problems.
I'll close this because it is working with the latest template. However if you track down the issue in your specific case and think it's a fault in some code in this repo, please let us know what you think we have wrong. Hope that's OK!

@SteveSandersonMS .. When will the new version be released? As the one on npm is still pointing to the old template :)

@pfrendo As soon as .NET Core 2.0 is released.


Added VolumetricBatchNormalization

The CUDNN R4 doc says batch normalization takes both 4D and 5D. Confirmed with NVIDIA that correct mode is CUDNN_BATCHNORM_SPATIAL for 3D batch normalization then copied and modified the SpatialBatchNormalization.lua. Also changed the bias vector size to match 3D.

Sorry this is wrong branch!


[k8s-extension] Update extension CLI to v1.2.2

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

k8s-extension


Allow dynamic S3 credentials

I would like to use several S3 buckets with several IAM users dynamically. But now the key and secret has to be defined in the Meteor settings which makes this impossible. The credentials are stored on the server.
Any chance this might be added in the near future? Is this possible at all when the S3 credentials are stored on the server and selected dynamically?

But now the key and secret has to be defined in the Meteor settings which makes this impossible.

That is not true. You can define credentials by setting the AWSAccessKeyId and AWSSecretAccessKey.
See https://github.com/CulturalMe/meteor-slingshot#aws-s3-slingshots3storage

+1 to this feature
@gsuess You are right but even if we set it in the directive, its not dynamic. The region and bucket keys should accept a function in lieu of a String so that different users files may be stored in different regions/buckets closest to their location.
region: function () {
  // Return region value based on this.userId
},

bucket: function () {
  // Return bucket value based on this.userId
},

@shantanubhadoria have you achieve this with any workaround,  i need the same functionality.


Move into core subproject

I followed instructions from https://docs.gradle.org/current/userguide/multi_project_builds.html
I will add api submodule by following https://docs.gradle.org/current/userguide/declaring_dependencies_between_subprojects.html
but I have some issues with the convention plugin.

@juherr - Can you please hold off on the next PR.. so that I can get my PR merged :) I dont want to keep re-basing this again and again :)


  The last 20 or so workflows have hung after completing the first 5/7 steps successfully and the next step was never triggered.  The previous ones all completed in ~20 mins, but the last 20 have hung for over 5 hours (so I just deleted them all).
in argo server the "workflow" was running/spinning, but some containers had finished and no subsequent containers/stpes were kicked off.
Diagnostics
What version of Argo Workflows are you running?
2.10.0
(no yaml since I deleted the workflows :( )

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Can you please attach the controller logs?

I do have logs from then still, but I don't know what I'd be looking for.  After looking and filterign manually for about half hour everything looks OK (to me).  I unfortunately dont have the references to the workflows that were hanging so I was just looking for things that might seem "weird".  Any pointers on what to look for?

Without either reproduction steps, or more diagnostics it is not possible to determine the cause of this problem.
When this reoccurs - can you please capture the logs?
Then can you try restarting the controller?

ok i had this issue happen again and i think i found some relevant logs
i was tracing the most recent hung pod (~40 minutes earlier) : ys-play-8846w
this location in the logs of the workflow controller is the last time this workflow is mentioned
restarting the workflow controller picks up the workflows from where they left off though 👍
time="2020-09-22T03:55:22Z" level=info msg="Alloc=177500 TotalAlloc=57750984 Sys=836015 NumGC=3600 Goroutines=166"
E0922 03:56:33.870098       1 event.go:263] Server rejected event '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"ys-play-msfdd.1636fe90550fbea0", GenerateName:"", Namespace:"argo-events", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ClusterName:"", ManagedFields:[]v1.ManagedFieldsEntry(nil)}, InvolvedObject:v1.ObjectReference{Kind:"Workflow", Namespace:"argo-events", Name:"ys-play-msfdd", UID:"1b54a65a-7c0d-44aa-b316-49d2bd973955", APIVersion:"argoproj.io/v1alpha1", ResourceVersion:"23549548", FieldPath:""}, Reason:"WorkflowTimedOut", Message:"ys-play-msfdd error in entry template execution: Deadline exceeded\ngithub.com/argoproj/argo/errors.New\n\t/go/src/github.com/argoproj/argo/errors/errors.go:49\ngithub.com/argoproj/argo/workflow/controller.init\n\t/go/src/github.com/argoproj/argo/workflow/controller/operator.go:103\nruntime.doInit\n\t/usr/local/go/src/runtime/proc.go:5222\nruntime.doInit\n\t/usr/local/go/src/runtime/proc.go:5217\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:190\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357", Source:v1.EventSource{Component:"workflow-controller", Host:""}, FirstTimestamp:v1.Time{Time:time.Time{wall:0xbfd27afd59c96ca0, ext:285891151377828, loc:(*time.Location)(0x29a41c0)}}, LastTimestamp:v1.Time{Time:time.Time{wall:0xbfd27afd59c96ca0, ext:285891151377828, loc:(*time.Location)(0x29a41c0)}}, Count:1, Type:"Warning", EventTime:v1.MicroTime{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}': 'the server was unable to return a response in the time allotted, but may still be processing the request (post events)' (will not retry!)
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-game-packaging-575nn
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-h62ck
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-hqnt9
time="2020-09-22T03:56:33Z" level=info msg="Processing workflow" namespace=argo-events workflow=ys-play-h62ck
time="2020-09-22T03:56:33Z" level=info msg="Processing workflow" namespace=argo-events workflow=ys-play-hqnt9
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-66cgc
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-hl9sj
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-llgfl
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-4tbmx
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-r6l6w
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-6skb2
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-mmw2g
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-zwzps
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-ll7hj
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-z42sk
time="2020-09-22T03:56:33Z" level=error msg="workflow timeout" error="the server was unable to return a response in the time allotted, but may still be processing the request (get pods)" namespace=argo-events workflow=ys-play-8846w
time="2020-09-22T03:56:33Z" level=info msg="Processing workflow" namespace=argo-events workflow=ys-play-4tbmx
time="2020-09-22T03:56:33Z" level=info msg="Processing workflow" namespace=argo-events workflow=ys-play-ll7hj
time="2020-09-22T03:56:34Z" level=info msg="insignificant pod change" key=argo-events/ys-play-6skb2-1526641406
time="2020-09-22T03:56:34Z" level=info msg="Workflow update successful" namespace=argo-events phase=Running resourceVersion=23553495 workflow=ys-game-packaging-cbz7v
time="2020-09-22T03:56:34Z" level=info msg="Workflow update successful" namespace=argo-events phase=Running resourceVersion=23553496 workflow=ys-game-packaging-rcjcz
E0922 03:56:34.984364       1 event.go:272] Unable to write event: 'Patch https://<IP_ADDRESS>:443/api/v1/namespaces/argo-events/events/ys-game-packaging-z64r7.1636fe5c383b29a3: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=""' (may retry after sleeping)
time="2020-09-22T03:56:34Z" level=error msg="workflow timeout" error="Get https://<IP_ADDRESS>:443/api/v1/namespaces/argo-events/pods?labelSelector=workflows.argoproj.io%2Fworkflow%3Dys-game-packaging-z64r7: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=\"\"" namespace=argo-events workflow=ys-game-packaging-z64r7
time="2020-09-22T03:56:34Z" level=error msg="workflow timeout" error="Get https://<IP_ADDRESS>:443/api/v1/namespaces/argo-events/pods?labelSelector=workflows.argoproj.io%2Fworkflow%3Dys-play-msfdd: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=\"\"" namespace=argo-events workflow=ys-play-msfdd
E0922 03:56:34.984466       1 ttlcontroller.go:114] error deleting 'argo-events/ys-game-packaging-bkn24': Delete https://<IP_ADDRESS>:443/apis/argoproj.io/v1alpha1/namespaces/argo-events/workflows/ys-game-packaging-bkn24: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=""
time="2020-09-22T03:56:34Z" level=error msg="workflow timeout" error="Get https://<IP_ADDRESS>:443/api/v1/namespaces/argo-events/pods?labelSelector=workflows.argoproj.io%2Fworkflow%3Dys-play-ll7hj: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=\"\"" namespace=argo-events workflow=ys-play-ll7hj
time="2020-09-22T03:56:34Z" level=error msg="workflow timeout" error="Get https://<IP_ADDRESS>:443/api/v1/namespaces/argo-events/pods?labelSelector=workflows.argoproj.io%2Fworkflow%3Dys-play-h62ck: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=\"\"" namespace=argo-events workflow=ys-play-h62ck
time="2020-09-22T03:56:34Z" level=error msg="Failed to labeled pod completed" err="Patch https://<IP_ADDRESS>:443/api/v1/namespaces/argo-events/pods/ys-play-msfdd-2648834506: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=\"\"" namespace=argo-events pod=ys-play-msfdd-2648834506
time="2020-09-22T03:56:34Z" level=error msg="workflow timeout" error="Get https://<IP_ADDRESS>:443/api/v1/namespaces/argo-events/pods?labelSelector=workflows.argoproj.io%2Fworkflow%3Dys-play-hqnt9: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=\"\"" namespace=argo-events workflow=ys-play-hqnt9
time="2020-09-22T03:56:34Z" level=error msg="workflow timeout" error="Get https://<IP_ADDRESS>:443/api/v1/namespaces/argo-events/pods?labelSelector=workflows.argoproj.io%2Fworkflow%3Dys-play-5ckzt: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=\"\"" namespace=argo-events workflow=ys-play-5ckzt
time="2020-09-22T03:56:34Z" level=error msg="workflow timeout" error="Get https://<IP_ADDRESS>:443/api/v1/namespaces/argo-events/pods?labelSelector=workflows.argoproj.io%2Fworkflow%3Dys-play-4tbmx: http2: server sent GOAWAY and closed the connection; LastStreamID=2693, ErrCode=NO_ERROR, debug=\"\"" namespace=argo-events workflow=ys-play-4tbmx

Maybe fixed by #4103

Will be fixed in v2.11.1

Fixed.


[BUG]: Incorrect path for API request

When JS frontend tries to retrieve options data for Attach Field, it goes to not existing route.
When inspecting network request in dev console, it show api/method/frappe_better_attach_control.api.get_options, but there is no api controller selected. It should be api/method/frappe_better_attach_control.api.field.get_options.
I think, starting in https://github.com/kid1194/frappe-better-attach-control/blob/04cb21b656595cd80f70d72e9779ca36fb506324/frappe_better_attach_control/public/js/controls/attach.js#L305-L306 there should by:
request(
  'field.get_options',

@qbadev Hey bro..
Sorry for the late reply, and thank you for reporting this bug..
As you can see below, the field file is fully imported so calling frappe_better_attach_control.api.get_options instead of frappe_better_attach_control.api.field.get_options should be fine but I think that it doesn't work like this in frontend..
https://github.com/kid1194/frappe-better-attach-control/blob/04cb21b656595cd80f70d72e9779ca36fb506324/frappe_better_attach_control/api/__init__.py#L8
Anyway, thanks to you I will make this change in the frontend js files..
Best regards..

Path in frontend must be strictly valid against frappe api pattern and rules, I guess. I tested it out already: path field.get_options works fine.

There might be other places that require correction in frontend. I am not sure, but I recall other errors in dev console in browser indicating similar issue.

@qbadev Hey bro..
Can you please post a screenshot for all the errors you see in console or anywhere else?
Your help is much appreciated 😁
Best regards..

When clicking Attach Image control button in the form, nothing happens visualy, but the error shows up in console log.
attach.js:125 Uncaught TypeError: Cannot read properties of undefined (reading 'allowed_file_types')
    at attach.js:125:33
    at frappe.ui.form.ControlAttachImage.on_attach_doc_image (attach.js:135:13)
    at frappe.ui.form.ControlAttachImage.on_attach_click (attach.js:110:37)
    at HTMLButtonElement.click (attach.js:9:9)
    at HTMLButtonElement.dispatch (jquery.js:5135:27)
    at Rt.handle (jquery.js:4939:28)
(anonymous) @ attach.js:125
on_attach_doc_image @ attach.js:135
on_attach_click @ attach.js:110
click @ attach.js:9
dispatch @ jquery.js:5135
Rt.handle @ jquery.js:4939

It is a result of not receiving proper data from ajax request.

I also noticed that Your api field file algorithm does not check tabCustom Field table for possible values.
Another issue is that JS FE script tries to check field named image hardcoded, while one can have multiple fields in one form with totally different names.

@qbadev Hey bro..
Sorry for the late reply..
Regarding the console error, I don't know exactly why its happening so I have added a simple check in order to avoid the error..

I also noticed that Your api field file algorithm does not check tabCustom Field table for possible values.

You have noticed a great mistake of mine 😅
I have added the Custom Field query..

Another issue is that JS FE script tries to check field named image hardcoded, while one can have multiple fields in one form with totally different names.

I can't really find the exact code that you are referring to so can you please help me by pointing it out..
I have created this long time ago and when I look at the codes now I feel that it wasn't me who wrote them 😅
Maybe I will recreate this plugin and make it much more better..
Thanks a lot bro for your help. I'm really grateful..
Best regards..


Python Bindings setup outdated? Can't run e2e keras keyword_spotting_streaming_test.py

I tried to install and use the IREE Python bindings. I build and set up IREE as described in Get Started Python.
To verify my installation is ran the tests.
All tests are passing when I run the command ctest -L bindings/python as well as
python ../iree/integrations/tensorflow/e2e/simple_arithmetic_test.py \
    --target_backends=iree_vmla --artifacts_dir=/tmp/artifacts

is passing (skipping SimpleArithmeticTest.test_session).

In the Get Started docs there is a section about "Installing and Packaging". However the file python bindings/python/setup.py does not exist.
There are some setup.py files that are located in:
./bindings/python/pyiree/compiler2/setup.py
./bindings/python/pyiree/tools/tf/setup.py
./bindings/python/pyiree/rt/setup.py

So I just installed all of them as described.
Now I wanted to run the cnn e2e test that is listed in tensorflow_coverage/language_and_speech_coverage.md.
However running python ../integrations/tensorflow/e2e/keras/keyword_spotting_streaming_test.py from the iree-build directory will produce the following error:
Traceback (most recent call last):
  File "../iree/integrations/tensorflow/e2e/keras/keyword_spotting_streaming_test.py", line 25, in <module>
    from kws_streaming.layers import modes
ModuleNotFoundError: No module named 'kws_streaming'

EDIT: I cloned the kws_streaming module from the Google Research Repository and added it to the PYTHONPATH. The e2e test is now working.
Maybe this should be documented as well. My issue itself is resolved.

Thank you for the report. Yes, there are some doc bugs that need updating. @phoenix-meadowlark would you mind taking a pass through the documented steps from scratch and make sure they are up to date?
Also, I think the kws issue stems from missing a test only dependency. Phoenix: how does the CI resolve this? Should we have a requirements.txt somewhere for test deps and make sure we direct both systems and people to use it?

Ok, the issue is that the kws_streaming python package is not installed automatically in our OSS releases. Also, it seems to only be published as part of the google-research repo, which must be checkout out manually.
The following worked for me (assuming that you are checking out to $HOME/src):
cd $HOME/src
git clone https://github.com/google-research/google-research
export PYTHONPATH=$PYTHONPATH:$HOME/src/google-research

We should update docs and or have a script to pull/configure such test-only deps.

Ah right, we were linking that in via a bazel http archive so that we wouldn't have to add an IREE-wide dep on google-research, but that disappeared with the rest of the bazel goo. The CI doesn't address this because we're not running the tests.
It might be possible to add the boiler plate to allow pip install git+https://github.com/google-research/google-research/kws_streaming (depends on if git(hub) will let me target a subdir and if I can make python be okay with setup.py being inside of kws_streaming/). That would make the CI happy and allow people to run the tests as a part of development without managing a google-research clone in their pythonpath. I'll investigate.

If serious, you may want to talk to Oleg about promoting it to a top-level project, which wouldn't be too hard. Then either submodule or pip install it.

For local use, I have gotten this working by:
cd ~/src
git clone https://github.com/google-research/google-research.git

Then from the CMake build directory:
ln -s ~/src/google-research/kws_streaming bindings/python/

Also requires an additional package tensorflow-model-optimization which I am adding to the integrations/tensorflow/bindings/python/build_requirements.txt`.
We should document and/or script this somewhere.

Also seems to have some sensitivity to the precise keras version. We need to triage this more.

@stellaraccident Another old one, still active?

This issue looks stale, closing.


selective_scan_cuda

I'm using linux and while installing, I ran into two problems.
(1) Using “cd kernels/selective_scan && pip install .” command, I encountered the following problem.

（2）I installed causal-conv1d and mamba_ssm following this code.

When installing, no error is reported, but this error is reported when running the code, which may also be based on the fact that problem (1) is not resolved.

This problem has been bothering me for a long time, I've reinstalled it many times and it still hasn't been solved, I'm asking for your help, thank you very much!

The same issues

您好，您的邮件我已收到，我会尽快回复的，谢谢！


Add Binance

Url:
https://www.binance.com/restapipub.html
Tasks:

[ ] Tests
[ ] REST Wrapper
[x] Pair Formatter
[ ] Interface

Hi, Interested in picking up this ticket. new to open source :)

Hey @Mukz95 !
Great to hear you want to contribute! I'd suggest to first get acquainted with the code base of BitEx. Take a look at how we do things around here. If you feel like you have a grasp of what's going on (or if you don't, do not hesitate to ask!) and fork the repository.
Start committing your code (be sure to read [bitex/CONTRIBUTING.md](https://github.com/nlsdfnbch/bitex/blob/master/CONTRIBUTING.md) for requirements) and once you're done simply submit your pull request.
I'll check it out as soon as I can and leave feedback if it needs improvements / fixes, or simply merge it if everything's fine.
Also note that you do not have to submit a PR containing ALL the above points, but must always supply tests for your new code (so you may submit a new PairFormatter with tests, without having to supply REST wrappers or interface functions, etc).

Yes just trying to understand the codebase, I was wondering
if  https://github.com/Mukz95/bitex/blob/master/tests/formatters.py tests pass? I was looking into the code didn't see how they were supposed to pass, unless i have missed something or are they meant to fail for now and pass when implementation takes place?

Actually, I'm not sure - I've added them at some point and somewhat abandoned the tests on master right after - but these changes are all meant for the 2.0 release, hence you should develop from master (there everything should work - there's also more tests).
Sorry it's all a little confusing. Trying to clean it up for excellent people like you willing to contribute!

@Mukz95 are you planning on continuing work on this one? If not, I would be interested in picking up the rest of this

Actually... I'm afraid that I already started on this one.
I've got the REST part working - I need to work through the interface class now.
@nlsdfnbch would you like me to PR the REST part, or wait until I can do both the REST and the Interface?

@HughMacdonald , either way is fine!

Done. Initial REST api implementation in #120

How do you like to deal with additional required parameters to methods?
For example, both order_status and cancel_order on Binance are going to require the pair that the order is on. Am I okay to add this to the method definition, or do you want to ensure that all method definitions are identical between exchanges, and insist on the extra parameters being passed in through kwargs?
Thanks

Actually, now all in #122. I took it in a direction that I felt okay with - happy to change it if you'd prefer.
Binance has the basic methods implemented, but I want to go through and put additional methods in place.

Merged! Thanks @HughMacdonald!

Has this been merged yet? We are waiting.

It has been merged already. It may not be on pypi yet - feel free to pip install via the dev branch to get the latest version for now


Create new factory method for forecasting via reduction

Reference Issues/PRs
See #220.
What does this implement/fix? Explain your changes.
Created new factory method that combines the two current factory methods into one.
What should a reviewer concentrate their feedback on?
Is this new factory method tidier, for both users and contributors?
Any other comments?
For all contributions

[ ] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] I've added unit tests and made sure they pass locally.

Should I add tests for this factory method?

Also, technical question about github, could I accept your suggested change and have auto-formatting within github?

Hi @Lovkush-A - yes, if you want to add a test that would be much appreciated!

@mloning
Testing. OK, I will add some sort of tests. I just looked and there is currently only one test (of pipelines) for the compose subfolder in forecasting. Does that mean we don't know whether all the other stuff in compose actually works?  Also, the test for the pipeline does not use pytest, unlike the other tests I have seen for forecasting. Should I create an issue for lack of testing in compose?
Formatting. Alright, good to know.
Next step. I still need to do multioutput! Multioutput should be straightforward though, I think I can copy and paste the direct reducer and change a few lines.  I am happy to work on exogenous variables after that. For exogenous variables, am I correct in thinking that we just need to add extra features to the dataframe - ensuring we line up the rows appropriately?

@Lovkush-A oh yes forgot about multi-output!
Regarding exogenous features yes, that's right, I had an idea how to restructure the code (see #390).
Regarding testing, a simple test that calls the function with different input arguments would be sufficient for now.

@Lovkush-A let me know if you're happy with this to be merged, will leave it open a bit longer in case others want to comment.

@mloning Not ready for a PR yet. I have written some tests but am struggling to get VSCode's python testing to work. I will push another commit later today with the tests later today.

Are there any time series regression algorithms? I ask because I would like to test the ts-regressor scitype of the factory method.

@Lovkush-A there is a TimeSeriesForestRegressor in the regression module I believe, otherwise using a pipeline with a Tabularizer and any regressor from scikit-learn should also work.

@mloning I used pipeline with tabularizer.  As far as I am concerned, this is ready to be pulled in.


S4 [Task] Define AAD Group Protobuf

Task
Define AAD Group Protobuf

Task Title
Define AAD Group Protobuf

User Story
#49

Epic
#35

T-shirt size default is S(mall)
S

Story Points - Fibonacci (1,2,3,5)
1

Description
Define AAD User data protobuf

Business Need (the why):

Applications or Systems impacted

Dependencies

Assumptions

Scrum team concluded not valid. closing.


Expose Dockstore link to pipeline used for analysis

Benedict brought this up during demo. Will fill in details later.

@hannes-ucsc Spike 1 to fill in details

@hannes-ucsc Spike 1 to fill in details

@kbergin, my PI suggested this. It makes total sense but it is a long game feature since it may require a metadata schema change, most likely to analysis_protocol. Is there a even a Dockstore image that we can point to for the pipelines that you use for analysis?

Hi @theathorn, is there a blocker in Azul for this?

Obsolete.


Fix ModifyBoost in calculateStat

It doesn't use the Pokemon's boosts.

The crashes are my fault too, aren't they
I should just be blocked from making pull requests


JavaFX - Exception in Application start method

Stack trace:
Exception in Application start method
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at com.sun.javafx.application.LauncherImpl.launchApplicationWithArgs(Unknown Source)
	at com.sun.javafx.application.LauncherImpl.launchApplication(Unknown Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at sun.launcher.LauncherHelper$FXHelper.main(Unknown Source)
Caused by: java.lang.RuntimeException: Exception in Application start method
	at com.sun.javafx.application.LauncherImpl.launchApplication1(Unknown Source)
	at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$147(Unknown Source)
	at com.sun.javafx.application.LauncherImpl$$Lambda$48/1732398722.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException: Location is required.
	at javafx.fxml.FXMLLoader.loadImpl(Unknown Source)
	at javafx.fxml.FXMLLoader.loadImpl(Unknown Source)
	at javafx.fxml.FXMLLoader.loadImpl(Unknown Source)
	at javafx.fxml.FXMLLoader.loadImpl(Unknown Source)
	at javafx.fxml.FXMLLoader.loadImpl(Unknown Source)
	at javafx.fxml.FXMLLoader.load(Unknown Source)
	at application.Main.start(Main.java:14)
	at com.sun.javafx.application.LauncherImpl.lambda$launchApplication1$153(Unknown Source)
	at com.sun.javafx.application.LauncherImpl$$Lambda$51/1778973910.run(Unknown Source)
	at com.sun.javafx.application.PlatformImpl.lambda$runAndWait$166(Unknown Source)
	at com.sun.javafx.application.PlatformImpl$$Lambda$44/1051754451.run(Unknown Source)
	at com.sun.javafx.application.PlatformImpl.lambda$null$164(Unknown Source)
	at com.sun.javafx.application.PlatformImpl$$Lambda$47/813155481.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sun.javafx.application.PlatformImpl.lambda$runLater$165(Unknown Source)
	at com.sun.javafx.application.PlatformImpl$$Lambda$46/1775282465.run(Unknown Source)
	at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(Unknown Source)
	at com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
	at com.sun.glass.ui.win.WinApplication.lambda$null$141(Unknown Source)
	at com.sun.glass.ui.win.WinApplication$$Lambda$37/1109371569.run(Unknown Source)
	... 1 more
Exception running application application.Main

How can I solve this issue ?

Please show your source code I suspect you have Caused by: java.lang.NullPointerException: Location is required.according to the log which means you have caught null pointer error....

Please show your source code I suspect you have Caused by: java.lang.NullPointerException: Location is required.according to the log which means you have caught null pointer error....

could you help me?i meet the same problem.


Old version of docker (<20) does not format to JSON

Old version of Docker does not allow for --format to be JSON
Incorrect information about the docker ps -a and docker images

branch attached: bugfix/JSONDecodeError_notErrorField


Add OpenHCL servicing tests (petri)

It seems we're missing basic OpenHCL servicing tests using our integration test.
This came up when discussing other topics with @chris-oo , and he suggested I file an issue. I'm happy to do so, but don't mean to imply this is our only test gap :)

Dup of #75


Add USR2 signal to reread the config

Short Description:
Usage: kill -USR2
Now we can send USR2 signal instead of restart the program

LGTM

But my suggestion getting that signal name from config.json. Beucase i have 20 working bot if i use that when i send this signal it's will kill all @douglascamata @solderzzc

@Zgrkaralar but why would you send that SIGNAL to all processes instead of just the process you want to reload the config?

Ah ya, the logic should implemented on main function.
Thanks for that suggestion.
Also add the code on if __name__ == '__main__' caused the application run forever.
My bad.

@LIQRGV please update files accordingly, also recreate PR to merge into dev branch


Consider making types non_exhaustive

The need to make a breaking release every time a new field is added to a type causes a lot of churn in dependent crates (see for instance https://github.com/brendanzab/codespan/issues/124).
We could reduce this significantly (perhaps completely) by making all enums and structs non exhaustive through adding an extra variant to all enums and an extra field to all structs which is not meant to be referred to directly.
pub enum Enum {
    A,
    B(String),

    #[doc(hidden)]
    _NonExhaustive,
}

#[derive(Default)]
pub struct Struct {
    pub a: i32,
    pub b: String,

    #[doc(hidden)]
    #[serde(skip)]
    pub _non_exhaustive: (),
}

Uses of any enums would then need to add a catch all case on each match which errors on unknown variants and use Struct { a, b, .. } when matching on structs. Further, constructing any struct would require Default::default() + functional record update which is perhaps the biggest ergonomic loss.
Struct {
    a: 1,
    b: "".into()
    .. Default::default(),
}

I haven't decided yet if I think being able to move to 1.0 is worth the ergonomic loss but I wanted to float the idea here.
@Xanewok
@matklad
@brendanzab
@autozimu
(more?)

There is a #[non_exhaustive] which is in FCP https://github.com/rust-lang/rust/issues/44109 but since it doesn't allow for structs with the attribute to be constructed we can't use it anyway (well, enums could still use it I believe)

Note that with private fields or #[non_exhaustive] either, FRU doesn't work with structs, so construction would require constructors or builders rather than structural construction.

I feel like there's no really good solution here. Backwards compatibility of the wire format does not translate nicely to the backwards compatibility of the Rust API (mostly, to due to the impedance mismatch between TypeScript's structural and Rust's nominal type systems).
My current view is that, instead trying to share lsp types as a whole, crates that act as building blocks for LSP servers/clients should just vendor the relevant types. For example, my lsp-server crate does not use lsp_types, and instead just looks manually for initialized, exit notifications.
And yes, I totally did make a typo there once, which broke rust-analyzer, but, with the typo fixed, I feel like this code won't be changed in the future.
Similarly, crates for diagnostics could vendor only diagnostics-related structs, and crates for VFS can vendor only change-notification related structs.
In other words, I advocate for "worse is better" approach in this instance :)

Note that with private fields or #[non_exhaustive] either, FRU doesn't work with structs, so construction would require constructors or builders rather than structural construction.

Yes, #[non_exhaustive] can't be used (https://github.com/gluon-lang/lsp-types/issues/117#issuecomment-537492404). But having a public, #[doc(hidden)] field does work with FRU.
Some simple types like https://docs.rs/lsp-types/0.61.0/lsp_types/struct.Location.html could fairly reasonably be seen as types which won't have fields added and could be spared the non-exhaustiveness. After all even if they do get a field it is not the end of the world if a 2.x has to be released, we just need to make breaking releases unlikely enough to not be much of an issue.

Since these types are inherently structural, maybe it'd make more sense to wait for https://github.com/rust-lang/rfcs/pull/2584 instead?

@Xanewok I don't see how would that help, what am I missing? Most types already have names in the LSP definition in any case.

I feel like there's no really good solution here. Backwards compatibility of the wire format does not translate nicely to the backwards compatibility of the Rust API (mostly, to due to the impedance mismatch between TypeScript's structural and Rust's nominal type systems).

It isn't really structural vs nominal that is at play here, just that typescript (or in a way just plain JSON which is the actual data format) have data which are free to be extended with additonal fields or cases.

My current view is that, instead trying to share lsp types as a whole, crates that act as building blocks for LSP servers/clients should just vendor the relevant types. For example, my lsp-server crate does not use lsp_types, and instead just looks manually for initialized, exit notifications.

That works well in many cases such as that where the crate doesn't leak the LSP-types outside of its API (notably, lsp-server could just use an arbitrary version of lsp-types without affecting any users of the crate other than potentially needing to compile multiple versions of lsp-types).
It is always possible to vendor the types when needed, the question here is whether doing this change, which would make 1.0 possible, does not adversely affect crates using lsp-types when they do not need interop via lsp-types

It isn't really structural vs nominal that is at play here, just that typescript (or in a way just plain JSON which is the actual data format) have data which are free to be extended with additonal fields or cases.

You're right - apart from structural types we'd need structural subtyping (which is, rather, what makes these TS-side definitions extendable IIUC), which I believe is out of scope in the RFC I linked previously. Sorry.

I looked it this a bit, but there are types which have fields without a sensible default so we can't use Default + functional record update (FRU).
Avoiding churn could perhaps be avoided by crates specifying a version range instead. Still forces some churn, but it would only be for crates like codespan and not downstream users of codespan (@brendanzab )

Yeah, I'm really thinking I want to avoid direct dependencies on lsp-types alas, which might cause me to want to deprecate both codespan and codespan-lsp entirely in favour of just supporting codespan-reporting. It just causes too much churn for me to keep up with. :(

Could you perhaps explain/give an example for what you mean by "specifying a version range instead" - I feel like I missed something there.

In Cargo.toml you can do lsp-types = "0.70>=,<0.81". Since codespan-lsp doesn't construct any types that has changed recently it should work with a wide range of versions. Still forces one to update the maximum version every now and then but that can be released  as non-breaking versions.

Ahhh, that is indeed handy!

Yeah, I'd be pretty conservative with the version bounds, only bumping when asked, and only specifying it up to a currently released version.

I'm wondering if we should put this in the README: "Note that due to frequent updates, we recommend library authors to specify a version range... (post example, with guidelines for how and when to update bounds)". cc. @ebkalderon

This sounds like a good solution! I think this could be a great solution for codespan-lsp, which only constructs two relatively unchanging types as part of its public interface. I'm not completely sure about tower-lsp, however, since it couples closely to lsp-types by design and uses quite a few of its types internally. I'll do a bit of testing to make sure the >=0.73,<0.81 version range works as expected.

I probably wouldn't use >=0.73,<0.81 because it's only on 0.73 right now. That's kind of what I was saying about guidelines. For >=0.73,<0.81 you're kind of asserting that all of the changes from 0.73 to 0.81 will work with tower-lsp (based on what you're using in that library), but you can't really assert that if those versions haven't been published yet! So if Marwes publishes a change in 0.74 that breaks tower-lsp, then consumers of tower-lsp won't be able to compile their code.

Tbh I still think there might be value in making the definitions in lsp-types forwards-compatible if reasonably possible (without making the datatypes too annoying to work with), because the it may help to make this kind of decision a tad less error prone.

Makes sense to me, yeah. I like your idea of selecting a version range from a past version up to the currently released version. I think that could be a good strategy, provided that the number of types your library directly references or constructs is relatively small.

I've made a PR on codespan-lsp that uses a version ranges for lsp-types. I'm still rather wary of this though, as it could potentially break cargo update if people get it wrong, which is pretty unforgivable from my perspective (have had enough bad experiences with non-Cargo package managers recently that tend to do this).


Goal to MiR doesn't work

Hi,
I was able to connect to both MiR100 and MiR250 using the mir_robot package. When listening to the different topics I received the correct information, and publishing I was able to move both robots using the cmd_vel topic. But when I tried to send a move to position goal it didn't work: "move_base_simple/goal" subscriber didn't do anything.
If this happened to anyone else I would really appreciate the help,
Thanks a lot.

This sounds like it might be related to #62. Which version of the MiR software are you running? For reference, we are running <IP_ADDRESS> (I believe), and "move_base_simple/goal" should be working I believe (but I haven't tested it in a long time).

I'm running different versions depending on the robot:
MIR100 - <IP_ADDRESS>
MIR250 - <IP_ADDRESS>
I was using the correction made in #62 and I tried to publish both the topic as well as the action from the command line and that didn't work wither.
Thanks for helping out!

What do you mean, you tried the correction made in #62? That's already merged, so no need for you to do anything.
Which version of this repo are you using? The one from the binary packages, or from source (and if from source, which git commit and did you make any changes)?

I didn't make any changes. Just pointed out that I was using the corrected version.
I tried the binary packages on ubuntu 18.

Aaah, so that's your problem then. Ubuntu 18.04 still has ROS melodic, and the latest release into melodic (1.0.8) was made almost 2 years ago, on 2021-06-11.
It would be best if you could instead run Ubuntu 20.04 with ROS noetic so you get the newest version.
Alternatively you could try to run the noetic branch from source on ROS melodic, but that's going to need some adjustments because melodic is still Python 2, whereas noetic is Python 3.

Oh, good to know. Thanks' i'll try it out and let you know

Just FYI: I've just confirmed that the "move_base_simple/goal" (published from RViz) works with our MiR100 robot, software version <IP_ADDRESS>, mir_robot branch noetic (1d7f6c2).

ok thanks. I'll update my ubuntu and ROS and let you know.

I have the same problem. I can't move the robot with /cmd_vel or /move_base.
I have Ubunto 20 and the robot is mir250 with software version 2.14.

@DanyResasco : If you can send me the MiR software upgrade image to 2.14, I can have a look.

Forgive my ignorance but How can I get the image?

If you upgraded the MiR software yourself, you should have a file called something like MiR_Software-2.13.3.mir. This is the one I need. If your MiR already came preinstalled with this version (or a technician installed it), then you probably don't have this file.

Unfortunately the Mir came directly with the new software.

@mintar also this new version, the manual mode get disabled if u don't move the robot for few seconds.
The webpage and some messages/actions are different from your package

Are you sure you are using the most up to date noetic version of this package? There were some changes to the cmd_vel topic years ago that we had to adapt to (https://github.com/DFKI-NI/mir_robot/issues/45#issuecomment-651892529), but I would be surprised if they changed it again.

I installed using sudo apt install ros-noetic-mir-robot . I'm not sure how can I move it via ros if the manual mode gets disconnected all the time.
For now, I changed my ROS_MASTER_URI to the MIR's IP and try to see the difference with your package, one example is if I use your package I don't have data from sensors, while with the ROS_MASTER_URI I can listen to the topics.

I installed using sudo apt install ros-noetic-mir-robot.

Ok, that's good then.

I'm not sure how can I move it via ros if the manual mode gets disconnected all the time.

You can still move it via ROS even if the manual mode gets disconnected, that doesn't matter.

For now, I changed my ROS_MASTER_URI to the MIR's IP and try to see the difference with your package, one example is if I use your package I don't have data from sensors, while with the ROS_MASTER_URI I can listen to the topics.

Ok, then the first step would be getting data from the sensors. It sounds like my package didn't connect properly to the MiR at all.
What's your MiR IP? If it's not the default (<IP_ADDRESS>), then you have to adjust mir_hostname accordingly (roslaunch mir_driver mir.launch mir_hostname:=192.168.xxx.xxx).
What's being printed in the console?

if I export the ROS_MASTER_URI=http:/<IP_ADDRESS>:11311 I can get the sensor data (rostopic echo) and display them in rviz.
My problem right now is that the robot doesn't move.
I tried with the command line rostopic pub /cmd_vel . I can see the msg is modified with the value I publish but the robot stays still.

@mintar wiht roslaunch mir_driver mir.launch I can see ROS_BRIDGE CONNECTED then the logs regarding which msgs is subscribing to (some are warnings because they changed the name)

@mintar my bad, I have the <IP_ADDRESS> MIR250
[INFO] [1687369617.386966]: [/mir_bridge] publishing topic 'LightCtrl/us_list' [sensor_msgs/Range] [WARN] [1687369617.387829]: [/mir_bridge] topic 'LightCtrl/us_list' is not published by the MiR! [INFO] [1687369617.389313]: [/mir_bridge] publishing topic 'MC/currents' [sdc21x0/MotorCurrents] [WARN] [1687369617.390120]: [/mir_bridge] topic 'MC/currents' is not published by the MiR! [INFO] [1687369617.391713]: [/mir_bridge] publishing topic 'MissionController/CheckArea/visualization_marker' [visualization_msgs/Marker] [INFO] [1687369617.393524]: [/mir_bridge] publishing topic 'SickPLC/parameter_descriptions' [dynamic_reconfigure/ConfigDescription] [WARN] [1687369617.394519]: [/mir_bridge] topic 'SickPLC/parameter_descriptions' is not published by the MiR! [INFO] [1687369617.396428]: [/mir_bridge] publishing topic 'SickPLC/parameter_updates' [dynamic_reconfigure/Config] [WARN] [1687369617.397461]: [/mir_bridge] topic 'SickPLC/parameter_updates' is not published by the MiR!  [INFO] [1687369617.406128]: [/mir_bridge] publishing topic 'camera_floor/background' [sensor_msgs/PointCloud2] [WARN] [1687369617.406973]: [/mir_bridge] topic 'camera_floor/background' is not published by the MiR! [INFO] [1687369617.408528]: [/mir_bridge] publishing topic 'camera_floor/depth/parameter_descriptions' [dynamic_reconfigure/ConfigDescription] [WARN] [1687369617.409743]: [/mir_bridge] topic 'camera_floor/depth/parameter_descriptions' is not published by the MiR! [INFO] [1687369617.411686]: [/mir_bridge] publishing topic 'camera_floor/depth/parameter_updates' [dynamic_reconfigure/Config] [WARN] [1687369617.412913]: [/mir_bridge] topic 'camera_floor/depth/parameter_updates' is not published by the MiR! [INFO] [1687369617.414906]: [/mir_bridge] publishing topic 'camera_floor/depth/points' [sensor_msgs/PointCloud2] [WARN] [1687369617.415768]: [/mir_bridge] topic 'camera_floor/depth/points' is not published by the MiR! [INFO] [1687369617.417264]: [/mir_bridge] publishing topic 'camera_floor/filter/visualization_marker' [visualization_msgs/Marker] [WARN] [1687369617.418110]: [/mir_bridge] topic 'camera_floor/filter/visualization_marker' is not published by the MiR! [INFO] [1687369617.419652]: [/mir_bridge] publishing topic 'camera_floor/floor' [sensor_msgs/PointCloud2] [WARN] [1687369617.420488]: [/mir_bridge] topic 'camera_floor/floor' is not published by the MiR! [INFO] [1687369617.421962]: [/mir_bridge] publishing topic 'camera_floor/obstacles' [sensor_msgs/PointCloud2] [WARN] [1687369617.422870]: [/mir_bridge] topic 'camera_floor/obstacles' is not published by the MiR!  [INFO] [1687369617.437751]: [/mir_bridge] publishing topic 'laser_back/driver/parameter_updates' [dynamic_reconfigure/Config] [WARN] [1687369617.438630]: [/mir_bridge] topic 'laser_back/driver/parameter_updates' is not published by the MiR! [INFO] [1687369617.440196]: [/mir_bridge] publishing topic 'laser_front/driver/parameter_descriptions' [dynamic_reconfigure/ConfigDescription] [WARN] [1687369617.441082]: [/mir_bridge] topic 'laser_front/driver/parameter_descriptions' is not published by the MiR! [INFO] [1687369617.442855]: [/mir_bridge] publishing topic 'laser_front/driver/parameter_updates' [dynamic_reconfigure/Config] [WARN] [1687369617.443758]: [/mir_bridge] topic 'laser_front/driver/parameter_updates' is not published by the MiR! [INFO] [1687369617.445737]: [/mir_bridge] publishing topic '/map' [nav_msgs/OccupancyGrid] [INFO] [1687369617.447116]: [/mir_bridge] starting to stream messages on topic '/map' [INFO] [1687369617.449050]: [/mir_bridge] publishing topic '/map_metadata' [nav_msgs/MapMetaData] [INFO] [1687369617.450707]: [/mir_bridge] publishing topic 'mir_amcl/parameter_descriptions' [dynamic_reconfigure/ConfigDescription] [WARN] [1687369617.451560]: [/mir_bridge] topic 'mir_amcl/parameter_descriptions' is not published by the MiR! [INFO] [1687369617.453144]: [/mir_bridge] publishing topic 'mir_amcl/parameter_updates' [dynamic_reconfigure/Config] [WARN] [1687369617.453976]: [/mir_bridge] topic 'mir_amcl/parameter_updates' is not published by the MiR!
Is the emergency stop deactivated?
What colors do the MiR LEDs have?
Does the MiR web interface show any errors?
What's the output of rostopic info /cmd_vel?


xps questions

what is method
should peak not rather be peaks?

peaks is always singular

change method to experiment


Remove PR comments

This should be done with a separate action.

Fixed with https://github.com/badsyntax/github-action-aws-cloudformation/pull/14


collection of errors related to simulation and WeDo

the null value is not handled at all. It is unclear, how it should behave. See #21  <- same for master, not relevant here
[x] the switch led on (to red e.g.) crashes the simulation
[x] Roberta Mobile App freezes, if a loop is used without "wait ms" block in it. See #192
[x] WeDo has only one timer, but can reset five. See #212
[x] Functions with deactivated blocks may not be executed correctly in the simulation. See #198
[ ] WeDo-Program with "play frequency Hz" block is not be executed. See #191
Simulation does not open if ternary block, with empty branch, is in task. See #203 <- same for master, not relevant here
[x] Testing multiple robots in simulation
[ ] Unify the simulation constants and interpreter constants
[x] Set Motor Port B speed % (EV3)
[x] Invalid statement op: math change
[x] Invalid statement op MathPropFunct, TextAppend
[x] Using for-each leads to bug in opening the sim
[x] Count loop terminates if i is used in if without else stmt
[x] Calliope "turn LED internal on" turns right wheel to white
[x] EV3 math power does nothing (invalid supOp POWER)
[x] Calliope set brightness does nothing
[x] Calliope "debug" does not print to console
[x] EV3 math all floats considered odd?
Calliope "temp" sensor does not work <- same for master, not relevant here
[x] nxt colour == colour doesn't work
[x] nxt set colour sensor on doesn't work
[x] for each in list doesn't work
muliple sim: first 2 robots, then 1 robot, still 2 available <- same for master, not relevant here
[ ] EV3 lists: get and remove from empty lists
[ ] EV3 lists: pop failed with empty
[x] EV3 lists: remove does not work (invalid op on LIst function Name)
[x] EV3 lists:List set does not modify first
[ ] EV3 lists: not null -> false, null -> false
[x] Calliope "color with" breaks sim -> invalid stmt op rgbColor
Change by TEXT Tooltip wrong <- same for master, not relevant here
random int between 0, 0.9 returns 1 <- same for master, not relevant here
[x] NXT sound sensor not working
Some old issues:
[x] Cant't open simulation when using text append block (old 1116)
[x] EV3Sim Lists wrong behaviour (old 1008)

at current state we have the following problem with timing (example calliope)

generates with the old simulation (master) the following output:

and here the output from the new simulation (develop)

Both are far away from the real calliope output:
2045
19
2046
19
2046
19
2046
19
2046
19
2046
19
2046
19
2046
19
2046
19
2046
19
The new behavior will break almost all user programs which depends on time.


RuntimeError: CUDA out of memory.

Depending on your resources, you may have to reduce the batch size.
We trained on two NVIDIA A100 (40GB) GPUs.

Depending on your resources, you may have to reduce the batch size. We trained on two NVIDIA A100 (40GB) GPUs.

Hi, I can't find which file to change batch size, can you tell me the location ? (I mean testing.)

Did you mean you got the error during testing? If so, the error would occur because the input audio was so long.
If you got the error during training, you need to reduce the batch_size below.
https://github.com/mindslab-ai/nuwave2/blob/c05a0b6135ce1c46b9a5e57f132f18d3e3091745/hparameter.yaml#L2


[LintDiff] Invalid validation on ResourceMustReferenceCommonTypes

Describe the bug
Alert on

Resource definition 'ManagedClusterSnapshot' must reference the common types resource definition for ProxyResource or TrackedResource. Location: aks/preview/2023-05-02-preview/managedClusters.json#L7004

is invalid, as the model has been declared with
      "allOf": [
        {
          "$ref": "../../../../../../common-types/resource-management/v3/types.json#/definitions/TrackedResource"
        }
      ],

To Reproduce
See check result.
Expected behavior
Should not raise alert on this.
Screenshots
See check result.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Note this rule has been disabled by:

https://github.com/Azure/azure-openapi-validator/pull/506


OpenAPIV3Parser assigns null for empty string in response description

Problem statement
We have a response definition in the swagger as given below:
    "responses": {
          "200": {
            "description": "",
            "headers": {}
          }
        }

We are executing the below code snippet over this swaggerContent :

     // Validate Swagger definition - Line 1

    OpenAPI getOpenAPI(String oasDefinition) {
       OpenAPIV3Parser openAPIV3Parser = new OpenAPIV3Parser();
       SwaggerParseResult parseAttemptForV3 = openAPIV3Parser.readContents(oasDefinition, null, null);
       if (CollectionUtils.isNotEmpty(parseAttemptForV3.getMessages())) {
           log.debug("Errors found when parsing OAS definition");
       }
       return parseAttemptForV3.getOpenAPI();
    }

     OpenAPI openAPI = getOpenAPI(swaggerContent);
     Paths paths = openAPI.getPaths();
     // some logic here
    String swaggerContent  = Json.pretty(openAPI);

     // Validate swaggerContent - Line 101

The open API object generated is as given below:
 responses: class ApiResponses {
                    {200=class ApiResponse {
                        description: null
                        headers: null
                        content: null
                        links: null
                        extensions: null
                        $ref: null
                    }}
                    extensions: null
                }

And the returned swagger definition from Json.pretty() method is as given below:
    "responses" : {
          "200" : { }
        },

First, we are validating the swagger definition before applying the logic and there are no errors. But, when revalidating this returned swaggerContent from Json.pretty() method we encounter an error message from OAS3Parser as attribute paths.'/auth/signup'(post).responses.200.description is missing. We are using OAS Parser version 2.0.20 and it generates definitions in version 3.0.1 - [1].
So the issue is when  "description": "" in the swagger definition the swagger validation is passing. After converting it to an open API object, do some logic and reconvert it back to a swagger content to a string it removes the description attribute from the response, hence throwing an error.
Solution

We need to reject the swagger definition when it has a response description is an empty string from Line-1 itself. But here due to the OpenAPIV3Parser behavior, it is rejecting the definition at Line-101.

Or else OpenAPIV3Parser should  not assign null values for empty strings when converting a string swagger to an open API object

[1] https://github.com/swagger-api/swagger-core/blob/v2.1.2/modules/swagger-models/src/main/java/io/swagger/v3/oas/models/OpenAPI.java#L37

Hi Team, Any update on this issue ?

Hi, we had a PR merged a few weeks ago. Which version are you using?
https://github.com/swagger-api/swagger-parser/pull/1619

We are using 2.0.20.
As this is urgent shall we get a release with this fix ASAP ?

@gracekarina when we can expect the next release of swagger-parser?

@Sarangan0219 we are currently on 2.0.29-SNAPSHOT, please update your parser, this issue was already fix.

@vithu30  @Sarangan0219  we plan to release this week 🎉

Even with swagger-parser-v3-2.0.29.jar I am still getting a null in the response for the open API content
openapi: 3.0.0
servers:
  - url: https://api.remove.bg/v1.0
info:
  title: Background Removal API
  version: 1.0.0
paths:
  /test:
    get:
      responses:
        "200":
          description: ""

@SCSreekanth  are you setting the new option allowEmptyStrings to true?

Hi @gracekarina - Sorry, it's working for me now.
Thanks,
Sree


Implementing ImageNet in R

I'm trying to implement Imagenet in R using alexnet architecture. I successfully made it work in python, with the exception of a couple of architectures that are not working. However, alexnet is working in python.
What I get right now is that the accuracy is not going up: 0.00100694444444444, 0.00112268518518518, 0.00107638888888889, 0.00110416666666666, 0.00107638888888889.... It goes like this forever.
I'm using 4 GPUs and a batch size of 576 (I tried different batch sizes). This is the code I have:
# Train imagenet
require(mxnet)
require(argparse)

get_iterator <- function(args) {
  data.shape <- c(args$data_shape, args$data_shape, 3)
  train = mx.io.ImageRecordIter(
    path.imgrec     = file.path(args$data_dir, args$train_dataset),
    batch.size      = args$batch_size,
    data.shape      = data.shape,
    mean.r          = 123.68,
    mean.g          = 116.779,
    mean.b          = 103.939,
    rand.crop       = TRUE,
    rand.mirror     = TRUE
  )

  val = mx.io.ImageRecordIter(
    path.imgrec     = file.path(args$data_dir, args$val_dataset),
    batch.size      = args$batch_size,
    data.shape      = data.shape,
    mean.r          = 123.68,
    mean.g          = 116.779,
    mean.b          = 103.939,
    rand.crop       = FALSE,
    rand.mirror     = FALSE
  )
  ret = list(train=train, value=val)
}

parse_args <- function() {
  parser <- ArgumentParser(description='train an image classifer on ImageNet')
  parser$add_argument('--network', type='character', default='alexnet',
                      choices = c('alexnet', 'vgg','resnet'),
                      help = 'the cnn to use')
  parser$add_argument('--data-dir', type='character', default='../../data',
                      help='the input data directory')
  parser$add_argument('--train-dataset', type='character', default="train.rec",
                      help='train dataset name')
  parser$add_argument('--val-dataset', type='character', default="val.rec",
                      help="validation dataset name")
  parser$add_argument('--gpus', type='character',
                      help='the gpus will be used, e.g "0,1,2,3"')
  parser$add_argument('--batch-size', type='integer', default=128,
                      help='the batch size')
  parser$add_argument('--lr', type='double', default=.01,
                      help='the initial learning rate')
  parser$add_argument('--model-prefix', type='character',
                      help='the prefix of the model to load/save')
  parser$add_argument('--num-round', type='integer', default=10,
                      help='the number of iterations over training data to train the model')
  parser$add_argument('--kv-store', type='character', default='local',
                      help='the kvstore type')
  parser$add_argument('--num-classes', type='integer', default=1000,
                      help='the number of classes')
  parser$add_argument('--data-shape', type='integer', default=224,
                      help='set images shape')
  parser$parse_args()
}
args <- parse_args()

# network
if (args$network == 'alexnet') {
  source("symbol_alexnet.R")
} else if (args$network == 'vgg'){
  source("symbol_vgg.R")
} else {
  source("symbol_resnet.R")
}
network <- get_symbol(args$num_classes)

# data
data <- get_iterator(args)
train <- data$train
val <- data$value

# devices
if (is.null(args$gpus)) {
  devs <- mx.cpu()
} else {
  devs <- lapply(unlist(strsplit(args$gpus, ",")), function(i) {
    mx.gpu(as.integer(i))
  })
}

# save model
if (is.null(args$model_prefix)) {
  checkpoint <- NULL
} else {
  checkpoint <- mx.callback.save.checkpoint(args$model_prefix)
}

# train
model = mx.model.FeedForward.create(
  X                  = train,
  eval.data          = val,
  ctx                = devs,
  symbol             = network,
  eval.metric        = mx.metric.accuracy,
  num.round          = args$num_round,
  learning.rate      = args$lr,
  momentum           = 0.9,
  wd                 = 0.00001,
  kvstore            = args$kv_store,
  array.batch.size   = args$batch_size,
  epoch.end.callback = checkpoint,
  initializer        = mx.init.Xavier(factor_type="in", magnitude=2),
  batch.end.callback = mx.callback.log.train.metric(50))

Any ideas?

are you double checked the data? namely you can train alexnet on the .rec data using python.

Yes, the same data. Samples are going at 234.11 samples/sec and accuracies are going up steadily. There are several differences between the python and R script, such as, in the iterator:
        num_parts   = kv.num_workers,
        part_index  = kv.rank

Also in R I don't have the lr-factor and clip-gradient as in python. But that shouldn't be the reason right?

clip-gradient is important to avoid very bad things.
On Sat, Sep 24, 2016 at 2:27 PM, Miguel González-Fierro <
<EMAIL_ADDRESS>wrote:

Yes, the same data. Samples are going at 234.11 samples/sec and accuracies
are going up steadily. There are several differences between the python
https://github.com/dmlc/mxnet/blob/master/example/image-classification/train_imagenet.pyand
R script, such as, in the iterator:
    num_parts   = kv.num_workers,
    part_index  = kv.rank

Also in R I don't have the lr-factor and clip-gradient as in python
https://github.com/dmlc/mxnet/blob/master/example/image-classification/train_model.py#L59.
But that shouldn't be the reason right?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dmlc/mxnet/issues/3367#issuecomment-249388635, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZv4cE5FF511fiNDkYLmCkiAPF_OZDbks5qtZXFgaJpZM4KFsKm
.

Tried to add clip_gradient. I'm not sure how to implement it in R. I added this to the arguments:
  parser$add_argument('--clip-gradient', type='double', default=5,
                      help='clip min/max gradient to prevent extreme value')

And also this as an argument to the training function mx.model.FeedForward.create:
  clip_gradient      = args$clip_gradient,

Now, I don't get any different result, the train accuracy is still not converging and the trainingis getting slower. Any other idea? Thanks

I updated also the lr_scheduler like this:
# learning rate scheduler
if (args$lr_factor < 1){
  epoch_size <- args$num_examples/args$batch_size
  #lr_scheduler <- mx.lr_scheduler.FactorScheduler(
  FactorScheduler <- mxnet:::FactorScheduler
  lr_scheduler <- FactorScheduler(
    step = as.integer(max(epoch_size * args$lr_factor_epoch, 1)),
    factor_val = args$lr_factor)
} else{
  lr_scheduler = NULL
}

I had to take the function FactorScheduler from the namespace because it wasn't in the namespace.
However, the code is not working. I realised that if I remove the scheduler in python, the training doesn't converge.
Any idea what could be the problem?

It looks that if you remove remove the num_parts = kv.num_workers and part_index = kv.rank in the image iterator in python, the training doesn't converge.
In python it's easy to access num_workers and rank, they have getters. However, in R there is only a call to a cpp function.
Do you know @mli @thirdwing how I can access num_workers and rank in R?

I have imagenet running in R. There are still many difference with python mostly because the python API is more developed. As soon as I have some results I'll do a PR.

Hi, Miguel,
Can you show an example? I just finished one paper so I think I have
some time this week.
On 10/12/2016 08:22 AM, Miguel González-Fierro wrote:

I have imagenet running in R. There are still many difference with
python mostly because the python API is more developed. As soon as I
have some results I'll do a PR.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/dmlc/mxnet/issues/3367#issuecomment-253198440, or
mute the thread
https://github.com/notifications/unsubscribe-auth/ABebVcF22VBjrTCzFuu6qKWcwlW39nzbks5qzNDqgaJpZM4KFsKm.

Ey, KK, I just sent you an email


rpi-backlight not working in debian bullseye.

rpi-backlight worked in debian buster, but not on bullseye. Installing gives this notification:
Defaulting to user installation because normal site-packages is not writeable
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting rpi-backlight
Downloading https://www.piwheels.org/simple/rpi-backlight/rpi_backlight-2.4.1-py3-none-any.whl (9.8 kB)
Installing collected packages: rpi-backlight
Successfully installed rpi-backlight-2.4.1
After installation i gave the command:"echo 'SUBSYSTEM=="backlight",RUN+="/bin/chmod 666 /sys/class/backlight/%k/brightness /sys/class/backlight/%k/bl_power"' | sudo tee -a /etc/udev/rules.d/backlight-permissions.rules"
and a reboot, when i give the command backlight -b5 it is saying it doesn't excist.
With rpi-backlight -b5 it is saying:"
Traceback (most recent call last):
File "/home/pi/.local/bin/rpi-backlight", line 8, in
sys.exit(main())
File "/home/pi/.local/lib/python3.9/site-packages/rpi_backlight/cli.py", line 78, in main
backlight = Backlight(
File "/home/pi/.local/lib/python3.9/site-packages/rpi_backlight/init.py", line 75, in init
self._max_brightness = self._get_value("max_brightness")  # 255
File "/home/pi/.local/lib/python3.9/site-packages/rpi_backlight/init.py", line 92, in _get_value
raise e
File "/home/pi/.local/lib/python3.9/site-packages/rpi_backlight/init.py", line 84, in _get_value
return int((self._backlight_sysfs_path / name).read_text())
File "/usr/lib/python3.9/pathlib.py", line 1255, in read_text
with self.open(mode='r', encoding=encoding, errors=errors) as f:
File "/usr/lib/python3.9/pathlib.py", line 1241, in open
return io.open(self, mode, buffering, encoding, errors, newline,
File "/usr/lib/python3.9/pathlib.py", line 1109, in _opener
return self._accessor.open(self, flags, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/backlight/rpi_backlight/max_brightness'
In /sys/class there is a directory "backlight", but no directory "rpi_backlight". Only a directory "10-0045"
Has this to do with a new video-driver in the debian bullseye?
Thanks in advance.

I don't know. Try:
from rpi_backlight import Backlight
backlight = Backlight("/sys/class/backlight/10-0045")
backlight.brightness = 50

and see if that works.

Thank you Linus.
This works great when i go into the python shell. But how can i make it work when i want to do the same with a SSH command? I want it to do the same with my home automation.

Glad to hear :)
If you mean using the rpi-backlight command, you can simply pass the path as the first argument:
rpi-backlight --options /sys/class/...

Out of curiously, is this plain Debian or Raspbian / Raspberry Pi OS?

With :"rpi-backlight --options /sys/class/backlight/..."
i got:
usage: rpi-backlight [-h] [--get-brightness] [-b VALUE] [--get-power]
[-p VALUE] [-d DURATION]
[-B {raspberry-pi,tinker-board,tinker-board-2}] [-V]
[SYSFS_PATH]
rpi-backlight: error: unrecognized arguments: --options
It is the Debian bullseye. I got no problem with the debian buster for my raspberry pi 4b

Sure, that was just an example - you need to provide some proper options ;)
If this was Raspbian I'd consider a built-in workaround, but for plain Debian I'm afraid the existing option of explicitly specifying a path will need to be sufficient enough.

Running Bullseye on Raspbian (upgraded from Buster- not a fresh install) I have /sys/class/backlight/rpi_backlight/max_brightness

Strange. I don't. I did a fresh install of the debian bullseye. And i can't create a /sys/class/backlight/rpi-backlight. It is saying "access denied" or something like that. And i'm not good at it, but don't know how to make a path.

Yep have the same issue with a fresh installed Buster 64-Bit its listed under /sys/class/10-0045 i've modified the init.py on my Pi manually.
Line 29:    BoardType.RASPBERRY_PI: "/sys/class/backlight/rpi_backlight/",
to
BoardType.RASPBERRY_PI: "/sys/class/10-0045/rpi_backlight/",
its located in ~/.local/lib/python3.9/site-packages/rpi_backlight. Could be that you have another Python version then you have to change the version in the link

I've got very similar issue, but I'm struggling with the last step you are suggesting.
I'm running Raspbian bullseye 11 on Rpi4b and original 7" touch display.
After installation, if I try to launch the GUI, I get the FileNotFoundError:

This is my sys/class directory content:

Running your solution on a command shell would lead to:

And now I'm stuck because it's not clear to me which commands are required to get the rpi-backlight folder up.

You're running that in a bash shell, but it's python code.

Now I run it on python:

but the directory didn't change:

So I'm still having the same FileNotFoundError when trying to launch rpi-backlight-gui
Why the python commands are not effective ?


Invalid key: "refresh" for router dc_tracker info all

Are you using Helium hosted Console or running your own open source Console?

My own. Built from d2b6af6bb85acda507cc4cfbcc83a8d2dc786418
Please describe your issue:
docker exec helium_router router dc_tracker info all --less 9999999 --refresh results in
Invalid key: "refresh"
{error,1}

How do I use the refresh parameter?

The flag is --refetch: router dc_tracker info all --less 9999999 --refetch

My bad. Thanks for explaining.


Video Trimmer: Fix for blank frames in video trimmer frames strip

Context

In the video trimmer framers strip, It looks like trying to grab the  frames after the canplay event fires creates mixed results with the frames successfully extracted in FF but failing in chrome which returns a blank/transparent frame.
Summary

The least disruptive solution I found was to skip the first fraction of a ms  by simply adding #t=0.000001 at the end of the video file url. This works for both FF and Chrome.
Relevant Technical Choices

To-do

User-facing changes

Before
After

Testing Instructions

[ ] This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

Add a video to a page in chrome.
Toggle video trim mode
Verify there are no blank frames (white space) at the start of the frames strip.

Reviews
Does this PR have a security-related impact?

No
Does this PR change what data or activity we track or use?

No
Does this PR have a legal-related impact?

No
Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[ ] I have verified accessibility to the best of my abilities (docs)
[ ] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[ ] This code is covered by automated tests (unit, integration, and/or e2e) to verify it works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #9870

@Trapsta There's still a black (empty) area above the frames, didn't realize the origin issue didn't include fixing that but would be good to fully fix the looks while we're at it. The frames should cover the whole strip area.

@Trapsta There's still a black (empty) area above the frames, didn't realize the origin issue didn't include fixing that but would be good to fully fix the looks while we're at it. The frames should cover the whole strip area.

@miina , the black strip is part of the video. Updated the description with screenshots of a different video that doesn't have any black strips to show the difference. I recall we did have an issue with some white parts at the top or sometimes at the bottom but not seeing that currently .

Tested on stories-qa-server and confirmed fix ✔


WD-3737 WD-3736 updating axios interface, and User endpoints, adding …

…test for user.
Pull Request Considerations
Although some of these things can only be done after merged, please ensure all items have been considered when doing pull requests.

Updated README.md(s) for new functionality or changes.
Have you added an env file?

Did you update Openshift secrets/config maps in repository?
Did you added this env variable explanation in the appropriate README.md file.

Have you changed any Openshift configurations/templates?

Have you applied changes.

Did changes trigger Openshift img re builds.

Check Openshift instance of application to ensure your changes are working.

The rest of the code looks fine but the single test itself, in my opinion should be renamed and expanded to also check that the the view is updated with data from the API. If there were a problem with either hitting the /admin/user route or properly getting data from the server and having the data displayed in the component, we wouldn't catch it.


Feature/include logo

Description
Implements issue #471
Reason for this PR

We did not have any logo on our website

Changes in this PR

Replace placeholder in Navbar with new logo
add logo to about, login and welcome page

Type of change (remove all that don't apply)

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Manually tested all use cases this could alter

Checklist: (remove all that don't apply)

[x] I have performed a self-review of my own code
[x] My changes generate no new linting warnings or console warnings
[x] I have updated the CHANGELOG.md to include any changes made in this PR (add WIP to the top, if there is none already)

Screenshots:

The logo seems to be a really good fit. However, I'm not 100% convinced of the logo's colour in the navbar. It doesn't look horribly wrong or anything but for me, it's not a perfect match either. However, other than maybe completely white I can't think of any solution. Maybe something lighter to have more contrast to the navbar. However, I reckon that this will mess with our tailwind colour scheme.
Do you know if there is an option to set the favicon icon based on the browsers' preferences? I use Chrome's dark mode and the logo is barely visible for me (see screenshot).
 GJ!

For the navbar, I tried around with different logo and navbar colors, I think this blue is one of the better solutions that I found. It is the same blue as the non-hover style of our primary blue buttons.
For the favicon I just used the index HTML in the "common" way. I did not look into browser specific settings so far.. 😅


@ alias imports

Weren't working earlier, see how to alias

This seems simply to implement with the tsconfig file, however this project is written in jsx


Explicit TLS config

Motivation
Currently users provide a TLSConfiguration to the PSQLConnection.Configuration to signal they want to require TLS. This is very implicit and it will create a new NIOSSLContext for every new connection (VERY, VERY expensive operation).
Changes

Make TLS config explicit in PSQLConnection.Configuration. The initial provided values are .disable, .prefer, .require
If users use .prefer or .require they must provide a NIOSSLContext

Result

Faster more explicit code

Codecov Report

Merging #237 (7ab76cc) into main (63e7d57) will increase coverage by 4.21%.
The diff coverage is 60.75%.

@@            Coverage Diff             @@
##             main     #237      +/-   ##
==========================================
+ Coverage   39.82%   44.04%   +4.21%
==========================================
  Files         116      116
  Lines        9413     9474      +61
==========================================
+ Hits         3749     4173     +424
+ Misses       5664     5301     -363

Flag
Coverage Δ

unittests
44.04% <60.75%> (+4.21%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...es/PostgresNIO/Connection/PostgresConnection.swift
0.00% <0.00%> (ø)

Sources/PostgresNIO/New/PSQLConnection.swift
33.33% <65.00%> (+5.43%)
:arrow_up:

Sources/PostgresNIO/New/PSQLChannelHandler.swift
61.83% <94.73%> (+12.16%)
:arrow_up:

...nection State Machine/ConnectionStateMachine.swift
55.24% <100.00%> (+9.30%)
:arrow_up:

...ces/PostgresNIO/New/PostgresRow-multi-decode.swift
4.44% <0.00%> (+0.19%)
:arrow_up:

Sources/PostgresNIO/Data/PostgresRow.swift
50.00% <0.00%> (+1.02%)
:arrow_up:

...s/PostgresNIO/New/Data/Array+PostgresCodable.swift
94.68% <0.00%> (+1.06%)
:arrow_up:

...rces/PostgresNIO/New/Extensions/Logging+PSQL.swift
19.60% <0.00%> (+1.42%)
:arrow_up:

...ostgresNIO/Deprecated/PostgresMessageDecoder.swift
95.45% <0.00%> (+2.27%)
:arrow_up:

... and 24 more


Clear model after firing destroyed event

When destroying a model this.clear() gets called before the destroyed event is fired. (https://github.com/tgriesser/bookshelf/blob/c30d2b481763904d37280cf596153c02dbbbf169/src/model.js#L1051-L1065). I think it would make sense to switch the order here to allow event listeners to access the old attributes of the model.

Hm. The "destroying" event is not sufficient because there is a chance destroy will fail, right?

@rhys-vdw Correct.

Are previousAttributes accessible in the "destroyed" callback? That would makes sense if they were, I think. It seems correct to fire the "destroyed" event after all side effects of destroy have completed.

@rhys-vdw Good point - previousAttributes is accessible, so I guess this is a no-issue. Thanks for the quick responses!

No probs.


Handle macOS Homebrew on ARM

Output brew doctor and brew install messages noting this configuration is (currently) unsupported and encourage use of Rosetta instead
Output Rosetta 2 usage in brew config on ARM (whether in Rosetta 2 or not)
Check the architecture of (newly installed) dependencies and ensure they are using the correct architecture.
Don't allow installing macOS Intel Homebrew in macOS ARM Homebrew default prefix (and vice versa
Actually write out the architecture of dependencies to the tab rather than generating and throwing them away
Set and document the expected default prefix for macOS Intel Homebrew, macOS ARM Homebrew (/opt/homebrew) and Homebrew on Linux

While we're here:

Don't say Big Sur is a prerelease version but still make it clear we don't support it (yet).
Don't reference non-existent IRC channel

This needs to be merged and in a tagged release before Big Sur is released so please prioritise testing and reviewing this ASAP CC @claui @Bo98 @fxcoudert @mistydemeo

Thanks for this necessary work, Mike, and on a tight deadline.


python312Packages.slack-sdk: 3.33.3 -> 3.33.4

Things done

python312Packages.slack-sdk: 3.33.3 -> 3.33.4
python312Packages.slack-bolt: fix on darwin; clean

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/)
25.05 Release Notes (or backporting 24.11 and 25.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 358119

x86_64-linux

:fast_forward: 2 packages marked as broken and skipped:

krr
krr.dist

:white_check_mark: 10 packages built:

prowler
prowler.dist
python311Packages.slack-bolt
python311Packages.slack-bolt.dist
python311Packages.slack-sdk
python311Packages.slack-sdk.dist
python312Packages.slack-bolt
python312Packages.slack-bolt.dist
python312Packages.slack-sdk
python312Packages.slack-sdk.dist

aarch64-linux

:fast_forward: 2 packages marked as broken and skipped:

krr
krr.dist

:white_check_mark: 10 packages built:

prowler
prowler.dist
python311Packages.slack-bolt
python311Packages.slack-bolt.dist
python311Packages.slack-sdk
python311Packages.slack-sdk.dist
python312Packages.slack-bolt
python312Packages.slack-bolt.dist
python312Packages.slack-sdk
python312Packages.slack-sdk.dist

x86_64-darwin

:fast_forward: 2 packages marked as broken and skipped:

krr
krr.dist

:white_check_mark: 10 packages built:

prowler
prowler.dist
python311Packages.slack-bolt
python311Packages.slack-bolt.dist
python311Packages.slack-sdk
python311Packages.slack-sdk.dist
python312Packages.slack-bolt
python312Packages.slack-bolt.dist
python312Packages.slack-sdk
python312Packages.slack-sdk.dist

aarch64-darwin

:fast_forward: 2 packages marked as broken and skipped:

krr
krr.dist

:white_check_mark: 10 packages built:

prowler
prowler.dist
python311Packages.slack-bolt
python311Packages.slack-bolt.dist
python311Packages.slack-sdk
python311Packages.slack-sdk.dist
python312Packages.slack-bolt
python312Packages.slack-bolt.dist
python312Packages.slack-sdk
python312Packages.slack-sdk.dist

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

x86_64-linux

:fast_forward: 2 packages marked as broken and skipped:

krr
krr.dist

:white_check_mark: 10 packages built:

prowler
prowler.dist
python311Packages.slack-bolt
python311Packages.slack-bolt.dist
python311Packages.slack-sdk
python311Packages.slack-sdk.dist
python312Packages.slack-bolt
python312Packages.slack-bolt.dist
python312Packages.slack-sdk
python312Packages.slack-sdk.dist


Failed to extract BGI scripts

I encountered an error while using VNTextPatch.exe extractlocal . ./output/ --format=ethornell to extract text from 恋にはあまえが必要です : The given key was not present in the dictionary.
I suspect that this may be due to the presence of Emoji in the game text (for example, “❤” appears in this game text). Afterward, I changed https://github.com/arcusmaximus/VNTranslationTools/blob/36fbe909d02f2e9bb187443e03e2df595f56bfec/VNTextPatch.Shared/Scripts/Ethornell/EthornellV0Disassembler.cs#L227 and
https://github.com/arcusmaximus/VNTranslationTools/blob/36fbe909d02f2e9bb187443e03e2df595f56bfec/VNTextPatch.Shared/Scripts/Ethornell/EthornellV1Disassembler.cs#L636 to ReadOperands(OperandTemplates.TryGetValue(opcode, out var value) ? value : "");. Then i got a new error using the replaced code: Unable to read beyond the end of the stream (this error only occurred once after scripts were fully extracted). However, the result of unpacking the text is right except for Emoji (after modification, where ❤ should have appeared originally, \u0002 appeared).
I've attached the script files for reference.
scripts.zip

Try this one


python component

pycco:  The literate-programming-style documentation generator.

change json output to yaml output

nose: a nicer unittest for python
nose2: the successor to nose, based on unittest2
pytest: a mature full-featured python testing tool
unittest: unit testing framework
tox: auto builds and tests with multiple python
coverage: code coverage measurement.
line_profiler: line-by-line profiling
memory_profiler: monitor memory usage of python code
pybuilder: continuous build tool for python
green: a clean, colorful test runner
mamba: the definitive testing tool for python

find -name 'README.md' | while read F;do DN=`dirname $F`; cd $DN; grep docker README.md | while read L;do $L; done; cd -; done


21 version update

Hello @Scitator! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file homework-1/micrograd/mnist.py:

Line 7:80: E501 line too long (91 > 79 characters)

In the file week-13/deploy/common.py:

Line 14:80: E501 line too long (80 > 79 characters)

In the file week-13/deploy/web.py:

Line 34:80: E501 line too long (97 > 79 characters)
Line 40:80: E501 line too long (85 > 79 characters)

In the file week-13/research/experiments/multistage/dataset.py:

Line 37:80: E501 line too long (92 > 79 characters)
Line 53:80: E501 line too long (80 > 79 characters)
Line 55:80: E501 line too long (90 > 79 characters)

In the file week-13/research/experiments/optuna/dataset.py:

Line 27:80: E501 line too long (92 > 79 characters)
Line 43:80: E501 line too long (80 > 79 characters)
Line 45:80: E501 line too long (90 > 79 characters)

In the file week-13/research/experiments/optuna/experiment.py:

Line 17:80: E501 line too long (86 > 79 characters)
Line 18:80: E501 line too long (91 > 79 characters)

In the file week-13/research/experiments/simple/dataset.py:

Line 27:80: E501 line too long (92 > 79 characters)
Line 43:80: E501 line too long (80 > 79 characters)
Line 45:80: E501 line too long (90 > 79 characters)

In the file week-13/research/experiments/simple/experiment.py:

Line 17:80: E501 line too long (86 > 79 characters)
Line 18:80: E501 line too long (91 > 79 characters)


Update event-delivery-guarantees-azure-stream-analytics.md

@sidramadoss : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@mamccrea - when can we expect this page to go live? https://docs.microsoft.com/en-us/stream-analytics-query/event-delivery-guarantees-azure-stream-analytics?toc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fstream-analytics%2Ftoc.json&bc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbread%2Ftoc.json#duplicate-records

@sidramadoss - this should go live tomorrow.