Flaky Fuchsia failures cause frequent tree closures.

An example of such failures is https://chromium-swarm.appspot.com/task?id=4f32a561503b9b10. Currently, a substantial number of recent failures on Fuchsia are due to this error.

The error looks like a machine is unreachable
ssh: connect to host fd5d:df04:d8c7:0:73b7:3bb5:6468:26a7 port 22: Network is unreachable

cc @chaselatta

There was a recent netstack change which was causing connection failures. The change is being reverted so this should be resolved shortly.

Excellent. Can you please cross-reference the patchset so someone can followup on it to decide when we can close this issue?

The revert is https://fuchsia-review.googlesource.com/c/fuchsia/+/437874

The tree seems to be closed for that revert to land.
@zanderso: We may need to attempt retries manually or disable these checks to unblock ourselves in the meantime. Or just wait it out :)

Per the internal thread. Change is being force submitted.

The patch has landed but not yet rolled into the engine because the engine tree is red (because the issue the patch purportedly fixes).

The patch was rolled into the engine and I don't see any new failures after the roll. I'm going to call this one a success.

This reoccurred here https://ci.chromium.org/p/flutter/builders/prod/Linux Fuchsia/5815, so I'm reopening this.

I have reverted the Fuchsia SDK roll to back before the flake started. If/When that clears things up, I'll downgrade this from P0.

@chaselatta told me via other channels that:
"I got a conversation started with the netstack team and some of the flutter folks. We also have created a bug (fxb/61962) which is tracking this internally with the connectivity team and it's been added to the chaselist."

Mitigation for this problem:

https://github.com/flutter/packages/pull/227
https://github.com/flutter/infra/pull/243
https://github.com/flutter/engine/pull/21828

@zanderso says this should be fixed upstream by the Fuchsia netstack team. He will followup on the roll into the engine.

From triage of presubmit flakes reported by users, this one still seems to be an ongoing issue with the following report:

https://chromium-swarm.appspot.com/task?id=4f391f8860d55610

@chinmaygarde that presubmit run was before the Fuchsia SDK roll that included the fix here https://github.com/flutter/engine/commit/ea2aea1c610242ffdf57d0b813f5281ff17fdd16. Since then I haven't seen any flakes, so I will close this.


Remove unused property statement

Hi @tpunt, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@tpunt thanks!


progress conflicts with last version of mtime (v2.0.0)

Would it be possible to update progress to avoid the conflict with mtime (version 2.0.0)?
Thank you.

Yes, I will cut a release as soon as I can.

Close by ocaml/opam-repository#23826


Where can I find source codes for the buttons on the bottom of page https://react.semantic-ui.com/layouts/fixed-menu

Hi,
I want to use the similar layouts and sources buttons on the bottom of page https://react.semantic-ui.com/layouts/fixed-menu. However, I cannot find the source codes for it in the GitHub repository.
Can anyone help me with this?
Thanks
--------------^ Click "Preview" for a nicer view!
We primarily use GitHub as an issue tracker; for usage and support questions, please check out these resources below. Thanks! 😁.

Gitter Community Chat: https://gitter.im/Semantic-Org/Semantic-UI-React
StackOverflow: https://stackoverflow.com/questions/tagged/semantic-ui-react using the tag semantic-ui-react
Also have a look at our docs: http://react.semantic-ui.com

https://github.com/Semantic-Org/Semantic-UI-React/blob/master/docs/src/components/LayoutsLayout.js


Add GitHub Workflow to check for fmt, vet, and mod tidy.

Using github actions (outside openshift org on forks) to notify dev of fmt, vet, or mod issues.
See run https://github.com/kaovilai/oadp-operator/actions/runs/3206089810

Codecov Report
Base: 31.92% // Head: 31.92% // No change to project coverage :thumbsup:

Coverage data is based on head (a4b2e04) compared to base (45fcd3d).
Patch has no changes to coverable lines.

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

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #839   +/-   ##
=======================================
  Coverage   31.92%   31.92%
=======================================
  Files          16       16
  Lines        3057     3057
=======================================
  Hits          976      976
  Misses       1989     1989
  Partials       92       92

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I guess the main risk of bot commits to the PR is they get overwritten with force pushes. I'm assuming that a force push will just regenerate the bot commits, so it may be fine. The alternative (which is what happens upstream with Velero) is a ci task that fails with an error message asking the user to tidy/format.

Force push regenerates bot commits as long as github actions isn't offline in your fork. We cannot use github actions in this org so it won't show up in statuses here. This is run from the fork side only.

But yes can make the action fail from the fork side.

Failing in a CI task requires you to push again at a later time. Pushing format and tidy for you saves dev time. They can just pull the tidy.. or force push a tidied commit if they wish.
Any accidental untidied force pushes will be auto fixed in the next bot commit.

This would, at least for me, make my life much more challenging in managing my branches. Having something auto-commit w/o the end user asking for it scares me.

@shawn-hurley I have similar concerns. I'm not in the habit of fetching my PR branches after I create them. In fact on a recent PR after I merged a commit to my PR branch from someone else, I subsequently forgot that I did that and force-pushed a rebase change, which lost those remote PR changes.

It is the same reason that I don't like to use the commit suggestions. I always get divergent branches, I can recover it but just something to consider.

so in pelorus we have a precommit hook that works locally for developers that run any lint and format prior to the developer pushing the code.  Not sure if I 100% understand this yet, but I'd rather not have code fixed in CI and committed by ci tooling.
Prevent the commit locally if lint fails.
https://github.com/konveyor/pelorus/blob/master/Makefile#L75
https://github.com/konveyor/pelorus/blob/master/scripts/pre-commit
not 100% sure if this applies here yet.. but look at it more.

@weshayutin @shawn-hurley @sseago addressed feedback. doing git diff --exit-code instead of committing.

Updated PR description. See run example here. https://github.com/kaovilai/oadp-operator/actions/runs/3206089810
PS. 4.10 flake
/retest

4.9 succeeded but failed ci deprovisioning.
/override 4.9-operator-e2e-aws
4.11 succeeded but failed ci must-gather
/override 4.11-operator-e2e-aws

4.9 succeeded but failed ci deprovisioning.
/override ci/prow/4.9-operator-e2e-aws
4.11 succeeded but failed ci must-gather
/override ci/prow/4.11-operator-e2e-aws

/test ci/prow/4.10-operator-e2e-aws
level=error msg=Error: Provider produced inconsistent result after apply

That moment when the test and override context are different :/
/test 4.10-operator-e2e-aws
level=error msg=Error: Provider produced inconsistent result after apply

Adding a precommit

/retest


Create a migration script for new fernet encrypted keys.

With #123 in place, we will need a script to be able to move from the older style sqlalchemy_utils encrypted column to the new fernet encrypted column.
This will be handled via a alembic migration that will create an intermediate table such that we can convert between the new encryption scheme and the old scheme. New deployments should not have to undergo this migration.

Closed by #128


Add detailed schedule

What happened
Replace the barebone schedule with the complete list of talks.
Insight
The schedule data is stored in a separate yml file for each day (to keep it easy to update). The link between the schedule yml files and speakers rely on a new speaker id.
The tabbed navigation is browser history friendly so that users can share links (e.g., /schedule/#day-2) for each day and see the correct content.
The detailed information for each speaker will be added in another PR.
Proof Of Work

Small Screen
Large Screen

Thanks for the updates and fixes. I made another round of improvements. Let's aim for further improvement in a future PR.


invoice QR flow wrongly attempts cross-community xfer and fails

on phone A select community AAA and account A which has a balance in AAA but not in BBB
on phone B select community BBB and account B
B requests funds from A and shows QR code
A scans the qr code
app tries to send, but fails with a meaningless error message. Most likely, this is because A tries to send B tokens which it doesn't have or it tries to send AAA tokens but pay fees in BBB?

Desired behavior:

dialog warning about invoice bing for a different community. allow A to send AAA tokens to B if confirmed. But then, also pay fees in AAA

Ah check that verifies the community and cid has been implemented.


Cannot edit the Department under User Update profile section

Suggested Labels
Type/Bug
Affected/IS550-Beta2
Priority/High
Description
Login to the management console
Create a user role
Create a User
Assign the created role to the user
Go to Update profile section of the created user
Observation
Cannot input a value for the Department as in [1]
[1]. update-profile.png

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


fix browsersync issue

Removed single quotes around _site folder in browser sync script to make compatible with Microsoft Windows environments.

Looks like @wiredacorn beat me to the punch. This fixes issue #24

增加一个404


Cursor pagination does not work properly on a hasManyThrough relationship.

Laravel Version: 8.78.1
PHP Version: 8.0.13
Database Driver & Version: MySQL 8.0.27

Description:
I noticed wrong data being returned from the database when using cursor pagination on a hasManyThrough relationship.
By default (without cursor pagination), hasManyThrough generates this query:

But when using cursor pagination, it uses SELECT * (instead of SELECT table.*) along with INNER JOIN which ends up mixing up values from both tables:

Steps To Reproduce:

Create a hasManyThrough relationship. (I used the example on this page).
Make sure the intermediate and final tables have a column with the same name (like uuid).
Run cursorPaginate on the hasManyThrough relationship and dump the model's uuid (cursorPaginate()->first()->uuid), and you'll see that it put a value from the intermediate table instead of the value in the final table.

Heya, thanks for reporting.
We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as separate commits on the main/master branch and share the repository here? Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.
laravel new bug-report --github="--public"

Please do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue.
Thanks!
PS. I realise you have created the repo already but because you've committed all your changes in the initial commit it's hard for me to debug this. Please recreate the repo with the above command.

Done: https://github.com/paulandroshchuk/bug-report
@driesvints

Hey @paulandroshchuk, thanks for that. I sent in a PR that should fix this: https://github.com/laravel/framework/pull/40300


"error: the path "usersvc/deployment.yaml" does not exist"

For this step of the blog post
bash up.sh usersvc

I get this error:
error: the path "usersvc/deployment.yaml" does not exist

Could I suggest to use Makefile instead of Bash to build and deploy to minikube ? something like this ? could send you a PR if you agree.

Hi, thanks for the bug report! I'm not sure switching to a Makefile versus bash would really simplify things -- my preference would be to fix the root cause. But interested in hearing your thoughts?

I found the root cause was the environment variables being overridden in recursive bash scripts,
In K8Guard we used Makefiles and we have a parent project that deploys other projects in other repos, and using Makefiles simplified depending on Bash variables specially when you include another bash file.
I find Make a good fit, since it is installed by default on most systems (including linux and mac)


Query of death

The query: q=Second+atmosphere consistently returns a 500 response.
HTTP/1.1 500 Internal Server Error [Server: nginx, Date: Tue, 15 May 2018 14:37:03 GMT, Content-Type: text/html;charset=utf-8, Content-Length: 1633, Connection: keep-alive, Content-Language: en] org.apache.http.conn.BasicManagedEntity@2b5825fa
All other queries have been fine.

Hello, thanks for reporting this issue. It has been fixed with commit 99be1cf. A new version of SMAPH built from that commit has been deployed on D4Science.


69 map road same view

created split component in inspect page, with map, road surface image and graph

I think some dependencies were not installed correctly(?)

I think some dependencies were not installed correctly(?)

Yes, It should be fix if you do npm i and add the package-lock.json


Explorer functionality crashes the app

Describe the bug
When I load the app then go from Query to Explorer the app crashes.
I am on => Surrealdb 1.1.0.   Surrealist Version 1.11.3 (20240125.225857).   OSX 12.0.1   M1 MacBook Pro
Error on the Explorer =>
Unexpected Application Error!
e.at is not a function. (In 'e.at(-1)', 'e.at' is undefined)
lXt@http://localhost:18982/assets/index-d19b4f02.js:1264:4179783
uXt@http://localhost:18982/assets/index-d19b4f02.js:1264:4180135
DJ@http://localhost:18982/assets/index-d19b4f02.js:88:188993
RDe@http://localhost:18982/assets/index-d19b4f02.js:90:241851
IDe@http://localhost:18982/assets/index-d19b4f02.js:90:237552
IZe@http://localhost:18982/assets/index-d19b4f02.js:90:237475
O@http://localhost:18982/assets/index-d19b4f02.js:90:237325
Nq@http://localhost:18982/assets/index-d19b4f02.js:90:233672
Uae@http://localhost:18982/assets/index-d19b4f02.js:90:234478
Uae@[native code]
d@http://localhost:18982/assets/index-d19b4f02.js:88:172697
@http://localhost:18982/assets/index-d19b4f02.js:90:231990

This appears to be caused by a browser compatibility issue. I'll fix the affected code to prevent it from happening.
Additionally, it might be possible to fix this issue directly if you make sure your version of Safari is up-to-date (at least 15.4)

Ok.  I have upgraded my computer so that it has the updated Safari and the Explorer is now working.  Thank you for the info and making Surrealist!


Build image more than once, UI does not block 'create' button when not select a project.

In GitLab by @wknet123 on Mar 28, 2018, 16:36

In GitLab by @liyanq528 on Nov 8, 2019, 07:49
fixed by pull request #1177

In GitLab by @wknet123 on Nov 8, 2019, 07:49
Close it as fixed

In GitLab by @sokril on Nov 8, 2019, 08:20
closed

In GitLab by @sokril on Nov 8, 2019, 08:20
assigned to @wknet123

In GitLab by @liyanq528 on Nov 11, 2019, 08:52
mentioned in merge request !485

In GitLab by @liyanq528 on Nov 12, 2019, 02:22
mentioned in merge request !872

In GitLab by @liyanq528 on Nov 13, 2019, 04:37
mentioned in merge request !603

In GitLab by @liyanq528 on Nov 13, 2019, 07:25
mentioned in merge request !507


Add set state in Go

This continues to grow our state support by adding map state support. Once this is in, I'll add a follow up PR with an integration test. In the meantime, I tested manually by running the hacked wordcount found here - https://github.com/damccorm/beam/pull/96/files#diff-46f0bd8f9f6b541e840079960d684ba78e6513f1293b673d08faaec94d48a234 - and it produced output like:
swimming: false. Total num keys: 2. With keys: [swimming36 swimming]
hourly: false. Total num keys: 2. With keys: [hourly52 hourly]
hourly: true. Total num keys: 3. With keys: [hourly33 hourly52 hourly]
hourly: true. Total num keys: 4. With keys: [hourly52 hourly hourly1 hourly33]
About: false. Total num keys: 2. With keys: [About About38]
advise: false. Total num keys: 2. With keys: [advise18 advise]
advise: true. Total num keys: 3. With keys: [advise18 advise68 advise]
advise: true. Total num keys: 4. With keys: [advise68 advise18 advise4 advise]
lawful: false. Total num keys: 2. With keys: [lawful9 lawful]
lawful: true. Total num keys: 3. With keys: [lawful9 lawful lawful49]
lawful: true. Total num keys: 4. With keys: [lawful49 lawful38 lawful lawful9]

Note that this doesn't add support for Remove (to remove a single key). This will come in a future pr and has been noted in #22736
Part of #22736

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @riteshghorse


Handling logging to file with gunicorn

How do you handle logging to file when running the project with gunicorn since it spawns multiple workers?

Logging can be configured by using various flags in the gunicorn.conf.py. In the generated project this file is located in the .config submodule and contains values from: https://github.com/benoitc/gunicorn/blob/master/examples/example_config.py
To configure gunicorn to log to a file you need to change accesslog and errorlog default values.
Example:
errorlog = "/var/log/fastapi.errror.log"
accesslog = "/var/log/fastapi.log"

Just make sure that the user which is running the app has rw permissions to the log file you want to write in. Otherwise, you will have the following error:
[2022-01-21 10:30:33 +0100] [4129321] [INFO] Start gunicorn WSGI with ASGI workers.

Error: Error: '/var/log/fastapi.error.log' isn't writable [PermissionError(13, 'Permission denied')]

Resources:

Gunicorn logging configuration documentation: https://docs.gunicorn.org/en/latest/settings.html#logging
Example gunicorn.conf.py generated with the project: https://github.com/rszamszur/fastapi-mvc-example/blob/master/fastapi_mvc_example/config/gunicorn.conf.py

Logfile output example:
$ cat fastapi.error.log
[2022-01-21 10:33:41 +0100] [4134628] [INFO] Starting gunicorn 20.1.0
[2022-01-21 10:33:41 +0100] [4134628] [INFO] Listening at: http://<IP_ADDRESS>:8000 (4134628)
[2022-01-21 10:33:41 +0100] [4134628] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2022-01-21 10:33:41 +0100] [4134628] [INFO] Server is ready. Spawning workers
[2022-01-21 10:33:41 +0100] [4134642] [INFO] Booting worker with pid: 4134642
[2022-01-21 10:33:41 +0100] [4134642] [INFO] Worker spawned (pid: 4134642)
[2022-01-21 10:33:41 +0100] [4134642] [INFO] Started server process [4134642]
[2022-01-21 10:33:41 +0100] [4134642] [INFO] Waiting for application startup.
[2022-01-21 10:33:41 +0100] [4134642] [INFO] Application startup complete.
[2022-01-21 10:33:41 +0100] [4134643] [INFO] Booting worker with pid: 4134643
[2022-01-21 10:33:41 +0100] [4134643] [INFO] Worker spawned (pid: 4134643)
[2022-01-21 10:33:41 +0100] [4134643] [INFO] Started server process [4134643]
[2022-01-21 10:33:41 +0100] [4134643] [INFO] Waiting for application startup.
[2022-01-21 10:33:41 +0100] [4134643] [INFO] Application startup complete.
[2022-01-21 10:33:56 +0100] [4134628] [INFO] Handling signal: int
[2022-01-21 10:33:57 +0100] [4134628] [WARNING] Worker with pid 4134643 was terminated due to signal 3
[2022-01-21 10:33:57 +0100] [4134628] [WARNING] Worker with pid 4134642 was terminated due to signal 3
[2022-01-21 10:33:57 +0100] [4134628] [INFO] Shutting down: Master
[2022-01-21 10:34:05 +0100] [4135479] [INFO] Starting gunicorn 20.1.0
[2022-01-21 10:34:05 +0100] [4135479] [INFO] Listening at: http://<IP_ADDRESS>:8000 (4135479)
[2022-01-21 10:34:05 +0100] [4135479] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2022-01-21 10:34:05 +0100] [4135479] [INFO] Server is ready. Spawning workers
[2022-01-21 10:34:05 +0100] [4135497] [INFO] Booting worker with pid: 4135497
[2022-01-21 10:34:05 +0100] [4135497] [INFO] Worker spawned (pid: 4135497)
[2022-01-21 10:34:05 +0100] [4135497] [INFO] Started server process [4135497]
[2022-01-21 10:34:05 +0100] [4135497] [INFO] Waiting for application startup.
[2022-01-21 10:34:05 +0100] [4135497] [INFO] Application startup complete.
[2022-01-21 10:34:05 +0100] [4135503] [INFO] Booting worker with pid: 4135503
[2022-01-21 10:34:05 +0100] [4135503] [INFO] Worker spawned (pid: 4135503)
[2022-01-21 10:34:05 +0100] [4135503] [INFO] Started server process [4135503]
[2022-01-21 10:34:05 +0100] [4135503] [INFO] Waiting for application startup.
[2022-01-21 10:34:05 +0100] [4135503] [INFO] Application startup complete.
[2022-01-21 10:34:16 +0100] [4135479] [INFO] Handling signal: int
[2022-01-21 10:34:16 +0100] [4135479] [WARNING] Worker with pid 4135503 was terminated due to signal 3
[2022-01-21 10:34:16 +0100] [4135479] [WARNING] Worker with pid 4135497 was terminated due to signal 3
[2022-01-21 10:34:17 +0100] [4135479] [INFO] Shutting down: Master
$ fastapi.log
<IP_ADDRESS>:43920 - "GET /api/ready HTTP/1.1" 200
<IP_ADDRESS>:43920 - "GET /favicon.ico HTTP/1.1" 404
<IP_ADDRESS>:43924 - "GET /api/ready HTTP/1.1" 200
<IP_ADDRESS>:43926 - "GET /api/ready2 HTTP/1.1" 404

Thanks for the response. Still I feel like this falls under the problem that logging in python does not handle multiprocessing which is essentially what gunicorn does. I always use the logconfig-dict to setup logging for my projects and thats what I'm pointing gunicorn to. But from what I have seen it does not work well with multiple workers trying to log to the same files, specially when you use a RotatingFileHandler

If I may ask, what is your use case, that you need to a logfile per worker? Maybe I can find some solution for you.
In my experience with web frameworks usually, there is one application log per master-worker regardless of how many child processes there might be. For instance in Ruby on Rails puma logs application log into one file despite how many workers you configure by default.
In the meantime, I'll experiment with gunicorn logging configuration and see what's possible.
Lastly, you might research the topic of structure logging. If you have to store, filter, and read logs from many distributed systems it can be really helpful. Structured logging uses a defined format to add important details to logs and make it easier to interact with them in different ways. Meaning you can easily filter log files by hostname, PID, level, or any other field that you'll define.
Personally, I've used seq: https://datalust.co/seq
If you'd be interested I've written a custom logging handler for sending logs to seq. It's not perfect but get the job done.

That sounds like a nice solution, I was looking into trying Grafana Loki actually, but that does sound interesting I might hit up later on that.
I don't really need 1 logfile per worker but From what I have been reading and tried gunicorn logging to file with multiple workers does not work properly (even going on stuff about gunicorn). Take a look: https://docs.python.org/3/howto/logging-cookbook.html#logging-to-a-single-file-from-multiple-processes
I'm probably mistaken, but when I tried a RotatingFileHandler the first log file was fine with the logs from the workers, but every new log file was only being written by one worker. I'm not sure tho if the issue comes from the multiprocessing logging or if indeed everything was being served by only 1 worker. This is the script I used to test my app
async def fetch(idx: int, client: httpx.AsyncClient):
    response = await client.put(url, headers=headers, data=payload, timeout=None)
    return response.elapsed
async def fetch_all(times: int):
    async with httpx.AsyncClient() as client:
        return await asyncio.gather(
            *map(
                fetch,
                list(range(times)),
                itertools.repeat(client),
            )
        )
if __name__ == "__main__":
    loop = asyncio.get_event_loop()
    result = loop.run_until_complete(fetch_all(1000))
    print("avg", sum(result, datetime.timedelta(0)) / len(result))
    print("min", min(result))
    print("max", max(result))

Thanks for the materials! I wasn't even aware there is an issue with writing to a single file from multiple processes in Python. Also, I haven't had a chance to research this topic more. In the past, when posed with a similar problem, I've decided to use structured logging instead and don't worry about log files. Finally, with the gunicorn I guess I've assumed it works out of the box since one can configure logging to a single file.
Since I already have some implementation for the Seq logging handler, I might add it to the template. Also, I'll add Seq deployment to Kubernetes application stack t in make dev-env, so it should be much more convenient to test and play with it. However, a significant tradeoff is that a message queue or separate process is needed to send records to the Seq application. Otherwise, you can clog up the network interface, resulting in some record requests lost due to timeout (caused by too many requests). Whereas Grafana Loki seems to have the opposite approach - scraps logs from defined paths and then parses it to some structure.
For now, I'll include seq, to the template: #26
Later on, I might play with Grafana Loki as well and see how that works.

Hi @rszamszur  @jeanlst
With the help of some information obtained on the internet I was able to customize the fastapi-mvc-example to do the following:

Use loguru instead of the standard Python logging module to manage system logs. Apparently loguru works better with threads and multiprocessing.
Capture all logs, even Gunicorn startup logs with the custom log format I intend to use in my application.
Put the following information in the log lines: PID of the process (gunicorn worker) that generated the log line, x-correlation-id and x-request-id (a necessity of my application and which are generated/obtained by a fastapi middleware )
Gunicorn's master and workers appear with a friendly name when I run a ps axu

By default I generate the logs in stdout, but I also tested saving the logs in a file and it worked perfectly, even after rotating the file. Each worker continued writing to the same file after loguru's file rotation.
My version of wsgi.py is hardcoded to configure Gunicorn workers and threads as per this post: https://medium.com/building-the-system/gunicorn-3-means-of-concurrency-efbb547674b7 - I don't know if it is the most efficient way, but in my tests it worked fine.
Although not complete, I added a new command to start a uvicorn server only, this is because I like to use its reload feature when I'm developing my code and I couldn't find a way to do this with Gunicorn - apparently it's impossible. The command is:
das_sankhya devserve
I used this information to prepare this demo:

https://medium.com/building-the-system/gunicorn-3-means-of-concurrency-efbb547674b7
https://pawamoy.github.io/posts/unify-logging-for-a-gunicorn-uvicorn-app/
https://github.com/pahntanapat/Unified-FastAPI-Gunicorn-Log
https://github.com/Delgan/loguru/issues/365
https://loguru.readthedocs.io/en/stable/api/logger.html#sink
https://github.com/snok/asgi-correlation-id

And the main changes I made are in these files:

https://github.com/abnerjacobsen/fastapi-mvc-loguru/blob/main/das_sankhya/wsgi.py
https://github.com/abnerjacobsen/fastapi-mvc-loguru/blob/main/das_sankhya/core/logs2.py
https://github.com/abnerjacobsen/fastapi-mvc-loguru/blob/main/das_sankhya/core/gunicorn_logs.py

The repository with my changes is here: https://github.com/abnerjacobsen/fastapi-mvc-loguru
I did several tests with locust running:
 locust -f locust/test1.py
and apparently everything worked correctly.
@rszamszur  what do you think? can my changes cause some unexpected problem if it is put to run in Kubernetes ?
I don't understand much about Gunicorn's inner workings, I've just been gathering and experimenting with information obtained from the internet and now I would like a more authoritative opinion.
Anyway, congratulations on your project, it's excellent. And thanks for making it available to the community.

Hey @abnerjacobsen
Thanks for the input, that's quality research right there!
Please give me some time to dig into that, and go through the materials you've provided. But, at the first glance loguru could be implemented to the template as an optional logging class to choose from during project generation. Even though it is yet to be matured project, looks very promising (0.6.0 and 11k dayum :) )

Although not complete, I added a new command to start a uvicorn server only, this is because I like to use its reload feature when I'm developing my code and I couldn't find a way to do this with Gunicorn - apparently it's impossible.

That's actually a solid idea, already created an issue for that: #31
I'm not sure yet how this should be implemented:

separate command
additional flag  --reload in serve command. However, simple --reload won't be sufficient with WSGI + ASGI combo.
automatically based on env FASTAPI_ENV=development FASTAPI_ENV=production similar to Ruby on rails
other??

@abnerjacobsen any suggestions?

can my changes cause some unexpected problem if it is put to run in Kubernetes ?

If those changes don't break the application or the way it's served, then they should cause problems in Kubernetes deployment. For that, integration workflow comes in handy: https://github.com/rszamszur/fastapi-mvc/actions/workflows/integration.yml
Any merge to master will trigger it. It's basically a complete integration test for the fully generated project. This workflow will ensure that generated project:

virtualized environment (Vagrantfile)
make install
make image
helm chart
make dev-env - bootstraping minikube cluster with Redis HA cluster

works properly.


added logseq-searx-plugin

Submit a new Plugin to Marketplace
Plugin Github repo URL:  [[(https://github.com/zoernert/logseq-searx)]]
Github releases checklist

[x] a legal package.json file.
[x] a valid CI workflow build action for Github releases. (theme plugin for this).
[x] a release which includes a release zip pkg from a successful build.
[x] a clear README file, ideally with an image or gif showcase. (For more friendly to users, it is recommended to have English version description).
[x] a license in the LICENSE file.

Hi @zoernert I just found that the release zip pkg is missing from the Github releases page. https://github.com/zoernert/logseq-searx/releases
Maybe this plugin is helpful :) https://github.com/xyhp915/logseq-journals-calendar


MC Shortcuts not available on Mac Boot Up / Error Message

Before opening the issue, have you...?

[X] Searched for existing issues
[X] Looked through the wiki
[X] Updated MonitorControl to the latest version (if applicable)

Describe the bug
On almost every startup, MC fails to be recognised in Pricay / Accessibility despite being previously selected and switched on. Happens approx 80% of reboots. Sometimes rebooting twice fixes the problem
Shortcuts not available
You need to enable MonitorControl in
System Preferences > Security and
Privacy > Accessibility for the keyboard shortcuts to work
Steps to reproduce
Reboot Mac, message appears after system has loaded
Expected behavior
Machine to reboot with no messages relating to MC
Anything else?

Environment Information (please complete the following information)
- macOS version:13.4 (22F66)
- Mac model: MacBook Air M2
- MonitorControl version: 4.1
- Monitor(s):0 just on laptop currently
- Apple Silicon/M1 (yes or no): yes

You'll probably need to reset the privacy database in Terminal: tccutil reset Accessibility


confusing hcloudmachinetemplate controller error when using k0s

/kind bug
What steps did you take and what happened:
Please see here: https://github.com/k0sproject/k0smotron/issues/561
Basically I'm trying to run the basic k0s cluster-api + hetzner example from their docs and running into a lot of problems. I've tracked it down to the CAPH machinetemplate controller failing to create the machine template because it can't fetch the hcloud api key secret from the parent hetznercluster object... but that seems to be configured correctly, so I'm stumped.
What did you expect to happen:
A k0s cluster to spin up in hetzner.
Anything else you would like to add:
Environment:

cluster-api-provider-hetzner version: v1.0.0-beta.32
Kubernetes version: (use kubectl version) v1.29.3
OS (e.g. from /etc/os-release):  mac os

I never used k0s, but I use caph daily and it works fine.
Why do you use k0s? I don't know that project.
Have you tried using caph the normal way (start with the mgt cluster in a kind cluster, later you can move the mgt cluster into a wl cluster)?

Yes I am using caph the normal way daily as well! I'm using a regular old kubeadm cluster in Hetzner as my management cluster and have used it to create lots of clusters.
I'm now trying to make some extremely lightweight k0s clusters for users and so that put me down the path of trying to get caph to work with the k0s control plane provider. So any guidance on how to debug caph in this case would be greatly appreciated.

If the secret can't be found, these things come to my mind:
Check the namespace.
Check rbacs via impersonating the service account.

@rgarcia Were you able to solve it?

I gave up and switched back to default control plane provider in CAPH (kubeadm). It's working fine for now. I do think it would be nice to get a lightweight control plane provider like k0s or k3s working, since Hetzner is often the place people go for super low-cost VMs. E.g. running a single node k0s cluster on a cax11 would be neat.
Thanks for checking in and feel free to close.

thank you for your feedback. Feel free to open a new issue if something is not working or not easy to understand.


[docs] URL for circleci config is broken

What: Under the Automating section, in the Manual Setup the link for circleci configuration is broken.
Where: https://open-wc.org/automating/#setup

looks like that file was deleted in 17c40312c3d852465a74f94fe1d66af1ed5c1480
Since that package is deprecated, shouldn't we also remove this page?

we no longer have it in our generators but the info is still good... we probably should just show a good circleci config to copy from
at some point we might wanna switch/promote github actions - but first we need to verify that it work reliably for our usecase...

we no longer have such a section in our updated website 😅


三网延迟监控

Environment
Debian11
Nezha Version
1.4.3
Describe the bug

To Reproduce
更新到出1.4.2. 1.4.3版本后出现的
Additional Context

Validation

[X] I confirm this is a bug about nezha (Nezha Dashboard).
[X] I have searched Issues and confirm this bug has been reported before.

https://mjj.today/i/9yVLGM


[Backup]Added default backup retention as 30 days

Description
Added default backup retention as 30 days
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Backup


Make naming consistent

Use short names like eth, hdr, proto, since that's what Rust stdlib is doing with network-related names.
Name the protocol enums after the frames they are included in. So, for example, EthProto for protocol info included in the Ethernet header.
Remove all from_be methods, callers of the library should do that.
Use proto enums directly as member field types, so we avoid manual conversion.

Signed-off-by: Michal Rostecki<EMAIL_ADDRESS>

I'm seeing this - in case you want to change:
$ cargo doc
 Documenting network-types v0.0.2 (/Users/dsavints/dev/hack/gh/vadorovsky/network-types)
warning: this URL is not a hyperlink
  --> src/l3/ip.rs:94:5
   |
94 | /// https://en.wikipedia.org/wiki/List_of_IP_protocol_numbers
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use an automatic link instead: `<https://en.wikipedia.org/wiki/List_of_IP_protocol_numbers>`

$ cargo doc
Documenting network-types v0.0.2 (/Users/dmitris/dev/hack/gh/vadorovsky/network-types)
warning: this URL is not a hyperlink
--> src/l3/ip.rs:94:5
|
94 | /// https://en.wikipedia.org/wiki/List_of_IP_protocol_numbers
|     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use an automatic link instead: <https://en.wikipedia.org/wiki/List_of_IP_protocol_numbers>

@dmitris Fixed, thanks for review!

@dave-tucker

Naming wise, I think I actually prefer the verbosity unless the acronyms are well known

To be honest, I don't have any hard preference whether names should be short or verbose, but Alessandro's point for using the short ones (Ipv4Hdr, eth and so on) is that std::net is using shortened names and almost never fully verbose ones.

Re src/dst vs. src_addr/dst_addr, I think the most logical and easiest to remember would be the name that is closest to the ones used in the related Linux kernel structures.  If have to choose between short and verbose, my preference would be on the short/succinct side.


Related data not present in result when specifying include.

Bug description
Related data when using include in queries not available.
When issuing a query, e.g.:
const jobsQuery = trpc.job.findManyJob.useQuery({
  take: 40,
  include: { employer: true },
});

the logs show that the correct database queries are made to retrieve the model specified in the include directive from the DB.
However the related data is not present in the result-object, rather just the fields of basic types relationships. This is despite the relations being properly defined in the schema (i.e. the relationships work in Prisma studio). In particular I can do the following:
{jobsQuery.data?.map((job) => {

{job.employerId}
;
})}

while the following does not work:
{jobsQuery.data?.map((job) => {

{job.employer}
;
})}

In the past, that is, before include and select was a feature, the returned type was that of the model generated from the Prisma schema, in this case Job. Now it is SerializeObject<UndefinedToOptional<Job>>. I do not know if this is related to the issue.
I may be doing something wrong, but another person is experiencing this as well, so it may be version-specific or perhaps the docs are hard to understand (or I am just bad at reading), but I tried numerous times to get it to work to no avail.
How to reproduce

Create bare-bones trpc-prisma-starter project using the setup guide and the dependencies listed in "Environment and Setup".
Generate the model.
Run a query with include.

If you let me know I can share the project in question, since it includes a lot of boilerplate.
Expected behavior
I expect that upon invoking the following query:
const jobsQuery = trpc.job.findManyJob.useQuery({
  take: 40,
  include: { employer: true },
});

I should be able to do things like:
{jobsQuery.data?.map((job) => {

{job.employer.name}
;
})}

however the field is not present in the object.
Prisma information
datasource db {
  provider = "postgres"
  url      = env("DATABASE_URL")
}

generator trpc {
  provider       = "prisma-trpc-generator"
  withMiddleware = false
  withShield     = false
  contextPath       = "../src/server/context"
  isGenerateSelect   = true
  isGenerateInclude  = true
}

generator client {
  provider = "prisma-client-js"
}

generator erd {
  provider = "prisma-erd-generator"
  theme = "default"
}

model Post {
  id    String @id @default(uuid())
  title String
  text  String

  // To return `Date`s intact through the API we use transformers
  // https://trpc.io/docs/data-transformers
  // This is unique so it can be used for cursor-based pagination
  createdAt DateTime @default(now())
  updatedAt DateTime @default(now()) @updatedAt
}

model Job {
  id          String     @id @default(cuid())
  title       String     @db.VarChar(255)
  description String     @db.Text
  employerId  String
  employer    User       @relation(fields: [employerId], references: [id], onDelete: Cascade)
  addressId   String
  address     Address    @relation(fields: [addressId], references: [id], onDelete: Cascade)
  fields      JobField[]
  createdAt   DateTime   @default(now()) @map(name: "created_at")
  updatedAt   DateTime   @updatedAt @map(name: "updated_at")
}

model JobField {
  id   String @id @default(cuid())
  text String @unique
  jobs Job[]
}

model Address {
  id        String    @id @default(cuid())
  name      String?   @db.Text
  street    String    @db.Text
  city      String    @db.Text
  zip       String    @db.Text
  latitude  String?   @db.Text
  longitude String?   @db.Text
  countryId String
  country   Country   @relation(fields: [countryId], references: [id])
  jobs      Job[]
}

model Country {
  id      String    @id @default(cuid())
  name    String    @unique
  Address Address[]
}

model Session {
  id           Int      @id @default(autoincrement())
  sessionToken String   @unique @map("session_token")
  userId       String   @map("user_id")
  expires      DateTime
  user         User     @relation(fields: [userId], references: [id], onDelete: Cascade)

  @@map("sessions")
}

model User {
  id            String    @id @default(cuid())
  role          Role
  name          String    @db.VarChar(255)
  description   String
  imageUrl      String?   @db.Text
  email         String?   @unique
  emailVerified DateTime? @map("email_verified")
  jobs          Job[]
  createdAt     DateTime  @default(now()) @map(name: "created_at")
  updatedAt     DateTime  @updatedAt @map(name: "updated_at")
  sessions      Session[]

  @@map(name: "users")
}

model VerificationToken {
  identifier String
  token      String   @unique
  expires    DateTime

  @@unique([identifier, token])
  @@map("verificationtokens")
}

enum Role {
  EMPLOYER
  APPLICANT
}

Environment & setup

OS: Mac OS
Database: PostgreSQL
Node.js version: v16.15.1

Using package.yaml:
{
  "name": "@examples/trpc-next-prisma-starter",
  "version": "10.9.0",
  "private": true,
  "scripts": {
    "migrate-postgres": "prisma migrate dev",
    "generate-postgres": "prisma generate",
    "prisma-studio-postgres": "prisma studio",
    "db-seed": "prisma db seed",
    "db-reset": "prisma migrate reset",
    "dx:next": "run-s migrate-postgres generate-postgres && next dev",
    "dx:prisma-studio": "pnpm prisma-studio-postgres",
    "dx": "run-p dx:* --print-label",
    "dev": "pnpm dx:next",
    "build-postgres": "run-s generate-postgres migrate && next build",
    "build": "pnpm build-postgres",
    "start": "next start",
    "lint": "eslint --ext \".js,.ts,.tsx\" --report-unused-disable-directives --report-unused-disable-directives src",
    "lint-fix": "pnpm lint --fix",
    "migrate-dev": "prisma migrate dev",
    "migrate": "prisma migrate deploy",
    "test": "run-s test:*",
    "test:unit": "vitest run",
    "test:e2e": "playwright test",
    "test-dev": "start-server-and-test 'next dev' http://<IP_ADDRESS>:3000 test",
    "test-start": "start-server-and-test start http://<IP_ADDRESS>:3000 test",
    "postinstall": "prisma generate"
  },
  "prisma": {
    "seed": "tsx prisma/seed.ts"
  },
  "prettier": {
    "printWidth": 80,
    "trailingComma": "all",
    "singleQuote": true
  },
  "dependencies": {
    "@prisma/client": "^4.7.1",
    "@tanstack/react-query": "^4.3.8",
    "@trpc/client": "^10.9.0",
    "@trpc/next": "^10.9.0",
    "@trpc/react-query": "^10.9.0",
    "@trpc/server": "^10.9.0",
    "clsx": "^1.1.1",
    "next": "^13.0.0",
    "prisma-trpc-generator": "^1.0.2",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "superjson": "^1.7.4",
    "zod": "^3.0.0"
  },
  "devDependencies": {
    "@faker-js/faker": "^7.6.0",
    "@mermaid-js/mermaid-cli": "^9.3.0",
    "@playwright/test": "^1.26.1",
    "@types/node": "^18.7.20",
    "@types/react": "^18.0.9",
    "@typescript-eslint/eslint-plugin": "^5.47.0",
    "@typescript-eslint/parser": "^5.47.0",
    "eslint": "^8.30.0",
    "eslint-config-next": "^13.1.0",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-prettier": "^4.2.1",
    "eslint-plugin-react": "^7.31.11",
    "eslint-plugin-react-hooks": "^4.6.0",
    "npm-run-all": "^4.1.5",
    "prettier": "^2.7.1",
    "prisma": "^4.7.1",
    "prisma-erd-generator": "^1.2.5",
    "start-server-and-test": "^1.12.0",
    "tsx": "^3.9.0",
    "typescript": "^4.8.3",
    "vite": "^3.1.3",
    "vitest": "^0.23.4"
  },
  "publishConfig": {
    "access": "restricted"
  }
}

Prisma Version
Environment variables loaded from .env
prisma                  : 4.8.1
@prisma/client          : 4.8.1
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine d6e67a83f971b175a593ccc12e15c4a757f93ffe (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.8.0-61.d6e67a83f971b175a593ccc12e15c4a757f93ffe
Default Engines Hash    : d6e67a83f971b175a593ccc12e15c4a757f93ffe
Studio                  : 0.479.0

Hey, I think this is related to your issue: https://github.com/omar-dulaimi/prisma-trpc-generator/discussions/61
The user seems to have found a workaround

I think we could integrate this "workaround" which gets the PayloadType by inferring the query parameters as said in #61
Maybe when enabling "include" the generator should add this inference. so that included or selected relational fields show up in the procedures return type. Definitely a pretty important thing to offer for typescript users.

I went into a little rabbithole.
I tried to get the Payload type with Prisma.TableGetPayload<type of input> which does work when passing it to useQuery<myPayloadTyle> and infers my types when including in a predefined query input. Then I tried to add this to a generated FindFirst procedure but because at this scope it cannot infer the type given the input. It seems to me this is an intricate typescript inference story...
At this point I think it could only be done by some genetic payload wrapper type in the useQuery call to pass down the type of the query input directly to the Prisma call and back.
As this is a big issue for my current project I'll try to ask in the Prisma and or typescript discord to find some magician that can give me insights on this issue


Local path dependencies trigger advisory warnings for crates of the same name

Describe the bug
In opentelemetry we have an example crate called http, which is sitting at version 0.1.0. It recently started triggering the advisory check for RUSTSEC-2019-0033 and RUSTSEC-2019-0034 even though it is a completely different crate (just sharing the same name).
To Reproduce
Steps to reproduce the behavior:

Create example crate with same name/version as a crate that has a vulnerability

Expected behavior
Would expect to get no warnings/errors in this case.
Screenshots

Duplicate of #446


added get_dataframe_from_drive, auth_drive methods

Checklist for this pull request:

[x ] I have added docstrings to my additions if needed
[ ] I have added the module to docs/index.rst if it is completely new

Description:

@bxjw @ffaristocrat added tests for review


No Module Name certipy.entry

During the start of certipy below error appear . Any one help me out on this
Traceback (most recent call last):
File "/usr/local/bin/certipy", line 5, in
from certipy.entry import main
ModuleNotFoundError: No module named 'certipy.entry'

Have you tried to install with "pip3 install /path/to/Certipy"

yes i had installed by using below command :
pip3 install .
Output
└─# pip install .
Processing /root/Desktop/Certipy
Requirement already satisfied: asn1crypto in /usr/lib/python3/dist-packages (from Certipy==3.0.0) (1.4.0)
Requirement already satisfied: cryptography>=3.5 in /usr/local/lib/python3.9/dist-packages/cryptography-37.0.2-py3.9-linux-x86_64.egg (from Certipy==3.0.0) (37.0.2)
Requirement already satisfied: dnspython in /usr/lib/python3/dist-packages (from Certipy==3.0.0) (2.0.0)
Requirement already satisfied: dsinternals in /usr/local/lib/python3.9/dist-packages/dsinternals-1.2.4-py3.9.egg (from Certipy==3.0.0) (1.2.4)
Requirement already satisfied: impacket in /usr/lib/python3/dist-packages (from Certipy==3.0.0) (0.9.24)
Requirement already satisfied: ldap3 in /usr/lib/python3/dist-packages (from Certipy==3.0.0) (2.8.1)
Requirement already satisfied: pyasn1 in /usr/lib/python3/dist-packages (from Certipy==3.0.0) (0.4.8)
Requirement already satisfied: pyopenssl>=22.0.0 in /usr/local/lib/python3.9/dist-packages/pyOpenSSL-22.0.0-py3.9.egg (from Certipy==3.0.0) (22.0.0)
Requirement already satisfied: cffi>=1.12 in /usr/lib/python3/dist-packages (from cryptography>=3.5->Certipy==3.0.0) (1.14.6)
Building wheels for collected packages: Certipy
Building wheel for Certipy (setup.py) ... done
Created wheel for Certipy: filename=Certipy-3.0.0-py3-none-any.whl size=62389 sha256=99d5472cea3845d7e0976558595c6cd6466165cb85401e97de1adea557622db5
Stored in directory: /tmp/pip-ephem-wheel-cache-v3uj41um/wheels/ae/be/17/5e122ae3e94c957008a4503a0a0c47d7982e744809a7e4d12a
Successfully built Certipy
Installing collected packages: Certipy
Attempting uninstall: Certipy
Found existing installation: Certipy 3.0.0
Uninstalling Certipy-3.0.0:
Successfully uninstalled Certipy-3.0.0
Successfully installed Certipy-3.0.0
Error
┌──(root💀CaptainPing)-[~/Desktop/Certipy]
└─# certipy
Traceback (most recent call last):
File "/usr/local/bin/certipy", line 5, in
from certipy.entry import main
ModuleNotFoundError: No module named 'certipy.entry'


set on_connect_commands via a textarea split on newlines

on_connect_commands is an array of commands to be run when the
connection is made. Editing an array in html isn't (super) easy, so for
a quick implementation which just uses a textarea and split the lines on
newline.
PLEASE! CHECK MY WORK HERE. I had to dig a lot and change things I wasn't 100% confident about.

Rebased into master (627f57a).
Thanks for the contribution!


Update access rights for github token?

In the readme the following information is provided.

VUE_APP_GITHUB_TOKEN
Specifies the GitHub Personal Access Token utilized for API requests. Generate this token with the following scopes: copilot, manage_billing:copilot, manage_billing:enterprise, read:enterprise, admin:org.

I believe that admin:org is overkill. When I did my local setup, I used the less intrusive scope read:org, and it worked just fine. If there is no functionality I'm missing, I would suggest that the README be updated to adhere to the principle of least privilege.

@msfe , it could be. The README follows the guidelines of the API documentation which mentions admin:org .
@djopatrny , do you have any comments about this? 🙇

I believe a recent update may have added the read:org scope. The documentation update should go in soon.

As the docs have been updated and admin permissions requirement has been removed, I updated on this PR the references to admin:enterprise and admin:org. Thanks for raising this.


Add instance IsCmdArgument (NonEmpty String)

Add this little useful instance which doesn't introduce any new dependencies.
Please let me know if I should add a test case.
Would it make sense to add IsCmdArgument instances for Text and ByteString as well or were they left out on purpose? (It seems that using -XOverloadedStrings isn't really supported anyway?)

Thanks for the patch! Will let CI weigh in, but looks good to me. No need for a test.
Overloaded strings and arguments don't work well, since both ends end up being quite polymorphic. The absence of a ByteString instance is because it's not a very good fit - not many people use ByteString for command line arguments. Text would work well, but I deliberately avoid the dependency on text - the https://hackage.haskell.org/package/shake-plus project might be a better bet for text.

Ok, it's fair you don't want to depend on text.
Regarding my Text/ByteString comment—I was suggesting that we might want a IsCmdArgument instance for Text not for literals, but rather for results of other computations. The point I was trying to make was that shake doesn't seem to support -XOverloadedStrings well anyway, hence it might not be too evil to add these instances. My use case is like this:
foo = do
    Stdout x <- cmd "wibble"
    (xs :: NonEmpty ByteString) <- processBigByteString x
    cmd_ "wuzzle" (map pack $ toList xs)

But, hey, I'm happy if I can at least omit the toList :)

I'm not too fussed about having a ByteString instance for CmdArgument. I guess it would be interpreted as UTF8? While I don't think I'd add one myself, I'd accept such a PR.

I wouldn't assume any encoding. I'd use unpack.

Sure, that's fine too.

What encoding does unpack implement?  Is it actually Latin-1, or is it a non-standard encoding that covers the same set of characters?  Either way, I'd prefer the type error to shake silently garbling my filenames.

See https://hackage.haskell.org/package/bytestring-<IP_ADDRESS>/docs/Data-ByteString-Char8.html#v:unpack:

More specifically these byte strings are taken to be in the subset of Unicode covered by code points 0-255. This covers Unicode Basic Latin, Latin-1 Supplement and C0+C1 Controls.

Comparing the U0080 codepage with Latin-1 it looks like unpack will correctly decode Latin-1 text, as well as accepting some bytes that aren't valid Latin-1.  (I thought Latin-1 assigned meaning to all 256 bytes, but it doesn't.)

Yes, on second thought I think Data.ByteString.Char8 is dangerous. I suppose we can assume UTF8, with an appropriate comment that the StdinBS option can be used for raw bytestreams. Would this be an acceptable solution?

I.e. I can't think of any scenario where this might lead to confusing behaviour, but I might be overlooking something.

Given there are two possible interpretations, my inclination is not to bake either choice into an instance - people can manually convert to String in whatever locale makes sense for them. Anything else is going to be buggy for someone.


Rekognition api

Updated the readme to discuss more app setup (running commands to get the app to run, but also getting the API keys).
Added a class for handing the Rekognition API calls (scan a predetermined video; pull that response).
Added a class for handling the Rekognition response data structure.
Updated Video Recording screen to interface with rekognition api.
Added a Video Response UI screen to review the results of the selected scan job.
Open Video screen.docx

Did you merge camera screen branch into this one?


Per-vertex border colour/alpha for CleanTriangle and CleanConvex + small test project changes

Main changes to the library:

Added per-vertex border colour/alpha to CleanTriangle (.Border3) and CleanConvex (.BorderExt)

Changes to the test project:

Added a lil controller object to hop between the test rooms, instead of having to drag the one you wanna look at to the top and then compile...
Fixed the pug test (was missing a CleanTransformReset() screwing up other test rooms)
Edited oTestSurface so it doesn't throw a CleanSpline-related error (will report bug separately)
2.3.2 stable

Could you split this PR up into smaller pieces please?


Compiler: fix named args type matching

Fixes #7523
The order of matching named arguments type was wrong (match vs. signature but should have been the other way around).

Yeah, it should probably be named "can be cast to", but in general the whole matching logic should be refactored. This is just a small patch.

Awesome! Can't wait to try this out on some stuff I'm working on. I just noticed there is a highly docker build so I'll give that a try later. Thanks for fixing this!


Bug: calling getPayload multiple times

The last time a block was produced I got the following logs:
- level=debug msg=getPayload method=getPayload version=v1.5.0
- level=debug msg="calling getPayload" ...
- level=info msg="received payload from relay"
- level=info msg="http: POST /eth/v1/builder/blinded_blocks 200"
- level=debug msg=getPayload method=getPayload version=v1.5.0
- level=debug msg="calling getPayload"
- level=warning msg="error making request to relay, retrying" blockHash=x error="HTTP error response: 400 / {\"code\":400,\"message\":\"payload for this slot was already delivered\"}\n" method=getPayload
- level=warning msg="error making request to relay, retrying" blockHash=x error="HTTP error response: 400 / {\"code\":400,\"message\":\"payload for this slot was already delivered\"}\n" method=getPayload
- level=warning msg="error making request to relay, retrying" blockHash=x error="HTTP error response: 400 / {\"code\":400,\"message\":\"payload for this slot was already delivered\"}\n" method=getPayload
- level=warning msg="error making request to relay, retrying" blockHash=x error="HTTP error response: 400 / {\"code\":400,\"message\":\"payload for this slot was already delivered\"}\n" method=getPayload
- level=warning msg="error making request to relay, retrying" blockHash=x error="HTTP error response: 400 / {\"code\":400,\"message\":\"payload for this slot was already delivered\"}\n" method=getPayload
- level=error msg="error making request to relay" blockHash=x error="request context error after 6 attempts: context deadline exceeded" method=getPayload parentHash=x url="https://relay.ultrasound.money/eth/v1/builder/blinded_blocks" version=v1.5.0
- level=error msg="no payload received from relay!" \
- level=info msg="http: POST /eth/v1/builder/blinded_blocks 502

Omitted some information, and can share more in private via request.

Payload was received, the block was proposed successfully and was not orphaned.

Tracked here: https://github.com/flashbots/mev-boost-relay/issues/397
Fixed on relay mainnet branch (https://github.com/flashbots/mev-boost-relay/pull/400), will be deployed to mainnet relays soon.

This should have been fixed and deployed now (see also https://github.com/flashbots/mev-boost-relay/issues/397)


Removed bytes that appeared as double dash on windows.

Signed-off-by: Konstantina Chremmou<EMAIL_ADDRESS>

Merging this myself as the change is not visible to the eye.


OnClick: StopPropagation Enhancement

Description
Normally a user can need stopPropagation if they use OnClick event. However we did not have stopPropagation parameter in our components. This time, blazor doesn't allow to use OnClick and onclick:stopPropagation both. If we want to use them both we need to describe it in our components.
So with this PR, if a component has onclick method, we added a OnClickStopPropagation parameter to use them both.
Note: If a component already had OnClickStopPropagation, we also add the parameter, but this time set it initially true.
Note 2: I think we may discuss stopPropagation option on all components but its better to postpone it with input and theme remakes.
How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

@Garderoben This adds the boolean parameter OnClickStopPropagation to every component which uses @onclick. What do you think?

Wouldn't it make more sense to put this in a base component, like MudComponentBase?
Also, which onclick takes precedence, and is the order guaranteed?
@onclick="OnClickHandler" @onclick:stopPropagation="OnClickStopPropagation"

I could be wrong, but implementing this is waiting for Pandora's Box to be opened.

We cant add this into MudComponentBase for now, because if we add it, we accept all components has stop propagation, but actually it has no effect until we describe a stop propagation mechanism in the component itself.
And sorry i didnt understand the precedence.

@Garderoben This adds the boolean parameter OnClickStopPropagation to every component which uses @onclick. What do you think?

I dont know, i think its unnecessary for us as a component library. I really dont see why most of this components would need this, we design components to do what they do. In some cases we have even set the propagation specifically because it needs to be in that way.
Like why did you change the Alert, Badge etc here? can you provide a real usecase?

Like why did you change the Alert, Badge etc here? can you provide a real usecase?

If a user has their own click method on container div, they may want to stop propagation on badge, alert etc. click. Example i set a click method on page, but i want to call this only click directly on div, not on bubbled component clicks.
In current users have to write this if they want to use stopPropagation
<div @onclick:stopPropagation="true">
  <MudBadge />
</div>

Now we can directly use stopPropagation
<MudBadge OnClickStopPropagation />

Like why did you change the Alert, Badge etc here? can you provide a real usecase?

If a user has their own click method on container div, they may want to stop propagation on badge, alert etc. click. Example i set a click method on page, but i want to call this only click directly on div, not on bubbled component clicks.
In current situation, users have to write this if they want to use stopPropagation (if they have onclick method)
<div @onclick:stopPropagation="true">
  <MudBadge />
</div>

Now we can directly use stopPropagation
<MudBadge OnClickStopPropagation="true" />

That some one have OnClick on whole page is very...  rare. Secondly i dont see a issue, nor why we should complicate things when users can easily add this themself? either with CSS or set @onclick:stopPropagation="true" on parent themself.

That some one have OnClick on whole page is very... rare. Secondly i dont see a issue, nor why we should complicate things when users can easily add this themself? either with CSS or set @OnClick:stopPropagation="true" on parent themself.
Most of this component that you changed feels very point less in doing this change on. There might be one that makes sense but I doubt it.

I don't make arguments about complexity or we really need this. I also doesn't need to this in my application. I am talking about design.
https://try.mudblazor.com/snippet/cYGQuIwecXgAFrAE
Please look at this example. Native html and blazor components like input, div, span etc accepts both onclick and onclick:stopPropagation, but our components not. When we added these two parameters in a mud component we have a compile error like this:
The component parameter 'onclick' is used two or more times for this component. Parameters must be unique (case-insensitive). The component parameter 'onclick' is generated by the '@onclick:stopPropagation' directive attribute.
I only pointed this problem. I think if blazor hative elements can accept these parameters both, so Mud elements have the same capability too. Its not unnecessary API, they are not created feature by us, they are already blazor have, so we should add this in our components.
Actually i prefer to add this in all components by design.


Be consistent in the exception types thrown by core metadata

For very similar cases in core metadata we sometimes throw ArgumentException, sometimes throw InvalidOperationException, and sometimes throw ModelItemNotFoundException. We should decide what the general categories of errors are here and then be consistent in what we throw.

ModelItemNotFoundException is removed
I propose to throw ArgumentException if the condition is only on the arguments, not any other state, otherwise throw InvalidOperationException


Error after attempt to launch. :c

Error message
An item with the same key has already been added. Key: [, StudioCore.Editors.TextureViewer.TextureFolderBank+TextureViewInfo]
This is right after launching the program. All 3 required programs have been installed.

Smithbox - Version <IP_ADDRESS>
An item with the same key has already been added. Key: [, StudioCore.Editors.TextureViewer.TextureFolderBank+TextureViewInfo]
at System.Collections.Generic.TreeSet1.AddIfNotPresent(T item)    at System.Collections.Generic.SortedSet1.Add(T item)
at System.Collections.Generic.SortedDictionary`2.Add(TKey key, TValue value)
at StudioCore.Editors.TextureViewer.TextureFolderBank.AddTextureFolder(String path, TextureViewCategory category, Boolean isModFile) in ./src/StudioCore/Editors/TextureViewer/TextureFolderBank.cs:line 310
at StudioCore.Editors.TextureViewer.TextureFolderBank.FindTextureFolder(String folderDir, String fileExt, TextureViewCategory category) in ./src/StudioCore/Editors/TextureViewer/TextureFolderBank.cs:line 284
at StudioCore.Editors.TextureViewer.TextureFolderBank.ScanPartsFolder(TextureViewCategory category) in ./src/StudioCore/Editors/TextureViewer/TextureFolderBank.cs:line 193
at StudioCore.Editors.TextureViewer.TextureFolderBank.LoadTextureFolders() in ./src/StudioCore/Editors/TextureViewer/TextureFolderBank.cs:line 52
at StudioCore.TextureViewer.TextureViewerScreen.OnGUI(String[] initcmd) in ./src/StudioCore/Editors/TextureViewer/TextureViewerScreen.cs:line 220
at StudioCore.Smithbox.Update(Single deltaseconds) in ./src/StudioCore/Smithbox.cs:line 617
at StudioCore.Smithbox.Run() in ./src/StudioCore/Smithbox.cs:line 327
at Smithbox.Program.Main(String[] args) in ./src/Studio.App/Smithbox/Program.cs:line 36

I'll look into this, looks like a missing condition before the dictionary add. Might be due to the new update too.

Ok thanks. I'll just wait for update.


[4.x] Header are not forwarded to the request in the React Native build

Do you want to request a feature or report a bug?
BUG
What is the current behavior?
We can't set extra headers (e.g. referer) with the React Native build.
client.setExtraHeader('referer', 'value');

The browser implementation inline the headers to avoid the CORS preflight request (with a Simple Request). But in a native environment (like React Native) there is no concept of CORS so we can set the headers directly on the request.

Going to close this, please re-open this issue if you think we may face this issue with the v4.


pico-pi-imx7d: bump to dunfell

depends on https://github.com/mendersoftware/meta-mender/pull/1398

Hey @texierp
there is a PR for backporting the patch to meta-mender.
https://github.com/mendersoftware/meta-mender/pull/1401
Once it's done I will merge this.

Thanks for the feedback @TheMeaningfulEngineer ;)

Hi @TheMeaningfulEngineer
This PR can be merged ;)
Commit in meta-mender is now on dunfell [1]
[1] - https://github.com/mendersoftware/meta-mender/commit/906c17722eace50674f3b9983c1f5d2f989ab699

Thanks @texierp
Merging


Maintenance: Replace tab indentation with two-space.

Everybody else in the Ruby world uses two-space, so we
should too.

There are still tabs in Gemfile, README.md, Rakefile, ruby-macho.gemspec, and test/src/{,lib}hello.c. Is that intentional or an oversight?

Oops, oversight. I'll fix that right now.


Can this run on apache?

I want to run your application on apache. Is this possible? If yes, what is the vhost config?

@Arjoni I believe that it is possible in this case putting the public folder on your host configuration

Yes I confirm

@Arjoni vhost config for this would be
<VirtualHost *:80>
  ServerName koel.local
  DocumentRoot <Absolute path to public folder in koel>
  ErrorLog <Absolute path to error log for this vhost>
</VirtualHost>

This config will make koel available on koel.local

DocumentRoot should be the Koel's installation root actually.
On Tue, Feb 2, 2016 at 10:46 AM, Vivek Kumar<EMAIL_ADDRESS>wrote:

@Arjoni https://github.com/Arjoni vhost config for this would be
<VirtualHost *:80>
ServerName koel.local
DocumentRoot
ErrorLog

This config will make koel available on koel.local
—
Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/215#issuecomment-178327416.

@phanan Only public directory in Laravel should be made public since making Laravel's installation public can cause security issues if not configured properly.

Configure it properly then. I think the provided .htaccess should do it.
Anyway, I was giving recommendation as the one who came up with Koel's
folder structure.
On Tue, Feb 2, 2016 at 11:13 AM, Vivek Kumar<EMAIL_ADDRESS>wrote:

@phanan https://github.com/phanan Only public directory in Laravel
should be made public since making Laravel's installation public can cause
security issues if not configured properly.
—
Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/215#issuecomment-178337937.

@phanan Ah. Got it. For koel, the DocumentRoot needs to installation directory.


Ability to get gifts via gift token

Hello there! Not a long time ago i mistaked #499 as something i've met before. The point is that sometimes its proficient to buy game directly in steam, send it as a gift to your bot, and farm it out. And all hapens well if you have your bot in your freind-list. But lets look at one of these situations:

You dont have bot in your freind-list.
You've got a gift from some site/service in a token form

Then you would have some problems with redeemeng a gift.
Also i would like to say that i dont have my bots in my freind-list. I just really like to keep it short.
So, what i did, is i created a new function IsValidGiftToken with regex ^[0-9A-F]{16}$. Then implemented some simple code in ArchiWebHandler:
string request = SteamStoreURL + "/account/ackgift/" + token;
return await WebBrowser.UrlHeadRetry(request).ConfigureAwait(false);

(got a crash after i removed 'const' ,not sure if it)
Next, there were no problem to implement a new function !getgift <Bot> <token>
It works just fine. Bot accepts and redeems gift shortly after executing a command. This command helped me to redeem some gifts.
So why i didnt a PR? Dirty code, <Bot> instead of <Bots>, no response check, possibility to merge it with !redeem.
I was trying to fix it all by myself, but i stuck at the point where i was thinking: shall i forward or distribute a token? Right now im pretty confused with "How its all should look like?", basicaly because i haven't enough expirience to code it in a good way.
P.S. I've got a strange crash after recoding. Not sure now if UrlHeadRetry could stable work with not constant string, tested well only with const string, Anyway, all you need to do is a GET with cookies.

Command-wise I don't see it as an issue, but you should definitely check if you can't achieve what you want already with reverse-engineered ArchiHandler.RedeemGuestPass() which is being used for implementing AcceptGifts in ASF. Using AWH for web-based commands should be the last thing to do, once we're sure there is no better way to do this from within Steam network.
Regarding any kind of forwarding and distributing - this will be only possible if gifts include information about what packageID they're about to add. If they lack that info, don't even bother.

First of all - I'm still not sure if this is the best idea. If we ever implement #499 there will be certainly a better way, but so far we not have it the suggestion sounds legit.
What I wanted to tell - I doubt that forwarding possible without implementing #499 first, because, if I remember it right (you may want to check it), after you try to accept the gift - token gets invalid, even if you didn't actually received the gift. Also, this will interfere with current accepting gifts implementation (it only works for you because of this, because just accessing /account/ackgift/<token> is not enough for redeeming). Because of this I think it's a bad idea to try to merge it with !redeem, in the best case we will achieve different behavior of command depending of what we send as a parameter, and that's not a good way - commands behavior should be predictable.
I don't even know if we need this command with syntax for multiple bots at all. I just realized I never tried to use !redeem with both multiple keys and multiple bot names, I should really investigate how it works, maybe this will give me an idea about usability of similar command for gift tokens.
And, in any case - then there is one more problem to be solved - regexp ^[0-9A-F]{16}$ can match bot name, if the name is exactly 16 characters. Unlike keys (they at least have dashes) this can cause troubles to users who use descriptive names for bots. Can't say how important this issue, as I have no statistics of bot naming. Maybe @JustArchi could parse bot names with statistics = true and check if we have something that match this pattern?

Bot name is not important, every command is supports n arguments, and n + 1 with bot name included - this is no different. Yes, there are many commands which can't make use of <Bots> and would fine with <Bot> alone, but actually implementing exclusive support for <Bot> syntax when <Bots> is already implemented is waste of time - both machine during compilation, and your own one as a programmer.
I don't like this idea that much either and I definitely won't accept half-broken behaviour - if we ever want to add command like this, we must answer following mandatory questions:

Is it possible to use ArchiHandler.RedeemGuestPass() for redeeming? If not, there is a very good chance this should not be added in the first place.
Can we read packageID from the gift? If not, any forwarding/distributing is out by definition.

And definitely this is out of !redeem function that is already 3x longer than it should be. If anything, this should be another command.
BTW, @Ryzhehvost - #499 has nothing to do with it, since if we even implemented that, it would be simply sending gifts through direct gifting, and ASF already has support for it in AcceptGifts - those two issues are mutually exclusive, and do not depend on each other.

#499 has nothing to do with it

It has, because

those two issues are mutually exclusive

And #499 is better and more native implementation. If we will have #499 - this function is useless.. But I'm not ready to start development of #499, and if I understand it right - you don't want to implement it in the near time too (and I completely understand why). So, in the meantime we may have this, if @TheSergiooo thinks (at least) he will use it, and when(if) we implement #499 - we can just deprecate this command (or leave it as is, if it does not cause us any problems).

I'm not sure how ackgift works, if it just uses token and then forwards gift to guest passes that AcceptGifts can parse

Yes, that's how it work. If you receive the gift by email and follow the link from it in the web browser, where one of asf bots logged in - you will never be able to redeem it, because after the link is opened ASF will see it in the queue and redeem it before you are able to press "accept".

And if we can, are we able to keep gift unused and forward token further?

No, we can't. Just checked it, second account gets this error:

An error was encountered while processing your request:
There was a problem redeeming the gift. Please try again later, or contact Steam Support for assistance.

Then solution proposed by @TheSergiooo is fine by me - we'll have a command that requires AcceptGifts to be set to true and allow to "claim" gift with given token for bot account, which will be automatically redeemed. This is the whole point of this, and it sounds good to me, definitely a lot better than implementing #499 - and a lot easier too.

And due to complexity of this, there is no forwarding included whatsoever - if we ever want to implement any forwarding, it should be implemented in a function that is dealing with AcceptGifts natively - this command would just "claim" the gift and add it to the parsing queue.
But I do not recommend starting any work on this, unless you want to reverse-engineer yourself. A command for claiming gifts is OK though, since it's only a bridge to ASF logic that is already implemented.

On a second thought - I'm unsure if this idea will give any profit.
Let's see, to send gift to the bot this way, one will need:

Buy a gift, and send it to your own email.
Open email, and copy token from the gift link
Send the command with token to the bot.

Without this command, one will need:

Invite bot in question to friends.
Buy game and send it directly.
Remove bot from friends.

Unsure which way is faster and more convenient. Of course, it will be much more useful if you received gift from someone or bought a gift link on some gray market.
Actually, while thinking about this suggestion and #499 I came to one more idea, but I'll put it to separate issue, to not clutter this one.

First of all, i would like to thank you very much for your response. I've got answers i wanted.

But I do not recommend starting any work on forwarding, unless you want to reverse-engineer yourself.

Thats a relief. I've already done some code that works just fine without forwarding and then stuck. Now i will try to clear my code and make a PR with !getgift

On a second thought - I'm unsure if this idea will give any profit.

I would like to implement this feauture not because it would be easier to send gifts - no, it's because right now, only way to redeem a gift token is trough steam website. And even if you would get a small amount of tokens, maybe just 10, then redeeming would start to become a headache

@JustArchi we can get appID or subID from game picture src in <img> tag in email (if it exists)
Just checked my email with tons of different emails with different games:
SubID - http://cdn.akamai.steamstatic.com/steam/subs/49788/header.jpg?t=1447456033 (giftmail with Deus Ex Collection)
AppID - http://cdn.edgecast.steamstatic.com/steam/apps/513320/header.jpg?t=1488452427 (giftmail with Alice VR)

@KazeZlat asf does not get emails, so it can't parse it contents.

@Ryzhehvost just take a look of what I wrote in #499
I know ASF doesn't get emails, but can get it contents via POST queries in ArchiWebHandler.

Now i will try to clear my code and make a PR with !getgift

:+1:. I think !ackgift command would be better, but that's misc naming though. Remember to requrie AcceptGifts in this command, same like !input requires Headless.

With recent changes from Valve it's impossible to send gifts to email, and thus no way to get token, am I right? If it is so - this issue is probably obsolete and can be dropped.

@Ryzhehvost you can still do this for previously bought gifts, but yea, someday it can be dropped.

Due to recent gifting changes from Valve there's no point working on this anymore, if nobody coded anything regarding this yet. Therefore I'm closing this issue, at least until it is possible to make use of it for newly bought gifts.


why we need the first indexs2.shape[0] in gt_bo_masks[:indexs2.shape[0]]?

Thanks for your attention, codes as follows.
new_gt_bo_masks1 = gt_bo_masks[indexs2,:,:].squeeze()
new_gt_bo_masks2 = gt_bo_masks[:indexs2.shape[0]]
if new_gt_bo_masks1.shape != new_gt_bo_masks2.shape:
new_gt_bo_masks1 = new_gt_bo_masks1.unsqueeze(0)
new_gt_bo_masks = torch.cat((new_gt_bo_masks1, new_gt_bo_masks2),0)

Thanks for the question.
This code section is to balance the number of occluded objects vs. non-occluded object during mask loss training. It is beneficial for the first GCN layer for predicting the occluders by making occluded objects occupying over 50%.


FIO-9321 fixed onlyAlailableItems validation for select Boxes

Link to Jira Ticket
https://formio.atlassian.net/browse/FIO-9321
Description
The problem of incorrect Only Available Items validation of the Select Boxes component value has been fixed.
The value of the Select boxes component is a map with pairs key (value option) - value (true or false). Therefore the check for the difference between the data value keys and allowed options values has been added.
Breaking Changes / Backwards Compatibility
n/a
Dependencies
n/a
How has this PR been tested?
Automated tests have been added. All tests pass locally
Checklist:

[x] I have completed the above PR template
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (if applicable)
[x] My changes generate no new warnings
[x] My changes include tests that prove my fix is effective (or that my feature works as intended)
[x] New and existing unit/integration tests pass locally with my changes
[ ] Any dependent changes have corresponding PRs that are listed above

This looks good, but shouldn't we add the same condition to the synchronous version of this function (for, I guess, static values only)?

The check works for both types of Select Boxes: static values and with url dataSrc. Appropriate tests have been added


Registry - removeEventlistener can remove references to other active event listeners

With the recent change introduced in 5.4.0, to reduce memory usage during app lifetime, seems to have introduced a new memory leak. The code I'm referencing to is in the removeEventListener function:
https://github.com/rdkcentral/Lightning-SDK/blob/01e0ab82e85be1ebca701ecf281b9712a1a5394b/src/Registry/index.js#L139-L143
For example: we first add an event listener on target A and then an event listener on target B.
If we then first remove the event listener on target A, it seems to also remove any references to target B and its event listeners. So when we try to remove the event listener on target B, we get an error that it cannot be found. However, the event listener itself was not removed. It looks like splice is removing all elements from the startIndex to the end of the array, which could remove references to  event listeners that are still active.

Hey @Jns-Rs
Thanks for bringing this issue upfront. We have fixed the issue and created a PR.
Please check if this fixes your issue. #401 .

Hello @sandeep-vedam
Just tested this out in our project and the issue is fixed. Thanks for the quick fix.


PWA

Here is some code to make it a Progressive web app

I will take a look thanks. Currently i’m working on something else which may cause some conflicts.


[resolves #682] Remove shading of the config tool

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/488/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/489/
Test PASSed.


Aba matrix with lu factorization

Modified the structure and methods for the ABA matrix for better use in PowerFlow.jl

closing pull request since branch was created from outdated version of main (no docstrings).


Avoid API changes in revisions (x.y.Z).

Re: https://godotengine.org/article/maintenance-release-godot-2-0-4 -
"Added InputMap.get_actions()"
"Rename CanvasItem.edit_get() to edit_get_state()"
Whilst the former isn't such an issue, the latter could cause (albeit only minor) issues if the previous syntax/statement is removed altogether.
Perhaps such changes should either be reserved for minor versions (x.Y.z) or a warning added that the previous way of doing things is obsolete (and to be removed at the next minor version increase)?

Yeah but see #4653.
As long as I will be alone to maintain the stable branch, I'll continue doing it with my gut feeling and won't overly bother myself with trying to preserve 100% API compatibility. I think I'm doing an OK job already, and so far nobody complained about any API change (apart from people concerned from a theoretical standpoint).
InputMap.get_actions() does not impact the existing API, it just adds a simple new method, I don't see why anyone would be annoyed by having one function more. You don't have to use it.
Renaming CanvasItem.edit_get() is indeed an API breakage and I thought a bit about it before cherry-picking it, but I consider that the previous function name was a bug, and if a couple users were using it, they'll check the release notes and see why they're now getting an error.

No complaints here. I hadn't been aware of #4653 (or its unpleasantness).

Closing as I think that the current subjective cherry-picking I do for patch releases is good enough. I'd be open to real life examples from users that got issues due to the limited API changes that were done over 2.0.x; so far the feedback is mostly positive, so I'm happy enough with how I worked.


Feature: Add IPv6 Match Function

Fixes #10817.
Description
Added a SQL function to match IPv6 addresses to a given subnet. This was based off the existing IPv4_MATCH function. I initially considered changing the existing IPv4_MATCH function to be a more generic (e.g. IP_MATCH). However, given this has been a function for some time I thought it best to keep the existing function for existing queries and make an IPv6 specific implementation. Like the existing IPv4 implementation, this relies on the Java inet.ipaddr library
Release note
Added IPv6_MATCH SQL function for matching IPv6 addresses in a subnet
Key added classes in this PR

IPv6AddressExprUtils
IPv6AddressMatchExprMacro

This PR has:

[x] been self-reviewed.
[x] added documentation for new or modified features or behaviors.
[x] a release note entry in the PR description.
[x] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[x] been tested in a test Druid cluster.

Looks like the IT tests are a little flaky. Is it possible to rerun a single check?

Hi - is there an approx ETA for a release containing this change?

Hi - is there an approx ETA for a release containing this change?

It will depend when this PR gets reviewed. I've been keeping an eye on it but unfortunately I don't have any way of asking maintainers to have a look. Doesn't look like this will get in prior to the current 28.0 milestone but hopefully the one afterwards (reviews dependent!)

@LakshSingla, @abhishekagarwal87 Sorry to bother you both but would it be possible to get a PR review on this please? Just been open a while and I would welcome your feedback!


Update pylint

Pull Request Description
What issue does this change request address?
#1764
What are the significant changes in functionality due to this change request?
This fixes pylint checking ravenframework instead of framework, and also fixes all the accumulated pylint failures that had not been noticed because this checking was not working.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Hm, on second thought, we should change the dill library requirement in HERON/dependencies.xml not in RAVEN.

Job Mingw Test on 34f34d7 : invalidated by @joshua-cogliati-inl
FAILED  Diff tests/framework/PostProcessors/EconomicRatio/timeDepDataset

Job Test qsubs sawtooth on 34f34d7 : invalidated by @dylanjm
Sawtooth Outage Complete

Job Test qsubs sawtooth on 34f34d7 : invalidated by @wangcj05
sawtooth is back


Import: Modify Client to initiate import from all locations

Invoke command from:
Import will be able to be initiated from any place we currently expose adding a new deployment, as well as explicitly within the triple-dot menu and the command palette.

Add to the … menu next to deployments
Add to the options listed when user clicks + sign to add new deployment
Add to the options listed when user clicks on select deployment
Add import command to the VSCode Command Palette
NOTE: We did not choose to move forward with a separate explicit import button.

Closing, as we have moved to a simpler initial implementation: #2285


License of the future – CC0

The person who associated a work with this deed has dedicated the work to the public domain by waiving all of his or her rights to the work worldwide under copyright law, including all related and neighboring rights, to the extent allowed by law.
You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission. See Other Information below.
…

In full: https://creativecommons.org/publicdomain/zero/1.0/

It is merged 😂


ERROR: rtl8821au (this driver is not recommended - expect driver errors)

ERROR: rtl8821au (this driver is not recommended - expect driver errors)
HW INFO: TP-LINK Archer T2U Plus AC600
SW INFO:
-driver installed https://github.com/morrownr/8821au-20210708.git
`# lsusb
Bus 001 Device 002: ID 2357:0120 TP-Link Archer T2U PLUS [RTL8821AU]
aireplay-ng --test wlan0
20:43:05  Trying broadcast probe requests...
20:43:06  Injection is working!
20:43:07  Found 1 AP
hcxdumptool -o id.pcap -i wlan0 --enable_status=1 --filterlist_ap=id.txt --filtermode=2
This is a penetration testing tool!
It is made to detect vulnerabilities in your NETWORK mercilessly!
Don't report bugs if this tool does exactly what it was coded to do!
initialization of hcxdumptool 6.2.7-59-g0a12c7b (depending on the capabilities of the device, this may take some time)...
BPF is unset. Make sure hcxdumptool is running in a 100% controlled environment!
interface is already in monitor mode, skipping ioctl(SIOCSIWMODE) and ioctl(SIOCSIFFLAGS) system calls
start capturing (stop with ctrl+c)
NMEA 0183 PROTOCOL........: N/A
PHYSICAL INTERFACE........: phy0
INTERFACE NAME............: wlan0
INTERFACE PROTOCOL........: IEEE 802.11b
INTERFACE TX POWER........: 0 dBm (lowest value reported by the device)
INTERFACE HARDWARE MAC....: 2887baafaa2a (not used for the attack)
INTERFACE VIRTUAL MAC.....: 2887baafaa2a (not used for the attack)
DRIVER....................: rtl8821au (this driver is not recommended - expect driver errors)
DRIVER VERSION............: v<IP_ADDRESS>-0-g70054197b.20210708
DRIVER FIRMWARE VERSION...: 42.4
openSSL version...........: 1.0
ERRORMAX..................: 100 errors
BPF code blocks...........: 0
FILTERLIST ACCESS POINT...: 1 entries
FILTERLIST CLIENT.........: 0 entries
FILTERMODE................: attack
WEAK CANDIDATE............: 12345678
ESSID list................: 0 entries
ACCESS POINT (ROGUE)......: 000dc25cb63e (BROADCAST WILDCARD used for the attack)
ACCESS POINT (ROGUE)......: 000dc25cb63f (BROADCAST OPEN used for the attack)
ACCESS POINT (ROGUE)......: 000dc25cb640 (used for the attack and incremented on every new client)
CLIENT (ROGUE)............: e00db9b3da0a
EAPOLTIMEOUT..............: 20000 usec
EAPOLEAPTIMEOUT...........: 2500000 usec
REPLAYCOUNT...............: 62955
ANONCE....................: ce3e2bfb7d0d9400431210a2358e9a6231a7ef8ca5d274c1fc8fde0cecb8f772
SNONCE....................: d3bdceb082e45a86aa580b7f3ba45de9a0dba3ec1a3b5237530d32149a889aa8
TIME     FREQ/CH  MAC_DEST     MAC_SOURCE   ESSID [FRAME TYPE]`
?

could you tell me which driver should I use
tq

hcxdumptool use WIRELESS EXTENSIONS to control the device. Unfortunately some Realtek drivers do not support this calls. They use NETLINK instead and dropped WIRELESS EXTENSIONS. All(!) rtl88xxau drivers are based on NETLINK only.
aircrack-ng suite, iw and ip use libnl to communicate via NETLINK (nl80211) to control the device. That is absolutely no option for me:
airmon-ng -> iw -> libnl (nl80211) -> driver
airodump-ng -> libnl -> (nl80211) -> driver
but
hcxdumptool -> WIRELESS EXTENSIONS -> driver
Currently I'm working on a new version that use nl80211 without running into the dependency of libnl:
hcxdumptool -> WIRELESS EXTENSIONS/NETLINK -> driver
$ ./hcxlabtool -I -C

available wlan devices:

phy idx hw-mac       virtual-mac  m ifname           driver (protocol)
---------------------------------------------------------------------------------------------
  0   3 aca213117f56 aca213117f56 + wlp39s0f3u1u2    mt7601u (WIRELESS EXTENSIONS & NETLINK)
  1   4 3c7c3f498de0 3c7c3f498de0 + wlp39s0f3u1u3    mt76x0u (WIRELESS EXTENSIONS & NETLINK)
  3   7 f81a670dc527 f81a670dc527 + wlp39s0f3u1u1u2  rtl8xxxu (WIRELESS EXTENSIONS & NETLINK)
  6   9 74da380645e7 74da380645e7 + wlp39s0f3u1u4    rtl88XXau (NETLINK)
  7  10 7cdd908965fb 7cdd908965fb + wlp39s0f3u1u1u3  rt2800usb (WIRELESS EXTENSIONS & NETLINK)

+ monitor mode available
- no monitor mode available

wlp39s0f3u1u2 default scan list: frequency [channel] tx-power
  2412 [1] 20.0 dBm	  2417 [2] 20.0 dBm	  2422 [3] 20.0 dBm	  2427 [4] 20.0 dBm
  2432 [5] 20.0 dBm	  2437 [6] 20.0 dBm	  2442 [7] 20.0 dBm	  2447 [8] 20.0 dBm
  2452 [9] 20.0 dBm	  2457 [10] 20.0 dBm	  2462 [11] 20.0 dBm	  2467 [12] 20.0 dBm
  2472 [13] 20.0 dBm

wlp39s0f3u1u3 default scan list: frequency [channel] tx-power
  2412 [1] 16.0 dBm	  2417 [2] 16.0 dBm	  2422 [3] 16.0 dBm	  2427 [4] 16.0 dBm
  2432 [5] 16.0 dBm	  2437 [6] 16.0 dBm	  2442 [7] 16.0 dBm	  2447 [8] 16.0 dBm
  2452 [9] 16.0 dBm	  2457 [10] 16.0 dBm	  2462 [11] 16.0 dBm	  2467 [12] 16.0 dBm
  2472 [13] 16.0 dBm	  5180 [36] 20.0 dBm	  5200 [40] 20.0 dBm	  5220 [44] 20.0 dBm
  5240 [48] 20.0 dBm	  5260 [52] 20.0 dBm	  5280 [56] 20.0 dBm	  5300 [60] 20.0 dBm
  5320 [64] 20.0 dBm	  5500 [100] 20.0 dBm	  5520 [104] 20.0 dBm	  5540 [108] 20.0 dBm
  5560 [112] 20.0 dBm	  5580 [116] 20.0 dBm	  5600 [120] 20.0 dBm	  5620 [124] 20.0 dBm
  5640 [128] 20.0 dBm	  5660 [132] 20.0 dBm	  5680 [136] 20.0 dBm	  5700 [140] 20.0 dBm
  5720 [144] 13.0 dBm	  5745 [149] 13.0 dBm	  5765 [153] 13.0 dBm	  5785 [157] 13.0 dBm
  5805 [161] 13.0 dBm	  5825 [165] 13.0 dBm	  5845 [169] 13.0 dBm	  5865 [173] 13.0 dBm

wlp39s0f3u1u1u2 default scan list: frequency [channel] tx-power
  2412 [1] 20.0 dBm	  2417 [2] 20.0 dBm	  2422 [3] 20.0 dBm	  2427 [4] 20.0 dBm
  2432 [5] 20.0 dBm	  2437 [6] 20.0 dBm	  2442 [7] 20.0 dBm	  2447 [8] 20.0 dBm
  2452 [9] 20.0 dBm	  2457 [10] 20.0 dBm	  2462 [11] 20.0 dBm	  2467 [12] 20.0 dBm
  2472 [13] 20.0 dBm

wlp39s0f3u1u4 default scan list: frequency [channel] tx-power
  2412 [1] 20.0 dBm	  2417 [2] 20.0 dBm	  2422 [3] 20.0 dBm	  2427 [4] 20.0 dBm
  2432 [5] 20.0 dBm	  2437 [6] 20.0 dBm	  2442 [7] 20.0 dBm	  2447 [8] 20.0 dBm
  2452 [9] 20.0 dBm	  2457 [10] 20.0 dBm	  2462 [11] 20.0 dBm	  2467 [12] 20.0 dBm
  2472 [13] 20.0 dBm	  2484 [14] 20.0 dBm	  5075 [15] 30.0 dBm	  5080 [16] 30.0 dBm
  5085 [17] 30.0 dBm	  5090 [18] 30.0 dBm	  5100 [20] 30.0 dBm	  5120 [24] 30.0 dBm
  5140 [28] 30.0 dBm	  5160 [32] 23.0 dBm	  5180 [36] 23.0 dBm	  5200 [40] 23.0 dBm
  5220 [44] 23.0 dBm	  5240 [48] 23.0 dBm	  5260 [52] 20.0 dBm	  5280 [56] 20.0 dBm
  5300 [60] 20.0 dBm	  5320 [64] 20.0 dBm	  5340 [68] 20.0 dBm	  5360 [72] 30.0 dBm
  5380 [76] 30.0 dBm	  5400 [80] 30.0 dBm	  5420 [84] 30.0 dBm	  5440 [88] 30.0 dBm
  5460 [92] 30.0 dBm	  5480 [96] 26.0 dBm	  5500 [100] 26.0 dBm	  5520 [104] 26.0 dBm
  5540 [108] 26.0 dBm	  5560 [112] 26.0 dBm	  5580 [116] 26.0 dBm	  5600 [120] 26.0 dBm
  5620 [124] 26.0 dBm	  5640 [128] 26.0 dBm	  5660 [132] 26.0 dBm	  5680 [136] 26.0 dBm
  5700 [140] 26.0 dBm	  5720 [144] 13.0 dBm	  5745 [149] 13.0 dBm	  5765 [153] 13.0 dBm
  5785 [157] 13.0 dBm	  5805 [161] 13.0 dBm	  5825 [165] 13.0 dBm	  5845 [169] 13.0 dBm
  5865 [173] 13.0 dBm	  5885 [177] 30.0 dBm

wlp39s0f3u1u1u3 default scan list: frequency [channel] tx-power
  2412 [1] 20.0 dBm	  2417 [2] 20.0 dBm	  2422 [3] 20.0 dBm	  2427 [4] 20.0 dBm
  2432 [5] 20.0 dBm	  2437 [6] 20.0 dBm	  2442 [7] 20.0 dBm	  2447 [8] 20.0 dBm
  2452 [9] 20.0 dBm	  2457 [10] 20.0 dBm	  2462 [11] 20.0 dBm	  2467 [12] 20.0 dBm
  2472 [13] 20.0 dBm

bye-bye

The tested Realtek driver is from here:
rtl88XXau (as you can see NETLINK only)
https://github.com/aircrack-ng/rtl8812au
and here:
rtl8xxxu (luckily support of WIRELESS EXTENSIONS and NETLINK)
https://github.com/kimocoder/realtek_rtwifi
If the basic functions are coded and tested, I'll push them to:
https://github.com/ZerBea/wifi_laboratory
I think we can close this here, because there is no (known) WIRELESS EXTENSION driver for this interface.