text:
Pass json values through karate-config.js

Problem Statment:
i have created redemptions_secrets.json which has qa and stage key / values. In run time, based on karate.env value either stage or qa.
I need qa json object or stage json object to pass the key values to feature files.
What i tried so far.
I tried to call redemptions_secrets.json in karate-config.js and return the object and tried to call direct json key (QA or Stage) in feature files but no success.
I got struck here to maintain environment properties in one file
Project link
https://github.com/qaselenium12/poc-karate
Execute FulfillmentTestRunner.java which call fetch-servicetoken.feature.

closing as the instructions here have not been followed: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue

repo: intuit/karate


text:
Add Auto to generate releases based on semantic version labels on pull requests

Generate releases based on semantic version labels on pull requests using Intuit's Auto: https://github.com/intuit/auto

It would be great if this automates updating the changelog.md (which we have forgotten to do!)

I'm putting up a PR for this!

source: gharchive/issue

authors: reubenae skodamarthi tylerkrupicka

repo: intuit/user-data-for-fraud-prevention

license: MIT

license_type: permissive

license_source: github-api


text:
Get cell-tpe-specific TF-gene regulatory relations

Hi there!
Thanks for the excellent work!
I am interested in getting  the cell-type-specific TF-gene regulations. However, in the taget gene module, I find that all the potential target genes are provided for a certain TF. In the Peak-Browser, the cell-type-specific TF ChIP-seq bed file can be downloaded. I tried to process the bed file via annotatePeak function of ChIPseeker package, while some errors always ocurred,indicating that 'start' or 'end' cannot contain NAs.
Therefore, I was wondering if there is a more convenient way to get the cell-cell-specific TF-gene regulations according to all the cell-type-specific ChIP-seq data?
I look forward to your reply. Thanks in advance for your time and help!
Best,
Scotty

Thank you so much! I tried the pipeline and it worked well.

repo: inutano/chip-atlas


text:
global: setup automatic updates and releases

Since this repository uses the lists from https://github.com/atmire/COUNTER-Robots/, syncing should be done in an automatic fashion (e.g. on Travis) and be released in regular intervals (e.g. each month).

@sakshamarora1 be aware of GH CI actions suspended after 2 months, workaround implemented here

authors: ntarocco slint

repo: inveniosoftware/counter-robots


text:
installation: remove invenio-query-parser

Removes invenio-query-parser as a dependence. (addresses #139)

Signed-off-by: Sebastian Witowski witowski.sebastian@gmail.com

Travis requires a release of invenio-records-rest.

source: gharchive/pull-request

repo: inveniosoftware/invenio-oaiserver

license: mit

license_source: bigquery


text:
serializers: minor fixes to datacite json and add tests for xml

closes https://github.com/inveniosoftware/invenio-rdm-records/issues/703
Differences I can observe in comparison with the full example of DataCite 4.3 XML, which are not yet implemented are:

All languages should use the 2 letter encoding, instead of 3. This should be fixed for the JSON schema too.
We do not have alternate identifiers, we put them in identifiers. This would differ from the JSON schema. We should:

pids --> identifiers
identifiers --> alternate identifiers

All languages should use the 2 letter encoding, instead of 3. This should be fixed for the JSON schema too.

BCP 47 includes ISO 639-3 so we are good.

We do not have alternate identifiers, we put them in identifiers. This would differ from the JSON schema. We should:
pids --> identifiers
identifiers --> alternate identifiers

Not needed, is taken care by datacite, ref

Other issues I've seen:

Dates should also serialize the embargo date.

Rebased on latest master (There were conflicts) and added the content of https://github.com/inveniosoftware/invenio-rdm-records/pull/731 to close https://github.com/inveniosoftware/invenio-rdm-records/issues/727

authors: lnielsen ppanero

repo: inveniosoftware/invenio-rdm-records


text:
Source for translation

Hello I translated program except some section. Would you please help me where comes from those (split and removed received ) I want to change them also but I couldnt find the source. Also bottom pagination explanation showing ...of .. rows?

These translation hooks should now be implemented in #1263
Once your translation is done please submit a PR with the translation files! :)

These translation hooks should now be implemented in #1263
Once your translation is done please submit a PR with the translation files! :)

@neco1982 did #1263 expose those translations for you?

@neco1982 did #1263 expose those translations for you?

Hey @neco1982 did you complete the Turkish translation? Are you able to submit the translation files as a pull request?

I'm going to close this issue out now - please do contribute back your translation data when you have a chance.

repo: inventree/InvenTree


text:
Replaces occurrences of Symbol(string) to Symbol.for(string)

Description
Replaces Symbol(string) with Symbol.for(string)
Related Issue
inversify #691
Motivation and Context
See description of a Symbol
Calling Symbol() creates a unique primitive value in the Javascript engine. Without a reference to it, it becomes lost.
Symbol('foo') === Symbol('foo')  // false

let key1 = Symbol('foo')
let key2 = Symbol('foo')
let obj = {
    [key1]: 'bar',
    [key2]: 'baz'
}
obj[key1] === 'bar' // true
obj[key2] === 'baz' // true

Object keys created using Symbol() are therefore impossible to use without keeping a reference to them.
Using Symbol.for('foobar') looks up the symbol in the JS registry and returns it if found or creates it if not found.
How Has This Been Tested?
This just updates tests in the repo
Types of changes

[x] Bug fix / Docs (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes. (Changes tests)
[ ] All new and existing tests passed.

Thanks a lot for the PR 👍

repo: inversify/inversify-binding-decorators


text:
Problem in Install [bug]:

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
No response
What happened?
During install I get the following error (Latest Python and Pytorch installed):
Collecting torch-fidelity
Using cached torch_fidelity-0.3.0-py3-none-any.whl (37 kB)
Collecting torchmetrics
Using cached torchmetrics-0.11.0-py3-none-any.whl (512 kB)
Collecting transformers==4.25.*
Using cached transformers-4.25.1-py3-none-any.whl (5.8 MB)
ERROR: Ignored the following versions that require a different python version: 0.55.2 Requires-Python <3.5; 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11
ERROR: Could not find a version that satisfies the requirement torch==1.12.1 (from versions: none)
ERROR: No matching distribution found for torch==1.12.1
Installation of requirements failed. See above for errors and check https://invoke-ai.github.io/InvokeAI/installation/INSTALL_AUTOMATED/#troubleshooting for potential solutions.
Screenshots
No response
Additional context
I've tried uninstalling and reinstalling pytorch and torchvision, no change.
Contact Details
ogresan@gmail.com

I'm sorry you're seeing this problem. Could you try the following tests for me and post your results?

Using the windows power shell, enter the invokeai directory that the install script created. It is usually in \Users\your_name\invokeai
Post the contents of the file requirements.txt
Run the command python -V and post the result.
Run the command .venv\Scripts\activate.bat (your prompt should change to include the word .venv. Let me know if it doesn't)
Run the command python -V again and post the result (I'm worried about different versions of Python being installed in different places)
Run the command pip install --no-cache -r requirements.txt

(6) should run to completion without any errors about the torch version.  If it doesn't, then the information you provided will help sorting out the issue.

Thanks for getting back to me. Here's what I got:
requirements.txt:
-r environments-and-requirements/requirements-base.txt
Get hardware-appropriate torch/torchvision
--extra-index-url https://download.pytorch.org/whl/cu116 --trusted-host https://download.pytorch.org
torch==1.12.1
torchvision==0.13.1
PS C:\Users\User\invokeai> python -v
import _frozen_importlib # frozen
import _imp # builtin
import '_thread' # <class '_frozen_importlib.BuiltinImporter'>
import '_warnings' # <class '_frozen_importlib.BuiltinImporter'>
import '_weakref' # <class '_frozen_importlib.BuiltinImporter'>
import 'winreg' # <class '_frozen_importlib.BuiltinImporter'>
import '_io' # <class '_frozen_importlib.BuiltinImporter'>
import 'marshal' # <class '_frozen_importlib.BuiltinImporter'>
import 'nt' # <class '_frozen_importlib.BuiltinImporter'>
import '_frozen_importlib_external' # <class '_frozen_importlib.FrozenImporter'>
installing zipimport hook
import 'time' # <class '_frozen_importlib.BuiltinImporter'>
import 'zipimport' # <class '_frozen_importlib.FrozenImporter'>
installed zipimport hook
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings_pycache__init_.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings_init_.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings\pycache\init.cpython-311.pyc'
import '_codecs' # <class '_frozen_importlib.BuiltinImporter'>
import 'codecs' # <class '_frozen_importlib.FrozenImporter'>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings_pycache_\aliases.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings\aliases.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings\pycache\aliases.cpython-311.pyc'
import 'encodings.aliases' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA59A1990>
import 'encodings' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5997350>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings_pycache_\utf_8.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings\utf_8.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings\pycache\utf_8.cpython-311.pyc'
import 'encodings.utf_8' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA59C1610>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings_pycache_\cp1252.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings\cp1252.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\encodings\pycache\cp1252.cpython-311.pyc'
import 'encodings.cp1252' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA59C1BD0>
import '_signal' # <class '_frozen_importlib.BuiltinImporter'>
import '_abc' # <class '_frozen_importlib.BuiltinImporter'>
import 'abc' # <class '_frozen_importlib.FrozenImporter'>
import 'io' # <class '_frozen_importlib.FrozenImporter'>
import '_stat' # <class '_frozen_importlib.BuiltinImporter'>
import 'stat' # <class '_frozen_importlib.FrozenImporter'>
import '_collections_abc' # <class '_frozen_importlib.FrozenImporter'>
import 'genericpath' # <class '_frozen_importlib.FrozenImporter'>
import '_winapi' # <class '_frozen_importlib.BuiltinImporter'>
import 'ntpath' # <class '_frozen_importlib.FrozenImporter'>
import 'os' # <class '_frozen_importlib.FrozenImporter'>
import '_sitebuiltins' # <class '_frozen_importlib.FrozenImporter'>
Processing user site-packages
Processing global site-packages
Adding directory: 'C:\Users\User\AppData\Local\Programs\Python\Python311'
Adding directory: 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages'
Processing .pth file: 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\distutils-precedence.pth'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages_distutils_hack_pycache__init_.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages_distutils_hack_init_.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\_distutils_hack\pycache\init.cpython-311.pyc'
import '_distutils_hack' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5B5C550>
import 'site' # <class '_frozen_importlib.FrozenImporter'>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\rlcompleter.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\rlcompleter.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\rlcompleter.cpython-311.pyc'
import 'atexit' # <class '_frozen_importlib.BuiltinImporter'>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\inspect.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\inspect.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\inspect.cpython-311.pyc'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\ast.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\ast.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\ast.cpython-311.pyc'
import '_ast' # <class '_frozen_importlib.BuiltinImporter'>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\contextlib.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\contextlib.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\contextlib.cpython-311.pyc'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\collections_pycache__init_.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\collections_init_.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\collections\pycache\init.cpython-311.pyc'
import 'itertools' # <class '_frozen_importlib.BuiltinImporter'>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\keyword.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\keyword.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\keyword.cpython-311.pyc'
import 'keyword' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5BEE790>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\operator.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\operator.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\operator.cpython-311.pyc'
import '_operator' # <class '_frozen_importlib.BuiltinImporter'>
import 'operator' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5BEECD0>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\reprlib.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\reprlib.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\reprlib.cpython-311.pyc'
import 'reprlib' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5BEF910>
import '_collections' # <class '_frozen_importlib.BuiltinImporter'>
import 'collections' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5BC6190>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\functools.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\functools.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\functools.cpython-311.pyc'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\types.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\types.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\types.cpython-311.pyc'
import 'types' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5C13190>
import '_functools' # <class '_frozen_importlib.BuiltinImporter'>
import 'functools' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5BD5050>
import 'contextlib' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5BC55D0>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\enum.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\enum.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\enum.cpython-311.pyc'
import 'enum' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5BC7490>
import 'ast' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5B84B10>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\dis.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\dis.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\dis.cpython-311.pyc'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\opcode.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\opcode.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\opcode.cpython-311.pyc'
import '_opcode' # <class '_frozen_importlib.BuiltinImporter'>
import 'opcode' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E61750>
import 'dis' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5B87250>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\collections_pycache_\abc.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\collections\abc.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\collections\pycache\abc.cpython-311.pyc'
import 'collections.abc' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E52A10>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\importlib_pycache__init_.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\importlib_init_.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\importlib\pycache\init.cpython-311.pyc'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\warnings.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\warnings.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\warnings.cpython-311.pyc'
import 'warnings' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E69310>
import 'importlib' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E69F10>
import 'importlib.machinery' # <class '_frozen_importlib.FrozenImporter'>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\linecache.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\linecache.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\linecache.cpython-311.pyc'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\tokenize.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\tokenize.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\tokenize.cpython-311.pyc'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_pycache__init_.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_init_.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re\pycache\init.cpython-311.pyc'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_pycache__compiler.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_compiler.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re\pycache\_compiler.cpython-311.pyc'
import '_sre' # <class '_frozen_importlib.BuiltinImporter'>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_pycache__parser.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_parser.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re\pycache\_parser.cpython-311.pyc'
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_pycache__constants.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_constants.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re\pycache\_constants.cpython-311.pyc'
import 're._constants' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E918D0>
import 're._parser' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E86910>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_pycache__casefix.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re_casefix.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\re\pycache\_casefix.cpython-311.pyc'
import 're._casefix' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E9CFD0>
import 're._compiler' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E83210>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\copyreg.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\copyreg.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\copyreg.cpython-311.pyc'
import 'copyreg' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E9E410>
import 're' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E81490>
C:\Users\User\AppData\Local\Programs\Python\Python311\Lib_pycache_\token.cpython-311.pyc matches C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\token.py
code object from 'C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\pycache\token.cpython-311.pyc'
import 'token' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E82A90>
import 'tokenize' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E6E490>
import 'linecache' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5E52990>
import 'inspect' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5B5EA90>
import 'rlcompleter' # <_frozen_importlib_external.SourceFileLoader object at 0x000001AFA5B52A50>
Python 3.11.1 (tags/v3.11.1:a7a450f, Dec  6 2022, 19:58:39) [MSC v.1934 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

PS C:\Users\User\invokeai> .venv\Scripts\activate.bat
PS C:\Users\User\invokeai> (Prompt didn't change)
PS C:\Users\User\invokeai> python -v  (No change)
PS C:\Users\User\invokeAI-Installer> pip install --no-cache -r requirements.txt
(Result: Failed in the same place, same error)

I ran into this same issue. Line for line the same errors. Couldn't find it again to quote it here, but on a python forum post somewhere they said that Python 3.11 doesn't see and/or interact with torch for some reason. Uninstalled 3.11, rebooted, did a clean install of 3.10.5 and the InvokeAI install script ran just fine with no errors.

authors: jhewittdev lstein ogresan

repo: invoke-ai/InvokeAI


text:
[enhancement]: allow multiples of 8

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
It is now possible generate images with sizes in multiples of 8, but we don't allow it yet.
Besides the UI changes needed, this appears to be a very simple fix - change the 64 to an 8 here:
https://github.com/invoke-ai/InvokeAI/blob/27a113d872d0e798df60501ced193a403addbcf5/invokeai/backend/generate.py#L1215
At least, that lets me do txt2img at any multiple of 8. Maybe there are other places where we need to change this?
Alternatives
No response
Aditional Content
No response

Not stale

What else may we need to change to allow 8px increments?

merged


text:
Configuration script tidying up

Rename configure_invokeai.py to invokeai_configure.py to be consistent with installed script name
Remove warning message about half-precision models not being available during the model download process.
adjust estimated file size reported by configure
guesstimate disk space needed for "all" models
fix up the "latest" tag to be named 'v2.3-latest'

fyi the letter e is missing in
please run 'invokeai-configure'
line 8 in scripts/configure_invokeai.py


text:
Web Docs Update

Included some documentation for the Web docs.
I think we likely need to revisit documentation for the project broadly, but beyond the scope of getting 2.0 release out the door.

@blessedcoolant

Hey seems good for most part. Sorry for the trouble but I made a last minute change. I replaced the Invoke button from the camera icon to a Invoke text button. Maybe you could update that change? Thanks.

@blessedcoolant - No worries, updated!

The images will need updating coz the icon is no longer the camera.

Invoke is the new black.

@blessedcoolant - Final.

Only 1 update is updated?

weird - reuploading

authors: blessedcoolant hipsterusername


text:
Convert to ValesDeDespensa complement

Converts from a mx.FoodVouchersComplement complement to a CFDI's valesdedespensa:ValesDeDespensa
Mapping is very direct as the GOBL struct was designed for this purpose and the GOBL library already validates and massages the data.
Depends on https://github.com/invopop/gobl/pull/211 => Make sure to update the mod.go file once the changes are released

Merged to move forward with testing and launching of the functionality. Feedback always welcome!

I think the only thing that's missing from these PRs for the complements is documentation. It'd be great to describe that these are available in the README.md, and how they can be used.

Indeed, thanks Sam! Done here: a963197

authors: cavalle samlown


text:
🛑 Bitwage API (Sandbox) is down

In 0f0bf15, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 104 ms

Resolved: Bitwage API (Sandbox) is back up in 7c228a3 after 1 hour, 7 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 8994ca0, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 330 ms

Resolved: Bitwage API (Sandbox) is back up in 450c700 after 19 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In ec9d03c, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 55 ms

Resolved: Bitwage API (Sandbox) is back up in 786c136 after 6 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In cd215b6, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 249 ms

Resolved: Bitwage API (Sandbox) is back up in b8c818d after 2 hours, 22 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In ac17bf7, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 313 ms

Resolved: Bitwage API (Sandbox) is back up in 7a14a71 after 39 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In ff228e4, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 157 ms

Resolved: Bitwage API (Sandbox) is back up in 2e7aaf8 after 9 minutes.


text:
Update air-q version in stable to 1.0.3

Added some requested changes concerning error messages and more logging info.

RE-CHECK!


text:
Fixed filtering of bokeh LineAnnotationPlot properties

Minor self-explanatory fix.

Looks good, happy to merge once the tests pass.

Will have to add a dask 0.14 compatibility PR because they changed a bit of API, hopefully they can restore the correct behavior in 0.15.

Have you filled an issue for dask pointing out the breaking change?

Have you filled an issue for dask pointing out the breaking change?

Pinged the person responsibly after asking Matt about it. Temporarily pinned dask now. Once I've heard back we'll have to decide what to do.

Temporarily pinned dask now

That means I can merge once the tests pass, right?

That means I can merge once the tests pass, right?

Yes.

Great!
The pr build has now passed and the push build will fail due to a transient. I don't see any reason to bother restarting the push build. Merging.

authors: jbednar jlstevens philippjfr

repo: ioam/holoviews


text:
stopAdaptersOnSamePort doesn't work

@GermanBluefox I think this logic is trying to be too smart for it's own good. I do not like it at all for a number of reasons:

It fails on my system here because there is an old web instance running, which uses the old Let's Encrypt method which does not have the listen port defined in port but of course defined in lePort and thus isn't found.
There is absolutely no way to guarantee other adapters won't have similar config and be missed. I note, for example, that you changed the name of the port config in this adatper to be port for consistency but that's only because you know about this. It will be very hard to police this. I don't like that you made that change - I prefer verbose names as much as possible for clarity.
To avoid the above, if you think users can't be trusted to properly configure ports (see point 5) there really should be a mechanism for port management with a nice API or whatever for adapters to use to check ports, request port release, notify port release, etc, etc. I doubt this is going to happen any time soon (or even ever?).
I really do not like the idea of one adapter stopping another like this. There is no safeguard to absolutely guarantee that an adapter would be restarted if ACME crashed.
If someone has configured their system to use the same ports for two different adapters then IMHO that is a big mistake. I think the an adapter should fail with the address already in use message so the system owner can find an alternate port.
If you absolutely insist that this function should stay (and why would we keep something with all the above issues?) then I think there should be an option to disable it, and if enabled, there should be logging all over that start/stop logic to let a system owner know what's going on. Imagine the frustration of not knowing why an adapter has restarted seemingly randomly.

And the most obvious reason: the challenge server only ever runs on the public facing port 80 (or where that has been forwarded to) which is for insecure HTTP. If one is using ACME that implies they also want to use HTTPS, not HTTP, and therefore would never have anything else running on the same insecure HTTP port anyway!

Why we should do something to complex if it could be simple? :)
Best practice is "port" for the port number and leEnabled/lePort for letsencrypt ports. Just now leEnabled/lePort will be replaced by your adapter, but port will be required from now during review. And we will make a requests to other adapters to change name of port and bind address to port and bind (and may be to v6bind).
Latest Admin version has JSON-Config type port. It checks if the port is free (by name of course)

Why we should do something to complex if it could be simple? :) Best practice is port for the port number and leEnabled/leUpdate/leCheckPort for letsencrypt ports. Just now leEnabled/leUpdate/leCheckPort will be replaced by your adapter, but port will be required from now during review. And we will make a requests to other adapters to change name of port and bind address to port and bind (and may be to v6bind). Latest Admin version has JSON-Config type port. It checks if the port is free (by name of course)

@GermanBluefox - Guess I've been outvoted :cry:

authors: GermanBluefox raintonr


text:
Update stable version in repo from 2.0.5 to 2.1.0

Think about update stable version to 2.1.0
Version: stable=2.0.5 (221 days old) => latest=2.1.0 (15 days old)
Installs: stable=794 (66.06%), latest=155 (12.9%), total=1202
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 2.1.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 2.1.0 but the current stable version is already 2.1.0.
So this issue should be closed.
@mcm1957 for evidence


text:
iof-av:adaptedFrom should be URL not literal

You define iof-av:adaptedFrom thusly:
iof-av:adaptedFrom  rdf:type  owl:AnnotationProperty ;
        rdfs:subPropertyOf  dcterms:source ;

dct:source is merely rdf:Property but there's a skos:note "This term is intended to be used with non-literal values": that's really the difference between dct:source and dc:source
So iof-av:adaptedFrom should also point to a resource.
But then you use it as a string:
iof-core:roleOf  rdf:type   owl:ObjectProperty ;
        iof-av:adaptedFrom  "http://purl.obolibrary.org/obo/RO_0000081" ;

Please change this to a URL <http://purl.obolibrary.org/obo/RO_0000081>.
Which will have the added benefit that many tools will show it as a clickable link.

In other cases you use a literal with URI datatype:
iof-core:isOutputOf  rdf:type  owl:ObjectProperty ;
        iof-av:adaptedFrom  "http://www.ontologyrepository.com/CommonCoreOntologies/Mid/ExtendedRelationOntology"^^xsd:anyURI ;

That's a bit better, but I've asked before what's the benefit of such literal compared to a real URL.
I found only one benefit so far: if the URL is invalid, a repository will reject the URL but will happily accept the xsd:anyURI.
Which is not the case here!

repo: iofoundry/Core


text:
DeepLinker doesn't handle reloading views when parameters change

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
Current behavior:
If I have an app with a segment like /foo/:id and I change from say /foo/1 to /foo/2 in the browser bar (or via window.location), ionic doesn't detect and change this appropriately. Hitting F5 to reload the app then loads id 2 correctly.
I believe this is due to the loop in DeepLinker's _loadViewForSegment which calls done() only when comparing the viewcontroller/segment ids rather than the data that has been passed.
Expected behavior:
Changing a route parameter the browser bar or window.location should cause ionViewWillEnter to trigger
and the navParams to reflect the new details.

I've noticed this, however I find that if I tell it to go to the url twice it will work.

change url from www/1 to www/2
hit enter, page does nothing
click to enter the address bar again
hit enter, page will navigate.

@davec21 believe this is the browser intellegently refreshing the page when you try navigating twice rather than anythnig coming from ionic itself.

@mzealey Definitely possible!

repo: ionic-team/ionic


text:
bug:   Infinite scroll does not trigger when using smaller page size

I have a component which handles infinite scroll for different Items
<ion-list>
  <div *ngIf="!config?.isSliding">
    <ng-template *ngFor="let entity of entityList" [ngTemplateOutlet]="template" [ngTemplateOutletContext]="{entity: entity}">
    </ng-template>
  </div>
</ion-list>
<ion-refresher (ionRefresh)="refresh($event)">
    <ion-refresher-content pullingIcon="arrow-dropdown" pullingText="Pull to refresh"
                              refreshingSpinner="circles" refreshingText="Refreshing...">
    </ion-refresher-content>
</ion-refresher>
<ion-infinite-scroll threshold="10%" *ngIf="!config?.isReverse && !isPagingComplete"
  (ionInfinite)="loadData($event)" position="bottom">
    <ion-infinite-scroll-content
      loadingSpinner="bubbles"
      loadingText="Loading more data">
    </ion-infinite-scroll-content>
</ion-infinite-scroll>

If I make a request for a page of items that is smaller than the viewport, the Infinite scroll stops working.  In Ionic 3 I solved this issue by checking the height of this list.
assureInfiniteScrollIsPopulated() {

    if (this.isPagingComplete) {
        return;
    }

    // Do this after the dom is rendered
    setTimeout(() => {
        const scrollContent = this.elementRef.nativeElement.closest('.scroll-content');

        if (!scrollContent) {
            return;
        }

        if (!this.isVScrollable(scrollContent)) {
            this.getNextPage();
        }
    });
}

isVScrollable(nativeElement: any) {
    return nativeElement.scrollHeight > nativeElement.clientHeight;
}

They've removed the scroll-content class and there is nothing really meaningful to filter on.
How can I ensure the list is populated?

Thanks for the issue. Is this still an issue with the latest version of Ionic Framework? If so, please provide a repo with the code required to reproduce this issue.


text:
src/components/tabs/tabs.ts

I added a new part about "Dynamic Tab Selection" because it wasn't clear previously. There are a lot of forum that talk about how call a specific tab from any page but the solutions are always strange or dirty. I hope that this adding can is helpfull for other developer
Short description of what this resolves:
Changes proposed in this pull request:

Ionic Version: 1.x / 2.x / 3.x
Fixes: #

Hello and thank you for contributing to Ionic! We have been working on porting all of the Ionic components to web components and have recently updated master to reflect this. This significant change has caused this pull request to break. While we really appreciate the time and effort you put into creating this, we are not able to merge it because of the newly introduced conflicts. We are extremely sorry about this. We will not be merging any more features in to v3. If this is a feature and you have the time, please resubmit this PR against the master branch. If this is a critical security issue in v3, we would greatly appreciate it if you would resubmit the PR against the new v3 branch. Thanks so much for your time!

authors: Ionitron vinzZappavigna


text:
Prevent error on autocomplete lookbehind

Believe this fixes #147 - the 1-based offset was going past the end of text because the case of starting at 0 was excluded. (e.g. typing # at the start of an empty file).

LGTM

authors: cloudRoutine nwolverson

repo: ionide/ionide-fsharp


text:
Improve build.cmd Error message

build.cmd failed with a cryptic error.
I looked in the code and found that the missing vsce was the reason.
This improves the error message.
I hope the indenting is OK (Is ther a f#-format )
Thanks for the great work.
old message
FsiEvaluationException:

Error: System.NullReferenceException: Object reference not set to an instance of an object.
           at FSI_0005.Build.platformTool(String tool, String path) in C:\open\ionide-vscode-fsharp\build.fsx:line 53
           at <StartupCode$FSI_0005>.$FSI_0005_Build$fsx.main@() in C:\open\ionide-vscode-fsharp\build.fsx:line 58
        Stopped due to error

new failure
FsiEvaluationException:

Error: System.Exception: can't find tool vsce on PATH
           at Microsoft.FSharp.Core.Operators.FailWith[T](String message)
           at <StartupCode$FSI_0005>.$FSI_0005_Build$fsx.main@() in c:\open\ionide-vscode-fsharp\build.fsx:line 64
        Stopped due to error

Thanks a lot!

authors: Krzysztof-Cieslak fbehrens

repo: ionide/ionide-vscode-fsharp


text:
script async syntax support

make groovy/java script support async/await syntax.

#11

have some problems with multi nested CompletableFuture

script can define without class

repo: iotaki/immanuel


text:
Private Tangle: Spammer fails

Describe the bug
When starting the private tangle the Spammer goes into a crash loop, reproduceable locally and in CI.
Anecdotally beta.9 shows the same behavior locally, where beta.8 works. But in beta.8 the Faucet does not come up initially , although it works after restarting the container.
To Reproduce
Steps to reproduce the behavior:

Pull latest private_tangle from GitHub releases or use latest dev branch
Start private tangle
See error

inx-spammer          | 2022-09-26T10:27:24Z	INFO	INX	Connecting to node and reading node configuration ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	INX	Reading node status ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Setting up spammer ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Address for Sender: tst1qqweu75ldpyann5jsthqsa6m0thx4tmqxncj6uqxf5q974pmqx30y5mcdp2
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Address for Receiver: tst1qqkzz4kd0e5gz5dwequ8mwvjljd78gzh4hv677djcqe3cj28je7u5c6n09a
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading core components ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading core components: INX ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading core components: Spammer ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading core components: Shutdown ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading plugins ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading plugin: Profiling ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Loading plugin: Prometheus ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Executing core components ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting core component: INX ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting core component: Spammer ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting core component: Shutdown ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Executing plugins ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting plugin: Profiling ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting plugin: Prometheus ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	App	Starting background workers ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Prometheus	Starting Prometheus exporter ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Prometheus	You can now access the Prometheus exporter using: http://172.18.211.26:9311/metrics
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Profiling	You can now access the profiling server using: http://172.18.211.26:6060/debug/pprof/
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Starting Spammer 1 ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	INX	Starting NodeBridge ...
inx-spammer          | ⇨ http server started on 172.18.211.26:9311
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Starting API ... done
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Starting API server ...
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	You can now access the API using: http://172.18.211.26:9092/
inx-spammer          | ⇨ http server started on 172.18.211.26:9092
inx-spammer          | 2022-09-26T10:27:24Z	INFO	Spammer	Starting API server ... done
inx-spammer          | 2022-09-26T10:27:43Z	WARN	Shutdown	Critical App self-shutdown: Spammer plugin hit a critical error while applying new ledger update: context deadline exceeded; waiting (max 300 seconds) to finish processing ...
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Prometheus	Stopping Prometheus exporter ...
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Prometheus	Stopping Prometheus exporter ... done
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Spammer	Stopping API ...
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Spammer	Stopping API ... done
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Spammer	Stopping Spammer 1 ...
inx-spammer          | 2022-09-26T10:27:43Z	INFO	Spammer	Stopping Spammer 1 ... done
inx-spammer          | 2022-09-26T10:27:43Z	INFO	INX	Stopped NodeBridge
inx-spammer          | 2022-09-26T10:27:43Z	INFO	App	Shutdown complete!

Expected behavior
Spammer should start and stay up.
Environment information:

OS: GitHub runner ubuntu-latest and locally Ubuntu 22.04
Hornet Version: beta.10

Thanks for the bug-report. I could reproduce it and a fix for the inx-indexer is incoming. This should fix the spammer issue.
I'll close this ticket as soon as the fix is released.

Ok, should work now. Please run ./bootstrap.sh build or do a docker compose pull inx-indexer

Can confirm it works on latest dev. Thank you for the swift resolution!

authors: alexsporn eike-hass

repo: iotaledger/hornet


text:
Rust Identity Actor

Description of change
This implements an initial version of an identity actor, a peer-to-peer communication framework for identity related operations. It is intended to host implementations of the DIDComm protocols with future updates. Together with these protocols, this will, for example, allow for did-authenticated communication between two identities to exchange verifiable credentials or presentations.
This description serves as a technical introduction to the actor. For a high-level and less technical introduction, see the blog post on the actor.
The most important component of the actor is libp2p. What is libp2p?

The one-liner pitch is that libp2p is a modular system of protocols, specifications and libraries that enable the development of peer-to-peer network applications.

We use libp2p because it can easily secure transports using the noise protocol, is agnostic of transports so actors could conceivably communicate over TCP, websockets or Bluetooth, and because of how flexible it is, we can make it suit the actor nicely.
Building an actor
let id_keys = libp2p::identity::Keypair::generate_ed25519();
let addr: libp2p::Multiaddr = "/ip4/0.0.0.0/tcp/0".parse().unwrap();

let dns_transport = lib2p::dns::TokioDnsConfig::system(libp2p::tcp::TokioTcpConfig::new())?;
let transport = dns_transport.clone().or_transport(libp2p::websocket::WsConfig::new(dns_transport));

  let actor: Actor = ActorBuilder::new()
    .keypair(id_keys)
    .listen_on(addr.clone())
    .build_with_transport(transport)
    .await?;

To build a minimal working actor, we generate a new KeyPair from which the PeerId of the actor is derived. The PeerId is a libp2p concept to allow for cryptographically verifiable identification of a peer. This decouples the identity concept from the underlying network address, which is important if the peer moves across networks. Next we create the address for the actor to listen on. A Multiaddr is the address format in libp2p to encode addresses of various transports. Finally, we setup the transport, which supports DNS resolution and can use TCP or websockets.
Processing incoming requests
To make the actor do something useful, we need handlers. A handler is simply an asynchronous function (or closure) that processes an incoming request and will be invoked if the actor is able to deserialize the incoming request to the type the handler expects. A handler has as its input:

an object that holds the state in-between handler invocations and across different handlers. The requirement is that it is Clone, Send and Sync. A copy of the state object will be injected into each invocation of the handler, so the idea is that it will usually wrap its content in Arcs.
a copy of the Actor, which can be used to send or receive messages from within handlers.
the request it wants to handle, which needs to implement the ActorRequest trait.

Here is an example of a handler function being registered on an ActorBuilder, which uses RemoteAccounts - some exemplary type that manages Accounts remotely.
#[derive(Clone)]
pub struct RemoteAccounts {
    accounts: Arc<dashmap::DashMap<identity_iota::did::IotaDID, identity_account::account::Account>>,
}

#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct RemoteAccountsGet(pub IotaDID);

impl ActorRequest<Synchronous> for RemoteAccountsGet {
  type Response = Result<IotaDocument, RemoteAccountError>;

  fn endpoint() -> Endpoint {
    "remote_accounts/get".parse().unwrap()
  }
}

builder
    .add_state(RemoteAccounts::new())
    .add_sync_handler(
        |remote_accounts: RemoteAccounts, _actor: Actor, request: RequestContext<RemoteAccountsGet>| async move {
            remote_accounts
            .accounts
            .get(&request.input.0)
            .map(|account| account.document().to_owned())
            .ok_or(RemoteAccountError::IdentityNotFound)
        },
    );

We also define the struct that will be sent over the network, RemoteAccountsGet. It has a DID as its parameter that we want to lookup on the remote and retrieve the document of the associated account. It defines its return type in the ActorRequest implementation - why ActorRequest is generic will be discussed later. It also defines the endpoint it is associated to - "remote_accounts/get" in this case. Endpoints are identifiers for handlers.
First we add an instance of the RemoteAccounts as a shared state object. Then we add a handler function that will be invoked for requests to the endpoint "remote_accounts/get", and returns the IotaDocumemt if it can find the DID. If we wanted, we could attach more handler functions to the same state object. While we're using a closure here, a regular async function with compatible parameters would also work.
Sending requests
To invoke such a handler on a remote actor, we send an instance of an ActorRequest.
let mut actor = ActorBuilder::new().build().await?;
actor.add_address(remote_peer_id, addr).await?;

let result: Result<Result<IotaDocument, RemoteAccountsError>, identity_actor::Error> =
    actor.send_request(remote_peer_id, RemoteAccountsGet("did:iota:...".parse().unwrap()));

After building the actor and adding the address of the remote peer, we can send a request. The actor takes care of serializing the request, and attempts to deserialize the response into ActorRequest::Response of the RemoteAccountsGet type.
Actor modes
We've just seen an example of a synchronous request, one where we invoke a handler on a remote actor and wait for it to finish execution and return a result. The actor supports an alternative asynchronous mode, where we send a message without waiting for the result of the handler invocation. Instead, we can explicitly await a message:
fn didcomm_protocol(didcomm_actor: &DidCommActor) -> ActorResult {
  let thread_id = ThreadId::new();

  didcomm_actor
      .send_message(peer, &thread_id, PresentationOffer::default())
      .await?;

  let request: DidCommPlaintextMessage<PresentationRequest> = actor.await_message(&thread_id).await?;
}

This request mode is only implemented to support DIDComm protocols, which is why a separate DidCommActor is introduced that extends the Actors functionality and handles the specifics of DIDComm. Note that the base Actor doesn't support the asynchronous mode.
Here, the protocol expects us to first exchange a PresentationOffer message, before receiving a wrapped PresentationRequest. This allows for imperative protocol implementations within a single actor handler. This is nice to have, because the alternative would be that each message invokes a separate handler on an actor, which would force protocol implementors to hold the state in the shared state object, rather than implicitly in the function (such as the thread_id here). This mode of operation is primarily intended for DIDComm protocols, as it directly implements DIDComm concepts such as threads.
These two modes of operation are what require the ActorRequest to be generic over the SyncMode, i.e. Synchronous or Asynchronous. This allows us to write two separate send functions for each mode and ensure a match of mode to function at compile-time.
Hooks
While the asynchronous mode of operation allows for implementation of DIDComm protocols, it does not yet allow users to hook in their own logic. This might be required to ask a user for consent before proceeding with the exchange of a credential. To that end, the DidCommActor has the concept of hooks, which are similar to handlers. There are various approaches to hooks:

Implicit hooks: There is an implicit hook point for each message that goes over the network that users can add logic to. They are implicit in that the protocol implementer is not required to define them, they are automatically there.
Explicit hooks: The protocol defines the hooks explicitly within the protocol. This is complementary to the implicit approach.
Hook closures: The function that implements an async mode protocol takes hooks as explicit closure arguments. The actor itself has no concept of hooks in this model.
Hook trait: Similar to the closures approach, but defining all hooks as methods on a trait and requiring users to implement that trait.

The actor currently implements the implicit hooks approach, mostly as an exploratory option, not necessarily because it was deemed the best one. Suppose we want to insert custom logic before await_message returns the PresentationRequest in the above eample. One registers a hook like so:
async fn receive_presentation_request_hook(
    state: HookState,
    _actor: DidCommActor,
    req: RequestContext<DidCommPlaintextMessage<PresentationRequest>>,
) -> StdResult<DidCommPlaintextMessage<PresentationRequest>, DidCommTermination> {
    // Custom logic, like modifying the input or obtaining user consent.
    Ok(req.input)
}

builder
    .add_state(HookState::new())
    .add_hook(receive_presentation_request_hook)?;

The signature of a hook function is very similar to a handler, except for its return type. It needs to return the same type that it received as input or an instruction for the actor to terminate the connection. The endpoint of a hook includes the /hook postfix, and indicates to the actor that this hook should be called either before an ActorRequest with a didcomm/presentation_request endpoint is sent, or before it is returned from await_message, as is the case in this example.
Limitations
The limitation of this hook implementation is thus that the user can only insert custom logic in between network requests, but not at arbitrary points in the protocol. With the current implementation (and some small modifications), it would also be possible to allow protocol implementors to define arbitrary hook points and call them.
In theory hooks can be attached to the same state as a handler, so they can access and modify the handlers state. However, in practice we will likely have a function that adds certain protocol handlers to an ActorBuilder and a user will add their hooks at other points. At this point, however, the ephemeral HandlerBuilder will have gone out of scope and no more typing guarantees could be given that a hook uses the same state object as a handler, e.g. there could be an incompatibility. Because of this lack of typing guarantees, it is currently not possible at all to attach a hook to some previously added state, as it seems very error-prone.
An alternative would be to use std::any::TypeId for identification of a state object, so if a handler and a hook take a certain OBJ type as state object, then the actor can determine the TypeId of the object and guarantee internally, that it will be called with the same object. The downside is, that users cannot add two different state objects that have the same TypeId.
Implementation Details
This section goes into some details of actor internals.
The overall architecture can be seen as four layers. A libp2p layer, a commander layer to interact with the libp2p layer, the raw actor layer (which uses the commander) and the DIDComm actor on top. This is strongly inspired by stronghold-p2p.

The p2p layer consists of a libp2p::RequestResponse protocol, which enforces on a type level that each request requires a response. This naturally maps to the sync mode of the actor where each request has some response, as well as to the async mode where each message will be acknowledged.
This layer has an EventLoop that concurrently polls the libp2p Swarm and handles its events, as well as commands that are sent to it from the NetCommander.
The commander layer, or NetCommander communicates with the event loop via channels and is thus the interface for the EventLoop.
When the actor is built, it spawns an EventLoop in the background and interacts with it using the NetCommander.
On incoming requests, the EventLoop spawns a new task and injects a clone of the actor into it (see EventLoop::run and its argument).
To build handlers type-safely, the HandlerBuilder is generic over the shared state object OBJ. (DidComm)HandlerBuilder::add_*_handler then requires the handler to be added, to have OBJ as the object parameter. This ensures a type match on the object at compile-time.
Since ActorRequest::endpoint returns an Endpoint statically for each ActorRequest, a type match can be ensured whenever the same ActorRequest is used. For example, when adding a hook with a given ActorRequest, then the actor ensures that the hook is called before/after the handler with the same ActorRequest is called. In other words, it's impossible to hook the wrong ActorRequest.

Examples
This PR does not add examples to the examples directory. This is mostly because I expect lots of changes are coming anyway, and this makes updating the code base easier. Still, there are two "examples" for each mode of operation, the remote account as a synchronous example, and the DIDComm presentation protocol as an asynchronous example. These live inside the crate rather than as outside examples, because we will probably want to ship something like that at some point. Especially the DIDComm example is very simple and minimal and mostly exists as a proof of concept for the async mode, but it also serves as an example for how a DIDComm protocol could potentially be implemented.
DIDComm example setup
The async mode didcomm examples are worth explaining a little more. The implementation difficulty for these protocols comes mostly because of how flexible they are. In the presentation protocol for example, both the holder and verifier can initiate the exchange. On the actor level, this means either calling the protocol explicitly to initiate it, or registering a handler to let the actor handle the protocol in the background when the other party initiates. Thus, there is one function that implements the actual protocol for each side (e.g. holder and verifier in the presentation protocol). As an example, this is what the holder actor would do:
pub async fn presentation_holder_handler(
  mut actor: DidCommActor,
  peer: PeerId,
  request: Option<DidCommPlaintextMessage<PresentationRequest>>,
) -> ActorResult<()> { ... }

The holder can call this function to initiate the protocol imperatively by passing None as request. On the other hand, if the verifier initiates, the holder defines an actor handler function that will inject some request:
impl DidCommState {
  pub async fn presentation_holder_actor_handler(
    self,
    actor: DidCommActor,
    request: RequestContext<DidCommPlaintextMessage<PresentationRequest>>,
  ) {
    let result = presentation_holder_handler(actor, request.peer, Some(request.input)).await;

    if let Err(err) = result {
      log::error!("presentation_holder_actor_handler errored: {:?}", err);
    }
  }
}

and registers it:
didcomm_builder
      .add_state(handler)
      .add_async_handler(DidCommState::presentation_holder_actor_handler);

This allows us to nicely reuse the presentation_holder_handler function as the core protocol implementation and only requires defining a thin actor handler. The verifier can follow the same pattern for their side of the protocol.
Additional notes

In async mode, the DidCommActor returns an acknowledgment if 1) a handler for the endpoint or a thread exists and 2) if the request can be deserialized into the expected type for the handler of thread (e.g. a DIDComm plaintext message)
Timeouts can occur in two ways and both are configured via ActorBuilder::timeout.

A request sender can receive an InboundFailure::Timeout if the peer did not respond within the configured timeout. This happens on the event loop level and is handled by the RequestResponse protocol.
Actor::await_message can timeout. This is the same timeout value as for the underlying RequestResponse protocol. In such a case, the event loop will receive a timeout error, but since no entry in the hash map is waiting for a response, it is silently dropped. Thus, await_message implements its own timeout, and automatically uses the same duration as the underlying protocol to ensure consistent behaviour. For this reason, the await_message timeout is a per-actor configuration value, and not a parameter on the function, although that would also be possible if desired.

ActorRequest::endpoint is not absolutely necessary for async requests, as most messages in such a protocol (like DIDComm) would be identified via a ThreadId rather than an endpoint. For now, endpoints are however also used for hooks, and since all endpoints are implicitly hookable, the endpoint requirement on ActorRequests still makes sense. If we change how hooks work or remove them as an explicit actor feature, then endpoints can be re-thought.

Open Questions

Do we need more type safety for handlers and ActorRequests? That is, should we use and encourage usage of something like protocol buffers?
Is the hook implementation sufficient for real world usage? I believe we need to implement protocols first and see it in practice, but my hunch is that we will have to have a different hooking mechanism.
There are a lot of clones of actors or objects, which is what requires heavy usage of Arc internally and on the user side. The initial attempt to design handlers with lifetimes did not succeed, which is why the current version does not have them. Since handlers are spawned onto separate tasks and tokio::spawn or tokio::spawn_local require those futures to be 'static, it does not seem possible to omit that clone. However, within the handler, there is currently a second clone, which could possibly be removed. Whether this matters for real-world performance is debatable.
How do handlers clean up state? Is that supposed to be done in handlers themselves, and/or do we need to expose additional disconnect handlers/events that users can react to?
How would users add hooks in a type-safe way to a pre-configured actor/actorbuilder? Typing could be checked (based on TypeId), but only at hook registration time, not at compile-time.
Is the assumption that any await_message(thread_id) is preceded by a send_message on the same thread_id correct? Based on this assumption, the actor currently uses oneshot channels, but if multiple messages may be received on a thread, then a different channel type will have to be used. A MessageBuilder could be added whose result is passed into DidCommActor::send_message so threads can be created only when necessary.
Should we replace RequestMessage::from_bytes with some serialization that's faster or more compact? For now, it seems good enough to use json. Some crate like rkyv would make the actor potentially less easily portable, if it would ever receive an implementation in a foreign language, while json is highly compatible. How much that downside matters with our single source code of truth approach is debatable. But this particular RequestMessage type is fairly simple anyway, and so the serialization performance gains might not be that significant?
There is an attempt to call synchronous ActorRequests "requests", and asynchronous ones messages. However, that terminology is not ideal, because there is no umbrella term for request or message. So it is used interchangebly at times.
DIDComm problem reports are not implemented, but can be easily added.
Generics are not passed all the way through to the NetCommander or EventLoop, instead they already require serialized bytes. As of now, there doesn't seem to be any advantage of deferring serialization to a lower-level in the architecture, except perhaps for a nicer layering / concern separation. Definitely looking for input here.
Would it be better to be "more upfront" about the actual required bounds for an ActorRequest? For instance, to actually work, types implementing that trait need to be Sync, but this is not an explicit bound on the trait. Instead, it is only required where it is actually needed, such as on HandlerBuilder::add_*_handler.

Links to any relevant issues
fixes #299
Type of change
Add an x to the boxes that are relevant to your changes.

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] Enhancement (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Fix

How the change has been tested

A synchronous and asynchronous example implementation was added as remote_account and didcomm respectively.
Tests were added in identity-actor/src/tests which use those examples.

Change checklist
Add an x to the boxes that are relevant to your changes.

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

One question: is the identity-actor only used to communicate with between peers on the same system, or also between different devices/ networks. In case of the latter: how do you plan to connect peers that can not dial each other directly, e.g. because of firewalls or NAT?

The latter, indeed. We definitely want to add relay support in the future to enable those use cases, but it's not part of this initial, minimal version.

Addressed all your comments so far, @olivereanderson, thanks for taking a detailed look!

Addressed all your comments so far, @olivereanderson, thanks for taking a detailed look!

Thanks!

Also, tests require more documentation.

Can you be more specific what parts you would like to see documented? I now documented one of the end-to-end tests in more detail and most of them follow a similar pattern. Documenting tests thoroughly increases the maintenance burden by a lot, so I would refrain from just documenting them all. So perhaps you can point out more specifically what parts are unclear.

Thanks for the review! I addressed the comments.

Added some documentation for didcomm tests.
Removed one of the larger tests whose assertions are already tested in other tests, which should also make it easier to understand the test module. Let me know if it's better now, but feel free to request more docs if it's not yet sufficient.
Renamed System to Agent, and Actor to Handler.
Introduced a type alias AgentId for PeerId and use it everywhere, except for the p2p module (to keep modules loosely coupled).

Note that the Cargo.toml contains some TODOs which I don't think must be addressed in this PR. It has to do with some of our crates (identity_iota_client and identity_account_storage) not properly supporting default-features = false, which should be addressed in a separate PR.

authors: PhilippGackstatter olivereanderson


text:
Ensure test coverage of #1557

Description
https://github.com/iotaledger/iota-sdk/pull/1557 was submitted at the time of Python bindings being broken for 2.0, making its testing tricky. It should be revisited once the bindings (and the tests) work again.
Are you planning to do it yourself in a pull request?
Yes.

It's tested in https://github.com/iotaledger/iota-sdk/blob/0ac4ff46671966c83296e329b284f422d434af19/bindings/python/tests/test_output.py#L29 now https://github.com/iotaledger/iota-sdk/blob/0ac4ff46671966c83296e329b284f422d434af19/bindings/python/tests/test_output.py#L183-L185

authors: Thoralf-M tadzik

repo: iotaledger/iota-sdk


text:
add shadow

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind api-change
/kind backend-change
/kind ui-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

please resolve conflicts

authors: blesstosam puncsky

repo: iotexproject/iotex-explorer


text:
🛑 备用KMS激活服务器 01 is down

In dba1f11, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in fa7ab69 after 25 minutes.

repo: iougemini/ikms-uptime


text:
🛑 备用KMS激活服务器 01 is down

In b13833f, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 86c3743 after 18 minutes.


text:
🛑 备用KMS激活服务器 01 is down

In ca5eae2, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in ba15d08 after 9 minutes.


text:
🛑 备用KMS激活服务器 01 is down

In b7d98e3, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 10a462d after 10 minutes.


text:
Added musl support

memfrob is a glibc function, so we reimplement it if it doesn't exist. endian.h is required for the htobe* functions.

Coverage remained the same at 96.049% when pulling d9e87d33fd27fbd96b8dd2d9768fcbf1ca3704ec on jpsamaroo:musl into 089f6279752adfb01386600d119913403ed326ee on iovisor:master.

Great. Any idea when we can get this merged?

@pchaigno said they'll be free soon to review open PRs during/after the holidays.

Bump @pchaigno

@pchaigno I'd really like to have this merged if possible; without it, I have to constantly rebase when I test changes in my other branches.

@rlane would you be willing to merge this? I think it's pretty simple and harmless to non-musl systems.

Bump @rlane

authors: Alan-Jowett coveralls jpsamaroo

repo: iovisor/ubpf


text:
🛑 Rasadnik FYI is down

In 0a37dbc, Rasadnik FYI (https://rasadnik.fyi/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Rasadnik FYI is back up in c27075f after 25 minutes.


text:
Spruce up the homepage hero and add basic layout

A responsive first draft of the home page layout

sm
md
lg

There the question about naming pads... the new homepage design does away with asking users to name their pads before creating them, so to implement it without breaking things i'm defaulting the pad name to New PeerPad which is ok, but then every new pad url will have that in it, so if we can do without encoding the name into the url, then maybe we should take it out?

👓

authors: alanshaw olizilla

repo: ipfs-shipyard/peerpad


text:
Q1 2017 Blog Post

@flyingzumwalt mentioned putting together a blog post (https://github.com/ipfs/pm/issues/365#issuecomment-272755766) and I think that's a great idea - wanted to get the ball rolling here.

In blog post, if we write it, we should discuss
stale endeavors
lessons learned about kanban (loosely coordinated vs. not coordinated)
thrashing
sprints, sprintinos

@flyingzumwalt would you like to author this and flesh this out? I feel like you would be the best person to put this piece together.

I doubt that I'll have time for it during the next 2 weeks. data.gov gets priority.

Understandable - is anyone willing to pick this up?

I might still be the right one to write it, but that would mean putting out the post in early February. Alternative: put out a basic post now, explaining the changes and pointing to the roadmap, and I can write a more complete explanation in February.

I agree - With the changes to the sprint formats, I think it's important to get a brief post out earlier, mostly introducing the new structure of the sprints. This can also include pointing to the roadmap and the first all hands covering the changes.
Having a more expanded post in the future is a good idea, especially once the dust settles and we're more in-tune to any areas of clarifications that are needed about the process. It will give time for people to engage and respond to the new process. It might also be a good idea to open up a discourse conversation about the new sprint format, to start fostering feedback and directing questions.
Do you think you would be able to put together a brief post this week?

I'm maxed out this week. I think someone else could write the first brief, informative post with links to the roadmap and the all-hands video. @RichardLitt would you be able to put that basic post together?

@flyingzumwalt I've stubbed out one, here. We should merge the Stale Endeavors PR in ipfs/ipfs, first, and we should also have a way of showing the roadmap in ipfs/pm. Can you take a look and tell me if you want me to severely edit the blogpost before a final polish?
https://github.com/ipfs/blog/blob/feat/q1-blogpost/src/23-2017-q1-update/index.md

@flyingzumwalt Can you please review the above?

Reviewed and updated.

Lgtm!
On Wed, Jan 25, 2017 at 9:06 PM Matt Zumwalt notifications@github.com
wrote:

Reviewed and updated.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ipfs/blog/issues/90#issuecomment-275272403, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA3loaFKS4oE3O9DrBPD1M7rNU0CI3Cyks5rV-OFgaJpZM4Lk4Vx
.

Closing b/c team decided not to publish at the time, and window of opportunity has passed.

authors: RichardLitt em-ly flyingzumwalt mishmosh

repo: ipfs/blog


text:
IPFS walkthrough

Can we do this real quick today on the call?

@autonome Doesn't look like we'll have time for this, and I think I've done it myself anyhow this week.
However, if you still think it's worth doing, let me know.

repo: ipfs/browser-design-guidelines


text:
seed nicer go-ipfs index page assets

License: MIT
Signed-off-by: Henry cryptix@riseup.net

Thanks, seeded.

authors: cryptix jbenet

repo: ipfs/infrastructure


text:
Cannot use with electron-builder when asar: false

I'm trying to use this module for the Agregore Browser with the latest version of Electron and I'm trying to use ESM.
Although Electron doesn't support ESM natively, it's possible to use it if one disables ASAR support and imports files from the filesystem.
However, for some reason electron-builder has been getting me the following error when I try to build a binary without ASAR (on Liunux). You can find more detailed build logs here: https://github.com/AgregoreWeb/agregore-browser/actions/runs/4009313691/jobs/6884515962#step:5:99
 • asar usage is disabled — this is strongly not recommended  solution=enable asar and use asarUnpack to unpack files that must be externally available
  ⨯ ENOENT: no such file or directory, symlink '/home/mauve/programming/agregore-browser/node_modules/go-ipfs/go-ipfs/ipfs' -> '/home/mauve/programming/agregore-browser/release/linux-unpacked/resources/app/node_modules/go-ipfs/bin/ipfs'  failedTask=build stackTrace=Error: ENOENT: no such file or directory, symlink '/home/mauve/programming/agregore-browser/node_modules/go-ipfs/go-ipfs/ipfs' -> '/home/mauve/programming/agregore-browser/release/linux-unpacked/resources/app/node_modules/go-ipfs/bin/ipfs'
    at processImmediate (node:internal/timers:471:21)
From previous event:
    at Object.copyAppFiles (/home/mauve/programming/agregore-browser/node_modules/app-builder-lib/src/util/appFileCopier.ts:85:27)

Sometimes not using ASAR is important to making apps work and this is currently prevent that option from being pursued.
Are there any thoughts on what can be done about this or what I can do to debug the issue further?
I'll post any fixes I find here as I go.

I ended up having asar:true but extracting pretty much all the files at runtime to get it to work. 🙃
https://github.com/electron/electron/issues/21457#issuecomment-1404327157

repo: ipfs/npm-go-ipfs


text:
🛑 NowBoarding (tokyo) is down

In b929b6c, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NowBoarding (tokyo) is back up in 25eef43 after 5 minutes.

repo: iplanwebsites/up


text:
Only first channel fetched

Using these versions on mac, the generated guide (guides/en/bt.com.xml) has only 1 channel, even through all other channels are pulled correctly.
% npm --version
9.3.1
% node --version
v18.14.0
npm run grab -- --site=bt.com --lang=en

grab
node scripts/commands/epg/grab.js --site=bt.com --lang=en

◐ staring...                                                                                9:56:42 AM
ℹ settings:                                                                                9:56:42 AM
ℹ   gzip: false                                                                                9:56:42 AM
ℹ   site: bt.com                                                                                9:56:42 AM
ℹ   lang: en                                                                                9:56:42 AM
ℹ   output: /Volumes/WorkDisk/lucru/video/epg/guides/{lang}/{site}.xml                                                                                9:56:42 AM
ℹ   config: /Volumes/WorkDisk/lucru/video/epg/sites/bt.com/bt.com.config.js                                                                                9:56:42 AM
ℹ   channels: /Volumes/WorkDisk/lucru/video/epg/sites/bt.com/bt.com*.channels.xml                                                                                9:56:42 AM
ℹ config:                                                                                9:56:42 AM
ℹ   site: bt.com                                                                                9:56:42 AM
ℹ   days: 2                                                                                9:56:42 AM
ℹ creating queue...                                                                                9:56:42 AM
[Error: ENOENT: no such file or directory, open '/Volumes/WorkDisk/lucru/video/epg/scripts/tmp/data/channels.json'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/Volumes/WorkDisk/lucru/video/epg/scripts/tmp/data/channels.json'
}
ERROR  Unexpected token u in JSON at position 0                                                                                9:56:42 AM
at JSON.parse ()
at API.load (scripts/core/api.js:13:28)
at async createQueue (scripts/commands/epg/grab.js:123:3)
at async main (scripts/commands/epg/grab.js:42:17)
ℹ   loading "/Volumes/WorkDisk/lucru/video/epg/sites/bt.com/bt.com.channels.xml"...                                                                                9:56:42 AM
ℹ   added 326 items                                                                                9:56:42 AM
ℹ run #1:                                                                                9:56:42 AM
ℹ   [1/326] bt.com (en) - 4seven.uk - Sep 15, 2023 (28 programs)                                                                                9:56:47 AM
ℹ   [2/326] bt.com (en) - 4seven.uk - Sep 16, 2023 (28 programs)                                                                                9:56:51 AM
ℹ   [3/326] bt.com (en) - 5Action.uk - Sep 15, 2023 (24 programs)
...
Resulted guide has only 1 channel.
egrep "channel id"  guides/en/bt.com.xml
4sevenhttps://bt.com

Fixed in #2171

authors: freearhey marianpopeanga

repo: iptv-org/epg

license: Unlicense


text:
Tooltips for sliders

The title says it all: basically, often it would be quite useful to have tooltips when hovering over a slider, with these tooltips showing the value (or label for selection slider) which will be selected if clicking at this point.

It would be easy to implement a tooltip for the slider handle. I think it would be hard to implement a tooltip over the slider track (though maybe not impossible).

authors: aplavin jasongrout

repo: ipython/ipywidgets


text:
HTTP Error 400 at EC conversion

Hello! Thanks for making what seems to be some very useful software...however, after a seamless install, I'm running into a problem getting the info from KEGG through the API on a simple first test run of data:
(base) andre@vulcan:~/MirallesProjects/CanteraMGS-CEMEX2018$ keggcharter -f MirallesMetaG-unstrat-matrix-RPKM_final.txt -o keggcharter/first_test -it 'MirallesMGS-CEMEX2018' --map-all -t 40 -ecc 'function' -qcol 'N1,N2' -mm 00680
Created keggcharter/first_test/maps
Created keggcharter/first_test/json
Created /home/andre/bin/miniconda3/share/kc_kgmls
Created /home/andre/bin/miniconda3/share/kc_csvs
2023-12-30 01:51:20: Reading input data.
2023-12-30 01:51:20: Arguments valid.
Converting 2880 EC numbers to KOs through the KEGG API:   0%|                                                                                | 0/72 [00:00<?, ?it/s]IDs conversion broke at index 0; Error: HTTP Error 400: Bad Request; Trying again...
IDs conversion broke at index 0 again; Error: HTTP Error 400: Bad Request
Converting 2880 EC numbers to KOs through the KEGG API:   1%|=                                                                                | 1/72 [00:02<03:05,  2.61s/it]IDs conversion broke at index 40; Error: HTTP Error 400: Bad Request; Trying again...
IDs conversion broke at index 40 again; Error: HTTP Error 400: Bad Request
Converting 2880 EC numbers to KOs through the KEGG API:   3%|==>                                                                                | 2/72 [00:05<02:54,  2.49s/it]IDs conversion broke at index 80; Error: HTTP Error 400: Bad Request; Trying again...
IDs conversion broke at index 80 again; Error: HTTP Error 400: Bad Request
Converting 2880 EC numbers to KOs through the KEGG API:   4%|====                                                                                | 3/72 [00:07<02:48,  2.44s/it]IDs conversion broke at index 120; Error: HTTP Error 400: Bad Request; Trying again...
IDs conversion broke at index 120 again; Error: HTTP Error 400: Bad Request
Converting 2880 EC numbers to KOs through the KEGG API:   6%|=====>                                                                                | 4/72 [00:09<02:45,  2.43s/it]IDs conversion broke at index 160; Error: HTTP Error 400: Bad Request; Trying again...
IDs conversion broke at index 160 again; Error: HTTP Error 400: Bad Request

This is happening with the same install on our two different servers and at first I thought it might be a problem with our servers' firewalls preventing it, but I can successfully query the KEGG REST server from our servers (using example wget http://rest.genome.jp/link/hsa:56894) and get the results back. So do you think there has been a change in the way the REST API is called since you created the software? Or do you think from my side still? Thanks!

PS: Here is the command used and a snippet of the top of the input file used, for reference:
keggcharter -f MirallesMetaG-unstrat-matrix-RPKM_final.txt -o first_time_running_KC -it 'MirallesMGS-CEMEX2018' --map-all -t 40 -ecc 'function' -qcol 'N1,N2' -mm 00680
Function	N1	N2	N3	P10O	P11O	P12OR1	P12OR2	P13O	P14O	P15O	P16O	P17O	P18O	P1O	P2O	P3O	P4O	P5O	P7O	P8O	P9O
EC:6.3.2.6	344.2662444585336	435.49652106421223	364.8194144473019	317.3068637689078	366.0990998038725	516.9760211537803	568.644580298925	432.6393866595689	412.613879719137	465.41536088733426	471.2825228186336	495.9413141659699	383.43556844340225	441.2511621422144	527.8250327333293	447.3818739269597	499.5641019147747	481.70022854611335	389.6242969660617	656.551178801158	405.5655007957861
EC:4.1.1.32	226.6846979674137	217.31275187531926	214.43720409058798	151.30922168037176	170.0959414314209	184.89900160686122	225.37543307299217	100.70546930312044	243.04636800460992	118.75338804428371	152.9143264841801	196.12742573239737	233.35661625976704	196.95712313603335	139.96209057518257	159.2381858762867	121.55757690322207	140.33963475682995	208.62517575919054	89.03125291827901	168.26526952651773
EC:2.7.4.1	144.94586509972513	148.87215533130228	154.84316759799154	64.93105542036218	94.72963247849869	128.0788246599505	119.99145212534954	96.35865329943678	106.88893461965348	61.97422118927997	80.9392176719888	102.90219319598324	130.19578909237646	96.1525844377649	80.20711232901692	78.93090584829154	62.58248818578593	102.98626491158338	104.05695213260442	65.16020586269403	77.54892016179359
EC:3.6.5.n1	992.8852894013689	999.7737521934347	1015.6703441449205	929.7434098942456	1023.9106883884666	943.825715130447	1035.721008099207	1060.6701593262655	875.5266587380352	1096.0409937770326	1065.3274394834057	982.885256042751	834.1057301604101	842.7976006160397	1054.5105698712457	973.0561367040477	1056.598561803838	1031.7290807181873	897.383447643698	1147.5029279705548	975.1084096882113
EC:2.7.2.11	104.49869924765143	113.44152278343617	105.21502499318052	119.1479827332404	220.22393017668364	119.96438451277515	88.44176823025424	108.33987433516255	104.25652216146489	245.18986565782677	214.5825458509538	144.27658344724833	122.92567480434533	107.72444154615422	184.55202462902403	136.3070342464695	137.70203999285852	210.3264236353069	188.90692195927053	205.96189008692411	126.33717716759487
EC:5.3.3.2	54.548589381601204	20.75808014865597	45.060478151210795	135.40322362232118	69.58446948896426	45.55777972688312	25.285908169639914	45.85936357683856	67.11918342027383	29.58698802570689	55.112951606693905	94.72462199697821	43.80633334520038	46.95869202690863	53.72540184481863	40.42535228286331	24.731748333781006	60.07884846946387	42.31210936692708	30.02976159337093	59.90132602198951

I'm ignoring the other columns right now and just testing the first two for the "transcriptomic" gradient coloring.

Sorry - my bad! Seems I answered my own question in responding above with the input file snippet (and reading more that 400 error means the wrong syntax was used in the API)...our MicrobiomeHelper MGS pipeline adds the "EC:" part to the beginning of the EC# column and that was messing things up, since you require just the straight numbers alone in that column. Once I removed those, it ran to completion...you can close this issue!

Hey there! Nice you found out the problem, KEGGCharter does need better sanitization of these columns that require a very specific format...
I'll have to implement some regex to better inform on the incorrect formats, next versions will bring this.

authors: amcomeau iquasere

repo: iquasere/KEGGCharter


text:
ZSH _complet_goto_aliasas autocomplete error

OSX 10.11
bash --version
GNU bash, version 4.4.19(1)-release (x86_64-apple-darwin15.6.0)
zsh --version
zsh 5.0.8 (x86_64-apple-darwin15.0)
When using bash, works great. When using ZSH, however, it returns the error. I can register and list entries, and can manually type the whole registered alias. When tab completing registered aliases, it returns the following error:
~  goto -l
git /Users/'username'/GIT
~ goto _complete_goto_aliases:local:4: not valid in this context: git /Users/'username'/GIT)
_complete_goto_aliases:local:4: not valid in this context: git /Users/'username'/GIT)
_complete_goto_aliases:local:4: not valid in this context: git /Users/'username'/GIT)
goto
I know that ZSH substitution is different than bash, but haven't been able to pin down exactly what part of the _complete_goto_aliases function is not substituting correctly
Great tool!

Thanks for reporting! I will also add an item to test in zsh also in the TODO section of the README file.

FYI - had to enable bash completion script compatibility mode to handle the 'compete' command for me.
autoload bashcompinit
bashcompinit

Having a similar issue with tab completion in ZSH with partial completions
zsh 5.0.2 (x86_64-pc-linux-gnu)
goto d
_complete_goto_aliases:13: bad substitution
Agree -- very helpful!

@caanaan Thank you! I will try to fix that even though I'm not that familiar with zsh :crossed_fingers:

trying to autocomplete a wrong word using zsh version 5.4.2 (x86_64-pc-linux-gnu)

From a quick look at zsh, I get the feeling that the script has to be re-written for zsh in its own file since the completion mechanism is very different from Bash's. git does the same for its completion scripts.
It won't happen soon, at least by me cause I have to familiarize myself with zsh first.
Adding the help wanted label.

Completion now is supported!
@jshort Just checked the functionality on zsh and it's great :+1: :+1: :+1:

repo: iridakos/goto


text:
Reorganize source files and header files

We should move header files to an include/ directory.
ipam_client might need to be removed or separated.
pam_interactive.cpp should probably be main.cpp.

Also need to look into separating pam_handshake_auth_check executable. This is being used by the server-side plugin, but it may behoove us to make its own CMakeLists file for clarity and separation of concerns.

If any further reorganization is needed post-#21, please open a new issue.

authors: SwooshyCueb alanking


text:
package-info.javaのJavadocコメントをパッケージ図に表示する

#14 のあと。
取れさえすればFQNと一緒に JapaneseNameRepository に突っ込むだけでいける。

ba8f23751781eeeeaa0f52e1615b639be527ec8f でできた。

repo: irof/Jig


text:
Small & simple settings page for the extension

No react here, keep the bundle to a minimum
just a simple webpage where users can configure settings for the extension side:

websockets server (by default: http://localhost:9002)
log level (by default info)

Implemented in #94

repo: iron-wallet/iron


text:
Changelog?

Is there a changelog in this repo? There is no version tag so it is very difficult to compare changes between different versions.

Will definitely start a changelog.
As for tags, for some reason I see that they stopped after 3.0.0
I pushed the most recent tag (5.1.2) and will try to make sure this doesn't happen again in the future

repo: ironSource/node-regedit


text:
add snappy compression

I'm trying to compress the parquet file after  its creation, but AWS Athena can't read it.
`HIVE_CANNOT_OPEN_SPLIT: Error opening Hive split s3://bucket-example/data/parquet_node/year=2018/month=04/day=18/hour=18/minute=47/file.snappy.parquet (offset=0, length=11716266): can not read class parquet.format.FileMetaData: don't know what type: 15`

This query ran against the "tes" database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query Id: 3b3a2df1-b202.

is it possible to add an optional snappy compression in the writer?

i've read the integration tests, and i got the key, i have to add an optional option 'compress' ('SNAPPY') in the schema.
close it please, thanks!

Could you give more details about how this can be done. I don't find any documentation for this.

@anilsdas it looks like you can add compression: 'SNAPPY' to each schema type definition.

authors: anilsdas fzaffarana t3h2mas

repo: ironSource/parquetjs


text:
Make archive text configurable

I am suffering from this atom issue: https://github.com/atom/atom/issues/6435, https://github.com/atom/atom/issues/6214
I have already managed to find fonts which are able to display the ☐, ✔, ✘ characters. Since you can redefine these symbols (e.g. [ ], [x], [-]) in the settings, it is not a big deal to make atom-tasks work; even if there is no proper font available.
It would be nice if the archive text is configurable as well: https://github.com/irrationalistic/atom-tasks/blob/master/lib/tasks.coffee#L320-L326
It is quite annoying in atom on linux:

Or maybe just use
"""
----------------------------
Archive:
"""

I've added a setting to the package so you can control this to be whatever you want!
If you want to replace the existing one, you have to delete it first, then re-archive since it won't replace existing archive sections.

Nice! Thank you very much!

authors: irrationalistic rumpelsepp

repo: irrationalistic/atom-tasks


text:
refactor: Add localeExtension config option and clean up config procedure

General cleanup of the config creation procedure.
Fixes #257, #294, and #297.

@capellini Mind reviewing? Note that I had less than a half hour free this evening so haven't had a chance to write tests for the new config option. Appreciate any help you can offer. Thanks!


text:
childrenIgnored wrong return?

https://github.com/isaacs/node-glob/blob/ed22c06c060a89f02b30d996c0eec032b1781962/src/ignore.ts#L109-L111
Maybe I misunderstanding the purpose here, shouldn't this block return true rather single true?

I run into a problem that the ignore option didn't ignore a infinite symlink directory and iterate its infinite files, I think the problem is this code doesn't work expected.

Omg, yes, that is obviously a bug, good spot.
What's funny is that it actually still works, assuming the path isn't an ELOOP, just way slower because it iterates over every file.

authors: isaacs pilaoda

repo: isaacs/node-glob

license: isc


text:
Installing packages locally almost always fails with this error.

Does this with almost all local installs. Sometimes sudo works. Global installs tend to work. --save switch is also seems to be ignored. Can shared folder be the cause somehow? (Ubuntu is guest in VM. Does this since install.)
wizek@wizek-VB-Ubuntu:~/Work_Area/Code/Tali$ npm install doc.md --save
npm ERR! error installing doc.md@0.0.3 Error: ENOENT, No such file or directory '/media/sf_Work_Area/Code/Tali/node_modules/doc.md/index.js'
npm ERR! error rolling back doc.md@0.0.3 Error: ENOTEMPTY, Directory not empty '/media/sf_Work_Area/Code/Tali/node_modules/doc.md'
npm ERR! Error: ENOENT, No such file or directory '/media/sf_Work_Area/Code/Tali/node_modules/doc.md/index.js'
npm ERR! Report this *entire* log at:
npm ERR!
npm ERR! or email it to:
npm ERR!
npm ERR!
npm ERR! System Linux 2.6.38-10-generic
npm ERR! command "node" "/usr/local/bin/npm" "install" "doc.md" "--save"
npm ERR! cwd /media/sf_Work_Area/Code/Tali
npm ERR! node -v v0.4.9
npm ERR! npm -v 1.0.24
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /media/sf_Work_Area/Code/Tali/npm-debug.log
npm not ok
wizek@wizek-VB-Ubuntu:~/Work_Area/Code/Tali$

Just wanted to add that I have this same issue trying to use a VirtualBox folder share (host Windows 7, vm Ubuntu Server 11, vb 4.1.6)

Does this help: http://en.wikipedia.org/wiki/NTFS_symbolic_link ? (showing that after all win (or ntfs to be more precise) does support symlinks)

@Wizek The question is not "can windows do symbolic links in any fashion whatsoever".  The question is, "does a virtualbox or vmware unix filesystem mounted on top of NTFS present the same symlink interface as unix."
And the answer, unfortunately, is a resounding No.
This is especially confusing to the tar program that is included in most Unix operating systems.  (Typically, either bsdtar, gnutar, star, or solaris posix tar.)  The npm alpha version shipping with node 0.6.5 is a bit more resilient, so you could try using that, but it'll probably still fail to create symbolic links normally on filesystems mounted on top of NTFS.

authors: Wizek isaacs stephenr85

repo: isaacs/npm


text:
C++ Syntax Misunderstands Nested Parens in String Constructor

Consider the following C++ program
void main() {
  std::string foo(bar()->baz());
}

HLJS will incorrectly mark the (bar() as the parameters to the string constructor, resulting in inconsistently highlighted parens.
std
::

  string
  foo
  (bar()
  ->
  baz
  ())
;

I think I see a related problem. The following fails to highlight at all for me:
Buffer myBuffer(getBuffer());

For me I think it is related to the )). If I replace by a single ) it hightlights correctly.

Can you confirm this is still and issue and perhaps provide a jsfiddle?
You can use my template:
https://jsfiddle.net/ajoshguy/nagkqytv/18/

I can no longer repro: https://jsfiddle.net/jmpgx6hc/
Thanks!

I also verify that it has been fixed: https://jsfiddle.net/goodbyte/jhv3L7do/ thanks!

authors: erikman wyattallen yyyc514


text:
Sample object type hierarchy broken on expand

It looks like the sample object type hierarchy view filter is broken when you click it.  This is 100% reproducible.  Investigating.

Pushed to iSamples Central and closed.