Free access then enable billing later

How can I best approach this?
I'd like users to install the app for free, and offer billed upgrades.
So ideally, I'd need the billable middleware in place, but if I disable billing in the config, the middleware is going to be skipped.
Can I set billing enabled, but set the price to 0.00?
I know you are looking into multiple billing plans, but in the mean time, I'd like to give this idea a crack myself.

Yup its been on my mind, I just haven't mapped out the best solution yet.
What I've been planning is:
a) Allow for multiple plans in the config
b) Change grandfathered in shops table to be called free_use or similar
c) Add a "free on install" option in the config, so on initial install, we set the shop as free_use = true
d) You can then do $shop->isFreeUse() or something to detect if they're using the "free" plan
e) Add an easy way to go to the billing controller with a param which identifies which plan in the config to use for processing... a linkable way like "/billing?plan=x" (maybe the index of the array, unsure)
Just my notes from my plans, you're welcome to pick it apart. I haven't started dev on it yet because I wanted a solid plan as its a big change.

There is an easier way around this that I came up with last night.
The issue is Shopify won't allow you to do $0.00 unless you also have a value in the SHOPIFY_BILLING_CAPPED_AMOUNTfield. Here is what I am doing:
SHOPIFY_BILLING_ENABLED=1
SHOPIFY_BILLING_TYPE=recurring
SHOPIFY_BILLING_PLAN_NAME="Free Plan"
SHOPIFY_BILLING_PRICE=0.00
SHOPIFY_BILLING_CAPPED_AMOUNT=10000.00
SHOPIFY_BILLING_TERMS="Test stuff"
SHOPIFY_BILLING_TEST=1

You must also have a value in SHOPIFY_BILLING_TERMS for this to work, as per the documentation. Just make SHOPIFY_BILLING_CAPPED_AMOUNT the amount of your highest paid plan.

The method above would cause them to see a billing screen with Free Plan yeah, its a clever workaround! I'm trying to aim for a more, you install and just use it then upgrade later kinda flow. If my logic above is sound then I may pursue it.

I'd prefer they didn't see the initial billing screen either, so i'll have a think tomorrow about how this can be done. I imagine it'll need additional data to be stored against each shop.

I think the only data off the top of my head is the change from
"grandfathered" to "free_use" so we can write a method for the shop model
to determine if they're free.
On Thu., Aug. 16, 2018, 5:23 p.m. Paul Canning<EMAIL_ADDRESS>wrote:

I'd prefer they didn't see the initial billing screen either, so i'll have
a think tomorrow about how this can be done. I imagine it'll need
additional data to be stored against each shop.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ohmybrew/laravel-shopify/issues/76#issuecomment-413664919,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTuOlwQRyNoUVOji1H9tScMG1G02h7Xks5uRc2ngaJpZM4WAD9d
.

In my opinion the free_use and grandfathered serve two different purposes.
Grandfathered to me means that they have full access to the app without any need to pay anything.
Free use would mean that the shop is on a "freemium" plan. They can use the app with a limited set of features for free and that they have the option to upgrade to a larger set of features with a paid plan.
I think that adding "free_use" alongside "grandfathered" vs replacing grandfathered allows for a broader set of use cases.

There can also be another env setting that could maybe be SHOPIFY_BILLING_AUTO_FREEMIUM so that when the shop installs the app they automatically get tagged as "free_use".

Ah good point. Keeping grandfathered would be a good idea. Freemium
env/config is the way to go as you don't want to make a 0.00 plan for
nothing when a flag would work.. I like that word too.. freemium would be a
better column name than free_use.
On Thu., Aug. 23, 2018, 7:13 a.m. Nathan Pope<EMAIL_ADDRESS>wrote:

There can also be another env setting that could maybe be
SHOPIFY_BILLING_AUTO_FREEMIUM so that when the shop installs the app they
automatically get tagged as "free_use".
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ohmybrew/laravel-shopify/issues/76#issuecomment-415356645,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTuOrwI5fp4mgbrObnz3-6RlKbyU9kZks5uTnlFgaJpZM4WAD9d
.

I agree with the Free Use and Grandfathered.
TBH what I'm currently doing is splitting the Shop authentication and Billing stuff into two separate packages, which can be included via Composer.
Devs can then setup some config options and default routes and everything is taken care of.
I did some work making the Billing package as flexible as possible (currently just recurring and single charges) so the app doesn't rely on pre-defined config options. This means you can define different price plans (to allow access to different 'packages').
Although I might look at using a 'freemium' config option, if I can figure out a nice workflow.

Interesting approach. Is this something viable for this package you think?
Never thought of having it as components..
On Thu., Aug. 23, 2018, 10:36 a.m. Paul Canning<EMAIL_ADDRESS>wrote:

I agree with the Free Use and Grandfathered.
TBH what I'm currently doing is splitting the Shop authentication and
Billing stuff into two separate packages, which can be included via
Composer.
Devs can then setup some config options and default routes and everything
is taken care of.
I did some work making the Billing package as flexible as possible
(currently just recurring and single charges) so the app doesn't rely on
pre-defined config options. This means you can define different price plans
(to allow access to different 'packages').
Although I might look at using a 'freemium' config option, if I can figure
out a nice workflow.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ohmybrew/laravel-shopify/issues/76#issuecomment-415407279,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTuOvlKs7bYjB4ipQG4c-d8FK1SxR4uks5uTqjkgaJpZM4WAD9d
.

Possibly, but the reason I did it was so I didn't need this package 😛 However, the Shop Auth and Billing packages I made do use your Shopify API package, and the Shop Auth is mostly based on this one, but stripped back.
I'll most probably look at tidying up the auth package to make it as streamlined and flexible as possible (tbh, its quite lightweight already, more a case of tidying up the code)

Ah very good, was just curious! I'll continue on a freemium idea/multiple plans :) thanks!

Just taking a look at this now for my billing package.
I'm thinking, have the freemium flag in the config, along with a flag for single or recurring charge, and the prices for both etc.
So, if the app if free to install, bypass all billing and handle charges via the app later on OR the app is installed, and its either a one off cost (defined in config) or a recurring cost (also defined in config).
You can then also do additional billing stuff after the app is installed and paid for.
The only issue I can see is relying on having the installation costs in the config. Might be good to pull them from a database possibly?

So you're thinking. Just plain have freemium, one time or recurring in the
config, any other plans, handle outside of that?
I thought about using a table for plans but I figured this would be more
lightweight on someone to manage. Have the plans listed in the config as an
array, then pass the index to the billing controller which pulls that plan
from the array of plans.
On Thu., Aug. 23, 2018, 12:49 p.m. Paul Canning<EMAIL_ADDRESS>wrote:

Just taking a look at this now for my billing package.
I'm thinking, have the freemium flag in the config, along with a flag for
single or recurring charge, and the prices for both etc.
So, if the app if free to install, bypass all billing and handle charges
via the app later on OR the app is installed, and its either a one off cost
(defined in config) or a recurring cost (also defined in config).
You can then also do additional billing stuff after the app is installed
and paid for.
The only issue I can see is relying on having the installation costs in
the config. Might be good to pull them from a database possibly?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ohmybrew/laravel-shopify/issues/76#issuecomment-415456332,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTuOjyslcYktRTdmyTgCXxu3Jly5Wb1ks5uTsf4gaJpZM4WAD9d
.

Yes, so if freemium, bypass billing on install, but have various billing options in the app for extra features etc, otherwise, on install, do a recurring or single charge, as defined in the config (or database perhaps).
I added some Plan & Package stuff into my billing package, but it's not complete yet. Plans are simply defined in the database (could make a CRUD screen somewhere) and they can be linked to different 'packages' - the idea being to let a user access a controller based on the packages they have.

Ohh very good point on the access.. maybe this will have to be in the
database afterall.
In the case of it being in database what would be a good way to charge a
customer on install, have config reference the plan ID or have a plan
flagged in the database as the one to use for install?
On Thu., Aug. 23, 2018, 1:14 p.m. Paul Canning<EMAIL_ADDRESS>wrote:

Yes, so if freemium, bypass billing on install, but have various billing
options in the app for extra features etc, otherwise, on install, do a
recurring or single charge, as defined in the config (or database perhaps).
I added some Plan & Package stuff into my billing package, but it's not
complete yet. Plans are simply defined in the database (could make a CRUD
screen somewhere) and they can be linked to different 'packages' - the idea
being to let a user access a controller based on the packages they have.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ohmybrew/laravel-shopify/issues/76#issuecomment-415465212,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTuOgaGsrRFXeV5KlkYoKR4q14JelXbks5uTs33gaJpZM4WAD9d
.

Either or I guess!
Just doing this all now myself so I'll figure it out :)

A flag for the plan in database sounds better at first thought..
freemium in config, if false, and billing enabled, find the plan in the
database that's on_install or something...
On Thu., Aug. 23, 2018, 1:20 p.m. Paul Canning<EMAIL_ADDRESS>wrote:

Either or I guess!
Just doing this all now myself so I'll figure it out :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ohmybrew/laravel-shopify/issues/76#issuecomment-415467254,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTuOhhbpw0lhMZKXRqo2e_qK6o-QiSzks5uTs9RgaJpZM4WAD9d
.

(Started a branch for this)[https://github.com/ohmybrew/laravel-shopify/tree/76-multi-plans].

Yup! Already committed code for the database method. I store the name,
price, type, on_install flag, trial days, test flag, etc.
The charges table has a reference to plan_id (if applicable for the
charge), and shop table has a plan_id along with a new freemium flag.
I redid the billing controller to accept an optional plan_id param. If one
exists, it uses it for billing, if blank, it find the plan flagged
on_install and uses that.
Surprisingly did a lot for a couple hours, I have to mod one more file, and
begin redoing the unit tests and should be ok.
On Sat., Sep. 1, 2018, 6:53 a.m. Nathan Pope<EMAIL_ADDRESS>wrote:

I like the idea of storing plan information in the database.
Then for storing the selected plan we could do something very simple like
this:
shop_plans
shop_id plan_id
1 2
2 1
Or it might make more sense just to place the plan_id on the charges
table. I'm not sure which is best.
Just looking at all the information here on this simple layout I think it
would be too clunky to store this in an array on a config file. I think
using the db would be best.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ohmybrew/laravel-shopify/issues/76#issuecomment-417845870,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTuOr0bT32diwm-Es-Uphbbqe_k9m_Hks5uWlIdgaJpZM4WAD9d
.

Can you make sure this works with existing versions? I already have a custom plan method that I've created and would like to keep it for now. I'm afraid if I update it would break my existing plans.
If anyone is interested in how I solved this. I created a Plan model with no relationships and then attaching it to the Shop model like below.
public function plan()
{
        return Plan::where('name', '=', $this->current_charge()['name'])->first();
}

public function current_charge()
{
       $charge = $this->charges->where("status", "=", "active")->first()->retrieve();
       return collect($charge);
}

Not sure it's possible to make it work with current version as its a whole
new table, and two indexes, plus the changes to the billing controller. Can
probably migrate your plan from the config to the database, and add the
on_install flag, and update all shop entries to be plan_id=thatID, and
things should work.
On Sat., Sep. 1, 2018, 2:05 p.m. Cory Fail<EMAIL_ADDRESS>wrote:

Can you make sure this works with existing versions? I already have a
custom plan method that I've created and would like to keep it for now. I'm
afraid if I update it would break my existing plans.
If anyone is interested in how I solved this. I created a Plan model with
no relationships and then attaching it to the Shop model like below.
public function plan()
{
return Plan::where('name', '=', $this->current_charge()['name'])->first();
}
public function current_charge()
{
$charge = $this->charges->where("status", "=", "active")->first()->retrieve();
return collect($charge);
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ohmybrew/laravel-shopify/issues/76#issuecomment-417871195,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTuOt5tkjjoC-28p8vtPaAFBnlEl8tHks5uWrdBgaJpZM4WAD9d
.

@ohmybrew ah yes, I must have missed that commit message earlier. It's looking great 👍

Completed the code today, all tests passed. Just need to do some physical testing now, but hopefully that goes fine!
Seems upgrade path would be to run the new migrations, create a default plan in the database with on_install set to true, update all non-grandfathered shops in the database to plan_id = X, and make a few changes to the config file.

Hey all
Sorry for the delay on this - been super busy. However I sat down tonight to go beyond the unit tests and do real world testing; I'm pretty happy with the results of all our combined thoughts on this.
Freemium + Billing enabled:

Shop gets installed
Flagged as freemium
Upgrading to a plan removes freemium and sets a plan, plus a charge to the shop

Non-Freemium + Billing enabled:

Shop gets installed
Default plan gets set based on on_install
Uprading to another plan via route link to /billing, cancels the old plan, sets a new plan to the shop plus a new charge log

Things seem to be working as expected, I think I'll release this the weekend. :)

Would this also work for:
Freemium + charge per use?
On Thu, Sep 6, 2018 at 9:37 PM Tyler King<EMAIL_ADDRESS>wrote:

Hey all
Sorry for the delay on this - been super busy. However I sat down tonight
to go beyond the unit tests and do real world testing; I'm pretty happy
with the results of all our combined thoughts on this.
Freemium + Billing enabled:

Shop gets installed
Flagged as freemium
Upgrading to a plan removes freemium and sets a plan, plus a charge
to the shop

Non-Freemium + Billing enabled:

Shop gets installed
Default plan gets set based on on_install
Uprading to another plan via route link to /billing, cancels the old
plan, sets a new plan to the shop plus a new charge log

Things seem to be working as expected, I think I'll release this the
weekend. :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ohmybrew/laravel-shopify/issues/76#issuecomment-419293068,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGsrEI4mNZJTvTfSLVjAMFWgC-JDzTGmks5uYc3xgaJpZM4WAD9d
.

--
Cory C. Fail
Software Engineer
coryfail.com /<PHONE_NUMBER>

@fyroc Sorry been busy! Actually, slipped my mind. But you can not do freemium plus charge per use. Usage charges require a recurring charge. Work around for this is to create a recurring charge that's $0, with a capped amount, then Ty

I've just commited code to support usage charges directly for ease (untested), will be unit testing and physical testing it tonight.
Sending a get/post to /billing/usage-charge, with a price and description, plus a signature (which is price + description + app secret key) will grab the shop's latest recurring charge, create the usage charge, log it in the database, and link it to the recurring charge as well.
It will show an error view if an error occurs, as per support for #96, and can redirect either back to the original spot the form/link was, or if you supply a redirect url, it will go there.

v4.0.0

This is a good way to upgrade freemium to paid reccuring plan, but what if someone want to downgrade paid to freemium mode?
How we can handle this situations?

You'd have to cancel the plan, then set them as freemium. You could do this
currently with the package methods.
On Fri., Feb. 26, 2021, 16:23 manishelsner<EMAIL_ADDRESS>wrote:

This is a good way to upgrade freemium to paid reccuring plan, but what if
someone want to downgrade paid to freemium mode?
How we can handle this situations?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/osiset/laravel-shopify/issues/76#issuecomment-786860496,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASO4OVD6DCWANTEMK735WLTA732BANCNFSM4FQAH5OQ
.

I have already look too much for this code, can you suggest me which function or method? please.

You can use the cancel plan action....
Something like:
use Osiset\ShopifyApp\Actions\CancelCurrentPlan;

# ...

$cpa = resolve(CancelCurrentPlan::class);
$cancelled = $cpa($shop->getId());

if ($cancelled) {
    $shop->plan_id = null;
    $shop->shopify_freemium = true;
    $shop->save();
}

Something like that

@osiset I used the code given below but it is not working. it showed the error like "Can only instantiate this object with an int". in the above code where I can find $shop instance.
`      $shop = Auth::user();
$cpa = resolve(CancelCurrentPlan::class);
$cancelled = $cpa($shop->getId());
    if ($cancelled) {
        $shop->plan_id = null;
        $shop->shopify_freemium = true;
        $shop->save();
    }`


[catch2] Update to 3.3.2

Update catch2 from 3.3.1 to 3.3.2 : https://github.com/catchorg/Catch2/releases/tag/v3.3.2

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

The usage has been tested successfully locally.
find_package()
target_link_library()

@jimwang118 Why are we changing the versioning scheme?


Big spec file

Has my application grow, the spec on my controller become heavy. I thought about creating one file by action. I'll end with the architecture :
specs/controller/api/users/index_spec.rb
specs/controller/api/users/create_spec.rb
...
Do you think it's a good idea ?

It's up to you how you feel you should structure your tests, the way you suggest will cause you no issues. However Github issues are not the place to ask this sort of advice, in future please use the irc channel (#rspec on freenode) or the mailing list / google group (https://groups.google.com/forum/#!forum/rspec)

If your logic is so complicated that it requires a very large spec file, it may be telling you something about the complexity of your implementation and suggesting that you should perhaps refactor it to be composed of multiple smaller pieces.


Question about the tf_family.txt mentioned in getMotif2Gene(...)

Hi, in the chapter 11.5 getMotif2Gene of the manual, you mentioned that a tf_family.txt file should be prepared, but I am not familiar with such data. Could you please give some advice about how to get such a tf_family.txt? Thank you!

You can download the tf family information at http://bioinfo.life.hust.edu.cn/AnimalTFDB/#!/download.

That's great! Thank you!


Adding warnings field to Cassandra traces table

Signed-off-by: Aditya Kumar Praharaj<EMAIL_ADDRESS>
Which problem is this PR solving?

Resolves #705 - namely adds the field Warnings to the traces table in jaeger's cassandra keyspace.

Short description of the changes

This diff adds the Warnings field in traces table and renames the subsequent table to traces_v2. It accompanies migrations v003.cql.tmpl which is the CQL schema files and two subsequent migration scripts from moving to traces_v2 from traces:

migration/v002tov003part1.sh: Alters existing traces table to add the column and creates a new traces_v2 table as well. Copies existing data from traces to traces_v2.
migration/v002tov003part2.sh: Truncates and deletes traces table.

It makes changes to SpanReader and SpanWriter to actually read from traces_v2. This is backwards compatible and falls back to using traces if the traces_v2 table actually doesn't exist (which means the migrations have not been carried out).

Followup

Create the same changes for Elasticsearch Backend.
Propagating and showing these in the UI.

A few thoughts:

pr #1924 is already introducing changes to the DB schema, we should combine them to minimize dB migrations
it is preferable if the code works both with the old and new schema and just automatically  adjusts to the presence or absence of the additional columns. An example of that can be found in the handling of the dependencies table.

Hey Yuri!
Thanks for the comments. Would appreciate if you can clarify some points:

I saw the issue linked above (#1924), and it seems like the changes are not merged. After those changes are done (or before) - I will make my changes on top of those. Along those same lines:

What is the strategy for DB migrations? Should all the subsequent DB migrations since V2 be merged in a single file?
What about handling these in code - does the code need to actually handle all the possible states between migrations? That seems necessary though unsustainable.

Thanks. I have tried to add that by having both V1 and V2 versions of query statements and automatically detecting which columns to read / update depending on the state of the keyspace at runtime. (Please refer to changes in cassandra/spanstore/reader.go, cassandra/spanstore/table_version.go and cassandra/spanstore/writer.go).

Sorry for so many questions. Just trying to get a general sense of things cause this is my first diff here.

The PR (#1924) needs some work, but it should happen shortly. It currently does not implement backwards compatibility (e.g. by [interrogating table metadata[1).
It is ok to have an additional migration script, but they should all be wired together for "upgrade for next release", AND it's better to combine changes into a single V3 full schema file.
Handling in code - we usually keep compatibility for a 1-2 releases then remove the old code. Initially the code only needs to be compatible with the previous version of the schema.
The dependencies table example is not quite right for this change, because that one required full schema change (we were switching from SASI indices to direct lookups). Your change is much less intrusive, it's only adding one optional, non-indexed column, so creating a whole new table for that is overkill, we should simply alter the existing table.
Speaking of schema changes, we're actually planning to implement an alternative format for storing spans in Cassandra, as Protobuf blobs instead of fully typed schema. This should make Cassandra storage much more performant, and would automatically include the extra column (that would warrant traces_v2 table).  Would you be interested in working on that instead?

Yeah that sounds interesting. I would like to take that up as well. Let me try to  refactor this diff for the changes suggested in the meantime.

storing spans in Cassandra, as Protobuf blobs instead of fully typed schema

Will Jaeger use a compressed format? Like use zstd to compress after protobuf serialization.

Compression should definitely be an option. @vprithvi experimented with trained zstd in the past, it easily achieved 8x compression ratio.

Closing due to inactivity.


Dev/nigelhew

Updated docstrings in workflows.py.

Question: What is the return type in def charge_density_difference?

Small fixes to eos_fit.py

Removed some redundant code. I think plot_mv should be moved to magnetism.py

Small reformatting changes to data_extraction.py and aggregate_extraction.py

Actually, let me move plot_mv in the other pull request.

Actually, let me move plot_mv in the other pull request.

Thanks.


Release heapster v0.6

Added a service for heapster to access the '/validate' endpoint.

LGTM

Wonder why travis is slow.


Farsi Translation

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Thank you for working on this @silvercover ! I'll convert this to a draft for now while it's in progress, but feel free to convert it back when you're finished!

[x]  Have you followed the contributing guidelines?
[x]  Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Acces

Hi. Thanks for the emails and invitation to be a part of this. I have a lot of questions and I have a lot to learn about all of this. Tomorrow morning I'll go through the documents that GitHub offers to those of us who are beginners with coding. I'm clueless as to why so many people have been working on my phone. Mozilla and Google developers as well as USDA, National Science Foundation, Stacked, NIST, CIS.... I don't know what to think. Because of the many experiments logged in my phone and the death threats to be a live subject in the the entertainment business ownership of people. I've been overwhelmed with all of this and I would like to know what is going on. This hasn't exactly been a fair set-up, as I'm outnumbered and deemed the "enemy" from the other people who have focused on my life with constant contact within their own agenda for me trapped in this scandal.

Code

Thank you for working on this @silvercover ! I'll convert this to a draft for now while it's in progress, but feel free to convert it back when you're finished!

I've done the whole translation. please undo draft status. also I want to mention Farsi is RTL language and I think some tweaks and style editing needed.

☺

Would you please review my pull request?

☺

Would you please review my pull request?

Thank you for the translation work! I'll merge this when the tests pass.

@silvercover Would you mind trying to merge or rebase latest master into your PR? Hopefully the tests will get triggered by that. Thank you!

@itsbagpack Thanks for your help. please see this:

what should I do then?

@silvercover Hi, as per my earlier comments and your screenshot, the build is stuck. As such, I suggest merging latest master into your branch to hopefully kick off a new build.

@itsbagpack @silvercover Hi, I just merged the latest master. I hope it helps.

@silvercover What's the latest status of this? Thanks!

@silvercover What's the latest status of this? Thanks!

Hi, I get these messages and don't know what to do.

@silvercover I have to manually enable CI when you push new commits. There's another error here: https://github.com/github/opensource.guide/pull/2351/checks?check_run_id=3554172773#step:7:29

@MikeMcQuaid
as for this, we've reviewed it again and found nothing to fix.
I don't know what control characters caused this.

Jovan Ramirez
lunes, 13 de septiembre 2021, 1:09 +03:00 de MaryJaneLove4 @.>:
@. approved this pull request.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly,  view it on GitHub , or  unsubscribe .
Triage notifications on the go with GitHub Mobile for  iOS or  Android .

@silvercover You can push new commits now and it'll retest automatically. I'm afraid I can't merge until we figure out the failures here 😭

@MikeMcQuaid Hopefully I fixed few errors and warnings and now there is only 1 warning which I really don't have any clue about it in this file:
how-to-contribute.md
137:1-137:57  warning  Missing blank line before block node  no-missing-blank-lines  remark-lint

@MikeMcQuaid All checks have passed!
🥳

@MikeMcQuaid Thank you.
Since Farsi is RTL language, what's your suggestion on making this RTL. I don't know whether putting <div dir='rtl'>  at the beginning allowed or not.

@silvercover you're welcome!
I'd suggest something dynamic/conditional like https://github.com/github/opensourcefriday/blob/7ce1cdc59edc6840b390c2d02259878fb8c9c606/app/views/layouts/application.html.erb#L2 should be added (but will use Liquid rather than ERB). Could you open a PR for discussion?


the mAP compared to py-faster-rcnn

sorry to bother you again.
I find it your checkpoint given is about 65% mAP on pascal 2007 test set.
does it need more iters to train?
I also train for about 70k iters but can only reach 50% mAP.

I noticed that, too. And I'm working on this problem.
Some code (VGGnet_fast_rcnn_iter_70000.ckpt) was based on caffe model, in the shape of 1xCxHxW, so it needed a lot transpose and reshape before and after anchor layer and rpn layer.  While I tried to simplify this process, I did some modification in these layers. That explains why there is a drop in mAP with the provided model.
I also found out the parameters, like BBOX_INSIDE_WEIGHTS, BBOX_NORMALIZE_STDS, matered a lot, which I tried to get rid of them, because I thought it's too complex for understanding.
I'll reconsider to add the paramters.
Thank you for your important feedback!

@xinghedyc
I did a small modification in proposal_layer_tf.py.
Now we can evaluate the old model via:

uncomment scores = rpn_cls_prob_reshape[:,:,:,_num_anchors:] in proposal_layer_tf.py
run  ./experiments/eval/voc2007_test.sh

I got the same results:
AP for aeroplane = 0.6980
AP for bicycle = 0.7883
AP for bird = 0.6566
AP for boat = 0.5602
AP for bottle = 0.4778
AP for bus = 0.7620
AP for car = 0.7971
AP for cat = 0.7927
AP for chair = 0.4781
AP for cow = 0.7243
AP for diningtable = 0.6478
AP for dog = 0.8020
AP for horse = 0.7968
AP for motorbike = 0.7319
AP for person = 0.7706
AP for pottedplant = 0.3827
AP for sheep = 0.6642
AP for sofa = 0.6503
AP for train = 0.7660
AP for tvmonitor = 0.6669
Mean AP = 0.6807

@CharlesShang thanks a lot!
I'll try it, and if I wanna train the model from the start, should I take 70k iters which 50k for learning rate of 0.001 and the rest 20k iters for learning rate of 0.0001?
I find your config file that learning rate is divided by 10 every 30k iters.

This is from the original paper.

We use a learning rate of 0.001
for 60k mini-batches, and 0.0001 for the next 20k
mini-batches on the PASCAL VOC dataset. We use a
momentum of 0.9 and a weight decay of 0.0005

@CharlesShang Hi, I read your readme about kitti converting to pascal format.
Does kitti test set has labels?
And how much memory does it cost when training on kitti, I'm using gtx1080 and get a out of memory abort in the trainning time.
Thanks.

KITTI does not provide testing labels.
GTX1080' RAM is enough for training 2xkitti (about 700x2400).
There's a recent paper, A Unified Multi-scale Deep Convolutional Neural Network for Fast Object Detection, disscussing the parameter setting for kitti. Scaling the input image by 1.5~2 will results about 3 percents gain in mAP.

thanks a lot for your information！

So far, I got the mAP 0.65 after 70k iters training, still toooooo low for us.
I did a little modification in the loss layer, I'll retrain on voc07 for 70iters with the exactly same paramesters.

@CharlesShang If I want evaluate the checkpoint trained myself on pascal and kitti, Do I need to uncomment the line scores = rpn_cls_prob_reshape[:,:,:,_num_anchors:] in proposal_layer_tf.py?

If I want evaluate the checkpoint trained myself on pascal and kitti, Do I need to uncomment the line scores = rpn_cls_prob_reshape[:,:,:,_num_anchors:] in proposal_layer_tf.py?

The answer is yes.
    # TODO: NOTICE: the old version is ordered by (1, H, W, 2, A) !!!!
    # TODO: if you use the old trained model, VGGnet_fast_rcnn_iter_70000.ckpt, uncomment this line
    scores = rpn_cls_prob_reshape[:,:,:,_num_anchors:]

Plz notice the order is different.
In the old implementation, the rpn_label is ordered by (H, W, 2, A), A is the number of anchors.
To be more elegant,  I change that to (H, W, A, 2), just like the rpn_boxes.

So far, the best mAP I got after 80k iters is 0.685 (0.699 in the original paper).
There're still improvement, like tuning loss_weight, adding regularization (there is no regularization in the current version).
Now I'm closing this issue.
I'll solve it in a few days.

I met the same problem. I train the resnet50 70000iters, but the result is just 0.29, and after uncomment the line, the result is 0.128...

How can I get the value of mAP?

How can I get the value of AP? Please tell me,   please ,please~


Vs code window relaunch/reload option

It is a feature request - please add option under file menu to relaunch the vs code current window or workspace.

Do you know about the Developer: Reload Window command in the Command Palette (F1)?

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Options error: --secret fails with '/etc/openvpn/secret.obfs4.key': No such file or directory

I know this sounds stupid but i have no idea where to get secret.obfs4.key

Hi,
It seems that you did realize how to do it in the end. But if you think that the inline comments (or documentations) could be improved to avoid these kinda confusions for others, please do tell.

Sure I will add some further explanation that is commented in the scripts, into the Readme


Virtual: View Checkins displaying empty tables when "Go" button is clicked without selecting any value in dropdown Disaster

Steps to follow:
a) Login to the Crisis Check-In application
b) Click on the link View checkins
c) Click on "Go" with out selecting any values in Disaster dropdown
d) Observe that blank table are displayed
Expected Result: The user should be either prompted to select value in Disaster dropdown/ OR information related to all disasters should be displayed instead of blank tables
Priority: 1

Milestone - Features backlog


About world coordinates of D435 in realsense-viewer

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ D435 }

Firmware Version
(<IP_ADDRESS>)

Operating System & Version
Linux (Ubuntu 16)

Kernel Version (Linux Only)
(4.15.32)

Platform
PC

SDK Version
{ legacy / 2.<15> }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
Hi, in projection in Realsense SDK 2.0 it is written that the positive x-axis points to the right, the positive y-axis points down, and the positive z-axis points forward. However, in realsense-viewer the coordinate system looks different ( x to left, y points up). What is the reason for that? I also shared a ss for making my question clear. Thanks in advance.

I don't have the answer for this question, but the I noticed that the axis orientation is also not the same between the Viewer visualization and the point cloud capture itself. So, as you said, there is indeed a difference with the different axis definitions.
Point cloud in the Viewer (lets assume X goes to the right, Y up and Z forward for the depth) :

Same point cloud in Meshlab (the coordinates are not really what you would expect from the Viewer as Y is pointing down, but they match with what the documentation says) :

[Realsense Customer Engineering Team Comment]
The points are calculated by rs2_deproject_pixel_to_point.
https://github.com/IntelRealSense/librealsense/blob/master/include/librealsense2/rsutil.h#L50
and in other hands, the green axis points to Y-, in the realsense-viewer.
https://github.com/IntelRealSense/librealsense/blob/master/common/rendering.h#L1210
That is the difference what you see.

[Realsense Customer Engineering Team Comment]
@kubrakaracan  Any other questions about this ticket? Looking forward to your update. Thanks!

Thank you for your answer! but I meant to say that why y-axis points to upward in realsense-viewer render? Should it point to downward as written in the document? I also checked the rendering algorithm you posted, and it is also written in positive manner. if y-axis points upward then x-axis in realsense-viewer points inversely?

I got the point now, thank you so much !!


Add continuous integration

The project needs github actions workflows for testing, linting, releases, docs builds, etc set up still.
References:

https://github.com/parafoxia/analytix/tree/main/.github/workflows
https://github.com/Jonxslays/wom.py/tree/master/.github/workflows

I'm not sure it's actually best to be running the nox sessions, and instead have the installation and run steps separate, if only to incorporate layer caching.


The withDefaults function loses arguments when assigning a function default value

Version
3.2.26
Reproduction link
sfc.vuejs.org/
Steps to reproduce
const props = withDefaults(defineProps<{
  fn?: (name: string) => void
}>(), {
  fn(name: string) {
    return name.toUpperCase()
  }
})
console.log(props.fn)

What is expected?
Returns the correct default value
What is actually happening?
Function defaults lose arguments

Arrow function seems to work

Arrow function seems to work
Can you give me a simple example? It doesn't seem to work if I try
sfc.vuejs.org/

example

example

Thank you, but why doesn't my way of writing it work? I think it's still a bug

When using a method like you do, you would have to explicitly type this: undefined as the first argument of the method.

When using a method like you do, you would have to explicitly type this: undefined as the first argument of the method.

I specified this: undefined as you said, but it still does not work properly. I have tried three ways of writing, maybe you need to teach me
sfc.vuejs.org

The mentioned fact that you need to use an arrow function or annotate this properly is documented here:
https://v3.vuejs.org/guide/typescript-support.html#annotating-props
But indeed, a method with this: undefined doesn't work work on withDefaults().  But it does with arrow functions. Not sure if this is a necessary consequence of the TS limitation mentioned in the docs or we can fix it.

I created a PR for this problem https://github.com/vuejs/core/pull/5615


fix(themes): :bug: fixes plugins to work with pro repeaters

It fixes Tailwindcss/Windicss/Unocss to not get repeaters invalid state for inner inputs states.
It adds a new feature of grouping that came with Tailwindcss 3.2, that makes it possible to target groups when specifing variants to nested rule sets, by setting a group/* to the outer class of the element you want to group and to adding formkit-invalid/*:text-red-500 to the section you want to style based on the group state.

I will add documentation about it the new feature and the examples of using it.

I'll be honest. I dont know tailwind well enough to know if this is good 😂 but I trust you on this one @GustavoFenilli


Emit old value on input

Hi Damian,
thank you for this amazing plugin. I'm working on project, where I need to grab the original value on input change in a case of a reset if API call fails. Would it be possible to emit the old value alongside the new value, please?
Thank you

@cizza Please keep a reference of old values in your project.


licence

Hi, I can't find the licence of the dataset, can you make it visible or point me to it?

Hi, thanks for your interest in the Amazon Reviews dataset! Regarding license, please refer to #1.


Cleanup: updated text referring to web console

@ALRubinger mind taking a look at this?

merged: https://github.com/openshiftio/appdev-documentation/commit/3f1b536c22ccb20180024b561b929ab8bf94274a


Artificial dataset test failure - Warning about singular matrix

A second group of failures. The following warning is raised :
logs/test_artificial_1024_cumsum_constant_5__20.log:UserWarning: Singular matrix in solving dual problem. Using least-squares solution instead.
sample script :
tests/artificial/transf_cumsum/trend_constant/cycle_5/ar_/test_artificial_1024_cumsum_constant_5__20.py

change the solver ... force svd => no warning
accodrding to this doc :
http://scikit-learn.org/stable/modules/generated/sklearn.linear_model.Ridge.html
This is a quite good fix but will change all AR/ARX models => run all the tests before commit.


[iot] identity_assignment is called on another thread

I discovered a problem with iot module:
https://github.com/Azure/azure-cli/blob/9ef066f0571b8c4f03af32c439e669a14b563b85/src/azure-cli/azure/cli/command_modules/iot/custom.py#L588-L590
polling=True causes SDK to start a separate thread to do the LRO polling. Even if identity_assignment fails, it fails in that separate thread, so the main thread running the CLI command still succeeds, which is not expected.
Originally posted by @jiasli in https://github.com/Azure/azure-cli/issues/25452#issuecomment-1430959244

route to service team

Please also see https://github.com/Azure/azure-cli/pull/17185

Merged. closing issue


[BOW-110] Implement curl downloader

Codecov Report
Patch and project coverage have no change.

Comparison is base (31b4efa) 15.88% compared to head (40e45fc) 15.88%.

:exclamation: Current head 40e45fc differs from pull request most recent head 6dd9a2b. Consider uploading reports for the commit 6dd9a2b to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #116   +/-   ##
=======================================
  Coverage   15.88%   15.88%
=======================================
  Files           5        5
  Lines         957      957
  Branches        2        2
=======================================
  Hits          152      152
  Misses        805      805

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


Does not change VR LOD Settings

Hello, I gave this a go and managed to get it working well in 2D!
However the TLOD and OLOD values only change in the 2D sim settings, not the VR sim settings.
Any plans to add that functionality? This would be great for VR!

Nope, not planned.
And "2D" is a bit wrong. VR is also just a 2D Projection of a 3D Scene, you just have two different 2D Projections so that your Brain can be tricked.

Understood thanks.
Does having different settings in the separate menus (Monitor & VR) for LOD's create any issues?
Thanks for the great work!

Don't know, I don't have a VR Headset.
But as you see in the UserCfg.opt, it is two different Parameter (two different Sets for each Mode) - don't know why Asobo made it that Way when the Settings need to be the same in both Modes. Of course there is always the Chance that Asobo messed up something and did not fix it yet (ever?) 😅

From my understanding of reading about this on the official MSFS forums, the only mirror between Monitor and VR is for the mouse clicking. So apparently both values of LOD (Monitor & VR) are independent.
If there is any way that us VR users could be able to tweak this application to change the VR Settings Values for LOD instead of the Monitor Setting values, please do let me know.
This would be an absolute game changer for many VR users!
Apologies for the persistence and many thanks once again.

Hey, the Code and Method are open - you're free to dig into that and tell me the Offsets/Pointers to use afterwards 😉

I wouldn't have the faintest clue where to start digging.
But I'm hoping that someone far more clever than me could give it a go and figure it out :)

Any plans on fixing the thing that's a bit wrong about it in an update? It works like a charm. Could be the biggest thing yet for improved performance on approach and on the ground.

FYI, there are two offsets (they seems to be doing the same thing) which you can read to know the VR mode is active, which is likely useful to make the switch between settings automatic.
FlightSimulator.exe+765B694
FlightSimulator.exe+765B704
Both are DWORDS ( 4 bytes ), and the value it's 1 if VR Mode is enabled, otherwise they are 0.


IbkrWsKey should have conid for market data subscriptions

Problem description
Market data subscriptions require a complex key smd+conid+{...}. The IbkrWsKey enum does not account for the possibility of having a conid as a part of the channel.
The inconsistent usage of keys in the QueueController and SubscriptionController makes this issue a bit harder to mitigate. The QueueController is using the IbkrWsKey enum as keys. While the SubscriptionController is using the key.channel string as keys.
Trying to be smart and getting the conid from the data dictionary:
class MyIbkrSubscriptionProcessor(SubscriptionProcessor):
    def make_payload(self, channel: str, data: dict) -> str:
        conid = data['conid']
        json_data = data.copy()
        del json_data['conid']

        payload = f"{channel}+{conid}+{json.dumps(json_data)}"

        return payload

    def make_subscribe_payload(self, channel: str, data: dict = None) -> str:
        return f"s{self.make_payload(channel, data)}"

    def make_unsubscribe_payload(self, channel: str, data: dict = None) -> str:
        return f"u{self.make_payload(channel, data)}"

subscription_data = {
    'conid': gc_futures[0]['conid'],
    'fields': [
        FIELD_BID_PRICE,
        FIELD_ASK_PRICE,
        FIELD_BID_SIZE,
        FIELD_ASK_SIZE,
        FIELD_LAST_PRICE,
        FIELD_VOLUME,
    ]
}
processor = MyIbkrSubscriptionProcessor()
key = IbkrWsKey.MARKET_DATA
ws_client.subscribe(channel=key.channel, data=subscription_data, subscription_processor=processor)
accessor = ws_client.new_queue_accessor(key)

results in unexpected behavior that generates additional logging:
IbkrWsClient: Handled a channel "md+712565966" message that is missing a subscription. Message: {'server_id': 'q1', 'conidEx': '712565966', 'conid': 712565966, '_updated':<PHONE_NUMBER>282, '6119': 'q1', '85': '5', '88': '11', '86': '2452.50', '84': '2452.20', 'topic': 'smd+712565966'}
actual value from get(...): {712565966: {'conid': 712565966, '_updated':<PHONE_NUMBER>282, 'topic': 'smd+712565966', 'market_data_marker': 'q1', 'ask_size': '5', 'bid_size': '11', 'ask_price': '2452.50', 'bid_price': '2452.20'}}

which forces the silencing:
logger = logging.getLogger('ibind.ibkr_ws_client')
logger.level = logging.ERROR

Solution

QueueController and SubscriptionController should use the same keys.
IbkrWsKey should provide a way to incorporate a conid for market data subscriptions

Recommendation
Add the option to skip key remapping and just return the raw message as is. If I supply field '84' (bid price) I would like to get a dictionary with key '84' and not 'bid_price'. Having the fields as constants is more than enough to write readable code. No need for the processing overhead.

Hey @teodorkostov many thanks for describing your issue in detail 👍

Market data subscriptions require a complex key smd+conid+{...}. The IbkrWsKey enum does not account for the possibility of having a conid as a part of the channel.

Indeed it does require it. The solution I've been running with is to include the conid with the channel string, such as:
ws_client.subscribe(channel='mh+265598', ...)
# or
key = IbkrWsKey.MARKET_DATA
ws_client.subscribe(channel=f'{key.channel}+265598', ...)

The reason being - from standpoint of both our client and IBKR servers (as far as I could empirically see) if a conid is present, it is married into the channel name:

We store the channel+conid pair internally and manage subscriptions, unsubscriptions and resubsriptions based on it
We unsubscribe using the same channel+conid pair
IBKR gives us a server (or an equivalent of) for each channel+conid pair

In essence, the channel+conid pair becomes a de-facto channel name that we subscribe to. It was a choice of simplicity to treat it as just the channel argument.
You can see it being used in this form in these two examples:

https://github.com/Voyz/ibind/blob/master/examples/ws_02_intermediate.py
https://github.com/Voyz/ibind/blob/master/examples/ws_03_market_history.py

Can you see anywhere in the code that would benefit from having these two stored separately?

The inconsistent usage of keys in the QueueController and SubscriptionController makes this issue a bit harder to mitigate.

This is a fair observation, and I'm glad you've pointed it out. I've gone over the code once again to see why was this the decision. Indeed, the answer is related to channel+conid pairs.
Why SubscriptionController uses strings?

Subscriptions make sense if we treat them as strings, containing either channel or channel+conid. A subscription to the same channel but to a different coind should be treated as a separate entry and handled individually. The unique key to a subscription is indeed the channel and its parameters.
Hence, the SubscriptionController uses strings - to represent channels with its parameters (if present), such as tr or mh+265598.

Why QueueController uses enums?

However, when we receive the data from IBKR we don't get it nicely segmented based on conid - it is just fed to us through the WebSocket. We do a little bit of parsing to figure out which channel it came from, but other than that it is just data. If I recall correctly some channels' data doesn't even contain the conid in its messages despite being needed for subscribing.
Hence, the part of the interface that exposes data consumption - QueueController - uses IbkrWsKey enum with a 1-1 mapping to channel names. It doesn't support channel parameters, such as conids (or channel+conid strings), since we cannot assume that all data sent to us will have it. If it does you'll need to do the parsing in your application, which usually is quite trivial. Instead of enums we could use strings that only contain channel names, but I find enums safer and more readable.

Would you have any suggestions on how to improve this?

Sorry, I only just noticed your recommendation is related to a slightly different issue:

Add the option to skip key remapping and just return the raw message as is. If I supply field '84' (bid price) I would like to get a dictionary with key '84' and not 'bid_price'. Having the fields as constants is more than enough to write readable code. No need for the processing overhead.

Yes, absolutely, we can do this. Got it implemented, I'll publish it in the next release.

I do agree that it is possible to make it work. However, think about the ibind API from the perspective of a new user. The person does not know how the internals work. To make it work some advanced examples have to be read. Some of the framework code has to be explored.
It would be better for the design to guide the user.
What if the methods accept a dataclass and not the enum/string?
@dataclass(frozen=True)
class Subscription:
    key: IbkrWsKey
    conid: str = None  # or List[str]
    data: ... = None

    def __post_init__(self):
        val(self)

subscription = Subscription(...)  # should throw an error if the optional fields are not defined for the special keys
ws_client.subscribe(subscription)
accessor = ws_client.new_queue_accessor(subscription)

Then the classes could decide what key to use internally. The user of the API does not have to know.
The sooner the user gets an error that something is wrong the better.
What do you think?

Better use a library for that. Something like Pydantic. Data validation is a common problem to solve. It is a certainty that the users of an API will mess up or even exploit it. Minimizing that possibility is good choice.

Sorry, I'm currently travelling, hence sparsely I find time to look into this. Things should be easing out for me in the upcoming months.

What if the methods accept a dataclass and not the enum/string?

Yeah, that seems like a good idea worth exploring. I agree that having a unified interface would be nicer.
Would you like to give it a shot implementing the change? Otherwise, I'm happy to do it once I'm back working.

Hey @teodorkostov just FYI I'm working on this already, you can see the WIP branch here:  https://github.com/Voyz/ibind/tree/subscription-overhaul along with v0.2.0rc1 supporting the new system. I'll fill in more details once I'm more or less happy with it. Would you have time to do a PR review on it once it's ready?


Video / audio sync problem in RTMP streams ingested from Dahua cameras

Which version are you using?
v1.3.1
Which operating system are you using?

[x] Linux amd64 standard
[ ] Linux amd64 Docker
[ ] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
When publishing RTMP streams from Dahua cameras sometimes audio is delayed for about 1 second (more or less).
Describe how to replicate the issue

Start the MediaMTX server
Push RTMP stream from camera (Dahua, e.g. N43CG62) to rtmp://<MediaMTX URL>/test-stream
Play stream with RTMP player, e.g. ffplay -i rtmp://<MediaMTX URL>/test-stream
or record stream with ffmpeg e.g. ffmpeg -i rtmp://<MediaMTX URL>/test-stream -c copy test-stream.mp4

Is the issue is not happening, try again.
Did you attach the server logs?
No
Did you attach a network dump?
Yes (will send by email)

Hello @rudyryk, i took a look at the network dumps through Wireshark, and in particular at the pcap corresponding to the "bad" sample.
For the first two seconds, your camera just sends audio, without video. The first audio sample has a timestamp of "0" and was received at 0.73 seconds:

At 2.1 seconds, video starts to appear, but it has a timestamp of "0" instead of "2.1 seconds":

This video frame is associated with the audio frame that was sent with the same timestamp, that is zero, so the video frame received at 2.1 seconds it associated with the audio frame received at 0.73 seconds, and that is why video and audio are not synced correctly.
This mess is caused by the camera.
In my opinion you can mitigate the issue by using a workaround: in RTSP, contrarily to RTMP, timestamp has a starting value that is random and unique for each track, and a video frame received at X seconds is always associated with the audio frame received at X seconds, regardless of the timestamp field. Therefore, if you publish the stream to the server with RTMP, but you read this same stream with RTSP, the problem will disappear. You can even use FFmpeg to obtain a synced RTMP stream:
ffmpeg -i rtsp://server/unsynced-stream -c copy -f flv rtmp://server/synced-stream

@aler9 Thank you so much, appreciate the help on diving into the problem. We'll pass the information to camera manufacturer.
Btw, the real offset is around 400ms, while the difference between 2.1s and 0.73s is around 1400ms, do you know where is an extra 1s comes from?


Model design

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

Your Assignment is marked, your relationships are bit confusing, one employee can have many shifts, one order can have many sales, and one date can have many sales. you passed the assignment , feedback is to improve your thought process.


Nesting if.bind breaks enclosed binding

There seems to be a problem with nesting if.bind. Consider the following view snippet:
<div if.bind="foo">
    <div if.bind="bar">
        ${baz}
    </div>
</div>

Currently, if foo is set to a falsy value, then the binding on baz will break.
Here is a Plunker that demonstrates the problem.
Maybe this is related to aurelia/binding#215?

@jdanyow Do you have time to look at this?

yep


Issues upgrading to Carbon for IBM.com v1.18.0

Detailed description

Describe in detail the issue you're having.

From a couple of adopters:
We are getting build issue w.r.t ibmdotcom-styles package.

anyone else getting this issue when trying to upgrade to v1.18.0?

warning "<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@carbon/ibmdotcom-web-components ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>
➜  think-2021-nextjs git:(master) ✗ yarn install
Couldn't find any versions for "carbon-components-react" that matches "^7.33.1"
? Please choose a version of "carbon-components-react" from this list: (Use arrow keys)
❯ 7.33.0
  7.33.0-rc.0

Is this a feature request (new component, new icon), a bug, or a general
issue?

Bug

Is this issue related to a specific component?

Application install level

What did you expect to happen? What happened instead? What would you like to
see changed?

No issues upgrading to latest Carbon for IBM.com

What version of Carbon for IBM.com are you using?

v1.18.0

@jeffchew Can this issue be closed?  There is a merged PR.

@RobertaJHahn yes. And why are you working on a Sunday?


feature: 部署策略排序 (closed #857)

Codecov Report

Merging #880 (1fa6d0d) into _V2.2.X_issue#856_857_optimization_policy (fefdf10) will decrease coverage by 0.02%.
The diff coverage is n/a.

:exclamation: Current head 1fa6d0d differs from pull request most recent head 0d41300. Consider uploading reports for the commit 0d41300 to get more accurate results

@@                              Coverage Diff                              @@
##           _V2.2.X_issue#856_857_optimization_policy     #880      +/-   ##
=============================================================================
- Coverage                                      71.03%   71.01%   -0.03%
=============================================================================
  Files                                            294      294
  Lines                                          21597    21606       +9
=============================================================================
+ Hits                                           15342    15343       +1
- Misses                                          6255     6263       +8

Impacted Files
Coverage Δ

apps/node_man/serializers/policy.py
64.76% <0.00%> (-9.40%)
:arrow_down:

apps/backend/subscription/serializers.py
87.67% <0.00%> (-0.57%)
:arrow_down:

apps/node_man/handlers/plugin_v2.py
85.00% <0.00%> (+0.15%)
:arrow_up:

apps/backend/subscription/views.py
51.30% <0.00%> (+0.29%)
:arrow_up:

...nents/collections/agent_new/choose_access_point.py
95.60% <0.00%> (+0.48%)
:arrow_up:

apps/backend/subscription/steps/plugin.py
48.04% <0.00%> (+0.55%)
:arrow_up:

Continue to review full report at Codecov.

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


Option to mark a workspace as the Default workspace

This feature will get implemented in v1.0.0+4 update, proposed by Then-Benefit-1276

Completed, can be tested via v1.0.0+4 beta


[Bug]: Newest version does not work from homebrew

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
It should work
Actual behavior
After updating to newest version on homebrew, theme serve no longer works.
Command failed with exit code 1: /opt/homebrew/opt/ruby/bin/bundle install
/opt/homebrew/opt/ruby/bin/bundle:25:in `load': cannot load such file -- /opt/homebrew/lib/ruby/gems/3.2.0/gems/bundler-2.3.20/exe/bundle (LoadError)

This is where I'm at now freshly reinstalling everything.
first it complained I didn't have bundler so to install it it with gem, so I did, and then it complains it's the wrong version, so then I install the right version...
Now I'm back where I was after updating where it complains about not having this file
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- listen (LoadError)
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'

oddly going back to using the system version, not the homebrew version it was using before which is strange...
even trying to send the bug report fails:
You cannot use gems with Shopify CLI.
[LoadError] cannot load such file -- bugsnag

forcing it to use the homebrew ruby gives
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems.rb:265:in `find_spec_for_exe': can't find gem shopify-cli (>= 0.a) with executable shopify

It's like the shopify cli from homebrew installs itself to the local version of ruby but then tries to only use the homebrew version but doesn't do it completely...
and you can't install the version 3 cli directly as a gem so it's like some awful cross dependency issue.
Hopefully there is a plan to just scrap ruby from the process entirely...
Stack trace
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify:9:in `require'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/shopify_cli/file_system_listener.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify:9:in `require'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/shopify_cli/theme/dev_server/watcher.rb:2:in `<top (required)>'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/shopify_cli/theme/dev_server.rb:18:in `require_relative'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/shopify_cli/theme/dev_server.rb:18:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify:9:in `require'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/project_types/theme/commands/serve.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify:9:in `require'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/shopify_cli/command.rb:63:in `const_get'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/shopify_cli/command.rb:63:in `block in subcommand'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/command_registry.rb:87:in `resolve_class'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/command_registry.rb:70:in `resolve_global_command'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/command_registry.rb:64:in `resolve_command'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/command_registry.rb:41:in `lookup_command'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/shopify_cli/core/monorail.rb:42:in `full_command'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/shopify_cli/core/monorail.rb:20:in `log'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/lib/shopify_cli/core/entry_point.rb:16:in `call'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify:50:in `block (2 levels) in <main>'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/error_handler.rb:75:in `handle_abort'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/error_handler.rb:21:in `call'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify:49:in `block in <main>'
	from /opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify:59:in `<main>'
/opt/homebrew/Cellar/shopify-cli/3.40.1/libexec/lib/node_modules/@shopify/cli/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;

Reproduction steps

have any theme
run shopify theme serve [args]
profit?

Operating System
MacOS 13.2 (22D49)
Shopify CLI version (check your project's package.json if you're not sure)
3.40.1
Shell
zsh
Node version (run node -v if you're not sure)
v19.6.0
What language and version are you using in your application?
No response

okay...it started working after I have ruby using homebrew's version with
if [ -d "/opt/homebrew/opt/ruby/bin" ]; then
  export PATH=/opt/homebrew/opt/ruby/bin:$PATH
  export PATH=`gem environment gemdir`/bin:$PATH
fi

in my .zshrc
I installed the version 2 cli then uninstalled it
and now it works again...

Could you please upgrade to 3.42 and try again? There are a couple of additional related fixes. If it doesn't work, can you try with SHOPIFY_CLI_BUNDLED_THEME_CLI=1 shopify theme dev?

Seems similar to https://github.com/Shopify/cli/issues/1320

True, Isorese, though since that issue is closed and this one more closely matches the errors I received I opted to add here.

The latest release (3.43.0) should fix this issue. Sorry for the inconvenience!

Yes, please. In v3.43 we temporarily disabled some stuff to avoid this
issue, and we would like to ensure that it's now fixed before enabling it
again. It can be checked with that flag (note it's a new one). Thanks a lot!
El vie, 17 feb 2023, 17:27, Chris Houck @.***> escribió:

@gonzaloriestra https://github.com/gonzaloriestra I don't have to need
to use that once 3.43 came out. would you want me to try it using that even
though it isn't required?
—
Reply to this email directly, view it on GitHub
https://github.com/Shopify/cli/issues/1306#issuecomment-1434879326, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSJAJM63TN4ZW6NMKIT6WLWX6RF7ANCNFSM6AAAAAAUTZX3NU
.
You are receiving this because you were mentioned.Message ID:
@.***>


Saga fails to compensate action. Throwing NullPointerException instead of calling compensation action.

Describe the bug
When part of the Saga step fails, compensating action should be called. Instead, NullPointerException is thrown. Demo project is attached.
Steps to reproduce the behavior

Create an integration
Create a Saga with 2 actions (e.g. createOrder and reserveCredit) and appropriate compensation actions (e.g. cancelOrder and refundCredit)
Throw exception in reserveCredit action
Observe NullPointerException is thrown instead of calling a compensation action.
saga-demo.zip

Variant
Web Application
Container Management (if applicable)
None
Operating System (if applicable)
None
Version
4.4.0
Relevant log output
.camel.saga.InMemorySagaCoordinator : Cannot finalize compensation the saga
java.util.concurrent.CompletionException: java.lang.NullPointerException
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315) ~[?:?]
	at java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1194) ~[?:?]
	at java.base/java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2309) ~[?:?]
	at org.apache.camel.saga.InMemorySagaCoordinator.doFinalize(InMemorySagaCoordinator.java:172) ~[camel-support-4.4.0.jar:4.4.0]
	at org.apache.camel.saga.InMemorySagaCoordinator.doCompensate(InMemorySagaCoordinator.java:151) ~[camel-support-4.4.0.jar:4.4.0]
	at org.apache.camel.saga.InMemorySagaCoordinator.compensate(InMemorySagaCoordinator.java:119) ~[camel-support-4.4.0.jar:4.4.0]
	at org.apache.camel.processor.saga.SagaProcessor.handleSagaCompletion(SagaProcessor.java:80) ~[camel-core-processor-4.4.0.jar:4.4.0]
	at org.apache.camel.processor.saga.RequiresNewSagaProcessor.lambda$process$0(RequiresNewSagaProcessor.java:48) ~[camel-core-processor-4.4.0.jar:4.4.0]
	at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44) [camel-api-4.4.0.jar:4.4.0]
	at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.doRun(DefaultReactiveExecutor.java:199) [camel-base-engine-4.4.0.jar:4.4.0]
	at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeReactiveWork(DefaultReactiveExecutor.java:189) [camel-base-engine-4.4.0.jar:4.4.0]
	at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.tryExecuteReactiveWork(DefaultReactiveExecutor.java:166) [camel-base-engine-4.4.0.jar:4.4.0]
	at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:148) [camel-base-engine-4.4.0.jar:4.4.0]
	at org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:59) [camel-base-engine-4.4.0.jar:4.4.0]
	at org.apache.camel.processor.Pipeline.process(Pipeline.java:163) [camel-core-processor-4.4.0.jar:4.4.0]
	at org.apache.camel.impl.engine.CamelInternalProcessor.processNonTransacted(CamelInternalProcessor.java:354) [camel-base-engine-4.4.0.jar:4.4.0]
	at org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:330) [camel-base-engine-4.4.0.jar:4.4.0]
	at org.apache.camel.component.scheduler.SchedulerConsumer.sendTimerExchange(SchedulerConsumer.java:70) [camel-scheduler-4.4.0.jar:4.4.0]
	at org.apache.camel.component.scheduler.SchedulerConsumer.poll(SchedulerConsumer.java:50) [camel-scheduler-4.4.0.jar:4.4.0]
	at org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:204) [camel-support-4.4.0.jar:4.4.0]
	at org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:118) [camel-support-4.4.0.jar:4.4.0]
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
	at java.base/java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: java.lang.NullPointerException
	at java.base/java.util.concurrent.CompletableFuture.screenExecutor(CompletableFuture.java:455) ~[?:?]
	at java.base/java.util.concurrent.CompletableFuture.supplyAsync(CompletableFuture.java:2005) ~[?:?]
	at org.apache.camel.saga.InMemorySagaCoordinator.doFinalize(InMemorySagaCoordinator.java:188) ~[camel-support-4.4.0.jar:4.4.0]
	at org.apache.camel.saga.InMemorySagaCoordinator.lambda$doFinalize$5(InMemorySagaCoordinator.java:173) ~[camel-support-4.4.0.jar:4.4.0]
	at java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1187) ~[?:?]
	... 25 more

This is a general Apache Camel problem and not Karavan (Karavan is the UI designer).
You need to report these kind of "running Camel problems" to Camel itself
https://camel.apache.org/community/support/

I created a ticket at Apache Camel JIRA for you
https://issues.apache.org/jira/browse/CAMEL-20752

Okay so I have a fix in the works
2024-05-09 16:40:59.393  INFO 2150 --- [hread #7 - saga] saga-demo.camel.yaml:95                  : Order cancelled!
Try as workaround to use
initMethod: start
in the InMemorySagaService bean

Thank you @davsclaus for a quick fix


Some GPIO not accessible

Hi, some special ZERO GPIO are not accessible.
etc

| 25         |                  |  PB03  | RX
| 26         |                  |  PA27  | TX
| 27         |                  |  PA28  | USB_HOST_ENABLE
| 42         | AREF         |  PA03  |
| 30         |                  |  PB22  | EDBG_UART TX
| 31         |                  |  PB23  | EDBG_UART RX
| 32         |                  |  PA22  | EDBG_SDA
| 33         |                  |  PA23  | EDBG_SCL

What port and what version (commit)? I can look tomorrow.
On Mon, Nov 21, 2016 at 10:53 PM Peter Misenko<EMAIL_ADDRESS>wrote:

Hi, some special ZERO GPIO are not accessible.
etc

| 25 | | PB03 | RX
| 26 | | PA27 | TX
| 27 | | PA28 | USB_HOST_ENABLE
| 42 | AREF | PA03 |
| 30 | | PB22 | EDBG_UART TX
| 31 | | PB23 | EDBG_UART RX
| 32 | | PA22 | EDBG_SDA
| 33 | | PA23 | EDBG_SCL

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/adafruit/micropython/issues/54, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADNqTvp-fHw4Rxb_mgMxpdSQEgNAcpjks5rApFsgaJpZM4K5ERN
.

etc now ... micropython/atmel-samd/boards/arduino_zero/pins.c
This pins are not defined and maybe more, compared to arduino samd core variant
I understand that this pins are usually not used.

The pins should be available through their microcontroller names such as PA22 from the microcontroller.pin module. That module's pins are done automatically based on defines. https://github.com/adafruit/micropython/blob/master/atmel-samd/common-hal/microcontroller/init.c#L148

Having these accessible through microntroller.pin is enough to me.


yuzu-pineapple: Add version EA-2488

Merged manually with https://github.com/Calinou/scoop-games/commit/4e5fb6d4b091df2819858cc986fd6724e9cf6dec (added bin, fixed hash).


Implement back-end logic for setting a password

Only GameMaster can set password
Auto-generate a 6 digit password (integers only)
Save generated password to DB


Clustering error: Matrix inverse failed with error 4

cntraining chinese.stxihei.exp0.tr chinese.stxihei.exp1.tr chinese.stxihei.exp2.tr chinese.stxihei.exp3.tr
Reading chinese.stxihei.exp0.tr ...
Reading chinese.stxihei.exp1.tr ...
Reading chinese.stxihei.exp2.tr ...
Reading chinese.stxihei.exp3.tr ...
Clustering ...
Clustering error: Matrix inverse failed with error 4
what‘s wrong with it ?

@zdenop  Please close - duplicate https://github.com/tesseract-ocr/tesseract/issues/1111


Investigate Elastic search performance enhancements

It has been observed that the most time consuming part of the STP process is executing the cm-well search query to build the source graph - especially when yg / xg parameters are utilised. At present we will query elastic on a per stream element basis. Elastic will perform better if we can execute the same query for a number of stream elements. It may be worth investigating if this gives us a significant uplift in performance, and if so, designing an implementation into the flow.

unfortunately, this may not really improve anything


Is loop closure supported? If so, how to turn loop closure on?

Yes, ICE-BA supports loop closure by Solver::PushRelativeConstraint. In our experiments, we extract ORB features for each keyframe, estimate the relative pose from feature matches between keyframes at the loop, and push the relative constraint to ICE-BA. Unfortuanately it is not included in this repo. We just provide a simple optic flow based frontend. You need to impelment the loop detection and relative pose estimation to enable loop closure. Sorry for that...

Got it, thank you.

The question has been solved.


temporarily turn off correlation

Resolves #619
Turns off the correlation app so that it will not get released with b66.
Can be reverted after the release!
From PR (Correlation should show up between diff abund and Distributions, but it's not there!)

Thank you! I'll wait to merge until we're just about to do the monorepo release that will be for b66, just so that the correlation app can stay turned on as long as possible.


cannot import name 'ShapedArray' from 'jax'

After installing all of the prerequisites including installing jax and testing it, when I create the venv and attempt to run the server I get "cannot import name 'ShapedArray' from 'jax'".
ShapedArray was removed in jax in version 0.4.14.  Current latest version of jax is 0.4.23.
Do I need to install the older version of jax or is there some way around this?

Works when using the docker based version because it specifies to use 0.4.13.

Changing the requirements file found under dalle-playground to the following and reinitializing with pip fixed the issue for me:
Flask==2.1.0
Flask-Cors==3.0.9
Flask-RESTful==0.3.8
Werkzeug==2.2.2
jax==0.4.13
jaxlib==0.4.13
flax
rich
tqdm
flask_cloudflared
accelerate
transformers
diffusers


⚠ Processors has degraded performance

In cea5551, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 144 ms

Resolved: Processors performance has improved in ee2d9ab.


New CI images with rapids 23.06

Description

No code changes other than updating the CI versions

fixes #350
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

/merge


Implement high-level method for all exist alg

All alg without high-level implementation:

classifier
deep_classifier
sentiment_new

will not be implemented:

classifier


JSONpath Help

I'm trying to detect the price change on the following website and I can't get it to work.
https://www.woolworths.com.au/shop/productdetails/155536/nan-optipro-stage-1-baby-formula
At the moment I've tried using the json path 'json:$.offers.price', but that doesn't seem to work.
Is there anything that I'm missing?
Regards,
Aaron

JSONpath is used for selecting JSON content
https://en.wikipedia.org/wiki/JSON
and is not used for serving web-pages
the page you are using is served with HTML

It is served with HTML but the data that I want to check is in a script tag in json format.
Is that something that can be detected using your project?

@awirthy gday, no, but that's a super cool idea, I'll look into it! (or someone can provide a patch :) )

You mean this stuff?

Yes

@awirthy check out the PR https://github.com/dgtlmoon/changedetection.io/pull/158/files#diff-2c6ba6868c93bbd9d983d2d3e6287d89a599077020d97f6a31476adef47ccc5aL5-L6
espicially see the tests, basically i'm trying to parse any

Nice work, I thought it would have to be possible.

With the 'CSS/JSON Filter', how did you get it working for the below page?
All I'm getting is a 'Expecting value: line 1 column 1 (char 0)' error. When using 'json:$.offers.price'.
https://www.woolworths.com.au/shop/productdetails/155536/nan-optipro-stage-1-baby-formula

@awirthy oh no, so it works (and I improved the error reporting a little), but the problem is that


Could not validate Custom Website server

Describe the bug
When trying to add a custom website, upon clicking "Save service" the error message "Could not validate Custom Website server" appears right below the "Custom server" line. I'm trying to add my own Nextcloud server, which is reachable via the provided URL.
When I had a quick look at the console, it stated "ERR_TOO_MANY_REDIRECTS". The server URL (cloud.server.com) redirects to another URL (mycloudserver.duckdns.org) and the latter redirects to the IP - maybe this is related?
To Reproduce
Steps to reproduce the behavior:

Go to 'Available services'
Click on 'Custom Website'
Add the 'Name' and the 'Custom server'
Click on 'Save service'
The following error appears: "Could not validate Custom Website server"

Expected behavior
As with other URLs, the website should subsequently be loaded
Screenshots

Desktop:

OS: Windows 10
Browser: Firefox, Brave (latest versions)
Version: 5.2.0-beta.2

Same here, seems to be a problem when entering subfolders instead of (sub)domain only. https://cloud.myserver.com works, https://cloud.myserver.com/folder doesn't.

I've tried to add a server on a different port then 80 (i.e. http://somesite.local:8080), also not working.

I am experiencing the error message "Could not validate custom Custom Website server." when I try to save the custom server https://email.seznam.cz/. Adding the custom website https://www.seznam.cz/ works fine (but does not suffice as an alternative to the former website).

OS: Ubuntu 18.04
Franz client version: 5.1.0

I think the problem is in the custom website plugin itself, it does a validate on the given URL, but I don't think its following the redirect. OR NodeJS is having issues accepting the ssl certificates.

having the same issue. Any update on this ?

I have the same problem. Same requirements as all others.
But I was able to find a quick workaround to get around it: Open your Franz data folder (at Windows in your APPDATA). Navigate to the recipes folder and open up franz-custom-website, open & edit the file index.js and remove the whole validateUrl async function.
After this reload/restart Franz to apply the code changes. Now any URL can be used. Just a workaround, no fix.

Sad to say that, despite the boasted claims, custom websites are still not working correctly in the latest release (5.4.0). I especially take issue with the statement that user feedback has been implemented to improve the feature, because we still have no official comment and it's been over four months. Please fix asap, @adlk!
@promarcel: Thanks for the hint, I will try it out!


[DROOLS-729] add system properties parameter to kie-maven-plugin

changes originally done by @kedzie, thanks!

@mariofusco please take a look. I believe the system properties will be useful even for non-Android use cases.

Thanks for keeping on top of this, @psiroky!

@kedzie do we need this kind of additional configuration? After talking to @mariofusco we believe the same can be achieved using the <properties> directly in the maven pom. Or are there cases where this would not work?

The properties in the maven pom are NOT system properties..

On second thought I don't think they are published by maven as system properties.. but I don't know that for sure.  I could explore that a bit.

@kedzie my apologies, you are right. We can't just use the generic Maven properties.
Looking at the available options to define additional properties for the plugin, I would prefer this way:
<configuration>
  <properties>
    <drools.dialect.java.compiler.lnglevel>1.6</drools.dialect.java.compiler.lnglevel>
  </properties>
</configuration>

instead of
<configuration>
  <properties>
    <property>
      <name>drools.dialect.java.compiler.lnglevel</name>
      <value>1.6/value>
    </property>
  </properties>
</configuration>

I just pushed the changes mentioned in previous comment. @kedzie please let me know if this all right from you point of view. I believe we are ready to merge this.

@mariofusco from my point of view this is ready to be merged.

Merged by https://github.com/droolsjbpm/droolsjbpm-integration/commit/a3ef2b6b156c7bbeffa29c8385a44b41713ebbe3


SPIKE: Investigate terraform automation for deploying a project set work first time

Describe the bug
Currently running the terragrunt automation for a newly generated project set takes a few runs before everything is successfully deployed. The first run will always produce errors based on the order things are deployed and other factors.
Additional context

We want to make this a smooth run so that we can fully automate this later
not currently a blocker for hackathon but nice to have
plan won't work the first time because the accounts don't exist the first time
the new SEA version changes the order of operations

Definition of done

A fresh project set is created properly the first time that terragrunt run-all apply is run from within the project set folder.

Confirmed there is an error on first time run.
╷ │ Error: error adding LB Listener Certificate: UnsupportedCertificate: The certificate 'arn:aws:acm:ca-central-1:123456789:certificate/some-cert-code' must have a fully-qualified domain name, a supported signature, and a supported key size. │ 	status code: 400, request id: 1234asdf │  │   with module.account_route["abc123-dev"].aws_lb_listener_certificate.cert, │   on modules/account-routing/main.tf line 76, in resource "aws_lb_listener_certificate" "cert": │   76: resource "aws_lb_listener_certificate" "cert" { │  ╵

Fixed, added a certificate validator resource to the routing module https://github.com/BCDevOps/terraform-octk-aws-sea-routing/commit/12aa9e7f7f255985d9fff0b4cabaebb9458988f8


API required for tradeorg

Hello can anyone assist in setting up price api to come from Trade Orgs API here is the link. https://tradeogre.com/help/api
This would be good day for new coins like strayacoin

COmpleted


Fixed problems while building docker image in folder dev_sfc_controller_alpine

The same problems are solved in https://github.com/ligato/sfc-controller/pull/28


Bot does not move on when it fails to autojoin a voice channel

Assuming you are attempting to autojoin 5 differnt voice channels some of which may be in other server regions than others. Bot COULD possibly join servers 1-3 just fine but IF it fails to join server 4 due to an error similar to this (which will NOT show in terminal log during the autojoining cycle)
Traceback (most recent call last):
  File "/root/musicbot/musicbot/bot.py", line 260, in get_voice_client
    await asyncio.wait_for(voice_client.connect(), timeout=6, loop=self.loop)
  File "/usr/local/lib/python3.5/asyncio/tasks.py", line 390, in wait_for
    raise futures.TimeoutError()
concurrent.futures._base.TimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/musicbot/musicbot/bot.py", line 1710, in on_message
    response = await handler(**handler_kwargs)
  File "/root/musicbot/musicbot/bot.py", line 1250, in cmd_summon
    player = await self.get_player(author.voice_channel, create=True)
  File "/root/musicbot/musicbot/bot.py", line 343, in get_player
    voice_client = await self.get_voice_client(channel)
  File "/root/musicbot/musicbot/bot.py", line 262, in get_voice_client
    voice_client.keep_alive.cancel()
AttributeError: 'VoiceClient' object has no attribute 'keep_alive'

the bot will not move on and attempt to autojoin server 5 and so on but instead await commands.

This should be fix now in review.


Parsing environment variables bug in kedro azureml run

Hello,
I noticed that when I used the command kedro azureml run --extra-env, the cli fails to parse correct environment variable when the value has a = somewhere in the string. For example, if the key value pair is ACCOUNT_KEY=CDEF=123, then the value will become CDEF, instead of CDEF=123.
I have fixed the bug in cli_functions.py in function parse_extra_env_params and added a new test case in test_cli.py

Nice catch @datboi2001 !

Unit tests are failing, please run pre-commit and submit the changes.

Pre-commits are still not passing (black) @datboi2001

@marrrcin, I removed the unit test that I wrote. Hopefully, it will work this time

I think you should keep the test in! I think what @marrrcin meant was that the linting checks are failing. The best way to make sure all of these are passing is to run pre-commit run --all and pytest . to ensure that both all the formatting is done correctly and all tests are passing :) Please note that sometimes running pre-commit run --all will result in file changes that need to be added to the staged files via git add before doing the commit. :)

@fdroessler thanks for the help! I ran all of the commands you suggested and have pushed the reformatted file.

Merged, thanks for your contribution @datboi2001 !


Train support

Hi @ganyc717 again
When I run train mode in the begining of the train I get this error
Assertion failed: buffer.major != NULL, file src/ocl.cpp

Hi @AndrewSivrit
I have fix this issue. Thank you for your ticket.
Best Regards!


Add Maven Badge to README.md

Coverage remained the same at 97.993% when pulling 282bcf5f9bb4bbb976c61c4c6f4afa97daec43f8 on badge-updates into 6ad2481e0ab629c9de29f9a109d61827f3260028 on master.


fix: examples in tutorials

Proposed changes

refactored web3js-ext examples
refactored ethers-ext examples
changed source repository for automation of RPC API docs generation

klaytn/web3klaytn --> kaiachain/kaia-sdk

Types of changes
Please put an x in the boxes related to your change.

[ ] Minor Issues and Typos
[x] Major Content Contribution
[ ] Others

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to reach out. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING GUIDELINES
[x] I have read the CLA and signed by comment I have read the CLA Document and I hereby sign the CLA in first time contribute
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Related issues

Please leave the issue numbers or links related to this PR here.

Further comments
If this is a relatively large content contribution, kick off the discussion by explaining why you would suggest the content contribution, etc...

@Sotatek-TinnNguyen Please review the changed repository for rpc docs automation in ci/cd

@Sotatek-TanHoang Is there any more applicable updates in other sections than 'reference' given that "web3klaytn" is deprecated or obsolete? For example, Kaikas DApp Integration and LayerZero.

@scott-klaytn I see there are still part of kaia-docs other than "reference/sdk" that need to be updated. I will create a seperated PR for those updates.


Update npm command to support version 9

NPM drops support for the bin command in version 9 (ref here), while root is backwards compatible: ref.

@jakevdp I think this should be a pretty simple 1-line fix to merge in?
I just checked the issues tab, and this closes #113 .

AFAICS, the failing CI checks are not due to changes in this PR, but some issues on the CI env/config.

The anaconda distribution can be solved by using nodejs=18.13.0 as a forced dependency.
Anaconda had it auto-updated which later used npm9+ that fails...

Thanks for you PR @andyreagan. As you have noticed, there hasn't been any development in this repo for a while. Since Altair 5.2, the functionality of Altair Saver is now available in Altair via the vl-convert package. Most of the functionality has been available since 5.0, and the main addition in 5.2 was PDF export. See the docs on how to save charts for more details.
We are going to archive this repo, so I'm closing all the open issues and PRs before doing so. Try out the new options for saving charts mentioned above and if you run into issues, please open an issue directly in the altair or vl-convert repo.

Thanks for the very thoughtful follow up here! I'll be using vl-convert in the future :)


]nodemon watcher not working correctly

Hi,
src/helpers/renderHtml.js now is src/utils/renderHtml.js

@Dominionys Fixed, thanks a lot 👍


[BUG] Unexpected Flatpicker content rendering

Environment
Please provide as many details as you can:

Hosting type

[x] Form.io
[ ] Local deployment

Version:

Formio.js version: react-formio 4.3.0
Frontend framework: ReactJS 16.13.0, NextJS 9.2.2
Browser: Chrome
Browser version: 81.0.4044.138

Steps to Reproduce

Install and import react-formio as per the embed instructions
Render the form using our test form as the source.
View in the browser

Expected behavior
All the fields in the source form are displayed
Observed behavior
All the field in the source form are displayed with some additional unexpected HTML content seemingly belonging to flatpickr displayed at the bottom of the body tag.

You probably need to include either the formio.css file from react-formio or the flatpickr css. Those require some additional css from just bootstrap.

I couldn't find any information in the documentation on embedding stating that this was required? We would prefer not to have to use bootstrap styling if possible or spend time overriding it?

OK, I've included the formio.full.min.css and that seems to have resolved the issue described above via display: none. I can see though that the elements are required to render the flatpickr calendar properly.

calender in not displaying in my project could you please help me


Integrate with MTEB

Amazing work 🚀 Would be cool to integrate this work with MTEB - opened an issue here: https://github.com/embeddings-benchmark/mteb/issues/907 😇

Hi Niklas @Muennighoff I think it is a very good idea. Let me find some time to wrap up the data.


devilutionx: unstable-2020-10-20 -> 1.2.0

Motivation for this change
devilutionx was released with a lot of improvements
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Hello @aanderse, please review :)

You didn't change the hash. This PR needs to be redone.


No songs, artists, or album displayed

Hi
I just downloaded this wonderful project. Kudos to the author and contributors.
As I built and installed the project on my phone, nothing was returned I.e songs, artists, genres and albums fragments are blank. Is there something I need to do?

It sounds like Android Studio may have defaulted to the demo version of Jockey, which tries to load a fake library instead of your actual music library. You should be able to fix this by changing the build variant from demoDebug to standardDebug (This option should be in the "Build Variants" tab in the bottom left corner of Android Studio).

Oh! Really? Thanks for your quick response.