mateuszmistecki.pl Report : Visit Site

Technical data of the mateuszmistecki.pl

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host mateuszmistecki.pl. Currently, hosted in Poland and its service provider is Internet Cafe Uslugi Informatyczne Miroslaw Backiel .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

mateusz mistecki software developer home menu daj się poznać 2017 , get noticed! be cautious using the “g” flag in regex april 5, 2017 no comments lately, i’ve stuck with a very interesting problem. but let’s start from the beginning. there’s an internal library application in the company i’m currently working for. in a nutshell, the app allows employees to borrow books the company has and my task was to resolve a problem with search functionality. the search generally works but not always. sometimes it doesn’t show all elements it should, for example, there are two books: “institutional investment management: equity and bond portfolio strategies and applications” “institutional investors (mit press)” when you type “institutional” in the search box only the first of these books appears as the result. but when you type the whole title of the second book it appears normally as it should. however, you never get both of them at the same time. what’s even more interesting, it happened only if you wanted to find books by the word at the beginning of their titles. for example, if the second book had the word “institutional” in the middle of the title then both of them would appear in the search result. strange. firstly i’ve checked the controller responsible for retrieving books from the database but it works correctly and what’s more the controller isn’t involved in the searching process. searching is implemented as filtering on the web page in the angular pipe. pipes in angular are used to filter, format or transform the way the data is displayed. the application’s frontend is written in angular 2 and i’ve to admit that i have never worked with angular before. that’s more or less what the code looked like. c# import { pipe, pipetransform } from '@angular/coreproject'; @pipe({ name: 'searchbook' }) export class searchbookpipe implements pipetransform { transform(value, search) { let regexp = new regexp(search, 'gi'); return value.filter(row => regexp.test(row.title)); } } 1 2 3 4 5 6 7 8 9 import { pipe , pipetransform } from '@angular/coreproject' ; @ pipe ( { name : 'searchbook' } ) export class searchbookpipe implements pipetransform { transform ( value , search ) { let regexp = new regexp ( search , 'gi' ) ; return value . filter ( row = > regexp . test ( row . title ) ) ; } } at first glance, everything looks fine. there is the regex with “i” and “g” attributes which stands for case insensitivities and for a global match respectively. the global match means that it find all matches rather than stopping after the first one. this piece of code, for example, works correctly and the result is true: c# var regexp = regexp.test("institutional investors (mit press)"); var result = value.filter(row => regexp.test(row.title)); 1 2 var regexp = regexp . test ( "institutional investors (mit press)" ) ; var result = value . filter ( row = > regexp . test ( row . title ) ) ; so the title matches search criteria. so why doesn’t the original code work correctly? why doesn’t it return all matches? i spent many hours rewriting the code in different ways and debugging it. finally, my teammate had a look at it and found the bug very quickly. what hi did, was to remove the “g” flag from the regex expression and everything started working as expected. but why? shouldn’t the “g” flag be necessary to find all the occurrences of the searched phrase? generally yes but it should be used when you want to find many occurrences in one string, not many occurrences in many strings. it’s explained on stackoverflow : the regexp object keeps track of the lastindex where a match occurred, so on subsequent matches it will start from the last used index, instead of 0. it explains why the code doesn’t work when the searched expressions are placed at the beginning of the book title but works correctly when they are located in different places in the title. so when we try to use the same regex object for many strings we should reset the index after each check. the conclusion for me is to read the documentation more carefully in such cases because things don’t always work in the way we think they do. another important thing is to ask others to take a look at the code if there is such possibility. it’s often easier for someone “fresh” to find a bug than for somebody who’s staring at the code for many hours. continue reading daj się poznać 2017 , get noticed! bravo microsoft! april 3, 2017 no comments in my post about continous integration in visual studio team services , i wrote it’s impossible to build a code written in .net core 1.1 using team services successfully. after microsoft replaced json configuration file by csproj they didn’t update the build definition. a predefined hosted agent was still looking for json file (an agent is an installable software that runs one build or deployment job at a time). however, four months after the issue was reported and one month after visual studio 2017 was released the problem has been finally resolved. microsoft added a new hosted agent to run the build and everything works as expected now. so let’s take a look at what to do to make the build work. there are only two simple steps needed. first, go to builds tab and edit the build definition. second, go to options and change the default hosted agent to hosted vs2017. that’s all. now you can run the build and see the beloved green colour of success. sources: build and release agents hosted agents support for .net core .csproj files? #3311 continue reading daj się poznać 2017 , get noticed! git commands with examples march 28, 2017 no comments there are plenty of websites about git and its commands on the internet. this one will be plenty plus one. if you’ve read my previous post you probably know that i’ve switched from git flow to github flow lately. during that switch, i had to create and delete some branches using console commands in git bash. they were very simple commands which can be very quickly found on the internet. but i decided to write this post to have this commands archived for me in one place and maybe it would be helpful for someone to see live examples of these commands usage. latest versions of visual studio and continues integrations tools are quite well integrated with git, so sometimes i haven’t been opening git bash for weeks. but at the moment i’m using it more often. firstly, because integration of team services and github isn’t finished yet and i don’t use any other continues integration tool. secondly, i simply want to be more familiar with the console because there are still things you can’t do using gui tools. git bush is simply more powerful. as a quick reminder, when i started working on the googletasksmanager project i was implementing gitflow as a branching strategy model but later i switched to github flow which is much simpler and more convenient for me. so firstly i had created develop branch according to git flow rules and later i had removed it because it wasn’t longer needed after i switched to github flow strategy. below are commands i used then. creating a new branch and switching to it: git checkout -b <branchname> (the command will create a new branch with current uncommitted changes) new branch was created locally and then i had to push it to the remote repository: git push origin <branchname> after i started following github flow rules, develop branch was no longer needed, so i deleted it. but before you are able to delete the branch you have to switch to another one. switching from one branch to another: git checkout <branchname> deleting branch: git branch -d <branchname> viewing all existing branches: git branch -a in the example above the develop branch is still on the list of branches. so let’s remove local reference to deleted branch: git fetch -p and finally, after the fetch the develop branch isn’t listed any longer. sources: basic git commands stackoverflow how to use git branches stackoverflow continue reading

URL analysis for mateuszmistecki.pl

http://mateuszmistecki.pl/2017/03/05/let-it-begin/#comments
http://mateuszmistecki.pl/wp-content/uploads/2017/03/github-flow.png
https://plus.google.com/share?url=http://mateuszmistecki.pl/2017/04/03/bravo-microsoft/
https://plus.google.com/share?url=http://mateuszmistecki.pl/2017/03/05/let-it-begin/
https://plus.google.com/share?url=http://mateuszmistecki.pl/2017/03/27/github-flow/
http://mateuszmistecki.pl/feed/
https://twitter.com/share?url=http://mateuszmistecki.pl/2017/03/12/connecting-visual-studio-team-services-to-github-repository/
http://mateuszmistecki.pl/wp-content/uploads/2017/03/createing-a-branch-sharpen.png
http://mateuszmistecki.pl/2017/03/27/github-flow/#comments
https://twitter.com/share?url=http://mateuszmistecki.pl/2017/03/27/github-flow/
http://mateuszmistecki.pl/wp-content/uploads/2017/04/hosted-vs2017-changed.png
https://www.facebook.com/sharer.php?u=http://mateuszmistecki.pl/2017/03/28/git-commands-with-examples/
http://mateuszmistecki.pl/wp-content/uploads/2017/03/build-started.png
http://mateuszmistecki.pl/2017/03/27/github-flow/
https://plus.google.com/share?url=http://mateuszmistecki.pl/2017/03/28/git-commands-with-examples/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

DOMAIN NAME: mateuszmistecki.pl
registrant type: individual
nameservers: ns1.webio.pl. [194.88.154.133]
ns2.webio.pl. [31.41.209.34]
created: 2010.09.13 14:38:13
last modified: 2018.08.01 07:38:20
renewal date: 2018.09.13 14:38:13

no option

dnssec: Unsigned


REGISTRAR:
Consulting Service Sp. z o.o.
ul. Domaniewska 35A lok.1B
02-672 Warszawa
Polska/Poland
+48.221238080
[email protected]

WHOIS database responses: http://www.dns.pl/english/opiskomunikatow_en.html

WHOIS displays data with a delay not exceeding 15 minutes in relation to the .pl Registry system
Registrant data available at http://dns.pl/cgi-bin/en_whois.pl

  REFERRER http://www.dns.pl/english/index.html

  REGISTRAR NASK

SERVERS

  SERVER pl.whois-servers.net

  ARGS mateuszmistecki.pl

  PORT 43

  TYPE domain

DOMAIN

  CREATED 2010-09-13

  CHANGED 2018-08-01

SPONSOR
Consulting Service Sp. z o.o.
ul. Domaniewska 35A lok.1B
02-672 Warszawa
Polska/Poland
+48.221238080
[email protected]
WHOIS database responses: http://www.dns.pl/english/opiskomunikatow_en.html

  NAME mateuszmistecki.pl

NSERVER

  NS1.WEBIO.PL 194.88.154.133

  NS2.WEBIO.PL 31.41.209.34

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .