Why I am getting java.lang.AbstractMethodError errors?












22















What are the possible causes for ABstractMethodError?



Exception in thread "pool-1-thread-1" java.lang.AbstractMethodError:



org.apache.thrift.ProcessFunction.isOneway()Z
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:51)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at com.gemfire.gemstone.thrift.hbase.ThreadPoolServer$ClientConnnection.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)









share|improve this question

























  • Give us some context , what are you trying to do ? May be some version issue ! The method that you invoke or some other code invokes is converted into an abstract method now .

    – NINCOMPOOP
    Jul 31 '13 at 11:44













  • I was trying out hbase thrift version. I build thrift compiler and generated thrift files. and using mvn building my project which is also downloading 0.9.0 version of apache thrift jars. this is the same I am using.

    – Avinash
    Jul 31 '13 at 11:56
















22















What are the possible causes for ABstractMethodError?



Exception in thread "pool-1-thread-1" java.lang.AbstractMethodError:



org.apache.thrift.ProcessFunction.isOneway()Z
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:51)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at com.gemfire.gemstone.thrift.hbase.ThreadPoolServer$ClientConnnection.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)









share|improve this question

























  • Give us some context , what are you trying to do ? May be some version issue ! The method that you invoke or some other code invokes is converted into an abstract method now .

    – NINCOMPOOP
    Jul 31 '13 at 11:44













  • I was trying out hbase thrift version. I build thrift compiler and generated thrift files. and using mvn building my project which is also downloading 0.9.0 version of apache thrift jars. this is the same I am using.

    – Avinash
    Jul 31 '13 at 11:56














22












22








22


4






What are the possible causes for ABstractMethodError?



Exception in thread "pool-1-thread-1" java.lang.AbstractMethodError:



org.apache.thrift.ProcessFunction.isOneway()Z
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:51)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at com.gemfire.gemstone.thrift.hbase.ThreadPoolServer$ClientConnnection.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)









share|improve this question
















What are the possible causes for ABstractMethodError?



Exception in thread "pool-1-thread-1" java.lang.AbstractMethodError:



org.apache.thrift.ProcessFunction.isOneway()Z
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:51)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at com.gemfire.gemstone.thrift.hbase.ThreadPoolServer$ClientConnnection.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)






java thrift






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 31 '13 at 11:44









dda

5,47822032




5,47822032










asked Jul 31 '13 at 11:41









AvinashAvinash

5,5272381157




5,5272381157













  • Give us some context , what are you trying to do ? May be some version issue ! The method that you invoke or some other code invokes is converted into an abstract method now .

    – NINCOMPOOP
    Jul 31 '13 at 11:44













  • I was trying out hbase thrift version. I build thrift compiler and generated thrift files. and using mvn building my project which is also downloading 0.9.0 version of apache thrift jars. this is the same I am using.

    – Avinash
    Jul 31 '13 at 11:56



















  • Give us some context , what are you trying to do ? May be some version issue ! The method that you invoke or some other code invokes is converted into an abstract method now .

    – NINCOMPOOP
    Jul 31 '13 at 11:44













  • I was trying out hbase thrift version. I build thrift compiler and generated thrift files. and using mvn building my project which is also downloading 0.9.0 version of apache thrift jars. this is the same I am using.

    – Avinash
    Jul 31 '13 at 11:56

















Give us some context , what are you trying to do ? May be some version issue ! The method that you invoke or some other code invokes is converted into an abstract method now .

– NINCOMPOOP
Jul 31 '13 at 11:44







Give us some context , what are you trying to do ? May be some version issue ! The method that you invoke or some other code invokes is converted into an abstract method now .

– NINCOMPOOP
Jul 31 '13 at 11:44















I was trying out hbase thrift version. I build thrift compiler and generated thrift files. and using mvn building my project which is also downloading 0.9.0 version of apache thrift jars. this is the same I am using.

– Avinash
Jul 31 '13 at 11:56





I was trying out hbase thrift version. I build thrift compiler and generated thrift files. and using mvn building my project which is also downloading 0.9.0 version of apache thrift jars. this is the same I am using.

– Avinash
Jul 31 '13 at 11:56












6 Answers
6






active

oldest

votes


















13














The simple answer is this: some code is trying to call a method which is declared abstract. Abstract methods have no body and cannot be executed. Since you have provided so little information I can't really elaborate more on how this can happen since the compiler usually catches this problem - as described here, this means the class must have changed at runtime.






share|improve this answer
























  • Yes, method is defined as abstract, but I traced through the eclipse and I see methods are implemented in child classes

    – Avinash
    Jul 31 '13 at 11:56











  • Sure, but that means you have to call a specific child class implementation. You still can't call the method itself.

    – devrobf
    Jul 31 '13 at 11:57











  • I checked again , Apache thrift generated code is calling child object specific implementation

    – Avinash
    Jul 31 '13 at 12:51











  • Please double-check that. If you are still sure about it, open a JIRA ticket with a complete, reproducible test case.

    – JensG
    Jul 31 '13 at 22:43



















41














It usually means that you are using an old version of an interface implementation which is missing a new interface method. For example java.sql.Connection interface got a new getSchema method in 1.7. If you have 1.6 JDBC driver and call Connection.getSchema you will get AbstractMethodError.






share|improve this answer



















  • 3





    Nice, you had me at "old version of an interface"

    – mtyson
    Sep 7 '16 at 20:53











  • Encountered this Exception recently. It's exactly the cause - interface incompatibly between components at runtime. One can refers to the javadoc of the exception for more details.

    – tuan.dinh
    May 11 '18 at 7:15



















3














From documnentation of AbstractMethodError




Thrown when an application tries to call an abstract method. Normally,
this error is caught by the compiler; this error can only occur at run
time if the definition of some class has incompatibly changed since
the currently executing method was last compiled.







share|improve this answer































    0














    If you you are getting this error on the implemented methods, make sure you have added your dependencies correctly as mentioned in this thread.






    share|improve this answer

































      0














      As Damian quoted :




      Normally, this error is caught by the compiler; this error can only
      occur at run time if [...]




      I had the same error that was not caught by the compiler but at runtime. To solve it I only compiled again without giving the code any modification.






      share|improve this answer































        0














        A kind of special case of the above answer.



        I had this error, because I was using a spring-boot-starter-parent (e.g. 2.1.0.RELEASE uses spring version: 5.1.2.RELEASE) but I also included a BOM, that also defined some spring dependencies, but in an older version (e.g. 5.0.9.RELEASE).



        So one thing to do, is check your dependency tree (in Eclipse e.g. you can use the Dependency Hierarchy) if you are using the same versions.



        So one solution could be that you upgrade the spring dependencies in your BOM, another one could be that you exclude them (but depending on the amount, this could be ugly).






        share|improve this answer























          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17969365%2fwhy-i-am-getting-java-lang-abstractmethoderror-errors%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          6 Answers
          6






          active

          oldest

          votes








          6 Answers
          6






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          13














          The simple answer is this: some code is trying to call a method which is declared abstract. Abstract methods have no body and cannot be executed. Since you have provided so little information I can't really elaborate more on how this can happen since the compiler usually catches this problem - as described here, this means the class must have changed at runtime.






          share|improve this answer
























          • Yes, method is defined as abstract, but I traced through the eclipse and I see methods are implemented in child classes

            – Avinash
            Jul 31 '13 at 11:56











          • Sure, but that means you have to call a specific child class implementation. You still can't call the method itself.

            – devrobf
            Jul 31 '13 at 11:57











          • I checked again , Apache thrift generated code is calling child object specific implementation

            – Avinash
            Jul 31 '13 at 12:51











          • Please double-check that. If you are still sure about it, open a JIRA ticket with a complete, reproducible test case.

            – JensG
            Jul 31 '13 at 22:43
















          13














          The simple answer is this: some code is trying to call a method which is declared abstract. Abstract methods have no body and cannot be executed. Since you have provided so little information I can't really elaborate more on how this can happen since the compiler usually catches this problem - as described here, this means the class must have changed at runtime.






          share|improve this answer
























          • Yes, method is defined as abstract, but I traced through the eclipse and I see methods are implemented in child classes

            – Avinash
            Jul 31 '13 at 11:56











          • Sure, but that means you have to call a specific child class implementation. You still can't call the method itself.

            – devrobf
            Jul 31 '13 at 11:57











          • I checked again , Apache thrift generated code is calling child object specific implementation

            – Avinash
            Jul 31 '13 at 12:51











          • Please double-check that. If you are still sure about it, open a JIRA ticket with a complete, reproducible test case.

            – JensG
            Jul 31 '13 at 22:43














          13












          13








          13







          The simple answer is this: some code is trying to call a method which is declared abstract. Abstract methods have no body and cannot be executed. Since you have provided so little information I can't really elaborate more on how this can happen since the compiler usually catches this problem - as described here, this means the class must have changed at runtime.






          share|improve this answer













          The simple answer is this: some code is trying to call a method which is declared abstract. Abstract methods have no body and cannot be executed. Since you have provided so little information I can't really elaborate more on how this can happen since the compiler usually catches this problem - as described here, this means the class must have changed at runtime.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 31 '13 at 11:44









          devrobfdevrobf

          4,90712037




          4,90712037













          • Yes, method is defined as abstract, but I traced through the eclipse and I see methods are implemented in child classes

            – Avinash
            Jul 31 '13 at 11:56











          • Sure, but that means you have to call a specific child class implementation. You still can't call the method itself.

            – devrobf
            Jul 31 '13 at 11:57











          • I checked again , Apache thrift generated code is calling child object specific implementation

            – Avinash
            Jul 31 '13 at 12:51











          • Please double-check that. If you are still sure about it, open a JIRA ticket with a complete, reproducible test case.

            – JensG
            Jul 31 '13 at 22:43



















          • Yes, method is defined as abstract, but I traced through the eclipse and I see methods are implemented in child classes

            – Avinash
            Jul 31 '13 at 11:56











          • Sure, but that means you have to call a specific child class implementation. You still can't call the method itself.

            – devrobf
            Jul 31 '13 at 11:57











          • I checked again , Apache thrift generated code is calling child object specific implementation

            – Avinash
            Jul 31 '13 at 12:51











          • Please double-check that. If you are still sure about it, open a JIRA ticket with a complete, reproducible test case.

            – JensG
            Jul 31 '13 at 22:43

















          Yes, method is defined as abstract, but I traced through the eclipse and I see methods are implemented in child classes

          – Avinash
          Jul 31 '13 at 11:56





          Yes, method is defined as abstract, but I traced through the eclipse and I see methods are implemented in child classes

          – Avinash
          Jul 31 '13 at 11:56













          Sure, but that means you have to call a specific child class implementation. You still can't call the method itself.

          – devrobf
          Jul 31 '13 at 11:57





          Sure, but that means you have to call a specific child class implementation. You still can't call the method itself.

          – devrobf
          Jul 31 '13 at 11:57













          I checked again , Apache thrift generated code is calling child object specific implementation

          – Avinash
          Jul 31 '13 at 12:51





          I checked again , Apache thrift generated code is calling child object specific implementation

          – Avinash
          Jul 31 '13 at 12:51













          Please double-check that. If you are still sure about it, open a JIRA ticket with a complete, reproducible test case.

          – JensG
          Jul 31 '13 at 22:43





          Please double-check that. If you are still sure about it, open a JIRA ticket with a complete, reproducible test case.

          – JensG
          Jul 31 '13 at 22:43













          41














          It usually means that you are using an old version of an interface implementation which is missing a new interface method. For example java.sql.Connection interface got a new getSchema method in 1.7. If you have 1.6 JDBC driver and call Connection.getSchema you will get AbstractMethodError.






          share|improve this answer



















          • 3





            Nice, you had me at "old version of an interface"

            – mtyson
            Sep 7 '16 at 20:53











          • Encountered this Exception recently. It's exactly the cause - interface incompatibly between components at runtime. One can refers to the javadoc of the exception for more details.

            – tuan.dinh
            May 11 '18 at 7:15
















          41














          It usually means that you are using an old version of an interface implementation which is missing a new interface method. For example java.sql.Connection interface got a new getSchema method in 1.7. If you have 1.6 JDBC driver and call Connection.getSchema you will get AbstractMethodError.






          share|improve this answer



















          • 3





            Nice, you had me at "old version of an interface"

            – mtyson
            Sep 7 '16 at 20:53











          • Encountered this Exception recently. It's exactly the cause - interface incompatibly between components at runtime. One can refers to the javadoc of the exception for more details.

            – tuan.dinh
            May 11 '18 at 7:15














          41












          41








          41







          It usually means that you are using an old version of an interface implementation which is missing a new interface method. For example java.sql.Connection interface got a new getSchema method in 1.7. If you have 1.6 JDBC driver and call Connection.getSchema you will get AbstractMethodError.






          share|improve this answer













          It usually means that you are using an old version of an interface implementation which is missing a new interface method. For example java.sql.Connection interface got a new getSchema method in 1.7. If you have 1.6 JDBC driver and call Connection.getSchema you will get AbstractMethodError.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 31 '13 at 12:15









          Evgeniy DorofeevEvgeniy Dorofeev

          105k23141222




          105k23141222








          • 3





            Nice, you had me at "old version of an interface"

            – mtyson
            Sep 7 '16 at 20:53











          • Encountered this Exception recently. It's exactly the cause - interface incompatibly between components at runtime. One can refers to the javadoc of the exception for more details.

            – tuan.dinh
            May 11 '18 at 7:15














          • 3





            Nice, you had me at "old version of an interface"

            – mtyson
            Sep 7 '16 at 20:53











          • Encountered this Exception recently. It's exactly the cause - interface incompatibly between components at runtime. One can refers to the javadoc of the exception for more details.

            – tuan.dinh
            May 11 '18 at 7:15








          3




          3





          Nice, you had me at "old version of an interface"

          – mtyson
          Sep 7 '16 at 20:53





          Nice, you had me at "old version of an interface"

          – mtyson
          Sep 7 '16 at 20:53













          Encountered this Exception recently. It's exactly the cause - interface incompatibly between components at runtime. One can refers to the javadoc of the exception for more details.

          – tuan.dinh
          May 11 '18 at 7:15





          Encountered this Exception recently. It's exactly the cause - interface incompatibly between components at runtime. One can refers to the javadoc of the exception for more details.

          – tuan.dinh
          May 11 '18 at 7:15











          3














          From documnentation of AbstractMethodError




          Thrown when an application tries to call an abstract method. Normally,
          this error is caught by the compiler; this error can only occur at run
          time if the definition of some class has incompatibly changed since
          the currently executing method was last compiled.







          share|improve this answer




























            3














            From documnentation of AbstractMethodError




            Thrown when an application tries to call an abstract method. Normally,
            this error is caught by the compiler; this error can only occur at run
            time if the definition of some class has incompatibly changed since
            the currently executing method was last compiled.







            share|improve this answer


























              3












              3








              3







              From documnentation of AbstractMethodError




              Thrown when an application tries to call an abstract method. Normally,
              this error is caught by the compiler; this error can only occur at run
              time if the definition of some class has incompatibly changed since
              the currently executing method was last compiled.







              share|improve this answer













              From documnentation of AbstractMethodError




              Thrown when an application tries to call an abstract method. Normally,
              this error is caught by the compiler; this error can only occur at run
              time if the definition of some class has incompatibly changed since
              the currently executing method was last compiled.








              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jul 31 '13 at 11:46









              Damian Leszczyński - VashDamian Leszczyński - Vash

              25.1k74587




              25.1k74587























                  0














                  If you you are getting this error on the implemented methods, make sure you have added your dependencies correctly as mentioned in this thread.






                  share|improve this answer






























                    0














                    If you you are getting this error on the implemented methods, make sure you have added your dependencies correctly as mentioned in this thread.






                    share|improve this answer




























                      0












                      0








                      0







                      If you you are getting this error on the implemented methods, make sure you have added your dependencies correctly as mentioned in this thread.






                      share|improve this answer















                      If you you are getting this error on the implemented methods, make sure you have added your dependencies correctly as mentioned in this thread.







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited May 23 '17 at 11:47









                      Community

                      11




                      11










                      answered Dec 14 '16 at 13:04









                      amanzooramanzoor

                      22026




                      22026























                          0














                          As Damian quoted :




                          Normally, this error is caught by the compiler; this error can only
                          occur at run time if [...]




                          I had the same error that was not caught by the compiler but at runtime. To solve it I only compiled again without giving the code any modification.






                          share|improve this answer




























                            0














                            As Damian quoted :




                            Normally, this error is caught by the compiler; this error can only
                            occur at run time if [...]




                            I had the same error that was not caught by the compiler but at runtime. To solve it I only compiled again without giving the code any modification.






                            share|improve this answer


























                              0












                              0








                              0







                              As Damian quoted :




                              Normally, this error is caught by the compiler; this error can only
                              occur at run time if [...]




                              I had the same error that was not caught by the compiler but at runtime. To solve it I only compiled again without giving the code any modification.






                              share|improve this answer













                              As Damian quoted :




                              Normally, this error is caught by the compiler; this error can only
                              occur at run time if [...]




                              I had the same error that was not caught by the compiler but at runtime. To solve it I only compiled again without giving the code any modification.







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Jun 28 '18 at 12:30









                              yutanpoyutanpo

                              236




                              236























                                  0














                                  A kind of special case of the above answer.



                                  I had this error, because I was using a spring-boot-starter-parent (e.g. 2.1.0.RELEASE uses spring version: 5.1.2.RELEASE) but I also included a BOM, that also defined some spring dependencies, but in an older version (e.g. 5.0.9.RELEASE).



                                  So one thing to do, is check your dependency tree (in Eclipse e.g. you can use the Dependency Hierarchy) if you are using the same versions.



                                  So one solution could be that you upgrade the spring dependencies in your BOM, another one could be that you exclude them (but depending on the amount, this could be ugly).






                                  share|improve this answer




























                                    0














                                    A kind of special case of the above answer.



                                    I had this error, because I was using a spring-boot-starter-parent (e.g. 2.1.0.RELEASE uses spring version: 5.1.2.RELEASE) but I also included a BOM, that also defined some spring dependencies, but in an older version (e.g. 5.0.9.RELEASE).



                                    So one thing to do, is check your dependency tree (in Eclipse e.g. you can use the Dependency Hierarchy) if you are using the same versions.



                                    So one solution could be that you upgrade the spring dependencies in your BOM, another one could be that you exclude them (but depending on the amount, this could be ugly).






                                    share|improve this answer


























                                      0












                                      0








                                      0







                                      A kind of special case of the above answer.



                                      I had this error, because I was using a spring-boot-starter-parent (e.g. 2.1.0.RELEASE uses spring version: 5.1.2.RELEASE) but I also included a BOM, that also defined some spring dependencies, but in an older version (e.g. 5.0.9.RELEASE).



                                      So one thing to do, is check your dependency tree (in Eclipse e.g. you can use the Dependency Hierarchy) if you are using the same versions.



                                      So one solution could be that you upgrade the spring dependencies in your BOM, another one could be that you exclude them (but depending on the amount, this could be ugly).






                                      share|improve this answer













                                      A kind of special case of the above answer.



                                      I had this error, because I was using a spring-boot-starter-parent (e.g. 2.1.0.RELEASE uses spring version: 5.1.2.RELEASE) but I also included a BOM, that also defined some spring dependencies, but in an older version (e.g. 5.0.9.RELEASE).



                                      So one thing to do, is check your dependency tree (in Eclipse e.g. you can use the Dependency Hierarchy) if you are using the same versions.



                                      So one solution could be that you upgrade the spring dependencies in your BOM, another one could be that you exclude them (but depending on the amount, this could be ugly).







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Nov 13 '18 at 18:11









                                      morecoremorecore

                                      1851318




                                      1851318






























                                          draft saved

                                          draft discarded




















































                                          Thanks for contributing an answer to Stack Overflow!


                                          • Please be sure to answer the question. Provide details and share your research!

                                          But avoid



                                          • Asking for help, clarification, or responding to other answers.

                                          • Making statements based on opinion; back them up with references or personal experience.


                                          To learn more, see our tips on writing great answers.




                                          draft saved


                                          draft discarded














                                          StackExchange.ready(
                                          function () {
                                          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17969365%2fwhy-i-am-getting-java-lang-abstractmethoderror-errors%23new-answer', 'question_page');
                                          }
                                          );

                                          Post as a guest















                                          Required, but never shown





















































                                          Required, but never shown














                                          Required, but never shown












                                          Required, but never shown







                                          Required, but never shown

































                                          Required, but never shown














                                          Required, but never shown












                                          Required, but never shown







                                          Required, but never shown







                                          Popular posts from this blog

                                          Xamarin.iOS Cant Deploy on Iphone

                                          Glorious Revolution

                                          Dulmage-Mendelsohn matrix decomposition in Python