Allow report generation even if  defined file does not exist

Is your feature request related to a problem? Please describe.
With  we can define a file to customize the final report. This file should exist for the cluecumber plugin to generate the report. In our case,  resource.properties file content is dynamically generated with a custom tool, thus the file should exist on git. When there are errors generating the properties file, the cluecumber report is not created. Is it possible to allow the generation of the cluebumer report even if this file does not exist?
Describe the solution you'd like
Throw a warning for the user to easily identify that something is wrong with the resource.properties file defined in the , either for file not existent, or bad format, etc
Describe alternatives you've considered
I've created the file in gitlab with no content and untracked it so my IDEA stops identifying this auto-generated file to commit and push. This is just a trivial nice-to-have feature :)
Additional context
[ERROR] Failed to execute goal com.trivago.rta:cluecumber-maven:3.8.1:reporting (default-cli) on project automation-tests-reports: File '/builds/cgdpnce/pemp/cgd-corporateloans-e2e-automation-tests/automation-tests-reports/src/test/resources/report.properties (customParametersFile)' could not be found. -> [Help 1]

This can be included in the next release.

Ready for release in 3.8.3

Released

Thank you. Will update it :)


Devolution (stage 1)

...

Codecov Report

Merging #9 (2d73050) into main (a597463) will decrease coverage by 1.41%.
The diff coverage is 79.56%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main       #9      +/-   ##
==========================================
- Coverage   90.57%   89.17%   -1.41%
==========================================
  Files          65       65
  Lines        7971     8020      +49
  Branches        0     1099    +1099
==========================================
- Hits         7220     7152      -68
+ Misses        751      586     -165
- Partials        0      282     +282

Files Changed
Coverage Δ

src/hypercoil/__about__.py
100.00% <ø> (ø)

src/hypercoil/functional/activation.py
86.95% <0.00%> (ø)

src/hypercoil/functional/cmass.py
91.30% <ø> (ø)

src/hypercoil/functional/connectopy.py
95.45% <ø> (ø)

src/hypercoil/functional/crosshair.py
78.04% <ø> (ø)

src/hypercoil/functional/crosssim.py
100.00% <ø> (ø)

src/hypercoil/functional/fourier.py
84.00% <0.00%> (ø)

src/hypercoil/functional/kernel.py
89.94% <ø> (ø)

src/hypercoil/functional/semidefinite.py
93.93% <ø> (ø)

src/hypercoil/functional/sphere.py
90.62% <0.00%> (ø)

... and 55 more

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


CTL Browser - Support Wallet Configured Networks

Currently we only support connecting to testnet for CTL browser apps. We want to make it so that the network the wallet is configured to is passed to CTL.
The following is how Nami supports setting the network:

This line of code is where we would need to support this:
https://github.com/ArdanaLabs/dUSD/compare/evan/try-mainnet?expand=1#diff-b57ecdd3fa818251d164204628a2c1c86fdaa01dc1b2de5174c800a7c497e302R87

Have you able to resolved your issues


Use pathname when crafting addresses in the js

Fix addresses crafted in the js when visdom is not at the "base address".
This allows to use visdom behind a proxy at addresses like "ip_address:port/foo".
I just rebuilt the static js for python, let me know if anything else should be changed.

Looking good - thanks for this!


Added new sync related repositories to README

Motivation
Having multiple sync related repositories that are not connected is not good user experience. Adding links to newly created repos to README.

This is PR from my trepel/branch to trepel/master, closing


Auto reconnect

Hello,
It is possible to automatically reconnect if the socket is disconnected ?
thk's

There isn't a property like autoReconnect per say, but it can be done by simply doing:
func websocketDidDisconnect(socket: WebSocket, error: NSError?) {
socket.connect() //will reconnect on disconnect
}

This way you have control over when to reconnect, which is useful if you want to manually disconnect the socket or have another reason for the WebSocket to be disconnected.


[CDEC-451] Remove Mockable

Description
The Mockable typeclass is a layer of indirection which allows code to be run in different monads without requiring changes to the monadic functions.
Mockable is apparently only executed in IO, and thus provides no benefit and a fair amount of hassle due to indirection & confusion for developers.
Remove the Mockable typeclass and associated instances.
Linked issue
https://iohk.myjetbrains.com/youtrack/issue/CDEC-451
Type of change

[~] 🐞 Bug fix (non-breaking change which fixes an issue)
[~] 🛠 New feature (non-breaking change which adds functionality)
[~] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[x] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[~] 🔨 New or improved tests for existing code
[~] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[x] I have read the style guide document, and my code follows the code style of this project.
[x] If my code deals with exceptions, it follows the guidelines.
[x] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[~] I have added tests to cover my changes.
[x] All new and existing tests passed.
^ I can see a good argument for tests to ensure the functions of Pos.Core.Conc are equivalent to those of Pos.Core.Mockable.Production. At present I have not added such tests, though.

Since there are a lot of changes here, I'd recommend going through the commits separately. The first 2 delete dead code which used Mockable. The next removes imports of Mockable from source code files. The next deletes the Mockable modules, and removes the last imports of Mockable from a few test packages.

Looking forward to see this get merged into 'develop'. Getting rid of 'Production' will make our life easier!
Thanks for that great job @mhuesch

LGTM, I am happy to see the change too.  As long as @avieth is fine with removing the files, I am fine with it.


Download PNG/PDF doesn't work before i generate atleast once

When i load my previous session from this tab

Then i try to download PNG/PDF, it bugged the UI, and it fails to download
https://user-images.githubusercontent.com/64251396/208912875-76ff72b5-e86f-4f50-b602-91438909aae5.mp4
Next i try to add a single prompt on that same session, then try to download PNG/PDF, it worked

I also have the same behaviour.

Hello, I was a contributor once to this project and I see that liady stopped maintaining it. Because of that I have created my own version of the ChatGPT-pdf, called ChatgptToPdf, If you see that you have problems with this extension I invite you to try mine and see if your issues get fix, let's work together to improve it. Thank you!


Add automated test to prevent package changes without version changes

It's currently possible to update behaviours in our first party published packages in https://github.com/flutter/plugins without changing the package's version number.
Therefore it's possible for people on the same team to have pub got the package before and after the behaviour change and get different behaviours despite being on the same version.
Create a test to machine enforce version changes.

It's useful to be able to make minor changes without updating the version with no intent to publish (e.g., test or example code changes), and per the comment above it shouldn't be possible to accidentally publish in that case.
Absent definitive evidence that this can somehow happen, I'm going to close this.


replace jansson with nlohmann::json (master)

Will be able to merge pending successful CI test runs against supporting PR https://github.com/irods/externals/pull/90 . (Those changes in the irods/externals were necessary for AMQP to run on Ub18 )

rebased and rebuilding , will squash and # when ready for merge

Squashed to 1 commit and verified it compiles against the json irods-externals lib
Not sure if I've done something fishy in moving this code from jansson -> json , or even if that is what's behind the test failing in CI . (It passed on 4-2-stable, where it still uses jansson).

Bumping this thread to encourage possibly getting this in :)

Superseded by #105?

@d-w-moore This work appears to have been completed as part of #105. Can we close this PR?

@d-w-moore This work appears to have been completed as part of #105. Can we close this PR?

I'd say so, as jansson no longer appears in the code or as a dependency....

okay, closing...


UDF functions

✅ No public API change.

✅ No public API change.

✅ No public API change.

✅ No public API change.

✅ No public API change.

                }

Can we share this check with UDF eval on L299?

Refers to: src/libraries/Microsoft.PowerFx.Interpreter/EvalVisitor.cs:318 in 2695975. [](commit_id = 26959751d64d9c62983efdb3f038b2ac171ae7f9, deletion_comment = False)

    public override async ValueTask<FormulaValue> Visit(ResolvedObjectNode node, EvalVisitorContext context)

Per my other comments - (in UserDefinitionsNameResolver)
I think this functions will need to be update to know about parameters.

Refers to: src/libraries/Microsoft.PowerFx.Interpreter/EvalVisitor.cs:726 in 2695975. [](commit_id = 26959751d64d9c62983efdb3f038b2ac171ae7f9, deletion_comment = False)

✅ No public API change.

                }

I'll check. This brings the question: why not all result is checked this way?

In reply to:<PHONE_NUMBER>

Refers to: src/libraries/Microsoft.PowerFx.Interpreter/EvalVisitor.cs:318 in 2695975. [](commit_id = 26959751d64d9c62983efdb3f038b2ac171ae7f9, deletion_comment = False)

✅ No public API change.

                }

Correct, it should be, there is already an issue field for it
https://github.com/microsoft/Power-Fx/issues/1634

In reply to:<PHONE_NUMBER>

Refers to: src/libraries/Microsoft.PowerFx.Interpreter/EvalVisitor.cs:318 in d7573a1. [](commit_id = d7573a139aaf1b025a7fd5a76a91052c829ec599, deletion_comment = False)

                }

I see. Better if we address all these type checks in #1634, IMO.

In reply to:<PHONE_NUMBER>

Refers to: src/libraries/Microsoft.PowerFx.Interpreter/EvalVisitor.cs:318 in 2695975. [](commit_id = 26959751d64d9c62983efdb3f038b2ac171ae7f9, deletion_comment = False)

✅ No public API change.

✅ No public API change.

✅ No public API change.


[Expression] inconsistency between doc and implementation for 'int', 'float'

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
What package version of the SDK are you using.
Current main
Describe the bug
Give a clear and concise description of what the bug is.
The document says 'Return the floating point representation of the specified string or the string itself if conversion isn't possible.'
https://docs.microsoft.com/en-us/azure/bot-service/adaptive-expressions/adaptive-expressions-prebuilt-functions?view=azure-bot-service-4.0#conversion-functions
However, if one uses int('bad'), float('bad'), it will throw an exception 'Input string was not in a correct format.'
To Reproduce
Steps to reproduce the behavior:

See https://github.com/xieofxie/botbuilder-dotnet/commit/5084688a55c11b3749a85dbae9ca426bd33a14be

Expected behavior
Give a clear and concise description of what you expected to happen.
If exception is the planned behavior, we still need a function to know if a string is whether in int format (from document, we could int and then isInteger
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Firstly, the exception is as expected.
Let me summarize the requirements:

The doc of "int()" is wrong.
Require a new function that can determine if a string can be converted into an integer. Maybe like:

tryParseToInt(param): {isInt: bool, result:number}

Is that right?
If so, a series of functions need to be added:
tryParseToJson
tryParseToFloat
tryParseToBool
tryParseToBase64
tryParseToXml
tryParseToBinary

hmmm, this should be considered carefully.

Yeah.. I like the way in document better

@xieofxie The changes are now live.

Since the doc has been updated. Mark this issue as the new feature requirement of new prebuilt functions.

The changes are live, should I close the issue @xieofxie?

@emgrol Sure, hope the new functions could be added soon.

close this one due to the duplication of #4773


Layer Behaving differently to README

For some reason whenever I use this layer, any command output (stdout) is going to the response of the lambda, and anything that I write to stderr (>&2) is going to Cloudwatch, which is the opposite of what the README mentions.
Has anything changed? Or could I have missed any important step in the setup process?
Thanks

That's odd. Nothing has changed that should make that different. At least on my end.
Could you post some example code so I can see what's going on? Thanks!

Sure. Here is my handler code:
`function handler () {
set -e
EVENT_DATA=$1
link=$( echo $EVENT_DATA | jq ."channelUrl" )
echo "THIS GETS LOGGED" >&2
echo $link >&2
echo "THIS GETS RETURNED"

}
`
And here are the results:

Hmmm, that's really odd. I'll need to do more testing to see why this is. I haven't made any changes in my layer to cause this, and I don't know of any AWS changes that would cause this either.

I just tried this again and my results are the exact opposite. (Mine match the README).
If this is still an issue please let me know but I can't reproduce it as of now.


Receiving NULL when using fastapi with flutterflow

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
#this section will be for providing an API for the application

#system imports
import os
import sys
import psycopg2
import pandas as pd
import datetime as dt
import uvicorn
from typing import Union
import fastapi
from fastapi import FastAPI, Depends, HTTPException
from fastapi.security import OAuth2PasswordBearer
from fastapi.encoders import jsonable_encoder
from fastapi.responses import JSONResponse
import json
from starlette import status
from pydantic import BaseModel
import warnings
warnings.filterwarnings("ignore")

#the os path to the folder to the ocular-git master folder
dir_path = os.getcwd()
#the sub path to the parent folder that contains the modules to import
sub_path = '\\ocular\\database\\connection_info\\'
sys.path.append(dir_path + sub_path)
path = sys.path.append(dir_path + sub_path)

#module/package imports. example " from 'module_name' import 'function_name' " within the parent folder

from config import config

#display this programs file name and that it has been started
print(os.path.basename(__file__) , ' has started')

#logic variables
logic_name = 'API Execution Logic'

#function to perform a read query on the database
def read_postgresql_conn(name,query):
    conn = None
    try:
        params = config()
        conn = psycopg2.connect(**params)
        cur = conn.cursor()
        print("|logic| " + logic_name + " |executed query| " + query)
        df = pd.read_sql(query, conn)
        return df
        cur.close()
    except (Exception, psycopg2.DatabaseError) as error:
        print(error)
    finally:
        if conn is not None:
            conn.close()

#function to perform a write query on the database
def write_postgresql_conn(name,query):
    conn = None
    try:
        # read connection parameters
        params = config()
        conn = psycopg2.connect(**params)
        cur = conn.cursor()
        print("|logic| " + logic_name + " |executed query| " + query)
        df = cur.execute(query, conn)
        conn.commit()
        cur.close()
    except (Exception, psycopg2.DatabaseError) as error:
        print(error)
    finally:
        if conn is not None:
            conn.close()

#SECURITY AUTHENTICATION LOGIC------------------------------------------------------------

# Use token based authentication
oauth2_scheme = OAuth2PasswordBearer(tokenUrl="token")

# Ensure the request is authenticated
def auth_request(token: str = Depends(oauth2_scheme)) -> bool:
    authenticated = token == os.getenv("API_KEY", "dummy-api-key")
    return authenticated

#END OF SECURITY AUTHENTICATION LOGIC------------------------------------------------------------

app = FastAPI()

#THIS IS THE SIMPLEST API THAT I CREATED FOR TROUBLESHOOTING. IT ALSO WORKS WITH POSTMAN BUT NOT FLUTTERFLOW

@app.get("/hello", status_code=status.HTTP_200_OK, dependencies=[Depends(auth_request)])
async def hello():
    return {"message": "Hello World"}

#THE FOLLOW APIS ARE THE ONES THAT WORK WITH POSTMAN BUT NOT FLUTTERFLOW - THESE ARE RELATED TO MY APPLICATION

@app.get("/newestcard")
async def newestcard(authenticated: bool = Depends(auth_request)):
    # Check for authentication like so
    if not authenticated:
        raise HTTPException(
            status_code=status.HTTP_401_UNAUTHORIZED,
            detail="Not authenticated")

    # query to retrieve the newest card
    retrieve_newest_card_query = 'SELECT * FROM public."API_Card_Data_View" ORDER BY "timestamp" DESC LIMIT 1'

    #call the function to query the database for the latest card to analyze
    new_card_results = read_postgresql_conn(logic_name,retrieve_newest_card_query)

    #return the results of the query as a dictionary
    return new_card_results.to_dict(orient='records')

#retrieve cards from the database based on a range of row numbers------------------------------------------------------------
@app.post("/cardrange")
async def cardrange(offset: int, limit: int, authenticated: bool = Depends(auth_request)):
    # Check for authentication like so
    if not authenticated:
        raise HTTPException(
            status_code=status.HTTP_401_UNAUTHORIZED,
            detail="Not authenticated")

    # query to retrieve the newest card. Limit is the amount of cards and offset is the starting point 0 based. App must
    # track how many cards are currently queried and where it last left off
    retrieve_card_range_query = 'SELECT * FROM public."API_Card_Data_View" ORDER BY "timestamp" DESC LIMIT ' + str(limit) + ' OFFSET ' + str(offset)

    #call the function to query the database for the latest card to analyze
    card_range_results = read_postgresql_conn(logic_name,retrieve_card_range_query)

    #return the results of the query as a dictionary
    return card_range_results.to_dict(orient='records')

#retrieve the user setpoints from the database------------------------------------------------------------

@app.get("/readsetpoints")
async def setpoints(authenticated: bool = Depends(auth_request)):
    # Check for authentication like so
    if not authenticated:
        raise HTTPException(
            status_code=status.HTTP_401_UNAUTHORIZED,
            detail="Not authenticated")

    # query to retrieve the newest card
    retrieve_setpoints_query = 'SELECT * FROM public."user_control_and_setpoints"'

    #call the function to query the database for the latest card to analyze
    setpoints_results = read_postgresql_conn(logic_name,retrieve_setpoints_query)

    #return the results with a dictionary
    return setpoints_results.to_dict('records')

#update the user setpoints in the database using post user input data with two parameters--this is used for manual shutdown and reset/ack
@app.post("/updatesetpoints")
async def setpoints(value: float, column: str, authenticated: bool = Depends(auth_request)):
    # Check for authentication like so
    if not authenticated:
        raise HTTPException(
            status_code=status.HTTP_401_UNAUTHORIZED,
            detail="Not authenticated")

    # query to update the setpoints
    update_setpoints_query = 'UPDATE public."user_control_and_setpoints" SET ' + column + ' = ' + str(value)

    #call the function to query the database for the latest card to analyze
    setpoints_results = write_postgresql_conn(logic_name,update_setpoints_query)

    #return the results with a dictionary
    return 'setpoint updated!'

#launch unvicorn to run the fastapi application on localhost with reload enabled
if __name__ == "__main__":
    uvicorn.run(app, host="localhost", port=80)

Description
I am seeing an odd issue that i can't seem to track down. When i use postman I receive status code 200 and can retrieve data with api bearer token logic functioning correctly. However, when i attempt to use the flutterflow to retrieve the same data i receive a status code 200 and NULL data results. FYI, to get my localhost Fastapi outside of my network i have been using ngrok and i have verified that everything functions correctly with postman while using the ngrok external https address. I also have noticed that removing the bearer token from flutterflow still results in a status code 200. I watched the incoming traffic to uvicorn and noticed that the server is not seeing any requests when i test the flutterflow logic. i'm unsure if there is an issue on the flutterflow side or if ngrok is doing something strange with the traffic, but i'm leaning towards flutterflow since postman works perfectly with ngrok. I realize the questions here are going to be "You mention flutterflow 10 times....have you talked to them?". And yes i have a request into them as well, but i would like to get a second opinion on my logic to rule out any issues on my side while i wait to hear back from them.
Operating System
Windows
Operating System Details
Python version:  3.10.7 (tags/v3.10.7:6cc6b13, Sep  5 2022, 14:08:36) [MSC v.1933 64 bit (AMD64)]
Pandas version:  1.4.3
FastAPI version:  0.84.0
Uvicorn version:  0.18.3
Windows 10 with VSC
FastAPI Version
FastAPI version:  0.84.0
Python Version
Python version:  3.10.7
Additional Context
No response

well to anyone stumbling across this thread with the same issue. I was able to resolve it...or it resolved itself. The only thing that has happened between now and posting this comment was i registered for the pro plan with flutterflow and paid for ngrok pro. I then used a custom domain with ngrok instead of the one provided by ngrok when using the free version. So my custom domain was "www.mydomain.api.ngrok.io" rather than the cryptic "www.ngrok.23-25-23-52-6a-3g.io". Once i did this it suddenly started working. I honestly do not know why but i have a theory that flutterflows servers only validate domains that are alpha characters and that ngroks complex temporary URL names mess up the flutterflow server. Wish i had a better explaination......i hope this helps someone out there.

Thanks for closing the issue 👍


Restrictions for the event name

This code will produce an exception:
const mitt = require("mitt")

const emitter = mitt()

emitter.on('constructor', e => console.log(1))
emitter.emit('constructor', {})

You may want to filter all those native methods out, or use a different approach of collecting the events.

Hmm - good call, this might be another reason to use set. Another interesting solution: prefix all types with : when storing them on the object.

@developit or you can use prototype-less objects with Object.create, which is supported in IE9.
Example for current code:
-all = all || {};
+all = all || Object.create(null);

More on this: http://www.2ality.com/2013/10/dict-pattern.html

That's a great idea, I used to use it in Preact. I guess I'd be fine with saying IE9+ instead of "literally any JS runtime" 🤠


Question: How do you make it seed-based so it is the same every time with the same seed?

How do you make it seed-based so it is the same every time with the same seed?
I have tried to use seedrandom.min.js and add Math.seedrandom(this.seed); It works, but when I resize the canvas, it changes.
EDIT: I tried out the fork made by @ToddAT but it still changes when the canvas size does.

I don't know the answer to your question but I'm curious — are you using the random point distribution or the grid distribution?

I am using sitesDistribution: 'hexagon'

Basically, I don't want anything "random".

If you set a new width and height in the config, the size of the perlin canvas will be resized to 1/3 of the island canvas. Try setting perlinWidth and perlinHeight to a fixed value.

Nope. Still changes.

Try setting sitesRandomisation and nbGraphRelaxation to 0 in the initial config.
This fork is seed based so you may want to look at it : http://luckylooke.github.io/phaser-islandjs-plugin/

That works! Thanks.


In angular cli v13 and angular material v13, getting double stars .

Description
Hi,
I am upgraded my angular application from angular v9 to angular v13 and all other angular frameworks in the app, step by step.
Commands used were -
npx @angular/cli@11 update @angular/core@11 @angular/cli@11  --allow-dirty --force

npx @angular/cli@11 update @angular/material@11 --allow-dirty --force

=======================
Till angular material v12, the application UI looked same. However, for angular cli v13 and angular material v13, there are double stars on mandatory fields (.i.e. 'required' fields) selected for a particular section.
And when we downgrade the material version of angular keeping rest all version the same to angular material v12, a star disappear.  And the UI is alright.
package.json file (one with the error)-
"dependencies": {
"@angular-devkit/schematics": "^13.3.1",
"@angular/animations": "^13.3.1",
"@angular/cdk": "^13.3.2",
"@angular/common": "~13.3.1",
"@angular/compiler": "~13.3.1",
"@angular/core": "^13.3.1",
"@angular/forms": "~13.3.1",
"@angular/material": "^13.3.2",
"@angular/material-moment-adapter": "^13.3.2",
"@angular/platform-browser": "~13.3.1",
"@angular/platform-browser-dynamic": "~13.3.1",
"@angular/router": "~13.3.1",
"@azure/msal-angular": "^0.1.2",
"@ng-bootstrap/ng-bootstrap": "^5.1.0",
"@ngx-translate/core": "^11.0.1",
"@ngx-translate/http-loader": "^4.0.0",
"@types/xrm": "^9.0.7",
"angular-xslt": "^0.2.1",
"angular2-notifications": "^9.0.0",
"aws-sdk": "^2.520.0",
"bootstrap": "^4.3.1",
"core-js": "^2.5.4",
"corsproxy": "^1.5.0",
"crypto-js": "^3.1.9-1",
"exceljs": "^3.6.1",
"file-saver": "^2.0.2",
"flag-icon-css": "^3.3.0",
"hammerjs": "^2.0.8",
"jquery": "^3.6.0",
"jwt-decode": "^2.2.0",
"material-design-icons": "^3.0.1",
"mime-types": "^2.1.24",
"moment": "^2.24.0",
"ngx-cookie": "^4.1.2",
"ngx-papaparse": "^4.0.4",
"popper.js": "^1.15.0",
"process": "^0.11.10",
"qz-tray": "^2.0.9",
"regenerator-runtime": "^0.13.3",
"rsvp": "^4.8.5",
"rxjs": "~6.5.5",
"rxjs-compat": "^6.5.2",
"sanitize-html": "^1.20.1",
"sha.js": "^2.4.11",
"stream": "0.0.2",
"timers": "^0.1.1",
"underscore": "^1.9.1",
"util": "^0.12.4",
"ws": "^7.0.0",
"xlsx": "^0.15.2",
"xml-js": "^1.6.11",
"zone.js": "~0.11.4"
},
"devDependencies": {
"@angular-devkit/build-angular": "^13.3.1",
"@angular-devkit/core": "^13.3.1",
"@angular/cli": "^13.3.1",
"@angular/compiler-cli": "~13.3.1",
"@angular/language-service": "~13.3.1",
"@nguniversal/express-engine": "^8.1.1",
"@types/file-saver": "^2.0.1",
"@types/jasmine": "~3.6.0",
"@types/jasminewd2": "~2.0.3",
"@types/jwt-decode": "^2.2.1",
"@types/node": "^12.11.1",
"codelyzer": "^6.0.0",
"grunt": "^1.0.4",
"grunt-bump": "^0.8.0",
"inquirer": "^7.0.0",
"jasmine-core": "~3.5.0",
"jasmine-spec-reporter": "~5.0.0",
"karma": "~6.3.17",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage-istanbul-reporter": "~3.0.2",
"karma-jasmine": "~4.0.0",
"karma-jasmine-html-reporter": "^1.5.0",
"pm2": "^4.1.2",
"protractor": "~7.0.0",
"tasksfile": "^5.1.0",
"ts-node": "~7.0.0",
"tslib": "^2.3.1",
"tslint": "~6.1.0",
"typescript": "~4.6.3"
}
I would like to ask would downgrading particularly, material v from 13 to 12 only would resolve the issue or shall downloading the entire angular framework dependencies and devDependencies version to 12 only would resolve the issue.
What is the affected URL?
No response
Please provide the steps to reproduce the issue
No response
Please provide the expected behavior vs the actual behavior you encountered
No response
Please provide a screenshot if possible

Please provide the exception or error you saw
No response
Is this a browser-specific issue? If so, please specify the device, browser, and version.
No. The issue is not browser specific.

Hi, this is the new default behaviour in form field. I think you have added your own asterisk to the template, it just needs to be removed.
If a form field control is marked with a required attribute, an asterisk will be added to the marker to indicate that it is a required field. If this is undesirable, this can be disabled by setting the hideRequiredMarker property to <mat-form-field>.

The explanation from @volvachev sounds like the likely root cause. Closing the issue, but it can be reopened if new information comes up.


[Feature Request] add support for fake location

This is how it is done with idevicelocation https://github.com/JonGabilondoAngulo/idevicelocation/blob/master/src/idevicelocation.c
Would love to see that here so that i can write a cross platform app to fake location on iOS device (an OSS one!)
Thanks

You can already do this in the current codebase, would you like a Rust example or were you asking if I would write a convenience struct?

Actually after reading this issue I came to the same conclusion that it was already possible. What I would ask from you is maybe help find the methods in rust corresponding to the method in c. Can you guide me a bit ?
And thanks a lot for your answer and this lib. It would(will) be a amazing thing to finally have an OSS project to fake location on iOS devices

Get a device by UDID
Create a service client
Send a string to the client

@jkcoxson So i have this in rust
let devices = match idevice::get_devices() {
    Ok(devices) => devices,
    Err(e) => {
      // If the daemon is not running or does not behave as expected, this returns an error
      println!("Error getting devices: {:?}", e);
      return;
    }
  };
  println!("Devices found: {:?}", devices);
  for device in devices {
    // Start an instproxy service on the device
    let mut lockdown_client = match device.new_lockdownd_client("idevicelocation".to_string()) {
      Ok(lockdown_client) => {
        println!("Successfully started lockdown_client");
        lockdown_client
      }
      Err(e) => {
        println!("Error starting lockdown_client: {:?}", e);
        return;
      }
    };
    let service =
      match lockdown_client.start_service("com.apple.dt.simulatelocation".to_string(), false) {
        Ok(service) => {
          println!("Successfully started service");
          service
        }
        Err(e) => {
          println!("Error starting service: {:?}", e);
          return;
        }
      };
      service.send("".to_string());
  }

Though it complains about the service not having a send method. I see in the doc that the result of start_service wont have a type. but how can i fix this?
Thanks again

Take that service that you created and put it into a service::ServiceClient. a ServiceClient is a generic service that you can call send on. As the docs say, [ServiceClient] is useful for services that don’t have abstractions and need to be handled manually

@jkcoxson thanks a lot i think i got it almost working. I am sorry but i still might need your help on one thing. I cant find how to pass a string to the ServiceClient::send method. I tried many things but none work. I end up with a Vec<u8> while the send method expects Vec<i8>

Hmmm I’m not sure if it would work without converting to a cstr, but you could try
let y = v.into_iter().map( |x| { x as i8 } ).collect::<Vec>().to_vec();
or something like that. I typed that on my phone.


Add a front-end test workflow

It's missing because for now, it's unnecessary. My goal is not to create a deployment build. Once we get to deployment, we'll add it.


How to run Emu2-gen with native pytorch?

Hi! I tried to run Emu2-gen with native pytorch.
from emu.diffusion import EmuVisualGeneration
from PIL import Image
import numpy as np
import cv2
import torch

pipe = EmuVisualGeneration.from_pretrained(
        "/data/lychen/code/decoding/emu2/Emu2-Gen_pytorch_model.bf16.safetensors", # "/home/lychen/.cache/huggingface/hub to Emu2-Gen_pytorch_model.bf16.safetensors",
        dtype=torch.bfloat16,
        use_safetensors=True,
)

I got error
Traceback (most recent call last):
  File "/data/lychen/code/decoding/emu2/Emu/Emu2/gen.py", line 7, in <module>
    pipe = EmuVisualGeneration.from_pretrained(
  File "/data/lychen/code/decoding/emu2/Emu/Emu2/emu/diffusion.py", line 257, in from_pretrained
    return cls(
  File "/data/lychen/code/decoding/emu2/Emu/Emu2/emu/diffusion.py", line 39, in __init__
    print(self.emu_model.load_state_dict(encoder, strict=False))
  File "/data/lychen/code/decoding/emu2/Emu/Emu2/emu/emu.py", line 236, in load_state_dict
    state_dict = torch.load(state_dict, map_location="cpu")
  File "/home/lychen/.local/lib/python3.10/site-packages/torch/serialization.py", line 986, in load
    with _open_file_like(f, 'rb') as opened_file:
  File "/home/lychen/.local/lib/python3.10/site-packages/torch/serialization.py", line 435, in _open_file_like
    return _open_file(name_or_buffer, mode)
  File "/home/lychen/.local/lib/python3.10/site-packages/torch/serialization.py", line 416, in __init__
    super().__init__(open(name, mode))
NotADirectoryError: [Errno 20] Not a directory: '/data/lychen/code/decoding/emu2/Emu2-Gen_pytorch_model.bf16.safetensors/multimodal_encoder/pytorch_model.bin'

You may use the huggingface version of code to load native pytorch version model. Please make sure you are using EmuVisualGeneration in here.

Thank you! I pulled the latest code and resolved the issue.


[CARBONDATA-2599]Use RowStreamParserImp as default value of config 'carbon.stream.parser'

Parser 'RowStreamParserImpl' is used more often for real scene, so use 'RowStreamParserImpl' as default value of config 'carbon.stream.parser'
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?

[x] Any backward compatibility impacted?

[x] Document update required?

[x] Testing done : already added before
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5269/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6312/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5150/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5270/

retest this please

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5152/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6314/

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6315/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5153/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6322/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5162/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5284/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6332/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5170/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6333/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5171/

@QiangCai @jackylk please help to review, thanks.

LGTM


v0.37.x TestTransportMultiplexAcceptNonBlocking is flaky

Bug Report
TestTransportMultiplexAcceptNonBlocking is flaky
Setup
ci
Config
ci
What happened?
I ran ci 40 times
What did you expect to happen?
tests should pass
How to reproduce it
use my branch
Logs
https://github.com/cometbft/cometbft/actions/runs/7388289351/job/20098837460?pr=1936

There is probably some underlying non determinism here.


Registration 2fa Code incorrect

Describe the bug

How To Reproduce

Expected behavior

2fa should be recorded and entering code should done set up
Screenshots and Videos

Server Information

OS: [e.g. Ubuntu 18, CentOS 7]
Java Version: Java18
Server Game Version: 1.19.4
Plugin Version: 1.6.3
Plugin List: -
Using Bungeecord? No
Loaded Bungeecord? No

Additional context

Fixed in 1.7.0


Error when sending a new account transaction.

I am using Dawn 4.2.  When I submit a new account transaction, I get an error about authorization for the eosio account. I submit this transaction:
eos.transaction(tr => {
  tr.newaccount({
    creator: "eosio",
    name: "acct1",
    owner: pubkey,
    active: pubkey
  });
});

I get this response.  I do not have a problem when a call cleos directly. I tried adding an authorization to the transaction but it did not allow that syntax.
api error => { message: 'transaction declares authority \'{"actor":"eosio","permission":"active"}\', but does not have signatures for it under a provided delay of 0 ms',
  file: 'authorization_manager.cpp',
  line_number: 405,
  method: 'check_authorization' } http://<IP_ADDRESS>:8888/v1/chain/push_transaction {"compression":"none","transaction":{"expiration":"2018-05-28T13:56:08","ref_block_num":52,"ref_block_prefix":292376965,"net_usage_words":0,"max_cpu_usage_ms":0,"delay_sec":0,"context_free_actions":[],"actions":[{"account":"eosio","name":"newaccount","authorization":[{"actor":"eosio","permission":"active"}],"data":"0000000000ea3055000000008090113201000000010003675ee3bd2f2421b9f66e501265516d78b5029c67375262b070025ec00ca7262a0100000001000000010003675ee3bd2f2421b9f66e501265516d78b5029c67375262b070025ec00ca7262a01000000"}],"transaction_extensions":[]},"signatures":["SIG_K1_K8uzyz3iVXEAEHP3Ko3TqmW8kt3ibqgpSs1Q2CyVCUDnqjoQhxgmTBRZeY7UVqd6JiRTiigp8A5kPYmTwZiPGErssyP3fP"]}
{ Error: {"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}
    at /home/max/dev/eosdev/eosride/app/node_modules/eosjs-api/lib/apigen.js:115:23
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:118:7) status: 500, statusText: 'Internal Server Error' }
{ Error: {"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}
    at /home/max/dev/eosdev/eosride/app/node_modules/eosjs-api/lib/apigen.js:115:23
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:118:7) status: 500, statusText: 'Internal Server Error' }
[push_transaction error] '{"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}', transaction '780a0c5b340085516d1100000000010000000000ea305500409e9a2264b89a010000000000ea305500000000a8ed3232660000000000ea3055000000008090113201000000010003675ee3bd2f2421b9f66e501265516d78b5029c67375262b070025ec00ca7262a0100000001000000010003675ee3bd2f2421b9f66e501265516d78b5029c67375262b070025ec00ca7262a0100000000'
{"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}
(node:23213) UnhandledPromiseRejectionWarning: {"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}
(node:23213) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:23213) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

write here your connection settings eos obj

How do I access that object? Here's how I'm setting the object up:
Eos = require("eosjs"); // Eos = require('./src')
binaryen = require("binaryen");

keyProvider = "5JhhMGNPsuU42XXjZ57FcDKvbb7KLrehN65tdTQFrH51uruZLHi";
pubkey = "EOS7ckzf4BMgxjgNSYV22rtTXga8R9Z4XWVhYp8TBgnBi2cErJ2hn";

eos = Eos.Localnet({ keyProvider, binaryen });

Is the same secret key in your local wallet (keosd)? What version of eosjs are you using? In the previous version of eosjs + dawn4.2 I also received this error, but I updated  eosjs and this solved issue

I have the same issue on<EMAIL_ADDRESS>It's likely related to: #131

It could be reated to #131.. try with the chain ID .. Eosjs v13 comes with a chain ID from the dawn 4.2 branch in github.  The community testnest will all very likely use a different chainId.
const chainID = 'a628a5a6123d6ed60242560f23354c557f4a02826e223bb38aad79ddeb9afbca'
eos = Eos.Localnet({ keyProvider, binaryen })

Re-test or close..

I will update and re-test this upcoming week. I can close for now and re-open if it occurs again.


[FLINK-1984] initial commit of hard constraint evaluator

This is related to the work in FLINK-1984.  In earlier patch sets, mesos constraints were evaluated, but that appears to have been dropped in the fenzo code, and now all constraint evaluators return null.
This is a start of exposing the fenzo constraint system, and only exposes a minimal subset of that functionality for now, hopefully in a way that allows it to be extended by later authors.
Signed-off-by: Stephen Gran<EMAIL_ADDRESS>

Thanks for this contribution, I'm glad to see Flink take advantage of Fenzo's considerable power.
Please open a new bug for this, since FLINK-1984 is closed, assign it to yourself, and update the PR description accordingly.    Mark the bug with 'Mesos' component.

I've closed this, opened a JIRA, and rebased the commit onto master.
The new PR is #3744


fix(CI): partially revert 404e649

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area CI
Does this PR require a change in the driver versions?
No
What this PR does / why we need it:
This PR partially reverts https://github.com/falcosecurity/libs/commit/404e6491b83944653b251cff29523bd2defe898e since KERNELDIR is still needed when using QEMU as you can see from this PR https://github.com/falcosecurity/libs/pull/1566.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 01e558c10a60b4d85510315b78a16c701439175d

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Fail on API error

Do not infinitely loop at least.

Is this referring to an error in the Twitter Streaming API connection?  If so, I may be experiencing the same problem.  I have it running 24x7 on Heroku and once every day or two, the connection to the Streaming API dies and does not reconnect.  I know very little (read: no) Scala, so first I'm working on instrumenting so I can pinpoint the issue.

Hi, that's possible. A bit of logs would help. Thanks!

Hi @rollulus!  Here are some logs.  Both startup of the process and the exception where it died.  I'm using the connector just as a Kafka Producer.  https://gist.github.com/crcastle/6f78b025d29840c626d9ba995a92850e
Does that help?

Thanks @crcastle, that is a bug we weren't aware of. I created its own issue #37.


Create a model to unit test

[ ] prompt
[ ] input keybord
[ ] define a prototype of test

created tests units using shell script and github actions


⚠ Bofrost.be has degraded performance

In a130b76, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1665 ms

Resolved: Bofrost.be performance has improved in 945b1ec.


Support for Monk's Enhanced Journal

Currently, when using this module with Monk's Enhanced Journal, the sidebar in the Journal Viewer is a similar colour to the text making it hard to read. Any chance you could alter the theme to fix that sidebar?

 XD
it's a lot of work, it will take me a while to integrate

Oh wow, when you said it'd be a lot of work, I didn't expect a release for it about a day later! Thank you very much!


Blender cask broken

Hi,
brew cask install blender is giving this error.
==> Verifying checksum for Cask blender
Error: It seems the App source is not there: '/usr/local/Caskroom/blender/2.78c/blender.app'
Error: nothing to install
Thanks

From the issue template that shows when opening a new issue:

Before opening your issue you must check our instructions for reporting bugs (…) [it] has several links to help diagnose and fix common issues.
(…)
if it is apparent you ignored the instructions for reporting issues, we may close the issue without review.

That seems to be the case, which is why I closed this issue. We worked hard  on those guides to keep things running smoothly, so I ask that you go back and follow them. It is OK to open a new issue for that.
If I was wrong in closing this issue, please do reply stating why! Closing an issue does not mean the conversation is over.
I understand sometimes we’re tired and don’t want to sift through a guide to make what we feel is a simple bug report. But when each user ignores the guides to save a few minutes, maintainers lose hours and get fatigued. I ask you take that into consideration.
Thank you for understanding.

https://github.com/caskroom/homebrew-cask/pull/30677/files


Creation date of the draft Conventions document

Currently the creation date of the draft version of the Conventions document is the same as the recentmost released version e.g. today the draft version of CF-1.11 is "version 1.11 draft, 31 August, 2022", even though a PR was merged earlier today.
I imagine that it would be possible to somewhere in the document build process dynamically assign the correct date. But I afraid that the technical aspects for making this happen is out of my reach.

I suppose that a simple fix for that is simply to delete the date in the working version. It can be replaced with some obvious placeholder, to be filled in when a new release is made. Would that be better?

Yes, that could work. Alternatively, we could have a date that is a placeholder in the AsciiDoc and gets turned into a date during build. I think this question is mostly for those responsible for the building, what they prefer.

I have played around with this and will shortly create a pull request. In addition to minor changes to the AsciiDoc file, the github workflow for creating the documents have to be slightly modified (details in the PR).

Hi Lars,
This looks good to me. I have tested it on my local build, and it looks fine for both HTML and PDF documents.
Might I suggest creating an environment variable for the resolved date that can be used in both HTML and PDF build commands? E.g.
    - name: Set draft date-time formatting
      if: github.event_name != 'release'
      run: |
        echo "docprodtime=-a docprodtime=$(date -u '+%d %B, %Y')" >> "$GITHUB_ENV"
    - name: Set "final" tag and date-time formatting
      if: github.event_name == 'release'
      run: |
        echo "FINAL_TAG=-a final" >> "$GITHUB_ENV"
    # Build cf-conventions.html using the Analog-inc asciidoctor-action
    - name: Build cf-conventions.html
      uses<EMAIL_ADDRESS>      with:
        shellcommand: 'asciidoctor --verbose ${FINAL_TAG} ${docprodtime} cf-conventions.adoc -D conventions_build; cp -r images conventions_build'
    # Build cf-conventions.pdf using the Analog-inc asciidoctor-action
    - name: Build cf-conventions.pdf
      uses<EMAIL_ADDRESS>      with:
        shellcommand: 'asciidoctor-pdf --verbose ${FINAL_TAG} -a docprodtime="$(date -u ${DATE_FMT})" -d book -a pdf-theme=default-theme-CF-version.yml --trace cf-conventions.adoc -D conventions_build'
    # Upload artifact containing cf-convent

Yes, indeed, the environment variable should be used for both builds. And I an see that you are using a more advanced one than I was [able to figure out], which simplifies the asciidoctor arguments.
However, by not creating this variable in the if: github.event_name == 'release' branch it will only work for building the drafts and not when building the final versions (if I am not mistaken ?).
In my version I used slightly different time stamp formats for the draft and final versions. The former included hh:mm:ssZ because I thought that maybe there could possibly be more than one version in one day, but this might very well overdo it. In the final version the time was not included.

I  experimented a bit with creating the docprodtime environment variable as per your suggestion, but I couldn't get it working in the github workflow (nor locally). Seems that I couldn't get the single and double  apostrophes right. As the current versions works I think that it is enough. What do you think @davidhassell ?

What works well locally seems not to work on the runner. The following error appears when building both the html and pdf:
date: invalid date ''+%d %B, %Y %H:%M:%SZ''

Hi Lars, Does the "invalid date" only appear when you introduce the environment variable? If so, then the other version that works is certainly fine by me.

It now works, see this screen clip:

The html and pdf documents produced when testing the PR are available for download as a zip file from the bottom of this page: https://github.com/cf-convention/cf-conventions/actions/runs/6955303266 (only useful for checking the outcome of the change).
The problem went away when I removed the apostrophes in the DATE_FMT assignments. With this I think the PR is ready to merge. @davidhassell would you mind having a final look and then merge is nothing more comes up?

Hi Lars,  Looks good - merging.


Implement dummy data importing for testing

Right now, when a new deployment is made to Heroku, a new database instance is created. It would be convenient to have a button to trigger import of dummy data so that testing of the app's UI and logic can be made easier

@tskir Some considerations about this issue.

Should we drop any pre-existing data before importing new ones? I'd say yes due to possible conflicts happening
How much data should we import for every model? I'm thinking we should import enough to cover any existing edge case, one or two for each possible status for example
Should we import dummy data for easily accessible cases? For example since there is an open PR on getting ZOOMA suggestions, should I create dummy suggestions as well?

Should we drop any pre-existing data before importing new ones? I'd say yes due to possible conflicts happening

Yes, it's OK to wipe the database

How much data should we import for every model? I'm thinking we should import enough to cover any existing edge case, one or two for each possible status for example

Agreed, just a few examples should suffice.

Should we import dummy data for easily accessible cases? For example since there is an open PR on getting ZOOMA suggestions, should I create dummy suggestions as well?

I'm not sure I got this entirely; what do you mean by 'easily accessible' cases?
Regarding the contents of dummy data, I think it should cover everything which is currently in the model (perhaps including already opened PRs like ZOOMA suggestions); and then every time we add something to the model/functionality which might require testing, we can update the dummy data in the same PR.
Essentially, think of the dummy data as a precursor to automated integration testing (which we will implement at some point).

I'm not sure I got this entirely; what do you mean by 'easily accessible' cases?
I mean that we can easily get unmapped trait names and mapping suggestions for traits using the already implemented ClinVar and ZOOMA queries. Should we have dummy data for those cases as well?

I'm not sure I got this entirely; what do you mean by 'easily accessible' cases?

I mean that we can easily get unmapped trait names and mapping suggestions for traits using the already implemented ClinVar and ZOOMA queries. Should we have dummy data for those cases as well?

Ah, I see. On the one hand, yes, for these cases it should be fine to use existing querying functionality and not to bother with explicitly specifying dummy data. However, for example for ClinVar, we can't rely on the top X records from the variants_summary file being the same every time, because the data gets updated frequently. If this doesn't matter for testing then we should be fine


NO Response from server when using Egrees

We have set up a server with livekit docker from the documents  ( self-hosting ).
The Services Run corectly on the server, But when start a new room, and generate it and pass token and secret token and server's url ( which starts with wss ) , using CLI, for sending an Egrees start composite, the recording does not start and returned 503, we tried to run it locally on an Ubuntu meachine but the same result.
We are using the latest Version of livekit service with Egrees and ingress from the docker run command in the docs.
Thank you.

Please do not duplicate issues across repos

Hi again Found That the Server cores where not meeting the required minimum so Yeah it is fixed.


shared_textures_3497.patch did not apply cleanly

I think because the 3497 branch has moved on since patch was originally created.
Attached is modified patch for 3497 branch that worked for me as at commit 13f506f9
shared_textures_3497-updated.zip

This issue doesn't need to be left open.  Only reason for logging it was in case updated patch is useful for someone else.


Incompatible library version: libvips-cpp.dylib requires version 10.0.0 or later, but libtiff.5.dylib provides version 9.0.0

What is the output of running npx envinfo --binaries --languages --system --utilities?
 System:
    OS: macOS High Sierra 10.13.6
    CPU: (4) x64 Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz
    Memory: 414.53 MB / 8.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 11.3.0 - /usr/local/bin/node
    Yarn: 1.12.3 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
  Utilities:
    CMake: 3.13.1 - /usr/local/bin/cmake
    Make: 3.81 - /usr/bin/make
    GCC: 4.2.1 - /usr/bin/gcc
    Git: 2.20.0 - /usr/local/bin/git
  Languages:
    Bash: 3.2.57 - /bin/bash
    Perl: 5.18.2 - /usr/bin/perl
    PHP: 7.1.23 - /usr/bin/php
    Python: 2.7.15 - /usr/local/bin/python
    Ruby: 2.3.7p456 - /usr/bin/ruby

After an update from sharp 0.20.8 to 0.22.0 I got this unexpected error while running my application. It looks funny, I though that sharp was using its own libraries stored in the vendor directory, so I don't understand if this is related to some other libtiff library present.
I use     "electron-builder": "20.39.0",  to pack everything together, this is the error I get launching: electron-webpack dev
Error: dlopen(/Users/bianco/Src/AppWebPack/node_modules/sharp/build/Release/sharp.node, 1): Library not loaded: @rpath/libtiff.5.dylib
    Referenced from: /Users/bianco/Src/AppWebPack/node_modules/sharp/vendor/lib/libvips-cpp.42.dylib
    Reason: Incompatible library version: libvips-cpp.dylib requires version 10.0.0 or later, but libtiff.5.dylib provides version 9.0.0
      at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:160:31)
      at Object.Module._extensions..node (internal/modules/cjs/loader.js:722:18)
      at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:160:31)
      at Module.load (internal/modules/cjs/loader.js:602:32)
      at tryModuleLoad (internal/modules/cjs/loader.js:541:12)
      at Function.Module._load (internal/modules/cjs/loader.js:533:3)
      at Module.require (internal/modules/cjs/loader.js:640:17)
      at require (internal/modules/cjs/helpers.js:20:18)
      at bindings (/Users/bianco/Src/AppWebPack/node_modules/bindings/bindings.js:112:48)
      at Object.<anonymous> (/Users/bianco/Src/AppWebPack/node_modules/sharp/lib/constructor.js:10:34)

Hello, has libtiff (or vips) been installed globally via Homebrew? If so, has brew update && brew upgrade been run?
Are there any other native dependencies of your Electron app that might require libtiff?

hello,
updating the globally installed libtiff doesn't make any difference, I don't have visp installed.
I have another native dependency that require libtiff, I am trying to update that also. It is weird anyway that there is a conflict between the two, since they have different paths

Whichever dependency requires their libtiff shared library first will "win" for this is the shared library game.

The issue is solved updating the libtiff in the other native dependency. Thanks for the support!


Help me !!!

The new 3.0.0 version of Inspy is hard to use. I need examples of using methods.  What will we do ? I can not use --emspy
Please help me?

Hello, @yigitozdamar ,
I ran through around an hour of troubleshooting and i have it successfully searching, but as @gojhonny knows, LinkedIn has changed their protocols to prevent this tool at the moment, rendering 0 searches on any and every domain combination.
As for your example, as long as you have everything set up correctly so far, here's the example you wanted using google:
./InSpy.py Google --domain www.google.com --email<EMAIL_ADDRESS>--titles ./wordlists/title-list-small.txt
You'll notice that you now have the option to input specific domains, emails, titles, and also the option for the output files exclusively.


LGTM, can we even have the required api routes here related to users and the middleware here, so that we can  have everything at one place
@PrakharSinha-09, can you talk with @Janith-Chamikara and take some of the tasks and work parallely?
So that we can pace it up.
UI @Mohitsen11 is working, so we need to get pieces together, likely after 2 days

@Janith-Chamikara Can you kindly update where are placed now and how long will it take to complete this complete backend feature.. UI is almost ready, thanks to @Mohitsen11

Declining as duplicate of https://github.com/krishnaacharyaa/wanderlust/pull/129


Add context menu to master deploys

Fixes #69

This change is

Deployed : https://cdn.vaadin.com/vaadin-core-elements/master/vaadin-core-elements/

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


[AutoPR] cdn/resource-manager

Created to accumulate context: cdn/resource-manager

@AutorestCI rebase

Rebase done and pushed to the branch

@AutorestCI rebuild https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cdn/resource-manager/readme.md

Working on generating https://github.com/azure/azure-rest-api-specs/blob/master/specification/cdn/resource-manager/readme.md for you!!!

Build SDK finished and cleaned

Codecov Report

Merging #2137 into master will increase coverage by 0.04%.
The diff coverage is 55.39%.

@@            Coverage Diff             @@
##           master    #2137      +/-   ##
==========================================
+ Coverage   56.01%   56.06%   +0.04%
==========================================
  Files        6850     6901      +51
  Lines      146483   146955     +472
==========================================
+ Hits        82058    82387     +329
- Misses      64425    64568     +143

Impacted Files
Coverage Δ

...ure/mgmt/cdn/models/cdn_management_client_enums.py
100% <100%> (ø)
:arrow_up:

azure-mgmt-cdn/azure/mgmt/cdn/version.py
100% <100%> (ø)
:arrow_up:

azure-mgmt-cdn/azure/mgmt/cdn/models/__init__.py
100% <100%> (ø)
:arrow_up:

...e/mgmt/cdn/models/check_name_availability_input.py
100% <100%> (ø)
:arrow_up:

...e/mgmt/cdn/operations/resource_usage_operations.py
39.39% <100%> (ø)
:arrow_up:

...e-mgmt-cdn/azure/mgmt/cdn/operations/operations.py
41.93% <100%> (ø)
:arrow_up:

...t/cdn/models/check_name_availability_output_py3.py
100% <100%> (ø)

...mt/cdn/models/check_name_availability_input_py3.py
100% <100%> (ø)

...azure/mgmt/cdn/operations/edge_nodes_operations.py
41.93% <100%> (ø)
:arrow_up:

.../mgmt/cdn/models/check_name_availability_output.py
100% <100%> (ø)
:arrow_up:

... and 134 more

Continue to review full report at Codecov.

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


[Feature Request] Provide capability for not adding top docs collector in the query search path

Is your feature request related to a problem? Please describe
Right now as part of search code path both Default and Concurrent QueryPhaseSearchers are adding TopDocsCollector as first collector in the chain (code ref1 DefaultQueryPhaseSearcher, code ref2 ConcurrentQueryPhaseSearcher).
In case of certain types of extensions that may lead to a performance degradation of search. In particular that's true if custom collector and collector manager are added and those collectors are used in a way that scores are collected with a custom logic. In such case some compute (like filtering) will be done twice and depending on the extension logic that can be a thrown away work.
Example of such extension is hybrid query. Please check collector manager and collector added in neural-search plugin.
Describe the solution you'd like
I suggest core add an interface or method in existing QueryPhaseSearcher interface (or public core class QueryPhaseSearcherWrapper) that allows extension or plugin to set a flag and depending on that flag the top docs collector will be added or skipped. Default implementation should allow adding of topdocscollector so system is backward compatible.
Related component
Search
Describe alternatives you've considered
Right now there isn't much of alternatives, custom collector is executed after the top docs collector. This leads to performance degradation of search queries, that has been submitted to us by multiple customers.
Additional context
Custom query collector and collector manager were added as part of the neural-search plugin in 2.13 release (original PR)

@martin-gaievski I don't think we need to modify QueryPhaseSearcher but if needed you could (and probably should) provide your own implementation of  QueryPhaseSearcher::searchWithCollector

@reta if we modify the QueryPhaseSearcher::searchWithCollector then we will miss out on the optimizations/other functionalities happening in the SearchWithCollector functions or any new functionality that is getting added there.

I suggest core add an interface or method in existing QueryPhaseSearcher interface (or public core class QueryPhaseSearcherWrapper) that allows extension or plugin to set a flag and depending on that flag the top docs collector will be added or skipped. Default implementation should allow adding of topdocscollector so system is backward compatible.

On this I would suggest we can have a function returns the topDocsCollector instance, rather than a flag which says topdocscollector should be added or not.

On this I would suggest we can have a function returns the topDocsCollector instance, rather than a flag which says topdocscollector should be added or not.

@navneet1v we may have an overloaded version:
        protected boolean searchWithCollector(
            QueryCollectorContext  queryCollectorContext,
            SearchContext searchContext,
            ContextIndexSearcher searcher,
            Query query,
            LinkedList<QueryCollectorContext> collectors,
            boolean hasFilterCollector,
            boolean hasTimeout
        ) throws IOException {
            ...
        }

The current searchWithCollector(...) would delegate to new  searchWithCollector(...) with TopDocsCollector instance.

@navneet1v we may have an overloaded version:

@reta when you say we may have an overload version, are you saying we already have it? or we can build such a version? Little confused here.

@navneet1v sorry, I should have been more clear: we could add the overloaded version (no flags or functions).

@navneet1v sorry, I should have been more clear: we could add the overloaded version (no flags or functions).

Thanks. I myself don't agree with flags. But we can do override functions. :D Thanks @reta for helping out here.
@martin-gaievski can we start making the change.

It would be great if you folks can confirm my understanding of the approach with new overloaded function with additional param QueryCollectorContext:

the way we can skip top docs collector in custom implementation is if return null for TopDocsCollectorContext, in such case it will not be added to the list of collector context objects LinkedList<QueryCollectorContext> collectors
function searchWithCollector(...) is part of both ConcurrentQPS (QPS stands for QueryPhaseSearcher) and DefaultQPS, not the QueryPhaseSearcher interface. To be able to take advantage of that overloaded function we need to extend both implementation of core QPS
2 means that we need to use our implementations instead of those used in core today. For that we need to override searchWith from QueryPhaseSearcherWrapper in the plugin.

the way we can skip top docs collector in custom implementation is if return null for TopDocsCollectorContext, in such case it will not be added to the list of collector context objects LinkedList collectors

:+1

function searchWithCollector(...) is part of both ConcurrentQPS (QPS stands for QueryPhaseSearcher) and DefaultQPS, not the QueryPhaseSearcher interface. To be able to take advantage of that overloaded function we need to extend both implementation of core QPS

That is correct, QueryPhaseSearcher is unchanged, the idea is to allow reusing the implementation only

2 means that we need to use our implementations instead of those used in core today. For that we need to override searchWith from QueryPhaseSearcherWrapper in the plugin.

I think no, the implementation would follow this chain: searchWithCollector -> searchWithCollector -> new overloaded searchWithCollector, so you would only need to override searchWithCollector to pass null as queryCollectorContext

@martin-gaievski i know you did some deep-dive on the impact of having topdocs collector and hybrid search collector both running. Can you paste the flame graph and benchmark results here for visibility.

Sure Navneet, after we've implemented one optimization on plugin side I got following numbers :
One sub-query that selects 11M documents

Bool: 84.7201
Hybrid: 256.799

One sub-query that selects 1.6K documents

Bool: 89.6258
Hybrid: 85.4563

Three sub-query that select 15M documents

Bool: 90.1481
Hybrid: 326.331

Based on profiling info (flamegraphs are attached) 45 to 80% percent of CPU time taken by the TopDocsCollector related methods, mainly by collect method.

For reference: benchmark is done for 2.13 using noaa OSB workload. Following search queries used for benchmark
Bool queries:
Query 1
        "size": 100,
        "query": {
          "bool": {
              "should": [
                  {
                      "term": {
                          "station.country_code": "JA"
                      }
                  },
                  {
                      "range": {
                          "TRANGE": {
                              "gte": 0,
                              "lte": 30
                          }
                      }
                  },
                  {
                    "range": {
                        "date": {
                            "gte": "2016-06-04",
                            "format":"yyyy-MM-dd"
                        }
                    }
                  }
              ]
          }
        }

Query 2
        "size": 100,
        "query": {
          "bool": {
              "should": [
                  {
                      "range": {
                          "TRANGE": {
                              "gte": -100,
                              "lte": -50
                          }
                      }
                  }
              ]
          }
        }

Query 3
        "size": 100,
        "query": {
          "bool": {
              "should": [
                  {
                      "range": {
                        "TRANGE": {
                          "gte": 1,
                          "lte": 35
                        }
                      }
                  }
              ]
          }

equivalent hybrid queres are:
Query 1
        "size": 100,
        "query": {
          "hybrid": {
            "queries": [
                {
                    "term": {
                        "station.country_code": "JA"
                    }
                },
                {
                    "range": {
                        "TRANGE": {
                            "gte": 0,
                            "lte": 30
                        }
                    }
                },
                {
                  "range": {
                      "date": {
                          "gte": "2016-06-04",
                          "format":"yyyy-MM-dd"
                      }
                  }
                }
            ]
          }
        }

Query 2
        "size": 100,
        "query": {
          "hybrid": {
            "queries": [
                {
                    "range": {
                        "TRANGE": {
                          "gte": -100,
                          "lte": -50
                        }
                    }
                }
            ]
          }

Query 3
        "size": 100,
        "query": {
          "hybrid": {
            "queries": [
                {
                    "range": {
                      "TRANGE": {
                        "gte": 1,
                        "lte": 35
                      }
                    }
                }
            ]
          }

Thanks martin for providing the details. Let start working on the POC to remove the topdocsCollector and see how much improvement we can get here.

Is there a scope of making this work little more generic?
I mean like to disable or enable any collector?

I mean like to disable or enable any collector?

@vibrantvarun  I don't think the idea is to enable or disable any collector, instead the QueryCollectorContext could be provided w/o query collectors. In that sense, the solution is generic.


Baklava in Lua

Hereby adding the iconic Baklava in Lua.

@toturkmen If you have time please :)

Hello, Ümit! Sorry for delay. 🙏🏻 I merge your pull request. Thank you so much for contributing.


Replace usage of time crate with chrono

Summary of changes

Changes introduced in this pull request:

Replace all usages of time crate (note: this crate differs from core::time, std::time, and tokio::time) with chrono crate

Reference issue to close (if applicable)

Closes #2664
Other information and links

N/A
Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Maybe we could also ban time:: usage in .clippy.toml

Is it possible to ban an entire crate? In .clippy.toml, I only see ways to ban specific types/methods. If not, maybe it could be something we configure in one of the dependencies check scripts. I'll open a new issue to research it.


goog.graphics.SolidFill's opt_opacity fails on zero value

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=131

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


Sort channels in lexicographical order in packagemanifest

Description of the change:
Motivation for the change:
Architectural changes:

Testing remarks:

Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Bug fixes are accompanied by regression test(s)
[ ] e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
[ ] tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
[ ] Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive
[ ] Tests marked as [FLAKE] are truly flaky and have an issue
[ ] Code is properly formatted

Nice! Should we add a test for this to avoid regressions?


Dynamically add Data Needed to Customer by DR

I like the dynamic way how a detection rule is able to declare the data
needed part.
This change will extend the list of DN for a customer depending on the
detection rules which are applied to the customer.

Hello @andurin!
This functionality looks pretty good, at the same time it interferes with the idea behind the Customer entity.
Let me explain in detail and provide you with a solution.
The Idea behind the Customer entity
The Customer entity originally was created to track the deployment/implementation of Detection Rules.
For example, you have configured specific Logging Policies in one Customer's environment.
You can export the current state into elasticsearch index, and highlight what Data Needed you will get now (in Kibana).
Then you can put there Data Needed, and rebuild the es index, then highlight what Detection Rules you can deploy with this data. Then track implementation — what detection rules have been implemented, what detection rules could be implemented but haven't implemented yet.
So if we will automatically calculate Data Needed, that will break this idea.
The win-win solution
I think that many of our users could benefit from your idea.
What do you think about creating an extra option in the configuration file, that will enable the function you've developed?
Something like:
automatically_map_data_needed_to_detection_rules_in_customer_entity: True

This way people that would need this, would be able to enable it in the config and it will not interfere with the original idea (:


AoA: Localization of HuntPrey

Changed Dmiri Yoltosha and Duergar Slave Lord: Set RuleElement of Hunt Prey to Localization via re-en.json

On another monster, yes. So, do I need to combine these two to use the same Label ID?
Gesendet von Mail für Windows
Von: TikaelSol
Gesendet: Sonntag, 24. Juli 2022 16:29
An: foundryvtt/pf2e
Cc: Manni; Author
Betreff: Re: [foundryvtt/pf2e] AoA: Localization of HuntPrey (PR #3103)
@TikaelSol commented on this pull request.
In static/lang/re-en.json:

@@ -467,6 +467,9 @@
"BittersweetDreamsCriticalFailure": "Critical Failure",
"BittersweetDreamsSuccessFailure": "Success or Failure"
},

       "DuergarSlaveLord": {

           "FirstHitDamage": "First Hit on Hunted Prey of the round"

I think we have this exact note elsewhere, no?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Yeah, before we do a release let's just make a generic NPCAbility section with HuntPrey under it and consolidate. No sense in duplicating text here.

Oh, we already have hunt prey in there, just throw everything under that.


make RuntimeEngine nullable for proper serialization #143

When creating a new ClusterAttributes object, if the runtime_enigne is being set to Photon it does not get serialized. I believe it is ignored in the ApiClient because of the JsonSerializerOptions where DefaultIgnoreCondition is set to JsonIgnoreCondition.WhenWritingDefault, and when setting that value to 0 (RuntimeEngine.Photon) it just ignores it. Setting it to RuntimeEngine.Standard (1) works.
I think the RuntimeEngine enum can be made nullable since the API documentation states that if left unspecified, the runtime engine is inferred from spark_version.
Issue #143

/azp run

/azp run

LGTM.


Fix incorrect link path and add TRPG Engine Logo

Changes

Fix Incorrect link in Here

and added my project logo append here
Testing

Docs

Thank you!


Prepare 2.0.0 release

There has been done major contributions to the codebase both by you the users and me as a developer.
I feel we have come to a point where i need to make a list of things that needs to be done/fixed before we can officially go live with a community supported version.

Documentation needs to be updated especially installation and Configuration and first login

Datasource defintions is now only one datasource and i need to remove config and update code to represent this.

Automatic docker image publishing when travis runs

With these in place i will be confident enough to make a major release.
And if we find more bugs before release we just fix them

Automatic docker image publishing when travis runs
Done

Release is dependending on #135 to be resolved.

Hi, Jarl. I'm not sure how to report correctly the issue I met on 2.0.0, so I will post here for a while. Maybe you will help to sort it out:
TR069 conversations log is empty, as well as tr069 events log. I installed new release by dpkg -i over old RC..19 with config files replacement (answer Y when asked). Then I added quirks for my test device, but failed to get it working. Then I noticed there is no conversation in log.
After that I decided to delete unit and create it again. I added new unit of existing type and profile, but it didn't help

Interesting. Might be logback. I will check. There should be a logback file in config. I think i set root level on tr069 to logback (same as for all other modules) but conversation and event and stuff should override. I will check

2.0.0 release was success.


Sketch 3.5 support

Replaced resizeRoot with resizeToFitChildrenWithOption
Reference: http://mail.sketchplugins.com/pipermail/dev_sketchplugins.com/2016-January/001765.html

thank you so much~


PDFObjRef  instead of int

I've encountered bug during extracting pages using extract_pages() (pdfminer.high_level).
I already found a solution so I will create pull request with it.
Image below provides this bug:

pdfminer version: 20221105
pdf to recreate bug:
pdf_bug_1.pdf

Confirmed, could replicate the bug

Would love to see your PR on this :)

PR #834
https://github.com/pdfminer/pdfminer.six/pull/834#issue-1453253203


Report usage of deferred-components to analytics.

Towards https://github.com/flutter/flutter/issues/159212.
/cc @jtmcdole

As long as we aren't sending events for a new tool that isn't covered by the PDD or sending any PII in event data for an existing tool, then there is no issue with sending new analytics events. 👍


why are you useing at logo

https://at.govt.nz/

because it looks cool
but yes, didnt check, i thought it's not commercial
logo will be changed in a few days

done btw


[Graph algorithm] : Bellman-Ford Algorithm

We need implementation of Bellman-Ford Algorithm.
Files are located in ./src/Graph Algorithms/Bellman-Ford.cpp

Hi, can I be assigned to this? I can implement DFS and BFS.

Sure @sally-golding

@sally-golding  we've moved each algorithm to it's corresponding issue.
Find BFS and DFS at #23 and #24


Can i work with you ?

@IDKiro  if pssoble please let me

If you are referring to collaborating on new research, that's not possible. My superiors prefer to keep subsequent technologies confidential. SDXS might not receive any updates and might not even be submitted to any conferences or journals.


[DOCS]: added ts defs documentation

Should help show people how to manually wire up type defs

Thanks!


fix cloud-init schema validation error when {{ growpart_str }} is not empty

{{ growpart_str }}, when is not empty, breaks cloud-init schema validation.
This is easily fixed by moving {{ growpart_str }} up in the template file.

Thanks for the PR! It seems that I moved that section to the wrong place in one recent update. Are you using microOS for your cluster?

Yes, I’m using microOS for the cluster nodes. I had to hardcode an extra environment variable into ‘master_install_script.sh’ and generate a new binary to make the installation work, though. Maybe I’ll open a new issue with the details.

That would be nice, thanks!


assess which wallets we want to support

for now we support only Anchor...
Which ones should we support?

Scatter
Wombat
Lynx
etc..

One of the new UALProvider authenticators is erroring out. In dev mode, it's loud (see below). I don't think it impacts user experience in prod mode though. But it is annoying in dev mode.

I think it's Scatter. Not sure.


New mysql 8.0 got error

With mysql r39-6
I got this error when I try to load a gamemode
[00:44:11 06/03/21] [ERROR] CMySQLConnection::Connect - (error #2059) Authentication plugin 'caching_sha2_password' cannot be loaded: /usr/lib/mysql/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory

Create another database user account with standart authentication and use this account to connect to database.


github actions for marking issues and PRs as stale

Modified version of the configuration for actions/stale from SciTools/iris
More info on the action here: https://github.com/actions/stale
To be discussed:

Choosing a suitable number of days before the action will assign the "Stale" label to a issue/PR (60 days right now).
Choosing a suitable number of days after issue/PR being marked as stale before issue/PR is actually closed (30 days right now).
Any further label exclusions?

Hopefully will work (permissions on improver repo. setup to allow).

Thanks @BelligerG.  We can similarly target improver_suite and paraflow.
@bayliffe, are you happy with the proposed timescales and label exceptions?
cheers

@bayliffe, @tjtg thanks for getting involved in this.
You have both raised valid concerns over dealing with issues.  There are a range of ways in which concerns can be addressed but as @tjtg rightly points out, these have implications on workflow.
I'm going to suggest we limit this to dealing with 'stale' PRs for now (assuming that is not controversial, @tjtg do chime in) and we then discuss the potential of handling issues offline later?
Cheers

I'm all for the PR closure. I'd be happy with a shorter period before marking them as stale, say 30 days, then closure 30 days after that, but if that's a bit too short, I'm happy with 90 days. - @bayliffe

I might agree - I was being conservative.
I think we might better off discuss lowering the current threshold when we also discuss the potential for handling issues with BOM and USAF (in future meeting).
Ready for review.
ping @tjtg

@bayliffe / @BelligerG, you still happy to approve? :)

Thanks everyone.  Fingers crossed this works :)


Upstream sync

Codecov Report

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


[Map] DM-(BULL)_Voyeur

Hash: 66f801c39f1f28271dc77e31fd988424e442e062
Current name: DM-(BULL)_Voyeur
The author's name here should be added to the Bulldozer alias file

Done


feat(RCSET-11195): Adding sdlc_snyk_container_scan

Context
The security team at OutSystems (Host & Network Security) has implemented image scanning at the repository level to enhance the security of the image build process.

Communications regarding this have been constantly provided and certain teams have added this image scanning as a workflow to their repository
We have identitifed this repository to be out-of-compliance by not implementing this workflow
So we are creating this branch by adding the necessary workflow configuration to integrate image scanning seamlessly into the development process.

What to do next:

[ ] DONOT Merge this PR
[ ] Git pull this branch
[ ] Modify the workflow file name FROM security_sdlc_snyk_container_analysis.yaml TO sdlc_snyk_container_analysis.yaml so that you can control this file
[ ] Commit the changes
[ ] Push the changes
[ ] Create a PR
[ ] Merge the PR
[ ] Delete the branch

If your PR is blocked by a CRITICAL/HIGH vulnerability that is fixable, you can ignore it for a fixed period of time by following this process

Jira Issue
RCSET-11195
Impacts

[ ] Refactor (big refactor on a sensitive asset )
[ ] Requires revision on public documentation
[ ] Breaking Change

[ ] Behavioral breaking change
[ ] Breaks existent APIs

[x] Workflow will block all your PRs if snyk identifies a CRITICAL/HIGH vulnerability that can be fixed.

Information on how to work with this workflow can be found here  https://docs.google.com/presentation/d/1-nxFjpZ-p6HoGMRV-y3zttAiuWCUho8Z6wE_nFn2MEM

Code Checklist

[x] Tested
[x] Documented

Note:

If merging is blocked by The base branch requires all commits to be signed
please use the option Merge without waiting for requirements to be met (bypass branch protections) to bypass.

How to contact us

Slack us : https://outsystems.slack.com/archives/C06PSDG4ZSL

This repository does not push images to Eden. I will add the exemption topic to be added here.


chore: release main

:robot: I have created a release beep boop
0.7.1
0.7.1 (2024-06-22)
Bug Fixes

dont release chart before building images (#390) (b0a3abd)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

0.7.1
:sunflower:


chore: move overlays to root in sync script

For RHTAP the Dockerfile needs to be in one of a limited set of locations. The easiest to deal with is at root.
Moving Dockerfile to ./overlays instead of ./overlays/cosign so that we can just have a generic move of all files under overlays and any directory structure is copied, instead of picking files from specific directories and moving them.

/lgtm

/lgtm

/lgtm


Support passing optional options argument to resize action

The ResizeObserver Web API supports an optional options object on .observe().
Being able to pass such an options object in the config would allow for picking the desired box model the observer will observe changes to, which is highly desirable in some situations.
Currently use:resize is restricted to content-box, the API's default, which returns the size of the content area as defined in CSS. Other models supported by the WebAPI are:

border-box Size of the box border area as defined in CSS.
device-pixel-content-box The size of the content area as defined in CSS, in device pixels, before applying any CSS transforms on the element or its ancestors.

Now available in<EMAIL_ADDRESS>


Touch Device input always binds to top left coordinates of the bound dispay

Regression?
Yes
System Info and Version
 System/Version info
Version info
$ hyprctl version
Hyprland, built from branch main at commit b672118f9238a48a18efd741cbcda387c5552238  (xwayland: deactivate xwayland focus if wayland is focused (7458)).
Date: Sun Aug 25 16:37:03 2024
Tag: v0.42.0-67-gb672118f, commits: 5136
flags: (if any)
# OS: Arcolinux (Arch-based)
# Kernel: 6.10.6-zen1-1-zen

Monitor configuration
#   ########################################
#  ###    Monitors, Displays, etc.                                        ###
# #########################################
# Configure your Display resolution, offset, scale and Monitors here, use `hyprctl monitors` to get the info.
# See https://wiki.hyprland.org/Configuring/Monitors/

# Enable auto-rotation (requires `iio-hyprland`)
 exec-once = iio-hyprland

#   ###################
#  # Default Monitor config #
# ####################
 monitor     =           , preferred   , auto               , 1                           # Extend, Balanced resol/refresh
#monitor     =           , highres     , auto               , 1                           # Extend, Maximum resolution
#monitor     =           , highref   , auto               , auto       , mirror , DP-2    # Mirror, maximum refresh rate

#   #################
#  # Multi-Monitor Setup #
# ##################
# Offset for 2x(16:9,27',horizontal) & 1x(16:9,24',vertical) monitors
#  -> NOTE: scaling on xwayland does not work well and will lead to bad text representation
 $dp_abs_offset = 420               # 420 ~ ( max_H - min_H )
 $dp_h_scale    = 1.2               # 1.2 ~ $dp_abs_scale * ( $monitor_max_scale / $monitor_min_scale )
 $dp_h_offset   = 275               # 240 ~ ( 1 / $dp_hp_scale) * $dp_abs_offset

# monitor (use `[Win] + [M]` for quick monitor infos)
 monitor     =            eDP-1    , 1920x1080@60 , -200x-200             , 1           , transform, 0, vrr, 1 # , bitdepth , 10
   workspace = 1, monitor:eDP-1    , default:true
# External usb-c monitor
#monitor     =            DP-1     , preferred    , auto             , 1           , transform, 3, vrr, 1
#  workspace = 2, monitor:DP-1     , default:false
# External HDMI monitor
#monitor     =            HDMI-A-2 , preferred    , auto             , 1           , transform, 0, vrr, 1
#  workspace = 2, monitor:HDMI-A-2 , default:false

# Set primary monitor (solves some xwayland window placement issues)
exec-once = xrandr --output eDP-1 --primary

# "Fix" wayland scaling issues
xwayland {
  force_zero_scaling = true
}

# ...

#   ##############################################
#  ###    HW Device specific rules (window rules)                         ###
# ###############################################
# See https://wiki.hyprland.org/Configuring/Variables/#input

# Laptop Touchscreen
$TOUCH_ENABLED = false
device {
  name=wacom-pen-and-multitouch-sensor-finger
  enabled = $TOUCH_ENABLED
}

# Laptop touchpad
device {
    # https://github.com/hyprwm/Hyprland/discussions/4283?sort=new
	name=elan-touchpad
    #speed = 1.0
	enabled = true
}

# ...

Current detected device & monitor configuration
$ hyprctl monitors
Monitor eDP-1 (ID 0):
<EMAIL_ADDRESS>at -200x-200
	description: BOE 0x075F
	make: BOE
	model: 0x075F
	serial:
	active workspace: 2 (2)
	special workspace: 0 ()
	reserved: 0 37 0 0
	scale: 1.00
	transform: 0
	focused: yes
	dpmsStatus: 1
	vrr: 0
	activelyTearing: false
	disabled: false
	currentFormat: A XRGB8888 H XRGB8888
	availableModes<EMAIL_ADDRESS>
$  hyprctl devices

# ...

Tablets:
	Tablet at 6246db8e9630:
		wacom-pen-and-multitouch-sensor-pen
			size: 293.76x165.24mm

Touch:
	Touch Device at 6246db689ed0:
		wacom-pen-and-multitouch-sensor-finger

# ...

Description
Issue

(Enabled) touch dislay always triggers touch input on coordinates of the bound display (e.g. 0x0) regardless of where the screen is touched

This is a hyprland issues as libinput  debug-gui correctly displays the touch input position.
Expected behaviour

Touch is registered where finger touches screen

Notes

I had this working knowingly about half a year ago (maybe even 3 months ago) on my system out of the box without setup required.
I tested moving the display to -200x-200, the toch isstill  registered at (0,0)
I had used arcolinux as a base for setting up my system and modified the configurations for myself, a detailed configuration for my system can be found here.

My Lenovo Yoga L390 has the following hardware:
CPU: Intel i5-8265U (8) @ 3.900GHz
GPU: Intel WhiskeyLake-U GT2 [UHD Graphics 620]
Ram: 16 Gib

How to reproduce
Monitor is bound to position 0x0 (hyprland.config) > Toch on display anywhere (touch at (0,0) will open my app-menu) > App menu will open.
Crash reports, logs, images, videos
https://github.com/user-attachments/assets/46dfa4b0-9d5d-4317-a17a-e2370397d228
Note: In the video I display the touchscreen input issue via libinput debug-gui and i "enable" and "disable" the touchpad, this is done via the following script:
#!/usr/bin/env bash
# see: https://www.reddit.com/r/hyprland/comments/1bqohmd/dynamically_enabledisable_device/

export TOUCH_DEVICE="wacom-pen-and-multitouch-sensor-finger"

enable_touchpad() {
    notify-send -u normal "Touchpad enabled"
    hyprctl keyword input:touchdevice:enabled true
    hyprctl keyword "device[$TOUCH_DEVICE]:enabled" true
}

disable_touchpad() {
    notify-send -u normal "Touchpad disabled"
    hyprctl keyword input:touchdevice:enabled false
    hyprctl keyword "device[$TOUCH_DEVICE]:enabled" false
}

if [ "$(hyprctl getoption input:touchdevice:enabled | grep int | awk '{print $2}')" == "1" ]; then
  disable_touchpad
else
  enable_touchpad
fi

unset TOUCH_DEVICE

Update

Confirmed (on my device: Yoga L390) touchscreen is working as expected after uprgading  hyprland 0.44.1 hyprlang 0.5.3-1 libinput 1.26.2-1 xf86-input-libinput 1.4.0-2

$ hyprctl version
Hyprland, built from branch  at commit 4520b30d498daca8079365bdb909a8dea38e8d55  (version: bump to 0.44.1).
Date: Wed Oct 9 12:54:39 2024
Tag: v0.44.1, commits: 5309
built against aquamarine 0.4.2

flags: (if any)