text:
npm install esl

npm WARN package.json esl@0.0.1 No description
npm WARN package.json esl@0.0.1 No repository field.
npm WARN package.json esl@0.0.1 No README data
npm WARN package.json esl@0.0.1 No license field.
npm WARN install Refusing to install esl as a dependency of itself

Current version is 5.2.2, what does npm --verbose install esl say?

authors: freeneutron shimaore

repo: shimaore/esl

license: unlicense


text:
Post Date constraint for like/comment

It would be great if the bot has the ability to limit likes/comments to posts of a certain age. Example: Only like 1 post per account if it was posted in the last 7 days. No one wants to like the last post from 2019 🤣

@datslo "It would be great if the bot has the ability to limit likes/comments to posts of a certain age." - that's a good suggestion. It will be added in the next version.

@datslo "It would be great if the bot has the ability to limit likes/comments to posts of a certain age." - that's a good suggestion. It will be added in the next version.

was this feature added? I think using this feature the other request I made for "recent posts" will also apply

@datslo "It would be great if the bot has the ability to limit likes/comments to posts of a certain age." - that's a good suggestion. It will be added in the next version.

was this feature added? I think using this feature the other request I made for "recent posts" will also apply

This should be quite a useful feature. I will add this

@datslo "It would be great if the bot has the ability to limit likes/comments to posts of a certain age." - that's a good suggestion. It will be added in the next version.

was this feature added? I think using this feature the other request I made for "recent posts" will also apply

This should be quite a useful feature. I will add this

Recently added. Script can now filter posts based on recent n days. (use option -il or --inlast)

source: gharchive/issue

authors: ap0l0 datslo shine-jayakumar

repo: shine-jayakumar/insta-likecom-bot

license: MIT

license_type: permissive

license_source: github-api


text:
Add gremots.com

Thanks! :)

What kind of website is it? Unfortunately I can only read Japanese and English.

Squash those two commits into one.

No feedback.

@gremots Request me to reopen this if you're still interested.

source: gharchive/pull-request

authors: gremots shinnn

repo: shinnn/isogram

license: mit

license_source: bigquery


text:
Failed in Ble Characteristics.Notify()  after upgrading to 1.0.0.531

IF YOU DON'T ANSWER THIS TEMPLATE - THE BOT WILL AUTOMATICALLY CLOSE YOUR ISSUE!
Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[ ] iOS
[X] Android
[X] UWP
[ ] watchOS
[ ] tvOS
[ ] Tizen
[ ] .NET Standard

Feature Library

[ ] Core
[X] BluetoothLE
[ ] Beacons
[ ] Locations
[ ]
HTTP Transfers
[ ] Notifications
[ ] Sensors

Version of Library
1.0.0.531
Version of OS(s) listed above with issue
Windows10, Android 8.1
Steps to Reproduce

Expected Behavior
First of all thanks for that great work - I'm recently developing a project with Shiny framework.
I had a working code with 1.0.0.484 release. After upgrading to 1.0.0.531 - I need to replace RegisterAndNotify invocation of IGattCharacteristics with Notify() - which is fine - as the latest commits(dated 16 Dec) entitled 'Simplifying BLE' suggests. I have not updated anything else.  but no more reading data from a GattCharacteristics. I subscribed it the same way I did before (similar to ShinySamples) - but do not receive anything.
It is now very hard for me to present any meaningful bug report for why this happens. Everything else is same - just upgraded the package. Is it possible that I missed a related behavioral change that I did not adjust my code or is it some general issue?
I'm sorry for not being more specific.
In case it is relevant I can only note the following: after upgrading the built failt in UWP project (not in Android though) because of an AppManifest error due to UWP Background task entry point validation error. I added ActivatableClassId="Shiny.Support.Uwp.ShinyBackgroundTask" for InProcessServer to .appxmanifest file to fix build error.
Actual Behavior
I have adjusted the method name only - and expect to see the same behavior. But no more Characteristics reading.

Same issue for me.

@pehlivan38 There are breaking changes and bugs.  It will happen.  Please add code to show what you are doing.
@hudaIT "me too"'s are not helpful.  They only add noise - no more in the future please.

@aritchie  To make sure I do not waste your time I tried several things, checked for package dependencies but not able to succeed. So here is what I can do to help you in identifying bug:
I will share a simple project that I created back in September to see what I can do with ShinyBle, This is basically your ShinySamples with only BleCentral but with very limited dependency on any other libraries/frameworks. I made it public on Github and made it testable for the bug. (https://github.com/pehlivan38/BlePrototypeBasedOnShiny)
The project is a very simple&stupid one, just to reproduce bug and served me to understand how Shiny works. It does not even read/write - but just registers a GattCharacteristics with Notify. It works on UWP and Android (never tried for IOS)
Steps to reproduce bug:

The project depends on Version 1.0.0.484-beta. And it works perfectly. You may want to double-check. Scan, Connect and then click on a service with Read/Notify capability. Then notify from a peripheral - you will see the first byte as value. I was using a peripheral simulator for battery status - so i was happy with single byte value display. (on your first run, you may need to Stop Scan after your first click on Start - and then Re-Scan again - there is a flaw in UI update which I ignored) The code is a very stupid one - selecting any other service also calls for ToggleNotify method - I'm not sure with the response though.

Just upgrade the package to Version 1.0.0.531. You will get a compiler error in GattCharacteristicViewModel line 69. replace RegisterAndNotify with Notify since this is required by the latest version.

After running the project. Scan/Connect works as it is supposed to - but when you click on a service with Read/Notify capability. It does not enable the notifications on the peripheral (at least on both my simulator and a real device that I'm working on) hence it does not read anything.

I hope it helps...

Notify does seem to be working fine on Android.  UWP is currently not ready for testing at this time.  Since the sample is essentially a copy of my test code, it doesn't really qualify for a reproducible test case.

authors: aritchie hudaIT pehlivan38

repo: shinyorg/shiny


text:
Using openshift-pipelines/setup-tektoncd Action

Changes
Adopting openshift-pipelines/setup-tektoncd action in order to setup Tekton Pipelines and the Container Registry.
Preparing the release v2 with renamed inputs, following GitHub Action best practices and introducing feature_flags input to power up shipwright-io/triggers end-to-end testing using CustomRun instances (Tekton Custom Tasks).
Submitter Checklist

[x] Includes tests if functionality changed/was added
[x] Includes docs if changes are user-facing
[x] Set a kind label on this PR
[x] Release notes block has been filled in, or marked NONE

Release Notes
Renaming inputs to use underscore, instead of dashes. Please consider documentation to set up the inputs accordingly.

Introducing `feature_flags` to set Tekton Pipeline feature flags toggles.

/assign @SaschaSchwarze0

repo: shipwright-io/setup


text:
Shirasagi Job (仮称)

非同期処理・バックグラウンド処理。
現在は音声合成しか利用予定がないけど、汎用的に作成した。
個人リポジトリ sunny4381/shirasagi at voice-dev で開発中。

課題
現在、把握している課題。

管理画面との統合。

管理者が Stop / Start をやりたい。

基本的な使い方
Job の例
app/models の下にジョブクラスを作成する。
$ vi app/models/example_job.rb

class ExampleJob
  include Job::Worker

  public
    def call(id)
      # put your business logic here
      puts "id=#{id}"
    end
end

Registering a Job
Job クラスの call_async(...) メソッドを呼び出すと Job が登録される。
$ bundle exec rails c
Loading development environment (Rails 4.1.6)
irb(main):001:0> ExampleJob.call_async("xyz")
=> #<Job::Model _id: 44, created: 2014-12-14 08:19:31 UTC, updated: 2014-12-14 08:19:31 UTC, text_index: nil, user_id: nil, id: nil, name: "job:model", state: "stop", interrupt: nil, started: nil, closed: nil, total_count: 0, current_count: 0, logs: [], pool: "default", class_name: "ExampleJob", args: ["xyz"], priority: 1418545171, at: 1418545171>

Execute Job
Rake タスク job:run を実行する。
$ bundle exec rake job:run
taks.id=44, task.class_name=ExampleJob, task.args=["xyz"]
id=xyz
Completed Job 44 in 18.395877000000002 ms

call_async(...) メソッドの引数は、call(...) メソッドに渡され、ビジネスロジックが実行される。
Advanced
Scheduled Job
Sidekiq 風の Scheduled Job をサポートしている。call_in(interval, ...) メソッドを呼び出す。
$ bundle exec rails c
Loading development environment (Rails 4.1.6)
irb(main):001:0> ExampleJob.call_in(3.minutes.from_now, "xyz")
=> #<Job::Model _id: 46, created: 2014-12-14 08:27:38 UTC, updated: 2014-12-14 08:27:38 UTC, text_index: nil, user_id: nil, id: nil, name: "job:model", state: "stop", interrupt: nil, started: nil, closed: nil, total_count: 0, current_count: 0, logs: [], pool: "default", class_name: "ExampleJob", args: ["xyz"], priority: 1418545658, at: 1418545838>

Rake タスク job:run を実行して Job を実行する。
$ bundle exec rake job:run
# nothing occur
$ sleep 3m
$ bundle exec rake job:run
taks.id=46, task.class_name=ExampleJob, task.args=["xyz"]
id=xyz
Completed Job 46 in 14.703932 ms

3 分後に Job を実行するように指定したので、初回の job:run では、何も起きない。
3 分待機した後、job:run を実行すると、登録した Job が実行される。
Limit Job Counts to Register
既定では Job の登録数は無制限であるが、制限することができ、音声合成 Job は、最大 100 件に制限している。制限は config/job.yml で設定する。
vi config/job.yml

# job

production: &production
  fork: 2
  poll:
    # polling pools
    - 'default'
    - 'voice_synthesis'
  pool:
    # individual pool config
    voice_synthesis:
      # voice synthesis job is limited to 100 jobs
      max_size: 100

test:
  <<: *production

development:
  <<: *production

class Voice::SynthesisJob では、pool を次のように指定している。
class Voice::SynthesisJob
  include Job::Worker

  self.job_options = { 'pool' => 'voice_synthesis' }

  public
    def call(id)

    ...

SynthesisJob.call_async(...) が呼び出されたら Job request は、voice_synthesis に登録される。
Concept

sidekiq を参考。
Job のパラメータは MongoDB に保存する。

call() メソッドのパラメータとして使用できるのは、Fixnum, String などの MongoDB に保存できる型のみ。
Job の引数はなるべく単純であるべき。
Job を実行するのに複雑なパラメータが必要な場合は、そのパラメータをモデルに保存し、モデルの id を Job の引数とすべき。

Schedule 機能は限定的。

定期実行したい場合（cron のような機能）は、Sidekiq と同様、whenever や clockwork を使用する。

マルチ・プロセス。

Sidekiq と異なり、マルチスレッドではなく、fork して Job を実行。
ただし、fork するのも万能ではなく、今後の検証で問題が見つかった場合は、仕様を変更する可能性あり。

非デーモン化。

Sidekiq とは異なりデーモン起動しません。rake job:run を実行します。
rake job:run は、2 重起動防止措置が講じられており、何回実行しても 1 つしか起動しません。

内部実装詳細
Job 実行情報
call_async(...) メソッドを実行すると、Job の実行情報が ss_tasks に登録される。

id
name
state
pool
class_name
args
priority
at

44
job:model
stop
default
ExampleJob
["xyz"]
1418545171
1418545171

priority は Job の優先度を表す。値が小さいほど優先度が高い。
at は実行してもいい日時を UnixTime 形式で。at >= Time.now.to_i が真のレコードを選択。

rake job:run
rake job:run 内で、ss_tasks の次のレコードをロック。

id
name
state
current_count

| job:service | stop  | 0             |

ロックすると次のようになる。

id
name
state
current_count
started

| job:service | running | 1             | ISODate("2014-12-14T08:31:11.268Z") |

current_count を atomic にインクリメント。

find_and_modify({ '$inc' => { current_count: 1 } }, ...) を使用。

インクリメントの結果、閾値（= 1）以下なら実行可。それ以外なら実行不可。

実行不可の場合、current_count をデクリメント。
実行可の場合、state を running に変更、started を Time.now に変更。

config の fork:

0 の場合、fork せずに、カレントプロセスで 1 多重で Job を実行。
0 以外の場合、指定数だけ fork。fork 内で Job を実行。

rake job:run が終了すると、ss_tasks のレコードは次のようになる。

id
name
state
current_count
total_count
started
closed

| job:service | stop    | 0             |          +1 | ISODate("2014-12-14T08:31:11.268Z") | ISODate("2014-12-14T08:31:27.316Z")

Job 実行情報の取得

poll に設定されたプール名を順に poll。

まず "default" を poll。
"default" が空になると "voice_synthesis" を処理。
"voice_synthesis" が空になると終了。

started が nil のレコードを atomic に選択。

find_and_modify({ '$set' => { started: Time.now }}, ...) を使用。

Job のインスタンス化

class_name で指定したクラスを String#constantize し、Class オブジェクトを取得。
取得した Class オブジェクトの new メソッドを呼び、インスタンス化。

インスタンス化した Job の call() メソッドを呼び出す。

Job 実行後
ss_tasks に登録した Job の実行情報は削除される。

id
name
state
pool
class_name
args
priority
at

44
(removed)

find_and_modify についての考慮点

atomic に read と save が行える。ロックする際に便利。
MongoDB の公式文書を読むと：

Database ごとの Reader Writer Lock。
（2.2 では mongod ごとの Reader Writer Lock だったが改善された）
Writer Greedy 戦略。

MongoDB の公式文書を読む限り、find_and_modify() が特別性能が悪いというわけではなく、save() と同程度と推測。大規模展開時でも性能面の問題はなさそうであった。
ただし、

ロックに失敗しても無駄に複数回実行されるだけで実害は少ない。
実害は少ないことから、単純に read して save しても可だとは思う。

ジョブの実行結果確認画面
ジョブ実行時にエラーが発生した場合、ログを見ないといけないのでは不便すぎる。
ジョブの実行結果を管理画面で見えたほうが、運用時の手離れがいいだろう。
#105 で「音声ファイルの作成状況がみれたらよい」という要望がある。
これを読み替えて「ジョブの実行結果がみれたらよい」とすることもできる。
システム管理者の管理画面でのみジョブの実行結果が見えるのでは不便だ。
サイト管理者の管理画面でも（権限があれば）ジョブの実行結果が見えたほうがいい。
すべてのジョブはサイトに紐づけられるか？
現在構想中のジョブは、サイトと紐づけることができる。
実装の都合を考慮すると、モデルがサイトに関連するかどうかを表す SS::Reference::Site クラスは、
現在のところ site_id が必須である。
※モデルがユーザに関連するかどうかを表す SS::Reference::User クラスは、user_id を省略できるのとは対照的だ。
現在見えている範囲と、実装の都合を考えて、ジョブはサイトに紐づけることができるものとし、サイトを必須としようと思う。
ジョブ登録時にサイト必須
上の call や call_in メソッドでは、サイトを省略できるが、この仕様を改め、サイトを必須とする。
例:
ExampleJob.call_async(@cur_site, "xyz")
ExampleJob.call_in(@cur_site, 3.minutes.from_now, "xyz")

再: ジョブの実行結果確認画面
システム管理者は、サイトに関係なく全ジョブの実行結果が見える。
サイト管理者は、サイトに関連付けられたジョブの実行結果が見える（ただし権限が必要）。

マルチ・プロセス改マルチ・スレッド
fork して job を実行すると、mongo が duplicate key という謎のエラーが履いたので断念。
マルチ・スレッドで job を多重に実行するようにした。
マルチ・スレッドで job を実行すると、今度は、Rails （の一部）がマルチスレッドに対応していないみたいで、"Circular dependency detected while autoloading constant XXXX" という例外を吐いて job がエラーになる。
上記の例外は class や module の autoloading 機構で発生している。
この例外を回避するため、現時点では job クラスで明示的に必要な class や module を require しなければならない。

Job をサイトに関連付ける方法
次のように async_call にブロックを渡すと、Job が得られる。
Job の site_id 属性を適切に設定することで、Job をサイトに関連付けることができる。
ExampleJob.call_async("xyz") do |job|
  job.site_id = @cur_site.id
end

Job をサイトに関連付けると何が嬉しいかというと、管理画面でジョブの実行履歴が見えるようになる。
将来の課題
Job はサイトと関連付けなくても実行できる。サイトと無関係な Job の実行履歴を、システム管理者の管理画面で見えるようになるべきだと思うが、現在は未対応。
Job はサイトと関連付けるようにしてください。

仕様変更(再): マルチ・スレッドをマルチ・プロセスに変更
マルチ・スレッドで job を実行すると、今度は、Rails （の一部）がマルチスレッドに対応していないみたいで、"Circular dependency detected while autoloading constant XXXX" という例外を吐いて job がエラーになる。
この点を嫌気。
もう一度、マルチ・プロセス方式を検討し、今度はうまくいきそうな方法を見つけた。

プルリクをマージしたのでクローズします。
今後、問題が発生したら別チケットで対応します。

repo: shirasagi/shirasagi


text:
Update xlswriter@8.1

Build xlswriter@8.1

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-extensions


text:
swoole@7.2: Rebuild with openssl@3

swoole@7.2: Rebuild with openssl3

:beers: @BrewTestBot has triggered a merge.


text:
Update imap@8.4

Build imap@8.4

:beers: @BrewTestBot has triggered a merge.


text:
Update php@8.1

Build php@8.1

:shipit: @shivammathur has triggered a merge.

repo: shivammathur/homebrew-php


text:
Update php@8.3-debug

Build php@8.3-debug

:beers: @BrewTestBot has triggered a merge.


text:
Fix iPhone playback

This change broke playback on iPhone, this change should fix it and perform as intended.

If a format is specified then no subsequent judgement should be made
For example, https://xxx.m3u8 can also return other types of video formats

const defaultMatcher: hlsPluginOptions['matcher'] = (video, source) =>
  (!(
    Boolean(video.canPlayType('application/x-mpegURL')) ||
    Boolean(video.canPlayType('application/vnd.apple.mpegURL'))
  ) &&
    source.format === 'm3u8') ||
  ((source.format === 'auto' || typeof source.format === 'undefined') &&
    /m3u8(#|\?|$)/i.test(source.src))

https://github.com/shiyiya/oplayer/commit/e5bb7c8a7fb1d44e8d42f2061cbda34c4fc0be20#diff-873ea15f9df2b309f4d8078f1e958bfd9ec7fd708e354b50eee44121001b506dR18
set format auto | undefined

authors: phpb-com shiyiya

repo: shiyiya/oplayer


text:
多开

问下大佬，这个支持多开吗

可以自行多开

authors: dandyzzc shiyutim

repo: shiyutim/tickets


text:
npm-sass / gyp errors when running ./psh.phar install on ubuntu 16.04

   gyp ERR! System Linux 4.15.0-1044-gcp         gyp ERR! command "/usr/bin/node" "/app/platform/src/Storefront/Resources/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose " "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="         gyp ERR! cwd /app/platform/src/Storefront/Resources/node_modules/node-sass         gyp ERR! node -v v11.15.0         gyp ERR! node-gyp -v v3.8.0         gyp ERR! not ok          Build failed with error code: 1         npm ERR! code ELIFECYCLE         npm ERR! errno 1         npm ERR! node-sass@4.12.0 postinstall:node scripts/build.js         npm ERR! Exit status 1         npm ERR!          npm ERR! Failed at the node-sass@4.12.0 postinstall script.         npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
 Unable to save binary /app/platform/src/Administration/Resources/administration/node_modules/node-sass/vendor/linux-x64-67 : { Error : EACCES: permission denied, mkdir '/app/platform/src/Administration/Resources/administration/node_modules/node-sass/vendor'             at Object.mkdirSync (fs.js:773:3)             at sync (/app/platform/src/Administration/Resources/administration/node_modules/mkdirp/index.js:71:13)             at Function.sync (/app/platform/src/Administration/Resources/administration/node_modules/mkdirp/index.js:77:24)             at checkAndDownloadBinary (/app/platform/src/Administration/Resources/administration/node_modules/node-sass/scripts/install.js:1 14:11)             at Object.<anonymous> (/app/platform/src/Administration/Resources/administration/node_modules/node-sass/scripts/install.js:157:1 )             at Module._compile (internal/modules/cjs/loader.js:816:30)             at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10)             at Module.load (internal/modules/cjs/loader.js:685:32)             at Function.Module._load (internal/modules/cjs/loader.js:620:12)             at Function.Module.runMain (internal/modules/cjs/loader.js:877:12)           errno: -13,           syscall: 'mkdir',           code: 'EACCES',           path:

npm install -g npm@latest
helped with it, those issues happen with npm version 6.10 that comes with the docker setup

sudo npm install --unsafe-perm for some reason also helps, why do i need unsafe permissions to simply install packages without errors?

Ok so I could reproduce this issue, when you run bin/setup the first time, and then have to rerun it, you might encounter permission errors on linux, after i did sudo chown -R $USER:$USER /project/location it went through to "All commands successfully executed!" :)

Since you resolved the Error yourself I close this due to inactivity.

authors: BogdanChayka pantrtxp

repo: shopware/platform


text:
refactor: Simplify configuration logic for the product slider cms element

1. Why is this change necessary?
Easier understanding of the template, and no replace_recursive call.
2. What does this change do, exactly?
Simplify the logic of the product slider configuration.
3. Describe each step to reproduce the issue or behaviour.
No issue, just refactoring.
4. Please link to the relevant issues (if any).
-
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-20564
Please use this issue to track the state of your pull request.

Many thanks for your contribution! 🚀


text:
NEXT-7442 fixes #851 add guest pill to customer list and detail view …

…next to the customer name

1. Why is this change necessary?
Boost Day Task in order to make guest orders visible
2. What does this change do, exactly?
It displays a small pill for guest users next to the name in the list and detail view of customers.
3. Describe each step to reproduce the issue or behaviour.
Place an order as guest and click on customers in the administration to see the guest customer
4. Please link to the relevant issues (if any).
https://github.com/shopware/platform/issues/851
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfill them.

QA approved. :heavy_check_mark:

@mitelg @raknison formatted and updated, thanks

@raknison should be good now

authors: GitEvil MDSLKTR


text:
Multiple shopping experiences for one category (6h)

We can assign only one shipping experience for one category. Its also not translate able. We need that to have for each sales channel a own shopping experience. Its also a wanted sw6 core feature.
So we should implement that in Core

Please overwrite at this section also the Meta Information for the home controller to use the Sales Channel Name

repo: shopwareDowntown/portal


text:
update

update

update

repo: showsmall/websocket


text:
Add deep clone methods to VToken

As the title says. Requested by @w7rus.

Json.NET supports this via myjtoken.CloneToken().

Resolved with 3abd1792552ed32ad17086c4c77d19f9074efed2.


text:
Can't get the suppression to work in Rider

I can't figure out how to get this suppression to work in Rider. Is it so that it will not work at all because Rider doesn't support analyser suppressions?
I installed the NuGet package. That by itself didn't do anything, as expected. I use records.
Modifying .editorconfig to suppress records, also did nothing.
Test code as follows:
abstract record Command
{
    public sealed record Create : Command;

    public sealed record Update : Command;
}

public class UnitTest1
{
    [Fact]
    public void Test1()
    {
        Command command = new Command.Create();

        // NuGet package is installed
        // .editorconfig is modified to suppress on records
        // CS8509 warning still not suppressed
        var action = command switch
        {
            Command.Create c => "Create",
            Command.Update u => "Update",
        };
    }
}

It's a shame, really. Was looking forward to fix this silly compiler problem.
Would it be possible to do this the other way around? To create an analyser with with a custom id, like XX8509 to replace CS8509, and have that to raise a warning when the switch expression doesn't handle all cases on a closed type hierarchy?

Hi Thomas,
TL;DR: Rider does not support diagnostic suppressors and no-one really seems to care. I will not create a replacement analyzer, because that is A LOT more work.
Also note that even in VS your test code would not trigger suppression because your Command record's constructor is not private.
The long version:
unfortunately, it seems that Rider does not support DiagnosticSuppressors. I link to the corresponding issue in the README.
Since I created this, it has become apparent that for some reason diagnostic suppressors are not supported by many tools, such as Rider, VS Code through Omnisharp and even Visual Studio for Mac.
They are really only supported by Visual Studio for Windows.
So yes, I have thought about the workflow you suggest to disable the three diagnostics altogether and issue new ones instead.
This brings of course the burden of making sure that the new analyzer is at least as good as the one it aims to replace.
This means constant maintenance in the face of new language features etc..
With the current approach the suppressor does not have to worry about any of that because it just does nothing when it is not sure what to do.
It will never make anything worse.
On the contrary, the suppressor automatically benefits from improvements made to the built-in analyzers.
This is also the reason why I will not change anything.
There already are analyzers that try to replace the existing exhaustiveness checks, like (https://github.com/sundews/Sundew.DiscriminatedUnions) and probably others.
Last I checked, they did lack important features though, like proper NRT support, which is why I started this project in the first place.
I hope you can find or create something that fits your needs :-)

Closed due to inactivity

authors: shuebner thomaseyde


text:
首段无法自动缩进

如Typst issues#331所描述，Typst上游首段缩进问题尚未解决，如果需要首段缩进，需要手动在段落开头使用 #h({length}) 添加缩进。
以缩进两个字符为例，需要手动在段落开头添加 #h(2em).

我的项目 https://github.com/lucifer1004/pkuthss-typst 首段缩进似乎没问题，但是另外的项目里确实遇到了。猜测是我魔改的 heading 使得首段不再是首段了。

参照这个项目，在标题后面添加了空白段
#show heading: it =>  {
  if it.level == 1 {
    set align(center)
    set text(font:heiti, size: font_size.xiaoer, weight: "regular")
    it
    par(leading: 1.5em)[#text(size:0.0em)[#h(0.0em)]]
  } else if it.level == 2 {
    set text(font:heiti, size: font_size.sihao, weight: "regular")
    it
    par(leading: 1.5em)[#text(size:0.0em)[#h(0.0em)]]
  } else if it.level == 3 {
    set text(font:heiti, size: font_size.xiaosi, weight: "regular")
    it
    par(leading: 1.5em)[#text(size:0.0em)[#h(0.0em)]]
  }
}

使得首段不再是首段了，所以"首段"可以缩进了

repo: shuosc/SHU-Bachelor-Thesis-Typst


text:
link for pretrained model 404

Would you please provide a new link for pretrained model since present link is 404.

The links to download the model can be found here.

The links to download the model can be found here.

hi, the link you put here is the webpage of the challenge. I can't find the pre-trained model there. Can you please point it out where to find it? Or the updated pre-trained model link.
Thanks.

authors: Zealoe ulatekh wayneszq


text:
Added glowing-animated-button in buttons folder

What is the change?
Added Glowing Animated Button files in glowing-animated-button folder in buttons directory. The files included are: index.html, index.css and readme.md .
Related issue?
closes: #46
How was it tested?
The code was tested using Live Preview in VSCode and also with Chrome and Firefox web browsers and was found to be working perfectly fine.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelineswhile contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Have you tested the code before submission?
[x] Have you formatted your code ? (You can use any html,css beautifier)
[x] My changes generates no new warnings.
[x] I'm Hacktoberfest'21 contributor.
[x] I have commented my code, particularly in hard-to-understand areas.

GIF/video of the working of component you created:

@siddhi-244 I have added my component in the general readme as told. Kindly approve the pull request. Thank you.

@siddhi-244 I have added my component in the general readme as told. Kindly approve the pull request. Thank you.

You have added button also.

@siddhi-244 I have added my first component 'animated glowing button' for PR #56  from apkbranch, and 'animated search bar' for PR #63
from apk1branch.


text:
INVALID_CALLBACK_URL_ERROR when deployed on cyclic

Environment

Operating System: Linux
Node Version:     v16.15.1
Nuxt Version:     3.6.1
Nitro Version:    2.5.2
Package Manager:  npm@8.11.0
Builder:          vite
User Config:      runtimeConfig, modules, auth
Runtime Modules:  @sidebase/nuxt-auth@0.6.0-beta.3
Build Modules:    -

Reproduction
Github repo
Vercel deployment
Cyclic deployment
Describe the bug
With both versions 0.5.0 and 0.6.0-beta.3 it works correctly locally and on Vercel, but when deployed on Dyclic, the project can't start with INVALID_CALLBACK_URL_ERROR. See log below.
Additional context
I think this issue was similar but closed due to lack of reproduction.
The important parts of my code:

.env

NEXTAUTH_SECRET       = 'my-auth-secret'
AUTH_ORIGIN           = 'https://my-domain.com'
FAUNA_SECRET          = 'fauna-secret'
MARANGADU_USER        = 'my-email'
MARANGADU_PASSWORD    = 'email-password'
MARANGADU_HOST        = 'email-smtp-server'
MARANGADU_PORT        = 465
MARANGADU_FROM        = 'my-email'

packages.json

  "devDependencies": {
    "@sidebase/nuxt-auth": "^0.6.0-beta.3",
    "nuxt": "^3.6.1"
  },
  "dependencies": {
    "faunadb": "^4.8.0",
    "nodemailer": "^6.9.3"
  }

nuxt.config.js

  modules: [
    '@sidebase/nuxt-auth'
  ],

  auth: {
    provider: {
      type: 'authjs',
      addDefaultCallbackUrl: true
    },
    origin: process.env.AUTH_ORIGIN,
    baseUrl: `/api/auth`,
    addDefaultCallbackUrl: true,
    globalAppMiddleware: {
      isEnabled: true,
      allow404WithoutAuth: true,
      addDefaultCallbackUrl: true
    },
  }

server/api/auth/[...].js

const client = new faunadb.Client({
  secret: faunaSecret,
  scheme: "https",
  domain: "db.fauna.com",
  port: 443,
});

export default NuxtAuthHandler({
  secret: nextAuthSecret,
  providers: [
    EmailProvider.default({
      id: 'magic-link',
      name: 'send magic link by email',
      type: 'email',
      server: {
        host: marangaduHost,
        port: marangaduPort,
        auth: {
          user: marangaduUser,
          pass: marangaduPassword
        }
      },
      from: marangaduFrom,
      maxAge: 60 * 60
    })
  ],
  adapter: myLoginAdapter(client)
});

server/middleware/auth.js

import { getServerSession } from '#auth';

export default defineEventHandler(async (event) => {

  const targetUrl = event.req.url;
	const securedUrls = '/api/dashboard/';

  if (targetUrl.startsWith(securedUrls)) {

    const session = await getServerSession(event);

    if (!session) {
      throw createError({
        statusMessage: 'Unauthenticated',
        statusCode: 403
      });
    };

    event.session = session
  }
});

pages/login.vue

<script setup>
definePageMeta({
  auth: {
    unauthenticatedOnly: true,
    navigateAuthenticatedTo: `/dashboard`,
  },
});

const { signIn } = useAuth();

const email = ref(null);

const signInHandler = async () => {
  try {
    await signIn('magic-link', {
      email: email.value,
      callbackUrl: `/dashboard`,
    });
  } catch (error) {
    alert(error);
  }
};
const { query } = useRoute();
</script>

<template>
  This page query: {{ query }}
  <NuxtLayout>
    <form @submit.prevent="signInHandler">
      <input v-model="email" />
      <input type="submit" value="Send email" />
    </form>
  </NuxtLayout>
</template>

Logs
GET/api/auth/session?callbackUrl=https://outrageous-ox-hat.cyclic.app/__nuxt_error?url=/%26statusCode=500%26statusMessage=Internal%2BServer%2BError%26message=%2B(500%2BInternal%2BServer%2BError%2B(https://outrageous-ox-hat.cyclic.app/api/auth/session?callbackUrl=https://outrageous-ox-hat.cyclic.app/))%26stack%26data=%25257B%252522message%252522:%252522There%2Bis%2Ba%2Bproblem%2Bwith%2Bthe%2Bserver%2Bconfiguration.%2BCheck%2Bthe%2Bserver%2Blogs%2Bfor%2Bmore%2Binformation.%252522%25257D
 Request Headers
2023-06-30 21:24:35.191: [next-auth][error][INVALID_CALLBACK_URL_ERROR]
https://next-auth.js.org/errors#invalid_callback_url_error Invalid callback URL. Received: https:// InvalidCallbackUrl: Invalid callback URL. Received: https://
    at assertConfig (/var/task/.output/server/node_modules/next-auth/core/lib/assert.js:53:12)
    at AuthHandler (/var/task/.output/server/node_modules/next-auth/core/index.js:77:52)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///var/task/.output/server/chunks/nitro/node-server.mjs:859:24
    at async Object.handler (file:///var/task/.output/server/node_modules/h3/dist/index.mjs:1284:19)
    at async Server.toNodeHandle (file:///var/task/.output/server/node_modules/h3/dist/index.mjs:1359:7) {
  code: 'INVALID_CALLBACK_URL_ERROR'
}
500 09:24:35.191 (0.055s)
 Response Headers
 Response Payload
{
  "message": "There is a problem with the server configuration. Check the server logs for more information."
}

@learntheropes did you get a solution for this?

No. I moved to a different hosting provider.

Thanks, but I just realized that issue pops up in version 0.6 and not 0.5

Closed due to an old version. If anyone is still experiencing this issue, please check if it still exists in 0.8.0 and that the module has been setup using the new docs: https://auth.sidebase.io

authors: kennedyngigi4 learntheropes zoey-kaiser

repo: sidebase/nuxt-auth


text:
Icon Request: Disabled camera

[ ] Bug report
[x ] Feature request
[ ] Documentation issue or request

Current behavior
None
Expected behavior

I would like to order a disabled version of the camera icon. The application which we develop handles cameras and we need an icon which represents the disabled state of the camera.
Something similar like this one, but of course in an IX environment.
https://www.iconfinder.com/icons/4926490/camera_disable_disallow_no_photography_icon

OK, will be added with next release.
Name:

photo-camera-cancelled(-filled)

Related icons will also be added:

surveillance-cancelled(-filled)
webcam-cancelled(-filled)

Thank you, and also for the quick answer! When will the new release takes place?

Icons are now available

authors: dorareviczki nuke-ellington silviowolf

repo: siemens/ix-icons


text:
add IOT2050 to Blinka (CircuitPython) compatible board list

Hey there,
we ( @TheresaHeim and I ) want to add the IOT2050 to the compatible list of boards of Blinka: https://learn.adafruit.com/circuitpython-on-raspberrypi-linux/more-to-come
I²C and SPI should be functioning out of the box with the default system libraries for them.
Adding GPIO and PWM would be great to have it working on top of MRAA, which was already suggested here:
https://github.com/adafruit/Adafruit_Python_GPIO/pull/46#issuecomment-428752678
And a PR here (was rejected as they were moving forward to Blinka):
https://github.com/adafruit/Adafruit_Python_GPIO/pull/68
This would enable a variety of code examples to use with common adafruit breakout boards!
Anybody willing to support us on our journey here? :)
Cheers

Would surely be nice!
On first sight, this indeed looks like a generic task, mapping of mraa's python binding to blinka. Or do you already see something missing in meta-iot2050 and its mraa extension?

Hey @jan-kiszka , thanks for your fast answer!
Yes, I fully agree on this. I do not see anything that would be dependent only on the IOT2050.
But I think that you cannot easily integrate all mraa compatible boards to Blinka, which reflects already in individual board_identifiers for the basic and advanced version of the IOT2050.
But this work should be as generic as possible!
(IOT2040 could be added by this as well if desired)
We have to see what easy steps will look like to integrate it. The tutorial is already really user friendly, but @TheresaHeim is completely new to Linux and Python. So this might be a challenge. Would be cool if someone could support us with the nasty bits.. But with MRAA we might be able to skip working with linux internas at all! We'll see how it goes.. 😄
Cheers

Yeah, current mraa support for iot2050 does not cover all bits of the hw, see e.g. #24. But that can be extended later, and what is there would already be useful to expose this way.
i'm not familiar with CircuitPython and Blinka yet, but I try to support from the platform perspective. Just drop your questions or issues.

I have already changed and added the constants and detection codes. Now I am at the point to add the chip file. Which GPIOs are used in the IOT2050 and are they changing?

I have already changed and added the constants and detection codes. Now I am at the point to add the chip file. Which GPIOs are used in the IOT2050 and are they changing? How are the names of the libgpio? Here is an example of another board of pin.py.

You are addressing the GPIO via libgpio, right? That one also incorrectly seems to rely on GPIO numbers. But, as written above, they are conceptually not stable. A mapping like above would break when we move from the TI kernel 4.19 to upstream kernel 5.10.
There is now https://github.com/siemens/meta-iot2050/pull/48 (which I still need to check out...) which addresses that for mraa. If you can use mraa instead of libgpio plus that MR, you would be on the safe side. mraa contains a mapping from I/O pin names to the currently valid GPIO number.

The GPIOs are working now.
But if I try to test an Adafruit Sensor (bme680) I get an Error in the file busio.py: ModuleNotFoundError: No module named "machine".  I have allready installed "machine" and updated blinka, like it was recommended in an other issue. (https://github.com/adafruit/Adafruit_Blinka/issues/263) It´s still not working.

Do you have an idea whats the problem could be?

python2 / python3 confusion? I often install to python[2] by accident when I meant python3/pip3 etc.

I used the right one: python3 -m pip install machine

Check via strace which files are being opened and compare what has been installed. Maybe the local site is not in the python search path.

FWIW, we have now gpiod support in master, and we have named GPIO lines. Maybe that helps also with Blinka.

Still relevant?

Seems this effort stalled.

authors: TheresaHeim gramss jan-kiszka


text:
ROS# does not work when building the project

My OS is: Windows 10
My Unity Version is: Unity 2019.3.5f1
My ROS Distribution is: ROS Kinetic on Ubuntu 16.04 LTS
My Build Target Platform is: Ubuntu 16.04 LTS

Hi there,
I've been trying to communicate from Unity to ROS in several ways:

Clicking play button from the Unity3D app --> The communication works, it connects to rosbridge server and the desired topic can be displayed
Building the project without changing anything from 1) --> I tried to export it for Windows (.exe) as well as for Linux (.x86-64), but none of them worked. Rosbridge server notices there is one new connection, but "rostopic list" does not show the Unity topic.

Steps Taken:
I have tried to replace the Newtonsoft.xml from this page: https://assetstore.unity.com/packages/tools/input-management/json-net-for-unity-11347, which does not work.
I don't understand what's the difference between compiling+building the project and running it from the app.
Desired behavior:
Run the built project (.x86-64) from Linux in localhost to publish and subscribe to other topics from the same computer.

You should change your project to mono & .net 4.x
But if someone replaces  Newtonsoft.Json to JSON .NET it will helpful.
Newtonsoft.Json is bad for cross compile and li2cpp support

You should change your project to mono & .net 4.x
But if someone replaces Newtonsoft.Json to JSON .NET it will helpful.
Newtonsoft.Json is bad for cross compile and li2cpp support

Thank you very much, Andor233, I would've never thought of that, but is finally working. Have a great day!

I'm happy to hear you solved your problem, it takes me much time when I faced the problem, but it just a temporary solution.
Newtonsoft.Json can't work on the platform which doesn't support reflection.
So maybe keep this issue open maybe better?

Hi,
With the recent changes here, one can use .NET JSON serializer instead of Newtonsoft JSON serializer. Maybe you can give it a try and see if it works on the platform you want.
It would be nice to see your experiences regarding which serializer works with which platform, so you can comment your findings on this issue.

Hi there, berkayalpcakal
I am not sure I'm doing this correctly, so could you please tell me how to use .NET JSON instead?

Hi,
With the recent changes here, one can use .NET JSON serializer instead of Newtonsoft JSON serializer. Maybe you can give it a try and see if it works on the platform you want.
It would be nice to see your experiences regarding which serializer works with which platform, so you can comment your findings on this issue.

Hi,
I am not sure I'm doing it correctly. Could you please guide me through the process. I think I am not replacing anything, because results are the same: it does not work once built.

Hi @Scharfhausen,
Have you pulled the recent changes to your local already?
If you did so, you can see that RosSocket gets an argument to set the serialization tool.
What you can do on Unity side;

Go to your RosConnector component on the inspector editor
Set e.g. Serializer: Microsoft and Protocol: WebSocketSharp etc.

Hi @Scharfhausen,
Have you pulled the recent changes to your local already?
If you did so, you can see that RosSocket gets an argument to set the serialization tool.
What you can do on Unity side;
* Go to your RosConnector component on the inspector editor

* Set e.g. Serializer: Microsoft and Protocol: WebSocketSharp etc.

OK, I did not know that it was that recent, I cloned the repo 10 days ago. But with the new commit, it works perfectly selecting "Microsoft" as serializer, both in Linux (I tried with Ubuntu 16.04) and in Windows 10.

authors: Andor233 Scharfhausen berkayalpcakal

repo: siemens/ros-sharp


text:
Latest Chat-API is here

Hi!
Have You seen latest version of Chat-API here?
its working fine without any issues.
https://chat-api.net
Thanks

Please do not advertise on this repository.

authors: chat-api sigalor

repo: sigalor/whatsapp-web-reveng


text:
Cursor not updating properly when deleting tab character.

When deleting a tab from a tab indented line, cursor column position doesn't update. Tabs count as 4 characters.

bde579c71263e4fd8b8d1aac58d85b780eb57658 fixes the issue. Closing.

repo: sigmareaver/ImGuiColorTextEdit


text:
Limit switch doesn't work

On master branch
./SigSci.py --limit 3
Produces all results and does not limit the output. Tried in combination with from, still same outcome.

Thanks for reporting this @nickwinn. I hope to get a fix in soon.

Fixed this in v0.0.9 https://github.com/signalsciences/SigSciApiPy/releases/tag/v0.0.9

authors: foospidy nickwinn

repo: signalsciences/SigSciApiPy


text:
🛑 sfgz is down

In 4a33183, sfgz (https://sfgz.ch/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sfgz is back up in 2957ec6.

repo: signalwerk/uptime


text:
call.receive with multiple contexts

Force calling.onInbound to send contexts as an array of strings and simplify RelayConsumer code

@Astaelan of course, i tested on staging and we're 👍

repo: signalwire/signalwire-node


text:
Add kleung@ as a reviewer on sigstore/helm-charts

Description

I'm making a bunch of minor changes to the helm charts and would like to be able to more easily bunch versions of the helm charts to pick up new dependent chart versions.
Would be nice to have permissions to assign reviewers and merge permissions.
@dlorenc @cpanato

With the amount of great contribution that @k4leung4 has put forth, i'm totally in favor!

Cool, me too! I'll close this out.

+1000

👏🏻

repo: sigstore/helm-charts


text:
undefined method issue with JRuby publisher

Description
👋  I got the following error with trusted publisher used by JRuby.
https://github.com/ruby/psych/actions/runs/12115672565/job/33774497380#step:8:58
ERROR:  While executing gem ... (NoMethodError)
    undefined method `public_to_der' for #<OpenSSL::PKey::EC:0x650d5a3d>
Did you mean?  public_method
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/sigstore-0.2.1/lib/sigstore/verifier.rb:286:in `verify_sct'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/sigstore-0.2.1/lib/sigstore/verifier.rb:264:in `block in verify_scts'
	org/jruby/RubyArray.java:1981:in `each'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/sigstore-0.2.1/lib/sigstore/verifier.rb:263:in `verify_scts'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/sigstore-0.2.1/lib/sigstore/signer.rb:1[54](https://github.com/ruby/psych/actions/runs/12115672565/job/33774497380#step:8:58):in `verify_chain'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/sigstore-0.2.1/lib/sigstore/signer.rb:43:in `sign'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/sigstore-cli-0.2.1/lib/sigstore/cli.rb:95:in `sign'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/thor-1.3.2/lib/thor/command.rb:28:in `run'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/thor-1.3.2/lib/thor/invocation.rb:127:in `invoke_command'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/thor-1.3.2/lib/thor.rb:538:in `dispatch'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/thor-1.3.2/lib/thor/base.rb:584:in `start'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/sigstore-cli-0.2.1/lib/sigstore/cli.rb:13:in `start'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/gems/shared/gems/sigstore-cli-0.2.1/exe/sigstore-cli:5:in `<main>'
	org/jruby/RubyKernel.java:1220:in `load'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/stdlib/rubygems/commands/exec_command.rb:225:in `load!'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/stdlib/rubygems/commands/exec_command.rb:74:in `execute'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/stdlib/rubygems/command.rb:326:in `invoke_with_build_args'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/stdlib/rubygems/command_manager.rb:253:in `invoke_command'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/stdlib/rubygems/command_manager.rb:194:in `process_args'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/stdlib/rubygems/command_manager.rb:152:in `run'
	/home/runner/.rubies/jruby-9.4.8.0/lib/ruby/stdlib/rubygems/gem_runner.rb:[57](https://github.com/ruby/psych/actions/runs/12115672565/job/33774497380#step:8:61):in `run'
	/home/runner/.rubies/jruby-9.4.8.0/bin/gem:12:in `<main>'

Version
sigstore-0.2.1 and release-gem@1.1.0.

JRuby is unsupported due to numerous issues with jruby-openssl, let me disable for jruby on release-gem

ah the push still succeeded but the attesting failed, again because jruby-openssl isn't fully compatible with the OpenSSL module interface

Yes, gem push is succeeded with JRuby. Can we disable only sigstore feature with JRuby?

We do plan to fix these things... just nobody available to work on them right now!

I've been working on getting around this in https://github.com/sigstore/sigstore-ruby/pull/192

authors: headius hsbt segiddins

repo: sigstore/sigstore-ruby


text:
Use project ID, not code, in CrdtMerge API

Fix #1168.
We now use project code and ID in root folder name, use "crdt" and "fw" inside root folder no matter what the project's actual code or name is.
We also use project ID rather than code in the API request parameters. So now instead of POSTing to /sync/?projectCode=sena-3, you would POST to /sync/?projectId=0ebc5976-058d-4447-aaa7-297f8569f968.

Draft PR for now. Once https://github.com/sillsdev/languageforge-lexbox/pull/1170 finishes passing tests, I'll merge it, then rebase this PR on top of it and then we'll be ready for review.

repo: sillsdev/languageforge-lexbox


text:
SF/Serval: Limit drafting requests without training data to translations where both source and target are native NLLB-supported languages

If the source or target language is not a native NLLB supported language, require training data to be supplied. Scripture Forge should check that training books are selected. Serval should check that training data is available before launching a training job.

This has been completed already.

repo: sillsdev/serval


text:
Save Image or Video in another dir | raspimjpeg crashs

Hi,

I tried the part on eLinux --> Move images and videos to antoher folder. So for testing purposes I'm using a mounted USB Stick. So if I bind my Stick with /var/www/media I can't take any pictures or videos anymore. The buttons are not working since then. After restarting the Raspberry und starting the interface again the cam everything is working fine, but still no saving on my USB Stick. My goal is to save all the stuff on a external hdd.
After some ours with motion detection raspimjpg is just crashing. After that I always need to restart the interface service. Any Idea?

So far
Jannis

Lots of people use external storage so it is a matter of getting settings right. One thing that is important is that the www-data user has full permissions to read and write on the storage.
For problems including crashing the first thing to do is check the log inside schedule which also logs all errors from the core raspimjpeg program.


text:
Add docs for admonitions

Create Admonitions.md
This is already mentioned in the CHANGELOG.md, but I think it is easier to find when it has a seperate page.

Thanks!

repo: silverbulletmd/silverbullet


text:
Fix for Issue CartEditField using Product

Fix for #605

I was not sure that this would fix the problem but from my tests it has. It would make me feel safer if another dev can confirm this but for me it fixed what I was working toward.

Buyable should return the Product for the default OrderItems, so this is basically no change for the default shop. And since tests are passing I think this is safe to merge. Thanks @catharsisjelly

authors: bummzack catharsisjelly

repo: silvershop/silvershop-core


text:
DEP Remove unsupported modules

Issue https://github.com/silverstripe/.github/issues/342

Updated

Userforms CI failure is a known issue and not related to this PR

authors: GuySartorelli emteknetnz

repo: silverstripe/recipe-kitchen-sink


text:
Strongly type FieldList

Many methods on FieldList will silently fail if you give them bad types.
e.g.: $fields->addFieldsToTab('Root.Main', $field1, $field2, $field3) will only add $field1 to the tab.
Acceptance criteria

All methods in FieldList are strongly typed and have an explicit return type.
addFieldsToTab hard fails if the second parameter is not an array.
All of kitchen sink is shown to pass CI before any PRs are merged

FieldList is not in a vacuum - it's the subclass of ArrayList which is a subclass of ViewableData, uses a trait, and implements several interfaces.
The ACs should specify whether any of that is in scope, or if this card is only for methods defined directly in FieldList, or if it's mostly about methods defined directly in FieldList but the implementor can choose to strongly-type other methods if they feel it's relevant to the goal of the card (i.e. making it clearer what can/cannot be passed into FieldList).

PRs merged

authors: GuySartorelli maxime-rainville

repo: silverstripe/silverstripe-framework


text:
BUG TinyMCE “WARNING: Your changes have not been saved.”

In current master of framework with TInyMCE 4.0.
“WARNING: Your changes have not been saved.” alert box shows up even when clicking between pages in the site tree that have no changes. Also refreshing the page with no changes shows this alert too.
Jira: https://silverstripe.atlassian.net/browse/OSS-1721

Fixed with https://github.com/silverstripe/silverstripe-cms/issues/1473

authors: chillu tractorcow


text:
Versioned::allVersions() somewhat broken

https://github.com/silverstripe/silverstripe-framework/blob/3.5/model/Versioned.php#L1038-L1090
$baseTable isn't defined if line 1059 doesn't ever evaluate to true
$having parameter is useless as there is no having method on DataList. If $having is supplied expect an error to be triggered

Why can't we just use $this->owner->baseTable()? :P
We also have this on 4.0... let's just make it an error and completely remove this arg (method?) in master.
if ($having) {
            // @todo - This method doesn't exist on DataList
            $list->having($having);
        }

This looks like one of the few versioned methods I didn't completely re-write... I'd have done it differently if so. :P

I'm going to be super lazy and guess this might work without testing it.
/**
 * Filterable datalist that returns all versions
 *
 * @return DataList
 */
public function allVersions()
{
	return DataObject::get($this->owner->baseClass())
		->distinct(false)
		->setDataQueryParam('Versioned.mode', 'all_versions');
}

I would hope the ORM / augmentSQL() would be smart enough to return the correct list for me.

Can't we just use Versioned::get_all_versions() (which is basically the code you've written out)
https://github.com/silverstripe/silverstripe-versioned/blob/1.0/src/Versioned.php#L2516-L2531

Oh right, yeah that is pretty much the same method isn't it?
... so why does allVersions() do what it does...

Oh right, because it returns a list of Versioned_Version instead, not the object itself.
solution: Drop Versioned_Version :D Looking at that class it seems super redundant.

agreed

All pull requests are merged, feel free to reopen if there is still work to be done

authors: dhensby robbieaverill tractorcow


text:
serviceworker.js:1 Uncaught (in promise) TypeError: Request failed

Hello i have the error:
Laravel PWA: ServiceWorker registration successful with scope:  https://divuar.com.ua/
serviceworker.js:1 Uncaught (in promise) TypeError: Request failed
var staticCacheName = "pwa-v" + new Date().getTime();
var filesToCache = [
'/offline',
'/css/app.css',
'/js/app.js',
'/images/icons/icon-72x72.png',
'/images/icons/icon-96x96.png',
'/images/icons/icon-128x128.png',
'/images/icons/icon-144x144.png',
'/images/icons/icon-152x152.png',
'/images/icons/icon-192x192.png',
'/images/icons/icon-384x384.png',
'/images/icons/icon-512x512.png',
];
Please Explain me what the problem.
You can check site url https://divuar.com.ua

How did you solve this problem?

Сan't remember exactly.
But if I'm not mistaken, the list of files should be available.
In my example files were not available
'/css/app.css',
'/js/app.js',

Saved my day!! Thanks a lot

For anybody else that is coming here for this issue. Ensure that vendor/laravelpwa/offline.blade.php is able to load at /offline

repo: silviolleite/laravel-pwa


text:
Display custom title and selection count with multi-selection

<select name="propertyType" id="propertyType" class="selectpicker btn-noborder" multiple>
  <option value="1">Detached</option>
  <option value="2">Semi-detached</option>
  <option value="3">Terraced</option>
  <option value="4">Flat</option>
  <option value="5">Bungalow</option>
  <option value="6">Land</option>
</select>

Using the code above, rather than the label saying "None selected" or "Detached, Semi-detached, Terraced", I would like it to always say "Property Type" and if one or more options are selected, the selection count is also displayed. For example "Property Type (3)".
Is this functionality already supported or would I need to code it myself? Thanks.

<select name="propertyType" id="propertyType" class="selectpicker btn-noborder" title="Property Type" data-selected-text-format="count" data-count-selected-text="Property Type ({0})" multiple>
  <option value="1">Detached</option>
  <option value="2">Semi-detached</option>
  <option value="3">Terraced</option>
  <option value="4">Flat</option>
  <option value="5">Bungalow</option>
  <option value="6">Land</option>
</select>

Perfect thanks!

authors: davidenco talhsoft

repo: silviomoreto/bootstrap-select


text:
[gui][ImageStack] improve _PlotWithWaitingLabel thread management.

Changelog:

LGTM

repo: silx-kit/silx


text:
SQLite Session Extension

What would be the best way to explore using the official SQLite Session Extension with Drift?
https://sqlite.org/sessionintro.html
From my research the API is in C, and would need some compile flags passed to the custom sqlite build.
I did find an interesting example for iOS/MacOS:
https://github.com/gerdemb/SQLiteChangesetSync

At the moment (I hope this gets a lot easier with the native assets SDK feature), you can't pass custom compiler flags to the buildscripts in sqlite3_flutter_libs. So the first step is to fork that package and add the relevant definitions for the platforms you need unfortunately.
Once you have the functions available, you can write bindings to them using dart:ffi. You'll need the sqlite3* pointer to the database connection drift uses. You get access to the underlying database in the setup method on NativeDatabase constructors and you can use .handle to get the native pointer to use when calling other sqlite3 functions (it might be easier to start with a local database instead of using background isolates to have everything available in the same isolate).
With the database pointer, it should be possible to create changesets and apply them. How to best integrate that functionality into drift is another question. You could call the methods to create sessions synchronously, then use drift methods to run statements and once that's done, use another C call to obtain a changeset.

Node.js is about to unflag the SQLite API and I saw it supports the session extension!
https://nodejs.org/api/sqlite.html
I will be looking at it on how it maps to the c code from JS.


text:
🛑 Victoris Webby is down

In 1114a9a, Victoris Webby (https://$VW_SITE1/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Victoris Webby is back up in 7234d50 after 3 minutes.


text:
Easy way to change schema number?

In DiskLruCache you can change the version number when you build the cache. Is there a similar option for this library?

Hi @bmccorvey3, currently there is no option to change the appVersion number while building an instance of Bucket.
However, that could quite easily be done by passing a value to the createDiskLruCache method in SimpleDiskCache.java, currently value 1 is always passed. The value would need to be passed through the Builder class first, so it can be created using the builder.
All PRs for features you might need are very welcome and I will gladly merge them and publish a new version of the library if requested. Be sure to create a PR to the develop branch and that all tests pass. 👍
Otherwise, I might add this feature request to my queue and get around implementing it sometime in the future. 🕐
Thank you for your interest in the lib. Let me know if there's anything else I can help you with.

Thanks! This is a great lib :) I'll look into adding that feature, but not sure if I can do it immediately.

repo: simonpercic/Bucket


text:
"datasette inspect" outputs invalid JSON if an error is logged

See https://github.com/simonw/register-of-members-interests/issues/6:
% datasette inspect regmem.db
ERROR: conn=<sqlite3.Connection object at 0x10d2a9c60>, sql = 'select count(*) from [items_fts]', params = None: SQL logic error
{
  "regmem": {
    "hash": "6fde27e3dea80d6b65f2ac7f89cd8448980fee8c91b505ba29c311ba0393317f",
    "size": 936198144,

Here's why: https://github.com/simonw/datasette/blob/37f87b5e52e7f8ddd1c4ffcf368bd7a62a406a6d/datasette/database.py#L158-L163

https://clig.dev/#the-basics

Send messaging to stderr. Log messages, errors, and so on should all be sent to stderr. This means that when commands are piped together, these messages are displayed to the user and not fed into the next command.

https://clig.dev/#the-basics

Send messaging to stderr. Log messages, errors, and so on should all be sent to stderr. This means that when commands are piped together, these messages are displayed to the user and not fed into the next command.

Oddly enough, I tried fixing this with sys.stderr.write("{}\n".format(e)) - but my Click CLIRunner tests failed because result.stderr was an empty string. Adding sys.stderr.flush() to the code that output errors fixed that issue.

repo: simonw/datasette


text:
Reduce table counts on index page with many databases

Since #467 the index page has attempted to optimistically count times.
My personal Dogsheep has enough connected databases and tables that the page can still take way too long to load - sometimes more than twenty seconds.

The easiest solution would be to only show counts on the index pages for immutable (-I) databases.
I don't like this, because the most common uses of Datasette don't in my opinion justify it. Most of the time Datasette will be running against a single, small, mutable database. I'd like to show counts in that case.
Some options:

disable counts on the index page for mutable databases of more than one is attached
disable counts on the index page for databases where the file in disk is larger than a specified threshold (maybe 10MB? I'm making up this number)
implement an overall timer which cuts off table counting once the sum of time spent on it has gone beyond a second

Worth prototyping a bit to see what works best.

I tried this out in https://github.com/simonw/datasette/commit/34bc16aa591a2f02b2bb33277d33e5bccfb95569 with an upper limit of 100MB and it worked an absolute treat against my personal Dogsheep.


text:
Inject custom token/session during fastboot

Hello,
I have a case where I need to require authentication to access a page, but render the page or part of it for crawlers during fastboot. I've configured fastboot and simple-auth on ember and it works like a charm, and renders a page if cookie exists, but login page if not.
I would like to inject custom token/session (or way to authenticate) for API service during fastboot if cookie doesn't exist. I wandered through documentation and code, but couldn't find a way to implement this correctly. I think that this feature would be super useful for a lot of cases.
Could you please advice on how I can implement above use case using fastboot and simple-auth.

I'm not sure what the requirement is here tbh. By default the AuthenticatedRouteMixin will transition to the login route if a route that requires authentication is accessed without the session being authenticated. If you don't want that behavior you can just as well not use the mixin and always render the route and render/not render certain parts of the template depending on whether the session is authenticated or not.

authors: dulmandakh marcoow

repo: simplabs/ember-simple-auth


text:
Can we use Simple.OData.Client where Metadata endpoint/information not available?

Odata is new to me. Currently, I am trying to use Simple.OData.Client.  The API  I'm  comnsuming is build on OData but the metadata endpoint is not available.
Now I believe without metadata information/endpoint OData client will not going to work but Iam not sure.
So, is it possible to use Simple.OData.Client where metadata URL not being exposed by API or metadata information not available?

You should be able to download the metadata from somewhere, it's not really an OData endpoint without metadata,; you can then assign it statically in your client.

@phatcher  thank you.

authors: GSingha phatcher


text:
How to handle CLOB and BLOB fields

My existing data base has CLOB and BLOB fields are part of master/transaction records. How do we handle these fields?

CLOB : If the CLOB field is to be rendered as if it is a text field (but large) by the client, for both input and output, then you do not need to do anything. That is, use this field as if it is a VARCHAR field. Simplity takes care of saving/retrieving it.
if BLOB/CLOB is actually an attachment :  In this case, the server side handling is very simple. Just declare the field dataType as blob/clob. (In record.xml, <field dataType="blob".../>, you may do the same in procedureParameter as well)
Once you declare the data type as clob/blob, Simplity uses the field to store the name of a temp file in which the actual content of the attachment is saved (either for storage during upload, or for downloading during retrieval)
An example is provided in Help/Tutorial example for this.
Client-side code depends on your client design.
When you retrieve a record, client would get the name of this temp file as the field value. Use a url /a._f? as src value (for example, if this is an image, you may set src="a._f?), If you want to download this, use url a._f?download=

In this example, we have created a record for the underlying table. No service is required, as we can use on-the-fly service namely filter_tutorial.blobTest and save_tutorial.blobTest. Your server side coding is just this record.xml. Nothing more.
blobTest.zip

Here is the revised example. This one demos how to use externally stored attachment files as well.
Step 1. Setting the application for externally storing attachments.
You should set attachmentStoragePath="" in application.xml
for example I used
attachmentsFolderPath="e:/attachments/"
Step 2. Create the test table BLOB_TEST_TABLE in your db
(I have used oracle)
CREATE TABLE  "BLOB_TEST_TABLE"     (	"BLOB_TEST_NAME" VARCHAR2(100) NOT NULL ENABLE,  	"CLOB_IN_ROW" CLOB,  	"CLOB_TEXT" VARCHAR2(1000) NOT NULL ENABLE,  	"BLOB_EXTERNAL" VARCHAR2(100) NOT NULL ENABLE    ) ;
Step 3: Create blobTest.xml
(I have used it inside folder tutorial)
`
<record
xmlns="http://www.simplity.org/schema"
name="blobTest"
moduleName="tutorial"
recordType="storage"
okToSelectAll="true"
tableName="BLOB_TEST_TABLE"
description="We demonstrate three different ways of dealing with LOBs
1. treat it as text
2. declare it as CLOB and save it as part of record
3. store the file externally, ad keep key to it as a text field in th database "

<fields>
	<field
		name="blobTestName"
		dataType="text"
		columnName="BLOB_TEST_NAME"
		description="Name that the user identifies this row with." />
	<field
		name="clobInRow"
		dataType="clob"
		columnName="CLOB_IN_ROW"
		description="This is delared as CLOB in RDBMS.
			Used to store a text file attachment." />
	<field
		name="clobText"
		dataType="text"
		columnName="CLOB_TEXT"
		description="Declared as CLOB in RDBMS but we use textDataType. Used as if it is text field by app and client." />
	<field
		name="blobExternal"
		dataType="text"
		columnName="BLOB_EXTERNAL"
		description="Declared as VARCHAR2 in RDBMS.
			Attachment that is stored externally, but a key to that attachment is saved in rdbms as a text field.
			Client uses this attachment." />
</fields>

`
**Step 4 : Define service to add row to this**
We could have used auto-service (on-the-fly-service) but for the externally stored attachment
Here is my saveBlob.xml inside tutorial folder
`

`
Step 4 : Define a service to read rows from this table
We use a filter action to read all. Once again, we have to write a service because of externally stored attachment. Here is my getBlobs.xml inside tutorial folder
`

<service
xmlns="http://www.simplity.org/schema"
name="getBlobs"
moduleName="tutorial"
dbAccessType="readOnly"
description="We could have used on-the-fly service like filter_tutorial.getBlobs, but for the externally stored blob.
To keep it simple for the demo, we select all rows, and hence no input.
We have set-up the application to save attachments in a specific folder"

<actions>
	<filter filterRecordName="tutorial.blobTest" outputSheetName="blobs"></filter>
</actions>
<!-- attachmentColumns attribute directs Simplity to retrieve externally stored blob using the key in the fiel bolbExternal.
	This key is replaced with the new key that poiints to temp-storage from where it can be streamed to client.
-->
<outputData attachmentColumns="blobs.blobExternal" >
	<outputRecords>
		<outputRecord sheetName="blobs" />
	</outputRecords>
</outputData>

`
Step 6 : Finally the client side code
Nothing fancy, just to show the features, here is my blobDemo.html
`

Blob Clob Test

Clob Blob Demo

Existing Entries

Code
Description (from a CLOB field)
Clob in Row
Clob Download
Blob External
Blob Download

__blobTestName__
__clobText__
__clobInRow__
download
__blobExternal__
download

Add a Row

Name

Description
This is saved as clob.

Text File

Binary File

`
Here is the zip file with all the code (except application.xml setting)
blobTest.zip

repo: simplity/simplity


text:
cste ?

Dear Sina,
In paper, You use cste as abbreviation; however, there is no explicit form of cste in paper. What does cste refer to ? Thank you for clarification.

Hi,
In our equations, "Cste" means constant. We meant that there is an additional term, other than the KL divergence, which does not affect the optimization. For example, $- \log(1 + |\mathcal{C}^b| + |\mathcal{C}^n|)$ in equation 7.
$\operatorname{KL}(\widehat{\mathbf{p}} || \mathbf{u}) = \widehat{\mathbf{p}} \cdot \log \frac{\widehat{\mathbf{p}}}{\mathbf{u}} = \widehat{\mathbf{p}} \cdot \log \widehat{\mathbf{p}} - \widehat{\mathbf{p}} \cdot \log \mathbf{u} = \widehat{\mathbf{p}} \cdot \log \widehat{\mathbf{p}} + \log(1 + |\mathcal{C}^b| + |\mathcal{C}^n|)$
Sorry for the confusion.

When Π replaces uniform distribution, cste term equals = p_cap · log Π . Although this is not constant, you keep on referring to it as constant. By the way, thank you for the explanation.

No problem. I think you are right, thanks for noticing.

authors: alpoler sinahmr

repo: sinahmr/DIaM


text:
Auth: Create new User account

[ ] API Endpoint
[ ] React Webpage

@Kalunge  doing api endpoint and @Dachoka3000 doing react design page and we'll jointly do the react logic.

Postgres issue => is still being resolved.
@Kalunge will meet with @Dachoka3000 to fix the issues tomorrow(22nd March 2023)

authors: Dachoka3000 mutuajoseph otsembo

repo: sinatra-pod/moringa-library


text:
Switch to event-kit instead of emissary

From https://github.com/atom/emissary:

Achtung! This library is currently used in Atom and various Atom dependencies, but our long-term plan is to transition away from it in favor of the simpler event-kit library. Don't depend on supporting this library forever.

I can look into that when #90 is closed :)

@nicolasbrugneaux :+1: Really appreciate it :)

Hey @sindresorhus, after working on it today, I'm really wondering what's the point of emissary.Subscriber.extend(plugin), because it doesn't seem to achieve much. From my tests we just get rid of it totally.

@nicolasbrugneaux Yeah, I guess https://github.com/sindresorhus/atom-jshint/commit/ce1adbde573bd1384d1b80902c687b4e0c245223 made it moot. Go ahead ;)

authors: nicolasbrugneaux sindresorhus

repo: sindresorhus/atom-jshint


text:
For web frameworks

https://github.com/crocodilejs/crocodile-node-mvc-framework

NOT RELEASED YET

Try again when it's more mature.
Also please read the contributing guidelines next time.

Okay I understand, but no need to come off as snarky and rude haha, was
just trying to contribute since all the other frameworks listed are trash +
outdated.
On Nov 4, 2016 11:44 AM, "Sindre Sorhus" notifications@github.com wrote:

NOT RELEASED YET
Try again when it's more mature.
Also please read the contributing guidelines
http://../blob/master/contributing.md next time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sindresorhus/awesome-nodejs/issues/613#issuecomment-258467205,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAf7hSjNuxI_mLROzayDiRvOQJuWVjqiks5q61LegaJpZM4Kpo6D
.

authors: niftylettuce sindresorhus

repo: sindresorhus/awesome-nodejs


text:
New list: Energy Efficiency for Mobile Apps

I am adding the awesome list of papers of energy efficiency for mobile apps. (https://github.com/luiscruz/awesome-mobile-app-energy-papers)

https://github.com/luiscruz/awesome-mobile-app-energy-papers
This is an awesome-based list with academic literature on energy efficiency coding practices for mobile app development
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The heading title of your list should be in the following format: # Awesome Name of List

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ #

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.
To verify that you've read all the guidelines, please add comment with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

authors: luiscruz sindresorhus

repo: sindresorhus/awesome


text:
Add support for doing the hashing in a worker thread

Could maybe be useful for hashing large files, as the crypto Node.js module is synchronous, so it could block the main thread for some time.
https://nodejs.org/api/worker_threads.html
Thoughts?

There is a $80.00 open bounty on this issue. Add more on Issuehunt.

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on Issuehunt to raise funds.

I like it. It's usually not super expensive, but a 1gb file shasum takes ~4s on my macbook 2015 2.8 GHz Intel Core i7
I would actually prefer a C++ binding (that I'd guess would be faster, since in OS X for example, running openssl sha1 :file takes 4x less time than the crypto approach in node.

I would actually prefer a C++ binding (that I'd guess would be faster, since in OS X for example, running openssl sha1 :file takes 4x less time than the crypto approach in node.

Not interested in doing native bindings. That comes it its own set of horribleness.

Related to https://github.com/sindresorhus/crypto-hash/pull/7
// @stroncium

Can easily be done for file hashes(and will work perfectly).
For strings/buffers, I don't see a way to go further than is done in https://github.com/sindresorhus/crypto-hash/pull/7 so I'd just use it.
As far as my understanding goes, we will have to always clone(not transfer) bytes for arbitrary streams, and as chunks are expected to be pretty small, the chance clone+send task overhead will be be bigger than just hashing in place is quite high. Needs some benchmarks, but I'm pretty sure it's not viable.
Speaking of performance comparison with openssl, it sounds strange to me, as node is using openssl underneath. If such issue actually exists it could use some serious debugging on libuv/nodejs/app level.

@issuehunt has funded $80.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

On it.
@sindresorhus Should I add crypto-hash as a dependency or duplicate code?

Does crypto-hash expose enough functionality? Would be good to share code if possible, yes.

@sindresorhus Need to check it, but should be enough.

@sindresorhus Never mind. I didn't notice there was no async version of string/buffer hashing in hasha. Without it there is almost no code intersection with crypto-hash.

I didn't notice there was no async version of string/buffer hashing in hasha.

Sorry if the issue was not clear enough on this, but the intention is to add it now that it's possible.

@sindresorhus Well, then there are some questions:

Should it be a breaking change(to promise returning function) or additional method?
crypto-hash doesn't support md5, should we add it just for nodejs? (And while at it, should we add a method you pass algorithm string to for consistency?)
If not, should we use crypto-hash at all? Most code will need to be duplicated here to implement md5 anyhow.

Should it be a breaking change(to promise returning function) or additional method?

Additional method.

crypto-hash doesn't support md5, should we add it just for nodejs? (And while at it, should we add a method you pass algorithm string to for consistency?)

Nah

If not, should we use crypto-hash at all? Most code will need to be duplicated here to implement md5 anyhow.

Probably not worth using crypto-hash at all then.

authors: IssuehuntBot sindresorhus stroncium tomasdev

repo: sindresorhus/hasha


text:
performance tests and comparisons

Do we know how fast noop3 is?
How much faster is it than lodash.noop?
Or jQuery.noop?
We should also experiment with using child processes or Web Workers to offload the task of doing nothing so that we can do nothing without blocking the main thread.

Great idea! By doing this I'm supremely confident we could boost the performance tenfold of nothing.

authors: jokeyrhyme sindresorhus


text:
Alignment issue in Releases subnav

Test url: https://github.com/sindresorhus/refined-github/releases
DOM as it appears:

			Releases
			Tags

			Packages

				Sign up for the GitHub Package RegistryBeta

		Draft a new release

			Select
				tag

Apparently this is what it looks like without Refined GitHub. Awful too

This seems to be the fix, but I don't know what's causing the issue in the first place. PR welcome to locate the troubling CSS and placing this next to it.
.subnav > :first-child {
	flex-grow: 1
}

Just noticed this issue as well. I'll push a fix tonight.

authors: fregante hardikmodha

repo: sindresorhus/refined-github


text:
Enhance view-markdown-source with line actions

Currently within the source/features/view-markdown-source.tsx the plugin does not add the ... menu on line highlight.
Before:

After:

Example URL:
https://github.com/sindresorhus/refined-github/blob/3d517d6cd00e83a51973808c7ff03cae2b692d2b/contributing.md

I also understand that links like "https://github.com/sindresorhus/refined-github/blob/master/contributing.md#L76" only work with RG installed. Non RG users will just be brought to the top of the file. (That is a shortcoming of GH with markdown.)

This feature appears to be super easy. This is the code needed, it just needs to be cleaned up (use .append, JSX, our icons, drop unnecessary attributes)
$('.blob-wrapper').insertAdjacentHTML('beforeend', `

      <svg class="octicon octicon-kebab-horizontal" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M8 9a1.5 1.5 0 100-3 1.5 1.5 0 000 3zM1.5 9a1.5 1.5 0 100-3 1.5 1.5 0 000 3zm13 0a1.5 1.5 0 100-3 1.5 1.5 0 000 3z"></path></svg>

          <clipboard-copy role="menuitem" class="dropdown-item" id="js-copy-lines" style="cursor:pointer;" tabindex="0" value="import select from 'select-dom';" data-ga-click="Blob, copyLines, numLines:1">Copy line</clipboard-copy>

          <clipboard-copy role="menuitem" class="dropdown-item" id="js-copy-permalink" style="cursor:pointer;" tabindex="0" value="https://github.com/sindresorhus/refined-github/blob/3d517d6cd00e83a51973808c7ff03cae2b692d2b/source/features/view-markdown-source.tsx#L3" data-ga-click="Blob, copyPermalink, numLines:1">
            Copy permalink
          </clipboard-copy>

View git blame

Reference in new issue

  `)

authors: fregante shadowbq


text:
added line-through to deleted branches

Closes #1985

See my last comment on that issue. This change isn’t enough and can probably be fixed by adding the style on the SPAN without adding the extra CSS file

Alright, I will send feedback commits soon.

I closed the PR because that code was dropped. I reopened your issue

authors: fregante gurrrung


text:
跑400MB的文本数据会出现错误

是否无法处理大规模数据？

@Vanqingyu 我测试下，因为是用的基于磁盘的排序，所以数据量大了，仅仅是时间问题。能贴出来错误么？400MB也不算大的。

@Vanqingyu 方便共享一下文本么？

目前只能看到报的在treenode上的错误

能否加你的QQ

文本里面含有英文，是否会造成影响？

https://pan.baidu.com/s/1eRFdJJ8
这是其中一部分文本数据

@Vanqingyu 314235397 QQ


text:
[Feature request] Python 3.12 support

Add support for Python 3.12 (release Oct 2023).

while we are at it, it would be good to remove 3.8 support. Lots of our upstream packages have already done so (e.g. numba, pandas, etc)

Status as of 2024-02-05: numba 0.58 is not yet ready for Python 3.12.
$ docker run --rm -it --entrypoint=/bin/bash python:3.12-bookworm
root@20d715ac5ab7:/# pip install numba==0.58
Collecting numba==0.58
  Downloading numba-0.58.0.tar.gz (2.6 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.6/2.6 MB 32.5 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-417bk_qg/numba_1954fc6d020f4c6087042050c24f72c3/setup.py", line 51, in <module>
          _guard_py_ver()
        File "/tmp/pip-install-417bk_qg/numba_1954fc6d020f4c6087042050c24f72c3/setup.py", line 48, in _guard_py_ver
          raise RuntimeError(msg.format(cur_py, min_py, max_py))
      RuntimeError: Cannot install on Python version 3.12.1; only versions >=3.8,<3.12 are supported.
      [end of output]

$ docker run --rm -it --entrypoint=/bin/bash python:3.11-bookworm
root@d8f7153f52c6:/# pip install numba==0.58
Collecting numba==0.58
  Obtaining dependency information for numba==0.58 from https://files.pythonhosted.org/packages/f7/b6/8800604a3380aa94af830c30839db93077c7fe2812a48ce7d4400d75ba9c/numba-0.58.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl.metadata
...
Installing collected packages: numpy, llvmlite, numba
Successfully installed llvmlite-0.41.1 numba-0.58.0 numpy-1.25.2

Numba 0.59, with Python 3.12 support has shipped.  Pandas, Scipy and others also have support for it.  Worth getting on a sprint plan IMHO

@bkmartinjr today on a fresh run from a clean Docker image I still see
ubuntu@anzo[prod][][~]$ docker run --rm -it --entrypoint=/bin/bash python:3.12-bookworm
root@b40ac19e07af:/# pip install numba==0.58
Collecting numba==0.58
  Downloading numba-0.58.0.tar.gz (2.6 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.6/2.6 MB 50.8 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-j2snfwgz/numba_d1b59dcca00a4953958d684844fe3e9d/setup.py", line 51, in <module>
          _guard_py_ver()
        File "/tmp/pip-install-j2snfwgz/numba_d1b59dcca00a4953958d684844fe3e9d/setup.py", line 48, in _guard_py_ver
          raise RuntimeError(msg.format(cur_py, min_py, max_py))
      RuntimeError: Cannot install on Python version 3.12.1; only versions >=3.8,<3.12 are supported.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

[notice] A new release of pip is available: 23.2.1 -> 24.0
[notice] To update, run: pip install --upgrade pip

I don't think this is sprint-schedulable for TileDB-SOMA until we can do the above without error.

@bkmartinjr this succeeds for me! :)
ubuntu@anzo[prod][][~]$ docker run --rm -it --entrypoint=/bin/bash python:3.12-bookworm
root@62dc2a187e2d:/# pip install numba==0.59
...

I'll re-try my #2108 probe ...

Work items detailed on #2140; more info coming here momentarily

I put up PR #2108 and it was green so I merged it
Now PRs #2119 #2136 and anything else new is failing MacPS Python 3.12 CI fails

Unable to install wheel for pyarrow
https://github.com/single-cell-data/TileDB-SOMA/actions/runs/7896650237/job/21550972931?pr=2138 for example

Another issue: TileDB-Py doesn't have wheels for 3.12

https://pypi.org/project/tiledb/#files

Changes:

Leave 3.12 support in place -- don't entirely revert #1849
Don't fail CI for 3.12 until the above is resolved
Leave #1849 open for tracking

while we are at it, it would be good to remove 3.8 support. Lots of our upstream packages have already done so (e.g. numba, pandas, etc)

@bkmartinjr I will file a separate tracking task -- bring up the leading edge and deprecating the trailing edge (for all stakeholders involved) are two very different problems

Please also see https://github.com/TileDB-Inc/TileDB-Py/issues/1865
[sc-37726]

@johnkerl - FYI, I believe tiledb-py is now supported on Python 3.12 (in reference to TileDB-Inc/TileDB-Py#1865).

@bkmartinjr thanks! On the discussion list for the next sprint :v:

Pending https://github.com/TileDB-Inc/TileDB-Py/issues/1865

Huge progress: https://github.com/TileDB-Inc/TileDB/pull/5223 is near completion in core. This should go into a core 2.26, which we'd include in a tiledbsoma 1.14.

Current unsolved challenges:

Latest Python 3.12 is 3.12.5

As debug I tried Python 3.12.3 which worked as debug, but isn't a good option for shipping

TileDB-SOMA's current typeguard version is 4.2.0
Python 3.12.4 added a new required argument to evaluate_forward_ref within Python's built-in typing module which broke many packages including typeguard
As a result, our TileDB-SOMA CI for PR 3001 fails like this

TypeError: ForwardRef._evaluate() missing 1 required keyword-only argument: 'recursive_guard'

typeguard 4.3.0 contains a fix for this problem

https://github.com/agronholm/typeguard/releases

But this surfaces another problem which is:

E       typeguard.TypeCheckError: item 0 of argument "coords" (tuple) did not match any element in the union:
E         NoneType: is not an instance of NoneType
E         int: is not an instance of int
E         somacore.types.Slice[int]: is not compatible with the Slice protocol because it has no attribute named '__orig_bases__'

/home/ubuntu/.pyenv/versions/3.12.5/lib/python3.12/site-packages/typeguard/_checkers.py:433: TypeCheckError

https://github.com/single-cell-data/SOMA/pull/222
Once that works, we'll need to:

Merge this PR
Tag a release of this repo (somacore)
Depend on 1.0.next of somacore within the TileDB-SOMA repo

I've currently got the following setup on an EC2 instance:

somacore locally with pip install -e with this PR checked out
tiledbsoma locally with pip install -e with https://github.com/single-cell-data/TileDB-SOMA/pull/3001 checked out

https://github.com/single-cell-data/TileDB-SOMA/issues/3221#issuecomment-2432148047

https://github.com/agronholm/typeguard/releases/tag/4.4.0

authors: bkmartinjr johnkerl

repo: single-cell-data/TileDB-SOMA


text:
Use the same timestamp across read and write operations.

This eliminates the distinction between the timestamps used to read and write TileDB data. This ensures that:

All data is written with the same timestamp.
When one context is used to write and then read the same data, the same timestamp is used for both operations.
A consistent view of a TileDB object is used for metadata when opening a handle for writing.

Given that all our tests pass, and this eliminates the "auxiliary read at time now" hack, I think this might be the right thing to do for this case.

preserving some of the stuff I have said in chat for posterity:
The model I have in my head, though, is that when interacting with a dataset, you are interacting with TileDB at one specific timestamp. If you want to read at a different timestamp, that belongs in a different context. (This would be even more salient with the proposed reopen API.)
Moreover, based on the following events:

10:00: Create collection a. This sets the write timestamp of all changes we do to a.
10:02: a.add_new_dataframe('b', ...). Write lots of data to b.
10:04: a.add_new_dataframe('c', ...). Write lots more data to c.
10:06: Close everything.

With the existing model, the timestamp of a write is determined by when the open occurs. That means that the write to a, which includes adding b and c as sub-elements, occurs at 10:00. However, the writes to b and c only occur at 10:02 and :04 (respectively), meaning that, if after all writes complete:

If you open a as of 10:01, b and c will both appear as members of the group, but will not contain any data (in fact, the metadata will not be set, which I am now thinking “write metadata with the timestamp of object creation” is probably the right thing to do).
If you open a as of 10:03, only b will contain data.
Only if you open a as of 10:04 or later, will the full object be there.

With this new model, all of a, b, and c will be created and written as of the same timestamp (10:00, by default, when the context was created).

I think this is kind of a thorny question, if for whatever reason we've opened the object for writing at a past timestamp (preceding other, existing, later-timestamped writes), what view of the contents/metadata should we start with?

My strong opinion is that it should always be as of the only specified timestamp, so that you get a temporally coherent view no matter what. If the user wants to act based on the “current” metadata, they can open the array/group/whatever as of Now (or The Infinite Future, as the case may be).
I’m going to leave this open until sometime tomorrow so that more discussion can happen if need be.

Then also for the record, my opinion is that setting the same timestamp across a group of writes is currently not advisable (especially as a default behavior) due to the randomization behavior exhibited in #919. We think we know how to avoid that (TBD -- it may not yet be fixed), but it's a deep and wide pitfall, which we ourselves fell into without delay. Again, I defer to you as long as this has been considered and deemed an acceptable risk (hopefully a temporary one).

What I don’t entirely understand is what circumstances are leading to randomized writes—are you opening, writing, and closing the same SOMA object multiple times over the course of a single execution? Because if you’re doing multiple writes on the same open, the behavior here will be unchanged on a per–SOMA object basis, since all write calls on the same open are recorded at the same timestamp anyway.
The other problem I was aiming to solve here is that there is an asymmetry between the way read timestamps and write timestamps are handled. For instance, with the previous behavior:

T+0:00: Create a new context with default options.
T+0:01: Use the context to write a bunch of data. Close.
T+0:02: Use that same context to read the data you just wrote.

When you read the data, it will not actually see the data you just wrote, because the read timestamp stored in the context is T+0:00, before the (automatic) timestamp used to write the data at T+0:01.
My feeling is that if we’re writing at the current timestamp, we should also be reading at the current timestamp, so the behavior is consistent on both sides. This can be achieved by allowing the user to opt out of timestamp consistency by passing None as a timestamp. (Alternately, we could make it opt-in, where None is the default but a user can pass in the current timestamp at context creation.)

Codecov Report
Base: 80.29% // Head: 90.92% // Increases project coverage by +10.63% :tada:

Coverage data is based on head (99e0c66) compared to base (957b78b).
Patch coverage: 100.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #981       +/-   ##
===========================================
+ Coverage   80.29%   90.92%   +10.63%
===========================================
  Files          72       30       -42
  Lines        3867     2138     -1729
===========================================
- Hits         3105     1944     -1161
+ Misses        762      194      -568

Flag
Coverage Δ

python
90.92% <100.00%> (-0.11%)
:arrow_down:

r
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

apis/python/src/tiledbsoma/_tiledb_array.py
98.55% <ø> (ø)

apis/python/src/tiledbsoma/_tdb_handles.py
94.50% <100.00%> (-0.76%)
:arrow_down:

...hon/src/tiledbsoma/options/_soma_tiledb_context.py
100.00% <100.00%> (ø)

src/rinterface.cpp

inst/tiledb/include/tiledb/domain.h

src/include/tiledbsoma/common.h

inst/tiledb/include/tiledb/vfs.h

R/SOMASparseNdArray.R

... and 37 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Issuing a correction on my previous statements regarding write timing: The timestamps of writes are recorded as of the close call, not as of the open. This means that some of the worse symptoms described above do not occur, but the asymmetry between read and write would remain.

My caution is an acknowledgment that I don't think I fully understand all the circumstances when it may be hazardous to set the same timestamp across my logical group of writes -- it's already surprised me a couple of times. Since we're demonstrably in the vicinity of the worst possible kind of bug -- nondeterministic, silent, and undetected data corruption -- my instinct is to just avoid the whole area, if possible, rather than attempt to navigate it safely.
On the other side of the scale, I understand we want to share the write timestamps mainly so that there will exist no timestamp when a reader would see some but not all of our writes. That's a virtuous property, which however I don't think necessary for SOMA & Cell Census. It should suffice that we can publish a known-good timestamp when the reader will see all of our writes (and nothing written after). I think we can simply let the timestamps default to "now" as we actually apply each write, per TileDB default behavior, and report when we finished.
Therefore I wouldn't set any shared write timestamp by default given our experience with the current version of TileDB. That implies I think the write timestamp is distinct from the read timestamp, where a shared default seems reasonable for some snapshot consistency (but always better to set a known-good one explicitly).
This isn't to say the current implementation doesn't have its own sharp edges that could be improved, which you've pointed out, but I feel your full model for read/write temporal coherence across a group of objects would be more safely adopted by TileDB-SOMA at a future date, when it's fully supported by TileDB itself, without even the slightest proximity to a data corruption hazard area.
Finally, to belabor it once again, this is all my personal opinion; I'm not suggesting I'm right, and I'm fine with agreeing to disagree on any of it, with you choosing what to do next.

Getting the opt-out tested ended up taking a little more time than I anticipated (mostly, the part where I was learning more about how timestamps work that led to my last comment), so I wasn’t able to get it out yesterday.
For now I would still prefer to make consistency opt-out, but we still have the option to make it opt-in if we need to before release.

After some discussion with Bruce, I’m going to submit this with timestamp consistency being the default (so that by doing nothing you get consistency). I would like to discuss at the big meeting tomorrow whether that should be the default, and if we want to go to “no timestamp by default” it will be a one-line change, just so that the rest of the implementation isn’t blocked on the default decision.

authors: codecov-commenter mlin thetorpedodog