Ensure Windows SDK directories are not cleared when caller specifies include/library dirs

This corrects a long-standing bug in the _msvccompiler implementation where the INCLUDE and LIB variables from the environment would be entirely overridden by --include-dirs and --library-dirs options (regardless of how they were passed). Instead, these should be appended after any user-specified directories. Overriding the _fix_*_args methods handles this for all users of the class.
This will make fixes such as what PyWin32 uses redundant.

@jaraco You know I don't like pinging you directly on stuff, but I'd love to get this off my in-progress list before I take a couple weeks away :-)

I welcome pings. Can I take a look at this Friday?

It feels like this approach is papering over a design defect. From distutils' perspective (and setuptools'), add_include_dir is used exclusively by this compiler, so it doesn't make sense to leave it lying around if its only usage was broken.
I'd rather see a solution that involves re-designing CCompiler such that add_*_dirs does the right thing. Or if add_*_dirs was never going to work, remove it and provide a proper interface where a subclass can supplement the include dirs.
More importantly, if this bug has been lying around essentially since its inception, perhaps it would make sense to create a regression test to capture the flaw (missed expectation), especially since the change didn't break any tests.

The design defect has been in MSVCCompiler ever since I rewrote it (maybe earlier, I didn't check). Fundamentally, MSVC requires all its directories specified with -I/-L, while CCompiler assumes that only extra directories need to be specified this way.
This change handles that assumption by injecting the compilers directories later on, just before launching the compiler. They get added after any user directories, so nothing should break. At worst, the system directories will be added twice by everyone with workarounds (e.g. PyWin32). (I guess technically the worst is that some deliberately(!?) failing builds will start succeeding, but that's the point of bug fixes.)
I'd love to completely rework all the compilers, but since that would break everyone's hacks, it can't really be in setuptools or distutils ;-)

Any more thoughts on this one? I'm still not sure what a test would prove, and the path ordering should ensure that it can only affect builds that currently fail with missing header files.

I notice that set_include_dirs, which is what the different commands use, purports not to affect include dirs used by the compiler by default:
https://github.com/pypa/distutils/blob/1845a34d7151718ee65bbb6e392b41bf404e1bc4/distutils/ccompiler.py#L233-L241

I'm working on writing a test for this change, but I can't even find where _fix_compile_args is called for this compiler. Have you confirmed this change has the desired effect? Can you create repro steps that replicate the broken behavior?

I notice that set_include_dirs, which is what the different commands use, purports not to affect include dirs used by the compiler by default:

Yes, this is why my change makes it so that it doesn't ;-)
"By default" behaves slightly differently on Windows, because the default ones are smuggled in through the environment, not automatically determined by the compiler itself. Since we wipe out the environment, we need to pass them along ourselves, and previously were doing it through set_include_dirs essentially, when we should've been doing it independently from this.

Have you confirmed this change has the desired effect? Can you create repro steps that replicate the broken behavior?

It definitely works. I can have a go at repro steps, but essentially what I'll try to do is create a .c file that includes something from the Windows SDK, and show that calling build_ext -L <other dir> prevents the SDK from being found. Maybe you'll get to it before me.

I'm close to a repro. It requires attempting to cross-compile and specifying -p on the command line (or presumably through a configuration file), which causes build_ext to initialise the compiler earlier. Then specifying any overrides with -I will wipe the include directories.

So the version without a subclass requires the -p option to be passed. Passing win32 to a 64-bit interpreter is fine, as long as it doesn't match get_platform() (the default).
Alternatively, subclassing build_ext and calling set_include_dirs, no matter how "correctly", will break it too. This is a pretty common override that I see in projects.
from setuptools import setup, Extension
from setuptools.command.build_ext import build_ext as _build_ext

EXT_MODULES = [Extension(
    'file',
    ['file.c'],
)]

class build_ext(_build_ext):
    def compile(self):
        self.set_include_dirs(self.include_dirs)
        super().compile()

setup(
    name="proj",
    version="1.0",
    ext_modules=EXT_MODULES,
    cmdclass={"build_ext": build_ext},
)

One thing that is missing from my patch that only impacts the include directories is, as you pointed out, _fix_compile_args doesn't get called. It looks like it is meant to be called from _setup_compile rather than duplicating the same code in that function. I was mainly interested in the library dirs, which is how I had all of my stuff working with this change.
Considering all the compiler classes use this for preprocessing but not compiling, and the method says it's for compiling, I assume this was an oversight and it should be changed for all of them. I'll update my PR with it for reference, but if we only want to enable it for MSVC then I'm not going to argue too strongly. Nobody else overrides it within distutils or setuptools currently.

Today I stumbled on #166, where one of the extension building tests for Windows is failing to link. I wonder if that test somehow serves as a repro for this issue.

In the bugfix/153-test branch, I've started work on a test to capture the failure. It doesn't fail yet because:

The C file doesn't contain any SDK calls.
The set_{include,library}_dirs calls happen before .compile, which is what triggers compiler.initialize() (add add_*_dirs happens in initialize, so won't be affected by the earlier set).

I'm thinking for the second issue to simply repeat the set_*_dirs call and then run compile again. Is that what's happening with build_ext?
Steve, can you help by providing some minimal C file that one would expect to fail in this scenario? I'd be happy with one that just fails on Windows for now, but it'd be nice to have a comparable one for Unix (maybe that relies on libc?).
Feel free to send a PR to that branch, or just post it here and I'll integrate it.

Sure. I got it to fail with this c file:
#include <Python.h>
#include <windows.h>

PyMODINIT_FUNC
PyInit_file(void)
{
    return NULL;
}

This setup.py:
from setuptools import setup, Extension

setup(
    name="proj",
    version="1.0",
    ext_modules=[Extension('file', ['file.c'])],
)

And then invoking as python setup.py -p win32 (where the default plat-name would have been win-amd64).
Changing the default platform is the easiest way to trigger this, though I've seen it in more complex cases where the compiler is made to initialize early or where paths are updated later.
You won't see the same issue on other platforms because it only affects _msvccompiler, which is only used on Windows.

I believe I've replicated the failure in 71cffcb8a8ec7e36dc389a5aa6dc2cc9769a9e97.

I believe I've replicated the failure in 71cffcb.

Yeah, that ought to do it. I mainly avoided doing it that way because nobody "out there" does that - they always get caught by the more subtle cases.

Merging this with bugfix/153-test indicates that the fix has the intended effect and the test captured the failure. I'd like to do a bit of refactoring, but I'm confident this PR can be merged soon.


Missing instructions for tests

Describe the bug
The automated tests contained within the tests directory cannot be easily run, potentially due to a lack of clear documentation or possibly an issue around imports as is suggests in the tracebacks when trying to run these tests.
To Reproduce

Running with pytest

In an environment without iwopy installed or in an environment with iwopy installed(python-3-10-environment) user@machine:~/path/to/iwopy/repository$ python -m pytest tests
================================================================== test session starts
==================================================================
platform linux -- Python 3.10.10, pytest-7.4.0, pluggy-1.2.0
rootdir: /home/bewinche/modelling/reviewing/iwopy
collected 0 items / 7 errors
......
======================================================================== ERRORS =========================================================================
______________________________________________________ ERROR collecting tests/scipy/test_scipy.py
ImportError while importing test module '/home/bewinche/modelling/reviewing/iwopy/tests/scipy/test_scipy.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
../../../anaconda3/envs/py310/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/scipy/test_scipy.py:3: in <module>
    from iwopy import DiscretizeRegGrid, SimpleConstraint
iwopy/__init__.py:12: in <module>
    from . import interfaces
iwopy/interfaces/__init__.py:2: in <module>
    from . import pymoo
iwopy/interfaces/pymoo/__init__.py:1: in <module>
    from .optimizer import Optimizer_pymoo, DefaultCallback
iwopy/interfaces/pymoo/optimizer.py:5: in <module>
    from .problem import SingleObjProblem, MultiObjProblem
iwopy/interfaces/pymoo/problem.py:4: in <module>
    from .imports import check_import, Problem, Real, Integer
E   ImportError: cannot import name 'Real' from 'iwopy.interfaces.pymoo.imports' (/home/bewinche/modelling/reviewing/iwopy/iwopy/interfaces/pymoo/imports.py)
================================================================= short test summary info ================================================================
ERROR tests/core/test_discr_grid.py
ERROR tests/core/test_discretize.py
ERROR tests/core/test_gradients_ana.py
ERROR tests/core/test_varmap.py
ERROR tests/pygmo/test_pygmo.py
ERROR tests/pymoo/test_pymoo.py
ERROR tests/scipy/test_scipy.py
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 7 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
==================================================================== 7 errors in 1.43s ===================================================================

Running with Python directly

In an environment without iwopy installed(python-3-10-without-iwopy) user@machine:~/path/to/iwopy/repository$ python tests/core/test_discr_grid.py
Traceback (most recent call last):
  File "/home/bewinche/modelling/reviewing/iwopy/tests/core/test_discr_grid.py", line 3, in <module>
    import iwopy
  File "/home/bewinche/anaconda3/envs/py310/lib/python3.10/site-packages/iwopy/__init__.py", line 12, in <module>
    from . import interfaces
  File "/home/bewinche/anaconda3/envs/py310/lib/python3.10/site-packages/iwopy/interfaces/__init__.py", line 2, in <module>
    from . import pymoo
  File "/home/bewinche/anaconda3/envs/py310/lib/python3.10/site-packages/iwopy/interfaces/pymoo/__init__.py", line 1, in <module>
    from .optimizer import Optimizer_pymoo, DefaultCallback
  File "/home/bewinche/anaconda3/envs/py310/lib/python3.10/site-packages/iwopy/interfaces/pymoo/optimizer.py", line 5, in <module>
    from .problem import SingleObjProblem, MultiObjProblem
  File "/home/bewinche/anaconda3/envs/py310/lib/python3.10/site-packages/iwopy/interfaces/pymoo/problem.py", line 4, in <module>
    from .imports import check_import, Problem, Real, Integer
ImportError: cannot import name 'Real' from 'iwopy.interfaces.pymoo.imports' (/home/bewinche/anaconda3/envs/py310/lib/python3.10/site-packages/iwopy/interfaces/pymoo/imports.py)

In an environment with iwopy installed(python-3-10-with-iwopy) user@machine:~/path/to/iwopy/repository$ python tests/core/test_discr_grid.py
Traceback (most recent call last):
  File "/home/bewinche/modelling/reviewing/iwopy/tests/core/test_discr_grid.py", line 3, in <module>
    import iwopy
  File "/home/bewinche/anaconda3/envs/testground/lib/python3.10/site-packages/iwopy/__init__.py", line 12, in <module>
    from . import interfaces
  File "/home/bewinche/anaconda3/envs/testground/lib/python3.10/site-packages/iwopy/interfaces/__init__.py", line 2, in <module>
    from . import pymoo
  File "/home/bewinche/anaconda3/envs/testground/lib/python3.10/site-packages/iwopy/interfaces/pymoo/__init__.py", line 1, in <module>
    from .optimizer import Optimizer_pymoo, DefaultCallback
  File "/home/bewinche/anaconda3/envs/testground/lib/python3.10/site-packages/iwopy/interfaces/pymoo/optimizer.py", line 5, in <module>
    from .problem import SingleObjProblem, MultiObjProblem
  File "/home/bewinche/anaconda3/envs/testground/lib/python3.10/site-packages/iwopy/interfaces/pymoo/problem.py", line 4, in <module>
    from .imports import check_import, Problem, Real, Integer
ImportError: cannot import name 'Real' from 'iwopy.interfaces.pymoo.imports' (/home/bewinche/anaconda3/envs/testground/lib/python3.10/site-packages/iwopy/interfaces/pymoo/imports.py)

Expected behavior
From standard testing practices, a user would expect for the tests to be runnable, either with pytest or directly (e.g., python path/to/test.py). This should then produce a test output or some measure of success. It's possible that this issue is install related (e.g., that packages required for the testing do not come installed when installing iwopyas dependencies) or that documentation is missing and could be clearer around how to run these automated tests.
Desktop (please complete the following information):

OS: Debian 11.6

Additional context
This was raised as part of the review for the JOSS here.

Thanks for the bug report. Which version of iwopy are you running? It this the latest main branch from github, or an installation from pypi, or from conda-forge? It seems that I cannot reproduce this behaviour in my local clone of the repository. Thanks

Sorry, I can now indeed reprodce this for a fresh install! I will try to find out what is behind this.

I think this due to pymoo not being installed. For me, pip install pymoo solved the issue (for conda installations please install from there).
Currently the optimization packages are optional. However, this behaviour as it is now is not desired. I will think of a new solution.

@BenWinchester The instructions for tests have now been added to the documentation and also the README.


README: update installation instructions

lightargs is currently broken for Python2. Fixing the version to 1.22 resolves the problem. I've also changed the repository to https checkout to avoid private key requirements (but the yaml config will still require a private key)

Thanks for the fixes!


Very uneven column heights if a column has an item with a very big height

What the title says:
if a column has a huge item it gets way past the others.
This happens with the balanced_columns branch,

The solution is here:
https://github.com/rnmp/salvattore/pull/70#issuecomment-128822579
I suppose we could add this to the Readme file.
Thanks


Revert "Bump @types/react from 18.2.31 to 18.2.32"

Reverts otterscan/otterscan#1418

The new types are causing compilation errors, it may be just the types are wrong.


[WIP] Add lnd-graph-crawl by mutatrum

https://github.com/rootzoll/raspiblitz/issues/2087
Should this be on the menu too?
Maybe change the bos score json to this one https://nodes.lightning.computer/availability/v1/btc.json
Edit: It was working, now is not, wait a bit...
The script is creating a 0B file, but when running manually, it is working.
Edit: Even though this is a short PR, I stopped working on it for now due to giving privilege to Tor menu, if you want to take this PR, just comment and do it.

Revisiting this one...
i built a colab notebook, that does some analysis on the describegraph, still very WIP, but it gives some recommendations based on centrality and better position your node, if you want to check it out! I thinks it more focused on routing than decentralization though...
Can try to make into a python script or something...
https://colab.research.google.com/drive/1EF_i8kM1rOhPw5mN2AXpZTymjCS8K_MZ?usp=sharing


Add authentication

Food access point providers need to be able to log in in order to update their food access point details. Devise is probably be a good option.

I would be willing to create an authentication model if that would be helpful. I can do it from scratch or use devise if you would prefer. Should I offer this help in the slack channel??

Yes this would helpful! I usually default to devise, seems like it would be wise to stand on the community's shoulders rather than write something from scratch?

that's fine. writing from scratch isn't that much harder and I feel like i know all that is going on...but devise is battle-tested and robust...so devise it is....seed data first though

i've installed devise and started applying some styling and getting it look like it's part of the app and working.  I'm wondering if we want to allow for registrations from the app - so that anyone could register - or if the registrations are really restricted to people who would need to update info on a site, in which case we might want to restrict registration in some fashion?

ALso, when should I submit a PR? When it's ALL done? Or incrementally as I work on it?

i've installed devise and started applying some styling and getting it look like it's part of the app and working. I'm wondering if we want to allow for registrations from the app - so that anyone could register - or if the registrations are really restricted to people who would need to update info on a site, in which case we might want to restrict registration in some fashion?

Just seeing your comment now, months after the fact! Let's hold off on figuring that out until we can run a minimally working version of this by Little Rivers. I think what you've done so far meets the requirements to close this issue


highlight_fields causing them to be shown as 'undefined'

Description
highlight_fields causing them to be shown as 'undefined'
Steps to reproduce
if the field is not in  queryBy: "description,concat" it's shown as undefined when there is a highlight.
in this case:
highlight_fields:"name,description,concat",
Typsense Version: 0.22.rc6
"typesense-js": "^0.14.0",
"typesense-instantsearch-adapter": "^2.0.1"
OS: linux ubuntu
note: earlier versions of the typesense js libraries were showing all these fields as undefined even if there was no highlight.

@dianos If you use highlight_fields (which means results will be highlighted with snippetting), you'd need to use the Snippet widget to access the results.

Snippet causes text in the field to be cut short.  Is there a way to highlight full fields that are not in queryBy?


coverity module: refactoring for module stabilization

This commit is to stabilize the functions of the coverity module.
Changelog

Added cibot_comment to report current defects
Refactored the existing functions
Improved exception handling to control coverity scan
Fixed typos

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>

:memo: Version: 1.3.20190927. Thank you for submitting PR #561. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

INFO: You can read if there are syntax errors in the our shellcheck report. Please read http://nnsuite.mooo.com/TAOS-CI/ci/repo-workers/pr-checker/561-201911050800320.37056803703308-770a8e60e32abac38f1635348468b065dbc9b06b/report/shellcheck_syntax_result.txt.

After this PR:

INFO: You can read if there are syntax errors in the our shellcheck report. Please read http://nnsuite.mooo.com/TAOS-CI/ci/repo-workers/pr-checker/561-201911050813480.30481505393982-fbbdb33d62dc1f70bd02c12f36a779f04b42489a/report/shellcheck_syntax_result.txt.


404 Not Found while running ng update after installing<EMAIL_ADDRESS>

Bug Report or Feature Request (mark with an x)
- [X ] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [X] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions
Angular CLI: 6.0.8
Node: 8.11.3
OS: win32 x64
Angular: 6.0.9
... animations, common, compiler, core, forms, http
... language-service, platform-browser, platform-browser-dynamic
... router
Package                           Version
@angular-devkit/architect                 0.6.8
@angular-devkit/build-angular         0.6.8
@angular-devkit/build-optimizer      0.6.8
@angular-devkit/core                        0.6.8
@angular-devkit/schematics            0.6.8
@angular/cli                                       6.0.8
@angular/language-service              5.2.11
@ngtools/webpack                            6.0.8
@schematics/angular                        0.6.8
@schematics/update                         0.6.8
rxjs                                                    6.2.1
typescript                                         2.7.2
webpack                                          4.16.0

Repro steps

Open an existing project
Update Angular 5 to Angular 6
Try to run the app, and get this error message :
404 Not Found

The log given by the failure

404 Not Found
Mention any other details that might be useful
I tried updating my project using the following commands
npm cache verify
npm i -g @angular/cli@latest
npm i @angular/cli@latest
npm install
ng update
Abnormal Behaviour

Running ng update command again and again, shows that it marks absent one of the many dependencies randomly.

Anyone?

We are not able to determine what is going on here with the information provided, please provide either a link to the repo or at least your angular.json file

#11684 Angular.json
``{
"$schema"<EMAIL_ADDRESS>"version": 1,
"newProjectRoot": "projects",
"projects": {
"dice-ui-cli": {
"root": "",
"sourceRoot": "src",
"projectType": "application",
"prefix": "app",
"schematics": {},
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:browser",
"options": {
"outputPath": "dist/dice-ui-cli",
"index": "src/index.html",
"main": "src/main.ts",
"polyfills": "src/polyfills.ts",
"tsConfig": "src/tsconfig.app.json",
"assets": [
"src/favicon.ico",
"src/assets"
],
"styles": [
"src/styles.css"
],
"scripts": []
},
"configurations": {
"production": {
"fileReplacements": [
{
"replace": "src/environments/environment.ts",
"with": "src/environments/environment.prod.ts"
}
],
"optimization": true,
"outputHashing": "all",
"sourceMap": false,
"extractCss": true,
"namedChunks": false,
"aot": true,
"extractLicenses": true,
"vendorChunk": false,
"buildOptimizer": true
}
}
},
"serve": {
"builder": "@angular-devkit/build-angular:dev-server",
"options": {
"browserTarget": "dice-ui-cli:build"
},
"configurations": {
"production": {
"browserTarget": "dice-ui-cli:build:production"
}
}
},
"extract-i18n": {
"builder": "@angular-devkit/build-angular:extract-i18n",
"options": {
"browserTarget": "dice-ui-cli:build"
}
},
"test": {
"builder": "@angular-devkit/build-angular:karma",
"options": {
"main": "src/test.ts",
"polyfills": "src/polyfills.ts",
"tsConfig": "src/tsconfig.spec.json",
"karmaConfig": "src/karma.conf.js",
"styles": [
"src/styles.css"
],
"scripts": [],
"assets": [
"src/favicon.ico",
"src/assets"
]
}
},
"lint": {
"builder": "@angular-devkit/build-angular:tslint",
"options": {
"tsConfig": [
"src/tsconfig.app.json",
"src/tsconfig.spec.json"
],
"exclude": [
"/node_modules/"
]
}
}
}
},
"dice-ui-cli-e2e": {
"root": "e2e/",
"projectType": "application",
"architect": {
"e2e": {
"builder": "@angular-devkit/build-angular:protractor",
"options": {
"protractorConfig": "e2e/protractor.conf.js",
"devServerTarget": "dice-ui-cli:serve"
},
"configurations": {
"production": {
"devServerTarget": "dice-ui-cli:serve:production"
}
}
},
"lint": {
"builder": "@angular-devkit/build-angular:tslint",
"options": {
"tsConfig": "e2e/tsconfig.e2e.json",
"exclude": [
"/node_modules/"
]
}
}
}
}
},
"defaultProject": "dice-ui-cli"
}''
I think there is a problem with schematics, not being able to recursively recognize already installed packages.
Problem persists after creating new applications also while doing ng update

Any update on this?

I'm sorry, but we can't reproduce the problem following the instructions you provided.
Remember that we have a large number of issues to resolve, and have only a limited amount of time to reproduce your issue.
Short, explicit instructions make it much more likely we'll be able to reproduce the problem so we can fix it.
If the problem persists, please open a new issue following our submission guidelines.
A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

logs/2018-12-13T15_08_07_329Z-debug.log
11 verbose stack     at Immediate.Async.drainQueues [as _onImmediate] (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
11 verbose stack     at processImmediate (timers.js:632:19)
12 verbose cwd /Users/rjoseph/workspace/iornics/myApp
13 verbose Darwin 18.2.0
14 verbose argv "/usr/local/Cellar/node/11.3.0_1/bin/node" "/usr/local/bin/npm" "install" "-g" "@angular/angular-cli"
15 verbose node v11.4.0
16 verbose npm  v6.4.1
17 error code E404
18 error 404 Not Found: @angular/angular-cli@latest
19 verbose exit [ 1, true ]

gyp ERR! node -v v11.4.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/Cellar/node/11.3.0_1/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js clean' (1)
node-pre-gyp ERR! stack     at ChildProcess. (/usr/local/Cellar/node/11.3.0_1/lib/node_modules/@angular/cli/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:189:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:978:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
node-pre-gyp ERR! System Darwin 18.2.0
node-pre-gyp ERR! command "/usr/local/Cellar/node/11.3.0_1/bin/node" "/usr/local/Cellar/node/11.3.0_1/lib/node_modules/@angular/cli/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /usr/local/Cellar/node/11.3.0_1/lib/node_modules/@angular/cli/node_modules/fsevents
node-pre-gyp ERR! node -v v11.4.0
node-pre-gyp ERR! node-pre-gyp -v v0.10.0
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/Cellar/node/11.3.0_1/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js clean' (1)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@angular/cli/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>install: node install
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1


Pair Programming

Implementing a Pair Programming Feature with a text file for #237

@tonybaloney this pull request should be ready for a review.

File imports will be another blocker to #276 in which browser extensions cannot support the fs module.
Please have a look at https://www.npmjs.com/package/vsls with example https://marketplace.visualstudio.com/items?itemName=lostintangent.vsls-whiteboard as APIs for sharing information inside a VS Code live share.

Codecov Report

Merging #308 (9f23dc6) into master (cee543c) will decrease coverage by 2.28%.
The diff coverage is n/a.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I can use vscode's built in file system. Does that work in the browser?

File imports will be another blocker to #276 in which browser extensions cannot support the fs module.
Please have a look at https://www.npmjs.com/package/vsls with example https://marketplace.visualstudio.com/items?itemName=lostintangent.vsls-whiteboard as APIs for sharing information inside a VS Code live share.

Does vscode's built in file system work in the browser?

I've made a couple of changes:

The exported files are JSON instead of the text format. The array type was already serializable and now it'll handle the formatting issues
The input colour is validated to avoid the mystery pet bug
The exported file uses the "untitled" protocol which opens it in a tab in VS Code ready to save, but without having saved the files so the user can rename it
The exported file name has  a unique-ish number in it to avoid collision
The import action uses the open file dialog so the user can pick the file, instead of assuming it's named a certain way and inside the workspace (since the workspace might be a project they're working on and nothing to do with pets).

@tonybaloney thank you


Reevaluate the restriction that a given user can only have the same synced URL open once

SyncUser::register_session currently enforces a restriction that a given user can only have the same synced URL open once. There are plausible use cases where a user would have the same synced URL open at multiple, different local paths. I'm not aware of a reason for the restriction to exist.
@mrackwitz is running into this restriction in realm/realm-js#679, which was masked by the deadlock fixed in #242.
/cc @austinzheng

The most straightforward way to fix this is to have SyncUser store sessions based on their local path, not on their URL. We may or may not be able to replace SyncUser's map member variables with calls to SyncManager, since SyncManager also stores sessions based on local path. We can then leave it up to the bindings if they want to provide a feature to map URLs to sessions.

@mrackwitz, is this ticket blocking client permissions?

Not directly, it is only breaking the integration test on realm-sync-services (& realm-js). For now we can probably just disable this test.


Allowing sql highlighting

This currently doesn't work in jupyterlab.
We should tackle this issue to make the code more readable for users.

I did some research on this a while ago. It's pretty complex to add support to syntax highlighting in the current version of JupyterLab. I remember reading this it is possible installing the language protocol, and that the upcoming major release will simplify things; but still worth investigating and summarizing what's the status now.

Here's a link with more information. tl;dr; it isn't trivial to bring back syntax color to JupyterLab. The answer suggests using an external package that implements language server protocol. We could add a guide to our docs.

I agree on the original issue. but I think #43 is for the syntax, this issue was more to color the result cell, you don't think it's a valuable feature?

closing in favor of https://github.com/ploomber/jupysql/issues/6


FlipView animation not working when SelectionIndex is changed by more than 1

Describe the bug
Currently, <FlipView /> won't play flip animation when its index is changed by more than 1. Only adjacent items animation is working.
Steps to reproduce the bug

Open WinUI 3 Gallery (latest MS Store version)
Go to Scrolling > PipsPager
Click on Middle dot at PipsPager control in PipsPager integrated with a FlipView sample

Expected behavior
Since <FlipView /> is just a <ScrollViewer /> with <ItemsPresenter /> inside of it, I don't see any reason it wouldn't play animation when its index is changed by more than 1.
Screenshots
This behavior in WinUI 3 Gallery (Windows App SDK 1.5)
https://github.com/microsoft/microsoft-ui-xaml/assets/42270214/8989f70b-13a4-4204-866b-9f9ccf09b1fa
NuGet package version
WinUI 3 - Windows App SDK 1.5.1: 1.5.240311000
Windows version
Windows 11 (22H2): Build 22621
Additional context
If somebody could point me to the code responsible for <FlipView /> scrolling, I'd be glad to try to fix it myself and submit a PR.

@bpulliam Why is this area-PipsPager? It's clearly about FlipView, because SelectionIndex can be controlled by everything, even by ListView...


Consider using easy-peasy on top of Redux

Redux is great!
But.. it's very verbose IMO, and tends to lead to a lot of boilerplating with actions, actionCreators, reducers, HoC's for connecting state etc.
easy-peasy is an abstraction over redux which provdes a more consise API for setting up actions, uses hooks instead of connect while maintaining the great aspects of Redux such as performant global state, stateful hot reloading (I think), redux dev tools etc.
Let's check it out

Hi, I'm back. I recommend redux toolkit


USHIFT-4336: Implement embedded container build support in bootc tests

Which issue(s) this PR addresses:

Closes #

Everything seems to be working fine, except the router pod that fails to start with the following error.
[pod/router-default-74c8bbb85b-fs5bw/router] I0913 13:09:11.500833       1 router.go:537] "msg"=
"calling reload function" "fn"=0 "logger"="template"
[pod/router-default-74c8bbb85b-fs5bw/router] E0913 13:09:11.501025       1 haproxy.go:418] can't
 scrape HAProxy: dial unix /var/lib/haproxy/run/haproxy.sock: connect: no such file or directory
[pod/router-default-74c8bbb85b-fs5bw/router] I0913 13:09:11.501047       1 router.go:541] "msg"=
"reloading the router" "logger"="template"
[pod/router-default-74c8bbb85b-fs5bw/router] E0913 13:09:11.522860       1 limiter.go:165] error
 reloading router: exit status 1
[pod/router-default-74c8bbb85b-fs5bw/router] [NOTICE]   (9) : haproxy version is 2.8.10-f28885f
[pod/router-default-74c8bbb85b-fs5bw/router] [NOTICE]   (9) : path to executable is /usr/sbin/ha
proxy
[pod/router-default-74c8bbb85b-fs5bw/router] [ALERT]    (9) : Binding [/var/lib/haproxy/conf/hap
roxy.config:63] for frontend public: cannot bind socket (Permission denied) for [<IP_ADDRESS>:80]
[pod/router-default-74c8bbb85b-fs5bw/router] [ALERT]    (9) : Binding [/var/lib/haproxy/conf/hap
roxy.config:98] for frontend public_ssl: cannot bind socket (Permission denied) for [<IP_ADDRESS>:443
]
[pod/router-default-74c8bbb85b-fs5bw/router] [ALERT]    (9) : [/usr/sbin/haproxy.main()] Some pr
otocols failed to start their listeners! Exiting.

/test ?

/test metal-bootc-periodic-test-arm

/test metal-bootc-periodic-test

/test metal-bootc-periodic-test

/test metal-bootc-periodic-test-arm
/test metal-bootc-periodic-test

/test verify

/test metal-bootc-periodic-test
/test metal-bootc-periodic-test-arm
/test verify

The isolated container builds exhibit failures. Asked about it in the PBI tracker issue.
STEP 1/14: FROM localhost/cos9-bootc-source:latest
STEP 2/14: RUN --mount=type=secret,id=pullsecret,dst=/run/secrets/pull-secret.json     podman pull     --authfile /run/secrets/pull-secret.json     --root=/var/lib/containers/storage-preloaded     "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0c12ddea1c28a7287700c19e623c4bf66ce9931a6b8a8c882fd80204393996c6"
time="2024-09-17T13:05:47Z" level=warning msg="\"/\" is not a shared mount, this could cause issues or missing mounts with rootless containers"
Trying to pull quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0c12ddea1c28a7287700c19e623c4bf66ce9931a6b8a8c882fd80204393996c6...
Getting image source signatures
Copying blob sha256:4f05dc73d94cbbd0cd91587184e671ba4112087f93f86139ebdcb3afa3b1aae7
Copying blob sha256:d8e5548c38deb03c17871de35e63257444e05109754c25725185b8bf2630cfce
Copying blob sha256:0ea779877a0c9ea774298c27e45ffa6589e7b157fef28dad9d6869859cf8077f
Copying blob sha256:abced7ee58448ba09b150b6a5d0083ceb67e2e834226c951cc0c678891596db9
Copying config sha256:fd1a10b5a8443d0436fb6447b24b6aee75848995909962aa1c681e5942c70a72
Writing manifest to image destination
fd1a10b5a8443d0436fb6447b24b6aee75848995909962aa1c681e5942c70a72
--> 79b9daa6d479
STEP 3/14: RUN --mount=type=secret,id=pullsecret,dst=/run/secrets/pull-secret.json     podman pull     --authfile /run/secrets/pull-secret.json     --root=/var/lib/containers/storage-preloaded     "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:69219ccc460d06c01cfbbf5617795ed28eb3834704af811e8bf3469ace763bd3"
cannot set user namespace

/test metal-bootc-periodic-test-arm

/test e2e-aws-tests-bootc-periodic

/test e2e-aws-tests-bootc-periodic e2e-aws-tests-bootc-periodic-arm
/test verify

@pacevedom , I updated the code to use skopeo copy instead of podman pull and it seems to be more stable during builds. PTAL.

/test e2e-aws-tests-bootc-periodic-arm

Overriding the test as its failures have nothing to do with the current change.
/override ci/prow/e2e-aws-tests-bootc-periodic-arm

/lgtm cancel

/test metal-bootc-periodic-test metal-bootc-periodic-test-arm

/test e2e-aws-tests-bootc-periodic
/test e2e-aws-tests-bootc-periodic-arm

/test e2e-aws-tests-bootc-periodic
/test e2e-aws-tests-bootc-periodic-arm

/test all

/test metal-bootc-periodic-test-arm
/test metal-bootc-periodic-test

/test e2e-aws-tests-bootc-periodic
/test e2e-aws-tests-bootc-periodic-arm

/test e2e-aws-tests-bootc-periodic
/test e2e-aws-tests-bootc-periodic-arm

/test e2e-aws-tests-bootc-periodic
/test e2e-aws-tests-bootc-periodic-arm

Now that we have VM install retry-on-error fix merged, let's see the results. https://github.com/openshift/microshift/pull/3953
/test e2e-aws-tests-bootc-periodic
/test e2e-aws-tests-bootc-periodic-arm
P.S. There might still be errors due to https://github.com/openshift/microshift/pull/3952


(Question) Use a restream.io Server instead of build in Nginx/Node

First of All, this is a awesone piece of Software. Totally love it. The reason of my question is: I try to stream a gopro hero8 stream to noalbs on a dedicated Streaming PC at home. With node as the rtmp server. This works absolutly great, until I use my 4g Internet. The Hero won't Connect to the rtmp URL. The strange thing is, streamlabs for Android does. I can stream to the noalbs server with the ddns address just fine. And every other rtmp Server will work just fine with the gopro app. Only my ddns rtmp adress of the noalbs server won't connect through the gopro app. 1935 is opened.
That takes me to my question: if I use restream.io to stream to from the gopro app, can I use this restream server and monitor it, instead of the build in rtmp server? I know there are some api codes for restream, but can I get this to work like this?
I've done tests the last 3 days, why the gopro app won't stream to my ddns address, but can't figured it out.
Gopro app > 4g > reastream > worked
Gopro app > 4g > ddns Adress of noalb > don't work
Gopro app > local > ddns Adresse of noalb > worked
Streamlabs app > 4g > ddns address of noalb > worked
Gopro app > 4g to home VPN server > ddns Adresse of noalb > won't work
It drive me nuts, because for this I buy this hero8. My hero5 don't support streaming  :/
Any ideas?

So you want to use a different RTMP endpoint other than NGINX or NMS that's built-in to NOALBS correct? If so check out www.norip.io, or if restream can stream to a custom RTMP have it point to your RTMP server at home?

correct.
was thinking about some rtmp to rtmp at home route but was hoping i can get the stats from the restream rtmp stream to use in noalbs on my end. actually i messing around with a vpn. 4g to vpn on my synology nas > noalbs on my streaming pc.
so there is no way to get the endpoint infos from restream and work with it in noalbs?
restream can indeed point to a custom rtmp, but only with a subscribtion. for free, it can only stream to twitch/facebook/yt e.t.c. and im planning to stream this only ~2 times a month. so thats a little bit op i think ;)


Fails to serialize categories with icalendar 4.0.3

Running icalendar 4.0.3 and todoman 3.5.0 I get lots of errors like this when adding new files:
Failed to read entry /home/jelmer/.calendars/jelmer/foss/BLAH.ics.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/todoman/model.py", line 956, in update_cache
    self.cache.add_vtodo(component, entry_path)
  File "/usr/lib/python3/dist-packages/todoman/model.py", line 622, in add_vtodo
    self._serialize_categories(todo, 'categories'),
  File "/usr/lib/python3/dist-packages/todoman/model.py", line 570, in _serialize_categories
    return ','.join([str(category) for category in categories.cats])
AttributeError: 'list' object has no attribute 'cats'

The representation for categories in icalendar has changed in 4.0.3, possibly due to "Categories are comma separated not 1 per line #265. [cleder]" (https://pypi.org/project/icalendar/)

todoman 3.5.0 should work fine with ilcalendar 4.0.3 (support was added in previous versions).
This looks pretty odd; can you provide the output of pip freeze, to confirm these are the actual versions?

I'm running both from their Debian package:
% dpkg -l | grep -e "(icalendar|todoman)"
ii  python3-icalendar                         4.0.3-2                               all          parser/generator of iCalendar files for use with Python3
ii  todoman                                   3.5.0-1                               amd64        Simple CalDAV-based todo manager

I tried to reproduce this on a clean installation of buster:
# apt-get update
...
# apt-get install -y todoman
...
# todo
bash: todo: command not found
# todoman
Traceback (most recent call last):
  File "/usr/bin/todoman", line 6, in <module>
    from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

Looks like there's something broken with the debian package, and it won't work out of the box. I can't further debug this, sorry. You should report this to the debian package maintainers.
FWIW, support for icalendar 4.0.3 was included in todoman 3.5.0. I've just validated that it works as expected by installing todoman on buster via pip. Filtering via categories, etc, works as expected.
This is either a problem with your installation, or with the debian package itself, but, regrettably, the debian package won't work for me, so I can't really look into it.

The todoman binary is called todoman on Debian, to prevent clashes with another package with a binary with the same name in it.
On November 26, 2018 4:44:33 PM UTC, Hugo Osvaldo Barrera<EMAIL_ADDRESS>wrote:

I tried to reproduce this on a clean installation of buster:
# apt-get update
...
# apt-get install -y todoman
...
# todo
bash: todo: command not found
# todoman
Traceback (most recent call last):
 File "/usr/bin/todoman", line 6, in <module>
   from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

Looks like there's something broken with the debian package, and it
won't work out of the box. I can't further debug this, sorry. You
should report this to the debian package maintainers.
FWIW, support for icalendar 4.0.3 was included in todoman 3.5.0. I've
just validated that it works as expected by installing todoman on
buster via pip. Filtering via categories, etc, works as expected.
This is either a problem with your installation, or with the debian
package itself, but, regrettably, the debian package won't work for me,
so I can't really look into it.
--
You are receiving this because you authored the thread.

Traceback (most recent call last):
File "/home/jelmer/.local/lib/python3.7/site-packages/todoman/model.py", line 956, in update_cache
self.cache.add_vtodo(component, entry_path)
File "/home/jelmer/.local/lib/python3.7/site-packages/todoman/model.py", line 622, in add_vtodo
self._serialize_categories(todo, 'categories'),
File "/home/jelmer/.local/lib/python3.7/site-packages/todoman/model.py", line 570, in _serialize_categories
return ','.join([str(category) for category in categories.cats])
AttributeError: 'list' object has no attribute 'cats'
Problematic file:
BEGIN:VCALENDAR
BEGIN:VTODO
CATEGORIES:documentation
CATEGORIES:git
CLASS:PUBLIC
CREATED:20181123T133148Z
DESCRIPTION:blah blah
STATUS:NEEDS-ACTION
SUMMARY:blah blah
UID:some-uid
URL:https://URL/blah
END:VTODO
END:VCALENDAR

More than one category can be included by comma-separating them in a single line. I don't think that having multiple Categories entries in the iCalendar file is valid.
At least that's what's confusing python-icalendar and making it return the wrong type.
Can you try replacing:
CATEGORIES:documentation
CATEGORIES:git

with the following:
CATEGORIES:documentation,git

Huh, I failed to find that reference. So, basically, there are multiple ways to express categories, and icalendar's API changes depending on what's present.
I'll try to address this soon; it'll probably be some ugly hack 🙁

On Mon, Nov 26, 2018 at 12:36:17PM -0800, Hugo Osvaldo Barrera wrote:

Huh, I failed to find that reference. So, basically, there are multiple ways to express categories, and icalendar's API changes depending on what's present.
I'll try to address this soon; it'll probably be some ugly hack 🙁
Yep :( The only reason I know about this is because I ran into the
same issue in Xandikos...

--
Jelmer Vernooĳ<EMAIL_ADDRESS>PGP Key: https://www.jelmer.uk/D729A457.asc

Any update on this? :(


Fix: _syncHandle sometimes causing NPEs in Kotlin / Wasm code

When onHandleSync is updated and there is no model, it causes a NPE error in Kotlin / Wasm code.
This manifests as a runtime error in the browser console and is masked as an abort error.
This PR attempts to fix the issue by taking a more defensive approach. However, I am unsure of the effects it will have on C++ / Wasm code.

The Wasm particles still should be failing the manual tests. I believe that this is due to a collections encoding error. For instance, the following seems malformed:
Handle is 'inputData' syncing '1:111:85:!846534373238833:https://$particles/Tutorial/Kotlin/5_Collections/Collections.arcs::0|name:T4:Jill|age:N70:|'

I presume this is using a Kotlin particle with particles/Tutorial/Javascript/5_Collections/Collections.arcs?
Assuming that, the encoding looks correct. The collection format is <num-entities>:<length>:<encoded><length>:<encoded>...
1:111:85:!846534373238833:https://$particles/Tutorial/Kotlin/5_Collections/Collections.arcs::0|name:T4:Jill|age:N70:|
So num-entities = 1 and length = 111, which matches the length of the remaining string. Then there should be one <encoded> entry (because num-entities = 1). That will be a singleton encoding, which is <id-length>:<id>|<field>:<value>|<field>:<value>|...|.
id-length = 85
id = !846534373238833:https://$particles/Tutorial/Kotlin/5_Collections/Collections.arcs::0
field = 'name'
value = 'T4:Jill' -> Text, length 4, 'Jill'
field = 'age'
value = 'N70' -> Number, 70

@mykmartin Found the issue -- the kotlinic syntax iterated one too many times.

Cool, will merge after build passes.


FOR-24: Implement survey display logic for Web SDK

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add optimization hints for checking slices

Similar to how rkyv now has a CopyOptimization associated constant in its Archive trait, bytecheck can support skipping checking a slice of types if the type has its optimization hint enabled.

The compiler is already able to optimize these out. This seems to be a different case compared to Archive since the optimization is very "natural".


React Native IOS app startCallComposite Localization is in Hebrew and cannot change language

Hi! I am working on an app adding videocall, I can successfully start the calls but on IOS I cannot change the language. By default use Hebrew language and I do not know why. I tried to modify the swift files inside pods but I could not find where it is getting the languages.
Versions:
'AzureCommunicationUICalling', '1.9.0'
"react": "18.2.0",
"react-native": "0.72.2",
If anyone needs help for implementing this library I am free to help. This is a very powerful library and, once learn how to use it, very easy to add into an App

Hi Jeronimo,
It sounds like you're encountering an issue with the localization behavior of the AzureCommunicationUICalling SDK on iOS. By default, the SDK applies the locale based on the device's settings, which might be why it's defaulting to Hebrew in your case.
To modify the language, you don't need to edit the Swift files directly inside the pods. Instead, you can use the SDK's localization APIs to set the desired language programmatically. You can refer to the official documentation on localization here for more detailed guidance.
If you still need help or if there's a specific part of the implementation that’s unclear, feel free to ask.

Hi! I will try this. I am working on another task, but already set another in the board to investigate.
What I found strange is that on Android every thing works perfect, if I change the language inside the startCallComposite, it works find. I almost can see all the languages using the method getSupportedLocales() on Android, but on IOS just give an array with "en".
This is my startCallComposite:
 try {       await RNAzureCommunicationUICalling.startCallComposite(         // local options         { "displayName": "token1", "title": "token1", "subtitle": "token1", "disableLeaveCallConfirmation": false },         // localAvatarImageResource         null,         // remote options         { "token": token1, "meeting": "${groupId-uuid}" },         // remoteAvatarImageResource         null,         // localization options         { "locale": "it", "layout": false },         // orientationOptions         { "setupOrientation": "PORTRAIT", "callOrientation": "PORTRAIT" }       )     } catch (error) {       console.error(error.message)     }
If I set the locale to "it", on Android change but on IOS still in Hebrew "he"
  try {         const locales = await RNAzureCommunicationUICalling.getSupportedLocales()         console.log(locales)       } catch (error) {         console.error(error)       }
And this method on Android give me an array with all the languages, but on IOS give me an array with just "en", but do not work either in English, still Hebrew.
I will investigate, thanks! If I find a solution, I will give more information (Sorry about my english, I am from Argentina)

Hi Jeronimo,
We've done some investigations on our side and have not as of yet been able to reproduce this issue.
Can you give more details about the devices used for testing? Is it only one iPhone? Simulator?
Are the bindings/samples being used without modification?
Can you tell me what is available in iOS SupportedLocale.values field?
Are you using this file for your bindings in a unmodified way?
https://github.com/Azure-Samples/communication-services-ui-library-react-native/blob/main/demo/ios/RNAzureCommunicationUICalling.swift
Please let us know if you have any more information.

Hi! Sorry about the late answer.  I still working on another task but next one is VideoCall
This error is on phisic iPhone and simulator iphone too ( I tried 15, 15pro, 14 ). Reading the doc I found this method who give us all the locales
try {         const locales = await RNAzureCommunicationUICalling.getSupportedLocales()         console.log(locales)       } catch (error) {         console.error(error)       }
Output iOS => ["en"]
Output Android => ["ar", "ar", "de", "de", "en", "en", "en", "es", "es", "fi", "fi", "fr", "fr", "it", "it", "iw", "ja", "ja", "ko", "ko", "nb", "nl", "nl", "pl", "pl", "pt", "pt", "ru", "ru", "sv", "tr", "tr", "zh", "zh", "zh"]
The wear thing is on iOS said "en" as default but i see in hebrew. I am working for Italy so for now I modify the hebrew file with Italian. I found the locales and I just copy-paste the Italian language into the Hebrew. Just for keep going on in project.
I saw some updates and new commits that I must try. Maybe someone find a solution. Let me know if I can help with something else. Thanks!

Hi @JeronimoGarciaBielsa
If you run this sample App you should be able to see list of localizations in the Settings. This list is populated using const locals = await RNAzureCommunicationUICalling?.getSupportedLocales();:


RulesEngine

RulesEngine has fireRules() method. Is there a way to fire individual rule like fireRule(rulename)? I probably could just registerRule before calling fireRules and unregisterRule after execution, but I'd prefer to keep all rules registered and fire as needed.

Is there a way to fire individual rule like fireRule(rulename)

No, not yet. You can indeed register only one rule and fire it.
In next major version, we will have a RuleSet API in which you can register only one rule and then fire the rule set. Something like:
RuleSet ruleSet = new RuleSet();
ruleSet.register(new MyRule());

RulesEngine rulesEngine = new InferenceRulesEngine(); // there will be multiple implementation (inference, backward chaining, rete, etc).

rulesEngine.fire(ruleSet);

Thanks, can you tell when the v3 is expected?

Unfortunately no, but I'm planning to start working on v3 in the next few weeks.
I will let you know when the first snapshot is deployed in order to give it a try if you want.
Kind regards

Great, appreciate it!

Hi @OlegJava
I'm closing this issue for now, stay tuned for v3 !
Kr
Mahmoud


Radio inputs break out of .form-contol containers when using floating labels

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
When using multiple radio inputs inside a .form-control div and using floating labels, the radio inputs will break out of form-contol div.
This can be solved by this change:
.form-floating > .form-control {
    height: fit-content;
}

Reduced test cases
https://codepen.io/mimmi20/pen/JjzYYrV
https://codepen.io/mimmi20/pen/ExMVZrJ - with validation
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Opera
What version of Bootstrap are you using?
5.3.2

Checking the source code and examples, it looks like the form-control class is intended to be assigned to the input elements instead of being a wrapper for them.
If you need a border around them, I'd consider using a combination of card with padding or a card-body inner element.

I dont want just a border around the checkboxes and radios. I also want to use floating labels and form validation (I added a second examle for that, but that includes more changes, which are not part of this ticket).
If this way handling radio inputs or checkboxes with floating labels is not intended, I would like have examples in the documentation for that.

hey! @mimmi20 , I'm a new contributer , can I get to know what exactly do you want. For example , if you just want to fix the radio inputs break out, you can add a size specifier such as mb-3 in the form check label tag. It will then look like the image i've attached. I just wanted to know if you wanted to fix that other than the fixes in the documentation.

Really sorry ,if I've misunderstood the issue , I'm just a newbie figuring out here :')

hey! @mimmi20 , I'm a new contributer , can I get to know what exactly do you want. For example , if you just want to fix the radio inputs break out, you can add a size specifier such as mb-3 in the form check label tag. It will then look like the image i've attached. I just wanted to know if you wanted to fix that other than the fixes in the documentation.

As you can see, there are two radio inputs. The second one is breaking out of .form-contol container. The reason is simple, that the .form-control in combination with .form-floating has a fixed height.

hey! @mimmi20 , I'm a new contributer , can I get to know what exactly do you want. For example , if you just want to fix the radio inputs break out, you can add a size specifier such as mb-3 in the form check label tag. It will then look like the image i've attached. I just wanted to know if you wanted to fix that other than the fixes in the documentation.

As you can see, there are two radio inputs. The second one is breaking out of .form-contol container. The reason is simple, that the .form-control in combination with .form-floating has a fixed height.
The result should look like in this pen

Oh! Gotcha. Thanks for clearing this out. This should definitely be added into the documentation.

We don't support radio inputs on floating forms.


Confusing error message for NULLable fields

Hello!
When (wrongly) trying to scan a NULL value into a non-pointer type, pgxscan gives me an error like so:
can't scan into dest[18]: cannot assign NULL to *float64
The context for the call:
type MyStruct struct {
	...
	ProblemField       float64   // 18th field
	...
}

// Called with address of a MyStruct
func GetMyStruct(ctx context.Context, dest interface{}, someID uint32) error {
	err := pgxscan.Get(ctx, db, dest,
		sqlQuery, // Query has a outer join hence the NULLable fields
		someID,
	)
	return err
}

I believe the error message should read can't scan into dest[18]: cannot assign NULL to float64 instead since the issue would be solved by having a pointer type. (The same type of error message happens in https://github.com/georgysavva/scany/issues/36.)
Thanks for taking a look!

Hello!
This error message cannot assign NULL to *float64 comes from pgx library. It says *float64 because for field ProblemField       float64 scany takes a reference and passes it as &MyStruct.ProblemField since otherwise, pgx wouldn't be able to mutate it. So pgx does receive *float64 type, not float64.
For NULLable fields you need to define them like ProblemField *float64 and pgx will receive **float64 (double pointer) and if something would go wrong it would return an error like that: cannot assign "something" to **float64, because now pgx indeed received **float64.
I hope it helps!

Ah yes, the struct getting passed by reference clears up the message meaning. @georgysavva thank you!


[EN] Deep learning cheetsheet. Possible typo?

Shouldn't line:
39. Remark: we say that we execute a given policy π if given a state a we take the action a=π(s).
be:
39. Remark: we say that we execute a given policy π if given a state s we take the action a=π(s).

Good catch, thank you Michal!


fastlane archive failed with method_missing

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I am trying to build my iOS App with Fastlane, but fails with method_missing.
Command executed
build_app(
    workspace: "token.xcworkspace",
    scheme: "token",
    export_method: "ad-hoc"
)

Complete output when running fastlane, including the stack trace and command used

/opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane_core/lib/fastlane_core/ui/interface.rb:163:in `build_failure!': \e[31m[!] Error building the application - see the log above\e[0m (FastlaneCore::Interface::FastlaneBuildFailure)
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/error_handler.rb:73:in `handle_build_error'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/runner.rb:114:in `block in build_app'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane_core/lib/fastlane_core/command_executor.rb:84:in `execute'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/runner.rb:110:in `build_app'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/runner.rb:18:in `run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/manager.rb:19:in `work'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/actions/build_app.rb:68:in `run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	from Fastfile:42:in `block (2 levels) in parsing_binding'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/commands_generator.rb:109:in `block (2 levels) in run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/commands_generator.rb:353:in `run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in `take_off'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/bin/fastlane:23:in `'
	from /opt/homebrew/opt/rbenv/versions/3.0.3/bin/fastlane:25:in `load'
	from /opt/homebrew/opt/rbenv/versions/3.0.3/bin/fastlane:25:in `'
/opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane_core/lib/fastlane_core/ui/interface.rb:163:in `build_failure!': Error building the application - see the log above (FastlaneCore::Interface::FastlaneBuildFailure)
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/error_handler.rb:73:in `handle_build_error'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/runner.rb:114:in `block in build_app'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane_core/lib/fastlane_core/command_executor.rb:84:in `execute'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/runner.rb:110:in `build_app'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/runner.rb:18:in `run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/gym/lib/gym/manager.rb:19:in `work'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/actions/build_app.rb:68:in `run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	from Fastfile:42:in `block (2 levels) in parsing_binding'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/commands_generator.rb:109:in `block (2 levels) in run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/commands_generator.rb:353:in `run'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in `take_off'
	from /opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib/ruby/gems/3.0.0/gems/fastlane-2.203.0/bin/fastlane:23:in `'
	from /opt/homebrew/opt/rbenv/versions/3.0.3/bin/fastlane:25:in `load'
	from /opt/homebrew/opt/rbenv/versions/3.0.3/bin/fastlane:25:in `'

Environment

swift-driver version: 1.26.21 ✅ fastlane environment ✅
Stack

Key
Value

OS
12.0.1

Ruby
3.0.3

Bundler?
false

Git
git version 2.31.1

Installation Source
/opt/homebrew/opt/rbenv/versions/3.0.3/bin/fastlane

Host
macOS 12.0.1 (21A559)

Ruby Lib Dir
/opt/homebrew/Cellar/rbenv/1.2.0/versions/3.0.3/lib

OpenSSL Version
OpenSSL 1.1.1m  14 Dec 2021

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
13.2.1

Swift Version
5.5.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  desc "upload to fir.im"
  lane :fir do
    build_app(
      workspace: "token.xcworkspace",
      scheme: "token",
      export_method: "ad-hoc"
    )
    firim(
      firim_api_token: "",
      app_changelog: changelog,
      firim_api_url: "https://api.bq04.com"
    )
  end

end

`./fastlane/Appfile`
app_identifier "im.xxxx.app" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

itc_team_id "xxxx" # iTunes Connect Team ID
team_id "xxxx" # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.203.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-versioning
0.5.0
✅ Up-To-Date

fastlane-plugin-firim
0.2.2
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.5.0

atomos
0.1.3

rexml
3.2.5

CFPropertyList
3.0.5

claide
1.0.3

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.21.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

plist
3.6.0

public_suffix
4.0.6

addressable
2.8.0

multipart-post
2.0.0

word_wrap
1.0.0

optparse
0.1.1

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

babosa
1.0.4

colored
1.2

highline
2.0.3

commander
4.6.0

excon
0.89.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

faraday-multipart
1.0.3

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.9.3

unf_ext
0.0.8

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.4

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

json
2.5.1

mini_magick
4.11.0

naturally
2.2.1

rubyzip
2.3.2

security
0.1.3

xcpretty-travis-formatter
1.0.1

dotenv
2.7.6

simctl
1.6.8

jwt
2.3.0

uber
0.1.0

declarative
0.0.20

trailblazer-option
0.1.2

representable
3.1.1

retriable
3.1.2

mini_mime
1.1.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.16.0

googleauth
1.1.0

httpclient
2.8.3

webrick
1.7.0

google-apis-core
0.4.1

google-apis-playcustomapp_v1
0.7.0

google-apis-androidpublisher_v3
0.15.0

google-cloud-env
1.5.0

google-cloud-errors
1.2.0

google-cloud-core
1.6.0

google-apis-iamcredentials_v1
0.10.0

google-apis-storage_v1
0.11.0

rake
13.0.3

digest-crc
0.6.4

google-cloud-storage
1.35.0

emoji_regex
3.2.3

jmespath
1.5.0

aws-partitions
1.547.0

aws-eventstream
1.2.0

aws-sigv4
1.4.0

aws-sdk-core
3.125.2

aws-sdk-kms
1.53.0

aws-sdk-s3
1.111.1

set
1.0.1

bundler
2.3.4

forwardable
1.3.2

logger
1.4.3

pathname
0.1.0

shellwords
0.1.0

cgi
0.2.1

date
3.1.3

timeout
0.1.1

stringio
3.0.1

securerandom
0.1.0

uri
0.10.1

ipaddr
1.2.2

openssl
2.2.1

digest
3.0.0

io-nonblock
0.1.0

io-wait
0.2.0

zlib
2.0.0

resolv
0.2.1

time
0.1.0

open-uri
0.1.0

mutex_m
0.1.1

net-protocol
0.1.1

ostruct
0.3.1

english
0.7.1

erb
2.2.0

strscan
3.0.1

abbrev
0.1.0

io-console
0.5.7

tempfile
0.1.1

delegate
0.2.0

fileutils
1.5.0

tmpdir
0.1.2

base64
0.1.0

singleton
0.1.1

net-http
0.1.1

open3
0.1.1

nkf
0.1.0

prettyprint
0.1.1

pp
0.2.1

find
0.1.0

yaml
0.1.1

psych
3.3.2

fastlane-plugin-versioning
0.5.0

firim
0.2.7

fastlane-plugin-firim
0.2.2

generated on: 2022-01-28

The problem that you have is probably because of wrong code signing settings. Without more logs the community won't be able to help you. It is explicitly written in logs that you pasted  "Error building the application - see the log above", so the problem is described higher in logs. I can advise you that you check if you can build and export app properly from Xcode. You could also take a look at http://docs.fastlane.tools/actions/update_project_provisioning and use it before build_app

I can build and export app properly from Xcode but can't from Fastlane, I will check the http://docs.fastlane.tools/actions/update_project_provisioning

Thank you so much to sharing this post.

I was building it and haven't faced this issue but good to know this thanks for sharing.

Thank you for sharing your valuable solution, it's work properly.


107 invalid links 500, while all headers are 200 ok

i have checked my website https://bit.ly/2Zf24uy internal links with chrome extension check my links but its showing all links as red invalid links (http 500 error). but when i visit my page its showing no error but when i click on 500 links which tool showing it show 500 page. please help me i am tired to use wordpress again and again i have fresh install wordpress and reenter data Manually. but still errors.

This is a rate limiting issue #57.


Quickstart documentation

I felt the quickstart page of tstrait is too brief (https://tskit.dev/tstrait/docs/stable/quick-start.html).
Instead, I think it should be more comprehensive like msprime (https://tskit.dev/msprime/docs/stable/quickstart.html), such that users can just look at the quickstart page to use the sim_phenotype function.

This issue will be closed, aas we had added more examples to the quickstart page in https://github.com/tskit-dev/tstrait/pull/130


Add basic page and file migrations

Summary
This adds a new ecms_migration module that will take a google sheet of urls and create basic pages and file/media entities from those URLS.
Metadata

Question
Answer

Did you use a meaningful pull request title?
yes

Did you apply meaningful labels to the pull request?
yes

Did you perform a self review first?
yes

Documentation reflects changes?
yes

CHANGELOG reflects changes?
yes

Unit/Functional tests reflect changes?
yes (mostly)

Did you perform browser testing?
yes

Risk level
Low

Relevant links
RIG-106

@ben-hamelin, I've addressed all of the QA fixes.

Looks great!
/approved


SSL_CTX_use_PrivateKey() fails to report mismatch with certificate

Quoth the man page:
       SSL_CTX_use_PrivateKey() adds pkey as private key to ctx.
       SSL_CTX_use_RSAPrivateKey() adds the private key rsa of type RSA to
       ctx. SSL_use_PrivateKey() adds pkey as private key to ssl;
       SSL_use_RSAPrivateKey() adds rsa as private key of type RSA to ssl.  If
       a certificate has already been set and the private does not belong to
       the certificate an error is returned. To change a certificate, private
       key pair the new certificate needs to be set with SSL_use_certificate()
       or SSL_CTX_use_certificate() before setting the private key with
       SSL_CTX_use_PrivateKey() or SSL_use_PrivateKey().

So if I add a certificate, and a private key that doesn't belong to the certificate, I'm supposed to get an error. Simple...
Except it doesn't seem to work like that. My torture test suite contains RSA, DSA and EC keys (and certs). If I load one cert and a different key, it seems to silently accept that, then just neglect to do any client cert auth on the wire without ever telling me.

It looks like applications need to explicitly call SSL_CTX_check_private_key() to check for the classes of mismatch which SSL_CTX_use_PrivateKey() doesn't report, if they want to behave well and report errors coherently to their users? Fixed in my application thus but the documentation still wants fixing.

This is not a new bug in 1.1.1, so removing that milestone.

@t8m In the current master branch, this seems to work as expected—the public key part is correctly compared with the one from the certificate. Additionally, the documentation accurately reflects the actual behavior of the function calls. Either I’m missing something, or this issue is now obsolete.

Yeah, I am closing this now.


interaction with the progress bar (hover over)

Deployed to: http://dev.quranicaudio.com:33029

Deployed to: http://dev.quranicaudio.com:33030


Fix broken HookedSAETransformer demo links

Description
Looks like the HookedSAETransformer.ipynb demo was changed to Hooked_SAE_Transformer.ipynb, also I forgot to change the branch name. This PR fixes the demo links.
Type of change

[ x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[ x] My changes generate no new warnings
[ x] New and existing unit tests pass locally with my changes
[ x] I have not rewritten tests relating to key interfaces which would affect backward compatibility

My bad. I updated the name to use the same casing as the rest of the demos, and didn't think to check the content of the demo to see if it was referencing the file name. I will make sure to note to keep an eye out for this in the future when similar situations happen. Thanks for making the change, and putting this up.

No worries, thanks for the quick merge!


[Dropdown] Add Clear/Reset Behavior

<select class="ui dropdown">
  <option value="">Gender</option>
  <option value="1">Male</option>
  <option value="0">Female</option>
</select>

Using a regular select dropdown enhanced with Semantic UI, is there currently no way to reset the value to nil? Right now that option gets parsed for the placeholder.
I tried the restore button approach shown in the example, but that only works if you're dealing with a new record that doesn't already have the default set to something else.
Thanks!

Can you create a test case to show the bug or missing behavior?
I'm not sure how $('.dropdown).dropdown('restore defaults'); is failing for you.
http://semantic-ui.com/modules/dropdown.html#restoring-defaults
This JSFiddle shows it working with <select>
http://jsfiddle.net/e2xzj36L/

Sure, here's an example that shows what I meant:
http://jsfiddle.net/6w9xqhfs/1/
I want the ability to reset the select to blank.

I've added .dropdown('clear') and clarified the documentation around .dropdown('restore defaults')
Defaults are values on page load, placeholder is the value that matches (empty string), or set on page load in class default text

Whenever i run $('.dropdown).dropdown('restore defaults'); or $('.dropdown).dropdown('clear');
i get error Error: [$rootScope:inprog] $apply already in progress
Why this is happning? any idea?

Try to wrap it in setTimeout(() => {
$('.dropdown').dropdown('clear');
}, 0); or in AngularJS $timeout(() =>{
$('.dropdown').dropdown('clear');
}, 0)


Fail gracefully for node<4 in react-native-cli (const->var)

const declarations were recently introduced into https://github.com/facebook/react-native/blob/master/react-native-cli/index.js, which runs before any transpilation so needs to be old-school. Replace them with var.
Fixes https://github.com/facebook/react-native/issues/11603

I don't see why this should be necessary. There is an engines key in the package.json of react-native-cli which specifies "node": ">=4". As far as I know even node 4.0.0 supports const declarations.

True, but a check for that is made at the end of 'run' by 'checkNodeVersion', where we fail gracefully with a helpful message if the requirements aren't met. As it is, the script crashes out before we get that far.

This is not the same thing. checkNodeVersion refers to the engines key of the package.json at REACT_NATIVE_PACKAGE_JSON_PATH which is react-native's package.json and not react-native-cli's.
They are the same at the moment but is sure for the time to come?
That aside. If you are correct and react-native-cli should always run to fail gracefully if react-native's node requirements aren't fulfilled. Doesn't that mean that react-native-cli's engines key should be set to an earlier version or get removed?

Sorry, yes you're right - I was jumping to conclusions based on the fact that var is used throughout the rest of the file. https://github.com/facebook/react-native/commit/72b713262fbb84a0606260c4d8879621a3c7f8e7 suggests the CLI deliberately dropped support for node<4 so that we could use newer language features from then on.
The engines key is advisory so I think it's legitimate to install but fail gracefully on older versions. https://github.com/facebook/react-native/issues/11603 demonstrates that the engines config alone isn't enough to make it clear to everyone what the problem is, so I guess the options are:

Retain enough support to fail gracefully (ideally checking against the CLI's engines setting).
Move forward and accept that users of old node versions will get a bad experience  (although note 0.12 is only just leaving LTS). Anyone familiar with ES6 should probably figure out the problem themselves anyway.

(Aside: I guess maybe people are running into this issue because the Getting Started guide doesn't mention that homebrew might need updating)

I think this means @ide's opinion on this could be interesting.

The intent of the version check is to make it really clear and helpful to people running old versions of Node that they are using a too-old version and what they can do to upgrade (moving forward we'll probably require Node 6 soon). The "engines" field in package.json isn't enough since people don't always see the warning message when running npm install since it's buried in other console output.
So what we want to do is have a small JS file that is compatible with ES5 and checks the Node version. This ES5 file then will load other files that rely on modern Node.

small JS file that is compatible with ES5

Assuming you're referring to index.js, I take it you're in favour of this PR @ide?
If so I'm happy to add a note in the comment block indicating that it's intended to stay ES5 compatible. I hesitate because your first reason in https://github.com/facebook/react-native/commit/72b713262fbb84a0606260c4d8879621a3c7f8e7 only really applies if you intend to allow ES6 within  index.js itself, since anything passed on to the local CLI is guarded by checkNodeVersion anyway.

@rh389 Can you add a comment that says this file should be es5 compatible so it can warn about old node versions.

@janicduplessis Done - that ok?

@shergin I guess this got stuck?


Healthcare expenditure/cost of each disease is missing

Healthcare expenditure in India at baseline and under intervention is not reported in Health-GPS results now.
We need to see if healthcare expenditure is calculated inside or outside Health-GPS. If inside Health-GPS, we need to collect data of monetary (financial) cost of each disease in the setting of India.

Message from Maxime:
We discussed this with the local team and other stakeholders while in India. And here are the possible approaches we agreed on:

1st best: using the microdata of NSS Social Consumption and Health survey, round 75 (info here: https://ecostatjk.nic.in/pdf/reports/nss/Health751.pdf) as in the below studies:
o	https://doi.org/10.1093/ntr/ntaa154
o	https://doi.org/10.1136%2Fbmjopen-2017-016990
We should request the microdata from IEG (our Indian partner).
2nd best but simpler and faster: using estimates from WHO NCD costing tool (info here: https://www.ncbi.nlm.nih.gov/books/NBK148602/bin/simplifiedtools-m5.pdf and here: https://www.who.int/tools/onehealth, software here: https://avenirhealth.org/software-onehealth.php).


How to handle release branches, backports etc

It is not uncommon for a project to have release branches for continued development of older releases. For example, your main branch might contain the tags 1.0.0, 1.0.1, 1.1.0 and 2.0.0, representing stable releases of your project. But you also have the branches 1.x and 2.x, where 1.x could contain the additional tags 1.0.2 and 1.1.1, for example. Those releases could have been published after 2.0.0 and will not have their commits on the main branch.
You touch on this subject in this section:

Subsequent Markdown content must be zero or more releases, also referred to as changelog entries. Releases must be sorted latest-first according to Semantic Versioning rules, even if a release with a smaller version was published at a later time. This means that the semantically latest (and hence most important and frequently sought) release is at the top of the changelog. There must be an entry for every new stable release.

So you can sort of imagine a "unified" changelog with all of the releases that has happened, no matter from which branch they originated. This is fully reasonable to me. But I wonder how to handle this in practice? There will be different versions of CHANGELOG.md in the main, 1.x and 2.x branches. Should I make sure that the CHANGELOG.md in main always is the "unified" version of all CHANGELOG.md files, or should such merging happen outside the repository?

https://github.com/vweevers/common-changelog/issues/3 is related, but there is no real advice to be found there.

My view is that people who are interested in an older release line, will have no problems finding that branch and the relevant changelog. But other people (the majority?) who use the release line from main are probably not interested in older release lines and may get confused.
I don't see the point of a unified changelog, and have no idea how that would be managed. It could be painful, for example when a changelog entry links to README.md#new-feature but that New feature header does not exist in the main branch.  This scenario makes sense to me because the changelog is paired with the actual content.


Create with {"microseconds":"fractional"} cause RangeError

The following, according to the current spec, will throw RangeError
let a = new Intl.DurationFormat("en", {"microseconds":"fractional"});

Is that desireable?
The constructor will call
f. Let unitOptions be ? GetDurationUnitOptions(unit, options, style, valueList, digitalBase, prevStyle).
with
GetDurationUnitOptions("years"...)
GetDurationUnitOptions("months"...)
GetDurationUnitOptions("weeks"...)
GetDurationUnitOptions("days"...)
GetDurationUnitOptions("hours"...)
GetDurationUnitOptions("minutes"...)
GetDurationUnitOptions("seconds"...)
then ...
GetDurationUnitOptions("milliseconds", {"microseconds":"fractional"}, "short",
« "long", "short", "narrow", "fractional" » , "numeric", "short")
then ...
GetDurationUnitOptions("microseconds", {"microseconds":"fractional"}, "short",
« "long", "short", "narrow", "fractional" » , "fractional", "short")

then inside GetDurationUnitOptions
after
1. Let style be ? GetOption(options, unit, string, stylesList, undefined).

style is "fractional"
and
2. Let displayDefault be "always".

then after
6. Let display be ? GetOption(options, displayField, string, « "auto", "always" », displayDefault).

display is "always" because displayDefault is "always"
and then
7. If display is "always" and style is "fractional", then
a. Throw a RangeError exception.

will throw.
But is this desired?

The test it will fail
intl402/DurationFormat/prototype/format/mixed-short-and-numeric
@anba @sffc @ben-allen @ryzokuken

I think it will always hit one of the several
1. Set displayDefault to "auto".

Also, "fractional" is spec-internal. It can't be specified in the API. It is always "numeric" in the API.

Also, "fractional" is spec-internal. It can't be specified in the API. It is always "numeric" in the API.

Or not: https://github.com/tc39/proposal-intl-duration-format/issues/196

And in the current spec, all of the following will throw RangeError
let a1 = new Intl.DurationFormat("en", {"milliseconds":"numeric"});
let a2 = new Intl.DurationFormat("en", {"microseconds":"numeric"});
let a3 = new Intl.DurationFormat("en", {"nanoseconds":"numeric"});
let a4 = new Intl.DurationFormat("en", {"milliseconds":"fractional"});
let a5 = new Intl.DurationFormat("en", {"microseconds":"fractional"});
let a6 = new Intl.DurationFormat("en", {"nanoseconds":"fractional"});

a1- a3 will throw RangeError because valuesList for  GetDurationUnitOptions are
« "long", "short", "narrow", "fractional" » for the case of "milliseconds", "microseconds" and "nanoseconds" and that does not contains "numeric" so GetOption will throw RangeError
a4-a6 will throw because Step 7 mentioned above

Fixed by https://github.com/tc39/proposal-intl-duration-format/pull/197


Add Django template syntax compatibility

The mustache support is a really nice feature. It would be great if the HTML beautifier also understood (and indented where required) Django template syntax.
Given the following:
{% extends "foo.html" %}{% block bar %}
{% for  in zulu %}
zulu
{% endfor %}
{% endblock %}

I would expect the output to be:
{% extends "foo.html" %}
{% block bar %}
    {% for  in zulu %}

            zulu

    {% endfor %}
{% endblock %}

Would love to see this feature too!

Django and related languages do not indent yet, but they are now supported in that they are not killed by beautification.

Any method to script this/add manually for project?

I'm also looking for a good solution

@AdrienLemaire @antnieszka @jkevingutierrez
PRs welcome.  If you look at what is don't for mustache and build around it, it should be possible.

It can also be used for liquid templates which use a similar syntax. The only difference is elsif instead of elif.
Full support for these languages isn't necessary, just indenting the parts inside those blocks. It already is indenting the parts within the blocks to the start of the blocks so it's already aware of it. There needs to be one level of indenting for every block content.
This is the default formatter in vscode so it would be good to use it because people using these templating languages have to disable it.
Or can we get an option to preserve everything in between certain tags? Then if we specify {% and %} it won't ruin the indenting inside it. There's already an option to preserve the wrapping of html attributes. It wouldn't be ideal but would at least let us keep the formatter on.


Add command "loadstatic" inside cmd for load automatically assets/static inside template

check here original project : https://github.com/vBlackOut/loadstatic

Hello, yes it's my first contribution i try to fix my linter code thank !

Thanks for this patch, however all new features require an accepted ticket.

Thanks for this patch, however it sounds like a third-party package is the best way to proceed so that people can try it out and then approaching the django-developers mailing list to reach a wider audience and see what other think.

why it's better package for this ? i didn't found ?
and for download the cdn on path static it's possible ? on automaticaly ?
i didn't found the solution on django ...

I didn't say that there is a better package for your use case.
IMO, it's not something that needs to be built into Django itself.

but it's better it's inside core for all people ? no
i creater documentation after and test unitest for thaht and add inside django for better use :) no ?
you are okai

but it's better it's inside core for all people ? no

No, the current thread is to keep Django a core framework, not providing every utility which might be useful.

ok thank for you explain it's just my proposal solution :) i create the package no other solution :( and i add pip install other package for that but it's weird for me


Componente Height

What is the simplest way to change the size of the component's height? Must adapt to the default CSS Bulma, but only the height. The rest can stay as it is, which is excellent.
I want to do it in the least invasive way possible. My concern is not without disturbing the natural behavior of the component.
Thanks a lot for the help.

That would be using CSS. You will have to override some css classes and set the correct :option-height.

What are the classes?
Other question: I have to increase the left margin of the text / value? How would I do this without causing problems in the standard structure?

I need to do this: Congratulations amazing job. You did an excellent component. Very good!

Well, thanks! :)
Take a look at the classes in this file: https://github.com/monterail/vue-multiselect/blob/master/src/Multiselect.vue
You can modify them at will.

@shentao, what it's ":option-height"? Css propertie? I am not find this.

I'm trying to override the classes of your component, but it has no effect.

My need is to increase the "z-index" (the bulma's footer, it's over.), Decrease the height of the field and increase the left margin of the content text.
I tried setting the css classes inside my

:option-height is for handling the arrow navigation. It is used to calculate the viewport offset.
Which class do you override?
Probably you have to look on the classes inside multiselect and override the specific classes.


Not able to use ngIf/ngFor directives in project

Hi everyone,
Recently I started working on Angular 2 with this project.
I am trying to set up a simple template with some ng directives, and whenever I include them in my HTML a parsing error appears:

            Media Content

Manager

import { Component } from '@angular/core';

import Video from '../../funke-base/models/Video';

@Component({
  selector: 'funke-video-search',
  styleUrls: [ '../resources/scss/video-list.scss' ],
  templateUrl: '../resources/html/video-list.tpl.html',
})
export class VideoListComponent {

    public videoList: Video[];
    public currentPage: number = 1;

    constructor() {
        this.videoList = [];
    }
}

With this code I always get the error:

main.browser.ts:25 Error: Template parse errors:
Can't bind to 'ngIf' since it isn't a known property of 'h1'.

When I remove the ngIf directive from the code it works great. Is there something I am doing wrong/any problem with my configuration?

Done, sorry was not importing the proper modules


fix linter

Seems like I needed to duplicate the linter file to a different location that Superlinter expects to find
Also prettier updated the MD a little bit too!
Thank you!

Thanks @MDunitz 😄 ! Merging!


Question about community of BIDMach and BIDMat

Hi All,
I love the idea of the project, and it is inline with what I was trying to build, so I am thinking about trying it out and maybe integrate it to my project.
So, been trying to get info about the community and how to contribute, but could not find anything from the project site:
http://bid2.berkeley.edu/bid-data-project/
Is there any dev or user mailing list to start collaborate or maybe Google groups?
I could not find such information about it, that is why I opened this issue (seemed like the only way to communicate about the project).
Thanks for your time,
Henry

Yes, there is a Google group here:
https://groups.google.com/forum/#!forum/bidmach-users-group
I just linked it from the github and project wiki landing pages.
re: dev and user groups, what would you suggest?

Thanks for the response and link to  the Google group, @jcanny.
We can use the Google user group as the main communication for end users, but maybe create another one called bidmach-dev-group to have more discussions about developing features or extending the BIDMach and BIDMat projects.
Also, the website (http://bid2.berkeley.edu/bid-data-project) does not seem to allow external users to comment. Maybe if possible to add moderated user comment ability would help to get more adoption and popularity of the project.
I like how some other projects also using https://gitter.im/ or to support chat to enable more collaborate environment.
Hope these comments help.

With regards to our community discussion earlier today -
@jcanny is your @cs.berkeley.edu address not the way to contact you directly?

@mattmacy yes, that is his email (whatever's listed on his website). However, you also have to remember that like many faculty, he gets hundreds of emails every day and can't respond to every one of them quickly. The community of developers for BIDMach/BIDMat is relatively small and confined to our group and a few others (or one could argue John does almost everything, which is true).


Implementing Cache

This PR includes additions to RadClass that implement a cache_size to index more data than required by integration. This improves performance by reducing the number of indexes pulled from data files. This includes a new RadClass method called run_cache that updates the rows stored in memory from the data file and keeps track of the new start position/timestamp. If the requisite rows are not found in cache memory, the cache is reinitialized.
A test of implementation is included in test_RadClass.py, which simply re-runs test_integration with a cache_size and double-checks that the answer is the same.

@gonuke The pushed changes address your feedback. Row indices (in the form of rows_idx) is still passed to collapse_data but now the cache is re-initialized, if required, outside the method. self.cache_idx keeps track of the indices in cache, which can be substracted from rows_idx (as an offset) to properly index rows for integration. A for-loop is no longer necessary.

@gonuke Both comments are addressed/implemented in the newest commit.