text:
Add APIs for redacting ICS contents

Add an API that can scrub an ICS file to remove sensitive fields, leaving just the data needed for debugging. This allows specifying a set of components, or use a default, as well as the maximum number of total lines in the output.

Codecov Report

Merging #163 (be8e1dd) into main (03f5d24) will increase coverage by 0.03%.
The diff coverage is 100.00%.

:exclamation: Current head be8e1dd differs from pull request most recent head bf90270. Consider uploading reports for the commit bf90270 to get more accurate results

@@            Coverage Diff             @@
##             main     #163      +/-   ##
==========================================
+ Coverage   96.74%   96.78%   +0.03%
==========================================
  Files          43       44       +1
  Lines        2552     2578      +26
==========================================
+ Hits         2469     2495      +26
  Misses         83       83

Impacted Files
Coverage Δ

ical/__init__.py
100.00% <ø> (ø)

ical/diagnostics.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: allenporter codecov-commenter

repo: allenporter/ical


text:
tzif code cleanup and API separation

Move the public interfaces to a separate file, and make the tzif file format code an implementation detail.
Issue #63

Codecov Report

Merging #84 (b729d36) into main (936df4b) will increase coverage by 0.00%.
The diff coverage is 98.18%.

@@           Coverage Diff           @@
##             main      #84   +/-   ##
=======================================
  Coverage   96.98%   96.99%
=======================================
  Files          17       19    +2
  Lines        1559     1562    +3
=======================================
+ Hits         1512     1515    +3
  Misses         47       47

Impacted Files
Coverage Δ

ical/tzif/tzif.py
95.37% <96.96%> (-1.28%)
:arrow_down:

ical/tzif/model.py
100.00% <100.00%> (ø)

ical/tzif/timezoneinfo.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
Trigger - once per bar close

Hi there.
Recently, there was a layout change in the Trigger section of Trading View's alarm settings. So, they responded to that issue by updating quickly. I encountered a problem while using the new updated version.
In TradingView, the default value of Trigger is set to only once. I am using an alarm program by modifying the config.yml file to use this once per bar close.
However, this part is done so quickly and without delay that if you set 100 alarms, about 20 do not change to once per bar close, but the alarm is set only once. Additionally, if the trigger part does not change, there is an error in that the message part below it cannot be modified.
I assume this error is because the trigger is set too quickly, but there may be other causes. thank you :)

Hi there - yes, looks like there needed to be a delay in there.
just made a quick patch release ...try updating
From your tradingview-alerts-home directory, run the following:
npm install @alleyway/add-tradingview-alerts-tool@2.6.6

Hi there - yes, looks like there needed to be a delay in there.
just made a quick patch release ...try updating
From your tradingview-alerts-home directory, run the following:
npm install @alleyway/add-tradingview-alerts-tool@2.6.6

hi there.
Thx for quick update. I followed your advice and ran npm install @alleyway/add-tradingview-alerts-tool@2.6.6 and ran the program, but the symptoms are still the same.
npx @alleyway/create-tradingview-alerts-home@latest, which is not an update method but a completely new installation method.
Even if I install a new file with this and run it from that folder, the problem is not resolved and the symptoms are the same. What should I do?

hi there.
Thx for quick update. I followed your advice and ran npm install @alleyway/add-tradingview-alerts-tool@2.6.6 and ran the program, but the symptoms are still the same.
npx @alleyway/create-tradingview-alerts-home@latest, which is not an update method but a completely new installation method.
Even if I install a new file with this and run it from that folder, the problem is not resolved and the symptoms are the same. What should I do?

I am also experiencing this issue. I don't believe it is an issue with timing but rather recognition of the new formatting. The error message I get in my terminal is:
ERROR  No fire rate 'option' available, but one was specified in alert configuration: Once Per Bar Close

fixed in 3.0.1

source: gharchive/issue

authors: jamidusu mlake nathanccmiller

repo: alleyway/add-tradingview-alerts-tool

license: MIT


text:
🛑 Remod Squad is down

In a9bd8bd, Remod Squad (https://remodsquad.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Remod Squad is back up in 56c7ee7 after 11 minutes.

repo: alliancewebteam/uptime


text:
Asynchronous grab, invalid access with time.sleep()

Hi, I'm running asynchronous grab using the software trigger following the Python API manual. Below is the code that I ran:
# Software trigger for continuous image acquisition

import time
from vmbpy import *

def handler(cam: Camera, stream: Stream, frame: Frame):
    print('Frame acquired: {}'.format(frame), flush=True)
    cam.queue_frame(frame)

def main():
    with VmbSystem.get_instance() as vmb:
        cam = vmb.get_all_cameras()[0]

        with cam:
            cam.TriggerSource.set('Software')
            cam.TriggerSelector.set('FrameStart')
            cam.TriggerMode.set('On')
            cam.AcquisitionMode.set('Continuous')

            try:
                cam.start_streaming(handler)
                time.sleep(1)
                cam.TriggerSoftware.run()
                time.sleep(1)

            finally:
                cam.stop_streaming()

if __name__ == '__main__':
    main()

And I get the following error message:
Traceback (most recent call last):

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\feature.py:403 in run
    call_vmb_c('VmbFeatureCommandRun', self._handle, self._info.name)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\util\tracer.py:139 in wrapper
    return func(*args, **kwargs)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\c_binding\vmb_c.py:892 in call_vmb_c
    getattr(_lib_instance, func_name)(*args)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\c_binding\vmb_c.py:811 in _eval_vmberror
    raise VmbCError(result)

VmbCError: VmbCError(<VmbError.InvalidAccess: -6>)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\stream.py:161 in exit
    self.context.cam.get_feature_by_name('AcquisitionStop').run()

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\util\tracer.py:139 in wrapper
    return func(*args, **kwargs)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\feature.py:414 in run
    raise exc from e

VmbFeatureError: Invalid access while calling 'run()' of Feature 'AcquisitionStop'. Read access: not allowed. Write access: allowed.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\spyder_kernels\py3compat.py:356 in compat_exec
    exec(code, globals, locals)

  File c:\users\fenglab\desktop\shuang\python\vimba_test.py:64
    cam.stop_streaming()

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\util\context_decorator.py:103 in wrapper
    return func(*args, **kwargs)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\util\tracer.py:139 in wrapper
    return func(*args, **kwargs)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\camera.py:406 in stop_streaming
    self.__streams[0].stop_streaming()

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\util\tracer.py:139 in wrapper
    return func(*args, **kwargs)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\util\context_decorator.py:103 in wrapper
    return func(*args, **kwargs)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\stream.py:497 in stop_streaming
    self.__capture_fsm.leave_capturing_mode()

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\stream.py:258 in leave_capturing_mode
    self.go_to_state(None)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\stream.py:241 in go_to_state
    raise exc.pop()

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\stream.py:232 in go_to_state
    self.__states.pop().exit()  # type: ignore

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\util\tracer.py:139 in wrapper
    return func(*args, **kwargs)

  File ~\anaconda3\envs\Shuang_env\Lib\site-packages\vmbpy\stream.py:165 in exit
    raise VmbCError(str(e))

VmbCError: VmbCError("Invalid access while calling 'run()' of Feature 'AcquisitionStop'. Read access: not allowed. Write access: allowed. ")

However if I comment out the time.sleep(1) before and after cam.TriggerSoftware.run():
try:
    cam.start_streaming(handler)
    # time.sleep(1)
    cam.TriggerSoftware.run()
    # time.sleep(1)

finally:
    cam.stop_streaming()

The code ran without error, and it printed out the frame info:
Frame acquired: Frame(id=1, status=FrameStatus.Complete, buffer=0x2594ad7d020)

I don't understand what's going on, and I need the 'time.sleep()' command to set up how often I take an image. Could someone help me with this? Thanks!

Hi, what camera, Version of VimbaX and OS are you using? It would also be helpful if you could save a settings file (that can be done through the VimbaX Viewer) and attach it here.

Hi, for this topic, please open a support ticket through the website and reference this issue, also include your camera serial number and firmware version there.
https://www.alliedvision.com/en/about-us/contact-us/technical-support-repair-/-rma/
This topic is related to the camera behaviour and not the API.

authors: Teresa-AlliedVision sgwu

repo: alliedvision/VmbPy


text:
Token '25' doesn't match specifier '%d'

Running...
$ goaccess -p /etc/goaccess/goaccess.conf -f peak.log -a > peak.html
I get the following error
Parsed 1 linesproducing the following errors:

Token '25' doesn't match specifier '%d'

Format Errors - Verify your log/date/time format
Which is weird, because "25" is a valid value of %d (day of month).
/etc/goaccess/goaccess.conf contains:

time-format %H:%M:%S
date-format %d/%b/%Y
log-format %h %l %u %^[%d/%b/%Y%^:%H%^:%M%^:%S %z%^] \"%r\" %>s %b \"%Referer}i\" \"%{User-Agent}i\" **%T/%D**

Version is 1.3 , installed on Debian stretch from the official repo.
Could goaccess be stumbling over the non-standard log-format?

Please post a few sample lines from your access.log. Thanks.

Sorry for the delay :-( Are 20 lines enough?

xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /panorama/polizei-sucht-_huehnerkiller_-30880912.html?_XML=AMP HTTP/1.1" 200 15618 "https://www.swp.de/blaulicht/crailsheim/frauenleiche-in-wohnung-gefunden-lebensgefaehrte-verhaftet-30881568.html?_XML=AMP" "Mozilla/5.0 (Linux; Android 9; SM-G950F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.112 Mobile Safari/537.36" **0/169472**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/4/2/8/0/5/7/8/3/tok_762e99b98610658d20d4ff875a109b62/w370_h518_x393_y174_dadc02b5df9cea4e.jpeg HTTP/1.1" 304 - "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/584**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/3/2/8/7/0/3/4/0/tok_25c8b878c2e9ea92f396660ebcc84843/w800_h450_x500_y750_gem__se-b78bdc17cd4ad07f.jpeg HTTP/1.1" 200 33690 "https://www.swp.de/suedwesten/staedte/bietigheim-bissingen/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/811**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/4/2/8/0/2/7/3/4/tok_006c7419910d418e96f701b6d4f97a19/w400_h225_x558_y259_cecca29521ee10ee.jpeg HTTP/1.1" 304 - "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/561**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /includes/ajax_treenodeid_controller_16257247.php?treenode_id=20295&count=3 HTTP/1.1" 200 5741 "https://www.swp.de/sport/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0" **0/4296**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/1/6/3/7/2/8/2/1/tok_e0f0149eba5bcd261ba8df2392a08020/w575_h323_x750_y422_3f2a24a1eb313aac.jpeg HTTP/1.1" 304 - "-" "Googlebot-Image/1.0" **0/773**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/3/1/9/4/7/9/3/6/tok_e9e7ecd258792924d309a24e5c1d93b8/w800_h450_x750_y382_boe_ganerbenfest8_mk-6a6be2c4bd45bea4.jpeg HTTP/1.1" 200 213062 "https://www.swp.de/suedwesten/staedte/bietigheim-bissingen/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/1331**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/4/2/7/9/5/6/4/4/tok_172bddb378150894a6d7d3808c9ab3fb/w400_h225_x501_y348_f74858cda0f36f56.jpeg HTTP/1.1" 200 14751 "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/627**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/4/2/7/9/9/9/6/0/tok_57a295b2e0280871756e149ca4711266/w400_h225_x292_y150_1243d243fd1a5785.jpeg HTTP/1.1" 304 - "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/516**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/4/2/7/5/1/4/4/0/tok_630bb1d612d16f4fd703107713fc02b5/w400_h225_x323_y247_c30211efd4836a4e.jpeg HTTP/1.1" 304 - "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/499**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/4/2/6/9/6/6/0/6/tok_0af368fc950f435043ec412d718c4fed/w400_h225_x929_y246_eea9d2dcc122ec67.jpeg HTTP/1.1" 304 - "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/537**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /imgs/07/4/2/8/0/4/9/4/0/tok_a84f716343818e18f1f7d6716575681b/w400_h225_x400_y255_c8be00720140a454.jpeg HTTP/1.1" 304 - "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/478**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:53 +0200] "GET /imgs/07/3/1/8/2/3/2/1/6/tok_a8f8997e8d371b237fa1523d74042482/w800_h450_x750_y369_lb_roncalli3_mk-78314252c84ef28f.jpeg HTTP/1.1" 200 116681 "https://www.swp.de/suedwesten/staedte/bietigheim-bissingen/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/1113**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:53 +0200] "GET /imgs/07/4/2/8/0/4/7/9/6/tok_ec19dd612a8e5e4a80be403281ee3a75/w400_h225_x750_y543_81f004dbc6ee7d3b.jpeg HTTP/1.1" 304 - "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/513**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:52 +0200] "GET /suedwesten/staedte/ulm/ HTTP/1.1" 200 26042 "https://www.google.com/" "Mozilla/5.0 (Linux; Android 7.0; F3111) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.136 Mobile Safari/537.36" **0/82136**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:53 +0200] "GET /imgs/07/4/2/7/5/6/5/2/6/tok_de9459c7f2a382a515a7cee03da6c449/w400_h225_x635_y336_cde840ec784f95b0.jpeg HTTP/1.1" 304 - "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/417**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:53 +0200] "GET /js/main.min.js?ts=20190415173000 HTTP/1.1" 200 83030 "https://www.swp.de/suedwesten/staedte/bietigheim-bissingen/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/24676**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:53 +0200] "GET /imgs/07/4/2/8/0/9/0/4/7/tok_bbb29eee4234057e7d0cd9e2a456475a/w400_h225_x400_y220_cc8e75fc0ee07fe8.jpeg HTTP/1.1" 304 - "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/632**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:53 +0200] "GET /imgs/07/4/2/8/1/1/5/1/1/tok_33634983b9f5dc907a6a6700ebd07317/w370_h518_x400_y276_0a1ea7061f5fb6e5.jpeg HTTP/1.1" 200 30028 "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/692**
xxx.xxx.xxx.xxx - - [08/May/2019:11:37:53 +0200] "GET /imgs/07/4/2/8/0/4/9/5/0/tok_c4cae22a7b56ad0344895036855f36e8/w370_h518_x400_y161_a0d1235b049df6e2.jpeg HTTP/1.1" 200 28982 "https://www.swp.de/suedwesten/staedte/heidenheim/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" **0/739**

This should do it:
goaccess access.log --log-format='~h{, } %^[%d:%t %^] "%r" %s %b "%R" "%u" %^/%D**' --date-format=%d/%b/%Y --time-format=%T

That seems to be working until I reach a count of roundabout 1,6 Million lines.
I tried multiple times. the exact numbers changes a little, but the error is always this one:

$ goaccess access.log --log-format='~h{, } %^[%d:%t %^] "%r" %s %b "%R" "%u" %^/%D**' --date-format=%d/%b/%Y --time-format=%T -f peak.log -o peak.html
Parsing... [1,611,867] [30,997/s]
GoAccess - version 1.3 - Nov 25 2018 19:47:35
Config file: No config file used

Fatal error has occurred
Error occurred at: src/parser.c - read_log - 2728
Unable to open the specified log file. No such file or directory

My logfile is 563M big, is that a problem?

Sounds like a permissions issue on your file. Can you try to isolate this by creating a new file and reading that file with goaccess? e.g.,
# cat access.log > /home/user/test.log
# goaccess test.log

Ah! Sorry, must have missed the notification :-/
The file was on a Windows-Partition and thus mode 777.  Copying to my /home (mode 740) did not change  anything unfortunately.
I get the exact same error.

I'd try running goaccess as root and see how it goes. Else, please feel free to run it through strace and attach the output here. Thanks.

PEBCAS
Ok, NOW I feel really, really stupid m(
I kept the copy-pasted "access.log" from the command you gave me and ADDED a "-f mylogfile.log":
goaccess access.log --log-format='~h{, } %^[%d:%t %^] "%r" %s %b "%R" "%u" %^/%D**' --date-format=%d/%b/%Y --time-format=%T -f peak.log -o peak.html
The command then choked on the extra logfile.
How did I not see that? Head -> Desk -> repeat...
This did work as expected:
goaccess --log-format='~h{, } %^[%d:%t %^] "%r" %s %b "%R" "%u" %^/%D**' --date-format=%d/%b/%Y --time-format=%T -f peak.log -o peak.html
Sorry for that.
I just  tried what happens if I do:
goaccess web01.log --log-format='~h{, } %^[%d:%t %^] "%r" %s %b "%R" "%u" %^/%D**' --date-format=%d/%b/%Y --time-format=%T -f web02.log -f web03.log -o test.html
All files existed this time and it worked. Great! That saves me merging the files prior to the analysis :-)
Thanks for helping me out!

No worries, it happens :) glad it is working now!

authors: allinurl markgraf

repo: allinurl/goaccess

license: mit

license_source: bigquery


text:
Caddy - GoAccess issues

Dear team,
I have tried to implement GoAccess to work with Caddy access logs
I have proceeded by running an apache2 docker container , and inside it running goaccess ( apt-get install goaccess )

goaccess --version
GoAccess - 1.4.
For more details visit: http://goaccess.io
Copyright (C) 2009-2020 by Gerardo Orellana
Build configure arguments:
--enable-utf8
--enable-geoip=mmdb
--with-openssl

I have followed the setup and running this command : goaccess /var/logs/caddy/site.fr-access.log -o /usr/local/apache2/htdocs/report.html --real-time-html --log-format=CADDY and I'm getting an error like this : Error occurred at: src/parser.c - parse_log - 2777 No time format was found on your conf file.
also tried this command regarding this issue : https://github.com/allinurl/goaccess/issues/1571#issuecomment-543186858
LANG="en_US.UTF-8" bash -c 'goaccess /var/logs/caddy/site-access.log -o /usr/local/apache2/htdocs/report.html --real-time-html --log-format=CADDY' but nothing special happened
my caddy config is like this :
site.fr {         handle {                 reverse_proxy site-hostname:80         }   log {     output file /var/log/caddy/site.fr-access.log     format json   } import common }
Please, if anyone have an idea how to fix this , I will be appreaciate it
thank you

JSON support was added in 1.4.4. Please use this docker image or the official deb repo.

That's correct.

Closing this. Feel free to reopen it as needed.

I have an issue when mapping Caddy reverse proxy to the container that GoAccess run on
my Caddy config is :
goaccess.innoyadev.fr {
        handle {
                reverse_proxy p-GoAccess-Apache:7890
                                basicauth {
        InnoyaDev JDJhJDE0JERkQ3hCbWhmemlETUdqNFg4QndhdHVIWVhXenRiRHV1enZXclBPS1VwM3o0MUkyR0RRZUFX
       }
        }
  log {
    output file /var/log/caddy/goaccess.innoyadev.fr-access.log
    format json
  }
}

running GoAccess on httpd docker container with this command
goaccess /var/logs/caddy/*-access.log -o /usr/local/apache2/htdocs/report.html --real-time-html --log-format=CADDY --daemonize
GoAccess running correctly inside the container :
root@p-GoAccess-Apache:/usr/local/apache2# lsof -i -P -n COMMAND  PID USER   FD   TYPE    DEVICE SIZE/OFF NODE NAME httpd      1 root    3u  IPv4 555951236      0t0  TCP *:80 (LISTEN) goaccess  99 root    8u  IPv4 555949745      0t0  TCP *:7890 (LISTEN)
when trying accessing goaccess.innoyadev.fr , I get 400 request

@allinurl FYI

Does this help? It seems to work for this user.

authors: MehdiKammakh allinurl


text:
Adding FreeAgent to the list of Lookbook users

Adding FreeAgent to the list of Lookbook users

Awesome - thank you :-)

authors: allmarkedup dmorgan-fa

repo: allmarkedup/lookbook


text:
data-am-sticky的bug

在firefox 36和ie 11下，当这样使用时，在两边会有莫名奇妙的空隙，但是当去掉data-am-sticky="{top: 50}"后，两边的空隙就会去掉，在chrome 40下正常。

有演示页面和截图吗？不然不太好理解你说的问题。

@Minwe  chrome下正常

ie和firefox下不正常

去掉data-am-sticky后都是正常的

是整栏固定还是就带头像的这一块固定？
Sticky 生效以后会添加 position: fixed 样式，会去计算 sticky 元素的宽度然后设置样式，可能不同浏览器在计算上会有问题。我用官网的边栏在 Firefox 上测试了一下没有发现问题，所以你可能需要给出实际的演示代码，具体看一下。你可以在 JSBin 上做一个演示的页面然后把地址贴出来。

http://jsbin.com/nufidofiqe/1/edit?html,output
这个地址，你用ie和firefox看就会有问题

authors: Minwe MiracleSnow

repo: allmobilize/amazeui


text:
[Suggestion]: Fixed header on mobile devices

Mobile devices screen is not that big to contain a lot of unnecessary data all the time you are surfing the website, like the website title.
in mobile view we have the fixed header as 2 x 50px containers.
What if we only made the 2nd container fixed and be sticky at top when scrolling down and leave the website title container at the top without fixing at the top of the screen.
I will try to provide some image to describe what I wrote here.

Hello,
I like the suggestion. We are implementing something similar for AdminLTE v3 wihtout compromising the title. Since we are currently not adding new features for V2. Will consider this for V3.
Thanks!

Yeah, I was talking about the upcoming v3,
Could we do anything to help you in it ?


text:
Logout User

There is now a new endpoint which redirects to Keycloak to log out user:
GET /api/logout
Optional param: redirect=, if not set then referrer will be used to redirect to after logout.
Fixes https://github.com/almighty/almighty-core/issues/987

[test]

[test]

Implementation looks good to me, though I couldn't test it locally ( since nothing keycloak-ish is working for me :(  )
@alexeykazakov ,
Just one thought on this is that -
This is a Keycloak logout but not really a platform logout , right?
I'm guessing that our jwt middleware would still be considering the access tokens as valid , and allowing folks to do everything non-keycloak-ish?
( this is absolutely a hack )
For platform-logout,
I was wondering if we should maintain a list of keycloak-logged-out tokens in-memory for  minutes to disallow them from being used?

@sbose78 right. it just kills the Keycloak and developers.redhat.com sessions with the browser. It doesn't revoke any tokens.
If we want to revoke tokens, it's a separate big story.

Yeah @aslakknutsen we have an issue for that. I even tried to move it once but the challenge is that we can't actually support both /login and /auth resources/controllers at the same time for compatibility. Goa limitation :( So we have to switch and drop supporting the old /login endpoint.

@hectorj2f I addressed all your comments.

repo: almighty/almighty-core


text:
Restructure tests to use suites

Remove dependency on global DB variable

Codecov Report

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

@@            Coverage Diff             @@
##           master     #977      +/-   ##
==========================================
+ Coverage   70.17%   70.25%   +0.08%
==========================================
  Files          91       91
  Lines        7004     7004
==========================================
+ Hits         4915     4921       +6
+ Misses       1636     1634       -2
+ Partials      453      449       -4

Impacted Files
Coverage Δ

controller/login.go
51.51% <0%> (-4.05%)
:x:

login/service.go
52.47% <0%> (-1.66%)
:x:

remoteworkitem/scheduler.go
63.41% <0%> (+9.75%)
:white_check_mark:

models/transaction.go
70% <0%> (+20%)
:white_check_mark:

remoteworkitem/github.go
100% <0%> (+22.85%)
:white_check_mark:

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 9313a3e...4b28555. Read the comment docs.

@aslakknutsen this merge broke master: https://ci.centos.org/view/Devtools/job/devtools-almighty-core-build-master/297/changes

@kwk no, master has been broken for weeks 😊

Oh yeah.. It's the famous version conflict ghost in our tests :)

authors: alexeykazakov aslakknutsen codecov-io kwk


text:
Update sbt-scoverage to 2.0.12

About this PR
📦 Updates org.scoverage:sbt-scoverage from 2.0.11 to 2.0.12
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
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!

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scoverage", artifactId = "sbt-scoverage" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

replaced by https://github.com/alonsodomin/cron4s/pull/594

authors: mbaechler scala-steward


text:
Implement a confirmation dialog or "Dead tossup" button to prevent accidentally pressing "Next" twice

Since the throw-out/replacement flow is flawed (#212 #245 etc.), add a barrier to preemptively prevent situations that require manually editing prior game state.

I'm leaning towards marking this as won't fix. For low-scoring games this becomes a hindrance, and I'm not aware of having to throw out questions because tossups were read in the wrong order (though I could be mistaken). The button could be disabled for a short amount of time (250 ms maybe), but that seems like overkill.

I think changing the text of the button to "Next (dead tossup)" or something would be a simple improvement.

Should it show the label if the tossup has negs but is still dead, or if there's only no buzzes?

It's a bit unbalanced if "(dead)" is added to the text. "(dead)" has the issue of being less useful if there were negs in the tossup, since it doesn't prevent this accidental case. Other forms like "(unanswered)" are much bulkier though.

authors: alopezlago hftf

repo: alopezlago/MODAQ


text:
优化：在创建 method 实例时定义元数据

需要新特性解决什么问题？
减少样板代码
你期望的新特性应该如何呈现？
在创建 method 实例时定义元数据，当前写法是类似这样的：
const loginAPI = (username, password) => {
  const methodInstance = alovaInst.Post('/login', {
    username,
    password
  });
  methodInstance.meta = {
    ignoreToken: true
  };
  return methodInstance;
};

希望把meta直接写到config中，类似这样：
const loginAPI = (username, password) => {
  return alovaInst.Post('/login', {
    username,
    password
  },{
    meta:{
      ignoreToken: true
    }
  });
};

它对你有多重要？
可以让我更便于开发

好建议

:tada: This issue has been resolved in version 2.18.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: alovajs/alova


text:
Revise RuleAtomData#compareTo

Eliminates the implicit assumption for two compared RuleAtomDatas to have the same variables set and instead works off the occurring variables of the rule.

Proposed change made obsolete by better solution.

repo: alpha-asp/Alpha


text:
Fix issue with briefs

It seems that we have been unable to run our functional tests recently because they have been looking for DOS3 briefs, but all live briefs on preview are now DOS4.

I haven't updated the step that finds closed briefs to use DOS4 yet, because there are only 6 closed DOS4 briefs on preview, vs 325 closed DOS3 briefs.
I'll add a TODO however, for future reference.


text:
Add size: "large" to homepage search

What
Add's size: "large" to the search input on the new homepage so that it triggers the search component's large mode.
Why
So that we are consistent with how we display the search input across the homepage and the super nav header.
Card
Visual changes
Before

After

@owenatgov looks good, any idea of whether we can meet our stretch of keeping it smaller on desktop?

@mia-allers-gds We're making good time so maybe. It'll involve a change to the gem so we could quite easily do it a bit later. I've got some thoughts about how to do this and will investigate as I get to the end of our snag list.

authors: mia-allers-gds owenatgov

repo: alphagov/frontend


text:
Further cleanup in MQ module.

Use an up-to-date Python runtime for the config Lambda.
Use aws_iam_policy_document for better ahead-of-time checking.
Fix the HTTP error handling in the lambda that uploads the config to RabbitMQ.
Fix a JSON syntax error in the config template which was causing RabbitMQ 3.11 to reject the config.
Use a map for the random_password resources, since we were putting them in a map for the template anyway.
Eliminate the publishing_amazonmq_instance_count parameter.
Remove unused provider declaration.
Remove redundant comments.

Tested: applied in the integration and staging accounts.
https://github.com/alphagov/govuk-infrastructure/issues/1267

Applied everywhere now; dropped the commit with the moved blocks.

repo: alphagov/govuk-aws


text:
Write the proposal for the component to take to the community

What

Background of our research
What we believe navigation should be, could be, should not be
Our definition of navigation levels
What we've decided not to consider
What we want from users

Done When

Working document — Navigation component: initial proposal

authors: domoscargin mia-allers-gds

repo: alphagov/govuk-design-system


text:
Find & fix root cause of 'html-pipeline' issue

First spotted by Tim Blair in April (https://github.com/alphagov/govuk-developer-docs/commit/e9541eb4d01d1fb4b883041ca211613086618641), html-pipeline 2.11.0 causes issues with ASCII/UTF-8 processing:
Error processing resource for index: apis/search/faceted-search.html
"\xE2" from ASCII-8BIT to UTF-8
 govuk-developer-docs/.bundle/gems/commonmarker-0.19.0/lib/commonmarker.rb:26:in `encode'

We pinned html-pipeline to 2.5.0 in https://github.com/alphagov/govuk-developer-docs/pull/1818/commits/6f81229297ab2a3107b317313de8101c1898a7a7, but should investigate the root cause and fix it.

We saw a very similar error here: https://github.com/alphagov/govuk-developer-docs/pull/2575/commits/d95bcbd509b92b0da14af36d3bf49a962f3b5c10 - but with a different stack trace.

repo: alphagov/govuk-developer-docs


text:
Update copy:files to glob “src” not “src/govuk”

This PR widens gulp copy:files to glob ./src/**/* not just the "govuk" directory
Why? Since https://github.com/alphagov/govuk-frontend/pull/2851 was merged we're now running build tasks on files within:
./src/govuk
./src/govuk-prototype-kit

As suggested by @36degrees in https://github.com/alphagov/govuk-frontend/pull/2851#pullrequestreview-1167005193 we could remove some unnecessary file operations:

(I think it'd be neater if the .js and .scss files were handled by the existing copy-files task, but that looks like it's caught up in the fact that config.src is actually src/govuk so happy to revisit that later)

These changes were made possible by:

https://github.com/alphagov/govuk-frontend/pull/2962

@36degrees Does this PR address your code review suggestion?

repo: alphagov/govuk-frontend


text:
Decide on the end user experience with recent security updates

We have recently added a package-lock file to help us get alerts on security issues.
We need to decide whether our users get that file:

what does the experience look like for them?
is there anything we need to change?
is there anything we need to tell our users about?
what does the upgrade process look like?
what about users who don't upgrade?

I think we also should decide whether we want to advise users with existing prototypes should add a package lockfile. Should that be part of this ticket or a separate issue?

@lfdebrux agree, added to this issue

Our Google doc investigating this
In summary:
The only issue we found was that the lock file version changed from 1 to 2 with npm 7. It will still work, regardless of version, but if someone is working with one version of node/npm, and someone else collaborating is working on another, the file will keep changing back and forth, and so appear in git as a changed file, which could be confusing.
We investigated setting it as version 1 for everyone, but discovered a couple of quite serious bugs when trying to do that:

If you set lockfile version to 1 to avoid the lockfileversion issue, npm 8.1.0 which comes with Node 16 has a bug which does not recognise this setting.

If you use npm 8.1.3, this issue is fixed, however npm ls command is broken. It does not recognise any installed packages.

So we are using version 2 instead.
We tested and updated the upgrade instructions

authors: joelanman lfdebrux

repo: alphagov/govuk-prototype-kit


text:
Graphite s3 backups

Enable S3 offsite backups for graphite.
This relies on #5540 and #5541

Rebased.

authors: SamLR surminus

repo: alphagov/govuk-puppet


text:
Don't send empty batches to the Link Checker API

Link Checker API doesn't accept empty batches.

Merge when green

authors: sihugh thomasleese

repo: alphagov/local-links-manager


text:
[WIP - do not merge]Save links to publishing-api on publish

Ticket: https://trello.com/c/Cx3K3y8I/544-publisher-migration-publisher-should-send-links-to-publishing-api-on-publish
Part of: https://trello.com/c/nGta782z/525-epic-migrate-publisher-to-the-new-tagging-infrastructure
Paired on this with @MatMoore.
cc: @tijmenb @mobaig @Davidslv @bishboria

This code assumes there is no need for a separate primary topic and additional topics. This will matter when we do the next step of the migration, i.e. making the frontend get this information from the publishing api. I'm going to do some investigation to see if this is actually the case.

So far, we haven't found anything that depends on the primary_topic. @MatMoore has contacted Mark Hurrel, who may know more about primary_topic's pedigree and intention.
In the meantime I'm happy to merge this PR, since we can always go back and add the primary_topic to the links hash.

authors: MatMoore jackscotti tijmenb

repo: alphagov/publisher


text:
Split elasticsearch/ into parts

The elasticsearch module is a holdover from the times when we supported solr as
well. Now it is a big catch all namespace for a lot of different things.
This PR separates it out into parts (see further comments below).
@tijmenb @rboulton Does the new structure make sense to you? If this is a good step forward, we can rework the namespaces to match, and rebase our snapshot/restore on top of this for https://trello.com/c/YAJY2zIl/359-implement-snapshot-restore-to-backup-elasticsearch-indexes
The aim of this refactor is to add some structure to the elasticsearch/ code and facilitate moving to the elasticsearch gem, since we plan to make a lot of changes to the indexing workflow in the future and the official gem makes a lot of things simpler to implement. (This came up before in https://trello.com/c/PqLodfBo/47-fix-elasticsearch-load-balancing)

The test directories also need to moving if we go ahead with this.

Closing for now, going to take another shot at it this afternoon.

After discussing with @tijmenb yesterday I decided to redo this. We decided that a large part of the former Elasticsearch module should belong to the indexer, and another chunk to the unified search part. This split is something we've started already, but a lot of classes have been left in the root directory/namespace.
Although not strictly necessary to do right now, I'm using the opportunity to

Organise those classes living directly under lib
Rename unified_search -> search in the code.
Group together presenters for search, and workers for the indexer.

I think the split between search/indexer is fairly good as I've tried to avoid moving anything that couples those two areas of the code.
gds0264:rummager matmoore$ grep -rl 'Search::' . | egrep -v '^\./(test|lib\/search)/'
./app.rb
./lib/index.rb
./lib/legacy_search/advanced_search.rb
./lib/legacy_search/advanced_search_query_builder.rb
./lib/searcher.rb
gds0264:rummager matmoore$ grep -rl 'Indexer::' . | egrep -v '^\./(test|lib\/indexer)/'
./bin/bulk_load
./lib/index.rb
./lib/tasks/indices.rake
./lib/tasks/message_queue.rake

What remains of the Elasticsearch module is what I view as the "model" code: SearchServer, IndexGroup, Index, SearchConfig. This is used all over the place at the moment, although it may change significantly when we introduce the elasticsearch gem.
legacy_client can be removed when the elasticsearch gem is introduced.
legacy_search is the old advanced search functionality, which I wanted to separate from the new search namespace.
I moved query_components under search as well, but I'm not renamespacing this as I think nesting them lexically hurts readability and I want to keep it simple. If anyone has differing opinions on this I'm happy to rework it.
In this PR I don't intend to make any API changes or structural changes beyond moving and renaming constants.
I plan to move some tests around after this to reflect the new structure.
@tijmenb @rboulton @mobaig

Really happy with his. Makes a lot of sense and will make it easier for new developers.
The only thing I'm not a 100% on is the Search namespace because the indexing side is called Indexer and it may be harder to grep. Would naming it Searcher be better?

I'm fine with either, or something else. I think both are an improvement on unified search.
I guess the only problem with Searcher is there is there is already a Searcher class, which currently lives outside of that namespace (in contrast to indexer.rb, which just requires stuff).
Maybe we could move this to Searcher::IndexSearcher or something like that? Otherwise it could be a bit confusing as Searcher isn't the thing you use to do the searching.

Yeah, searcher.rb should also go into the new namespace. Searcher::Search would make sense, but Search::Searcher would also be fine :)

Cool, I've moved this to Search::Searcher.

Nicely done.
Some suggestions below for further renaming - the intention here being clarity and succinctness. What do you think?
Search::Searcher => Search::Query (maybe with a renamed instance method e.g. - Search::Query.new(search_params).run)
Search::Queries (module) => Search::QueryHelpers or Search::ElasticsearchHelpers
Search::SearchBuilder => Search::QueryBuilder
Search::SearchPresenter => Search::ResultPresenter
Search::FacetExampleFetcher => Search::FacetExample
Search::SearchParameters => Search::Parameters
Indexer (module) => Index
Indexer::IndexQueue => Index::Queue
Indexer::IndexDocuments => Index::Documents

Thanks, those are good suggestions.
I've implemented the search ones, but left the indexer ones for now, because we still have some classes like "Index" and "IndexGroup" that could cause confusion. They are not part of what I'd consider "indexer" code at the moment since they are involved in other things like rake tasks, and advanced search. I expect we will rework this in the future so it might be good to revisit the naming another time.

:+1: :ship: :rocket:

:+1: massive improvement! :balloon:

:clap:

authors: MatMoore mobaig rboulton tijmenb

repo: alphagov/rummager


text:
Add govuk_environment to specify environment

Add govuk_environment Terraform variable
Feed this variable into the GCP project ID so that it doesn't necessarily need specifying

Closing in favour of a different approach


text:
Overseas passports: all users may need to attend an interview

All users may need to attend an interview
This is an older request that has slipped through the cracks for some countries.
Original request from zendesk:

any applicant type can be invited for interview, not just first time - amend sentence and move it further down in the section.

The 'You may need to attend interview' has been moved to its own paragraph in all
cases as per content designer advice.

Looks good to me.

authors: chrisroos tadast

repo: alphagov/smart-answers


text:
Use next_node blocks in uk-benefits-abroad

We've agreed to consistently use next_node {} to define our next node rules. Having a single way of defining the rules will hopefully make Smart Answers easier to develop and maintain.
This will ultimately allow us to remove the predicate code (define_predicate, on_condition, next_node_if etc).

LGTM :+1:

I've rebased on master and force pushed in preparation for merging.

authors: chrisroos floehopper


text:
Amend earliest application date

Supersedes #2683
Trello card
Trello card

Show notification message to soon to be pensioners who are 4months from receiving State Pension (SP) age can apply to get their State Pension. (i.e. advising them that they don't have to wait till their Sate Pension age before doing this.). #Previously, the notification message was also rendered for those within  4months and 4 days, but the rules have now been changed to only show the notification from 4months.

Factcheck
Preview Link
GOVU.UK
Expected changes

Display notification to only soon to be pensioners who are 4months from receiving State Pension (SP) and not for those within 4months and 4 days.

With a state pension date of 2016-12-17 and birthday of  1951-12-17
Under 4 months and 4 days rule 2016-12-21 is boundary with today's date of 2016-08-17
Under 4 months and 4 days rule 2016-12-17 is boundary with today's date of 2016-08-17

Factcheck (4 months and 4 days)
Preview Link
GOVU.UK
Before

After

Factcheck (4 months) No Changes
Preview Link
GOVU.UK
Before

After

at the moment the tests are failing.. because of a content schema update.. which has been fixed in #2691

@ikennaokpala I would have expected the dates tested in the unit tests to have changed as a result of these changes. As only the test titles have changed, it would appear that they aren't testing anything useful.
I would expect to see tests where the date is 4 months and 4 days in the past and that initially (before the changes) passed, and now fail, And tests for 4 months that always pass (before and after the changes).

@leenagupte Amends have now been made..

@ikennaokpala Thanks for updating the tests. 👍

@ikennaokpala, I guess the links (to gov.uk and heroku) are now wrong because this was two days ago, right? Can you update them so they can be checked today during the release?

@selfthinker thanks for letting me know I have updated the links and dates accordingly..  I will also make myself available post deploy to support in anyway I can

authors: ikennaokpala leenagupte selfthinker


text:
Add integration test for the calculate-employee-redundancy-pay flow

A new spec for the calculate-employee-redundancy-pay flow
Trello
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

Looks good! I think we should remove the all old mintiest integrations test with this PR, so we aren't running both

Yes, quite right - done.

Looks good! I think we should remove the all old mintiest integrations test with this PR, so we aren't running both

Yes, quite right - done.


text:
build on Linux & config for separate vsp/test-rp

These commits make these changes:

make it possible to use this on Linux
update config for stub-idp
add separate configs for test-rp and vsp/passport-stub so they can theoretically both be tested

That could go in another PR :D

repo: alphagov/verify-local-startup


text:
Remove withStatsdTiming

This method has been removed in https://github.com/alphagov/govuk-jenkinslib/pull/69.

Duplicate of #5458.

repo: alphagov/whitehall


text:
Extend schema validation test

This test will fail until https://github.com/alphagov/publishing-api/pull/2491 is merged
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
Follow these steps if you are doing a Rails upgrade.

(pushed to rebase)

authors: ChrisBAshton hannako


text:
Update watch task

Prise en compte à la volée des modifications sur nouveaux fichiers lors d'une tâche 'watch' :
https://stackoverflow.com/a/34346524

Merci !

authors: raphaelgoetter regisauclair

repo: alsacreations/bretzel