installing buildstream on fresh jessie from instructions at http://buildstream.gitlab.io/buildstream/install.html#installing

See original issue on GitLab
In GitLab by [Gitlab user @devcurmudgeon] on Apr 25, 2017, 15:13

the git clone fails unless we have an ssh key set, so let's replace "git clone git[Gitlab user @gitlab].com:BuildStream/buildstream.git" with "git clone https://gitlab.com/BuildStream/buildstream.git

ruamel fails to install...

Unpacking /home/admin/src/buildstream
  Running setup.py (path:/tmp/pip-rxu1im61-build/setup.py) egg_info for package from file:///home/admin/src/buildstream
    your setuptools is too old (<12)
    setuptools_scm functionality is degraded
    zip_safe flag not set; analyzing archive contents...

    Installed /tmp/pip-rxu1im61-build/pytest_runner-2.11.1-py3.4.egg

Requirement already satisfied (use --upgrade to upgrade): setuptools in /usr/lib/python3/dist-packages (from BuildStream==0.1)
Downloading/unpacking psutil (from BuildStream==0.1)
  Downloading psutil-5.2.2.tar.gz (348kB): 348kB downloaded
  Running setup.py (path:/tmp/pip-build-xy965he4/psutil/setup.py) egg_info for package psutil

    warning: manifest_maker: MANIFEST.in, line 14: 'recursive-include' expects <dir> <pattern1> <pattern2> ...

    warning: no previously-included files matching '*' found under directory 'docs/_build'
    warning: no previously-included files matching '*' found under directory '.ci'
Downloading/unpacking ruamel.yaml (from BuildStream==0.1)
  Downloading ruamel.yaml-0.14.9.tar.gz (241kB): 241kB downloaded
  Running setup.py (path:/tmp/pip-build-xy965he4/ruamel.yaml/setup.py) egg_info for package ruamel.yaml
    Traceback (most recent call last):
      File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2382, in _dep_map
        return self.__dep_map
      File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2457, in __getattr__
        raise AttributeError(attr)
    AttributeError: _Distribution__dep_map

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "<string>", line 17, in <module>
      File "/tmp/pip-build-xy965he4/ruamel.yaml/setup.py", line 858, in <module>
        main()
      File "/tmp/pip-build-xy965he4/ruamel.yaml/setup.py", line 847, in main
        setup(**kw)
      File "/usr/lib/python3.4/distutils/core.py", line 108, in setup
        _setup_distribution = dist = klass(attrs)
      File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 266, in __init__
        _Distribution.__init__(self,attrs)
      File "/usr/lib/python3.4/distutils/dist.py", line 280, in __init__
        self.finalize_options()
      File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 300, in finalize_options
        ep.require(installer=self.fetch_build_egg)
      File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2201, in require
        reqs = self.dist.requires(self.extras)
      File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2401, in requires
        dm = self._dep_map
      File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2390, in _dep_map
        if invalid_marker(marker):
      File "/usr/lib/python3/dist-packages/pkg_resources.py", line 1207, in is_invalid_marker
        cls.evaluate_marker(text)
      File "/usr/lib/python3/dist-packages/pkg_resources.py", line 1319, in _markerlib_evaluate
        for key in env.keys():
    RuntimeError: dictionary changed size during iteration
    sys.argv ['-c', 'egg_info', '--egg-base', 'pip-egg-info']
    test compiling test_ruamel_yaml
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2382, in _dep_map

    return self.__dep_map

  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2457, in __getattr__

    raise AttributeError(attr)

AttributeError: _Distribution__dep_map

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

  File "<string>", line 17, in <module>

  File "/tmp/pip-build-xy965he4/ruamel.yaml/setup.py", line 858, in <module>

    main()

  File "/tmp/pip-build-xy965he4/ruamel.yaml/setup.py", line 847, in main

    setup(**kw)

  File "/usr/lib/python3.4/distutils/core.py", line 108, in setup

    _setup_distribution = dist = klass(attrs)

  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 266, in __init__

    _Distribution.__init__(self,attrs)

  File "/usr/lib/python3.4/distutils/dist.py", line 280, in __init__

    self.finalize_options()

  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 300, in finalize_options

    ep.require(installer=self.fetch_build_egg)

  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2201, in require

    reqs = self.dist.requires(self.extras)

  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2401, in requires

    dm = self._dep_map

  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2390, in _dep_map

    if invalid_marker(marker):

  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 1207, in is_invalid_marker

    cls.evaluate_marker(text)

  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 1319, in _markerlib_evaluate

    for key in env.keys():

RuntimeError: dictionary changed size during iteration

sys.argv ['-c', 'egg_info', '--egg-base', 'pip-egg-info']

test compiling test_ruamel_yaml

----------------------------------------
Cleaning up...
Command python setup.py egg_info failed with error code 1 in /tmp/pip-build-xy965he4/ruamel.yaml
Storing debug log for failure in /home/admin/.pip/pip.log

In GitLab by [Gitlab user @tristanvb] on Apr 26, 2017, 12:30
closed

In GitLab by [Gitlab user @tristanvb] on Apr 26, 2017, 12:30
Thanks for the report and details !
I've fixed this in master with the following commit:
commit b88538309217b29d4df881e1b86b0e1f12eb91d8
Author: Tristan Van Berkom <tristan.vanberkom[[Gitlab user @codethink]](https://gitlab.com/codethink).co.uk>
Date:   Wed Apr 26 20:27:55 2017 +0900

    Documentation fixes for issue 12

      o Use the https gitlab url since the git url scheme requires you
        have a gitlab ssh key

      o Recommend installing ruamel.yaml with the package manager, as
        people are running into issues installing ruamel.yaml via pip


Thermal relaxation error channel

This implements two new channels: ResetChannel and ThermalRelaxationChannel, both following the corresponding Qiskit implementation. Note that the thermal relaxation channel, at least as it is implemented in Qiskit, is different depending on which of T1, T2 is larger. Specifically:

If T1 >= T2 (which I think is the common case experimentally), the channel is a probabilistic mixture of unitaries and collapse gate so it can be implemented as a special case of UnitaryChannel. This case can also be simulated with state vectors and sampling.

If T1 < T2 the channel is general (not a unitary mixture) and can only be used with density matrices. Qiskit uses the Choi matrix representation to define the channel in this case but since we don't have an implementation of this, I just worked out the transformation on paper and coded the functions that implement it both for the custom and tf backends.

All transformation equations are written in detail in our docs. If @AdrianPerezSalinas agrees, this PR together with #278 (already merged) should close #63.

This implements two new channels: ResetChannel and ThermalRelaxationChannel, both following the corresponding Qiskit implementation. Note that the thermal relaxation channel, at least as it is implemented in Qiskit, is different depending on which of T1, T2 is larger. Specifically:
* If T1 >= T2 (which I think is the common case experimentally), the channel is a probabilistic mixture of unitaries and collapse gate so it can be implemented as a special case of `UnitaryChannel`. This case can also be simulated with state vectors and sampling.

* If T1 < T2 the channel is general (not a unitary mixture) and can only be used with density matrices. Qiskit uses the Choi matrix representation to define the channel in this case but since we don't have an implementation of this, I just worked out the transformation on paper and coded the functions that implement it both for the custom and tf backends.

All transformation equations are written in detail in our docs. If @AdrianPerezSalinas agrees, this PR together with #278 (already merged) should close #63.

This implements two new channels: ResetChannel and ThermalRelaxationChannel, both following the corresponding Qiskit implementation. Note that the thermal relaxation channel, at least as it is implemented in Qiskit, is different depending on which of T1, T2 is larger. Specifically:
* If T1 >= T2 (which I think is the common case experimentally), the channel is a probabilistic mixture of unitaries and collapse gate so it can be implemented as a special case of `UnitaryChannel`. This case can also be simulated with state vectors and sampling.

* If T1 < T2 the channel is general (not a unitary mixture) and can only be used with density matrices. Qiskit uses the Choi matrix representation to define the channel in this case but since we don't have an implementation of this, I just worked out the transformation on paper and coded the functions that implement it both for the custom and tf backends.

All transformation equations are written in detail in our docs. If @AdrianPerezSalinas agrees, this PR together with #278 (already merged) should close #63.

Hi all, I know I am a bit late, but I have checked this PR and the previous issues on thermal errors, and everything seems fine to me. Thank you for the work!!


OneDimBinning: is_lin, is_log describe binning behavior, NOT regularity in either space

Work started in PR #612 by @atrettin, hopefully this fully fleshes out that idea. Please test from my branch, @atrettin & provide any feedback.
Note that the big change here is to make is_lin and is_log describe binning behavior, and not anything to do with whether or not the binning is "regular" in linear- or log-space. There is an additional property of OneDimBinning called is_irregular which will test the regularity of the binning in the space in which it is defined, if that information is useful / necessary (this is used, in part, in the new __str__ method to allow for more concise string representation of binnings; also could be useful for optimizing certain functions on the bin edges).
Full run-down of changes:

is_lin and is_log no longer imply uniformity in linear-/log-space
still can use is_lin and is_log at __init__, but if both are none, is_li=True
still use both is_lin and is_log as internal state (backwards compatibility)
make is_log, is_lin setter attributes
make is_irregular a derived quantity, cached in its getter (and invalidated if setters is_log or is_lin cause either to be modified)
update __init__ handling accordingly
update docstrings accordingly
new __str__ output that always describes lin/log behavior
rename is_bin_spacing_lin -> is_bin_spacing_lin_uniform, is_bin_spacing_log -> is_bin_spacing_log_uniform
oversample function modified to work bin-by-bin regardless of nature of binning (i.e., works for irregular binning, and doesn't check for regularity)
oversample bugfix: if factor < 1 error message: ">= 0" -> ">= 1"
update outdated pylint disables
disable line length checking for docstring examples
fix docstring doctest examples; all pass but a few that aren't expected to pass
fix basename function (previously didn't do what it advertised), add more docstring examples  (doctest)

Thank you for getting all this done so quickly! I will check it out now to see if it works for me.

I'm still having issues loading hypersurfaces because the binning hashes don't match... I'm looking into it.

Okay, I found the problem: In my first version, the is_log property for the PID binning with edges [0.55, 0.75, 1.0] was inferred to be True, when it should be (and now, is) linear.


Windows support?

Uncertain whether to label this issue a bug report or an enhancement.
I tried to make go-ext-wasm work in Windows by manually copying the 0.7.0 wasmer_runtime_c_api.dll to github.com\wasmerio\go-ext-wasm\wasmer.
Yet on seeking to run the example I receive Process finished with exit code -1073741515 (0xC0000135)
Is it possible to get go-ext-wasm running in Windows somehow? Or does the go extension currently not support Windows yet?

Thanks!  It seems like from the README that we may not support this on Windows yet -- once we do, we'll add it to our CI to make sure our installation instructions work on Windows too.
I don't have context on the go extension at all right now.  I have no idea if this is easy or hard to fix, perhaps it's something I can look into once I get the highest priority items off my todo list.  In the meantime, you're welcome to take a crack at fixing it if you'd like.  If you have context on Go on Windows, then you're more qualified to fix this than me!

Hey,
We are migrating our CI to Azure, so that we can start testing on Windows.

@MarkMcCaskey Hey any luck getting it to work on Windows? I've been postponing my project since like last year. It would really mean a lot if this got fixed/added. Thanks.

We will resume this work.


Hide margin estimations for perps markets

The Chore
There is a problem with margin estimations in core for perp markets. Wrong values are returned from the api in the specific case of when the oracle has not sent any data points. To avoid confusion we should hide it
Tasks

[ ] Hide margin estimation for perps markets
[ ] Or better: Hide margin estimations for perps markets that haven't received a data point from an oracle

Additional details / background info

The root cause of this issue has been resolved ad the validators deployed to mainnet v0.73.5 on the 20th Nov '23
The hiding of the margin estimation has been reverted with the network deployment now fixing the root cause


Add quotes to powershell command so it can be copy/pasted.

@jevansaks : Thanks for your contribution! The author(s) have been notified to review your proposed change. @glimoli

@glimoli Could you review this pull request?
#assign:glimoli

glimoli is not a valid GitHub ID, or is not a collaborator on this repo.

@glimoli I can't determine why PRMerger doesn't recognize you as a Microsoft contributor. When you have a chance, would you go through the steps in https://review.docs.microsoft.com/en-us/help/contribute/contribute-get-started-setup-github?branch=master to make sure your accounts are fully linked? Then, automated notification would work, and we can ensure that you are assigned to a public repo PR, as author of the article. Thanks!

@genlin I don't have approval access to merge in this branch but the change is correct. Can you approve and merge please?

#sign-off

@genlin: I'm sorry - only the author of this article, @glimoli, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


Use .yaml rather than .yml

The correct file extension for yaml files is .yaml rather than .yml (https://stackoverflow.com/a/54265316/14403974)

Please assign Matt


[Bug] [DataSource] java.lang.RuntimeException: datasource plugin doris' is not found

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

Version 3.2.0
Start in standalone mode, plug-in mysql as data element storage
The data source configuration is successfully connected to doris.
Create a new workflow and select the SQL task, select the doris data source, and perform the insert operation. A java.lang.RuntimeException: datasource plugin doris' is not found exception is reported, and the task execution fails.

1698979170482.log

What you expected to happen
The original doris data corresponding to the sql task was executed successfully.
How to reproduce
After reinstalling ds, the problem still occurs
Anything else
No response
Version
3.2.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

版本 3.2.0
启动方式standalone，外挂mysql作为数据元存储
数据源配置doris联通成功
新建工作流并选择sql任务，选择doris数据源，并执行insert操作报java.lang.RuntimeException: datasource plugin doris' is not found异常，任务执行失败

1698979170482.log

What you expected to happen
sql任务对应的doris数据原执行成功
How to reproduce
重新安装ds后，仍旧出现这个问题
Anything else
No response
Version
3.2.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

the same issue with https://github.com/apache/dolphinscheduler/issues/14547, I will close this issue


Extra-Libraries is for system libraries.

Use Build-Depends for util.
For more information, see input-output-hk/stack2nix#149 .

libutil is a system library, not a haskell dependency.

Oh! Well that explains it. :-)
Then the correct solution is to find out what it's called on Nix. Thanks for a quick answer.

Is it this one?
https://packages.debian.org/sid/libutil-freebsd-9

I think so. It's the system lib that has forkpty (it's in libc on macOS, but linux and BSD have a separate libutil that has it).

Thanks! That information will help me pin it down.

It's part of glibc, so it's not a package I need to supply. That settles everything, thank you for your guidance.


prepare-tac should merge multiple candidates at same location

I've hacked this into Reader/Document at https://github.com/wikilinks/neleval/compare/merge-duplicates?expand=1, but given that there is a facility to read in multiple candidates from each line of a .tsv, this should really be happening in prepare-tac.
But there should still be an error raised if the gold data for prepare-tac has multiple candidates for any annotation. So prepare-tac should probably have a --gold mode.

This was fixed by #13.


Evaluating document type on save like it is done on open

I am working a lot with bash scripts that do not have a file ending.
When I copy/paste an existing code block with the shebang line (#!/bin/bash)(I guess is used to identify its a bash script). I understand that it might not be useful to check the file type each time something was changed on a document but I would like that to happen when I hit CTRL+S.
At the moment I have to save and close the file and reopen it so that VS Code recognizes it as a bash file.

I wonder if it should rather be on type even? At least when the mode is plain text, we should maybe detect on typing?

I wonder if it should rather be on type even? At least when the mode is plain text, we should maybe detect on typing?


Add query options to backend datasource plugin

Hi, Can I get more information on how to implement query options with variable type "Query" in the backend data source plugin using Go. I am having trouble finding the documentation. I got the other variable types working using applyTemplateVariables but couldn't get much information on implementing metricFindQuery function.
Right now when I select my plugin under data source, the query field is not populating. Only the regex field shows up.

Hi, @ashritha-singu did you manage to figure this out?


command 'extension.runJestFile' not found

First up, thanks for this amazing extension! My Jest workflow is so smooth with it.
It seems that all versions since 0.4.3 when I try and "Run Jest" or "Run Jest file" I get the following message:
command 'extension.runJestFile' not found

In the console I see the following error:
Activating extension 'firsttris.vscode-jest-runner' failed: Cannot find module 'escape-string-regexp'
Require stack:
- /Users/andypearson/.vscode/extensions/firsttris.vscode-jest-runner-0.4.5/out/jestRunner.js
- /Users/andypearson/.vscode/extensions/firsttris.vscode-jest-runner-0.4.5/out/extension.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-amd.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js.

Rolling back to 0.4.2 fixes the problem and makes the commands work again.
Also, a small thing I noticed is that the recent entries in the change log are listed as happening in 2017, which confused me for a second :)

A little more of a dig, I think that "escape-string-regexp": "^2.0.0", should be in dependencies instead of devDependencies, although I can't say that for sure as I don't know how VSCode extensions work with package.json.
Shall I try and figure that our and submit a PR?

This just broke for me as well.  I can't seem to get it to run any more.  runJest is also broken.
Is there any workaround?
@andypearson did you find a workaround?
I really love this extension :-) and this is slowing down my workflow with it broken.  :-(

OK, I rolled back to version 0.4.2 and it seems to be working again now.  See How to Rollback a VSCode Extension Version for details.

@andypearson @andypearson  you guys are the man. Thank you so much. After rollback, everything works as expected.

thank for reporting that issue.
strange that my local build was working while the store build was not.
i fixed this issue in 0.4.7
can you please confirm that 0.4.7 is working for you?

HI @firsttris , no version 0.4.7 is also broken, but differently.  I upgraded to 0.4.7 and it dies with "Found non-callable @@iterator" and Jest won't run and the extension doesn't seem to work.  Neither developer tools nor extension host logs show any errors.  Not sure what the problem is but 0.4.7 does not work.  Happy to help test other versions or attach logs if you give me some directions!  :-)
So I'm going to revert to 0.4.2 again.

which OS are you using?
which vscode version?
is there any output in there terminal at all?

on my machine (manjaro & vscode 1.4.1)
i can't reproduce your issue

maybe because some other vscode dependencies have also been updated?

also tested on Windows10 with older vscode version

macOS Mojave
latest vscode version
I can get you the exact version numbers in the morning if that helps?
I tried turning off other extensions but that didn’t help.    It’s definitely vscode-jest-runner as far as I can tell.    Reverting to earlier versions of this extension makes the problem go away.
Any ideas?

On Dec 14, 2019 at 10:53 PM,  <Tristan Teufel (mailto:notifications@github.com)>  wrote:
which OS are you using?
which vscode version?
is there any output in there terminal at all?
—
You are receiving this because you commented.
Reply to this email directly,   view it on GitHub (https://github.com/firsttris/vscode-jest-runner/issues/48?email_source=notifications&email_token=AAMW46FMIDHDRP2LEZM3N2DQYXH7DA5CNFSM4J2463SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG4SWMY#issuecomment-565783347), or   unsubscribe (https://github.com/notifications/unsubscribe-auth/AAMW46EH6V5BF74HFYXZIE3QYXH7DANCNFSM4J2463SA).

will do some testing in osx and report back

Thanks!

On Dec 15, 2019 at 1:30 AM,  <Tristan Teufel (mailto:notifications@github.com)>  wrote:
will do some testing in osx and report back
—
You are receiving this because you commented.
Reply to this email directly,   view it on GitHub (https://github.com/firsttris/vscode-jest-runner/issues/48?email_source=notifications&email_token=AAMW46D3SJRWCY4VMXQX7NDQYX2LXA5CNFSM4J2463SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG4U44Q#issuecomment-565792370), or   unsubscribe (https://github.com/notifications/unsubscribe-auth/AAMW46CTBQFUYVJRM4IQZW3QYX2LXANCNFSM4J2463SA).

tested 0.4.7 on a macbook pro with darwin.
seems to work well :man_shrugging:

maybe the issue is on your end?
i put some basic test example projects in the repository:
https://github.com/firsttris/vscode-jest-runner/tree/master/test/Projekt A
if you still think there is a issue in the version you could probably create a reproducible example.

@iosdev-republicofapps remove your jestrunner config from you vscode settings.json, there was some changes. wrong config could create such issues. will check if can add some error handling.

Sorry for the late reply, but 0.4.9 is working nicely for me again. Thanks for your hard work @firsttris!


Is it possible to add HLint rule to require INLINABLE

Say I have type-class
class Foo a where
   foo :: MonadFoo m => m a

I'd want to require that all foo =  bindings have {-# INLINABLE foo #-} (or INLINE) in the same scope. AFAIU this cannot be implement as user hint.
instance Foo Int where
    foo = ...
    {-# INLINABLE foo #-}

I'll be perfectly happy if all foo = should have {-# INLINABLE foo #-} attached, independencly if they are actually instance methods or not. It would be my problem to turn false positives (I doubt I'll have local variables named foo e.g.).

With the user configurable .yaml file it seems entirely reasonable to require certain bindings to have certain pragmas. They are currently known as restrictions, and in a way they still are - just restricting the kind of pragmas you can omit.


Docs: Add logo config example

Verbatim copy of a Slack answer given by @danwom (better give credit where it’s due 🙂)
Having a few specific examples to go from in config docs always give you a good start

Ready for review again!


Different remaining space base shown in space list and sidebar

There is also a bit of discrepancy in the UI regarding the remaining space.
In the space list (when using the table view instead of the grid view) we see the remaining diskspace listed as the remaining quota which is at least misleading, when quota > remaining diskspace.

The the details view on the sidebar we the the quota usage calcuated based on the quota and actual space usage.

This is at least confusing. Also I am wondering if we really should expose the remaining diskspace at all, independent of which blobstore is being used. At least we should make a clear differentiation between how much quota is used and the amount of remaining diskspace.
Originally posted by @rhafer in https://github.com/owncloud/ocis/issues/9245#issuecomment-2368429330

Already landed in master


Can't detect device

Hi, and thanks for a very nice library :-)
I'm trying to use the BLE.Client.MAUI example to detect a custom hardware with a fairly standard BLE compliant chipset. I'm pretty sure the scanner itself works as intended, because it's picking up my headset, tv etc. Unfortunately it fails to detect the intended hardware. Said hardware is detected by Windows itself, a legacy UWP app, as well as a couple of third party BT scanners I downloaded (With bluetooth address 00:13:43:BE:43:CB), but not by the MAUI app.
This problem would be difficult to reproduce as it relies on custom hardware, but maybe you would be able to give me some pointers as to how I could address the problem? I've tried changing the ScanMode and ScanMatchMode parameters, but I don't really see any other alternatives.

Hi @vfiksdal,
I'm the friendly issue checker.
It seems like (100.00 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message.
But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!

Two questions:

Could you try BLE.Client.MAUI on a different operating system, in order to check if you see the device there? Android might be the easiest, but iOS and MacOS are also supported (if you have access to an Apple device).
How does the device advertise itself? What kind of data does the advertisement include?

Hi, and thanks for a swift reply to a rather unreasonable report :-)
Good idea, I'll try to get the project and/or your sample project loaded onto my tablet over the weekend. It's a couple of years old though, so it may have some hoops of it own to overcome.
As for the advertisement I don't really know much about it, maybe you can recommend a third party app which provides more in-depth details? I just randomly downloaded Medeival Bluetooth Network Scanner (Which in retrospect doesn't sound too promising)  and it provided the following data:

Thanks again, and I'll get back to you ASAP on how it works on Android.

As for the advertisement I don't really know much about it, maybe you can recommend a third party app which provides more in-depth details?

nRF Connect is a pretty good tool. I mostly used it on Android, but it seems there is also a Desktop variant that runs on Windows:
https://www.nordicsemi.com/Products/Development-tools/nrf-connect-for-desktop

I just randomly downloaded Medeival Bluetooth Network Scanner (Which in retrospect doesn't sound too promising) and it provided the following data:

It seems this doesn't show any details on the actual advertisement data. nRF Connect will be able to reveal that.

Unfortunately, I can't get this tool to scan in Windows. Might be because I have several systems running a newer version of JLink.
It did work in Android though, and interestingly it doesn't detect the device either. Android itself do find the device though, so the radio itself is not the problem.
Can this be some kind of compliance issue? The datasheet for the chipset says it's 4.2 compliant. That's kind of old now?

It did work in Android though, and interestingly it doesn't detect the device either. Android itself do find the device though, so the radio itself is not the problem.

Just to clarify what you are talking about: Did you try nRF Connect or BLE.Client.Maui on Android? If the Android OS sees the device, then both of these tools should in theory see it as well (unless it's a Bluetooth Classic device, which does not support BLE) ...

It's nRF Connect that failed to detect it. I'll need to set permissions etc to get my own project running on android, and haven't gotten around to it yet.
The chipset supports both LE and Classic, and the firmware does specify that it uses LE, but it may be using Classic due to a bug. Do you know a simple way to identify this?
Thanks a lot for your help again.

Looking at the firmware source, it seems like it is indeed BLE. All of these are enabled:

Bit 0 - Enable / Disable LE Secure connection.
Bit 1 - Enable / Disable LL Connection parameter request.
Bit 2 - Enable / Disable LL ping procedure (Supported only in TC35680/81).
Bit 3 - Enable / Disable Support for 2M PHY (Supported only in TC35680/81).
Bit 4 - Enable / Disable Support for LE Coded PHY (Supported only in TC35680/81).
Bit 5 - Enable / Disable Support for LE Extended Advertising (Supported only in TC35680/81).
Bit 6 - Enable / Disable Support for LE Data length change event (Supported only in TC35680/81).

I assume "secure connection" means encrypted, but this should not apply to the discovery?

It's nRF Connect that failed to detect it.

fwiw, nRf on android is the gold standard imho.
If your devices isnt detectable with that, it either doesn't want to be found or more likely something about the device is incompatible

Apparantly outside the scope of the library. Thank you for your input on the issue.


feat(samples): add caseClassifications.search

Part of #2207

Closing as discussed in https://github.com/googleapis/google-api-python-client/issues/2207#issuecomment-1656265573


fish: Unknown command 'fastlane'

Environment
macOS 10.12.2
Xcode 8.2.1
Shell: fish
Issue Description
When I typing fastlane ⏎ in Fish shell terminal, I got message: fish: Unknown command 'fastlane'.
Checklist

[x] xcode-select --install
[x] Reinstall fastlane successful. brew cask reinstall fastlane
[x] close Terminal and reopen.

How did you fix the issue?

@KrauseFx Fish shell $PATH not include ~/.fastlane/bin/, so unknown command 'fastlane'.
I config ~/.config/fish/config.fish file:
# Fastlane path
set PATH {$HOME}/.fastlane/bin/ $PATH

Then, it's worked.


Provide better ways to clean tuples

Checklist

[X] I agree to the terms within the OpenFGA Code of Conduct.

Describe the problem you'd like to have solved
We have been trying to migrate to openfga in case of our first application. However, we do have quite extensive integration tests and we are reusing like object ids. We would like to see better ways to delete tuples from openfga, to "reset" the state before/after single tests. By that way we could have possibility to execute repeatable tests.
I got everything working by using postgresql database behind openfga, and then executing commands to postgresql database itself. However, it is kind of dirty hack. So I propose real api for this.
I am running following code after each test:
		_, err = db.Exec("DELETE FROM tuple where object_type = 'document'")
		assert.NoError(t, err)

Describe the ideal solution
Ideally there could be way to delete all tuples related to object_type. I am thinking could POST /stores/{store_id}/write allow that? by specifying
{
  "deletes": {
    "tuple_keys": [
      {
        "user": "*",
        "relation": "*",
        "object": "document:*"
      }
    ]
  }
}

Other possibility is to provide new api that makes it possible to clean data easily from the openfga to make it working better with the tests. Like could there be way to clean all data from the store but keep the store_id?
My use-case is just for object_type. However, allowing wildcards in delete tuple_keys could help to make lot of more use-cases.
Alternatives and current workarounds
No response
Additional context
No response

nice to see you around @zetaab

lets say that I have object document:1 when someone goes to rest api and will delete that from application. I would like to clean all tuples related document:1. Currently its not easily possible? Or is it even possible to list all relations (and users) to object?

@zetaab could you potentially use the Read API followed by batches to the Write API to delete?
POST /stores/{store_id}/read
{
  "tuple_key": {
      "object": "document:1"
   }
}

@jpadilla well maybe.. but the issue is that in my integration tests I do really have like 500 documents. Each document do have 4 tuples. This means that I need to do 500 reads and then 2000 writes to api. Instead of just single sql exec command to database itself.

Hi @zetaab
This enhancement is captured in this Roadmap entry https://github.com/openfga/roadmap/issues/34
I'll close this issue now and we'll track it there.
Thanks a lot for the feedback


Would be nice to have a "host.fact.user" fact

Is your feature request related to a problem? Please describe.
Right now, if I want to get the user that is being used to connect to a given remote machine I have the following options:

Add group data that specifies the user for a given remote.
Use host.data.ssh_user (assuming an ssh connection).
Grab the host.fact.home fact and then split out the user.
Write a custom fact that does the above.

When running adhoc commands, the first two methods don't work, and the last two methods require duplicate code in all operations that happen to need the "user," which works but is not ideal.
Describe the solution you'd like
It would be great to have a built-in host.fact.user. The host.fact.home fact is almost what I need, but falls short when it comes to running adhoc commands.

I like this idea; to get the current user right? Could be implemented by executing whoami, but that would mean calling it with sudo would return root (or the sudo_user), which I think is useful. Ie:
# deploy-no-sudo.py
print(host.fact.user)  # SSH user

vs:
# deploy-with-global-sudo.py

SUDO = True
print(host.fact.user)  # root

This would be the same behaviour we have the host.fact.home. I think to get the SSH user (or winrm user, etc, etc) that is something specific to the connection type, and makes sense to be retrieved from there.

Yep, I pretty much just need the output of host.fact.home split to just the user. whoami was also the first thing my mind jumped to, but I wonder if there might be some systems/scenarios where that is not ideal (aside from not working on Windows). Maybe it could try several different methods, possibly starting with checking the $USER env var first?

Turns out both work everywhere!
--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/fedora24] vagrant
[@vagrant/fedora24] vagrant
    [@vagrant/fedora24] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/freebsd12] vagrant
[@vagrant/freebsd12] vagrant
    [@vagrant/freebsd12] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/centos8] vagrant
[@vagrant/centos8] vagrant
    [@vagrant/centos8] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/centos7] vagrant
[@vagrant/centos7] vagrant
    [@vagrant/centos7] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/centos6] vagrant
[@vagrant/centos6] vagrant
    [@vagrant/centos6] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/opensuse_tumbleweed] vagrant
[@vagrant/opensuse_tumbleweed] vagrant
    [@vagrant/opensuse_tumbleweed] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/debian8] vagrant
[@vagrant/debian8] vagrant
    [@vagrant/debian8] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/opensuse_leap15] vagrant
[@vagrant/opensuse_leap15] vagrant
    [@vagrant/opensuse_leap15] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/ubuntu18] vagrant
[@vagrant/ubuntu18] vagrant
    [@vagrant/ubuntu18] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/debian9] vagrant
[@vagrant/debian9] vagrant
    [@vagrant/debian9] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/ubuntu16] vagrant
[@vagrant/ubuntu16] vagrant
    [@vagrant/ubuntu16] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/openbsd6] vagrant
[@vagrant/openbsd6] vagrant
    [@vagrant/openbsd6] Success

--> Starting operation: Server/Shell (echo $USER; whoami)
[@vagrant/ubuntu20] vagrant
[@vagrant/ubuntu20] vagrant
    [@vagrant/ubuntu20] Success

I'll go with $USER as it matches the home fact!

I have now implemented the user fact in https://github.com/Fizzadar/pyinfra/commit/fdf74a444ed91421fc29771a4a5d5bd06fd797b9.

Now released in v1.3!


Singleton custom element viewmodel isn't singleton

I have a custom element (called Confirm) whose view model I want to be a singleton. Basically, the element is loaded in a view  but then its view model will be used by other custom elements and they all need to work with the same instance of the VM.
Decorating the element with singleton() doesn't prevent the viewmodel constructor to be called twice (once when Confirm element is loaded/rendered and once when it's injected as a dependency).
//custom element code

@singleton()
export class Confirm {
      constructor() {
       console.log("confirm created");

   }
}

//other custom element using Custom

@autoinject
export class Delete {
       constructor(public confirm:Confirm) {

      // alternate approach, it doesn't work either
      // this.confirm = Container.instance.get("Confirm");

    }

//in the view
 <require from="./resources/confirm"></require>
    <confirm></confirm>
    <delete></delete>

I get "confirm created" twice. I don't know if it's a bug or it's me not knowing how to use the DI Container.

I may be wrong, and if so I hope someone corrects me, but ..., your Confirm may be created in views having different Containers. You have the root container and child containers get created from it. So Confirm gets created as singleton in different containers. You can try and register it yourself in the root container as singleton.
aurelia.use
    .instance(Confirm, confirmInstance);

Or you can provide an Invoker that always returns the same instance.

Tried that, it's still invoked twice but definitely it's something related to the root/children DiC . Is there a way to force a singleton to be a global  singleton?

After some tests, it's clear that the custom element model used in the view it's not the same as the one from the Container. Basically, I've registered the view model as an instance  and set its property in the view  (via binding).
 a.use.instance(Confirm, Confirm.instance);

<confirm item="test"></confirm>

The instance available inside the Container still has the default value, while the one rendered shows "test".

Custom elements can't be singletons because what would happen if you did this:
<confirm></confirm>
<confirm></confirm>

If you need to share something, I recommend that you extract a singleton service that is shared by instances of the custom element and any other consumers in the app.

It would be a bug, since I need only one instance of confirm :P . Anyway, this is what I did, sort of, I've used a mediator.


Compose rest api specs for Azure Monitor LiveMetrics

Data Plane API - Pull Request

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[x] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:  Doc
Previous API Spec Doc: N/A
Updated paths: https://github.com/Azure/azure-rest-api-specs/tree/main/specification/applicationinsights/data-plane/Monitor.Exporters/preview

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

Checks stuck in `queued` state?
If the PR CI checks appear to be stuck in `queued` state, please add a comment with contents `/azp run`.
This should result in a new comment denoting a `PR validation pipeline` has started and the checks should be updated after few minutes.

fix https://github.com/Azure/azure-rest-api-specs/issues/27843

/pr RequestMerge


fix(pointcloud-pattern): Add more custom for switchPattern

:tada: This PR is included in version 1.12.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.16.1-alpha.1 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.16.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.9.0-alpha.1 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Remove-Item does not work correctly with long paths

From https://github.com/PowerShell/PowerShell/pull/15260#issuecomment-849160511.
Rename-Item and Set-Location are also affected by this issue.
Steps to reproduce
$testdrive = "$env:TEMP/test"
$longDir = 'a' * 250
$longSubDir = 'b' * 250
$fileName = "file1.txt"
$topPath = Join-Path $TestDrive $longDir
$longDirPath = Join-Path $topPath $longSubDir
$longFilePath = Join-Path $longDirPath $fileName
new-item -itemtype file -path $longFilePath -force
remove-item -Path $longFilePath

Expected behavior
file is removed successfully
Actual behavior
> remove-item -Path $longFilePath
Remove-Item: The system cannot find the path specified.
C:\Users\rjmho
> get-error

Exception             :
    Type            : System.ComponentModel.Win32Exception
    NativeErrorCode : 3
    ErrorCode       : -2147467259
    TargetSite      :
        Name          : IsReparsePointLikeSymlink
        DeclaringType : Microsoft.PowerShell.Commands.InternalSymbolicLinkLinkCodeMethods
        MemberType    : Method
        Module        : System.Management.Automation.dll
    StackTrace      :
   at Microsoft.PowerShell.Commands.InternalSymbolicLinkLinkCodeMethods.IsReparsePointLikeSymlink(FileSystemInfo
fileInfo) in System.Management.Automation.dll:token 0x60016f5+0x57
   at Microsoft.PowerShell.Commands.RemoveItemCommand.ProcessRecord() in
Microsoft.PowerShell.Commands.Management.dll:token 0x60004dd+0x2e2
   at System.Management.Automation.CommandProcessor.ProcessRecord() in System.Management.Automation.dll:token
0x60020f6+0x1ae
    Message         : The system cannot find the path specified.
    Source          : System.Management.Automation
    HResult         : -2147467259
CategoryInfo          : NotSpecified: (:) [Remove-Item], Win32Exception
FullyQualifiedErrorId : System.ComponentModel.Win32Exception,Microsoft.PowerShell.Commands.RemoveItemCommand
InvocationInfo        :
    MyCommand        : Remove-Item
    ScriptLineNumber : 1
    OffsetInLine     : 1
    HistoryId        : 4
    Line             : remove-item -Path $longFilePath
    PositionMessage  : At line:1 char:1
                       + remove-item -Path $longFilePath
                       + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    InvocationName   : remove-item
    CommandOrigin    : Internal
ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.0-preview.6
PSEdition                      Core
GitCommitId                    7.2.0-preview.6
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Proposed solution
Implement long paths:
diff --git a/src/System.Management.Automation/namespaces/FileSystemProvider.cs b/src/System.Management.Automation/namespaces/FileSystemProvider.cs
index b37b4d10c..da0e4cb2d 100644
--- a/src/System.Management.Automation/namespaces/FileSystemProvider.cs
+++ b/src/System.Management.Automation/namespaces/FileSystemProvider.cs
@@ -8243,6 +8243,12 @@ namespace Microsoft.PowerShell.Commands

             WIN32_FIND_DATA data = default;
             string fullPath = Path.TrimEndingDirectorySeparator(fileInfo.FullName);
+
+            if (fullPath.Length > MAX_PATH)
+            {
+                fullPath = "\\\\?\\" + fullPath;
+            }
+
             using (var handle = FindFirstFileEx(fullPath, FINDEX_INFO_LEVELS.FindExInfoBasic, ref data, FINDEX_SEARCH_OPS.FindExSearchNameMatch, IntPtr.Zero, 0))
             {

Also ensure that the actual file exists before calling the Windows API on it so that the proper error can be thrown if not:
https://github.com/PowerShell/PowerShell/blob/dd5cf8670a49dec25ce5763814efaf2092e321f8/src/Microsoft.PowerShell.Commands.Management/commands/management/Navigation.cs#L2701-L2702

Why conditionally add \\?\ if it exceeds max path, if we control what APIs are called then we should always add that prefix. The benefit there is you are always running the same code even for short paths rather than sometimes testing this edge case.
You also need to be careful when dealing with UNC paths, the prefix is \\?\UNC\$server\$share so just prefixing isn’t enough here.

Also while PowerShell’s location can probably be fine with paths that exceed MAX_PATH I’ve encountered problems in the past with trying to see a long path to the process’ working for. I don’t think that’s something powershell can change and might cause unknown problems down the line when spawning new processes from powershell that might inherit from the file system location (not 100% sure if it actually does today).

Sounds like we could use your review on the next PR to fix this @jborean93.

You also need to be careful when dealing with UNC paths, the prefix is \?\UNC$server$share so just prefixing isn’t enough here.

Good to know

Why conditionally add \?\ if it exceeds max path, if we control what APIs are called then we should always add that prefix

That suggestion was just based on a principle of minimal perturbation. But if FindFirstFileExW is always going to succeed there, then that seems reasonable.

Also while PowerShell’s location can probably be fine with paths that exceed MAX_PATH I’ve encountered problems in the past with trying to set a long path to the process’ working dir

Yeah, in this case I think the issue is due to us calling the Windows API directly in an attempt to work around OneDrive weirdness. In the process case, I think .NET does a lot more under the hood (as it does in the Path APIs).
It may also be that the right fix for us here is to abandon the efficiency that the original change was trying to get and simply look at the file twice, once to determine whether it's OneDrive and the second time to call through .NET and take advantage of its robustness.

I’ll have to add some comments when I’m next on a laptop. It’s hard to review actual code changes when looking from your phone :)

It’s hard to review actual code changes when looking from your phone :)

Dw I was also on a phone today 🙂

Still getting it in 7.2.5

@svermaak Please open new issue with exact repro steps.


OCPBUGS-20037: Fix journal entries to belong to greenboot unit

Which issue(s) this PR addresses:

Closes #

/jira refresh

/retest-required

/hold
Repurposing the bug because more failures were found

/unhold

/jira refresh

/lgtm

/retest-required

/cherry-pick release-4.14


Document missing bundled conda for self hosted runners

Closes #113

I think documenting the workarounds in the error message is enough for this corner case.

@goanpeca this should be ready to go

fyi @singhbal-baljinder


Refactors all the Post-related classes to remove wrapper divs, remove legacy stuff, and split up huge classes

Addressed comments and did a couple fixes/changes. Most importantly: I made the Thread story work again (the issue was that it was using an old format for the comment thread hidden within, which no longer works.
The Big Q: its style seems to match the other in the file. Should I update it to the new story format, or is that compatible? I can update them all if needed.
Also, let's get rid of the deprecated thread formats (in a different PR).

Addressed comments and did a couple fixes/changes. Most importantly: I made the Thread story work again (the issue was that it was using an old format for the comment thread hidden within, which no longer works.
The Big Q: its style seems to match the other in the file. Should I update it to the new story format, or is that compatible? I can update them all if needed.

One of my todos is updating all the stories to the new format, so it's going happen one way of the other. If you want to do these ones now while it's fresh in your mind that's great, but otherwise I will do them when I do the rest.

I've done it a little bit (it seems like the format they're in now is compatible with the story format, but I made the names a bit better), but these stories are a mess and I hope to get to do some work on threads refactoring too, so maybe I can give them a better attempt at clean up later.

I went and just added the intermediate link. Thank you so much for your review!


[BUG] uncaught error: RangeError: Invalid WebSocket frame: RSV1 must be clear

Describe the bug
During the last couple of days my nostream implementation failed with an error multiple times.
It is always the same stack trace:
| uncaught error: RangeError: Invalid WebSocket frame: RSV1 must be clear
|     at Receiver.getInfo (/app/node_modules/ws/lib/receiver.js:199:14)
|     at Receiver.startLoop (/app/node_modules/ws/lib/receiver.js:146:22)
|     at Receiver._write (/app/node_modules/ws/lib/receiver.js:84:10)
|     at writeOrBuffer (node:internal/streams/writable:392:12)
|     at _write (node:internal/streams/writable:333:10)
|     at Writable.write (node:internal/streams/writable:337:10)
|     at Socket.socketOnData (/app/node_modules/ws/lib/websocket.js:1274:35)
|     at Socket.emit (node:events:513:28)
|     at addChunk (node:internal/streams/readable:324:12)
|     at readableAddChunk (node:internal/streams/readable:297:9) {
|   code: 'WS_ERR_UNEXPECTED_RSV_1',
|   [Symbol(status-code)]: 1002
| }

To Reproduce
I don't know how to reproduce it. But of course I am willing to help to track it down.
Expected behavior
No error :-)
System (please complete the following information):

OS: Ubuntu 22.04.2
Platform: docker
Version: 1.22.06

Logs
No more logs before and after the stacktrace.
Additional context
Others seem to have the same problem:
https://github.com/Cameri/nostream/pull/225#issuecomment-1448713377

seeing this as well.  Comes with these types of requests in nginx access.log:
<IP_ADDRESS> - - [07/Mar/2023:10:14:35 +0000] "Version: 13\x0D\x0AS" 101 4 "-" "-"
<IP_ADDRESS> - - [07/Mar/2023:00:33:08 +0000] "onnection: Upg" 101 4 "-" "-"
but also (less frequently) with the regular /GET

Yes, I have the same lines always at the same time, there is an error.
It is always a HTTP 101 protocol switch with payload 4 bytes:
x.x.x.x - - [07/Mar/2023:13:55:07 +0100] "GET / HTTP/1.1" 101 4 "-" "-"
And I just found my own IP in the NGINX logs, while I was only running Damus at that time.
@jb55 Maybe you can help to track this down?

I just tried to debug it with Damus in XCode: I was able to create this RSV1 error within nostream a few times, but I could not find out in which circumstances it happens. Sometimes it does, sometimes it does not. And it never resulted in crashing nostream, only those uncaught errors occurred. But when it happens, it happens directly after Damus calls socket.connect() in RelayConnection:53.
Sorry not to be more precise, I have never used XCode before, still learning.

I just tried to debug it with Damus in XCode: I was able to create this RSV1 error within nostream a few times, but I could not find out in which circumstances it happens. Sometimes it does, sometimes it does not. And it never resulted in crashing nostream, only those uncaught errors occurred. But when it happens, it happens directly after Damus calls socket.connect() in RelayConnection:53.
Sorry not to be more precise, I have never used XCode before, still learning.

Amazing. Are there any options passed to that socket or socket.connect function? According to the node ws library this error occurs when the client and server negotiate ws extensions, the server lets the client know it doesn't support compression but the client sends compressed frames anyways

The socket is created using the following line:
let socket = WebSocket(request: req, compressionHandler: .none)
https://github.com/damus-io/damus/blob/795577a0a1065dee1ba74040f9ce109d659f1826/damus/Nostr/RelayConnection.swift#L24
I have never programmed Swift, but "compressionHandler: .none" indicates no compression to me!

Can also confirm this - using latest version of nostream and getting this error on my VPS all the time - although it does not seem to has a severe impact? Relay runs smooth so far I can see....

My nostream deployment crashes often - if I don't do a daily restart. But honestly I don't know if this error causes the crashing. Although this error is the only I see in the logs. But that does not necessarily mean the two are connected.


Update sprint_names.py with another cyclist's name

Please add a link to this cyclist's ProCyclingStats page. Only the most famous of cyclists can be included.

Fame is not what this cyclist strives for. His five-year mission: to explore strange new bike paths, to seek out new cyclists and new techniques, to boldly go where no cyclist has gone before.

After a lengthy review, it has been determined that Hari is not famous enough to be included in the list of famous cyclists.


[Bug] [UI/Master] The task of dependent should use taskCode

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
The task of dependent is using taskName, duplicate names can lead to dependency errors.
What you expected to happen
Please use taskCode to replace taskName.
How to reproduce

Anything else
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

You can't input a node name that alread exists in the same process.

You can't input a node name that alread exists in the same process.

That wil be fixed

You can't input a node name that alread exists in the same process.

I will fix it, that should be allowed.

Same node names in one process may bring misunderstandings, I think you should be careful about adding this

@lenboo @JinyLeeChina
In addition to the DEPENDENT task, the CONDITIONS and SWITCH tasks also had this problem. I fixed the UI part(#6719):

@lenboo @JinyLeeChina In addition to the DEPENDENT task, the CONDITIONS and SWITCH tasks also had this problem. I fixed the UI part(#6719):

well done! i  will test it.


Add Qumat to PyPi

Make a v1 release package

Want to add associated tickets to this so we can track how far away we are from this?


NotFound route always showing with static routes

Hi,
How can I define a notFound component with React Router 4 and static routes?
I use the nextversion of react-router-redux. So, in my client:
export default function appRoutes(history) {
  return (
    <ConnectedRouter history={history}>

        {routes.map((route, key) => (
          <Route key={key} {...route} />
        ))}

    </ConnectedRouter>
  );
}

And routes is:
export const routes = [
  {
    path: '/',
    component: App
  },
  {
    path: '/:lang/chat',
    component: Chat
  },
  {
    path: '/:lang',
    component: Listing
  },
  ...
  {
    path: '*',
    component: NotFound,
    status: 404
  },
];

With this approach, the component not found is always showing along with the matched route.
I have read that instead of wrapping the appRoutes method described above, with a div, I have to use Switch. But with this approach, the routes never match.
So, what I'm doing wrong?

You need to use a <Switch> in order to only render the first matching route.

But that's a problem because it only render one route. In the code I uploaded before, I have the App component rendering when path is '/' and where I have the navbar and other components. Then, when the path is '/:lang', I want to render the component Listing along with the navbar. How I can do that then @pshrmn?

I found a solution that works for me. I have removed from static routes the App component and placed before and then I used Switch to render only one route.
export default function appRoutes(history) {
  return (
    <ConnectedRouter history={history}>

        <Route path='/' component={App} />
        <Switch>
          {routes.map((route, key) => (
            <Route key={key} {...route} />
          ))}
        </Switch>

    </ConnectedRouter>
  );
}


Ignore NaNs when averaging spectrograms

Fixes #7024.
If this works, I'll add a test.

Turns out that we already had a test for NaNs in the data, but it was broken. I fixed it and I think this is ready for merge.

@agramfort @larsoner any chance we could backport this and make a bugfix release soon?

I've rebased so this could be merged. However, I'd still like to clarify whether or not parallelization makes sense here, because IMO scipy.signal.spectrogram should take care of vectorizing and therefore we don't need to parallelize ourselves. This makes the code much easier to read too.

In fact, using the test data from #7024, it takes around 0.49s for n_jobs=1 and around 2.00s for n_jobs>=2.

I would not be surprised if n_jobs > 1 is slower

I'm not surprised that it is slower either, but I wonder why this is still in the function. Unless there is a use case that I'm totally missing right now, I'd say we remove it completely.

Even code that is vectorized can use only a single core on a multi-core machine. Using one vs multiple cores in vectorized code depends on at least:

the linear algebra / FFT libraries used under the hood by NumPy and SciPy
the options for those libraries (e.g., OMP_NUM_THREADS), and
the actual functions being called

If the bulk of the time is spent in multithreaded BLAS or FFT calls, and the user has a multithreading BLAS/FFT library, and they have multithreading enabled for that library, then indeed there shouldn't be much benefit to parallelization (and even some loss possibly). If these conditions aren't satisfied, then there can be. Hence why we would probably still allow parallelization in cases like this, it can depend on the user's setup.
We can investigate whether or not there is a benefit under different circumstances / setups and evaluate if there is any benefit to n_jobs here, but we should probably do that separately.

Agreed, we can do this separately. There's no performance drop when keeping our parallelization and using n_jobs=1, so it is not a pressing issue. I think most people should be running a multithreaded linear algebra library nowadays (at least this is the case for Anaconda on all major platforms, and Python on macOS uses the Accelerate framework), so most people will likely see a dramatic performance drop (in my setup 1/4x) when using more than 1 job.
In summary, this is ready for merge.

Thanks @cbrnr

Backported. @agramfort should we just push out a quick 0.19.2? I think we can just do a quick twine call


Add JSON parsing concept

Reason for change
While browsing the JS Integration docs for Stencil, this line caught my eye:
<todo-list my-object="{}" my-array="[]"></todo-list>

“Oh! Stencil can just parse attributes as JSON! Neat”
Well, there’s a reason why that object & array is empty—in order for it to work, you have to do gross things like this: my-array="["itemOne","itemTwo"]". Hooray! 🙃
Still, Vue.js does support JSON attributes (as long as the attribute name is prefixed with :), and I like the idea. This is a stab at implementing that concept in Stencil (especially since the docs seem to hint that it’s easy).
An alternate method is to use a parser like JSON5, but that’s ~30 KB of weight.
Sidenote:
We should probably make more liberal use of @Watch, at least for the entry components. Our components are not good at listening to changes after initialization, and that would really improve support.

Gonna close it. Still don’t have an answer, short of loading a hefty JSON5 parsing library on the clientside. For now, we can just set things in JavaScript anyway, and the provision button is the only thing that has needed it so far.


Implement the shard management UI for Kvrocks controller

Description
This PR introduces UI for managing shards, including the feature to create and delete shards based upon previous cluster ui. The following features and improvements are included:

[x] Shard Sidebar Component listing all shards.
[x] Shard Card Component listing all nodes data.
[x] Shard Create Component for creating shards.
[x] Loading Component for adding spinner while loading data.

Screencast
Here is a video demonstration of the new UI features for creating and deleting shards:
https://www.loom.com/share/ce0caaac946b46fa95bbb44c66324488?sid=ab77ae3e-8c4a-4ef5-b950-9447003927a7

@git-hulk @jihuayu guys please review !

Great! I will have a look today!

Can you list out the issues you have completed? @CulturalProfessor
https://github.com/apache/kvrocks-controller/issues/135


Warning about auto_mkdir

Hello,
Simple issue. When reading a dataframe (in my case with, for now, with read_csv()), the following warning appears:
FutureWarning: The default value of auto_mkdir=True has been deprecated and will be changed to auto_mkdir=False by default in a future release.

And the most important is that the latter is an error (and not always appears) when computing:
{'error': 'Invalid arguments', 'details': 'The default value of auto_mkdir=True has been deprecated and will be changed to auto_mkdir=False by default in a future release.'}

Would be glad if someone discovered a path, or a work-around for this!
Thanks in advance!

What version of dask and fsspec?

You need to specify the argument as a storage option.
In [10]: df = pd.DataFrame({"A": [1, 2]})

In [11]: df.to_csv("data.csv")

In [12]: dd.read_csv("data.csv", storage_options=dict(auto_mkdir=False)).compute()
Out[12]:
   Unnamed: 0  A
0           0  1
1           1  2

cc @martindurant, do you recall do we want this warning visible right now, or should dask be passing it automatically?

What version of dask and fsspec?

fsspec==0.6.3
dask==2.12.0

You need to specify the argument as a storage option.
In [10]: df = pd.DataFrame({"A": [1, 2]})

In [11]: df.to_csv("data.csv")

In [12]: dd.read_csv("data.csv", storage_options=dict(auto_mkdir=False)).compute()
Out[12]:
   Unnamed: 0  A
0           0  1
1           1  2

cc @martindurant, do you recall do we want this warning visible right now, or should dask be passing it automatically?

Will try this and comment about this ASAP.
Thanks for the quick response!

Here's a recent issue from SO: https://stackoverflow.com/questions/60764849/strange-warning-using-dask-dataframe-to-read-csv/60765410#60765410
Written by @hellocoldworld, member of my team.

I don't think it's useful to dask users, no. In the next fsspec it can go away already, I think.

You need to specify the argument as a storage option.
In [10]: df = pd.DataFrame({"A": [1, 2]})

In [11]: df.to_csv("data.csv")

In [12]: dd.read_csv("data.csv", storage_options=dict(auto_mkdir=False)).compute()
Out[12]:
   Unnamed: 0  A
0           0  1
1           1  2

cc @martindurant, do you recall do we want this warning visible right now, or should dask be passing it automatically?

This approach is apparently working in my project.
But I don't know if it could cause future errors, somewhere using other tools.
I'd like to keep this ticket open.
Thanks!

The latest release of fsspec (0.7.1) has removed the auto_mkdir warning. I'm going to close this issue for now as I don't think there's anything left to do within dask. @perezzini we can reopen if you run into any issues


Integration with NGSI-LD/Scorpio broker

Currently we are working with Scorpio broker/NGSI-ID instead of orion context broker , i am trying to  integrate Anubis with Scorpio broker , is it work if i just change the image of upstream-service from orion to scorpio/NGSI-LD in docker-compose file or You are still working with it or any suggestion!

@SURAJKALLOLI I assume there is no much difference between Orion-LD and Scorpio in term of APIs. If that's the case, it's in the roadmap (#88)

duplicates #88


Angular schematics

Similar flux-based libs started providing schematics to reduce notoriously known "boilerplate". Is it planned feature within angular redux?

Yes, that is something that we would like to add. We will probably start with a schematic for initial setup and then go from there. Please see #57 to track our progress on the initial add schematic


Pub/Sub message ordering support

Fixes #723
Message ordering may require producing the events using an explicit regional endpoint. Not sure if we should add a helper to produce a pubsub client using a regional service endpoint or leave this as an exercise to the integrator.

I tested pubsub ordering key with this library but I fond an issue. When you send 3 or more messages, with same ordering key, receiver only waits for first one, second and third messages are consumed concurrently. I added a 5 second sleep in message handler in order to check in the total amount of time was 15seconds as expected, but it was 10 second. It can also be checked with logs. When I try the same directly invoking pubsub receiver, ir worked as expected.

Question from @rriolobos is tracked under #753.


KYLIN-4275 Fix avg function not working

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Kylin?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have create an issue on Kylin's jira, and have described the bug/feature there in detail
[ ] Commit messages in my PR start with the related jira ID, like "KYLIN-0000 Make Kylin project open-source"
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If this change need a document change, I will prepare another pr against the document branch
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at user@kylin or dev@kylin by explaining why you chose the solution you did and what alternatives you considered, etc...

Pull Request Test Coverage Report for Build 6099

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
10 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.002%) to 27.977%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

query/src/main/java/org/apache/kylin/query/relnode/OLAPAggregateRel.java
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

query/src/main/java/org/apache/kylin/query/relnode/OLAPAggregateRel.java
1
0%

core-cube/src/main/java/org/apache/kylin/cube/cuboid/TreeCuboidScheduler.java
2
68.46%

tool/src/main/java/org/apache/kylin/tool/query/ProbabilityGenerator.java
3
77.78%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java
4
78.12%

Totals

Change from base Build 6065:
0.002%

Covered Lines:
26112

Relevant Lines:
93334

💛  - Coveralls


Adds go/testhtml make target

Description
The target executes unittests and opens coverage report in a browser.
How can this be tested?
make go/testhtml

Checklist
- [ ] Unit tests have been updated/added

[x] PR is labeled accordingly with a single label
[x] I have read and understood the contribution guidelines

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

Project coverage is 66.82%.  Consider uploading reports for the commit 36d3d5c to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2879   +/-   ##
=======================================
  Coverage   66.82%   66.82%
=======================================
  Files         253      253
  Lines       13792    13792
=======================================
  Hits         9217     9217
  Misses       3768     3768
  Partials      807      807

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


Package Requested

[X] I would like someone else to build the manifest.
[ ] I would like help so I can submit the manifest.
[X] I have performed a search and couldn't find this package.
[X] I have checked that the installer for this package is not a standalone or portable executable or a .zip file
[ ] I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: Hibit
Publisher Url: https://www.hibitsoft.ir/
Package Name: Hibit.StartUpManager
Description: HiBit Startup Manager is a powerful Startup utility that Manage autostart programs by adding or removing apps, editing their properties and also Manage process, services, task scheduler and conrext menu.
Package Version: 2.3.20
Installer URL: https://www.hibitsoft.ir/HibitStartup/HiBitStartupManager-setup-2.3.20.exe
Current Package Identifier (for new versions):
https://www.hibitsoft.ir/HibitStartup/HiBitStartupManager-setup-2.3.20.exe

Merging now #65447


Added Swetugg Stockholm and Techorama Belgium

First, o yeah!

NICE!!!!!!!! Thanks for the contributions!!! <3


issue#1627 - primitive fix for LDAP without displayName & co

Draft code, not sure if it is quite right:
When asking LDAP for attr displayName, also ask for cn.
I did not check if is needed in both places.
When searching, fallback to "cn" before trying first+last name.
This will mostly obsolete the code using first+last name though,
since "cn" will usually exist if givenName and sn do.

Closing as this PR is outdated and LDAP related stuff aren't there anymore. Feel free to reopen or tag me if we need to do something about it.


[DOCS] Fixes more X-Pack links

Related to https://github.com/elastic/azure-marketplace/pull/348
This PR cleans up more out-dated links to X-Pack documentation.

ported to 7.5, 7.6, 7.7 and 7.8 branches


Take Appveyour changes to BugFixes

Sign off.

Thanks Raghu. I am just going to go ahead merge these.


[Nullability] Add nullability annotations

For Great Justice and better interop with Swift.
:warning: :fire: :fire_engine: WIP right now. All of these properties need double checking, I'm sure I missed some

Current coverage is 83.24%

Merging nullability into master will not effect coverage as of 46c14d0

Coverage Diff
@@            master   nullability   diff @@
============================================
  Files            3             3
  Stmts         1038          1038
  Branches         0             0
  Methods          0             0
============================================
  Hit            864           864
  Partial          0             0
  Missed         174           174

Powered by Codecov

Closing, someone else will have to finish this off.


Update info for Forida, add hallways entry

Hey everyone,
Just a quick change, seeing that hallways has happened :)

Could you also add a way to contact you?

Absolutely! Sorry about that, forgot that entry :)


[Pickles] Avoid recomputation of cached verification keys

Changes what Pickles.Cache returns in read_or_generate, from a keypair (prover and verifier key, Impl.Keypair.t) to a prover key (Impl.Prover_key.t, which is just a Rust prover index).
The verifier key on the Keypair.t structure was never used, but still expensively recomputed when reading prover keys from cache.

!ci-build-me


Gliding speed

Is there a way to implement gliding speed modifiers? It would be nicer to have that over zipping around on the ground missing things at movement speed x2/x3

I'll be updating codes for TOTK after FF stuff, maybe i'll look.. (Games not interesting to me)


Cannot generate RTIC project

Whenever using cargo generate to create an RTIC project, the pre-script.rhai script fails, outputting:
Caused by:
Data type incorrect: string (expecting bool) (line 497, position 29)
Attempting to build for multiple different boards including just using default settings reproduces bug in all attempted instances.
Below is the code which breaks:
if variable::get("rtic") && rtic_feature {
    hal_dependency += "\"${rtic_feature}\", "
}

It looks like 40c0a63adfe9f65182b1d8c4ac3d86fe89c57b46 (master) should fix this issue.


Problem with QueryContainer

See the following code:
        [Fact]
        public void QueryContainer_MultipleOutputs_Test()
        {
            var container = new QueryContainer();

            var asset_subject = new Subject<StreamEvent<IONRecord_Struct>>();
            var assets_input = container.RegisterInput(asset_subject, identifier: "input1");

            var prices_subject = new Subject<StreamEvent<IONRecord_Struct>>();
            var prices_input = container.RegisterInput(prices_subject, identifier: "input2");

            var join = assets_input.Join(
                right: prices_input,
                leftKeySelector: l => l.Id,
                rightKeySelector: r => r.Id,
                resultSelector: (l, r) => new
                {
                    l.Id,
                    l.Data,
                    r_Data = r.Data,
                });
            container.RegisterOutput(join, identifier: "output1").Subscribe(onNext: p => Debug.Print($"{p}"));

            var left_join = assets_input
                .LeftOuterJoin(right: prices_input,
                    leftKeySelector: l => l.Id,
                    rightKeySelector: r => r.Id,
                    outerResultSelector: l => new
                    {
                        l.Id,
                        l.Data,
                        r_Data = string.Empty,
                    },
                    innerResultSelector: (l, r) => new
                    {
                        l.Id,
                        l.Data,
                        r_Data = r.Data
                    });

            //NEXT LINE THROWS !??
            //System.InvalidOperationException: 'Operation is not valid due to the current state of the object.'
            container.RegisterOutput(left_join, identifier: "output2").Subscribe(onNext: p => Debug.Print($"{p}"));

            var process = container.Restore(inputStream: null);
        }

OK, this answer is going to be verbose and yet totally unsatisfying:
This is by design.
That's the unsatisfying part. Here's the verbose part.
The root cause of this issue is that you have two streamable variables (assets_input and prices_input) that are being used in multiple places within your query. Trill follows the same semantics as Rx - each subscription causes an independent chain of subscriptions through the query down to the input sources, and each ends up being a separate stream of actual data flowing through.
Without the QueryContainer, what results from that situation is stream duplication.  However, with a QueryContainer, that situation is bad when having to deal with checkpointing. It messes up our ability to tell what has and what has not been checkpointed yet, and causes some potential race conditions in restoration. In short, reusing a stream variable is "a bad idea" without a QueryContainer and simply not allowed with one.
The proximate solution for you in this case is to do a multicast on assets_input and prices_input, so you can reuse those streams while avoiding the situation stated above. It would look like:
var assets_multi = assets_input.Multicast[2];
var prices_multi = prices_input.Multicast[2];
var join = assets_multi[0].Join(prices_multi[0], ...)
var leftJoin = assets_multi[1].LeftOuterJoin(prices_multi[1], ...)
That said, this is what we call in the business a really bad user experience. There's no way that you could have figured this out from just the code. So at a minimum, I'm going to go in and see if there is a better way to communicate this issue to the user.
On top of that, there is a design issue. We decided early on to inherit from Rx semantics and have separate subscription chains for every caller. However, it's clear from user feedback that said semantics are confusing. I'm not even sure that Rx it totally happy with what they did. So we may go back and try to change the design to only have a single subscription chain irrespective of how many times a variable is used. That's a major change, so it's not something that will happen in the next few months, but one that comes up every now and then as a request and that we will seriously consider.

Thanks James. As always, your explanations are very clear.
Is this exactly what happens behind the Multicast operator?

...there is a design issue. We decided early on to inherit from Rx semantics and have separate subscription chains for every caller. However, it's clear from user feedback that said semantics are confusing. I'm not even sure that Rx it totally happy with what they did. So we may go back and try to change the design to only have a single subscription chain irrespective of how many times a variable is used.

I think I ran into this when starting with Rx and I've certainly spent time on this when teaching others. What would we lose by not having separate subscriptions or why do you think the Rx design went that route in the first place?

@nsulikowski Correct, apologies. I will go back and edit my comment.
@NickDarvey I think the Rx design is based on the semantics of Enumerable. I know that a lot of the work that went into Rx semantics are based on the theory that IObservable is a dual of IEnumerable. A subscription in that case is a "dual" of an enumeration, and each enumeration of an IEnumerable starts at the beginning and is independent of one another. As such, each subscription in essence "begins" at the beginning of the observable (even though in practice the IObservable may not be able to "reset" back to its original state on each subscription).
That explains why it's where we are, but concretely, what would we lose if we switch to assuming multicast on each variable reuse? Honestly, I'm not sure. In Rx, there may be something lost, but in the streaming world, I cannot help but think that we'd be better off assuming that variables are more like branches in a stream than adhering to an inherited semantics.


(Squashed) Merged initial request but not activated.

I have accept the PR/Merged the branch, but the project is not activated and the branch deleted.
Will the Bot check again or what did i need to do?

Hey @Dexus,
I just looked into your recent activity and found this: https://github.com/Dexus/node-sofort/pull/4
It looks like you created the PR for Greenkeeper's intial branch yourself.
Usually Greenkeeper would create that PR on its own, as soon as there are test results available from a CI service (e.g. Travis CI), but it looks like you don't have a CI service set up.
The enabling flow usually looks like this: https://github.com/greenkeeperio/greenkeeper/pull/382
Can you setup a CI service (e.g. Travis CI is free for open source) and reinstall the integration again?
Let me know how that worked.
Best,
Stephan

@boennemann I'm not sure if it's the same issue here, but https://github.com/alphasights/ember-graphql-adapter/pull/74 was merged and the badge still says "disabled" on the repo.


Backport ACMEv2 support

Upgrade simp_le
Swap out the acme module to support new plugin for activation

Thanks for opening this

Related: #557

Closing since this was merged to develop in #557.


Where is your model MNTDP's network structure

Hi Tom:
I'm very happy to see your paper with code. Regarding the code, I would like to ask you two questions:

Which one of src/moduls/ is the network of your algorithm MNTDP?
Where do the supernets in src/moduls/utils.py come from?

Thanks

Hi,
Thanks for your interest in our work.

MNTDP is using the ProgressiveSSN class defined here: https://github.com/TomVeniat/MNTDP/blob/d1e1beceddae6b6e66a61525fe61e42a55c5d53d/src/modules/PSSN_llmodel.py#L52
Do not hesitate if you need more help as the current version of this class contains a lot of things!

supernets can be obtained using the following steps:

git clone -b channel_sampling https://github.com/TomVeniat/SuperNetworks
cd SuperNetworks
pip install .

Thank you for raising these points, I will update the project today to fix these issues and add more guidance on how to launch trainings !

Hi,
You can now use the dev branch, in which you'll find the MNTDP class and updated requirements.
I need to do some more testing before merging into master but it should be functional as-is.


Initialized the angular project

Added header with theme switcher
Implemented the room creation page

@pavelSaikov How can I get rid of the validation style in the deck field? I want when the page opens, then there was no validation yet. Validation should happen when the user works with the field.


KBC-2761 improve base methods that sends requests

Jira: KBC-2761
Before asking for review make sure that:
Checklist

[x] New client method(s) has tests
[x] Apiary file is updated

Release

[x] I gave the PR a proper label:

major (BC break)
minor (new feature)
patch (backwards compatible fix)
no release (just test changes)

:eyes:


MFA_Enforced SQL errors on login of newly migrated Bookstack instance

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
I'm trying to migrate my data from one Ubuntu 20.04 LTS VM running Bookstack v0.31.7 to a new Ubuntu VM running Bookstack v22.03. I've successfully copied over the database and files required and fixed bookstack SQL login info. However, when I try to log into the new instance I get this error:
[previous exception] [object] (PDOException(code: 42S22): SQLSTATE[42S22]: Column not found: 1054 Unknown column 'mfa_enforced' in 'where clause' at /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php:368)
I believe this has something to do with us enabling Okta SSO in the original bookstack instance. I tried commenting out the Okta specific values in the .env file which doesn't have any impact on the problem. Trying to figure out how to manually resolve this.
laravel.log
Exact BookStack Version
v22.03
Log Content

Stack Trace
[previous exception] [object] (PDOException(code: 42S22): SQLSTATE[42S22]: Column not found: 1054 Unknown column 'mfa_enforced' in 'where clause' at /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php:368)
[stacktrace]
#0 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php(368): PDO->prepare()
#1 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php(705): Illuminate\\Database\\Connection->Illuminate\\Database\\{closure}()
#2 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php(672): Illuminate\\Database\\Connection->runQueryCallback()
#3 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php(376): Illuminate\\Database\\Connection->run()
#4 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(2736): Illuminate\\Database\\Connection->select()
#5 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(1657): Illuminate\\Database\\Query\\Builder->exists()
#6 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Support/Traits/ForwardsCalls.php(23): Illuminate\\Database\\Eloquent\\Builder->__call()
#7 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Support/Traits/ForwardsCalls.php(52): Illuminate\\Database\\Eloquent\\Relations\\Relation->forwardCallTo()
#8 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Relations/Relation.php(481): Illuminate\\Database\\Eloquent\\Relations\\Relation->forwardDecoratedCallTo()
#9 /var/www/bookstack/app/Auth/Access/Mfa/MfaSession.php(34): Illuminate\\Database\\Eloquent\\Relations\\Relation->__call()
#10 /var/www/bookstack/app/Auth/Access/Mfa/MfaSession.php(15): BookStack\\Auth\\Access\\Mfa\\MfaSession->userRoleEnforcesMfa()
#11 /var/www/bookstack/app/Auth/Access/LoginService.php(134): BookStack\\Auth\\Access\\Mfa\\MfaSession->isRequiredForUser()
#12 /var/www/bookstack/app/Auth/Access/LoginService.php(37): BookStack\\Auth\\Access\\LoginService->needsMfaVerification()
#13 /var/www/bookstack/app/Auth/Access/LoginService.php(159): BookStack\\Auth\\Access\\LoginService->login()
#14 /var/www/bookstack/app/Http/Controllers/Auth/LoginController.php(151): BookStack\\Auth\\Access\\LoginService->attempt()
#15 /var/www/bookstack/app/Http/Controllers/Auth/LoginController.php(120): BookStack\\Http\\Controllers\\Auth\\LoginController->attemptLogin()
#16 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(54): BookStack\\Http\\Controllers\\Auth\\LoginController->login()
#17 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(45): Illuminate\\Routing\\Controller->callAction()
#18 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Route.php(262): Illuminate\\Routing\\ControllerDispatcher->dispatch()
#19 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Route.php(205): Illuminate\\Routing\\Route->runController()
#20 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Router.php(721): Illuminate\\Routing\\Route->run()
#21 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(128): Illuminate\\Routing\\Router->Illuminate\\Routing\\{closure}()
#22 /var/www/bookstack/app/Http/Middleware/CheckGuard.php(27): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#23 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): BookStack\\Http\\Middleware\\CheckGuard->handle()
#24 /var/www/bookstack/app/Http/Middleware/RedirectIfAuthenticated.php(31): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#25 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): BookStack\\Http\\Middleware\\RedirectIfAuthenticated->handle()
#26 /var/www/bookstack/app/Http/Middleware/Localization.php(83): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#27 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): BookStack\\Http\\Middleware\\Localization->handle()
#28 /var/www/bookstack/app/Http/Middleware/RunThemeActions.php(26): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#29 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): BookStack\\Http\\Middleware\\RunThemeActions->handle()
#30 /var/www/bookstack/app/Http/Middleware/CheckEmailConfirmed.php(47): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#31 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): BookStack\\Http\\Middleware\\CheckEmailConfirmed->handle()
#32 /var/www/bookstack/app/Http/Middleware/PreventAuthenticatedResponseCaching.php(21): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#33 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): BookStack\\Http\\Middleware\\PreventAuthenticatedResponseCaching->handle()
#34 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php(78): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#35 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\\Foundation\\Http\\Middleware\\VerifyCsrfToken->handle()
#36 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php(49): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#37 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\\View\\Middleware\\ShareErrorsFromSession->handle()
#38 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(121): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#39 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(64): Illuminate\\Session\\Middleware\\StartSession->handleStatefulRequest()
#40 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\\Session\\Middleware\\StartSession->handle()
#41 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#42 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\\Cookie\\Middleware\\AddQueuedCookiesToResponse->handle()
#43 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(67): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#44 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\\Cookie\\Middleware\\EncryptCookies->handle()
#45 /var/www/bookstack/app/Http/Middleware/ApplyCspRules.php(33): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#46 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): BookStack\\Http\\Middleware\\ApplyCspRules->handle()
#47 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#48 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Router.php(723): Illuminate\\Pipeline\\Pipeline->then()
#49 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Router.php(698): Illuminate\\Routing\\Router->runRouteWithinStack()
#50 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Router.php(662): Illuminate\\Routing\\Router->runRoute()
#51 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Router.php(651): Illuminate\\Routing\\Router->dispatchToRoute()
#52 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(167): Illuminate\\Routing\\Router->dispatch()
#53 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(128): Illuminate\\Foundation\\Http\\Kernel->Illuminate\\Foundation\\Http\\{closure}()
#54 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Http/Middleware/TrustProxies.php(39): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#55 /var/www/bookstack/app/Http/Middleware/TrustProxies.php(41): Illuminate\\Http\\Middleware\\TrustProxies->handle()
#56 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): BookStack\\Http\\Middleware\\TrustProxies->handle()
#57 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#58 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TrimStrings.php(40): Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest->handle()
#59 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\\Foundation\\Http\\Middleware\\TrimStrings->handle()
#60 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#61 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\\Foundation\\Http\\Middleware\\ValidatePostSize->handle()
#62 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php(86): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#63 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\\Foundation\\Http\\Middleware\\PreventRequestsDuringMaintenance->handle()
#64 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#65 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(142): Illuminate\\Pipeline\\Pipeline->then()
#66 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(111): Illuminate\\Foundation\\Http\\Kernel->sendRequestThroughRouter()
#67 /var/www/bookstack/public/index.php(53): Illuminate\\Foundation\\Http\\Kernel->handle()
#68 {main}
"}

PHP Version
7.4
Hosting Environment
Ubuntu 20.04

Hi @eferreira2,

I believe this has something to do with us enabling Okta SSO in the original bookstack instance.

I don't think that's related at all. The error you are getting is due to the table structure not being as expected.
When you restore to a new instance it's very important that you restore the old database dump before any of the app-managed database migrations are ran, so there should ideally be no pre-existing tables in the database you restore into.
After that you'd then run the app-managed migrations via php artisan migrate to update your old data to the latest required state.
Doing the above steps in the wrong order, or not running each of them, may result in the kind of error you are experiencing.

Hi Dan,
Thanks for the info. I was able to fix the problem based on your input:

Deleted bookstack instance
Cleared out bookstack database
Imported database using the backup & restore commands
Commented out php artisan migrate in the Ubuntu install script
Ran Ubuntu install script
Performed php artisan migrate afterward