GS Collections has been migrated to the Eclipse Foundation, re-branded as Eclipse Collections. https://www.eclipse.org/collections/

The GS Collections Kata has been migrated to the Eclipse Foundation, re-branded as the Eclipse Collections Kata. https://github.com/eclipse/eclipse-collections-kata

Linux kernel release 3.x <http://kernel.org/> These are the release notes for Linux version 3. Read them carefully, as they tell you what this is all about, explain how to install the kernel, and what to do if something goes wrong. WHAT IS LINUX? Linux is a clone of the operating system Unix, written from scratch by Linus Torvalds with assistance from a loosely-knit team of hackers across the Net. It aims towards POSIX and Single UNIX Specification compliance. It has all the features you would expect in a modern fully-fledged Unix, including true multitasking, virtual memory, shared libraries, demand loading, shared copy-on-write executables, proper memory management, and multistack networking including IPv4 and IPv6. It is distributed under the GNU General Public License - see the accompanying COPYING file for more details. ON WHAT HARDWARE DOES IT RUN? Although originally developed first for 32-bit x86-based PCs (386 or higher), today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell, IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS, Xtensa, Tilera TILE, AVR32 and Renesas M32R architectures. Linux is easily portable to most general-purpose 32- or 64-bit architectures as long as they have a paged memory management unit (PMMU) and a port of the GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has also been ported to a number of architectures without a PMMU, although functionality is then obviously somewhat limited. Linux has also been ported to itself. You can now run the kernel as a userspace application - this is called UserMode Linux (UML). DOCUMENTATION: - There is a lot of documentation available both in electronic form on the Internet and in books, both Linux-specific and pertaining to general UNIX questions. I'd recommend looking into the documentation subdirectories on any Linux FTP site for the LDP (Linux Documentation Project) books. This README is not meant to be documentation on the system: there are much better sources available. - There are various README files in the Documentation/ subdirectory: these typically contain kernel-specific installation notes for some drivers for example. See Documentation/00-INDEX for a list of what is contained in each file. Please read the Changes file, as it contains information about the problems, which may result by upgrading your kernel. - The Documentation/DocBook/ subdirectory contains several guides for kernel developers and users. These guides can be rendered in a number of formats: PostScript (.ps), PDF, HTML, & man-pages, among others. After installation, "make psdocs", "make pdfdocs", "make htmldocs", or "make mandocs" will render the documentation in the requested format. INSTALLING the kernel source: - If you install the full sources, put the kernel tarball in a directory where you have permissions (eg. your home directory) and unpack it: gzip -cd linux-3.X.tar.gz | tar xvf - or bzip2 -dc linux-3.X.tar.bz2 | tar xvf - Replace "X" with the version number of the latest kernel. Do NOT use the /usr/src/linux area! This area has a (usually incomplete) set of kernel headers that are used by the library header files. They should match the library, and not get messed up by whatever the kernel-du-jour happens to be. - You can also upgrade between 3.x releases by patching. Patches are distributed in the traditional gzip and the newer bzip2 format. To install by patching, get all the newer patch files, enter the top level directory of the kernel source (linux-3.X) and execute: gzip -cd ../patch-3.x.gz | patch -p1 or bzip2 -dc ../patch-3.x.bz2 | patch -p1 Replace "x" for all versions bigger than the version "X" of your current source tree, _in_order_, and you should be ok. You may want to remove the backup files (some-file-name~ or some-file-name.orig), and make sure that there are no failed patches (some-file-name# or some-file-name.rej). If there are, either you or I have made a mistake. Unlike patches for the 3.x kernels, patches for the 3.x.y kernels (also known as the -stable kernels) are not incremental but instead apply directly to the base 3.x kernel. For example, if your base kernel is 3.0 and you want to apply the 3.0.3 patch, you must not first apply the 3.0.1 and 3.0.2 patches. Similarly, if you are running kernel version 3.0.2 and want to jump to 3.0.3, you must first reverse the 3.0.2 patch (that is, patch -R) _before_ applying the 3.0.3 patch. You can read more on this in Documentation/applying-patches.txt Alternatively, the script patch-kernel can be used to automate this process. It determines the current kernel version and applies any patches found. linux/scripts/patch-kernel linux The first argument in the command above is the location of the kernel source. Patches are applied from the current directory, but an alternative directory can be specified as the second argument. - Make sure you have no stale .o files and dependencies lying around: cd linux make mrproper You should now have the sources correctly installed. SOFTWARE REQUIREMENTS Compiling and running the 3.x kernels requires up-to-date versions of various software packages. Consult Documentation/Changes for the minimum version numbers required and how to get updates for these packages. Beware that using excessively old versions of these packages can cause indirect errors that are very difficult to track down, so don't assume that you can just update packages when obvious problems arise during build or operation. BUILD directory for the kernel: When compiling the kernel, all output files will per default be stored together with the kernel source code. Using the option "make O=output/dir" allow you to specify an alternate place for the output files (including .config). Example: kernel source code: /usr/src/linux-3.X build directory: /home/name/build/kernel To configure and build the kernel, use: cd /usr/src/linux-3.X make O=/home/name/build/kernel menuconfig make O=/home/name/build/kernel sudo make O=/home/name/build/kernel modules_install install Please note: If the 'O=output/dir' option is used, then it must be used for all invocations of make. CONFIGURING the kernel: Do not skip this step even if you are only upgrading one minor version. New configuration options are added in each release, and odd problems will turn up if the configuration files are not set up as expected. If you want to carry your existing configuration to a new version with minimal work, use "make oldconfig", which will only ask you for the answers to new questions. - Alternative configuration commands are: "make config" Plain text interface. "make menuconfig" Text based color menus, radiolists & dialogs. "make nconfig" Enhanced text based color menus. "make xconfig" X windows (Qt) based configuration tool. "make gconfig" X windows (Gtk) based configuration tool. "make oldconfig" Default all questions based on the contents of your existing ./.config file and asking about new config symbols. "make silentoldconfig" Like above, but avoids cluttering the screen with questions already answered. Additionally updates the dependencies. "make olddefconfig" Like above, but sets new symbols to their default values without prompting. "make defconfig" Create a ./.config file by using the default symbol values from either arch/$ARCH/defconfig or arch/$ARCH/configs/${PLATFORM}_defconfig, depending on the architecture. "make ${PLATFORM}_defconfig" Create a ./.config file by using the default symbol values from arch/$ARCH/configs/${PLATFORM}_defconfig. Use "make help" to get a list of all available platforms of your architecture. "make allyesconfig" Create a ./.config file by setting symbol values to 'y' as much as possible. "make allmodconfig" Create a ./.config file by setting symbol values to 'm' as much as possible. "make allnoconfig" Create a ./.config file by setting symbol values to 'n' as much as possible. "make randconfig" Create a ./.config file by setting symbol values to random values. "make localmodconfig" Create a config based on current config and loaded modules (lsmod). Disables any module option that is not needed for the loaded modules. To create a localmodconfig for another machine, store the lsmod of that machine into a file and pass it in as a LSMOD parameter. target$ lsmod > /tmp/mylsmod target$ scp /tmp/mylsmod host:/tmp host$ make LSMOD=/tmp/mylsmod localmodconfig The above also works when cross compiling. "make localyesconfig" Similar to localmodconfig, except it will convert all module options to built in (=y) options. You can find more information on using the Linux kernel config tools in Documentation/kbuild/kconfig.txt. - NOTES on "make config": - Having unnecessary drivers will make the kernel bigger, and can under some circumstances lead to problems: probing for a nonexistent controller card may confuse your other controllers - Compiling the kernel with "Processor type" set higher than 386 will result in a kernel that does NOT work on a 386. The kernel will detect this on bootup, and give up. - A kernel with math-emulation compiled in will still use the coprocessor if one is present: the math emulation will just never get used in that case. The kernel will be slightly larger, but will work on different machines regardless of whether they have a math coprocessor or not. - The "kernel hacking" configuration details usually result in a bigger or slower kernel (or both), and can even make the kernel less stable by configuring some routines to actively try to break bad code to find kernel problems (kmalloc()). Thus you should probably answer 'n' to the questions for "development", "experimental", or "debugging" features. COMPILING the kernel: - Make sure you have at least gcc 3.2 available. For more information, refer to Documentation/Changes. Please note that you can still run a.out user programs with this kernel. - Do a "make" to create a compressed kernel image. It is also possible to do "make install" if you have lilo installed to suit the kernel makefiles, but you may want to check your particular lilo setup first. To do the actual install, you have to be root, but none of the normal build should require that. Don't take the name of root in vain. - If you configured any of the parts of the kernel as `modules', you will also have to do "make modules_install". - Verbose kernel compile/build output: Normally, the kernel build system runs in a fairly quiet mode (but not totally silent). However, sometimes you or other kernel developers need to see compile, link, or other commands exactly as they are executed. For this, use "verbose" build mode. This is done by inserting "V=1" in the "make" command. E.g.: make V=1 all To have the build system also tell the reason for the rebuild of each target, use "V=2". The default is "V=0". - Keep a backup kernel handy in case something goes wrong. This is especially true for the development releases, since each new release contains new code which has not been debugged. Make sure you keep a backup of the modules corresponding to that kernel, as well. If you are installing a new kernel with the same version number as your working kernel, make a backup of your modules directory before you do a "make modules_install". Alternatively, before compiling, use the kernel config option "LOCALVERSION" to append a unique suffix to the regular kernel version. LOCALVERSION can be set in the "General Setup" menu. - In order to boot your new kernel, you'll need to copy the kernel image (e.g. .../linux/arch/i386/boot/bzImage after compilation) to the place where your regular bootable kernel is found. - Booting a kernel directly from a floppy without the assistance of a bootloader such as LILO, is no longer supported. If you boot Linux from the hard drive, chances are you use LILO, which uses the kernel image as specified in the file /etc/lilo.conf. The kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or /boot/bzImage. To use the new kernel, save a copy of the old image and copy the new image over the old one. Then, you MUST RERUN LILO to update the loading map!! If you don't, you won't be able to boot the new kernel image. Reinstalling LILO is usually a matter of running /sbin/lilo. You may wish to edit /etc/lilo.conf to specify an entry for your old kernel image (say, /vmlinux.old) in case the new one does not work. See the LILO docs for more information. After reinstalling LILO, you should be all set. Shutdown the system, reboot, and enjoy! If you ever need to change the default root device, video mode, ramdisk size, etc. in the kernel image, use the 'rdev' program (or alternatively the LILO boot options when appropriate). No need to recompile the kernel to change these parameters. - Reboot with the new kernel and enjoy. IF SOMETHING GOES WRONG: - If you have problems that seem to be due to kernel bugs, please check the file MAINTAINERS to see if there is a particular person associated with the part of the kernel that you are having trouble with. If there isn't anyone listed there, then the second best thing is to mail them to me (torvalds@linux-foundation.org), and possibly to any other relevant mailing-list or to the newsgroup. - In all bug-reports, *please* tell what kernel you are talking about, how to duplicate the problem, and what your setup is (use your common sense). If the problem is new, tell me so, and if the problem is old, please try to tell me when you first noticed it. - If the bug results in a message like unable to handle kernel paging request at address C0000010 Oops: 0002 EIP: 0010:XXXXXXXX eax: xxxxxxxx ebx: xxxxxxxx ecx: xxxxxxxx edx: xxxxxxxx esi: xxxxxxxx edi: xxxxxxxx ebp: xxxxxxxx ds: xxxx es: xxxx fs: xxxx gs: xxxx Pid: xx, process nr: xx xx xx xx xx xx xx xx xx xx xx or similar kernel debugging information on your screen or in your system log, please duplicate it *exactly*. The dump may look incomprehensible to you, but it does contain information that may help debugging the problem. The text above the dump is also important: it tells something about why the kernel dumped code (in the above example, it's due to a bad kernel pointer). More information on making sense of the dump is in Documentation/oops-tracing.txt - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump as is, otherwise you will have to use the "ksymoops" program to make sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred). This utility can be downloaded from ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ . Alternatively, you can do the dump lookup by hand: - In debugging dumps like the above, it helps enormously if you can look up what the EIP value means. The hex value as such doesn't help me or anybody else very much: it will depend on your particular kernel setup. What you should do is take the hex value from the EIP line (ignore the "0010:"), and look it up in the kernel namelist to see which kernel function contains the offending address. To find out the kernel function name, you'll need to find the system binary associated with the kernel that exhibited the symptom. This is the file 'linux/vmlinux'. To extract the namelist and match it against the EIP from the kernel crash, do: nm vmlinux | sort | less This will give you a list of kernel addresses sorted in ascending order, from which it is simple to find the function that contains the offending address. Note that the address given by the kernel debugging messages will not necessarily match exactly with the function addresses (in fact, that is very unlikely), so you can't just 'grep' the list: the list will, however, give you the starting point of each kernel function, so by looking for the function that has a starting address lower than the one you are searching for but is followed by a function with a higher address you will find the one you want. In fact, it may be a good idea to include a bit of "context" in your problem report, giving a few lines around the interesting one. If you for some reason cannot do the above (you have a pre-compiled kernel image or similar), telling me as much about your setup as possible will help. Please read the REPORTING-BUGS document for details. - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you cannot change values or set break points.) To do this, first compile the kernel with -g; edit arch/i386/Makefile appropriately, then do a "make clean". You'll also need to enable CONFIG_PROC_FS (via "make config"). After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore". You can now use all the usual gdb commands. The command to look up the point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes with the EIP value.) gdb'ing a non-running kernel currently fails because gdb (wrongly) disregards the starting offset for which the kernel is compiled.

An observable lists library with upcast compatibility, list wrapping, reentrancy protection, thread safety, list binding and robust unit testing.

** This assignment will combine a few things that you have learned in this class and will require a little learning on your own. Do your best and be creative. If you need help ask sooner rather than later in slack. Myself and your classmates are here to help and do not wait to the last minute to do this assignment. ** You may work in two person teams, if you plan to do so please email me to let me know who you are working with. You may NOT work in multiple teams. ** You may use python, JAVA or node.js (javascript) for this assignment. ** I have listed some tutorials below, but you may need to google some on your own. What You Will Do: You will create a RESTful web service that runs in a docker container. Your web service will contain two GET routes: One that displays a collection of records One that displays a single record that the corresponds to an ID Example: If I created two routes, /customers and /customers/35 (note, that 35 is the ID of a given customer in my database) The data returned from your web service routes must be in JSON or XML form. Note, if you would like to load your results in a web page you are welcome to do so, you just need a way to display the data your routes return in a web browser. You will create a hardcoded JSON file based database as the backing datastore for your web service routes. Note, if you are comfortable using a SQL or NO-SQL database as your datastore you may do so but it is not required. Also note, your data model is something you make up. Meaning you can store a collection of cars, customers, food items, restaurants, video games, sports teams etc. Be creative :) This is similar to what the presenter did in the GraphQL video we watched in our last class. He used a JSON file as a database for his demo. You will have to present your work to the class, with a live demo or video you recorded of you running your web service from own computer. This is not optional! Tutorials: Docker What is docker: https://www.youtube.com/watch?v=dz5_lsWlfTU Installing Docker: Windows - https://www.youtube.com/watch?v=wCTTHhehJbU Docker Tutorial (Step by Step) - https://www.youtube.com/watch?v=Vyp5_F42NGs https://blog.talpor.com/2015/01/docker-beginners-tutorial/ https://docs.docker.com/engine/getstarted/ https://hackr.io/tutorials/learn-docker Python RESTful services using Flask: https://code.tutsplus.com/tutorials/building-restful-apis-with-flask-diy--cms-26625 https://impythonist.wordpress.com/2015/07/12/build-an-api-under-30-lines-of-code-with-python-and-flask/ Node + Express REST API Example https://closebrace.com/tutorials/2017-03-02/creating-a-simple-restful-web-app-with-nodejs-express-and-mongodb Node Simple RESTful API (shows using json file as DB) https://www.tutorialspoint.com/nodejs/nodejs_restful_api.htm Dockerize your Flask App https://www.smartfile.com/blog/dockerizing-a-python-flask-application/ http://containertutorials.com/docker-compose/flask-simple-app.html Docker + Spring Boot (JAVA) https://spring.io/guides/gs/spring-boot-docker/ To Submit The Assignment (Read Carefully): ** Please follow all instructions as not following them will lead to loss of points. Create a github account. Create public github repository and all all of your source code for this assignment to the repository. (See the “getting started with github” document in the “Course Documents > Tutorials & Cheat Sheets” folder for help) Make sure to add a README file to the root of your repository that describes what your web service does. Create a presentation powerpoint slide deck that contains 2 slides: A title slides that contains your name(s) and the name of your web service project A slide that talks a little about your data model Submit the following to the “Submit Assignment” thread in RESTful Web Service Implementation + Docker discussion board. The powerpoint slide file. Link to your public github repository that contains all of the source code including your JSON database file. Note, if you worked with classmate for this assignment...if you did please state the person you worked with.

# Forecasting Stock Market Prices It is a **Time Series** dataset.A time series is simply a series of data points ordered in time.In a time series, time is often the independent variable and the goal is usually to make a forecast for the future. ## PROBLEM STATEMENT: Our Aim is to create a model that can forecast the future stock price based on the model training and provided dataset. ### Data We will be using a [Huge stock market dataset](https://www.kaggle.com/borismarjanovic/price-volume-data-for-all-us-stocks-etfs) from the Kaggle platform which has a very good collection of datasets.The file we will be using is present in following directory in the dataset zip file input\Data\Stocks\gs.us.txt The data is presented in CSV format as follows : Date, Open, High, Low, Close, Volume, OpenInt. Features: - Date - Open - High - Low - Close - Volume - OpenInt Note that prices have been adjusted for dividends and splits. ### LICENSE OF DATASET : [LICENSE](https://creativecommons.org/publicdomain/zero/1.0/) ### Requirements You will also need to have software installed to run and execute a [Jupyter Notebook](http://ipython.org/notebook.html) If you do not have Python installed yet, it is highly recommended that you install the [Anaconda](http://continuum.io/downloads) distribution of Python, which already has the above packages and more included. This project requires **Python** and the following Python libraries installed: - [NumPy](http://www.numpy.org/) - [Pandas](http://pandas.pydata.org/) - [matplotlib](http://matplotlib.org/) - [scikit-learn](http://scikit-learn.org/stable/) - [statsmodels](https://www.statsmodels.org/stable/) ### Run In a terminal or command window, navigate to the top-level project directory `STOCK MARKET FORECASTING/` (that contains this README) and run one of the following commands: ipython notebook Forecasting_Stock_Market_Prices_task.ipynb or jupyter notebook Forecasting_Stock_Market_Prices_task.ipynb This will open the Jupyter Notebook software and project file in your browser. ### Steps : 1. Importing Libraries 2. Exploring the Dataset 3. Exploratory Data Analysis > * Univariate Analysis 4. Data Preprocessing 5. Model Building > * AUTOREGRESSIVE MODEL > * MOVING AVERAGE MODEL 6. Evaluation > * MEAN SQUARE ERROR > * MEAN ABSOLUTE ERROR > * ROOT MEAN SQUARE ERROR 7. Conclusion

A library of observable dictionaries.

Booting Gs-Collections code kata.

GS@HackTheDeep: Map the Collections

A Gson type adapter library to deserialize Kotlin immutable collections.

*--> Crash <--* Exception: c000001d App: Gw2-64.exe Pid: 1404 Cmdline: BaseAddr: 00007FF762610000 ProgramId: 101 Build: 80238 Module: d3d9.dll When: 2017-08-01T20:17:14Z 2017-08-01T16:17:14-04:00 Uptime: 0 days 0:19:03 Flags: 0 *--> System <--* Name: ANDY-PC IpAddr: 192.168.1.127 Processors: 8 [GenuineIntel:6:14:3] OSVersion: Windows 6.3 (64 bit) *--> System Memory <--* Physical: 8104MB/16322MB 49% Paged: 9411MB/18754MB 50% Virtual: 134215128MB/134217727MB 3% Load: 50% CommitTotal: 9342MB CommitLimit: 18754MB CommitPeak: 11421MB SystemCache: 8704MB HandleCount: 35227 ProcessCount: 87 ThreadCount: 1085 *--> Process Memory <--* Private: 2319MB WorkingSet: 2298MB PeakWorkingSet: 2346MB PageFaults: 4583423 *--> Memory Category Usage (Inclusive) <--* [Category] [Size(MB)] [Count] Root 1111.19 1367660 VRAM 880.36 13669 Programmer Data 700.35 336948 Engine 359.25 167161 VRAM - Prop Tex 321.54 1068 Uncategorized 301.02 1000297 Model-Programmer 245.20 46354 Game 215.70 123891 Content 155.58 43069 VRAM - Character Tex 137.18 385 Collections 90.71 4372 Dictionary 89.26 1364 VRAM - Composite Tex 87.78 294 Gr 85.56 88204 VRAM - Gr Postproc 82.67 20 VRAM - Effect Texture 70.89 344 Art Assets 59.15 14983 Collide 50.66 15432 Text 46.34 4134 Gr Umbra 45.63 2182 Character Models 44.14 2835 Composite Models 43.83 1496 Composite Tex Pool 32.84 68 Composite Tex 32.84 68 *--> Memory Category Usage (Exclusive) <--* [Category] [Size(MB)] [Count] VRAM - Prop Tex 321.54 1068 Uncategorized 301.02 1000297 Model-Programmer 237.69 30644 Content 155.58 43069 VRAM - Character Tex 137.18 385 Dictionary 89.26 1364 VRAM - Composite Tex 87.78 294 VRAM - Gr Postproc 82.67 20 VRAM - Effect Texture 70.89 344 Text 46.34 4134 Gr Umbra 45.63 2182 Composite Tex Pool 32.84 68 Collide 32.24 1099 VRAM - DirectX Geo Buffers 29.20 1078 VRAM - UI Textures 23.89 412 Archive 20.51 38 VRAM - Gr Img 17.52 8 Collide Havok 13.26 13902 VRAM - DDI Shader 12.99 9665 VRAM - World Map Tex 11.69 55 Gr Model 11.59 25298 Composite Packfile 10.83 334 VRAM - Prop Geo 10.37 85 Map Zone 10.16 12510 *--> DllList <--* D:\Guild Wars 2\Gw2-64.exe C:\WINDOWS\SYSTEM32\ntdll.dll C:\WINDOWS\system32\KERNEL32.DLL C:\WINDOWS\system32\KERNELBASE.dll C:\WINDOWS\system32\apphelp.dll C:\WINDOWS\system32\USER32.dll C:\WINDOWS\system32\ADVAPI32.dll C:\WINDOWS\SYSTEM32\VERSION.dll C:\WINDOWS\system32\WS2_32.dll C:\WINDOWS\SYSTEM32\WTSAPI32.dll C:\WINDOWS\SYSTEM32\WINMM.dll C:\WINDOWS\system32\WINTRUST.dll C:\WINDOWS\system32\PSAPI.DLL C:\WINDOWS\system32\GDI32.dll C:\WINDOWS\system32\ole32.dll C:\WINDOWS\system32\OLEAUT32.dll C:\WINDOWS\system32\SHELL32.dll C:\WINDOWS\SYSTEM32\MSACM32.dll C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.18696_none_9333287b4748e6ab\gdiplus.dll C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17810_none_34ae2abd958aedeb\COMCTL32.dll C:\WINDOWS\system32\CRYPT32.dll C:\WINDOWS\SYSTEM32\USP10.dll C:\WINDOWS\SYSTEM32\MSIMG32.dll C:\WINDOWS\SYSTEM32\Secur32.dll C:\WINDOWS\system32\msvcrt.dll C:\WINDOWS\SYSTEM32\sechost.dll C:\WINDOWS\system32\RPCRT4.dll C:\WINDOWS\system32\NSI.dll C:\WINDOWS\SYSTEM32\WINMMBASE.dll C:\WINDOWS\system32\MSASN1.dll C:\WINDOWS\SYSTEM32\combase.dll C:\WINDOWS\system32\SHLWAPI.dll C:\WINDOWS\system32\SspiCli.dll C:\WINDOWS\SYSTEM32\cfgmgr32.dll C:\WINDOWS\SYSTEM32\DEVOBJ.dll C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll C:\WINDOWS\system32\IMM32.DLL C:\WINDOWS\system32\MSCTF.dll C:\WINDOWS\SYSTEM32\dbghelp.dll C:\WINDOWS\SYSTEM32\SHCORE.dll C:\WINDOWS\SYSTEM32\profapi.dll C:\WINDOWS\SYSTEM32\kernel.appcore.dll C:\WINDOWS\system32\uxtheme.dll C:\WINDOWS\SYSTEM32\clbcatq.dll C:\WINDOWS\SYSTEM32\ntmarta.dll C:\WINDOWS\system32\dwmapi.dll C:\WINDOWS\system32\napinsp.dll C:\WINDOWS\system32\pnrpnsp.dll C:\WINDOWS\system32\NLAapi.dll C:\WINDOWS\System32\mswsock.dll C:\WINDOWS\SYSTEM32\DNSAPI.dll C:\WINDOWS\System32\winrnr.dll C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL C:\WINDOWS\SYSTEM32\WINNSI.DLL C:\WINDOWS\SYSTEM32\WindowsCodecs.dll C:\WINDOWS\System32\fwpuclnt.dll C:\Windows\System32\rasadhlp.dll D:\Guild Wars 2\bin64\CoherentUI64.dll C:\WINDOWS\SYSTEM32\d3d9.dll C:\WINDOWS\SYSTEM32\CRYPTSP.dll C:\WINDOWS\system32\rsaenh.dll C:\WINDOWS\SYSTEM32\bcrypt.dll C:\WINDOWS\system32\imagehlp.dll C:\WINDOWS\SYSTEM32\ncrypt.dll C:\WINDOWS\SYSTEM32\NTASN1.dll C:\WINDOWS\SYSTEM32\gpapi.dll C:\Windows\System32\cryptnet.dll C:\WINDOWS\system32\WLDAP32.dll C:\WINDOWS\SYSTEM32\DPAPI.dll C:\WINDOWS\SYSTEM32\aticfx64.dll C:\WINDOWS\SYSTEM32\atiu9p64.dll C:\WINDOWS\SYSTEM32\atiumd64.dll C:\WINDOWS\SYSTEM32\atiumd6a.dll C:\WINDOWS\SYSTEM32\POWRPROF.dll C:\Users\Andy\AppData\Local\Temp\D460E7C2-48D4-4574-B11F-85B926645317\amd_ags_x64.dll C:\WINDOWS\SYSTEM32\atiadlxx.dll C:\WINDOWS\SYSTEM32\PROPSYS.dll C:\WINDOWS\SYSTEM32\USERENV.dll C:\WINDOWS\system32\SETUPAPI.dll C:\WINDOWS\system32\winbrand.dll C:\WINDOWS\SYSTEM32\dsound.dll C:\WINDOWS\SYSTEM32\WINSTA.dll C:\WINDOWS\System32\MMDevApi.dll C:\WINDOWS\SYSTEM32\wdmaud.drv C:\WINDOWS\SYSTEM32\ksuser.dll C:\WINDOWS\SYSTEM32\AVRT.dll C:\WINDOWS\SYSTEM32\AUDIOSES.DLL C:\WINDOWS\SYSTEM32\msacm32.drv C:\WINDOWS\SYSTEM32\midimap.dll C:\WINDOWS\SYSTEM32\mscms.dll C:\WINDOWS\SYSTEM32\icm32.dll [DbgHelp.dll is C:\WINDOWS\SYSTEM32\dbghelp.dll] [DbgHelp.dll version 6.3.9600.17787 (64/32-bit compatible)] *--> Thread 0x15cc <--* *--> Trace <--* Pc Rt : Args 00007ffe`53490155 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 *--> Thread registers <--* rax=0000000034545844 rbx=00000044501ef3a0 rcx=000000004c4c554e rdx=00000044501ef3a0 rsi=00000044505c5410 rdi=00000044501ef418 rip=00007ffe53490155 rsp=00000044501ef2e8 rbp=00000044501ef429 r8=00000044501ef3f8 r9=0000000000000003 r10=0000000000000000 r11=00007ffe5ed4470b r12=00000044501ef3f8 r13=0000000000000001 r14=0000000000000000 r15=0000004482ce8340 cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206 rbx-32 00000044501EF380 00000044`5de77938 00007ffe`34d1f87b ffffffff`00000000 00000000`00000000 rbx +0 00000044501EF3A0 00000002`4c4c554e 00000000`00000000 00000044`501ef418 00000000`00000001 rbx+32 00000044501EF3C0 00000000`00000000 00000000`00000000 00000000`00000000 00000001`00000081 rdx-32 00000044501EF380 00000044`5de77938 00007ffe`34d1f87b ffffffff`00000000 00000000`00000000 rdx +0 00000044501EF3A0 00000002`4c4c554e 00000000`00000000 00000044`501ef418 00000000`00000001 rdx+32 00000044501EF3C0 00000000`00000000 00000000`00000000 00000000`00000000 00000001`00000081 r8-32 00000044501EF3D8 00000001`00000081 00000000`00000000 00007ffe`34d1c1a5 00000000`00000000 r8 +0 00000044501EF3F8 00000000`00000000 00000000`00000000 00000044`501ef418 00000044`501ef418 r8+32 00000044501EF418 00000200`00000200 00000000`00000000 00000000`00000000 00000000`00000000 *--> Code <--* 00007ffe`53490135 0f8447d9 f7ffffc9 0f84bfe2 f7ffffc9 ..G............. 00007ffe`53490145 0f85bde2 f7ffe932 d9f7ffb8 44585434 .......2....DXT4 00007ffe`53490155 3bc87742 743481f9 4d455431 0f849be2 ;.wBt4..MET1.... 00007ffe`53490165 f7ff81f9 44585431 742681f9 44585432 ....DXT1t&..DXT2 00007ffe`53490175 741881f9 59555932 0f84c239 fbff81f9 t...YUY2...9.... 00007ffe`53490185 44585433 0f8579e2 f7ffb8f0 ffffffc3 DXT3..y......... *--> Stack <--* 00000044`501ef2e8 00007ffe`534d609e 00000000`00000000 ffffffff`fffe7960 00000000`00000000 .`MS............`y.............. 00000044`501ef308 00000044`00000001 00000044`82ce8340 00000000`00000000 00000000`00000001 ....D...@...D................... 00000044`501ef328 00000000`00000000 00000044`501ef418 00000044`505c5410 00000044`501ef429 ...........PD....T\PD...)..PD... 00000044`501ef348 00007ffe`53490e66 00000044`505c5410 00000044`501ef610 00000044`501ef610 f.IS.....T\PD......PD......PD... 00000044`501ef368 00007ffe`34d3196e 00000044`51a8ed98 00000044`501ef449 00000044`5de77938 n..4.......QD...I..PD...8y.]D... 00000044`501ef388 00007ffe`34d1f87b ffffffff`00000000 00000000`00000000 00000002`4c4c554e {..4....................NULL.... 00000044`501ef3a8 00000000`00000000 00000044`501ef418 00000000`00000001 00000000`00000000 ...........PD................... 00000044`501ef3c8 00000000`00000000 00000000`00000000 00000001`00000081 00000000`00000000 ................................ 00000044`501ef3e8 00007ffe`34d1c1a5 00000000`00000000 00000000`00000000 00000000`00000000 ...4............................ 00000044`501ef408 00000044`501ef418 00000044`501ef418 00000200`00000200 00000000`00000000 ...PD......PD................... 00000044`501ef428 00000000`00000000 00000000`00000000 00000044`501ef650 00000044`2f9b819c ................P..PD....../D... 00000044`501ef448 0000436f`c359fadf 00000000`00000000 00000044`505c5410 00000000`00000000 ..Y.oC...........T\PD........... 00000044`501ef468 00000000`00000000 00000000`00000001 00000044`501ef610 00000044`501ef510 ...................PD......PD... 00000044`501ef488 00007ffe`5341280c 00000044`4a470000 00000000`00000000 00000000`00000000 .(AS......GJD................... 00000044`501ef4a8 00000000`0000000d 00000000`000000d0 00000000`00140008 00000000`000000c0 ................................ 00000044`501ef4c8 00007ffe`5ece0d07 00000044`4a370000 00007ffe`00000000 00000000`000000c0 ...^......7JD................... 00000044`501ef4e8 00000000`00140008 00000044`50633d20 00007ffe`534116b3 00000000`00000000 ........ =cPD.....AS............ 00000044`501ef508 00007ffe`53411720 00000044`501ef690 00007ffe`534127a3 00007ffe`534127d0 .AS.......PD....'AS.....'AS.... 00000044`501ef528 00000044`50633d20 00000000`00000000 00000044`501ef610 ffffffff`fffffffe =cPD..............PD........... 00000044`501ef548 00007ff7`628680e8 00000044`7d249f00 00000000`00000000 00000044`501ef800 ...b......$}D..............PD... 00000044`501ef568 00000000`00000000 00000044`7d249f00 00000044`50633d20 00007ffe`53412730 ..........$}D... =cPD...0'AS.... 00000044`501ef588 00007ffe`5341b228 00000000`00000000 00000044`00000000 00000044`00000001 (.AS................D.......D... 00000044`501ef5a8 00000000`00000000 00000000`00000001 00000000`00000000 00000000`4c4c554e ........................NULL.... 00000044`501ef5c8 00000000`4c4c554e 00000000`00000000 00007ffe`00000000 00000000`00000000 NULL............................ 00000044`501ef5e8 00000044`501ef800 00000000`00000000 00007ffe`53413203 00000000`00000000 ...PD............2AS............ 00000044`501ef608 00007ffe`34d1c80f 00000044`505c5410 00000044`501ef670 00000001`00000001 ...4.....T\PD...p..PD........... 00000044`501ef628 00000000`08000001 4c4c554e`00000000 00000000`00000000 00000000`00000000 ............NULL................ 00000044`501ef648 00000000`00000000 00000044`50633d20 00000000`00000000 00000000`00000000 ........ =cPD................... 00000044`501ef668 00000044`7d249f38 00000200`00000200 00000000`00000000 00000000`00000000 8.$}D........................... 00000044`501ef688 00000000`00000000 00000044`82ce8340 00007ffe`00000001 00000000`00000000 ........@...D................... 00000044`501ef6a8 00000000`00000000 00000000`00000200 00000000`00000000 00000044`50633d20 ........................ =cPD... 00000044`501ef6c8 00000000`00000000 00000000`4c4c554e 00007ffe`53430ef7 00000000`00000001 ........NULL......CS............ *--> Error Logs <--* Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x080b24': Failed to resolve AimIK bone indices. Model '0x08223a': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x080b24': Failed to resolve AimIK bone indices. Texture '0x03539b' dimensions too small Loading '0x03539b' texture failed Model '0x08223f': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Couldn't find projectile effect for skill 'ViarU.pGPgw' Model '0x08223a': Failed to resolve AimIK bone indices. Texture missing mip chain: 0x19d40c Texture missing mip chain: 0x19d407 Texture missing mip chain: 0x19d40a Model '0x080b24': Failed to resolve AimIK bone indices. Texture missing mip chain: 0x00d956 Texture missing mip chain: 0x00d95a Texture missing mip chain: 0x00d95c Model '0x08223a': Failed to resolve AimIK bone indices. Model '0x080b24': Failed to resolve AimIK bone indices. Model '0x08223a': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x08223f': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x080b24': Failed to resolve AimIK bone indices. Model '0x08223a': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x08223a': Failed to resolve AimIK bone indices. Model '0x080b24': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x1aac89': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x1aac89': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. Model '0x082239': Failed to resolve AimIK bone indices. *--> DirectX Device Info <--* VendorId = 0x1002 DeviceId = 0x6798 Version = 22.19.0171.1024 Description = AMD Radeon R9 200 Series Compat = 0x00000000 VidMem = 0 MB

A desktop GUI application for Billing and inventory management

A small collection of singularity gs snippets for sublimetext

repo to study 3DGS, include many GS collection of papper with code

a collection of basic programs I've written on my apple ii gs

Collection of command line tool commands (imagemagick, ffmpeg, gs, etc) I frequently use

pingu repository - PKGBUILDs collection dedicated to GameShell Arch Linux ARM port - http://gs.dread.fr/arch/armv7h/

📝 My personal collection of document manipulation modules for working with Google Docs Editors, all written in an Apps Script (.gs file).

🚀 A collection of JavaScript and ServiceNow scripting practice exercises. Includes core JavaScript examples (for Node.js) and ServiceNow-specific scripts (using GlideRecord, gs, GlideAjax, etc.). This repo tracks my learning journey through CSA & CAD certifications, ServiceNow developer lessons (Chuck Tomasi, Earl Duque), and hands-on labs.

GS Collection V-x01

[関Java]GS Collections 道場

No description available

A collection of .gs files

Collection of gs project templates

No description available

No description available

No description available

Smartphone-friendly web app for a Compost Collection service.

No description available

The 'gs-collections' (goldmansachs java collection framework) study project