BindingResolutionException in Container.php line 744: Target [Illuminate\Contracts\Auth\Access\Gate] is not instantiable.

Hello, I'm receiving the following error when trying to configure this package on the newest version of Laravel (5.1.1).
BindingResolutionException in Container.php line 744: Target [Illuminate\Contracts\Auth\Access\Gate] is not instantiable.
Any help would be greatly appreciated.

I found a temporary workaround for this.
I commented out the following lines.
    public function boot(GateContract $gate)
    {
        parent::registerPolicies($gate);

        //
    }

Will look into that on sunday. Thanks @brockwddb for reporting the issue!

No problem @strebl. Thank you for looking into it.

Hey @brockwddb I can't replicate your problem.
I had an v5.1.3 Laravel test app, worked fine.
After updating Laravel to 5.1.17 (currently the newest version), app is still working.
After that, I follwed the optional upgrade guide - App still working.
I think its I typo, but you wrote that you are on v5.1.1, on which version are you?

5.1.16 (LTS) is the version I'm referring to. Sorry - typo.

Can you post your providers list in your config/app.php file?

'providers' => [

    /*
     * Laravel Framework Service Providers...
     */
    Illuminate\Foundation\Providers\ArtisanServiceProvider::class,
    Ccovey\LdapAuth\LdapAuthServiceProvider::class,
    Illuminate\Broadcasting\BroadcastServiceProvider::class,
    Illuminate\Bus\BusServiceProvider::class,
    Illuminate\Cache\CacheServiceProvider::class,
    Illuminate\Foundation\Providers\ConsoleSupportServiceProvider::class,
    Illuminate\Routing\ControllerServiceProvider::class,
    Illuminate\Cookie\CookieServiceProvider::class,
    Illuminate\Database\DatabaseServiceProvider::class,
    Illuminate\Encryption\EncryptionServiceProvider::class,
    Illuminate\Filesystem\FilesystemServiceProvider::class,
    Illuminate\Foundation\Providers\FoundationServiceProvider::class,
    Illuminate\Hashing\HashServiceProvider::class,
    Illuminate\Mail\MailServiceProvider::class,
    Illuminate\Pagination\PaginationServiceProvider::class,
    Illuminate\Pipeline\PipelineServiceProvider::class,
    Illuminate\Queue\QueueServiceProvider::class,
    Illuminate\Redis\RedisServiceProvider::class,
    Illuminate\Auth\Passwords\PasswordResetServiceProvider::class,
    Illuminate\Session\SessionServiceProvider::class,
    Illuminate\Translation\TranslationServiceProvider::class,
    Illuminate\Validation\ValidationServiceProvider::class,
    Illuminate\View\ViewServiceProvider::class,

    /*
     * Application Service Providers...
     */
    App\Providers\AppServiceProvider::class,
    App\Providers\AuthServiceProvider::class,
    App\Providers\EventServiceProvider::class,
    App\Providers\RouteServiceProvider::class,

 ],

I just did a fresh install of Laravel 5.1.17 and tried adding the provider and got the same error.

Okay I see the problem now.
Try to add Illuminate\Auth\AuthServiceProvider::class again.
Before Ccovey\LdapAuth\LdapAuthServiceProvider::class.
If that works, I'll update the docs.

Yes - appears to be working for me now.

Thanks @brockwddb for providing information and helping to resolve this issue!


Handle the ExhaustsResources issue

When doing a too big batch, we may get the error ExhaustsResources

The transaction would exhaust the resources of current block.
The transaction might be valid, but there are not enough resources left in the current block.

I came acros this when

undelegating 10+ tracks
remove vote
delegating 10+ tracks

So I imagine this may happen on Polkadot or Kusama. We need to check.
To prevent this, we need to split in different Txs, I don't think there's another way... Pinging the papi team here: https://github.com/polkadot-api/polkadot-api/issues/695

I came to this issue, as well when I tried to make a simple delegation on Westend


Implement navigating a TabContainer's tabs with keyboard or controller inputs

As far as I know, currently it is not builtin to switch tabs with keyboard/controller input.
However I think this is essential when you're developing a game that is meant to be played with a controller.
On top of that when you implement your own "hack" to enable this, you are still unable to move the focus above the tabcontainer without setting the corresponding Neighbour up for each tab.
I propose to map a shortcut for changing tabs to TAB and SHIFT-TAB (which should only happen if you're inside a tabcontainer with the focus).
It should be possible to enable the tabs to gain focus themselves, so they can be selected with ui_select.
My proposed key shortcut is currently used by ui_focus_next and ui_focus_prev actions by default.
I don't see a particular use case for these 2 anyway, because navigating with left,right, up and down keys is more intuitive than tabbing through all controls in order (but maybe they have their valid use cases and I just don't know them).
I would love to see this built into the engine.

Ctrl + Tab / Ctrl + Shift + Tab is a more common shortcut for changing tabs.

This should be fixed by https://github.com/godotengine/godot/pull/26597.

I am having this issue too
I need to be able to navigate tabs with not just the keyboard but gamepads as well
there is no tab on gamepads and up,down,left,right is how ui is handled it console games.

I'm also having this issue, can't use gamepads to navigate tabs.

you can't navigate between sliders either, and scrollbars can't even be moved with keyboard

Hi there, I do have this issue on Godot 4.1.3. No obvious way to use keyboard or controller to navigate tab containers.

This was implemented in 4.2 by https://github.com/godotengine/godot/pull/79104, closing. This won't be backported in 4.1.x, but you can try it out in 4.2.rc1 :slightly_smiling_face:


change concat_batches parameter to non owned reference

Which issue does this PR close?
Closes #3456
Are there any user-facing changes?
The users will be able to call concat_batches function by passing non owned references to RecordBatch
No breaking changes. Rust magically converts &[T] to impl IntoIterator <Item=&RecordBatch> while calling concat_batches function. So existing code calling concat_batches need no change.

cc @mustafasrepo


Updated yaml script as per the Issues raised by SQA

TC-DD-2.1 - Yaml script is updated as per Test-plan and Verfication sheet document.

Fix for https://github.com/project-chip/matter-test-scripts/issues/305,
https://github.com/project-chip/matter-test-scripts/issues/249,
https://github.com/project-chip/matter-test-scripts/issues/177.

TC-DESC-2.1 - Server List entries has been updated as per Verification step document.

Fix for https://github.com/project-chip/matter-test-scripts/issues/236

TC-DISHM-1.2 - Comment has been updated as per Verfication sheet document.

Fix for https://github.com/project-chip/matter-test-scripts/issues/292

TC-EEVSEM-1.2 - Comment has been updated as per Verfication sheet document.

Fix for https://github.com/project-chip/matter-test-scripts/issues/294

TC-EEVSEM-2.1 - Test step 9 PICS has to be updated as per Test plan.

Fix for https://github.com/project-chip/matter-test-scripts/issues/273

TC-I- 2.2, TC-I- 3.2 - Yaml has been updated as per the Tets-plan.

Fix for https://github.com/project-chip/matter-test-scripts/issues/232

TC-LWM-1.2 - Comment has been updated as per Verification step document.

Fix for https://github.com/project-chip/matter-test-scripts/issues/341

TC-MOD-1.3 - Yaml script has been updated as per Verification step document.

Fix for https://github.com/project-chip/matter-test-scripts/issues/358

TC-WASHERCTRL-2.2]- Yaml script has been updated as per Test plan.

Fix for https://github.com/project-chip/matter-test-scripts/issues/264

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


automate tasks and deployment

I am personally a fan of using Travis CI for this.

Update: using github actions for tests, so might try tweaking it to deploy the extension

I'm gonna let deployment be manual for now. I do not have enough maturity with deployment of VSCode extensions and it'd be painfully hard to automate, and also probably dangerous.


unable to get different dates with FuzzyDateTime

Hello,
In Django tests, i have
class EventFactory(factory.django.DjangoModelFactory):
    ...
    dtstart = FuzzyDateTime(datetime.datetime(2008, 1, 1, tzinfo=UTC), datetime.datetime(2009, 1, 1, tzinfo=UTC),
                        force_hour=10,
                        force_minute=30,
                        force_second=0, force_microsecond=0).evaluate(2, None, False)

and i use it:
self.event = EventFactory.create()
self.event2 = EventFactory.create()
self.event3 = EventFactory.create()

Displaying the resulting dtstart, i got:
dtstart: "2008-07-21 10:30:00+00:00"
dtstart: "2008-07-21 10:30:00+00:00"
dtstart: "2008-07-21 10:30:00+00:00"
The dates are the same, that's not what i expect.
What i don't understand is when i try it in python shell, everytime i call FuzzyDateTime(...), the rresult is always different.
Am i missing something?
thanks in advance for help,
gerard

Hi,
The problem is in your use of FuzzyDateTime.evaluate(): evaluate() is called by factory_boy's internals, this is what generates a new date.
Your code is equivalent to:
fuzzy_dt = FuzzyDateTime(
    datetime.datetime(2008, 1, 1, tzinfo=UTC),
    datetime.datetime(2009, 1, 1, tzinfo=UTC),
    force_hour=10,
    force_minute=30,
    force_second=0,
    force_microsecond=0
).evaluate(2, None, False)
# fuzzy_dt == datetime.datetime(2008, 7, 21, 10, 30)

class EventFactory(factory.Factory):
    dtstart = fuzzy_dt

When you declare a class, Python works as follows:

First, it evaluates the right-hand side of each attribute_name = value pair in the class declaration
Then, it passes those (attribute_name, value) pairs to the class definition.

Here, you're calling .evaluate() that returns an actual datetime.datetime instance instead of a generator.
=> You should remove the .evaluate() part.
Since .evaluate() was never intended to be used in Factory declarations, could you point me to the place you got the idea from? This is likely a bad documentation on my side :)
Thanks,

i found it here:
https://factoryboy.readthedocs.org/en/latest/fuzzy.html?highlight=fuzzydatetime#factory.fuzzy.FuzzyDateTime
and i used it as i was unable to obtain the datetimes i'm interested on.
In my project, i need to get a tuple of (start_dt, end_dt). Now, with your help, i can obtain start_dt, but how can i have end_dt as the result of start_dt+1hour?
thanks for your reply,

don't you think that, instead of generate random dates beetween limits, we could better have a sequence of datetimes, for instance:
EventFactory.create_batch(N, start_dt, period)
giving start_dt, start_dt+period, ... start_dt+N*period?
as in  .Sequence()?

Hi,
To get a end_dt, simply do the following:
class MyFactory(factory.Factory):
    start_dt = factory.fuzzy.FuzzyDateTime(
        datetime.datetime(2008, 1, 1, tzinfo=UTC),
        datetime.datetime(2009, 1, 1, tzinfo=UTC),
    )
    end_dt = factory.LazyAttribute(lambda o: o.start_dt + datetime.timedelta(hours=1))

As to the sequence, this is easy to design by overriding the rule for start_dt when calling create_batch:
EventFactory.create_batch(N,
     start_dt=factory.Sequence(lambda n: start_dt + datetime.timedelta(hours=n)),
)

Hi,
I'm closing this issue for now; feel free to re-open it if you need more help on this topic!


The device args doesn't take effect

Describe the issue
Run demo python with args like:
     --model-path /public/LLaVA/llava-v1.5-7b \
     --image-file "task_test.png" \
     --load-4bit
     --device='cuda:1'

Issue:
It will trigger different device error.
I believe it's a problem about the vision tower.
The images and casual language model are both in the device1 but the vision tower model.
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cuda:1! (when checking argument for argument weight in method wrapper_CUDA__cudnn_convolution)

Log:
Traceback (most recent call last):
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/planner/.vscode-server/extensions/ms-python.debugpy-2024.6.0/bundled/libs/debugpy/adapter/../../debugpy/launcher/../../debugpy/__main__.py", line 39, in <module>
    cli.main()
  File "/home/planner/.vscode-server/extensions/ms-python.debugpy-2024.6.0/bundled/libs/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py", line 430, in main
    run()
  File "/home/planner/.vscode-server/extensions/ms-python.debugpy-2024.6.0/bundled/libs/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py", line 284, in run_file
    runpy.run_path(target, run_name="__main__")
  File "/home/planner/.vscode-server/extensions/ms-python.debugpy-2024.6.0/bundled/libs/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 321, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "/home/planner/.vscode-server/extensions/ms-python.debugpy-2024.6.0/bundled/libs/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 135, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "/home/planner/.vscode-server/extensions/ms-python.debugpy-2024.6.0/bundled/libs/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 124, in _run_code
    exec(code, run_globals)
  File "/public/yzc/completely_new/first_load_llava.py", line 273, in <module>
    output=model(
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/public/yzc/completely_new/llava/model/language_model/llava_llama.py", line 81, in forward
    ) = self.prepare_inputs_labels_for_multimodal(
  File "/public/yzc/completely_new/llava/model/llava_arch.py", line 205, in prepare_inputs_labels_for_multimodal
    image_features = self.encode_images(images)
  File "/public/yzc/completely_new/llava/model/llava_arch.py", line 144, in encode_images
    image_features = encoder(images)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/public/yzc/completely_new/llava/model/multimodal_encoder/clip_encoder.py", line 54, in forward
    image_forward_outs = self.vision_tower(images.to(device=self.device, dtype=self.dtype), output_hidden_states=True)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/transformers/models/clip/modeling_clip.py", line 917, in forward
    return self.vision_model(
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/transformers/models/clip/modeling_clip.py", line 841, in forward
    hidden_states = self.embeddings(pixel_values)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/transformers/models/clip/modeling_clip.py", line 182, in forward
    patch_embeds = self.patch_embedding(pixel_values.to(dtype=target_dtype))  # shape = [*, width, grid, grid]
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 460, in forward
    return self._conv_forward(input, self.weight, self.bias)
  File "/home/planner/anaconda3/envs/habitat_latest/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 456, in _conv_forward
    return F.conv2d(input, weight, bias, self.stride,
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cuda:1! (when checking argument for argument weight in method wrapper_CUDA__cudnn_convolution)

Same here. Does anyone have a fix here?

same here.

same here.

same here


ble-shelly-dw.js does not do anything

Hello!
I've got an issue with the script of: ble-shelly-dw.js
I got a Shelly BLU DoorWindow. As you can see in the screenshot, I copied the address inserted and run the script. Nothing happens. Where is my error?

Thank you for your help!

Now I disabled the gateway option in the Bluetooth settings. Now I get rif of the "scanner already taken" issue. But still no reation.

Hello, @DaveMe81
Yeah the Bluetooth scan is shared across the device between observer, scripts and etc.
For the script "to do" something you have to populate both window open/close functions.

I installed FW 1.2.2 now, and it working now. So, deactive the bluetooth gateway in the settings, starting the script and voila works.


面板不能访问，成白板，shell命令ql update更新显示代码如下

现在ql应该是v2.8.5-001
运行命令ql update，显示v2.8.4-004，运行过ql check也不行。
代码如下：
root@qinglong:/ql $ ql check
开始执行... 2021-08-26 17:19:07
=====> 开始检测
---> 1. 复制通知文件
---> 复制一份 /ql/sample/notify.py 为 /ql/scripts/notify.py
'/ql/sample/notify.py' -> '/ql/scripts/notify.py'
---> 复制一份 /ql/sample/notify.js 为 /ql/scripts/sendNotify.js
'/ql/sample/notify.js' -> '/ql/scripts/sendNotify.js'
---> 通知文件复制完成
---> 2. 复制nginx配置文件
'/ql/docker/front.conf' -> '/etc/nginx/conf.d/front.conf'
---> 配置文件复制完成
=====> 检测面板

<script src="https://gw.alipayobjects.com/os/lib/react/16.13.1/umd/react.production.min.js"></script>
<script src="https://gw.alipayobjects.com/os/lib/react-dom/16.13.1/umd/react-dom.production.min.js"></script>
<script<EMAIL_ADDRESS><script<EMAIL_ADDRESS><script<EMAIL_ADDRESS><script<EMAIL_ADDRESS><script<EMAIL_ADDRESS><script src="/umi.c8a4ac84.js"></script>

=====> 面板服务启动正常
=====> 检测nginx服务
38 root      0:00 nginx: master process nginx -c /etc/nginx/nginx.conf
41 nginx     0:00 nginx: worker process
=====> nginx服务正常
---> pm2日志
2021-08-26T17:18:56: info:    ✌ Express loaded
2021-08-26T17:18:58: info:    ✌ DB loaded and connected!
2021-08-26T17:18:58: info:    ✌ Dependency Injector loaded
2021-08-26T17:18:58: info:    ✌ Express loaded
2021-08-26T17:19:00: info:    ✌ DB loaded and connected!
2021-08-26T17:19:00: info:    ✌ Dependency Injector loaded
2021-08-26T17:19:00: info:    ✌ Express loaded
2021-08-26T17:19:01: info:    ✌ DB loaded and connected!
2021-08-26T17:19:01: info:    ✌ Dependency Injector loaded
2021-08-26T17:19:01: info:    ✌ Express loaded
2021-08-26T17:19:03: info:    ✌ DB loaded and connected!
2021-08-26T17:19:03: info:    ✌ Dependency Injector loaded
2021-08-26T17:19:03: info:    ✌ Express loaded
2021-08-26T17:19:05: info:    ✌ DB loaded and connected!
2021-08-26T17:19:05: info:    ✌ Dependency Injector loaded
2021-08-26T17:19:05: info:    ✌ Express loaded
2021-08-26T17:19:06: info:    ✌ DB loaded and connected!
2021-08-26T17:19:06: info:    ✌ Dependency Injector loaded
2021-08-26T17:19:06: info:    ✌ Express loaded
2021-08-26T17:19:08: info:    ✌ DB loaded and connected!
2021-08-26T17:19:00: RangeError [ERR_FS_FILE_TOO_LARGE]: File size<PHONE_NUMBER>2) is greater than 2 GB
2021-08-26T17:19:00:     at FSReqCallback.readFileAfterStat [as oncomplete] (fs.js:303:11) {
2021-08-26T17:19:00:   code: 'ERR_FS_FILE_TOO_LARGE'
2021-08-26T17:19:00: }
2021-08-26T17:19:01: RangeError [ERR_FS_FILE_TOO_LARGE]: File size<PHONE_NUMBER>2) is greater than 2 GB
2021-08-26T17:19:01:     at FSReqCallback.readFileAfterStat [as oncomplete] (fs.js:303:11) {
2021-08-26T17:19:01:   code: 'ERR_FS_FILE_TOO_LARGE'
2021-08-26T17:19:01: }
2021-08-26T17:19:03: RangeError [ERR_FS_FILE_TOO_LARGE]: File size<PHONE_NUMBER>2) is greater than 2 GB
2021-08-26T17:19:03:     at FSReqCallback.readFileAfterStat [as oncomplete] (fs.js:303:11) {
2021-08-26T17:19:03:   code: 'ERR_FS_FILE_TOO_LARGE'
2021-08-26T17:19:03: }
2021-08-26T17:19:05: RangeError [ERR_FS_FILE_TOO_LARGE]: File size<PHONE_NUMBER>2) is greater than 2 GB
2021-08-26T17:19:05:     at FSReqCallback.readFileAfterStat [as oncomplete] (fs.js:303:11) {
2021-08-26T17:19:05:   code: 'ERR_FS_FILE_TOO_LARGE'
2021-08-26T17:19:05: }
2021-08-26T17:19:07: RangeError [ERR_FS_FILE_TOO_LARGE]: File size<PHONE_NUMBER>2) is greater than 2 GB
2021-08-26T17:19:07:     at FSReqCallback.readFileAfterStat [as oncomplete] (fs.js:303:11) {
2021-08-26T17:19:07:   code: 'ERR_FS_FILE_TOO_LARGE'
2021-08-26T17:19:07: }
=====> 检测后台
=====> 后台服务异常，重置基础环境并重启后台
---> 1. 开始检测配置文件
---> 配置文件检测完成
---> 2. 开始安装青龙依赖
检测到 /ql 的依赖包有变化，运行 npm install...
Lockfile is up-to-date, resolution step is skipped
Already up-to-date
---> 青龙依赖安装完成
---> 3. 开始安装脚本依赖
检测到 /ql/scripts 的依赖包有变化，运行 npm install...
Progress: resolved 1, reused 0, downloaded 0, added 0
 WARN  deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
Packages: -1
Progress: resolved 22, reused 22, downloaded 0, added 0, done
dependencies:

crypto-js 4.1.1

png-js

---> 脚本依赖安装完成
=====> 检测结束
执行结束... 2021-08-26 17:19:21  耗时 14 秒
root@qinglong:/ql $ ql update
fatal: Unable to create '/ql/.git/index.lock': File exists.
Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.
fatal: Unable to create '/ql/.git/index.lock': File exists.
Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.
error: cannot pull with rebase: You have unstaged changes.
error: please commit or stash them.
开始执行... 2021-08-26 17:19:38
开始更新仓库：/ql
Fetching origin
更新/ql成功...
开始更新仓库：/ql/repo/static
Fetching origin
HEAD is now at 24b812e copy static at 2021-08-25 15:58:02
Already up to date.
Current branch master is up to date.
更新/ql/repo/static成功...
当前版本 v2.8.4-004...
重启面板中...
执行结束... 2021-08-26 17:19:56  耗时 18 秒

哪个文件2G报错了，自己排查下

哇，大佬来啦。
请问怎么查文件的尺寸？我用window10+hyperv+Ubuntu，平时用finalshell管理，不过也只会些简单的命令，文件夹的操作还一直没有搞懂。

ql/db/中的crontab.db 有26.9G，正常吗？

不正常，远程下吧，你多少任务。目前用的数据库框架貌似有缺陷


Documentation on Accessibility

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
Is there any documentation outlining accessibility in Material UI? My team is evaluating frameworks to use, and I'm a big fan of Material UI, however, it's a tough sell if I can't really show that the framework aims to meet certain guidelines. Specifically I'm looking for 508 compliance.
I searched the docs and found that the datagrid seems to list the guidelines it tries to meet:
https://material-ui.com/components/data-grid/accessibility/#guidelines
Is there anything like this for the whole framework? I'm not really looking for ironclad support or anything, just something that states that the goal is to try and archive accessibility for certain guidelines. Does this project have any such goals for accessibility?

Duplicate of #14187

It has the same objective: document what's the state of a11y and WCAG compliance.

@oliviertassinari Good to know, thank you for the response! You may want to add that to this page:
https://material-ui.com/discover-more/vision/
As it simply states "Be cross browser compatible and accessible." Knowing that the objective is to meet certain levels of compliance is very valuable.


SSR asPath behavior when mounting app under a path

Bug report
Describe the bug
When mounting the next.js handler under a path asPath shows different values on server and browser.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Clone https://github.com/Janpot/next-mount-subpath
npm i
npm run dev
Go to http://localhost:3000/test
check the console

Expected behavior
No warnings
Screenshots

System information

OS: macOS
Browser: chrome
Version of Next.js: 6.1.1

Unrelated to this issue, but you're missing:
    server.get('*', (req, res) => {
      return handle(req, res)
    })

Actually, I don't want to serve anything under the root. I plan to compose several of these together with micro-proxy.
The app is working without your piece of code. What is it supposed to add?

Oh wait nvm you want to only server un /test 👍

For context, I'm just in the experimentation phase of a new i18n workflow I'd like to try.
basically

I'd like to run a next.js app for each locale
all of them get composed together with proxying
the next.js app webpack configuration will be augmented so it inlines i18n messages as react components (similar to this experiment)

It's actually a problem with express, they override req.url when using app.use
https://expressjs.com/en/api.html#req.originalUrl
This property is much like req.url; however, it retains the original request URL, allowing you to rewrite req.url freely for internal routing purposes. For example, the “mounting” feature of app.use() will rewrite req.url to strip the mount point.

Yes, they have req.originalUrl that we need to get back in the mix somehow

So what you have to do is req.url = req.originalUrl in the handler

This will also make sure Next looks for the right directory, as we don't have a client-side basepath option. Meaning your next/link wouldn't work correctly

I tried req.url = req.originalUrl but it doesn't work for me. next doesn't seem to recognize the internal urls anymore.
also, I have a solution for the next/link, I just need to prefix the asPath with /test. Witha  little context magic this becomes relatively clean
// components/link.js
import Link from 'next/link';
import React from 'react';
import PropTypes from 'prop-types';

export default class PrefixedLink extends React.Component {
  render () {
    const { href, as = href, ...props } = this.props;
    const { prefix = '' } = this.context;
    return <Link href={href} as={`${prefix}${as}`} {...props} />;
  }
}

PrefixedLink.contextTypes = {
  prefix: PropTypes.string
};

export class PathPrefix extends React.Component {
  getChildContext () {
    return { prefix: this.props.prefix || '' };
  }

  render () {
    return this.props.children;
  }
}

PathPrefix.childContextTypes = {
  prefix: PropTypes.string
};

Just make sure to set the context in _app.js and Links work everywhere
// pages/_app.js
import App, { Container } from 'next/app';
import React from 'react';
import { PathPrefix } from '../components/link';

export default class MyApp extends App {
  static async getInitialProps ({ Component, router, ctx }) {
    let pageProps = Component.getInitialProps
      ? await Component.getInitialProps(ctx)
      : {};

    return { pageProps };
  }

  render () {
    const { Component, pageProps } = this.props;
    return <Container>
      <PathPrefix prefix='/test'}>
        <Component {...pageProps} />
      </PathPrefix>
    </Container>;
  }
}

All your pages should be put into pages/test with this setup, that's the reason it doesn't work.

hmmm, that seems to generate some errors
GET http://localhost:3000/test/_next/-/page/test.js 404 (Not Found)

@timneutkens Actually, the following seems to do it:
    server.use('/test', (req, res) => {
      if (!/^\/(?:static|_next)\//.test(req.url)) {
        req.url = req.originalUrl;
      }
      handle(req, res);
    });

as well as
    server.get('/test*', (req, res) => {
      const nextUrl = req.url.replace(/^\/test/, '');
      if (/^\/(?:static|_next)\//.test(nextUrl)) {
        req.url = nextUrl;
      }
      handle(req, res);
    });

but tbh, it feels a bit hacky. I mean, whether using express or anything else, some url rewriting like this is always going to need to happen. Since it relies on internal API design (static|_next), it feels quite brittle.

In my ideal world I'd like to be able to do
const app = next({
  dev,
  conf: {
    appPrefix: `/test`, // tell next where the app root is
    assetPrefix: `/test`
  }
});

And
server.get('/test*', app.getRequestHandler());

And the pages would reside under /pages (no subfolder equal to the path)
This would make the resulting app quite portable across paths, only need to update appPrefix.
Is that something that next.js could be interested in in working towards?

@Janpot Tried your method above and I got a 404 for all my _next files.
server.use("/auth", (req, res) => {
    if (!/^\/(?:static|_next)\//.test(req.url)) {
      req.url = req.originalUrl;
    }
    handle(req, res);
  });

server.get("/auth*", (req, res) => {
const nextUrl = req.url.replace(/^\/auth/, "");
if (/^\/(?:static|_next)\//.test(nextUrl)) {
    req.url = nextUrl;
}
handle(req, res);
});

And you've put your pages under ./pages/auth/?

I did not. I think that is the issue... will report back once my build process finishes. Thanks!

So for localhost:3000/auth/PATH I get:
GET http://localhost:3000/_next/49d131b1-34ac-4d68-a8b2-a39a51266781/page/_app.js 404 (Not Found)
My pages are now inside the auth subfolder. Anything else I am missing?

@lucasnorman Check out this branch: https://github.com/Janpot/next-mount-subpath/tree/with-subfolder
@timneutkens Do you mean that with this solution, <Link>s are supposed to work with the right basepath?

Closing this in favor of #4998


Refuse to do destructive operations if disk has a mountpoint

Instead of letting the user choose which disks to ignore formatting, which is an approach prone to errors, we can use e.g. lsblk to detect the disk where the root / partition is mounted, and some other reserved paths (e.g. /media, /mnt, /run), and automatically ignore them.
The only disks we want to format are /dev/sd*, excluding the system disk, which may not always be /dev/sda.
For every other disk containing a swap partition, we should turn the swapoff before formatting.

get_disks provides the info now

If swapping is happening, [SWAP] is listed as a mountpoint. The server should do a swapoff automatically in that case and the client should not block any operation if [SWAP] is the only mountpoint (keep in mind that it may be repeated multiple times in the mountpoint array).

Title updated, related to #27, if we want to unmount disks we should create an unmount command


Exported test function typed

Issue: #12
What Changed

Added typings to the exported test function.
How to test

Install this version of the package
In your code editor, go to a test file
Verify that the page and other options in the test('test-name', options) argument are typed

[x] Author QA'd
[ ] Reviewer QA'd

Change Type

[ ] maintenance
[ ] documentation
[x] patch
[ ] minor
[ ] major

📦 Published PR as canary version: 0.0.26--canary.23.ca010d2.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

LGTM!

:rocket: PR was released in v0.0.26 :rocket:


Import error on protocol package

The relevant section of the stacktrace is:
    ...
    from thriftpy.rpc import make_server
File "/var/www/jmanager_scielo_org/jmanager-env/lib/python2.7/site-packages/thriftpy/rpc.py", line 7, in <module>
    from thriftpy.protocol import TBinaryProtocolFactory
  File "/var/www/jmanager_scielo_org/jmanager-env/lib/python2.7/site-packages/thriftpy/protocol/__init__.py", line 15, in <module>
    from .cybin import TCyBinaryProtocol, TCyBinaryProtocolFactory
ImportError: /var/www/jmanager_scielo_org/jmanager-env/lib/python2.7/site-packages/thriftpy/protocol/cybin.so: undefined symbol: be64toh

I've installed thriftpy with $ pip install cython thriftpy on a Centos 5.10 64bit machine.
Am I missing something?

Yah this package haven't been tested in Centos 5, may be this is the problem.
I'll see to it later.


Wrong test

it(@"Should recognize regardless of orientation") test recognizes an original image instead of the rotated one.
Proof is here: https://coveralls.io/builds/2256888/source?filename=TesseractOCR%2FUIImage%2BG8FixOrientation.m
The code for rotated images is never run.

Fix is here: https://github.com/ws233/Tesseract-OCR-iOS/commit/ae90c2ce87802f35aa220d6ff16dc55ec9ee6ffb
Proof is here: https://coveralls.io/builds/2380273/source?filename=TesseractOCR%2FUIImage%2BG8FixOrientation.m


makeBinaryWriter Writer gives empty results

  const prettyWriter = makePrettyWriter()
  prettyWriter.stepIn(IonTypes.STRUCT)
  prettyWriter.writeFieldName('foo')
  prettyWriter.writeInt(1)
  prettyWriter.stepOut()
  const prettyBytes = prettyWriter.getBytes()
  console.log(`should have contents: ${toBase64(prettyBytes)}`)
  // Prints
  // should have contents: ewogIGZvbzogMQp9

  const binaryWriter = makeBinaryWriter()
  binaryWriter.stepIn(IonTypes.STRUCT)
  binaryWriter.writeFieldName('foo')
  binaryWriter.writeInt(1)
  binaryWriter.stepOut()
  const binaryBytes = binaryWriter.getBytes()
  console.log(`should have contents: ${toBase64(binaryBytes)}`)
  // Prints
  // should have contents:

Thanks for reaching out about this delaneyj@!
The example here requires the writer to be closed before getting the bytes to print.
Solution:
const binaryWriter = makeBinaryWriter()
  binaryWriter.stepIn(IonTypes.STRUCT)
  binaryWriter.writeFieldName('foo')
  binaryWriter.writeInt(1)
  binaryWriter.stepOut()

  binaryWriter.close()   // <---- close the binary writer before getting the bytes

  const binaryBytes = binaryWriter.getBytes()

Ah, didn't see that in the example


build - debug playwright install

cc @lszomoru

You could also just add process.env.DEBUG="pw:install" inside the https://github.com/microsoft/vscode/blob/main/build/azure-pipelines/common/installPlaywright.ts.

@mxschmitt can you do this in a PR? maybe revert my changes then. thanks.


⚠ Bofrost.at has degraded performance

In 2da981a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1738 ms

Resolved: Bofrost.at performance has improved in 87b7f9f after 13 minutes.


Error: Failed to launch chrome!

Whenever I call puppeteer from inside a Docker image based on this buildfile - I get this error:
(node:9) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome!
[1125/075021.625772:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
It's just a simple:
var browser = await puppeteer.launch({ headless: true });
On the provided link it says: IMPORTANT NOTE: The Linux SUID sandbox is almost but not completely removed.
So I'm not sure it's a viable strategy to use that - do you know a solution?

Sorry, but it's a limitation with running it in Docker (which should be already sandboxed for most practical purposes). If you pass --no-sandbox to the args when launching, it should fix it:
browser = await puppeteer.launch({
    args: [
      // Required for Docker version of Puppeteer
      '--no-sandbox',
      '--disable-setuid-sandbox',
      // This will write shared memory files into /tmp instead of /dev/shm,
      // because Docker’s default for /dev/shm is 64MB
      '--disable-dev-shm-usage'
    ]
  })


[ESXi] Ubuntu Packer build process hanging

Reported externally, I'm able to reproduce:

Not sure what the root cause is at the moment.

Seeing lots of this in the Packer debug logs. Digging into it more:
2021/01/11 13:26:00 packer-builder-vmware-iso plugin: [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm list
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm port list -w 564925
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready
2021/01/11 13:26:10 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:10 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm list
2021/01/11 13:26:11 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:11 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm port list -w 564925
2021/01/11 13:26:11 packer-builder-vmware-iso plugin: [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready
2021/01/11 13:26:16 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:16 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm list
2021/01/11 13:26:17 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:17 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm port list -w 564925

Seeing lots of this in the Packer debug logs. Digging into it more:
2021/01/11 13:26:00 packer-builder-vmware-iso plugin: [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm list
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm port list -w 564925
2021/01/11 13:26:05 packer-builder-vmware-iso plugin: [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready
2021/01/11 13:26:10 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:10 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm list
2021/01/11 13:26:11 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:11 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm port list -w 564925
2021/01/11 13:26:11 packer-builder-vmware-iso plugin: [DEBUG] Error getting SSH address: No interface on the VM has an IP address ready
2021/01/11 13:26:16 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:16 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm list
2021/01/11 13:26:17 packer-builder-vmware-iso plugin: [DEBUG] Opening new ssh session
2021/01/11 13:26:17 packer-builder-vmware-iso plugin: [DEBUG] starting remote command: esxcli --formatter csv network vm port list -w 564925

This appears to be this issue: https://github.com/chef/bento/issues/1285

This appears to be this issue: https://github.com/chef/bento/issues/1285

At this point, I actually believe the root cause is connectivity. I have firewall rules blocking my lab hosts from initiating connections to my primary VLAN, so access to the preseed.cfg (which gets served on the host Packer runs on) would be blocked. When I moved the preseed.cfg to a host that my lab hosts can access, installation continued as expected.
TL;DR: Your ESXi host must be able to connect back to the host you're running packer from.

At this point, I actually believe the root cause is connectivity. I have firewall rules blocking my lab hosts from initiating connections to my primary VLAN, so access to the preseed.cfg (which gets served on the host Packer runs on) would be blocked. When I moved the preseed.cfg to a host that my lab hosts can access, installation continued as expected.
TL;DR: Your ESXi host must be able to connect back to the host you're running packer from.


Add MailHog  for email testing

Hey @stribny I love your work here. I think adding an email testing tool for developers would be a great addition.
If you wish I can contribute this snippet inside the docker-compose.yml
  mailhog:
    image: mailhog/mailhog:latest
    restart: always
    ports:
      -1025:1025
      -8025:8025

Hi @tugrulpinar!
Great idea!
I added it in this commit here: https://github.com/stribny/sidewinder/commit/5b7569ba52a9386f190a70422ffee9a9ce3d4344


AUDIO.findFreeChannel should start with 1 in Lua when startChannel_ is nil.

findFreeChannel should start with 1 in Lua when startChannel_ is nil.
function M.findFreeChannel(startChannel_)
	-- Solar2D API: audio.findFreeChannel( [ startChannel ] )
	-- Search will increase upwards from this channel. 0 or no parameter begins searching at the lowest possible value.
	-- The search does not include reserved channels.

	-- Returns 0 if no available channel found, else it returns next available channel.
	-- return getNextAvailableChannel(startChannel_ or 0) or 0
	return getNextAvailableChannel(startChannel_ or 1) or 0
end

This chained into another bug, both should now be fixed. Thank you!


All http verbs

This PR introduces the remaining http verbs:

DELETE
HEAD
OPTIONS
PATCH
PUT

I've left the PR as a draft for now.

@nunomaduro a quick question: can I add the python "mock" server I use to test the requests in the repository?
In case, please suggest a folder where I can put the python file and the documentation on how to run it for local testing.

@nahime0 Yes you can. You decide where to put it. Thanks!

@nahime0 Yes you can. You decide where to put it. Thanks!

Thanks, I'll make a different PR for that

Yes, working on it

PR ready: https://github.com/pestphp/docs/pull/246


Doesn't pass egui color test

The gradients should all match up seamlessly.
To reproduce:
let mut egui_test = egui_demo_lib::ColorTest::default();
egui::Window::new("Test").show(&egui_ctx, |ui| {
    let mut none = None;
    egui_test.ui(ui,&mut none);
});

I think the problem might be with the srgb conversion/blending code, but I'm not sure.

Thanks for pointing that out! I've put in a fix which appears to correct the color space, at least on my Mac. But if you can confirm, I will go ahead and mark this as fixed.

Looks fixed to me! :+1:


[Refactor] refactor spill trigger strategy for hash join

We try to reserve a large amount of memory (1G per operator) when restoring the partition hash table. In this PR, we modify the memory table size to memory_table_num * memory_table_bytes_size. If each partition is currently small, but the overall memory table exceeds the memory_table_bytes_size, we will flush half of the memory table to ensure that the memory table is smaller than the expected size.
this PR also fix a bug for auto-spill mode (rows unmatched)
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

could you provide some cases that can benifit from this new strategy?

could you provide some cases that can benifit from this new strategy?

add in description


Application from SUN ZU Lab

SUN ZU Lab
Grant category
Please select one or more of:

[ ] Open source maintenance
[x] Developer tools / services
[ ] Educational material
[x] Data provider

Description
SUN ZU Lab is a leading data solutions provider, on a mission to bring better data to the global crypto ecosystem through independent quantitative analyses. We collect the most granular market data from major liquidity venues, analyze it, and deliver our solutions through real-time dashboards. SUN ZU Lab provides crypto professionals with actionable data to monitor the market.
The dashboards will allow our users to: follow price action in real time in the most accurate way possible; identify and monitor price anomalies between different exchanges; get alerted of large unusual transactions or periods of exceptional volatility; identify the venue with the best price to adjust the inventory of their tokens.
Problem statement
Crypto has showed a tremendous growth potential but is still lacking institutional standards that help protect basic token users' rights. We believe that this is starting to change post defining events such as the Terra Luna ecosystem implosion or FTX's bankruptcy, and that our tools can help bring a deeper understanding and monitoring of tokens' market activity.
SUN ZU Lab dashboards and insights will help bring more maturity and institutionalize the crypto markets, driving the next wave of mass adoption from banks and asset managers managing trillions of retail investors money.
We target the B2B market of existing crypto market participants and TradFi Institutions. We identify 1 million addressable data consuming endpoints in TradFi alone (Bloomberg, Refinitiv… users). Our priority target clients are crypto/hybrid buy side, token ecosystems and crypto trading venues.
Impact
Using our dashboard, your ecosystem will be able to have a full 360 degree view of its token’s liquidity, and will be able to react in real-time to urgent market events that could be catastrophic if not well handled (deppeg, liquidity crunch, bid-ask spread spikes…). This in turn will increase the token's market circulation quality and bring a new wave of both retail and institutional users.
The idea of the collaboration with your ecosystem would be to create a free, open-source dashboard for token holders, allowing them to track the tokens’ activity in real time on a single interface. We could also make it available through API & Flat files.
A second use case is for your foundation directly (and CFO if exist); foundations are often asked to buy/sell large quantities of tokens. SUN ZU Lab Dashboard enables them to have an aggregated view and real-time monitoring tool of the market and, therefore to better choose or execute but also to be alerted if there is a liquidity issue on a market X, for example.
Milestones and funding
100% of the Grant is used to deploy the infrastructure of the integrated protocol & maintain it
(Maintenance = $03k / Month)

Milestone 1: Deployment on your ecosystem (Deadline: Q3 2023) $10k Deployment + $09k Maintenance
Milestone 2: 2k Unique Users on your ecosytem $09k Maintenance
Milestone 3: 10k Unique Users on your ecosystem (Deadline: Q1 2024) $09k Maintenance

We raised $1.5m in 2022: Backed by BPI France, Kima Ventures & Elaia.
And we already have secured $1.5m on $2m for this current seed round.
Website : https://sunzulab.com/
Pitchdeck : https://drive.google.com/file/d/1mb4-x1IuX7xaB26K2OENZixDmNQeNzqJ/view?usp=sharing
1 Pager : https://drive.google.com/file/d/1yGMwazOsxkH6dbMZhXxC6DVZNh-hf6zU/view?usp=sharing
Technical Stack : https://drive.google.com/file/d/1JOzK16MRXOQdKIGJ0t4J3KoEBjri99F9/view?usp=sharing
System Architecture : https://drive.google.com/file/d/1v51C3EbuvRMW9HJotna5o2aOzGf_wi_C/view?usp=sharing
Demo URL : https://drive.google.com/file/d/1Fb_u5DjcH21A7GYf2CPtOOIdLTMfKl0h/view?usp=sharing

@SunZuLab as pointed our in the readme and templates, our grants program is currently on pause until we relaunch a new program. we're not accepting new applications at this moment.


Open telemetry

This adds some basic spans to setup and to predictions when running the predictor via the Redis queue worker.
Telemetry is enabled when the OTEL_SERVICE_NAME environment variable is set. The OTLP exporter also needs to be configured via environment variables.
If a traceparent parameter is provided with the prediction request, Cog will use that value as the parent for the prediction spans. This allows spans from Cog to show up in distributed traces.
This PR includes a lot of whitespace churn due to the new with …: blocks, so is probably best reviewed with ?w=1

We should maybe pull some of the context from the commit messages into the queue worker docs.


Cash Out

Cash Out dosen't appear to have working winning conditions - I've both collected at least 25 gold and returned to the encampment.

Note - I go back if I have 30+ gold just incase it was a text error.

Fixed it.


:hammer: raise strict mode error for non-unique index

Usually when an index is not unique, you haven't properly specified the dimensions of the data or done roll-ups that you need to.
We would enforce this for new PRs only.

Here is an example of changes needed to comply with this strict mode: https://github.com/owid/etl/pull/1282

There's already a warning if an index is non-unique. I wanted to make it compulsory too, but then I decided it wasn't worth refactoring all steps (regions in particular).

only raise a warning instead of an error

I totally agree that this might be too strict, or not ideal. On this part, Pandas already warns every time, and we have tons of these warnings every day, which is what triggered this.


Switch the order of env var for LWS_LEADER_ADDRESS

What type of PR is this?
Quick change to make LWS_LEADER_ADDRESS to be the first container env var so we could reference that in the template from other env vars

What this PR does / why we need it
Which issue(s) this PR fixes

Fixes #
Special notes for your reviewer
Does this PR introduce a user-facing change?

In general, I'd agree with a better approach which is to have an annotation to store the leader address

Talked offline, we want to put the internal env variables in prior to the use specified ones, then envs like LWS_LEADER_ADDRESS can be reused, then makes sense to me. Please add a comment to explain the reason. Thanks.
By the way, hope to use as less annotations as we can since we have a bunch of annotations already, my two cenets.


Update INSTALL_RASPI.md

Updated time for Pi 4B. Plus address that rip_install is not set to +x

Thank you.


Wrong URL in QR code for helloPurr

I went to page
http://appinventor.mit.edu/explore/ai2/hellopurr.html
and tried to download the apk for HelloPurr using the QR code.
The code there seems  to be for the wrong URL:  It is
appinventor.mit.edu/sites/all/files/ai2tutorials/.....
The link just underneath there is correct:
appinventor.mit.edu/explore/sites/all/files/ai2tutorials/....
I didn't check any of the other tutorials, so I don't know how prevalent this is.
I'd hope we can easily solve this with a symbolic link on the server, but I don't know how that interacts with statification.

fixed with new QR code for this tutorial - did not investigate whether other QR codes were broken

fixed


HTML Renderer should show warnings/fail to render for JSON-schema violations

The HTML renderer currently accepts string values where a bool is expected, but the other renderers are strict about requiring a bool.  The payload below works in HTML but not in UWP or Android.
Our JSON-schema states that wrap is a boolean so we should probably run the payload through a JSON-schema validator and either output the warnings in the Visualizer or maybe fail to render.
Thoughts?
{
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "type": "AdaptiveCard",
  "version": "0.5",
  "body": [
    {
     "type": "TextBlock",
     "text": "Hello",
     "wrap": "true"
    }
    ]
}

Yes, we should run through a schema validator. This however requires that we have an up to date JSON schema, which I don't think is the case right now.


Quotes for urls

url(blah.png) or url('blah.png') pr url("blah.png").

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Hi All!
I'm closing this because unless a PR is created it won't likely be addressed.
If you feel strongly about this request I encourage you to dig in and submit a PR 😸


Text "Step of" and Skip are in English

Samsung Galaxy J3 Prime
Android version 7.0
Text “Step of" is in English on the French screens. Further, on the Step 6 screen, text "Skip" is in English.
Expected result
The text should be in French.
WCAG
https://www.w3.org/WAI/WCAG21/Understanding/language-of-parts
Screenshots

Closed by #318


How to set volume ?

Please show me the example for set the volume in docker-compose file.
Thank you

I was wondering the same thing, as this Redis UI definitely uses persistent data which will be lost if you remove and recreate the container by say updating your version of redis-commander.  I used the docker diff command to determine what files within the running container were changes and determined the configuration file you can map into your host is /redis-commander/config/local-production.json, so you can either bind mount this file, or use a volume for /redis-commander/config.  Hope that helps with your docker-compose configuration.

@kveroneau your assumption about persistent data is partly wrong - it does create this local-production.json file, but this one is automatically created from the env vars set for starting this container. And this file is overwritten on every restart. Therefore persisting it is completly useless.
It may seem to help if you do not configure every redis connection on startup but add/remove redis servers later on during runtime - they are saved there. But as i said, this file gets overwritten on next startup whenever an env var related to redis connections is set.
It may help only  to mount a config file if you have your own one to set other config parameters as you like without using env vars or define a much broader list of redis-connections as its possible via env var (as mentioned/suggested inside the redis commander docs). And this behaviour with the config files is documented directly under "Configuration" in the readme...
So the inital question - the first answer asking google presents an answer: https://stackoverflow.com/questions/42248198/how-to-mount-a-single-file-in-a-volume
or the docker-compose documentation itself at https://docs.docker.com/compose/compose-file/#volumes
And the issue author does not stated what he really want to do or reach - this very generic question can be completely answered by the docker documentaton alone. Cannot see something special or non-working stuff here...


static-css.d.ts is not being generated in the styled-system/types folder

Description
Typescript typecheck fails because in styled-system/types/recipe.d.ts RecipeRule is imported from a non-existing file (styled-system/types/static-css.d.ts)
Link to Reproduction
https://stackblitz.com/edit/vitejs-vite-xzduax?file=styled-system%2Ftypes%2Frecipe.d.ts
Steps to reproduce

Open the reproduction link
Go to styled-system/types
static-css.d.ts is not present
styled-system/types/recipe.d.ts is referencing the non-existing file

JS Framework
No response
Panda CSS Version
0.21.0
Browser
No response
Operating System

[ ] macOS
[ ] Windows
[X] Linux

Additional Information
No response

Good catch @bertuccellimatteo
I just pushed a fix for this. We'll release an update shortly.
If the issue persists after upgrading, I'll re-open it.


reduce and reduceBy

These two computed macros are not available in the current npm release.

Were added after 1.3.0: https://github.com/martndemus/ember-array-computed-macros/commit/86abc59ed603189a76d0bd12e6c6fa3eca83cf07
There haven't been a release for a long time...


Is it possible to implement a timeline semaphore with arbitrary payload value by any means?

I'm looking for a way to implement a semaphore with arbitrary payload value.
What I want is that I can signal a semaphore with any uint64_t value, and wait for it to become less/equal/greater than the signaled value.
Both of the VK_KHR_timeline_semaphore extension and this Vulkan-ExtensionLayer requires that the value in question must increase, going backwards is not allowed.
I wonder is it possible to emulate such a semaphore in vulkan layer or just by top level vulkan apis?

Thanks for your reply.
Some console platform implement this simply by a GPU label.
It is just a 4 or 8 bytes memory which will can be write and wait at proper pipeline stages.
I just guess desktop GPU should have such simple functionality.
But things seems not as easy as I think.


Fix recreate client after destroy

What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Intrgration test cases: https://github.com/apache/dubbo/issues/11782

Codecov Report

Merging #11780 (b862674) into 3.1 (7277c15) will increase coverage by 0.00%.
The diff coverage is 87.09%.

@@            Coverage Diff            @@
##                3.1   #11780   +/-   ##
=========================================
  Coverage     64.68%   64.68%
  Complexity       14       14
=========================================
  Files          1431     1433    +2
  Lines         60034    60065   +31
  Branches       8827     8828    +1
=========================================
+ Hits          38832    38856   +24
- Misses        17119    17136   +17
+ Partials       4083     4073   -10

Impacted Files
Coverage Δ

...bbo/rpc/protocol/ReferenceCountInvokerWrapper.java
80.95% <80.95%> (ø)

...apache/dubbo/rpc/protocol/InvokerCountWrapper.java
100.00% <100.00%> (ø)

... and 41 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


The python executable does not run on older OS X versions

Perhaps setting MACOSX_DEPLOYMENT_TARGET can help prevent this as suggested in Creating an embeddable Python distribution on OS X.

Running Python 3.5.2 built on Sierra on Yosemite:
Tests-MacBook-Pro:~ test$ /Applications/rinoh.app/Contents/MacOS/rinoh
dyld: lazy symbol binding failed: Symbol not found: _getentropy
  Referenced from: /Applications/rinoh.app/Contents/Resources/python/bin/python3 (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _getentropy
  Referenced from: /Applications/rinoh.app/Contents/Resources/python/bin/python3 (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

/Applications/rinoh.app/Contents/MacOS/rinoh: line 5:   611 Trace/BPT trap: 5       python/bin/python3 -m rinoh_macapp.app

Thanks for the report. I'll take a look at this when I roll the next release of the support packages.

If I'm reading this right, the change you've suggested should also result in a build that works on any release back to Mountain Lion. Unfortunately, I don't have a machine available to test this - I'm currently on Yosemite, and don't have easy access to Sierra or any earlier releases.
Are you able to confirm that adding MACOSX_DEPLOYMENT_TARGET=10.8 to the configure statement at line 259 of the Makefile results in a macOS build that works on Yosemite?

I installed Yosemite in a VirtualBox VM. That was not without problems, however. VMWare Fusion or Parallels should work better.
You might want to consider setting up CI on Travis to build the macOS binaries. Unfortunately, the macOS build servers are overloaded as is.

Perhaps another option is to build the binaries on an old macOS version, though I'm not sure they will run on later versions. The oldest macOS version supported by Travis is Yosemite (10.10). I would like to support at least back to 10.8. Do you think there is a need to support older versions?

Here's a .travis.yml to build binaries on Travis. It would be good to add basic tests, or perhaps even run the Python test suite. You could also automatically upload the tar.gz to Bintray, for example.
But since Travis only supports OS X back to Yosemite, the produced binaries won't run on older OS X versions. I don't suppose older SDKs are present on the Travis VM images, so we can't use the MACOSX_DEPLOYMENT_TARGET variable.

This should be addressed in the most recent binary builds (uploading as I type).
I agree that an automated build & test would be desirable; that should be opened as a separate issue.


Performance Issue

Any strategies or techniques can we implement to enhance the efficient and performance of the WinAppDriver process.? Currently we facing slow performance.

@PrajinC we have no performance problems. We used more FindElements instead of FindElement calls in our code.  With FindElements you need to wait for existence and clickable point.  With FindElement these are always waited for.  Hope this helps.


Add Links to Games in the README

@ninadsachania Great improvement! Thanks! 👍😄

No problem. Happy to help!


Heroku: introduce service support

[Current coverage][cc-pull] is 100%

Merging [#362][cc-pull] into [heroku][cc-base-branch] will not change coverage

@@           heroku   #362   diff @@
====================================
  Files          24     24
  Lines         365    365
  Methods        77     77
  Messages        0      0
  Branches        0      0
====================================
  Hits          365    365
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last updated by [64c40bd...40ef7f8][cc-compare]
[cc-base-branch]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/branch/heroku?src=pr
[cc-compare]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/compare/64c40bdc2f8b656835479b614ddd8b7d6163a34b...40ef7f8d2a95abcf8368198131016ba31eae9484
[cc-pull]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/pull/362?src=pr


FormsPlot: Fix issue affecting plots on windows that have been closed and reopened

My proposal to fix this issue is to instantiate the SKControl each time the form is shown.
In this PR:

in Sandbox.WinForms: Launch-button added to Winforms Sandbox to reproduce issue #3589
in ScottPlot.WinForms: Fix in FormsPlot

I tested this solution in 2 different applications with different chart types: it works without problems.

Hi @CodeBehemoth, thanks for this fix! I refactored your implementation a bit and moved your example out of the sandbox and into the demo app. I also added a related demo and a few Color niceties to this PR. I'm merging now and these features will be in the next release! 🚀


DBZ-3114 Support for Transaction Metadata in MySql connector

PROVIDE_TRANSACTION_METADATA

Will add the documentation and update the PR. Any specific reason to add PROVIDE_TRANSACTION_METADATA in MySqlConnectorConfig#CONFIG_DEFINITION? It's not done for Postgres.

It's not done for Postgres.

Yes, that's an oversight, it really should be there. I've logged https://issues.redhat.com/browse/DBZ-3132 for adding it for all the connectors which support this feature.

It's not done for Postgres.

Yes, that's an oversight, it really should be there. I've logged https://issues.redhat.com/browse/DBZ-3132 for adding it for all the connectors which support this feature.

Fixed this and added documentation. Please review and merge if looks good.

I reverted the change of adding PROVIDE_TRANSACTION_METADATA in MySQLConnectorConfig. It was already added from CommonConnectorConfig.

The field is defined in CommonConnectorConfig, but specific sub-classes must explicitly add this to the fields they expose. See the Oracle connector config for how it's done: https://github.com/debezium/debezium-incubator/blob/master/debezium-connector-oracle/src/main/java/io/debezium/connector/oracle/OracleConnectorConfig.java#L307 and https://github.com/debezium/debezium-incubator/blob/master/debezium-connector-oracle/src/main/java/io/debezium/connector/oracle/OracleConnectorConfig.java#L397 (only that configDef() and ALL_FIELDS is shared for MySQL).

Test failures might be unrelated, there are some intermittent ones unfortunately atm.

I guess it was not related to intermittent failure. I was getting this error while running the unit test.
"Configuration provide.transaction.metadata is defined twice."
Do I need to exclude first and add this explicitly ?

Ah, yes, that sounds related indeed. So looking at MySqlConnectorConfig again, it should be added - exactly once - to CONFIG_DEFINITION; is that what you tried?

Raaah, no, now I realize this CONFIG_DEFINITION extends the parent one. Sorry, I had missed that :( So no, you don't need to add it, indeed it's inherited already. Sorry about the noise.

Ah, yes, that sounds related indeed. So looking at MySqlConnectorConfig again, it should be added - exactly once - to CONFIG_DEFINITION; is that what you tried?

Yes, like this
https://github.com/nitin456/debezium/commit/a1541537da3629c57a29a02bff8255980fdce03a
One was already coming from HistorizedRelationalDatabaseConnectorConfig.CONFIG_DEFINITION.edit().

One was already coming from HistorizedRelationalDatabaseConnectorConfig.CONFIG_DEFINITION.edit().

Yes, exactly. I completely had missed we have this extension scheme in place already. All good then. Awaiting CI and then it should be ready to be merged. Sorry for the confusion.

One was already coming from HistorizedRelationalDatabaseConnectorConfig.CONFIG_DEFINITION.edit().

Yes, exactly. I completely had missed we have this extension scheme in place already. All good then. Awaiting CI and then it should be ready to be merged. Sorry for the confusion.

No problem, thanks :)

Applied; great work, thanks a lot!


fix(patch.js): fix functional component scope attribute update

fix functional component update scope attribute when patch use same node
fix #11171

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Running:  select2
 ✖ Timed out while waiting for element <.select2> to be present for 1000 milliseconds.  - expected "visible" but got: "not found"
    at Object.select2 (/root/project/vue/test/e2e/specs/select2.js:6:8)
    at process._tickCallback (internal/process/next_tick.js:61:11)

FAILED:  1 assertions failed (2.329s)

i dont know how to fix this error


Updates For Static Issue

IssueHunt Summary

Referenced issues
This pull request has been submitted to:

#224: Bug: Static noise appears over a long period of audio processing

Can you please reindent those two files with just 2 spaces? This project uses 2 space indentation format. Then I can merge in and release a test version for people :)

Done and pushed to my fork.Do I need to create another pull request?
On Wednesday, June 24, 2020, 01:36:51 PM EDT, Roman Kisil<EMAIL_ADDRESS>wrote:
Can you please reindent those two files with just 2 spaces? This project uses 2 space indentation format. Then I can merge in and release a test version for people :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

No I will sort everything out from here. Thank you. I will merge it into development for now and release a test build shortly

Once people approve the issue is fixed I will transfer the IssueHunt bounty to you

I somehow fucked up the merge trying to fix the indentations for you initially :( Will have to figure it out

I always just use the default Xcode 4 space.  I just changed it to 2, reformatted, and checked it in again.

Reply to this email directly, view it on GitHub, or unsubscribe.


Send Message👌

Sure! Here’s a structured email campaign for Black Friday to maximize online sales of handbag products. This campaign will include multiple emails, each designed to build anticipation, create urgency, and encourage conversions.
Campaign Overview:
Goal: Boost online sales of handbag products during the Black Friday shopping period.
Duration: Ramp up the campaign starting one week before Black Friday, with a series of emails leading up to and including the day itself.

Email Campaign Structure:
Email 1: Teaser Announcement (One week before Black Friday)
Subject Line: 🎉 Something Exciting is Coming – Black Friday at [Your Brand Name]!
Content:

Introduce the upcoming Black Friday sale.
Highlight exclusive handbag deals.
Use enticing visuals of top-selling handbags.
Include a countdown timer to create excitement.
CTA: “Get Ready for the Best Deals!”

Email 2: Sneak Peek (Five days before Black Friday)
Subject Line: 👀 Sneak Peek: Our Black Friday Handbag Specials!
Content:

Showcase a selection of featured handbags that will be on sale.
Include brief descriptions emphasizing quality and style.
Offer a “wish list” feature or link for customers to save their favorite items.
CTA: “Mark Your Calendar for Black Friday!”

Email 3: Early Access for Subscribers (Two days before Black Friday)
Subject Line: 🔓 Early Access: Black Friday Handbag Sale Just for You

Sure! Here’s a structured email campaign for Black Friday to maximize online sales of handbag products. This campaign will include multiple emails, each designed to build anticipation, create urgency, and encourage conversions.
Campaign Overview:
Goal: Boost online sales of handbag products during the Black Friday shopping period.
Duration: Ramp up the campaign starting one week before Black Friday, with a series of emails leading up to and including the day itself.

Email Campaign Structure:
Email 1: Teaser Announcement (One week before Black Friday)
Subject Line: 🎉 Something Exciting is Coming – Black Friday at [Your Brand Name]!
Content:

Introduce the upcoming Black Friday sale.
Highlight exclusive handbag deals.
Use enticing visuals of top-selling handbags.
Include a countdown timer to create excitement.
CTA: “Get Ready for the Best Deals!”

Email 2: Sneak Peek (Five days before Black Friday)
Subject Line: 👀 Sneak Peek: Our Black Friday Handbag Specials!
Content:

Showcase a selection of featured handbags that will be on sale.
Include brief descriptions emphasizing quality and style.
Offer a “wish list” feature or link for customers to save their favorite items.
CTA: “Mark Your Calendar for Black Friday!”

Email 3: Early Access for Subscribers (Two days before Black Friday)
Subject Line: 🔓 Early Access: Black Friday Handbag Sale Just for You


Update README.md

added some udemy courses

🛠 Fixes Issue

👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

Hi, this repository is just for free resources


Improve rustdoc-json-types message

Most of the PR's right now do need to change the types, so be clearer about that.
Additionally, be clearer about what FORMAT_VERSION is, and how it needs to be changed.

cc @craftspider


 Most of time we only need that when debugging. Dev will determine whenever to run up xdebug instead start by default
Example
ENABLE_XDEBUG=1

The two containers php-fpm and php-debug is by design and as running the debug container has no more overhead than running a 2nd fpm pool there is little reason to make the php-debug container optional when php-fpm is running. Doing so would make for a more confusing developer experience, as there would then be more things to check and steps to run through when preparing to debug. The intention here is for launching into debugging on a Warden environment be as simple as clicking the Enable Xdebug button from the Xdebug Helper browser extension and refreshing the page.


Refactor responses

The issue is about to return better data structure on fetch methods.
Then, every time  is possible to see more information about the response, like the parameters ,which it is not part of the pagination data.
Example:
Instead of return PaginatedData:
interface PaginatedData {
items
Pagination
}

# Response:
{
PaginatedData
Params
}

Duplicated #179


Shnaton parser - update and not just add

Right now, the shnaton parser only checks if the parsed object already exist in the database with their exact fields. If some field was changes (let's say an hour of a lesson) the shnaton parser will create a new lesson for that.
We need to be able to tell when a certain object is not new, find out what is the old object, and update it (or delete it and replace with a new one).

see https://github.com/asaf-kali/coursist/pull/110


Database Schema

[x] Operatinal Parts

[x] Operational center
[x] Programs
[x] Pumps
[x] Pump runtime

[x] Measurement

[x] Sectors
[x] Fields
[x] Field data

finalized with Version 2.0


operators [R] assisted-service-operator (0.0.4 0.0.5 0.0.6 0.0.7)

Newer versions were not marking older ones as replaced (since 0.0.4)
Signed-off-by: Flavio Percoco<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.

/cc @djzager

/merge possible

/merge possible


how to test the runtime isolation of computing resource and memory？

hi,
I want to test the runtime isolation of computing resource and memory, how to test the isolation and where are testcases for it? Thanks in advance!

We used detectron2 inference benchmark. To control the workload, we adjust the inter-arrival time of inference requests. For instance, you can increase the workload by reducing the inter-arrival time to force higher GPU utilization. By with our GPU isolation mechanism(Gemini), the GPU utilization should be bounded under the limit specified in YAML.


Edit

- Summary

- Test plan

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Working Product

.

Setting Updated


Docs: Change http to https

Proposed changes
Issue Number: close #xxx
Problem Summary:
A minor PR, change links in README from http to https
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Hi @morningman, sorry for asking questions in unrelated PR comments since the issue channel is not open in this project.
I find the project actually use Apache Maven as build system, but the maven root folder is a sub dir instead of root dir of the repo, do you have a plan to add other things not managed by maven to this repo?
Another question is the sub dir name is spark-doris-connector, but you define the <artifactId>doris-spark-connector</artifactId> in pom.xml, I think it's a little bit confusing.

Hi @pan3793 , thanks for your contribution.

since the issue channel is not open in this project.

I didn't notice that the issue feature is disabled. I will enable it later.

I find the project actually use Apache Maven as build system, but the maven root folder is a sub dir instead of root dir of the repo, do you have a plan to add other things not managed by maven to this repo?

Yes, there may be some other tools not managed by manve.
Because we've just moved this submodule from the Doris main repo.
And before everything settle down, I prefer to use a single dir to save the source code of the connector along.

Another question is the sub dir name is spark-doris-connector, but you define the <artifactId>doris-spark-connector</artifactId> in pom.xml, I think it's a little bit confusing.

Indeed, I will change it later.


pyeodh search example shortcomings

in the example pyeodh notebook:
https://github.com/EO-DataHub/eodh-training/blob/main/api-client/2_ResourceCatalog.ipynb
1.'rc' is not declared before use.
2. required packages shall be declared
3. data IDs are used directly like 'CMIP6.ScenarioMIP.THU.CIESM.ssp585.r1i1p1f1.Amon.rsus.gr.v20200806'
which shall be either found in the catalog UI - but then ideally it shall be accessed easier (in one step, not repeating navigation through collection) or found based on search criteria though the pyeodh (like searching with AOI, time, collection)

Thanks - we will attend to this issue when we update the training materials.


concurrency: support context propagator SPI

In order for mp-concurrency to replace Reactive Contexts which is currently used by RESTEasy to provide context propagation, it would be very useful if there could be an SPI to declare custom context propagators.
For example, RxJava 1 and 2 both support a plugin system where it is relatively easy to implement automatic context propagation with a context API such as mp-concurrency and Reactive Contexts.
Supporting an SPI for context propagators is as simple as defining an interface with a single setup method, and an entry in META-INF/services to declare implementations.
With this in hand, mp-concurrency could provide two optional dependencies that provide implementations that hook into RxJava 1 and 2 in order to use mp-concurrency context propagation to propagate contexts automatically to all RxJava pipelines, rather than require users to implement it themselves or depend on a third-party library.
Copied from https://github.com/eclipse/microprofile-sandbox/issues/19

I'll try to re-explain this issue here in case my original explanation was not clear.
In RESTEasy and Reactive Contexts we take advantage of RxJava's plugin system to make context propagation automatic. For example the following code works out of the box:
@GET
public Single<Hello> hello(){
 return Single.just("Hello")
  .delay(2, TimeUnit.SECONDS)
  .map(string -> string); // you can use your context here
}

This works because the resteasy-rxjava2 module imports the reactive-contexts-propagators-rxjava2 which implements the propagator SPI to register hooks into RxJava2 so that any callback created in an RxJava2 pipeline will capture the context and restore it in all subsequent listeners.
This is much better than requiring the user to use the context propagation API explicily, especially since context propagation is the better default.
For example, CompletionStage, which does not support plugins, requires users to do it explicitly by injecting a ThreadContext and calling ctx.withContextCapture() on every CompletionStage they get.
Does this help?

This has been implemented by #48


airflow: Repair run_id for FAIL event in Airflow 2.6+

Problem
In Airflow 2.6 in this PR there was a change regarding where the listener's on_task_X methods are called. As a result, the on_task_failure method is called before the TaskIntstance.state becomes FAILED and before the try_number is increased.
Here is PR from OL provider package related to this issue (probably I will try to improve testing there in near future).
When building run_id for OL FAIL event here, we are subtracting 1 from try_number when we should take it as it is, starting from  Airflow version 2.6.0.
Solution
To ensure compatibility across all supported Airflow versions, we should implement building run_id based on a _try_number (private) attribute of TaskInstance, which will remain unchanged regardless of the TaskInstance's state, leading to consistent run_ids for all task events.
I've also added integration tests that will verify if we receive exactly one START and one END (COMPLETE or FAIL) event for each run_id to make sure we can spot similar issues in the future . I've also added a DAG (bash_dag) in integration tests that will send both COMPLETE and FAIL events, and will run on all Airflow versions, to make sure there is at least one integration test always running and testing that test case.
One-line summary:
Run_id for FAIL event was different than in START event for Airflow 2.6+, this PR fixes it.
Checklist

[X] You've signed-off your work
[X] Your pull request title follows our guidelines
[X] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8f473e9) 83.92% compared to head (c6b10c4) 83.43%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2305      +/-   ##
==========================================
- Coverage   83.92%   83.43%   -0.50%
==========================================
  Files          59       54       -5
  Lines        3341     3169     -172
==========================================
- Hits         2804     2644     -160
+ Misses        537      525      -12

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Updated broadcast, get-score and added LICENCE.

given the use of this repo a more permsive license might be more apropriate, something like the https://choosealicense.com/licenses/unlicense/


Community Meeting May 8, 2024

Overview
At 10am Eastern, 7am Pacific, 2pm UTC; find your time
Video call link: https://meet.google.com/ved-ivnv-aen
dial-in: (US) +1<PHONE_NUMBER>
PIN: 873 550 579#
More phone numbers: tel.meet/ved-ivnv-aen?pin=7872592963542&hs=1
Add topics you'd like to discuss below!

Trusted Tasks:

Consider using a gated floating ref to reduce the amount of updates required.
Consider brainstorming ideas on a different approach to tracking trusted bundles.


Run headful mode in the background

I have several jobs that require running in headless false mode and therefore run them locally on my main machine.
Because each new page pulls Chromium to the foreground, I can't do anything else while these jobs run.
Is there a way to run headful mode but keep the puppeteer instance in the background?
I tried setting "CONCURRENCY_PAGE" which is better but still pulls the browser to the foreground on each new page.

Sorry, but this is out of scope of this library. There is probably a way to do this somehow by using Windows tricks, but this is a very special edge case, that this library will not support.


Enable Sourcegraph

I want to use Sourcegraph code search and code review with blinker. A project maintainer needs to enable it to set up a webhook so the code is up-to-date there.
Could you please enable blinker on @Sourcegraph by going to https://sourcegraph.com/github.com/jek/blinker and clicking on Settings? (It should only take 15 seconds.)
Thank you!

Done.


Delete pkg/typed_mock

Used by anyone?
CC @devoncarew @scheglov

In Analyzer and Analysis Server we migrated to mockito, and this is probably what users should do too.
So, yes, we can remove typed_mock now.

Happy to approve the CL
On Wed, Feb 21, 2018 at 12:04 PM, Konstantin Scheglov <
<EMAIL_ADDRESS>wrote:

In Analyzer and Analysis Server we migrated to mockito, and this is
probably what users should do too.
So, yes, we can remove typed_mock now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/32271#issuecomment-367453406,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCit21ZgtBaIw1lvMCk7HbLKQ3DhCaks5tXHbWgaJpZM4SOPbr
.

https://dart-review.googlesource.com/c/sdk/+/42862


Do we want to show a total for pending transactions?

Maybe the .../Transactions/NeedApproval page can show a total and count?

New vs. old

Sure, throw it in


Assistant with Multiple Vector Store Ids?

Hello,
I noticed that when creating the Assistant you could pass in a list of VectorStoreIds? At the moment however we can only pass in one VectorStoreId per Assistant. Does that mean there are plans for an Assistant to use multiple Vector Stores in the future?
Assistant assistant = await assistantClient.CreateAssistantAsync(
    model: "gpt-4",
    new AssistantCreationOptions()
    {
        Name = "Assistant v2",
        Tools =
                {
                    new FileSearchToolDefinition(),
                },
        ToolResources = new()
        {
            FileSearch = new()
            {
                VectorStoreIds = [vs1.Id] // can support multiple ids in the future?
            }
        },
    });

Great question, @hemnaathR! With the disclaimer that I have no insider knowledge one way or another, I'll say that guess makes a lot of sense to me and that I share it -- there wouldn't be much of a reason to define this as an "array of one item" (per API reference and YAML spec if there weren't a prediction of having more than one.

Cool. Fingers crossed. 🤞🏼


PR: Store autosave information in separate files instead of the Spyder config

Description of Changes

[x] Wrote at least one-line docstrings (for any new functions)
[x] Added unit test(s) covering the changes (if testable)
[x] Included a screenshot or animation (if affecting the UI, see Licecap) N/A

This PR stores which files are autosaved and where in a separate file called pidNNN.txt in the autosave directory, where NNN is the pid of the Spyder process. This information is used when the files are recovered after a crash. Before this information was stored in the Spyder config file.
The new approach has two advantages. Firstly, if the user is running multiple Spyder instances simultaneously, then one instance overwrites the changes the other instance makes to the config file, so the autosave info got muddled in the old system, while now each instance has its own location to write its data to. Secondly, by also recording the pid of the Spyder process that created the autosave file, we can check whether that process is still running. and not change the autosave file if it is.
Issue(s) Resolved
Fixes #9420
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:
Jitse Niesen

Hello @jitseniesen! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/editor/utils/tests/test_autosave.py:

Line 174:80: E501 line too long (82 > 79 characters)

In the file spyder/plugins/editor/widgets/recover.py:

Line 119:45: E261 at least two spaces before inline comment

I left a very small review because I trust your work to solve this problem.

Thanks, though I'm sure that it's possible to find more things that can be improved.


Relative paths error

Godot couldn't load the TileSet texture. The bug turned out to be that the plugin specified the wrong path to the image.
Here's my file structure:
res://
  maps/
    test.ldtk
    tilesets/
      dungeon.png

In the test.ldtk file the relative path to dungeon.png was specified as tilesets/dungeon.png.
On the line 123 in the LDtk.gd Godot returns an error file 'res://tilesets/dungeon.png' not found.
#create new tileset from tileset_data.
func new_tileset(tileset_data):
	var tileset = TileSet.new()
	var texture_filepath = 'res://' + tileset_data.relPath
	var texture = load(texture_filepath)

I fixed this bug by changing the value of the texture_filepath to:
var texture_filepath = map_data.base_dir + '/' + tileset_data.relPath

map_data.base_dir appears in the function load_LDtk_file:
#get LDtk file as JSON.
func load_LDtk_file(filepath):
    var json_file = File.new()
    json_file.open(filepath, File.READ)
    var json = JSON.parse(json_file.get_as_text()).result
    json_file.close()

    json['base_dir'] = filepath.get_base_dir()

    return json

After that, everything worked.
P.S.
sorry for my broken english

Thank you, I've updated the code to fix the issue.
Also your english is very good!

Thank you, I've updated the code to fix the issue.
Also your english is very good!


[DS-4127] Add Docker Build/Push to Travis Build

https://jira.duraspace.org/browse/DS-4127
(Depends on https://github.com/DSpace/DSpace/pull/2307)
purpose of this PR
The purpose of this PR is to generate a new Docker image for each DSpace pull request that passes the travis build checks.  This would allow other DSpace users to test the PR (in docker) without needing to compile a local instance of the pull request.
Sample Execution
This example assumes https://github.com/DSpace-Labs/DSpace-Docker-Images/pull/68 has been merged.
Assumption: a branch named pr1001 has been created for dspace-6_x.  At the end of the travis build, the following image will be published: dspace/dspace:dspace-6_x_pr1001.  To launch DSpace using that image, run the following.
export DSPACE_VER=dspace-6_x_pr1001
docker-compose -p d6 -f docker-compose.yml -f d6.override.yml up -d

Pre-requisites

A new team has been created in the dspace dockerhub repo that has write access to dspace/dspace
A new docker user has been created and added to that group
The username and password will need to be added as repository environment variables in travis for DSpace/DSpace

Build Output

Travis will terminate the build if the full docker build output is logged
Travis will terminate the build if no output is generated from the build step (note the egrep added to the docker build step)
The docker push step of the build is currently failing because a docker id/password have not yet been added to Travis

This pull request is part of a larger set of goals for DSpace and Docker

Make DSpace Docker Images the recommended approach for developing and testing changes to DSpace.  By creating a default development and testing environment for DSpace, the process of on-boarding and supporting new developers could be simplified.
Publish docker images for each pull request submitted to DSpace.  Because this would eliminate the need to run a local build for a given PR, the review cycle for PR's should be improved.
Document instructions for running published DSpace docker images on each of the major cloud providers.

Closing as "won't fix".  We've configured DockerHub to auto-build images on every commit to our repos, so this is not needed.

Closing as "won't fix".  We've configured DockerHub to auto-build images on every commit to our repos, so this is not needed.


Update the game over message

Update the game over message so people know how to play again!

d'accord


Update sha following 12.4.0 update

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please re-render

Thanks Alex! 🙏


better handling of bbox parameter starting with a minus

Bbox coordinates starting with a negative value result in a failing map machine render process, e.g. the giving the bbox
-b -57.5609702111,-38.0083456336,-57.5300067903,-37.9922146273 as parameter does not create a map.
I get the following error then:
$ map-machine render --cache /maps/cache -z 14 -o /maps/test.svg -b -57.5609702111,-38.0083456336,-57.5300067903,-37.9922146273
usage: map-machine render [-h] [-i [<path> ...]] [-o <path>]
                          [-b <lon1>,<lat1>,<lon2>,<lat2>] [--cache <path>]
                          [-z <float>] [-c <latitude>,<longitude>]
                          [-s <width>,<height>] [--buildings <mode>]
                          [--mode <string>] [--overlap <integer>]
                          [--labels <string>] [--level LEVEL]
                          [--seed <string>] [--tooltips | --no-tooltips]
                          [--country COUNTRY]
                          [--ignore-level-matching | --no-ignore-level-matching]
                          [--roofs | --no-roofs]
map-machine render: error: argument -b/--boundary-box: expected one argument

This error can be worked around when i leave out the space between the parameter and the bbox, e.g. -b-57.5609702111,-38.0083456336,-57.5300067903,-37.9922146273

It gets even worse if you use the bbox -23.0016,-67.7356,-23.0415,-67.7576:
$ map-machine render --cache /maps/cache -z 17 -o /maps/test.svg -b-23.0016,-67.7356,-23.0415,-67.7576
CRITICAL Negative horizontal boundary.
CRITICAL Specify either --input, or --boundary-box, or --coordinates and --size.

Hello, @Strubbl!
Just two days ago discussed this with @Eiim. Please take a look at his issue #109.
In #110 I've added even more notes to the readme and help message. But not sure whether this make things clearer or more confusing.

Thanks for the hint. I was searching the issues for the word longitude only, so that i have not seen #109


test

This is a test

Ttt
On Mon, Jan 2, 2023 at 8:40 PM mdoryammilwalrus @.***>
wrote:

This is a test
—
Reply to this email directly, view it on GitHub
https://github.com/IDontCodee/sussy/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWSFISQ675L7JBCRQGHWJXTWQOGTRANCNFSM6AAAAAATPIFJ2Y
.


Issue Reporting - application to be configure with task

Issue reporting is not loading, see screen shot error below

@mct8638Get Thanks for contacting us. Unfortunately, we're unable to handle Support requests for the product here. To contact Support, see here: https://powerapps.microsoft.com/support.
Closing this issue.