<commit_before>00:01 It probably won't surprise you to hear that to delete a blog post 
00:04 we are going to issue an http request to the blog post url with the delete verb. 
00:10 So this is a very simple request, we are just going to say delete/api/blog/id 
00:14 and the response is not going to be any data just 202 that worked. 
00:19 In code, again, this is probably the simplest of the 4 operations that we're doing, 
00:24 with working with data here, including get. 
00:27 So we come up with the url, api/blog/post id 
00:31 and then we're going to issue an http request with a delete verb 
00:35 and we're just going to issue it straight to that url, nothing else is required, 
00:39 and all that is left is to determine did that work, or did it not work, 
00:42 so in our case, the right response code, or the expected response code is 202 
00:46 from the server, you may also want to be on the lookout for 200s
00:50 if whoever wrote the API is not super careful about status codes, 
00:53 or 204 is another reasonable response code that could mean success, 
00:57 it's unlikely this will vary over time for particular API, 
01:01 it's just that they may have made a different choice than 202.
01:04 So you want to check here and then if you get pass that, that post should be deleted. <commit_msg>Update 13.txt<commit_after>00:01 It probably won't surprise you to hear that to delete a blog post 
00:04 we are going to issue an HTTP request to the blog post URL with the DELETE verb. 
00:10 So this is a very simple request, we are just going to say delete/api/blog/id 
00:14 and the response is not going to be any data just 202 that worked. 
00:19 In code, again, this is probably the simplest of the 4 operations that we're doing, 
00:24 with working with data here, including GET. 
00:27 So we come up with the url, api/blog/post id 
00:31 and then we're going to issue an HTTP request with a DELETE verb 
00:35 and we're just going to issue it straight to that URL, nothing else is required, 
00:39 and all that is left is to determine did that work, or did it not work, 
00:42 so in our case, the right response code, or the expected response code is 202 
00:46 from the server, you may also want to be on the lookout for 200s
00:50 if whoever wrote the API is not super careful about status codes, 
00:53 or 204 is another reasonable response code that could mean success. 
00:57 it's unlikely this will vary over time for particular API, 
01:01 it's just that they may have made a different choice than 202.
01:04 So you want to check here and then if you get pass that, that post should be deleted. 

{'fraction_non_alphanumeric': 0.040792985131528785, 'fraction_numerical': 0.06481128478841022, 'mean_word_length': 3.8864059590316575, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '506537', 'n_tokens_mistral': 867, 'n_tokens_neox': 749, 'n_words': 485}