text:
nuitka compiled exe in Windows is indentified as a virus/trojan

Any Onefile compiled python code in Windows is identified as a virus/trojan by avast and many others.
Some standalone builds are also reported as viruses/Trojans but not all seems depending on specific code compiled
I know that there are already reported similar issues but they're old, and some does not give code examples

Nuitka version, full Python version, flavor, OS, etc. as output by this exact command.

python -m nuitka --version

1.9.7
Commercial: None
Python: 3.8.18 (default, Aug 28 2023, 15:16:02) [MSC v.1900 64 bit (AMD64)]
Flavor: CPython Official
Executable: C:\Program Files\Python38\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
Version C compiler: ~\gcc (gcc 12.1.0).

Actually it's Windows 11 Pro

How did you install Nuitka and Python
Using installer from here
https://github.com/adang1345/PythonWindows/blob/master/3.8.18/python-3.8.18-amd64-full.exe
Here are it virustotal report
https://www.virustotal.com/gui/file/c61ab0ecc6a529492015d29c3c9e15e5d4340e78c7e232fe59b0d5d870eb02e2

The specific PyPI names and versions
It should be taken from this output if there specific packages involved, e.g. numpy, you are
expected to shorten this to the relevant ones.

python -m pip freeze

gmsh==4.12.0
Nuitka==1.9.7
numpy==1.24.4
numpy-stl==3.1.1
ordered-set==4.1.0
parea==0.1.1
psutil==5.9.7
PyQt5==5.15.10
PyQt5-Qt5==5.15.2
PyQt5-sip==12.13.0
python-utils==3.8.1
screeninfo==0.8.1
shapely==2.0.2
trimesh==4.0.8
typing_extensions==4.9.0
zstandard==0.22.0

Many times when you get an error from Nuitka, your setup may be special
Any python code compiled as OneFile in Windows is reported  as virus/trojan. If the same file is build as standalone no problem is reported when running with anti-virus installed.

Also supply a Short, Self Contained, Correct, Example
Call this code mypython_version.py and build it as a very simple example:

import sys

print("Python version:")
print(sys.version)

Provide in your issue the Nuitka options used
python -m nuitka --onefile --remove-output mypython_version.py

Here is its virustotal report
https://www.virustotal.com/gui/file/bbd9f9e104cf6bc334aa57dcf002b5ca619fa3c97f8ff540a9734d0e4a1e71d5
Compiling same as a standalone, include folder in a zip file upload to virustotal shows a similar problem too:
https://www.virustotal.com/gui/file/bdf60fcdca73e9f4deb58ec6ec720560ea772bf5da185a0e893a592d44e74779
Uploading a single exe from inside standalone build:
https://www.virustotal.com/gui/file/f2dc4a670a46ba80a6ad9a5f61a07c543dd8677dfa0bc2da660bb37fd3be6597
This is a another python example that's not reported a virus if built standalone for major anti-virus program like avast despite having more complex code and dependencies, report is much cleaner but not 100% on virustotal. But it's reported so if built as onefile:
Call it p-area.py and compile as python -m nuitka --standalone --remove-output --output-filename=parea p-area.py or python -m nuitka --onefile --remove-output --output-filename=parea p-area.py
# -*- coding: utf-8 -*-
import re
import sys
from parea import main
if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
    sys.exit(main())

Here is its standalone report
https://www.virustotal.com/gui/file/5e032f573c07c625304dcc1b076e49c79a09a7497bf6e19aa6e93e4585559eee
Here is its onefile report
https://www.virustotal.com/gui/file/3c7b754e63968d032332b87f158cf378021470484941ae5d22759eb2fff72991

pip uninstall zstandard
Then manually pack with upx.

Nuitka is the preferred choice of malware authors due to its protection of the source code, and the inability to investigate behavior of the program without deep analysis. This leads to Nuitka compiled binaries being reported as malware based on being similar to it, even for small programs, esp. for programs that use Crypto libraries and that deal with Crypto payments in particular.
There are ways around this, but further action will be needed, they are described here: https://nuitka.net/doc/user-manual.html#windows-virus-scanners
Naive compilation however is exactly what malware authors do, so it's not going to be sufficient to get your binaries not flagged.

pip uninstall zstandard

compile manually with nuitka.
Then manually pack with upx.

@7gxycn08
hi  how to compile ? with onefile o standalone? if standaalone how pack to one file all dll and exe ?

repo: Nuitka/Nuitka


text:
Error while using module created using Nuitka from python package using numpy.

I am trying to create a standalone module using a simple package I created.
Following is the file structure I have:

/home/user/nuitka_demo/NumpyProject/
    -- ./test.py
    -- ./firstPack/
        -- ./__init__.py
        -- ./firstpack.py

Content of the files:

# __init__.py
from firstPack.firstpack import MyVector

# firstpack.py
import numpy as np

class MyVector:
    def __init__(self, vector_as_list):
        self.vector = vector_as_list

    def vectorize(self):
        return np.array(self.vector)

    def scale(self, scale_factor):
        return scale_factor*self.vectorize()

# test.py
import firstPack
from firstPack import MyVector
vec = MyVector([1,2,3])
print(vec.vectorize())
print(vec.scale(3))

I am using the following command to create the module from the folder /home/user/nuitka_demo/NumpyProject/

python -m nuitka --module firstPack --plugin-enable=numpy --follow-imports --include-package=firstPack --include-plugin-directory=/home/user/anaconda3/envs/nuitka_env/lib/python3.6/site-packages/numpy/core --include-plugin-directory=/home/user/anaconda3/envs/nuitka_env/lib/python3.6/site-packages/numpy/lib

When I run this command in terminal I am getting the following warning:

Nuitka:WARNING:Recursed to package 'firstPack' at /home/user/nuitka_demo/NumpyProject/firstPack' twice.

When I try to use the firstPack.so module created, I get the following error:

$ python test.py
Traceback (most recent call last):
  File "test.py", line 1, in <module>
    import firstPack
  File "/home/user/nuitka_demo/NumpyProject/firstPack/__init__.py", line 1, in <module firstPack>
  File "/home/user/nuitka_demo/NumpyProject/firstPack/firstpack.py", line 1, in <module firstPack.firstpack>
  File "/home/user/nuitka_demo/NumpyProject/numpy/__init__.py", line 142, in <module numpy>
  File "/home/user/nuitka_demo/NumpyProject/numpy/core/__init__.py", line 3, in <module numpy.core>

Details:

$python -m nuitka --version
0.6.5
Python: 3.6.9 |Anaconda, Inc.| (default, Jul 30 2019, 19:07:31)
Executable: /home/user/anaconda3/envs/nuitka_env/bin/python
OS: Linux
Arch: x86_64

I installed Nuitka using pip install Nuitka

I tried the hello world example of Nuitka. It worked for me. There was no issue.

It will be great if someone can point me in the right direction. I am not sure what is it that I am missing and how to resolve this issue.
Thank you in advance.

Okay, I got to a point where I create a module something like firstPack.so using nuitka, and in my test.py module, I import module after importing numpy. Then the code is working. I have shared the updated code below.
# test.py
import numpy as np
import firstPack
from firstPack import MyVector
vec = MyVector([1,2,3])
print(vec.vectorize())
print(vec.scale(3))

Does this mean I cannot create a single module firstPack.so which will include numpy internally? Will have to mention numpy as a dependency always for this module?
Please let me know if I am missing something or any more information is required.

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Updated Backend.scons to add Haiku header path

This PR adds Python headers path for Haiku operating system.
With the default Backend.scons, there was no way to run Nuitka on Haiku as the existent paths didn't cover the specific paths in the Haiku operating system thus the headers are never found and Nuitka always halts with the "no Python header found" error.

Let me know when you had a chance to test it, so we don't have to do it twice.

I can take care of the autoformat, no problem.

Thanks for your contribution, I manually merged it to develop branch.

Good day @kayhayen,
Thanks for the merge. I'll notify the Haiku community about it, I'm sure the python devs will be happy.
Nonetheless, I still have to carry some testing with bigger projects, that I haven't had time yet to do. My pace is much slower than yours :)
I'll report any issue I may find when I try to bundle a bigger size project on Haiku. I'll try on metal during the holidays (hope so).
Thanks again and Merry Christmas!
Regards,
RR

@roired that's ok, take your time, but be sure everything you come up with will be welcome

source: gharchive/pull-request

authors: kayhayen roired


text:
Check lang keys at compile time

And fixed some erroneous lang keys found by it.
Examples (in my modified source for testing):
C:\Users\Liqueur Librazy\Documents\Github\nyaautils\src\main\java\cat\nyaa\nyaautils\lootprotect\LootProtectMode.java:7: 警告: Key component suffix LANG_CHECKER not found in lang en_US.yml
public enum LootProtectMode {
       ^
C:\Users\Liqueur Librazy\Documents\Github\nyaautils\src\main\java\cat\nyaa\nyaautils\CommandHandler.java:229: 警告: Key prefix user.p.mode_ not found in lang en_US.yml
        p.sendMessage(I18n.format("user.p.mode_" + plugin.cfg.lootProtectMode.name()));
                                  ^
C:\Users\Liqueur Librazy\Documents\Github\nyaautils\src\main\java\cat\nyaa\nyaautils\CommandHandler.java:365: 警告: Corrupted key user.rename.name_too_long in en_US.yml: Name '%s' is too long! Should less than %d chars
            msg(p, "user.rename.name_too_long", name);
                   ^
C:\Users\Liqueur Librazy\Documents\Github\nyaautils\src\main\java\cat\nyaa\nyaautils\CommandHandler.java:370: 警告: Key nu.warn.blocked_format_codes not found in lang en_US.yml
                msg(p, "nu.warn.blocked_format_codes", "&" + k);
                       ^

Integrating with idea:

Could you explain how the annotation works on Enum types and
what does the SUFFIX mean?

For enum types, it checks their enum constants' name as a string.
For something annotated as SUFFIX, it should appear as a suffix. Thus, there should be a key that endsWith it.
For PREFIX, should be a key that startsWith it.
For INFIX, should be a key that contains it.
For KEY, should be a key that equals it.

authors: Librazy RecursiveG

repo: NyaaCat/nyaautils

license: mit

license_source: bigquery


text:
Mirrors link to pantsu.cat on Fap/Fun link

config.WebAddress() just returns the URL from the default_config.yml
it should try to guess if the website is a mirror and if it is, return the current hostname

They just have to configure their own domain name on their own config.yml . It is always better to configure it through a file that no one can modify except a dev, than to use some http headers which can be falsified.

The problem is that they aren't running their own instance of pantsu so they can't have their own config files (i think?), they're all mirroring to the same instance of pantsu
Also even if it's falsifield, the web address is just used to get the right link (right fap/fun link in header and faq, right link for the feeds, right link for the email verification mail) so i don't think it can actually do any bad

So are we doing this or not?
I spent hours looking at the golang doc to try to get the hostname, tried to look at the headers too, nothing seems to work
If you don't want to do it then we can close the issue

repo: NyaaPantsu/nyaa


text:
Question - How to handle when refresh access token fails?

How do you pass a callback to the renew token process in the event that it fails?

all is done automatically
If someone want a notification or a closure to make a callback, feel free to PR

authors: phimage tcatwork

repo: OAuthSwift/OAuthSwiftAlamofire


text:
Move work off ODIQueensland

If ODIQueensland is defunct, would be it advisable to move work off this account to somewhere else?

Hi @JDziurlaj
It's a good point. I guess at this stage, personally I find that:

it keeps this project organised with the others (including examples) started with ODI and ODIQueensland. So it kinda makes sense just in terms of where I find this and related work.
I like the idea of keeping it in a place where @Stephen-Gates is also an overseer, as the project was his concept originally.

But yes perhaps I should fork this project now and place under QCIF, as from a maintenance point of view, it makes more sense there.
I'll leave this open for a bit - there might be other opinions out there. If I keep it here I'll add in other members from QCIF or if I fork the repo, I'll ensure @Stephen-Gates is added back in, and any existing reps from our sponsors.

I have no problem with forking but a number of other sites point here so a note in the readme point ing to the new location would help.
Known sites linking here:

https://frictionlessdata.io/tooling/labs/
https://frictionlessdata.io/blog/2019/03/01/datacurator/#using-data-curator
https://theodi.org/article/odi-toolbox-application-experiments-from-comma-chameleon-to-data-curator/
http://comma-chameleon.io

Thanks @Stephen-Gates Much appreciated. I've also added 2 other devs from QCIF as admins to this repo just as an extra layer of redundancy.

Started updating main page (see #1016) and README.md.

It is possible to move a repo without breaking links. If you transfer a repo rather than forking it, github will redirect traffic from the old URL so links won't break. Github will maintain the redirect indefinitely unless you create a new repo with the same name in the old user/org namespace.
There are various example of big projects which moved owner where this redirect still applies e.g:

https://github.com/kennethreitz/requests --> https://github.com/psf/requests
https://github.com/robmorgan/phinx --> https://github.com/cakephp/phinx

more info https://help.github.com/en/github/administering-a-repository/transferring-a-repository

Hi @chris48s
Yep for sure. Sorry for confusion - I think I was considering a fork initially as a conservative way to get started (in case there was resistance to the idea) - I should have made this more clear as discussions with our sponsors have moved on from this. Our sponsors support us moving completely from ODIQueensland to QCIF, knowing that Github will allow the redirects from old site, and I haven't seen any feedback suggest why we shouldn't move.
I've proposed that we do the move as part of our next Beta release, and have announced the move in our news. That way we have a bit of allocated time to fix up any redundant links/refs to ODIQueensland or to the old repo in our integration tests.
So yes a move, not a fork, will be happening within the next couple of weeks - thanks for the pickup :)

I'll add this in to our current milestone.

authors: JDziurlaj Stephen-Gates chris48s mattRedBox

repo: ODIQueensland/data-curator


text:
Images are displayed in black in OHIF viewer 2.0. Unsupported orthanc versions

I am using the OHIF Viewer 2.0 and Orthanc 1.5.0 versions and the images are displayed correctly in the orthanc viewer, but in the OHIF viewer it is not displayed. The image is not displayed(Black screen) even when patient data and series information has been loaded successfully.
This is how the image is displayed in the orthanc viewer:

When opening the same study with the OHIF viewer it appears like this:

I decided to try version 1.5.0 of orthanc because with newer versions the images appears with some black stains. I share with you a very similar case published previously:
https://github.com/OHIF/Viewers/issues/359
Using orthanc version 1.9.6 and the OHIF viewer 2.0, the image is displayed with black spots as can be seen below:

I could notice that this does not happen when I project the image in another viewer with the same version 1.9.6 of orthanc:

I am attaching dicom image used earlier in the examples, so that you can replicate the bug and help me find a solution.
https://drive.google.com/file/d/1iwYRPDkUlZ53mPo5VtxXNu6pZ7RB_N9S/view?usp=sharing
I have not found correct documentation of the versions of the orthanc compatible with the OHIF viewer 2.0 or of how to solve this error.

This loads fine in latest master

Please review the latest code in the master branch. This issue might have been resolved. If it persists, kindly reopen the issue with updated details.
Try viewer-dev.ohif.org instead of viewer.ohif.org
Our viewer.ohif.org is deployed from release branch while viewer-dev.ohif.org is our master  branch
Read more about branch explanations here https://docs.ohif.org/development/getting-started#developing

authors: JorgeFragozo sedghi

repo: OHIF/Viewers

license: MIT


text:
IC09/IC10 Generate CE Estab Addressed PQs

Motivation and Context
Want to generate individual addressed initial contact questionnaires for CE Estabs in English and Welsh
What has changed
New ActionRules
Pipenv fix
How to test?
Build and run with other repos and then run ATs
Links
https://trello.com/c/0JfdnR6q/795-ic09-ic10-generate-ce-ic-addressed-pqs-we-qids-required-13

 (IC09/IC10) Generate CE IC Addressed PQs: W&E QIDs required (13)

repo: ONSdigital/census-rm-ops


text:
Fix autosuggest error padding

What is the context of this PR?
Autosuggest error not displaying correctly this PR is to fix it

How to review
Check error now displays correctly

 Autosuggest error not displaying correctly

repo: ONSdigital/design-system


text:
Add ethnic group pattern

What is the context of this PR?
PR to add the ethnic group pattern used in Census 2021
How to review
Pattern looks as it did in Census 2021 and documentation makes sense

 Ethnic group [Ask users for...]


text:
⬆  Back To Top Link

What is the context of this PR?
Fixes: #1599
The back-to-top link is a requested feature for the Design System. The button takes you from wherever you are on the page to the top of the page or wherever you specify.
The default options for both are "Back to Top" taking you to "#top". To modify the text of the button, edit the description parameter. Similarly, to modify the jump location, edit the anchor parameter. When making a custom point to anchor, make sure to add an id to the element you want to jump to which matches the id in the anchor parameter.
As per the requirements, the button will appear towards the bottom of the screen when the user scrolls two window heights down from the anchor div. When the user reaches the link on the page, it will take the form of the link on the page.
Note: The width of the button is based on the width of the immediate sibling element previous to it. Suggested use would be to put the BTT adjacent to the element you want to mirror the width of, not inside.
How to review this PR
Check out the back to top button examples and make sure they are working correctly. Also test resizing the window to make sure the BTT links margins move accordingly
Checklist
This needs to be completed by the person raising the PR.

[x] I have selected the correct Assignee
[x] I have linked the correct Issue

On the second example the highlighting stays on after I use the back to top link, I think that after it goes back to top we would want the highlight to disappear?
This only happens on the full page version - not the first version.

Another small thing is where the page pulls you back to when linking to a specific point in the page - usually when I've seen section links used they put the bit you want to go back to at the natural reading height on the screen. Not sure if this might cause other issues or has already been considered!!
So as a user I'd expect it to go to a position roughly like this, rather than the 'Contents' title being right at the top of the page

Think this focus state might be a bit big. Also I think because of this we are losing the black underline that is used on other focused elements

Just realised we are also missing a _macro-options.md file for this

Another small thing is where the page pulls you back to when linking to a specific point in the page - usually when I've seen section links used they put the bit you want to go back to at the natural reading height on the screen. Not sure if this might cause other issues or has already been considered!!
So as a user I'd expect it to go to a position roughly like this, rather than the 'Contents' title being right at the top of the page

Talked to Joe about this and the decision was made to keep it as is. Doing this would confuse the user where they have jumped to if there was a say a one line bit of text above the jump location.

Think this focus state might be a bit big. Also I think because of this we are losing the black underline that is used on other focused elements

Talked to Joe about the width and the width being full / almost full width is fine and as intended. To match the skip-to-content component, the text underline is being added back in on focus.

Think this focus state might be a bit big. Also I think because of this we are losing the black underline that is used on other focused elements

Talked to Joe about the width being full / almost full width it is deemed to be as intended. To match the skip-to-content component, the text underline is being added back in on focus.

If you want to match skip-to-content wouldn't you want to have the whole thing highlighted?

Id recommend adding the eslint extension to your VScode and changing the "render whitespace" setting to "all" which will allow you to easily spot some of these things

Think this focus state might be a bit big. Also I think because of this we are losing the black underline that is used on other focused elements

Talked to Joe about the width being full / almost full width it is deemed to be as intended. To match the skip-to-content component, the text underline is being added back in on focus.

If you want to match skip-to-content wouldn't you want to have the whole thing highlighted?

Joe has confirmed this is what the intended behaviour should be. I will work on adding this in

Think this focus state might be a bit big. Also I think because of this we are losing the black underline that is used on other focused elements

Talked to Joe about the width being full / almost full width it is deemed to be as intended. To match the skip-to-content component, the text underline is being added back in on focus.

If you want to match skip-to-content wouldn't you want to have the whole thing highlighted?

Joe has confirmed this is what the intended behaviour should be. I will work on adding this in

An update on this. This would not be a good solution for screens which are wide / have wide windows. Joe has requested additional UX work to be done to make a decision on this before it is implemented.

authors: adi-unni balibirchlee rmccar


text:
Add new health question in census household

What is the context of this PR?
Adding new question including piped answer into question & updated functional and integration tests for new question addition
Card: https://trello.com/c/TyvH3nSJ/1501-add-health-question-s
How to review
The usual

@MIslam92 this PR contains changes other then what is described in the Trello card. can you attach the other cards if this PR is grouping changes?

@jonnyshaw89 reverted back now to only my changes

@MIslam92 all of them?

@jonnyshaw89 yes allllll of them 🙃

repo: ONSdigital/eq-survey-runner


text:
Add config file

What? and Why?

What does this pull request change/fix? Why was it necessary?

Move all service config to app config file. Should make config easier to maintain.
Checklist

[x] CHANGELOG.md updated? (if required)

Codecov Report

Merging #45 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #45   +/-   ##
=======================================
  Coverage   84.59%   84.59%
=======================================
  Files           6        6
  Lines         331      331
=======================================
  Hits          280      280
  Misses         51       51

Continue to review full report at Codecov.

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

 Continue to create config.ini files for SDX services

repo: ONSdigital/sdx-sequence


text:
opae.cfg: touch up config file for d5005

Signed-off-by: Tim Whisonant tim.whisonant@intel.com

Coverage remained the same at 65.346% when pulling 51454c4b7b189df078e982112449e90f98b5c899 on tswhison/d5005_cfg into 8faf6064f8447e5916772501b301ce9d43a64f8d on feature/config-file.

authors: coveralls tswhison

repo: OPAE/opae-sdk


text:
DocsArchive-15.0.0.0Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/717 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target.git

Docs Build status updates of commit bde9079:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-01-26-02-33-58 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit bde9079:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-01-26-02-33-58 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

authors: VSC-Service-Account v-alji


text:
DocsArchive-15.0.0.0Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_a9f3e1d2-a06c-4107-bfce-42913cfa4dea/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_a9f3e1d2-a06c-4107-bfce-42913cfa4dea.git

Docs Build status updates of commit 08ce394:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


text:
DocsArchive-1.0.0.0Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit bf28615:
:clock10: Pending: waiting for processors (47 builds ahead of you)
:warning: Docs Build is busy, currently there are 47 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit bf28615:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-11-20-07-36-34 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Archive_master_2019-11-20-07-36-34

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
:(

What am I doing with my life...

Codecov Report

Merging #176 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #176   +/-   ##
=======================================
  Coverage   87.21%   87.21%
=======================================
  Files          53       53
  Lines        2846     2846
=======================================
  Hits         2482     2482
  Misses        364      364

Impacted Files
Coverage Δ

source/dealii/dealii_solver.cc
96.29% <ø> (ø)
:arrow_up:

include/mfmg/common/amge.templates.hpp
87.81% <ø> (ø)
:arrow_up:

tests/hierarchy_driver.cc
45.06% <ø> (ø)
:arrow_up:

source/dealii/dealii_matrix_free_smoother.cc
86.66% <ø> (ø)
:arrow_up:

source/dealii/dealii_hierarchy_helpers.cc
99.06% <ø> (ø)
:arrow_up:

.../mfmg/dealii/dealii_matrix_free_mesh_evaluator.hpp
0% <ø> (ø)
:arrow_up:

include/mfmg/common/smoother.hpp
100% <ø> (ø)
:arrow_up:

tests/test_laplace.cc
100% <ø> (ø)
:arrow_up:

include/mfmg/common/hierarchy_helpers.hpp
25% <ø> (ø)
:arrow_up:

...mg/dealii/dealii_matrix_free_hierarchy_helpers.hpp
100% <ø> (ø)
:arrow_up:

... and 42 more

Continue to review full report at Codecov.

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

codespell ?

vim spell

Great commit message. Super useful when someone is looking at the history...

authors: Rombur aprokop codecov-io masterleinad

repo: ORNL-CEES/mfmg


text:
CPPMicroservices fail two tests

On branch devel: After I have updated TensorMethod interface, which is now called TensorFunctor, two tests (NumServerTester, TensorRuntimeTester) began to fail with that below. I have no idea why it is complaining now as I see no relation to CPPMicroservices in my changes. Note that I built the MPI version of ExaTN (gcc/8.2.0, mpich/3.2.1).
terminate called after throwing an instance of 'std::runtime_error'
what():  Bundle#3 start failed: libantlr4-runtime.so.SOVERSION: cannot open shared object file: No such file or directory
Aborted

I have just built the same devel branch without MPI, it passes the tests. Alex, apparently something got screwed up in the MPI-enabled build with respect to CPPMicroservices configuration. Could you please check?

I just built, installed, and ran tests with OpenMPI and everything worked fine. Also note that the CI is building everything with CUDA and MPICH, and the tests/CI are still passing.

Hmm, do you have any idea why CPPMicroservices is trying to open libantlr4-runtime.so.SOVERSION with unresolved version on my machine?

CppMicroServices is not necessarily trying to open libantlr, but it is trying to load the libexatn-taprol-parser.so plugin, which links to libantr4. And if it can't make that link, then the plugin will not load, and CppMicroServices will throw the error.

This was due to CMake appending suffix 'd' to libraries on debug builds. Turning that off...

authors: DmitryLyakh amccaskey

repo: ORNL-QCI/exatn


text:
random seg fault in antlr-gen pyxasmparser

(gdb) bt
#0  0x00007ffff6907a08 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#1  0x00007ffff6908d53 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#2  0x00007ffff690974d in _Unwind_Find_FDE () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#3  0x00007ffff6905848 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#4  0x00007ffff6906a10 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#5  0x00007ffff6906f89 in _Unwind_RaiseException () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#6  0x00007ffff69bb78c in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x00007ffff4458eb3 in pyxasm::pyxasmParser::expr_stmt (this=0x7fffffff8cb0) at ../handlers/token_collector/pyxasm/generated/pyxasmParser.cpp:2272
#8  0x00007ffff445819f in pyxasm::pyxasmParser::small_stmt (this=0x7fffffff8cb0) at ../handlers/token_collector/pyxasm/generated/pyxasmParser.cpp:2017
#9  0x00007ffff445788c in pyxasm::pyxasmParser::simple_stmt (this=0x7fffffff8cb0) at ../handlers/token_collector/pyxasm/generated/pyxasmParser.cpp:1888
#10 0x00007ffff444f1f8 in pyxasm::pyxasmParser::single_input (this=0x7fffffff8cb0) at ../handlers/token_collector/pyxasm/generated/pyxasmParser.cpp:128
#11 0x00007ffff44b9b99 in qcor::PyXasmTokenCollector::collect (this=0x7fffe806dd70, PP=..., Toks=..., bufferNames=std::vector of length 1, capacity 1 = {...}, ss=...)
    at ../handlers/token_collector/pyxasm/pyxasm_token_collector.cpp:188
#12 0x00007fffe1e44d10 in qcor::run_token_collector (PP=..., Toks=..., bufferNames=std::vector of length 1, capacity 1 = {...}) at ../handlers/token_collector/token_collector_util.cpp:198
#13 0x00007fffe5652a1e in qcor::QCORSyntaxHandler::GetReplacement (this=0x7fffffffa040, PP=..., kernel_name="ansatz", program_arg_types=std::vector of length 2, capacity 2 = {...},
    program_parameters=std::vector of length 2, capacity 2 = {...}, bufferNames=std::vector of length 1, capacity 1 = {...}, Toks=..., OS=..., add_het_map_ctor=true)
    at ../handlers/qcor_syntax_handler.cpp:85
#14 0x00007fffe682e219 in qcor::QJIT::run_syntax_handler (this=0x1e6fed0,
    kernel_src="__qpu__ void ansatz(qreg q,double theta) {\nusing qcor::pyxasm;\n\n", ' ' <repeats 12 times>, "X(q[0])\n", ' ' <repeats 12 times>, "Ry(q[1], theta)\n", ' ' <repeats 12 times>, "CX(q[1], q[0])\n}\n", add_het_map_kernel_ctor=true) at runtime/jit/qcor_jit.cpp:218

It seems like the CI machine still had SEGFAULT at the end of the qcor_simple_kernel_jit_python test. It ran all test cases successfully. Other Python tests were fine as well.
Need to look into it.
See: https://code.ornl.gov/qci/qcor/-/jobs/908237
I didn't observe it locally, hence will try to reproduce

It seems like the CI machine still had SEGFAULT at the end of the qcor_simple_kernel_jit_python test. It ran all test cases successfully. Other Python tests were fine as well.
Need to look into it.
See: https://code.ornl.gov/qci/qcor/-/jobs/908237
I didn't observe it locally, hence will try to reproduce

Fixed in https://github.com/ORNL-QCI/qcor/pull/78. Hence, closing.

Fixed in https://github.com/ORNL-QCI/qcor/pull/78. Hence, closing.

authors: amccaskey tnguyen-ornl

repo: ORNL-QCI/qcor


text:
Charts and Visualizations

charting? protovis?

what about http://www.jqplot.com/

repo: OSBI/saiku-ui


text:
FLEX-3150 ~ Get and set device configuration

There are a lot of changes, because the save settings are different.

Can one of the admins verify this patch?

Ok to test

This pull request makes the build fail.

repo: OSGP/Integration-Tests


text:
improve SEO

try googling a sample EPSG code, such as "epsg 3978"
notice that the spatialreference.org associated page is not highly ranked (if at all)
view-source of that page, and you'll see missing meta tags for description, keywords etc (that help search engines crawl the pages)
other tips for discovery (this is nothing new) include managing your site in the Google Search Console, setting up a sitemap for your site, etc.

Maybe try adding a description tag first?
For comparison, view-source of https://epsg.io/3978

Hi @jmckenna
I know that unfortunately we are not very high in the rank. To be honest, I am surprised that in 2024 search engines are making any difference if there is data in the description tag that is already in the content of the page. It would be basically duplicating the text. The main information is already in the title tag (code and name)!
About the sitemap, https://github.com/OSGeo/spatialreference.org/pull/17 is there since March
If you let me be evil, I understand that epsg dot io is better ranked: it has a lot of adds from Google. We have none. That makes our page less interesting to be visited for the adds provider... that is also the search engine. But maybe I am too suspicious.

Hi @jjimenezshaw I've found that even in 2024, doing the basics still helps.  For example, I notice that we lack a robots.txt, for machines to crawl. (see how-to)
I'm also ok to close this ticket now, someday someone can come back to tackle, and re-open.

I will add a non restrictive robots.txt (2 lines) and the description and keywords tags... just repeating the information that is already there.
Probably it is more effective that other pages link to ours... but I have no control over that ;)

This tool is giving some insights:
https://seorch.net --> URL: https://spatialreference.org/
Besides many good SEO test results there are also some issues listed. Summary:

No Meta Description found.
The  Tag is too short: 25 characters.
The  Tag has too few words: 3.
The website text is too short: 54 words. Text length should be more than 400 words.
Links without TITLE attribute: 15
No <h1> Tags found. (Missing heading)
No robots.txt found.

Thanks @neteler that is giving some useful tips.
I run it in a specific CRS, and it gives slightly different (but similar) results. I think what we want to be reached per CRS, that is what people search.
What make me nuts is the "The  Tag has too few words: 3." Really? Look at the title of a Google page ;)

What make me nuts is the "The  Tag has too few words: 3." Really? Look at the title of a Google page ;)

Seorch is not my system, I was just the messenger :-)

thanks @jjimenezshaw, worth a try!

I have made an attempt to add an intro in #26.
Still, pages like https://spatialreference.org/ref/epsg/3978/ are looking pretty nerdy to me.
For people coming directly to this page, it may not be obvious what this is all about :-)
So, what about adding some text between
EPSG:3978
and
NAD83 / Canada Atlas Lambert
?

Update: trying the search from above again:
https://www.google.com/search?q=epsg+3978
Now (at least here in Germany) this site ranks 3rd, so the situation slowly  seems to improve.

Agreed, improving (2nd result here).

authors: jjimenezshaw jmckenna neteler


text:
BUG: Entrypoint sentinel with TLS enabled bug

I noticed that the port setup for sentinel is being done like so:
port_setup() {
        {
            echo port "${SENTINEL_PORT}"
        } >> /etc/redis/sentinel.conf
}

And the port and tls_port are being defined in the tls_setup() function.
However, since port_setup runs after tls_setup I think the port=0 definition from tls_setup is being overriden by port setup.

And also in the entrypoint for redis I think the TLS setup is not right either:
if [[ "${SETUP_MODE}" == "cluster" ]]; then
            {
                echo tls-replication yes
                echo tls-cluster yes
            } >> /etc/redis/redis.conf

The tls-replication yes should be in an else I believe.

Thank you for pointing it out. The first issue has been fixed by #81

Thank you for pointing it out. The first issue has been fixed by #81

Thank you, do you know when a new image will be issued with this fix?

Thank you, do you know when a new image will be issued with this fix?

Sorry, I'm not sure about the exact time.

You can try the latest v6.2.14 v7.0.15 @Leo791

repo: OT-CONTAINER-KIT/redis


text:
Upgrade dependency

Upgrade jsonwebtoken@8.5.1 to version 9.0.1

Added by OX Security


text:
Update vulnerable packages

Update vulnerable packages
There are two packages left with critical errors.
xmlhttprequest-ssl
Used in: @myetherwallet/mewconnect-connector.
Chain of dependency: @myetherwallet/mewconnect-connector > @myetherwallet/mewconnect-web-client > socket.io-client > engine.io-client > xmlhttprequest-ssl
This package is deprecated, so it may takes some time to fix it.
json-schema
Used in: snowflake-sdk, node-sass, @oasisdex/web3-context, @oasisdex/connectors, web3, @oasisdex/connectors, @myetherwallet/mewconnect-connector.
This package is used seven dependencies, but the problem is that it is a deep dependency of dependency of dependency (...), that always ends in the same place. This package in problematic version is used in request which is deprecated and even newest version causes this error. Some of the dependencies are our internal commons from @oasisdex and maybe they don't need request at all, but that doesn't solve others. Needs deep investigation if they can be updated.
Changes 👷♀

linked ejs to resolution in version ^3.1.7

MEW has new connector, so fix will be to use new dependency https://app.shortcut.com/oazo-apps/story/3984/use-new-mew-connector

authors: johnnieskywalker piotrkonowrocki

repo: OasisDEX/oasis-borrow


text:
Add swap functionality and enhance SDK integration

Introduce swap capabilities to the deposit process, improve UI components, and enhance SDK logging and error handling. Refactor asset management for better token swapping and deposit logic.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (dev@c5a64f5). Learn more about missing BASE report.

Additional details and impacted files
@@          Coverage Diff           @@
##             dev     #599   +/-   ##
======================================
  Coverage       ?   70.16%
======================================
  Files          ?      129
  Lines          ?     1354
  Branches       ?       78
======================================
  Hits           ?      950
  Misses         ?      404
  Partials       ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter piotrwitek

repo: OasisDEX/summerfi-monorepo


text:
Long data in JSON formatter freezes the app, when you relaunch reloads same JSON and freezes again.

I've pasted a huge JSON data to format but the app stopped responding, and I killed it, when I relaunch the app, it reloads the same JSON data and freezes again. Is there a clear cache function?
Removing the app didn't work.

I've pasted a huge JSON data to format but the app stopped responding, and I killed it, when I relaunch the app, it reloads the same JSON data and freezes again. Is there a clear cache function?
Removing the app didn't work.

There is a stopgap. Just remove this file (~/Library/Preferences/com.yuki.DevToys.plist)

repo: ObuchiYuki/DevToysMac


text:
Performance with daily and hourly fields

Hello,
I am new to Parcels and my team and I are facing a problem of performance:
Usually, we perform simulations with daily forcing files (CMEMS PSY4, surface extracted) with 5000 particles. When using hourly forcing files, we expected the execution to be 24 times more slowly than simulations with daily forcing files. However, it is not the case as you can see in the following figures from a small test :

You can see than the time ratio hourly/daily is around 24 for short simulations but is then increasing linearly with simulation time. In this study we let chunksize to default.
Is there an explanation for this behaviour ?
Thanks for your help .
Julien.

Thank you @julien-temple, for reporting this! This indeed does not look very good. Can I ask which version of parcels you are using? The latest on conda? Or the latest master branch from github?
Because we have recently implemented two changes (#976 and #978) that potentially speed up Parcels significantly, especially if you use dask chunking and/or if your input files are very large so that they don't fit into memory well (and consequently trigger swap-memory).

Thank you @julien-temple, for reporting this! This indeed does not look very good. Can I ask which version of parcels you are using? The latest on conda? Or the latest master branch from github?
Because we have recently implemented two changes (#976 and #978) that potentially speed up Parcels significantly, especially if you use dask chunking and/or if your input files are very large so that they don't fit into memory well (and consequently trigger swap-memory).

Thank you for your response. We are using parcels 2.2.0 on conda.

Thank you for your response. We are using parcels 2.2.0 on conda.

OK thanks; would you mind trying with the latest version of parcels from the github master branch?

OK thanks; would you mind trying with the latest version of parcels from the github master branch?

Sure, I just installed it. I am performing the same test to see if there is a different behaviour. Thank you again.

Sure, I just installed it. I am performing the same test to see if there is a different behaviour. Thank you again.

Indeed, the execution is now really faster. We can see it with the following figures. The ratio hourly/daily is around 24 and does not increase as it used to :

Thank you very much !

Indeed, the execution is now really faster. We can see it with the following figures. The ratio hourly/daily is around 24 and does not increase as it used to :

Thank you very much !

That is very good to hear; I'm really glad about this! Pinging @CKehl and @reint-fischer, so that they are aware too that the latest master (237d85b) has much better performance
By the way, it's hard to see from the graphs but is the 'Daily forcing files' run also faster; or is it roughly the same speed as before?

That is very good to hear; I'm really glad about this! Pinging @CKehl and @reint-fischer, so that they are aware too that the latest master (237d85b) has much better performance
By the way, it's hard to see from the graphs but is the 'Daily forcing files' run also faster; or is it roughly the same speed as before?

For daily fields, the execution time is almost the same for both parcels versions. The following figure plot execution time (with daily fields, 20 particles) for both 2.2.0 version and last version from master branch :

For daily fields, the execution time is almost the same for both parcels versions. The following figure plot execution time (with daily fields, 20 particles) for both 2.2.0 version and last version from master branch :

authors: erikvansebille julien-temple

repo: OceanParcels/parcels


text:
Remove abandoned claim from Uploads Page

Issue
Ticket: #108
Interesting
Uploads Page uses claim_list
Channel Page uses claim_search
A second claim_list would instantly show updated results, but claim_search takes a long while to reflect the deletion.  If both are waiting for a transaction, why did claim_list work as expected?
Change
This PR only handles the claim_list (Uploads Page).
Aside
The claim_search version would be troublesome to handle. If a refresh would bring back the results (due to the claim_search slow update behavior), we would need to store the deleted claim persistently. Then ...

Store where? rehydrate?
When to clear?
How to make each ClaimList filter this out without polluting the code? etc.

...will be messy. Feels easier to "fix" at the claim_search to make it update faster like claim_list.

Probably not worth handling until the SDK can mempool resolve, and then this will fix itself. Claim list uses local wallet data, which is why it's able to reflect right away.

authors: infinite-persistence tzarebczan

repo: OdyseeTeam/odysee-frontend


text:
Another multisig test

When I was recently preparing the Substrate update in #67, I was briefly confused about the tests on the ThresholdMultisig. Once I read the tests carefully, I understood them and quickly got them passing.
However, I noticed that there was not a test for the case where the redeemer contains more than enough valid signatures. This PR adds a single test for when there is a 2/3 multisig, and the redeemer contains valid sigs for all three signatories even though only two are required. I expected this case to still successfully verify, but it seems it is not.
@coax1d is this the behavior you expected?

Looks good tho good test to add!

repo: Off-Narrative-Labs/Tuxedo


text:
SharedFunctions.ps1 issues

There are some illegal characters in this script Lines 331, 1161, 1456,
Also error on Line 331:
$defaultDisplayPropertySet = New-Object System.Management.Automation.PSPropertySet(�DefaultDisplayPropertySet�,[string[]]$defaultDisplaySet
And issue on line 1454:
If (-NOT ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole(`
[Security.Principal.WindowsBuiltInRole] Administrator))

Thank you for the feedback. The issues have been corrected and will be updated shortly.

authors: AStigall daltskin


text:
Add DocxToSource to the list of Related Tools in the README.md file.

Still actively working on this project but there is working code available.

Thank you.

repo: OfficeDev/Open-XML-SDK


text:
Loggingfixes

The Log.cs class contains some apparent copy/paste bugs. For example that the Warning methods aren't checking if the logLevel is actually warning or debug, but only debug.. Or that the same method checks for logLevel "information" rather than "debug" (there's a separate method for logLevel == Information)..
Also fixed a bug where one of the Error methods were incorrectly calling .Info() instead of .Error().

Hi @Zimmergren, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Very good catch! Thank you Tobias!

authors: Zimmergren erwinvanhunen msftclas

repo: OfficeDev/PnP-Sites-Core


text:
Optimize EwsXmlReader.readValue

I faced with a performance problem. To investigate this issue, I run ExchangeService.findAppointments many times and got the following summary statistic:

ExchangeService.findAppointments - 102 sec.

EwsXmlReader.readValue - 21 sec.

String.format - 14 sec.

EwsXmlReader.readValue uses String.format always (even when it is completely unnecessary). This PR improves this situation and prevents all unnecessary calls of String.format in this method.
It is only the one place where we can improve ExchangeService.findAppointments. I decided to not send all improvements to simplify code review.

Hi @vbauer, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@vbauer, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, AZPRBOT;

I've just updated PR (it was merged with master).

Thank you for merge.

thanks for the contribution ;)

authors: azurecla serious6 vbauer

repo: OfficeDev/ews-java-api


text:
Use gradle instead of maven

This PR disables maven support and moves the project to be managed with gradle. This enables us to:

delete all files in /.idea
let gradle generate a pom.xml
extend build.gradle easily

After merging this PR the project files will be generated with gradle. Just open a shell or cmd and execute gradlew idea on the project root. This will generate all needed files and also integrate google-style and file-encoding.

Hi @serious6, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

:+1: to get rid of /.idea files from source control!

ref. #235

closed for now

authors: azurecla serious6 vboctor


text:
vanilla project: Error: The dev server is not running on port 3000.

Hello,
I am following the 'Any Editor' version of the tutorial. I "yo office" with the appropriate settings, cd into dir and 'npm start' but the local webserver does not start with console message:
Starting the dev server... (webpack-dev-server --mode development)
Unable to start the dev server. Error: The dev server is not running on port 3000.
Powerpoint will open with an
'Add-in Error':
This add-in is no longer available. If this add-in's manifest was removed, please restore it to its previous location and try again.
Any suggestions?

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

ID: 50a89144-ac19-b28e-2842-5e2cbdb1cb00
Version Independent ID: cb59df19-9c22-de2c-0c46-7a1403312987
Content: Build your first PowerPoint task pane add-in - Office Add-ins
Content Source: docs/quickstarts/powerpoint-quickstart.md
Product: powerpoint
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

Hi @12s - Thanks for trying out Powerpoint add-ins submitting an issue about this! Our docs team will take a look and get back to you. As the Microsoft //build conference happens this week, we may take a few days to respond as our team is busier than normal.

@12s I tried this on a Windows 10 machine but it's working. Can you share more details about your setup (e.g. OS, Office version)?
@akrantz @TCourtneyOwen: Any suggestions that may help here?
Thanks.

I am running macOS Mojave 10.14.4
I installed the current version of generator-office

Microsoft PowerPoint for Mac
Version 16.16.9

So, in the mean time I have been developing on my windows machine where everything has been working as expected.
I do have a more pressing issue now.  Basically this stack post:
https://stackoverflow.com/questions/35744466/javascript-interaction-with-powerpoint-documents/35784313#
The post is from 3 years ago so I'm hoping there is a solution, but I too can't get any additional slide information from getSelectedDataAsync other than Id, title and index.
Is this still the case?

@12s:

Regarding your initial issue: on the yo office readme, there's a note for Mac developers to use Node Version Manager. There may be other tips for Mac in that repo so please take a look.
Per current docs for getSelectedDataAsync, it hasn't moved much further since then. I invite you to use UserVoice to suggest/upvote this feature as we consider UserVoice when we plan upcoming work.

Thanks again for raising the issues.

I'll go ahead and close this now but let us know to reopen it if you're still facing an issue.

Hi!
I'm having the same issue on the same system as 12s. I tried to use Node Version Manager, which on its own went smooth but didn't help regarding this.
I would be grateful for any ideas of how to make this error go away.

Well, I seem to have found the solution right now. sudo npm start was a success.

@JanZelenka: It's good that you're unblocked but we don't recommend using sudo as a long-term solution since that would seem to indicate there are still some permission/config issues.
@12s: Did you get a chance to try NVM? If so, can you share your results?
Thanks.

I know what the problem is. We've updated the Yo Office templates to make it easier to generate and install certificates for https://localhost. When "npm run dev-server" or "npm build" is done, the webpack config has a plugin which will generate the certificates and then prompt for permission to install them. The "npm start" command wll start the dev server as a detached process if it has not already been started, but the command output is not shown. Therefore, when "npm start" is used and the dev server is not already running, if dev certs need to be installed, the prompt cannot be seen, and after 30 seconds, the start command will stop waiting for the dev server to be started and show the error "Unable to start the dev server. Error: The dev server is not running on port 3000."
The workaround is to do one of the following:

Run npx office-addin-dev-certs install. Enter the password when prompted.
Run npm run dev-server before running npm start. Enter the password when prompted.
Open the project in VS Code. Use Terminal, Run Task, Dev Server to run the dev server inside VS Code. Enter the password when prompted.

There is a difference on Windows where the need to accept installing the dev certs is a dialog that appears rather than simply asking for the password to be entered from the command line. Therefore, this is not a problem on Windows.
I usually do #3 above, and in fact the task is set up to automatically start the Dev Server task when the folder is opened in VS Code, if you enable automatic tasks for the folder.

@akrantz: Thanks for your response. We'll see how we can incorporate this info with the various quick starts and tutorials.
@12s, @JanZelenka: Can you try this and let us know the outcome? Thanks.

@ElizabethSamuel-MSFT It would help to update the docs with information about this problem on Mac.
It is probably best to have them do npm run dev-server first, so there is a visible window showing the dev-server output, then Command+T to open a new tab (since the dev server keeps running), and then npm start.
Alternatively, if the instructions are focused on using VS Code, I would recommend doing everthing in VS Code. I find this a better approach because when I close VS Code, it automatically closes the associated dev server.
Glad to discuss more or review doc changes. Thanks.

Thanks for the quick response!
I have tried npm run dev-server and afterwards npm start in a new tab, got no errors and the web server is happily running.
Grateful your help!

@JanZelenka I'm glad to hear it!

Yes, running npm dev-server before npm start shows
"the dev server is already running on port 3000" correctly, followed by "Debugging started".
When powerpoint opens I see the same "Add-in Error" thinking the manifest is missing.
I'll keep trying to debug the issue, but without an API endpoint to get and set text (beyond the slide title from getSlideMetadata) my project won't go far :(

@12s Glad that the server is up and running now.
Regarding the "Add-in error", can you try sideloading the add-in? Let us know if that helps.
Thanks.

We've updated the tutorials and quick start with Mac guidance. Those updates should be go live this week.

Hey Elizabeth,
Looking forward to the Mac guide. I'll follow along when its up.

@12s We look forward to hearing your feedback on that. However, were you able to try sideloading the add-in? Thanks.

Waiting for the Mac guides as well here 🙏 ! In the mean time I followed @akrantz suggestion https://github.com/OfficeDev/office-js-docs-pr/issues/978#issuecomment-493118079

Closing this as the changes are live. We appreciate all the input on this. If you're still facing issues, let us know. Thanks.

I have the same issue and it is because I have a space in my username :(

authors: 12s ElizabethSamuel-MSFT JanZelenka Wolfthorne akrantz esbanarango mscharlock

repo: OfficeDev/office-js-docs-pr


text:
Update runtime logging info

Fixes #521.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/troubleshoot-manifest.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/troubleshoot-manifest.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
[Admin] (docs metadata) Update metadata attribute values for docs.

This PR updates metadata attribute values to improve our ability to generate reports about this doc set. It does the following:

sets metadata attribute ms.technology to add-ins for all files in this doc set (by using globalMetadata config setting in docfx.json)
sets metadata attribute ms.prod to the appropriate value in all files (by using fileMetadata config setting in docfx.json where feasible, and otherwise by setting this metadata attribute value in individual .md files)

ms.prod values set at the folder-level for the following folders:

folder
ms.prod value

concepts
non-product-specific

design
non-product-specific

develop
non-product-specific

excel
excel

onenote
onenote

overview
non-product-specific

powerpoint
powerpoint

project
project

publish
non-product-specific

reference
non-product-specific

reference/manifest
non-product-specific

reference/objectmodel/**/
outlook

resources
non-product-specific

testing
non-product-specific

word
word

ms.prod values set at the file-level for files in the following folders:

quickstarts
tutorials
reference/overview
reference/requirement-sets

OPS Build status updates of commit c5bc52f:
:clock10: Preparing: average preparing time is 44 sec(s)

OPS Build status updates of commit c5bc52f:
:clock10: Full build: average full build time is 38 sec(s) [calculated from last 3 build(s)]

Note: A full build takes more time than an incremental build.  This is the expected behavior of the build system.

OPS Build status updates of commit c5bc52f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/docfx.json
:white_check_mark:Succeeded

docs/index.yml
:white_check_mark:Succeeded

docs/quickstarts/excel-quickstart-angular.md
:white_check_mark:Succeeded

docs/quickstarts/excel-quickstart-jquery.md
:white_check_mark:Succeeded

docs/quickstarts/excel-quickstart-react.md
:white_check_mark:Succeeded

docs/quickstarts/excel-quickstart-vue.md
:white_check_mark:Succeeded

docs/quickstarts/onenote-quickstart.md
:white_check_mark:Succeeded

docs/quickstarts/powerpoint-quickstart.md
:white_check_mark:Succeeded

docs/quickstarts/project-quickstart.md
:white_check_mark:Succeeded

docs/quickstarts/word-quickstart.md
:white_check_mark:Succeeded

docs/reference/overview/excel-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/onenote-add-ins-javascript-reference.md
:white_check_mark:Succeeded

docs/reference/overview/visio-javascript-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/word-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/add-in-commands-requirement-sets.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/dialog-api-requirement-sets.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/excel-api-requirement-sets.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/identity-api-requirement-sets.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/office-add-in-requirement-sets.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/onenote-api-requirement-sets.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/outlook-api-requirement-sets.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/powerpoint-and-project-note.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/word-api-requirement-sets.md
:white_check_mark:Succeeded

docs/tutorials/excel-tutorial-create-custom-functions.md
:white_check_mark:Succeeded

docs/tutorials/excel-tutorial.md
:white_check_mark:Succeeded

docs/tutorials/powerpoint-tutorial.md
:white_check_mark:Succeeded

docs/tutorials/word-tutorial.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@lindalu-MSFT the APEX team recently whitelisted the following combinations of ms.prod and ms.technology attribute values for the Add-ins docs, so this PR updates the values of those attributes in OfficeDev/office-js-docs-pr.

Can you please review this PR? Thanks!

Hi @kbrandl , I saw this after I created the PR to merge to live. After I review, I'll merge this and push live again! Sorry for going about this backwards today!

@kbrandl I didn't squash and merge, for some reason I don't see the big ole green button... shouldn't it appear in front of me when I use the GitHub UI? At any rate, I'll check more closely next time. This merge, you'll see them all over again in the merge to live PR.

authors: kbrandl lindalu-MSFT o365devx


text:
loading image array Still having problems

Hi Thanks for the library, it is quite interesting! It hides a lot of problems and make it easy to use and train new models. Really nice work!
However I am trying to load the numpy array instead the file, and I am having some problems! I already saw the problem #49, but it didn't solve for me.
from PIL import Image
import numpy as np
image_arr = np.asarray(Image.open('/tmp/2.jpg'), dtype='float64')
detections = detector.detectObjectsFromImage(input_type="array", input_image=image_arr)
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/imageai/Detection/init.py", line 347, in detectObjectsFromImage
_, _, detections = model.predict_on_batch(np.expand_dims(image, axis=0))
File "/usr/local/lib/python3.6/dist-packages/keras/engine/training.py", line 1273, in predict_on_batch
self._make_predict_function()
File "/usr/local/lib/python3.6/dist-packages/keras/engine/training.py", line 554, in _make_predict_function
**kwargs)
File "/usr/local/lib/python3.6/dist-packages/keras/backend/tensorflow_backend.py", line 2744, in function
return Function(inputs, outputs, updates=updates, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/keras/backend/tensorflow_backend.py", line 2546, in init
with tf.control_dependencies(self.outputs):
File "/home/daniel/.local/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 5426, in control_dependencies
return get_default_graph().control_dependencies(control_inputs)
File "/home/daniel/.local/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 4867, in control_dependencies
c = self.as_graph_element(c)
File "/home/daniel/.local/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3796, in as_graph_element
return self._as_graph_element_locked(obj, allow_tensor, allow_operation)
File "/home/daniel/.local/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3875, in _as_graph_element_locked
raise ValueError("Tensor %s is not an element of this graph." % obj)
ValueError: Tensor Tensor("regression_1/concat:0", shape=(?, ?, 4), dtype=float32) is not an element of this graph.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/IPython/core/interactiveshell.py", line 3325, in run_code
exec(code_obj, self.user_global_ns, self.user_ns)
File "", line 1, in
detections = detector.detectObjectsFromImage(input_type="array", input_image=image_arr)
File "/usr/local/lib/python3.6/dist-packages/imageai/Detection/init.py", line 544, in detectObjectsFromImage
"Ensure you specified correct input image, input type, output type and/or output image path ")
ValueError: Ensure you specified correct input image, input type, output type and/or output image path
I am using:

Python 3.6
ImageAI 2.1.5

Even though for me the ideal would be to use the open from scikit. It allows you to read files and
urls the same way... so it is more convenient, you don't need to get worried if it is a file or an url.
from skimage import io
import numpy as np
url='https://file.kbb.com/kbb/images/car-research/researchheroimage-retina.png'
image=io.imread(url)
image_arr = np.asarray(image, dtype='float64')
detections = detector.detectObjectsFromImage(input_type="array", input_image=image_arr)
basically gives me the same error!!
Do you have any idea?

Try modifying this line:
image_arr = np.asarray(Image.open('/tmp/2.jpg'), dtype=np.uint8)

FOUND the reason, you get that if you don't set the "output_image_path" to a real file!
In my case I don't need the output_image_path at all, even if I point it to /dev/null I got the error!
I looked into your code, and by default the output is a file, if I don't provide a file name for the
output everything breaks.
This work though, changing the input type to array.
from skimage import io as sk_io
from imageai.Detection import ObjectDetection
from imageai.Prediction import ImagePrediction
models directory path
modelsPath = "."
Detection model, loaded just once for performance purposes
detector = ObjectDetection()
detector.setModelTypeAsRetinaNet()
detector.setModelPath( os.path.join(modelsPath, "resnet50_coco_best_v2.0.1.h5"))
detector.loadModel()
detectedValues=detector.detectObjectsFromImage(input_type="array",
input_image=image, output_type="array")
print(detectedValues)
Maybe could be a good idea of improvement to the library could be to test if the input_type is "file", and no output_image_path is provided, return a more explicit error message.
Again thanks for the library and rola93 for the comment :)

Maybe a good idea of improvement to the library, could be to add a test if the input_type is "file", and no output_image_path is provided, return a more explicit error message.

Great idea! for sure there are things to improve here. Thanks for your time!

repo: OlafenwaMoses/ImageAI


text:
Can't find babel-loader

bastion searches modules in it's own node_modules. It's incorrect with npm3 https://docs.npmjs.com/how-npm-works/npm3.

I solved it by creating a symlink.

Ah, I see, thanks for the report. I've had a few issues with referencing node modules, I expected some bugs around this area. I wonder if there's an API I can call to get the path to it. It's a shame npm@2 and npm@3 behave so differently.

I think it's because Windows handles badly long file paths ;)

Probably an npm@2 / npm@3 issue mainly. May look into it some day. If you want to fork the project and try it out, go ahead.

authors: Olical Yamakaky

repo: Olical/bastion

license: unlicense


text:
Vim:E731 error when slurping gzipped file in clojure

Description
When using the below reproduction steps I get the following error:
; eval (root-form): (->> "/Users/oliverm/pro...
; --------------------------------------------------------------------------------
; localhost:64309 (Vim:E731: using Dictionary as a String): .nrepl-port

I'm not sure of the route cause of this, but I was at least able to reproduce :D
Steps to reproduce
$ lein new gzip_bug
$ cd gzip_bug
$ echo "hi" > resources/my_file
$ gzip resources/my_file
$ cat > src/test/core.clj
(ns test.core)

(->> "./resources"
     clojure.java.io/file
     file-seq
     (remove #(.isDirectory %))
     (map slurp))
# NOTE: press Ctrl-D here
$ nvim src/test/core.clj

# (in another shell)
$ cd gzip_bug
$ lein repl

# Then finally execute the form using :ConjureEvalBuf

The full session log is:
; Sponsored by @Aljendro ❤
; --------------------------------------------------------------------------------
; localhost:64309 (connected): .nrepl-port
; --------------------------------------------------------------------------------
; Assumed session: Bernese Mountain Dog (Clojure)
; --------------------------------------------------------------------------------
; eval (buf): ...j/test/src/test/core.clj
nil
; --------------------------------------------------------------------------------
; localhost:64309 (Vim:E731: using Dictionary as a String): .nrepl-port

I don't think this will happen any more 🤔 I think it was a temporary bug from when I was adding a notification about what nREPL port file was used for the connection. I'll investigate but if you could check again and see if you can reproduce it that'd be super helpful! Thanks for the thorough report!

I can repro! Investigating.

I've worked out it's when this null byte is in the output string.
{:id "130d6fe2-db52-45b7-97d2-a246c4a9a006"
 :ns "test.core"
 :session "fcba79ee-903c-4543-b4da-5e3e7fcfc1ff"
 :value "((\\\031 \\� \\backspace \\backspace \\� \\� \\� \\` \\\000))"}

Now to work out why and get around it...

Minimal repro: :ConjureEval "\0".

That's amazing, thanks for the hard work 😁
On Sat, 12 Jun 2021, 17:09 Oliver Caldwell, @.***>
wrote:

Minimal repro: :ConjureEval "\0"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Olical/conjure/issues/212#issuecomment-860074187, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACD2NAW3JO3SC6D7XYVINWLTSOBDFANCNFSM457E7XYQ
.

I've realised you can also reproduce it in Janet! And I've narrowed it down to the line that causes it! This is probably the trickiest bug I've ever hit with Conjure, so congratulations 😅
https://github.com/Olical/conjure/blob/643ae9bf5f08e752a22027628b69a31ce271f1b5/fnl/conjure/eval.fnl#L66
My current hunch is that the null byte is hitting a bug in Neovim's Lua to VimL interop layer. I'll have to see if I can work around it for now and get a repro for the Neovim team to address at some point.

Minimal repro without Conjure involved at all.
(vim.fn.setreg "x" "\0")

I've pushed a workaround for this to develop, I'll raise a bug with Neovim or at least find an existing one.

I couldn't find a related bug so I've opened one: https://github.com/neovim/neovim/issues/14801

That's amazing, thanks so much for figuring it out!

authors: Akeboshiwind Olical

repo: Olical/conjure

license: Unlicense


text:
Support creation of raw transactions with non-wallet inputs

Four new RPCs are added to create or modify raw transactions with non-wallet inputs:

add a payload with class B encoding (omni_createrawtx_multisig)
add a payload with class C encoding (omni_createrawtx_opreturn)
add a transaction input (omni_createrawtx_input)
add a reference output (omni_createrawtx_reference)
add a change output (omni_createrawtx_change)

See the JSON-RPC API documentation.
The core components are the new TxBuilder and OmniTxBuilder classes.
See the class documentation.
Five new parsing helpers are added:

ParseTransaction()
ParseMutableTransaction()
ParsePubKeyOrAddress()
ParseOutputIndex()
ParsePrevTxs()

The new classes and functions are unit tested (except RPCs).

Re: the push a few seconds ago:
This is not an update, and there is still quite a bit to do, but now the branch is conflict free and up-to-date.

I started with yet another approach, but this one I kinda like.
Previously the issue for me was that everything was stuffed into one RPC, such as class B, class C, reference, no reference, fees, reference amounts, etc. etc., which was really ugly in my opinon, and at the same time still very limiting.
The idea now is that there are several RPCs to modify raw transactions:

add a payload with class B encoding
add a payload with class C encoding
add a reference output
add a change output (and inputs)

See:

src/omnicore/rpcrawtx.cpp#L177-L346

It's not yet finished, and I'd like to untangle it a a bit further, and see which calls are actually needed. Adding change and inputs is probably going to be seperated. The currently existing calls are already sufficient to create Omni transactions though. :)
The core components are the new TxBuilder and OmniTxBuilder classes, which are mostly finished.
See:

src/omnicore/createtx.h (has documentation with examples)

They may be extended, and I had a lot more methods at the beginning, but I removed all methods, which were not strictly necessary. Still missing is a mechanism to add inputs via the builder, which is done via InputsToMutableTx on the RPC layer at the moment.

@zathras-crypto: ready.
Please let me know, if there is anything to improve. :)

I'd also like to add a call to modify inputs, or rather: add an input. This is something that could be used in the context of #11 (to add the payment input).

@zathras-crypto: ready.

Sorry dude, missed the ping, will review again this weekend but I did play with this a little while back... Leave it with me :)

I'd also like to add a call to modify inputs, or rather: add an input. This is something that could be used in the context of #11 (to add the payment input).

I think this is fine, but perhaps it should be restricted to Class C only where sender identification is changed to first vin only and adding inputs doesn't risk changing the sender (when using largest input by sum).

I think this is fine, but perhaps it should be restricted to Class C only where sender identification is changed to first vin only and adding inputs doesn't risk changing the sender (when using largest input by sum).

Hm.. the builder doesn't have an understanding about Omni transactions, or their senders. Transactions are built in steps, with something like addReference(), addOpReturn(), whereby each step is exposed via the API as stateless call.
It's very low level, but I'm all for better usability, though I currently don't see how. Initially I used a broader approach, where the whole transaction is created in one step, i.e. the user provides all information together, but this was awefully large and unflexible.

I added ParseOutputIndex and omni_createrawtx_input.

Yep, that makes sense & I like the way it's done now in 'pieces' rather than a single pass, it's definitely more flexible.
I guess if the user is crafting raw transactions they should be fully aware of what they are doing and protecting them against an unintended change of sender by adding extra inputs might be a bit too much babysitting.

Ideally one would build a transaction, and then validate the results with "omni_decodetransaction".

Ideally one would build a transaction, and then validate the results with "omni_decodetransaction"

Ahh of course!

@zathras-crypto: did you have the chance to review?

@zathras-crypto: did you have the chance to review?

I did yep and the code is great, basically what I was attempting to do was recreate existing Omni transactions via the raw interface (of course they'd be unsigned) and compare them.
I was going to loop back around and try and figure out where I went wrong as I ran into some trouble.
Here is an example of one of the transactions I built, but I'm unable to decode it via omni_decodetransaction - I haven't had a chance to dig into why as yet (looked OK from a quick look at it via deocderawtransaction):
010000000163da7c92a0165f68fa280ccdbaaf46d5f61da7640148b40f6c9588c0161e28d10000000000ffffffff033c0f00000000000067514104e6bf7e7f3b8e1b5cbdb7ef22e893583aba36edc63871e265493fd04bd59230da6bdcbd76887863a0294f1114e02328e46b4b48b0fc364aef80f7f831b39eb1f02102c7e8649fc477c0622f2cb0fb5b3dea02a4044958b76809b8e48ecbfaec2299a452aeaa0a0000000000001976a914946cb2e08075bcbaf157e47bcb67eb2b2339d24288acaa0a0000000000001976a914fa0692278afe508514b5ffee8fe5e97732ce066988ac00000000

Oh, I also forgot to mention - the documentation notes the rawtx argument is optional, but it's required.  Perhaps this is just my interpretation, but I consider it a 'required' field if we have to include it (even empty).  Eg if I don't include the field because it's optional the command fails omni_createrawtx_opreturn "payload", but add the field with an empty value omni_createrawtx_opreturn "" "payload" and it's fine hence (imo) the field is required and supports empty values.  I hope that makes sense hehe :)
While on the subject, I did want to say the quality of your work is just really really professional (including commenting and documentation) - it really makes me realize that I need to "up my game" to bring my contributions up to the same standard/level of quality...
EDIT: I just did the same test transactions on another box with a fully synchronized node, I was able to decode successfully.  That makes sense now I think about it...  OK to merge :)

Here is an example of one of the transactions I built, but I'm unable to decode it [...] EDIT: I just did the same test transactions on another box with a fully synchronized node

Ah, I see. Did you explicitly provide the inputs when using "omni_decodetransaction"? If not, I assume this is the cause. The following should work, even on an unsynchronized box (untested):
omni_decodetransaction "010000000163da7c92a0165f68fa280ccdbaaf46d5f61da7640148b40f6c9588c0161e28d10000000000ffffffff033c0f00000000000067514104e6bf7e7f3b8e1b5cbdb7ef22e893583aba36edc63871e265493fd04bd59230da6bdcbd76887863a0294f1114e02328e46b4b48b0fc364aef80f7f831b39eb1f02102c7e8649fc477c0622f2cb0fb5b3dea02a4044958b76809b8e48ecbfaec2299a452aeaa0a0000000000001976a914946cb2e08075bcbaf157e47bcb67eb2b2339d24288acaa0a0000000000001976a914fa0692278afe508514b5ffee8fe5e97732ce066988ac00000000" '[{"txid":d1281e16c088956c0fb4480164a71df6d546afbacd0c28fa685f16a0927cda63","vout":0,"scriptPubKey":"76a914ee2953140b43d86027ced62f566c46a7ed495e9e88ac","value":0.0005}]'

Oh, I also forgot to mention - the documentation notes the rawtx argument is optional, but it's required.

Good you noticed this. It's one of the points I was wondering about. Currently the following approach is used:

if there is an argument at the very end, which has a default value, and which can be omitted, then the argument is optional
if there is an argument at the beginning or inbetween, which has a default value, and which may be set to a value, which isn't strictly matching to the underlying data type, then I call it optional, too

Let me clarify:
The call "omni_createrawtx_opreturn" expects "rawtx" "payload", whereby "rawtx" refers to a transaction. An empty value (either "" or null) isn't a transaction, but accepted, and by labelling it "optional" I wanted to emphasize that providing a transaction is not strictly needed.
A similar approach was used for a few other calls, for example "omni_sendissuancecrowdsale" (see the docs).
But I see your point and I agree, this is indeed confusing, and one may be tempted to omit optional arguments completely, which is worse than calling it "required". I'm going to update and change "optional" to "required" for those calls. :)

While on the subject [...] it really makes me realize that I need to "up my game" to bring my contributions up to the same standard/level of quality...

Thanks, very appreciated! But no worries mate, it's a pleasure to work with you. :) While I believe we should always try to improve, content should be higher valued than style etc., which is only nice to have, but not mandatory.
As a general rule of thumb, I try to tackle it from a perspective of "what can I do to make it easier for a fellow developer, who may not be familiar with the codebase". In an ideal scenario pointing to the code or documentation should be sufficient and self-sustaining, without the need for additional explainations (and if there is need for explanations, then it may as well be documented).

Updated.

Did you explicitly provide the inputs when using "omni_decodetransaction"

Nope, I picked up on that afterwards - I thought "of course it doesn't work, how can we identify sender if the inputs are not in the chain?" and remembered you had provided the option to supply the inputs directly to omni_decodetransaction so no problems there :)

A similar approach was used for a few other calls, for example "omni_sendissuancecrowdsale"

Understood, but even though things like URL or DATA may be empty, the field is still required (and noted as 'required' on the API docs).

But I see your point and I agree, this is indeed confusing, and one may be tempted to omit optional arguments completely, which is worse than calling it "required". I'm going to update and change "optional" to "required" for those calls. :)

Thanks :)  That was my main concern, that someone would be making the call with just one parameter thinking they didn't need to include the optional parameter and not getting far - I think the change is a good call :)

Thanks, very appreciated! But no worries mate...

You're too kind mate haha - any programming I did previously was to fill a need as part of my work in infrastructure (middleware etc) so the source never saw the light of day - I've got into some bad habits but every time I review your work I think "so polished! man my contributions have rough edges!" so if only for just taking pride in my own work I definitely think a little more effort in commenting and documenting would go a long way :)
Also I'm more than happy if you want to merge this in bud :)

(and noted as 'required' on the API docs)

Just to clarify: this was updated with this PR, and it currently still shows "optional" on the main brach.

Also I'm more than happy if you want to merge this in bud :)

Yay, thanks! :)

repo: OmniLayer/omnicore


text:
GalliumOS Omnisharp.path error

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0-preview2-003131)
Product Information:
Version:            1.0.0-preview2-003131
Commit SHA-1 hash:  635cf40e58
Runtime Environment:
OS Name:     galliumos
OS Version:  2.0
OS Platform: Linux
RID:         galliumos.2.0-x64
VS Code version: latest
C# Extension version: latest
Steps to reproduce
Start VC
Expected  behavior
Actual behavior
this came first:
[ERROR] Could not locate an OmniSharp server that supports your Linux distribution.
OmniSharp provides a richer C# editing experience, with features like IntelliSense and Find All References.
It is recommend that you download the version of OmniSharp that runs on Mono using the following steps:
1. If it's not already installed, download and install Mono (https://www.mono-project.com)
2. Download and untar the latest OmniSharp Mono release from  https://github.com/OmniSharp/omnisharp-roslyn/releases/
3. In Visual Studio Code, select Preferences->User Settings to open settings.json.
4. In settings.json, add a new setting: "omnisharp.path": "/path/to/omnisharp/OmniSharp.exe"
5. In settings.json, add a new setting: "omnisharp.useMono": true
6. Restart Visual Studio Code.
So I followed the instructions. my setting.json:
// Place your settings in this file to overwrite the default settings
{
"omnisharp.path": "/home/chrx/Omnisharp/Omnisharp.exe",
"omnisharp.useMono": true
}
I get this error on startup:
Invalid value specified for "omnisharp.path" ('/home/chrx/Omnisharp/Omnisharp.exe).

I changed Omnisharp.exe to OmniSharp.exe in the path, that still didn't fix it.

The entire path is case-sensitive. Also, what version of Mono do you have installed?

http://imgur.com/pDs98FGl.png
There's a screenshot with mono -v, VC settings.json, and the file manager open to the Omnisharp install.
Mono is working fine. I can run the hello test just fine.
I get this error when I run a simple .cs file though rightclick -> Run Code
(using https://code.visualstudio.com/docs/runtimes/dotnet to create a new dotnet project)
[Running] scriptcs "/home/chrx/Documents/TestingOmni/Program.cs"
/bin/sh: 1: scriptcs: not found
[Done] exited with code=127 in 0.031 seconds

While testing different ideas, I found by renaming Omnisharp (the one highlighted in the file manager) to Omnisharp.exe I now get this on startup:
Starting OmniSharp server at 11/1/2016, 12:27:50 AM
Target: /home/chrx/Documents/TestingOmni
OmniSharp server started wth Mono
Path: /home/chrx/Omnisharp/OmniSharp.exe
PID: 9815
Cannot open assembly '/home/chrx/Omnisharp/OmniSharp.exe': File does not contain a valid CIL image.
[ERROR] Error: Failed to start OmniSharp
I still get the same error when trying rghtclk->Run Code.

I get the same as the above when changing the omnisharp.path to /home/chrx/Omnisharp/OmniSharp

When you say that you right-click a file and choose Run Code, I'm actually not clear on where that is. I've been unable to find a "Run Code" command in VS Code. Perhaps that is coming from some other extension?
Could you try the latest v1.5-future-preview1 release of the C# extension. I suspect this may better.
Do the following to install the new extension:

Download the .vsix for the extension at the link above.
Open Visual Studio Code.
Select Preferences->User Settings from the menu and then removing the "omnisharp.path" and "omnisharp.useMono" settings from the settings.json.
Select View->Extensions to display the Extensions pane.
In the Extensions pane, click on the little gear icon next to the C# extension and select "Uninstall". Allow Visual Studio Code to reload.
In the Extensions pane, click on the [...] at the top-right corner of the pane and select "Install from VSIX...". Pick the .vsix you downloaded and then allow Visual Studio Core to restart.

That's from formulahendry.code-runner
He's output after installing the new version (code-runner disabled just incase):
Updating C# dependencies...
Downloading package 'Mono Runtime (Linux / x64)' (1547 KB) .................... Done!
Downloading package 'Mono Framework Assemblies' (5494 KB) .................... Done!
Downloading package 'OmniSharp (Mono 4.6)' (12867 KB) .................... Done!
Downloading package '.NET Core Debugger (Windows / x64)' (21291 KB) .................... Done!
Downloading package '.NET Core Debugger (macOS / x64)' (20149 KB) .................... Done!
Downloading package '.NET Core Debugger (CentOS / x64)' failed (error code '404')
Failed at stage: downloadPackages
404
Finished
[ERROR]: C# Extension failed to install the debugger package
Tried to uninstall/reinstall, but that didn't change anything.

@Neoakb can you give us the output from cat /etc/os-release?
@chuckries looks like we have some (multiple?) sort of issue here as it is trying to download multiple versions of the debugger, and then CentOS is giving a 404.

NAME="GalliumOS"
VERSION="2.0 (Xenon)"
ID=galliumos
ID_LIKE="ubuntu debian"
PRETTY_NAME="GalliumOS 2.0"
ANSI_COLOR="1;34"
VERSION_ID="2.0"
HOME_URL="https://galliumos.org/"
SUPPORT_URL="https://galliumos.org/"
BUG_REPORT_URL="https://github.com/GalliumOS/galliumos-distro/issues"
UBUNTU_CODENAME=xenial

@Neoakb one last question - are you trying to do .NET Core development or mono? If .NET Core, are you finding that the Ubuntu 16 version of .NET Core works well enough? Or are you using some sort of other version?

I am using this course to learn C# and wanted to be able to work while I was away. With .NET Core it seems like I'll be able to develop on and for most systems.
https://mva.microsoft.com/en-US/training-courses/c-fundamentals-for-absolute-beginners-16169?l=Lvld4EQIC_2706218949#
I'm 'technologically inclined', but I'm still a novice programmer.

@Neoakb got it. We haven't tried Gallium at all, but I can give you a test version of the C# extension later today which causes it to treat Gallium like Ubuntu 16 and you can see if that works for you.

NOTE: The CentOS failure is now being tracked with #910. Better handling of unknown Linux distros is tracked with #911. This bug will just track trying to get Gallium OS to work.

@Neoakb please try this:

Download the file: csharp-1.5.0-dev-galliumos.vsix.renamed.zip
Remove the '.renamed.zip' part of the extension
In VS Code: View->Extensions
Click the '...' to bring up the additional command menu and select 'Install from VSIX...', and navigate to the downloaded file
Confirm that downloading assets succeeds
Try debugging and see if that works (you can hit breakpoints, and the locals window shows your variables)

C# Output:
Updating C# dependencies...
Downloading package 'Mono Runtime (Linux / x64)' (1547 KB) .................... Done!
Downloading package 'Mono Framework Assemblies' (5494 KB) .................... Done!
Downloading package 'OmniSharp (Mono 4.6)' (12867 KB) .................... Done!
Downloading package '.NET Core Debugger (Ubuntu 16 / x64)' (29612 KB) .................... Done!
Installing package 'Mono Runtime (Linux / x64)'
Installing package 'Mono Framework Assemblies'
Installing package 'OmniSharp (Mono 4.6)'
Installing package '.NET Core Debugger (Ubuntu 16 / x64)'
Finished
Debug Console:
0 references0 references
Find
No results
    }
}

}
DEBUG CONSOLE
You may only use the C# Extension for Visual Studio Code with Visual Studio
Code, Visual Studio or Xamarin Studio software to help you develop and test your
applications.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/1.0.1/System.Private.CoreLib.ni.dll'. Cannot find or open the symbol file.
Loaded '/home/chrx/Documents/TestingCSharp/bin/Debug/netcoreapp1.0/TestingCSharp.dll'. Symbols loaded.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/1.0.1/System.Runtime.dll'. Cannot find or open the symbol file.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/1.0.1/mscorlib.dll'. Cannot find or open the symbol file.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/1.0.1/System.Console.dll'. Cannot find or open the symbol file.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/1.0.1/System.Threading.dll'. Cannot find or open the symbol file.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/1.0.1/System.IO.dll'. Cannot find or open the symbol file.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/1.0.1/System.IO.FileSystem.Primitives.dll'. Cannot find or open the symbol file.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/1.0.1/System.Runtime.Handles.dll'. Cannot find or open the symbol file.
Intellisense seems to work. I think we might be good. Don't know about those missing symbol files though. (TBH I know nothing about them either way.)

@Neoakb the 'Cannot find or open the symbol file' is normal for system assemblies. There is an issue to give that a nicer message so it doesn't sound like a problem, but we haven't fixed it yet.
Were you able to hit a breakpoint and inspect values?

I was just using a simple hello world to test. want me to test specific code or just make some variables and change them, etc.

It would be enough to just set a breakpoint on the 'Console.WriteLine' line and verify you can inspect 'args'.

me <- thrilled that IntelliSense works!

Just tested and it worked just fine. Looks like I'm set now. Anything I should keep an eye on? When to update back to the normal C# extension and what not.

@Neoakb The only things to keep in mind are:

We are out of time for this to make 1.5.0, so when that comes out (probably on Monday) do NOT upgrade to it. But you have 99.99% of the same bits, so that shouldn't be a problem.
When 1.5.1 or 1.6 (whatever we call the next release) comes out, you should be able to safely upgrade. You may want to explicitly remove the ~/.vscode/extensions/ms-vscode.csharp-1.5.0-1.5.0-dev-galliumos folder to make sure that VS Code prefers the released version.

@gregg-miskelly: What change is needed?

https://github.com/gregg-miskelly/omnisharp-vscode/commit/cbe1e20b578d653a236a905829a379bb63179d83

Awesome! Thanks for the help. Hope I helped somehow!

merge it :smile:

The fix in the release branch now. Thanks @Neoakb! It'll be in 1.5.

authors: DustinCampbell Neoakb gregg-miskelly

repo: OmniSharp/omnisharp-vscode


text:
Load Setting Does Not Load Netlist

Pluggin will not load netlist. I followed the video below, but it does not load nets.

Followed this video:
https://www.google.com/search?q=kicad+6+length+matching+plugin&client=firefox-b-1-d&ei=j4aLY8f_CISoptQPovedwA8&ved=0ahUKEwiHg9fv-937AhUElIkEHaJ7B_gQ4dUDCA8&uact=5&oq=kicad+6+length+matching+plugin&gs_lcp=Cgxnd3Mtd2l6LXNlcnAQAzIFCCEQoAE6CggAEEcQ1gQQsAM6BggAEBYQHjoFCCEQqwI6CAghEBYQHhAdSgQIQRgASgQIRhgAUJ8EWJ0PYO0QaAFwAXgAgAGAA4gBmQiSAQcwLjQuMC4xmAEAoAEByAEIwAEB&sclient=gws-wiz-serp#fpstate=ive&vld=cid:477ea3bd,vid:tDM1MDhxVoc

@mgroz Thanks for the report. Please wait for the updates

authors: mgroz thanhduongvs

repo: OneKiwiTech/kicad-length-matching


text:
Upload/Download File

Sorry if wrong place I am new to github/programming
Is it possible to upload, like say nightmare-upload?
great library,thanks

Hi @dejay12,
Currently chromy does not support method of uploading file easily.
But it might be able to implemented.
I'll implement it in the near future.
If you want to implement soon, below issue maybe helps you.
https://github.com/cyrus-and/chrome-remote-interface/issues/164
Chromy wrapped chrome-remote-interface and you can access it like this:
const Chromy = new Chromy()
const client = chromy.client
const {DOM, Runtime} = client

Hi @dejay12,
I've just added setFile() command to Chromy.
This command sets file or files to file control.
This is what you want right?
Here is example:
const Chromy = require('../src')
const path = require('path')

let chromy = new Chromy({visible: true})
chromy.chain()
      .goto('http://localhost/'))
      .setFile('input[type="file"]', __filename)
      .click('button.submit')
      .sleep(3000)
      .end()
      .catch(e => {
        console.log(e)
      })
      .then(_ => chromy.close())

Wow, thank you very very much for this

repo: OnetapInc/chromy


text:
Distinguish between client and backend API

From my understanding the current API description seems not to distinguish between client and backend core API. I would like to suggest to be more specific what API should be used by the clients, by the backends and by both.
I have some suggestion that may additionally be required by the backends:

REST API call to lock (POST), check lock (GET) and delete lock (DELETE) of resources across a cluster of workers, so that a resource that is worked on can not be modified by other workers in the same or other backends
REST API POST call provided by the job micro-service to send the current job/task status (accepted, evaluating, running, finished, error), so that clients that are subscribed to a job micro-service get noticed or can use a REST API GET call to check the status of a job/task
REST API GET call provided by the job micro-service to check if the the current job was marked to be terminated, stopped or cancelled

As the "middleware" Core API has been moved to the back-end there is no separation anymore. So I think this is now obsolete?!

I'll close this issue for now.

authors: appelmar huhabla m-mohr

repo: Open-EO/openeo-api-poc