text:
Creeping Amnesia

The work that I did yesterday and today seems to have disappeared.  A few minutes ago today's work was visible but it seems to have gone away ... sort of... If I look at revisions for a tiddler I edited today, there's a revision entry for it.  I did edit the ViewTemplate and the EditTemplate to add a custom field.  Could that have made the trouble?  Those edits are gone too.../b

And now everything is back...should I close this?

Thanks for the nicely complete answer. Some more questions:

When you create a lot of similar tiddlers, like the psalms, you doing "new tiddler" -> edit -> done, or some other process (perhaps importing)?
Do you do some of your editing offline and then sync back to the server?
According to the logs it appears that you may have renamed (or caused to be engaged the renaming process) about 61 different tiddlers. Do you know what that might have been?

The psalm tiddlers were created by me some days ago.  I used
store.saveTiddler() within Eric Shulman's SplitTiddler as edited by me.
The edits were done to include config.defaultCustomFields so that the
created tiddlers actually got saved.
I wound up renaming each of the psalm tiddlers so they had titles a bit
more meaningful than "Psalm ###".  For each psalm I also added a custom
field, "ordering", so I could sort them within collections based on
their tags.
I'm not sure that this is the issue since (it seems to me) that my edits
of ViewTemplate and EditTemplate went wandering off for a while as well.
All the editing was done online.
Again, thanks for the follow-up. You guys have been wonderfully
responsive.  /b
On 2/8/2012 9:00 AM, Chris Dent wrote:

Thanks for the nicely complete answer. Some more questions:

When you create a lot of similar tiddlers, like the psalms, you doing "new tiddler" ->  edit ->  done, or some other process (perhaps importing)?
Do you do some of your editing offline and then sync back to the server?
According to the logs it appears that you may have renamed (or caused to be engaged the renaming process) about 61 different tiddlers. Do you know what that might have been?

Reply to this email directly or view it on GitHub:
https://github.com/TiddlySpace/tiddlyspace/issues/911#issuecomment-3871202

Hi folks, just a hint.
I do know a FireFox Browser Cash problem. It can be reproduced like this:
(lateste test with: ubuntu 11.10 FF 9)
* open a TiddlySapce TW
* Pin the tab as an app
* create a tiddler and save it
* close the browser application
* open the browser application again
* new / renamed tiddler is gone
* shift-reload the page -> tiddlers are there.

Seems to be a FF only browser problem. It works with Chrome.
@brucedelagi
I did face this problem with earlier FF versions too but I didn't pay attention. The important thing is step "close browser", "open browser"

hmmm could be..I don't remember doing this but certainly
possible...Thanks Mario..../b
On 2/8/2012 2:56 PM, Mario Pietsch wrote:

Hi folks, just a hint.
I do know a FireFox Browser Cash problem. It can be reproduced like this:
(lateste test with: ubuntu 11.10 FF 9)
 * open a TiddlySapce TW
 * Pin the tab as an app
 * create a tiddler and save it
 * close the browser application
 * open the browser application again
 * new / renamed tiddler is gone
 * shift-reload the page ->  tiddlers are there.

Seems to be a FF only browser problem. It works with Chrome.
@brucedelagi
I did face this problem with earlier FF versions too but I didn't pay attention. The important thing is step "close browser", "open browser"

Reply to this email directly or view it on GitHub:
https://github.com/TiddlySpace/tiddlyspace/issues/911#issuecomment-3878227

TiddlySpace does use some fairly aggressive techniques to try to get the browser to always use a version in its local cache if possible. However, this is designed such that the local cache is always validated against the server.
Unfortunately, experience has shown that the browsers are not always doing this, usually in weird situations:

when repainting the screen after a back button
when reestablishing a persistent tab

This is more than a little unfortunate as in order for TiddlySpace to be friendly in the face of these kinds of problems it would need to cache much less and that would ruin performance.
Therefore the best thing to do when you think you are missing some tiddlers is to do a force reload to make sure the cache is being validated.
Bruce, if you keep seeing this sort of thing, and it is happening even after reloads and cache clearings, then reopen the ticket, but for now I think we ought to close it.
Thanks to both of you for the input.

OK Chris, thanks. I'll close the ticket.....and I was wondering to what
degree the local storage stuff in HTML5 is useful (and actually
operational).../b
On 2/9/2012 5:38 AM, Chris Dent wrote:

TiddlySpace does use some fairly aggressive techniques to try to get the browser to always use a version in its local cache if possible. However, this is designed such that the local cache is always validated against the server.
Unfortunately, experience has shown that the browsers are not always doing this, usually in weird situations:

when repainting the screen after a back button
when reestablishing a persistent tab

This is more than a little unfortunate as in order for TiddlySpace to be friendly in the face of these kinds of problems it would need to cache much less and that would ruin performance.
Therefore the best thing to do when you think you are missing some tiddlers is to do a force reload to make sure the cache is being validated.
Bruce, if you keep seeing this sort of thing, and it is happening even after reloads and cache clearings, then reopen the ticket, but for now I think we ought to close it.
Thanks to both of you for the input.

Reply to this email directly or view it on GitHub:
https://github.com/TiddlySpace/tiddlyspace/issues/911#issuecomment-3887396

At the moment TiddlySpace only uses LocalStorage in takenote, which you can access at /takenote
TiddlyWiki itself doesn't yet use LocalStorage

authors: brucedelagi cdent pmario

repo: TiddlySpace/tiddlyspace


text:
feat: [sc-36593] Implement Load Enumerations Request

Story details: https://app.shortcut.com/tiledb-inc/story/36593

We are missing the enumerationName optional property from the Attribute type. Other than that LGTM.

source: gharchive/pull-request

authors: SarantopoulosKon XanthosXanthopoulos

repo: TileDB-Inc/TileDB-Cloud-JS

license: MIT

license_type: permissive

license_source: github-api


text:
Add for each block

Today is not possible to get a response from a webrequest and make multiple replies.
Add a way to reply with text/media from an array.
As an example: https://www.youtube.com/watch?v=HFqGAjiNoCY

Hi Robert, thank you for your feedback. I added your request to our Feedback Board: https://tiledesk.sleekplan.app/feedback/108107
You should see it soon on our Public Roadmap too! ;-)

source: gharchive/issue

authors: MicheleTiledesk robertveloso

repo: Tiledesk/design-studio


text:
Ошибка при запуске скрипта ТГ-бота

Чего-то конкретно не нравится товарищу. Всячески пытался разобраться, методом исключения. Я не исключаю вариант, что мне не хватает опыта ))

@Tox1cP1g Здравствуйте! Можете указать, как вы запускаете свой пример? На скриншоте не видно.
Желательно полностью следовать инструкции, большинство проблем запуска там решены.
А также можете сказать, какая версия tksbrokerapi библиотеки установлена в тот питон, из-под которого вы запускаете пример бота по поиску аномалий? Попробуйте  переустановить. 6-й релиз библиотеки еще находится в разработке, поэтому нужно использовать фича-сборки. Тинькофф Инвестиции очень часто меняют без предупреждения своё http-api, поэтому было много ошибок с типами данных в старых версиях.
Я сейчас проверил пример на tksbrokerapi==1.6.dev155, всё отработало, как написано в инструкции.

@Tox1cP1g Здравствуйте! Можете указать, как вы запускаете свой пример? На скриншоте не видно. Желательно полностью следовать инструкции, большинство проблем запуска там решены.
А также можете сказать, какая версия tksbrokerapi библиотеки установлена в тот питон, из-под которого вы запускаете пример бота по поиску аномалий? Попробуйте переустановить. 6-й релиз библиотеки еще находится в разработке, поэтому нужно использовать фича-сборки. Тинькофф Инвестиции очень часто меняют без предупреждения своё http-api, поэтому было много ошибок с типами данных в старых версиях.
Я сейчас проверил пример на tksbrokerapi==1.6.dev155, всё отработало, как написано в инструкции. Скорее всего у вас был баг #128 из старой версии, который пофикшен.

Обязательно проверю, спасибо огромное


text:
Cannot sign commits with terminal pinentry programs

When I try to sign a commit with pinentry-tty as pinentry-program I cannot enter my passphrase and the pinentry text looks like this:

I believe this issue is related with #82 implementation wise.

authors: LeonGr TimUntersberger

repo: TimUntersberger/neogit


text:
Minor Nuisance

The "are you sure" window when you delete a macro always seems to pop under the main window. It'd be nice if it popped open on top. Very minor, I just move the main window out of the way.

This pops up on top for me but will only go under if I click on the underneath window.
TimothyLuke

On 7 Feb 2017, at 12:21 pm, npmilligan notifications@github.com wrote:
The "are you sure" window when you delete a macro always seems to pop under the main window. It'd be nice if it popped open on top. Very minor, I just move the main window out of the way.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

authors: TimothyLuke npmilligan

repo: TimothyLuke/GnomeSequencer-Enhanced


text:
The vehicle rotating on same spot Nigel

When i am running the main run file like
bash run_nigel.sh
python3 example_nigel.py
when i connected to autonomous the vehicle is rotating on same spot
How i can fix is iam missing anything
please help me

Hi @STEEVEPP,
That is the intended/expected behavior.
Essentially, example_nigel.py is meant to be a starting point prototyping template. The script initializes the necessary objects and assigns values of 1 to the throttle_command and steering_command for the vehicle. This makes the vehicle steer to the extreme left and drive forward with full throttle possible. Please refer to the comments to understand the code structure and workflow better. Once it is clear, you can implement the perception, planning and control logic yourself as per your problem statement and have fun experimenting with the different parameters associated and see their effect on vehicle performance.
Hope this helps and all the best!

authors: STEEVEPP Tinker-Twins

repo: Tinker-Twins/AutoDRIVE


text:
Update scalafmt-core to 3.7.4

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.7.3 to 3.7.4
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:n:3

Superseded by #45.


text:
DevOverlayの表示条件がおかしい

駅と位置情報がなくても表示だけはされるべきじゃないだろうか

そんなことなさそう

そんなことなさそう

repo: TinyKitten/TrainLCD


text:
About the Vision Tower.

Hello, Where can I find the pretrained vision tower, the original one seems to have been fine-tuned? Such as SigLip, CLIP

Our vision towers are loaded from huggingface, which are pretrained ones, not finetuned ones

authors: Sootung YingHuTsing


text:
make Group as sub-classes of Chatroom and Create new class Contact sub-class of Chatroom

There are two types of Chatrooms

Group
Contact

Collect all common functions inside class Chatroom

Fixed in https://github.com/Tithibots/tithiwa/commit/7d5c035946c73cc30c022c0afa02e995762f73b4

repo: Tithibots/tithiwa


text:
Demo project setup fails with Django-2.0

Setting up the demo project as described in the docs works perfectly fine with Django-1.11 but it fails with Django-2.0.
>>>python manage.py migrate --settings=demo.settings --noinput
Traceback (most recent call last):
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/rest_framework/compat.py", line 27, in <module>
    from django.urls import (
ImportError: cannot import name 'RegexURLPattern'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/management/__init__.py", line 371, in execute_from_command_line
    utility.execute()
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/management/__init__.py", line 365, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/management/base.py", line 332, in execute
    self.check()
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/management/base.py", line 364, in check
    include_deployment_checks=include_deployment_checks,
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 58, in _run_checks
    issues.extend(super()._run_checks(**kwargs))
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/management/base.py", line 351, in _run_checks
    return checks.run_checks(**kwargs)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/checks/registry.py", line 73, in run_checks
    new_errors = check(app_configs=app_configs)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/checks/urls.py", line 40, in check_url_namespaces_unique
    all_namespaces = _load_all_namespaces(resolver)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/core/checks/urls.py", line 57, in _load_all_namespaces
    url_patterns = getattr(resolver, 'url_patterns', [])
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/utils/functional.py", line 36, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/urls/resolvers.py", line 536, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/utils/functional.py", line 36, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/django/urls/resolvers.py", line 529, in urlconf_module
    return import_module(self.urlconf_name)
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/importlib/__init__.py", line 109, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 2254, in _gcd_import
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1129, in _exec
  File "<frozen importlib._bootstrap>", line 1471, in exec_module
  File "<frozen importlib._bootstrap>", line 321, in _call_with_frames_removed
  File "/tmp/django-rest-auth/demo/demo/urls.py", line 5, in <module>
    from rest_framework_swagger.views import get_swagger_view
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/rest_framework_swagger/views.py", line 1, in <module>
    from rest_framework import exceptions
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/rest_framework/exceptions.py", line 17, in <module>
    from rest_framework.utils.serializer_helpers import ReturnDict, ReturnList
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/rest_framework/utils/serializer_helpers.py", line 8, in <module>
    from rest_framework.compat import unicode_to_repr
  File "/tmp/django-rest-auth/demo/env/lib/python3.4/site-packages/rest_framework/compat.py", line 31, in <module>
    from django.core.urlresolvers import (  # Will be removed in Django 2.0
ImportError: No module named 'django.core.urlresolvers'

Hi @mr-kojo the error is being thrown in Django REST Framework - upgrading djangorestframework to 3.7.0 will fix it.
We will update requirements.txt in demo project.

authors: maxim-kht mr-kojo

repo: Tivix/django-rest-auth

license: mit

license_source: bigquery


text:
关于生命周期方法，onResume, onPause 相关的问题

有这么一个需求：
一个视频播放 APP，第一个页面播放视频，这个页面也存在跳转到其它页面去播放另一个视频，我目前可以用 precompose 中提供的 LocalLifecycleOwner.current 做到暂停和恢复，监听生命周期的代码如下：
@Composable
fun LifecycleEffect(
    onStart: (() -> Unit)? = null,
    onResume: (() -> Unit)? = null,
    onPause: (() -> Unit)? = null,
    onDestroy: (() -> Unit)? = null,
) {
    val lifecycleOwner = LocalLifecycleOwner.current
    DisposableEffect(lifecycleOwner) {
        val observer = object : LifecycleObserver {
            override fun onStateChanged(state: Lifecycle.State) {
                when (state) {
                    Lifecycle.State.Active -> onResume?.invoke()
                    Lifecycle.State.InActive -> onPause?.invoke()
                    Lifecycle.State.Destroyed -> onDestroy?.invoke()
                    Lifecycle.State.Initialized -> onStart?.invoke()
                    else -> {}
                }
            }
        }
        lifecycleOwner.lifecycle.addObserver(observer)
        onDispose {
            onDestroy?.invoke()
            lifecycleOwner.lifecycle.removeObserver(observer)
        }
    }
}

我在 onDestroy 中释放播放器，这样会导致一个问题，当我从当前播放页跳转到下一个播放页时，会触发 onDestroy，当我再返回这个播放页时，videoView 已经被释放了，无法继续播放。
目前我暂时的解决方法是onDestroy 中不释放，只暂停播放，然后在当前页面调用 navigator.goBack() 时，释放当前这个页面的播放器，目前回到上一个播放页面时可以继续播放。
可否新增一个生命周期 Stop，当导航到下一个页面时，触发 stop，不触发 destroy，只有在 goBack 时，才触发 destroy？
或者，目前我的临时解决方案，有什么更优的实现方式吗？

和PreCompose生命周期无关，请删除这一行：
@Composable
fun LifecycleEffect(
    onStart: (() -> Unit)? = null,
    onResume: (() -> Unit)? = null,
    onPause: (() -> Unit)? = null,
    onDestroy: (() -> Unit)? = null,
) {
    val lifecycleOwner = LocalLifecycleOwner.current
    DisposableEffect(lifecycleOwner) {
        val observer = object : LifecycleObserver {
            override fun onStateChanged(state: Lifecycle.State) {
                when (state) {
                    Lifecycle.State.Active -> onResume?.invoke()
                    Lifecycle.State.InActive -> onPause?.invoke()
                    Lifecycle.State.Destroyed -> onDestroy?.invoke()
                    Lifecycle.State.Initialized -> onStart?.invoke()
                    else -> {}
                }
            }
        }
        lifecycleOwner.lifecycle.addObserver(observer)
        onDispose {
-            onDestroy?.invoke()
            lifecycleOwner.lifecycle.removeObserver(observer)
        }
    }
}

有关DisposableEffect中onDispose的调用时机问题，可以参考官方文档
https://developer.android.com/jetpack/compose/side-effects#disposableeffect

我将代码改成这样子了：
@Composable
fun LifecycleEffect(
    onStart: (() -> Unit)? = null,
    onResume: (() -> Unit)? = null,
    onPause: (() -> Unit)? = null,
    onDestroy: (() -> Unit)? = null,
) {
    val lifecycleOwner = LocalLifecycleOwner.current
    DisposableEffect(lifecycleOwner) {
        val observer = object : LifecycleObserver {
            override fun onStateChanged(state: Lifecycle.State) {
                when (state) {
                    Lifecycle.State.Active -> onResume?.invoke()
                    Lifecycle.State.InActive -> onPause?.invoke()
                    Lifecycle.State.Destroyed -> {
                        onDestroy?.invoke()
//                        lifecycleOwner.lifecycle.removeObserver(this)
                    }
                    Lifecycle.State.Initialized -> onStart?.invoke()
                    else -> {}
                }
            }
        }
        lifecycleOwner.lifecycle.addObserver(observer)
        onDispose {
            lifecycleOwner.lifecycle.removeObserver(observer)
        }
    }
}

但是，新的问题是，不会触发 Destroyed 了，似乎onDispose更快执行，导致监听被取消了。

这是预期行为，scene 1 ->  scene 2的时候是不会触发Lifecycle的Destroyed，只有当从scene 2返回时，会在scene 2位置触发Lifecycle的Destroyed

针对这一个场景，你可以换一个思路，保存播放位置，这样即使被destroy也不需要关心了

不，我想表达的意思是，某些生命周期在一些常见的情况下不会触发，例如如下写法：
@Composable
fun LifecycleEffect(
    onStart: (() -> Unit)? = null,
    onResume: (() -> Unit)? = null,
    onPause: (() -> Unit)? = null,
    onDestroy: (() -> Unit)? = null,
) {
    // Safely update the current lambdas when a new one is provided
    val currentOnStart by rememberUpdatedState(onStart)
    val currentOnResume by rememberUpdatedState(onResume)
    val currentOnPause by rememberUpdatedState(onPause)
    val currentOnDestroy by rememberUpdatedState(onDestroy)
    val lifecycleOwner = LocalLifecycleOwner.current
    DisposableEffect(lifecycleOwner) {
        val observer = object : LifecycleObserver {
            override fun onStateChanged(state: Lifecycle.State) {
                when (state) {
                    Lifecycle.State.Active -> currentOnResume?.invoke()
                    Lifecycle.State.InActive -> {
                        currentOnPause?.invoke()
//                        lifecycleOwner.lifecycle.removeObserver(this)
                    }
                    Lifecycle.State.Destroyed -> {
                        currentOnDestroy?.invoke()
//                        lifecycleOwner.lifecycle.removeObserver(this)
                    }
                    Lifecycle.State.Initialized -> currentOnStart?.invoke()
                    else -> {}
                }
            }
        }
        lifecycleOwner.lifecycle.addObserver(observer)
        onDispose {
            lifecycleOwner.lifecycle.removeObserver(observer)
        }
    }
}

当我从scene 1 -> scene 2时，没有触发 scene 1 的InActive，当我从 scene 2 返回 scene 1 时，没有触发 scene 2 的InActive 以及 Destroyed

针对这一个场景，你可以换一个思路，保存播放位置，这样即使被destroy也不需要关心了

我觉得还是需要想办法保留 videoView 的整个状态，如果只保留一个播放位置，那么就需要重新缓冲了（目前我碰到的情况就是这样的）。

LifecycleEffect: 恢复 来自 Lifecycle.State.Active 回调

当我从scene 1 -> scene 2时，没有触发 scene 1 的InActive，当我从 scene 2 返回 scene 1 时，没有触发 scene 2 的InActive 以及 Destroyed
这确实是个bug，我已经在着手修复了
我觉得还是需要想办法保留 videoView 的整个状态，如果只保留一个播放位置，那么就需要重新缓冲了（目前我碰到的情况就是这样的）。
个人角度不是很推荐这样做，相当于虽然页面不可见，但是整个view仍然保留在内存中，可能会导致别的性能问题。对于重新缓冲问题，可以尝试添加缓存。

其实主要问题就在于，DisposableEffect 中监听lifecycle 时，onDispose 会比 InActive 和Destroyed 触发的更早，所以，这似乎是一个 bug
@Composable
fun LifecycleEffect(
    lifecycleOwner: LifecycleOwner = LocalLifecycleOwner.current,
    onStart: (() -> Unit)? = null,
    onResume: (() -> Unit)? = null,
    onPause: (() -> Unit)? = null,
    onDestroy: (() -> Unit)? = null,
) {
    // Safely update the current lambdas when a new one is provided
    val currentOnStart by rememberUpdatedState(onStart)
    val currentOnResume by rememberUpdatedState(onResume)
    val currentOnPause by rememberUpdatedState(onPause)
    val currentOnDestroy by rememberUpdatedState(onDestroy)
    DisposableEffect(lifecycleOwner) {
        val observer = object : LifecycleObserver {
            override fun onStateChanged(state: Lifecycle.State) {
                when (state) {
                    Lifecycle.State.Active -> {
                        logD("LifecycleEffect: Active")
                        currentOnResume?.invoke()
                    }
                    Lifecycle.State.InActive -> {
                        logD("LifecycleEffect: InActive")
                        currentOnPause?.invoke()
                    }
                    Lifecycle.State.Destroyed -> {
                        logD("LifecycleEffect: Destroyed")
                        currentOnDestroy?.invoke()
                    }
                    Lifecycle.State.Initialized -> {
                        logD("LifecycleEffect: Initialized")
                        currentOnStart?.invoke()
                    }
                    else -> {}
                }
            }
        }
        logD("LifecycleEffect: addObserver")
        lifecycleOwner.lifecycle.addObserver(observer)
        onDispose {
            logD("LifecycleEffect: removeObserver")
            lifecycleOwner.lifecycle.removeObserver(observer)
        }
    }
}

当我进入 Scene 2 ，随后返回 Scene 1 时，Log 是这么打印的（我只在 Scene 2 监听了）：

当我从scene 1 -> scene 2时，没有触发 scene 1 的InActive，当我从 scene 2 返回 scene 1 时，没有触发 scene 2 的InActive 以及 Destroyed

这确实是个bug，我已经在着手修复了

我觉得还是需要想办法保留 videoView 的整个状态，如果只保留一个播放位置，那么就需要重新缓冲了（目前我碰到的情况就是这样的）。

个人角度不是很推荐这样做，相当于虽然页面不可见，但是整个view仍然保留在内存中，可能会导致别的性能问题。对于重新缓冲问题，可以尝试添加缓存。

感谢建议。我会尝试下只保留进度。

似乎一直没有触发过Initialized，这个状态是无效的吗？

我想，这个 功能 如果能有一份详细的 使用帮助就好了

似乎一直没有触发过Initialized，这个状态是无效的吗？
#244 会修复这个问题

authors: Matcha-xiaobin Tlaster

repo: Tlaster/PreCompose


text:
ModuleNotFoundError: No module named 'fiona.errors'

Expected behavior and actual behavior.
When packaging new version of Fiona for openSUSE, the package tests fail with a rather large crash:
[  115s] + PYTHONPATH=/home/abuild/rpmbuild/BUILDROOT/python-Fiona-1.9.1-lp154.20.1.x86_64/usr/lib64/python3.6/site-packages
[  115s] + PYTHONDONTWRITEBYTECODE=1
[  115s] + pytest-3.6 --ignore=_build.python3 -v -rs -k 'not (wheel or test_open_zip_https or test_open_http or test_collection_http or test_collection_zip_http or GPSTrackMaker or (test_no_append_driver_cannot_append and (FlatGeobuf or GeoJSONSeq)))'
[  115s] ImportError while loading conftest '/home/abuild/rpmbuild/BUILD/Fiona-1.9.1/tests/conftest.py'.
[  115s] tests/conftest.py:14: in <module>
[  115s]     from fiona.crs import CRS
[  115s] fiona/_env.pxd:9: in init fiona.crs
[  115s]     ???
[  115s] fiona/_env.pyx:20: in init fiona._env
[  115s]     ???
[  115s] E   ModuleNotFoundError: No module named 'fiona.errors'

Complete build log showing all packages used and steps taken to reproduce the issue.
Also, for the information:
abuild@stitny:~/rpmbuild/BUILDROOT/python-Fiona-1.9.1-0.x86_64> find usr/lib64/
usr/lib64/
usr/lib64/python3.6
usr/lib64/python3.6/site-packages
usr/lib64/python3.6/site-packages/fiona
usr/lib64/python3.6/site-packages/fiona/_env.cpython-36m-x86_64-linux-gnu.so
usr/lib64/python3.6/site-packages/fiona/_err.cpython-36m-x86_64-linux-gnu.so
usr/lib64/python3.6/site-packages/fiona/_geometry.cpython-36m-x86_64-linux-gnu.so
usr/lib64/python3.6/site-packages/fiona/_transform.cpython-36m-x86_64-linux-gnu.so
usr/lib64/python3.6/site-packages/fiona/crs.cpython-36m-x86_64-linux-gnu.so
usr/lib64/python3.6/site-packages/fiona/ogrext.cpython-36m-x86_64-linux-gnu.so
usr/lib64/python3.6/site-packages/fiona/schema.cpython-36m-x86_64-linux-gnu.so
usr/lib64/python3.6/site-packages/Fiona-0.0.0.dist-info
usr/lib64/python3.6/site-packages/Fiona-0.0.0.dist-info/LICENSE.txt
usr/lib64/python3.6/site-packages/Fiona-0.0.0.dist-info/METADATA
usr/lib64/python3.6/site-packages/Fiona-0.0.0.dist-info/WHEEL
usr/lib64/python3.6/site-packages/Fiona-0.0.0.dist-info/top_level.txt
usr/lib64/python3.6/site-packages/Fiona-0.0.0.dist-info/INSTALLER
usr/lib64/python3.6/site-packages/Fiona-0.0.0.dist-info/RECORD
abuild@stitny:~/rpmbuild/BUILDROOT/python-Fiona-1.9.1-0.x86_64>

The test suite passes without a problem on more modern distros (with Python 3.8, 3.9, 3.10, and 3.11).
build log from Tumbleweed (current rolling distro)
However, I thought that Python 3.6 is still supported, isn’t it?
Steps to reproduce the problem.
See above, just run the test-suite.
Operating system
For example: openSUSE/Leap 15.4
Fiona and GDAL version and provenance
For example: FIONA, the 1.9.1 tarball from PyPI, building from scratch
GDAL 3.4.1 from openSUSE Leap 15.4 packages.

Fiona 1.9 dropped support for Python 3.6 (which reached end-of-life https://www.python.org/downloads/release/python-360/).

Pity. Thank you for the information.

authors: mcepl rbuffat

repo: Toblerity/Fiona


text:
Arrow not shooting from bow and crossbow

When trying to shoot an arrow from a bow or crossbow, no arrow shoots or gets used.
This happens when registering either CombatFeatures.modernVanilla() or CombatFeatures.VANILLA_PROJECTILE_ITEM and CombatFeatures.VANILLA_BOW (or crossbow).

Are you sure you are using the latest Minestom version? This is a recently fixed bug in Minestom

I updated it to the latest commit, and it works now. Thank you!


text:
🛑 Sitio WEB Corporativo is down

In 31c4cbe, Sitio WEB Corporativo (https://www.aysa.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sitio WEB Corporativo is back up in 3ed57e7 after 12 minutes.


text:
made tests and demo deterministic

Made tests deterministic for simplicity.
Should be approved after #58 to ensure that everything gets merged into master

The issue is that not all methods are not static. Some require randomness. This need to be parsed to the class to allow for deterministic "randomness" for tests but proper pseudorandomness for execution. I think the alternative is to parse the randomness generator as an argument for the methods which require it, which might be better to do?

repo: TokenScript/attestation


text:
cucumber failures with puppet 4.0.0 / hiera 2.0.0

Multiple acceptance tests are failing with the Gemfile from the current master which allows puppet 4.0.0 / hiera 2.0.0.
[master] ~/github/hiera-eyaml $ git show-ref HEAD
54b62eff28d72cb8670df226e2a16b7562aa16fc refs/remotes/origin/HEAD
[master] ~/github/hiera-eyaml $ ruby --version
ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-linux]
[master] ~/github/hiera-eyaml $ git diff
[master] ~/github/hiera-eyaml $ bundle show puppet
/home/jhoblitt/github/hiera-eyaml/.bundle/gems/puppet-4.0.0
[master] ~/github/hiera-eyaml $ bundle show hiera
/home/jhoblitt/github/hiera-eyaml/.bundle/gems/hiera-2.0.0
[master] ~/github/hiera-eyaml $ bundle show cucumber
/home/jhoblitt/github/hiera-eyaml/.bundle/gems/cucumber-1.3.19

  Scenario: encrypt a password                                        # features/encrypts.feature:23
    When I run `./supply_password.sh eyaml encrypt -o string -p`      # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:93
      No such file or directory - ./supply_password.sh (Aruba::LaunchError)
      features/encrypts.feature:24:in `When I run `./supply_password.sh eyaml encrypt -o string -p`'
    Then the file "password.output" should match /ENC\[PKCS7,(.*?)\]/ # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351

  Scenario: verify puppet3 with hiera can use hiera-eyaml to decrypt data                             # features/puppet.feature:7
    When I run `rm -f /tmp/eyaml_puppettest.* 2>/dev/null`                                            # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:93
    When I run `puppet apply --confdir ./puppet --node_name_value localhost puppet/manifests/init.pp` # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:93
    Then the file "/tmp/eyaml_puppettest.1" should match /^good night$/                               # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351
      expected "rise and shine\n" to match /^good night$/
      Diff:
      @@ -1,2 +1,2 @@
      -/^good night$/
      +rise and shine
       (RSpec::Expectations::ExpectationNotMetError)
      features/puppet.feature:10:in `Then the file "/tmp/eyaml_puppettest.1" should match /^good night$/'
    Then the file "/tmp/eyaml_puppettest.2" should match /^and good luck$/                            # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351
    Then the file "/tmp/eyaml_puppettest.3" should match /^and good luck$/                            # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351
    Then the file "/tmp/eyaml_puppettest.4" should match /^and good luck$/                            # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351
    Then the file "/tmp/eyaml_puppettest.5" should match /^gangs of new york$/                        # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351

  Scenario: verify puppet3 and facter for correct hash merge with incorrect fact                                              # features/puppet.feature:17
    Given I set FACTER_fact to "not-existcity"                                                                                # features/support/puppet.rb:1
    When I run `rm -f /tmp/eyaml_puppettest.* 2>/dev/null`                                                                    # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:93
    When I run `puppet apply --confdir ./puppet-hiera-merge --node_name_value localhost puppet-hiera-merge/manifests/init.pp` # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:93
    Then the file "/tmp/eyaml_puppettest.1" should match /^good night$/                                                       # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351
      expected "rise and shine\n" to match /^good night$/
      Diff:
      @@ -1,2 +1,2 @@
      -/^good night$/
      +rise and shine
       (RSpec::Expectations::ExpectationNotMetError)
      features/puppet.feature:22:in `Then the file "/tmp/eyaml_puppettest.1" should match /^good night$/'
    Then the file "/tmp/eyaml_puppettest.2" should match /^great to see you$/                                                 # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351
    Then the file "/tmp/eyaml_puppettest.3" should match /good luck/                                                          # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351
    Then the file "/tmp/eyaml_puppettest.4" should match /"here": "we go again!"/                                             # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351
    Then the file "/tmp/eyaml_puppettest.5" should match /^gangs of new york\nis to the warriors$/                            # .bundle/gems/aruba-0.6.2/lib/aruba/cucumber.rb:351

Hi @jhoblitt, sorry for the (very) late reply!
There's some interesting stuff here, do you think this is a hiera-eyaml or a cucumber (aruba) incompatibility with puppet 4.0? The load error seems like it's a potentially normal issue, but eyaml returning the wrong decrypted values seems very strange!

Closing this as solved by #181.

authors: TomPoulton jhoblitt sihil

repo: TomPoulton/hiera-eyaml


text:
Respect configured AWS profile when calling boto3

Use a shared boto3.session.Session between pyathena and manual
boto3 calls. This fixes #120

How similar is this PR to #56 ?

Aah, I obviously don't know how to search. This PR is very similar, where it differs is that it shares one session with pyathena and that the bug is fixed for newly introduced usages of boto3. I can close this in favor of the old one if that is preferable and it is updated to cover the new places that boto3 is used.

#125 leverages this approach and introduces a global variable that holds the boto3_session that can be retrieve at any point in time via get_boto3_session(). Happy to decline that PR in favour of this one. As I mention #125, #56 has been lying around for quite some time (outdated version of the code) and #124 addresses the issue in only one instance of the adapter i.e. clean_up_table.

authors: cstruct owenprough-sift w0rks74710n

repo: Tomme/dbt-athena


text:
docs: add jekyll landing page

Describe your changes
Using jekyll (picked https://phlow.github.io/feeling-responsive which seems to be more maintained than https://mmistakes.github.io/minimal-mistakes)

[x] ~content~ (moved to #1579)

https://ccpi.ac.uk/cil/
Tomography-RALTeam/Website content

[x] fix logos (remove hardcoded /assets/img/)
[x] fix nav dropdowns prefixing {{site.basurl}} https://github.com/Phlow/feeling-responsive/pull/276
[x] ~auto-fix _config.yml:url~
[x] update colours
[x] update contributing documentation

[x] update docs/Makefile
[x] how to build locally: make -C docs dirhtml web-deps web serve
[x] how to check CI: GHA Art[ie]facts DocumentationHTML unzip into CIL subfolder before running http.server

[x] GHA DocumentationHTML: use /prnum_merge instead of /nightly
[x] add subpages
[x] ~add more "widgets"~ moved to #1579
[x] fix duplicate refs.bib entries

Describe any testing you have performed
Link relevant issues

part of #1579
follow-up to #1679

Checklist when you are ready to request a review

[x] I have performed a self-review of my code
[x] ~I have added docstrings in line with the guidance in the developer guide~
[x] ~I have implemented unit tests that cover any new or modified functionality~
[x] ~CHANGELOG.md has been updated with any functionality change~
[x] Request review from all relevant developers
[x] Change pull request label to 'Waiting for review'

Contribution Notes
Please read and adhere to the developer guide and local patterns and conventions.

[x] The content of this Pull Request (the Contribution) is intentionally submitted for inclusion in CIL (the Work) under the terms and conditions of the Apache-2.0 License.
[x] I confirm that the contribution does not violate any intellectual property rights of third parties

What is the best way for us to review this? Are there build instructions so we can view it, or could you set up a (short) meeting to show us it if you have it running locally?

Instructions for testing are included in the docs in this PR.
I ran this:

download & extract DocumentationHTML from the CI
python -m http.server (for now accessible at https://stfc.cdcl.ml)

If it is a quick fix, can this paragraph

have slightly bigger text, by default, and be the first thing on the page?

If it is a quick fix, can this paragraph have slightly bigger text, by default, and be the first thing on the page?

not a quick fix unfortunately, but added to #1579 :)

authors: MargaretDuff casperdcl gfardell

repo: TomographicImaging/CIL


text:
🛑 VTP.XYZ is down

In 6619f08, VTP.XYZ (https://vtp.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: VTP.XYZ is back up in e04d042.

repo: TomsProject/uptime


text:
🛑 CKCode is down

In 2ee2b9d, CKCode (https://www.ckbctc.com/) was down:

HTTP code: 502
Response time: 834 ms

Resolved: CKCode is back up in 1dc412f.


text:
What overhead is associated with re-creating instruments and effect nodes?

Currently, I'm sharing the the instrument and effect instances and just updating their parameters when necessary. However, sharing state this way breaks down for fast melodies where the effects should change in between notes that are faster than the callback lookahead time:
var instrument = new PolySynth(tone.FMSynth);
var reverbNode = new Tone.Reverb(0);
var volumeNode = new Tone.Volume(0);
instrument.chain(reverbNode, volumeNode, Tone.Destination);

function playChordStateful(time, chord, duration, volume, reverb) {
  volumeNode.volume.value = volume;
  reverbNode.reverb.value = reverb;
  instrument.triggerAttackRelease(chord, duration, time);
}

I'm now wondering whether I should create an instrument and effect instances for each individual chord that is played. It seems that this should work conceptually, although ToneJS is probably not meant to be used this way:
function playChordStateless(time, chord, duration, volume, reverb) {
  var instrument = new PolySynth(tone.FMSynth);
  var reverbNode = new Tone.Reverb(reverb);
  var volumeNode = new Tone.Volume(volume);
  instrument.chain(reverbNode, volumeNode, Tone.Destination);
  instrument.triggerAttackRelease(chord, duration, time);
}

Does this seem like a valid solution or would you expect performance problems due to either overhead of re-creating audio nodes or previous instances not being cleaned up automatically?

I would recommend that you reuse the instruments instead of recreating them in a callback. The startup overhead is going to depend on which synths and effects you are using. Reverb has an especially large startup overhead since it has to generate the impulse response.
Beyond the startup overhead, each synth and effect adds multiple audio processing nodes to the underlying audio context graph which will stick around unless you explicitly disconnect/dispose those nodes using .dispose().

Thanks for pointing our .dispose(). Do you have an idea how to solve the problem described above, i.e. timing exactly when effects should change? With the example above, the effects switch look ahead time too early, which affects notes that are being played before the one that should get the new effect setup. Thanks!

I would probably have both effects chains setup in parallel each with a gain in front of it. At the moment that you want the effects to change, set one gain to 0 and the other to 1 using setValueAtTime or rampTo.

Thanks for your input! Let's say there is a fast melody playing, where each note starts 0.01 seconds after the previous one. The default lookahead time in ToneJS is 0.1 seconds. The user may choose to change effects on every note. This means I would need at least 10 parallel effect chains to alternate between, e.g. in round-robin fashion.

Thanks again for your input! Searching for setValueAtTime in the docs did not return any results -- where can I learn more about it? Would this feature allow me to schedule changes to the effect parameters as well? In that case, there would be no need for duplicating the effect chain anymore.

authors: danijar tambien


text:
How wo broadcat part of cient?

Onlye broast part of client
For example client1 client2 client3 connect with server
At the side of server ,just send data to client1 ,client2 ,except cient3,I try somethiong,but not working

There is a function in WebSocketServer:
public void broadcast(byte[] data, Collection<WebSocket> clients)

This should do what you want. There are also versions for String and ByteBuffer instead of byte[]

authors: PhilipRoman yummyChina

repo: TooTallNate/Java-WebSocket


text:
Why  WebsocketClient.sendhandshake  use  uri.getQuery?

In sendHandshake() method, I see  uri.getQuery(),  why not use uri.getRawQuery().
uri.getQuery() invoke decode.   if  query of uri has encoded,  and Server always decode, there is problem.

I have try your way .But not working  and I got exception like RuntimeException: unknown scheme  https.I don't retract the issue.what is requirement for connecting https URL??

In my case,  scheme use ws://,    or  use wss://

@piyurabadiya     In my case, scheme use ws://, or use wss://

I also try this way but in my case not work and thrown exception MalformedURLException

I pass URI to WebsocketClient,   URI can accept ws scheme

Hello @37du  and @piyurabadiya
please use the following example when you call the constructor:
new URI("ws://example.org)"
Greetings
marci4


text:
Tmhmm support

adds support to show TmHmm predictions.
some linting
fix misspell

Haven't finished. Need to do:

When TMHMM is complete change the text correspondingly. Ex., http://localhost:4300/genomes/GCF_001315015.1 shows TMHMM status in green, but the text is: "TMHMM Predictions with TMHMM is not complete"
On the gene detail page the TM check box should be functional: check on - show TMs, check off - do not show.
Clicking on TM regions on the domains architecture image should highlight a corresponding sequence fragment.

authors: ToshkaDev daviortega

repo: ToshkaDev/mist-web-v


text:
Bug fix in CFeedFetcher where the respondsToSelector is checking for the

Bug fix in CFeedFetcher where the respondsToSelector is checking for the wrong method.
This fix allows the

(void)feedFetcher:(CFeedFetcher *)inFeedFetcher didFailFetchingFeed:(CFeed *)inFeed withError:(NSError *)inError delegate method to work properly again.

Thanks for the fix.

repo: TouchCode/TouchRSS


text:
Add "type: module" (was: Additional Options: UTC Dates + Skip emitting file data)

This PR adds several options, added via additional options parameters. Not sure if this is best way to add these, or if you would consider adding them, and definitely open to suggestions. Wanted to suggest PR so can avoid having a separate fork. The main purpose of this is to support a use case for creating an 'in-place' ZIP around data that already exists on IPFS.

The first option is utcDates, which forces using the Date.getUTC* functions. Yes, I saw the note re: DOS dates and default local timezone, but it would still be very helpful to have consistent, reproducible date setting, regardless of the time zone. This option allows for that.

The next option is skipEmitFileData, which may seem a bit strange. The use case is for generating ZIP file for data that is already stored elsewhere (in this case, in IPFS) and emitting only the blocks 'around' the data. In my use case, I use this to detect when the new file entry data starts: https://github.com/webrecorder/ipfs-composite-files/blob/store-ops/src/zip.js#L57 (There's probably more concise way of doing, such as emitting a custom id instead, but wanted to support this with minimal changes to client-zip). Of course, when this is set, the actual zip emitted is no longer valid, as the data is skipped. There's probably a way to support this outside of makeZip, but would require exposing new functions..

Also set type: module to allow the built index.js to be used with esm modules in node.

Definitely open to thoughts / suggestions for how it might be possible support this use case.

Hi Ilya.

If you want "consistent, reproducible date setting, regardless of the time zone", using UTC in the DOS date is not the way to go. Instead, you can implement the UNIX Extra Field (0x000d) specified in section 4.5.7 of the APPNOTE. Those date fields are regular UNIX timestamps and always interpreted as UTC (unlike the DOS date).

I'd like to understand your use case a bit more, but it sounds like client-zip could help if we find a smarter way to output the data. Maybe we could insert some symbols in the async iterable and return it directly instead of its Stream wrapper, so you don't have to rely on pattern matching binary data.

Sure.

If you can make a PR with 1 and 3, I could validate that quickly. The skipEmitFileData thing maybe needs more discussion.

If you want "consistent, reproducible date setting, regardless of the time zone", using UTC in the DOS date is not the way to go. Instead, you can implement the UNIX Extra Field (0x000d) specified in section 4.5.7 of the APPNOTE. Those date fields are regular UNIX timestamps and always interpreted as UTC (unlike the DOS date).

Well, don't actually care about the date value in the ZIP itself, the important part is for ZIP bytes stream to return a consistent stream bytes no matter where it is run, given the same input. But setting lastModified: new Date(0) will result in different bytes, based on the timezone, with how the Date class works. I don't see an easy way of doing that without using the getUTC* functions. Do you propose a different solution to address that?

I'd like to understand your use case a bit more, but it sounds like client-zip could help if we find a smarter way to output the data. Maybe we could insert some symbols in the async iterable and return it directly instead of its Stream wrapper, so you don't have to rely on pattern matching binary data.

Actually, yes, I've since had a case where I need the data, but needed to know where it stars, so a zero-length Uint8Array marker at beginning and end of file is a more flexible solution, can then detect these, but the stream is still valid ZIP data.
Can make a separate PR for that later.

I still don't see why you need that "consistent" DOS date in the byte stream. As I said, the correct way to store a date that doesn't depend on system timezone is the UNIX extra field. A DOS date based on UTC will be incorrect on any system that isn't itself set to UTC.
I was actually thinking of using Symbols as markers. You can't distinguish a zero-length buffer from another, but with symbols we can have multiple markers (for start of data, start of headers, etc.) and we insert different symbols in the iteration (and just skip them when converting to a binary stream for normal usage). We could also decorate the initial buffer of a section with a symbol-named property whose value indicates what it's about (and we could even expose structured metadata that way).

If you need the consistency for testing, just set the timezone to UTC when running the test, by prefixing your command line with TZ=UTC.

If you need the consistency for testing, just set the timezone to UTC when running the test, by prefixing your command line with TZ=UTC.

There are many reasons to want to have deterministic output, testing is definitely one of them. It's not always possible to change the system timezone, especially when running in the browser. I am considering using client-zip as part of a library that runs in the browser, where changing the timezone is not an option. (especially since not really using the date at all!)  Would you be opening to an option to just zero out the date field instead, so its always set to a fixed value?

There are many reasons to want to have deterministic output, testing is definitely one of them. It's not always possible to change the system timezone, especially when running in the browser. I am considering using client-zip as part of a library that runs in the browser, where changing the timezone is not an option. (especially since not really using the date at all!) Would you be opening to an option to just zero out the date field instead, so its always set to a fixed value?

Ok, I guess I can accomplish deterministic results just adding the offset manually, eg: lastModified: new Date(time + new Date().getTimezoneOffset() * 60000)

Yeah, adding the offset will cancel the effect of the system's timezone on the stored date. If you already know a file's modification time, I suppose that means you can predict its DOS timestamp fully. I'd still like to hear what reason you have for that beside testing.
Based on your project's README and what you said, I guess you're running client-zip on the server ? but then you said you'd like to run in the browser, and those timezone issues wouldn't make much sense on the back-end… are you going to access IPFS directly from the browser ?

Yeah, adding the offset will cancel the effect of the system's timezone on the stored date. If you already know a file's modification time, I suppose that means you can predict its DOS timestamp fully. I'd still like to hear what reason you have for that beside testing. Based on your project's README and what you said, I guess you're running client-zip on the server ? but then you said you'd like to run in the browser, and those timezone issues wouldn't make much sense on the back-end… are you going to access IPFS directly from the browser ?

Yes, that's just one usage, and eventually the hope is for ipfs-composite-files to also be used in the browser.
Also currently using client-zip in a browser extension.
I've updated the PR to remove utc dates and skipping, instead adding a 'before file start' marker and 'after file end' marker, which can be arbitrary objects, including symbols, that the user passes in.
Now using it like this:
https://github.com/webrecorder/ipfs-composite-files/blob/store-ops/src/zip.js#L48
and as part of a much more complex system, in the browser:
https://github.com/webrecorder/archiveweb.page/blob/ipfs-custom-splits/src/downloader.js#L259
I'm actually setting the before and after markers to the same object, so can be the same object / symbol for start and end, but made it two markers just in case, for flexibility.. (But could change it to one if you'd prefer)

I was actually thinking of using Symbols as markers. You can't distinguish a zero-length buffer from another, but with symbols we can have multiple markers (for start of data, start of headers, etc.) and we insert different symbols in the iteration (and just skip them when converting to a binary stream for normal usage). We could also decorate the initial buffer of a section with a symbol-named property whose value indicates what it's about (and we could even expose structured metadata that way).

I used zero-length Uint8Array as that's backwards compatible with regular streaming (can just be ignored if consuming bytes), but using === can check for the exact marker objects that are passed in. But happy to use a different approach as well!

Here's an example if what I was thinking with symbol decorations, in zip.ts :
export const zipSectionStart = Symbol()

export async function* fileData(file: ZipFileDescription) {
  // ...
  if (bytes instanceof Uint8Array) {
    bytes[zipSectionStart] = "data"
    yield bytes
  // ...
  } else {
  // ...
    let first = true
    while (true) {
  // ...
      if (first) value[zipSectionStart] = "data"
      first = false
      yield value!
    }
  }
}

You don't need to pass your own zero-length buffers to make that work, or to add empty buffers at all. Just import the symbol and look up the property named with it in each buffer. I didn't add "end" markers because they're a pain to set in a generator loop, but the solution is to always add a marker to the following section (that would be the data descriptor), so when you see a buffer with another marker, you know the previous ("data") section is ended.

Hm, I guess that could work, but seems like a bit more changes?
But, good news, I realized I could just wrap the generator on my end, and then no changes are needed!
async function* addMarkers(iter) {
  yield marker;
  yield *iter;
  yield marker;
}

So maybe just 3, type: module is all that's needed (in node, works already in the browser).
Sometimes the best code is no code at all...

Closing in favor of cleaner #56 as this is no longer needed.

authors: Touffy ikreymer

repo: Touffy/client-zip


text:
DiscordSRV  问题

使用 DiscordSRV 连结 Discord 在游戏打字  Discord 连结的频道没显示文字

在settings.yml中添加
Options:
  ChatEvent-Hooks: ['DiscordSRV']

authors: ItsFlicker MOMOas

repo: TrPlugins/TrChat


text:
HR not showing when connected to Garmin FR 255 (broadcasting)

The Android app is connected to the Garmin forerunner, which is broadcasting heart rate. When starting my Schwinn bike I can see actions coming from my bike, but heart rate stays empty.
Is there anything I should do to display HR (Source: Garmin watch) while on my Schwinn bike?

Which Schwinn bike do you have? Usually (depending on the model) they are capable of pairing the HRM and usually my app can receive the heart rate via the console. This way you'd see heart rate both on the console or in the app.
There's also a possibility to pair the HRM directly to the app. That can be done before the workout on the generic scan screen: you can click on the HRM row's play button icon and that'd pair it with the app. Then when you click on the bike's play button the heart rate should be visible.
The other possibility is IF the instant measurement start option is NOT enabled (it's enabled by default, this causes the app to automatically start the workout recording once the navigation completes to the workout recording screen), then you can click the heart icon in the menu and you can pair HRM. This can theoretically be done even during the workout.
Recently I have reports that the application has problems with Schwinn 170/270/570 (#433). I haven't had opportunity to debug that yet, and it can happen that you may discovered a new or related bug. In that case the app has an internal logging capability: under the expert preferences you can turn on the logging to INFO level and then export a log. (Then don't forget to turn off the logging).
It's another story if the HRM doesn't show up in the scans. The heart rate monitor should be Bluetooth Low Energy Heart Rate Profile compatible.

Any news on this?

DC Rainmaker's guide on Garmin Wearable Heart Rate Broadcasting: https://www.dcrainmaker.com/2020/04/quick-how-to-garmin-wearable-heart-rate-broadcasting-to-apps.html

For Wear OS see https://github.com/TrackMyIndoorWorkout/TrackMyIndoorWorkout/issues/457 https://play.google.com/store/apps/details?id=lukas.the.coder.heartforbluetooth

I close this with the premise that Wear OS or Garmin native watch app which can transmit heart rate via standard HRM profile BLE protocol.

authors: MrCsabaToth rjwonder


text:
Sometimes the Bluetooth protocol stack doesn't supply some BT device names

Every once in a while this happens. Back in the past we didn't even list machines without names. Later we introduced a workaround: in this case we just assume a string "Unnamed", see #410.
Last time this happened when I started to pair the app when everyone was hitting the Stage button on the Stages SC3 bikes. This is the time I think when all the console connect via ANT+ to the 3 NPE WASP / HÔRNET aggregators so Cyclebar would receive the workout data. ANT+ operates in the exact same 2.4 GHz range as Bluetooth or traditional WiFi. Probably that creates a ton of chatter (since the power meters already have to pair with the console (42 times), then an extra 42 ANT+. I suspect that this crowdedness might cause this lack of device name, this is a suspicion.
The end result is that it's hard to sort out which console is which. Normally the console is named after the bike ("Staged IC 021" for example). With a lot of them being Unnamed I'd be only be able to see the BT Address, once #439 is implemented. Without that the only way to find the right device is to connect and check if the numbers match up with the console.
Even seeing the Bluetooth Address might not help. The best would be to fetch the name from a possible earlier workout which had the device name. So before scan we could assemble a BT Address -> BT Device Name hashmap by requesting the activities (which are only in the range of a few hundred). Then if we encounter the unnamed scenario we could possibly replenish the name.

Will be available with the next release


text:
上下線で停車駅が違う種別と土日通過に対応する

Direction
0: Both(上り・下り)
1: Inbound(上り)
2: Outbound(下り)
Pass(NEW)
0: すべての曜日で停車する
1: すべての列車が通過する
2: 一部列車が通過する
3: 平日のみ停車する
4: 休日のみ停車する

下位互換性をもたせてあげないといけないので、パラメータで指定されない限りpassの2~4は0扱いにする

repo: TrainLCD/StationAPI


text:
Add test cases for Travis CI

Need test cases so that the backend will pass Sprint 2 rubric

Here are the rubric notes

Tests exist and run.
Test cover use cases expected.
Unit testing and/or scripts for backend.

Chris using Selenium for front end tests
Cecilia and Julienne using DjangoTest for backend tests

NPM and Selenium autotests delayed to Sprint 3, all other tests working as it on Travis


text:
🛑 MeVuelo Core API (production) is down

In 173d41c, MeVuelo Core API (production) (https://api.core.production.travelonux.com/status) was down:

HTTP code: 502
Response time: 621 ms

Resolved: MeVuelo Core API (production) is back up in f9f7f50 after 8 minutes.

repo: Travelonux/upptime


text:
Typescript compiler error for refs with tresjs

Describe the bug
I am using tresjs and would like to reference my newly loaded .glb  and a directional light.
I should say, the page actually functions as expected, however the red squiggly line appears in my local VSCode with an error, and so would like to nail it down if possible.
Final note: this typescript compiler error only occurs on my local VSCode system, as can be seen from the StackBlitz link below, it doesn't occur there.
So I'm not sure if this is even a bug, but I'd like to ask for help to remove the red squiggly line from my local system, thanks if possible.
Reproduction
https://stackblitz.com/edit/vitejs-vite-qn7w4v
Steps to reproduce
I've tried changing the type of ref to a few things, eg: <THREE.DirectionalLight>, however nothing seems to remove this error:
(property) ref?: ((Ref<THREE.DirectionalLight> | Readonly<Ref<THREE.DirectionalLight>>) & VNodeRef) | undefined
System Info
Here is my package.json for that project:

{
  "name": "tresjs_1",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "vue-tsc && vite build",
    "preview": "vite preview"
  },
  "dependencies": {
    "@tresjs/cientos": "^2.1.3",
    "@tresjs/core": "^2.1.2",

    "three": "^0.153.0",
    "three-stdlib": "^2.23.9",
    "vue": "^3.2.47"
  },
  "devDependencies": {

    "@types/three": "^0.152.1",
    "@vitejs/plugin-vue": "^4.1.0",
    "typescript": "^5.0.2",
    "vite": "^4.3.9",
    "vue-tsc": "^1.4.2"
  }
}

Used Package Manager
npm
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hey @alvarosabu,
Would like to take this issue if you let me.
Cheers.

@lausuarez02 sure thing, PR welcome 😊

repo: Tresjs/tres


text:
关于访问首页出现空白页面问题

访问首页发现是空白的情况，可以查看仓库根目录下，应该会有一个index.html文件
打开这个文件不出意外是空白的，静态文件生成了，但是没有内容。
hexo g --debug

会看到类似的报错信息
ERROR Script load failed: themes/obsidian/scripts/libs/cheerio/static.js
Error: Cannot find module 'css-what'
Require stack:
- /www/wwwroot/myblog/node_modules/css-select/lib/compile.js
- /www/wwwroot/myblog/node_modules/css-select/index.js
- /www/wwwroot/myblog/themes/obsidian/scripts/libs/cheerio/static.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
    at Function.Module._load (internal/modules/cjs/loader.js:842:27)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/www/wwwroot/myblog/node_modules/css-select/lib/compile.js:9:19)
    at Module._compile (internal/modules/cjs/loader.js:1138:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
    at Module.load (internal/modules/cjs/loader.js:986:32)
    at Function.Module._load (internal/modules/cjs/loader.js:879:14)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/www/wwwroot/myblog/node_modules/css-select/index.js:12:21)
    at Module._compile (internal/modules/cjs/loader.js:1138:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
    at Module.load (internal/modules/cjs/loader.js:986:32)
    at Function.Module._load (internal/modules/cjs/loader.js:879:14)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at require (/www/wwwroot/myblog/node_modules/hexo/lib/hexo/index.js:280:23)
    at /www/wwwroot/myblog/themes/obsidian/scripts/libs/cheerio/static.js:6:14
    at /www/wwwroot/myblog/node_modules/hexo/lib/hexo/index.js:293:14
    at tryCatcher (/www/wwwroot/myblog/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/www/wwwroot/myblog/node_modules/bluebird/js/release/promise.js:547:31)

简而言之，就是模块缺失，作者给出了package.json
所以解决办法：
cd themes/obsidian/
npm install

#40 这里也提到了此问题，手动安装一次就好了

我在说明文档中补充了这个步骤了。谢谢支持！

repo: TriDiamond/hexo-theme-obsidian


text:
docs: update readme

Summary
Updated README with new installation steps and feature list
Changes

new feature list remarks and rejection , new version explanation of sign and verfication

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: TrustVC/trustvc


text:
Examples for Object Detection

Is your feature request related to a problem? Please describe.
Hi, I notice that Robust DPatch is available in ART which is quite interesting, but the object detector is not implemented.
https://github.com/Trusted-AI/adversarial-robustness-toolbox/blob/main/art/attacks/evasion/dpatch_robust.py
https://github.com/Trusted-AI/adversarial-robustness-toolbox/blob/d351b3d33c266b436abbf13b9279f266a3dd3062/art/estimators/object_detection/object_detector.py#L39
I'm wondering will there be any examples of DPatch attacks against object detector.
Describe the solution you'd like
Perhaps a similar notebook such as the adversarial patch against a classifier.
https://github.com/Trusted-AI/adversarial-robustness-toolbox/blob/main/notebooks/adversarial_patch/attack_adversarial_patch.ipynb

Hi @wuhanstudio Thank you very much for using ART!
This module adversarial-robustness-toolbox/art/estimators/object_detection/object_detector.py only contains the abstract base class for object detectors. Two model-specific object detection estimators are currently available in art.estimators.object_detection: PyTorchFasterRCNN and TensorFlowFasterRCNN.
We have currently a get-started example script for RobustDPatch and PyTorchFasterRCNN in https://github.com/Trusted-AI/adversarial-robustness-toolbox/blob/main/examples/get_started_fasterrcnn.py

Thanks for your help. I'll check this out and hope there will be YOLO support in the future.

@wuhanstudio I agree, YOLO support would be great and it shouldn't be too difficult to implement. Let me know if you are interested to get start with an estimator for YOLO, we would be happy to help and provide support.

I have implemented several physical patch attacks against YOLO (Keras Model).
Perhaps I can add a file such as tensorflow_yolo.py after finishing my experiments soon.

I notice that ART imports models either from the official pytorch torchvision.models.detection.fasterrcnn_resnet50_fpn or the official tensorflow models.
Unfortunately, YOLO is not officially supported by none the two:

pytorch (https://pytorch.org/vision/stable/models.html)
tensorflow (https://github.com/tensorflow/models/tree/master/research/object_detection/models)

authors: beat-buesser wuhanstudio


text:
How can I disable the 'Subscription' feature

I don't intend to offer subscriptions, so I would like to make these 'SUBSCRIBE' buttons disappear everywhere.

Hey @paulosacramento,
The solution was already posted on our forum.
We ask that you please do not use GitHub for support or feature requests 😄. We use GitHub solely for bug-tracking and on-going feature development.
Our forum is a great place to get community support, plus it helps create a central location for searching problems/solutions.
Thanks!

authors: minimaluminium paulosacramento

repo: TryGhost/Casper


text:
Reorder account signup form

People were having trouble with automatically entering password verification in blog title field. This re-orders the form to a more "normal" flow where password field is the last item on the page, so no risk of double-typing it.
Closes https://github.com/TryGhost/Ghost/issues/8622 by inadvertent knock-on effect.

Coverage remained the same at 73.106% when pulling 281fd2f670548716ed8fef339ed88aef88238d73 on JohnONolan:reorder-signup into a0de451961172bc0edc1af8ad8d7acc16d443c09 on TryGhost:master.

authors: JohnONolan coveralls

repo: TryGhost/Ghost-Admin


text:
Trying to invite a user with the same email as the current user results in an incorrect validation

Issue Summary
Step 3 screen, attempting to invite using an existing email address (i.e. the one provided in Step 2) results in "Failed to send 1 invitation: . Please check your email configuration, see http://support.ghost.org/mail for instructions"
Looking in the server log shows an "Error: User is already registered", so that's not the issue here.
Steps to Reproduce

Setup blog with email address
Invite same email address
Invite completes and observe above error message in top alert

I believe this is a regression, and this was handled in the validation step before?
Technical details:

Ghost Version: master
Node Version: latest 4.x
Browser/OS: Chrome 52
Database: SQLite

@kevinansfield @kirrg001 wasn't sure if this is a blocker?

Not a blocker, pretty sure it's been like this for a while 😉

When I use the email address, I registered with, plus two (valid) more email addresses, I have the following situation:

The button in step 3 tells me, that I'm about to invite 2 users, although 3 emails are entered. But this is completely correct, as one of them is used already.
After hitting the invite button, I get the same error as @acburdine for the used email PLUS (and that's what I think, is wrong)
The error message tells me, that it failed to invite 2 users and lists the first (already used email) and the second one I entered, but when I check the network response, I can see, that the invite for the second user was successful.

Also, in my terminal, I got this message: Warning: Error sending email: Error: Message could not be sent More info: Mail from command failed - 550 5.7.1  Mail from IP 197.162.254.169 was rejected due to listing in Spamhaus PBL. For details please see http://www.spamhaus.org/query/bl?ip=197.162.254.169 Please check your email settings and resend the invitation.

This has been fixed in 1.0 😄

authors: AileenCGN ErisDS acburdine kevinansfield

repo: TryGhost/Ghost


text:
Only emit changed settings.

Closes #12038

[x] There's a clear use-case for this code change => It's not causing any problem. But it can later.
[x] Commit message has a short title & references relevant issues
[x] The build will pass (run yarn test and yarn lint)

More info can be found by clicking the "guidelines for contributing" link above.

Thank you @sainthkh :bow: :sun_with_face:

authors: allouis sainthkh


text:
Enable Node 4.2 testing

Do not error when node unsupported if engine-strict=false is set
Default engine-strict=true via .npmrc
Run engine check in preinstall script

issue #5821

Now we're on the right track :smile:
The great thing about this, is its totally future proof - we can add allowed failures for node 5.x and start keeping track of changes in advance.
I also really like the idea of using an env variable here, however I have a few concerns about using the npm engine strict config var:

the meaning/behaviour of engine-strict seems to keep changing, although if I'm understanding https://docs.npmjs.com/files/package.json#enginestrict correctly, then it was only the engineStrict option in package.json that was deprecated, the config flag/env var version is still active. Still, I'm not 100% how this will impact running npm install ghost and whether the behaviour in that case will be correct?

Do you know what versions of npm the config flag/env var version works for? The documentation is not versioned - I believe it is pretty much every version but it's a question worth considering.

I have a very strong aversion to adding dotfiles ... this is getting ridiculous (and code climate wants one too if we want to configure it properly):

If it is the case that using the engine-strict npm setting is the only way to ensure correct behaviour for running both npm install inside the ghost project and running npm install ghost, then I agree it makes sense to use it.
If however, the engine-strict npm setting does not result in additional 'good behaviour' for the npm install ghost case (or worse causes problems), then I'd propose having a ghost-specific config flag something like GHOST_NODE_VERSION_CHECK=false instead as that eradicates complications from npm and the .npmrc file.
As an additional note, I'm working on writing up some docs on Ghost & node version support which can be output in the error message here to give people loads of useful info including what versions have what level of support, why, and how to override it.

Ok, so setting engine-strict makes npm fail if it it can't satisfy engines. It does however only work for dependencies, not for the project that you're installing. What we're doing here is just checking it manually, there shouldn't be any side effects.
I found a mention of both the flag and environment variables in the 1.4 docs, I don't think we have to worry about that. :smile: But even if npm doesn't support it, the check will evaluate to false and it keeps installing. (This might actually be a bad thing, any errors in versionCheck are currently ignored).
npm doesn't really say if a value has been set manually. But if we really don't want another dotfile, we could just check the environment variable manually (but then we would miss other ways to set it, like ~/.npmrc and cli options).

there shouldn't be any side effects

Can you verify this please?

we could just check the environment variable manually

Surely this would require it to be set manually?
I guess my underlying question is "What is the tangible benefit of using npm's engine-strict over using a Ghost-specific env variable?"

I guess my underlying question is "What is the tangible benefit of using npm's engine-strict over using a Ghost-specific env variable?"

Let me be a bit more clear, we want engine-strict=true. It makes npm verify that all dependencies support the engine the user is running. The reason to also use it for our startup check is that you would only have to set a single env variable to override it. This is all covered in npm's documentation, there's nothing obscure about this.

I understand what the setting does. We had engine-strict=true - and we were told by staff @ npm it was deprecated and to remove it: https://github.com/TryGhost/Ghost/pull/5114.We were also told it was causing problems when installing ghost from npm.
That's why I'm asking you to verify that this mechanism (using the same setting in a different way) isn't going to cause the same issues.

Oh, engineStrict was actually removed because it was confusing and they felt package authors shouldn't have control over that setting: https://github.com/npm/npm/issues/7171#issuecomment-70608972
But that was never about engine-strict as in the npm config.
I really can't think of any issues this could cause. For apps that require ghost as a package, the .npmrc doesn't apply, so it's up to them to make sure the node version is supported.

@ErisDS Here is the test output, checking all versions supported by us against all dependencies:
hawk 3.1.0 does not satisfy engine 0.10.0 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.1 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.2 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.3 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.4 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.5 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.6 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.7 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.8 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.9 (>=0.10.32)
boom 2.9.0 does not satisfy engine 0.10.0 (>=0.10.40)
boom 2.9.0 does not satisfy engine 0.10.1 (>=0.10.40)
boom 2.9.0 does not satisfy engine 0.10.2 (>=0.10.40)
boom 2.9.0 does not satisfy engine 0.10.3 (>=0.10.40)
boom 2.9.0 does not satisfy engine 0.10.4 (>=0.10.40)
boom 2.9.0 does not satisfy engine 0.10.5 (>=0.10.40)
boom 2.9.0 does not satisfy engine 0.10.6 (>=0.10.40)
boom 2.9.0 does not satisfy engine 0.10.7 (>=0.10.40)
boom 2.9.0 does not satisfy engine 0.10.8 (>=0.10.40)
boom 2.9.0 does not satisfy engine 0.10.9 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.0 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.1 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.2 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.3 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.4 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.5 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.6 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.7 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.8 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.9 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.0 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.1 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.2 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.3 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.4 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.5 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.6 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.7 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.8 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.9 (>=0.10.40)
hawk 3.1.1 does not satisfy engine 0.10.0 (>=0.10.32)
hawk 3.1.1 does not satisfy engine 0.10.1 (>=0.10.32)
hawk 3.1.1 does not satisfy engine 0.10.2 (>=0.10.32)
hawk 3.1.1 does not satisfy engine 0.10.3 (>=0.10.32)
hawk 3.1.1 does not satisfy engine 0.10.4 (>=0.10.32)
hawk 3.1.1 does not satisfy engine 0.10.5 (>=0.10.32)
hawk 3.1.1 does not satisfy engine 0.10.6 (>=0.10.32)
hawk 3.1.1 does not satisfy engine 0.10.7 (>=0.10.32)
hawk 3.1.1 does not satisfy engine 0.10.8 (>=0.10.32)
hawk 3.1.1 does not satisfy engine 0.10.9 (>=0.10.32)
boom 2.10.1 does not satisfy engine 0.10.0 (>=0.10.40)
boom 2.10.1 does not satisfy engine 0.10.1 (>=0.10.40)
boom 2.10.1 does not satisfy engine 0.10.2 (>=0.10.40)
boom 2.10.1 does not satisfy engine 0.10.3 (>=0.10.40)
boom 2.10.1 does not satisfy engine 0.10.4 (>=0.10.40)
boom 2.10.1 does not satisfy engine 0.10.5 (>=0.10.40)
boom 2.10.1 does not satisfy engine 0.10.6 (>=0.10.40)
boom 2.10.1 does not satisfy engine 0.10.7 (>=0.10.40)
boom 2.10.1 does not satisfy engine 0.10.8 (>=0.10.40)
boom 2.10.1 does not satisfy engine 0.10.9 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.0 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.1 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.2 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.3 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.4 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.5 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.6 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.7 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.8 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.9 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.0 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.1 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.2 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.3 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.4 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.5 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.6 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.7 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.8 (>=0.10.40)
hoek 2.16.3 does not satisfy engine 0.10.9 (>=0.10.40)
hawk 3.1.0 does not satisfy engine 0.10.0 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.1 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.2 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.3 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.4 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.5 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.6 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.7 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.8 (>=0.10.32)
hawk 3.1.0 does not satisfy engine 0.10.9 (>=0.10.32)
cryptiles 2.0.5 does not satisfy engine 0.10.0 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.1 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.2 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.3 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.4 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.5 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.6 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.7 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.8 (>=0.10.40)
cryptiles 2.0.5 does not satisfy engine 0.10.9 (>=0.10.40)

Network requests in unit tests are ok? Sorry, there was no other way to get the node versions. And it's not what makes the test slow, 90% of the time is spend at npm.ls.  :unamused:

@jgillich Sorry if I gave you the wrong impression, I don't think this test is something that we should run all the time - I was thinking more along the lines of having a tool for checking this easily. It's not really a test because surely if it was, it would be failing right now?
As for going back to the discussion here about the engine-strict flag, I wanted to write up what was discussed in Slack...
Essentially, the engine-strict parameter is fine, unless you try to install ghost using npm install ghost on a version of Node <0.10.40, in which case you'll get a very unhelpful error message something like:
npm ERR! Error: No compatible version found: hawk@'>=3.1.0-0 <3.2.0-0'
npm ERR! Valid install targets:
npm ERR! ["0.0.1","0.0.2","0.0.3","0.0.4","0.0.5","0.0.6","0.0.7","0.0.8","0.1.0","0.2.0","0.3.0","0.4.0","0.5.0","0.5.1","0.5.2","0.5.3","0.6.0","0.6.1","0.7.0","0.12.0","0.12.1","0.12.2","0.13.0","0.13.1","0.14.0","0.15.0","1.0.0","1.1.0-pre","1.1.1","1.1.2","2.0.0","2.1.0","2.1.1","2.1.2","2.1.3","2.2.0","2.2.1","2.2.2","2.2.3","2.3.0","2.3.1"]
npm ERR!     at installTargetsError (/usr/share/npm/lib/cache.js:719:10)
npm ERR!     at next (/usr/share/npm/lib/cache.js:698:17)
npm ERR!     at /usr/share/npm/lib/cache.js:675:5
npm ERR!     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:142:7)
npm ERR!     at /usr/lib/nodejs/graceful-fs/polyfills.js:133:7
npm ERR!     at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

The problem is that within our dependency tree, there are dependencies which have set their engines to things like >=0.10.40 as seen in the test output above. It isn't actually causing us a problem, but in terms of complete version correctness, if we add engines-strict back as the default config, then we should also be either getting rid of those dependences or not supporting anything less than 0.10.40.
This gives us 3 options from here:

set our node version to > 0.10.40
leave it as is and add documentation for the issue as it only occurs for people npm installing
do something else

The problem with 1 is that we lose support for versions of node which people are currently running on with no warning, particularly a problem for people who use ubuntu LTS and are on node 0.10.25. The upgrade path would be:

grab the latest ghost
delete your old core folder and replace with the new one
run npm install --production
get an error and have to upgrade node or undo your Ghost upgrade.

This is just horrible, and we really need to provide a smooth mechanism for telling people it's time to upgrade node that's not halfway through an install. This needs to be done within the next few months but isn't realistic for right now.
The problem with 2 is that the error message that gets output from npm is confusing and says to report the error to npm. We had this situation before and it resulted in folks from npm complaining to us because they were getting lots of complaints. I don't really want to end up there again.
So we're back to 3.
As much as I think engine-strict is a nice solution, it really isn't viable right now.

Update: I spoke to the folks at npm. They advised that .npmrc has a security issue which means it is no longer included in packages as of npm 2.14.1 adding further complications, and also suggested that this is not the intended use case for engine-strict.
It seems to me that we need to define a custom env var that will allow users to disable the version check feature if we want to offer that.

The test isn't failing because I commented that part out. But it might as well be a Grunt task?
So, custom env var it is. Hopefully I can get that done tomorrow.

But it might as well be a Grunt task? (Edit: Just came to my mind that this could as well be a simple cli tool, nothing Ghost specific in there)

I was thinking it would make for a neat tool like npm-check :) https://www.npmjs.com/package/npm-check
Could also be wired up as a grunt task :)

So, custom env var it is. Hopefully I can get that done tomorrow.

That would be awesome - 0.7.2 is almost ready now and it would be ideal to get this in as part of it.

Everything else for 0.7.2 is pretty much done now. @jgillich are you working on this? At the bare minimum I want to get the preinstall hook into the next version to reduce confusion :wink:

@ErisDS All done now, sorry for the delay. My crappy Acer notebook died last Friday so I had to move everything to another computer.

authors: ErisDS jgillich


text:
fix: refresh settings cache for migration 006

no issue
If migration fixture 006/001 (transform dates) runs, it can happen that the settings cache is out of date and ember will get an outdated settings object. We are editing 2 setting entries, that's why we need to force clearing the settings cache.
We have deleted populateSettings in one of the previous PR's, which should have updated the cache after running migrations.

ready to merge 🎉


text:
Fix SVG minification

SVG minification in the next branch is currently broken. I have seen a few issues, one of which seemed to remove actual items from the compressed code. This, of course, affects the new SVG icon sprite-sheet workflow. SVGO is probably to blame for this and I will investigate the various SVGO options to see if one of them is causing the error. It could also be due to strangely formatted SVG code itself.. watch this space 👀

Do you have mode details on this issue and how could I reproduce it?
Maybe you can share files which caused the issue and I could try to have a look.

@rentorm I experienced a few issues where some svg paths or even groups were being removed. I have not been able to find the issue. I should find the offending SVG, the TMW logo, and add to the ticket..

Turned out to be a malformed SVG source file..

authors: mrmartineau rentorm

repo: TryKickoff/kickoff


text:
fix(carousel): when single pic should with no dot

Signed-off-by: Sepush sepush@outlook.com
close #1777

直接把 dotType 中的 never 改成showDots或许更好，让用户自己去控制，也能跟 showArrow 对应起来

感觉 never 够用了 我们把只有一张图片的情况默认处理了 其他的交给用户用 never 就好了 少开一些口子

authors: Sepush nooooooom

repo: TuSimple/naive-ui


text:
🛑 Content Delivery Network (S3 Bucket) is down

In 5990b37, Content Delivery Network (S3 Bucket) (https://cdn.tubnet.gg/minecraft-resourcepack/TubPack-production.zip) was down:

HTTP code: 522
Response time: 15653 ms

Resolved: Content Delivery Network (S3 Bucket) is back up in 45340f3 after 13 minutes.

repo: Tubnom/tubnet-uptime


text:
Spelling

This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at https://github.com/jsoref/TugboatQA-docs/commit/13fb7b23c7823b0618936094b00c1276cf97f930#commitcomment-82758600
The action reports that the changes in this PR would make it happy: https://github.com/jsoref/TugboatQA-docs/commit/1bdc23bf0bdc1138ab8c5e859dff70d897c6b7a9
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.

Nice, thanks @jsoref ! Looks like you'll need to run yarn lint-fix after these spelling fixes are made.

Done.

repo: TugboatQA/docs


text:
BUG Report - wrong search for sDelete in Windows system folder v1.3.0

In Windows 10 , sDelete-GUI 1.3.0 searches in sysWow64 folder for sDelete.exe instead of (to search for) sDelete64.exe and NOT searches in system32 folder for sDelete.exe.... This is a big BUG.... Only sDelete64.exe can be copied to sysWow folder. If we copy sDelete.exe to sysWow folder (instead of sDelete64.exe) , for the next time , Windows will automatically remove sDelete.exe from the sysWow folder. Also, the program doesn't search in system32 folder for sDelete.exe....

Thanks for the report, I will take a look next week!

I think there's some misunderstanding of system32 and SysWOW64 folder.
SysWOW64 is for 32-bit applications and system32 is for 64-bit applications:
https://www.howtogeek.com/326509/whats-the-difference-between-the-system32-and-syswow64-folders-in-windows

Fixed, working and published in 1.3.4. Thanks a lot @abyssox !

authors: RAJUPROP abyssox ricardopolo

repo: Tulpep/SDelete-Gui


text:
add a simpler block to Tweening

Allows a variable to automatically be tweened with the specified methods. Does not pause the thread in order to allow for multiple tweens in a row.

framerate isn't a massive issue, that's just a bi-product of changing framerates

i kinda think its something i should fix though
if a block doesnt work like it said it would then i would probably make an issue for it

fixed the problem

Someone has opened something similar already https://github.com/TurboWarp/extensions/pull/727

i think this would be a good addition to those blocks

just wondering, is there anything preventing this from being merged currently?

Superceded by https://github.com/TurboWarp/extensions/pull/851

repo: TurboWarp/extensions


text:
Trigger benchmarking with Bors commands

Turing's benchmarking is not used often at the moment. I think part of the reason is that the benchmarking process is a bit complicated, even with Nanosoldiers. Would it make sense to try to

trigger benchmarking for PRs using bors bot, with a customised command (see below)
replace Nanosoldier with PkgBenchmark , which is designed specifically for track performance changes of Julia packages.

Ps: some references:

bors try arguments: these arguments are stored as commit message, and can be extracted by the benchmarking script.
perhaps: bors try --benchmarking?

Maybe https://github.com/tkf/BenchmarkCI.jl could be useful. The trigger of the Github action could be adjusted to whatever we think would be suitable.

Closed in favour of https://github.com/TuringLang/DynamicPPL.jl/pull/346

authors: devmotion yebai