Tuesday, January 28, 2020

Application Inspector build with Roslyn analyze my AST parser

All are known, copy-paste is a bad thing for a code, but my project contains 95% of duplicated code. This code mostly generated with Roslyn to support ASt parser and importer for Arango graph db. When i run new Microsoft tool Application Inspector I finally know how large is auto generated code in my project.

This analyzer also know where I read from file, or even I need to switch from Newton.Json


I think it is security and discovery tool by Guy Acosta to better know what exactly you tried to run in your sandbox

Friday, January 24, 2020

Two languages and one on the host

It is easy to install Java in the ChromeOs, extracted from archive it simply works with sdk for development. Golang is supported by the crew as common package. .NET Core is hosted on the server for me, I can connect with ssh and Termius client.


Tuesday, January 21, 2020

Virtual Box 64bit setup

I tried to install Virtual Box from the rpm package but it did not work, because of a kernel module build. Here is an instruction from a link:

cd /etc/yum.repos.d/
wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
dnf install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms
dnf install VirtualBox-6.0
/usr/lib/virtualbox/vboxdrv.sh setup
usermod -a -G vboxusers user_name
   

Monday, January 13, 2020

Where Microsoft packages live

https://packages.microsoft.com is a home for packages like .net core and mssql-server. But it has other packages required for cloud maintenance, for example i found in the repo:

The Moby project
SCXCore
procdump

Not so much, but this is only one listed repo where i found .Net Core for my OS.

Saturday, January 11, 2020

Steam on Oracle Linux 8

Here is an instruction,
 
# dnf install json-glib.i686 libdbusmenu.i686 fontconfig.i686 freetype.i686 glib2.i686 gtk2.i686 pango.i686 glibc.i686
# wget https://negativo17.org/repos/steam/epel-7/x86_64/libdbusmenu-gtk2-16.04.0-4.el7.i686.rpm
# rpm -U libdbusmenu-gtk2-16.04.0-4.el7.i686.rpm --nodeps
# dnf install libdrm.i686
# dnf install https://download1.rpmfusion.org/free/el/updates/8/x86_64/l/libva-intel-driver-2.1.0-4.el8.x86_64.rpm
# dnf install alsa-lib.i686 alsa-plugins-pulseaudio.i686 libXScrnSaver.i686 libXtst.i686 libatomic.i686 libcurl.i686 libdbusmenu-gtk3.i686 libpng12.i686 libvdpau.i686
# dnf install mesa-dri-drivers.i686 mesa-libGL.i686 nss.i686
# dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm 
# dnf install https://download1.rpmfusion.org/free/el/rpmfusion-free-release-8.noarch.rpm
# dnf install https://download1.rpmfusion.org/nonfree/el/rpmfusion-nonfree-release-8.noarch.rpm
# dnf install steam
 
Although not all games with linux support have been started, this list exactly works for me:

Portal
Portal2
Arcadia (unknown novel) 
Life is Strange
Tomb Rider

I built Nvidia driver for me, but desktop manager simply have not open my workspace. 
May be next time for Oracle Linux. I remembered driver for GTX 970 works in Ubuntu 18.04 last time.

Then I returned to my Intel Corporation 8th Gen Core Processor Gaussian Mixture Model,
that have 60fps for Tomb Rider only for Low quality, Life is Strange that created after Tomb Rider looks very good.
 
 
 

OJet. May be is possible on x86 but not in arm chromebook.

node /mnt/stateful_partition/dev_
image/share/nodebrew/node/v13.0.1/lib/node_modules/@oracle/ojet-cli/ojet build




chronos@localhost /home/user/46f836ee257e57280b1bac56c5164f65dcfcfbbe/Projects/robovault_ui $ node /mnt/stateful_partition/dev_image/share/nodebrew/node/v10.18.0/lib/node_modules/@oracle/ojet-cli/ojet build
Warning: Command is missing platform. Default to web.
Cleaning staging path.
Running before_build hook.
Copy files to staging directory.
Copy finished.
Copy library files to staging directory.
Copy finished.
Copy reference components to staging directory.
Copy finished.
Copy local web components
Copy local web components skipped
Optimizing svg into SVG sprites.
Svg optimization task finished.
Compiling sass...
Sass compile finished.
Task index.html cdn bundle injection finished.
Running theme injection task.
Task index.html theme path injection finished.
Running theme copy task.
Theme copy task finished.
Running injection tasks.
Task main.js paths injection finished.
runAllComponentHooks
Running after_build hook.


chronos@localhost /home/user/46f836ee257e57280b1bac56c5164f65dcfcfbbe/Projects/robovault_ui $ node /mnt/stateful_partition/dev_image/share/nodebrew/node/v10.18.0/lib/node_modules/@oracle/ojet-cli/ojet serve
Warning: Command is missing platform. Default to web.
Build: true
BuildType: dev
Destination: undefined
Destination target: undefined
Livereload: true
Livereload port: 35729
Platform: web
Port: 8000
Theme: alta
Theme platform: web
Theme version: 8.0.0
Building app.
Cleaning staging path.
Running before_build hook.
Copy files to staging directory.
Copy finished.
Copy library files to staging directory.
Copy finished.
Copy reference components to staging directory.
Copy finished.
Copy local web components
Copy local web components skipped
Optimizing svg into SVG sprites.
Svg optimization task finished.
Svg optimization task finished.
Compiling sass...
Sass compile finished.
Task index.html cdn bundle injection finished.
Running theme injection task.
Task index.html theme path injection finished.
Running theme copy task.
Theme copy task finished.
Running injection tasks.
Task main.js paths injection finished.
runAllComponentHooks
Running after_build hook.
Running before_serve hook.
Starting web server.
Connecting to http://localhost:8000
Starting watcher.
Running after_serve hook.
Server ready: http://localhost:8000
Listening on port 35729.
Watching files.
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: spawn xdg-open ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)




npm install http-server -g


chronos@localhost /home/user/46f836ee257e57280b1bac56c5164f65dcfcfbbe/Projects/robovault_ui/web $ node /mnt/stateful_partition/dev_image/share/nodebrew/node/v10.18.0/lib/node_modules/http-server/bin/http-server
Starting up http-server, serving ./
Available on:
  http://127.0.0.1:8080
  http://192.168.0.101:8080
Hit CTRL-C to stop the server

Tuesday, January 7, 2020

I just put a lecture here

This is a message for every new user executing sudo and elevate previlegies :


[eugene@localhost tt18.1.2.4.0]$  sudo groupadd -g 10000 timesten

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.


In this default lecture I have found one of programming ethics principles and Spider-map phrase about power and responsibility :

  • Contribute to society and human well-being. Programmers should work to develop computer systems that can reduce negative consequences to society, such as threats to safety and health, and that can make everyday activities and work easier. It is “an obligation to develop to high standards” (Savage).[3]
  • Avoid harm to others. Computer systems have an indirect impact on third parties. They can cause loss of information and resources that might result severely harmful for users, the general public, or employers. Therefore, software developers should minimize the risk of harming others due to coding errors, or security issues, by following standards to design and test systems (Code of Ethics and Professional Conduct).[2]
  • Be honest and trustworthy. This principle encourages programmers to be honest and aware of their limitations in knowledge and education when writing computer systems. Also, if a programmer knows there is something wrong with a computer system, he or she should report it immediately to avoid undesirable consequences.
  • Give proper credit for intellectual property. It is mandatory for every software developer to never use and take credit for someone else's work, even when it has not been protected by a copyright law, patent, etc. They must recognize and fully credit other people's works, and they should use their own ideas to develop software.
  • Respect the privacy of others. Computer systems are wrongly used by some people to violate the privacy of others. Software developers should write programs that can protect users’ private information and that can avoid other undesired people to have unauthorized access to it (Code of Ethics and Professional Conduct).
  • Honor confidentiality. Unless required by law or any other ethical guideline, a programmer must keep secret any additional information related to his or her employer that arises from working in a project.
From Software Engineering Code of Ethics and Professional Practice[4] (IEEE, ACM):
  • Approve software only if they have a well-founded belief it is safe and meets specifications. Programmers cannot assume that a system is ready to use only because it performs the tasks needed. They should make sure these systems are also safe and meet every specification required by the user. If programs are not safe, users are unprotected from hackers that could steal important information or money. Therefore, several tests should be performed in order to ensure a system's security before approving it.
  • Accept full responsibility for their own work. If a program presents errors, the software developer should accept full responsibility for his or her work, and should work on revising, correcting, modifying, and testing it.
  • Not knowingly use software that is obtained or retained either illegally or unethically. If a computer system will be used as a base for the creation of another, then permission to do so should be asked by the programmer. This principle prohibits using any other software for any purpose if the way it was gotten is not clear or is known to be illegal or unethical.
  • Identify, define, and address ethical, economic, cultural, legal and environmental issues related to work projects. If a programmer notices and identifies that working on a project will lead to any kind of problems, then the programmer should report it to his or her employer before continuing.
  • Ensure that specifications for software on which they work satisfy the users’ requirements and they have the appropriate approvals. Software developers should come to their employers to ask for the correspondent approval to the system they are creating before continuing working on the next part. If it doesn't meet the requirements, then a modification to the source code of the system should be made.
  • Ensure adequate testing, debugging and review of software. Programmers should perform the appropriate tests to the pieces of software they work with, and should check for errors and system security holes to make sure that the programs are well implemented.
  • Not engage in deceptive financial practices such as bribery, double billing, or other improper financial practices. Programmers are exposed to be participants in illegal activities to get money. They get involved in them due to threats, economic issues, or simply because they want to obtain easy money by taking advantage of their knowledge about how computer systems work. This guideline prohibits programmer involvement in such unlawful actions.
  • Improve their ability to create safe, reliable, and useful quality software. Since technology advances faster year by year, and so does virtual criminality, the need of well-structured and designed programs is increasing. Computer systems get old and limited by new ones and new devices. Programmers should “further their knowledge of developments in the analysis, specification, design, development, maintenance, and testing software and related documents” (Software Engineering Code of Ethics and Professional Practice)[4] in order to create better pieces of software.




debug magazine archive

  71 jounals still available on issuu with great story of netlabels time.  debug_mag Publisher Publications - Issuu