Add example for configuring TIA_IncludePathFilters

I wanted to tune the test impact analysis in my pipeline, and it took me way longer than I feel it should have to to figure out exactly where to set the TIA_IncludePathFilters variable.
Having a simple YAML example would go a long way to help people figure this out faster.
While I'm at it, is there a reason there is no simple, straightforward way to modify this property? I would assume situations such as not wanting to have to run a full build when the README.md file is changed are common enough that it would merit making this property a first-class citizen on the pipeline task.
Lastly, I could be wrong, but it seems like there is a typo where under Manage Test Impact Analysis behavior it states that the variable is TI_IncludePathFilters, when I believe it should be TIA_IncludePathFilters.

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

ID: 66e098a7-83b4-c389-3d30-21ad3446b76c
Version Independent ID: cafbcbd5-3321-88cf-eeaf-038d49ec0ada
Content: Use Test Impact Analysis - Azure Pipelines
Content Source: docs/pipelines/test/test-impact-analysis.md
Product: devops
Technology: devops-cicd
GitHub Login: @PBoraMSFT
Microsoft Alias: pbora

@josh-degraw Thank you for the feedback, assigning this to the author for review.

Bumping this as I'm unable to find out where I should configure tia_includepathfilters. The documentation tells us we need to set it but not where. Anywhere? .runsettings? yml? It's a useless feature if you can't find it!

@qujck It's been a while since I dealt with this, but if I remember correctly, I think I just put it at the top of the azure-pipelines.yml file.

+1

Also bumping this as I've unsuccessfully attempted to use TIA_IncludePathFilters today. Following on from an above suggestion I included this at the top of my .yaml build file, but the build failed with the following message:
Unexpected value 'tia_includepathfilters'
I echo the comment that a simple YAML example would be useful.

Also bumping this as I've unsuccessfully attempted to use TIA_IncludePathFilters today. Following on from an above suggestion I included this at the top of my .yaml build file, but the build failed with the following message:
Unexpected value 'tia_includepathfilters'
I echo the comment that a simple YAML example would be useful.

Adding @shashban to help.

Adding @shashban to help.

+1 An example of this would be appreciated

So, where do we set TIA_IncludePathFilters? In the project file of the test project?

If someone is still looking for a hint, here's an example of usage that works in my case
      - job: Build
        variables:
          - template: templates/variables.yml
          - name: TIA_IncludePathFilters
            value: "!**\*.csproj"
        steps:
          - template: templates/build.yml

#reassign:@PBoraMSFT


Setting for tab complete for nicks to append :

Instead of simply completing the nickname, have the option to append :  (or any other string) to the end if the nickname is the first word in the message.

Duplicate of #1176 and several others.


Parameter wrapping incompatible with ktlint with long function parameter

Current ktfmt formatting:
private fun testWrapping(
  testParameter:
    (
      longEnoughNameToForceMultilineParams: MyVeryLongObject,
      anotherVeryLongName: ALongObject) -> Unit
) {
  // foobar
}

What ktlint expects:
private fun testWrapping(
  testParameter: (
    longEnoughNameToForceMultilineParams: MyVeryLongObject,
    anotherVeryLongName: ALongObject
  ) -> Unit
) {
  // foobar
}

I think the ktlint formatting looks better.  The ) on a new line would be standard for "google-style".  The ( not being on its own line is a bit more compact and it's more obvious what the parens are "attached" to.  However, the current style is similar to the version with a scoping function, e.g.: (Acceptable for both ktfmt and ktlint)
private fun testWrapping(
  testParameter:
    suspend (
      longEnoughNameToForceMultilineParams: MyVeryLongObject,
      anotherVeryLongName: ALongObject,
    ) -> Unit
) {
  // foobar
}

Similar issue:
Original (and ktlint's version, and my personal preference):
typealias Listener = (
  aVeryLongFoo: String,
  anotherVeryLongFoo: String,
  aThirdVeryLongFoo: String,
  aFourthVerylongFoo: String
) -> Unit

ktfmt's version (google-style, FWIW):
typealias Listener =
  (
    aVeryLongFoo: String,
    anotherVeryLongFoo: String,
    aThirdVeryLongFoo: String,
    aFourthVerylongFoo: String) -> Unit

Fixed by 1bebf0bc4677832a2b7004acf42a938baecd565a, closing.


Cannot provision a "modern" site to the "tenant.sharepoint.com" URL.

Category

[ ] Question
[ ] Typo
[X] Bug
[ ] Additional article idea

Expected or Desired Behavior
It is not possible to provision a "modern" site using the "root" or default "mytenant.sharepoint.com" URL. I attempted to do this using the PnP PowerShell commands and also using the "Create a site" wizard on the new admin portal, both with similar (failed) results.
Steps to Reproduce
Using PnP PowerShell, with the following commands
Connect-PnPOnline -Url https://mytenant-admin.sharepoint.com
New-PnPSite
    -Type CommunicationSite
    -Title "Communication Site"
    -Description "Communication Site"
    -Url "https://mytenant.sharepoint.com"
    -Classification "classification"
    -SiteDesign Showcase

The response message I got was
New-PnPSite : {
    "error": {
        "code" : "-2147024894, System.IO.FileNotFoundException",
        "message" : "File Not Found."
    }
}

I also attempted to do this via the new admin portal, with no success. It seems there is no way to define the URL and you are forced to only add new sites under the /sites or /teams paths. Here is a screenshot of it:

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

ID: 1114c203-314e-f97a-a8a4-d4f5ec73af0e
Version Independent ID: 79c90765-56a2-9d05-9ace-83cd71fc0fde
Content: Provisioning
Content Source: docs/solution-guidance/modern-experience-customizations-provisioning-sites.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

This is indeed by design as it's also not supported to delete the root site collection from your tenant as that will cause long-lasting issues. We will be releasing new cmdlet and CSOM APIs to modernize your classic root site collection. Also - all new tenants have already communication sites created to the root site collection. If you have already deleted the root site collection using some method, please contact support using the tenant admin support pages to get your situation resolved.


Fixed possible run-time check failures

Run-Time Check Failure #1 - A cast to a smaller data type has caused a
loss of data.

Also fixed the case when someone trying to use bgfx in debug mode without RenderDoc headers.

RenderDoc header is here: https://github.com/bkaradzic/bgfx/blob/master/3rdparty/renderdoc/renderdoc_app.h
Where do you get these run-time checks failures?

With VS2013 with my own project settings.
Here is a screenshot:

VS2013 is the vanilla community edition one, and here are my settings in case you need them:
NotUsing
Disabled
ProgramDatabase
true
true
_HAS_EXCEPTIONS=0;%(PreprocessorDefinitions)
true
false
Async
true
MultiThreadedDebug
true
Fast
false
None
/Gw /Zc:rvalueCast %(AdditionalOptions)


Update dataset metadata in Time-resolved Systems Immunology Reveals a Late Juncture Linked to Fatal COVID-19

The datasets in Time-resolved Systems Immunology Reveals a Late Juncture Linked to Fatal COVID-19 should be corrected to:

[ ] Use 'blood' rather than 'Blood' as the tissue label
[ ] Use 'normal' and rather than 'Normal' as the disease label as indicated by PATO:0000461

During migration, we will remove the fields containing labels, and allow the Portal to assign the correct label.
Is this ticket still necessary?

resolved via migration to 2.0.0


3DMM

What is the function of the 3DMM module？

According to the parameters required for NeRF training, the 3DMM face tracker is used to obtain the internal and external camera parameters corresponding to each frame.

According to the parameters required for NeRF training, the 3DMM face tracker is used to obtain the internal and external camera parameters corresponding to each frame.

If the video is shot with a fixed camera position, will the camera parameters calculated for each frame be the same?

According to the parameters required for NeRF training, the 3DMM face tracker is used to obtain the internal and external camera parameters corresponding to each frame.

If the video is shot with a fixed camera position, will the camera parameters calculated for each frame be the same?

The internal parameters of the camera are fixed. The external parameter matrix is a matrix composed of the 3D position and posture angle of the face in the camera coordinate system obtained in each frame. Since the human face is moving, the extrinsic parameter matrices of each frame are different.


Exclude entities with length of one character

We had the idea to exclude links to DBPedia for entities with length 1. We experienced many wrong links to entities like B, ., ( and with this strategy we could eliminate all of these wrong links. I can also hardly think of a useful entity that has length one.
This is only a suggestion. Please dont implement it right away in FREME 0.4.
It might be useful to introduce a parameter to switch this behaviour on / off.

there are several options on how we can implement this:

black lists of entity mentions
black lists of regex filters - I believe with regex we can filter out also entities with length one

@jnehring do you have any example where signs like B, ., ( are spotted as entities?

These entities where detected in https://github.com/freme-project/e-Entity/issues/48 and https://github.com/freme-project/e-Entity/issues/43 . There is only one example text that produces an entity "(". Now the API call does not produce this anymore. So I close this issue.


added delta time + delta system time

There weren't any references for them previously so added them in.

Thanks!


Roll engine 7f753f8f528a..5846027dcde0 (2 commits)

https://github.com/flutter/engine/compare/7f753f8f528a...5846027dcde0
git log 7f753f8f528a1c92cc4f23957694623ad45104eb..5846027dcde082b2e43120848b1b2a97aeed76d7 --no-merges --oneline
5846027dc Roll src/third_party/skia 3349fb0195ff..e178c0586cd6 (1 commits) (flutter/engine#8763)
3493dcfba Rename tightWidth to longestLine (flutter/engine#8706)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (liyuqian@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/4951641202622464

Commit queue failed; closing this roll.


How to user the Clipboard history on Windows.

How to create a Clipboard and add to Windows Clipboard?
I want to create 2 or more item in history.

This isn't an issue with the pyperclip module. But you can do this with a program that constantly calls pyperclip.copy() to monitor the contents of the clipboard:
import pyperclip, time, pprint

contents = ''
history = []

try:
    while True:
        time.sleep(0.2)  # A slight pause so it doesn't lock up access to the clipboard.
        currentContents = pyperclip.paste()
        if currentContents != contents:
            contents = currentContents
            history.append(contents)
except KeyboardInterrupt:
    pprint.pprint(history)


draft for tutorial on odissei soda website

still need to think how to add this to the docs in the package

Hi Flavio, it's very nice! Nicely written, very clear. Just a couple of small comments:
On the first paragraph, maybe add a few words about why is it important to protect your privacy? As a person who has never done webscraping, I genuily don't know why I should care (I am sure there's a reason of course).
For the VPN providers you suggest, maybe you could clarify that they are not free (or if I misunderstood, add they are free).
Lastly, in other tutorials we end with a small conclusion paragraph summarizing what was shown (see for instance here: https://odissei-soda.nl/tutorials/post-7/). I think adding this 3-4 lines at the end can give a nice wrap to the tutorial. You can add the citation info in that paragraph as well.

closing this. the tutorial text has moved here https://gist.github.com/f-hafner/15db6a423bb9ba68f421d197bebdf61f, and the commits unrelated to the tutorial have been cherry-picked into the main branch.


Not able to use nlohmann json with c++ code built using emscripten to wasm

I am getting errors in json::parse when i am using json::parse code in my c++ and compiling that to wasm.

In order to asses your issue, we need the following information:

What is the issue you have?

Please describe the steps to reproduce the issue. Can you provide a small but working code example?

What is the expected behavior?

And what is the actual behavior instead?

Which compiler and operating system are you using? Is it a supported compiler?

Did you use a released version of the library or the version from the develop branch?

If you experience a compilation error: can you compile and run the unit tests?

FYI, we have been using this library in WASM through Emscripten for several years with no issues.

Closing the issue , will raise another with more information


iOS/Android: Text input error for screenreaders

Requires API Proposal
This issue requires a new API. An API proposal should be added and discussed before proceeding with implementation. The API proposal can be added in the comments of this issue or linked as a separate issue.
Description
Cannot specify error text on TextInputs. Errors for form fields, while they can be displayed visually in many unique ways, need to have a strong association with the problematic field itself for accessibility. Otherwise, any users who can't visually see the relation of the error to the field won't necessarily know which field is the problem.
React Native version:
v0.63
Expected Results
Upon focus of a text input in an error state, the error message specified should announced after the main focus announcement, prefixed with "Error: ". Upon changing the contents of a text input which puts the input into an error state, an error message should be announced prefixed with "Error: ".
Snack
https://snack.expo.io/X4NIqnJ2K
Android Details
To implement error states on Android, you should call the setError method of the TextView.  This will automatically set the correct properties on the AccessibilityNodeInfo that will inform screen readers to this state. If you need to do this manually, what this does behind the scenes is call setContentInvalid(true) and setError(youErrorString) on the AccessibilityNodeInfo.
iOS Details
iOS has no standard pattern for the presentation of error states on text inputs, so I'd recommend we follow Android's pattern here.  To do this, you'll need to implement a key press listener, and on change, detect if the field is now in an error state.  If it is, you'll need to make a manual screen reader announcement of the error message, and append this message to the accessibilityValue for the field.

API Proposal:
This will require adding a new prop to JS, and Android and iOS changes to use that prop.
JS
Add a new prop to TextInput:
  /**
   * String to be read by screenreaders to indicate an error state. If this value is
   * not null, an error will be announced. You can use onChangeText or onBlur to
   * detect an error and set this prop. Once the error is gone, set this to null
   * to clear the error
   */
  errorMessage?: ?Stringish,

Example usage:
In this example, the TextInput goes into an error state if the user types "error" into the TextInput.
export default function Playground(): React.Node {
  const [text, setText] = React.useState('');
  const [error, setError] = React.useState(null);
  return (
    <TextInput
      error={error}
      onChangeText={newText => {
        setText(newText);
        setError(newText === 'error' ? 'this input is invalid' : null);
      }}
      value={text}
    />
  );
}

Note: onChangeText may not be the right place to announce the error. This API gives flexibility to set the error when needed. Another place might be onBlur, which is when the TextInput loses focus.
Implementation Thoughts
On Android, implementation will follow the suggestions in the issue. To avoid visual styling, we will call setContentInvalid(true) and setError(youErrorString) on the AccessibilityNodeInfo manually.
On iOS, since there is no way to do this sanctioned by Apple, we'll follow the recommended approach listed in the issue. The behavior will be as similar to Android as possible.

Curious to know why this was moved back onto the backlog? This is definitely something that would be a dealbreaker for me if it woldn't work as described here.

Curious to know why this was moved back onto the backlog? This is definitely something that would be a dealbreaker for me if it woldn't work as described here.

Hello! I changed teams and no longer had capacity to work on it, which is why I released the issue. It'd be really great if you wanted to pick this up, though! You can follow my proposal above if you're interested in working on this.

@blavalla I would like to work on this after completing the review of https://github.com/facebook/react-native/pull/31666 Thanks :pray:

Thanks a lot @blavalla
1- Issues iOS/Android: Text input error for screenreaders #30848 and Android: Error state change (text inputs) #30859 should be solved together (as explained in Brett comment).
2- Issue Android: Error state change (text inputs) #30859 may require updates to Android API (see test case Change of error state from onChangeText show/hides a TextInput error). I found a draft solution for the issue and I think is related to updateState. I will prepare a fix for this issue in a couple of days.
3- I tested Kacie's API Proposal (videos of my tests, my draft branch). I agree with her API Proposal. The prop name would be android_errorMessage.
4- I did not yet investigate the iOS API

I added the following test cases. I tested the PR on Fabric and Paper iOS.
76. iOS - announce lastChar (not entire text) onChangeText and avoid multiple announcements (Fabric) (link)
77. iOS - announces or does not announce the accessibilityError through Button onPress (not onChangeText) (Fabric) (link)
78. iOS - the error is announced with accessibilityInvalid true and does not clear after typing text (onChangeText) (Fabric) (link)
I'll complete the below TODOs and move the PR to ready to Review by Monday morning (New York time).

[ ] Implement changes from my own code review
[ ] Implement solution for multiline TextInput (iOS)
[ ] Further review, test and improve the pull request

iOS - Exception thrown while executing UI block: - RCTUITextView setAccessibilityErrorMessage:]: unrecognized selector sent to instance (iOS - Paper on main branch)

I'll move the PR as Ready for Review, once I complete these tasks:

[ ] fix regression in Fabric iOS. Reintroduce solution from commit https://github.com/facebook/react-native/pull/33468/commits/318a96420f0593dc59c030193009e9cba31eb666
[ ] extensive iOS and Android tests
[ ] review diff and PR summary

I moved PR https://github.com/facebook/react-native/pull/33468 Ready for Review.
I remain available for any improvement. Thanks

PR not merged, could add it as separate library

This is considered basic functionality. This should not be a library, as developers will not know of its existence and therefore render an accessibility experience that is inferior without the package installed. This should be part of core.

I'm not talking of a single fix, but creating a new clone of the TextInput component outside of react-native.
I have been contributing to facebook/react-native for 4 years full-time and I have 60 PRs. I'm also the SE that published the PR for this issue but did not make it to main.
I would keep maintaining and improving the library. Users would have the choice between TextInput component from facebook/react-native and TextInputImproved component from fabriziobertoglio1987/react-native-improved
Do you prefer to have at least a choice in this situation?
If you had no choice (at least until the PRs are merged, which may take years), would you use TextInput from an external library that includes 100-1000 fixes for TextInput and all the original functionalities?
I’m asking because I’m organizing a list of issues and I will start working on them soon. Thanks

My problem with that approach is that developers aren't going to make that choice. They won't know the choice exists, or they won't care enough to make the choice, or their hands will be tied by management/an overzealous product owner/what have you to not make the choice for all sorts of different reasons. It'd be one more thing to maintain, one more third-party dependency.
Proper error prevention and reporting is among the basics of basics where accessibility is concerned. Not getting this right is a failure of WCAG, which will get a company sued and will give users who actually need this to work a bad user experience. Apps on mobile are already being yanked under this same umbrella and it's up to the maintainers of React Native to realize that this has priority and can't be hanging out in the wings for years. If you reckon this will take years, I'm all for creating a fork of the component so there is at least an option for devs who care about not discriminating against a bunch of users. This really needs to be in main though, eventually.


Performance doesn't improve (scalability issue) with # GPUs with running train_imagenet.py

While training AlexNet CNN with ImageNet data, i don't see performance improvement (in-fact i see slight performance degradation) with increasing number of GPUs
python train_imagenet.py --data-train /local/ImageNet/MXNet_data/MXNet_data.rec --data-val /local/ImageNet/MXNet_data/MXNet_data_test.rec --gpus 0,1,2,3 --network alexnet --batch-size 256  --num-epochs 1 --kv-store device
Per epoch (and batch-size/GPU : 64),
With 1 GPU, Time-cost : 910 sec
With 2 GPU, Time-cost : 924 sec
With 4 GPU, Time-cost : 964 sec
I have 4 Titan Xps
However, with synthetic data (as shown in the demo https://github.com/apache/incubator-mxnet/blob/master/example/image-classification/README.md) i see good scalability.

 How many cores do you have on your CPU? If more than 4 then try to set --data-nthreads N where N is number of threads to do IO. By default MXNet uses only 4 cores to do IO. You may also limit augmentations you perform (by default train_imagenet script performs a lot of augmentations).
I am in the process of improving image IO (#7152), that should also help.

Thank you, ptrendx.  That helps, but with 4 GPUs there isn't any performance gain
% i limited the augmentations by setting 'data.set_data_aug_level(parser, 0)'
%set data_threads to 8 (I have 8 physical cores)
python train_imagenet.py --data-train /local/ImageNet/MXNet_data/MXNet_data.rec --data-val /local/ImageNet/MXNet_data/MXNet_data_test.rec --gpus 0,1,2,3 --network alexnet --data-nthreads 8 --batch-size 1024 --num-epochs 1 --kv-store device
With 1 GPU, Time-cost : 680 sec
With 2 GPU, Time-cost : 373 sec
With 4 GPU, Time-cost : 378 sec
So,

As I said, alexnet is a very small network, so with 8 physical cores you probably will not get a much better scaling result with those GPUs.
Still, IO speed is a big problem going forward even for larger networks and that is why we are working on ways to improve it (besides my PR see for example #7092)


Option to populate model from DOM on initializing bindings

At the moment when you initialize the view bindings if the inputs you are binding to already have values that have been populated from the server they will be overwritten by the model defaults where in many cases you might want the model defaults to be overwritten by what is passed from the server.
A config option could be created to determine whether to sync from DOM to model or Model to DOM on initializing. Perhaps there is a way to do this already but I couldn't find it after searching for a few hours.
Thanks

I'm also looking to be able to do this.


Added Slice as its own type info in userland

There are a few reasons why we want this:

Checking if something is a slice becomes trivial.
The pointer properties of the slice are immediately available. No need to get the ptr field and @typeInfo that.
When @createType/@reify becomes a thing, this will make it possible to actually construct slices.

This is only a userland change. The backend still treats slices as structs.

Didn't realize that I got #1000. Nice :confetti_ball: :fireworks:

Good idea


add Bugsnag to list of supported crash reporters

I've performed compatibility testing and have confirmed that it's possible to send an ANRError to Bugsnag by calling Bugsnag.notify(error). I've added bugsnag to the list of working crash reporters, and also took the liberty of updating hockeyapp to use https rather than http.

:+1:


holistic file does not exist

bat version:0.1.0
Python version:3.10.12
Operating System:linux

Description
In https://github.com/IBM/benchbench/blob/main/src/bat/utils.py#L7
it seems that the combined_holistic_20240708.csv file mentioned in this line of code does not exist.
What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

hello，has the code been updated?

The readme and example are fixed.
closing this issue, thanks again.
LMK if you need further help


chore: github workflow for publishing to pub.dev

https://github.com/marketplace/actions/dart-and-flutter-package-publisher

I don't think we want to publish the app and designer package.
Also this is not using melos, so it cannot figure out in which order to upload the dependencies.
But I think you can adjust the order of steps so it always first uploads:

core
flutter_common

Oh, and this seems totally fine and a great idea. Hope it works.
I think you should be able to do all the required steps now by yourself, but let me know if this is not the case.

Thanks for the feedback. I'll leave the dryRunOnly field active for the next test run and remove it if everything works fine.


Update instructions on updating vimrc

Maybe it would be better to use git stash instead of git reset as according to this page, a reset creates a new commit point in the branch history (probably undesirable?); stash does not.

Maybe it would be better to use git stash instead of git reset as according to this page, a reset creates a new commit point in the branch history (probably undesirable?); stash does not.

Maybe it would be better to use git stash instead of git reset as according to this page, a reset creates a new commit point in the branch history (probably undesirable?); stash does not.

git reset --hard does not create any new commit

Maybe it would be better to use git stash instead of git reset as according to this page, a reset creates a new commit point in the branch history (probably undesirable?); stash does not.

git reset --hard does not create any new commit

Thanks, folks 🙏


docs: update docs for JWT revocation

Description:
Update JWT revocation docs following the update in implementation introduced by this PR
Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist:

[ ] My PR follows the contribution guidelines of this project
[ ] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked the PR title to follow the conventional commit specification

@shotexa, you need to merge the megalinter fixes from this PR
And if you add [skip ci] to the PR title, the build will pass much faster ;)


Unsupported class file major version 60

I added your dependency to my project and I have gotten "Unsupported class file major version 60" error after run project.
help me to solve this problem, thanks.

I added your dependency to my project and I have gotten "Unsupported class file major version 60" error after run project.
help me to solve this problem, thanks.

Hello, you need to use Java 16 to run this project, you are probably on Java 8 or 11

Java Version: 16
Gradle Plugin Version: 4.2.1
Gradle Version: 6.7.1
And this is my build.gradle :
plugins {
    id 'com.android.application'
}

android {
    compileSdkVersion 30
    buildToolsVersion "30.0.3"

    defaultConfig {
        applicationId "com.yarinweb.whatsapptools"
        minSdkVersion 16
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_16
        targetCompatibility JavaVersion.VERSION_16
    }
}

dependencies {

    implementation 'androidx.appcompat:appcompat:1.2.0'
    implementation 'com.google.android.material:material:1.3.0'
    implementation 'androidx.constraintlayout:constraintlayout:2.0.4'
    testImplementation 'junit:junit:4.13.2'
    androidTestImplementation 'androidx.test.ext:junit:1.1.2'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.3.0'

    implementation 'com.github.auties00:whatsappweb4j:1.2'
}

Java Version: 16
Gradle Plugin Version: 4.2.1
Gradle Version: 6.7.1
And this is my build.gradle :
plugins {
    id 'com.android.application'
}

android {
    compileSdkVersion 30
    buildToolsVersion "30.0.3"

    defaultConfig {
        applicationId "com.xxx.xxxx"
        minSdkVersion 16
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_16
        targetCompatibility JavaVersion.VERSION_16
    }
}

dependencies {

    implementation 'androidx.appcompat:appcompat:1.2.0'
    implementation 'com.google.android.material:material:1.3.0'
    implementation 'androidx.constraintlayout:constraintlayout:2.0.4'
    testImplementation 'junit:junit:4.13.2'
    androidTestImplementation 'androidx.test.ext:junit:1.1.2'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.3.0'

    implementation 'com.github.auties00:whatsappweb4j:1.2'
}

Try to set the release option to target java 16

How can i do it?
When I run app in debug mode on a emulator, get this error!

This is you running the wrong version of java -
The maven and gradle options have been supplied -
If you still have difficulties setting the java version which you are using..... get the idea?
This isn't a school, it's an issue and help forum

How can i do it?
When I run app in debug mode on a emulator, get this error!

what version of android are you using?

This is you running the wrong version of java -
The maven and gradle options have been supplied -
If you still have difficulties setting the java version which you are using..... get the idea?
This isn't a school, it's an issue and help forum,
Try an online Java course

Thank You.
Can I Try an Offline Java course or must be an online course?

How can i do it?
When I run app in debug mode on a emulator, get this error!

what version of android are you using?

Api Version 30

Api Version 30

I doubt they are running Java 16 on Android 11 as it was released in September 2020, while Java 16 was released in March of this year.


Connect CardanoBlock node to current mainnet

We should test the following: start a (cardano-)node running CardanoBlock from a non-empty database created by a node running ByronBlock and let it connect to other nodes running Byron to see whether it really is compatible.
We expect compatibility among two axes:

It must be able to read the blocks from disk. As the ledger database is not compatible, it will read all blocks from disk.
Network compatibility: it should be compatible with V1 of the NodeToNode protocol and V1/V2 of the NodeToClient protocol.

First point was addressed in #2385.


MONDO:0007736 HPA 1 Recognition polymorphism, beta-globin-related[Obsolete]

Mondo term (ID and Label)
MONDO:0007736
HPA 1 Recognition polymorphism, beta-globin-related
Reason for deprecation
From the OMIM x-ref: "This entry is included in the database for historical reasons; the beta-related HpaI RFLP was the first to be discovered."
This is describing DNA polymorphism that was found in association with sickle-cell trait, not actually a disease entry from OMIM.
Suggested term to consider
MONDO:0011382 sickle cell anemia
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here

note to self:
sh run.sh owltools --use-catalog mondo-edit.obo  --obsolete-replace MONDO:0007736 MONDO:0011382 -o -f obo mondo-edit.obo


Android -  Setting - App crashes on tapping view keyboard shortcuts

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch the app
Log in with any account
Go to Setting  > About
Click " View Keyboard Shortcuts"

Expected Result:
Information about keyboard shortcut  should appear
Actual Result:
App crashes all the time
Workaround:
Unknown
Platform:

Where is this issue occurring?

Android

Version Number: v1.1.23-0
Reproducible in staging?: Yes
Reproducible in production?: option not available
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/147143103-24a41d90-4c69-489a-b9e9-f092ad4f2f4e.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Triggered auto assignment to @tylerkaraszewski (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Cc: @akshayasalvi this should not be visible on native devices.

Noted. @parasharrajat I've raised a PR to fix this.

Cc: @akshayasalvi this should not be visible on native devices.

Why? This should work on native devices too, no? Why restrict it? It should just work.

Yeah, Now we can rethink this after https://github.com/Expensify/App/issues/6883. I said so as we didn't have keyboard shortcuts for native.

But definitely crash should not happen as It is just a modal and should work on native devices too.  Meantime, I have requested the hold on the PR.

Just merged https://github.com/Expensify/App/pull/6881 to unblock deploys, but I agree we should enable keyboard shortcuts on native in https://github.com/Expensify/App/issues/6883. I thought it would be better to unblock deploys to @jasperhuangg can take his time with https://github.com/Expensify/App/issues/6883

Does someone want to take this from me? I logged in to see this hourly issue with a bunch of activity already on it and apparently it's no longer a deploy blocker?

Sure, I can grab this from you @tylerkaraszewski

It should be fixed in 1.1.23-1

Thanks!

Closing this out per https://github.com/Expensify/App/issues/6860#issuecomment-1000600647


Add the ability to control the backlight brightness

I'm not 100% sure whether this backlight pin is intended to be PWM'd, given the way it cuts in fairly bright already and then tops out around 13-14% duty cycle, but this does give some control over brightness.

I think this all got cherry-picked into #8 thank you!


Add tests showing how signatures work

Generate JWT public key as X and Y coordinates, from a non-compact secp256k1 key

Generate a hash (input to signature algorithm) from bytes in a JWT header + payload

Added -- see https://github.com/microsoft-healthcare-madison/health-wallet-demo/blob/master/testing-endpoints.md


SQL not working on Synapse

Example: Use a nonclustered index to enforce a primary key constraint on a columnstore table
The SQL code provided under this example does not work on Azure Synapse as unable to create foreign keys or unique constraint without non enforced. Can you please advice how to maintain referential integrity in a synapse data warehouse without using primary or foreign keys?

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

ID: 3e021430-b8b5-1a96-1e71-c95d72580c0f
Version Independent ID: 9f8a8520-31ef-eb8f-3ff5-c92db7d69514
Content: Columnstore indexes - Data Warehouse - SQL Server
Content Source: docs/relational-databases/indexes/columnstore-indexes-data-warehouse.md
Product: sql
Technology: table-view-index
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@Nayyar0 -- thank you for your feedback.  Please consider these resources for your question:

DBA Stack Exchange
Stack Overflow

@MikeRayMSFT -- please look into this issue.  The code is in this section.

@Nayyar Hello and thank you for contacting Microsoft. I am sorry for the delay in response.  You are correct, primary key and foreign key referential constraint is not supported by Azure Synapse Analytics.  To add this as native support in the product, we need to first support unique constraint enforcement.  You can submit your support for this feature at https://feedback.azure.com/forums/307516-azure-synapse-analytics/suggestions/39016030-prevent-duplicate-values-allow-enforce-constraint.

@Nayyar0 Hello and thank you for contacting Microsoft. I am sorry for the delay in response. You are correct, primary key and foreign key referential constraint is not supported by Azure Synapse Analytics. To add this as native support in the product, we need to first support unique constraint enforcement. You can submit your support for this feature at https://feedback.azure.com/forums/307516-azure-synapse-analytics/suggestions/39016030-prevent-duplicate-values-allow-enforce-constraint.
I am reviewing the article for updates. A work around for enforcing referential integrity is to use IF EXISTS to not insert duplicate values.

@Nayyar0 Hello, I have created a work item to track the work on updating this article. Thank you for bringing this to our attention. I will proceed with closing this issue and will update you once the article is complete. If further communication is needed, the @notification mechanism continues to work even after an item is closed. We hope to hear from you again.

#please-close

@Nayyar0 I wanted to let you know I have updated the Columnstore indexes - Data Warehouse - SQL Server article. I have removed the support for Azure Synapse Analytics. You will see the update in the next day or so. Thank you for contributing to Microsoft Docs.


Seeking Guidance on Project Execution and Potential Sale

Dear CrimsonSunrise
I hope this message finds you well. My name is thiago, and I came across your project, blaze, on GitHub. I'm impressed by the concept and strategies implemented in the project.
I would like to explore the possibility of utilizing the project for further purposes, potentially offering it to others. However, I am in need of guidance regarding how to make it executable within my environment.
Could you please provide me with instructions or guidelines on how to set up and run the project locally? Any documentation or steps you could share would be greatly appreciated.
Thank you for your time and consideration. I look forward to your response.
Best regards,
thiago

Hello Thiago,
Sorry for answer your request before, I was quite busy lately.
You can email me at<EMAIL_ADDRESS>so we can plan to have a call or closer interaction to make it work for you too.
Best wishes.


Gobblin 1773

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1773

Description

[ ] Here are some details about my PR, including screenshots (if applicable):
We used to check the quota when we accept flow for ad-hoc flow and run immediately flow. But we only use the same execution id for ad-hoc flow. So for a run immediately flow, we will check quota once with a random execution id, and then really run the job with a different execution id and forget the first one. This will cause us to double-check the quota for a run immediately flow and never release one of them.
In this PR:

We change the behavior to only check the quota upon accepting the request when it's an adhoc job, and for run-immediate flow, we won't check the quota. If quota exceeds, we will fail the first job but still keep the config and schedule the job in the future
When we see there is duplicate flow running and skip the exception, if it is an adhoc flow, we will release the quota for corresponding execution.

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Unit tests

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3636 (d5e22ea) into master (9f8ab24) will increase coverage by 8.00%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #3636      +/-   ##
============================================
+ Coverage     40.16%   48.17%   +8.00%
- Complexity     3544     7830    +4286
============================================
  Files           791     1474     +683
  Lines         33285    58133   +24848
  Branches       3699     6692    +2993
============================================
+ Hits          13368    28003   +14635
- Misses        18601    27518    +8917
- Partials       1316     2612    +1296

Impacted Files
Coverage Δ

...org/apache/gobblin/metrics/InnerMetricContext.java
55.67% <0.00%> (ø)

.../gobblin/cluster/GobblinHelixTaskStateTracker.java
62.50% <0.00%> (-6.25%)
:arrow_down:

...in/java/org/apache/gobblin/cluster/HelixUtils.java
44.44% <0.00%> (-1.67%)
:arrow_down:

...obblin/compliance/ComplianceConfigurationKeys.java

...estion/google/webmaster/GoogleWebmasterClient.java

...bblin/metrics/kafka/GobblinScopePusherFactory.java

...java/org/apache/gobblin/type/ContentTypeUtils.java

...apache/gobblin/couchbase/common/TupleDocument.java

...he/gobblin/compliance/purger/HivePurgerWriter.java

...pache/gobblin/compliance/utils/PartitionUtils.java

... and 1442 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


exceeded memory limit on slurm cluster

Hi all,
I'm trying the RNAseq pipeline on a slurm cluster, but the jobs get killed pretty quick during star alignment...
2018-05-04 17:03:44.377 [IPEngineApp] Using existing profile dir: u'/scratch/mdeboth/p5674/p5674/work/log/ipython'
2018-05-04 17:03:44.391 [IPEngineApp] Loading url_file u'/scratch/mdeboth/p5674/p5674/work/log/ipython/security/ipcontroller-5d6deb0e-d9ff-4395-94f6-ee98790c8464-engine.json'
2018-05-04 17:03:44.428 [IPEngineApp] Registering with controller at tcp://<IP_ADDRESS>:46597
2018-05-04 17:03:44.481 [IPEngineApp] Starting to monitor the heartbeat signal from the hub every 5010 ms.
2018-05-04 17:03:44.483 [IPEngineApp] Using existing profile dir: u'/scratch/mdeboth/p5674/p5674/work/log/ipython'
2018-05-04 17:03:44.487 [IPEngineApp] Completed registration with id 1
slurmstepd-dback-c11-n01: error: Job 848444 exceeded memory limit (33715636 > 32757760), being killed
slurmstepd-dback-c11-n01: error: Exceeded job memory limit
slurmstepd-dback-c11-n01: error: *** JOB 848444 ON dback-c11-n01 CANCELLED AT 2018-05-04T17:06:42 ***

I thought the fix might be to tweak bcbio_system.yaml to run star with fewer cores/more memory, but the jobs still seem to get killed at the same memory limit (32757760). I'm wondering if I'm misunderstanding the job memory limit or if there's another setting I can tweak. Thanks!

Matt;
Thanks for the report and sorry for the issues. It looks like you're getting allocated 32Gb of memory and STAR is using more than that, triggering the memory issues. Seeing exactly how you're configuring memory and cores for bcbio and knowing more about your cluster machines (how many cores/memory) could help us provide more specific feedback but some general advice:

Do you need to use STAR? If not, you could use a no alignment kallisto or salmon pipeline, or a different aligner like hisat2 to avoid the memory overhead.
Can you tweak cores/memory to get allocated additional memory resources on your machines? If they max at 32Gb this isn't an option, but should be if you have larger machines.

Hope this helps some and gets your analysis running.

Brad - thanks so much for helping debug my user error. I could not figure out why I was unable to allocate more memory... today I learned there's a single, random node in our cluster with only 32GB of memory that was limiting me.


Unexpected changes

Hi Wiliam,
I noticed you recently made two changes that broke compatibility with my integration.
The first one: seconds().
This function is not defined among all those in svg/.h (it's defined in app/).
Not bad, I can always put
#define seconds() 0
since I'm not interested in timing..
The second change is about the SVGDocument constructor.
It was before
SVGDocument(FontHandler *fh)
now it is
SVGDocument(FontHandler *fh, const double w, const double h, const double ppi = 96)
Honestly, I don't understand why it's required to specify the size of the canvas when loading/analyzing the SVG file.
From my point of view, the sizing of the canvas concerns the rendering phase, i.e. when I initialize an SVGDrawingContext by passing it
an appropriately sized BLImage.
What's more, only after loading an SVG file, I can know the image's dimensions (or rather the height/width ratios) to size the canvas (or set up a scale transformation).
Maybe I didn't understand correctly, but I think that canvaHeight,width should not be part of SVFDocument.

seconds() made a brief appearance for debugging.
I've gone back and forth on the SVGDocument including or not including the canvas size.  You're right in that the document does not need this information until it is time to render.
If you look at the SVGDocument class, you'll see that it inherits from "IAmGroot".  This facilitates being able to render, because it contains environment information, like the Window/canvas width and height, and dpi.
This information is only needed when you actually render, but it's needed for two things.

Size of the canvas.  We need this so we can resolve cases where "%" is used for a size, instead of absolute units.  We also need the 'dpi' for the same reason.  When units, such as 'in', 'mm', 'cm' are used, we need to know the dpi so we can resolve to actual number of pixels.
Looking up objects.  There are many places that might be holding a reference to an object, such as the 'use' element, or gradients referring to a template gradient, or colors, referring to a gradient, etc.  at 'bind' time, we need to know where we can lookup all those values.  They are tied to the "IAmGroot" interface.

At the moment, 'bindToGroot()' is called within the 'addNode()' function of the document.  Therefore, the SVGDocument already needs to know this information.
Well, it doesn't have to be like this at all.  As long as when the document is being constructed, all those nodes are held in some form where they can be looked up later, this binding can happen at any time, such as when you're drawing into a context.
In that case, it make more sense to change the SVGDocument::draw() function to be more like
void draw(IRenderSVG * ctx, IAmGroot *groot) override

That way, you don't need to bind early, and you won't need to pass the width and height or dpi earlier.
The same can go for document construction.  There's no reason SVGDocument needs to inherit from IAMGroot.  As long as a pointer to such an object is included in the "loadFromXmlIterator" call, we can completely remove this code to a separate object, and the SVGDocument itself becomes even simpler.
Those are my thoughts on it.


Using certifi for SSL validation in st2client

This PR adds certifi to st2client dependencies and changes the SSL validation behavior to True.
To merge this, we need to make sure that our CA gets added to the certifi bundle; I’ll do that.

To merge this, we need to make sure that our CA gets added to the certifi bundle; I’ll do that.

I assume you mean locally aka in our code, right?

We also need to make sure that the code where we add our CA to certifi bundle is added early on so it also works in other places where requests is used (where we talk to mistral and back, etc.), not just in st2client.

Yes. What I want to do is append our root CA into the certifi bundle as soon as we generate it. Since it's global, we'll be able to use it anywhere, just need to make sure we don't set verify=False in the places you want it to work.

I kinda want to resurrect this PR in the context of new packages. Any chance we could install certifi as a dependency during the package install and then append our own CA to it?

Closing.Reopen if you need it.


Lock state doesn't update

Hello,
I have three danalock v3 zwave edition included in my zwave network operated by fibaro. In order to use them with homekit, I use the homebridge-fibaro-hc3 plugin. When I use homekit to open or close the lock, it works perfectly but the lock always seems open in the homekit app. It seems like the Lock State doesnt change.
The following message also appear in the log:
[8/7/2020, 2:46:46 PM] [FibaroHC3] Setting value to device:  104  parameter: Lock Target State
[8/7/2020, 2:46:46 PM] [FibaroHC3] Command:  secure, value: 0, to: 104
[8/7/2020, 2:46:51 PM] [FibaroHC3] There was a problem setting value to Lock:  104

I have exactly the same problem with my danalock v3 zwave edition.

Unfortunately this is very hard to analyze without a real device.

Hi, I am experiencing a similar issue with Yale Lock with Zwave - It's like the lock is always unlocked in the Home App, but when i try to lock it, it sends the "Lock Command" to fibaro, but then the status remains as "unlocked" or "No Response"
I do have Charles Proxy, if there is something you would like me to test and provide debug info, please let me know.

Hi, I am experiencing a similar issue with Yale Lock with Zwave - It's like the lock is always unlocked in the Home App, but when i try to lock it, it sends the "Lock Command" to fibaro, but then the status remains as "unlocked" or "No Response"
I do have Charles Proxy, if there is something you would like me to test and provide debug info, please let me know.

+1

+1

getLockCurrentState function should be fixed like below
https://github.com/khw1006/homebridge-fibaro-hc3/commit/d53125caf14c1b2dfa6ec9c92f699945c8e9c245

getLockCurrentState function should be fixed like below
https://github.com/khw1006/homebridge-fibaro-hc3/commit/d53125caf14c1b2dfa6ec9c92f699945c8e9c245

getLockCurrentState function should be fixed as follows
khw1006@d53125c

Your fix works. I've verified it on my local installation with Danalock.  I think, it'd be logical to send a pull request with you fix as a next step.

@khw1006 please pack a PR.
@vkamenski thanks for testing.

@khw1006 @vkamenski just published version 1.0.9 containing the fix.

Hi,
Still getting the same error:
[28/03/2021, 13:52:13] [FibaroHC3] Setting value to device:  212  parameter: Lock Target State
[28/03/2021, 13:52:13] [FibaroHC3] Command:  secure, value: 0, to: 212
[28/03/2021, 13:52:13] [FibaroHC3] There was a problem setting value to Lock:  212

This is now working for Yale Lock! Thanks

I have an issue with danalock v3 zwave

@vkamenski try install the beta version homebridge-fibaro-hc3@beta

@vkamenski try install the beta version homebridge-fibaro-hc3@beta

well, I'll better wait for the next release :)

I have an issue with danalock v3 zwave

What exactly is your issue?


Make recyclerview support dependency optional

Is it possible to make recyclerview dependency optional?
I have an application which doesn't use recyclerview, but suffers from 65k problem.

There are couple of ways to do it:

Create a separate module which depends on the base module and the optional dependency
Create a module per optional dependency which the base module depends on.
Mark the dependency as non-transitive and activate the functionality at runtime if present
Use reflection and activate the functionality at runtime if present
Use a Service Provider Interface and call the correct implementation at runtime

Runtime check implementation could be reviewed here: https://github.com/umano/AndroidSlidingUpPanel/pull/572

Yes, I have the same problem with 65k on my project, and do not use recyclerview, so would be really cool if you could remove it. Many thanks in advance!

+1


upgradetest: remove deprecated operator S3 tests

lgtm. unit-ci failed seems to be unreleated.

Fixing it in https://github.com/coreos/etcd-operator/pull/1427
It's underlying tool upgrade.


image is not getting share in android

here is my issue I wrote a question on here - https://stackoverflow.com/questions/49516150/base64-image-not-sharing-in-react-native-android .
in iOS its working perfect.

i have the same problem it get confused with react-native-image-crop-picker provider
+1

I am facing the same problem. On sharing image unsupported content exception is coming. Although Base 64 Obj is getting created

have the same problem...
+1

Solved!
Added user permission at AndroidManifest.xml

and make sure you've enabled Storage permission for your app

Solved!
Added user permission at AndroidManifest.xml
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
and make sure you've enabled Storage permission for your app


Training the model on a custom dataset, how to?

Hello, thank you very much for the code that you provides to easily use deepxml. I am planning to train the deepxml/astec model on a custom dataset. I wonder how should I proceed to do this?
My main concern is how to prepare the BoW features required. What type of approach is used? Thank you!

Thanks for trying out deepxml. You might want to look at this example which demonstrates the pipeline to create unigram based BoW features.
PS: You might also want to look into sub-word based features (such as WordPiece) as they provide additional gains over unigram features on some applications.


The show-source deprecation warning should have a clearer call to action

"Please update your configuration" should be more specific.
Raised in https://github.com/astral-sh/ruff/pull/9874

Hi @zanieb - love Ruff, would love to contribute.
What's a good replacement?
Current message: show-source is deprecated and is now part of output-format in the form of full or concise options. Please update your configuration.
Modified message: show-source is deprecated and is now part of output-format in the form of full or concise options. Please update your configuration by replacing show-source with either output-format = full or output-format = concise in your configuration file. full  would show you the source code snippets and concise would not. Other possible values can be viewed at [https://docs.astral.sh/ruff/settings/#output-format](show-source is deprecated and is now part of output-format in the form of full or concise options. Please update your configuration by replacing show-source with either output-format = full or output-format = concise in your configuration file. full  would show you the source code snippets and concise would not. Other possible values can be viewed at https://docs.astral.sh/ruff/settings/#output-format").

Hey @AbhinavMir! Love to hear that :)
I don't think we need to be quite so verbose. I haven't given the exact message a lot of thought but here are some ideas. This is a bit more work, but we should actually be able to tell which value they're using so if they use show-source=true we can say

The show-source option has been deprecated. Use output-format=full instead.

and for show-source=false we can say

The show-source option has been deprecated. Use output-format=text instead.

We may also be able to tell if this was provided via the CLI or a configuration file. If so, we can make even better suggestions e.g.

The show-source option has been deprecated. Update your configuration file to use output-format = text instead.

and

The --show-source option has been deprecated. Use --output-format=full instead.

Gotcha, I can probably prod into the code a bit more tomorrow, but it'd be great if you could point out where the options are being read from. The idea, I assume is, read the flags, show the correct output - but just wondering how this is architectured in the code base.

Should this issue be closed in light of #9814, which removes show-source as an option (along with its deprecation warning)?

Thanks!


Fix code smells

:white_check_mark: Build Sankhya-SDK-dotnet 2.0.511 completed (commit https://github.com/guibranco/Sankhya-SDK-dotnet/commit/ce6291620f by @guibranco)


Remove postgresql storageClass value

Description
The existing postgresql.global.storageClass affects chart installation on the basic Kubernetes cluster. For a basic installation, data persistence could be omitted.
Epic/Story
#223

Yep, this was a mistake to merge from a contribution, leaving it blank will pick up the clusters default storageClass


[RFE] display whitespace changes

First, thanks for making this!
Playing around with difftastic, I noticed that in textual mode the last line of a file being appended to is being marked as different:
$ difft --version
Difftastic 0.24.0
$ difft <(echo -ne 'one\ntwo\nthree\n') <(echo -ne 'one\ntwo\nthree\nfour\n')
/dev/fd/62 --- 1/1 --- Text
1 one                                   1 one
2 two                                   2 two
3 three                                 3 three
                                        4 four

(here, three is red/green)
Playing further with it, adding spaces at end of lines is just not displayed aside of coloring the line, leaving one to wonder why the line was marked modified. Missing last end of line also does not show anything -- it might make sense for syntactic changes when it understands a file but I believe text files should display these, stuff like e.g. markdown behaves differently when there are trailing spaces.
(in particular git default diff command shows these in red and it helps when reviewing code being added with e.g. git add -p. That command doesn't use external diff tool so I'd still see it then, but not when inspecting changes before or when adding in larger batches)
For programs it understand, e.g. trying with C files a line with added spaces isn't even marked as modified -- it's all blank. "No synatic change" if there's nothing else, and not highlighted at all if there's other changes.
It's correct, but I'd like an option to display these if possible -- think git diff --ignore-all-space opposite.
I don't think I'll be ready to replace the default diff until I can display whitespaces reliably, but I'll definitely keep it around as difftool. cheers!

Hi! Thanks for this project, it looks great!
I share @martinetd opinion: I would like to difftastic for my daily git diffs and the main feature that is missing for me is the possibility to force the highlighting of whitespace changes.


Invalid solutions are always not fully initialized

It's impossible to perform the regular operations on them.
┆Issue is synchronized with this Clickup  by Unito

I thought this was already reported, but I couldn't find one about invalid issue. I think this also happens to valid solutions towards the end of a large list.
Similar issue: #953

I think this also happens to valid solutions towards the end of a large list.

Sometimes the comments don't load for normal solutions too, but a page refresh usually fixes it. However, with invalid solutions it never works: maybe it has to do something with the fact that they are hidden by default, and so the details are probably not loaded for them? And when you click to view them, the loading doesn't restart?

I think this also happens to valid solutions towards the end of a large list.

Sometimes the comments don't load for normal solutions too, but a page refresh usually fixes it. However, with invalid solutions it never works: maybe it has to do something with the fact that they are hidden by default, and so the details are probably not loaded for them? And when you click to view them, the loading doesn't restart?

Closing because invalidated solutions are shown differently now


Missing whitespace

Some words are missing a whitespace.

It looks like the styling for the anchor tags. The anchor tags in the hero section and background section have the spaces around them missing.

Thanks @stevepolitodesign ❤
Fixed in v2.

@matthewl it was actually caused by a html compression plugin I was running via netlify. Turned it off and everything was fine!


Create ichimoku

Basic ichimoku cloud trading strategy. It buys when the price is above the cloud and sells when the price is inside or below the cloud.

 Fixed it


fastprogress bar in README.md doesn't render

hi,
i have a fastprogress bar in my index, it ends up in README.md just rendering the html like this:
 100.00% [10/10 00:02<00:00 Images downloaded]

would it be difficult to render the text/console version for the markdown file?

Yeah fastprogress/nbdev requires a proper markdown environment, which github readme doesn't provide. Happy to take a PR to fix this, if there's interest, but not likely to do it myself.


ScanCode.io: Craft d2d pipeline steps for Go

The design is to extend the "map_deploy_to_develop" with a "Go" option  given the framework in:

#1111

The process will be to:

[x] Collect Go symbols with the new go-inspector. Completed in https://github.com/nexB/go-inspector/issues/2
[x] Integrate the Go symbols collection in ScanCode.io
[x] Create steps in the D2D pipeline to use the Go data for paths-based d2d
[x] Create reusable pipes to create Go packages inferred from the Go binary data

This is now done and we have a set of proper steps grouped and tagged for Go "binary" analysis that can be selectively used in the context of:

https://github.com/nexB/scancode.io/issues/1111

The actual Go-specific pipeline steps look like this:

To test the feature:

Install ScanCode.io
Create a new project
Add these two Download URLs exactly as below using these webpacked examples:

source:  https://github.com/nexB/scancode.io/raw/main/scanpipe/tests/data/d2d-elf/from-data.zip#from
binary: https://github.com/nexB/scancode.io/raw/main/scanpipe/tests/data/d2d-elf/to-data.zip#to

Select and execute the "map_deploy_to_develop" pipeline, clicking on the Elf option

Here is how the project creation looks like:

When pipeline run is finished, refresh

and click on the "relations" , and you can see the mapping between source and binaries:

At the resource page, there are also file-level mappings details:


Add Grand Forks county, ND

Fixes #2181.
This data source has a whole lot more columns but they aren't filled in :(.

I've been trying to sort this one out in #2195,  the regexes are a pain.

Alritey, I'll close this one out then.

Well, how did you make out? If your PR covers it, then let's go with that.

Not so well. The sample shows that I screwed up the street regex.


[mgmt] imagebuilder release

https://github.com/Azure/sdk-release-request/issues/5252

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/arm-imagebuilder


Support for particle system scaling/sizing in world space

Allows particle system billboards to be sized in world space via sizeInMeters property that was added and cascaded to billboards during update/creation process.

Thanks for the pull request @richard3d!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Please wait to merge

Thanks for the awesome work @richard3d! Your contribution is about to launch to millions of users with the next release. :rocket:
Do you mind if we tweet about it? CC @OmarShehata @Slchow.

Adding test coverage... will reopen pull request shortly

Sorry about the erroneous Concierge messages @richard3d. The GitHub API doesn't differentiate between "closed" and "merged" without calling an additional endpoint to check. It's been on my list to fix.
Anyway, thanks so much for the contribution!! We absolutely appreciate it. Hopefully it's the first of many :)


feat: enable to mount local spec for docker container

Description
This is continued from https://github.com/asyncapi/studio/pull/404 .
@magicmatatjahu

remove provided asyncapi.yaml in this PR

If asyncapi.yaml is removed, it doesn't work on local since dev-server doesn't return 404 code in HTTP header.
dev-server returns html document even if there's no static file.
Can you just ignore public/docs/asyncapi/asyncapi.yaml and public/docs/asyncapi/asyncapi.json for deployment?
Related issue(s)

Resolves https://github.com/asyncapi/studio/issues/403

@magicmatatjahu do you mind having a look?

@rikuson there are errors in your code. Would you mind having a look? Apologies for the delay in the review 🙏

@rikuson do you need some help with this?

OK, I'll take a look.

@KhudaDad414 @fmvilas I fixed!

Sorry, it seems got broken after I merge master branch.

@KhudaDad414 @fmvilas Done.

@rikuson @KhudaDad414  Sonarcloud is complaining about COPY . .  I'm wondering why this was not triggered before.
I see this as a common practice in multi-stage builds, I suggest to add it as an exception maybe, or explicitly copy the files.

Hi @rikuson can you take a look at this PR ?
Thanks

@rikuson this PR needs some love :)

Sorry, I'm not motivated anymore.
I'm not gonna continue and it can be closed.