Menu is buggy / out of sync

Summary
When selecting text very fast (i.e. letting go of selection straight away) on iPhone, the menu doesn't pop up and you must tap the selection to get the menu up.
Also, when you have logic in the menu e.g.
menuItems={
someFunction() ?
[
{
label: "Dictionary",
key: "dictionary",
},
{
label: "Copy",
key: "copy",
}
]
:
[]
}

the menu can get out of sync. It may display when it's not supposed to and not display when it should. Almost like it's using a ref that's behind state, but not always, just on occasion.
What platform(s) does this occur on?
iOS
What workflow(s) does this occur on?
Expo Workflow
Environment (or package.json)
{
"name": "pagepal",
"version": "1.0.0",
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web",
"lint": "eslint ."
},
"dependencies": {
<EMAIL_ADDRESS>"^0.12.0",
"@epubjs-react-native/core": "^1.4.1",
"@epubjs-react-native/expo-file-system": "^1.1.3",
"@gorhom/bottom-sheet": "^4.6.1",
"@react-native-async-storage/async-storage": "1.23.1",
"@react-navigation/bottom-tabs": "^6.6.1",
"@react-navigation/elements": "^1.3.30",
"@react-navigation/native": "^6.1.17",
"@react-navigation/stack": "^6.3.29",
"@tanstack/react-query": "^5.52.1",
"axios": "^1.6.8",
"buffer": "^6.0.3",
"epubjs": "^0.3.93",
"expo": "^51.0.32",
"expo-av": "~14.0.5",
"expo-document-picker": "~12.0.1",
"expo-file-system": "~17.0.1",
"expo-linear-gradient": "~13.0.2",
"expo-status-bar": "~1.12.1",
"lucide-react-native": "^0.426.0",
"moti": "^0.28.1",
"react": "18.2.0",
"react-native": "0.74.1",
"react-native-drawer-layout": "^3.3.0",
"react-native-fs": "^2.20.0",
"react-native-gesture-handler": "~2.16.1",
"react-native-modal": "^13.0.1",
"react-native-paper": "^5.12.5",
"react-native-reanimated": "~3.10.1",
"react-native-safe-area-context": "4.10.1",
"react-native-screens": "3.31.1",
"react-native-svg": "^15.5.0",
"react-native-webview": "13.8.6"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@expo/metro-runtime": "~3.2.3",
"eslint": "8.0.0",
"eslint-config-universe": "^12.0.0",
"react-dom": "18.2.0",
"react-native-web": "~0.19.10"
},
"private": true
}
Your .epub file
No response
Minimal reproducible example
No response
I confirm that i have

[X] I looked for a solution to my problem in other open and resolved issues
[X] I checked the examples provided solve my problem
[X] I have verified that my problem is not caused by a third-party library
[X] I cloned the project environment examples and still the problem persists
[X] I'm using the latest available version of the library and its complements

Okay I've done some experimenting.
Moving the function calculation outside of the menuItems and calculating it beforehand does NOT help.
The two bugs I listed are in fact related.
The only time we get the wrong (previous) menu pop up, is if a quick release is done. Very similar to how we get no menu popup at all when releasing quickly.


If Spawner dies while Raining Gold, doesn't switch to spawn

If someone nukes a Spawner while Raining Gold is active, nothing is clicked automatically, when it should start clicking on the spawn.

@BuddhaBuddy1 Does it still happen?

It is hard to tell, the levels are over so fast, but I think it does still fail to switch to the spawn when the spawner dies while Raining Gold still has time left.

This merits some investigation

I believe the problem is in the part where it has found a raining gold lane and is scanning through the enemies. The script scans through every monster in the game, as opposed to just the ones in the lane, and finds the one that would yield the most gold if it was in the raining gold lane.
What this means is that if there is a spawner in the lane with the highest raining gold multiplier it will attack the spawner. If there are only creeps but there is a spawner in a different lane, you will still be targeting the empty spawner position and wind up just sitting there.

@armetilou nice catch! Just submitted a pull request

@wchill https://github.com/wchill/steamSummerMinigame/pull/161
This can be closed :)


fix(parser): apigw check_message_id and tests

Issue #, if available:
Description of changes:
Changes:

Add some more unit tests
Fix bug with check_message_id not looking in the RequestContext
Add more mypy coverage
Add pragma: no cover

Checklist

[X] Meet tenets criteria
[X] Update tests
[X] Update docs
[X] PR title follows conventional commit semantics

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@risenberg-cyberark  - can you check the apigw fix I made for the validation.

Codecov Report

Merging #553 (0e01247) into develop (a768b68) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #553      +/-   ##
===========================================
+ Coverage    99.86%   99.91%   +0.04%
===========================================
  Files          113      113
  Lines         4483     4477       -6
  Branches       243      243
===========================================
- Hits          4477     4473       -4
+ Misses           3        1       -2
  Partials         3        3

Impacted Files
Coverage Δ

aws_lambda_powertools/tracing/tracer.py
100.00% <ø> (+1.04%)
:arrow_up:

...ols/utilities/feature_toggles/appconfig_fetcher.py
100.00% <100.00%> (ø)

...ools/utilities/idempotency/persistence/dynamodb.py
100.00% <100.00%> (ø)

...lambda_powertools/utilities/parameters/dynamodb.py
100.00% <100.00%> (ø)

...lambda_powertools/utilities/parser/models/apigw.py
100.00% <100.00%> (+2.59%)
:arrow_up:

aws_lambda_powertools/utilities/parser/types.py
71.42% <0.00%> (-28.58%)
:arrow_down:

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 a768b68...0e01247. Read the comment docs.

btw, the code coverage is insane :) @michaelbrewer

@heitorlessa  i will leave out the other possible type checking and validation checks for idempotent for another time


Add cursor style option

This makes it possible to change the default cursor style of the
terminal. It requires a restart to apply the changes.
When vim or a different terminal application changes the cursor, it is
not reset. But I wouldn't say that's an issue with alacritty, but rather
with the terminal application.

Would it be possible to detect cusor changes from a spawned process, and revert them upon termination? Probably should be a separate PR if we want to do something like that...

I've made the requested changes. I didn't see a way to get the config from the set_cursor_style call, so I added the default cursor as a field on the Term struct.
Not sure if that's the best approach, but it seems like the easiest way to make it work.

Travis passed except for one job that wouldn't start.

This is amazing! I got everything working (live reload, ansi sequence, vim, vim in tmux, vim in tmux in ssh).
Wondering if the blinking cursor modes will become supported. I run many terminal windows and it is very difficult to tell which alacritty window is currently focused if the active window's cursor does not change color or blink. It's perhaps outside the scope of this PR but I noticed there are blinking modes and they work great in iTerm. See here

@unphased blinking cursors is tracked in this PR: https://github.com/jwilm/alacritty/pull/651
Right now I don't think anyone is working on this and it's quite a bit more work to get it done from what I understood. But it's definitely something that's planned.

Oh, thank you! Sorry, I didn't do a proper search before posting my question.

No problem. :)


emails: Fix contact_us macros for "mailto" in email links.

As noted in this CZO discussion, the new macros introduced for contact us links in commit dcea17eb4496ffa708c90b2d57dd7bc56b2400a2 were missing the "mailto:" in the anchor tags.
Notes:

Updates the contact_us_zulip_cloud and contact_us_self_hosted email macros to have the "mailto:" scheme in the anchor tag for the support email address.
Also updates the Zulip Cloud version of the support email anchor tag for the account_registered email, which has a slightly different format/text than the macro.
Did a sweep of all anchor tags in the templates/zerver/emails directory to make sure there are no other email links that are broken.

Screenshots and screen captures:

Zulip cloud - new account registered email in dev environment

Self-hosted org - new account registered email in dev environment

Zulip cloud - onboarding guide in dev environment

Self-hosted org - onboarding guide in dev environment

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @laurynmm!


AWX tower URL redirection

Production environment

OS: CentOS OEL
Kubernetes/K3s: K3s
AWX Operator: 23.8.0

Description
We have awx setup and the URL is https:/<>// and we wanted to change the old url to new URL  https://<>.
Do we have provision to redirect the old url to new url.

@Nilesh486
Hi, sorry for the late reply, I haven't been feeling well and couldn't find the time to respond.

We have awx setup and the URL is https:/<>// and we wanted to change the old url to new URL https://<>.

Lack of information, but am I correct that you want to redirect users from https://old-url-of-awx.example.com/ for your old AWX on K3s to https://new-url-of-awx.example.com/?
If so, technically we can use RedirectRegex feature of Traefik to redirect users, but it also requires additional expertise with Traefik, Ingress, K3s, AWX Operator, SNI, etc.
It is out of scope to provide a complete guide here, so if you are interested, give it a try.
If you want a quick fix, you can run the web server with the old URL to redirect users, for example.


401 error

Hi,
I'm testing the WP Node API and I'm trying to create a post, however I get this error:
{   "code": "rest_cannot_create",   "message": "Sorry, you are not allowed to create new posts.",   "data": {     "status": 401   } }
I'm authenticating with my login for wordpress and testing it on localhost. This is the code:
var WPAPI = require( 'wpapi' );

var wp = new WPAPI({
    endpoint: 'http://localhost/WordPressAPI/wordpress/wp-json',

    username: 'username',
    password: '--!',
    auth: true
})

var post = wp.posts().create({
    // "title" and "content" are the only required properties
    title: 'Your Post Title',
    content: 'Your post content',
    // Post will be created as a draft by default if a specific "status"
    // is not specified
    status: 'publish'
}).then(function( response ) {
    // "response" will hold all properties of your newly-created post,
    // including the unique `id` the post was assigned on creation
    console.log( response.id );
});

Running this code in NodeJS doesn't do anything either. Does someone know what I'm doing wrong?
Thanks!

Hello @marcianosr and thanks for using the WordPress REST API (and this library!) Can I ask whether you're running the Basic Auth plugin on your site? That plugin must be installed and active for username/password authentication to succeed.
As a side note, the "auth: true" should be unnecessary, but would not contribute to the error you are seeing.

Hi @kadamwhite!
Thanks for answering!
Yes I downloaded the Basic Auth plugin on my website. I somehow still get a 401 error on creating posts. Pretty weird, maybe I missed something.

@marcianosr May I ask what you're using to run your local server?
You can check to see if it's an issue with the client itself or an issue with your server by testing the request with curl; for my test environment if I run
curl --user apiuser:password http://wpapi.loc/wp-json/wp/v2/users/me

I then get back the JSON for my user record, the same as if I ran
require( 'wpapi' ).site( 'http://wpapi.loc/wp-json' ).auth({
  username: 'apiuser',
  password: 'password'
}).users().me().then(function( user ) {
  console.log( user );
});

If the curl command doesn't work (and curl should be available for all systems, how you install it depends on your operating system) then the issue is probably a server setting of some sort.

@kadamwhite
I'm using wamp server for my wordpress configuration with a standard installed wordpress, and running another server on another port for the frontend and node js backend.
When I cURL or use postman to the url, I get the same 401 error, while I am logged in to WordPress.
{   "code": "rest_not_logged_in",   "message": "You are not currently logged in.",   "data": {     "status": 401   } }

@kadamwhite
I got it working! It seems I installed the wrong basic auth plugin...
I now installed the good version: https://github.com/WP-API/Basic-Auth
Thanks  for helping :)

@marcianosr my pleasure, I'm glad to hear you got things working! Thanks for the update and let us know if you run into anything else!


Black Lives Matter

and wtf is this Black Lives Matter??
I thought I go to moment.js page, not on a propaganda page

I agree.  It's just obnoxious spam at this point.

Мир ебанулся

This seems to be more of a personal issue, not one with the library.

I haven't any "personal issue" with this "bs". every one feeding us whid it. and now moment js how haven't any connection with this. so maybe it's enough.

In the communist country from where I came, students were made to recite slogans of the party, and we could see large banners of those slogans everywhere we go.  The authoritarian government wanted to make sure everyone is on the same page...
For those who wants justice: Equality of opportunity is the only true justice.  Equality of opportunity should be the ONLY type of equality the social justice movement be concerned with.  But as it stands, the movement is something much more sinister.
The social justice movement, if it had been pure in aim, has now been co-opted by radical Marxists.  Marxists are power-craving authoritarians who are obsessed with inequality, and want an authoritarian government to take from the haves and give it to the have-nots, regardless of merit.  That last part is important, because not all inequality is caused by injustice.  The radical Marxists, however, do not care about the distinction.
In the 20th century, the focus was on wealth inequality, and under the guise of compassion they pitted the poor against the rich.  The ensuing class warfare resulted in some 60 million deaths, multiple times the work of Adolf.  And even though their meritless utopian ideal were thoroughly discredited, they did not give up.  Since then they've come up with a new plan.    Different players; same game.
The number of unarmed black people killed by police last year can be counted on your fingers.  And it is not out of proportion, demographically, when the crime rate per capita is taken into account.  There is no rational basis at all for the ongoing racial unrest.  There is no data supporting it, and such policy prescriptions as defunding the police are patently insane.  Truth is, the radical Marxists want to defund the police so that their roaming mobs can exert power over your community, like what's happening in Portland and Seattle.  That's what they really mean by "reimagining public safety", as the NYT called it.
As authoritarians, they want to use their power to squash ideological nonconformity.    Last week in Washington a group of BLM protesters entered a restaurant and asked everyone to raise their fist to show their solidarity.  If the reader thinks that that is somehow okay, then the reader does not understand what mob rule is, and has taken for granted the freedom and liberty that millions of your predecessors gave their lives to protect.

Agreed. This is insufferable propaganda that needs to stop. I'm using https://date-fns.org/ from now on.

I read this quote that I liked:
"I don’t think it’s helpful to push the minority population to exaggerate their suffering. I think it’s important to know where the problems are but this hyperbolic approach of decrying systemic racism in every institution, in the entire country, and everyone in it as corrupt and racist...well first off I don’t believe that to be true and second of all that does not admit for any solutions on a practical level."

I read this quote that I liked:
"I don’t think it’s helpful to push the minority population to exaggerate their suffering. I think it’s important to know where the problems are but this hyperbolic approach of decrying systemic racism in every institution, in the entire country, and everyone in it as corrupt and racist...well first off I don’t believe that to be true and second of all that does not admit for any solutions on a practical level."


alonso features before collateral

If this is what you meant, I'll close the other alonso related PRs.

data_hash -> datum change is pending.


Auto update installs a version unsupported by OS

Expected Behavior
Automatic updates will not be offered if they require an OS version greater than the current one.
Actual Behavior
Insomnia gave me a popup to auto-update to 8.4.0 but then once installed I could no longer open the app since it requires a higher version of MacOS than I am using.
Reproduction Steps
No response
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
8.4.0
What operating system are you using?
macOS
Operating System Version
10.14.6
Installation method
Download originally, auto-update through the app since
Last Known Working Insomnia version
8.3.0

We did update the Electron version to 27.x and it seems like older version of Mac are not supported anymore by Electron itself (well, by Chromium specifically): https://www.electronjs.org/blog/electron-27-0#removed-macos-1013--1014-support
While we would like to have Insomnia run on every version of the OS, we also cannot run on outdated versions of Electron.

That’s fine, but what I’m suggesting is that it should not auto update to a version that is unsupported on the current OS because then there is no way to open the app or revert.

Ah I see what you mean. We are using the auto-updater capability of Electron which determines the updated based on the version alone.
To keep using an older version on an older OS you can manually download the specific version that you want from our releases and disable the auto-updates in the preferences.


Fixed perma-crash on LS compile failure with a try/catch.

NOTE: Changed package settings to host/listen on <IP_ADDRESS>.

This isn't the way to fix it. Will figure out something else and resubmit PR.


Add resource.address.httpxe test dependency to server\pom.xml since it i...

...s needed for the WebSocket transport. This allows other projects such as jms.server.itests to use the server pom.xml as a BOM without needing to add specific dependencies like this.

David please release Gateway after merging this (or I can do it if you tell me how). Thanks, chris

Coverage decreased (-0.01%) to 46.41% when pulling dba2d11d0f7aacb89d216f25fbd93bd8b44be831 on cmebarrow:add_httpxe_to_server into 75b8887fcba7d1e03f07df2abc7ec16c8ffbef9f on kaazing:develop.

Coverage decreased (-0.01%) to 46.41% when pulling dba2d11d0f7aacb89d216f25fbd93bd8b44be831 on cmebarrow:add_httpxe_to_server into 75b8887fcba7d1e03f07df2abc7ec16c8ffbef9f on kaazing:develop.


Implements boolean logical and/or in kcl

Recreation of old PR #4194 (previous PR was created on a fork owned by me, this PR is a branch on modeling-app origin)
Moved tests to simulation tests, and omitted keyword parsing fix that is no longer needed (but left the tests for this behavior).
Closes #4188.

Push an empty commit to accept the png snapshot and trigger CI.

Push an empty commit to accept the png snapshot and trigger CI.

will do, thanks @jtran


Status update?

Hey!
I was really looking forward to seeing this project get released and grow. I apologize for opening an issue here but I couldn't find an email for you on your website. Are there updates regarding this project you can share?
Thanks!

Hey @jonpalmisc , no need to apologize! I'll send you an email directly, but there should also be an email going out to the mailing list shortly. Progress has been slowed and often delayed throughout the year, and a lot is still undecided in terms of establishing a lasting syntax, which I would like to have in place before a 1.0 release in order to avoid breaking changes to old files as the project grows over time.
That being said, I'd like to open up the development soon and engage with everybody who is interested in the project.
Thank you for your interest and patience :)


New Endpoint for PFAM domains

Fixes #60
Added a new endpoint for PFAM domains. The PfamDomain model currently reflects the biomart file, but we should probably extend it with additional domain information.

@onursumer could we change the property to default to the included biomart file path ensembl.biomart.pfam. Right now heroku fails because it can't find the biomart file. I think we should set up in such a way, such that it builds without doing any extra steps.
2017-09-26T09:14:31.995875+00:00 app[web.1]: java.lang.IllegalArgumentException: Could not resolve placeholder 'ensembl.biomart.pfam' in string value "${ensembl.biomart.pfam}"
2017-09-26T09:14:31.995876+00:00 app[web.1]:    at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:174) ~[spring-core-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0aae6db). Click here to learn what that means.
The diff coverage is 0%.

@@           Coverage Diff            @@
##             master     #62   +/-   ##
========================================
  Coverage          ?   8.81%
  Complexity        ?      29
========================================
  Files             ?      29
  Lines             ?     771
  Branches          ?      74
========================================
  Hits              ?      68
  Misses            ?     692
  Partials          ?      11

Impacted Files
Coverage Δ
Complexity Δ

...tion/domain/internal/PfamDomainRepositoryImpl.java
0% <0%> (ø)
0 <0> (?)

...al/genome_nexus/annotation/web/PfamController.java
0% <0%> (ø)
0 <0> (?)

...tal/genome_nexus/annotation/domain/PfamDomain.java
0% <0%> (ø)
0 <0> (?)

...tation/service/internal/PfamDomainServiceImpl.java
0% <0%> (ø)
0 <0> (?)

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 0aae6db...1763cee. Read the comment docs.

@inodb There was a typo in application.properties.EXAMPLE, now the heroku instance should work fine.


newline, enter function in markdown.

When I input "Enter key" twice, I would like the mark-down to be something like a br tag or a line break.
Can this function be put in?
I can help if you want. :)

The line break feature already exists.
I will open it again after the test.


KendoUI Web Components

davidpurkiss writes
I think something that should be discussed sooner rather than later is the current support that Telerik provides for web components with KendoUI.
http://docs.telerik.com/kendo-ui/webcomponents
Personally, I've been avoiding the issue as that means I need to now understand, intimately, how web components work. Over the last few weeks as my understanding of Aurelia has grown and having had a chance to play around with building custom elements properly, I feel like this is now less of a task.
Off the bat, I've come across this article and this aurelia issue. So it sounds like the Telerik web components are based on Polymer's implementation of custom elements which means we will never be able to use them with Aurelia (unless your bring Polymer into Aurelia, which sounds undesirable), which I don't think is really an issue. At this point I don't know yet, perhaps someone else has some insight?
For me the more important question is, should we be basing our implementation on Telerik's web component implementation. In other words, ideally I would copy and paste some sample from the KendoUI documentation into an Aurelia app and it just works.
I guess the TL:DR of the issue is, how do KendoUI components fit into this project?

I believe that our wrappers are web components also, but are more integrated with aurelia than the web components of Kendo itself. I don't see any reason why we should use their web component controls.


Add Support for ROCM (AMD GPUs)

Summary
Nvidia GPUs are ubiquitous in the market and darknet supports them well. However, it would be nice to have options in the AMD GPU market, which tends to be less expensive and often has more VRAM available for darknet training and usage than many of their Nvidia counterparts.
Though there are two options for non-Nvidia support (OpenCL and HIP/ROCM), the mapping between HIP and CUDA calls should be more of a one-to-one, and easier to support. Various papers/research surveys have also noted that OpenCL is generally slower (often by multiples like 2-8x, depending on operations).
In a hackathon, a group submitted a pull request to the old darknet repo with support for HIP. The integration was crude with #defines used to replace CUDA calls with direct HIP calls. It would be appreciated to review this pull request and/or tools that exist for CUDA->HIP porting to support modern AMD GPU optimizations so that the .weights models can be directly loaded onto the GPU without conversions to onnx.
Goals

Implement HIP/ROCM support in darknet for training and running weights models
Integrate HIP/ROCM compilation into the cmake build process

This will require the purchase of some AMD hardware, since I only have NVIDIA-based systems.


add callback to fs.writeFile

The callback argument for fs.writeFile seems to be enforced on newer versions of node. Without this argument the hash save fails and npm install runs each time as there is no saved hash to compare against.

Thanks!


Refactor clrypt: remove M2Crypto dependency

This is a significant two-part refactor:

I separated the bulk of clrypt's behavior into EncryptedDirectory and OpenSSLKeypair classes; this means we can test encryption and file management independently. clrypt/__init__.py simply composes a keypair constructed from the appropriate environment variables with an encrypted directory.

Instead of M2Crypto we use the OpenSSL command-line tool. It's pretty much guaranteed to be available everywhere, all of our uses of clrypt seem to be outside of the request flow so performance isn't much of a concern, and we will no longer have to deal with SWIG or OpenSSL headers.

also new

better

this is awesome! LGTM. like the docstrings and tests, and thanks for taking the time to ensure that this is backwards-compatible with our current setup.
in terms of further work, we could add a TODO to use the pubkey signature rather than the key ID that we compute, as you mentioned.
beyond that, we should think about the feasibility of removing secrets from our codebase completely, but I also think that this approach will continue to work for the time being.

Thanks! I'll merge. OK if I bump to v0.2.0 + tag?

sounds good


Fixed Wing Offboard Ignores Attitude Setpoint

The fixed wing controller ignores attitude setpoints in offboard mode. I originally filed this over on mavros, but later found the problem in the px4 firmware (https://github.com/mavlink/mavros/issues/630)
I've tentatively traced it to the fixed-wing attitude controller which generates attitude targets from the manual inputs whenever climb rate control is disabled (line 959, https://github.com/PX4/Firmware/blob/master/src/modules/fw_att_control/fw_att_control_main.cpp)
adding another condition for offboard mode fixes it, but I'm not familiar enough with the controller structure to know if that is likely to introduces problems elsewhere.
Original:
if (!_vcontrol_mode.flag_control_climb_rate_enabled) {
With additional condition:
if (!_vcontrol_mode.flag_control_climb_rate_enabled && !_vcontrol_mode.flag_control_offboard_enabled) {

@fiji3119 FYI

That's part of it, but you'll also want to prevent fw_pos_ctrl_l1 from publishing like MC does here - https://github.com/PX4/Firmware/blob/master/src/modules/mc_pos_control/mc_pos_control_main.cpp#L2201

Ah, thanks. It did work after only the first few changes, weird. I guess the two setpoints were fighting for the controller's attention.


Remember FAQ page state (#1091)

Closes #1091

Store page state in route

Add logic to remember opened questions

Fix cypress tests for updated back end data

In Question "How do i make a donation to Civic Tech Index" and "What are topic tags?" and "How do i volunteer with Civic Tech Index?",
the link opens in the same page.I think external links are supposed to be open on another tab.when i was working on Collaborate With us Page
i was told external link should open on new tab.I am not sure this is feasible because the questions and answers are from an api

You're right, external links should open new tabs.  You're also correct that the front end doesn't have control over how links are presented in the FAQs since it is content that comes from the back end API.


Maven: allow specifying a custom groupid/artifactid

This is going to be tricky, but is required to be able to publish Ceylon modules in Maven Central.
For this, we need to be able to specify which group/artifact we belong to, in a more custom way than splitting on the last dot as we do ATM.
For example, the entire distrib in Maven Central has been published using the org.ceylon-lang groupId: https://mvnrepository.com/artifact/org.ceylon-lang
In order to support generating the right pom.xml I need to add some annotation in the language module to describe this on the module descriptor.
But I also probably need to build in somewhere an equivalence so that ceylon.language and maven:"org.ceylon-lang:ceylon.language" are seen as equivalent. I still have to think about this, and how it impacts compile/run-times.

Perhaps something like an artifact annotation with a group attribute and an optional second prefix attribute? If you don't specify the prefix the entire module name will be used as the artifact name. So for our modules in Maven Central it would simply be:
`artifact(group="org.ceylon-lang")`

But for situations where you want to split the original module name in two you could do something like:
`artifact(group="org.ceylon-lang", prefix="com.redhat.ceylon")`

Which would have given us artifacts like org.ceylon-lang:common and org.ceylon-lang:module-resolver.

Wait. Is org.ceylon-lang really a great group id? I would prefer one without dashes.

It's what Julien has used for Maven Central since version 1.2.0. It's also what our top level domain is for the website.

We also own ceylonlang.org
On 17 January 2017 at 16:52, Tako Schotanus<EMAIL_ADDRESS>wrote:

It's what Julien has used for Maven Central since version 1.2.0. It's also
what our top level domain is for the website.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ceylon/ceylon/issues/6853#issuecomment-273227387, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1rf6AcZZS6QvI9uVfGy3HUkWnPyTK9ks5rTPHQgaJpZM4Lb4pi
.

Funny is that it's not legal as a groupId (see https://maven.apache.org/guides/mini/guide-naming-conventions.html) but it's obviously been accepted.
It does follow https://mvnrepository.com/artifact/org.scala-lang, though.

See #6872.

Done.


Visual Studio - exited with code<PHONE_NUMBER> (0x406d1388) (shared libs)

Hi, it seems there are some compilation flags that causing this issue (which is related with thread naming). It mainly happens when I try to set the tread_count > 1 and then opening the codec. I've tested same ffmpeg version (7.1) with gyan's releases and was working fine.
Possible related compilation flags here?
https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/thread.h

Not sure what you're asking. Those codes mean nothing. Looks like a "good old crash" to me, so you're probably doing something wrong in your code.
But impossible to tell, and this is also not the place to debug your code.

I'm pretty sure the issue with the compilation as Gyan's same version works.
Sorry for not having an easy reproducible way yet. I might have tomorrow.
Leave this open and I will try to create a PR when I will find some time to compile it manually.

Do you have a commandline that reproduces the crash?

It happens only when using the libraries as native from Visual Studio.

I can't really make any promises when using them from Visual Studio.
Not even sure if all type sizes are the same between MSVC and gcc/mingw. Though they normally should be.
But some kind of semantics might be slightly different. Would highly recommend not using MSVC together with non-MSVC-built libraries, specially if those libraries bundle in a ton of libraries.

One reason that I'm using a custom Generator is that. To fix all the type sizes issues that currently FFmpeg. Autogen has. But I'm pretty sure that the issue is not with the type sizes.

What do you mean by "custom Generator", and how does ffmpeg have type size issues?
Also, what is "ffmpeg autogen"? FFmpeg does not use autotools. And the build system has no influence on type sizes whatsoever anyway.

FFmpeg.Autogen is an FFmpeg auto generated unsafe bindings for C#/.NET and Core (Linux, MacOS and Mono).
Underneath uses CppSharp package which generates the C# code which I also use with my custom generator.
FFmpeg.Autogen has the issue with the type sizes and not the ffmpeg itself.
Hope I clarify things for you :)

Ah, yes. autogen.sh is often the script to generate an autotools based build system.
And yeah, there definitely will be type size issues between C# and C/C++ types and structs. Independently of MSVC vs. gcc.

It takes too long to build the docker and compile so until then ...
I suspect this is related with zmq < 4.3.4 hxxps://github.com/zeromq/libzmq/issues/3586

Here is a minimal reproducible example (.NET 8 x64 C#)
using System.Runtime.InteropServices;
using System.Security;

namespace BtbNThreadNamingCrash;

unsafe internal partial class Program
{
    static void Main(string[] args)
    {
        LoadFFmpegLibraries(@"c:\FFmpeg\BtbN\x64");

        var codec = avcodec_find_decoder_by_name("h264");
        var avctx = avcodec_alloc_context3(codec);
        void* dict = null;
        //av_dict_set(&dict, "threads", "1", 0); // success
        av_dict_set(&dict, "threads", "2", 0); // failed
        var ret = avcodec_open2(avctx, null, &dict);

        Thread.Sleep(3000);
        Console.WriteLine("Success");
    }

    public const string AVCODEC    = "avcodec";
    public const string AVDEVICE   = "avdevice";
    public const string AVFILTER   = "avfilter";
    public const string AVFORMAT   = "avformat";
    public const string AVUTIL     = "avutil";
    public const string POSTPROC   = "postproc";
    public const string SWRESAMPLE = "swresample";
    public const string SWSCALE    = "swscale";
    public static Dictionary<string, nint> libToPtr = [];

    public static void LoadFFmpegLibraries(string ffmpegPath)
    {
        var files = Directory.GetFiles(ffmpegPath, $"{AVUTIL}*.dll");
        libToPtr[AVUTIL] = LoadLibraryW(files[0]);

        files = Directory.GetFiles(ffmpegPath, $"{SWSCALE}*.dll");
        libToPtr[SWSCALE] = LoadLibraryW(files[0]);

        files = Directory.GetFiles(ffmpegPath, $"{SWRESAMPLE}*.dll");
        libToPtr[SWRESAMPLE] = LoadLibraryW(files[0]);

        files = Directory.GetFiles(ffmpegPath, $"{POSTPROC}*.dll");
        libToPtr[POSTPROC] = LoadLibraryW(files[0]);

        files = Directory.GetFiles(ffmpegPath, $"{AVCODEC}*.dll");
        libToPtr[AVCODEC] = LoadLibraryW(files[0]);

        files = Directory.GetFiles(ffmpegPath, $"{AVFORMAT}*.dll");
        libToPtr[AVFORMAT] = LoadLibraryW(files[0]);

        files = Directory.GetFiles(ffmpegPath, $"{AVFILTER}*.dll");
        libToPtr[AVFILTER] = LoadLibraryW(files[0]);

        files = Directory.GetFiles(ffmpegPath, $"{AVDEVICE}*.dll");
        libToPtr[AVDEVICE] = LoadLibraryW(files[0]);

        NativeLibrary.SetDllImportResolver(typeof(Program).Assembly, DllImportResolver);
    }

    private static IntPtr DllImportResolver(string libraryName, System.Reflection.Assembly assembly, DllImportSearchPath? searchPath)
    {
        libToPtr.TryGetValue(libraryName, out var ptr);

        return ptr;
    }

    [DllImport("kernel32", ExactSpelling = true, CharSet = CharSet.Unicode, SetLastError = true), SuppressUnmanagedCodeSecurity]
    public static extern IntPtr LoadLibraryW(string dllToLoad);

    [DllImport(AVCODEC, CallingConvention = CallingConvention.Cdecl, ExactSpelling = true), SuppressUnmanagedCodeSecurity]
    public static extern void* avcodec_alloc_context3(void* codec);

    [DllImport(AVCODEC, CallingConvention = CallingConvention.Cdecl, ExactSpelling = true), SuppressUnmanagedCodeSecurity]
    public static extern int avcodec_open2(void* avctx, void* codec, void** options);

    [DllImport(AVCODEC, CallingConvention = CallingConvention.Cdecl, ExactSpelling = true), SuppressUnmanagedCodeSecurity]
    public static extern void* avcodec_find_decoder_by_name([MarshalAs(UnmanagedType.LPUTF8Str)] string name);

    [DllImport(AVUTIL, CallingConvention = CallingConvention.Cdecl, ExactSpelling = true), SuppressUnmanagedCodeSecurity]
    public static extern int av_dict_set(void** pm, [MarshalAs(UnmanagedType.LPUTF8Str)] string key, [MarshalAs(UnmanagedType.LPUTF8Str)] string value, int flags);
}

BtbNThreadNamingCrash.zip
Quick VS solution zip

This doesn't seem like an issue with the builds to me still. Or I'm not sure what you're asking from me.
I can't help you with the usage of third party wrappers. So unless you can point out a specific issue with these builds, I'll close this ticket.

There are a lot of people using FFmpeg libraries with .NET bindings that they have this issue and they don't even know it.
I'm pretty sure I've provided enough information, so you can see that the issue is with your builds as it does not happen with Gyan's builds (just run the project I've attached). I've even provided a workaround by downgrading MinGW (couldn't investigate this further, at least for now).
The issue is critical and you should leave it open, even if you don't care, so other people will be informed and possible contribute resolving this.

I don't doubt that there is an issue. But I have no experience with the .NET bindings and their inner working, or developing with C# native bindings in general.
So I can't debug this further. And from "it doesn't work" I can't really deduce any possible issue.
I generally don't understand what issue you are trying to point to. What does the thread name have to do with it? If the C# bindings crash depending on a thread name, that looks like a bug in the bindings to me?

MS - Tips for debugging threads
I'm not sure what exactly happens, if it thinks that there is a debugger attached or doesn't check at all so even at release mode it throws that exception and the app crashes. It is also possible that FFmpeg should catch that exception, but I think probably the issue is down to mingw. Not even sure if you could 'configure' the threading from your builds (eg. you have some configs for pthreads/winpthreads)


feat: add new style documentStyle for match-document-filename rule

related https://github.com/dotansimha/graphql-eslint/issues/919

@B2o5T still a draft?

@dotansimha will rename documentStyle to matchDocumentStyle and merge


Add Django 2.1 to tox

Problem
With the release of Django 2.1, the model argument is removed from DeferredAttribute, breaking FieldTracker when used with a defer call. However, this only applies to the 3.1.2 release - the changes in master work fine with Django 2.1.
Can you cut a new release so that we have Django 2.1 support?
Solution
This adds Django 2.1 to tox.
Traceback (most recent call last):
  File "/Users/robertmarchman/doc-trips/fyt/core/tests/tests.py", line 33, in test_model_name_lower
    triptemplate = TripTemplate.objects.defer('name').get()
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/django/db/models/query.py", line 393, in get
    num = len(clone)
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/django/db/models/query.py", line 250, in __len__
    self._fetch_all()
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/django/db/models/query.py", line 1183, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/django/db/models/query.py", line 64, in __iter__
    obj = model_cls.from_db(db, init_list, row[model_fields_start:model_fields_end])
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/django/db/models/base.py", line 496, in from_db
    new = cls(*values)
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/django/db/models/base.py", line 486, in __init__
    post_init.send(sender=cls, instance=self)
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 175, in send
    for receiver in self._live_receivers(sender)
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 175, in <listcomp>
    for receiver in self._live_receivers(sender)
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/model_utils/tracker.py", line 163, in initialize_tracker
    tracker = self.tracker_class(instance, self.fields, self.field_map)
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/model_utils/tracker.py", line 37, in __init__
    self.init_deferred_fields()
  File "/Users/robertmarchman/doc-trips/venv/lib/python3.6/site-packages/model_utils/tracker.py", line 112, in init_deferred_fields
    field_obj.field_name, None)
TypeError: __init__() takes 2 positional arguments but 3 were given

Environment

Django Model Utils version: 3.1.2
Django version: 2.1
Python version: 3.6.1

Any chance of a new release? Django 2.1 support would be great...

Hi @auvipy, it looks like Travis calls tox directly so nothing needs to be updated there.


[Sluggable] Unique feature slow...

I was going to use the unique feature, but realized it does a select on all the data.  My data will be user generated and have over 3 million users.. so there's going to be duplicate title posts.
Why not do orderBy slug desc and setMaxResults(1) for people with this use-case instead of:
SELECT slug FROM post p WHERE p.slug LIKE 'my-slug%'

interesting idea, I'll check that

Awesome.  Let me know! :)

hm, theres an issue in your proposed way. if slug is like test 6767 theres no way to match slug index. It was implemented in this way in the begining. The problem was having same slug persisted with a number ending, which is treated like slug index.
And another thing is that you should have unique index on unique slug. This way it will be much faster to retrieve it. Considering your proposition, you would introduce order by. which would do worse, it would scan whole table to get those similar slugs + create temp table to sort them + take 1 row in result. So processing even 1000 similar slugs in php is much faster.

Yeah, I just set it so that my slugs can be duplicated and am appending the ID to the end of the url.... some-slug-123.


Stackful coroutines required for general-purpose callback adapter

Hey guys,
I was looking into converting some callback based native code into a more convenient front-end using co-routines, and was disappointed to learn that I cannot.
Some example code here
Specifically:
private val inputs = generate<InputVector> {
  PretendFortran.INSTANCE.__FANCY_NATIVE_SYNTAX { input ->
    yield(input) //compiler error:
    //suspension functions can be called only within a coroutine block
  }
}.iterator()

It is worth mentioning that this problem generalizes to
enterCoRoutine{
  someType.functionWithCallback {
    suspendFunctionCall();
  }
}

where functionWithCallback is not tagged with inline (for example because all provided implementations of map are inline, the code someListOfWorkloads.map { await(it.workload) } will work just fine).
So after poking around, I believe the issue is that kotlin coroutines are stackless (this should make it evident to you that I am no expert in coroutine implementations).

Why was this design decision made?
Does anybody else have a use case similar to mine?
Is it work asking the implementors to re-implement with some stack tracing procedures to support the general use case of writing an adapter to convert a callback based system into a more regular interface?

It is worth mentioning that this adapter can be implemented with good old Threads and java.ultil.concurrent if you're willing to use multiple threads and a blocking queue. The cons of course to this strategy are all of the problems associated with locks and threads.
I would love to try and implement this with some kind of mark-stack & restore-stack functionality, wherein the state machine would keep track of an extra field, a List<StackFrame>. A call to a Continuation.resume would first mark the current frame in the callstack, then push each of the fields stack frames onto the callstack, and then enter state-machine switch. A call to a suspend fun would save everything between the current stack frame and the mark made on the call stack to the local field, then jump (across function boundaries) to the state machine's exit statement.
I also don't even know if jbc has access to the kind of verbiage needed to manipulate the callstack like this. To a running jitter --or even static bytecode verifiyer-- this kind of code is going to look awfully suspicious.
I have no idea how this impacts the existing try-finally logic, probably tragically. I also have no idea how to synchronize this for multhreading, that's also probably fairly tragic. I also have no idea how this impacts serializability, probably tragically.

This is a duplicate of #34 and #35. oops.


Add cluster info into GetPluginInfoResponse manifest output

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
we return Name and VendorVersion into GetPluginInfo,
add cluster info would be better
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

openstack-cloud-controller-manager version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

/assign


add/remove multiple toolchains

Teaches the toolchain subcommand to accept multiple arguments for toolchains to add or remove.
Depends on #968.

Thanks @durka can you add test cases? I think there are test cases to crib off of in cli-v2.rs, and the tests can go in that file as well.

Tests added. I didn't run them locally 'cause I have no idea how, so wait for CI.

@bors r+

:pushpin: Commit a807244 has been approved by brson

:hourglass: Testing commit a807244 with merge 02d1b87...

:sunny: Test successful - status-appveyor, status-travis
Approved by: brson
Pushing 02d1b87ae1ecd20d38bfe3481ea393f0764e6635 to master...


Problems on install SQLops on CentOS 7

SQL Operations Studio Version:

Steps to Reproduce:
the error message is : file not support ?
I have install SQL Server 2017 without any problems, but I cannot be able to install SQLOPS version 0.29.3 and i don know why.
Someone could give me helps because i am a beginner on Linux world.
Best regards,
LS

@lafs0501 have you tried the RPM installation instructions at https://docs.microsoft.com/en-us/sql/sql-operations-studio/download?view=sql-server-2017.  That is the easiest way to install on CentOS, though the tar.gz installation also should work.

@lafs0501 there are instructions for installing from tar.gz in the above docs links.  Please let me know if those steps are unclear.

@lafs0501 please let me know if you still are having issues installing on Linux.  I'll close this issue for now since there aren't recent updates.

Hello Karl,
I apologize for answering you just now.
Your reply solve the problem.
Best regards,
Luís Santos
Obter o Outlook para Androidhttps://aka.ms/ghei36

From: Karl Burtram<EMAIL_ADDRESS>Sent: Tuesday, June 5, 2018 6:34:02 PM
To: Microsoft/sqlopsstudio
Cc: lafs0501; Mention
Subject: Re: [Microsoft/sqlopsstudio] Problems on install SQLops on CentOS 7 (#1411)
Closed #1411https://github.com/Microsoft/sqlopsstudio/issues/1411.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/sqlopsstudio/issues/1411#event-1664305291, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Alev6FKMyk9jMZRwViZzebLsO1Vs61VFks5t5sEKgaJpZM4T_WZz.


Correct "nanonseconds" to "nanoseconds"

The word "nanoseconds" is misspelled in two places in the spec. This PR corrects both misspellings.

the spec.emu (the source) already correct that. Somehow the index.html is not automatically build and sync with that.

This PR is no longer needed after I land https://github.com/tc39/proposal-intl-duration-format/commit/03a4d11bb6a94bd6f69c9d02368e38fc211a38f2 since it now automatically sync the spec.emu to the index.html


Replace GSON with Moshi

Moshi is smaller and makes use of Okio (which is required by OkHttp anyway), thus final shaded jar would be smaller.

using moshi for the mojang api wrapper as a proof of concept


Observations/Identify Project filter does not accept Project IDs

When using Filters on the Observations or Identify page, the Project filter does not accept Project IDs.  On both of those pages, I  entered the Project ID 6810 and clicked the Update Search button and no filter was applied to the page.

Those are intended to be text searches on the project title, not the ID:

We either need to change the placeholder text or support Simon's request, b/c the placeholder definitely says you can enter an ID. I don't really care one way or the other since autocomplete basically solves the problem, but I think the original intent was to support IDs.

Oh shoot - your right - I didn't notice the placeholder text

I don't have strong preferences about:

changing placeholder text
or
adding IDs

Since 1 seems easier, unless there's a strong desire for 2 my preference would be to go with 1

Agreed that easiest mode is to change placeholder text to only include URL
slug.
Simon Kingston
Data Ranger
National Park Service
Natural Resource Stewardship and Science
Inventory & Monitoring Division
1201 Oakridge Drive, Suite 150
Fort Collins, CO 80525
970-225-3551 ph
970-225-3597 fax
iNaturalist profile: http://www.inaturalist.org/users/forester93
I stand for enthusiastic discovery in myself and others.
https://www.nps.gov/subjects/biodiversity/national-parks-bioblitz.htm
On Tue, Jun 7, 2016 at 3:16 PM, Scott Loarie<EMAIL_ADDRESS>wrote:

I don't have strong preferences about:

changing placeholder text
or
adding IDs

Since 1 seems easier, unless there's a strong desire for 2 my preference
would be to go with 1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/inaturalist/inaturalist/issues/997#issuecomment-224416975,
or mute the thread
https://github.com/notifications/unsubscribe/AGnFGgdLqF3GoQfgVfpIlxOAcHvZn_B_ks5qJd-bgaJpZM4IwSUW
.


increase float size to avoid some overflow error

resolves #11

Thanks! Merging now, pypi and conda will be updated in the next couple hours.


Fedora version?

Not really a bug report, but I'd love to see a Fedora version, so I can use it.

@danPixl Any chance you are capable of packaging for Fedora? Happy to pay a nice bounty for this.

Marking as feature-request and closing.


Add note about updating PowerShellGet module

Hello,
I was trying to use Powershell commands to connect and restore backups but it turned out that I was not able to download the prerelease version of ServiceFabric PowerShell module. After long research, I found I had to update the PowerShellGet module. The information about that was in in GitHub docs. Please add that note :)
Best regards

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

ID: 3f2bc356-6903-4a75-4c60-2888595afead
Version Independent ID: f993726e-375d-3f34-6423-957fa9273aa5
Content: Periodic backup and restore in Azure Service Fabric - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-backuprestoreservice-quickstart-azurecluster.md
Service: service-fabric
GitHub Login: @erikadoyle
Microsoft Alias: edoyle

@devmonte
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@erikadoyle
Can you please check and add your comments on this doc update request as applicable.


Check if uv get "extra stretch" before delete point

Rare case but on some models, simplification lead to UV artefacts : UVs are getting fully streched (same value on both vertices) when many other triangles could have been optimized instead, I suggest to give a lower priority to simplify/remove vertices/faces of the mesh leading to these results.
It might also be a bug in the way the uvs get re-assigned.
The model used to illustrate this example :
https://www.dropbox.com/scl/fi/po761ykdiqdmtbzd9fitf/rhino.glb?rlkey=s6jp06vtr4id0opnv76wwys1p&dl=0
Before simplify :

After simplify :

Are UVs mirrored here? If so then yeah it’s a known issue atm, and will get addressed eventually.


Update diagram-generator to work with pandoc-crossref

This change allows filters like pandoc-crossref and pandoc-fignos to reference the figure number created by diagram-generator.

Good idea, thanks!

Did anyone notice a problem with this since pandoc v3? My refs to diagrams are now broken.


fix: large requests with Caddy

This fix ensures that the request body buffer is full (if possible) before copying it to C memory.
Thanks to @francislavoie for pointing me to https://github.com/caddyserver/caddy/pull/5461, which revealed the bug.
Close #182.

This means you're buffering the whole request in memory? Or will it properly stream?

No, it still streams (we have a test for that). We don't buffer the whole request but wait for the buffer provided by PHP to be full (which is a bit larger than the buffer you use in Caddy by default).

Oh I see, so you just had to pump r.Body.Read until it reaches countBytes (or EOF) which is PHP's buffer instead of only calling r.Body.Read once which would return too few bytes, and PHP will call go_read_post again if it wants more. I think I get it. :+1:

@francislavoie Yes exactly, Go's approach is better (you don't have to wait), but we have no choice here, PHP forces our hand.


"Try connecting you device again" on Windows 10/11 with firmware 3

I recompiled the firmware to change the keymap on my 360 pro. I followed the instructions in the manual. The keyboard works fine when I plug it in my pc, I can see also that the mapping was successfully changed.
However, I can no longer connect my keyboard to my PC using bluetooth. I tried clearing all the profiles on the keyboard and I deleted the device from my Windows 10 PC (where it was paired before the firmware upgrade). I tried to connect it to another PC (Windows 11) where the keyboard had never been connected before. On both PC, I get this error after a few seconds of the pairing attempt:
Try connecting you device again
I tried to connect the keyboard to my iPhone and it worked.
What can I do to make my keyboard work with Windows again?

Have you ensured you're using a different bluetooth profile for each device?

Have you ensured you're using a different bluetooth profile for each device?

Yes, and I tried several profiles on Windows, they all failed to connect.

The board will reject the connection if the host device was paired to another profile. It might be worth clearing every profile on the device even if the light is fast flashing

I cleared all the profiles and tried again, same behaviour. Have you guys tested Windows with the latest firmware?

Yes, every update is tested on a windows, macOS and Linux computer.
Please try performing a settings reset using the guide linked here: https://kinesis-ergo.com/wp-content/uploads/Advantage360-Professional-Settings-Reset-Instructions-11.22.23-KB360-PRO-GBR.pdf

Thank you for the procedure. I did the reset and then proceeded to upload my firmware. Same issue as before, Windows attempts to connect and the message "Try connecting you device again" appears after a few seconds. They light continues flashing rapidly on the keyboard until it sleeps.

Does your computer have an intel wireless card? This could cause the problem
We've worked on a new beta firmware with changes to improve device compatibility, please find it attached.
360pro-beta-1-6-24.zip
If you'd be able to test this and provide feedback, it would be much appreciated

Hi, both of my PCs have Intel bluetooth chipsets. I tried the firmware you provided and it worked immediately. Thank you.
Is there any way I can customize this beta firmware? My key mapping is a bit different than the stock version.

You can solve this problem for the time being by putting these lines into your _defconfig files
https://github.com/KinesisCorporation/Adv360-Pro-ZMK/issues/278#issuecomment-1858876955

I added the lines mentioned in #278 to my config and it worked. Thank you so much for helping me fix this.

Thanks for your patience!


ARXIVNG-1210: miscellaneous bugfixes

This PR addresses a number of bugs surfaced while testing 100K random papers on beta.arxiv.org in batch:

handle the case where a versioned (not latest) .abs file does not include a "Categories:" field
handle the case where submitter name is not provided
change default encoding to latin-1 when opening .abs files
add missing proxy section to version history display
minor fix to author parsing

I added test data (.abs files) for all of these. This branch is currently active on beta.arxiv.org.

Pull Request Test Coverage Report for Build 266

24 of 26 (92.31%)  changed or added relevant lines in 4 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 84.077%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

browse/services/document/metadata.py
14
16
87.5%

Files with Coverage Reduction
New Missed Lines
%

browse/services/document/metadata.py
2
81.76%

Totals

Change from base Build 250:
-0.01%

Covered Lines:
2677

Relevant Lines:
3184

💛  - Coveralls

@bbarker the testing I'm referring to here is independent of the comparison script. The batch testing is meant to reveal error conditions in the form of HTTP exceptions (i.e. 500 errors). I have a simple one-liner that leverages parallel and curl; I'm running this against batches of 100K versioned IDs at a time, making requests like https://beta.arxiv.org/ng/abs/


Add the examples as test cases

This avoids them going out of date.

#43 adds a test for claws::inject_self


Update changelog for v1.15.0

Signed-off-by: Juraci Paixão Kröhling<EMAIL_ADDRESS>

Merging without a review, as it's weekend and I'm not available next week.


Refactor and test concrete 0.0.7

wtf is this

it's babyswarm

oh

can you test it?

lmao I thought this was concrete

install this branch kent/diamant-hackathon
run uv sync

then run this command
uv run python -m structure.tools.poc

from root

ayy, looks good


Choosing the Access Token Type

Hi, I am actually confused about choosing the Access token Type for the client. From the documentation I it seems like usually the Access token comes in two flavors (1. JWT 2. Reference ), Identity Server defaults to "JWT" so can you provide in detail in which scenarios I need to choose  the Reference  token.
Though JWT is the default choice, I am curious to know under what scenarios I need to choose the Access Token?

Identity server 4 supports two types of AccessTokenType.JWT AccessTokenType.Reference Enums.cs for clients.

A JWT token would be a self-contained access token - it’s a protected data structure with claims and an expiration. Once an API has learned about the key material, it can validate self-contained tokens without needing to communicate with the issuer. This makes JWTs hard to revoke.
When using reference tokens - IdentityServer will store the contents of the token in a data store and will only issue a unique identifier for this token back to the client. The API receiving this reference must then open a back-channel communication to IdentityServer to validate the token.

Above text shamelessly stolen from the documentation Reference Tokens
The basic difference being that the JWT token is validated itself.  Where as the reference token must be validated on the identity server.     Main thing i can see would be that you cant really expire an JWT its good as long as it hasn't expired.  Where as the Reference token i stored on the identity server you could technically remove that causing it to be invalid from one minute to the next.

And people who read them even more shocking 🤯

To be clear, the intent is that the lifetime of access tokens will be very short, say 3 to 5 mins, for any site that is concerned about security. The only reason for a longer lifetime for the access token is to accommodate user experience troubles in completing some action before the token expires.

Different apps have different security requirements based on context. I'd not make blanket statements about how people should do things without understanding all the requirements.

Hi Experts, I have a question which is related to tokens. I have asked same question and got some valuable answers

I am using identity token(JWT) for validating my APIs.  but now i got requirement to make load balancing environment for my application in terms of token usage.

is it possible to store JWT in redis to make it sharable between multiple instances of identity server?

as i heard and received information from one of the chat we cannot store JWT tokens as they wont be having persistence. is it correct ?

one behavior i observed is without storing JWT token at anywhere, I have tested same token in load balancing environment which means same configuration or same issuer for both the identity instances. and it is working fine.

so by default JWT can be load balanced till it expires or we need to store explicitly? if required is it possible to store JWT into redis? if yes can u please suggest on this.

I have used below code some time back but i am able to store all other configuration data but not token.
.AddOperationalStore(options =>
{
options.RedisConnectionString = Configuration["CacheConnectionString"];
options.Db = 7;
options.KeyPrefix = "IdentityToken";
options.ConfigurationOptions = operationalStoreOptions;
              })
              .AddRedisCaching(options =>
              {
                  options.RedisConnectionString = Configuration["CacheConnectionString"];
                  options.Db = 5;
                  options.KeyPrefix = "IdentityRedis";
                  options.ConfigurationOptions = CachingStoreOptions;

              })

Please suggest on this as we are almost close to our release

Advance appreciation and thanks for your kind advice or suggestion on above query .......


Use App Layout with Touchkit components

Hi, I wanto to use DatePicker inside App Layout, it is possivel?.
Thanks.

Never tried it so I cannot tell. This addon was never optimized it for the use with Touchkit but it might still work.
What exactly do you mean by this?

use DatePicker inside App Layout

a DatePicker in the Sliding Menu of the App Layout?
a DatePicker in the App Bar of the App Layout?
a DatePicker inside a View that is presented inside the App Layout?

Hi!, for now, use the DataPicker inside a View... but another options aren't discarded.
Thanks.

Would you mind putting a demo together? I have rather less experiance with Touchkit. I think there will only need to be some CSS necessary to fix eventual issues.

closing due to no response reopen if relevant again


Mapping an array of objects

Hi, There is no example on how its possible to map an array of objects, here is my issue
/X/Client/TestRequest.swift:21:8: Type 'TestRequest' does not conform to protocol 'RequestType'
the issue is that there is no responseFromObject function for arrays
struct TestRequest: XPRequest {
    typealias Response = [LKObject]

    private var page: Int!
    private var perPage: Int!

    var method: HTTPMethod {
        return .GET
    }

   var authenticate: Bool {
       return true
   }

   var path: String {
       return "/api/exps"
   }

   init(page: Int, perPage: Int) {
       self.page = page
       self.perPage = perPage
   }

   var parameters: [String : AnyObject] {
       return ["page": page, "per_page": perPage]
   }

}

Update
I made a wrapper like this
struct PaginatedExperience: Decodable {
    let items: [LKObject]
    static func decode(json: AnyObject) throws -> PaginatedExperience {
        return try PaginatedExperience(items: [LKObject].decode(json))
    }
}

and it works no but its not the best way

This is not an APIKit issue and you can return [LKObject] because that is the typealias of Response. (Are you refering to Himotoki?)

Just implement it in TestRequest:
func responseFromObject(object: AnyObject, URLResponse: NSHTTPURLResponse) -> Response? {
    return try? decodeArray(object)
}

Or https://github.com/Anviking/Decodable?

This might work for Anviking/Decodable:
func responseFromObject(object: AnyObject, URLResponse: NSHTTPURLResponse) -> Response? {
    return try? [LKObject].decode(object)
}

@ikesyo yeah, i use Anviking/Decodable, and that worked, thanks for your help


feature-wip Support hive partition cache

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.75 seconds
load time: 441 seconds
storage size:<PHONE_NUMBER>1 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221110091544_clickbench_pr_43315.html

LGTM


calico-node unable to start if one AZ subnet is down

On a test cluster when doing some testing for resilience purposes we found out that if we disable an AWS AZ subnet to mimic a failure, calico is unable to start a node on a working AWS AZ.
The cluster runs on 3 AWS AZ and when disabling one of the subnets we are unable to scale the cluster on the working remaining 2 AWS AZs until the failed AZ becomes operational again.
Expected Behavior
A newer fresh node on a working AZ should be able to start the calico stack.
Current Behavior
Unable to start the network stack on a fresh node until the node that's on the failed AZ becomes operational again.
Errors:
2023-07-26 19:12:07.526 [ERROR][60] cni-config-monitor/token_watch.go 106: Unable to create token for CNI kubeconfig error=Post "https://<IP_ADDRESS>:443/api/v1/namespaces/calico-system/serviceaccounts/calico-cni-plugin/token": dial tcp <IP_ADDRESS>:443: i/o timeout 2023-07-26 19:12:07.526 [ERROR][60] cni-config-monitor/token_watch.go 130: Failed to update CNI token, retrying... error=Post "https://<IP_ADDRESS>:443/api/v1/namespaces/calico-system/serviceaccounts/calico-cni-plugin/token": dial tcp <IP_ADDRESS>:443: i/o timeout 2023-07-26 19:12:07.539 [ERROR][57] felix/daemon.go 249: Failed to get config from datastore error=Get "https://<IP_ADDRESS>:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp <IP_ADDRESS>:443: i/o timeout 2023-07-26 19:12:07.564 [ERROR][63] status-reporter/discovery.go 199: Unable to get Typha service endpoints from Kubernetes. error=Get "https://<IP_ADDRESS>:443/api/v1/namespaces/calico-system/endpoints/calico-typha": dial tcp <IP_ADDRESS>:443: i/o timeout 2023-07-26 19:12:07.564 [FATAL][63] status-reporter/startsyncerclient.go 49: Typha discovery enabled but discovery failed. error=Get "https://<IP_ADDRESS>:443/api/v1/namespaces/calico-system/endpoints/calico-typha": dial tcp <IP_ADDRESS>:443: i/o timeout
pod events
Normal   Scheduled  22m   default-scheduler  Successfully assigned calico-system/calico-node-psn77 to ip-10-138-11-236.eu-west-2.compute.internal   Normal   Pulled     22m   kubelet            Container image "quay.io/calico/pod2daemon-flexvol:v3.26.0" already present on machine   Normal   Created    22m   kubelet            Created container flexvol-driver   Normal   Started    22m   kubelet            Started container flexvol-driver   Normal   Pulled     22m   kubelet            Container image "quay.io/calico/cni:v3.26.0" already present on machine   Normal   Created    22m   kubelet            Created container install-cni   Normal   Started    22m   kubelet            Started container install-cni   Warning  Unhealthy  22m   kubelet            Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused W0726 19:10:03.593464      18 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.   Warning  Unhealthy  22m  kubelet  Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused W0726 19:10:04.585214      31 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.   Warning  Unhealthy  21m  kubelet  Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused W0726 19:10:11.000953      45 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.   Warning  Unhealthy  21m  kubelet  Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused W0726 19:10:21.005574      59 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.   Normal   Killing    21m  kubelet  Container calico-node failed liveness probe, will be restarted   Warning  Unhealthy  21m  kubelet  Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused W0726 19:10:31.006689      72 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.    It will be removed in a future release.   Normal   Pulled     21m (x2 over 22m)  kubelet  Container image "quay.io/calico/node:v3.26.0" already present on machine   Normal   Started    21m (x2 over 22m)  kubelet  Started container calico-node   Normal   Created    21m (x2 over 22m)  kubelet  Created container calico-node   Warning  Unhealthy  21m                kubelet  Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused W0726 19:10:36.641655      17 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.   Warning  Unhealthy  21m  kubelet  Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused W0726 19:10:37.673517      31 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.   Warning  Unhealthy  21m (x4 over 22m)   kubelet  Liveness probe failed: Get "http://localhost:9099/liveness": dial tcp <IP_ADDRESS>:9099: connect: connection refused   Warning  Unhealthy  17m (x35 over 21m)  kubelet  (combined from similar events): Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 W0726 19:15:01.002831     478 feature_gate.go:241] Setting GA feature gate ServiceInternalTrafficPolicy=true. It will be removed in a future release.
Steps to Reproduce (for bugs)

Assuming you are running an EKS cluster on multi-AZ (subnet). Using AWS FIS create an experiment to fully disable a subnet for a period of time (30 min for example)
Add a newer node to the cluster on an operational AZ

Your Environment

Calico version: 2.36.1
Orchestrator version (e.g. kubernetes, mesos, rkt): EKS 1.27
Operating System and version: EKS ami

Failed to get config from datastore error=Get "https://<IP_ADDRESS>:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp <IP_ADDRESS>:443: i/o timeout 2023-07-26 19:12:07.564

The error seems to be a problem accessing the API server - is the network functioning between the node that Calico is running on and the EKS API server?
Is kube-proxy functioning on those node? This feels likely to be a node networking issue in some capacity.


fix docs

Looks harmless/reasonable.

Thank you for changing the pull request to the master branch, approved.


Infinite Reconnect loop

Description
Producer is stuck in Infinite Reconnect loop.  We have 5 brokers and one topic with 25 partitions.
Each application server runs an instance of the producer which produces messages to the topic .There are total of 5 application servers, so total of 5 instances of the producer. Application servers are load balance.
Our producers(all instances) produce a lot of messages in a day , may be close to 7 million messages. We also use SASL authentication. Recently we ran into issues where producer stopped producing messages and below is what is seen in the logs.

This is a critical issue for us and your help is much appreciated.
How to reproduce
This is the first time I have seen this issue. Not sure how to reproduce it.
Checklist
Please provide the following information:

[ x ] Confluent.Kafka nuget version: 0.11.5
[ x] Apache Kafka version: Confluent Kafka version 4.1.0
[ x] Client configuration:
{"bootstrap.servers", "xxx"},
{"api.version.request", false },
{"message.max.bytes",10000000},
{"queue.buffering.max.messages",2000000 },
{"queue.buffering.max.ms",100 },
{"message.send.max.retries", 3 },
{"broker.version.fallback","0.10.0" },
{ "api.version.fallback.ms", 0 },
{"debug", "protocol,broker,topic,msg" },
{"retry.backoff.ms", 500 },
{"security.protocol", "SASL_PLAINTEXT"},
{"sasl.mechanism", "SCRAM-SHA-256"},
{
"default.topic.config", new Dictionary<string, object>
{
{"acks", "1"},
{"message.timeout.ms", 30000}
}
}
[ x] Operating system: Windows server 2012 R2
[ x] Provide logs (with "debug" : "..." as necessary in configuration)
[ ] Provide broker log excerpts
[ x ] Critical issue

recommend upgrading to 0.11.6 - this smells like the integer overflow bug on Windows that was introduced in 0.11.5 after the clock precision was increased. this was fixed in 0.11.6. if you restart your servers (not just the application process, your servers) and the problem goes away, this is definitely that.

please let me know if this resolves the issue.

@mhowlett , I'll update you by end of the day today. Thank you for the info

@mhowlett , After updgrading to 0.11.6 issue is resolved.  Thank you so much.

good to hear. apologies that this bug got through the cracks. note: following discovery of this bug, we've introduced continuous soak testing of librdkafka clients as a means of catching this sort of bug earlier.


AFT Management fails when running customization pipeline when repositories are named differently from defaults

Bug Description
This bug occurs after AFT was successfully deployed. In the process of vending an account, the account appears to have been successfully vended but the customization pipeline for the newly vended account fails because the role aft-codepipeline-customizations-role expects the customization repositories to end with the suffix aft-*.
`

The service role or action role doesn’t have the permissions required to access the AWS CodeCommit repository
named aws-aft-account-global-customizations. Update the IAM role permissions, and then try again.
Error: User: arn:aws:sts::AFT-MGMT-ACCOUNT-ID:assumed-role/aft-codepipeline-customizations-role/16527-RANDOM-ID
is not authorized to perform: codecommit:GetBranch on resource: arn:aws:codecommit:sa-east-1:AFT-MGMT-ACCOUNT-ID
:aws-aft-account-global-customizations because no identity-based policy allows the codecommit:GetBranch action

To Reproduce
Steps to reproduce the behavior:

Deploy AFT but set customized repository names for your account customizations that does not begin with aft
Try to vend an account
Account will be vended
However, customization pipeline will fail with error above

Expected behavior
The account customization pipeline should run without failing. AFT should handle different repository names gracefully or not offer the option to change the default repository names.
Related Logs
Provide any related logs or error messages to help explain your problem.
Additional context

Hey Isaac, thanks for bringing this to our attention, I imagine it's frustrating to get that far into deployment and have this fail. Looks like the input validation for that prefix got missed. Just to make sure I understand though, is using the aft- prefix a blocker for your use case, or is it just the inconvenience of finding out something's wrong quite late? Either way, I've taken an item into our backlog to add input validation so at least this gets checked up-front.

No not a blocker for me, just frustrating as you mentioned so I'm hoping to spare some other hapless chap by getting it fixed.

@mbuotidem AFT 1.5.0 removes this aft-* prefix requirement, thanks for the call out here!


How do i fix Electron issue. Magic Mirror won't run

Platform --- Raspberry Pi 4
Windows – Linux
Node Version --- 18.4.0
MagicMirror² Version --- 2.19.0
Description --- I have done all the updates and installs and when I try to start the MM I get that message regarding the electron not found
pi@raspberrypi:~/MagicMirror $ npm start

<EMAIL_ADDRESS>start
.\node_modules.bin\electron js\electron.js

sh: 1: .node_modules.binelectron: not found
**I tried to install electron,
pi@raspberrypi:~/MagicMirror $ npm install<EMAIL_ADDRESS>npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16 || ^17' },
npm WARN EBADENGINE   current: { node: 'v18.4.0', npm: '8.12.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16 || ^17' },
npm WARN EBADENGINE   current: { node: 'v18.4.0', npm: '8.12.2' }
npm WARN EBADENGINE }
changed 1 package, and audited 765 packages in 13s
74 packages are looking for funding
run npm fund for details
1 high severity vulnerability
To address all issues (including breaking changes), run:
npm audit fix --force
Run npm audit for details.
**I run the command to force fix and got 3 moderate vulnerabilities. I tired fot force fix those and I am back to 1 high severity vulnerability that needs fixing. And it goes around and around again.
**How do I resolve this. Not sure what to do. I Just want to run my MagicMiror like I used to with all my modules (weather, time pollen count, calendar, new feed, comments and globe).

we are on a later version
npm install<EMAIL_ADDRESS>what version of node do you have?  must be 14 or 16

node 18.4.0
npm 8.12.2
node js 16.15.1

I ran the npm install<EMAIL_ADDRESS>and got
i@raspberrypi:~/MagicMirror $ npm install<EMAIL_ADDRESS>npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16 || ^17' },
npm WARN EBADENGINE   current: { node: 'v18.4.0', npm: '8.12.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16 || ^17' },
npm WARN EBADENGINE   current: { node: 'v18.4.0', npm: '8.12.2' }
npm WARN EBADENGINE }
added 43 packages, removed 58 packages, changed 6 packages, and audited 750 packages in 50s
79 packages are looking for funding
run npm fund for details
3 moderate severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Run npm audit for details.

pi@raspberrypi:~/MagicMirror $ npm audit
npm audit report
got  <11.8.5
Severity: moderate
Got allows a redirect to a UNIX socket - https://github.com/advisories/GHSA-pfrx-2q88-qq97
fix available via npm audit fix --force
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/got
@electron/get  *
Depends on vulnerable versions of got
node_modules/@electron/get
electron  >=7.0.0-beta.1
Depends on vulnerable versions of @electron/get
node_modules/electron
3 moderate severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
pi@raspberrypi:~/MagicMirror $

no idea. I suggest u start over, fresh flash, pi os, 32bit, full, called bullseye (current release)
then use my install script, see
https://github.com/sdetweil/MagicMirror_scripts
it does all the setup and dependency install

So your script will install everything needed (outside the modules and 3rd party modules) to get it going.

correct. get the base up and running. same as manual install would have done... (assuming everything was prepared correctly)


Enhance Keyword Should Exist performance by not looking for possible recommendations

In one project I am working on, they ran into an issue where checks were failing because Robot framework was taking up too much time. Analysis showed that the time was taken by calls to the Built in keyword Keyword should exist. In that particular situation it could take more than a second for a single call to Keyword should exist to return, with an average of 400ms. Anything above 500ms was causing failures.
Further analysis revealed the time to be spend on finding keyword recommendations. Finding these recommendations is a very useful feature when you misspell a keyword during test case development. However, when explicitly checking for a keyword's existence at runtime, the boolean answer suffices. In fact, in the current implementation the recommendations are disposed and not included in the reported failure.
A proposed solution is available in PR#4457.

Makes sense. I wasn't sure should we consider this a bug or enhancement but went with the latter. Either way, this will be included in RF 5.1 and hopefully already in beta 2.

This was fixed in PR #4457 by @JFoederer .


Add support for companion, decls and paramLists

The companion implementation doesn't support going from object -> class, only class -> object, as I haven't yet worked out how to construct a macro that starts from an object and I need to get some sleep.
On the plus side, with this patch, I was able to successfully cross-build Marley(https://github.com/guardian/marley/tree/macro-compat) with this.

Would you like me to merge this as is or wait for the object -> class direction as well.

I'll try and dig into that a bit first.

Okey doke :-)

So, after having had a bit of a dig, I can't find a way to fix that issue. Would a 'Known Issues' section in the README make sense to cover this? Should the macro abort if it find's something it can't add a sensible implementation for?

Did you get an answer from @retronym or @xeno-by on scala/scala?

@milessabin no

I've now got a working implementation from companion object to class. I'm not covering some of the more interesting corner cases covered by the implementation in 2.11 you pointed out, but I'd have no idea how to go about testing those.

Awesome! Many thanks ... merging :-)


Show a different font in the popped activity log when hovering over the original one

Storage Explorer Version: 1.11.1
Build: 20191205.1
Branch: master
Language: Chinese(zh-CN)
Platform/OS: Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer.
Open 'Settings' -> Application (Regional Settings) -> Select '中文(简体)' -> Restart Storage Explorer.
Expand one storage account -> File Shares.
Select one file share and copy it.
Paste it to another account -> Hover over the finished activity log then observe the popped activity log.

Expect Experience:
Show the same font for every character between the original and popped activity logs.
Actual Experience:
Show a different font in the popped activity log.

More Info:
This issue doesn't reproduce in zh-TW.

@craxal

Won't fix. We can't modify the font of tooltips


Add mypy ignore to bi_ci_tests pyproject.toml

To avoid erroneous mypy runner script invoke

@asnytin
Looks like pyproject.toml it is used in test_get_compose_path after all

@asnytin Looks like pyproject.toml it is used in test_get_compose_path after all

My bad, sorry. Reverted and just added mypy ignore to this pyproject.toml.


[WIP] Fixing blurred text

The following changes has been done:

rounding pos and size of layouts children
rounding last scrollview translation values after Animation has been finished

Still not sure about Accordion and TreeView.
Blurring of textures as expected appears only during animations.

Related issue: https://github.com/kivy/kivy/issues/2297#issuecomment-158348811.

@tito, could you look into this?

Seems like a really bad approach to me if it should be the default one mainly because using Animation could cause issues. On the other hand, we could perhaps have a Config/Widget option to have integers for pos only with a big warning?

I'm closing this PR.
It won't work before it break the Animation by forcing everything to be an int. The right resolution of the issue is much harder, like every widget should be pixel-aligned but can animate smoothly.


Use I2C instead of PWM for Lidar Lite v3

This pull request starts Lidar Lite v3 driver on i2c. The new version of Lidar Lite v3 works fine on i2c.

Tested  and works fine. I can see reasonable distance on QGC when SENS_EN_LL40LS=2.

Can this be added to coming stable release?

Will be in release v1.6, thanks a lot!

How would I test this on AERO RTF and PIXHAWK2.1 ? By
just wiring the Lidar Lite V3 into the I2C bus and then set
SENS_EN_LL40LS=2 and look at the analyze widget or is
there a more direct way ?


No module named 'plexapi'

I'm getting this error when trying to run plex-bloat-fix.py

File "C:\Users\lyonz\Documents\plexstuff\plex-bloat-fix.py", line 11, in
from plexapi.server import PlexServer
ModuleNotFoundError: No module named 'plexapi'

Not sure what I'm missing?

Requirements are not installed. Instructions require that you install the requirements.txt
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: Chris @.>
Sent: Monday, January 23, 2023 4:30 PM
To: @.>
Cc: @.***>
Subject: [bullmoose20/Plex-Stuff] No module named 'plexapi' (Issue #15)
I'm getting this error when trying to run plex-bloat-fix.py
File "C:\Users\lyonz\Documents\plexstuff\plex-bloat-fix.py", line 11, in
from plexapi.server import PlexServer
ModuleNotFoundError: No module named 'plexapi'
Not sure what I'm missing?
—
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbullmoose20%2FPlex-Stuff%2Fissues%2F15&data=05|01||b9329c3706344ab3fbcd08dafd891b11|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638101062547977726|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=VrsLi036yq%2BQTGQ%2BNah6RKwlH7fhLRHBoukDnPk4vf4%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAC7XXKIHZGFH4SZDQ7JP4B3WT32AZANCNFSM6AAAAAAUEKVXEY&data=05|01||b9329c3706344ab3fbcd08dafd891b11|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638101062547977726|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=0CmfWLtpXxtKQ0Qgy5QrTY%2BTTR%2Fm3C4Q%2BZ4ycSh2Ik0%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Thank you for that. I've made sure the requirements.txt was run, system showed it was being installed but when I run the command, I still get the same error.

1.3.8 was released


bug export in headless (Doesn't include shader as background)

Tested versions
I have tested versions 4.0 to 4.2 and have encountered this issue since version 4.0. I thought it would be fixed in 4.1, and eventually believed that it would be resolved in 4.2. However, it seems that this bug is not yet known.
System information
HEADLESS linux 20.04 terminal
Issue description
I was able to export and view an image with a background like this:

Keep in mind that I exported it manually, similar to how you would use the editor to export a project with a shader.
Thus, if you are using a desktop, you can still export the web version with a background.
However, when using a headless shell such as GitHub Actions, Docker, or similar, it exports with a black background (essentially, a fully black screen) since it ignores shader or doesn't include the shader.
This seems like a glitch or bug.
Steps to reproduce
You can do it on Raspberry PI, docker, git action or any that uses headless shell without running on the desktop.
Be sure you have the zipped folder here.

cd godot_source
./Godot_v4.2-stable_linux.x86_64 --headless --export-release Web ../html/index.html

View html/* however you like to use. For me, I just use this: https://github.com/pipejakob/godot_web for quickest to test. I have others as well.
Minimal reproduction project (MRP)

We use google drive for now:
https://drive.google.com/file/d/1spqcRV89ZCYGu6vAhKAnzE7hEyQPDMiW/view?usp=sharing

seems like a duplicate of https://github.com/godotengine/godot/issues/66842 - i ran into the same issue last week and with a little bit of searching found this issue. The workaround indeed fixed the sky shader for me on 4.2.1. project -> settings -> turn on advanced -> editor -> export -> uncheck "convert text resources to binary"

Wow! You are right, this is duplicate of that issue!
The workaround you gave me is indeed worked! thank you so much for your time! Closing since the issue exists already


Revisit setting daemon-reload to true by default

We need to revisit setting systemd::daemon_reload to true by default in calls from unit_file.
There may be bugs in Puppet and/or other things that this is currently masking.
Relates to #277
Notes from IRC

16:45 < tvaughan> ewoud: Do you think that daemon-reload should simply be implied no matter what? The only reason I added the parameter was to preseve the current (in my opinion broken) state if someone wanted it for whatever reason
16:50 < ewoud> tvaughan: I think it's a good question - ideally speaking you manage the service with Puppet and then Puppet 6.1.0+ should take care of the daemon-reload is needed - that said, we did find out that cases where you ensure something is absent, that won't work
16:51 < ewoud> also, having a drop in file but not managing the service would break, but I'm not sure why you'd do that (the manual restart in service_limits is still weird and something I'd deprecate)
16:52 < tvaughan> At this point, I know that it works with GDM and NFS (the hard edge cases) so I'd like to get it through and then we can figure out if puppet is broken or something else is going on
16:52 < ewoud> so I do wonder in which other cases it would be needed
16:52 < tvaughan> Both GDM and NFS actually have other auto-spawned items that need to happen in between the file drop and the service
16:52 < ewoud> GDM and NFS on which OSes (and versions)?
16:52 < tvaughan> So, there's systemd magic going on as well
16:52 < tvaughan> EL7 and 8 (and I suspect 9)
16:53 < tvaughan> GDM because we're working around hidepid=2 issues
16:53 < tvaughan> Basically, there are more situations that need the intermediate reload than you might think at first glance.
16:54 < ewoud> I'm questioning if the default should be true or false - false would mean you don't apply a workaround so technically a bit faster but true catches more issues
16:54 < tvaughan> That said, we could disable it by default and have users call it explicitly. That would reduce the execs but leave you scratching your head as to why things aren't working the way you expect
16:54 < tvaughan> (and/or puppet itself isn't doing what it's supposed to)
16:56 < tvaughan> ewoud: The daemon reload execs are fast and (unless you have a TON of dropins) you're really not going to notice

@trevor-vaughan I assume this was resolved by #277? I'm going to close the issue but feel free to reopen it.

@jhoblitt Yes, thank you. Apparently I type badly :-/


candle-flash-attn infinite compile time

When I added candle-flash-attn to my .toml file the build process seems hang on Building [=======================> ] 114/118: candle-flash-attn(build) and the compilation doesn't proceed.
My .toml file is
[package]
name = "occam"
version = "0.1.0"
edition = "2021"

[dependencies]
candle-core = { git = "https://github.com/huggingface/candle.git", version = "0.6", features = ["cuda"] }
candle-flash-attn = { git = "https://github.com/huggingface/candle.git", version = "0.6", features = [] }
candle-nn = { git = "https://github.com/huggingface/candle.git", version = "0.6", features = ["cuda"]}
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
glob = "0.3"
rand = "0.8"
anyhow = "1.0"

Compilation can be very long for the cuda kernels flash attn (and easily runs out of memory too). More than 10 minutes wouldn't be surprising. Do you see anything in top / ps (nvcc, cicc, ...)?
Also you probably want to set the CANDLE_FLASH_ATTN_BUILD_DIR environment variable to something like $HOME/.candle so that the kernel compilation doesn't trigger too often.

Hey, i'm having the same issue here trying to build it. Not sure if i'm missing a trick but when i add "flash-attn" to the features for candle-transformers my editor triggers the build . From here the 32GB of RAM in my system gets maxed out and my desktop just freezes. Is they a work around for this at all?

You may want to reduce the parallelism for your build to work by setting RAYON_NUM_THREADS to an appropriate value, and set CANDLE_FLASH_ATTN_BUILD_DIR as mentioned earlier to avoid recompiling this too often (with this setup you should be able to only get it to compiled once).


chore(package): update ember-source to version 2.14.1

Closes #62

looks like Travis doesn't like this

I wonder whether greenkeeper works for anyone else 😞

hmm, indeed I am very surprised that https://github.com/simplabs/ember-validated-form-buffer/pull/60 passed CI. but then again 0.4.0 (which is what was tested) didn't have the CLI version assertion yet, but 0.4.3 (which is the most recent release fitting our version constraint) has the assertion so semver drift is ultimately the "problem" here. "problem" in quotes because 0.4.0 will not actually work for us unless we update to Babel 6.