Transaction should ROLLBACK on False result

The database transaction should rollback on false result,
Imagine this is our model:
class User extends Model
{
    public static function boot()
    {
        static::saving(function () {
            return false;
        });
    }
}

And the transaction:
$saved = DB::transaction(function () {
    $saved = true;
    $saved = $saved && $anotherModel->save();
    $saved = $saved && $user->save();
    return $saved;
});

As you know the $anotherModel->save() will work but the $user->save() will fail without any exception, so the transaction won't rollback.

The database transaction should rollback on false result,

You fail to provider an argument as to why this is useful.
Also: if you really need it I believe it's pretty easy to wrap DB::transaction() with your own logic, honoring the returned value of the closure.

@mfn Why transactions are usefull? they are usefull to make sure all queries run successfully together. so this is why we need this option.
How can I wrap the function while you COMMIT when the clouser run ends? (See the code here)
But I can create new function which is not good idea.
Without this option, transactions are actually useless.

This would be a breaking change.
I also will say that if you feel that this is a pattern you have to use there's a structural problem with your code or your approach. Transactions only rollback when an error occurs. Returning false from a model observer prevents it from being saved, this is not necessarily indicative of an error. I recommend throwing an exception instead if you are really running into an error which must rollback the containing transaction.
If you must take your outlined approach then throw an exception when you detect result is false. However, I will maintain that this is likely to be indicative of a problem with the approach you're taking to solve whatever it is you're encountering.
try {
    $saved = DB::transaction(function () {
        $saved = true;
        $saved = $saved && $anotherModel->save();
        $saved = $saved && $user->save();

        if (! $saved) {
            throw new RuntimeException("Unable to save data");
        }

        return $saved;
    });
} catch (RuntimeException $e) {
    $saved = false;
}

@thecrypticace Yes it is a breaking change and I didn't say implement it right now ;)
but no it is not a design problem as i told, transactions are to make sure a bunch of queries run together, when one of them doesn't run we should ROLLBACK others.

Right, when there is an error. This is denoted in PHP by using Exceptions.

You can also use the beginTransaction and commit/rollback primitives instead of the closure method if you want more control over when things get rolled back.

@thecrypticace No, when some of queries fail :)
this fail can be cause of error, or can have logical reasons, but it is failed and the transaction should rollback.

No, when some of queries fail.

A query failure is ALWAYS denoted by an exception thrown by PDO. Period.1 And would be rolled back by virtue of an exception being thrown.
An error because of logical reasons is from a validation failure of some kind. Your validation is possibly in the wrong place.  In any case, if you're turning false to denote failure instead of using exceptions it is up to you to handle the rollback. By throwing an exception inside transaction() or dropping down to using DB::beginTransaction() and DB::commit/DB::rollBack().
Treating false as a sentinel for rollback is generally a bad idea and something that would certainly be considered an anti-pattern. Please use proper errors / exceptions. It makes developing much more future proof and easier to debug, especially in team environments.
1 Technically, you can turn them off if you really want to but that's not the point here

@thecrypticace sometimes you just return false when something is wrong. true? we don't always throw exception.

There's nuance that's kind of hard to get across without concrete code examples, but generally, no.

If it is generally no so why it exists in all before events?
In all events with "Continuing Verbs" you can return false and stop the process to continue.
saving, updating, creating, etc.
In GENERAL, it is yes.

By using return false you can prevent the save from happening. This is not the same thing as an error occurring or needing a rollback.
My final point: Rollback triggers automatically on error. return false is NOT automatically indicative of an error (whereas an Exception is 100% of the time indicative of an error). Therefore, no rollback should occur. If your code requires that the situation be different, it's up to you to handle it. Not the framework. The framework is for handling common cases. return false == error is not a common case (nor should it ever be).
I'm gonna bow out of this one for now.

return false in save method means false, means the query failed,
as long as we can prevent model by return false this option MUST exist in the transaction of the framework.
that's all, now what you think, is just your own.


GetPlaylistData doesn't return all videos in a playlist

This playlist has 155 songs, but GetPlaylistData only returns 100
let searchResult = await youtubesearchapi.GetListByKeyword('https://www.youtube.com/playlist?list=PLH4vUK9DCQdnBUbzQTXplfbeLqEpjr7dJ', true)
let playlist = await youtubesearchapi.GetPlaylistData(searchResult.items[0].id, true)
console.log(playlist.items.length) // 100

Any playlist with more than 100 songs, GetPlaylistData only returns 100

will resolve in version 1.1.1

This issue will fix it on 1.1.2. Please wait. Version 1.1.2 will release maybe next week.


Increase height to wave

Hello!
Very nice your lib...
So, how can I to increase the height of the effect?

Hi !
Thanks to use it !
Currently, you can't but I'm working on it ;)

Show!
Thank you very much!


Update menu-item-dropdown-user-menu.blade.php

Option visibility name user when show image is on.

Question
Answer

Issue or Enhancement
Issue

License
MIT

What's in this PR?

Checklist

[ ] I tested these changes.
[ ] I have linked the related issues.

@nestorPons This change do not have any sense for me. The next original code:
<span @if(config('adminlte.usermenu_image')) class="d-none d-md-inline" @endif>
    {{ Auth::user()->name }}
</span>

will hide the user name on small screen sizes when there is an image available for it (this is used to save visual space)...
Your change, that is equivalent to remove the entire if condition:
<span @if(config('adminlte.usermenu_image') or !config('adminlte.usermenu_image')) class="d-none d-md-inline" @endif>
    {{ Auth::user()->name }}
</span>

will hide the user name on small screen sizes whenever an image is available or not. So, in small screen sizes, if the name isn't visible, neither the image, how will a user interact with the user dropdown menu?

The idea is to be able to see only the user icon on large screens, when I copied it to this code I had a bad time. The condition is that if the icon is not seen, the name cannot be deactivated and one of the two is always visible. The correct code is this:
<span @if(config('adminlte.usermenu_name') or !config('adminlte.usermenu_image')) class="d-none d-md-inline" @endif>
{{ Auth::user()->name }}

Incomplete PR!


Invalidate calls in CXCallProvider.

This will make sure that CallKit isn't being confused when the app is reloaded when developing. Otherwise it would get confused and reject any transaction after the reload.

@ianlin Want to merge? Otherwise I will close the PR since we have already forked the library.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1835

Questions ?
Please refer to the Backport tool documentation


The save button is disabled when the retirement date is set to current or next day

The save button is disabled when the retirement date is set to current or next day.
The here was caused by the fact that moment(undefined) is the same as moment() and returns the current date.
Links
https://bugzilla.redhat.com/show_bug.cgi?id=1384030
Steps for Testing/QA
Select the retirement date for any VM that has none set yet to the current date or the next day. The Save button is disabled before this fix.

@miq-bot add_label ui, wip, bug

@miq-bot remove_label wip
@miq-bot add_label euwe/yes

@AparnaKarve, @h-kataria - please review

Euwe backport details:
$ git log -1
commit<PHONE_NUMBER>e6363a14c2ceb52d3c09419ebc9bf0
Author: Milan Zázrivec<EMAIL_ADDRESS>Date:   Wed Dec 7 15:45:06 2016 +0100

    Merge pull request #12343 from lgalis/save_retirement_date_fails

    The save button is disabled when the retirement date is set to current or next day
    (cherry picked from commit 8ce9c08dc652b83031fd877d075ac7c848eada84)

    https://bugzilla.redhat.com/show_bug.cgi?id=1411509


Use in-process?

I am wondering if it's possible to use MeiliSearch as a statically linked library that runs in-process? I would like to release a single binary, built in Rust, that basically exposes an alternative (more specialized) version of the web server that comes with the current binary, plus a few other things.
The Rust SDK accesses an external process, and I can't find any hints that this is possible.

Hello @kristiandupont, we are currently working on an independent rust library but for now you can't use meilisearch as a rust library.

Hey @kristiandupont,
Could you provide more information on waht you would like to expose with your HTTP front-end?
It will help us know what we will need to expose with the next Rust library we are working on.
Thank you very much :)

Sounds good!
I am making a tiny app that uses Meilisearch for indexing source code on my hard drive. I have a little web frontend for it and will make a vscode extension as well. So in terms of indexing, it currently scans raw text but I imagine I will introduce a parsing stage to get better results. As for the frontend, it's similar to the one built into Meilisearch except it doesn't show a dropdown for which index to search, and the results feature syntax highlighting etc.
It works for me at the moment, but I would like to be able to distribute it easily and having a single process, single executable would help quite a lot in that regard.

Closing because it will be done in the future.


Motionmagic

Fixes turret motion:

indexing
slewing
scanning

Updated with two commits reflecting review comments, and merging so we can proceed to test.


chore: run tests on 3.8

Looks like 3.8 is breaking somewhere in isoalte-cloud, looking around...

After wasting some time on this, turns out there are issues with 3.8 specifically and some mix of fastapi/pydantic and pickling. Was not able to get to the bottom of it in the meaningful amount of time and considering that 3.8 is near EOL we should just close this PR and fix 3.8 issues as they come up in real world.


Telegram returned an invalid response

?
!

Operating system
win7

PHP Telegram Bot version
?

PHP version
5.5.12

MySQL version
5.6.17

Update Method
Webhook

Self-signed certificate
no

Summary
i create anr run set.php
but :Telegram returned an invalid response!

What version of the bot was installed?
You can check in vendor/longman/telegram-bot/src/Telegram.php file, in the $version variable.
Be sure to check your bot username and API token.

Hi. I have same respons:  Telegram returned an invalid response!
"longman/telegram-bot": "^0.62.0" in my composer.json
protected $version = '0.62.0'; in vendor/longman/telegram-bot/src/Telegram.php
my bot username: zetSoftTestBot (i also tried @zetSoftTestBot );
my token is corrent.
i tried to manumally send get request to https://api.telegram.org/bot/setWebhook?url= and it returned :
{
ok: true,
result: true,
description: "Webhook was set"
}
"Telegram returned an invalid response!" how can i fix this. pls help me

i fixed it.

Glad it's working now 👍


dropdown-toggle is not working with angular bootstrap ui.

By default in angular bootstrap dropdowns no class, but when I added a class to dropdown-toggle it does not help.
So it does close datetimepicker on selecting date.
Controller
$scope.dateConfig = {
	startView: "day",
	minView: "day",
	dropdownSelector: ".date-toggle"
};

HTML

			{{filter.start_at | date:"dd-MM-yyyy"}}
			{{t.SELECT_START_AT}}

		<datetimepicker ng-model="filter.start_at" datetimepicker-config="dateConfig" />

Please create a plunker or fiddle the demonstrates the problem.

Closing due to lack of response from @glodov


docs: add installation instructions for Arch Linux

serpl is now in Arch repos: https://archlinux.org/packages/extra/x86_64/serpl/ 🥳

Amazing addition! appreciate this @orhun 🙏


I need to change or set the color of saturday and sunday to red in prolificinteractive material-calendarview

/**

Highlight Saturdays and Sundays with a background
*/
public class HighlightWeekendsDecorator implements DayViewDecorator {
private final Calendar calendar = Calendar.getInstance();
private final Drawable highlightDrawable;
private static final int color = Color.parseColor("#228BC34A");
public HighlightWeekendsDecorator() {
highlightDrawable = new ColorDrawable(color);
}
@Override
public boolean shouldDecorate(CalendarDay day) {
day.copyTo(calendar);
int weekDay = calendar.get(Calendar.DAY_OF_WEEK);
return weekDay == Calendar.SATURDAY || weekDay == Calendar.SUNDAY;
}
@Override
public void decorate(DayViewFacade view) {
view.setBackgroundDrawable(highlightDrawable);
}
}

Hi,
I was trying the some of the example code. But CalendarDay is cannot be resolved. can you help me resolve this
`        calendarView.addDecorator(new DayViewDecorator() {
@Override
public boolean shouldDecorate(CalendarDay day) {
// check if weekday is sunday
return day.getCalendar().get(Calendar.DAY_OF_WEEK) == Calendar.SUNDAY;
}
        @Override
        public void decorate(DayViewFacade view) {
            // add red foreground span
            view.addSpan(new ForegroundColorSpan(
                    ContextCompat.getColor(getContext(), Color.RED)));
        }
    });`

Hello all, the above code works only for first row of date. am i missing anything

Hello all, how can i change the week day lable color only for sunday


Custom query params in exchangeCodeForTokenServerURL

So, basically after user authorization, the frontend makes call to the backend with just 5 query params { code, client_id, grant_type, redirect_uri, state } but in some cases, oauth providers attach extra params to the url which are getting lost while a call is being made to exchangeCodeForTokenServerURL.
We should have the functionality to pass all the params along with the above ones to the backend server.

Hey @AniketHQ, can you post please an example demonstrating what you want to achieve and with which provider?


Support for PPC64le

Hello!
I'd like to get this working on PPC64. I tried getting something going, but all I get is this:
error[E0658]: inline assembly is not stable yet on this architecture
error: `clobber_abi` is not supported on this target

Looking at the loong PR, there's a way to to use the unstable inline assembly, but what about this clobber_abi thing? This has "only clobbers" under ppc, which makes me think it should work?
Also, would endianness matter here? I mostly want support for PPC64le, but would the same code work for PPC64(be)?
Thanks for any help!!

clobber_abi is optional, it's just a way to avoid listing all possible registers as clobbers. However it would be nice to have support for it added in the Rust compiler. As you can see in https://github.com/rust-lang/rust/pull/111237, it's not too difficult.
Endianness does not matter here. For example, the ARM/AArch64 code works fine in either endianess.

@Richard-Rogalski heya did you get any further with this? 😺

@Amanieu I also ran into the issues while attempting build of coronsense 0.1.4 on ppc64le arch. (Rhel 9.3). Are there any updates on adding support for ppc64le?

hello, i have a half complete PR for adding the necessary features into rustc. As far as i know, the only thing missing is tests, which I got too burnt out to finish. I’m not sure if I pushed my latest changes, I don’t think so. I’ll try to do that tonight, and if anyone wants to add the tests they’re more than welcome to
Oct 8, 2024 at 05:52 by @.***:

@Amanieu https://github.com/Amanieu>  I also ran into the issues while attempting build of coronsense 0.1.4 on ppc64le arch. (Rhel 9.3). Are there any updates on adding support for ppc64le?
—
Reply to this email directly, > view it on GitHub https://github.com/Amanieu/corosensei/issues/18#issuecomment-2399514749> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/ASR6C3KL45QKCLX7DQV5G4TZ2O2NZAVCNFSM6AAAAAAXZCMX6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJZGUYTINZUHE> .
You are receiving this because you were mentioned.> Message ID: > <Amanieu/corosensei/issues/18/2399514749> @> github> .> com>

Thanks @Richard-Rogalski! I'd be happy to start reviewing your PR even if it's incomplete.

Actually there seems to be another PR for that: https://github.com/rust-lang/rust/pull/131341


Update Jenkins build script to support multiple versions of MkDocs and other dependencies/plugins

Description:
Currently, the Jenkins build script is configured to support only a specific set of MkDocs versions and other dependencies/plugins. These versions are hardcoded within the script.
pip install mkdocs==1.4.2
pip install mkdocs-material==9.1.2
pip install pymdown-extensions==9.10
pip install mkdocs-minify-plugin==0.6.2
pip install mkdocs-markdownextradata-plugin==0.2.5
pip install mkdocs-redirects==1.2.0
pip install pathlib==1.0.1
pip install markdown-include==0.8.1
pip install markdown==3.2.1
pip install mkdocs-exclude==1.0.2
pip install jinja2==3.1.2

The Jenkins build script needs to be updated to support multiple versions of MkDocs and other dependencies/plugins. This update will be beneficial for future scenarios if different documentation versions require different versions of MkDocs and other dependencies/plugins.

As a solution, the requirements.txt file can be executed for each documentation version. The requirements.txt file contains the versions of MkDocs and other plugins for each documentation version.
Example:

For MI 4.3.0: https://github.com/wso2/docs-mi/blob/4.3.0/en/requirements.txt
For MI 4.2.0: https://github.com/wso2/docs-mi/blob/4.2.0/en/requirements.txt

The hardcoded versions were removed from the build script and replaced with the following.
pip install -r https://raw.githubusercontent.com/wso2/docs-mi/${GIT_BRANCH#*/}/en/requirements.txt


state history: deferred and executed in same block

Handle transactions which are deferred and executed in the same block.
@arhag: create a way to test this situation

Good news, further analysis revealed that this isn't a problem.
A contract-generated transaction scheduled and retired in the same block isn't a problem in the state history plugin since it only has one transaction trace in this case (that of the retired deferred transaction).
A delayed input transaction would be a problem for the state history plugin if it was to be scheduled and retired in the same block since the retired trace with overwrite the scheduled trace. But it shouldn't be possible for a delayed input transaction to be scheduled and retired in the same block.
The only way to indicate that an input transaction is delayed is by setting a non-zero value for the delay_sec field. The smallest possible value is 1, which would enforce that the delayed input transaction could not retire until at least the next block.

when will happen a  contract-generated transaction scheduled and retired in the same block ?

when will happen a contract-generated transaction scheduled and retired in the same block ?
@tbfleming


Adjusted Warning and Capitalize Support

Adjusted warning and capitalized Support

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @hmbrown64,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Test Vue 2 Composition API with vue-demi

I'm not sure this package works for Vue 2 composition API and how vue-demi works.

https://github.com/vueuse/vue-demi

Or giving up Vue 2 support and replace vue-demi with vue

In v0.4.4, have removed vue-demi, so this package only supports Vue 3.


Simplify and fix example for the StackPanel vs DockPanel article

Summary

Replaced the image resource required by anyone using this code with an emoji
Simplified the code-first approach
Split example into sections to clarify the difference between the XAML version and code-first version
Added an image to the doc

@StingyJack if you're watching, here is the updated csharp code, vb.net code, and xaml example.
Fixes #1586

Internal previews

📄 File
🔗 Preview link

dotnet-desktop-guide/framework/wpf/controls/how-to-choose-between-stackpanel-and-dockpanel.md
dotnet-desktop-guide/framework/wpf/controls/how-to-choose-between-stackpanel-and-dockpanel

@luisquintanilla Ready for review


Migrate /enterprise/guest_accounts e2e tests to TypeScript

Summary
Summary
Migrates the following integration e2e tests to TS:
guest_add_spec
guest_experience_ui_spec
guest_feature_spec
guest_identification_spec
guest_identification_ui_not_cloud_spec
guest_identification_ui_spec
guest_invitatioin_ui_more_spec
guest_invitatioin_ui_spec
guest_popover_ui_spec
guest_removal_ui_spec
member_invitation_ui_spec
system_console_guest_access_ui_spec
system_console_guest_not_cloud_spec
system_console_manage_guest_spec

Ticket Link
https://github.com/mattermost/mattermost-server/issues/21322
Screenshots

Release Note
NONE

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/252226

/release-note-none

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/252588

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.


Temp Groups/Permissions turning into Perm

Description

When i set a temp group or permission it changes to a perm group or permission sometimes when switching servers on bungee
Reproduction steps

It just happened randomly
Expected behaviour

The permission not to turn perm
Environment details

Server type/version: Paper running version 1.16.4 build 416
LuckPerms version: v5.3.17

Ill post if needed, im in a rush
Any other relevant details

None

I'm gonna need some more details in order to look into this for you.
Could you perhaps provide some screenshots of what you mean? I can't really follow your explaination.

Hello, this is what im meaning:
The group with the expiry added onto it didnt actually work as afew minutes later when switching servers it added one that has no expiry https://gyazo.com/04479c9ae58ef01ff912e15c1bdfe960

There's nothing in LP that would do this on it's own, so I imagine it is being caused by another plugin.
You could try turning Vault debug on in the config to see if that gives any hints as to what it is.


Getting a "failed to execute script" when I try to import Private Key to default wallet

Here are the steps I do to import private key from ZCL wallet to BTCP wallet.  I do want to preface by saying that I had my ZCL in Electrum wallet since February 1st and have not move it till today.

I transferred my ZCL from Electrum Wallet to Bittrex Wallet
Downloaded BTCP electrum wallet from Reddit github link
Opened (unzipped) BTCP electrum wallet and chose to import private key
Went to addresses on ZCL electrum wallet, right clicked on the first address and chose private key.
Copied private key and inserted into BTCP wallet when prompted to input private key
Immediately received "failed to execute script"

What am I doing wrong?  Please help.  Thank You.

Of course I was doing it wrong.  Here's how I got my BTCP:

Created new standard wallet.
Select I already have seed.
Used ZCL seed from ZCL wallet.
It was that easy.

Great work Dev team!

The private key should work though - this is a high priority fix / user clarity update


Commit to run a genesis validator - (A) Client Teams

The Ethereum EL/CL client teams are asked to commit to a number of validators they are willing to run at genesis for Holesky.
The recommended size of the validator-set per team is 80-100k. The estimated lifetime should be 3-5 years.
Please also indicate if you believe that a genesis with 1.5 million keys could cause issues.

EF DevOps commits to running 100k validators, We're also comfortable to run more or less depending on the network's needs.

Sigma Prime will happily commit to 100k validators (or any other size that is deemed ideal for client teams)

Status/Nimbus commits to running 100k validators, or however many is useful for the network.

ConsenSys commits to run 100k validators or more if needed.

ChainSafe/Lodestar committing to 100k validators.

Nethermind commits to running 100k validators

Grandine would take 50K-100K validators.

Nethermind commits to run 100k validators ;)

The Prysm team would be fine with running a 100k validators or a higher number if required.

Thank you for your participation. The comments have been noted and will make it into the genesis state. We'll be in touch for information about genesis state, etc. For more info please refer to the community call #1 notes: https://github.com/ethereum/pm/issues/814#issuecomment-1613224057


DOC: Fix example for subset_by_index in eigh doc

The main docstring correctly says:
To return only the second smallest to fifth smallest eigenvalues, [1, 4] is used.
But the example text is off from that.

Reference issue

None
What does this implement/fix?

Small miswording in the example docstring.
Additional information

Wow, surprised to see that it survived this long. Thanks @scottstanie


Update menu_ru.lang

Contains
Brief description of what the PR does like "Fixes #12345"
How to test
Brief description of how to test / confirm this PR before merging
Outstanding before merging
If anything. You can use neat checkboxes! Feel free to delete if not needed

[ ] Need to consider use case x
[ ] Still have to adjust the wiki doc
[ ] Will need translation work

Edit

Can one of the admins please verify this patch?

Great! Thank you!

Added you to the credits @naiffuR - should be visible shortly! :-)
Feel free to introduce yourself in the forum sometime if you like, you can get a contributor badge there if so. Happy to have any more improvements, be they more translations or anything else.
http://forum.terasology.org/forum/contributor-introductions.7/

Hi! This winter I signed up for the forum under the name Ruffian and previously made translation of game text into Russian language. I will be glad to help with translation into Russian language.

Excellent! I added the contributor badge to your forum account :-)
More help with Russian would be appreciated. Usually they would be doable via translate.terasology.org but its Git setup needs some maintenance as it fell behind what we have here on GitHub. Should be sorted out over the next few days.


Cross compile for Scala 2.13.0

add scala-collection-compat to cover JavaConverters deprecation
update various dependencies to the new one that supports 2.13
conditionally include some of the removed compiler flags
add 2.13 to travis.yml

Coverage increased (+0.2%) to 90.154% when pulling e2308f3b93dd6b02959f642212ce961dfabd4937 on markus1189:scala-213 into 6df65b068ff9388e6f9ed9c497c3533c6fef4d12 on WW-Digital:master.

Coverage increased (+0.2%) to 90.154% when pulling e2308f3b93dd6b02959f642212ce961dfabd4937 on markus1189:scala-213 into 6df65b068ff9388e6f9ed9c497c3533c6fef4d12 on WW-Digital:master.

@markglh @etspaceman any plans to move forward here?

Closing this, as it seems like nothing is going to happen here anyway :disappointed:

@markglh any interest to reopen this?


[Example] ggml: add grammar example

Add grammar example for https://github.com/WasmEdge/WasmEdge/pull/3318

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

Perhaps we can try this model. It seems to be one of the more reliable open source models for JSON generation.
https://github.com/NousResearch/Hermes-Function-Calling


net: sockets: socketpair: do not allow blocking IO in ISR context

Using a socketpair for communication in an ISR is not a great solution, but the implementation should be robust in that case as well.
It is not acceptible to block in ISR context, so robustness here means to return -1 to indicate an error, setting errno to EAGAIN (which is synonymous with EWOULDBLOCK).
Fixes #25417

I feel like I should get an award for longest procrastinated trivial bugfix 😅


Fix - App crashes when scrubbing through an mp4 file on attachment upload preview

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/36905
Tests

Open a chat on ND
Click on plus icon inside the compose box
Click on add attachment
Click on choose from gallery
Select an mp4 video
When the preview opens up play the video and manually scrub through the video using the progress bar

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/91068263/f132c108-f3d8-4aa7-8394-f9e09764a269

Android: mWeb Chrome
https://github.com/Expensify/App/assets/91068263/81236f05-e3fb-4b36-b195-b59e504a2887

iOS: Native
https://github.com/Expensify/App/assets/91068263/ac627af0-501e-40ed-ac4b-c30e505c5641

iOS: mWeb Safari
https://github.com/Expensify/App/assets/91068263/382f8a9f-88db-4ea0-979a-c27886dac742

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/91068263/200fd1db-126f-4934-b29f-3ffa7013af19

MacOS: Desktop
https://github.com/Expensify/App/assets/91068263/0580d0db-58d4-404d-9d8b-0cf8cd111626

@shubham1206agra it's caused by progressBarInteraction, I will sync tomorrow with Reanimated team, so they will help me investigate it, but since the crash is a deploy blocker, I would fix the warning in a separate followup PR. WDYT?
Cc. @rlinoz, since you're the internal engineer who is assigned to the issue.

We are not deploying this week anymore, so if we can get the warning fixed tomorrow that is fine, otherwise I agree we can fix it in a separate PR.

@rlinoz lets get the crash fixed in staging asap, the warning can follow up whenever fixed

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/chiragsalian in version: 1.4.43-14 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.43-20 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Issue 1117: Remove unused Maven dependencies from project

Pull Request Description
This pull request closes #1117

[ ] Removed unused dependencies from strongbox-data-service/pom.xml

Acceptance Test

[ ] Building the code with mvn clean install -Dintegration.tests still works.
[ ] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[ ] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[ ] The tests in the strongbox-web-integration-tests still run properly.

Questions

Does this pull request break backward compatibility?

[ ] Yes
[ ] No

Does this pull request require other pull requests to be merged first?

[ ] Yes, please see #...
[ ] No

Does this require an update of the documentation?

[ ] Yes, please see strongbox/strongbox-docs#{PR_NUMBER}
[ ] No

Thanks for your pull request! :)

Let me know, when you think you're ready with this pull request!
I would also like to invite you to join our chat channel.

What isn't clear to me is why the above 2 CI checks were skipped? When I look at the details of the web-integration-tests check it shows "Success".

Hi, @erikweibust,
Thank you for your contribution!
It looks like your PR needs to be rebased against the latest master which is why it's currently failing. :)
Also, would you mind signing the ICLA, as described in the Contributing page?
We would not be able to merge your pull request otherwise.
Regards,
Steve

Steve, I'm not a strong GitHub guy. I can google the rebase operation but would you care to share some guidance?

Steve, I'm not a strong GitHub guy. I can google the rebase operation but would you care to share some guidance?

Don't worry, @erikweibust! This is an excellent chance to learn exactly how to use git for this! :)
Have a look at our wiki page on using git rebase vs. git merge.


Updated Mockups and Create Problem layout added

-1.01: Create a Problem - Layout made
-I updated the individual mockups, and separated the caregiver and patient mockups and created separate PNGs for them (Hopefully they'll be easier to see). I tried making the fonts bigger and decreasing the text box size, making sure they're proportionate to the screens but still no change. Couldn't really make offline behaviour screens.

The changes sound good; could you really quickly take a few screenshots of the Problem layout (preview on Android Studio would be fine) so we can see what it looks like?

      The changes sound good; could you really quickly take a few screenshots of the Problem layout (preview on Android Studio would be fine) so we can see what it looks like?

Yeah no prob,


Menu wont open/show

Game version 3351 / 1.69
RageCoop and all requirements (scripthook and scriphookdotnet) are installed.
Mod won't show notification when join neither menu will open.
Tested both nightly and <IP_ADDRESS> versions.
(sorry for any spelling mistake or incoherence, english not my first language)

me too

i solved this problem, but i dont remember how, it was few months ago. sorry


Change Generation Rate to something lower than 1/T, game just crashes

is it possible to have the thing not produce during a tick and  during a time period? like 1/S, for more balanced configuration.
since otherwise it's always a minimum of one a tick, which is just not possible to config balance really.
-Astro

will look into it. It could e hard because minecraft runs on ticks.

I got the problem. The datatype used for that config value is float, so 0.x is converted into 0. And then zero division crashesz the game.

i think i "fixed" it by making it not possible to occur.

I did some backend changes and now it even works with really slow generators. I hope this is what you meant.
https://github.com/StickyPiston-development/CreateCobblestone/assets/97804691/59ca76f4-8cb6-447a-822a-01da90267eb0

ooh that looks great, very much thanking you, tysm. :D

No problem, i will release this in a few days on modrinth.

Here you go! (for forge, neoforge, fabric and quilt.
https://modrinth.com/mod/create-cobblestone/version/1.3.1+forge-1.20.1-36
https://modrinth.com/mod/create-cobblestone/version/1.3.1+fabric-1.20.1-36


ADD mpegts support

Have you read the FAQ and checked for duplicate open issues?
YES
Is your feature request related to a problem? Please describe.
Yes, it is related to a problem. I am currently trying to play an MPEG-TS live stream, but it seems that Shaka Player supports only HLS and DASH formats. This limitation restricts the usage of Shaka Player in environments where MPEG-TS streams are prevalent.
Describe the solution you'd like
I would like Shaka Player to include support for MPEG-TS streams. This would involve enabling the player to handle MPEG-TS container formats and potentially adapt to the different streaming protocols and codecs used in MPEG-TS compared to HLS and DASH. The ideal solution would allow seamless playback of MPEG-TS live streams, just as it currently does with HLS and DASH streams.
Describe alternatives you've considered
One alternative solution I have considered is using a different media player that supports MPEG-TS. However, this is not ideal as it requires integrating and maintaining multiple media players for different formats. Another alternative is transcoding MPEG-TS streams to HLS or DASH on the server side, but this adds additional complexity and resource requirements to the streaming process.
Additional context
The addition of MPEG-TS support in Shaka Player would significantly enhance its utility in various streaming scenarios, particularly for live broadcasting. Many broadcast systems and cameras natively output MPEG-TS streams, and having direct support in Shaka Player would simplify the workflow and reduce the need for format conversion. This feature would be highly beneficial for developers and content providers who work with a mix of HLS, DASH, and MPEG-TS streams.

Currently I don't think we can support this functionality. There is not enough community demand to support this.
If you want a player that fully supports this I recommend: https://github.com/xqq/mpegts.js
Sorry!

Currently I don't think we can support this functionality. There is not enough community demand to support this.
If you want a player that fully supports this I recommend: https://github.com/xqq/mpegts.js
Sorry!

Already using this, no support for ac3 Audio

Looking at the project code, it seems that they do support AC-3 (https://github.com/xqq/mpegts.js/blob/master/src/demux/ac3.ts)


Add “Licenses & certifications” as a target

It would be great to have the ability to search in the “Licenses & certifications” for a specific word.

@TSalvin suggest a part of the code in the issue #145


entity.save gives me an error

Hi,
First of all, thanks for sharing this implementation of Jest and D365.
I'm starting to implement some tests and i'm stucked trying to save one registry.
After setting some values i¡m using the xrmTest.Entity.save(); (also tried xrmTest.Entity.save(true)) instruction to save the record and it returns me this error:

Don't know what to do to save the record, is there any other way?
Many thanks agains for sharing this solution, in my opinion it's the best to create UI test over DataVerse, CDS or Dynamics.
Best regards.

Hi @Fernandobo21,
thanks for the kind words and for giving it a try.
For simple tests, you might also want to check out the chrome extension, which can help you in designing the tests: https://github.com/XRM-OSS/D365-UI-Test-Designer
As for your error: You most certainly have some required fields which are not filled out at the time where you want to save, can you check that?
Kind Regards,
Florian

Hi @Fernandobo21,
thanks for the kind words and for giving it a try.
For simple tests, you might also want to check out the chrome extension, which can help you in designing the tests: https://github.com/XRM-OSS/D365-UI-Test-Designer
As for your error: You most certainly have some required fields which are not filled out at the time where you want to save, can you check that?
Kind Regards,
Florian

wow! thanks for the really quick answer.
I'm totally using it for UI test in my pipelines and for the customers, with the chrome extension the QA tester can cooperate with the developers, in my case this implementation gives a plus for both , QA and DEV team. Big round of applause for sharing.
Your guess was correct. I'm trying to validate my javascript that makes some fields mandatory.
there are two ways to check that:
1- Entity.save() and take a look at the notification errors.
2-  Check the fields if they are mandatory or not (with expect or something like that)
As always, i chose the problematic option, i have QA soul, jajaja.
If is not an issue, then i will close it and get the second option.
I've created the test with the extension, thats why i click the save button and then check the mandatory fields. I export the test from the extension.
Thanks again.
Fernando

wow! thanks for the really quick answer.
I'm totally using it for UI test in my pipelines and for the customers, with the chrome extension the QA tester can cooperate with the developers, in my case this implementation gives a plus for both , QA and DEV team. Big round of applause for sharing.
Your guess was correct. I'm trying to validate my javascript that makes some fields mandatory.
there are two ways to check that:
1- Entity.save() and take a look at the notification errors.
2-  Check the fields if they are mandatory or not (with expect or something like that)
As always, i chose the problematic option, i have QA soul, jajaja.
If is not an issue, then i will close it and get the second option.
I've created the test with the extension, thats why i click the save button and then check the mandatory fields. I export the test from the extension.
Thanks again.
Fernando

Hi @Fernandobo21,
thanks for your feedback :)
In the upcoming releases I want to add a new assertion to the UI designer, which is "Assert Save fails".
This assertion would trigger the save function and expect it to fail. That would be ideal for your use case.
For the time being you have to chose the second approach that you described, in the UI Test designer you can just click the assertions button near the Actions label and then you can choose all fields that should be mandatory inside the dropdown that is added to the bottom of your test.
There you can check the checkbox before the "Required Level" label and select "Required", then the extension will generate code for all selected controls to be mandatory.
Please give it a try and come back to me if you're having problems. If it works as expected, please close the issue :)
Kind Regards,
Florian

Hi @Fernandobo21,
thanks for your feedback :)
In the upcoming releases I want to add a new assertion to the UI designer, which is "Assert Save fails".
This assertion would trigger the save function and expect it to fail. That would be ideal for your use case.
For the time being you have to chose the second approach that you described, in the UI Test designer you can just click the assertions button near the Actions label and then you can choose all fields that should be mandatory inside the dropdown that is added to the bottom of your test.
There you can check the checkbox before the "Required Level" label and select "Required", then the extension will generate code for all selected controls to be mandatory.
Please give it a try and come back to me if you're having problems. If it works as expected, please close the issue :)
Kind Regards,
Florian

Hi florian.
I'm really sorry.
I was my mistake the error of the save.
I've got in the afterall a Close so i didn't see the error.
The error was that the user doesn't have provileges to save the registry with the value i put.
Sorry to make you lose your time.
Closing the ticket.
State: closed.

Thanks again.

Hi florian.
I'm really sorry.
I was my mistake the error of the save.
I've got in the afterall a Close so i didn't see the error.
The error was that the user doesn't have provileges to save the registry with the value i put.
Sorry to make you lose your time.
Closing the ticket.
State: closed.

Thanks again.

Hi @Fernandobo21,
no worries, thanks for the laugh :D
Kind Regards,
Florian

Hi @Fernandobo21,
no worries, thanks for the laugh :D
Kind Regards,
Florian


Update Chrome support

I just found that CSS variables works on Chrome v48.
This is the complete information from my Chrome://version:
48.0.2564.22 (Official Build) dev-m (64-bit).
It is working there fine

Thanks, confirmed. Updated manually to avoid dealing with merge conflict


Feature EIP-7702 docs

Fixes https://github.com/safe-global/developer-experience/issues/313
Changes in PR:

Add introductory section for EIP-7702
Add problem with using existing Safe contracts with EIP-7702
Add possible approaches for using Safe with EIP-7702
Added diagrams

I updated the style of the diagrams. Can we use this version instead?


Create Pages “vender”

Automatically generated by Netlify CMS

👷 Deploy Preview for koyomiy processing.

Name
Link

🔨 Latest commit
369e004619d69144052596e74e3aba2266524dc7

🔍 Latest deploy log
https://app.netlify.com/sites/koyomiy/deploys/62d29d0a1cb3d20008a47fb0


Connection isn't completing properly

Both Xchat and ZNC don't believe the connection is complete after connecting.  Neither of their after connect hooks (like auto join) fire properly.
Here is what it looks like when I connect to a hector server:
* 001 TecnoBrat :Welcome to IRC
Comparably, when I connect to freenode:
* Welcome to the freenode Internet Relay Chat Network TecnoBrat
Here is the difference in the raw packets:
>> 001 TecnoBrat :Welcome to IRC
And freenode:
>> :kornbluth.freenode.net 001 TecnoBrat :Welcome to the freenode Internet Relay Chat Network TecnoBrat
Raws mentioned that the prefix is optional .. however it doesn't look like clients actually respect that.

I've noticed this as well with a few other IRC commands. (see https://github.com/leedo/alice/blob/master/lib/Alice/Role/IRCEvents.pm#L257-258 for an example

Okay, I talked to a ZNC developer, who acknowledged that ZNC does assume the first parameter of each message is a prefix (:kornbluth.freenode.net), and in fact doesn't even look at it—simply eats up the first parameter, no matter what it is. In this case, it's gobbling up 001 and then trying to figure out what the TecnoBrat command is.
We looked at the RFCs, and there's some ambiguity between the "optional" prefix in section 2.3 and the "must" in section 2.4, which covers numeric replies such as 001.
If it was just ZNC with this behavior, I'd prefer submitting a patch to them and leaving Hector be, but it looks like XChat might make the same assumption, and who knows what other edge case clients are out there. I think Hector should start sending the server name as a message prefix.

I'm working on this on my message-origin topic branch.

All tests pass and ZNC 0.202 connects successfully as of b4fd7ee. I'll test with XChat and Snak (another client found to exhibit this issue) tomorrow, and maybe we can get a release out.

I reproduced this bug in Hector 1.0.5 using XChat and Snak. It's fixed on my topic branch.
Thanks for reporting this, @tecnobrat! Time for Hector 1.0.6!


AdonisAuth - Return User data and JWT

How can I do to return a user's data after authentication in JWT using the Auth adonis library?
This is my current code:
async auth({request, response, auth}) {
    const { email, password } = request.all()
    return await auth.attempt(email, password)
  }

It returns with the following answer:
{
    "type": "bearer",
    "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1aWQiOiI1YTc5ZjI1Nzc3OThkNDJmYjhlMDU4OTIiLCJpYXQiOjE1MTgzMDgzNTN9.9FAmBBkSLwS_zIBDE_zPz6DFYfohh3grcdrA70JPWgs",
    "refreshToken": null
}

I would like it to return the following way, how to do it?
{
    "type": "bearer",
    "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1aWQiOiI1YTc5ZjI1Nzc3OThkNDJmYjhlMDU4OTIiLCJpYXQiOjE1MTgzMDgzNTN9.9FAmBBkSLwS_zIBDE_zPz6DFYfohh3grcdrA70JPWgs",
    "user": {
      "_id": id of user,
      "name": "Name of user",
      "email": "email of user"
      "user_type": "type of user"
     },
    "refreshToken": null
}

Hi @bryannbarbosa,
You might try something like this
async auth({request, response, auth}) {
    const { email, password } = request.all()
    let token = await auth.attempt(email, password)
    let user = auth.user
    return {} // your structured object
}

My request response was as follows, it returns null:
I'm using Lucid-Mongo as database for Auth.
{
    "response": {
        "type": "bearer",
        "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1aWQiOiI1YTc5ZjI1Nzc3OThkNDJmYjhlMDU4OTIiLCJpYXQiOjE1MTgzMTgwNzl9.lyG3sId7hI4R8UiS2qfshN7oPzOryB5gEMR754ULOJw",
        "refreshToken": null
    },
    "user": null
}

I've never used Lucid-Mongo, but I would assume the api is the same; however, since you already have the user's email you can query the user model to return it
const User = use('App/Models/User')

async auth({request, response, auth}) {
    const { email, password } = request.all()
    let token = await auth.attempt(email, password)
    let user = await User.query().where('email', email).fetch()
    return {} // your structured object
}

Hi, just do this:
async function auth({request, response, auth}) {
    const { email, password } = request.all();
    let auth0 = await auth.attempt(email, password);
    auth0.user =  await auth.getUser();
    return auth0;
}

@touskar Using this code, I received the following response:
{
    "response": "E_INVALID_JWT_TOKEN: jwt must be provided"
}

Hi @bryannbarbosa I don't think this is an issue and it is inappropriate to post it here.
I best suited for the forum and you will get faster response there.

Hey @jpcbarros! 👋
If you have any bugs with the framework feel free to open a new issue.
If you have any questions, please open a thread on the forum or join the discord server.

This is in fact an issue, there's no login method to return the user information and auth.attempt returns token.
Right now i need to include some of the user info as jwtPayload when user signs in and certainly you can't do it with auth.attempt because you don't have the user object yet.
It's not ideal at all to use auth.attempt just to check uid and pass matches and then try to get the user and then regenerate the token with your jwt playload/claim. For one you're making extra call to the database for second you're wasting resources calculating jwt token twice.
There needs to be either something like auth.login method which checks the credential and returns user object if successful or make auth.attempt do it and use auth.generate for generating tokens.

This is in fact something we can have in consideration for the next release of Adonis @Tim-MCC.
I would recommend to create an RFC explaining exactly what you want and expect. 👍


Port XACC (Build + Test) CI to GitHub Actions

This will remove dependency on the external GitLab runner.
Sometimes, the pipeline may fail sporadically, e.g., due to downloading Boost (https://code.ornl.gov/qci/xacc/-/jobs/1075894).
Having CI in GitHub allows XACC committers to control the pipeline (e.g., rerun)
GitHub Actions is free for open-source repositories and we can run both Linux and Mac build.
My testing shows that it takes ~20 mins to build and test XACC (Linux and Mac pipelines can run simultaneously)

@amccaskey what do you think?

I think this is a great idea. I've looked into it before, but I always thought the free VMs would be too slow (at least, much slower than the CADES VMs we had).
At this point, I don't think we have much choice. It is important to move away from the existing Gitlab CI/CD. This is probably the easiest next step, and we can update to better VMs later if possible.


Bug: try_join! macro blocks on first.

In my testing on a work project, I found that unfortunately try_join! will block on the execution of the first future. join! does work perfectly, executing both futures concurrently.
This is reproducible by creating two async functions with blocking operations in each that return Result types. Using try_join! will never complete if the first blocks indefinitely, and the second future will not be run concurrently.

None of the internal concurrency primitives provided in futures will handle blocking futures correctly (which is basically everything outside of futures::executor). I'm not sure why you're seeing join! work, it should function identically to try_join! in this case, they both poll in order in the current implementation so will both stop if the first future blocks.
It might be a good idea to add a crate-level documentation section explaining that blocking will mess with internal concurrency, and link to it from relevant places (all the join and select macros/functions, Futures{Un,}Ordered, etc.)


Disable text selection for the checkbox

Is there a reason selecting label text is discouraged?

Hey @pespantelis. Thank you for the PR!
However, I agree with @Garbee that this should be user style and not in MDL. Vanilla checkboxes have selectable text as well: http://codepen.io/surma/pen/rOLxjJ


[storage] Port PR #24759 from storage/stable

port tests
use isBrowser from core-util
port the source changes
re-generate client
update test resource names to use different variable names. New recorder
unique names are slightly different from previous version and cause same name to
be retrieved for "dir" variable.
add recordings

API change check
API changes are not detected in this pull request.


feat(create branch): respect git prefix and optionally add wi id when creating branch

Respect the Git: Branch prefix setting if defined, as proposed in #7
Introduce a configuration setting azdevops-vscode-simplify.useWorkitemIdInBranchName to trigger the inclusion of the work item id in the proposed branch name, as proposed in #8

@DavidFeldhoff sorry, please PTAL again as I had to resolve a merge conflict in the changelog


⚠ Bofrost.lu has degraded performance

In c28e19e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 928 ms

Resolved: Bofrost.lu performance has improved in be6f835.


Check wiki format availability

This commit adds functionality to check availability of wiki formats. This information can be used by gollum/gollum#1173 to visually signal the availability of wiki formats and fix gollum/gollum#705.

This is an redo of #251.

Great stuff. Will merge ASAP, but perhaps can you still squash this commit into logical chunks, or just into one commit? (With git rebase -i HEAD~9, in this case)

Done.

🎆 Thanks!

Terrific! 🎆 🎉 👍


Add faster NegativeBinomial

Codecov Report
Attention: Patch coverage is 95.55556% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 83.16%.  Consider uploading reports for the commit 8fbaa2e to get more accurate results

Files
Patch %
Lines

preliz/distributions/negativebinomial.py
96.55%
3 Missing :warning:

preliz/internal/special.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #351      +/-   ##
==========================================
+ Coverage   83.06%   83.16%   +0.09%
==========================================
  Files          48       49       +1
  Lines        4890     4929      +39
==========================================
+ Hits         4062     4099      +37
- Misses        828      830       +2

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


I have some questions about “Minimizing Instance Uncertainty to align the distributions of the labeled and unlabeled instances”

Hi, I think that there are some problems in your derivation and analysis:

theta_g and theta_f1/2 are non-linear, so the step 4 is not reasonable.

There is indeed a feature vector, which can make loss=0.

Minimizing the distribution bias is achieved by TWO steps (maximizing AND minimizing uncertainty, as shown in Fig. 2(a) ) but not only minimizing uncertainty. The reduction of bias is achieved in such an iterative process but not a single step.


Implement "make_note" action

[ ] Define the grammar
[ ] Implement keyboard shortcut

This needs to be refactored as something grammar-based...

Superseded by #33 and parse ("p") action for CropObjectView selection.


How to resolve v8 deprecated warnings

Installed Node version - v - 7.7.1
warning: ‘v8::Localv8::Object v8::Function::NewInstance(int, v8::Localv8::Value*) const’ is deprecated (declared at /root/.node-gyp/7.7.1/include/node/v8.h:3657): Use maybe version [-Wdeprecated-declarations]  info.GetReturnValue().Set(cons->NewInstance(argc, argv));
Code -
v8::Localv8::Value argv[argc] = { info[0] };
v8::Localv8::Function cons = Nan::Newv8::Function(constructor);
info.GetReturnValue().Set(cons->NewInstance(argc, argv));
if we use Nan wrapper Nan::MaybeLocal instead of v8::Local  can't call cons->NewInstance function.
Pls suggest how to resolve this

Its resolved by using  info.GetReturnValue().Set(Nan::NewInstance(cons, argc, argv).ToLocalChecked());

work for me


Icon Fonts not showing up in Unpackaged Windows Deployment

Describe the bug
When using new .NET8 Unpackaged Windows Deployment  the icon font is not included/applied in the published App. (MauiIcons 2.0). I haven't tested with MSIX deployment yet, so can't say if it works there.
I made simple example based on .NET8 Maui Hello World template. I only replaced the dot net bot image with a Mood Material Icon.
See code in GitHub Repo (MauiIcon branch)
or patch against base template here:
MauiIconsInHelloWorldMaui.patch
This is how it looks like
from IDE: OK

published: NOT OK

Thanks for reporting this issue, I'll try diagnosing this issue on Sample Application and Get Back to you

@KaFo Also would you mind explaining the patch url? What is that file

@KaFo the issue seems to be related this issue
https://github.com/dotnet/maui/issues/9104
Will investigate this further and come with a solution as soon as possible

Hi. Thank you for investigating this. Seems quite a few problems with maui development end up being<EMAIL_ADDRESS>But at least they gave it prio "p/1". Which means "Work that is critical for release but we can probably ship without". Hargh Hargh. :-)

Is Shipping your application as unpackaged is business requirement? As I do consultation on lots of enterprise application, I do always recommend to ship windows application as packaged. I know your milage may vary but still I recommend packaged over unpackaged since the advantages of packaged makes unpackaged kind a obsolete in this day and age.

Hi I have same problem here, any solution?

Hi I have same problem here, any solution?

We are waiting for fix on Maui Side, as far as now, I'm not aware of any workarounds

Hello Folks,
Update on this issue, This issue is finally Fixed with Win2D v1.2.0, we can expect to Maui to update the Win2D Dependency to v1.2.0 upcoming service releases. Once that's done, we can finally close this issue

AFAIK, the upstream issue was fixed months ago in Maui. I haven't tried the project myself, but at a quick glance it looks like MauiVersion here has been left at its default, so its value would be defined by the toolchain (currently Maui 8.0.21 assuming VS 17.10.1), currently latest Maui is 8.0.40. But the Win2D dependency could also be bumped explicitly with a PackageReference (if you're targetting 8.0.10 or later).

Is there a workaround / solution for using this library on an unpackaged app as of the current state? I noticed this issue referenced recently but the context doesn't make much sense given what I'm able to read. What is the current status of this issue in this regard?


Forgetting curve

Record time for each card, Forgetting curve Scientific revision time,
A ringtone alerts the user that it's time to review.
After playing the voice, it automatically switches to the next card.

Please allocate this task to me. I'm capable of tackling it as I possess all the requisite skills to address the matter at hand.

While doing so remember the progress of #4 too as that issue proposes the same thing too...

Would be happy to work on this issue. Please allocate it to me


Unexpected behavior in our database for non-US currency token orders

{{ count }} tokens
amount due expressed in US dollars

that's because that agreement was made before we stored the amount of tokens


GetClientRect instead of GetWindowRect in standalone win32 example

I think you meant to use GetClientRect instead of GetWindowRect in the below file.
Otherwise the RECT is oversized and the sizing controls on the right and bottom will not function.
Xaml-Islands-Samples/Standalone_Samples/CppWinRT_Desktop_Win32App/DesktopWin32App/DesktopWin32App.cpp

Thanks @thomasbarker for the the recommendation. The sample was removed. Please follow up other samples. Thanks!


Block of text appearing on every page of P5.js Hindi translation

Actual Behaviour
Some taglines are appearing on every page of p5.js Hindi Translation.
Expected Behaviour
Removing the taglines should fix this problem. I have shared some screenshots below.
Screenshots of the issue

Would you like to work on the issue?
Yes I would like to work on this issue

I have checked the en.yml file for the P5.js site, it also has the same taglines. I think there is something wrong with the index.hbs file in Hindi branch. I will look for any error and then I have a PR. Thanks

I'm not sure we need to removed the taglines completely since I don't understand why the taglines are so long (they should be a short sentence only), which seems like a bug to me (maybe the Hindi yml file has formatting issues?)

@limzykenneth the taglines have been commented here and not shown anymore.

@SanjaySinghRajpoot I would suggest you to always wait until the issue is assigned to you before raising a PR. 🙂

fixed in #1023


Responsive Layout

Specs by @jouni
Depends on #5 (multiple columns), where “column count” is described.
Column count is reduced at certain breakpoints. The developer can configure those if needed using a CSS custom property, e.g. --vaadin-form-layout-columns.
The property value format is a comma-separated list of space-separated values of a CSS length and a number, where the CSS length indicates the breakpoint width and the number indicates the column count. The length value can be omitted which equals it to 0.
The default value for that property is 0, 20em 1, 40em 2, which means the following:
When the layout width (independent of the browser viewport width) is:

< 20em column count is 0
>= 20em and < 40em column count is 1.
>= 40em column count is 2.

More examples:

--vaadin-form-layout-columns: 0; column count is always 0
--vaadin-form-layout-columns: 3; column count is always 3
--vaadin-form-layout-columns: 0 3; column count is always 3
--vaadin-form-layout-columns: 3 0; invalid length (3 == 0), column count is always 0
--vaadin-form-layout-columns: 0, 400px 2; column count is 0 below 400px, and 2 above 400px
--vaadin-form-layout-columns: 1, 600px 2; column count is 1 below 600px, and 2 otherwise
--vaadin-form-layout-columns: 0, 40em 1, 20em 2; column count is 0 below 20em and 2 above 20em. The value 40em 1 is parsed correctly (and perhaps even applied), but it never takes precendence over the following value.
--vaadin-form-layout-columns: none; any unrecognized value (including single length values like 123px) is ignored and equals to 0.

This is so closely related to #5 (multiple columns) it feels to me they should be done together.

At least I provided the designs for this in a comment in #5.

Updated the specs. The --vaadin-form-layout-columns property is probably controversial, so take some time to think about it.

https://picturepan2.github.io/spectre/layout.html

We could consider dropping the number from the syntax and just leave the threshold values:

columns='400px' column count is 1 below 400px, and 2 above 400px
columns='400px 600px' column count is 1 below 400px, and 2 above 400px, and 3 above 600px


Fix tinyusb_driver_install (dangling pointer)

Pointer to gpio_conf variable was used out of its scope. This caused dereference to some trash values in the following call usb_new_phy(). I moved the variable definition to include usb_new_phy() call in its scope and now it's working ok.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.lsita seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your contribution.

sha=db90b512a11479a11275b4f08d5ea35127d9c4c0


AD Credentials not working for SMB file share

We recently implemented AD authentication for Azure smb file shares to test out. All seems to go well, but after giving users permissions to those shares, they are unable to logon with their AD credentials. Upon putting the smb path in file explorer, they are prompted for credentials but receive an access denied or in some instances a message that the remote device or resource wont accept the connection.

@onalos , Please let us know if you have any further question.


Questions on Yolov9-MIT

Interesting repo. I notice the notation to predict/train models is totally different from regular YOLO. Is that correct? e.g. we can not call python yolo detect train dataset=data.yaml device=0,1. Is it correct?
Also, how does it perform against the original yolov9 in terms of mAP and speed?

Q1
Yes and no. The command lines are different. For example:
Inference with a webcam can be done using python yolo/lazy.py task.data.source=0 or directly running $yolo task.data.source=0 in the command line. For more argument examples, you can refer to the HOWTO page. We will provide detailed documentation for the arguments in the future.
For your specific command example, you can use yolo task=train dataset=data.yaml. For multiple GPU training, use torchrun --nproc_per_node=gpu yolo/lazy.py.
Currently, we only support detection tasks, but more tasks will be implemented in the near future!
This repository is the official implementation of YOLOv9. The theoretical results should be the same as or better than the original YOLOv9 in terms of performance and inference speed. Some functions are still in progress.

Thanks. So 2 recommendations:
In the future, maybe we can use the exact arguments used in yolo for better usability?
Maybe we benefit from adding classification task as well.


migration fails with Cassandra cluster

Hi,
I got a problem that the kong start fails on a fresh installation of kong.
A kong schema migration step fails after  spinning up a kong docker container running against a Cassandra cluster with multiple nodes. Cassandra and kong are running as docker containers within OpenShift.
Kong version 0.10.0RC3
docker container of kong based on: https://github.com/Mashape/docker-kong
cassandra version: 2.2 and 3
The Cassandra cluster is in a healthy state and no keyspace kong exists
nodetool status
Datacenter: datacenter1
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address    Load       Tokens       Owns (effective)  Host ID                               Rack
UN  <IP_ADDRESS>   83.11 KiB  32           100.0%            1bf1c845-d9c3-494b-893a-d39bfd576b2d  rack1
UN  <IP_ADDRESS>  65.66 KiB  32           100.0%            b0a33b1d-7dda-4b01-9984-f4cbff6608c3  rack1
The cluster is blank and no kong keyspace exist
cqlsh
Connected to Test Cluster at <IP_ADDRESS>:9042.
[cqlsh 5.0.1 | Cassandra 3.9 | CQL spec 3.4.2 | Native protocol v4]
Use HELP for help.
cqlsh> describe keyspaces
system_traces  system_schema  system_auth  system  system_distributed
cqlsh>
If I spin up a kong container it fails during the migration process
W0209 16:26:43.790349    2097 cmd.go:269] log is DEPRECATED and will be removed in a future version. Use logs instead.
2017/02/09 03:25:37 [verbose] Kong: 0.10.0rc3
2017/02/09 03:25:37 [debug] ngx_lua: 10007
2017/02/09 03:25:37 [debug] nginx: 1011002
2017/02/09 03:25:37 [debug] Lua: LuaJIT 2.1.0-beta2
2017/02/09 03:25:37 [debug] PRNG seed:<PHONE_NUMBER>87
2017/02/09 03:25:37 [verbose] no config file found at /etc/kong/kong.conf
2017/02/09 03:25:37 [verbose] no config file found at /etc/kong.conf
2017/02/09 03:25:37 [verbose] no config file, skipping loading
2017/02/09 03:25:37 [debug] KONG_CASSANDRA_CONTACT_POINTS ENV found with "cassandra-cluster"
2017/02/09 03:25:37 [debug] KONG_PG_HOST ENV found with "cassandra-cluster"
2017/02/09 03:25:37 [debug] KONG_NGINX_DAEMON ENV found with "off"
2017/02/09 03:25:37 [debug] KONG_DATABASE ENV found with "cassandra"
2017/02/09 03:25:37 [debug] admin_listen = "<IP_ADDRESS>:8001"
2017/02/09 03:25:37 [debug] admin_listen_ssl = "<IP_ADDRESS>:8444"
2017/02/09 03:25:37 [debug] admin_ssl = true
2017/02/09 03:25:37 [debug] anonymous_reports = true
2017/02/09 03:25:37 [debug] cassandra_consistency = "ONE"
2017/02/09 03:25:37 [debug] cassandra_contact_points = {"cassandra-cluster"}
2017/02/09 03:25:37 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
2017/02/09 03:25:37 [debug] cassandra_keyspace = "kong"
2017/02/09 03:25:37 [debug] cassandra_lb_policy = "RoundRobin"
2017/02/09 03:25:37 [debug] cassandra_port = 9042
2017/02/09 03:25:37 [debug] cassandra_repl_factor = 1
2017/02/09 03:25:37 [debug] cassandra_repl_strategy = "SimpleStrategy"
2017/02/09 03:25:37 [debug] cassandra_ssl = false
2017/02/09 03:25:37 [debug] cassandra_ssl_verify = false
2017/02/09 03:25:37 [debug] cassandra_timeout = 5000
2017/02/09 03:25:37 [debug] cassandra_username = "kong"
2017/02/09 03:25:37 [debug] cluster_listen = "<IP_ADDRESS>:7946"
2017/02/09 03:25:37 [debug] cluster_listen_rpc = "<IP_ADDRESS>:7373"
2017/02/09 03:25:37 [debug] cluster_profile = "wan"
2017/02/09 03:25:37 [debug] cluster_ttl_on_failure = 3600
2017/02/09 03:25:37 [debug] custom_plugins = {}
2017/02/09 03:25:37 [debug] database = "cassandra"
2017/02/09 03:25:37 [debug] dns_hostsfile = "/etc/hosts"
2017/02/09 03:25:37 [debug] dns_resolver = {}
2017/02/09 03:25:37 [debug] log_level = "notice"
2017/02/09 03:25:37 [debug] lua_code_cache = "on"
2017/02/09 03:25:37 [debug] lua_package_cpath = ""
2017/02/09 03:25:37 [debug] lua_package_path = "?/init.lua;./kong/?.lua"
2017/02/09 03:25:37 [debug] lua_ssl_verify_depth = 1
2017/02/09 03:25:37 [debug] mem_cache_size = "128m"
2017/02/09 03:25:37 [debug] nginx_daemon = "off"
2017/02/09 03:25:37 [debug] nginx_optimizations = true
2017/02/09 03:25:37 [debug] nginx_worker_processes = "auto"
2017/02/09 03:25:37 [debug] pg_database = "kong"
2017/02/09 03:25:37 [debug] pg_host = "cassandra-cluster"
2017/02/09 03:25:37 [debug] pg_port = 5432
2017/02/09 03:25:37 [debug] pg_ssl = false
2017/02/09 03:25:37 [debug] pg_ssl_verify = false
2017/02/09 03:25:37 [debug] pg_user = "kong"
2017/02/09 03:25:37 [debug] prefix = "/usr/local/kong/"
2017/02/09 03:25:37 [debug] proxy_listen = "<IP_ADDRESS>:8000"
2017/02/09 03:25:37 [debug] proxy_listen_ssl = "<IP_ADDRESS>:8443"
2017/02/09 03:25:37 [debug] serf_path = "serf"
2017/02/09 03:25:37 [debug] ssl = true
2017/02/09 03:25:37 [debug] upstream_keepalive = 60
2017/02/09 03:25:37 [verbose] prefix in use: /usr/local/kong
2017/02/09 03:25:37 [verbose] preparing nginx prefix directory at /usr/local/kong
2017/02/09 03:25:37 [verbose] saving serf identifier to /usr/local/kong/serf/serf.id
2017/02/09 03:25:37 [debug] searching for OpenResty 'resty' executable
2017/02/09 03:25:37 [debug] /usr/local/openresty/bin/resty -V: 'nginx version: openresty/<IP_ADDRESS>'
2017/02/09 03:25:37 [debug] found OpenResty 'resty' executable at /usr/local/openresty/bin/resty
2017/02/09 03:25:37 [verbose] saving serf shell script handler to /usr/local/kong/serf/serf_event.sh
2017/02/09 03:25:37 [verbose] SSL enabled, no custom certificate set: using default certificate
2017/02/09 03:25:37 [verbose] generating default SSL certificate and key
2017/02/09 03:25:38 [verbose] Admin SSL enabled, no custom certificate set: using default certificate
2017/02/09 03:25:38 [verbose] generating admin SSL certificate and key
2017/02/09 03:25:38 [verbose] running datastore migrations
2017/02/09 03:25:38 [info] migrating core for keyspace kong
2017/02/09 03:25:40 [info] core migrated up to: 2015-01-12-175310_skeleton
2017/02/09 03:26:03 [info] core migrated up to: 2015-01-12-175310_init_schema
2017/02/09 03:26:06 [info] core migrated up to: 2015-11-23-817313_nodes
2017/02/09 03:26:07 [info] core migrated up to: 2016-02-25-160900_remove_null_consumer_id
2017/02/09 03:26:07 [info] core migrated up to: 2016-02-29-121813_remove_ttls
2017/02/09 03:26:09 [info] core migrated up to: 2016-09-05-212515_retries_step_1
2017/02/09 03:26:09 [info] core migrated up to: 2016-09-05-212515_retries_step_2
2017/02/09 03:26:14 [info] core migrated up to: 2016-09-16-141423_upstreams
2017/02/09 03:26:23 [info] core migrated up to: 2016-12-14-172100_move_ssl_certs_to_core
2017/02/09 03:26:27 [info] core migrated up to: 2016-11-11-151900_new_apis_router_1
2017/02/09 03:26:28 [info] core migrated up to: 2016-11-11-151900_new_apis_router_2
2017/02/09 03:26:34 [info] core migrated up to: 2016-11-11-151900_new_apis_router_3
2017/02/09 03:26:35 [info] core migrated up to: 2016-09-16-141423_upstreams
2017/02/09 03:26:35 [info] migrating request-transformer for keyspace kong
2017/02/09 03:26:35 [info] request-transformer migrated up to: 2016-03-10-160000_req_trans_schema_changes
2017/02/09 03:26:35 [info] migrating rate-limiting for keyspace kong
2017/02/09 03:26:37 [info] rate-limiting migrated up to: 2015-08-03-132400_init_ratelimiting
2017/02/09 03:26:37 [info] rate-limiting migrated up to: 2016-07-25-471385_ratelimiting_policies
2017/02/09 03:26:37 [info] migrating jwt for keyspace kong
2017/02/09 03:26:42 [info] jwt migrated up to: 2015-06-09-jwt-auth
2017/02/09 03:26:43 [info] jwt migrated up to: 2016-03-07-jwt-alg
2017/02/09 03:26:43 [info] migrating hmac-auth for keyspace kong
2017/02/09 03:26:50 [info] hmac-auth migrated up to: 2015-09-16-132400_init_hmacauth
2017/02/09 03:26:50 [info] migrating ip-restriction for keyspace kong
2017/02/09 03:26:50 [info] ip-restriction migrated up to: 2016-05-24-remove-cache
2017/02/09 03:26:50 [info] migrating response-ratelimiting for keyspace kong
2017/02/09 03:26:51 [info] response-ratelimiting migrated up to: 2015-08-21_init_response-rate-limiting
2017/02/09 03:26:52 [info] response-ratelimiting migrated up to: 2016-08-04-321512_response-rate-limiting_policies
2017/02/09 03:26:52 [info] migrating galileo for keyspace kong
2017/02/09 03:26:52 [info] galileo migrated up to: 2016-04-15_galileo-import-mashape-analytics
2017/02/09 03:26:52 [info] migrating acl for keyspace kong
2017/02/09 03:26:59 [info] acl migrated up to: 2015-08-25-841841_init_acl
2017/02/09 03:26:59 [info] migrating basic-auth for keyspace kong
2017/02/09 03:27:04 [info] basic-auth migrated up to: 2015-08-03-132400_init_basicauth
2017/02/09 03:27:04 [info] migrating oauth2 for keyspace kong
2017/02/09 03:27:22 [info] oauth2 migrated up to: 2015-08-03-132400_init_oauth2
2017/02/09 03:27:23 [info] oauth2 migrated up to: 2015-08-24-215800_cascade_delete_index
2017/02/09 03:27:24 [info] oauth2 migrated up to: 2016-02-29-435612_remove_ttl
2017/02/09 03:27:24 [info] oauth2 migrated up to: 2016-04-14-283949_serialize_redirect_uri
2017/02/09 03:27:25 [info] oauth2 migrated up to: 2016-07-15-oauth2_code_credential_id
2017/02/09 03:27:26 [info] oauth2 migrated up to: 2016-09-19-oauth2_code_index
2017/02/09 03:27:30 [info] oauth2 migrated up to: 2016-09-19-oauth2_api_id
2017/02/09 03:27:31 [info] oauth2 migrated up to: 2016-12-15-set_global_credentials
2017/02/09 03:27:31 [info] migrating response-transformer for keyspace kong
2017/02/09 03:27:31 [info] response-transformer migrated up to: 2016-03-10-160000_resp_trans_schema_changes
2017/02/09 03:27:31 [info] migrating key-auth for keyspace kong
2017/02/09 03:27:34 [info] key-auth migrated up to: 2015-07-31-172400_init_keyauth
2017/02/09 03:27:34 [info] 35 migrations ran
2017/02/09 03:27:34 [verbose] migrations up to date
Error:
/usr/local/share/lua/5.1/kong/cmd/start.lua:34: /usr/local/share/lua/5.1/kong/cmd/start.lua:23: nginx: [error] init_by_lua error: /usr/local/share/lua/5.1/kong.lua:133: [cassandra error] Error during migration 2016-09-05-212515_retries_step_1: [Invalid] Invalid column name retries because it conflicts with an existing column
stack traceback:
[C]: in function 'assert'
/usr/local/share/lua/5.1/kong.lua:133: in function 'init'
init_by_lua:4: in main chunk
stack traceback:
[C]: in function 'error'
/usr/local/share/lua/5.1/kong/cmd/start.lua:34: in function 'cmd_exec'
/usr/local/share/lua/5.1/kong/cmd/init.lua:89: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:89>
[C]: in function 'xpcall'
/usr/local/share/lua/5.1/kong/cmd/init.lua:89: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:45>
/usr/local/bin/kong:5: in function 'file_gen'
init_worker_by_lua:38: in function <init_worker_by_lua:36>
[C]: in function 'pcall'
init_worker_by_lua:45: in function <init_worker_by_lua:43>
2017/02/09 03:27:34 [verbose] serf agent not running, deleting /usr/local/kong/pids/serf.pid
2017/02/09 03:27:34 [debug] checking 'serf' executable from 'serf_path' config setting
2017/02/09 03:27:35 [debug] serf version: 'Serf v0.8.0'
2017/02/09 03:27:35 [debug] starting serf agent: nohup serf agent -profile 'wan' -rpc-addr '<IP_ADDRESS>:7373' -event-handler 'member-join,member-leave,member-failed,member-update,member-reap,user:kong=/usr/local/kong/serf/serf_event.sh' -bind '<IP_ADDRESS>:7946' -node 'kong-4-2qaic_<IP_ADDRESS>:7946_60c14944a09e40509143f9f4dd282a36' -log-level 'err' > /usr/local/kong/logs/serf.log 2>&1 & echo $! > /usr/local/kong/pids/serf.pid
2017/02/09 03:27:35 [verbose] waiting for serf agent to be running
2017/02/09 03:27:35 [debug] sending signal to pid at: /usr/local/kong/pids/serf.pid
2017/02/09 03:27:35 [debug] kill -0 cat /usr/local/kong/pids/serf.pid >/dev/null 2>&1
2017/02/09 03:27:35 [verbose] serf agent started
2017/02/09 03:27:35 [verbose] auto-joining serf cluster
2017/02/09 03:27:35 [verbose] no other nodes found in the cluster
2017/02/09 03:27:35 [verbose] registering serf node in datastore
2017/02/09 03:27:35 [verbose] cluster joined and node registered in datastore
2017/02/09 03:27:35 [debug] searching for OpenResty 'nginx' executable
2017/02/09 03:27:35 [debug] /usr/local/openresty/nginx/sbin/nginx -v: 'nginx version: openresty/<IP_ADDRESS>'
2017/02/09 03:27:35 [debug] found OpenResty 'nginx' executable at /usr/local/openresty/nginx/sbin/nginx
2017/02/09 03:27:35 [debug] starting nginx: /usr/local/openresty/nginx/sbin/nginx -p /usr/local/kong -c nginx.conf
2017/02/09 03:27:37 [verbose] could not start Kong, stopping services
2017/02/09 03:27:37 [verbose] leaving serf cluster
2017/02/09 03:27:37 [verbose] left serf cluster
2017/02/09 03:27:37 [verbose] stopping serf agent at /usr/local/kong/pids/serf.pid
2017/02/09 03:27:37 [debug] sending signal to pid at: /usr/local/kong/pids/serf.pid
2017/02/09 03:27:37 [debug] kill -15 cat /usr/local/kong/pids/serf.pid >/dev/null 2>&1
2017/02/09 03:27:37 [verbose] serf agent stopped
2017/02/09 03:27:37 [verbose] stopped services

Hmm.. I'm getting the same error:
2017/02/16 17:47:57 [verbose] Kong: 0.9.8
2017/02/16 17:47:57 [verbose] no config file found at /etc/kong.conf
2017/02/16 17:47:57 [verbose] reading config file at /etc/kong/kong.conf
2017/02/16 17:47:57 [verbose] prefix in use: /usr/local/kong
2017/02/16 17:47:57 [verbose] preparing nginx prefix directory at /usr/local/kong
2017/02/16 17:47:57 [verbose] saving serf identifier to /usr/local/kong/serf/serf.id
2017/02/16 17:47:57 [verbose] saving serf shell script handler to /usr/local/kong/serf/serf_event.sh
2017/02/16 17:47:57 [verbose] SSL enabled, no custom certificate set: using default certificate
2017/02/16 17:47:57 [verbose] default SSL certificate found at /usr/local/kong/ssl/kong-default.crt
2017/02/16 17:47:57 [warn] ulimit is currently set to "1024". For better performance set it to at least "4096" using "ulimit -n"
2017/02/16 17:47:57 [verbose] running datastore migrations
2017/02/16 17:47:57 [warn] 10233#0: *2 [lua] log.lua:22: warn(): No cluster infos in shared dict cassandra, context: ngx.timer
2017/02/16 17:47:57 [info] migrating core for keyspace kong
2017/02/16 17:47:57 [info] core migrated up to: 2015-01-12-175310_skeleton
2017/02/16 17:47:58 [info] core migrated up to: 2015-01-12-175310_init_schema
2017/02/16 17:47:58 [info] core migrated up to: 2015-11-23-817313_nodes
2017/02/16 17:47:58 [info] core migrated up to: 2016-02-25-160900_remove_null_consumer_id
2017/02/16 17:48:00 [info] core migrated up to: 2016-02-29-121813_remove_ttls
2017/02/16 17:48:00 [info] migrating jwt for keyspace kong
2017/02/16 17:48:00 [info] jwt migrated up to: 2015-06-09-jwt-auth
2017/02/16 17:48:00 [verbose] could not start Kong, stopping services
2017/02/16 17:48:00 [verbose] leaving serf cluster
2017/02/16 17:48:00 [verbose] left serf cluster
2017/02/16 17:48:00 [verbose] stopping serf agent at /usr/local/kong/pids/serf.pid
2017/02/16 17:48:00 [verbose] serf agent stopped
2017/02/16 17:48:00 [verbose] stopping dnsmasq at /usr/local/kong/pids/dnsmasq.pid
2017/02/16 17:48:00 [verbose] stopped services
Error:
/usr/local/share/lua/5.1/kong/cmd/start.lua:37: /usr/local/share/lua/5.1/kong/cmd/start.lua:18: Error during migration 2016-03-07-jwt-alg: [Invalid] Invalid column name algorithm because it conflicts with an existing column
stack traceback:
[C]: in function 'error'
/usr/local/share/lua/5.1/kong/cmd/start.lua:37: in function 'cmd_exec'
/usr/local/share/lua/5.1/kong/cmd/init.lua:89: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:89>
[C]: in function 'xpcall'
/usr/local/share/lua/5.1/kong/cmd/init.lua:89: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:45>
/usr/local/bin/kong:13: in function 'file_gen'
init_worker_by_lua:38: in function <init_worker_by_lua:36>
[C]: in function 'pcall'
init_worker_by_lua:45: in function <init_worker_by_lua:43>

One workaround is to change number of replicas of your container to 1, let it finish migrating, then scale back up to two and try again.
Has this worked for you?

One workaround is to change the number of replicas of your container to 1, let it finish migrating, then scale back up to two and try again.
Obviously, this works initially. However, a restart of the Kong containers results in the same migration issue...

Try dropping the kong keyspace and try again maybe? Make sure the Cassandra containers are using persistent storage too.

I see the same error as well, dropping the keyspace cant be an answer to resolving this issue, this should be a bug, seems to be a persistent issue with many people, we have a cluster for cassandra using persistent storage and this still happens, it's a nasty bug which doesn't seem to be getting much attention

Thanks everyone for your input.
We tried deleting and re-adding the keystore. That did not resolve the problem for us. However, we did realize that our servers were reporting different times. It's early but after fixing NTP it looks like we are no longer seeing the duplicate entry issue.

Hi,
If you are encountering this problem and you are on a 0.10 RC, would you mind trying out the patch available at #2145? I believe it should greatly help (with both consistency and speed of the migrations).
Feedback is greatly appreciated on this PR.
Thanks!

Considering this fixed with #2145 since there was no reply.