Angular 13: Unable to build Cannot find namespace 'TopoJSON'

When trying to build a project with ng serve I get the following errors
Error: node_modules/@unovis/angular/dist/lib/components/topojson-map/topojson-map.component.d.ts:56:16 - error TS2503: Cannot find namespace 'TopoJSON'.

56     topojson?: TopoJSON.Topology;
                  ~~~~~~~~

Error: node_modules/@unovis/ts/components/topojson-map/config.d.ts:9:16 - error TS2503: Cannot find namespace 'TopoJSON'.

9     topojson?: TopoJSON.Topology;
                 ~~~~~~~~

I've added TopoJSON to my package.json but the issue persists. I've added the following packages:
"@types/topojson-specification": "^1.0.2",
"topojson": "^3.0.2",
"topojson-client": "^3.1.0",

However, updating the types in the files to Any fixes the issue. Or just importing TopoJSON into the file explicitly.
Is there something I'm missing in setting up the package? I figure that my tsconfig setup can also be the issue but just wanted to check if you guys have seen this before

Had one more error that was fixed by adding @types/lodash
Error: node_modules/@unovis/ts/core/component/index.d.ts:1:23 - error TS2688: Cannot find type definition file for 'lodash'.

1 /// <reference types="lodash" />
                        ~~~~~~

@AhmedHalat Thanks for reporting!
Yes, we had issues with TopoJSON typings before but I thought we've solved those. I've found a few issues in the package.json file of @unovis/ts. Can you please try installing version 1.0.1-beta.0:
npm i -P<EMAIL_ADDRESS>--force

And post whether it helped or not?

@rokotyan Issue persists on 1.0.1-beta.0. No changes

@AhmedHalat Ok, I'll need to look deeper into the issue. I'll keep you posted!

@AhmedHalat I've tried to set up a new Angular app with ng new and was able to catch and fix a bunch of types-related errors. However, the TopoJSON error was not there. So if you could share your tsconfig, that might be helpful.
In the meantime, can you please also try changing @unovis/ts and @unovis/angular versions to 1.0.1-beta.5 in your package.json, then remove node_modules, and  run npm install.
npm i -P<EMAIL_ADDRESS><EMAIL_ADDRESS>rm -rf node_modules
npm i

Hello,
Just to say that i followed the steps you suggested wrt 1.0.1-beta.5 and i still got the error with TopoJSON for which i applied the fix @AhmedHalat mentioned (the import). I also got some other errors regarding export = and i fixed these by adding
"esModuleInterop": true,
"allowSyntheticDefaultImports": true

to config.json (as suggested at https://stackoverflow.com/questions/60935889/cant-do-a-default-import-in-angular-9).
With these, the basic app i wanted to try (basic-line-chart) now works.

Odd. Updating my tsconfig as @astefano and the new doc update @rokotyan made suggested, but it doesn't seem to fix it for me. I guess one of my other tsconfig settings might be causing the issue here?
Can we compare other versions or our tsconfig? node v16.17.0
Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1301.4
@angular-devkit/build-angular   13.1.4
@angular-devkit/core            13.1.4
@angular-devkit/schematics      13.1.4
@angular/cdk                    13.1.1
@angular/cli                    13.1.4
@angular/material               13.1.1
@schematics/angular             13.1.4
rxjs                            6.6.7
typescript                      4.5.5

@AhmedHalat I've tried to create a new Angular app again with ng new on another machine, and the only change to tsconfig I needed to do to make it work was enabling allowSyntheticDefaultImports.
Here's how that tsconfig.json looks:
{
  "compileOnSave": false,
  "compilerOptions": {
    "allowSyntheticDefaultImports": true,
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    "forceConsistentCasingInFileNames": true,
    "strict": true,
    "noImplicitOverride": true,
    "noPropertyAccessFromIndexSignature": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,
    "sourceMap": true,
    "declaration": false,
    "downlevelIteration": true,
    "experimentalDecorators": true,
    "moduleResolution": "node",
    "importHelpers": true,
    "target": "ES2022",
    "module": "ES2022",
    "useDefineForClassFields": false,
    "lib": [
      "ES2022",
      "dom"
    ]
  },
  "angularCompilerOptions": {
    "enableI18nLegacyMessageIdFormat": false,
    "strictInjectionParameters": true,
    "strictInputAccessModifiers": true,
    "strictTemplates": true
  }
}

And package.json:
{
  "name": "unovis-angular",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "watch": "ng build --watch --configuration development",
    "test": "ng test"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^15.0.0",
    "@angular/common": "^15.0.0",
    "@angular/compiler": "^15.0.0",
    "@angular/core": "^15.0.0",
    "@angular/forms": "^15.0.0",
    "@angular/platform-browser": "^15.0.0",
    "@angular/platform-browser-dynamic": "^15.0.0",
    "@angular/router": "^15.0.0",
    "@unovis/angular": "^1.0.1-beta.5",
    "@unovis/ts": "^1.0.1-beta.5",
    "rxjs": "~7.5.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.12.0"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^15.0.4",
    "@angular/cli": "~15.0.4",
    "@angular/compiler-cli": "^15.0.0",
    "@types/jasmine": "~4.3.0",
    "jasmine-core": "~4.5.0",
    "karma": "~6.4.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.2.0",
    "karma-jasmine": "~5.1.0",
    "karma-jasmine-html-reporter": "~2.0.0",
    "typescript": "~4.8.2"
  }
}

My node version is 16.15.0.
@AhmedHalat Can you please share your tsconfig too?

@rokotyan Finally managed to get it working. None of my tsconfig.json settings seemed to fix it (including adding allowSyntheticDefaultImports), but the following did.
I added "@types/topojson-client" to my dev dependencies and to my types in compilerOptions in tsconfig.app.json
"compilerOptions": {
    "types": ["node", "...", "topojson-client"]

I also got off the beta and I'm still no longer getting the Namespace issue.
Thanks a lot for all your help!

If you still want my tsconfig, here it is:
{
  "compileOnSave": false,
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    "forceConsistentCasingInFileNames": true,
    "strict": false,
    "noImplicitReturns": true,
    "preserveSymlinks": true,
    "noFallthroughCasesInSwitch": true,
    "sourceMap": true,
    "declaration": false,
    "downlevelIteration": true,
    "experimentalDecorators": true,
    "moduleResolution": "node",
    "importHelpers": true,
    "target": "es2017",
    "module": "es2020",
    "typeRoots": ["node_modules/@types"],
    "lib": ["es2019", "dom"],
    "resolveJsonModule": true,
    "esModuleInterop": true
  },
  "angularCompilerOptions": {
    "enableI18nLegacyMessageIdFormat": false,
    "strictInjectionParameters": true,
    "strictInputAccessModifiers": true,
    "strictTemplates": false,
    "fullTemplateTypeCheck": true
  }
}

@AhmedHalat Great and thanks for writing about your fix!
When you explicitly set types in your tsconfig, only those types will be visible to the compiler. That's why you had to add "topojson-client" there explicitly. Here is an excerpt from TSConfig docs:

By default all visible ”@types” packages are included in your compilation. ...
...
If types is specified, only packages listed will be included in the global scope.

We'll add a few words about it to our docs too.


Unable to disable Dialogs/Triggers

This could be viewed as a complication caused by this issue as "overriding" dialogs/triggers can cause problems however I still think it's reasonable as part of a developer/user workflow to want to disable/deactivate a certain dialog/trigger to aid with testing.
For example you may wish to disable a dialog/trigger to test a scenario (unhandled intent) or disable functionality going into a specific test envrionment.
Right now you have to delete an entire dialog/trigger and then re-create it :-(
Describe the solution you'd like

An enabled/disable flag on a dialog/trigger

Being addressed in https://github.com/microsoft/BotFramework-Composer/issues/1695

@DesignPolice - please work with Sang on visual representation of the various types of nodes (including end-node, comment flag etc) as well as the look and feel of the nodes that are affected.


Fix release

Description
The wheel file is not building for windows on GitHub Actions (https://github.com/pybamm-team/PyBaMM/runs/5023662038?check_suite_focus=true). The error -
    [DEBUG] Downloading https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-gcc-fortran-10.2.0-1-any.pkg.tar.zst
    [DEBUG] Download failed -- retrying after 1000 ms.
    [DEBUG] Download failed -- retrying after 2000 ms.
    [DEBUG] Download failed -- retrying after 4000 ms.
    [DEBUG] Downloading https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-gcc-fortran-10.2.0-1-any.pkg.tar.zst
    [DEBUG] Download failed -- retrying after 1000 ms.
    [DEBUG] Download failed -- retrying after 2000 ms.
    [DEBUG] Download failed -- retrying after 4000 ms.
    [DEBUG] Downloading https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-gcc-fortran-10.2.0-1-any.pkg.tar.zst
    Error: Failed to download from mirror set:

The failing links are not active anymore, they have been moved somewhere else. Note how https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-gcc-fortran-10.2.0-1-any.pkg.tar.zst does not work but https://mirrors.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-gcc-fortran-10.2.0-1-any.pkg.tar.zst does (mirror -> mirrors).
I found a similar issue on GitHub that says this was fixed a couple of weeks back - https://github.com/microsoft/vcpkg/issues/22594
I tried updating the commit hash (baseline) of default vcpkg repository in vcpkg-configuration.json which gave me an error -
    running build_ext
    -- Building for: Visual Studio 16 2019
    -- Running vcpkg install
    Fetching registry information from https://github.com/pybamm-team/sundials-vcpkg-registry.git (HEAD)...
    Error: while checking out baseline from commit '2b543e52da6a7a595760f10c1160e808d89c41ed' at subpath 'versions/baseline.json':
    fatal: path 'versions/baseline.json' exists on disk, but not in '2b543e52da6a7a595760f10c1160e808d89c41ed'

    This may be fixed by updating vcpkg to the latest master via `git pull` or fetching commits via `git fetch`.

    You can use the current commit as a baseline, which is:
        "builtin-baseline": "df40d1c476dc02d71b113e4a63c3a32b00ebb5bd"
    -- Running vcpkg install - failed

This comment - https://github.com/microsoft/vcpkg/issues/18533#issuecomment-871865858 - says that we should update vcpkg by pulling in the latest code.
I tried removing the old vcpkg files and replaced them with the cloned GitHub repository, and it worked! The PR is a bit messy because of all the debugging, I will clean it up.
The passing workflow - https://github.com/Saransh-cpp/PyBaMM/runs/5033220394?check_suite_focus=true
Fixes # (issue)
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ flake8
[ ] All tests pass: $ python run-tests.py --unit
[ ] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

@Saransh-cpp If you keep the basline as "baseline": "" then it will always use the latest commit id

@Saransh-cpp If you keep the baseline as "baseline": "" then it will always use the latest commit id

Oh oh, yes we should do that. Thanks!

Could you also update the release checklist

Might as well try removing the baseline field completely?

I think we can keep it and say something like -

If building wheels on Windows gives a vcpkg related error - revert the baseline of default-registry to a stable commit in vcpkg-configuration.json

in the release checklist. Just in case the latest commit breaks down something?

Could you rebase commits

Could you rebase commits

Why is rebase required? I usually pull in the upstream branch which performs the merge automatically. I pulled main and it shows up to date, should I rebase this branch with main? (Or do you mean something else by rebase? Honestly, I have never used it.)

By rebasing I meant combining all the commits into one or two commits.

@tinosulzer let’s merge this

We should also make a PR from main to develop to avoid merge conflicts


Support old multisend contract

What is needed?
Decoding old multisend transactions
Background
Some multisend transactions were done using the old multisend contract and we would like to be able to decode them.
Legacy Multisend: https://etherscan.io/address/0xe74d6af1670fb6560dd61ee29eb57c7bc027ce4e#code

Old multisend transactions are already decoded, as an example you can check https://safe-transaction.rinkeby.gnosis.io/api/v1/transactions/0x6c175bd341f32100666ca25af3b04104eb599b5a3e21efc28bcb88e40129f609/

Old multisend transactions are already decoded, as an example you can check https://safe-transaction.rinkeby.gnosis.io/api/v1/transactions/0x6c175bd341f32100666ca25af3b04104eb599b5a3e21efc28bcb88e40129f609/


Setup custom pipelines and SAAS configuration for registry viewer

Which area is this issue related to?

/area ci
/area registry-viewer
Issue Description

As with #1636, we'll need to setup the SAAS configuration to use the registry viewer release image built and published by Konflux.
Acceptance Criteria

[X] Change the OpenShift template to separate the image tag used for registry-viewer image
[x] Add next tag under ADDITIONAL_TAGS, see example.
[x] Verify image is under redhat-services-prod before making changes to SAAS.
[x] Update your service to use the new image. This is usually done by updating REGISTRY_VIEWER_IMAGE OpenShift template parameter in a saas file. Add the new image to the imagePatterns list as well.

/status blocked
Unable to proceed until testing passes for open PR: https://github.com/devfile/registry/pull/529

/remove status/blocked
Ran testing locally to confirm changes in https://github.com/devfile/registry/pull/529 were not causing failures, with this confirmed the PR was merged via bypassing the protection and is no longer blocking this issue.

/remove-status blocked

/unblocked

SAAS deployments are now using both devfile-index and registry-viewer release images from Konflux, closing this issue.

Set story points to 2 days as time took to complete.


MinDate Previous Month Dates Activated

In my implementation I have two calendars and I use them in a date range format.
I have assigned an onChange event and set the minDate and maxDate properties of the corresponding calendar.
When I set the minDate of the calendar current months dates are disabled successfully but the previous months dates are enabled automatically.
This is my JS Script:
var dateAfter = $('#dateAfterRespTable'),
    dateBefore = $('#dateBeforeRespTable');

if(dateAfter.length && dateBefore.length)
{
    var dateFrom = dateAfter.flatpickr({
        dateFormat  : 'd/m/Y',
    }),
    dateTo = dateBefore.flatpickr({
        dateFormat : 'd/m/Y',
    });

    dateFrom.config.onChange = function (dateObj) {
        dateTo.set('minDate', dateObj[0]);
    };

    dateTo.config.onChange = function (dateObj) {
        dateFrom.set('maxDate', dateObj[0]);
    };
}

Hello,
I couldn't replicate the issue in the latest version.
Please see if its still relevant.
Thank you :+1:


[client] draft specification for the client

Motivation
We need a specification on how to implement a proper client.
This is important as developers will want to implement their own clients, and trying to replicate at our client code without much experience in rust is prone to errors.
Furthermore, auditing our own code is hard without a higher-level specification that defines each validation that we must apply on responses from validators.
While this draft is largely incomplete, this PR's goal is to encourage third-parties to contribute to it.

Should we make a new specifications folder and then have a folder under that called drafts?

This is awesome and we need more, well written, specs like this. I think we should play around with the format a bit and try to figure out some way that things won't fall out of date once we commit this.

@davidiw we talked earlier and I said that this should probably not be pushed before we have a more complete spec. But I think a good compromise could be to have this in a specification_drafts/ folder.

@bmwill  there's some trailing whitespace error, which shouldn't be a thing since it is valid in markdown : o

Yuck...Maybe you can do something like:
hello\
world

which renders as:
hello
world

I actually don't use these trailing spaces, so it is fine :D

I mean I understand that's the goal but that breaks down the moment you start adding links and headers and the like.

Headers are pretty clear in markdown no?
When it comes to link, if you avoid the []() syntax, you can do:
this is a reference [1]

[1]: http://link

There are also CLI tools to render markdown: https://www.reddit.com/r/commandline/comments/3xgd2w/good_markdown_viewer_in_terminal/
Markdown is nice for anchors and what not which isn't an easy feat in non-html based RFCs.
On the flip side, there's something elegant about using visual cues rather than font size to provide organization...

oh that CLI tool is going to be very useful thanks : D
btw we talked out of band with @bmwill and outcome was that I would just remove the trailing spaces since I actually don't make use of them (and I don't think it matters much) but I was being pedantic (it is valid markdown after all :D)


Update with atribute force not working

I'm trying force an update state with a same value, but not working see this example below:
class LoginController
    extends NotifierStore<Exception, String>
    implements ILoginController {
  LoginController() : super("");

  set email(String v) => update(v); // My view settled this state to<EMAIL_ADDRESS>
  @override
  get isValidEmail => Validator.email(state);

  //Here the controller check if email exists on my server,
 // I dont change state, But I want forcing the view update with same state<EMAIL_ADDRESS>  Future<void> checkServerEmail() async {
    setLoading(true);
    await Future.delayed(Duration(seconds: 1));
    var newState = state; // Same state before settled by view
    update(newState, force: true);
    setLoading(false);
  }

}

The ValueNotifier work with DISTINCT in your reactivite natively, so some things are impossible to force.
Use StreamStore instead of NotifierStore to resolve this issue.
Upgrade to a new version to help with this :)


GM1000 and/or GM3000 Modbus Map?

Hello. I was wondering if you had some information about the modbus maps used in the meters GM1000 or GM3000 (which in turn are the same as HK1000 and HK3000 I suppose).
Thanks!

Nope, unfortunately, such info is not publicly available or known to me.


Added question around attempting to reconcile failed cluster

Pull request guidance
as per work item:
https://supportability.visualstudio.com/AzureContainers/_workitems/edit/42016?src=WorkItemMention&src-action=artifact_link
Thank you for your contribution. The content team is monitoring the pull requests. Once your pull request is ready for review, please add a comment such as "PR is ready for review".

PR is ready for review

@jotavar per CPM and SME's triage, they are going to change the scope of the request to update another existing article. CPM suggested we decline this PR to update the FAQ, and he will create a new one for adding this cause/resolution to another article, as it might be confusing to re-scope this request.


Tox is incompatible with projects using flit.ini

This might duplicate #74, but there is a lot of information there, so I thought I'd express this issue here.
tox depends upon a setup.py file to manage. We can avoid processing setup.py, but this negates the purpose of the tool -- to install the software from within a container.
$ cat tox.ini
[testenv]
deps = pytest
commands = py.test --verbose {toxinidir}/tests

$ tox
Traceback (most recent call last):
  File "/usr/local/bin/tox", line 9, in <module>
    load_entry_point('tox==2.3.1', 'console_scripts', 'tox')()
  File "/Library/Python/2.7/site-packages/tox-2.3.1-py2.7.egg/tox/session.py", line 39, in main
    retcode = Session(config).runcommand()
  File "/Library/Python/2.7/site-packages/tox-2.3.1-py2.7.egg/tox/session.py", line 375, in runcommand
    return self.subcommand_test()
  File "/Library/Python/2.7/site-packages/tox-2.3.1-py2.7.egg/tox/session.py", line 520, in subcommand_test
    path = self.get_installpkg_path()
  File "/Library/Python/2.7/site-packages/tox-2.3.1-py2.7.egg/tox/session.py", line 496, in get_installpkg_path
    path = self._makesdist()
  File "/Library/Python/2.7/site-packages/tox-2.3.1-py2.7.egg/tox/session.py", line 390, in _makesdist
    raise tox.exception.MissingFile(setup)
tox.MissingFile: MissingFile: /Users/jquast/Code/ptyprocess/setup.py

We can modify tox.ini to ignore using setup.py,
[tox]
skipsdist=true

[testenv]
deps=pytest
commands = py.test --verbose {toxinidir}/tests

But not we're only creating a virtualenv to contain py.test and nothing more.  We are using tests from, and testing against the source folder.  We aim to test the installed version of our software to verify correct packaging (especially file inclusions/exclusions).
Try 3, to explicitly install dependency flit so that we can install our package for testing:
[tox]
skipsdist=true

[testenv]
deps=pytest
     flit
commands = flit
           flit -f {toxinidir}/flit.ini install
           py.test --verbose {toxinidir}/tests

This fails because flit is only made available as a python 3 wheel and without source distribution, so it fails to install for python2.7 testing. I'm not sure where to go from here.

Dealing with the ptyprocess specific question over there, answering more generally for flit here:
By and large, I prefer to test pure Python code from the source directory rather than installing it. Flit facilitates this by eliminating the biggest source of differences between the source and installation - package_data and MANIFEST.in. The installed package should be exactly the same as the source package, just at a different path in the filesystem.
If you do need to install the package, the intention for the next version of flit (see #72) is that flit should be installed outside your testing virtualenv, and be pointed to install the package inside it. The idea there is that flit is more a command line tool that happens to be implemented in Python, not something you should need to install in your testing environment. As you found, flit itself cannot be installed with Python 2, although there is a minimal installer shim that can be used in a pinch.
#74 summarises the various options for integrating with systems that expect sdists or setup.py files. I am hopeful that we can hash out a new source tree standard that doesn't rely on setup.py files - see pypa/interoperability-peps#54.

Thanks, I appreciate the explanation.
If you could envision a world where tox and flint get along, could this be a code change to tox conditionally support flit, say a "useflit=true" sort of option for tox.ini, this would change the default setup.py-based sdist packaging to use flit instead via the command-line interface?

I think the answer, given https://github.com/rbtcollins/interoperability-peps/blob/build-system-abstraction/build-system-abstraction.rst is "yes". Anyway, great work

Thanks! Yes, I think it would be technically possible to teach tox about flit specifically, but I'd prefer to try to push through that build system abstraction proposal, and then teach tox about the new standard for source distributions.

FYI, you can define skip_install = true in tox.ini (section testenv) and do what you want in the commands settings to install the package if you want to.


Use Cloudflare Access in front of Uptime Kuma

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
I'd like to use Cloudflare Access in front of Uptime Kuma. I have disabled authentication as indicated.

I would like to authorize access to uptime kuma only to certain users but allow anyone to access the status pages.
So I created 2 applications on the Zero Trust dashboard. One to authorize only certain users to access all paths and another to authorize all users to access the "/status" and "/api" paths.

📝 Error Message(s) or Log
But if I go as a normal user to the page "www.example.com/status/statusPage" an error appears

Maybe I should do something different?
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
Debian Bullseye
🌐 Browser
Google Chrome 121.0.6167.184
🖥 Deployment Environment

Runtime: Docker 24.0.7

So something has returned you an html site instead of a js site.
Have you looked at what the content of said html site was?
You handled two of the routes. How are the other routes handled?
These are the routes that are called for a sample stauts page (excluding index+api)

[!WARNING]
Note that other routes like the /metrics may leak information if you disabled auth.
=> Keep these protected

[!CAUTION]
Note that allowing /api for anybody might have security impliations if https://github.com/louislam/uptime-kuma/pull/3854 gets done in v2.1

=> I would recomend to use a custom domain name for your status page instead. See https://github.com/louislam/uptime-kuma/wiki/Status-Page#domain-names-for-status-pages

Ok thanks, so I use a custom domain for my status page that I authorize to everyone and I have another main url where I only authorize certain people. The problem is that I just have to go to the url I authorize, add "/dashboard" and the page is accessed because authentication is disabled.

I don't quite get what you are refering to and where the problem lies.

any requests to the main url (uptime.example.de) => under cloudflare auth => need to authorise via cloudflare
any requests to the status url (status.example.de) => NOT under cloudflare auth => need NOT authorise via cloudflare

What exactly is working how?
As far as I understand your statement, you

go to uptime.example.de
authorise in cloudflare
are now authorised and can access /dashboard

The problem is that if I go to status.example.de which is not under cloudflare auth everyone can access /dashboard

I had the same issue but the below works.
the tunnel

Applications

My allow policy, but nothing special as it allows everyone to the Status page.

This allows you access to the Status page

But not to /list or /dashboard or other endpoints found here as far as I tested;

https://raw.githubusercontent.com/louislam/uptime-kuma/master/src/router.js
hope this help.


Readme: fix example with --font instead of --font-file

The option is --font:  https://github.com/chjj/ttystudio/blob/master/lib/options.js#L72
Was it not working for some reason?

Oh, I see. There is an error in the readme args and the man page, but you might have changed the wrong part. :)

Ah, okay. :)


⚠ Bofrost.lu has degraded performance

In ff60c8a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1105 ms

Resolved: Bofrost.lu performance has improved in 5c9bb26 after 6 minutes.


This should be only merged in if https://github.com/econ-ark/HARK/pull/797 is merged.
This action ensures the code that is merged into master always follows the black style guidelines, even if the contributor hasn't installed it locally.


feat/subscription client

I'm taking over @codeflyer PR https://github.com/mercurius-js/mercurius-subscription-client/pull/1
Linked to https://github.com/mercurius-js/mercurius/issues/929
resolves: https://github.com/mercurius-js/mercurius-subscription-client/issues/2

I was thinking abount implementing the event ready so it is possibile to await once(client,ready) to send the subscription. @mcollina  what do you think?

@mcollina can I get some privileges on this repo and https://github.com/mercurius-js/mercurius-gateway please? Ideally the same I have on the main repo so we're somewhat independent in shipping these, triggering workflows etc

You should be set up

I've tried to integrate this client with a mercurius server and for some reason the server never sends the response to the subscription request.
I've also tried with another client graphql-ws and had the same result.
The test is visible in the file test/subscription-client.js mercurius integration. I'm not sure what causes this behaviour


indicating progress of async exports

It was defined that /allelematrix-search/status/{extractId} would respond something like
{ "metadata": { "pagination": { "pageSize": 0, "currentPage": 0, "totalCount": 0, "totalPages": 0 }, "status": [{"code" : "asynchstatus" , "message" : "FINISHED"}], "datafiles": ["/shared_files/app_test/file_bundle/crops/rice/extract/output/721"] }, "result" : { "data": [] } }
I would like to suggest adding an optional asynchprogress key to the status object, in order to provide means for implementations to supply some info, as a string, about the progress of the export process.

#146


Modify code for uploading country data files

I'd love help modifying the code to so we can point it to country-specific data files. You had suggested modifying the contact_matrix_dic() function so we can input a file path instead of a sheet name.
https://github.com/InstituteforDiseaseModeling/synthpops/blob/master/synthpops/contact_networks.py#L1019
Also, it would be great to get your input on how to best implement these changes without creating a new branch or fork.

@skroiss-idm  apologies for the super late reply on this - getting pretty swamped with issues and other modeling that needed to be done for Seattle area questions. I'm getting dev support now so we should be able to move more quickly on supporting the Pakistan work (it's one of the priorities). Can you share the provincial household matrix files with me so I can test out a solution for this? Let me know. Thanks!

That's great news Dina! I'll send you a DB invite to the folder where we're working on compiling those files. We're having trouble finding province level estimates for several things (school enrollment, school size, work place size, etc.) and are discussing options.

Ahh okay - good to know. I think school enrollment might be found only at the national scale. And school sizes might be hard. We should figure out what reasonable estimates could be. Workplace sizes might be found looking for firm sizes? I know it might be hard.

Closing for now, can reopen if needed


Added ability to have default application securitygroup rules

Works with an addition like -
[base]
default_securitygroup_rules = { "bastion" : [ { "start_port": "22", "end_port": "22", "protocol": "tcp" } ],
          "eureka" : [ { "start_port": "8080", "end_port": "8080", "protocol": "tcp" } ] }

to foremast.cfg

I don't see the example configs include this new DEFAULT_SECURITYGROUP_RULES option. Did I miss it or did we not want to include it?

Rebased and resolved conflicts.

Looks better. Clear for merge.


Add: TCSM.pt

Channel Name
TCSM
Native Name (optional)
No response
Network (optional)
No response
Country
PT
Subdivision (optional)
No response
City (optional)
No response
Broadcast Area
c/PT
Languages
pt
Categories (optional)
general
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://tcsm.cv
Logo
https://tcsm.cv/wp-content/uploads/2022/09/logotipo-tcsm-tv300.jpg
Notes
No response

https://github.com/iptv-org/iptv/pull/9015

Already in the database: https://iptv-org.github.io/?q=TCSM

when the https://github.com/iptv-org/iptv/issues/8952 will be completed?
Il giorno sab 24 set 2022 alle ore 18:50 Aleksandr Statciuk <
@.***> ha scritto:

Closed #492 https://github.com/iptv-org/database/issues/492 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/iptv-org/database/issues/492#event-7452519284, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALKITV6GO5FHWDT4OE5JE6TV75LRBANCNFSM6AAAAAAQUYW36A
.
You are receiving this because you authored the thread.Message ID:
@.***>

if the https://github.com/iptv-org/iptv/pull/9022 are accepted, the channel should appear in the playlist tomorrow.

thank you dear!
Il giorno sab 24 set 2022 alle ore 18:59 Aleksandr Statciuk <
@.***> ha scritto:

if the iptv-org/iptv#9022 https://github.com/iptv-org/iptv/pull/9022
are accepted, the channel should appear in the playlist tomorrow.
—
Reply to this email directly, view it on GitHub
https://github.com/iptv-org/database/issues/492#issuecomment-1257055213,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALKITVZS4HCHZDGXPOYUNGTV75MTLANCNFSM6AAAAAAQUYW36A
.
You are receiving this because you authored the thread.Message ID:
@.***>


Avast! antivirus claims Dreditor is a risky browser plugin

Avast! on my Windows machine today alerted me that there are three dangerous browser plugins on my system. One of their claims was dreditor.
This was the first time I've seen Avast warning about browser plugins so I suspect it is a new feature they have added.
Just wanted to let you know this is happening.

Dreditor is being decommissioned due to the lack of availability of current maintainers and the fact that Drupal.org is becoming more feature rich at a much faster rate than Dreditor itself now.
This decision was also partially made due to the amount of work (complete rewrite) it would take to create an "official" Firefox extension (#256).
If you already have the extension installed, it should continue working for a while until, inevitably,  the markup on Drupal.org changes. It will no longer be updated.
We understand that many of you love this extension, as do we. This isn't the end, in fact, it's a much brighter beginning. All the things we love about Dreditor can, and should, be moved into Drupal.org natively.
For more information, please follow: https://www.drupal.org/node/2779729

This issue was moved to dreditor/dreditor#14


NextJS Build Error

Failed to compile.

./components/FirstComponent.tsx
Module not found: Can't resolve 'classy-ui/normalize.css' in '/Users/devchris/Documents/code/nodejs/project/packages/next/components'

I follow the new updated documentation :/

Hi @yovanoc,
We have made a new release now, could you try again please? 😄 Thanks for trying out the beta!

Yay! It works! But without going further, the Head thing have to be in every pages so?

@yovanoc Oh, yeah... I believe we can change the docs to take advantage of the _app file, get back to you on this 😄

Thanks a lot! because i've spent a lot of time trying to make a boilerplate for nextjs with overmind and classy-ui :(

Hi there!
So updated docs now :) https://classy-ui.io/install/next-js


Raspberry Pi 4: 'linux-armv7' binaries cannot be used on the 'linux-armv6' platform

Hey Guys,
i try to use sharp within a electron application on my raspberry pi 4 with 4 GB. When i use 'require("sharp")' i get the following error:

Uncaught Error: 'linux-armv7' binaries cannot be used on the 'linux-armv6' platform. Please remove the 'node_modules/sharp' directory and run 'npm install' on the 'linux-armv6' platform.

I tried to build sharp from Source, but no success.
When i run 'npm install sharp' i get some errors:

gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Linux 4.19.118-v7l+
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pi/neu/photo-booth/node_modules/epoll
gyp ERR! node -v v12.18.2
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok

but 'npm install -g node-gyp' finished succesfull
Have you ensured the platform and version of Node.js used for npm install is the same as the platform and version of Node.js used at runtime?

How can i Check this?

Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?

Yes

If you are installing as a root or sudo user, have you tried with the npm install --unsafe-perm flag?

Yes

What is the output of running npx envinfo --binaries --system?

System:
OS: Linux 4.19 Raspbian GNU/Linux 10 (buster) 10 (buster)
CPU: (4) arm ARMv7 Processor rev 3 (v7l)
Memory: 870.39 MB / 3.81 GB
Container: Yes
Shell: 5.0.3 - /bin/bash
Binaries:
Node: 12.18.2 - /usr/local/bin/node
npm: 6.14.5 - /usr/local/bin/npm

Hi, it looks like the version of Node.js being used at runtime is for ARM v6 but the version used at install time is for ARM v7.
Please can you provide the output of running the following commands:
whereis node
node -p "process.config.variables"
npm config list | grep -i arm

Thanks for the fast Answer.
whereis node

node: /usr/sbin/node /usr/local/bin/node /usr/share/man/man8/node.8.gz

node -p "process.config.variables"

{
arm_float_abi: 'hard',
arm_fpu: 'vfpv3',
arm_thumb: 0,
arm_version: '7',
asan: 0,
build_v8_with_gn: false,
coverage: false,
dcheck_always_on: 0,
debug_nghttp2: false,
debug_node: false,
enable_lto: false,
enable_pgo_generate: false,
enable_pgo_use: false,
force_dynamic_crt: 0,
gas_version: '2.28',
host_arch: 'ia32',
icu_data_in: '../../deps/icu-small/source/data/in/icudt67l.dat',
icu_default_data: '',
icu_endianness: 'l',
icu_gyp_path: 'tools/icu/icu-generic.gyp',
icu_locales: 'en,root',
icu_path: 'deps/icu-small',
icu_small: true,
icu_ver_major: '67',
is_debug: 0,
llvm_version: '0.0',
napi_build_version: '6',
node_byteorder: 'little',
node_debug_lib: false,
node_enable_d8: false,
node_install_npm: true,
node_module_version: 72,
node_no_browser_globals: false,
node_prefix: '/',
node_release_urlbase: 'https://nodejs.org/download/release/',
node_shared: false,
node_shared_brotli: false,
node_shared_cares: false,
node_shared_http_parser: false,
node_shared_libuv: false,
node_shared_nghttp2: false,
node_shared_openssl: false,
node_shared_zlib: false,
node_tag: '',
node_target_type: 'executable',
node_use_bundled_v8: true,
node_use_dtrace: false,
node_use_etw: false,
node_use_node_code_cache: false,
node_use_node_snapshot: false,
node_use_openssl: true,
node_use_v8_platform: true,
node_with_ltcg: false,
node_without_node_options: false,
openssl_fips: '',
openssl_is_fips: false,
shlib_suffix: 'so.72',
target_arch: 'arm',
v8_enable_gdbjit: 0,
v8_enable_i18n_support: 1,
v8_enable_inspector: 1,
v8_no_strict_aliasing: 1,
v8_optimized_debug: 1,
v8_promise_internal_field_count: 1,
v8_random_seed: 0,
v8_trace_maps: 0,
v8_use_siphash: 1,
v8_use_snapshot: 1,
want_separate_host_toolset: 1
}

npm config list | grep -i arm

user-agent = "npm/6.14.5 node/v12.18.2 linux arm"

Thanks, and the following commands:
/usr/sbin/node -p "process.config.variables.arm_version"
/usr/local/bin/node -p "process.config.variables.arm_version"

/usr/sbin/node -p "process.config.variables.arm_version"

This command does nothing

/usr/local/bin/node -p "process.config.variables.arm_version"

7

Thanks, what's happening here is that /usr/local/bin/node is compiled for ARMv7 and is being used at npm install time but /usr/sbin/node is compiled for ARMv6 and is being used at run time.
You'll need to ensure /usr/local/bin/node is also used at run time.

I did not know how to You'll need to ensure /usr/local/bin/node is also used at run time. So i just deleted /usr/sbin/node and run npm install again, but nothing changed.

I I'm having the same problem. found any solution?

@SteffenLammers Deleting files from /usr/sbin is usually a bad idea. If there are two versions of node on this system, you'll need to run the one that you want using its full path e.g. /usr/local/bin/node script.js rather than relying on the OS to select one for you.

@diegodev3 If your problem is exactly the name, namely you are seeing the exact same 'linux-armv7' binaries cannot be used on the 'linux-armv6' platform error, then please provide answers to all of the questions I asked. If not, please open a new issue.

pi@raspberrypi:~ $ whereis node
node: /usr/bin/node /usr/local/bin/node /usr/include/node /usr/share/man/man1/node.1.gz
pi@raspberrypi:~ $ node -p "process.config.variables"
{
arm_float_abi: 'hard',
arm_fpu: 'vfpv3',
arm_thumb: 0,
arm_version: '7',
asan: 0,
build_v8_with_gn: false,
coverage: false,
dcheck_always_on: 0,
debug_nghttp2: false,
debug_node: false,
enable_lto: false,
enable_pgo_generate: false,
enable_pgo_use: false,
force_dynamic_crt: 0,
gas_version: '2.28',
host_arch: 'ia32',
icu_data_in: '../../deps/icu-small/source/data/in/icudt67l.dat',
icu_default_data: '',
icu_endianness: 'l',
icu_gyp_path: 'tools/icu/icu-generic.gyp',
icu_locales: 'en,root',
icu_path: 'deps/icu-small',
icu_small: true,
icu_ver_major: '67',
is_debug: 0,
llvm_version: '0.0',
napi_build_version: '6',
node_byteorder: 'little',
node_debug_lib: false,
node_enable_d8: false,
node_install_npm: true,
node_module_version: 72,
node_no_browser_globals: false,
node_prefix: '/',
node_release_urlbase: 'https://nodejs.org/download/release/',
node_shared: false,
node_shared_brotli: false,
node_shared_cares: false,
node_shared_http_parser: false,
node_shared_libuv: false,
node_shared_nghttp2: false,
node_shared_openssl: false,
node_shared_zlib: false,
node_tag: '',
node_target_type: 'executable',
node_use_bundled_v8: true,
node_use_dtrace: false,
node_use_etw: false,
node_use_node_code_cache: false,
node_use_node_snapshot: false,
node_use_openssl: true,
node_use_v8_platform: true,
node_with_ltcg: false,
node_without_node_options: false,
openssl_fips: '',
openssl_is_fips: false,
shlib_suffix: 'so.72',
target_arch: 'arm',
v8_enable_gdbjit: 0,
v8_enable_i18n_support: 1,
v8_enable_inspector: 1,
v8_no_strict_aliasing: 1,
v8_optimized_debug: 1,
v8_promise_internal_field_count: 1,
v8_random_seed: 0,
v8_trace_maps: 0,
v8_use_siphash: 1,
v8_use_snapshot: 1,
want_separate_host_toolset: 1
}
pi@raspberrypi:~ $ npm config list | grep -i arm
user-agent = "npm/6.14.5 node/v12.18.2 linux arm"
pi@raspberrypi:~ $ /usr/sbin/node -p "process.config.variables.arm_version"
bash: /usr/sbin/node: No such file or directory
pi@raspberrypi:~ $ /usr/local/bin/node -p "process.config.variables.arm_version"
7

@diegodev3 Thanks, it looks like there are two ARMv7 node executables so I'm unsure why you're seeing an error message that includes linux-armv6. To help you debug this, the logic to determine the platform version in use at runtime is https://github.com/lovell/sharp/blob/master/lib/platform.js#L16

values of the variables used in https://github.com/lovell/sharp/blob/master/lib/platform.js
process.env.npm_config_arch undefined
process.arch "arm"
process.env.npm_config_platform undefined
process.platform "linux"
process.env.npm_config_arm_version undefined
process.config.variables.arm_version undefined

I'm confused. You stated that the value of process.config.variables.arm_version was 7 for both versions of node on your machine, but now it has the value undefined.
Are you running your script via an explicit path e.g. /usr/local/bin/node script.js ?

I'm using electron on my project.
electron --disable-gpu .
I changed the value '6' to '7' at https://github.com/lovell/sharp/blob/master/lib/platform.js#L16 and it worked normally!

Aha, it looks like Electron doesn't set arm_version. Electron provides binaries for ARMv7 and not ARMv6, so perhaps we should look for process.versions.electron and consider its presence the equivalent of arm_version=7. Happy to accept a PR for this if you're able.

Hey @lovell i tried to uninstall and install node again, but nothing happens. I will post the new Output of the command above. I still dont know how to ensure that the ARMv7 node version is also used at run time.
whereis node

node: /usr/bin/node /usr/include/node /usr/share/man/man1/node.1.gz

node -p "process.config.variables"

{ arm_float_abi: 'hard',
arm_fpu: 'vfpv3',
arm_thumb: 0,
arm_version: '7',
asan: 0,
build_v8_with_gn: false,
coverage: false,
debug_nghttp2: false,
enable_lto: false,
enable_pgo_generate: false,
enable_pgo_use: false,
force_dynamic_crt: 0,
gas_version: '2.28',
host_arch: 'ia32',
icu_data_in: '../../deps/icu-small/source/data/in/icudt64l.dat',
icu_endianness: 'l',
icu_gyp_path: 'tools/icu/icu-generic.gyp',
icu_locales: 'en,root',
icu_path: 'deps/icu-small',
icu_small: true,
icu_ver_major: '64',
llvm_version: 0,
node_byteorder: 'little',
node_debug_lib: false,
node_enable_d8: false,
node_enable_v8_vtunejit: false,
node_install_npm: true,
node_module_version: 64,
node_no_browser_globals: false,
node_prefix: '/',
node_release_urlbase: 'https://nodejs.org/download/release/',
node_shared: false,
node_shared_cares: false,
node_shared_http_parser: false,
node_shared_libuv: false,
node_shared_nghttp2: false,
node_shared_openssl: false,
node_shared_zlib: false,
node_tag: '',
node_target_type: 'executable',
node_use_bundled_v8: true,
node_use_dtrace: false,
node_use_etw: false,
node_use_large_pages: false,
node_use_openssl: true,
node_use_pch: false,
node_use_perfctr: false,
node_use_v8_platform: true,
node_with_ltcg: false,
node_without_node_options: false,
openssl_fips: '',
openssl_no_asm: 0,
shlib_suffix: 'so.64',
target_arch: 'arm',
v8_enable_gdbjit: 0,
v8_enable_i18n_support: 1,
v8_enable_inspector: 1,
v8_no_strict_aliasing: 1,
v8_optimized_debug: 0,
v8_promise_internal_field_count: 1,
v8_random_seed: 0,
v8_trace_maps: 0,
v8_typed_array_max_size_in_heap: 0,
v8_use_snapshot: true,
want_separate_host_toolset: 1 }

npm config list | grep -i arm

user-agent = "npm/6.14.4 node/v10.21.0 linux arm"

/usr/bin/node  -p "process.config.variables.arm_version"

7

/usr/include/node -p "process.config.variables.arm_version"

bash: /usr/include/node: Ist ein Verzeichnis

I hope u can help me again.

Aha, it looks like Electron doesn't set arm_version. Electron provides binaries for ARMv7 and not ARMv6, so perhaps we should look for process.versions.electron and consider its presence the equivalent of arm_version=7. Happy to accept a PR for this if you're able.

Changes to ensure armv7 version if using electron in #2292

v0.26.0 now available, thanks for the PR.


"Bio" module not installing properly

@taylorreiter ran into an issue while pushing updates yesterday, addition of Bio or biopython as modules through toml does not create a version of KEGG-decoder 'tanglegram' that produces an output. Any insight as to the correct module to install?
Other elements still run correctly.

umm this is odd. was this a travis failure or something that failed locally?

@taylorreiter It happens at the pip install step. I tried the two different names of the Bio module that I could find. The pip install seems to work correctly and then running the tanglegram option throws an error about not finding the module.

oh! ok, did you try pip install biopython?

I have not. Though that would be troubling that the project toml couldn't install biopython properly...

yes I agree. import Bio is for biopython though. Am I asking the right questions or do I not understand the problem?

No, you are understanding correctly.

Hi,
I'm using the decoder for the first time (and love it!).
I installed it:python3 -m pip install KEGGDecoder
And KEGG-decoder --input KEGG_DECODER_in_all.txt --output FUNCTION_OUT_ALL.list --vizoption static runs perfectly fine.
However, when I try to pair it with a newick:
KEGG-decoder --input KEGG_DECODER_in_all_match_tree.txt --output FUNCTION_OUT_ALL.list --vizoption tanglegram --newick tree_output it produces this error:
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.7/bin/KEGG-decoder", line 10, in <module>
    sys.exit(main())
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/KEGGDecoder/KEGG_decoder.py", line 1390, in main
    make_tanglegram(genome, str(arg_dict['newick']))
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/KEGGDecoder/MakeTanglegram.py", line 20, in make_tanglegram
    genome_df = pd.read_csv(genome_df, index_col=0, sep='\t')
NameError: name 'pd' is not defined

Any idea what's wrong? Thanks a lot!

Thanks for the issue @jzrapp the tanglegram option has been causing some headaches. We are working on a fix.

@jzrapp this is particularly weird...the main function imports pandas: import pandas as pd, but then says its not defined. As @bjtully noted, we are working on fixing this!

@bjtully i wonder if #22 will solve this problem? the tanglegram function was not importing pandas, and it requires pandas. Without that library it should not produce an output

Now fixed.


Fetch SCM URL from UC

Initially, Repository name is used as in -p option
For EG: 42crunch-security-audit-plugin (which is a repo name) instead of 42crunch-security-audit (which is the plugin name)
Now, we can use the plugin short name instead of repo name.
Testing done
Unit Tests

Submitter checklist

[X] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[X] Ensure that the pull request title represents the desired changelog entry
[X] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Will take a look on review comments and merge conflicts tomorrow.

Right now, removed the fn to create a cache dir from the JenkinsPluginInfo class. I am not sure where to put the fn. Any suggestions?


allow user to delete value or set value with TTL in second

This pull request adds a feature to delete key-value or set key with a TTL value.

Hi @dgzlopes could you please take a look. My team is using this extension. However, we need to delete a key or set TTL to key since our test runs long and needs that feature to control and manage test data.

Hi @minhhoangvn! Thank you for opening the pull request.
Happy to hear that your team found the extension useful :)
The changes look good to me, so yeah, I will merge them. Thanks again!


Rebornix/move debugger out of kernels

While reading through https://github.com/microsoft/vscode-jupyter/pull/10855, it seems that kernels/debugger is directly used in notebooks and interactive window and no other sub components in kernels actually rely on it (only exception is kernels/variables/debugVariable but that is still related to debugging).
This PR is an attempt to move debugging feature code into notebooks and it proved our hypothesis that debugging is a standalone feature, moving it out doesn't modify any other file in kernels. This also opens the door of reviewing debugging code in notebooks and interactive-window and see if they can be unified.

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for feature-requests.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #10870 (3667f4e) into main (c0fe4cc) will increase coverage by 0%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##            main   #10870   +/-   ##
======================================
  Coverage     52%      52%
======================================
  Files        486      486
  Lines      33787    33787
  Branches    5501     5501
======================================
+ Hits       17782    17795   +13
+ Misses     14286    14275   -11
+ Partials    1719     1717    -2

Impacted Files
Coverage Δ

src/interactive-window/debugger/helper.ts
33% <ø> (ø)

src/interactive-window/types.ts
100% <ø> (ø)

src/kernels/serviceRegistry.node.ts
94% <ø> (-1%)
:arrow_down:

src/notebooks/debugger/constants.ts
100% <ø> (ø)

src/notebooks/debugger/debugLocationTracker.ts
73% <ø> (ø)

.../notebooks/debugger/debugLocationTrackerFactory.ts
50% <ø> (ø)

src/notebooks/debugger/debuggingTypes.ts
100% <ø> (ø)

src/notebooks/debugger/jupyterDebugService.node.ts
17% <ø> (ø)

...-window/debugger/interactiveWindowDebugger.node.ts
11% <100%> (ø)

...ve-window/debugger/jupyter/debugCellControllers.ts
23% <100%> (ø)

... and 19 more


Add node_meta to catalog/register endpoint

As per request from https://github.com/cablehead/python-consul/pull/190#issuecomment-403493820

Awesome thanks @ibrahimmenem

Thank you @ibrahimmenem. The PR is fine. One additional question. I it possible to update tests to cover node_meta? They are missed also in original PR #190.

@matusvalo Please check if it ok now!

Thank you @ibrahimmenem ! Looks great. I have found out that one point is missing:
https://www.consul.io/api/catalog.html#list-nodes-for-service
Could you add also this endpoint to your PR to have catalog fully covered? Is it feasible to you? After this I will merge your PR.

Thank you! Tomorrow I will merge the PR.


Automate news articles

There should be an automated list of the last X news articles and probably a "news archive" page as well.
Perhaps creating a new news article could be done with a Python script, e.g. "pqr-news-create" or something similar

You could write the news articles in Markdown and then use this https://github.com/scottstanfield/markdown-to-json to convert it to JSON, from which we could then put into the page.

I think we should just build a form with some level of authentication and have that it another mongo collection.

Since the only people updating the news would be Dr. Hutchison or Dr. Lambrecht, I think it would be easier to just to MD to JSON and then run a Python script.

Can we simply have a directory of Markdown filed ordered by date, eg
2015-05-11-Title.md
2015-05-15-first update.md
2015-06-01-June.md
Etc.
On Mon, May 11, 2015 at 2:56 PM Ritwik Gupta<EMAIL_ADDRESS>wrote:

Since the only people updating the news would be Dr. Hutchison or Dr.
Lambrecht, I think it would be easier to just to MD to JSON and then run a
Python script.
—
Reply to this email directly or view it on GitHub
https://github.com/pittquantum/backend/issues/13#issuecomment-101016742.

I'm fine with that. The only problem is if we want to add more features down the road (i.e. comment system, tag system, searching, etc.) it would be better if it was already in a mongo collection and we can just add more pivot tables for additional features as we come up with them.
But for a simple postings markdown should be fine.

I think the simple postings would work really well for now.

http://flask.pocoo.org/snippets/19/

Can we simply create a directory in the backend for the markdown files? If you do it, I'll create the "first launch" document. Filenames will be 2015-06-01-title.md, so it should be easy to parse dates.

I need to create the script for the news page first

Added article generation. All files in pqr/static/articles will be considered news items.


Resources not serializing correctly in edit command

cargo run edit https://atomicdata.dev/classes/Property recommends
print the output of what's commited, get this:

{
  "https://atomicdata.dev/properties/subject": "https://atomicdata.dev/classes/Property",
  "https://atomicdata.dev/properties/createdAt":<PHONE_NUMBER>264,
  "https://atomicdata.dev/properties/signer": "https://atomicdata.dev/agents/8S2U/viqkaAQVzUisaolrpX6hx/G/L3e2MTjWA83Rxk=",
  "https://atomicdata.dev/properties/set": {
    "https://atomicdata.dev/properties/recommends": {
      "ResourceArray": [
        "https://atomicdata.dev/properties/classtype"
      ]
    },
    "https://atomicdata.dev/properties/requires": {
      "ResourceArray": [
        "https://atomicdata.dev/properties/shortname",
        "https://atomicdata.dev/properties/description",
        "https://atomicdata.dev/properties/datatype"
      ]
    },
    "https://atomicdata.dev/properties/shortname": {
      "Slug": "property"
    },
    "https://atomicdata.dev/properties/isA": {
      "ResourceArray": [
        "https://atomicdata.dev/classes/Class"
      ]
    },
    "https://atomicdata.dev/properties/description": {
      "Markdown": "A Property is a single field in a Class. It's the thing that a property field in an Atom points to. An example is `birthdate`. An instance of Property requires various Properties, most notably a `datatype` (e.g. `string` or `integer`), a human readable `description` (such as the thing you're reading), and a `shortname`."
    }
  },
  "https://atomicdata.dev/properties/remove": [],
  "https://atomicdata.dev/properties/destroy": false,
  "https://atomicdata.dev/properties/signature": "J8ClI1HLFxr8MbwFutylrCrNB1CYk53fLCfsf7IbxVfIj61J8MXJuuyYxXRAKhaE1Ikwt/BliN6fRDcXHpCPDg==",
  "url": null
}

Turns out I hadn't updated commit serialization in the CLI. Fixed!


delete plm_dynamic_nullable and make plm_dynamic support return nil

调整了下，去掉了 plm_dynamic_nullable_xxx，默认的 plm_dynamic_xxx 就是 nullable 的。这样原有的判空逻辑不会受影响。只需要检查声明为 nonnull 的属性，将其改为使用 plm_dynamic_nonull_xxx

Codecov Report

Merging #10 into master will decrease coverage by 1.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage   90.88%   89.74%   -1.14%
==========================================
  Files           8        8
  Lines         351      351
  Branches       24       24
==========================================
- Hits          319      315       -4
- Misses         25       28       +3
- Partials        7        8       +1

Impacted Files
Coverage Δ

Tests/Tests.m
98.64% <100%> (ø)
:arrow_up:

Polymorph/Polymorph.m
88.73% <0%> (-2.82%)
:arrow_down:

Continue to review full report at Codecov.

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


Sort options and replace dots in keys

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.272%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
464

Relevant Lines:
514

💛  - Coveralls


Letsencrypt DNS Challenge not working for subdomain

Do you want to request a feature or report a bug?
Bug
What did you do?
Using: dnsProvider = "cloudflare"
when I use a top level domain "example.com" the challenge works. However when using a domain like "sub.example.com" it does not.
What did you expect to see?
A certificate securing my app.
What did you see instead?
No certificate
Output of traefik version: (What version of Traefik are you using?)
v1.3.5 / raclette docker image
What is your environment & configuration (arguments, toml, provider, platform, ...)?
traefikLogsFile = "/var/log/traefik/traefik.log"
accessLogsFile = "/var/log//traefik/access.log"
logLevel = "DEBUG"

defaultEntryPoints = ["http","https"]
[entryPoints]
  [entryPoints.http]
  address = ":80"
    [entryPoints.http.redirect]
      entryPoint = "https"
  [entryPoints.https]
  address = ":443"
    [entryPoints.https.tls]

[acme]
email =<EMAIL_ADDRESS>storage = "acme.json"
entryPoint = "https"
acmeLogging = true
onDemand = true
dnsProvider = "cloudflare"
[[acme.domains]]
   main = "sub1.example.com"
   sans = ["sub2.example.com", "sub3.example.com"]

[docker]
endpoint = "unix:///var/run/docker.sock"
domain = "example.com"
watch = true
exposedbydefault = false
swarmmode = true

[web]
address = ":8080"
  [web.auth.basic]
    users = ["admin:thisisnotapassword"]

Obviously I do not really use example.com
If applicable, please paste the log output in debug mode (--debug switch)
legolog: 2017/08/14 07:25:11 [INFO] acme: Registering account for<EMAIL_ADDRESS>legolog: 2017/08/14 07:25:12 [INFO][sub1.example.com, sub2.example.com, sub3.example.com] acme: Obtaining bundled SAN certificate
legolog: 2017/08/14 07:25:13 [INFO][sub1.example.com] AuthURL: https://acme-v01.api.letsencrypt.org/acme/authz/bla
legolog: 2017/08/14 07:25:13 [INFO][sub2.example.com] AuthURL: https://acme-v01.api.letsencrypt.org/acme/authz/bla
legolog: 2017/08/14 07:25:13 [INFO][sub3.example.com] AuthURL: https://acme-v01.api.letsencrypt.org/acme/authz/bla
legolog: 2017/08/14 07:25:13 [INFO][sub1.example.com] acme: Could not find solver for: tls-sni-01
legolog: 2017/08/14 07:25:13 [INFO][sub1.example.com] acme: Trying to solve DNS-01
legolog: 2017/08/14 07:25:13 [INFO][sub2.example.com] acme: Trying to solve DNS-01
legolog: 2017/08/14 07:25:13 [INFO][sub3.example.com] acme: Could not find solver for: http-01
legolog: 2017/08/14 07:25:13 [INFO][sub3.example.com] acme: Trying to solve DNS-01
legolog: 2017/08/14 07:25:23 [INFO][sub1.example.com] acme: Obtaining bundled SAN certificate
legolog: 2017/08/14 07:25:24 [INFO][sub1.example.com] AuthURL: https://acme-v01.api.letsencrypt.org/acme/authz/bla
legolog: 2017/08/14 07:25:24 [INFO][sub1.example.com] acme: Trying to solve DNS-01
2017/08/14 07:25:24 server.go:2753: http: TLS handshake error from <IP_ADDRESS>:65088: Cannot obtain certificates map[sub1.example.com:Error presenting token: Zone sub1.example.com. not found in CloudFlare for domain _acme-challenge.sub1.example.com.]+v

The bug itself seems to be in the way Lego is used/Lego itself:
the function getHostedZoneID() tries to get a cloudflare zoneId (id for example.com) but in stead it uses sub1.example.com and fails on getting the zoneId.

Diving deeper into lego it seems that it should return the correct domain on a SOA record response, but apperantly this goes wrong somehow. Am I doing something wrong here, do I need to change something from the default cloudflare setup? I'm currently forced to go back to self signed certs with my own CA which I would really like to avoid.

It turns out our internal dns returns a SOA record for the subdomain. returning the name of the subdomain in stead of the root domain.

@sjintas did you subdomain match you search/domain path of the server? because that is what i just ran into.
so basically if search/domain is foo.bar.tld ( of the traefik server)  and you try to issue any subdomain of that so sub.foo.bar.tld it will fail. Removing the search/domain from the /etc/resolv.conf fixes this again.
We have an own DNS server to, which traefik is using, so maybe its the same issue?

Well digging arround, its exactly the same, just in my case, not SOA is returned and @mmatur was explainting that the lega go acme library queries its current DNS for the SOA record to be able to poll for the TXT record being created..
Since i run a unbound server that SOA record is not present ( its the default unbound in opnsense/pfsense ) and i am right now expecting this being an issue for every isolated network .. which would be the DNA scenario of DNS01 i guess.
No idea how to proceed with that

Just a note to anyone else who comes across this - when using the helm chart I was able to overcome the SOA problem by setting the below params:
acme:
  resolvers:
  - abby.ns.cloudflare.com
  - sid.ns.cloudflare.com


Update compatibility for Symfony 7

Goal
Make the package compatible with Symfony 7.
Design
Because Symfony 7 compatibility requires return type-hinting because the framework types everything, we need to drop support for PHP < 7.0.
Changeset
Allowed versions 7 of symfony packages called in composer.json and update CI configuration.
Testing
Ran phpunit bin and checked if tests failed or not, they didn't.

Hi :wave:
Thank you for submitting this pull request to enable Symfony 7 support. We acknowledge the importance of Symfony 7 compatibility for BugSnag and have it on our backlog for future support. However, we currently don't have a definite timeline for the release of this feature. To stay informed about upcoming releases, we recommend watching this repository for updates and new releases.
While we appreciate your efforts in creating this pull request, we have decided to decline it at this time. We believe it's preferable for our engineering team to handle this update to ensure thorough consideration of the intricacies involved.


ksync syncthing keeps syncing the same folders

Hello ksync developers,
i am currently observing (apart from the other ticket) a phenomena, where the syncthing keeps syncing the a folder, allthough there are no changes locally nor remotely.
i currently use ksync with --local-read-only, thus i'd expect no test of remote changes at all.
observing the syncthing logs, i see tons of lines like this:
[A6ZLD] 12:10:33 VERBOSE: Remote change detected in folder "smooth-leopard-pontos-app-c5d75888-2xp6x": modified file vendor/symfony/dependency-injection/Compiler/DecoratorServicePass.php

followed by tons of lines like this:
[A6ZLD] 12:10:33 VERBOSE: Started syncing "smooth-leopard-pontos-app-c5d75888-2xp6x" / "vendor/sebastian/global-state/tests/SnapshotTest.php" (metadata file)
[A6ZLD] 12:10:33 VERBOSE: Finished syncing "smooth-leopard-pontos-app-c5d75888-2xp6x" / "vendor/sebastian/global-state/tests/SnapshotTest.php" (metadata file): Success

(random examples from the logs. if i'd search, i'd find a matching pair.)

@scones The wording might be a little ambiguous but --local-read-only writes no changes to the local folder. It will still read and write to the remote end. Is this the behavior you wanted?
Additionally, it looks like the syncing happening is to keep state up to date locally. Can you verify if changes are being written to locally? Maybe create a new file on the remote and see if it shows up. My understanding is that those metadata files are what Syncthing uses to track matching state, regardless of whether the file is replicated or not.

@timfallmk it is, in part, the behaviour i wanted. I wanted the local folder to be the source and the remote to be the target.
The files, syncthing assumes to be changed, are in fact unchanged. Those are external, pre-bundled libraries (hence vendor), that are not written or changed. Yet they are synced over and over again.
I do not have a problem with a sync from the remote to my local. My problem is with the endless loop of syncing initiated on the remote for unchanged files. I wouldn't even care that much for that if it weren't preventing the sync of the actually locally changed files to the remote.

So, to reiterate, although sync events are being triggered, remote files are not being written locally. Is that correct?
This could be an edge case with how one-way syncing is achieved. One-way syncing to the remote (i.e. when changes to the local are copied to the remote and changes to the remote are not copied to the local) is done by ignoring write operations on the local side. This may cause "file changed" messages to still be emitted from the remote side, which is probably what you're seeing. Why that would cause changes not to be mirrored properly is something else.
Could you give me a bit more info on what the sequence of events? Are you writing files locally, seeing the correct messages being emitted, then failing to see those files written remotely? This could also have something to do with your previous issue (#247) and how you're using minikube.

hello timfallmk,
i will try to take notes when next trying to use ksync. i will get back to you in the next few days with updates.

Feel free to reopen if needed.


❗❗❗👍🏻Good practices for raising issues and submitting PRs

Discussed in https://github.com/Luson045/medi-connect/discussions/83

Originally posted by Luson045 October  2, 2024
1) Do not ask the Admins to assign you issues that someone else created, you can ask if it is okay for you to collaborate
2) Do not give direct PRs,(i.e. You are giving PR without being assigned any issue) if done twice, you will be marked as FLAGGED
3) Do NOT Raise issues which already exists, we'll ignore replying to those. And if spammed, you'll be FLAGGED

"I'd like to work on this issue. Could you please assign it to me?

@Luson045 , i can make the issue and pull request template in the github action? can i try

We tried it but it kept failing, you can try @NawinKumarSharma

@NawinKumarSharma
A lot of workflow are failing, it's filling up my mail... Fix it.

@Luson045 , first of all, you need to generate the token from https://github.com/settings/developers
and then you have to add it to the project then only the workflow will run
Go to Your GitHub Repository:

Click on the Settings tab at the top of your repository page.
Navigate to Secrets and Variables:

In the left sidebar, scroll down to Secrets and variables under the Security section and click on Actions.
Create a New Repository Secret:

Click on the New repository secret button.
Set the Name and Value:

Name your secret MY_GITHUB_TOKEN

In the "Secret" field, paste your GitHub token.

Click the Add secret button to save it.


Long Text doesn't render correctly when in ScrollView

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: (8) x64 Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz
Memory: 1.82 GB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.11.0 - ~/.nvm/versions/node/v10.11.0/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v10.11.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 25, 26, 27, 28
Build Tools: 26.0.3, 27.0.3, 28.0.2
System Images: android-26 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.1 AI-173.4907809
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: 0.57.8 => 0.57.8
npmGlobalPackages:
react-native-cli: 2.0.1
Description
When placing a Text component into a ScrollView on iOS, if Text contains too many characters, then no text is rendered, however the Text component occupies the correct amount of space (i.e., the view scrolls). The number of characters for breaking the Text component varies depending on the device, but it is usually around 25,000.
N.B.: The bug is not present if we replace ScrollView with View.
This bug is not present on Android.
Wrong behaviour (no text, but the view scrolls):

Correct behaviour (text and the view scrolls):

Reproducible Demo
To reproduce the bug, run the following code on iOS
import React from 'react';
import { Text, ScrollView } from 'react-native';

export default () => (
  <ScrollView>
    <Text>{'a'.repeat(25000)}</Text>
  </ScrollView>
);

    <ScrollView contentContainerStyle={{ flex: 1 }}>

The bug seems to be related to the height of the content. So with a smaller font size, more text can be displayed.

Same problem here, agreed with @zuccha seems like the issue is with the Text component, the View size is correct.

I did some investigation in to this bug, and it appears to be related to Yoga, or the way we calculate heights using NSTextStorage. I wasn’t able to dig in much further.

Snack reproducing: https://snack.expo.io/@jkcooper/rn22713-long-text-in-scrollview

Related Issue: https://github.com/faceabook/react-native/issues/19453

Interesting update: I can confirm this only occurs in simulator. Running on devices doesn't appear to have this issue. I think it is a simulator issue.

Dupe of https://github.com/facebook/react-native/issues/19453 👌

<Text style={{ **flexShrink: 1** }}></Text>

Add flexShrink: 1
<Text style={{ flexShrink: 1 }}>


FRSky telem cannot by stopped via nsh

Tested on Pixracer

any details on this? Here's what I see:
nsh> frsky_telemetry status
frsky_telemetry: running: SPORT
nsh> frsky_telemetry stop
frsky_telemetry: freeing sPort memory
frsky_telemetry: .
frsky_telemetry: .
frsky_telemetry: .
frsky_telemetry: terminated.

For me it never stops but keeps printing the dots.

https://github.com/PX4/Firmware/pull/4210


AudioIn.stop() may be not be working for newer browser versions

When calling stop() for an AudioIn object, I received the following error in Chrome 49:

Uncaught TypeError: this.stream.stop is not a function

In Firefox 46.0.1:

MediaStream.stop() is deprecated and will soon be removed. Use MediaStreamTrack.stop() instead.

This likely corresponds to MediaStream.stop() has been deprecated (Firefox) and MediaStream Deprecations (Chrome). Other projects suggest that this was removed in Chrome M47.
I think this is a small fix from:
  p5.AudioIn.prototype.stop = function() {
    if (this.stream) {
      this.stream.stop();
    }
  };

to
  p5.AudioIn.prototype.stop = function() {
    if (this.stream) {
      this.stream.getTracks().forEach(function(track) {track.stop()});
    }
  };

I attempted to make this change myself, but I wasn't able to get mocha up and running.

I get similar issues w/ AudioIn, but it doesn't work for me at all in Chrome (Mac Version 49.0.2623.110 (64-bit)), not even the P5 demo page:
http://p5js.org/reference/#/p5.AudioIn
The error I get is:
NavigatorUserMediaError {name: "PermissionDeniedError", message: "Only secure origins are allowed (see: https://goo.gl/Y0ZkNV).", constraintName: ""}

Your case may be slightly different - change it to using https and see how it goes?

more details from @DigitalWheelie's original issue here: https://github.com/processing/p5.js/issues/1340#issuecomment-204747662

@DigitalWheelie Tried this on the latest version of Chrome. For your issue, using https, not http, will allow you to give the browser permission to use your microphone. Chrome will not allow using unsecure origins, even for the non-deprecated method navigator.mediaDevices.getUserMedia. This is to prevent attackers from listening to a user's microphone.
The documentation page you're referencing probably needs to handle the case where the user refuses to grant permission to use the microphone - or if the page is otherwise unable to get permission from the user. This is possible via an error callback on AudioIn.start().
Separately, the top-issue on the thread, AudioIn.stop() is flat-out broken, not deprecated, in Chrome, due to changes in the MediaStream API.

@therewasaguy Looks good, thanks.


Please add a license file

I'd like to add this to awesome-zsh-plugins, but it doesn't have a license file.
Please add a license file - if you don't have one in mind,  I recommend using choosealicense.com to help choose an appropriate one.
Thanks!

I've added MIT License, thank you @unixorn.


‘fileDirectory’ was not declared

The variable "fileDirectory"  was not declared in file LeGO-LOAM/src/mapOptmization.cpp:705. So, there is a error when build with "catkin_make -j1"
Need to add some declaration to LeGO-LOAM/LeGO-LOAM/include/utility.h

@Abramenko
Bug fixed.


Theming bibliography

My overall document uses text align justify. For the bibliography though, I'd rather switch to left but that currently doesn't seem to be supported.

I'm happy to share that this is what the converter does by default for bibliography lists. See https://github.com/asciidoctor/asciidoctor-pdf/blob/39c0ffbaede17f4219e5a62e4dc8648b10134e1f/lib/asciidoctor/pdf/converter.rb#L1367-L1368. However, the list does have to be designed as a bibliography. Otherwise, the converter cannot recognize it.
To make the list a bibliography, you must add the bibliography style either to the section that contains it (preferred):
[bibliography]
== Bibliography

* [[[bar]]] Bar, Foo. All The Things. 2010.

or directly on the list itself:
== Bibliography

[bibliography]
* [[[bar]]] Bar, Foo. All The Things. 2010.

@odrotbohm Does that solution work for you?

Not sure if I do anything wrong on my end. I am using the Bibtex extension as follows:
[bibliography]
= Bibliography

bibliography::references.bib[ieee]

The result looks like this:

The second entry seems to indicate that the text is still using justified alignment.

Aha! That's the detail I was looking for. I didn't realize you were using something else to generate the bibliography.
This turns out to be a shortcoming of asciidoctor-bibtex itself. It's not creating a list using the document model, so we have no way to recognize it as a bibliography list in Asciidoctor PDF. Instead, it's making a single paragraph for each bibliography item. Furthermore, it's not honoring the role set on the bibliography macro itself, so it's not even possible to pass in the text-left role to force the alignment on those paragraphs.
This is a problem that needs to be dealt with in asciidoctor-bibtex. It really shouldn't be creating multiple paragraphs. Instead, it should be constructing an unordered list with the bibliography role and letting the converter handle the formatting. It's important that extensions work in a way that is compatible with converters. Otherwise, the converters cannot properly format the document.

Thanks for the explanation, Dan. I'll open a ticket with the bibtex extension.

I've monkey-patched asciidoctor-bibtex (see asciidoctor/asciidoctor-bibtex#84). Not a serious suggestion for a fix, but does the trick for me for now.

Nice. I'll follow up there.


cant build in lua with new update

"No eligible build target"
When right before updating, everything worked just fine. Not sure what to do.

How are you configuring your build?

Closing due to inactivity.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.19.222",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=57e46acb3b48ea4e8efb1e1bea2e89e0c6cc43e2"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "57e46acb3b48ea4e8efb1e1bea2e89e0c6cc43e2",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "xen/console: harden hvc_xen against event channel storms\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.19.222 by commit 57e46acb3b48ea4e8efb1e1bea2e89e0c6cc43e2. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002663


Login fails on new branch

I tried with branch sveltekit-server-api-proxy, and fractal-server 1.2.5.
The login action fails, with no obvious errors in the browser.
The vite console logs are
(base) fractal@fractal-server-dev:/data/active/fractal/deployments/tmp_server_04/fractal-web$ npm run dev

><EMAIL_ADDRESS>dev
> vite dev

Port 5173 is in use, trying another one...

  VITE v4.2.2  ready in 974 ms

  ➜  Local:   http://localhost:5174/
  ➜  Network: use --host to expose
  ➜  press h to show help
SSR - Main layout
SSR - Main layout
Server info loaded: Alive true - 1.2.5 - testing
Server info loaded: Alive true - 1.2.5 - testing
Error loading user info
Error: Unable to fetch user identity
    at Module.whoami (/src/lib/server/api/v1/auth_api.js:35:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async load (/src/routes/+layout.server.js:34:20)
    at async Module.load_server_data (/node_modules/@sveltejs/kit/src/runtime/server/page/load_data.js:49:17)
    at async eval (/node_modules/@sveltejs/kit/src/runtime/server/page/index.js:150:13)
Error loading user info
Error: Unable to fetch user identity
    at Module.whoami (/src/lib/server/api/v1/auth_api.js:35:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async load (/src/routes/+layout.server.js:34:20)
    at async Module.load_server_data (/node_modules/@sveltejs/kit/src/runtime/server/page/load_data.js:49:17)
    at async eval (/node_modules/@sveltejs/kit/src/runtime/server/page/index.js:150:13)
SSR - Main layout
Server info loaded: Alive true - 1.2.5 - testing
Error loading user info
Error: Unable to fetch user identity
    at Module.whoami (/src/lib/server/api/v1/auth_api.js:35:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async load (/src/routes/+layout.server.js:34:20)
    at async Module.load_server_data (/node_modules/@sveltejs/kit/src/runtime/server/page/load_data.js:49:17)
    at async eval (/node_modules/@sveltejs/kit/src/runtime/server/page/index.js:150:13)
SSR - Main layout
Server info loaded: Alive true - 1.2.5 - testing
Error loading user info
Error: Unable to fetch user identity
    at Module.whoami (/src/lib/server/api/v1/auth_api.js:35:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async load (/src/routes/+layout.server.js:34:20)
    at async Module.load_server_data (/node_modules/@sveltejs/kit/src/runtime/server/page/load_data.js:49:17)
    at async eval (/node_modules/@sveltejs/kit/src/runtime/server/page/index.js:150:13)
12:55:42 PM [vite-plugin-svelte] ssr compile done.
package    	files	  time	   avg
fractal-app	    3	62.8ms	20.9ms

Note: this is actually with a specific setup, which involves SSH port forwarding and CORS.
I need to debug further.

Fractal-server logs:
INFO:     <IP_ADDRESS>:58232 - "POST /auth/token/login HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:58232 - "GET /api/alive/ HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:58246 - "GET /auth/whoami HTTP/1.1" 401 Unauthorized

Fixed by setting FRACTAL_SERVER_HOST=http://localhost:8000 instead of 127.0.01

For the record: this means that we were able to use fractal-web on a remote machine with a single ssh tunnel (the one for the fractal-web port), but without port-forwarding for fractal-server.
More debugging soon

Using localhost instead of <IP_ADDRESS> is required by the browser in order to accept the cookie that is sent by the client's server.
Using <IP_ADDRESS> does not match the localhost domain of the client's server, which in the end does not get stored in the browser and used to authenticate following requests through node server.
I don't understand what do you mean by:

[...] we were able to use fractal-web on a remote machine with a single ssh tunnel [...]


File changes made in pre-up task not included in builded image

I've realised that when I change files in pre-up stage script, this changes not included into building container.
Is this normal?
Maybe we can add pre-build stage?

I'm using docker builder.
Draft version: &version.Version{SemVer:"v0.15.0", GitCommit:"9d73889a1318a435d126bc5df846610d30cfbe7f", GitTreeState:"clean"}
Docker Version:
Client:
 Version:      18.03.1-ce
 API version:  1.37
 Go version:   go1.9.5
 Git commit:   9ee9f40
 Built:        Thu Apr 26 07:13:02 2018
 OS/Arch:      darwin/amd64
 Experimental: false
 Orchestrator: swarm

Server:
 Engine:
  Version:      18.03.1-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.5
  Git commit:   9ee9f40
  Built:        Thu Apr 26 07:22:38 2018
  OS/Arch:      linux/amd64
  Experimental: true

OS: macOS High Sierra 10.13.5

This was fixed in https://github.com/Azure/draft/pull/812 and is available in the canary release. It'll be available in the next release as well :)

@bacongobbler Thank you a lot. :)

Canary releases are linked here: https://github.com/Azure/draft/blob/master/docs/install-minikube.md#install-draft

Thank you


[FIX] changed pubchem ID for m01778c

Main improvements in this PR:
Fixed pubchem ID for m01778c
I hereby confirm that I have:

[X] Tested my code on my own computer for running the model
[X] Selected devel as a target branch

In addition to PubChem, should other metabolite ids (e.g. KEGG, MetaNetX) be modified as well? @jorgemlferreira

Hello again @Hao-Chalmers. So I've made a few changes that are present in the changelog provided on the commit. I think this part may be debatable, since most of the IDs provided by the model led to the conjugate base form of the metabolite. I don't know if this is the kind of identifiers you want in your model, so it's up for debate, since I believe most of the fatty acids are treated in the same manner. However, the initial change to the pubchem IDs are needed, and to be changed in all the compartments (I didn't do it in my first commit).
Please let me know if you just want changed the pubchem IDs, I'll rollback to the original .tsv and change only that.
Best regards

@jorgemlferreira the changes you made look okay based on the provided Changelog. But we'll need more time to evaluate them, and will come back to you later.

@Hao-Chalmers Hi again. No problem. I'll assume this kind of changes could lead to a high amount of work, and may not even be necessary, depending on how you want the model to work (specially in fatty acids metabolism).
Best

@jorgemlferreira thanks for the input with detail changelog and accurate InChI mapping! Really surprised by that the commit message could be so long, and can be a good way of log changes.
The modifications to PubChem and CHEBI ids are good. I would suggest to keep the ids from HMDB and LipidMaps though. Because CHEBI and PubChem have very detail classification, while the others don’t. The HMDB and LipidMaps ids are acceptable and good for inclusiveness. In this sense, the KEGG id for ocdcea should also be retained. What do you think?

@Hao-Chalmers Hello again, and thank you for the kind words. I agree with you, mainly due to how the fatty acids metabolism is built in the model. However, at some point in the future (maybe when another significant breakthrough is done in this area) it should be considered to revisit and rebuild the whole fatty acids metabolism, as a community effort.
I agree with only changing the PubChem and CHEBI ids, since the others are not 100% incorrect. I'll rollback the changes and only change the ids mentioned before.
Best,
Jorge Ferreira

@jorgemlferreira I am also very much in support of a complete redesign of the fatty acid metabolic network portion of Human-GEM, though I realize this is no small task.

@JonathanRob I think everyone wins in this scenario. You've made an important step in making this model and allowing the community to contribute in every way they can. And yes, I know this is not a simple and/or easy task, but a collaboration between the main and small developers/users of human metabolic models could make an integrated effort to improve this, and this repository is an important tool for that. Let's hope this can happen, and if it happens, I'll gladly help in anything I can.
Best,
Jorge


Enhance the docker windows installer to have an option NOT to install the daemon (and Hyper-V)

Tell us about your request
There should be an option to NOT install the docker daemon (and Hyper-V) if only the CLI tools are needed (and allowed).
Which service(s) is this request for?
Docker Windows Installer.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
It is not allowed to install docker (Hyper-V / WSL) in some companies.
Are you currently working around the issue?
No workaround available.
Additional context
See https://github.com/docker/for-win/issues/8872

This is the same as #144?

Yes. Seems to be the same. I envision an installer which installs the same as now, but NOT the daemon.

docker-cli
compose-cli
... everything but the daemon

I think we can dupe this against #144.

I think we can dupe this against #144.


What makes the NAME loader faster than the NetCDF loader?

📰 Custom Issue

@bsherratt has provided an interesting case. A Name III .txt file describing:

200 x 200 grid
~200 phenomena

The file takes ~20s to load. If Iris is used to convert the file to NetCDF, that NetCDF file takes ~105s to load. Both loaders are unreasonably slow in this example, since the grid is shared between all phenomena, yet the Coord instances are created on a Cube-by-Cube basis (see #3172 for discussion on sharing). But why is NetCDF even slower?
File available on request.

Just to update...
We had a theory that "breaking" the coordinate metadata could speed this up, and it really did.
Pre-processing: rename each variable's coordinates attribute to something that iris does not recognise. It will therefore not attempt to create any aux coords on load (so they show up as cubes instead).

netCDF4 example
with nc.Dataset(filename, "a") as file:
    for var in file.variables.values():
        if "coordinates" in var.ncattrs():
            var.renameAttribute("coordinates", "fake_coordinates")
    file.sync()

Post-processing: identify the "cubes" that were supposed to be aux coords, and add them to the relevant cubes. This can be done by overriding the usual netcdf loaders in iris.fileformats.FORMAT_AGENT with a simple wrapper around iris.fileformats.netcdf.load_cubes:

Incomplete example
def load_cubes(filenames, callback=None, constraints=None):
    # Identify coords
    cubes = []
    unknown = []
    coord_names = set()
    for cube in netcdf.load_cubes(filenames, callback, constraints):
        fake_coords = cube.attributes.get("fake_coordinates", "").split()
        if fake_coords:
            # Definitely a cube
            cubes.append(cube)
            coord_names.update(fake_coords)
        else:
            # Might be a cube or a coord
            unknown.append(cube)

    # Create the coords
    coords = {}
    for cube in unknown:
        if cube.name() in coord_names:
            coord = AuxCoord(cube.data)
            coord.metadata = cube.metadata
            coords[coord.var_name] = coord
        else:
            cubes.append(cube)

    # Add coords to cubes
    for cube in cubes:
        fake_coords = cube.attributes.pop("fake_coordinates", "").split()
        for name in fake_coords:
            # TODO: Assumes scalar...
            cube.add_aux_coord(coords[name])

        yield cube

This doesn't cover everything, such as bounds or non-scalar aux coords coords, but it did bring the load time down to ~3 seconds. The re-adding coordinates part is a tiny proportion of that so I don't imagine a full solution would take much longer either.
However... in all .nc cases the cube data is lazy, while the NAME loader does not create lazy data. Realising the data takes about 50s, so netCDF is still slower overall.

Tried really basic test where we bypass lazy array creation in _get_cf_var_data, if the array is "small".
This really speeds up the testcase for netcdf load -- from ~150sec to ~4secs ...
Like this...
_NONLAZY_SMALL_AUXCOORDS = True

def _get_cf_var_data(cf_var, filename):
    if _NONLAZY_SMALL_AUXCOORDS and np.prod(cf_var.shape) < 20:
        result = cf_var[:]
    else:
        # Get lazy chunked data out of a cf variable.

Of course, #3172 would be a solution, but sadly that still looks a long way off.
This sounds like a possible win, as-is ??
It doesn't seem like a breaking change.
How do we choose a size threshold ?

Closed by #5229


Tag sha256 together with current-podified

Tagging sha256 together with current-podified avoid it to be delete from quay in case we are tagging the same promoted-hash that was rebuilt.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/lgtm
We should tetsproject it

/lgtm

recheck

recheck

/approve
Doesn't look too nasty.


feat(typescript_indexer): add support for indexing literal properties

Add support for indexing string and numeric literals in property names,
and referencing string and numeric literals in a property access.

cc @evmar

@evmar / @kythe can you add the buildbot tag?

@evmar / @kythe can we merge?


Rules.toml empty?

Hey, thank you for this I’m trying to get up and running on traefik 2 from 1.7 and your repo is helping but the rules.toml that I need to get for google auth etc is empty please can you populate it.

Thanks for pointing that our I had traefik2 directory in .gitignore I have updated that.


Unable to access 'getting started' on webpage

Hi! Just giving you a heads up that there is a 404 error when trying to access 'getting started' on your application web page, furthermore the other link on your page goes to a PHP error:

MediaWiki 1.23.9
LocalSettings.php not found.
Please set up the wiki first.

Yup the wiki is pretty broken. Havnt had any time to fix. Will be in the next few days :-)

fyi: the link on the orange button ("getting started) works fine instead (click me)

Wiki is online again however will be moving to github wiki soon


Building out useable items

Currently I am in the process of building out useable items. Currently there is not really a process in the code that builds out useable items other than what is in the info node. For most useable items the important information is actually in spec which is not iterated over.
I am trying to figure out the best way to structure this. While we could always created a nested struct it does not seem necessary
type Item struct {
         Info Info
         Spec Spec
}

type Info struct {
         // Everything in info
}

type Spec struct {
         // Everything in spec
}

This seems like it would be rather tedious and not have any real advantages. The way I am currently experimenting with is by iterating over a slice of subSearches and creating items to map[int]Item . Once the iteration has finished the structs are merged.
				for j := uint32(0); j < uint32(itemGroupNode.ChildCount); j++ {
					itemNode := nodes[itemGroupNode.ChildID+j]
					name := textLookup[itemNode.NameID]

					var item Item
					itemMap := make(map[int]Item)

					subSearches := []string{"/info", "/spec"}
					for i, subSrch := range subSearches {
						subSearch := search + "/" + groupName + "/" + name + subSrch

						valid := gonx.FindNode(subSearch, nodes, textLookup, func(node *gonx.Node) {
							itemMap[i] = getItem(node, nodes, textLookup)
						})

						if !valid {
							log.Println("Invalid node search:", subSearch)
						}

					}
					item = itemMap[0]

					mergo.Merge(&item, itemMap[1])

					name = strings.TrimSuffix(name, filepath.Ext(name))
					itemID, err := strconv.Atoi(name)

					if err != nil {
						log.Println(err)
						continue
					}

					item.InvTabID = byte(itemID / 1e6)
					items[int32(itemID)] = item
				}

This method is using the following package at the cost of reflection:
https://github.com/imdario/mergo
Any ideas that might be more efficient or should this suffice?

Unless I am missing something I think the following would work best as there is less copying being done:
				for j := uint32(0); j < uint32(itemGroupNode.ChildCount); j++ {
					itemNode := nodes[itemGroupNode.ChildID+j]
					name := textLookup[itemNode.NameID]

					subSearches := []string{search + "/" + groupName + "/" + name + "/info",
						search + "/" + groupName + "/" + name + "/info"}

					var item Item

					for _, subSearch := range subSearches {
						valid := gonx.FindNode(subSearch, nodes, textLookup, func(node *gonx.Node) {
							getItem(node, nodes, textLookup, &item)
						})

						if !valid {
							log.Println("Invalid node search:", subSearch)
						}
					}

					name = strings.TrimSuffix(name, filepath.Ext(name))
					itemID, err := strconv.Atoi(name)

					if err != nil {
						log.Println(err)
						continue
					}

					item.InvTabID = byte(itemID / 1e6)
					items[int32(itemID)] = item
				}

where getItem is now:
func getItem(node *gonx.Node, nodes []gonx.Node, textLookup []string, item *Item) {
	for i := uint32(0); i < uint32(node.ChildCount); i++ {
		option := nodes[node.ChildID+i]
		optionName := textLookup[option.NameID]

		switch optionName {
		...
		default:
			log.Println("Unsupported NX item option:", optionName, "->", option.Data)
		}

	}
}

You can just extend the item struct to add the missing fields and then add the spec names in the switch statement