Why BOT responses are blanks?

When I run following, Why do I get blank responses from Bot.
(my_env) ubuntu@ip-172-31-16-139:~/chatbot/annbot$ python3 chatbot.py --mode chat
Preparing data to be model-ready ...
Data ready!
Initialize new model
Create placeholders
Create inference
Creating loss...
It might take a couple of minutes depending on how many buckets you have.
WARNING:tensorflow:From /home/ubuntu/anaconda3/envs/my_env/lib/python3.6/site-packages/tensorflow/python/ops/nn_impl.py:1310: softmax_cross_entropy_with_logits (from tensorflow.python.ops.nn_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Future major versions of TensorFlow will allow gradients to flow
into the labels input on backprop by default.
See tf.nn.softmax_cross_entropy_with_logits_v2.
Time: 27.975615978240967
Create optimizer...
It might take a couple of minutes depending on how many buckets you have.
Loading parameters for the Chatbot
Welcome to TensorBro. Say something. Enter to exit. Max length is 60

hi
[[-0.584015    6.833303   -0.7068891  ... -0.23560944 -0.49890977
-0.4948687 ]]
.
hello
[[-0.58008343  7.1182957  -0.69766235 ... -0.22473697 -0.4460981
-0.4717362 ]]
?
Hello
[[-0.58008343  7.1182957  -0.69766235 ... -0.22473697 -0.4460981
-0.4717362 ]]
?
How are you?
[[-0.45013425  6.5066013  -0.71693504 ... -0.17606334 -0.6236066
-0.541961  ]]
.

==================================================================
Also Why output_convo.txt BOT responses are blanks?
(my_env) ubuntu@ip-172-31-16-139:~/chatbot/annbot/processed$ nano output_convo.txt
HUMAN ++++ hi
BOT ++++ .
HUMAN ++++ hello
BOT ++++ ?
HUMAN ++++ Hello
BOT ++++ ?
HUMAN ++++ How are you?
BOT ++++ .
=============================================

I have met the same issue with you.The test loss is high. Did you solve the issue?

No yet.

train it more

How long we need to iterate? I have gone for more than 14000 iterations in 10 hours.
Is not enough?

enough is when you satisfied with output.   sometimes something is wrong and training not going well.
you need to play with your data and settings. chose smaller params first then move to bigger ones to see do it works at all

I trained it for 73000 iterations but still i am getting same results like ? and .

this is settings in my config.py  last iteration is 62800
BUCKETS = [(16, 19)]

NUM_LAYERS = 3
HIDDEN_SIZE = 256
BATCH_SIZE = 64

LR = 0.5
MAX_GRAD_NORM = 5.0

and result
> i dont know agent unk
[[ -0.58301872  10.56363678  -0.75994956 ...,  -0.98926491  -1.0604918
   -0.550138  ]]
oh , yeah .
> yeah
[[-0.48157236  9.12944603 -0.45098591 ..., -0.6943714  -0.65536427
  -0.37269545]]
.
> stop doting
[[ -0.68257785  11.46051979  -0.91514087 ...,  -0.51534909  -0.68435407
   -0.14121974]]
- -
> no and stripes i dont like even
[[-0.30254534  7.19619989 -0.30324209 ..., -0.46949279 -0.61815649
  -0.2052134 ]]
you ' re lying .
> no i not
[[ -0.74903452  10.35870457  -0.86198902 ...,  -0.66905749  -0.53297275
   -0.56081152]]
nothing .
> philosophy
[[ -0.57804114  11.67677402  -0.7756232  ...,  -0.4330861   -0.4938038
   -0.44071352]]
.
> how much legs cat hawe ?
[[-0.41352031  8.16804886 -0.73054808 ..., -0.73398674 -0.83470362
  -0.72415113]]
with the <unk> .
> yeah
[[-0.48157236  9.12944603 -0.45098591 ..., -0.6943714  -0.65536427
  -0.37269545]]
.
> tell me
[[-0.63063455  6.57353258 -0.46259886 ..., -0.70763153 -0.37358218
  -0.24181336]]
don ' t you tell me about it .
> no i dont know it
[[ -0.61053139  10.25772285  -0.99005854 ...,  -0.82599133  -1.04334843
   -0.67073309]]
and you do everything .
> no i dont do everything
[[-0.81464332  8.16336727 -1.04276168 ..., -0.75862557 -1.03167498
  -1.02897918]]
that ' s all .
> ok
[[-0.617365    9.04081535 -0.75897199 ..., -0.75397456 -0.4791148
  -0.37771353]]
don ' t have much .
> bye
[[-0.46397874  8.31635571 -0.79642689 ..., -0.59941679 -0.60873872
  -0.34941944]]
you ' re not in the mood .
>

What is the test loss? @MartinAbilev

~/dev/tenzorflow-chat-testdrive$ python chatbot.py
Data ready!
Bucketing conversation number 9999
Bucketing conversation number 19999
Bucketing conversation number 9999
Bucketing conversation number 19999
Bucketing conversation number 29999
Bucketing conversation number 39999
Bucketing conversation number 49999
Bucketing conversation number 59999
Bucketing conversation number 69999
Bucketing conversation number 79999
Bucketing conversation number 89999
Bucketing conversation number 99999
Bucketing conversation number 109999
Bucketing conversation number 119999
Bucketing conversation number 129999
Bucketing conversation number 139999
Bucketing conversation number 149999
Bucketing conversation number 159999
Bucketing conversation number 169999
Bucketing conversation number 179999
Bucketing conversation number 189999
Number of samples in each bucket:
 [103198]
Bucket scale:
 [1.0]
Initialize new model
Create placeholders
Create inference
Creating loss...
It might take a couple of minutes depending on how many buckets you have.
Time: 2.9458863735198975
Create optimizer...
It might take a couple of minutes depending on how many buckets you have.
Creating opt for bucket 0 took 6.980544805526733 seconds
Running session
Loading parameters for the Chatbot
Iter 62900: loss 1.7389020776748658, time 1.6152856349945068
Iter 63000: loss 1.713471269607544, time 1.4531621932983398
Test bucket 0: loss 3.626643180847168, time 2.8442370891571045

she is fun as ever :D
Running session
Loading parameters for the Chatbot
Iter 62900: loss 1.7389020776748658, time 1.6152856349945068
Iter 63000: loss 1.713471269607544, time 1.4531621932983398
Test bucket 0: loss 3.626643180847168, time 2.8442370891571045
Iter 63100: loss 1.7354186856746674, time 1.5451974868774414
Iter 63200: loss 1.7274975204467773, time 1.4273159503936768
Iter 63300: loss 1.7350391232967377, time 1.4423978328704834
^CTraceback (most recent call last):
  File "chatbot.py", line 262, in <module>
    main()
  File "chatbot.py", line 257, in main
    train()
  File "chatbot.py", line 156, in train
    _, step_loss, _ = run_step(sess, model, encoder_inputs, decoder_inputs, decoder_masks, bucket_id, False)
  File "chatbot.py", line 82, in run_step
    outputs = sess.run(output_feed, input_feed)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 889, in run
    run_metadata_ptr)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1120, in _run
    feed_dict_tensor, options, run_metadata)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1317, in _do_run
    options, run_metadata)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1323, in _do_call
    return fn(*args)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1302, in _run_fn
    status, run_metadata)
KeyboardInterrupt
~/dev/tenzorflow-chat-testdrive$ python3 chatbot.py --mode chat
Data ready!
Initialize new model
Create placeholders
Create inference
Creating loss...
It might take a couple of minutes depending on how many buckets you have.
Time: 2.344371795654297
Create optimizer...
It might take a couple of minutes depending on how many buckets you have.
Loading parameters for the Chatbot
Welcome to TensorBro. Say something. Enter to exit. Max length is 16
> hello
[[ -0.42601886  11.76952934  -0.96129787 ...,  -0.38945305  -0.63972712
   -0.52184105]]
come on .
> why you want me to do this ?
[[-0.84985662  7.54191875 -0.66726327 ..., -0.46486002 -0.69005805
  -0.38926086]]
throw me a little while .
> i trow some chocolate to you
[[-0.63454562  7.31223917 -0.68008763 ..., -0.3172918  -0.62918943
  -0.36875695]]
i ' m serious .
> me to !
[[ -1.19059336  10.17427731  -1.53483987 ...,  -0.87535918  -1.28455663
   -0.89420712]]
way to my room !
> ohh no
[[-0.62382394  8.92223644 -0.51953173 ..., -0.67145741 -0.60165089
  -0.46206495]]
no .
> i don`t want to get to bed with you now .
[[-0.61282045  7.70583582 -0.86621624 ..., -1.14901936 -1.03707504
  -0.30115816]]
where ' s the money ?
> i don`t tell you !
[[-0.9617241   9.48097229 -1.16938531 ..., -0.74119282 -1.03512502
  -0.71569276]]
what ?
> nothing
[[ -0.5954656   11.44416332  -0.8853721  ...,  -0.87170106  -0.29809356
   -0.50806785]]
- -
> bye
[[-0.35947308  7.6860323  -0.81516069 ..., -0.51186019 -0.61428398
  -0.26302782]]
i need to be .
> me too
[[-0.63649333  8.02639294 -1.06983578 ..., -0.93391991 -0.56139541
  -0.53440243]]
don ' t you ' re going to be here .
> no i go away. i go home .
[[-0.90490222  9.08857822 -0.83062935 ..., -0.40304869 -1.07223058
  -1.00504088]]
you will not . . . but you are .
> i am same as you
[[-1.13782763  8.06291008 -1.10772276 ..., -0.78122187 -1.07012486
  -0.79459012]]
if you please leave .
> yes i leave. bye.
[[-0.99189955  9.18696594 -0.97211885 ..., -0.34530568 -1.24671197
  -0.69110519]]
good .
>

i even have the same setting in config.py as your and my last iteration was 67100, but still only exclaimations and dots!!!
@MartinAbilev

something is wrong looks like with code or training data. it is hard to tell what exactly. you can create repo with your code and drop link.

or you can check my copy and compare with you code.. it is public.

No I didn't @EthanPhan!!

Ok. I'm gonna check MartinAbilev's code out and see if it works and see what is the difference. I'll update if I find any.

Unfortunately I have the same blank results. Something isn't working right with the code out of the box. Adjusting parameters made it worse.

I also have that problem. Is there any practical solution?

If you're not wed to using this particular model, this one works better than any other I've seen out in the open: https://github.com/pender/chatbot-rnn
It can be insulting though, as it was trained on reddit data, so be forewarned.

@J-Fo-S thank you for sharing the link. Is this your project?

You're welcome but no, it is not my project.

Is it related to the number of buckets?

@MartinAbilev
Hello，so your final result of loss is around 1.7？Is it too high？
I used AdamOptimizer to train with LR is 0.002，and the other deployment is same with you，but the loss is stoping decreasing until 2.2.
Could you help me to find the problem？Thank you very much.

I think the model is too simple! So its matching competence is not enough to hold so much data.
When I use 189999 samples, the final loss is around 2.2.
When 110000 samples, corresponding loss is around 2.0.
When lower samples, loss is still decreasing!
Hope this can help you.


Add Distinct selection to LINQ query provider

Any chance on getting this merged in?

Merged in.

Thanks


'freeze_backbone' is not defined

while using deeplabv3, getting error that freeze_backbone is not defined

just fixed this in the mast commit, simply add freeze_backbone=False in the arguments

you'll just need to add the input argument:

Thank you


Don't use ERR_PRINT_ONCE() for runtime class error because it will hide errors

This is a follow-up to PR https://github.com/godotengine/godot/pull/88683 which added this ERR_PRINT_ONCE().
On PR https://github.com/godotengine/godot/pull/91018, I learned that ERR_PRINT_ONCE() didn't work the way I thought it did, and that using it here would hide errors that we want to see.
That PR is targeting Godot 4.4, so this PR is just taking the bit switching ERR_PRINT_ONCE() to ERR_PRINT() for inclusion in Godot 4.3.

Thanks!


Indexing fails with 9000 nesting level

When I try to index a Drupal project, it ends with an error reaching the 9000 limit.
These are the last lines in the log:
[2016-11-30 21:28:10] completer.DEBUG: Processing node Symfony\Comp[44978/48629]
er\Tests\CliDumperTest [] []
[2016-11-30 21:28:10] completer.DEBUG: Indexing: [0.061321973800659]s [] []
[2016-11-30 21:28:10] completer.DEBUG: Memory: 331009504 [] []
[2016-11-30 21:28:10] completer.INFO: Progress: 49% [] []
[2016-11-30 21:28:10] completer.INFO: processing vendor/symfony/var-dumper/Tests
/Fixtures/GeneratorDemo.php [] []
[2016-11-30 21:28:10] completer.DEBUG: Cache status: disabled [] []
[2016-11-30 21:28:10] completer.ERROR: Parsing failed in file /Users/rob/Sites/c
lients/go-intranet/vendor/symfony/var-dumper/Tests/Fixtures/GeneratorDemo.php  [
] []
[2016-11-30 21:28:10] completer.INFO: Parsing: [0.0058910846710205]s [] []
[2016-11-30 21:28:10] completer.DEBUG: Processing nodes 0 [] []
[2016-11-30 21:28:10] completer.DEBUG: Indexing: [0.0069289207458496]s [] []
[2016-11-30 21:28:10] completer.DEBUG: Memory: 329638216 [] []
[2016-11-30 21:28:10] completer.INFO: Progress: 49% [] []
[2016-11-30 21:28:10] completer.INFO: processing vendor/symfony/var-dumper/Tests
/Fixtures/NotLoadableClass.php [] []
[2016-11-30 21:28:10] completer.DEBUG: Cache status: disabled [] []
[2016-11-30 21:28:10] completer.INFO: Traversing with 2 processors [] []
[2016-11-30 21:28:10] completer.INFO: Found 4 nodes [] []
[2016-11-30 21:28:10] completer.INFO: Parsing: [0.0022628307342529]s [] []
[2016-11-30 21:28:10] completer.DEBUG: Processing nodes 4 [] []
[2016-11-30 21:28:10] completer.DEBUG: Processing node Symfony\Component\VarDump
er\Tests\Fixtures\NotLoadableClass [] []
PHP Fatal error:  Maximum function nesting level of '9000' reached, aborting! in
 /Users/rob/Sites/other/padawan/vendor/mkusher/padawan/src/Entity/Collection/Spe
cification.php on line 50
PHP Stack trace:
PHP   1. {main}() /Users/rob/Sites/other/padawan/vendor/mkusher/padawan/bin/pada
wan:0
PHP   2. Application\CLI\App->handle() /Users/rob/Sites/other/padawan/vendor/mku
sher/padawan/bin/padawan:27
PHP   3. Application\BaseApplication->handle() /Users/rob/Sites/other/padawan/ve
ndor/mkusher/padawan/src/Application/CLI/App.php:16

This happens using padawan generate or :padawangenerate

class NotLoadableClass extends NotLoadableClass is there, so I guess this is normal..
We should be able to catch this somehow?

Duplicate of https://github.com/mkusher/padawan.php/issues/42

True, this can be closed.. I looked for something similar but couldnt find it.


'target' is not in list of destructive fields, but actually is destructive

My spec:
class Human
  include Mongoid::Document
  has_one :brain
end

class Brain
  include Mongoid::Document
  field :target
  belongs_to :human
end

describe Human do
  it { Human.create.create_brain(:target => 'Yay!').target.should == 'Yay!' }
end

results
  1) Human
     Failure/Error: it { Human.create.create_brain(:target => 'Yay!').target.should == 'Yay!' }
       expected: "Yay!"
            got: #<Brain _id: 4f198bb69759f7fae5000002, _type: nil, target: "Yay!", human_id: BSON::ObjectId('4f198bb69759f7fae5000001')> (using ==)
       Diff:
       @@ -1,2 +1,2 @@
       -"Yay!"
       +#<Brain _id: 4f198bb69759f7fae5000002, _type: nil, target: "Yay!", human_id: BSON::ObjectId('4f198bb69759f7fae5000001')>
     # ./spec/models/human_spec.rb:15:in `block (2 levels) in <top (required)>'

Thanks for reporting @Mik-die, the issue is that Mongoid::Relations::Many is not included in Mongoid::Relations and not mentioned in MODULES in lib/mongoid/components.rb.
I bet its not the only method missing...


\sqrt is rendered semi-invisible when Firefox is configured with custom colors (while High Contrast theme is set on Windows OS)

(UPDATE) Math renderer: chtml (svg renders correctly)
(UPDATE) Windows 10 theme: any High Contrast theme (used for accessibility feature)
Mathjax: 3.1.0
Browser: Firefox 80.0.1
Browser colors: (Text: white; Background: black)
Expression: (\sqrt[3]{4})
Numbers inside the square brackets (indices) are rendered invisible.

It works for me.  Perhaps there is other CSS that is affecting your page.  Can you provide a link to a (non-)working example?

It works for me. Perhaps there is other CSS that is affecting your page. Can you provide a link to a (non-)working example?

Sorry, it turns out that a High Contrast theme also has to be set, on Windows 10. (I updated my original comment to include this important piece.)

OK, I can reproduce it now that I know the full setting for the issue.
I was unaware of the high-contrast mode in Windows (I'm not a Windows user), and boy it looks like a real hack that causes all kinds of problems in all kinds of settings.  It also seems that it is implemented differently in different browsers.  MathJax CommonHTML works fine in Edge, for example, but there are some issues in Firefox, as you have noted.
The issue in this case is that Firefox seems to set the background color on every element, which includes each of the characters used to make up the MathJax output.  Since the "3" is placed on the page first, and the "√" is placed second, the root symbol is on top of the "3", and its solid black background obscures the "3".  Normally the background is transparent, and that is not a problem, but when Firefox sets the background color to black, it is.
While it would be possible to fix this particular case by adding CSS that places the "3" on top of the root, there are other situations like this where having the background color be non-transparent will cause problems.  For example, "\not\forall" will overlay the "/" over the "∀", and so the solid background of the "/" will obscure the underlying "∀".  And if you switched the order, the "∀" would obscure the "/".  So there is no way to get that to work in high-contrast mode in Firefox, as neither order works.  I was not able to find a way around the problem.
I think that the solution is to use SVG mode in Firefox, which works (as you point out).
While Firefox has some problems, Chrome is pretty much completely broken in high-contrast mode.  While it does seem to change the background color of the page, it doesn't change the foreground color, and so the output disappears entirely, in both CommonHTML and SVG.  (One has to set the colors explicitly in the page to get the proper effect.)
So it seems the HCM is very much a hit-or-miss proposition, and is inconsistently implemented across browsers, with wildly different levels of success for different ones.  I'm pretty sure we will not be able to support the high-contrast modes in MathJax in HCM's current state.

This could potentially be helpful: https://blogs.windows.com/msedgedev/2020/09/17/styling-for-windows-high-contrast-with-new-standards-for-forced-colors/


Resolve syncing conflicts from live-sync-work to live

Pull request opened by OPS to resolve syncing conflicts from live-sync-work to live.

another yak shaved


Pause the player after completion

I'm trying to pause the audio player once playback is complete. But I can't find any solution and I can't find the documentation that tells you how to pause once the audio is complete.
This is what I'm doing, but it gives me failure:
@Override
    public void onCompletedAudio() {
         player.pause();
    }

How can I fix this?

I haven't added player.setJcPlayerManagerListener(this)
could you give me an example of how once the audio has been completely heard, pause and don't jump to the next track

could you give me an example to be able to apply the pause once the audio track is complete, thanks.

@fumatamax I know @jeancsanchez is busy...
P.S : "@jeancsanchez if you can read this please check my email, and can you kindly get back to me..."
You can use player.setJcPlayerManagerListener(this) or let your Class implement JcPlayerManagerListener
and override all the methods of the interface
And to Stop the Player you simple need these lines below
(Just Check You might already have overridden this method)
@Override
public void onCompletedAudio() {
player.pause();
}

Thank you very much @jeancsanchez, excuse me for being so insistent. Tell you that I love your contribution to the community and that you continue with the project ahead.
I also wanted to ask you if you have the option to share the Player, I mean. Just as has the button to delete the Player, which has another button or the option to share.


Redundant .gitignore

Inside the plugins folder there is a .gitignore, since we already have a gitignore in the root of our project (the root of the wp-content), the one in the plugins folder is unnecessary!

[x] Delete .gitignore in the plugin folder (it is extra)

deleted the .gitignore file from the plugins.


Running Balance - Column Alignment off-center / not appearing at times

Name of Defective Feature

Show Running Balance // Style Running Balance in Red

I have attempted the basic troubleshooting such as clearing browser settings, disable/enable toolket, disable/enable feature and finally a full re-install of the addin and the same issues occurs.

System Settings (Required)

ToolKit Version: 2.4.1
Operating System (Mac/Windows/Etc): Mac & Windows
Browser (Chrome/Firefox/Safari): Chrome
Browser Version: 66.0.3359.170
Other Extensions: N/A

Export of Toolkit Settings (Bottom Left of Settings Page)

Settings Export
[{"key":"AccountsDisplayDensity","value":"2"},{"key":"AccountsEmphasizedOutflows","value":true},{"key":"AccountsStripedRows","value":true},{"key":"AdditionalColumns","value":true},{"key":"AdjustableColumnWidths","value":false},{"key":"AutoDistributeSplits","value":true},{"key":"BetterScrollbars","value":"1"},{"key":"BudgetProgressBars","value":"0"},{"key":"BudgetQuickSwitch","value":false},{"key":"CalendarFirstDay","value":"1"},{"key":"CategoryActivityCopy","value":true},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"ChangeEnterBehavior","value":true},{"key":"CheckCreditBalances","value":true},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":true},{"key":"CollapseSideMenu","value":true},{"key":"ColourBlindMode","value":false},{"key":"CompactIncomeVsExpense","value":true},{"key":"CreditCardEmoji","value":true},{"key":"CurrentMonthIndicator","value":true},{"key":"CustomFlagNames","value":false},{"key":"DaysOfBuffering","value":true},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":true},{"key":"DisplayUpcomingAmount","value":false},{"key":"EasyTransactionApproval","value":true},{"key":"EditAccountButton","value":"0"},{"key":"EnableRetroCalculator","value":false},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":true},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideHelp","value":true},{"key":"HideReferralBanner","value":true},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"1"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":true},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"2"},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":false},{"key":"ResizeInspector","value":false},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"2"},{"key":"RowsHeight","value":"0"},{"key":"RunningBalance","value":"1"},{"key":"SeamlessBudgetHeader","value":false},{"key":"ShowCategoryBalance","value":true},{"key":"ShowIntercom","value":false},{"key":"SpareChange","value":false},{"key":"SplitKeyboardShortcut","value":false},{"key":"SplitTransactionAutoAdjust","value":true},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":true},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":true},{"key":"ToBeBudgetedWarning","value":false},{"key":"ToggleMasterCategories","value":true},{"key":"ToggleSplits","value":true},{"key":"ToggleTransactionFilters","value":"1"},{"key":"TransactionGridFeatures","value":true},{"key":"ViewZeroAsEmpty","value":true},{"key":"goalIndicator","value":true},{"key":"highlightNegativesNegative","value":true},{"key":"l10n","value":"0"},{"key":"options.dark-mode","value":true},{"key":"pacing","value":"0"},{"key":"popupCalculator","value":true},{"key":"reports","value":true}]

Steps to Reproduce the Behavior

Enable Show Running Balance / Style Running Balance in Red feature
Refresh YNAB - Column width is either displayed off centre to column headers and/or running balance is blank

Expected Behavior

Running balance to show and column width to be aligned appropriately
Actual Behavior

Column width is either displayed off centre to column headers and/or running balance is blank

This issue has been plaguing us for a long time. I've found a few things that sometimes help to get the display "right". Try these things;

resize the window
switch to the budget view and then back to the account view
switch to a different account

I know these are just workarounds but I'm trying to offer something until the root of the problem is determined.

@RobAJHopkins Just checkin in one last time -- if you're not still seeing this issue consistently, feel free to close. If you are seeing it consistently, I'll try having another look. I've not seen this issue popup since fixing the last issue regarding running balance.

I'm also seeing this. If I switch to another budget and load an account it would not show the running balance. Reloading the page from the browser fixes this. If  I switch back to the previous budget and load an account and it will still not show the running balance until a browser reload.

@llpr I actually just closed the issue (#1290) that you're describing. We have an over-arching issue with toolkit features when budgets change which often requires a refresh and this is just something falling into that category. If I find the time I may resolve for that issue but it's honestly not likely.


Refactor Miscellaneous Field

Refactor and clean up instances of the miscellaneous field as discussed.  Change code references as needed.

Are we doing this? There are only a few instances of it.


ISPN-13461 Cache should stop if the initial state transfer times out

https://issues.redhat.com/browse/ISPN-13461

Merged, thanks


Fixes issue with limit

Closes #220

Good catch, sorry that I should have double checked the api when I perform the datafusion upgrade

@elliot14A could you help update the tests too? looks like two of them are failing.

Updated !


[SPARK-23484][SS] Fix possible race condition in KafkaContinuousReader

What changes were proposed in this pull request?
var KafkaContinuousReader.knownPartitions should be threadsafe as it is accessed from multiple threads - the query thread at the time of reader factory creation, and the epoch tracking thread at the time of needsReconfiguration.
How was this patch tested?
Existing tests.

@zsxwing thanks for finding this.
@jose-torres PTAL.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/996/
Test PASSed.

Test build #87598 has started for PR 20655 at commit 30412bf.

LGTM

LGTM

Test build #87598 has finished for PR 20655 at commit 30412bf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87598/
Test PASSed.

Merging to master and 2.3


fix: pointer not visible on hover over Features section

Title
Fix: Pointer not visible on hover over features button in navbar section
Related Issue(s)
#30
Additional Info
The href=""  was not defined for the button.

Summary by CodeRabbit

Bug Fix: Updated the Navbar component to prevent unintended page scrolling. The <Link> component within the Navbar was previously causing the page to scroll to the top when clicked due to an empty href attribute. This has now been addressed to improve user navigation experience.

Thanks a lot for contributing! You can star our project if you want!

Thanks a lot for contributing! You can star our project if you want!

sure


use the sphinx "pseudoxml" builder as a syntax checker

This probably isn't 100% right, but it's a good starting point, and it works better for me than the existing rst checkers.
I believe this should be the preferred checker for python documentation, but I don't know how I would implement that.

Current issues:

The "." in makeprgBuild will likely break down if $PWD isn't the same directory as conf.py.
There's no distinction between warning and error. This is nice-to-have imo.
This plugin isn't automatically activating for me. I have to set g:syntastic_rst_checkers = ['sphinx'] to make it work.

Yea... The first argument needs to be the first parent directory (of the file) that contains conf.py.
I'm not sure how to make that work. I suppose I'd have to write a VimL function for such?

Your 1. could be dealt with, by trying to locate conf.py.  2. is a minor annoyance, and 3. is to be expected, since not all checkers should be automatically activated.  However, generating unwanted output is a deal breaker, sorry.
I made an attempt at this myself, a few month ago (branch sphinx_checker).  My patch adds a new builder named dummy, that does everything except write the final result.  The deal breaker for it was that the builder has to be activated in conf.py (IIRC).  Still, I think this is a cleaner solution than yours.
If somebody could check my patch for sanity, add an option to sphinx to activate it from the command line, and get it included upstream, I'd say this would be the way to go.

I've fixed my !#1 using the findInParent util.
I note that there's currently three other checkers that generate unwanted output, and it seems to be the entire reason util#rmrf exists. They are co/coco java/javac lisp/clisp and sass/sass.
I'll probably be using this as-is, although I'll give your branch a quick spin.

Please note that your dummy builder still doesn't avoid writing out the weird pickle file that sphinx uses.
The rmrf strategy handles this (relatively) cleanly though.

I've fixed my !#1 using the  findInParent  util.

And somehow you missed to specify an errorformat?  Look, all that has been dealt with in my patch already.

I note that there's currently four other checkers that generate unwanted output, and it seems to be the entire reason util#rmrf exists. They are co/coco java/javac lisp/clisp and sass/sass.

Yes.  util#rmrf() is a rm -rf waiting to happen. :) I'd still prefer to avoid using it if possible.

OK, yes, but where we can't avoid it, such as sass and sphinx, it's the only alternative.
I'll work on getting a dummy builder in upstream sphinx, but it will take a month at least, and won't help anyone that has slightly-older sphinx installed.
I submitted this patch with no errorformat because it worked without it.
That said, I'll merge yours.
I only run #rmrfwith the  temporary directory that I created withutil#tmpdir`.
That's as safe as it can get.

I cleaned that up, commit 3f5bab3.  It still needs logging (the mechanisms for logging were different at the time I wrote that), and better handling of initial errors (letting the user know about missing extensions and the like).
The main point of trying to merge this upstream is not to add the dummy builder (there's no problem shipping it with syntastic), but to patch sphinx-builder to allow adding extensions from the command line.  That's the only thing not handled in my patch.  Without it you have to add syntastic to the list of extensions in conf.py, which means you'd also have to take it out before making a release.  This is way too much of a pain to be acceptable.
As for using pseudoxml, that slow things down.  I suppose you could maintain it as an external checker until dummy gets merged upstream, and make it a fallback option for people with older sphinxes after the merge.

I've merged your changes.
For your convenience, here's the diff between your branch and mine (after merging master) http://paste.pound-python.org/show/6cuY8553kjYM3k8DblSA/
A biggest difference between the two approaches is that your dummy writer doesn't catch this class of issues at all:
nail/home/buck/trees/theirs/requests/requests/api.py:docstring of requests.request:None: WARNING: py:obj reference target not found: float or tuple
/nail/home/buck/trees/theirs/requests/requests/api.py:docstring of requests.request:None: WARNING: py:obj reference target not found: bool
/nail/home/buck/trees/theirs/requests/docs/api.rst:127: WARNING: py:class reference target not found: HTTPError
/nail/home/buck/trees/theirs/requests/docs/api.rst:101: WARNING: py:class reference target not found: TooManyRedirects
/nail/home/buck/trees/theirs/requests/requests/sessions.py:docstring of requests.Session.request:None: WARNING: py:obj reference target not found: float or tuple
/nail/home/buck/trees/theirs/requests/requests/sessions.py:docstring of requests.Session.request:None: WARNING: py:obj reference target not found: bool
/nail/home/buck/trees/theirs/requests/requests/adapters.py:docstring of requests.adapters.HTTPAdapter:None: WARNING: py:obj reference target not found: int
/nail/home/buck/trees/theirs/requests/requests/adapters.py:docstring of requests.adapters.HTTPAdapter.send:None: WARNING: py:obj reference target not found: float or tuple
/nail/home/buck/trees/theirs/requests/docs/api.rst:127: WARNING: py:class reference target not found: HTTPError
/nail/home/buck/trees/theirs/requests/docs/api.rst:101: WARNING: py:class reference target not found: TooManyRedirects
/nail/home/buck/trees/theirs/requests/requests/sessions.py:docstring of requests.Session.request:None: WARNING: py:obj reference target not found: float or tuple
/nail/home/buck/trees/theirs/requests/requests/sessions.py:docstring of requests.Session.request:None: WARNING: py:obj reference target not found: bool
/nail/home/buck/trees/theirs/requests/requests/adapters.py:docstring of requests.adapters.HTTPAdapter:None: WARNING: py:obj reference target not found: int
/nail/home/buck/trees/theirs/requests/requests/adapters.py:docstring of requests.adapters.HTTPAdapter.send:None: WARNING: py:obj reference target not found: float or tuple

To correct this, change your stub of .write to a stub of .write_doc:
diff --git a/syntax_checkers/rst/syntastic.py b/syntax_checkers/rst/syntastic.py
index 198dae3..f67b9d8 100644
--- a/syntax_checkers/rst/syntastic.py
+++ b/syntax_checkers/rst/syntastic.py
@@ -25,7 +25,7 @@ class DummyBuilder(Builder):
     def prepare_writing(self, docnames):
         pass

-    def write(self, *ignored):
+    def write_doc(self, docname, doctree):
         pass

Since the main argument seems to be performance, I did five runs by each method on the requests index.rst: (after applying above patch to your dummy writer)

#
pseudoxml
dummy

1
3.929 *
4.440

2
4.125
3.565 *

3
3.874
3.551

4
3.975
3.600

5
3.852
3.516

Median times are 3.929 and 3.565 respectively. The difference is 9%.
While the speedup is significant, it borders on subliminal.
If you actually wanted to make it faster, you could eliminate >75% of the runtime by preserving the pickle cache somewhere, perhaps in the default, sphinx-configured spot. I do agree though that icky statefulness may not be worth the speedup.
Runtimes in that case: (manual runs without the -E option)

#
pseudoxml
dummy

1
.572
.493

2
.568
.490 *

3
.545
.485

4
.561
.477

5
.563 *
.495

The difference between the two is now 13%, but the difference to the uncached case is 86%.
In summary, I don't think the writing is a big enough issue to reject my branch. It's a 9% slowdown, and isn't the deciding factor for the rmrf. It's Good Enough and correct, although it could be a bit faster with some upstream work.

To correct this, change your stub of .write to a stub of .write_doc:

Done, thank you.  Commit a48916c.

If you actually wanted to make it faster, you could eliminate >75% of the runtime by preserving the pickle cache somewhere, perhaps in the default, sphinx-configured spot.

That's the point of this: the cache is preserved until Vim is restarted.  Of course, that's not the same as "full" persistence, but it should speed things up as long as you don't quit Vim.

Runtimes in that case: (manual runs without the -E option)

That's the point of moving -E to args: you can set g:syntastic_rst_sphinx_args to -n, and have the same thing in Vim.

In summary, I don't think the writing is a big enough issue to reject my branch. It's a 9% slowdown, and isn't the deciding factor for the rmrf. It's Good Enough and correct, although it could be a bit faster with some upstream work.

Ok, I'll merge your patch.  Out of curiosity, how does the above results change if you set g:syntastic_rst_sphinx_args to -n and you do the measurements without quitting Vim, as I pointed out above?

What am I meant to do when I see "syntastic: error: checker rst/sphinx returned abnormal status 1"?
Currently I edit the plugin to echo the command so I can try it myself, but that doesn't seem like it could be recommended practice. After some debugging I found that I had set the sphinx_args to "n" >.<
I'm uncertain how I'd time the command within VimL, but there is a definite speedup after the first check which seems commensurate with the above measurements. I made the above tables by running the sphinx-build command by hand.

Ok, I merged your version, with a few further cleanup changes.  Commit 131ec84.

What am I meant to do when I see "syntastic: error: checker rst/sphinx returned abnormal status 1"?

Sadly, I don't have a good answer to that.  You can enable debugging: set g:syntastic_debug to 3 (the useful values for this particular checker are 1, 3, and 33), then run the checker, and run :mes to see what's going on.  But this is not exactly user-friendly.
The problem here is that syntastic doesn't know in advance if the output from the checker is valid or not, and by the time it finds out it's too late to re-parse it to give a better meaningful message.  So, things like a messed up option or a missing extension lead to the message you're seeing.  Yes, there should be a (much) better way to address that than digging your way through the logs.  I don't have a solution to it yet. shrug

I'm uncertain how I'd time the command within VimL

The debug logs will give you some basic timing information, but you could also enable profiling.


Generate ActiveRecord 5.0 style migrations

Not a super elegant solution, but it works. Depends on ActiveRecord::Migration being defined. This doesn't happen during tests, so I was unable to add a test for it.
We need to test that ActiveRecord::Migration responds to .[] before
using .current_version, as .current_version is used in previous versions
of ActiveRecord but with different semantics.
I'm open to a better approach if someone is aware of one.
Closes #2148.

I couldn't see any tests for this part of the code base (and there is no easy way to test it).

Hmm, what about my suggestion with the migration_body to prevent the duplication?


fix variable name apearing with dollar signs around it

Ah that one slipped through (MathJax didn't work out for us on the website). Would you like me to merge right away or leave this open so you can add more fixes if you find them?

I think you can merge it now.


Request parameters get stripped in a very unfortunate way

Hello,
I was wondering why I can't pass any URL parameters to the Graph requests (for example $select) and the reason is that you forget to pass **kwargs to the parent when calling get().
Please fix.
https://github.com/microsoftgraph/msgraph-sdk-python-core/blob/dev/msgraphcore/graph_session.py#L42

I trying to use requests' session.get(path, params=...) to be clear

Hi @kkavod  thanks for pointing this out. Do you mind contributing a fix?


Development

Added commenting to the java backend under.

I am closing this one, osmething went wrong with git


Plugin Guidelines

All PostCSS plugins must pass Plugin Guidelines.

Create plugin by postcss.plugin.
Put input and output examples.

@ai

Create plugin by postcss.plugin.

OK, I will fix soon.

Put input and output examples.

Had I better to show styleguide.html ?

In a screenshot for example.

@ai Is this OK?

Nice. Can you check other rules in guidelines for your code?

I have not use postcss-style-guide in my project yet. When I get better example, I upload its image.


Added 'eus' on lib/domains

I addded my scholar education centre to the repo :)

@wildbacon1 Pull request merged. Thank you!


"Root cache could not be found. aborting." and "Error: The process '/usr/bin/docker' failed with exit code 1"

Describe the bug
creating the cache and filling it throwing errors
To Reproduce
Use example from README
Run action
Observe errors
Expected behavior
Working cache
Debug logs
https://github.com/valentijnscholten/django-DefectDojo/runs/1167379775?check_suite_focus=true
Run<EMAIL_ADDRESS>  with:
    key: docker-layer-caching-Docker Compose Actions Workflow-{hash}
    restore-keys: docker-layer-caching-Docker Compose Actions Workflow-
    concurrency: 4
    skip-save: false
Root cache could not be found. aborting.

and
1s
Post job cleanup.
Error: The process '/usr/bin/docker' failed with exit code 1
    at ExecState._setResult (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.8/dist/ttsc-dist/post.js/index.js:1300:25)
    at ExecState.CheckComplete (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.8/dist/ttsc-dist/post.js/index.js:1283:18)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.8/dist/ttsc-dist/post.js/index.js:1183:27)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:430:11)
    at Socket.emit (events.js:210:5)
    at Pipe.<anonymous> (net.js:659:12)
Error: Error: The process '/usr/bin/docker' failed with exit code 1

If applicable, add debug logs to help explain your problem.
Learn more about enabling the debug log at https://docs.github.com/en/actions/configuring-and-managing-workflows/managing-a-workflow-run#enabling-debug-logging
Runner Environment (please complete the following information):

OS:  ubuntu-latest
Action version: 0.0.8

Additional context
workflow file: https://github.com/valentijnscholten/django-DefectDojo/actions/runs/272961568/workflow

When trying master
Run satackey/action-docker-layer-caching@master
/home/runner/work/_actions/satackey/action-docker-layer-caching/master/main.ts:1
import * as core from '@actions/core'
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Module._compile (internal/modules/cjs/loader.js:895:18)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
    at internal/main/run_main_module.js:17:11

don't know that it's relevant, but 0.0.6 is outputting this for me
Post job cleanup.
mkdir -p /home/runner/work/services/services/.action-docker-layer-caching-docker_images/image
docker history -q e09701328653
docker history -q 4b80f68662ec
docker history -q ca5e106eb376
docker history -q 1ec9e8b6938d
docker history -q a24bb4013296
docker history -q ***.dkr.ecr.us-east-1.amazonaws.com/builder/liquibase:feature-RS2-1228-optimize-build
docker history -q ***.dkr.ecr.us-east-1.amazonaws.com/builder/liquibase:<none>
docker history -q liquibase/liquibase:latest
docker history -q alpine:latest

Error: The process '/usr/bin/docker' failed with exit code 1
    at ExecState._setResult (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.6/dist/ttsc-dist/post.js/index.js:1300:25)
    at ExecState.CheckComplete (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.6/dist/ttsc-dist/post.js/index.js:1283:18)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.6/dist/ttsc-dist/post.js/index.js:1183:27)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
Error: Error: The process '/usr/bin/docker' failed with exit code 1

I have the same problem with https://github.com/beeracademy/web/runs/1236371022?check_suite_focus=true

I am having a similar issue.
action step
      - uses<EMAIL_ADDRESS>        # Ignore the failure of a step and avoid terminating the job.
        continue-on-error: true

Run<EMAIL_ADDRESS>  with:
    key: docker-layer-caching-build-{hash}
    restore-keys: docker-layer-caching-build-
    concurrency: 4
    skip-save: false
  env:
    BOSUN_CONFIG: /home/runner/work/_actions/naveego/bosun/master/***-action/dist/bosun/bosun.yaml
    pythonLocation: /opt/hostedtoolcache/Python/2.7.18/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/2.7.18/x64/lib
    DOTNET_ROOT: /home/runner/.dotnet
Root cache could not be found. aborting.

Post step:
Post job cleanup.
/bin/sh -c docker save '' | tar xf - -C .
Error response from daemon: invalid reference format
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
Error: The process '/bin/sh' failed with exit code 2
    at ExecState._setResult (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.8/dist/ttsc-dist/post.js/index.js:1300:25)
    at ExecState.CheckComplete (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.8/dist/ttsc-dist/post.js/index.js:1283:18)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.8/dist/ttsc-dist/post.js/index.js:1183:27)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:430:11)
    at Socket.emit (events.js:210:5)
    at Pipe.<anonymous> (net.js:659:12)
Error: Error: The process '/bin/sh' failed with exit code 2

Not sure if something changed on the v0.0.8 version, but it just started working on my builds.

debug logging output from my workflow:
##[debug]Evaluating condition for step: 'Post Run<EMAIL_ADDRESS>##[debug]Evaluating: always()
##[debug]Evaluating always:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Post Run<EMAIL_ADDRESS>##[debug]Loading inputs
##[debug]Loading env
Post job cleanup.
##[debug]***"log":"getExistingImages","ids":["8bdb57071d85","f4f64f3d931e","29cd67a86407","394c925930cf","613632a0ab14","df3519fa4cb8","c3ef48204824","d50bd4b187b8","378dd12651fd","eac1e2b17b32","39b7b1552b75","602105ada0a5","3537a829554f","c58fb73dc3f4","b4d13dcd7f17","e71ac7366e27","cb4fd90214df","5f57c644dc6b","217e85391449","3eda611eadd1","858bcf22beaf","06e208522cad","56387899b840","1f560ce4ce7e","b39de549c36a","f3f98451c17d","c4ccba324c9c","091099bf65ad","d8b74300d554","bd53a8aa5ac9","57006130ce4b","f9dc9f9f4f4d","df043b4f0cf1","052664ad4351","a8007cad4069","8b286994f1a6","03cb4444a82d","78a2ce922f86","be4e4bea2c2e","c8bccc0af957","ed51199dbcc6","6d1ef012b567","b7c5ffe56db7","9a948d360778"],"repotags":["airbyte/source-stripe-abprotocol-singer:dev","airbyte/source-exchangeratesapi-singer-abprotocol:dev","airbyte/postgres-singer-source-abprotocol:dev","airbyte/source-template-singer:dev","airbyte/integration-base-singer:dev","airbyte/airbyte-postgres-destination-abprotocol:dev","airbyte/airbyte-csv-destination-abprotocol:dev","airbyte/airbyte-bigquery-destination-abprotocol:dev","airbyte/integration-base-python:dev","airbyte/integration-base-java:dev","airbyte/integration-base:dev","airbyte/scheduler:dev","airbyte/server:dev","airbyte/webapp:dev","airbyte/seed:dev","airbyte/db:dev","airbyte/code-generator:dev","airbyte/scheduler:<none>","python:3.7-slim","airbyte/airbyte-postgres-destination-abprotocol:0.1.0","airbyte/postgres-singer-source-abprotocol:0.1.0","openjdk:14.0.2-slim","node:10","node:12","buildpack-deps:stretch","buildpack-deps:buster","debian:9","debian:8","node:12-alpine","nginx:1.19-alpine","node:10-alpine","postgres:13-alpine","ubuntu:14.04","debian:10.5-slim","jekyll/builder:latest","rtcamp/action-slack-notify:v2.1.0","testcontainers/ryuk:0.3.0","alpine:3.9","alpine:3.10","alpine:3.8","postgres:9.6.12","alpine:3.7","alpine:3.4","mcr.microsoft.com/azure-pipelines/node8-typescript:latest"]***
##[debug]***"existingSet":***
##[debug]***"log":"getExistingImages","ids":["8bdb57071d85","f4f64f3d931e","29cd67a86407","394c925930cf","613632a0ab14","df3519fa4cb8","c3ef48204824","d50bd4b187b8","378dd12651fd","eac1e2b17b32","39b7b1552b75","602105ada0a5","3537a829554f","c58fb73dc3f4","b4d13dcd7f17","e71ac7366e27","cb4fd90214df","5f57c644dc6b","217e85391449","3eda611eadd1","858bcf22beaf","06e208522cad","56387899b840","1f560ce4ce7e","b39de549c36a","f3f98451c17d","c4ccba324c9c","091099bf65ad","d8b74300d554","bd53a8aa5ac9","57006130ce4b","f9dc9f9f4f4d","df043b4f0cf1","052664ad4351","a8007cad4069","8b286994f1a6","03cb4444a82d","78a2ce922f86","be4e4bea2c2e","c8bccc0af957","ed51199dbcc6","6d1ef012b567","b7c5ffe56db7","9a948d360778"],"repotags":["airbyte/source-stripe-abprotocol-singer:dev","airbyte/source-exchangeratesapi-singer-abprotocol:dev","airbyte/postgres-singer-source-abprotocol:dev","airbyte/source-template-singer:dev","airbyte/integration-base-singer:dev","airbyte/airbyte-postgres-destination-abprotocol:dev","airbyte/airbyte-csv-destination-abprotocol:dev","airbyte/airbyte-bigquery-destination-abprotocol:dev","airbyte/integration-base-python:dev","airbyte/integration-base-java:dev","airbyte/integration-base:dev","airbyte/scheduler:dev","airbyte/server:dev","airbyte/webapp:dev","airbyte/seed:dev","airbyte/db:dev","airbyte/code-generator:dev","airbyte/scheduler:<none>","python:3.7-slim","airbyte/airbyte-postgres-destination-abprotocol:0.1.0","airbyte/postgres-singer-source-abprotocol:0.1.0","openjdk:14.0.2-slim","node:10","node:12","buildpack-deps:stretch","buildpack-deps:buster","debian:9","debian:8","node:12-alpine","nginx:1.19-alpine","node:10-alpine","postgres:13-alpine","ubuntu:14.04","debian:10.5-slim","jekyll/builder:latest","rtcamp/action-slack-notify:v2.1.0","testcontainers/ryuk:0.3.0","alpine:3.9","alpine:3.10","alpine:3.8","postgres:9.6.12","alpine:3.7","alpine:3.4","mcr.microsoft.com/azure-pipelines/node8-typescript:latest"]***
##[debug]***"existingSet":***
Error: The process '/usr/bin/docker' failed with exit code 1
    at ExecState._setResult (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.8/dist/ttsc-dist/post.js/index.js:1300:25)
    at ExecState.CheckComplete (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.8/dist/ttsc-dist/post.js/index.js:1283:18)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.8/dist/ttsc-dist/post.js/index.js:1183:27)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
Error: Error: The process '/usr/bin/docker' failed with exit code 1
##[debug]Node Action run completed with exit code 1
##[debug]Finishing: Post Run<EMAIL_ADDRESS>

Same problem on v0.0.7.

Using v.0.0.8 only encountering this the furst run when nothing has been cached yet, second run it's working fine.

When trying master
Run satackey/action-docker-layer-caching@master

I think the version needs to be master-release (or maybe latest?) for that to work.

Just tried again with v0.0.11 same result.
https://github.com/DefectDojo/django-DefectDojo/runs/1584256485?check_suite_focus=true
Slightly different error messages:
Run<EMAIL_ADDRESS>  with:
    key: docker-layer-caching-Unit tests-{hash}
    restore-keys: docker-layer-caching-Unit tests-
    concurrency: 4
    skip-save: false
Root cache could not be found. aborting.

Post job cleanup.
<Buffer 45 72 72 6f 72 20 72 65 73 70 6f 6e 73 65 20 66 72 6f 6d 20 64 61 65 6d 6f 6e 3a 20 69 6e 76 61 6c 69 64 20 72 65 66 65 72 65 6e 63 65 20 66 6f 72 6d ... 3 more bytes>
Error: The process '/usr/bin/docker' failed with exit code 1
    at ExecState._setResult (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.11/dist/ttsc-dist/post.js/index.js:1035:25)
    at ExecState.CheckComplete (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.11/dist/ttsc-dist/post.js/index.js:1018:18)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/satackey/action-docker-layer-caching/v0.0.11/dist/ttsc-dist/post.js/index.js:912:27)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
Error: Error: The process '/usr/bin/docker' failed with exit code 1
<Buffer 45 72 72 6f 72 20 72 65 73 70 6f 6e 73 65 20 66 72 6f 6d 20 64 61 65 6d 6f 6e 3a 20 69 6e 76 61 6c 69 64 20 72 65 66 65 72 65 6e 63 65 20 66 6f 72 6d ... 3 more bytes>

Tried again with specifying a cache to avoid the space in the default cache. Same result. I'm giving up.
      - uses<EMAIL_ADDRESS>        # Ignore the failure of a step and avoid terminating the job.
        continue-on-error: true
        with:
          key: docker-layer-caching-Unit-tests-{hash}
          restore-keys: docker-layer-caching-Unit-tests-

Just tried again with v0.0.11 same result.
https://github.com/DefectDojo/django-DefectDojo/runs/1584256485?check_suite_focus=true
Running this workflow with ACTIONS_STEP_DEBUG set to true shows the following:

[...], "defectdojo/defectdojo-django:<none>", [...],"mysql:<none>", [...],"rabbitmq:<none>", [...],"python:<none>", [...]

This specific case is hitting the issue described in #17: currently this action doesn't support images specified by sha256 hash.

The error also happens for us, see for example this GitHub Actions step.
The GitHub Actions step looks like this:
    - name: Set up Docker cache
      uses<EMAIL_ADDRESS>      continue-on-error: true
      with:
        key: teste2e-docker-cache-{hash}
        restore-keys: |
          teste2e-docker-cache-

Has there been any progress on this issue in the last 4 months since it was opened?

The error also happens for us, using v0.0.11, see for example this Actions run:

In this case it looks like the cache really isn't there. It may be due to GitHub Actions not sharing caches between PR branches. Once there's a cache in the target branch the PRs will fall back to that if their own cache isn't found.
To confirm that it would be helpful to have a run of the workflow with step debug enabled. Instructions for doing that can be found here:
https://docs.github.com/en/actions/configuring-and-managing-workflows/managing-a-workflow-run#enabling-debug-logging

Has there been any progress on this issue in the last 5 months since it was opened?

It looks like almost all of these cases turned out to be #17. That includes valentijnscholten, sherifnada, xenoterracide and possibly derekssmith too (though they reported it as fixed after an update).
In andy-maier's case the error message was correct; the previous run had no new images to cache, so there was no cache present on the next run.
If anyone gets this message despite the previous run successfully saving a cache, please reply here with details. Include a link to your workflow run logs with ACTIONS_STEP_DEBUG enabled.

same problem with v0.0.11 I think


Tag appropriate version as the latest

Describe the bug
Current latest version is 3.0.0-alpha.1 which causes a downgrade when I use pnpm up --latest.

Your minimal, reproducible example
I doubt it's needed
Steps to reproduce
pnpm up --latest
Expected behavior
Installs 3.0.0-beta.48
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
macOS
tanstack-virtual version
^3.0.0-beta.41
TypeScript version
No response
Additional context
No response
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Came here to raise this.
The documentation on the website does not match the API (eg. "useVirtual" vs. "useVirtualized"  "size" vs. "count". So I wanted to see what version to use.  It's kind of weird that I get an "alpha" version but "beta" versions are seen as less-appropriate to be treated as the latest stable.
P.S. thanks for making and maintaining this software. The choice to make it a function rather than component is delightful.

No longer relevant to me - using virtuoso instead.

Hello, I think this can be reopened because it's still the case and the save behaviour happens. Beta 9 is marked as latest and following betas are "pre-release". I have doubts whether it's on purpose or not, and whether I should use beta 9 or the latest beta.


fix: pagination fix and some refactor

hide pagination if there are less than 10 items
Closes #1478, #1476

This has changes for 2 tickets.


Empty Directive test failing

The empty directive test is failing due to there being an exception being thrown in the console, but the exception is unrelated: 'http://localhost:8000/favicon.ico 0:0 Failed to load resource: the server responded with a status of 404 (Not Found)'

My test was clearly way too generic. I'll get that cleaned up this week.

Fixed test logic in PR #105 to be much more explicit.

@rev087 Can you close this?


GimpyG’s function wishlist

Well since you asked, heck yeah I do have a wishlist!(some are probably super difficult)
The cursor is getting really erratic and jumpy when I slow down to click on a button, feels like Gameface doesn’t know what to do with tiny/slow movements or when to simply pause trying to interpret insignificant adjustments so I can click. Hopefully the solution wouldn’t be too heavy handed so I can move on quickly to other gaming tasks.
add a mode that treats cursor movement like a D-pad on a controller. Basically WASD and the combinations needed for diagonals. This would allow retro gaming and that is a good thing!
Allow face gestures the option of being analog, for example pressing the gas in a driving game should be incremental rather than on/off. This would also help me with creating art since many programs adjust line darkness or width based on how much pressure is being applied. For instance mouth move left could gradually increase values as you move more left.
Those are wishes that would really improve the quality and versatility of Gameface beyond gaming into creating. Thanks @acidcoke for asking what might be helpful to me.

The cursor is getting really erratic and jumpy when I slow down to click on a button, feels like Gameface doesn’t know what to do with tiny/slow movements or when to simply pause trying to interpret insignificant adjustments so I can click. Hopefully the solution wouldn’t be too heavy handed so I can move on quickly to other gaming tasks.

Maybe not impossible but I don't know how you'd solve that.

add a mode that treats cursor movement like a D-pad on a controller. Basically WASD and the combinations needed for diagonals. This would allow retro gaming and that is a good thing!

This shouldn't be to hard to implement

Allow face gestures the option of being analog, for example pressing the gas in a driving game should be incremental rather than on/off. This would also help me with creating art since many programs adjust line darkness or width based on how much pressure is being applied. For instance mouth move left could gradually increase values as you move more left.

I think that this doable but a little bit more complicated since project-gameface would need to act as some kind of gamepad. And I haven't done any research what libraries are available/best to use.

Those are wishes that would really improve the quality and versatility of Gameface beyond gaming into creating. Thanks @acidcoke for asking what might be helpful to me.

 But I'm not doing it completely selfless since I'm using gameface myself 😜


add node error

@Arealm did you setup the Go backend?

I think that error happens when the DB has no node data.The this.state.form.parentNode and  this.state.nodes in function renderSelect is null,and leads to that error.

I tried to solve it in pr #100

Fixed in: https://github.com/casbin/casbin-forum/commit/bb9e9e5b48c5105aa67c1acad9a4f3aaed6baf56


drivers: charger: bq25180: fix return value check

Fix missing check of the return value of bq25180_set_charge_current function, resulting in logically dead code, as indicated by Coverity CID 347197.
Fixes #69117

Thanks!


Create copyReplace.ts

A tool which runs a simulation, confirms, creates backup in tar.gz, copy/replaces the existing config with the output from the genesis tool.
Full information for a README:
##USER:
Please provide a full description of this typescript tool
##ASSISTANT:
Creating a TypeScript-based tool to simulate file operations before actually performing them, especially for tasks like file copying and directory structure alignment, involves a more complex setup than a simple shell script. This is primarily because TypeScript (and JavaScript) runs in a Node.js environment, which is not as directly integrated with the file system and shell operations as bash scripting. However, Node.js provides powerful libraries, such as fs for file system operations and child_process for executing shell commands, making it possible to create a sophisticated tool for your requirements.
Description of the TypeScript Tool
This TypeScript tool will be designed to run on a Node.js environment and will perform the following tasks:

Simulation Phase:

It will simulate the copying process from the output directory to the config directory based on the most recent directory within output.
It will list all files that would be copied or replaced, showing the source and destination paths without actually performing the copy. This allows the user to review the changes that will be made.

Confirmation:

After the simulation, the tool will prompt the user to enter CONFIRM to proceed with the actual copying process. If the user does not confirm, the tool will exit without making any changes.

Backup Phase:

Before copying files, the tool will create a tar.gz archive of the entire config directory's current state. This serves as a backup to restore the original state in case of any issues with the update process.

Copy and Replace Phase:

Upon confirmation, the tool will then proceed to copy and replace files from the output directory to the config directory, following the simulation's outline.

Technical Considerations

File System Operations: Utilizes the fs and fs-extra libraries for reading directories, copying files, and creating the backup archive.
User Input: Uses the readline or similar libraries for handling user input from the console.
Archiving: Leverages archiver or command-line utilities via child_process for creating a backup of the config directory.
Path Handling: Employs the path library for managing file paths and ensuring compatibility across different operating systems.

Implementation Outline
The tool will be structured into several main components:

FileOperationSimulator: A class or function responsible for simulating the file operations and displaying the expected actions to the user.
UserConfirmation: A function to prompt the user for confirmation before proceeding with actual file modifications.
BackupCreator: A component for creating a backup of the config directory before any changes are made.
FileCopier: A class or function that handles the actual copying of files from output to config after user confirmation.

Usage
The tool will be a command-line application executed with Node.js. Users will run it from the terminal in the directory containing both the config and output directories. The workflow will be:

Execute the tool via node [toolName].js or through an npm script.
Review the simulated operations output by the tool.
Enter CONFIRM when prompted to proceed with the copying and backup creation.
Review the final output indicating successful copying and backup.

Advantages
This TypeScript tool provides a user-friendly interface for reviewing potential file system changes before they occur, along with a straightforward method for confirming those changes. It also ensures that a backup is created, adding a layer of safety to the operation.
Development Requirements

Node.js installed on the system.
Basic knowledge of TypeScript and Node.js for potential customizations.
Dependencies such as fs-extra, readline-sync (or similar), and archiver need to be installed via npm.

This description outlines a high-level overview of what the tool would look like and how it would function. Implementing such a tool requires writing TypeScript code, compiling it to JavaScript, and then running it with Node.js. It offers a robust and user-interactive way to manage file system operations with the added benefit of cross-platform compatibility.

Hell @defiQUG thanks for this. We welcome contributions so please feel free to send a PR across and we can review and add functionality in

It's a tool I personally have used.  This is really for those using the Quorum Dev Quickstart, then using the Genesis Tool to change keys.

Hi @defiQUG yep that is correct we use this in the quickstart and k8s repos. Im still not sure what problem the PR is solving though or how it addresses the concerns of automation. I'll close this PR if that's ok (feel free to open it if it addresses the concerns raised above). Let us know when the FusionAI Orchestrator is ready
Cheers


Beacon opt-out method for modpacks

I've read your article about the newly added telemetry, and the options to disable it.
In modpack context, unfortunately it seems that the options are only usable in MultiMC-style modpacks, not for example, ones hosted in Modrinth or Curseforge. Therefore I suggest adding a third way to disable the feature, e.g. via a config file.
Edit: I was informed of quilt_loader.txt, this seems very suitable for this purpose.

I don't think it should be a modpack makers decision, it should be up to the user

As a modpack creator, I disagree.
It is up to the user, when the user creates their own game instance. But when they download a modpack, the expectation is that the experience is already curated for them, which sometimes also means RAM management, Java flags and the like.
Why RAM and Java flags are not distributable in Modrinth/CurseForge packs is a question for another day, here I'd rather draw a parallel with the dependency overrides feature which is also a modpack-oriented config file.

That doesn't really answer my concern. Let me phrase it more clearly:
Why should a modpack creator be making this decision on behalf of the user? Why would they make that decision, if they could?
It will likely be based upon personal thoughts about Quilt's 'telemetry', whereas your example of RAM management doesn't involve personal feelings.

Why should a modpack creator be making this decision on behalf of the user? Why would they make that decision, if they could?

Some possible reasons include:

Not trusting the way this telemetry works
Saving bandwidth
Not trusting the server telemetry is sent to
Not wanting to appear in the count

and these values can be had:

by the user about this telemetry specifically
by the user about all telemetry
by the modpack about this telemetry specifically
by the modpack about all telemetry

So if the user knows and trusts the telemetry stance of a modpack, it is disingenuous if the modpack uses a mod loader in which it cannot disable the telemetry for every user by default.

That answers the second question, but not the first. The modpack creator has no right to be making this decision on behalf of the user, imo.

Users choose modpacks to make decisions for them, including mods, configs, resource packs, worlds... How is this any different?

That answers the second question, but not the first. The modpack creator has no right to be making this decision on behalf of the user, imo.

Itn's that kinda point of modpacks? To have ready collection of mods created by someone, without having to decide which mods to add or how to configure them? This also doesn't prevent users from enabling it if they want to.

this also doesn't prevent users from enabling it if they want to.

The chance of anyone doing that is minimal, let's be honest :( I wouldn't do it, out of laziness.

Saving bandwidth is a non-issue. This request is tiny. There are much bigger fish to fry in terms of network requests.
The rest of your reasons are personal feelings. They're about trust (apart from not wanting to be in the count, which is a personal opinion as well).

'Modpacks' do not hold values about telemetry. Modpack creators however, do. Allowing this would be allowing the modpack creators personal thoughts on (this) telemetry to be pushed onto the user, at the expense of Quilt.
Finally, you talk about trusting a modpack and it's decisions. Most of us forget that most users are not interested in all of this. They just want something that works for them - if the mod (or mod list in the case of modpacks) is attractive, and there are pretty photos in the description, I'd take a bet that most people aren't that bothered about the creator's stance on telemetry and how that affects them.

You can, it should be exposed as an config option (already is, but you can't define it in file). What's different from configuring a modloader to configuring a mod? Modloader is nothing more than a "core" mod, that you need to use for easier experience. In this case by being on by default quilt technically also decides for the user as they would likely be unaware about it.

The fact that configuring a mod might mean increasing the chance of pink sheep spontaneously exploding, while configuring the mod loader is making a decision about the users privacy based on the perception of the modpack creator, in this case.
Also, yes configuring a mod loader can be a part of a mod pack. Just not this configuration

That answers the second question, but not the first. The modpack creator has no right to be making this decision on behalf of the user, imo.

The blistering irony of saying this while opting users into a tracking beacon without asking them

First of all, that's poorly phrased, I am voicing a personal opinion, I did not opt anyone into anything. Secondly, I think I already made it clear that I don't think this is a violation of anyone's privacy when we talked on Discord earlier and therefore I don't see a problem with the beacon being opt-out, and even if I did, work is already being done to add an option to the installer as far as I can see. Anyway, that's not what this issue is about so let's not go round in circles again

There are some merits to the idea of providing an instance-based setting, but I don't think modpacks should be the intended scope for it. If anything, depending on how flexible the implementetion is, this could be a terrible idea - it'd suck pretty hard if a modpack was able to opt someone in, instead of opting them out.
I think we can do better with providing ways to opt out, though. Servers, for example, need to have an easier way to opt in or out that will function within a restricted filesystem, something which is common on server hosting platforms and would likely need an instance level setting.
It's worth nothing that the java argument isn't necessarily intended for direct use by users either - it's been pointed out a few times that it was intended for launchers to expose this where possible and willing, and that (combined with the installer PR to add an opt-out checkbox) would address your concerns as well, from what I can tell.
More options are good, but this is overstepping what a modpack should be responsible for, imo. After all, there are users out there that would rather have the beacon request enabled, as unlikely as that may seem to someone that would prefer to disable it.

My modpack currently disables non-essential network requests in 6 mods, plus Minecraft itself. Each one has a different reason behind it, be it a privacy concern, an unwanted extra feature or just practically unnecessary.
Still cannot understand why disabling it in the loader as well would be such "overstepping" and require special treatment compared to aforementioned changes.
Trying to convince users that the beacon is not bad while being very reluctant to give easy opt-outs is contradictory and does not increase the trust in the feature.

But to give some new ideas, how about:

the environment variable/JVM flag overrides the config file when present
the state of telemetry is listed in every usual loader log along with mods and the like, to notify users about whether it is enabled or not

Realistically, if your modpack doesn't clearly point out that it's disabling these things, and potentially if that isn't the primary point of the modpack, then I would consider it overstepping - if someone installs a tech modpack then I don't think they'd expect it to mess with that kind of thing.
One example I can think of that I've seen in the wild is modpacks that silently include a mod that intentionally breaks chat reporting, when the focus of the pack is completely unrelated. I'm sure you're actually telegraphing this since you seem to know what you're talking about, though.

Both of those approaches seem like good options to me.

I wouldn't really want a modpack to decide on whether or not I opt-in or out of a beacon, regardless of my opinion on the beacon.

I don't understand the point of "the modpack shouldn't decide for me". If you want to make the decision, then you can change the config file yourself. The thing is, the majority of people using modpacks (at least Optifine replacement modpacks) are using it cause they don't know how to do that stuff themselves, they need the modpack to do it for them. They wouldn't even know that Quilt has telemetry, let alone know how to disable it.
The choice is not between the user and the modpack deciding, it is between Quilt or the modpack deciding, and I think modpacks should have the ability to decide if they want to. If you want to make the decision yourself, you still can.

My point is that most users:

are not as privacy concious as the minority of people that have voiced their opinions here
do not mind this 'telemetry'
could not care less about it, to be frank

...it defeats the purpose of a MAU count if one person can make a decision based on their personal opinions that could potential disable thousands of users beacons

are not as privacy concious as the minority of people that have voiced their opinions here

That's why modpacks make the decisions for them. Like governments, you choose someone you trust to make some decisions for you.

do not mind this 'telemetry'

If they don't, it's easy to notice and re-enable then, because it is a clearly marked config file in their config folder.

could not care less about it, to be frank

Point 1 above.

...it defeats the purpose of a MAU count if one person can make a decision based on their personal opinions that could potential disable thousands of users beacons

Well, that's the goal? All methods of statistics collection have some margin of error, assuming they don't will only cause more problems.
A real-world example: a city wanted to change a bus route because they relied on travel card validation statistics and saw low activity in some bus stops. Guess what happened? Elders and children who did not have to validate their ticket protested against the change and the city reverted the route.

you choose someone you trust to make some decisions for you.

You have an inflated sense of what is going on here though. Most users find a modpack that has the mods they like, or has the best pictures in the description. They're not trusting the modpack author to do anything but get mods that don't crash from their point of view.

easy to notice and re-enable then

once again, 'could not care less'. It goes both ways. Couldn't care about it being enabled or disabled.
How is the goal to allow one person to disable the beacon for many people, that makes no sense? Of course there's margin of error: individuals who have a problem with it disabling it. That's very different to individuals who have a problem with it disabling it for people who have no opinion on it.

Modpacks are not a party in the data collection process, they aren't the one collecting data and they aren't the one the data is being collected from, why should they be allowed to change the data collection settings (regardless of whether or not it's a default).

why should they be allowed to change the data collection settings

Because their goal is to curate the experience for the users, preconfigure various settings including mod settings, instance settings and loader settings. If specific data collection is harmful or unwanted for a specific modpack context, it should be preconfigurable, just like any other setting.

Then we're back to the fact that it's an opinion that the beacon is bad and you're pushing that opinion onto other people at the expense of the MAU count, the reason for the beacon.

I'm not a lawyer but I feel like one talking to one might be useful in deciding if this is a good decision if someone does decide to implement this.

That was not intended as a threat by the way, just that introducing a third party in data collection might be iffy.
I think under the GDPR for example the modpack author might be seen as a joint data controller, for example.

This issue is not about extending data collection, only restricting. Similar to what Windows, Mac, Chrome give options for.
It is not a stretch to say that modpacks can be used in schools, LAN parties and the like, Minecraft is an educational game. My own modpack has also been deployed in a school.
There are reasons to restrict non-essential network activities: enterprise policies, (public) network rules, country laws (Quilt does have certain political activism), and yes, user preferences. Just because they may seem very theoretical at the moment, doesn't mean they will always stay so.

It is not a stretch to say that modpacks can be used in schools, LAN parties and the like, Minecraft is an educational game. My own modpack has also been deployed in a school.
In these cases the school owns the network and are allowed to ensure that their network is used responsibly and to protect students from inappropriate or harmful content. It's their network and (often) their hardware so they get to make certain decisions for users. That's not what's happening here.

The school point is really scraping the bottom of the barrel. All of those reasons are the responsibility of the user to deal with;
'what if my network was used on an organization network that forbids the Quilt beacon somehow? Better disable it for every user of my modpack just in case' makes no sense, and that is your point if i understand correctly.

'what if my network was used on an organization network that forbids the Quilt beacon somehow? Better disable it for every user of my modpack just in case' makes no sense, and that is your point if i understand correctly.

A "modpack" refers to any kind of prepackaged instance. An instance you share with a friend, a server that requires some clientside mods, a public set of mods and configs user chooses to install from a website, and yes, schools and other public environments. So even if you don't like that users could install such modpack from a website, you're discouraging other use cases as well.
Overall, having the option in a config file allows for:

users to follow the instructions to create the file by reading a website
users to download and copy a predefined config file
not having to have admin permissions to edit a registry
not having to scourge the web for how to change JVM arguments in their launcher or what they even are

A "modpack" refers to any kind of prepackaged instance.

Ah, sorry. I thought we were talking about adding configs to these types of modpacks:

ones hosted in Modrinth or Curseforge

As mentioned in the first post. And not about prepackaged instances of Quilt?

Ah, sorry. I thought we were talking about adding configs to these types of modpacks:

As mentioned in the first post. And not about prepackaged instances of Quilt?

Well, initially I didn't think that I'd need to elaborate on all use cases, so I only mentioned those in the OP which I was personally most interested in. But since you didn't like that reason/use case, I wrote down more reasons and use cases.

I think the best place for a setting like this would be in the client. I think a configuration outside of control of the (curseforge/modrinth type) modpack would not be a terrible idea, but I don't think that's what this issue was for, considering the title and description of the issue.

I think a config file outside of control of the (curseforge/modrinth type) modpack would not be a terrible idea, but I don't think that's what this issue was about, considering the title and description of the issue.

If Quilt Loader looked for config files outside of where it is installed, that would be overreaching on their end, similar to - but not exactly - the registry value. This telemetry affects only Quilt, only inside Minecraft - it doesn't make sense to store configs elsewhere. And when it is stored inside a Minecraft folder, it is by definition controllable by modpacks.

If Quilt Loader looked for config files outside of where it is installed, that would be overreaching on their end, similar to - but not exactly - the registry value. This telemetry affects only Quilt, only inside Minecraft - it doesn't make sense to store configs elsewhere. And when it is stored inside a Minecraft folder, it is by definition controllable by modpacks.

Fair enough. Thank you for the explanation. In that case I understand why Quilt went with java parameters instead.

If Quilt Loader looked for config files outside of where it is installed, that would be overreaching on their end

That makes no sense. How is that overreach? Is looking for an environment variable also overreaching by that logic? A registry key doesn't make sense I'll agree with that.

A "modpack" refers to any kind of prepackaged instance.

Yes, and 'schools and other public environments' is such a small subset of users which, most importantly, almost certainly have an IT manager or team that can deploy an environment variable to all computers if they felt the need too - which I still don't believe they would

Obsoleted by RFC#84


Inserting data directly into Quantumleap

Fixes issue-46
Updated the docs for inserting data into quantumleap directly

hi @iamarnavgarg thanks for this. I saw you ditched #266, so I suppose this PR replaces it? Like I said in #266, don't worry about tests failing, we'll force a merge of this PR ourselves later on and fix those (unrelated!!!) test failures in a separate PR. Thanks for your contribution!

Fixes #46


Add sum statistics and PhysicalExpr::column_statistics

Which issue does this PR close?
Fixes #992
Rationale for this change
Some statistics can propagate through expressions, such as min, max and sum.
In this particular case, I was looking at the ClickBench Q29 and realized we had no way to report sum statistics to DataFusion (which would also help for avg).
Q29 looks like this btw:
SELECT SUM("ResolutionWidth"), SUM("ResolutionWidth" + 1), SUM("ResolutionWidth" + 2), SUM("ResolutionWidth" + 3), SUM("ResolutionWidth" + 4), ... SUM("ResolutionWidth" + 88), SUM("ResolutionWidth" + 89) FROM hits;

And with correctly reported sum statistics, both Q2 and Q29 collapse down to O(1).
What changes are included in this PR?
PhysicalExpr has a new defaulted trait function column_statistics that takes a Statistics and returns statistics for the columnar result of the expression. (Unlike the linked issue which proposes returning a full Statistics object).
Further, this PR adds a sum statistic to demonstrate the value of propagation (that turns into Precision::Absent on overflow).
Are these changes tested?
Are there any user-facing changes?

Is there any combined script to run all the linting checks at once? I don't want to burn all your CI credits!

Thank you! (though we likely are spoiled as the Apache Software Foundation has lots of credits (thank you Github!)
The scripts in https://github.com/apache/datafusion/tree/main/ci/scripts can be used to run the tests locally

(BTW thank you for this well structured, well documented PR -- it was very easy to read and understand)

Sum statistics are not available in parquet, but I can easily see other file formats providing them so I think this is a good addition to DataFusion.

Aha, I might know one of those file formats! Here's the click bench diff (give or take quite a bit of noise): https://github.com/spiraldb/vortex/actions/runs/12297901942#summary-34320120073
Easy to see that Q2 and Q29 drop to constant time, and I think a few of the other queries benefit from AVG aggregations.

I really like that this PR integrates nicely with the existing  AggregateStatistics pass / value_from_statistics pass

I had actually considered other optimizer rules that might enable this, for example rewriting SUM(X + 1) to SUM(X) + SUM(1) with the latter sum turning into a constant evaluation. Unfortunately, rewriting the query in this way can significantly change overflow semantics, particularly with signed integers. It seemed best to preserve the original expression, attempt to evaluate over stats, and fallback to the original expression if the stats optimizations overflow.

The effect of making ColumnStatistics even larger (each ScalarValue is already quite large I think so adding another potential field may make statistics management even worse. Again, maybe this will be handled by the revamp that @suremarc is looking into

We ran into similar performance issues in Vortex in fact. We've found that actually having a Vec<(Stat, Value)> or Arc<[(Stat, Value)]> performs quite well since we now have ~10 different statistics, albeit sparsely populated.
(This reminds me, a sum statistic also doubles as a true/false count for boolean arrays. I imagine there are more optimizations in DataFusion that could benefit from a pre-computed true/false count)
Is having custom statistics something that DataFusion might support? For example, I could declare a custom statistic along with a custom optimizer rule that makes use of it. I can also see the opposite argument that if a statistic is in any way useful, then DataFusion should add support for it internally, and therefore it doesn't need extensible stats.

In terms of testing, I think we should create a "end to end" type test -- that shows registering a TableProvider that can provide sum statistics that the optimizer uses to optimize away the actual aggregates.

I will add one of these!

I will go spend some time trying to writeup what I think the consensus for Statistics is.

Do you consider this to be blocking for this PR? Or is expanding the size of ColumnStatistics acceptable in the short-term?

Is having custom statistics something that DataFusion might support? For example, I could declare a custom statistic along with a custom optimizer rule that makes use of it. I can also see the opposite argument that if a statistic is in any way useful, then DataFusion should add support for it internally, and therefore it doesn't need extensible stats.

Extending statistics to support user defined data seems very reasonable to me. I good test in my mind to avoid APIs that can't actually be used in the real world,  is to try and make some sort of example showing how someone would actually use it (e.g. maybe pass the custom statistics into a user defined function that can take advantage of it somehow?)

Do you consider this to be blocking for this PR? Or is expanding the size of ColumnStatistics acceptable in the short-term?

I don't consider it blocking per se -- especially if we are (finally) going to get the project to revamp Statistics moving again
I would like to get some consensus on what we want to do with Statistics / range / interval evaluation on statistics so that we don't end up with multiple incompatible partially overlapping features.
Thank you again

I have been thinking a lot about this PR and I don't want to let it die because we are stuck in trying to figure out a broader staistics question. I would like to find an incremental way forward.
Here is my proposal:
We target this feature (support sum statistics) for inclusion in DataFusion 45 (aka we plan to merge this / part of it after DataFuion 44 is out). That will give us time to rework / finagle the APIs without having to make brekaing changes in back to back  releases (hopefully)

Do you consider this to be blocking for this PR? Or is expanding the size of ColumnStatistics acceptable in the short-term?

I recommend:

Add the new sum statistics in one PR
Look into optimizing the size (maybe wrapping the Statistics with Arc or something) as a second PR(s)
Figure out how to integrate PhysicalExpr::column_statistics as a third PR (I think it would make sense after we had the ColumnStatistics in Arc)


Tune Dockerfile for faster builds

Pool go mod download for all arch
Use go cross build capabilities instead of building from containers running on different arch
Produce lighter binaries using -ldflags '-s -w'
Use -trimpath build option
Upgrade Alpine to 3.13

On my macbook pro (2,6 GHz 6-Core Intel Core i7) with clean cache:

main @ 62972bec5449bb8ac797c23f922ed2bb9947cef8: Building 731.6s (69/69)
tune-dockerfile @ dbd6eff83671d4b859a70e82d11a7a9320883013: Building 162.3s (41/41)

Produce lighter binaries using -ldflags '-s -w'

As we would like to offer a pprof endpoint sometime in the future, I do not think it is wise to add the -w flag and remove DWARF debug information.
One flag you may want to add, that has been available since Go 1.13, is the -trimpath flag.

Produce lighter binaries using -ldflags '-s -w'

As we would like to offer a pprof endpoint sometime in the future, I do not think it is wise to add the -w flag and remove DWARF debug information.
One flag you may want to add, that has been available since Go 1.13, is the -trimpath flag.

@sylr can I run this with Docker For Mac, do I need to setup anything, like buildx profiles?

@sylr can I run this with Docker For Mac, do I need to setup anything, like buildx profiles?

On mine I only had to do docker buildx create --use

On mine I only had to do docker buildx create --use

We've switched to tonistiigi/xx and now the multi-arch build takes 6m, instead of 42m. Closing this, thanks @sylr and sorry this didn't made it.


[FEATURE] Displaying name of social media platform on hover

Is your feature request related to a problem? Please describe.
Currently, on the home panel of extension, there are a lot of icons which users might not be aware about. This will deteriorate User Experience.
Describe the solution you'd like
To solve the problem mentioned above and improve the UX of the extension, I will add the functionality of displaying name of the social media app instead of the icon when the user hovers over it.
Describe alternatives you've considered
Adding tooltip kind of interface could also have been a solution but as this project uses Vanilla CSS instead of a UI library, the tooltip won't be the best option as it's positioning will always be a problem so the above proposed solution should be the go-to option.
Additional context
https://github.com/Param302/SocialRepo/assets/142862928/1e0038f9-a09a-4ae6-93d6-9f89ea065a10
Please assign this issue to me under GSSOC'24 @Param302 .

I have added a PR for this issue as well. @Param302
Looking forward to being assigned on this issue and getting the PR merged.


!in-place tag

A fairly common problem asked in the help channels involves in-place operations like list.sort() which return None. A simple tag could be used to explain the difference in behaviour between in-place and out-of-place functions (with examples such as sorted() vs list.sort()) and how common issues involving them can be fixed.

Sounds like a good idea, I don't think we have a tag like this currently.

Im interested in implementing this

Im interested in implementing this

👍 I've assigned you


ModuleNotFoundError: No module named 'yolox.data.datasets.vid_classes'

I intended to run the online demo, but I got this bug. How can I solve it? (I have already equipped yolox in my environment)

Please recreate a new conda env for yolov. Directly using yolox env will make python find reference file in YOLOX dir and result in this problem.


Update Spring Dependencies to align with Spring Boot 2.7.0

Update Spring Dependencies to align with Spring Boot 2.7.0. This PR is created by GitHub Actions: https://github.com/Netyyyy/spring-cloud-azure-tools/actions/runs/2494273391

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


Add profiling tests to repo

Add profiling test (using memory-profiler: https://pypi.org/project/memory-profiler/) to repository. To replicate, just execute python3 -m profiling/bench.py. Results should be generated and saved to the *.log files in the profiling directory.

Good job, thank you very much!

close #5


docs(apim): Provide update of API Gateway overview with SHGW v2.2.0

@dlepow
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off