Is there a way to set different font size of text?

Hi, is there a way to set different font size of text?
PS thank you for this awesome library!

Yes! i found it! )
here is how to do it
GuiSetStyle(DEFAULT, TEXT_SIZE, 40);

@atakhan Hi! Glad you like raygui! 😄
Good to know youalready found how to change text size!
Hope you enjoy it!


fix(catalog-management): update catalog management examples after recent api changes

PR summary
Examples are aligned to the updated Api.
Worth to consider merge this PR after the following: https://github.com/IBM/platform-services-node-sdk/pull/113
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Improvement] Automatically get the correct device_id and product_id before creating the ControlCenter object

At first this software didn't work on my laptop (TongFang GM5ZG7W) until I looked at the code and realized it used a different product_id at this line in the main method :
control = ControlCenter(vendor_id=0x048d, product_id=0xce00)
Using lsusb, I found that the product_id for my laptop is not 0xce00, but 0x6004:
Bus 003 Device 005: ID 048d:6004 Integrated Technology Express, Inc. ITE Device(8291)
Changing this parameter made the script work.
This seems to be a common problem for many people (#55, #48, #44, #20).
A way to fix this would be to automatically find the correct device_id and product_id, which shouldn't be that hard to implement. The show_devices() method from PyUSB doesn't seem to be able to get the correct description, but lsusb has no problem finding ITE Device(8291). You could make a function that enumerates all lines generated by lsusb, and then get the device_id and product_id from the line containing the ITE Device(8291) string.

Hi, sadly I don't have that laptop anymore, I returned it because of the shitty keyboard. The code looks good, though!


Build GDT and nanopb with Swift Package Manager

Public header Imports in .m's use relative path
PubIic imports in .h's use simple file name for intra-module publics
Public imports from other modules use module import for SPM
Using forked repo for nanopb for now.

Ack, I'll sort out the copybara implications before merging back to master. Thanks


🌐 Add Chinese translation for docs/advanced/websockets.md

As title

It seems this was translated at some point in another PR. So I'll close this one, but thanks for the effort! ☕


(fix) chaos-operator: Changed Runner Default ENV to use go-executor

Signed-off-by: Rahul M Chheda<EMAIL_ADDRESS>
What this PR does / why we need it:
To understand this change and loogic behind it, please take a look at: chaosengine_controller.go +571
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Checklist:

[ ] Fixes #
[ ] Labelled this PR & related issue with documentation tag
[ ] PR messages has document related information
[ ] Labelled this PR & related issue with breaking-changes tag
[ ] PR messages has breaking changes related information
[ ] Labelled this PR & related issue with requires-upgrade tag
[ ] PR messages has upgrade related information
[ ] Commit has unit tests
[ ] Commit has integration tests

Update the env in the deploy folder also


Failed executions are not logged

I was trying to create a reproducible bug report script for this (which led to https://github.com/basecamp/solid_queue/pull/106), but in the meantime, let me just write this up.
Nothing is logged when a job raises an exception. I tested this with a simple job:
class RaisingJob < ApplicationJob
  def perform
    raise StandardError
  end
end

In the logs, all I see is:
20:43:35 queue.1 | [SolidQueue] Claimed 1 jobs

I can see the SolidQueue::FailedExecution object:
SolidQueue::FailedExecution.last
=>
#<SolidQueue::FailedExecution:0x0000000128493a58
 id: 17,
 job_id: 26,
 error:
  {"exception_class"=>"StandardError",
   "message"=>"StandardError",
   "backtrace"=>[...]},
 created_at: Sat, 30 Dec 2023 19:43:35.882895000 UTC +00:00>

Hey @fractaledmind, aren't these logged via Active Job's logger? I get this doing a similar test, with a job that raises:
[ActiveJob] [StoreResultJob] [9f6ae83e-f908-47fb-a3b4-e372e4b2a77a] Performing StoreResultJob (Job ID: 9f6ae83e-f908-47fb-a3b4-e372e4b2a77a) from SolidQueue(background) enqueued at 2024-01-01T11:41:37.871438000Z with arguments: 2, {:exception=>RuntimeError}
[ActiveJob] [StoreResultJob] [9f6ae83e-f908-47fb-a3b4-e372e4b2a77a]   TRANSACTION (1.2ms)  BEGIN
[ActiveJob] [StoreResultJob] [9f6ae83e-f908-47fb-a3b4-e372e4b2a77a]   ↳ app/jobs/store_result_job.rb:5:in `perform'
[ActiveJob] [StoreResultJob] [9f6ae83e-f908-47fb-a3b4-e372e4b2a77a]   JobResult Create (2.8ms)  INSERT INTO `job_results` (`queue_name`, `status`, `value`, `created_at`, `updated_at`) VALUES ('background', 'started', '2', '2024-01-01 11:41:38.092244', '2024-01-01 11:41:38.092244')
[ActiveJob] [StoreResultJob] [9f6ae83e-f908-47fb-a3b4-e372e4b2a77a]   ↳ app/jobs/store_result_job.rb:5:in `perform'
[ActiveJob] [StoreResultJob] [9f6ae83e-f908-47fb-a3b4-e372e4b2a77a]   TRANSACTION (3.4ms)  COMMIT
[ActiveJob] [StoreResultJob] [9f6ae83e-f908-47fb-a3b4-e372e4b2a77a]   ↳ app/jobs/store_result_job.rb:5:in `perform'
[ActiveJob] [StoreResultJob] [9f6ae83e-f908-47fb-a3b4-e372e4b2a77a] Error performing StoreResultJob (Job ID: 9f6ae83e-f908-47fb-a3b4-e372e4b2a77a) from SolidQueue(background) in 19.26ms: RuntimeError (RuntimeError):
/Users/rosa/Work/basecamp/solid_queue/test/dummy/app/jobs/store_result_job.rb:8:in `perform'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/execution.rb:69:in `block in _perform_job'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:121:in `block in run_callbacks'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/i18n-1.14.1/lib/i18n.rb:322:in `with_locale'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/translation.rb:9:in `block (2 levels) in <module:Translation>'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:130:in `instance_exec'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:130:in `block in run_callbacks'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/core_ext/time/zones.rb:65:in `use_zone'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/timezones.rb:9:in `block (2 levels) in <module:Timezones>'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:130:in `instance_exec'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:130:in `block in run_callbacks'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:141:in `run_callbacks'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/execution.rb:68:in `_perform_job'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/instrumentation.rb:32:in `_perform_job'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/execution.rb:52:in `perform_now'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/instrumentation.rb:26:in `block in perform_now'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.1.0/lib/active_record/railties/job_runtime.rb:13:in `block in instrument'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/instrumentation.rb:40:in `block in instrument'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/notifications.rb:206:in `block in instrument'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/notifications/instrumenter.rb:58:in `instrument'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/notifications.rb:206:in `instrument'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/instrumentation.rb:39:in `instrument'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.1.0/lib/active_record/railties/job_runtime.rb:11:in `instrument'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/instrumentation.rb:26:in `perform_now'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/logging.rb:18:in `block in perform_now'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/tagged_logging.rb:135:in `block in tagged'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/tagged_logging.rb:39:in `tagged'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/tagged_logging.rb:135:in `tagged'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/broadcast_logger.rb:212:in `method_missing'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/logging.rb:25:in `tag_logger'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/logging.rb:18:in `perform_now'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/execution.rb:30:in `block in execute'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:121:in `block in run_callbacks'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/railtie.rb:67:in `block (4 levels) in <class:Railtie>'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/reloader.rb:77:in `block in wrap'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/execution_wrapper.rb:88:in `wrap'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/reloader.rb:74:in `wrap'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/railtie.rb:66:in `block (3 levels) in <class:Railtie>'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:130:in `instance_exec'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:130:in `block in run_callbacks'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/callbacks.rb:141:in `run_callbacks'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.1.0/lib/active_job/execution.rb:28:in `execute'
/Users/rosa/Work/basecamp/solid_queue/app/models/solid_queue/claimed_execution.rb:49:in `execute'
/Users/rosa/Work/basecamp/solid_queue/app/models/solid_queue/claimed_execution.rb:29:in `perform'
/Users/rosa/Work/basecamp/solid_queue/lib/solid_queue/pool.rb:23:in `block (2 levels) in post'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.1.0/lib/active_support/execution_wrapper.rb:92:in `wrap'
/Users/rosa/Work/basecamp/solid_queue/lib/solid_queue/app_executor.rb:7:in `wrap_in_app_executor'
/Users/rosa/Work/basecamp/solid_queue/lib/solid_queue/pool.rb:22:in `block in post'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/safe_task_executor.rb:24:in `block in execute'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/synchronization/mutex_lockable_object.rb:48:in `block in synchronize'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/synchronization/mutex_lockable_object.rb:48:in `synchronize'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/synchronization/mutex_lockable_object.rb:48:in `synchronize'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/safe_task_executor.rb:22:in `execute'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/ivar.rb:170:in `safe_execute'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/future.rb:55:in `block in execute'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:352:in `run_task'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:343:in `block (3 levels) in create_worker'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:334:in `loop'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:334:in `block (2 levels) in create_worker'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:333:in `catch'
/Users/rosa/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:333:in `block in create_worker'

This might be in log/development.log for you depending on how you have this configured.
In any case, I still have this pending: https://github.com/basecamp/solid_queue/issues/103, which is kind of related.

Hmm. I'll need to double check my ActiveJob logger. Sorry for the noise in that case. I've really enjoyed working with SolidQueue thus far, so thank you for the great library.

Oh, no worries at all, logging is not great right now. I definitely have to improve it.


[CONTROLLER/DB] add drop db config

This PR is for:

Server

add drop db config
Checklist

[ ] Added unit test.

Backport to branches

main

 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.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Cannot properly check if user is signed in before_action sessions controller

https://github.com/plataformatec/devise/blob/master/app/controllers/devise/sessions_controller.rb#L3
  prepend_before_action :allow_params_authentication!, only: :create

This line above seems to authenticate a user not just allow authentication.
I'm using a before_action which checks if a user is signed in or not. Obviously a session create action should have no authenticated user before hand, however due to this method allow_params_authentication! I'm always being returned true before the action is run.
I've fixed it for now by skipping the before_action and including the call in the create action
skip_before_action :allow_params_authentication!, only: :create

def create
  allow_params_authentication!
  ...
end

However I think there may actually be a deeper issue. Is it a problem with the way current_user and user_signed_in? works?

bump

I'm closing this issue because it has not had recent activity.
If you're still facing this on the latest version, please open a new one with all the information requested in the template.
Thank you!


BugFix fix replica not found in TabletInvertedIndex

Proposed changes
adding and dropping backend in cluster may lead to the different replica in different backend have the same replica id,
at that time, 'delete from table partition xxx' operation will be failed with exception:'Failed to commit txn 862, cause tablet 11653 succ replica num 1 < quorum replica num 2. ...'
and also, with the above delete operation, drop replica operation(class:TabletInvertedIndex) will be failed with WARN log:
' could not find tablet id for replica xxx, the tablet maybe dropped'
fix in master branch already merged: #34117

run buildall

run buildall

run buildall

run buildall

run p0


Add gamepad support

add gamepad support - https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API

Great idea and thanks for the support! I'm currently rather busy, but will hopefully be able to test and merge this PR within the next days.

Its a bit of a different use case for me but I see other uses for it. Basically, Im building a retropie for a facility that has cc tv modulators. The retropie will feed for example CH14 UHF. People at their desk can tune their TV into the retropie video feed and plug in a controller to their desktop PC to control it. The physical gamepad experience is a big win.
However, I could see how others would just prefer the gamepad to be physically connected to their mobile device.

Thanks again for the work. Please note that it would have been easier if you had based your work on and filed the PR on the brach develop.


Get all instances status showHistory

Get all instances status
showHistory is listed as an optional parameter in the table below the example. That param doesn't work if you don't specify the instanceId parameter.
I'm not sure if it's a bug in the API but since it doesn't show in the example I suspect the documentation is wrong.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 94a5a1f9-c135-47d2-9d73-b9de575b87ce
Version Independent ID: d62bafe7-6be6-f537-8a4f-4d1acdfe26f3
Content: HTTP APIs in Durable Functions - Azure Functions
Content Source: articles/azure-functions/durable/durable-functions-http-api.md
Service: azure-functions
Sub-service: durable
GitHub Login: @cgillum
Microsoft Alias: azfuncdf

@yoHasse
Thanks for your feedback! We will investigate and update as appropriate.

It looks like the table is wrong. The instanceId field should be removed from the table. The "Get all instance status" API doesn't accept an instanceId parameter.

@cgillum Thanks for the confirmation.
@yoHasse Thanks for reporting this item! I have updated the doc and it will be published soon. We appreciate the feedback!


Slow concurrent (simple) requests

Hey, I'm looking for concurrently calling a PostgreSQL database.
 Except the first query is relatively fast (200ms, network is the bottleneck) but executing all of them takes 1.6s.
As a reference, if I execute the one of these requests in my local DB administration tool (Postico), it shows 120ms.
2021/04/10 03:03:18 /usr/local/go/src/runtime/asm_amd64.s:1371 SLOW SQL >= 200ms
[253.060ms] [rows:1] SELECT * FROM "sponsor" ORDER BY "sponsor"."id" LIMIT 1

2021/04/10 03:03:18 /usr/local/go/src/runtime/asm_amd64.s:1371 SLOW SQL >= 200ms
[991.458ms] [rows:1] SELECT * FROM "sponsor" ORDER BY "sponsor"."id" LIMIT 1

2021/04/10 03:03:19 /usr/local/go/src/runtime/asm_amd64.s:1371 SLOW SQL >= 200ms
[1122.117ms] [rows:1] SELECT * FROM "sponsor" ORDER BY "sponsor"."id" LIMIT 1

2021/04/10 03:03:19 /usr/local/go/src/runtime/asm_amd64.s:1371 SLOW SQL >= 200ms
[1126.283ms] [rows:1] SELECT * FROM "sponsor" ORDER BY "sponsor"."id" LIMIT 1

2021/04/10 03:03:19 /usr/local/go/src/runtime/asm_amd64.s:1371 SLOW SQL >= 200ms
[1125.981ms] [rows:1] SELECT * FROM "sponsor" ORDER BY "sponsor"."id" LIMIT 1

2021/04/10 03:03:19 /usr/local/go/src/runtime/asm_amd64.s:1371 SLOW SQL >= 200ms
[1127.910ms] [rows:1] SELECT * FROM "sponsor" ORDER BY "sponsor"."id" LIMIT 1

2021/04/10 03:03:19 /usr/local/go/src/runtime/asm_amd64.s:1371 SLOW SQL >= 200ms
[1129.831ms] [rows:1] SELECT * FROM "sponsor" ORDER BY "sponsor"."id" LIMIT 1

2021/04/10 03:03:19 /usr/local/go/src/runtime/asm_amd64.s:1371 SLOW SQL >= 200ms
[1129.891ms] [rows:1] SELECT * FROM "sponsor" ORDER BY "sponsor"."id" LIMIT 1

EXPLAIN ANALYZE SELECT * FROM "sponsor" ORDER BY "sponsor"."id" LIMIT 1;

Limit  (cost=0.29..0.48 rows=1 width=137) (actual time=0.022..0.023 rows=1 loops=1)
  ->  Index Scan using sponsor_pkey on sponsor  (cost=0.29..6336.49 rows=32283 width=137) (actual time=0.021..0.021 rows=1 loops=1)
Planning Time: 0.102 ms
Execution Time: 0.043 ms

Am I misunderstanding that the whole thing should take around [120ms, 200ms], and not 1.6s? If so, what's the incorrect assumption?

Any update here?


Yoga the height of the first View within a StackLayout does not respect height

The height of the first view within a StackLayout does not respect the height. It is set 600 like the StackLayout but looks much smaller
<StackLayout height="600" style="background-color: green">
      <View
        style="
        flex: 1;
        width: 500,
        height: 600,
        align-items: flex-start;
        padding: 20;
        background: black
      "
      >
        <View style="flex: 1; width: 10; height: 100; background: red" />
        <View
          style="
            flex: 1;
            width: 10;
            height: 100;
            background: blue;
          "
        />
      </View>
    </StackLayout>

It looks like this

And it should look like this

You have the style syntax is not valid you have

        flex: 1;
        width: 500,
        height: 600,
        align-items: flex-start;
        padding: 20;
        background: black

What you need

        flex: 1;
        width: 500;
        height: 600;
        align-items: flex-start;
        padding: 20;
        background: black

Sorry @triniwiz , removing that the behavior disappears.


Compatibility of your plugin with GLPI 10

Hello,
It doesn't say whether your plugin is compatible with GLPI 10, is this the case?
If not, are you planning an update?
Regards
François

Hello,
No it's not compatible with recent version of GLPI
The plugin was developed for glpi 0.83 / 0.84
GLPI 9 and later have introduced very significant changes that made the migration non-trivial
It is extremely unlikely I'll ever do it, as I'm not using GLPI any more for several years.
If you want to do it, there is a branch in which I prepared something for GLPI 9, but it was so long ago I don't even remember how close from done it was.


Are you considering providing a version for Babylon.js after completing this project?

Description
I would like to have a version for Babylon.js
Suggested solution
I'm currently learning Babylon.js and have noticed some differences in terms of mesh events between Three.js and Babylon.js. Unlike Three.js, Babylon.js provides a mechanism similar to the actionManager on its meshes. I'm curious to know if Cientos has a similar feature. I'm looking forward to seeing how the combination of Vue with Babylon.js will eventually shape a project
Alternative
No response
Additional context
No response
Validations

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

Hi there, thanks for your question, is quite interesting.
TresJS is a custom render on top of ThreeJS, so it's not meant to work with something else. I'm afraid it would be a completely different project and ecosystem.
I would love to see a Vue custom renderer for BabylonJS, if you are interested on starting one, we can share our experience in creating it.
Cheers!

Sure, just let us know how we can help you 😊


fix: improve error message for --signature-format flag

Resolves #868
Signed-off-by: Junjie Gao<EMAIL_ADDRESS>

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

Project coverage is 67.35%. Comparing base (eaa5fb4) to head (689006e).
Report is 23 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #925      +/-   ##
==========================================
+ Coverage   64.93%   67.35%   +2.42%
==========================================
  Files          45       45
  Lines        2729     2166     -563
==========================================
- Hits         1772     1459     -313
+ Misses        795      545     -250
  Partials      162      162

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


use repo package: references instead of copying code

use repo package: references instead of copying code

This is re-landing https://github.com/dart-lang/dart-pad/pull/2956, but with updates to the cloud build file and the dart_services docker config, in order to allow pub get to work from within the dart_services docker container.

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

Looks like this one did build cleanly.


Example uses 100% CPU on macOS

When compiling the example from the README on macOS (10.15.7, SDL2 2.0.16 from homebrew), the application goes to 100%.
Printing the events that come from SDL_PollEvent, it doesn't seem that there are many events coming in (just what you would expect). Any clue what could be wrong, or how to figure out what's going wrong?

Hi @remko, that should be because the loop doesn't have a delay so it would render as many times as it can. You could put a sdl.Delay(16) inside the for running {} loop to have it refresh at roughly 60 frames per second.

Hi @veeableful
Thanks! I was actually confusing the behavior of SDL_PollEvent with SDL_WaitEvent.


Remove redundant information from signals doc

When I was messing around with #1009 I noticed that it was still displaying "per 100 people" even though that text never appeared in the source. It turned out this text was coming from descriptions.raw.txt and descriptions.generated.json, which both get refreshed by npm start. These files are read by constants.ts, and from there, used everywhere. To prevent these files from forcing outdated information into the web visualizations, we should remove all redundant fields from each listing.
Link to signals description doc

I've completed a pass with suggest changes turned on. I've left "format" and "units" alone for now; we can adjust changes for #1009 in a separate effort. @sgratzl would you take a quick pass to see if the proposed changes are likely to cause anything to explode?


Changelog doesn't include 0.1.0 version

Just includes 0.0.1. We could however reset the changelog to start at 0.1.0 which was the first proper release

:(


basic pagination component

#17 Please let me know if that is what you had in mind

Oh I'm sorry. I've reviewd but didnt send it!

Hi @lubien, unfortunately I won't be able to help anymore. Please unassign me

Hi @lubien, unfortunately I won't be able to help anymore. Please unassign me

No problem. Best regards. Hope to work with you again if possible.


fix(node): Cache the full VoiceStateUpdate; fixes Player.moveTo()

Currently, only the session_id is cached. When needed, a VoiceStateUpdate is reconstructed by the getter Player.voiceState.
However, this "reconstructed" VSU is missing the channel_id property. This break Player.moveTo(), because it calls Node.voiceStateUpdate() with this partial VSU, which is basically a noop without a channel_id.
This commit fixes this issue by caching the full VoiceStateUpdate (which includes the channel_id) in the Node.voiceStates Map.
This is the cleanest way I found.

I cannot cache the channel_id in the Player, because it may not exists yet when Node.voiceStateUpdate() is called (and creating it at this point may be undesirable).
Creating another Map just to cache the channel_id looks wrong.

For the record, Player.moveTo() appears to have been broken by the commit 551792856fa110c499d87bc4a34e49d5835e2f09 which changed the behavior of Node.voiceStateUpdate() when the channel_id property is missing.

Ah, excellent catch and thanks for explaining. I think this is probably the most reasonable solution. Initially we were only storing the session ID in an attempt to reduce memory usage; however, especially since it's lossy, I think that was a bit of premature optimization.
551792856fa110c499d87bc4a34e49d5835e2f09 is also an attempt to avoid memory leaks and I believe the logic there is sound; if the VSU packet has a null channel ID, the connection is being terminated.

If we want to reduce a bit the memory usage, we can do something like:
this.voiceStates.set(packet.guild_id, {
  guild_id: packet.guild_id,
  channel_id: packet.channel_id,
  user_id: packet.user_id,
  session_id: packet.session_id,
});

This would notably remove the member object from the VSU, which is likely half of its size

Is there a need for the member object? If not, I suggest we move forward with cutting it out.


fix mypy issue on withdraw + some refactoring

fix mypy issue on withdraw + some refactoring

Codecov Report

Merging #1290 (99a8c7a) into main (cc7c380) will decrease coverage by 0.03%.
The diff coverage is 42.55%.

@@            Coverage Diff             @@
##             main    #1290      +/-   ##
==========================================
- Coverage   48.61%   48.57%   -0.04%
==========================================
  Files         270      270
  Lines       15674    15641      -33
==========================================
- Hits         7620     7598      -22
+ Misses       8054     8043      -11

Impacted Files
Coverage Δ

lnbits/extensions/withdraw/crud.py
25.00% <27.27%> (+0.43%)
:arrow_up:

lnbits/extensions/withdraw/lnurl.py
29.41% <30.00%> (+7.53%)
:arrow_up:

lnbits/extensions/withdraw/views_api.py
32.75% <44.44%> (-1.09%)
:arrow_down:

lnbits/extensions/withdraw/models.py
81.48% <100.00%> (+0.77%)
:arrow_up:

lnbits/extensions/withdraw/views.py
30.00% <100.00%> (-1.95%)
:arrow_down:

lnbits/db.py
81.20% <0.00%> (-10.07%)
:arrow_down:

lnbits/commands.py
73.61% <0.00%> (-1.39%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix Neo4j in Travis builds

Currently Neo4j refuses to run in Travis' new container-based architecture.
I'm not sure why these builds do succeed, perhaps caching helps here. However I've forked the repository, set up Travis builds for my fork and… Neo4j refuses to start. Not even on master of which HEAD equals to original master's HEAD.
I suppose that anyone who will fork the repository and set up Travis builds will stumble upon the same issue.
The problem can be mitigated by installing custom Neo4j version as pointed out here: https://github.com/travis-ci/travis-ci/issues/3243

@skalee Great, thanks! :beers:


Model developers can set models to "private"

When a model developer adds a model, other model/app developers can always run train jobs with his/her model. A model should instead be configurable to be "public" or "private".

Done with #88


dont see the plugin anymore

i cant find the zulrah plugin anymore in the sidebar.
reinstalled but didnt help.

The panel now auto removes itself when not in Zulandra.
To disable that feature, uncheck the autohide box in the config menu.
Also, hotkeys now only work when in the Zulrah instance.

got it ty.


Define quota with a config variable

It would be a great addition to be able to set upload quotas. This could be done on a per record, per person, per role, per community basis or other configuration possibility.
A few examples:

a new/default user could have a predefined allowed quota of 10Gb per record
a researcher (role) could have a quota of 100Gb
a certain community could set it's quota to 50Gb
for a one time thing, the quota for a certain record could be set to 100Gb

There are probably other configuration possibilities as well.
Additional context
The server (e.g. nginx) must be configured properly
Maximum item size per storage bucket must be considered
Updating UI components to reflect allowed upload size
Current workflow for changing file upload size for records

cookiecutter (nginx): https://github.com/inveniosoftware/cookiecutter-invenio-rdm/blob/v7.0/{{cookiecutter.project_shortname}}/docker/nginx/conf.d/default.conf#L118
files-rest: the default configuration doesn't impose limits on the buckets (the limits are set to None: https://github.com/inveniosoftware/invenio-files-rest/blob/d1fb4d2f8d36cf6798a2eab0cb25e7d81df954ca/invenio_files_rest/config.py#L45-L49
UI: https://github.com/inveniosoftware/invenio-app-rdm/blob/efb3848a710011a2b59dabb0f6eefbf830175948/invenio_app_rdm/theme/assets/semantic-ui/js/invenio_app_rdm/deposit/RDMDepositForm.js#L171-L172

Copy/Create and adapt react components for UI
Export new .js file
Copy/Create and adapt .html template (import .js file)
Define functions for upload/edit of record
Define routes for upload/edit of record

Benefits
Adapt quotas to own needs
Time saver when only setting a config variable instead of having to go through the above steps

I've moved the quota management to the product roadmap. This ticket is now only about making it easy to change the hard-coded quota.


test: Test split_url on Windows paths

:books: Documentation preview :books:: https://meltano-sdk--1044.org.readthedocs.build/en/1044/

Committed to #1043. No longer relevant.


brew install --interactive: put args in an environment variable for convenience

Motivation
I am frequently debugging brew install --build-from-source build failures. When I brew install --debug <formula> and get to the interactive shell, I have to scroll back up the terminal to see how the formula was ./configured. Usually the ./configure line is truncated and I have to rerun with the verbose flag to see all of the ./configure arguments.
After I successfully ./configure, I would like to either let the brew formula continue after the configure or let me know what subsequent commands it would issue (e.g. make bootstrap).
Proposed Solution
First steps
To make debugging --interactive installs more convenient, the configure args could be stored in an environment variable such as HOMEBREW_CONFIGURE_ARGS.
Further generalization
To take this idea further, (a more) interactive mode could stop before executing each command (seen preceded by ==> ) and prompt the user to continue to the next command or instead drop down into a shell. If the user chooses to drop into the shell, an environment variable HOMEBREW_COMMAND_ARGS could be set and possibly another for the executable such as HOMEBREW_COMMAND. After the user exits this shell homebrew will continue through the process.
Thoughts?

There's no way really of doing this generically internally. I'm open to other solutions to this problem though. Sorry!

Is monkey-patching Kernel::system to intercept the ruby system calls out of the question?

Yes, sorry.


fix(v-model): update model correctly when input event is bound #6690

Use the "input" event instead of "change" when listening for
changes to the selection state since the "input" event will
always fire before the "change" event.
This avoids an issue where a user binds to the "input" event
with "v-bind" and causes the component to update and set its
model value back to the value of the select before it has
received the new selection value.
Fixes #6690

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:
There is a detailed description of what causes this bug in https://github.com/vuejs/vue/issues/6690#issuecomment-333734327

Thanks again for the PR - however, I don't think switching events would solve the root problem, which is that microtasks (which Vue uses for async deferring) can fire in between these supposedly sequential events.
I managed to find a nextTick implementation that fires after all sequential events in 6e41679a96582da3e0a60bdbf123c33ba0e86b31.


tests/store.test.js is not executed

When I run npm test I get:
START:
ERROR: 'Warning: Failed propType: Required prop `href` was not specified in `A`.'

    ✔ should render its children
ERROR: 'Warning: Failed propType: Required prop `children` was not specified in `A`.'
    ✔ should adopt the className
    ✔ should adopt the href
    ✔ should adopt the target
  <Button />
    ✔ should render its children
ERROR: 'Warning: Failed propType: Required prop `children` was not specified in `Button`.'
    ✔ should adopt the className
    ✔ should render an  tag if no route is specified
    ✔ should render a button to change route if the handleRoute prop is specified
    ✔ should handle click events

    ✔ should render the copyright notice
    ✔ should render the credits

    ✔ should render its text

    ✔ should render its text

    ✔ should render its text

    ✔ should render an  tag
    ✔ should have an alt attribute
  <IssueIcon />
    ✔ should render a SVG
  <List />
    ✔ should render the component if no items are passed
    ✔ should render the items
  <ListItem />
    ✔ should adopt the className
    ✔ should render the content passed to it
  <LoadingIndicator />
    ✔ should render 14 divs
  App Actions
    loadRepos
      ✔ should return the correct type
    reposLoaded
      ✔ should return the correct type and the passed repos
    repoLoadingError
      ✔ should return the correct type and the error
ERROR: 'Warning: Failed propType: Invalid prop `src` of type `object` supplied to `Img`, expected `string`.'
  <App />
    ✔ should render the logo
    ✔ should render its children
    ✔ should render the footer
  appReducer
    ✔ should return the initial state
    ✔ should handle the loadRepos action correctly
    ✔ should handle the reposLoaded action correctly
    ✔ should handle the repoLoadingError action correctly
  selectGlobal
    ✔ should select the global state
  selectCurrentUser
    ✔ should select the current user
  selectLoading
    ✔ should select the loading
  selectError
    ✔ should select the error
  selectRepos
    ✔ should select the repos
  selectLocationState
    ✔ should select the route as a plain JS object
  <FeaturePage />
    ✔ should render its heading
    ✔ should link to "/"
  Home Actions
    changeUsername
      ✔ should return the correct type and the passed name
  <HomePage />
    ✔ should render the loading indicator when its loading
    ✔ should render an error if loading failed
    ✔ should render the repositories if loading was successful
    ✔ should link to /features
  homeReducer
    ✔ should return the initial state
    ✔ should handle the changeUsername action correctly
  getGithubData Saga
    ✔ should dispatch the reposLoaded action if it requests the data successfully
LOG: undefined
    ✔ should call the repoLoadingError action if the response errors
  selectHome
    ✔ should select the home state
  selectUsername
    ✔ should select the username
  <NotFound />
    ✔ should render the Page Not Found text
    ✔ should render a button
    ✔ should link to "/"
  <RepoListItem />
    ✔ should render a ListItem
    ✔ should not render the current username
    ✔ should render usernames that are not the current one
    ✔ should render the repo name
    ✔ should render the issue count
    ✔ should render the IssueIcon
  hooks
    getHooks
      ✔ given a store, should return all hooks
    helpers
      injectAsyncReducer
        ✔ given a store, it should provide a function to inject a reducer
      injectAsyncSagas
        ✔ given a store, it should provide a function to inject a saga
  request
    stubbing successful response
      ✔ should format the response correctly
    stubbing error response
      ✔ should catch errors

=============================== Coverage summary ===============================
Statements   : 98.58% ( 1184/1201 ), 42 ignored
Branches     : 95.68% ( 354/370 ), 64 ignored
Functions    : 95.97% ( 262/273 ), 6 ignored
Lines        : 98.41% ( 745/757 )
================================================================================

Finished in 0.193 secs / 0.112 secs

SUMMARY:
✔ 65 tests completed

In this output, I don't see the tests defined in store.test.js.
Why aren't included?

I guess the problem is inside the test-bundler, the regex excludes store.test.js

Good catch, we should definitely add that!

Fixed by the amazing @uzarubin in #858!


Update the Limitations

One of the limitations of the Insights feature is that it does not work when the report is distributed via 'App'. It only works if the report is accessed directly. Please confirm with the authors and add this as a limitation. This is an important limitation to know if the report will be distributed via App.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 216c87b1-d196-a091-048c-dc55b0649338
Version Independent ID: f8bb7489-d0bd-58f0-9eb3-6471d4d57eab
Content: Use insights to explain increases and decreases in visuals - Power BI
Content Source: powerbi-docs/create-reports/desktop-insights.md
Service: powerbi
Sub-service: pbi-reports-dashboards
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @pawarbi.
I've assigned this issue to the doc author for review.
In the meantime, you might find an answer in the Power BI Community.

Thanks for your comment! I've updated the article to reflect this limitation.


Replace require with import for images on the homepage

Problem

We use require for images on the homepage. require will be deprecated in Nuxt 3.
Description

We should move the images to /static folder, and use the static URLs.
https://github.com/WordPress/openverse/blob/507d7401a774aad70b984ae7237183d510b0de30/frontend/src/components/VHomeGallery/VHomeGallery.vue#L115-L117

I'd like to work on this.

Hey @WordPress/openverse-maintainers, I would like to work on this issue,

Hey @WordPress/openverse-maintainers, I would like to work on this issue,

@sehgxl , I've added more details to the issue description.

@obulat appreciate you adding the details, working on this.


lv_label pause at beginning of LV_LABEL_LONG_ROLL animation.

I think having the animation start immediately for LV_LABEL_LONG_ROLL animation is a bit jarring and can also cause a user to miss the first few characters, so I applied the same delay as at the end of the animation. I also exposed the macro to lv_conf for greater customization. Perhaps other animations like LV_LABEL_LONG_ROLL_CIRC should have this same initial delay.

Seems like a good update to me.

Added, seems like this is ready to merge?

Thank you @BrianPugh!


cookiecutter notes

remove data_dir fixture, possibly delete conftest altogether
remove python 3.8 support
add python 3.11 support?

Agree! I would also maybe consider some possible mechanism for testing upstream bioio-base compatibility.
Like how we are doing a test-upstreams on aicsimageio but the downstream plugins should have tests for upstream with bioio-base

Can be future thing tho


Enter custom value in QuerySelectField

Hi,
I have problem to create editable select.
The user should choose to pick from the list or add a new value.
I read many help for select2, flask-admin and nothing..
I use QuerySelectField.
Can You help me?

I can't think of a simple way to do this.
My approach would be to have two fields: a select and a text input field. Add a "new item" option to the select, and in your javascript, show/hide the text field depending on the select field's state.


Refs #13637 -- Removed unused code in GenericRelatedObjectManager

Appears unused since 585b7acaa359fc1df07269c1a4b4756bdb6703f7.

All the tests seems to have passed, I don't know why it's marked as failure.


Create dataset loader for SEA MADLAD

Dataloader name: sea_madlad/sea_madlad.py
DataCatalogue: http://seacrowd.github.io/seacrowd-catalogue/card.html?sea_madlad

Dataset
sea_madlad

Description
SEA MADLAD is a subset of MADLAD-400 (Multilingual Audited Dataset: Low-resource And Document-level), which is a document-level multilingual dataset based on Common Crawl. SEA MADLAD only filters the language of the "clean" subset, which covers 36 languages indigenous to SEA from 419 languages in total.   Please note some of SEA lang codes weren't available in this version because those belongs to the languages whose decision was to "remove from its clean version" based on MADLAD auditing process.  MADLAD uses all snapshots of CommonCrawl available as of August 1, 2022. The primary advantage of this dataset over similar datasets is that it is more multilingual, it is audited and more highly filtered, and it is document-level. The main disadvantage is also its strength -- being more filtered, it may lack the recall needed for some applications.

Subsets
ace, akb, ban, bbc, bew, bik, btx, ceb, fil, gor, hil, iba, ilo, ind, jav, kac, khm, kxd, lao, mad, mak, meo, min, mkn, msa, msi, mya, nij, nut, pag, shn, sun, tet, tha, vie, war

Languages
ace, akb, ban, bbc, bew, btx, ceb, fil, gor, hil, iba, ilo, ind, jav, kac, khm, kxd, lao, mad, mak, meo, min, mkn, msi, mya, nij, nut, pag, shn, sun, tet, tha, vie, war

Tasks
Language Modeling, Language Identification

License
Creative Commons Attribution 4.0 (cc-by-4.0)

Homepage
https://huggingface.co/datasets/allenai/MADLAD-400

HF URL
https://huggingface.co/datasets/allenai/MADLAD-400

Paper URL
https://arxiv.org/abs/2309.04662

#self-assign

Hi, this dataset hasn't been able to be implemented due to limitations in my storage. Will freeing up it after most of the reviewing process has been done


[MM-35712] Add notice about bindings refresh on oauth user change

Summary
Documentation for https://github.com/mattermost/mattermost-plugin-apps/pull/188
Ticket Link
https://github.com/mattermost/mattermost-plugin-apps/pull/188

/update-branch


Fix phase name typos in 5 packages' runHook invocations

Description of changes
Fix typos.
(Noticed while surveying custom hooks during https://github.com/NixOS/nixpkgs/pull/233837 review)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Uhm, I would have expected the build to fail in this case.

Invoking runHook on a thing that doesn't exist is an allowed no-op.  Often there's not a preFoo and postFoo for every phase Foo, and this is fine.
I think in all of these cases, the author intended to do the normal "When overriding a phase, for example installPhase, it is important to start with runHook preInstall and end it with runHook postInstall", in case they were defined.  No builds failed because no essential behavior (probably not any behavior) was in any of the missed-due-to-typo hooks.
This PR prevents future surprises if any of those hooks are defined for these packages in future (or out-of-tree), and stops spread of these misspellings before people copy/paste them as examples when setting up new packages.


Saving to %AppData%\Code

I'd like to save to %AppData%\Code but with this line in my user settings.json:
"local-history.path": "%AppData%\\Code"

I get an error creating directory or something. It seems that it tries to append %AppData%\\Code to the current working directory instead of resolving it to a full path.
Awesome extension btw :)

The path with %[Windows variables]% are not suported yet.

fix in version 1.2.1

Very cool, thank you!


reexport CPAL

I need to use CPAL for audio input but I'd have to take extra care of making sure that my version matches one used by rodio so that my crate::cpal::SomeStruct is the same as rodio::cpal::SomeStruct. If rodio reexported the entire CPAL module as rodio::cpal I wouldn't have have that problem.
Are there any reasons not to do that? If no, I can prepare a pull request.

I would like this feature. Do you want to go ahead?

Makes sense. breaking changes in cpal require breaking changes in rodio already. PRs welcome!


fill_in autocomplete form

Seems like to me that poltergeist is having some issues doing a fill_in on an autocomplete form, especially on fields that already have content.
ie: fill_in :name, with: "Bo" shows no change to the input field when I generate a capybara_screenshot
A workarround I found for this is to fill in our autocomplete fields via:
page.execute_script "$('input[name=#{locator}]').val('#{with}')"

I'm experiencing this problem as well.

If a minimal test case is provided that exhibits this behavior with latest poltergeist we can reopen, otherwise I'm closing this due to age


Missing token in WebGL builds

Describe the issue
I build for WebGL and the token is missing (either stripped by the building process or not included at all). I see that there is a VimeoSettings class that is used in VimeoBuildProcessor to set the token on build but nowhere in the README file says I should include a VimeoSettings component in the scene. Is the documentation missing something? Should the VimeoPlayer contain the settings?
Steps to reproduce the problem

Added package in the project
Added a VimeoPlayer (Canvas) object in my scene
Removed the Canvas and made it a child on my already existing Canvas and configured the video surface size to fit my scene.
Used the VimeoPlayer component to successfully login
Added a link for a private video (owned by me/in my account)
Built for WebGL
Deployed to test hosting
This error is displayed after scene loading is complete:

{
    "error": "Something strange occurred. Please contact the app owners.",
    "link": null,
    "developer_message": "No user credentials were provided.",
    "error_code": 8003
}

I inspect the requests sent by the browser and I see an API request to Vimeo with the following header:
Authorization: Bearer

which means the token is missing.
Unity version
2018.2.0f2
Operating system
Ubuntu 16.04 (KDE neon User Edition 5.13)

I checked out your repo, built one of your scenes for WebGL and it seems to bundle the token properly. I also tried building the project in OSX 10.12.6 with Unity 2018.2.1f1 but the issue persists.
I also checked the actual playerprefs file and the token is stored properly inside.
Any more ideas?

Ok, another update. The VimeoBuildProcessor's OnProcessScene assumes that the player will be direct child of the scene root. My setup positions VimeoPlayer in a (not so complex but quite deep) hierarchy of Canvas/UI elements thus not being able to be found by the build processor.
I'm going to fix that for my project, so do you accept pull requests regarding this or it's something you want to keep as is?

Hey @ragecryx - sorry for the trouble and thanks for uncovering the issue. We definitely accept PRs!  Although I went ahead and created one which should resolve the issue (see #39)


uthash: 2.1.0 -> 2.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/uthash/versions.
meta.description for uthash is: "A hash table for C structures"
meta.homepage for uthash is: "http://troydhanson.github.io/uthash"
meta.changelog for uthash is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.3.0 with grep in /nix/store/8si6nizlvd8r32fg242flw6j36x6b4gf-uthash-2.3.0

found 2.3.0 in filename of file in /nix/store/8si6nizlvd8r32fg242flw6j36x6b4gf-uthash-2.3.0

directory tree listing: https://gist.github.com/6e6bc398efd9ab2e1fe81ee6370aed96

du listing: https://gist.github.com/426677199203009669a43d309c938a7d

Rebuild report (if merged into master) (click to expand)

61728 total rebuild path(s)

17660 package rebuild(s)

17635 x86_64-linux rebuild(s)
16449 i686-linux rebuild(s)
11354 x86_64-darwin rebuild(s)
16290 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
AusweisApp2
CHOWTapeModel
DisnixWebService
EBTKS
EmptyEpsilon
MIDIVisualizer
OSCAR
OVMF
OVMF-CSM
OVMF-secureBoot
R
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net
SDL2_ttf
SDL_Pango
SDL_gpu
SDL_mixer
Sylk
Xaw3d
_1oom
_1password-gui
_20kly
_90secondportraits
a2jmidid
abbaye-des-morts
abcl
abcm2ps
abiword
abuse
accountsservice
acgtk
acoustidFingerprinter
acsccid
adafruit-ampy
adapta-gtk-theme
adementary-theme
adminer
adms
adobe-reader
adom
adoptopenjdk-bin
adoptopenjdk-hotspot-bin-11
adoptopenjdk-hotspot-bin-13
adoptopenjdk-hotspot-bin-14
adoptopenjdk-hotspot-bin-15
adoptopenjdk-hotspot-bin-16
adoptopenjdk-hotspot-bin-8

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8si6nizlvd8r32fg242flw6j36x6b4gf-uthash-2.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A uthash https://github.com/r-ryantm/nixpkgs/archive/8b86559adfa8caa6dcbf2202c1ff29d5852e5a4a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8si6nizlvd8r32fg242flw6j36x6b4gf-uthash-2.3.0
ls -la /nix/store/8si6nizlvd8r32fg242flw6j36x6b4gf-uthash-2.3.0/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings

Replaced with #136904 (fix tests running).


Update LiveRaveN.toml

Description
Previous PR's starting from testnet-3

540
1061
1711

If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present
[ ] The email, discord, elements telegram, and twitter fields are present and valid

Successfully validated transactions.toml file for commit hash 7427a77


Group: window list does not bring window into focus on click

In Ubuntu 14.04 when creating a pie for Group: window lists (like alt+tab), clicking on a slice doesn't bring the corresponding window into focus. The window is highlighted in the Unity launcher, but doesn't come forefront into focus. Tested in 2 different computers running 14.04.
Steps to replicate:
1- Create custom pie
2- Select Group:window lists
3- Open several windows on computer, for example, nautilus, firefox, writer, etc.
4- Call Gnome-pie custom launcher.
5- Click on any window that is not into focus.
6- On click, the window is highlighted in the Unity launcher menu, but it does not come into focus
Expected behaviour:
6- On click the window comes forefront into focus.

Thanks for your report! Can you please exit Gnome-Pie and launch it from terminal by typing
gnome-pie
Is anything printed to the terminal when activating a slice of your window-list-pie?

I came to the project to report on the same issue, I had it both on Ubuntu 14.04 and 14.10 (both at work n home).
Home PC is intel i5 with real time kernel
Work PC is intel i7 with generic kernel
No further customization on the systems. Ubuntu with unity and removed unnecessary stuff like shopping lens.
the logs are:
$ gnome-pie
[MESSAGE] Welcome to Gnome-Pie 0.6.1!
[MESSAGE] Loading Pies from "/home/budius/.config/gnome-pie/pies.conf".
[MESSAGE] Started happily...
[MESSAGE] Devices changed...
[WARNING] Failed to fetch xid: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.window' on object at path /org/ayatana/bamf/window/52428885
[WARNING] Failed to fetch type: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.window' on object at path /org/ayatana/bamf/window/52428885
[WARNING] Failed to fetch monitor: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.window' on object at path /org/ayatana/bamf/window/52428885
[WARNING] Failed to fetch maximized state: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.window' on object at path /org/ayatana/bamf/window/52428885
[WARNING] Failed to fetch xid: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.window' on object at path /org/ayatana/bamf/window/52428885
[WARNING] Unable to fetch children: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.view' on object at path /org/ayatana/bamf/application/1339296950

[WARNING] Failed to fetch path: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.application' on object at path /org/ayatana/bamf/application/1339296950

(gnome-pie:6014): Wnck-WARNING **: Received a timestamp of 0; window activation may not function properly.

I hope it helps, I'm loving this project, totally replaced my unity launcher

Here is my log when launched from terminal and trying to bring window into focus using the gnome-pie launcher
leo@Lemur:~$ gnome-pie
[MESSAGE] Welcome to Gnome-Pie 0.6.1!
[MESSAGE] Loading Pies from "/home/leo/.config/gnome-pie/pies.conf".
[WARNING] Failed to find file ".gtk-bookmarks"!
[WARNING] Icon "gnome-session-halt" not found! Using default icon...
[WARNING] No default icon found! Will be ugly...
[MESSAGE] Error loading image file: Failed to open file '': No such file or directory
[WARNING] Icon "stock_unknown" not found! Using default icon...
[WARNING] No default icon found! Will be ugly...
[MESSAGE] Error loading image file: Failed to open file '': No such file or directory
[MESSAGE] Started happily...
(gnome-pie:12517): Wnck-WARNING **: Received a timestamp of 0; window activation may not function properly.
(gnome-pie:12517): Wnck-WARNING **: Received a timestamp of 0; window activation may not function properly.
(gnome-pie:12517): Wnck-WARNING **: Received a timestamp of 0; window activation may not function properly.

Ok... this Wnck-WARNING seems interesting, I will have a look at this!

Hey, there was a simple fix I guess (9af18c88c382fe10bd0e8818332759da6f3d5495). Is it possible for one of you to compile the develop branch and confirm that it works as supposed?

Solve the issue for me in a VM running 14.04 32bits.
I'll tested in 14.04 64-bits when I'm back at home.

I'm installing dependencies compiling at this moment. I'll report back later today.
Do we get an ETA on this patch or I better use the dev branch for now?

OK tested on my work PC.
stock Ubuntu with Unity 14.10 (x64) on i7.
All working good.
Still doesn't change workspace if the running application is not in current workspace (but I guess that would be a different ticket).

An opt-in option to change workspaces if windows in different workspace would be amazing.

This fix will be part of 0.6.2 which I'll try to release at the end of next week!


Node.hide() throws "no node registered to path: null"

Getting this error when i try to hide a node  -

Could this be related to #487?

@ArjunRajJain can I see more of the code?


Update Contacts API docs

/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html
Updated to include information about not modifying a recipient's record when an API call attempts to upload an exact duplicate of that recipient. The recipient will be added to the "unmodified_indices" list.
Added unmodified_indices parameter to response bodies

@emily-stang-sendgrid This is the docs update you requested as per https://github.com/sendgrid/go_segment/pull/553
Would you be able to quickly review my changes? Thanks!

LGTM


feat: manage app settings

Allow managing app settings either in or outside of Terraform. Previously, we were only able to manage app settings outside of Terraform.
Checklist

[x] I've updated both the azurerm_linux_web_app and azurerm_windows_web_app resources.

Tests pass 🎉


Feature 3.10/computed values add test

Scope & Purpose
3.10 backport of https://github.com/arangodb/arangodb/pull/16619.

[ ] :hankey: Bugfix
[x] :pizza: New feature
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[x] Tests

[ ] Regression tests
[ ] C++ Unit tests
[x] integration tests
[ ] resilience tests

[x] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)

Related Information

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket:
[ ] Design document:

[x] https://jenkins01.arangodb.biz/job/arangodb-matrix-pr/22796/


Make page titles/headers more homogeneous

Current situation:

Technically h1 should be the preferred header to use for the main title of a page (also from accessibility perspective). However for me it looks a bit too heavy, so I combined it with Bootstrap fw-light to remove the bold. Let me know if you prefer something different.
I've also kept the breadcrumbs only on pages that have a parent page.
Ref f9f219989ae629b0f1e1543ac8cf4d0ccf9a4b23

Great that this becomes more uniform. Here are some minor points:

How does the Projects page (listing all the projects) look with this?
Regarding bold vs. light: no strong opinion, I'm fine with this light one.
Regarding breadcrumbs: The admin area doesn't necessarily need those, as admin area is a top-level link.
Have these new headers been applied like this everywhere? e.g. dataset pages? I actually think we could drop the title in the dataset page (similar to the workflow page), because the info is in the breadcrumbs. Same for the workflow job page

Regarding breadcrumbs vs. titles: It looks to me like we could go either/or instead of having both on some pages => top-level pages have a title, but no breadcrumbs (because those links are in the header). Pages further down the hierarchy have breadcrumbs, but no title (like workflows atm). Would that make sense?

We can remove all the titles of the pages that are directly accessible from the main menu. In that case we could also highlight the currently active section (I think we already discussed about this), to make it clearer where we are:

Oh, that's a great idea! Love it!
1-4 => perfect, let's go with that!

Regarding the first point, what about jobs page title? It says "Jobs of user X". Is this info useful to not confuse it with the admin jobs page? Could we rename the menu link to "My Jobs" and remove the title?

I don't think that's necessary for the job page. All our users don't have access to the Admin area. Plus, the admin area is marked with the nice red bar on top, so won't be confused :)
=> Let's also drop the title on the Jobs page

Looks great, thanks for the screenshots!


ASB:905 Check your submission item page add complete flag for submission items

:tada: This PR is included in version 2.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Porch migration to Nephio

Tracking issue for the migration discussed here: https://github.com/nephio-project/nephio/discussions/450
Migration

[x] Create new repository
[x] Migrate v0.0.35 server code to new repository
[x] Get builds working in new repository
[x] Get base CI working in new repository
[ ] Get Porch e2e tests working new repository
[ ] Migrate v0.0.35 CLI code to a new porchctl CLI tool (instead of kpt alpha)
[ ] Get the CI / e2e for the CLI working
[ ] Add a build or release process for the CLI binary
[ ] Consider re-introducing the changes in https://github.com/kptdev/kpt/pull/4094, but with additional E2E tests and related fixes (it seems to have some concurrency problems).

Clean Up

[x] Remove unused controllers
[ ] Move fleet-sync GCP-specific controller to a separate repo, and consider re-instating other GCP-specific controllers if desired
[ ] Remove the "Task List" concept from PackageRevision
[ ] Remove the Function CRD, as we are not using it
[ ] Remove the "Package" CRD, as it is not fully implemented
[ ] Consider removing OCI support. We don't use it today, and it is not as well exercised as the Git support

For the Porch e2e tests, it does some of them now but not the ones that require a cluster. We need:

Image build and push working for PRs for the nephio-project/porch repo
The make ci-test-porch needs to create a Kind cluster, deploy the code (make deploy), then set E2E=1 and do the make test. Right now, it doesn't set E2E so those tests are skipped.

See also
https://github.com/nephio-project/porch/pull/4#issuecomment-1861976730 and the subsequent comments.

@electrocucaracha can you help with the above?

Once this is done, we will want to update the docs to all use porchctl instead of kpt alpha. We will still use kpt for some things (like function execution, etc.).

Once this is done, we will want to update the docs to all use porchctl instead of kpt alpha. We will still use kpt for some things (like function execution, etc.).

Done

For the Porch e2e tests, it does some of them now but not the ones that require a cluster. We need:
* Image build and push working for PRs for the nephio-project/porch repo

* The `make ci-test-porch` needs to create a Kind cluster, deploy the code (`make deploy`), then set `E2E=1` and do the `make test`. Right now, it doesn't set `E2E` so those tests are skipped.

See also nephio-project/porch#4 (comment) and the subsequent comments.

PR raised here - https://github.com/nephio-project/porch/pull/21

Triaged
Triage Comment: Complete in R3

Closing with the following exceptions.
Outstanding items:

Task List removal/reimplementation. Issue created here - https://github.com/nephio-project/nephio/issues/822
OCI support will be retained for now
Package (PorchPackage) CR will be retained for now.


Create kubenav.yaml

this is a basic yaml file which can be used instead of helm with kubectl create -f kubenav.yaml

can you make this accessible publicly please?

Hi @si458, I'm not sure if we really need this file. What is the difference to just running kubectl apply --kustomize github.com/kubenav/deploy/kustomize or kubectl apply -f kustomize/?

Hi @ricoberger,
this was to help facilitate the install on the @civo kube100 clusters,
as they had kubectl installed but not the kustomize, so it required only a single yaml file
it might also help others who only use yaml files and dont understand kustomize like myself

Mh I'm still not sure about the additional file. My biggest problem with it is that it is another file, which must be maintained and the same can be achieved by running the following commands:
kubectl apply -f kustomize/namespace.yaml
kubectl apply -f kustomize/clusterrole.yaml
kubectl apply -f kustomize/clusterrolebinding.yaml
kubectl apply -f kustomize/serviceaccount.yaml
kubectl apply -f kustomize/deployment.yaml
kubectl apply -f kustomize/service.yaml

Hmmm ok don't worry about this file then
As is I managed to get the k3s helm cattle.io yaml working!?


contributor_docs folder creation and i18n contribution moving from wiki

As proposed on #340 by @lmccart and talked on #307 I'm creating the folder contributor_docs.
The aim of this folder is to store the wiki documentation un markdown files, in order to make easier the changes tracking.
In this PR I'm also moving the Contributing to p5.js website internationalization (i18n) from the wiki. This includes the creation of the sub-folder assets which stores the screenshots used in the tutorial.

Thanks @lmccart and @limzykenneth for your feedback and happy holidays, I'm working to update these changes.

Hi @lmccart and @limzykenneth, I've included all the suggestions you did.
Please let me know if there are any other changes you think can be included.
Just a heads up, I'll be offline for two weeks since Saturday.


Feature request: push insight events for quiet down mode, number of agents connected

Two very important things for me to alert on are whether our Jenkins is stuck in 'quiet down mode', and if there are no ephemeral agents connected.
It would be nice to be able to push this data up to NR insights, so that I can build alerts on it

Is there a reason for this just is being ignored/nothing happens? I think the idea is really good and I'd like to extend this to send more information - like queue as well. But I don't wanna start working on it if ain't going anywhere...
@dalvizu @sdewitt-newrelic @sschwartzman

@KvistA-ELS I did have a look a bit ago at #12 but I wasn't really fond of the implementation.  I was going to make comments on the PR but haven't been able to get to it.  I will try to get back to looking at it.

Hi @sdewitt-newrelic is there anything you'd like to see improved on the PR to make it more suitable for a merge?


Fix update model from server

Proposed changes:

Unzipping a model usually put the files in a default directory named after the archive name. If that's the case, domain and models should be taken from this directory (otherwise there is a FileNotFound error)

Status (please check what you already did):

[X ] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

 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.Nathan Zylbersztejn seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for submitting this PR, we'll give it a review as soon as possible

@znat thanks for submitting this PR! When you say usually put the files in a default directory, do you mean this also happens when the model is zipped from within the model directory? Because that's the intended zipping procedure before upload (cd models/dialogue && zip -r core_model.zip *)

@znat I see. But even if you zip the files in OS X and provide this zipped model at a model endpoint, the zip_ref.extractall() function handles it normally. The pull_model_and_fingerprint method isn't intended to look for local OSX-unzipped model files

But even if you zip the files in OS X and provide this zipped model at a model endpoint, the zip_ref.extractall() function handles it normally.

The bug happens with a model zipped locally with the mac os utility, then uploaded to an endpoint. After fetching, core unzips in the tmp folder and looks for model in the same folder as the archive. But it's one level below in the folder created by the macos utility. So unless you don't expect users to zip model files manually and to only use a particular utility to build archive it is still an issue I think

@znat I cannot reproduce this bug - would you mind posting exact steps to reproduce?
When I use the osx-native tool (right-click->Compress) and then in a python shell run zipfile.ZipFile('Archive.zip').extract_all('.') on that archive, I get the zipped files themselves, not contained in a default directory. See the screenshot attached - I presume you mean the same utility?

I'll close this, please let us know if there is still something we need to fix.


Slide in navigation

Here's a slide in navigation
https://jsfiddle.net/link2twenty/3bkvu1sq/
Needs Fixing:

Can still scroll background content when the menu is open.

Same concept different implementation
https://jsfiddle.net/link2twenty/bxjzdt39/


Fix #530 - Functionalize Korean translation

Continues #529

Checked the updated site, seems good!
Thanks for the quick response.
(Will ask others if my translation is OK, and if there are some strings to edit I'll PR when there should be major edits.)

Nice!


Full screen is not work on ipad

I have setup videojs-youtube on my website and everything ok but the full screen function doesn't work on iPad (Safari & Chrome). At first, i think it's an issue of my website code but i have try downloading your fresh example and try. It doesn't work too.
I have modified your example: http://www.mediafire.com/download/is0gcrce986ide1/videojs-youtube-fullScreen.zip
just open the file simple.html in examples folder. The top 2 video which using videojs-youtube cannot run full-screen on ipad. The last video which using a mp4 video source is ok.
I just try to call the function requestFullscreen() of video.js by another button but it cannot work too.
As far as my investigation, i have try adding some attribute like: allowFullScreen="true", webkitallowfullscreen and mozallowfullscreen = "true" also but nothing helps.
My ipad is working on iOS 8.3.

Could anyone help me out? any workaround solution or any information?

I have the same issue. Have you found a solution?

Nope, but i think it should be an issue of iOS and Youtube, not videosjs. I have tried other player like JWPlayer and exactly same issue happen. You may also try to open youtube.com on your ipad (remove youtube app if yu installed it) and force Safari request Youtube as desktop. If you click the full screen button, youtube will say, it not support - looks like even youtube cannot do anything better. So, all we can do: just customize to showing the message like that.


[Request] Add jrnl

Please add https://jrnl.sh/en/stable/
A command-line journalling tool

Hi there! I'm a jrnl maintainer and I primarily use Windows. I don't have much experience with scoop, but if anyone is interested in working on this and would like some help, please let me know here or feel free to chime in on our package manager issue.


add isort

See also #1386
When all is ready, I will call the command "python make isort" to sort all imports. This are the only manual changes.

The Travis Fail was expected. It will work when you give your OK and I actually changed the import-order.

See also: #1386

See also: https://groups.google.com/forum/#!topic/django-developers/EQhbI4cDuX4

I changed the pull request that only isort is installed and a isort-config file is appended. With this, we can use isort to fix the imports in one file but do not have to change any file right now.
We can add the travis check when the release is near.
-> Ready for review.

@normanjaeckel please review (I don't know If you realised my change here)

@normanjaeckel push

Rebase and merge.


rosdep: fixing osxbrew -> osx platform key

This is the only one like it, is this a valid platform key?

Uh, it used to be, when you could do OS X with Homebrew or Macports, they were different operating systems. But since then Macports has done their own thing where the ros packages are bundled in with MacPorts.


Temporary anka-base-XXXXXXXXX VM should be deleted after cloning to vm_name

I think the temporary anka-base-XXXXXXXXX VM should be deleted after cloning to the destination vm_name VM

The base VM could be used as source_vm_name for another build operations. From perspective of efficiency of disk space usage, it's recommended to use same base VM (with guest operating system and common stuff preinstalled) for different destination VMs.

It should at least be optional. We have no control over the name and you're appending a random sequence at the end of the name. Looking at the list of images is meaningless because you have no context as to which image is associated with what source. This is especially true in an unattended CI system.


[Tracking] Migrate Rest API to MLC Serve

Overview

This issue tracks the migration of Current Rest API backend to use MLC Serve. MLC Serve implements a paged KV cache interface and supports batched processings of prompts. This will allow the server to handle multiple requests concurrently.
Action Items

[ ] Confirm performance with batch size of 1 against the old interface
[ ] Migrate all the models to use the new KV Cache interface
[ ] Update Rest API docs to use MLC Serve
[ ] Delete old Rest API (pending finish of #1749)

Links to Related Issues and PRs

#1749
#1651
https://github.com/apache/tvm/pull/16273

cc @MasterJH5574 @tqchen @shreygupta2809

Hi guys, appreciate the work. We would love to support concurrent usage and therefore require this afaik. Do you have any timeline on this? Thanks a bunch!

@xapss Hi! This is mostly done :)

@Kartik14  Almost done? :)

@xapss Hi, this has been completed.
Thanks


msys2 package with pcre2-8 no more working :(

I'm currently using github actions with msys2 (project pvsneslib on github)
last week , everything was working fine with my windows part of my github action, which is:
        uses: msys2/setup-msys2@v2
        with:
          update: true
          msystem: UCRT64
          install: >-
            mingw-w64-ucrt-x86_64-toolchain
            mingw-w64-ucrt-x86_64-cmake
            mingw-w64-ucrt-x86_64-pcre2
            mingw-w64-ucrt-x86_64-doxygen
            base-devel
            git
            zip

This week, when I launch the action, during compilation of the lib, I have
gcc -Wall -O2 -pedantic -D__BUILD_DATE="\"20240302\"" -D__BUILD_VERSION="\"1.0.0\"" -DPCRE2_STATIC  build/helpers.o  build/main.o  build/optimizer.o -lpthread -lpthread -static -lpcre2-posix -lpcre2-8 -liconv -o 816-opt.exe
D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../lib\libpcre2-posix.a(libpcre2_posix_la-pcre2posix.o):(.text+0x18e): undefined reference to `__imp_pcre2_match_data_free_8'
D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../lib\libpcre2-posix.a(libpcre2_posix_la-pcre2posix.o):(.text+0x19d): undefined reference to `__imp_pcre2_code_free_8'
D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../lib\libpcre2-posix.a(libpcre2_posix_la-pcre2posix.o):(.text+0x26e): undefined reference to `__imp_pcre2_compile_8'
D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../lib\libpcre2-posix.a(libpcre2_posix_la-pcre2posix.o):(.text+0x292): undefined reference to `__imp_pcre2_pattern_info_8'
D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../lib\libpcre2-posix.a(libpcre2_posix_la-pcre2posix.o):(.text+0x2a9): undefined reference to `__imp_pcre2_match_data_create_8'
D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../lib\libpcre2-posix.a(libpcre2_posix_la-pcre2posix.o):(.text+0x355): undefined reference to `__imp_pcre2_code_free_8'
D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../lib\libpcre2-posix.a(libpcre2_posix_la-pcre2posix.o):(.text+0x42d): undefined reference to `__imp_pcre2_match_8'
D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: D:/a/_temp/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../lib\libpcre2-posix.a(libpcre2_posix_la-pcre2posix.o):(.text+0x4e5): undefined reference to `__imp_pcre2_get_ovector_pointer_8'
collect2.exe: error: ld returned 1 exit status

As you can see, pcre2-8 is loaded but the linker seems to have problem :(
Any clew about where to search for a solution?
As I said, it worked perfectly last week.

This is an typical issue with static library in mingw package. I can try to fix this issue.


Keep curl package for health-checks

If using docker-compose.yml healthcheck, the normal is to use curl to check app health.
See: https://docs.docker.com/compose/compose-file/#healthcheck

Thanks for your contribution!


[WIP]fix: build failed at 1.10.x version(#63)

Codecov Report

Merging #64 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #64   +/-   ##
=======================================
  Coverage   89.62%   89.62%
=======================================
  Files           5        5
  Lines         501      501
=======================================
  Hits          449      449
  Misses         36       36
  Partials       16       16

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7fe2f9a...aa0a9ea. Read the comment docs.


Create Standardized Local Development Environment

I was talking with Jorge in the discord and getting a standardized local development environment set up would make it much easier to onboard folks. The biggest hurdle I found working with this project is not having an easy way to configure a development environment using automation.
Current process:

Create Local Container Registry
Download ISO for Silverblue and install on your VM
Add configuration information to point to local registry
Rebase onto your locally built container image

Proposed Process:

Install Ansible
Run Ansible-Playbook
Development environment is up

What will the playbook do?

Download CoreOS Image based on your hypervisor and use ignition file to rebase on your local repository

Anyone have any thoughts on this?

cc @ublue-os/approver @ublue-os/member

This sounds pretty similar to https://github.com/ublue-os/forge except without the PXE boot stuff.

I would be interested to see what you come up with, as I am not seeing how this is a "development environment". Happy to have more explained to me though. :-)
I do think it sounds interesting as an easy way to get a local container registry running. That can be very valuable since local builds avoid costly/slow downloads from GHCR.  As I see it, this would still require the user/developer to be doing manual podman build with appropriate build-args to run all the correct options, and then podman push, though obviously it could be scripted.
So, that's helpful, but IMO, the more challenging problem is the Github Actions workflows. We rely on them heavily, and they are often a pain point.
I've done some playing with https://gitea.com/gitea/act_runner, a fork of https://github.com/nektos/act ...  At least in the gitea fork, there's some problems related to cgroups, when trying to run our Actions workflows under act_runner in nested containers.  If this could be solved so act could run our workflows locally, then we'd have a pretty huge benefit of being able to run a full set of local builds for dev/test.

I'm going to revisit this issue with some new ideas I've had. This project is exactly the sort of thing that I was hoping would exist one day:
https://github.com/osbuild/bootc-image-builder
It's not quite ready, but the idea I have here is once it can support local container registries the workflow for onboarding someone new would look like this:

Run First Time Setup Ansible Playbook (or shell script if we prefer that)

This would setup the following: (supported on Linux only for the time being)

Local container registry with the project you want to develop on.
Create a qcow2 image and make it available inside of Virt Manager
Anytime you make any changes to the container registry, your virtual machine should see those changes and you can reboot it to reflect the changes.

I know most folks like to just use containers to develop this project, but VMs are awfully nice for troubleshooting UI related issues or testing things related to that.


Add an option to report cucumber scenario steps as allure steps

Add an option to report cucumber scenario steps as allure steps
Fix pending tests issues for jasmine.

Fixes for issues
https://github.com/webdriverio/wdio-allure-reporter/issues/97
https://github.com/webdriverio/wdio-allure-reporter/issues/95

Yes, I had the same thoughts to enable it by default for cucumber users and finally decided that we should not break current users reports and make it optional.
Let give some feedbacks and maybe change option default value in future.

Released as v0.6.0


Use React Router Linking on MenuSidebar

Describe your changes and why you are making these changes
Updates menuSidebar to use react-router linking. Pages no longer need to trigger a browser refresh when transitioning from one page to another and now load instantly.
Loom Demo: https://www.loom.com/share/c0312eda788f4e3d96cc36d677cd12ad
Related issue number (if any)
N/A
Checklist before requesting a review

[x] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[x] I have performed a self-review of my code.
[x] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[x] If this is a new feature, I have added unit tests and integration tests.
[x] I have run the integration tests locally and they are passing.
[x] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[x] All features on the UI continue to work correctly.
[x] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

Minor note to double check GH actions as they are failing

Neat! Are these all Links we've been using in our codebase?

@likawind Yes, these are the Links that we've been using in our codebase, but under the hood they use the routing system that React Router does, so instead of triggering page refreshes, we trigger a navigation event instead.


Add minute, hour to it

I love this project, exactly what I need, but could we also please add minute as unit to it? it would be even better!

i'm currently trying to make it possible to add the unit to the value... so u could use 1s, 10m or 5d.
but it may be available in the next larger release.. because i'm currently implementing the option that delayed actions survive a home-assistant restart


new ctor NewLogf() takes nsq-like log func instead of Logger

... to finish up log-level support in nsqd
I wanted to make some use of nsq/internal/lg but

.../src/github.com/nsqio/go-diskqueue/diskqueue.go:17:2: use of internal package not allowed

But wait and see the companion nsq PR, the LogLevel type makes things ugly, it would have been better as an int.

btw, I'm open to better ideas (than copying in nsq/internal/lg)

I don't really care about backwards compat for this library, let's just improve the API and update the existing New

updated. ran "go test" locally, built and ran nsqd for a couple of seconds locally


[FEATURE REQUEST] Cusomtized the output msix file name

msix created: build/windows/runner/Release/flutter_app.msix
is that anywhere can customized it?

Please use the bug report template: https://github.com/YehudaKremer/msix/blob/main/.github/ISSUE_TEMPLATE/bug_report.md


Add gas benchmarks vs reference FunC implementation

These should automatically run in Sandbox the same typical communication scenarios for Tact and FunC implementations and show the consumed gas for both versions, the absolute and relative difference.
Benchmark results

Jetton Version - Gas Consumption
SimpleTransfer
JettonBurn
WalletDiscovery
avg. Factor

FunC reference
0.0099692
0.0053376
0.002827999
1x

Tact
0.0224328
0.010996799
0.006611199
2.22x

Tact without address validation
0.0165316
0.011217199
0.006625198
2.03x

Jetton Version
Gas Consumption

FunC reference
0.001

Tact without constant propagation
0.0225008

Tact with constant propagation
0.0225008

These are unexpected results on all sides.
Check it out @anton-trunov
P.S. You can check GasTests branch with commit, that tests gas consumption.

@anton-trunov The overall results, while not dramatically, are noticeably better. But SimpleTransfer results improved from 2.25x to 1.65x

But according to results, JettonBurn and walletDiscovery became just a little bit, but still worse. I rechecked previous tests on the same machine, same code and same packages (except tact-compiler itself). And I am still getting this results. Looks very strange for me


Feat refresh token prop

Replaces PR #85, Based upon #91
See commit message:

feat(baseConfig): change refreshTokenName option value and add refreshTokenProp (breaking)
BREAKING CHANGE: refreshTokenName option value has been changed from 'refresh_token' to 'token'. The new refreshTokenProp option is set to 'refresh_token' by default (a non-breaking change).

merged


[CLOUD-1167] - Remove deploymentConfig label from all templates

Hey @spolti, it looks like these changes are out of date and can't be merged.  Also, we need to address the eap-amq templates (and probably the decision/process server-amq templates too).  The label application= identifies the application (i.e. all these resources were created for, say, eap-app).  Because of this, we need to use different identifiers for the service selectors, perhaps using multiple labels as @luksa recommended (e.g. application=, component=amq; or application=, component=eap).


SDK-681 Changes SDK Side due to fixes on Circuit V2

https://horizenlabs.atlassian.net/browse/SDK-681

@i-Alex  Thank you for merging!


Day of Week background

Is there a way to change the background color of the days of week section when those are pinned to the top of the calendar?

Hi @SaitamLe - sorry for the delay on this. I think this seems like something that we can support. I'll need to add a new API to configure this on CalendarViewContent, but it should be pretty straightforward. I'll get a change up this week for it.

Looking forward to this change as well :)

und color of the days of week section when those are pinned to the top of the calendar

How did u display three characters in days of week ?

@haffez23
Unfortunately your only option right now is to just fully override the view with your own implementation with withDayOfWeekItemModelProvider which provides Month?, Int parameters with the 2nd being the dayOfWeekIndex that you can index into Calendar to get which day it is and format the value how you want

Thinking this through a bit more, it seems like right now there are 2 options:

Use the default items, which don't allow any customization
Provide your own custom items, which allow full customization

I think there's a middle-ground here, where a customization point is provided for the default items. I agree it seems silly to need to create your own custom items just to change a font size or a background color. Will give this some thought in the next few days.

@bryankeller When I was going to implement my header, what I really wanted was to just access and provide an instance of the default's InvariantViewProperties but the entire struct's hierarchy is internal

@Mordil makes total sense! My current plan is to just expose these publicly. For the default DayView, I'm just going to open source the one I built for Airbnb internally, which has iPad pointer interaction support, configurable haptics, and more 🙂

Hey all, I've got a PR out which exposes configurable default views for month headers, days of the week, and individual days https://github.com/airbnb/HorizonCalendar/pull/140
Should be merged in the next few days - hopefully you can delete some code on your end once this lands! 🤞

Merged! v1.10.0 contains a public DayView, DayOfWeekView and MonthHeaderView.


Add a Instagram Clone

I want to add an instagram clone to this website clone list. The clone site will look like this -
I am using HTML, CSS, JS, ReactJS to build this.

Can you assign me under GSSOC'22.

Already assigned #56