GAL-3706: auto period on comment input

Description:
This seems to be a React Native's limitation. Please refer this. There is an ongoing work to fix this issue.
As of now, the workaround is to set the multiline prop to true. And I don't presume making it multiline affects our CommentBox comment.
Demo
https://www.loom.com/share/7ac2a321c718400ab03a23b090a927cc?sid=beaa36aa-9069-432b-b2c3-4dcf7895907a

nice find @SouravInsights !! the period is showing up as expected ✅
I noticed that when I type on a new line, sometimes the vertical position glitches a bit and resets to showing the line above. attached a video as an example.
would you be able to take a look? looks like it's new behavior due to it being multiline
https://github.com/gallery-so/gallery/assets/80802871/cb96c4df-6251-4e5b-baa4-ffca4b5778dd

Oh yeah I know why it's happening, I read somewhere that this is a possible issue we need to handle when we set multiline to true. I'll take a look! Sorry I missed it initially.

hey, @kaitoo1 turns out we could adjust the height of the comment box dynamically based on the content size.. i think it fixed the glitch but let me know your feedback! here's demo

hey @SouravInsights thanks for looking for a solution. it looks like unfortunately it doesn't work when the keyboard is actually open on the screen- attached a recording.
https://github.com/gallery-so/gallery/assets/80802871/cb0be74f-b991-4cac-be83-66b1923f59f2
IMO the original issue of not supporting the auto-period iOS feature isn't a huge deal so let's table this for now - it's not a game changer and I don't think it's worth investing in a workaround since it's not supported by react native. thanks for researching alternatives 🙏


Paloma function stops working after 5.1 upgrade from 4.2.1!

To handle specific controller actions, my js files for each required page had this, as seen on the github readme page:
// area above this contains callback functions that are used
// in various parts of the page, under the function below
var ArticlesController = Paloma.controller('Articles');
ArticlesController.prototype.edit = function(){
// Handle edit article
};
While my rails site was updated to 5.0, I was using paloma 4.2.1 and this worked fine.  But in rails 5.1, the upgrade paloma to 5.1 is mandatory however now the above code will not run at all.  When the website is running, I used to see in the console that Paloma was loaded to the page, but that does not show up now.
I tried running the code by enclosing it all inside $( document ).ready(function() {   }); and some of the code did run, however, the paloma part never ran.  I really need this to work since I am using this paloma functionality to handle specific associations to the data in the controller that is impossible without it.

Just fixed this all, turned out that there were two issues - Paloma wasn't loading to the page since our old setup did not use a paloma hook on the application.html.erb page, and also the controllers needed javascript to run a paloma start function in order for the controller call to work.  After this, a page refresh was required for the js to get called when navigating to any page, which is a turbolinks 5 issue: see this article for how it got fixed:
https://stackoverflow.com/questions/17317816/rails-javascript-only-works-after-reload
If you are having this issue after upgrading to Rails 5.1, be sure to invoke the paloma.start function from within the turbolinks load function:
$(document).on('turbolinks:load', function() {
Paloma.engine.start();
});


Send rawtx conditional

Related to account abstraction.
Implementation of this endpoint https://notes.ethereum.org/@yoav/SkaX2lS9j

basically the same as eth_sendRawTransaction, with the ability to specify a number of conditions

[x] have put X in the RPC name for now - spec may not be finalized
[x] limit max number of user-specified constraints
[x]  check expected storageHash against blockchainQueries actual value (needs a new method to expose this)

Overall looks good, just minor things and some questions.
One thing is still not clear to me about the lifecycle of a tx sent by this method, should the conditional be evaluated also after the tx has been accepted? For example given a block range condition, if it is satisfied when accepting the tx, but not anymore satisfied when the tx is selected to be included in a block, should the tx be included or discarded?

changed to draft while we're waiting on clarification on this question

Suggest we ask in the ERC implementers Telegram the question Fabio posed. DM me for details

Adding context from Yoav:
It must be evaluated against the current state at the time of inclusion in a block.
The purpose of this RPC is to create a transaction that will only be included if the conditions are met at the time it is included.  It's a cheap alternative to the otherwise-expensive alternative of running the transaction and ensuring non-reversion (like the Flashbots relay does).  The sender does the work of mapping the minimum conditions for the transaction to succeed, so the validator/sequencer doesn't have to run the entire transaction.  But if the conditions are no longer met, the transaction might revert despite the sender's best effort.  That's where the above guarantee fills the gap by dropping the transaction.

think it makes more sense to do this in a plugin

If we want to support account abstraction on many chains, we may want to ship this in vanilla Besu, so its picked up in any upstream changes. What do you think?


Laravel doesn't redirect back to authorization form after login

Laravel Version: 5.5
PHP Version: 7.1, 7.2
Database Driver & Version: MySQL, Postgresql

Description:
Passport doesn't redirect back to authorization form after login.
Problem only on chrome(tested from 64-67).
If I enter through the link directly in the new tab, the problem does not occur, but if it is in the same card, laravel gets an invalid url()->previous()
Related: https://github.com/laravel/passport/issues/703

Closed without comment? Best practices on laravel team, great job.

Use a different framework, we don't want your sarcasm and abusive language.


Guzzle 6

Hello,
Any chance of this package supporting Guzzle 6?

This is planned, I don't think there are issues so far, need to check by modifying the composer and see if test passes.

Actually, some work needs to be done.

I've created a PR: https://github.com/neoxygen/neo4j-neoclient/pull/56


Fixed that the config was not used

Instead of using the environment variable in the Twitter class the config passed to the constructor should be used.

Oh, thanks for this!!


update to new std.Thread.Mutex api

as per the change in https://github.com/ziglang/zig/commit/008b0ec5e58fc7e31f3b989868a7d1ea4df3f41d

Thank you very much!


Implement operations for RVResults

Right now, the following code does not work:
X = RV(Exponential(rate=1/4))
x = X.sim(10000)
mean((x - x.mean()) ** 2)

That's because x - x.mean() is not well-defined. We would need to define operations on RVResults objects to make this work.

I've attached a notebook with some tests of operations in RV and simulation space.
Simulation space operations.pdf
RV space appears to be working fine - aside from tuples created with *.  For example, in order to implement
X = RV(BivariateNormal() * Poisson(1))
(X + ((0, -10.4), 100)).draw()

I need to use
X, Y = RV(BivariateNormal() * Poisson(1))
((X + (0, -10.4)) & (Y + 100)).draw()

But I think the bigger issues are with simulation space.  In short,  things like (X + 3).sim(10) work fine, but things like X.sim(10) + 3 return errors (though things like X.draw() + 10 do work).  (apply seems to work fine in both RV and sim space.)
Before making any changes, I think we should think about this issue more carefully.  I think the idea from the beginning has been that whatever can be done in RV space should also have a sim space version, e.g. X.apply(sqrt).sim(10) and X.sim(10).apply(sqrt) are both possible.  My question is do we really want the same operations to work in RV and sim spaces?  I haven't thought this through, but the answer might be no.
From a pedagogical perspective, I tell my students to first define all elements of the model - prob space, RVs, transformations - and then simulate.  Basically, distinguish between what one repetition of the simulation entails and summarizing the results of many simulations.  So I would encourage students to code as X.apply(sqrt).sim(10) rather than X.sim(10).apply(sqrt).  Is there a pedagogical advantage to allowing the simulation space operation (other than just preventing coding errors)?  For example, does simulation space syntax X.sim(10).apply(sqrt) help students better understand LOTUS?
For single RVs, simulation space operations like X.sim(10) + 3 seem natural, but it gets trickier when dealing with multiple RVs, like
X = RV(BivariateNormal())
X.sim(10) + Vector((0, -10.4))

Another example: do we really want/need a simulation space equivalent of the following?
X, Y = RV(BivariateNormal(mean1=0,mean2=10) * BivariateNormal(mean1=100, mean2=20))
(X + Y).sim(10)

If we think of outcomes as rows and RVs as columns, then RV space operations apply row by row, outcome by outcome.  Should we force users to define in RV space anything that can be defined in RV space?  And then treat simulation space operations like vectorized numpy arrays operating on columns?  The latter might make things like mean((x - x.mean()) ** 2) and lots more easier/more natural.

I believe this issue is addressed by #79

Yes, I'll close this.


Support for FP8 quantization

With the release of the new Mistral NeMo 12B model we now have weights that were pre-trained with FP8. It would be great if Unsloth could support 8bit as well as the existing 4bit training so we could do training without any quantization related loss.

Apologies on the delay just did! https://huggingface.co/unsloth/Mistral-Nemo-Base-2407-bnb-4bit


Add delete syntax for primary key table

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #4361
Problem Summary(Required) ：

This PR implement delete syntax for primary key table, delete syntax is already supported in other key models using old parser/analyzer/planner. For the primary key table, we use a totally different approach and implement using new parser/planner.
This creates a dispatch issue, for an upcoming delete SQL statement, first it will be dispatched to new parser and analyze it, if the table is primary key table then continue analyzing&planning, otherwise fallback using old analyzer, then when executing the statement, check whether it supports new planer, if so use execplan and execute plan fragment, if not use the old DeleteHandler.

[FE PR Coverage check]
:disappointed: fail : 116 / 147 (78.91%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/analysis/InsertStmt.java
0
1
00.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
8
30
26.67%

:large_blue_circle:
com/starrocks/sql/analyzer/DeleteAnalyzer.java
30
36
83.33%

:large_blue_circle:
com/starrocks/analysis/DeleteStmt.java
16
17
94.12%

:large_blue_circle:
com/starrocks/sql/DeletePlanner.java
36
37
97.30%

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
10
10
100.00%

:large_blue_circle:
com/starrocks/sql/StatementPlanner.java
8
8
100.00%

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
1
1
100.00%

:large_blue_circle:
com/starrocks/analysis/DmlStmt.java
1
1
100.00%

:large_blue_circle:
com/starrocks/load/DeleteHandler.java
4
4
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 128 / 149 (85.91%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/analysis/InsertStmt.java
0
1
00.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
8
23
34.78%

:large_blue_circle:
com/starrocks/sql/analyzer/DeleteAnalyzer.java
33
36
91.67%

:large_blue_circle:
com/starrocks/analysis/DeleteStmt.java
16
17
94.12%

:large_blue_circle:
com/starrocks/sql/DeletePlanner.java
36
37
97.30%

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
19
19
100.00%

:large_blue_circle:
com/starrocks/sql/StatementPlanner.java
8
8
100.00%

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
1
1
100.00%

:large_blue_circle:
com/starrocks/analysis/DmlStmt.java
1
1
100.00%

:large_blue_circle:
com/starrocks/load/DeleteHandler.java
4
4
100.00%

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage check]
:heart_eyes: pass : 128 / 149 (85.91%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/analysis/InsertStmt.java
0
1
00.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
8
23
34.78%

:large_blue_circle:
com/starrocks/sql/analyzer/DeleteAnalyzer.java
33
36
91.67%

:large_blue_circle:
com/starrocks/analysis/DeleteStmt.java
16
17
94.12%

:large_blue_circle:
com/starrocks/sql/DeletePlanner.java
36
37
97.30%

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
19
19
100.00%

:large_blue_circle:
com/starrocks/sql/StatementPlanner.java
8
8
100.00%

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
1
1
100.00%

:large_blue_circle:
com/starrocks/analysis/DmlStmt.java
1
1
100.00%

:large_blue_circle:
com/starrocks/load/DeleteHandler.java
4
4
100.00%


A question about the performance reported in your paper

Hi, is the performance of the synthetic distortion datasets reported in your paper, e.g. CSIQ, TID2013, and KADID-10K, obtained using the reference image splitting training test set with 80-20% ratio? Or is the splitting done directly on all distorted images.

Hi! thanks for your question!
Your question is same as https://github.com/IIGROUP/MANIQA/issues/7
We use the reference image splitting training test set with 20-20% ratio.
If we just split all distorted images, the performance will drop a lot.

OK, thanks for your reply.


RSN Parser: Fixed RSN parser generation output (close #201)

That did not fix it
https://github.com/DiligentGraphics/DiligentTools/actions/runs/6926439810/job/18838609995#step:5:846


Schema Generation skips over fields with default values

I have a data class like so:
@Serializable
data class Town(val name: String = "MyTown", val population: Int)

When converting this data class to a schema and printing it:
val schema = Avro.default.schema(Town.serializer())
println(schema.toString(true))

the output is:
{
  "type" : "record",
  "name" : "Town",
  "namespace" : "com.sksamuel.avro4k",
  "fields" : [ {
    "name" : "population",
    "type" : "int"
  } ]
}

with the Town.name field missing

Temporarily fixed by removing all calls to descriptor.isElementOptional() in the following 2 places:
ClassSchemaFor.kt:20
.filterNot { descriptor.isElementOptional(it) }
RecordDecoder.kt:128
override fun decodeElementIndex(desc: SerialDescriptor): Int {
      currentIndex++
      while (currentIndex < desc.elementsCount) {
         if (desc.isElementOptional(currentIndex)) {
            currentIndex++
         } else {
            return currentIndex
         }
      }
      return CompositeDecoder.READ_DONE
   }

changed to:
override fun decodeElementIndex(desc: SerialDescriptor): Int {
      currentIndex++
      while (currentIndex < desc.elementsCount) {
         return currentIndex
      }
      return CompositeDecoder.READ_DONE
   }

I think that fix might break nullable fields? I'd have to check.

Try 0.20.0 as this is fixed.


license?

hi there,
maybe i'm blind but i can't find any license information.
i would appreciate if you make this clear by adding a license into the git root.
thx

Duplicate of #512 - you might want to add your thoughts there. I'm closing this one, but feel free to chime in on the other one.


Improve reliability of AppHostTests.TestEndpointsReturnOk

Use WaitForText since some services are really slow to start (CosmosDB emulator takes 45s locally).
Use predicates in LoggerNotificationService since some texts are more complex than just Contains. For instance CosmonDBEmulator uses Started as the log when it's ready, but it also uses it many other times in the middle of some lines. Another example us MySql which starts the server twice (temp server).
Microsoft Reviewers: Open in CodeFlow

If this doesn't fix the cosmos/playground failure then I'll disable that, so we can get to closer to a cleaner CI.


Python Extension crashes Extension host on load (M1 Apple Big Sur)

Environment data

VS Code version: Version: 1.54.0-insider
Extension version (available under the Extensions sidebar): v2021.2.582707922
OS and version: Mac OS Big Sur M1 Mac Mini
Python version (& distribution if applicable, e.g. Anaconda): python 3.8.7 (pyenv install)
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
Relevant/affected Python packages and their versions: XXX
Relevant/affected Python-related VS Code extensions and their versions: XXX
Value of the python.languageServer setting: XXX

Expected behaviour
No crash, python extension should load
Actual behaviour
When loading code-insider the extension host starts up (logs below) and crashes immediately when starting the python extension
Steps to reproduce:
Fresh install of vscode on a Big Sur Apple M1 Computer?
I am also running the regular VSCode app. In there, it runs fine but i do experience regular "random?" crashes of the extension host
Logs
Developer Tools Logs
TMScopeRegistry.ts:45 Overwriting grammar scope name to file mapping for scope source.yaml.
Old grammar file: file:///Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/extensions/yaml/syntaxes/yaml.tmLanguage.json.
New grammar file: file:///Users/bastienboutonnet/.vscode-insiders/extensions/redhat.vscode-yaml-0.15.0/syntaxes/yaml.tmLanguage.json
register @ TMScopeRegistry.ts:45
TMScopeRegistry.ts:45 Overwriting grammar scope name to file mapping for scope source.toml.
Old grammar file: file:///Users/bastienboutonnet/.vscode-insiders/extensions/be5invis.toml-0.5.1/extension/toml.tmLanguage.json.
New grammar file: file:///Users/bastienboutonnet/.vscode-insiders/extensions/tamasfe.even-better-toml-0.10.0/toml.tmLanguage.json
register @ TMScopeRegistry.ts:45
console.ts:137 [Extension Host] (node:83404) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] seito-openfile extension started (at activate (/Users/bastienboutonnet/.vscode-insiders/extensions/fr43nk.seito-openfile-1.8.7/out/extension.js:14:13))
console.ts:137 [Extension Host] Loaded softwaredotcom.music-time v2.1.8 (at /Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.music-time-2.1.8/dist/extension.js:401:53615)
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/Users/bastienboutonnet/Library/Application Support/Code - Insiders/User/globalStorage/vscodevim.vim/.registers' (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'extHostLog' (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'extHostLog' (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3) (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'extHostLog' (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6) (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] swdc-tracker initialized and ready to send events to com-software-prod1.collector.snplow.net (at /Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.music-time-2.1.8/dist/extension.js:414:42596)
console.ts:137 [Extension Host] swdc-vscode: Loaded softwaredotcom.swdc-vscode v2.4.9 (at Object.K [as logIt] (/Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.swdc-vscode-2.4.9/dist/extension.js:3:6931))
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'extHostLog' (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8) (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] swdc-tracker initialized and ready to send events to com-software-prod1.collector.snplow.net (at /Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.swdc-vscode-2.4.9/dist/extension.js:419:13929)
console.ts:137 [Extension Host] swdc-vscode: liveshare version - 0.3.1291 (at Object.K [as logIt] (/Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.swdc-vscode-2.4.9/dist/extension.js:3:6931))
console.ts:137 [Extension Host] [CodeTime] connected to codemetrics websockets server (at A (/Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.swdc-vscode-2.4.9/dist/extension.js:281:6935))
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: TypeError: Cannot destructure property 'end' of 'i' as it is undefined.	at /Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.swdc-vscode-2.4.9/dist/extension.js:412:155435	at Generator.next (<anonymous>)	at o (/Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.swdc-vscode-2.4.9/dist/extension.js:412:154575)	at processTicksAndRejections (internal/process/task_queues.js:97:5) (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
console.ts:137 [Extension Host] (node:83404) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10) (at writeOut (internal/process/warning.js:32:3))
S @ console.ts:137
localProcessExtensionHost.ts:265 Extension Host
localProcessExtensionHost.ts:266 [CodeTime] websockets connection open[CodeTime] received websocket message:  {"type":"info","body":"connected to codemetrics websockets server","userId":168595}
abstractExtensionService.ts:466 Extension host terminated unexpectedly. Code:  1  Signal:  null
_onExtensionHostCrashed @ abstractExtensionService.ts:466
log.ts:296   ERR Extension host terminated unexpectedly. The following extensions were running: vscode.microsoft-authentication, vscode.debug-auto-launch, vscode.git, redhat.vscode-yaml, CoenraadS.bracket-pair-colorizer, Equinusocio.vsc-material-theme, equinusocio.vsc-material-theme-icons, Fr43nk.seito-openfile, Gruntfuggly.todo-tree, iceliu.highlight-icemode, kortina.vscode-markdown-notes, mhutchie.git-graph, ms-vsliveshare.vsliveshare, shardulm94.trailing-spaces, softwaredotcom.music-time, streetsidesoftware.code-spell-checker, vscodevim.vim, zhuangtongfa.material-theme, yzhang.markdown-all-in-one, bierner.markdown-emoji, bierner.markdown-image-size, ms-vscode.js-debug, vscode.github, atlassian.atlascode, jebbs.markdown-extended, vscode.github-authentication, marp-team.marp-vscode, vscode.configuration-editing, vscode.json-language-features, vscode.typescript-language-features, aaron-bond.better-comments, vscode.emmet, vscode.merge-conflict, vscode.testing-editor-contributions, alefragnani.Bookmarks, codespaces-contrib.codeswing, eamodio.gitlens, esbenp.prettier-vscode, ms-vscode-remote.remote-containers, softwaredotcom.swdc-vscode, ms-toolsai.jupyter, njpwerner.autodocstring, ms-python.python
notificationsAlerts.ts:40 Extension host terminated unexpectedly.
onDidChangeNotification @ notificationsAlerts.ts:40
bootstrap-window.js:259 [uncaught exception]: Error: This socket has been ended by the other party
g @ bootstrap-window.js:259
bootstrap-window.js:262 Error: This socket has been ended by the other party
    at Socket.writeAfterFIN [as write] (net.js:455)
    at b.write (ipc.net.ts:65)
    at b._writeNow (ipc.net.ts:338)
    at b.flush (ipc.net.ts:293)
    at b.dispose (ipc.net.ts:279)
    at Object.v [as dispose] (lifecycle.ts:96)
    at n.dispose (ipc.net.ts:687)
    at localProcessExtensionHost.ts:623
g @ bootstrap-window.js:262
events.js:292 Uncaught Error: This socket has been ended by the other party
    at Socket.writeAfterFIN [as write] (net.js:455)
    at b.write (ipc.net.ts:65)
    at b._writeNow (ipc.net.ts:338)
    at b.flush (ipc.net.ts:293)
    at b.dispose (ipc.net.ts:279)
    at Object.v [as dispose] (lifecycle.ts:96)
    at n.dispose (ipc.net.ts:687)
    at localProcessExtensionHost.ts:623
localProcessExtensionHost.ts:265 Extension Host
localProcessExtensionHost.ts:266 events.js:292      throw er; // Unhandled 'error' event      ^[Error: read ENOTCONN	at tryReadStart (net.js:573:20)	at Socket._read (net.js:584:5)	at Socket.Readable.read (_stream_readable.js:467:10)	at Socket.read (net.js:624:39)	at new Socket (net.js:376:12)	at Object.Socket (net.js:267:41)	at createSocket (internal/child_process.js:314:14)	at ChildProcess.spawn (internal/child_process.js:437:23)	at Object.spawn (child_process.js:557:9)	at Object.t.plainExec (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:9:702198)	at o.exec (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:29:17354)	at r.isCondaInCurrentPath (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:58060)	at processTicksAndRejections (internal/process/task_queues.js:97:5)	at async r.getCondaFileImpl (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:61125)	at async r.getCondaFile (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:57960)	at async r.getCondaInfo (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:58162)Emitted 'error' event on Socket instance at:	at emitErrorNT (internal/streams/destroy.js:92:8)	at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)	at processTicksAndRejections (internal/process/task_queues.js:84:21)] {  errno: 'ENOTCONN',  code: 'ENOTCONN',  syscall: 'read',  vslsStack: [    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {}  ]}
commentService.ts:198 Canceled: Canceled
    at Object.C [as canceled] (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5:1157)
    at r._remoteCall (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1676:9841)
    at Proxy.D.<computed>.I.charCodeAt.D.<computed> (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1676:6385)
    at s.getDocumentComments (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2383:49037)
    at file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:812:59625
    at Map.forEach (<anonymous>)
    at S.getComments (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:812:59604)
    at file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1927:4515
    at file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:55:19161

Extension Host Logs
[2021-02-21 22:06:56.273] [exthost] [info] extension host started
[2021-02-21 22:06:56.286] [exthost] [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication {"startup":false,"extensionId":{"value":"vscode.microsoft-authentication","_lower":"vscode.microsoft-authentication"},"activationEvent":"onAuthenticationRequest:microsoft"}
[2021-02-21 22:06:56.286] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/microsoft-authentication/dist/extension.js
[2021-02-21 22:06:56.295] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"extensionId":{"value":"vscode.debug-auto-launch","_lower":"vscode.debug-auto-launch"},"activationEvent":"*"}
[2021-02-21 22:06:56.295] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/debug-auto-launch/dist/extension
[2021-02-21 22:06:56.298] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":{"value":"atlassian.atlascode","_lower":"atlassian.atlascode"},"activationEvent":"*"}
[2021-02-21 22:06:56.298] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/git/dist/main
[2021-02-21 22:06:56.306] [exthost] [info] ExtensionService#_doActivateExtension redhat.vscode-yaml {"startup":true,"extensionId":{"value":"atlassian.atlascode","_lower":"atlassian.atlascode"},"activationEvent":"*"}
[2021-02-21 22:06:56.306] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/redhat.vscode-yaml-0.15.0/out/src/extension
[2021-02-21 22:06:56.351] [exthost] [info] ExtensionService#_doActivateExtension CoenraadS.bracket-pair-colorizer {"startup":true,"extensionId":{"value":"CoenraadS.bracket-pair-colorizer","_lower":"coenraads.bracket-pair-colorizer"},"activationEvent":"*"}
[2021-02-21 22:06:56.351] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/coenraads.bracket-pair-colorizer-1.0.61/out/src/extension
[2021-02-21 22:06:56.364] [exthost] [info] ExtensionService#_doActivateExtension Equinusocio.vsc-material-theme {"startup":true,"extensionId":{"value":"Equinusocio.vsc-material-theme","_lower":"equinusocio.vsc-material-theme"},"activationEvent":"*"}
[2021-02-21 22:06:56.364] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/equinusocio.vsc-material-theme-33.1.2/build/material.theme.config
[2021-02-21 22:06:56.371] [exthost] [info] ExtensionService#_doActivateExtension equinusocio.vsc-material-theme-icons {"startup":true,"extensionId":{"value":"equinusocio.vsc-material-theme-icons","_lower":"equinusocio.vsc-material-theme-icons"},"activationEvent":"*"}
[2021-02-21 22:06:56.371] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/equinusocio.vsc-material-theme-icons-1.2.2/out/src/extension
[2021-02-21 22:06:56.377] [exthost] [info] ExtensionService#_doActivateExtension Fr43nk.seito-openfile {"startup":true,"extensionId":{"value":"Fr43nk.seito-openfile","_lower":"fr43nk.seito-openfile"},"activationEvent":"*"}
[2021-02-21 22:06:56.377] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/fr43nk.seito-openfile-1.8.7/out/extension.js
[2021-02-21 22:06:56.395] [exthost] [info] ExtensionService#_doActivateExtension Gruntfuggly.todo-tree {"startup":true,"extensionId":{"value":"Gruntfuggly.todo-tree","_lower":"gruntfuggly.todo-tree"},"activationEvent":"*"}
[2021-02-21 22:06:56.395] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/gruntfuggly.todo-tree-0.0.196/dist/extension
[2021-02-21 22:06:56.409] [exthost] [info] ExtensionService#_doActivateExtension iceliu.highlight-icemode {"startup":true,"extensionId":{"value":"iceliu.highlight-icemode","_lower":"iceliu.highlight-icemode"},"activationEvent":"*"}
[2021-02-21 22:06:56.409] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/iceliu.highlight-icemode-0.0.6/extension
[2021-02-21 22:06:56.410] [exthost] [info] ExtensionService#_doActivateExtension kortina.vscode-markdown-notes {"startup":true,"extensionId":{"value":"kortina.vscode-markdown-notes","_lower":"kortina.vscode-markdown-notes"},"activationEvent":"*"}
[2021-02-21 22:06:56.410] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/kortina.vscode-markdown-notes-0.0.22/out/extension.js
[2021-02-21 22:06:56.418] [exthost] [info] ExtensionService#_doActivateExtension mhutchie.git-graph {"startup":true,"extensionId":{"value":"mhutchie.git-graph","_lower":"mhutchie.git-graph"},"activationEvent":"*"}
[2021-02-21 22:06:56.419] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/mhutchie.git-graph-1.28.0/out/extension.js
[2021-02-21 22:06:56.453] [exthost] [info] ExtensionService#_doActivateExtension ms-vsliveshare.vsliveshare {"startup":true,"extensionId":{"value":"ms-vsliveshare.vsliveshare","_lower":"ms-vsliveshare.vsliveshare"},"activationEvent":"*"}
[2021-02-21 22:06:56.453] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/ms-vsliveshare.vsliveshare-1.0.3784/out/prod/extension-prod
[2021-02-21 22:06:56.519] [exthost] [info] ExtensionService#_doActivateExtension shardulm94.trailing-spaces {"startup":true,"extensionId":{"value":"shardulm94.trailing-spaces","_lower":"shardulm94.trailing-spaces"},"activationEvent":"*"}
[2021-02-21 22:06:56.519] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/shardulm94.trailing-spaces-0.3.1/out/src/extension
[2021-02-21 22:06:56.536] [exthost] [info] ExtensionService#_doActivateExtension softwaredotcom.music-time {"startup":true,"extensionId":{"value":"softwaredotcom.music-time","_lower":"softwaredotcom.music-time"},"activationEvent":"*"}
[2021-02-21 22:06:56.536] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.music-time-2.1.8/dist/extension
[2021-02-21 22:06:56.614] [exthost] [info] ExtensionService#_doActivateExtension streetsidesoftware.code-spell-checker {"startup":true,"extensionId":{"value":"streetsidesoftware.code-spell-checker","_lower":"streetsidesoftware.code-spell-checker"},"activationEvent":"*"}
[2021-02-21 22:06:56.614] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/streetsidesoftware.code-spell-checker-1.10.2/dist/extension.js
[2021-02-21 22:06:56.620] [exthost] [info] ExtensionService#_doActivateExtension vscodevim.vim {"startup":true,"extensionId":{"value":"vscodevim.vim","_lower":"vscodevim.vim"},"activationEvent":"*"}
[2021-02-21 22:06:56.620] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/vscodevim.vim-1.18.9/out/extension
[2021-02-21 22:06:56.634] [exthost] [info] ExtensionService#_doActivateExtension zhuangtongfa.material-theme {"startup":true,"extensionId":{"value":"zhuangtongfa.material-theme","_lower":"zhuangtongfa.material-theme"},"activationEvent":"*"}
[2021-02-21 22:06:56.634] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/zhuangtongfa.material-theme-3.9.15/out/extension.js
[2021-02-21 22:06:56.651] [exthost] [info] ExtensionService#_doActivateExtension yzhang.markdown-all-in-one {"startup":true,"extensionId":{"value":"yzhang.markdown-all-in-one","_lower":"yzhang.markdown-all-in-one"},"activationEvent":"workspaceContains:README.md"}
[2021-02-21 22:06:56.651] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/yzhang.markdown-all-in-one-3.4.0/dist/extension
[2021-02-21 22:06:56.716] [exthost] [info] ExtensionService#_doActivateExtension bierner.markdown-emoji {"startup":false,"extensionId":{"value":"yzhang.markdown-all-in-one","_lower":"yzhang.markdown-all-in-one"},"activationEvent":"api"}
[2021-02-21 22:06:56.716] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/bierner.markdown-emoji-0.0.9/extension.js
[2021-02-21 22:06:56.786] [exthost] [info] ExtensionService#_doActivateExtension bierner.markdown-image-size {"startup":false,"extensionId":{"value":"yzhang.markdown-all-in-one","_lower":"yzhang.markdown-all-in-one"},"activationEvent":"api"}
[2021-02-21 22:06:56.786] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/bierner.markdown-image-size-0.0.4/extension.js
[2021-02-21 22:06:56.798] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.js-debug {"startup":false,"extensionId":{"value":"ms-vscode.js-debug","_lower":"ms-vscode.js-debug"},"activationEvent":"onCommand:extension.js-debug.clearAutoAttachVariables"}
[2021-02-21 22:06:56.798] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/extension.js
[2021-02-21 22:06:56.859] [exthost] [info] ExtensionService#_doActivateExtension vscode.github {"startup":false,"extensionId":{"value":"vscode.github","_lower":"vscode.github"},"activationEvent":"*"}
[2021-02-21 22:06:56.859] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/github/dist/extension.js
[2021-02-21 22:06:56.861] [exthost] [info] ExtensionService#_doActivateExtension atlassian.atlascode {"startup":false,"extensionId":{"value":"atlassian.atlascode","_lower":"atlassian.atlascode"},"activationEvent":"*"}
[2021-02-21 22:06:56.861] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/atlassian.atlascode-2.8.5/build/extension/extension
[2021-02-21 22:06:56.938] [exthost] [info] ExtensionService#_doActivateExtension jebbs.markdown-extended {"startup":false,"extensionId":{"value":"yzhang.markdown-all-in-one","_lower":"yzhang.markdown-all-in-one"},"activationEvent":"api"}
[2021-02-21 22:06:56.938] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/jebbs.markdown-extended-1.0.19/out/src/extension
[2021-02-21 22:06:57.183] [exthost] [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
[2021-02-21 22:06:57.191] [exthost] [info] ExtensionService#_doActivateExtension vscode.github-authentication {"startup":false,"extensionId":{"value":"vscode.github-authentication","_lower":"vscode.github-authentication"},"activationEvent":"onAuthenticationRequest:github"}
[2021-02-21 22:06:57.191] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/github-authentication/dist/extension.js
[2021-02-21 22:06:57.282] [exthost] [info] ExtensionService#_doActivateExtension marp-team.marp-vscode {"startup":false,"extensionId":{"value":"yzhang.markdown-all-in-one","_lower":"yzhang.markdown-all-in-one"},"activationEvent":"api"}
[2021-02-21 22:06:57.282] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/marp-team.marp-vscode-0.17.2/lib/extension.js
[2021-02-21 22:06:57.771] [exthost] [info] ExtensionService#_doActivateExtension vscode.configuration-editing {"startup":false,"extensionId":{"value":"vscode.configuration-editing","_lower":"vscode.configuration-editing"},"activationEvent":"onLanguage:jsonc"}
[2021-02-21 22:06:57.771] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/configuration-editing/dist/configurationEditingMain
[2021-02-21 22:06:57.773] [exthost] [info] ExtensionService#_doActivateExtension vscode.json-language-features {"startup":false,"extensionId":{"value":"vscode.json-language-features","_lower":"vscode.json-language-features"},"activationEvent":"onLanguage:jsonc"}
[2021-02-21 22:06:57.773] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/json-language-features/client/dist/node/jsonClientMain
[2021-02-21 22:06:57.789] [exthost] [info] ExtensionService#_doActivateExtension vscode.typescript-language-features {"startup":false,"extensionId":{"value":"vscode.typescript-language-features","_lower":"vscode.typescript-language-features"},"activationEvent":"onLanguage:jsonc"}
[2021-02-21 22:06:57.789] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension
[2021-02-21 22:06:57.799] [exthost] [info] ExtensionService#_doActivateExtension aaron-bond.better-comments {"startup":false,"extensionId":{"value":"aaron-bond.better-comments","_lower":"aaron-bond.better-comments"},"activationEvent":"onLanguage:jsonc"}
[2021-02-21 22:06:57.799] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/aaron-bond.better-comments-2.1.0/out/extension
[2021-02-21 22:07:00.008] [exthost] [info] eager extensions activated
[2021-02-21 22:07:00.017] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":false,"extensionId":{"value":"vscode.emmet","_lower":"vscode.emmet"},"activationEvent":"onStartupFinished"}
[2021-02-21 22:07:00.017] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/emmet/dist/node/emmetNodeMain
[2021-02-21 22:07:00.020] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":false,"extensionId":{"value":"vscode.merge-conflict","_lower":"vscode.merge-conflict"},"activationEvent":"onStartupFinished"}
[2021-02-21 22:07:00.020] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/merge-conflict/dist/mergeConflictMain
[2021-02-21 22:07:00.021] [exthost] [info] ExtensionService#_doActivateExtension vscode.testing-editor-contributions {"startup":false,"extensionId":{"value":"vscode.testing-editor-contributions","_lower":"vscode.testing-editor-contributions"},"activationEvent":"onStartupFinished"}
[2021-02-21 22:07:00.021] [exthost] [info] ExtensionService#loadCommonJSModule file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/testing-editor-contributions/dist/extension.js
[2021-02-21 22:07:00.024] [exthost] [info] ExtensionService#_doActivateExtension alefragnani.Bookmarks {"startup":false,"extensionId":{"value":"alefragnani.Bookmarks","_lower":"alefragnani.bookmarks"},"activationEvent":"onStartupFinished"}
[2021-02-21 22:07:00.024] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/alefragnani.bookmarks-13.0.1/dist/extension
[2021-02-21 22:07:00.028] [exthost] [info] ExtensionService#_doActivateExtension codespaces-contrib.codeswing {"startup":false,"extensionId":{"value":"codespaces-contrib.codeswing","_lower":"codespaces-contrib.codeswing"},"activationEvent":"onStartupFinished"}
[2021-02-21 22:07:00.028] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/codespaces-contrib.codeswing-0.0.13/dist/extension.js
[2021-02-21 22:07:00.107] [exthost] [info] ExtensionService#_doActivateExtension eamodio.gitlens {"startup":false,"extensionId":{"value":"eamodio.gitlens","_lower":"eamodio.gitlens"},"activationEvent":"onStartupFinished"}
[2021-02-21 22:07:00.107] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/eamodio.gitlens-11.2.1/dist/gitlens
[2021-02-21 22:07:00.215] [exthost] [info] ExtensionService#_doActivateExtension esbenp.prettier-vscode {"startup":false,"extensionId":{"value":"esbenp.prettier-vscode","_lower":"esbenp.prettier-vscode"},"activationEvent":"onStartupFinished"}
[2021-02-21 22:07:00.215] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/esbenp.prettier-vscode-5.9.2/dist/extension
[2021-02-21 22:07:00.233] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-containers {"startup":false,"extensionId":{"value":"ms-vscode-remote.remote-containers","_lower":"ms-vscode-remote.remote-containers"},"activationEvent":"onStartupFinished"}
[2021-02-21 22:07:00.233] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/ms-vscode-remote.remote-containers-0.161.0/dist/extension/extension
[2021-02-21 22:07:00.264] [exthost] [info] ExtensionService#_doActivateExtension softwaredotcom.swdc-vscode {"startup":false,"extensionId":{"value":"softwaredotcom.swdc-vscode","_lower":"softwaredotcom.swdc-vscode"},"activationEvent":"onStartupFinished"}
[2021-02-21 22:07:00.264] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/softwaredotcom.swdc-vscode-2.4.9/dist/extension
[2021-02-21 22:07:07.074] [exthost] [info] ExtensionService#_doActivateExtension ms-toolsai.jupyter {"startup":false,"extensionId":{"value":"ms-toolsai.jupyter","_lower":"ms-toolsai.jupyter"},"activationEvent":"onLanguage:python"}
[2021-02-21 22:07:07.074] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/ms-toolsai.jupyter-2021.2.576440691/out/client/extension
[2021-02-21 22:07:07.119] [exthost] [info] ExtensionService#_doActivateExtension njpwerner.autodocstring {"startup":false,"extensionId":{"value":"njpwerner.autodocstring","_lower":"njpwerner.autodocstring"},"activationEvent":"onLanguage:python"}
[2021-02-21 22:07:07.119] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/njpwerner.autodocstring-0.5.4/out/extension.js
[2021-02-21 22:07:07.364] [exthost] [info] ExtensionService#_doActivateExtension ms-python.python {"startup":false,"extensionId":{"value":"ms-python.vscode-pylance","_lower":"ms-python.vscode-pylance"},"activationEvent":"onLanguage:python"}
[2021-02-21 22:07:07.364] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension

Thanks for the bug report! We just wanted to quickly acknowledge we received it and we will triage this as soon as we can.

@bastienboutonnet Looking at the logs I'm not sure if it's the python extension that's causing the crash.
Can you please provide the logs as mentioned in the issue template.
Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Does disabling Python extension help? Please also try disabling all other extensions, and see if the crash happens with just Python extension enabled.

@karrtikr Thanks for the reply sorry I was not using my M1 mac during the week. I'm not sure where to find what you ask for. I don't seem to have this python option. See attached screenshot

@karrtikr I'm still not sure how to send you the info you need although I see you added the tag. Any chance you could guide me in the right direction?

I actually removed the tag, signifying that further info is not needed at the moment. I'll get back to you soon after I process the info you sent.

Oh gosh... @karrtikr really sorry about this --it's the end of day for me. Let me know if I can be of any further help. Thanks again for looking into this.

No worries.  In that case,

Uninstall Python extension (if you have pylance uninstall it first).
Close all instances of VS Code.
Go to~/.vscode/extensions.
Delete any folder with the name starting with ms-python.python*
Start VS Code, and install Python extension (also pylance if you uninstalled it in step 1).

See if that addresses the issue.

If it doesn't, can you try installing an older version of the extension, and see if your problem happens?
You can follow the prompts from "Extensions: Install Specific Version of Extension..." in the command palette:

Or you can open the extensions side bar, click on the settings for the Python extension and pick "Install Another Version...":

Try adding the following in your user settings,

"python.experiments.optOutFrom": [
    "All"
],

Your issue in kind of similar to https://github.com/microsoft/vscode-python/issues/15236, although not so much in terms of logs.

@karrtikr I think I'm seeing similar issues on our CI server, see here
https://github.com/microsoft/vscode-jupyter/runs/2042627991?check_suite_focus=true#step:12:141
read ENOTCONN: Error: read ENOTCONN
    at tryReadStart (net.js:573:20)
    at Socket._read (net.js:584:5)
    at Socket.Readable.read (_stream_readable.js:467:10)
    at Socket.read (net.js:624:39)
    at new Socket (net.js:376:12)
    at Object.Socket (net.js:267:41)
    at createSocket (internal/child_process.js:314:14)
    at ChildProcess.spawn (internal/child_process.js:437:23)
    at ChildProcess.spawn (/Users/runner/work/vscode-jupyter/vscode-jupyter/node_modules/process-on-spawn/index.js:74:13)
    at Object.spawn (child_process.js:557:9)
    at Object.t.plainExec (/Users/runner/.vscode/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:9:702198)
    at o.exec (/Users/runner/.vscode/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:29:17354)
    at /Users/runner/.vscode/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:45248
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at /Users/runner/.vscode/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:29:12358
    at getSearchPaths (/Users/runner/.vscode/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:67623)
    at f.suggestionsFromKnownVenvs (/Users/runner/.vscode/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:29:15371)

This issue doesn't seem to be related to yours, given the stack trace. The issue here is that the extension doesn't even load.

I would suggest they try installing the latest insiders extension from the blob store, provide the link & then try.
Looks like it is loading, but fails to load completely due to the socket error.
As you can see here,
 ^[Error: read ENOTCONN	at tryReadStart (net.js:573:20)	at Socket._read (net.js:584:5)	at Socket.Readable.read (_stream_readable.js:467:10)	at Socket.read (net.js:624:39)	at new Socket (net.js:376:12)	at Object.Socket (net.js:267:41)	at createSocket (internal/child_process.js:314:14)	at ChildProcess.spawn (internal/child_process.js:437:23)	at Object.spawn (child_process.js:557:9)	at Object.t.plainExec (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:9:702198)	at o.exec (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:29:17354)	at r.isCondaInCurrentPath (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:58060)	at processTicksAndRejections (internal/process/task_queues.js:97:5)	at async r.getCondaFileImpl (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:61125)	at async r.getCondaFile (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:57960)	at async r.getCondaInfo (/Users/bastienboutonnet/.vscode-insiders/extensions/ms-python.python-2021.2.582707922/out/client/extension.js:78:58162)Emitted 'error' event on Socket instance at:	at emitErrorNT (internal/streams/destroy.js:92:8)	at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)	at processTicksAndRejections (internal/process/task_queues.js:84:21)] {  errno: 'ENOTCONN',  code: 'ENOTCONN',  syscall: 'read',  vslsStack: [    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {},    CallSite {}, CallSite {}  ]} commentService.ts:198 Canceled: Canceled
This is from the very first issue on top.
Looks like its failing at the same place for everyone, i.e. it is identical to the issue I have mentioned.
I'm certain this has been fixed in insiders, fixed here https://github.com/microsoft/vscode-python/pull/15446

@bastienboutonnet

Please could you download the VSIX from here https://pvsc.blob.core.windows.net/extension-builds/ms-python-insiders.vsix
Go into VS Code select the command Install from VSIX
Select the VSIX that you just downloaded & install it
If prompted to reload VSCode, please do so.
Please test once again & confirm the issue no longer exists, thanks

@karrtikr @DonJayamanne
I tried the removal of the extension folders and uninstalling but this didn't work.
However, @DonJayamanne 's solution did work, the extension loads and (so far in the last 10minutes of useage) it doesn't seem to be crashing.
In terms of going forward should I always be installing vrom VSIX? or this was just to get the latest unreleased stuff?

I had the same problem.
@DonJayamanne solution work for me. I have the same question: how do I install updates in the future?

have the same question: how do I install updates in the future?
ys be installing vrom VSIX? or this was just to get the latest unreleased stuff?

Python extension has a concept of an insider vsix. Builds generated daily.

You can opt into the process of using the latest development build of the extension (Python: Switch to Insiders Daily/Weekly Channel)

Daily - You will get the latest builds automatically installed, once a day
Weekly - You will get the latest builds automatically installed, every week

If theres a new release on the marketplace, you will get that as well
I.e. just like VS Code Insiders, this is an insider build of the Python extenison.

Thanks all for the info! Closing as dup of https://github.com/microsoft/vscode-python/issues/15395.

@DonJayamanne @karrtikr thanks a lot for the help on this! <3

Fix has just been released in the stable version of the extension.


Allow for multiple values in missing_value or _FillValue

NetCDF files which specify multiple missing_value or _FillValue values will
result in a warning being issues and any elements which match any of the
missing_value or _FillValue values being decoded as NaN.
closes #471

Also -- a brief note in doc/whats-new.rst would also be appreciated.

Looks like there is something broken on NumPy 1.8:
https://travis-ci.org/xray/xray/jobs/72030577

I think those commits should cover all the comments, let me know if I missed any or if this need further refinement.

looks great, thanks!


Remove link out for non specified phenotypes

Description
Using one or more sentences, describe the proposed changes and the reason for making them.
Listed phenotypes link out to a view displaying all loci with this phenotypes. This link should be removed for the phenotypes that are of type 'non_specified'.
Views affected
List the website view(s) that you know are affected by this change.
If possible please provide a URL that shows the change. For Ensembl developers this could be your sandbox.
Gene, variation, structural variation phenotypes view.
example phenotype: "ClinVar: phenotype not specified"
Gene phenotypes view:

e100: http://www.ensembl.org/Homo_sapiens/Gene/Phenotype?db=core;g=ENSG00000182372;r=8:1755778-1801711;source=dbSNP;v=rs184988046;vdb=variation;vf=144518072
e101: http://ves-hx2-76.ebi.ac.uk:6080/Homo_sapiens/Gene/Phenotype?db=core;g=ENSG00000182372;r=8:1755778-1801711;source=dbSNP;v=rs184988046;vdb=variation;vf=144518072

Fixed for Variation: http://ves-hx2-76.ebi.ac.uk:6080/Homo_sapiens/Variation/Phenotype?db=core;r=8:1770872-1771872;v=rs184988046;vdb=variation;vf=144518072
Fixed for Structural Variation: http://ves-hx2-76.ebi.ac.uk:6080/Homo_sapiens/StructuralVariation/Phenotype?db=core;r=X:154030127-154031213;sv=nsv1197401;svf=123066747;vdb=variation
Possible complications
None expected.
Merge conflicts
None.
Related JIRA Issues (EBI developers only)
ENSVAR-2926

Tagging @sarahhunt as per our SOP.


Ooops and Oops

VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T08:03:11.395Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

docomment
k--kato
0.0.14

csharp
ms-vscode
1.9.0

PowerShell
ms-vscode
0.12.2

embrace
mycelo
1.0.0

Steps to Reproduce:
1... Difficult  o impossible Indentation
2....Intellisense non captching real time
3 ...Missing  a parenthesis and all is crazy...

@wilsonlopez17III17 Can you please give more specific steps? Like what language you are in, what you are typing, what you expect to happen vs. what actually happens. A gif or a screenshot could also help, but as it stand right now I don't know what you mean...


Question: difference from libavc

This project seem to have a significant code overlap with https://github.com/ittiam-systems/libavc
libavc seems to be used in AOSP and comes with an encoder and decoder, while this repository has only a decoder, with some additional "plugins": an ffmpeg plugin providing browser.
From what I gather, the actual decoder code is virtually the same. What is the reason between split then?
If I only need a decoder, am I better off using this repo, lib264?

Yes, this repo is mainly to enable integration of H264 Decoder into systems beyond AOSP. Licensing terms are different compared to AOSP and code base supports plugins like FFmpeg, Browser Plugin with WASM build.
Currently the repo has support for H264 Decoder.


Dict as id does not work

When Python dicts are used as element id, all of the elements get the same React key [object Object] because dicts are not stringified correctly. Because of this, all elements are on top of each other.
Being able to use dicts as element ids is especially important for Pattern-Matching Callbacks.
Example:
app.layout = html.Div([
    html.H1("Dash Draggable"),
    dash_draggable.GridLayout(
        id='draggable',
        save=False,
        children=[
            html.Div("HELLO 1", id={"type": "text", "id": "hello1"}),
            html.Div("HELLO 2", id={"type": "text", "id": "hello2"}),
            html.Div("HELLO 3", id={"type": "text", "id": "hello3"}),
            html.Div("HELLO 4", id={"type": "text", "id": "hello4"})
        ]
    ),
])

Léon Lazar<EMAIL_ADDRESS>on behalf of Mercedes-Benz Tech Innovation GmbH, Imprint

Any update about this? besides manually converting the id to a string?
Any other solutions to this issue?

Any update about this? besides manually converting the id to a string? Any other solutions to this issue?

I fixed it in our fork https://github.com/mercedes-benz/dash-draggable/tree/bugfix/dict_as_id
Since no one seems to merge PRs, I did not bother to open another PR.
To use it, you would have to build the package by yourself and install it manually: https://github.com/MehdiChelh/dash-draggable/blob/5fd5d87c6aaa0a1bd4e666540d693314a03ac616/README.md


Transaction sends but gets stuck in mempool

Issue Template
Context
I have a transaction which was created via the iOS wallet and got stuck in the mempool.
I've tried sending the raw tx which v5.0 and it gets send but still ends up stuck in the mempool.
When sending the same transaction with a v4.0 codebase it rejects the tx before sending it.
The debug.log error for v4.0 is:
ERROR: FetchInputs() : 75874fa8c8 mempool Tx prev not found a9cdcb0897

https://github.com/vergecurrency/VERGE/blob/9d0cd61f8d2a45a90cba5a2ad4d0167f4b85d240/src/main.cpp#L1430
The console command sendrawtransaction stops here:
https://github.com/vergecurrency/VERGE/blob/9d0cd61f8d2a45a90cba5a2ad4d0167f4b85d240/src/rpcrawtransaction.cpp#L525
The raw transactions:
[encoded data, 7770 characters]

From what I can see the minimal fees required for a transaction in 4.0 and 5.0 are different. In 4.0 we can see the following codes.
https://github.com/vergecurrency/VERGE/blob/9d0cd61f8d2a45a90cba5a2ad4d0167f4b85d240/src/main.cpp#L614-L616
While in 5.0 the following codes are used.
https://github.com/vergecurrency/VERGE/blob/8e663893d96cf8352be8dcc89895ec9efdc9b87d/src/wallet/fees.cpp#L18-L26
This means in 5.0 will have lower minimal fees required, if transaction is larger than 1000 bytes.

i also have transactions stuck in memorypool?? (since june 2nd)

no idea what to do??
#help wanted

i also have transactions stuck in memorypool?? (since june 2nd)

no idea what to do??
#help wanted

He,
You could try this:

Export your private key
Delete wallet.dat file
Open wallet with zero balance and already synched
Import the private key
Fire the rescanblockchain call from the console and wait until its done.

With the next transaction you try to create small transactions, to prevent them getting stuck.
Until this bug is fixed.

thank you a lot 👏

is this correct, that the fee calculation is disabled and set constant to 0.1 XVG ?
https://github.com/vergecurrency/VERGE/blob/603654beef9b60823d0aa30481de25448a0c5e43/src/policy/feerate.cpp#L26

I’ve opened a branch this morning, working on a fee fix
https://github.com/vergecurrency/VERGE/tree/bugfix-fees-structure
As our feerate isn’t Variable it doesn’t make sense to keep those files anyways
But for now I will keep it simple

this fix is only on tx create not relay check, so i have dead transactions in mempool of v5 nodes, which will not accepted from v4 nodes. so this transactions will never get written on blockchain by v4 mining nodes.

@tpfuemp sure, but you have to manually abandon the transaction. It will not automatically remove your tx from the mempool just by too low fees

this won't help. after erasing mempool the malicious transactions will be rebroadcasted after some minutes from other v5 nodes. As I understand the code right the fee is checked against fix value (0.1), regardless of transactionsize.
to be clear - I won't bother you with useless tasks. my intention is to find differences on network level between v4 and v5 nodes to get v5 nodes working for mining. as @pinpins mentioned on other thread, v4 has reached "end of life" for mining, so we should get v5 compatible working.

@tpfuemp Surely true there. I feel the same way but we are also making some steps towards this goal and I don't think this is useless. I think we should rather "forbid" too low fees you basically can't send a tx with a fee below what you described (0.1 XVG/KB)

i also have transactions stuck in memorypool?? (since june 2nd)

no idea what to do??
#help wanted

He,
You could try this:
* Export your private key

* Delete wallet.dat file (backup first!!!!)

* Open wallet with zero balance and already synched

* Import the private key

* Fire the `rescanblockchain` call from the console and wait until its done.

With the next transaction you try to create small transactions, to prevent them getting stuck.
Until this bug is fixed.

So I should export every private key that holds XVG that is stuck and re-import them in this manner?

So I should export every private key that holds XVG that is stuck and re-import them in this manner?

Exactly, you could also try the "abandon" transaction functionality, but that only works if it is in mempool only :)

Okay, I'm super new to this stuff... Any hint as to where to find how this works?
I can't find it in the command-line options...

unlock your wallet first.. either through the UI .  Then go to Help -> debug window -> console
to export private key it's:
dumpprivkey "address"
so like:
dumpprivkey "Daslkdjas9321481" , or whatever address it is you have your coins on.
Before you do the next step, make sure that's the only address in your wallet that has coins.  If you have 50,000 coins on that address, go to:
https://verge-blockchain.info/
search for your address, and make sure it really shows 50,000.  If it doesn't, your coins are likely on other addresses
So copy the result of your dumpprivkey to a notepad... keep very safe and secure.  This is the key to your wallet and doesn't require a password/passphrase.
Close down the QT wallet.    Most likely in C:\Users\YOU\AppData\Roaming\Verge
make a backup of your wallet.dat (copy it to a jump drive)... and then rename it to like "wallet_old.dat"
open up QT wallet again
back to help -> debug -> console
now do:
importprivkey "address"
Should take a few minutes.
Now your mempool should be clean.. and proceed with smaller transactions

The fee problem is fixed with #948

Anyone had a play with TX size?  What is the most you can send without it getting stuck?

Well with the latest master you will be able to send any tx size without being stuck.
For now, there's a certain area where this happens. 1000 bytes - 1024 bytes etc ...

Hello Marpme, despite the issue being closed about 23 hours ago, I do have 2 questions which are directly related to this issue:

How does one ensure that transactions "stuck" in mempool (because size too large > 1kb) since June 30th (4 days) go through at this point? I seem to misunderstand what an updated master means; i.e. does the master affect the VergeLumos <IP_ADDRESS> wallet (must we download a new version of the wallet?)

Transactions which are "Status: 0/unconfirmed, in memory pool" which are not eligible for cmd abandontransaction, will stay stuck for how long? And is there another way of getting these unstuck?

Also I meant to talk to you about something else: I understand that very little people are currently working on this project and I can only imagine the level of fatigue and strain, as such, I sympathize with you guys, nonetheless, this is one of the most complicated and counter-intuitive platforms (my humble opinion). As a miner, having to wrap my head around the concept that one must bundle transactions together before being able to transact was not easily found nor explained - I have mined using ASIC and GPU several currencies and this is a first for me - and the lack of info to boot is a bit much. The inability to increase the transaction fee despite it being an option in the wallet is baffling at best; But what really makes things worst is I have seen comments and responses from a member of your team which tbh are somewhat curt as the onerous of knowledge seems to be put on us the users. The users cannot make any assumptions as to the fitness of what is put forward by your team and trust in basic functionality based on the expectation of the average user is legitimate - when these people express their concerns, in my humble opinion, these should not be ridiculed of dissed just because they are not up to your teammates standards of technical intellect - these are your customers, backers, believers and some of them have vested interests in your work and support to be able to access their funds (THEIR MONEY). So may I suggest that a particular member of your team (I think you may know who I am referring to) keep this in mind next time he/she feels that the pesky customers are bothersome and more-or-less tells them to piss off. Verge was once a project full of promise of a bright future and those who have stuck with the project despite several incidences such as the "hacking" of the mining algo and the drama concerning that the core code is allegedly a copy paste of another project, deserve a little respect IMO.
If I got any part of this incorrect, please forgive me.
Peace my friend
0xed

Wait for the new release and download it, afterwards everything will be 👌
It's not like that I can time-travel and implement everything at once, but we are working on rejected "too low fee" tx's.
I assume that you might be using new functionality too, but obviously they won't work now, as 99% of the network is still dominated by v4's and they will reject everything unknown or new to them. So you always have the opportunity to just rollback to v4 - always keep that in mind :)

Thanks Marpe, I do appreciate the info - however, in what time-frame

do the "stuck in mempool" transactions get released/reverted?

If you want to clear them, you can check out my instructions here:
https://github.com/vergecurrency/VERGE/issues/853#issuecomment-506586680
Basically it involves exporting your address private key, creating a new wallet.dat (make sure you create a backup and passphrase on it) , and then importing private key again.

and just out of curiosity -- has your wallet been opened and running constantly since 6/30?  I remember reading somewhere that they will eventually time out, but that process only takes a couple days (your wallet needs to be open the whole time).
So if your wallet has been running since those 6/30 transactions, and they are still stuck, I think you might need to follow those instructions to clear them out.

and have you tried to right click the transaction and select "Abandon transaction" ?  If that option isn't available, then your only route is to do the export/new wallet/import I believe.

you can also try to delete mempool.dat - file and start Verge-wallet with option -zapwallettxes

We should actually also reject low fee txs inside the mempool, that won’t solve the problem of broken txs in your wallet as you can create them anyways (somehow)


Integrate Java SDK with new service protocol negotiation mechanism

This commit lets the Java SDK extract the accepted ServiceDiscoveryProtocolVersions
from the accept header of the discovery request and sends a correspondingly encoded
response back if the endpoint supports the service discovery protocol version.
Likewise the SDK is now extracting the service protocol version from the content type
header when the service is invoked. If the endpoint does not support the specified
protocol version, then it will reject the request with a status code 415.
We are no longer sending the protocol version via the message headers
of the start message. This commit removes this logic.
This fixes https://github.com/restatedev/sdk-java/issues/317.

The PR is still missing the Lambda handler part.

Thanks for the review @slinkydeveloper. I've addressed your comments and added the support for the lambda case. PTAL.

The CounterTest should be failing because it needs restatedev/restate#1526

I've tested the e2e tests locally and they passed with restatedev/restate#1526.

Thanks for the review @slinkydeveloper. Merging this PR once GHA gives green light.


Move all 2015 sports pages into a subfolder

Will need to:
-Move into subfolder
-Change all links to subfolder
-Change links in each page (css and js links need to refer up a folder, links to other pages need to include subfolder name before page name)

Instead, I:

Changed all the html file names to have "Sports_" at the beginning of the file names
Changed all links (to pages that end in "Overview" to also navigate to "Sports([a-zA-Z0-9_.]+)_Overview" instead

As of 5pm on 12/16/23, I have not yet uploaded these new files to Github.

Next task: Move old sports html files to depreciated Github folder, then upload my new files

Looks like I did complete the task above on 12/16/23


No connected sign on dungeonmastersvault

Checklist

[X ] The FAQ does not resolve my issue.
[X ] This bug report is not a duplicate.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'Dungeonmastersvault.com'
Click on 'Character builder'
No connected to vtt bridge sign

Expected behavior
Connected to vtt bridge
Screenshots

Environment
Please complete the following information:

Device: [e.g. iPhone, Desktop]
OS: [e.g. Windows 10, Linux]
Browser: [e.g. Google Chrome, Mozilla Firefox]
Extension version: [e.g. v1.0.0]
Google Chrome 1.4.0
Additional context
I have updated the extension but for some reason there still no connected to vtt bridge on dungeonmastersvault

Sorry about that i have been using wrong

I'm glad your issue was resolved!
I assume this was the problem?

Make sure that you clicked the www link. If you are on the correct page, the URL should end with ?frame.


Optionally Include password in the params.query object passed to User.find()

I have a DB that requires userName and Password to verify the user record.  The user service only receives the userName now.  The password is left off.  I understand that it isn't necessary for most systems. But it is for mine.
How about a config option to include password in params.query?
If I am not mistaken, a little code could be added right here
https://github.com/feathersjs/feathers-authentication/blob/master/src/services/local/index.js#L22-L26
maybe something like this?
const params = {
   query: {
        [this.options.usernameField]: username
    }
};
//optionally add the password to params.query
if(this.options.includePasswordInQuery){
   params.query[this.options.passwordField] = password
}

Would you consider a pull request with this?
Thanks

I think there already was a feature request somewhere to be able to query for different fields. But there still needs to be a password comparison function. How are you comparing your passwords? I assume they aren't just plain text.

In this DB The passwords are stored hashed, but I can't access the hash.  All I can do is query the DB with a UserName and Password, if the Password matches I get back the User Record.  If it doesn't I do not.
So I query the DB, if the UserRecord comes back I hash the password right then and stick it on the userObject.  Then the normal comparison function is happy and generates the token.
A bit of hack I'll grant you but what else can I do :-)

#165 seems related


Maps is not displaying as of today

Hi!
Today, Maps stopped displaying in projects. Do you know how to solve this?
(It's not a code problem nor an API problem..)

@mariemchtourou I think this may be related to issue #296 bresam forked this project and is working on a fix


Submission: STANNcam

What kind of resource is this?
Library
If other was selected, what is it?
No response
Logo
https://raw.githubusercontent.com/jack27121/STANNcam/master/LogoJack.png
Description
About An easy to use camera object for Gamemaker studio, with options to change game and GUI resolution independently, and upscale pixelart
Authors
stannco
Link to your resource
https://github.com/jack27121/STANNcam
Tags
camera, resolution
Post
STANNcam is a pixel-perfect camera and resolution manager system for GameMaker (and onwards)
It foregoes GameMaker's viewports and application_surface,
and instead gives full control on where and in which order to draw your different camera's contents to the screen.
What versions does your resource support?

[ ] LTS
[X] 2023.1+
[ ] 2024.2+
[ ] Latest current runtime version (local packages)
[ ] Latest current runtime version (prefabs)
[ ] New runtime (local packages)
[ ] New runtime (prefabs)
[X] I've selected a version per above

What platforms has this been tested on?

[X] Windows
[ ] MacOSX
[ ] Linux
[ ] HTML5/GX.games
[ ] iOS
[ ] Android
[ ] Consoles
[ ] All of the above

Added.


Issue with foreign characters

Hi,
Not sure where this issue is coming from but I'm trying to implement 2 things:

Next 13
Contentlayer

In local environment, there's no issue at all.
When it comes to prod, (I'm using AWS S3 for static hosting)
it gets me the following error.
SyntaxError: Unexpected token '한', ..."00\\uB2A5\한 \\uB180\"... is not valid JSON
    at JSON.parse (<anonymous>)
    at 12694 (781-7ce873b7c2a3a830.js:1:353)
    at s (webpack-92af148b2d97d254.js:1:151)
    at 65857 (page-623c86b8da64ad0d.js:1:206)
    at s (webpack-92af148b2d97d254.js:1:151)
    at S (596-100846a90423a0a4.js:9:2045)
    at P (596-100846a90423a0a4.js:9:1313)
    at 596-100846a90423a0a4.js:9:6084

The application supports 3 languages, English, Spanish and Korean.
The character 한 is from Korean contents (mdx file)
When I deleted the whole Korean contents and published, the issues are gone and application works fine.
Currently using:
"contentlayer": "^0.3.1",
"next-contentlayer": "^0.3.1",
"next": "^13.4.0",

But the latest version was the same.
Also, I use output: 'export' for static hosting in S3.
Currently I deleted all date related stuff and modified all components into the following format
const Whatever = () => {}
default export Whatever;

just to avoid use client error that could possibly happen.
Any idea what's causing this?
Thank you!

Found the issue.
When I contentlayer dev, then access to the troubling content in .contentlayer folder,
It looks like,
children:[\"Pedometer \\uB294 \\uC13C\\uC11C\\uB85C step\\uC744 \\uCE21\\uC815 \\uAC00\\uB2A5\\uD55C \\uB180\\uB77C\\uC6B4 package \\uC774\\uB2E4.\",

Then when I build, in out folder, the same content looks like,
children:[\\"Pedometer \\\\uB294 \\\\uC13C\\\\uC11C\\\\uB85C step\\\\uC744 \\\\uCE21\\\\uC815 \\\\uAC00\\\\uB2A5\\\uD55C \\\\uB180\\\\uB77C\\\\uC6B4 package \\\\uC774\\\\uB2E4.\\",

There's a lot more back slash involved here.

Same issues here. Can't build content with Korean characters😿

same issue

same..........................korean characters....

hi. I too have been struggling with the same problem for several days.
I ended up downgrading the versions of nextjs and contentlayer.
In the end, I solved these problems, and both build and deployment worked normally.
my nextjs version is '13.5.4' and contentlayer version is '0.3.4'.
I hope these problems are resolved as soon as possible.
Thank you🥲

I couldn't solve this problem either

Small update here.
Couldn't deal with the issue but just giving up mdx format could resolve my issue (at least).
Feels not right giving up such useful tool but....better than not working (or waiting for fix).
So, in summary:

Give up mdx and use md
If using vscode, try markdown lint extension to avoid mistakes in format
My current setup in next.config.js (Again, I run static contents)

const { withContentlayer } = require("next-contentlayer");

const nextConfig = {
  output: 'export',
  reactStrictMode: true,
  swcMinify: true,
  compress: true,
  images: {
    unoptimized: true
  },
};

module.exports = withContentlayer(nextConfig);

Well, it's unfortunate to say that I couldn't find a proper solution.
Hopefully someone else finds it. 😄


nextpnr cant route design, Vivado works - ERROR: timing analysis failed due to presence of combinatorial loops, incomplete specification of timing ports, etc.

ERROR_timing_analysis_failed_due_to_presence_of_combinatorial_loops_incomplete_specification_of_timing_ports.zip

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


feat: auto fill content in store's files

auto fill content in store's files
auto fill content in the files in models folder

Codecov Report

Merging #908 (d7d3fcf) into release/1.3.0 (fe359e4) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release/1.3.0     #908   +/-   ##
==============================================
  Coverage          57.14%   57.14%
==============================================
  Files                  1        1
  Lines                 70       70
  Branches              15       15
==============================================
  Hits                  40       40
  Misses                30       30

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 fe359e4...d7d3fcf. Read the comment docs.


NAT Configuration for custom external port

Empire Version
2.0 / 1.6
OS Information (Linux flavor, Python version)
Debian
I want to route over WAN and I've tried many suggested solution and it didn't work.
Config:
Server -> publicDNS:3322 (custom port, can't be changed to 80)
local IP:1100
3322 is mapped to 1100 on the firewall
I have tried setting host -> publicDNS and port -> 3322 but it won't work
What is the right setting?

see #363


Create spritesheet for SpriteFrames by drag and dropping.

Close https://github.com/godotengine/godot-proposals/issues/378

@dankan1890 Why was this closed?

Sorry, my mistake :(

Needs a rebase, otherwise should be OK to merge.

Needs a rebase, otherwise should be OK to merge.

Thanks!

Thanks!

Cherry-picked for 3.2.4.

Cherry-picked for 3.2.4.


refactor: explicit config loading in examples

A proposal in the light of potential issues regarding how we load the next-i18next.config.js.
Currently it's not possible to use the examples "as is" in a monorepo structure, they will lead to errors like
Error: Cannot find module '/home/sebastien/github/next-i18next/examples/simple/next-i18next.config.js'

See https://github.com/i18next/next-i18next/pull/2012 for reasons why and https://github.com/i18next/next-i18next/issues/1917#issuecomment-1285401978.
I feel the examples should cover this by default.
I would even go further later on and take the opportunity of upcoming release (v13) to include some breaking changes.

appWithTranslation: make the second parameter (the config override) mandatory.  It seems okay cause people upgrading will have to do it only on one file (_app.tsx).
serverSideTranslations: This is more risky as there will be multiple occurences of it in user routes. So BC more complex to deal with. A suggestion would be to create a new function (ie: getServerTranslations(config, locale, namespaces?)). So people affected could progressively adapt (ie: when they move to monorepo...)

In my experience, I used to not rely directly on the serverSideTranslations and wrap it in something similar to this:
/**
 * Retrieve translations on server-side, wraps next-i18next.serverSideTranslations
 * to allow further customizations.
 */
import type { SSRConfig, UserConfig } from 'next-i18next';
import { serverSideTranslations } from 'next-i18next/serverSideTranslations';
import nextI18nextConfig from '../../../next-i18next.config';

export const getServerSideTranslations = async (
  locale: string,
  namespacesRequired?: string[] | Readonly<string[]> | undefined,
  configOverride?: UserConfig | null
): Promise<SSRConfig> => {
  const override = configOverride ?? nextI18nextConfig;

  // Slice needed here cause serverSlideTranslations does not accept Readonly type
  return serverSideTranslations(locale, namespacesRequired?.slice(), override);
};

https://github.com/belgattitude/nextjs-monorepo-example/blob/3f385aeb3b392671cce91114416ed32312d6ea6c/apps/nextjs-app/src/lib/i18n/getServerSideTranslations.ts#L6-L18
Don't know yet if it would make sense to:

either document/recommend to wrap like the last example
either add the 2 BC (or paths) suggested above

I'll take some time to think about this. Not sure myself

At the beginning the simple example was really there to have the minimum amount of code to use next-i18next...
Alternatively, a new example with more advanced setup could be created?

Make sense.

I'll plan to rework the examples. Moving to a monorepo would make sense. I'll come with a proposal soon
In the meantime I've added a section to help users facing the issue

https://github.com/i18next/next-i18next/pull/2018/files#diff-2a0bc40e955e3ada6192d2991fb316c2e356e510e2cdab1f6f3a14db0e41bf2b

@adrai I feel the requirement of passing next-i18n.config.js will have to be done at some point.
Without passing the config I fear we actually makes it complex.
Example

https://github.com/i18next/next-i18next/issues/1917#issuecomment-1320439358
(and many others)

I'll keep this PR open for investigation after v13.0.0 and update the TROUBLESHOOT once I'm sure


feat: add kms remote IP filter

Description
Please add a description of the changes that this PR introduces and the files that
are the most critical to review.

Closes: #684
Add IP filter to allow a connection from remote ostracon-kms

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


DB: integrate database

Create tables
For users and maybe even for previous played games to have a replay functionality

User Table created
In this commit I added the insert script for the users table and the users repository
237c00c

Everything is in the database now.


Share Context or State Across components?

Is there a way to share context or state across components? I have multiple web components that need access to the same source of data. Is there a way I can share this data with all of them with a store of some kind? Or is this something I would have to custom code?
Thanks!

Each of the Web Components we create has its own React execution, so there's no React-based way to share info between them.
It should be fairly straight-forward with some external JS though, mimicking React methodology. I have not tested this, but this is the general idea:
const GLOBAL_STATE_KEY = "myGlobalState"

function useGlobalState() {
  if (!window[GLOBAL_STATE_KEY]) {
    // This is where we store the current value, the setters that need to be informed of changes,
    // add/remove functions for setters, and the logic to inform those setters.
    window[GLOBAL_STATE_KEY] = {
      value: {}, // default state value
      setters: [],
      addSetter: (setter) => {
        window[GLOBAL_STATE_KEY].setters.push(setLocalState)
      },
      removeSetter: (setter) => {
        const index = window[GLOBAL_STATE_KEY].setters.indexOf(setLocalState)
        if (index > -1) {
          window[GLOBAL_STATE_KEY].setters.splice(index, 1)
        }
      },
      setState: (value) => {
        window[GLOBAL_STATE_KEY].value = value
        for (const setter of window[GLOBAL_STATE_KEY].setters) {
          setter(value)
        }
      },
    }
  }

  // We're storing the state in React's useState, but storing the setter outside React so we can call it when we need.
  const [ state, setLocalState ] = useState(window[GLOBAL_STATE_KEY].value)

  useEffect(() => {
    window[GLOBAL_STATE_KEY].addSetter(setLocalState)
    return () => window[GLOBAL_STATE_KEY].removeSetter(setLocalState)
  }, [])

  return [ state, window[GLOBAL_STATE_KEY].setState ]
}

hey @christopherjbaker, being able to share context accross web components is critical and would enable many things (all things react really).
i tried to do something about it by writing an events-based shim for react context, still wip, but can you please check this out https://github.com/mathematikoi/eventually

I faced same challenge for the modal instance and two places that trigger it.
I simply used mobx ( https://mobx.js.org/getting-started.html ) with a singleton store instance, by exporting an instantiated store object:
export interface ModalStore {
  isOpen: boolean;
  open: () => void;
  close: () => void;
}

class ModalStoreImpl implements ModalStore {
  isOpen = false;

  constructor() {
    makeObservable(this, {
      isOpen: observable,
      open: action,
      close: action,
    });
    this.isOpen = false;
  }

  open = () => {
    this.isOpen = true
  };

  close = () => {
    this.isOpen = false;
  };
}

export const modalStoreSingleton: ModalStore = new ModalStoreImpl();

And now each instance of some top lvl component wrapped into a web component just uses this as observable:
observer(() => {return modalStoreSingleton.isOpen ?
open modal
 :
closed modal
});


Floor built in function return type

https://github.com/apache/arrow-datafusion/blob/f0af5eb949e2c5fa9f66eb6f6a9fcdf8f7389c9d/datafusion/expr/src/built_in_function.rs#L899-L915
from this code floor() only retun float type
but from postgresql
floor ( numeric ) → numeric

floor ( double precision ) → double precision

Nearest integer less than or equal to argument

floor(42.8) → 42

floor(-42.8) → -43

https://www.postgresql.org/docs/current/functions-math.html

seems cast in some place
❯ explain verbose  select floor(-1);
+------------------------------------------------------------+--------------------------------------------------------------------------------------------------------+
| plan_type                                                  | plan                                                                                |
+------------------------------------------------------------+--------------------------------------------------------------------------------------------------------+
| initial_logical_plan                                       | Projection: floor(Int64(-1))                                                                           |
|                                                            |   EmptyRelation                                                                                |
| logical_plan after inline_table_scan                       | SAME TEXT AS ABOVE                                                                                |
| logical_plan after type_coercion                           | Projection: floor(CAST(Int64(-1) AS Float64))                                                          |
|                                                            |   EmptyRelation                                                                                |
| logical_plan after count_wildcard_rule                     | SAME TEXT AS ABOVE                                                                                |
| analyzed_logical_plan                                      | SAME TEXT AS ABOVE                                                                                |
| logical_plan after eliminate_nested_union                  | SAME TEXT AS ABOVE                                                                                |
| logical_plan after simplify_expressions                    | Projection: Float64(-1) AS floor(Int64(-1))                                                            |
|                                                            |   EmptyRelation                                                                                |
| logical_plan after unwrap_cast_in_comparison               | SAME TEXT AS ABOVE                                                                                |
| logical_plan after replace_distinct_aggregate              | SAME TEXT AS ABOVE                                                                                |
| logical_plan after eliminate_join                          | SAME TEXT AS ABOVE

If you are saying that floor(decimal) should return decimal that makes sense to me

@alamb, @Ted-Jiang, hi! I created draft PR
if the idea is ok, would like to compare all return types in pg and fixed them

If you are saying that floor(decimal) should return decimal that makes sense to me

Yes, basiclly all numeric  type  should have the return type same as input.
And i have check the numeric  type list is same as pg


Pin karma, karma-mocha dev dependencies

Codecov Report

Merging #10 into master will decrease coverage by 1.4%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage     100%   98.59%   -1.41%
==========================================
  Files           1        1
  Lines          71       71
==========================================
- Hits           71       70       -1
- Misses          0        1       +1

Impacted Files
Coverage Δ

lib/index.js
98.59% <0%> (-1.41%)
: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 1f71e9d...f415342. Read the comment docs.


Develop SWF AWS VPC Module

Created VPC resources in https://github.com/defenseunicorns/uds-infrastructure-software-factory-aws


Overeager refmt punning

module Foo = {
  type bar = {foo:Baz.foo};
}

goes to:
module Foo = {
  type bar = {foo};
};

Looking into this.

@rickyvetter Pull request with fix is ready for review & CI.

Thanks for the quick fix, @IwanKaramazow