[Feature Request]: The ability to keep the screen on when it's full screen

Choose the extension for feature request.
Full Screen Mode
📝 Provide a description of the new feature
I'm really enjoying your extension! I usually wash dishes and do other things while listening to Spotify, but since I got to know your extension, I've tried to use your full screen mode and keep the screen on. However, the screen automatically turned off after about a minute, just as the normal Windows. I know I can adjust the screen off time in the window settings, of course, but I don't want to, because that's going to apply to all other programs as well. What I want is just for the spotify full screen, the screen keeps turned on just like when a video is playing in windows.
➕ Additional Information
No response

I looked into it, it is possible using the wakelock api, but not sure when I'll get the time to implement it into the extension, have been a little busy.
Till then @korjnghyn you can try out @SIMULATAN solution.


Allow testing with istio enabled

This will allow start testing eventing-istio by using the existing
eventing test suite.
Signed-off-by: Pierangelo Di Pilato<EMAIL_ADDRESS>

/cc @creydr

/cc @matzew

/cherry-pick release-1.9

/cherry-pick release-1.8

/cherry-pick release-1.7

@matzew updated, thanks!

/unhold


Reorder steps in deprovisioning

Description
Deleting Kyma resource should be executed after AVS, EDP, IAS unregistrations
Changes proposed in this pull request:

Delete Kyma resource (and check if it is deleted) moved after AVS, EDP and IAS unregistration steps

Related issue(s)

/hołd

/hold

/unhold


⚠ Samsung has degraded performance

In 70cf270, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 3307 ms

Resolved: Samsung performance has improved in 1566459.


glyphicons-halflings-regular.woff2 Line 1: Unexpected token ILLEGAL

When I tried this example, I received the following error:
ERROR in ./~/bootstrap/fonts/glyphicons-halflings-regular.woff2
Module parse failed: /Users/pdrummond/src/bootstrap-webpack-example/node_modules/bootstrap/fonts/glyphicons-halflings-regular.woff2 Line 1: Unexpected token ILLEGAL
You may need an appropriate loader to handle this file type.
(Source code omitted for this binary file)
 @ ./~/bootstrap-webpack/~/css-loader!./~/bootstrap-webpack/~/less-loader!./~/bootstrap-webpack/bootstrap-styles.loader.js!./bootstrap.config.js 2:56882-56943

I am new to webpack so I'm not sure what's happening here but if I add the following to webpack-config.js, the error goes away and it all seems to work as expected:
{ test: /\.woff2(\?v=\d+\.\d+\.\d+)?$/, loader: "url?limit=10000&minetype=application/font-woff" },

This is simply a copy of the woff loader entry but for woff2.

MIME type for woff2 fonts is application/font-woff2 and not application/font-woff

It would be nice to have a more informative error.


improve GPU node startup/join time on autoscale

Currently we measure node startup time to be around 10 minutes from the cluster autoscaler triggers adding a new GPU node.
Would like to find a way to improve this time.  e.g. pre-compiling the kernel module and storing it in a container image instead of recompiling every time.

It should be possible to cache the driver artifacts so that the installer DaemonSet only has to copy them rather than build from source every time. This would reduce the node startup time by several minutes.
Proposal:

Use Cloud Build to run Packer with a COS instance image and an attached GPU. Example of using packer from Cloud Build. Note that the COS image used should follow the image that is used by GKE. For example, the /etc/os-release file on a GKE 1.14 node shows VERSION_ID=73 so the cos-73-lts image family should work. I think GKE 1.15 uses cos-77-lts. TODO: find a better way to track this.
Use a Packer provisioner script to run the modified webrtc driver installer script in the original init container image, or one like it. Note that the image used is cos-nvidia-installer:fixed, which is pre-loaded in to the GKE node image so it's never pulled. The Dockerfile is here and will have to be built separately as a Cloud Build step before running Packer.
The Packer provisioner creates a tar.gz archive of the /home/kubernetes/bin/nvidia directory created inside the driver installer container and copies it to GCS.
The Cloud Build can be run daily with Cloud Scheduler to keep driver in sync with the COS release channel. Example of invoking cloud build with scheduler
Create new entrypoint script for the driver installer init container that extracts the driver and libs from GCS to the node and runs the modprobe to install the kernel modules.

I'm open to other ways of implementing this too, for example, packer could also build push and image with the artifacts to GCR. Sometimes GCR is a little cleaner than GCS when it comes to bucket management and ability to tag images.

There is a problem with the packer approach using COS specifically that I'll try to detail here:

gpu driver signature is no longer available from the cos-tools gcs bucket
COS kernel boots with kernel module signature verification on.  as part of the installer script, if it cannot find the driver keypair to sign the kernel module, it will attempt to disable this requirement and reboot the VM.
as the VM reboots, packer dies and fails the build

The reason we don't see this with the original approach with the daemonset (and possibly the reason why it works from inside GKE, but it takes the node so long to join) is that the node reboots and comes back with the driver signature verification turned off, and the daemonset starts the install script over again.  The second time we run the kernel module build script, we can build and load the unsigned kernel module.  I'm estimating node reboots and rejoins to GKE take probably around 3-4 minutes.
There's a couple of approaches i can think of here:

ask the COS team to publish driver signature keys so we can sign the kernel module.
use Ubuntu nodes for GPU nodepools in GKE, which presumably can load unsigned kernel modules, but at the expense of some of the COS container-centric security features like read-only filesystem by default, etc


Angular 1.5 support

I've been using this with angular 1.5 with no issues. Can you please bump the bower allowed version to <2.0

Bower's semver parsing is wrong FYI #42

Thanks, I didn't notice that.


feat(proxySupport): Add ability to set proxy settings

Currently only supports http proxies...

Pull Request Test Coverage Report for Build #65

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.6%) to 93.309%

Files with Coverage Reduction
New Missed Lines
%

file:/home/runner/work/armory-observability-plugin/armory-observability-plugin/common/src/main/java/io/armory/plugin/observability/model/PluginMetricsNewRelicConfig.java
1
93.33%

file:/home/runner/work/armory-observability-plugin/armory-observability-plugin/common/src/main/java/io/armory/plugin/observability/newrelic/NewRelicRegistrySupplier.java
1
95.0%

Totals

Change from base Build #64:
-0.6%

Covered Lines:
251

Relevant Lines:
269

💛  - Coveralls


Add cwd to createTerminal

Couldn't find that elsewhere: Add a parameter to createTerminal to specify the root folder or more generally the current working directory.

@chrmarti
Am I correct you mean a new optional parameter cwd to the extension API
@Tyriar - I am overdue to help with some terminal stuff, I can add to my November Q...
createTerminal(nameOrOptions: vscode.TerminalOptions | string, shellPath?: string, shellArgs?: string[]): vscode.Terminal {
if (typeof nameOrOptions === 'object') {
return extHostTerminalService.createTerminalFromOptions(<vscode.TerminalOptions>nameOrOptions);
}
return extHostTerminalService.createTerminal(nameOrOptions, shellPath, shellArgs);
},

@cleidigh Correct, that would allow for opening the shell in any of the workspace folders and also any other folder where that makes sense.

@cleidigh yeah, just adding it to the TerminalOptions prototype, not the other one though (which already has enough params).

@Tyriar
Not sure what you mean by the "other one", but I think you do mean to alter ITerminalOptions
in vscode.d.ts  : I have never touched this file before, I assume it's sort of a base file?
export interface TerminalOptions {
/**
* A human-readable string which will be used to represent the terminal in the UI.
*/
name?: string;
	/**
	 * A path to a custom shell executable to be used in the terminal.
	 */
	shellPath?: string;

	/**
	 * Args for the custom shell executable, this does not work on Windows (see #8429)
	 */
	shellArgs?: string[];
	/**
	 * Object with environment variables that will be added to the VS Code process.
	 */
	env?: { [key: string]: string | null };
}

@cleidigh I mean keep the API prototype like this and modify vscode.TerminalOptions:
createTerminal(nameOrOptions: vscode.TerminalOptions | string, shellPath?: string, shellArgs?: string[]): vscode.Terminal

Not like this:
createTerminal(nameOrOptions: vscode.TerminalOptions | string, shellPath?: string, shellArgs?: string[], env?: ...): vscode.Terminal

Addressed with PR #38132

Fixed in https://github.com/Microsoft/vscode/pull/38132


Pipelines definitions not getting created - The remote server returned an error: (403) Forbidden.

Recently our pipelines have stopped getting created when we create new solutions and DevOps Projects. I have traced back the error to the line below and get a 'The remote server returned an error: (403) Forbidden' error in the output.
https://github.com/microsoft/coe-alm-accelerator-templates/blob/afbdbb6c926e320b17171a6ca15fa78aa2bc9143/PowerShell/branch-pipeline-policy.ps1#L473
We have used ALM Accelerator for some time now and have not run into this until recently. Any ideas as to what may be causing this?

I'm also facing the same issue. Deploy pipelines are not getting created. When I looks at the jobs run log it says 'An exception occurred: The remote server returned an error: (403) Forbidden'. How do we get power cat team to address this issue?

@mbuckman10  - Were you able to resolve this issue?

This is a permissions issue related to the Build Service. Double check the permissions listed below.
https://learn.microsoft.com/en-us/power-platform/guidance/alm-accelerator/setup-components-manually#set-permissions-for-the-project-build-service
Also, there's some additional configuration required based on security updates in Azure DevOps from earlier this year.
https://github.com/microsoft/coe-starter-kit/issues/7930#issuecomment-2024283993

@mikefactorial - Hi Mike, I've checked all the permissions and it looks good. This was working few months ago (July 2024) when I first set up the ALM accelerator. The commit from ALM Accelerator canvas app would create pipeline and deploy. But now pipelines are not getting created for any new solution, but the the old pipelines that were created in July is still functioning. Please help.

Hello,
I have exactly the same issue.
I have setup permissions has described in different posts and it doesn't work anymore.
The issue appears when I use a dedicated project for pipeline templates.
Should I have to configure specific permissions on the pipeline templates project ?
Thanks in advance for your help.
PS : By the way, are you planning to relaese a new version of the ALM Accelerator ?

I have found a solution by setting up permissions for the user "Project Collection Build Service (Your Organization Name)" too in the Pipelines security page :
Go to Pipelines -> Manage Security -> select the "Project Collection Build Service (Your Organization Name)" user -> Allow :

Administer build permissions
Create buil pipeline
Edit build pipeline
Queue builds

Hope it will help ...

I have all these permissions set up in my pipelines security. The current pipelines that was created few months ago for old solutions are still working. The new pipelines are not getting created for new solutions. The issue is new pipelines are not getting created for new solutions in the repository.
Looks like Power Cat team is not actively supporting these issues. Probably need to stop using ALM Accelerator and use DevOps pipelines directly instead.

Maybe this can be addressed when ALM Acclerator app i creating an ADO project with wizard to set up correct permission. Currently this needs to be set up manually regerdless manual or wizard based ADO project creation.


Accuracy of the SiLU op is incorrect

I found that the accuracy of the mirage graph generated by the gated_mlp example is completely mismatched. After testing, I found that the accuracy of the silu op could not be aligned. The reproduction code is:
import mirage as mi
import torch

if __name__ == "__main__":
    graph = mi.new_kernel_graph()
    X = graph.new_input(dims=(8, 4096), dtype=mi.float16)
    O = graph.silu(X)

    input_tensors = [
        torch.randn(8, 4096, dtype=torch.float16, device='cuda:0'),
    ]

    outputs = graph(inputs=input_tensors, outputs=[O])

    # ========= Correctness check =========
    silu = torch.nn.SiLU()
    output0_correct = silu(input_tensors[0])

    print('mirage output[0]:', outputs[0], sep='\n')
    print()
    print('correct output[0]:', output0_correct, sep='\n')

    # check the correctness of the output tensors
    print('Correctness of output[0]:', torch.allclose(outputs[0], output0_correct, atol=1e-3))

My result shows:
mirage output[0]:
tensor([[-0.0649,  0.2749,  0.1782,  ..., -0.0425, -1.0791, -0.5083],
        [-0.2474, -0.9648, -2.0488,  ...,  0.2686, -0.0774,  0.2732],
        [-1.1436,  0.2286,  0.2664,  ..., -0.1858,  0.2676, -0.8286],
        ...,
        [ 0.1395,  0.1825, -1.2383,  ...,  0.2644,  0.2130,  0.1720],
        [-0.6152,  0.2764,  0.2761,  ...,  0.2688,  0.1360,  0.1368],
        [-0.3640,  0.2686,  0.2167,  ...,  0.2749,  0.2336, -0.7979]],
       device='cuda:0', dtype=torch.float16)

correct output[0]:
tensor([[-0.0574,  1.1934,  0.2827,  ..., -0.0392, -0.2778, -0.2404],
        [-0.1639, -0.2783, -0.2134,  ...,  1.3369, -0.0670,  1.2344],
        [-0.2764,  0.4514,  0.6997,  ..., -0.1348,  1.3545, -0.2749],
        ...,
        [ 0.1949,  0.2939, -0.2732,  ...,  0.6792,  2.0527,  0.2666],
        [-0.2571,  1.1455,  1.1553,  ...,  1.3330,  0.1880,  0.1896],
        [-0.2058,  0.7256,  0.4023,  ...,  1.1934,  0.4744, -0.2734]],
       device='cuda:0', dtype=torch.float16)
Correctness of output[0]: False

The values are completely misaligned.

Thanks for pointing out the issue @zk1998 !

The issue should have been fixed by #100.


Is this support matrix correct?

I try to generate migration project the offline from RDS SQL to Azure DB, but the offline migration doesn't appear.
Is this support matrix correct?

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

ID: 8c8dc618-bff7-b1aa-be2c-b6b933f75545
Version Independent ID: 9a608dd8-d781-eb4a-c796-34f758f0d58a
Content: Database migration scenario status
Content Source: articles/dms/resource-scenario-status.md
Service: dms
GitHub Login: @HJToland3
Microsoft Alias: jtoland

Thanks for the question! We are investigating and will update you shortly.

@yuharucan Can you please walk through this Quickstart: Create an instance of the Azure Database Migration Service by using the Azure portal. You are seeking an offline migration for RDS SQL -> Azure SQL Database.
What I do see is a tutorial for an online migration: Tutorial: Migrate RDS SQL Server to Azure SQL Database or an Azure SQL Database managed instance online using DMS
The documentation is stating that the RDS SQL -> Azure SQL Database migration is only available offline, yet there is a tutorial written for online (mode).

@yuharucan - I have updated the table to reflect current status. The changes will go live tomorrow.  Offline migration of RDS SQL Server to Azure SQL Database or an Azure SQL Database managed instance using DMS is not currently supported.  Thanks!

@yuharucan We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Instructions for AOVPN include depricated call in the powershell

The instructions in the documentation specifies using Gwmi which is not available in pwsh 7.  It has been changed to Get-CimInstance

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

ID: 77e14da1-102d-3ddf-e2a1-a20ce533b95a
Version Independent ID: 374edc4c-f527-b7b7-c291-353928b97d8d
Content: Configure Windows 10 Client Always On VPN Connections
Content Source: WindowsServerDocs/remote/remote-access/vpn/always-on-vpn/deploy/vpn-deploy-client-vpn-connections.md
Product: windows-server
Technology: networking-ras
GitHub Login: @Teresa-Motiv
Microsoft Alias: v-tea

#please-close Fixed in: https://github.com/MicrosoftDocs/windowsserverdocs-pr/pull/3398


Build fails on RPi3

Building on RPi3 (freshly built, with functioning pico sdk etc.) build fails:
Scanning dependencies of target elf2uf2
[ 50%] Building CXX object CMakeFiles/elf2uf2.dir/main.cpp.o
[100%] Linking CXX executable elf2uf2
[100%] Built target elf2uf2
[ 11%] No install step for 'ELF2UF2Build'
[ 11%] Completed 'ELF2UF2Build'
[ 11%] Built target ELF2UF2Build
Scanning dependencies of target roundlcd_demo
[ 11%] Building CXX object examples/breakout_roundlcd/CMakeFiles/roundlcd_demo.dir/demo.cpp.obj
/home/pi/pico/pimoroni-pico/examples/breakout_roundlcd/demo.cpp: In function 'int main()':
/home/pi/pico/pimoroni-pico/examples/breakout_roundlcd/demo.cpp:49:25: error: request for member '_private_us_since_boot' in 'at', which is of non-class type 'absolute_time_t {aka long long unsigned int}'
         uint64_t t = at._private_us_since_boot / 100000;
                         ^~~~~~~~~~~~~~~~~~~~~~
make[2]: *** [examples/breakout_roundlcd/CMakeFiles/roundlcd_demo.dir/build.make:63: examples/breakout_roundlcd/CMakeFiles/roundlcd_demo.dir/demo.cpp.obj] Error 1
make[1]: *** [CMakeFiles/Makefile2:2156: examples/breakout_roundlcd/CMakeFiles/roundlcd_demo.dir/all] Error 2
make: *** [Makefile:84: all] Error 2

I note also error in where to get µpython from in docs - repo should be:
pi@raspberrypi:~/pico/micropython/ports/rp2 $ git remote -v
origin	git@github.com:micropython/micropython.git (fetch)
origin	git@github.com:micropython/micropython.git (push)

?
(the repo listed in the README does not exist)

Ooof, yes that line should be:
uint64_t t = to_us_since_boot(at) / 100000;

I should not use members that are marked "private" with two different conventions :grimacing:
Will raise a PR to patch it.

👍
Thanks for the quick fix


[ja] typo

What article on docs.github.com is affected?
https://docs.github.com/ja/graphql/guides/forming-calls-with-graphql#about-queries
What part(s) of the article would you like to see updated?
GraphQLのクエリは、指定したデータのみを返します。 クエリを作成する2は、[omit...]

should be
GraphQLのクエリは、指定したデータのみを返します。 クエリを作成するには、[omit...]

Additional information

Whoops, sorry for that inadvertent bot close @KisaragiEffective!
Unfortunately, we are not able to accept pull requests for translated content in this repo. Our translation process involves an integration with an external service at crowdin.com, where all translation activity happens. We hope to eventually open up the translation process to the open-source community, but we're not there yet.
See https://github.com/github/docs/blob/main/CONTRIBUTING.md#earth_asia-translations for more details.
I've opened an internal issue for our team to look into this typo 💛


Revision of string interpolation quickstart

On the journey related to #3285 I've revised the string interpolation quickstart. The philosophy behind made changes is the following.
First, I use string interpolation when referring to the feature and interpolated string when talking about a string literal. That looks that folks prefer string interpolation term when searching in Google. Let's hope those changes will bring the quickstart page to the top of the search results.
Second, current comments under the quickstart show that audience is confused. That's why I've tried to simplify the quickstart, especially its second step.
At last, I've made one more pass on the feature description itself to make it smoother.
@BillWagner @rpetrusha please review.

@BillWagner thank you for the feedback, I've addressed all comments.

Thanks for making the updates @pkulikov It looks great.  I've approved the changes, and I'll :shipit: now.
Thanks again for your continued involvement.

@BillWagner thank you very much for the highlight.
So far, it's been very cool to work with you and your team (@mairaw @rpetrusha you also rock): your reviews and feedback are always good and welcoming; of course, my favorite one is :shipit: :).


Crash when controlling AXA Remote 2.0 synchronous

Hi,
I'm using your code to control both a 'normal' AXA Remote 2.0 as well as a 'synchronous' version that has two motors connected.
The single motor version works fine, but with the double motor version there occurs a crash every now and then.
I'm new to ESPHome development, so I'm wondering how I can debug this issue.
Can you provide some support?

Hi, i do not have two AXA modules to test. May be the serial port gives some feedback and you have to put a trace on the serial ouput to give some clue what is going on? The code will put also some logging to the LOG feed (accessible via Esphome LOG).

Hi, Thank you for your answer. I've been able to drastically reduce the crashes by performing a bounds check when writing to the buff array in the while(available()) loop.
It still crashes about 4 times a day, but it's useable now. The communication isn't 100% reliable as the commands from ESPHome might interfere with the master slave communication in which case both messages are lost.
Unfortunately I don't have a spare set, otherwise it would be much easier to dive into the communication to see whether reliability can be improved.

Hi, Thank you for your answer. I've been able to drastically reduce the crashes by performing a bounds check when writing to the buff array in the while(available()) loop.
It still crashes about 4 times a day, but it's useable now. The communication isn't 100% reliable as the commands from ESPHome might interfere with the master slave communication in which case both messages are lost.
Unfortunately I don't have a spare set, otherwise it would be much easier to dive into the communication to see whether reliability can be improved.

@rpoelstra
I think you'll find the crash related to the ESP chip losing power or browning out due to the extra draw from the dual motor setup.   I have had occasional errors with that even with the single motor setup device (the 2.0)
You may need to increase track size for the DC power rails to the AXA and the ESP chip.


Make gray CameraImage before OCR recognition.

As I know tesseract works better if image is grayscale. ocrOnFrame is accepting only CameraImage and I didn't find a way to make it gray

CameraOnImage  does automatically this changes, don't care about it :)

But is there any way to improve accuracy of tesseract recognition? You said that I don't need to do any image preprocessing, so what should I do to improve it?

This is flow that flutter_vision do,  if you need more accuracy, you should modify preprocess phase, and it must be in c++, c or golang language, but it is not possible yet.

In the next release YoloV5, Tesseract and OCR will be apart each one to other, and you will have this possibility to modified intermediate phase with dart code assuming speed loss yourself


Rename to hug

slog is funny but I don't think it fits slog's personality. slog feels slow and sloppy but slog is anything but. I think this library could be very successful within the community and I don't want it to be held back by its name.
I like hug because of it's major focus on developer UX and the API design.

hug is ok but a name that indicates it’s a log is helpful when scanning through code or dependencies.

That's fair, hug is a little opaque. 🤔

Since no one else has issues with the name, going to close.


To fix Warning c4099: type name first seen using 'class' now seen using 'struct'

Looks great, tests are passing, so I will just merge it, thanks.


Infix, Postfix & Prefix expression evaluator using JavaScript

Is your feature request related to a problem? Please describe.
No its not a problem. I just want to add a new project which evaluate the infix, postfix & prefix expression using JavaScript under GSSOC 2021.
Describe the solution you'd like
I will make an evaluator which evaluate infix, postfix & prefix expression. When user enters a infix/prefix/postfix expression and click on evaluate button then it evaluate the expression.

@shivammahajancse how is it different from #733 . If it is different then I would assigned this issue to @headphone-rachit


Saving edited map coordinates

If I get the map coordinates wrong the first time, there is no way to correct them and save them.
https://www.webonary.org/wp-admin/link-manager.php?page=links-map-publish%2Flinks-map-publish.php
I edited the coordinates of Buli and saved, but my changes did not save. They should be 9.667758424, -1.186802471
Normally these codes come from the Ethnologue, but sometimes the Ethnologue does not have coordinates. Then I use this site to manually search for them, https://www.whatsmygps.com/index.php?.

Looks good.


chore: automatically replace erw with rw that work as well

This is an automatically generated PR, replacing 443 erw calls with rw for free. I'm working on a follow-up that manually deals with the context around these erws: deleting now-useless comments about erw and merging adjacent rw calls into one. Keeping the automatically generated changes apart from the manual ones should help with reviewing.
How to reproduce this PR
Check out the branch erw-to-rw-setup. Run the command
lake build | grep '^info:' | awk -F ":" '{ print "-i ‘.bak’ -e "$3"s/erw/rw/ "$2; }' | xargs -L 1 sed

and git diff should show you exactly the same modifications as in this PR.
Technical details
In Mathlib.Tactic.Core I added the following rule to erw:
import Mathlib.Tactic.TryThis

/-- if we call `erw`, first try running regular `rw` and warn if that succeds. -/
macro_rules
  | `(tactic| erw $s $(loc)?) =>
    `(tactic| try_this rw $(.none)? $s $(loc)?)

This makes erw display a "Try this:" message if rw would have succeeded as well. Beware that this does not mean that the file compiles just as well after doing the replacement, since a rw could succeed by rewriting a different term, so subsequent tactics fail. This is important for running the script!
With that edit in place, it's possible to run the script. This will parse the lake build output, looking for the lines produced by the macro rule, and replace erw with rw on the lines that it indicates. Note that it assumes there is at most one erw on one line; that was true at least when I ran the script.

Here's the lake build output I used to generate this PR: erw-build-log.txt.

Thanks :tada:
If CI passes, please remove the label awaiting-CI and merge this yourself, by adding a comment bors r+.
bors d+

It builds now, so:
bors r+


ModuleNotFoundError

Extension Version: 3.7.3 64-bit
I cannot run even the simplest program.

I ran start_mc.py and the import command went wrong. I obviously have a "minecraft.py" in "mcpi" folder, why is the import always not successful??

You've to tell the extension where to look for module "mcpi". To do that, create a file .env with content PYTHONPATH=..
The extension cannot know the value of sys.path, so appending to it doesn't work.

Do you mean creating something like this? It won't work too.

The name of the file is .env. It's described in more detail in the documentation.

The name of the file is .env. It's described in more detail in the documentation.

Thanks! I've got it right this time.


Add support for Custom JS / CSS in jobs run form

As ...
P.D. - Plugin Developer
I want ...
to add support for custom JS/CSS on a per-job basis the jobs/run forms
So that ...
I can provide a better UI/UX to end users when using jobs. e,g hide/show fields onchange events etc etc
I know this is done when...
when the ability to add job specific CSS/JS is supported
Optional - Feature groups this request pertains to.

[ ] Automation
[ ] Circuits
[ ] DCIM
[ ] IPAM
[ ] Misc (including Data Sources)
[ ] Organization
[x] Plugins (and other Extensibility)
[ ] Security (Secrets, etc)
[ ] Image Management
[x] UI/UX
[ ] Documentation
[ ] Other (not directly a platform feature)

Database Changes
No response
External Dependencies
No response
Requirements/Thing to Consider

Existing templates support sensible blocks so as to permit overloading a portion of the UI if so desired

Closed via #1866


Line chart: markers strokeWidth options

Unable to use array for markers' strokeWidth

Thanks for reporting.
Fixed it. Will be possible in the next version.


Unable to flash SGS 5

I've been attempting to root my SGS 5 (International) on OSX. The device is detected, but when performing an action (e.g. print-pit) It will fail. The specific error I see when using verbose output is:
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
Looking at the OSX specific logs I see:
kernel[0]: USBF:    88081. 66    AppleUSBEHCI::Found a transaction past the completion deadline on bus 0x1d, timing out! (Addr: 6, EP: 1)
This is both with the stock cable, as well as an old one that is known to be a good cable that I've used in the past. I have also tried on multiple different laptops (both Apple) with the same results.
Please let me know if any additional information is needed.

SM-G900T OSX Mavericks
heimdall flash --stdout-errors --verbose --no-reboot --BOOT boot.img --CACHE cache.img.ext4 --RECOVERY recovery.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:685D
     bcdDevice: 0100

iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #1 failed. Result: 1025344
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #2 failed. Result: 998992
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #3 failed. Result: 998240
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #4 failed. Result: 1031904
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #5 failed. Result: 998240
WARNING: Control transfer #6 failed. Result: -9
WARNING: Control transfer #6 failed. Result: 998992
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 250 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 998240 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 998960 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 998960 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 1031904 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 998960 whilst sending packet.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 250 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 1031904 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 998208 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 998992 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 1031904 whilst sending packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst sending packet.ERROR: libusb error 998208 whilst sending packet.
ERROR: Failed to send end session packet!
ERROR: Failed to send end session packet!
Releasing device interface...

Hi @all,
for what it's worth: A self-compiled heimdall from current master (as of 28.7.2016 - sorry, no commit ID...) had absolutely no problems with my SM-G900F (S5 international version/klte). I did have a bad USB port/cable combination (USB device resetting after every open()), but changing cables did the trick.
What I did:

Compiled heimdall from master on Kubuntu 16.04 by following Linux/README.
Updated stock ROM to 6.0.1 on phone
Entered Download Mode
Downloaded PIT without rebooting, worked correctly
Printed PIT without rebooting, worked correctly
Flashed TWRP 3.0.1, worked correctly
Booted into Recovery

Hope this helps anyone!

FYI I just had success using the commandline (not frontend) compiled from source 1.4.1 on Samsung Galaxy S5 G900F https://github.com/Benjamin-Dobell/Heimdall/issues/348#issuecomment-263537426


system  voteproducer problem can  not take turns producing

1、Here is my  list of producers :

In fact, only lwz is in the non-stop production block, the other two producers hml and lz only receive, no rotation production block.
2、lwz:

hml:

lx:

3、when i Cancel vote
cleos --url http://<IP_ADDRESS>:9800 system  voteproducer prods  userc  lx
cleos --url http://<IP_ADDRESS>:9800 system  voteproducer prods  userb  hml
cleos --url http://<IP_ADDRESS>:9800 system  voteproducer prods  usera  lwz

4、I vote again:
cleos --url http://<IP_ADDRESS>:9800 system  voteproducer prods  userc  hml
cleos --url http://<IP_ADDRESS>:9800 system  voteproducer prods  userb   hml
cleos --url http://<IP_ADDRESS>:9800 system  voteproducer prods  usera   lx

The result is still lwz has been in production, hml and lz have been receiving。

Check the config.ini for the nodes running hml and lz.  Be sure those accounts are listed as producer-name = in each respective config file.  If using the command line instead, be sure those accounts are being passed to nodeos with -p hml and -p lz.

You need to specify producer-name multiple times in config.ini, for example:
producer-name = inita
producer-name = initb
producer-name = initc

I add  producer-name in three nodeos's config , but the result is that the three producers are no longer producing blocks.

Please provide config.ini for each of your nodes.

1、eosio's config file(on the <IP_ADDRESS> host):
bnet-endpoint = <IP_ADDRESS>:4321
bnet-follow-irreversible = 0
bnet-no-trx = false
bnet-peer-log-format = ["${_name}" ${_ip}:${_port}]
blocks-dir = "blocks"
abi-serializer-max-time-ms = 15000
chain-state-db-size-mb = 1024
chain-state-db-guard-size-mb = 128
reversible-blocks-db-size-mb = 340
reversible-blocks-db-guard-size-mb = 2
contracts-console = false
read-mode = speculative
validation-mode = full
https-client-validate-peers = 1
http-server-address = <IP_ADDRESS>:9800
access-control-allow-credentials = false
max-body-size = 1048576
verbose-http-errors = false
http-validate-host = 1
max-login-requests = 1000000
max-login-timeout = 60
mongodb-queue-size = 1024
mongodb-abi-cache-size = 2048
mongodb-wipe = false
mongodb-block-start = 0
Enables storing blocks in mongodb. (eosio::mongo_db_plugin)
mongodb-store-blocks = 1
Enables storing block state in mongodb. (eosio::mongo_db_plugin)
mongodb-store-block-states = 1
Enables storing transactions in mongodb. (eosio::mongo_db_plugin)
Enables storing transaction traces in mongodb. (eosio::mongo_db_plugin)
mongodb-store-transaction-traces = 1
Enables storing action traces in mongodb. (eosio::mongo_db_plugin)
mongodb-store-action-traces = 1
The actual host:port used to listen for incoming p2p connections. (eosio::net_plugin)
p2p-listen-endpoint = <IP_ADDRESS>:9900
An externally accessible host:port for identifying this node. Defaults to p2p-listen-endpoint. (eosio::net_plugin)
#p2p-server-address =
The public endpoint of a peer node to connect to. Use multiple p2p-peer-address options as needed to compose a network. (eosio::net_plugin)
p2p-peer-address = <IP_ADDRESS>:9900
p2p-peer-address = <IP_ADDRESS>:9877
p2p-peer-address = <IP_ADDRESS>:9877
Maximum number of client nodes from any single IP address (eosio::net_plugin)
p2p-max-nodes-per-host = 1
The name supplied to identify this node amongst the peers. (eosio::net_plugin)
agent-name = "EOS Test Agent"
Can be 'any' or 'producers' or 'specified' or 'none'. If 'specified', peer-key must be specified at least once. If only 'producers', peer-key is not required. 'producers' and 'specified' may be combined. (eosio::net_plugin)
allowed-connection = any
Maximum number of clients from which connections are accepted, use 0 for no limit (eosio::net_plugin)
max-clients = 25
number of seconds to wait before cleaning up dead connections (eosio::net_plugin)
connection-cleanup-period = 30
max connection cleanup time per cleanup call in millisec (eosio::net_plugin)
max-cleanup-time-msec = 10
True to require exact match of peer network version. (eosio::net_plugin)
network-version-match = 0
number of blocks to retrieve in a chunk from any individual peer during synchronization (eosio::net_plugin)
sync-fetch-span = 100
maximum sizes of transaction or block messages that are sent without first sending a notice (eosio::net_plugin)
max-implicit-request = 1500
Enable expirimental socket read watermark optimization (eosio::net_plugin)
use-socket-read-watermark = 0
(eosio::net_plugin)
peer-log-format = ["${_name}" ${_ip}:${_port}]
Enable block production, even if the chain is stale. (eosio::producer_plugin)
enable-stale-production = true
Start this node in a state where production is paused (eosio::producer_plugin)
pause-on-startup = false
Limits the maximum time (in milliseconds) that is allowed a pushed transaction's code to execute before being considered invalid (eosio::producer_plugin)
max-transaction-time = 30
Limits the maximum age (in seconds) of the DPOS Irreversible Block for a chain this node will produce blocks on (use negative value to indicate unlimited) (eosio::producer_plugin)
max-irreversible-block-age = -1
ID of producer controlled by this node (e.g. inita; may specify multiple times) (eosio::producer_plugin)
producer-name = eosio
signature-provider = EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV=KEY:5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Limits the maximum time (in milliseconds) that is allowd for sending blocks to a keosd provider for signing (eosio::producer_plugin)
keosd-provider-timeout = 5
account that can not access to extended CPU/NET virtual resources (eosio::producer_plugin)
greylist-account =
offset of non last block producing time in micro second. Negative number results in blocks to go out sooner, and positive number results in blocks to go out later (eosio::producer_plugin)
produce-time-offset-us = 0
offset of last block producing time in micro second. Negative number results in blocks to go out sooner, and positive number results in blocks to go out later (eosio::producer_plugin)
last-block-time-offset-us = 0
ratio between incoming transations and deferred transactions when both are exhausted (eosio::producer_plugin)
incoming-defer-ratio = 1
Lag in number of blocks from the head block when selecting the reference block for transactions (-1 means Last Irreversible Block) (eosio::txn_test_gen_plugin)
txn-reference-block-lag = 0
Plugin(s) to enable, may be specified multiple times
plugin =
plugin = eosio::chain_api_plugin
plugin = eosio::history_api_plugin
plugin = eosio::chain_plugin
plugin = eosio::history_plugin
plugin = eosio::net_plugin
plugin = eosio::net_api_plugin
plugin = eosio::http_plugin
2、lwz nodes config(lwz  and lwz on the same host)：
the endpoint upon which to listen for incoming connections (eosio::bnet_plugin)
bnet-endpoint = <IP_ADDRESS>:4322
this peer will request only irreversible blocks from other nodes (eosio::bnet_plugin)
bnet-follow-irreversible = 0
the number of threads to use to process network messages (eosio::bnet_plugin)
bnet-threads =
remote endpoint of other node to connect to; Use multiple bnet-connect options as needed to compose a network (eosio::bnet_plugin)
bnet-connect =
this peer will request no pending transactions from other nodes (eosio::bnet_plugin)
bnet-no-trx = false
bnet-peer-log-format = ["${_name}" ${_ip}:${_port}]
the location of the blocks directory (absolute path or relative to application data dir) (eosio::chain_plugin)
blocks-dir = "blocks"
Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints. (eosio::chain_plugin)
checkpoint =
Override default WASM runtime (eosio::chain_plugin)
wasm-runtime =
Override default maximum ABI serialization time allowed in ms (eosio::chain_plugin)
abi-serializer-max-time-ms = 15000
Maximum size (in MiB) of the chain state database (eosio::chain_plugin)
chain-state-db-size-mb = 1024
Safely shut down node when free space remaining in the chain state database drops below this size (in MiB). (eosio::chain_plugin)
chain-state-db-guard-size-mb = 128
Maximum size (in MiB) of the reversible blocks database (eosio::chain_plugin)
reversible-blocks-db-size-mb = 340
Safely shut down node when free space remaining in the reverseible blocks database drops below this size (in MiB). (eosio::chain_plugin)
reversible-blocks-db-guard-size-mb = 2
print contract's output to console (eosio::chain_plugin)
contracts-console = false
read-mode = speculative
Chain validation mode ("full" or "light").
In "full" mode all incoming blocks will be fully validated.
In "light" mode all incoming blocks headers will be fully validated; transactions in those validated blocks will be trusted
(eosio::chain_plugin)
validation-mode = full
true: validate that the peer certificates are valid and trusted, false: ignore cert errors (eosio::http_client_plugin)
https-client-validate-peers = 1
The local IP and port to listen for incoming http connections; set blank to disable. (eosio::http_plugin)
http-server-address = <IP_ADDRESS>:888
access-control-allow-credentials = false
The maximum body size in bytes allowed for incoming RPC requests (eosio::http_plugin)
max-body-size = 1048576
Append the error log to HTTP responses (eosio::http_plugin)
verbose-http-errors = false
If set to false, then any incoming "Host" header is considered valid (eosio::http_plugin)
http-validate-host = 1
Additionaly acceptable values for the "Host" header of incoming HTTP requests, can be specified multiple times.  Includes http/s_server_address by default. (eosio::http_plugin)
http-alias =
The maximum number of pending login requests (eosio::login_plugin)
max-login-requests = 1000000
The maximum timeout for pending login requests (in seconds) (eosio::login_plugin)
max-login-timeout = 60
The target queue size between nodeos and MongoDB plugin thread. (eosio::mongo_db_plugin)
mongodb-queue-size = 1024
The maximum size of the abi cache for serializing data. (eosio::mongo_db_plugin)
mongodb-abi-cache-size = 2048
Required with --replay-blockchain, --hard-replay-blockchain, or --delete-all-blocks to wipe mongo db.This option required to prevent accidental wipe of mongo db. (eosio::mongo_db_plugin)
mongodb-wipe = false
If specified then only abi data pushed to mongodb until specified block is reached. (eosio::mongo_db_plugin)
mongodb-block-start = 0
MongoDB URI connection string, see: https://docs.mongodb.com/master/reference/connection-string/. If not specified then plugin is disabled. Default database 'EOS' is used if not specified in URI. Example: mongodb://<IP_ADDRESS>:27017/EOS (eosio::mongo_db_plugin)
mongodb-uri =
Enables storing blocks in mongodb. (eosio::mongo_db_plugin)
mongodb-store-blocks = 1
Enables storing block state in mongodb. (eosio::mongo_db_plugin)
mongodb-store-block-states = 1
Enables storing transactions in mongodb. (eosio::mongo_db_plugin)
mongodb-store-transactions = 1
Enables storing transaction traces in mongodb. (eosio::mongo_db_plugin)
mongodb-store-transaction-traces = 1
Enables storing action traces in mongodb. (eosio::mongo_db_plugin)
mongodb-store-action-traces = 1
p2p-listen-endpoint = <IP_ADDRESS>:9877
An externally accessible host:port for identifying this node. Defaults to p2p-listen-endpoint. (eosio::net_plugin)
p2p-server-address =
The public endpoint of a peer node to connect to. Use multiple p2p-peer-address options as needed to compose a network. (eosio::net_plugin)
p2p-peer-address = <IP_ADDRESS>:9900
p2p-peer-address = <IP_ADDRESS>:9900
p2p-peer-address = <IP_ADDRESS>:9877
Maximum number of client nodes from any single IP address (eosio::net_plugin)
p2p-max-nodes-per-host = 1
The name supplied to identify this node amongst the peers. (eosio::net_plugin)
agent-name = "EOS Test Agent"
Can be 'any' or 'producers' or 'specified' or 'none'. If 'specified', peer-key must be specified at least once. If only 'producers', peer-key is not required. 'producers' and 'specified' may be combined. (eosio::net_plugin)
allowed-connection = any
Maximum number of clients from which connections are accepted, use 0 for no limit (eosio::net_plugin)
max-clients = 25
number of seconds to wait before cleaning up dead connections (eosio::net_plugin)
connection-cleanup-period = 30
max connection cleanup time per cleanup call in millisec (eosio::net_plugin)
max-cleanup-time-msec = 10
True to require exact match of peer network version. (eosio::net_plugin)
network-version-match = 0
number of blocks to retrieve in a chunk from any individual peer during synchronization (eosio::net_plugin)
sync-fetch-span = 100
maximum sizes of transaction or block messages that are sent without first sending a notice (eosio::net_plugin)
max-implicit-request = 1500
Enable expirimental socket read watermark optimization (eosio::net_plugin)
use-socket-read-watermark = 0
peer-log-format = ["${_name}" ${_ip}:${_port}]
Enable block production, even if the chain is stale. (eosio::producer_plugin)
enable-stale-production = false
Start this node in a state where production is paused (eosio::producer_plugin)
pause-on-startup = false
Limits the maximum time (in milliseconds) that is allowed a pushed transaction's code to execute before being considered invalid (eosio::producer_plugin)
max-transaction-time = 30
Limits the maximum age (in seconds) of the DPOS Irreversible Block for a chain this node will produce blocks on (use negative value to indicate unlimited) (eosio::producer_plugin)
max-irreversible-block-age = -1
ID of producer controlled by this node (e.g. inita; may specify multiple times) (eosio::producer_plugin)
producer-name = lwz
producer-name = hml
producer-name = lx
signature-provider = EOS7ijWCBmoXBi3CgtK7DJxentZZeTkeUnaSDvyro9dq7Sd1C3dC4=KEY:5Jmsawgsp1tQ3GD6JyGCwy1dcvqKZgX6ugMVMdjirx85iv5VyPR
Limits the maximum time (in milliseconds) that is allowd for sending blocks to a keosd provider for signing (eosio::producer_plugin)
keosd-provider-timeout = 5
account that can not access to extended CPU/NET virtual resources (eosio::producer_plugin)
greylist-account =
offset of non last block producing time in micro second. Negative number results in blocks to go out sooner, and positive number results in blocks to go out later (eosio::producer_plugin)
produce-time-offset-us = 0
offset of last block producing time in micro second. Negative number results in blocks to go out sooner, and positive number results in blocks to go out later (eosio::producer_plugin)
last-block-time-offset-us = 0
ratio between incoming transations and deferred transactions when both are exhausted (eosio::producer_plugin)
incoming-defer-ratio = 1
Lag in number of blocks from the head block when selecting the reference block for transactions (-1 means Last Irreversible Block) (eosio::txn_test_gen_plugin)
txn-reference-block-lag = 0
Plugin(s) to enable, may be specified multiple times
plugin =
plugin = eosio::chain_api_plugin
plugin = eosio::history_api_plugin
plugin = eosio::chain_plugin
plugin = eosio::history_plugin
plugin = eosio::net_plugin
plugin = eosio::net_api_plugin
plugin = eosio::http_plugin
3、hml nodeos config(on the <IP_ADDRESS> host):
the endpoint upon which to listen for incoming connections (eosio::bnet_plugin)
bnet-endpoint = <IP_ADDRESS>:4321
this peer will request only irreversible blocks from other nodes (eosio::bnet_plugin)
bnet-follow-irreversible = 0
the number of threads to use to process network messages (eosio::bnet_plugin)
bnet-threads =
remote endpoint of other node to connect to; Use multiple bnet-connect options as needed to compose a network (eosio::bnet_plugin)
bnet-connect =
this peer will request no pending transactions from other nodes (eosio::bnet_plugin)
bnet-no-trx = false
bnet-peer-log-format = ["${_name}" ${_ip}:${_port}]
the location of the blocks directory (absolute path or relative to application data dir) (eosio::chain_plugin)
blocks-dir = "blocks"
Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints. (eosio::chain_plugin)
checkpoint =
Override default WASM runtime (eosio::chain_plugin)
wasm-runtime =
Override default maximum ABI serialization time allowed in ms (eosio::chain_plugin)
abi-serializer-max-time-ms = 15000
Maximum size (in MiB) of the chain state database (eosio::chain_plugin)
chain-state-db-size-mb = 1024
Safely shut down node when free space remaining in the chain state database drops below this size (in MiB). (eosio::chain_plugin)
chain-state-db-guard-size-mb = 128
Maximum size (in MiB) of the reversible blocks database (eosio::chain_plugin)
reversible-blocks-db-size-mb = 340
Safely shut down node when free space remaining in the reverseible blocks database drops below this size (in MiB). (eosio::chain_plugin)
reversible-blocks-db-guard-size-mb = 2
print contract's output to console (eosio::chain_plugin)
contracts-console = false
(eosio::chain_plugin)
read-mode = speculative
Chain validation mode ("full" or "light").
In "full" mode all incoming blocks will be fully validated.
In "light" mode all incoming blocks headers will be fully validated; transactions in those validated blocks will be trusted
(eosio::chain_plugin)
validation-mode = full
true: validate that the peer certificates are valid and trusted, false: ignore cert errors (eosio::http_client_plugin)
https-client-validate-peers = 1
The local IP and port to listen for incoming http connections; set blank to disable. (eosio::http_plugin)
http-server-address = <IP_ADDRESS>:9800
access-control-allow-credentials = false
The maximum body size in bytes allowed for incoming RPC requests (eosio::http_plugin)
max-body-size = 1048576
Append the error log to HTTP responses (eosio::http_plugin)
verbose-http-errors = false
If set to false, then any incoming "Host" header is considered valid (eosio::http_plugin)
http-validate-host = 1
Additionaly acceptable values for the "Host" header of incoming HTTP requests, can be specified multiple times.  Includes http/s_server_address by default. (eosio::http_plugin)
http-alias =
The maximum number of pending login requests (eosio::login_plugin)
max-login-requests = 1000000
The maximum timeout for pending login requests (in seconds) (eosio::login_plugin)
max-login-timeout = 60
The target queue size between nodeos and MongoDB plugin thread. (eosio::mongo_db_plugin)
mongodb-queue-size = 1024
The maximum size of the abi cache for serializing data. (eosio::mongo_db_plugin)
mongodb-abi-cache-size = 2048
Required with --replay-blockchain, --hard-replay-blockchain, or --delete-all-blocks to wipe mongo db.This option required to prevent accidental wipe of mongo db. (eosio::mongo_db_plugin)
mongodb-wipe = false
mongodb-block-start = 0
MongoDB URI connection string, see: https://docs.mongodb.com/master/reference/connection-string/. If not specified then plugin is disabled. Default database 'EOS' is used if not specified in URI. Example: mongodb://<IP_ADDRESS>:27017/EOS (eosio::mongo_db_plugin)
mongodb-uri =
Enables storing blocks in mongodb. (eosio::mongo_db_plugin)
mongodb-store-blocks = 1
Enables storing block state in mongodb. (eosio::mongo_db_plugin)
mongodb-store-block-states = 1
Enables storing transactions in mongodb. (eosio::mongo_db_plugin)
mongodb-store-transactions = 1
Enables storing transaction traces in mongodb. (eosio::mongo_db_plugin)
mongodb-store-transaction-traces = 1
Enables storing action traces in mongodb. (eosio::mongo_db_plugin)
mongodb-store-action-traces = 1
p2p-listen-endpoint = <IP_ADDRESS>:9900
An externally accessible host:port for identifying this node. Defaults to p2p-listen-endpoint. (eosio::net_plugin)
p2p-server-address =
The public endpoint of a peer node to connect to. Use multiple p2p-peer-address options as needed to compose a network. (eosio::net_plugin)
p2p-peer-address = <IP_ADDRESS>:9900
p2p-peer-address = <IP_ADDRESS>:9877
p2p-peer-address = <IP_ADDRESS>:9877
Maximum number of client nodes from any single IP address (eosio::net_plugin)
p2p-max-nodes-per-host = 1
The name supplied to identify this node amongst the peers. (eosio::net_plugin)
agent-name = "EOS Test Agent"
Can be 'any' or 'producers' or 'specified' or 'none'. If 'specified', peer-key must be specified at least once. If only 'producers', peer-key is not required. 'producers' and 'specified' may be combined. (eosio::net_plugin)
allowed-connection = any
Optional public key of peer allowed to connect.  May be used multiple times. (eosio::net_plugin)
peer-key =
Tuple of [PublicKey, WIF private key] (may specify multiple times) (eosio::net_plugin)
peer-private-key =
Maximum number of clients from which connections are accepted, use 0 for no limit (eosio::net_plugin)
max-clients = 25
number of seconds to wait before cleaning up dead connections (eosio::net_plugin)
connection-cleanup-period = 30
max connection cleanup time per cleanup call in millisec (eosio::net_plugin)
max-cleanup-time-msec = 10
True to require exact match of peer network version. (eosio::net_plugin)
network-version-match = 0
number of blocks to retrieve in a chunk from any individual peer during synchronization (eosio::net_plugin)
sync-fetch-span = 100
maximum sizes of transaction or block messages that are sent without first sending a notice (eosio::net_plugin)
max-implicit-request = 1500
Enable expirimental socket read watermark optimization (eosio::net_plugin)
use-socket-read-watermark = 0
peer-log-format = ["${_name}" ${_ip}:${_port}]
Enable block production, even if the chain is stale. (eosio::producer_plugin)
enable-stale-production = false
Start this node in a state where production is paused (eosio::producer_plugin)
pause-on-startup = false
Limits the maximum time (in milliseconds) that is allowed a pushed transaction's code to execute before being considered invalid (eosio::producer_plugin)
max-transaction-time = 30
Limits the maximum age (in seconds) of the DPOS Irreversible Block for a chain this node will produce blocks on (use negative value to indicate unlimited) (eosio::producer_plugin)
max-irreversible-block-age = -1
ID of producer controlled by this node (e.g. inita; may specify multiple times) (eosio::producer_plugin)
producer-name = hml
producer-name = lwz
producer-name = lx
signature-provider = EOS7fu9rx1wtEPnX3jY2ZfezyLwV5Ly29g6nmyTSwtLAQMu4boFJz=KEY:5JjWBaVxKnWpcr857E8dWBr8Duq76M7wzoUEEwAAzzwUjz9Yyqs
Limits the maximum time (in milliseconds) that is allowd for sending blocks to a keosd provider for signing (eosio::producer_plugin)
keosd-provider-timeout = 5
account that can not access to extended CPU/NET virtual resources (eosio::producer_plugin)
greylist-account =
offset of non last block producing time in micro second. Negative number results in blocks to go out sooner, and positive number results in blocks to go out later (eosio::producer_plugin)
produce-time-offset-us = 0
offset of last block producing time in micro second. Negative number results in blocks to go out sooner, and positive number results in blocks to go out later (eosio::producer_plugin)
last-block-time-offset-us = 0
ratio between incoming transations and deferred transactions when both are exhausted (eosio::producer_plugin)
incoming-defer-ratio = 1
Lag in number of blocks from the head block when selecting the reference block for transactions (-1 means Last Irreversible Block) (eosio::txn_test_gen_plugin)
txn-reference-block-lag = 0
Plugin(s) to enable, may be specified multiple times
plugin =
plugin = eosio::chain_api_plugin
plugin = eosio::history_api_plugin
plugin = eosio::chain_plugin
plugin = eosio::history_plugin
plugin = eosio::net_plugin
plugin = eosio::net_api_plugin
plugin = eosio::http_plugin
4、lx nodeos config(lx and hml on the same host <IP_ADDRESS>)
bnet-endpoint = <IP_ADDRESS>:4322
this peer will request only irreversible blocks from other nodes (eosio::bnet_plugin)
bnet-follow-irreversible = 0
the number of threads to use to process network messages (eosio::bnet_plugin)
bnet-threads =
remote endpoint of other node to connect to; Use multiple bnet-connect options as needed to compose a network (eosio::bnet_plugin)
bnet-connect =
this peer will request no pending transactions from other nodes (eosio::bnet_plugin)
bnet-no-trx = false
bnet-peer-log-format = ["${_name}" ${_ip}:${_port}]
the location of the blocks directory (absolute path or relative to application data dir) (eosio::chain_plugin)
blocks-dir = "blocks"
Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints. (eosio::chain_plugin)
checkpoint =
Override default WASM runtime (eosio::chain_plugin)
wasm-runtime =
Override default maximum ABI serialization time allowed in ms (eosio::chain_plugin)
abi-serializer-max-time-ms = 15000
Maximum size (in MiB) of the chain state database (eosio::chain_plugin)
chain-state-db-size-mb = 1024
Safely shut down node when free space remaining in the chain state database drops below this size (in MiB). (eosio::chain_plugin)
chain-state-db-guard-size-mb = 128
Maximum size (in MiB) of the reversible blocks database (eosio::chain_plugin)
reversible-blocks-db-size-mb = 340
Safely shut down node when free space remaining in the reverseible blocks database drops below this size (in MiB). (eosio::chain_plugin)
reversible-blocks-db-guard-size-mb = 2
print contract's output to console (eosio::chain_plugin)
contracts-console = false
read-mode = speculative
Chain validation mode ("full" or "light").
In "full" mode all incoming blocks will be fully validated.
In "light" mode all incoming blocks headers will be fully validated; transactions in those validated blocks will be trusted
(eosio::chain_plugin)
validation-mode = full
https-client-validate-peers = 1
The local IP and port to listen for incoming http connections; set blank to disable. (eosio::http_plugin)
http-server-address = <IP_ADDRESS>:8889
access-control-allow-credentials = false
The maximum body size in bytes allowed for incoming RPC requests (eosio::http_plugin)
max-body-size = 1048576
Append the error log to HTTP responses (eosio::http_plugin)
verbose-http-errors = false
If set to false, then any incoming "Host" header is considered valid (eosio::http_plugin)
http-validate-host = 0
Additionaly acceptable values for the "Host" header of incoming HTTP requests, can be specified multiple times.  Includes http/s_server_address by default. (eosio::http_plugin)
http-alias =
The maximum number of pending login requests (eosio::login_plugin)
max-login-requests = 1000000
The maximum timeout for pending login requests (in seconds) (eosio::login_plugin)
max-login-timeout = 60
The target queue size between nodeos and MongoDB plugin thread. (eosio::mongo_db_plugin)
mongodb-queue-size = 1024
The maximum size of the abi cache for serializing data. (eosio::mongo_db_plugin)
mongodb-abi-cache-size = 2048
Required with --replay-blockchain, --hard-replay-blockchain, or --delete-all-blocks to wipe mongo db.This option required to prevent accidental wipe of mongo db. (eosio::mongo_db_plugin)
mongodb-wipe = false
mongodb-block-start = 0
MongoDB URI connection string, see: https://docs.mongodb.com/master/reference/connection-string/. If not specified then plugin is disabled. Default database 'EOS' is used if not specified in URI. Example: mongodb://<IP_ADDRESS>:27017/EOS (eosio::mongo_db_plugin)
mongodb-uri =
Enables storing blocks in mongodb. (eosio::mongo_db_plugin)
mongodb-store-blocks = 1
Enables storing block state in mongodb. (eosio::mongo_db_plugin)
mongodb-store-block-states = 1
Enables storing transactions in mongodb. (eosio::mongo_db_plugin)
mongodb-store-transactions = 1
Enables storing transaction traces in mongodb. (eosio::mongo_db_plugin)
mongodb-store-transaction-traces = 1
Enables storing action traces in mongodb. (eosio::mongo_db_plugin)
mongodb-store-action-traces = 1
p2p-listen-endpoint = <IP_ADDRESS>:9877
An externally accessible host:port for identifying this node. Defaults to p2p-listen-endpoint. (eosio::net_plugin)
p2p-server-address =
The public endpoint of a peer node to connect to. Use multiple p2p-peer-address options as needed to compose a network. (eosio::net_plugin)
p2p-peer-address =
p2p-peer-address = <IP_ADDRESS>:9900
p2p-peer-address = <IP_ADDRESS>:9877
p2p-peer-address = <IP_ADDRESS>:9900
Maximum number of client nodes from any single IP address (eosio::net_plugin)
p2p-max-nodes-per-host = 1
The name supplied to identify this node amongst the peers. (eosio::net_plugin)
agent-name = "EOS hml Agent"
Can be 'any' or 'producers' or 'specified' or 'none'. If 'specified', peer-key must be specified at least once. If only 'producers', peer-key is not required. 'producers' and 'specified' may be combined. (eosio::net_plugin)
allowed-connection = any
max-clients = 25
number of seconds to wait before cleaning up dead connections (eosio::net_plugin)
connection-cleanup-period = 30
max connection cleanup time per cleanup call in millisec (eosio::net_plugin)
max-cleanup-time-msec = 10
True to require exact match of peer network version. (eosio::net_plugin)
network-version-match = 0
number of blocks to retrieve in a chunk from any individual peer during synchronization (eosio::net_plugin)
sync-fetch-span = 100
maximum sizes of transaction or block messages that are sent without first sending a notice (eosio::net_plugin)
max-implicit-request = 1500
Enable expirimental socket read watermark optimization (eosio::net_plugin)
use-socket-read-watermark = 0
peer-log-format = ["${_name}" ${_ip}:${_port}]
Enable block production, even if the chain is stale. (eosio::producer_plugin)
enable-stale-production = false
Start this node in a state where production is paused (eosio::producer_plugin)
pause-on-startup = false
Limits the maximum time (in milliseconds) that is allowed a pushed transaction's code to execute before being considered invalid (eosio::producer_plugin)
max-transaction-time = 30
Limits the maximum age (in seconds) of the DPOS Irreversible Block for a chain this node will produce blocks on (use negative value to indicate unlimited) (eosio::producer_plugin)
max-irreversible-block-age = -1
ID of producer controlled by this node (e.g. inita; may specify multiple times) (eosio::producer_plugin)
producer-name = eosio
producer-name = lx
producer-name = hml
producer-name = lwz
signature-provider = EOS5n442Qz4yVc4LbdPCDnxNSseAiUCrNjRxAfPhUvM8tWS5svid6=KEY:5JCStvbRgUZ6hjyfUiUaxt5iU3HP6zC1kwx3W7SweaEGvs4EPfQ
Limits the maximum time (in milliseconds) that is allowd for sending blocks to a keosd provider for signing (eosio::producer_plugin)
keosd-provider-timeout = 5
account that can not access to extended CPU/NET virtual resources (eosio::producer_plugin)
greylist-account =
offset of non last block producing time in micro second. Negative number results in blocks to go out sooner, and positive number results in blocks to go out later (eosio::producer_plugin)
produce-time-offset-us = 0
offset of last block producing time in micro second. Negative number results in blocks to go out sooner, and positive number results in blocks to go out later (eosio::producer_plugin)
last-block-time-offset-us = 0
ratio between incoming transations and deferred transactions when both are exhausted (eosio::producer_plugin)
incoming-defer-ratio = 1
Lag in number of blocks from the head block when selecting the reference block for transactions (-1 means Last Irreversible Block) (eosio::txn_test_gen_plugin)
txn-reference-block-lag = 0
plugin = eosio::chain_api_plugin
plugin = eosio::history_api_plugin
plugin = eosio::chain_plugin
plugin = eosio::history_plugin
plugin = eosio::net_plugin
plugin = eosio::net_api_plugin
plugin = eosio::http_plugin
5、IN the two host i import lwz 、hml 、lx 、eosio 's private key into wallet:
cleos --url http://<IP_ADDRESS>:9800  wallet  import --private-key
cleos --url http://<IP_ADDRESS>:9800  wallet  import --private-key

I see I must clarify my English.  The word "respective" means "in each corresponding" file.
You can not duplicate producer-name = lx on multiple synchronized hosts.  It must appear in only one config file.  The same is true for each named producer.  So if you want <IP_ADDRESS> to be the lwz producer, its config file should be the only one with producer-name = lwz in it.  If you want <IP_ADDRESS> to be the hml producer, its config file should be the only one with producer-name = hml in it.  Likewise the lx producer should appear in only one config file.
It is not necessary to import producer keys into a wallet unless you're using the KEOSD form of signature provider.

We haven't received any follow up from this.

If you still have the problem and wish to discuss further, please post it in https://eosio.stackexchange.com. To keep things organized, Github issues are intended for bugs reporting and features tracking, and Stack Exchange is the right place for any technical support discussions. Thanks!


[question] How to run this with newest LLVM?

Thanks for posting this demo! I was following the instructions with latest emsdk (LLVM version 10.0.0) and I am getting an empty main.wasm. What should I change for it to work again?

Adding --export-all to the wasm-ld command line produces a working main.wasm. Perhaps it would be better to mark the function you want to export (e.g. main) in main.ll but I don't know how to do that.


arc plots for long transcripts (>3500 bases) crash program

For Longleaf install using Jupyter notebook (UNC OnDemand interface). Trying to generate an arc plot for a 7kb transcript crashes the program. Generating arc plots for regions <=3500 bases is successful. Generating simpler plots for the full 7kb transcript completes without error.
Error message generated for larger transcripts:
"Kernel Restarting
The kernel for [Notebook name].ipynb appears to have died. It will restart automatically."
Examples:
Generates above error
plot = DMS.plot_arcs(interactions="pairprob")
Generates above error
plot = DMS.plot_arcs(interactions="pairprob", region=[1,5000])
Generates above error
plot = DMS.plot_arcs(interactions="pairprob", region=[1,4000])
Completes without error
plot = DMS.plot_arcs(interactions="pairprob", region=[1,3500])
Completes without error
plot = DMS.plot_arcs(interactions="pairprob", region=[1,3000])
Completes without error for full 7kb transcript
plot = DMS.plot_shapemapper()

Man, Scott. You're really testing RNAvigates limits. Awesome!
I suspect you are running up against OnDemand's default memory allocation. Try requesting more memory.
Additionally, by default all plots are stored in memory. Run the following to clean up if making a lot of large plots:
import matplotlib.pyplot as plt
plt.close('all')

There is another limit on plot size imposed by matplotlib, which you won't be able to overcome. I'm not sure if a 7kb RNA will reach that limit or not.

Hey Patrick - that totally worked. Using more memory allowed generating the full length arc plot without error. I'll post the solution here in case other lab members run into this in the future:
When generating the Jupyter notebook session in the OnDemand Portal there is a box for additional arguments.
Enter: --mem=8G corresponding to 8GB. More or less may be necessary depending on transcript length.


NuGet & Local Packages on WSL2

Describe the bug
I'm trying to do some development inside WSL2 on a .NET Interactive Notebook (.dib format). I have local packages published to:
~/home/USERNAME/code/dotnet-sample/_packages
I've tried to use the #i "nuget:" format to reference the local folder i.e.
#i "nuget:~/home/USERNAME/code/dotnet-sample/_packages"
And have tried many different permutations of the file path format, but get the following error:
Error: PackageManagement Error 3217 Invalid URI: The format of the URI could not be determined.
Please complete the following:

Version: 1.0.431302+bd4cbf9d5b5a501ebf55c887f8591d851d046f4f
Library version: 1.0.0-beta.23313.2+bd4cbf9d5b5a501ebf55c887f8591d851d046f4f
Build date: 2023-06-13T18:23:18.0000000Z
OS

[X] Windows 11
[X] Linux WSL2 Debian

Frontend

[X] Visual Studio Code

/cc @KevinRansom

@HowardvanRooijen did you try the absolute path without the ~ .ie. /usr/username... ? I find ~ often does not work for these kinds of things.
What I am finding trying to use #i is that relative URIs just don't seem to work at all so this means this feature cant be used for scripts that are shared across a team (if that is indeed the case.).


[WIP] Add wlr_idle_listen, needed by sway idle_v2

Adding wlr_idle_listen to use idle timers without going through the idle protocol, but using the timers directly. Needed by sway idle_v2 https://github.com/swaywm/sway/pull/1831

Two general comments:

About wlr_idle_listen: I don't think we want to expose the timers in wlr_idle. Better to use timers in the compositor, it's really not hard.
The session interface should be generic. That means "releasing the lock" isn't going to be always "closing a file". You need to abstract this. Also, the callback should be replaced with a signal.


refactor: factor out fetch code from resolve

I replaved ResolveResult with Resolution which is more detailed type, a
discriminated union.
Then I removed fetch attribute from ResolveResult and moved that logic to
fetchResolution function. Thus removing src/resolve/fetch module entirely.

I've done requested changes.

A good place to discuss shrinkwrap is this issue at ied. Note: I used a different format from the one specified in the specs there, I'll make a PR to suggest the format I for pnpm.
Regarding this PR, if the tests pass and you don't want to make additional changes, I am ready to merge

I think I'm good with it.
On Fri, 20 Jan 2017 at 00:10 Zoltan Kochan<EMAIL_ADDRESS>wrote:

A good place to discuss shrinkwrap is this issue
https://github.com/alexanderGugel/ied/issues/188 at ied. Note: I used a
different format from the one specified in the specs there, I'll make a PR
to suggest the format I for pnpm.
Regarding this PR, if the tests pass and you don't want to make additional
changes, I am ready to merge
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rstacruz/pnpm/pull/563#issuecomment-273899637, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAB3gtyHpJlbHR7F9p0rCn6B7wt-IPg-ks5rT9FagaJpZM4LoWno
.

Hm... actually we might break current shrinkwrap format with this pull
request
On Fri, 20 Jan 2017 at 00:12 Andrey Popp<EMAIL_ADDRESS>wrote:

I think I'm good with it.
On Fri, 20 Jan 2017 at 00:10 Zoltan Kochan<EMAIL_ADDRESS>wrote:
A good place to discuss shrinkwrap is this issue
https://github.com/alexanderGugel/ied/issues/188 at ied. Note: I used a
different format from the one specified in the specs there, I'll make a PR
to suggest the format I for pnpm.
Regarding this PR, if the tests pass and you don't want to make additional
changes, I am ready to merge
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rstacruz/pnpm/pull/563#issuecomment-273899637, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAB3gtyHpJlbHR7F9p0rCn6B7wt-IPg-ks5rT9FagaJpZM4LoWno
.

Seems like the only breaking change is the addition of type, right? If type gets removed then it is not a breaking change

Ok, provided a backward compat for shrinkwrap. I still want to keep type in Resolution type as TS can't really differentiate different types in union without it and now resolution types are more untangled than before, I think.

Thanks, very nice refactoring!


kubeflow 1.3 not creating gpu notebooks

I was able to get a kubeflow 1.3 installation using microk8s 1.21 and the steps documented here (with a --purge of microk8s/juju before):  https://github.com/ubuntu/microk8s/issues/2253#issuecomment-838158746
However, when creating a new notebook, I get the following error:

Vanilla config, eg:

Thank you for pointing this out! Have you had any success with a custom image?

Also is this with the microk8s gpu addon enabled?

yes I am using the GPU addon, it pulled down the new operator I believe.  Will try a custom image in a bit.

hmm...

microk8s.kubectl get nodes "-o=custom-columns=NAME:.metadata.name,GPU:.status.allocatable.nvidia.com/gpu"
NAME     GPU
athena   none

So it might be an issue with microk8s.enable gpu @joedborg or @ktsakalozos, is this output expected?

creating cpu-only containers works, for what it's worth.  happy to tear down/rebuild things once the official release goes live.  happy to help trouble shoot things!

Any updates? I am experiencing the same problem

still seeing this w/ 20.04 + microk8s 1.20 +
sudo snap install microk8s --classic
microk8s.enable gpu
microk8s enable kubeflow --bundle=cs:kubeflow


remove JRuby from project

Use asciidoctor.js + opal + Nashorn instead of JRuby

I've been trying to achieve this but got mixed results.
Eval'ing the asciidoctor-all.js file (asciidoctor + opal) resulted in parsing errors - the kind of errors that can be tracked to Nashorn bugs and/or Opal+Asciidoctor needing more work to adapt to that platform.
In any case, at the current state this change would make the application too dependent on the asciidoctor and JVM versions, whereas we're trying to achieve maximum compatibility with contributors' environment here.
This issue may be revisited in the future, closing for now.


Two fixes for Bionic

lockf isn't provided in Bionic and the ilogb constants are defined differently.

LGTM

Auto-merge toggled on

Please don't put non-Posix functions into core.sys.posix, flock should live under core.sys.linux or core.sys.bionic.