weixin_39628247的博客

I still have same problem.

Reproduce 1. chown -hR www-data:www-data ./prestashop 2. git clone https://github.com/PrestaShop/PrestaShop.git 3. cd prestashop 4. docker-compose up

docker Docker version 19.03.2, build 6a30dfc

docker-compose docker-compose version 1.24.1, build 4667896b

error message

\n Reapplying PrestaShop files for enabled volumes ... cp: cannot stat '/tmp/data-ps/prestashop/': No such file or directory

Thank you very much for you work. I watched your Presentations on Youtube and started using botman for small project. I'm a Newbie, but could it be a solution to use notification channels instead of the driver packages for Botman stay up to date ? They are well maintained...

What's the status on this? The library consistently still crashes whenever a user changes their orientation.

This patch will at least act as a bandaid over the crash. I too would like to see a solution to the overall problem that doesn't involve manually handling configchanges

diff -r 44b3f51dfe41 facebook/src/com/facebook/android/FbDialog.java
--- a/facebook/src/com/facebook/android/FbDialog.java   Wed Jul 14 15:52:05 2010 -0400
+++ b/facebook/src/com/facebook/android/FbDialog.java   Wed Jul 14 16:18:27 2010 -0400
@@ -162,7 +162,11 @@
             if (title != null && title.length() > 0) {
                 mTitle.setText(title);
             }
-            mSpinner.dismiss();
+            try {
+                mSpinner.dismiss();
+            } catch( IllegalArgumentException ignored ) {
+                // thrown if the underlying activity was dismissed, eg. during device orientation change
+            }
         }   

     }

We too are seeing very high error rates during login.

+1

Yes, pulled the stable branch and ran "composer update". Now everything is fine again

Sorry my fault, I saw phpseclib has released version 2.0.9 and now stable is running fine. Before they released 2.0.9 the stable branch was broken for new installations as 2.0.8 was installed.

This looks great overall!

Technically this is still relevant for multiple context in a single class, but it's such an edge case that I feel like it belongs on Stack Overflow

I'm not sure this case is so edge, it was the first question that came to my mind when I knew about this

or some recipes section

Is it supported to access multiple contexts from this.context? If so, yes please add info about this somewhere from the beginning.

I imagine something like this:

static contextTypes = {
    myContext1: MyContext1,
    myContext2: MyContext2,
}

or

static contextTypes = [MyContext1, MyContext2]

EDIT: Just noticed this was already requested here: https://github.com/facebook/react/pull/13728#issuecomment-426007618

I see exactly what you're saying, and I understand the functionality of using load_only and dump_only.

Whilst better names such as force_load, etc do improve the usability of the library, it still wouldn't expose API to whitelist fields from being loaded/dumped. (Unless specifying force_load or force_dump implies that any unlisted fields shouldn't be loaded or dumped)

After reading this discussion, I set out to try solve this myself. I implemented a POC function

 python
def merge_schema_errors(errors):
    if errors and errors['_schema']:
        schema_errors = errors['_schema']
        del errors['_schema']

        for f in schema_errors:
            for field, field_errs in f.items():
                if field not in errors:
                    errors[field] = []

                errors[field].extend(field_errs)

    return errors

Which did what I wanted it to, provided I called ValidationError like this:

raise ValidationError({'fieldName': ['Error message here']})

This has a terrible interface, but my use case required it..

But, whilst finishing off writing my validation errors, I noticed the docstring for ValidationError specifies that you can actually provide a tuple or list of field of where to apply the message specified as the first argument of ValidationError

So without any extra code, I got this working by using

 python
ValidationError('This is my validation error', field_names=['myField', 'myField2'])

I hope this clears things up for anyone looking here in the future.

can you help us write a test to get this deployed?

me too !!!

那就是xbindkeys没有绑定快捷键，xbindkeys就是绑定快捷键到某命令上。 你google搜一下xbindkeys文档，因为这是我几年前弄的，现在也忘了。

配置为 "xdotool key --window $(xdotool search --name 'QQ' | head -n1) ctrl+alt+z" control+Mod1 + z

1. alt 改为 Mod1
2. 用 xbindkeys -k 这种方式进行热键配置

最后非常感谢，快捷键能用了。

shell 执行 "xdotool key --window $(xdotool search --name 'QQ' | head -n1) ctrl+alt+z" 试试

shell 执行完，会弹出QQ敞口。 不过ctrl+alt+z 无效。是否要重启什么服务？

"xdotool key --window $(xdotool search --name 'QQ' | head -n1) ctrl+alt+z"

把"QQ"换成对应的进程名字。 另外手动在shell中执行"$(xdotool search --name 'QQ' | head -n1)"验证是否能找到进程。

zhuozl:~$ xdotool search --name 'QQ' | head -n1

90177555

可以找到 但是还是不生效。

```

Wine安装的程序，全局快捷键只在wine程序有焦点时可以使用。 安装xdotool和xbindkeys，前者负责将按键转发给指定的应用程序窗口，后者负责将按键绑定至指定的Shell命令。 编辑配置文件：

xbindkeys --defaults > /root/.xbindkeysrc
vi ~/.xbindkeysrc

输入(QQ换成对应的进程名)：

 "xdotool key --window $(xdotool search --name 'QQ' | head -n1) ctrl+alt+z"
 Control+Alt + z

这样就把Control+Alt + z快捷键绑定到了上面的命令，然后通过xdotool 搜索窗口，传递按键 xdotool 可以搜索窗口、聚焦窗口、模拟击键、模拟鼠标点击

# Examples of commands:

"xbindkeys_show"
  control+shift + q

"xdotool key --window $(xdotool search --name 'QQ' | head -n1) ctrl+alt+z"
  Control+Alt + z


# set directly keycode (here control + f with my keyboard)
#"xterm"
#  c:41 + m:0x4

# specify a mouse button
#"xterm"
#  control + b:2

设置了无效

+1

👋 hey , I come about on this error Number of distinct destination bucket ARNs cannot exceed 1 , and while I set priority to all rules I kept getting this error even on latest version of the provider (3.21).

The problem was that I was not specifying filter {} as I don't have any filters at all. The moment I specified this it worked, even as an empty object. Not sure what will be the best behavior here but just in case anyone else has the same problem.

Maybe we can update the docs?

I also have been trying to figure out a way to remove that error, but have been unsuccessful. The only way that I have been able to suppress the error is by casting this to type any. This just feels wrong and removes a lot of the benefits of using Typescript in the first place.

 ts
({
  computed: {
    ...mapGetters('ChartModule', {
      charts: 'getCharts'
    })
  }
})
export default class ChartCompoment extends Vue {
   created() {
     console.log((this as any).charts)
   }
}

The other option that I have considered is using ,, etc. decorators in the component, but that requires one decorator for each mapped function. This looks clunky and is far less readable when you start to have many of these decorators in one component.

Conclusion: I just want to be able to reference map[Getters/Mutations/State] in a class component using this.

I think it's okay.

It's cool that some of my arrangement bugs are fixed. And I would like to give some tips. The font used in the original logo is "Neutra Text Bold", which is also used in logo.js as I know. It is used with the default optical kerning option in Photoshop and with increased spacing. And I think that it really asked for some custom grid arrangement. The colors at first stage are meant to be picked from the original logo.js SVG, but now it doesn't seem necessary. And also there is an idea of inverted "dark" version of logo.

The thing I disagree with is the dashes. You see, the first version of logo was made with the original "Neutra Text" dashes, which are pretty short by design. So the font itself is meant to have short dashes. It is designed that way. I reconstructed the proportions of the dashes and made the arrow so they are connected in the way shown on this schemes plus a little visual tuning.

please do a new npm release to include https://github.com/react-native-community/react-native-svg/commit/be8797be5239085d5d09eec90a926ae8da7a8583, thank you :)

How's game performance ? Do you notice any slowdown?