how to run code?

Hi
I can't run your code.
Please explain how should run it at README.md
Thank you.

Hi,
I'll check and fix it soon.
@kianakiaei

@kianakiaei
Hi, I’ve upgrade this code.
Just try to run the script "model_test.py". If nothing goes wrong, it would test the example model on the example data. This means the code is ok. Then, change the parameters and run "train.py" to start a new training~


add this to your wiki (command lines to to change ressources values)

to change the value of ressources while in the game by using the debug console as host or admin
resources_infantry = value;
resources_ammo = value;
resources_fuel = value;
i had to dig a long time to find this and this should be quite an obvious thing to know!

Deprecated since about 1,5 years. Won’t be added.

If anything it could be added to GREUH wiki:
http://greuh-liberation.wikia.com/wiki/GREUH_Liberation_Wikia
KP Liberation != GREUH Liberation


Page has bug and not working

Steps to replicate,

open the page (and inspect element)
select country
click on any range
Error:
SyntaxError: Unexpected token < in JSON at position 0
console. @ index.js:1375

As I can log the server returns 500 because file not found (Macedonia, Serbia JSON)

Yeap there is an update is going on. Just wait for few hours.


Restart: Cleanup kernel process

Follow up on #853
This will ensure to kill the old kernel process before starting a new one.
For me this fixes the issue describe by @t9md: https://github.com/nteract/hydrogen/issues/863#issuecomment-307076817
Unfortunately I can't reproduce #863 so I don't know for sure if this will fix the original issue.

#863 is still active.

@wowserx Just to make sure, have you tested with the latest master? v1.17.0 doesn't yet include this fix.

I feel silly, wasn't running atom in dev mode.
#863 is no longer active! It works fine.

Awesome thanks for checking! 🎉
I'll ship a patch release since this fixes a critical issue.

For me this fixes the issue describe by @t9md: #863 (comment)

I still can reproduce with latest master v1.17.1.
My steps to reproduce is

prepare sample code below.

let a = [1, 2, 3]
a.push(10)
a // %%
a.push(20)
a // %%
a.push(30)
a.map(e => e * e)
a // %%

execute restart-kernel-and-re-evaluate-bubbles via keymap so that I can execute multiple times with short gab between each execution.

I keymap is here,
'atom-text-editor':
  'cmd-h': 'hydrogen:restart-kernel-and-re-evaluate-bubbles'

If I execute ten times, I can see some instance where bubbles are not filled with value(checkmark which represent undefined).

I can reproduce the above, but it's not the same problem as #863, since the code is definitely running, just not consistently re-populating the bubbles.
In #863, the process was hanging indefinitely, but in the issue described above I've had it work where only some of the bubbles populate, but their results are correct:

I could also reproduce this problem by mashing a custom keymap which calls restart kernel and clear bubbles simultaneously, then quickly running the code.

@t9md want to try that my fork on #876? I think this could be related to #870

@BenRussert Sorry for late response(I didn't noticed this comment).
I tried with #876, and but no luck, I can still reproduce this the issue I described above.
How about you?
The step is very simple, "Invoking restart-and-re-evaluate via keymap multiple times for ijavascript kernel"

@t9md I see your issue now. This is a weird one.

So you could reproduce it right?

Looks like we run into #591 with IJavascript

@t9md Is this issue something that comes up in your normal workflow, or does it only happen when you rapidly run this command?

Yes, I can say it's easily happens in normal workflow.
I believe, you and all other people can easily reproduce this issue, by

invoke restart-kernel-and-re-evaluate-bubbles via keymap on ijavascript kernel.

This is NOT corner case of usage.
As my understanding, I didn't see this issue before hydrogen introduce rapid restart mechanism.
I prefer "slow but reliable" behavior than "quick but occasional un-reliable" behavior.
I want you and other maintainer try to reproduce this issue, and if it's really easy to reproduce as I explained, then my opinion is, we should revert to slow-but-reliable behavior worked in previous version.
I wonder if #591 is related(this is old issue), why this issue is not happen(I believe so) in previous slow restart then begin to appear from rapid restart?

👍 I'll take a look at it later this week.

we should revert to slow-but-reliable behavior worked in previous version

That sounds good to me.


Include matplotlib in Help > Dependencies

This will give users more helpful info about their installation and improve Spyder problem reports when users paste their installed dependencies list.
Package Versions

Spyder: 3.2.8

@ccordoba12 If you get to it first, I've been meaning to do this for a long time but can we sort our dependency list alphabetically, and make the order consistent between the dialog/manually copyed dep list and the Report Error Help Menu item/automatic error report? This has been bugging me for a while and makes tracking down issues due to specific package versions (or ruling them out) that much harder.

can we sort our dependency list alphabetically, and make the order consistent between the dialog/manually copyed dep list and the Report Error Help Menu item/automatic error report?

This is for another issue, and I don't have plans to solve it for now.

@ccordoba12 Okay, I'll try to get to it at some point—its been high in my queue due to how annoying it has been, but keeps getting bumped by more pressing matters.

@dalthviz, an easy one for you. Please add the dependency in plugins/ipythonconsole.py


As a user I want to be able to search by translation

For me this title sounds ambiguous. Maybe better to say: As a user I want to receive translations of a word


fix: Disable prefetching artworks on the Notification page

Description
Somehow, prefetching the artworkRoutes_ArtworkQuery query seems to cause this error on the Notification page. It looks like prefetching the query causes the removal of the data in the Relay store (maybe by overriding or garbage collecting the data 🤔).
Internal error after a few milliseconds:

Artwork is visible and disappears after a few milliseconds with this error:

@olerichter00 - did you find that this actually fixes things?

I thought it had fixed both issues from the description, but now I'm seeing the same error (just not caused by usePrefetchRoute again)...

@damassi, this PR does not disable all prefetching that is happening on the notification page.
I've opened a follow-up PR that disables prefetching on some other links on the page: https://github.com/artsy/force/pull/14822


Quiesce test failing for pre-squid

Possibly due to the new feature being backported to squid branch:
 === RUN   TestFSQuiesce
    fs_quiesce_reef_test.go:22:
        	Error Trace:	/go/src/github.com/ceph/go-ceph/cephfs/admin/fs_quiesce_reef_test.go:22
        	Error:      	Expected nil, but got: &admin.FSQuiesceInfo{Epoch:5, SetVersion:1, Sets:map[string]admin.QuiesceInfo{"ac47ac80":admin.QuiesceInfo{Version:1, AgeRef:0, State:admin.QuiesceState{Name:"TIMEDOUT", Age:0}, Timeout:0, Expiration:0, Members:map[string]admin.QuiesceInfoMember{"file:/volumes/_nogroup/quiesceMe/bf7b4f2b-e605-40f0-8103-4b7f692440ad":admin.QuiesceInfoMember{Excluded:false, State:admin.QuiesceState{Name:"QUIESCING", Age:0}}}}}}
        	Test:       	TestFSQuiesce
    fs_quiesce_reef_test.go:24:
        	Error Trace:	/go/src/github.com/ceph/go-ceph/cephfs/admin/fs_quiesce_reef_test.go:24
        	Error:      	Should be true
        	Test:       	TestFSQuiesce
--- FAIL: TestFSQuiesce (0.09s)
=== RUN   TestServerSentinel

https://github.com/ceph/go-ceph/actions/runs/8398382664/job/23003150402

cc: @manishym  @nixpanic  @anoopcs9

We all knew this was coming and that's exactly why I requested for an issue early on to track the changes required with the build tags for 2 variants of test files(fs_quiesce_test.go and fs_quiesce_reef_test.go).
Let's keep the issue open until squid release is out with the feature and corresponding CI job is enabled for go-ceph.
Till then we could have the following change in build tags:
index 5a1075c..73e28ff 100644
--- a/cephfs/admin/fs_quiesce_reef_test.go
+++ b/cephfs/admin/fs_quiesce_reef_test.go
@@ -1,4 +1,4 @@
-//go:build (nautilus || octopus || pacific || quincy || reef || squid || ceph_pre_squid) && ceph_preview
+//go:build (nautilus || octopus || pacific || quincy || reef) && ceph_preview

 package admin

diff --git a/cephfs/admin/fs_quiesce_test.go b/cephfs/admin/fs_quiesce_test.go
index db2d94d..4aa4b05 100644
--- a/cephfs/admin/fs_quiesce_test.go
+++ b/cephfs/admin/fs_quiesce_test.go
@@ -1,4 +1,4 @@
-//go:build !(nautilus || octopus || pacific || quincy || reef || squid || ceph_pre_squid) && ceph_preview
+//go:build !(nautilus || octopus || pacific || quincy || reef) && ceph_preview

 package admin

I would also suggest a change in name for fs_quiesce_reef_test.go as it is applicable for any version prior to squid(upcoming).

I would also suggest a change in name for fs_quiesce_reef_test.go as it is applicable for any version prior to squid(upcoming).

Created #990 to address the ambiguity in test file name.

I can confirm that the test TestFSQuiesce from fs_quiesce_test.go is passing with https://github.com/ceph/go-ceph/pull/1012. Thus we no longer require any build tag changes.


Add missing triple backticks

I'm using some markdown add-on for Eclipse, and it requires that there be a newline before the backticks in order to display properly. This appears to be a bug in the add-on, as it works on github and isn't referenced in the markdown documentation, but we might as well enforce it nonetheless.


How to use storage account connection string from Key Vault instead of appSettings?

[Enter feedback here]

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

ID: 61008c1e-a107-ff6a-a5e8-26cd0b42b443
Version Independent ID: b7a1b3c9-4165-8930-d309-da6420f26360
Content: Configure a connection string - Azure Storage
Content Source: articles/storage/common/storage-configure-connection-string.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

@abmis-mi Thanks for your question. We are checking on this and will respond to you soon.

@abmis-mi The connection string format can be found in this section of the article you linked. Please see, Use Azure Key Vault to manage your access keys, for links to how you can store your access key.
Hopefully this information helps to answer your question, please let me know if you need further assistance.


Clearer Documentation on using Filters from Client Side

I know that client side is not the focus of Hot Chocolate, and perhaps this is simple frustration at failure to find proper related documentation that I need. I started with Hot Chocolate and fell in love quickly. I'm using Code First + EF, have sorting, paging, filtering, selection all set up. I have an Angular front end and I've been able to get everything set up within Angular generic enough that the service will create and structure the queries and variables proper based on the request & type. Problem is that I don't know how to structure this filter variable properly and I'm going nuts not able to find the documentation. I see that Michael Staib, shows some where clause in his .NET Oxford video around 47:52, but other than showing me a general visual, it's not helping me do this via Variables. Banana Pop gives me this information...but, not any more. I've tried moving around quotes, braces, spaces, commas, blah, blah and have yet to get any further. It would simply be GREAT to have the proper structures expected by the WHERE variables, with multiple fields, documented so I can figure out what the heck I'm supposed to be doing! I don't know if this is proper place to or not, but Stack Overflow doesn't get enough attention yet for you and Google &  my search term choices have been beyond unsuccessful. Any assistance is greatly appreciated!

Hi @brianafinney
Looks like this causes quite some headache, sorry for that!
The variables in graphql are the same as the json representation of the graphql input type.
You can use IntelliSense to autocomplete the filters in your query.
query ExampleQuery {
   foo(where: { bar: "asd",  baz_gt: 4}) {
      bar
      baz
   }
}

You can then basically just copy and paste the values to your json variable:
query ExampleQuery($where: FooFilter) {
   foo(where: $where) {
      bar
      baz
   }
}

{
    "where": { "bar": "asd",  "baz_gt": 4}
}

regarding AND and OR:
All filters are by default concatenated with and. So when you have a filter like the one above, the criteria is bar AND baz_gt.  You do not have to write the AND in this case.
for both, AND and OR you do have to provide an array value though.
You have to use it like this:
query ExampleQuery($where: FooFilter) {
   foo(where: { OR: [{bar: "asd"},{ baz_gt: 4}]}) {
      bar
      baz
   }
}

{
    "where": { "OR": [{"bar": "asd"},{ "baz_gt": 4}]}
}

You should not write
query ExampleQuery {
   foo(where: { bar: "asd",  OR: {baz_gt: 4}) {
      bar
      baz
   }
}

as variables
{
    "where": { "bar": "asd",  "OR": {"baz_gt": 4}}
}

Hi Pascal (love your name, btw)
Thank you VERY much for such a thorough and informative response. It definitely tells me I'm in the right direction, but I must have something else going on that's just not letting it happen. If I do this with one field ..I'm fine. It's only when I add more than 1. I will receive one of two errors consistently..no matter what. One error: The $where variable has invalid structure I know never even makes it to the back end before the error is thrown. The other results in an "Execution Error" regardless of how I place it in, which seems to be valid. This request DOES get to the back end...but comes back with "Unexpected Execution Error". I have an EF back end, and literally have the easiest set up. Do you have any idea what this is? Have I set up something wrong/neglected some setup?
This one: [cid:ccce8b5f-6b04-4077-94a3-177b3d2a08e1] OR this one both bring back this error:
[cid:ec857411-1d68-44ab-a1a0-9e4876d7084c]
The error stack trace looks like this:
[cid:3ba261ed-8f81-4e76-9ec3-93a2bb9db54f]

From: PascalSenn<EMAIL_ADDRESS>Sent: Saturday, April 18, 2020 8:24 AM
To: ChilliCream/hotchocolate<EMAIL_ADDRESS>Cc: brianafinney<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ChilliCream/hotchocolate] Clearer Documentation on using Filters from Client Side (#1730)
Hi @brianafinneyhttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbrianafinney&data=02|01||e55448c4318542f94f8f08d7e3ac8ba8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637228202518114779&sdata=lZA%2FON5t0lRbQiP5rNZVvXtCDyPx9XwOGzXfAs7Jfqo%3D&reserved=0
Looks like this causes quite some headache, sorry for that!
The variables in graphql are the same as the json representation of the graphql input type.
You can use IntelliSense to autocomplete the filters in your query.
query ExampleQuery {
foo(where: { bar: "asd",  baz_gt: 4}) {
bar
baz
}
}
You can then basically just copy and paste the values to your json variable:
query ExampleQuery($where: FooFilter) {
foo(where: $where) {
bar
baz
}
}
{
"where": { "bar": "asd",  "baz_gt": 4}
}
regarding AND and OR:
All filters are by default concatenated with and. So when you have a filter like the one above, the criteria is bar AND baz_gt. You do not have to write the AND in this case.
for both, AND and OR you do have to provide an array value though.
You have to use it like this:
query ExampleQuery($where: FooFilter) {
foo(where: { OR: [{bar: "asd"},{ baz_gt: 4}]}) {
bar
baz
}
}
{
"where": { "OR": [{"bar": "asd"},{ "baz_gt": 4}]}
}
You should not write
query ExampleQuery {
foo(where: { bar: "asd",  OR: {baz_gt: 4}) {
bar
baz
}
}
as variables
{
"where": { "bar": "asd",  "OR": {"baz_gt": 4}}
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FChilliCream%2Fhotchocolate%2Fissues%2F1730%23issuecomment-615889179&data=02|01||e55448c4318542f94f8f08d7e3ac8ba8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637228202518119768&sdata=oO5GqQWu%2BmI%2FiyO16hONRLARmsNiwoC9rorH%2FqFPbrs%3D&reserved=0, or unsubscribehttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGZD6QLD57KVWFN73LGV67LRNHAZTANCNFSM4MK47BUQ&data=02|01||e55448c4318542f94f8f08d7e3ac8ba8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637228202518124758&sdata=do6HvPosTISGeemgn0TvTcVPiWdAZAgLmj1GKWFpvds%3D&reserved=0.

Hi Pascal (love your name, btw)
Thank you VERY much for such a thorough and informative response. It definitely tells me I'm in the right direction, but I must have something else going on that's just not letting it happen. If I do this with one field ..I'm fine. It's only when I add more than 1. I will receive one of two errors consistently..no matter what. One error: The $where variable has invalid structure I know never even makes it to the back end before the error is thrown. The other results in an "Execution Error" regardless of how I place it in, which seems to be valid. This request DOES get to the back end...but comes back with "Unexpected Execution Error". I have an EF back end, and literally have the easiest set up. Do you have any idea what this is? Have I set up something wrong/neglected some setup?
This one:

OR this one both bring back this error:

The error stack trace looks like this:

Thank you 🙂

One error: The $where variable has invalid structure I know never even makes it to the back end before the error is thrown

In this case the validation fails, this happens when the argument is not in the correct format

.but comes back with "Unexpected Execution Error"

Hm... there are two cases where this can happen. Either the visitor runs into an invalid state or the field you were requesting was not found on the type. Which both seem weird because validation should have already checked for this..
If you can provide a minimal repro of this issue, e.g. in a github repository, we can have a look at it.
Without code and schema it is really hard to tell what the issue is

Well, I've never done of these before, but I'll do my best. I am so thankful for your assistance with this. I'll respond back when I have a repro created.

Well, holy moly batman! Here's what I can tell you...I began to create the repro and when I was looking at the packages, noticed that the versions being offered was different that the one in my project, so I uploaded my project to 11.0.0 prerelease.127 and simple hit the play button again on my query and it came back as expected. My project had 11.0.0 prerelease.121, so must have been an issue there. So, I guess it's worked out. Your first response with all the information documenting how to build these queries is HUGE for me and so very, very appreciated!!! THANK YOU PASCAL!

Well, that is interesting...Glad that it worked out though 😄
You are most welcome Briana 👍
Just let us know if you have any more issues 🌶
As this is resolved I am gonna close this issue :)


Investigate slow Tabulator table data loading and Virtual DOM configuration

Tabulator seems to stall on loading over 100K rows even when adding 10K rows at the time.
Current table settings:
// table view settings
const toolbarHeight = 40; // table view toolbar height offset
const autoResize = true;
const autoColumns = true;
const enableClipboard = true; // enable clipboard copy and paste
const clipboardPasteAction = 'replace';
const movableColumns = true;
const movableRows = true;
const selectableRows =  true;
const reactiveData = false;
const renderVerticalBuffer = 300; // virtual view buffer height in px for redraw on scroll

Might need to try turning off redraw when adding more data to the table.
see docs: http://tabulator.info/docs/5.0/layout#virtual-dom

I added paging to the Tabular Data Viewer Observable JS test notebook and tried it with 200+K rows dataset:
https://observablehq.com/@randomfractals/data-table-viewer?dataUrl=https://raw.githubusercontent.com/vega/vega-datasets/master/data/flights-3m.csv
That data displays in a few seconds in a browser.
So, this issue must be related to our vscode webview context, Tabulator config in table view, and incremental data loading. Setting data page size to 100K rows loads them just fine but then table scrolling and sometimes vscode IDE freezes up. Current setup only works for 10K rows display for some reason.

Reviewing Tabulator reactive data docs: http://tabulator.info/docs/5.0/reactivity#reactive-data

Array Manipulation
Once a data array has been added to the data property it will be watched for changes using any of the standard row manipulation functions, push, pop, shift, unshift, and splice. Using any of these functions on the array will automatically trigger an update on the table

After trying some of those table data update options, I could not get Tabulator to incrementally add more data rows beyond the initial 100K data items added on initial load without major UX performance degradation.
Will add custom 100K rows paging UI in #60 with complete replace of data added to Tabulator table on each data page request, and explore swappable data grids for larger datasets with Perspective and/or RevoGrid.
Will open a ticket in Tabulator repo for this UI limitation scenario later. Closing this tickets for now.


Search pane UX

Added a "+" and "-" thing to the search panel header as a visual hint it can be expanded/folded.
The whole line is still clickable though.
See https://github.com/bnjbvr/kresus/issues/259.

Thanks! The +/- are slightly misaligned with the text, also I am not a big fan of a sign without any border or any color hint to the user.
Can you use a button with a bootstrap's glyphicon ( http://getbootstrap.com/components/#glyphicons ), instead, please? There's an example there: https://github.com/bnjbvr/kresus/blob/incoming/client/components/NewBankForm.js#L191-L195

I will !

Thanks for the update! There is a bad side effect that I don't understand: when I start typing stuff in the free text form field, let's say it type qwertyuiop, only the first chars are typed (qwe) and I lose focus in the search field. I don't understand how this is related to this PR, but it is though, as I don't have this behavior without your PR applied locally.
Also, can you please rebase onto incoming?

Thank you, it looks great!


Provide steps for a workaround when deleting larger scale data

Users have had bad experiences when using DETACH DELETE on larger scale data. We should provide steps for a workaround in the section of the docs that explains DELETE clause and mentions DETACH DELETE .
Context from a Slack conversation

This should be added after it's implemented -> https://github.com/memgraph/mage/pull/446


RTL Language Sliders Display Issues

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
4.0.10
Last working release (if known):
NA
Browser and Operating System:
All

Description of problem:
Sliders do not render correctly when language direction is rtl.

Javascript errors shown in the web inspector (if applicable):

Your Full Card Config

Additional information:
https://github.com/Nerwyn/android-tv-card/issues/134

Fixed in 4.1.0


Sometimes 'Unexpected response from YouTube'

Full StackTrace: https://controlc.com/fcc30d7e
This happens sometimes when i try to !play youtube-link
But the same command (with the same yt-link)  works after a while... sometimes...
And sometimes the Bot joins the VC, but doesnt play anything :/
However, the link from the StackTrace is: https://www.youtube.com/watch?v=XjOAA18z9uw
Version: bec3995
If you need more info, tell me!

I'm having the same issue here. YouTube playback either fail with "Unexpected response from YouTube" OR their end with reason "load_failed". I haven't changed my code and it always used to work.
I also noticed that lavaplayer cannot find anything on YouTube when searching for keywords (youtube:keyword). I wonder, do you experience this as well @BrainBaze ?
Links from SoundCloud seem to work fine.

ty!
Is there a new Version for Maven or do I have to download the git repo?

Use Devoxin's fork, this repo is not maintened currently: https://github.com/Devoxin/lavaplayer
implementation 'com.github.Devoxin:lavaplayer:1.3.59' on jitpack

You can use jitpack to download it directly from my github. Check this example on gradle.

Use Devoxin's fork, this repo is currently not maintened: https://github.com/Devoxin/lavaplayer
implementation 'com.github.Devoxin:lavaplayer:1.3.59' on jitpack

Or this, whatever suits you better. I personally like my own solution better to this specific issue more.

Use Devoxin's fork, this repo is currently not maintened: https://github.com/Devoxin/lavaplayer
implementation 'com.github.Devoxin:lavaplayer:1.3.59' on jitpack

This fixed the issue for me!

okay, i now use
<groupId>com.github.menmaa</groupId>
<artifactId>lavaplayer</artifactId>
<version>a4b8b48ed5</version>
My error mentioned above seems to be solved now!
Otherwise I will make a new Issue.
Thank you all for your incredible fast help!

Added some workaround for an issue raised causing "Something went wrong loading the track.".
You can use new commit hash 737770c2a7 or you can use master-SNAPSHOT to get latest branch changes.


how to generate user address with did doc

I have went through the scripts and found that there is no way to generate a new account user with
cli add keys myfoousr
and generate the did doc based on this address. Is that possible to do so?  what is the proper way to obtain the did doc
MIGUEL_DID="did:ixo:4XJLBfGtWSGKSz4BeRxdun"
MIGUEL_DID_FULL="{\"did\":\"did:ixo:4XJLBfGtWSGKSz4BeRxdun\",\"verifyKey\":\"2vMHhssdhrBCRFiq9vj7TxGYDybW4yYdrYh9JG56RaAt\",\"encryptionPublicKey\":\"6GBp8qYgjE3ducksUa9Ar26ganhDFcmYfbZE9ezFx5xS\",\"secret\":{\"seed\":\"38734eeb53b5d69177da1fa9a093f10d218b3e0f81087226be6ce0cdce478180\",\"signKey\":\"4oMozrMR6BXRN93MDk6UYoqBVBLiPn9RnZhR3wQd6tBh\",\"encryptionPrivateKey\":\"4oMozrMR6BXRN93MDk6UYoqBVBLiPn9RnZhR3wQd6tBh\"}}"

Hi @jjhesk, ixo blockchain does not use the Cosmos keybase. You can use an existing DID Doc (such as MIGUEL_DID_FULL) if you're just trying stuff out. In future versions, we will have ways to generate new DID Docs from the CLI.

To get a Cosmos SDK address from a DID Doc, there's a query that you can use:
ixocli q did get-address-from-pubkey <verify_key>


Some settings are no longer applicable

"Settings categories" section lists Browser Start pages and Enterprise mode site list, but these do NOT apply to Edge Chromium, just legacy Edge. [MMD switched to Edge Chromium].
Suggest add a note to this effect.

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

ID: c8e5e9bd-4de7-92eb-3eca-b0b5164c8374
Version Independent ID: 80b519bc-c4d6-abfc-ceff-f7698b9501b6
Content: Microsoft Managed Desktop and Windows 11 - Microsoft Managed Desktop
Content Source: microsoft-365/managed-desktop/intro/win11-overview.md
Service: m365-md
GitHub Login: @tiaraquan
Microsoft Alias: tiaraquan

Added a note to this page to address this issue. It is included in https://github.com/MicrosoftDocs/microsoft-365-docs-pr/pull/13130


Add P3 and Rec2020 support

Thanks for amazing tool. I love it so much and use to rgb → lch convert.
Now we start to work with P3 colors and found that tool is not very useful. We can send PR to improve P3 support, but want to got a approve from maintainer first.
My current plans:

I see only one border on canvases right now. It seems like it is a border for sRGB colors. We want to add multiple borders for sRGB limit, P3 limit, Rec2020 limit and eye visibility limit.
In additional to making RGB hex field red, add a note that color is out of sRGB or is out of P3 color space.
Optionally we can hide Rec2020 limit and show it only by hot key (since we do not have enough Rec2020 screens right now).

I think it will be very useful changes for the tool because we have a lot P3 displays right now (most of OLED screens, all modern Apple screens), Safari got a full support for P3 colors and other browsers and CSSWG is planning to add this support too.

Sounds like a good addition 👍
I'd make wider gamuts optional they are still a pretty new thing.
If your PR is not ready yet I'd ask you to wait a couple of days. Currently I'm working on adding OKLCH color space and have a lot of stuff broken inside. I plan to release the new version with lots of inner changes this weekend

Cool. I will wait for release before creating a task for PR.

It looks amazing 🤩
When you plan to deploy it? I want to promote this feature in Twitter.

Glad you like it. Hope to release this thursday or friday. There is still a list of improvements to make 🥴

The new version is just deployed 😉
So, closing this issue.


Add Emilien for code and maintenance

Add @emilienbev as contributor

@all-contributors add @emilienbev for code and maintenance

@all-contributors add @emilienbev for code and maintenance


[EventHubs] Add notes on AAD Authentication

For users who would rather use AAD to connect to their Event Hubs, add a
small note that this library supports using Azure Identity to do so. In
addition, make a note about needing to assign specific roles to the AAD
principal used, and provide a link to the service's documentation on AAD
so users can learn more about what role they may want to use and how to
assign it to a principal.

Noticed and appreciated that the Storage Blobs has a small section that talks about AAD authentication and includes links that talk about assigning permissions to a principal, figured I'd bring it over here as well and be a little more prescriptive on the names of roles that you might want to assign.
I prefer to use AAD personally because it involves less juggling around keeping connection strings secure, but out of the box things don't work unless you actually assign some roles, so I figured I'd call it out here.
I plan to make similar changes in the other languages.

Do you mind if I steal your work and incorporate it into the README revisions that I've currently got in flight?

Not at all!

Happy to make the content changes here, Jesse, if that makes it easier for you to incorporate. If you'd rather just take this is and merge and wordsmith with your changes and then have me review that, that works for me to.
Let me know what's easier on your end.

No need to trouble you with the revisions if I'm going to pull them in.   You've done enough with just the conceptualization; the base content to work from is gravy!   Thanks very much for your flexibility.   It is appreciated.

As you were kind enough to agree to, I pulled these changes (with some word smithing) into #9296

Closing as this has been incorporated into #9296.


feat(context): allow surrogate to maintain context on unhooked methods

Specifying a method or list of methods allows Surrogate to maintain object context on the specified methods when they are not called through the object.

:tada: This PR is included in version 1.8.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Add NetworkKind

Add a new type NetworkKind the describes the kind of network we are on, ether mainnet or one of the test nets (testnet, regtest, signet).
Use it in Address, PrivateKey, and bip32.

This looks great to me. Am a little worried about the bip32 case where theoretically there could be more prefixes added (and no doubt we'll get the ypub/zpub people whining that we're making it even harder for them to implement their weird layer violations). But I'm doubtful. The model we've moved to, in my view, is that keys are "just keys" and networks should be specified elsewhere, e.g. at the descriptor layer.

Rebased, no other changes.

This is missing the API break label.


Long task with synchronous pieces does not time out

Describe the bug
Basically I've got a synchronous function that I want to test is reasonably fast with a large amount of data. I understand the issue of not being able to interrupt the process for the synchronous task, and saw for example another issue mentioning the problem with an infinite loop—but this function does eventually resolve. If I've set a timeout for 150ms and it takes 5 seconds to resolve, I would expect the test to fail as timed out, but it doesn't, no matter how long it takes.
I suppose this may be "behaving as expected" as timeout is only intended to interrupt asynchronous tasks if it can and does nothing if it can't interrupt, but it's definitely unintuitive to me that a test with a 150ms timeout that resolves in 5 seconds is considered to have passed.
For my particular use case I did a const start = Date.now(); … expect(Date.now() - start).toBeLessThan(150); and I'm sure that will probably be the response here, but I think it's unintuitive that the distinction between synchronous and asynchronous code (even synchronous code within a promise) will change whether the same behavior is considered to have timed out.
Reproduction
Times out as I'd expect, because (as far as I understand, and I admit I'm a little fuzzy) setTimeout does not monopolize ticks and allows the test process to intervene:
it('times out', async () => {
  await new Promise((resolve) => {
    setTimeout(resolve, 5_000);
  });
}, 150);

Does not time out, and does not fail once completed:
it('does not time out', async () => {
  const start = Date.now();
  await new Promise((resolve) => {
    while (Date.now() - start < 5_000) {}
    resolve();
  });
}, 150);

Even this, which occurred to me while writing this issue, does not result in a timeout:
it('does not time out even with a promise after completion allowing the test runner to intervene', async () => {
  const start = Date.now();
  while (Date.now() - start < 5_000) {}
  await new Promise((resolve) => {
    setImmediate(resolve); // setTimeout(resolve, 0 or even 10) has no effect either
  });
}, 150);

System Info
System:
    OS: macOS 13.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 85.13 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.10.0 - ~/.nodenv/versions/18.10.0/bin/node
    npm: 8.19.2 - ~/.nodenv/versions/18.10.0/bin/npm
  Browsers:
    Firefox: 109.0.1
    Safari: 16.2
  npmPackages:
    @vitest/coverage-c8: ^0.24.5 => 0.24.5
    vite: ^3.2.4 => 3.2.4
    vitest: ^0.24.5 => 0.24.5

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

If it helps, here's a repo that I just threw together. Vite/vitest versions are absolute latest https://github.com/bensaufley/vitest-timeout-example

Found that putting the synchronous task inside the promise, with setImmediate, produces a timeout:
  it("times out", async () => {
    const start = Date.now();
    await new Promise<void>((resolve) => {
      while (Date.now() - start < 5_000) {}
      setImmediate(resolve);
    });
  }, 150);

I'm 100% certain there are system-level reasons for why there are distinctions here, but from a usage standpoint, the distinction between longRunningSync(); promise(setImmediate()) and promise(longRunningSync(); setImmediate()) for the purpose of testing and determining whether to time out seems … unexpected?

^ just discovered that this last strategy does not work for my actual use case, which … actually makes no sense, because it's the same thing except instead of the while loop it's calling a function with a for loop inside. Completes in ~3 seconds, and shows it:

Hi there! Is there any update on this issue? I came across a similar issue: an infinite loop inside a synchronous function, and the testTimeout didn't kill it.

This is just how JavaScript engine works, I don't what else to update here. while loop doesn't empty the event queue so setTimeout cannot be run to stop the test.

The originally reported issue is not that the task isn't canceled (which I agree is just the nature of JS); it's that when the task completes, it isn't marked as timed out, despite taking much longer than the specified time.

Test time is not checked after the test has finished

And this is the core of the issue. I explained all of this above:

I suppose this may be "behaving as expected" as timeout is only intended to interrupt asynchronous tasks if it can and does nothing if it can't interrupt, but it's definitely unintuitive to me that a test with a 150ms timeout that resolves in 5 seconds is considered to have passed.

If we're considering timeout to only mean "canceled before execution could finish" then timeout may not be the best way to frame that.

To JS it did lot took 5 seconds.

This is just incorrect. JS knows what time it took. Vite even reports that time in the output. That's where the heart of this issue is.

This is just how JavaScript engine works, I don't what else to update here. while loop doesn't empty the event queue so setTimeout cannot be run to stop the test.

Then what about the assertion itself? I used except.objectContaing to validate that a given object containing some variables and arrays , but it went into an infinite loop, although there is a valid returned value from except.objectContaing.
The code was some thing like this:
// This is just a sample script. Paste your real code (javascript or HTML) here.
it('title', () => {
    const obj = someFunction();
    except(object).toEqual(
        except.objectContaining({
            sample1: [],
            sample2: [],
            sample3: {
                foo: undefined,
                bar: undefined,
                title: undefined,
            },
        })
    });
});

Note: I used toBe and toEqual but same issue.

That doesn't seem related to this discussion.


Creating helm charts for schema registry deployment

This PR creates helm charts for deployment of schema registry on a Kubernetes cluster.

@SrishT Also, please use standard Pravega guidelines for naming and describing this PR: https://github.com/pravega/pravega/wiki/Contributing#creating-a-pull-request.
The description is missing details, and the name does not have the issue number on it.

Closing this PR since the branch is in a bad shape.


Allow the close parentheses of a class parameter list to be on next line

I would like to see the following:
class Foo(
  bar: String,
  baz: String
)

Right now scalariform creates:
class Foo(
  bar: String,
  baz: String)

danglingCloseParenthesis=Prevent does this.


When connecting to https, connection is lost every 5-6 seconds or so, but http works fine

This was reported by a Transloadit customer in our support tool, and I've asked them to provide more information in this ticket

@kvz any update on this? If it's iOS9 could be a easy switch.

Hey @MMasterson!
I just reopened that ticket with this response:
Hi Marc,

Might you have more information regarding this?
Our new iOS developer just mentioned in https://github.com/transloadit/ios-sdk/issues/13#issuecomment-231160057 that:

"If it's iOS9 could be a easy switch."

Also, we have upgraded our HTTPS stack recently which could also have improved the situation https://transloadit.com/blog/2016/07/ssl-upgraded/

Looking forward to hear from you!

Kind regards,

Just got word that

We ended up writing our own utility for iOS and no longer utilize Transloadit. Thanks for the followup!

So I'll close this issue until someone reports this again


feat(nodes): WIP restricted invocation context

What type of PR is this? (check all applicable)

[x] Refactor
[x] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Description
Note: this PR is based on the #4758 branch
feat(nodes): WIP restricted invocation context
This is a first draft of a restricted InvocationContext, which is provided to all nodes.
Motivation
The existingInvocationContext class has two issues.
1. Too powerful
It's entirely possible that a node could wreck an installation by accidentally calling a destructive method or something like that.
Also, the application relies on nodes to be well-behaved and never do certain things (like delete images), so we should just enforce this explicitly.
It's probably not possible to prevent a node from doing something naughty if it wants to, but we can reduce the chance of unintentional footgunning to almost zero by providing a restricted API.
2. Too low-level/complicated
Many of the service methods are low-level and present an awkward API.
Consider the method to save an image:
image_dto = context.services.images.create(
    image=image,
    image_origin=ResourceOrigin.INTERNAL,
    image_category=ImageCategory.GENERAL,
    node_id=self.id,
    session_id=context.graph_execution_state_id,
    is_intermediate=self.is_intermediate,
    metadata=self.metadata.model_dump() if self.metadata else Non
    workflow=self.workflow,
)

There's a crapload of fluff here that nodes shouldn't need to worry about. It's mostly boilerplate.
Draft API
The full-fat context is now called AppInvocationContext, and the restricted one is InvocationContext. These names can be changed, I just did this so I didn't have to change a bazillion imports in all nodes while testing.
See base_invocation.py for the full implementation - it's a simple wrapper.
Example improved method:
The above create() method is reduced to this:
image_name = context.save_image(image)

The other methods don't have as drastic an improvement but they are all improved.
Discussion points
In addition to the design and implementation, there are a few points that probably warrant discussion.

Core vs community nodes

This restricted API is currently set up to apply to all nodes - core, InvokeAI-managed nodes and future community nodes.
Do we want to maybe let core nodes get access to the original, full-fat context, and only give the restricted context to community nodes?

Power creep

So far, I've implemented most of what our core nodes use. What if community nodes want more access - say, to star images? How do we decide what makes the cut?

Exposing extra stuff in the context

There are some constants/enums/things that we want to provide to nodes. We can do that via the context, as opposed to via imports.
Example:
Images have categories, which are selected via the ImageCategory enum - see the create() method above for how it works in the current release.
In this PR, I've exposed that enum as context.categories and made this an optional arg:
context.save_image(image, category=context.categories.GENERAL)

This feels neat and tidy but I'm unsure if it's a good idea. Maybe the context should be methods and context attributes only?
Related Tickets & Documents

Related Issue #
Closes #4887

QA Instructions, Screenshots, Recordings

You can test this now, using a simple txt2img workflow with sd1.5 (other nodes are not migrated). You'll first need to run pip install -e ".[dev,test]" to get pydantic v2 installed.
simple t2i.json
Added/updated tests?

[ ] Yes
[ ] No : please replace this line with details on why tests
have not been included

[optional] Are there any post deployment tasks we need to perform?

Has this been updated with pydantic changes?

Overall, I love this initiative! Thanks for putting together a draft.
It's a little hard to review right now because the diff is polluted with pydantic changes. I'll just leave a few high-level comments for now.

Do we want to maybe let core nodes get access to the original, full-fat context, and only give the restricted context to community nodes?

In my opinion, we should aim to have all nodes (core and community) interface with the same API. It's nice to have a clear boundary between nodes and the app backend. I think there are a few downsides to allowing special cases for core nodes:

If we allow it once, there will be temptation to do it again and again.
It adds new considerations for any general node handling (e.g. adds complexity to node versioning, automatic node migration, etc.)
It will become harder to write good node tests. If the node API is fixed, we can easily write a mock context implementation that is shared across all tests.

Put another way, before adding a method to the context we should ask ourselves: "Are we willing to support this method for both core and community nodes indefinitely?"
Of course, my mind could be changed if there was a compelling use case.

As somebody interested in color spaces and wider gamuts and how those could be used in the future, I'd like to see load_image and save_image methods become load_PIL_image and save_PIL_image methods. This would allow us to support other image formats and APIs going forward that utilized 16 bits/LAB/etc.

Superseded by #5491


Best way to test the operation

After I installed this integration I would like to know if it works properly. For that I set the longitude and latitude at a location in Australia where, according to https://www.lightningmaps.org, it is thunderstorm with a range of 500 kilometers.
Unfortunately, the counter remains at zero. Should I be more patient or is there a better way to test?

More patient was the solution, it works fine

More patient was the solution, it works fine


The method setElevation(int) is undefined for the type View

I am getting this error when I imported the new Java file
The method setElevation(int) is undefined for the type View
Device OS : Android

Are you using an SDK of API level lower than 21? Please update your local Android SDK in that case.

Great, it worked when I changed target to 21 (target=android-21), but it affects another plugin (NetworkManager.java) , It would be really helpful if you are able to help me on this, both plugins are working with the target 19, If I swap the target either one of them not working.

You can leave your target to anything you want, as long as you're compiling against at least 21.
Are you referring to this plugin you have a problem with?

Yes the same Network Manager plugin. I don't have knowledge in Java, After
setting the target 21, Toast Plugin is working fine , but the network
manager plugin throws error, I guess there might be some library files
needs to be loaded, I could not resolve it, that's what I requested for
your help, Thanks a lot for your time
Thanks and Regards
Udhayakumar Manoharan
Cognizant Technology Solutions.Mobile : +1<PHONE_NUMBER>
On Mon, May 23, 2016 at 12:15 AM, Eddy Verbruggen<EMAIL_ADDRESS>wrote:

You can leave your target to anything you want, as long as you're
compiling against at least 21.
Are you referring to this plugin
https://github.com/apache/cordova-plugin-network-information/blob/master/src/android/NetworkManager.java
you have a problem with?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/EddyVerbruggen/Toast-PhoneGap-Plugin/issues/87#issuecomment-220903816

Just to be sure: when you say 'target', did you change the SDK in Android Studio, or did you change the target in AndroidManifest.xml? I was referring to the first.

I changed the target in project.properties file target=android-21, I am not
using android studio, I am using eclipse ADT. Check the below screenshot,
Android XML File

but in project build target , could not see API Level 21
[image: Inline image 1]
[image: Inline image 2]
Udhay
Thanks and Regards
Udhayakumar Manoharan
Cognizant Technology Solutions.Mobile : +1<PHONE_NUMBER>
On Mon, May 23, 2016 at 11:59 AM, Eddy Verbruggen<EMAIL_ADDRESS>wrote:

Just to be sure: when you say 'target', did you change the SDK in Android
Studio, or did you change the target in AndroidManifest.xml? I was
referring to the first.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/EddyVerbruggen/Toast-PhoneGap-Plugin/issues/87#issuecomment-221058525


Support for ash_postgres v2.0.10

As mentioned in #8 I noticed that ash_postgres v2.0.10 will break the tests and possibly other apps using this extension with the following error:
  6) test AshUUID.PrefixedV4 testing pineapples (AshUUIDTest)
     test/ash_uuid_test.exs:176
     ** (Ash.Error.Unknown) Unknown Error

     * ** (Postgrex.Error) ERROR 22P02 (invalid_text_representation) invalid input syntax for type uuid: "pineapple-smoothie_02wsgCff7yup2N8ZhJUxLc". If you are trying to query a JSON field, the parameter may need to be interpolated. Instead of

         p.json["field"] != "value"

     do

         p.json["field"] != ^"value"

         query: SELECT p0."id", p0."secondary_id", p0."inserted_at", p0."pineapple_smoothie_id" FROM "pineapples" AS p0 WHERE (p0."pineapple_smoothie_id"::uuid IN ('pineapple-smoothie_02wsgCff7yup2N8ZhJUxLc'))
         at pineapples

This PR is just here to reproduce the errors in CI with updated dependencies.

@zachdaniel Sorry for bothering you, but I'm trying to fix this but it might actually be a bug in ash_postgres.
I used git bisect and it looks like this issue was introduced in https://github.com/ash-project/ash_postgres/commit/526020e26cc0917d8f94c4929ffa2dfb1bbeb348. I suspect the latest changes to AshPostgres.SqlImplementation.determine_types/2 might have introduced this bug.
It only fails when loading a relationship (like Ash.load!(lime_smoothie, :limes)) and I'm currenty dbging the return value of the function:
diff --git a/lib/sql_implementation.ex b/lib/sql_implementation.ex
index d037d2d..7310431 100644
--- a/lib/sql_implementation.ex
+++ b/lib/sql_implementation.ex
@@ -293,6 +293,7 @@ defmodule AshPostgres.SqlImplementation do
           end
         end)
     end
+    |> dbg
   end

   defp closest_fitting_type(types, values) do

Here the output when running the a single test and the result of determine_types/2:

ash_postgres v2.0.9
$ mix test test/ash_uuid_test.exs:75
Running ExUnit with seed: 265972, max_cases: 16
Excluding tags: [:test]
Including tags: [location: {"test/ash_uuid_test.exs", 75}]

[(ash_postgres 2.0.10) lib/sql_implementation.ex:268: AshPostgres.SqlImplementation.determine_types/2]
cond do
  :erlang.function_exported(mod, :types, 0) -> mod.types()
  :erlang.function_exported(mod, :args, 0) -> mod.args()
  true -> [:any]
end #=> [[:any, {:array, :same}]]
|> Enum.concat(Map.keys(Ash.Query.Operator.operator_overloads(name) || %{})) #=> [[:any, {:array, :same}]]
|> Enum.map(fn types ->
  case types do
    :same ->
      types =
        for _ <- values do
          :same
        end

      closest_fitting_type(types, values)

    :any ->
      for _ <- values do
        :any
      end

    types ->
      closest_fitting_type(types, values)
  end
end) #=> [
  [
    {:parameterized, AshUUID.UUID.EctoType,
     [
       migration_default?: false,
       prefix: "lime-smoothie",
       version: 4,
       encoded?: true,
       prefixed?: false,
       strict?: true
     ]},
    {:in,
     {:parameterized, AshUUID.UUID.EctoType,
      [
        migration_default?: false,
        prefix: "lime-smoothie",
        version: 4,
        encoded?: true,
        prefixed?: false,
        strict?: true
      ]}}
  ]
]
|> Enum.filter(fn types -> Enum.all?(types, &(vagueness(&1) == 0)) end) #=> [
  [
    {:parameterized, AshUUID.UUID.EctoType,
     [
       migration_default?: false,
       prefix: "lime-smoothie",
       version: 4,
       encoded?: true,
       prefixed?: false,
       strict?: true
     ]},
    {:in,
     {:parameterized, AshUUID.UUID.EctoType,
      [
        migration_default?: false,
        prefix: "lime-smoothie",
        version: 4,
        encoded?: true,
        prefixed?: false,
        strict?: true
      ]}}
  ]
]
|> case do
  [type] ->
    if type == :any || type == {:in, :any} do
      nil
    else
      type
    end

  _ ->
    Enum.map(values, fn _ -> nil end)
end #=> [
  {:parameterized, AshUUID.UUID.EctoType,
   [
     migration_default?: false,
     prefix: "lime-smoothie",
     version: 4,
     encoded?: true,
     prefixed?: false,
     strict?: true
   ]},
  {:in,
   {:parameterized, AshUUID.UUID.EctoType,
    [
      migration_default?: false,
      prefix: "lime-smoothie",
      version: 4,
      encoded?: true,
      prefixed?: false,
      strict?: true
    ]}}
]
.
Finished in 0.4 seconds (0.00s async, 0.4s sync)
14 tests, 0 failures, 13 excluded

[
  {:parameterized, AshUUID.UUID.EctoType,
   [
     migration_default?: false,
     prefix: "lime-smoothie",
     version: 4,
     encoded?: true,
     prefixed?: false,
     strict?: true
   ]},
  {:in,
   {:parameterized, AshUUID.UUID.EctoType,
    [
      migration_default?: false,
      prefix: "lime-smoothie",
      version: 4,
      encoded?: true,
      prefixed?: false,
      strict?: true
    ]}}
]

ash_postgres v2.0.10
mix test test/ash_uuid_test.exs:75
Running ExUnit with seed: 651359, max_cases: 16
Excluding tags: [:test]
Including tags: [location: {"test/ash_uuid_test.exs", 75}]

[(ash_postgres 2.0.9) lib/sql_implementation.ex:296: AshPostgres.SqlImplementation.determine_types/2]
cond do
  :erlang.function_exported(mod, :types, 0) -> mod.types()
  :erlang.function_exported(mod, :args, 0) -> mod.args()
  true -> [:any]
end #=> [[:any, {:array, :same}]]
|> then(fn types ->
  Enum.concat(Map.keys(Ash.Query.Operator.operator_overloads(name) || %{}), types)
end) #=> [[:any, {:array, :same}]]
|> Enum.flat_map(fn types ->
  case types do
    :same ->
      types =
        for _ <- values do
          :same
        end

      [closest_fitting_type(types, values)]

    :any ->
      []

    types ->
      [types]
  end
end) #=> [[:any, {:array, :same}]]
|> Enum.filter(fn types -> Enum.all?(types, &(vagueness(&1) == 0)) end) #=> []
|> case do
  [types] ->
    types

  types ->
    Enum.find_value(types, Enum.map(values, fn _ -> nil end), fn types ->
      if length(types) == length(values) do
        types
        |> Enum.zip(values)
        |> Enum.reduce_while([], fn {type, value}, vals ->
          type = Ash.Type.get_type(type)

          if Ash.Type.ash_type?(type) do
            {type, constraints} =
              case type do
                {type, constraints} -> {type, constraints}
                type -> {type, []}
              end

            case value do
              %Ash.Query.Function.Type{arguments: [_, ^type | _]} ->
                {:cont, vals ++ [:any]}

              %Ash.Query.Ref{attribute: %{type: ^type}} ->
                {:cont, vals ++ [:any]}

              _ ->
                if Ash.Type.matches_type?(type, value, constraints) do
                  {:cont, vals ++ [parameterized_type(type, constraints)]}
                else
                  {:halt, nil}
                end
            end
          else
            {:halt, nil}
          end
        end)
      end
    end)
end #=> [nil, nil]

  1) test AshUUID.PrefixedV4 testing limes (AshUUIDTest)
     test/ash_uuid_test.exs:75
     ** (Ash.Error.Unknown) Unknown Error

     * ** (Postgrex.Error) ERROR 22P02 (invalid_text_representation) invalid input syntax for type uuid: "5AbK9g2dZBR6DMhp7zg7vF". If you are trying to query a JSON field, the parameter may need to be interpolated. Instead of

         p.json["field"] != "value"

     do

         p.json["field"] != ^"value"

         query: SELECT l0."id", l0."inserted_at", l0."lime_smoothie_id" FROM "limes" AS l0 WHERE (l0."lime_smoothie_id"::uuid IN ('5AbK9g2dZBR6DMhp7zg7vF'))
         at limes
       (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
       (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:952: Ecto.Adapters.SQL.execute/6
       (ecto 3.11.2) lib/ecto/repo/queryable.ex:232: Ecto.Repo.Queryable.execute/4
       (ecto 3.11.2) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
       (ash_postgres 2.0.10) lib/data_layer.ex:758: anonymous fn/3 in AshPostgres.DataLayer.run_query/2
       (ash_postgres 2.0.10) lib/data_layer.ex:756: AshPostgres.DataLayer.run_query/2
       (ash 3.0.15) lib/ash/actions/read/read.ex:2423: Ash.Actions.Read.run_query/4
       (ash 3.0.15) lib/ash/actions/read/read.ex:447: anonymous fn/5 in Ash.Actions.Read.do_read/4
       (ash 3.0.15) lib/ash/actions/read/read.ex:777: Ash.Actions.Read.maybe_in_transaction/3
       (ash 3.0.15) lib/ash/actions/read/read.ex:248: Ash.Actions.Read.do_run/3
       (ash 3.0.15) lib/ash/actions/read/read.ex:66: anonymous fn/3 in Ash.Actions.Read.run/3
       (ash 3.0.15) lib/ash/actions/read/read.ex:65: Ash.Actions.Read.run/3
       (ash 3.0.15) lib/ash/actions/read/relationships.ex:496: anonymous fn/3 in Ash.Actions.Read.Relationships.do_fetch_related_records/3
       (elixir 1.17.0) lib/enum.ex:1711: anonymous fn/3 in Enum.map/2
       (elixir 1.17.0) lib/enum.ex:4423: anonymous fn/3 in Enum.map/2
       (elixir 1.17.0) lib/stream.ex:1879: anonymous fn/3 in Enumerable.Stream.reduce/3
       (elixir 1.17.0) lib/enum.ex:4858: Enumerable.List.reduce/3
       (elixir 1.17.0) lib/stream.ex:1891: Enumerable.Stream.do_each/4
       (elixir 1.17.0) lib/enum.ex:4423: Enum.map/2
       (ash 3.0.15) lib/ash/actions/read/relationships.ex:43: Ash.Actions.Read.Relationships.fetch_related_records/2
     stacktrace:
       (elixir 1.17.0) lib/process.ex:864: Process.info/2
       (ash 3.0.15) lib/ash/error/unknown.ex:3: Ash.Error.Unknown."exception (overridable 2)"/1
       (ash 3.0.15) /Users/hw/Projects/ash_uuid/deps/splode/lib/splode.ex:211: Ash.Error.to_class/2
       (ash 3.0.15) lib/ash/error/error.ex:66: Ash.Error.to_error_class/2
       (ash 3.0.15) lib/ash/actions/read/read.ex:319: anonymous fn/2 in Ash.Actions.Read.do_run/3
       (ash 3.0.15) lib/ash/actions/read/read.ex:258: Ash.Actions.Read.do_run/3
       (ash 3.0.15) lib/ash/actions/read/read.ex:66: anonymous fn/3 in Ash.Actions.Read.run/3
       (ash 3.0.15) lib/ash/actions/read/read.ex:65: Ash.Actions.Read.run/3
       (ash 3.0.15) lib/ash/actions/read/relationships.ex:496: anonymous fn/3 in Ash.Actions.Read.Relationships.do_fetch_related_records/3
       (elixir 1.17.0) lib/enum.ex:1711: anonymous fn/3 in Enum.map/2
       (elixir 1.17.0) lib/enum.ex:4423: anonymous fn/3 in Enum.map/2
       (elixir 1.17.0) lib/stream.ex:1879: anonymous fn/3 in Enumerable.Stream.reduce/3
       (elixir 1.17.0) lib/enum.ex:4858: Enumerable.List.reduce/3
       (elixir 1.17.0) lib/stream.ex:1891: Enumerable.Stream.do_each/4
       (elixir 1.17.0) lib/enum.ex:4423: Enum.map/2
       (ash 3.0.15) lib/ash/actions/read/relationships.ex:43: Ash.Actions.Read.Relationships.fetch_related_records/2
       (ash 3.0.15) lib/ash/actions/read/relationships.ex:24: Ash.Actions.Read.Relationships.load/3
       (ash 3.0.15) lib/ash/actions/read/read.ex:270: Ash.Actions.Read.do_run/3
       (ash 3.0.15) lib/ash/actions/read/read.ex:66: anonymous fn/3 in Ash.Actions.Read.run/3
       (ash 3.0.15) lib/ash/actions/read/read.ex:65: Ash.Actions.Read.run/3

Finished in 0.3 seconds (0.00s async, 0.3s sync)
14 tests, 1 failure, 13 excluded

[nil, nil]

It looks like you were maybe right with your comment? 😆 When I remove the vagueness-filter, the function returns [:any, {:array, :same}] which results in another error:
  1) test AshUUID.PrefixedV4 testing limes (AshUUIDTest)
     test/ash_uuid_test.exs:75
     ** (Ash.Error.Unknown) Unknown Error

     * ** (UndefinedFunctionError) function :same.cast/1 is undefined (module :same is not available)
         at limes
       :same.cast("4yWxSasWegNNwmFy4dGH21")
       (ecto 3.11.2) lib/ecto/type.ex:1339: Ecto.Type.array/4
       (elixir 1.17.0) lib/enum.ex:2531: Enum."-reduce/3-lists^foldl/2-0-"/3
       (elixir 1.17.0) lib/enum.ex:1829: Enum."-map_reduce/3-lists^mapfoldl/2-0-"/3
       (elixir 1.17.0) lib/enum.ex:2531: Enum."-reduce/3-lists^foldl/2-0-"/3
       (ecto 3.11.2) lib/ecto/repo/queryable.ex:214: Ecto.Repo.Queryable.execute/4
       (ecto 3.11.2) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
       (ash_postgres 2.0.10) lib/data_layer.ex:758: anonymous fn/3 in AshPostgres.DataLayer.run_query/2
       (ash_postgres 2.0.10) lib/data_layer.ex:756: AshPostgres.DataLayer.run_query/2

Any help would be appreciated! I can also report an issue in ash_postgres if you think this belongs there.

Actually, if I change the following line, the tests in ash_uuid pass!
diff --git a/lib/sql_implementation.ex b/lib/sql_implementation.ex
index b3242b6..08558fa 100644
--- a/lib/sql_implementation.ex
+++ b/lib/sql_implementation.ex
@@ -248,7 +248,7 @@ defmodule AshPostgres.SqlImplementation do
           []

         types ->
-          [types]
+          [closest_fitting_type(types, values)]
       end
     end)
     # this doesn't seem right to me

Hi @hwuethrich
I'll try to fix this tomorrow (Italy work time).
I think the issue is that AshUUID.UUID should implement the new "load" callback of the Ash.Type behaviour.
Thank you for notice this bug, opening the PR and your contribution!

This is definitely a bug in ash_postgres, I will fix. There should be no changes required on your end.

I've just pushed a new version of ash_postgres that should resolve these issues.

Apologies for the breaking change 🙇

@zachdaniel No worries and thanks for the quick fix!
@moissela Should I close this PR or would you like to merge my changes anyway? Maybe adding a dependency constraint for ash_postgres > 2.0.10?

@moissela I updated the dependencies to require ash_postgres 2.0.11 or later and the tests are now passing.
Not sure if the Ash.Type.load/4 is required. Ash.Type.UUID doesn't implement it.

Thanks @hwuethrich and @zachdaniel, I'm merging into main this through #11 shortly.
I'm releasing to hex today.

Released!


New release

Hi @wdm0006, I am handing over the management of the repository.
The repository is prepared for a new release, which is long due since the last published release doesn't work so well under Pandas 1.0.0 (the master branch works fine). I hope you will find time to manage the repository.

Hey @janmotl. Thanks for all the work so far. I can take a look at a release (and maybe setting up an action to handle releases in the future), I've also opened an issue to solicit maintainers as I really don't have the time to keep up with this very closely these days.

Ok, after some minor turmoil I've moved all the CI tasks to github actions, so that others can more easily modify or add to them.

The test suite will run in 4 versions of python on all commits to master and PRs.
The docs will update on any push to master (we could modify this to only happen on release, I could go either way).
Build and publication to PyPI will happen anytime a release is created via the releases section on github, so it's now pretty easy to do also.

With that, the docs are hosted and up to date, and v2.2.2 is out here:
https://pypi.org/project/category-encoders/


Optional .spec.ingressClassName

Proposed changes
Introdcues support for .spec.ingressClassName field in helm chart. Closes #139
Checklist

[x] Lint and unit tests pass locally with my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added documentation to describe my feature.
[x] I have squashed my commits into logic units.
[x] I have described the changes in the commit messages.

Other information

Merged, thanks for your contribution!


routing: fix race condition when resuming payments

Found while running the integration tests with -race. Reuse of err variable when resuming payments in goroutines.
==================
WARNING: DATA RACE
Write at 0x00c000a680f0 by goroutine 147:
  github.com/lightningnetwork/lnd/routing.(*ChannelRouter).Start.func1()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/routing/router.go:536 +0x251

Previous write at 0x00c000a680f0 by goroutine 143:
  github.com/lightningnetwork/lnd/routing.(*ChannelRouter).Start.func1()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/routing/router.go:536 +0x251

Goroutine 147 (running) created at:
  github.com/lightningnetwork/lnd/routing.(*ChannelRouter).Start()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/routing/router.go:521 +0x42c
  github.com/lightningnetwork/lnd.(*server).Start.func1()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/server.go:1283 +0xaa0
  sync.(*Once).doSlow()
      /usr/local/Cellar/go/1.13/libexec/src/sync/once.go:66 +0x100
  sync.(*Once).Do()
      /usr/local/Cellar/go/1.13/libexec/src/sync/once.go:57 +0x68
  github.com/lightningnetwork/lnd.(*server).Start()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/server.go:1207 +0x7d
  github.com/lightningnetwork/lnd.Main()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/lnd.go:624 +0x29d3
  main.main()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/cmd/lnd/main.go:14 +0x3f

Goroutine 143 (running) created at:
  github.com/lightningnetwork/lnd/routing.(*ChannelRouter).Start()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/routing/router.go:521 +0x42c
  github.com/lightningnetwork/lnd.(*server).Start.func1()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/server.go:1283 +0xaa0
  sync.(*Once).doSlow()
      /usr/local/Cellar/go/1.13/libexec/src/sync/once.go:66 +0x100
  sync.(*Once).Do()
      /usr/local/Cellar/go/1.13/libexec/src/sync/once.go:57 +0x68
  github.com/lightningnetwork/lnd.(*server).Start()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/server.go:1207 +0x7d
  github.com/lightningnetwork/lnd.Main()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/lnd.go:624 +0x29d3
  main.main()
      /Users/nsa/go/src/github.com/lightningnetwork/lnd/cmd/lnd/main.go:14 +0x3f
==================

Found while running the integration tests with -race

So you mean you've modified the binaries that are executed to build with -race?

Found while running the integration tests with -race

So you mean you've modified the binaries that are executed to build with -race?

Yeah I had to increase all of the timeouts as well since the race detector is super slow.

Very cool, once we clean up the lnd package a bit cmd/lnd, we should be able to use that instead to runt the integration tests rather than spinning up a new binary. I'm working on a PoC of this direction for the main package. Amongst many other things, it would allow us to have the itest count toward cover coverage and also likely make the tests much faster as each node is now just a series of goroutines rather than entirely new go runtime instance.

Very cool, once we clean up the lnd package a bit cmd/lnd, we should be able to use that instead to runt the integration tests rather than spinning up a new binary. I'm working on a PoC of this direction for the main package. Amongst many other things, it would allow us to have the itest count toward cover coverage and also likely make the tests much faster as each node is now just a series of goroutines rather than entirely new go runtime instance.

that's great! I wanted to target the itests since they test more cases with various subsystems than the unit tests do. If this could be eventually run as part of the CI I'm sure it would catch even more bugs


Represent S3 bucket policies in the graph

Description:

Describe your idea.  Please be detailed.  If a feature request, please
describe the desired behavior, what scenario it enables, and how it
would be used.

Cartography already pulls s3 bucket policies and parses them with policyuniverse to determine internet exposure. We should expand on this feature to compute s3-specific permission relationships.
For background, S3 permissions can be defined by S3 ACLs, IAM policies, and S3 bucket policies (AWS ref).
We already surface S3 perms at the IAM level but we do not have visibility at S3 itself. Many orgs may choose to use only S3-specific perms so lack of this support in this cartography gives an incomplete picture.
Plan
I see this feature as needing 2 tasks.

Represent the S3 policies and policy statements in the graph.
Use the data from (1) to compute AWSPrincipal-to-S3Bucket S3-specific relationships. This will be similar to our resource permission relationships functionality with IAM, although I don't think we necessarily need to define a whole separate yaml file for that.

It data model will look like this:

Testing for this feature can be done like this:

Help wanted! Please reach out if can work on this and we can help point in the right direction.
[optional Relevant Links:]

Any extra documentation required to understand the issue.

https://aws.amazon.com/blogs/security/iam-policies-and-bucket-policies-and-acls-oh-my-controlling-access-to-s3-resources/
https://lyft.github.io/cartography/modules/aws/permissions-mapping.html

Further discussion on Slack: https://lyftoss.slack.com/archives/CTZUQL0KX/p1643754325800859
Summarized,

Ideally we will be able to consolidate the IAM + resource policy story for at least S3 buckets
We will want to accurately represent cross-account bucket accesses

I've added more details in this one-pager: https://docs.google.com/document/d/1EOn9DBwubQhT_uk0WUO2Sx4WjSPR8mdBBbbWuheloc8/edit#. @SecPrez - can you have a look? :-)


The requested resource was not found on this server.

In case I am logged into the ASRG webpage and I click in the menu the green marked items (see picture_1) I got the error message "The requested resource was not found on this server." (see picture_2)

@SvenSchran Can you please add the pictures?


defineR metadata template

The FAQ at https://definer.r-sassy.org/articles/defineR-faq.html mentions:
Is this the same template as the SAS® toolkit?
Q: This template looks exactly like the template in the SAS® Clinical Standards Toolkit. Are they the same?
A: Yes. The metadata template for the defineR package was taken directly from the SAS® template. This was done for ease of interchange/migration between the two systems.
This is incorrect. Although the metadata content is very similar, the structure of the metadata tables and columns is quite different between CST and defineR.

Yes, you're right.  I just updated the documentation.  The template was take from the book "Implementing CDISC Using SAS" instead of from the CST.  Will also resubmit my COSA application.

Aah, yes, I forgot about Holland / Shostak book! Thank you.

Just resubmitted updated application to COSA, and updated package to CRAN.  Thanks for reminding me of this issue.


proto.InternalMessageInfo is undefined

Hi,
One of my project dependencies depends on your library's master, and now my build is broken with the following error message:

../../vendor/google.golang.org/genproto/googleapis/rpc/status/status.pb.go:111:28:
undefined: proto.InternalMessageInfo

I'm using dep.
Please advise.
Many thanks.

I think this is the same issue as #66. I believe you have to go get -u github.com/golang/protobuf/proto

In my case, I had to dep ensure -update my project. After that, everything compiled.


Daniel Widdis: Blacklist asvi.biz

Daniel Widdis requests the blacklist of the website asvi\.biz. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

asvi\.biz has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Was not aware that I should not blacklist after one TP.  If possible to convert to watch, please do, otherwise please close.

Rejected by NobodyNada in Charcoal HQ. Reason: 'Only one hit; needs 2 more before eligible for blacklist (under the preexisting campaign clause)'


Reshaping tensors

New Tensorex.reshape/2 function to resize the tensor with keeping its values.

Codecov Report

Merging #6 (36f7787) into main (04b5714) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          238       241    +3
=========================================
+ Hits           238       241    +3

Impacted Files
Coverage Δ

lib/tensorex.ex
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #6 (36f7787) into main (04b5714) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          238       241    +3
=========================================
+ Hits           238       241    +3

Impacted Files
Coverage Δ

lib/tensorex.ex
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


show correct message when transforming with axis-constraint (fixes #4870)

when moving a 3d object and pressing MMB to switch the axis, the wrong message was displayed.

@nunodonato Please, refer the issue fixed, as explained in Github's help page. You can do it in the PR text rather than the commit message as well.

I think there was no open issue on this... should I have opened it first?

@nunodonato What about https://github.com/godotengine/godot/issues/4870 ?

@bojidar-bg good find!


Pull to refresh with multitouch

When 3 or 4 fingers are placed on the screen where there is the pull to refresh component, the content jumps around:
Demo here.

Thanks, fixed. It is also possible to follow only last changed touch but i am not sure to bring hundreds of lines of code for that. Now it follows just a first touch, at least much better than jumping content :)

Looks good - thanks for the quick fix :)
I will try it out shortly and let you know if I have any issues.

Works like a charm. Thanks again.


All line charts are zero based?

If I render a line chart with or without the -zero-based argument, the y-axis is always anchored at zero. Is the default y-axis supposed to be based on the minimum value?

Thank you.
The --zero-based option was only partially supported by this commit:
https://github.com/marianogappa/chart/commit/6d931b2e1056773aee348d88c9a84b0fd14ffac3
This release has --zero-based support for all charts
https://github.com/marianogappa/chart/releases/tag/v1.0.3
(or just go get -u)
FYI --zero-based was actually implemented for a kind of line charts, but there are 2 underlying types of line charts:

"discrete" line charts
"scatter" line charts
The difference is that "discrete" line charts are not scaled, because the x-axis values are strings.

Let me know if it works for you. Thank you for your reviews! Please close if solved.

Works as expected!


Bump Actions cache to v2

The scheduled action ran as expected today and succeeded, however GitHub Actions cache v1 does not support reading or writing caches when using a "schedule" trigger. Bumping to v2 which does support this.

Fixed the failing trailing space check here - #725


Replace position: sticky with sticky-js

Why even bother?  Support for position: sticky is already pretty good and it only gets better plus it can degrade gracefully.  Isn't this just another library to slow page loads?

position: sticky doesn't account for viewport heights. This library will disable the sticky when the window is small, so we don't get any cutoff elements. People have been complaining about it a lot.

Ah, okay, that's good then :+1:

Alternatively use a media query to not position: sticky if viewport height is too small

This will need some changes after media page I think.

:D @matthewdias Can you update for media pages? :heart:


Minor design/dark-mode improvements

Note: a lot of these proposed changes are just personal preferences! Happy to revert any of these changes, but I think a few of them are important for readability.
Home page:

Fixed alignment of title + badge/label (e.g. "Instructions — ARROWGLACIER")
Added letter spacing to small uppercase text for improved readability
Fixed text colors for dark mode to improve a11y/visibility

Playground page:

Fixed alignment of title + badge/label (e.g. "EVM Playground — ARROWGLACIER")
Fixed text colors for dark mode to improve a11y/visibility

About page:

Added max width to improve readability on larger screens

Screenshots
For comparing before vs after. (Most of the changes are subtle, see above for description of what changed!)

Home page (before)
Home page (after)

Playground page (before)
Playground page (after)

About page (before)
About page (after)

These changes all look great to me, thanks for the PR!
How did you decide on a max-width for the About page? My gut feeling when loading the new version was that it felt a bit narrow to me. Though I agree with you that a max width of 5xl definitely feels too big.

hey @malexw! i think the "best practice" max width for long-form text content is between 50-100 characters (which is quite narrow), and max-w-4xl comes out to around 120-130 characters per line, which i thought was reasonable.
(for reference: https://css-tricks.com/six-tips-for-better-web-typography)
this "about" page is also a bit tricky because it's pretty long and almost reads like its own blog post, so i also took a look at blogs like supabase's and stripe's for reference, and they set a relatively narrow max width.
(also if you're worried about too much whitespace we could probably add a floating table of contents on the left side, and/or something else on the right side 🤔)


With play store, it is accessed after adding agmail a/c ,how about aurora?

Solved already.

Done


modules/keymap: include buffer when registering keymapsOnEvents

This feels more correct to me: I believe we were registering a keymap for all buffers, even if only some of them have experienced the relevant autocmd.
I don't know if it's guaranteed here that args.buf always exists (but maybe it's not a problem if it doesn't exist, because we'll still register a keymap for all buffers?).
This fixes https://github.com/nix-community/nixvim/issues/2711

@mergify queue

Thanks for the quick merge, @matt

Bisecting a lua error points this commit as the cause.
Error executing lua callback: vim/shared.lua:0: key found in more than one map: buffer
stack traceback:
	[C]: in function 'error'
	vim/shared.lua: in function 'tbl_extend'
	/nix/store/d7h1rgpfh4ds52p7mj71gpj1yvgs00cg-init.lua: in function </nix/store/d7h1rgpfh4ds52p7mj71gpj1yvgs00cg-init.lua:0>
	[C]: in function 'nvim_exec_autocmds'
	...ompiled-0.10.2/share/nvim/runtime/lua/vim/lsp/client.lua: in function '_on_attach'
	...ompiled-0.10.2/share/nvim/runtime/lua/vim/lsp/client.lua: in function ''
	vim/_editor.lua: in function <vim/_editor.lua:0>

@khaneliman, I opted to use vim.tbl_extend("error", ...) to try to avoid suprising people that we're now specifying a buffer for them.
Are you specifying an autoCmd that specifies a buffer?

I've got only a handful of autoCmds https://github.com/search?q=repo%3Akhaneliman%2Fkhanelivim autoCmd&type=code and then a bunch of plugins with will create their own.

I guess the easiest way to track this down would be to look at your generated init.lua file. Can you give me a command to repro the issue?

Hm, maybe extending with "error" mode isn't the best approach? If a user has explicitly configured something, that should override whatever defaults we're setting. :thinking:

If a user has explicitly configured something, that should override whatever defaults we're setting.

Generally I'd agree, but in this case, I think we're talking about a buffer hardcoded at build time? Which doesn't make any sense to me. Perhaps I'm fundamentally misunderstanding what's happening here. Having a repro would be nice to set me straight.

a buffer hardcoded at build time

I believe you can use "buffer 0" to reference the "current" buffer? So maybe some people are explicitly doing that?
I haven't looked too closely, so it's likely I'm missing something fundamental too. But my first thought is that if we don't want to allow setting buffnr through nixvim options, that should be a eval time filter and/or warning/assertion.

Ah yeah, using "buffer 0" could make some sense.
Sorry for the breakage. I'm leaving for a trip soon, and won't have any real time to spend on this until the new year. Here's a quickfix: https://github.com/nix-community/nixvim/pull/2719.


POC: Flow Integration tests

POC Golden Path Flow:

Get node status and info
Publish a dataset
Index + query DDO
Decrypt and download dataset

done in https://github.com/oceanprotocol/ocean-node/pull/161


Cannot initialise Vuex store from localStorage on App initialization for Authentication

Hi Guys,
I'm struggling to initialize my Vuex store with the account details of the logged in user from localStorage.
I've been through as many examples as I can of Auth using Nuxt, and none of them demonstrate how on the client side to pull an authToken from localStorage to re-use with subsequent API requests when the user refreshes the page or navigates to the App
Disclaimer: I'm not using Nuxt in SSR (this might affect your answer).
What is annoying is that I can actually load from localStorage and initialize my state but then it gets overwritten. I'll show you what I mean with this small code example:
buildInitialState () {
   if (!process.server) {
      // Query the localStorage and return accessToken, refreshToken and account details
      return {accessToken: <valid-string>, refreshToken: <valid-string>, account: <valid-json-blob>}
   } else {
      // Return "empty map", we use the string "INVALID" for demonstration purposes.
     return {accessToken: "INVALID", refreshToken: "INVALID", account: "INVALID"}
  }
}

export const state = () => buildInitialState()

If I put a breakpoint on buildInitialState I can see that I correctly initialize the state with the value of localStorage, i.e. I get the accessToken and refreshToken, etc.. back.
All seems well.
But then .....in another part of the program I'm using Axois to send requests, and I use an axios interceptor to decorate the request with the accessToken. To do this I have to stick it into a plugin to get access to the store.
Something like so:
export default ({ app, store }) => {
  axios.interceptors.request.use((config) => {
    const accessToken = _.get(store.state, ['account', 'accessToken'])
    if (accessToken) {
      config.headers.common['x-auth-token'] = accessToken
    }
    return config
  }, (error) => Promise.reject(error))
}

Here the store is closed over in the arrow function supplied to axios so when I go to send the request it sees if there is a valid accessToken, and if so then use it.
BUT, and here's the kicker, when a request is made, I look at the store.state.account.accessToken and low and behold its been reinitialized back to the value of "INVALID".
What? Que?
It's almost like the store was reinitialized behind the scenes? Or somehow the state in the plugin is "server side state"?? because if I try and log buildInitialState I don't get any messages indicating that the path that produced a map with INVALID is being run.
Basically, I don't thoroughly understand the initialization pathway Nuxt is taking here at all.
If any Nuxt masters could help me out understand this a bit more that would be great, it's turning into a bit of a show stopper for me.
Essentially! All I want to be able to do is save the user so that when they refresh their page we can keep on running without forcing them to re-login again....I thought that would be simple.
Thanks and regards, Jason.

I wonder if I'm fighting the system here a bit too much -- because I know access to window is not is a PITA during initialization.
Is there an alternative method that I'm over looking to save a session on the client that is super easy that I'm overlooking here (Cookie?)

Thanks @alexchopin
I've solved this with a bit of experimentation and comments from other posters around what is called SSR and SPA.
Firstly, this https://github.com/nuxt/nuxt.js/issues/1500 thread really helped me and the final comment from @jsonberry steered my mind in the right direction, away from fetch and asyncData.
I finally had a bit more of an understanding of how NUXT.js was separating SSR and SPA calls.
I then tried @robyedlin suggestion of putting localStorage initialization in the created() method for my main layout/default.vue page.
While I made progress with that suggestion it turns out created() is also called SSR and I was still trying to initialise my store from credentials that weren't accessible.
Finally, moving the initialisation to mounted() did the trick!
So in summary:

My account store is left alone, I don't try and initialize it when it is created (it's just overwritten  at some point when the SSR stuff runs)
On mounted() in layout/defualt.vue I read from localStorage and initialize the account store so I can start making API requests with the appropriate accessToken.

That seems to have done the trick.


Discontinue the support of Windows Vista

In order to reduce the maintenance burden, we have decided to discontinue the support of Windows Vista and remove support code for that.

Basically Mozc 2.17.2445.102 (42fe48a6cba49c14c6332dde58a3753412ed0f88) is the last version that is supposed to run on Windows Vista.


TS Variable types wrong for operations with default variables

Describe the bug
The types generated for operations with variables that have set defaults are wrong, and force a value.
To Reproduce
Steps to reproduce the behavior:

My GraphQL schema:

extend type Mutation {
  setUserActive(id: ID!, active: Boolean!): Boolean
}

My GraphQL operations:

mutation SetUserActive($id: ID!, $active: Boolean = true) {
  setUserActive(id: $id, active: $active)
}

My codegen.yml config file:

overwrite: true
documents:
  - src/client/**/documents.graphql
schema:
  - src/client/**/*schema.graphql
generates:
  src/client/generated/graphql.ts:
    config:
      avoidOptionals: false
      immutableTypes: true
    plugins:
      - typescript
      - typescript-operations
      - typescript-apollo-angular
  src/client/generated/schema-client.graphql:
    plugins:
      - "schema-ast"

Expected behavior
I expect the generated Variable type to allow active to be optional
Environment:

OS: 10.13.6
<EMAIL_ADDRESS>NodeJS: 10

#1567 Should fix it

I released a canary version, could you try: 1.0.5-alpha-4b26c306.0+4b26c306?

Fixed in 1.0.5.


composer panics when curl fails to download a package in the worker

Apr 23 15:54:05 ip-172-31-67-32.ec2.internal osbuild-worker[14173]: Running 'osbuild' job d0274498-fb07-41a7-96b1-88a643c2187c
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]: Traceback (most recent call last):
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]:   File "/usr/bin/osbuild", line 33, in <module>
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]:     sys.exit(load_entry_point('osbuild==28', 'console_scripts', 'osbuild')())
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]:   File "/usr/lib/python3.9/site-packages/osbuild/main_cli.py", line 137, in osbuild_cli
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]:     r = manifest.build(
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]:   File "/usr/lib/python3.9/site-packages/osbuild/pipeline.py", line 282, in build
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]:     source.download(store, libdir)
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]:   File "/usr/lib/python3.9/site-packages/osbuild/sources.py", line 55, in download
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]:     raise RuntimeError(f"{source}: " + reply["error"])
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14595]: RuntimeError: org.osbuild.curl: curl: error downloading {'url': 'http://ftp.usf.edu/pub/fedora/linux/updates/33/Everything/aarch64/Packages/l/libtirpc-1.2.6-3.rc4.fc33.aarch64.rpm'}: error code 22
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14173]: 2021/04/23 15:54:10 Job d0274498-fb07-41a7-96b1-88a643c2187c failed: error decoding osbuild output: unexpected end of JSON input
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14173]: the raw output:
Apr 23 15:54:10 ip-172-31-67-32.ec2.internal osbuild-worker[14173]: Waiting for a new job...
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: 2021/04/23 15:54:11 http: panic serving @: runtime error: invalid memory address or nil pointer dereference
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: goroutine 325 [running]:
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: net/http.(*conn).serve.func1(0x400007c500)
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]:         /usr/lib/golang/src/net/http/server.go:1801 +0xf4
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: panic(0xaaaab6363460, 0xaaaab66bac80)
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]:         /usr/lib/golang/src/runtime/panic.go:975 +0x3f0
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: github.com/osbuild/osbuild-composer/internal/osbuild1.(*Result).Write(0x0, 0xaaaab64160c0, 0x4000174700, 0xaaaab64160c0, 0x4000174700)
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]:         /builddir/build/BUILD/osbuild-composer-3991bd81f614fd9f03083695958efbada0d2d34b/_build/src/github.com/osbuild/osbuild-composer/internal/osbuild1/result.go:83 +0x28
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: github.com/osbuild/osbuild-composer/internal/weldr.(*API).composeLogHandler(0x40000eeb80, 0xaaaab641f700, 0x4000174700, 0x40001ccf00, 0x40001c6880, 0x2, 0x4)
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]:         /builddir/build/BUILD/osbuild-composer-3991bd81f614fd9f03083695958efbada0d2d34b/_build/src/github.com/osbuild/osbuild-composer/internal/weldr/api.go:2707 +0x394
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: github.com/julienschmidt/httprouter.(*Router).ServeHTTP(0x40000b0f00, 0xaaaab641f700, 0x4000174700, 0x40001ccf00)
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]:         /usr/share/gocode/src/github.com/julienschmidt/httprouter/router.go:387 +0x9a4
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: github.com/osbuild/osbuild-composer/internal/weldr.(*API).ServeHTTP(0x40000eeb80, 0xaaaab641f700, 0x4000174700, 0x40001ccf00)
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]:         /builddir/build/BUILD/osbuild-composer-3991bd81f614fd9f03083695958efbada0d2d34b/_build/src/github.com/osbuild/osbuild-composer/internal/weldr/api.go:192 +0x114
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: net/http.serverHandler.ServeHTTP(0x4000174620, 0xaaaab641f700, 0x4000174700, 0x40001ccf00)
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]:         /usr/lib/golang/src/net/http/server.go:2843 +0xbc
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: net/http.(*conn).serve(0x400007c500, 0xaaaab6421080, 0x400028e580)
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]:         /usr/lib/golang/src/net/http/server.go:1925 +0x6f4
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]: created by net/http.(*Server).Serve
Apr 23 15:54:11 ip-172-31-67-32.ec2.internal osbuild-composer[14172]:         /usr/lib/golang/src/net/http/server.go:2969 +0x2d8

seen here: https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1207472219

@gicmo something to improve in osbuild to give structured errors in this case?

See https://github.com/osbuild/osbuild-composer/issues/1414 for more details. @teg do you think this is something to fix in osbuild?

This is totally on the list to fix in osbuild, has been on my mind for a long time. I am laying down the foundations with the new host services infra.

If we expect osbuild to fail with an exception from time to time, should we also fix this on the osbuild-composer side? For example: Is it a good idea to expect JSON output in case osbuild failed?

I guess we should clarify the different failure modes osbuild can have and handle them appropriately in the worker. Might make sense to discuss this after the host services have landed?


Bugfix for regex that matches specs to load

Bugfix: line 71 initialized a new variable, fileMatcher which gets set to a regular expression matching files ending in ".js" if "matcher" (an optional argument to jasmine.executeSpecsInFolder) is falsey.
However, instead of passing "fileMatcher" to specs.load, "matcher" is passed. This resulted in incorrect selection of which files to execute as spec files, in the absence of an explicit "matcher".
The fix is to pass "fileMatcher" to specs.load, instead of "matcher".

thank it has been merged


Add support for Lightning Web Components

@kevinohara80 Can you take a look at this sometime soon?

@kevinohara80 Also if you are interested in having a co-maintainer to help with the occasional PR's like this for adding metadata types, I'm up for it.

@kevinohara80 Bump!


Add Hub Token

Add Hub Token Listing
Hub, the Human Trust Protocol, solves endemic trust problems and provides verifiable and portable trust. The HUB token’s aim is to encode identity and reputation on the blockchain, to become the next digital identity protocol interoperable across multiple platforms
Project background:
Official announcement: https://hubtoken.org
Project team background: https://hubtoken.org
Project basic information: https://hubtoken.org
Tradeable exchanges: Bitcoin.com, UniSwap
Block.cc: https://block.cc/coin/hub-token
CMC: https://coinmarketcap.com/currencies/hub-human-trust-protocol/
CoinGecko: https://www.coingecko.com/en/coins/hub-token
Exchange Listings:
https://exchange.bitcoin.com/hub-to-usdt
https://exchange.bitcoin.com/hub-to-btc
https://info.uniswap.org/pair/0xe73278216cce7c0275794cf7858034f7bf2cd8e7
Social Media:
"blog": "https://medium.com/@hubtoken",
"facebook": "https://www.facebook.com/hubtoken/",
"linkedin": "https://www.linkedin.com/company/hubtoken/",
"twitter": "https://twitter.com/hubtoken",
Youtube: https://www.youtube.com/channel/UC3W5n0ZsEw5E4oLzjhOJYAA

Hi @JamesWatling  - There is a new requirement that the logo has to be in SVG format. Can I ask you to add it as a replacement for the PNG one? Thanks

@xrn Thanks for letting me know I have changed the image and supplied an SVG for reference


Babylon Native getting different shadow shader code than appears on the Web

For questions, please use the forum.
Describe the bug
Under certain poorly-understood conditions, Babylon.js seems to be sending different shadow shader code to Native than it does to the browser.
From Spector.js:

From ShaderCompilerD3D.cpp:

To Reproduce
Replace the default light creation in experience.js with something like the following:
        scene.activeCamera.radius = 5;
        const light = new BABYLON.SpotLight("*spot00", new BABYLON.Vector3(2, 20, -10), new BABYLON.Vector3(0, -1, 0.3), 1.2, 24, scene);

        const shadowGenerator = new BABYLON.ShadowGenerator(128, light);
        shadowGenerator.getShadowMap().renderList.push(scene.meshes[0]);

        const ground = BABYLON.Mesh.CreateGround("Ground", 50, 50, 1, scene);
        ground.position.y = -0.4;

        ground.receiveShadows = true;

Compare with a similarly established Playground on the Web.
Expected behavior
If different shader code is passed to Native versus the Web, I would expect that difference to be required to make the shadows work. As it stands, the shadows don't render, and it's unclear why the shader source is different.

output is different: packing to 4 floats VS returning 1 float. This is generally the case when you don't have float texture support and pack a float to RGBA8.
Looking at the caps in native engine, I think it's the case here:
https://github.com/BabylonJS/Babylon.js/blob/c89dbd5ae3ccb3126aa03c84869fbdfa8b7f3e7b/src/Engines/nativeEngine.ts#L851

We need to check if this still repros since we added float texture support.

Some more flags are needed to get same shaders between web and native on my PC:
https://github.com/BabylonJS/Babylon.js/blob/18d6cdcda0438711750b4a411e60af7906a4e050/packages/dev/core/src/Engines/nativeEngine.ts#L246
Once tweaked with same caps between web and native, I can see the same shader.
Closing this issue: validation tests are testing shadow and this issue exists for the caps : https://github.com/BabylonJS/BabylonNative/issues/553


Cannot connect to the Extension Marketplace

Its been a few months I've been waiting and wondering if this software will ever work.  Tried on Debian, Ubuntu, Win 10, 11.  None can install extensions so never got past installing and uninstalling.   Always installing newest version.  Error "We cannot connect to Marketplace ......

Please share the logs from the following locations while you reproduce the issue
- Help -> Toggle Developer Tools -> Console
- View -> Command Pallette... -> Toggle Shared Process -> Console
- View -> Open View… -> Log (Shared)
- View -> Open View… -> Log (Window)

same issue here, get this error message when using the marketplace:
extensionsViews.ts:323 Error querying extensions gallery Cannot read property 'toLowerCase' of undefined
query @ extensionsViews.ts:323

Hi guys,
Running into a similar problem. Brand new installation of Manjaro and Brand new installation of vscode.
When attempting to search for extensions in the marketplace I am told it cannot connect. I've attached the console logs from the developer tools. Not too sure how to make sense of it. Would appreciate any input, thank you.
vscode-app-1626298121199.log
I've tried the following:

Disabled firewall (ufw)
Updated all packages to most recent versions

I'm a linux n00b so I'm unsure what else I can do. Will continue working on this as I can. Thanks again.

@markovicdenis Is there a full stack trace of this error in the console? or in the logs View > Open View > Log (window) ?
If so can you please share it?

@sandy081 Weirdly enough I don't see a "Log (window)" under open view options following your 4 step instructions. Best I can do is use the "Save as" button in the console. I should also mention that this issue only happens on VSCode Insiders build, everything works fine in the stable version...
vscode-app-1626423119606.log

Can you please try the command Developer: Open Log File... ?

Can you please try the command Developer: Open Log File... ?

Yeah, that works...
rendererLog.txt

after recent update (12th July 2021) I get "We cannot connect to the Extension Marketplace at this time, please try again later."

How I ended up resolving it was removing code and replacing it with the snaps package.

Same here, Snaps package solved it.

@critamine
thanks for the hint. My choice was to downgrade to version, that did not suffer from the issue

/duplicate of #128583