四种结果

         “这比喻乃是这样:种子就是神的道。 那些在路旁的,就是人听了道,随后魔鬼来,从他们心里把道夺去,恐怕他们信了得救。 那些在磐石上的,就是人听道,欢喜领受,但心中没有根,不过暂时相信,及至遇见试炼就退后了。 那落在荆棘里的,就是人听了道,走开以后,被今生的思虑、钱财、宴乐挤住了,便结不出成熟的子粒来。 那落在好土里的,就是人听了道,持守在诚实善良的心里,并且忍耐着结实。” (路加福音 8:11-15 和合本)

        Now the parable is this: The seed is the word of God.Those by the way side are they that hear; then cometh the devil, and taketh away the word out of their hearts, lest they should believe and be saved.They on the rock are they, which, when they hear, receive the word with joy; and these have no root, which for a while believe, and in time of temptation fall away.And that which fell among thorns are they, which, when they have heard, go forth, and are choked with cares and riches and pleasures of this life, and bring no fruit to perfection.But that on the good ground are they, which in an honest and good heart, having heard the word, keep it, and bring forth fruit with patience. (Luke 8:11-15 KJV)

        在听道的人群中,有一些人是属于第一种情况,如文士们,他们心里早已有了自己的主张,魔鬼早已把很多错误的道理塞在他们的心里,使他们把这些错误的道理当作正确的,他们用他们所相信的,所以为的这些道理,去判断一切,以至于真理根本无法进入他们的心。今天,有人以为无神论是正确的,有人认为佛教的理论是正确的,也有人笃信可兰经的理论,所以他们的心再也没有办法听见别的。魔鬼就是那迷惑人的,把错误的道理充满人的心,目的就是为了抵挡圣经的真理,这就是飞鸟来吃尽了的现象。

        也有一些人,他们听了道,情感上愿意接受,很兴奋,但是并没有让主的道深深地进入他们的心里,也没有把自己的生命真正的交托主。他们觉得这道很好,就接受了,一旦为主的道遭遇艰难和痛苦,他们马上就退后了,这是第二种情况!

       第三种情况是,他们觉得主很好,也愿意接受相信,但是他们放不下这个世界,各种各样的思虑、钱财等等的迷惑,以致他们不能够真心的跟随主!就像那个来找主的少年财主,最后因着放不下钱财,忧忧愁愁地走了。

        而最后一种人,就像彼得保罗这些人,他们有一个诚实的心,听见主的道,蒙了光照后,就接受耶稣基督作他们的救主。既是真理,他们就不顾一切地跟随,不管遇到多少艰难险阻,也跟随到底,以至于结果累累,这就是最后一种田地。

 用比喻的目的

        门徒问耶稣说:“这比喻是什么意思呢?” 他说:“ 神国的奥秘只叫你们知道;至于别人,就用比喻,叫他们看也看不见,听也听不明。” (路加福音 8:9-10 和合本)

        And his disciples asked him, saying, What might this parable be?And he said, Unto you it is given to know the mysteries of the kingdom of God: but to others in parables; that seeing they might not see, and hearing they might not understand. (Luke 8:9-10 KJV)

         耶稣用一些普通的言论作为起头,来答复门徒对这个故事的询问。祂把门徒跟其他人作比较:特别强调你们。神国的奥秘是启示给他们的。真秘(mystēria)是那些我们自己永远无法发现,但神已经将之启示出来的真理;这个字在保罗书信中很常见,但在福音书中却只出现在与此有关的经文中。但至于别人,看却看不见,听也听不明;他们听见了比喻,却不明白它们的意义。比喻启示了真理,同时也把真理隐藏起来:它们把真理向诚心寻求的人启示出来,他们不厌其烦的在表面底下挖掘,发现其意义;但它们也把真理向那只以听听故事为满足的人隐藏起来。这很明显是比喻的结果,但耶稣却说这也是它们的目的(叫……)。对那些认真的人而言,比喻是知识的矿场;但对那些随随便便、漫不经心的人来说,它们是个审判。求主怜悯我们,让我们成为谦卑跟随主的人,因为主向谦卑跟随他的人就显出来,向骄傲的人就藏起来,所以我们要不断地求主保守我们的心,始终有一颗谦卑受教寻求的心。


How to fix up sendgrid-python, BadRequestsError

Traceback (most recent call last):
  File "sendmail.py", line 79, in <module>
    response = sg.client.mail.send.post(request_body=mail.get())
  File "/home/errong_leng/.local/lib/python2.7/site-packages/python_http_client/client.py", line 227, in http_request
    return Response(self._make_request(opener, request))
  File "/home/errong_leng/.local/lib/python2.7/site-packages/python_http_client/client.py", line 161, in _make_request
    raise exc
python_http_client.exceptions.BadRequestsError

The easy way is to catch this exception and print out the error body:
try:
    response = sg.client.mail.send.post(request_body=mail.get())
    print(response.status_code)
    print(response.body)
    print(response.headers)
except Exception as e:
    print (e.body)  #print (e.read()) 


Then you can know why bad request error reported, such as:
{"errors":[{"message":"Following RFC 1341, section 7.2, if either text/html or text/plain are to be sent in your email: text/plain needs to be first, followed by text/html, followed by any other content.","field":"content","help":null}]}

{"errors":[{"message":"The subject is required. You can get around this requirement if you use a template with a subject defined or if every personalization has a subject defined.","field":"subject","help":"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#message.subject"}]}

{"errors":[{"message":"Each email address in the personalization block should be unique between to, cc, and bcc. We found the first duplicate instance of [errong.leng@gmail.com] in the personalizations.0.to field.","field":"personalizations.0","help":"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#message.recipient-errors"}]}

Set up shadowsocks server on your google compute engine(ubuntu os) from shadowsocks-libev sources.

Refers:
https://github.com/shadowsocks/shadowsocks-libev

How to generate crash backtrace just from your serial crash log, without coredump file.

If your crash log have dump maps, user stacks, and you have symbols too,
You can try to get a backtrace via below python scripts.

[2-11624.8825] PC, LR MEMINFO
[2-11624.8825] --------------------------------------------------------------------------------------
[2-11624.8825] PC:46cbfc92, LR:46cbfc59
[2-11624.8825] --------------------------------------------------------------------------------------
[2-11624.8825] PC meminfo (0x46cc005d to 0x46cc0092)
[2-11624.8825] 0040:                                                                               
[2-11624.8825] 0060: be07e9cd 801cf8d0 f04fb085 f1010901 ea4f061b e0015707 d03142b4 f85446a3
[2-11624.8825] 0080: f0055b04 2b010303 ea4fd1f6 f8d85a15 ea4f3a14
[2-11624.8825] --------------------------------------------------------------------------------------
[2-11624.8825] LR meminfo (0x46cbf459 to 0x46cc0059)
[2-11624.8825] f440:                                                                0205ea02
[2-11624.8825] f460: bf0442a2 f8832201 d009202c f84269da 6a191020 f1016a9a ea020101 621a0201
[2-11624.8825] f480: e9ddb002 b0024500 bf004770 8000f3af 4506e96d 5413ea4f e9cd460d ea4f8e04
......
[2-11624.8831] * dump maps on pid (2548 - efl_webprocess)
[2-11624.8831] -----------------------------------------------------------
[2-11624.8831] 00010000-00011000 r-xp 00000000 b3:12 55716      /usr/lib/chromium-efl/efl_webprocess
[2-11624.8831] 00020000-00021000 r--p 00000000 b3:12 55716      /usr/lib/chromium-efl/efl_webprocess
[2-11624.8831] 00021000-00022000 rw-p 00000000 00:00 0         
[2-11624.8831] 00031000-00036000 rw-p 00001000 b3:12 55716      /usr/lib/chromium-efl/efl_webprocess
[2-11624.8831] 00036000-0007c000 rw-p 00000000 00:00 0          [heap]
[2-11624.8831] 0007c000-008ae000 rw-p 00000000 00:00 0          [heap]

[2-11624.8917] -----------------------------------------------------------
[2-11624.8917] * dump user stack
[2-11624.8917] -----------------------------------------------------------
[2-11624.8917] pid(2548) stack vma (0xbe729000 ~ 0xbe74c000)
[2-11624.8917] User Stack: (0xbe749e20 to 0xbe745f10)
[2-11624.8917] -----------------------------------------------------------

fixed: embedded-redis: Unable to run on macOS Sonoma

Issue you might see below error while trying to run embedded-redis for your testing on your macOS after you upgrade to Sonoma. java.la...