Emscripten WebGL inefficiency with glEnable/DisableVertexAttribArray

Looking at a bgfx demo in Spector.js shows the two following profiles:

The renderer first disables all attrib arrays, and then re-enables them. These API calls are quite inefficient in web browsers. It would be better to use a bitfield to track which are currently set, and which want to be set, and only do the minimal delta of enable/disable calls to switch from old state to new state. This can improve CPU performance on the order of +5%.

This can improve CPU performance on the order of +5%.

Cool. Send PR.

A quick test with removing the redundant calls to glEnableVertexAttribArray and glDisableVertexAttribArray from the generated JS build output code shows a -9.9% reduction in used CPU time (or +11% performance increase).
Before:

After:

(glDisableVertexAttribArray removed to be never called, glEnableVertexAttribArray only called to enable array indices if they haven't been enabled yet)

You still have to call glDisableVertexAttribArray for attributes not used by vertex shader. This type of optimization affects other platforms. Could you check on some other platform other than desktop?

You still have to call glDisableVertexAttribArray for attributes not used by vertex shader.

Actually, why? A honest question, I was thinking the same, but cannot find a reason in the GL spec to see why any attrib arrays need to be disabled. The GL spec does not seem to give a reason, technical or behavioral, that I could find. Disabling an attrib array means "I want to use a constant vector value for this attribute instead of sourcing the attribute from a VBO" (i.e. source that attribute via glVertexAttrib*f instead of glVertexAttribPointerfv), it does not mean that that attribute index would be disabled (there is no function to disable attribute indices). Also disabling an attrib array does not unbind the VBO from that attribute index so calling glDisableVertexAttribArray does not contribute to releasing memory either. Extra attributes not consumed by a VS are just ignored.

This type of optimization affects other platforms. Could you check on some other platform other than desktop?

I did not actually modify the engine code, but just the build output of a page from Emscripten that I was given to consult. I don't have the source project to test other platforms.

See: https://github.com/bkaradzic/bgfx/pull/1515

Thanks, very interesting. In such case, using the bitfield approach to keep the enabled set of attribute array indices to a minimum can be used. In the profile numbers above where I removed the glDisableVertexAttribArray calls altogether there was no effect to rendering, so the profiles show an upper limit as to what the performance effect of these api calls is.


Fix committing to branch

Fixes #13

Worked on https://github.com/nimrodkor/test_yor_action/actions/runs/1692837581, see commit https://github.com/nimrodkor/test_yor_action/commit/c6d0b643a272d4bc4b65f1d8849930a914239a51


detector.py only reads utf-8 encoded files

copydetect was throwing "file not ASCII text" for multiple files I am working on. In detector.py it expects all readings to be in utf-8, so I used chardet to automagically detect file encodings and set the appropriate encoding when opening a file.
Fix 1.1 - add to imports:
import chardet
Fix 1.2 - detect character encoding:
In "CodeFingerPrint.init"
change:
"with open(file, encoding="utf-8") as code_fp:"
to:
rawdata = open(file, "rb").read()
encoding = chardet.detect(rawdata)['encoding']
with open(file, encoding=encoding) as code_fp:
This will allow copydetect to work with files of any encoding. I had this problem on my system and had to fix it.

I've created a fix/other_encodings branch that allows encoding specification or autodetection if chardet is installed. I still have to do a bit of cleanup and documentation updating but if you install the package from that branch you should be able to use --encoding DETECT on the CLI to read the non-utf8 files.

The CLI flag allowing other encodings (#43) has been included in copydetect 0.4.6


Problem using this library with Spark

I'm trying to use this library and it works very well except when I use it in a Spark (both 1.3.1 and 1.4.0) application. I get an IllegalAccessError on the LogstashBasicMarker but I'm not sure why:
Exception in thread "main" java.lang.IllegalAccessError: tried to access method org.slf4j.helpers.BasicMarker.<init>(Ljava/lang/String;)V from class org.slf4j.helpers.LogstashBasicMarker
	at org.slf4j.helpers.LogstashBasicMarker.<init>(LogstashBasicMarker.java:25)
	at net.logstash.logback.marker.LogstashMarker.<init>(LogstashMarker.java:35)
	at net.logstash.logback.marker.SingleFieldAppendingMarker.<init>(SingleFieldAppendingMarker.java:37)
	at net.logstash.logback.marker.ObjectAppendingMarker.<init>(ObjectAppendingMarker.java:47)
	at net.logstash.logback.marker.Markers.append(Markers.java:59)
        ...

Maybe LogstashBasicMarker should not be used to bypass the visibility level of the constructor of BasicMarker? Anyway, do you know how to solve this problem?

I don't have any experience with spark.  If you can provide a small sample application that reproduces the problem, I'll be happy to look into it.

I created a small example that just creates a Marker. To see the error, you can create the assembly of the project with sbt assembly and then run it as Spark job with something like ${SPARK_HOME}/bin/spark-submit --master ${MASTER} logbackSparkProblem-assembly-1.0.jar (based on when you have spark installed, if it's a local install then you can set MASTER="local[2]").

Thanks for the example @melrief!   It's a good thing you provided it, because I thought you were referring to the spark framework.
I have reproduced the problem using apache spark.
By default, org.slf4j.helpers.BasicMarker is loaded from the spark assembly jar (rather than your assembly).  You can see this by using verbose classloader output like this:
SPARK_SUBMIT_OPTS="-verbose:class" ${SPARK_HOME}/bin/spark-submit --master ${MASTER} target/scala-2.11/logbackSparkProblem-assembly-1.0.jar

which outputs:
[Loaded org.slf4j.helpers.BasicMarker from file:/tmp/spark-1.4.0-bin-hadoop2.6/lib/spark-assembly-1.4.0-hadoop2.6.0.jar]
[Loaded org.slf4j.helpers.LogstashBasicMarker from file:/tmp/logbackSparkProblem/target/scala-2.11/logbackSparkProblem-assembly-1.0.jar]

A workaround is to set spark.driver.userClassPathFirst=true in your spark config  (either via --conf spark.driver.userClassPathFirst=true OR the spark-defaults.conf file).  This forces spark to load BasicMarker from your assembly.  You can see this by running:
SPARK_SUBMIT_OPTS="-verbose:class" ${SPARK_HOME}/bin/spark-submit --conf spark.driver.userClassPathFirst=true --master ${MASTER} target/scala-2.11/logbackSparkProblem-assembly-1.0.jar

which outputs
[Loaded org.slf4j.helpers.BasicMarker from file:/tmp/logbackSparkProblem/target/scala-2.11/logbackSparkProblem-assembly-1.0.jar]
[Loaded org.slf4j.helpers.LogstashBasicMarker from file:/tmp/logbackSparkProblem/target/scala-2.11/logbackSparkProblem-assembly-1.0.jar]

I'm not sure why spark prevents access to the BasicMarker package-private constructor.  I haven't investigated the classloader configuration being in spark yet.  Normally, this will work fine in a typical java application.
Other than the workaround I mentioned above, I believe the only fix for this will be to either:
A. Modify BasicMarker in slf4j-api, to expose a public constructor
OR
B. Remove usage of org.slf4j.helpers.BasicMarker and reimplement the logic from it in logstash-logback-encoder
I'll implement B for the time being.

Sounds good to me and thanks for the workarounds!

I've created the PR https://github.com/logstash/logstash-logback-encoder/pull/108 for this that reimplements the logic of BasicMarker into LogstashBasicMarker

Thanks for the PR!

4.4 has been released with this fix


Setup include-what-you-use & link-what-you-use

Won't do yet -- after some reseach, it seems these tools are not too mature at this time to work on any project. link-what-you-use, for example, does not ship prebuilt binaries, only source tarballs, and (according to its main README) currently makes a number of assumptions about the names of the C++ files.


Issue #20 Integrate glide

#20

@ty2 I saw you're PR. Reason I didn't merge huge changes I'm about to post. Current code base does not fit some of requirements thus need to be changed. Once I push we can update and merge.

I suggest merge to dep to management for dependencies.

@ipfans Thought to use it since it was beta. Now they conform it is safe for production so worth to try. Thanks

Closed in favor to PR #44


The device_groups "kind" was incorrect, the test did not fail we need to investigate

Original issue:  #579
Suspicious test:   https://github.com/F5Networks/f5-common-python/blob/81e35af626579f96d13879a4f02506decb421aef/test/functional/cm/test_device_group.py#L65

Fixed by: 5e55005


Super call with reserved keyword

Describe the bug
When a super call contains a reserved keyword, it is highlighted when normally it would not.
Expected behavior
super:: calls shouldn't highlight reserved words.
Screenshots

LPC Code
inherit "/std/object.c";
inherit "/std/something.c";
void fn () {
    object::fn();       // object is highlighted like a variable
    something::fn();    // working as expected
}

VS Code Version:
Version: 1.78.2
OS: [e.g. Windows 10, MacOS, Arch Linux]
Windows 10
Additional context
vscode-lpc-lang v1.1.4

Confirmed, it is being highlighted as storage.type by virtue of object being one of the storage types.

Maybe should \b(\w+::) matched as meta.block. 🤔


Stop a game of hangman?

As far as I can tell, there's no command to stop an in-progress game of hangman.

no, and there won't be any, at least for now, since anyone can control the game.


update build script to use npm run tsc and npm run build

What changed -

use the tsc command defind in scripts in package.json,
run build script in gui folder, without this, when we run code.sh, we don't pick up the changes in gui folder.

noiiiice

beautiful


[CELEBORN-1023] The notifyBacklog method should send PbBacklogAnnouncement instead of BacklogAnnouncement

What changes were proposed in this pull request?
As Title
Why are the changes needed?
In https://github.com/apache/incubator-celeborn/pull/1905, the purpose is Convert BacklogAnnouncement, BufferStreamEnd, ReadAddCredit to PB. But in notifyBacklog method ,what it sends is BacklogAnnouncement
Does this PR introduce any user-facing change?
No
How was this patch tested?
PASS GA

@jiaoqingbo, I have sent PbBacklogAnnouncement instead of BacklogAnnouncement in #1905. But there is compatibility  problem in service for this. This could only send BacklogAnnouncement at present.

@jiaoqingbo, I have sent PbBacklogAnnouncement instead of BacklogAnnouncement in #1905. But there is compatibility problem in service for this. This could only send BacklogAnnouncement at present. cc @RexXiong

In ReadClientHandler, the following code converts PbBacklogAnnouncement to BacklogAnnouncement. Why is there a compatibility issue? Why does BufferStreamEnd work? Can you explain it in detail? @SteNicholas
  case RPC_REQUEST:
    try {
      TransportMessage transportMessage =
          TransportMessage.fromByteBuffer(msg.body().nioByteBuffer());
      switch (transportMessage.getMessageTypeValue()) {
        case BACKLOG_ANNOUNCEMENT_VALUE:
          receive(client, BacklogAnnouncement.fromProto(transportMessage.getParsedPayload()));
          break;

@jiaoqingbo, I have sent PbBacklogAnnouncement instead of BacklogAnnouncement in #1905. But there is compatibility problem in service for this. This could only send BacklogAnnouncement at present. cc @RexXiong

In ReadClientHandler, the following code converts PbBacklogAnnouncement to BacklogAnnouncement. Why is there a compatibility issue? Why does BufferStreamEnd work? Can you explain it in detail? @SteNicholas
  case RPC_REQUEST:
    try {
      TransportMessage transportMessage =
          TransportMessage.fromByteBuffer(msg.body().nioByteBuffer());
      switch (transportMessage.getMessageTypeValue()) {
        case BACKLOG_ANNOUNCEMENT_VALUE:
          receive(client, BacklogAnnouncement.fromProto(transportMessage.getParsedPayload()));
          break;

Client jar in Spark or Flink might not be able to upgrade. So this RPC can not be convert to PB recently.


Binary export tests generator

#17

Tests with char fail: https://github.com/npgsql/npgsql/issues/5110


Add strokeWidth to Cell component

Although it's not explicitly stated in the API documentation, there is a strokeWidth prop allowed in the Cell component.
You can see it in the second example here: http://recharts.org/en-US/api/Cell
This was a pretty simple addition.

thanks!


[Feature-Request] Internal shell

So with micro working so well when editing multiple files, I kind of don't ever want to have to leave micro to do anything. So I was wondering if it was possible for a working shell to exist inside a buffer, behaving just like a file really. This would mean you could have shells open in multiple tabs or in a buffer split accross the screen. Maybe something for v2?

Try using the > term command. Unless I'm misunderstanding I think this does what you want.

Holy f*ck micro really is perfect. Is this a v2 feature? As it's not in the docs.

Hmm, I did notice that when I am inside this terminal, and it's the only tab I can't use micro anymore, it's not capturing any input except mouseinput. Maybe there should be an escape sequence? Or did you also already think of that?

Yeah you're right, escape should probably unfocus the terminal, though escape is sometimes useful for programs that are running inside the terminal (maybe a better idea is double clicking escape?). The term command has actually been around for a while, but I guess I never added it to the docs...

Docomentation is important, you can't keep all the good stuff to yourself =p

Features don't have much purpose unless users actually know about them

I also notice the shell doesn't respond when I try to paste something into it.


Fix processing logic in master/scan_results/masscan_json_to_csv.py

Add try/except for files that may not be processed successfully
What about 0 byte files?
Send an email alert?

For 0 byte files: https://github.com/rackerlabs/scantron/pull/177
Not going to send email alert

try/except added in PR for https://github.com/rackerlabs/scantron/issues/193


Error while building from Source.

Hi Everyone.
I tried to build hive  from source but it generates the following error:
$ make
go get .
# github.com/araddon/gou
../../araddon/gou/testutil.go:26:6: error: expected operand
  for range timer.C {
      ^
../../araddon/gou/testutil.go:26:6: error: expected ‘{’
../../araddon/gou/testutil.go:26:6: error: expected ‘;’ or ‘}’ or newline
../../araddon/gou/testutil.go:29:9: error: break statement not within for or switch or select
    break
         ^
../../araddon/gou/testutil.go:31:3: error: expected declaration
   if tryct >= timeoutSecs*10 {
   ^
../../araddon/gou/testutil.go:33:4: error: expected declaration
    break
    ^
../../araddon/gou/testutil.go:34:3: error: expected declaration
   }
   ^
../../araddon/gou/testutil.go:35:3: error: expected declaration
   tryct++
   ^
../../araddon/gou/testutil.go:36:2: error: expected declaration
  }
  ^
../../araddon/gou/testutil.go:37:1: error: expected declaration
 }
 ^
make: *** [build/hive-server] Error 2

Please help me resolve this issue. Thanks in advance!

For reference am able to build from source without issue on Mac OS X with latest release of go (as of date of posting).
$ mkdir -p $GOPATH/src/github.com/nytlabs
$ cd $GOPATH/src/github.com/nytlabs
$ git clone git@github.com:nytlabs/hive.git
Cloning into 'hive'...
remote: Counting objects: 28, done.
remote: Total 28 (delta 0), reused 0 (delta 0), pack-reused 28
Receiving objects: 100% (28/28), 31.59 KiB | 0 bytes/s, done.
Resolving deltas: 100% (7/7), done.
Checking connectivity... done.
$ cd hive
$ make
go get .
go build -o build/hive-server .
$ go version
go version go1.8.3 darwin/amd64
$ uname -a
Darwin imacglitchdigital.local 15.6.0 Darwin Kernel Version 15.6.0: Mon Aug 29 20:21:34 PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64 x86_64
$ ./build/hive-server
2017/07/31 16:17:46 running hive-server on port 8080 storing data in elasticsearch under index hive


Update the standard editorconfig file

Added scss, js, json and erb to the standard editorconfig file. Ideally all languages that are used across GDS can be added so it is a simple copy / paste for new projects.

Added vendor section as requested @selfthinker.

Definitely a good topic to bring up at the Tech Forum. My stance is that we should be using one for all projects. Ideally only a single file in the root of a project to simplify maintenance. It would be good to get the various different teams to agree to a GDS standard for each language then use this for each new project.
Where we stand on "legacy" applications may be a little more difficult. It could be that the agreed standard is tweaked to fit this application (i.e. the .editorconfig in its root folder) rather than making a large number of changes retroactively.

After a conversation with @rboulton I propose we merge this PR as is as a first attempt at a global .editorconfig file. If any teams or language experts disagree with anything listed a seperate PR should be raised.

Good plan. Awaiting the :+1: and merge from @rboulton.


Containerize Python LSP

Include all dependencies and plugins, e.g. pyls-isort et al., so that no longer have to deal with virtualenv shenanigans or ambiguities or making sure to download everything and keep it organized.

See: https://github.com/emacs-lsp/lsp-docker/


Few managers optimizations

Polished few things:

Items cache:

Reorganized cache update, now it is similar to how we do it for Devices and Groups (do not clear items map, but update every item)
Used "overridable" functions addNewItem/updateCachedItem for two purposed update cache and update items. By default it just put but might be used to track additional maps (like uniqueIds) or update item by fields.
It is not necessary to override whole functions addItem/updateItem/removeItem and especially refreshItems just put manager specific code in addNewItem/updateCachedItem/removeCachedItem if necessary
Spread refresh calls by appropriate constructors

Used Permission class also for retrieving permissions from database

Do not think we will use common function executeMapQuery in near future, replace it to particular executePermissionsQuery
Updating permission cache now looks much much clear.

Also fixed small issue in group cache update.

Thanks for the tip. Did not think about it. Now it is perfect.

Merged, thanks.


[Generator] Add support of deepObject style in query params

Motivation
The generator changes for: https://github.com/apple/swift-openapi-generator/issues/259
Depends on https://github.com/apple/swift-openapi-runtime/pull/100 landing first and getting released, and the version dependency being bumped here.
Modifications
Added deepObject style to serializer & parser in order to support nested keys on query parameters.
Result
Support nested keys on query parameters.
Test Plan
Adapted snippet tests (SnippetBasedReferenceTests)

We discussed this offline, this is the PR https://github.com/apple/swift-openapi-generator/pull/538 reopened again, so that we can finish it up even while the original author is busy 🙂 Thanks @arthurcro for adding you both to the commit, it's important that we give credit to @kstefanou52 for the work already done!

Kicked off CI to see what state we're in.

Sorry, I couldn’t find the time to complete this PR yet. I made some progress, but there seems to be an issue with the unit tests—possibly something with the runtime library. I’ll have some time this weekend, so if @arthurcro would like any help, please let me know.

Sorry, I couldn’t find the time to complete this PR yet. I made some progress, but there seems to be an issue with the unit tests—possibly something with the runtime library. I’ll have some time this weekend, so if @arthurcro would like any help, please let me know.

Thanks for the update @kstefanou52! I've got some availability this weekend too and would be happy to help . If you'd prefer to complete it yourself given the progress you've made, that's completely fine - just let me know what works best for you!

Sorry, I couldn’t find the time to complete this PR yet. I made some progress, but there seems to be an issue with the unit tests—possibly something with the runtime library. I’ll have some time this weekend, so if @arthurcro would like any help, please let me know.

Thanks for the update @kstefanou52! I've got some availability this weekend too and would be happy to help . If you'd prefer to complete it yourself given the progress you've made, that's completely fine - just let me know what works best for you!

Thank you so much for the understanding @arthurcro. I'm just giving it a try and I will let you know about the outcome until Sunday end of the day.


CLI Usage GIF

It would be nice to have a GIF of a usage example.
Like those.
Such a GIF could be added to the info website from #17.

Would be great to have a label "nice to have" :D

You can create labels yourself.
https://github.com/povils/phpmnd/labels

@povils I suggest not to create 100 labels. I know the temptation! Resist! 😀

@ravage84 thanks! :)
@padraic i'll try to not :D


Error when opening sql file

I am getting an error when vim-dadbod-completion loads.
Failed to source `/home/jp/.local/share/nvim/lazy/vim-dadbod-completion/after/plugin/vim_dadbod_completion.lua`

vim/_editor.lua:0: FileType Autocommands for "sql"..script nvim_exec2() called at FileType Autocommands for "sql":0../home/jp/.local/share/nvim/lazy/vim-dadbod-completion/after/plugin/vim_dadbod_completion.lua: Vim(source):E5113: Error wh
ile calling lua chunk: ...dadbod-completion/after/plugin/vim_dadbod_completion.lua:8: attempt to index local 'completion' (a boolean value)
stack traceback:
^I...dadbod-completion/after/plugin/vim_dadbod_completion.lua:8: in main chunk
^I[C]: in function 'nvim_exec2'
^Ivim/_editor.lua: in function 'cmd'
^I...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:506: in function <...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:505>
^I[C]: in function 'xpcall'
^I.../.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:135: in function 'try'
^I...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:505: in function 'source'
^I...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:453: in function 'source_runtime'
^I...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:424: in function 'packadd'
^I...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:356: in function '_load'
^I...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:197: in function 'load'
^I...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:85: in function <...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:72>

# stacktrace:
  - vim/_editor.lua:0 _in_ **cmd**

Neovim version:
NVIM v0.10.1
Build type: Release
LuaJIT 2.1.1725453128
Plugin commit:
branch master
commit 880f7e9
Relevant configuration:
return {
  'kristijanhusak/vim-dadbod-ui',
  dependencies = {
    { 'tpope/vim-dadbod', lazy = true },
    { 'kristijanhusak/vim-dadbod-completion', ft = { 'sql', 'mysql', 'plsql' }, lazy = true },
  },
  cmd = {
    'DBUI',
    'DBUIToggle',
    'DBUIAddConnection',
    'DBUIFindBuffer',
  },
  init = function()
    -- Your DBUI configuration
    vim.g.db_ui_use_nerd_fonts = 1
  end,
}

Closing because I seemed to have fixed it by changing my config around.


Dubbed Audios

What feature do you want to add?
There is no hindi dubbed audio track for English movies like iron man Twilight etc.
Why do you want to have this feature?
I am Indian so I need this
Any other details to share?
No response

someday...


Viewer program

I could see this becoming the de-facto standard logging format for Slog, if a viewer program were to be provided alongside it. Perhaps one that simply reads from the JSON format, and outputs in the slog-term format, with some basic searching and date-time range capabilities. Is this in your plans?

I had no plans like this. JSON is so ubiquitous that there are multitude of tools to handle them. A viewing software would be potentially more work to write and maintain than slog itself.
If you do find something working for you, or plan to work on it, please let us know!

Okay, but there's the general JSON format, then the specific structure of Slog JSON log files... I think I may write a viewing tool myself. We'll see.

slog-json does not really define anything that goes into the json. It's entirely up to the user to define time format, logging severyty key and format and so on. There are some defaults, but they are mostly for users that don't really care. bunyan on the other hand is JSON + definition of key-values semantics.

So it’s just a thin wrapper over slog-stream really? I didn’t know that (had never actually used it, only judged from what you said about it). Fair enough!

On 1 Dec 2016, at 19:59, Dawid Ciężarkiewicz<EMAIL_ADDRESS>wrote:
slog-json does not really define anything that goes into the json. It's entirely up to the user to define time format, logging severyty key and format and so on. There are some defaults, but they are mostly for users that don't really care. bunyan on the other hand is JSON + definition of key-values semantics.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/slog-rs/json/issues/1#issuecomment-264277719, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEF3E47fV91Rt1zfwTP2IkGmFx9O4rtks5rDycOgaJpZM4LBzTJ.

slog-stream provides a Drain that takes something implementing Format and writes it to something implementing io::Writer.
slog-json uses serde serde-json) and uses it to implement Format for slog-stream with additional fields (key + value) given by user.


Add Iterative Merge Sort

I would like to contribute under GSSoC'23 the iterative version of merge sort
Please assign it to me

Please assign me this issue under GSSOC 23.i am intrested  in this issue.


Incompatible with laravel/scout ^5

This package does not work with laravel scout after version 4, where they changed the interface for the Laravel\Scout\Engines\Engine abstract class. I think the composer.json file should be updated to reflect this so it won't let you install it with incompatible peers.
You can see it was introduced in https://github.com/laravel/scout/commit/9f06b9c4d77879d53cf1680740b7f8bf19f78279
If you are willing, I would be able to provide a PR to add the conflict key to the composer to rectify this.

I have exactly the same issue:
Symfony\Component\Debug\Exception\FatalErrorException
Declaration of Basemkhirat\Elasticsearch\ScoutEngine::map($results, $model) must be compatible with Laravel\Scout\Engines\Engine::map(Laravel\Scout\Builder $builder, $results, $model)

Just now, i have the same probem, can anybody help us?

Seems like this might be unmaintained. I'm going to close this issue to clear out my own backlog


Common flow

Fixes #2366
Can we please cast a fine 👁 over this as there were some changes to code that I don't have full insight into.
I can't find a way to enforce flowing of content in common.
Could we be mindful of this in PRs that it's needed to have the whole codebase typed to get any benefit from it, and to stop having to do refactors like this which are a little dangerous.
It'd be good if someone could take a look at this too:
https://github.com/wellcometrust/wellcomecollection.org/pull/2344
As a note JSON+LD is not typed as I lost the will be then.

@davidpmccormick flow errors averted, all systems are go.


BUG

After selecting a novel in library then pressing back button doesn't deselect the selected novel instead it closes the app

That's not a bug but the expected behavior as it's the app is on the same initial screen.


Able to send Boost without the sufficient balance.

The Boost show in the channel but not idea how to see if transfer was done,
Most likely not.
Also in The Bitcoin Audionaut tribe, On Dec 19 and Jan 6th I boosted for 33333 and the top stats shows as Contributed :  6969 sats
TFTC tribe, 3 times 33333 total contributed 47k sat

Android boosting a podcast.

Android boosting a podcast.


Improve onExit command handler when exit command runs

onExit key on global schema is a shell script to execute like handler on exit command like docker-compose stop or anything you want to.
Pull request on fuge-config:
https://github.com/apparatus/fuge-config/pull/11
fuge_global:
  tail: false
  monitor: false
  monitor_excludes:
    - '**/node_modules/**'
    - '**/.git/**'
    - '**/*.log'
  onExit:
    docker-compose -f docker-compose.yml stop;

Nice one - thanks! I think that this could be generally useful. Couple of things before merge please:

On fuge-config could you change the setting to be on_exit to be consistent with the rest of the config file.

On fuge-config could you add a unit test for this setting - this could be just an update to an existing fixture just to ensure it is passed through correctly

on this repo (fuge) could you add a unit test for on_exit

Let me know if you need any help doing this! Will merge once these are in.
Cheers.


Added document similarity specific functionalities to postgresql.py

PR description
Added funtionalities retrieve and insert to document_similarity/microservice/library/postgresql.py.
Added a parameter language to the new_document_embedding method in document similarity microservice.
Root cause
Repeating code and missing parameters.
Solution description
Functionalities retrieve and insert replace the code that was frequently used to either retrieve values from the database or to insert them in it.
I added a language parameter to the method for updating the similarities table in the database (method new_document_embedding) and made the necessary changes to the index.html files in document_similarity microservice and entrypoint microservice.
Is this PR associated with an issue
Yes. Fixes #9

Sorry for not responding...
I found this block about the above SQL issue (https://www.psycopg.org/docs/usage.html#passing-parameters-to-sql-queries):
TL;DR. Only query values should be bound using %s. For a dynamic table name setting use the psycopg2 SQL module and the Identifier function.

Only query values should be bound via this method: it shouldn’t be used to merge table or field names to the query (Psycopg will try quoting the table name as a string value, generating invalid SQL). If you need to generate dynamically SQL queries (for instance choosing dynamically a table name) you can use the facilities provided by the psycopg2.sql module:

cur.execute("INSERT INTO %s VALUES (%s)", ('numbers', 10))  # WRONG
cur.execute(                                                # correct
...     SQL("INSERT INTO {} VALUES (%s)").format(Identifier('numbers')),
...     (10,))

@ErikNovak Thank you, this looks promising. I'll start working on it right away.

After a quick discussion with @ErikNovak, I decided to change the code so that it would be only applicable to postgres databases with architecture as ours. I couldn't find a way to make the proposed solution (link to comment) work.

After a quick discussion with @ErikNovak, I decided to change the code so that it would be only applicable to postgres databases with architecture as ours. I couldn't find a way to make the proposed solution (link to comment) work.


help wanted: playing a file into main thread in electron

I'm working with webtorrent on electron, after read the docs of how works electron I discovered that the play of file should works in main thread, beacuse if it runs in a html it will be asiciated with a renderer activity, and in change of renderer the play will be interrupted, but in API I can't find a way of do this. So my question is what method I should use to play a file in main thread?
Thanks for any response.
@feross

Creating a readStream and sending via ipc any new data looks goog option but see https://github.com/feross/webtorrent/issues/971


No support for new Android plugin system in 3.2.2?

I suspect that when I get this error it should be because of the incompatibility with the new build system of Android which is introduced in Godot 3.2.2:
AttributeError: 'SConsEnvironment' object has no attribute 'android_add_dependency':
File "D:\temp\godot-master\SConstruct", line 554:
config.configure(env)
File "modules/GodotFacebook\config.py", line 12:
env.android_add_dependency("implementation 'com.facebook.android:facebook-android-sdk:5.+'")
Please tell me that I am not right :) No compatibility with the 3.2.2's new Android plugin system?

Plugin updated and using now new plugin management system.


Add logging

We should add logging to:

[ ] DispatcherMiddleware
[ ] EndpointMiddleware
[ ] DispatcherBase + all subclasses
[ ] EndpointSelector + all subclasses

Take a stab at this and try to figure out the ideal things to log - use routing as an inspiration.

/cc @anurse - are there any changes in logging/diagnostics practices we should be aware of?

One the one, as referenced in various issues (https://github.com/aspnet/SignalR/issues/876 https://github.com/aspnet/Hosting/issues/1205 https://github.com/aspnet/Mvc/issues/6818): make sure that when you specify an Event ID, you use new EventId([number], "[name]") rather than just an int. Having names associated with the events makes it much easier to filter and avoids having to look up obscure ints. The names should be unique but only within a particular ILogger category.

That and: Log lots, use Trace if you're worried about logging too much :).

@rynowak Should the EndpointSelectorContext have a logger? Then HttpMethodEndpointSelector can use context.Logger inside the SelectAsync method. Is it correct to get that from DI here?

Should the EndpointSelectorContext have a logger?

No, we don't usually pass services this way. Let's discuss this at the meeting tomorrw


MHR crashes after 10 seconds without error

After installing dinput8.dll in the game folder and launching, the REFrameworks window appears and after about 10 seconds the game closes, leaving behind a hung process in the task manager.
re2_framework_log.txt

BTW, the game sometimes crashes itself with the same symptoms (hung process).

Should we expect support for pirated versions?


should remove --disable-encryption from THORIUM.BAT

the flag is rather annoying than it actually is helpful, because when the flag is on, every time you close the browser, every log-in reset, such as yt, github, fb, etc. The flag can be removed mannually by notepad or any editor, but I just want to let you know, because that may affect those who use "portable" mode without knowing how their log-in keep reset.
Note: The thorium version this post mentioned is m122 v3

@xdeadstokex Done!


Static files are at the wrong path if you have a publicPath option set.

This is related to the following issue: https://github.com/webpack/webpack-dev-server/issues/288
Basically, if we have a public path, I would expect your copyPublicFolder to copy it to dist/<publicPath> rather than just to dist. At the very least I would want an option to add this behavior.

Interesting, I'm wanting to move the copy task to webpack itself using copy-webpack-plugin.
This would expose the configuration and allow changes like that to happen.
Let me work on that now :)

Fixed in v2.2.0


Problem with duplicate books from NYT

Troubleshoot why the NYT list contains duplicates, should be 100 unique books.

Changing the list from all to combined-print-and-e-book-fiction resulted in the API returning 15 books and no duplicates where found.


Display all linked nodes as graph on map

As a user that needs to be able to visualize geospatial relationships as well as associative relationships, I would like to be able to toggle a switch in the configuration of the Map View plugin that enables the display of any nodes linked to nodes with geolocation information. This would provide a hybrid map + graph view: geolocated nodes are located on the map according to their coordinates (current functionality) and any nodes linked to them are displayed as a graph (default Obsidian graph functionality). Notes:

Nodes w/ geolocation information display as geo markers (current functionality)
Nodes w/o geolocation information display as circles (default Obsidian functionality)
Graph display could be controlled by standard Obsidian graph filter/forces/etc. configuration

Someone requested it in the past already so sounds like it's certain a desirable feature, but weighting so many other features I'd like to add, and currently only me working on this project, I'm afraid it will remain a low priority for now :(

A partial version of this (that only shows the map markers) is now in 5.0.0.


Datetime filter not working correctly

The Datetime filter on the GraphQL API currently ignores timezones. To solve this problem an issue was opened the Hot Chocolate Repository. As of 16.06.2021 a fix is scheduled for Version 12. Review the time zone filter client side, once this bug is fixed.

I have confirmed that the timezone is not taken into account when filtering DateTime-Elements.

Issue created ChilliCream/hotchocolate#3691

Issue still open


Add STMicroelectronics STM32H573I-DK model

Thank you for contributing to the IoT Plug and Play Models repository
:memo: Please review this checklist before submission

[X ] :eyes: The models submitted in this PR follow the DTDL Naming Guidelines for contributing to this repository.
[X ] 🕵I have validated the models locally using the dmr-client command line tool.
[X ] ❗ I understand once the PR is approved, the models are considered immutable: any edits will require to submit new files.
[ ] ✨ When creating a new top level dtmi:namespace, I have completed the PR Info Template below.

:zap: PR validation steps are described in the tools Wiki.
PR Info Template
When submitting models to the repository we ask that you provide as much of the following meta information around your models and related devices as possible. This info will be used to improve the IoT Plug and Play ecosystem.
👇: Please replace the markdown comment examples with your own values.
Company Info

Info identifying your company (if applicable).

Company name: STMicroelectronics
Company website: https://www.st.com
GitHub presence: https://github.com/STMicroelectronics

IoT Plug and Play Device Info

Info identifying your device.

Product website:  https://www.st.com/en/evaluation-tools/stm32h573i-dk.html
OS & Arch: Azure RTOS , ARM Cortex M33
SDK used for model implementation: https://github.com/Azure/azure-sdk-for-c

Model Submission Goals

Info related to broader submission goals.

Device certification
Presence in the Certified Device catalog
IoT Central integration

Code Owners & Reserved Names

Indicates GitHub alias entries to be added to the repo CODEOWNERS for the incoming model namespace. The codeowner is expected to be involved in subsequent DTDL model submissions against the same namespace.

GKNSTM
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact<EMAIL_ADDRESS>with any additional questions or comments.

Hi @GKNSTM
Wondering if you plan to agree with the CLA requirements, so we can move forward with this PR, otherwise can you close it.?

Hello @rido-min ,
We still don't have approval in company to sign CLA so I prefer to close this PR and re-submit the change when this topic is solved.
Guillaume.


Decide where to put the constant values for the leg dimensions

Need to centralize all the places where robot physical dimension information is stored, and do it in a way that's compatible with the modified source file structure that came out of issue 93

Based on the new file structure, we should handle physical dimension info as follows:
symbols that represent the actual dimensions should go in global_variables.cpp. This could be either run time variables, or compile time symbols, i.e. macros defined via #define. I favour doing both in global_variables.cpp: defining macros to represent the actual measurements, and defining the variables that are used at run time as well, as global variables.
The necessary run time variables are initialized, using combinations of the macros, in setup a routine, or routines, in configDetails.cpp. If these were only used by one function, or bag of functions, it might be reasonable to have the setup done there, but I don't think that's the case for physical dimensions, so configDetails.cpp is the best place.
I'll open a new ticket (done: 118)  to implement the handling of dimensions as described above.


PaDiM performance in README is wrong

Where do you get the PaDiM detection data in AUROC in the README table?
From the official paper, there are no provide detailed categories DET AUROC score but only provides DET AUROC total mean score with WR50_2 backbone (95.3) at most. How did you get an overall 97.5 in PaDiM paper performance in Anomaly Detection in README table?
I assume that you copy the wrong data into the README table from the paper, which you copy Localization AUROC into Image-level table and Localization AUPRO into Pixel level table.
Thanks

Hi! Thanks for verifying the data!
You are right. I'll adapt the table.


Makes graph nodes rounded

Users keep requested this feature and @djrm who promised this feature is dissappear. So, I've tried to accept all feedback from #17926 and make a new version. I did not add any new parameters to editor settings, and use Stylebox override to achive this result..

@toger5 Wow, your version looks much clear than mine.. Why you didnt PR it ?

also had to do (maybe it was just nice...) some calculation for the header hight so the text is always entered and you can make the header hight based on the margins of the style box.

I just leave it as default 24 * EDSCALE
Why need to change it ?

@Chaosus good question... I really don't know. Maybe there is a little bit missing or I had an additional idea which I really wanted to add to it. no-one knows... it's 10 month ago ;)
I'm really thankful you brought the whole idea back to live though.

I think you should copy the header hight and the offset stuff. you used a second dictionary for the header which is nice. it makes it easier to read than my "string combination thing".
It's funny that they are so similar ;)
I think I didn't even change the style though.it looks the same but allows for more advanced theme options.

do you want me to merge and rebase on current master? so you have an easier time comparing?

I still think this is not a good time for this, all the current theme is square (like it or not), i tried to add rounded corners to the whole theme, however it did not look that good because the 2d antialias 'sucks' (as pointed out by reduz), so this is on hold, i still plan to do some theme work for the next version.

@djrm Ah, thankfully you are alive !
@toger5 I dont know really, reduz said his "no" in irc and probably @djrm have the correct solution
Then I will close this

I like the round theme for graph nodes. It makes them feel more like they can be moved around, more "floaty" that the squared blocks. If we keep that only for nodes in graphs I do not think it is a problem.
Also, I think it's prettier ^^

@groud Should I reopen it ? I really dont know..

There is aa for styleboxes, and it rooks good enough.
I would not consider this as an arguement against the feature. The way it is implemented also should make it look okay when you zoom in.
Adding two styleboxes to graph nodes is with bo quedtion an improovement, also for ppl creating games. Otherwise graph node styles are quiet limited.
My proposal:
@Chaosus reopens and adds proper the auto header scaling + auto close button positioning. And you could split it knto two commits. One for the updated look and one for the additional graph node faerures.

Than we merge really quick and decide before 3.1 if the updated style gets reverted or not.

I also could do the rebase on my version.. it's more or less the same.(except the auto header height cacluation)

@toger5 I have some troubles with your version. You can add this auto height calculation after, if this PR is ever been merged, so I leave it opened as it is now.


Chore: fix terraform helm hooks

Fantastic! Great to see we replaced ~300 lines with 8!

all the credit is yours!


Build instructions

Added build instructions of BRUTAL in order to make easier for new contributors to get started !

<3


Fix issue of index creation when already exists in 260 to 310 migration

Purpose

Cannot create an index when it is already available and so this has to be checked before creating an index. This happens in apim 260-> 310 process, if the existing 210 setup had been migrated to 260 from a prior version earlier.

Below are the errors occurred in mysql.
ERROR 1061 (42000): Duplicate key name 'IDX_RID'
ERROR 1061 (42000): Duplicate key name 'IDX_USER'
ERROR 1061 (42000): Duplicate key name 'IDX_RS'
ERROR 1061 (42000): Duplicate key name 'IDX_PT'
Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

@rmsamitha , please send this fix to the master branch as well.


Use From for some lossless integer conversions

Thanks.
I thought clippy warns about these conversions...? How did you come up with the patch? (="Am I using clippy wrong?")

I think that clippy misses cases that involve bool or usize.


vmware: fix cpu reservation during vm scale

Description
Fixes #5706
Correctly set CPU reservation while scaling a dynamically scalable VM.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

Before fix (CPU reservation is set using offering's CPU speed for the VM after scaling even when global setting vmware.reserve.cpu is false):
> deploy virtualmachine zoneid=d295b42c-c67b-4224-9ea7-4777ce3e788e templateid=a9c03b25-4c1e-11ec-b0f8-1e006d000305 serviceofferingid=cdb3674b-aab0-4d75-a09f-a1ad48046bd6 networkids=4cf8b5b5-d2a9-475f-9bd4-5d872ce66c13 name=v1
{
  "virtualmachine": {
    "account": "admin",
    "affinitygroup": [],
    "cpunumber": 2,
    "cpuspeed": 1000,
    "created": "2021-11-23T08:37:28+0000",
    "details": {
      "cpuOvercommitRatio": "4.0",
      "dataDiskController": "osdefault",
      "memoryOvercommitRatio": "1.0",
      "rootDiskController": "ide"
    },
    "displayname": "v1",
    "displayvm": true,
    "domain": "ROOT",
    "domainid": "a9bbca90-4c1e-11ec-b0f8-1e006d000305",
    "guestosid": "a9c4b2bd-4c1e-11ec-b0f8-1e006d000305",
    "haenable": false,
    "hasannotations": false,
    "hostid": "22f5a5da-88dd-476b-97af-54b53d2a8040",
    "hostname": "<IP_ADDRESS>",
    "hypervisor": "VMware",
    "id": "1f3e742b-c220-4353-b80f-9328b9127128",
    "instancename": "i-2-12-VM",
    "isdynamicallyscalable": true,
    "jobid": "1d821c40-7165-447b-a20a-a78feacd404e",
    "jobstatus": 0,
    "lastupdated": "2021-11-23T08:37:40+0000",
    "memory": 1024,
    "name": "v1",
    "nic": [
      {
        "broadcasturi": "vlan://1871",
        "deviceid": "0",
        "extradhcpoption": [],
        "id": "14715db2-d9e8-4bed-bf47-00c6a118d5ad",
        "isdefault": true,
        "isolationuri": "vlan://1871",
        "macaddress": "02:00:5c:b6:00:0a",
        "networkid": "4cf8b5b5-d2a9-475f-9bd4-5d872ce66c13",
        "networkname": "L2-1",
        "secondaryip": [],
        "traffictype": "Guest",
        "type": "L2"
      }
    ],
    "osdisplayname": "CentOS 5.3 (64-bit)",
    "ostypeid": "a9c4b2bd-4c1e-11ec-b0f8-1e006d000305",
    "passwordenabled": false,
    "pooltype": "NetworkFilesystem",
    "receivedbytes": 0,
    "rootdeviceid": 0,
    "rootdevicetype": "ROOT",
    "securitygroup": [],
    "sentbytes": 0,
    "serviceofferingid": "cdb3674b-aab0-4d75-a09f-a1ad48046bd6",
    "serviceofferingname": "2vCPU1G",
    "state": "Running",
    "tags": [],
    "templatedisplaytext": "CentOS 5.3(64-bit) no GUI (vSphere)",
    "templateid": "a9c03b25-4c1e-11ec-b0f8-1e006d000305",
    "templatename": "CentOS 5.3(64-bit) no GUI (vSphere)",
    "userid": "c3206062-4c1e-11ec-b0f8-1e006d000305",
    "username": "admin",
    "zoneid": "d295b42c-c67b-4224-9ea7-4777ce3e788e",
    "zonename": "pr5700-t2575-vmware-65u2"
  }
}

> scale virtualmachine id=1f3e742b-c220-4353-b80f-9328b9127128 serviceofferingid=f57056ba-db2e-4801-b391-4d825a8eb221
{
  "virtualmachine": {
    "account": "admin",
    "affinitygroup": [],
    "cpunumber": 2,
    "cpuspeed": 1000,
    "cpuused": "NaN%",
    "created": "2021-11-23T08:37:28+0000",
    "details": {
      "cpuOvercommitRatio": "4.0",
      "dataDiskController": "osdefault",
      "memoryOvercommitRatio": "1.0",
      "rootDiskController": "ide"
    },
    "diskioread": 11,
    "diskiowrite": 0,
    "diskkbsread": 345,
    "diskkbswrite": 0,
    "displayname": "v1",
    "displayvm": true,
    "domain": "ROOT",
    "domainid": "a9bbca90-4c1e-11ec-b0f8-1e006d000305",
    "guestosid": "a9c4b2bd-4c1e-11ec-b0f8-1e006d000305",
    "haenable": false,
    "hasannotations": false,
    "hostid": "22f5a5da-88dd-476b-97af-54b53d2a8040",
    "hostname": "<IP_ADDRESS>",
    "hypervisor": "VMware",
    "id": "1f3e742b-c220-4353-b80f-9328b9127128",
    "instancename": "i-2-12-VM",
    "isdynamicallyscalable": true,
    "lastupdated": "2021-11-23T08:37:40+0000",
    "memory": 2048,
    "memoryintfreekbs": 0,
    "memorykbs": 1048576,
    "memorytargetkbs": 1048576,
    "name": "v1",
    "networkkbsread": 0,
    "networkkbswrite": 0,
    "nic": [
      {
        "broadcasturi": "vlan://1871",
        "deviceid": "0",
        "extradhcpoption": [],
        "id": "14715db2-d9e8-4bed-bf47-00c6a118d5ad",
        "isdefault": true,
        "isolationuri": "vlan://1871",
        "macaddress": "02:00:5c:b6:00:0a",
        "networkid": "4cf8b5b5-d2a9-475f-9bd4-5d872ce66c13",
        "networkname": "L2-1",
        "secondaryip": [],
        "traffictype": "Guest",
        "type": "L2"
      }
    ],
    "osdisplayname": "CentOS 5.3 (64-bit)",
    "ostypeid": "a9c4b2bd-4c1e-11ec-b0f8-1e006d000305",
    "passwordenabled": false,
    "pooltype": "NetworkFilesystem",
    "receivedbytes": 0,
    "rootdeviceid": 0,
    "rootdevicetype": "ROOT",
    "securitygroup": [],
    "sentbytes": 0,
    "serviceofferingid": "f57056ba-db2e-4801-b391-4d825a8eb221",
    "serviceofferingname": "2vCPU2G",
    "state": "Running",
    "tags": [],
    "templatedisplaytext": "CentOS 5.3(64-bit) no GUI (vSphere)",
    "templateid": "a9c03b25-4c1e-11ec-b0f8-1e006d000305",
    "templatename": "CentOS 5.3(64-bit) no GUI (vSphere)",
    "userid": "c3206062-4c1e-11ec-b0f8-1e006d000305",
    "username": "admin",
    "zoneid": "d295b42c-c67b-4224-9ea7-4777ce3e788e",
    "zonename": "pr5700-t2575-vmware-65u2"
  }
}

After fix (CPU reservation is set to 0 for the VM after scaling when global setting vmware.reserve.cpu is false):
> deploy virtualmachine zoneid=d295b42c-c67b-4224-9ea7-4777ce3e788e templateid=a9c03b25-4c1e-11ec-b0f8-1e006d000305 serviceofferingid=cdb3674b-aab0-4d75-a09f-a1ad48046bd6 networkids=4cf8b5b5-d2a9-475f-9bd4-5d872ce66c13 name=v2
{
  "virtualmachine": {
    "account": "admin",
    "affinitygroup": [],
    "cpunumber": 2,
    "cpuspeed": 1000,
    "created": "2021-11-23T08:59:53+0000",
    "details": {
      "cpuOvercommitRatio": "4.0",
      "dataDiskController": "osdefault",
      "memoryOvercommitRatio": "1.0",
      "rootDiskController": "ide"
    },
    "displayname": "v2",
    "displayvm": true,
    "domain": "ROOT",
    "domainid": "a9bbca90-4c1e-11ec-b0f8-1e006d000305",
    "guestosid": "a9c4b2bd-4c1e-11ec-b0f8-1e006d000305",
    "haenable": false,
    "hasannotations": false,
    "hostid": "8dc1aeec-49fa-4fe9-a176-098d754a3efb",
    "hostname": "<IP_ADDRESS>",
    "hypervisor": "VMware",
    "id": "693fb47f-84ee-4dd1-acc9-fe7477d3d6e6",
    "instancename": "i-2-13-VM",
    "isdynamicallyscalable": true,
    "jobid": "107b12ff-aad4-44a7-869a-78cab0291782",
    "jobstatus": 0,
    "lastupdated": "2021-11-23T09:00:06+0000",
    "memory": 1024,
    "name": "v2",
    "nic": [
      {
        "broadcasturi": "vlan://1871",
        "deviceid": "0",
        "extradhcpoption": [],
        "id": "5085808c-ad64-4cbf-b410-f65558efeeea",
        "isdefault": true,
        "isolationuri": "vlan://1871",
        "macaddress": "02:00:12:46:00:0b",
        "networkid": "4cf8b5b5-d2a9-475f-9bd4-5d872ce66c13",
        "networkname": "L2-1",
        "secondaryip": [],
        "traffictype": "Guest",
        "type": "L2"
      }
    ],
    "osdisplayname": "CentOS 5.3 (64-bit)",
    "ostypeid": "a9c4b2bd-4c1e-11ec-b0f8-1e006d000305",
    "passwordenabled": false,
    "pooltype": "NetworkFilesystem",
    "receivedbytes": 0,
    "rootdeviceid": 0,
    "rootdevicetype": "ROOT",
    "securitygroup": [],
    "sentbytes": 0,
    "serviceofferingid": "cdb3674b-aab0-4d75-a09f-a1ad48046bd6",
    "serviceofferingname": "2vCPU1G",
    "state": "Running",
    "tags": [],
    "templatedisplaytext": "CentOS 5.3(64-bit) no GUI (vSphere)",
    "templateid": "a9c03b25-4c1e-11ec-b0f8-1e006d000305",
    "templatename": "CentOS 5.3(64-bit) no GUI (vSphere)",
    "userid": "c3206062-4c1e-11ec-b0f8-1e006d000305",
    "username": "admin",
    "zoneid": "d295b42c-c67b-4224-9ea7-4777ce3e788e",
    "zonename": "pr5700-t2575-vmware-65u2"
  }
}

> scale virtualmachine id=693fb47f-84ee-4dd1-acc9-fe7477d3d6e6 serviceofferingid=f57056ba-db2e-4801-b391-4d825a8eb221
{
  "virtualmachine": {
    "account": "admin",
    "affinitygroup": [],
    "cpunumber": 2,
    "cpuspeed": 1000,
    "cpuused": "0%",
    "created": "2021-11-23T08:59:53+0000",
    "details": {
      "cpuOvercommitRatio": "4.0",
      "dataDiskController": "osdefault",
      "memoryOvercommitRatio": "1.0",
      "rootDiskController": "ide"
    },
    "diskioread": 0,
    "diskiowrite": 0,
    "diskkbsread": 11,
    "diskkbswrite": 0,
    "displayname": "v2",
    "displayvm": true,
    "domain": "ROOT",
    "domainid": "a9bbca90-4c1e-11ec-b0f8-1e006d000305",
    "guestosid": "a9c4b2bd-4c1e-11ec-b0f8-1e006d000305",
    "haenable": false,
    "hasannotations": false,
    "hostid": "8dc1aeec-49fa-4fe9-a176-098d754a3efb",
    "hostname": "<IP_ADDRESS>",
    "hypervisor": "VMware",
    "id": "693fb47f-84ee-4dd1-acc9-fe7477d3d6e6",
    "instancename": "i-2-13-VM",
    "isdynamicallyscalable": true,
    "lastupdated": "2021-11-23T09:00:06+0000",
    "memory": 2048,
    "memoryintfreekbs": 786432,
    "memorykbs": 1048576,
    "memorytargetkbs": 1048576,
    "name": "v2",
    "networkkbsread": 0,
    "networkkbswrite": 0,
    "nic": [
      {
        "broadcasturi": "vlan://1871",
        "deviceid": "0",
        "extradhcpoption": [],
        "id": "5085808c-ad64-4cbf-b410-f65558efeeea",
        "isdefault": true,
        "isolationuri": "vlan://1871",
        "macaddress": "02:00:12:46:00:0b",
        "networkid": "4cf8b5b5-d2a9-475f-9bd4-5d872ce66c13",
        "networkname": "L2-1",
        "secondaryip": [],
        "traffictype": "Guest",
        "type": "L2"
      }
    ],
    "osdisplayname": "CentOS 5.3 (64-bit)",
    "ostypeid": "a9c4b2bd-4c1e-11ec-b0f8-1e006d000305",
    "passwordenabled": false,
    "pooltype": "NetworkFilesystem",
    "receivedbytes": 0,
    "rootdeviceid": 0,
    "rootdevicetype": "ROOT",
    "securitygroup": [],
    "sentbytes": 0,
    "serviceofferingid": "f57056ba-db2e-4801-b391-4d825a8eb221",
    "serviceofferingname": "2vCPU2G",
    "state": "Running",
    "tags": [],
    "templatedisplaytext": "CentOS 5.3(64-bit) no GUI (vSphere)",
    "templateid": "a9c03b25-4c1e-11ec-b0f8-1e006d000305",
    "templatename": "CentOS 5.3(64-bit) no GUI (vSphere)",
    "userid": "c3206062-4c1e-11ec-b0f8-1e006d000305",
    "username": "admin",
    "zoneid": "d295b42c-c67b-4224-9ea7-4777ce3e788e",
    "zonename": "pr5700-t2575-vmware-65u2"
  }
}

@blueorangutan package

@shwstppr a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1765

@DaanHoogland updated summary for screenshots.
Before fix, ACS sets CPU reservation for the VM while scaling irrespective of the value of global setting - vmware.reserve.cpu. It should be set only when vmware.reserve.cpu is true. Also, it maybe wrong as it is not calculated the same way as it is done during VM deployment.
After fix, the same method is used for setting CPU reservation which is used during VM deployment.

@blueorangutan test centos7 vmware-65u2

@shwstppr a Trillian-Jenkins test job (centos7 mgmt + vmware-65u2) has been kicked to run smoke tests

Trillian Build Failed (tid-2579)

@blueorangutan help

@sureshanaparti I understand these words: "help", "hello", "thanks", "package", "test"
Test command usage: test [mgmt os] [hypervisor] [keepEnv]
Mgmt OS options: ['centos7', 'centos6', 'alma8', 'ubuntu18', 'suse15', 'ubuntu20', 'rocky8', 'centos8']
Hypervisor options: ['kvm-centos6', 'kvm-centos7', 'kvm-centos8', 'kvm-rocky8', 'kvm-alma8', 'kvm-ubuntu18', 'kvm-ubuntu20', 'kvm-suse15', 'vmware-55u3', 'vmware-60u2', 'vmware-65u2', 'vmware-67u3', 'vmware-70u1', 'xenserver-65sp1', 'xenserver-71', 'xenserver-74', 'xcpng74', 'xcpng76', 'xcpng80', 'xcpng81', 'xcpng82']
Note: when keepEnv is passed, you need to specify mgmt server os and hypervisor or use the matrix command.
Blessed contributors for kicking Trillian test jobs: ['rhtyd', 'nvazquez', 'PaulAngus', 'borisstoyanov', 'DaanHoogland', 'shwstppr', 'andrijapanicsb', 'Spaceman1984', 'Pearl1594', 'davidjumani', 'harikrishna-patnala', 'vladimirpetrov', 'sureshanaparti', 'weizhouapache', 'NuxRo']

@blueorangutan test centos7 vmware-67u3

@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests

Trillian test result (tid-2581)
Environment: vmware-67u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 36439 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5708-t2581-vmware-67u3.zip
Smoke tests completed. 89 look OK, 2 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_createPortablePublicIPAcquire
Error
0.04
test_portable_publicip.py

test_createPortablePublicIPRange
Error
0.02
test_portable_publicip.py

test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL
Failure
429.62
test_vpc_redundant.py

@blueorangutan package

@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1831

@blueorangutan test centos7 vmware-67u3

@blueorangutan package

@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1838

@blueorangutan test centos7 vmware-67u3

@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests

Trillian test result (tid-2623)
Environment: vmware-67u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 34009 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5708-t2623-vmware-67u3.zip
Smoke tests completed. 91 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

Trillian Build Failed (tid-2635)


Symbolic Link Shell Extension

Description
There is a shell extension for Windows 10/11 which adds a convenient way to create symbolic links: https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
Currently this extension does not work correctly in Files. The "Pick Link Source" context menu item never appears, and the "Drop Here" menu always produces an error. In Windows Explorer it works correctly.
Steps To Reproduce

Install Link Shell Extension as per instructions on website.
Open Files.
Right click any file or folder and navigate to shell extensions section.
(4. Interact with the "Drop Here" menu entry.)

Requirements

"Pick Link Source" should appear in context menu for files and folders
"Drop Here" should only appear in context menu for folders, and only if a source has been picked (neither currently the case in Files)

The following functionality should be provided by the shell extension once the two conditions above are met:

"Pick Link Source" should add a location to the shell extension's memory, whereupon "Drop Here" should allow creating symbolic links, hard links etc. at the destination. (By default this requires Admin privileges and should display the Admin prompt.)

Files Version
<IP_ADDRESS>
Windows Version
Edition	Windows 10 Pro Version	22H2 Installed on	13/07/2023 OS build	19045.3570 Experience	Windows Feature Experience Pack 1000.19052.1000.0
Log File
Attempting to use the Drop Here -> Symbolic Link context menu option (no link source could be picked, so idk what it is trying to drop):

There is nothing relevant in the log, presumably because this is an error thrown by the shell extension, not Files.

Thanks for the report, We're tracking this in #9991. You can check there or click subscribe in the right sidebar for updates.

https://github.com/files-community/Files/issues/13481#issue-1930765313


chore: Update java, kotlin & AGP from 7.0.3 to 8.0.1

Changes description

Context

Version
Previous
New

Java
11
17

Kotlin Gradle Plugin
1.5.31
1.8.21

AGP
7.0.3
8.0.1

Gradle wrapper
7.0.2
8.1.1

[x] Make sure you are requesting to pull a topic/feature/bugfix branch. Please, don't request directly from your main!
[x] Check commits & PR names matches our requested structure. It must follow the https://www.conventionalcommits.org pattern.
[x] Check your code additions will fail neither code linting checks.
[x] I have reviewed the submitted code.
[x] I have tested on a phone device/emulator.
[ ] I have tested on a tablet device/emulator.
[ ] I have tested on a large screen device/emulator.

Does this introduce a breaking change?

Yes
No

You can download the apk here :

You can download the apk here :

You can download the apk here :

You can download the apk here :
sample-debug.apk :
https://app.bitrise.io/app/62ac2962b2dd627a/build/62bea287-3143-46fa-b99a-65790310feea/artifact/184a8f7ccb26bc65/p/e5cb440d4d06a7ac4bf2d23fbc3b5886

You can download the apk here :
sample-debug.apk :
https://app.bitrise.io/app/62ac2962b2dd627a/build/650abfc2-b3b5-4f83-92c7-56d6dfef7dd0/artifact/a77bb2ee2740cefd/p/fccfe24ab34dc4136922c477ba3006d9


Global memory consolidation / optimization

We are using some seriously large buffers and a lot of book-keeping variables in the global space.
Can some of these be optimized, removed, made smaller?
Can we make better use of "unions" to "reclaim and reuse" space for some structures that are not needed concurrently?
Related:

BSS Section size tracking (#23)
Implement a Stack Canary (#16)

Some progress has been made on this.  In the course of refactoring the UI (#22), numerous globals have been reorganized and some unused ones removed.  We are actually being "reasonably" efficient so far.  I'd say there still remains some to do, but calling this a low priority issue for now.


Cross links edited

Updated cross-links for the Rollup Glossary

Hi @sthwnd, I noticed in the Client section, the link to Geth is pointing to #geth, is this correct? shouldn't it point to #geth-go-ethereum instead?


fix(telemetry): fix Span instanciation

This PR aims at fixing a compatibility problem with dd-trace (and possibly other opentelemetry providers), the library provided by Datadog to instrument nodejs apps.
dd-trace is now compatible with opentelemetry by default and makes collecting opentelemetry data in Datadog a breeze. However, it uses it's own Provider / Span... implementation which doesn't work with the current prisma:engine:* Span implementation.
As stated in this issue, engines spans don't show up in the instrumentation. prisma:client:* spans do appear though.
It seems to be linked to the fact that the current implementation instantiate an @opentelemetry/sdk-trace-base Span, which is not picked up by Datadog.
Instead, I suggest to let the tracer create the Span as it's the only one that knows which type of Span it expects.
With this change, prisma:egine:* spans do pop in Datadog.
Sidenotes:

I have absolutely 0 experience with opentelemetry. Make sure to review thoroughly, even if it's a small change :)
with versions >5.0 of @prisma/instrumentation, the code completely breaks the dd-trace integration, as instanciating an opentelemetry sdk-trace-base Span calls code that doesn't work with a dd-trace tracer. Dd-trace tracer doesn't implement the getSpanLimits  method as they don't use it. So their Span constructor doesn't have this parentTracer.getSpanLimits() call. See the error below

TypeError: parentTracer.getSpanLimits is not a function
at new Span (/app/node_modules/@opentelemetry/sdk-trace-base/build/src/Span.js:59:41)
at Ki.createEngineSpan (/app/node_modules/@prisma/client/runtime/library.js:123:1600)
at pr.logger (/app/node_modules/@prisma/client/runtime/library.js:114:1093)
at /app/node_modules/@prisma/instrumentation/dist/ActiveTracingHelper.js:59:20
at ActiveTracingHelper.createEngineSpan (/app/node_modules/@prisma/instrumentation/dist/ActiveTracingHelper.js:44:27)
at Array.forEach (<anonymous>)
at /app/node_modules/@prisma/client/runtime/library.js:114:850

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

I think the current implementation in this PR doesn't propagate correctly the engineSpan.parent_span_id as it takes the parentSpanId from the active context in tracer.startSpan().
I will look into that.

So the parent_span_id is fixed. But there is one last (big) difference with the previous code: previously the spanId was forced with spanId = engineSpan.spanId. Which is not doable with startSpan().
It's probably the reason the tests fail => The child - parent relationship must be broken at some point

Closing as this PR is getting old and the proposed solution is not optimal.
I reckon a better way to solve this problem would be to send Rust spans not only when they end, but when they start as well. So that the spans could be properly created in TS land, keeping the parent / child relationship.


Intermediate step for Running setup screen; show spinner

Remove the hint text for the selected bundle
Intermediate step for redesign of the Running setup screen

The actual implementation of the streaming JSON is more involved and something 'other' is needed


docs: Add links between GitHub repo and docs

As stated in the title,

Fix the broken link from README.md to the docs
Add a link from the docs to the GitHub repo

Close #15
Signed-off-by: Daniel Lim Wee Soong<EMAIL_ADDRESS>

Btw why isn't the readthedocs for this repo using the material theme like other symbiflow projects? If we use the material theme for this we can have the link to GitHub in the header like this

Btw why isn't the readthedocs for this repo using the material theme like other symbiflow projects? If we use the material theme for this we can have the link to GitHub in the header like this

Probably because nobody has gotten around to making this repo use the material theme :-). Want to create an issue and do the conversion?

Yes, especially that line is already there inside conf.py but commented out.
#html_theme = 'sphinx_materialdesign_theme'


Wrong Icons in Sources View

The Sources for Nintendo 3DS and Nintendo DS use the Origin Launcher icon instead of their own.

This issue extends to everywhere the icon is used, e.g. Source View, below the "total hours" graph as well as the session overview.
GameActivity is set to use its own icons, not the ones defined via Playnite.
Thank you in advance!

https://github.com/Lacro59/playnite-plugincommon/commit/e282b3e2ba9ca98ee0d16ecc09ab7e47994c04f9


Import stores with .csv

Hello, I want import my file with all my stores but i have very importants fields on my .csv. How can i add news fields on stockists?

You have to create new fields in the database and add them to the grid. search for a particular field and then add more like it where you see it mentioned.


cmake(feat): Add support for etc files with absolute paths in romfs CMake module

Summary
The current romfs cmake method only supports adding relative paths to the etc path.
# etc/ must be in the relative path of the current script directory
list(APPEND RCSRCS etc/init.d/rcS etc/init.d/rc.sysinit)
list(APPEND RCRAWS etc/media/media.conf)
  nuttx_add_romfs(
    NAME
    etc
    MOUNTPOINT
    etc
    RCSRCS
    ${RCSRCS}
    RCRAWS
    ${RCRAWS}
    PATH
    ${CMAKE_CURRENT_BINARY_DIR}/etc)

This patch supports adding romfs files with absolute paths at any location.
Because different boards on the same chip platform may have common board-level configurations, a common romfs file needs to be added
Usage after this patch:
# in any CMakeLists.txt we can call
  add_board_rcsrcs(${CMAKE_CURRENT_SOURCE_DIR}/etc/build.prop)
  add_board_rcraws(${CMAKE_CURRENT_SOURCE_DIR}/etc/video_config.json)

# also compatible and supports the original call
# in board src CMakeLists.txt

  nuttx_add_romfs(
    NAME
    etc
    MOUNTPOINT
    etc
    RCSRCS
    etc/srcfile
    RCRAWS
    etc/rawfile
    PATH
    ${CMAKE_CURRENT_BINARY_DIR}/etc)

# The final romfs is a collection of all files

Impact
Forward compatibility
Testing
CI

[Experimental Bot, please feedback here]
The PR appears to satisfy the NuttX requirements.
Here's a breakdown based on your provided information:

Summary:  You clearly explain the problem (romfs only supporting relative paths limiting flexibility), the solution (supporting absolute paths), and provide code examples for both old and new usage.  This is well done!
Impact:

Forward Compatibility: Excellent! You directly call out the impact and how it improves the build system.
Other Impacts: While you don't explicitly say "NO" to other impacts, the assumption is that this is purely a build system improvement with no user-facing changes. It's a good practice to explicitly state "NO" for clarity.

Testing:

CI:  Relying on CI is good, but you should ideally provide some specific test scenarios in your local setup as well. Mention which CI environments (if there are multiple) will cover this change.
Logs:  Even with CI, include snippets showing the difference in the generated romfs content or build output before/after your change. This gives reviewers concrete evidence that the change works.

Recommendations for Improvement

Impact:  For completeness, add "NO" to the other impact categories (user, build process, hardware, documentation, security, backward compatibility).
Testing:

Be more specific about your local setup (OS, compiler, target board/architecture).
Include brief log snippets demonstrating the change in romfs content or build output.

Overall:  Your PR description is well-structured and informative.  Adding the minor improvements mentioned above will make it even stronger.

[Experimental Bot, please feedback here]
The PR appears to satisfy the NuttX requirements.
Here's a breakdown based on your provided information:

@lupyuen This is so cool!!!!!

Thank you so much! Check out my new article this weekend, all about our PR Review Bot :-)


Bump Abacus to get resource specific report. Adopt broker smoke test

Coverage remained the same at 89.109% when pulling 428d5aadddcc68914cec1f231559e3212b6b6b19 on SAP:specific-report into cd5a29fd8eb538e25314f87f7d9a381f9c29c401 on cloudfoundry-incubator:master.


[BUG] - ver command not working - pad.m - Anushree Bose

Describe the bug
The ver command in Matlab 2024b is not working anymore because of a naming conflict in the pad.m function.
Computer configuration (please complete the following information):

MATLAB version [e.g. 2024b]

Additional context
MRSHub post (https://forum.mrshub.org/t/unable-to-launch-osprey-2-8-gui-pad-function-error-osprey-overview-error/2139)

Solved in #786


Prevent kernel death on introspection.

I have updated the code relating to introspection so that it now respects the messaging spec v5.0.
Still, there is no tooltip shown on the frontend, even though I was able to confirm (using Debug.Trace) that the message produced by toJSON (from IHaskell.IPython.Message.Writer) had proper structure.
I searched the ipython repository for keyword tooltip, and it seems like it is implemented in IPython but not in jupyter. We might have to implement custom tooltips for IHaskell.
This will be required for #347.

More details
For an example cell,
sin pi

Tracing toJSON for PublishDisplayData, we get:
{
    "data": {
        "text/plain": "1.2246467991473532e-16"
    },
    "metadata": {},
    "source": "haskell"
}

Tracing toJSON for InspectReply, with inspection on pi gives:
{
    "status": "ok",
    "data": {
        "text/html": "
Type: forall a. Floating a => a
",
        "text/plain": "forall a. Floating a => a"
    },
    "metadata": {}
}

According to the spec, the data should be a mime-bundle similar to display_data, which it is as seen above.

@gibiansky  The ipython devs (@Carreau) on gitter told me that just sending a inspect_reply message should work. I have done that but I think I'm missing something. Can you take a look?
Also, introspection on the master branch causes the kernel to die. With this code, it doesn't. This seems to be a step in the right direction.

Alright, will do!

To be more clear it should work on shift-tab, otherwise the handler won't know where to put the message.
Can be changed though.
Sent from my iPhone

On 4 avr. 2015, at 23:23, Sumit Sahrawat<EMAIL_ADDRESS>wrote:
@gibiansky The ipython devs (@Carreau) on gitter told me that just sending a inspect_reply message should work. I have done that but I think I'm missing something. Can you take a look?
Also, introspection on the master branch causes the kernel to die. With this code, it doesn't. This seems to be a step in the right direction.
—
Reply to this email directly or view it on GitHub.

You mean to say that if the inspect_reply is sent without first receiving a inspect_request (sent by a shift-tab), the tooltip would not show, right?
Currently, my code doesn't work even on shift-tab, and I have been unable to find a reason for it.
Thanks for the help.

What's the state of this PR?  Specifically:

What exactly does it enable?
Is it ready to merge?
If not, what still needs to be done to get it merge-ready?

What exactly does it enable?

Currently, this receives the input (whole cell text + cursor position), finds the word at that position (no proper lexing), and prints a lot of info, including the proper types in the console if kernelDebug = True. I also implemented proper replies, but the tooltip doesn't show for some unknown reason.

Is it ready to merge?

Not yet.

If not, what still needs to be done to get it merge-ready?

Proper lexing needs to be done, most probably using the GHC API.
The tooltip has to appear.

I tried tracing the incoming-outgoing json messages and nothing looks fishy. I also changed replyTo to send a fixed reply, ignoring the contents of the request and yet it didn't work.

I've edited the PR so that it prevents kernel death on introspection. The tooltip still does not show, but this can be merged as it stands.

Perfect. I will investigate and merge today

Having a strange issue on travis. ./build.sh ihaskell works for me (GHC 7.10.1). Travis shows an error in a very unexpected place.

The build failures were unrelated I believe to this PR. Some of them may have been fixed in this one which I just merged (I did not realize it was ready to merge). There may also have been some changes to classy-prelude which are breaking things, but I got things to build fine; I'll investigate travis issues separately from this PR.
Can I go ahead and merge this, then?

You can go ahead and merge this. I don't have anything else I can add.
You could also try restarting the build, now that #488 has been merged.

@sumitsahrawat It turned out that you needed a found key to be true in order for the tooltip to display. This was completely undocumented (although about a week ago there was an ipython PR to document this, but the documentation has not yet appeared in the messaging spec online in HTML form). Once you added a found key everything displayed and your PR worked.


Create blob in storage account via Bicep and put in a container registry

not working, need to create an issue at bicep project


Warning: syntax error, unexpected BOOL_TRUE

I have an ini file that looks like this:
[general]
...
yes = "Yes"
no = "No"

When I reload my page, there is this error:
Warning: syntax error, unexpected BOOL_TRUE in .../i18n/lang/lang_en.ini on line 11 in .../i18n/I18n.php on line 304

Warning: Invalid argument supplied for foreach() in ..../i18n/I18n.php on line 324

This /lang/lang_en.ini on line 11 points to the line yes = "Yes"
Not sure why it is considering "yes" as a boolean value and why that is invalid here.

Apparently PHP's .ini parser doesn't allow some keywords in keys: https://www.php.net/manual/en/function.parse-ini-file.php.
I haven't been able to find out how to fix that, and had no success with scanner_mode.


Mention syntax for multi-line footnote text and named footnotes

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes
What part(s) of the article would you like to see updated?
There are currently two main issues regarding the above linked docs entry about the footnotes syntax:

They only mention and show an example for a single-line footnote comment.
They only mention and show the numbered footnotes syntax.

The footnotes syntax does support both multi-line comments and named footnotes but both are not mentioned anywhere in those docs and the only proof of their existence is the Preview-gif on the Changelog about footnotes
The docs should be updated to include info regarding how you can make multi-line comments and how footnotes don't have to be pure numbers but can also be text.
Here is a quick mockup of how this could look like:
## Footnotes

You can add footnotes to your content by using this bracket syntax:

```
Here is simple footnote[^1].

[^1]: My reference.
```

The footnote will render like this:

![Rendered footnote](/assets/images/site/rendered-footnote.png)

Footnotes can also be named or you can use multiple lines for the reference by using two spaces in front of each new line:

```
Here is an advanced footnote[^note].

[^note]: Comments in references can be on multiple lines.
  All you have to do is add two spaces in front of it.
```

The output would render like this:

![Rendered advanced footnote](/assets/images/site/rendered-advanced-footnote.png)

Additional information
Maybe it could be a good idea to also mention the second (and imo better) syntax for multi-line text usable, which is to keep the first line after the [^n]: empty and start each other line with four spaces:
[^1]:
    Multi-line footnote text.
    This syntax is supported too!

I've tested the above syntax and a proof-of-concept is below.[^proof].
[^proof]:
Multi-line footnote text.
This syntax is supported too!

Sounds great! You or anyone else is welcome to create a PR doing just that. ⚡

Sounds great! You or anyone else is welcome to create a PR doing just that. ⚡

I can work on something for it. Just need to figure out how to make it in terms of images.


Can't play Roblox VR

When the Oculus app and SteamVR are open, and my Oculus/Meta Quest 2 is ready for play, it shows the VR place loading model, but launches to the normal screen mode. I am using OculusKiller and i don't know if this issue exists while using the normal app.

OpenGL

first, why are you using opengl, second, vr only works on directx


Removed weavework-scope url from the doc

Description
Since Weavework has been closed (#45482) its URL mentioned  has been removed from docs.
Issue: #47421

Related Page -> https://kubernetes.io/docs/concepts/cluster-administration/addons/

@divya-mohan0209 @nate-double-u, raised the PR PTAL.

It also resolves English page from the issue #47441.

I can only give you an informal lgtm, but good catch!

Thanks for this @utkarsh-singh1
/remove-lifecycle stale
/lgtm


Pkg 4462 v12.3 initial

Destination channel: defaults
Links

PKG-4462

Explanation of changes:

Part of CUDA 12.x build, following conda-forge's pattern which was developed in conjunction with Nvidia. There isn't a need to stage these then release them all at once. They won't cause a problem released one at a time.
Please check the main branch too, this has just been forked
Uploads to private anaconda.org channel because we don't have the license agreement for many of the packages in this buildout, including upstreams.
Changes made to adjust feedstocks for differences between conda-forge and defaults. Please see commit messages for description of changes.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_3f8gbnq522/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:192: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:64: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.

===== ERRORS =====

clone/recipe/meta.yaml:192: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:50: outputs_not_unique: output "libcusolver": Output name is not unique
clone/recipe/meta.yaml:1: missing_tests: output "libcusolver": No tests were found.
clone/recipe/meta.yaml:192: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
4 Errors and 7 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_6b4ernuiwl/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:64: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:192: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:192: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:1: missing_tests: output "libcusolver": No tests were found.
clone/recipe/meta.yaml:192: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:50: outputs_not_unique: output "libcusolver": Output name is not unique
===== Final Report: =====
4 Errors and 7 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_2cbrp9ji69/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:192: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:64: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:192: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:1: missing_tests: output "libcusolver": No tests were found.
clone/recipe/meta.yaml:192: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:50: outputs_not_unique: output "libcusolver": Output name is not unique
===== Final Report: =====
4 Errors and 7 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_a3utcx0tqs/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:64: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:192: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:50: outputs_not_unique: output "libcusolver": Output name is not unique
clone/recipe/meta.yaml:1: missing_tests: output "libcusolver": No tests were found.
clone/recipe/meta.yaml:192: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:192: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
4 Errors and 7 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_27is_v3ivj/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:192: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:64: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:192: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:1: missing_tests: output "libcusolver": No tests were found.
clone/recipe/meta.yaml:50: outputs_not_unique: output "libcusolver": Output name is not unique
clone/recipe/meta.yaml:192: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
4 Errors and 7 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_f7nbenn0dz/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:64: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:192: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:50: outputs_not_unique: output "libcusolver": Output name is not unique
clone/recipe/meta.yaml:192: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:192: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:1: missing_tests: output "libcusolver": No tests were found.
===== Final Report: =====
4 Errors and 7 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_fe9pnot7zn/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:64: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:192: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:192: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:50: outputs_not_unique: output "libcusolver": Output name is not unique
clone/recipe/meta.yaml:192: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:1: missing_tests: output "libcusolver": No tests were found.
===== Final Report: =====
4 Errors and 7 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_2821rvu65t/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:64: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:192: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:1: missing_tests: output "libcusolver": No tests were found.
clone/recipe/meta.yaml:192: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:50: outputs_not_unique: output "libcusolver": Output name is not unique
clone/recipe/meta.yaml:192: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
4 Errors and 7 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_aa1gsjl9hu/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:64: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:192: license_file_overspecified: Using license_file and license_url is overspecified.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "libcusolver-static": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: output "libcusolver": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:50: outputs_not_unique: output "libcusolver": Output name is not unique
clone/recipe/meta.yaml:192: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:1: missing_tests: output "libcusolver": No tests were found.
clone/recipe/meta.yaml:192: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
4 Errors and 7 Warnings were found