Depreacte --output-format, only allow --output option

Current situation

The help message says "-o --output=file.html|json|csv - Output either an HTML, JSON or a CSV file."
While using -o (and the deprecated --output-format), it will trigger read_option_args: case 'o'

This one checks valid_output_type first, then stores it to output_formats.

When using --output, it will trigger parse_long_opt: "output"

This one stores it to output_formats directly.

The bug I encountered
While using --output out.tsv, it runs through the parsing process and has no output file.
When changed to -o out.tsv for short, it finally gives me the "invalid filename extension" error.
Refer to commit history

In 2016 Jun 2e7c4b8, Added an --output=file.[html|csv|json] as a shortcut to --output-format
In 2017 Apr 91da175, Updated README.md with Docker details

Changed output-format to output in README.

In 2017 Jun 6309ed6, Fix error in example config file

The latest --output-format in this repo (except src/options.c) is removed.

In 2017 Oct 27d8782, Add valid_output_type() to validate the filename given via -o

The file extension check is only applied for -o (--output-format), and the PR author forgot about --output.

According to the commit history, we can see that --output-format has been replaced for 6+ years. I think it's safe to remove it without any warning.
So after this PR is merged, --output-format will only output a fatal error, saying it's deprecated, without backward compatibility.

I still not confident about how to write the text with short word.
Here is some version (with inspiration of ChatGPT), which one would you preferred?
(A)
-o --output=<format|filename>   - Output to stdout or the specificed file.
                                  Currently support HTML, JSON and CSV format.
                                                                               *
(B)                                                                            *
-o --output=<format|filename>   - Specify the output format or output filename.
                                  The filename must have .html, .json, or .csv extension.
                                                                               *
(C)                                                                            *
-o --output=<html|json|csv>     - Specify the output format.
-o --output=<FILENAME>          - Save report to a file. The FILENAME must
                                  have .html, .json, or .csv extension.
                                                                               *
(D)                                                                            *
-o --output=[FILE.]<FORMAT>     - Output to stdout or the specificed file.
                                  Supported FORMAT: html, json, csv.
                                                                               *
(E)                                                                            *
-o --output=<html|json|csv|FILE> - Set output format or write to a file.
                                   The FILE must have .html, .json, or .csv extension.
                                                                               *
(F)                                                                            *
-o --output=[file.]<html|json|csv> - Output to stdout or the specificed file.

                                                                               *
(G)                                                                            *
-o --output=<format|filename> - Output to stdout or the specificed file.
                                e.g., --output=report.html, -o out.json, --output=csv
                                                                               *
  (Current longest text)                                                       *
--unknowns-as-crawlers          - Classify unknown OS and browsers as crawlers.
--external-assets               - Output HTML assets to external JS/CSS files.

Thanks for posting these options. Let's roll with G; I think that's pretty clear, in my opinion.

Okay! Just pushed a new version. ☺

And I do a little adjustment here, think it would be more readable.
(From this)
-o --output=<format|filename> - Output to stdout or the specified file.
                                e.g., --output=report.html, -o out.json, --output=csv

(Changed to this)
-o --output=<format|filename>   - Output to stdout or the specified file.
                                  e.g.: -o csv, -o out.json, --output=report.html

Thanks, Sean! The changes have been merged.


Fix dns vars description according to AWS Docs

This is a request to fix description of 2 variables. According to the official documentation, dns variables are about public hostnames and the public DNS server(s) of AWS: http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html

Sorry for the delay. I don't know how I managed to skipped this one.
Good idea to write things correctly, but let's write it more generic:

Should be true to enable DNS support in the VPC
Should be true to enable DNS hostnames in the VPC

via:

https://www.terraform.io/docs/providers/aws/r/vpc.html#enable_dns_support
https://www.terraform.io/docs/providers/aws/r/vpc.html#enable_dns_hostnames


Update UBI Ruby image test OpenSSL version

What does this PR do?
This commit updates the OpenSSL version expected in the UBI Ruby image from
"OpenSSL 1.1.1c FIPS  28 May 2019" to "OpenSSL 1.1.1g FIPS  21 Apr 2020"
What ticket does this PR close?
Resolves #39
Checklists
Change log

[ ] The CHANGELOG has been updated, or
[x] This PR does not include user-facing changes and doesn't require a CHANGELOG update

Test coverage

[ ] This PR includes new unit and integration tests to go with the code changes, or
[x] The changes in this PR do not require tests

Documentation

[ ] This PR does not require updating any documentation, or
[x] Docs (e.g. READMEs) were updated in this PR, and/or there is a follow-on issue to update docs

@izgeri could you please update the relevant description and readme with the changed openssl version?
Thanks!


Module not allowed

I am call the "/rest/v11/BulkImport/records/av5_circuits" endpoint with this body
{"records":[{"name":"test"}]}
and a valid oauth-token but I get this error back.
{     "error": "invalid_parameter",     "error_message": "Module av5_circuits not allowed" }
I have created the module in sugar and verified the name is correct. I am wondering if this issue is in SugarCRM or in this API?

Hey there Justin.
I believe that error is coming from the line at the below link.
https://github.com/sugarcrmlabs/BulkImport/blob/11b46d0e836d34c68ef31796b061924a4aa588af/src/custom/include/bulkimport/BulkImport.php#L415
Did you set up the config_override options for that module?

In was able to find that the configs where being set in config.php instead of config_override in a different format. I added the configs to the config.php file and it works. Thanks for your help.


New format checking IP ( 4 or 6 )

Currently only formats specified in the JSON schema spec itself are implemented. Whilst I could understand the argument of adding an ip format, that should be done at a JSON schema level. I am not particularly keen on maintaining a custom set of formats. Implementations allow users to add their own custom formats, so if you need an ip format you should use that in the meantime.

Ok, thanks!


Client testing fix

39/39 included unit tests now pass by mocking AuthService. All user profile related tests are commented out because they are out of scope. Before closing this issue, documentation about why the user profile tests were commented are needed, as well as a confirmation about the validity of the existing AuthService documentation.
#4

Cool. Now we just have to keep documentation in mind!!


Update Composer dependencies (2024-02-13-00-10)

Visual regression test passed!
View the visual regression test report


Cloudera Manager API

HI, i want to add to the definition yml
External authentication (ldaps)
Please advise how to use the Cloudera Manager API to see how its writable in exists cluster and how to add it to the yml definition for new installation

@hodafplay, it is documented here : https://github.com/cloudera-labs/cloudera.cluster/blob/main/docs/freeipa.md#ldap-configs


Nav mesh outside fire exit, bodies uncollectable

The maps Offence and Assurance have fire exits with cliffs that the Pikmin get stuck on. Is there a way for them to drop to the nav mesh below, or for them to detect the obstructed path to the ship and avoid that path? If not, would a blacklist for the fire exits on these moons work? Changing the configuration file mid-game to have them only path to main works as a temporary solution, though it's... meh.
There was also a bug with enemy corpses not being picked up by Pikmin when defeated near main or when there was no onion for the Pikmin to transport to. Even after collecting an onion, they would not target the body, and it would be rendered unobtainable. Same goes for when 'Onion produces sprouts' is disabled and the Pikmin move the body to the ship, it would not be taken back to the onion when the config is reenabled. I'm not sure if the bug was patched in the more recent updates.

The first part with fire exits being broken have already been mentioned in issue 13. I'm still thinking of a work around for them, but I'll keep your Blacklist idea in mind.
The second part is an issue that occurs because I forgot to make it so pikmin won't ignore bodies when near main or when inside the ship, I'll fix that next update.


Bump up chart version to trigger chart release

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

@lingxiankong I think we need this to trigger chart release.

@lingxiankong although you could first try deleting the release and tags re-running the action since it currently thinks there is nothing to release: https://github.com/kubernetes/cloud-provider-openstack/runs/1069901731?check_suite_focus=true#step:5:9

/ok-to-test

should we wait for 1.19 out then we can bump together?

No need, these charts uses the latest image anyway so makes no difference.

ok, I am good with it
/lgtm

should we wait for 1.19 out then we can bump together?
@jichenjc I think thats good idea , we need to update the images version from latest to 1.19 once the branch is cut , and do the  chart release for 1.19 , so we can bump version there , could you submit PR on 1.19 branch , should be cut today @lingxiankong

/lgtm

I’ve never managed to get the chart instal action to pass. It fails because the names that the helm chart renders is too long. Perhaps we should disable it until someone has time to fix it.

let's merge this first
/approve


Skip GPG provisioning tests temporarily

As first part of CORE-3257, skipping GPG provisioning tests on all OSs temporarily until the cause of the sporadic gpg "Bad signing error" can be determined/fixed.
r? @maxtaco

👍  but we should prioritize figuring out what's going on here

I'm working on it now.  Can reproduce, but haven't figured it out yet.

retest please


Item route improvements

Description
Improvements in item route functions / pipes. (in preparation for future changes.)
Test cases
All non-trivial changes which have been done have now a e2e test to check the new behavior.
The only exception is the forum/thread which are more difficult to test for the moment.

[auto-generated message] E2E test report on: https://algorea-static.s3.eu-central-1.amazonaws.com/branch/itemRouteImprovements/playwright-report/index.html

[auto-generated message] E2E test report on: https://algorea-static.s3.eu-central-1.amazonaws.com/branch/itemRouteImprovements/playwright-report/index.html


After closing VS Code's window, it won't reopen

top shows the processes are still running. Perhaps we're accidentally using XDestroyWindow (or XCB equiv) when it is expecting WM_DELETE?

After killall code, it opens again.

Whoops, wrong project.


Input checks for pvsamv1 result in inputs required for disabled subarrays

Simulation error when subarray2_track_mode is not assigned even when subarray2_enable = 0:
Error: check fail: reason unassigned referenced, with 'subarray2_track_mode' for: subarray2_monthly_tilt time -1.000000
EXEC_FAIL: pvsamv1

To replicate, run this script in SDKTool with SSC Version 280:
pv-subarray-input-tests.zip
See https://github.com/NREL/pysam/issues/155

@janinefreeman I assume this will be resolved in the next release. Do you have a sense of when that will be? Thanks!

Hi @caseyzak24 ! We are hoping for a release in mid-November.

The issue here is that subarray2_track_mode is required for some input variable checks even when subarray2_enable is set to zero.
For example, in order to check that subarray2_tilt is not set for the 2-axis or seasonal tilt options, the line in the var table for subarray2_track_mode needs to check subarray2_track_mode:
{SSC_INPUT, SSC_NUMBER, "subarray2_tilt", "Sub-array 2 Tilt", "degrees", "0=horizontal,90=vertical", "System Design", "subarray2_enable=1&subarray2_track_mode~2&subarray2_track_mode~4", "MIN=0,MAX=90", "" },

In other words, for this variable check to pass the following has to be true:
subarray2_enable == 1 && subarray2_track_mode != 2 && subarray2_track_mode != 4

So, although subarray2_track_mode is not required for the simulation, it is required for the variable check logic. Given the way; the variable table is set up, I'm not sure there is a way to avoid this, but I will investigate further.

Note, that in compute_module::check_required the Boolean expressions are evaluated from left to right. Therefore, if the first constraint fails, the remaining constraints are not checked.

The example file has a failure for “subarray2_monthly_tilt” because only subarray_track_mode is checked and not subarray2_enable=1 first

Pull request #1062 addresses the REQUIRED_IF issue for all of the "subarrayn_monthly_tilt" inputs

Thanks, @sjanzou.


Tab selection fix

These changes make selecting hard tabs work like it does in other editors. Currently in Atom, if you click in the middle of a hard tab the cursor always goes to the left edge. These changes make it go to the closest edge.
Tests have been updated, and new ones have been added for the new functionality.
I believe I've hit everything in the contribution guidelines. Let me know if I need to make any changes!

:+1: This will be nice to have implemented :).

@as-cii Can we lean on you to review this PR? Looks valuable.

Can we lean on you to review this PR? Looks valuable.

@nathansobo: sure thing! I'll have a look later on today :+1:

@adzenith: first of all, thank you for taking the time to contribute. Nice job here :+1:
The repository has seen many changes since you opened the pull-request (many of them impact how clipping works), thus it would be awesome if you could merge master into this branch. I have already checked and, apparently, there aren't many conflicts, so it should be a straightforward task.
After merging you'll encounter some errors while running the tests: once again, I feel like fixing them should be quite easy, but I'll be happy to help you along the way if there's any problem.
In the meantime, I'll write some thoughts about your changes so that we can :ship: this! :fire:

The additional unit tests are working; I'm going to try a merge and see what I can see.

I've merged it into master and all tests are passing. Let me know if there's anything else you'd like me to change!

I've taken out the tabLength change entirely. I've been making changes and then merging with master; in general, would you prefer this or a rebase?
I'll write some more tests around screenColumnForBufferColumn.
Thanks!

I've taken out the tabLength change entirely

Good job there! :+1:

I've been making changes and then merging with master; in general, would you prefer this or a rebase?

Merging is fine :wink:
After completing those specs I mentioned earlier on, I think we can merge this right away :metal:

Sounds great. I'll add some specs for screenColumnForBufferColumn and push them up.

I've been making changes and then merging with master; in general, would you prefer this or a rebase?

Either is fine, but generally a rebase is better in my opinion as it keeps the commit history cleaner. I don't even use the Merge pull request button on my personal projects because I really care about keeping the history as clean and "consumable" as possible :grinning:
Regardless, thanks for working on this!

a rebase is better in my opinion as it keeps the commit history cleaner.

I agree. I asked because I've also seen projects where they want a merge commit every time. I'll rebase it :)

Pushed the rebased code. I'm going to look into adding specs for soft tabs and screenPositionForBufferPosition.

Pushed the rebased code. I'm going to look into adding specs for soft tabs and screenPositionForBufferPosition.

@adzenith: I left some comments, but overall I think we're getting closer to merge this :metal:
@atom/non-github-maintainers: would you be interested in testing this out to catch eventual regressions we're not taking into account? Your help would be much appreciated! :pray:

Sweet. At this point I think I've updated the code based on all the comments and feedback you've provided: tests for the change to screenColumnForBufferColumn, new tests for screenPositionForBufferPosition's handling of soft tabs, and changing the global tabLength in display-buffer-spec back to 2.
If there's anything I've missed, let me know. Otherwise ... maybe it's ready for merge :dart:?!

If there's anything I've missed, let me know. Otherwise ... maybe it's ready for merge ?!

Two minor comments, but we should be good to go. Before merging this, however, I'd like to leave it open for a while and catch any regression we may have missed.
Awesome job, @adzenith! :rainbow:

Excellent! Thanks so much for the great code review @as-cii! I enjoyed the emoji considerably. :tophat: :wave:

Excellent! Thanks so much for the great code review @as-cii! I enjoyed the emoji considerably.

It was great to collaborate with you on this.
@nathansobo: could you have a final look so that we can :shipit:? Thank you :bow:

I'd like to see the option name move more toward what we're working on in text-document if possible, but other than that, I think this is looking really good. Thanks to both of you!

I'd like to see the option name move more toward what we're working on in text-document if possible, but other than that, I think this is looking really good. Thanks to both of you!

@adzenith did a great job here :checkered_flag: Let's wait for him to update this PR with the renaming you proposed and then we can :shipit:

I don't know what you mean... it's been called clip this whole time :sparkles: :stuck_out_tongue:
Re-rebased onto master; all tests are still passing. Let me know if I can make any more changes! :doughnut:

Thanks a lot, @adzenith! :fireworks: :fireworks: :fireworks:

Woo merged! Thanks so much! :sunny::seedling:


Changed --genkey --secret to --genkey secret

DEPRECATED OPTION: The option --secret is deprecated.
WARNING: Using --genkey --secret filename is DEPRECATED.  Use --genkey secret filename instead.

Duplicate.

okay, why not to fix it?

There is nothing to fix. Search the duplicate issues for previous discussion on the matter. Or better yet, test your pull request in the supported distributions, and you will see that this change breaks compatibility with some of them. "Works for me" is not good enough when submitting a pull request.


Add variable to use Taskbar replace default Launchers in AOSP for Android.mk

When AOSP wants to integrate Taskbar as default Launcher, we can use Taskbar to override other Launchers in AOSP to make sure the system will build the Taskbar only. Also we can remove other Launchers from build system, but it needs to modify the build system to support remove packages with variable, such as add new variable REMOVE_PRODUCT_PACKAGES, or remove them from PRODUCT_PACKAGES in build/make/target/product/core.mk. All methods need user to change other code in build system. With the added variable ENABLE_TASKBAR_REPLACE, user only should add ENABLE_TASKBAR_REPLACE := true to this device makefile. The default behaviour is as the normal, doesn't apply overriding, it will not affect the user has integrated Taskbar to AOSP or other Android-inherited system.

Thanks for your contribution.  I noticed a small typo in the Android.mk that I'll fix real quick (EANBLE should be ENABLE), otherwise looks good.

@farmerbb , it's my fault, thanks.


Allow API server port selection

Currently API Server ports are set to 443 and 8080.
In my scenario, port 443 at master is used by an ingress controller.
To allow other ports we would need  extra parameters --api-server-insecure-port and --api-server-secure-port for render and start commands.
This would affect:

temporary apiserver
apiserver daemonset
kubeconfig

@odacremolbap it has been somewhat of a long-standing design decision not to plumb through most options into the render/start steps - because at some point we're just adding every flag available to k8s components into bootkube itself (and this quickly becomes untenable).
Instead, we've split render/start into two distinct steps so that it is easy to modify the generated templates to your needs.
In this case it might not be as easy as simply modifying the rendered templates because the temporary control plane will operate at a different port. However, I am extremely hesitant to add any flags that require coordination between render and start - because that means you could have assets which only work if you happen to provide the correct flags to start, and this could easily cause users trouble.
I think to properly support something like this we might need to change to using static manifests for the temporary control plane (https://github.com/kubernetes-incubator/bootkube/issues/168). Then the process would allow for you to run render normally, but then you could go and modify the flags to both your temporary and self-hosted control plane and run start without any flags.
One thing to call out, however, is that the static manifest temporary control-plane makes other things difficult, so not immediately sure the best options here: https://github.com/kubernetes-incubator/bootkube/issues/168#issuecomment-279815328
Ultimately, until we have a good generic way of solving these problems - I am not very keen on adding flags to solve these problems - as it will make bootkube very difficult to test / maintain.

agreed on #168
Thanks

@aaronlevy What do you think about changing the secure port to something other than 443? I ran into the same problem when trying to set up ingress, and got it working by updating all of the references to 6443.

Ping @aaronlevy
I have the changes locally and can open a PR to change the default if you're 👍 to that.

Hi @lblackstone
I think this is being worked in a different direction. The control plane would no longer be an in-binary string but a rendered yaml, so we would be able to customize after the render stage.
see https://github.com/kubernetes-incubator/bootkube/issues/168

Closing, as this can be customized in the temporary control-plane now


Check path existence / file permissions for cassette file (fixes #28)

Also includes some indentation / trailing whitespace / formatting fixes to spec file.

Hey @robforman, what's the status of this PR? Anything I can do to help get it merged?

Sorry- was traveling. No, it looks great.


Remove version: Jackett.Jackett version 0.20.2304

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.20.2304/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


How to Make Play Button UI?

How to Make Play Button UI?
 var whoosh = new Sound('advertising.mp3', Sound.MAIN_BUNDLE
  render() {
    return (
      <View>
        <Text title="mp3 in bundle" buttonLabel={'Play'} onPress={this.props.play(whoosh)} >Play</Text>
      </View >
    );
  }

What Should I put in onPress or How to Play advertising.mp3` file?

@saeedhei ,
onPress={this.whoosh.play()}

Dear @kot-ezhva I got This red Screen Error:
undefined is not an object (evaluating 'this.whoosh.play')
How Can I Fix That?
My mainScreen:
export default class Sara extends Component {
  constructor(props) {
    super(props);
    //
    // Enable playback in silence mode (iOS only)
    Sound.setCategory('Playback');

    // Load the sound file 'whoosh.mp3' from the app bundle
    // See notes below about preloading sounds within initialization code below.
    var whoosh = new Sound('advertising.mp3', Sound.MAIN_BUNDLE, (error) => {
      if (error) {
        console.log('failed to load the sound', error);
        return;
      }
      // loaded successfully
      console.log('duration in seconds: ' + whoosh.getDuration() + 'number of channels: ' + whoosh.getNumberOfChannels());
    });

    // Play the sound with an onEnd callback
    whoosh.play((success) => {
      if (success) {
        console.log('successfully finished playing');
      } else {
        console.log('playback failed due to audio decoding errors');
      }
    });

    // Reduce the volume by half
    whoosh.setVolume(0.5);

    // Position the sound to the full right in a stereo field
    whoosh.setPan(1);

    // Loop indefinitely until stop() is called
    whoosh.setNumberOfLoops(-1);

    // Get properties of the player instance
    console.log('volume: ' + whoosh.getVolume());
    console.log('pan: ' + whoosh.getPan());
    console.log('loops: ' + whoosh.getNumberOfLoops());

    // Seek to a specific point in seconds
    whoosh.setCurrentTime(2.5);

    // Get the current playback point in seconds
    whoosh.getCurrentTime((seconds) => console.log('at ' + seconds));

    // Pause the sound
    whoosh.pause();

    // Stop the sound and rewind to the beginning
    whoosh.stop(() => {
      // Note: If you want to play a sound after stopping and rewinding it,
      // it is important to call play() in a callback.
      whoosh.play();
    });

    // Release the audio player resource
    whoosh.release();
    //
    this.state = {
      loopingSound: undefined,
      tests: {},
    };
  }
  render() {
    return (
      <View>
        <Button title="mp3 in bundle" buttonLabel={'Play'} onPress={this.whoosh.play()} ></Button>
      </View >
    );
  }
}

AppRegistry.registerComponent('Sara', () => Sara);

@saeedhei this is a basics of javascript. You're trying to create a variable whoosh in constructor(), but it never assigned to this.woosh, so of course it's undefined when you call it from onPress.
Try to assign it like this in constructor: this.woosh = woosh;


map component

Hello, are there any plans to add a map component？For example, a map of a city, a country

Hello @khcshell
This is not planned for the moment.


Delete IDE dispose analyzer rules

The IDE dispose analyzer rules have been deleted from Roslyn:
https://github.com/dotnet/roslyn/commit/eeba499ecf839ec35bca25062d69d2fc5c4885b9
cc: @iSazonov

See also: https://github.com/dotnet/runtime/commit/ca3b27963931172f0535fff644e1fae23f406193

IDE0067: DisposeObjectsBeforeLosingScope can be replaced with CA2000: Dispose objects before losing scope.
IDE0069: DisposableFieldsShouldBeDisposed can be replaced with CA2213: Disposable fields should be disposed.


Additional command line options not included

--dont_check_norm command was not added to relion job

I think they are - just double checking ...


Rename "M5Module-4Relay"

Resolves https://github.com/arduino/library-registry/issues/1643

2022/08/03 15:39:23 Loaded 5052 libraries from DB
Removing MODULE_4RELAY
Success!

Done


RBT-1 creating front and backend

Creating front and backend. Please check it out.

untested accept


FlexLayoutDemos: "Photo Wrapping" sample broken

Build and the FlexLayoutDemos and run them in an iOS simulator and in an Android emulator.  When the app starts, click "Photo wrapping".
On iOS, the screen is empty white:

Click "< Back" at the top, then click "Photo wrapping" again, and the page is now loaded with image - except they are all very tiny and in one big vertical stack.  There is no scrolling behavior.

On Android, the page initially loads while rendering the results - again in one big vertical stack.  But then the app hangs and crashes without any logged exceptions.
adb logcat shows:
2022-08-02 16:48:06.740 29747-29747/?  If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.795 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.796 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.796 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.796 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.796 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.797 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.798 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.799 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.800 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.800 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.800 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.800 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.800 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.800 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.800 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.801 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.801 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.801 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.801 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:20.801 29747-29747/com.companyname.flexlayoutdemos I/CustomViewTarget: Glide treats LayoutParams.WRAP_CONTENT as a request for an image the size of this device's screen dimensions. If you want to load the original image and are ok with the corresponding memory cost and OOMs (depending on the input size), use .override(Target.SIZE_ORIGINAL). Otherwise, use LayoutParams.MATCH_PARENT, set layout_width and layout_height to fixed dimension, or use .override() with fixed dimensions.
2022-08-02 16:48:21.382 29747-29774/com.companyname.flexlayoutdemos D/EGL_emulation: app_time_stats: avg=25.64ms min=1.56ms max=186.78ms count=36
2022-08-02 16:48:22.411 29747-29774/com.companyname.flexlayoutdemos D/EGL_emulation: app_time_stats: avg=508.77ms min=219.68ms max=797.87ms count=2
2022-08-02 16:48:23.069 29747-29747/com.companyname.flexlayoutdemos I/Choreographer: Skipped 66 frames!  The application may be doing too much work on its main thread.
2022-08-02 16:48:24.394 29747-29774/com.companyname.flexlayoutdemos D/EGL_emulation: app_time_stats: avg=1973.05ms min=1973.05ms max=1973.05ms count=1
2022-08-02 16:48:24.408 29747-29757/com.companyname.flexlayoutdemos I/flexlayoutdemo: NativeAlloc concurrent copying GC freed 326(72KB) AllocSpace objects, 2(136KB) LOS objects, 49% free, 4892KB/9784KB, paused 50us,1.188ms total 211.640ms
2022-08-02 16:48:25.946 29747-29747/com.companyname.flexlayoutdemos I/Choreographer: Skipped 89 frames!  The application may be doing too much work on its main thread.
2022-08-02 16:48:26.006 29747-29757/com.companyname.flexlayoutdemos W/flexlayoutdemo: Suspending all threads took: 21.163ms
2022-08-02 16:48:26.073 29747-29757/com.companyname.flexlayoutdemos I/flexlayoutdemo: NativeAlloc concurrent copying GC freed 196(60KB) AllocSpace objects, 1(68KB) LOS objects, 49% free, 4936KB/9873KB, paused 1.506ms,26.352ms total 364.148ms

Workaround:
Where the image is loaded here:
https://github.com/dotnet/maui-samples/blob/768d9d0458dfc253fe436788afe31b9d46a198f4/6.0/UserInterface/Layouts/FlexLayoutDemos/FlexLayoutDemos/Views/PhotoWrappingPage.xaml.cs#L42-L46
Specify a width and height request.
Image image = new Image
{
    Source = ImageSource.FromUri(new Uri(photoUri)),
    WidthRequest = 100,
    HeightRequest = 100
};

Then everything loads and scrolls as expected.

That works in Android as well, and prevents the crash.
Is this a bug in the sample, or a bug in MAUI?

Hi @mattjohnsonpint
Agreed about the photos on iOS and Android, although the latest MAUI release for iOS does produce a slightly different result. Windows does the best job of displaying the photos, without setting any dimensions, but still gives a weird result
Its bugs in MAUI - the identical sample runs in Xamarin.Forms just fine. But I'll update the sample with your suggestion, which is sensible anyway (controlling the image size yourself), so thanks for reporting this.


[Docs] Replace johns-apparel with IANA-reserved domain

WHY are these changes introduced?
Partially addresses https://github.com/Shopify/shopify-dev/issues/46788
WHAT is this pull request doing?
Replace johns-apparel in CLI docs with IANA-reserved domain for technical documentation
How to test your changes?
🎩
Copied files to shopify-dev
Example of change in CLI docs there
Post-release steps
Need to publish documentation pages
Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[ ] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes

To tophat you need to manually copy the doc files into shopify-dev (in the CLI docs folder)

/shipit

👋🏼 This change has been released, so it's time to run the post-release steps!


[add] promises list

Hello there :)
We have a lot of async sagas that must be done before server rendering, therefore we need to store all promises and it seems annoying (too much const promise = store.dispatch()). We can see that better way to make a small middleware collecting such promises, but I’ve realized that we try to reinventing redux-wait-for-action. With this PR  redux-wait-for-action will allow us for gathering promises resolving after [WAIT_FOR_ACTION] without annoying overhead code (like collecting promises from fetch at https://blog.chionlab.moe/2016/12/21/universal-react-app-reuse-effects-on-server-side/#更优雅地组织同构应用).
configureStore.js:
import <...>

export default function configureStore(initialState, helpersConfig) {

  const sagaMiddleware = createSagaMiddleware()
  const reduxWaitForMiddleware = createReduxWaitForMiddleware()

  <...>
  const store = createStore(rootReducer, initialState, enhancer)
  store.prerenderSagasDone = () => {
    const pending = reduxWaitForMiddleware.getPromisesList()
    return Promise.all(pending)
  }
  return store
}

handleServerRendering.js (Express middleware)
  await store.prerenderSagasDone()
  const html = ReactDOM.renderToStaticMarkup(<Html {...data} />)
  res.status(route.status || 200)
  res.send(`<!doctype html>${html}`)

No any other changes. In the action creators all the same (just [WAIT_FOR_ACTION] and [ERROR_ACTION] properties adding to Flux Standard Action).

Good work. We'll add getPromiseList() in the next minor release and docs will be updated soon. Merged.


Error when a parent class recieves arbitrary number of arguments and a parent of the parent is not

It's better to show on modules actually:
module Shiny
  def initialize(*)
    super
    @foo = 1
  end
end

Inject = Dry::AutoInject(one: 1)

class Foo
  include Shiny
  include Inject[:one]
end

Foo.new

__END__
[8] pry(main)> wtf?
Exception: ArgumentError: wrong number of arguments (given 1, expected 0)
--
0: (pry):3:in `initialize'
1: (pry):3:in `initialize'
2: /Users/gordon/dev/dry-auto_inject/lib/dry/auto_inject/injection.rb:123:in `initialize'

@timriley do you think the case is valid? I think about removing all injected arguments prior to call super method as a default behavior, what do you think?
Oh, and one more issue. Currently .new accepts arbitrary number of arguments but silently ignores superfluous.

@flash-gordon Very interesting! I was about to say that this is probably not about, that Shiny#initialize should have some understanding of its circumstances and pass the appropriate args to super (or no args, via super()).
However, I did notice that Shiny#initialize's parameters is different to what I've been checking for so far. It returns [[:rest]], instead of [[:rest, :args]], which is what you get for a method that accepts a named splat argument like *args.
When there's no name for the splat, then it's clear the method has no intention to use them, so I think we should probably handle this case specially. When we know the super #initialize has * args, then we should probably just pass none of the dependencies to it, the same as this case. What do you think?

Yes, I thought about it and it does the job in that case, we can be sure that Shiny won't do super() because it makes no sense as far as I can imagine. But the issue can be also resolved with something like this:
@@ -67,7 +67,7 @@ module Dry
           def self.new(*args)
             names = #{dependency_map.inspect}
             deps = names.values.map.with_index { |identifier, i| args[i] || container[identifier] }
-            super(*deps)
+            super(*deps, *args[deps.size..-1])
           end
         RUBY
       end
@@ -110,12 +110,10 @@ module Dry
       # @api private
       def define_constructor_with_args(klass)
         super_method = Dry::AutoInject.super_method(klass, :initialize)
-        super_params = if super_method.nil? || super_method.parameters.empty?
+        super_params = if super_method.nil?
           ''
-        elsif super_method.parameters.any? { |type, _| type == :rest }
-          '*args'
         else
-          "*args[0..#{super_method.parameters.length - 1}]"
+          "*args[#{dependency_map.size}..-1]"
         end

I suggest it because I see no reason why parent class should know about dependencies of child classes. Could you explain the reason to me because auto-inject is very awesome and I want to use it properly :)

It's worth to mention about one more case:
[1] pry(main)> Inject = Dry::AutoInject(one: 1, two: 2)
=> #<Dry::AutoInject::Injector:0x007f999281eda8 @container={:one=>1, :two=>2}, @options={}>
[2] pry(main)> class Foo
[2] pry(main)*   include Inject[:one]
[2] pry(main)* end
=> Foo
[3] pry(main)> class Bar < Foo
[3] pry(main)*   include Inject[:two]
[3] pry(main)* end
=> Bar
[4] pry(main)> Bar.new
=> #<Bar:0x007f9993321de0 @one=2, @two=2>
[5] pry(main)>

:)

BTW it came to my mind that we can provide different strategies for sequential parameters.


CurseForge mark on Command Macros compitable with 1.18.2

Hello, please put a note on CurseForge that it is compatible with 1.18.2, I need it for the modpack.

I marked it as such

thanks


Open keyboard programmatically

.callOnClick() does nothing, Adding OnClickListener shows that onClick was called programmatically, but keyboard not shown. Keyboard will appear only after manually click.
Please fix it ASAP

Please upgrade to version 1.4.3.


Add user-agent to credential pipelines

Closes #9014 by ensuring credentials' requests include a user-agent, e.g. 'azsdk-python-identity/1.1.1 Python/3.7.2 (Windows-10-10.0.18362-SP0)'.

/azp run python - identity - ci

@scbedd apparently the tests added here are failing, as if they're running against old code. They pass locally (Linux, tox). The built wheel contains the new code. I'm stumped.

@chlowell I'm checking.

Can one of the admins verify this patch?


Web interface not accessible at "hostname.local"

Describe the bug
Not sure if a bug or I misunderstood the documentation. When launching copyparty with -z and trying to access the web interface using "http://myhostname.local", the browser says it is unreachable.
To Reproduce

Run copyparty with the -z flag:

$ hostname
$ home
$ copyparty -v /home/me/mystuff:/stuff:rw -z

Open "http://home.local" in Firefox
Get a "Unable to connect" error

Expected behavior
Get access to the web interface on "http://home.local".
Server details
if the issue is possibly on the server-side, then mention some of the following:

server OS / version:  Arch
python version: 3.12.6
copyparty arguments: -v /home/me/mystuff:/stuff:rw -z
filesystem (lsblk -f on linux): btrfs

Client details
Same. But also tried to access from another machine running Ubuntu 20.04
Additional context
Zeroconf is configured correctly on my machine, as explained on the Arch Wiki.

hey, thanks for trying copyparty :>
the issue is that the server listens on port 3923 by default, while browsers expect either 80 (for http) or 443 (for https). I've probably not communicated this very well for the zeroconf option.
3923 is the default because both Linux and Macos prevent you from using ports below 1024 due to security reasons.
I think you have five options, roughly sorted from best to worst:

option 1: access the server with http://myhostname.local:3923/ to keep using the default port

this is the safest option, just kinda sucks
but if you also enable --qr to generate a QR-code with the link on startup, then the QR-code will include the correct port

option 2: forward port 80 and 443 to port 3923

this is still perfectly safe, just cumbersome since you'll need to do this after every reboot:iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 3923
iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-port 3923

option 3: allow the use of ports 80 and 443, and then use those instead

note that this will weaken your security by a tiny bit, since all python scripts are then technically able to pretend they are a privileged service -- however I wouldn't be too concerned about this on an average workstation, especially if you already have a dns server running (like dnsmasq)
on Linux, first do this:setcap CAP_NET_BIND_SERVICE=+eip $(realpath $(which python))

then add -p 80,443 to the copyparty arguments

option 4: set up a reverse-proxy on port 80/443 and relay to copyparty

this is the option that makes the most sense on proper headless servers, but it sounds like you're running this on a workstation, in which case that would just be overkill

option 5: run copyparty as root (please don't), and also add -p 80,443 to the args

i'll get this added to the documentation somehow, thanks for the headsup :>


Rename UpdateHandle to WorkflowUpdateHandle (💥 - incompatible change)

What was changed

Renamed UpdateHandle to WorkflowUpdateHandle.
This is a breaking change.
⚠ Feature tests are failing; I can update them as a fast follow-up.
Why?

Consistency. (as discussed previously)
Checklist

How was this tested:
Existing tests.
Any docs updates needed?
I checked https://docs.temporal.io/develop/java/message-passing and the UpdateHandle type isn't mentioned anywhere.
I also cannot see it in the samples repo (search)
The release docs will need to mention this change, though.

LGTM, you'll need to create a feature branch and update the code since it did use UpdateHandle

Let me know if you need any help with that!

👀 https://github.com/temporalio/features/pull/532

LGTM!


Revert "Exclude scala-xml from provided classpath"

This reverts commit 2bcc584022f761efa9968a3c126608b559b8fedb.

Why was this reverted?

Reverted because of failing system tests without any useful information in the logs.


[INLONG-540] query cluster info

query cluster info
JIRA link - [INLONG-540] created by stingpeng

Closed due to TubeMQ manager has merged


Trim problem

I am getting this error, but then it seems to work correctly.
Method invocation failed because [System.String[]] doesn't contain a method named 'Trim'.
At Check-PESecurity.ps1:523 char:101

    $DllCharacteristics = $NtHeader.OptionalHeader.DllCharacteristics.toString().Split(',').Trim <<<< ()

CategoryInfo          : InvalidOperation: (Trim:String) [], RuntimeExcep   tion
FullyQualifiedErrorId : MethodNotFound

I fixed the code and it should work now.


feat(Workspaces): remove public role privileges on created database

This PR intends to remove public role privileges on created database. It allows to restrict the created role to have access to  only his workspace databases.
Changes

Add query to revoke all privileges on database to the public role.

How/what to test
By using a Posgres client, open a connection to the database server and try to access to another database.
Screenshots / screencast
If relevant, please add some screenshots or a short video.

@cheikhgwane nice! Could you add a test?

@pvanliefland you can check now

@cheikhgwane LGTM!


Anomaly in login code

Everyone seems to get signed in as the same user, seems non-optimal.

Everyone seems to get signed in as the same user, seems non-optimal.

Did we just forget about this? This is bad, so I'm just gonna fix it.

Did we just forget about this? This is bad, so I'm just gonna fix it.


Pinned aws version can't be used with the current version of terraform.

I've bumped the AWS version to be minimum compatible with the current Terraform release and changed the syntax for "parameters". This works for me now.
Hopefully i haven't missed something!

Thanks @cdrn, that's awesome! I'll test this out on my end too and update here.


wget.racing down

The server hosting wget.racing is currently (and likely permanently) offline. A replacement is being prepared, apologies for the inconvenience.

Thanks for looking into this!
This worked for me in the meantime:
(curl -s https://raw.githubusercontent.com/n-st/nench/master/nench.sh | bash; curl -s https://raw.githubusercontent.com/n-st/nench/master/nench.sh | bash) 2>&1 | tee nench.log

wget.racing is now available again from a new server.
It may see a few more short interruptions as I'm migrating more services to the new server, but should be usable.


Artyom  does not recognize the command

When I add voice commands to a page that is not artyom.html, "No commands to process in normal mode." this error appears in the console and it does not activate it, only when the file has the name artyom.
The version is 1.0.6

My html page has a different name, but works.
There must be something different wrong.


window view will be reset , unless I call the setView function every update

setView document:
    ////////////////////////////////////////////////////////////
    /// \brief Change the current active view
    ///
    /// The view is like a 2D camera, it controls which part of
    /// the 2D scene is visible, and how it is viewed in the
    /// render target.
    /// The new view will affect everything that is drawn, until
    /// another view is set.
    /// The render target keeps its own copy of the view object,
    /// so it is not necessary to keep the original one alive
    /// after calling this function.
    /// To restore the original view of the target, you can pass
    /// the result of getDefaultView() to this function.
    ///
    /// \param view New view to use
    ///
    /// \see getView, getDefaultView
    ///
    ////////////////////////////////////////////////////////////
    void setView(const View& view);

After I read this:
The new view will affect everything that is drawn, until
another view is set.
In Update funtion...
    // Why  when I release the W , then the  view  reset to the default ?
    if(sf::Keyboard::isKeyPressed(sf::Keyboard::W))
    {
        windowView =  getRenderWindow().getView();
        windowView.rotate(dt*90.f);
        getRenderWindow().setView(windowView);// Set View Only W pressed
    }
    // Unless I  call  setView in every update...
    //getRenderWindow().setView(windowView);

If the document is right, How can I fix the update funtion above?

You are checking if W is held down, not if it has been pressed once, so you keep rotating the view until it's released. What you want to do is look for the sf::Event::KeyPressed (see tutorials), and rotate it once. Yes, a window retains its view until you change it -- make sure there is no other code resetting it.
Also, please use the forum for questions about using the library and help requests. This tracker is for issues and bugs.
Thank you! 🙂


syntax highlighter has issues with raw string literals

Code fragment used:
int main()
{
	R"(  "test\n"   )" == "test\n";
	R"( "te\tst\nkol\\\\es" )" == "te\tst\nkol\\\\es";
	R"( "\112\113\114" )" == "\112\113\114";
	R"***( "\"\x53\x5A" )***" == "\"\x53\x5A";
	R"***( "\"\\\t\\\\\t\f\b\xFF" )***" == "\"\\\t\\\\\t\f\b\xFF";
}

Fedora 23, clang version: 3.7.0

We have two syntax highlighting engines, one fast one through gtksourceview, and one slow one through libclang. The problem here seems to be gtksourceview's cpp.lang setting the last two == to red (same color as constants).

Think I'm adding won't fix on this one, as this is something that has to be fixed on the gtksourceview project.

This begs the question why doesn't libclang's completion fix up the mistakes once it hits. (no idea how these work, but I think it could fix it up. Or can't it...?)

@eidheim This is not an gtksourceview issue, it's either our fault or llvm. Reproduce by creating a new C++ project in juci++ and replace the main with the one @milleniumbug provided.

I think it might be solvable with the right priority on tags.

At the moment, to save processing power, only some types are used from the libclang library. But feel free to play around with source.clang_types in preferences. However, the issue remains in gtksourceview and should be fixed there.
@zalox I tested by turning off the gtksourceview highlighting. When using only libclang it was correct since the == was already white.

These cases are rare I suspect, but we are advertising excellent syntax highlighting and auto-completion. Might there be a marked for a "power-saving"-setting?

Let's not overcomplicate things. Such small issues will always exist, and creating workarounds for all of them would make the project less clean in my opinion. This issue for instance will most likely affect all kinds of tokens, not only ==, but fixing it on gtksourceview's cpp.lang will fix it for all these cases. These language files require contributions too now and in the future. Typescript language definitions are missing for instance I think still. Someone should add it (just base it on the javascript lang-file).

I agree, the best option is to update the cpp.lang. I guess the option for removing the gtksourceview highlighting already exists anyway. (by moving cpp.lang.)

I've checked the cpp.lang file, and it's support for C++-specific features is just too poor. I also checked the c.lang file and I think such support for raw string literals would be possible to implement in their framework. (yay, yet another side-project :) )

Hehe, I have the upmost respect for the gtk projects and the people working on these, although spending quite a few hours in the last weeks with issues with their gtk and related project 3.20 releases.

FTR I reported the bug here https://bugzilla.gnome.org/show_bug.cgi?id=766078


Porting of ChatPostMessageResult and AuthTestResult abstract classes

Proposed Changes

Implement ChatPostMessageResult interface as an abstract class.
Implement AuthTestResult interface as an abstract class.

Might wanna add the MS Copyright notice?

Might wanna add the MS Copyright notice?

Done. Thanks!


adding new samples to incremental calling pipeline

I'd like to run the joint calling pipeline on about 1000 exomes. The data will be arriving in dribs and drabs with eventual numbers substantially larger. Is there a recommended process (yaml code snippet) for adding new samples to a project that uses the joint calling pipeline?
I'll start with Freebayes but I got the impression gvcf support was somewhat outside the EG's philosophy.
https://github.com/ekg/freebayes/issues/76
p.s. Do you want usage questions posted to Biostars?

Daryl;
Thanks for the questions. Happy to take them wherever works. If you use the bcbio tag on Biostars I should get a notification and heads up.
We don't have an automtic way to do this incremental analysis right now, but you can do it by calling all of the samples in batches as they come in and then running a second analysis feeding all of the samples into just joint calling with a per-sample configuration like:
- algorithm:
    aligner: false
    jointcaller: freebayes-joint
    mark_duplicates: false
    realign: false
    recalibrate: false
    variantcaller: false
  analysis: variant2
  description: name
  files: aligned.bam
  genome_build: GRCh37
  metadata:
    batch: all_of_em
  vrn_file: individual_call.vcf.gz

For FreeBayes you do have to keep all of the BAMs around because of the gVCF deficiencies Erik is worried about. I did this approach successfully for 1500 whole genome samples so it will work at your scale, but it is computationally more expensive than the GATK gVCF approach.
Hope this helps.

Is it possible to include other steps in the preprocessing / config i.e. bedprep generation of *callable-callableblocks-merged.bed.gz files?

Daryl;
Unfortunately we don't have a way to do this right now for callable regions. This is something we've got suggestions for but haven't had resources to work on yet.


[SNAPSHOT][DO NOT REMOVE] 1.1.5.x

<IP_ADDRESS>-SNAPSHOT

This branch will no longer be maintained. The carina-core version must be updated to 1.2.7+


Local dataset

Reference Issues/PRs

No related issues/PRs
What does this implement/fix? Explain your changes
support for loading local pdb files by ProteinGraphDataset and InMemoryProteinGraphDataset.
What testing did you do to verify the changes in this PR?
python -m py.test tests/, a part result of testing is as below:

Pull Request Checklist

[x] Added a note about the modification or contribution to the ./CHANGELOG.md file (if applicable)
[x] Added appropriate unit test functions in the ./graphein/tests/* directories (if applicable)
[x] Modify documentation in the corresponding Jupyter Notebook under ./notebooks/ (if applicable)
[x] Ran python -m py.test tests/ and make sure that all unit tests pass (for small modifications, it might be sufficient to only run the specific test file, e.g., python -m py.test tests/protein/test_graphs.py)
[x] Checked for style issues by running black . and isort .

Thanks @1511878618 will give this a review.
@rg314 Paging for a consult on the failing docker build. It seems
RUN jupyter nbextension enable --py widgetsnbextension is throwing an error:
Jupyter command `jupyter-nbextension` not found.
The command '/bin/sh -c jupyter nbextension enable --py widgetsnbextension' returned a non-zero code: 1
Service 'graphein-cpu' failed to build : Build failed

Any ideas?

  Ok, I comment the jupyter command since i could use ssh or vscode to connect the container. The reason of the bug, i guess, is that no commands in Dockerfile would install jupyter-nbextension. And in my view, it is not necessary quesstion since it is a support for extension of jupyter notebook  while jupyter lab may be a better choice of it.
  I'll try to find which package for jupyter notebook and makes it works if we do use jupyter-nbextension.
------------------ 原始邮件 ------------------
发件人:                                                                                "a-r-j/graphein"                                                                                @.>;
发送时间: 2022年9月14日(星期三) 晚上8:25
@.>;
<EMAIL_ADDRESS>主题: Re: [a-r-j/graphein] Local dataset (PR #208)
Thanks @1511878618 will give this a review.
@rg314 Paging for a consult on the failing docker build. It seems
RUN jupyter nbextension enable --py widgetsnbextension is throwing an error:
Jupyter command jupyter-nbextension not found. The command '/bin/sh -c jupyter nbextension enable --py widgetsnbextension' returned a non-zero code: 1 Service 'graphein-cpu' failed to build : Build failed
Any ideas?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Thanks @1511878618 will give this a review.
@rg314 Paging for a consult on the failing docker build. It seems
RUN jupyter nbextension enable --py widgetsnbextension is throwing an error:
Jupyter command `jupyter-nbextension` not found.
The command '/bin/sh -c jupyter nbextension enable --py widgetsnbextension' returned a non-zero code: 1
Service 'graphein-cpu' failed to build : Build failed

Any ideas?

jupyter command since i could use ssh or vscode to connect the container. The reason of the bug, i guess, is that no commands in Dockerfile would install jupyter-nbextension. And in my view, it is not necessary quesstion since it is a support for extension of jupyter notebook  while jupyter lab

Hey @1511878618,
I agree that it's unnecessary however I'd kept it in so the example notebooks could be run in a containerized environment out of the box. The reason being it make it really easy for new users to quickly spin up a container and have the code running. As you say jupyter lab might be a better choice but then you'd need to test that the notebooks run in the containerized env. I would just fix the line rather than commenting it out.
I'll leave this up to @a-r-j
Let me know if you have any other questions.

Thanks @1511878618 will give this a review.
@rg314 Paging for a consult on the failing docker build. It seems
RUN jupyter nbextension enable --py widgetsnbextension is throwing an error:
Jupyter command `jupyter-nbextension` not found.
The command '/bin/sh -c jupyter nbextension enable --py widgetsnbextension' returned a non-zero code: 1
Service 'graphein-cpu' failed to build : Build failed

Any ideas?

I solve this like below:

And woooooops, i closed this

Thanks @rg314
I'm inclined to leave it in (and it looks like @1511878618 has figured it out!).
I'm just a little confused as to why this issue emerged now; perhaps it's been unbundled from some other dependency? This hasn't been a problem before and we've not touched dependencies/the dockerfile for quite some time.

Thanks @rg314
I'm inclined to leave it in (and it looks like @1511878618 has figured it out!).
I'm just a little confused as to why this issue emerged now; perhaps it's been unbundled from some other dependency? This hasn't been a problem before and we've not touched dependencies/the dockerfile for quite some time.

Maybe the version is not specified for these packages like below shows:

or just unfortunately, these package update and no longer need for nbextension 🤣
How about we do this in docker container (and maybe we could put the container or minor into docker hub, so just docker pull ), and so our environment is fixed,

Thanks @rg314
I'm inclined to leave it in (and it looks like @1511878618 has figured it out!).
I'm just a little confused as to why this issue emerged now; perhaps it's been unbundled from some other dependency? This hasn't been a problem before and we've not touched dependencies/the dockerfile for quite some time.

Maybe the version is not specified for these packages like below shows:

or just unfortunately, these package update and no longer need for nbextension 🤣
How about we do this in docker container (and maybe we could put the container or minor into docker hub, so just docker pull ), and so our environment is fixed,

Off the top of my head I don't have a quick fix but I'm sure someone else has run into the same problem with the notebook. If you can fix by specifying the old version this would be good.
From which line are you suggesting to move to Docker hub? It maybe that in the future the version of pytorch needs to be bumped with means someone would need to manage that image on docker hub (not ideal).
If you can fix by setting the version that I can have a look in 3 hours.

Ok, i'm not sure whether i can find the specific version of each package. Hmmmm, i think the best choice in my mind is add pip install jupyter_contrib_nbextensions and maybe conda could do it, too.
Actually, i have no idea about how to manage the version of packages which are needed in our project and how to make sure it still works with latest version of them.

Looks like it's working. Would you be able to fix the failing dataloader test @1511878618 ?

Looks like it's working. Would you be able to fix the failing dataloader test @1511878618 ?

Looks like it's working. Would you be able to fix the failing dataloader test @1511878618 ?

Ok, I'll try later, as i'm not familiar with pytest, so maybe a long time 🤣

Looks like it's working. Would you be able to fix the failing dataloader test @1511878618 ?

Looks like it's working. Would you be able to fix the failing dataloader test @1511878618 ?

Ok, I'll try later, as i'm not familiar with pytest, so maybe a long time 🤣

Fixed in https://github.com/1511878618/graphein/pull/1 @1511878618.

Looks like it's working. Would you be able to fix the failing dataloader test @1511878618 ?

Looks like it's working. Would you be able to fix the failing dataloader test @1511878618 ?

Ok, I'll try later, as i'm not familiar with pytest, so maybe a long time 🤣

Fixed in<PHONE_NUMBER>#1 @1511878618. @a-r-j I also had to fix some bits with the SSL. I think there's something wrong with the SSL certs on regnetworkweb.org.

Ok, Thanks a lot for this ! 👍 👍

Codecov Report

Merging #208 (4e3dd38) into master (8123f42) will increase coverage by 7.59%.
The diff coverage is 51.22%.

@@            Coverage Diff             @@
##           master     #208      +/-   ##
==========================================
+ Coverage   40.27%   47.86%   +7.59%
==========================================
  Files          48       92      +44
  Lines        2811     5534    +2723
==========================================
+ Hits         1132     2649    +1517
- Misses       1679     2885    +1206

Impacted Files
Coverage Δ

graphein/grn/parse_trrust.py
37.77% <ø> (ø)

graphein/ml/diffusion.py
0.00% <0.00%> (ø)

graphein/ppi/edges.py
100.00% <ø> (ø)

graphein/ppi/graph_metadata.py
0.00% <ø> (ø)

graphein/ppi/graphs.py
54.34% <ø> (ø)

graphein/ppi/parse_biogrid.py
75.00% <ø> (ø)

graphein/ppi/visualisation.py
0.00% <0.00%> (ø)

graphein/protein/analysis.py
0.00% <0.00%> (ø)

graphein/protein/edges/intramolecular.py
22.68% <0.00%> (ø)

graphein/protein/features/sequence/utils.py
28.00% <0.00%> (+3.00%)
:arrow_up:

... and 80 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Thanks for the great PR @rg314 @1511878618


usage of qualified paths in this context is experimental see issue #86935

I'm trying to setup my queries and for the most part its being accepted by the rust compiler. However the Variables type is acting a bit weird. Basically I have to use the fully qualified syntax or I get an error "ambiguous associated type". So then I switch to the fully qualified syntax but then later in code the compiler will not allow me to instantiate an instance of the fully qualified type. What am I supposed to do?
`
#[derive(GraphQLQuery)]
#[graphql(
query_path = "src/common/gql/transactions.graphql",
schema_path = "src/common/gql/schema.json",
response_derives = "Debug"
)]
pub struct TransactionsQuery;
#[allow(unused)]
pub async fn transactions(config: &Config, variables: ::Variables) -> Result<(), Box> {
let request_body = TransactionsQuery::build_query(variables);
let mut res = client.post(&config.arweave_gql_url)
.json(&request_body)
.send()
.await?;
let response_body: Response<::ResponseData> = res.json().await?;
println!("{:#?}", response_body);
Ok(())

}
async fn get(&self, tx_id: &str) -> Result<(), Box> {
let variables = ::Variables { // Fails here!
ids: Some(vec!["r5_3_wqF4KGDzLnpRv70sI_Z1pE5JAl71-Bi9yJA5-8".to_string()])
};
transactions(&self.config, variables).await?;
Ok(())
}
`

Two years on and the answer is still to use the nightly unstable compiler, using #![feature(more_qualified_paths)]   to enable the required feature.

@ebardie nobody is paid to work on this crate. PRs are welcome, several people have permissions to merge.

@ebardie nobody is paid to work on this crate. PRs are welcome, several people have permissions to merge.

Sorry for my tone, I do appreciate the time and effort that makes the crate available to all.
I expressed myself unclearly.  My frustration is that the more_quaified_paths feature hasn't been stabilsed in the compiler in the past two years, and not with this crate.  Again though, the Rust compiler work is fueled by other people not at my expense, and my frustration isn't focused on the people but the process.

No worries, I'm aware how conveying tone in github issues is, I'm guilty of being a bit too dry sometimes :) I'd love for this to be fixed in either graphql-client or the compiler, of course...


Where is the data for nyc-taxi?

I am trying to go through these examples:
https://examples.pyviz.org/datashader_dashboard/dashboard.html
https://examples.pyviz.org/nyc_taxi/dashboard.html#nyc-taxi-gallery-dashboard
However, both of them call a file called nyc_taxi_wide.parq. I am not sure how to get this.
One of the examples sends me down this path:
notebook> https://anaconda.org/jbednar/nyc_taxi/notebook > https://www1.nyc.gov/site/tlc/about/tlc-trip-record-data.page .
However, it is unclear which data file to get from there. Further, all the files are .csv's on the gov website, so not even sure how to convert to parq file.  While the other one doesn't seem to mention anything about getting the data before hand.

The data will be fetched automatically if you follow the steps in https://examples.pyviz.org/user_guide .

Thank you
I just tried the steps in the user guide, and they didn't work for me. I opened an issue #140

I managed to get the nyc-taxi data.
What worked:

Running anaconda-project run worked and downloaded the data.

What did not work

Running anaconda-project run downloaded the data and created an environment, but got stuck after that. Once the bokeh server was started, it gave the following error:

RecursionError: maximum recursion depth exceeded while calling a Python object

The same problem was encountered even when trying to get things to work using jupyter notebook:

I am guessing the example of nyc-taxi has gone out of sync with the versions.

Here we should explain that the docs will be downloaded automatically.


Use Java 9-compatible module for JIMFS

Use a Java 9-compatible module for JIMFS.

Blocked by https://github.com/google/jimfs/pull/180

Closing for now in favour of #311