text:
OL quits on Verilator error, but they are only warnings

Description
Running the stock spm example with OL 2023.05.19 the flow quits on error:
/foss/designs > flow.tcl -design spm
OpenLane af89aba6b7fd4c629a97fce12c26c0c8d219a947
All rights reserved. (c) 2020-2022 Efabless Corporation and contributors.
Available under the Apache License, version 2.0. See the LICENSE file for more details.

[INFO]: Using configuration in 'spm/config.json'...
[INFO]: PDK Root: /foss/pdks
[INFO]: Process Design Kit: sky130A
[INFO]: Standard Cell Library: sky130_fd_sc_hd
[INFO]: Optimization Standard Cell Library: sky130_fd_sc_hd
[INFO]: Run Directory: /foss/designs/spm/runs/RUN_2023.05.22_15.31.55
[INFO]: Saving runtime environment...
[INFO]: Preparing LEF files for the nom corner...
[INFO]: Preparing LEF files for the min corner...
[INFO]: Preparing LEF files for the max corner...
[INFO]: Running Verilator (log: spm/runs/RUN_2023.05.22_15.31.55/logs/synthesis/verilator.log)...
[ERROR]: 2 errors found by Verilator
[ERROR]: Step 0 (verilator_lint_check) failed with error:
-code 1 -level 0 -errorstack {INNER {invokeStk1 throw_error} CALL run_verilator CALL run_verilator_step CALL {run_non_interactive_mode -design spm}} -errorcode NONE -errorinfo {
    while executing
"throw_error"
    (procedure "run_verilator" line 35)
    invoked from within
"run_verilator"
    (procedure "run_verilator_step" line 3)
    invoked from within
"run_verilator_step"} -errorline 1
[INFO]: Saving current set of views in 'spm/runs/RUN_2023.05.22_15.31.55/results/final'...
[INFO]: Generating final set of reports...
[INFO]: Created manufacturability report at 'spm/runs/RUN_2023.05.22_15.31.55/reports/manufacturability.rpt'.
[INFO]: Created metrics report at 'spm/runs/RUN_2023.05.22_15.31.55/reports/metrics.csv'.
[INFO]: Saving runtime environment...
[ERROR]: Flow failed.

However, when running Verilator on the spm.v, only two warnings are thrown:
/foss/designs > iic-vlint.sh -v spm/src/spm.v
[INFO] Run verilator linting on spm/src/spm.v...
%Warning-DECLFILENAME: spm/src/spm.v:35:8: Filename 'spm' does not match MODULE name: 'TCMP'
   35 | module TCMP(clk, rst, a, s);
      |        ^~~~
                       ... For warning description see https://verilator.org/warn/DECLFILENAME?v=5.009
                       ... Use "/* verilator lint_off DECLFILENAME */" and lint_on around source to disable this message.
%Warning-UNUSEDSIGNAL: spm/src/spm.v:23:20: Signal is not driven, nor used: 'xy'
                                          : ... In instance spm
   23 |     wire[size-1:0] xy;
      |                    ^~
%Error: Exiting due to 2 warning(s)
[DONE] Bye!

@donn Please take a look. Maybe the variable QUIT_ON_VERILATOR_ERRORS should be set to 0 for some time being.
Expected Behavior
OL running spm w/o error.
Environment report
/foss/tools/openlane/2023.05 > python3 ./env.py issue-survey
Kernel: Linux v5.15.49-linuxkit
Distribution: ubuntu 22.04
Python: v3.10.6 (OK)
Critical Alert: No Docker or Docker-compatible container engine was found.
OpenLane Git Version: af89aba6b7fd4c629a97fce12c26c0c8d219a947
pip: INSTALLED
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

af89aba6 2023-05-18T13:37:26+03:00 get_tag.py: Don't encode illegal docker tag when local building (#1803) - Darryl Miles -  (HEAD, tag: 2023.05.19)
2ec3bfdd 2023-05-16T21:06:51+03:00 Do not skip STA when `CLOCK_PORT` is not specified (#1797) - Kareem Farid -  (tag: 2023.05.17)
54bfaa3d 2023-05-11T21:01:58+03:00 [BOT] Update openroad_app (#1774) - Openlane Bot -  (tag: 2023.05.12)
---
Git Remotes

origin	https://github.com/The-OpenROAD-Project/OpenLane (fetch)
origin	https://github.com/The-OpenROAD-Project/OpenLane (push)

Reproduction material
Run stock spm
Relevant log output
See above.

Can you show the log file produced by OpenLane?
/foss/designs > iic-vlint.sh -v spm/src/spm.v
[INFO] Run verilator linting on spm/src/spm.v...
%Warning-DECLFILENAME: spm/src/spm.v:35:8: Filename 'spm' does not match MODULE name: 'TCMP'
   35 | module TCMP(clk, rst, a, s);
      |        ^~~~
                       ... For warning description see https://verilator.org/warn/DECLFILENAME?v=5.009
                       ... Use "/* verilator lint_off DECLFILENAME */" and lint_on around source to disable this message.
%Warning-UNUSEDSIGNAL: spm/src/spm.v:23:20: Signal is not driven, nor used: 'xy'
                                          : ... In instance spm
   23 |     wire[size-1:0] xy;
      |                    ^~
%Error: Exiting due to 2 warning(s)
[DONE] Bye!

OpenLane uses --Wno-DECLFILENAME so this can't be the output produced from OpenLane.

openlane.log

The linting output above is from our own linting script, iic-vlint.sh. I posted openlane.log above.

I meant verilator log file spm/runs/RUN_2023.05.22_15.31.55/logs/synthesis/verilator.log

verilator.log
Sorry, here the correct one.

Ah, I see. You have a WA in your Verilator build script:
# workaround for
# %Error: //build/share/verilator/include/verilated_std.sv:28:9: Redeclaring the 'std' package is not allowed
#28 | package std;
#/build/share/verilator/include/verilated_std.sv:2:1: ... note: In file included from verilated_std.sv

RUN rm /build/share/verilator/include/verilated_std.sv &&\
    touch /build/share/verilator/include/verilated_std.sv

Does this mean we also need this? Is this bricking something with Verilator? We have just one instance of Verilator for everything, not only for OL.

The interesting part here is that iic-vlint.sh didn't produce the same error. I could figure out what triggers the std error. If we can understand why this happens with OL, we can remove the WA. I think we can start by comparing iic-vlint.sh with the way OL runs it.

Here you go: https://github.com/iic-jku/iic-osic/blob/main/iic-vlint.sh
We do just a plan call verilator --lint-only -Wall "$FILE_NAME", without all the lib includes you do. Somewhere from the SKY130 libs the error seems to be triggered.

Whenever either this -I /foss/pdks/sky130A/libs.ref/sky130_fd_sc_hd/verilog/sky130_fd_sc_hd.v or -I /foss/pdks/sky130A/libs.ref/sky130_fd_sc_hd/verilog/primitives.v is included in the Verilator call it fails with the error.

I just tried. This happens with using any -I <file>.

Yes

❯ verilator --lint-only -Wall --Wno-DECLFILENAME src/spm.v -I src/spm.v
%Error: //usr/local/share/verilator/include/verilated_std.sv:28:9: Redeclaring the 'std' package is not allowed
   28 | package std;
      |         ^~~
        /usr/local/share/verilator/include/verilated_std.sv:2:1: ... note: In file included from verilated_std.sv
%Error: Exiting due to 1 error(s)

Ah, know I have a guess. The file share/verilator/include/verilated_std.sv says in the comment, it is automatic included whenever blablabla. What if it is included for every file, and of course the second time the std package is already declared.

It would be great if you did yes. Thanks.

Done, see https://github.com/verilator/verilator/issues/4215

@kareefardi The underlying Verilator issues have been fixed (see https://github.com/verilator/verilator/issues/4215), but the OL calling of Verilator needs to be fixed as well.
You call Verilator with
verilator  --lint-only  -Wall  --Wno-DECLFILENAME  --top-module spm  -I /foss/pdks/sky130A/libs.ref/sky130_fd_sc_hd/verilog/sky130_fd_sc_hd.v -I /foss/pdks/sky130A/libs.ref/sky130_fd_sc_hd/verilog/primitives.v /foss/designs/spm/src/spm.v -Wno-fatal --relative-includes
But -I shall point to directories, not files! From Verilator help:
-I<dir>                    Directory to search for includes

authors: hpretl kareefardi

repo: The-OpenROAD-Project/OpenLane


text:
Add in compile flags in splash

Addresses #4550
Output

Thanks, @luarss. Please add one more for QtCharts, because it's possible to compile the GUI without charts. Also, please list options alphabetically.

New version

GUI after GPU

Can we modify ORFS so it lists splash screen once?

Updated.

Would it make sense to make this a single line since it's not that many items? Also should par/mpl2 be on the list since they are conditionally compiled for MacOS?

Can we modify ORFS so it lists splash screen once?

Each step is a separate run so I think it is best to record it.  You could in principle restart the flow at any step with a new build giving a mixed result.

Can we modify ORFS so it lists splash screen once?

Each step is a separate run so I think it is best to record it. You could in principle restart the flow at any step with a new build giving a mixed result.

While it would be nice to reduce logging noise, idempotency of the steps is  a requirement....
Minimally the version is needed in every log. Dumping copyright only to console once would be Ok.

Just to clarify, I see versions.txt recording the OR, yosys and klayout versions already. Do we want something like
@echo openroad -splash in ORFS Makefile?

I don't feel the copyright is excessive.  If we really want to save a line you could be the features after the commit id.

Addresses https://github.com/The-OpenROAD-Project/OpenROAD/issues/4550

@luarss FYI It's better to use one of the special keywords such as "fix" or "resolve" to link the PR with the issue so that when merged the issue will be closed: Linking a PR to an Issue in GH

fails on mac

Doesn't this solution feel like overkill? Why does it need a whole CMake generated config file? Can't you just simply use add_definition() or similar and then reference that directly?

@maliberty
The error is because we disabled compile definitions for macos in src/CMakeLists.
. Fixing this with an else init.
@rovinski That is a good suggestion. Is there any preference for using add_compile_definitions vs add_definitions?

@rovinski That is a good suggestion. Is there any preference for using add_compile_definitions vs add_definitions?

Just whichever one works and simplifies the code.

Doesn't this solution feel like overkill? Why does it need a whole CMake generated config file? Can't you just simply use add_definition() or similar and then reference that directly?

I agree with this.  The file generation isn't needed.

@maliberty Updated, now uses less overhead

source: gharchive/pull-request

authors: AcKoucher gadfort luarss maliberty oharboe rovinski

repo: The-OpenROAD-Project/OpenROAD

license_type: permissive

license_source: github-api


text:
pdn: separate repair channels area and repairable area to avoid failing on channels with partial overlap

Fixes:

repair channels would fail if there is partial overlap in narrow channels, this separates the channel area and the actually repairable area so both can be tracked separately

Can you create a unit test for this?

@maliberty unit test created

authors: gadfort maliberty


text:
make[3]: don't know how to make /usr/ports/cad/replace/work/RePlAce-1.1.1-277-gcf289bb/src/replace/src/replace.i. Stop

You have
set(REPLACE_HOME ${PROJECT_SOURCE_DIR}/src/replace )
...
add_custom_command(OUTPUT ${REPLACE_WRAP}
  COMMAND ${SWIG_EXECUTABLE} -tcl8 -c++ -o ${REPLACE_WRAP} ${REPLACE_HOME}/src/replace.i
  WORKING_DIRECTORY ${REPLACE_HOME}
  DEPENDS ${REPLACE_HOME}/src/replace.i ${REPLACE_HOME}/include/replace/Replace.h
)

which looks for replace.i in ${PROJECT_SOURCE_DIR}/src/replace/src/replace.i which doesn't exist.
1.1.1-277-gcf289bb

Could you compile on the top-level app repo? (e.g. https://github.com/The-OpenROAD-Project/OpenROAD). I had updated it in the README.md
The standalone mode will not be supported anymore.

The standalone mode will not be supported anymore.

qflow also suggests that replace can be used with it as a standalone tool.

Besides, isn't it just an obvious bug with a path that needs to be fixed?

This is not a bug in the top-level app.
${PROJECT_SOURCE_DIR} is OpenROAD source dir and has the RePlAce submodule in the OpenROAD/src/replace.
OpenROAD/src/replace/src/replace.i is correct path to point the replace.i

This is not a bug in the top-level app.
${PROJECT_SOURCE_DIR} is OpenROAD source dir and has the RePlAce submodule in the OpenROAD/src/replace.

OpenROAD/src/replace/src/replace.i is correct path to point the replace.i

You don't have to hardcode global paths in a project. The desired behavior can be achieved by setting a cmake variable from outside.

source: gharchive/issue

authors: mgwoo yurivict

repo: The-OpenROAD-Project/RePlAce


text:
[FEATURE] Documentation improved and make some method efficient in DSU

Issue that resolved
Closes https://github.com/TheAlgorithms/C-Plus-Plus/issues/1402
Description of Change

Before there is a method called find_set implemented recursively.
Recursion uses extra space for a stack.
It also badly impact on performance due to function overhead.
find_set is the most called function in the program.
I implement this method iteratively and all problems resolved.
Documentation improved.
Readability improved.

I am creating a pull request for...

[x] Added description of change
[x] Added tests and example, test must pass
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[x] Relevant documentation/comments is changed or added
[x] PR title follows semantic commit guidelines
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Thank you for your valuable suggestion. please review it now. @Panquesito7.

Thank you for your valuable suggestion. please review it now. @Panquesito7.

repo: TheAlgorithms/C-Plus-Plus

license: MIT


text:
Math folder

This is to start the math folder and have collatz sequence as the starter!

I am sorry for this closing and opening. I take full responsibilities for the inconvenience.

On some files you used unit tests. Should we make this a requirement for all algorithms?

On some files you used unit tests. Should we make this a requirement for all algorithms?

I think that this is a good idea as it is a good way for someone using the code to know that the code works with those tests.
It is just like doctest in python.

Nice. Can you add tests to all your files like you did in math/line_length.jl (with the @testset)?

On some files, you used unit tests. Should we make this a requirement for all algorithms?

Sounds good to me. We can add it to the contributing guidelines. 👍

authors: Panquesito7 Ved-Mahajan maltejur

repo: TheAlgorithms/Julia


text:
Don't Copy, Move Instead.

Hi, can i have info on how to move instead of copying the file to ipfs? thanks.

Hey @S1m1B1lly, I missed this issue. Did you still need a feature like this? How would it work in your eyes?

@TheDiscordian thanks but I don't need it anymore

repo: TheDiscordian/ipfs-sync


text:
Construct road-edge curves

Right now, we generate RoadLanes (for AI) but we don't have any way to fetch the edge along a curve/road. Someone who wants to, for example, create a sidewalk or barrier following the edge of a road would have to place their own curve.
Let's use the same approximation mentioned here to construct one or more "Road edge curves".
For Wheel Steal Game, since RoadPoints are always added one RoadPoint at a time, we will need to be able to have these curves be per-RoadSegments. But there should also be an option/mode to create them per RoadContainer. The RoadContainer use case is likely much nicer for many users, as they can have one barrier that extends the entire road, whereas per RoadSegment they'd have to set up the configuration on each individual RoadPoint.
Some considerations:

In order to be useful, these generated 3D paths need to be visible in the viewport hierarchy
This also means great effort should go into reusing the same Path node, instead of deleting / re-adding. This is because we expect the user to place children underneath.
For that reason, likely the approach should be something like:
a. If the check mark is checked, start this process
b. See if the target curve children exist (following some naming convention); if not, create it
c. Now update the curve resource accordingly (the safe part)
c. If the checkbox is later unchecked, give a popup warning if there are any children to say that it will be deleted.
It should be an option. Perhaps by default, on for RoadContainers but off for RoadPoints.
The way this works for non-intersections is pretty clear. But this will be tricky to maintain, most likely, for intersections. If we really want to support use cases like sidewalks however, it will be important this generalized to intersection use cases as well, even if it's in a secondary step.

As we discussed, Edge curves will be placed on each RoadPoint. However, the "Create Edge Curves" flag that enables/disables them will be on the RoadContainer.
Per the requirements, if Create Edge Curves is disabled, it it will clear all of the edge curves on scene load or when a rebuild is triggered.
Also, the logic that drives much of the program behavior is such that only the selected RoadPoint gets updated when a change is made. Not the entire network. Hence, edge curves only get created for RoadPoints that are updated in some way. This may or may not be the desired behavior. Feel free to weigh in.
Lastly, since each RoadSegment will have a left and a right curve, they will be named "edge_L" and "edge_R". They will be unique on a per RoadPoint basis. Thus, complex naming isn't needed.

Minor update: The edge curves will actually be called "edge_F" and "edge_R" for "Forward" and "Reverse".

Hey @bdog2112! Thanks for laying out the additional details here. Agreed on all points above, including the naming. I appreciate the revision there, since that nicely parallels the pre-existing terminology. Couple things to upack a little further:

Per the requirements, if Create Edge Curves is disabled, it it will clear all of the edge curves on scene load or when a rebuild is triggered.

To be more explicit, let's go with:

If "Create Edge Curves" is disabled, we can outright delete the Path3D nodes (which would delete all children as well).
If "Create Edge Curves" is enabled, and any rebuild is triggered (via a roadpoint update, container-wide rebuild), we should only update the curve reference within the pre-existing Path3D nodes. This is because users will be manually placing children on these road edges, we don't want to delete their work!

Another thought I had is whether we should try to create some kind of warning or popup if a user tries to disable edges on a container when such edges already have pre-existing children. This would probably be tricky, especially since we'll still need to use export vars. So, I'm shelving that idea for now but something to consider in the future.
One other thing to watch out for is how the behavior works with undo (and redo). There's already some cases today that aren't ideal (bug here: https://github.com/TheDuckCow/godot-road-generator/issues/84) so we could potentially just tack onto that if we have new problems arise. So, don't fret if it's not perfect out of the box.

Ah I'm now realizing I already wrote much of this in the above description - anyhow, main priority is getting the reusable edges in place, other polishing features like popups and undo/redo we can take in a second stride.

Need some input on desired curve behavior when manipulating RoadPoints.
During RoadPoint Rotation/Translation (manipulation), RoadLanes are cleared. But, when mouse button is released, RoadLanes are rebuilt. Meanwhile, road geometry is updated throughout the manipulation process. What is the desired behavior for RoadEdges?

Hide RoadEdge on manipulation start. Then, show RoadEdge on manipulation end.
Update RoadEdge continuously during RoadEdge manipulation.
Leave RoadEdge visible during manipulation. But, don't update until manipulation end.

RoadEdges will have attached objects. Hence, the above alternatives are applicable, there, as well. What is the desired behavior for attached objects?
For the moment, I will proceed with option 1 for RoadEdges and option 3 for attached objects.

Also recommend performing the following test: Attach objects to RoadEdges, manipulate associated RoadPoints, and observe what happens to the attached objects. Then, think about the desired behavior of the attached objects. What is the desired behavior?

I actually am liking the idea of number two - since the objects aren't being destroyed and created each time, just updating some curves, it should remain pretty responsive. Plus it may be useful for users to preview how roadside elements will be before they release. On Mar 1, 2024 1:29 PM, "B. Rhoades" @.***> wrote:
Need some input on desired curve behavior when manipulating RoadPoints.
During RoadPoint Rotation/Translation (manipulation), RoadLanes are cleared. But, when mouse button is released, RoadLanes are rebuilt. Meanwhile, road geometry is updated throughout the manipulation process. What is the desired behavior for RoadEdges?
Hide RoadEdge on manipulation start. Then, show RoadEdge on manipulation end.Update RoadEdge continuously during RoadEdge manipulation.Leave RoadEdge visible during manipulation. But, don't update until manipulation end.
RoadEdges will have attached objects. Hence, the above alternatives are applicable, there, as well. What is the desired behavior for attached objects?
For the moment, I will proceed with option 1 for RoadEdges and option 3 for attached objects.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Alright! Just pushed an update. Here are the deets:

When user selects RoadContainer in Scene dock and toggles "Create Edge Curves" in Inspector panel, edge curves update automatically. (Before, user had to save and reload scene.)
Curves update continuously when RoadPoints are manipulated
Curves are persistent (no longer re-created) during manipulation
Attached objects are persistent unless "Create Edge Curves" is toggled
When edge curves are deleted, curve children are also explicitly deleted to avoid orphans

TTD:

Adjust curve position based on number of lanes.

Curves appear fine on first RoadSegment. But, something is wrong on subsequent segments. Investigating...

Nice update @bdog2112! Had fun playing around with it here :D
https://github.com/TheDuckCow/godot-road-generator/assets/2958461/a73cab63-f399-470d-8487-52347b5a8b17
Only comment is it seems there might be some global to local mixup (I guess that's the godot equivalent of "off by 1"), see here, just in case you weren't already aware. Really excited to see this working once we have intersection offsets accounted for, making great progress.
https://github.com/TheDuckCow/godot-road-generator/assets/2958461/cdb36b5d-1afe-4743-aaac-783a1d834b05

Pushed latest WIP. Previously, refactored code so that it would update instead of add curve points if they already existed. Determined that a couple of local/global coordinate conversions were needed in the refactored code. Curves should not plot as expected.

Nice - we can start moving the discussion more into the PR itself now, so we don't have to post in both locations - my latest comment (and future ones) will be there

I'm going to mark this task as done, since they are working in dev to spec. Good work!

repo: TheDuckCow/godot-road-generator


text:
ChatBot Issue

Hi, I have successfully build up the chatbot. However, it can only reply via image instead of message. Could I know what problem regarding this case? Thank you

Do you mean that the chat command gives you error?
If so please can you share a screenshot of the same?

authors: DiolTop MCUxDaredevil

repo: TheExplainthis/ChatGPT-Discord-Bot


text:
~4x slower upscaling compared to hosted site

I'm facing an issue where on your hosted site https://waifuxl.com/ upscaling takes about 7-15s, but when I clone the repository the identical upscales take 60s+. This occurs even when running in production mode. Any suggestions? Thank you.
Great work, it's amazing to see real-esrgan running the the browser.

The CPU usage for https://waifuxl.com/ goes up to ~80% on my computer, but doesn't rise above 30% locally.

I figured it out. To take advantage of hardware concurrency the site needs to be served over HTTPS and some specific security headers need to be sent. This has to do with the Spectre/Meltdown vulnerability of 2018.
The headers I needed were Cross-Origin-Embedder-Policy: require-corp and Cross-Origin-Opener-Policy: same-origin. You can actually set these headers quite easily in the next.config.js file.
// next.config.js
module.exports = {
  async headers() {
    return [
      {
        // Apply these headers to all routes in your application.
        source: '/(.*)',
        headers: [
          {
            key: 'Cross-Origin-Embedder-Policy',
            value: 'require-corp',
          },
          {
            key: 'Cross-Origin-Opener-Policy',
            value: 'same-origin',
          },
        ],
      },
    ]
  },
}

I made a fork of this project that lets you do batches of upscales and persist everything using IndexedDb. Thank you for the amazing work porting Real-ESRGAN to the web!

Hey @tom-leamon, sorry we took so long to get back, we probably could have saved you some time. You definitely came to the right conclusion with the headers, we have to serve those through cloudflare. If you'd like to submit a PR with the header changes for local runs we'd love to merge it.

authors: haydn-jones tom-leamon

repo: TheFutureGadgetsLab/WaifuXL


text:
Issues installing gammaos

every time i try to download gamma os to my anbernic 405m at the step Spreadtrum / Unisoc Bootloader Unlock Tool I click on connect and the pop up says no compatible device found. im not sure what im doing wrong my device says its connected at fastboot apperrs on the screen before hand.

Check drivers and ensure you are using Google Chrome.

authors: Arthurshepardson TheGammaSqueeze

repo: TheGammaSqueeze/GammaOS


text:
Bad text recognition - "its" polish/english languages

Describe the bug

"its" return as "iłs"

Where is the bug

Edit Text Window

To Reproduce
in windows I have 2 languages installed, English and Polish
I tried to select Polish or English, but it did not help
Grab Frame on the image attached
Expected behavior
Should return “its”.
A good option would be to use only 1 language
Where did you get Text Grab?

GitHub releases

Exe

Desktop (please complete the following information):

OS: Windows 10 Pro
Version: 22H2 (19045.4651)
Text Grab Version: 4.5

This is a bug with the underlying OCR models being used. I am eager to use updated models when they become available to 3rd party developers, but currently the best way to improve would be to use the Text Grab settings to install Tesseract and use those models.

repo: TheJoeFin/Text-Grab


text:
getoutput is not defined - v2-1-768

The last step of running the google collab instance ends with the following error:
NameError                                 Traceback (most recent call last)
[<ipython-input-11-f6968eae0295>](https://localhost:8080/#) in <module>
     51   get_ipython().system("grep -o 'https[^ ]*' /content/srv.txt >srvr.txt")
     52   time.sleep(2)
---> 53   srv= get_output('cat /content/srvr.txt')
     54
     55   for line in fileinput.input('/usr/local/lib/python3.8/dist-packages/gradio/blocks.py', inplace=True):

NameError: name 'get_output' is not defined
     ```

I'll fix it in a bit

authors: Pmejna TheLastBen

repo: TheLastBen/fast-stable-diffusion


text:
🛑 AdGuard is down

In 94b9a37, AdGuard (https://adguard.sny.sh) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AdGuard is back up in a273343 after 8 minutes.

repo: TheLastZombie/upptime


text:
No hay optimización en el borrado de construcciones

TIPO DE ERROR: DISEÑO
Impacto: Medio
Entorno: PC y móvil
Descripción: En cuanto eliges una construcción y quieres coger otra de ellas, tienes que ponerla y despúes borrarla para poder volver a construir una cosa diferente

Lamentamos el malentendido. La confusión se podía deber a cómo se indicaban las distintas opciones en el menú de construcción. Para cancelar la construcción de una estructura bastaba con darle al botón de Delete, pero consideramos que lleva a malentendido.
Se ha modificado el texto del botón de Delete a la hora de confirmar la construcción de una estructura por un texto y un icono de Cancel.
El error se ha solucionado en el siguiente commit: https://github.com/TheNidesRA/FrozenFury/commit/522c8292fbeafce40222525386ad0528a2891dde
¡Muchas gracias por ayudarnos a mejorar Frozen Fury!
TheNidesRA

authors: TheNidesRA miniponti

repo: TheNidesRA/FrozenFury


text:
css-exercises: color contrast updates for WCAG compliance

Because

This PR fixes the text color contrast of multiple exercises. Each color contrast was updated to comply with WCAG AA at minimum. Most colors also comply with WCAG AAA guidelines. All existing exercises were checked for color contrast compliance. Each updated exercise had its style.css, solution.css, and desired-outcome.png(s) updated.
All contrast compliance was checked with this tool.
This PR

foundations/05-decendant-combinator

Text color "red" → #E00000. AA compliant.

grid/01-grid-layout-1 & 02-grid-layout-2 & 03-grid-layout-3

Header background color #FFDE22 → #006157. AAA compliant.
Sidebar background color #FF7755 → #005B94. AAA compliant.
Nav background color #00DDFF → #642CDE. AAA compliant.
Article background color #BCCBDE → #7E1DC3. AAA compliant.
Footer background color already AAA compliant.

Desired-outcome png(s) updated to match new color changes.

Issue

Closes #286 and #324 and #325
Additional Information

Pull Request Requirements

[x] I have thoroughly read and understand The Odin Project Contributing Guide
[x] The title of this PR follows the location of change: brief description of change format, e.g. 01-flex-center: Update self check
[x] The Because section summarizes the reason for this PR
[x] The This PR section has a bullet point list describing the changes in this PR
[x] If this PR addresses an open issue, it is linked in the Issue section
[x] If applicable, I have ensured that the TOP solution files match the Desired Outcome image

beautiful... great work @christinamakes

authors: christinamakes codyloyd

repo: TheOdinProject/css-exercises


text:
Make location of spec files more explicit in README

This change was motivated by helping 2 - 3 different people understand where to actually complete the remove x from xit instruction in Discord. While it's slightly more verbose / repetitive, I'd argue better to give explicit  instructions especially at a stage when things like this aren't necessarily obvious to learners.

Thanks so much for taking the time to submit the PR to clarify these instructions. I have one idea & I'd love to hear your input. +1

Updated, how does this look?

repo: TheOdinProject/ruby-exercises


text:
Dashboard App instance 개수 표시

현재 App instance 개수가 dev + staging + prod 개수로 표시되는 문제..
실제로는 각각이 나뉘어져 표시되어야 함. 운영자가 프로덕션이 저 인스턴스 개수인 것으로 오인할 수 있음.
ex) dev (1), prod (2)

현재 좌측 화살표 클릭시, 영역별로 인스턴스 개수가 표시됨.

화살표 클릭을 하지 않아도 알 수 있도록 dev (1), prod (2) 으로 표기가 필요

authors: SeungpilPark jinyoung

repo: TheOpenCloudEngine/uEngine-cloud


text:
Internal Error Compiler VS2017

I am getting an internal error in Visual Studio's compiler. I am using the 2017 64-bit compiler without the permissive flag. It is the most up to date compiler for the 2017 version.
It seems to have a problem with:
return c.check(L, index, std::forward<Handler>(handler), tracking);
On line 10372 (in the single file) of the current release.
I have disabled the permissive flag for the Visual Studio project, which fixes a different problem. I have no idea why this is happening, but if I just have it return false it works fine. Also right above that you have:
// VC++ has a bad warning here: shut it up
(void)c;
so I'm not sure if that has something to do with it. If this can't be easily fixed then is there something you recommend? How often does this function actually get used, would it be a train wreck if I just returned true/false?
This is without any code other than a main and
#include "libs/sol/sol.hpp"

Ok, now I am more confused. I was playing around a bit with your code and the problem actually seems to be with:
using Tu = meta::unqualified_t<T>;
Instead using that line of code I manually substituted in-place of Tu, so 'c' is now defined as
qualified_checker<T, lua_type_of_v<meta::unqualified_t<T>>> c;
instead of
qualified_checker<T, lua_type_of_v<Tu>> c;
I really don't see how this could possibly make any difference, but for compatibility sake I think it would be best to get rid of the using statement.

I went through and replaced many of these in an effort to fix non-/permissive- bugs and /permissive- bugs in the MSVC compiler. Long story short, the compiler is super wrong here and workarounds either break upstream (VS2019) or tie my hands with bad code that doesn't compile on GCC or Clang. :/
I can spend some more time fixing this for the sake of just trying to get VS 2017 to stop being garbage.
Also: no, please don't just return true or false: this is the thing that changes how sol::overload works and also puts sane type safety into the system. Returning just true/false will likely break the entire system in hilarious spectacular (but probably very frustrating) ways.

As a side note, I only have VS 2019 right now (because I was trying to fix another VS 2019/2017 bug and I had to delete everything, only for the problem to still be there, HAH) so it'll be a bit while I reinstall 2017. For the 3rd time. e.e

I can't reproduce this error on VS 2017, VS 2019, or VS2019 Preview: sorry. Please include the full error code and the full code sample you run through Visual Studio, maybe with your compiler settings too.

authors: Mjdgithuber ThePhD

license: mit

license_source: bigquery


text:
[Snyk] Security upgrade python from 3.7 to 3.13.0b3

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 2 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

base/scrapyd/1.2.1/Dockerfile

We recommend upgrading to python:3.13.0b3, as this image has only 197 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  829

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  829

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  829

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  829

Resource Exhaustion SNYK-DEBIAN12-NGHTTP2-5953379
  829

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Resource Exhaustion

Checkmarx One – Scan Summary & Details – bc45a010-9e19-476a-ba49-559e16e8beff
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2023-36415
Python-azure-identity-1.13.0
Vulnerable Package

CVE-2024-36039
Python-PyMySQL-1.1.0
Vulnerable Package

CVE-2024-39689
Python-certifi-2023.7.22
Vulnerable Package

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 8
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 12
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 2
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 23
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 8
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 8
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 14
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 11
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 11
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 9
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 8
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 12
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 8
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 7
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 12
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 12
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 13
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 12
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction

More results are available on AST platform

repo: TheRedHatter/vulhub


text:
doc: Add The Things Node quickstart

Summary

New documentation page (quickstart) about using The Things Node with the Things Stack
Migrating V2 documentation to The Things Stack.
Old V2 doc:
The Things Node: https://www.thethingsnetwork.org/docs/devices/node/quick-start/
Screenshots

...
Changes

...
...

Notes for Reviewers

NOTE: I haven't migrated some sections as I don't have a Things Node.
@laurensslats
@benolayinka
Checklist

[ ] Scope: The referenced issue is addressed, there are no unrelated changes.
[ ] Run Locally: Verified that the docs build using make server, posted screenshots, verified external links. Test with HUGO_PARAMS_SEARCH_ENABLED=true if style changes will affect the search bar.
[ ] New Features Marked: Documentation for new features is marked using the new-in-version shortcode, according to the guidelines in CONTRIBUTING.
[ ] Style Guidelines: Documentation obeys style guidelines in CONTRIBUTING.
[ ] Commits: Commit messages follow guidelines in CONTRIBUTING, there are no fixup commits left.

@nejraselimovic I have updated the document. All the required images are added to the doc.

repo: TheThingsIndustries/lorawan-stack-docs


text:
🛑 Trident API is down

In 5b6a76a, Trident API (https://thetrident.one/api) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Trident API is back up in 4c6fdb4 after 2 minutes.

repo: TheTridentOne/upptime


text:
Chronicle of Shadows not working

If i collect an item, the book disappears and the collected item takes its place. when i go into creative to grab the book, it doesn't open. I'm using 0.7.1+1.19.2 on a server using Fabric 0.15.5.

Do you have patchouli installed?

Presumed issue with no Patchouli

authors: TheWinABagel vortxxswirly

repo: TheWinABagel/Zenith


text:
🛑 Linkedin is down

In 449defb, Linkedin (https://www.linkedin.com) was down:

HTTP code: 429
Response time: 120 ms

Resolved: Linkedin is back up in 1b24b73.

repo: Thexyz/downly


text:
Negation meets unit-casting causes invalid/broken output

p {
  width: -($foo/16)em;
}

becomes:
p {
  width: -($foo / 16)em);
}

This will be fixed in v2.14.2 or newer.

authors: ThisIsManta maranomynet

repo: ThisIsManta/stylus-supremacy


text:
🛑 x5i5 Plex2 is down

In 983c5d9, x5i5 Plex2 ($X5I5_PLEX2) was down:

HTTP code: 404
Response time: 89 ms

Resolved: x5i5 Plex2 is back up in ccf750f.

repo: Thomvh/thvmh-uptime


text:
IndexError: list index out of range

I using Python 3.8.5.
OS: Ubuntu 20.04.2 LTS
known: ronaldo.jpg
Docker version 20.10.7, build f0df350
And i got this error, help me please

Refer to #117

authors: JunPham ThoughtfulDev

repo: ThoughtfulDev/EagleEye

license: WTFPL


text:
Threadfin not booting since today - log frozen in 'check file'

Hi, since today (after a docker reboot) my threadfin instance is not booting up, looking at the logs it says:
2024/08/31 13:56:16 [Threadfin] Header filename:        ....
2024/08/31 13:56:22 [Threadfin] Check File:                  ...
So it downloads the m3u as normal but then freezes in the status check file

I am having the same issue.

Same Problem here. Reverted back to threadfin:1.2.0

I've noticed the same. Removed everything (of cause didn't have any backup) and reverted back to v1.2.2 and it works again.
I couldn't find a log or anything showing what the problem was (using 75% CPU and almost all RAM - QNAP NAS).

More than likely you have a ton of 24/7 channels. You'll need to get rid of those as now it's updating the incoming m3u

can you please develop on " as now it's updating the incoming m3u"? Is is the "Probe Channel Feature" mentioned in the changelog?
How can we remove 24/7 channels on the fly?

More than likely you have a ton of 24/7 channels. You'll need to get rid of those as now it's updating the incoming m3u

what does that mean? I guess a lot of us have an external m3u provider and we use threadfin to filter / etc. if not threadfin required to pre-filter m3u ... isnt that the initial purpose of threadfin? i love this project and i would love to see a fix for this

More than likely you have a ton of 24/7 channels. You'll need to get rid of those as now it's updating the incoming m3u

I love this project! I think this will cause trouble for lots of people, since they are not in control of an external M3U. Wouldn't it be more "correct" to do it on the filtered channels instead? This would limit the amount of channels greatly. Just an suggestion ....

This has nothing to do with probing. I'm adding tvg-id where it's blank except it's duplicating the channels. People with 24/7 channels are getting those duplicated which is why it's taking forever.
I'll have a fix on Monday or Tuesday when I'm at my computer

oh wow I just started using Threadfin and was wondering why so many people rate it over xTeVe, when it couldn't even load up my relatively small m3u. Spun up v1.2.2 and it's working like a charm! Thanks for that suggestion, and I hope this gets fixed soon!

Could this be the same issue I'm having when importing a playlist rather than at startup, where Threadfin eventually gets killed for OOM?

Don't use 1.2.5 revert to one that works until 1.2.6 comes out

Don't use 1.2.5 revert to one that works until 1.2.6 comes out

I've reverted to 1.2.2, but with Threadfin running in Docker, when loading a 110MB M3U, the memory usage balloons so much that the entire VM running Docker (7GB memory) gets killed for OOM

Thank you for this topic, I thought for some reason my installation went bust - good to see that I am not the only one getting issues. I know I have a massive m3u list but never had these resource issues (eating up CPU and RAM). Hope they fix it soon, love this selfhosted app!

I guess, 1.2.6. should fix this issue - i have updated to 1.2.6 but its still booting up for more than one hour with 80-90% CPU usage

Same for me (used on unRAID).

1.2.5 and 1.2.6 also don't work for me, they take way too long to boot.
1.2.2 boots within a minute or so, 1.2.5 and 1.2.6 was taking way longer.
Please fix this?

Also have the same issue hanging on check_file in version 1.2.6

I can also confirm 1.2.6 doesn't fix the issue.

Can you confirm if your m3u contains 24/7 channels? If so, then that is the problem. Threadfin now assigns a tvg-id to those that are blank, which probably means it's having to go through the massive m3u

There are some 24/7 channels in there, yes. Can this be fixed somehow from threadfin? Because i am not sure yet how i should handle it otherwise (as its an external m3u which would then need to be prefiltered)

I don't really understand what you mean by 24/7 channels.
The playlist I'm using is massive (about 10.000 streams).
I don't really understand why a tvg-id needs to be assigned.
All I know is that up until 1.2.2 everything is just working fine.
In later releases new features are added which is nice.
But normally behavior off the application should not change or this should be clearly stated in the release notes.
Whether the whole tvg-id is needed I don't know. If it really is I would suggest it is only done on channels that are filtered in order to reduce processing.

As a workaround iam using https://github.com/euzu/m3u-filter to filter down my external m3u and then give it to threadfin, but would be great to have a fix in threadfin

At least that's a workaround.
Still I'm not going to update threadfin. I'm hoping there is a way that existing performance an functionality can be kept.
I'm not looking forward to add yet another layer of failure, even more when before I had no need to do so.

I’ve found reverting to 1.2.0 to be stable again

Can you confirm if your m3u contains 24/7 channels? If so, then that is the problem. Threadfin now assigns a tvg-id to those that are blank, which probably means it's having to go through the massive m3u

what would be the solution if we wanted the 24/7 channels available?
According to my list, I've 103 channels with "24/7" in their name. About half are in my "active streams" list on v1.2.3. I don't understand how this is causing such a massive issue at boot.
I can't say i'm interesting in running it via m3u-filter. I chose threadfin as it appeared to be everything i needed in 1 tool.

Can you confirm if your m3u contains 24/7 channels? If so, then that is the problem. Threadfin now assigns a tvg-id to those that are blank, which probably means it's having to go through the massive m3u

Could you please explain the reasoning behind the tvg-id assignment ?

I need you to understand me clearly. I will not be tailoring this software around your shitty providers who give you a massive m3u with 10,000 channels and most of them useless 24/7 channels. The rest of us have proper m3u's that are not clogged up. Please pre-filter it with a service like m3u4u or something like it. Stop asking for a fix for this

I need you to understand me clearly. I will not be tailoring this software around your shitty providers who give you a massive m3u with 10,000 channels and most of them useless 24/7 channels. The rest of us have proper m3u's that are not clogged up. Please pre-filter it with a service like m3u4u or something like it. Stop asking for a fix for this

You might be right about the reasons why the issue can't be solved. And I might agree or not.
However I don't think your response displays the right attitude.
One thing is explaining why something is not possible, another saying someone is asking for something taylor made. As a matter of fact there is some functional regression and this is not clearly documented . If you don't document regression on something you shouldn't be frustrated when users update and complain about it.

One thing is explaining why something is not possible, another saying someone is asking for something taylor made. As a matter of fact there is some functional regression and this is not clearly documented . If you don't document regression on something you shouldn't be frustrated when users update and complain about it.

This is open-source and he is in no way obligated to document anything. I'm a dev my self and i find this comment so frustrating. He decided to fork an existing project and adjust it. Nothing is holding you or anyone back from using v1.2.3 which works.

One thing is explaining why something is not possible, another saying someone is asking for something taylor made. As a matter of fact there is some functional regression and this is not clearly documented . If you don't document regression on something you shouldn't be frustrated when users update and complain about it.

This is open-source and he is in no way obligated to document anything. I'm a dev my self and i find this comment so frustrating ("i want / need it fixed"). He decided to fork an existing project and adjust it. Nothing is holding you or anyone back from using v1.2.3 which works.

I think communication is key.
You're absolutely right about him doing this work in his free time . But once you have a user base and want to keep it you need to document changes to some degree.
I'm also a dev and definitely see why my comments could be frustrating. But on the other hand this is also a bit frustrating as an user

Nothing is holding you or anyone back from using v1.2.3 which works.

2 points here:

yes there is an issue stopping (some) of us using older versions. https://github.com/Threadfin/Threadfin/issues/341. fixed for >=1.2.4 but it introduces the issue discussed in here.
this is also the entire point of this thread. this new feature for tvg-id has regressed.
You've admitted the issue is 'fixed in an older version', i'd imagine to any normal person that would imply newer versions are broken.

maybe it's me, but i see an entire thread here of people with issues, it's not isolated to 1 or 2 users.
Yes the dev can do as he sees fit. It's their software, time and desires. us users are just along for the ride.
fwiw, i wasnt on the attack in my last message, but appears it may've come across as that. Applogies if i've offended anyone, that wasnt the intention.
ateotd, Fyb3roptik has spoken, closed as "complete" so time to find another tool that works for me as this one no longer functions in my scenario.

Wow this thread took an interesting turn, I'll leave it at that.

I just wanted to state that using m3u4u is a great proposal from @Fyb3roptik. It 1st solves the issue (which i think is not because threadfin is doing something wrong) but our m3us are sorted, named, grouped in a way which is not standard and / or rubbish and 2nd gives far more granular renaming, sorting ability outside of threadfin. Then use threadfin for the bare purpose of mapping epg, proxying & serving to emby, etc.

At that point the filtering capabilities of threadfin become useless but yeah

You can use an alternative project called Stream Master [](https://github.com/SenexCrenshaw/StreamMaster)

You can use an alternative project called Stream Master

I have tried StreamMaster, although the interface is nice and the potential with this project looks positive, I experienced more buffering issues than usual plus I could not figure out epg and related guide data, it worked at first then stopped working, no idea what was going on or how to fix.  Possibly user error, couldn't find much information re: setup, settings etc.  Documentation seems light.  Will keep an eye on it for sure.

I need you to understand me clearly. I will not be tailoring this software around your shitty providers who give you a massive m3u with 10,000 channels and most of them useless 24/7 channels. The rest of us have proper m3u's that are not clogged up. Please pre-filter it with a service like m3u4u or something like it. Stop asking for a fix for this

It's clearly an issue because a number of people here are unable to use threadfin now, is there any way you could add an option that would allow us with shitty providers to continue using the app?

You can use an intermediate tool like https://github.com/euzu/m3u-filter  or other online tools.
Ofc this complicates the deployment because you're adding another layer into the stack.
I've been experiencing the so called duplication issues and they are quite annoying and detrimental to the overall experience.
From a technical standpoint the easiest thing is assigning unique id's if they are not present instead of working out a whole logic structure to distinguish unique channels. Specially in garbage playlists this is very difficult.
However I don't understand why we are called entitled (or annoying) for complaining that we can't use a tool we were using like we already were.  If you make the decision to not support an existing use case because it's technically getting to complicated you need to communicate this properly in the release notes. Ideally you explain the reason so that users at least know were you're coming from. Otherwise you make sure you test things properly and that you don't have regression in existing use cases.
Yes the application is open source and no retribution is received, but your application will have no future if you don't communicate properly. Proper communication shouldn't be a big ask.
At this point I've spend hours trying to migrate channels through m3u-filter so that when finished I can migrate to one of the newer versions of threadfin. I'm not really pleased about this outcome because of the required effort but at least I get from where the devs are coming. I just wish they communicated properly and not after the fact when a lot of us were complaining.
For now I'll keep  using threadfin but I definitely will keep an eye open for other alternatives in order to simplify my stack.

This issue is just absolutely ridiculous, and @Fyb3roptik is absolutely laughable. I heard he is working on a Jellyfin replacement. LOOOOOL, it will be funny with this mentality.

People that don't understand how tech works laughing at programmers. Ok buddy. Go cry somewhere else

I need you to understand me clearly. I will not be tailoring this software around your shitty providers who give you a massive m3u with 10,000 channels and most of them useless 24/7 channels. The rest of us have proper m3u's that are not clogged up. Please pre-filter it with a service like m3u4u or something like it. Stop asking for a fix for this

It's clearly an issue because a number of people here are unable to use threadfin now, is there any way you could add an option that would allow us with shitty providers to continue using the app?

For us shitty-provider-peasants i found this tool here:
https://github.com/sonroyaalmerol/m3u-stream-merger-proxy
This does everything threadfin does, and even more.
Is basically a complete replacement.

repo: Threadfin/Threadfin


text:
Help needed?

Hey @m110 ,
I have been enjoying your content and your course (so far 😉 )! At work, we are on the journey to an event-driven-architecture and are leveraging SQS in specific quite a bit. We would really like to test out watermill as the backbone for this architecture but this package seems a bit "underdeveloped" (no offense!). Do you have concrete plans to maintain and support it or is this more something the community should take care of? I am just curious if you are looking for help to maintain/develop this package to bring it to a stable release? Or do you suggest to better fork and maintain in private?
Greetings from Berlin!

Hi @bastiankoetsier! Pls check this PR https://github.com/ThreeDotsLabs/watermill-amazonsqs/pull/14#issuecomment-1906021524
I've been using it for a while and works pretty good for my use case

@Mariscal6 thanks for the response! I saw the PR but was a bit discouraged/curious about the plans of this package. Hence my question for a "stable"/maintained release of it.

Hey @bastiankoetsier! We definitely want to support this package in the near future. It would be great to hear feedback from people who use SQS/SNS on production, as we currently don't. :)

Releasing a stable v1.0.0 is one of our goals for Q1. We're also happy to review contributions (I'm sorry if it takes long - please ping us if we don't reply right away!)

@roblaszczak is working on v1.0 right now, so I'm closing the issue. :)

repo: ThreeDotsLabs/watermill-amazonsqs


text:
🛑 tesetter is down

In b7f52f9, tesetter (https://teset-min.farhansamil.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tesetter is back up in 4682090.

repo: Thunderoar/upper


text:
Update version for 14.1.3 in properties

Update version for 14.1.3 in properties

Do you mean to have a plugin jar that only supports 14.1.0 and 14.1.1, then another jar for 14.1.3 and later?  Srikanth suggested that, but it seems like a pain.  I guess it's not so big a deal, though.  Just add another property file and a new target to for common.xml to detect the proper version.

I would suggest support latest only, and probably if you guys still use 13, then it too.

Also, @EBatTiVo can you run unit tests in 14.1.3? I got some issues

Will do.  It’ll take five minutes.
-Eric
From: as3boyan [mailto:notifications@github.com]
Sent: Friday, May 29, 2015 8:49 AM
To: TiVo/intellij-haxe
Cc: Eric Bishton
Subject: Re: [intellij-haxe] Update version for 14.1.3 in properties (#283)
Also, @EBatTiVohttps://github.com/EBatTiVo can you run unit tests in 14.1.3? I got some issues
—
Reply to this email directly or view it on GitHubhttps://github.com/TiVo/intellij-haxe/pull/283#issuecomment-106853838.

This email and any attachments may contain confidential and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments) by others is prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete this email and any attachments. No employee or agent of TiVo Inc. is authorized to conclude any binding agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo Inc. may only be made by a signed written agreement.

Unit tests all run fine.  This merge is approved.  I'll do the work to get a better compatibility note.

Thanks. I just got an errors when I try to run unit tests.

By the way, did you do a make from the HEAD this morning, or were you synced to the same point as the rest of the release?  I’m just wondering because there was that extra parsing fix that didn’t make it into the 13.1 and 14.0 builds.
-Eric
From: as3boyan [mailto:notifications@github.com]
Sent: Friday, May 29, 2015 9:10 AM
To: TiVo/intellij-haxe
Cc: Eric Bishton
Subject: Re: [intellij-haxe] Update version for 14.1.3 in properties (#283)
Thanks. I just got an errors when I try to run unit tests.
—
Reply to this email directly or view it on GitHubhttps://github.com/TiVo/intellij-haxe/pull/283#issuecomment-106859635.

This email and any attachments may contain confidential and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments) by others is prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete this email and any attachments. No employee or agent of TiVo Inc. is authorized to conclude any binding agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo Inc. may only be made by a signed written agreement.

I updated project. (VCS - Update), so it seems like I build it from HEAD

OK.  No problem.
-Eric
From: as3boyan [mailto:notifications@github.com]
Sent: Friday, May 29, 2015 9:31 AM
To: TiVo/intellij-haxe
Cc: Eric Bishton
Subject: Re: [intellij-haxe] Update version for 14.1.3 in properties (#283)
I updated project. (VCS - Update), so it seems like I build it from HEAD
—
Reply to this email directly or view it on GitHubhttps://github.com/TiVo/intellij-haxe/pull/283#issuecomment-106864715.

This email and any attachments may contain confidential and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments) by others is prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete this email and any attachments. No employee or agent of TiVo Inc. is authorized to conclude any binding agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo Inc. may only be made by a signed written agreement.

Hmm. I guess it was the extra text that caused the upload error.  That's good to know.

repo: TiVo/intellij-haxe


text:
Task9 core delete comments

task 9:

add functional delete comment button (only able to delete their own comments)
delete button would only show on the comments that has same username as logged in user
create a fake deleted effect (removes it from commentsShowing)
alert would be shown when comment has been deleted successfully on the server side
alert would be shown when comment has failed to be deleted
roll back of deleted comment would happen when failed to delete (revert the commentsShowing back to allComments)
new comments have their delete button and like button disabled until the page rerenders or page refresh to prevent interacting with fake comments

additional:

after sending comment the send button would be disabled until the server has processed the result
roll back of comments would happen when comment has failed to send (same logic as above).

Thanks for the feedback Ali 😁


text:
🛑 Melon Ticket is down

In 3935ca8, Melon Ticket (https://ticket.melon.com) was down:

HTTP code: 406
Response time: 1004 ms

Resolved: Melon Ticket is back up in 8f91821 after 9 minutes.

repo: TicketOpen/status


text:
Remove "fresh" dependency strategy from the matrix.

This reverts to essentially the version of the pipeline YAML file from
before we added the "fresh checkout" version. It seems like running too
many tests concurrently is causing us trouble where the server gives us
502s, so this is an attempt to reduce it. Limiting the number of runners
means that we would have to wait for two (or more) tests to complete
one after the other. In the context of a test pipeline, pinned
dependencies are more useful than a fresh install.

I think for a fresh install we will have to go with the strategy from https://github.com/TileDB-Inc/TileDB-Cloud-Py/pull/169#issuecomment-910716803, because right now trying it on every PR appears to be causing too much flakiness.

ha ha ha it did not work ha ha ha

this takes it from “almost never works” to “sometimes works” so it’s going in

repo: TileDB-Inc/TileDB-Cloud-Py