Junyung/mutator changes

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Hi RAVEN team, do you think we can review/merge this in the next week or so? (This seems very promising).

@wangcj05 @mandd @Jimmy-INL is there anything we can do to help for this review/MR?

I think @mandd is in charge of this PR. @mandd Is it possible that you can split this PR into at least two separate PRs? One for mutator changes so that we can review and merge into devel soon, and the other one for the fix in ensemble model.

@mandd ?

@JunyungKim the precheck is failing and I saw also the the test if I remember correctly

Diego, please let us know if this PR has any issues. I might need it merged before my visit to FPoli this Monday.
Mohammad G. Abdo, Ph.D.
Modeling and Simulation Scientist   |  Digital Reactor Technology and Development (C160)
Reactor Systems Design and Analysis   |   NS&T
<EMAIL_ADDRESS> |  REC EROB IF-654 3EM402  |  Phone:<PHONE_NUMBER>
Idaho National Laboratory   |   2525 Fremont Ave.   |   Idaho Falls, ID   |   83415
[6GC4jc7QCCEAAAAASUVORK5CYII=]https://www.linkedin.com/in/mohammad-abdo-a7625082/.               [PXly9OZ1PK9LcRv4PSG3pAb9jevQAAAAASUVORK5CYII=] https://www.researchgate.net/profile/Mohammad_Abdo/research                 [RPr5ytnPx9Cc691m9I+4T+nIo7v4HxgxndxMwKP8AAAAASUVORK5CYII=] https://github.com/Jimmy-INL

[wYtJH347IiIiAYVYS1skEvgxC4KpkYRTFRBbsT51peEIp5j0ExRuvWouzr1J+za4DYirM+SlQmTZXUTsvjtVtouILWngWSxC+xJbAP86Fg5oVmy2ERH1w38A8nnHfeT8na8AAAAASUVORK5CYII=]
From: Andrea Alfonsi @.>
Date: Wednesday, November 9, 2022 at 10:16 AM
To: idaholab/raven @.>
Cc: Mohammad G. Abdo @.>, Mention @.>
Subject: [EXTERNAL] Re: [idaholab/raven] Junyung/mutator changes (PR #1993)
@manddhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmandd&data=05|01|mohammad.abdo%40inl.gov|d88cdd4becd84220923608dac27627b4|4cf464b7869a42368da2a98566485554|0|0|638036109997143902|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Ky%2B4YC%2FJqi92reOn5246uXSsKYx7kIECETliKaP5LDE%3D&reserved=0 ?
—
Reply to this email directly, view it on GitHubhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fidaholab%2Fraven%2Fpull%2F1993%23issuecomment-1309082171&data=05|01|mohammad.abdo%40inl.gov|d88cdd4becd84220923608dac27627b4|4cf464b7869a42368da2a98566485554|0|0|638036109997143902|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=4tp663aEenC0bWr8J3jKCLmYnjADOP%2FfsrFc%2B%2FzXTUc%3D&reserved=0, or unsubscribehttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMP5ECT45AZR4YEER5SZEVLWHPL7FANCNFSM6AAAAAARDRMM24&data=05|01|mohammad.abdo%40inl.gov|d88cdd4becd84220923608dac27627b4|4cf464b7869a42368da2a98566485554|0|0|638036109997143902|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=jCvot%2BrXCRY%2FObhsGajtTp1TUlXWIB1X84Ii9djHQ0Q%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@JunyungKim the precheck is failing and I saw also the the tests if I remember correctly

@JunyungKim ?

I think this PR should be removed, it has been recreated and merged with #1968.
We should remove the WIP from #1968 to start seeing the tests. @mandd can you please try that?

This PR is closed: All necessary changes are reflected in mandd/mutatorChanges


ASN.1 from 3GPP 38.331 Rel.16 standards don't compile

Good day to you all,
Parsing ASN.1 specs extracted from 3GPP 38.331 release 16 standards always throw this error (at different lines in different versions of the spec):
ASN.1 grammar parse error near 38331-g31-asn1.txt:6545 (token "[["): syntax error, unexpected TOK_VBracketLeft
The identical ASN.1 spec. compiled successfully in https://asn1.io/asn1playground/
However, asn1c does compile 3GPP 38.331 release 15 ASN.1 specs. without this error. Any hints on how to fix this issue?
All the best
James
38331-g31-asn1.txt
asn1playground.txt

the current version of ref 16 seems to be 38331-gf1 (3gpp/latest/Rel-16/38_series/)
Today I could compile

38331-fo1
38331-gf1
38331-h70
(Refs 15-17)
with mouse07410's version: https://github.com/mouse07410/asn1c

Ref 18 (i00) raises syntax errors though:
ASN.1 grammar parse error near 38331-i00.asn1:4887 (token "}"): syntax error
Cannot parse "38331-i00.asn1"


Install + run Docker Desktop without admin privileges

Tell us about your request

Allow users to install and run Docker Desktop without entering any admin privileges.

Which service(s) is this request for?

Docker Desktop for Mac
Docker Desktop for Windows (WSL2 only. This will not be possible for Hyper-V)

Additional context
We recently adjusted the Docker Desktop for Mac permission requirements to allow users to provide admin privileges at install (via the CLI) rather than at first run. This prevents the privileged com.docker.vmnetd service from running in the background while Docker Desktop is in use. It's also useful in Enterprise environments where users don't have root access on their machines and require admins to install Docker Desktop on their behalf.
Our next step is to completely remove the need for admin privileges during install and run of Docker Desktop.

Thanks for the feedback @the-neil ! We're currently working on a couple of new UX flows for this and aiming to implement very soon, as a top priority. I wonder if I could schedule 30 mins with you to get some feedback ? If so, please do reach out via<EMAIL_ADDRESS>Thanks again !

Is there any date of release for the public announced ? I would really enjoy this feature !

Hi @symsym-1629 , this will be ready for the upcoming v4.18 of Docker Desktop, which will be released at the end of March. Thanks for your feedback !

Docker's roadmap and execution track record literally restores my faith in humanity regularly

Hello ! just flagging that v4.18 was released yesterday and includes a new install flow for macOS, making it easier to install + run Docker Desktop without admin privileges. A big thank you to those of you that spent some time with us reviewing the flows and providing your feedback. Much appreciated !

Is there a way you could post what is this new install flow? Because I can't see anything anywhere.

I would second/third/fourth this. What's the procedure to prevent admin for the first time run on a mac

Hi @giancarloerra and @Ragnar-von-Detroit, the new install flow that allows you to use Docker Desktop for Mac without admin privileges only appears for fresh installs of Docker Desktop versions >= 4.18.
If you already have Docker Desktop installed, you can do as follows:

Update to most recent version
Go to 'Settings > Advanced'
Deselect all options that have 'requires password' beside them (this will ensure DD runs on your machine without admin privileges)

Alternatively, you can uninstall and reinstall the latest version, to get the new install flow.
Cheers,
Chris

I would much like to know if there is any progress in the foreseeable future that the Linux docker desktop gets consistent permission settings. As if now there only seem to be a big workaround that keeps main user from being permissions owner instead of root which leads to chaotic permissions and manual setting of permissions.

This was moved to "Shipped! Enjoy!" on May 28. Can you confirm which version this is shipped in? I just downloaded the latest Docker Desktop for Windows installer (4.30.0, according to the release notes) and the installer is still asking for admin rights.

I think this was only implemented for macOS (https://github.com/docker/roadmap/issues/413#issuecomment-1499103070), not Windows.

@tianon-sso yeah that comment was 2023 which is why I asked. Since the issue detail includes the Windows version, what will happen to that part?

Still not available on windows


Cypress/E2E: Fix more unreads position with scroll spec

Summary

Fixed scrolling so that indicators show/hide properly.

Ticket Link
NA

/update-branch


Updates cannot be received through insomnia APT repository.

Expected Behavior
Installing Insomnia through the apt repository after the versioning change from 2023.X.X to 8.X.X should detect 8.X.X as the latest version.
Actual Behavior
In installations through apt repository , something similar to what was described in #6612 also occurs. When the apt update command is executed, the latest detected version is 2023.5.8 instead of 8.X.X .
Reproduction Steps
No response
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
Additionally, if you run apt list -a insomnia, you can notice that versions 202X.X.X are treated as more recent and take precedence over versions 8.X.X.
insomnia/unknown,now 2023.5.8 amd64 [installed]
insomnia/unknown 2023.5.7 amd64
insomnia/unknown 2023.5.6 amd64
insomnia/unknown 2023.5.5 amd64
insomnia/unknown 2023.5.4 amd64
insomnia/unknown 2023.5.3 amd64
insomnia/unknown 2023.5.2 amd64
insomnia/unknown 2023.5.1 amd64
insomnia/unknown 2023.5.0 amd64
insomnia/unknown 2023.3.0 amd64
insomnia/unknown 2023.2.2 amd64
insomnia/unknown 2023.2.1 amd64
insomnia/unknown 2023.2.0 amd64
insomnia/unknown 2023.1.0 amd64
insomnia/unknown 2022.7.5 amd64
insomnia/unknown 2022.7.4 amd64
insomnia/unknown 2022.7.3 amd64
insomnia/unknown 2022.7.2 amd64
insomnia/unknown 2022.7.1 amd64
insomnia/unknown 2022.7.0 amd64
insomnia/unknown 2022.6.0 amd64
insomnia/unknown 2022.5.1 amd64
insomnia/unknown 2022.5.0 amd64
insomnia/unknown 2022.4.2 amd64
insomnia/unknown 2022.4.1 amd64
insomnia/unknown 2022.4.0 amd64
insomnia/unknown 2022.3.0 amd64
insomnia/unknown 2022.2.1 amd64
insomnia/unknown 2022.2.0 amd64
insomnia/unknown 2022.1.1 amd64
insomnia/unknown 2022.1.0 amd64
insomnia/unknown 2021.7.2 amd64
insomnia/unknown 2021.7.1 amd64
insomnia/unknown 2021.7.0 amd64
insomnia/unknown 2021.6.0 amd64
insomnia/unknown 2021.5.3 amd64
insomnia/unknown 2021.5.2 amd64
insomnia/unknown 2021.5.1 amd64
insomnia/unknown 2021.5.0 amd64
insomnia/unknown 2021.4.1 amd64
insomnia/unknown 2021.4.0 amd64
insomnia/unknown 2021.3.0 amd64
insomnia/unknown 2021.2.2 amd64
insomnia/unknown 8.5.1 amd64
insomnia/unknown 8.5.0 amd64
insomnia/unknown 8.4.5 amd64
insomnia/unknown 8.4.4 amd64
insomnia/unknown 8.4.3 amd64
insomnia/unknown 8.4.2 amd64
insomnia/unknown 8.4.1 amd64
insomnia/unknown 8.4.0 amd64
insomnia/unknown 8.3.0 amd64
insomnia/unknown 8.2.0 amd64
insomnia/unknown 8.1.0 amd64
insomnia/unknown 8.0.0 amd64

Insomnia Version
2023.5.8
What operating system are you using?
Ubuntu
Operating System Version
Ubuntu 23.10 x86_64
Installation method
Official apt repository
Last Known Working Insomnia version
No response

Hey @cesar19004!
Kong Inc. employee in charge of package hosting here.
Because there will not be a way to convince apt to sort the packages in any other way besides semver in a single repo, I've opted to populate a new repo with the 202[1..3]-versioned packages, and leave the default repo for 8.x.y packages.
We are also in the process of changing our package hosting to Cloudsmith.
The repos are:

Main (8.x.y verisoning): https://cloudsmith.io/~kong/repos/insomnia/packages/?sort=-version
Legacy (202x.y.z versioning): https://cloudsmith.io/~kong/repos/insomnia-legacy/packages/?sort=-version

Setup instructions can be found here: https://cloudsmith.io/~kong/repos/insomnia/setup/#formats-deb
After you setup the repo, to allow apt to install an 8.x.y version while removing a 202x version, you will need --allow-downgrades.
Let me know if you need any help or if that resolves this issue.

Hello, thanks for the response.
Nice, splitting the repository sounds good. I tried to install it using Ubuntu 23.10, but the following URL, which is used to retrieve the deb configuration file and check if the distribution is supported https://packages.konghq.com/public/insomnia/config.deb.txt?distro=${distro}&codename=${codename}&version=${version}&arch=${arch}, returns a valid configuration file for any version of Ubuntu and an HTTP status code of 200, even though there are only packages for Ubuntu Focal Fossa. In any case, forcing the installation using Focal as the Ubuntu version worked well, and I could upgrade to version 8.6.0.

@curiositycasualty, as @cesar19004 said, only the focal codename returns a valid configuration; the jammy for example (latest LTS) doesn't.


Still seeing sporatic LFTP timeouts that seem to lock up the thread

I am seeing LFTP timeouts that seem to lock the thread so that it cannot be used again unless the service is restarted.
After a while, I have noticed that the DL speeds would cap out at a very low level.

The speeds would not resume to normal until after I restart the service.

Nothing jumps out in the logs -aside from the timeout that is.
2022/03/29 10:49:28 - ERROR - seedsync.Controller.Lftp - Lftp timeout exception
Traceback (most recent call last):
File "lftp/lftp.py", line 128, in __run_command
File "pexpect/spawnbase.py", line 343, in expect
File "pexpect/spawnbase.py", line 372, in expect_list
File "pexpect/expect.py", line 181, in expect_loop
File "pexpect/expect.py", line 144, in timeout
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x7f6f01dfd4c0>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', 'XXXXXXXXX,XXXXXXXXXXXXXX', 'sftp://XXXX.XXXXXXXX.XX']
buffer (last 100 chars): b' '
before (last 100 chars): b' '
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 21081
child_fd: 28
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXXX@XXXXXXXX.XX:.>')
2022/03/29 10:49:32 - ERROR - seedsync.Controller.Lftp - Lftp timeout exception
Traceback (most recent call last):
File "lftp/lftp.py", line 128, in __run_command
File "pexpect/spawnbase.py", line 343, in expect
File "pexpect/spawnbase.py", line 372, in expect_list
File "pexpect/expect.py", line 181, in expect_loop
File "pexpect/expect.py", line 144, in timeout
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x7f6f01dfd4c0>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', 'XXXXXXXXX,XXXXXXXXXXXXXX', 'sftp://XXXX.XXXXXXXX.XX']
buffer (last 100 chars): b' '
before (last 100 chars): b' '
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 21081
child_fd: 28
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXXX@XXXXXXXX.XX:.>')
2022/03/29 10:50:10 - ERROR - seedsync.Controller.Lftp - Lftp timeout exception
Traceback (most recent call last):
File "lftp/lftp.py", line 128, in __run_command
File "pexpect/spawnbase.py", line 343, in expect
File "pexpect/spawnbase.py", line 372, in expect_list
File "pexpect/expect.py", line 181, in expect_loop
File "pexpect/expect.py", line 144, in timeout
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x7f6f01dfd4c0>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', 'XXXXXXXXX,XXXXXXXXXXXXXX', 'sftp://XXXX.XXXXXXXX.XX']
buffer (last 100 chars): b' '
before (last 100 chars): b' '
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 21081
child_fd: 28
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXXX@XXXXXXXX.XX:.>')
2022/03/29 10:50:14 - ERROR - seedsync.Controller.Lftp - Lftp timeout exception
Traceback (most recent call last):
File "lftp/lftp.py", line 128, in __run_command
File "pexpect/spawnbase.py", line 343, in expect
File "pexpect/spawnbase.py", line 372, in expect_list
File "pexpect/expect.py", line 181, in expect_loop
File "pexpect/expect.py", line 144, in timeout
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x7f6f01dfd4c0>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', 'XXXXXXXXX,XXXXXXXXXXXXXX', 'sftp://XXXX.XXXXXXXX.XX']
buffer (last 100 chars): b' '
before (last 100 chars): b' '
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 21081
child_fd: 28
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXXX@XXXXXXXX.XX:.>')
2022/03/29 10:50:17 - ERROR - seedsync.Controller.Lftp - Lftp timeout exception
Traceback (most recent call last):
File "lftp/lftp.py", line 128, in __run_command
File "pexpect/spawnbase.py", line 343, in expect
File "pexpect/spawnbase.py", line 372, in expect_list
File "pexpect/expect.py", line 181, in expect_loop
File "pexpect/expect.py", line 144, in timeout
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x7f6f01dfd4c0>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', 'XXXXXXXXX,XXXXXXXXXXXXXX', 'sftp://XXXX.XXXXXXXX.XX']
buffer (last 100 chars): b' '
before (last 100 chars): b' '
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 21081
child_fd: 28
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXXX@XXXXXXXX.XX:.>')
2022/03/29 10:50:56 - ERROR - seedsync.Controller.Lftp - Lftp timeout exception
Traceback (most recent call last):
File "lftp/lftp.py", line 128, in __run_command
File "pexpect/spawnbase.py", line 343, in expect
File "pexpect/spawnbase.py", line 372, in expect_list
File "pexpect/expect.py", line 181, in expect_loop
File "pexpect/expect.py", line 144, in timeout
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x7f6f01dfd4c0>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', 'XXXXXXXXX,XXXXXXXXXXXXXX', 'sftp://XXXX.XXXXXXXX.XX']
buffer (last 100 chars): b' '
before (last 100 chars): b' '
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 21081
child_fd: 28
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXXX@XXXXXXXX.XX:.>')
2022/03/29 10:50:59 - ERROR - seedsync.Controller.Lftp - Lftp timeout exception
Traceback (most recent call last):
File "lftp/lftp.py", line 128, in __run_command
File "pexpect/spawnbase.py", line 343, in expect
File "pexpect/spawnbase.py", line 372, in expect_list
File "pexpect/expect.py", line 181, in expect_loop
File "pexpect/expect.py", line 144, in timeout
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x7f6f01dfd4c0>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', 'XXXXXXXXX,XXXXXXXXXXXXXX', 'sftp://XXXX.XXXXXXXX.XX']
buffer (last 100 chars): b' '
before (last 100 chars): b' '
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 21081
child_fd: 28
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXXX@XXXXXXXX.XX:.>')
2022/03/29 10:51:03 - ERROR - seedsync.Controller.Lftp - Lftp timeout exception
Traceback (most recent call last):
File "lftp/lftp.py", line 128, in __run_command
File "pexpect/spawnbase.py", line 343, in expect
File "pexpect/spawnbase.py", line 372, in expect_list
File "pexpect/expect.py", line 181, in expect_loop
File "pexpect/expect.py", line 144, in timeout
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x7f6f01dfd4c0>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', 'XXXXXXXXX,XXXXXXXXXXXXXX', 'sftp://XXXX.XXXXXXXX.XX']
buffer (last 100 chars): b' jobs -v\r\n'
before (last 100 chars): b' jobs -v\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 21081
child_fd: 28
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXXX@XXXXXXXX.XX:.>')

I'm having these issues. It takes like 4-5 attempts to start a download and half of the time I need to restart the service.

I happened across an article that referred to LFTP default settings. In there are timeouts and retries settings.
It would be great to have access to those settings. I tried editing the etc/lftp.conf file but there is no nano or vim installed and I am unable to install those on the Docker container. I also am unable to so anything sudo as sudo does not exist.
There was an article that apparently explained how to add sudo to a docker container but my brain broke trying to figure it out.
But, adding vars to account for the LFTP settings or, exposing the conf file in the containers persistent settings would be an awesome addition to help tweak LFTP.
https://askubuntu.com/questions/1012006/lftp-default-timeout-and-retry

Here is the complete list of default LFTP settings in the system
lftp :~> set -d set bmk:auto-sync yes set bmk:save-passwords no set cache:cache-empty-listings no set cache:enable yes set cache:expire 60m set cache:expire-negative 1m set cache:size 16M set cmd:at-background "" set cmd:at-exit "" set cmd:at-exit-bg "" set cmd:at-exit-fg "" set cmd:at-finish "" set cmd:at-queue-finish "" set cmd:at-terminate "" set cmd:cls-completion-default -FBa set cmd:cls-default -F set cmd:cls-exact-time yes set cmd:csh-history off set cmd:default-protocol ftp set cmd:default-title "lftp \\h:\\w" set cmd:fail-exit no set cmd:interactive auto set cmd:long-running 30 set cmd:ls-default "" set cmd:move-background yes set cmd:move-background-detach yes set cmd:nullglob yes set cmd:parallel 1 set cmd:prompt "lftp \\S\\? \\u\\@\\h:\\w> " set cmd:queue-parallel 1 set cmd:remote-completion on set cmd:save-cwd-history yes set cmd:save-rl-history yes set cmd:set-term-status no set cmd:show-status yes set cmd:status-interval 0.8s set cmd:stifle-rl-history 500 set cmd:term-status "" set cmd:time-style "%b %e  %Y|%b %e %H:%M" set cmd:trace no set cmd:verbose no set cmd:verify-host yes set cmd:verify-path yes set cmd:verify-path-cached no set color:dir-colors "" set color:use-color auto set dns:SRV-query no set dns:cache-enable yes set dns:cache-expire 1h set dns:cache-size 256 set dns:fatal-timeout 7d set dns:max-retries 1000 set dns:name "" set dns:order "inet6 inet" set dns:use-fork yes set file:charset "" set file:use-fallocate yes set file:use-lock no set fish:auto-confirm no set fish:charset "" set fish:connect-program "ssh -a -x" set fish:shell /bin/sh set ftp:abor-max-wait 15s set ftp:acct "" set ftp:anon-pass lftp@ set ftp:anon-user anonymous set ftp:auto-passive-mode yes set ftp:auto-sync-mode "" set ftp:bind-data-socket yes set ftp:catch-size yes set ftp:charset "" set ftp:client lftp/4.8.4 set ftp:compressed-re "\\.(bz2|[glrsx7]z|lzma|lz[hox]|[ai]ce|apk|ar[cj]|cab|cfs|dar|[je]ar|lha|isz|pak|rar|sitx?|t(gz|bz2|lz)|tar\\.(gz|xz|bz2|lzma)|war|zipx?|zoo|[arz0][0-9][0-9])$" set ftp:device-prefix no set ftp:fix-pasv-address yes set ftp:fxp-force no set ftp:fxp-passive-source no set ftp:fxp-passive-sscn yes set ftp:home "" set ftp:ignore-pasv-address no set ftp:lang "" set ftp:list-empty-ok no set ftp:list-options "" set ftp:mode-z-level 6 set ftp:netkey-allow yes set ftp:nop-interval 120 set ftp:passive-mode on set ftp:port-ipv4 "" set ftp:port-range full set ftp:prefer-epsv no set ftp:proxy "" set ftp:proxy-auth-type user set ftp:rest-list no set ftp:rest-stor yes set ftp:retry-530 "too many|overloaded|try (again |back )?later|is restricted to|maximum number|number of connect|only.*session.*allowed|more connection|already connected|simultaneous login" set ftp:retry-530-anonymous "Login incorrect" set ftp:site (nil) set ftp:site-group "" set ftp:skey-allow yes set ftp:skey-force no set ftp:ssl-allow yes set ftp:ssl-allow-anonymous no set ftp:ssl-auth TLS set ftp:ssl-copy-sid yes set ftp:ssl-data-use-keys yes set ftp:ssl-force no set ftp:ssl-protect-data no set ftp:ssl-protect-fxp no set ftp:ssl-protect-list yes set ftp:ssl-shutdown-timeout 5 set ftp:ssl-use-ccc no set ftp:stat-interval 1 set ftp:strict-multiline off set ftp:sync-mode on set ftp:timezone GMT set ftp:too-many-re "(Too many|No more) connections" set ftp:trust-feat no set ftp:use-abor yes set ftp:use-allo yes set ftp:use-feat yes set ftp:use-fxp yes set ftp:use-hftp yes set ftp:use-ip-tos no set ftp:use-mdtm yes set ftp:use-mdtm-overloaded no set ftp:use-mlsd yes set ftp:use-mode-z yes set ftp:use-pret yes set ftp:use-quit yes set ftp:use-site-chmod yes set ftp:use-site-idle no set ftp:use-site-utime yes set ftp:use-site-utime2 yes set ftp:use-size yes set ftp:use-stat yes set ftp:use-stat-for-list no set ftp:use-telnet-iac yes set ftp:use-tvfs auto set ftp:use-utf8 yes set ftp:verify-address no set ftp:verify-port no set ftp:waiting-150-timeout 5 set ftp:web-mode off set ftps:initial-prot "" set hftp:cache yes set hftp:cache-control "" set hftp:decode no set hftp:proxy "" set hftp:use-allprop no set hftp:use-authorization yes set hftp:use-head yes set hftp:use-mkcol no set hftp:use-propfind no set hftp:use-range yes set hftp:use-type yes set http:accept */* set http:accept-charset "" set http:accept-encoding "" set http:accept-language "" set http:authorization "" set http:cache yes set http:cache-control "" set http:cookie "" set http:decode yes set http:post-content-type application/x-www-form-urlencoded set http:proxy "" set http:put-content-type "" set http:put-method PUT set http:referer "" set http:set-cookies no set http:use-allprop no set http:use-mkcol yes set http:use-propfind no set http:use-range yes set http:user-agent lftp/4.8.4 set https:proxy "" set log:enabled no set log:file "" set log:level 9 set log:max-size 1M set log:prefix-error "**** " set log:prefix-note "---- " set log:prefix-recv "<--- " set log:prefix-send "---> " set log:show-ctx no set log:show-pid no set log:show-time no set mirror:dereference no set mirror:exclude-regex "(^|/)(\\.in\\.|\\.nfs)" set mirror:include-regex "" set mirror:no-empty-dirs no set mirror:order "*.sfv *.sig *.md5* *.sum * */" set mirror:overwrite no set mirror:parallel-directories yes set mirror:parallel-transfer-count 0 set mirror:require-source no set mirror:set-permissions yes set mirror:skip-noaccess no set mirror:sort-by name set mirror:use-pget-n 0 set module:path /usr/lib/lftp/4.8.4:/usr/lib/lftp set net:connection-limit 0 set net:connection-limit-timer 5m set net:connection-takeover yes set net:idle 3m set net:limit-max 0 set net:limit-rate 0:0 set net:limit-total-max 0 set net:limit-total-rate 0:0 set net:max-retries 1000 set net:no-proxy "" set net:persist-retries 0 set net:reconnect-interval-base 30 set net:reconnect-interval-max 600 set net:reconnect-interval-multiplier 1.5 set net:socket-bind-ipv4 "" set net:socket-bind-ipv6 "" set net:socket-buffer 0 set net:socket-maxseg 0 set net:timeout 5m set pget:default-n 5 set pget:min-chunk-size 1M set pget:save-status 10s set sftp:auto-confirm no set sftp:charset "" set sftp:connect-program "ssh -a -x" set sftp:max-packets-in-flight 16 set sftp:protocol-version 6 set sftp:server-program sftp set sftp:size-read 32k set sftp:size-write 32k set sftp:use-full-path yes set ssl:ca-file "" set ssl:cert-file "" set ssl:check-hostname yes set ssl:crl-file "" set ssl:key-file "" set ssl:priority "" set ssl:use-sni yes set ssl:verify-certificate yes set torrent:ip "" set torrent:ipv6 "" set torrent:max-peers 60 set torrent:port-range 6881-6889 set torrent:retracker "" set torrent:save-metadata yes set torrent:seed-max-time 30d set torrent:seed-min-peers 3 set torrent:stop-min-ppr 1.4 set torrent:stop-on-ratio 2.0 set torrent:timeout 7d set torrent:use-dht yes set xfer:auto-rename no set xfer:backup-suffix ~%Y%m%d%H%M%S~ set xfer:buffer-size 0x10000 set xfer:clobber no set xfer:destination-directory "" set xfer:disk-full-fatal no set xfer:eta-period 120 set xfer:eta-terse yes set xfer:keep-backup no set xfer:make-backup yes set xfer:max-redirections 5 set xfer:parallel 1 set xfer:rate-period 15 set xfer:temp-file-name .in.* set xfer:timeout 1d set xfer:use-temp-file no set xfer:verify no set xfer:verify-command ""

Some things that stuck out to me
set net:idle 3m -
This will time out a connection with no traffic after 3 minutes. That might be a bit long.
set net:max-retries 1000 -
This will cap how many times it will retry a transfer. While 1000 seems like it would be sufficient, I wonder if this limit gets hit and if the LFTP service is still running, that count might be getting stuck. That's why a restart of the service seems to open things back up again.
set net:reconnect-interval-base 30
set net:reconnect-interval-max 600
set net:reconnect-interval-multiplier 1.5
These values are in seconds (aside from the multiplier). The service will wait to reconnect after 30 seconds. After each subsequent failure to connect it will apply the multiplier to the current interval value, assign the result to the current reconnect time period and try again. If it fails again, the multiplier is used to calculate the next new reconnect time period. Up to the maximum reconnect time period which is set to 600 seconds. This to me seems a bit too long across the board. For a server to take 30 seconds to respond means there are other problems. Connections should be measured in milliseconds, not seconds.
set net:timeout 5m
Sets the network protocol timeout, in this case SFTP. 5 minutes is an eternity for a server to wait for a command, especially so for an automated system like Seedsync. This should be much much shorter.
The thought I had with most of these settings if these statistics are persisted when the service is started up. If that's the case then hitting the max on timeouts and retires would mean the server never recovers lost threads and dropped connections.
Perhaps the Seedsync UI, the scanner and LFTP need to be separate services. When the scanner detects changes on the server it starts up LFTP and starts transfers. Each queued item in the list, once completed, would shut down and restart the LFTP service for the next queued item so that the stats are cleared each time a new download starts. I know that this would kill simultaneous file downloads, but, each file downloaded would get all of the threads meaning each file would download faster. We are, after all, limited to the bandwidth our ISPs provide us. Whether you are downloading 1 file or 5 files at once, the bandwidth is spread across all downloads. Why not just get each individual file faster? That is actually how my config is set up. I always had corruption issues when I had it set to download multiple files at once.
Just a thought (and a hope).


proposal: x/net/websocket: add Config.DialContext

What version of Go are you using (go version)?

$ go version
go version go1.19.5 darwin/arm64

Does this issue reproduce with the latest release?
Yes.
What did you do?
websocket.DialConfig function can block indefinitely. While it's possible to specify the TLS connection timeout using the config parameter, the function calls the NewClient method that does read/write operations, and they can be blocked indefinitely.
Also because the code is so old, there is no way to provide context.Context to support cancellation.
What did you expect to see?
A way to not block the connection.

Hey what's the status of this, kinda curious

It's on the list for the proposal review committee.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

Have all concerns with this proposal been addressed?

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group

I have a CL that implements this: https://go-review.googlesource.com/c/net/+/463097#message-31956dbc4b1568dbd323fd81a18b6a1fcb016c9e


Specify namespace when describing deployments (#1519)

Issue #, if available:
Description of changes:
Committing #1519 again after confirming that it works locally
Testing (if applicable):
Ran multiple e2e tests with the changes
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Testing this along with https://github.com/aws/eks-anywhere/pull/1530


hmr? (hot module reloading)

Most clis enable users with a watch command

rollup
eleventy
typescript
nodemon
vite
Letting sern deal with this would be very convenient for users.
We could also just include it in the future with global plugins, once compatibility branch rolls around

I'm not sure @EvolutionX-10 is here

He's taking his long break I think

Can we do it without him?

need his permission as he's author.

🤔 weren't you the owner?

Most clis enable users with a watch command

rollup
eleventy
typescript
nodemon
vite
Letting sern deal with this would be very convenient for users.
We could also just include it in the future with global plugins, once compatibility branch rolls around

sern watch ?
what things will it do 🤔

Unlike nodemon it wouldn’t restart. But nodemon also works idk
On Thu, Jul 21, 2022 at 12:31 PM Evo @.***> wrote:

Would it mean a restart? or No restarts?
—
Reply to this email directly, view it on GitHub
https://github.com/sern-handler/cli/issues/62#issuecomment-1191754421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASJS6O6JYUTYPPMC6NS52ULVVGCNHANCNFSM54IIYQPA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I’ve messed around with hmr with vite and honestly it’s one of the most
productive things I’ve used
On Thu, Jul 21, 2022 at 12:32 PM Jacob Nguyen @.***>
wrote:

Unlike nodemon it wouldn’t restart. But nodemon also works idk
On Thu, Jul 21, 2022 at 12:31 PM Evo @.***> wrote:

Would it mean a restart? or No restarts?
—
Reply to this email directly, view it on GitHub
https://github.com/sern-handler/cli/issues/62#issuecomment-1191754421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASJS6O6JYUTYPPMC6NS52ULVVGCNHANCNFSM54IIYQPA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yep I've used hmr as well in a discord bot before, I loved it
However it doesn't work good with TS if we want no restarts since TS compiling to JS is done as a whole project not a single file itself

Yep, true, could tell typescript users to use the tsc watch command however and then hmr on distribution

Also check #63
had in my mind from a long time and finally completed it, if you got more improvements, you can commit there and notify me

If you want you can create a branch and work on it, else I'll work on it by next week
My account will be enabled soon btw, exam's this week

git fetch origin
git checkout feat/hmr

POG, looking forward to return
Hmr experimenting should be good

Ok cool guys

🥸
On Sun, Jul 24, 2022 at 3:55 PM vKxni @.***> wrote:

Ok cool guys
—
Reply to this email directly, view it on GitHub
https://github.com/sern-handler/cli/issues/62#issuecomment-1193392701,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASJS6OYF7DB2DBHDG4OPNZTVVWUU5ANCNFSM54IIYQPA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Will be working on this. Experimental at the moment! A dev i saw ( Chooksie ) has a really good explanation on this, so I will research into it.

Well just discovered hmr and nodemon near the same thing. nodemon is more for server side stuff while hmr is frontend.
https://stackoverflow.com/questions/46086297/nodemon-and-or-hot-reloading-with-a-node-react-web-app. I suppose we can just do some chokidar based system? @leonardobagi recommended this can be done in the framework and not in the cli

I suppose we can just do some chokidar based system? @leonardobagi recommended this can be done in the framework and not in the cli

This feature could either be directly implemented in the Sern.init command via an option, or made via plugin. I do think that making built-in in Sern can be lighter, faster (since there's no need for external packages) and more customizable; it could also be easier to implement, because controlling command files via plugin can generate conflicts with the main code. The only drawback, though, is that we couldn't watch for an X file rather than the entire folder, but that is not such a big deal

A sern watch cli command wouldn't be that good imo, since the init thing of the cli only generates the code

A sern watch cli command wouldn't be that good imo, since the init thing of the cli only generates the code
Understandable.
I was thinking these ways to implement a module watcher

through cli
through plugins
through global plugins ( experimental (and top secret!!!! jk) )
built in

one part of Sern i want to keep is to keep customization and to not add any extra features that users may not want.
So with this reasoning, I would say global plugins or built in is the best option. Like you said here :

I suppose we can just do some chokidar based system? @leonardobagi recommended this can be done in the framework and not in the cli

This feature could either be directly implemented in the Sern.init command via an option, or made via plugin. I do think that making built-in in Sern can be lighter, faster (since there's no need for external packages) and more customizable; it could also be easier to implement, because controlling command files via plugin can generate conflicts with the main code. The only drawback, though, is that we couldn't watch for an X file rather than the entire folder, but that is not such a big deal

Individual command watchers is just inefficient and id rather have a whole directory being watched.
So that brings us down to two options

global plugins
built in
Now the question boils down to is adding an hmr system ( in return adding more to the depedencies list most likely ) built into the framework wise? Or would it best be handled via the user, to opt into it through plugins.

Now that you mentioned global plug-ins thing (which is probably what I wanted to do), it's better to apply that option.
It's very likely some users will prefer nodemon over this watcher, since, sometimes, the user needs to hot reload other files outside the commands directory (a utils folder e.g).
In addition, making it a plugin will reduce unnecessary and unwanted dependencies. (Because chokidar would be required, and some users will just not use the feature, increasing final bundle size)

I also think that promoting plug-ins with that hmr one will make them look for more utilities plug-ins, create their own and contribute to existing ones. It's a nice way to a promote such an unique feature in handlers.

It's very likely some users will prefer nodemon over this watcher, since, sometimes, the user needs to hot reload other files outside the commands directory (a utils folder e.g).

Our main point is to avoid multiple bot relogins and restarts, and only dynamically reload the commands, making everything faster and using less bandwidth. We can even make a dev slash command /reload, if it fits here.

reviving this, I want a convenient way of developing my bot without using ts-node or nodemon!

It seems like the plug-ins API can't get us the commands yet, so we'll have to wait for that to happen

yea some guy at the discord just asked for that

Yea I did

oh wait its you?

oh yeah you are 💀

Lmfao

@leonardobagi  has been working on an experimental FileWatcher that may work

That class starts the whole hmr thing, the only thing remaining is syncing the commands on discord. This could be easily done via (https://github.com/sern-handler/sern-community/pull/30)[a CommandsSyncer] class I made for the sern-community bot.


fix(Containerfile): add netcat for SNO DNS testing and workaround

Description
Adds netcat to test SNO DNS connectivity

:tada: This PR is included in version 1.8.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


uninitialized constant Moped::BSON when using mongoid-observer gem

Due to the current method for checking for Mongoid 3 i.e checking for the Observer constant in Mongoid
using mongoid-observer will break the check because it defines this constant.
Happy to make a PR, there are 2 ways I can think of to fix this:
Check the mongoid version
def self.mongoid3?
  unless defined?(@is_mongoid3)
     # Might need to check this part
     @is_mongoid3 = Gem::Version.new(Mongoid::VERSION)
          .between?(Gem::Version.new(3), Gem::Version.new(4))
  end
  @is_mongoid3
end

Or perhaps check for BSON in Moped
def self.mongoid3?
  ::Moped.const_defined?(:BSON)
end

Which has more to do with the Moped gem than Mongoid. Not sure if mongoid3? is used just to test for Moped::BSON exclusively. Perhaps it would be better to have Mongoid::Slug.mod_bson return either Moped::BSON or BSON and just use that method.

This is sloppy work on my part when implementing mongoid5 compat, I should have replaced all the calls to mongoid3?. Done in https://github.com/digitalplaywright/mongoid-slug/pull/195 with bringing in mongoid-observers and reproducing this error in tests.

I released 5.2.0 with this fix.

Awesome work! thanks! :+1:


Capture exit code of failing lsp server?

Is there a way to hook the LanguageClient to report the exit code for a LSP server?  Neither the initializationFailedHandler nor ErrorHandler options of the LanguageClientOptions seems to work for this.
https://github.com/microsoft/vscode-languageserver-node/tree/master/client

@akaroml thanks.


Dependency conflict

When I run:
cordova build android
I get the following:
What went wrong: A problem occurred configuring root project android. Cannot add task :processDebugGoogleServices' as a task with that name already exists.
I am attempting to use Firebase Analytics (cordova-plugin-firebase-analytics) which requires your plugin, Google Services (cordova-support-google-services).  I am also using Firebase Cloud Messaging (cordova-plugin-fcm). The cordova-plugin-fcm includes Google Services 3.0.0 and the cordova-support-google-services has Google Services at 3.1.0 creating the conflict.
I am new to using Ionic 3/Angular 4.  A fix I had found on a different forum, and implemented, was changing the version in platforms/android/cordova-support-google-services to 3.0.0 from 3.1.0.   This was only a temporary fix, and a Sr. Dev on my team said this was terrible and should never be done.  Of course, I do not want to do something that is a bad practice, however, what this error informed me of is that if I can get the dependencies at the same version, then the conflict resolves and the project builds.
Do you have an earlier plugin that has Google Services at 3.0.0 or is there a way to specify the version of Google Services at the time of installation?  Any guidance you can offer would be extremely helpful.
Thank you!

Look for any "firebase-core:11.0.x" entry in platform/android/project.properties and build.gralde and change it to "firebase-core:11.0.1"

@HeatherWolford I think you'd need to send a PR to the maintainer of cordova-plugin-fcm to use this plugin to run the Google Services gradle task.

@macdonst does it make sense to create a PR to https://github.com/phonegap/phonegap-plugin-push, to use this repo as a dependency? Should solve some conflicts that people might have. Or there are some plans to integrate google services task into cordova-android?

@chemerisuk yeah, I'd be cool with a PR to the push plugin. It should make things more consistent if we only have one plugin adding this step.

I sent a PR to cordova-plugin-fcm but I'm not sure if the plugin is even maintained anymore.

The conflict will be fixed after merging of https://github.com/fechanique/cordova-plugin-fcm/pull/495


[Firefox]: blocked mixed content while requesting get_table_rows

Version of EOSJS
^20.0.0-beta3
Describe the bug
Firefox blocks mixed content while requesting for data using get_table_rows.
Expected behavior
Should not error.
Screenshots

Desktop (please complete the following information):

OS: MacOSX
Browser: Firefox latest version

For security reasons, Firefox doesn't notify JS code of this failure. eosjs can't detect it.

@tbfleming thanks for your comment. So what should I do about this problem? Do you have any workaround?

If you're serving your app using https (highly recommended), then your app should only allow https endpoints.


Update troubleshoot-rdp-general-error.md

Check if RDP is disabled by group polices.
REM Get the group policy if any
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v fDenyTSConnections

If the group policy states that RDP is disabled (1), enable RDP by using the following command:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v fDenyTSConnections /t REG_DWORD /d 0 /f

Note : If the value is 1, RDP is disabled either by local policy or domain policy. Once you are able to RDP, check the resultant set of policy to identify the policy which is disabling RDP. Based on the policy being enforced, update the AD policy from domain controller or local policy of the VM.

Check the current remote connection configuration.
REM Get the local remote connection setting
reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections

If the command returns 1, the VM is not allowing remote connection. Then, allow remote connection using the following command:
     reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f

Reason:
To anyone ready reading the document, gives the following understanding.

We ae going to check if RDP is disabled via policies
Check Local group Policy @ HKLM\CCS\Control\Terminal Server
Check Domain group Policy @ HKLM\Software\Policies\Microsoft\Windows NT…..

Fact :  Both Domain and Local polices go to @ HKLM\Software\Policies\Microsoft\Windows NT\Terminal Server  ONLY.
However the article pointing to check-query HKLM\CCS\Control\Terminal Server under the title “Get the Local Policy” .  Local Group Policy isn’t stored there under the HKLM\CCS\Control\Terminal Server key.

Hi @AharnaMoulick - Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone will review your changes. Thanks!

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

@genlin - Could you review this pull request? Thanks.

@AharnaMoulick  Thanks for the suggestion.
#sign-off

Hi @genlin - Should the PR be closed or merged? Thanks!

#please-close

@AharnaMoulick， I am submitting a PR. so to avoid conflict,  I will consolidate your suggested changes in that PR. Thanks!


[Server] dendrology:parcel is missing

FML says that dendrology:parcel is missing at startup ... every time.
And it asks for /FML confirm

1.10 Unabridged/Abridged discontinued.


change username

- Summary

- Test plan

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

👷 Deploy Preview for warm-travesseiro-9bc536 processing.

Name
Link

🔨 Latest commit
8247435c84e1d926ba071e9027d7c90d14606981

🔍 Latest deploy log
https://app.netlify.com/sites/warm-travesseiro-9bc536/deploys/625bfb3009d31b0008877af1


Docs.MS CI Updates for Azure.MixedReality.RemoteRendering

CI Update for release of Azure.MixedReality.RemoteRendering

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

File
Status
Preview URL
Details

docfx.json
:x:Error

Details

docfx.json

Line 271, Column 24: [Error-file-not-found] Invalid file link: 'missing_apis.yml'.

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

@danieljurek, @scbedd:   Would one of you be so kind as to offer your thoughts on this?

This has to do with the target branch. We have 2 interesting branches to the docs building process in the docs repo:

onboarding (the target branch of this PR) -- This is where we add and configure the list of packages for which to generate documentation.
master -- This is where reference docs are placed when generated from configuration in the onboarding branch.

The bot messaging us here is, in this case, attempting to publish docs from the onboarding branch as if it were the master branch. I've got an issue open to figure out if there's anything we can do here: https://github.com/Azure/azure-sdk-for-net/issues/18704


⚠ ClamAV has degraded performance

In 03c7d56, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 56 ms

Resolved: ClamAV performance has improved in f7f83e0.


Logitech.GHub version 2021.9.7463

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

https://github.com/microsoft/winget-pkgs/issues/9185#issuecomment-805418508


NECO-200: Added margin for expiration time.

Changes

Added margin for expiration time.

Tests

See the ticket.

I reviewed all the changes. Thank you for your coding!
I'm gonna merge this pull request.


Could this extension be made available in the Open VSX Registry?

This would enable users of VSCodium to make use of your extension more easily.

I just publish it in https://open-vsx.org/extension/LuoZhihao/call-graph and also Github Release :)

That's wonderful! Thanks so much!


Fixed error 404

Ticket: #30
Describe The Problem Being Solved:
added a new attribute "next" in server.js
app.use((err, req, res, next)
Checklist For Submitter

[x ] I have documented all new functionality
[ x

] I have screenshotted new UI changes and attached them to this PR

Reminder list For Reviewers

Code formatting/static analysis: is the code formatted properly? Does a linter/other form of static analysis reveal any issues? Does the code have appropriately low cyclomatic complexity?
Code architecture: concerns are separated, code follows single-responsibility principle, code utilizes OOP, DRY code.
Coding best practices: code avoids hard-coded variables, inefficient computations, reinventing the wheel when using frameworks. Code is well-commented and generally readable.
Non-functional requirements: Code has accompanying tests. Programmer can easily explain decisions to reviewers.

No changes needed. Awesome job


[0.13] Test Failure due to void Xbyak::util::Cpu::setCacheHierarchy(): Assertion `smt_width != 0' failed.

http://debomatic-amd64.debian.net/distribution#unstable/mkl-dnn/0.13-1/buildlog
Any idea about this build failure? I cannot reproduce this issue on my 7440HQ cpu. The CPU of that build server is possibly, I guess, xeon 26xx or something alike.

Hi @CDLuminate, thanks for the report. I'll look into this. Is there any way to know which CPU did the build host use? One other thing that caught my eye is that cmake is run with -DCMAKE_BUILD_TYPE=None. I would suggest using -DCMAKE_BUILD_TYPE=Release or (less tested) -DCMAKE_BUILD_TYPE=RelWithDebugInfo if you want to provide a package with the debug information (separately).

lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              8
On-line CPU(s) list: 0-7
Thread(s) per core:  1
Core(s) per socket:  8
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               63
Model name:          Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz
Stepping:            2
CPU MHz:             2600.126
BogoMIPS:            5200.00
Hypervisor vendor:   Xen
Virtualization type: full
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
L3 cache:            35840K
NUMA node0 CPU(s):   0-7
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush acpi mmx fxsr sse sse2 ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl eagerfpu pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single kaiser fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt

It's 2697 v3 @rsdubtso
I just added the lscpu command to the build script. The package was rebuilt and ended up with the same failure.
http://debomatic-amd64.debian.net/distribution#unstable/mkl-dnn/0.13-1/buildlog

I'm having troubles reproducing this... is it possible that the build and tests are run inside a VM/QEMU? I'm really not sure how to debug this further...

@rsdubtso It should be an Xen guest. I'm not aware of whether the CPU behaviour changes when working in Xen. Should I ignore this problem, or contact Xen maintainers?

@CDLuminate Can you please ping the maintainers of the build asking for any CPUID masking settings they use for Xen? I have almost set up a machine I can try this on :)

@rsdubtso Wow, that's awesome. Wait a moment and let me ping him.

@rsdubtso Copied from maintainer's mail:
Sure, hopefully they are the correct ones:

cpuid = [
    "0x00000001:ecx=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "0x00000007,0x00:ebx=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
]

== Detailed mask derivation info ==

EAX1 ECX registers:
11111111111110100011001000000011
11111111111110100011001000000011
11111111111110100011001000000011
================================
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

EAX1 EDX registers:
00010111110010111111101111111111
00010111110010111111101111111111
00010111110010111111101111111111
================================
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

EAX7,0 EBX registers:
00000000000000000010011110101011
00000000000000000010011110101011
00000000000000000010011110101011
================================
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

EAX7,0 ECX registers:
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
================================
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


Common Pointers for all the jobs in the queue.

In the function thpool_add_work of thpool.c the assignmenet of the newJob is as follows:
newJob->arg=arg_p
where arg_p is the argument of the function.
This leads to a situation in which all the jobs in the queue having the same pointer.
This can be mitigated by replacing the lines with:
newJob->arg=(char*)malloc(10000*sizeof(char));
strcpy(newJob->arg,arg_p);
but this way we lose the obscureness of the API.

I mark this as closed. If you have any further inqueries, feel free to reopen!


basic UI for creating workflow

Any reference to basic UI for creating/modifying workflow. It is just for demo purpose.

I'm currently exploring draw.io and doing something similar to the AWS Step Functions plugin:
https://github.com/sakazuki/step-functions-draw.io

Currently, we do not have a UI for creating worflows. It can only be done programmatically and/or using JSON and JSONPath.
Please feel free to submit a PR with an implementation and we would be happy to review and merge the same.

Currently, we do not have a UI for creating worflows. It can only be done programmatically and/or using JSON and JSONPath.
Please feel free to submit a PR with an implementation and we would be happy to review and merge the same.

Hi, passed year after your answer, is there any UI for creating worflows was developed?)

Currently, we do not have a UI for creating worflows. It can only be done programmatically and/or using JSON and JSONPath.
Please feel free to submit a PR with an implementation and we would be happy to review and merge the same.

Hi, passed year after your answer, is there any UI for creating worflows was developed?)

@vbratitsa We're pipelining the release of revamped UI later this year. We don't have concrete timelines yet, we'll update as we know more.

Bump. Any updates on this?

This ability was added to the UI in v3.6.0


Can it accelerate data transfer in both directions?

Can it accelerate data transfer in both directions?

strictly speaking it's forward-error-correction, not acceleration.
Yes, it's indeed working on both directions


Added client support for HTTP&HTTPS proxy requests.

new method: Client<HTTP/HTTPS>::proxy_request(...)

Thank you, but the diff is somewhat strange?

Yes, I noticed it too, while merging the changes. I don't know why, but I guess my editor screwed up the whitespaces or the encoding. I'll try to fix it.

Should be fine now... My editor has set the line endings to Windows-style

I agree that there is too much equal code in the two request method, but I'm thinking that one could set the proxy parameters at the Client-constructor instead. What do you think? Also, if possible, one could use one string to specify host:port like done at the moment when specifying the server to connect to.

I agree. It's more logical to set the proxy details together with the target host in the client's constructor. This means adding an overload to the ClientBase, Client<HTTP> and Client<HTTPS> constructor and remove the proxy_request() method from the client's interface.
The request() would then create a proxy request if a proxy-connection has been passed to the constructor and would fall back to a regular HTTP(S) request if none has been supplied.
I agree that the semantic for setting the proxy information should be the same, which is used to set the target host.
So the additional constructors would look like this:
ClientBase(const std::string& host_port, unsigned short default_port, const std::string& proxy_host_port, unsigned short default_proxy_port);
Client<HTTP>(const std::string& server_port_path, const std::string& proxy_port);
Client<HTTPS>(const std::string& server_port_path, const std::string& proxy_port);

I'll try to change the code accordingly tomorrow.

What do you think of this implementation?

Thank you, looks good, but I'll probably try to make some simplifications during the Weekend when I have time. Might also move the proxy setup to a Config class instead of using the constructors, I know more after I've looked into the changes in detail. Nevertheless, it's a good starting point!

Merged https://github.com/eidheim/Simple-Web-Server/commit/743785b563f2371d9eb6fac971b130872459e777, I'll work on the rest in the Weekend.

Just wanted to say that I've not forgotten this PR, and will have time to work on it in a couple of days.

Proxy support has now been added to Client. Have not tested it though.

Something seems to be missing for HTTPS proxy support.
To establish an HTTPS connection over an proxy, you have to first send an http CONNECT request. The Proxy then establishes a TCP tunnel (if responds with OK) and then you can start your SSL handshake over that TCP tunnel. That way the proxy cannot read your traffic.
As it is implemented right now, you simply start an HTTPS connection with the proxy and then use the regular proxy requests. This makes certificate validation impossible and lets the proxy see all your traffic, which would make https meaningless.

Ok thank you, I'll add this as well Tomorrow morning. I just added a fix btw for the corrected paths when using proxy.

Do you know if there are any default proxy ports for http and https?

I searched a while but coudln't find a decisive answer in any forum.
Most HTTP-Proxies I found in proxy lists were using port 80 or 8080. While HTTPS proxies were mostly using port 8080 or 8088.
It seems as if port 8080 would be the default port for both protocols, which makes somewhat sense, because you need only one port to support proxying HTTP and HTTPS.

Thank you. I added the CONNECT request, hopefully I got it right.

Also fixed the request path when performing HTTPS client requests using a proxy server.

Again, the code is untested, so feel free to let me know if it's working or not (both HTTP and HTTPS proxies).

Ok, I'll run some tests as soon, as I find some time to do so, but the code changes look right and it should work.

Sorry, that it took me so long, but I finally found the time to run your implementation through my proxy tests and the HTTP proxy works fine, but the HTTPS proxy requests are failing with uninitialized socket errors.
The first error occurs in async_write() at line 87 because you are writing the first HTTP CONNECT request to an SSL socket, which hasn't been initialized yet (no handshake). The HTTP request must be written to the TCP socket (one layer below).
This can be easily fixed by changing the line to:
boost::asio::async_write(socket->next_layer(), write_buffer, ...

But then the next uninitialized socket error occurrs when trying to read the response from the SSL socket via request_read() in line 100 which always reads from the top layer of the client's socket.
This is not easily fixed, because request_read() needs to accept the socket to read from as parameter, which would affect:

line 251 in request_read
line 256 in request_read
line 296 in request_read_chunked
line 331 in request_read_chunked

That's why I had to introduce this protected request()-overload in my suggested implementation.

Thank you! The HTTPS proxy issue should hopefully be fixed in https://github.com/eidheim/Simple-Web-Server/commit/4606dbd85557fec53fba1ada50100a374810504c.

Yes, 4606dbd has fixed the problem and my proxy tests are all green. 👍

Great, and thank you again for contributing in implementing this feature!


Updates to contribution and demo site docs

Merged in https://github.com/torchbox/wagtail/commit/479cee9e293ae4fb3b6cbae584a7f526909e3115


Cm 477 get actions test

Initial test added for actions endpoint.

Merging without review since this will not affect production code.


New Metric: Change Request Closure Ratio

Here's the PR for the new Change Request Closure Ratio metric based on this gdoc
See also issue #187

@klumb -- can you help get this pushed to the website?

Thanks @klumb! The link to the issue can stay up for now.


Fix build problem with current 1.0.2 branch

never mind.

no, we'll use this to fix it.

Pushed. Thanks.


chore(#29): Update dependecies

Resolved #29

Also, we should inform to developers which NodeJS version we are using in the project, therefore we should modify this line in the readme file:
https://github.com/josdem/playwright-vetlog/blob/15b2212d3153fe06db8037f27c9023baf3b45201/README.md?plain=1#L9

@all-collaborators please add @ahmedhalac for code

@all-contributors please add @ahmedhalac for code


Update README.md removing broken image with link and making formatting changes

Certainly! It looks like you are addressing a GitHub issue related to updating the README.md file in the covid-19-repo-data repository. The task involves removing a broken image and corresponding link, and making some formatting changes.
Here are the steps you should follow to successfully complete this task:
Step-by-Step Guide
1. Clone the Repository
First, clone the repository to your local machine if you haven’t already:
git clone https://github.com/yourusername/covid-19-repo-data.git
cd covid-19-repo-data

2. Create a New Branch
Create a new branch to make your changes:
git checkout -b update-readme

3. Edit the README.md File
Open the README.md file in your preferred text editor and make the necessary changes. For instance:

Remove the broken image:

Locate the broken image link and delete it.

Update formatting:

Ensure consistency in headers, lists, and other markdown elements.

4.  Push the Changes to GitHub
Push your changes to the newly created branch on GitHub:
git push origin update-readme

6. Create a Pull Request
Go to your repository on GitHub and you should see a prompt to create a pull request for the newly pushed branch. Follow the instructions:

Click on the Compare & pull request button.
Ensure the base branch is master and compare branch is update-readme.
Add a descriptive title and comment for the pull request, e.g., “Update README.md to remove broken image and improve formatting”.
Submit the pull request by clicking on Create pull request.

Pull Request Example
Here's what the pull request might look like:
Title: Update README.md removing broken image with link and making formatting changes
Description:
This pull request addresses issue #67. It removes the broken image link from the README.md file and makes necessary formatting updates for better readability.
Review
Once the pull request is submitted, it will need to be reviewed and approved by collaborators. Make sure to incorporate any feedback if provided.
Merge the Pull Request
After approval, you (or another collaborator with the necessary permissions) can merge the pull request into the master branch.
git checkout master
git pull origin master
git merge update-readme

Alternatively, you can use the GitHub interface to complete the merge and delete the branch:

Click on Merge pull request.
Confirm the merge.
Optionally, delete the branch after the merge.

By following these steps, you will successfully update the README.md file to remove the broken image/link and improve formatting. If any further assistance is needed, feel free to ask!

Ok


Material 2 Components Build Error - sourceMappingURL

I have installed material2 components using package.json file.
Now whenever I try to build using systemjs, I received below errors:
Error: ENOENT: no such file or directory, open<EMAIL_ADDRESS>When I opened the input file.js in node_modules@angular2-material\input I found the below line at the end of the file.
//# sourceMappingURL=/usr/local/google/home/jelbourn/material2/tmp/broccoli_type_script_compiler-input_base_path-IydvmmBU.tmp/0/components/input/input.js.map
it seems that the sourceMappingURL provided in js files of all components is incorrect.
Can anyone please guide?

This is a duplicate of #541

Thank you Paul for the update, I will follow that ticket.

Closing as dupe of #541


Support both class and method level annotations in the same class

Support both class and method level annotations in the same class

Provide a possibility to use both class and method level @LogIt annotation in the same class
Do not log the methods that have class and method annotations twice
Method level annotation has a higher priority

Released and tested 1.1.3


Cookies not set in iOS Simulator

Device information:

Hardware: iOS Simulator
Operating System and Version: iPhone 11 Pro Max 13.3
Forge Platform version: v2.8.4

App information:
 "modules": {
    "contact": {
      "version": "2.13",
      "config": {
        "usage_description": "Allow access to your contacts in order to recommend the app."
      },
      "disabled": %disable_recommend_module%
    },
    "icons": {
      "version": "2.9",
      "config": {
        "android": {
          ...
          }
        },
        "ios": {
          ...
        }
      }
    },
    "launchimage": {
      "version": "2.13",
      "config": {
        "android": {
          ...
        },
        "ios": {
         ...
        },
        "hide-manually": true
      }
    },
    "display": {
      "version": "2.11",
      "config": {
        "statusbar": {
          "android": {
            "transparent": true
          },
          "ios": {}
        },
        "orientations": {
          "ipad": "any",
          "android": "any",
          "iphone": "portrait"
        }
      }
    },
    "file": {
      "version": "2.24",
      "config": {
        "usage_description": "Allow to upload images or videos stored on your device, e.g. for in app posts, comments or chat messages."
      },
      "disabled": false
    },
    "capture": {
      "version": "2.25",
      "config": {
        "usage_description": "Allow to upload images or videos stored on your device, e.g. for in app posts, comments or chat messages."
      }
    },
    "notification": {
      "version": "2.8",
      "config": {}
    },
    "bolts": {
      "version": "1.9.0",
      "config": {}
    },
    "sb_parse": {
      "version": "3.3.14",
      "config": {
        ...
        }
      }
    },
    "tabs": {
      "version": "3.3",
      "config": {}
    },
    "urlhandler": {
      "version": "2.2",
      "config": {
       ...
      }
    },
    "request": {
      "version": "2.11",
      "config": {}
    },
    "share": {
      "version": "1.3",
      "config": {}
    },
    "prefs": {
      "version": "2.2",
      "config": {}
    },
    "browsersettings": {
      "version": "1.6",
      "config": {
        "accept_cookies": true,
        "media_playback": {
          "inline_video": false,
          "autoplay_video": true,
          "enable_html5_audio": true,
          "enable_background_audio": false,
          "respect_playing_audio": true
        }
      }
    },
    "utils": {
      "version": "0.67",
      "config": {
        ...
      }
    },
    "platform": {
      "version": "2.3",
      "config": {}
    },
 }

To Reproduce

XHR-call which sets cookie in response

Expected behaviour
Cookies are set.
Actual behaviour
Cookies are not set.
TypeError: undefined is not an object (evaluating 'window.forge._receive')

Confirmed as a long-standing Apple bug that has been present in WKWebView since at least iOS 10.
Existing workarounds did not work for JSONP calls.
Existing workarounds for other calls were rendered ineffective after Apple stopped including cookies in response headers.
There's a workaround.

1. Update platform to v2.8.6
"platform_version": "v2.8.6"

2. Prime cookie store
When your app first starts up, use the new forge.tools.setCookie() API to set a dummy cookie for the domain(s) you are going to be making calls to.
For example:
    forge.tools.setCookie("trigger.io", "/api/v1/auth/hello", "foo", "bar", function () {
        // cookie has been set and cookie store has been synchronized
        // continue with normal startup, make JSONP calls etc.
    });

This seems to "prime" the cookie store which then responds to the cookies sent by the server.
Only the first parameter, the domain, matters. You can set any value for the other parameters unless you wanted to provide a specific cookie.
It's essential that subsequent app startup happens in the completion callback as setting cookies and flushing the cookie storage is an asynchronous operation.
Only works on hardware, not on the iOS simulator.


Intersection observer can display FOUC

In examples/list.html, you can see when scrolling an element into view, it 'pops' into place. This could be solved with a smaller threshold for the IntersectionObserver, or possibly pre-render just the background color at least (but not actually WebGL render, which would trigger the GL setup, which might be ok, but least desirable solution, IMO)

I think this was fixed.


swagger spec in api-docs.json contains bogus fields

My Environment

ArangoDB Version:        3.4.5

Component, Query & Data
Affected feature:
api-docs.json swagger spec
Steps to reproduce

Download from https://raw.githubusercontent.com/arangodb/arangodb/devel/js/apps/system/_admin/aardvark/APP/api-docs.json

Problem:
The swagger spec contains multiple bogus entries.

In /_api/wal/tail in parameter "global" the type is "bool" instead of "boolean"
Several occurrences where the format is empty (... "format": ""...)
Several occurrences where the format is either boolen, integer or object. boolean, integer and object are types. Most of the occurrences double the type in the format which shouldn't be

Expected result:
There should be only standard types and formats or arango specific ones. All the format occurrences can be deleted. That is how I correct my spec:
... | sed -e 's/"bool"/"boolean"/g' | sed -E 's/"format": "(boolean|integer|object)?",//g'

Boolean fix: https://github.com/arangodb/arangodb/pull/9045

bool has been changed to boolean. Number types have been specified better for numbers. There are still empty formats and for type boolean a format boolean. There is also a format uint64 which is not part of Swagger/OpenAPI. Formats can be custom but sometimes this is not intended. For parameters there is often a "format=string" and no type field. I think these should be called type=string. Shall I make individual tickets for different types of problems?

@noha Looks like you approved https://github.com/arangodb/arangodb/pull/9045 shortly after your comment, does that mean all of the problems are solved or is there still something to fix? Can you suggest required code changes?

Actually I approved before my comment. It was accudental but I did not see how to remove that approval again. So I added a comment. I need to look into the last changed. Last time I looked there were still problems

This was worked on and resolved last year, closing as outdated.
Please note that ArangoDB 3.7 is available.


sanity_check issue with geodesic loss

In order to avoid loss is Nan
In compute_geodesic_distance_from_two_matrices(m1, m2)
I changed
cos = torch.min(cos, torch.autograd.Variable(torch.ones(batch).cuda()) )
cos = torch.max(cos, torch.autograd.Variable(torch.ones(batch).cuda())*-1 )
to
cos = torch.min(cos, torch.autograd.Variable(torch.ones(batch).cuda()) * 0.9999)
cos = torch.max(cos, torch.autograd.Variable(torch.ones(batch).cuda()) * -0.9999 )
then training ran but after few iterations I got a constant error and the same for all models
Then I realized their is a problem as teta value can be negative and in model definition we have
def compute_geodesic_loss(self, gt_r_matrix, out_r_matrix):
theta = tools.compute_geodesic_distance_from_two_matrices(gt_r_matrix, out_r_matrix)
error = theta.mean()
return error
so if I am not wrong error can be negative
I tried
In compute_geodesic_distance_from_two_matrices(m1, m2)
at the end : return torch.abs( teta)
I now have a steady decrease of geodesic loss for all the models :)
after 100000 iterations
ortho6d 0.018
ortho5d 0.021
quaternion 0.162
euler 0.198
rodriguez 0.104
euler_sin_cos 0.066
Quaternion_half 0.041

You could have a check here: https://pytorch3d.readthedocs.io/en/latest/modules/transforms.html#pytorch3d.transforms.so3_relative_angle


Ruling with low income (like it was in previous version)

I see that the field for master's and under 30 is no longer in this new version, how do you adjust the lower income requirement for the 30% for this now?

With the new version of the website, its not possible to specify what kind of 30% ruling someone is entitled to
https://user-images.githubusercontent.com/60266962/214048711-6c124e6d-ad1c-4b7e-948d-0757ed208317.png
Since the 30% ruling is only valid if the annual taxable salary is higher than ~41k , a person with master degree that has a lower salary, doesn't have the correct net value calculation because the annual taxable salary only needs to be higher than ~31k

@stockiller I've added the options that were in the old version, please check

It works, thanks!


[stable/kubernetes-dashboard] Create Role and RoleBinding in "kube-system" namespace

Fixes https://github.com/helm/charts/issues/3104
Kubernetes dashboard has kube-system namespace hardcoded in several places. So it doesn't respect the namespace where the pod is actually deployed and still tries to create & access kubernetes-dashboard-key-holder secret and kubernetes-dashboard-settings configmap in the kube-system namespace.
The issue on kubernetes/dashboard side: https://github.com/kubernetes/dashboard/issues/2655
The fix is still in the WIP state: https://github.com/kubernetes/dashboard/pull/3197

Can we have an update on the status of this workaround? Thanks!

@legal90 With the fix pending merge - Should we wait to merge this here as well, and update the chart deployment to add the flag arg?

@FrenchBen Yeah, sure. I'm OK with that. Looking forward https://github.com/kubernetes/dashboard/pull/3197 to be merged. Then I will redo this PR with using the flag instead.

/cc @carrodher @AdamDang can someone look at this and provide feedback?

Changes here LGTM, but AFAIK we're waiting for https://github.com/kubernetes/dashboard/pull/3197 to be merged before merge this one, right?

/assign @desaintmartin
Since it takes quite long time, maybe we should merge this fix to get the issue solved right now? And then revert/redo this as soon as kubernetes/dashboard#3197 is merged and released?


Console color not showing correctly

Describe the bug
Console color not showing correctly. This is caused by some patches, not the plugins.
To Reproduce
We take CMI as an example. Or other plugins, all fine. When CMI starts, it will log the information using blue color. But in Dionysus it turns to be totally white, so does the other plugins.
Plugins
All plugins using the logger
Version
Newest version of Dionysus, this problems seems to occur since very old versions
Misc
Maybe caused by some patches which breaks the color in console.

it is a bug but it isn't really that much of a deal


Parse segment binary with version 1 prototype by default.

Coverage increased (+0.0005%) to 12.034% when pulling b7e5ec1fc3e7b2d276eb030d14287d34c72d1986 on peng-yongsheng:fixed/segment_version into 5577f67de7c9c6fd4896e1ac435cf5cff30ccad4 on apache:master.


Updating the package.json to use new ldap-filter module

I have run the tests locally with this applied using Node 6 and Node 8. All tests are passing so I'm going to merge it into the next branch.

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


TYPO -> VSCode Intellisense -> cloneWithRows() pop-up

VSCode Version: Version 1.19.3 (1.19.3)
OS Version: macOS High Sierra 10.13.3 (17D47)

Steps to Reproduce:

The Intellisense pop-up for cloneWithRows() has a typo in the first paragraph on the word information. Currently it is: Clones this ListViewDataSource with the specified dataBlob and rowIdentities. The dataBlob is just an aribitrary blob of data. At construction an extractor to get the interesting **informatoin** was defined (or the default was used).

Does this issue occur when all extensions are disabled?: Yes

Please open this issue against whichever library you are using.


Land Library admin view

Hi,
One quick question - is it possible to include in the LL admin view, the location country of the publisher? Perhaps also the organization type? So that is an entry field in the organization CT - which is really useful to know the # of local sources in the LL.
I counted this manually for the Library presentation at the annual meeting last year - but as we're exceeding 500 publishers soon, I don't think I will be able to do it.
I'm not sure if the LL admin view is the best place to do this..... any suggestions as to how best get these results would be really appreciated :)

solved using SPARQL :)
https://github.com/landportal/data/blob/master/landlibrary/stats/Land Library Stats.sparql


Fix publication issues of Wasmtime 23.0.0

Remove the readme directive of the cranelift-bitset crate as the file doesn't exist.

Remove invalid categories of the wasmtime-wasi-threads crate that aren't present on crates.io.

Current plan is to backport this to 23.0.0 and make a patch release of 23.0.1 with new artifacts.


add register_device to register a single ios device more easily

Thanks for contributing to fastlane! Before you submit your pull request, please make sure to check the following boxes:

[X] Run bundle exec rspec from the root directory.
[X] Run bundle exec rubocop -a to ensure the code style is valid
[X] Read the Contribution Guidelines
[X] We currently don't accept new actions, please publish a plugin instead, more information in Plugins.md

Before submitting a pull request, we appreciate if you create an issue first to discuss the change :+1:
Issue: #7797

Could you also make the register_devices action use the register_device action? This way we have far less duplicate code. Also make sure to add the new action to unused_options_spec to make the tests pass 👍

Ah, just read your comment on https://github.com/fastlane/fastlane/issues/7797#issuecomment-271558296.

i made a pr but i didnt make register_devices call register_device, fistly because i dont know, and secondly because then it has to check all the time for credentials, and i dont know if that will be too slow.. what do you think?

Yeah, great point, it would login for every device, which is not something we want to do. Let's keep it like this for now then 👍

I can't believe yet another fastlane contributor is from Vienna. You should come to this Thursday's CocoaHeads meeting in Vienna: https://www.facebook.com/events/698465373653477/

I will fix those in a few minutes. hehe I was living in Vienna. I moved to Amsterdam in November.

Looks good to me, thanks for your contribution. This will be in the next release 🚀


switching from beta to stable breaks iOS build, magic line fixes for release only

I recently switched from using beta on local machine building android to stable, the local mac I was using for iOS builds was always on stable.
This seemed to break the iOS build.
Following the suggestion from this comment fixed the error:
error: 'Flutter/Flutter.h' file not found

for release builds using flutter build ipa but did not fix the error for flutter run.
I have no idea why this magic line was missing  from my podfile, I have no idea why adding it in fixes the release build but not the debug builds.
Any explanation or further information on the above error or any of the above unanswered questions would be most appreciated.

Hi @maks
I see there's an open issue addressing the case you described.
Please follow up on that issue, Closing as duplicate of https://github.com/flutter/flutter/issues/79920
If you disagree, please write in the comments and I will reopen it.
Thank you


⚠ preview - Auth API has degraded performance

In fc171c1, preview - Auth API (https://auth-api.pro.cf-explorer-preview.eu-west-1.beta.explorer.cardano.org/api/v1/user/info) experienced degraded performance:

HTTP code: 504
Response time: 10379 ms

Resolved: preview - Auth API performance has improved in fbd3bcd after 13 minutes.


Hooks

New functionality
Introduced a before and after hooks.
Usage
"rnpm": {
  "hooks": {
    "before": "./bin/run-something",
    "after": "./bin/run-something-else"
  }
}

Ready to be reviewed! I'll compose a separated PR in rnpm repo itself to make a README patch

Quick question - do we really have to introduce async here at all? It does not matter since it's CLI, I think it would've been easier to just use https://github.com/shelljs/shelljs#execcommand--options--callback ?

Well, for me both of these variants are equivalent. I'm fine with promises also, but it's already written using async and callbacks. Do you think we need to rewrite it?

Where else we can use these hooks? Can you provide any examples? Imo link is the only place where we iterate dependencies.

I am afraid that plugin author has to write some code snippets in order to support that feature (they can forget about it etc.

Not sure I can follow this. We're not pushing library authors to support this feature, it's up to them if it's needed.

Where else we can use these hooks? Can you provide any examples? Imo link is the only place where we iterate dependencies.

Well, you have answered yourself in 3 point :D If we are aiming for the hooks to also work in other plugins and actions, I would aim for something less generic.

Do you think we need to rewrite it?

Well, it's not a deal breaking feature which means we have some time to work on it ;) I am fine with async, but I can see a bit more pros of going all the way down with Promises.

Shouldn't we add return callback() here as well? https://github.com/rnpm/rnpm-plugin-link/blob/126f7768ef13a073e93297a2260cc6d94744bf23/src/link.js#L55

@Kureev generally happy, you can merge it straight away - just check my inline comment


An admin should be able to administrate convos users from the web

An admin should be able to list and edit users. Suggested actions:

List emails, registration date and roles.
Give/take admin rights.
Generate recover links.
Delete users

This is implemented in #505, so closing this issue now.


{Freeway-Bug}[Adaptive Cards - ActivityUpdate]: Keyboard focus order of Date Picker in 'Set Due Date' under 'ActivityUpdate' is not logical using Arrow key.

Target Platforms
Android
SDK Version
2<IP_ADDRESS>
Application Name
Adaptive Card
Problem Description
Test Environment
Device: S21+ 5G
Screen Reader: Talkback
AdaptiveCard Android App version: 2<IP_ADDRESS>
Tools: Logitech Bluetooth Keyboard
Repro Steps:

Launch the Adaptive cards app on Android.
Navigate to 'Import' control and select it.
Navigate to 'Sample cards' and select it.
Navigate to available dropdown under 'Sample cards' and select it.
Navigate all the controls under dropdown and select 'ActivityUpdate'.
Navigate to 'Visual' tab control and select it.
Navigate to 'Set Due Date' and activate it.
A Date Picker dialog will open.
Try navigating in the dates using arrow keys.
Observe the issue.

Actual Result:
Keyboard focus order of Date Picker in 'Set Due Date' under 'ActivityUpdate' is not logical.
On pressing of the left/right arrow keys focus directly Moves to the next month date in that row.
Expected Result:
Keyboard focus order of Date Picker in 'Set Due Date' under 'ActivityUpdate' should be logical. On pressing of the left/right arrow keys focus should move to the next date in that same month.
For example if focus is on 18 September on pressing of the right arrow key focus should move to 19 September and not to the next month.
User Experience:
Keyboard users would be confused if focus order of Date Picker in 'Set Due Date' under 'ActivityUpdate' is not logical.
WCAG Reference:
[Focus Order - Liquid (microsoft.com)](https://www.w3.org/WAI/WCAG21/Understanding/focus-order)
"Have feedback to share on Bugs ? Please help fill Trusted Tester Bug Feedback (office.com) “
Screenshots
https://user-images.githubusercontent.com/89897257/232708073-d02735ba-ec5a-4ccc-9b9a-dc8162ccd7fb.mp4
Card JSON
NA

Sample Code Language
No response
Sample Code
No response

it's also Android date picker issue, there is nothing we can do about it.


Plugin not working in React Fiddle

Describe the bug
Plugin does not seem to work with React.js. Even in the demo fiddle, the points are not draggable.
To Reproduce
https://jsfiddle.net/3v9kexbh/
(copied link directly from "Line - React Fiddle")
Expected behavior
Points should be draggable on line graph

Hey @bhu413!
Sorry for the inconvenience, the Fiddle was pointing to the "latest" version of the plugin (which is incompatible with Chart.js v2), but is still using Chart.js v2.
Here's the "corrected" and working link to a Fiddle using Chart.js v 2.x and version 1.x of this plugin:
https://jsfiddle.net/16kvxd4u/3/
I'll update the readme accordingly!
Other than this, there is no apparent reason why the plugin shouldn't work with React, Chart.js v3, and the latest version of this plugin as well.
I'll close this for now, let me know if you run into issues and I will re-open.


Decimal: FormulaTypeJsonConverter

Fix issue: https://github.com/microsoft/Power-Fx/issues/1316

✅ No public API change.

✅ No public API change.

https://github.com/microsoft/Power-Fx/issues/1316 is fixed so closed this PR


Cannot read properties of undefined (reading 'match')

TypeError: Cannot read properties of undefined (reading 'match')
    at https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:161:11733
    at Object.useMemo (https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:58:59152)
    at Jt.useMemo (https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:40:5905)
    at Wx (https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:161:11719)
    at ax (https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:58:53207)
    at ZS (https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:62:8852)
    at US (https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:62:959)
    at f$ (https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:62:887)
    at U1 (https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:62:740)
    at n7 (https://hanmus-mapfun.tlon.network/apps/grid/assets/index.2d5b6b39.js:60:10912)

What were you doing at the time this occured? Which browser are you using?


Ignored attempt to cancel a touchmove event with cancelable=false, for example because scrolling is in progress and cannot be interrupted.

Ignored attempt to cancel a touchmove event with cancelable=false, for example because scrolling is in progress and cannot be interrupted.
188 event.preventDefault();

Ignored attempt to cancel a touchmove event with cancelable=false, for example because scrolling is in progress and cannot be interrupted. 188 event.preventDefault();

set(event) {
        if (!RangeTouch.enabled || !is.event(event) || event.target.disabled) {
            return;
        }

        // Prevent text highlight on iOS
        event.preventDefault();

        // Set value
        // eslint-disable-next-line no-param-reassign
        event.target.value = this.get(event);

        // Trigger event
        trigger(event.target, event.type === 'touchend' ? 'change' : 'input');
    }

Device: Android and Linux chrome


Simplify BufferedSeriesIterator usage

Allow for BufferedSeriesIterator instances to be created without an underlying iterator, to simplify their usage.
Signed-off-by: Alin Sinpalean<EMAIL_ADDRESS>

That looks cleaner (and will save a bit of memory for federation). We can merge this after the bugfix moratorium, and you've fixed the failing tests.

Sorry for the tests, I had copied a test file into the root dir and was getting a confusing build failure for it (which I've now figured out) and had ascribed the real test failures to the same mystery cause. Fixed now.

Don't worry about it, it happens to us all.

Thanks!


Teh/colors

This may be the cause of https://github.com/JuliaGraphics/ColorTypes.jl/pull/143#issuecomment-567136645. If this looks OK, can this be merged quickly?

Thanks!


Add Cargo.lock

Could you please add a Cargo.lock to this project? This would help packaging your project for NixOS.

Hi @michaeladler. I'm glad there is enough interest for a package for NixOS. I'll gladly add the lock-file, sorry that it is missing in the first place!
I expect to add it within the next 1-2 days, and I'll update this issue once added.

@michaeladler I have pushed the missing Cargo.lock file. Please feel free to reopen or reach out in another issue should there be anything else required! 👍


Proposed Abstract classes and methods

Proposed : abstract classes and methods

Has this been discussed on the swift-evolution mailing list yet?

Has this been submitted to the swift-evolution mailing list? I don't recall seeing this

I just checked, and it has not (at least not under an easily-findable subject). Closing the PR; please open up a discussion on swift-evolution

Yes, we did and someone suggested to use protocol extensions.
David Scrève

Le 7 janv. 2016 à 18:25, Doug Gregor<EMAIL_ADDRESS>a écrit :
Has this been discussed on the swift-evolution mailing list yet?
—
Reply to this email directly or view it on GitHub.

Please send this as a [Proposal draft] to swift-evolution, since several of us didn't see and could not find the discussion you're talking about. It appears too early to schedule a public review.

Here it is : https://lists.swift.org/pipermail/swift-evolution/2015-December/000123.html

But I think it was lost in the massive flow of early days.
I'll post a new proposal as you suggested.


PR-template added

I have created a professional GitHub PR template that includes all the information and guidelines you provided

This is great! Very helpful. Thanks @Muhindo-Galien


Cannot read properties of null (reading 'useContext')

Issue summary
After installation, when i run yarn dev, I got this error:

@shopify/shopify-app-express version:^2.1.3
Node version:18
Operating system:MacOs

Hi @Natanael-Exe, this seems to be an issue with the CLI. I'll transfer it to the appropriate repository.


Right click selection of  row in storage table is not working

OS - Windows
Plugin Version - 0.1.205
IDE - Intellij Idea Ultimate 14.1.3 , JRE 1.8
Authentication - Publish Settings file
Steps:
Click Azure.
Click storage.
Expand a Storage Account.
Expand a particular Storage.
Expand tables.
Expand a particular table.
Add few entities to the table.
Bring the cursor to any row and right click the mouse button.
It will have edit and delete option for the row , which are not responding .
These option are responding when row selection is done through left click of the mouse ,whereas ,  In VS both right and left click are able to select the row .

This may be fixed after the empty rows was fixed and the row is selected. Please regress

Hi @BeatriceOltean , the empty row problem has been fixed , but this problem still exists .
Row selection is still not happening through right click in storage table .

Right Click selection is now working fine ..


Adding Sushi WMATIC-GHST vault

vault and strategy for wmatic-ghst on sushi
Aavegotchi GHST token image added. Not sure if this is the correct one.
Strat: 0x936d1f2ecf2c911efba16bcbb9f205184d827986
BeefyV6Vault: 0xce069a70925409db10f5df617d947b6b4a4a4202

owner not yet changed to multisig, need verification on the correctness of the contract first. Did full testing of the vault/strat however.

new contracts deployed
ownership of vault changed
ownership of strat changed

Vault: 0x756866Bd84A2441664e80367977357b1F9b5F3D3
Strategy: 0x42844d785816e53adfFBdFc66d6BFC2E3E83d8FD
Want: 0xf69e93771F11AECd8E554aA165C3Fe7fd811530c
PoolId: 39