Fix mistakenly changed MongoDB version

Thanks to @ivanbakel for reporting the error in https://github.com/bigchaindb/bigchaindb/commit/3fec83d2e2390de61d1b7ca1f05dc10c7f9b8cbd#commitcomment-22947951

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1641   +/-   ##
=======================================
  Coverage   98.46%   98.46%
=======================================
  Files          59       59
  Lines        2862     2862
=======================================
  Hits         2818     2818
  Misses         44       44


Posts can be flagged and owners can appeal

A user can flag inappropriate of messages. Conditions of hiding messages should be implemented. For example, the message will be hidden if at least be flagged by 2 individuals.
The user of the flagged message can appeal. The appeal should be juried by the community, maybe via some kind of governance?

Premise
I fully support this feature, but I think there are some challenges that need to be thought through very deeply first.
Difficulties
Suppose we implement this feature as you mentioned, so:

users can mark posts as inappropriate
after a defined number of flags (let's say 2 to be coherent with your example) the posts will be hidden

Who should manage this situations
The first question that comes into my mind is: who should the owner of the flagged post speak to?
We have two different options to keep things decentralized.
1. The handling is done through a decentralized governance made of all the community.
This can unfortunately lead to two different bad situations (that can even verify together):

The overall managing of such situation can take too long.
If we take example from the Cosmos Hub, it takes up to a month to have a simple proposal sorted out properly. Even the post in the example is of high importance, things should be cleared as soon as possible.

The community can ban users that do not think like the majority of them.
This could lead to politics-related censorship as well as other form of censorship that emerges when a group of people with a certain mindset has the power to vote on whether a group of people with a different mindset can express their opinion or not.

2. An elected group of people
I personally like best the idea in which there is an elected group of people (elected from the whole community via a specific governance proposal) that rotates a couple of times per year, and which handles such situations. In this case what they would do it:

Visualize the message
Express an individual vote on whether the post should be hidden or not.

This would allow for a faster management of such situations, but could lead to an easier corruption of such people from the user that posted the flagged message.
How to prevent double posting?
When the community has flagged a post as inappropriate, and it is being review or has already been hidden, how do we prevent the same person from posting the same message?
What we could do is "jailing" him until the message has been reviewed. By jailing I mean not allowing him to post any other message. I, however, find this option really brutal and should not be applied.
On the other hand, we could implement a sort of exponential jail time for flagged posts that result being classified as inappropriate. For example:

Bob posts a message, which is flagged as inappropriate. This leads to him being jailed for 1 hour.
Bob while the first post was under review had posted another one flagged and later classified as inappropriate. This leads his jail time to increase to 1 day and 1 hour.
After 25 hours, Bob is unjailed and posts another message flagged and classified inappropriate. This leads to him being jailed for 1 week.

We can then go up exponentially from 1 hour to 1 day, 1 week, 1 moth, etc.
This will surely lead to posters avoiding posting new messages that can be easily flagged as inappropriate.
The problem witht hi

Event-based solution
Problems with the solution proposed above
During the latest weekly call on Tuesday 3 March 2020, some problems have been raised about creating a universal reporting system that is 100% on-chain and governed by the Desmos users or by the chain government.
The problems can be synthesized with the following key points.
Censorship attacks
Having a government-based way of handling reports might lead to censorship attacks.
Suppose for example that a user is targeted from a group of users (we might think as racists, diverging politic ideals, etc). In order to completely censor that user, the attacking group can report any post multiple times, leading a first block of that posts. If they also manage to have a great governance power (they possess a lot of tokens or corrupt the right people) they can also have the posts permanently hidden from the chain.
Of course, they will not be deleted from the chain state, but they could be made very much difficult to be read.
Different applications Terms of Services
Desmos is thought to be the protocol that allows to create any kind of social networks. That being said, we should consider what would happen in the case of two completely different applications being developed on top of it.
Suppose, for example, that one day we end up with PornHub as well as Facebook developing their social networks on top of Desmos.
If we have the same reporting system shared among the two social networks, this might cause some problems. As Desmos-based applications will share the users too, this means that every Facebook user could report the content present inside PornHub's social network. Of course, they could report them for nudity or other porn-related motivations, but PornHub does not have the same ToS of Facebook and such contents should (obviously) be visualized inside its social network.
For this reason, a shared reporting system might be problematic to handle in the case of multiple, very different, applications build on top of Desmos.
Event-based solution
In order to solve both of the problems depicted above, what we could do is implement an event-based system. This should work as follows.
Every time a post is reported, the following happens:

The report is saved on-chain.
A post_reported event is emitted.
Desmos-based applications will listen to such event and act accordingly.

In order to make the system as much generic as possible, the following features should be implemented.
NOTE. The best thing should be to implement all those features inside a new report module.
Types
A Report type should be created, containing the following data:
type Report struct {
  Type    String         `json:"type"`     // Identifies the type of the report
  Message String         `json:"message"`  // Contains the user message
  User    sdk.AccAddress `json:"user"`     // Identifies the reporting user
}

To be consistent across different applications, we should define a list of supported Types (probably inside the genesis) so that custom applications can have a list of them.
Messages
A new MsgReportPost should be created, having the following structure:
type MsgReportPost struct {
  PostID types.PostID `json:"post_id"`  // Identifies the reported post
  Report types.Report `json:"report"`   // Contains the report data
}

Keeper
The Keeper should have a method that allows to store a report for a post as well as one to read all the reports of a post.
func (k Keeper) SaveReport(ctx sdk.Context, postID types.PostID, report types.Report) {}

func (k Keeper) GetPostReports(ctx sdk.Context, postID types.PostID) []types.Report {}

Storage
The storage should be pretty simply, allowing to store a list of Report associated to a specific PostID:
PostID -> []Report

Conclusion
The event-based solution allows for both an on-chain storage of all the reports that are created from users as well as a custom handling of such reports from different applications.
Combined with Djuno this is in my opinion the best way we should pursue related to the posts reporting implementation.

I'm wondering if emitting an event is enough for this. What if the event subscription is lost at some point? Would the application still knows a specific post is being reported and needed to be handled? For the case of having Facebook and PornHub, as long as we separate the posts and flags in their own subspaces, would that confusion happen?

What if the event subscription is lost at some point? Would the application still knows a specific post is being reported and needed to be handled?

The reports will be stored on-chain as well, so that should do it as it can get them later and perform a diff.

For the case of having Facebook and PornHub, as long as we separate the posts and flags in their own subspaces, would that confusion happen?

Right, I didn't think about subspaces. Users can still do censorship attacks reporting them cross-app tho :thinking:

@RiccardoM Hm... actually there is no contradiction with your design. The spec you are proposing is good enough to implement the idea. We don't need the appeal feature at this moment. We only need to let users flag the posts. Whether displaying or not all depends on the apps themselves based on their own rules. The most basic info we can have would be number of reports and storage association is simple enough.
In the future when we have more values regarding user accounts like reputations, we may also list them out along with the flags for the applications to consider if those values should be taken into account. That will be another story.
For the cross-app censorship attack, it may be solvable if we move this with the usage of smart contract. The state update has to be done by the smart contract and it depends on who can trigger the smart contract.

What do you guys think about implementing this into v0.7.0?

@bragaz Yes, this might be good for v0.7.0. Please when implementing this do not consider the following point:

To be consistent across different applications, we should define a list of supported Types (probably inside the genesis) so that custom applications can have a list of them.

I really think that leaving application the freedom of supporting their own types might be better and easier to manage in the future.

@bragaz agree to have it in v0.7.0. Please also study the feasibilities on adapting smart contract system in this aspect.


Update part1-completion.md (bad link)

A quick, update: the link https://github.com/fixie-ai/ai-jsx/tree/main/packages/tutorial in the document https://docs.ai-jsx.com/tutorials/aijsxTutorials/part1-completion is bad

This was pointed to the wrong link. Should have been pointed at https://github.com/fixie-ai/ai-jsx/blob/main/packages/tutorial/README.md to fix the broken link to the tutorial (which is now fixed).


provide firebase configuration

Can you provide firebase security rules and any other configuration needed for migrating to another firebase account? I'm getting an error when trying to create an account after changing firebase url.
Thanks for this great example!

Check out the readme!


[Question]SSL

I get the following error when I translate.
httpcore._exceptions.ConnectError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1002)

Resolved.


Openthread Sleepy End Device Reboot when parent connection is lost.

I have an openthread set-up with Rpi based Border Router and 2 SED nodes and 1 FTD node.
The set-up is such that, 1 SED is placed near to Border Router so it's always the direct neighbour and child of Border Router and another SED is placed far such that it connects to Border Router with 1 hop via FTD.
Set-up runs perfect for days if all devices are on.
Now when FTD is powered off for 7-8 hours, 2nd SED, which is direct child of FTD, gets rebooted once FTD is powered on again. Sometimes SED also backs off from the network.
My application is build over Nordic's NRF SDK for Thread and Zigbee Version 4.0.0.
Hardware used: nrf52840 SoC
Daemon Version: 0.08.00d (/345bf7d; Jun 27 2019 17:02:59)
NCP Version: "OPENTHREAD/20191113-00092-g8a1992e2; NRF52840; Apr  6 2020 22:33:55"

@bhumikaajain , thanks for raising this issue.
Can you indicate how you determined that the SED is "rebooting"? Does the device have any watchdog enabled by default?
/cc/ @LuDuda

Yes, we have watchdog enabled by default.

Yes, we have watchdog enabled by default.

@bhumikaajain , would it be possible for you to hook up a debugger and determine what is causing the watchdog reset?

It is not feasible as the reset time is not fixed and I am using my SEDs as sensor nodes, remotely placed.

It is not feasible as the reset time is not fixed and I am using my SEDs as sensor nodes, remotely placed.

@bhumikaajain , unfortunately, we have not yet experienced any similar behavior. If it is possible to replicate your setup, a debugger will help us identify the issue. If you disable the watchdog, spin-loops and asserts are easy to identify.

Closing stale issue. Please reopen if there are further updates.


Debug Output Wrapping with Short Output

via https://github.com/MetroRobots/ros_command/pull/20#issuecomment-1448097217

I looked into it a bit more and noticed it's only a problem with roslaunch, rosrun works fine.
Here's a minimal example on my machine:
https://github.com/v4hn/ros_command_test_minimal_output

I found an initial fix, but I'm still trying to figure out what's going on.
diff --git a/src/ros_command/command_lib.py b/src/ros_command/command_lib.py
index 5f2729f..3fa6f3c 100644
--- a/src/ros_command/command_lib.py
+++ b/src/ros_command/command_lib.py
@@ -9,7 +9,7 @@ import click

 async def _read_stream(stream, callback, encoding='UTF8'):
     while True:
-        line = await stream.readline()
+        line = await stream.read(4)
         if line:
             callback(line.decode(encoding))
         else:


[FEATURE]

Is this a unique feature?

[X] I have checked "open" AND "closed" issues and this is not a duplicate

Is your feature request related to a problem/unavailable functionality? Please describe.
pic
How to customize this part of ui
Proposed Solution
how?
Screenshots
No response
Do you want to work on this issue?
No
If "yes" to the above, please explain how you would technically implement this (issue will not be assigned if this is skipped)
No response

Thank you for reporting issue.
Do you mean fully custom rendering or just adding some styles to every item?

Added classnames for this in v4.3.0
Check example and docs:
https://yoopta-editor.vercel.app/examples/withCustomStyles#dc2f645d-48dc-467c-aae3-086b5913e3a2


Undocumented Vim version dependency?

Running on Ubuntu 14.04.3 and Vim 7.4, I get the following error when writing a .go file:
Error detected while processing function <SNR>81_write_triggered_update_tags[3]..<SNR>81_update_tags[31]..gutentags#pwd:
line    4:
E118: Too many arguments for function: getcwd
E15: Invalid expression: haslocaldir() ? getcwd(0, 0) : getcwd()
Error detected while processing function <SNR>81_write_triggered_update_tags[3]..<SNR>81_update_tags[41]..gutentags#chdir:
line    6:
E344: Can't find directory "0" in cdpath
E472: Command failed
Error detected while processing function <SNR>81_write_triggered_update_tags:
line    3:
E170: Missing :endfor

The tags were also not found by Vim.
Upgrading to Vim 8.0, fixes the problem and tags now work. I assume there is an undocumented Vim version dependency?

@hkupty FYI

Sorry for taking long to answer.. I'll take a look at it.
Cheers

Ah yes it looks like we need to add a check for Patch 7.4.1126, which is when getcwd got the new arguments.

@ludovicchabant sure.. I'll add that

I think the merging of PR https://github.com/ludovicchabant/vim-gutentags/pull/117 fixed this?


Rebased cmake-staging branch (post PR#10)

This is the cmake-staging branch rebased on the recent bitcoin/master one with squashed "FIXUP" commits.
Rebase phase: cmake-staging/pr11-init --> cmake-staging/pr11-rebased. Fixed conflicts with the following PRs:

https://github.com/bitcoin/bitcoin/pull/25781
https://github.com/bitcoin/bitcoin/pull/26177
https://github.com/bitcoin/bitcoin/pull/27118
https://github.com/bitcoin/bitcoin/pull/27150
https://github.com/bitcoin/bitcoin/pull/27238

Squash phase: cmake-staging/pr11-rebased --> cmake-staging/pr11-squashed. A diff must be zero :)
Expected to work:
Cross-compiling for Windows:
make -C depends HOST=x86_64-w64-mingw32 NO_QT=1 NO_WALLET=1 NO_ZMQ=1 NO_UPNP=1 NO_NATPMP=1 NO_USDT=1
cmake -S . -B build -DCMAKE_TOOLCHAIN_FILE=depends/x86_64-w64-mingw32/share/toolchain.cmake
cmake --build build

Cross-compiling for macOS, arm64:
make -C depends HOST=arm64-apple-darwin NO_QT=1 NO_WALLET=1 NO_ZMQ=1 NO_UPNP=1 NO_NATPMP=1 NO_USDT=1
cmake -S . -B build -DCMAKE_TOOLCHAIN_FILE=depends/arm64-apple-darwin/share/toolchain.cmake
cmake --build build

Cross-compiling with libc++:
$ make -C depends CC=clang CXX="clang++ -stdlib=libc++" NO_QT=1 NO_WALLET=1 NO_ZMQ=1 NO_UPNP=1 NO_NATPMP=1 NO_USDT=1
cmake -S . -B build -DCMAKE_TOOLCHAIN_FILE=depends/x86_64-pc-linux-gnu/share/toolchain.cmake
cmake --build build

Previous linearization PR:

https://github.com/hebasto/bitcoin/pull/8

@vasild @TheCharlatan @theStack @theuni @willcl-ark
Ready for extensive testing :)

Rebased.

Were there any fixups or changes other than the squashing?

Yes. PRs from the PR description introduced changes in the source tree that were accommodated here.

LGTM, I checked that the fixup commit made it to the right place with
diff <(git show 00c44c815cd22c9d924e245bb0e01c34b561a2e3) <(git show 91f28a6a961f962e0408130cbc46d9aa8cc4b84b)

This branch has been force pushed into the https://github.com/hebasto/bitcoin/tree/cmake-staging.
Closing.


Build Production Mode

Built Production Mode got dead code elimination from react-tools extension

Thanks for creating the issue! Would you like to submit a PR ?


Use local IPs for inter-node communication

Using public IPs in Amazon requires the shared security group open to external traffic.
Suggest testing this with the shared security group customizer enabled. If working could update the docs not to require it.
I've tested this with the security groups open to external traffic. If not working with the stock security groups could look at  --api-servers=${KUBERNETES_URL} as a potential cause.

Looks good, have tested on Softlayer.


Container error in AnalyticEngine service setup

We are trying to install CP4D 4.0.9 with the Deployer tool on the existing Openshift environment. After a few hours during the installation, we see that the operators are formed properly on the OC side, but while creating the pods required for the AnalyticEngine, it falls into an error state when it takes the images related to the spark and the installation fails on bastion node's terminal. After deleting the tmp files, we tried again several times, but the problem persists.
I am sharing a picture of the error with the pods below. As far as I guess, there is a problem during the image extraction process via ansible scripts.

**Cloud Environment

OS: OpenShift
Version 4.8
CP4D Version: 4.0.9

@ugurozker My best guess is that the node running the pod is running out of space. This is not a "deployer" issue. What is the infrastructure you're running this on?

Thanks for your return @fketelaars,
You can find my nodes resources and bastion node log messages at the following screenshots.

I need to add more details, i removed analytical engine in catalog and try to install again and this time same error caused by wml at the bastion node terminal sc.

@ugurozker I will ping you, I need the logs to understand better what the issue is.

log.txt
cartridge.txt
Dear @fketelaars,
You can find all the logs I have obtained from bastion node attached. I'm waiting for your good news

I have not been able to replay this issue and provisioning of AE consistently works. Closing.


Document TRAM [aggregate] entry method attribute

Original issue: https://charm.cs.illinois.edu/redmine/issues/1225

No body.

Original date: 2017-04-04 20:02:12

Setting priority higher because these are easy to fix things that act as paper-cuts to users

Original date: 2017-04-10 16:59:51

This is already documented in the libraries manual, where all of TRAM is documented. Is that sufficient, or do we want to transfer some/all of that documentation over to the main manual?

Original date: 2017-04-10 17:04:17

That bit of documention can be reduced, since the header and module linkage is now automatic. The [aggregate] entry method API should be documented in the main Charm++ manual.

Original date: 2017-04-12 00:38:23

Implemented in ~~https://charm.cs.illinois.edu/gerrit/#/c/2388/~~ https://github.com/UIUC-PPL/charm/commit/61bd4f95b5aa8110b71f3847a94b5aa65ad2f82b


Busted install link?

yes, template vms do not have networking by default.
i am also not sure how a template vm got involved in the build process here.
i suggest we close this for now and reopen if the problem persists and more details become avail.

Yeah, if you can't ping github from your build AppVM using the regular sys-firewall then the problem certainly isn't with mirage-firewall.

Yeah,  github ping was no problem, it was the particular recommended location within github that wasn't responding. It's been a while now and I couldn't find any info so I let that one rest. I think such an install in my opinion is for high experienced qubes users. I managed to set up bionic desktop, ubuntu, and a very isolated windows 10 making it useless without something like the mirage firewall.  I have networked equipment that can't communicate with windows 10 that's why I tried the mirage firewall. Maybe I will try again this June when I have a little extra time, thanks for the pointerSent from my T-Mobile 4G LTE Device
-------- Original message --------From: Thomas Leonard<EMAIL_ADDRESS>Date: 3/22/20  4:31 AM  (GMT-08:00) To: mirage/qubes-mirage-firewall<EMAIL_ADDRESS>Cc: Chris<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [mirage/qubes-mirage-firewall] Busted install link? (#92)
Yeah, if you can't ping github from your build AppVM using the regular sys-firewall then the problem certainly isn't with mirage-firewall.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/mirage/qubes-mirage-firewall/issues/92#issuecomment-602185051",
"url": "https://github.com/mirage/qubes-mirage-firewall/issues/92#issuecomment-602185051",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]


react-flip-move not working with preact-compat

Hi! I'm trying to use react-flip-move with my preact project, and I'm getting an error about not being able to call children.map when I add it.
import {h} from 'preact'
import {Component} from 'preact-compat'
import FlipMove from 'react-flip-move'

export default class Test extends Component {
  render() {
    return (
      <FlipMove
      typeName="div"
      enterAnimation="fade"
      leaveAnimation="fade"
      >
      <div key="hi"/>
      </FlipMove>
    )
  }
}

TypeError: props.children.map is not a function
    at new FlipMove (https://localhost:8000/js/***.js:2653:32)
    at createComponent (https://localhost:8000/js/vendor.js:7095:20)
    at renderComponent (https://localhost:8000/js/vendor.js:7154:55)
    at setComponentProps (https://localhost:8000/js/vendor.js:7127:103)
    at buildComponentFromVNode (https://localhost:8000/js/vendor.js:7214:13)
    at idiff (https://localhost:8000/js/vendor.js:7017:57)
...

Thanks!

Hi there!  I'm actually not sure why react-flip-move is trying to use props.children.map, since that should be undefined in React as well.  However, adding an empty Text node seems to fix the issue.  Here is a JSFiddle reproduction that you can see working with the empty text node added:
https://jsfiddle.net/developit/3cqbq0n7/

Interesting! Thanks for looking into it!


jQueryUI wrong version?

Hello!
Is AdminLTE shipping an outdated version of jQueryUI in plugins/jQueryUI?
For example, index.html uses the following js:

http://code.jquery.com/ui/1.11.2/jquery-ui.min.js

but AdminLTE has a local jQueryUI plugin copy using version 1.10.3.
My suggestions:
1: Remove plugins/jQueryUI from the project; or
2: Update the plugins/jQueryUI version, to match the index.html sample.
Thanks.

Hi,
The lack of use of jQueryUI in AdminLTE makes me forget updating it with every release.
I have decided to use bower in the future to avoid this issue from happening again. For now, I will update it manually.

Fixed in master.


Should probably be jasmine-wrap.

Seeing this issue - https://github.com/facebook/jest/issues/3155 made me remember that the internal test runner is actually Jasmine.  Looks like jest will be test runner agnostic in the future, and people will need different -wrap libs depending on which they use.

I think until just his test run or agnostic, jest–wrap will still be needed.  It's beneficial to have the appropriate peer dependency requirements and test coverage in the meantime.
Certainly creating jasmine-wrap is a good idea also.

Closing this out as Jest has cut out jasmine completely as of version 20.


Add DateTimeOffset to Oracle type map

as TIMESTAMP(4) WITH TIME ZONE

@vgrigoriu Thanks for the pr !


font-variation-settings not supported?

Is it just me or is font-variation-settings not supported?

font-variation-settings isn't in normalize.css either.


Not work methods of WpPost instance

constructor(
    private wpService: WpService,
    private route: ActivatedRoute,
    private location: Location
  ) {}
  /** Post Response */
  post: WpPost;
  /** Post Endpoint */
  endpoint = WpEndpoint.posts;
  /** Model */
  model;
  //
  postEmbed;
  ngOnInit(){
    let slug = this.route.snapshot.params['slug'];
    console.log(slug);
    let args = {
      _embed: true,
      slug: slug
    };
    this.model = this.wpService.collection().posts();
    this.model.get(args).subscribe( (res: ModelResponse) => {
      if( res.error ) {
        console.log(res.error);
      }
      else {
        this.post = new WpPost( res.data[0] );
        console.log(this.post);
        this.postEmbed = {
          // in component class that works
          featuredImage: this.post.featuredImageUrl('full')
        };
      }
    } );

  }

but in template not work
<img [src]="post.featuredImageUrl('full')">

@Maden-maxi what error are you getting?

I assume you fixed your problem, feel free to reopen.
closing this for now..

Yes, I solved this problem.
Sorry that I did not reply for a while


start of N67 support

Hello @AndrewAnnex! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file get_spice.py:

Line 277:1: E302 expected 2 blank lines, found 1

In the file src/spiceypy/tests/test_wrapper.py: No issues found.

the one failing test is from pointing to an n66 shared library, so it's working! just gotta decide which thing to merge first, possibly this one as I will still need to version bump spiceypy for conda-forge things.


Pressing invalid key adds ng-invalid class

When pressing invalid key on the keyboard it does add ng-invalid class to the input, pressing invalid key again removes ng-invalid class
<input type="text" placeholder="First Name" ng-model="vm.profile.first_name" ng-pattern="/^$|[a-zA-Z-\-\ ']+$/" ng-pattern-restrict />

Thank you very much!
I think this may be related to #17, but I haven't done investigation on any of these. I'll take a look at these later.

I was not able to reproduce this problem with Angular 1.4.7. I tested manually with Chrome 45 and Firefox 40. Then I ran an automatic test and all browsers seemed to not have this problem.
Here's the test I built to check this:
<form name="testForm">
  Text 1:
  <input type="text" id="textbox1" name="textbox1" ng-pattern="/^[abc]*$/" ng-pattern-restrict ng-model="modelValue" />

textbox.valid: {{testForm.textbox1.$valid}}

</form>

it('should leave input always in a valid state', function() {
  //valid input
  page.setText('abc');
  expect(page.getValidStatusPromise()).toBe("true"); // gets the contets of #ngValid

  //invalid input
  page.setText('def');
  expect(page.getValidStatusPromise()).toBe("true"); // gets the contets of #ngValid
});

While on the test I checked for the $valid attribute of the input, I was not able to see at any point that the ng-invalid was added to the input or to the form at all.
Do you have any other detail I could use to reproduce the problem?

PS: If you want to work off of the test I built, I had started it in the fix-validation-issues branch.

Hi! I haven't heard back from you and I haven't yet found a way to reproduce this problem.
I'll close this ticket for now, and if you or somebody else comes up with a way of reproducing it, feel free to let me know and I'll reopen it or we can just start another discussion.
In the meantime I'll add these new tests to the master branch so that they're ready for everyone to start the troubleshooting.


Remove version: Principle.Lusun version 2.2.8

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://releases.lusun.com/lusun-2.2.8-win-x64.exe
Response Error: The remote server returned an error: (403) Forbidden.
(Automated message - build 912)

Hi @Exorcism0666,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 887.)

URL: https://releases.lusun.com/lusun-2.2.8-win-x64.exe
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 887)

For moderators or/and anyone else

[!Caution]
As a result of several personal problems I've had over the last few months + my final exams coming up very soon, I'm currently unable to look at my GitHub notifications every day and maintain my executions correctly.
If you detect a certain problem on a certain pul request:

Either you can close the pull request directly without mentioning me.
Or you can send me a message on X (Twitter): @Exorcism0666

Thank you for your understanding, and I'm sorry if some pull requests can't be approved due to the situation I'm in.

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

[!IMPORTANT]
This package should NOT be removed! The installer URL is still valid.
21:44:38 D:\...\winget-pkgs  [master ≡] 1ms pwsh> winget download -e Principle.Lusun -v 2.2.8
已找到 芦笋 [Principle.Lusun] 版本 2.2.8
此应用程序由其所有者授权给你。
Microsoft 对第三方程序包概不负责，也不向第三方程序包授予任何许可证。
正在下载 https://releases.lusun.com/lusun-2.2.8-win-x64.exe
  ██████████████████████████████  79.9 MB / 79.9 MB
已成功验证安装程序哈希
已下载安装程序: D:\Download\Aria2\Principle.Lusun_2.2.8\芦笋_2.2.8_Machine_X64_nullsoft_zh-CN.exe
21:45:12 D:\...\winget-pkgs  [master ≡] 13.864s pwsh>

URL: https://releases.lusun.com/lusun-2.2.8-win-x64.exe
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 887)

Response status code does not indicate success: 403 (Forbidden).

Is it related to request headers? Does the server (provided by Tengine) block winget.exe by detecting it's specific headers?

403 Forbidden
You don't have permission to access the URL on this server.
Denied by region_block

Enable "global mode" of my Clash for Windows and switch to a Singapore proxy node. Issue successfully reproduced.

It seems requests from China (including Mainland, Hongkong SAR., Macau SAR. and Taiwan Province) are only permitted to access the Tengine server.

URL: https://releases.lusun.com/lusun-2.2.8-win-x64.exe
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 887)

URL: https://releases.lusun.com/lusun-2.2.8-win-x64.exe
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 887)

URL: https://releases.lusun.com/lusun-2.2.8-win-x64.exe
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 887)


Add toml and yaml formatters to pre-commit

Context: https://github.com/iterative/dvclive/pull/773#discussion_r1480220196
Format was not enforced for TOML and YAML files.

Could you also apply the changes to the pyproject.toml template? Otherwise I assume it will have to be reformatted each time once the project is generated.

That is a very good point, @dberenbaum!
I formatted the files and tried it on my computer. Everything is well formatted at repo initialization.


[Epic] Path to adopting React Server Components in Hydrogen

This issue documents our path to adopting the official React Server Components implementation in Hydrogen.
I've documented Vite-specific steps in an official Vite discussion here: https://github.com/vitejs/vite/discussions/4591
Why is this important? We want to eliminate our custom "fork" of Server Component logic as quickly as possible in order to adopt the official RSC version when it's ready and avoid hairy bugs.
Phase 0: Today

Date
Status

Today
Done

We've reverse-engineered a version of Server Components that works in Vite and with React 18 alpha.
This works for the most part and has unblocked devs and merchants from building on Hydrogen using patterns of Server Components. There are limitations and bugs that we'll need to advertise and support workarounds for early beta Hydrogen users.
Read more about how this phase came to be.
Phase 1: Build a Vite version of React Server Components

Date
Status

August 2021
In progress

The official Server Components demo is built with the React experimental build using react-server-dom-webpack. This package is Webpack-specific in some parts, like how client components are proxied on the server, and how client components are dynamically loaded in the browser.
However, lots of the code is not Webpack-specific! This means we can create a Vite (or even "rollup") version of the React package with relative ease.
This phase involves creating react-server-dom-vite in the official React repo. We'll open a PR when we're ready and work with the core team to update, merge, and change certain parts as needed. Since it's an experimental build, we aren't on the hook for maintaining backwards compat or supporting existing users.
Phase 2: Build a demo with Vite + React Server Components

Date
Status

September 2021
Not started

We should create a version of the official server components demo to prove out the functionality we built in the previous phase.
This can live in a Shopify repo, or in Facebook/React's org if they want.
Here's a starter repo: https://github.com/shopify/server-components-demo-vite
This will serve as a reference to both Shopify and to others hoping to implement React Server Components in Vite/Rollup.
Phase 3: Test Vite version of React Server Components with Hydrogen

Date
Status

September 2021
Not started

Once we have react-server-dom-vite in the React repo, we should swap out our reverse-engineered implementation with the real version.
There are two caveats with this:

SSR won't work (yet)
There might be critical bugs

I'm particularly interested in the latter part, because we'll need to fix these bugs and blockers before RSC goes live. This is an opportunity to contribute fixes upstream in React and to the third-party packages we use.
For example: we might notice that React Router stops working. Or the way we're using Context in Hydrogen doesn't work in RSC.
Phase 4: Adopt the official implementation in Hydrogen

Date
Status

December 2021*
Not started

This could happen a number of ways:

Allow a dev to opt-in to the official RSC implementation using a feature flag in shopify.config.js. They might have to install the experimental version of React, which we could prompt from them.
React ships RSC in React 18, meaning we can ship this even more easily as a feature flag in Hydrogen
React ships RSC as part of React 19. We simply adopt it in Hydrogen, make changes as necessary, and cut a major release.

Most of these depend on the official React roadmap and how quickly RSC gets shipped into stable.
* Very, very optimistic estimate for our Hydrogen roadmap. It could be much longer.

Closed in favor of a new roadmap: https://github.com/Shopify/hydrogen/discussions/287


BigQueryVectorStore assumes we are now creating the vector store

If we already have an existing VectorStore in BigQuery and we just want to connect to it and fetch documents from it, the _create_search_query method crashes when using filters, since self.table_schema is not initialized, due to these lines:
if filter:
            filter_expressions = []
            for column, value in filter.items():
                if self.table_schema[column] in ["INTEGER", "FLOAT"]:  # type: ignore[index]
                    filter_expressions.append(f"base.{column} = {value}")
                else:
                    filter_expressions.append(f"base.{column} = '{value}'")
            where_filter_expr = " AND ".join(filter_expressions)
        else:
            where_filter_expr = "TRUE"

Fixed it locally by changing it to:
if filter:
            if not self.table_schema:
                self._validate_bq_table()
            filter_expressions = []
            for column, value in filter.items():
                if self.table_schema[column] in ["INTEGER", "FLOAT"]:  # type: ignore[index]
                    filter_expressions.append(f"base.{column} = {value}")
                else:
                    filter_expressions.append(f"base.{column} = '{value}'")
            where_filter_expr = " AND ".join(filter_expressions)
        else:
            where_filter_expr = "TRUE"

@eliasecchig

thanks for flagging this @Shai-Di, will prepare a PR tomorrow to fix this!


Optimization: check and mount the bpf file system during kmesh startup

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/lgtm


drizzle-orm integration cannot generate vector columns

If I try to generate a PG table with a column like so:
embedding: vector('embedding', {dimensions: 1536}),

Then, the drizzle-kit generated migration will look like this:
ALTER TABLE "documents" ADD COLUMN "embedding" "vector(1536)";

This is not valid SQL in Postgres, it should be:
ALTER TABLE "documents" ADD COLUMN "embedding" vector(1536);

(Otherwise, you get ERROR:  type "vector(1536)" does not exist)
I am not 100% sure if this is an issue with this extension or not, but figured I'd report it here.

Hi @davidgomes, unfortunately, this is a current limitation of Drizzle Kit (docs).
https://github.com/drizzle-team/drizzle-kit-mirror/issues/115

Thank you!

This has, i believe, finally been addressed.
https://github.com/drizzle-team/drizzle-orm/pull/2360


add volumeName for each mountpoint

Introduced a name volumeName next to path in mountpoints array. Addresses #123 for windows and mac. Linux is needed.

And it would be great if this PR could update the examples in the README too :-)

@hedss What's happening with Versionist in this PR's status-checks?

Assigning this to @jviotti since (unfortunately for him) I think he knows more VBScript than any of the other Etcher team-members.

I've added a better way of extracting volume name on mac

@lurch, I think versionist will only do anything if a label is applied, hence no status report from it yet

@lurch @jhermsmeier   VersionBot only currently operates on Resin respositories. This is because it is not a public Integration. Unfortunately, in this case, we're trying to merge from an outside repo (vohtaski:master) and VersionBot has no access to it. So, we're going to need to rethink our workflow here. We could use a repo merge branch. I think this needs some discussion in a process call.

Hi @vohtaski @lurch  and @jviotti,
Have you some update about it?
I'm combining drivelist with linux-mountutils to mount and unmount in linux via NodeJS.
Drivelist reported me one device in /dev/sdc but If I do a  mount in bash, Linux says me /dev/sdc1. So, when I try to mount /dev/sdc, a linux-mountutils error displays "this device is already mounted or busy".
That error is because drivelist doesn't provide the volumeName.
Thanks for all your job.
BR
Oriol

@oriolpuig
I am using this fork for our needs, I don't know if there is a plan to merge it

@oriolpuig /dev/sdc is the device name (i.e. the whole hard-drive) but /dev/sdc1 is the partition name (i.e. the first (and maybe only?) partition on the drive). It's possible for a drive to contain multiple partitions. Etcher (which is what this module was written for) only needs the drive name (because it overwrites the whole drive at a low level). linux-mountutils (and the mount command) need the partition name, because they need to know which partition on the drive (there could be several) you actually want to mount.

yes, @lurch and that's why I would like to have the volumeName, to concat the deviceName and volumeName and mount it with the other library.

@oriolpuig "volume name" is something else entirely, and I'm not sure it's actually what you're after. AFAIK volume name is effectively a text-label that you can add to a partition, if the filesystem used on a partition supports such a feature.


cummeRbund error

hi @johanzi ,
i've been running the cufflink-cuffdiff-cummerbund pipeline for my analysis involving 2 groups (hyp-has 2 replicate, lyp-only one sample). Everything went well up to cuffdiff but when i tried plotting on cummerbund i end up with error everytime i try to plot (csScatter, csDensity, heatmap) only for the significant genes . Error says that: error:unable to find an inherited method for function 'csScatter' for signature '"data.frame". Im trying to understand where im going wrong, any help will be much appreciated.
#cuffdiff command
cuffdiff -o ./cuffdiff_output_testdata -L hyp,lyp -p 8 -b Oryza_indica.ASM465v1.dna_sm.toplevel.fa ./cuffmerge_output/merged.gtf /R32P1_R4_ensembl_GTF_tophat_out/accepted_hits.bam,/R32P3_R4_ensembl_GTF_tophat_out/accepted_hits.bam /R34P4_R_ensembl_GTF_tophat_out/accepted_hits.bam
#cummerbund
> cuffdiff_data
CuffSet instance with:
	 2 samples
	 56245 genes
	 88197 isoforms
	 76870 TSS
	 40736 CDS
	 56245 promoters
	 76870 splicing
	 39033 relCDS
> gene_diff <- diffData(genes(cuffdiff_data))
> sig_gene_diff <- subset(gene_diff, (significant == 'yes'))
> nrow(sig_gene_diff)
[1] 347
> csScatter(sig_gene_diff, 'hyp', 'lyp')
Error in (function (classes, fdef, mtable)  :
  unable to find an inherited method for function 'csScatter' for signature '"data.frame"'

Is your object "sig_gene_diff " an object of class ('CuffData','CuffFeatureSet') after subsetting? (maybe the subset function comes from another package and generates a data.frame object?


Deprecated items

When updating the vocabulary, it would be good to maintain deprecated terms in the production version and link them to their new, updated definitions. This approach ensures continuity and clarity, especially for users who might access the vocabulary through older references.
For example, the URL https://vocabulary.actris.nilu.no/actris_vocab/METEKMIRA35 was updated to https://vocabulary.actris.nilu.no/skosmos/actris_vocab/en/page/MetekMIRA35. While the update is valid, the original link now leads to a 404 error page. Such broken links create confusion as vocabulary URLs are expected to be persistent.
A better strategy would be to mark the original term as deprecated and provide a direct link to the new definition. This method is exemplified in the handling of terms in the Finto vocabulary (see https://finto.fi/yso/en/page/p24381 for reference), where deprecated terms are kept accessible and linked to their updated versions. This approach not only aids in seamless navigation but also preserves the historical context of the vocabulary changes.

Has been implemented using this documentation:
https://github.com/NatLibFi/Skosmos/wiki/Data-Model#deprecated-concepts


Auto merge GitHub PRs

One of the nice features of GitLab is the "Merge when pipeline succeeds", which GitHub currently lacks.
Civet could try to do this through the GitHub API. When done testing (and everything passes) it could check if there is an approved review on the PR and if so then merge it through the API.
If that is a bit much, it could check for the existence of a "Auto merge" label or something.
We might want to consider what would happen when a PR is "Allowed to fail". We usually want to take a look at this to make sure it is OK.

@rwcarlsen @aeslaughter

don't automerge on allowed to fail.  And also don't merge if "do not merge" label is set.


Issues formatting a large (legal) document

Source document: https://docs.google.com/document/d/15zDjqbJ7B9KBthDEYl_LH_G-Anf9CRebvKWcU5RMyB4/edit?usp=sharing
Issues found:

Header with numbers (bullets) are converted to number lists and we can't know they are headers anymore

Adding the number in the header could also be fine (e.g., ## 3. Overview)

In some cases where multiple levels of indentation occur, the formatter "get lost"

Unfortunately because of the issues, we cannot use Docs to Markdown, so we have a baseline of the type of output we would expect using .docx to markdown online converter.
Here is the full output we use from the other tool: termsOfUse.fr-CA.md

The headers in your document are numbered lists (as well as Heading 2). I suppose we could do some custom work to support this, but seems like a special case. Closing for now.


Hotfix/updated version number

@GeeH is zendframework/ZendSkeletonApplication@89c54dd supposed to be in this patch?

@Ocramius I did it yesterday in https://github.com/zendframework/ZendSkeletonApplication/pull/352, with version 3.0.1, changed to 3.0.0 ...

Oh, this is gonna be fun, ain't it.


Migration from 0.32 to 2.3.0

Hi guys,
I want to migrate from 0.32 to 2.3.0. Is that painful? Is there any documenation about it?
Best Regards
Piotr

Wow - that's a huge step!
No documentation - sorry. Just try it and fix the errors :)

Hi,
The biggest difference between v1 (and below) and v2 are internal representations and references.
In v2 both of them are removed in order to be able to work with existing inline SVG's.
Where you would have this.parent as a static variable on an element, you now have this.parent() as a method.
This it the case with all static references.

Thanks a lot for the explanation.

No prob, let us know if you have more questions.
I would just go for it, shouldn't be that hard.


Add Profile PDF exports

Maybe try using the Spatie PDF package.

@betsyecastro maybe try https://spatie.be/docs/browsershot

Currently cherry-picking from PR #78 to modify the subviews for the profile sections to be rendered without being paginated.

Created PR #79 as a draft as it still needs some work.


[aavegotchi-agip] Aavegotchi

Fixes # .
Changes proposed in this pull request:

Add new wearable IDs
Update tests

I see a few active proposals on aavegotchi space
if we merge this those will be affected
better to wait until those proposals are closed

The active proposals are likely to fail due to lack of quorum, because they are affected by the issue this PR fixes. @ChaituVR

Please merge if you don't see any other issues, thanks!

But users already voted may have old voting power while new ones will have new voting power 😅

But the VP will only increase, will not decrease @ChaituVR

If we update the voting strategy the users that already voted on current proposals will keep the same voting power but new ones will have voting power based on the updated strategy
It can cause a lot of confusion

You think you can communicate this information to users?

Yes we will communicate the update in our DAO channel.
If users that have already voted vote again, will the VP be updated?

Not by default, but if we remove cache then if users vote again, VP will be updated.

@cinnabarhorse we just flushed the cache, make sure to communicate with your users to vote again :)


Create values-fr/string.xml

French translation ;)

@zoeil5  Thanks for this. Much appreciated . <3


feat: add rate limit throttling

Description
This PR fixes #524
There are two approaches to storing the usage of an API endpoint:

Using Redis
Local in-memory store

While using Redis is the preferred method, I did not want to impose setting up Redis for Robyn users, especially if they might not even want to rate limit their APIs.
The implementation is not done, there are a few more things I would like to add, thus, this PR is still a WIP.
I am having issues with the in-memory store due to a RuntimeError: already borrowed error when I try to curl requests that have a rate limiter attached to them. Using Redis the rate limiter is working as expected.
@sansyrox If you could take a look and advise it would be very appreciated since I am a bit stuck here. Thanks!
python integration_tests/base_routes.py
curl HTTP://localhost:8080/sync/rate/get -v

Hey @IdoKendo 👋
Thank you for the great work 😄 I will take a deeper look by this weekend for sure. :D

This is very cool, I just wonder if it makes sense to be in the core Robyn implementation? It'd be adding an additional Redis dependency to all users, which wouldn't be ideal. I imagine a lot of people run robyn behind a load balancer anyway which would do the rate limiting. Not a blocker at all, just asking the question.
Could this not be an external plugin / repository that hooks into the before_request handlers?

This is very cool, I just wonder if it makes sense to be in the core Robyn implementation? It'd be adding an additional Redis dependency to all users, which wouldn't be ideal. I imagine a lot of people run robyn behind a load balancer / proxy anyway which would do the rate limiting. Not a blocker at all, just asking the question.
Could this not be an external plugin / repository that hooks into the before_request handlers?

I think making the Redis part an optional dependency would solve the issue of adding it to all users. That's also my plan once I get over the hurdle of the in-memory cache. I think it can be even more generic - Some users might want to use memcached instead of Redis, and it can also be supported.
Surely it can be developed externally, as a plugin, but I think there is an advantage in having it be included in the standard implementation.

Hey @IdoKendo @JackThomson2 👋
Thank you for your comments here 😄  I partly agree with both of you here.
We should add rate limiting as a core feature for one but should keep redis/memcached as an optional dependency like we have for templates.
And as for the issue with the implementation, @IdoKendo give me a few more hours. I will run it locally and get back to you 😄

@IdoKendo , I think I may have found a part reason. This looks like a circular dependency here.

And the second error is due to this

We get a better error message

21:19:18.717385 line        42         current_timestamp = int(time.time())
New var:....... current_timestamp =<PHONE_NUMBER>
21:19:18.717564 line        43         if pool:
21:19:18.717739 line        49         elif self.app:
21:19:18.717911 line        50             calls_count = self.app.server.get_calls_count(
21:19:18.718084 line        51                 limit_key, self.limit_ttl, current_timestamp
21:19:18.718255 line        50             calls_count = self.app.server.get_calls_count(
thread 'actix-rt|system:0|arbiter:0' panicked at 'Already mutably borrowed: PyBorrowError', /Users/sanskar/.cargo/registry/src/github.com-1ecc6299db9ec823/pyo3-0.18.1/src/pycell.rs:298:27
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
21:19:18.718632 exception   50             calls_count = self.app.server.get_calls_count(
Exception:..... pyo3_runtime.PanicException: Already mutably borrowed: PyBorrowError
Call ended by exception
Elapsed time: 00:00:00.002641
--- PyO3 is resuming a panic after fetching a PanicException from Python. ---
Python stack trace below:
Traceback (most recent call last):
  File "/Users/sanskar/repos/robyn/robyn/router.py", line 113, in inner_handler
    if client and rate_limiter and rate_limiter.limit_exceeded(
  File "/Users/sanskar/repos/robyn/venv/lib/python3.10/site-packages/pysnooper/tracer.py", line 305, in simple_wrapper
    return function(*args, **kwargs)
  File "/Users/sanskar/repos/robyn/robyn/throttling.py", line 50, in limit_exceeded
    calls_count = self.app.server.get_calls_count(
pyo3_runtime.PanicException: Already mutably borrowed: PyBorrowError

@IdoKendo , I think I may have found a part reason. This looks like a circular dependency here.

Thanks for helping to look into it!
Maybe I'm missing something, but why is this a circular dependency?

Hey @IdoKendo , I made a typo sorry. I meant a circular reference and not a dependency but that should not cause any issues.
I found a fix to our problem.
See this

Hey @IdoKendo , I made a typo sorry. I meant a circular reference and not a dependency but that should not cause any issues.
I found a fix to our problem.
See this

Ohh, great! I think this unblocks me! Thank you! I will continue working on this PR and update you when it's ready.

Not a problem 😄 I am really excited for this feature

Hey @sansyrox and @JackThomson2 👋
Thanks for all the comments and help! I've been away for a bit, but getting back to it!
For now, I've decided to remove the Redis support and add it later - to reduce the scale of this PR to a more bite-sized change.
I've changed the implementation quite a bit and still a WIP but seems to be in a much more positive direction.
If you have any helpful guidance and comments regarding the new direction, I would greatly appreciate it!

Hey @IdoKendo 👋
Welcome back 😄
I will start taking a look soon!

Hey @IdoKendo 👋
Thank you for making the latest changes. I have left a new review 😄

Hey @IdoKendo 👋
Thank you for making the latest changes. I have left a new review 😄

Thanks for the review! Helping us nail this implementation down 😎
I do wonder, I see that CI is always failing in Ubuntu yet passes in other platforms - Any thought what could be the root cause? Can't really see an issue there.

Hey @IdoKendo 👋
Thank you for the update. I have just left one final comment 😄

I do wonder, I see that CI is always failing in Ubuntu yet passes in other platforms - Any thought what could be the root cause? Can't really see an issue there.

The error seems to be here
r = method(route, expected_status_code=429)

This is resulting in a 200 status code. Looks like the rate limit is not being applied on Ubuntu. I can try testing it on my real linux machine tomorrow 😅

The error seems to be here
r = method(route, expected_status_code=429)

This is resulting in a 200 status code. Looks like the rate limit is not being applied on Ubuntu. I can try testing it on my real linux machine tomorrow 😅

Thanks! Let me know if I can help - can't seem to reproduce it on my end.

Hey @IdoKendo :wave:
I did run the tests. However, I found an unusual observation
The test run perfectly if we run just them , i.e.
venv) [batman@batmachine robyn]$ pytest -vv -k rate_limiting
============================================================ test session starts ============================================================
platform linux -- Python 3.11.3, pytest-7.2.1, pluggy-1.2.0 -- /home/batman/repos/robyn/venv/bin/python3
codspeed: 2.0.1 (callgraph: not supported)
cachedir: .pytest_cache
rootdir: /home/batman/repos/robyn
plugins: codspeed-2.0.1
collected 116 items / 110 deselected / 6 selected

integration_tests/test_rate_limiting.py::test_throttling[/sync/rate/get-get] PASSED                                                   [ 16%]
integration_tests/test_rate_limiting.py::test_throttling[/async/rate/get-get] PASSED                                                  [ 33%]
integration_tests/test_rate_limiting.py::test_throttling[/sync/rate/put-put] PASSED                                                   [ 50%]
integration_tests/test_rate_limiting.py::test_throttling[/async/rate/put-put] PASSED                                                  [ 66%]
integration_tests/test_rate_limiting.py::test_throttling[/sync/rate/post-post] PASSED                                                 [ 83%]
integration_tests/test_rate_limiting.py::test_throttling[/async/rate/post-post] PASSED                                                [100%]

===================================================== 6 passed, 110 deselected in 0.22s =====================================================

However, they fail when run with everyone else
venv) [batman@batmachine robyn]$ pytest
============================================================ test session starts ============================================================
platform linux -- Python 3.11.3, pytest-7.2.1, pluggy-1.2.0
codspeed: 2.0.1 (callgraph: not supported)
rootdir: /home/batman/repos/robyn
plugins: codspeed-2.0.1
collected 116 items

integration_tests/test_app.py ....                                                                                [  3%]
integration_tests/test_authentication.py ........                                                                                [ 10%]
integration_tests/test_base_url.py ....                                                                                [ 13%]
integration_tests/test_basic_routes.py ..................                                                                             [ 29%]
integration_tests/test_binary_output.py ....                                                                                [ 32%]
integration_tests/test_delete_requests.py ....                                                                                [ 36%]
integration_tests/test_env_populator.py .                                                                                [ 37%]
integration_tests/test_exception_handling.py ......                                                                                [ 42%]
integration_tests/test_file_download.py ..                                                                                [ 43%]
integration_tests/test_get_requests.py ..........                                                                                [ 52%]
integration_tests/test_middlewares.py ....                                                                                [ 56%]
integration_tests/test_patch_requests.py ....                                                                                [ 59%]
integration_tests/test_post_requests.py ....                                                                                [ 62%]
integration_tests/test_put_requests.py ....                                                                                [ 66%]
integration_tests/test_rate_limiting.py FF.FFF                                                                                [ 71%]
integration_tests/test_status_code.py .....                                                                                [ 75%]
integration_tests/test_subrouter.py .........                                                                                [ 83%]
integration_tests/test_unsupported_types.py .........                                                                                [ 91%]
integration_tests/test_views.py ........                                                                                [ 98%]
integration_tests/test_web_sockets.py ..

This implies an issue with the fixture being called from these throttling tests.

This implies an issue with the fixture being called from these throttling tests.

What fixture? the paramterize?

Hey @IdoKendo 👋
I have pushed a change. Let's see if that will work.

Hey @IdoKendo 👋
All looks good to me 😄 Can you please update some documentation for the same?

Hey @IdoKendo 👋
All looks good to me 😄 Can you please update some documentation for the same?

Done 😃

This adds a non-trivial amount of code to the hotpath even if it isn't enabled. Isn't this going to slow down robyn significantly?

@JackThomson2 , thanks for pointing this out. I just ran the benchmarks and the regressions are too much.
This is the after
 ~/repos/robyn  main *47  oha  --insecure -c 100 -n 100000 http://localhost:8080                                                                              ✔  1m 32s  robyn Py
Summary:
  Success rate: NaN
  Total:        5.3133 secs
  Slowest:      -inf secs
  Fastest:      inf secs
  Average:      0.0000 secs
  Requests/sec: 0.0000

  Total data:   0 B
  Size/request: NaN
  Size/sec:     0 B

Response time histogram:

Latency distribution:
  10% in NaN secs
  25% in NaN secs
  50% in NaN secs
  75% in NaN secs
  90% in NaN secs
  95% in NaN secs
  99% in NaN secs

Details (average, fastest, slowest):
  DNS+dialup:   0.0000 secs, inf secs, -inf secs
  DNS-lookup:   0.0000 secs, inf secs, -inf secs

Status code distribution:

 ~/repos/robyn  main *47  oha  --insecure -c 100 -n 100000 http://localhost:8080                                                                                 ✔  5s  robyn Py
Summary:
  Success rate: 0.1492
  Total:        26.7531 secs
  Slowest:      0.4223 secs
  Fastest:      0.0145 secs
  Average:      0.1818 secs
  Requests/sec: 2948.1840

  Total data:   126.38 KiB
  Size/request: 11 B
  Size/sec:     4.72 KiB

Response time histogram:
  0.015 [1]    |
  0.055 [1569] |■■■■■■■■■■■■■■■■■■■■■■■■■■■■
  0.096 [1456] |■■■■■■■■■■■■■■■■■■■■■■■■■■
  0.137 [1765] |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
  0.178 [1623] |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
  0.218 [1452] |■■■■■■■■■■■■■■■■■■■■■■■■■■
  0.259 [945]  |■■■■■■■■■■■■■■■■■
  0.300 [663]  |■■■■■■■■■■■■
  0.341 [803]  |■■■■■■■■■■■■■■
  0.381 [939]  |■■■■■■■■■■■■■■■■■
  0.422 [549]  |■■■■■■■■■

and this was the before.
Summary:
  Success rate: 1.0000
  Total:        1.5308 secs
  Slowest:      0.0316 secs
  Fastest:      0.0047 secs
  Average:      0.0153 secs
  Requests/sec: 6532.5208

  Total data:   107.42 KiB
  Size/request: 11 B
  Size/sec:     70.17 KiB

Response time histogram:
  0.005 [1]    |
  0.007 [10]   |
  0.010 [2]    |
  0.013 [3273] |■■■■■■■■■■■■■■■■■■■■
  0.015 [489]  |■■
  0.018 [5224] |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
  0.021 [924]  |■■■■■
  0.024 [40]   |
  0.026 [1]    |
  0.029 [23]   |
  0.032 [13]   |

Latency distribution:
  10% in 0.0111 secs
  25% in 0.0118 secs
  50% in 0.0167 secs
  75% in 0.0174 secs
  90% in 0.0181 secs
  95% in 0.0186 secs
  99% in 0.0193 secs

Details (average, fastest, slowest):
  DNS+dialup:   0.0024 secs, 0.0007 secs, 0.0033 secs
  DNS-lookup:   0.0000 secs, 0.0000 secs, 0.0000 secs

Status code distribution:

@IdoKendo , I will be reverting this PR for now. @JackThomson2 , do you have any suggestions on how we can make it faster?
I also wonder why codspeed didn't show us any regressions.

@IdoKendo , can you please remove this PR?

You could try putting this code here behind a conditional if rate limiting is enabled on the specified endpoint, it may help but only if it isn't enabled. As for fixing it when rate limiting is enabled.
The code here does a lot of allocating which I understand why this approach was taken as you'd need a mutable reference. You could try putting the array in a mutex and acquiring a lock to append too it (this should make the rate limiting more accurate as currently if two requests are made at once there's a chance one is missed.) It's a complicated problem and would require some thought into how to make it performant, just some ideas from the top of my head

I've reopened the PR at #572


Update Line 2

The title just said Continuous Integration whereas the blurb below says Continuous Integration and Continuous Deployment.

Why:

Closes [issue link]
What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[ ] For content changes, I have reviewed the localization checklist
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

@kleeadrian Thanks so much for opening a PR! I'll get this triaged for review 🎉

@kleeadrian I'm going to close this for now, but if you'd like to make the changes suggested in https://github.com/github/docs/pull/5619#pullrequestreview-647664536, feel free to reopen!

The title just said Continuous Integration whereas the blurb below says Continuous Integration and Continuous Deployment.
Why:
Closes [issue link]
What's being changed:
Check off the following:

[ ]  I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[ ]  For content changes, I have reviewed the localization checklist
[ ]  For content changes, I have reviewed the Content style guide for GitHub Docs.

Why are you stealing my repositories


network/2020-05-01: adding the missing web application firewall files

There's a large number of files in this Resource Provider - it appears this one was missed when copying over from 2020-04-01

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask<EMAIL_ADDRESS>(or NullMDR in github) for additional help.

@ArcturusZhang out of interest, shouldn't this breaking change to the Networking API be detected by the breaking change tooling?

Can one of the admins verify this patch?

@tombuildsstuff, there are a couple of linting errors, could you take a look?

hey, better to use common az networking rules to prevent such cases... sync up with me related to it

Hi @tombuildsstuff since this PR is adding some new APIs to network rather than replacing - therefore the breaking change CI will detect no breaking changes.

@ArcturusZhang

Hi @tombuildsstuff since this PR is adding some new APIs to network rather than replacing - therefore the breaking change CI will detect no breaking changes.

to clarify,I meant in the PR which added API version 2020-05, where presumably the breaking change detector should have compared this with 2020-04 and detected this functionality is being removed in the new API version?

Hi @tombuildsstuff unfortunately this is not the way that our breaking changes CI works. Our breaking change CI only check the breaking changes in the same api-version, it would not check the same thing between different api-versions.
As for the LintDiff error, it is detected because one of the paths is not in camel cases. And the service team has decided that they would fix this issue in a future api-version - therefore we could temporarily ignore the LintDiff error.

/azp run

/azp run


Displaying the name of the sender on the message

It would be really good to have the capability, especially if you decide to implement group chats

Yes, this is a feature that we plan to implement, if you want to you can create a pull request.

Hi, I am not able to access the constructor  "ChatMessage(String message, long timestamp, Type type, String sender)" for displaying sender name in group chat. Please reply asap.Thanks in advance

Hi @andkishor,
Sorry for the delayed response. The fix has been made to the master branch. We'll do some reconciliation for the dev and master branches and tag a new release containing these fixes.

how to change color of sender text


Add  support for motoman_mh5 robot with moveit_simple

Currently we support tests for kuka_kr10 robot in moveit_simple. We would like to integrate our wrapper with the motoman_mh5 and run all our functionalities for the same. We would like to use the IKFast plugin solver for this robot.

@shaun-edwards I am going to source the motoman IKFast plugin that @nsnitish created into my workspace and go from there.


Niri Nixpkgs may need to be equal to NixOS Nixpkgs

I got a black screen without error output until adding this line, worth pointing out in the readme?
    niri.inputs.nixpkgs.follows = "nixpkgs";

I don't do this, and my system has worked fine. Do you know if there's a particular package that must be in sync? I don't see any reason why it should be necessary.

Yeah, I was confused by it as well to be honest but it definitely fixed the issue for me. Among multiple tries I once get an error libGL error: DRI driver not from this Mesa build that made me try this, other than that I have no idea what could be going wrong.

The exported packages.${system}.niri now has an overridable property pkgs which can be used to set all native dependencies. In the NixOS module, it will automatically override to use the pkgs provided by the configuration, instead of the flake inputs. This means niri will always compile against the same version of mesa as in your system pkgs, and you no longer need to override the nixpkgs input. https://github.com/sodiboo/niri-flake/commit/dd8755d42d3854fc0c60e99eccd16a4c3dd282ec?diff=unified&w=1

Thanks!


Issue from website page Get Started: Install on Windows

From URL: https://flutter.io/setup-windows/

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


SL-82: build and packaging

Some remarks

tslib must be on the dependencies because we use tsconfig/importHelpers:true
I had to break down jest configurations. This is the !key! of this pull request. I will explain why in a section below.
I updated the code with some unrelated minor changes: specified node version in .nvmrc, updated .vscode with a typescript reference, updated readme with a jest hint

Why did you split jest.config.js, Chris?
In order to explain that I need to state some facts first:

we use oclif to build CLI
oclif must build to es2017 - otherwise unit testing is impossible because SomeCommand.run() fails at compilation-time
the cli package must define it's tsconfig.json file with target set to es2017
we use ts-jest combined with jest to run tests
jest.config.js has a special property called globals.ts-jest.tsConfig which tells jest+ts-jest which tsconfig.json to use (:!:)
if globals.ts-jest.tsConfig is left empty -> jest will pick up the tsconfig.json file relative to the "currently processed package's directory"
we want to be able to run all tests with one command, and generate all coverage with one command executed from the root directory
because globals.ts-jest.tsConfig is a global configuration, ts-jest will leak incompatible tsconfig.json files between packages if we set this property explicitly...

So, in order to achieve the expected result I had to add projects property to the jest.config.js file, add an individual jest.config.js file to each package, remove the globals.ts-jest property, and leave the tsconfig.json files with their standard names.
There is another gotcha, though.
The way jest extends properties from one file to another is broken.
For example:

if the base file has a projects field defined it will run all underlying jest tests and will carry some configurations. It will, for instance, carry the moduleNameMapper :| but I will not resolve testMatch property correctly.
in order to fix that I had to create a separate file called jest.base which could be then extended.

So... jest is broken, but I have somehow manage to trick it and make the configuration work. Hopefully they will fix all those issues one day.

@StefanDywersant changes addressed

Ignore the -0.6% coverage drop it's not related to my PR, codeclimate is being crazy


processing entity undefined

Describe the bug
Noticed this in the logs...
>  [discovery] - processing entity undefined
>  [discovery] - using cached metadata for entity undefined

Looking in the cache directory, I see undefined.json
{"data":{"properties":{},"hooks":{},"indexes":[],"uniques":[],"class":{"NEW":"NEW","RUNNING":"RUNNING","REPAIR":"REPAIR","REMOVED":"REMOVED","MOVED":"MOVED"},"constructorParams":[],"toJsonParams":[],"useCache":true,"path":"./build/src/db/entities/RigStatus.js"},"origin":"./build/src/db/entities/RigStatus.js","hash":"b840d15999f116addec6f1f0a4530197"}

Which contains...
import { registerEnumType } from "type-graphql";

export enum RigStatus {
	NEW = 'NEW',
	RUNNING = 'RUNNING',
	REPAIR = 'REPAIR',
	REMOVED = 'REMOVED',
	MOVED = 'MOVED',
}

registerEnumType(RigStatus, {
	name: "RigStatus", // this one is mandatory
});

Now, one could say that I shouldn't do that. =) Or another could say... throw an error if we're going to make something undefined...
Note that RigStatus is used as an enum field in the entities.
Versions

Dependency
Version

mikro-orm
3.6.5

Kind of another issue, but the documentation also states:
"For schema generator to work properly in case of string enums, you need to define the enum is same file as where it is used, so its values can be automatically discovered. If you want to define the enum in another file, you should reexport it also in place where you use it."

Note that putting the enum into its own file, does seem to work... I just get the extra json file.
Can you also add an example of reexporting it? I'm confused by that.

It depends on how you register the enum. If you do @Enum(() => RigStatus), then you do not have to care about anything.
That note is about using ts-morph discovery with just @Enum(), where the RigStatus will be read as a string and then it will try to require it from the file where entity was defined.
Reexporting simply means that in the context of the file there will be the enum available, so just this in your entity source file:
export { RigStatus } from './enum.ts';

Regarding the issue itself, I guess I will just ignore plain objects in the discovery, valid entity needs to export either class or instance of EntitySchema.

Cool, I'm doing the first bit. Might be good to expand the docs a bit to explain that so it is a little more clear.
Agreed on the main issue fix. =) Should be able to mix files in my entities directory since this enum is primarily used from there.

Thanks @B4nan . =)


Send Video

I want to add submissions for videos
sendVideo(this: Context, ...args: Shorthand<'sendVideo'>) {
this.assert(this.chat, 'sendVideo')
return this.telegram.sendVideo(this.chat.id, ...args)
}

Thanks for your PR, but where your change? i didn't see any change for your commits, i just see you just create pull request from branch dev to master. I will close this PR.


Visualization for 2D detection/segmentation

BOP has 2D tracks that focus on detection and segmentation. Does this repo support them as well. If not is there a plan to include them? If not, can anybody suggest a vis-kit for 2D tasks that is consistent with BOP format.

Hello, I tried to solve the issue.
This is what I did:
Modify the bop_viz_kit to include support for 2D detection and segmentation tasks consistent with the BOP format. This involves adding new functions to draw bounding boxes and segmentation masks, and updating the example script to demonstrate these new features.
You can review changes in this commit: https://github.com/lattaai9/nv-nguyen-bop_viz_kit-1/commit/7ba87a24396a5a4bd70618f27865c10805b6e835.

[!CAUTION]
Disclaimer: The commit was created by Latta AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

This issue was tried to solve for free by Latta AI - https://latta.ai/ourmission
If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.

Damn! I didn't know AI bots are resolving repo issues now. I will give it a try, but so far I figures that pycocotools is an alternative for 2D tasks. will post more details when I am sure/


Stuck on Failed to load account information, how it`s fix

Version
latest
Description
Stuck on Failed to load account information, I checked and confirmed the API key/secret for binance testnet, but still get "Failed to load account information"
at accountInfo i see only this
{balances: Array(0)}
please, help to fix this

@Superzirochka did you check issue #586?

Thanks, it worked


Updating Category via Webhook

Changes in this PR

update Contentful Webhook handling to allow existing Categories to be updated
add null constraints to description and slug columns on categories

Hey @EdwinKruglov, I keep forgetting the CHANGELOG. What changes are being added here? I can see from @montychristo's PR screenshots that markdown templates are already published in staging so it would be good to have a plan documented in this PR explaining how updates are made and when. For the benefit of both developers and content designers. This is functionality that needs to be recorded in Confluence so maybe @quaypho can contribute? Just mindful that until we can process MD we don't want to break staging.


T265 :Enumeration after boot on Jetson Xavier NX

| Camera Model | T265 |
| Operating System & Version | Linux nvdia-desktop 4.9.140-tegra #1 SMP PREEMPT Wed Apr 8 18:15:20 PDT 2020 aarch64 aarch64 aarch64 GNU/Linux |
| Platform | Jetson Xavier NX  |
| SDK Version | 2.35.2 |
Issue Description
Can anyone please provide any update on this issue. It seems like the camera is not detected after initial boot and one has to plug out and plug in to make it work. This is a serious problem that prevents this camera from being used in any of my products. Customers certainly cant plug out and plug in every time they want to use this device. I am really hoping Engineering team can provide some workaround for this issue.
nvdia@nvdia-desktop:~$ lsusb
Bus 002 Device 006: ID 2b03:f682
Bus 002 Device 005: ID 05e3:0620 Genesys Logic, Inc.
Bus 002 Device 004: ID 0bda:0489 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:3549 IMC Networks
Bus 001 Device 014: ID 2b03:f681
Bus 001 Device 013: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 016: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 015: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard
Bus 001 Device 012: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 011: ID 03e7:2150
Bus 001 Device 010: ID 0bda:5489 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nvdia@nvdia-desktop:~$ lsusb -d 03e7:2150 -v | grep bcdUSB
bcdUSB               1.10
nvdia@nvdia-desktop:/usr/bin$ uname -a
Linux nvdia-desktop 4.9.140-tegra #1 SMP PREEMPT Wed Apr 8 18:15:20 PDT 2020 aarch64 aarch64 aarch64 GNU/Linux
nvdia@nvdia-desktop:/usr/bin$ ./rs-pose
RealSense error calling rs2_pipeline_start_with_config(pipe:0x55bcafe4d0, config:0x55bcae7730):
No device connected
use uhubctl get data:
nvdia@nvdia-desktop:~/Downloads/USBHubReset_265/uhubctl$ sudo ./uhubctl -e -l 1-1.2 -a 1 -R
[sudo] password for nvdia:
No compatible smart hubs detected at location 1-1.2!

This is a well-known issue with this device, with no evidence of any support or fix forthcoming.
To work around, install a tool like uhubctl and use it to powercycle your usb ports on boot. On the Rpi you would do:
uhubctl -a cycle -l 1 -p 1-4
uhubctl -a cycle -l 2 -p 1-4

So I assume something like that will work for you too.

we have the same issue on jetson
t265 will not get after reboot.
we also got uhubctl compatible hub;
it doesn't seem to save the off state after reboot;
@csr-kick do you suggest to try the commands above given external usb hub?

This is clearly a bug, support should handle this as such, not with "have you tried turn it off and on again?"

seems we got it with specific usbctl compatible hub with command
uhubctl -a cycle -l 1 -p 1-4
uhubctl -a cycle -l 2 -p 1-4

First, check the USB port information through  lsusb -t
(Note: You can plug and unplug the USB you want to control to determine which BUS is which port.)
Here I'm going to operate port 6 under port 1 of BUS 02.
Execute the following command to unbind the USB:
echo '2-1.6' | sudo tee /sys/bus/usb/drivers/usb/unbind
to rebind the command, just change the unbind in the command above to BIND.
echo '2-1.6' | sudo tee /sys/bus/usb/drivers/usb/bind
I solved this problem by controlling USB binding/unbinding before enabling the program;
But this does not fundamentally solve the product problem;

there is no unbind entry on jetson

yes, I meet this problem too!!! does anyone knows how to bind-rebind the realsense device on nvidia-nx?

also got the problem ;-(


Support showing the pronunciation of Japanese like the NHK News

If there is an option to show the pronuciation  rendered above the character just like the NHK news, I think it's good for Japanese learners.
About the solution:

HTML Ruby Annotation element can support the render pronuciation above character.
In the Mecab parser, can also get the token's reading, maybe need add a field to the ParsedToken, then pass it the to the Textitem, then in the textitem template add the Ruby Annotation element with prouncation.
In the setting page, need add setting option.

Not sure  if it will effect selecting term/multipleterm event.

Thanks for the issue, as always. :-)  This could be generalized to other languages like Russian, Greek, etc etc ... but it gets challenging, for a few reasons:

it would be a big change from the current parsing mechanism and rendering -- a fundamental change actually, and I'm not sure what the ramifications would be.  You're correct in your notes about ParsedToken and the template. 👍
mecab isn't always correct in its parsing
other langs don't have something similar to Mecab, as far as I know

I think that there are add-ons that people can use to add furigana to sites as they read ... I'm not sure.
Lute is more an app for learning through reading, and not a general purpose reader, you know what I'm saying?  Perhaps something like what you're asking for is outside of Lute's scope.
One thing I can think of: after users define their terms and add pronunciations, Lute could show them that information ... but they'd have to provide that initial info.

Thank for you quick feedback jz. I agree it's may out of Lute's scope.
Yeah, what I asking for is heavily dependent on the Mecab and not suitable for other language. Making changes may result in unexpected consequences for Lute's function. And the MeCab or other parser(if exists) are not so reliable, so it really need user to provide the correct info.
I am also happy to know your idea about showing the pronunciation.

Thank you jzohrab for your work on lute3!
Having just found lute today and installed in windows docker, this is also a feature I'm looking for, mainly for Cantonese study.
I note that:
https://chromewebstore.google.com/detail/inject-jyutping/lfgpgjkjglogbndlkikjgbbfoiofbdjp?pli=1
Achieves the rime "furigana" behaviour in chrome (see image)
However the injected jyutping (i.e. Cantonese pinyin) appears to conflict with sentence translation (which I just inherited from the Classical Chinese translation option in lute, and which works for the test Cantonese text I used).

Hence, there might be an update to lute to manage this injected behaviour (as opposed to performing the injection itself).
I have some python knowledge and will investigate.

As an aside, this extension for Mandarin provides a number of 'injection' options depending on your proficiency level.
https://chromewebstore.google.com/detail/chinese-words-separator-c/gacfacdpfimbkgcnlegknnmcccjgcbnp
It overrides the translation feature in lute, i.e. by replacing the 'hover-over' behaviour.
For beginners, inclusion of tone colouring, character pronunciation would be interesting.
As part of the extension, characters can be remembered (and linked to their HSK level).
For open source extensions such as these- I imagine communication between the extension and lute could be achieved where it makes sense.

Hi @jonathonmh , I'm not 100% clear on what you've said above, so to clarify: I was thinking that the pronunciation that the user enters for the words would be shown above the word, eg:

This can be done with "ruby" text as below, but apparently browsers might not support it:
    <ruby>
        hello
        <rt>ˈhɛloʊ</rt>
    </ruby>

It could also be done with CSS and divs etc, which would be a big change from how Lute currently renders (not necessarily a dealbreaker, just has to be well tested):

...

        hello

ˈhɛloʊ

Communication with Lute and extensions would be neat, if that's possible.

Hi @jzohrab, thanks: I wasn't aware lute had the 'ruby' feature already, which seems to be intended as a manual entry.
However, for chinese characters it's my personal preference that this is done for the whole document - certainly at my beginner level of character reading.
I have the problem that: whilst I may know a Cantonese word orally, my character recognition is minimal, and hence automated ruby generation is best, and appears easily achieved through browser extensions.
I suppose then, the option that might make sense is that for well known words (as flagged in lute), their should be an option to suppress the automatic ruby/furigana injection: which is probably where the lute<>extension communication comes about.
I think this should be possible, leveraging one orf the open source extensions above.
(Note, the ability to suppress autogenerated ruby on known words, would generalise for Japanese too, and I could imagine it would be useful for other scripts where automatic generation could be valuable. Hebrew and Arabic come to mind, due to their abjad nature).
Lots of ideas here!


[VS Code] Could not connect to the server. Check that you are using a valid service endpoint.

Error:
Could not connect to the server. Check that you are using a valid service endpoint.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.198

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.23.1

platformName
MacOS

platformVersion
17.5.0

Thanks for reporting the issue. Can you send us your logs? Use the "Live Share: Export Logs" command and either drag-and-drop the zip here or email them to<EMAIL_ADDRESS>


feat: Eliminate flux dependency for cluster autoscaler

@okozachenko1203 did you forget git add by any chance? :)

@okozachenko1203 did you forget git add by any chance? :)

aha, my bad

so the only thing left here is enabling the configuration of the image_repository for the autoscaler.


readme doc updated to be in par with checklist

addressing the checklist items

Codecov Report

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

@@          Coverage Diff           @@
##           master     #21   +/-   ##
======================================
  Coverage    46.5%   46.5%
======================================
  Files         162     162
  Lines        5991    5991
  Branches     1006    1006
======================================
  Hits         2786    2786
  Misses       2783    2783
  Partials      422     422

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 1eb1b1c...c0ddbf6. Read the comment docs.


Download file from weblink

Is it possible to download a file from a weblink?
See the example below from the downloadthis R package that inspired your quarto shortcode.  https://fmmattioni.github.io/downloadthis/index.html#web-address
## Link in Github repo
download_link(
  link = "https://github.com/fmmattioni/downloadthis/raw/master/inst/example/file_1.pdf",
  button_label = "Download pdf file",
  button_type = "danger",
  has_icon = TRUE,
  icon = "fa fa-save",
  self_contained = FALSE
)

Um, no. I have not implemented download_link in this extension, mostly because this extension is not even needed to create a download button with a web link. I mean you can create the button using the raw html. Consider the following reprex,
---
title: "download_link"
format: html
---

## Quarto

<button class="btn btn-danger">Download Link</button>

Anyway, I will try to implement download_link in this extension for people who want to avoid using raw HTML as soon as possible 😃.

Or the same button could be created by adding css classes. Maybe the extension isn't needed? Maybe just a vignette?
The example below adds the pdf icon using the Quarto FontAwesome extension.
[Download Link {{< fa file-pdf>}}](https://github.com/fmmattioni/downloadthis/raw/master/inst/example/file_1.pdf){.btn .btn-danger}


need to filter item

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
customers can filter items based on their preferences (e.g., durability, price, brand reputation, sustainability). This personalization improves satisfaction by making it easier for customers to find exactly what they're looking for.

Faster Decision-Making:
Improved Product Discovery:
Higher Customer Confidence:
Use Case
A customer is looking for a backpack for travel and wants something that’s lightweight, durable, and has a high customer rating for comfort.
Benefits
By filtering for features that align with their needs, customers are more likely to be satisfied with their purchase, resulting in fewer returns and exchanges. This benefits both the customer and the business by reducing post-purchase friction.
Priority
High
Agreements

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC contributor
[X] I'm a Hacktoberfest contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

Any update?

is working in


Issue compiling using Burrito and Zig

Hi!
I am trying to compile this project as it is part of the Elixir Ash library.
I am compiling it using Burrito which is using Zig (Mingw)
I have tried to make my own .h files that link to the files inside Zig but it is a never ending rabit hole as file x links to y and y to z and so on...
This is the output I get:
52.41 --> Going to recompile NIF for cross-build: picosat_elixir -> x86_64-windows
52.58 rm -f /app/deps/picosat_elixir/priv/lib/picosat_elixir/priv/picosat_nif.so
52.58 rm -f /app/deps/picosat_elixir/priv/*.o
52.58 zig cc -target x86_64-windows -O2 -dynamic -shared -Wl,-undefined=dynamic_lookup -std=c99 -finline-functions -Wall -O3 -DNDEBUG -fPIC -I /tmp/unpacked_erts_F32707FEA96460E8/otp-windows/erts-14.2.2/include -o /app/deps/picosat_elixir/priv/picosat.o -c /app/deps/picosat_elixir/c_src/picosat.c
52.60 /app/deps/picosat_elixir/c_src/picosat.c:2282:50: warning: variable 'count_resolved' set but not used [-Wunused-but-set-variable]
52.60   unsigned num_true, num_undef, num_false, size, count_resolved;
52.60                                                  ^
52.61 /app/deps/picosat_elixir/c_src/picosat.c:5334:12: warning: variable 'collect' set but not used [-Wunused-but-set-variable]
52.61   unsigned collect, delta;
52.61            ^
52.61 /app/deps/picosat_elixir/c_src/picosat.c:6467:12: warning: variable 'num_non_false' set but not used [-Wunused-but-set-variable]
52.61   unsigned num_non_false;
52.61            ^
52.63 /app/deps/picosat_elixir/c_src/picosat.c:8149:10: fatal error: 'sys/resource.h' file not found
52.63 #include <sys/resource.h>
52.63          ^~~~~~~~~~~~~~~~
52.63 3 warnings and 1 error generated.
52.63 make: *** [Makefile:49: /app/deps/picosat_elixir/priv/picosat.o] Error 1

I was able to compile it when I added  -DNGETRUSAGE=1 to the CFLAGS for Linux
I am not sure how to fix this in a way to allow it to be compiled by Zig though..
I guess this is happening because the Makefilx.win does not apply when compiling picosat_elixir when the host is linux and the target is Windows. Somehow..
UNAME_SYS := $(shell uname -s)
ifeq ($(UNAME_SYS), Darwin)
	CFLAGS := -std=c99 -finline-functions -Wall
	LDFLAGS := -flat_namespace -undefined suppress
else ifeq ($(UNAME_SYS), FreeBSD)
	CFLAGS := -std=c99 -finline-functions -Wall
else ifeq ($(UNAME_SYS), Linux)
	CFLAGS := -std=c99 -finline-functions -Wall -DNGETRUSAGE=1
endif


Get rid of omz

We want some funktionality of omz in our shell WITHOUT waiting a second until the terminal has loaded.
We need atleast

[ ] ricing
[ ] no need for cd
[ ] better history

Chatgpt:
In Zsh, you can use the omz (Oh My Zsh) framework to enhance your command line experience, but if you're looking to make the cd command obsolete, you can create a custom function or alias that allows you to navigate directories more efficiently.
One common approach is to use the autcd feature, which allows you to change directories just by typing the directory name without needing to use the cd command explicitly. Here's how you can set it up:

Enable autcd in your .zshrc file:
Open your .zshrc file in your favorite text editor:
nano ~/.zshrc

Add the following line:
This line enables the autcd feature:
setopt auto_cd

Save and exit:
If you're using nano, you can save and exit by pressing CTRL + X, then Y, and Enter.

Reload your .zshrc:
To apply the changes, run:
source ~/.zshrc

Now, you can simply type the name of a directory to navigate into it without needing to type cd. For example, if you have a directory named Documents, you can just type:
Documents

And it will take you to that directory.
Additional Tips

Using fzf for fuzzy finding: If you want to enhance your navigation further, consider using fzf, a command-line fuzzy finder. You can set it up to quickly navigate through directories.

Creating custom functions: You can also create custom functions in your .zshrc to handle specific navigation tasks or shortcuts.

By using these features, you can effectively make the cd command less necessary in your workflow.


Bug: SnsSchema parsing fails when Subject is null

Expected Behavior
Sns events with a Subject that is null should pass schema parsing with SnsSchema.
Current Behavior
For an event like this:
{
  "Records": [
    {
      "EventSource": "aws:sns",
      "EventVersion": "1.0",
      "EventSubscriptionArn": "a subscription arn",
      "Sns": {
        "Type": "Notification",
        "MessageId": "a message id",
        "TopicArn": "an arn",
        "Subject": null,
        "Message": "hi there",
        "Timestamp": "2024-12-04T08:00:04.497Z",
        "SignatureVersion": "1",
        "Signature": "",
        "SigningCertUrl": "http://www.google.com",
        "UnsubscribeUrl": "http://www.google.com",
        "MessageAttributes": {}
      }
    }
  ]
}

The following fails:
import { SnsSchema } from '@aws-lambda-powertools/parser/schemas';

SnsSchema.parse(event)

This is due to Subject being null. It can be omitted or undefined, but in the case of null it seems to throw. However, it is a valid case for SNS to have Subject be null.
Code snippet
import { SnsSchema } from '@aws-lambda-powertools/parser/schemas';

SnsSchema.parse(
{
  "Records": [
    {
      "EventSource": "aws:sns",
      "EventVersion": "1.0",
      "EventSubscriptionArn": "a subscription arn",
      "Sns": {
        "Type": "Notification",
        "MessageId": "a message id",
        "TopicArn": "an arn",
        "Subject": null,
        "Message": "hi there",
        "Timestamp": "2024-12-04T08:00:04.497Z",
        "SignatureVersion": "1",
        "Signature": "",
        "SigningCertUrl": "http://www.google.com",
        "UnsubscribeUrl": "http://www.google.com",
        "MessageAttributes": {}
      }
    }
  ]
}
)

Steps to Reproduce
Run the codesnippet above and it should fail
Possible Solution
Allow the Subject field to be null as well as omitted
Powertools for AWS Lambda (TypeScript) version
latest
AWS Lambda function runtime
22.x
Packaging format used
npm
Execution logs

Hey Niels, thanks for opening the issue! While the fix is easy, I will take a closer look why we missed it in our tests.
Feel free to drop a PR, if you like, since you have spotted it first 😁.

@am29d I just came here because this started happening to me. I'm almost willing to posit that AWS actually changed it because @types/aws-lambda is Subject?: string as well. I have no proof of course, I worked around it by sending a subject.


After bulk expiring silences, the silences should be deselected

This bug was normally not seen because after expiring the silences, they are not displayed on the list page with the default list settings. You could see the bug by changing the list filter to display the expired silences before navigating away from the page.

/lgtm


Feature: Make reaction and repo list tooltips

Type of feature
🍕 Feature
Current behavior
There are places in the app that do not show context
Display the list of people that reacted

Show the other repos that are listed

Suggested solution
This might need api-updates.
Additional context
No response
Code of Conduct

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

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

@bdougie Can you guide mw where to look into?

Look for the ToolTip component and how it's implemented. Use that component as a wrapper for the reaction.
I not entirely sure the data is provided from the API, I'd check that and look at the api to confirm.

There is an issue about showing a tooltip in highlight reactions https://github.com/open-sauced/insights/issues/1092


Swapped User logic incorrect in Django 1.7

in permissionmodels.py there is a piece of logic to determine if the user is swapped. There are two paths through the code, one for Django 1.6 and one for other versions of Django. The wrong branch is taken in Django 1.7. The logic should, in my opinion be,
if DJANGO_1_6 or DJANGO_1_7:
and DJANGO_1_7 should be imported at the top.

Moved mentioned migration-models

"PageUserGroup" and "PagePermission"

from original origin in file

cms/migrations/0002_auto_20140816_1918.py

to initial file:

cms/migrations/0001_initial.py

and did a sqlmigrate on both files (sqlmigrate cms 0001_initial & sqlmigrate cms 0002_auto_20140816_1918).
Works like a charm without any more modifications!
At https://docs.djangoproject.com/en/1.7/topics/auth/customizing/#substituting-a-custom-user-model  its described that:

"AUTH_USER_MODEL is created in the first migration of its app (usually called 0001_initial); otherwise, you will have dependency issues"

"PageUserGroup" and "PagePermission" access "AUTH_USER_MODEL" thats the reason why they need to be moved to 0001_initial.py file.