Full page width

Hello,
How can I make each slide be full width?
These are my settings:
$('.slider').slick({
        autoplay: true,
        slidesToShow: 1,
        autoplaySpeed: 2000,
        arrows: false,
        variableWidth: true,
        variableHeight: true
    });

never mind seems it was an error on my part


cvuqdisk doesn't install on FIPS-enabled system

cvuqdisk.rpm is missing a few digests and thus doesn't install on FIPS-enabled systems. Use rpm as a workaround.
# rpm --checksig --verbose /u01/app/19.0.0/grid_1/cv/rpm/cvuqdisk-1.0.10-1.rpm
/u01/app/19.0.0/grid_1/cv/rpm/cvuqdisk-1.0.10-1.rpm:
    Header SHA1 digest: OK
    Payload SHA256 digest: NOTFOUND
    MD5 digest: NOTFOUND

# fips-mode-setup --check
FIPS mode is enabled.
# yum -y install /u01/app/19.0.0/grid_1/cv/rpm/cvuqdisk-1.0.10-1.rpm
Last metadata expiration check: 0:36:11 ago on Tue 16 Apr 2024 07:17:46 PM CEST.
Dependencies resolved.
=============================================================================================================================================================
 Package                              Architecture                       Version                              Repository                                Size
=============================================================================================================================================================
Installing:
 cvuqdisk                             x86_64                             1.0.10-1                             @commandline                              11 k

Transaction Summary
=============================================================================================================================================================
Install  1 Package

Total size: 11 k
Installed size: 22 k
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction test error:
  package cvuqdisk-1.0.10-1.x86_64 does not verify: no digest

Going to provide a fix shortly.

Hi Thilo,
I tried to reproduce the issue but can't find the correct FIPS setup.
yum-config-manager --enable ol7_security_validation
yum install -y dracut-fips dracut-fips-aesni

dracut -f

Add fips=1 to grub /etc/default/grub
grub2-mkconfig -o /boot/grub2/grub.cfg
Reboot system.
cat /proc/sys/crypto/fips_enabled
1

ansible all -m setup  | grep ansible_fips
        "ansible_fips": true,

I can install thr RPM with yum without any problem.
Do you know what I skipped in my test setup?

Hi Thorsten,
what does fips-mode-setup --check return for your test setup? If it's not FIPS mode is enabled. there likely isn't a fully FIPS enabled system. In my opinion, FIPS mode should better be enabled by fips-mode-setup --enable. Also I'm not sure if the rpm fails on OEL7, too. I had this issue with OEL8 and OEL9.


Support jest.testEnvironment in package.json

Hey guys,
use case: The user accesses my site with a query param in the URL for filling a questionnaire.  I have a class in my project which is for the backend communication. This class fetches the correct param from window.location.search and adds it to the request.
I now want to test this class and method, but manipulation of window.location is not so easy with current jsdom versions. According to this issue and comment in jest-repo https://github.com/facebook/jest/issues/5124#issuecomment-352778013 there is a npm package which does the magic with jsdom.reconfigure.
I tried this so setup in my project, but got the error message from CRA the "testEnvironment" is not yet supported. I can either npm run eject or open an issue, to might support this jest config option.
Is there a reason, why not supporting all jest config options or a way, which I can use the given config? Thanks for your help.

Hey guys, are here any updates?


Improve error message for "Unable to locate pem file"

Summary
After splitting config with single pem into separate key/dhparam/certificate files (or rather, leaving them as is provided by letsencrypt/certbot), mounting them on a docker volume (local bind to /etc/letsencrypt), and upgrading to 1.8.2 (presumably from 1.7.x — something tagged latest` from 2 years earlier)... official Docker image of znc failed to start.
version: '3.7'
volumes:
  znc:
    external: true
services:
  znc:
    image: znc:1.8
    volumes:
      - znc:/znc-data
      - "/etc/letsencrypt:/etc/letsencrypt:ro"
    ports:
      - '6697:6697'
    restart: always

$ docker-compose up
Creating network "znc_default" with the default driver
Creating znc_znc_1 ... done
Attaching to znc_znc_1
znc_1  | Building modules ./push.cpp...
...
... # building modules
...
znc_1  | Checking for list of available modules...
znc_1  | Opening config [/znc-data/configs/znc.conf]...
znc_1  | Found old config from ZNC 1.7.2. Saving a backup of it.
znc_1  | Creating a config backup... [ File exists ]
znc_1  | Loading global module [webadmin]...
znc_1  | Loading global module [lastseen]...
znc_1  | Binding to port [+6697]... [ Unable to locate pem file: /etc/letsencrypt/live/ratijas.tk/fullchain.pem ]
znc_1  | Unrecoverable config error.

And when running manually with equivalent set of options, znc presents interactive dialog:
$ docker run --rm -it -p 6697:6697 -v znc:/znc-data -v /etc/letsencrypt:/etc/letsencrypt:ro znc:1.8.2
Building modules ./push.cpp...
...
... # building modules
...
[ .. ] Checking for list of available modules...
[ .. ] Opening config [/znc-data/configs/znc.conf]...
[ ** ] Found old config from ZNC 1.7.2. Saving a backup of it.
[ .. ] Creating a config backup...
[ !! ] File exists
[ .. ] Loading global module [webadmin]...
[ .. ] Loading global module [lastseen]...
[ .. ] Binding to port [+6697]...
[ !! ] Unable to locate pem file: /etc/letsencrypt/live/ratijas.tk/fullchain.pem
[ ?? ] Would you like to create a new pem file? (yes/no) [yes]: no
[ ** ] Unrecoverable config error.

However, the pem file sure exists. It can be opened and read, as demonstrated below.
$ docker run -p 6697:6697 -v znc:/znc-data -v /etc/letsencrypt:/etc/letsencrypt:ro --rm -it --entrypoint=/bin/sh znc:1.8.2
/ # ls -lF /etc/letsencrypt/live/ratijas.tk/fullchain.pem
lrwxrwxrwx    1 root     root            40 Nov 29 07:12 /etc/letsencrypt/live/ratijas.tk/fullchain.pem -> ../../archive/ratijas.tk/fullchain11.pem
/ # head -n1 /etc/letsencrypt/live/ratijas.tk/fullchain.pem
-----BEGIN CERTIFICATE-----
/ #

Version
Docker:
docker version
Client:
 Version:           18.09.3
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        774a1f4
 Built:             Thu Feb 28 06:40:58 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.3
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       774a1f4
  Built:            Thu Feb 28 05:59:55 2019
  OS/Arch:          linux/amd64
  Experimental:     false

ZNC: znc:1.8.2
Related
Issue #1267 looks exactly like mine, but it was closed for reasons either not explained, or the ones I gon't understand.

Because head works for you (thanks for that test), this is different from #1267.
By providing --entrypoint, you're skipping the step of changing user from root to znc. Perhaps znc user doesn't have enough permissions to read one of directories in path to /etc/letsencrypt/live/ratijas.tk/fullchain.pem?

  (And I should have had some sleep before posting issues)
From now on, this issue will be split in two.

[PART 1]
The first thing is, there are different permissions for different types of files under /etc/letsencrypt/archive/domain/. The private key is the only one with most restrictive mode ower: rw, others: nothing.
$ # Inside znc:1.8.2 docker container
$ cd /etc/letsencrypt/archive/ratijas.tk
$ ls -lh *11*
-rw-r--r-- 1 root root 1.9K Nov 29 07:12 cert11.pem
-rw-r--r-- 1 root root 1.7K Nov 29 07:12 chain11.pem
-rw-r--r-- 1 root root 3.5K Nov 29 07:12 fullchain11.pem
-rw------- 1 root root 1.7K Nov 29 07:12 privkey11.pem
$ su-exec znc:znc head -n1 cert11.pem
-----BEGIN CERTIFICATE-----
$ su-exec znc:znc head -n1 privkey11.pem
head: privkey11.pem: Permission denied

Now, I wonder about two things:

How nginx works?

They have quite similar-looking RUN script in Dockerfile, which also adds non-root user & group, namely nginx:nginx. But it's an option, meaning it's there for our convenience, but not enabled by default.
Nginx container also fails, when switched to nginx:nginx user.me@server$ docker run --rm -it \
  -v /etc/letsencrypt:/etc/letsencrypt:ro \
  --workdir /etc/letsencrypt/archive/ratijas.tk \
  --entrypoint=/bin/bash nginx:latest
root@docker$ head -n1 privkey11.pem
-----BEGIN PRIVATE KEY-----
root@docker$ su -s /bin/bash -g nginx nginx
nginx@docker$ id
uid=101(nginx) gid=101(nginx) groups=101(nginx)
nginx@docker$ head -n1 privkey11.pem
head: cannot open 'privkey11.pem' for reading: Permission denied

What would be the downsides of running ZNC as root in docker?

Certificates can be mounted read-only anyway, so that's probably not a concern.
Current strict default configuration basically renders ZNC incompatible with arguably most popular certificate authority out of the box.

[PART 2]
Here lies a problem. The code is so busy checking for file's mere "existence" that it forgot what it was supposed do.
Checking for file status before making an attempt to open it leads to inherent race conditions and poor control flow with redundant error checking. There are plenty of articles on this topic (just google for TOCTOU), I don't have to repeat myself, but the short of it is this:

DO NOT check for file's existence, attributes etc.
Just open it, for whatever mode intended.
Check for any error from the previous step (which you MUST do anyway).
Handle those errors.

Checking for file status before making an attempt to open it leads to inherent race conditions and poor control flow with redundant error checking.

Well, we can just drop the check for that file's existence. This replaces the error from "ZNC refuses to start since it cannot access the SSL certificate" with "ZNC closes all incoming SSL connections without answering the handshake and no clear error message anywhere". The socket library that ZNC uses loads the certificate for each incoming connection.
(Well, if you run ZNC in --debug mode, one of these messages become visible: https://github.com/jimloco/Csocket/blob/e8d9e0bb248c521c2c7fa01e1c6a116d929c41b4/Csocket.cc#L1858-L1884)
(Oh and while we are talking about "do not use access": Feel free to open an issue on Csocket: https://github.com/jimloco/Csocket/blob/e8d9e0bb248c521c2c7fa01e1c6a116d929c41b4/Csocket.cc#L1842-L1854)
Also, this is not a security check. We are not checking the file's owner or doing magic. This is just a convenience feature / quality of life thing. If you read the wikipedia article for TOCTOU, it all sounds quite security-centric.

This replaces the error from "ZNC refuses to start since it cannot access the SSL certificate" with "ZNC closes all incoming SSL connections without answering the handshake and no clear error message anywhere".

What are you talking about? In this case instead of reporting the real underlying problem of opening a file, it prints custom misleading error message about file purportedly being not found.
This check does nothing right. If the point is to verify that https/SSL is set up correctly — how about doing self-test GET request? It would prove much more than simply file being found or not. After all,

If you read the wikipedia article for TOCTOU, it all sounds quite security-centric.

"Sounds"? I am not officially qualified to make comments on security either. Are you 100% sure it can not be misused (apart from already masking real errors, that is)?
Let's see. When the code takes on "Unable to locate pem file" branch, it then may attempt to prompt user with message "Would you like to create a new pem file?". If the answer is "yes", program would attempt to write to that same pem file as returned by the same CZNC::GetPemLocation() function. Let's say, what would happen if at that exact moment certbot on the host triggered by a periodic systemd timer updates certificates and re-creates links? I don't know how certbot works — it may replace soft links atomically, it may not. What it ZNC creates it's PEM file at exact moment between deletion and creation? I totally don't know. Sounds like an undefined behavior.

What would be the downsides of running ZNC as root in docker?

That's a security risk? It's easier to escape the container as root than as non-root.

it prints custom misleading error message about file purportedly being not found.

I agree, the message could be improved to tell what exactly went wrong.

This check does nothing right.

PRs with fixes are welcome.

how about doing self-test GET request?

That could work. I'm not sure it worth though. Does nginx do anything like that?
Again, we could just remove the check. But currently ZNC reads the key upon accepting a connection, and the current error message is better than failing to start handshake, because that's harder to debug. The proper fix would be to read the file on startup, and provide a way for certbot to trigger re-reading it.

Are you 100% sure it can not be misused (apart from already masking real errors, that is)?

Correct.

If the answer is "yes", program would attempt to write to that same pem file as returned by the same CZNC::GetPemLocation() function.

If that file doesn't... khem... exist due to its location being inaccessible, then ZNC won't be able to write to it either.

That could work. I'm not sure it worth though. Does nginx do anything like that?

Nginx reads certificate & keys once. And only reloads them on configuration change (signal nginx -s reload). It doesn't just check for file existence, but actually loads the keys. So if that went smoothly, I'm sure it will be alright from that point onward.

Again, we could just remove the check. But currently ZNC reads the key upon accepting a connection, and the current error message is better than failing to start handshake, because that's harder to debug. The proper fix would be to read the file on startup, and provide a way for certbot to trigger re-reading it.

Yeah, that's kinda wasteful. Definitely something to improve on.

Are you 100% sure it can not be misused (apart from already masking real errors, that is)?

Correct.

How may I verify this statement for correctness?

If that file doesn't... khem... exist due to its location being inaccessible, then ZNC won't be able to write to it either.

Think carefully, think twice.

ZNC checks file via symbolic link — not accessible
Certbot initiates renewal
ZNC prompts to create PEM file — because it "thinks" file does not exist
Certbot removes old link
Just before certbot installs new link...
ZNC creates dummy PEM where the link was just a moment ago.
< -- Undefined state with race condition starts here

Think carefully, think twice.

Could you be less aggressive, please?
Step 3.5 in your scenario: user clicks Yes on that prompt. Does the user not know that he configured certbot before? If user doesn't know what he's doing, we can't protect from that. User has access to run ZNC and/or to overwrite any files he pleases.
Anyway, this is dupe of #1215 - when ZNC gains ability to read the cert once, on startup, it won't need such separate check on startup.

Yeah, sorry. I'm just feeling terribly annoyed, because the first step toward a solution is acknowledging the problem at hands, which is like... not happening here.

Does the user not know that he configured certbot before?

First, I don't ever assume that users knows what they are doing. Second, they might know, and might not; they might even not be administrators (znc is designed to be run as non-root anyway). I, for example, share my server with friends to run some web stuff like znc, and I am the one doing DNS and certificates management — I certainly wouldn't wanna let them mess it up even by pure accident, i.e. without malicious intentions.

Anyway, this is dupe of #1215 - when ZNC gains ability to read the cert once, on startup, it won't need such separate check on startup.

Not much of a duplicate, as I've raised totally different concerns here. Although a good solution might resolve both issues at once. Thanks for pointing out, I'll take a look at what can be done there as well.
Closing this means that (1) an error message became adequate, (2) race conditions are eliminated. Possibly, (3) an option to run ZNC as root or otherwise integrate nicely with letsencrypt/certbot out-of-the-box. For option (3) updating some documentation on ZNC wiki wouldn't hurt.
Thus, please, consider reopening.

This issue seems to only describe half of what could be the problem. Under OpenBSD 6.8 I was experiencing the following scenario:
I placed the cert into the .znc directory and added it to the config:
SSLCertFile = ~/.znc/cert1.pem

znc kept nagging that it wasn't able to locate the pem file, even though the same user it was running under could cat the file. At some point I didn't know what to do and simply pressed y, to let znc create the pem. This was what it resulted in:

Turns out that in my config I had a whitespace at the end of the certificate name. I kid you not. My config was SSLCertFile = ~/.znc/cert1.pem  instead of SSLCertFile = ~/.znc/cert1.pem. Hence znc wasn't unable to find the pem and so it created a file that had a whitespace at the end of its name.


Adopt a Widget - MaterialBanner

The MaterialBanner widget needs:

A code / DartPad sample

For details about how to participate, see flutter.dev/adoptawidget

I would like to be assigned to this issue


disable filter dropdown on maintenance detail

Types of changes

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

Checklist:

[x] The code follows the code style and conventions of this project.
[ ] The change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.

Description of the change

disable filter dropdown on maintenance detail

Motivation for the change

fix #614

@maple10001,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Benchmak CLI

A simple CLI to easily test disco via the terminal, e.g.
npm run benchmark -- --numberOfUsers 3 --epochs 2 --roundDuration 1

Once Decentralized is working again we can also include the training scheme as a flag.
This will make it much easier for developer / students to test out their features while they are building them.
Closes #261

super nice!! maybe add the new result folder to .gitignore? and remove it in a future commit to ensure it is not merged into develop :)


fix next version conflict

This fixes the conflict between Next.js versions logged during Next dev and build commands.

Is anyone still maintaining this project?


Hotfix: Fixes nonce edge case with Rosetta

When a transaction is received in the same block that a transaction is sent, the nonce returned by the account-balance lookup returns an older nonce. There was also another edge case that hasn't occurred yet where nonces could be off-by-one, this is also now fixed.
Ultimately this is caused by the archive processor writing balance entries with a nonce that doesn't take into account new nonces that may have been written within the current block.
Explain your changes:

The query-pending SQL is broken apart into separate balance and nonce components. The nonce component takes the latest 255 entries and picks the maximum nonce to workaround this bug. This will cover the case where this block sends many transactions but receives one and breaks the rules.
Additionally, in certain fallback situations when the balance entries don't exist for one reason or another (archive failures for example), we were reading nonces from user commands but not adding one to account for the incremented nonce in that account. This branch of the code has not been used yet, but it is fixed now just in case this does occur soon.

Explain how you tested your changes:

Connected to Mainnet and tested a known query that triggered this edge case and a few that didn't of different shapes to ensure no regressions

I don't have quite enough context to fully review this, but the parts that I understand look good to me:

The OCaml code LGTM
The strategy taken to replace the actual nonce in the original query with the highest nonce in the same block, also seems correct to me. (Although I'm not proficient enough in SQL to assert that the SQL code correctly implement this strategy)


pulled functionality out into unique files

Reorganized files into their individual silos.
The tests could be split up as well.

Thanks!


Implement LifecycleOwner in tests

Proposed Changes

Implement LifecycleOwner in tests, provide it in LocalLifecycleOwner
Provide the means to change Lifecycle in runComposeUiTest

Testing
Test: LifecycleInTestsTest

Does Android provide LifecycleOwner in tests?

Does Android provide LifecycleOwner in tests?

I don't think so.
Delegating the review to m-sasha, as the owner of ui-test

@m-sasha On Android it might be used via activity/fragment. See TextFieldFocusCustomDialogTest or LifecycleOwnerInAppCompatActivityTest

If Android's ui-test doesn't include lifecycle stuff, I'm thinking maybe we shouldn't either. Can we provide the same functionality from e.g. lifecycle-test?


Drill to detail fails with "Error: 400 Bad Request: The CSRF tokens do not match."

Bug description
In 4.0.0rc1, drilling to detail on seemingly any chart generates an error message: "Error: 400 Bad Request: The CSRF tokens do not match."  This is a regression from 3.1.1 where I can drill on these charts successfully.
How to reproduce the bug
Right click on a chart, drill to detail.
Screenshots/recordings
4.0.0rc1:

Same operation succeeds in 3.1.1:

Superset version
master / latest-dev
Python version
I don't know
Node version
I don't know
Browser
Firefox
Additional context
Possibly relevant config:
SESSION_COOKIE_SAMESITE = 'None'
SESSION_COOKIE_SECURE = True
HTTP_HEADERS = {'X-Frame-Options': 'ALLOWALL'}
ENABLE_PROXY_FIX = True

Stacktrace:
<IP_ADDRESS>:58134 - - [07/Mar/2024:15:24:48 +0000] "POST /superset/log/?explode=events&dashboard_id=83 HTTP/1.1" 200 1 "https://analyticstest.a2gov.org/superset/dashboard/a2fixit/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0"
2024-03-07 15:24:49,218:INFO:flask_wtf.csrf:The CSRF tokens do not match.
Refresh CSRF token error
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 261, in protect
    validate_csrf(self._get_csrf_token())
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 115, in validate_csrf
    raise ValidationError("The CSRF tokens do not match.")
wtforms.validators.ValidationError: The CSRF tokens do not match.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1821, in full_dispatch_request
    rv = self.preprocess_request()
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2313, in preprocess_request
    rv = self.ensure_sync(before_func)()
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 229, in csrf_protect
    self.protect()
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 264, in protect
    self._error_response(e.args[0])
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 307, in _error_response
    raise CSRFError(reason)
flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF tokens do not match.
2024-03-07 15:24:49,219:WARNING:superset.views.base:Refresh CSRF token error
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 261, in protect
    validate_csrf(self._get_csrf_token())
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 115, in validate_csrf
    raise ValidationError("The CSRF tokens do not match.")
wtforms.validators.ValidationError: The CSRF tokens do not match.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1821, in full_dispatch_request
    rv = self.preprocess_request()
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2313, in preprocess_request
    rv = self.ensure_sync(before_func)()
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 229, in csrf_protect
    self.protect()
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 264, in protect
    self._error_response(e.args[0])
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 307, in _error_response
    raise CSRFError(reason)
flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF tokens do not match.
HTTPException
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 261, in protect
    validate_csrf(self._get_csrf_token())
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 115, in validate_csrf
    raise ValidationError("The CSRF tokens do not match.")
wtforms.validators.ValidationError: The CSRF tokens do not match.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1821, in full_dispatch_request
    rv = self.preprocess_request()
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2313, in preprocess_request
    rv = self.ensure_sync(before_func)()
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 229, in csrf_protect
    self.protect()
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 264, in protect
    self._error_response(e.args[0])
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 307, in _error_response
    raise CSRFError(reason)
flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF tokens do not match.
2024-03-07 15:24:49,219:WARNING:superset.views.base:HTTPException
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 261, in protect
    validate_csrf(self._get_csrf_token())
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 115, in validate_csrf
    raise ValidationError("The CSRF tokens do not match.")
wtforms.validators.ValidationError: The CSRF tokens do not match.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1821, in full_dispatch_request
    rv = self.preprocess_request()
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2313, in preprocess_request
    rv = self.ensure_sync(before_func)()
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 229, in csrf_protect
    self.protect()
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 264, in protect
    self._error_response(e.args[0])
  File "/usr/local/lib/python3.9/site-packages/flask_wtf/csrf.py", line 307, in _error_response
    raise CSRFError(reason)
flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF tokens do not match.

Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Doh, I cannot replicate this again.  Drilling to detail is fine now.  Maybe false alarm?  I wonder what happened.  All I can think is that maybe my session expired but I was still able to click charts?  I have no idea, I will close this unless I can replicate.


Update package-immutability.md

Why:
Fixes #122 .
What's being changed:
The original issue refers to this page only. However, the indicated text comes from the reusable being modified by this PR.  New content for private packages as per the original issue author's suggestion.
Additional information
This PR affects not only the page referenced by the issue, but also every other page that depends on this reusable.
Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging.
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Thanks @casals 💝 I'll send this over to the @github/docs-content-ecosystem team for review!


New stubs class generate class definition conflict with existing classes in downstream project

Context
Project using PHPStan for static analysis on Castor tasks, the stub file is included in phpstan.neon using the bootstrapFiles directive:
parameters:
    bootstrapFiles:
        - .castor.stub.php

Problem
Since the latest release, running PHPStan with the included stub results in a fatal error because some class included here https://github.com/jolicode/castor/blob/main/src/Stub/StubsGenerator.php#L81 could already be present in the current execution context
I would like to establish the best way to solve that problem and then I could try to submit a PR to resolve the problem.

Not sure to see why this would break on latest release only. Unless I'm wrong, the stubs changed on #536 only to fix the the PHPDoc not using FQCN, but the array of frequently used classes you mention did not change (we also removed some privacy props/method/const from the stubs and added some Castor internal classes, but nothing else related to vendor classes).
What was the exact error you faced?

Hello @pyrech you are right sorry for the misunderstanding, i updated from [v0.18.2] to [v0.19.0]
The problem i am facing is when i run phpstan using the stub as bootstrapFiles on a project already using classes in the frequently used classes array i get the following error :
Fatal error: Cannot declare class Symfony\Component\Console\Application, because the name is already in use in /app/.castor.stub.php on line 1108

Is it fixed by https://github.com/jolicode/castor/pull/552?

Hello @lyrixx
Same behavior with #552 the Symfony\Component\Console\Application class stub still present in the generated file.

I was trying to reproduce your issue but without luck. Then I figured that on our projects, we confgure phpstan like this:
parameters:
    scanFiles:
        - .castor.stub.php

According to PHPStan documentation, scanFiles seems more appropriate to load stub files. Could you confirm whether if it solves your issues?

thanks for the finding @pyrech this is working perfectly.


US & CA tax updates

Docs Build status updates of commit dc1abe9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/payroll/CAN18YETax.md
:white_check_mark:Succeeded
View

dynamics-gp/payroll/US19JanTaxR1.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


reference: remove duplicate compose navigation

The compose cli reference section contained links to all compose
commands, but all of them were redirects to the "compose" section
in the Docker CLI reference.
This patch:

removes the duplicated navigation
changes the Docker Compose CLI reference section into a link to
the new location
moves the "overview" and "environment variables" pages inside
the new section (this page should possibly be merged into the
CLI overview, which lists all environment variables).

Before:

After:

./cc @usha-mandya @dockertopia

Thanks @usha-mandya, @thaJeztah and I went over this during our sync today so I'm going ahead and merge this.


Add validator in rich status

Wait for https://github.com/cryptape/cita-proto/pull/25

Codecov Report

Merging #153 into develop will decrease coverage by 0.02%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##           develop     #153      +/-   ##
===========================================
- Coverage    35.44%   35.41%   -0.03%
===========================================
  Files          142      142
  Lines        26483    26505      +22
===========================================
  Hits          9387     9387
- Misses       17096    17118      +22

Impacted Files
Coverage Δ

authority_manage/src/wal.rs
0% <ø> (ø)
:arrow_up:

authority_manage/src/lib.rs
0% <0%> (ø)
:arrow_up:

libproto/src/protos/blockchain.rs
12.17% <0%> (-0.14%)
:arrow_down:

libproto/src/protos/executor.rs
0% <0%> (ø)
:arrow_up:

rlp/src/stream.rs
39.13% <0%> (+1.76%)
:arrow_up:

Continue to review full report at Codecov.

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


Remove Email Field

Email field has been made redundant as of #46 . We plan to replace it with another feature (perhaps Amenities/Favourites/Last Visited etc), so tests using this have been temporarily commented out.


Travis branch

Codecov Report

Merging #36 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #36   +/-   ##
=======================================
  Coverage   55.61%   55.61%
=======================================
  Files           1        1
  Lines         863      863
=======================================
  Hits          480      480
  Misses        383      383

Continue to review full report at Codecov.

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


Fixed automatic documentation

Closes #38: Docstrings are now correctly extracted from modules and documentation is accessible at https://pk-model.readthedocs.io/en/latest/index.html.

Codecov Report

Merging #61 into master will increase coverage by 1.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #61      +/-   ##
==========================================
+ Coverage   93.42%   94.54%   +1.11%
==========================================
  Files           8        8
  Lines         213      220       +7
==========================================
+ Hits          199      208       +9
+ Misses         14       12       -2

Impacted Files
Coverage Δ

pkmodel/tests/test_model.py
100.00% <0.00%> (ø)

pkmodel/model.py
82.25% <0.00%> (+4.29%)
:arrow_up:

Continue to review full report at Codecov.

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

Good work Stella! 👍


Review previous steps on roadmap

Detail the completed and pending steps

Maybe would be good to add the new Git Flow Roadmap to the documentation

The requested changes have been made. The doubt remains regarding the topics not yet covered, in my point of view. I suggest leaving a separate document so that, when addressed, such topics can be incorporated into other existing documents.


[BUG] VDOM options - Interfaces

Bug description
All interfaces are extract and then if we have a lot of VDOM, generation will be longer and we had to delete manually informations.
Command-line input
New-AsBuiltReport -Report Fortinet.FortiGate -Target FQDN -Username demo -Password 'demo' -Format Html -OutputFolderPath 'C:\monuser\AsBuiltReport' -Timestamp
Steps to reproduce
Edit .json and put a VDOM name which exist on the FortiGate
Generate a report with an account which can access more than the VDOM to document.
Expected behaviour
I want to only get interface attached to the VDOM and not to the global VDOM.
Screenshots

Operating System
Windows Server
PowerShell Version
5.1.14409.1029
PowerShell Modules
Name                             Version

AsBuiltReport.Core               1.3.0
AsBuiltReport.Fortinet.FortiGate 0.2.0
AsBuiltReport.Fortinet.FortiGate 0.1.1
PowerFGT                         0.7.0
PScribo                          0.10.0
Additional Context
It's not a PowerShell issue but certainly a wrong execute command or in wrong context/emplacment.
Before submitting

[X] I have read and followed the bug reporting guidelines.
[X] I have read the documentation, and referred to the known issues before submitting this bug report.
[X] I have checked for previously opened & closed issues before submitting this bug report.

Hi 👋
it is by Fortigate API design… (and found a CVE about this…) what release do you have ? The account have access to all interface ?
i will look for display only selected vdom…

Hi Alexis,
The request is done with a super_admin account. So he get access to everything 😉
I don't try with a limited account with a VDOM limit access.
We are on FortiOS 7.0.12
Cordialement,
Renaud HUMBERT
Support Technique Client TSR
[cid:8d3d1046-a61b-43d5-9884-12f716d56792]
<EMAIL_ADDRESS>[cid:fbbf8ed6-3222-4f70-ab6e-c6d1f93607e2]
0383988930
[cid:0e979c33-4895-4ca2-9119-40c308d7174d]
Agence et Datacenters de Nancy
[cid:a8e089fa-c8c8-403e-929e-45dd5a4ee703] [cid:9ec59f79-64fb-442e-a483-3527724082cf]  [NSE 7] [cid:09bf4535-92ff-452c-91d2-c7c15fec5b09]
[Fortinet FortiAnalyzer 6.4 Administrator][Fortinet FortiGate 7.0 Administrator][Fortinet FortiManager 6.4 Administrator][Fortinet SD-WAN 6.4 Architect]
[cid:97db6a45-1180-4eab-abc1-170f41521d59]
[cid:97128539-d823-4ac6-8213-c84a2944198b]https://www.adista.fr/
[cid:d1198fdd-8859-4ae2-a3d5-54304e19632d]https://twitter.com/adistafrance
[cid:2f1aab13-82a9-4493-84d9-8f95664f9ab5]https://www.youtube.com/user/adistafrance
[cid:fc994cf4-0502-4444-bfcc-82c2cfccd71d]https://fr.linkedin.com/company/adista
[cid:81c6433a-d013-4f58-943c-6ecdccd89d92]https://www.facebook.com/adistafrance/

De : Alexis La Goutte @.>
Envoyé : vendredi 11 août 2023 12:31
À : AsBuiltReport/AsBuiltReport.Fortinet.FortiGate @.>
Cc : Renaud HUMBERT @.>; Author @.>
Objet : Re: [AsBuiltReport/AsBuiltReport.Fortinet.FortiGate] [BUG] VDOM options - Interfaces (Issue #44)
[Externe inherent]
Ne cliquez pas sur les liens, ou n'ouvrez pas les pièces jointes à moins de connaître l'expéditeur et de savoir que le contenu est sûr.
Hi 👋
it is by Fortigate API design… (and found a CVE about this…) what release do you have ? The account have access to all interface ?
i will look for display only selected vdom…
—
Reply to this email directly, view it on GitHubhttps://github.com/AsBuiltReport/AsBuiltReport.Fortinet.FortiGate/issues/44#issuecomment-1674537840, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2MNOMMMJHW2IEIZPOI55S3XUYCXXANCNFSM6AAAAAA3MVI6G4.
You are receiving this because you authored the thread.Message ID: @.***>


Documentation for release and update process

Add some docs for release process and how to update tachyon in cloudformation.

Fixed typo


[DRAFT: DO NOT MERGE] Analyzers UI

Scope & Purpose
This (draft) PR adds a new section in the web interface to list/view/add analyzers via the web UI. As of creating this draft, the following analyzers are supported:

Identity
Delimiter
Stem
Norm
N-Gram
Text

The following analyzers are yet to be supported (currently under development):

AQL
GeoJSON
GeoPoint
Pipeline

Once the above analyzer UIs are ready and added to this PR, it will be ready for final review and merge.
Target Release: 3.10.
The UI is built on the React Framework, but a few parts in the legacy frontend code may have been touched upon to support the integration. The following features are available:

See a list of available analyzers.
View an analyzers details - name, type, features and properties.
Delete an analyzer (if the user has the necessary permission, and the analyzer is not built-in).
Add an analyzer - one of the aforementioned types. Several ways are supported:

Using a type-specific form.
Using a JSON code editor.
Using an existing analyzer as a starting template, from where it can be edited using either of the above.

CHANGELOG entry, feature documentation and release notes are pending.

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[x] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[x] No backports required
[ ] Backports required for: (Please specify versions and link PRs)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[ ] Enterprise PR:
[x] GitHub issue / Jira ticket number: https://arangodb.atlassian.net/browse/APM-115?atlOrigin=eyJpIjoiNDM4YjMwYTY1OTdlNDI5Zjg4OGQ3OTdiYWZmMjMzZjEiLCJwIjoiaiJ9
[x] Design document: https://docs.google.com/document/d/1ObcVYCb1Sy0_Op_63EoQKy8pUDW1NPpWz9HDdYPqOpI/edit

Testing & Verification
(Please pick either of the following options)

[ ] This change is a trivial rework / code cleanup without any test coverage.
[x] The behavior in this PR was manually tested
[ ] This change is already covered by existing tests, such as (please describe tests).
[ ] This PR adds tests that were used to verify all changes:

[ ] Added new C++ Unit tests
[ ] Added new integration tests (e.g. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

Link to Jenkins PR run: https://jenkins.arangodb.biz:3456/view/PR/job/arangodb-matrix-pr/16524/
Documentation

All new features should be accompanied by corresponding documentation.
Bugs and features should furthermore be documented in the CHANGELOG so that
support, end users, and other developers have a concise overview.

[ ] Added entry to Release Notes
[ ] Added a new section in the Manual
[ ] Added a new section in the HTTP API
[ ] Added Swagger examples for the HTTP API
[ ] Updated license information in LICENSES-OTHER-COMPONENTS.md for 3rd party libraries

External contributors / CLA Note
Please note that for legal reasons we require you to sign the Contributor Agreement
before we can accept your pull requests.

@adityamukho

Once the above analyzer UIs are ready and added to this PR, it will be ready for final review and merge.

Couldn't we somehow mark them as "disabled" in code? Or hide them? Then we could merge before. But both is fine for me (either merge now/soon or later).

@adityamukho

Once the above analyzer UIs are ready and added to this PR, it will be ready for final review and merge.

Couldn't we somehow mark them as "disabled" in code? Or hide them? Then we could merge before. But both is fine for me (either merge now/soon or later).

I'm not sure we can do that. It was decided not to merge until all analyzers are ready. For now, the ones that are not yet supported are not even present in the UI, and are thus effectively hidden.


container pattern not working when having tokens

Description
When having tokens in panda.config.ts, container pattern function or even using Container jsx has invalid css values like "max-width: 8xl". When I remove tokens from config it works perfectly fine.
In the panda css playground I provided there is nothing in tokens but even with something defined in tokens it doesn't work. The simple fact of having tokens in config make container stop working properly. I tried with stack pattern and it works fine. Semantic tokens doesn't seem to make container bug.
Link to Reproduction
https://play.panda-css.com/5WJY2rWIEO
Steps to reproduce
No response
JS Framework
react (TS)
Panda CSS Version
0.9.0
Browser
Google Chrome 115
Operating System

[ ] macOS
[X] Windows
[ ] Linux

Additional Information

you're replacing the tokens entirely instead of extending them, change your config like so:
- theme: { extend: {}, tokens: {} },
+ theme: { extend: { tokens: {} }, },

you're replacing the tokens entirely instead of extending them, change your config like so:
- theme: { extend: {}, tokens: {} },
+ theme: { extend: { tokens: {} }, },

It works perfectly, thank you !


Clean build failing due to missing npm codepage 1.3.8 module

xlsx 0.8.0 depends on codepage "~1.3.6".  The npm logic finds 1.3.8 and tries to pull that, but is failing with the following output on our jenkins server:
npm  ERR!  fetch failed  https://registry.npmjs.org/codepage/-/codepage-1.3.8.tgz
npm  WARN  will retry, error on last attempt: Error: fetch failed with status code 502
Manually pulling this URL fails with 502 also.  Did something break with the published npm packages for codepage?

@mbeynon what version of node / npm are you using? Also, can you check if the same problem shows up with xlsx 0.8.1?


Attempt to fix chrome experimental waterfalls

Taking in account previous connection to calculate start time of any new requests that reuse the connection and also adding options to disable cache
Before and after:

I'm going to try to refactor this to capture the time and store it as blocking time instead of bumping out the start time. Blocking is where it should be anyways.

Great, that makes more sense I think

Getting an issue with redirected URLs, so I'll have to take a look at that tomorrow, but I feel like it's getting closer.

Rebased these changes into a single commit, so opened #109

Hello,
Me and my family have visited a very cozy place recently, you may really like it, just take a look at some pics of it http://thingoquethi.darioscollection.com/xynpck
Looking forward<EMAIL_ADDRESS>


Enhancement: Pasting signatures only where you are.

If possible, only allowing signatures to be pasted into the system you are currently in, or, perhaps creating a confirmation popup if you try pasting to a hole you are not in.

Do you mean with "pasting" the "signature reader dialog"? - Or the lazy way: You can simply press CTRL + v. If a system was selected the signatures will get updated automatically.
To prevent update signatures in other systems is very important. So a confirmation dialog, and/or a visual warning should work as well, what do you think?

Yep, either a confirmation or warning - either way as long as it gives you a chance to cancel your action.
I wouldn't want to completely remove the ability to paste to other systems, occasionally, you leave a system, remember you didn't paste the sigs, but still have them saved to your clipboard.

I made the following changes:

A new confirmation dialog for signature update was added:
Update signatures by pressing ctrl + v on a selected system, which is not the current system of a character, will show a confirmation dialog.


Add deprecation notices about cookiecutter and django

As discussed in #175 we should include a deprecation notice, so the users are aware in future changes in the interface.

Coverage remained the same at 98.469% when pulling 1436295e99bfdbdba5b17f0f12828cedd2d0020f on abravalheri:deprecation-notice into 013ef529b09826d84cb270dfb9ecea4b8a0b8c2c on blue-yonder:master.

@abravalheri Thanks!


Navbar bug in Contact Page

The hamburger menu seems to be collapsing with the data

I want to work on this under JWOC

@smaranjitghose @anushbhatia can you please have a look at the issue and the PR


High frequency IMU topic acts wierd.

Hi, thanks for the great code.
I am using Velodyne VLP-16 lidar and Xsens MTi-3 imu for building map.
When the freq of lidar topic is 10hz and freq of the IMU topic to 10hz, at least the base_link looks fine near the odom.

But when I increase the freq of the IMU topic from 10 to 100 hz, the base_link goes wrong.*(the path has a spiral pattern even the lidar and imu are standing still)

Here is my setting:
LIDAR
            x
       ^
       |
<------o  z
y

IMU
            x
       ^
       |
<------o  z
y

The README suggest us to use 500hz on IMU, so I think maybe something wrong with my setting? Or should I just go with 10hz on IMU?

I am also facing the same issue even though I am using 200hz of imu data

Hey,
I'm also having this issue with my IMU (SBG ellipseD). The IMU is flickering a little bit in all directions with a frequency of 200Hz. A few changes may need to be done in the settings but I am currently not able to figure out where the problem is exactly.
My settings of the frame directions are the same as @vinci-xiao.
Did anybody solved this problem already?
All the best,
Lennard

I am facing the same issue. Did anyone find any solution


Fix hat block spacing

Resolves
What Github issue does this resolve (please include link)?
Fixes https://github.com/LLK/scratch-blocks/issues/838
Proposed Changes
Describe what this Pull Request does
Adds Blockly.BlockSvg.START_HAT_HEIGHT to the y offset in the flyout layout method for hat blocks. This offset was being added to the top, but not to the y offset for the bottom, squishing blocks together.
Reason for Changes
Explain why these changes should be made
Bug reported https://github.com/LLK/scratch-blocks/issues/838
Incidentally this problem actually already existed, it just wasn't as obvious because of the previous large spacing. You can tell looking back before the margin that something wasn't right:

Test Coverage
Here are some before/after screenshots:
Before

After

Landing for test. @rachel-fenichel happy to revert after testing if desired.


Add server-side search for all pages

Similar to: https://github.com/casbin/casdoor/issues/268
It can be implemented by antd easily:

https://ant-design.gitee.io/components/table/#:~:text=filter dropdown items-,searchable,-.

https://ant-design.gitee.io/components/table/#:~:text=a customized column-,search,-example via filterDropdown

@seriouszyx this can be put in next steps.


Remove unnecessary negations which broke Thermal Expansion and Thaumc…

…raft recipe handlers.

apologies, I just realised this is probably to stop the "stuck modifications", is there a possibility for a config option to override this so I don't have to restart mc while building the scripts?


Add grid websocket approach

Server app and client working properly using HTTP protocol + Socket IO communication pattern

Async websocket grid app
Sync websocket grid client

PS: I noticed that @mccorby  had already implemented a client version using the socket io approach. I made only a few adaptations to fit the pattern that was adopted in this repository.(Thanks @mccorby :smiley: ) .
TODO:

Add Heroku  deployment settings.
Improve a security level using the HTTPS protocol (It is apparently already enabled, but the creator of the socket io library does not provide in the documentation a way to test with self-signed certificates for security reasons). But it should work with certificates signed by certifying entities
Issue link: https://github.com/miguelgrinberg/python-socketio/issues/283

Good one!
Be aware that this implementation blocks the server socket. To allow the same socket to be used by more than one client we would need to modify the way the flags (they should be threading.Event()) do the blocking.
My idea is to create an object per client so that the server would block depending on the client identifier (so every operation coming through socketio should include the client's id)

Related to #200

Branch status Update:

Deploy on Heroku : DONE
Perform HTTPS connections: DONE (The client is already compatible with the protocol.)
Add eventlet worker proxy to manage balance and control concurrency

Problems to solve:
I send and retrieve the tensors correctly. However, when trying to perform arithmetic operations with them, I get this warning followed by a string of exceptions.
WARNING:root:Worker me couldn't recognize worker 0
Has anyone had a similar problem? @iamtrask @mari-linhares

Can you send an example of how you're doing it? I would say that probably these tensors are not owned by the same owner. When you send/retrieve an object you'll need to update the tensor's location and owner (for grid workers I don't think this is done automatically).

Problem solved. Just needed to specify the worker id.
Experimental Notebook


Remove win is not fully resetting ratings sometimes

Need to make sure that the oldRating value is being reset accurately on multiple deletes

Be able to select game as well


JSON key support?

Just created a service account, and noticed it gives the option for a .json key, is/will this be supported?
example file:
{
  "type": "service_account",
  "project_id": "blahblah",
  "private_key_id": "123...",
  "private_key": "-----BEGIN PRIVATE KEY-----\n_LOTS_OF_STUFF_IN_HERE_==\n-----END PRIVATE KEY-----\n",
  "client_email"<EMAIL_ADDRESS>  "client_id": "123...",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://accounts.google.com/o/oauth2/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/blahblahblah.iam.gserviceaccount.com"
}

Added support for json key.
Just read the json key and export private key part as a key var in your config.
You can use something like this.
var fs = require('fs');
const KEYPATH = '../json-googleapi-key';
var json = fs.readFileSync(KEYPATH, 'utf8');
var key = JSON.parse(json).private_key;
module.exports.key = key;

Thanks for that 😄


newsboat: Add a new module for newsboat

A program module for configuring newsboat. Or at least the initial module for it.
It supports right now just a few configuration values, stuff that I mostly use, as well as support for urls, tags and queries.

Much nicer, thanks for the improvements :-)
Rebased to master in 4caa45b8bb2ee8aafcfaa2e96328127b9d19ce0f.


fix pipewire equalizer filename and change path

First, there is an error in the file name of cp. The actual file name is sink-eq.conf.
Secondly, I think it's more appropriate to copy it directly to the etc path because the script is executed as the root user, and the original cp command will create it in the root home directory.

This is the correct fix for the current issue, but were looking at #89 as a possible better solution.

Issue resolved in #89


Can I reduce the size of the text in the pages list view?

Hi, this is more a question than a feature requests. Since i'm not very good at Tweaking things I ask here if this is easily possible.
My problem is that I will do a Medicine database so for each chapter I'll have a huge list of pages.
In the current configuration  when you deploy a chapter to display the list of pages inside, the fonts is quite big and there is a ton of spacing between each page title, which looks nice but when you have about 150 page to display a more "compacted" list would be more useful for me.
If there is an easy way (1-2 lines of code somewhere to edit) I'll gladly take it. If it's too complicated, well I'll forget about it...
Thanks for the help

Hi @guischmo,
Sorry for the late response.
This is possible with a little bit of custom CSS. Add the following to the "Custom HTML Head Content" option in the settings area:
<style>
	.book-content .entity-list h4, .chapter-content .entity-list h4 {
		font-size: 1.2em;
	}
</style>

You can tweak the 1.2 above to suite your needs. The default in BookStack is 1.666. Note that future BookStack updates could affect this tweak.

Closing this off as it appears to be answered and no follow-up seems to be required.


fix: Distribute rootfs

…ory under rootfs

Describe what this PR does / why we need it
Does this pull request fix one issue?

Distribute rootfs and ensure that there is an application directory under rootfs

Describe how you did it
Describe how to verify it
Special notes for reviews

Codecov Report
Base: 20.77% // Head: 20.76% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (d02b535) compared to base (3f404f5).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1797      +/-   ##
==========================================
- Coverage   20.77%   20.76%   -0.02%
==========================================
  Files          71       71
  Lines        6570     6574       +4
==========================================
  Hits         1365     1365
- Misses       5024     5028       +4
  Partials      181      181

Impacted Files
Coverage Δ

pkg/cluster-runtime/installer.go
0.00% <0.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Shader pass bugs

Since the number of supported shadow types was increased from 5->6 (in https://github.com/playcanvas/engine/pull/3763), some existing code mistakingly categorises shaders incorrectly.
For example see:
https://github.com/playcanvas/engine/blob/main/src/graphics/program-lib/programs/standard.js#L295 and https://github.com/playcanvas/engine/blob/main/src/graphics/program-lib/programs/standard.js#L479
We must:

change the constants defined at https://github.com/playcanvas/engine/blob/main/src/scene/constants.js#L631

redefine SHADER_PICK to be value 3
redefine SHADER_SHADOW to be value 4

perhaps add helper functions to make sense of it all
use the new helpers around the codebase instead of relying on the value 17 in the codebase
consider renaming the defines from SHADER_SHADOW to SHADERPASS_SHADOW

I've refactored the code in the linked PR. I have avoided the constant renames in this PR, as that would possibly create a larger conflict with shader refactoring open PR.


Draft 11 updates

Here are some missing -11 changes that turned up during my interop with @kazuho

Merged by hand


Code Sample isn't stand-alone

ServerConnection serverConnect = new ServerConnection();
refers to stuff in other samples. Not helpful.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b36c7b75-662d-293c-2588-457c82fb117f
Version Independent ID: 39c91bba-7655-25b8-b3f1-01b2705403af
Content: Sample: Export ribbon definitions (Developer Guide for Dynamics 365 for Customer Engagement)
Content Source: ce/developer/customize-dev/sample-export-ribbon-definitions.md
Service: crm-online
GitHub Login: @JimDaly
Microsoft Alias: jdaly

@rdegrove Thanks for your feedback.
We paste the sample code in the topic so that people get to see the actual sample code when they search for it. We also have links in this topic where you can download the entire sample code and also  to the helper code where the connection code is explained in details.
Closing this issue.


[RFC|DNM] cmake: Abstract toolchain usage

This commit:

Refactors the Zephyr's CMake build system
Removes hardcoded assumptions of GNU toolchain
Generalizes/lifts these out into separate "API" macros
API macro names are intent-based
Preserves most CMake containers/datastructures so a common
expectation is shared among toolchains.

As discussed in the TSC.
See presentation: https://drive.google.com/file/d/0B5NybbZNGEEdZWpxZzFmLVY3N3hxMzBHOUNQaVM4LTg2Sjd3/view?usp=sharing
TODO: More documentation of macros and the contracts between them and CMakeLists.txt.
Signed-off-by: Mark Ruvald Pedersen<EMAIL_ADDRESS>

Rebasing this to make CI run, will take some time.

The link from TSC MoM is behind access control for some reason.
Here is a working (personal) copy:
https://drive.google.com/file/d/1hGgk9ITFTXS3QoOr3GTFlC46VhEopT0Y/view?usp=sharing

I like the refactoring Mark! Still some work on the 'Hmmm' sections for Userspace support. Any thoughts on handling differences in linker command files formats (esp. the generated parts)?

I like the refactoring Mark!

Thank you!

Still some work on the 'Hmmm' sections for Userspace support.

To be pragmatic, I will defer that work until we need it: I bet the first many commercial-compilers are targetting systems without MPU and User mode threading.

Any thoughts on handling differences in linker command files formats (esp. the generated parts)?

Yes. The generated linker script is really just a preprocessed version of linker.ld which can come from the Board, SoC or via CONFIG_HAVE_CUSTOM_LINKER_SCRIPT. Every linker.ld in Zephyr is meant for GNU ld compatible linkers, so that leaves us with CONFIG_HAVE_CUSTOM_LINKER_SCRIPT where we, for now, have to supply a custom-written linker file through. Then it will pass through the preprocessor like the others, which is fine.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6de96b1). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #11551   +/-   ##
=========================================
  Coverage          ?   48.23%
=========================================
  Files             ?      279
  Lines             ?    43291
  Branches          ?    10359
=========================================
  Hits              ?    20881
  Misses            ?    18270
  Partials          ?     4140

Continue to review full report at Codecov.

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

I am missing documentation for the 'intents'.

That documentation has actually been provided. E.g. toolchain_cc():
## @Brief: toolchain_cc: Macro that expands into compiler options.
## @Details:
##   toolchain_cc must have been defined by compiler/${COMPILER}.cmake, where
##     COMPILER was set by toolchain/${ZEPHYR_TOOLCHAIN_VARIANT}.cmake.
##
##  --> 2. Toolchain-specific and Zephyr-specific:
##          Covers:
##            a. Mapping Kconfig "intents" to toolchain-specific flags (e.g. W,
##              CONFIG_SPEED_OPTIMIZATIONS, CONFIG_READABLE_ASM).
##            b. Mapping Zephyr expectations to toolchain-specific flags
##              PIC/PIE, freestanding,  inclusion of autoconf.h, expected
##              overflow behavior, etc.
##          Where: Should be placed in toolchain_cc() or toolchain_ld().
##          Note: It may be neat, but optional, to further subdivide
##            toolchain_cc down into toolchain_cc_{security,optimizations,cpp,
##            freestanding,warnings,diagnostics,asm}. Subdividing like this can
##            improve reuse

E.g. I would expect "security" to be documented. Or maybe even finer granularity than "security". But I definitely expect documentation at a finer level than toolchain_cc().

Well that documentation is by definition toolchain-specific. Hence I can only document the intention of what that macro should do, which was done above.
toolchain_cc_security() is a subdivision for GCC, as also written above. This subdivision can get documentation attached to it (which I will do), but is entirely specific to GCC.
To be clear: toolchain_cc_security() is therefore not a requirement to implement by every toolchain. But a toolchain may do so, if it sees fit.

This PR is way too big and does too many things, it is too difficult to review it, and too difficult to maintain it until it is ready for merging.

I feel the commits do what they say, and are described well enough.
The whole point of this is to clean up Zephyr's usage of CMake which is frankly already unreadable and dare I say, unmaintainable.
Of course there is going to be a gigantic diff when hundreds of lines of hard-codedness is replaced with a single toolchain_cc().
Regarding contribution workflow, it is not the law.
Big/revolutionary changes should be limited yes, but it isn't always possible is it?
12f8f76165 - Sebastian Bøe : Introduce cmake-based rewrite of KBuild
644 files changed, 7815 insertions(+)

Compared to my biggest commit:
34 files changed, 1102 insertions(+), 845 deletions(-)

To be clear: toolchain_cc_security() is therefore not a requirement to implement by every toolchain. But a toolchain may do so, if it sees fit.

There is something that is not quite right here. Let us take this line for instance;
zephyr_compile_options_ifdef(CONFIG_STACK_CANARIES -fstack-protector-all)
When STACK_CANARIES is enabled. It is not up to the toolchain to determine whether guard variables should be used or not. The user has enabled the feature, and expects it to be present no matter which toolchain he uses. If the toolchain does not support guard variables, this must be restricted through Kconfig.

Big/revolutionary changes should be limited yes, but it isn't always possible is it?

Not always, but it is in this instance. I have to insist that the contribution guidelines are followed before I invest time into getting this reviewed.

Not always, but it is in this instance. I have to insist that the contribution guidelines are followed before I invest time into getting this reviewed.

Alright, I understand. Many small PRs it is.
To avoid further NACKs, what are your max-size requirements?

To avoid further NACKs, what are your max-size requirements?

There is no LOC limit. The goal is for the code to be reviewable, traceable, and bisectable.
These types of things should be not be in the same commit (unless required for bisectability):
Adding docs/comments to existing functionality.
Refactoring existing functionality.
Changing existing functionality.
Adding new functionality.
Notably, these types of things can/should be in the same commit:
Adding new functionality and adding docs/comments to this new functionality.
Changing functionality X and changing functionality Y, when X is a backwards-incompatible change and requires changing Y.
It is okay to group together many unrelated comments into the same commit. Because adding a comment is unlikely to require a revert or a helpful commit message. But refactorings should not be grouped past a handful of recatorings because a refactoring might accidentally not be a refactoring, and might require a revert or a bisect.
Functionality should be separated as far as possible into independent features in individual commits. But only when it serves the purpose of being: reviewable, traceable and bisectable.

Will split up across smaller PRs.


added mustBeOverriden and mustCallSuper annotation. doesn't affect performance.

Hey. Great library!
I've started using it in production and I've made a few code changes.
Thanks to @mustCallSuper annotation you can enforce that extended classes contain the same parameters as the parent.
You can then in addition, add more hashParameters.
Without mustCallSuper:

With mustCallSuper:

Correctly implemented with mustCallSuper:

I've also simplified the code a bit and removed the abstract class component, feel free to revert this change.
Perhaps you can also instead of having mixin FastEquatable you could have abstract mixin class. Then you can use the FastEquatable either as a mixin or as a class without affecting performance.

Hello @bvoq ,
wow! Someone is interested in this package :) thank you for contributing!
For some reasons I missed your PR's, as I was not expecting some activity here, and also seem to overlook the email alerts. However, we gonna fix this now.
I think the abstraction is not needed anymore. I was thinking a bit too far ahead, when implementing it initially. I will merge your code as-it-is.
Thank you again :+1:

@bvoq your changes are included in the latest version ob pub.dev. Thanks again for the PR!


make install CARLA=../carla SR=../scenario_runner" errors

Hi
I follow the steps in Docs/Install.md and install all of them correctly up to "Installing DReyeVR". I have execute the following command which encounter error:
make install CARLA=../carla SR=../scenario_runner
  File "Scripts/install.py", line 22
    DOC_STRING: str = "Install DReyeVR atop a working Carla and/or ScenarioRunner directory"
              ^
SyntaxError: invalid syntax
make: *** [install] Error 1

I run this command with different python versions but error still remain:
python2.7,3.6
python3.8,3.9
I would be appreciate if someone help me to solve this error.

Hi there, this is almost certainly a python2 vs python3 problem since that syntax is Python3-only.
Curious, are you building on Windows?
The makefile (make) command defaults to the system python which might still be python2.7 since we actually assume you only have python3 installed (since python2 is deprecated). But you should be able to either make a symlink from python2 -> 3 or force it to use python3.
To see whether this is the problem, in your terminal (or command prompt) type:
python

and see whether this prompt (no suffix after python) is python 2 or 3. We require that this command invokes python3.

thank you for your response
I am building on Windows 10 and I execute this command on "WSL"

Ok that should be fine, note that you'll still need to run make launch and make PythonAPI and make package on the x64 command prompt though. But in WSL you should be able to run make install. What does the python command say your default python instance is?

Dear Gustavo, Many thanks for your assistance.
I works by uninstalling python2.7 and link python to python3 using the following commands:
sudo apt purge -y python2.7-minimal
sudo ln -s /usr/bin/python3 /usr/bin/python


Change docstrings from multiline datatypes to singleline datatypes

This patch changes how the datatypes of parameter are formatted
in docstrings.
For some datatype definitions of parameters in docstrings, the
different allowed datatypes were split over multiple lines to
make them easier to read and to avoid breaking the line length
limit. This is now changed so that these datatype definitions
always only consist of a single line, even if that severely
breaks the line length limit.
This is often horrendously ugly and very hard to read.
Unfortunately it seems to be the only format that is both
understood by Sphinx (when generating ReadTheDocs pages)
and PyCharm. Various ways seem to exist that make multiline
datatype definitions work in either of these cases, but
none that works in both cases. That is why it is now changed
to singleline definitions.

Codecov Report

Merging #386 into master will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #386      +/-   ##
==========================================
+ Coverage   95.61%   95.63%   +0.02%
==========================================
  Files          33       33
  Lines       10853    10853
==========================================
+ Hits        10377    10379       +2
+ Misses        476      474       -2


Some errors with status machine

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:
Currently when user creates a volume, api-server will create a volume object in database and update the status to creating, then controller will handler the rest and finally update the status to available or error based on the return value. But if some errors occur when apiserver connects controller, the operation would be abandoned and pull a error, but from user's view he can't find any problem and the status of volume would be set creating forever.
What you expected to happen:
Change volume status to error, rather than creating.
How to reproduce it (as minimally and precisely as possible):

Install opensds cluster
Stop osdslet service
Create a volume
Check the status of volume

Anything else we need to know?:
@xing-yang @wisererik
Environment:

Hotpot(release/branch) version: development branch
OS (e.g. from /etc/os-release): Ubuntu 16.04
Kernel (e.g. uname -a):
Install tools:
Others:

@leonwanghui : Please refer #674 for this issue, Thanks

@leonwanghui , can we close this? could you please check it again?

Actually this is due to the API flow issue as well. DB update to be done based on the action. / we need to optimize. I had created one issue for the backlog #870 . I am moving this to backlog.


Format YAML files when saving

The goal of this task is to format YAML files (e.g. config files, OpenAPI schemas) when saving them. The solution can be built upon the solution implemented for Java files in #719.

I initially considered using the ESLint Nx executor with the Prettier plugin, however a quick attempts failed. This article describes why using ESLint as a wrapper to run Prettier is a bad idea.

Formatting issues reported as problems by ESLint
It is a bit slower than running Prettier directly
You have another layer where bugs can be introduced

Options considered:

Run prettier directly
Format using Spotless but this may be difficult for projects that don't use Gradle like api-spec

Prettier can not solve SyntaxError on its own. Here using the Prettier extension for VS Code (see red button below).

The VS Code extension uses the prettier binary found in the path, instead of shipping with its own version of Prettier. This is great because Prettier should give the same result whether it is run via the VS Code extension or via the command line (git hooks, CI/CD workflow).
This is confirmed by the following error from the VS Code extension after uninstalling prettier.
["ERROR" - 2:07:50 AM] Failed to load module. If you have prettier or plugins referenced in package.json, ensure you have run `npm install`
["ERROR" - 2:07:50 AM] Cannot find module 'prettier' from '/workspaces/challenge-registry'
Error: Cannot find module 'prettier' from '/workspaces/challenge-registry'
	at Function.e.exports [as sync] (/home/vscode/.vscode-server/extensions/esbenp.prettier-vscode-9.9.0/dist/extension.js:1:37040)
	at t.ModuleResolver.findPkg (/home/vscode/.vscode-server/extensions/esbenp.prettier-vscode-9.9.0/dist/extension.js:1:7291)
	at t.ModuleResolver.getPrettierInstance (/home/vscode/.vscode-server/extensions/esbenp.prettier-vscode-9.9.0/dist/extension.js:1:3251)
	at t.default.format (/home/vscode/.vscode-server/extensions/esbenp.prettier-vscode-9.9.0/dist/extension.js:1:13317)
	at async t.PrettierEditProvider.provideEdits (/home/vscode/.vscode-server/extensions/esbenp.prettier-vscode-9.9.0/dist/extension.js:1:11197)
	at async x.provideDocumentFormattingEdits (/vscode/vscode-server/bin/linux-x64/74b1f979648cc44d385a2286793c226e611f59e7/out/vs/workbench/api/node/extensionHostProcess.js:87:45865)
["ERROR" - 2:07:50 AM] Prettier could not be loaded. See previous logs for more information.


musicbee: Update to 3.5.8447 and improve checkver

Closes #10567

[X] I have read the Contributing Guide.

/verify

/verify


Suggestion: Disable Indexing on Non-Wiki Pages

Currently, Google has indexed all the URLs available on my otterwiki instance. Normally this would be fine, but a lot of the search results point to sub-URLs such as the specific revision pages (URL including ?revision=) and the source pages.
I've solved this on my own system by modifying nginx confs to provide noindex headers, but this might be a good option to have for less technically inclined users. A settings dropdown could disable indexing for the non-wiki pages or even the whole wiki, for cases where an instance is only meant for personal documentation.

Hey @bwfiq,
Thank you for bringing this up! An Otter Wiki up to version 2.5.2 sets <meta name="robots" content="noindex, nofollow"/> only for page history, page attachments and page blame. Even for sane defaults this is not enough. Will add this to at least the changelog and pages displayed with a given `revision.
To amke this configureable in a convient way, I follow what you propsed. My first idea to implement this is to add a settings option that controls the generated /robots.txt.
When allowed the robots.txt is generated as
User-agent: *
Allow: /

else
User-agent: *
Disallow: /

For more complex configurations users should provide a custom robots.txt.


🐛 Bug Report: Homepage Layout fix required

📜 Description
The homepage layout is not properly aligned. The Navigation layout is overlapped on the main layout due to which some texts are not visible on the screen.

👟 Reproduction steps

Open developer tools on chrome or any browser.
Click on the toggle device toollbar icon. (Chrome - Ctrl + Shift + M)
Reduce screen size and the issue will be clearly visible.

👍 Expected behavior
The expected behaviour should be like:

Normal Screen

Developer mode

👎 Actual Behavior with Screenshots
All the screenshots were uploaded above.
Pay attention on the line starting with Enter a query related...
💻 Operating system
Linux
What browsers are you seeing the problem on?
Firefox, Chrome
🤖 What development environment are you experiencing this bug on?
Local Dev Server
🔒 Did you set the correct environment variables in the right path? List the environment variable names (not values please!)
No response
📃 Provide any additional context for the Bug.
No response
📖 Relevant log output
No response
👀 Have you spent some time to check if this bug has been raised before?

[ ] I checked and didn't find similar issue

🔗 Are you willing to submit PR?
Yes, I am willing to submit a PR!
🧑⚖ Code of Conduct

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

Hi Owner,
Looks like there is a whole new UI designed for this Website.
Thanks,
Harsh


Server crash

Mon_Jul_26-12.47.53-WIB_2021.log

Can you explain how this happened? What did you do before it crashed?

Can you explain how this happened? What did you do before it crashed?

I think i left the server in staff mode

Does it happen every time you logout in staffmode?

https://poggit.pmmp.io/ci/ItsMax123/StaffMode/StaffMode/dev:31
This might fix it, im still not 100% sure why it crashed tho.

https://poggit.pmmp.io/ci/ItsMax123/StaffMode/StaffMode/dev:31
This might fix it, im still not 100% sure why it crashed tho.
Keep me informed

Its fixed but when we rejoin we can fly in survival

When you join back are you in gamemode survival or in spectator mode?

When you join back are you in gamemode survival or in spectator mode?

Survival but we can fly

This bug hasnt been fixed

Fixed in commit 9da74f2
Download here: https://poggit.pmmp.io/ci/ItsMax123/StaffMode/StaffMode/dev:42


Adding the new map layouts

Adds the 3 map layouts proposed in slack to the environment.

Not sure how to test these with just a human agent locally. Is there a command I can run to do so?

Not sure how to test these with just a human agent locally. Is there a command I can run to do so?

Yep! Clone and setup the multiHRI repo and then run:
python scripts/run_overcooked_game.py

Some things to note:

By default, run_overcooked_game.py will load a trained FCP agent for 2 of the chefs, and allow you to play as the third (blue hat) chef.

Make sure you download this folder and save it at multiHRI/agent_models. This folder has pre-trained agents in it that we can use for evaluation during experiments

These are the lines that specify the path to the FCP agent that gets loaded for the game (that they assume you have performed the step above)

If you want to test your layouts, just change the string on this line to be the name of the layout you want to test.

If you're running in WSL, you will need to have an X-server (or similar) running so the pygame window can open

I'm testing the environments and it seems like with the long onion, if you place an empty plate next to the pot (img below), the game crashes with
Traceback (most recent call last):
  File "scripts/run_overcooked_game.py", line 42, in <module>
    dc.on_execute()
  File "/home/naren/Developer/py/mhri/multiHRI/oai_agents/common/overcooked_gui.py", line 274, in on_execute
    done = self.step_env(action)
  File "/home/naren/Developer/py/mhri/multiHRI/oai_agents/common/overcooked_gui.py", line 194, in step_env
    obs, reward, done, info = self.env.step(agent_action)
  File "/home/naren/Developer/py/mhri/multiHRI/oai_agents/gym_environments/base_overcooked_env.py", line 232, in step
    tm_obs = self.get_obs(c_idx=t_idx, enc_fn=teammate.encoding_fn)
  File "/home/naren/Developer/py/mhri/multiHRI/oai_agents/gym_environments/base_overcooked_env.py", line 199, in get_obs
    obs['subtask_mask'] = self.action_masks(c_idx)
  File "/home/naren/Developer/py/mhri/multiHRI/oai_agents/gym_environments/base_overcooked_env.py", line 182, in action_masks
    self.valid_counters, USEABLE_COUNTERS.get(self.layout_name, 5)).astype(bool)
  File "/home/naren/Developer/py/mhri/multiHRI/oai_agents/common/subtasks.py", line 156, in get_doable_subtasks
    elif obj.name == 'dish' and prev_subtask != 'put_plate_closer' and obj.position in valid_counters[p_idx]:
IndexError: list index out of range

This is okay just comment that line that causes the crash (its Stephane's code that we don’t use)

Should I push up commenting out those lines to the mutliHRI repo?

No, it’s fine
On Thu, Aug 29, 2024 at 7:53 AM Naren Dasan @.***>
wrote:

Should I push up commenting out those lines to the mutliHRI repo?
—
Reply to this email directly, view it on GitHub
https://github.com/HIRO-group/overcooked_ai/pull/2#issuecomment-2317727959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKFWIHHWAN75E2ZVP5RVV2DZT4RVDAVCNFSM6AAAAABNHOFGKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJXG4ZDOOJVHE
.
You are receiving this because your review was requested.Message ID:
@.***>


correct url writing

older url writing is failed to  jump correct web.

LGTM
Thanks for this.

@xiekeyang This PR should have modified doc/spec/api.md.tmpl, as well. Please submit a PR with the fixed template file.

@stevvooe Thanks! I will submit ASAP.

@xiekeyang Since this has already been merged, you'll need to submit a separate PR.

@stevvooe  will do!


I running DNSCrypt Loader 1.2 is fails

Hello ,
I  looked your page how to setup but is fails , what can i do ?
Where can find configuration file ? This mean /usr/local/etc/dnscrypt-proxy.conf or /usr/local/sbin/dnscrypt-loader ?
Thank
https://ibb.co/iOLeX5
https://ibb.co/d8WmC5
# dnscrypt-loader
root@debian:~# dnscrypt-loader 1.2
Tue Aug  1 09:18:06 2017 [ERROR] Error: no resolver name given, no configuration file either.
Tue Aug  1 09:18:06 2017 [ERROR] The easiest way to get started is to edit the example configuration file
Tue Aug  1 09:18:06 2017 [ERROR] and to append the full path to that file to the dnscrypt-proxy command.
Tue Aug  1 09:18:06 2017 [ERROR] Example: dnscrypt-proxy /usr/local/etc/dnscrypt-proxy.conf
Tue Aug  1 09:18:06 2017 [ERROR] The local list of public resolvers is loaded from: [/usr/local/share/dnscrypt-proxy/dnscrypt-resolvers.csv]
Tue Aug  1 09:18:06 2017 [ERROR] Consult https://dnscrypt.org for more information about dnscrypt-proxy.
dirname: missing operand
Try 'dirname --help' for more information.
The path to resolvers.csv on dnscrypt-loader script
differs from dnscrypt-proxy setup
Please change dnscrypt-loader 'cCSVBaseDir' and 'cSIGBaseDir' parameters to
cCSVBaseDir='/'
cSIGBaseDir='/'
Edit script at /usr/local/sbin/dnscrypt-loader
Hope can help me , Thank
# DNSCrypt-proxy 1.95

Hi, thanks for trying to use the script. The error message you posted was issued by dnscrypt-proxy and not by dnscrypt-loader, this may have confused you. Please check the installation of dnscrypt-proxy. If you would like to use dnscrypt-loader install version 1.6 of dnscrypt-proxy. Take a look here: https://github.com/GortCodex/DNSCrypt-Loader/pull/14

Hi ,
I think you should statement your version not yet support  dnscrypt-proxy new version . IF you want to use DNSCrypt Loader please use version 1.6 dnscrypt-proxy.
Because people not to know what happened
Thank !

Hi, you're right. I am updating the manual and putting a warning about using the versions there.


Strategies continue to be called after a previous one fails

I noticed that even if a strategy fails auth, the remaining strategies are still evaluated. They are still called even though https://github.com/continuationlabs/nuisance/blob/master/lib/index.js#L33 has been hit.
Is this the desired behaviour or is the behaviour to attempt the strategies in series and then exit early if one fails?
This is the case due to Insync.each being used. Insync.series would execute them in series and fail early if one failed.

I'd take a PR for this. The docs should probably clarify the way these are checked.

@cjihrig Thanks for addressing this so quickly. Apologies for not getting to submitting the PR before you got to tackling it.

No problem. Glad it's taken care of.


Provide helper for location values

The CDA SDK has a helper for these: http://cocoadocs.org/docsets/ContentfulDeliveryAPI/1.7.4/Classes/CDAEntry.html#//api/name/CLLocationCoordinate2DFromFieldWithIdentifier:
Currently needs to be done manually if using persistence:
id value = …; // The property value from Core Data
CLLocationCoordinate2D location = { 0.0, 0.0 };
 [value getBytes:&location length:sizeof(location)];

Closing as project is now deprecated


Document overall front end site structure

Overview
Document front end file structure
Action Items

[ ] Document front end file structure including directories and relationships between files

Resources/Instructions
Civic Tech Index Site Architecture documentation can be updated here

Overview section added to Site Architecture


Update scalac-scoverage-runtime to 1.4.8

Updates org.scoverage:scalac-scoverage-runtime from 1.4.7 to 1.4.8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "scalac-scoverage-runtime" } ]

labels: library-update, semver-patch

Codecov Report

Merging #34 (647db38) into main (d27d286) will decrease coverage by 48.38%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #34       +/-   ##
===========================================
- Coverage   83.87%   35.48%   -48.39%
===========================================
  Files           2        2
  Lines          31       31
===========================================
- Hits           26       11       -15
- Misses          5       20       +15

Impacted Files
Coverage Δ

.../de/tobiasroeser/mill/vcs/version/VcsVersion.scala
0.00% <0.00%> (-83.34%)
:arrow_down:

Continue to review full report at Codecov.

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


fix: ios unsupported platform message

name: Bug fix
about: Fixing a problem with Flutter OTP Autofill.
assignees: MbIXjkee

Checklist

[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Is there an existing issue for this PR?

link issue here

[ ] Have the files been linted and formatted?
[ ] Have the docs been updated to match the changes in the PR?
[ ] Have the tests been updated to match the changes in the PR?
[ ] Have you run the tests locally to confirm they pass?

Changes
What is the current behavior, and the steps to reproduce the issue?
What is the expected behavior?
How does this PR fix the problem?

Codecov Report
Base: 100.00% // Head: 96.34% // Decreases project coverage by -3.65% :warning:

Coverage data is based on head (dd52f23) compared to base (f69c382).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##              main      #31      +/-   ##
===========================================
- Coverage   100.00%   96.34%   -3.66%
===========================================
  Files            3        4       +1
  Lines           79       82       +3
===========================================
  Hits            79       79
- Misses           0        3       +3

Impacted Files
Coverage Δ

lib/src/base/exceptions.dart
0.00% <0.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Multiprocess dispatcher

to: @javuto
cc: @ryandeivert
cc: @airbnb/binaryalert-maintainers
size: small
Background
#112 generalized the dispatcher, but did so by alternating between the different queues and polling from each. The AWS documentation for SQS Long Polling recommends instead to have different threads for each queue being polled. This way, the dispatcher is not blocked if one of its queues is empty.
Changes

Use one Process for each queue that the dispatcher is polling
Fix a small bug in the downloader introduced by #112 and update the downloader README
Instead of invoking the dispatcher every minute, invoke every 5 minutes and use the maximum long poll timeout (20 seconds)
Remove custom metrics from the dispatcher. They are not in the dashboard and have never proved useful for troubleshooting. Built-in metrics for Lambda and SQS have proven sufficient.

Testing

./manage.py configure - enable downloader
./manage.py deploy
./manage.py cb_copy_all - enqueue thousands of fake events to SQS
./manage.py analyze_all
./manage.py configure - remove downloader
./manage.py deploy - ensure the dispatcher still works with only a single queue

The dispatcher logs show that it is interleaving events from both the analyzer and downloader queues

Coverage decreased (-0.06%) to 93.009% when pulling 28e4cdc8491bbfd5cc21609c07f5784ec07faf59 on multiprocess-dispatcher into 733675d13bb6386c135e992a0e2cfbcb1f2421c6 on master.

nice work!! 😄


Added program on maximum product of subarray

Different Optimized solutions to find maximum product of a subarray

This repository is excluded from hacktoberfest if want to contribute you can contribute in https://github.com/Mridul-1-Sharma/data_structures_algos


Change social mobility application

change social mobility pdf/web application copy
change social mobility financial section
change trade application pdf/web copy

 [QAE17IMP] As a user I want to see updated questions in the Promoting Opportunity award, so that assessors get more relevant information


Boot2Docker URLs should allow file:/// URI syntax

docker-machine create -d vmwarefusion --vmwarefusion-cpu-count "2" --vmwarefusion-memory-size "2048" --vmwarefusion-boot2docker-url "file:///Users/huslage/Downloads/boo2docker-vmware.iso" localdev  does not work as I would expect:
Downloading boot2docker-vmware.iso from file:///Users/huslage/Downloads/boo2docker-vmware.iso...
Error creating machine: open /Users/huslage/Downloads/boo2docker-vmware.iso: no such file or directory
You will want to check the provider to make sure the machine and associated resources were properly removed.
➜  ~  ls /Users/huslage/Downloads/boot2docker-vmware.iso
/Users/huslage/Downloads/boot2docker-vmware.iso

It should work fine, so this seems to be bug to me.

This should work.  I've used it.  Can you try without the quotes?  That might be causing an issue.

@huslage this is working for me with the 0.4.0-rc2.  Can you try again with the latest RC2?

Looks ok now.
On Thu, Aug 6, 2015 at 9:15 PM, Evan Hazlett<EMAIL_ADDRESS>wrote:

@huslage https://github.com/huslage this is working for me with the
0.4.0-rc2. Can you try again with the latest RC2?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/issues/1638#issuecomment-128554285.

--
Aaron Huslage
Solution Architect - Docker, Inc.
+1-919-600-1712


please support Aloha proxy

hi @Snawoot, Aloha browser provides free unlimited proxies

any updates?

hi! nope, no updates

will resort to this if opera-proxy or hola-proxy will get completely banned; for now I have no capacity to reverse and support this one as well.

that's a sad news, @Snawoot
opera and hola often ban users very frequently, but aloha never.

I'll look into that at some point anyway, but no promises. I think they're not getting banned for now just because they're not much popular.


feat: add entity history

Codecov Report

Merging #259 (872c645) into main (7476f89) will increase coverage by 0.19%.
The diff coverage is 51.72%.

@@            Coverage Diff             @@
##             main     #259      +/-   ##
==========================================
+ Coverage   14.55%   14.75%   +0.19%
==========================================
  Files         112      113       +1
  Lines       14412    14420       +8
==========================================
+ Hits         2098     2128      +30
+ Misses      12148    12126      -22
  Partials      166      166

Impacted Files
Coverage Δ

pkg/service/rawdata.go
0.00% <0.00%> (ø)

pkg/service/ts.go
0.00% <0.00%> (ø)

pkg/service/entity_history.go
83.33% <83.33%> (ø)

Continue to review full report at Codecov.

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


Upgrade Byte Buddy 1.14.15 -> 1.14.16

This PR contains the following updates:

Package
Type
Update
Change

Byte Buddy
compile
patch
1.14.15 -> 1.14.16

Release Notes

raphw/byte-buddy (Byte Buddy)
v1.14.16

Update ASM and introduce support for Java 23.

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade Byte Buddy 1.14.15 -> 1.14.16

See:
- https://github.com/raphw/byte-buddy/releases/tag/byte-buddy-1.14.16
- https://github.com/raphw/byte-buddy/compare/byte-buddy-1.14.15...byte-buddy-1.14.16


DataDog agent builder update: Handle multiple files in validation script

What does this PR do?
Fix gitlab test: Handle multiple files in validation script

Merging for RC3


add features and responsive

Thank you for your pull request. Please provide a description above and review
the requirements below.
Bug fixes and new features should include tests.
-->
Checklist

[ ] only relevant code is changed (make a diff before you submit the PR)
[ ] run tests npm run test
[ ] tests are included
[ ] commit message and code follows the Developer's Certification of Origin

Checklist (for documentation change)

[ ] only relevant documentation part is changed (make a diff before you submit the PR)
[ ] motivation/reason is provided
[ ] commit message and code follows the Developer's Certification of Origin

Before: -

After: -

make responsive


adding linter

Signed-off-by: Upkar Lidder<EMAIL_ADDRESS>Describe at a high level the solution you're providing
Adding linter for md files in the repo

@upkarlidder check out the Docker linter failure


Provide urn for every ISO/IEC document according to RFC 5141

We want to provide RFC 5141 URN information per ISO and IEC documents: https://tools.ietf.org/html/rfc5141
The standard-id would be something like:
      urn:iso:std:iso:9999:-1:ed-1:v1-amd1.v1:en,fr:amd:2:v2:en
      (isoversion scheme)
      refers to the corrected version of Amendment 2, in English, which
      amends the document comprising the 1st version of edition 1 of ISO
      9999-1 incorporating the 1st version of Amendment 1, in English/
      French (bilingual document)

For examples, see https://tools.ietf.org/html/rfc5141#section-2.4.2
Related to https://github.com/relaton/relaton-iec/issues/22

@ronaldtse We have the to_all_parts function which removes a part number from a document identifier and adds "(all parts)" string to it. How should we handle the URN in the all-parts functionality?
I've discussed it with Nick. He suggests just remove the part number without adding "all parts" back into the URN.

@andrew2net this case is specified in RFC 5141:
   NSS           = std-nss

      All URNs conforming to this specification begin the NSS with the
      prefix "std:" to denote the restriction to documents developed by
      the ISO standards development procedures as defined in the ISO/IEC
      Directives, Part 1 [ISODIR-1] and the ISO Supplement [ISODIR-S].
      Prefixes that identify ISO objects of other kinds may be defined
      in future revisions of this specification.

      std-nss       = "std:" docidentifier *supplement *docelement
                      [addition]

      The prefix "std:" distinguishes an <std-nss>.  An <std-nss>
      identifies the ISO document that is designated by the
      <docidentifier>, as extended or modified by any identified
      <supplement>.  (An <std-nss> that identifies all parts of a
      multipart ISO document is a special case as described under the

Goodwin & Apel               Informational                      [Page 4]

RFC 5141                     ISO URN Schema                   March 2008

      element <partnumber>.)  If the <std-nss> contains an <addition>
      element, the NSS identifies a resource extracted from the ISO
      document or otherwise associated with it (see below).

Notice that the ISO URN Schema differs from the IEC URN Schema. I will provide details of the IEC URN schema in a separate ticket. This ticket should only be for ISO.