Bug when power toys run is remapped to only win key

Microsoft PowerToys version
0.37.2
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
in my case power toys run opens up using "win + space"
so, I used keyboard manager to map "win" key to "win + space"
so now whenever I press the "win" key power toys run comes up
whenever any shortcut with "win" key associated (e.g "win + r") is pressed power toys run appears but also quits when the preferred app opens up
however, the emoji menu "win + ." doesn't work properly, instead of inserting emojis in the text field, the emojis are inserted in power toys run
https://user-images.githubusercontent.com/57803702/118394990-96082380-b665-11eb-839f-a098421be120.mp4
✔ Expected Behavior
emoji menu emojis should be inserted in text field the
❌ Actual Behavior
emoji menu emojis are inserted in power toys run
Other Software
No response

@jh070
this is currently by design.
https://github.com/microsoft/PowerToys/issues/8952 tracks the ability to activate a shortcut only on key up, that would solve your problem.


Node.js  Loaders Team Meeting 2022-01-11

Time
UTC Tue 11-Jan-2022 19:00 (07:00 PM):

Timezone
Date/Time

US / Pacific
Tue 11-Jan-2022 11:00 (11:00 AM)

US / Mountain
Tue 11-Jan-2022 12:00 (12:00 PM)

US / Central
Tue 11-Jan-2022 13:00 (01:00 PM)

US / Eastern
Tue 11-Jan-2022 14:00 (02:00 PM)

EU / Western
Tue 11-Jan-2022 19:00 (07:00 PM)

EU / Central
Tue 11-Jan-2022 20:00 (08:00 PM)

EU / Eastern
Tue 11-Jan-2022 21:00 (09:00 PM)

Moscow
Tue 11-Jan-2022 22:00 (10:00 PM)

Chennai
Wed 12-Jan-2022 00:30 (12:30 AM)

Hangzhou
Wed 12-Jan-2022 03:00 (03:00 AM)

Tokyo
Wed 12-Jan-2022 04:00 (04:00 AM)

Sydney
Wed 12-Jan-2022 06:00 (06:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Loaders Team+Meeting+2022-01-11&iso=20220111T1900
or https://www.wolframalpha.com/input/?i=07PM+UTC%2C+Jan+11%2C+2022+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1sRwDX_6o1mi8mvJm5ZZ21JWxpdRXC1h3AhYrO3UjoJA/edit

Agenda
Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node

esm: implement the getFileSystem hook #41076

nodejs/loaders

Loader chaining while loading loaders #56

Invited

Loaders team: @nodejs/loaders

Observers/Guests
Notes
The agenda comes from issues labelled with loaders-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

link for participants: https://zoom.us/j/97506450082

For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live

https://github.com/nodejs/loaders/pull/59


Attempt to resolve a google issue where the first letter is omitted from motif headings in search results

Link to Ticket
Description of Changes Made

Move the actual heading 1 to a visually hidden h1 tag
Put the motif heading 1 into a paragraph tag hidden from screen readers
Leave other headings with the same markup as previously
Remove an extra unnecessary vendor prefix from the styles

How to Test
View the home page and check the heading one and heading two styles display correctly.
Ensure that the heading one text is output twice, with both a h1 and a p tag. The h1 tag should be visible to screen readers, and the p tag should have the motif styles and be hidden from screen readers.
Screenshots

Expand to see more
Home page heading one showing markup in the inspector

Home page heading two showing markup in the inspector

MR Checklist

[x] Add a description of your pull request and instructions for the reviewer to verify your work.
[x] If your pull request is for a specific ticket, link to it in the description.
[x] Stay on point and keep it small so the merge request can be easily reviewed.
[x] Tests and linting passes.

Unit tests

[ ] Added
[x] Not required

Documentation

[x] Updated build docs
[ ] Updated editor guidelines (https://docs.google.com/document/d/1PAWccdQ4tfaZsrEWmpDhvP3GH5RRmBOARFVp4b-kje8/edit?usp=sharing)
[ ] Updated field spec (https://docs.google.com/spreadsheets/d/1v1yqcSC54Vag4mxmTp8e6ZrnxITqzbjCA4A9XPQdXk8/edit?usp=sharing)
[ ] Not required

Browser testing

[x] I have tested in the following browsers and environments (edit the list as required)

Latest version of Chrome on mac
Latest version of Firefox on mac
Latest version of Safari on mac
Safari on last two versions of iOS
Chrome on last two versions of Android

[ ] Not required

Data protection

[x] Not relevant
[ ] This adds new sources of PII and documents it and modifies Birdbath processors accordingly

Accessibility

[x] Automated WCAG 2.1 tests pass
[x] HTML validation passes
[ ] Manual WCAG 2.1 tests completed
[x] I have tested in a screen reader
[ ] I have tested in high-contrast mode
[ ] Any animations removed for prefers-reduced-motion
[ ] Not required

Sustainability

[ ] Images are optimised and lazy-loading used where appropriate
[ ] SVGs have been optimised
[ ] Perfomance and transfer of data considered
[ ] If JavaScript is needed alternatives have been considered
[x] Not required

Pattern library

[ ] The pattern library component for this template displays correctly, and does not break parent templates
[ ] The styleguide is updated if relevant
[x] Changes are not relevant the pattern library

Thanks @chris-lawton have addressed your feedback - are you happy to approve now?

Thanks @chris-lawton have addressed your feedback - are you happy to approve now?

Yep, looks good. Nice one : )


Finding Research Papers

Search topics that are -

Not very old
Present in Major libraries like IEEE, ACM, AAAI , etc.
Are related to topics

Bayesian Decision Theory
Max Likelihood and Bayesian Parameter Estimation
Nonparametric Techniques
Linear Discriminant

Robust and Sparse Linear Discriminant Analysis via an Alternating Direction Method of Multipliers
In this paper, we propose a robust linear discriminant analysis (RLDA) through Bhattacharyya error bound optimization. RLDA considers a nonconvex problem with the L 1 -norm operation that makes it less sensitive to outliers and noise than the L 2 -norm linear discriminant analysis (LDA). In addition, we extend our RLDA to a sparse model (RSLDA). Both RLDA and RSLDA can extract unbounded numbers of features and avoid the small sample size (SSS) problem, and an alternating direction method of multipliers (ADMM) is used to cope with the nonconvexity in the proposed formulations. Compared with the traditional LDA, our RLDA and RSLDA are more robust to outliers and noise, and RSLDA can obtain sparse discriminant directions. These findings are supported by experiments on artificial data sets as well as human face databases.
https://ieeexplore.ieee.org/abstract/document/8710607

Here's how we can section this:

Background of paper (what has been done/tried, what is current norm)
Problems we want to solve (Number of features, small sample size problem)
Introduction of paper and inspiration of why we chose this paper
Key contributions of paper: Description of RLDA/RSLDA and how they work
Results of contribution: how does RLDA/RSLDA perform (include analysis of results)
Any concluding remarks

To do: Figure where ADMM fits

The paper proposes a robust and sparse variant of Linear Discriminant Analysis (LDA) that can handle outliers and high-dimensional data with sparse feature sets and also uses an Alternating Direction Method of Multipliers (ADMM) algorithm to solve the optimization problem. The proposed method has several potential advantages over traditional LDA approaches. So I think it would be a good choice.

Thanks for the suggestion, @JoeyChor! I agree that this paper covers the requested topics and looks promising. I'm in favor of choosing this paper.

I agree that "Robust and Sparse Linear Discriminant Analysis via an Alternating Direction Method of Multipliers" provides valuable contributions to the field of linear discriminant analysis. RLDA and RSLDA are more robust to outliers and noise than traditional LDA due to the use of L1-norm and ADMM to cope with nonconvexity. The paper's recent publication and presence in major libraries demonstrate its relevance and impact.

Everyone agreed to PCA paper
Robust and Sparse Linear Discriminant Analysis via an Alternating Direction Method of Multipliers
~from IEEE~


Remix Vite cannot run with pnpm on Windows

Reproduction
Clone this repo, then run pnpm i.
Finally, execute pnpm run build in the workspace package.
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
    Memory: 41.94 GB / 79.93 GB
  Binaries:
    Node: 18.12.1 - ~\scoop\apps\volta\current\appdata\tools\image\node\18.12.1\node.EXE
    Yarn: 1.22.18 - ~\scoop\apps\volta\current\appdata\tools\image\yarn\1.22.18\bin\yarn.CMD
    npm: 9.6.1 - ~\scoop\apps\volta\current\appdata\tools\image\npm\9.6.1\bin\npm.CMD
    pnpm: 8.9.0 - ~\scoop\apps\volta\current\appdata\bin\pnpm.EXE
  Browsers:
    Edge: Chromium (119.0.2151.72)
    Internet Explorer: 11.0.22621.1

Used Package Manager
pnpm
Expected Behavior
The project can be built successfully.
Actual Behavior
After executing the command, an error is triggered.
[vite]: Rollup failed to resolve import "/@fsE:\project\node_modules\.pnpm\@remix-run+dev@2.3.1_typescript@5.3.2_vite<EMAIL_ADDRESS>from "virtual:server-entry".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
error during build:
Error: [vite]: Rollup failed to resolve import "/@fsE:\project\node_modules\.pnpm\@remix-run+dev@2.3.1_typescript@5.3.2_vite<EMAIL_ADDRESS>from "virtual:server-entry".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`

After debugging, I temporarily modified the code in node_modules.
I edited the file https://github.com/remix-run/remix/blob/e5d24b4848d7df41e71a260abb868ee94ca6480b/packages/remix-dev/vite/plugin.ts#L94 and added / after @fs, which resolved the issue for me.

@pcattori This is the same error I got that you told me to create an issue on the repo about in discord. You can also reproduce this in Remix Dev Tools:
https://github.com/Code-Forge-Net/Remix-Dev-Tools

clone the repo
npm install
npm run build
npm run dev:vite

I get the same error

I think this is a duplicate of https://github.com/remix-run/remix/issues/7722#issuecomment-1810263774
This is supposed to be fixed by https://github.com/remix-run/remix/pull/8057 but it seems it was not included in v2.3.1 (even though the bot said it's in v2.3.1-pre.1 https://github.com/remix-run/remix/pull/8057#issuecomment-1823204154).
Could you try nightly?

I think this is a duplicate of #7722 (comment) This is supposed to be fixed by #8057 but it seems it was not included in v2.3.1 (even though the bot said it's in v2.3.1-pre.1 #8057 (comment)). Could you try nightly?

I tried the version @remix-run/dev 0.0.0-nightly-6953c3f-20231123 and it worked for me
Thank You

@hi-ogawa also can confirm it works now, sweet, this will speed up my remix dev tools vite plugin development by a ton!


Issue 236

I have added the support for $filter directive in $project. I tried to cover the cases of the documentation and I will carry on to find other cases. If somebody helps me to find new cases it could be amazing.
Anyway I added a new class (ProjectedFilter) in the Project class, following what the other developers did.
I cloned the collection in a temporary collection, I created a query to delete elements in the temporary collection and I subtracted the elements of the temporary collection to the original collection.

many thanks !


use rdMolDraw2D.MolDraw2DCairo when possible in rdkit.Chem.Draw

This was implemented in like 2018
Closing


Link to the newest version of the lib docs

This PR changes the docs.rs link in the readme. The link now links to the newest version of the library by default. Before, it just linked to 0.1.0 which isn't even the new version (now at 0.1.3).

Thanks!

Thanks!


[WIP] Implement Authenticate and Reload

closes #37

http://www.future-shock.net/blog/post/Creating-a-simple-login-in-ASP.NET-Core-2-using-Authentication-and-Authorization-NOT-Identity could help with the simple authentication

Thanks @Meir017 !

Now that I'm thinking about it, it might be easier to create a method on a controller an return 401 if the username and password don't match without getting into the authentication system in aspnetcore.
Not sure about this

Ready to review @Meir017


FIX: Incorrect posts when loading posts near a given post number.

Moneky patch core's method. In an ideal world, we wouldn't have to do this here but TopicView in core does not
yet properly support ordering posts in any other order except by Post#sort_order and several methods in
core's TopicView is strongly tied to the assumption that posts are always ordered by Post#sort_order. Fixing
core is hard and risky so we will just carry this monkey patch instead. There is also a small performance tradeoff
here in the following implementation. In PostgreSQL, we basically have to scan for every single posts in order
to figure out what the "row_number" for each post. From there, we can then properly fetch the window of posts
near a given post number.
Another alternative to this solution here is to rely on Post#sort_order and update the column of all posts
whenever a post is voted on or created in the topic. We basically trade-off voting and post creation performance
for a more efficient read query.

Thank you for the review both @CvX and @pmusaraj :+1:


Sparse PS?(Hybrid Data Structures for Power-Law Words)

It's seems glintlda doesn't support "Hybrid Data Structures for Power-Law Words" which is mentioned in LightLDA. I think some like Sparse ps should be need.

This would be a very interesting direction and I think would increase scalability a lot. But I found that it is challenging to do in a JVM environment because implementing such a sparse datastructure in the JVM causes significant garbage collection overhead. The garbage collector goes from O(1) for a dense primitive array to O(n), where n is usually large enough to cause problems. Other projects such as scala-offheap or scala-native may help in this regard, because they can allocate off-heap which prevents garbage collection overhead. I'd be interested in adding this to glint, but unfortunately don't have much time to work on this right now.

Cheers! I am looking forward.

What do you think if I introduce redis as sparse ps in "Hybrid Data Structures"?


[now-cli] Error after upgrading to 16.3.0

Receive an error message/unable to deploy after upgrading now-cli to version 16.3.0.
Works okay when reverting back to 16.2.0
Details:

Upgrade to 16.3.0 with
npm i -g now@latest

In console, run "now" command
now

Get this error:

Error! ENOENT: no such file or directory, stat 'LOCAL_PATH/mobile/node_modules/.bin/detect-libc'

The 'LOCAL_PATH/mobile' is the directory for a react-native version in the same repo.

Revert back to 16.2.0
npm i -g<EMAIL_ADDRESS>

In console, run "now" command
now

Runs and deploys correctly without errors

I was able to recreate these steps several times.

got the same error with the docz package:
Error! ENOENT: no such file or directory, stat '<LOCAL_PATH>/reusecore/node_modules/.bin/docz'

No issue though with<EMAIL_ADDRESS>

Thanks for reporting this bug!
We released 16.3.1 with several bug fixes.
Can you see if that fixes the issue for you?
If not, could you provide more details or a failing deployment URL? Thanks!

Thanks so much for all you do and the prompt response.
I am getting the same error with 16.3.1.
If I revert back to 16.2.0, it deploys without error (I do notice some red warning messages in the web dashboard build console output). I am PMing you a deployment URL.
Let me know if you need anything else.

Thanks for the update! It seems this is only affecting some machines because I was unable to reproduce but @sophearak was able to reproduce.
We released a fix to the canary channel that should resolve this problem.
Can you try npm i -g now@canary to confirm this this solves your issue? Thanks!

Hi, it worked! Was able to do one deployment with the canary version.
I should have mentioned that my client environment is Ubuntu 16.04 LTS, so probably not the norm. Thanks!!!


Feature/restful burndown chart

In the burndown chart:

[x] If there are no estimate history objects, the page will tell user to create tasks on taskboard.
[x] The chart shows the chart with the estimate history filled between days.
[x] The tasks between today and the estimated end date will be annotated and can be toggled by the checkboxes
[ ] If there is only one estimate history object, or if the estimate history with the latest date has the highest time remaining, the chart will try to use average velocity. The user will be informed that there is not enough data to estimate velocity.

Yknow, 1 out of 4 tasks does not seem very "basically finished to me". Also, I see that you expect that a chart with one estimate history object will somehow produce a velocity when on average (spoilers 0 divided by anything is still 0).

I also see that for the past 2 days, no changes were made to the charts presentation at all. If the chart was already done why didn't you pull request sooner?

pls fix failing tests.

I think the date view looks fine, but the week and month view look off.

Can you make the velocity line a normal line instead of a dashed line? I don't know what you would get from dashed line, it is hard to notice.

I think the date view looks fine, but the week and month view look off.
...
Can you make the velocity line a normal line instead of a dashed line? I don't know what you would get from dashed line, it is hard to notice.

btw are you sure your calling the week velocity? It should not be the same as month

Also

I'm pretty sure you know why this is wrong

wrong

How to recreate?

Is this supposed to be working product?


[ruff] Detect duplicate codes as part of unused-noqa (RUF100)

Summary
Implement duplicate code detection as part of RUF100, mirroring the behavior of flake8-noqa (NQA005) mentioned in #850. The idea to merge the rule into RUF100 was suggested by @MichaReiser https://github.com/astral-sh/ruff/pull/10325#issuecomment-2025535444.
Test Plan
Test cases were added to the fixture.

Given the violations in the ecosystem check (# noqa: PGH001, S307), there is a question of whether duplicates should be detected based on rule (i.e. PGH001 and S307 are the same rule) or code (i.e. PGH001 and S307 are different codes).

Hmm yeah... I think it would make sense to match based on rule, but it's confusing that the diagnostic lists the redirected code (and so, presumedly, the one that should stay).
I'd say let's do the duplicate detection based on code for now. Seems simpler.

Ok I modified it to use the original code. I also had to modify the list of valid codes, to also use the original code for the fix to work. This has the added effect that redirects will no longer be updated. But this might be less confusing behavior for users since codes will no longer be updated to new codes without explanation.
If we want to detect redirects and lint against them, then the user should probably be notified that they are using a redirect.

Could we add a separate "reason" for redirected codes?

Ya I was just thinking about that. Do you want me to do it in this PR, or a separate one?

I'm cool with either, whichever is easier for you.

Ok I will add it to this one

Should redirects be a seperate rule? Technically RUF100 is unused-noqa which isn't strictly true of redirects.

I'm gonna split this to help merge it

@charliermarsh hopefully this should be an easy merge now 😉


CC Deployment Failure

Deploying the company communicator the AppService sync fails,

looking at the sync logs there are several errors shown below
Is anyone having the same problem? Has anyone solved this yet?
Issue.txt
Thank you
npm http GET https://registry.npmjs.org/types/color-hash
npm ERR! Error: 3124:error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:openssl\ssl\s23_clnt.c:602:
npm ERR!
npm ERR!     at CleartextStream._puller (tls.js:501:24)
npm ERR!     at CleartextStream._pull (tls.js:432:19)
npm ERR!     at SecurePair.cycle (tls.js:727:20)
npm ERR!     at EncryptedStream.write (tls.js:130:13)
npm ERR!     at Socket.ondata (stream.js:38:26)
npm ERR!     at Socket.emit (events.js:67:17)
npm ERR!     at TCP.onread (net.js:367:14)
npm ERR!  [Error: 3124:error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:openssl\ssl\s23_clnt.c:602:
npm ERR! ]
npm ERR! You may report this log at:
npm ERR!     http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files (x86)\nodejs\\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "install" "--no-audit"
npm ERR! cwd C:\home\site\repository\Source\CompanyCommunicator\ClientApp
npm ERR! node -v v0.6.20
npm ERR! npm -v 1.1.37
npm ERR! message 3124:error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:openssl\ssl\s23_clnt.c:602:
npm ERR! message

Hi @pgriziotti,
Thanks for raising the query. Please follow the below steps.

Go to azure portal-->Go to resource group(Where the deployment has been done)-->Select  App Service from list of resources

Go to configuration section-->Add the below parameter.
WEBSITE_NPM_DEFAULT_VERSION: 8.19.2

Save it

Then go to deployment center-->Do SYNC again.

Hope it helps.

It works!
Thanks a lot!

Hi  again @pgriziotti ,
Please let us know if you have any queries otherwise we make it to closure.

You can close, Thanks again!


Screenshot not being uploaded

New Issue Checklist

[v] Updated fastlane to the latest version
[v] I have read the Contribution Guidelines

Issue Description
Screenshot image are not uploaded
Complete output when running fastlane, including the stack trace and command used
deliver --username<EMAIL_ADDRESS>--app_identifier $appIdentifier ipa release.ipa --app_icon appIcon --metadata_path fastlane/metadata --screenshots_path fastlane/screenshots/ --skip_binary_upload $skip_binary_upload --skip_screenshots $skip_screenshots --skip_metadata $skip_metadata --force $force --submit_for_review $submit_for_review --automatic_release $automatic_release --app_rating_config_path appRating
14:01:21 [14:01:21]: Login to iTunes Connect<EMAIL_ADDRESS>14:01:25 [14:01:25]: Login successful
14:01:25
14:01:25 +--------------------------------------+-----------------------------+
14:01:25 |                       deliver 1.13.1 Summary                       |
14:01:25 +--------------------------------------+-----------------------------+
14:01:25 | username                             |<EMAIL_ADDRESS>|
14:01:25 | app_identifier                       | come.paybay.windrose        |
14:01:25 | metadata_path                        | fastlane/metadata           |
14:01:25 | screenshots_path                     | fastlane/screenshots/       |
14:01:25 | skip_binary_upload                   | false                       |
14:01:25 | skip_screenshots                     | false                       |
14:01:25 | skip_metadata                        | false                       |
14:01:25 | force                                | true                        |
14:01:25 | submit_for_review                    | true                        |
14:01:25 | automatic_release                    | true                        |
14:01:25 | app_review_information.first_name    | Jenkins10                   |
14:01:25 | app_review_information.last_name     | Jenkins10                   |
14:01:25 | app_review_information.phone_number  | +39<PHONE_NUMBER>              |
14:01:25 | app_review_information.email_address |<EMAIL_ADDRESS>       |
14:01:25 | app_review_information.notes         | Jenkins10Jenkins10Jenkins10 |
14:01:25 | app_review_information.demo_user     | Jenkins10dm                 |
14:01:25 | app_review_information.demo_password | ********                    |
14:01:25 | app_version                          | 2.0.4                       |
14:01:25 | ipa                                  | release.ipa                 |
14:01:25 | dev_portal_team_id                   | CYQRJUG9MR                  |
14:01:25 +--------------------------------------+-----------------------------+
14:01:25
14:01:25 [14:01:25]: Making sure the latest version on iTunes Connect matches '2.0.4' from the ipa file...
14:01:27 [14:01:27]: '2.0.4' is the latest version on iTunes Connect
14:01:27 [14:01:27]: Loading 'fastlane/metadata/it/description.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/it/keywords.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/it/release_notes.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/it/support_url.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/it/marketing_url.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/it/name.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/it/privacy_url.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/copyright.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/primary_category.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/secondary_category.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/primary_first_sub_category.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/primary_second_sub_category.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/secondary_first_sub_category.txt'...
14:01:27 [14:01:27]: Loading 'fastlane/metadata/secondary_second_sub_category.txt'...
14:01:28 [14:01:28]: Activating language it...
14:01:30 [14:01:30]: Uploading metadata to iTunes Connect
14:01:31 [14:01:31]: Successfully uploaded initial set of metadata to iTunes Connect
14:01:32 [14:01:32]: Starting with the upload of screenshots...
14:01:32 [14:01:32]: Successfully uploaded screenshots to iTunes Connect
14:01:34 [14:01:34]: Uploading binary to iTunes Connect
14:01:36 [14:01:36]: Going to upload updated app to iTunes Connect
14:01:36 [14:01:36]: This might take a few minutes, please don't interrupt the script
14:02:54 [14:02:54]: iTunes Transporter successfully finished its job
14:02:54 [14:02:54]: ------------------------------------------------------------------------------------------------------
14:02:54 [14:02:54]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
14:02:54 [14:02:54]: ------------------------------------------------------------------------------------------------------
14:02:54 [14:02:54]: Finished the upload to iTunes Connect
14:02:56 [14:02:56]: Selecting the latest build...
14:02:57 [14:02:57]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:03:32 [14:03:32]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:04:11 [14:04:11]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:04:46 [14:04:46]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:05:18 [14:05:18]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:05:53 [14:05:53]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:06:25 [14:06:25]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:06:57 [14:06:57]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:07:29 [14:07:29]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:08:08 [14:08:08]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:08:08 [14:08:08]:
14:08:08 [14:08:08]: You can tweet: "iTunes Connect #iosprocessingtime 5 minutes"
14:08:44 [14:08:44]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:08:44 [14:08:44]:
14:08:44 [14:08:44]: You can tweet: "iTunes Connect #iosprocessingtime 6 minutes"
14:09:16 [14:09:16]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:09:16 [14:09:16]:
14:09:16 [14:09:16]: You can tweet: "iTunes Connect #iosprocessingtime 6 minutes"
14:09:49 [14:09:49]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:09:49 [14:09:49]:
14:09:49 [14:09:49]: You can tweet: "iTunes Connect #iosprocessingtime 7 minutes"
14:10:21 [14:10:21]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:10:21 [14:10:21]:
14:10:21 [14:10:21]: You can tweet: "iTunes Connect #iosprocessingtime 7 minutes"
14:10:53 [14:10:53]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:10:53 [14:10:53]:
14:10:53 [14:10:53]: You can tweet: "iTunes Connect #iosprocessingtime 8 minutes"
14:11:25 [14:11:25]: Waiting iTunes Connect processing for build 2.0.4 (18)... this might take a while...
14:11:25 [14:11:25]:
14:11:25 [14:11:25]: You can tweet: "iTunes Connect #iosprocessingtime 8 minutes"
14:11:58 [14:11:58]: Selecting build 2.0.4 (18)...
14:11:59 [14:11:59]: Successfully selected build
14:11:59 [14:11:59]: Submitting the app for review...

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Fastfile:
default_platform :ios

platform :ios do

    before_all do
        cocoapods
    end

    desc "Runs all the tests"
        lane :test do
        scan
    end

    desc "Submit a new Beta Build to Apple TestFlight"
    desc "This will also make sure the profile is up to date"
    lane :qualityExt do
        increment_build_number
    end

    desc "Deploy a new version to the App Store"
    lane :release do
        increment_build_number
    end

    after_all do |lane|

    end

    error do |lane, exception|

    end
end

Environment
fastlane version (run fastlane -v): fastlane 1.95.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
screenshots folder structure:
fastlane/screenshots/{
Simulator Screen Shot 14 giu 2016, 17.40.25.png
Simulator Screen Shot 14 giu 2016, 17.41.08.png
Simulator Screen Shot 14 giu 2016, 17.41.36.png
Simulator Screen Shot 14 giu 2016, 17.41.55.png
Simulator Screen Shot 14 giu 2016, 17.42.17.png
Simulator Screen Shot 14 giu 2016, 17.42.42.png
}

Perhaps $skip_screenshots is set to true?

+1


Webpack can load modules recursively

This issue is fixed: https://github.com/webpack/webpack/issues/4959

Fixed and released in 2.0.0, thanks!


python39Full: fix to use Python 3.9 rather than 3.8

Motivation for this change
python39Full was actually providing a build of Python 3.8. Looks like this was a typo when python39 was added in 648152fdb.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thank you!

Backported to 20.03.


Logo

Hi. I am a graphic designer. I would like to volunteer to design a logo for this repository that you can use in the readme file. What do you say?

Hi!
This would be a massive help for us!
Would you like to join out chat on Gitter or message me on my gmail (carlspring@...)?

@batarian71 ,
We're actually actively working on our project's (yet uncommitted) UI. Here's a preview of the UI for our search.

We have some ideas of how it should look like, but we're also open to suggestions.
I look forward to hearing from you! :)


Added missing resolveRootPath method to configmodule

Added missing method #76

Pull Request Test Coverage Report for Build 210

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 97.101%

Totals

Change from base Build 208:
0.03%

Covered Lines:
151

Relevant Lines:
151

💛  - Coveralls

Pull Request Test Coverage Report for Build 210

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 97.101%

Totals

Change from base Build 208:
0.03%

Covered Lines:
151

Relevant Lines:
151

💛  - Coveralls

Pull Request Test Coverage Report for Build 210

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 97.101%

Totals

Change from base Build 208:
0.03%

Covered Lines:
151

Relevant Lines:
151

💛  - Coveralls


Issue trying to using ${option.values}

Hello,
I'm Jonathan from Rundeck support. I wanna report a wrong behaviour on this plugin using Rundeck 3 (latest 3.0.22) which is not taking the $[option.values} to be used as POST with webhook json plugin. Please advice.
e.g.
POST /ob/?ExecutionID=393555&EventID=${option.eventid}&ExecutionStatus=success HTTP/1.1
Content-Type: application/json
User-Agent: Java/1.8.0_121
Host: api.company.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 5965

.....

","notif_email":"hidden@email","git_branch":"master","ansible_ssh_user":"ansible","ansible_vault":"W %$(HrV$\u003e","playbook":"site.yaml"}}},"trigger":"success","config":{"webhookURL":"https://api.company.com/ob/?ExecutionID\u003d393555\u0026EventID\u003d${option.eventid}\u0026ExecutionStatus\u003dsuccess"}}

@G3NSVRV
Thanks for your report! I'll check if it could be fixed 👀

@G3NSVRV
Hmm... 🤔
It seems that the parse of option values works well in version 3.0.23-20190619.
Webhook URL:

Option values:

Webhook request dump:
--> POST /?id=212a4997-31f1-442b-bb42-df5422b78acf&val1=bar&val2=1234 HTTP/1.1
--> Content-Type: application/json
--> User-Agent: Java/1.8.0_191
--> Host: <IP_ADDRESS>:3000
--> Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
--> Connection: keep-alive
--> Content-Length: 1237
-->
-->
[socket#17] event: data
--> {"execution":{"id":21,"href":"http://<IP_ADDRESS>:4440/project/test01/execution/follow/21","status":"running","user":"admin","dateStarted":"Aug 3, 2019 10:02:33 AM","dateStartedUnixtime":1564826553990,"dateStartedW3c":"2019-08-03T10:02:33Z","description":"","argstring":"-val1 bar -val2 1234","project":"test01","loglevel":"INFO","job":{"id":"212a4997-31f1-442b-bb42-df5422b78acf","href":"http://<IP_ADDRESS>:4440/project/test01/job/show/212a4997-31f1-442b-bb42-df5422b78acf","name":"test1","group":"","schedule":"","project":"test01","description":"","averageDuration":1601},"context":{"globals":{},"job":{"successOnEmptyNodeFilter":"false","executionType":"user","wasRetry":"false","user.name":"admin","project":"test01","threadcount":"1","url":"http://<IP_ADDRESS>:4440/project/test01/execution/follow/21","execid":"21","serverUUID":"a14bc3e6-75e8-4fe4-a90d-a16dcc976bf6","serverUrl":"http://<IP_ADDRESS>:4440/","loglevel":"INFO","name":"test1","retryInitialExecId":"0","id":"212a4997-31f1-442b-bb42-df5422b78acf","retryAttempt":"0","username":"admin"},"option":{"val2":"1234","val1":"bar"}}},"trigger":"start","config":{"webhookURL":"http://<IP_ADDRESS>:3000/?id\u003d212a4997-31f1-442b-bb42-df5422b78acf\u0026val1\u003dbar\u0026val2\u003d1234"}}

@G3NSVRV
I'll close this issue. Please reopen if you still have problems.


Path level parameters suppress warning on missing requestBody description

This structure correctly causes the warning

Field requestBody for operation post at path /some/path is missing a description

paths:
  /some/path:
    post:
      requestBody:
        # no description here

However, if the path has any path level parameters, the error is not emitted, for example:
paths:
  /some/path/{id}:
    parameters:
      - in: path
        name: id
        type: string
    post:
      requestBody:
        # no description here, but no warning emitted

Nice catch! This should be fixed for sure. Working on it.

Fixed! Thank you for all your contributions and support.


Only show autocomplete in commends

Only show autocomplete in comments but when you are outside at command there are nothing, you don't get any autocomplete at all

Hello,
Example ? Is it a php project managed with composer ?


fix: android build issue

Fixes #1105
Post Mortem:

Added CI for catching build errors on Android

Sorry folks, that was my bad from https://github.com/lottie-react-native/lottie-react-native/pull/1101

Sorry folks, that was my bad from #1101

It's alright. We needed to have CI in place to stop things like this anyway. Between iOS and Android, we are now certain any PR that merges first builds correctly on the target platform now. We needed this anyway.


Remove stacktrace from database errors

Summary
I'm always frustrated when scrolling throw stack trace to my actual errors in database.
#381
Solution
Remove stack trace and keep only database errors.
Before
clickhouse adapter: ClickHouse server does not support exchange tables Database Error
  Code: 1.
  DB::Exception: System call renameat2() is not supported. Stack trace:

  0. DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0xce3f35a in /usr/bin/clickhouse
  1. DB::renameExchange(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x11a385a5 in /usr/bin/clickhouse
  2. DB::DatabaseAtomic::renameTable(std::__1::shared_ptr<DB::Context const>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, DB::IDatabase&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool, bool) @ 0x11a2f0dd in /usr/bin/clickhouse
  3. DB::InterpreterRenameQuery::executeToTables(DB::ASTRenameQuery const&, std::__1::vector<DB::RenameDescription, std::__1::allocator<DB::RenameDescription> > const&, std::__1::map<DB::UniqueTableName, std::__1::unique_ptr<DB::DDLGuard, std::__1::default_delete<DB::DDLGuard> >, std::__1::less<DB::UniqueTableName>, std::__1::allocator<std::__1::pair<DB::UniqueTableName const, std::__1::unique_ptr<DB::DDLGuard, std::__1::default_delete<DB::DDLGuard> > > > >&) @ 0x125ca713 in /usr/bin/clickhouse
  4. DB::InterpreterRenameQuery::execute() @ 0x125c9608 in /usr/bin/clickhouse
  5. ? @ 0x1297956b in /usr/bin/clickhouse
  6. DB::executeQuery(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::shared_ptr<DB::Context>, bool, DB::QueryProcessingStage::Enum) @ 0x1297682d in /usr/bin/clickhouse
  7. DB::TCPHandler::runImpl() @ 0x1353d924 in /usr/bin/clickhouse
  8. DB::TCPHandler::run() @ 0x13551919 in /usr/bin/clickhouse
  9. Poco::Net::TCPServerConnection::start() @ 0x1636236f in /usr/bin/clickhouse
  10. Poco::Net::TCPServerDispatcher::run() @ 0x163646fb in /usr/bin/clickhouse
  11. Poco::PooledThread::run() @ 0x1651ff92 in /usr/bin/clickhouse
  12. Poco::ThreadImpl::runnableEntry(void*) @ 0x1651d71d in /usr/bin/clickhouse
  13. ? @ 0x7fd8e7797609 in ?
  14. clone @ 0x7fd8e76bc133 in ?

After
clickhouse adapter: ClickHouse server does not support exchange tables Database Error
  Code: 1.
  DB::Exception: System call renameat2() is not supported.

Checklist
Delete items not relevant to your PR:

[x] Unit and integration tests covering the common scenarios were added
[x] A human-readable description of the changes was provided to include in CHANGELOG
[ ] For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

Hi @3fonov
Thank you for your contribution!
I'm not sure this behavior would be desired, as we often use the stack trace to investigate CH side issues.
In addition, usually, the error appears right at the beginning of the stack trace, so in what case do you need to scroll to find it? You can just ignore the reset of the lines.
I understand that it might be frustrating for you to have irrelevant text, but it is crucial for many other users.
We would love to get your help with other critical issues in this repo.
Thank you again for your contribution.

@BentsiLeviav added ENV VAR to control behavior and corresponding tests.

Could you please fix the lint issue?

Could you please fix the lint issue?

It seems that it is from file that i didn't touched: tests/integration/adapter/dictionary/test_dictionary.py. Fixed it anyway.

Ohh thanks for that!


ORV2-1368 User Info Wizard for invited users

Description
Please provide a summary of the change and the issue fixed. Please include relevant context. List dependency changes.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have already been accepted and merged

Further comments

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend - Vehicles available
Backend - DOPS available
Frontend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

There is one code smell highlighted by Sonarcloud in LoginRedirect#Line40  because the navigation for it is same as Line 43 in the file. For the sake of code clarity, I'm choosing to not address it as the user redirection needs a lot of supporting comments on which path the application is taking per scenario


Adding Hike to the react native showcase.

About Hike: Hike is India’s first social and technology company. The Hike app is a freeware and cross-platform messaging and Voice over IP (VoIP) service. It also provides snackable content on the go in the form of news, cricket scores, and jokes.
The app was launched on 12/12/12 and acquired a user base of over 100 million in January 2016. In August 2016, Hike raised its fourth round of funding of USD 175 million led by Tencent and Foxconn at a valuation of USD 1.4 billion, making it the fastest company in India to attain a valuation of USD 1 billion, having reached the milestone in just 3.7 years. Investors in Hike include Tencent, Foxconn, Tiger Global, Softbank, and Bharti. Apart from these, some of the top tech veterans from the Silicon Valley have also invested in the company and are advisors.
https://get.hike.in/

Thank you for your contribution, and we appreciate that you enjoy React Native.
Unfortunately, we do not accept any PRs that modify the showcase, the list is now curated by hand.


Undoing creation of a dropped visual shader node results in error

Tested versions
4.3 dev1 and earlier
System information
Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; <IP_ADDRESS>3) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)
Issue description
When you drop a texture to visual shader and undo it, you will get EditorProperty is outside inspector. error.
Steps to reproduce

Create VisualShader
Drag and drop a texture into the shader
Undo

Minimal reproduction project (MRP)
N/A

For me "UndoRedo history mismatch: expected 0, got 2." will pop out when drop a texture into the visual shader too.

So, basically looking into this, in the file editor/plugins/visual_shader_editor_plugin.cpp in the function call _add_node, there are basically 3 add_do_method. The first two are adding nodes on VisualShader and VisualShaderGraphPlugin, and the 3rd one only happens for Textures and add set_texture
The problem with this is in editor/editor_undo_redo_manager.cpp in get_history_id_for_object(Object *p_object) function. The first two methods are not nodes or resources, so the history_id given for them is 0 (Global history I believe).
However the third method is on a resource, so the function gives it a history_id based on whatever scene is currently open (from get_current_edited_scene_history_id()). However, this history_id does not match the one of the first method which is what set the the  pending_action.history_id. This leads to the error flagged in EditorUndoRedoManager::get_history_for_object(Object *p_object) which compares the two ids, and registers the conflict.

So I guess one obvious way to solve this is to split the undoredo action into 2 seperate ones, but that will make user to redo twice to revert the action, maybe not a good idea.
( And it seems the seperation between scene and global history will cause some small errors in some corner cases, maybe we can find a time to check it all? )

The history mismatch is another bug, which already has a pending fix: #79750


RowEditingTemplate Support to create new Rows

Is your feature request related to a problem? Please describe.
I made this on TryMudBlazor, but I can not save it at the moment (Try again later):
@using System.Threading

<MudTable Elevation=10 Items="Movies" Dense=true  Hover=true CommitEditTooltip="Save" OnCommitEditClick=@ApplyChanges>
    <ColGroup>
        <col style="width: 20%;" />
        <col style="width: 20%;"/>
        <col style="width: 50%;" />
        <col style="width: 10%;" />
    </ColGroup>
    <HeaderContent>
        <MudTh>
            RatedR
        </MudTh>
        <MudTh>
            <MudTableSortLabel SortBy="new Func<Movie, object>(b => b.Rating)">Rating</MudTableSortLabel>
        </MudTh>
        <MudTh>
            <MudTableSortLabel SortBy="new Func<Movie, object>(b => b.Name)">Name</MudTableSortLabel>
        </MudTh>
        <MudTh>
            <MudTooltip Text="Create" Placement="Placement.End">
                <MudIconButton<EMAIL_ADDRESS>Color="Color.Tertiary" OnClick="AddMovie"></MudIconButton>
            </MudTooltip>
        </MudTh>
    </HeaderContent>
    <RowTemplate>
        <MudTd DataLabel="RatedR">
            <MudCheckBox<EMAIL_ADDRESS>Color="Color.Error" ></MudCheckBox>
        </MudTd>
        <MudTd DataLabel="Rating">
            @context.Rating
        </MudTd>
        <MudTd DataLabel="Name">
            @context.Name
        </MudTd>
        <MudTd>
            <MudTooltip Text="Delete" Placement="Placement.End">
                <MudIconButton Color="Color.Error" @onclick="@(() => Delete(@context))"<EMAIL_ADDRESS>Size="Size.Small"></MudIconButton>
            </MudTooltip>
        </MudTd>
    </RowTemplate>
    <RowEditingTemplate>
        <MudTd>

            <MudCheckBox<EMAIL_ADDRESS>Color="Color.Error"></MudCheckBox>
        </MudTd>
        <MudTd>
            <MudSelect<EMAIL_ADDRESS>                @foreach (var item in PossibleRatings)
                {
                    <MudSelectItem Value="@item">@item</MudSelectItem>
                }
            </MudSelect>
        </MudTd>
        <MudTd>

            <MudTextField Margin="Margin.Dense" Variant="Variant.Outlined"<EMAIL_ADDRESS>Label="Name of the Movie"/>
        </MudTd>
        <MudTd>

        </MudTd>
    </RowEditingTemplate>
</MudTable>

@code {
    class Movie{
        public int Rating {get; set;}
        public string Name {get; set;}
        public bool RatedR {get; set;}
    }

    private ICollection<Movie> Movies { get; set; }

    private IList<int> PossibleRatings = new List<int>(){
        1,2,3,4,5,6,7,8,9,10
    };

    protected override void OnInitialized()
    {
        Movies = new List<Movie>();
    }

    private EventCallback<ICollection<Movie>> TableChanged { get; set; }

    private void AddMovie()
    {
        var movie = new Movie()
        {
            Name = "",
            RatedR = false
        };
        Movies.Add(movie);
    }

    private async Task Delete(Movie movie)
    {
        Movies.Remove(movie);
        await ApplyChanges();
    }

    private async Task ApplyChanges()
    {
        await TableChanged.InvokeAsync(Movies);
    }
}

Is it possible to Set the row that is added by clicking on the + button as the current edited row?
After I click on it it looks quite good with the MudTextField Variant.Outlined.
Is it possible to align the plus icon, delete icon, and Check icon vertically centered?
When I change the rating to a nullable int, in order to avoid a default value, it breaks my solution.
Describe the solution you'd like
Maybe it is already possible and I just didn´t figure out how to do it.
I would like to be able to change the AddMovie function and set the created movie as the currently edited row without having to manually click on the field.
I think the method is:
public override void SetEditingItem(object item)
I just could not figure out how to call it.
Describe alternatives you've considered
You can have a popup with a form and then enter the data, but I think the solution like in my example is interesting in some situations.

I changed your code, I hope this helps: https://try.mudblazor.com/snippet/cYQFOQbnStjqEIOS

Great, thank you.
I did not know you can access the table this way:
MudTable<Movie> _table;

sorry, this code be not working


Issue #56 fix use of keyid_hash_algorithms in key data

The current implementation of generating multiple key IDs and allowing them to be used is not in line with the spec and opens a security hole, per discussion yesterday with @tedbow

This unresolved PR in TUF may date from when multiple key IDs were allowed for the same key.  I'm guessing this was solving by limiting key ID to only be the sha-256 digest in the spec.
https://github.com/theupdateframework/tuf/commit/1a00d87f454e9294325752e838f9fa50c19d48ff
I guess there is still a weird case that 2 keys could use the same public key with different signature schemes, but that would still require them to have both been added to root.json... maybe a risk for delegated keys?


java.lang.IllegalArgumentException: ONS configuration - Error while adding Oracle DB to Weblogic <IP_ADDRESS>

Hi,
When I try to create a new JDBC connection(Oracle DB) from Weblogic <IP_ADDRESS>, I receive the below error.
Error:
java.lang.IllegalArgumentException: ONS configuration
Docker images used:
container-registry.oracle.com/middleware/weblogic:<IP_ADDRESS>
container-registry.oracle.com/middleware/weblogic:<IP_ADDRESS>-190111
I appreciate any suggestions to resolve it
Thanks

What I did was to modify the config_internal.sh to include -Doracle.jdbc.fanEnabled=false


Add support for Openstack / generic cloud

AlmaLinux needs to provide cloud images compatible with Openstack.
Basic requirements are

qcow2 format (ready for libvirt)
cloud-init with openstack datasource enabled

This is the reason I'm hesitant to offer it to VPS customers. Every major distro offers this. They aren't just useful for OpenStack either, because other clouds can add their cloud-init datasource to the cloud image.
Anything like these would be great: https://docs.openstack.org/image-guide/obtain-images.html

Any feedback is welcome: https://repo.almalinux.org/almalinux/8/cloud/x86_64/images/

Thank you @ezamriy
As a first feedback is that we also need a more stable release than the daily build, so that one can rely on a number like "8.4" instead of "20210616".
I am not sure how AlmaLinux is plannig the release train, but since this issue is closed we need a major release of this image, too.

It is not necessarily a problem, however, if trying to cleanly migrate from CentOS, then net.ifnames=0 should not be set as boot option (https://github.com/AlmaLinux/cloud-images/blob/master/http/almalinux-8.gencloud.ks)
It causes the network interface to be named eth0 under KVM rather than ens3. In my case, where I simply tried to replace the qcow2 I made manually with this one, it failed to come online because my meta-data file for cloud-init contains interface name.
In terms of naming - I have no problem with that, as it is also how CentOS names it and people should be used to that.
However, if one wanted to do something nice it would be to build the image regularly and symlink it from e.g. AlmaLinux-8-GenericCloud-latest.x86_64.qcow2 so that the dnf update when rolling a new vm does not take that long.

@ AlmaLinux team:
Any feedback is welcome: https://repo.almalinux.org/almalinux/8/cloud/x86_64/images/

Thanks for the work put into this!

@fbhdk:
It is not necessarily a problem, however, if trying to cleanly migrate from CentOS, then net.ifnames=0 should not be set as boot option (https://github.com/AlmaLinux/cloud-images/blob/master/http/almalinux-8.gencloud.ks)

Setting it to 0 disables the predictable naming feature (see docs). The difference between eth0 and ens3 thus likely originates from somewhere else, as CentOS also has it disabled in all their images as far as I remember.

Setting it to 0 disables the predictable naming feature (see docs). The difference between eth0 and ens3 thus likely originates from somewhere else, as CentOS also has it disabled in all their images as far as I remember.

You are absolutely right, it is my mistake, I looked at the wrong line when comparing.   Please disregard my comment about interface naming.

Yeah, my goal was creating an image that will be as close to the CentOS one as possible so that people can use it as a drop-in replacement.
The question is only about tooling: at the end I see it as a minimal necessary kickstart file and a set of well documented and tested Ansible roles so that it can be easily used for producing derivatives. Of course it will take some time for refactoring, improving CI and arranging other things.

@mariusleu

As a first feedback is that we also need a more stable release than the daily build, so that one can rely on a number like "8.4" instead of "20210616".

Let me explain the naming scheme, please:
AlmaLinux-8-GenericCloud-8.4-20210616.x86_64.qcow2

* AlmaLinux - distribution name
* 8 - major distribution version
* GenericCloud - image type
* 8.4 - minor distribution version. It will be changed to 8.5 and so on later
* 20210616 - image build timestamp
* x86_64 - architecture
* qcow2 - image format

It doesn't mean that this image is a daily or unstable build, but it clearly indicates when this image has been built and/or updated.

I am not sure how AlmaLinux is plannig the release train, but since this issue is closed we need a major release of this image, too.

We are updating all our cloud/container images due to the following reasons:

security updates available for the packages on an image
fixed a bug reported by the community or our CI which is evolving constantly

Does it mean that such an update turns an image into something beta/unstable state? I don't think so! It just improves the quality and offers the community a secure image out of the box.
But if you are not okay with regularly updates (usually once per month), you can just hold on a specific image version. It's completely up to you :)

Btw, guys, I closed this GH issue because that milestone is achieved. But if you see any bugs/problems with the image, just create another issue and let's work on it.


Showing "put" (extra asterisks appears)

https://docs.microsoft.com/ja-jp/office/vba/access/concepts/miscellaneous/ado-for-visual-c-plus-plus-syntax-index-for-com

@hyoshioka0128 Hi Hiroshi, when you log these issues, is it possible for you to add an Assignee? If so, please add "OfficeGlobal" as an assignee for each issue that you log. Thank you.

@Linda-Editor I understand. (I'm Poor English)
However, Assignees are not displayed at the stage of isssue.

I'm investigating if it can not be done by another method.

@hyoshioka0128 Are you not able to see this in the right navigation?

@Linda-Editor As in the previous screen shot, the right navigation  is not displayed.
Even after pressing 'Submit new issue' button, gear button does not appear.


fix team member remove flake

oh sorry for not thumbing this one, I looked at it before the call and thought it was a good play! thanks


Redirects don't seem to respect target page component's head section (or at least title, specifically)

Subj. I.e. if I have a page pages/index.vue redirecting to /students, and then in pages/students.vue there's head: { title: 'students' }, it's not being taken into account and the actual DOM tree's head section is not updated.

Did you try making the head a method? According to docs the head should a method.
https://nuxtjs.org/api/pages-head/#the-head-method
head () {
  return {
    title: 'students'
  }
}

@Andkoo actually it seems to work now, no matter the function or the object I use. Looks like there were a version bump fixing this.


Invalid JSON in the wiki

The wiki has a small typo in one of its codeblocks, the first json here has a comma after the architecture block.

fixed in revision db8b6c3


Addition of Excel data collection templates back into the repo

In this PR we are accomplishing the following tasks:
Update linkml version to use updated version of gen-excel and add script and Makefile rule to organize generated Excel files based on checklists into a specific folder called mixs-templates at the root of the repo. There is also a README file alongside the folder, documenting the file structure/file content of that folder.
Fixes #725 #724 #631 #685 #714 #395 #360

Merging this in since we went over a demo of what this PR accomplishes on 12/22


ColumnDef types gives typescript error

Describe the bug
Looking at the examples and docs I expect this to correctly type my columns for me. Instead I get a large error with this code:
  type Example = {
    name: string
    age: number
  }

  const columnHelper = createColumnHelper<Example>()

  const columns = useMemo<ColumnDef<Example>[]>(
    () => [
      columnHelper.accessor("name", {
        cell: (info) => info.getValue(),
      }),
      columnHelper.accessor("age", {
        cell: (info) => info.getValue(),
      }),
    ],
    [columnHelper],
  )

Am I doing something wrong here?
Regards Jonathan
Your minimal, reproducible example
https://codesandbox.io/s/typescript-playground-export-forked-iqm265?file=/index.tsx
Steps to reproduce

Create a type with two different types, string and name for example.
Use the createColumnHelper with the type
Define columns with columnHelper and type them with ColumnDef

Expected behavior
I expected the Columdef to correctly type my columns.
How often does this bug happen?
Every time
Screenshots or Videos

Platform
Mac OS
react-table version
v8.5.13
TypeScript version
v4.8.2
Additional context
No response
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Only way I've found to get around this is to add a as string or some other primitive type after info.getValue()

I'm having the same problem, any updates on this?

I m having same, so i fix with
const columns = useMemo<ColumnDef<Example, any>[]>

i don't know if this is the best way, but the typescript error should go away.

We skipped using columnDef, it still works as good and gives type help.
  const columns = [
      columnHelper.accessor("name", {
        cell: (info) => info.getValue(),
      }),
      columnHelper.accessor("age", {
        cell: (info) => info.getValue(),
      }),
    ]

This is the way.

Thank you, it does work this way!

@tannerlinsley if you're saying @Jontii 's solution is the right way, you might want to change the docs for the Column Defs page in the docs to not use a column helper and a typed array.  That is what you're saying right, either use one or the other?

If I understand it, if you use grouped columns like this example https://tanstack.com/table/v8/docs/examples/react/column-sizing then it is correct. If you are not using grouped columns, you shouldn't use it.

You should only be using the column helper and not pre-typing anything.

@tannerlinsley This is the first example in the Column Defs guide page:
// Define your row shape
type Person = {
  firstName: string
  lastName: string
  age: number
  visits: number
  status: string
  progress: number
}

const columnHelper = createColumnHelper<Person>()

// Make some columns!
const defaultColumns: ColumnDef<Person>[] = [  // <- Pre typed Array
  // Display Column
  columnHelper.display({ // <- While using column helper
    id: 'actions',
    cell: props => <RowActions row={props.row} />,
  }),
  // Grouping Column
  columnHelper.group({
    header: 'Name',
    footer: props => props.column.id,
    columns: [
      // Accessor Column
      columnHelper.accessor('firstName', {
        cell: info => info.getValue(),
        footer: props => props.column.id,
      }),
      // Accessor Column
      columnHelper.accessor(row => row.lastName, {
        id: 'lastName',
        cell: info => info.getValue(),
        header: () => Last Name,
        footer: props => props.column.id,
      }),
    ],
  }),
  // ...

It has the column array pre-typed and throws errors if any of these accessor columns are top level.

Yeah… we should fix that.
On Oct 5, 2022 at 11:40 AM -0700, Chris Sandvik @.***>, wrote:

@tannerlinsley This is the first example in the Column Defs guide page:
// Define your row shape
type Person = {
firstName: string
lastName: string
age: number
visits: number
status: string
progress: number
}
const columnHelper = createColumnHelper()
// Make some columns!
const defaultColumns: ColumnDef[] = [  // <- Pre typed Array
// Display Column
columnHelper.display({ // <- While using column helper
id: 'actions',
cell: props => ,
}),
// Grouping Column
columnHelper.group({
header: 'Name',
footer: props => props.column.id,
columns: [
// Accessor Column
columnHelper.accessor('firstName', {
cell: info => info.getValue(),
footer: props => props.column.id,
}),
// Accessor Column
columnHelper.accessor(row => row.lastName, {
id: 'lastName',
cell: info => info.getValue(),
header: () => Last Name,
footer: props => props.column.id,
}),
],
}),
// ...
It has the column array pre-typed and throws errors if any of these accessor columns are top level.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Pre-typing would be helpful for public interfaces e.g. if we create a wrapper components with columns and data props. I am using this here right now:
interface DataTableProps {
  // FIXME: Can we figure out something more type restrictive which actually works?
  data: unknown[]
  columns: ColumnDef<any, any>[];
}

That makes TypeScript "happy"... but I would prefer something more strict.
I guess I was looking for a typed CustomTableComponent example which uses TanStack/Table underneath.

Pre-typing would be helpful for public interfaces e.g. if we create a wrapper components with columns and data props. I am using this here right now:

This! We're making a custom MyTableComponent and expose columns as prop that is pre-typed.

Pre-typing would be helpful for public interfaces e.g. if we create a wrapper components with columns and data props. I am using this here right now:
interface DataTableProps {
  // FIXME: Can we figure out something more type restrictive which actually works?
  data: unknown[]
  columns: ColumnDef<any, any>[];
}

That makes TypeScript "happy"... but I would prefer something more strict.
I guess I was looking for a typed CustomTableComponent example which uses TanStack/Table underneath.

This makes typescript happy IF you allow use of any which my codebase explicitly does not and which TS does not recommend

I am having the same issue here. Is there a way to avoid typing any?
type Props<T> = {
  data: T[];
  columns: ColumnDef<T, any>[];
};

The EditableData example also uses React.useMemo<ColumnDef<Person>[]>(, I guess that's not correct either?

Hey 👋  I there any update on "any" type issue? It seems this thread is no more watched by Tanstack team. Should we create separated issue instead?

I just encountered the same issue, which forced me to turn off no-explicit-any.

Any update on this issue? Running into the same issue. My solution is to use any for the type and individually define the types for each cell:
`
type BillingDetails = {
id: number;
service: string;
talentName: string;
amount: number;
createdAt: string;
};
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const columns: ColumnDef<BillingDetails, any>[] = [
columnHelper.accessor('service', {
id: 'service',
cell: (props) => props.getValue() as string,
header: 'Service',
enableSorting: false,
}),
columnHelper.accessor('talentName', {
id: 'talentName',
cell: (props) => props.getValue() as string,
header: 'Talent name',
enableSorting: false,
}),
columnHelper.accessor('amount', {
id: 'amount',
cell: (props) => props.getValue() as number,
header: 'Amount',
enableSorting: false,
}),
columnHelper.accessor('createdAt', {
id: 'createdAt',
cell: (props) => props.getValue() as string,
header: 'Created at',
enableSorting: false,
}),
`

Getting the same here, trying to convince our team to migrate to @tanstack/react-table and this is certainly getting in the way of that. I've defined columns as such: (nothing revolutionary)
  const columnHelper = createColumnHelper<Coffee>();

  const columns = [
    columnHelper.accessor(data => data.id, {
      id: 'id',
      cell: info => info.getValue()
    })
  ];

and have typed my generic table component as:
interface TableProps<T extends object> {
  data: T[];
  columns: ColumnDef<T>[];
}

export default function index<T extends object>({ columns, data }: TableProps<T>) {
  const table = useReactTable({
    data,
    columns,
    getCoreRowModel: getCoreRowModel()
  });

(...)

But am then getting the following Type Error when passing my columns as a prop:
        Property 'accessorFn' is missing in type 'ColumnDefBase<Coffee, number> & StringHeaderIdentifier' but required in type 'AccessorFnColumnDefBase<Coffee, unknown>'.ts(2322)
types.d.ts(83, 5): 'accessorFn' is declared here.
index.tsx(6, 3): The expected type comes from property 'columns' which is declared here on type 'IntrinsicAttributes & TableProps<Coffee>'

Any advice is appreciated
react-table version: 8.10.7
@types/react-table version: 7.7.18

Yeah getting same issue.

Waiting for the solution of this issue too.

yeah please i really require a solution for this.

Any progress here? Going to have to drop react-table if this isn't fixed, unfortunately.

Any progress here? Going to have to drop react-table if this isn't fixed, unfortunately.

That's very excessive, just put any for the second argument and it'll still work really well.

Can anyone provide a working vue-table example project that passes column info into a table component?
I'm using typescript and getting the following error no matter how I move the types around:
Uncaught (in promise) TypeError: columnDefs2 is undefined

for the time being I just removed the ColumnDef<Example>[] from const columns: ColumnDef<Example>[] = [...] and all worked just fine.
My generic table component have prop columns?: ColumnDef<T, any>[]; and it's also fine.

still waiting for the official fix lol

Downgrade to 8.10.3 and it works.

This still happens only when you have multiple types on your object property
export type User = {
  id: number;
  name: string;
  email: string;
  role: "admin" | "member";
  status: "active" | "pending";
};

// changing everything with type of string fixed the issue but whats the point of using typescript here
export type User = {
  id: string;
  name: string;
  email: string;
  role: string;
  status: string;
};

@swernerx can you get some comments about this issue? Are you planning on fixing this? Please pay special attention to @cameronthrntn comment

What I've done for now to atleast keep the types is use unknown, then assert the type in the cell.
[...]

// Use `unknown` type here
const columns: ColumnDef<unknown>[] = [
  {
    accessorKey: "Person",
    header: "Person",
  },
  {
    accessorKey: "email",
    header: "Email",
  },
  {
    accessorKey: "role",
    header: "Role",
  },
  {
    accessorKey: "status",
    header: "Status",
  },
  {
    id: "actions",
    cell: ({ row }) => {
      // assert type as desired here
      const person = row.original as Person; //


RSpec/LeadingSubject autocorrect causes infinite loop error

I have the following 2 declarations in a long legacy testfile that both cause this error:
  describe 'pending_linkedin_imports' do
    describe(subject { PortfolioLink.pending_linkedin_imports })
   # ...
  end

  # ...

  describe 'AASM' do
    describe(subject { create(:linkedin_portfolio_link, employee: employee) })
    # ...
  end

This is quite the bad syntax tbh but somehow it works and fails the autocorrect.

describe(subject { how does it work?

I'm not sure. Currently getting rid of this confusing code, nevertheless, it does work and causes an error with rubocop-rspec.

This code works roughly as following:
  describe 'pending_linkedin_imports' do
    nonsense = subject { PortfolioLink.pending_linkedin_imports } # most probably `nil`
    describe(nonsense) # empty example group
    # ...
  end

It's a bad code that we have no intention to introduce checks to account for such weird and nonsensical usage.
Thanks for understanding.
Please, next time include error messages and the backtrace of rubocop --debug.


fix(deps): update dependency rxjs to v6.5.5

This PR contains the following updates:

Package
Type
Update
Change

rxjs
dependencies
patch
6.5.4 -> 6.5.5

Release Notes

reactivex/rxjs
v6.5.5
Compare Source

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

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

v5.0.6
GitHub release

Your semantic-release bot :package::rocket:


Decouple program_stats from campaign_stats

Currently the campaign stats view is giving us a count of campaigns for a program, by using ROLLUP. We should instead have a program stats view that counts campaigns (among other things).
It could even join with the the campaign stats view and do aggregates across all the programs campaigns.

This TODO may also be related https://github.com/bikebrigade/dispatch/blob/main/lib/bike_brigade/stats.ex#L171-L173

@sereprz see https://github.com/bikebrigade/dispatch/blob/804f743d32be63ad317af2de2a87c29dcf09751a/priv/repo/sql/campaign_stats_view.sql and especially this diff.
In the diff you see I half solved this ticket - I took out the rollup / campaigns per program count from the view. Now we just don't get the stat from anywhere (that diff comments out displaying program.campaign_count).
I think it would be useful to have a program stats view, but it needs to be scoped out.

This TODO may also be related https://github.com/bikebrigade/dispatch/blob/main/lib/bike_brigade/stats.ex#L171-L173
This was about a different stats view - riders not campaigns. We can scope out an issue here also if/when you have time.


Add special uniqueID to draw_text_scribble*() functions

https://github.com/JujuAdams/Scribble/commit/d2f6d3ebec4b8fbe98b48de283ea6fca8fa51e0b


Error: Unexpected format to the list of available marts.

Hi,
When I was using -g mm10, an error took place like this:
Error: Unexpected format to the list of available marts.
Please check the following URL manually, and try ?listMarts for advice.
http://may2012.archive.ensembl.org:80/biomart/martservice?type=registry&requestid=biomaRt
In addition: Warning message:
Ensembl will soon enforce the use of https.
Ensure the 'host' argument includes "https://"
Execution halted
I tried to change the host path of mm10 in annotation_config.yaml. However, another error took place, as following:
Error in martCheck(mart) :
No dataset selected, please select a dataset first.  You can see the available datasets by using the listDatasets function see ?listDatasets for more information.  Then you should create the Mart object by using the useMart function.  See ?useMart for more information
Calls: Main ... LoadGenomeAnnotation -> GetAnnotations -> getBM -> martCheck
In addition: Warning message:
Ensembl will soon enforce the use of https.
Ensure the 'host' argument includes "https://"
Execution halted
May I get your help? Thank you very much!

Hello willluo123,
the problem is that annotations from oct2018.archive.ensembl.org are not available now.
You can replace line 253 in plot2DO/config/annotation_config.yaml with the value host: https://jan2019.archive.ensembl.org
Please, let me know if it works.
Best,
Paula

Hi Paula,
I replaced the host in the annotation_config.yaml and it works.
Thank you very much!
Best,
Will Luo
| |
罗维翰
|
|
@.***
|
---- Replied Message ----
| From | @.> |
| Date | 3/27/2024 03:06 |
| To | @.> |
| Cc | @.> ,
@.> |
| Subject | Re: [rchereji/plot2DO] Error: Unexpected format to the list of available marts. (Issue #18) |
Hello willluo123,
the problem is that annotations from oct2018.archive.ensembl.org are not available now.
You can replace line 253 in plot2DO/config/annotation_config.yaml with the value host: https://jan2019.archive.ensembl.org
Please, let me know if it works.
Best,
Paula
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Update widget package to different version

Codecov Report

Merging #12168 (79e37e9) into main (9b75af3) will decrease coverage by 0%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            main   #12168    +/-   ##
=======================================
- Coverage     70%      70%    -1%
=======================================
  Files        500      500
  Lines      31621    31621
  Branches    4937     4937
=======================================
- Hits       22251    22142   -109
- Misses      7490     7613   +123
+ Partials    1880     1866    -14

Impacted Files
Coverage Δ

src/platform/common/net/httpClient.ts
44% <0%> (-34%)
:arrow_down:

src/kernels/execution/executionHelpers.ts
33% <0%> (-34%)
:arrow_down:

...c/kernels/execution/cellExecutionMessageHandler.ts
57% <0%> (-22%)
:arrow_down:

src/platform/common/utils/serializers.ts
8% <0%> (-21%)
:arrow_down:

.../notebooks/debugger/debugLocationTrackerFactory.ts
96% <0%> (-4%)
:arrow_down:

...ebooks/controllers/notebookIPyWidgetCoordinator.ts
83% <0%> (-4%)
:arrow_down:

src/kernels/raw/session/rawKernel.node.ts
62% <0%> (-3%)
:arrow_down:

src/kernels/common/baseJupyterSession.ts
79% <0%> (-3%)
:arrow_down:

src/kernels/raw/session/rawSocket.node.ts
73% <0%> (-3%)
:arrow_down:

src/kernels/helpers.ts
71% <0%> (-3%)
:arrow_down:

... and 10 more


Recurring Donations Automatically Being Created

Hi - We have a custom checkbox, sustainer, that is used on the Opportunity object. Checking that box creates a recurring donation for that opportunity (It's backwards). The issue is, over time, more and more recurring donations are created (some with, some without opportunities). Also, instead of creating new opportunities each time a credit card is charged, it is adding transactions to one opportunity, which is incorrect.
We also have a large amount of DLRS fields.  If one of these roll ups edits a recurring donation, what are the effects from NPSP?
Thanks.

Hi @Agroag - as with the other issue you posted, this is best for the Power of Us Hub where the community can help you troubleshoot solutions. This isn't related to NPSP, so I would probably post in the System Administrators group for best results (since it's your customization and DLRS)
As I mentioned in the other thread, we reserve Github issues for items that have been verified as bugs/issue in the code for our developers to address, and not for general troubleshooting. Thanks!


Correction for raw affiliation Department of Surgery, Western University

Correction needed for raw affiliation Department of Surgery, Western University
raw_affiliation_name: Department of Surgery, Western University
new_rors: 02grkyz14
previous_rors: 02agqkc58
works_examples: W4324130371;W4367304795
contact: 8eb5591c3691d81f6cebb8526233030b:c58955d5ab036756 @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-21. The new affiliations should be visible within the next 7 days.


Hardcoded source IP

I am running your tool on a 10.0.x.x network and the source IP in both wireshark and your tool state that is sourced from <IP_ADDRESS>.
I found in your code that the source IP (<IP_ADDRESS>) is hard coded.
Shouldn't this be defined automatically or via user input?
I have manually changed the source IP and found that 1 is consistently appended onto the source IP, eg src_net = "<IP_ADDRESS>" becomes source IP <IP_ADDRESS>1. Removing the last 5 causes the source IP to <IP_ADDRESS>

Thanks for responding.
I appreciate the explanation of your code.
I was thinking firewalls could possibly interfere with SYN packets marked from a different or non-existent network. Plus, my OCD wanted to see those packets coming from the right network :smile:
In an ideal world, this source IP would be automatically configured if no option to specify source IP was listed in the command, and an additional option would allow the user to specify source IP if wanted.
I'll play around with your code a bit and see if I can get it to work w/ user input. If that happens, I will hand in the code for review.

You are correct that a firewall could potentially block such requests :)
I guess one could get the current IP address from one of the active network cards and use the network part of the address as the base for spoofing the source IP addresses.
Quick question, how did you find this repository?

I found this repo via google. I wanted a tool that would generate SYN packets for me so I could experiment with my home network. This was the first tool I found.

Cool :)

FYI I have created a private Gitlab repository with a copy of your code so I can work on it there. Once I have a working version, I will let you know so you can create a new branch and start a QA process on any work I can complete.

@mjdubell I am ready to merge my fork back into this repo. Do you want to create a branch for me to merge into? If not, I can merge into master.
Thanks!

@LucasGood You can create a pull request and from there I can merge into master.

Once a PR comes in, I will review it and merge it.


Added support for CRLF line endings through option in Yarner.toml

Line endings can be controlled via bool option crlf_newline in section [parser] of Yarner.toml.
Not really an optimal solution for projects used on different systems.
Made crlf_newline optional, use system newline if not provided.
Fixes #119

Withdrawn in favor of #122


RoleService UpdatePermissions

https://github.com/fullstackhero/dotnet-webapi-boilerplate/blob/54d25010fb2e316adc7cf36bef8f6d4f8f6a9500/src/Infrastructure/Identity/RoleService.cs#L156
What exactly does that method do?

(lines 186-190) It first deletes all permission claims from the role
(lines 192-202) then it adds the selectedpermissions as claims to the role again (using an extension method which should probably just be in the service as it's only used here, or not even be a separate method at al?)
(lines 204-212) then it goes over all the selected permissions again and checks if they are in the permissions of the role (they all should be as they were just added in the previous step?) and in that case they are saved once more using the roleclaimservice??

Isn't this last step redundant? This is doing 2 times the same thing, right? Or am I missing something?
@iammukeshm You can hopefully shed some light on this?
Also while we're at the subject, and also in light of PR #377 ... I think the role api should change a bit:

GET api/role/{id}: would return the permissions included inside the RoleDto (we will probably need a new dto for that, or rename the existing one to RoleListDto). Just a List<string>. No need for the Enabled property.
UpdatePermissionsRequest would also just contain a List<string> of permissions.

Side thought: We could even include the updatepermissions (optionally) into the PUT api/role/{id} call maybe?
That together with the static FSHPermissions strings (in the shared project) is enough to build the whole UI for it I think. No need to send "Enabled" properties over the wire... that's 100% a UI concern, right?
I even think we can eliminate the roleclaimservice. What else is that used for other than adding and removing permissions from roles? I would roll (no pun intended) all that functionality into the roleservice (which practically already is there) and just eliminate the roleclaimservice and -api?
To put it into DDD terms: it would be the "Role aggregate", which contains the permissions (roleclaims).

Hi, you can assign it into me , I can change it.

Remove roleClaimService
You mean remove the GetPermissions, and include this one in the main Get?
UpdatePermission would only receive a List that would be the ones to have. Yes maybe is better.
The code of the method were already there, but we can refactor it(the UpdatePermissions)

I can't assign issues myself... but you can go ahead... can use the existing pr... will review when ready ;-)

You mean remove the GetPermissions, and include this one in the main Get?

Yes, I think the get is only used to see detailed info of a role (otherwise the listdto (RoleDto now) is used to create/update roles atm) so I think it would fit perfectly there I think...

@fretje , Yes, the last step is not needed there. maybe it's a piece of old code that went unnoticed. We can remove that.
Do you mean, a single request to update both the role details and the associated claim (permission)? Not sure of that. Currently, it's split up into 2 requests keeping security in mind. Someone who has access to view the Role details shouldn't be able to see the permissions too, in case.

@iammukeshm  I Will review all the UpdatePermissions  method, because i didnt touch it too much because i guess was already verified

@fretje  Yes, is better to have a method only to GetPermissions, and another to GetRole, because in the Basic/Admin role we cant edit, but if we create another roles, we can edit them(name and description), so is better have seperated methods

PR updated

Ok, I understand that it need to be separate methods... but I would rename the GetPermissions method to GetByIdWithPermissions and return the same result but wrapped in a RoleDto... then there's no need to do 2 calls on the client. And still have the same protection by the FSHPermissions.RoleClaims.View permission...

Ok, that is a good way to do it yes


LCTT test : Trigger Join Request problem

Hi,
I am using the LBM version 4.5.0 and I am testing the firmware using LCTT.
I obseved that loraMac freezes (no more packets are sent or a new Join is sent) when the tool asks the device to trigger a Join Request. However, all the other LCTT commands works fine.
When debugging I obseved that the "lorawan_join_internal_add_task( stack_id )" cannot be called as the modem task priority blocks the access in line below:
context->modem_task[JOIN_TASK + ( NUMBER_OF_TASKS * stack_id )].priority != TASK_FINISH
I added the line below to leave the network when the LORAWAN_CERTIFICATION_DUT_JOIN_REQ command is received and now it works fine (Join triggered successfully and there is no problem)
lorawan_api_join_status_clear( lorawan_certification_obj->stack_id );
Can you check please if the fix is OK
    case LORAWAN_CERTIFICATION_DUT_JOIN_REQ:
        if( rx_buffer_length == LORAWAN_CERTIFICATION_DUT_JOIN_REQ_SIZE )
        {
            // leave network
           lorawan_api_join_status_clear( lorawan_certification_obj->stack_id );
            lorawan_api_set_activation_mode( ACTIVATION_MODE_OTAA, lorawan_certification_obj->stack_id );
            ret = LORAWAN_CERTIFICATION_JOIN_REQ;
        }

Thank you.
Best regards.

Hello, thank you for using LBM
Can you check if you didn't delete the line of code inadvertently ?
https://github.com/Lora-net/SWL2001/blob/d05dad5b4df9c0e5899008e43bfce48f5498abb5/lbm_lib/smtc_modem_core/lorawan_packages/lorawan_certification/lorawan_certification.c#L560
The lorawan_api_join_status_clear() is present in the master branch
Best Regards

Hi,
Thank you for you quick reply.
Sorry, I posted the wrong place.
The line added was :
 smtc_modem_leave_network( lorawan_certification_obj[idx].stack_id );
in the section below:
case LORAWAN_CERTIFICATION_JOIN_REQ: {
        if( lorawan_api_isjoined( lorawan_certification_obj[idx].stack_id ) != JOINED )
        {
            // Leave the network before starting a rejoin.
            smtc_modem_leave_network( lorawan_certification_obj[idx].stack_id );
            lorawan_join_add_task( lorawan_certification_obj[idx].stack_id );
        }
        break;

Note, that I observed that this API: "smtc_modem_leave_network()" was added for "DM_REJOIN" but not in the section above. I do not know if it is forgotten.
case DM_REJOIN: {
        uint16_t dev_nonce       = ( cmd_input->buffer[1] << 8 ) | cmd_input->buffer[0];
        uint16_t lr1mac_devnonce = lorawan_api_devnonce_get( ctx->stack_id );
        if( lr1mac_devnonce != dev_nonce )
        {
            SMTC_MODEM_HAL_TRACE_WARNING( "DM invalid devnonce to rejoin\n" );
            uint8_t dm_fields_payload[1] = { DM_INFO_SESSION };
            cloud_dm_set_info_field( ctx->stack_id, dm_fields_payload, 1, DM_INFO_NOW );
            break;
        }
        // Leave network
        smtc_modem_leave_network( ctx->stack_id );
        // Add a new join task
        lorawan_join_add_task( ctx->stack_id );
        break;

Thank you.

Hi,
The smtc_modem_leave_network() command must not be used in certification to avoid killing the certification task.
Could you please test without this line added ?
Many thanks,
Best regards

Hi,
If I don't add the smtc_modem_leave_network(), the modem will never trigger a Join request.
After debugging, I observed the the lorawan_join_internal_add_task( stack_id ) cannot be called.
For unknown reason the task priority blocks the access in line below:
context->modem_task[JOIN_TASK + ( NUMBER_OF_TASKS * stack_id )].priority != TASK_FINISH
I did not find another workaround for this issue.
Did you test from your side the LORAWAN_CERTIFICATION_DUT_JOIN_REQ command with LCTT?
Thank you.
Best regards.


Jas assembler rewrite

The pull request rewrites and implements the Jas assembler after the initial fumbling is completed. it implemented a new architecture aimed at reducing code size and significantly improving speed for assembling code. As of today, this pull request is not completed and requires more work before it can be merged into the dev branch for further testing
Regards,
Alvin

Honestly, at this point there's no reason to not merge this onto the dev branch as it does not affect anything, what was I thinking? However, the concept is valid


Code 127: /bin/bash: cmd/search/search: No such file or directory

Hi, I need some help here.
Not sure if this is due to using Catalina, or do I need some go setup, but I'm getting this error (debugging this workflow):
|[08:46:32.669] ERROR: Bear[Script Filter] Code 127: /bin/bash: cmd/search/search: No such file or directory
Any ideas?
I'm using Alfred 4.0.5.
Thanks.

I'm working on adding detailed instructions for how to do this in the readme but if you know how to open a terminal to the Bear workflow folder inside of Alfred, you can try running this command:
open cmd/search/search; open cmd/create/create; open cmd/link/link

and seeing if it resolves the issue.

I'm not sure what happened here, but I reinstalled and it worked fine.
I think I had a lot of mixed installations of Bear workflows, and somehow they were Messe up. 🤷♂
Apologies for this.
And thank you so much for this.

I'm working on adding detailed instructions for how to do this in the readme

If I can help in some way, please say so

Interesting. I'll hold off on documenting it until someone runs into the same problem then. Thanks for getting back to me on the issue.


Calling flash after get_flashed_messages fails

In a single request, do this:

call get_flashed_messages()
call flash(...)
call get_flashed_messages() again, observe that it returns the empty list, despite a message just having been flashed.

After the first call to get_flashed_messages(), request_ctx.flashes is  [], which appears to send this code in get_flashed_messages off the rails:
https://github.com/pallets/flask/blob/98a7f9fcf09fce5d32bf25e7f917c1c3026719d1/src/flask/helpers.py#L364-L367
Environment:

Python version: 3.11
Flask version: 3.0.2

What does "off the rails" mean? Did an error happen? Be sure to provide a minimal reproducible example and the full traceback when reporting an issue.

Sure, fair:
from flask import Flask, flash, get_flashed_messages

app = Flask(__name__)
app.secret_key = "abcdef"

@app.route("/")
def hello_world():
    get_flashed_messages()
    flash("hi")
    assert get_flashed_messages()

Run with
flask --app=flask_repro run

go to http://<IP_ADDRESS>:5000/ and see
Traceback (most recent call last):
  File "/home/andreas/src/env-3.12/lib/python3.12/site-packages/flask/app.py", line 1455, in wsgi_app
    response = self.full_dispatch_request()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/andreas/src/env-3.12/lib/python3.12/site-packages/flask/app.py", line 869, in full_dispatch_request
    rv = self.handle_user_exception(e)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/andreas/src/env-3.12/lib/python3.12/site-packages/flask/app.py", line 867, in full_dispatch_request
    rv = self.dispatch_request()
         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/andreas/src/env-3.12/lib/python3.12/site-packages/flask/app.py", line 852, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/andreas/tmp/flask_repro.py", line 10, in hello_world
    assert get_flashed_messages()
AssertionError

What does "off the rails" mean?

"Off the rails" means that flashes is not None there, and so the code does not look in the session (assuming that's what it's supposed to do).

This is documented: https://flask.palletsprojects.com/en/3.0.x/api/#flask.get_flashed_messages

Further calls in the same request to the function will return the same messages.

The intended use is documented as well: https://flask.palletsprojects.com/en/3.0.x/patterns/flashing/

The flashing system basically makes it possible to record a message at the end of a request and access it next request and only next request.

You're intended to put messages into one request, then get them out in the next request. Getting them out, putting them in, and getting them out again in the same request is not the intended use case.


Unable to run with GPT40

Hi
Thanks for the great tool!
I was recently trying to use it with GPT4o but I keep getting this error -
Error while parsing the file '/NS/llm-1/work/afkhan/Work/Paper.pdf': Failed to parse the file: <FILE_ID>, status: ERROR
I've removed the actual file id incase it can be misused by others.
This even happens if I supply my own API key.
Here are the code snippets -
No API Key -
from llama_parse import LlamaParse

parser_gpt4o = LlamaParse(
    result_type="markdown",
    # api_key=api_key,
    gpt4o_mode=True,
    split_by_page=True,
    # gpt4o_api_key=OAI_KEY
)

Provided Personal API Key -
from llama_parse import LlamaParse

parser_gpt4o = LlamaParse(
    result_type="markdown",
    # api_key=api_key,
    gpt4o_mode=True,
    split_by_page=True,
    gpt4o_api_key=OAI_KEY
)

I have already set os.environ["LLAMA_CLOUD_API_KEY"] and it works well when I set gpt4o_mode to False

Could you provide the file / job id. they are linked to your account and can only be accessed when using your own API key.

Could you provide the file / job id. they are linked to your account and can only be accessed when using your own API key.

Hey
I was parsing this paper https://arxiv.org/abs/2404.12957

@hexapode any updates on this?


feat: add option to include zero based carets dependencies

By default, the plugin ignores zero-based carets. But this option to update them too will be useful for many popular packages that are still 0.*.* version. For example fastapi or uvicorn.
Closes #41

@MousaZeidBaker Could you take a look?

Since we're using --latest, everything except those locked to specific versions can be upgraded. By default, 0.x versions should be upgraded.

The plugin's README doesn’t mention this issue at all--"By default, the plugin ignores zero-based carets. ". I initially thought it was a bug in version parsing, but after reviewing the code, I found some special handling that seems unnecessary. Since we're using --latest, everything except those locked to specific versions should be upgraded. By default, 0.x versions should be upgraded. On the computer I use, I simply deleted those 4 lines of code. I think this plugin has quite a lot of options.

I agree. The behavior I was expecting is that zero-ver dependencies are upgraded too when using --latest.
For several month, since the PR https://github.com/MousaZeidBaker/poetry-plugin-up/pull/26 , I have to manually upgrade them.
I think the behaviour introduced by https://github.com/MousaZeidBaker/poetry-plugin-up/pull/26 is confusing, and should be reverted rather than adding an option for overriding it.
What I would suggest is :

to revert 8a5d3cb6a4f122537e7e66faf52c1672d8773abc (but that would be breaking).
reopen an issue or a PR to discuss about adding an exception or an option for "incomplete" requirements (^0.0, ^0, ^1, ^1.0, `~1.0,…) who have special meanings, to keep the semantic meaning when increasing version.

First of all, sorry for the late feedback. I've ben overwhelmed with other projects and haven't had time to look into this.
Upgrading ^0.0 to ^0.0.x do change the behaviour of the semantics, thus it's a valid use case to be able to ignore zero-based requirements. However, I do agree with @koalp that I'd rather have a flag that ignores "incomplete" requirements in order to preserve their meaning. If you can open a PR that would be highly appreciated, this way even if its a breaking change, people will still be able to have current behaviour by using the new flag.

Not sure if I fully understand, so I'm just thinking out loud. Which of these would be happening by defaults, and which would go behind the incomplete flag?

^0.2.3 -> ^0.3.0  (currently doesn't upgrade with --latest, e.g. fastapi, ruff, sqlmodel, etc)
^0.2.3 -> ^1.0.0
^0.2.3 -> ^0.2.4
^0.0 -> ^0.0.4 (this is called "incomplete")

Are there any other relevant situations? As far as my expectations go, I don't know about or understand the importance of the special or "incomplete", but I do expect at least the first three in the list to update when running poetry up --latest

Not sure if I fully understand, so I'm just thinking out loud. Which of these would be happening by defaults, and which would go behind the incomplete flag?
* `^0.2.3 -> ^0.3.0`  (currently doesn't upgrade with `--latest`, e.g. fastapi, ruff, sqlmodel, etc)

* `^0.2.3 -> ^1.0.0`

* `^0.2.3 -> ^0.2.4`

* `^0.0 -> ^0.0.4` (this is called "incomplete")

Are there any other relevant situations? As far as my expectations go, I don't know about or understand the importance of the special or "incomplete", but I do expect at least the first three in the list to update when running poetry up --latest

I didn't find time to draft a PR but if I do it, what I had in mind for the default would have been "keep the version spec when the latest version is still described by it[^initial_zero_based_handling], update if not". Some tests I would write would be :

^0 -> ^0 if the latest version is 0.x.y

^0 ->^1.0.0 if the latest version is 1.0.0

^1 -> ^1 if the latest version is 1.x.y

^1 ->^2.3.4 if the latest version is 2.3.4

^0.0 -> ^0.0 if the latest version is 0.0.x

^0.0 -> ^0.1.0 if the latest version is `

^0.1 -> ^0.1 if the latest version is 0.1.x

^0.1 -> ^0.2.0if the latest version is 0.2.0

^0.2.3 -> ^0.2.4 if the latest version is 0.2.4

^0.2.3 -> ^0.3.0 if the latest version is 0.3.0

(haven't looked at how tilde and wildcard are handled by poetry up but would probably do something similar.
An alternative could be "keep the meaning of version", for example ^1 -> ^2 if the latest version is 2.1.0 but I think it's a better practice to specify the minimal version precisely. This could be implemented later by someone who needs it --keep-semantics or something like this.
[^initial_zero_based_handling] this was what the initial PR for zero based versions was for : https://github.com/MousaZeidBaker/poetry-plugin-up/pull/26 . It would keep this behavior.

New version 0.8.0 now deployed


Add fpgainfo events documentation

Coverage remained the same at 61.227% when pulling 245fe20ecd746938945f693b4e6215a5551b023c on ele/fpgainfo-events-documentation into 70c24cc4274392dd15d60af1672308e78a575c80 on master.