Support for macOS release mode (1 of 2)

Description
Update the assemble commands to generate an App.framework for the macOS project instead of producing individual artifacts. This is implemented via flutter assemble and produces a "dummy" App.framework which also contains the resources necessary to run a debug application.
Once we build the aot artifacts for macOS, this can be transparently updated to compile a real App.framework and exclude debug artifacts, thus adding release (and profile) mode support to macOS without further project changes.
This also removes some of the assemble usages that did not work well, such as placing all artifacts within the cache and forcing macOS to build there. Instead, we'll gradually add support for aot by caching in the .dart_tool directory and copying out into the framework during the bundle step. This avoids the awkward and error prone synchronization of the build directory.
This requires the project changes in https://github.com/google/flutter-desktop-embedding/pull/475

@stuartmorgan I made this more confusing than it needed to be by bundling it with the  tool changes to support real AOT. I'll split those out into a second PR to make this easier to review


TFJob cannot utilize GPUs in the node.

I have an Azure (AKS) cluster of the following configuration:

4x Standard_DS2_V2 nodes
8x Standard_NC6 nodes

Each NC6 node is backed by a single K80 GPU.
The image I used was the tf1 image built from the Tensorflow Object Detection API docker.
I tried running a TFJob with the configuration:

Master (limit:1 GPU) 1 replicas
Worker (limit:1 GPU) 7 replicas
PS (limit:1 CPU) 3 replicas

However this job failed with the error in one of the workers:
tensorflow/stream_executor/cuda/cuda_driver.cc:175] Check failed: err == cudaSuccess || err == cudaErrorInvalidValue Unexpected CUDA error: out of memory

Ultimately, the job worked successfully if I used 3 Worker replicas. If I used any more than 3 Workers, the above error ocurred. This is really bothering me, because I have allocated 8 GPUs in total and could only use 4! Again, I did another experiment: When my node had 3 GPU nodes, I could only use 1 master and 1 worker; 1 master and 2 workers led to the above error.
These above jobs were run with relatively small amounts of data. I ran another job with more data, and became confounded: I could only use 1 Master and 1 Worker, even thought the cluster had 8 gpu nodes. Any more than 1 worker and the old error struck again.
At this point I'm not sure what is causing this, leading me to file an issue. If this is not a TFJob specific issue, I'll close this and then refer to the Object Detection API; it may be a code specific issue as well.
Any help would be appreciated. Thanks!

out of memory

GPU memory is not enough for your training job.

out of memory

GPU memory is not enough for your training job.

But the training job works and finishes successfully when I reduce the number of GPUs. What is the reason behind this?

I think it is not caused by TFJob, it may be related to TensorFlow. Can you monitor the GPU and see when it OOMs?

BTW, are you increasing the batch size when you use more replicas?

Yeah it is also likely that this is caused by TensorFlow. I'll try monitoring the GPU, this is a good idea. And the batch sizes are kept to the minimum, which is 1.

Then it is weird. Please keep sync here if there is progress.

Then it is weird. Please keep sync here if there is progress.

Will do!

Did you fix the issue?

I haven't solved it yet. My team has gotten in touch with technical support from Azure, and they're looking into this at the moment. But I will close the issue here, since it seems probable that this is being caused by the inner workings of the OD API iteself, rather than any component in TFJob or Kubeflow. Thank you for all the responses thus far!


Error when an known variable is set but not used by the current flow

meta 2

This breaks any instances of the same config file being used for multiple flows. What prompted this?a

To clarify, I am including things such as --flow OpenInKLayout

This breaks any instances of the same config file being used for multiple flows. What prompted this?

I was attempting to run an old design with a custom flow. It was using GRT_REPAIR_ANTENNAS but the step was not in the custom flow (since it was recently reworked). A user would potentially be under a false assumption that the step ran.
I wasn't aware of the breakage but we should find a strategy for such scenario.

At any rate, this is not the solution. We can discuss other approaches

I think the original problem is handling old configuration files that uses steps whose behavior have drastically changed.


Allow for cases where a return intent should be sent

Adds a method which can be overridden by an activity which extends IntroActivity so that when IntroActivity prepares to set the result to RESULT_OK, it gives the extending activity class the chance to construct an Intent to set as the return intent.
See #95 for further details.

Looks great!
I only have to make some small changes in that pull request.

Approved


Support variable precision in GRO writer

Description
Resolves #117
Checklist

[ ] Add tests
[x] Lint
[ ] Update docstrings

Hey, something worked on CI after working on my computer!


HDDS-5767. Unit check may timeout

What changes were proposed in this pull request?
Increase timeout for basic check to avoid edge case where basic (unit) check timeouts.
https://issues.apache.org/jira/browse/HDDS-5767
How was this patch tested?
Check completed successfully in ~47 minutes:
https://github.com/adoroszlai/hadoop-ozone/runs/3652391011

Thanks @sodonnel for the review.


Can you showSimpleNotification from the bottom of the screen?

Is it possible to have the notification show at the bottom of the screen rather than the top? Is there something I could modify in the package to get it to show at the bottom instead of the top?

Yes, you can use the method showOverlay to customize the effect you want.

Thanks! Do you have a quick example syntax i could use as an example?

OK, sorry for delay.

class BottomSlideNotification extends StatelessWidget {
  final double progress;

  final WidgetBuilder builder;

  const BottomSlideNotification({Key key, this.progress, this.builder})
      : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Material(
      color: Colors.transparent,
      child: Align(
        alignment: Alignment.bottomCenter,
        child: FractionalTranslation(
          translation:
              Offset.lerp(const Offset(0, 1), const Offset(0, 0), progress),
          child: builder(context),
        ),
      ),
    );
  }
}

then you  can use showOverlay function

showOverlay((context, t) {
  return BottomSlideNotification(
    progress: t,
    builder: (context) {
      return SafeArea(
        child: ListTile(
          title: Text("from bottom"),
        ),
      );
    },
  );
});

@boyan01 excellent, thanks so much for your help


Do not get table output

I do not get any code beside the header comment when I call it as follows
./pycrc.py --width=8 --poly=0x07 --xor-in=0 --xor-out=0x55 --reflect-in=false --reflect-out=False --table-idx-width=4 --algorithm=table-driven --generate=table
I ecpected some kind of hex number sequence to be included in my static table (at least v0.7.8 worked this way).

Thanks Johannes for reporting this. This is fixed in v0.9.2

Thank you for your really quick response. I will test it the next few days. Regards...


Improve type safety with generics on simulators

I think there are some open issues complaining about some of these things? Can you find them and see if this addresses them?

@mpharrigan There was only #554 about the general problem from a while ago. Added a link there but there's still more work to be done before closing that particular issue. There are some other open type issues around gates and operations, parameters, and such but I didn't see any open issues referring specifically to simulators.

Does this PR address https://github.com/quantumlib/Cirq/issues/2413?

Oh, I didn't see that one. Yes, that should be fixed now.
On Fri, Feb 19, 2021, 1:17 PM Matthew Harrigan<EMAIL_ADDRESS>wrote:

Does this PR address #2413
https://github.com/quantumlib/Cirq/issues/2413?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/quantumlib/Cirq/pull/3818#issuecomment-782357838, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG464IZ22HW3S6AAU53KSDS73INTANCNFSM4XYUOBRA
.


Not accurately for fingerprint

Windows.Security.Credentials.UI.UserConsentVerifier.CheckAvailabilityAsync(), I have checked the doc for this api, and it is said that this api is to check the availability of user consent verifier, including fingerprint, windows password PIN, windows hello and etc. If any one of these are available, this api will return Available, it not for fingerprint only and it can't tell the status of fingerprint. I have tested in a machine that set the PIN but no fingerprint it return available.
https://docs.microsoft.com/en-us/uwp/api/windows.security.credentials.ui.userconsentverifier.checkavailabilityasync#Windows_Security_Credentials_UI_UserConsentVerifier_CheckAvailabilityAsync

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

ID: feadf273-2dac-2af0-1fa6-c2bad76a9c23
Version Independent ID: 2fec4ec8-7290-df7e-5514-82b0ca729915
Content: Fingerprint biometrics - UWP app developer
Content Source: windows-apps-src/security/fingerprint-biometrics.md
Service: unspecified
GitHub Login: @msatranjr
Microsoft Alias: misatran

It looks like your feedback concerns the product itself, rather than the documentation for the product. Unfortunately, GitHub issues in this repo are only used for documentation issues.
The best way to leave product feedback is through the Feedback Hub app. If you return to the documentation page related to this issue and scroll to the bottom, there is a button to leave feedback about this product
For completeness' sake, here is a list of developer resources:

The Feedback Hub app is the right place to suggest or lobby for a change or feature.
Try our forums and StackOverflow for community assistance with development questions.
The Windows developer support site explains other support options.
The Visual Studio developer community is helpful and responsive. You can also suggest or lobby for a change or feature by clicking the report a problem or suggest a feature buttons.
For developer issues or suspected product bugs, visit Microsoft Support. A support engineer will determine whether the issue is a Microsoft product bug. If it is, the ticket will be free of charge.

If you receive assistance via any support resource and you believe that information would help us improve the docs, then please let us know or consider submitting a pull request.
Thanks,
Shawn


confused about the bert-multitask-learning/baseline.md

Hi~
I'm a bit confused about the results in the baseline.md:
Does the baseline mean that we use the bert model without multi-task learning and the multitask_label_transfer_first_train mean that we use the bert model with multi-task learning?
It seems that all the results prove that the multitask_label_transfer_first_train  is not as good as  the baseline?
Hope to get your reply. Thanks a lot.

Hi,
Baseline means training the problem individually and multitask means training multiple problems at the same time. Yes, multitask training is not as good as training each task individually. I have tried various tricks(please look for # multitask in params.py) and none of their result can dominate the baseline.
And please note that the results are outdated because I updated the tokenizer for better sequence labeling and the results are not updated. However, the conclusion holds for either tokenizer.
I will update the results in couple days. Thanks for bringing this up!

The baseline is updated. Closing the issue.

The baseline is updated. Closing the issue.
@JayYip
Hi,
I just noticed that you have been upgraded the baseline.md.
The F1 value of the WeiboNER(singleTask) is 0.5735 which is 11% lower than before. (I remember that the previous F1 value was around 0.68.)
Is there any change?
Hope to get your reply, Thanks.

Oops. Caught up by other things lately and didn't have time to take a deep look at the results. Now the results are strange and I spotted a bug in generating evaluation data which caused severe result underestimation.
I'll re-open the issue and fix it today. Thanks!

Bug fixed and baseline updated. Closing the issue.

Hi @JayYip, in Microsoft paper mt-dnn, they prove multi-task learning can improve the performance of bert, did you have any studies in why the multi-task is not good as single task in your proposed, or maybe there are other tricks in mt-dnn, thanks.


Preserve pagination after actions which trigger a grid update

This is a backport of #5411 to the master branch. Closes #33, closes #570, closes #572 (already marked as such by #5411).
For this one, although the change was sort of forced on me by the new architecture, it can be backported with reasonable effort to the master branch.
Summary: this changes the grid pagination so that users to not input a page number, but the index of the first row in the view. Why do this?

it solves #33 and others, because starting row number can be meaningfully preserved for all row-wise operations. In comparison, preserving the page number is not guaranteed to keep the view in the same place because changes to earlier rows can shift page boundaries
it's generally a better practice for pagination, as is explained by various documents (such as https://medium.com/swlh/sql-pagination-you-are-probably-doing-it-wrong-d0f2719cc166)
it's required for the new architecture, which is what pushed me to working on this.

It's a change that has implications for the UI and the web API (which is not meant to be stable).
It relies on manually annotating all operations with row/record preservation. In this PR it is done in the frontend, but further backend changes will move this information to the backend (making it possible to detect the row/record preservation of sequences of operations run via the apply-operations command, for instance).
One oddity of this change is that in records mode, the pagination is still done based on row ids and not on record ids. This is intentional, because:

it would make it possible to switch between rows and records mode while preserving pagination (although this is not enabled so far)
so far, the new architecture drops the notion of record ids and uses the starting row index instead. This is primarily for performance reasons, as it enables more efficient record grouping.

p.s. I had rebased your branch onto master so that I could test with the latest code base, but perhaps something get messed up, so I'll retest with an untouched version of the branch.

Thanks for the review! Good catch, I simply hadn't enabled the preservation of pagination for the 'Choose new match' button. It should work now.

Hi - I've been trying this, love that it mostly fixes the problem! However if you navigate to a page while reconciling using the "Previous" link (going back in pages), then the first match done on a page removes all reconciliation links and data on the page. Navigation back one more page (Previous) and then forward (Next) restores the reconciliation data, and in general when you navigate via "Next" it always works fine.

Thanks a lot for trying it out and finding this bug! That was an oversight on my part which should be fixed.

@tfmorris do you intend to review this PR again or is it good to go on your side? I'd be interested in merging it to unblock #6563.


Tycho

Screenies
Bucket List (Home)

Bucket Content

Log

License

Supported API

Can't we document the APIs using our /system/api mechanism?

Unfortunately, this is not trivially possible. The relevant requests are processed via a special dispatcher with curious mechanics off the charted routes. It would be highly desirable, though, and may be the subject of future refactoring.


user-guide: add a doc about resolving merge-conflicts

https://github.com/iterative/dvc/pull/4298

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏

Super cool doc, thanks @efiop ! Please let us know when you'd like us to review it. I just did a quick read so far.

@jorgeorpinel what is the status of this? Can we merge this? Looks like only some minor things left?
@efiop @jorgeorpinel should we put some links to dvc add, dvc run, any other places, to this doc?
@efiop great start, good and simple summary of different possibilities.

Can we merge this? Looks like only some minor things left?

I approved this some time ago 🙂 although
a) I think it could be shortened as explained in https://github.com/iterative/dvc.org/pull/1684#pullrequestreview-464382836.
b) I just noticed another possibly relevant question, see https://github.com/iterative/dvc.org/pull/1684#pullrequestreview-469627408 above.

put some links to dvc add, dvc run, any other places, to this doc?

OK hold on... ⌛


Failed to start on Fedora22

The xrdp service failed to start automatically on my Fedora22.After I manually execute xrdp and xrdp-sesman I can connect from MSTSC but still with login failure.I install it following the instructions in readme.txt and it seemed going smoothly.There lots of related information in journalctl and other logs.And I don't know what to show here as well as what to do.Anybody could help?

Can you start xrdp service manually?

@metalefty If I use "systemctl start xrdp.service" command and it will give this back:

A dependency job for xrdp.service failed. See 'journalctl -xe' for details.

If I start xrdp-sesman.service in the same way, the information is like this:

Job for xrdp-sesman.service failed. See "systemctl status xrdp-sesman.service" and "journalctl -xe" for details.

I execute xrdp and xrdp-sesman in terminal and the service seemed to start but when I log in with MSTSC, I can see the login frame but after submit it returned:

xrdp_mm_process_login_response:login failed

Looks like the same issue as mine, since Fedora 21. Unfortunately I have no idea yet.

neutrinolabs/xrdp#236
metalefty/X11RDP-RH-Matic#13

@metalefty Wow, that might be something related to system designs or kernels.I do like this software a lot and I hope this problem can be solved.Thanks a lot for answering.

I am working to have a working rpm for F-22, this bug is related to selinux, here are more info ->
https://bugzilla.redhat.com/show_bug.cgi?id=1177202

Good news! Fixed in Fedora 23.
https://bugzilla.redhat.com/show_bug.cgi?id=1177202#c25
It will take significant time the fix come down to RHEL or clones but this issue is considered to be fixed.

Fixed in Fedora.


Consider using qtpy?

Hello,
Amazing work getting this all together.
Would you considering using qtpy instead of PyQt5 in your imports?
It mostly lets us that are on the bleeding edge experiment with PyQt6/PySide2/PySide6 a little more freely.
Thanks!
2 line patch below.
diff --git a/micro_sam/sam_annotator/annotator.py b/micro_sam/sam_annotator/annotator.py
index 9be755f..8ec02ed 100644
--- a/micro_sam/sam_annotator/annotator.py
+++ b/micro_sam/sam_annotator/annotator.py
@@ -7,7 +7,7 @@ import numpy as np
 import zarr
 from magicgui.widgets import Container, Label, LineEdit, SpinBox, ComboBox
 from magicgui.application import use_app
-from PyQt5.QtWidgets import QFileDialog, QMessageBox
+from qtpy.QtWidgets import QFileDialog, QMessageBox

 from ..util import load_image_data, get_model_names, _DEFAULT_MODEL
 from .annotator_2d import annotator_2d
diff --git a/micro_sam/sam_annotator/gui_utils.py b/micro_sam/sam_annotator/gui_utils.py
index fb41242..bf9b8a0 100644
--- a/micro_sam/sam_annotator/gui_utils.py
+++ b/micro_sam/sam_annotator/gui_utils.py
@@ -6,7 +6,7 @@ from typing import Union
 from magicgui.widgets import Container
 from magicgui.application import use_app

-from PyQt5 import QtWidgets
+from qtpy import QtWidgets

 def show_wrong_file_warning(file_path: Union[str, os.PathLike]) -> Union[str, os.PathLike]:

Done in #275. I have merged this into the dev branch, which contains most of the recent changes. I will merge this into master and create a new release in the next few weeks. Let us know if there are any other issues with this ;) .

amazing thanks!


Can't add modded biomes or dimensions

I wanted no snow in the dimensions, so I changed invertNonWinterBiomes to true and invertNonWinterDimensions to true, and it worked. But when i wanted to add dimensions or biomes (in my case "aether:the_aether" and some incendium biomes, the whole world had no snow. Pretty much i broke the config, but i still want to know what's wrong

As I'm not magic and can't see inside your config file, I cannot tell you what's wrong. There seems to be some issue w.r.t dimension/biome blacklisting you might be running into. See #101


Show remaining balance of authorized amnt

When the WM extension is connected to a digital wallet, there is an amount of money/value that the user authorizes the extension to access from the user's connected wallet.
The extension pop-up should accurately update the displayed remaining balance of the authorized total value.

Relevant: https://github.com/interledger/open-payments/issues/469

Is this ticket still blocked @raducristianpopa @sidvishnoi?

Correct. Still blocked.

What's blocking it? Tseli mentioned that the Open Payments issue is resolved. I guess we also need to define the UI

Pending on releases (Rafiki, Open Payments client).
UI: I think there's something in the Figma (link in #web-monetization-extension Slack channel's pinned message), but not sure if it's outdated

https://rafiki.money now returns grantSpentDebitAmount.
Now blocked only on open-payments SDK update.


Audit: Cypress tests for contributors

Overview
A duplicate of this issue - https://github.com/chaynHQ/ysm/issues/228 but with special attention to Cypress environment variables.
Currently these tests cannot be ran by contributors. We need to update the documentation to reflect this and note of potential new issues to increase e2e test coverage.
Action Items

[x] Gather test env vars
[x] Complete issue - https://github.com/chaynHQ/bloom-frontend/issues/705
[x] Discuss solutions for inaccessible Cypress env vars
[x] Update docs and create new issues if needed.

Resources/Instructions

Currently, integration tests are inaccessible to outside contributors. Bumble and badoo testing env vars are impossible for external contributors to source, and very few available for staff.
Integration tests are being ran using GitHub Secrets in GitHub Actions.

Done: https://github.com/chaynHQ/bloom-frontend/commit/df3501bfaa9b7efbff4dc4072e643e1a6eeb7933


Add Oracle as hard

URL: https://www.oracle.com/legal/data-privacy-inquiry-form.html
difficulty: hard
notes: You have to send a privacy inquiry to get your data deleted. (It can take a few days)

Thanks for your contribution!


⚠ Bofrost.be has degraded performance

In daccb15, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1748 ms

Resolved: Bofrost.be performance has improved in 3db499e.


[Switch]: Styles broken

In the Switch component the styles seem to be broken in both the checked and unchecked state.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
The "line" part of the component isn't displayed at all and in checked state the "thumb" part is cut off slightly. In unchecked state the "thumb" part is always displayed as black. Also the animation seems to be missing.
Expected Behavior 🤔
The "line" part should be visible and the "thumb" part shouldn't be black but like displayed in its documentation. The component should also animate when switching its state.
Steps to Reproduce 🕹
The visual bug can be seen here:
https://codesandbox.io/s/material-ui-issue-forked-i64u2?file=/package.json
Your Environment 🌎
Happens regardless of the browser.
Other notes
In the reproduction codesandbox link, I added a slightly styled version of the Switch that has the most glaring issue (the "line" part not being visible at all) fixed.
The issue seems to be CSS injection order: the MuiSwitch-switchBase class's styles seem to be overridden by other styles.

Duplicate of #24109

You need to configure the injection order. We have finished the migration of this component in v5, so it shouldn't be as much of an issue in this occurrence.

Hmm though I forgot to put that on the codesandbox, I do have the <StylesProvider injectFirst /> in my app in which I originally noticed the issue.
I'll check if I'll figure out why it's not working there.
Thanks anyway!

Ah yeah should've read that issue this duplicates. It's the import from @material-ui/core/styles instead of @material-ui/core

My fault. I have pushed for using a component with the same name between JSS and emotion. We have renamed it afterward. Now it's StylesProvider for JSS and StyledEngineProvider for emotion/sc.


cannot get dobi examples to work

Any suggestions on why I cannot run the dobi examples?
dobi is running when I run dobi on in the main directory. For example:
ubuntu@ip-172-31-46-77:~/repos/dobi$ sudo dobi list
  all                  Run all lint and build tasks
  binary               Build the static binary
  deps                 Install go dependencies
  dist-img             Build the distribution image
  docs                 Build docs and start an http server to preview the docs
  lint                 Run style checks
  refactor-shell       Start an interactive shell for running go refactor tools
  shell                Start an interactive development environment
  test                 Run all tests
  watch                Watch for code changes and run the unit tests

however, when I try to run 'dobi list' inside the the sample cases in the examples directory, I am getting errors:
ubuntu@ip-172-31-46-77:~/repos/dobi/examples/init-named-volume$ dobi list
[ERROR] Failed to load config from "dobi.yaml": Invalid config for resource "mount=data":
Error at mount=data.name: unexpected key

ubuntu@ip-172-31-46-77:~/repos/dobi/examples/inline-dockerfile$ sudo dobi list
[ERROR] Failed to load config from "dobi.yaml": Invalid config for resource "image=dev":
Error at image=dev.steps: unexpected key

mount.name and image.steps are both new fields added in https://github.com/dnephin/dobi/releases/tag/v0.10. Which version of dobi are you running?

Ok I was at v.08
I upgraded to v0.10 and it seems to have taken care of my issue. I submitted a pull request to update the one-liner to v.10. Thanks!


Fix issues with userConfig handling in app charts

Importing https://github.com/epinio/helm-charts/pull/401
Ref #2177
Fix for the upgrade issues exposed by that PR.

And the upgrade works - https://github.com/epinio/epinio/actions/runs/4609182875


Dex Error with androidx libraries

I started a new project and I saw that in the dependencies block there are androidx libraries.
dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    implementation 'androidx.appcompat:appcompat:1.0.0-alpha3'
    implementation 'androidx.constraintlayout:constraintlayout:1.1.2'
    implementation 'com.google.firebase:firebase-core:16.0.1'
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'androidx.test:runner:1.1.0-alpha3'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.0-alpha3'
}

if I add implementation 'com.google.firebase:firebase-core:16.0.1' I got follow error:
Error: Program type already present: android.support.v4.os.ResultReceiver

There is a way to use firebase with these libraries?

Resolved and the problem was not cause by Firebase.  Indeed there are not these lines in gradle.proprerties file.
android.useAndroidX=true
android.enableJetifier=true

After I added them, everything has been ok.


Optimize custom fetch-depth settings for workflows

As part of #148 and later GH issues/PRs I switched from using a fetch-depth of 0 (everything) to the last 50 commits and also included an additional step to pull the last 50 commits from the primary & development branches.
This works and in some cases may be better than before, but I applied those settings in places where it isn't strictly needed.
For example, the go.mod validation job steps don't need 50 commits to determine whether there are missing changes, just the very last commit for the PR branch being evaluated.
There are other places where a single commit is sufficient for the workflow job(s).

For example, the go.mod validation job steps don't need 50 commits to determine whether there are missing changes, just the very last commit for the PR branch being evaluated.
There are other places where a single commit is sufficient for the workflow job(s).

I should clarify: the Assert PR branch is ahead job is the primary focus. It is unlikely that many commits are needed for this job to serve its purpose properly.


HHH-18949 backport to 6.6

[Please describe here what your change is about]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

https://hibernate.atlassian.net/browse/HHH-18949

OK, great, thanks @mbladel, I was not sure of the process.


Possible comment bug reported by user

Reported in Stackerz Chat
https://t.me/stackernews/378

right, I think this is something to do with replying to your own comment while its timing out. Steps to reproduce:

make a comment, submit it. Your comment will appear at the top of the list
before the edit-window times out, refresh the page with your browser, your comment appears at the bottom
Reply to your own comment at the bottom of the list before the edit-window times out...  Now you have two edit-windows counting down.
Wait for both edit-windows to time-out and refresh the page. Your reply will be in response to the previously-last comment in the list rather than to your own

Looks like this could be getting confused because replyOpen is being shared among the various reply components.
Maybe here?

Possibly related issue reported by darthcoin https://stacker.news/items/29464

I couldn't recreate this when I tried today and no one has reported anything like it for a over a year. Going to close. I think this was mostly a misunderstanding/user error.


PLAGE motifs are too big!

Can we restrict the size of motif nodes, or make the molecules move further away? Impossible to hover over the nodes (see screenshot)?

will try

Hi Simon,
change the parameter "charge" in d3 can move molecules further away, but I guess here is a better solution:
always put circles(motifs) under squares (molecules), then we will not have hover issues.
like this:

What do you think?

It is a working solution I would say....though it depends on the colour (differences) between circles and molecules. In this view it is quite obvious, in the PLAGE view it isn't always that obvious....


why don't have REDMINE_HOST?

so , the url in fogot password is error.

@YauzZ you should configure the redmine url in redmine settings page.

@sameersbn thx, it 's ok.


Pod::Cache isn't safe for concurrent access

when using util/update-and-test (which generates a script called retest), we are running all the test files against a small subset of the tests. If that test uses lib/Pod/Cache and it's determined that the file needs to be updated in the cache, multiple instances of the test can possible hit at the same time. This can cause the file to be mangled, causing tests like xt/aspell to fail because they are not looking at the full source.
(Try to clean the pod cache before a run of make xtest with a small number of TEST_FILES but a TEST_JOBS of 3 or so helps to highlight the issue)
Noticed because a recent run of the tools was complaining about a typo in doc/Language/typesystem.pod6 that just did not exist in the original file, nor in raku --doc output. Clearing the cache and rerunning? same error. Clearing the cache and using TEST_JOBS=1 when rerunning? avoids the error.

@JJ   - does https://github.com/JJ/raku-cache-pod/blob/master/lib/Pod::To::Cache.pm6 avoid the concurrency problems?

No, it does not, I'm afraid. It's a good idea to try and switch it anyway.
I started Cache::Pod to overcome both problems
https://github.com/JJ/raku-cache-pod but it's not there yet. Adding
concurrency to the spec.
Baseline is, concurrency is not something you can latch on later, you need
to bake it in.

OH HEY there's already a .lock in there there wasn't doing anything.

Tried to fix this a bit with:
ea98b81ac

flock seems to be working, closing ticket.

@niner points out that .lock does work in his example, so something else may be going on here. The fix here is probably also broken on Windows. So see if we can remove the flock fix and keep the working code.

While I did seem to have a bad run of pod-cache in the last refactor of xt/aspell.t, it's been behaving for me for a bit now.
Closing ticket.


Updated readme to give a bit more clarity to the code

Explained what different parts of the code achieve

What you've written feels verbose, you could probably condense it a bit.

@praveensvsrk, done! Thanks for reviewing mate!

Nice work!! Fix #12 #13


Fix autoindent for ']' in TeX

Check last character on the current line instead of the first (after indent).

You need to contact maintainer listed at the top of the file:
" Maintainer:   YiChao Zhou <broken.zhou AT gmail.com>

Bram accepts such changes from maintainers only unless it appears that maintainer is unreachable.


Added back button detection

Fixes #54. Merge if @skellock says it's okay.

:+1: -- works for our app

This is like γρεεκ

heh


StackOverflowException running tests with DynamicData where the target class uses JToken (and dynamic).

Description
A StackOverflowException occurs running a DataTestMethod test using DynamicData when the target POCO class includes a JToken as a Dictionary TValue type.  Note, the same thing occurs if I change JToken to dynamic.
Steps to reproduce
See attached sample solution and run tests.
Expected behavior
The test receives the test case deserialized as expected without a StackOverflowException occurring.
Actual behavior
The Newtonsoft.JSON deserialization works as expected -- the object's dictionary contains one item whose value is JArray -- however, there is XML serialization happening in the DynamicDataAttribute's code that is causing a StackOverflowException.
Environment

macOS Big Sur

<Project Sdk="Microsoft.NET.Sdk">

    <PropertyGroup>
        <TargetFramework>net6.0</TargetFramework>
        <Nullable>enable</Nullable>

        <IsPackable>false</IsPackable>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.1.0" />
        <PackageReference Include="MSTest.TestAdapter" Version="2.2.8" />
        <PackageReference Include="MSTest.TestFramework" Version="2.2.8" />
        <PackageReference Include="coverlet.collector" Version="3.1.2">
          <PrivateAssets>all</PrivateAssets>
          <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
        </PackageReference>
        <PackageReference Include="NFluent" Version="2.8.0" />
    </ItemGroup>

    <ItemGroup>
      <ProjectReference Include="..\MSTestSerializationIssue\MSTestSerializationIssue.csproj" />
    </ItemGroup>

    <ItemGroup>
      <None Remove="Resources\Example.json" />
      <EmbeddedResource Include="Resources\Example.json" />
    </ItemGroup>

</Project>

MSTestSerialization.zip
AB#1642309

Encountered this as well. For now i'll probably make a workaround by passing indices of array of test data objects to the test method but i'd like to see a proper solution...

Please see this for solution.

I am currently investigating this issue and it's not linked to the test ID generation (my initial thought). It seems to be linked to some interaction between Test Platform and MSTest because MSTest 2.2.3 does work as long as I stay on 16.X of TP but using MSTest 2.2.4+ with TP 16.X also fails.
I will dig deeper to understand what's going-on.

Hey folks! It looks like it was fixed by some changes we did in MSTest in the new release we are working on. I have added a test case (and did some manual test) and I cannot repro on main of MSTest (I can repro using released version up to 2.2.10).


Add linting rule

Why this PR?
Add code format check
Visible changes
Linting rules are defined in .editorconfig file.
 property is added to the csproj file and then all code format issues will be reported during build process. In the editorconfig file, it sets the severity of IDE0055 and some other formating rules to error.
This will make build fail if the formating rule is not followed.

what's the purpose of this file: https://github.com/Azure/AppConfiguration-DotnetProvider/blob/main/AzureAppConfigurationRules.ruleset ?

what's the purpose of this file: https://github.com/Azure/AppConfiguration-DotnetProvider/blob/main/AzureAppConfigurationRules.ruleset ?

@juniwang This file is used for enforce CA2007 check. #410

what's the purpose of this file: https://github.com/Azure/AppConfiguration-DotnetProvider/blob/main/AzureAppConfigurationRules.ruleset ?

@juniwang This file is used for enforce CA2007 check. #410
Code analysis is a big topic. It includes two aspects: code quality and code style.

CA2007 belongs to code quality check.
Even for code style, there are 4 aspects as shown in the screenshot below.

In this PR, we only focus on the formatting rules.

OK,


Redis Queue: Jobs are ending up in the queue without a $payload['job'] value.

This is then causing the queue to crash because in /Jobs/Job.php resolveAndFire() and failed() methods both look for the 'job' value. It's undefined so the job never ends up as a failed job.
I've verified looking at the list in redis directly that there is a "job" simply with an ID and attempts values:
"{\"id\":\"2XB76hubeCDCRqP74lsB326oftfwMmsY\",\"attempts\":81441}"

As you can see, this is being retried repeatedly despite ---tries being set to 3.
I'm not able to work out how these payloads are ending up there without a job field, which is clearly the root cause. However it would be useful if the failed() method at least could handle this undefined index. I'm sure this might be clearer to someone with more experience with the Queue code.
I'm pretty certain the jobs that are missing the 'job' index are being added via $this->dispatch() method in the controller as opposed to the older Queue::push(), that we've been using for longer reliably.
Also using the same redis database for cache + sessions, though we've not had any problems before. This started soon after we started using the $this->dispatch() method in a controller with a

What Laravel version please.

Using "laravel/framework": "5.1.*" in composer.json

Thanks.

After reviewing this, I don't think it's a bug. Looks like you have old formatted jobs in the queue from a previous version, maybe 4.2 or something.

I'm unable to replicate this issue.

If you're able to provide very short replication instructions on 5.1, please send a new issue.

It's extremely unlikely we had old formatted jobs, we upgraded to 5.1 a long time ago now. There has to be another reason that some jobs were able to get into the queue with an ID but no $payload['job'] value.  If I can reliably reproduce I will open another issue.

I have encountered this problem, and finally what is the solution?

I faced the same issue. I am not that much sure, but one possible reason to such a problem can be that after the job serialized into the queue, you changed the name of the class, or did something similar to a property of the job and now the job cannot get unseriazlied because the class does not exists any more.

I'm newbie , so apologize me if is not a correct practice to write on a closed bug , i faced the same issue as described , but i finally make it work! , the problem seems  when attaching kind of files , datatype out of primitive types, need to be encoded in base64 , and then be decoded just when data is "gone thorough  the closure context"  and then you can decode again. Here my working  dirty example :
``
$pdf = base64_encode($this->generatePdf());
Mail::queue($this->bladeEmailTemplate, $this->emailArrayData, function ($message) use ($pdf,
$emailConfig) {
$message->from('emailFromAddress');
$message->subject('emailSubjectText');
$message->to('emailToAddress');
$message->attachData(base64_decode($pdf), name.pdf');
});
Hope this helps others !


Shim locking improvements and context cancel

This improves shim locking where we only hold the lock for shim state, and not system level operations.

Codecov Report

Merging #2589 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2589   +/-   ##
=======================================
  Coverage   44.07%   44.07%
=======================================
  Files          96       96
  Lines       10125    10125
=======================================
  Hits         4463     4463
  Misses       4940     4940
  Partials      722      722

Flag
Coverage Δ

#linux
47.79% <ø> (ø)
:arrow_up:

#windows
40.98% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ce1161f...451447f. Read the comment docs.

As long as Process is thread safe, this PR LGTM. However, operations could still block each other inside Process, given that each operation grab a lock.
Anyway, this is still better than before. :)

@Random-Liu process is threadsafe.  And this is the start of various fixes.  I'm getting timeouts working for ttrpc clients, etc

@crosbymichael SGTM. Thanks a lot! :)

LGTM


Attributes from Splunk ES Correlation Search Entry

Currently, when getting a search result back from the API (SavedSearch Entry) we can't seem to find the values that the ES Correlation Search Entry has.
I've used Postman and I can see the attributes do exist but I am unable to determine what methods to call to expose those entries via the Client Library. We are trying to get values back like the notable event information and risk scores.

action.correlationsearch.label
action.notable
action.notable.param.security_domain
action.notable.param.severity
action.risk.param._risk_score

Hi @nhalstead,
We have tested SavedSearch using Postman and yes attributes do exist. Whereas in case of fetching those attributes from SDK, it is possible to fetch all the above mentioned values. Please find below code snippet for reference.
SavedSearchCollection collection = service.getSavedSearches(); // service is instance of Service class.
if (collection != null && collection.size() > 0) {

    collection.keySet().forEach(key -> {

        SavedSearch savedSearch = collection.get(key);
        if (savedSearch != null && savedSearch.getBoolean("action.correlationsearch.enabled", false)) {

            System.out.println(
                    "Label : " + savedSearch.get("action.correlationsearch.label")
                    + ", Notable : " + savedSearch.get("action.notable")
                    + ", Sec. Domain : " + savedSearch.get("action.notable.param.security_domain")
                    + ", Severity : " + savedSearch.get("action.notable.param.severity")
                    + ", Risk Score : " + savedSearch.get("action.risk.param._risk_score"));
        }
    });
}

Please check at your end and let us know, if you still face any issues.

Hi @bparmar-splunk, appreciate the response, finally had time to test it out.
The method getBoolean is not exported from the package (it has no access modifier so it's only available at the package level), so I'm not able to call that method!
My test code:

splunk-<IP_ADDRESS>.jar: com.splunk.Entity

There is a workaround since Entity::get is public, I can duplicate the getBoolean method to run the same check.


prompt + KeyPair fixes and test cases

Fixes incorrect error handling in KeyPair
Updates prompt to properly catch errors when attempting to import an invalid wif
Add test cases for coverage

I'm surprised to see there's a conflict for missing

from neo.UInt160 import UInt160
from neo.UInt256 import UInt256

as they're both unused imports


Different PresenterManager implementations for MVI and MVP

Hi, I found out that in the 3.0 version you have introduced aPresenterManager. It has two different implementations for MVI and MVP. I've got some (rather conceptual) questions about these implementations:

Why have you decided to let them rely on a completely different mechanism of retaining presenters?
Why have you decided to abandon (kinda platform-provided) MVP retention mechanisms in MVI Fragments and Activities? Why have you decided to use PresenterManager there?

I know that these questions are rather close to the metal but I would like to get the general feeling of these decisions to understand the possible usecases better.

I have to apologize,
I simply haven't found time to refactor MVP modules.
For the final release 3.0 release both, MVI and MVP will use the same PresenterManager from the presenter manager module.

Well, I was aware that it may be like this because of the alpha stage, no need to apologize ;)
Could you tell me why you have decided to use this particular implementation, not the second one? I'm still curious about the answer for the second question: Why have you decided to abandon MVP retention mechanisms in the MVI Fragments and Activities?  Do you plan to do the same in the MVP ones?

The implementation of the presenter manager in MVP currently uses a retaining Fragment. The problem is that is is not guaranteed when this retaining Fragment is committed. Perhabs that this happens after another MVP fragment is already committed. No guarantees.
The MVI implementation basically uses a static map with some additional tricks to ensure that it is scoped to the parent activity.
This also unifies the way a presenter is stored internally. Activity, Fragment, retaining Fragments, child Fragmetns, ViewGroups (like MvpFrameLayout) now all use this static map.

Why have you decided to abandon MVP retention mechanisms in the MVI Fragments and Activities?

Not sure what you exactly mean / referring to, but I guess you mean that there is no shouldRetainInstance() / isRetainInstance() method any more? This has now simply be moved into the corresponding MviDelegate and configureable with a constructor parameter.

Do you plan to do the same in the MVP ones?

Yes, MvpDelegates will take that responsibility similar to MviDelegate


Gzip compression

Add a flag to allow compression of assets using GZIP. Assets are compressed in memory before uploading and then the Content-Type and Content-Encoding are set so that the browser can decompress them.

Make it work with Python 3.

Updated import to support Python 3

Looks good then.


32bit linux MDB_MAP_FULL boundaries?

Howdy.
I am using node-lmdb on a 32bit machine.  Works phenomenal on 64bit!
My mapsize is set to:
const MAP_SIZE = 100 * 1024 * 1024 * 1024;
Cannot seem to get a DB larger than 700K
Any suggestion is appreciated.

So LMDB has a preprocessor constant MDB_VL32 for supporting large DBs on 32-bit machines, that we could try. I have never used it before, and if you are running into problems at only 700KB (strange limit), it is possible that something else might be wrong. Do you have any specific error message that occurs? Or does it segfault? Do you know if it stops on a certain action (possibly adding a record that increases the size)?
If you do want to try MDB_VL32, I believe you can turn it on by changing the targets/defines in binding.gyp (and recompiling) to:
"defines": ["MDB_VL32"],

Nothing happens on the OS side in syslogs or dmesg.
The error
{"message":"MDB_MAP_FULL: Environment mapsize limit reached","stack":"Error: MDB_MAP_FULL: Environment mapsize limit reached\n    at insertRecords (/home/ubuntu/harperdb/utility/lmdb/writeUtility.js:80:29)\n    at lmdbCreateRecords (/home/ubuntu/harperdb/data_layer/harperBridge/lmdbBridge/lmdbMethods/lmdbCreateRecords.js:42:29)\n    at async LMDBBridge.createRecords (/home/ubuntu/harperdb/data_layer/harperBridge/lmdbBridge/LMDBBridge.js:105:20)\n    at async insertData (/home/ubuntu/harperdb/data_layer/insert.js:128:36)\n    at async bulkLoad (/home/ubuntu/harperdb/data_layer/csvBulkLoad.js:412:30)\n    at async callBulkLoad (/home/ubuntu/harperdb/data_layer/csvBulkLoad.js:356:32)\n    at async Object.callOperationFunctionAsAwait (/home/ubuntu/harperdb/utility/OperationFunctionCaller.js:39:18)\n    at async insertChunk (/home/ubuntu/harperdb/data_layer/csvBulkLoad.js:282:38)","code":-30792,"level":"error","timestamp":"2020-08-03T22:48:39.140Z"}
However, no SWAP or Disk space is being over-utilized...
I'll try to recompile gyp with the setting you suggested and report back.
Your time and diligence are appreciated.

In that case, I doubt the issue is LMDB itself, node-lmdb is using the size_t for mapSize, which is machine-word-sized. I'll look into changing that to a fixed 64-bit type and see if that could possibly help.

OK, do you want to try kriszyp/node-lmdb#c35f6d235e1a50686dd22d2a34c13f5d5398003a and see if that works (certainly no guarantees, not sure how to set up a 32-bit environment locally for testing)?

Yesir.. will try this evening.
I also had issue configuring 32bit local.
Thanks for the quick response..
On Mon, Aug 3, 2020, 6:46 PM Kris Zyp<EMAIL_ADDRESS>wrote:

OK, do you want to try
kriszyp/node-lmdb#c35f6d235e1a50686dd22d2a34c13f5d5398003a and see if that
works (certainly no guarantees, not sure how to set up a 32-bit environment
locally for testing)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Venemo/node-lmdb/issues/172#issuecomment-668310567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGCELVDIWYWI2PZGBSFJ4MLR65K77ANCNFSM4PTZT7XA
.

--
This transmission may contain information that is proprietary,
privileged, confidential, and/or exempt from disclosure under applicable
law. If you are not the intended recipient, you are hereby notified that
any disclosure, copying, distribution, or use of the information contained
herein (including any reliance thereon) is STRICTLY PROHIBITED. If you
received this transmission in error, please immediately contact the sender
and destroy the material in its entirety, whether in electronic or hard
copy format.

Righteous!
That worked!
Thank you very much, I have spent a lot of time iterating that issue.
I certainly thought it was operator error. which it is.. no one uses 32bit,
except the people/clients that do...
What is the protocol to move this into a release, iff you believe it is
releases, worthy?
Cheers,
Z
On Mon, Aug 3, 2020 at 7:40 PM Zachary Fowler<EMAIL_ADDRESS>wrote:

Yesir.. will try this evening.
I also had issue configuring 32bit local.
Thanks for the quick response..
On Mon, Aug 3, 2020, 6:46 PM Kris Zyp<EMAIL_ADDRESS>wrote:

OK, do you want to try
kriszyp/node-lmdb#c35f6d235e1a50686dd22d2a34c13f5d5398003a and see if that
works (certainly no guarantees, not sure how to set up a 32-bit environment
locally for testing)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Venemo/node-lmdb/issues/172#issuecomment-668310567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGCELVDIWYWI2PZGBSFJ4MLR65K77ANCNFSM4PTZT7XA
.

--
Zachary Fowler
Chief Product Officer
m:<PHONE_NUMBER>
w: harperdb.io  e<EMAIL_ADDRESS>Simplicity Without Sacrifice
--
This transmission may contain information that is proprietary,
privileged, confidential, and/or exempt from disclosure under applicable
law. If you are not the intended recipient, you are hereby notified that
any disclosure, copying, distribution, or use of the information contained
herein (including any reliance thereon) is STRICTLY PROHIBITED. If you
received this transmission in error, please immediately contact the sender
and destroy the material in its entirety, whether in electronic or hard
copy format.

OK, I published a version 0.9.3, with the fix for the type. However, I changed the use of the MDB_VL32 constant to be conditional based on the use_vl32 build variable. You can build with this enabled by using npm install --use_vl32=true (and it should only apply with a 32-bit architecture). I believe you can set this command in you scripts/install in your package.json so your own package builds with that variable enabled. Let me know if there are any issues with that.

Amazing!
Works perfectly!
Your time and diligence are appreciated!
Cheers!


Route planner - show entire route

Center and zoom until the whole route fits the screen

Implemented  in v3.0.0-alpha-19.
Added button to fit planned route on map.
A dialog is shown when there is no planned route yet.


quickemu: 4.9.4-unstable-2024-05-28 -> 4.9.5

Description of changes
Fixes #322484, also adds the changelog to the package file.
Changelog: https://github.com/quickemu-project/quickemu/releases/tag/4.9.5

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Updating following both of your suggestions!

What's the hold up?