Is there anyway to check if one script is set as autoload(singleton) script ?

I'm trying to add a checker in my script
e.g.
SceneManager.gd
# This script manage scenes, need to run as @@ Singleton script @@
func _ready():
       if not is_autoloaded():
             print("[error] this scripts should run as autoload script !!!")

Is there a function to check if current script is autoloaded ?

Not directly, but this can be accomplished with a script like this (autoloaded as "Autoloaded"):
extends Node

var loaded = false

func _ready():
	if Autoloaded.loaded:
		printerr("[error] this scripts should run as autoload script !!!")
	else:
		Autoloaded.loaded = true

This code:

Will fail if the script is not autoloaded (since it accesses its autoloaded instance).

Will print an error if there is more than one instance (allowing only the autoloaded one).

By the way, GitHub isn't a support forum, typically it would be better to ask these questions elsewhere. However, I'll leave this open in case we wanted to add something like is_autoloaded.

That is epically hard to know, it needs to be added to docs and a is_autoloaded function would be VERY welcome (hint hint )

@aaronfranke Thanks

I've been thinking about how one could implement this. The problem is that Singleton Nodes are just normal Nodes at runtime.
One way to do it would be to just add a property is_autoloaded to the Node class that is set to true after an autoloaded Node is instantiated. This, of course, has the downside that it would be easy to manipulate that value from the outside.
SceneTree could also create and hold a list of autoloaded Nodes.
Reading and comparing Autoloads from ProjectSettings at runtime will only work if the name of the autoloaded Nodes is never changed.
One could also try to check ScriptServer for matching globals but then this would only work with Autoloads that have "Singleton" enabled, and depends on the registered script languages. I also couldn't find an easy way of retrieving globals directly from ScriptServer.
Any thoughts on this?

This should work:
func _ready():
	# Autoloads are always children of the SceneTree's root node and not the SceneTree's current_scene
	if get_parent() == get_tree().root and self != get_tree().current_scene:
		print("This is an autoload %s" % name)
	else:
		print("This is NOT an autoload %s" % name)

@mrcdk Thanks, this helps me out

I saw that some years ago @vnen added has_autoload to ProjectSettings.cpp
https://github.com/godotengine/godot/pull/40162/files#diff-d06617966387fb7135d4af8cf52217b94e7a4c658c6ed9f259bbf8cd801e31d5R967-R989
However this was never exposed to GDScript/C# (EG: via EditorPlugin): is it a design decision?

However this was never exposed to GDScript/C# (EG: via EditorPlugin): is it a design decision?

I didn't feel the need to expose it. But I believe you can already get a list of autoloads from ProjectSettings, since they are a setting like any other under the hood (maybe it's not properly documented).
Still, this issue is 3 years old, so it probably should be closed and if this is needed it should be opened as a proposal instead.

Thanks very much for the reply @vnen .
Yes you're right, this code from GDScript works:
if ProjectSettings.has_setting("autoload/Game"):
   var game = ProjectSettings.get_setting("autoload/Game")
   print(game) # *res://addons/game-template/game.gd

Issue can be closed on my side!


feat(demo): sort the menu items in the documentation

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactoring
[ ] Build or CI related changes
[ ] Tests related changes
[ ] Documentation content changes

What is the current behaviour?
The menu items in the documentation didn't sorted
Closes #5815
What is the new behaviour?
The menu items in the documentation sorted alphabetically

I think we shouldn't sort 'Foundations' and 'Documentation' sections. I will exclude this sections from sorting.


Scss implementation

Hy @rajeshwarpatlolla !
This pullrequest contains:

[x] plugin installation in the dev section of the package.js file (gulp-scss, gulp-autoprefixer)
[x] extention of gulp task css2js to handle scss
[x] new folderstructure for scss files (foldername is "scss")
[x] a file that holds all variables, called "variables.scss"
[x] the ionic-datepicker-styles.scss file that imports the variables and uses them
[x] refactoring of all hex colors to scss variables

This pullrequest closes #271 , #238.

You could consider to ship the plugin in two files, .js and .css and also provide an scss folder including all .scss files. This could make it even easier to customize you module.

great work .. i was working on something like this in my own fork ...
consider simplifying the scss using mixins an nested classes ..  (that's what i'm doing right now).

Cool, I avoided this because ther where not too many changes in the Code. I was hoping the PR goes through faster if there are not that many changes.
What will you do if your done? How do we merge our pr's?

Hi @rajeshwarpatlolla!
When do you consider to merge this pr?
Do you have knowledge about merging pr's?
If you I could hlep you...


Fix 1.4

Codecov Report

Merging #193 (05df3ce) into master (0759638) will not change coverage.
The diff coverage is n/a.

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

@@            Coverage Diff            @@
##             master     #193   +/-   ##
=========================================
  Coverage     73.31%   73.31%
  Complexity      776      776
=========================================
  Files           101      101
  Lines          2372     2372
  Branches        271      271
=========================================
  Hits           1739     1739
  Misses          542      542
  Partials         91       91

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 0759638...fe1b862. Read the comment docs.


Copy/Paste doesn't work with general clipboard

Hi, I've just tested it and it seems you cannot copy/paste from within the environment but only inside of onlyoffice application. This is someone a limit. If I want to copy a text from web, or a pdf document or anything else from outside of onlyoffice the copy/paste function will not work.

Opening this to the documentserver


Internationalization

Hello!
I'm in the process to add i18n module for translations.
in next.config.ts according to docs I have to wrap up like in pic below. Do you have any idea how to wrap up current nextConfig?

const withNextIntl = require('next-intl/plugin')();

/** @type {import('next').NextConfig} */
const nextConfig = {
}

module.exports = withNextIntl(nextConfig);

I have done it like that and works. But I am having issues using useRouter to change between langugae routes:


Update repositories.txt

Add sensirion libraries 2021-11

All ERRORs should be resolved
Removed 2 repositories from the list
Tagged the one missing the corresponding tag.

Yay! @ArduinoBot please check it again.

Uh, sorry, just squashed the two commits for a clean commit history. No changes, just a squash.
Didn't expect you guys to be this fast. Thank you!


Refactored Lexer (and a bit more)

Removed unnecessary includes
Suppressed two -Wextra warnings
Added some consts + noexcepts here and there
Compacted all returns of currs and some more
Fixed the bug referenced in #99
Changed the function replace_escape_chars (in testing on compiler explorer, this change reduces the size of the assembly from 346 lines to 129 lines on -O3, probably reduces memory usage, and increases the speed since accessing a jump table is more likely to be faster than accessing a hashmap)

Also, yay #100!

ok, so I've made some improvements to token.cpp, but I'm not sure you'll like it. Because instead of == the is_value() function now do this:
return (type >= TokenType::BOOL_L && type <= TokenType::VAR)
		|| type == TokenType::OPEN_SQUARE;

cancelling token refactor, cuz it didn't work.

I left some comments on the formatting.  I also still need the travis file as I'm currently working on it. I'm not sure how to accept only certain changes, so I manually added them in (unnecessary includes, const, gitignore). For the switch optimization, for now I want to keep it as a map for readability, but I added an issue as I'm going to revist this later in the future. Thanks for the help!

I'm not sure how to accept only certain changes, so I manually added them in (unnecessary includes, const, gitignore).

I think this might help? https://stackoverflow.com/questions/7217031/github-accept-pull-request-but-only-some-commits

For the switch optimization, for now I want to keep it as a map for readability, but I added an issue as I'm going to revist this later in the future. Thanks for the help!

Ah, ok then. And also, no problem :).


SQL syntax issue

I'm using version 1.1.2 and I'm getting this error.
You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '"password" = 'HASHED MD5 HERE'' at line 1
The code that I use to execute the query is:
 $user = $db->select('users', [ 				'name', 'id' 			],[  				'email' => $email, 				'password' => $pass,             ]);
The generated query:
SELECT "name","id" FROM "users" WHERE "email" = 'MY EMAIL' "password" = 'HASHED MD5 HERE
It's me or there should be an 'AND' between "email" and "password"?

I see a comma after $pass. Maybe is that?

@Nicero For some odd reason PHP allows orphan commas after last array just like JS. (Don't know why...)
@lluiscab You are generating your query incorrectly. Please read the documents next time first before reporting an issue. The time you would spend writing the issue could have been used to debug the issue yourself and continue your day.
http://medoo.in/api/where
Read the "Relativity Condition" section.
Thanks.

 And I know what you mean. Specially sometimes when the answer hangs in front of your face just after you post a question. haha
Cheers!

This time I've been looking to the docs (Select and where) but I can't find a way of executing that query (I'm sure there's a way and also I'm sure It's in front of my face)
 SELECT * FROM   conversations WHERE  id IN (SELECT conversation_id               FROM   member_conversation_map               WHERE  member_id = 123)


Create initial distributions for turtle, sparql and pie

I've been following progress on these for a little while - I'm interested in getting distributions for turtle and SPARQL highlighting working.
I've taken look at the advice over at the highlight.js repo and gotten this into a working state. There's an index.html included in this PR which demonstrates the highlighting for each of pie, turtle and SPARQL.
Running the highlight.js tests shows a few failures, namely the turtle grammar causing "exponential" and "polynomial" backtracking, and some other languages getting misrecognised as pie. I haven't fixed these for now and would need some help from the maintainers if these do need to be fixed.
But seems to work well enough for now!

causing "exponential" and "polynomial" backtracking

Those can lead to pretty serious security issues if highlighting user provided code (because they can craft damaging payloads)... and stability issues even if you know the code isn't malicious because you could still run into code that would lock up your browser, or Node.js, etc...  they are the things someone really should focus on understanding and fixing - though it's not always easy...

Cheers for the review Josh - I'm certainly up for trying to understand it further. For now, this is the output I'm getting from the tests - the quantifiers are pretty verbose and I'm struggling to even map these back to where they're appears in the turtle grammar.
1) turtle
       should not cause exponential backtracking:
     Error: turtle/[1]/begin: The quantifier `([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])*` ambiguous for all words "\\-".repeat(n) for any n>1. This will cause exponential backtracking.

To fix this issue, you have to rewrite the element (let's call it E) of the quantifier. The goal is modify E such that it is disjoint with repetitions of itself. This means that if a (sub-)string is matched by E, then it must not be possible for E{2}, E{3}, E{4}, etc. to match that (sub-)string.

Example: `(?:\w+|::)+`
The problem lies in `\w+` because `\w+` and `(?:\w+){2}` are not disjoint as the string "aa" is fully matched by both. In this example, the pattern by easily fixed by changing `\w+` to `\w`.
In the real world, patterns can be a lot harder to fix. If you are trying to make the tests pass for a pull request but can't fix the issue yourself, then make the pull request (or commit) anyway. A maintainer will help you.

Full pattern:
/\^\^([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F]([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.]*[-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀])?)?:([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_:0-9]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])*([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])?/im

turtle/[4]/begin: The quantifier `([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])*` ambiguous for all words "\\-".repeat(n) for any n>1. This will cause exponential backtracking.

To fix this issue, you have to rewrite the element (let's call it E) of the quantifier. The goal is modify E such that it is disjoint with repetitions of itself. This means that if a (sub-)string is matched by E, then it must not be possible for E{2}, E{3}, E{4}, etc. to match that (sub-)string.

Example: `(?:\w+|::)+`
The problem lies in `\w+` because `\w+` and `(?:\w+){2}` are not disjoint as the string "aa" is fully matched by both. In this example, the pattern by easily fixed by changing `\w+` to `\w`.
In the real world, patterns can be a lot harder to fix. If you are trying to make the tests pass for a pull request but can't fix the issue yourself, then make the pull request (or commit) anyway. A maintainer will help you.

Full pattern:
/([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F]([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.]*[-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀])?)?:(([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_:0-9]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])*([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])?)?/im

2) turtle
       should not cause polynomial backtracking:
     Error: turtle/[1]/begin: Polynomial backtracking. By repeating any character that matches /:/i, an attack string can be created.

    [-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.]*[-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀])?)?:([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_:0-9]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])*
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Full pattern:
/\^\^([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F]([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.]*[-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀])?)?:([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_:0-9]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])*([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])?/im
                                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

turtle/[4]/begin: Polynomial backtracking. By repeating any character that matches /:/i, an attack string can be created.

    [-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.]*[-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀])?)?:(([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_:0-9]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])*
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Full pattern:
/([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F]([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.]*[-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀])?)?:(([A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_:0-9]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀.:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])*([-A-Za-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿-⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�က0-F_0-9·̀-ͯ‿-⁀:]|%[0-9A-Fa-f][0-9A-Fa-f]|\\[_~.!$&'()*+,;=/?#@%-])?)?/im
                                                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I'll try to briefly explain in my own words, but you may need to turn to Google and read up on disjoined expressions and polynomial and exponential backtracking.  It can be complex.   The help that's outputted is actually pretty good...
You're trying to avoid things like:
(a+)(a+)F

a (one or many times) followed by a one or many times, then f...
In this case there are only 20 options though, so that's not so bad... but now take something like:
(a+)*F

Again given:
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaX

Now, yikes... there are 2^20 different ways this could match... it could match (a)(a)(a).... (aaaaaa)(aaaaaa)(aaaaaa) (a)(aa)(aaa) and every possible combo you can imagine... and it will try them ALL, always looking for the F that it will never find.  If the string was instead aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaF it would match crazy fast, cause whatever it tried first would match... this is why these regex are so dangerous... because often you're writing them to match... and not thinking about what happens if they FAIL to match - or just run across the wrong text content purely by accident.

The simplest advice I can give is to try to make sure that your regex always matches unambiguously... that each segment is "disjoint"... that the regex engine only has one way it can pattern match - and that was is always forward (never needing to backtrack)...

I'm struggling to even map these back to where they appear in the turtle grammar.

It tells you:
turtle/[4]/begin:

The 5th (4+1, 0 index) mode in the turtle grammar, in the begin regex...
    contains: [
      LANGTAG, // 0
      DATATYPE, // 1
      IRI_LITERAL, // 2
      BLANK_NODE, // 3
      PNAME, // 4

So PNAME is the culprit.

There are some great articles out there on this stuff... really we should find some and add them to the Wiki.


Filter user provided data in flask rest api

Provide strict filters on what is passed to the flask rest api to prevent malicious requests from making it to the plugins logic.

cases such as the below require filtering any javascript or html from the response:
toaster.pop({
type: 'success',
body: data.response.replace(/(?:\r\n|\r|\n)/g, ''),
showCloseButton: true,
bodyOutputType: 'trustedHtml',
});


upgrade to latest LSP

vscode compatiblity layer is introduced to make use of vscode-languageclient directly instead of vscode-base-languageclient

Please review.

I've finished the implementation of VS Code compatibility layer with LSP and Monaco: https://github.com/TypeFox/monaco-languageclient/pull/89/files#diff-9b485517654cf1807a16cc585e670df4. This layer only implements APIs which are used by vscode-languageclient. Resolution of VS Code module should be adjusted by clients, for example with webpack: https://github.com/TypeFox/monaco-languageclient/pull/89/files#diff-9bb3de20ef60fb0751fb0025b2cd27ea
API-wise there are some minor breaking changes: https://github.com/TypeFox/monaco-languageclient/pull/89/files#diff-412ff84fa2527e608a8217ca35f1a30c Major change is the switch to ES6. vscode-languageclient is targeting it, so we either have to switch to ES6 or fork it again and compile down to ES5. I would like to go for ES6, since it supported by all latest browsers: https://kangax.github.io/compat-table/es6/. Clients can still transpile it to ES5 via webpack with babel-loader.
I've also added support of latest LSP features: https://github.com/TypeFox/monaco-languageclient/blob/1a8247cbac116071ffad283cdef99982a3a4cb7f/src/services.ts#L173-L176 They are implemented via Monaco as well, except folding. For folding first we have to upgade to latest Monaco. I will do it as a separate PR.

As the next step i am going to publish next version and test it with Theia.

@rcjsuen many thanks for trying it out

We've decided to keep vscode-base-languageclient as a vscode-languageclient transpiled to es5. As soon as https://github.com/Microsoft/vscode-languageserver-node/issues/382 is resolved, we can abandon vscode-base-languageclient completely.


Get-ChildItem -Recurse shouldn't quietly ignore -Include and -Exclude when -LiteralPath is used instead of -Path

Even without using wildcards, Get-ChildItem -Recurse allows matching items on every level of the target hierarchy, possibly filtered with -Include and -Exclude.
However, if you use -LiteralPath rather than the (implied) -Path parameter, -Include and -Exclude are quietly ignored:
If there's a good reason for this behavior (none that I'm aware of), then at the very least a warning about -Include / -Exclude  getting ignored should be issued, or a separate parameter set should prevent combining -LiteralPath with -Include / -Exclude.
Steps to reproduce
Get-ChildItem              $PSHOME -Recurse -Exclude *   # implies -Path $PSHOME
Get-ChildItem -LiteralPath $PSHOME -Recurse -Exclude *

Expected behavior
Both calls should yield no output, because all items should be excluded by virtue of -Exclude *.
Actual behavior
The 2nd command, due to -Exclude * getting ignored, outputs the entire subtree of $PSHOME.
Environment data

PowerShell Core v6.0.0-alpha (v6.0.0-alpha.18) on macOS 10.12.4
PowerShell Core v6.0.0-alpha (v6.0.0-alpha.18) on Microsoft Windows 10 Pro (64-bit; v10.0.14393)

This appears to be a regression from v5 (repros with v5.1)

This appears to be a regression from v5 (repros with v5.1)

From my observations, it worked as expected in PS v5 Preview. So something changed exactly in v5 Preview -> v5 RTM.


Is there a polyfill of MouseEvent?

Is there a polyfill of MouseEvent? Thanks.

Not currently. I googled and couldn't find anything.
What do you need a MouseEvent polyfill for?

I need to trigger/simulate mouse events (mousemove, mouseover, click) for unit testing my client side JS code.
I am currently using this code to address the cross browser compatibility (mainly IE).
I would like to drop this in favor of a library/module if already available, otherwise create one instead of copy pasting the same code across multiple repos.

We'd welcome it.  You can find our contribution guidelines at http://cdn.polyfill.io/v1/docs/contributing


Added Amazon Prime Home Page Clone

This is the PR for the issue Amazon Prime Home Page Clone #382
Kindly Review it
Thank you Sir

@gurjeetsinghvirdee Your requested changes are done sir, Kindly review them..
Thank You Sir


[Listbox]: Wrongly styled to fill content

Description
unlike other menu, listbox has a block flow and fully stretches filling the available space

Component(s) impacted
listbox
Browser
No response
Vivid Web Components version
3.0.0
Severity
Severity 3 = The problem is visible or noticeable to users but does not impede the usability or functionality. Affects minor functionality, has a workaround.
Application/website
null
CodeSandbox example
null
Steps to reproduce the issue (if applicable)
No response
Release date (if applicable)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

@yinonov @rachelbt I remember that we've decided this in the PR on purpose right?
It's like in other components, for example:
https://vivid.deno.dev/components/nav
https://vivid.deno.dev/components/accordion

not sure I fully understand. What is the desired behaviour?

@rachelbt this

Are you referring to the starch or the selected + hover bg colors?
In menu - it is inside popup that has width: fit-content.
here the author can control the with with the host or a wrapper element

any reason for them to stretch fully by default? why not align with other components?

any reason for them to stretch fully by default? why not align with other components?

@yinonov  It's the same in other components, for example:
vivid.deno.dev/components/nav
vivid.deno.dev/components/accordion

@AyalaBu What do you think?

@rinaok
In option, nav-item & menu (vertical in this case) there is absolutely no reason to fully stretch the component.
Please view the design in this folder:
https://www.figma.com/file/JJNgZvt1qf3ydYmOwbE3Jg/Vivid-UI-Kit---3.0-WIP?node-id=19097%3A80656&t=kxUDfOYQuYorXHv1-3
Also, the states are looking wrong:

Hover state should be neutral 50
Selected state should be neutral 100
Pressed state should be neutral 200

Disregard information that isn't relevant to the display flow and online size

@AyalaBu @yinonov Should we open a new issue about the states?

@rinaok @yinonov Perhaps it should be a separate issue since it's dealing with a different appearance criteria?

open a new issue please

@yinonov @rinaok Done:
https://github.com/Vonage/vivid-3/issues/925


Where there should be quotes, they are not visible in the documentation.

modified:   exampleSite/content/docs/look-and-feel/index.md
    modified:   exampleSite/content/docs/look-and-feel/index.zh-hans.md
modified:   exampleSite/content/docs/look-and-feel/index.zh-hant.md
modified:   i18n/ru.toml

Hello. :slightly_smiling_face:
While busy adding and changing the color of icons, I noticed some inaccuracies in the instructions and my own translation error.
I wrote a short post about icons that will give you an understanding of what I encountered: https://sudakov.spb.ru
Where there should be quotes, they are not visible in the documentation. The quotes must be exactly like this, otherwise it won’t work. At least when writing a menu with icons.

I don't know Russian, but I think I get your point, that issue is caused by the : symbol, which make YAML/TOML parsing failed.


Fix docs comments in utility folder

PR Summary
The PR contains only style changes outside codes. It does not aim to eliminate all style issues - only reduce their number and increase the CodeFactor usefulness.
Changes are distributed by commits to make it easier to review.

Add final dot in xml doc comments.
Start comments with capical letter.
Remove empty lines in xml doc comments.
Add new line at EOF.
Remove unneeded comments.
Some minor fixes.

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

I looked at some of the changes and my primary concern is that adding a period to the end of a  comment doesn't make it a sentence.  Many of the existing comments are just clauses and not complete sentences and adding the period addresses the CodeFactor rule, but makes the comment worse.  If we want to address those, we should have better comments that are complete sentences.

Unfortunately, most public comments are formal and do not do any benefits. We could remove them at all or replace them with a placeholder.
Can someone replace all these formal comments with useful ones? It seems not real. So we can just remove the noisy CodeFactor issues formally.

@dantraMSFT Your comments was addresed.

@iSazonov looking at some of the original comments in the code, they don't provide value other than get past the compiler error of not having a <summary/>.  It seems that we would eventually want good comments so that we can generate SDK docs from the code, but that is a non-trivial task to review all the comments and make them useful and complete sentences.  Perhaps we should defer that as a separate issue.

@dantraMSFT please take a look again.

@dantraMSFT Your comment was addressed.


Create bitdomains spec/whitepaper

I think we're at a point now in experimentation where I have a solid idea on the implementation and various trade-offs. Create a draft spec that captures these decisions.
It should include at least:

What is bitdomains, what are differences/similarities to other projects (focus on decentralization, security over speed)
the contracts involved and how they interact
how name resolution is performed
how transactions are formed
format/required fields/spec of individual boxes
profit sharing/developer revenue
user freedom vs UX trade offs (in regards to user owned boxes, UX means protecting users from mispending the bitdomains items they own and bricking their boxes)
tokens?
etc

UX: prevent users from making txs that brick their names but don't have extra checks for othee things
A balance between protecting the user and keeping contracts as simple as possible


Start UI

elm-ui has some useful starters, including a lazy image loader that could be investigated...

This is mostly done new exuding the modal and the map, so ..


Inconsistency (or unclear text) wrt. closing with an authenticated client.

The spec says:

If the other client is authenticated, the client SHALL send a 'close' message to the other client containing the close code 3001 (Protocol Error). Both clients SHALL terminate the connection to the server (normal close code).

Here I did read "normal close code" as "1000 Normal Closure".
But in the section for the 'close' message it also says:

A client who sends a 'close' message [..] The client SHALL also terminate the connection to the server with a close code of 1001 (Going Away) if the connection is still open.

Which mean on a protocol error we are supposed to close with 1000 based on the protocol error and 1001 based on sending a close message.
There is also:

A receiving client [..] The client SHALL also terminate the connection to the server (no specific close code) if the connection is still open.

Where I'm not sure if it means you should set no close code (which is possible) or if it means you can set any arbitrary close code.

We could read "normal close code" as "close as normally done by the close message", in which case it's not a inconsistency but just a bit unclear text.


Remove soup from PACKAGECONFIG only if ptest is not enabled

I am working to enable ostree in my yocto build using meta-updater.
I see a build issue related to ostree-ptest when ptest is enabled as part of the distro features. It seems like ostree-ptest has a dependency on ostree-trivial-httpd and it breaks on removing soup from PACKAGECONFIG.
This change is to remove soup only if ptest is not enabled.
Build, boot up and ota update are successful with this change.

Please update the first patch to include your signed-off-by and drop the second and the third, not needed.
Can you also change the commit message to be 'ostree: remove soup...', easier to identify that this change is specific to the ostree recipe.

Hi Ricardo,
Thanks for the comments. Made all the changes.

@quic-roshs minor thing, can you update your author line to have your name instead?
It is currently:
Author: quic-roshs<EMAIL_ADDRESS>

Done


WIP: Add name to user invite

Description

Checklist:

[ ] Have you documented your changes in the pull request description?
[ ] Does the change present any security considerations?
[ ] Is any gem functionality overloaded? Eg: Devise controller methods being overloaded.
[ ] Has acceptance criteria been tested by a peer?
[ ] Has the CHANGELOG been updated? (If change is worth telling users about.)

General testing (author)

[ ] Test without JavaScript
[ ] Test on small screen

Accessibility testing (author)

[ ] Works keyboard only
[ ] Tested with one screen reader
[ ] Zoom page to 400% - content still visible
[ ] Disable CSS - does content make sense and appear in a logical order?

Codecov Report

Merging #1699 (fb3ce00) into master (bcd1a83) will decrease coverage by 86.10%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #1699       +/-   ##
==========================================
- Coverage   89.72%   3.62%   -86.11%
==========================================
  Files         399     399
  Lines        8578   13077     +4499
  Branches     1241     224     -1017
==========================================
- Hits         7697     474     -7223
- Misses        701   12602    +11901
+ Partials      180       1      -179

Impacted Files
Coverage Δ

app/controllers/invitations_controller.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/forms/invite_user_to_team_form.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/services/invite_user_to_team.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/role.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/team.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/alert.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/contact.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/country.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/product.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/accident.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 359 more

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 bcd1a83...fb3ce00. Read the comment docs.


Logging in to IAM Role shows SSO Console label instead of IAM Console label

Extension Version
1.8.11
Description
When assuming an IAM Role the following happens:

SSO Login to the account the role is attached to
The header (and footer) color reflects that of the account signed into (and the label is updated)
The SwitchRole UI is shown and the Display name field gets populated with the name of the SSO account instead of IAM Role and gets submitted
Role is assumed, name of the SSO account is shown instead of that of the assumed role
No coloring is applied to the header/footer

I assumed the "IAM Console Label" would be used in this case, not the SSO Console Label.

Browsers
Chrome
OS
Linux

Thanks for the details! I fixed a bug where the SSO label format was applying for IAM roles.
Although, I wasn't able to reproduce the color part - the correct colors always appeared.


fullcalendar -> "verkürzte Darstellung"

In the fullCalendar template multiday events gets shows multiple times.
The Feature available on other calendar views "verkürzte Darstellung" is missing here.

PS: this happens only for dates added by "extended repetition"


Add provenance field docs for the GitHub hosted build

Fixes https://github.com/slsa-framework/slsa-github-generator/issues/166

Formatting this into a table was really difficult because of the embedded examples :/
Adding the release tag though

Formatting this into a table was really difficult because of the embedded examples :/

If you're talking about formatting the markdown text, formatting tools really help. I've found that https://prettier.io works pretty well.


We need have split method for text

We need to be able to split strings by some substrings

@Graur please assign me

@EugeneDar Maybe split? According to this: https://arxiv.org/pdf/2206.02585.pdf

@Graur I agree

@EugeneDar 2 puzzles #57, #58 are still not solved.

@EugeneDar 3 puzzles #58, #76, #77 are still not solved; solved: #57.

@EugeneDar 2 puzzles #58, #76 are still not solved; solved: #57, #77.

@EugeneDar the puzzle #58 is still not solved; solved: #57, #76, #77.

@EugeneDar the puzzle #138 is still not solved; solved: #57, #58, #76, #77.


Added Project Webhooks, Project Services slack, Project Tags and Project Commits

Added Project Webhooks, Service Slack, Project Tags and Project Commits

This is great work. I'll accept the merge request once the following is changed:

[ ] Markdown help instead of Command-based help
[ ] Singular names for functions

I think this is ready now.

[x] Markdown help instead of Command-based help
[x] Singular names for functions


[gfm mode] add emoji rule

notes:

the token regex allows for \w!?+- characters to be between the : markup. Since there's no emoji spec that I know of (and because e.g. markdown-it allows pretty much anything the user specifies), I chose this character set to both 1) cover the most common emojis 2) minimize probability the regex will match non-emoji text.
didn't add default .cm-emoji to codemirror.css to not bloat the file since gfm is the only mode right now to utilize it (added a note for users in the index.html)
:question:  not sure if to disable by default

closes https://github.com/codemirror/CodeMirror/issues/4858

the token regex allows for \w!?+- characters to be between the : markup. Since there's no emoji spec that I know of (and because e.g. markdown-it allows pretty much anything the user specifies), I chose this character set to both 1) cover the most common emojis 2) minimize probability the regex will match non-emoji text.

GitHub links to this cheat sheet. All emojis in there match [a-z_\d+-].

Yea, I'm aware of that -- not sure if that's really authoritative. I started with that regex but decided to include ?/! so it covers :?: etc. coz it seemed it might be common. I can revert.

Thank you! Merged as b11179d1f6e1a. I've added patch 4292c2ff1bad0, which changes the default token type to "builtin", so that regular themes will style these (token types in the markdown mode aren't terribly semantically-meaningful at the moment, because at the moment the widely themed set of types doesn't cover a lot of prose-specific types)


configuration files on other browsers than Chrome displayed as single line.

On my machine, (MacBook Air), all the configuration files for the DNSmasq plugin are displayed as single line, with safari (12.0.1) and Firefox (63.0.3).  (I've noticed this behaviour earlier but didn't write down the versions).
in firefox the errors are:
Source map error: request failed with status 404
Resource URL: http:///system/scripts/jquery/jquery.mobile-1.4.5.min.js
Source Map URL: jquery.mobile-1.4.5.min.map
Source map error: TypeError: NetworkError when attempting to fetch resource.
Resource URL: moz-extension://c47372a4-4b4f-1045-9b1d-54ad39bb11fa/browser-polyfill.min.js
Source Map URL: browser-polyfill.min.js.map
in safari the errors are:
Failed to load resource: the server responded with a status of 404 (Not Found) http:///system/scripts/jquery/jquery.mobile-1.4.5.min.map

Duplicate of https://github.com/Woersty/LoxBerry-Plugin-DNSmasq/issues/1
The other errors are Loxberry Core errors - not plugin errors.
Report here=> https://github.com/mschlenstedt/Loxberry/issues/

Please update to Pre-Release 2<IP_ADDRESS> using Autoupdate or manual install https://github.com/Woersty/LoxBerry-Plugin-DNSmasq/archive/v2<IP_ADDRESS>.zip

I have to disagree. I is a issue with the dnsmasq.html page. It uses a wrong stylesheet for textareas that google chrome is kind to, but safari and firefox aren't. I've created a pull-request


Rule conflicts between prettier and standard

Is there an existing issue for this?

[X] I have searched the existing issues

Are you using the latest Super-linter version available?

[X] I am using the latest Super-linter version.

[X] I can reproduce the issue running Super-linter using complete version identifier (example: vX.Y.Z), and not just with a partial one (example: vX)

[X] I am using the super-linter/super-linter action or container image, and not the deprecated github/super-linter action or container image.

Are you resonably sure that it's a Super-linter issue, and not an issue related to a tool that Super-linter runs?

[X] I think that this is a Super-linter issue.

Current Behavior
https://github.com/super-linter/super-linter/blob/c46346c7743f7ce191073a49d90a1fa7b3d11996/test/linters/javascript_prettier/javascript_good_1.js#L1
Prettier expects ours to use double-quoted strings and semicolons in javascript code.
https://github.com/super-linter/super-linter/blob/c46346c7743f7ce191073a49d90a1fa7b3d11996/test/linters/javascript_standard/javascript_good_1.js#L1
Standard expects ours to use single-quoted strings and no semicolons in javascript code.
These rules are in conflict.
As a result, if I fix javascript code using prettier, standard will fail, and if I fix it using standard, prettier will fail.
No matter what I do, I can't make the super-linter succeed.
Expected Behavior
I expect that either a rule that uses double-quote strings and semicolons or a rule that uses single quote  strings and no semicolons applies to prettier and standard.
Super-Linter version
v6.8.0

Super-linter configuration
https://github.com/dev-hato/hato-atama/blob/master/.github/workflows/super-linter.yml
---
name: super-linter
on:
  pull_request:
    branches: [master]
  merge_group:
  workflow_dispatch:
permissions:
  contents: read
  packages: read
  statuses: write
jobs:
  super-linter:
    runs-on: ubuntu-latest
    timeout-minutes: 30
    steps:
      - uses<EMAIL_ADDRESS>        with:
          fetch-depth: 0
      - uses<EMAIL_ADDRESS>        with:
          node-version-file: .node-version
          cache: npm
      - run: bash "${GITHUB_WORKSPACE}/scripts/super_linter/super_linter/set_path.sh"
      - name: Super-Linter
        uses<EMAIL_ADDRESS>        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          LINTER_RULES_PATH: .
          # Go modulesを使っているため、こちらはfalseにする
          VALIDATE_GO: false
concurrency:
  group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.ref }}
  cancel-in-progress: true

Relevant log output
Fix javascript code using standard
https://github.com/dev-hato/hato-atama/actions/runs/10228090683/job/28300251559 ( https://github.com/dev-hato/hato-atama/pull/4386/commits/896b3343cc9d85574be1c3f22a71620af4f1da6f )
JAVASCRIPT_PRETTIER
  2024-08-03 12:46:28 [INFO]   Linting JAVASCRIPT_PRETTIER items...
  Error: -03 12:46:30 [ERROR]   Found errors when linting JAVASCRIPT_PRETTIER. Exit code: 1.
  2024-08-03 12:46:30 [INFO]   Command output for JAVASCRIPT_PRETTIER:
  ------
  Checking formatting...
  ------
  2024-08-03 12:46:30 [INFO]   Stderr contents for JAVASCRIPT_PRETTIER:
  ------
  [warn] frontend/webpack.config.js
  [warn] scripts/fail_notify/fail_notify/get_slack_payload.js
  [warn] scripts/release/remove_app_engine_past_versions/get_run_numbers.js
  [warn] scripts/release/create_pr_environment/create_pr_environment.js
  [warn] scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js
  [warn] frontend/src/index.js
  [warn] test/e2e/cypress.config.js
  [warn] scripts/sleep.js
  [warn] test/e2e/cypress/e2e/all/mini_spec.cy.js
  [warn] test/e2e/cypress/e2e/mini/mini_spec.cy.js
  [warn] test/e2e/cypress/plugins/index.js
  [warn] test/e2e/cypress/support/e2e.js
  [warn] Code style issues found in 12 files. Run Prettier with --write to fix.
  ------

Fix javascript code using prettier
https://github.com/dev-hato/hato-atama/actions/runs/10228336907/job/28300745924 ( https://github.com/dev-hato/hato-atama/pull/4386/commits/88b4bdca630f7fb6a5d376fb4cfd6be946442319 )

JAVASCRIPT_STANDARD
  2024-08-03 13:20:50 [INFO]   Linting JAVASCRIPT_STANDARD items...
  Error: -03 13:21:02 [ERROR]   Found errors when linting JAVASCRIPT_STANDARD. Exit code: 1.
  2024-08-03 13:21:02 [INFO]   Command output for JAVASCRIPT_STANDARD:
  ------
    /github/workspace/frontend/webpack.config.js:1:35: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:1:57: Extra semicolon. (semi)
    /github/workspace/frontend/webpack.config.js:2:28: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:2:50: Extra semicolon. (semi)
    /github/workspace/frontend/webpack.config.js:3:40: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:3:63: Extra semicolon. (semi)
    /github/workspace/frontend/webpack.config.js:4:22: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:4:29: Extra semicolon. (semi)
    /github/workspace/frontend/webpack.config.js:12:17: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:12:30: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:20:21: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:22:29: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:23:14: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:24:12: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:25:10: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:26:8: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:27:6: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:30:35: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:31:15: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:31:39: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:34:41: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:34:56: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:35:39: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:36:29: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:40:11: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:43:7: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:43:16: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:44:7: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:44:14: Strings must use singlequote. (quotes)
    /github/workspace/frontend/webpack.config.js:44:49: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:45:6: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:46:4: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/webpack.config.js:47:2: Extra semicolon. (semi)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:3:12: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:6:16: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:8:20: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:9:8: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:10:6: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:11:4: Extra semicolon. (semi)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:17:66: Extra semicolon. (semi)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:21:8: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:21:13: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:22:8: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:22:13: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:23:8: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:23:13: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:23:20: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:25:77: Extra semicolon. (semi)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:29:26: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:29:40: Extra semicolon. (semi)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:33:106: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:35:15: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:35:20: Extra semicolon. (semi)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:37:26: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:37:32: Extra semicolon. (semi)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:38:155: Extra semicolon. (semi)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:43:11: Strings must use singlequote. (quotes)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:44:30: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:45:5: Extra semicolon. (semi)
    /github/workspace/scripts/fail_notify/fail_notify/get_slack_payload.js:46:2: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:1:23: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:1:40: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:4:40: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:7:28: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:8:4: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:9:19: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:9:28: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:10:24: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:11:13: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:14:17: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:14:65: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:17:19: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:18:6: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:19:52: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:19:62: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:25:26: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:26:10: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:27:21: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:27:54: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:28:44: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:31:33: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:32:10: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:33:73: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:35:28: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:36:27: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:39:36: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:40:11: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:41:9: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:42:6: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:43:47: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:44:25: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:45:65: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:49:20: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:49:46: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:52:22: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:52:26: Extra semicolon. (semi)
    /github/workspace/scripts/release/remove_app_engine_past_versions/get_run_numbers.js:53:2: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:2:32: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:2:42: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:3:64: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:4:55: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:5:67: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:6:11: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:6:45: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:7:11: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:7:57: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:8:11: Strings must use singlequote. (quotes)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:8:52: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:9:40: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:10:43: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:15:9: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:16:5: Extra semicolon. (semi)
    /github/workspace/scripts/release/create_pr_environment/create_pr_environment.js:17:2: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:1:23: Strings must use singlequote. (quotes)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:1:40: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:4:40: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:5:78: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:6:19: Strings must use singlequote. (quotes)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:6:28: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:7:24: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:8:13: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:11:17: Strings must use singlequote. (quotes)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:11:65: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:14:19: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:15:6: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:16:52: Strings must use singlequote. (quotes)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:16:62: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:22:26: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:23:10: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:24:21: Strings must use singlequote. (quotes)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:24:54: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:25:44: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:28:33: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:29:10: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:31:30: Strings must use singlequote. (quotes)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:32:27: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:35:38: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:36:11: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:37:9: Unexpected trailing comma. (comma-dangle)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:38:6: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:39:47: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:40:65: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:44:20: Strings must use singlequote. (quotes)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:44:46: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:47:22: Strings must use singlequote. (quotes)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:47:26: Extra semicolon. (semi)
    /github/workspace/scripts/remove_app_engine_versions/remove_app_engine_versions/get_run_numbers.js:48:2: Extra semicolon. (semi)
    /github/workspace/frontend/src/index.js:1:1: Strings must use singlequote. (quotes)
    /github/workspace/frontend/src/index.js:1:13: Extra semicolon. (semi)
    /github/workspace/frontend/src/index.js:3:8: Strings must use singlequote. (quotes)
    /github/workspace/frontend/src/index.js:3:22: Extra semicolon. (semi)
    /github/workspace/frontend/src/index.js:4:21: Strings must use singlequote. (quotes)
    /github/workspace/frontend/src/index.js:4:33: Extra semicolon. (semi)
    /github/workspace/frontend/src/index.js:7:33: Strings must use singlequote. (quotes)
    /github/workspace/frontend/src/index.js:7:40: Unexpected trailing comma. (comma-dangle)
    /github/workspace/frontend/src/index.js:8:3: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress.config.js:1:34: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress.config.js:1:44: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress.config.js:3:43: Extra semicolon. (semi)
    /github/workspace/scripts/sleep.js:3:11: Extra semicolon. (semi)
    /github/workspace/scripts/sleep.js:9:66: Extra semicolon. (semi)
    /github/workspace/scripts/sleep.js:10:40: Extra semicolon. (semi)
    /github/workspace/scripts/sleep.js:11:75: Extra semicolon. (semi)
    /github/workspace/scripts/sleep.js:12:2: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:3:10: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:4:6: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:5:33: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:5:44: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:7:22: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:9:12: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:9:37: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:11:12: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:11:29: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:13:12: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:14:15: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:14:28: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:16:30: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:17:45: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:18:11: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:19:30: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:20:45: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:21:11: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:22:30: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:23:45: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:24:11: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:25:30: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:27:47: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:28:12: Unexpected trailing comma. (comma-dangle)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:29:10: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:30:9: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:31:5: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/all/mini_spec.cy.js:32:3: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:3:10: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:4:6: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:5:33: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:5:44: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:7:22: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:9:12: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:9:37: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:11:12: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:11:29: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:13:12: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:14:15: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:14:28: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:16:30: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:17:45: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:18:11: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:19:30: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:20:45: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:21:11: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:22:30: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:23:45: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:24:11: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:25:30: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:27:47: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:28:12: Unexpected trailing comma. (comma-dangle)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:29:10: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:30:9: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:31:5: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/e2e/mini/mini_spec.cy.js:32:3: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/plugins/index.js:21:2: Extra semicolon. (semi)
    /github/workspace/test/e2e/cypress/support/e2e.js:17:8: Strings must use singlequote. (quotes)
    /github/workspace/test/e2e/cypress/support/e2e.js:17:20: Extra semicolon. (semi)
  ------
  2024-08-03 13:21:03 [INFO]   Stderr contents for JAVASCRIPT_STANDARD:
  ------
  standard: Use JavaScript Standard Style (https://standardjs.com/)
  standard: Run `standard --fix` to automatically fix some problems.

Steps To Reproduce
https://github.com/dev-hato/hato-atama/pull/4386

I fix javascript code using standard (and prettier fails): https://github.com/dev-hato/hato-atama/pull/4386/commits/896b3343cc9d85574be1c3f22a71620af4f1da6f
I fix it using prettier (and standard fails): https://github.com/dev-hato/hato-atama/pull/4386/commits/88b4bdca630f7fb6a5d376fb4cfd6be946442319

Anything else?
No response

Hi @massongit !
I suppose this is expected. We don't need to pick a style for test cases because the test case logic already handle this.
As you can see from your log, Prettier is going to lint only files in the test/linters/javascript_prettier/{good,bad} directory, while Standard is going to lint files test/linters/javascript_standard/{good,bad}.
What you're doing in https://github.com/massongit/super-linter/pull/77 is going to cause this error because you're asking Prettier to check a file something that doesn't match with the expected formatting. So, files in test/linters/javascript_standard/good should be formatted as Standard requires, while files test/linters/javascript_prettier/good should be formatted as Prettier requires. We don't have to pick a formatting for those files because they are test cases, so we need them to differ.

@ferrarimarco I update issue description.
What I want to say is that if I fix javascript code using prettier, standard will fail, and if I fix it using standard, prettier will fail.
No matter what I do, I can't make the super-linter succeed.

Ah, I thought you were talking about the Super-linter repository in particular.
This might be a duplicated of #5954 then.

https://github.com/super-linter/super-linter/issues/5954#issuecomment-2266651939

I suggest disabling either Standard, or Prettier, depending on which one you prefer.

Sorry, I overlooked https://github.com/super-linter/super-linter/issues/5954.
I am satisfied with the above answer in https://github.com/super-linter/super-linter/issues/5954, so I will close this issue.

No worries :)


In the current state of the PR, It basically covers every test relying on the modules test repo with its public GitLab equivalent
This won't work as is for bitbucket (because of a different valid HTMLURL), and tests will probably need to be extended to not dumbly fail over refs with .git (which work), but this is not handled properly at the moment
This relies on a mirror of dagger-module-tests:

gitlab.com/dagger-modules/test/more/dagger-test-modules-public (auto-sync to-be-done)
bitbucket incoming

cc @jedevc, I realized at the same time that the current HTMLURL() implementation does not handle bitbucket's URL format.

We currently build it as such: u := "https://" + src.Root + "/tree/" + src.Commit, but a real bitbucket example would be: https://bitbucket.org/test-travail/test/commits/b17a8e871052f7d14dbb198b7071986f997ab7a8.

I still wonder what is the best implementation: shall we store the corresponding VCS as part of the gitmodulesource ? As the HTMLURL seems resolved from the gitsource, I don't think we will have access to this information ?

Both failing tests are due to flakiness


1.5 enhancement

Coverage remained the same at 77.188% when pulling fe808619a584a3c17ddd9909f829d88a8e64430f on ZhangH795:1.5_Enhancement into f799bc712042082d4c1e85231cb4736120809739 on CS2103AUG2017-W09-B3:master.


pool: add gominer support.

Depends on #320
This adds the decred gominer as a supported mining client.
Work towards #316.

Closing this since it most definitely won't work as of the latest changes to gominer.


config,sshPort not used

Trying to connect to a remote RethinkDB server on Compose.io. Compose gives a specific port to connect to the ssh server. In a bash command like<EMAIL_ADDRESS>-p XXXXX. I thought I could use the sshPort config variable like this
uiConfig =
  privateKey: key
  username: username
  sshPort: sshPort
  host: host
  srcHost: composeConfig.ip
  srcPort: composeConfig.uiPort
  dstPort: localConfig.uiPort
  dstHost: localConfig.ip
  keepAlive: true
uiTunnel = tunnel uiConfig, (e, uiTunnel)->
  if e
    console.log 'TUNNEL ERROR >>>>', e.message
  else
    console.log 'UI TUNNEL CONNECTED'

When the server connects I get
Error: getaddrinfo ENOTFOUND<EMAIL_ADDRESS>compose@cloudserver.com:22
Is this because config.sshPort is defaulting to port 22?

You need to remove the username from the hostname. (getaddrinfo => hostname can't be resolved)
The sshPort is working, but you are right about the error message ... it shows port 22 even if another port is used,  i'll report the error to the ssh2 lib.


[Event Request] Application “Tests-Workflow” Codeunit 134204 "Document Approval - Requests"

[Event Request] Application “Tests-Workflow”, 134204 "Document Approval - Requests"
Could you please insert the OnTestInitialize Event at the beginning of Initialize procedure:

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Update CT Search request

🗣 Description

I updated the CT Search API request to expand the new cert_der field.

💭 Motivation and context

According to the SSLMate Changelog, on January 3rd 2023 the cert object was deprecated. You now use cert_der to retrieve certificate data.

Resolves #51

🧪 Testing

I verified that our tasks still function as expected with the changes in place. To test, I performed a dry run and monitored progress from the Celery Flower dashboard. The summary_by_domain task returned results with cert_der expanded, and the cert_by_issuance task returned the base64 representation of the DER-encoded certificate. I stopped the dry run after approximately 10 domains had been scanned.

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[ ] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

@king-alexander - The linter failure should go away once the current Kraken flows down to this repository.

@king-alexander You should mention something in this PR about why version 1.3.4 will not be built after this PR was merged.


Fix "not found" error on fresh install

The login command at the end of the script was running without the CLI being in $PATH.
I also fixed the shell detection for Zsh ($SHELL is not always reliable).
I could not get the script to work in fish.

Thanks for the fix @nasso!


does it have support for FMOD dsp Plugins?

So, the question on the title :)
Can you add to the library and easily use plugins for FMOD?
Specificically how hard is implement with the lib spatial audio, using plugins like oculus spatialicer, steam audio or resonance audio by google.
A few days ago, I got to use the regular FMOD headers for c# with resonance audio in a small monogame test project, but of course bot are separated libs, and aren't integrated one into the other, like your pluging does, incorporing fmod with the content pipeline of monogame and other awesome stuff.
So... can you do that in the current state of the lib? :P
thanks!

If I'll ever need them -- I will implement that into the library. But for now -- it is what it is.
My main priority is making a game, so spreading my time on the thing I may not even need is no good for me.
And, you know, the native library loading code is all here for you, so you could try doing that yourself. ; - )


feat: increase the body size limit for resume update

Description
Found some error logs in ppresume server:
ppresume-api-1  | [09:07:27] ERROR (payload): PayloadTooLargeError: request entity too large
ppresume-api-1  |     at readStream (/app/node_modules/.pnpm/raw-body@2.5.1/node_modules/raw-body/index.js:156:17)
ppresume-api-1  |     at getRawBody (/app/node_modules/.pnpm/raw-body@2.5.1/node_modules/raw-body/index.js:109:12)
ppresume-api-1  |     at read (/app/node_modules/.pnpm/body-parser@1.20.1/node_modules/body-parser/lib/read.js:79:3)
ppresume-api-1  |     at jsonParser (/app/node_modules/.pnpm/body-parser@1.20.1/node_modules/body-parser/lib/types/json.js:135:5)
ppresume-api-1  |     at Layer.handle [as handle_request] (/app/node_modules/.pnpm/express@4.18.2/node_modules/express/lib/router/layer.js:95:5)
ppresume-api-1  |     at trim_prefix (/app/node_modules/.pnpm/express@4.18.2/node_modules/express/lib/router/index.js:328:13)
ppresume-api-1  |     at /app/node_modules/.pnpm/express@4.18.2/node_modules/express/lib/router/index.js:286:9
ppresume-api-1  |     at Function.process_params (/app/node_modules/.pnpm/express@4.18.2/node_modules/express/lib/router/index.js:346:12)
ppresume-api-1  |     at next (/app/node_modules/.pnpm/express@4.18.2/node_modules/express/lib/router/index.js:280:10)
ppresume-api-1  |     at middleware (/app/node_modules/.pnpm/payload@2.5.0_esbuild@0.18.20_typescript@4.9.5_webpack@5.89.0/node_modules/payload/dist/localization/middleware.js:46:16)

By default, express apply a 100kb limit for body parser: https://expressjs.com/en/resources/middleware/body-parser.html.
We can relax this limit for some MB. I will take 10 MB as the limit here, which is 100x larger than the default—can't believe anybody's resume would have more than 10MB in plain text.
[Optional] Possible Solutions
NA
Acceptance Criteria

relax the size limit of body parser from 10 KB to 10 MB.

Todo list
NA

Fixed.


Refactor /benchmark pr

On triggering /benchmark pr, prometheus-master will be deployed as it is.
prometheus-pr will be deployed as follows:

prombench image will be used in the container with args make start-pr
PR will be cloned & prometheus binaries will be built using promu
./prometheus will be executed to start prometheus-pr

GCS is no longer needed in prow because decorate:true is not used anymore.

Closed by #66


Update TAB mc.theflyingbirds.net so that colours are matching and consistent.

As a Developer, I want to update TAB view so that colours are matching and more consistent.
Currently the colours, are different and not matching + mc and .net are still boring grey colours.

I can understand the IP part but I don't understand whats meant with "matching and consistent colors"?


Panic when creating new container with affinity

I got the following panic when I attempted to create a new container using the API with different affinities specified.
2015/12/11 22:01:25 http: panic serving <IP_ADDRESS>:63859: runtime error: index out of range
goroutine 731 [running]:
net/http.(*conn).serve.func1(0xc8200900b0, 0x7f5d96971030, 0xc820134190)
	/usr/local/go/src/net/http/server.go:1287 +0xb5
github.com/docker/swarm/scheduler/filter.(*AffinityFilter).Filter(0x130efe8, 0xc820788400, 0xc820337be0, 0x3, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0)
	/go/src/github.com/docker/swarm/scheduler/filter/affinity.go:37 +0x1365
github.com/docker/swarm/scheduler/filter.ApplyFilters(0xc820074a00, 0x5, 0x8, 0xc820788400, 0xc820337be0, 0x3, 0x4, 0x0, 0x0, 0x0, ...)
	/go/src/github.com/docker/swarm/scheduler/filter/filter.go:61 +0x12d
github.com/docker/swarm/scheduler.(*Scheduler).SelectNodesForContainer(0xc8200f62d0, 0xc820337b20, 0x3, 0x3, 0xc820788400, 0x0, 0x0, 0x0, 0x0, 0x0)
	/go/src/github.com/docker/swarm/scheduler/scheduler.go:37 +0xb3
github.com/docker/swarm/cluster/swarm.(*Cluster).createContainer(0xc82000b340, 0xc820788400, 0xc82074281d, 0x1a, 0x0, 0x0, 0x0, 0x0)
	/go/src/github.com/docker/swarm/cluster/swarm/cluster.go:153 +0x417
github.com/docker/swarm/cluster/swarm.(*Cluster).CreateContainer(0xc82000b340, 0xc820788400, 0xc82074281d, 0x1a, 0x0, 0x0, 0x0)
	/go/src/github.com/docker/swarm/cluster/swarm/cluster.go:119 +0x60
github.com/docker/swarm/api.postContainersCreate(0xc8200eb900, 0x7f5d969c3418, 0xc820090a50, 0xc8200d6460)
	/go/src/github.com/docker/swarm/api/handlers.go:430 +0x2d2
github.com/docker/swarm/api.setupPrimaryRouter.func1(0x7f5d969c3418, 0xc820090a50, 0xc8200d6460)
	/go/src/github.com/docker/swarm/api/primary.go:151 +0x303
net/http.HandlerFunc.ServeHTTP(0xc8201ff7e0, 0x7f5d969c3418, 0xc820090a50, 0xc8200d6460)
	/usr/local/go/src/net/http/server.go:1422 +0x3a
github.com/gorilla/mux.(*Router).ServeHTTP(0xc82000eeb0, 0x7f5d969c3418, 0xc820090a50, 0xc8200d6460)
	/go/src/github.com/docker/swarm/Godeps/_workspace/src/github.com/gorilla/mux/mux.go:98 +0x29e
github.com/docker/swarm/api.(*dispatcher).ServeHTTP(0xc8200ed620, 0x7f5d969c3418, 0xc820090a50, 0xc8200d6460)
	/go/src/github.com/docker/swarm/api/server.go:32 +0x9f
net/http.serverHandler.ServeHTTP(0xc820316e40, 0x7f5d969c3418, 0xc820090a50, 0xc8200d6460)
	/usr/local/go/src/net/http/server.go:1862 +0x19e
net/http.(*conn).serve(0xc8200900b0)
	/usr/local/go/src/net/http/server.go:1361 +0xbee
created by net/http.(*Server).Serve
	/usr/local/go/src/net/http/server.go:1910 +0x3f6

Version Info:
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:12:04 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      swarm/1.0.1
 API version:  1.21
 Go version:   go1.5.2
 Git commit:   744e3a3
 Built:
 OS/Arch:      linux/amd64

The container I was trying to start had the following affinities specified:
constraint:pod==aws-us-east-1e-pod-01
affinity:container!=mongo_SwarmMongo12_Secondary
affinity:container!=mongo_SwarmMongo12_Arbiter

The containers mongo_SwarmMongo12_Secondary and mongo_SwarmMongo12_Arbiter were not created yet.  And the swarm hosts have the label aws-us-east-1e-pod-01 specified.

@chosenken Thanks for reporting the issue! It looks similar to #1421.

@dongluochen You may be right, I just checked and my swarm does indead of a "Dead" container.  Once I removed the dead container and restarted the swarm_master daemon I was able to create my containers again.

@chosenken I think swarm should fix the crash issue here.

@dongluochen Yes, swarm does need to be able to handle dead containers when filtering on affinity/constraints.  The work around for now is to get rid of the dead containers, but if this was a production box I wouldn't be able to restart the docker daemon, so swarm would have to handle it.


Move ShowExtensionSurveyPrompt experiment to ExP

For #15530
Note that we explicitly don't migrate people who opted in/out of the old experiment.

Codecov Report

Merging #15693 (65ef168) into main (c7fea18) will decrease coverage by 0%.
The diff coverage is 100%.

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

@@          Coverage Diff           @@
##            main   #15693   +/-   ##
======================================
- Coverage     64%      64%   -1%
======================================
  Files        557      557
  Lines      26814    26812    -2
  Branches    3901     3901
======================================
- Hits       17366    17364    -2
  Misses      8714     8714
  Partials     734      734

Impacted Files
Coverage Δ

src/client/activation/extensionSurvey.ts
95% <100%> (-1%)
:arrow_down:

src/client/common/experiments/groups.ts
100% <100%> (ø)

src/client/common/experiments/manager.ts
85% <100%> (ø)


APEXCORE-619 Checkpoint leaf stateless operator for correct recovery after application restart.

Purging of checkpoints skips the stateless operators, so please check that purging is happening correctly.

our check-style rules fails the build for empty block, hence kept it as it is.

purging checkpoint is working as LeafStatelessStorageAgent is extended from FSStatelessStorageAgent

@tushargosavi It's been a while so can you rebase and I can look into it

@tushargosavi @PramodSSImmaneni closed due to inactivity.


Importing the getDiscordSecrets function results in 13 MB JS bundle

Really appreciate the fixes you've made in the last hours 👍
However, there seems to be an issue with the tree shaking I assume.
Importing from
import { getDiscordSecrets } from "discord-bot-cdk-construct";
results in a 13 MB big lambda file.
Changing the import to
import { getDiscordSecrets } from "discord-bot-cdk-construct/dist/functions/utils/DiscordSecrets";
workarounds the problem.
I've noticed your oculus-start-bot still relies on a local version of the function, too, so this might went under your radar.

Hmm... I don't seem to be able to reproduce this? I don't believe this should be caused by include the Discord secrets, as even the DiscordBotFunction's Lambda is fairly small (17.1kB for me). Can you post your Lambda code that you're seeing this issue with?
I saw you removed another reference to the oculus-start-bot, appreciate that! That's my main test playground atm, so yeah, a few references were from there :sweat_smile:

I'll prepare a minimum reproducible repository for you to test 👍

Here you go:
https://github.com/timbru31/DiscordBotCDKConstructIssue4
I've basically made an empty skeleton with cdk init and added the example lambda function from the README. (https://github.com/timbru31/DiscordBotCDKConstructIssue4/blob/master/lib/functions/lambda.ts).
If you do an npm i && cdk synth you should notice that the CommandsLambda is way too big.

Not 100% sure but this might be caused by depending on axios? (see https://github.com/GEMISIS/discord-bot-cdk-construct/blob/e2aa772ff23396676edbed4ac8fe31920dbad34c/package.json#L74)
Probably the construct itself doesn't need this dependency anyways?!

So I'm still not able to reproduce this, even with your repo as shown.

This sounds like something odd in your setup specifically? Are you on the latest CDK CLI version? Also, you've built the package with npm run build beforehand right? Nothing weird like that causing issues?

You were able to reproduce it! 🎉
The zip is half a megabyte and I bet if you unpack it, it will be around 3mb

CDK is at 1.104.0 (build 44d3383), Node.js v14.16.1

Gotcha, okay, you'd mentioned this was 13MB, but 3MB is different and a bit more acceptable for something like this right now (axios seems like it might be a likely candidate, as it's only blowing up the size of the commands lambda, not the discord one). I've updated the title of this to accurately reflect this and will take a look, though this isn't super high priority, as I'm sure that there's some


fails to load stories below project root

Describe the bug
When defining match storyMatch below the root directory of the histoire project, in for example a monorepo, build and dev will throw an error of "Failed to load url.".
Reproduction
Create a project with this folder structure:
├── apps
|  └── test
|     ├── histoire.config.ts
|     └── package.json
├── package.json
├── pnpm-lock.yaml
├── pnpm-workspace.yaml
└── stories
   └── Test.story.vue

histoire installed in apps/test with:
pnpm i -D histoire @histoire/plugin-vue
with this apps/test/histoire.config.ts:
import { defineConfig } from "histoire";
import { HstVue } from "@histoire/plugin-vue";

export default defineConfig({
  plugins: [HstVue()],
  storyMatch: ["../../stories/*.story.vue"],
});

and stories/Test.story.vue:
<template>
  <Story title="🐱 Meow"> 🐱 </Story>
</template>

Then after running pnpm story:dev in apps/test it will throw:
Error while collecting story /Users/tihav/src/atrium-ui/atrium-ui-mono/stories/Test.story.vue:
Error: [vite-node] Failed to load /Users/tihav/src/atrium-ui/atrium-ui-mono/stories/Test.story.vue
    at ViteNodeRunner.directRequest (file:///Users/tihav/src/atrium-ui/atrium-ui-mono/node_modules/.pnpm/vite-node@0.23.4/node_modules/vite-node/dist/client.mjs:180:13)
    at async ViteNodeRunner.cachedRequest (file:///Users/tihav/src/atrium-ui/atrium-ui-mono/node_modules/.pnpm/vite-node@0.23.4/node_modules/vite-node/dist/client.mjs:128:12)
    at async request (file:///Users/tihav/src/atrium-ui/atrium-ui-mono/node_modules/.pnpm/vite-node@0.23.4/node_modules/vite-node/dist/client.mjs:151:16)
    at async v (/Users/tihav/src/atrium-ui/atrium-ui-mono/node_modules/.pnpm/@histoire+plugin-vue@0.11.9_vgxee6juai2ux6n5oucjlvgv4a/node_modules/@histoire/plugin-vue/dist/bundled/client/server/run.js:12:26)
    at async run (/Users/tihav/src/atrium-ui/atrium-ui-mono/node_modules/.pnpm/histoire@0.11.9_vite@3.2.5/node_modules/histoire/dist/node/collect/run.js:6:20)
    at async default (file:///Users/tihav/src/atrium-ui/atrium-ui-mono/node_modules/.pnpm/histoire@0.11.9_vite@3.2.5/node_modules/histoire/dist/node/collect/worker.js:41:5)
    at async file:///Users/tihav/src/atrium-ui/atrium-ui-mono/node_modules/.pnpm/tinypool@0.1.3/node_modules/tinypool/dist/esm/worker.js:96:20

System Info
System:
    OS: macOS 13.0.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 724.16 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 17.9.0 - ~/.nvm/versions/node/v17.9.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v17.9.0/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v17.9.0/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 108.0.5359.124
    Chrome Canary: 110.0.5481.3
    Firefox: 106.0.5
    Safari: 16.1
    Safari Technology Preview: 16.4
  npmPackages:
    @histoire/plugin-vue: ^0.11.9 => 0.11.9
    @vitejs/plugin-vue: ^4.0.0 => 4.0.0
    histoire: ^0.11.9 => 0.11.9
    vite: ^4.0.1 => 4.0.1

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

@serkodev Sure thing! Im not sure why I didn't post it here, sry.
For me it was a vite problem.
I needed to allow vite to access the files below its root like this:
export default defineConfig({
  ...
  server: {
    fs: {
      allow: ["../../"]
    }
  },
  ...
})

@luckydye Thanks! I used your solution to solve my problem.


fix: don't execute new shell when passing --dry-run to install.sh script

Don't execute a new shell when passing the dry run option to the install.sh script.
https://github.com/nyoungstudios/alfa/blob/2bd377b90aa86850ab11687089a9a2e8ec9757db/install.sh#L92-L96

fixed by this commit: https://github.com/nyoungstudios/alfa/commit/426dd7bb684da364193f3515edc6a6e0c4a33646


Add main encoding detection functions

I had wrapped some functions to convert from one encoding to another, and then I realized you had just done the same a few days ago. ;-) So I went on and wrote wrappers for encoding detection functions, which seem to work relatively well in the few tests I did.
Something I'm not sure I did right is what to do when ucsdet_detect returns NULL. I could return C_NULL or nothing, which would break type stability. So for now I return an object with a null pointer, and I handle this in ucsdet_getName, by returning an empty encoding name.

Bump! I have rebased this old branch.

Could this be merged?  We have a need for it also.  Thanks!

Re-bump!

You might want to use https://github.com/JuliaString/ICU.jl instead, which supports the character detection API, fixes a bunch of errors with leaking memory (by adding finalizers and keeping a pointer to the other Julia object to prevent premature GC), and is tested (I am working on getting it to 100% coverage)

Ah, cool. I guess it would make sense to redirect to your fork and register it in METADATA if you plan to maintain it in the future?

Yes, that's what I was hoping for. I never did hear back from @nolta about that. If you get a chance, I'd love your comments on it, constructive criticism is very very much appreciated!


MEV_RELAYS can now be multi-line

This is a fairly big change to enable one thing: Multi-line values in .env. There is one user that has their MEV_RELAYS as multi-line, and we kept breaking their .env whenever the version of the template changed.
Not touching the config workflow deeply, but that could be next - it'd make a lot of sense to re-use the Lido CSM config flow for all MEV_RELAYS purposes, or at least when MEV_RELAYS has not been set by the user, and construct multi-line during config.
That'd be a separate PR

I am merging this without review, so I can increment the .env version for the ssvlabs repo changeover. Without this, I'll break the setup of the one user that has a multi-line value :/
The awk code is GPT-generated. A review is still welcome, we may want to tighten / improve it


Add new section above "Download AKS Base Images" titled "Download Required VM Extensions"

Add new section above "Download AKS Base Images" titled "Download Required VM Extensions"
Here is the document with the content: https://microsoft-my.sharepoint-df.com/:w:/p/waltero/EUnUiBaGfExCmQZZ87b9BzcBLgeFl-ZqBST9Eh0l28MqEg?e=dn1RvD

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

ID: 5161bfe9-b400-e18f-0119-5d1c5a50abb4
Version Independent ID: a3ddc8f7-bdb6-e6a7-097d-b0e405ee3e82
Content: Install and offer the Azure Kubernetes Service on Azure Stack Hub - Azure Stack Hub
Content Source: azure-stack/operator/aks-add-on.md
Service: azure-stack
Sub-service: azure-stack-hub
GitHub Login: @mattbriggs
Microsoft Alias: mabrigg

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

#in-progress

#please-close


[Bug]: Poetry install fails

Describe the bug
After running pip install poetry:
abrichr@MacBook-Pro-3 OpenAdapt % poetry install

dyld[41834]: Library not loaded<EMAIL_ADDRESS>  Referenced from: <1E0708EA-DAC7-3EED-9755-EE85F923CB77> /Users/abrichr/Library/Application Support/pypoetry/venv/bin/python
  Reason: tried<EMAIL_ADDRESS>(no such file<EMAIL_ADDRESS>(no such file<EMAIL_ADDRESS>(no such file), '/Library/Frameworks/Python.framework/Versions/3.10/Python' (no such file), '/System/Library/Frameworks/Python.framework/Versions/3.10/Python' (no such file, not in dyld cache)
zsh: abort      poetry install

To Reproduce
Follow installation instructions in README:
git clone https://github.com/MLDSAI/OpenAdapt.git
cd OpenAdapt
pip install poetry
poetry install

Attempted workaround:
pip uninstall poetry
python3.10 -m pip install poetry
poetry install

Same error.

Fix, from https://stackoverflow.com/a/73654972/95989:
curl -sSL https://install.python-poetry.org | python3 - --uninstall

Removing Poetry (1.2.2)

Then:
poetry install

👍

I got the following error:
... [I ran pip install poetry, it executed successfully]...
(.venv) PS P:\OpenAdapt> poetry install

Poetry could not find a pyproject.toml file in P:\OpenAdapt or its parents


Lorem ipsum.

-Need text for this screen. This screen arrives at the time of approval.

"Please approve this request by scanning the Secondary Key stored with any of the other backups"

-Verified this change on dev app v1.5.0(260)