text:
ngx-mat-timepicker shows "invalidDateTime" in Brave Browser but works fine in Chrome and Edge

Whenever I try to use ngx-time-picker package, the user will click the input box and a menu will pop up where they can select the time. However after selecting the time "Invalid DateTime". This only happens with Brave Browser. However , whenever I try it on Google Chrome or Microsoft Edge, the ngx-time-picker works just fine as the time selected by the user from the popup menu is the time displayed in the input box. What might be causing this?
https://stackoverflow.com/questions/75393607/ngx-mat-timepicker-shows-invaliddatetime-in-brave-browser-but-works-fine-in-ch

The issue has not surfaced with Chrome also with the move to chromium 110.0.5481.77/78. Currently edge is on 109 version thus it works on Edge. Please suggest any workaround / fix for Chrome and Brave.

Ok, I'm closing this as duplicate of #51

repo: tonysamperi/ngx-mat-timepicker


text:
Should I consider JPEGMeta Struct Here A Bad Pattern in the Context of C++?

Just to suggest that this JPEGMeta be handled with a class with RAII pattern instead of struct.
So that no manual allocation is needed (done in constructor), and no manual deallocation, plus a reasonable move or copy assignment syntax.
Perhaps this is not the point of this course. But I do think this may be a point of improvement for future students to learn from best & safe practices (in the context of CPP).

I agree with you. In context of modern C++ using here, I think it is good to use RAII and other modern C++ features for this struct. 👍

Thanks for pointing out! I will refine this struct for the next semster.

Thank you for your comments, and we will strive to adhere to modern C++ conventions in our future projects. In fact, for Assignment2, I have already implemented the modern C++ style. However, for the sake of performance optimization, there are instances where it is preferable to minimize excessive abstractions. As a result, the code structure for Assignment2 does not heavily rely on modern C++ features. Thank you for your understanding.

Performance is a good point! CppCon 2019: Chandler Carruth “There Are No Zero-cost Abstractions” on the cost of unique_ptr.

source: gharchive/issue

authors: Congyuwang I-am-Future MeloYang05 tonyyxliu

license: MIT

license_type: permissive

license_source: github-api


text:
Hide pacing indicator for not current month

I think that the pacing indicator for the budget rows progress bars should not show up for months that are not current. ie the line that indicates how far through the month we are. Not a big issue.

We're going to go ahead and track enhancement requests on the Trello roadmap. I've added your request to the Under Discussion column and we'll track conversation on it here: https://trello.com/c/guYvaOcI/233-hide-pacing-indicator-for-months-that-aren-t-the-current-month
Thank you!

authors: auhsor blargity

repo: toolkit-for-ynab/toolkit-for-ynab

license: mit

license_source: bigquery


text:
[BUG] "Hide Account Balance" won't toggle back

Describe the bug
Toggling Account Balance back OFF (after briefly working with it ON) does not turn it back off in YNAB.  Even stranger: the running account balance is only on in the two accounts I was working with in YNAB at the time I toggled it back on.  The other accounts are not showing the running balances.  But when I went back to YNAB to test multiple ways of this to report the error, I discovered that ANY account that I'm in when the option gets toggled back ON, and then stays on when toggled back.  It's almost as if there's some residual memory of it in YNAB, even though the Toolkit option is OFF.
To Reproduce
Steps to reproduce the behavior:

Go to Account tab within Toolkit, scroll down to Automatically Enable Running Balance, turn On, back to YNAB, refresh
When finished, go back to toolkit, toggle off, back to YNAB refresh. For me, only accounts I had worked in while it was "Enabled" are staying "Enabled" while the others are as they should be with no running balance.

Expected behavior
Account balances should go away after toggling off and refreshing YNAB
Screenshots
N/A by choice
Desktop (please complete the following information):
Mac OS Monterey 12.3.1
Firefox 120.0.1 (64-bit)
Current version of Toolkit 3.10.1
Setting Export
Please replace the text 'REPLACE_ME_WITH_SETTINGS' below with your exported Toolkit settings. You can export these by going to the Toolkit Options page, click the Import/Export Settings button at the top right and copying the text in the modal which appears.
Note! DO NOT replace the leading and trailing ``` characters as they are required formatting characters.
[{"key":"AccountsDisplayDensity","value":"0"},{"key":"AccountsEmphasizedInflows","value":true},{"key":"AccountsEmphasizedOutflows","value":false},{"key":"AccountsStripedRows","value":false},{"key":"AccountsStripedRowsColor","value":"#fafafa"},{"key":"AccountsStripedRowsDarkColor","value":"#1e1e1f"},{"key":"AssistedClear","value":false},{"key":"AutoDistributeSplits","value":true},{"key":"AutoEnableRunningBalance","value":false},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":"0"},{"key":"BottomNotificationBar","value":false},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":false},{"key":"BudgetQuickSwitch","value":false},{"key":"BudgetSpendingGoal","value":false},{"key":"BulkEditMemo","value":true},{"key":"BulkManagePayees","value":true},{"key":"CalculateIRR","value":false},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":false},{"key":"CategoryActivityPopupWidth","value":"1"},{"key":"CategorySoloMode","value":"0"},{"key":"ChangeEnterBehavior","value":true},{"key":"ChangeMemoEnterBehavior","value":false},{"key":"CheckCreditBalances","value":false},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":false},{"key":"CollapseInspector","value":false},{"key":"ColourBlindMode","value":false},{"key":"CompactAccountHeader","value":false},{"key":"CompactIncomeVsExpense","value":true},{"key":"ConfirmEditTransactionCancellation","value":false},{"key":"ConfirmKeyboardCancelationOfTransactionChanges","value":false},{"key":"CreditCardEmoji","value":false},{"key":"CtrlEnterCleared","value":false},{"key":"CurrentMonthIndicator","value":true},{"key":"CustomAverageBudgeting","value":"6"},{"key":"CustomFlagNames","value":true},{"key":"CustomizeColourScheme","value":true},{"key":"DateOfMoney","value":false},{"key":"DaysOfBuffering","value":false},{"key":"DaysOfBufferingDate","value":false},{"key":"DaysOfBufferingExcludeCreditCards","value":false},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DefaultCCToCleared","value":false},{"key":"DeselectTransactionsOnSave","value":true},{"key":"DisableToolkit","value":false},{"key":"DisplayMonthlyGoalsOverview","value":false},{"key":"DisplayTargetGoalAmount","value":"3"},{"key":"DisplayTotalMonthlyGoals","value":true},{"key":"DisplayTotalOverspent","value":true},{"key":"DisplayUpcomingAmount","value":false},{"key":"EasyTransactionApproval","value":false},{"key":"EditAccountButton","value":"0"},{"key":"EmphasizeNegativeLoans","value":false},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"FilterCategories","value":true},{"key":"GoalIndicator","value":true},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"3"},{"key":"HideAgeOfMoney","value":false},{"key":"HideClosedAccounts","value":true},{"key":"HideDebtRatio","value":true},{"key":"HideHelp","value":true},{"key":"HideReferralBanner","value":true},{"key":"HideTotalAvailable","value":false},{"key":"HighlightNegatives","value":true},{"key":"HoveredBudgetRows","value":true},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"0"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"LinkInMemo","value":false},{"key":"LinkToInflows","value":false},{"key":"LiveOnLastMonthsIncome","value":"0"},{"key":"MasterCategoryRowColor","value":true},{"key":"MasterCategoryRowColorSelect","value":"#d1d1d6"},{"key":"MasterCategoryRowDarkColorSelect","value":"#636366"},{"key":"MemoAsMarkdown","value":false},{"key":"MonthlyNotesPopupWidth","value":"2"},{"key":"NavDisplayDensity","value":"0"},{"key":"NotesAsMarkdown","value":true},{"key":"POSStyleCurrencyEntryMode","value":false},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconcileAssistant","value":false},{"key":"ReconcileBalance","value":false},{"key":"ReconcileConfetti","value":false},{"key":"ReconciledTextColor","value":"4"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":false},{"key":"ResetColumnWidths","value":true},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"SavingsRatio","value":"0.10"},{"key":"ScrollableEditMenu","value":false},{"key":"SeamlessBudgetHeader","value":false},{"key":"SetMultipleFlags","value":false},{"key":"ShowAvailableAfterSavings","value":false},{"key":"ShowCategoryBalance","value":false},{"key":"SpareChange","value":false},{"key":"SplitTransactionAutoAdjust","value":true},{"key":"SplitTransactionAutoFillPayee","value":false},{"key":"SplitTransactionTabExpand","value":true},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":false},{"key":"StripedBudgetRows","value":true},{"key":"SubtractUpcomingFromAvailable","value":"0"},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":false},{"key":"ToggleAccountColumns","value":true},{"key":"ToggleMasterCategories","value":true},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"0"},{"key":"ToolkitReports","value":true},{"key":"UnclearedAccountHighlight","value":false},{"key":"ViewZeroAsEmpty","value":true},{"key":"l10n","value":"0"}]

I wonder if this is something to do with the build.  I can reproduce this bug (using Chrome) with the normal release 3.1.10 installed and turned on.

Here's my steps to prove the bug is not in YNAB itself:

Turn off the entire YNAB Toolkit.
Refresh the browser.
Select an account.
Click the View dropdown.
Turn off Show Running Balance.  The Balance column will disappear.
Refresh the browser.  The Balance column stays off.

Here's my steps to reproduce the bug proving it's in the YNAB Toolkit:

Turn on the YNAB Toolkit.  DO NOT EVEN TURN ON THE Automatically Enable Running Balance option.
Refresh the browser.
Select an account.
Click the View dropdown.
Turn off Show Running Balance.  The Balance column will disappear.
Refresh the browser.  The Balance column will be back on.

Obviously something in the YNAB Toolkit is interfering with the Show Running Balance checkbox in the View dropdown and I'm guessing it's not the Automatically Enable Running Balance feature.
Now here's where it gets weird.  Coincidentally, I just happened to have been working on a new feature (Fund Half) so I pulled the code for version 3.1.10 to add my feature to.

I don't see that bug in my build.  Here's my steps:

Turn off the released build of the YNAB Toolkit.
Turn on my build of the YNAB Toolkit that contains my feature (which has nothing to do with the View dropdown or running balance).
Refresh the browser.
Select an account.
Click the View dropdown.
Turn off Show Running Balance.  The Balance column will disappear.
Refresh the browser.  The Balance column  stays off!

For some reason, my build doesn't have the problem.  I don't know how the options get stored so maybe the saved options are invalid to use for both builds since my build has an additional feature to turn on/off.  However in the OP, it looks like the options are saved as JSON so I wouldn't expect that to be an issue.
If it's not build related my best guess is a different feature, one targeting something in the View dropdown, is misbehaving.
I just wanted to submit this information in case it helps.
@OlegWock @joshmadewell


text:
Feature: Subtract Upcoming Transactions from Available Balance

GitHub Issue (if applicable): #1849
Trello Link (if applicable): https://trello.com/c/kmCAkWVP
Explanation of Bugfix/Feature/Modification:
Subtracts upcoming transactions from the available balance for each category. In other words, treat upcoming transactions as if the money has already been spent. Also shows the total available after upcoming transactions in the budget inspector.

There are currently some issues with this that I'm not sure how to solve. Any help is greatly appreciated.
Known Issues:

Any change made to a category will overwrite the changes made by this feature (e.g. money is moved in or out of the category). Similarly, YNAB seems to refresh the values in the budget page seemingly at random, causing the same issue.

Fix(?): invoke() needs to be run whenever anything is updated.

Switching to the reports page causes YNAB to break: Something has gone wrong likely having to do with internets and tubes. Refresh your browser to get back in business. For some reason the feature is being invoked despite the fact that it should only be running on the budget page.
CSS from Square Negative Mode is not being applied from balances that are being updated by this feature.

There is of course a mismatch between what available says vs. what is actually available with this feature enabled. For example, available could say -$50 (say, $50 budgeted and $100 upcoming), but if you go to move money from the category it will say you have $50 to move. It will also show up as money you can use to cover overspending and such. Personally I think it makes sense. Available should show at a glance the amount you can actually safely spend (point of this feature being that funds for upcoming transactions are not safe to spend). But if you actually need to move money from a category with upcoming transactions, you can.

Cleaned up a lot of the code and fixed several bugs. It now properly updates when there are any changes to categories. I haven't been able to reproduce any crashing either.
I'm not sure if budget-bar-v2 is the best thing to use for the hook for detecting updates on categories.
Also, I can't figure out how to make Square Negative Mode work with this.

Added an option that will subtract the total of your credit card balances from 'Available After Upcoming Transactions' in the budget inspector. That way you can see how much money you would have available excluding money "reserved" for credit card payments.

I absolutely LOVE the idea of this feature.  However, there appear to be a few issues.
If have a scheduled transaction in September, and I budget in the future for that month, it correctly shows an available balance of zero.  However, the balance reappears as available in October and subsequent month.
It also appears that some months are having a netting transaction in the assigned amount.  For example, In September, I budgeted and have a scheduled transaction for a hotel stay for $250.  It correctly shows zero.  But then in October, the assigned amount is -$250.

@shamadoo Thanks for the feedback. I'll see if there's a way to fix that.

Yeah, looking at the code, my guess is you will want to iterate from the displayed month back each month until the current month (another for-loop around line 133).  I'm not sure whether it is more efficient to iterate by category then by month or vice version (might not matter at all).

@adamhl8 is the feature stable now? I just enabled it and loving it! Thank you

source: gharchive/pull-request

authors: adamhl8 dynek shamadoo


text:
Scroll behaviour on Safari

🐛 Bug Report
I have faced an issue related to scroll behaviour on Safari (14.1 version). When i use to
const openModal = () => router.push(makeContextualHref({ pathName: SAMPLE }), SAMPLE, { shallow: true })

for open modal, then scroll is not working on Safari.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Scroll is working properly on Safari.

Hi @enkhtulga,
we should ensure that the issue is caused by next-use-contextual-routing itself. Is scroll broken if you open the modal with a plain router.push call?

authors: enkhtulga toomuchdesign


text:
开启laravel_sms数据库记录后报错。

PhpSms::make()->to('18636600630')->template('YunTongXun', '14453')->data(['12345', 5])->send();

报错如下：

修改了数据库表结构 voive_code 后就可以了。

repo: toplan/laravel-sms


text:
Chewy::UndefinedUpdateStrategy: updating indexed model from within background job

Hello! First off, I love the gem; it's made working with ES super convenient in a few Rails projects I've used. Recently I've had some issues when I try to update an indexed model from within a Sidekiq job. Using Ruby 2.3.1, Rails 4.2.5.2 and Chewy 0.8.2:
In config/initializers/chewy.rb:
Chewy.request_strategy = :sidekiq
Chewy.logger = Logger.new(STDOUT)
Chewy.logger.level = Logger::INFO

and as script that updates our User model (UsersIndex << Chewy::Index):
class SampleWorker
  include Sidekiq::Worker

  def perform(params)
    @params = params

    some_method_that_updates_the_user_model
  end
end

I get:
Chewy::UndefinedUpdateStrategy
Index update strategy is undefined in current context.
Please wrap your code with `Chewy.strategy(:strategy_name) block.`

I have tried following that hint, using strategy(:atomic) and sidekiq, but keep getting the same error message. If I move the update out of the worker, everything works as expected, however it is important that the code in question is performed in the background. I've not been able to find anything relevant to my problem in the docs, sorry if I'm missing something obvious.
Please advise.

well,
def perform(params)
  @params = params

  Chewy.strategy(:atomic) { some_method_that_updates_the_user_model }
end

should do the trick

Hey, sorry for taking so long to get back to this -- I got pulled onto a different project and this fell to the wayside. For whatever reason the way I was wrapping the code in the atomic strategy block was not working previously, but now I am doing something similar with a different model, and it works. Thanks for your help!

I solved this by using an around_perform within ApplicationJob:
class ApplicationJob < ActiveJob::Base
  around_perform do |job, block|
    Chewy.strategy(:atomic) do
      block.call
    end
  end
end

This works because all of my jobs inherit from ApplicationJob.

@perkins2099 Here's how to set a default strategy for sidekiq jobs: https://github.com/education/classroom/pull/378/files

authors: PepperTeasdale oozzal pyromaniac thechrisoshow

repo: toptal/chewy


text:
Are there any concerns using Chewy with GCP Elastic Cloud Managed Service?

Are there any concerns using Chewy with GCP Elastic Cloud Managed Service?
I didn't see an example for that and wanted to make sure there is support for that.
Also is this: https://github.com/toptal/chewy/issues/190 the preferred way of authenticating?

Version 6.8 is available and the official ruby client is supported - that means that it should work with chewy 6. However, I personally didn't have any experience in such setups and haven't heard of them. You can try (they have 14 days trial) and then share your experience here.

Sure will do, thanks!

authors: aabhushan rabotyaga


text:
Installation Problem

Hi All.
I am trying to install cuTorch on a cluster.
The cluster has CUDA lib but it is not in default (/usr/local) directory.
I am using this command:
luarocks install cutorch
and it gives me this error:
Installing https://raw.githubusercontent.com/torch/rocks/master/cutorch-scm-1.rockspec...
Using https://raw.githubusercontent.com/torch/rocks/master/cutorch-scm-1.rockspec... switching to 'build' mode
Initialized empty Git repository in /tmp/luarocks_cutorch-scm-1-7917/cutorch/.git/
remote: Counting objects: 119, done.
remote: Compressing objects: 100% (102/102), done.
remote: Total 119 (delta 45), reused 47 (delta 14), pack-reused 0
Receiving objects: 100% (119/119), 117.09 KiB, done.
Resolving deltas: 100% (45/45), done.
cmake -E make_directory build && cd build && cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_PREFIX_PATH="/home/mnorouzz/torch/install/bin/.." -DCMAKE_INSTALL_PREFIX="/home/mnorouzz/torch/install/lib/luarocks/rocks/cutorch/scm-1" && make -j$(getconf _NPROCESSORS_ONLN) install
-- The C compiler identification is GNU 4.4.7
-- The CXX compiler identification is GNU 4.4.7
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found Torch7 in /home/mnorouzz/torch/install
CMake Error at /usr/share/cmake/Modules/FindCUDA.cmake:548 (message):
Specify CUDA_TOOLKIT_ROOT_DIR
Call Stack (most recent call first):
CMakeLists.txt:7 (FIND_PACKAGE)
-- Configuring incomplete, errors occurred!
See also "/tmp/luarocks_cutorch-scm-1-7917/cutorch/build/CMakeFiles/CMakeOutput.log".
Error: Build error: Failed building.
How can I fix this?
How can I set CUDA_TOOLKIT_ROOT_DIR ?
Thanks

How did you solve this problem?

By setting this in my .bashrc file:
export CUDA_BIN_PATH=/path/to/CUDA/home

thanks

I set PATH=/usr/bin:$PATH because nvcc is in /bin here, and FindCUDA strips out a /bin/ from CUDA_HOE, leaving an empty string, and then says it has not found nvcc. (Mageia Linux) Luckily /bin and /usr/bin are the same thing these days.

I set PATH=/usr/bin:$PATH because nvcc is in /bin here, and FindCUDA strips out a /bin/ from CUDA_HOE, leaving an empty string, and then says it has not found nvcc. (Mageia Linux) Luckily /bin and /usr/bin are the same thing these days.

I don't know how to find the path to CUDA...

I fixed this problem by making sure that the default folder "/usr/local/cuda" exists. Somehow my system only had "/usr/local/cuda-8.0", so I created a symbolic link: "ln -s /usr/local/cuda-8.0 /usr/local/cuda"

I agree with @liamquin . My solution is that using the following command:
export PATH=/usr/local/cuda-8.0/bin/:$PATH
Please make sure that "nvcc" works after you type this command.

authors: andymckenzie arashno fighting41love liamquin nightrome seindlut

repo: torch/cutorch


text:
Fixed sign in update rule & reconciled code with version 4 of the paper

The sign in the update rule in version 4 (3rd March) of the paper does'nt seem to work? The code works when the update to the parameters is positive not negative? To be precise, on page 2, the fifth line up from the bottom should be,
theta_t <- theta_t-1 + alpha_t . m_t / (sqrt(v_t) + epsilon )
not
theta_t <- theta_t-1 - alpha_t . m_t / (sqrt(v_t) + epsilon )
Made some cosmetic changes to reconciled the code with version 4 of the paper

It's not a mistake in the paper.
For the variational autoencoder I was using for testing, the objective function is negLL. So you do gradient ascent, not descent, so the update to the parameters should be positive, i.e. you use a negative learning rate.
I'm kind of dumb :-1:

repo: torch/optim


text:
Userbar doesn't open with mouse

I have a touchscreen laptop, which means my browser returns true for the ontouchstart check in the  userbar setup, disabling my ability to use the userbar with a mouse.

This should now be fixed since #2386 has been merged. Thanks for reporting!

authors: kaedroho seb-b

repo: torchbox/wagtail


text:
Question: Use alternative WYSIWYG editor.

Hi guys, i was looking for the WYSIWYG editor in wagtail and i saw that hallo.js hasn't updated in one year, we can think that is down. I like wagtail's WYSIWYG editor, is simple, softly, beautiful, but, he hasn't much tools, you know, than ckeditor, for example. CKEditor have much useful tools, tables for example, that hall.js hasn't but hallo.js is more beautiful than ckeditor.
I don't know if you want use ckeditor, or put many tools to hallo.js. CKeditor with wagtail's WYSIWYG editor will be great.
Also, i want as other question, i can replace wagtail's richtext with django-ckeditor's richtext?
Thank you very much.

Hi @SalahAdDin,
We don't support any alternative WYSIWYG editors, because this would require heavily customising each editor to work within Wagtail - for example, using the Wagtail image library when inserting images. We've also made a deliberate decision to keep the WYSIWYG editor simple, and discourage the use of complex, structured HTML such as tables: if you need to display table-based data, it's much better to find a way to represent it in your site's data model, where it can be properly styled and queried, instead of being buried in a blob of HTML.
We're currently working on a new approach to 'mixed' content, described here: https://github.com/torchbox/wagtail/wiki/StreamField-specification . In this approach, all of the content types that are currently allowed in WYSIWYG content (headings, paragraphs, images, video...) would be separated into individual blocks, using the most appropriate interface for editing each one. This means that (over time...) Wagtail will become less and less reliant on WYSIWYG editors.

I totally agree that the rich text editor should discourage anything complex.
However, I'd love to be able to use Medium Editor, which works beautifully and is very easy to tailor to your needs.
For example, It's very easy to add a custom button that lets you mark some text for example.
Such a rich text feature could even be enabled from RichTextBlock().

:+1:

Just in case: https://pypi.python.org/pypi/wagtailtinymce/

We don't support any alternative WYSIWYG editors, because this would require heavily customising each editor to work within Wagtail

That assumes you would implement all editors inside wagtail. I don't that was what is being suggested here at all. You would still only have one editor inside wagtail, but others could easily create add-ons for other editors (and do the integration).
I would hesitate to call anything without table (and source view) support out of the box for a CMS... Though I must admit StreamField looks promising.

We don't support any alternative WYSIWYG editors, because this would require heavily customising each editor to work within Wagtail

This comment - from nearly two years ago - is no longer true. See https://wagtail.io/blog/wagtail-1-5/, which discusses Wagtail 1.5's support for third party editors and table blocks.

authors: SalahAdDin dchaplinsky dperetti fuzzy76 gasman tomdyson


text:
update to the latest maitake and cordyceps

the currently pinned dependencies are somewhat old

Merged https://github.com/tosc-rs/mnemos-alloc/pull/9, which I think helps with this!

thanks!

authors: hawkw jamesmunns

repo: tosc-rs/mnemos


text:
🛑 MSP-Trust is down

In f3238f3, MSP-Trust (https://www.hanatrust.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-Trust is back up in 31b5fa4 after 18 minutes.

repo: touguy/uptime


text:
Fix issue to unstream milvusmixin

Signed-off-by: shiyu22 shiyu.chen@zilliz.com

/lgtm
/approve

repo: towhee-io/towhee


text:
Resnet operator for image classification task.

mainly modified files:
towhee/tests/mock_operators/pytorch_resnet_operator/pytorch_resnet_operator.py
towhee/tests/operators/test_pytorch_resnet_operator.py

/approve
/lgtm

Codecov Report

Merging #147 (eccf923) into main (b61c8d6) will increase coverage by 0.25%.
The diff coverage is 94.11%.

@@            Coverage Diff             @@
##             main     #147      +/-   ##
==========================================
+ Coverage   77.56%   77.81%   +0.25%
==========================================
  Files          88       90       +2
  Lines        3231     3282      +51
  Branches      330      331       +1
==========================================
+ Hits         2506     2554      +48
- Misses        598      600       +2
- Partials      127      128       +1

Impacted Files
Coverage Δ

...tors/test_pytorch_image_classification_operator.py
90.90% <90.90%> (ø)

..._operator/pytorch_image_classification_operator.py
96.42% <96.42%> (ø)

towhee/tests/mock_operators/__init__.py
83.33% <100.00%> (+0.98%)
: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 b61c8d6...eccf923. Read the comment docs.

authors: codecov-commenter derekdqc fzliu


text:
Does not work in xcode 7.1 Swift 2.0

The latest version does not work with Swift 2.0 and in Xcode 7.1
Thanks

Need this fixed

I worked on

repo: toygard/youtube-parser


text:
updated typical literate setup

Updated the text explaining the typical setup.

Wonderful, thanks a lot for the contribution :-)!

Pleasure :)
I still don't see the changes on the webpage though.

The changes do not appear on the page automatically – only when we release a new version.
(Which I did just yesterday, so they should be visible now.)
Thanks again!
From: Indy Garcia [mailto:notifications@github.com]
Sent: Tuesday, April 14, 2015 10:07 PM
To: tpetricek/FSharp.Formatting
Cc: Tomas Petricek
Subject: Re: [FSharp.Formatting] updated typical literate setup (#286)
Pleasure :)
I still don't see the changes on the webpage though.
—
Reply to this email directly or view it on GitHub https://github.com/tpetricek/FSharp.Formatting/pull/286#issuecomment-93061425 .  https://github.com/notifications/beacon/AAdoJdiI6ZqYhYRp-qBPaGxbCYNStAtrks5n_XjkgaJpZM4D75St.gif


text:
linux-asahi from 2023-08-25 does not build with Rust support enabled

After today's update, I am unable to build the kernel. I am running NixOS 23.05, flake input updated just a couple of minutes ago (github:nixos/nixpkgs/fc944919f743bb22379dddf18dcb72db6cff84aa).
The kernel seems to build if I disable Rust support or use unstable.
Build log:
error: builder for '/nix/store/yg8a5k5g1zn8yysi32ial27074cciq0r-linux-6.4.0-asahi.drv' failed with exit code 1:

@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/b27f62ngi8b36l60zirx9djxc237xhqp-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
applying patch /nix/store/j217pbp9pqv3z336nv6lx8fhrzdb5pmj-rust-bindgen-version.patch
patching file scripts/rust_is_available.sh
applying patch /nix/store/f3yvg9zp5lisfrfdw5szqn6v4h47nx6h-default-pagesize-16k.patch
patching file arch/arm64/Kconfig
Hunk #1 succeeded at 1197 (offset 161 lines).
applying patch /nix/store/a6jy7ivg8dljlap45ccwrx93j3bh05zb-rust-bindgen-0.63-fix.patch
patching file rust/Makefile
Hunk #1 succeeded at 321 (offset -12 lines).
applying patch /nix/store/fc3pfhi9cxzgiwdwf32w96hpl78imwis-rust-bindgen-0.65-fix.patch
patching file rust/Makefile
Hunk #1 succeeded at 301 (offset 13 lines).
applying patch /nix/store/zac8l1vmba0kzl6md10anps8ay9dn798-rust_1_71_0.patch
patching file rust/Makefile
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file rust/Makefile.rej
patching file rust/compiler_builtins.rs
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file rust/compiler_builtins.rs.rej
patching file rust/alloc/alloc.rs
Hunk #1 FAILED at 337.
1 out of 1 hunk FAILED -- saving rejects to file rust/alloc/alloc.rs.rej
patching file rust/alloc/boxed.rs
Hunk #1 FAILED at 380.
Hunk #2 FAILED at 410.
Hunk #3 FAILED at 445.
Hunk #4 FAILED at 486.
Hunk #5 FAILED at 517.
Hunk #6 FAILED at 558.
Hunk #7 FAILED at 577.
Hunk #8 FAILED at 591.
Hunk #9 FAILED at 609.
Hunk #10 FAILED at 828.
Hunk #11 FAILED at 863.
Hunk #12 FAILED at 1109.
Hunk #13 FAILED at 1121.
Hunk #14 FAILED at 1140.
Hunk #15 FAILED at 1182.
Hunk #16 FAILED at 1460.
Hunk #17 FAILED at 1898.
Hunk #18 FAILED at 1908.
18 out of 18 hunks FAILED -- saving rejects to file rust/alloc/boxed.rs.rej
patching file rust/alloc/lib.rs
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file rust/alloc/lib.rs.rej
patching file rust/alloc/vec/mod.rs
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file rust/alloc/vec/mod.rs.rej
patching file rust/kernel/allocator.rs
Hunk #1 FAILED at 26.
1 out of 1 hunk FAILED -- saving rejects to file rust/kernel/allocator.rs.rej
patching file rust/kernel/driver.rs
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file rust/kernel/driver.rs.rej

I suspect the version chosen for the Rust patch check is wrong - I attempted to skip the patch and the kernel seems to be building. I'll report later whether the compilation managed to finish.

Build was successful, running the new kernel now.

Thanks, fixed in the latest release.

authors: autrimpo tpwrules

repo: tpwrules/nixos-apple-silicon


text:
It crashed on start.

This mod keeps crashing on start bc yes. i need help.
crash report:crash-2023-03-04_19.59.59-client.txt
Log:latest.log

The mod "identity" is crashing. Might be a hard incompatibility between that mod and this mod.

ok, thanks. ill tell you if it crashes again


text:
ログイン履歴・セッションリスト提供API

ログインのログを保存し、履歴や現在有効なセッションのリストの取得、セッションの無効化をするAPIの実装

セッション管理を自前で実装できたので、後はログインのログを取って履歴を提供する

repo: traPtitech/traQ


text:
Update scala-library to 2.12.18

About this PR
📦 Updates org.scala-lang:scala-library from 2.12.16 to 2.12.18
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala-library" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:n:2

Superseded by #241.


text:
🐛 Bug Report: Downloading all versions of the same library

Which component is this bug for?
Traceloop SDK
📜 Description
For some reasons, the installation script downloads all versions of the library. Is this intended or a bug?
👟 Reproduction steps
pip install traceloop-sdk
👍 Expected behavior
It should be downloading only the required version of a library
👎 Actual Behavior with Screenshots

🤖 Python Version
3.10
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
None

@bhattbhuwan13 thanks! Does the installation succeed at the end? Can you provide the output of pip freeze on your machine?

It has been over 20 minutes, installation isn't complete yet.

@bhattbhuwan13 I suspect the issue is with some conflict in your environment, and pip trying to resolve it (that's why you see it downloading these versions - it's trying to find a version that's compatible). We don't see it with other users so I'd suggest using a clean environment with pyenv or poetry.

I used pyenv to create a virtual environment(using python 3.10) and then installed using pip

@bhattbhuwan13 just ran that on my environment. Can you share your pip freeze output?
https://github.com/user-attachments/assets/69e13e14-6cd5-4027-a30a-429e7b63a4db

Here is the requirements file:
annotated-types==0.7.0
anthropic==0.31.2
anyio==4.4.0
backoff==2.2.1
certifi==2024.7.4
charset-normalizer==3.3.2
colorama==0.4.6
Deprecated==1.2.14
distro==1.9.0
exceptiongroup==1.2.2
filelock==3.15.4
fsspec==2024.6.1
googleapis-common-protos==1.63.2
grpcio==1.65.1
h11==0.14.0
httpcore==1.0.5
httpx==0.27.0
huggingface-hub==0.24.2
idna==3.7
importlib_metadata==7.1.0
inflection==0.5.1
Jinja2==3.1.4
jiter==0.5.0
MarkupSafe==2.1.5
monotonic==1.6
opentelemetry-api==1.25.0
opentelemetry-exporter-otlp-proto-common==1.25.0
opentelemetry-exporter-otlp-proto-grpc==1.25.0
opentelemetry-exporter-otlp-proto-http==1.25.0
opentelemetry-instrumentation==0.46b0
opentelemetry-instrumentation-alephalpha==0.26.0
opentelemetry-instrumentation-anthropic==0.26.0
opentelemetry-instrumentation-bedrock==0.26.0
opentelemetry-instrumentation-chromadb==0.26.0
opentelemetry-instrumentation-cohere==0.26.0
opentelemetry-instrumentation-google-generativeai==0.26.0
opentelemetry-instrumentation-haystack==0.26.0
opentelemetry-instrumentation-langchain==0.26.0
opentelemetry-instrumentation-llamaindex==0.26.0
opentelemetry-instrumentation-marqo==0.26.0
opentelemetry-instrumentation-milvus==0.26.0
opentelemetry-instrumentation-mistralai==0.26.0
opentelemetry-instrumentation-ollama==0.26.0
opentelemetry-instrumentation-openai==0.26.0
opentelemetry-instrumentation-pinecone==0.26.0
opentelemetry-instrumentation-qdrant==0.26.0
opentelemetry-instrumentation-replicate==0.26.0
opentelemetry-instrumentation-requests==0.46b0
opentelemetry-instrumentation-sqlalchemy==0.46b0
opentelemetry-instrumentation-together==0.26.0
opentelemetry-instrumentation-transformers==0.26.0
opentelemetry-instrumentation-urllib3==0.46b0
opentelemetry-instrumentation-vertexai==0.26.0
opentelemetry-instrumentation-watsonx==0.26.0
opentelemetry-instrumentation-weaviate==0.26.0
opentelemetry-proto==1.25.0
opentelemetry-sdk==1.25.0
opentelemetry-semantic-conventions==0.46b0
opentelemetry-semantic-conventions-ai==0.3.6
opentelemetry-util-http==0.46b0
packaging==24.1
posthog==3.5.0
protobuf==4.25.4
pydantic==2.8.2
pydantic_core==2.20.1
python-dateutil==2.9.0.post0
PyYAML==6.0.1
regex==2024.7.24
requests==2.32.3
six==1.16.0
sniffio==1.3.1
tenacity==8.5.0
tiktoken==0.7.0
tokenizers==0.19.1
tqdm==4.66.4
traceloop-sdk==0.26.0
typing_extensions==4.12.2
urllib3==2.2.2
wrapt==1.16.0
zipp==3.19.2

Looks like the installation is finally done?

Haha. Yes it finished installing. Trying it out now.

Very weird that it took so long! I wonder what other package was causing this weird issue because the sdk by itself installs quickly.

It didn't take this long. It took 20-25 minutes to install. It was grpcio and one other package(forgot what it was)

Beh that's OpenTelemetry dependencies we don't really control 🫠
Did you had something like that installed before?

I hadn't installed OpenTelemetry or grpcio before

Very weird. I'll try to reproduce it some more tomorrow but have never encountered it.

Some context you might need to reproduce:
MacOS, M2 pro chip
python 3.10

ps the grpc exporter thing could be considered something we can make optional, as from a base instrumentation POV it isn't required. This also complicates alpine #1454. proto over http is less difficult to manage from a platform POV, and also as I understand universally supported.

authors: bhattbhuwan13 codefromthecrypt nirga

repo: traceloop/openllmetry


text:
"Translatable field" label not showing next to additional fields

I've created an additional TextField called Introduction on HomePage (Which extends Page, and then extends SiteTree) and added the code to make this new field translatable:
private static $translate = array(         'Introduction'     );
Everything works just fine, but in the back-end there is no green flag icon that indicates that the field is translatable:

Please follow the instructions at https://github.com/tractorcow/silverstripe-fluent/blob/master/docs/en/dataobjects.md#default-field-scaffolder and you'll have no more trouble. :)

authors: Faloude tractorcow

repo: tractorcow/silverstripe-fluent


text:
fix candlestick width at smaller bar spacing

Type of PR: bugfix / enhancement
PR checklist:

N/A Addresses an existing issue
[x] Includes tests
N/A Documentation update

Overview of change:
~Changes the calculation for the width of candlesticks at smaller bar spacing values.~
Adds a test case for the candlestick widths at smaller bar spacing values.
Decided that the existing behaviour is better for chart readability (instead of preventing slight overlapping). So the changes to the width calculation have been reverted.

~Problem:
Previously, there were cases where the candlestick width would be larger than the bar spacing therefore candlesticks could overlap. Preview of issue: https://codesandbox.io/p/sandbox/lightweight-charts-js-starter-forked-fnycf7?file=%2Fsrc%2Fmain.js%3A19%2C1
~
~Solution:
Adjusted the optimalCandlestickWidth function such that the calculated width (in bitmap pixels) should never exceed the barSpacing gap (in bitmap pixels) until the width reaches a single pixel.~
~Plot of the new function results: https://jsfiddle.net/msilverwood/jx0zLo6f/~
Blue - candle width (pixels)
Red - bar spacing (pixels)
Green - bar spacing (media size)

Change not required.

repo: tradingview/lightweight-charts


text:
Add explanation

I miss the bit where test test must be in the same package, while normally it would go in a package_test (to emulate outside usage)

Hello,
With PR #11, the mock can be exported.

authors: ldez marcelloh

repo: traefik/mocktail


text:
PathPrefix RegEx

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
Dear Dev Team -
I have been working on condensing my IngressRoute "routers," so they are nice and neat when developing my React application. Issue In Community
To start, as many people know, or don't, react runs on the premise of everything runs off the / path and the react-router does the matching itself of the path in the URL to get to the page. In my app, I use vite, react, react-router, and graphql for a feature set talking to a NodeJS microservice. So for example, in my app:
/
/list
/queue
/pirnt/[:ID]
/print/list
/assets/[*.js]
/locale/en_US/[*.json]
/locale/en/[*.json]

The "URLs" or pages are:
/
/list
/queue
/pirnt/[:ID]
/print/list

and
/assets/[*.js]
/locale/en_US/[*.json]
/locale/en/[*.json]

Hold the "static" content.
In the App design, the frontend is its docker image hosting everything. The static and the dyanmic. It's not two different services. Someone suggested I create a service just to hold the static stuff. I wonder why someone would do this. Below is my Kube YAML for the IngressRoutes:
Note 1: I removed the ports, TLS info, and metadata from the YAML below for ease of clarity.
Note 2: "frontend" is where Nginx runs the html, js, and static. "controller" is the graphql service that federates all the other graphql gateways.
apiVersion: traefik.io/v1alpha1
kind: IngressRoute
# Removed for cleaner stuff
spec:
  entryPoints:
    - websecure
  routes:
    - kind: Rule
      match: Host(`{{ .Values.frontend.fqdn }}`) && PathPrefix(`/{path:((assets.*|locales.*))}`) || PathPrefix(`/`)
      services:
        - kind: Service
          name: frontend
    - kind: Rule
      match: Host(`{{ .Values.frontend.fqdn }}`) && !PathPrefix(`/{path:((assets.*|locales.*))}`) && !PathPrefix(`/`)
      middlewares:
        - name: middleware-frontend-replacement-path
      services:
        - kind: Service
          name: frontend

---
apiVersion: traefik.io/v1alpha1
kind: IngressRoute
# Removed for cleaner stuff
spec:
  entryPoints:
    - websecure
  routes:
    - kind: Rule
      match: Host(`{{ .Values.frontend.fqdn }}`) && Header(`X-Graphql`, `true`) && PathPrefix(`/graphql`)
      services:
        - kind: Service
          name: controller # This is the graphql
      middlewares:
        - name: middleware-controller-replacement-path
---
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: middleware-frontend-replacement-path
spec:
  replacePath:
    path: /
---
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: middleware-controller-replacement-path
spec:
  replacePath:
    path: /graphql

So, the regex in the top YAML for the frontend server, I have tested in several regex editor sites it does match all of these:
/
/assets/[*.js]
/locale/en_US/[*.json]
/locale/en/[*.json]

... paths correctly. The reason why / should be included is that this path does not need any middleware to replace anything.
In the second one, I have ! before PatchPrefix and it should "not" the search for everything else. This is because GoLang Regex does not have a negative match operator. (Why not? Idk.)
In the 3rd route, I have the same FQDN and the graphql endpoint plus the HTTP header, which is passed on by the client, so that the rule gets hit. And it does work. I had to add /graphql to the middleware because the service runs the graphql on the /graphql path and not the root of the path.
I am welcome to be proved wrong, but again, all my testing shows that Treafik shows it as valid input, but it doesn't seem to work correctly. I welcome being pointed to where this code is, and I can try to fix it myself if it is a bug. If it's a feature, I can work on it with my limited GoLang knowledge that I have been able to understand. (I am still learning.)
Thanks
What did you see instead?
So this is what I am trying to achieve, but I am getting one working, not the other.
For instance, a user http://FQDN/ loads up all the pages, js files, etc. with no issue, including talking to the graphql endpoint. Depending on what setting I change to get this to work, I can make it so that https;//FQDN/list does not 404, or is missing from the react logic, but it can't load the assets or js files in https://FQDN/assents/some_js_file_here.js  come up as not being able to be found. I looked at the ngnix logs and it seems not even to get there.
I tried 50 combos, so this has to be a bug in PathPrefix RegEx. I know this would it work if ifI put all possible paths like:

PathPrefix(/list) PAthPrefix(/queue) PAthPrefix(/print/{path:(.*)}) PAthPrefix(/print)

... in for every endpoint, but this could take a long time for a more elegant application.
What version of Traefik are you using?
3.0.0 RC1
What is your environment & configuration?
additionalArguments:
- --serversTransport.insecureSkipVerify=true
- --log.level=DEBUG
additionalVolumeMounts: []
affinity: {}
autoscaling:
  enabled: false
certResolvers: {}
commonLabels: {}
deployment:
  additionalContainers: []
  additionalVolumes: []
  annotations: {}
  dnsConfig: {}
  enabled: true
  imagePullSecrets: []
  initContainers: []
  kind: Deployment
  labels: {}
  lifecycle: {}
  minReadySeconds: 0
  podAnnotations: {}
  podLabels: {}
  replicas: 1
  shareProcessNamespace: false
  terminationGracePeriodSeconds: 60
env:
- name: POD_NAME
  valueFrom:
    fieldRef:
      fieldPath: metadata.name
- name: POD_NAMESPACE
  valueFrom:
    fieldRef:
      fieldPath: metadata.namespace
envFrom: []
experimental:
  kubernetesGateway:
    enabled: false
  plugins: {}
extraObjects: []
globalArguments:
- --global.sendanonymoususage=false
- --global.checknewversion=false
hostNetwork: false
image:
  pullPolicy: IfNotPresent
  registry: docker.io
  repository: traefik
  tag: v3.0.0-rc1
ingressClass:
  enabled: true
  isDefaultClass: true
ingressRoute:
  dashboard:
    annotations: {}
    enabled: false
    entryPoints:
    - traefik
    labels: {}
    matchRule: PathPrefix(`/dashboard`) || PathPrefix(`/api`)
    middlewares: []
    tls: {}
  healthcheck:
    annotations: {}
    enabled: false
    entryPoints:
    - traefik
    labels: {}
    matchRule: PathPrefix(`/ping`)
    middlewares: []
    tls: {}
livenessProbe:
  failureThreshold: 3
  initialDelaySeconds: 2
  periodSeconds: 10
  successThreshold: 1
  timeoutSeconds: 2
logs:
  access:
    enabled: false
    fields:
      general:
        defaultmode: keep
        names: {}
      headers:
        defaultmode: drop
        names: {}
    filters: {}
  general:
    level: DEBUG
metrics:
  prometheus:
    entryPoint: metrics
nodeSelector: {}
persistence:
  accessMode: ReadWriteOnce
  annotations: {}
  enabled: false
  name: data
  path: /data
  size: 128Mi
podDisruptionBudget:
  enabled: false
podSecurityContext:
  fsGroupChangePolicy: OnRootMismatch
  runAsGroup: 65532
  runAsNonRoot: true
  runAsUser: 65532
podSecurityPolicy:
  enabled: false
ports:
  metrics:
    expose: false
    exposeInternal: false
    exposedPort: 9100
    port: 9100
    protocol: TCP
  traefik:
    expose: false
    exposeInternal: false
    exposedPort: 9000
    port: 9000
    protocol: TCP
  web:
    expose: true
    exposeInternal: false
    exposedPort: 80
    port: 8000
    protocol: TCP
    redirectTo:
      port: websecure
      priority: 10
  websecure:
    expose: true
    exposeInternal: false
    exposedPort: 443
    http3:
      enabled: false
    middlewares: []
    port: 8443
    protocol: TCP
    tls:
      certResolver: ""
      domains: []
      enabled: true
      options: ""
priorityClassName: ""
providers:
  file:
    content: ""
    enabled: false
    watch: true
  kubernetesCRD:
    allowCrossNamespace: false
    allowEmptyServices: false
    allowExternalNameServices: true
    enabled: true
    ingressClass: traefik-external
    namespaces: []
  kubernetesIngress:
    allowEmptyServices: false
    allowExternalNameServices: false
    enabled: true
    namespaces: []
    publishedService:
      enabled: false
rbac:
  enabled: true
  namespaced: false
readinessProbe:
  failureThreshold: 1
  initialDelaySeconds: 2
  periodSeconds: 10
  successThreshold: 1
  timeoutSeconds: 2
resources: {}
securityContext:
  allowPrivilegeEscalation: false
  capabilities:
    drop:
    - ALL
  readOnlyRootFilesystem: true
service:
  annotations: {}
  annotationsTCP: {}
  annotationsUDP: {}
  enabled: true
  externalIPs: []
  labels: {}
  loadBalancerIP: 172.22.0.2
  loadBalancerSourceRanges: []
  single: true
  spec: {}
  type: LoadBalancer
serviceAccount:
  name: ""
serviceAccountAnnotations: {}
tlsOptions: {}
tlsStore: {}
tolerations: []
topologySpreadConstraints: []
tracing: {}
updateStrategy:
  rollingUpdate:
    maxSurge: 1
    maxUnavailable: 0
  type: RollingUpdate
volumes: []

Add more configuration information here.
If applicable, please paste the log output in DEBUG level
No response

Hi @Bugs5382,
Thanks for your interest in Traefik!
PathPrefix doesn't support regexp in v3, you have to use PathRegexp to use regexp now (https://doc.traefik.io/traefik/v3.0/routing/routers/#path-pathprefix-and-pathregexp).
Here's how I rewrote your IngressRoute for my test (I focused exclusively on the frontend part on my tests and used two different whoami to see if the routing seems correct):
---
apiVersion: traefik.io/v1alpha1
kind: IngressRoute
metadata:
  name: web
  namespace: default
spec:
  entryPoints:
    - websecure
  routes:
    - kind: Rule
      match: Host(`toto.localhost`) && (PathRegexp(`^/((assets.*|locales.*))`) || Path(`/`))
      services:
        - kind: Service
          name: whoami1
          port: 80
    - kind: Rule
      match: Host(`toto.localhost`) && (!PathRegexp(`^/((assets.*|locales.*))`) && !Path(`/`))
      middlewares:
        - name: middleware-frontend-replacement-path
      services:
        - kind: Service
          name: whoami2
          port: 80

---
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: middleware-frontend-replacement-path
spec:
  replacePath:
    path: /

I replaced the PathPrefix by PathRegexp, and changed the PathPrefix('/') by a strict Path('/') because the it would match everything so it sounded weird (but maybe I'm wrong here).
Details

❯ curl -k https://toto.localhost:8443
Hostname: whoami1-7b6f7cbc7f-jw8zx
IP: 127.0.0.1
IP: ::1
IP: 10.42.0.13
IP: fe80::c848:baff:fe52:9201
RemoteAddr: 10.42.0.12:48320
GET / HTTP/1.1
Host: toto.localhost:8443
User-Agent: curl/8.4.0
Accept: */*
Accept-Encoding: gzip
X-Forwarded-For: 127.0.0.1
X-Forwarded-Host: toto.localhost:8443
X-Forwarded-Port: 8443
X-Forwarded-Proto: https
X-Forwarded-Server: traefik-564cdb4977-4sz4h
X-Real-Ip: 127.0.0.1

❯ curl -k https://toto.localhost:8443/assets/test.js
Hostname: whoami1-7b6f7cbc7f-jw8zx
IP: 127.0.0.1
IP: ::1
IP: 10.42.0.13
IP: fe80::c848:baff:fe52:9201
RemoteAddr: 10.42.0.12:48320
GET /assets/test.js HTTP/1.1
Host: toto.localhost:8443
User-Agent: curl/8.4.0
Accept: */*
Accept-Encoding: gzip
X-Forwarded-For: 127.0.0.1
X-Forwarded-Host: toto.localhost:8443
X-Forwarded-Port: 8443
X-Forwarded-Proto: https
X-Forwarded-Server: traefik-564cdb4977-4sz4h
X-Real-Ip: 127.0.0.1

❯ curl -k https://toto.localhost:8443/locales/test.js
Hostname: whoami1-7b6f7cbc7f-jw8zx
IP: 127.0.0.1
IP: ::1
IP: 10.42.0.13
IP: fe80::c848:baff:fe52:9201
RemoteAddr: 10.42.0.12:48320
GET /locales/test.js HTTP/1.1
Host: toto.localhost:8443
User-Agent: curl/8.4.0
Accept: */*
Accept-Encoding: gzip
X-Forwarded-For: 127.0.0.1
X-Forwarded-Host: toto.localhost:8443
X-Forwarded-Port: 8443
X-Forwarded-Proto: https
X-Forwarded-Server: traefik-564cdb4977-4sz4h
X-Real-Ip: 127.0.0.1

❯ curl -k https://toto.localhost:8443/list
Hostname: whoami2-5f74765f4-cxhrn
IP: 127.0.0.1
IP: ::1
IP: 10.42.0.14
IP: fe80::9460:5bff:fe70:f36f
RemoteAddr: 10.42.0.12:53922
GET / HTTP/1.1
Host: toto.localhost:8443
User-Agent: curl/8.4.0
Accept: */*
Accept-Encoding: gzip
X-Forwarded-For: 127.0.0.1
X-Forwarded-Host: toto.localhost:8443
X-Forwarded-Port: 8443
X-Forwarded-Proto: https
X-Forwarded-Server: traefik-564cdb4977-4sz4h
X-Real-Ip: 127.0.0.1
X-Replaced-Path: /list

It seems to work nicely with this configuration.
If you have any other issues with the rules, don't hesitate to check the migration guide.
If this works for you, I will close the issue.

@youkoulayley Just waking up for the day. I totally looked around to see if there was a new "matcher".  Once I am in the office I will give it a try. :)

@youkoulayley  Didn't get a chance before you closed, yes. That worked.

repo: traefik/traefik


text:
Fixed issue with logger being called on validate

This is the error I fixed:
debug: trailpack: validating footprints
TypeError: Cannot read property 'warn' of undefined
    at FootprintsTrailpack.validate (/Users/Matteo/Developer/projects/Yeeti/Hamsa/hamsa-api-server/node_modules/trailpack-footprints/index.js:23:19)
    at app.after.then.then (/Users/Matteo/Developer/projects/Yeeti/Hamsa/hamsa-api-server/node_modules/trails/lib/Core.js:188:24)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)
    at Function.Module.runMain (module.js:703:11)
    at startup (bootstrap_node.js:190:16)
    at bootstrap_node.js:662:3
(node:30120) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'warn' of undefined
    at FootprintsTrailpack.validate (/Users/Matteo/Developer/projects/Yeeti/Hamsa/hamsa-api-server/node_modules/trailpack-footprints/index.js:23:19)
    at app.after.then.then (/Users/Matteo/Developer/projects/Yeeti/Hamsa/hamsa-api-server/node_modules/trails/lib/Core.js:188:24)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)
    at Function.Module.runMain (module.js:703:11)
    at startup (bootstrap_node.js:190:16)
    at bootstrap_node.js:662:3

@tjwebb let me know if this fix can be released 👍

repo: trailsjs/trailpack-footprints


text:
debug the pom.xml on windows

running mvn clean install doesn't work.  Find the root cause and fix all errors (hopefully also makes it compatible with visual studios code).

The pom.xml worked with Intellij on windows but doesn't seem to configure eclipse or VS code properly.

VSCode now supports the pom as they've added build helper support for older versions, but, debugging seems to fail. Investigation continues.

repo: trakerr-io/trakerr-java


text:
Added form name

Should solve #5

Thank you for your commit!

No problem, I love the theme!

authors: tranduyhung wolframite

repo: tranduyhung/grav-theme-x-corporation


text:
MB-16579 - Add selective dependency resolution for semver

The purpose of this resolution is to address a dependabot security alert https://github.com/transcom/mymove/security/dependabot/107
Jira ticket
Summary
Is there anything you would like reviewers to give additional scrutiny?
this article explains more about the approach used.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.
Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the
Login as a

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots

Messages

:book:
:link: MB-16579

  Generated by :no_entry_sign: dangerJS against 06ac38c00d38a92471e01ad3f932be1beff12846

authors: michaelvaldes-truss robot-mymove

repo: transcom/mymove


text:
Ak mb 3158 frontend for hhg move setup

Description
This creates the UI for the HHG setup form in which data can be entered.  Creates an AddressField, ContactField, and HHGDetailsForm component, each with a storybook version and client tests.
It does not include styling and a couple subtitles, so does not match the wireframe to the T.
Reviewer Notes
This story is a blocker for other stories, so if there are any visual change request that are more than minimal, that could be put in a different PR so that at least the form is available for the blocked story.
The linter was complaining about using the same name as the default export of HHGDetailsForm in the HHGMoveSetup page, so We are importing as HHGDetailsFormComponent, but wondered if there was a way not to have to change the name?
Setup
run storybook:
make storybook
Check out:
Component --> HHGDetailsForm
Component --> AddressFields
Component --> ContactInfoFields
locally, run the client and server. Log in as a service member with a move.
Navigate to moves/[moveId]/hhg-start and try out the form
Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 7b9dadae4fd272817625bd5cdea27f6fa6937ed0

I can't seem to get the same lint error when I rename HHGDetailsFormComponent to HHGDetailsForm. There should be nothing wrong with importing the same name as the default

I can't seem to get the same lint error when I rename HHGDetailsFormComponent to HHGDetailsForm. There should be nothing wrong with importing the same name as the default

I checked, and it wasn't a lint error, but the UI was erroring (failed to compile)

Moot point if we combine route page with the form component, but baffling. . .

I can't seem to get the same lint error when I rename HHGDetailsFormComponent to HHGDetailsForm. There should be nothing wrong with importing the same name as the default

I checked, and it wasn't a lint error, but the UI was erroring (failed to compile)

Moot point if we combine route page with the form component, but baffling. . .

I am also not seeing this lint error, but I can provide some background here since this is a subtle but pretty important lint rule. When you import the default export from a module (i.e., import MyForm from './MyForm'), there is nothing to enforce what you call it, as you're essentially assigning it a name when you import it. So you could just as soon do import NonsenseWhatever from './MyForm' and it would be the same thing.
However for named exports, you have to import by the name it is exported by (i.e., import { MyForm } from './MyForm'). Default exports don't have a name (hence why you have to give them one when you import them). So this rule is to guard against a scenario where if you have a module with both a default export and named exports...
export class MyForm { ...

export default MyForm

...it will not allow you to name the default export the same as one of the named exports...
// this would cause a lint error, because there's a potential naming conflict between the default export & the MyName export
import MyForm from './MyForm

It ensures that you could theoretically always import all exports from a given file, without naming conflicts. I also think it provides value in keeping it clear what you're importing (since if you did import a default and give it the same name as something else, it might be confusing which one you mean).
A common pattern is to export a component with HOCs (such as connecting to Redux) as the default export, and also export the component on its own as a named export (such as for testing purposes if you want to test the component in isolation):
export class MyComponent { ... }

export default connect(MyComponent)

In this case I find it helpful to be descriptive when importing the default, and call it something like ConnectedMyComponent so that it is clear I am importing the component + its connectors.

I can't seem to get the same lint error when I rename HHGDetailsFormComponent to HHGDetailsForm. There should be nothing wrong with importing the same name as the default

I checked, and it wasn't a lint error, but the UI was erroring (failed to compile)

Moot point if we combine route page with the form component, but baffling. . .

I am also not seeing this lint error, but I can provide some background here since this is a subtle but pretty important lint rule. When you import the default export from a module (i.e., import MyForm from './MyForm'), there is nothing to enforce what you call it, as you're essentially assigning it a name when you import it. So you could just as soon do import NonsenseWhatever from './MyForm' and it would be the same thing.
However for named exports, you have to import by the name it is exported by (i.e., import { MyForm } from './MyForm'). Default exports don't have a name (hence why you have to give them one when you import them). So this rule is to guard against a scenario where if you have a module with both a default export and named exports...
export class MyForm { ...

export default MyForm

...it will not allow you to name the default export the same as one of the named exports...
// this would cause a lint error, because there's a potential naming conflict between the default export & the MyName export
import MyForm from './MyForm

It ensures that you could theoretically always import all exports from a given file, without naming conflicts. I also think it provides value in keeping it clear what you're importing (since if you did import a default and give it the same name as something else, it might be confusing which one you mean).
A common pattern is to export a component with HOCs (such as connecting to Redux) as the default export, and also export the component on its own as a named export (such as for testing purposes if you want to test the component in isolation):
export class MyComponent { ... }

export default connect(MyComponent)

In this case I find it helpful to be descriptive when importing the default, and call it something like ConnectedMyComponent so that it is clear I am importing the component + its connectors.

This is really helpful and makes sense.  Thanks for the explanation!

This is looking really good! making separate components for the address & contact info fieldsets is a great idea :D One thing that's left to fully hook the form inputs up with Formik is to pass in the Formik values and onChange handler to all inputs. Then Formik will become aware of all of the input values and keep them in sync at the form level. If you do this, then for example you wouldn't actually need the hasDeliveryAddress state at all anymore because you can look at values['has-delivery-address'] instead.
Formik provides a few different ways to do this, but probably the easiest one to do based on what you have already is to wrap all of its children like so (full docs at https://formik.org/docs/api/formik#children-reactreactnode--props-formikpropsvalues--reactnode):
<Formik initialValues={initialValues}>
{({ handleChange, values, ... }) => (
  <WizardPage ...>
  // everything else in the form...
  </WizardPage>
)}
</Formik>

then you have access to values, handleChange (and any other Formik context props or methods you need) inside the form itself. Each input will need to get onChange={handleChange} added, as well as value={values.<input name>}. Then the inputs will become "controlled" by Formik, and it'll become easier to add branches and validation later on. let me know if you have any questions and I would be happy to help and/or pair on this!
A few other minor things:

I would make all input name values camelCase so it's easier to access them in JS. The name attributes should all match the keys in the form data model, so perhaps using the shape you created for props.initialValues would make sense here.
For input id values, it is usually a best practice to use a uuid generator. The requirements of an input id attribute are they have to match their label for attribute, and they have to be unique. Since they're hardcoded right now, there's more than one element with the same idea for example in the repeated Address & ContactInfo fieldsets. Usually I like to create an input ID using the name and a random uuid, so for example mailingAddress1_a1b2c3

@suzubara Kim and I believe we've made these requested changes
@Ronolibert please let us know if there's anything else you'd like us to do

authors: Ronolibert SirenaBorracha kimallen robot-mymove suzubara


text:
[MB-11565] Use swagger 0.29.0 for code generation

Jira ticket for this change
Summary
This PR updates our Docker references to use an image that has go-swagger 0.29.0 (the latest version).  In turn, I have run make server_generate using it; this PR includes any changes to the generated files.  Part of the reason to get on the latest version is to make it easier to install and run the swagger utility locally to avoid long execution times using Docker on Apple Silicon machines.
Note that there are two commits -- the first updates all the hashes and references to go-swagger 0.29.0.  The second contains all the generated files that changed.
Although xx generated files changed, there appear to be only two template changes that affected us:

TBD
TBD

See the go-swagger 0.29.0 release notes for more details.
Here is the corresponding PR in the circleci-docker repository: https://github.com/transcom/circleci-docker/pull/209.  I am currently referencing hashes from that branch, but will update this PR with the merged hash after this PR has gone through some initial vetting.
Setup to Run Your Code
Make sure that all tests still pass.  Exercise the app a bit and make sure nothing strange seems to be happening.
Run a make server_generate and see that everything still works and that there are no local changes after regenerating.
Verification Steps for Author
These are to be checked by the author.

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Messages

:book:
:link: MB-11565

  Generated by :no_entry_sign: dangerJS against 2f5ae682412d5c1c26269bb5a0b8422d28775f21

authors: reggieriser robot-mymove


text:
Getting info about resources causes "unsupported protocol scheme" error

Hello and thanks for the nice tool! I cloned the repository locally and I either push or pull resources I get error unsupported protocol scheme "" I also tried two earlier versions of the tool and the same thing happens.
I built the tool locally according to the guide with make docker-build.

I ran tx migrate and the error went away. Closing this one.

repo: transifex/cli


text:
Adding the project logo

Adding th project logo and icon
fixes transitive-bullshit/chatgpt-api#353

Perfect fit @transitive-bullshit

This project is undergoing a major revamp; closing out old PRs as part of the prep process.

authors: gucr transitive-bullshit yuan442177

repo: transitive-bullshit/chatgpt-api


text:
perf: github plugin that shows bundle size diff on every PR

self explanatory from title — would be nice to have exact numbers/percentages on how much each PR and the deps they add contribute to bundle size to avoid bloating the app

one option: https://github.com/sarthak-saxena/JSBundleSize (doesn't show diff tho)

https://github.com/marketplace/actions/bundle-size-diff?

https://github.com/marketplace/actions/bundle-size-diff?

oo nice this looks great, @h0tw4t3r wanna PR it in?

https://github.com/marketplace/actions/bundle-size-diff?

oo nice this looks great, @h0tw4t3r wanna PR it in?

yeah, lemme take that.
eta 24h

@transmissions11, I've spent some time with implementing this, bundle-size-diff is not our choice since it's for webpack, and here we use rollup.
I've generated the bundle stats files with rollup-plugin-visualizer, but the format is different and bundle-size-diff can't eat it.
Which brings us back to the search of an action that builds a diff based on rollup-plugin-visualizer plugin.


text:
Copy files for balancing but remove source only after checksum of cop…

…ied file matches source

Makes things slower but helps me sleep at night. Maybe out of scope for tool as could be argued responsibility for file integrity lies with file system, just close if no interest.

If I were to accept a change to support this it'd need to be optional and cleaned up. Shouldn't be using && like that and instead properly call subprocess call for each and compare exit codes.

authors: pessimal trapexit

repo: trapexit/mergerfs-tools

license: isc


text:
🛑 TechinAsia_WordPress_API is down

In 303c0dd, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 171 ms

Resolved: TechinAsia_WordPress_API is back up in 34a9f1d after 7 minutes.

repo: traqy/upptime


text:
🛑 TechinAsia_Saigon is down

In ff55e48, TechinAsia_Saigon (https://saigon.techinasia.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TechinAsia_Saigon is back up in 3b79672 after 16 minutes.


text:
🛑 TechinAsia is down

In bae8e89, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 755 ms

Resolved: TechinAsia is back up in 6fa1e14 after 14 minutes.


text:
🛑 TechinAsia_Laravel_API is down

In 93eb967, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 172 ms

Resolved: TechinAsia_Laravel_API is back up in 8873bb6 after 7 minutes.


text:
🛑 TechinAsia_Laravel_API is down

In 423a341, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 222 ms

Resolved: TechinAsia_Laravel_API is back up in 24dad46 after 7 minutes.


text:
🛑 TechinAsia is down

In 9141386, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 924 ms

Resolved: TechinAsia is back up in 2354817 after 25 minutes.


text:
Ping

Create IMAP folder.

Again!

repo: trasherdk/svelte-gantt


text:
[FIX] add bundle analyzer default config

previously if BUNDLE_ANALYZE=both yarn build is executed it doesn't create analyzer report page because missing config
this pull request add the missing config

Coverage remained the same at 100.0% when pulling c354305dd10f01fed2120f5d37b615fef62af8f1 on khaeransori:fix/bundle-analyzer-config into fd15320206d4c4fd624cd5cb527786ed72f97bd1 on traveloka:master.

Fixed in 30b0d1c

authors: coveralls khaeransori sayuti-daniel

repo: traveloka/soya-next


text:
calendarConfig：{ defaultDay: false,}

this.calendar.setCalendarConfig({
defaultDay: this.data.peakOrderInfo.startDate,
});
默认不选择时间，然后页面加载完成设置默认时间，点选择日历，日历打开并没有选中我设置的时间是怎么回事。

这里文档没补全，setCalendarConfig 只会对部分配置生效，defaultDay 是日历初始化的时候读取的，需要日历加载完成跳转至某天，可调用  'jump'

authors: WchHxl treadpit


text:
UI view for import

Part of https://github.com/treeverse/lakeFS/issues/3137
Implement a new UI view described in #3137

Done.

repo: treeverse/lakeFS


text:
Use If-None-Match in LakeFSLinker

Closes #7488
Change Description
Background
Allow creating Data/Output/InputStream with conditional overwrite on the last stage of creating the lakeFS entry by supporting the If-None-Match in the LakeFSLinker
Testing Details
Should be covered by the Hadoop contractual testing
Breaking Change?
No

Thanks!
Aside from the comment, I'm not sure how catalogs will be able to consume this method. It's not accessible via any FileSystem method.

Catalogs consume this method via the TableMetadataParser.write and the FIleIO implementation. as part of the write method we invoke either a create method or a createOrOverwrite method which produces a FSDataOutputStream with the overwrite param set accordingly


text:
feat: allowed disabled state to SelectItem, SearchSelectItem, MulitSelectItem

feat/allowed disabled state to , ,  issue #853

Description

feat/allowed disabled state to , ,
Related issue(s)
#853

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

[] Bug fix (non-breaking change which fixes an issue)
[✓  ] New Feature (non-breaking change which adds functionality)
[ ] New Feature (BREAKING CHANGE which adds functionality)
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

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

[ ] Yes
[ ✓ ] No

If yes, please describe the impact and migration path for existing applications:
How has This been tested?

Screenshots (if appropriate):
The PR fulfills these requirements:

[ ✓ ] It's submitted to the main branch
[✓  ] When resolving a specific issue, it's referenced in the related issue section above
[✓  ] My change requires a change to the documentation. (Managed by Tremor Team)
[ ] I have added tests to cover my changes
[✓  ] Check the "Allow edits from maintainers" option while creating your PR.
[✓  ] Add refs #XXX or fixes #XXX to the related issue section if your PR refers to or fixes an issue.
[✓  ] By contributing to Tremor, you confirm that you have read and agreed to Tremor's CONTRIBUTING.md guideline. You also agree that your contributions will be licensed under the Apache License 2.0 license.

Hi! Thank you for taking your time and creating this PR. As mentioned in https://github.com/tremorlabs/tremor/issues/853#issuecomment-2034720621 this won't be added to the selects.

repo: tremorlabs/tremor


text:
Update ms.tex

typos

Thanks, John!

authors: john-livingston trevordavid

repo: trevordavid/rossby-ridge


text:
Final Pull Request

Extra Credit

Worked with @jp1478 and @02NRA


text:
Entries have hidden hard limit separate from returned results

When using either scraping.tweets or scraping.media, the debug printer shows that there are hundreds or sometimes thousands of unique results when searching through with the cursor yet when it puts these results into the list for the entries it caps out at either 102 or 101 entries.

In the above screenshot, I am running the scraping.media function with debug=1 enabled.
As the cursor goes through the account it finds ~700 unique results (which lines up with the ~700 images/videos this user has uploaded) and stops there.
The 101 at the bottom is the number of actual entries the function fetches which is nowhere near the ~700 purported.
This number was obtained by this method:
user_media = scraping.media([twitter_id_string])
print(len(user_media[0]['data']['user']['result']['timeline_v2']['timeline']['instructions'][0]['entries']))

Why is the number of entries in this list incongruous with the results that the API reports when scrolling through the user's feed?
Is there a separate way I should be gathering those entries that gets everything?
Any info would be appreciated.

user_media[0] is only indexing into the first batch.
Each endpoint has a limit to the number of results it can return, usually between ~20 and ~100.
Following your method, to get all media you would do:

[y for x in user_media for y in x['data']['user']['result']['timeline_v2']['timeline']['instructions'][0]['entries']]

or simply:
from twitter.util import find_key
import pandas as pd

df = pd.DataFrame(y for x in find_key(user_media, 'entries') for y in x)
df

authors: Survivian trevorhobenshield

repo: trevorhobenshield/twitter-api-client


text:
Trickster v2.0.0-beta2 : Prometheus query_range calls resulting in proxy-only sometimes instead of cache hit

We are trying to upgrade from Trickster v1.1 to v2.0.0-beta2 and facing the following issue. Hit rate has decreased and some of the calls are now being served as proxy-only. More details in logs below.
The same suite which used to give 100% hit rate in v1.1 is giving lesser hit rate in v.2.0 beta version.
Test setup :
Trickster is deployed in our K8s cluster and we tried running the test suite with different number of pod replicas and here are our findings. We are making 10 queries/sec. Test is run continuously for ~10 mins. Same query (test_metrics) which is already present in TSDB is made every time.
Backend used is Prometheus and config is such that recent 5 mins data is not cached, anything older than till 3 weeks is cached.

Fixed time range means test_metrics is queried for same fixed time range every time REST call is made ie. start & end query params is fixed for all calls.
Variable time range uses a dynamic time range ie. end as the currentTime and start as currentTime - 900 secs (15 mins ago) for each API call this should result in partial hit (phit) for Trickster.
Fixed time range means test_metrics is queried for same fixed time range every time REST call is made ie. start & end query params is fixed for all calls.
Variable time range uses a dynamic time range ie. end as the currentTime and start as currentTime - 900 secs (15 mins ago) for each API call this should result in partial hit (phit) for Trickster.

Panel Queries :
Hit Rate : sum(rate(trickster_proxy_requests_total{path=~"/api/.*", cache_status=~"hit|phit|nchit|rhit", job="m3-query-pod-name"}[2m])) /  sum(rate(trickster_proxy_requests_total{path=~"/api/.*", job="m3-query-pod-name"}[2m]))
Proxy Only Rate : sum(rate(trickster_proxy_requests_total{path=~"/api/.*", cache_status=~".*proxy.*", job="m3-query-pod-name"}[2m])) /  sum(rate(trickster_proxy_requests_total{path=~"/api/.*", job="m3-query-pod-name"}[2m]))
Trickster Configuration :
---
trickster-conf:
  backends:
    default:
      max_ttl_ms: 1814400000
      origin_url: "http://127.0.0.1:8500"
      provider: prometheus
      timeseries_retention_factor: 4096
      timeseries_ttl_ms: 1814400000
  caches:
    default:
      index:
        max_size_bytes: 5120000000
      provider: filesystem
  frontend:
    listen_port: 8480
  metrics:
    listen_port: 8481

Test suite logs with trickster response headers :
16:31:41.239 [DEBUG] i.g.h.e.t.HttpTxExecutor - Sending request=query uri=http://prometheus-url/api/v1/query_range?query=test_metrics&start=1640946196&end=1640947096&step=30s: scenario=Query, userId=5029
16:31:41.254 [DEBUG] i.g.h.c.i.HttpAppHandler - Read msg='DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
access-control-allow-origin: *
cache-control: s-maxage=1814400
content-type: application/json; charset=UTF-8
**x-trickster-result: engine=DeltaProxyCache; status=hit; ffstatus=off**
date: Fri, 31 Dec 2021 11:01:41 GMT
x-envoy-upstream-service-time: 1
transfer-encoding: chunked'

16:31:41.338 [DEBUG] i.g.h.e.t.HttpTxExecutor - Sending request=query uri=http://prometheus-url/api/v1/query_range?query=test_metrics&start=1640946196&end=1640947096&step=30s: scenario=Query, userId=5030
16:31:41.415 [DEBUG] i.g.h.c.i.HttpAppHandler - Read msg='DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
access-control-allow-origin: *
content-type: application/json
date: Fri, 31 Dec 2021 11:01:41 GMT
**x-trickster-result: engine=HTTPProxy; status=proxy-only**
x-envoy-upstream-service-time: 92
transfer-encoding: chunked'

Please let me know if their is something wrong/missing in config which is leading to some queries getting served as proxy-only instead of cache hit.

We have found that in trickster-v2, the reason for decreased hit rate and calls being served as proxy-only is because, all the pods don't use cache. It is also found that request it tracks is: /api/v1 instead of /api/v1/query_range.
Due to incorrect request tracking, the handler for /api/v1 used is Proxy-handler instead of  Query-range handler.
Can you please let us know if this could be related to: https://github.com/trickstercache/trickster/pull/672/files where the paths is not being copied.

It is found that following is the cause of this issue:
When the default backend routes are registered, currently it is as per unordered map. This means that the routes can have "\" or "\api\v1\" before "api\v1\query_range". When the router matches the regex expression with the routes map, if partial routes appears first that will be considered as a match, which causes request to be "Proxy-Only".
Thus, with sorting we will ensure that routes will be a sorted array in the descending order of path lengths, meaning: "\api\v1\query_range" would appear before "api\v1" and "\" so that we have appropriate match.

Will raise a PR for the same. Please reach out in case any issues. Thanks!

repo: trickstercache/trickster


text:
define things from Senritsu "Unidentified" folder

Most of the images are coming off as a part of the Unidentified folder, likely due to not considering characters take place exclusively in this game like sprites for Major Isabella Fitzgerald (iza), Marion Garland (mro), and Ramon Noboa (nob). There are also some BGs with the prefix bgt which are backgrounds not placed in the background folder. The CGs are given the prefix evt, which are also placed in Unidentified. You can have them in a Story/CG directory like you do for Afterglow (Zankou).

Just for clarification, all names listed are First Last name, correct? I want to keep consistency with the sorting.

Yes. The names of the characters are American in the game, and so the names are in first-last notation.

Could you give some examples of backgrounds prefixed with bgt? I need to know what regex to use to search for them.

Alright, I've released the latest version which should add the requested categorization, you can use the resort option in int/hg3/resort to just update the categorization of already-extracted pngs.

repo: trigger-death/GrisaiaExtractor


text:
Fix agreement in installer in Russian

Я согласен(на) с лиценией -> лицензией

Это к QtIFW, но процесс не простой: https://wiki.qt.io/Qt_Contribution_Guidelines

Вот место "ошибки" https://github.com/qtproject/installer-framework/blob/master/src/sdk/translations/ifw_ru.ts#L1423

Пока что добавлен bug на jira
https://bugreports.qt.io/browse/QTIFW-1496

authors: anastasiia-kornilova iakov khodand

repo: trikset/trik-studio


text:
Modus Select - Different behavior between optimized and unoptimized code

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have read the contributing guidelines

Describe the issue
We found an issue with the Modus Select. It behaves differently between optimized code and unoptimized code and because of that the logic written for default value and onValueChanged differs.
Below it's a picture on how a list looks like in 2 different environments one optimize and one not:

I noticed the issue also in the docs https://modus-web-components.trimble.com/?path=/docs/user-inputs-select--default
In the official docs you have e.details as the result value of an value change - which happened for us in optimized code
and in the canvas, the result is actually e.detail.display, what we saw in unoptimized code

Reduced test cases
No response
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What is the issue regarding ?
@trimble-oss/modus-web-components
What version of npm package are you using ?
"@trimble-oss/modus-react-components": "^0.1.49-react17"
Priority
Medium
What product/project are you using Modus Components for ?
Trimble Creator
What is your team/division name ?
team-trimble-creator
Are you willing to contribute ?
None
Are you using Modus Web Components in production ?
No response

@rthanga1 to talk to Maha to understand the issue better

repo: trimble-oss/modus-web-components


text:
angular components upgrade to v17

Description

fixes: #2002
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

How Has This Been Tested?

Checklist

[x ] My code follows the style guidelines of this project
[x ] I have performed a self-review of my own code
[x ] I have commented my code, particularly in hard-to-understand areas
[x ] I have made corresponding changes to the documentation
[x ] My changes generate no new warnings
[x ] I have added tests that prove my fix is effective or that my feature works
[x ] New and existing unit tests pass locally with my changes
[x ] Any dependent changes have been merged and published in downstream modules
[x ] I have checked my code and corrected any misspellings

Thanks for the PR - looks like the angular-workspace\ng17\projects\trimble-oss\modus-angular-components\package.json needs updating though:

I can do that and run npm i to update the package-lock.json but not sure if any other Angular changes are needed in this directory.

authors: coliff quynh-le-trimble


text:
SessionAuthentication

Use AwsBasicSessionAuthentication when a user is already logged in and uses a valid credentials object.

Thanks 😄

authors: pgiguere triniwiz

repo: triniwiz/nativescript-aws-sdk


text:
Pager automatically changes page after textfield focus\blur

Hello! I found a bug, ns-pager automatically changes page after textfield focus and blur event. Can you help me? Attached screen recording.
Versions:

nativescript-pager: 11.0.9,
nativescript-vue: 2.4.0,
tns-android: 6.1.0-2019-08-13-154901-03
tns-core-modules: 6.0.6

Thank you!

First thing you want to ensure ita backed back by an observable array if using the dynamic feature

try updating to the latest version while using ObservableArray

authors: abinpey triniwiz

repo: triniwiz/nativescript-pager


text:
Liveish editing with docker

Hi,
This is a simple change to enable live editing (still need to refresh the page with F5) for the docker env.
It cache bundle gem, and share files live with the container using docker-compose.
I change the readme so anyone can try it now and see for themself. it is very easy, follow instruction, then change something in index.md and press F5 on your browser.
Thank you to the tripit team and contribuors of slate!

Cool, I'll take a look at this when I have a chance. Thanks for contributing!

it is based off my dev box if you need more info:
https://github.com/pywebdesign/docker-rails-dev

(Sorry for the slow reply!)
Hmm, this Dockerfile is starting to get complicated. @pywebdesign, thoughts on just using Vagrant instead? Slate isn't hosted on servers with this Dockerfile, and we're not really using any fancy features of Docker, so Vagrant almost seems like it'd be simpler for our purposes.

I think we now have this, so going to close, but thanks!

authors: lord pywebdesign

repo: tripit/slate


text:
Android StatusBar styles not applied when app opened from notification.

Version

Type of phone: Android
OS Version: Multiple
Model: Multiple

Steps to reproduce
When clicking on the a Safe Paths notification in the drawer, the app opens to the LocationTracking.js view. However, the StatusBar style (light-content, transparent, translucent) set inside render does not get applied to the status bar. This. seems to be a known React Native bug, which can be worked around by using the static StatusBar methods.
Expected Behavior
When I click on a notification in the drawer, I expect the status bar in LocationTracking.js screen to be styled with light content, transparent, and translucent.
Upload any files to the Issue useful in helping us to investigate
The screenshot is difficult to see because it runs into the white background, but the status bar is white from notification click.

Work has been merged, closing.

repo: tripleblindmarket/covid-safe-paths


text:
Slack doesn't display ASCII responses properly

Wrap ASCII responses in Slack's blockquote syntax if :slack adapter is in use.

Thanks @reidblomquist!

authors: reidblomquist tristaneuan

repo: tristaneuan/lita-ascii-art


text:
Remove ITL from console when non-streaming

Before:

After:

CI ref: 15844661

repo: triton-inference-server/client


text:
Nespresso Vertuo Next

Hi,
is it compatible with the vertuo next ?

It seems to be impossible. I haven't enough time to try all available bluetooth commands, but it seems like the whole button isn't exposed as interface. (Also the Nespresso app doesn't have a button to do so unfortunately)

Hi there.
Nespresso Vertuo Next coffee machine has both Bluetooth and WiFi connections.
So, is it possible to add it to HomeBridge since it's connected to my WiFi network?

authors: isaaccs tritter xazac

repo: tritter/homebridge-brewer


text:
Error formatting using VSCode when using vue-property-decorator in Vue file.

Your Environment

Prettier version: 2.7.1
node version 18.17.0
package manager: pnpm@8
IDE: VScode with Prettier extension v10.1.0

Describe the bug

Error formatting using VSCode when using vue-property-decorator in Vue file.
To Reproduce

Open test.vue.
Run VSCode command Format Document With
Select Prettier - Code formatter
See VSCode OUTPUT panel.

<!-- test.vue -->
<template lang="pug">
div
  div(:class='$style.inputWrap')
    div(:class='$style.inputLabel') NAME
    input(
      v-model='name',
      type='text',
      :class='$style.input',
      :placeholder='testPlaceholder',
      ref='name')/

  div(:class='$style.inputWrap')
    div(:class='$style.inputLabel') PHONE
    input(
      v-model='phone',
      type='number',
      :class='$style.input',
      :placeholder='testPlaceholder',
      ref='phone')/
</template>

<script lang="ts">
import { Vue, Component ,Prop} from 'vue-property-decorator'

@Component
export default class TestVue extends Vue {
  @Prop(String) theme!: string

  name=''
  phone=''
  testPlaceholder = ''
}
</script>

<style module>
.input {
  display: block;
}
</style>

Expected behavior

Format normal.
Screenshots, code sample, etc

Configuration File (cat .prettierrc, prettier.config.js, .prettier.js)

// .prettierrc.cjs
/** @type {import('prettier').Options} */
module.exports = {
  importOrder: ['^@/(.*)$', '^[./]'],
  importOrderSeparation: true,
  importOrderParserPlugins: ['classProperties', 'decorators-legacy'],
  plugins: [
    require.resolve('@prettier/plugin-pug'),
    require('@trivago/prettier-plugin-sort-imports'),
  ],
}

Error log

["ERROR" - 10:20:33 AM] Error formatting document.
["ERROR" - 10:20:33 AM] Unexpected token (6:21)
   1 | <template lang="pug">
   2 | div
   3 |   div(:class='$style.inputWrap')
   4 |     div(:class='$style.inputLabel') NAME
   5 |     input(
   6 |       v-model='name',
   7 |       type='text',
   8 |       :class='$style.input',
   9 |       :placeholder='testPlaceholder',
  10 |       ref='name')/
  11 |
  12 |   div(:class='$style.inputWrap')
  13 |     div(:class='$style.inputLabel') PHONE
  14 |     input(
  15 |       v-model='phone',
  16 |       type='number',
  17 |       :class='$style.input',
  18 |       :placeholder='testPlaceholder',
  19 |       ref='phone')/
  20 | </template>
  21 |
  22 | <script lang="ts">
  23 | import { Vue, Component ,Prop} from 'vue-property-decorator'
  24 |
  25 | @Component
  26 | export default class LpForm extends Vue {
  27 |   @Prop(String) theme!: string
  28 |
  29 |   name=''
  30 |   phone=''
  31 |   testPlaceholder = ''
  32 | }
  33 | </script>
  34 |
  35 | <style module>
  36 | .input {
  37 |   display: block;
  38 | }
  39 | </style>
  40 |
SyntaxError: Unexpected token (6:21)
   1 | <template lang="pug">
   2 | div
   3 |   div(:class='$style.inputWrap')
   4 |     div(:class='$style.inputLabel') NAME
   5 |     input(
   6 |       v-model='name',
   7 |       type='text',
   8 |       :class='$style.input',
   9 |       :placeholder='testPlaceholder',
  10 |       ref='name')/
  11 |
  12 |   div(:class='$style.inputWrap')
  13 |     div(:class='$style.inputLabel') PHONE
  14 |     input(
  15 |       v-model='phone',
  16 |       type='number',
  17 |       :class='$style.input',
  18 |       :placeholder='testPlaceholder',
  19 |       ref='phone')/
  20 | </template>
  21 |
  22 | <script lang="ts">
  23 | import { Vue, Component ,Prop} from 'vue-property-decorator'
  24 |
  25 | @Component
  26 | export default class LpForm extends Vue {
  27 |   @Prop(String) theme!: string
  28 |
  29 |   name=''
  30 |   phone=''
  31 |   testPlaceholder = ''
  32 | }
  33 | </script>
  34 |
  35 | <style module>
  36 | .input {
  37 |   display: block;
  38 | }
  39 | </style>
  40 |
	at instantiate (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:72:32)
	at constructor (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:359:12)
	at Parser.raise (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:3339:19)
	at Parser.unexpected (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:3377:16)
	at Parser.parseClassMemberWithIsStatic (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:15716:12)
	at Parser.parseClassMember (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:15583:10)
	at C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:15523:14
	at Parser.withSmartMixTopicForbiddingContext (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:14323:14)
	at Parser.parseClassBody (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:15498:10)
	at Parser.parseClass (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:15472:22)
	at Parser.parseExportDefaultExpression (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:15997:19)
	at Parser.parseExport (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:15905:31)
	at Parser.parseStatementContent (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:14759:27)
	at Parser.parseStatement (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:14643:17)
	at Parser.parseBlockOrModuleBlockBody (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:15286:25)
	at Parser.parseBlockBody (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:15277:10)
	at Parser.parseProgram (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:14561:10)
	at Parser.parseTopLevel (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:14548:25)
	at Parser.parse (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:16556:10)
	at Object.parse (C:\path\to\node_modules\.pnpm\@babel+parser@7.18.9\node_modules\@babel\parser\lib\index.js:16608:38)
	at Object.preprocessor (C:\path\to\node_modules\.pnpm\@trivago+prettier-plugin-sort-imports@4.0.0_@vue+compiler-sfc@3.3.4_prettier@2.7.1\node_modules\@trivago\prettier-plugin-sort-imports\lib\src\preprocessors\preprocessor.js:15:24)
	at Object.vuePreprocessor [as preprocess] (C:\path\to\node_modules\.pnpm\@trivago+prettier-plugin-sort-imports@4.0.0_@vue+compiler-sfc@3.3.4_prettier@2.7.1\node_modules\@trivago\prettier-plugin-sort-imports\lib\src\preprocessors\vue-preprocessor.js:10:56)
	at Object.parse (C:\path\to\node_modules\.pnpm\prettier@2.7.1\node_modules\prettier\index.js:7330:25)
	at coreFormat (C:\path\to\node_modules\.pnpm\prettier@2.7.1\node_modules\prettier\index.js:8645:18)
	at formatWithCursor2 (C:\path\to\node_modules\.pnpm\prettier@2.7.1\node_modules\prettier\index.js:8837:18)
	at C:\path\to\node_modules\.pnpm\prettier@2.7.1\node_modules\prettier\index.js:37229:12
	at Object.format (C:\path\to\node_modules\.pnpm\prettier@2.7.1\node_modules\prettier\index.js:37243:12)
	at t.PrettierMainThreadInstance.format (c:\Users\Richex\.vscode\extensions\esbenp.prettier-vscode-10.1.0\dist\extension.js:1:18023)
	at t.default.format (c:\Users\Richex\.vscode\extensions\esbenp.prettier-vscode-10.1.0\dist\extension.js:1:16114)
	at async t.PrettierEditProvider.provideEdits (c:\Users\Richex\.vscode\extensions\esbenp.prettier-vscode-10.1.0\dist\extension.js:1:12672)
	at async U.provideDocumentFormattingEdits (c:\tools\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:104:44948)
["INFO" - 10:20:33 AM] Formatting completed in 27ms.

Contribute to @trivago/prettier-plugin-sort-imports

[ ] I'm willing to fix this bug 🥇

It seems like I overlooked the typescript plugin:
/** @type {import('prettier').Options} */
module.exports = {
  plugins: [
    require.resolve('@prettier/plugin-pug'),
    require.resolve('@trivago/prettier-plugin-sort-imports'),
  ],

  importOrder: ['^@/config(.*)$', '^@/util(.*)$', '^@/common(.*)$', '^@/(.*)$', '^[./]'],
  importOrderSeparation: true,
  importOrderParserPlugins: ['typescript', '["decorators", { "decoratorsBeforeExport": true }]'],
}

It's working normally now.

repo: trivago/prettier-plugin-sort-imports


text:
Rename files according to nhs_*.jl

Keeping in mind that more searches will be added, then this could increase readability in the directory, no?

I have a local branch depending on #8 and #9 where I move these files to a separate folder neighborhood_searches, so that we have neighborhood_searches/trivial.jl, neighborhood_searches/grid.jl and so on.

authors: LasNikas efaulhaber