Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Aug 26 07:08
    YunLemon reopened #1477
  • Aug 17 06:17
    YunLemon opened #1477
  • May 31 19:42
    Spnetic-5 opened #1476
  • May 25 18:42
    viditvarshney closed #1452
  • May 25 18:42
    viditvarshney commented #1452
  • May 25 08:57
    viditvarshney commented #1452
  • Jan 25 15:29

    Orbiter on dev-dist

    status of susi_server_binary_la… (compare)

  • Dec 27 2020 13:39
    ashutoshc8101 commented #1472
  • Oct 25 2020 07:50
    rounaksarda commented #1472
  • Oct 18 2020 17:37
    salhasalman commented #1472
  • Oct 05 2020 07:05
    Lucifer0x17 commented #1475
  • Oct 04 2020 19:21
    mariobehling closed #1475
  • Oct 04 2020 19:21
    mariobehling commented #1475
  • Oct 04 2020 17:09
    Lucifer0x17 synchronize #1475
  • Oct 04 2020 11:39
    Lucifer0x17 commented #1475
  • Oct 04 2020 11:37
    norbusan commented #1475
  • Oct 04 2020 11:33
    lgtm-com[bot] commented #1475
  • Oct 04 2020 11:29
    Lucifer0x17 opened #1475
  • Oct 04 2020 10:37
    Lucifer0x17 commented #1408
  • Oct 04 2020 07:35
    bhadreshpsavani commented #1408
Areeb Jamal
@iamareebjamal
Hi, I can't recall where I reformatted the files without function changes, and I have already put in unit tests to prove that not only my changes don't break the current system, but even that they are working correctly with previous behavior as there were no unit tests before which tested the skill loading and metadata, so in a way, we could conclude that there was no way previously to know if the system works without manually checking it, but now we do as now I have written tests for DAOFileAccess, SkillQueryParser, SkillQuery and every class I have added. If someone can show me the changes where I have just changed the formatting without functional changes and have not added tests for the function, I would be happy to oblige and either add tests for the same or revert it. I follow the rule of no reformatting without necessary changes quite strictly myself and have made as minimal as possible changes to ensure that the vulnerability is removed and system remains testable. The only changes I made which weren't related to the vulnerability were which broke the system on testing, for example, in SusiUtterance, the server crashed with error 500 when parsing a skill with just a "?" with IndexOutofBoundException because it didn't test for string being empty before accessing the first character, I fixed that and also added a test to ensure it parses such files correctly, so I am confident that more bugs are even fixed in the commits and tests have been added to prove that. However, I have split the changes into multiple atomic commits so it remains easy to git bisect and find where the bug is and if there are some changes someone feels unrelated to the PR or entirely cosmetic, I will be more than happy to add tests to prove they don't break and maybe even fix the system, or revert them :)
Thanks
Mario Behling
@mariobehling
:thumbsup:
Mario Behling
@mariobehling
SUSI.AI weekly meeting taking place now: https://meet.jit.si/SUSI.AI
Nickolay V. Shmyrev
@nshmyrev

https://www.cnx-software.com/2020/05/25/rpi_ac108-audio-board-ships-with-a-4-mic-array-for-raspberry-pi/

This design requires software AEC/DOA unfortunately which might load RPi CPU significantly in particular if you want DOA with neural networks. On one side it is more flexible, on other side given you run speech recognition will have problems with compute.

When we play with vosk(https://github.com/alphacep/vosk-api) on RPi it loads RPi3 almost 90%, so offloading AEC and DOA is a big gain. So Respeaker core 2 design with XMOS is somewhat more preferable.

Mohammad Abdullah
@abdabdullah
Hello everyone I am Mohammad Abdullah 2nd Year B.Tech student of Computer Science from Cluster Innovation Centre, University of Delhi. I want to contribute to your organization. I have learned java and a little bit of python. So anyone please help me to get started
Mohammad Abdullah
@abdabdullah
Right now I started doing some stuff on with reference to Automating the boring stuff with python and motivated to contribute in open source. So please help me to understand and let me know how to start from scratch because I am a beginner never contributed before this. with the provided instruction I will move forward to set up my environment.
Nickolay V. Shmyrev
@nshmyrev

Right now I started doing some stuff on with reference to Automating the boring stuff with python and motivated to contribute in open source. So please help me to understand and let me know how to start from scratch because I am a beginner never contributed before this. with the provided instruction I will move forward to set up my environment.

Clone code from github and implement something like fossasia/susi_server#969

Mario Behling
@mariobehling
The weekly SUSI.AI meeting is starting shortly https://meet.jit.si/SUSI.AI
Mario Behling
@mariobehling
@/all Weekly SUSI.AI meeting starting now https://meet.jit.si/SUSI.AI
Steve The Philosophist
@Philosophist
Hey, I'm having issues with the app. I am unable to sign up. The capcha checkbox won't react to being clicked. The app also has a problem where I am signing up for the first time, but it tells me that I'm already in. I reset the password and attempted to sign in, but it then tells me that my email isn't recognized.
Mario Behling
@mariobehling
Please join the SUSI.AI desktop installation workshop. It starts in a few minutes here https://meet.jit.si/SUSI.AI
This session covers step-by-step guide how to set up and configure Susi on Linux
Mario Behling
@mariobehling
Dear @/all, we are running the next version of our SUSI.AI installation workshop. This workshop is a run through to test our installation process for SUSI.AI on smart speakers. Compared to the last time we have improved a number of steps. The goal of this workshop is to make installations of SUSI.AI on smart speakers easier and enable more contributors to run workshops independently in future. Please join us at 8PM SGT, 5.30PM IST 2PM CET here https://meet.jit.si/SUSI.AI
(in a few minutes)
Mario Behling
@mariobehling

@/all Love #webdevelopment #Python #Javascript? Become a web developer and work on the #openevent software powering eventyay.com. Convince us to hire you by making a pull request! More info on https://jobs.fossasia.org

https://twitter.com/mariobehling/status/1288798977056477186

Norbert Preining
@norbusan
^^^^^^ yeah, please go for it!
Mario Behling
@mariobehling
:-)
1TekPro
@1TekPro
There seems to be an issue when you type ... to susi
1TekPro
@1TekPro
It generates an inappropriate response that it pulled from someones twitter post
Mario Behling
@mariobehling
Dear @/all, the next SUSI.AI workshop is a run through to test our installation process for on the desktop. The main goal of this workshop is to make installations of SUSI.AI on the desktop easier.
Please join us here https://meet.jit.si/SUSI.AI on
Tuesday, August 4, 2020
15:00 Berlin | 18:30 India | 21:00 Singapore | Tokyo 22:00
maitris
@blossom2017
Hi everyone ! Can newcomers contribute to this project ?
Mario Behling
@mariobehling
Yes
maitris
@blossom2017
I had to follow some additional steps for setting up susi server locally on mac since gradle was failing. Should I send a PR to update readme ?
Norbert Preining
@norbusan
@blossom2017 Sure, go ahead with it. We will see how it fits in. Thanks
maitris
@blossom2017
Thank you
Mario Behling
@mariobehling

@/all Please join the new edition of the #Codeheat #Coding #Contest organized by @fossasia @opntec Win cash prizes, get certificates and join developer events online. Sign up at http://codeheat.org

Please share the tweet https://twitter.com/codeheat_/status/1310611761490427905

kartikey rawat
@carrycooldude
Hello everyone I am new in this repo can anyone help me out I am begineer in open source project...
kartikey rawat
@carrycooldude
Screenshot from 2020-10-08 03-00-49.png
why it is showing error in installing this...???
Norbert Preining
@norbusan
Run git submodule update --init --recursive before running the build.
kartikey rawat
@carrycooldude
@norbusan after that even it's not working....
same error//
Norbert Preining
@norbusan
Indeed, strange. Seems to be some unrelated changes, @Orbiter can you look into that, I have seen similar problems. @carrycooldude which Java version are you using?
kartikey rawat
@carrycooldude
openjdk 11.0.8 2020-07-14
OpenJDK Runtime Environment (build 11.0.8+10-post-Ubuntu-0ubuntu120.04)
OpenJDK 64-Bit Server VM (build 11.0.8+10-post-Ubuntu-0ubuntu120.04, mixed mode, sharing)
this one
kartikey rawat
@carrycooldude
@norbusan
Norbert Preining
@norbusan
Yes, acked, but still I don't know what is the problem.
kartikey rawat
@carrycooldude
  • What went wrong:
    Could not initialize class org.codehaus.groovy.runtime.InvokerHelper
this is coming...
Norbert Preining
@norbusan
seems to be the gradlew wrapper being for a too old gradle. When Icall gradle buildit does build (but still some errors)
kartikey rawat
@carrycooldude
So what I do now make Issue of this in the repo...
Norbert Preining
@norbusan
I cannot parse your sentence, what do you want to say?
kartikey rawat
@carrycooldude
Like I add this as a Issue...
Norbert Preining
@norbusan
I guess using JDK8 it will work.
kartikey rawat
@carrycooldude
Ok let me try this...
kartikey rawat
@carrycooldude
@norbusan No it is showing the same error...
Norbert Preining
@norbusan
As I said, with my system-wide grade it builds, but the tests fail.
kartikey rawat
@carrycooldude
Even after that showing the same error @norbusan

FAILURE: Build failed with an exception.

  • What went wrong:
    Could not initialize class org.codehaus.groovy.reflection.ReflectionCache

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

BUILD FAILED in 8s

Starting a Gradle Daemon (subsequent builds will be faster)
java.lang.NoClassDefFoundError: Could not initialize class org.codehaus.groovy.vmplugin.v7.Java7
at org.codehaus.groovy.vmplugin.VMPluginFactory.<clinit>(VMPluginFactory.java:43)
at org.codehaus.groovy.reflection.GroovyClassValueFactory.<clinit>(GroovyClassValueFactory.java:35)
at org.codehaus.groovy.reflection.ClassInfo.<clinit>(ClassInfo.java:109)
at org.codehaus.groovy.reflection.ReflectionCache.getCachedClass(ReflectionCache.java:95)
at org.codehaus.groovy.reflection.ReflectionCache.<clinit>(ReflectionCache.java:39)
at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.registerMethods(MetaClassRegistryImpl.java:209)
at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(MetaClassRegistryImpl.java:107)
at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(MetaClassRegistryImpl.java:85)
at groovy.lang.GroovySystem.<clinit>(GroovySystem.java:36)
at org.codehaus.groovy.runtime.InvokerHelper.<clinit>(InvokerHelper.java:86)
at groovy.lang.GroovyObjectSupport.getDefaultMetaClass(GroovyObjectSupport.java:59)
at groovy.lang.GroovyObjectSupport.<init>(GroovyObjectSupport.java:32)
at org.gradle.internal.extensibility.DefaultExtraPropertiesExtension.<init>(DefaultExtraPropertiesExtension.java:29)
at org.gradle.internal.extensibility.DefaultConvention.<init>(DefaultConvention.java:48)
at org.gradle.api.internal.plugins.DefaultConvention.<init>(DefaultConvention.java:28)
at org.gradle.internal.extensibility.ExtensibleDynamicObject.<init>(ExtensibleDynamicObject.java:60)
at org.gradle.internal.instantiation.MixInExtensibleDynamicObject.<init>(MixInExtensibleDynamicObject.java:34)
at org.gradle.initialization.DefaultSettings_Decorated.getAsDynamicObject(Unknown Source)
at org.gradle.initialization.SettingsFactory.createSettings(SettingsFactory.java:58)
at org.gradle.initialization.ScriptEvaluatingSettingsProcessor.process(ScriptEvaluatingSettingsProcessor.java:60)
at org.gradle.initialization.PropertiesLoadingSettingsProcessor.process(PropertiesLoadingSettingsProcessor.java:37)
at org.gradle.initialization.SettingsEvaluatedCallbackFiringSettingsProcessor.process(SettingsEvaluatedCallbackFiringSettingsProcessor.java:34)
at org.gradle.initialization.RootBuildCacheControllerSettingsProcessor.process(RootBuildCacheControllerSettingsProcessor.java:36)
at org.gradle.initialization.BuildOperationSettingsProcessor$2.call(BuildOperationSettingsProcessor.java:50)
at org.gradle.initialization.BuildOperationSettingsProcessor$2.call(BuildOperationSettingsProcessor.java:47)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:416)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:406)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:102)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
at org.gradle.initialization.BuildOperationSettingsProcessor.process(BuildOperationSettingsProcessor.java:47)
at org.gradle.initialization.DefaultSettingsLoader.findSettingsAndLoadIfAppropriate(DefaultSettingsLoader.java:104)
at org.gradle.initialization.DefaultSettingsLoader.findAndLoadSettings(DefaultSettingsLoader.java:45)
at org.gradle.initialization.SettingsAttachi