Add SQL

Added awesome-sql
Link:
https://github.com/mbiesiad/awesome-sql#readme
Awesome lists about SQL stuff, inspired by the awesome list.
SQL-related awesome list.
Reviewed PRs:
#1770 #1760
Requirements for your pull request
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.

You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
    ✅ Add Swift
    ✅ Add Software Architecture
    ❌ Update readme.md
    ❌ Add Awesome Swift
    ❌ Add swift
    ❌ Adding Swift
    ❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
    ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
    ✅ - [Framer](…) - Prototyping interactive UI designs.
    ❌ - [iOS](…) - Resources and tools for iOS development.
    ❌ - [Framer](…)
    ❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.

The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list
Has been around for at least 30 days.
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
Includes a succinct description of the project/theme at the top of the readme. (Example)
    ✅ Mobile operating system for Apple phones and tablets.
    ✅ Prototyping interactive UI designs.
    ❌ Resources and tools for iOS development.
    ❌ Awesome Framer packages and tools.
It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.
    ✅ awesome-swift
    ✅ awesome-web-typography
    ❌ awesome-Swift
    ❌ AwesomeWebTypography
The heading title of your list should be in title case format: # Awesome Name of List.
    ✅ # Awesome Swift
    ✅ # Awesome Web Typography
    ❌ # awesome-swift
    ❌ # AwesomeSwift
Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.
    Either centered, fullwidth, or placed at the top-right of the readme. (Example)
    The image should link to the project website or any relevant website.
    The image should be high-DPI. Set it to maximum half the width of the original image.
Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.
    Should be placed on the right side of the readme heading.
        Can be placed centered if the list has a centered graphics header.
    Should link back to this list.
Has a Table of Contents section.
    Should be named Contents, not Table of Contents.
    Should be the first section in the list.
    Should only have one level of nested lists, preferably none.
Has an appropriate license.
    We strongly recommend the CC0 license, but any Creative Commons license will work.
        Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=master&template=cc0-1.0 (replace <user> and <repo> accordingly).
    A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
    Place a file named license or LICENSE in the repo root with the license text.
    Do not add the license name or text to the readme. GitHub already shows the license name at the top of the repo.
    To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
Has contribution guidelines.
    The file should be named contributing.md. Casing is up to you.
Has consistent formatting and proper spelling/grammar.
    The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
    The description starts with an uppercase character and ends with a period.
    Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
Doesn't include a Travis badge.
You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.
Reopen #1783
Best wishes,

unicorn

Pretty much the same feedback as https://github.com/sindresorhus/awesome/pull/1802. Ensure you follow all the guidelines and try to improve the list further.

Ok, thank you. Improved.

You're right, awesome linter said about dead link last time: http://sqlfiddle.com/ the site is running.

@biesiadamich I mean in your readme line 42, there is no link for SQL Fiddle. That's probably what awesome-lint meant by dead link.

No, I mean the link have been added, but linter marked this as dead link, so was removed. Greetings

@biesiadamich I just ran awesome-lint after adding the link [SQL Fiddle](http://sqlfiddle.com/), and it passed all the tests.

I'm not sure what went wrong in your end. But leaving out the link from an entry defeats the very purpose of an awesome resource, if it's still happening you can add an ignore comment so awesome-lint skips that particular entry.

SQL is a broad topic with an immense amount of cool stuff, but your list has very little content. It doesn't look like a lot of effort was put into the list either. I'm going to pass on this for now.
Not everything needs to be included here though. Users can discover a lot more lists than what's here through https://github.com/topics/awesome.


4.x breaks vite pre-rendering

Describe the bug
The 4.x series of releases cause build failures with Vite (and Vike) when using the "prerendering: true" option.  The error DOES NOT occur using 3.9.5 but occurs on 4.0.0
The error is:
[vike][Warning] Vite's development server was instantiated while the environment is set to be a production environment by process.env.NODE_ENV === "production" which is contradictory, see https://vike.dev/NODE_ENV

To replicate the error:

npm init vike@latest
npm install @vanilla-extract/vite-plugin
Apply this commit or the below commands:
edit package.json to add a "name" field (build will fail unless a project has a name)
edit vite.config.ts to add vanilla-extract:

import react from '@vitejs/plugin-react'
import vike from 'vike/plugin'
import { UserConfig } from 'vite'
import { vanillaExtractPlugin } from '@vanilla-extract/vite-plugin';

const config: UserConfig = {
  plugins: [vanillaExtractPlugin(), react(), vike({ prerender: true })]
}

export default config

run npm run build

Reproduction
https://github.com/nathanstitt/vanilla-extract-vite-ssg
System Info
System:
    OS: macOS 14.3.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 336.00 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.5.0 - /usr/local/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 9.8.0 - /usr/local/bin/npm
    pnpm: 8.15.2 - /usr/local/bin/pnpm
  Browsers:
    Chrome: 124.0.6367.93
    Safari: 17.3.1
  npmPackages:
    @vanilla-extract/vite-plugin: ^4.0 => 4.0.9
    vite: ^5.0.10 => 5.2.10

Used Package Manager
npm
Logs
dist/server/entry.mjs                                5.13 kB
✓ built in 65ms
vike v0.4.171 pre-rendering HTML...
2:30:26 PM [vike][Warning] Vite's development server was instantiated while the environment is set to be a production environment by process.env.NODE_ENV === "production" which is contradictory, see https://vike.dev/NODE_ENV
Error<EMAIL_ADDRESS>You stumbled upon a Vike bug. Go to https://github.com/vikejs/vike/issues/new and copy-paste this error. A maintainer will fix the bug (usually under 24 hours).
    at initGlobalContext (file:///private/tmp/vt/node_modules/vike/dist/esm/node/runtime/globalContext.js:90:9)
    at runPrerender (file:///private/tmp/vt/node_modules/vike/dist/esm/node/prerender/runPrerender.js:80:11)
    at runPrerenderFromAutoFullBuild (file:///private/tmp/vt/node_modules/vike/dist/esm/node/prerender/runPrerender.js:47:9)
    at triggerFullBuild (file:///private/tmp/vt/node_modules/vike/dist/esm/node/plugin/plugins/autoFullBuild.js:92:9)
    at Object.handler (file:///private/tmp/vt/node_modules/vike/dist/esm/node/plugin/plugins/autoFullBuild.js:31:25)
    at async Promise.all (index 0)
    at PluginDriver.hookParallel (file:///private/tmp/vt/node_modules/rollup/dist/es/shared/node-entry.js:19706:9)
    at file:///private/tmp/vt/node_modules/rollup/dist/es/shared/node-entry.js:20703:13

Validations

[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

In general, 4.x seems very broken with vike.
If I use both vike-node and @vanilla-extract/vite-plugin and run pnpm build, the vite compiler enters an endless loop.
Repro: emonadeo/repro_vanilla-extract_1403
I think this happens, because @vanilla-extract/vite-plugin also calls the vite compiler internally and passes down the plugins from the user's vite config, and as such includes vike-node.
A potential fix for this might be to let the user decide with what (subset of) vite plugins vanilla-extract should run.


Set up the project infrastructure

With quality tooling specifically for SBT.
We are targeting

Scalastyle
CPD
Scapegoat
Scoverage
Scalariform

for initial integration

#2


Getting the Working Directory of the Application

I know that the shell script finds its way into the ….app/Contents/Resources/ directory. Is there a simple way of getting the app directory? Currently I use this:
	dir=$(builtin cd "../../.."; pwd)

It works, but I wondered whether there is a more direct approach?

As noted in the documentation:
https://github.com/sveinbjornt/Platypus/blob/master/Documentation/Documentation.md#how-do-i-get-the-path-to-my-application-andor-bundled-files-from-within-the-script
What do you mean by "more direct approach"?

No, that’s pretty clear. I wondered whether there might be an argument or something like that.
Thanks again.


[1] - Dashboard Sidebar

Addresses: #1
https://github.com/user-attachments/assets/646d739d-3fa3-41f6-baa3-5206fcbce2af
Sidebar for Dashobard for Admins user role:

Super Admin (admin@gmail.com:password)
System Admin (system-admin@gmail.com:password)
Institute Admin
Branch Admin (branch@gmail.com:password)

Added user-specific sidebar menus based on roles


Apply the change from STU4B#35 to the 1.3 translator

Ballot comment STU4B#35 deals with the potential for a timing phrase that includes an offset and an or less clause to result in a translation that does not account for the possibility that the right argument to the timing phrase is null. In this case, the resulting translation compares the left argument of the timing phrase to an interval with null and closed boundaries, effectively resulting in true for all possible values of the left argument.
This issue is to apply the changes made to address this issue in the 1.4 translator to the 1.3 branch.

Included in the 1.3.21 release


How jsTree instances identify to which DOM element they are tied?

Hello, we used two instances of jsTree in our project and all was fine, but I needed to add one more instance and now, somehow I getting refresh method as undefined from specific jsTree instance, while trees itself working, if not this.
We don't use ids with DOM elements at all, as we are using own made JavaScript front-end framework, where we developing using real JavaScript classes, how we getting programming very similar like for instance on .NET, where we store rendered DOM element jQuery object as such class member, in order to reduce performance costs for all the time searching of such DOM elements by for instance ID. Same as we store specific created jsTree instance as such class member, but I started to wonder, that maybe jsTree very needs that DOM id attribute? I don't know how it identify specific its instance...
Our code looks like this (this is pseudo code, real code is way more complex):
class OurTreeWrapper {
 specificClassMethod() {
  this.jqThis = $('<div>'); // ...creation of new DOM element, without an id, as usual..
  this.jsTree = this.jqThis.jstree(params); // creation of jsTree
  if($.isFunction(this.jsTree.refresh))
    alert('[this.jsTree.refresh] function not found!');

  // If we need to access specific tied to our class DOM element, we just call this.jqThis, for instance: this.jqThis.val(); it works fine
  // Such approach works fine for several years with many outside components and regular jQuery stuff. No problems in long run.
 }
}

Let's say, we have several instances of OurTreeWrapper class.
And it worked fine pretty long time, with such style initialization, but after I added one more tree, jsTree, refresh method started to be undefined on all of instances, while those all trees itself working... I wonder, maybe I need to add unique Id to DOM element or somehow to specify some unique identifier for specific jsTree instance, maybe it messes up with them or something else happening, but after its creation, we capture and save its instance at its OOP class... It has unique identifier as key only for its state module.

It seems that it was fault not of this component, sorry for distraction. We sort of had large globalized tree, and when was added one more such tree, some static ties started to mess up, probably unrelated with jsTree itself issue. I closing this issue. Sorries!


Is it possible to restrict Entry text Length using Bindable Property only

I have a doubt, Is it possible to restrict Entry text length  to 10 characters using Bindable properties only, not custom renderer along with BindableProperties.
Please add one example in your docs so that I can understand it.
Thank you.

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

ID: b054a909-6f7f-0b32-5059-eb5c8a9b366b
Version Independent ID: 723af07b-8f4e-ebe3-a520-99cdcf5efc5a
Content: Bindable Properties - Xamarin
Content Source: docs/xamarin-forms/xaml/bindable-properties.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @arvindrajachourasiya
There's an easier way: set the Entry.MaxLength property to 10 - https://docs.microsoft.com/xamarin/xamarin-forms/user-interface/text/entry#limiting-input-length


build: update envoy and fix ci build

Description: this PR updates envoy and makes the following changes:

linux CI jobs now use the envoy-build-ubuntu container published by envoy-build-tools
updates upload/download-artifact to v2.
specified using remote jdk toolchain for the coverage build.
temporarily moves java and kt unit tests to macOS. Subsequent PR will move as many CI jobs as possible to run on linux runners, as this saves time via container execution; and concurrency as the linux limit is higher than the macOS limit.
updates protobuf dep to 3.14.0
updates metrics transport to V3 Api
updates bazel build targets used in several places in the codebase
Fixes warnings in C++ tests.
Risk Level: low for all jobs ran in CI. High for release and artifact jobs as they won't execute until a release is done, and they are most likely broken. Will fix after running.
Testing: CI

Signed-off-by: Jose Nino<EMAIL_ADDRESS>

merged onto https://github.com/envoyproxy/envoy-mobile/pull/1230

merged onto https://github.com/envoyproxy/envoy-mobile/pull/1230


Fixed a pesky error in PagedPinotOutputStream.getPages

In #14375 an error in the data block deserialization is reported. After some debugging, it looks like the issue is actually in one of the libraries introduced to write the serialization efficiently. Specifically, PagedPinotOutputStream has an error when the number of written bytes was exactly a multiple of the page size and there was no seek.
This PR fixes the issue and therefore fixes #14375.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (b0bb2e8).
Report is 1288 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (b0bb2e8). Click for more details.
HEAD has 43 uploads less than BASE

Flag
BASE (59551e4)
HEAD (b0bb2e8)

integration
7
3

temurin
12
3

java-21
7
2

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
2

unittests
5
0

unittests1
2
0

java-11
5
1

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14389       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
0.00% <ø> (-61.71%)
:arrow_down:

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
0.00% <ø> (-27.73%)
:arrow_down:

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Asset Library no longer works

Godot version: 3.2.2 and 3.2.3
OS/device including version:
Windows 10
Issue description:
Clicking the Asset Library tab, waiting, searching, all fail (stays perpetually on "loading ..."). An error appears eventually.
Steps to reproduce:
Open the asset library.
Note: browsing the URL that appears below, shows "page not found".

Can't reproduce on my Manjaro (3.2.3 stable)

I also get 404 Not Found on https://godotengine.org/asset-library/api, I think it's because there is no endpoint at that exact location.

@nathanfranke The URL is https://godotengine.org/asset-library/api/asset (/asset is always appended).

I'm not behind a proxy or double-stack as far as I know.
I tried again right now and it seems that it's working again. Hurray.


useMotionValue of component A affected by onMouse events of component B that has nothing to do with A

1. Describe the bug
I'm building a React project. I have ComponentA.js and ComponentB.js that have nothing to do with each other except rendered in the same page.
In ComponentA.js, I have
// A
const dragX = const dragX = useMotionValue(0);
console.log(dragX);

In ComponentB.js, I have
// B
// I personally don't think the tag matters here
<video
  onMouseOver={() => setFocus(true)}
  onMouseOut={() => setFocus(false)}
  onEnded={onEndedLoop}
  src="/videos/something.mp4"
  muted
  playsInline
/>

Everytime the onMouse event listeners in B are triggered, dragX in A changes (can be seen from console.log(dragX)). This leads to unwanted animation effects on A.
If I use
// B
<video
  onMouseOver={() => {console.log("message 1")}}
  onMouseOut={() => {console.log("message 2")}}
  // omit repeated code for succinctness
/>

in B, then dragX in A won't change (no output from console.log(dragX)).
Also, if I have
// A
console.log(dragX.get())

in A, then hovering in B makes the console produce lots of 0s (by comparison, dragging in A produces meaningful coordinates, which is intended).
2. IMPORTANT: Provide a CodeSandbox reproduction of the bug
I wish I could provide code here, but I'm working on a private project with much code, and I personally think it could be distracting if trivial code is present.
3. Expected behavior
Hovering in B should not impact dragX or useMotionValue in A.
4. Video or screenshots
useMotionValue(0) (in A) is triggered when hovering (on an element in B). Note dragX.get() produces 0s.
https://github.com/user-attachments/assets/fc9a9c5a-ccb0-4750-a114-3fbc1922d3d5
useMotionValue(0) (in A) is triggered when interacting with an element (the carousel) in A. Note dragX.get() produces meaningful coordinates.
https://github.com/user-attachments/assets/7a1cb9cd-c953-4116-a2e2-d8f9299604fb
6. Environment details
Windows 10 22H2
Chrome Version 130.0.6723.119 (Official Build) (64-bit)
React 18.3.1 (problem happens even without StrictMode)

Unfortunately I’m going to need a sandbox to look into this further. My off the top of the head idea is that focusing is doing something to the videos layout?

Thanks for reaching out!
So focus is just a useState to identify if the user hovers on the video. Layout of the video is never changed.
Below is the related code.
// ComponentB.js

const loop = () => {
  ref.current.play();
};

const pauseLoop = () => {
  ref.current.pause();
};

const onEndedLoop = () => {
  if (focus) loop(); // when ended check if its focused then loop
};

useEffect(() => {
  if (focus) loop(); // when focused then loop
  if (!focus) pauseLoop(); // when not focused then pause loop
}, [focus]);

return (
<div>
  // ... omit for succinctness
  <video
    onMouseOver={() => setFocus(true)}
    onMouseOut={() => setFocus(false)}
    onEnded={onEndedLoop}
    src="/videos/something.mp4"
    muted
    playsInline
  />
  // ... omit for succinctness
</div>
);

I'm not sure if I'm able to write a working demo in a sandbox because there's much code involved. I'll need to factor things out, reorganize, and simplify, which would take me some time.


Task: Audit performance of Accessibility Conformance Report (VPAT) page

Describe the task
Audit performance of Clean and Green Philly's Accessibility Conformance Report (VPAT) page using Google Lighthouse. Document audit results, including areas of improvement.
Acceptance Criteria

[ ] Generate Lighthouse report for mobile devices
[ ] Generate Lighthouse report for desktop devices
[ ] Post screenshots of results in this issue's comments section
[ ] Write brief summary of audit highlights, including Lighthouse's recommendations for improvement

Additional context

For instructions on using Lighthouse, see https://developer.chrome.com/docs/lighthouse/overview

Hi, can I be assigned this ticket pls?

@zheyichn assigned!

Lighthouse report for mobile devices

Performance score was 69/100. It took a big hit due to largest contentful paint time of 7.1 seconds, and a total blocking time of 340ms.

Screenshots

Lighthouse report for desktop devices

All four scores were above 90/100.
Accessibility can be further improved by increasing contrast ratio for some table titles.

Screenshots

Summary

Performance score took big hit on mobile devices because of largest contentful paint time of 7.1 seconds, and a total blocking time of 340ms.
Some less unurgent issues for performance are similar to other pages:

Accessibility points deducted from misue of aria-* attribute on elements. This issue has been reported in #727 previously, but currently wontfix since it came from NextUI.
SEO requires links to be crawlable.

Improvement recommendations

Explore how to reduce content loading time/ blocking time. (Performance on mobile)
Increase contrast ratio for some table headers. (Accessibility)
Resolve the aria-* mismatch with role issue of the menu button, possibily by refactoring the menu component as discussed in https://github.com/CodeForPhilly/clean-and-green-philly/issues/727. (Accessibility)
Make links crawlable to search engines. (SEO)


Data Load / Volume Test -: Queue Optimization - Dashboard + System under more volume of data

Title of ticket:
Description
The purpose of this issue is to make the FOI Flow system under at least 1 - 2 years of data volume and under stand the break conditions and do required optimizations. One of the known candidate is the Dashboard queue.
Dependencies
Are there any dependencies?
DOD

[x] Use Automation Testing Tool or JMeter to Load the system with 1000 - 3000 records. This is should be set up by set up process.
[x]  MAJOR DELIVARABLE -DO SERVER SIDE PAGINATION, SORTING and FILTERING
[x]  If possible, make it work for 1000- 1500 records.  Create sensible amount of data/request with different states
[x]  Understand the loading on Dashboard. TRY TO MITIGATE THE LOADING with UX
[x]  Because 1000 records will not be available for a state at a given point to time

@m-prodan  @arielleandrews @lmullane  - Advice with a historical data volume or # of records under each state for FOI Requests

@abin-aot  - I'm not sure I can check historically active, but looking at right now it appears we have 2767 active FOI Requests - of those, the majority (1035) are in Records Review, and second highest state is CFR at 460. Looking at the last 3 years, we receive on average 864 requests a month. That doesn't account for the impact the application fee will have on that figure going forward.
Hopefully that can help you get started!

Looking to start this one in the new year - jan 4

#1094  #1000 - Should be analyzed while doing this.

Hi team,
Since business team already wrote the ACs for IAO queue and Ministry Queue, shall we reuse the ACs in the related User stories?
Please reference ACs in the following US when doing QA:
#20 Queue for Unopen
#85 Sorting
#200 Search
#288 Search by state
#354 Navigate to request from queue
#570 Ministry queue
#571 Filter (for example, Assigned to me)

@richard-aot, do we need a QA on this? Unclear to me how we test this?

Discussed with @abin-aot.  We know what needs to be done.

@Mullane, Loren CITZ:EX @.***>Good question. Yes, we do
need a QA on this. I understand the confusion here. From the user
perspective, nothing seems changed on the IAO queue (dashboard) and
Ministry queue, which is what we are trying to archive.
However, behind the scenes, both frontend and backend are updated:
For IAO queue and Ministry queue, we used to retrieve all requests from the
server in one API call, then do the listing, pagination, searching, sorting
on the front end. This works fine if we don't have too many requests in our
system. If there is more data, we will start seeing performance and memory
issues.
In the new implementation, the pagination, searching, sorting is executed
on the database server, which is what the database is designed for. The API
serves 10 requests (configurable) to frontend each time, so regardless of
how many requests in the system, the performance will not be impacted.
To QA this, we need to re-test User Stories for IAO queue and Ministry
queue. Go through the ACs in those US's again. The purpose is making sure
that both queues are working as they used to be (same columns,  data,
searching and sorting).
Below are the User Stories that I found for re-test:
#20 https://github.com/bcgov/foi-flow/issues/20 Queue for Unopen
#85 https://github.com/bcgov/foi-flow/issues/85 Sorting
#200 https://github.com/bcgov/foi-flow/issues/200 Search
#288 https://github.com/bcgov/foi-flow/issues/288 Search by state
#354 https://github.com/bcgov/foi-flow/issues/354 Navigate to request
from queue
#570 https://github.com/bcgov/foi-flow/issues/570 Ministry queue
#571 https://github.com/bcgov/foi-flow/issues/571 Filter (for example,
Assigned to me)
Let me know if you have any questions.
Thanks.
On Tue, Feb 15, 2022 at 3:31 PM Loren Mullane @.***>
wrote:

@richard-aot https://github.com/richard-aot, do we need a QA on this?
Unclear to me how we test this?
—
Reply to this email directly, view it on GitHub
https://github.com/bcgov/foi-flow/issues/1088#issuecomment-1040903950,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVTSVKKBZMWK4G4QJGZLKKLU3LO5BANCNFSM5KFPTVVA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Note, when you sort by 'Received Date' the sort is not chronological.


Added JUnit tests for AuthorizationFeatureService

Some unit tests for AuthorizationFeatureService service is added.
Regards,
Francesco

Coverage remained the same at 37.752% when pulling bed13e16deb4d1c55d36bd1ed87e764e490d132e on fcadili:DS-4413_authz into adfe2b6959a89763d573652939ad0f28846a561f on 4Science:DS-4413_authz.


[libwebp] Update to 1.3.1

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

I am not sure what to do with the support clause item.
I tested installation with triplet x64-windows.

Duplicate with #32767 submitted two minutes mine for the exact same thing. I am closing.


shortened file path and added support for requirements.txt

file path shortened to remove the unnecessary path strings
added the basic support for python to support the root requirements.txt

Hey @jyasveer, thanks for the PR. What are we trying to achieve by shortening paths? And why only Maven paths? :)

@msrb for now. we are concerned only for mavens. Same thing has to be done for python and node ecosystems. But we dont know how the full path looks like. so handled only for maven as of now

Thanks for the quick reply :) And what's the problem with the long paths? Possible information leakage, or something else?

Full path has some directory structure which is not relevant to the application workspace. We are only concerned with the paths that is relevant to code workspace. hence this fix

Some bug:
$ mvn clean verify

<-- snip -->

[INFO] Compiling 7 source files to /home/msrb/projects/fabric8-analytics/fabric8-analytics-jenkins-plugin/target/classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/msrb/projects/fabric8-analytics/fabric8-analytics-jenkins-plugin/src/main/java/com/redhat/jenkins/plugins/bayesian/Bayesian.java:[70,13] cannot find symbol
  symbol: variable url
[ERROR] /home/msrb/projects/fabric8-analytics/fabric8-analytics-jenkins-plugin/src/main/java/com/redhat/jenkins/plugins/bayesian/Bayesian.java:[143,16] cannot find symbol
  symbol:   variable url
  location: class com.redhat.jenkins.plugins.bayesian.Bayesian
[ERROR] /home/msrb/projects/fabric8-analytics/fabric8-analytics-jenkins-plugin/src/main/java/com/redhat/jenkins/plugins/bayesian/Bayesian.java:[147,13] cannot find symbol
  symbol: variable url
[INFO] 3 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

@msrb  can you please verify it now  ?

LGTM 😉


rbd: flatten datasource image before creating volume

This commit encures that parent image is flattened before
creating volume.

If the data source is a PVC, the underlying image's parent
is flattened(which would be a temp clone or snapshot).
hard & soft limit is reduced by 2 to account for depth that
will be added by temp & final clone.

If the data source is a Snapshot, the underlying image is
itself flattened.
hard & soft limit is reduced by 1 to account for depth that
will be added by the clone which will be restored from the
snapshot.

Flattening of resulting PVC image restored from snapshot is removed.
Signed-off-by: Rakshith R<EMAIL_ADDRESS>

/retest all

@Rakshith-R have you tested this with hardlimit and softlimit of 1?

It will not affect the flattening at this stage according to this check, pre existing behaviour will continue.

		const depthToAvoidFlatten = 2 #1 for snapshot
		if rbdHardMaxCloneDepth > depthToAvoidFlatten {
			hardLimit = rbdHardMaxCloneDepth - depthToAvoidFlatten
		}
		if rbdSoftMaxCloneDepth > depthToAvoidFlatten {
			softLimit = rbdSoftMaxCloneDepth - depthToAvoidFlatten
		}

Flattening for the temporary clones and final image is being removed in this pr,
Where the lower limit would have flattened intermediate clones(for clone) and final image(for snapshot) before the pr change.
IMO, the above change(2nd) is fine since cephcsi is the one which decides when depth should be checked and flattening operation performed.

@mergifyio rebase

changes LGTM can you please set max limit RbdHardMaxCloneDepth to 2 here https://github.com/ceph/ceph-csi/blob/devel/scripts/install-helm.sh#L182 to test no stale are left behind?

@Madhu-1 , Due to #2327 , setting this lower depth will leave stale images.
That's why this option was not set earlier.

/retest all

/retest all

seems jenkins errored out
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/organizations/jenkins/mini-e2e-helm_k8s-1.21/detail/mini-e2e-helm_k8s-1.21/2982/pipeline
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/organizations/jenkins/mini-e2e-helm_k8s-1.22/detail/mini-e2e-helm_k8s-1.22/2264/pipeline

@mergifyio rebase
ptal @ceph/ceph-csi-contributors

changes LGTM can you please set max limit RbdHardMaxCloneDepth to 2 here https://github.com/ceph/ceph-csi/blob/devel/scripts/install-helm.sh#L182 to test no stale are left behind?

@Madhu-1 , Due to #2327 , setting this lower depth will leave stale images. That's why this option was not set earlier.

Asked to make sure in any case there wont be any stale resources left behind

@mergifyio refresh

@Mergifyio refresh

@mergifyio rebase

@mergifyio rebase

@mergifyio rebase

@mergifyio refresh

@mergifyio rebase

/retest ci/centos/upgrade-tests-rbd

/retest ci/centos/k8s-e2e-external-storage/1.23

/retest ci/centos/k8s-e2e-external-storage/1.23
/retest ci/centos/upgrade-tests-rbd

success status was not reflected back to github
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/organizations/jenkins/upgrade-tests-rbd/detail/upgrade-tests-rbd/4869/pipeline
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/organizations/jenkins/k8s-e2e-external-storage-1.23/detail/k8s-e2e-external-storage-1.23/879/pipeline

@mergifyio rebase


Starting daemon on non default port

When starting the Daemon on non-default, the subsequent api calls fallback to default ports. Steps I followed are:
1. let daemon = await new DaemonFactory(binary).spawn({disposable: false, repoPath: repoPath}).catch(err => log.error(err.toString()))
2. await daemon.init(account.keypair.secret(), {repoPath: repoPath, swarmPorts: [4102], apiBindAddr: "<IP_ADDRESS>:41600", gatewayBinAddr: "<IP_ADDRESS>:5150"}).catch(err => log.error('Could not init', err.toString()))
3. await daemon.start({repoPath: repoPath}).catch(err => log.error('Not started', err.toString()))
4. log.info(await daemon.api.config.get())
Step 4 displays the api port as the default port and any further api calls go to that port.

@carsonfarmer do you have any immediate thoughts about this? If so, great, if not, I'll jump into it.

Not really. I think probably what's going on here is that the js-http-client is hardcoded to use the default ports etc. So it really just needs to get this information from the daemon on startup and use those instead.

@dominicpaul1911 Could you confirm that the init is indeed writing the correct ports to the textile config file? Should be a file called textile in the repoPath you specified. You can probably share that here, just make sure you don't share any private information :P

Attaching textile file
textile.txt

Here's the relevant bit:
"Addresses": {
        "API": "\"41600\"",
        "CafeAPI": "<IP_ADDRESS>:40601",
        "Gateway": "\"<IP_ADDRESS>:5150\"",
        "Profiling": "<IP_ADDRESS>:6060"
    },

Which is all messed up. Can you share the code snippet used to set these? Maybe just a tiny reproducible example?

The API addr should be something like "http://<IP_ADDRESS>:41600" and similarly the gateway. It looks like they are getting string escaped, which might be a bug?


The source code clarifies which errors were considered transient and worthy of retry, as of April 2013.

Its great to know Azure has such stability in its error codes and infrastructures that the list is still relevant 5 years later.

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

ID: a12b92b1-d5aa-5214-5f53-ef30a82dc8b1
Version Independent ID: 3bd8058c-7c35-ef4a-e82c-2e21dd6a0384
Content: Working with transient errors - Azure SQL Database
Content Source: articles/sql-database/sql-database-connectivity-issues.md
Service: sql-database
GitHub Login: @dalechen
Microsoft Alias: ninarn

@stofte Thank you for the feedback. We will investigate, review, and update the documentation with relevant updates.

@stofte Are you referring to the retrying Python project? That code is not dependant upon any specific error code set.

Retrying is an Apache 2.0 licensed general-purpose retrying library, written in Python, to simplify the task of adding retry behavior to just about anything.

So, as long as an application generates a success code and at least one error code, retry logic becomes useable.
I am not sure I follow you with regard to your statement: "Its great to know Azure has such stability in its error codes and infrastructures that the list is still relevant 5 years later."
Is there a document that is outdated and needs updating? Thanks, Mike

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


[CERT-TEST-FAILURE] - TC-HEPAFREMON-2.1 - Test failed

Feature Area
Other
Test Case
TC-HEPAFREMON-2.1
Reproduction steps
All-clusters-app has to be enabled with below mentioned Attribute :

[x] LastChangedTime
[ ] ReplacementProductList

Bug prevalence
Whenever I do this
GitHub hash of the SDK that was being used
b6caecf7860072bd4e55be43dc830b5ce990ddef
Platform
raspi
Anything else?
Spec Reference:

Test plan Reference:

Verified with this commit 78c62b0e43b223a72e0aba40ef5090c308575182 and found that "LastChangedTime attribute" has been implemented and updated the task list in the issue.
Keeping this issue open to get "ReplacementProductList" to be implemented.

Issue resolved


cloudworker does not support export / require?

I have a worker already running in cloudflare and working fine. When I try to test it with cloudworker though I always get the following error: ReferenceError: require is not defined
Do cloudworker support export/requires?

Neither Cloudflare Workers nor cloudwork does. Check out https://developers.cloudflare.com/workers/writing-workers/using-npm-modules/ for how to use modules. The TLDR is use webpack to combine the modules with your script and then use cloudworker to run the resulting script.

This thread has an approach too: https://github.com/dollarshaveclub/cloudworker/issues/95


Capture SIGINT/SIGTERM and wait for the child process to terminate.

I'm not entirely sure this is the right approach to threading the interrupted flag through to the other code, but it seems to work.

Awesome, thank you for the PR!
It looks the travis test failures are caused by a change to the version of the dash shell shipped by homebrew and are unrelated to your changes.
I won't have the time to give this a proper review until this weekend, although I have some thoughts:
It looks like it only processes ctrl-c during non-shebang recipes, it should probably check for an interruption before running a shebang recipe too? As is, if there are multiple interdependent shebang recipes that themselve ignore ctrl-c, will ctrl-cs be ignored?
It would be nice to add a test for this. It'll likely be complex though; would we have to spin up a process and send it sigint?

Alright, just got the time for a real review!
Since the SIGINT handler is global, I think it's okay for the interrupted flag to be global as well, which is possible with atomic bools. Check out this sketch:
https://play.rust-lang.org/?gist=90d1627a4192a2ddfe33f21ccd6f9d45&version=stable&mode=debug&edition=2015
This saves us from threading the interrupted flag through the program.
But, there are a couple more important questions first:

Sorry for taking absolutely forever with this, I've been swamped with work.
I started fooling around with different ways for formulate this, and I wound up writing what's in #345. I feel it's bad open-source etiquette to write an alternative implementation of a pull-request, but I just couldn't figure out or articulate what the right thing to do was without writing it myself. Sometimes my brain doesn't work as well as my hands.
I went with a guard-based approach which a destructor to try to minimize the amount of time we're ignoring interrupts, and to ensure that we abort, even if we panic for some reason.
Testing wasn't actually nearly as bad as I thought it would be. It just runs a justfile with a command that sleeps for two seconds, waits for a second, kills it, and then asserts that it exits in about 1 second, indicating that the signal was ignored for a bit and then handled, and that it returns the right status code.
I had to disable tests on windows, because rust libc on windows doesn't include a kill function, I think because windows doesn't have the same concept of signals as unix.
Would you mind testing #345 and checking that it works with the tests that weren't exiting on ctrl-C?

Yeah, that seems to have done it. Thanks!


TCL Error  Can't find a usable init.tcl in the following directories:

After I run the .bat file I get this error:
Traceback (most recent call last):
File "C:\Users\aking\Downloads\PySilon-malware-main\PySilon-malware-main\builder.py", line 391, in
root = Tk()
File "C:\Users\aking\AppData\Local\Programs\Python\Python313\Lib\tkinter_init_.py", line 2459, in init
self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use)
~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
_tkinter.TclError: Can't find a usable init.tcl in the following directories:
C:/Users/aking/AppData/Local/Programs/Python/Python313/lib/tcl8.6 C:/Users/aking/AppData/Local/Programs/Python/lib/tcl8.6 C:/Users/aking/AppData/Local/Programs/lib/tcl8.6 C:/Users/aking/AppData/Local/Programs/Python/library C:/Users/aking/AppData/Local/Programs/library C:/Users/aking/AppData/Local/Programs/tcl8.6.14/library C:/Users/aking/AppData/Local/tcl8.6.14/library
This probably means that Tcl wasn't installed properly."
I have used this before but I'm just now installing it again to use but now I am getting this error. Do I need a certain version of python? I am using the latest one...

yep i have the same problem

Hey, just open pysilon from builder.py with python instead of using the .bat

So your saying just open builder.py any everything will work normally?

Build it in a linux environment it worked for me

it did not work even tho when i run it it runs with visual studio code

I am on windows

Hey, just use the ModdedPysilon version, it covers every bug and it make sure your discord account never get banned.
Leave me a star if you like my project ;)


Elevator Block dupe crash

I was removing and repositioning Elevators, where, when placing down the recovered Elevator in another spot next to an RF source, the block was placed, but the item didn't leave the inventory - Confused as hell by this behavior, I tried mining the newly placed elevator, and the game just crashed - And keeps crashing on the world whenever I try to reload.
Using the newest version of "All The Mods" modpack (v1.44) with no additional mods and no changes to the config.
crash-2016-11-18_19.24.12-server.txt

Already fixed in 5.61 released today

Awesome! Manual update it is


test2

OPS Build status updates of commit 4377c30:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 4377c30:
:clock10: Incremental building: average incremental building time is 25 sec(s)

OPS Build status updates of commit 4377c30:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/distribution/ConcurExpense.md
:warning:Warning
View
Details

dynamics-gp/financials/PaymentDocumentManagement.md
:warning:Warning
View
Details

dynamics-gp/installation/ProfServicesToolsLibrary.md
:warning:Warning
View
Details

dynamics-gp/payroll/AdvancedPayroll.md
:warning:Warning
View
Details

dynamics-gp/TOC.md
:white_check_mark:Succeeded
View

dynamics-gp/distribution/media/CONCFLOW.jpg
:white_check_mark:Succeeded
View

dynamics-gp/distribution/media/CONCSET.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/CashFlowManagement.md
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/02a0837ff55c8999cb6c934c9adb56cb.gif
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/48da5b4904ef0a78eb1e3da2e1fa1c16.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/66ae6e632683f0642194355db830790d.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/81f51d8030c93f0b164a5a01b594533b.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/9a5376f5aaa58e0cde3bb0e122bc6bcf.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/CFFOR.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/CFM (12).gif
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/CFM (12).jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/CFM (17).jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/CFM (23).jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/CFM (24).jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/CFMCAL.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/CFMTRX.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/CPDM.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/PCPDS.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/PPDE1.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/PPDM.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/PPDMS.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/PPDSET.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/SCPDS1.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/SPDENQ.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/SPDM01.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/media/SPDMS.jpg
:white_check_mark:Succeeded
View

dynamics-gp/financials/uk-tax-mtd.md
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/EMPMOD.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PST1099M.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTACM.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTACTMOD.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTCERT.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTCERTP.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTCHMOD.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTCLOOK.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTCOPCO.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTCUSMOD.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTFAMOD.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTFISMOD.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTINS.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTINVMOD.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTITCO.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTITDMOD.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTITEMMOD.jpg
:white_check_mark:Succeeded
View

dynamics-gp/installation/media/PSTLIB.jpg
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

dynamics-gp/distribution/ConcurExpense.md

Line 44: [Warning] Invalid file link:(~/distribution/media/4f75e5eddb78d8c48d19b37b5a611ca6.jpg).
Line 127: [Warning] Invalid file link:(~/distribution/media/d278c881aa2e80e8bcc5f1aad2832336.jpg).

dynamics-gp/financials/PaymentDocumentManagement.md

Line 112: [Warning] Invalid file link:(~/financials/media/e2a028dcfa3545c3d0c12d12f1bb13fe.jpg).
Line 149: [Warning] Invalid file link:(~/financials/media/0f2a0eaefb89be35406a19c11794980d.jpg).
Line 195: [Warning] Invalid file link:(~/financials/media/2ee44fa43e761471b8a0e14b61689a48.jpg).
Line 233: [Warning] Invalid file link:(~/financials/media/2a26e204107e4c0347f2b84eec636f69.jpg).
Line 360: [Warning] Invalid file link:(~/financials/media/b73c66ae9c337f8aa42744011bbd8239.jpg).
Line 419: [Warning] Invalid file link:(~/financials/media/4a28db5857371b1982f1fd27cfee734a.jpg).
Line 469: [Warning] Invalid file link:(~/financials/media/7b5559618301c36f03bfa6768684403c.jpg).
Line 596: [Warning] Invalid file link:(~/financials/media/fe7a6c9499a0656e849699d82be6b631.jpg).
Line 632: [Warning] Invalid file link:(~/financials/media/331108befae1ede8317d7e19611cad73.jpg).
Line 1020: [Warning] Invalid file link:(~/financials/media/7eaaf175a75b89f087816a95c4e833cf.jpg).

dynamics-gp/installation/ProfServicesToolsLibrary.md

Line 21: [Warning] Invalid file link:(~/installation/media/b2ab6ec2dd6025f7327e9004dd0eb287.png).
Line 37: [Warning] Invalid file link:(~/installation/media/b2ab6ec2dd6025f7327e9004dd0eb287.png).
Line 51: [Warning] Invalid file link:(~/installation/media/b2ab6ec2dd6025f7327e9004dd0eb287.png).
Line 155: [Warning] Invalid file link:(~/installation/media/e98c1352cd449d7aa876197e6c740aea.jpg).
Line 287: [Warning] Invalid file link:(~/installation/media/bbad3af62fb8663718fecbb98e2d0590.jpg).
Line 308: [Warning] Invalid file link:(~/installation/media/cac0db5c96fd8c6606fcd355bed3d6ca.jpg).
Line 336: [Warning] Invalid file link:(~/installation/media/d8e78bce04f58707d273878c6c62e0b5.jpg).
Line 439: [Warning] Invalid file link:(~/installation/media/a88f4caf017aa370984bf14c95b51684.jpg).
Line 460: [Warning] Invalid file link:(~/installation/media/a16ea972059cd90148e294a3201e64ec.jpg).
Line 537: [Warning] Invalid file link:(~/installation/media/bc17fd7f416e464646166ee5e0818aab.jpg).
Line 555: [Warning] Invalid file link:(~/installation/media/1f929a3c36ad3144684ead12e67491c2.jpg).
Line 582: [Warning] Invalid file link:(~/installation/media/c54c9c7d6757d91e394323e5e096590a.jpg).
Line 666: [Warning] Invalid file link:(~/installation/media/4876f57348d9d6bdc8258615e008aa21.jpg).
Line 831: [Warning] Invalid file link:(~/installation/media/51043b306addcd813fc1de1071a5ce51.jpg).
Line 855: [Warning] Invalid file link:(~/installation/media/57f8b2ae7d26b178176adfc7e8cf1d70.jpg).
Line 973: [Warning] Invalid file link:(~/installation/media/7dfc3dfe73a52902fe9a88f3dc4d8d05.jpg).
Line 1045: [Warning] Invalid file link:(~/installation/media/6e87b8ff4a476026db4102542602b0d7.jpg).
Line 1076: [Warning] Invalid file link:(~/installation/media/b46f5819dbd446008227ace25469d45a.jpg).
Line 1113: [Warning] Invalid file link:(~/installation/media/dab50933fff5188b269046bb2537650a.jpg).
Line 1127: [Warning] Invalid file link:(~/installation/media/e9ee2a1d4204acac692f5431d54349d6.jpg).
Line 1155: [Warning] Invalid file link:(~/installation/media/b1d2cb4dc84cd4830ad1b4a082785974.jpg).
Line 1181: [Warning] Invalid file link:(~/installation/media/8ac1cd7a0995b1655083fd883416a512.jpg).
Line 1210: [Warning] Invalid file link:(~/installation/media/6346596ff60bc29163e079652ac6dc27.jpg).
Line 1392: [Warning] Invalid file link:(~/installation/media/57dfd93b57a510254fd8750a7761a96c.jpg).
Line 1465: [Warning] Invalid file link:(~/installation/media/b64a60fc657a7ff60a52e834b610c85c.jpg).
Line 1539: [Warning] Invalid file link:(~/installation/media/0cd4ee5bc05eca0373eb73ed79a5f7e4.jpg).
Line 1592: [Warning] Invalid file link:(~/installation/media/c1191b26fd8c4b16fbd42dc3cfd908fd.jpg).
Line 1629: [Warning] Invalid file link:(~/installation/media/5a4c5a9e7c53c8d89a0f5fd2cdb19771.jpg).
Line 1680: [Warning] Invalid file link:(~/installation/media/c14af4a366e6717fcfb00e3387148407.jpg).
Line 1760: [Warning] Invalid file link:(~/installation/media/e98c1352cd449d7aa876197e6c740aea.jpg).
Line 1795: [Warning] Invalid file link:(~/installation/media/f6cd48c209fdd7cacf54e6965ea45cab.jpg).
Line 1829: [Warning] Invalid file link:(~/installation/media/14d96c71a001e5f12450c7f34eca1f74.jpg).
Line 1859: [Warning] Invalid file link:(~/installation/media/0e6852a93880e5b59c05b21cc5ee6cac.jpg).
Line 1920: [Warning] Invalid file link:(~/installation/media/522477c75245b10318d8f5a971306177.jpg).
Line 2047: [Warning] Invalid file link:(~/installation/media/577c501cb87929fc73ecf070d08df050.jpg).

dynamics-gp/payroll/AdvancedPayroll.md

Line 400: [Warning] Invalid file link:(~/payroll/media/4be45bdfbfa7fa5b8e5e1273c99fe1ca.jpg).
Line 444: [Warning] Invalid file link:(~/payroll/media/1b7a7d0d2105d38b4f108fcbcae8a9ea.jpg).
Line 497: [Warning] Invalid file link:(~/payroll/media/3682febe7f8380e092213bf04723673a.jpg).
Line 646: [Warning] Invalid file link:(~/payroll/media/38faa911c7b27828dae0557600159f32.jpg).
Line 744: [Warning] Invalid file link:(~/payroll/media/1859a5d77be20b8a7241e4ea2624640f.jpg).
Line 784: [Warning] Invalid file link:(~/payroll/media/48e1813c069cc3809e85f08cf7e45bcb.jpg).
Line 913: [Warning] Invalid file link:(~/payroll/media/1496d6c0f31bccc37099c5590b1b3092.jpg).
Line 936: [Warning] Invalid file link:(~/payroll/media/7977806af2f0ec351776e5cb71069fb1.jpg).
Line 1238: [Warning] Invalid file link:(~/payroll/media/10d43b370e55069491f108e962d29310.jpg).
Line 1267: [Warning] Invalid file link:(~/payroll/media/0a40d3be32d5491e1636f612d457a794.jpg).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Support preview Team Review Requests API

GitHub Announcement:
https://developer.github.com/changes/2017-07-26-team-review-request-thor-preview/
GitHub API Docs:
https://developer.github.com/v3/pulls/review_requests/
Note that the announcement describes a breaking change which may involve a bump of this package's version number.

@gmlewis @shurcooL
Can I take this up?

Sure thing, feel free to go for it! Thanks.

Thank you for resolving this issue @RaviTezu!


fix: image src is null after loaded

Close https://github.com/Brooooooklyn/canvas/issues/882

#886  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Brooooooklyn and the rest of your teammates on  Graphite


How to outout structured in agent?

In https://github.com/knowsuchagency/promptic/pull/21, these is a structured tools example: examples/use_tools_structured.py. As you can see, all tools outputs structured result, but the scheduler only outputs text, is there a way to make it outputs structured?

I don't think it's necessary to handle structured output from tools in the same way as functions decorated with promptic since the outputs of tools get fed to the llm, not the user. However, you can still get structured output from your agent. I integrated your examples in the test suite and demonstrated getting structured output here

Thanks.


I can't open social fish

Before you submit this bug report check that you have ran the required setup correctly. Follow the steps on the wiki.
I can't open social fish

Please I have been able to obtain victim login but I don't know how to extract it or get the username and password please I need help


Call for comments: Job System

Series upcoming features.
More than once I read of users that were to use EnTT along with a job system.
So I thought: why not?
I'd like to design a bunch of template classes well suited for a header only library so as to integrate a tailored job system within EnTT.
Before to start working on it, I'd like to know if it's really a wanna have feature.
I think I'll use the job system in my projects, so probably I'll create it anyway. However, knowing that some others are going to use it and can help me testing and improving that part would be great!!
Lighting issue just to collect some feedback. I'll close it in 24/48 hours.
Thank you all in any case!!

@skypjack There actually process classes that similar thing, what the difference will be?

I'd say a single threaded cooperative scheduler vs multi threaded job system. Pretty much orthogonal a tool, they will match with different use cases.

@skypjack An simple example for Unity.

Cpp-taskflow looks like a brilliant library. Perhaps EnTT could provide a few helpers for using the two libraries together.

Yes. Yes. It's promising. I like transwarp  too.
Recently, i "requeste a comparison between cpp-taskflow and transwarp here.
However, IMHO, EnTT should avoid dependencies at all costs and be a self-contained project. It should be just a separate extension with its own maintenance.
My two cents.
DJuego

@DJuego I agree that EnTT should be self-contained but if the helpers are in their own header, then cpp-taskflow is only a dependency if the user chooses to include the helpers header. Also, cpp-taskflow is just one self-contained header file.

@ArnCarveris  thanks a lot for that taskflow library. I didnt know of it and it seems awesome.
@skypjack  i dont think  a built in task system is needed with the engine. It is something that depends too much on the specific architecture of the engine, i think. It would be like adding a graphics library to EnTT for some reason. Personally, i would prefer that things are kept simple.

@vblanco20-1 Totally agree with you.
@skypjack  Any way, there should be provided necessary API if needed. No need use any external dependencies.

Found another library that could be useful: concurrentqueue

@ArnCarveris  im using that queue in my experiment. I can confirm it works great and it is REALLY fast.

Actually, I was thinking about something pretty different than a queue from which threads pick up some work to do.
Just to be clear, it won't be embedded within the ECS in any way. It will be part of the library as SigH or Scheduler, that is it will have its own header and users can just ignore it. However, the idea is that I'll extensively use it to schedule my jobs in a multi threaded fashion.
Good to know that there exists a good library I can use for a comparison!! :-)

@skypjack Notify when will be any API draft .

I'd like to design a bunch of template classes well suited for a header only library so as to integrate a tailored job system within EnTT.

Can you talk a little about what you are thinking for this?
The reason I’m asking is that the discussion above seems to be discussing adding a job system directly to EnTT. I think this is a bad idea — different people will want different job systems. Some already have one that they want to integrate with. I, personally, want to use Intel’s Threading Building Blocks’ task system because I’m already familiar with it, but other people won’t want to use that and will want to use something else instead.
So, even if its in a companion library, I’m not sure if the effort is necessarily worth it. However, adding something to make it easier to support plugging in your own job system would be greatly beneficial, I think. I’m not exactly sure what would be needed to make that work. I guess some way to scatter/gather so that component data can be pushed out to tasks and then be pulled back in.
I haevn’t started my own experimentation yet, but I was planning on doing something like this:
Systems that don’t modify component (only read them) can be run in parallel, but sequentially before those that do need to modify components. Then, the ones that write data, they must be run in such a way that only one thread ever writes a component at a time (must be careful that reads are syncrhonised too). I haven’t thought too hard about how this should work yet or how systems should be sequenced so that they read the components at the right time (before antoher sysetm writes? after?).
What I’ve done in the past (not using EnTT) is my state was double buffered: systems always read the previous state and wrote the new state, then at the end of the frame, it gets swapped so the next frame reads the new state. This works well since all reads are synchronised, but means that if the output of one sysetm must be immediately known by another one, the components can’t be used directly but instead messages/events need to be used to pass this data along. Ie written state is never read until it gets swapped at the end of the frame.
I hope that makes sense. Like I said, I haven’t started experimenting yet, so I’m still a bit fuzzy on it.

@danielytics The fact is that I need something simple and flexible and I don't want to pull in such a complex external library in my codebase. Therefore, I'm going to design a minimal job system to use along with the registry somehow. However, it won't be integrated with the registry itself, so users can just ignore it as they can ignore the Scheduler class and so on. Moreover, I want to write something that isn't on the same line with TBB and the other mentioned, because so aren't my requirements and those libraries don't match actually.

@vblanco20-1 Put a note in the TODO file so as to think about it.

@skypjack I’m not asking to pull in TBB or any other library, quite the opposite.
I’m saying that, because different people will have different requirements (or different favourite job systems, or in-house ones or whatever —  I only mentioned TBB as an example of what I want to use), I think the most useful thing would be to make sure that the users can themselves easily plug in their favourite job system to work with EnTT. Basically, I’m agreeing with @vblanco20-1
I was thinking that since writing a job system, even a simple one, is a bit of work, that time may be better spent making sure EnTT can be easily integrated with any job system and then letting everyone use whichever one they want, and you could then use an existing simple one for your needs rather than reinventing the wheel. Of course, if none exists that suit your needs, then by all means, write your own, doing so may be a great exerice to figuring out what features might be added to EnTT to better support a job system.
I’ve also used the concurrent queue that @ArnCarveris mentionend. Its worked out great for me and performs extremely well. Its a single-header library too, so its really easy to integrate.

No, I’ve not had a problem with it, although, as I said in my earlier comment, I haven’t started prototyping it yet. I don’t envision any real problems, although I’ve not yet figured out the best way to manage writes to a component (other than double buffering, but that also has issues — eg how do I swap components without lots of memory copying), but I imagine your design will actually help answer some of these questions.
In any case, I’m looking forward to what you come up with.

I should have said: other than double buffering or serialising writes. Obviously serialising writes is always an option and, I guess, they can be in parallel as long as they’re different components on the smae entitiy, or the same components on different entities.

Thank you all for this interesting discussion. Really appreciated.
Time to close this issue.

@vblanco20-1

A way to "deep copy" a registry, keeping specific component types, and keeping the entities ID (and versions) correct. Im not sure if the serialization system can be used for this, im still planning things so i havent tested if the serialization system would do the trick for such a "deep copy" of the registry.

The use is for a "pipelined" engine. You have the "main" ECS registry for simulation, and when you are going to render the world, you deep copy the "render" related components into a Render ECS registry, wich then goes into a second thread to run the rendering of the world.

I thought about this. Doesn't a continuous loader work in your case?
More than keeping entities' IDs and versions correct, you need a way to keep a correct mapping between entities ID and versions from both the sides. This is exactly the purpose of a continuous loader.
It's a matter of defining an archive that is filled by an instance of a snapshot and writes everything directly to a target registry by means of a continuous loader.

Some issues ive been runing into while refactoring the space battle benchmark to use taskflow https://github.com/cpp-taskflow/cpp-taskflow
Ive been trying to implement a deep copy for the registry to use in pipelining, but it didnt work. Some kind of way to use the snapshot system to actually copy into a new registry while keeping the entity ID numbers would be great (becouse my Transforms system uses entity ids to handle parenting).
Another issue ive ran into is storing/caching views. both move operator and copy operator on a view are deleted, and the use case for it is a task that "prepares" a system, and then it links into a parallel for type task. The parallel for cant really create the view inside, and it is needed that the task prepares the system, as im using a separate "schedule" step.
The current architecture has worked linearly (one system after another), but im trying to make it much more parallelized. It works by having each system have a "schedule" function that creates one or multiple tasks to schedule the work, and once the tasks tree is built, it is executed. The pipelining with the render systems would work by copying the registry into a "render registry", and that way its safe to keep the game systems doing things while the render systems are busy rendering the last frame.

@vblanco20-1 I don't think there are problems to make views copy/move constructible/assignable. I can work on it when I'm back home, probably it's a matter of a few changes.
On the other side, to make a deep copy of the registry is quite hard because of the type erased pools. However a deep copy isn't some kind of way to use the snapshot system to actually copy into a new registry while keeping the entity ID numbers. The latter is far easier.
Can you argument a bit more about what's the actual requirement?

@skypjack  im trying to improve my spaceship benchmark thing. At the moment, im bottlenecked due to the main thread having sync points. This sync points are due to safely multithreading everything.
To improve it, im moving it to a task or fiber system (testing both). Due to all those clear sync points, i want to pipeline the engine with 2 pipeline stages, the Game stage and the Render stage.
The game stage is as usual, but what i want to do is to  "copy" all the relevant components from the registry into a "render only" registry, that then gets used for the rendering portion of the engine (culling + rendering). Im  aware that EnTT is not thread safe if you are adding or removing entities, so if i want to have my render code run at the same time as the game thread is doing things, i have no option but to copy it. Once the copy is done, the game thread will start to instantly go execute the next simulation frame, while the render thread is busy rendering to the screen. I expect to get a gain of 30% speed with this.


Hopscotch Release 0.2.7

Maintenance release for master branch. Only includes urgent patches necessary for integrating with latest versions of build tools.

[x] Merge #312
[x] Merge #307
[x] Add deprecation notice to Contributing section of README.md on master. (General gist is that we're only considering urgent fixes for now; no new feature development at this time.)
[x] Sanity check master with changes.
[x] Issue new release and publish to npm.

Version 0.2.7 tagged, pushed to master, and published to NPM. Release complete. 🎉


implement #69 use classnames module to construct react classnames

#69

better commit message:
refactor(classnames): use classnames to build css classes

resolves issue #69

:rocket:

Cool, I like that :+1:


cargo run --release fails on factors example

My pc:
cpu: i7 5500u
ram: 16gb ddr3
os: ubuntu 18.04
I'm trying to run the factors example on my pc but it fails with the following error messages at end of step 4. Here's the log:
log.txt

The same kind of error occurs when I try to benchmark my pc within the risc0 package.

The poly_fp.cpp file is very intensive for most compilers and we've seen similar "internal compiler error" (ICE) with older compilers. It's also possible that the compiler is running out of RAM. Here are a few workarounds I can offer:

Use a newer version of gcc
Install clang and use it with: export CC=clang CXX=clang++
Build on a machine with more RAM

In the future, we plan to have prebuilt binaries that will be published for cases like this.

Yes, it was a ram issue! Seems that minimum ram is > 16gb and a safe bet would be 24-32gb.


Integrated with react router

How do i integrate react router

By providing an href key to a leaf element in the tree material-ui-treeview will use the Link component of react-router-dom to perform the transition.
const tree = [
  {
    value: 'Parent A',
    nodes: [{ value: 'Child A', href: '/child-a' }, { value: 'Child B', href: '/child-b' }],
  },
];

// ...

<MuiTreeView tree={tree} />

@helfi92 Thank you so much

You're welcome!


demonstration server not working

The mordred publication mentions a demonstration server at https://mordred.phs.osaka-u.ac.jp/ which I was able to access in December. That server seems to be down now. Can an alternative demonstration server be made available?
Thank you!

@sibo Tested today with Chrome. It is working.


debuginfo: Don't strip ELF files if text section is missing

Fixes: #1369

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I hope I understood the issue correctly. I was a bit confused whether it was asking to simply flush the file as is if .text was missing or return an error. I went with the former. Let me know if the solution is correct. cc @brancz
I also wanted to write a unit test using an elf file that lacked a .text section but I couldn't understand how the testdata elf files were being generated even after taking a look at this tool https://github.com/kakkoyun/readelf-sections

On the topic of writing a test, I haven't used the tool you linked above. But you can also use llvm-strip with -R option to have some testdata file with no .text section.

@palash25 This is so close to the finishing line. Let us know how we can help you.

@kakkoyun i was just waiting for your reply, do the changes look good to you? i guess the only thing left is writing a unit test by generating tesdata like @v-thakkar suggested. I will try to do that tomorrow

@kakkoyun i was just waiting for your reply, do the changes look good to you? i guess the only thing left is writing a unit test by generating tesdata like @v-thakkar suggested. I will try to do that tomorrow

The changes look good :) Thanks for the contribution. We can merge it after some tests.


py.typed

Is there a reason why this project doesn't have a py.typed file in the module folder?
I'm new to mypy, but it's complaining that there's no typings unless I add that file in the site-packages directory.
I'd submit a PR, but it looks like the build is failing?

@escaped, could you please check this issue? Without it, mypy thinks the package doesn't have typing support.

I just release 1.2.0, which includes a py.typed file. :)


Tap to show often is mistaken for a stroke

And then there's a dot there where I tapped.

This has probably been fixed and if not is has been moved to JIRA.


[BUG] Fails on an ipv6-only tailnet

Describe the bug
The step "Facts | Get IPv4 address" fails when run on a machine attached to a v6-only tailnet.
To Reproduce
Steps to reproduce the behavior:

Create tailnet
set disableIPv4: true in the tailnet acl.
Run role on machine to join to tailnet
See error

Expected behavior
Role completes successfully
Screenshots
TASK [artis3n.tailscale : Facts | Get IPv4 address] **************************************************************************************************************************************************************************************************************************************
fatal: [guffnet-ch-01]: FAILED! => {"changed": false, "cmd": ["tailscale", "ip", "--4"], "delta": "0:00:00.021313", "end": "2024-09-03 14:37:21.667542", "msg": "non-zero return code", "rc": 1, "start": "2024-09-03 14:37:21.646229", "stderr": "no Tailscale IPv4 address", "stderr_lines": ["no Tailscale IPv4 address"], "stdout": "", "stdout_lines": []}

Target (please complete the following information):

OS: Debian 12
Ansible version: 2.17.3
artis3n.tailscale version: 4.5.0
Tailscale version (set verbose to true): 1.72.1

Output of tailscale status during role execution (set verbose to true):
$ sudo tailscale status --peers=false
fd7a:115c:a1e0::c001:4f01 guffnet-ch-01        userid:15d52116014f28 linux   -

Additional context
This worked in 4.4.2!

Thanks - we'll need to set the IPv4 and IPv6 facts to have an empty default to prevent task failures


How to go about altering a where clause

I know that I can add to a query build where clause with qb.where, qb.orWhereIn, etc. and those have been working great. However I recently came across a scenario where the query (via separate modifiers/logic) ends up like...
Model.query().where('foo', 'bar').orWhere('abc', 'xyz')

Before that executes I need to change that to...
Model.query().where(qb =>
  qb.where('foo', 'bar').orWhere('abc', 'xyz')
).whereIn('id', [123, 456]);

Essentially trying to figure out how to grab an existing where clause and wrap it and then add to it.

There's no way to do that.


[[TrasmissiOne]] Venezia Parma In Diretta Streaming 09 novembre 2024

Venezia FC vs. Parma Live: Stream, Time & Betting Odds 11/9
By BVM Sportsdesk, 11/04/2024
Venezia FC and Parma are both facing tough seasons in Serie A, with Venezia sitting at 19th place and Parma at 15th. Venezia recently lost 1-0 to Inter Milan, being outshot 19 to 8, while Parma also fell 1-0 at home to Genoa CFC, with a close shot count of 15 to 12 against them. The two teams will clash on Saturday, November 9, 2024, at Stadio Pierluigi Penzo, beginning at 9:00 AM ET. Fans can watch the game via live stream on Paramount Plus. Betting odds indicate a competitive match, with close lines for both teams and a draw option available.
By the Numbers
Venezia FC is currently 19th in Serie A with a recent record of 1-0 loss against Inter.
Parma sits at 15th place, losing 1-0 to Genoa in their last match.
Venezia was outshot 19 to 8 in their last game; Parma faced 15 to 12.
Yes, But
Both teams have been struggling, raising concerns about their chances of avoiding relegation. Their recent performances indicate systemic issues on both sides, particularly in attack, which may hinder ability to gain points in upcoming matches.
State of Play
Venezia FC seeks to break a losing streak and improve its standing in Serie A.
Parma aims to capitalize on their opponent's vulnerabilities to gain necessary points.
The match is crucial for both teams in the relegation battle.
What's Next
Looking ahead, the outcome of this match will significantly impact both teams' standings. A win for Venezia could rejuvenate their season, while a victory for Parma would provide them with much-needed momentum as they aim to distance themselves from the relegation zone.
Bottom Line
This matchup is pivotal for both Venezia FC and Parma, with potential repercussions on their season aspirations. Keeping a close eye on offensive execution will be key for either team to secure a much-needed victory.

hggh

tyhyt


[CHALLENGE SUBMISSION] - Day 23

Please provide the following information for your submission:
What is your name? (First, Last)
Stuart Leaver
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/stuartleaver/25-days-of-serverless/tree/master/23-instrumenting-functions
What Challenge is this for? (Challenge number between 1 and 25)
23
(Optional) Anything else we should know? e.g., language used, location, blog post?
C#, Azure Function, Durable Entities, Application Insights, Logic App, Twilio.

The unthinkable has happened: after weeks of community members all over the globe chipping in to help solve people's problems with serverless technology, the evil grinch's heart is starting to soften! He's still not quite ready to give up his server-stealing plot, but our whole Azure Cloud Advocacy team is flying up to the grinch's lair to help convince him to change his ways.
As such, the team behind 25 Days of Serverless is OOF (Out Of Facility/Office) between Dec 24, 2019 and January 1, 2020. We'll not review Issues in this period of time, but encourage you to catch up on any challenges you haven't had the time to work on yet. 😄 Our Discord Server is a perfect place to reach out to for community support during this time. After our return, we'll add contributors who submitted a working solution as an Issue to CONTRIBUTORS.md file until January 15, 2020.


Adding code coverage analysis for tasks

Description:

Add nyc for coverage report
Add a condition to run only for node version >= 10
Add publishing step to the pipeline
Increase timeout time for tasks, since nyc command run longer
fix incorrect mock for fs module

Documentation changes required: N
Added unit tests: N
Checklist:

[x] Checked that applied changes work as expected

/azp run


Add Issue Template

Add a template for new issues creations.

I want to work on this. Please assign this to me.

i would like to work on this!


error go routines old code

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

$ go version

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?

What did you expect to see?
What did you see instead?

go version go1.12.3 darwin/amd64

sig := make(chan os.Signal, 1024)
signal.Notify(sig, os.Interrupt, syscall.SIGTERM, os.Kill, os.Interrupt)
defer close(sig)
go svc.Webmain(sig)

////////////////////////////////


🐛 Bug Report: TechDocs legacyCopyReadmeMdToIndexMd breaks relative links in README

📜 Description
Using TechDocs legacyCopyReadmeMdToIndexMd feature breaks relative links from the readme file located in the root of the project that point to files in docs directory.
For example, given following directory structure:
.
├── README.md
└── docs
    ├── adr.md
    └── diagram.svg

and README.md file:
# Readme

Relative link: [architecture decision record](docs/adr.md)

![Architecture diagram](docs/diagram.svg)

results in a broken link (and image) in the resulting docs index page.
👍 Expected behavior
When using readme files from the root of the project for tech docs index pages relative links and images targeting other files inside docs directory should continue to work.
👎 Actual Behavior with Screenshots
Relative links are broken, because TechDocs plugin copies readme file from project's root into docs directory, which breaks relative links that target files inside the docs directory.
👟 Reproduction steps
Generate docs using the setup explained above (legacyCopyReadmeMdToIndexMd enabled, readme file in project roots with relative links / images pointing to files in docs directory) and check the documentation index page.
📃 Provide the context for the Bug.
The legacyCopyReadmeMdToIndexMd feature is genuinely useful, and enables me to bootstrap a lot of projects (git repos) quickly and without changes in the projects themselves. However, this relative links bug prevents project developers from slowly building up more elaborate documentation in their docs directory while keeping project readme as the main entry point for the project. I think it's useful (and expected) to have readme in the root of the project, so I'd like to continue using this setup readme file in the project root, docs directory with slowly building extra stuff, and relative links between them.
🖥 Your Environment
Dependencies:
  @backstage/app-defaults                          1.4.2
  @backstage/backend-app-api                       0.4.5, 0.5.2
  @backstage/backend-common                        0.18.5, 0.19.4
  @backstage/backend-dev-utils                     0.1.1
  @backstage/backend-openapi-utils                 0.0.3
  @backstage/backend-plugin-api                    0.5.4, 0.6.2
  @backstage/backend-tasks                         0.5.7
  @backstage/backend-test-utils                    0.2.2
  @backstage/catalog-client                        1.4.3
  @backstage/catalog-model                         1.2.0, 1.4.1
  @backstage/cli-common                            0.1.12
  @backstage/cli-node                              0.1.3
  @backstage/cli                                   0.22.12
  @backstage/config-loader                         1.4.0
  @backstage/config                                1.0.8
  @backstage/core-app-api                          1.9.1
  @backstage/core-components                       0.12.4, 0.12.5, 0.13.4
  @backstage/core-plugin-api                       1.0.6, 1.5.3
  @backstage/dev-utils                             1.0.20
  @backstage/errors                                1.2.1
  @backstage/eslint-plugin                         0.1.3
  @backstage/integration-aws-node                  0.1.5
  @backstage/integration-react                     1.1.18
  @backstage/integration                           1.6.2
  @backstage/plugin-api-docs                       0.9.10
  @backstage/plugin-app-backend                    0.3.50
  @backstage/plugin-app-node                       0.1.2
  @backstage/plugin-auth-backend                   0.18.8
  @backstage/plugin-auth-node                      0.2.19
  @backstage/plugin-catalog-backend-module-ldap    0.5.17
  @backstage/plugin-catalog-backend                1.12.4
  @backstage/plugin-catalog-common                 1.0.15
  @backstage/plugin-catalog-graph                  0.2.35
  @backstage/plugin-catalog-import                 0.9.13
  @backstage/plugin-catalog-node                   1.4.3
  @backstage/plugin-catalog-react                  1.2.1, 1.8.3
  @backstage/plugin-catalog                        1.12.4
  @backstage/plugin-events-node                    0.2.11
  @backstage/plugin-github-actions                 0.6.4
  @backstage/plugin-home-react                     0.1.2
  @backstage/plugin-home                           0.5.7
  @backstage/plugin-jenkins-backend                0.2.5
  @backstage/plugin-jenkins-common                 0.1.18
  @backstage/plugin-jenkins                        0.8.5
  @backstage/plugin-linguist-backend               0.4.2
  @backstage/plugin-linguist-common                0.1.1
  @backstage/plugin-linguist                       0.1.8
  @backstage/plugin-org                            0.6.13
  @backstage/plugin-permission-backend             0.5.25
  @backstage/plugin-permission-common              0.7.7
  @backstage/plugin-permission-node                0.7.13
  @backstage/plugin-permission-react               0.4.14
  @backstage/plugin-proxy-backend                  0.3.2
  @backstage/plugin-scaffolder-backend             1.16.5
  @backstage/plugin-scaffolder-common              1.4.0
  @backstage/plugin-scaffolder-node                0.2.2
  @backstage/plugin-scaffolder-react               1.5.4
  @backstage/plugin-scaffolder                     1.14.4
  @backstage/plugin-search-backend-module-catalog  0.1.6
  @backstage/plugin-search-backend-module-pg       0.5.11
  @backstage/plugin-search-backend-module-techdocs 0.1.6
  @backstage/plugin-search-backend-node            1.2.6
  @backstage/plugin-search-backend                 1.4.2
  @backstage/plugin-search-common                  1.2.5
  @backstage/plugin-search-react                   1.6.4
  @backstage/plugin-search                         1.3.6
  @backstage/plugin-sonarqube-backend              0.2.4
  @backstage/plugin-sonarqube-react                0.1.7
  @backstage/plugin-sonarqube                      0.7.4
  @backstage/plugin-tech-radar                     0.6.7
  @backstage/plugin-techdocs-backend               1.6.7
  @backstage/plugin-techdocs-module-addons-contrib 1.0.18
  @backstage/plugin-techdocs-node                  1.7.6
  @backstage/plugin-techdocs-react                 1.1.9
  @backstage/plugin-techdocs                       1.6.8
  @backstage/plugin-user-settings                  0.7.8
  @backstage/release-manifests                     0.0.9
  @backstage/test-utils                            1.4.2
  @backstage/theme                                 0.2.19, 0.4.1
  @backstage/types                                 1.1.0
  @backstage/version-bridge                        1.0.4

👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Regarding implementation of this, I think it could be solved in a few places:

In the TechDocs plugin itself, in the code that is copying readme files.
In the mkdocs-techdocs-core plugin.
Backstage users themselves could develop mkdocs plugin of their own and plug it in using the newly introduced defaultPlugins config option.

In each of these cases I think fix is simple. We can use a relatively sane regex (or couple of them) to detect relative links and images with path starting with docs/ prefix and remove it.

Is there some more info I could provide on this one? As I said, I'm interested in opening a pull request to fix this, if you think it's worth fixing.


Upgrade to cert-manager 1.7

Update to cert-manager 1.7
Update to controller-runtime 0.11
Update to compatible k8s dependencies
Build using Go 1.17

The e2e tests are not run automatically (yet) so I ran them locally:
$ make kind-cluster deploy-cert-manager docker-build kind-load deploy
...

$ make e2e
kubectl apply --filename config/samples
kubectl wait --for=condition=Ready --timeout=5s issuers.sample-issuer.example.com issuer-sample
kubectl wait --for=condition=Ready --timeout=5s  certificaterequests.cert-manager.io issuer-sample
kubectl wait --for=condition=Ready --timeout=5s  certificates.cert-manager.io certificate-by-issuer
kubectl wait --for=condition=Ready --timeout=5s clusterissuers.sample-issuer.example.com clusterissuer-sample
kubectl wait --for=condition=Ready --timeout=5s  certificaterequests.cert-manager.io clusterissuer-sample
kubectl wait --for=condition=Ready --timeout=5s  certificates.cert-manager.io certificate-by-clusterissuer
kubectl delete --filename config/samples
certificate.cert-manager.io/certificate-by-clusterissuer created
certificate.cert-manager.io/certificate-by-issuer created
certificaterequest.cert-manager.io/clusterissuer-sample created
certificaterequest.cert-manager.io/issuer-sample created
clusterissuer.sample-issuer.example.com/clusterissuer-sample unchanged
issuer.sample-issuer.example.com/issuer-sample unchanged
secret/clusterissuer-sample-credentials unchanged
secret/issuer-sample-credentials unchanged
issuer.sample-issuer.example.com/issuer-sample condition met
certificaterequest.cert-manager.io/issuer-sample condition met
certificate.cert-manager.io/certificate-by-issuer condition met
clusterissuer.sample-issuer.example.com/clusterissuer-sample condition met
certificaterequest.cert-manager.io/clusterissuer-sample condition met
certificate.cert-manager.io/certificate-by-clusterissuer condition met
certificate.cert-manager.io "certificate-by-clusterissuer" deleted
certificate.cert-manager.io "certificate-by-issuer" deleted
certificaterequest.cert-manager.io "clusterissuer-sample" deleted
certificaterequest.cert-manager.io "issuer-sample" deleted
clusterissuer.sample-issuer.example.com "clusterissuer-sample" deleted
issuer.sample-issuer.example.com "issuer-sample" deleted
secret "clusterissuer-sample-credentials" deleted
secret "issuer-sample-credentials" deleted

I updated this PR to use the latest released cert-manager 1.7.0.

@jahrlin I pushed some of those changes we just discussed to hopefully get the Makefile working on Mac M1 + darwin.


chore(main): release 2.4.1

:robot: I have created a release beep boop
2.4.1 (2023-04-23)
Bug Fixes

discovery fails on some UPnP implementations (27ceae9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/huffSamuel/upnp_explorer/releases/tag/v2.4.1 :sunflower:


Support for TeensyLC

Hello, Here's a pull request for the Teensy LC (https://www.pjrc.com/teensy/teensyLC.html).  I hope I've covered everything.  It needs the ldscript file mkl26z64.ld but not sure how to include that here.

@colincarter thanks a lot for your contribution!

Do you have that board?
mkl26z64.ld we will ask @valeros to add it to ldscripts package, which is located in home_dir/packages/ldsripts
Has @PaulStoffregen finished with TeensyLC and Arduino framework? Is TeensyLC officially released with Arduino IDE?
@valeros please update package framework-arduinoteensy with this core https://github.com/PaulStoffregen/cores
How about uploading? Does Teensy CLI support all OS?

Hi,

Yes I've got the board
I copied mkl26z64.ld from the Arduino hardware/teensy/avr/cores/teensy3 (on OS X) directory to home_dir/packages/ldscripts to test the build.
As far as I can see it's been officially released and comes bundled with the latest Teensy Loader Application.
I've used the Teensy Loader to upload with platformio run

Regarding question 3: YES.  Teensy-LC was officially released on March 12.  Teensy-LC is now in stock at many major distributors, or of course can be ordered directly from PJRC.
https://www.sparkfun.com/products/13305
http://www.exp-tech.de/teensy-lc
https://www.adafruit.com/products/2419
http://www.hobbytronics.co.uk/teensy-lc?keyword=teensy
Teensyduino 1.21, the first non-beta version to support Teensy-LC, was released on March 15.
Teensyduino 1.22, primarily an update to support Arduino 1.6.2 & 1.6.3 (released within the last week) will be published later today.  Beta versions for 1.22 have been available for the last 5 days.

@valeros Please update framework-arduinoteensy and tool-teensy to the latest version for the all platforms.


Issue 250: improvement/helm chart defaults 0.4

Re-Issuance of PR #251 following the the contributing guide.
I also updated the default image tag version to the latest version.
Change log description
Updated the default Controller URI to match the default pravega helm charts since localhost would not be valid given the image used in the k8 helm chart environment.
Purpose of the change
Addresses #250
This PR allows the schema registry helm charts to be compatible with the Pravega helm charts when following the Pravega Kubernetes 101 Guide.
The guide states to install the pravega charts via the pravega release name: helm install pravega pravega/pravega --version=0.8.0, which will default to creating the controller service in the ClusterIP with the internal dns of "pravega-pravega-controller".
What the code does
No code change, just default configuration.
How to verify it
Follow the  Pravega Kubernetes 101 Guide and then install the schema registry charts with default values.

@shshashwat this PR, in fact, only changes the charts file. I don't know why this is showing a change in gradle.properties, because it is not changing anything (it already has the values that are already there).

@shshashwat this PR, in fact, only changes the charts file. I don't know why this is showing a change in gradle.properties, because it is not changing anything (it already has the values that are already there).

I think it's showing changes because of the tip of the head wasn't pointing to the latest master and after creating a PR when the latest was updated it was updated on current branch rather than the master itself. This PR needs a rebase with the latest master synced with forked master. These changes will go with that.

@tsteinholz, can you please update your master and rebase this branch with latest master? That way we would be able to close this soon.

Closing this PR as didn't get any response. A re-creation of this PR is merged to master.


Error: Navigating frame was detached

Steps to reproduce
Environment:
Puppeteer   2.0.0;
OS               Windows 10;
Node.js       12.0.0;
`const puppeteer = require('puppeteer');
(async () => {
const browser = await puppeteer.launch({
headless: false
});
const page = await browser.newPage();
page.on('framenavigated', (frame) => {
    console.log('Frame navigated: ' + frame.name());
});

page.on('framedetached', (frame) => {
    console.log('Frame detached: ' + frame.name());
});

await page.goto('http://example.com');
await page.evaluate(() => {
    let iframe;
    iframe = document.createElement('iframe');
    iframe.name = 'my_frame';
    document.body.appendChild(iframe);
});

let frames = await page.frames();
let my_frame = frames[1];

try {
    await my_frame.goto('http://example.org');
} catch (error) {
    console.log(error);
}

try {
    await my_frame.goto('http://example.net');
} catch (error) {
    console.log(error);
}

await browser.close();

})();`
What is the expected result?
Navigation should be completed without errors.
What happens instead?

Well, this doesn't happen in versions prior to 1.20.0

My bad, Page.navigate is getting a frameId.

I was struggling with similar problem (frame detaching) on version 2.0.0. For whatever reason iframe I was interested for was detaching, and page.frames() returned an empty array and at the same time iframe was still there in the dom. So downgrading to 1.19.0 fixed the problem.

@cssberries @dmnrmr could you try disabling the site-per-process flag?
const browser = await puppeteer.launch({headless: false, args: ['--disable-features=site-per-process']})

It seems like '--disable-features=site-per-process' does the trick. This is a good news!
The question though is what are the implications of this? What is the bad news?

@mathiasbynens I think you will have some insights related to this flag.