Memory operation

I'm trying to implement a "load in array" operation, so giving an array filled with some values to the "compute" function, which reads and returns the content of array[4]. The generated code seems correct, but the returned value is not:
static void test2()
{
    MIR_context_t fContext = MIR_init();
    MIR_module_t fModule = MIR_new_module(fContext, "Faust");

    // Create 'compute' function
    MIR_type_t res_type = MIR_T_D;
    MIR_item_t fCompute = MIR_new_func(fContext, "compute", 1, &res_type, 1, MIR_T_P, "real_heap");

    // Get 'heap' argument
    MIR_reg_t HEAP = MIR_reg(fContext, "real_heap", fCompute->u.func);

    // Create a local
    MIR_reg_t VAR1 = MIR_new_func_reg(fContext, fCompute->u.func, MIR_T_D, "VAR1");

    // Create and set 'index'
    MIR_reg_t INDEX = MIR_new_func_reg(fContext, fCompute->u.func, MIR_T_I64, "INDEX");

    MIR_append_insn(fContext, fCompute,
                     MIR_new_insn(fContext,
                                  MIR_MOV,
                                  MIR_new_reg_op(fContext, INDEX),
                                  MIR_new_int_op(fContext, 4)));

    // Get the 'heap' content at 'index'
    MIR_append_insn(fContext, fCompute,
                     MIR_new_insn(fContext, MIR_DMOV,
                                   MIR_new_reg_op(fContext, VAR1),
                                   MIR_new_mem_op(fContext, MIR_T_D, 0, HEAP, INDEX, 1)));

    MIR_append_insn(fContext, fCompute, MIR_new_ret_insn(fContext, 1, MIR_new_reg_op(fContext, VAR1)));

    // Finish function
    MIR_finish_func(fContext);

    // Finish module
    MIR_finish_module(fContext);

    MIR_load_module (fContext, fModule);
    MIR_link(fContext, MIR_set_interp_interface, import_resolver);

    // Dump module
    MIR_output(fContext, stderr);

    // Preparing test heap with some values
    double heap[8];
    for (int i = 0; i < 8; i++) {
        heap[i] = (double)i;
        printf("Heap: %f\n", heap[i]);
    }

    MIR_val_t val;
    MIR_interp(fContext, fCompute, &val, 1, (MIR_val_t){.a = (void*)heap});
    printf("Result: %f\n", val.d);

    MIR_finish(fContext);
}

Faust:	module
compute:	func	d, p:real_heap
	local	d:VAR1, i64:INDEX, i64:t1
# 1 arg, 3 locals
	mov	INDEX, 4
	add	t1, real_heap, INDEX
	dmov	VAR1, d:(t1)
	ret	VAR1
	endfunc
	endmodule
Heap: 0.000000
Heap: 1.000000
Heap: 2.000000
Heap: 3.000000
Heap: 4.000000
Heap: 5.000000
Heap: 6.000000
Heap: 7.000000
Result: 0.000000

mov	INDEX, 4
add	t1, real_heap, INDEX
dmov	VAR1, d:(t1)

When you use index it is scaled by the last operand of MIR_new_mem_op which is 1 in your test.  Therefore your MIR code reads from half of the 0th heap double (not just 4th double).  Instead of
MIR_new_mem_op(fContext, MIR_T_D, 0, HEAP, INDEX, 1) you should use MIR_new_mem_op(fContext, MIR_T_D, 0, HEAP, INDEX, 8)
MIR is low level language, it is easy to make a mistake.  Some people generates C code and use c2mir although it slows down compilation a lot and make JIT much bigger.

Working, thanks a lot !
So I understand that I can also write some C and use c2mir to better understand what has to be generated.

So I understand that I can also write some C and use c2mir to better understand what has to be generated.

Yes, you can.  And some people do this.  Such approach makes JIT bigger and slow. Generation of code through MIR API is about 10-15 times faster than through c2mir.  Although c2mir is also 10-15 times faster than gcc -O2 it was never designed to be a fast compiler.
My own plans to implement JIT for Ruby is to use MIR API directly during JIT work and c2mir for translation of C code only during building Ruby (it is an existing C code implementing standard Ruby methods).  During JIT work, the translated C code can be inlined with MIR code generated by MIR API to use inlining and to optimize the result inlined code.

I plan to directly use MIR API. My point what to say: I can write some simple C tests, compile them using c2mir to understand what has too be generated, then directly generate MIR.

I plan to directly use MIR API. My point what to say: I can write some simple C tests, compile them using c2mir to understand what has to be generated, then directly generate MIR.

I like your approach.  I guess it can work for you.  The only trouble is that MIR code generated from C might be hard to read and there are a lot of dead code (it is mostly results of assign-stmts which are never used).


v2.6.0

Typescript Migration Guide
Nuxt 2.5 users may only require to add ts-node to the dependencies

Remove nuxt-ts dependency (2.4 users only)
Add nuxt  and ts-node to dependencies:

yarn: yarn add nuxt ts-node
npm: npm i nuxt ts-node

Add @nuxt/typescript to  devDependencies:

yarn: yarn add -D @nuxt/typescript
npm: npm i @nuxt/typescript

Create an empty tsconfig.json file. Nuxt will automatically generate it with defaults at first run, then you can edit it to fit your needs

Features

feat(babel-preset-app): support specifying core-js version (#5411) (Xin Du (Clark)) (159123fe)
feat(cli): add --quiet option to nuxt generate command (#5357) (Franck Abgrall) (91f4eb04)
feat(typescript): detect typescript based on tsconfig.json (#5412) (Pooya Parsa) (6ffc5c57)

Fixes

fix: unexpected token export in importing babel runtime helper (#5401) (ryota yamamoto) (3b85dd97)
fix: disable node-externals for dev mode (#5414) (Xin Du (Clark)) (a5a16574)
fix(core): call ready to prevent breaking changes (Pooya Parsa) (#5413) (001ba775)
fix(build): disable loading babel.config.js by default (#5365) (Xin Du (Clark)) (64fa4244)
fix(builder): await for renderer to load resources (#5341) (Pooya Parsa) (caf51984)
fix(cli): catch all possible errors thrown from proper-filelock (#5347) (Pim) (39bbe46e)
fix(renderer): retry render if renderer is in loading or created state (#5417) (Pooya Parsa) (8b996959)
fix(vue-app): decode uri in getlocation (#5337) (Johan Roxendal) (77dcfe6e)
fix(vue-app): prevent mounting page twice on redirect (#5361) (noe132) (2d73e8ae)
fix(vue-renderer): add the csp hash if unsafe-inline hasn't been specified (#5387) (Sam Bowler) (97db6a4b)
fix(types): add type definition for typescript.typeCheck (#5326) (Daniel Roe) (2c1444d9)

Refactors

refactor(typescript): only generate tsconfig.json if missing (#5356) (#5367) (Kevin Marrec) (9a3fc8a4)
refactor(vue-renderer): improve ready status error (#5339) (Pooya Parsa) (535327c4)
refactor(webpack): add ability to get webpack config class (#5378) (Damian Stasik) (abf7db1f)

Examples

examples: add docker example (#5430) (Utkarsh Gupta) (3eec1152)
examples(vue-apollo): update to @nuxtjs/apollo 4.x (#5345) (Dmitry Molotkov) (95f2a125)
examples(with-buefy): update example (#5348) (Dmitry Molotkov) (ce66a8cb)
examples(with-element-ui): fix package scripts (#5349) (Dmitry Molotkov) (10812e30)

Chore

chore(postcss): deprecate config support (#5419) (Alexander Lichter) (1bd4fb14)
chore(readme): fix grammar (#5395) (Irvin Lin) (f8d3626c)

Dependency Upgrades

loading-screen: use wss for https (nuxt/loading-screen#4)
loading-screen: fallback to fetch if ws fails (nuxt/loading-screen#6)

Codecov Report

Merging #5352 into 2.x will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             2.x    #5352      +/-   ##
=========================================
- Coverage   95.7%   95.69%   -0.02%
=========================================
  Files         74       74
  Lines       2513     2529      +16
  Branches     639      641       +2
=========================================
+ Hits        2405     2420      +15
- Misses        91       92       +1
  Partials      17       17

Impacted Files
Coverage Δ

packages/utils/src/locking.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderer.js
91.58% <0%> (-0.5%)
:arrow_down:

Continue to review full report at Codecov.

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

Changelog updated

Codecov Report

Merging #5352 into 2.x will increase coverage by 0.42%.
The diff coverage is 94.73%.

@@            Coverage Diff            @@
##             2.x    #5352      +/-   ##
=========================================
+ Coverage   95.7%   96.12%   +0.42%
=========================================
  Files         74       74
  Lines       2513     2555      +42
  Branches     639      650      +11
=========================================
+ Hits        2405     2456      +51
+ Misses        91       83       -8
+ Partials      17       16       -1

Impacted Files
Coverage Δ

packages/config/src/config/build.js
100% <ø> (ø)
:arrow_up:

packages/typescript/src/index.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderer.js
95.56% <100%> (+3.48%)
:arrow_up:

packages/webpack/src/utils/postcss.js
93.22% <100%> (+0.62%)
:arrow_up:

packages/cli/src/imports.js
100% <100%> (ø)
:arrow_up:

packages/cli/src/commands/dev.js
84.61% <100%> (ø)
:arrow_up:

packages/webpack/src/config/client.js
98.18% <100%> (+0.18%)
:arrow_up:

packages/core/src/nuxt.js
94.73% <100%> (+0.29%)
:arrow_up:

packages/builder/src/builder.js
100% <100%> (ø)
:arrow_up:

packages/cli/src/commands/build.js
86.36% <100%> (ø)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #5352 into 2.x will increase coverage by 0.42%.
The diff coverage is 94.73%.

@@            Coverage Diff            @@
##             2.x    #5352      +/-   ##
=========================================
+ Coverage   95.7%   96.12%   +0.42%
=========================================
  Files         74       74
  Lines       2513     2555      +42
  Branches     639      650      +11
=========================================
+ Hits        2405     2456      +51
+ Misses        91       83       -8
+ Partials      17       16       -1

Impacted Files
Coverage Δ

packages/config/src/config/build.js
100% <ø> (ø)
:arrow_up:

packages/typescript/src/index.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderer.js
95.56% <100%> (+3.48%)
:arrow_up:

packages/webpack/src/utils/postcss.js
93.22% <100%> (+0.62%)
:arrow_up:

packages/cli/src/imports.js
100% <100%> (ø)
:arrow_up:

packages/cli/src/commands/dev.js
84.61% <100%> (ø)
:arrow_up:

packages/webpack/src/config/client.js
98.18% <100%> (+0.18%)
:arrow_up:

packages/core/src/nuxt.js
94.73% <100%> (+0.29%)
:arrow_up:

packages/builder/src/builder.js
100% <100%> (ø)
:arrow_up:

packages/cli/src/commands/build.js
86.36% <100%> (ø)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

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

notes updated with migration guide and nuxt-edge guide

Have ever tried with firebase? Errors happened newly like The XMLHttpRequest compatibility library was not found.

Have ever tried with firebase? Errors happened newly like The XMLHttpRequest compatibility library was not found.

@sgmheyhey Did you tried adding xmlhttprequest npm dependency?

@sgmheyhey Did you tried adding xmlhttprequest npm dependency?

No needed with Nuxt.js v2.5.2-25897721.3b85dd97.
And v2.6, I've tried to add  xmlhttprequest but not worked.

No needed with Nuxt.js v2.5.2-25897721.3b85dd97.
And v2.6, I've tried to add xmlhttprequest. But not worked.

@sgmheyhey Please create an issue with the small repository or at least link on the method that you are deploying to the firebase. Sharing custom server.js, nuxt.config and package.json can also help.

Failed to open new issue. :(  https://github.com/nuxt/nuxt.js/issues/5441


KSTokenView resign first responder issue

When resigning the first responder, text in the cell doesn't become tokenized. If I type in a word and then tap in another textField or textView, that text isn't tokenized.
I've tried setting removesTokensOnEndEditing to false but it did nothing

@anthonycastelli text is tokenized only after user press "Done" button in keyboard or any of character specified in tokenizingCharacters array.


Why is there no magnetism

I've set the MAGMOM and ISPIN, why is there no magnetism information out

The magnetism, i.e. the site projected magnetic moments, are only available when you run with LORBIT = 10 or 11.


Level reset to 0

Describe the bug
Using a solo gestalt character, Aasimar Angelkin, Dragonblood Shifter/Armiger Fighter. Upon gaining the first mythic path at the end of act one, and picking up the Master Shapeshifter mythic feat, once we transition to the next act, the character level is reset to 0, forever.
Even if you manually set the character level back to what it was originally, it'll reset once again whenever you transition to another map or reloading a save.
It appears to trigger once you gain the mythic rank 1/feat.
To Reproduce
Steps to reproduce the behavior:

Go to save file, in the Grey Garrison, just before the final fight on act 1.
Click on the Wardstone, go through the dialog options. (I chose 'Cleanse renegade angels option'
Defeat Minagho and her demons, complete her dialog, gain the 1st rank Mythic Feat.
Optional, choose a mythic feat. (I chose Closer to the Abyss and Master Shapeshifter)
Save on a new save, and either reload that same save, or go to act 2.
Once loaded, you character level should be reset to 0.

Expected behavior
Once the bug triggers, your character level, but not your class levels, is reset to 0. Any attempt to change this level is undone once you reload or change map area. The bug appears to be in a loop, constantly resetting you character level to 0.
Save Files
To help us reproduce your issue, please attach a named save file
Please zip it or GitHub will not accept it.
Manual_1058_Gray_Garrison__21_Arodus__VIII__4715__05_33_32.zip
Screenshots
If applicable, add screenshots to help explain your problem.
Settings
Please attach your settings.xml file from the mod folder
Settings.zip
Version Info:

ToyBox Version: 1.4.22

OS: Windows 10 Pro, Build 19044.2728

Version: 21H2

Additional context
The only other mod installed is Modded Achievements, which I seriously doubt is the one causing this problem.

Please ensure that only one of your classes is marked as gestalt.

That solved the issue.
Thou for the record I thought I had only marked one class. I don't know at what point both had become marked.
The fact that they can be, and that leads to such game breaking bugs, seems like something of a design flaw to me.
In either case thank you.


Adjustments to rails testing setup

Some tweaks to the testing system.  If all the tests pass with these, we're probably good.
So, some explanation regarding the changes:
Moving fakeweb fixtures to their own directory
When we started with fakeweb there were only like two, now there's like 10 and it's cluttering up that directory.  Also I remember Rails saying somewhere that "the fixtures directory is for yaml fixtures"
Adding json_expressions
We need a DSL for specifying our responses as we move more and more towards Rails-as-an-API.  This isn't perfect, but there's really no great ones.  It'll do until we can test the serializers directly.
Adding factory_girl
Fixtures are great, and base data is nice to have.  But sometimes you need a bit more oomph, like in the groups tests.  I ran out of users to test all the unique combinations.  Factories solve that very real problem, and if we combine them with fixtures we can get the best of both worlds.
Adding minitest-rails
I'm tired of the shittiness of Test::Unit that I'm forced to use by Rails.  Spec-style assertions are a lot clearer and let(:thing) {} is hella boss.  This plugs MiniTest into Rails as a (hopefully) drop-in replacement.

The one I'm most worried about is minitest-rails, since it has the potential to break the entire test suite in one fell swoop.  json_expressions I'm a bit iffy on, too.  It's really not remarkable, but it's a net improvement so I think it's worth it for now.
FactoryGirl is long overdue and I think we all know it.

Thinking of replacing FakeWeb with WebMock too, because then we could mount the APIv1 rack app and ensure that it never changes (within parameters we can easily specify with json_expressions!)

:clock11: :clock1130: :clock12: :fireworks: :fireworks: :fireworks:
:+1: LGTM

:tanabata_tree: :mahjong: :100: Should I do the WebMock so we can test APIv1?

Go for it :+1:

:+1: Looking good LGTM


error masking should always be enabled

Currently, error masking is only enabled in staging and production environments. It should also be enabled in development mode, so the behavior is as close as possible.

yes

But in dev you also want to be able to look at stack traces to help debugging?

@saihaj Please read the yoga docs 😁 https://www.graphql-yoga.com/docs/features/error-masking#receive-original-error-in-development


Keybase updater fails with "System cannot open the device or file specified" - Due to RAM disk used as temp storage

Keybase GUI Version: 3.1.0-20190307142254+1ebfca5cab
This is really just an issue with msiexec when it's launched from a RAM disk as supplied by imdisk.exe. I use a 4GB RAM disk for my temp files and have the environment variable for TEMP/TMP set to the appropriate directories on R:
Downloader uses this path to download the .MSI file and execute it. Upon trying to extract the package, msiexec.exe fails. Presumably it uses different calls to look for the path, or validate it,  and since this is a 3rd party virtual disk driver it doesn't find it. That's my conjecture.
Solved by changing paths for temp to point to system drive, rebooted and ran keybase update check with no issues. I've not had this problem with any other installers.
OS: Windows 10 Home version 1803 (OS Build 17134.590) 64bit
16GB RAM
Example log entries from MSI installer log:
Action start 13:59:19: INSTALL.
Action 13:59:19: FindRelatedProducts. Searching for related applications
Action start 13:59:19: FindRelatedProducts.
FindRelatedProducts: Found application: {BA03442F-5878-4F04-BB19-9201E67CB436}
Action ended 13:59:19: FindRelatedProducts. Return value 1.
Action 13:59:19: AppSearch. Searching for installed applications
Action start 13:59:19: AppSearch.
AppSearch: Property: WIXNETFX4RELEASEINSTALLED, Signature: NetFx4ReleaseInstalled
Action ended 13:59:19: AppSearch. Return value 1.
Action 13:59:19: SetWIX_IS_NETFRAMEWORK_452_OR_LATER_INSTALLED.
Action start 13:59:19: SetWIX_IS_NETFRAMEWORK_452_OR_LATER_INSTALLED.
Action ended 13:59:19: SetWIX_IS_NETFRAMEWORK_452_OR_LATER_INSTALLED. Return value 1.
Action 13:59:19: LaunchConditions. Evaluating launch conditions
Action start 13:59:19: LaunchConditions.
Action ended 13:59:19: LaunchConditions. Return value 1.
Action 13:59:19: ValidateProductID.
Action start 13:59:19: ValidateProductID.
Action ended 13:59:19: ValidateProductID. Return value 1.
Action 13:59:19: CostInitialize. Computing space requirements
Action start 13:59:19: CostInitialize.
Action ended 13:59:19: CostInitialize. Return value 1.
Action 13:59:19: FileCost. Computing space requirements
Action start 13:59:19: FileCost.
Action ended 13:59:19: FileCost. Return value 1.
Action 13:59:19: CostFinalize. Computing space requirements
Action start 13:59:19: CostFinalize.
Action ended 13:59:23: CostFinalize. Return value 1.
Action 13:59:23: MigrateFeatureStates. Migrating feature states from related applications
Action start 13:59:23: MigrateFeatureStates.
Action ended 13:59:24: MigrateFeatureStates. Return value 1.
Action 13:59:24: ExecuteAction.
Action start 13:59:24: ExecuteAction.
The system cannot open the device or file specified.

Example entries from Keybase updater log:
2019/03/08 13:59:18 DEBG Wrote to C:\Users\Jedi\AppData\Local\Keybase\updater.json
2019/03/08 13:59:18 DEBG Execute: msiexec.exe [/i R:\AppData\Local\Temp\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ\Keybase_3.1.0-20190307141824+1ebfca5cab.amd64.msi /log R:\AppData\Local\Temp\KeybaseMsi_20190308135918.log]
2019/03/08 14:01:38 DEBG Executed msiexec.exe [/i R:\AppData\Local\Temp\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ\Keybase_3.1.0-20190307141824+1ebfca5cab.amd64.msi /log R:\AppData\Local\Temp\KeybaseMsi_20190308135918.log]
2019/03/08 14:01:38 INFO [Apply error: %v exit status 1603]
2019/03/08 14:01:38 DEBG Remove temporary directory: "R:\\AppData\\Local\\Temp\\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ"
2019/03/08 14:01:38 INFO Reporting: https://api.keybase.io/_/api/1.0/pkg/error.json map[request_id:[4680d05a032365db9314a31f] version:[3.0.0-20190205103647+6394d03e6c] upd_version:[0.3.5] error_type:[apply] description:[Update Error (apply): exit status 1603] install_id:[22299246d2c0ef9c57dfd5d5101f165fd70a32e96a9cfa1d]]
2019/03/08 14:01:39 INFO Exiting for restart

Error 1603 from msiexec is the generic "Something failed" useless message from Microserf. In addition the Keybase updater displays a final error code 2755, which ultimately seems to be another generic and useless catch-all error code.

so, R:\AppData\Local\Temp exists and os wrieable, and the environment variables TEMP and TMP are set to it?
Can you do a keybase log send so we can see the whole log?

Correct, R: is the RAM drive and 100% accessible and writable. Definitely not full either.
=== Logging started: 3/8/2019  13:59:19 ===
Action 13:59:19: INSTALL.
Action start 13:59:19: INSTALL.
Action 13:59:19: FindRelatedProducts. Searching for related applications
Action start 13:59:19: FindRelatedProducts.
FindRelatedProducts: Found application: {BA03442F-5878-4F04-BB19-9201E67CB436}
Action ended 13:59:19: FindRelatedProducts. Return value 1.
Action 13:59:19: AppSearch. Searching for installed applications
Action start 13:59:19: AppSearch.
AppSearch: Property: WIXNETFX4RELEASEINSTALLED, Signature: NetFx4ReleaseInstalled
Action ended 13:59:19: AppSearch. Return value 1.
Action 13:59:19: SetWIX_IS_NETFRAMEWORK_452_OR_LATER_INSTALLED.
Action start 13:59:19: SetWIX_IS_NETFRAMEWORK_452_OR_LATER_INSTALLED.
Action ended 13:59:19: SetWIX_IS_NETFRAMEWORK_452_OR_LATER_INSTALLED. Return value 1.
Action 13:59:19: LaunchConditions. Evaluating launch conditions
Action start 13:59:19: LaunchConditions.
Action ended 13:59:19: LaunchConditions. Return value 1.
Action 13:59:19: ValidateProductID.
Action start 13:59:19: ValidateProductID.
Action ended 13:59:19: ValidateProductID. Return value 1.
Action 13:59:19: CostInitialize. Computing space requirements
Action start 13:59:19: CostInitialize.
Action ended 13:59:19: CostInitialize. Return value 1.
Action 13:59:19: FileCost. Computing space requirements
Action start 13:59:19: FileCost.
Action ended 13:59:19: FileCost. Return value 1.
Action 13:59:19: CostFinalize. Computing space requirements
Action start 13:59:19: CostFinalize.
Action ended 13:59:23: CostFinalize. Return value 1.
Action 13:59:23: MigrateFeatureStates. Migrating feature states from related applications
Action start 13:59:23: MigrateFeatureStates.
Action ended 13:59:24: MigrateFeatureStates. Return value 1.
Action 13:59:24: ExecuteAction.
Action start 13:59:24: ExecuteAction.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
The system cannot open the device or file specified.
DEBUG: Error 2755:  Server returned unexpected error 110 attempting to install package R:\AppData\Local\Temp\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ\Keybase_3.1.0-20190307141824+1ebfca5cab.amd64.msi.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755. The arguments are: 110, R:\AppData\Local\Temp\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ\Keybase_3.1.0-20190307141824+1ebfca5cab.amd64.msi,
MSI (c) (88:B4) [14:01:38:867]: Product: Keybase -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755. The arguments are: 110, R:\AppData\Local\Temp\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ\Keybase_3.1.0-20190307141824+1ebfca5cab.amd64.msi,

Action ended 14:01:38: ExecuteAction. Return value 3.
Action ended 14:01:38: INSTALL. Return value 3.
Property(C): UpgradeCode = {C118F7EC-9A1D-4FF1-91F5-15D208499D7B}
Property(C): WIXNETFX4RELEASEINSTALLED = #461808
Property(C): INSTALLFOLDER = C:\Users\redacted\AppData\Local\Keybase\
Property(C): GuiDir = C:\Users\redacted\AppData\Local\Keybase\Gui\
Property(C): dirBCEEF4B5A5E6A966F8D5F4C6F8FAA534 = C:\Users\redacted\AppData\Local\Keybase\Gui\locales\
Property(C): GuiResourcesDir = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\
Property(C): dir5295E69FA872F199E656853FCEC4D7AD = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\app\
Property(C): dirB1609A4AD5969BD7962D3C70844785B3 = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\app\desktop\
Property(C): dirA5664FC3B87A7D18DED9071D95B897FF = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\app\desktop\dist\
Property(C): dirB8B1A888CDE5444D0239F26F05784B18 = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\app\images\
Property(C): dirE1BA13F516B38622AE32BD20CDED0B7B = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\app\images\icons\
Property(C): dir1C0628012E13D4C0FE3CA814726C5593 = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\app\images\illustrations\
Property(C): dir003A9766F1476092211CA4C87B3515BC = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\app\images\install\
Property(C): dir2BDFEEE228A1B096F41182A5A18F10C1 = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\app\images\menubarIcon\
Property(C): dir7E8B5C9C779EADCBECD073B7CA409F56 = C:\Users\redacted\AppData\Local\Keybase\Gui\resources\app\images\nav\
Property(C): dirF1C57D0509574A51289D374EB70B4FF0 = C:\Users\redacted\AppData\Local\Keybase\Gui\swiftshader\
Property(C): ProgramMenuFolder = C:\Users\redacted\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\
Property(C): StartupFolder = C:\Users\redacted\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\
Property(C): WIX_IS_NETFRAMEWORK_452_OR_LATER_INSTALLED = 1
Property(C): LocalAppDataFolder = C:\Users\redacted\AppData\Local\
Property(C): TARGETDIR = D:\
Property(C): SystemFolder = C:\WINDOWS\SysWOW64\
Property(C): SourceDir = R:\AppData\Local\Temp\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ\
Property(C): ARPPRODUCTICON = ProductIcon
Property(C): ARPHELPLINK = https://www.keybase.io
Property(C): ARPURLINFOABOUT = https://www.keybase.io
Property(C): MSIRESTARTMANAGERCONTROL = Disable
Property(C): EXECUTABLETARGET = bin
Property(C): MsiLogging = oicewarmup
Property(C): Setup = Setup
Property(C): ButtonText_No = &No
Property(C): ButtonText_Yes = &Yes
Property(C): ButtonText_Install = &Install
Property(C): ButtonText_Cancel = Cancel
Property(C): BannerBitmap = bannrbmp
Property(C): Wizard = Setup Wizard
Property(C): InfoIcon = info
Property(C): Manufacturer = Keybase, Inc.
Property(C): ProductCode = {A263C2BB-A3E3-4A60-9FBD-F4A889CB8BA9}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Keybase
Property(C): ProductVersion = <IP_ADDRESS>
Property(C): SecureCustomProperties = WIX_DOWNGRADE_DETECTED;WIX_IS_NETFRAMEWORK_452_OR_LATER_INSTALLED;WIX_UPGRADE_DETECTED;WIXNETFX4RELEASEINSTALLED
Property(C): WIX_UPGRADE_DETECTED = {BA03442F-5878-4F04-BB19-9201E67CB436}
Property(C): MsiLogFileLocation = R:\AppData\Local\Temp\KeybaseMsi_20190308135918.log
Property(C): PackageCode = {233A3CB4-C269-47D8-B20D-E369996C3CEF}
Property(C): ProductState = -1
Property(C): PackagecodeChanging = 1
Property(C): CURRENTDIRECTORY = C:\Users\redacted\AppData\Local\Keybase
Property(C): CLIENTUILEVEL = 0
Property(C): CLIENTPROCESSID = 15240
Property(C): MsiSystemRebootPending = 1
Property(C): VersionDatabase = 500
Property(C): VersionMsi = 5.00
Property(C): VersionNT = 603
Property(C): VersionNT64 = 603
Property(C): WindowsBuild = 9600
Property(C): ServicePackLevel = 0
Property(C): ServicePackLevelMinor = 0
Property(C): MsiNTProductType = 1
Property(C): MsiNTSuitePersonal = 1
Property(C): WindowsFolder = C:\WINDOWS\
Property(C): WindowsVolume = C:\
Property(C): System64Folder = C:\WINDOWS\system32\
Property(C): RemoteAdminTS = 1
Property(C): TempFolder = R:\AppData\Local\Temp\
Property(C): ProgramFilesFolder = C:\Program Files (x86)\
Property(C): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(C): ProgramFiles64Folder = C:\Program Files\
Property(C): CommonFiles64Folder = C:\Program Files\Common Files\
Property(C): AppDataFolder = C:\Users\redacted\AppData\Roaming\
Property(C): FavoritesFolder = C:\Users\redacted\Favorites\
Property(C): NetHoodFolder = C:\Users\redacted\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(C): PersonalFolder = C:\Users\redacted\Documents\
Property(C): PrintHoodFolder = C:\Users\redacted\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(C): RecentFolder = C:\Users\redacted\AppData\Roaming\Microsoft\Windows\Recent\
Property(C): SendToFolder = C:\Users\redacted\AppData\Roaming\Microsoft\Windows\SendTo\
Property(C): TemplateFolder = C:\Users\redacted\AppData\Roaming\Microsoft\Windows\Templates\
Property(C): CommonAppDataFolder = C:\ProgramData\
Property(C): MyPicturesFolder = C:\Users\redacted\Pictures\
Property(C): AdminToolsFolder = C:\Users\redacted\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(C): StartMenuFolder = C:\Users\redacted\AppData\Roaming\Microsoft\Windows\Start Menu\
Property(C): DesktopFolder = C:\Users\redacted\Desktop\
Property(C): FontsFolder = C:\WINDOWS\Fonts\
Property(C): GPTSupport = 1
Property(C): OLEAdvtSupport = 1
Property(C): ShellAdvtSupport = 1
Property(C): MsiAMD64 = 6
Property(C): Msix64 = 6
Property(C): Intel = 6
Property(C): PhysicalMemory = 16325
Property(C): VirtualMemory = 11567
Property(C): LogonUser = redacted
Property(C): UserSID = redacted
Property(C): UserLanguageID = 1033
Property(C): ComputerName = redacted
Property(C): SystemLanguageID = 1033
Property(C): ScreenX = 1920
Property(C): ScreenY = 1080
Property(C): CaptionHeight = 22
Property(C): BorderTop = 1
Property(C): BorderSide = 1
Property(C): TextHeight = 16
Property(C): TextInternalLeading = 3
Property(C): ColorBits = 32
Property(C): TTCSupport = 1
Property(C): Time = 14:01:38
Property(C): Date = 3/8/2019
Property(C): MsiNetAssemblySupport = 4.7.3056.0
Property(C): MsiWin32AssemblySupport = 6.3.17134.1
Property(C): RedirectedDllSupport = 2
Property(C): USERNAME = Windows User
Property(C): DATABASE = R:\AppData\Local\Temp\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ\Keybase_3.1.0-20190307141824+1ebfca5cab.amd64.msi
Property(C): OriginalDatabase = R:\AppData\Local\Temp\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ\Keybase_3.1.0-20190307141824+1ebfca5cab.amd64.msi
Property(C): SOURCEDIR = R:\AppData\Local\Temp\KeybaseUpdater.THPOYMXA6WYJIDL3QANQ26MZMCF7Q5QBPYBGNS3WK5EXGPAEKPZQ\
Property(C): VersionHandler = 5.00
Property(C): MIGRATE = {BA03442F-5878-4F04-BB19-9201E67CB436}
Property(C): EXECUTEACTION = INSTALL
Property(C): ACTION = INSTALL
Property(C): UILevel = 5
Property(C): ROOTDRIVE = D:\
Property(C): CostingComplete = 0
Property(C): OutOfDiskSpace = 0
Property(C): OutOfNoRbDiskSpace = 0
Property(C): PrimaryVolumeSpaceAvailable = 0
Property(C): PrimaryVolumeSpaceRequired = 0
Property(C): PrimaryVolumeSpaceRemaining = 0
Property(C): INSTALLLEVEL = 1
=== Logging stopped: 3/8/2019  14:01:38 ===
MSI (c) (88:B4) [14:01:38:874]: Windows Installer installed the product. Product Name: Keybase. Product Version: <IP_ADDRESS>. Product Language: 1033. Manufacturer: Keybase, Inc.. Installation success or error status: 1603.

Can you verify that %windir%\Installer exists and is writeable? Someone fixed this error by creating that after it had gone missing.
Other than that, I double checked that the installer works with nonstandard TEMP/TMP defined - there is not much we can do if the msi system can't read your ram disk.

I checked and %windir%\Installer exists and is writeable, though it requires admin privs to write to. Which I believe is normal.
I don't expect there is much that can be done, as this lies in msiexec.msi but it may be possible to pre-detect the condition if there's a way to test the paths for temp/tmp and see if they are physical or non-physical disks. For exmaple, I'm not sure if this same problem would occur if they were pointed to a network share.
Ultimately yes this is an issue in the installer engine, but I felt like reporting it to make the team aware, because I hadn't gotten it in previous updates.

Are you saying that keybase was able to update in the past with your temp set to the ramdisk?
Thanks for the detailed report.

Yes, I've been using a RAM disk temp directory for at least a year now. Looks like it successfully updated multiple times, including last month:
2019/02/05 22:58:14 DEBG Last update time (is recent? false): 2019-02-05 21:58:11.0149548 -0500 EST
2019/02/05 22:58:14 DEBG Set last update time
2019/02/05 22:58:14 DEBG Execute: C:\Users\redacted\AppData\Local\Keybase\keybase.exe [version -S]
2019/02/05 22:58:14 DEBG Executed C:\Users\redacted\AppData\Local\Keybase\keybase.exe [version -S]
2019/02/05 22:58:14 DEBG Execute: cmd [/c ver]
2019/02/05 22:58:14 DEBG Executed cmd [/c ver]
2019/02/05 22:58:14 INFO Checking for update, current version is 2.13.2-20190122174230+6bb157b5d0
2019/02/05 22:58:14 INFO Using updater source: Keybase.io
2019/02/05 22:58:14 DEBG Using options: updater.UpdateOptions{Version:"2.13.2-20190122174230+6bb157b5d0", Platform:"windows", DestinationPath:"C:\\Users\\redacted\\AppData\\Local\\Keybase\\", URL:"", Channel:"", Env:"prod", Arch:"Intel64", Force:false, OSVersion:"Microsoft Windows [Version 10.0.17134.523]", UpdaterVersion:"0.3.5", IgnoreSnooze:false}
2019/02/05 22:58:14 INFO Request "https://api.keybase.io/_/api/1.0/pkg/update.json?arch=Intel64&auto_update=0&ignore_snooze=0&install_id=22299246d2c0ef9c57dfd5d5101f165fd70a32e96a9cfa1d&os_version=Microsoft+Windows+%5BVersion+10.0.17134.523%5D&platform=windows&run_mode=prod&upd_version=0.3.5&version=2.13.2-20190122174230%2B6bb157b5d0"
2019/02/05 22:58:14 DEBG Received update response: updater.Update{Version:"3.0.0-20190205103647+6394d03e6c", Name:"v3.0.0-20190205103647+6394d03e6c", Description:"• New reaction bar. Quickly add reactions by hovering over any message.\n• A new clearer and faster way to start a new conversation\n• New slash commands. Hit / to see a list of useful shortcuts\n• Set short term retention policies on teams and direct messages\n• Better 'who is typing' indicator\n\nBugfixes:\n• Menubar widget more accurately shows logging in state\n• Fixed 'empty amount' errors\n• Fix for attachment saving failing\n• Images in chat url previews are clickable now\n• Better waiting indicators in the teams tab\n• Startup screen could be stretched on some screens\n", InstallID:"22299246d2c0ef9c57dfd5d5101f165fd70a32e96a9cfa1d", RequestID:"8a8197098bbc2294c6eef21f", Type:0, PublishedAt:1549363007000, Props:[]updater.Property(nil), Asset:(*updater.Asset)(0xc042090550), NeedUpdate:true}
2019/02/05 22:58:14 INFO Got update with version: 3.0.0-20190205103647+6394d03e6c
2019/02/05 22:58:14 DEBG [Prompt for update]
2019/02/05 22:58:14 DEBG Auto update: false (set=true autoOverride=false)
2019/02/05 22:58:14 DEBG Execute: C:\Users\redacted\AppData\Local\Keybase\prompter.exe [{"title":"Keybase Update: Version 3.0.0-20190205103647+6394d03e6c","message":"The version you are currently running (2.13.2-20190122174230+6bb157b5d0) is outdated.","description":"• New reaction bar. Quickly add reactions by hovering over any message.\n• A new clearer and faster way to start a new conversation\n• New slash commands. Hit / to see a list of useful shortcuts\n• Set short term retention policies on teams and direct messages\n• Better 'who is typing' indicator\n\nBugfixes:\n• Menubar widget more accurately shows logging in state\n• Fixed 'empty amount' errors\n• Fix for attachment saving failing\n• Images in chat url previews are clickable now\n• Better waiting indicators in the teams tab\n• Startup screen could be stretched on some screens\n","autoUpdate":false,"outPath":"R:\\AppData\\Local\\Temp\\updatePrompt46MIGXKUAJIJHRHL44IK5L44ABVB43QLQDW37AMXANXZOXTJXD3Q"}]
2019/02/05 23:54:44 DEBG Executed C:\Users\redacted\AppData\Local\Keybase\prompter.exe [{"title":"Keybase Update: Version 3.0.0-20190205103647+6394d03e6c","message":"The version you are currently running (2.13.2-20190122174230+6bb157b5d0) is outdated.","description":"• New reaction bar. Quickly add reactions by hovering over any message.\n• A new clearer and faster way to start a new conversation\n• New slash commands. Hit / to see a list of useful shortcuts\n• Set short term retention policies on teams and direct messages\n• Better 'who is typing' indicator\n\nBugfixes:\n• Menubar widget more accurately shows logging in state\n• Fixed 'empty amount' errors\n• Fix for attachment saving failing\n• Images in chat url previews are clickable now\n• Better waiting indicators in the teams tab\n• Startup screen could be stretched on some screens\n","autoUpdate":false,"outPath":"R:\\AppData\\Local\\Temp\\updatePrompt46MIGXKUAJIJHRHL44IK5L44ABVB43QLQDW37AMXANXZOXTJXD3Q"}]
2019/02/05 23:54:44 DEBG Update prompt response: &updater.UpdatePromptResponse{Action:"apply", AutoUpdate:false, SnoozeDuration:0}
2019/02/05 23:54:44 DEBG Writing to C:\Users\redacted\AppData\Local\Keybase\updater.json
2019/02/05 23:54:44 DEBG Temporary file generated: C:\Users\redacted\AppData\Local\Keybase\updater.json-GTFPCG4UUU3TN557OHJGDFDOFLIKB44SDYRF4DFEK7QNQHCNY53A
2019/02/05 23:54:44 DEBG Wrote to C:\Users\redacted\AppData\Local\Keybase\updater.json
2019/02/05 23:54:44 INFO Reporting: https://api.keybase.io/_/api/1.0/pkg/act.json map[action:[apply] auto_update:[0] install_id:[22299246d2c0ef9c57dfd5d5101f165fd70a32e96a9cfa1d] request_id:[8a8197098bbc2294c6eef21f] version:[2.13.2-20190122174230+6bb157b5d0] upd_version:[0.3.5]]
2019/02/05 23:54:44 DEBG Creating: R:\AppData\Local\Temp\KeybaseUpdater.OJA77U7TAUEX7JB5NGN6QCGDGU3FOVURXIQZPCOVBGEAY5K5D6FQ

2019/02/05 23:54:44 INFO Request https://prerelease.keybase.io/windows/Keybase_3.0.0-20190205103647%2B6394d03e6c.amd64.msi
2019/02/05 23:54:44 INFO Downloading to R:\AppData\Local\Temp\KeybaseUpdater.OJA77U7TAUEX7JB5NGN6QCGDGU3FOVURXIQZPCOVBGEAY5K5D6FQ\Keybase_3.0.0-20190205103647+6394d03e6c.amd64.msi.download
2019/02/05 23:55:05 INFO Downloaded 178679808 bytes
2019/02/05 23:55:05 INFO Verified digest: bfe8e32e7936ba33ab98bdcf7a55124283a19e2b6c6b71b666bc601064d32b90 (R:\AppData\Local\Temp\KeybaseUpdater.OJA77U7TAUEX7JB5NGN6QCGDGU3FOVURXIQZPCOVBGEAY5K5D6FQ\Keybase_3.0.0-20190205103647+6394d03e6c.amd64.msi.download)
2019/02/05 23:55:05 INFO Moving R:\AppData\Local\Temp\KeybaseUpdater.OJA77U7TAUEX7JB5NGN6QCGDGU3FOVURXIQZPCOVBGEAY5K5D6FQ\Keybase_3.0.0-20190205103647+6394d03e6c.amd64.msi.download to R:\AppData\Local\Temp\KeybaseUpdater.OJA77U7TAUEX7JB5NGN6QCGDGU3FOVURXIQZPCOVBGEAY5K5D6FQ\Keybase_3.0.0-20190205103647+6394d03e6c.amd64.msi
2019/02/05 23:55:05 INFO Verify asset: R:\AppData\Local\Temp\KeybaseUpdater.OJA77U7TAUEX7JB5NGN6QCGDGU3FOVURXIQZPCOVBGEAY5K5D6FQ\Keybase_3.0.0-20190205103647+6394d03e6c.amd64.msi
2019/02/05 23:55:05 INFO Signed by deaa8ae7d06ea9aa49cc678ec49f2b1e1dddb63683e384db539a8649c47925f9
2019/02/05 23:55:05 DEBG Valid KID: deaa8ae7d06ea9aa49cc678ec49f2b1e1dddb63683e384db539a8649c47925f9
2019/02/05 23:55:05 INFO [Before apply]
2019/02/05 23:55:05 DEBG Execute: C:\Users\redacted\AppData\Local\Keybase\keybase.exe [update check-in-use]
2019/02/05 23:55:05 DEBG Executed C:\Users\redacted\AppData\Local\Keybase\keybase.exe [update check-in-use]
2019/02/05 23:55:05 INFO [Applying update]
2019/02/05 23:55:05 DEBG Execute: C:\Users\redacted\AppData\Local\Keybase\keybaserq.exe [C:\Users\redacted\AppData\Local\Keybase\keybase.exe ctl stop]
2019/02/05 23:55:05 DEBG Executed C:\Users\redacted\AppData\Local\Keybase\keybaserq.exe [C:\Users\redacted\AppData\Local\Keybase\keybase.exe ctl stop]
2019/02/05 23:55:06 INFO Terminating any existing programs we will be updating
2019/02/05 23:55:06 INFO Terminating C:\Users\redacted\AppData\Local\Keybase\DokanSetup_redist.exe
2019/02/05 23:55:07 INFO Terminating C:\Users\redacted\AppData\Local\Keybase\git-remote-keybase.exe
2019/02/05 23:55:07 INFO Terminating C:\Users\redacted\AppData\Local\Keybase\kbfsdokan.exe
2019/02/05 23:55:07 INFO Terminating C:\Users\redacted\AppData\Local\Keybase\kbnm.exe
2019/02/05 23:55:07 INFO Terminating C:\Users\redacted\AppData\Local\Keybase\keybase.exe
2019/02/05 23:55:07 INFO Terminating C:\Users\redacted\AppData\Local\Keybase\keybaserq.exe
2019/02/05 23:55:07 INFO Terminating C:\Users\redacted\AppData\Local\Keybase\prompter.exe
2019/02/05 23:55:07 INFO Terminating C:\Users\redacted\AppData\Local\Keybase\upd.exe
2019/02/05 23:55:07 DEBG Searching OS for 0
2019/02/05 23:55:07 ERR  Error terminating 0: Error finding OS process: OpenProcess: The parameter is incorrect.
2019/02/05 23:55:07 INFO Terminating C:\Users\redacted\AppData\Local\Keybase\Gui\Keybase.exe
2019/02/05 23:55:07 DEBG Writing to C:\Users\redacted\AppData\Local\Keybase\updater.json
2019/02/05 23:55:07 DEBG Temporary file generated: C:\Users\redacted\AppData\Local\Keybase\updater.json-WUPQMNSVB64RH2Z4IZHYRVNNGCURN4MJGZ7F7LAV2QFVXKU4MVDQ
2019/02/05 23:55:07 DEBG Wrote to C:\Users\redacted\AppData\Local\Keybase\updater.json
2019/02/05 23:55:07 DEBG Execute: msiexec.exe [/i R:\AppData\Local\Temp\KeybaseUpdater.OJA77U7TAUEX7JB5NGN6QCGDGU3FOVURXIQZPCOVBGEAY5K5D6FQ\Keybase_3.0.0-20190205103647+6394d03e6c.amd64.msi /log R:\AppData\Local\Temp\KeybaseMsi_20190205235507.log]
2019/02/05 23:55:31 INFO Updater 0.3.5
2019/02/05 23:55:31 DEBG Last update time (is recent? true): 2019-02-05 22:58:14.5458852 -0500 EST
2019/02/05 23:55:31 DEBG Starting (ticker 1h0m0s)
2019/02/05 23:55:32 INFO Updater 0.3.5
2019/02/05 23:55:32 DEBG Last update time (is recent? true): 2019-02-05 22:58:14.5458852 -0500 EST
2019/02/05 23:55:32 DEBG Starting (ticker 1h0m0s)
2019/02/06 00:55:32 DEBG Checking for update (ticker)
2019/02/06 00:55:32 DEBG Set last update time
2019/02/06 00:55:32 DEBG Execute: C:\Users\redacted\AppData\Local\Keybase\keybase.exe [version -S]
2019/02/06 00:55:32 DEBG Executed C:\Users\redacted\AppData\Local\Keybase\keybase.exe [version -S]
2019/02/06 00:55:32 DEBG Execute: cmd [/c ver]
2019/02/06 00:55:32 DEBG Executed cmd [/c ver]
2019/02/06 00:55:32 INFO Checking for update, current version is 3.0.0-20190205103647+6394d03e6c
2019/02/06 00:55:32 INFO Using updater source: Keybase.io
2019/02/06 00:55:32 DEBG Using options: updater.UpdateOptions{Version:"3.0.0-20190205103647+6394d03e6c", Platform:"windows", DestinationPath:"C:\\Users\\redacted\\AppData\\Local\\Keybase\\", URL:"", Channel:"", Env:"prod", Arch:"Intel64", Force:false, OSVersion:"Microsoft Windows [Version 10.0.17134.523]", UpdaterVersion:"0.3.5", IgnoreSnooze:false}
2019/02/06 00:55:32 INFO Request "https://api.keybase.io/_/api/1.0/pkg/update.json?arch=Intel64&auto_update=0&ignore_snooze=0&install_id=22299246d2c0ef9c57dfd5d5101f165fd70a32e96a9cfa1d&os_version=Microsoft+Windows+%5BVersion+10.0.17134.523%5D&platform=windows&run_mode=prod&upd_version=0.3.5&version=3.0.0-20190205103647%2B6394d03e6c"
2019/02/06 00:55:32 DEBG Received update response: updater.Update{Version:"3.0.0-20190205103647+6394d03e6c", Name:"v3.0.0-20190205103647+6394d03e6c", Description:"• New reaction bar. Quickly add reactions by hovering over any message.\n• A new clearer and faster way to start a new conversation\n• New slash commands. Hit / to see a list of useful shortcuts\n• Set short term retention policies on teams and direct messages\n• Better 'who is typing' indicator\n\nBugfixes:\n• Menubar widget more accurately shows logging in state\n• Fixed 'empty amount' errors\n• Fix for attachment saving failing\n• Images in chat url previews are clickable now\n• Better waiting indicators in the teams tab\n• Startup screen could be stretched on some screens\n", InstallID:"22299246d2c0ef9c57dfd5d5101f165fd70a32e96a9cfa1d", RequestID:"", Type:0, PublishedAt:1549363007000, Props:[]updater.Property(nil), Asset:(*updater.Asset)(0xc042144500), NeedUpdate:false}

I have been avoiding installing the Microsoft October update due to its numerous serious problems, but eventually they force-installed it on my system. This could be a result of policy/permission changes. This seems to correlate to the change in OS version from what it was on Feb 2nd 2019: Microsoft Windows [Version 10.0.17134.523] to what it updated to around Feb 15th 2019: Microsoft Windows [Version 10.0.17134.590]
I think this could be addressed then, if so inclined, by a logic check of OS version before launching installer, and maybe throw-up a warning. I've seen a few other people complaining about this recent update and RAM disk temp directories.

this updater is literally the only one that has problems with my ram drive. having to redownload the complete installer every time you guys release a new version really sucks, would be great if you could fix your updater

From what I've read recently on imdisk's forum this is really a Microsoft bug. Supposedly there's an MSU out that addresses it but the MSU won't even install on my system, :/
https://sourceforge.net/p/imdisk-toolkit/discussion/general/thread/2e07838286/
I think this should be marked as not-a-bug in keybase, but a known issue with the installer and recent MS updates. Just part of a vast litany of cluster-fraks from the October Windows 10 update fiasco, :(

For anyone seeing a similar issue, I can confirm that, as of now, this problem has not been explicitly and permanently fixed. Here's a description of what I believe to be the underlying problem: http://reboot.pro/topic/22008-getfinalpathnamebyhandle-fails-with-error-invalid-function/
tl;dr your ramdisk (probably imdisk) is disallowing a low-level file operation (GetFinalPathNameByHandle) that our install tool (msi) uses. The good news is that there's another ramdisk creation tool that does not error: https://arsenalrecon.com/downloads/ or for a cli tool (aim_ll which is very similar to the imdisk tool) https://github.com/ArsenalRecon/Arsenal-Image-Mounter/tree/master/Command line applications
Sorry for the inconvenience.


Add and update tests for midstream exception policy bug 5825 - v3

Previous (draft) PR: https://github.com/OISF/suricata-verify/pull/1223
Changes:

add tests 'drop-flow' in ids mode.
tests for bug-5825 (midstream exception policy config conflict) added into dedicated directory
add a note to existing test that triggers bug 6109 about reject behavior in ids
add a suricata.json log to 'exception-policy-midstream-03' so we can check the config/warning messages (there seems to be a bug with 'SCLogConfig')

Obs: 'exception-policy-ids-disabled-reject' fails (bug 6109)
Suricata PR: https://github.com/OISF/suricata/pull/8952

Replaced by: https://github.com/OISF/suricata-verify/pull/1230


Blog app - controllers specs

This is a PR for adding tests to the user and post controller

Add test and user spec to test each controller
Test if the correct template is rendered
Test if the connection is successful
Test if the correct placeholder is displayed

Thank you for reviewing and approving my project


Add v1beta2 support to policyrules.go + basic unit test

This PR is stacked on #67. It represents the small change in code logic to support v1beta2. The diff between PR #67 and this one represents the changes that this PR actually introduces. As far as I understand it, the only difference between API versions v1beta1 and v1beta2 is the addition of the endPort field for a port specification.

I mistakenly understood comments from @zeeke in #67 to be requesting separate PRs for different parts of supporting v1beta2. Instead, he was only asking me to split various of the changes into distinct commits in that PR. Closing this PR, and I will put all of the changes back into #67, but broken out into more discreet commits.


Updated information for AzurePowerShell@5

It would be great to get the parameters etc. updated for version 5. The current covers version 4.
Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fb215324-b1a0-93b5-5022-4bcc7da93bb7
Version Independent ID: 9eb2977b-ac34-9d53-670e-04fa027bc8e4
Content: Azure PowerShell task - Azure Pipelines
Content Source: docs/pipelines/tasks/deploy/azure-powershell.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

The merged PR above addresses this issue.


Levels are not grouped in the same pyramid if their origins differ slightly

Some DICOM WSI images have levels with slightly differing origin coordinates. An example is openslide.cs.cmu.edu/download/openslide-testdata/DICOM/Leica-4.zip. Currently this leads to the levels being grouped into separate pyramids in wsidicom.series.pyramids.Pyramids._group_instances_into_pyramids.
Here is a small patch doing greedy max diameter clustering that would solve this. I could adjust it and make a PR if desired.
Minimal example:
import os
from wsidicom import WsiDicom

# Prerequisite: download and extract the Leica-4 test image at `PATH`:
# https://openslide.cs.cmu.edu/download/openslide-testdata/DICOM/Leica-4.zip
PATH = "Leica-4"

slide = WsiDicom.open(PATH)
print(slide.levels)  # Only one level.
print("Number of pyramids:", len(slide._pyramids))  # There are 3 separate pyramids.
print(
    "Level dimensions according to wsidicom:",
    tuple((lvl.size.width, lvl.size.height) for lvl in slide.levels),
)

# -------- for reference: open the image with openslide --------
from openslide import OpenSlide
slide_openslide = OpenSlide(
    next(os.path.join(PATH, f) for f in os.listdir(PATH) if f.endswith(".dcm"))
)
print("Level dimensions according to openslide:", slide_openslide.level_dimensions)

As a note, the dicomslide package also implements a pyramid tolerance parameter.
(For the particular Leica-4 image mentioned above, dicomslide fails with an error, because it identifies the thumbnail file <IP_ADDRESS>.4.1.36533.1881662823325113479691652532302192524914036.dcm as a level; if one removes that file, dicomslide loads the image fine, grouping all levels into one pyramid.)

Hi @jleuschn,
This sounds like reasonable change, please make a merge requests. Some suggestions:

Make the threshold a setting like focal_plane_distance_threshold.
I have added Leica-4 as test data, so it would be nice to get some tests for reading regions etc.

Thanks!


Enhance input processing

Enhance input processing to support 3 different options:

No processing on the input
Input payloads will be ignored

Process
Input payloads will be processed, and Amazon Echo Hub will save the states, but without outputting the payload

Process and output
Input payloads will be processed, and output will be passed to all available devices.

Thanks, @Barabba11
I've checked the @verjus implementation. Mine is similar, and I've just summarized it in a single dropdown instead of two checkboxes.

Hello Datech,
First, I am very impressed with your code. Thank you for making it publicly available.
Please take a look at the small modifications I made in this fork. One modification achieves a similar result but dynamically, instead of relying on a static setting, by relying on the content of the topic in the input message. If the topic is empty, nothing is passed through in output (only the state is updated). If the topic is set (e.g. topic=brightness), the corresponding state is updated and passed in output.
Other potentially interesting modifications are discussed here.

Can somebody kindly tell me how is useful to process an input payload but don't output it? How can be useful to update something on HUB? (what it updates? It's a just a transparent process to node red devices.).
may Echo ask something to HUB about a status? Thank you

Alexa queries the state of the (emulated) hub when certain conditions are met. The state of your bulbs is kept in memory by this software. That state will be queried by Alexa over your local network and will be reflected in the Alexa app. However, if you use another method to change the state of a physical bulb, the physical state of the bulb will change but this software will not know about it. For example, I use a motion sensor and Philips switches. When I change the state of a bulb using the switch or because of the motion sensor, the software will not know about that change since it took place over the Zigbee network. Using Zigbee2mqtt, I can update the state in the software memory by sending this info in the input node. Now when Alexa queries the state of a given bulb, it will get the correct state. Another use case is if you use a node-red based timer to turn on your lights automatically at a certain time. You would also need to update the state of the lights in the software.
On a side node, that state is kept in a node context. This means that it can also be changed without using node-red wires, by modifying the state directly with a simple modification. So, I've modified the software to keep this information in a flow context instead by changing this line:
setDeviceAttributes(msg.payload.deviceid, msg.payload, hubNode.context());
to
setDeviceAttributes(msg.payload.deviceid, msg.payload, hubNode.context().flow);
This way, my node red sensor code looks like this:
const BULB= 'Osram';
const THRESHOLD=  5;
const BRIGHTNESS= 5;

var outMsg = { 'payload': '',
               'topic'  : '' };
var sensor= JSON.parse(msg.payload);

**state= flow.get(BULB) || {};**

if (typeof state.on === 'undefined') {
  state.on= false
}

//node.warn('last='+ last);
//node.warn('current='+ current);

switch (true) {

  // Turn On:
  case ( (sensor.occupancy === true) && (sensor.illuminance <= THRESHOLD) && (state.on === false) ):
        outMsg.topic= 'zigbee2mqtt/' + BULB +'/set';
        outMsg.payload= {'state':'ON', 'brightness':BRIGHTNESS, 'transition':2};
        node.send(outMsg);
        **state.on= true;
        flow.set(BULB, state);**
        break;

  // Turn Off:
  case (sensor.occupancy === false) && (state.on === true):
        outMsg.topic= 'zigbee2mqtt/' + BULB +'/set';
        outMsg.payload= {'state':'OFF', 'transition':4};
        node.send(outMsg);
        **state.on= false;
        flow.set(BULB, state);**
        break;

}

Perhaps this simple modification can be incorporated in the main branch.
Hope this helps!

Released in v0.1.9


Payment Service v2

All seems good, to do add test for POST app.js in app.test.js

resolve the conflicts

@Grant-Steinfeld resolve the conflicts

@Grant-Steinfeld I fixed the merge conflicts, but it looks like you added a package without using yarn add, because it wasn't updated in the yarn.lock


"Wolfbrain" probably doesn't make sense for the GH token. What does?

[ ] update nerdbot and environment variable

How about "bot_user" or something? What does this token actually correspond to?

The token corresponds to @wolfbrain. I determined the user was no longer being used, so I scavenged. it

So, it's just a bot user that has access to the repos under review.

Exactly. @wolfbrain happens to have a lot of that access from days forgotten.

Perhaps a requirement is for folks to set up a GitHub account just for their bot? That would also allow them to better control access.

Oh... wait. I see. Never mind. :+1:

Any plans to merge this? I'm setting up this handler and wasn't sure what this environment variable meant. Also, it would be good to list what permissions are required.
Thanks for the plugin!

@johnallen3d thanks for calling me out on this! Yes this needs to be finished. Actually, revisiting it should probably be a handler configuration (which may be set by ENV in lita_config.rb). I might have some time today. Would love to get it in there for you :smile:

:eyes: @

Just pushed a better implementation of this that uses Lita's handler configuration. Will test, merge, and issue a new release if all looks well :+1:

:eyes: @mutexkid

@johnallen3d just published v0.3.0. It should work better for you :). Let me know if you have any other ideas to make things better!

Excellent, thanks!


Integrate json_repair package to overcome the slow json feature

Hi there,
Ollama is a great tool to get started with LLMs but the issue I'm facing is the JSON processing. The JSON format enforcer argument by the Ollama package just takes too long. It turns a 8 second response from LLaMa3 into a 90 second response. I don't know why it takes too long. I've come across a great package called "json_repair" that fixes broken JSON responses.
If the Ollama team can kindly integrate it so whenever the LLMs give out a broken JSON response, it can be fixed within 1 or 2 seconds. That'd be a great help in Function Calling too.
Here's the repo:
https://github.com/mangiucugna/json_repair

Hi @ArslanKAS. Thanks for the issue! This is an incredibly cool project. In terms of improving the JSON output with Ollama, this is something we'd want to fix in the inference code vs post-processing if we can. However I'd be excited to let folks know about this project via an example or in our discord


Launcher' s Refresh button does not work

When trying to refresh Project content by hitting the Refresh icon btn at the top right of the UI, nothing happens.

When stepping out from the project via project selector and stepping back into it all assets being refreshed.
Refresh should be working without need of any other action invovled.

Moved to the main OP repository as an issue...


[Feature Request] - table get_state() return selected index

Description
I'm using table component. When I call get_state, it doesn't return anything. I need the selected index instead.
Changes
The following changes to table.rs are expected
fn get_state(&self) -> Payload {
        Payload::One(Value::Usize(self.states.list_index))
    }

...

Implementation
Probably there is another way to get it? Thanks.

It makes sense. I'm gonna release this on the next week


Remove examples folder

Closes #650

Coverage increased (+0.5%) to 87.352% when pulling 8c3f05e764bf9d5fed0921ff3c9c73b98eff1ae7 on remove-examples into 0e94034efb1e88b88a06ca3862d8d2cc2f2ed5d0 on master.

Coverage increased (+0.5%) to 87.352% when pulling 8c3f05e764bf9d5fed0921ff3c9c73b98eff1ae7 on remove-examples into 0e94034efb1e88b88a06ca3862d8d2cc2f2ed5d0 on master.

Coverage increased (+0.5%) to 87.352% when pulling 8c3f05e764bf9d5fed0921ff3c9c73b98eff1ae7 on remove-examples into 0e94034efb1e88b88a06ca3862d8d2cc2f2ed5d0 on master.


grpc_credentials_tests broken at master

https://github.com/grpc/grpc/pull/9328 seems to be the culprit.
If fix is simple, we can move forward with it. Otherwise I suggest a rollback.

Fixed by https://github.com/grpc/grpc/pull/10587


Validation bug: license should contain path or name

A package license can be referenced via path and/or name: https://specs.frictionlessdata.io/data-package/#licenses. One of the two is sufficient, but validation in Frictionless 5.10.1 seems to require both, even though the help message mentions "path" or "name":

The data package has an error: license requires "path" or "name": {'path': 'http://creativecommons.org/publicdomain/zero/1.0/'}

The following fails validation (same if only name is provided), while it should pass:
{
    "licenses": [
        {
            "path": "http://creativecommons.org/publicdomain/zero/1.0/"
        }
    ],
    "resources": [
        {
        "name": "test",
        "data": [
            {
            "id": 1,
            "individualName": "Reinaert",
            "scientificName": "Vulpes vulpes"
            }
        ]
        }
    ]
}

The following passes validation:
{
    "licenses": [
        {
            "name": "CC0-1.0",
            "path": "http://creativecommons.org/publicdomain/zero/1.0/"
        }
    ],
    "resources": [
        {
        "name": "test",
        "data": [
            {
            "id": 1,
            "individualName": "Reinaert",
            "scientificName": "Vulpes vulpes"
            }
        ]
        }
    ]
}

Thanks @peterdesmet !

We're releasing<EMAIL_ADDRESS>with the fix

I can confirm this is fixed.


fix import in agent

Why does it point to a TS file? that should be lib/resolver.js right?

Yeah, you really want js as an entry point. It might have worked in your specific environment,  but just having the typescript files as entrypoint, will basically ensure almost everyone else will not be able to work with the lib


[WIP] Collect reports from BPF FV runs.

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

Going to close this since it's quite old and conflicty.


Fix ytick regression

closes #6943
also fixes:

the behavior of the show_names param, which was supposed to be showing channel indices when picks=None but was showing channel names (which led to a mismatch between the yaxis label "channel (index)" and the ticklabels)
the overplotting of the same yticklabel several times in some cases (e.g., the test case with only 2 channels)
clarifies slightly the show_names docstring

There is plenty of room for further improvement here, for example aligning the x ticks with the center of the imshow columns, but that will be rather involved and should be done in a separate PR.

@stfnrpplngr can you review also?

Here is the first plot from mne/viz/tests/test_evoked.py:test_plot_evoked_image() before the regression, after the regression, and after this PR:
before regression

after regression

this PR

Looks much cleaner.

Azure failure is unrelated and should be fixed by #6946, +1 for merge once @jona-sassenhagen's comments are addressed


watch w/ Revise

profile_and_watch_file is now fully integrated with Revise.ji,
which allows us to update/reflect changes in Base/stdlibs/packages
that are not directly included in virtual_process!ed files.
Revise will automatically take care of those usinged in
virtual_process!ed files (because JET.jl is currently just re-using
Juila's using as is), but extra tweak is needed to reflect changes
in Base/stdlibs
if we want to reflect changes in e.g. Base, we will do
profile_and_watch_file("file_using_base.jl"; modules = Base),
where the modules keyword option will be passed onto
Revise.entr(; modules)

this PR works, but still in WIP

some code clean up
maybe test for watch mode

Codecov Report

Merging #85 (19d09af) into master (111101e) will decrease coverage by 1.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #85      +/-   ##
==========================================
- Coverage   84.09%   83.06%   -1.04%
==========================================
  Files          10       10
  Lines         918      927       +9
==========================================
- Hits          772      770       -2
- Misses        146      157      +11

Flag
Coverage Δ

unittests
83.06% <0.00%> (-1.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/watch.jl
0.00% <0.00%> (-8.00%)
:arrow_down:

src/reports.jl
88.18% <0.00%> (+0.39%)
:arrow_up:

src/print.jl
79.79% <0.00%> (+1.58%)
:arrow_up:

Continue to review full report at Codecov.

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


Minor amendments to docstrings and fix media_count datatype

Firstly, great work with this repo and thanks for building it! I've migrated over from twint and stweet has been a fantastic alternative.
This is a trivial PR to clean up some mislabeled docstrings and correct one field datatype (User: media_count). Let me know if any changes need to be made.

Thank you for stweet Code Review I will merge it after my work today. 😉

Codecov Report

Merging #60 (ff7224a) into develop (61eb083) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head ff7224a differs from pull request most recent head 3c8dbd8. Consider uploading reports for the commit 3c8dbd8 to get more accurate results

@@            Coverage Diff            @@
##           develop       #60   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           71        71
  Lines         1030      1030
=========================================
  Hits          1030      1030

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

stweet/get_user_runner/user_parser.py
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


fix(zk_stack): Non-isolated network for compose-generated zk stack

What ❔
Removing creation of isolated docker network for zk stack components generated from zk stack init
Why ❔
This will enable to access all API's and endpoints from local machine.
Checklist

[x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[x] Code has been formatted via zk fmt and zk lint.
[ ] Spellcheck has been run via zk spellcheck.
[ ] Linkcheck has been run via zk linkcheck.

@artmakh is this PR still relevant? If not, could you please close it?


1646 kodadot v3 icon in pwa

Thank you for your contribution to the KodaDot NFT gallery.
👇  _ Do a quick check before the merge.
PR type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything works
[ ] I found edge cases

What's new?

[x] PR closes #1646
[x] added new KodaDot icon for PWA and also updated apple-touch-icon

Had issue bounty label ?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI, a screenshot for others, is best to understand changes.

Perfect, I’ve sent the payout https://kusama.subscan.io/extrinsic/0x1372d62fbc21360c0b893cdf59e8aee1d4a88f8d1ca3e017126977ab59f16591
Let’s grab another issue and get rewarded!
https://github.com/kodadot/nft-gallery/issues/


NetworkCloud Azure-cli-extension 2023-07-01 api -Do not Review/Merge  7/15

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

Thanks for the review @kairu-ms  , We would like to get these merged on 7/27.

Thanks for the review @kairu-ms , We would like to get these merged on 7/27.

Hi @priyamshet, is it ready to release?

@kairu-ms , yes please, this is ready to be released. Thank you for following up closely on this.


Better path display for deeply nested directories

What system are you running Yazi on?
Linux X11
What terminal are you running Yazi in?
GNOME v3.48.1
Yazi version
yazi 0.2.2
Did you try the latest main branch to see if the problem got fixed?
Tried, but the problem still
Describe the bug
When navigating through directories, the path to the directory is displayed at the top of the UI.
In deeply nested directories, only the first part of the path that can be displayed on the screen is displayed.
For example, if the path is a/b/c/d/e/f/g/h/i/j/k and only a path of length 5 can be displayed, then a/b/c/d/e will be displayed.
Expected Behavior
The last part of the path should be displayed, not the first as the purpose of the path display is for users to know where they are. For example, if the path a/b/c/d/e/f/g/h/i/j/k is navigated into and only paths of length 5 can be displayed, then .../g/h/i/j/k should be displayed, not a/b/c/d/e.
To Reproduce
Navigate into a deeply nested directory whose path can't be contained in the area for path display.
Configuration
no config
Anything else?
No response

Thanks for the report!
This sounds more like a feature request than a bug, as it's the current expected behavior - I'll add an "enhancement" label to it.

https://github.com/sxyazi/yazi/blob/b6fb02fda3317652270930043e298b63fd1d1f97/yazi-plugin/preset/components/header.lua#L5-L13
I think we just need to truncate the text here, anyone want to give it a try?

I don't understand where it cuts off. I brought these directories over, went in, and it shows full length.

@og900aero, my example assumes that the max path length that can be displayed is 5. It doesn't cut off on your computer because the max path length is greater than needed. If the path length can't fit in the allotted space for the path display, you will see the cutoff.


Unify wrappers for the Ably SDK

The main purpose of this PR is to create the universal wrapper for ARTRealtime from the ably-cocoa SDK and use the same either in the subscriber or publisher package.
It's split into two parts:

Creating protocols for publisher, subscriber and common. Creating wrapper around the ARTRealtime using protocols. - this part doesn't contain the implementation of the "new wrapper" in the DefaultPublisher and DefaultSubscriber (commits: fb521295c43dd27c4e02abe02b116ccc7d6ec5de f291d04dd54f771a05b90d1eb6e8cdae27a4cfef 984abfba7239f8518426edbe895412855f25abf1)
Implementing of the before created wrapper in DeafaultPublisher and DefaultSubscriber using their protocols to hide some of the methods from each other. Fixing existing tests. (TBD)

Would be nice to see an example of code duplication this PR solves. Thanks @lukasz-szyszkowski  🙏

Would be nice to see an example of code duplication this PR solves. Thanks @lukasz-szyszkowski 🙏

Initialisers are almost the same. It's split into two methods init and  connect

They implement the same subscriptions like channel.presence.subscribe, channel.presence.enter, channel.on, client.connection.on

The stopTracking and leaveChannelPresence methods do the same

Here is another part of the changes related to AblyPublisher and its tests:

Replacing DefaultAblyPublisherService with DefaultAbly wrapper hidden behind AblyPublisher interface (78113916ef8996d7f993a58d48694c1a26c5d75b)
Updating MockAblyPublisherService from test target (fff3af466ccab76000899a14d9cf2bbacf38cde3)
Updating SystemTests with new Ably wrapper (aa795559803a381522b948bf14f2b9dde05005ca)
Fixing Publisher tests against new Ably wrapper (b89fed1d0c52ddfefa976bacdfff7b82072e7b9f)

Yet another part of the changes related to AblySubscriber and its tests:

Replacing DefaultAblySubscriberService with DefaultAbly wrapper hidden behind AblySubscriber interface (ca8379fcafa0fd9dc49868a484a69255785318ca)
Updating MockAblySubscriberService from test target (f6c72e14f988689c380325ebafd9eff1fe4e6fed)
Fixing Subscriber tests against new Ably wrapper (118cc36297ed07f57d83ab6aa5a0bfd1648bcee6)
Remove previous protocols and wrappers for Ably (6d5e2d386b4654df6e1f761bffca486bc071795a)
Add missing subscriber delegate method call (af574a51ff731253d43b763e4bced5515b3a8ccd)


Replace misk.assertThrows with kotlin.test.assertFailsWith

https://kotlinlang.org/api/latest/kotlin.test/kotlin.test/assert-fails-with.html
No need to reimplement kotlin functions.
Will need to add kotlin.test to gradle build

Closed with #309


Documentation is a little bit confused

Welcome!

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

What did you expect to see?
I've recently started using Traefik, and when I searched how to use Basic Auth I quickly found Documentation page:

But thing is that copy-pasting this snippet does not work, and you have to understand that you also need to activate middleware, probably I had to read whole doc first to understand it, but I think low number of devs doing it like this in our world where there are tons of different tools. So it works if you add:
labels:
  - "traefik.http.routers.api.middlewares=test-auth"
  - "traefik.http.middlewares.test-auth.basicauth.users=test:$$apr1$$H6uskkkW$$IgXLP6ewTrSuBkTrqE8wj/,test2:$$apr1$$d9hr9HBB$$4HxwgUir3HP4EsggP/QNo0"

So I mean why not to just add this line to snippet too, at least to first one:
 - "traefik.http.routers.api.middlewares=test-auth"

Hello @ivictbor,
Thanks for your interest in Traefik,
As explained in https://github.com/traefik/traefik/pull/9057#issuecomment-1143275561

The configuration example section in a middleware page contains only an example of an available configuration option for this middleware. This example is not meant to include a working router configuration, as introduced by this pull request. For that, we already have a generic page documenting how to configure a router referencing a middleware.

According to this, we will decline this issue.


[Plot] Add support of scatter plot given value and colormap

Plot.addCurve allows to display a scatter plot given x, y and colors, but not given x, y, values and colormap...
Proposal: Add a addScatter method which supports both... and that can also supports different sizes.

Let me check if I understand.
Now it is implemented as in the PyMca API where the color could be a sequence of the same length as the input data.
Now you would like to provide x, y and an additional value and calculate the color applying the colormap to the the additinal value.
Did I properly understood?

Yes that's the idea @dnaudet will probably need this.

Closed by PR #697


Remove minor keyword incompatibilities with C++

Hi wlroots Team :wave:
When working on my compositor I have noticed there are a small number of statements that cause some incompatibilities with C++.

A few static array statements are peppered throughout the headers.
The xwayland struct has a member named class which is a reserved keyword.

I humbly raise this PR to make the adjustments to fix up these issues. Other than these pretty much everything else works great with C++.
Thanks for all the work on such a great framework, i hope this doesn't inconvenience too much.

Hiya, this has been brought up before but we're not interested. You should forward declare things yourself or some similar workaround. We don't subscribe to the line of thinking which presumes C and C++ are the same language, to us C++ is no different from any other FFI.

ok thanks for the info, will do.


Duplicate lines

Commands.py lines 23 and 32 are duplicate if statements.
Also, I would recommend "Ahem:" or "Ahem."

Direct links for convenience:

23
32

Looks like it is defiantly a duplicate command.
I personally don't have any preference on "Ah hem" vs "Ahem".
I thought it was an attempt to replicate Pennys tone of voice by adding the space and additional "h", but it could be another typo.

Resolved.


Verification socket exception

W/KISSmetricsAPI﹕ Verification experienced an Exception: java.net.SocketException: Socket is closed

I'm closing this since there isn't any steps to repo it or a stacktrace.


Bump rustic

What package(s) should be bumped?
rustic
Why should Doom bump these packages early?
Several issues were fixed recently
rust-mode will be a dependency of rustic soon(https://github.com/brotzeit/rustic/pull/290) so I'd like to pin the package before it gets merged. This way less users will be affected if the changes broke existing functionality.
The package should be bumped to "d7a5019a4e30fe389729c4172ec19b422e20e36d"

Should be stable.

#6153


LUN-253: Intuitive scroll and click behaviour

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword LUN.

Similar behavior implemented in #240


Namespace '"C:/Data/Solutions/.../node_modules/@types/leaflet/index"' has no exported member 'MarkerClusterGroup'.

Got leaflet and leaflet.markercluster installed

Imported them as such:

but when using:

reports: has no exported member 'MarkerClusterGroup'.
Can I get some help please?

We don't handle typescript in this repo.


Fix crash on Add Iterator click when MS or MA selected

This is a hotfix that just ignores everything that doesn't
have an instance of FunctionInfo.
Tests: Manual, Unit
Bug: http://b/232058826

@dpallotti, you're right. I've forgotten it's merged.


TXID issue

Test for Jim Flanagan: I cannot copy Transaction ID, and cannot view on Blockchain, link not working.(created from Zendesk ticket #3006) gz#3006

Agent comment from Jim Flanagan in Zendesk ticket #3006:I have sent this issue to our developers, thank you for bringing this to our attention.
We will try to resolve this issue for you as quickly as possible.
°°°

Agent comment from Jim Flanagan in Zendesk ticket #3006:Thank you for your response.
°°°

@Crypto-Keeper-miners  Will you find out if they are using Android or iOS
Which version of device ?
Thanks

Feature request


Pose matching: Add an LED size model

If we use information about the expected size of an LED at a given distance, we can more intelligently constrain the match distance for blobs to LEDs in rift-sensor-pose-helper.c

Would these equations assist with that?
https://pages.uoregon.edu/soper/Light/luminosity.html

What I had in mind when I wrote this is a model that would take into account the luminosity of the LED, the physical size, the distance and angle to the camera in the proposed pose, and spit out an expected brightness range for the pixels, and the size of the bounding box in pixels, and possible also a 'shape' to match against. When checking if the camera-observed pixels match a proposed pose, it would be good to know that we expect an LED to only appears as 1-2 pixels for example, and not match against a blob that's many times bigger than that.
That's definitely in 'future refinement' territory though - it'll produce more accurate and stable pose observations, but isn't critical to "getting something working" at this stage.

Would this have to be done via mathhh, or would we be able to help by gathering data?

Maths mostly, and definitely an item for the distant future still

9f118cd9970d7cf00324a4a25e25ae15ccefabd2 adds some prediction of the expected size of LEDs at a given distance. Hard to tell if it helps yet, but it didn't seem to hurt.


Fix code scanning alert - Reflected server-side cross-site scripting

Tracking issue for:

[x] https://github.com/abhisheksr01/zero-2-hero-python-flask-microservice/security/code-scanning/1

Added the fix recommended by codeql.


Test for db file existance instead of creating a new one in password-restet.js

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
Upon detailed review of the issue, the only thing needed was to add a try catch block.
Code was already testing for db file existance
Fixes #4518
Type of change
no addition or deletion
just moved 2 lines in a try catch block
Please delete any options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
This change requires a documentation update

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[ ] (not needed) I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
[x] My changes generates no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)
Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

Thanks for the bugfix!
All changes in this PR are small and uncontroversial ⇒ merging with junior maintainer approval


add columns from overlap object

Is there a possibility to add columns from the pyranges which was used for overlapping. What I mean is that let's say one uses a subset of gtf file as regions of interest, but after overlapping wants to also annotate with other columns like gene name from gtf file.
It could be an option like this:
gr.overlap(gr_gtf, addcols = True)
The output would have all rows from gr that overlap with gtf, but in addition also all columns from gtf object for each overlap.

join does this if I understand you correctly. Thanks for trying PyRanges btw, it makes me happy :)
gr.join(gr_gtf)

Oh, my bad! Did not notice the join function! Sorry! Anyways, pyranges is really great! Huge thanks for developing this!


[Feature] Allow zend-cache setters to optionally specify TTL

I find I tend to create multiple cache instances, with TTL being the only appreciable difference in their configuration (eg a short, medium, and long-term cache).
If one of those doesn't quite fit my needs, I further end up doing things like:
$originalTtl = $cache->getOptions()->getTtl();
$cache->getOptions()->setTtl($someOtherTtl);
$cache->setItem($key, $value);
$cache->getOptions()->setTtl($originalTtl);

I propose to be able to:
$cache->setItem($key, $value, $someOtherTtl);

The change looks fairly trivial for storage adapters which natively support TTL (most of the "real" ones like memcache, xcache, redis), and maybe can be ignored for others?
I'd be happy to work on this and submit a pull request if there's interest.

linked with #5386 by @Thinkscape /cc @Ocramius

ah, I didn't find #5386 when searching - given the original implementation there was quite similar to what I am proposing, and it's marked as 'wont fix', I'm probably wasting my time?

Zend\Cache is opinionated on how you should structure your caches - follows the "container architecture" where you're supposed to have a lot of containers defined, each with pre-set, separate ttl.
I've wasted time on #5386 trying to explain that there's different approaches to caching, then switched all my apps to faster and more flexible cachet - https://github.com/shabbyrobe/cachet.


Why are so many DLLs in the package?

Even a small console application is 30MB. Inside are a lot of DLL that are part of the runtime. Is the runtime not a dependency, why also provide those DLLs? Also there is Visual basic DLL and I don't even use that. How can I strip it?

The DLLs which are packaged are the result of publishing your application as a framework-independent package using dotnet publish. It includes the runtime.
You are right that it may be easier to declare the runtime as a dependency. This would reduce the size of the application.
There's no built-in support for that right now, but it's something worth considering.
One caveat here would be that your users would be required to add the .NET Core repository for your operating system to their list of repositories before they can install your app, since .NET Core is not packaged by any of the major distro's (that I know of).

Ok. That explains the large packages.


Gettext translations

Hi,
I've re-done the i18n PR with the python's gettext module.
It's subjective, but I think that i18n module is easier to work with -- you have simple yml files which you can edit directly.
To work with gettext, you have to use command-line tools to generate binary .mo files.
I was also not able to rework 1 test that compares countries for equality since in my code I add translate method at runtime.
Anyway, let me know what you think.
Otherwise i18n functionality is desperately needed I think, currently some countries have their holidays names in local language, others in English (even when not local, e.g. some arabic countries).

Hi @arkid15r. Thanks for the quick look. Looking forward to further comments.

Hi @dragoon,
I've just filed #827 stacked on this one.
Please take a look/review it when you have a chance.
Thank you!


Tikhonov regularizer

Tikonov regularization is really useful for problems where we know that features covary with each other.
For instance, in time series problems, nearby time points are correlated. In receptive-field estimation problems, nearby pixels are correlated. In gene expression problems, we have prior knowledge on which genes are likely to be co-expressed.
One way to implement this is to accept a parameter called Tikhonov_Tau which is a n_features x n_features matrix.
We would then pass this parameter to the _penalty function, where instead of
penalty = reg_lambda * (1.0 - alpha) * 0.5 * np.linalg.norm(beta, 2) + \
                alpha * np.linalg.norm(beta, 1)

we would write
L2penalty = reg_lambda * (1.0 - alpha) * 0.5 * np.dot(np.dot(beta.T, Tiknonov_Tau), beta) + \
                   alpha * np.linalg.norm(beta, 1)

+1, sounds easy enough to implement.


Kysely Query with array of "From" with raw SQL not as documented

I am using Kysely with Postgres), However applying Kysely equivalent for FROM X, Y does not seem to work. I would like to produce the following SQL (you can ignore the WHERE clause):
SELECT *
FROM
  products,
    jsonb_array_elements(products.properties#>'{someProperty}') as search_item

where cast(value as integer)=2

The equivalent I saw in the source code documentation (having multiple FROM and also raw sql is:
/node_modules/kysely/dist/esm/query-creator.d.ts:
import { sql } from 'kysely'

const items = await db.selectFrom([
    'person as p',
    db.selectFrom('pet').select('pet.species').as('a'),
    sql<{ one: number }>`(select 1 as one)`.as('q')
  ])
  .select(['p.id', 'a.species', 'q.one'])
  .execute()

The generated SQL (PostgreSQL):

select "p".id, "a"."species", "q"."one"
from
  "person" as "p",
  (select "pet"."species" from "pet") as a,
  (select 1 as one) as "q"

So I used the syntax utilizing the sql object like the 3rd select argument as the following:
const res2 = await db.selectFrom([
    'products',
    sql<{ someProperty: number }>`(jsonb_array_elements(products.properties#>'{someProperty}')`.as('search_item')
  ]).select(['products.properties', 'search_item']).execute();

However getting an error:

error: Uncaught (in promise) PostgresError: syntax error at end of input
          error = new PostgresError(parseNoticeMessage(current_message));
                  ^
    at Connection.#simpleQuery (https://deno.land/x/postgres@v0.17.0/connection/connection.ts:700:19)
    at eventLoopTick (ext:core/01_core.js:183:11)
    at async Connection.query (https://deno.land/x/postgres@v0.17.0/connection/connection.ts:949:16)
    at async PoolClient.#executeQuery (https://deno.land/x/postgres@v0.17.0/client.ts:245:12)
    at async PoolClient.queryObject (https://deno.land/x/postgres@v0.17.0/client.ts:433:12)
    at async PostgreSQLDriverDatabaseConnection.executeQuery (https://deno.land/x/kysely_deno_postgres@v0.4.0/src/PostgreSQLDriverDatabaseConnection.ts:14:12)
    at async https://esm.sh/v133/kysely@0.26.3/denonext/kysely.mjs:3:50936
    at async Or.provideConnection (https://esm.sh/v133/kysely@0.26.3/denonext/kysely.mjs:3:86791)
    at async t.executeQuery (https://esm.sh/v133/kysely@0.26.3/denonext/kysely.mjs:3:50891)
    at async t.execute (https://esm.sh/v133/kysely@0.26.3/denonext/kysely.mjs:3:58522)

Any idea? It seems equivalent to the docs in terms of how to have multiple terms in the FROM statement, also using raw sql as well. (Also if I try to add select search_item the type is not identified for this string.

You did right except you did not close the round brackets.
(jsonb_array_elements(products.properties#>'{someProperty}') -> (jsonb_array_elements(products.properties#>'{someProperty}'))
or just jsonb_array_elements(products.properties#>'{someProperty}')

You did right except you did not close the round brackets. (jsonb_array_elements(products.properties#>'{someProperty}') -> (jsonb_array_elements(products.properties#>'{someProperty}'))
or just jsonb_array_elements(products.properties#>'{someProperty}')

Thanks, I've managed to finally find it by patching the postgres module and printing the query (if there is an easier way to print/debug kysely queries let me know:
Thanks, I

I checked the generated sql from playground.

I checked the generated sql from playground.

Thank you. I didnt know how to import the sql in the playground, but I will use it from now on🤘


[Modal] IE11 scroll position

Problem
Scroll position is moved to top in IE11 (possibly any IE version) when the modal is refreshed.
Steps to reproduce:

Open scolling modal on http://www.semantic-ui.com/modules/modal.html#/examples
Resize window or do something else that will trigger a modal refresh.

Expected
The scroll position should stay intact.

Well that is weird. Thanks IE :wink:

Well, at least it works in project spartan ;-) /IE

I have looked at this for a half hour and have no clue. If anyone has a lead on this please advise. As far as I can see it, IE is not correctly storing the scrollPosition when overflow changes on a container.

I didn't dive that deep in to the problem. It is a good start to know that much.
I guess in some situations it is a lot less annoying then others. For example when re-sizing the window.
We got bug reports from users when they were filling form inputs inside the modal and that is really annoying. So what we did as a workaround was to disable dom mutation observation of the modal subtree (modal.js#148)
observer.observe(element, {   childList : true,   **subtree   : false** });

Won't that change have a lot of consequences? For example if the height of the modal content change to not fit on screen?

Sorry for late reply. I believe having it 'opt-in' is an adequate solution for those who are loading content into modals after the fact.

Yeah I've been running the same change you did in 2.0 in 1.X and no problem so far.


Allow manual entry of smoothing window size

The new smoothing feature is awesome but it's really hard (or impossible?) to get some specific smoothing window sizes. E.g. about 5 or 6 seconds is the sweet spot I'm looking for, but the slider seems to only allow certain values: 0, 2, 4, 7, 9, 12, ... s.
It would be great to be able to click the window size value and manually enter a value (e.g. 5 s); alternatively, allowing more values at the low end with the current slider would work for me as well (e.g. any integer value of seconds up to 15, then 5 second jumps after that).

+1

I'm going to close this as you can use the keyboard or manual entry in the advanced panel.


wsgiref dependency doesn't work on Python 3

Hi Kenneth! I'm trying to install PingdomLib on Python 3 but with no luck because of wsgiref dependency. As far as I know it is built-in to Python 3.
Couldn't you just remove this dependency from setup.py? Is it somehow used by your library? I can't see any direct usages in the source code.

Howdy @haxoza, sorry for the late response on this, I believe pip freeze tossed that in there because of something related to requests and it should be fine without it. I'll get that dropped and put out a new release today.

Thanks!


How to add GSN provider to useDApp?

So, how can I add gsn RelayProvider to my project using useDApp? Any ideas? I'm afraid I don't have enough expertise in this. Where can i get currentProvider and how to bind provider to useDApp? Image from GSN docs

However, I decided to give it a try. But what should I pass to the provider parameter in RelayProvider.newProvider? It looks like using the web3.js library, but we use ethers. I tried to pass there library from useEthers, but an error is shown. And unfortunately this is not a type error.

If readonly just put it in your config.

I don't quite understand. Put provider to useDApp config? How?

So, I think this not useDApp issue, i close it.
Maybe my experience will help someone.
Unfortunately, RelayProvider does not work in the activate useDApp method. Just like the library provider from useEthers is not suitable as a provider parameter in Relay Provider. I think this is the problem of the Relay Provider itself.
Therefore, we decided on the project to use transactions via gsn separately from transactions running through the useDApp library. Here is the code that calls the deposit method in the contract. MyContract is a JSON abi contract file. The work was carried out in Binace Smart Chain Testnet


exactOptionalPropertyTypes vs class implementing interface with optional properties

Bug Report

🔎 Search Terms
exactOptionalPropertyTypes interface implementation class
🕗 Version & Regression Information
4.4
Regressed additional case in 5.0.4

This is the behavior in every version I tried, and I reviewed the FAQ for entries about exactOptionalPropertyTypes (there are no FAQ entries)
I was unable to test this on prior versions because the feature was introduced in 4.4

⏯ Playground Link
Playground link with relevant code
💻 Code
// with exactOptionalPropertyTypes enabled

interface T {
    x?: 1;
}

// Breaks in 5.0.4 with TS2420
// Class 'TT' incorrectly implements interface 'T'.
//  Types of property 'x' are incompatible.
//    Type '1 | undefined' is not assignable to type '1'.
//      Type 'undefined' is not assignable to type '1'
class TT implements T {
    x?: T["x"];
}

// Broken since 4.4 with TS2559
// Type 'TTT' has no properties in common with type 'Partial<T>'.
class TTT implements Partial<T> {
    X?: 1;
}

🙁 Actual behavior
It is not possible to implement the interface in 5.0.4, and difficult to implement by reference in 4.4
🙂 Expected behavior
Both cases satisfy the constraint

This is possible, you just can't write T['x'] since that is 1 | undefined and you're not allowed to have an instantiated property with value undefined under EOPT. All this behavior follows from the definitions of the rules.
class TT implements T {
    x?: 1 = 1;
}

The hover in vscode shows T["x"] as 1 not 1 | undefined
this is also useless since in real cases there is no default value here; 1 is a trivial example
But

not allowed to have an instantiated property with value undefined under EOPT

seems like something that should be documented along with the option since that makes it quite possible to create interfaces that are not implementable.

Also is there a reason for requiring properties to have values when instantiated? This is literally modeling a constructor that conditionally sets a property.

Are these rules documented anywhere?

Also is there a reason for requiring properties to have values when instantiated?

Because that is literally the raison d'être for exactOptionalPropertyTypes?  If you don’t want that behavior, turn it off.

Because that is literally the raison d'être for exactOptionalPropertyTypes? If you don’t want that behavior, turn it off.

how do you model the difference between
class X {
   constructor() {
      this.x = 1;
   }
}

and
class X {
   constructor(x) {
       if (x) {
            this.x = 1;
       }
   }
}

I'm using EOPT specifically for this.

T["x"] in a read position is 1 | undefined, you can experiment to determine this:
interface T {
    x?: 1;
}

class TT {
    x: T["x"];
    constructor() {
        this.x = undefined; // allowed
    }
}

seems like something that should be documented along with the option since that makes it quite possible to create interfaces that are not implementable.

But you can implement it; my example showed how.

Ugh this is not really resolved — you can't use EOPT on classes this way.


Revert "Merge pull request #26 from andyburke/master"

This reverts commit ef7929a1c9029b1d6b09775f1202cee45aaa07f6, reversing
changes made to f7f8a7b0bf1b59ac7c811f22b91d198db1c432fb.

Yes please. There's es5-shim for this.


Integration of copyright site parameter.

The config parameters are already getting a bit lengthy, I'd rather see customisation like this done via overriding the relevant partial. Hugo allows you to do this without forking the theme.

Except copyright is an expected parameter that's included in spf13's "unenhanced" hyde as well as most of the Hugo themes I've looked at.
Having your name stamped on it and forcing the user to needlessly override the partial sounds like more of a vanity issue than anything else.

When I created this repo I decided the Hyde copyright notice should be replaced by a more detailed /license page, and repurposed that sidebar section to link back to Hugo and this repo. That latter part was prompted by the huge number of blogs I've seen where I wished I knew how it was built.
If you disagree with this, or any other aspect of the theme, that's perfectly OK.