Pass-through RSS proxy?

Thanks for a great project.
One thing that would be helpful for my use case, and might be easy to implement, is a pass-through bridge or proxy bridge that would take an existing RSS feed and generate an RSS bridge URL for it. No parsing would even be needed, though for security perhaps the admin would have to tick a box or whitelist some domains. I use another service as an aggregator and I've noticed that some websites like Reddit have started blocking them. It would be nice to use my existing RSS bridge install to proxy the feed before sending it to my aggregator.
Thanks again for a really solid project that is easy to install and use.

Filter bridge with no filters should do exactly that.

OK, this is great and exactly what I was looking for. Thank you.
I'm going to close the issue, but while I have you...is there a bridge for combining RSS feeds?

Not afaik. But why would you need to? 2 separate feeds just sort themselves into each other. Or are you limited by only being able to run one feed?

It depends on if your aggregator puts everything in one big stream or not. I prefer that it doesn't, since some feeds I monitor only loosely or have too much traffic, while others I might read everything. But I want to unify a bunch of twitter feeds under one RSS feed and have it come in as one feed, without integrating with my non-Twitter feeds. Sounds like RSS bridge might not have that functionality. Maybe if I get bored I'll brush up on my PHP and add a bridge for it :)

Eh, it's not a major issue, it's just a matter of clutter and looking for something tidier. I know it's not a real core thing that RSS bridge should do, just wondering if it had that functionality. There are other tools that do this, like Zapier, I just don't want to bother with them. Thanks for your help :)


How to use Ambassador to support GRPC protobuf field based ingress load balance

If I have a route.proto like this:
syntax = "proto3";
package routing;
message CopyImageRequest {
int32 camera_id = 1;
}
message CopyImageResponse {
string result = 1;
}
service RoutingService {
rpc service_A_hello(CopyImageRequest) returns (CopyImageResponse) {};
rpc service_B_hello(CopyImageRequest) returns (CopyImageResponse) {};
rpc service_C_hello(CopyImageRequest) returns (CopyImageResponse) {};
}
how can I use Ambassador to achieve ingress load balance by "camera_id"?

Please let us know and reopen if this issue persists on Ambassador v2.x.  Attaching our gRPC docs here for reference.


Change variable name "name" for key

Goal: make the key/value concept explicit. 'name' or 'var' it is not.

agreed, great thanks.


Make containers e2e test not complain on unexpected tags on nginx

What does this PR do?
Make the containers new-e2e tests ignore unexpected tags on nginx and redis metrics.
Motivation
If @DataDog/agent-integrations team modify the nginx or redis checks and make them send legit new tags, we don’t want to impact the containers e2e tests.
Additional Notes
Possible Drawbacks / Trade-offs
This effectively reduces the test coverage but nginx and redis tags should be asserted elsewhere.
Describe how to test/QA your changes
Check the new-e2e-containers GitLab job in the CI pipeline.

/merge

/merge


Error with line #37.

Getting this error, any idea where the issue lies? :-)
python3 hq_main.py
getting
Show not on.
Traceback (most recent call last):
File "hq_main.py", line 37, in
next_time = datetime.strptime(response_data["nextShowTime"], "%Y-%m-%dT%H:%M:%S.000Z")
KeyError: 'nextShowTime'

Could you post the log file?

This issue is consistent, it happens during broadcasting as well.

sure :-)

I'm still in the learning phase at the moment, I've only had a few weeks worth of experience with this.  Where would I locate the proper log?  The information under data.log in the HackQ_Trivia directory only says this: INFO:root:{'error': 'Auth not valid', 'errorCode': 105}.  I've taken care of the root issue so I don't believe that's the log that I'm looking for.  I used the command import logging.basicConfig(level=logging.INFO} and got this info: bash: syntax error near unexpected token `('    Is there somewhere else that I should be looking for a proper log file?  Thanks for your help! :-)

The log file you are looking at is the only one. I have updated the program so an error would be raised saying the connection settings are invalid when it is detected. Your bearer token is probably incorrect, which is causing HQ to not send you any information.

Awesome, and thanks for the help!  I'll check out my bearer token and see if that corrects my issue.

No problem. If you have trouble finding the correct bearer token and user ID, you can find 2 examples in gjacobs314's HackQ for Swift repository: https://github.com/gjacobs314/HQTrivia.

You were correct! It seems I didn't copy the entire bearer token.  For reason's I can't quite explain, I copied about 99% of the token but left just a bit behind.  Thanks again, everything is working great now!

That's great! Let me know if you have any more problems.


[BUG] Client-side error (".jsx is not a function") in production (minified) NextJS app

Describe the bug
We are using NextJS. We have used react-tooltip v4 with no problem. We have wrapped it with the mounting effect to avoid SSR errors. When we update to v5, we get an application (client-side) error in production that reads a.jsx is not a function. The library functions fine in development.
Version of Package
v5.9.1
To Reproduce
deploy a production build of a NextJS app using a tooltip of this version—navigate to the page. Note that this is a run-time application error, not a build error.
Expected behavior
It should not crash the application
Screenshots

Desktop (please complete the following information if possible or delete this section):

MacOS
Firefox
110.0.1 (64-bit)
React 18 / Next 13

Additional context
We are also using a turbo-repo, though I don't expect that's the issue

+1 for this. Our production is also gone now 😪

Do you mind creating a sample project to help us debug the issue? Just a simple NextJS project with the tooltip.
For now, please try v5.8.3 and see if it still happens.
We switched from rollup to esbuild on v5.9.0, so that might be the cause.

@gabrieljablonski Same issue on v5.8.3 as well

I fix version  "react-tooltip": "^5.8.3" to  "react-tooltip": "5.8.3".
It worked in production.

Hi guys, can someone create a sample project with this issue, please?
We will take a look as soon as possible when someone provides a sample project. Thanks!

Same here downgrade to 5.8.3 fixed the pb

I have the same issue.    If I set swcMinify: false in next.config.js, the error goes away.
Changing from "react-tooltip": "^5.7.4", to  "react-tooltip": "5.8.3", also resolves it.

@gabrieljablonski and @danielbarion Sorry about the delay, here ya go: https://github.com/thomasmost/react-tooltip-repro
Reproduced with the latest version (5.10)

@thomasmost Thanks for taking the time. As @devilsgeographer mentioned, you can set swcMinify: false on next.config.js as a workaround to this issue.
We'll be investigating why this is happening, but it seems to be an issue with the interaction between the default NextJS 13 minifier and our own bundling/minification process.
The issue will stay open until we figure it out.

@gabrieljablonski Glad to help! And no problem at all, as others have also mentioned, 5.8.3 doesn't seem to have this behavior. So I think I'm set for the time being 🙂

Thanks a lot @thomasmost - you're a lifesaver

Hi, can you try this beta version and let me know if it worked, please?
<EMAIL_ADDRESS>

@thomasmost thanks for the example repository, testest on it and it's working, please test and let me know

Working in my deployed app as well!

After some researches, it seems to be caused by the SWC minifier, enabled by default on next 13 onwards
The SWC compiler had quite a lot of issues that looks a lot like the one you pointed out. See for example https://github.com/vercel/next.js/issues/40601. I've tried<EMAIL_ADDRESS>on the provided repro https://github.com/thomasmost/react-tooltip-repro and the issue reappeared. I managed to solve it by setting swcMinify to false in next.config.js.
Using minified or unminified versions of react-tooltip did not changed anything. Eg: both works as long as swcMinify is false
Since other bundlers work without any problem, I have the feeling that this is a bug of swcMinify, that Terser (used when swcMinify: false) does not have.

I would not be surprised at all if it were a bug of swc, not really related to this package.

That being the case, what was changed in 5.10.1-beta.4 to resolve the issue though?
I can also link this issue with one in the NextJS GitHub...

@thomasmost not sure because we do not track beta releases, they are just for testing possible solutions purpose, also we have 2 PRs opened, one of them we started with the 5.10.1-beta.5, so, 5.10.1-beta.4 was before, maybe @gabrieljablonski remember

@danielbarion https://github.com/ReactTooltip/react-tooltip/issues/981#issuecomment-1464054004
not sure what was the exact change, but maybe this helps tracking it down

ohh, nice @gabrieljablonski
@thomasmost probably the first commit is related to the version that you want know the changes: https://github.com/ReactTooltip/react-tooltip/pull/982/commits/86549eea0efaf1fd184ce88928a006e1e422c748

I can confirm that<EMAIL_ADDRESS>corrects the issue for me. Will there be a patch version released with this?

Hi guys, we are still working on this, please check open PRs and let us know wich works 100% for you!
Thanks

I'll take a look as soon as possible with what we changed for beta 4, thanks for letting us know

guys, just a heads up, please check this comment: https://github.com/ReactTooltip/react-tooltip/pull/984#issuecomment-1485086609

guys, just a heads up, please check this comment: #984 (comment)

5.10.2-beta.1 fixes this issue for me on NextJS 13.1.6 (using SWC, not using experimental app folder), in both dev and production builds

The latest version (5.10.4) still has this issue for us.
We are using NextJS 13 with babel.
Downgrading to 5.8.3, as suggested above, helped.

@pohy @everyone please try this one: https://github.com/ReactTooltip/react-tooltip/pull/984#issuecomment-1488476993 (the next release candidate) and let us know.
I tested this PR using Next.js 13 + experimental APP folder and SWC enabled and worked.

This beta version is broken too
I using next 13.2.4, SWC
The error only occurs in a production build
When I hover over the element that triggers the tooltip, this happens

in bundle

@pohy @everyone please try this one: #984 (comment) (the next release candidate) and let us know.
I tested this PR using Next.js 13 + experimental APP folder and SWC enabled and worked.

I can confirm I'm running "next": "13.2.4", and after installing "react-tooltip": "^5.10.2-beta.4", and running npm run build and  npm run next start I'm no longer getting the above issues.

@AllanOliveiraM can you provide an example so I can test it, please?
Thanks for confirming @thathurtabit!

@thomasmost just tested your example and upgrading to Next.js 13.2.5-canary.22 release fixed the issue, so, probably next stable release of next.js will solve the problem (as it is caused by next.js)
cc @gabrieljablonski

@danielbarion
I installed version 13.2.5-canary.22 as you mentioned and that apparently fixed the issue
However, I don't understand exactly what the problem is
You who are inside the project will be able to answer me more safely, could there be a bug hidden in the react-tooltip code or can I rest assured that an update of next makes everything stable?

As mentioned above (https://github.com/ReactTooltip/react-tooltip/issues/972#issuecomment-1465259198), I personally highly suspect a bug in SWC minifier. Yet, all beta release you've seen mentionned are tries to limit occurrence of those bugs.
I cannot strcitly affirm it is a bug in next.js, nor affirm it is a bug in react-tooltip. That very specific kind of issue is a hell to diagnose properly.
Sorry for the back & forths.

Well thanks a lot for the help
I'm going to test and monitor it, since I depend a lot on the library
Anyway, if it happens again, I'll come here to tell you with more information to debug

I'd say we can technically consider #984 a fix for this issue.
In case Next.js takes too long to promote this new version to stable, we might consider adding a troubleshoot section to the docs/readme so people aren't left on the dark about this.


Clean up badges

Description

[ ] Badge for recently added Cirrus CI is missing (URL: https://api.cirrus-ci.com/github/nlohmann/json.svg, Link: https://cirrus-ci.com/github/nlohmann/json - it should be added
[ ] Badge for lgtm states no longer available - it should be removed

may I work on this?

Sure!


[Issue]: ImportError: Please install dependencies first although I already installed them.

The issue
I use a virtual environment and installed pyautogen[retrievechat] by running pip install "pyautogen[retrievechat]" but still getting the error saying that dependency isn't installed
Screenshots and logs

@selimhanerhan can you please run the following commands and report outputs:
pip list | grep chromadb
pip list | grep pyautogen

Hi Sorry for the late reply!
for grep pyautogen pyautogen         0.1.14
I get blank output when I type grep chromadb.
I reinstalled the chromadb and still getting the same output

The latest version of autogen is 0.2.6. Please install it with:
pip install "pyautogen[retrievechat]==0.2.6"

Then run the commands again and verify that you have the latest versions:
pip list | grep chromadb
pip list | grep pyautogen

Also make sure you are not using Python 3.12. Use Python 3.11.

Also make sure you are not using Python 3.12. Use Python 3.11. Related #1271

Thank you! this solved my issue.


Add a configurable title for the swagger ui

This will help to brand the REST API Swagger UI for different systems.
This could include the graphId.
This should probably be done after #1420.
To demonstrate this, we should update the example projects (road-traffic, basic, federated) to have different tittles.

Merged into develop.


.gitlab-ci: remove RHEL 8.6/9.0 ga runners

The commit message mentions 9.1 (incorrect) but the code change removes 9.0 (correct). Can you please fix that?

The commit message mentions 9.1 (incorrect) but the code change removes 9.0 (correct). Can you please fix that?

:facepalm: of course

For ostree we shold probably drop fedora 35 as well :duck: opening another one


History list Additions to track past alc consumption

Finished history additions. It will start when first drink is taken in and session will end when bac < 0.0001. Will make better check in the future.
It also saves peak BAC.
Ignore the negative number, I had end and start flipped.

LGTM


[BD-46] docs: new component examples and editable live code blocks

Description

[x] Ensure rendered components for each live code blocks are rendered on a light background (e.g., gray-200, light-200) to more clearly delineate where the code examples are on the page.
[x]  Ensure collapsible for showing the live code editor is rendered as the large card style (i.e., styling="card-lg").
[x] Ensure an icon (default Collapsible icon is likely fine) is rendered as an affordance to indicate that the live code block may be collapsed/expanded.
[x]  Discovery: make a recommendation for implementing a "Copy" to clipboard (icon)button for live code blocks to allow engineers/consumers to more easily copy/paste from the component code snippets on the docs site. If implemented, ensure it gets a Segment event when clicked where the event name follows the same convention as other Segment event names throughout the docs site.

Issue: https://github.com/openedx/paragon/issues/1981
Deploy Preview
Paragon
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[x] Does your change adhere to the documented style conventions?
[x] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[x] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @PKulkoRaccoonGang!
When this pull request is ready, tag your edX technical lead.

@PKulkoRaccoonGang 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

:tada: This PR is included in version 21.0.0-alpha.21 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 20.30.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[POC] ChatGPT integration

Set API key as env on watcher

kubectl set env deployment/pipelines-as-code-watcher CHATGPT_API_KEY=$(pass show chatgpt/apikey)

Generate an error from a task
Watch the magic

Demo
https://www.youtube.com/watch?v=4swhFkitMcs
ScreenShot

Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

/retest

/retest

/retest

/cancel go-testing

Nice thing! <3 👍


[CARBONDATA-2512][32k] Support writing longstring through SDK

Support writing longstring through SDK.
User can specify the datatype as 'varchar' for longstring columns.
Please note that, the 'varchar' column cannot be sort_columns.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?
NO

[x] Any backward compatibility impacted?
NO

[x] Document update required?
NO

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

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

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

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

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

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5679/

retest sdv please

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5693/

retest sdv please

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

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

LGTM


Clarify acceptable return values for sortType

Since the implementation just uses Array.prototype.sort, I wonder if we can change the documented return type for the sortType function to reflect that. Likewise, 0 is presumably also an acceptable return value, and we should document that, as well.
The reason for what may seem like a rather pedantic change here is to avoid unnecessarily having to convert comparison return values from functions like localeCompare (which only specifies generally a negative, positive, or zero value) to -1 or 1 in order to align with expectations set by react-table documentation.

Closing this to clear it out of my personal backlog.


DF Curvy Walls 3.3.0 not published

According to https://foundryvtt.com/packages/df-curvy-walls 3.2.4 is the latest, but https://github.com/flamewave000/dragonflagon-fvtt/blob/master/df-curvy-walls/CHANGELOG.md shows 3.3.0 is the latest and supports foundry v9. I'm guessing something happened and it didn't get published like the others?

It is currently in pre-release for my patrons. This is a 1 week beta. It will be fully released at the end of this week. This is the same for Chat Enhancements, Scene Enhancements, and Architect.


Pin clap to ~3.1

Derive macro receives a lot of deprecated warnings.
Refs: https://github.com/clap-rs/clap/issues/3822

bors r+


Not none check instead of OR in init: authz_state.py

fixes #33

this fixes #33

Please squash the fix of the apparent syntax error to the original patch and write a sensible commit message to keep the version history happy, otherwise the change itself LGTM.
Note that the travis checks fail because a pip version requirement needs to be added, see [#32] where I already fixed it.


Collapsible docs

Introduction
This is a

[ ] Bug/Issue
[x] Feature request
[ ] General stuff

Explain the feature
~Class~ Method level docs should be collapsible
Example (Click to toggle)

Example section
<?php

function a()
{
    return 'a';
}

fixed already. pls check resources/docs/docs.twig


[WIP] Fixup e2e tests after introducing v1beta3

TBD

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 58.05%. Comparing base (e4a2a0f) to head (324aa7e).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3494   +/-   ##
=======================================
  Coverage   58.05%   58.05%
=======================================
  Files         365      365
  Lines       20316    20316
=======================================
  Hits        11794    11794
  Misses       7269     7269
  Partials     1253     1253

Flag
Coverage Δ

unittests
58.05% <ø> (ø)

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

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


Geo-disaster recovery vs paired namespaces

Could you specify what a difference between geo-disaster recovery and paired namespaces.

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

ID: e985ad51-e8e6-6cd3-bde4-70fe0b29ee6a
Version Independent ID: 912d2335-78c1-9df7-09a6-3859b68e8ae4
Content: Azure Service Bus paired namespaces
Content Source: articles/service-bus-messaging/service-bus-paired-namespaces.md
Service: service-bus-messaging
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@bastyuchenko Thank you for your inquiry. We will investigate your question and get you the information you are seeking shortly.

@bastyuchenko At the very bottom of the page you are referring to with this issue, there is a link to content discussing disaster recovery in a little more detail; specifically paired namespace.
According to the content, paired namespace is to be used for high availability within a single data center or region. If you are looking to implement high availability beyond a single data center or region, you would implement geo-redundancy, which provides reliability should a single datacenter or region go off-line.
Implementing Geo-Redundancy: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-geo-dr
The geo-redundant high availability option is described in a seperate chapter, and does not link from the paired namspace content.
Please let me know if this provides you the information you are looking for. Thank you.

@bastyuchenko Please let me know if you need additional assistance with this inquiry. If you do not, I am going to move forward with closing this issue. Thank you.


[ServiceLinker] Support abstract base type using customization

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.ServiceLinker


kube apiserver unaccessible when unrelated egress policy is removed

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Sometimes, when a NetworkPolicy with egress rules is deleted, a Pod will lose access to 1 or both apiservers.
I've checked a couple nodes when they have pods experiencing the issue and the apiserver IPs are in the ipcache and their identities have the reserved:kube-apiserver label; no duplicate identities for the IPs. And this does not seem to affect existing connections.
Restarting the agent usually fixes the issue and the apiservers get new identities. Sometimes some nodes only block 1 of the apiservers after a restart. And so far, it's been a couple hours since the last restart and it hasn't happened again.
When a node is having this issue, it doesn't happen until a network policy with unrelated egress rules for the pod is deleted. Then the pod can't make connections the apiserver.
Having a cnp that has an egress rule for 443/TCP also fixes the denial issue. Seems a cnp with egress rule that allows world or includes a CIDR doesn't match.
I can reproduce this pretty reliable with an internal test suite we run. Gist is, it's adding/removing a handful of "services" (usually, 6 pods each) in parallel each with their own network policy with ingress+egress rules to allow only access to pods in the same service. There is a global CCNP that allows egress to 10/8, cluster, and world though. When our test suite cleans up a service, it will delete the service specific network policy before the pods are terminated, and that's when some of the pods have an issue accessing 1 or both of the apiservers. It's usually only a couple nodes (out of ~6) that it happens on, so that's why not all pods are affected.
https://github.com/cilium/cilium/pull/24875 does not fix this issue
Cilium Version
Client: 1.13.1 a6be57eb 2023-03-15T19:39:01+01:00 go version go1.19.6 linux/amd64
Daemon: 1.13.1 a6be57eb 2023-03-15T19:39:01+01:00 go version go1.19.6 linux/amd64
Kernel Version
Linux ip-10-0-0-231 5.15.0-1033-aws #37~20.04.1-Ubuntu SMP Fri Mar 17 11:39:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
EKS v1.23
Sysdump
No response
Relevant log output
No response
Anything else?
From https://github.com/cilium/cilium/issues/24502#issuecomment-1516784438:
> @dctrwatson interesting. At first glance, that seems like a separate issue. When the bug happens, do all pods (with an applicable policy) on the node in question lose access to the apiserver?

No, only pods that have their specific network policy deleted are affected. Other pods on the node continue to work fine until then.

> If you trigger it, can you confirm that the apiserver's IP is missing from cilium bpf ipcache list?

When I checked affected nodes, both apiserver ips there. That's why I wasn't sure if this was the same same issue. It just manifested similarly.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Have been running v1.13.4 for awhile now and have not had this reoccur.
The egress policy that doesn't seem to be affected:
egress:
      - toEntities:
          - kube-apiserver
        toPorts:
          - ports:
              - port: "443"
                protocol: TCP


ConsolidateBlocks should not fail because "failed to diagonalize M2"

Besides the problem with weyl_coordinates (see https://github.com/Qiskit/qiskit-terra/issues/3637#issuecomment-612970960), ConsolidateBlocks should not fail because the synthesis fails.
This PR considers that and continues even when synthesis fails.

The solution here: https://github.com/Qiskit/qiskit-terra/issues/3637 does not fix this?

I think the solucion for #3637 is normalization. The code raising in #3637 is independent from the transpiler. This PR is about the transpiler should continue when synthesis fails (does not matter why).

But the user should be explicitly told that consolidate blocks is not being run if that is the case.

:+1: We would not have found and fixed the case from #3637 if the failure had been caught silently. The synthesis algorithms aren't expected to fail regularly, so I'm okay with allowing it to raise when it fails.

closing in favor of https://github.com/Qiskit/qiskit-terra/pull/4156


examples(with loki.js): add a new example with loki.js

Types of changes

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

Description

This adds a new example demonstrating a number of key concepts.
This demo showcases building CRUD app with embedded json database
Loki.js and featuring Vuetify. Also it uses Nuxt ServerMiddleware, new Fetch, local modules, hooks and
Express Router for creating a CRUD api.
We use two (anti)patterns for communicating with DB.

VUEX SSR - Through Vuex Store initialised on server
Hybrid - Using Axios on client and db calls on server
CRUD with AsyncData - Through /api middleware doing all the DB CRUD communication
CRUD with new Fetch - Through /api middleware doing all the DB CRUD communication

It's a full rewrite of a previous pull request here
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

@pi0 I have rewritten the example and taken into account your feedback. Please, let me know if anything else

Codecov Report

Merging #7034 into dev will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #7034   +/-   ##
=======================================
  Coverage   62.70%   62.70%
=======================================
  Files          84       84
  Lines        3376     3376
  Branches      920      920
=======================================
  Hits         2117     2117
  Misses       1013     1013
  Partials      246      246

Flag
Coverage Δ

#unittests
62.70% <ø> (ø)

Continue to review full report at Codecov.

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

@pi0 @Atinux do I need to do anything on this? It seems all working, tests fail on unrelated issue. I have other examples to bring in, waiting for this to go in first

Hi @husayt,
I'm so sorry not to update you on this PR. Actually, we internally discussed and the outcome was to only keep minimal examples that demonstrate Nuxt.js features in examples because maintenance here would be much harder to keep them updated thus closing this PR... (some of the current examples are also subject to be externalized)
I would suggest creating a repository for nuxt-loki-starter and making a PR to list in awesome-nuxt#community-examples section.
Also if you wish i can suggest some improvements on codebase when you created repo can make a PR ;)
Best wishes and thanks again for all efforts on this setup. Wish we can move it forward :+1:


Whether custom resource.attributes will be supported

Is your feature request related to a problem? Please describe.
Whether custom resource attributes will be supported. I want to add a custom tag to resource.
Describe the solution you'd like
Providing environment variables makes it possible to inject resource attributes.
Describe alternatives you've considered
provide environment variables

Could I write a PR to support this?


Freezes after some time on Ubuntu 12.04 32 bit

I don't see a pattern here, it just works for some time and then stops updating, tray menu also doesn't work. Log doesn't contain anything useful just state changes. Works fine on my Debian jessie amd64 though.

sounds strange, and I don't know if I can do anything then. I only know the bug that the text on the menu is not updated on Ubuntu which is probably a issue of trayhost. Do you still get state changes after the icon and menu are frozen?

Nope, it stops completely. The process just sits there and doesn't react to anything including Syncthing state changes.


dockerhub tag "latest" useful?

Question
If we just started using dockerhub today, would there be value in continuing to have the latest tag?
Opinion
For applications like this, I see latest as a way for changes to sneak into other people's use of fmriprep without their intention; perhaps causing their pipeline to break or change unexpectedly. It may also become a little more difficult to report the version used in subsequent articles published using fmriprep.
Is this concern overblown and/or are there good uses of the latest tag I'm not seeing for this (and similar) projects?
I wanted to get a quick opinion on this for other projects, since one has to actively avoid creating a latest tag.
Thanks!

I would be +1 to drop it, as it does create confusion, and lead to people not knowing that they're using an old version. Are we able to remove the tag altogether from DockerHub? I think leaving an old latest that never updates will be even more confusing.

we had this same discussion with heudiconv, latest can misrepresent the actual version being used, especially since docker will not refresh unless an explicit docker pull is called.
We experimented with removing the tag altogether and instead recommended users pull direct version tags instead (i.e. heudiconv:0.5.4), but there was enough confusion / push back from the community to warrant bringing it back. What we ended up settling on was similar to this repo's implementation:

versioned tag of each release
latest (pointing to the latest release)
master (current master branch, aka unstable)

Furthermore, we're starting to add an automated version checker to some of our packages to combat this problem of a stale latest. A simple check like this:
https://github.com/neuronets/kwyk/blob/e3f7b8140210da7986b5cc0b56c36dc84143ccdb/kwyk/cli.py#L39-L40
with the option to allow developers to send warnings (and possibly stop running bugged versions down the line)

We experimented with removing the tag altogether and instead recommended users pull direct version tags instead (i.e. heudiconv:0.5.4), but there was enough confusion / push back from the community to warrant bringing it back.

+1 on this. meica only uses versioned tags, and I've had several comments to the effect of "something is broken" because people very much expect there to be a latest tag. I really like the solution @mgxd outlines above !

I believe whoever has admin access to the dockerhub repository can delete the tag. Here is an example from another project I am an admin for.

Thinking out loud, to go this route, we would need to change:

docs/contributing.rst
.circleci/config.yml: in various places
docs/installtion.rst

and any place a tag is not specifically mentioned.
Thanks @mgxd, and I like the solution you've proposed, especially for projects that have used latest for a while. I'm also apprehensive about removing latest for fmriprep, but I (and presumably others) use fmriprep as a "model" for making other projects, I like to think about decisions that could be made at the onset before community momentum takes hold.
Thanks @emdupre, good to know there is precedence for only using versioned tags too!

I think we actually have been doing the version check lately, but it's a bit problematic, because we encourage people not to upgrade unless there's a bug they need fixed, to ensure consistent preprocessing across all subjects.
Given that, it might turn out to be a useful speed bump to not be able to use :latest. To try to cut down on explaining ourselves to angry users, we can try to make a FAQ explaining our reasoning very prominent, and point people to fmriprep-docker, which piggybacks on Python's versioning schemes to choose fully-qualified Docker tags.


How to disable some debug messages?

Hi, I am using ESP32_Display_Panel and I want to disable debug message in serial monitor like:
D (15479) ESP_PanelTouch: Touch panel @0x3c327b20 touched (11, 170, 20)
I cannot find where I can configure this. Thanks!

Hi @zizheng1, you can set ESP_PANEL_ENABLE_LOG to 0 in the file ESP_Panel_Conf.h which should be located in the project folder.


Update RVIZ2 Overlay

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
Updating the current rviz2 autoware overlay to look better and more sleek.

Purpose
Updating the current rviz2 autoware overlay to look better and more sleek.
Possible approaches
Using one island view with a single row instead of 2 separate island views with 2 rows
Definition of done

[x] Overlay is centered
[x] All items in overlay are aligned

Closed with the PRs merged.
Test video with AWSIM Labs 1.0.0: https://www.youtube.com/watch?v=GPow8YPgi1s


DROOLS-733 - splitted and refactored work item operations test

Splitted testWorkItemOperations.
User task shouldn't be handled as work item because in such case it doesn't behave consistently: in database there was left task in ready status even when process instance was completed. That caused issues in other tests.
In this PR user task is completed using startTask/completeTask and work item operation tests are done on second task - Email work item.
Test was splitted to cover both abortWorkItem and completeWorkItem.

merged into master, thanks @sutaakar


ignore target-group-arn changes

PR o'clock
Description
Create an EKS cluster through this project defaults to no ALB target group attachments. While these can be added through setting target_group_arns  in worker_groups, we have another terraform project managing ingress ALBs. This other module attaches ASGs to ALBs via aws_autoscaling_attachment resources.
The problem arises when the module managing ingress ALBs and ASG attachments runs, and then this module is rerun. This module will remove the ASG attachments created by the other module.
Adding 'target_group_arns' to 'ignore_changes' in the worker lifecycle config fixes this problem.
Checklist

[x] terraform fmt and terraform validate both work from the root and examples/eks_test_fixture directories (look in CI for an example)
[ ] Tests for the changes have been added and passing (for bug fixes/features)
[ ] Test results are pasted in this PR (in lieu of CI)
[ ] Docs have been updated using terraform-docs per README.md instructions
[ ] I've added my change to CHANGELOG.md
[x] Any breaking changes are highlighted above

Could this change affect other people who are using target_group_arns for whatever reason?
@brandoconnor I think wrote the TF ALB module so I'll defer to him.

incorporated feedback into another approach, sidestepping this issue. closing and cancelling pr

@max-rocket-internet target_group_arns is not configurable for the workers ASG, so since it's a value that can only be configured outside of this module it should be ignored.
Your comment here: https://github.com/terraform-aws-modules/terraform-aws-eks/issues/219#issuecomment-447765926 is not possible since it's not a variable that's consumed here: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/workers.tf#L1
My use case for this is that my kubernetes ingress controller manages the target group & ELB, therefore running an update will clobber this. Even if target_group_arns was configurable in the workers ASG I would assume for many who use kubernetes service resources of type LoadBalancer or like me is managed via a Kubernetes controller this will be a blocker.
Please let me know if I've made an incorrect assumption above 😄but as far as i can tell this should be safe to make for everyone and essential for those of us who's target groups are managed in K8s.

Hey @grahamar!
But is in the configuration, it's here?
So if this PR was merged, then someone who wanted to change the target_group_arns for one or more of their worker_groups, then it wouldn't work.
Am I misunderstanding something here?

My use case for this is that my kubernetes ingress controller manages the target group & ELB, therefore running an update will clobber this

Understood but are you sure that's the case?

I would assume for many who use kubernetes service resources of type LoadBalancer

This will just create a new ELB, associated it with subnets that have the correct tags and add all cluster nodes to the ELB. Nothing to do with the ASG AFAIK.

🤦♂no idea how I missed it in the configuration! Thanks, that at least is a workaround.
Again my apologies it's just the official AWS ALB controller not the AWS kubernetes default provider so you're right about services of type LoadBalancer
I'll manually hard code my target groups for now until https://github.com/hashicorp/terraform/issues/3116 is fixed. Thanks @max-rocket-internet !

No worries at all!
But still, I'm curious about this

If you are using the ALB controller, the controller will create the ALB and do the association with the ASG itself, right?
In that scenario, does TF undo that association next time it is run?

I'm using https://github.com/zalando-incubator/kube-ingress-aws-controller which also does the ASG association, but have used the AWS ALB controller previously.
Correct. Running terraform removed the association as my config has nothing specified for target_group_arns since it's managed by K8s. This only started since I updated the module from 1.7.0.

I see.
Hopefully in the next release of Terraform we can have interpolations in lifecycle rules.
Or perhaps there is more people in your situation and it would warrant merging this PR making other users update target_group_arns manually.


Update Core wording

Some small updates to clarify the definition of .NET Core.
I'm writing a blog post at the same time, so aligning the two.

nit: Unix should be either with a capital U or the trademarked version UNIX


check27: nothing reported when cloudtrail does not exist

$ aws cloudtrail describe-trails --profile xyz --region us-east-1
{
"trailList": []
}
$ aws cloudtrail describe-trails --profile xys --region us-east-1 --query 'trailList[].[Name,KmsKeyId]' --output text
$
I believe the while loop is exiting before the if/else conditions can check $trail and $key:
$AWSCLI cloudtrail describe-trails --query 'trailList[].[Name,KmsKeyId]' --output text $PROFILE_OPT --region $REGION | while read trail key; do
if [[ "$trail" ]] ; then
if [[ "$key" != "None" ]] ; then
textPass "KMS key found for $trail"
else
textFail "Encryption is not enabled in your CloudTrail trail $trail (KMS key not found)!"
fi
else
textFail "CloudTrail bucket doesn't exist!"
fi
done
Could be resolved by adding after check for null after done that flags as a fail or if you prefer an info
done
if [[ -z "$trail" ]] ; then
textFail "No CloudTrail to encrypt"
fi
}

https://github.com/toniblyx/prowler/issues/704


Set [plugins."io.containerd.grpc.v1.cri".registry].config_path by default

What is the problem you're trying to solve
I'm trying to add a new private registry (with a self-signed CA) to an existing Kubernetes cluster, where I may not have ssh access (but I do have cluster-admin).
Describe the solution you'd like
When using docker, something like the following suffices to add a selfsigned CA:
echo "${PEM_ENCODED_CERT}" > /etc/docker/certs.d/${REGISTRY_NAME}/ca.crt

According the containerd documentation, loading registry certificates after startup requires the following key to be set in config.toml:
[plugins."io.containerd.grpc.v1.cri".registry]
   config_path = "/etc/containerd/certs.d"

Adding this entry isn't sufficient, however, because you also need to restart containerd. Users end up with solutions like this:
http://hypernephelist.com/2021/03/23/kubernetes-containerd-certificate.html
Note that this solution is debian (update-ca-certificates) / systemd (systemctl) specific, and actually modifies the entire set of trust roots for the host, rather than modifying the config.toml programatically (because that seems dangerous)
It would be much cleaner if [plugins."io.containerd.grpc.v1.cri".registry].config_path defaulted to either:

"/etc/containerd/certs.d"
"/etc/containerd/certs.d:/etc/docker/certs.d"

My preference would be for 2, because it would allow scripts that worked with Docker to also work with containerd, but would still prefer certs in /etc/containerd if present.
Additional context
No response

cc @adisky

This is not defaulted because it is a new option which is replacing older options.
We could see if the older options are set and set a default if they are not, maybe?
Alternatively, depending on your situation, ask your k8s provider to set a default value for new nodes.

Would it be reasonable to default it if older options are not set? I'd be happy to do a PR proposal if that would make it easier.
I'm trying to write up provider-independent directions and tutorials for an on-cluster or local build chain, so I'm hoping for a default that would work across providers. 😁

Would it be reasonable to default it if older options are not set? I'd be happy to do a PR proposal if that would make it easier.

That seems reasonable to me.

Discussion in #6488 includes "We could probably wait for 2.0 for this (should be release after 1.7)." from @cpuguy83
Can this issue be removed from milestone 1.7?

Removing from the v2.0 milestone as staled


Vickel: Watch chemxpert(?!.com)

Vickel requests the watch of the watch_keyword chemxpert(?!\.com). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

chemxpert(?!\.com) has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Attach elements to DOM with event listeners

Version
2.6.10
Steps to reproduce
This is more of a support request to be honest but I'm pretty sure to not be the first one having this issue. Sorry for the fake reproduction link.
We are running our acceptance tests using selenium and we have random failures on some tests.
What we are doing is basically waiting for a button to appear (vue to draw it), and then we click on it.
After spending a lot of time, what  it seems happening is the following:

Vue draws a component on the DOM (but did not make in time to attach events yet).
Selenium detects the element and clicks on it
Nothing happens, the event listener on that button is not triggered since vue did not make in time to attach the event listener.

Adding a small delay (50ms as example) fixes the issue.
What is expected?
When vue draws a component, event listeners are already registered
What is actually happening?
It seems that takes some time for event listeners to be registered

Is there some parameter to tweak vue and to not attach the nodes to the dom without registering event handlers?

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.

My 50 cents: I believe this totally belongs here as I face the same issue and it's easily reproducible by adding a link with a v-on:click event handler in a component: event is not handled right after component is displayed, only after an unwanted and annoying delay, which is not the expected behavior.
So either it is a bug report because it could be considered Vue doesn't behave as expected, or attaching events before actually rendering the component is actually a feature request.


Hexabin/Square styles don't work on old viz with infowindows migrated to builder

STR:

Create Map in old editor
Add datasets with points
Add click and hover infowindows
Open viz in builder
Apply style with aggregation (hexabins, squares)

An error ir shown where the Maps API can't find an interactivity column. The problem is worked around by reapplying infowindow (popup) styles in the builder.
log.js:27 Request to Maps API failed: Postgis Plugin: ERROR:  column "hu_site_limit" does not exist
LINE 1: ... 3.37241e-06), 6.74483e-06)) AS geom,"cartodb_id","hu_site_l...
                                                             ^

in executeQuery Full sql was: 'SELECT ST_AsBinary(ST_Simplify(ST_SnapToGrid("the_geom_webmercator", 3.37241e-06), 6.74483e-06)) AS geom,"cartodb_id","hu_site_limit" FROM (WITH hgrid AS (SELECT CDB_RectangleGrid ( ST_Expand(ST_MakeEnvelope(-20037508.3,20037508.29613578,-20037508.29613578,20037508.3,3857), greatest(0.000134897,0.000134897) * 100), greatest(0.000134897,0.000134897) * 100, greatest(0.000134897,0.000134897) * 100) as cell) SELECT hgrid.cell as the_geom_webmercator, count(1) as points_count, count(1)/power( 100 * CDB_XYZ_Resolution(CDB_ZoomFromScale(0.520686)), 2 ) as points_density, 1 as cartodb_id FROM hgrid, (SELECT * FROM fl_insurance_sample) i where ST_Intersects(i.the_geom_webmercator, hgrid.cell) GROUP BY hgrid.cell) as cdbq LIMIT 65535'

infowindows should be disabled when style is hexagons or rectangles (torque based ones as well)
cc @matallo

doing so in https://github.com/CartoDB/cartodb/blob/master/lib/assets/javascripts/cartodb3/data/layer-definition-model.js#L94-L101
shall we do the same with tooltips?

Already disabled tooltip and infowindow fields when a style aggregated or animated is enabled.
Branch: issue-7857


181 prevent reservations from spanning timeslots

Related to Issue #
What changes has been added?
Backend
Timeslot and Reservation had many to many relationship
I changed that Timeslot can have multiple Reservations, but Reservation can have only one Timeslot.
Frontend
Expected Behaviour

Tehty myös #172


polysemy-plugin explodes when dealing with VDQs

See the discussion here: https://github.com/isovector/polysemy/issues/45#issuecomment-492427836
Unfortunately, this issue will come up whenever there is a phantom effect parameter :|

Some reading on VDQs

I wonder if this is fixed by #62?

It is


fix #2736 - remove explicit check for list as a return value in make_response

This PR addresses an issue introduced in #2256 which breaks a custom response class that supports returning lists from view functions.
A list is not an expected response value and is not intended to be handled by make_response. I'm unsure why it made it's way into this instance check, but there are no consequences to removing it, based on what I can see in the tests & related code.

OK, your fork is probably going to be messed up after this, since you made the PR from your master and I just force pushed it to look like 1.0-maintenance. You can probably fix it by force pushing origin/master and origin/1.0-maintenance to your fork once this is merged, or just delete and fork again.


Add Carthage support by sharing Pods' build scheme to git

Minor changes - Carthage need to have available build scheme to build the library.
Great lib, keep up the good job! :)

Awesome, much appreciated. This was on my list of things to get around to - thanks!


Enhancement: New Tab In Toolbox 'Modcharts'

Please check for duplicates or similar issues before creating this issue.
What is your suggestion, and why should it be implemented?

A New tab called modcharts.
Basicly you will create a modchart and it will ask 'Do you want to do notes or player'
Notes will be like wiggling and stuff
Player will be either bf, gf, or dad and can float up and down and stuff
This can be saved as either a .json file, .lua file or a .hx file.
Kade and / or Psych scripts can be supported with this as well
hope yall understand it im bad at explaining

I understand this, this would be great to add in.

won't be added in
there's too much that can conflict with it, such as middlescroll, downscroll, gui size and such.
adding support for these would overcomplicate the ui, making it unusable.
also its better to code those in


Made folder name looks simpler

I will put more useful features soon.

@antronic can you show a screenshot of your feature?


Drain a lot of power running on Macbook Pro 2017 with touch bar of High Sierra system

The Energy impact while playing music is 60-100, and the avg energy impact is 27.06, I don't know what's wrong? And the hotkey bundling is not configurable, that whatever I type won't be reflected on the hotkey blank.

OS:
Issue Descriptions:
Steps to Reproduce:

Same here. I don't even have the touchbar macbook. Just 2015 model with High Sierra. It was the same when I had Sierra.

Performance and energy usage concerns have been raised before but have been found every time to be a result of GPM itself rather than GPMDP logic.  Some users have reported success with a combination of minimizing the window and staying on the home page of GPM but 🤷♂ I've never really had energy issues so I can't speak to those workarounds


Mobile - Bug Cannot set property 'status' of undefined

Describe the bug
Bug Cannot set property 'status' of undefined
Device: IOS < 16.4

Version test:
Android: https://www.diawi.com/qrcode/link/DQgm27
IOS: https://www.diawi.com/qrcode/link/SpTVTE
Device test: IP 11 (17.5), IP 7+(15.8), S20 FE 5G
Validation passed in case

Install/Upgrade version
IOS < 16.4: Transactions proceed normally on networks that have not updated the runtime(Re-check all validate)
Android, IOS > 16.4: Keep the logic unchanged, not affected


6.1.2 didn't bump the shared library name

Throughout many of the previous releases the shared library contained the release version, for example 6.1.1 builds lib/libcint.so.6.1.1
However, 6.1.2 discontinued this trend, and 6.1.2 still builds lib/libcint.so.6.1.1
Is this intended?

This is just a tag to align to the release in qcint library. There is no substantial changes than the previous version.


Missing file in "'models/instructions_processed_LP“

Thank you for your great works! I have met an error when run the main.py, as follows:
No such file or directory: 'models/instructions_processed_LP/instruction2_params_test_unseen_noappended.p'

When I copy those .p file from FILM project and run the code, I get KeyError, which mean those missing files are not from FILM project. Can you share those file? Thank you very much!

Sorry about that, it is completely my bad.
I just pushed the files, so please check


docs: update python docs link in readme.md

Description
Update python docs link in README.md to new website
Related Issue(s)
closes #1898
Documentation

@roeap Approve of micro change? :-)

@thomasfrederikhoeck thanks for fixing this. do you mind fixing the link in the table below was well?

LGTM 👍

@thomasfrederikhoeck thanks for fixing this. do you mind fixing the link in the table below was well?

Done @roeap  :-)


fix(e2e): remove flaky garbage check from e2e

Signed-off-by: AmitKumarDas<EMAIL_ADDRESS>

:tada: This PR is included in version 1.11.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Allow setting "today" to any date for query "explain" to work with

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
While using the "Explain" feature for querying it would be handy to set the current date as any date to see how the query would work at a specific point in time.
For example, this following query for getting task for the current week:
(due after this week) AND (due before sunday)
is difficult to forecast depending on the current day it is explained.
✔ Solution
I would add a date after "explain" to set the today date for the explaining as following:
not done
(due after this week) AND (due before sunday)
explain 2022-12-01

❓ Alternatives
Changing my computer date 🙁
📝 Additional Context
No response

Good idea 👍


RN2903 using freqPlan TTN_FP_AS920_923 fails

I am attempting to use The Things Uno with the Asian 920-923 range, however
I am getting the errors:
...
Data Rate: 3
RX Delay 1: 1000
RX Delay 2: 2000
-- JOIN
Model: RN2903
Version: 0.9.8
...
Sending: mac save
Sending: mac set adr off
Sending: mac set rx2 2 923200000
Response is not OK: invalid_param
Sending: mac set ch dcycle 0 799
Response is not OK: invalid_param
Sending: mac set ch dcycle 1 799
Response is not OK: invalid_param
Sending: mac set ch dcycle 2 799
Response is not OK: invalid_param
Sending: mac set ch freq 2 922000000
Response is not OK: invalid_param
Sending: mac set ch drrange 2 0 5
Response is not OK: invalid_param
Sending: mac set ch status 2 on
Sending: mac set ch dcycle 3 799
Response is not OK: invalid_param
Sending: mac set ch freq 3 922200000
Response is not OK: invalid_param
Sending: mac set ch drrange 3 0 5
Response is not OK: invalid_param
Sending: mac set ch status 3 on
Sending: mac set ch dcycle 4 799
Response is not OK: invalid_param
Sending: mac set ch freq 4 922400000
Response is not OK: invalid_param
Sending: mac set ch drrange 4 0 5
Response is not OK: invalid_param
Sending: mac set ch status 4 on
Sending: mac set ch dcycle 5 799
Response is not OK: invalid_param
Sending: mac set ch freq 5 922600000
Response is not OK: invalid_param
Sending: mac set ch drrange 5 0 5
Response is not OK: invalid_param
Sending: mac set ch status 5 on
Sending: mac set ch dcycle 6 799
Response is not OK: invalid_param
Sending: mac set ch freq 6 922800000
Response is not OK: invalid_param
Sending: mac set ch drrange 6 0 5
Response is not OK: invalid_param
Sending: mac set ch status 6 on
Sending: mac set ch dcycle 7 799
Response is not OK: invalid_param
Sending: mac set ch freq 7 923000000
Response is not OK: invalid_param
Sending: mac set ch drrange 7 0 5
Response is not OK: invalid_param
Sending: mac set ch status 7 on
Sending: mac set pwridx 1
Response is not OK: invalid_param
Sending: mac set retx 7
Sending: mac set dr 5
Response is not OK: invalid_param

on startup,
Here is my code that I simply ran from the example. I have omitted my keys:
#include <TheThingsNetwork.h>
#include <TheThingsMessage.h>

// Set your AppEUI and AppKey
const char *appEui = "secret";
const char *appKey = "very secret";

#define loraSerial Serial1
#define debugSerial Serial

// Replace REPLACE_ME with TTN_FP_EU868 or TTN_FP_US915 or TTN_FP_AS920_923
#define freqPlan TTN_FP_AS920_923

TheThingsNetwork ttn(loraSerial, debugSerial, freqPlan);

devicedata_t data = api_DeviceData_init_default;

void setup()
{
  loraSerial.begin(57600);
  debugSerial.begin(115200);

  // Wait a maximum of 10s for Serial Monitor
  while (!debugSerial && millis() < 10000)
    ;

  debugSerial.println("-- STATUS");
  ttn.showStatus();

  debugSerial.println("-- JOIN");
  ttn.join(appEui, appKey);

  // Select what fields to include in the encoded message
  data.has_motion = true;
  data.has_water = false;
  data.has_temperature_celcius = true;
  data.has_temperature_fahrenheit = true;
  data.has_humidity = true;
}

void loop()
{
  debugSerial.println("-- LOOP");

  // Read the sensors
  data.motion = true;

  // Encode the selected fields of the struct as bytes
  byte *buffer;
  size_t size;
  TheThingsMessage::encodeDeviceData(&data, &buffer, &size);

  ttn.sendBytes(buffer, size);

  delay(10000);
}

From the source, it seems correct, any one have any idea why I am getting this error?
The firmware version is: Version: 0.9.8
I just tested another chip:
Model: RN2903
Version: 1.0.5
Same issue :(

Can you try with the passthrough example, and issuing commands directly as specified in the data sheet?

@kevin192291 I'm having very similar issues as you. I wrote my sketch and debug serial output on the TTN forum here.
I suspect the supported frequency plans are hard-coded into the chip because changing the freqPlan TTN_FP_AS920_923
to TTN_FP_US915 seemed to solve all the invalid_param errors...
I bought my chip here and am not really that surprised since it did say "North-America" in the description...
Will be trying this one out and will let you know.

@RCPilot1604 It has been quite some time since I was trying to use this chip, I have found there are alternatives. After talking to Microchip directly, they told me that they have never released an official fw for as923. And, to expand on this, this chip lacks a Telec certification, so if you want it to work for hobby purposes, you will be okay, but it is a no-go for building actual products.
I have been using RAK chips lately, these are just as, if not more easy to work with. RAK3172 This is certified, it supports LoRaWAN Class A, B, and C, and is a serial connection just like the RN2903.


README

README
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN a Prework project repository,
WHEN I view the README for the repository,
THEN I see a professional README that provides information on the project and how to use it

I've updated the contents of the READ.ME file to display Licensing, Instructions and Credits for users to refer to


Fix CodeQL build

Closing in favor of smaller fixes/changes that are more localized to area which will make it easier to merge later.


refactor: organize manager providers by version

Issue or need
v1 and v2 provider manager APIs are in the same directory. It's not explicit just by looking at dir structure which API is used, which is old...

Proposed changes
Organize by version directories. Extract common outside

Quick reminders

🤝 I will follow Code of Conduct
✅ No existing pull request already does almost same changes
👁 Contributing docs are something I've taken a look at
📝 Commit messages convention has been followed
💬 TSDoc comments have been added or updated indicating API visibility if API surface has changed.
🧪 Tests have been added if needed. For instance, if adding new features or fixing a bug. Or removed if removing features.
⚙ API Report has been updated if API surface is altered.

#948  👈
main

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

Join @davidlj95 and the rest of your teammates on  Graphite


Added operator, unit test and REST test for GetDeviceServiceById

Fixes #1690.
Signed-off-by: Brandon Forster<EMAIL_ADDRESS>

Codecov Report

Merging #1691 into master will increase coverage by 0.2%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #1691     +/-   ##
=========================================
+ Coverage   34.67%   34.88%   +0.2%
=========================================
  Files         139      139
  Lines       11770    11780     +10
=========================================
+ Hits         4081     4109     +28
+ Misses       7488     7470     -18
  Partials      201      201

Impacted Files
Coverage Δ

internal/core/metadata/rest_deviceservice.go
25.72% <100%> (+3.25%)
:arrow_up:

...rnal/core/metadata/operators/device_service/get.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


TVPaint: Fix plugin for TVPaint 11.7

Brief description
Plugin for TVPaint was modified to work in TVPaint 11.7.
Description
TVPaint 11.7 is more sensitive about when the connection should be created and caused crashes. The connection is created in function defined by SDK where the init logic should happen.
Testing notes:

Run TVPaint 11.7 (it will probably ask to copy plugin file)
All should work

Task: OP-4197

Task linked: OP-4197 TVPaint 11.7 integration issues


Use existing string resource for settings screen toolbar title

... instead of hardcoded "Settings" string.
I noticed this while working on the french translation (PR #75) 😃

Thanks!


Built-In Math Functionality

Lots of useful (i.e. GLSL math) functions should be included, such as clamping. Also commonly-used functions like proper random integer generators.

Fixed inside the Anchor Collision Fix commit


Fix crash on Driver Properties -> Registry -> Jump To Key

wsprintf on registry key (https://github.com/hfiref0x/WinObjEx64/blame/9245836619bae5baa1a7da3edf5ade03dda1d659/Source/WinObjEx64/props/propDriver.c#L433) was causing memory corruption which led to crash or instability of the program because of incorrect allocation of registry key path string

Good catch. Now I need to figure out why there two mostly identical on purpose constants.


[Issue]: Failed to create final entities while using local vLLM Server and local Embedding Model.

Do you need to file an issue?

[x] I have searched the existing issues and this bug is not already filed.
[ ] My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
[x] I believe this is a legitimate bug, not just a question. If this is a question, please use the Discussions area.

Describe the issue
GraphRAG failed to create final entities, while using local LLM and local Embedding Model.
embedding model is a fschat server, and LLM is Qwen2.5-7B, run by a vllm OpenAI server.
Steps to reproduce

execute the command : "python -m graphrag.index --root ./"

Error occured.

GraphRAG Config Used

encoding_model: cl100k_base
skip_workflows: []
llm:
  api_key: ${GRAPHRAG_API_KEY}
  type: openai_chat # or azure_openai_chat
  model: /home/sylu/workspace/lyh/Qwen/Qwen2_5-7B-Instruct/
  model_supports_json: true # recommended if this is available for your model.
  # max_tokens: 4000
  # request_timeout: 180.0
  api_base: http://<IP_ADDRESS>:8000/v1
  # api_version: 2024-02-15-preview
  # organization: <organization_id>
  # deployment_name: <azure_model_deployment_name>
  # tokens_per_minute: 150_000 # set a leaky bucket throttle
  # requests_per_minute: 10_000 # set a leaky bucket throttle
  # max_retries: 10
  # max_retry_wait: 10.0
  # sleep_on_rate_limit_recommendation: true # whether to sleep when azure suggests wait-times
  # concurrent_requests: 25 # the number of parallel inflight requests that may be made
  # temperature: 0 # temperature for sampling
  # top_p: 1 # top-p sampling
  # n: 1 # Number of completions to generate

parallelization:
  stagger: 0.3
  # num_threads: 50 # the number of threads to use for parallel processing

async_mode: threaded # or asyncio

embeddings:
  ## parallelization: override the global parallelization settings for embeddings
  async_mode: threaded # or asyncio
  # target: required # or all
  # batch_size: 16 # the number of documents to send in a single request
  # batch_max_tokens: 8191 # the maximum number of tokens to send in a single request
  llm:
    api_key: ${GRAPHRAG_API_KEY}
    type: openai_embedding # or azure_openai_embedding
    model: gpt-4
    api_base: http://<IP_ADDRESS>:8200/v1
    # api_version: 2024-02-15-preview
    # organization: <organization_id>
    # deployment_name: <azure_model_deployment_name>
    # tokens_per_minute: 150_000 # set a leaky bucket throttle
    # requests_per_minute: 10_000 # set a leaky bucket throttle
    # max_retries: 10
    # max_retry_wait: 10.0
    # sleep_on_rate_limit_recommendation: true # whether to sleep when azure suggests wait-times
    # concurrent_requests: 25 # the number of parallel inflight requests that may be made

chunks:
  size: 1200
  overlap: 100
  group_by_columns: [id] # by default, we don't allow chunks to cross documents

input:
  type: file # or blob
  file_type: text # or csv
  base_dir: "input"
  file_encoding: utf-8
  file_pattern: ".*\\.txt$"

cache:
  type: file # or blob
  base_dir: "cache"
  # connection_string: <azure_blob_storage_connection_string>
  # container_name: <azure_blob_storage_container_name>

storage:
  type: file # or blob
  base_dir: "output"
  # connection_string: <azure_blob_storage_connection_string>
  # container_name: <azure_blob_storage_container_name>

reporting:
  type: file # or console, blob
  base_dir: "output"
  # connection_string: <azure_blob_storage_connection_string>
  # container_name: <azure_blob_storage_container_name>

entity_extraction:
  ## strategy: fully override the entity extraction strategy.
  ##   type: one of graph_intelligence, graph_intelligence_json and nltk
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  prompt: "prompts/entity_extraction.txt"
  entity_types: [organization,person,geo,event]
  max_gleanings: 1

summarize_descriptions:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  prompt: "prompts/summarize_descriptions.txt"
  max_length: 500

claim_extraction:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  # enabled: true
  prompt: "prompts/claim_extraction.txt"
  description: "Any claims or facts that could be relevant to information discovery."
  max_gleanings: 1

community_reports:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  prompt: "prompts/community_report.txt"
  max_length: 2000
  max_input_length: 8000

cluster_graph:
  max_cluster_size: 10

embed_graph:
  enabled: false # if true, will generate node2vec embeddings for nodes
  # num_walks: 10
  # walk_length: 40
  # window_size: 2
  # iterations: 3
  # random_seed: 597832

umap:
  enabled: false # if true, will generate UMAP embeddings for nodes

snapshots:
  graphml: true
  raw_entities: false
  top_level_nodes: false

local_search:
  # text_unit_prop: 0.5
  # community_prop: 0.1
  # conversation_history_max_turns: 5
  # top_k_mapped_entities: 10
  # top_k_relationships: 10
  # llm_temperature: 0 # temperature for sampling
  # llm_top_p: 1 # top-p sampling
  # llm_n: 1 # Number of completions to generate
  # max_tokens: 12000

global_search:
  # llm_temperature: 0 # temperature for sampling
  # llm_top_p: 1 # top-p sampling
  # llm_n: 1 # Number of completions to generate
  # max_tokens: 12000
  # data_max_tokens: 12000
  # map_max_tokens: 1000
  # reduce_max_tokens: 2000
  # concurrency: 32

Logs and screenshots
indexing-engine.log
Additional Information

GraphRAG Version: 0.3.6
Operating System: Linux
Python Version: 3.11
Related Issues:

You may need to use a model with larger parameters, I tried llama3.1-70b and it didn't work, finally using deepseek-chat worked!

well, it might work while using API key, however, we must use local LLM and embedding model due to some restrictions from the project we're now working on.

well, it might work while using API key, however, we must use local LLM and embedding model due to some restrictions from the project we're now working on.

Is this problem solved?

well, it might work while using API key, however, we must use local LLM and embedding model due to some restrictions from the project we're now working on.

I failed using qwen2.5 14B


Missing colon in --seq2 example in Wiki

https://github.com/mcveanlab/mccortex/wiki/Workflow-Examples#read-threading
The example for thread with --seq2 R1 R2 should be --seq2 R1:R2.

Fixed, thanks Torsten.


Helm deployment instructions are incorrect

Portus is NOT located on the incubator repository at this time.  And yet the instructions on the
deploy instructions reference it more than once.
https://github.com/kubic-project/caasp-services/tree/master/contrib/helm-charts/portus
https://kubernetes-charts-incubator.storage.googleapis.com/

Thanks,  I saw the PR and read through all of it... seems like just some last hurdles (tests) to pass to get it bumped into stable (per: https://github.com/kubernetes/charts/pull/2766).
Don't know how stale that is?  Is it still worth fighting the good fight on?

Thanks,  I saw the PR and read through all of it... seems like just some last hurdles (tests) to pass to get it bumped into stable (per: https://github.com/kubernetes/charts/pull/2766).
Don't know how stale that is?  Is it still worth fighting the good fight on?

Yes that is the one. I was not involved with the project at the time so I can't speak to why it was not merged initially... but I do have to admit, that PR been open for quite a while! It looks like the most recent issue is just from requirements.lock?
With that said the 2 charts have diverged quite a bit, and the incubator PR chart is still based on openSUSE/portus:2.2 though 2.3 has had some significant updates.


Can we use table and image button?

We want to include two buttons

Table: by clicking the table button user should be able to choose rows and columns of table, and finally this should insert a table.
Image: User should be able to upload image, and application should upload the image in base64 format.

Please let us know if it is possible if yes how we can achieve this?

@vinusorout that's not what you have out of the box, but you always can create your own plugin and do content manipulation


Adding conda unpack option to docker build / entrypoint

Trying to remove as much logging as possible but allowing for development / debugging. I believe this should remove all the unpack logs from the pod start

Hey @dtpryce ,
It seems tests are failing due to an issue that has now been fixed in master. Would you be able to rebase?

Hey @dtpryce ,
It seems tests are failing due to an issue that has now been fixed in master. Would you be able to rebase?

I think I have done it ... if this fails, I can make a new fork and re-request :D

Nice one! Looks all it's green! :rocket:


Remove TinyMCE extension

I feel bad, because I helped to create it, but I don't think there's any point to including the TinyMCE extension any more:
https://www.mediawiki.org/wiki/Extension:TinyMCE
VisualEditor works quite a bit better, I think, both on its own and within forms - and TinyMCE seems to be basically unmaintained at this point.

I support removing this.


DesignOverview and SteelEffectiveLengths tests corrected

All unit tests corrected to allign with the latest GM 26.7.2022 (6.02.0022.348.24e69e77d6e).
Unit tests: 154 passed, 7 skipped in 174.59s

Do you test it in latest GM @dogukankaratas?

Do you test it in latest GM @dogukankaratas?

Yes. grandmaster_b156162_24e69e77d6e


[RAFD-1561] Fix for change in hdfs-site.xml in Hadoop 3.1 for JCEKS path

"dfs.nameservices" is used to fetch cluster name instead of dfs.internal.nameservices

what is this change about?

@miraj-godha-guavus Sir, JCEKS path is<EMAIL_ADDRESS>From HDP 3.1, the cluster name in hdfs-site.xml is found as dfs.nameservices instead of dfs.internal.nameservices.
So I have just changed that in our code, particularly in parseConf.java


Refactor UNet and MultiResUNet models

The current API has a very explicit implementation for both models, as more requirements are needed for different types of training loops, a more general implementation is needed that can take the following parameters

Unet:

[x] Type of regularization, L_1, L_2 or L1_L2.
[x] Value of the regularization parameter

MultiResUnet:

[ ] Type of regularization, L_1, L_2 or L1_L2.
[ ] Value of the regularization parameter

UNet is done in #19 .

Refactoring and generalizing MultiResUnet is up to you @gmagannaDevelop :+1:


Provide choice of BIOS to use (EFI/Legacy)

As a UTM user I would like to be able to configure a q35 VM that uses EFI BIOS instead of legacy BIOS.
AFAIK UTM already ships with more BIOS files than are available through the system configuration. So this would only require a configuration option.

I'd like to add another vote for this feature: UEFI is already the standard by which modern operating systems boot, and Windows 10 in particular depends on it for some pretty important functionality (secure boot first and foremost, as well as several features in Windows Defender).
Please add this: it may even help with the blue screen issue plaguing recent Windows 10 versions on q35).

I'd like to add another vote for this feature: UEFI is already the standard by which modern operating systems boot, and Windows 10 in particular depends on it for some pretty important functionality (secure boot first and foremost, as well as several features in Windows Defender).
Please add this: it may even help with the blue screen issue plaguing recent Windows 10 versions on q35).

As a workaround until this is implemented, you can make UTM use an UEFI for your VM manually:

Download the EFI BIOS (archive includes both x86_64 and ARM 64 / AARCH64 versions however the latter is already included with UTM)
Open the Drives Configuration for the VM that should use EFI BIOS.
Import the EFI BIOS file into the Drives list (file OVMF_CODE-utmlogo-RELEASE.fd is for x86_64 system and file QEMU-AARCH64_EFI-utmlogo-RELEASE.fd is for AARCH64 system; Note that UTM includes this EFI BIOS for AARCH64 already).
Set drive properties:
4a. For x86_64 system, change the Interface to PC System Flash (pflash), and leave Type as Disk Image.
4b. For AARCH64 system, change the Type to BIOS.

UTM will recognize that a BIOS / PFLASH drive has been added and use it instead of the default BIOS.

Also, according to #2628 I think an EFI BIOS may be able to provide the default resolutions of the Host MAC on the target OS?


Source analyzer doesn't restart if it gets killed.

It looks like a source analyzer process is spawned for each project in the current solution.  I used the Task Manager to kill one of these analyzers, and as a result, the python editor stopped doing some things it usually does, and I didn't see another source analyzer appearing to replace it.
What the editor doesn't do, that I noticed, was (1) update color codings for class names (it's fine for Python keywords), (2) find syntax errors (in my case, I removed the trailing quote from a string, and no squigglies appeared nor anything in the Error List window.
So I think what you would want to do is monitor those spawned processes for any notification that they died and restore them if so.
The reason I did this experiment was on account of my previous issue post (#3298) regarding the source analyzer process growing in memory usage.  I wanted to see what would happen if it grew to the point of running out of memory, so I just manually killed the process instead.

Analyzer restart done in https://github.com/Microsoft/PTVS/pull/5045


Adding the ThermoML dataset

I'm happy to have a go at adding the ThermoML archives as a dataset, if this is useful.
Already mentioned on Discord by @marcosfelt, including the useful link to thermopyl and @marcosfelt's updated fork.

In terms of licensing, it looks like the ThermoML archive has recently been "FAIRified" and can be downloaded in bulk at http://doi.org/10.18434/mds2-2422


Revert "[MM-35703] Maintain scroll position in channel when opening reply message permalinks"

Reverts mattermost/mattermost-webapp#10723
See discussion here: https://github.com/mattermost/mattermost-webapp/pull/10723#discussion_r1000063233, easier to just revert the commit than try and re add everything
Reverting: Maintain scroll position in channel when opening reply message permalinks

cc // @kyeongsoosoo

/cherry-pick cloud

Cherry pick is scheduled.


Allow for conditional prompting

Cookiecutter version: latest
Template project url:
Python version:
Operating System:

Description:
Depending on the answer to one of the prompts, show or hide other related prompts.

Hi @milin! 👋
Thank you for your suggestion.
Please see #848

Thanks @hackebrot. Looks like skipIf is what I am looking for. Any idea if its still looking for sponsorship or if its being worked on. Wouldn't mind jumping in, if some extra help is needed.


Consider using or providing an alternative license

Some countries (i.e. Germany) do not accept The Unlicense as a valid license. Would it be possible to provide an alternative license alongside it, or worst case scenario change the license to something like CC0?

I mainly just liked the simple text of the unlicence, but the point of the public domain idea: I don't really care about the project or what anyone does with it until the next time I start a minecraft server and have a use for it when playing with friends across the world :)
I guess I could add a duplicate licence if it really matters to people :)
I should also add a readme telling others what this program actually does: It retransmits packets before the other side has even received them in order to keep the stream flowing, it trades bandwidth for latency (in the cases where it's useful probably by about 3 or 4 times)

Done.


Memory efficient triplet sampling

The current (random) triplet sampling requires a lot of memory if a reasonable number of objects is used.

Allow custom sampling probabilities

Implementation hint:
import numpy as np

def random_query(n_object, n_query, n_col):
    """ Generate random sets of unique integers with Floyd's algorithm.

    This algorithm is both fast and memory efficient such that it scales
    to large scale problems.
    Floyd's sampling algorithm assures unbiased insertion probability
    for randomly generated sets.

    A naive implementation would sample rows from all unique combinations of
    the integers 0 to n_objects-1, causing extensive memory usage by the
    number of combinations (n_objects choose n_col).
    In contrast, the memory and runtime usage of this algorithm is linear
    in the number of rows and columns, and constant in the number of objects.
    ttps://math.stackexchange.com/q/178690

    References
    ----------
    Bentley, J., & Floyd, B.(1987). Programming pearls: A sample of brilliance.
    Communications of the ACM, 30(9), 754–757. https://doi.org/10.1145/30401.315746
    """
    assert n_object >= n_col
    query = np.zeros((n_query, n_col), dtype=np.uint)
    rng = np.random.default_rng()

    query[:, 0] = rng.integers(0, n_object - n_col + 1, n_query)
    for i in range(1, n_col):
        j = n_object - n_col + i
        t = rng.integers(0, j + 1, n_query)
        t_is_new = (query[:, :i] != t.reshape(-1, 1)).all(axis=1)
        query[:, i] = np.where(t_is_new, t, j)

    # Floyd's algorithm does not guarantee equal probability
    # in the order of insertion, so we randomize the column order.
    random_column_order = rng.random(query.shape).argsort(axis=1)
    return np.take_along_axis(query, random_column_order, axis=1)

o = 6
n = 5_000_000
c = 6
a = random_query(o, n, c)
print(a.shape)
print(a[:5])
print(np.bincount(a.ravel().astype(int), minlength=o), c*n//o)
for c in range(a.shape[1]):
    print(np.bincount(a[:, c].astype(int), minlength=o))


How does it differ from PRQL?

This seems very similar to the effort done by the PRQL team.
How does this project differ and have you considered joining forces instead of creating a new SQL competitor.

Hi, it's kind of mentioned in the blog:
https://blog.runreveal.com/introducing-pql/
The goal is to provide something similar to the piped languages like Splunk, Sumo, etc that security engineers generally use. The syntax of PRQL doesn't really fit that need and I don't really forsee security engineers adopting PRQL any time soon, so it motivated the creation of pql.

Going to close this issue since it's just a question.


update version firefox/gecko

Please, update version for firefox/gecko driver or get the LATEST version  automatically

Upgraded Firefox to 102 and Geckdriver to 0.31.0.


[BUG] prevent creation of tables with no names

Describe the bug
Create table method can create a table without any name
Expected behavior
table-name field cannot be empty when clicking on Create table button.
Screenshots

@Shivansh-yadav13  i would like to contribute on this issue.

@Shivansh-yadav13  i am not able to to run "go run main.go"  command , could u help me setting up.

@RachitGarg-12 what does the terminal says? and are you following the setup guide https://github.com/Shivansh-yadav13/SQLite-UI#-set-up-project-locally


Big data example

The Big data example takes to long to. Chrome and Firefox showing "to long working javascript" errors.
Any ideas how to speed this up? I need 1000+ rows in the android chrome.

Also with around 800 rows, it would be nice to not block the whole interface while creating the treegrid.

I will think what I can do

when you render the tree, it seems like you render it line by line instead of navigating the tree, am I right? Because it leads to a lot of recursive processing.

I've got a view with a bit more than 800 rows, and with this change, it reduces from 40s to 5s. Maybe it needs more test but is seems to work fine for me. And maybe it works only with bootstrap as I'm using the "hidden" class. If not using bootstrap, it would need something to handle the visibility but you shouldn't use hide and show in a loop. Let Jquery handle the loop by applying hide and show to a collection.

it is not working for me...i have around 400 to 500 rows it is taking around 40sec..please help me out..

you've tried my change?

I have the same problem, i have ~1500 rows to show and the treegrid and treeGrid collapse parts are too long  and they freeze my browser :
treeGrid: 15861.654ms
collapse: 10863.867ms

have you tried my code change suggestion ?

For your change @YMA-MDL I think we should set that like this :
if ($this.treegrid('isOneOfParentsCollapsed')) {
     $this.addClass('hide');
} else {
     $this.removeClass('hide');
}

Because the show class in Bootstrap show elements as block. And the gain is very small (1s)

Strange, it made a very significant change for me. This issue was that the code was iterating on important DOM manipulation where now it's just a class update and Jquery does the rest.

but that part does not solve the tree-grid initialization. Only the collapse part. I think  the modificzation to optimize the code is to rewrittent all of this without jQuery but with pure javascript and frasgments. In my code, if i try to manipulate a large amount of data, i increase the loadTime and reduce this by 10 only with fragment and javascript native DOM elements

@YMA-MDL - for what it's worth, integration with this script http://nexts.github.io/Clusterize.js/ would likely solve the big data pains and increase your scripts outer limits by hundreds of thousands of records. I might investigate this myself once I have some time.

Good Luck, not sure if it will allow to save nested state. Like you browse a structure, and getting back to it later, the same branches are deployd.

@YMA-MDL, did you implemented Clusterize? If yes, can you share some sample code, please?

No I did not, but I may come across the same need soon.

Thank you. I try but it does not worked :(

Also tried to combine the Clusterize, but initializing still stays slow with about 1500 rows. Commit from @YMA-MDL (thanks by the way ;-) ) was applied to the code.
Attached the performance record i did with Chrome Version 61.0.3163.100 (64-bit) for future analyses:


Power toys to control screen brightness.

Is there any way for the brightness toggle to be incorporated in the next update?That would be really convenient .
.

@shubamjyotidas
the tracker for this feature is https://github.com/microsoft/PowerToys/issues/1052
Closing as duplicate.
Thanks.


Add web builds.

The important part is posted below. Archiving for now.
      - name: Set up Emscripten latest
        uses: mymindstorm/setup-emsdk@v11
        with:
          version: ${{env.EM_VERSION}}
          actions-cache-folder: ${{env.EM_CACHE_FOLDER}}

      - name: Verify Emscripten setup
        run: |
          emcc -v
```


Unwrenched machines have no collisions

You can unwrench a machine and push it through a wall.

This seems to be an oversight of the layer/mask definitions, not anything to do with wrenching/unwrenching machines. It's only noticeable on vending machines and computers when unwrenched because they don't collide with walls otherwise.
Specifically, vending machines and computers have no mask. Walls also have no mask. This means they don't collide, even though they're on the same layer.


Load global symbols

This is the basic PR to make use of ign-plugin in other libraries.
This comment in this other PR https://github.com/ignitionrobotics/ign-sensors/pull/38#issuecomment-678123125 explains what is going on. Basically some libraries pre-load some symbols of other libraries (for example libignition-gazebo4-sensors-system.so pre-load some ign-sensor symbols) and when you need to load some of the ign-sensor libraries you can't access these symbols because it was load previously.
Using RTLD_GLOBAL we can access theses symbols but we should filter in all the libraries and look for the right one.
Signed-off-by: ahcorde<EMAIL_ADDRESS>

Just as a curiosity, which version of dlfcn-win32 is used in the CI ? vcpkg has 1.1.1 while conda-forge has 1.2.0, and the 1.2.0 had some changes w.r.t. 1.1.1 related also to the RTLD_GLOBAL flag (see https://github.com/dlfcn-win32/dlfcn-win32/pull/44).

Thinking a little bit more about this I think this should target main. There are no changes in the API but the behaviour of the library has changed and this will required to modify the existing code that makes use of ign-plugin1. What do you think @mjcarroll and @chapulina ?

Thinking a little bit more about this I think this should target main. There are no changes in the API but the behaviour of the library has changed and this will required to modify the existing code that makes use of ign-plugin1. What do you think @mjcarroll and @chapulina ?

I agree that main probably makes more sense.  @chapulina are we bumping plugin for Edifice?

I agree that main probably makes more sense.  @chapulina are we bumping plugin for Edifice?

are we bumping plugin for Edifice?

If you peeps are certain that this change is needed to get ign-sensors to work, I'm ok bumping ign-plugin in Edifice. Every downstream library is already being bumped, so this shouldn't have a large impact.

are we bumping plugin for Edifice?

If you peeps are certain that this change is needed to get ign-sensors to work, I'm ok bumping ign-plugin in Edifice. Every downstream library is already being bumped, so this shouldn't have a large impact.

Retargeted to main.

Retargeted to main.

friendly ping @mjcarroll and @chapulina

friendly ping @mjcarroll and @chapulina

Just as a curiosity, which version of dlfcn-win32 is used in the CI ?

That's a question for @j-rivero

Just as a curiosity, which version of dlfcn-win32 is used in the CI ?

That's a question for @j-rivero

Just as a curiosity, which version of dlfcn-win32 is used in the CI ?

That's a question for @j-rivero

Uhm. We are using tarball in the ign-plugin build, I can not find the version on the code. The date of the tarball is Nov 2017, probably 1.1.1?

I talked to @mxgrey and he had the nice suggestion of adding a flag to enable the new behaviour. If we do this, we may not need to bump the version and only enable the new behaviour for the libraries that need it.
Then I started looking more closely and noticed that the dlopen call being changed is inside ForgetLibrary. I hadn't noticed this detail before. I think it explains the changes in the tests. But now I'm confused about how this helps ign-sensors. Can you elaborate a bit more on why this is needed, @ahcorde ?

@chapulina
Adding a flag required to keep the two functionalities at the same time but the idea it's to keep just one way to load libraries (remove the code in ign-common if I remember correctly).
The function dlclose() decrements the reference count on the dynamic library handle. If the reference count drops to zero and no other loaded libraries use symbols in it, then the dynamic library is unloaded. But this is not reliable. Anyhow I'm also using NODELETE to avoid unload something that it's already running. I remember I got some segfault without this .
I not really sure about how this could help the different libraries (ign-sensors, ign-gui, ign-rendering or ign-gazebo). But the idea it's to use ign-plugin which is the library focuses on loading shared libraries. Maybe there is a deeper implementation issue inside ign-plugin and we don't want to move forward with this implemention, because we nned to load all the symbols an filter them in each library.

Just as a curiosity, which version of dlfcn-win32 is used in the CI ?

That's a question for @j-rivero

Uhm. We are using tarball in the ign-plugin build, I can not find the version on the code. The date of the tarball is Nov 2017, probably 1.1.1?

Thanks! I am asking as in the journey to get a reliable working Gazebo with vcpkg-installed dependencies I became the dlfcn-win32 maintainer, even if I am definitively not an expert of Windows shared library interface. However, several users over time contributed quite a lot to the library. In particular in the release 1.2.0 that came out in 2019 (https://github.com/dlfcn-win32/dlfcn-win32/releases/tag/v1.2.0) there have been some works on loading of global symbols (see https://github.com/dlfcn-win32/dlfcn-win32/pull/44). I would expect for everything to work fine for both dlfcn-win32 1.1.1 and 1.2.0, but with this tricky issues problems can always emerge.

Removing beta label, we won't have time to wrap this up before code freeze. Let's retarget at Ignition-F.

This isn't necessary anymore as we solved the ign-sensors needs by removing plugin functionality.


Add sahmyook university Korean name

It's just an additional Korean name
Please review, and if everything looks good, merge please
Thank you :)

@bhyunnie Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


README typos and fixes

conda env update --name happypose --file environment_noversion.yml -> environment_noversion.yaml
git lfs install should be run before git lfs pull
conda env update --name happypose --file environment_full.yml -> conda/environment_full.yml
Suggestion: use mamba instead of conda for updating the environment -> much faster
Suggestion: propose a script to run to check if installation was successful (e.g.
Suggestion: Instructions to download data/model?

Already solve in dev


Chore/migrate published function to drizzle WIP

✨ Codu Pull Request 💻

Pull Request details
Working

Cursor with oldest and newest and top sort
Searching by tag is working (stolen from #860)
removed dependency on drizzle-pagination
denormalised likes into post table to make queries easier and improve performance ref: https://www.wired.com/2015/11/how-instagram-solved-its-justin-bieber-problem/

Any Breaking changes

Yes schema change to post table. Will require a migration. Can work on this next before it deploys to dev but will need schema migration first

Associated Screenshots

None same as before

Summary by CodeRabbit

New Features

Articles now display user details like name, username, and image more reliably.
Added a "likes" feature for articles, allowing articles to be liked, with likes displayed on each article.
Enhanced article sorting and filtering capabilities, including sorting by likes, publish date, and bookmarks.

Bug Fixes

Fixed an issue where articles were not being uniquely identified, by using the article's id as a key in lists.

Refactor

Improved consistency in naming by changing currentUserLikesPost to currentUserBookmarkedPost.
Enhanced post retrieval logic to support more complex queries based on user interactions and article metadata.

Chores

Updated database schema to include a likes field for articles, initializing with a default value to support the new likes feature.

I see the title still has "WIP" is this ready to go?

I see the title still has "WIP" is this ready to go?

Yes forgot to change


Could it used to monitor elasticsearch cluster health like watcher?

Currently i found the rules are based on the index, but there is no built-in index for elasticsearch but some api.
The elastic official monitor tool has this feature.
https://www.elastic.co/guide/en/watcher/current/watch-cluster-status.html#health-add-input

It would be nice to have the option to trigger an alert if a cluster health is not green.


2.2 - hosted 3bot - no available pool

tried to deploy a hosted 3bot

@waleedhammam @m-motawea Should we convert that to an enduser app? where network, pools are all done behind the user? and what is your estimate if so?

i just realized that, but that couldnt be, because i built 3 pools already before. could it be that sometims it doesnt detect my pools?

@waleedhammam @m-motawea Should we convert that to an enduser app? where network, pools are all done behind the user? and what is your estimate if so?

Seems doable, may take a couple of hours for extra testing AFAIK

i just realized that, but that couldnt be, because i built 3 pools already before. could it be that sometims it doesnt detect my pools?

Could you provide us with these Pools ids please ?

281, 286, 385
now it shows again

281, 286, 385
now it shows again

yes It just minute or two to charge/complete the payment.
from what i see is 281 is empty. you will be able to use 286 and 385

ok thanks.
so lets say i create a pool also on staging marketplace-testnet2.grid.tf, would it also show on testner production marketplace-testnet.grid.tf,?

ok thanks.
so lets say i create a pool also on staging marketplace-testnet2.grid.tf, would it also show on testner production marketplace-testnet.grid.tf,?

Pools created on marketplace-testnet2.grid.tf "are owned by the marketplace identity" that's completely different than  marketplace-testnet.grid.tf because it's owned by another marketplace identity. Both shouldn't be confused or "shared"