text:
[BUG] All toolkit additions to budget down

Describe the bug
Since tonights update,
. Pacing on name column and goals on budgeted column
. Show Upcoming Transaction Total
. Striped Budget Rows
. Display goal amount and emphasize funded goals as green
basically everythingl down
To Reproduce
Steps to reproduce the behavior:

Go to 'budget
See error

Expected behavior
Category lines should be shaded blue/green to show funding progress and spending progress.  Both broken since "YNAB got better" message (Should be we have probably killed YNAB Toolkit extensuion again).
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. OSX, Windows]  win 11
Browser [e.g. chrome, firefox]  chrome
Toolkit Version [e.g. 2.22.0]  3.8.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":"2"},{"key":"AccountsEmphasizedInflows","value":true},{"key":"AccountsEmphasizedOutflows","value":true},{"key":"AccountsStripedRows","value":true},{"key":"AccountsStripedRowsColor","value":"#fafafa"},{"key":"AccountsStripedRowsDarkColor","value":"#1e1e1f"},{"key":"AssistedClear","value":true},{"key":"AutoDistributeSplits","value":true},{"key":"AutoEnableRunningBalance","value":true},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":false},{"key":"BottomNotificationBar","value":false},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"both"},{"key":"BudgetQuickSwitch","value":true},{"key":"BudgetSpendingGoal","value":false},{"key":"BulkEditMemo","value":false},{"key":"BulkManagePayees","value":false},{"key":"CalculateIRR","value":"Blue"},{"key":"CalendarFirstDay","value":"1"},{"key":"CategoryActivityCopy","value":true},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"CategorySoloMode","value":"cat-solo-mode-toggle-all"},{"key":"ChangeEnterBehavior","value":true},{"key":"ChangeMemoEnterBehavior","value":true},{"key":"CheckCreditBalances","value":false},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":true},{"key":"CollapseInspector","value":false},{"key":"ColourBlindMode","value":false},{"key":"CompactAccountHeader","value":false},{"key":"CompactIncomeVsExpense","value":true},{"key":"ConfirmEditTransactionCancellation","value":true},{"key":"ConfirmKeyboardCancelationOfTransactionChanges","value":true},{"key":"CreditCardEmoji","value":true},{"key":"CtrlEnterCleared","value":true},{"key":"CurrentMonthIndicator","value":false},{"key":"CustomAverageBudgeting","value":false},{"key":"CustomFlagNames","value":false},{"key":"CustomizeColourScheme","value":true},{"key":"DateOfMoney","value":true},{"key":"DaysOfBuffering","value":"12"},{"key":"DaysOfBufferingDate","value":true},{"key":"DaysOfBufferingExcludeCreditCards","value":false},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DefaultCCToCleared","value":false},{"key":"DeselectTransactionsOnSave","value":false},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"2"},{"key":"DisplayTotalMonthlyGoals","value":"show-total-only"},{"key":"DisplayTotalOverspent","value":true},{"key":"DisplayUpcomingAmount","value":true},{"key":"EasyTransactionApproval","value":true},{"key":"EditAccountButton","value":"0"},{"key":"EmphasizeNegativeLoans","value":false},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"FilterCategories","value":true},{"key":"GoalIndicator","value":true},{"key":"GoalWarningColor","value":true},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":false},{"key":"HideAgeOfMoney","value":false},{"key":"HideClosedAccounts","value":true},{"key":"HideDebtRatio","value":false},{"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":"3"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":true},{"key":"LastReconciledDate","value":"days-since"},{"key":"LinkInMemo","value":false},{"key":"LinkToInflows","value":true},{"key":"LiveOnLastMonthsIncome","value":"3"},{"key":"MasterCategoryRowColor","value":true},{"key":"MasterCategoryRowColorSelect","value":"#d1d1d6"},{"key":"MasterCategoryRowDarkColorSelect","value":"#636366"},{"key":"MemoAsMarkdown","value":false},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"2"},{"key":"NotesAsMarkdown","value":false},{"key":"POSStyleCurrencyEntryMode","value":false},{"key":"Pacing","value":false},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"2"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconcileAssistant","value":false},{"key":"ReconcileBalance","value":false},{"key":"ReconcileConfetti","value":true},{"key":"ReconciledTextColor","value":"4"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":false},{"key":"ResetColumnWidths","value":true},{"key":"RightClickToEdit","value":false},{"key":"RowHeight","value":"1"},{"key":"RowsHeight","value":"3"},{"key":"SavingsRatio","value":"0.40"},{"key":"ScrollableEditMenu","value":true},{"key":"SeamlessBudgetHeader","value":true},{"key":"SetMultipleFlags","value":true},{"key":"ShowAvailableAfterSavings","value":true},{"key":"ShowCategoryBalance","value":true},{"key":"SpareChange","value":true},{"key":"SplitTransactionAutoAdjust","value":true},{"key":"SplitTransactionAutoFillPayee","value":false},{"key":"SplitTransactionTabExpand","value":true},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":true},{"key":"StripedBudgetRows","value":true},{"key":"SubtractUpcomingFromAvailable","value":false},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":true},{"key":"ToBeBudgetedWarning","value":true},{"key":"ToggleAccountColumns","value":true},{"key":"ToggleMasterCategories","value":true},{"key":"ToggleSplits","value":true},{"key":"ToggleTransactionFilters","value":"1"},{"key":"ToolkitReports","value":true},{"key":"UnclearedAccountHighlight","value":true},{"key":"ViewZeroAsEmpty","value":true},{"key":"l10n","value":"0"},{"key":"options.dark-mode","value":false}]

Since the update, you can't even edit account entries if the Toolkit is on. :(

I can edit transactions with toolkit on.

From: rpraying @.>
Sent: 03 October 2023 00:46
To: toolkit-for-ynab/toolkit-for-ynab @.>
Cc: d-whitaker @.>; Author @.>
Subject: Re: [toolkit-for-ynab/toolkit-for-ynab] [BUG] All toolkit additions to budget down (Issue #3246)
Since the update, you can't even edit account entries if the Toolkit is on. :(
—
Reply to this email directly, view it on GitHubhttps://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/3246#issuecomment-1743929182, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJC3Z2P7F753NIGHRH5QPLDX5NG6PAVCNFSM6AAAAAA5P4G7F6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTHEZDSMJYGI.
You are receiving this because you authored the thread.Message ID: @.***>

I can't edit transactions.
I can't import transactions. And then when I reload the app with Toolkit disabled, the transactions are imported but are not matched to manually entered transactions.
When I "Enter Now" a transfer between accounts, it goes into the register and shows "Needs a Category".
None of this happens with the Toolkit disabled.

I can't edit transactions.
I can't import transactions. And then when I reload the app with Toolkit disabled, the transactions are imported but are not matched to manually entered transactions.
When I "Enter Now" a transfer between accounts, it goes into the register and shows "Needs a Category".
None of this happens with the Toolkit disabled.

That's exactly the behavior I'm getting, too. Thank you, @nolesrule, for describing it so precisely so I don't have to!

Since yesterday's update I'm having the same issue as described by the others on both FF and Brave (uses Blink engine)

I have the same issues as described above.  (Google Chrome)

I am able to enter transactions, and the Toolkit mostly appears to be working.  However, pacing indicators have disappeared.

All goals have disappeared totals -indicator

Add Total Monthly Goals not working either

Can we relabel this issue? Other toolkit features are working because it looks like YNAB updated "upcoming transactions" to use the Glimmer components. So it looks like any features that look at upcoming transactions are having issues, including total monthly goals.
The whole toolkit is not down, just upcoming transactions.

I didn't title it ALL TOOLKIT down - it is titled ALL TOOLKIT ADDITIONS TO  ""BUDGET"" DOWN.
I'll change it to MOST budget extensions down.

From: Joshua Saxton @.>
Sent: 05 October 2023 13:36
To: toolkit-for-ynab/toolkit-for-ynab @.>
Cc: d-whitaker @.>; Author @.>
Subject: Re: [toolkit-for-ynab/toolkit-for-ynab] [BUG] All toolkit additions to budget down (Issue #3246)
Can we relabel this issue? Other toolkit features are working because it looks like YNAB updated "upcoming transactions" to use the Glimmer components. So it looks like any features that look at upcoming transactions are having issues, including total monthly goals.
The whole toolkit is not down, just upcoming transactions.
—
Reply to this email directly, view it on GitHubhttps://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/3246#issuecomment-1748812589, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJC3Z2MG2X6T6ULTNXN7S6LX52SUTAVCNFSM6AAAAAA5P4G7F6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYHAYTENJYHE.
You are receiving this because you authored the thread.Message ID: @.***>

Same here. A few things are still working (like filter categories) but any additional columns to the budget, as well as most other features have stopped working.

Same here.  Noticed when I looked for pacing.  Checked the toolkit and pacing is still selected, just not showing up.

Total Monthly Goals appears to be working now, toolkit version 3.9.0.

Can confirm, pacing at the very least is still broken.

Budget Rows Progress Bars broken for me. as well as subtract upcoming transactions from available. My two most important features to manage spend :(

authors: LSTO55 Rabbit-gts TheRotag d-whitaker heni-amiri jawy007 monsterfurby mopsis73 nolesrule ohsoquiet rpraying saxtonjoshua1 shamadoo

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


text:
godep save with GO15VENDOREXPERIMENT doesn't save everything

godep v41 (from head today)
godep restore && godep save ./... show no diffs.
godep restore; export GO15VENDOREXPERIMENT=1; rm -rf Godeps; godep save ./... returns 0, but there are diffs to Godeps.json and there's a LOT of things missing from my vendor/ dir, even stuff that is listed in Godeps.json
I can't tell if the other open issues are related - these are things that are directly referenced by code in ./... - not transitive.

Confirmed, closing in favor of #358

source: gharchive/issue

authors: freeformz thockin

repo: tools/godep

license_type: permissive

license_source: github-api


text:
Issue with update_index on after_commit :delete when overriding _id

@pyromaniac Due to an existing implementation detail (in another language) I have an index definition in Chewy that ends up looking like this ...
module Indices
  class DogsIndex < Chewy::Index
    define_type Models::Dog do
      field :id, type: "long"
    end

    define_type Models::Owner, name: "owner" do
      root parent: "dog",
           parent_id: -> { dog_id },
           _id: -> { external_id } do
        field :id, type: "long", value: -> { external_id }
        field :dog_id, type: "long"
        field :name
      end
    end
  end
end

For my Models::Owner it looks like
module Models
  class Owner < ActiveRecord::Base
    belongs_to :dog
    update_index "Indices::Dogs#owner", self
  end
end

I also tried these variations on update_index
update_index "Indices::Dogs#owner" do self end

update_index "Indices::Dogs#owner" do |owner| owner end

They had the same impact.
external_id is a attribute on an Owner model instance.
When creating or updating a instance of Owner I see no issues. However when I destroy an instance I get a sad face because the { external_id } bit is evaluated and self is equal to the id of the Owner instance, not the Owner instance, so therefore I get an error like undefined local variable or method external_id for 1:Fixnum
I'm trying to debug through this myself, but no luck so far.

To be even more clear - here is what the original mapping code looks like in Python. Perhaps what I'm doing wrong has to do with my declaration of the mapping in Chewy and not to do with the update_index call
self._put_mapping('owner', {
            "owner": {
                "_parent": {
                    "type": "dog"
                },
                "_routing": {
                    "required": True,
                    "path": "dog_id"
                },
                "_id": {
                    "path": "id"
                },
                "properties": {
                    "dog_id": {
                        "type": "integer",
                        "index": "not_analyzed",
                    },
                   "name": {
                      "index": "not_analyzed",
                   },
                }
            }
        }, index=self.index_name)

I also realize I can get to the external id in the updates_index block via the previous_changes hash, but I don't see how that helps unless I use some kind of anti-pattern to decorate self such that self.id returns self.external_id inside of the block only.

Don't you have any stacktrace?

D, [2015-11-14T00:47:31.414963 #19050] DEBUG -- :   Models::Owner Load (0.6ms)  SELECT  owners.* FROM owners  WHERE owners.deleted_at IS NULL AND owners.id = 7511 LIMIT 1
DEBUG -  Chewy strategies stack: [2] <- atomic @ /home/vagrant/xxxxxxxx/current/dwapi/lib/routes/resources.rb:173
DEBUG -  Chewy strategies stack: [2] -> atomic @ /home/vagrant/xxxxxxxx/current/dwapi/lib/routes/resources.rb:173
DEBUG -  Chewy strategies stack: [2] <- atomic @ /home/vagrant/xxxxxxxx/current/dwapi/lib/routes/resources.rb:182
D, [2015-11-14T00:47:31.417015 #19050] DEBUG -- :    (0.4ms)  BEGIN
D, [2015-11-14T00:47:31.418603 #19050] DEBUG -- :   SQL (0.4ms)  UPDATE owners SET owners.updated_at = '2015-11-14 00:47:31', owners.deleted_at = '2015-11-14 00:47:31' WHERE owners.id = 7511
D, [2015-11-14T00:47:31.420985 #19050] DEBUG -- :    (2.0ms)  COMMIT
DEBUG -  Chewy strategies stack: [2] -> atomic @ /home/vagrant/xxxxxxxx/current/dwapi/lib/routes/resources.rb:182
D, [2015-11-14T00:47:31.425000 #19050] DEBUG -- :    (0.5ms)  SELECT COUNT(*) FROM owners  WHERE owners.deleted_at IS NULL AND owners.id IN (7511)
NameError - undefined local variable or method external_id' for 7511:Fixnum: 	/home/vagrant/xxxxx/current/dwapi/lib/indices/dogs_index.rb:11:in block (2 levels) in class:DogsIndex'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/fields/root.rb:72:in instance_exec' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/fields/root.rb:72:in compose_id'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:89:in delete_bulk_entry' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:81:in block (2 levels) in bulk_body'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:81:in map' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:81:in block in bulk_body'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:79:in each' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:79:in inject'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:79:in bulk_body' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:30:in block (2 levels) in import'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:126:in block in import_objects' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:125:in each_slice'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:125:in each' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:125:in map'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:125:in import_objects' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:86:in import'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:28:in block in import' 	/usr/local/rvm/gems/ruby-2.1.1/gems/activesupport-4.1.7/lib/active_support/notifications.rb:159:in block in instrument'
/usr/local/rvm/gems/ruby-2.1.1/gems/activesupport-4.1.7/lib/active_support/notifications/instrumenter.rb:20:in instrument' 	/usr/local/rvm/gems/ruby-2.1.1/gems/activesupport-4.1.7/lib/active_support/notifications.rb:159:in instrument'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:27:in import' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy/atomic.rb:27:in block in leave'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy/atomic.rb:27:in each' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy/atomic.rb:27:in all?'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy/atomic.rb:27:in leave' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy.rb:36:in tap'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy.rb:36:in pop' 	/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy.rb:44:in wrap'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy.rb:161:in strategy' 	/home/vagrant/xxxxxxx/current/dwapi/lib/routes/resources.rb:182:in block in registered'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1603:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1603:in block in compile!'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:966:in []' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:966:in block (3 levels) in route!'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:985:in route_eval' 	/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:135:in route_eval_with_newrelic'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:966:in block (2 levels) in route!' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1006:in block in process_route'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1004:in catch' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1004:in process_route'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:115:in process_route_with_newrelic' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:964:in block in route!'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:963:in each' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:963:in route!'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1076:in block in dispatch!' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in block in invoke'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in catch' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in invoke'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1073:in dispatch!' 	/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:166:in dispatch_and_notice_errors_with_newrelic'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:152:in block in dispatch_with_newrelic' 	/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/controller_instrumentation.rb:366:in perform_action_with_newrelic_trace'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:149:in dispatch_with_newrelic' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in block in call!'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in block in invoke' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in catch'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in invoke' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in call!'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:886:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/rack/browser_monitoring.rb:23:in traced_call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:55:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/rack/agent_hooks.rb:30:in traced_call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:55:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/bugsnag-2.8.10/lib/bugsnag/rack.rb:33:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-cors-0.3.1/lib/rack/cors.rb:72:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/home/vagrant/mattermark/current/dwapi/lib/rack/rate_limit.rb:21:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-1.5.2/lib/rack/logger.rb:15:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-1.5.2/lib/rack/commonlogger.rb:33:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:217:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:210:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-1.5.2/lib/rack/head.rb:11:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:180:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:2014:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1478:in block in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1788:in synchronize'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1478:in call' 	/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:86:in block in pre_process' 	/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:84:in catch'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:84:in pre_process' 	/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:53:in process'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:39:in receive_data' 	/usr/local/rvm/gems/ruby-2.1.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run_machine'
/usr/local/rvm/gems/ruby-2.1.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run' 	/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/backends/base.rb:73:in start'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/server.rb:162:in start' 	/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/controllers/controller.rb:87:in start'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/runner.rb:200:in run_command' 	/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/runner.rb:156:in run!'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/bin/thin:6:in <top (required)>' 	/usr/local/rvm/gems/ruby-2.1.1/bin/thin:23:in load'
/usr/local/rvm/gems/ruby-2.1.1/bin/thin:23:in <main>' 	/usr/local/rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in eval'
/usr/local/rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in <main>' E, [2015-11-14T00:47:31.438646 #19050] ERROR -- : Exception: NameError: undefined local variable or method external_id' for 7511:Fixnum
E, [2015-11-14T00:47:31.438792 #19050] ERROR -- : /home/vagrant/xxxxxx/current/dwapi/lib/indices/dogs_index.rb:11:in block (2 levels) in <class:DogsIndex>' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/fields/root.rb:72:in instance_exec'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/fields/root.rb:72:in compose_id' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:89:in delete_bulk_entry'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:81:in block (2 levels) in bulk_body' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:81:in map'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:81:in block in bulk_body' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:79:in each'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:79:in inject' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:79:in bulk_body'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:30:in block (2 levels) in import' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:126:in block in import_objects'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:125:in each_slice' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:125:in each'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:125:in map' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:125:in import_objects'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/adapter/orm.rb:86:in import' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:28:in block in import'
/usr/local/rvm/gems/ruby-2.1.1/gems/activesupport-4.1.7/lib/active_support/notifications.rb:159:in block in instrument' /usr/local/rvm/gems/ruby-2.1.1/gems/activesupport-4.1.7/lib/active_support/notifications/instrumenter.rb:20:in instrument'
/usr/local/rvm/gems/ruby-2.1.1/gems/activesupport-4.1.7/lib/active_support/notifications.rb:159:in instrument' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/type/import.rb:27:in import'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy/atomic.rb:27:in block in leave' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy/atomic.rb:27:in each'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy/atomic.rb:27:in all?' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy/atomic.rb:27:in leave'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy.rb:36:in tap' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy.rb:36:in pop'
/usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy/strategy.rb:44:in wrap' /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.7.0/lib/chewy.rb:161:in strategy'
/home/vagrant/xxxxxx/current/dwapi/lib/routes/resources.rb:182:in block in registered' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1603:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1603:in block in compile!' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:966:in []'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:966:in block (3 levels) in route!' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:985:in route_eval'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:135:in route_eval_with_newrelic' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:966:in block (2 levels) in route!'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1006:in block in process_route' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1004:in catch'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1004:in process_route' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:115:in process_route_with_newrelic'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:964:in block in route!' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:963:in each'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:963:in route!' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1076:in block in dispatch!'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in block in invoke' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in catch'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in invoke' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1073:in dispatch!'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:166:in dispatch_and_notice_errors_with_newrelic' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:152:in block in dispatch_with_newrelic'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/controller_instrumentation.rb:366:in perform_action_with_newrelic_trace' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/sinatra.rb:149:in dispatch_with_newrelic'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in block in call!' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in block in invoke'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in catch' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in invoke'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in call!' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:886:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/rack/browser_monitoring.rb:23:in traced_call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:55:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/rack/agent_hooks.rb:30:in traced_call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:55:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/bugsnag-2.8.10/lib/bugsnag/rack.rb:33:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-cors-0.3.1/lib/rack/cors.rb:72:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/home/vagrant/mattermark/current/dwapi/lib/rack/rate_limit.rb:21:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-1.5.2/lib/rack/logger.rb:15:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-1.5.2/lib/rack/commonlogger.rb:33:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:217:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:210:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-1.5.2/lib/rack/head.rb:11:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:180:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:2014:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1478:in block in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1788:in synchronize' /usr/local/rvm/gems/ruby-2.1.1/gems/sinatra-1.4.5/lib/sinatra/base.rb:1478:in call'
/usr/local/rvm/gems/ruby-2.1.1/gems/newrelic_rpm-3.9.9.275/lib/new_relic/agent/instrumentation/middleware_tracing.rb:57:in call' /usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:86:in block in pre_process'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:84:in catch' /usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:84:in pre_process'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:53:in process' /usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/connection.rb:39:in receive_data'
/usr/local/rvm/gems/ruby-2.1.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run_machine' /usr/local/rvm/gems/ruby-2.1.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/backends/base.rb:73:in start' /usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/server.rb:162:in start'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/controllers/controller.rb:87:in start' /usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/runner.rb:200:in run_command'
/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/lib/thin/runner.rb:156:in run!' /usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.3/bin/thin:6:in <top (required)>'
/usr/local/rvm/gems/ruby-2.1.1/bin/thin:23:in load' /usr/local/rvm/gems/ruby-2.1.1/bin/thin:23:in '
/usr/local/rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in eval' /usr/local/rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in '
192.168.33.10 - - [14/Nov/2015 00:47:31] "DELETE /1.3/orm/owners/7511 HTTP/1.1" 500 11867 0.0805

Sorry to bother you with this, I've just been busting my face up against it all day.

Well, the problem is here: https://github.com/toptal/chewy/blob/master/lib/chewy/type/import.rb#L91
I'm trying to compose id, while id is not an object. And it is not an object because atomic strategy stores ids instead of objects. https://github.com/toptal/chewy/blob/master/lib/chewy/strategy/atomic.rb#L23

Is this working as you expect or do you believe that this is a defect for which a change / fix is appropriate?

Defect. And solution would be: in the atomic strategy here https://github.com/toptal/chewy/blob/master/lib/chewy/strategy/atomic.rb#L23 to use adapter.some_method which returns identify method result or composed ids using type-defined id evaluator if is exist. And remove https://github.com/toptal/chewy/blob/master/lib/chewy/type/import.rb#L91 and https://github.com/toptal/chewy/blob/master/lib/chewy/type/import.rb#L111 lines code since here we will have composed id already.

Misspelled: use type.identify which uses type.adapter.identify to add composing logic there

The only thing I'm concerned about is: composing id evaluation would be highly inefficient for objects collection. But actually we have the same case currently, so it is fine. Also none of the specs supposed to be broken with such an approach.

k. With a fix in place will you patch 0.7.0 to 0.7.1 or do I need to switch to latest v?

Better to switch to latest, there are tones of fixes

Which version of ES are you running your specs against? I can't get latest master to pass locally. Which is odd because it didn't used to be an issue.

Failure/Error: stub_model(:city)
     NoMethodError:
       undefined method `stub_model' for #<RSpec::ExampleGroups::ChewySearch::NamedScopes:0x000000069f1388>

19 additional errors with the same NoMethodError.

Yeah same problem even with a completely fresh checkout. Hmm.

Check out travis.yml
14 Ноя 2015 г. 12:49 пользователь "caldwecr" notifications@github.com
написал:

Yeah same problem even with a completely fresh checkout. Hmm.
—
Reply to this email directly or view it on GitHub.

@pyromaniac as an FYI I had to uncomment the
# gem 'activerecord'

from the Gemfile to get the specs passing. Not sure why so many gems are commented out in the Gemfile

Well, because gemfile is mostly a template for appraisals :) Any success on patch? Maybe you have questions?

Close on patch. About to push it up.

Ok well I'm having trouble with removing line 91 from type/import.rb - can you be a bit more clear about exactly what you think these areas of code should look like?
I'll push up the change I have and open a PR where we can discuss the removals (L91 and L111)

See #282

Hey, @caldwecr, look, it is a bit complicated and probably almost impossible to fix this in a common way, but there is a workaround:
module Models
  class Owner < ActiveRecord::Base
    belongs_to :dog
    update_index("Indices::Dogs#owner") { destroyed? ? external_id : self }
  end
end

Tell me please if it works or not for you. I will continue fixing everything over the weekend, currently I don't have much time to do this though.

Or maybe it would not help. Try the latest master please, I did some patch

The latest master appears to fix the problem when I test it in the application. It (strangely) still fails the spec that I wrote
describe "Destroying a Owner model" do
    it "updates the ::dogs#owner" do
      expect { owner.destroy }.
        to update_index Indices::DogsIndex::Owner
    end
  end

produces
(to actual test the change I built the gem and installed it as 0.8.3)
Failure/Error: expect { owner.destroy }.
     NoMethodError:
       undefined method `with' for nil:NilClass
     # /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.8.3/lib/chewy/rspec/update_index.rb:103:in `instance_eval'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.8.3/lib/chewy/rspec/update_index.rb:103:in `instance_eval'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/chewy-0.8.3/lib/chewy/rspec/update_index.rb:103:in `block (2 levels) in <top (required)>'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-expectations-3.1.2/lib/rspec/matchers/dsl.rb:43:in `block in match'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-expectations-3.1.2/lib/rspec/expectations/handler.rb:48:in `handle_matcher'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-expectations-3.1.2/lib/rspec/expectations/expectation_target.rb:54:in `to'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-expectations-3.1.2/lib/rspec/expectations/expectation_target.rb:87:in `to'
     # ./spec/chewy/updating_indexes_spec.rb:54:in `block (3 levels) in <top (required)>'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:152:in `instance_exec'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:152:in `block in run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:222:in `call'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:222:in `call'
     # ./spec/spec_helper.rb:91:in `block (3 levels) in <top (required)>'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/database_cleaner-1.4.1/lib/database_cleaner/generic/base.rb:15:in `cleaning'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/database_cleaner-1.4.1/lib/database_cleaner/base.rb:92:in `cleaning'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/database_cleaner-1.4.1/lib/database_cleaner/configuration.rb:86:in `block (2 levels) in cleaning'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/database_cleaner-1.4.1/lib/database_cleaner/configuration.rb:87:in `call'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/database_cleaner-1.4.1/lib/database_cleaner/configuration.rb:87:in `cleaning'
     # ./spec/spec_helper.rb:90:in `block (2 levels) in <top (required)>'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:322:in `instance_exec'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:322:in `instance_exec'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/hooks.rb:380:in `execute_with'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/hooks.rb:446:in `block (2 levels) in run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:222:in `call'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:222:in `call'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/hooks.rb:447:in `run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/hooks.rb:500:in `run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:331:in `with_around_example_hooks'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example.rb:149:in `run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example_group.rb:490:in `block in run_examples'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example_group.rb:486:in `map'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example_group.rb:486:in `run_examples'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example_group.rb:453:in `run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example_group.rb:454:in `block in run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example_group.rb:454:in `map'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/example_group.rb:454:in `run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:111:in `block (2 levels) in run_specs'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:111:in `map'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:111:in `block in run_specs'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/reporter.rb:53:in `report'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:107:in `run_specs'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:85:in `run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:69:in `run'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:37:in `invoke'
     # /usr/local/rvm/gems/ruby-2.1.1/gems/rspec-core-3.1.7/exe/rspec:4:in `<top (required)>'
     # /usr/local/rvm/gems/ruby-2.1.1/bin/rspec:23:in `load'
     # /usr/local/rvm/gems/ruby-2.1.1/bin/rspec:23:in `<main>'
     # /usr/local/rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `eval'
     # /usr/local/rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `<main>'

Finished in 8.32 seconds (files took 2.2 seconds to load)
1 example, 1 failure

It seems like you have Mocha installed but not enabled: https://github.com/toptal/chewy/blob/master/lib/chewy/rspec/update_index.rb#L197

Looks good to me. Can you ship a latest version 0.8.4?
Kind regards. Thanks for all the assistance.

Welcome! As for a new version - it will be a little bit later. Use master please for now.

Btw, there was a Mocha fix, did it help?

Yes that did help. It resolved my issue.

@mainameiz thanks, you was in time :)

Great :-)

authors: caldwecr mainameiz pyromaniac

repo: toptal/chewy

license: mit

license_source: bigquery


text:
How to get proper value of Groovy method in script score?

I enabled dynamic scripting.
2.3.0 :214 > DiagnosesIndex.script_score("_score").query(match: {name: "cham k"}).map(&:_score)
  DiagnosesIndex Search (28.7ms) {:body=>{:query=>{:function_score=>{:functions=>[{:script_score=>{:script=>"_score"}}], :query=>{:match=>{:name=>"cham k"}}}}}, :index=>["diagnoses"], :type=>[]}
 => [2.5906327, 1.1099176, 1.0467807, 1.0402842, 1.0119661, 0.8601855, 0.6585796, 0.5438596, 0.36430773, 0.36430773]

However, I'm trying to get the integer value of script score using Groovy method:
2.3.0 :215 > DiagnosesIndex.script_score("_score.intValue()").query(match: {name: "cham k"}).map(&:_score)
  DiagnosesIndex Search (13.1ms) {:body=>{:query=>{:function_score=>{:functions=>[{:script_score=>{:script=>"_score.intValue()"}}], :query=>{:match=>{:name=>"cham k"}}}}}, :index=>["diagnoses"], :type=>[]}
 => [1.6095443, 1.0535263, 1.023123, 1.0199432, 1.0059652, 0.0, 0.0, 0.0, 0.0, 0.0]

Values do change but still in double values and not being integers. I'm not sure what causing this or what's really behind this?

_score is a float number, not sure what are you trying to do

@pyromaniac so calling _score always yield float values after all even though I'm trying to get integer values like ceil(_score), floor(_score), abs(_score), _score.intValue() in script_score? Integer values are what I'm trying to get.

I haven't play with function score, so can't help you here, but obviously you are doing something wrong and it is not related to chewy, read ES docs carefully

Thanks @pyromaniac, I was hoping to understand what's going behind this mystery.

I'm sorry I couldn't help you more

authors: knd pyromaniac


text:
issue - running yarn test:cypress with build:packages (lerna)

Hi, how to run "yarn test:cypress" in picasso?
I tried to run it and get the following error. Not sure what is going on.
`Stephanie@DESKTOP-90ROKD9 MINGW64 /d/reactpicasso (master)
$ yarn run test:cypress
yarn run v1.22.17
$ yarn build:package && yarn test:setup cypress run-ct
$ lerna run build:package --stream --parallel
lerna notice cli v3.22.1
lerna info versioning independent
lerna info Executing command in 7 packages: "yarn run build:package"
@toptal/picasso-charts: $ cross-env NODE_ENV=production node ../../bin/build.js --tsConfig=./tsconfig.build.json
@toptal/picasso-codemod: $ ./bin/build.sh
@toptal/picasso-forms: $ cross-env NODE_ENV=production node ../../bin/build.js --tsConfig=./tsconfig.build.json
@toptal/picasso: $ cross-env NODE_ENV=production node ../../bin/build.js --tsConfig=./tsconfig.build.json
@toptal/picasso-shared: $ cross-env NODE_ENV=production node ../../bin/build.js --tsConfig=./tsconfig.build.json
@toptal/picasso-provider: $ cross-env NODE_ENV=production node ./bin/build.js
@topkit/analytics-charts: $ cross-env NODE_ENV=production node ../../bin/build.js --tsConfig=./tsconfig.build.json
@toptal/picasso-charts: Building @toptal/picasso-charts:21.0.0
@toptal/picasso-charts: Removing: dist-package
@toptal/picasso-charts: node:internal/fs/utils:344
@toptal/picasso-charts:     throw err;
@toptal/picasso-charts:     ^
@toptal/picasso-charts: Error: ENOENT: no such file or directory, stat 'dist-package'
@toptal/picasso-charts:     at Object.statSync (node:fs:1536:3)
@toptal/picasso-charts:     at _node_internal (node:internal/fs/utils:793:8)
@toptal/picasso-charts:     at Object.rmdirSync (node:fs:1156:15)
@toptal/picasso-charts:     at clean (D:\reactpicasso\bin\build.js:25:8)
@toptal/picasso-charts:     at compile (D:\reactpicasso\bin\build.js:31:3)
@toptal/picasso-charts:     at Object. (D:\reactpicasso\bin\build.js:48:1)
@toptal/picasso-charts:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
@toptal/picasso-charts:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
@toptal/picasso-charts:     at Module.load (node:internal/modules/cjs/loader:981:32)
@toptal/picasso-charts:     at Function.Module._load (node:internal/modules/cjs/loader:822:12) {
@toptal/picasso-charts:   errno: -4058,
@toptal/picasso-charts:   syscall: 'stat',
@toptal/picasso-charts:   code: 'ENOENT',
@toptal/picasso-charts:   path: 'dist-package'
@toptal/picasso-charts: }
@toptal/picasso-forms: Building @toptal/picasso-forms:28.0.0
@toptal/picasso-forms: Removing: dist-package
@toptal/picasso-forms: node:internal/fs/utils:344
@toptal/picasso-forms:     throw err;
@toptal/picasso-forms:     ^
@toptal/picasso-forms: Error: ENOENT: no such file or directory, stat 'dist-package'
@toptal/picasso-forms:     at Object.statSync (node:fs:1536:3)
@toptal/picasso-forms:     at _node_internal (node:internal/fs/utils:793:8)
@toptal/picasso-forms:     at Object.rmdirSync (node:fs:1156:15)
@toptal/picasso-forms:     at clean (D:\reactpicasso\bin\build.js:25:8)
@toptal/picasso-forms:     at compile (D:\reactpicasso\bin\build.js:31:3)
@toptal/picasso-forms:     at Object. (D:\reactpicasso\bin\build.js:48:1)
@toptal/picasso-forms:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
@toptal/picasso-forms:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
@toptal/picasso-forms:     at Module.load (node:internal/modules/cjs/loader:981:32)
@toptal/picasso-forms:     at Function.Module._load (node:internal/modules/cjs/loader:822:12) {
@toptal/picasso-forms:   errno: -4058,
@toptal/picasso-forms:   syscall: 'stat',
@toptal/picasso-forms:   code: 'ENOENT',
@toptal/picasso-forms:   path: 'dist-package'
@toptal/picasso-forms: }
@toptal/picasso-shared: Building @toptal/picasso-shared:7.2.2
@toptal/picasso-shared: Removing: dist-package
@toptal/picasso: Building @toptal/picasso:18.3.0
@toptal/picasso: Removing: dist-package
@toptal/picasso-shared: node:internal/fs/utils:344
@toptal/picasso-shared:     throw err;
@toptal/picasso-shared:     ^
@toptal/picasso-shared: Error: ENOENT: no such file or directory, stat 'dist-package'
@toptal/picasso-shared:     at Object.statSync (node:fs:1536:3)
@toptal/picasso-shared:     at _node_internal (node:internal/fs/utils:793:8)
@toptal/picasso-shared:     at Object.rmdirSync (node:fs:1156:15)
@toptal/picasso-shared:     at clean (D:\reactpicasso\bin\build.js:25:8)
@toptal/picasso-shared:     at compile (D:\reactpicasso\bin\build.js:31:3)
@toptal/picasso-shared:     at Object. (D:\reactpicasso\bin\build.js:48:1)
@toptal/picasso-shared:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
@toptal/picasso-shared:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
@toptal/picasso-shared:     at Module.load (node:internal/modules/cjs/loader:981:32)
@toptal/picasso-shared:     at Function.Module._load (node:internal/modules/cjs/loader:822:12) {
@toptal/picasso-shared:   errno: -4058,
@toptal/picasso-shared:   syscall: 'stat',
@toptal/picasso-shared:   code: 'ENOENT',
@toptal/picasso-shared:   path: 'dist-package'
@toptal/picasso-shared: }
@toptal/picasso: node:internal/fs/utils:344
@toptal/picasso:     throw err;
@toptal/picasso:     ^
@toptal/picasso: Error: ENOENT: no such file or directory, stat 'dist-package'
@toptal/picasso:     at Object.statSync (node:fs:1536:3)
@toptal/picasso:     at _node_internal (node:internal/fs/utils:793:8)
@toptal/picasso:     at Object.rmdirSync (node:fs:1156:15)
@toptal/picasso:     at clean (D:\reactpicasso\bin\build.js:25:8)
@toptal/picasso:     at compile (D:\reactpicasso\bin\build.js:31:3)
@toptal/picasso:     at Object. (D:\reactpicasso\bin\build.js:48:1)
@toptal/picasso:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
@toptal/picasso:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
@toptal/picasso:     at Module.load (node:internal/modules/cjs/loader:981:32)
@toptal/picasso:     at Function.Module._load (node:internal/modules/cjs/loader:822:12) {
@toptal/picasso:   errno: -4058,
@toptal/picasso:   syscall: 'stat',
@toptal/picasso:   code: 'ENOENT',
@toptal/picasso:   path: 'dist-package'
@toptal/picasso: }
@toptal/picasso-charts: error Command failed with exit code 1.
@toptal/picasso-charts: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@topkit/analytics-charts: Building @topkit/analytics-charts:18.0.0
@topkit/analytics-charts: Removing: dist-package
@topkit/analytics-charts: node:internal/fs/utils:344
@topkit/analytics-charts:     throw err;
@topkit/analytics-charts:     ^
@topkit/analytics-charts: Error: ENOENT: no such file or directory, stat 'dist-package'
@topkit/analytics-charts:     at Object.statSync (node:fs:1536:3)
@topkit/analytics-charts:     at _node_internal (node:internal/fs/utils:793:8)
@topkit/analytics-charts:     at Object.rmdirSync (node:fs:1156:15)
@topkit/analytics-charts:     at clean (D:\reactpicasso\bin\build.js:25:8)
@topkit/analytics-charts:     at compile (D:\reactpicasso\bin\build.js:31:3)
@topkit/analytics-charts:     at Object. (D:\reactpicasso\bin\build.js:48:1)
@topkit/analytics-charts:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
@topkit/analytics-charts:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
@topkit/analytics-charts:     at Module.load (node:internal/modules/cjs/loader:981:32)
@topkit/analytics-charts:     at Function.Module._load (node:internal/modules/cjs/loader:822:12) {
@topkit/analytics-charts:   errno: -4058,
@topkit/analytics-charts:   syscall: 'stat',
@topkit/analytics-charts:   code: 'ENOENT',
@topkit/analytics-charts:   path: 'dist-package'
@topkit/analytics-charts: }
@toptal/picasso-forms: error Command failed with exit code 1.
@toptal/picasso-forms: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR! yarn run build:package exited 1 in '@toptal/picasso-charts'
lerna WARN complete Waiting for 6 child processes to exit. CTRL-C to exit immediately.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Stephanie@DESKTOP-90ROKD9 MINGW64 /d/reactpicasso (master)
$`

Hey @stephyswe 👋  It's happening most likely because of your permissions for your folders. So it can't create dist-package folders inside each Picasso package. Try to configure your folder permissions and it should work for you 😃  Also, you have to have Docker installed and configured to be able to run visual tests in Docker image, but there is also an opportunity to run visual tests without Docker image, directly on your machine, however, generated visual snapshots can have differences from the ones committed to the repo.

Hey @stephyswe 👋 It's happening most likely because of your permissions for your folders. So it can't create dist-package folders inside each Picasso package. Try to configure your folder permissions and it should work for you 😃 Also, you have to have Docker installed and configured to be able to run visual tests in Docker image, but there is also an opportunity to run visual tests without Docker image, directly on your machine, however, generated visual snapshots can have differences from the ones committed to the repo.

Thanks so much! Do you know how to change permission ? Using Windows 10
Ive Docker installed! Need to look up how configure it to fit visual testing !

@stephyswe and are you using Linux subsystem (WSL)? or working directly on windows?

@stephyswe either way, as first I would try to create manually empty dist-package inside all packages. It solved the issue lately for someone.

@stephyswe It's a little hard to create the dist-package inside all packages.
I recommend you go to bin/build.js in picasso, and comment out lines 23 to 31, effectively commenting out the clean() function. Run the script again, and the folders should be created by themselves. After everything is set up, uncomment the code.
You'll not have this issue moving forward afterwards. 👍

Will be fixed with https://github.com/toptal/picasso/pull/2439

authors: TomasSlama denieler separatio stephyswe

repo: toptal/picasso

license: MIT


text:
feat(TopBar): add TopBarMenu and TopBarItem components

FX-3139
Description
Add support for centered menu links in TopBar. There is a new (internal) component PageHamburger and also two (public) components TopBarMenu and TopBarItem created.
PageHamburger also has context provided for the whole  so that it can detect whether there is content inside TopBar (center menu) or in Sidebar.
Figma designs
How to test

check temploy example
see happo changes

Screenshots

Development checks

[x] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Make sure that additions and changes on design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests

Breaking change

codemod is created and showcased in the changeset
test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers

closing in favor of #3217, #3218 and #3219

source: gharchive/pull-request


text:
User can upload to any collection from choosers

I have an installation with two collections:

Root
My awesome collection

I have a user with Editor role. Editor role have "Add" and "Edit" permission for "My awesome collection" collection and don't have any permissions for "Root" collection.
The user can upload image / document to "Root" collection from chooser.

Fixed in #2517

repo: torchbox/wagtail


text:
refactor: @toss/utils에서 제공해주는 유틸 함수로 대체하기

어떤 목적의 PR인가요?
emotion-utils 라는 패키지에서
const typeof window === 'undefined' && typeof global !== 'undefined';  로 서버인지 클라이언트인지 체크하는 변수를 선언하는 구문이 있습니다.
하지만 다른 라이브러리들을 살펴보면 @toss/utils 패키지를 워크스페이스 내부에서 사용하여서 isServer 함수를 제공받아서 사용하는것을 확인하였습니다.
같은 방법으로 리팩토링 해봤습니다!
===

[ ] Documentation update
[ ] Bug fix
[ ] New feature
[x] Refactor
[ ] Other :

내용을 설명해주세요
직접 선언되어있던 isServer 함수를,
@toss/utils 패키지에서 불러오도록 리팩토링 하였습니다.
체크리스트

[x] 아래 항목들을 모두 확인하였습니다.

PR 내용을 잘 설명하였습니다 : 넵!
문서화를 충분히 하였습니다 (필요시)
테스트가 충분히 작성되었습니다 (필요시)

Thx!

repo: toss/slash


text:
MD파일에 들어가는 요소들의 스타일을 TOML형식으로 정리하기

정리합니다.

https://github.com/tossicat/typecat/commit/9e59b644487a9ec3bddb4fe1436bcbc525afe1f9

repo: tossicat/typecat


text:
fix: JSON.parse accepting null

Please let me know if I missed anything in this.
Fixes: https://github.com/total-typescript/ts-reset/issues/173

Argument name should not change.

it should never have been called text or begin with. it's a value.

That is not a typescript issue.

For completeness and consistency, we should generalize to all valid JSON string producing text values.
parse<T extends boolean | number | bigint>(text: T, /*...*/): T
parse<T extends boolean | number | bigint | null>(text: T, /*...*/): unknown

repo: total-typescript/ts-reset


text:
🛑 MSP-HIT is down

In cb7de64, MSP-HIT (https://hit.hanati.co.kr/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-HIT is back up in f76b167 after 9 minutes.

repo: touguy/uptime


text:
🛑 PoE server is down

In 654c5b5, PoE server (https://poe.townway.com.tw/iota/message?messageID=42a2685d98d11bfb336d0928ce1e49cf3c85f5f2f075f5028fc1ea29497a1c67) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PoE server is back up in f2a1a46 after 12 minutes.

repo: towNingtek/upptime-monitor


text:
Add parameters for transform_video: start_sec & end_sec

Signed-off-by: Jael Gu mengjia.gu@zilliz.com

Codecov Report

Merging #1142 (edc3239) into main (4505778) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1142   +/-   ##
=======================================
  Coverage   65.97%   65.97%
=======================================
  Files         226      226
  Lines       10298    10298
  Branches     1731     1731
=======================================
  Hits         6794     6794
  Misses       3056     3056
  Partials      448      448

Impacted Files
Coverage Δ

towhee/models/utils/video_transforms.py
86.41% <100.00%> (ø)

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 4505778...edc3239. Read the comment docs.

/lgtm
/approve

authors: codecov-commenter jaelgu oneseer

repo: towhee-io/towhee


text:
add vit_pretrained.py and test_vit_pretrained.py

add vit_pretrained.py for loading pretrained transformer.
add ut for loading pretrained.

Codecov Report

Merging #97 (35fc225) into main (9debfd9) will increase coverage by 4.38%.
The diff coverage is 91.30%.

@@            Coverage Diff             @@
##             main      #97      +/-   ##
==========================================
+ Coverage   76.07%   80.46%   +4.38%
==========================================
  Files          51       57       +6
  Lines        1530     1863     +333
  Branches      143      163      +20
==========================================
+ Hits         1164     1499     +335
+ Misses        319      305      -14
- Partials       47       59      +12

Impacted Files
Coverage Δ

towhee/tests/trainer/test_vit_configs.py
75.00% <75.00%> (ø)

towhee/tests/trainer/test_vit_pretrained.py
84.61% <84.61%> (ø)

towhee/trainer/models/vit/vit_configs.py
100.00% <100.00%> (ø)

towhee/trainer/models/vit/vit_pretrained.py
100.00% <100.00%> (ø)

towhee/engine/engine.py
0.00% <0.00%> (ø)

towhee/dataframe/dataframe.py
83.90% <0.00%> (ø)

towhee/base_repr.py

towhee/tests/dag/test_base_repr.py
98.00% <0.00%> (ø)

towhee/tests/dag/test_operator_repr.py
93.75% <0.00%> (ø)

... and 10 more

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 9debfd9...35fc225. Read the comment docs.

authors: codecov-commenter oneseer


text:
Accessing attributes on a PlaneBufferGeometry?

I'm trying to access the attributes property of a PlaneBufferGeometry. What's the best way to do this?
With three.js, I can just do:
var planeGeometry = new THREE.PlaneGeometry(1, 1);
planeGeometry.attributes.uv.setXY(0, 1.0, 0.5);

Would it be best to add a ref, then update the attributes in componentDidMount?

I think so, but I will take a look to see if we can use props to do something like this

authors: kevinhikaruevans toxicFork

repo: toxicFork/react-three-renderer


text:
Exercise 4.8 A school adopt letter grade system from C to A+ as follows:

A school adopt letter grade system from C to A+ as follows:
letter_grades <- c("C", "B-", "B", "B+", "A-", "A", "A+")

However, when there is need to calulate GPA, they convert each letter grade to each value in the following numeric_grades vector:
numeric_grades <- c(2, 2.5, 3, 3.5, 4, 4.5, 5)

A student with the following letter grades need to convert them to numeric_grades:
studentGrades <- c('B','A','A+','B+','A-','B','B-','B','A+','B+','C','B-','B-','B','C','C','B+','B','B+','B')

He asked you for help. You layout the following programming plan:
studentLetterGrades <- {
  # Task map c("C", "B-", "B", "B+", "A-", "A", "A+") to c(2, 2.5, 3, 3.5, 4, 4.5, 5)

  # step1: for each grade in studentGrades find its position in c("C", "B-", "B", "B+", "A-", "A", "A+") so if studentGrades = c("C","A-"), step1 = c(1, 5) since c("C", "B-", "B", "B+", "A-", "A", "A+")[c(1, 5)] will give him "C", "A-"

  # step2: Use step1 result as position indices to retrieve from c(2, 2.5, 3, 3.5, 4, 4.5, 5). From previous example, step1=c(1, 5), then  c(2, 2.5, 3, 3.5, 4, 4.5, 5)[step1] will give him c(2, 4)

}

Complete the programming block.

https://github.com/raychiu135/110-1-r4ds-main/blob/52519c461799d4e40fb2fbc983d207bd713cc5e3/exercise_4.8.rmd#L2

https://github.com/Vincent23412/110-1-r4ds-main/blob/bd83d77d595817955b932658bc688552edf029f2/20211127.Rmd#L42

teacher, can you explain this exercise next week?

https://github.com/Jimmy885/110-1-r4ds-main/blob/c578bea448139461967067a4f75b1950c2b4d28e/4.8.rmd#L635

https://github.com/linttttt/110-1-r4ds-main/blob/a7e32a7334911a1117cad0cde2aed838ed825bb4/studyCH4(EX).Rmd#L43


text:
consider factoring out implicit sender validation to the top level main entry point

https://github.com/tqtezos/minter/blob/9bd894ec8c7a5a5a45d166f6b0c6b49c3810ddc7/contracts/ligo/src/english_auction_tez.mligo#L164
Check also all other functions called from english_auction_tez_main

Closed by https://github.com/tqtezos/minter/commit/4490a239187cd8a8babee7f6d7cac6cf57d89337

authors: EGuenz emishur

repo: tqtezos/minter


text:
ユーザーアイコンスタンプをスタンプピッカーで選べるように

カテゴリのアイコンがないですが…
よろしくお願いします

メッセージに押すスタンプの場合のスタンプピッカーはどうなりますか

あーそこでstamp id使いますね…
スタンプピッカーのmemberをメッセージの場合だけ無効化するのとサーバー側にAPIを生やすのどっちがいいでしょう？

現在のスタンプの仕様だと、サーバー側にAPIを生やすのはしんどいと思います。
ユーザーアイコンをスタンプとして登録しないといけないので。

メッセージの場合は無効化するようにしました

アイコンつくりました

これもドラフトはずしました

authors: sapphi-red wtks

repo: traPtitech/traQ-UI


text:
Add support for datadog span types

This adds support for datadog's built in type.
See https://docs.datadoghq.com/tracing/guide/send_traces_to_agent_by_api/
These correspond to

@xeinherjar thanks for the contribution. This will be released tonight as a part of v0.13.0

authors: catostrophe xeinherjar


text:
Update CHANGELOG.md

fixed typo

This is an auto generated file and isn't needed any fixes.

repo: traceloop/openllmetry


text:
🛑 Immich is down

In c3924d9, Immich (https://photos.$DOMAIN2) was down:

HTTP code: 502
Response time: 536 ms

Resolved: Immich is back up in 63ae5fa after 9 minutes.

repo: traktuner/status


text:
MB-15974: update storybook dependencies

JIRA Ticket: MB-15974
Jira ticket
Summary
Upgrading storybook dependencies that should be updated at the same time. Replaces #10781 (no other ones have been opened by dependabot yet).
Most of the changes were related to Vue 3, Nextjs, and a CI workflow, so it seems like it should be fine.
One nice update is from the happo-plugin-storybook package, which now allows us to configure a timeout when waiting for interactive events. I vaguely recall there maybe being times we've had problems with flaky happo diffs due to interactivity. See changelog below for details.
Release Notes & Changelog
Main storybook packages

Release notes
Sourced from storybook's releases.

v7.0.18
Bug Fixes

Vue3: Fix TS 5.0 compat with vue-component-type-helpers #22814
Vue3: Fix reactive args updates in decorators #22717
Vue3: Revert v7 breaking change, restore reactive v6-compat API #22692

Build

Build: Add more checks to ci:daily workflow #22815
Build: Fix Nextjs E2E tests #22816
Build: Bring back new Vue3 tests to main #22685

Changelog
Sourced from storybook's changelog.

7.0.18 (May 26, 2023)
Bug Fixes

Vue3: Fix TS 5.0 compat with vue-component-type-helpers #22814
Vue3: Fix reactive args updates in decorators #22717
Vue3: Revert v7 breaking change, restore reactive v6-compat API #22692

Build

Build: Add more checks to ci:daily workflow #22815
Build: Fix Nextjs E2E tests #22816
Build: Bring back new Vue3 tests to main #22685

Commits

8edc254 v7.0.18
5ba99c4 Update git head to 7.0.17, update yarn.lock [ci skip]
See full diff in compare view

happo-plugin-storybook
From https://github.com/happo/happo-plugin-storybook/releases/tag/v3.3.0
This minor release adds a way to configure the timeout used when waiting for interactive events happening as part of rendering a story. To set it, use the setRenderTimeoutMs function exported by happo-plugin-storybook/register:
import { setRenderTimeoutMs } from 'happo-plugin-storybook/register';

setRenderTimeoutMs(5000);

The default timeout is 2000ms/2s.

Messages

:book:
:link: MB-15974

  Generated by :no_entry_sign: dangerJS against cbb2fc2ac3812d0b69665e3229f052cd26fbbdc8

authors: felipe-lee robot-mymove

repo: transcom/mymove


text:
MB-4141 Return error if missing MTO id

Description
The story MB-4141 is about handling various error states for payment request creation. This PR covers MB-5344 when the MTO Id is uuid.Nil aka all zeros. If it is this will return a InvalidCreateInputError
Reviewer Notes
Is InvalidCreateInputError appropriate, or would BadDataError or InvalidInputError be more appropriate here. I'm going with InvalidCreateInputError because MTO Id is user input (from the prime) and this is being checked on create.
Setup
Setup server
make db_dev_e2e_populate
make server_run

Save this json to a payload.json
{
  "body": {
    "isFinal": false,
    "moveTaskOrderID": "00000000-0000-0000-0000-000000000000",
    "serviceItems": [
      {
        "id": "94bc8b44-fefe-469f-83a0-39b1e31116fb"
      },
      {
        "id": "eee4b555-2475-4e67-a5b8-102f28d950f8"
      },
      {
        "id": "6431e3e2-4ee4-41b5-b226-393f9133eb6c"
      },
      {
        "id": "fd6741a5-a92c-44d5-8303-1d7f5e60afbf"
      }
    ]
  }
}

Try to create a new payment request see the error
prime-api-client --insecure create-payment-request --filename payload.json | jq
{
  "Payload": {
    "detail": "Invalid Create Input Error: MoveTaskOrderID is required on PaymentRequest create",
    "instance": "689f5fb5-d73e-4d60-9fd9-6700135e0107",
    "title": "Validation Error",
    "invalidFields": null
  }
}

Validate handler returns correct error a 422 Unprocessable Entity:
❯ prime-api-client --insecure create-payment-request --filename tmp/payloads/local_create_payment_request.json -v
POST /prime/v1/payment-requests HTTP/1.1
Host: primelocal:9443
User-Agent: Go-http-client/1.1
Content-Length: 332
Accept: application/json
Content-Type: application/json
Accept-Encoding: gzip

{"isFinal":false,"moveTaskOrderID":"00000000-0000-0000-0000-000000000000","serviceItems":[{"id":"94bc8b44-fefe-469f-83a0-39b1e31116fb","params":null},{"id":"eee4b555-2475-4e67-a5b8-102f28d950f8","params":null},{"id":"6431e3e2-4ee4-41b5-b226-393f9133eb6c","params":null},{"id":"fd6741a5-a92c-44d5-8303-1d7f5e60afbf","params":null}]}

HTTP/1.1 422 Unprocessable Entity
Content-Length: 192
Cache-Control: no-cache, no-store, must-revalidate
Content-Security-Policy: frame-ancestors 'none'
Content-Type: application/json
Date: Tue, 10 Nov 2020 17:05:50 GMT
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: deny
X-Xss-Protection: 1; mode=block

{"detail":"Invalid Create Input Error: MoveTaskOrderID is required on PaymentRequest create","instance":"646c5b61-5db4-4c53-8e30-da5c3858e1ea","title":"Validation Error","invalidFields":null}

{"Payload":{"detail":"Invalid Create Input Error: MoveTaskOrderID is required on PaymentRequest create","instance":"646c5b61-5db4-4c53-8e30-da5c3858e1ea","title":"Validation Error","detail":"Invalid Create Input Error: MoveTaskOrderID is required on PaymentRequest create","instance":"646c5b61-5db4-4c53-8e30-da5c3858e1ea","invalidFields":null,"title":"Validation Error","invalidFields":null}}%

Code Review Verification Steps

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

References

Jira story for this change
Jira subtask for this change

Messages

:book:
:link: MB-4141

  Generated by :no_entry_sign: dangerJS against ab76d0bb1f7cc6119b7c503a5ab548d4203f8930

As long as the response is 422 Unprocessable Entity I think it's okay to use whatever underlying error best fits.

authors: gidjin robot-mymove shimonacarvalho


text:
Refactor ParamsPricer interface to return pricer-based parameters

Description
This PR refactors our current ParamsPricer interface (and other related methods/functions) to return pricer-based parameters.
Reviewer Notes
TBD
Setup
TBD
Code Review Verification Steps

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
[ ] 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
The technical design doc explains more about the approach used.

Warnings

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

  Generated by :no_entry_sign: dangerJS against fa804f0099941dcd6b06ea1212688082953eba40

authors: reggieriser robot-mymove


text:
🛑 TechinAsia is down

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

HTTP code: 403
Response time: 995 ms

Resolved: TechinAsia is back up in ac6f6d8 after 10 minutes.

repo: traqy/upptime


text:
🛑 TechinAsia_Laravel_API is down

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

HTTP code: 403
Response time: 171 ms

Resolved: TechinAsia_Laravel_API is back up in 28ec2a3 after 1 minute.


text:
🛑 TechinAsia is down

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

HTTP code: 403
Response time: 1008 ms

Resolved: TechinAsia is back up in 7972bd8 after 9 minutes.


text:
Ruby 2.3.3 doesn't work in non-travis environment

Is rubies binaries on http://rubies.travis-ci.org/, supposed to work in non-travis environment?
Since 2.3.x and 2.4.x versions for OSX 10.12 (at least) do not work, showing me:
dyld: Library not loaded: /Users/travis/.rvm/rubies/ruby-2.3.2/lib/libruby.2.3.0.dylib
  Referenced from: <removed>
  Reason: image not found

Not sure if this issue belongs to this repo, so apologies if that the case

If working (from http://rubies.travis-ci.org/usage) with rvm –
$ rvm reinstall ruby-head --binary
...
ruby-head - #validate archive
ruby-head - #extract
ruby-head - #validate binary
Libraries missing for ruby-head: /Users/travis/.rvm/rubies/ruby-head/lib/libruby.2.4.0.dylib. Refer to your system manual for installing libraries
Mounting remote ruby failed with status 10, stopping installation.

Same story with 2.1.x, different with 2.2.x - https://github.com/travis-ci/worker/issues/234

Same with #234. This is not the right repository.
Probably the same as https://github.com/travis-ci/travis-rubies/issues/26.

authors: BanzaiMan markelog

repo: travis-ci/worker


text:
Update sbt-scoverage to 2.0.9

About this PR
📦 Updates org.scoverage:sbt-scoverage from 1.9.1 to 2.0.9 ⚠
📜 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.scoverage", artifactId = "sbt-scoverage" } ]

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

labels: sbt-plugin-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #193.

repo: travisbrown/iteratee-twitter


text:
Query __args that are Integer value are not converting into integer

Scenarios: lets say we got query like this:

{
users (first: 1000, where: {showInFrontend: true}) {  // first : 1000 is an integer value
edges {
node {
databaseId
}
}
}
}

the resulting argument object becomes:
args { first: '1000', where: { showInFrontend: true } } // this is incorrect as its meant to be IntValue
I did a modification to your code locally for now to fix it. The Fix:
In your getArguments and getArgumentObject function you also want to check the kind for IntValue like this eg in your getArguments function :
} else if (arg.value.kind === 'IntValue') {  argsObj[arg.name.value] = parseInt(arg.value.value); {
I can do a PR if you want. Also thanks saved me hours of work trying to convert to Json 👍

This is a great suggestion, thank you for this @BhupenT ! Could you open a pull request for it with an added unit test?
Do you know how the behaviour would be for other types, let's say floats - could you implement these number types as well? Would booleans work already?
Thank you!

Thanks for raising this issue @BhupenT 👍🏼
I agree with @rickschubert here! If you could raise a PR, that'd be great along with unit test coverage for your changes.
Great question @rickschubert, what will happen with floats and booleans etc

Sure thanks @rickschubert, I will do a PR sometime by tomorrow. Boolean works fine as selectionSet value must be true or false without quote. Haven’t tested with floats. We do need to support all the AST kinds if DocumentNode of that value is set as string type. Eg. value: ‘123.45’

@BhupenT I was wondering if you were still happy to take on this issue? We'd love to see a solution for it 🙏🏼 Let us know if there's anything we can do to assist 🤝

Hey @BhupenT, it's been a while since we heard from you.
Are you still interested in providing a PR to fix this issue?
We would love to support you in getting this fixed, if not - don't worry we can look into it 👍🏼

Hi @thomaschaplin and @rickschubert. Thanks a lot guys. Sorry that i am late to the party, been busy and had to quickly do things on some project which had to work on so din't had time. I also found few other features that may be a good idea to add here. I just forked and put it there which i can create a PR if this is something that may interest you guys.

Support for inline fragments ( using __on similar to how Json to gqlQuery does )
Support for alias based query (using __aliasFor similar to Json to gqlQuery does
So it can be used with the combination for JSON->Query and Query->Json

Here is the forked one which i just added a commit that i had implemented ages ago which i think its good to share it with you guys. Commit changes view here
Once again Thanks you all.

Hi @thomaschaplin and @rickschubert. Thanks a lot guys. Sorry that i am late to the party, been busy and had to quickly do things on some project which had to work on so din't had time. I also found few other features that may be a good idea to add here. I just forked and put it there which i can create a PR if this is something that may interest you guys.

Support for inline fragments ( using __on similar to how Json to gqlQuery does )
Support for alias based query (using __aliasFor similar to Json to gqlQuery does
So it can be used with the combination for JSON->Query and Query->Json

Here is the forked one which i just added a commit that i had implemented ages ago which i think its good to share it with you guys. Commit changes view here
Once again Thank you all.

Thanks @BhupenT - I've created an issue for this to be looked into. We may get in touch to discuss it with you further.
Thanks again

@BhupenT @thomaschaplin Hi, just checking if we are currently supporting inline fragments query to be converted to json? if not, can you please suggest how we can convert it using any other method?

@harmeetsingh17 Checked this open PR if it does what you need? https://github.com/trayio/graphql-query-to-json/pull/23

authors: BhupenT VincentSC harmeetsingh17 rickschubert thomaschaplin

repo: trayio/graphql-query-to-json


text:
Top level I/O: vanished input

This is something odd which I do not understand at all. The same does not happen on ECLiPSe, GNU, Scryer, SICStus, SWI, YAP, XSB. It does happen on B, though.
The idea is to copy-paste the text
[user].
faktum(1).

directly into the toplevel. In most of the systems, what happens is that one sees that very text and so one issues Cntr-d and this very fact is defined.
However, in Trealla (and B), one only sees [user]. but not the text thereafter. Still, this fact will be defined.
ulrich@p0:/opt/gupu/trealla$ cat /tmp/feil
[user].
faktum(1).
ulrich@p0:/opt/gupu/trealla$ ./tpl -f
?- [user].
faktum(2).
   true.
?- faktum(L).
   L = 1
;  L = 2.

So here, I pasted the entire text including faktum(1). but it does not show. Therefore I added another fact faktum(2). and both are now defined...

today, I've seen this, too.
but I get a syntax error:
v1.22.0-1-g3cf9c
?- [user].
faktum(1).
Error: syntax error, mismatched parens/brackets/braces, line 1 ''

and also without any parens:
?- [user].
faktum.
Error: syntax error, mismatched parens/brackets/braces, line 1 ''

Looks like it has something to do with the newline [user].<nl>
% [user].<nl> pasted,
$ [user].

f.
Error: syntax error, mismatched parens/brackets/braces, line 1 ''

In the cut/paste source there is nothing hidden
$ od -cx txt
0000000   [   u   s   e   r   ]   .  \n   f   a   k   t   u   m   (   1
           755b    6573    5d72    0a2e    6166    746b    6d75    3128
0000020   )   .  \n
           2e29    000a
0000023

This is a bit tricky.
cut/paste [user].<nl>
$ [user].

press <return> here and then enter a dot<ret>

?- [user].

.
Error: syntax error, operator expected '.', line 1, '.
'
Segmentation fault (core dumped)

These are all manifestations of the top-level input mechanism not going
through read_term. You can see the same with
?- true. true.
So currently you can only have one statement per input.
On Sun, Feb 6, 2022 at 6:57 AM UWN @.***> wrote:

This is something odd which I do not understand at all. The same does not
happen on ECLiPSe, GNU, Scryer, SICStus, SWI, YAP, XSB. It does happen on
B, though.
The idea is to copy-paste the text
[user].
faktum(1).
directly into the toplevel. In most of the systems, what happens is that
one sees that very text and so one issues Cntr-d and this very fact is
defined.
However, in Trealla (and B), one only sees [user]. but not the text
thereafter. Still, this fact will be defined.
@.:/opt/gupu/trealla$ cat /tmp/feil
[user].
faktum(1).
@.:/opt/gupu/trealla$ ./tpl -f
?- [user].
faktum(2).
true.
?- faktum(L).
L = 1
;  L = 2.
So here, I pasted the entire text including faktum(1). but it does not
show. Therefore I added another fact faktum(2). and both are now
defined...
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/441, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEV6CHKFHW3YDHTPQH3UZWFMLANCNFSM5NUNU2ZQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

one statement per input:
?- [user].
f.
.
Error: syntax error, operator expected '.', line 2, '.
'
Segmentation fault (core dumped)

Can't see that. How did you do it? Paste or type...
On Sun, Feb 6, 2022 at 12:56 PM flexoron @.***> wrote:

one statement per input:
?- [user].
f.
..
Error: syntax error, operator expected '.', line 2, '.
'
Segmentation fault (core dumped)
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/441#issuecomment-1030740524,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSETM3NBUIMTBYPYZOKTUZXPL7ANCNFSM5NUNU2ZQ
.
You are receiving this because you commented.Message ID:
@.***>

typed
$ tpl -v
Trealla Prolog (c) Infradig 2020-2022, v1.22.2
(build with make debug)

debugger tells me
void xref_rule(module *m, clause *r, predicate *parent)
        :
	for (pl_idx_t i = 0; i < head->nbr_cells; i++, c++) {
		if (!is_variable(c))   <--
        :

there is no difference:
$ make clean
$ git pull
Already up to date.
$ make
:
$ ./tpl -v
Trealla Prolog (c) Infradig 2020-2022, v1.22.2
./tpl
?- [user].
f.
.
Error: syntax error, operator expected '.', line 2, '.
'
Segmentation fault (core dumped)

holla, die waldfee % sorry for this germanic saying :-)
?- [user].
f,
^D
Error: syntax error, incomplete statement, line 2 'f,
'
Error: syntax error, incomplete statement, line 3 'f,
'
Error: syntax error, incomplete statement, line 4 'f,
'
Error: syntax error, incomplete statement, line 5 'f,
'
Error: syntax error, incomplete statement, line 6 'f,
'
Error: syntax error, incomplete statement, line 7 'f,
'
Error: syntax error, incomplete statement, line 8 'f,
'
   true.

Are you on devel branch?
On Sun, Feb 6, 2022 at 1:54 PM flexoron @.***> wrote:

there is no difference:
$ make clean
$ git pull
Already up to date.
$ make
:
$ ./tpl -v
Trealla Prolog (c) Infradig 2020-2022, v1.22.2
./tpl
?- [user].
f.
..
Error: syntax error, operator expected '.', line 2, '.
'
Segmentation fault (core dumped)
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/441#issuecomment-1030746310,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSESYMMSPMXKE3TDZYPTUZXWIHANCNFSM5NUNU2ZQ
.
You are receiving this because you commented.Message ID:
@.***>

$ git branch -a
* devel
  main
  remotes/origin/HEAD -> origin/main
  remotes/origin/devel
  remotes/origin/gh-pages
  remotes/origin/main
  remotes/origin/testing

$ make clean
$ git pull
$ make
$ ./tpl -v
Trealla Prolog (c) Infradig 2020-2022, v1.22.2-15-ga4c4f0
$ ./tpl
?- [user].
f,
Error: syntax error, incomplete statement, line 2 'f,
'
   true.

v1.22.3 ok

hmm, not ok
$ ./tpl
?- [user].

.
Error: syntax error, operator expected '.', line 2, '.
'
Segmentation fault (core dumped)

Not seeing a crash, but i will look deeper.
On Sun, Feb 6, 2022 at 3:26 PM flexoron @.***> wrote:

hmm, not ok
$ ./tpl
?- [user].
..
Error: syntax error, operator expected '.', line 2, '.
'
Segmentation fault (core dumped)
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/441#issuecomment-1030755357,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEVZ3FIF6LDAY5OBSPDUZYBBDANCNFSM5NUNU2ZQ
.
You are receiving this because you commented.Message ID:
@.***>

Valgrind shows nothing unusual.
On Sun, Feb 6, 2022 at 3:26 PM flexoron @.***> wrote:

hmm, not ok
$ ./tpl
?- [user].
..
Error: syntax error, operator expected '.', line 2, '.
'
Segmentation fault (core dumped)
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/441#issuecomment-1030755357,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEVZ3FIF6LDAY5OBSPDUZYBBDANCNFSM5NUNU2ZQ
.
You are receiving this because you commented.Message ID:
@.***>

it is a new git clone.
$ git clone https://github.com/trealla-prolog/trealla.git && cd trealla
$ make
$ make clean
$ make debug # does not complain: src/imath/imath.c:1702:51: warning: unused parameter
$ ./tpl
?- [user].
.
Error: syntax error, operator expected '.', line 2, '.
'
Segmentation fault (core dumped)

debugger stopped here again:
void xref_rule(module *m, clause *r, predicate *parent)
        :
	for (pl_idx_t i = 0; i < head->nbr_cells; i++, c++) {
		if (!is_variable(c))   <--
        :

#0  xref_rule(m = 0x5555556780e0, r = 0x5555558b4e00, parent = 0x0) at src/module.c:1062
#1  tokenize(p = 0x5555558b3130, args = false, consing = false) at src/parser.c:2501
#2  load_fp(m = 0x5555556780e0, fp = 0x7ffff7a86800 <_IO_2_1_stdin_>, filename = 0x5555558b3110 "user_1\\n", including = false) at src/module.c:1312
#3  load_file(m = 0x5555556780e0, filename = 0x5555558b3110 "user_1\\n", including = false) at src/module.c:1386
#4  consultall(q = 0x555555876300, l = 0x555555875970, l_ctx = 0) at src/query.c:1701
#5  start(q = 0x555555876300) at src/query.c:1788
#6  execute(q = 0x555555876300, cells = 0x555555875970, nbr_vars = 0) at src/query.c:1889
#7  run(p = 0x555555873c80, pSrc = 0x555555873bc0 "[user].", dump = true) at src/parser.c:2994
#8  pl_eval(pl = 0x7ffff729c010, s = 0x555555873bc0 "[user].") at src/prolog.c:133
#9  main(ac = 1, av = 0x7fffffffe528) at tpl.c:313

Valgrind? what is this?
I do not use tools like that!

The gap is between readline() and getline()
To make it visible, you can change /etc/inputrc.
# Assuming that no $HOME/.inputrc exist!
# The "readline programm name" of tpl is "other".

# readline() initialization file
$ vi /etc/inputrc
:
$if other
set editing-mode vi
set keymap vi
set show-mode-in-prompt on
$endif
:

$ ./tpl
(ins)?-   % prompt shows vi mode (ins) + prolog prompt

(ins)?- [user].^Ma.^Mb.^Mc.^M
^D
   true.
(ins)?- listing.
a.
b.
c.
   true.

a.^Mb.^Mc.^M <-- this is kinda paste simulation, getline() reads the buffer.

Not sure but I guess "echo input characters" is turned on delayed.

Hint: You cannot paste this, it must be entered like so: (in vi mode ^V is not visible)
[user].^V^Ma.^V^Mb.^V^Mc.^V^M<return>^D

authors: UWN flexoron infradig

repo: trealla-prolog/trealla


text:
Create SECURITY.md

Adding a SECURITY.md to the reepository.

Adding a Security policy to OSS repository is out of scope. Closing this PR.

repo: treasure-data/digdag


text:
Feature Request: Add rebase option for branches

Merging branches and resolving merge conflicts can be very difficult, It would be awesome if we have a release option also available.
Maybe we can choose a default option at the repository level?
This somehow ties to integration with git, but I believe is a good feature on its own.

Hi @mishraprafful, first of all thanks!
I have some follow-up questions in order to see I fully understand your suggestion.

What do you mean by "release option"? rebase option maybe? :)
Do you think adding “ours” or “theirs” strategy options to lakeFS merge functionality will help solve the difficulties you encountered? Something like lakectl merge --strategy=theirs

My 2 agoroth: Some people hate rebases,  some love them. Git offers both,  and the Git* tools also offer them (e.g. GitHub offers rebase-and-merge as a way to pull PRs). People hate rebases because they rewrite commit histories. People (myself included...) love rebases because they rewrite commit histories and allow you to fix things after the fact.
I think we should be unopinionated here and offer rebases. Clearly workarounds exist, and equally clearly they are not as good for the people who want the actual feature.
Also, some of the issues with rebases vanish with lakeFS, because it is not a distributed view.

Hi @lynnro314

yes, I think that was a typo from my end, I meant rebase option.
I think that would help us for sure. 👍🏻

Also, thanks for your inputs @arielshaqed I think I completed agree with you.

@mishraprafful
With rebase we diff each commit with the base branch and effectively rebasing each commit separately, so we'll need to resolve conflicts (if there are any) with every commit.
With that in mind, I would love to hear about your requirements for the rebase feature.
Do you thinks adding strategy options to lakeFS merge functionality will be enough (at this point) to solve the difficulties of resolving conflicts? Or the rebase feature is important regardless of resolving conflicts?

@lynnro314 I think adding strategy options with merge works for us. I understand that having rebase adds more complexities in terms of resolving conflicts.
With the rebase, we would preserve all the commits that are added to the branch, and we wish to be able to revert to specific commits on the branches as well without having to keep the branches alive. So with rebase, we would be able to have all the effective versions of data on the main branch itself (i.e without losing individual commits on a branch, which we would if using merge to main)
However, once the rebase feature is rolled out we would use that instead of merge. But for now, having strategy options with merge works 🎉

@mishraprafful Thanks for your answers!
With respect to this I opened a new issue regarding the merge strategies.

authors: arielshaqed lynnro314 mishraprafful

repo: treeverse/lakeFS


text:
Add ttl to dns replies

Pull request
Description
Add a ttl field to the dns sink
Related

Related docs PR

Checklist

[x] The RFC, if required, has been submitted and approved
[x] Any user-facing impact of the changes is reflected in docs.tremor.rs
[x] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[x] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[x] The performance impact of the change is measured (see below)

Performance
Sink only changes

Coverage remained the same at 83.387% when pulling cc36cfb913a7b806b57625aa7237be096389392f on dns-ttl into cd64ed3494173de8754097cbb2bbb13755f57600 on main.

authors: Licenser coveralls

repo: tremor-rs/tremor-runtime


text:
Handle react 404 page not found error and display the 404 Page

If route is not present in routes and no component is assigned to that route display a component which will say this route is not present and it should be beasutiful

@trickster26  Done in branch random_url_page_breakdown. Kindly review and merge.

Working but routes like admin/dashboard/abc or admin/fgh not working but i dont think this is important


text:
feat(app-bar): Add prominent property

Closes #789

Merging after #810

repo: trimox/angular-mdc-web