Use gradle/gradle-build-action

https://github.com/gradle/gradle-build-action
Ref https://github.com/detekt/detekt/pull/3723, it's really so fast to run jobs, and many other advantages.

Very good idea. Thanks. I've edited the PR slightly.

I've tested the build performance with and without gradle-build-action, as well as with an empty cache and with a pre-filled cache. The benefits are extremely small in our case: 5s if the cache is filled. If the cache is empty, it even makes the build a lot slower (about 45s) because the cache needs to be uploaded at the end. I don't see a value for this change at the moment. I've reverted the commit. Sorry, but thanks anyhow for the contribution! 👍


GTID Related SET in Database Dump Will Cause Db Import to Fail

Databases coming from Aurora RDS frequently have GTID related SETs which cause problems when importing into a local non-replicated MariaDB container:
$ zgrep -E '\@\@(GLOBAL\.GTID_PURGED|SESSION\.SQL_LOG_BIN)' ./magento.sql.gz
SET @MYSQLDUMP_TEMP_LOG_BIN = @@SESSION.SQL_LOG_BIN;
SET @@SESSION.SQL_LOG_BIN= 0;
SET @@GLOBAL.GTID_PURGED='';
SET @@SESSION.SQL_LOG_BIN = @MYSQLDUMP_TEMP_LOG_BIN;
SET @MYSQLDUMP_TEMP_LOG_BIN = @@SESSION.SQL_LOG_BIN;
SET @@SESSION.SQL_LOG_BIN= 0;
SET @@GLOBAL.GTID_PURGED='';
SET @@SESSION.SQL_LOG_BIN = @MYSQLDUMP_TEMP_LOG_BIN;

The errors these will cause looks like the following:
==> [16:33:13] Importing database
ERROR 1227 (42000) at line 18: Access denied; you need (at least one of) the SUPER privilege(s) for this operation

This change appears to have caused issues with database imports. At least two different individuals (and myself!) have run into the following errors:
==> [21:47:37] Importing database
 251MiB 0:28:53 [ 148KiB/s] [==============================================================================================================================================================================================================================================================================================================>] 100%
ERROR 1064 (42000) at line 17659: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'Binary file (standard input) matches' at line 1
ERROR: Command `"${WARDEN_DIR}/bin/warden" env exec -T db mysql -u"${MYSQL_USER}" -p"${MYSQL_PASSWORD}" "${MYSQL_DATABASE}"` on line 45 failed with exit code 1
ERROR: Command `warden db import` on line 231 failed with exit code 1

Why this is occurring, I'm not entirely sure, but as I've never seen it prior to this being introduced this will be reverted in 0.6.0 release.

I finally figured out what caused the failures when importing databases running through grep; the magical binary file detection grep has.
Grep has the following special flag which seems to resolve this issue:

-a, --text
Process a binary file as if it were text; this is equivalent to the --binary-files=text option.

The issue is because grep is switching to binary mode half way through filtering the piped data, and is echoing Binary file (standard input) matches to the stdout pipe which is passed to MySQL which is then chocking on the data. What I'm not certain of is why grep is detecting binary data on some database dumps (although it's not surprising).
Alternate solution is to use sed to strip the lines (sed is already used to change the definers on functions and triggeres to CURRENT_USER and it works reliably):
LC_ALL=C sed -E '/\@\@(GLOBAL\.GTID_PURGED|SESSION\.SQL_LOG_BIN)/d'

This solution of using sed is the one I plan to implement.


PivotItem IsEnabled="False" has no effect

Describe the bug
When setting PivotItem property IsEnabled="False" pivot control still alow user to navigate to the disabled PivotItem.
Steps to reproduce the bug
//XAML
<Pivot Title="EMAIL">
    <PivotItem Header="All">
        <TextBlock Text="all emails go here." />
    </PivotItem>
    <PivotItem Header="Unread"  IsEnabled="False">
        <TextBlock Text="unread emails go here." />
    </PivotItem>
    <PivotItem Header="Flagged">
        <TextBlock Text="flagged emails go here." />
    </PivotItem>
    <PivotItem Header="Urgent">
        <TextBlock Text="urgent emails go here." />
    </PivotItem>
</Pivot>

Expected behavior
When PivotItem property IsEnabled is set to false, PivotItem should be visible but disabled, and PivotItem selection shouldn't be allowed.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.0 (If you're seeing your issue in older previews of WinUI 3, please try this release)
Windows app type

[X] UWP
[ ] Win32

Device form factor
Desktop
Windows version
October 2018 Update (17763)
Additional context
No response

What input methods allow you to navigate to that item? Mouse, touch, keyboard, programmatic?

Input method used : Mouse

Pivot isn't in active development so I don't think this will get addressed over other issues any time soon.

Encountered the same issue. This should get repopened


Reverse Linked List

Description
Submission description here
Checklist:

[x] I've checked the issue list before deciding what to submit.
[x] I've read the contribution guidelines.
[x] I've edited the README.md link to my code.

I have not edited any README.md file, please explain on that thing, I did not get it.

Rename the file as Reverse_linked_list.cpp and Reverse_linked_list.py

Made the changes ✔

@Abhijit2505 There is no need of creating a new folder with the name 'LinkedList'. You have to commit your code in the ds folder

I have not edited any README.md file, please explain on that thing, I did not get it.

You have to edit this README.md to link your program under the Data structure list. You have to do the same for the python file in the python folder.

Three things,

The space after count+= and the blank line you pointed out gets ignored by the compiler in C++ and Python when the compiled file is generated. There is no meaning of removing a blank line or adding some space.

ds folder is good, but there are around 40/50 Linked List algorithms which will be messy inside the ds folder. Hence I have created another folder named Linked List to make the repository modularized. Well as the number of program increases, you will understand the thing.

Comments should be there inside every code to make it easier for some users. The comments which you have asked me to remover were not wrong neither had any faults, still as per your review I have removed them.

I was here just to know about the repository structure and mechanism because I am going to mentor the participants in the upcoming Contributor's Hack by HakinCodes.
Thank You.

Three things,

The space after count+= and the blank line you pointed out gets ignored by the compiler in C++ and Python when the compiled file is generated. There is no meaning of removing a blank line or adding some space.
ds folder is good, but there are around 40/50 Linked List algorithms which will be messy inside the ds folder. Hence I have created another folder named Linked List to make the repository modularized. Well as the number of program increases, you will understand the thing.
Comments should be there inside every code to make it easier for some users. The comments which you have asked me to remover were not wrong neither had any faults, still as per your review I have removed them.

I was here just to know about the repository structure and mechanism because I am going to mentor the participants in the upcoming Contributor's Hack by HakinCodes.
Thank You.

All the points mentioned by you are quite legit but I have my own reasons for suggesting those changes.
Reasons:

Yes, the space and blank lines gets ignored by the compiler in C++ and Python when compiled file is generated, but proper use of spaces and blank lines enhance the readability of the code. Refer to point 5 and 7 of this document. Your code is well structured and that's commendable.

We will be restructuring all the folders soon. For now we are merging all the commits to their respective domain folder. Making a new folder was justified from your end.

I never said that the comment I asked you to remove was wrong or had any fault. I just felt that it was superfluous.

We are really excited about Contributor's Hack. Will love to work with you . Your codes are really well structured and are example for our other contributors. I hope I cleared my points.
Thank You

@Abhijit2505 Can you please squash your commits so that I can merge this PR.

@Abhijit2505 Can you please squash your commits so that I can merge this PR.

I think the Squash And Merge option is available for the people having write access to the repository. Hence please squash and merge it.

@Abhijit2505 Okay, done.

@all-contributors please add @Abhijit2505 for code


[113] Issue #113 - July 12, 2018

To contribute to this issue, simply leave a comment here. Please also review our contributing guidelines.
The current draft for this issue in _drafts/. If you want to contribute directly, feel free to open a pull request.

If somebody would like to take this issue, that would be 💯!

I could be a backup plan:) if no one will take in next two-threee days - I will take

https://github.com/apple/swift-evolution/issues/863
Sent with GitHawk

SE-0202 amendment accepted
https://forums.swift.org/t/amendment-to-se-0202-removing-collection-randomelement-as-a-customization-point/14101
SE-0216: User-defined dynamically callable types accepted
https://forums.swift.org/t/accepted-se-216-user-defined-dynamically-callable-types/14110

217 in review
Sent with GitHawk

218 in review
Sent with GitHawk

Thanks @RomanVolkov ! 🙌

moving URLSession + other components to a new corelibs-foundation-networking lib
https://forums.swift.org/t/pitch-move-urlsession-to-new-foundationnetworking-module/14002

I’m working on support for protocols with superclass constraints - the missing piece of SE-0156 I never implemented in Swift 4.0 https://github.com/apple/swift/pull/17816

https://twitter.com/slava_pestov/status/1015498949816303616

Codable is awesome but enums require so much boilerplate

https://github.com/apple/swift-package-manager/pull/1655/files#diff-31d171cad93e680d3ffc6cb3c4fc6848R13
https://twitter.com/aciidb0mb3r/status/1016124417527595008

@aciidb0mb3r Looks like something a compiler could generate

@jckarter Yeah, I made a Sourcery template to generate this but it would be nice to have it synthesized by the compiler.

Heads up that we're publishing in three days.
If you need any help, let me know @RomanVolkov!

Finally: https://twitter.com/slava_pestov/status/1016534163988496384

https://github.com/apple/swift-evolution/pull/873/files

@BasThomas yep, working on the draft

https://twitter.com/Ilseman/status/1017143932168241153

@BasThomas  sorry for late update. Draft is pushed, PR is ready

Thanks all!


Live

Go Live

Learn Build status updates of commit f04b64e:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Support $text evaluation query operator

Support only the simplest queries with strings.Contains for now:

[ ] $search field (excluding phrases and negation)
[ ] $language field with the value none or absent
[ ] $caseSensitive

Return ErrNotImplemented for:

phrases in quotes
negation
other $language values
$diacriticSensitive

Out of scope:

stop words
stemmed words
text score
all complex cases

Added integration test for MongoDB in #702, where it's clear that the $text index is required. So the issue is postponed.


Fix typo

See #15

@Saela I added ticket #16  to the sprint because even though part of the frontend tests, I believe it differs in scope and warrants its own ticket
This PR is a proof of concept for the changes I made to the CI file on staging. It is not optimal yet, but it

Runs the tests (currently only npm i)
Builds the container
IF the push is to stage or main (which it isnt here), it also pushes the image to the registry
The deploy step only runs for pushes to stage or main

It could be optimized further, I believe, but like this, we not only have passing tests as requirement, but also a passing build. In the previous version, you could have passing tests but failing builds and would have noticed this only in the buildstep 🤷


Missing include in BLEValue.cpp

Hey there,
https://github.com/nkolban/ESP32_BLE_Arduino/blob/master/src/BLEValue.cpp missing #include "BLEValue.h"

Thanks, fixed.

This issue impacts the 1.0.0 release of https://github.com/nkolban/ESP32_BLE_Arduino - could you please release a new version there?

@hansmbakker its been fixed in ESP32_BLE_Arduino library, or am i missing something?

This fix is also not included in the PlatformIO 1.0.0 version for example: https://github.com/nkolban/ESP32_BLE_Arduino/commit/24d7bdf1f083ceb95c06c0393e8be80c8e0cc18a.
Maybe you can create a new release? Like 1.0.1?

I can do that.

done.

Thank you! I'll wait a bit before it shows up at https://platformio.org/lib/show/1841/ESP32 BLE Arduino.
The updated library.properties is already showing on the manifest tab, but it does not yet show as a new release in the right-hand sidebar and the BLE_client.ino example is not updated yet (the doScan line is not correct)

Sorry for inconvenience, it was big and rush update.


wasm: simplify transaction planner

Closes #609
This commit gets most of the way to dramatically simplifying the transaction planner.  It completely eliminates the fork of the Rust crate's Planner API, and focuses on what the web extension actually needs, namely, serving TransactionPlanRequests.
The only thing remaining is cleaning up the test code, which was written against the previous API and much of which doesn't make sense any more.
Along the way, it also fixes a bug in the existing web extension code, which would result in making unnecessary spends sometimes (always spending all available notes, even if unnecessary).
One observation growing out of this (cc @zbuc) is that we should change the way gas costs are computed on-chain, removing the transaction-wide byte costs and making the gas cost of the transaction just be the sum of the gas costs of its constituent actions. (In other words, we'd attribute the block space costs of each action to that action, and make the surrounding transaction contents free, rather than what we currently do, which is have the block space costs attributed to the transaction as a whole and make it free for each action). The reason is that this makes it very difficult to do "incremental" reasoning about the gas costs of the transaction as actions are added or removed.
We could also later backport much of this simplification to the Rust planner.

Initially, I assumed we were moving towards using wasm only in places where it was critically needed

the use of specific cryptography
heavy code duplication
I also assumed that we were moving towards avoiding reading and writing to IndexedDb for wasm. For reasons such as:
we still don't know how to test wasm with indexedDb global
we don't have good control over everything that happens in wasm
I have an idea that instead of having one big wasm function that turns TransactionPlannerRequest to TransactionPlan (and which is kind of a black box for TS) we can have many small wasm wrapper functions over things we can't do in TS.
For example

for tpr::Swap {
        value,
        target_asset,
        fee,
        claim_address,
    } in request.swaps
    {
        let value: Value = value
            .ok_or_else(|| anyhow!("missing value in swap"))?
            .try_into()?;
        let target_asset = target_asset
            .ok_or_else(|| anyhow!("missing target asset in swap"))?
            .try_into()?;
        let fee = fee
            .ok_or_else(|| anyhow!("missing fee in swap"))?
            .try_into()?;
        let claim_address = claim_address
            .ok_or_else(|| anyhow!("missing claim address in swap"))?
            .try_into()?;

        // Determine the canonical order for the assets being swapped.
        // This will determine whether the input amount is assigned to delta_1 or delta_2.
        let trading_pair = TradingPair::new(value.asset_id, target_asset);

        // If `trading_pair.asset_1` is the input asset, then `delta_1` is the input amount,
        // and `delta_2` is 0.
        //
        // Otherwise, `delta_1` is 0, and `delta_2` is the input amount.
        let (delta_1, delta_2) = if trading_pair.asset_1() == value.asset_id {
            (value.amount, 0u64.into())
        } else {
            (0u64.into(), value.amount)
        };

        // If there is no input, then there is no swap.
        if delta_1 == Amount::zero() && delta_2 == Amount::zero() {
            return Err(anyhow!("No input value for swap").into());
        }

        // Create the `SwapPlaintext` representing the swap to be performed:
        let swap_plaintext = SwapPlaintext::new(
            &mut OsRng,
            trading_pair,
            delta_1,
            delta_2,
            fee,
            claim_address,
        );

        let swap = SwapPlan::new(&mut OsRng, swap_plaintext).into();

        actions.push(swap);
    }

We can replicate all this logic on TS, but we can't replicate SwapPlan::new() because it uses cryptography to generate proof_blinding_r and proof_blinding_s
https://github.com/penumbra-zone/penumbra/blob/5863116e3a2e0a0ee379eb22818316e40c4be275/crates/core/component/dex/src/swap/plan.rs#L26-L37
The idea is that we create a wasm wrapper for SwapPlan::new(), but move all the rest of the logic to TS.
In this case wasm planner will become a set of small helper functions (obviously there will be quite a lot of them), but most of the logic will be moved to TS (hopefully all indexed-db interaction) and covered by tests.

The problem is that the transaction planner needs to do fee estimation, and because of that it needs to do exact arithmetic on Values, which is not really possible to do separately from the Rust code. So it's better that the entire thing be on the Rust side, where at least it can be simple, straight-line code.

✅ wasm reads all necessary data directly from indexed-db
✅ pass FVK to wasm instead of passing refundAddress
✅ cleanup
This works for most transactions, but when trying to spend a penumbra (UM) token I get an error
ConnectError: [unknown] Tendermint: failed to deliver transaction: check_stateless failed: a spend proof did not verify: spend proof did not verify
❌ wasm tests are still broken

The error seems to be related to zero spend

@Valentine1898 good catch. I have an idea of a clean way to handle it, I'll push a commit onto the branch

I'm not sure at all if this error is related to this PR, because I found in indexed-db note with zero amount, maybe it's a view service issue

@Valentine1898 I think the problem with zero valued notes is that they're treated differently in the proofs -- there's a capability to do "dummy spends" at the protocol level, I think this makes spending a zero-valued note in the normal way not possible. @redshiftzero would know the exact details.
In the commit I pushed, we filter them out at the same time as prioritizing notes.

@Valentine1898 I think the problem with zero valued notes is that they're treated differently in the proofs -- there's a capability to do "dummy spends" at the protocol level, I think this makes spending a zero-valued note in the normal way not possible. @redshiftzero would know the exact details.

I got a zero note as a result of a swap claim, I thought there used to be zero note filtering somewhere at the block scanner layer, but I haven't found anything like it

In the commit I pushed, we filter them out at the same time as prioritizing notes.

That fixed the error, awesome

https://github.com/penumbra-zone/penumbra/blob/d2ec71f38f73cb2f1e8c57a42c5744f706e64adb/crates/core/component/shielded-pool/src/note_payload.rs#L26-L31
Found it, zero notes are legal

oh excellent! thank you


Add multiple options to force aspect ratio.

This branch adds more options to force ratio:

Visuals, only force visuals to aspect ratio,
Global, force all game to aspect ratio,
None, or anything else, do nothing.

When force aspect ratio is Visuals a class .forceAspectRatio is added to visuals content div, if global its added to monogatori main element.
Now I am getting size from "body" element instead of Monotogari element, because I can't read size and change it at same time.
Hope, this is ok, I tested with example and my game and seems to be good.

Thank you so much!
Yes, probably reading the width and height of the body element is perfect since that way we get the whole window size and also takes into account if it's in an iframe wich is awesome :D
Really, thank you so much for all your work!


No process template with type {guid} was found

Hi all,
I've tried to use the demo generator build tool to export an ADO project. This works. I then attempt to import it into another ADO organisation and i get the error 'No process template with type {guid} was found'.
I can't seem to find anything related to why this may be happening. Could anyone shed some light on what may be causing this?
Thank you.

Hi @MattLeach25
Thanks for reaching us. If you are trying with a custom template, source and destination organizations must have the same process template Id.
If the source project is using a custom/inherited process template, you cannot have the same process in the destination/target organization. You must use the same organization to import it back.

Hi there, thank you for your response. So if i understand the above correctly, if the source project is using a custom process template, you cannot simply export it and put it in another ADO org? If this is the case, this sadly will not work as we would like to make this template available for other people to use.
Thank you @aksh-h

@MattLeach25 yes, you're correct.


Insertion_at_start of array in java

A program to add elements at the beginning  of an array in java.
I am a GSSOC'21 participant, and I would like to contribute the Java code for this problem. I will make sure that the code is commented properly and follows all the given guidelines. Please give me this opportunity. Thankyou!
@tarun26091999  @rudrakshi99

issue present at #146


Load Handling

Hi, thanks for this library. Do you perhaps have any stats on what load this library would be able to handle (messages / second) ? Looking to use this library in a micro service.

Real production load test no, but times ago  (using some groovy scripts you
can find in the tools/benchmark directory) I've proved that in publish
end-to-end, a client subscribing to a topic, and publishing a message (with
send timestamp inside the payload) on the same topic, the broker performed
almost 30K msg/sec as global outbound limit, so using 2 clients flows, I
saw 15K msg/sec per client.
Andrea
On Mon, Aug 28, 2017 at 11:23 AM, Hein Smith<EMAIL_ADDRESS>wrote:

Hi, thanks for this library. Do you perhaps have any stats on what load
this library would be able to handle (messages / second) ? Looking to use
this library in a micro service.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/andsel/moquette/issues/354, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_Y0RA3CMAO0GREE-V2W_Pdr1N9yaEzks5scocfgaJpZM4PESDu
.

Thanks for the fast reply. Seems impressive.


Improve 'windows' OS detection of taskbar location

Should be helpful for the following issues
https://github.com/maxogden/menubar/issues/264
https://github.com/maxogden/menubar/issues/232

Sure, updated PR

fix ur program. https://github.com/maxogden/menubar/issues/309

Is this going to be merged into an official release?

Is this going to be merged into an official release?

@amaurymartiny we have users reporting this bug when the taskbar is on the left as well. Any chance we could get this merged and released? I'm happy to help test as well if needed.

@amaurymartiny we have users reporting this bug when the taskbar is on the left as well. Any chance we could get this merged and released? I'm happy to help test as well if needed.

I unfortunately didn't get the chance to test on Windows. It seems that it's blocking a couple of users, so I am going to merge it. Thanks @semenov-oleg for the work!

I unfortunately didn't get the chance to test on Windows. It seems that it's blocking a couple of users, so I am going to merge it. Thanks @semenov-oleg for the work!

@amaurymartiny it seems that left sided taskbars are still broken with this PR, according to some users.

@amaurymartiny it seems that left sided taskbars are still broken with this PR, according to some users.

#343 fixes the left-sided taskbar issue.


feat(app.runWithContext): Support getCurrentInstance

What problem does this feature solve?
When getCurrentInstance is used within app.runWithContext - top-level component instance should be returned (if it already exists). This should allow easier usage of Vue features outside components.
This behavior can currently be 'emulated' with app.provide, but it feels like there should be no need for this workaround.
runWithContext was first introduced in https://github.com/vuejs/core/pull/7451
What does the proposed API look like?
const app = createApp(App)
app.mount('#app')
app.runWithContext(() => {
  getCurrentInstance() === app._instance // true
})

The existing behavior is more flexible as it allows differentiating if you are running within a component + runWithContext().
If anything, I would say getCurrentInstance() should be null within runWithContext() but I think it's fine to keep the behavior unspecified. The goal of runWithContext()
The questions are: why do you need the app._instance for? Where are you accessing it right now given it's a private property that is only used for Devtools?

Well, given that, the following code does something illegal -
const app = v.createApp(
  v.defineComponent({
    setup() {
      const instance = v.getCurrentInstance()
      setTimeout(() => {
        console.log(instance === app._instance)
      })
    },
  })
)
app.mount('#app')

One might even argue that getCurrentInstance should not be allowed anywhere except for DevTools.
In all seriousness my use case is pretty much the same as for plugins. Except plugin installs require boilerplate code and, well, installing the plugin. While most of the time I just need to know under which Vue app my code currently runs. Specifically, I need access to created App, not app._instance, but without the inconvenience of exporting app or defining a plugin.
Actual usage of this for me involves classes and decorators, which would not make for a good example, however.

One might even argue that getCurrentInstance should not be allowed anywhere except for DevTools.

Not at all, it's actually pretty useful. It's used to know if we are in the context of a component's setup.

In all seriousness my use case is pretty much the same as for plugins. Except plugin installs require boilerplate code and, well, installing the plugin

I see. Then I think you should stick to plugins, it's better to not introduce yet another (and more obscure 😄 ) way of doing things. You get the current app directly on the plugin function's first argument. Unless there is something that cannot be achieved by plugins, this doesn't seem to be worth pursuing. If you find some, a well-defined use case would definitely help!


Update portuguese translations; COUNTRY=mozambique

Description
Add missing translations
How to test the feature:

[ ]
[ ]

Checklist - did you ...

Test your changes with

[ ] REACT_APP_COUNTRY=rbd yarn start
[ ] REACT_APP_COUNTRY=cambodia yarn start
[ ] REACT_APP_COUNTRY=mozambique yarn start
[ ] Add / update necessary tests?
[ ] Add / update outdated documentation?

Screenshot/video of feature:

More updates will follow when https://github.com/WFP-VAM/prism-app/issues/1262 is addressed


New Architecture landing page

Adds content to the New Architecture landing page, which should introduce the New Architecture and direct the reader to the relevant content for them.

Pushed a few updates, but I stopped on updating the brief descriptions of the pillars for now, since I asked a few more questions; I'm interested in what y'all think are the most important things to say about each in a one-line summary


Can this plugin co-exist with Onemind-Services-LLC/netbox-metatype-importer

Hi,
I used Onemind-Services-LLC/netbox-metatype-importer to selectively import a collection of device types and modules.
(https://github.com/Onemind-Services-LLC/netbox-metatype-importer)
Will the Device-Type-Library-Import module honor the already imported types and modules, or try to overwrite them?

Hello, if the object is the same then it should not overwrite. That being said I would have to test this further to make sure that is correct. You could test this yourself by trying a single import for one that already exists


[Linear]: Make use of autoFocus prop in Sub Actions

Description
This PR makes use of the new autoFocus prop on Action Items. Docs here.
Screencast
Notice that in this demo, when I select "Set Status…", the current status item is auto focused ✨
https://user-images.githubusercontent.com/372831/201091483-62ae4292-3b54-40c2-85d4-66a5c3a7a7e1.mp4
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@mathieudutour yep, just noticed and removed.

Very nice addition that makes it more intuitive to use the action panel submenus, ship it 👏

🚀


fix: Prints correct prerelease count

Nothing of real importance but it took me a while to figure out why the action found more prereleases than the repo actually has.

Thanks for the PR, I'm so sorry for bothering you with my carelessness!

No worries, thanks for creating the action in the first place!


poolTester Test Suite Hangs

The poolTester test suite is run using ./poolTester runScript -s scripts/master but it hangs and fails to complete when I try to run it.  I can run individual poolTester tests such as:
% ./poolTester runScript -s scripts/repeatedHardRestart
% echo $status
0
%

And the killPlumbedWorker script fails with usable debugging information before scripts/master hangs.  I don't know which test is causing poolTester to hang.

If I run the tests individually nothing hangs??  Strange:
% date
Wed Sep 13 15:30:54 EDT 2017
% foreach script ("scripts/flushWorkers" "scripts/hardRestart" "scripts/killPlumbedWorker" \
"scripts/replaceIdleFirst" "scripts/restartFullHouse" "scripts/shrink" \
"scripts/restartWithPeriodicQueries" "scripts/deferredWorkerActivation" \
"scripts/fastFlush" "scripts/fastHardRestart" "scripts/hardStop" "scripts/stop" \
"scripts/hardRestartNoResume")
foreach?   echo $script
foreach?   ./poolTester runScript -s $script
foreach? end
scripts/flushWorkers
scripts/hardRestart
scripts/killPlumbedWorker
2017-09-13 15:31:36 >>> Warning: Pool log does not match 'scripts/killPlumbedWorker.log'.
2017-09-13 15:31:36 *** Stripped (compared) log files kept as './../scratch/testpool1/log.stripped' and './../scratch/testpool1/log.expected.stripped'.
scripts/replaceIdleFirst
scripts/restartFullHouse
scripts/shrink
scripts/restartWithPeriodicQueries
scripts/deferredWorkerActivation
scripts/fastFlush
scripts/fastHardRestart
scripts/hardStop
scripts/stop
scripts/hardRestartNoResume
% date
Wed Sep 13 15:45:41 EDT 2017

killPlumbedWorker fails on solaris also. It provides a manifestation of a bug where old generations don't get collected as they should.
I haven't had an issue with the master script hanging though.
You should be able to tell how far it gets by looking in the scratch/testpool1 directory. There will be a subdirectory for each script that the master script runs labeled script0, script1 ... script
The script subdirectories have a log file, so you can see what the pool has logged so far.


There is no model yet -> There are no models yet

Should be "there are no models yet"

Fixed by https://github.com/containers/podman-desktop-extension-ai-lab/pull/1042


tensorflow 1.12.0 install package requires protobuf>=3.6.1 but comes with protobuf==3.6.0

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
binary
TensorFlow version (use command below):
Python version:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

('v1.12.0-0-ga6d8ffae09', '1.12.0')
You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior
If you download the Python 2.7 CPU-only official whl file (following https://www.tensorflow.org/install/pip) https://storage.googleapis.com/tensorflow/linux/cpu/tensorflow-1.12.0-cp27-none-linux_x86_64.whl, you will see that it requires protobuf>=3.6.1.
However, after you extract it and see the include files, they are protobuf==3.6.0.
Describe the expected behavior
The protobuf version should be consistent.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
wget https://storage.googleapis.com/tensorflow/linux/cpu/tensorflow-1.12.0-cp27-none-linux_x86_64.whl
unzip tensorflow-1.12.0-cp27-none-linux_x86_64.whl
less tensorflow-1.12.0.dist-info/metadata.jsoin
less tensorflow-1.12.0.data/purelib/tensorflow/include/google/protobuf/stubs/common.h
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Ideally it should be consistent, but most packages are expected to be compatible between patch release versions.
Unless this is causing a breakage for you, this is not a problem.


Documentation: beforeShowDay

I find it difficult to understand beforeShowDay, since there are no examples given in ReadTheDocs.  I have Googled and searched StackOverflow extensively and have not found one working example.
In below code, I would like to add a class onto the selected day.  Instead it adds it onto all days.  The variable "date" is returning every date shown in the current view.  (See console).
More specifically, I want to either:  add a class to the parent row of the currently selected date, OR add a class to currently selected date + next 4 (mon-fri).  Either should be sufficient to make my week-picker work.
Version
1.7.1.
Example code
`
 beforeShowDay: function(date){
   var d = date;  //returns all days shown in calendar
   if (d) {
      console.log ("d: " + d);
      return { classes: 'activeClass' };
   }
}

`
Codepen
As you can see in the Codepen, it turns all days pink (activeClass) because "date" is all the dates.
https://codepen.io/btn-ninja/pen/WEYvMO

@btn-ninja Seeing this is an old issue, it might no longer be relevant, but anyway:
The beforeShowDay function is called for each day separately. date in your example isn't all days shown in calendar per se, but rather the beforeShowDay function is being called for each of the days separately.


Is incremental coverage supported?

Xgo is working on a similar tool, the UI is still under refactoring. And I see this repository is doing this.
Are you going to support incremental coverage and CLI tool to display locally?
https://github.com/xhd2015/xgo/pull/106

Chances are, maybe xgo can opt in into this tool?

sure, what are the requirements?

sure, what are the requirements?

When working a large code base, reviewing coverage of each file sucks as there were too may files.
Incremental coverage is a way to improve this experience. It filters out files not changed compared with master or main, which can be achieved by doing a git diff. And more, it should also filter out lines not changed within updated file.
This way, only changed code need a care on coverage.
How do you think?

Understood, let me think about how to do it.

@xhd2015 can you open a pr here to create cover.out with your tool here? I want to see what it looks like.

@xhd2015 can you open a pr here to create cover.out with your tool here? I want to see what it looks like.
edit --
doesn't look like your tool does the incremental part, is the .out file generated by go tool?

Sure, let me do this later.
Actually it does, but that part of code is still being open-sourcing. So now only binary is released.But soon the code will be opened.

would simply diffing main.out and current.out work?

would simply diffing main.out and current.out work?

Maybe. I can try that

I think that diffing the cover.out and then creating the html will work. I am a bit sick but I will be able to write some tests in the next few days.

it works:
https://gha-common.github.io/go-beautiful-html-coverage/1995226f86dae3c251d4ee590f9083cacb633c9d.html
https://gha-common.github.io/go-beautiful-html-coverage/1995226f86dae3c251d4ee590f9083cacb633c9d-inc.html
https://gha-common.github.io/go-beautiful-html-coverage/main.html

making some progress on having dark and light themes from github and refining the UI.

I don't think it will be as feature rich as the one you posted tho.

making some progress on having dark and light themes from github and refining the UI.

I don't think it will be as feature rich as the one you posted tho.

Amazing! At least this is the first step to make it work!

UI progress https://kilianc.github.io/pretender/test/#file0

@xhd2015 how do you get information about your base branch in your tooling? For example in feature-a branch, how do you compare it main? do you checkout main and run the tests? Is the coverage saved somewhere?
If this was a cli, like go run go-beautiful-html-coverage what would be the arguments?

Just merged into main, I need to add a "incremental button" to the UI and then I'll focus on the CLI.
@xhd2015 how do you get information about your base branch in your tooling? For example in feature-a branch, how do you compare it main? do you checkout main and run the tests? Is the coverage saved somewhere?
If this was a cli, like go run go-beautiful-html-coverage what would be the arguments?

This part of diffing is not open sourced yet, I'll work on this later.
Basically it just uses the exec.Command to spawn some git diff process and capture the output.

but that's not enough to diff the coverage, a change on foo.go#13 might affect coverage of func Bar in bar.go#56. The diff won't help you understand the impact of your code changes on coverage.
You need a full coverage diff against the base branch of your PR. When running locally, where do you get the coverage from? run the tests on main and cache them?

Oh so you are right, I missed the affect-chain problems... Currently only static diff is considered

closing this for now


keyboard not working after changing language

i tried to change language to german, but after changing it keyboard input doesn't work anymore.
Neither virtual touch keyboard nor physical keyboard.

Same here. Changed system to german, keyboard pinput doesnt work anymore.

Same as https://github.com/leapdroid-team/leapdroid/issues/43


Leverage "Column Names as Contracts" ideas to (auto)generate column tests

Noel, one of our community members posted an article from Emily (Capital One) on our discord: https://discord.com/channels/752101657218908281/789211881117057064/807763141526028338
Which refers to the idea of using column names as contracts:

https://emilyriederer.netlify.app/post/column-name-contracts/
https://emilyriederer.netlify.app/post/convo-dbt/

The TLDR of these articles are that if you use strong column naming conventions such as: ID, DT, CAT you can directly from the column name have some assumptions such as something may have certain values to expect (e.g for categorical columns main you have a finite amount or terms, IDs should be unique and not null, dates should be within a certain range etc.)
If this is something people choose to use in their data models, we should be able to auto generate tests for them.
Probably the easiest and most explicit thing to do in a first version is to give users a way to configure a series of mappings in a yaml document which could look like the following:
- auto_tests:
  - pattern: '^ID_'
    test_rules: ['unique', 'not_null']
  - pattern: '^CAT_'
    test_rules: ['allowable_values']
    test_arguments: ['cat_a', 'cat_b']

dbt-sugar could then "evalute" (in a safe manner) these configs and propose tests based on those column conventions.
A similar start of an idea is in discussio in #24 in which we propose the idea that if a column is named as the primary key in the {{config()}} of a model that we could automatically propose a ['unique', 'not_null'] test on this column to the user as they document things.
This could also lead to the birth of a new dbt-sugar task which could be called auto-tests (or we'll find something sweeter later) which would iterate over all of the models of a dbt-project and add tests based on those user rules.
Later, later, we could offer a way for people to share their user pattern/configs so that people could maybe install "packages" of configs into their dbt-sugar projects.

I like the idea, but I am not sure the CAT_ test_arguments would work as every column this applies to may have different values.
I also wonder if calling this auto_tests is broad enough vs calling it something more generic like model_vocabulary and thinking about level 1, 2, and 3.
This way the vocabulary can be used to test that attribute names follow the convention, auto generate starting yml with column descriptions, and auto create the tests as suggested.


No validator here as in Textform field

Hi, It's very beautiful. Very Nice. The only problem is there is no validator. How can I set it as mandatory field. Please kindly add validation as in textform field. Loved it.

Hi @imnimeshdev  Thanks for reporting this issue.
Validator has been added in the new version of animated_hint_textfield
Feel free to reopen the issue if problem presists.


flexDirection seems to be set to column-reverse in 0.60.*

Description
After upgrading to RN 0.60.* from 0.59.10, we noticed everything was rendering in a reverse order. I have upgraded to 0.61.5 hoping it would fix the issue but it did not. This issue can only be seen on iOS running on a device. Android device/emulator and iOS simulator render everything in order.
According to RN documentation, flexDirection: column is by default but it doesn't seem to be the case. It seems like it is being set to column-reverse. I applied flexDirection: column manually to our main component and then everything rendered in order.
I started putting breakpoints in some of RN's files like the RCTView.m and RCTUiManager.m, it looks like RCTShadowView in uiBlockWithLayoutUpdateForRootView method of RCTUiManager has direction set to LTR but it's property layoutMetrics has direction set to RTL and this seems to be the issue. I'm not 100% since I'm not familiar with the codebase but having a mix of layout directions on a same object doesn't sound right.
We tested this on two different iOS Devices:

iPhone 8 with OS 13.2
iPhone 7 Plus with 11.2.1

React Native version:
System:
OS: macOS Mojave 10.14.4
CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Memory: 809.16 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.14.1 - ~/.nvm/versions/node/v10.14.1/bin/node
npm: 6.9.0 - ~/.nvm/versions/node/v10.14.1/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 27, 28
Build Tools: 27.0.1, 28.0.3
System Images: android-22 | Google APIs Intel x86 Atom, android-26 | Google APIs Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
IDEs:
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
solidarity-react-native: 2.0.2
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Upgrade your existing app to 0.60.* or even 0.61.* (I have tried both hoping it would fix in 0.61.*)
Run the app on an iOS device

The fact that this is only on device (not in iOS simulator) and only for an upgraded app really limits the ability to investigate. I wasn't sure if the upgrade was essential - are you seeing this on a clean new app? If not, it seems like something is off as a result of the upgrade process?
Given your comments about debugging in and seeing RTL behavior... what locale is this iOS device running on? Recently having looked into RTL issues ourselves we discovered some documentation issues. There may be some helpful information there?

Thank you for replying @chrisglein. I wanted to do some more debugging before replying back so I don't make a fool of myself.
I-tried-1
So I went through our upgrade process again just to make sure I didn't miss anything, and I did not miss anything. I upgraded using the upgrade tool website provided by RN.
So about the locale question, I was confused about that too at first thinking it's the locale direction, but that's not the case. Because all the text renders from LTR. And all the other apps on the device are LTR as well.
The problem we're running into is the flex layout direction. After looking more into this, I discover YGNode (yoga node) has base direction set to YGDirectionLTR but context property for the node (in this case RCTShadowView) has the layoutMetrics.layoutDirection set to UIUserInterfaeLayoutDirectionRightToLeft.
So then I started looking at when a RCTShadowView created, by default the layoutDirection is being set to LTR (UIUserInterfaeLayoutDirectionLeftToRight) but something changes it to RTL and that's the part I'm struggling to figure out. Then I landed at this line of code https://github.com/facebook/react-native/blob/v0.61.5/React/Views/RCTLayout.m#L56
This is what seems to be changing from LTR to RTL. yoganode goes in having a direction set to LTR but somehow it returns RTL and that's what gets set as the layoutDirection. I can't debug further deep because then it gets into low level code and there is no way for me to debug or have enough knowledge to do so.
I-tried-2
Then I stripped our app to a bare bone single screen example in RN with just two text components, it still rendered them in reverse.
I-tried-3
Then I created a new app with RN 0.60.*, which rendered fine in correct order.
NOTE: I tried all of the above things on the same iOS device.

If I'm understanding your response correctly, it sounds like a clean app doesn't have the issue, but your app with everything stripped down does repro it. Which seems to me like something's drifted during upgrades in your core app project (not the app code)? If you haven't already, I'd recommend checking out the upgrade helper repo for diffs on core project files to see if something was missed in the upgrade.

Sorry to bother, turns out the react-native-unity-view and Unity libs we were using somehow took control of the views. Looks like an upgrade to those libs have resolved the issue. Leaving this comment for anyone else on the same boat as I saw quiet a few people run into this issue and they reported it on react-native-unity-view.


Update JSON file access by karma/jasmine tests

Existing node JS tests (in js/test) use a combination of gulp and phantomjs to run.
phantomjs is now unsupported (and seems to be a pain to get working locally) so it would be good to refactor the tests to use karma/jasmine.
I've had a quick go at this but got stuck trying to get the test functions to access the CSV files. (If we have to we could convert them to JSON as part of the test script.)

This is mostly done with #305. But this uses karma-jasmine-jquery which hasn't been updated for a long time, and has a lot of issues with pulling in old, obsolete dependencies.
So it would be good if someone with a bit more time and karma/jasmine experience could find a more up-to-date way to access JSON files from within tests.

Recommended tag: implementation


SStables are not fully exported from .csv

10,000 rows of csv exports 10,000 rows, but 100,000 rows exports only 12513 rows.
I tried it with even higher rows, but same results.
Here's other details like, schema and codes: http://stackoverflow.com/questions/32708039/cqlsstablewriter-not-exporting-csv-fully-to-sstable-cassandra

What exact cassandra version are you using to generate SSTable?

The one creating SSTables is on windows server 2008 and i am using this version for it: v2.2.1 (Latest Development Release)
& same for EC2 instance, but thats in ubuntu.


Is this project dead?

Okay so this is a bit hypocritical, and that is not lost on me. But still, looking at this repo status one has to wonder if this has been abandoned. No for a long, long time, and no activity in issues other than people asking about new problems.
So the dreaded question, is this project dead?

Hi, sorry for the delay :) It is not dead. I have plans to upgrade to webpack 5, but it will need to wait as currently, I don't have much free time over my day job.

@swashata thank you so much for taking the time to comment on this. I'll close this now if that's okay with you.

It seems to be dead. It was an awesome project. Looking for an alternative.

@dbjpanda for now it still works for me, but I have to agree, not looking good atm. Let me know if you find anything.


Put request processing should probably lock the datastore

In the PUT request writes we first check if the node we want to insert is present. This is needed for deducing the correct HTTP status code.

Consistent with [RFC7231], if the PUT request creates a new resource,
a "201 Created" status-line is returned.  If an existing resource is
modified, a "204 No Content" status-line is returned.

These are 2 operations into the DS (first query for existence, then the actual write) while the DS is not locked. This means that somebody could change the the DS after we query but before we actually write into the datastore (i.e., he/she can insert/erase the data node we want to insert) and the status code would be invalid.

(and it's likely not just PUT, it's any method which validates whether something exists, and then goas ahead and does something.)


[Feature][python] Add basic components for CLI

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Add basic configure for CLI, which includes:

Third part CLI package
Basics usage for CLI
Document for CLI
Verify work after installation
Test on it

Use case
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

After related PR was merged, issue would auto close, cc: @jieguangzhou


[iAdvize Connector] Fixes

Showing iAdvize messages in the dialog, ignoring messages that come after the forward response
Improved logo display in dialog box

Thank you !


feat: add loading local graphql schema file

Description
For some usecases of me loading a local GQL schema is just easier then fetching the remote one (authentication required that is not so easy to set up). Therefore I'd like to propose adding this functionality also to Bruno.
This for now only loads a local file and handles it like the result of an introspection query. Long term I could see this built out further to e.g. store the schema path in the Bru file, adding file watching for the schema, etc.

Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[x] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[ ] Create an issue and link to the pull request.

Nice!
Thanks @mheidinger !


i found this error during the scroll

This bug is not occur often but only when the list goes really long and fast.
03-02 18:17:32.403  15537-15537/com.buildsystemexample.app.test_native E/AndroidRuntime﹕ FATAL EXCEPTION: main
    Process: com.buildsystemexample.app.test_native, PID: 15537
    java.lang.NullPointerException
            at com.nineoldandroids.view.ViewPropertyAnimatorICS.<init>(ViewPropertyAnimatorICS.java:22)
            at com.nineoldandroids.view.ViewPropertyAnimator.animate(ViewPropertyAnimator.java:62)
            at com.twotoasters.jazzylistview.JazzyHelper.doJazzinessImpl(JazzyHelper.java:195)
            at com.twotoasters.jazzylistview.JazzyHelper.doJazziness(JazzyHelper.java:187)
            at com.twotoasters.jazzylistview.JazzyHelper.onScroll(JazzyHelper.java:103)
            at android.widget.AbsListView.invokeOnItemScrollListener(AbsListView.java:1417)
            at android.widget.GridView.layoutChildren(GridView.java:1305)
            at android.widget.AbsListView$FlingRunnable.run(AbsListView.java:4209)
            at android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
            at android.view.Choreographer.doCallbacks(Choreographer.java:574)
            at android.view.Choreographer.doFrame(Choreographer.java:543)
            at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
            at android.os.Handler.handleCallback(Handler.java:733)
            at android.os.Handler.dispatchMessage(Handler.java:95)
            at android.os.Looper.loop(Looper.java:136)
            at android.app.ActivityThread.main(ActivityThread.java:5146)
            at java.lang.reflect.Method.invokeNative(Native Method)
            at java.lang.reflect.Method.invoke(Method.java:515)
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
            at dalvik.system.NativeStart.main(Native Method)

does this still happen for you on v1.2? can you please try that and see if that fixes the issue?

This happens to me very occasionaly usually on our users' older phones but i can't upgrade to 1.2 because I keep my minsdk at 14.

@sbaar ah, ok. i should be able to bring this down to 15. there's like no users running 14, so u should really bump ur app up to 15, but let me look at an update

@sbaar just pushed an update to 1.2.1 it should be available shortly on jcenter or prolly tmr morning on mavenCentral. lemme know if that fixes your issue

@sbaar would you issue a gradle repo on jcenter?

@jjhesk jbarr21 did
https://bintray.com/twotoasters/maven/com.twotoasters.jazzylistview/1.2.1/view

@sbaar  i am using API 21 to compile and min sdk is 16. I had to import the library into the project since there is no gradle path to include. Here is my setup code in gradle
apply plugin: 'android-library'

android {
    compileSdkVersion 20
    buildToolsVersion '21.1.2'

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 21
    }
    sourceSets {
        main {
            manifest.srcFile 'AndroidManifest.xml'
            java.srcDirs = ['src']
            resources.srcDirs = ['src']
            aidl.srcDirs = ['src']
            renderscript.srcDirs = ['src']
            res.srcDirs = ['res']
            assets.srcDirs = ['assets']
        }

        instrumentTest.setRoot('tests')

        debug.setRoot('build-types/debug')
        release.setRoot('build-types/release')
    }
}

dependencies {
    compile 'com.android.support:support-v4:19.0.0'
    compile 'com.nineoldandroids:library:2.4.0'
}

//apply from: 'https://raw.github.com/twotoasters/gradle-mvn-push/master/gradle-mvn-push.gradle'

@sbaar noticed.

I don't quite understand what the issue you're having is. It's available on maven central right now. compile 'com.twotoasters.jazzylistview:library:1.2.1'
http://search.maven.org/#artifactdetails|com.twotoasters.jazzylistview|library|1.2.1|aar

lets add this path on the readme

Resolved by #28


post v1: related posts pulling in other types of content

CEE has expressed strong interest in the related posts organism pulling in other types of content (i.e. reports, tools, products, etc). Just logging this as a requested enhancement post v1.

Actually, I think it would be helpful to log this in Jira instead of here so I can work through the backlog in one location.
@tnferrell Would you create an improvement task over there and tag it with the Post V1 epic? thanks!

Since Tanya's been out, I moved this into the Jira backlog and am closing this issue for now.


Question：the same ip of the router && Drop package at the beginning

Hello，
In a certain scenario, I encountered a problem！
The topology is as follows：
pc2 <IP_ADDRESS>
|
pc1（<IP_ADDRESS>) -  router1（<IP_ADDRESS>）- router2(<IP_ADDRESS>) - router3(<IP_ADDRESS>) -  router4(<IP_ADDRESS>)
|
router5(<IP_ADDRESS>   rp) - router6(<IP_ADDRESS>)
|
pc3 <IP_ADDRESS>
the router5 is rp.  There are routes between pc1, pc2, pc3, router2, router3, router5。but the router1、router4、router6 have the same ip。      When pc3 joins the multicast <IP_ADDRESS>, when pc1 starts to send packets, it will drop about 100 packets ，and later packets will be received。    The RPT tree can be built, but the spt tree cannot be built at first. I don't know what the problem is?

If you have duplicate IP addresses in the network, its very unlikely your going to get PIM routing to work, especially if your running network address translation.

In fact, if I change the ip to a different one, there may be serious packet drops. Is pimd not suitable for wireless routing scenarios? In addition, when the PC has multiple network cards, it may not receive data packets.

The above image is garbled and very hard to make out what your problem is, have you tried applying some Markdown markup to put your ASCII art in verbatim mode?


Mapping - Shift Channels, Unable to turn off

Please first read the documentation. Problems affecting the client, e.g. Plex or Emby should be reported there in the forum.
Describe the bug
I seem to be unable to disable Shift Channels, when ever I save and go back into Mapping, it's enabled again.
Server (please complete the following information):

OS [e.g. Linux - Ubuntu]: Unraid 6.11.0 (Docker)
Arch [e.g. Intel 64 Bit]: amd64
xTeVe Version and Build:  2.5.2 Build: 2

To Reproduce
Steps to reproduce the behavior:

Go to Mapping
Disable Shift Channels
Save

Expected behavior
I expected it to leave the option disabled after being saved.
Desktop (please complete the following information):

OS: [e.g. iOS]: Windows 11
Browser [e.g. chrome, safari]: Chrome
Version [e.g. 22]: 106.0.5249.91

I will look into this

I will look into this

Thank you.
I'm actually unsure if it does turn it on/off and its just a ui glitch.
I have tried to look but have been unable to find it, does this feature have a setting in the config?

You are right, it is not saved. I think this is a miss and will add it in


Upgrade migrate logic

This PR provides a little bit of sanity to the code:

Only migrates dataset of type dataset given that versioning only stores that kind of package, we shouldn't migrate for example: showcases.
Refactored the main CKANClient object for better architecture and testing
Refactored the tests to actually make them pass and work

I'm merging this to open another branch to work on #11, but I would love some feedback here @shevron. I tried to keep it simple as a first cleanup.


Desktop App Converter .net failures when installing/converting a Win32 app in a VM, v. 17134

Please check SO link for details:
https://stackoverflow.com/questions/51437203/desktopappconverter-woes-windows-10-v-17134

Hi @ddbb2017 -- I'm going to close out this issue. If you have updates for our docs, let us know. Thank you!

@ginami no, I'm posting it here so that Microsoft fixes their gddm UWP converter. I wasted 7 days to convert my app for the Windows store. Don't you think that is the reason why the only thing Windows store has is a crickets sound.
Anyway, that Microsoft employee did nothing. The resolution to this issue is indeed in that SO thread. It was way more simple -- to disable  "Real-time protection" in the "Virus & threat protection settings".
But is it really a fix???


Support for SwiftPM and Accio

Hey,
I tried to add this project with Accio, but a Manifest file is missing.
Can you please add this? Maybe in the roadmap to version 2 :)

Hi @rocklyve! I will look into adding this in the next version 🙂

Should be working now (#345) 🙂 Can you target the master branch and verify that it works for you as well before I release a new version?


Unable to ssh into an instance whose tenant's cidr-prefix-size=30

ssh seems to be broken when you change the subnet size.  I've noticed this on both a real cluster and on singlevm.
$ ciao-cli tenant list
Projects for user
	UUID: 7173eddb-685f-4d8e-a12c-d22668348f71
	Name:
$ ciao-cli instance add --workload 9eb90d3a-4b73-43a9-9401-728c3f000f14
Created new (pending) instance: 99200779-7e6a-4656-ae73-e9311b268d97
$ ciao-cli instance list
# UUID                                 Status Private IP SSH IP        SSH PORT
1 99200779-7e6a-4656-ae73-e9311b268d97 active <IP_ADDRESS> <IP_ADDRESS> 33002
$ ssh -i ~/local/testkey<EMAIL_ADDRESS>-p 33002
ssh: connect to host <IP_ADDRESS> port 33002: Connection refused

I can see via netcat that the instance is up and running.

I tried with the prefix set to 28 and I was able to log into an instance.

Note with the prefix of 30 there are no ip tables rules relating to SSH.  I think there might be a off by one error here.  With a prefix of 28, the last ip table rule for ssh is <IP_ADDRESS>.  Shouldn't it be 14, yes, I think it should.  It looks like the ip tables rule for the last instance in a subnet is missing.


Data visualization

Overview
This pull request contains new plots and data visualization that help answer the first two of this project's central questions:

How much of a problem is there in regards to the temperature delta during nighttime observations?
How long does it take for the telescope to respond to changes in set-temperature by on-site operators?

Data visualization that directly answer the above questions can be found in the folders doc/nb/time_plots/response_time and doc/nb/time_plots/temp_distributions/nighttime respectively. Additional data visualization of interest can be found in the folder doc/nb/time_plots

Update
As of April 10th, 2023, I have presented the aforementioned data visualization to other collaborators in the DESI collaboration. This pull request signifies the halting of data visualization work for the time being as I switch focus to developing a prediction neural network.


Create description, merchant and reportID filters

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/46043
$ https://github.com/Expensify/App/issues/46034
$ https://github.com/Expensify/App/issues/46032
PROPOSAL: N/A
Tests

Go to advanced Filters page.
Verify that description filter works and adds description part to url after saving viewing results.
Verify that merchant filter works and adds merchant part to url after saving viewing results.
Verify that reportID filter works and adds reportID part to url after saving viewing results.

Offline tests

QA Steps

Same as tests.
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/3f42bb5f-453b-4748-9a45-464422c5b543

Android: mWeb Chrome
https://github.com/user-attachments/assets/8818b9e5-1d35-4c41-ab93-aaaafc3e991e

iOS: Native
https://github.com/user-attachments/assets/415d6055-f711-4527-82f5-6d412c25008e

iOS: mWeb Safari
https://github.com/user-attachments/assets/3c741fa9-2a57-41dd-b692-8cea49c58fc3

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/5538fd58-00eb-4509-a4aa-29fe067dcd58

MacOS: Desktop
https://github.com/user-attachments/assets/78980391-8c5e-4b8f-aaf9-517187de1ced

Ready for review @luacmartins!

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@ikevin127 it's an expected result. We're just modifying URL, which later will be used to produce expected Expenses list, but BE is not ready yet.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.0.16-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/marcaaron in version: 9.0.16-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Update winograd convolution for 30_2_6 to 30_3_1

The most interesting changes are inside
src/solver/conv_winoRxS_fused.cpp
src/solver/conv_winoRxS_fused.cpp
src/kernels/Conv_Winograd_v30_3_1_metadata.inc
Measurements are on the way.

@CAHEK7 there seems to be some CI issues, could you follow through and push this PR to completion? I wish to get it in right when the next release branch is cut :)

I hope everything will pass with updated gfx94x kernels.

@junliume seems like it can be merged

@junliume seems like it can be merged

This commit needs its own staging, let me arrange it in the next round of staging :)


Fix: Hue Normalization

Closes https://github.com/adobe/react-spectrum/issues/6202
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[x] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

GET_BUILD

GET_BUILD

GET_BUILD

GET_BUILD

Tried out the ColorWheel, I can get it to fire onChange with both 0 and 360. This seems poor as it could result in an extra/ambiguous render.

I was still able to get a hue value of 360 from an onChange with the latest build. I did it by slowly dragging the handle with a mouse event. I'm not able to get it with keyboard events.


AllPublicDeclarationsHaveDocumentation doesn't check enums, actors, or nested declarations

public enum Foo {}

public actor Bar {}

/// Comment
public struct X {
    public func baz() {}
}

Foo, Bar, and baz are all public declarations, but no warning will be emitted for missing a doc comment. The same issue also exists with BeginDocumentationCommentWithOneLineSummary and UseSynthesizedInitializer (nested structs will be skipped).

Synced to Apple’s issue tracker as rdar://132401334


Fix IE8 & IE9 issues with cross-domain requests

@vdurmont here is a fix for #5

It seems great!
I'm travelling right now so I didn't have the time to test your code.
I'll test it asap

Sure, no problem :smiley:

Hey!

It seems to work fine so I'll merge it today!
Thanks for all the work!


Method to programmatically close tooltip

clickToHide is nice, but would like a way to have other components control visibility of the tooltip, i.e. toggling a checkbox immediately shows/hides an open tooltip.

Thanks @bradyhigginbotham for raising the enhancement request.
I have added new props: dismiss in order to close tooltip programmatically. Can you please install latest version 0.0.6 to verify the same.
Please let me know in case you face any issues.
Thanks
</ Pranav >


feat(explorer): As a User, I want to see a disclaimer on the expiration date

What does this PR do?
Description
Added a tooltip to provide clarity about attestation expiration dates. This enhancement helps users better understand that attestation validity is determined by the issuer and that adherence to expiration dates is optional for consumers.
Changes

Added an information icon (ℹ) next to the Expiration Date field in attestation details
Implemented hover tooltip using the existing Tooltip component
Added disclaimer text explaining the nature of attestation validity
Maintained consistent styling with the application's design system

Implementation Details

Used Lucide React's Info icon for the tooltip trigger
Leveraged the existing Tooltip component for consistency
Added tooltip content through the list item configuration
Ensured proper spacing and alignment with existing UI elements

Testing

Verified tooltip appears on hover
Confirmed tooltip text is correct and readable
Tested in both light and dark modes
Ensured responsive behavior across different screen sizes

Related ticket
Fixes #570
Type of change

[ ] Chore
[ ] Bug fix
[X] New feature
[ ] Documentation update

Check list

[ ] Unit tests for any smart contract change
[ ] Contracts and functions are documented

Hey @Chirag-S-Kotian
The right column still doesn't seem to be aligned because of the new icon:

YOu should probably give a bit more width to the left column 😉

hy @alainncls i fixed it now ,see this ,is it okay?


Prevent download of test asset on every build - instead only on test

We made a change to remove a manual download step of jasmine; however this was plugged into the gulp 'build' task, meaning it downloads the asset on every build. This is usually ok, but on a slower network connection it's noticeable as the gulp build pauses for a while as the file is downloaded.
This PR moves the download dependencies task into a subtask of the 'test' task so only when you invoke 'gulp test' does the file get downloaded.

I didn't notice the delay on my corporate network but looking over this at home has shown the download to be a bit of a blocker - it took me over a minute just then.

Wouldn't it be better to only download this file, if doesn't yet exist? Could probably use something like (fa.stat)[https://nodejs.org/api/fs.html#fs_fs_stat_path_callback] to check for its existence.

Using fs.exists to check for existence. This is a better approach as it'll only run once without something else happening like a user manually deleting that file.
Hattip @spatney.

Awesome. Thanks for taking care of this :)


TypeError: Cannot read property 'name' of undefined

I'm getting this error when executing my code:
/home/app/node_modules/source-map-support/source-map-support.js:379
return state.nextPosition.name || originalFunctionName();
^
TypeError: Cannot read property 'name' of undefined

It looks like the previous line checks to see if state.nextPosition is null, but does not check if it's undefined.

I can confirm that I found this issue too I'm rolling back from 0.5.15 to 0.5.13 for now

Annoyingly, it's one of my downstream packages which is causing this issue for me. In particular, @google-cloud/trace-agent: https://github.com/googleapis/cloud-trace-nodejs/blob/master/src/util.ts#L265

@kjin any chances @google-cloud/trace-agent can pin source-map-support version ?

You can pin it yourself by adding your own source-map-support dependency on 0.5.13 exactly, npm should de-dupe it: https://gist.github.com/kjin/1b0ec56149f9db708922460f66a94df0

@kjin good point! Thanks! For the sake of others running into this problem, would it make sense to pin it directly in your package directly anyway?

Was out traveling today so got to this late, fixing this now 🐎

Published as 0.5.16 🚀


Update Time Zone Entities documentation

Announce TimeZoneRule's deprecation
Remove duplicate reference in "See Also"

Signed-off-by: Shubham Sharma<EMAIL_ADDRESS>

@phecke the sample was a duplicate entry. It was already there in the "See Also" section.

Awaiting review from @NHelgren on this.


Docs link corrected to the relative path.

it should be ../quickstart, not configuration/quickstart. I have corrected the relative path and now it should redirect to the relevant page.

Thanks!