Come up with an alternative for helix potential or implement new force in OpenMM

I'm looking at using AWSEM. I'm far more familiar with OpenMM than LAMMPS, but the missing helix term is a bit confusing. Is the OpenMM version usable and correct, or should I go with LAMMPS?

Unfortunately, the alpha-helical hydrogen-bonding potential lies just outside of what is currently possible to implement in OpenMM's custom forces framework because it is both density-dependent and involves the interaction of three atoms in the pairwise part of the potential (to ensure that both the distance and the angle are appropriate for a hydrogen bond). Fortunately, the alpha-helical hydrogen-bonding potential is not the only potential in AWSEM that contains helical signals. For most of its history, the AWSEM family of potentials relied on the associative memory potential (also sometimes called the fragment memory potential) to capture local-in-sequence signals. The alpha-helical hydrogen-bonding potential was introduced as a possible means of replacing the (non-transferrable) associative memory potential with a fully transferrable potential for alpha-helical proteins. The paper that introduced the potential showed that the alpha-helical hydrogen bonding potential by itself is not always a good substitute for the associative memory potential. In short, for most purposes, it should be fine to use OpenAWSEM with the associative memory potential even if you are interested in simulating alpha-helical proteins. If you are familiar with OpenMM and not very familiar with LAMMPS, then I would say that OpenAWSEM is the better choice, especially if you have access to GPUs and are interested in large or very long simulations. If you are familiar with OpenMM's custom forces framework, you could even implement your own (non-density-dependent) alpha-helical hydrogen bonding potential. Let me know if you disagree with anything that I said @luwei0917 or @cabb99, and thanks for your interest @agrossfield.

Ok, that’s reassuring. The system I’m interested in isn’t particularly helical, so I’ll take a look at this to start.
Cheers,
Alan
From: Nicholas Schafer<EMAIL_ADDRESS>Reply-To: npschafer/openawsem<EMAIL_ADDRESS>Date: Monday, September 21, 2020 at 10:19 AM
To: npschafer/openawsem<EMAIL_ADDRESS>Cc: "Grossfield, Alan"<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [EXT] Re: [npschafer/openawsem] Come up with an alternative for helix potential or implement new force in OpenMM (#10)
Unfortunately, the alpha-helical hydrogen-bonding potential lies just outside of what is currently possible to implement in OpenMM's custom forces framework because it is both density-dependent and involves the interaction of three atoms in the pairwise part of the potential (to ensure that both the distance and the angle are appropriate for a hydrogen bond). Fortunately, the alpha-helical hydrogen-bonding potential is not the only potential in AWSEM that contains helical signals. For most of its history, the AWSEM family of potentials relied on the associative memory potential (also sometimes called the fragment memory potential) to capture local-in-sequence signals. The alpha-helical hydrogen-bonding potential was introduced as a possible means of replacing the (non-transferrable) associative memory potential with a fully transferrable potential for alpha-helical proteins. The paper that introduced the potentialhttps://urldefense.proofpoint.com/v2/url?u=https-3A__www.sciencedirect.com_science_article_pii_S1046202310001507&d=DwMFaQ&c=4sF48jRmVAe_CH-k9mXYXEGfSnM3bY53YSKuLUQRxhA&r=49qnaP-kgQR_zujl5kbj_PmvQeXyz1NAoiLoIzsc27zuRX32UDM2oX8NQCaAsZzH&m=-_Wl-eMy8ix6rWHWrJRQaQr7uAsmbYw-zJsng9DAe_0&s=gtrd4dEMSfqpN1pD9cQk5009K9KRJUsNbO3xg9cXI3s&e= showed that the alpha-helical hydrogen bonding potential by itself is not always a good substitute for the associative memory potential. In short, for most purposes, it should be fine to use OpenAWSEM with the associative memory potential even if you are interested in simulating alpha-helical proteins. If you are familiar with OpenMM and not very familiar with LAMMPS, then I would say that OpenAWSEM is the better choice, especially if you have access to GPUs and are interested in large or very long simulations. If you are familiar with OpenMM's custom forces framework, you could even implement your own (non-density-dependent) alpha-helical hydrogen bonding potential. Let me know if you disagree with anything that I said @luwei0917https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_luwei0917&d=DwMFaQ&c=4sF48jRmVAe_CH-k9mXYXEGfSnM3bY53YSKuLUQRxhA&r=49qnaP-kgQR_zujl5kbj_PmvQeXyz1NAoiLoIzsc27zuRX32UDM2oX8NQCaAsZzH&m=-_Wl-eMy8ix6rWHWrJRQaQr7uAsmbYw-zJsng9DAe_0&s=6T0yW-A4hP1BPaK15WpEiL9gWXG1jIap3-SEnwwJqOI&e= or @cabb99https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cabb99&d=DwMFaQ&c=4sF48jRmVAe_CH-k9mXYXEGfSnM3bY53YSKuLUQRxhA&r=49qnaP-kgQR_zujl5kbj_PmvQeXyz1NAoiLoIzsc27zuRX32UDM2oX8NQCaAsZzH&m=-_Wl-eMy8ix6rWHWrJRQaQr7uAsmbYw-zJsng9DAe_0&s=jb_7l2IIAqwa0dmDjrkK_hUWDiM30cSTyUSjNFrsUf4&e=, and thanks for your interest @agrossfieldhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_agrossfield&d=DwMFaQ&c=4sF48jRmVAe_CH-k9mXYXEGfSnM3bY53YSKuLUQRxhA&r=49qnaP-kgQR_zujl5kbj_PmvQeXyz1NAoiLoIzsc27zuRX32UDM2oX8NQCaAsZzH&m=-_Wl-eMy8ix6rWHWrJRQaQr7uAsmbYw-zJsng9DAe_0&s=nXC548JyenXvjCkHvuzKEJB6IDBClxt5MaG5B58rIpc&e=.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_npschafer_openawsem_issues_10-23issuecomment-2D696144965&d=DwMFaQ&c=4sF48jRmVAe_CH-k9mXYXEGfSnM3bY53YSKuLUQRxhA&r=49qnaP-kgQR_zujl5kbj_PmvQeXyz1NAoiLoIzsc27zuRX32UDM2oX8NQCaAsZzH&m=-_Wl-eMy8ix6rWHWrJRQaQr7uAsmbYw-zJsng9DAe_0&s=BhbQMibXV2CxZ52rhkJJDt7NJIZDXwTlE0yoACp3RgE&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADH754RBUJV2VQJ3SS4AZH3SG5OFZANCNFSM4DX4H67Q&d=DwMFaQ&c=4sF48jRmVAe_CH-k9mXYXEGfSnM3bY53YSKuLUQRxhA&r=49qnaP-kgQR_zujl5kbj_PmvQeXyz1NAoiLoIzsc27zuRX32UDM2oX8NQCaAsZzH&m=-_Wl-eMy8ix6rWHWrJRQaQr7uAsmbYw-zJsng9DAe_0&s=OLHRPTPSyM9UKFUtGUoi5OrDA-3W65pptobGr-k0ANY&e=.


Initial the Authorization result APIs

Travis failed because of PMD. Going to suppress them until we implement the method.


chore: parameterize Makefile and Dockerfile

r? @m8ttyB
Closes #24

Also you can delete the matt_tmp branch.  this is a copy of that.

r+


CASMTRIAGE-6182: Install latest RPMs from tarball onto m001 after redeploy

Description
Modify the install procedure so that the latest RPMs from the tarball are saved off and installed on m001 after redeploy.

Checklist

[X] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[X] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[X] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.4


[Bug Report]: Azure Sql Database deployment breaks when Db name is longer than 25 characters

Describe the bug
Since the addition of backupShortTermRetentionPolicies and backupLongTermRetentionPolicies in Sql Database module in PR https://github.com/Azure/ResourceModules/pull/2802, a deployment will fail if the Sql Database name is longer than 25 characters because the resulting module name would exceed the maximum allowed one (64 chars).
A potential fix would be adding a take() function as to shorten the name when building the module name:

from '${uniqueString(deployment().name, location)}-${name}-shortTermBackupRetention' to '${uniqueString(deployment().name, location)}-${take(name,25)}-shortTermBackupRetention'
from name: '${uniqueString(deployment().name, location)}-${name}-longTermBackupRetention' to name: '${uniqueString(deployment().name, location)}-${take(name,26)}-longTermBackupRetention'

To reproduce
Deploy a Sql Database whose name is longer than 25 characters, with any set of parameters. The deployment will fail
Code snippet
No response
Relevant log output
the provided deployment name '[.......]' has a length of '65' which exceeds the maximum length of '64'. Please see https://aka.ms/arm-deploy for usage details.

Needs to be investigated on if the same issue impacts other resources as well.
The same has been implemented in:

websites/slots
sql/databases
cdn/profiles/endpoints

In that case a possible workaround would be to update the ${name} part with a deterministic and fixed length name such as the resourcetype

We face the same problem. Not critical, but would be great if this gets fixed


feat(control): Mobile Ads (Banner and Interstitial)

Closes #286
Test Code:
import flet as ft
import flet.ads as ads

def main(page: ft.Page):
    page.horizontal_alignment = ft.CrossAxisAlignment.CENTER

    id_interstitial = (
        "ca-app-pub-3940256099942544/1033173712"
        if page.platform == ft.PagePlatform.ANDROID
        else "ca-app-pub-3940256099942544/4411468910"
    )

    id_banner = (
        "ca-app-pub-3940256099942544/6300978111"
        if page.platform == ft.PagePlatform.ANDROID
        else "ca-app-pub-3940256099942544/2934735716"
    )

    def handle_interstitial_close(e):
        nonlocal iad
        print("InterstitialAd closed")
        page.overlay.remove(e.control)
        page.overlay.append(iad := get_new_interstitial_ad())
        page.update()

    def get_new_interstitial_ad():
        return ads.InterstitialAd(
            unit_id=id_interstitial,
            on_load=lambda e: print("InterstitialAd loaded"),
            on_error=lambda e: print("InterstitialAd error", e.data),
            on_open=lambda e: print("InterstitialAd opened"),
            on_close=handle_interstitial_close,
            on_impression=lambda e: print("InterstitialAd impression"),
            on_click=lambda e: print("InterstitialAd clicked"),
        )

    def display_new_banner_ad():
        page.add(
            ft.Container(
                content=ads.BannerAd(
                    unit_id=id_banner,
                    on_click=lambda e: print("BannerAd clicked"),
                    on_load=lambda e: print("BannerAd loaded"),
                    on_error=lambda e: print("BannerAd error", e.data),
                    on_open=lambda e: print("BannerAd opened"),
                    on_close=lambda e: print("BannerAd closed"),
                    on_impression=lambda e: print("BannerAd impression"),
                    on_will_dismiss=lambda e: print("BannerAd will dismiss"),
                ),
                width=320,
                height=50,
                bgcolor=ft.colors.TRANSPARENT,
            )
        )

    page.overlay.append(iad := get_new_interstitial_ad())
    page.appbar = ft.AppBar(
        adaptive=True,
        title=ft.Text("Mobile Ads Playground"),
        bgcolor=ft.colors.LIGHT_BLUE_300,
    )
    page.add(
        ft.OutlinedButton("Show InterstitialAd", on_click=lambda e: iad.show()),
        ft.OutlinedButton("Show BannerAd", on_click=lambda e: display_new_banner_ad()),
    )

ft.app(main)

Summary by Sourcery
This pull request adds support for mobile ads (Banner and Interstitial) to the Flet framework. It includes new classes for managing these ads, updates to the main Dart file for initialization, and modifications to the pubspec.yaml to include the new package. Initial documentation for the new controls is also provided.

New Features:

Introduced support for mobile ads, including Banner and Interstitial ads, in the Flet framework.
Added new classes for handling mobile ads: BannerAd, InterstitialAd, and NativeAd with associated event handlers for load, error, open, close, impression, click, and will dismiss events.

Enhancements:

Updated the main Dart file to initialize the new mobile ads package and ensure it is properly set up.
Modified the pubspec.yaml to include the new flet_mobile_ads package.

Documentation:

Added initial documentation for the new mobile ads controls in the README.md file of the flet_mobile_ads package.

Can you add (Rewarded interstitial - Interstitial Video - App Open)

Waiting on https://github.com/flet-dev/flet/issues/3345 to finalize
(the unit ID for the ads is passed as property, but however needs to be passed to iOS .plist and Android .xml)

can you add some documentation for native ads

.

Waiting on #3345 to finalize (the unit ID for the ads is passed as property, but however needs to be added to iOS .plist and Android .xml equally)

please can you add native ads in documentation?

I faced some issues while trying to add Native ads (forgot which one though).
It's files are present in this PR, but the Control can't be accessed nor used as its not fully ready-for-use.
For a start, we will have just Banner and Interstitial ads. Native might come up later on...

@sourcery-ai review

i test baner you ad code . and why error in app
"unknow control : banner_ad "
i test in android

Using the Flet mobile app? Or you packaged as apk?

Using the Flet mobile app? Or you packaged as apk?

Flet mobile . Yeah it shouldn't work . But is there a way to debug directly into android . Like . Flutter run android . That would be useful. When the development


Code signing for MacOS binary

If this affects the version bundled with the VSCode extension, we'll need to do this sooner. otherwise, it can be closer to launch.

Since this doesn't affect the extension and only the CLI I'm going to break this out of v1.2.0


Hyperparameter tuning

Unfortunately the paper doesn't talk at all about the hyperparameter tuning. I was hoping you could share some of your experience. In particular, I'm interested to hear what parameters were worth tuning.
I'm in the process of using the code for a python code dataset that is an order of magnitude smaller than the datasets reported in the paper. The performance that I get so far is about half of what you got (but I'm not done tuning yet). So far it seems that smaller learning rates work better.
Anything else that you played with and it proved beneficial? Thank you!

One parameter that I couldn't find in the paper is the number of layers in the GGNN. What values did you use?

Apologize for the delay.
The performance of the model in code datasets is highly dependent on the quality of the dataset. As reported in the paper (and in the technical report by one of the co-authors), if there is duplication in the dataset this will impact performance, so without knowing the dataset it is hard to know.
However I can tell you that GGNN steps used for code was [2, 2, 2, 2] since the strutucture is more relevant in code than in natural language.

I'm fairly confident there is no duplication in the dataset by construction. I'll keep you posted with what I find. Shall I understand that there were 4 layers and the number of steps were 2? I'm not sure what [2, 2, 2, 2] means.

It means 4 layers with two timesteps each.
Ioana Baldini<EMAIL_ADDRESS>escreveu no dia segunda, 6/05/2019
à(s) 15:19:

I'm fairly confident there is no duplication in the dataset by
construction. I'll keep you posted with what I find. Shall I understand
that there were 4 layers and the number of steps were 2? I'm not sure what [2,
2, 2, 2] means.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/CoderPat/structured-neural-summarization/issues/17#issuecomment-489638044,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACV2WM6BDLB7SRQBZSQXDYTPUA47FANCNFSM4HIGD7IA
.

Makes sense. (your portuguese notifications look cool :) )


parseEvent 'round_end' returning undefined reason and winner

Hello, I was testing your example for finding clutches in a demo, and I bumped on the following issue:
Running
let round_ends = parseEvent(pathToDemo, 'round_end')
Returns
round_ends: [
  {
    event_name: 'round_end',
    reason: null,
    round: 1,
    tick: 0,
    winner: null
  },
  {
    event_name: 'round_end',
    reason: 'bomb_exploded',
    round: 2,
    tick: 9451,
    winner: 'T'
  },

The reason and winner for the first round are missing, but they appear incorrectly in the second round instead.
I encountered this issue on all 3 maps from the Copenhagen Major's final.
Awesome library by the way, thanks for putting it together.

As far as I understand, this happens for several reasons:

Restart of the round (There can be many empty values in round ended and not only in 1 round)
I also found that if a knife round is played, then it is also taken into account in this dataframe

I write in python, so I don't know how to fix it in js. In Python it looks like this:
df = parser.parse_event("round_end", other=["total_rounds_played", 'round_win_status'])
df = df[df.winner.isna() == False].drop_duplicates(subset='total_rounds_played', keep='last').reset_index()

Principle: first you delete empty values, and then duplicates (according to the total_rounds_played parameter), where you leave only the last value (if total_rounds_played = 1 more than 1 time, then you need to leave only the last one, since it is correctly relevant)
If something is unclear, then ask GPT to rewrite the code in js and figure it out


Segment splitting incorrect

According to https://www.hbci-zka.de/dokumente/spezifikation_deutsch/fintsv3/FinTS_3.0_Formals_2017-10-06_final_version.pdf (G. Data Dictionary -> Segmentkennung), the splitting in the constructor of Response.php needs to be something like this:
$this->segments = preg_split("/'+(?=[A-Z0-9]{1,6}:\d{1,3}:\d{1,3}(:\d{1,3})?)/", $rawResponse);

The old regexp splitted on two subsequent single quotes in transaction texts (''), which is definitely wrong.
Even better would be to filter out binary content ('@@'), see documentation, which could still contain segment headers (i.e. 'A:1:2) and break stuff.

Ty @roben ! Safed my day!
The owner of this lib is still offline? No answer after buy pro version! Frustrated...


4664: Moved ImageFragment to ViewBinding

Fixes #4664
What changes did you make and why?

Issue: As per the information provided and work request on the ticket above, ImageFragment.kt is currently using Kotlin Synthetic which creates auto-generated class, and has been alread deprecated.
Solution: Hence migration was done by replacing kotlin-synthetic with viewbinding, which is always null safe, type-safe and supports both Java and Kotlin.

NB: During migration a redundant semicolon was removed.

@dbrant Requesting to review this PR

Thanks @bosankus and sorry for the long wait!


Achieve GDAL stability on all platforms

Document process for achieving stable install of GDAL on Windows/Linux.  Incorporate into POM if necessary.

Depends on #63 (putting jar libraries shaded into final jar/exe)

Attempting OSGeo4W (32bit) installer, which has packages that support gdal-java bindings as well as a swig package

OSGeo4W 64-bit has no pre-built gdal dlls or jar.  GDAL was compiled on a 64 bit machine using MSVS 2013 Express Edition with SWIG bindings to Java.
Adding a lib folder to RGISuite that will contain both gdal.jar and all x64 gdal dlls necessary for running the application.  Also, the gdal data folder will be added to the classpath.

RGISuite/lib must be put into the windows path variable and eclipse must be restarted to take effect.

Adding documentation for creating a sane build/run environment with GDAL in the SWAGD wiki area: https://github.com/GitHubRGI/swagd/wiki/Creating-A-Sane-GDAL-Environment-(Windows-64-bit)

Added documentation to the wiki for a build/run environment on Linux. https://github.com/GitHubRGI/swagd/wiki/Creating-A-Sane-GDAL-Environment-(Linux-x64)


Adjust table inset behavior to the same as container's (#1979)

Resolves #1979 .

I wonder why I didn't do this in the first place... probably an oversight.

Just for completeness, can you also add a table in your tests which uses all 4 inset configuration keys?
Also, I believe it might be a good idea to add an example to the inset parameter's documentation (the docstring above the inset field), with two tables: one with a simple inset parameter (e.g. 10pt), and another the 4 inset config keys.

@PgBiel Parameters can only have one example or at least both things would need to be part of one example. But that's one very long example.

@PgBiel Parameters can only have one example or at least both things would need to be part of one example. But that's one very long example.

Yeah I think it's fine to have a single example with both. They can be very short tables.
For instance:
#table(inset: 10pt)[Info 1][Info 2]

#table(inset: (left: 4pt, top: 10pt, bottom: 20pt, right: 2pt)[Cell 1][Cell 2]

#table(
  inset: 10pt,
  [Info 1],
  [Info 2],
)

#table(
  inset: (
    left: 4pt,
    top: 10pt,
    bottom: 20pt,
    right: 2pt,
  ),
  [Cell 1],
  [Cell 2],
)

will likely render more nicely because it's side by side. the left side will probably be a bit higher. whereas wide input that produces a high output will not look good.

Thanks!


chore: update to @podman-desktop/ui-svelte 1.14

Is your enhancement related to a problem? Please describe
We are using version 1.12
https://github.com/containers/podman-desktop-extension-ai-lab/blob/79d1543e3f7aaeed7871fa75bf50e25b99befc78/packages/frontend/package.json#L19
Newer version improve the components, however there are some issue with the dependabot because svelte check is failing.
Describe the solution you'd like
Fix the svelte check errors
Describe alternatives you've considered
No response
Additional context
No response

blocked by https://github.com/containers/podman-desktop-extension-ai-lab/issues/1897

blocked by #1897

Yes I opened https://github.com/containers/podman-desktop-extension-ai-lab/pull/1994


attribute lookup CalibData on pykitti.odometry failed

Hi,when I set up the dataset,runing the order
python train.py --config configs/train/monorec/monorec_depth.json --options stereo
"enumerate(self.data_loader)"    will alert pickle.PicklingError: Can't pickle <class 'pykitti.odometry.CalibData'>: attribute lookup CalibData on pykitti.odometry failed

Had the same problem, +1

If you run it with Windows, set "numworks" = 0.Because numworks means multiprogress data,Windows forbids it
------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2022年4月10日(星期天) 晚上9:01
收件人: @.>;
抄送: @.>; "State @.>;
主题: Re: [Brummi/MonoRec]  attribute lookup CalibData on pykitti.odometry failed (Issue #29)
Had the same problem, +1
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.***>

Hi, thank you for your reply, it is greatly useful for me and i solve this issue. But now,when i try to run train.py  i meet the bug "TypeError: 'tuple' object is not callable", and this is my kitti dataset, could you help me solve this issue, thank you sincerely.
------------------ 原始邮件 ------------------
发件人:                                                                                "Brummi/MonoRec"                                                                                @.>;
发送时间: 2022年4月11日(星期一) 上午7:46
@.>;
<EMAIL_ADDRESS>主题: Re: [Brummi/MonoRec]  attribute lookup CalibData on pykitti.odometry failed (Issue #29)
If you run it with Windows, set "numworks" = 0.Because numworks means multiprogress data,Windows forbids it
------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2022年4月10日(星期天) 晚上9:01
收件人: @.>;
抄送: @.>; "State @.>;
主题: Re: [Brummi/MonoRec]  attribute lookup CalibData on pykitti.odometry failed (Issue #29)
Had the same problem, +1
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.>


fatal error - cygheap base mismatch detected - 0x13A1410/0x13D1410

I was trying to install poppe using this command npm install popper --save but I got a bunch of errors like this error message:
      3 [main] sh (28644) C:\Program Files\Git\usr\bin\sh.exe: *** fatal error - cygheap base mismatch detected - 0x13A1410/0x13D1410.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version.  The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.  Rebooting is also suggested if you
are unable to find another cygwin DLL.
      1 [main] sh 956 fork: child -1 - forked process 28644 died unexpectedly, retry 0, exit code 0xC0000142, errno 11
      2 [main] sh (24104) C:\Program Files\Git\usr\bin\sh.exe: *** fatal error - cygheap base mismatch detected - 0x13A1410/0x11B1410.

What is the problem and how can I fix?

As this is clearly a problem with cygwin/your particular command line setup, and not bootstrap itself, i'd recommend asking on stackoverflow or similar. see https://github.com/twbs/bootstrap/blob/master/.github/CONTRIBUTING.md#using-the-issue-tracker


CI: Replace set-output use in repo-defined actions

We see the following annotation in multiple workflows:

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

set-output is used in:

.github/actions/annotate
.github/actions/issue_closer
.github/actions/simplecov-report

Let's update the code to use the "Environment Files" approach.

This may partially resolve https://github.com/newrelic/newrelic-ruby-agent/issues/2211


Snap crashes Gnome3 session on Ubuntu 17.10

My Setup

Operating System: Ubuntu 17.10 (kernel 4.15.2-041502-generic)

App Version: 2.7.0 (latest version available as a snap as default when installing through Ubuntu at time of testing).

[x ] I have tested with the latest version

[x ] I can simulate the issue easily

Description
To reproduce, I just need to open the app on my system.
Current Behavior
The entire Gnome 3 shell (Wayland) session instantly crashes (which obviously closes all running desktop applications and throws back to the login).
Note, this is an issue specific to the rocketchat-desktop SNAP package. Installing via the .deb package works fine (although I note the .deb is version 2.10.2).
Expected Behavior
The app should run without crashing the session.

This happens to me, too. Both the spotify snap and an electron app that I made locally crash Gnome shell. I see a segfault in the system logs when it happens:
Feb 15 09:33:38 raven spotify_spotify.desktop[26607]: Gtk-Message: Failed to load module "canberra-gtk-module"
Feb 15 09:33:39 raven PackageKit: resolve transaction /112_bebcacce from uid 1000 finished with success after 403ms
Feb 15 09:33:39 raven gnome-software[26326]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=spo on plugin=snap on a
pps system/package/ubuntu-artful-universe/desktop/blocks-of-the-undead.desktop/*,system/package/ubuntu-artful-universe/desktop/tuxfootball.desktop/*,system/packag
e/ubuntu-artful-universe/desktop/etw.desktop/*,system/package/ubuntu-artful-universe/desktop/Xdx.desktop/*,system/package/ubuntu-artful-universe/desktop/gtranscri
be.desktop/*,system/snap/Snap Store/desktop/vsslagent/*,system/snap/Snap Store/desktop/tizonia/*,system/snap/Snap Store/desktop/rockscissorspaperlizardspock-snap/
*,system/snap/Snap Store/desktop/spotify/* took 2958ms
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE)
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) Backtrace:
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 0: /usr/bin/Xwayland (xorg_backtrace+0x4d) [0x561556b0843d]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 1: /usr/bin/Xwayland (0x561556960000+0x1ac1d9) [0x561556b0c1d9]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f6a896f1000+0x13150) [0x7f6a89704150]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7f6a81749000+0x22fcb6) [0x7f6a81978cb6]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7f6a81749000+0x19a829) [0x7f6a818e3829]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7f6a81749000+0x12e272) [0x7f6a81877272]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7f6a81749000+0x12e2ae) [0x7f6a818772ae]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7f6a81749000+0x12e311) [0x7f6a81877311]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7f6a81749000+0x98152) [0x7f6a817e1152]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7f6a81749000+0x23c63b) [0x7f6a8198563b]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7f6a81749000+0x3b3afd) [0x7f6a81afcafd]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 11: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7f6a81749000+0x3b2bd3) [0x7f6a81afbbd3]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 12: /usr/bin/Xwayland (0x561556960000+0xc88f9) [0x561556a288f9]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 13: /usr/bin/Xwayland (0x561556960000+0xc78e5) [0x561556a278e5]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 14: /usr/bin/Xwayland (0x561556960000+0x196772) [0x561556af6772]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 15: /usr/bin/Xwayland (0x561556960000+0xcc307) [0x561556a2c307]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 16: /usr/bin/Xwayland (0x561556960000+0xc7bac) [0x561556a27bac]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 17: /usr/bin/Xwayland (0x561556960000+0x171c48) [0x561556ad1c48]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 18: /usr/bin/Xwayland (0x561556960000+0x175c90) [0x561556ad5c90]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7f6a893321c1]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) 20: /usr/bin/Xwayland (_start+0x2a) [0x56155699aa9a]
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE)
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) Segmentation fault at address 0x70
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE)
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: Fatal server error:
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Feb 15 09:33:40 raven org.gnome.Shell.desktop[26025]: (EE)

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!


[decompiler] clean up vector detection and add vector float product detection

Pull Request Test Coverage Report for Build 976951366

81 of 172 (47.09%)  changed or added relevant lines in 6 files are covered.
109 unchanged lines in 8 files lost coverage.
Overall coverage decreased (-0.3%) to 69.262%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

decompiler/IR2/AtomicOpTypeAnalysis.cpp
2
4
50.0%

decompiler/analysis/insert_lets.cpp
10
12
83.33%

decompiler/IR2/Form.cpp
2
6
33.33%

decompiler/IR2/AtomicOp.cpp
11
17
64.71%

decompiler/IR2/FormExpressionAnalysis.cpp
14
35
40.0%

decompiler/analysis/atomic_op_builder.cpp
42
98
42.86%

Files with Coverage Reduction
New Missed Lines
%

decompiler/IR2/AtomicOpTypeAnalysis.cpp
1
76.68%

decompiler/IR2/AtomicOp.cpp
3
60.2%

decompiler/IR2/FormStack.cpp
3
78.09%

decompiler/analysis/atomic_op_builder.cpp
4
86.44%

decompiler/IR2/Form.h
7
93.49%

decompiler/IR2/Form.cpp
16
73.77%

decompiler/IR2/AtomicOpForm.cpp
33
67.2%

decompiler/IR2/FormExpressionAnalysis.cpp
42
77.18%

Totals

Change from base Build 976551951:
-0.3%

Covered Lines:
37004

Relevant Lines:
53426

💛  - Coveralls


refactor: streamline & update rust dependencies

Partially satisfies https://github.com/near/devx/issues/157
Following the advice given here to ensure there are no different versions of common libraries
Formatting changes come from the auto run of rustfmt in my editor

@evgenykuzyakov tests currently failing with:
test tests::test_fail_request_transfer_already_used ... FAILED
test tests::test_request_transfer_ok ... FAILED

failures:

---- tests::test_fail_request_transfer_already_used stdout ----
thread 'tests::test_fail_request_transfer_already_used' panicked at 'The given hash is already used for transfer', src/lib.rs:98:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- tests::test_request_transfer_ok stdout ----
Salt is 58
thread 'tests::test_request_transfer_ok' panicked at 'The given hash is already used for transfer', src/lib.rs:98:9

Pointers on how to fix?

Also replace StrPublicKey with  near_sdk::json_types::Base58PublicKey

I was able to get rid of the whole types.rs file after doing this 🎉


Access to Bluetooth devices?

Hi,
Firstly, let me thank you for the great utility you have produced.
I have an Android app that accesses hardware via a Bluetooth socket. I have tried it on a chromebook using your software and, as far as I can tell, everything works except for the Bluetooth. My app reports that no Bluetooth devices are present. Is this a limitation of the App Runtime (from Google) or the conversion/packaging process?
Cheers,
Mark

Hello there, I have the same issue. Have you found any solution?


Django 3.0 fixes

Hopefully get tests passing on Django master.
Incorporates #5488

Merged in via https://github.com/wagtail/wagtail/commit/dc780c5bb15fb0ae3c039d977e8a172edb5437ae
As mentioned in above discussion, the subtle differences in the test cases are due to different aesthetic formatting in some Django messages for 3.0


Crash on orientation change

Fixes NullPointerException on orientation change

Added it manually. Thanks.

Thank you for your great work.
On Mon, Feb 20, 2012 at 9:50 PM, Jake Wharton <
<EMAIL_ADDRESS>
wrote:

Added it manually. Thanks.

Reply to this email directly or view it on GitHub:
https://github.com/JakeWharton/ActionBarSherlock/pull/294#issuecomment-4061466


[FLINK-30166][Connector/FileSystem] Refactor tests that use the deprecated StreamingFileSink instead of FileSink

Same as https://github.com/apache/flink/pull/21371, except for c4dc109cba59f406f2f1a38ed4e3fdadb62d4970 which now also removes the StreamingFileSink from the E2E tests

@MartijnVisser keep in mind that I reverted all the commits related to FLINK-30166. PR #21371 changed 13 files. This PR only changes 3. I guess, you have to cherry-pick the other commits once more? :thinking:

@MartijnVisser keep in mind that I reverted all the commits related to FLINK-30166. PR #21371 changed 13 files. This PR only changes 3. I guess, you have to cherry-pick the other commits once more? 🤔

Yeah I forgot to revert your reversion ;) I've done that now, while making the commit message a bit more clear 😅

@flinkbot run azure

What's the plan with the StreamingFileSink? Are there follow-up tickets which are not linked with FLINK-30166? I'm just wondering because we're removing tests here for a class that's still present in the codebase. Why don't we remove everything at once?

Why don't we remove everything at once?

That was the original idea, but I chatted offline with @JingsongLi and there is work to be done on FileSystemTableSink in order to be able to completely remove StreamingFileSink. I've created https://issues.apache.org/jira/browse/FLINK-30627 as a follow-up ticket.

Should we get rid of those as well?

We can't yet due to https://issues.apache.org/jira/browse/FLINK-30627

Sorry for being picky on that one. But even with knowing these details, it becomes kind of hard for me to review this PR. There are still code location where I have questions but which are hard to mention in this PR if they are actually not touched as code change. Why do we need to do the cleanup before the refactoring? Can't we wait for the refactoring and clean up everything properly afterwards? Or do we gain anything from cleaning up code partially which I'm not aware of?
Alternatively, if you really want to push for it, it might be more reasonable to ask @JingsongLi for a review or someone more related to whether the partial cleanup is to his liking. WDYT?

Alternatively, if you really want to push for it, it might be more reasonable to ask @JingsongLi for a review or someone more related to whether the partial cleanup is to his liking. WDYT?

The original PR (https://github.com/apache/flink/pull/21371) was reviewed and approved by @gaoyunhaii so it might make more sense to ask him :)

@gaoyunhaii Can you take one more look? You've already reviewed the original PR, which missed one thing that is now addressed in this PR.

Very sorry for missing the message, I’lol have a look soon.

Very sorry for missing the message, I’ll have a look soon.

Thank you!


There should be a public API that allows to render in a hash.

At the moment it seems render returns only a String since it uses to_json. There should be a as_json equivalent publicly accessible.
https://github.com/jsonapi-rb/jsonapi-serializable/blob/master/lib/jsonapi/serializable/renderer.rb#L22

Hi @vasilakisfil – you are right. I've had that under my radar for a while but somehow forgot about it. As jsonapi-serializable does not depend on ActiveSupport, there would be no #as_json, but the returned hash would be what one would expect from #as_json.
So, basically it's just a matter of removing .to_json here and here. Feel free to open a PR if you have the file open in your text editor already, otherwise I'll do it myself over the weekend.

@beauby was this merged into rubygems version?


Add option to clear all requests from the log

Feature Request
It should be possible to clear all the requests on the monitor screen to make it easier to debug requests from a certain point.

Fixed by 506cd23769f9ef02b4b299abd0a9fd426b0fc628


Empty View not working properly

When we add any Item and then delete it causing it empty list ,then  it doesn't show default empty view text Click Add button to start adding items.

Fixed


flaky test(s): TestSearchCmdOptions, TestSearchOnCentralRegistry, TestSearchWithLimit

One issue because they all started failing at once, and always seem to fail together.
Seen failing on master: https://jenkins.dockerproject.org/job/Docker Master/label=ubuntu-1404 && aufs/6834/consoleFull
 FAIL: docker_cli_search_test.go:47: DockerSuite.TestSearchCmdOptions

 docker_cli_search_test.go:72:
     c.Assert(outSearchCmdOfficialSlice, checker.HasLen, 3) // 1 header, 1 line, 1 carriage return
 ... obtained []string = []string{"NAME      DESCRIPTION   STARS     OFFICIAL   AUTOMATED", ""}
 ... n int = 3

 ----------------------------------------------------------------------
 FAIL: docker_cli_search_test.go:12: DockerSuite.TestSearchOnCentralRegistry

 docker_cli_search_test.go:16:
     c.Assert(out, checker.Contains, "Busybox base image.", check.Commentf("couldn't find any repository named (or containing) 'Busybox base image.'"))
 ... obtained string = "NAME      DESCRIPTION   STARS     OFFICIAL   AUTOMATED\n"
 ... substring string = "Busybox base image."
 ... couldn't find any repository named (or containing) 'Busybox base image.'

 ----------------------------------------------------------------------
 FAIL: docker_cli_search_test.go:103: DockerSuite.TestSearchWithLimit

 docker_cli_search_test.go:110:
     c.Assert(outSlice, checker.HasLen, limit+2) // 1 header, 1 carriage return
 ... obtained []string = []string{"NAME      DESCRIPTION   STARS     OFFICIAL   AUTOMATED", ""}
 ... n int = 12

 ----------------------------------------------------------------------

search on hub was down, it's back to normal now.
Thanks for the report.


Will added Conan/VCPKG Support ?

Will added Conan/VCPKG Support ?

Good question. I'm not sure what's involved. I just skimmed a page that explained how to use Conan for building, but that particular page didn't explain how to add support to make a package conan-able. I'd be more than happy to accept pull requests for it.

If I have time I'll pack it for conan


OSD-15495 - Add method to check if the container is already running

What type of PR is this?
bug
What this PR does / Why we need it?
We need this PR to fix console container creation issues when console is already running.
Which Jira/Github issue(s) does this PR fix?
OSD-15495
Pre-checks (if applicable)

[x] Validated the changes in a cluster

Codecov Report

Merging #53 (b35c24d) into main (9e6721c) will decrease coverage by 0.75%.
The diff coverage is 0.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #53      +/-   ##
==========================================
- Coverage   42.89%   42.14%   -0.75%
==========================================
  Files          37       37
  Lines        2138     2176      +38
==========================================
  Hits          917      917
- Misses       1078     1116      +38
  Partials      143      143

Impacted Files
Coverage Δ

cmd/ocm-backplane/console/console.go
11.76% <0.00%> (-1.41%)
:arrow_down:

/lgtm
/approve


Add docs on symbols and source link

https://www.symbolsource.org/Public/Wiki/Publishing

https://github.com/ctaggart/SourceLink#sourcelink
https://github.com/aspnet/BuildTools/pull/407

becoming a non-issue in 2.3


[Bug] the answers are mixed up with Markdown syntax and formulas

📦 Deployment Method
Other
📌 Version

💻 Operating System
Windows
📌 System Version
10
🌐 Browser
Chrome
📌 Browser Version

🐛 Bug Description
Recently, in the desktop program Next Chat, messages from GPT have been coming with markdown errors and formulas mixed in with the text. This has never happened before.
📷 Recurrence Steps
ввожу сообщение в Next Chat и получаю ответ со смешанным синтаксисом markdown and formule
🚦 Expected Behavior
I want the response from ChatGPT not to violate Markdown syntax and to be executed correctly.To do this, it is important to follow the syntax and formatting rules of the Markdown language.
📝 Additional Information
No response

example


Uncaught TypeError: Cannot read property 'isError' of undefined

Packages -> TFS -> Get Latest Version
tf.exe Version: 10.0.30319.1
tfpt.exe Version: 2010
Atom Version: 1.7.2
System: Microsoft Windows 7 Enterprise
Thrown From: atom-tfs package, v0.4.0
Stack Trace
Uncaught TypeError: Cannot read property 'isError' of undefined
At /C:/Users/adfase1/.atom/packages/atom-tfs/lib/tfs/get.coffee:14

TypeError: Cannot read property 'isError' of undefined
    at get (file:///C:/Users/adfase1/.atom/packages/atom-tfs/lib/tfs/get.coffee:12:14)
    at Object.module.exports.AtomTfs.tfsExec (file:///C:/Users/adfase1/.atom/packages/atom-tfs/lib/atom-tfs.coffee:30:5)
    at atom-workspace.subscriptions.add.atom.commands.add.atom-tfs:get (file:///C:/Users/adfase1/.atom/packages/atom-tfs/lib/atom-tfs.coffee:9:80)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (C:\Users\adfase1\AppData\Local\atom\app-1.7.2\resources\app.asar\src\command-registry.js:260:29)
    at CommandRegistry.handleCommandEvent (C:\Users\adfase1\AppData\Local\atom\app-1.7.2\resources\app.asar\src\command-registry.js:3:61)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (C:\Users\adfase1\AppData\Local\atom\app-1.7.2\resources\app.asar\src\command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (C:\Users\adfase1\AppData\Local\atom\app-1.7.2\resources\app.asar\src\atom-environment.js:1100:28)
    at EventEmitter.outerCallback (C:\Users\adfase1\AppData\Local\atom\app-1.7.2\resources\app.asar\src\application-delegate.js:314:25)
    at emitTwo (events.js:87:13)
    at EventEmitter.emit (events.js:172:7)

Commands
     -3:23.1.0 core:delete (atom-text-editor.editor.is-focused)
  2x -3:22.2.0 core:move-right (atom-text-editor.editor.is-focused)
     -3:21.6.0 core:delete (atom-text-editor.editor.is-focused)
  3x -3:17.8.0 core:select-left (atom-text-editor.editor.is-focused)
     -3:15 core:delete (atom-text-editor.editor.is-focused)
  2x -3:14.5.0 core:save (atom-text-editor.editor.is-focused)
     -0:28.6.0 atom-tfs:get (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)

Config
{
  "core": {}
}

Installed Packages
# User
atom-tfs, v0.4.0
atom-tfs-auto, v0.2.0
keyboard-localization, v1.4.18
minimap, v4.23.1

# Dev
No dev packages

+1


Ignore the docs dir

Currently, HTML is automatically generated by CI, so there is no need to include the docs directory in this repository.

:+1: merge when ready


Don't gate code based on enable flag

This might be a controversial change (and it is breaking), but I think the enable feature is spreading bad practices. If a library/binary uses this crate's enable feature, it is still bringing in all the dependencies and build time to set up this crate only to have it be mostly empty. The correct way to use this crate would be to have a tracing feature in user's crates that conditionally enables this one, that way no trace (pun intended) of this crate or its dependencies remains in a production build.
Furthermore, for devs of this crate obeying the enable feature complicates reasoning around structs and the code in general.

I’m not sure what your plan is to deal with builds that do not end up setting TRACY_ENABLE which ends up producing the tracy client library without any symbols. I’m pretty sure we must have a way to not set that environment variable due to how just linking the tracy client libraries can begin broadcasting all sorts of information on the network.
Now one could argue that people could make tracy-client-sys an optional dependency of their crates, but that’s a pretty onerous requirement to maintain given the possible implications of messing it up. On the other hand a disabled-by-default enable feature is much more straightforward to control at the binary crate (with the libraries not needing to worry about it.)

I’m not sure what your plan is to deal with builds that do not end up setting TRACY_ENABLE which ends up producing the tracy client library without any symbols

Hmmm, good point. So is the idea that people would use tracy-client-sys as a library to build other crates? In that case, I think we can leave the enable feature in tracy-client-sys and have it disabled by default (in fact all features should probably be disabled by default). Then, tracy-client and tracy-tracing (which I consider to be end user libraries that should be conditionally compiled in) always set the enable flag.
So the end result is:

tracy-client-sys has all the features and full control.
Client libraries always imply the use tracy and must therefore be removed entirely from the production dependency tree. (And my argument is that this is what people should be doing anyway.)

Removing the enable feature has the nice benefit of making sure that people who upgrade without reading the release notes will notice the behavior changed if they were using the enable feature.

Unfortunately, I do not believe the the downgrade in usability is going to cut it here. I agree that conceptually it is very nice to have the dependents do the proper thing and have the dependencies themselves optional. In practice I don’t think having every invocation of tracy_client::span!() be wrapped in { #![cfg(feature = "tracy-client")] ... } is going to make users happy. However if they don’t mind putting in that sort of effort, there's nothing stopping them from doing so already.
On the other hand, I personally found that handling enable in the implementation of tracy-client and especially tracing-tracy to require minimal effort. Definitely not a sufficient pain point to eschew the benefits these features provide to the users of these crates.

Ah, shoot I forgot about people using plain spans instead of the tracing ones. Bummer, I think you're right that this isn't worth it.


[Feature Request] - Description

Is your feature request related to a problem? Please describe.
Please remove "Greyed logos are not open source." from instructions atop https://landscape.riscv.org/
Describe the solution you'd like
remove "Greyed logos are not open source"
Describe alternatives you've considered
n/a
Additional context
n/a

Fixed by https://github.com/riscv-admin/riscv-landscape/commit/5f6e7d847918c1fc2af95fcd1d9628488291d331


Game crashes when I remove the mod

**Mod Version: **
3.6.10
Forge Version:
<IP_ADDRESS>54
Link to client log:
Even of there is a crash log, the client log can provide the necessary context for why the exception occured.  You can use a service like pastebin or hastebin to upload the log, and paste the link here.  The log file is called latest.txt and can be found in your logs folder.

Description:
Description of the problem.  In the case of crashes, it is good to know things like the following:

Did you just add the mod to a pack? No...
Did it just start crashing, or has it always crashed? It started crashing
Did you update any other mods in your pack and it started crashing?  No...
If updating multiple mods did you update one by one or all at once?  To help narrow the problem down adding one by one is helpful. No...
Is the modpack you are using available online somewhere?  No...

PLSS!!! FIX THIS!!!!!! I CANNOT REMOVE THE MOD!!!!!

FIX YOUR MOD!!! PLSSSS!!!

wait nvm it fixed itself

NVM ITS BACK NANI?!?!?!!

If you removed the mod how can it be my mod?  And you are sure there are no log files, like the forge log?

Not an expert at all, but maybe DSurround causes Mixin 0.8 to load and when removed the next mod in load order has older Mixin and then again the next mods needs 0.8?

same issue for me. idk if i have any logs.

That is why I need the logs to understand what is going on.  If they removed my mod it would not be a factor.  However, there could be another mod needing Mixin.  That information will be in the Forge log.

latest.log
do you need this?

Yep that's it.  And it is Mixin like I was suspecting.  It is being triggered by SteveKunG's-Lib-1.12.2-1.1.9.jar.  You can try adding MixinBootstrap  to your pack to see if it helps.  If that continues to cause an issue, add Mixin Compatibility.

Posted <IP_ADDRESS> to CurseForge as BETA.  MixinBoostrap will also need to be installed.


Please add a cell in dreambooth notebook to stop the image generator cause of OOM

I tested the model and i wanted to retrain new one, i cant ccause model is loaded into memory so please add a cell to unload it so we can train again instesad of disconnecting and running it over from 0
It shows out of memory when i run training after i generated imgs

Is that why I can't find the ckpt file? I wanted to try to train a custom model I had but I couldn't find the model anywhere. Also I notice if you disable the hugginface token line you can't train.

You can restart the runtime (Runtime -> Restart runtime), this will preserve the installed libraries and files. After this, start from the "Login to HuggingFace" cell.
DON'T do "Disconnect and delete runtime" for that, you will start from scratch.


Saving to compressed zarr yields lower or negative compression

xbitinfo version:
xbitinfo                  0.0.2                    pypi_0    pypi

Python version:
python                    3.10.5          hdaaf3db_0_cpython    conda-forge

Operating System:
macOS Big Sur

Description
I ran the tutorial notebook for saving to .nc and .zarr (https://xbitinfo.readthedocs.io/en/latest/quick-start.html). I expected progressively smaller file sizes, with "original" > "compressed" > "bitrounded". For .nc, this is what happened, while for .zarr

the file size of the "original" is 30% smaller than for .nc (2.8 MB).
Doing "ds.to_compressed_zarr") increases the size by 60% (4.5 MB).
Saving the bitrounded data to compressed_zarr yields (as expected) a smaller file size (804 KB), which is 64% larger than the equivalent .nc file

I have uploaded the notebook with results at https://github.com/mattphysics/xbitinfo/blob/main/tests/nb_xbitinfo_export.ipynb

Hi @mattphysics,
Thanks for trying out xbitinfo and opening this PR. The tricky part here is that to_zarr [compresses by default](            assert actual.get_config() == blosc_comp.get_config()). This explains why the xbitinfo/original.zarr is much smaller than xbitinfo/original.nc. The to_compressed_zarr method that xbitinfo provides is rather optimised for bit rounded data and might have some overhead for a small file without bit rounding.
Check out https://github.com/observingClouds/xbitinfo/blob/4d5563e3416d61b26589abcdd32a08dd72fd361b/tests/test_save_compressed.py#L59-L71
Here we explicitly set the compression to None for the to_zarr method.
We should adapt this in the notebook as well.


feat(authorization): adds a section for authorization

I added a library for authorization and related article of how to integrate this library with Express based API.
The library is called CASL - https://github.com/stalniy/casl. There are also a lot of interesting stuff in  documentation - https://stalniy.github.io/casl/ and related articles on Medium.
The library has been around for few months, I used it on several projects and believe it's a very good addition to this list.
Thanks for your time guys!
Relates to #752

Any news? Can this be merged?
In the nearest future I plan to publish 2.0.0 version


Update width.textproto

Per a UXR study with Hilary today, a user reported they felt that "Super" is less than "Ultra".
Since this naming is outside the OT Spec, we could consider renaming "SuperCondensed" to "HyperCondensed".

There is an open question/discussion around this. We'd probably want to review this with Evan.


Vagrant Install Broken with ceph/ubuntu-xenial Box

Vagrant is failing with the following error when using the ceph/ubuntu-xenial box (bento/ubuntu-16.04 completes without error):
==> mon0: Mounting shared folders...
    mon0: /vagrant => /Users/bobthebuilder/gitstuff/ceph-ansible/working-secondary
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

This is using the latest release of Virtualbox and Vagrant and the ceph/ubuntu-xenial box:
Version 5.1.10 r112026 (Qt5.6.2)
Vagrant 1.8.7

Just to be sure :
did you well installed the vagrant-vbguest plugin ?
vagrant plugin install vagrant-vbguest

I also saw this and can verify that vagrant plugin install vagrant-vbguest fixes the issue, at least for me. Is this something we can/should fix in the box itself? With the CI tests we disable the mounting of shared folders, so I imagine that's why we don't run into this there.

No activity. Closing this, feel free to re-open.


Save pkl files

Hi,
is there a way to save the model pkl files?
I added the --save_outputs flag, but they're neither being saved while running the distogram nor the 10A distance mode.

Hi,
Thanks for letting us know! Should be fixed now.


Simplify CocoaPod integration

I think we can use newly released script phases to get rid of manual step in Sourcery integration http://blog.cocoapods.org/CocoaPods-1.4.0/

What script would we put there then? Just $PODS_ROOT/Sourcery/bin/sourcery and rely on config file being in source root?

yeah I think so, yml is the way to go anyway, the command line args are error prone and annoying to repeat when people want to work on new templates etc


Can Proxykit intrgrate with Polly and HttpClientFactory

Can we use polly : https://github.com/App-vNext/Polly  to create resilience and transient-fault-handling

Hi!
Firstly ProxyKit uses HttpClientFactory https://github.com/damianh/ProxyKit#24-configuring-proxykits-httpclient and you can configure it.
Regarding Polly and retries in general, this is something I'd like to see. However there are some challenges... ProxyKit is stream based and not message based for performance reasons - it doesn't buffer the incoming request to be able to forward it to another upstream host by default. If we were to attempt a retry we need to hook into the right places where this makes sense. I think being able to do a retry up to the point the headers are flushed to the upstream host could be achievable. Doing a retry when an error occurs after that is a bit more complex.
Could you share any specific scenarios you have in mind where this would work for you?


Spanish Translation

Hi
In the login Page Appear the text labelNickname
How we can contribute to fix this translation label nickname is not a correct Spanish Word?
Thx in advance...
The parameters are
	$(document).ready(function() {
		Candy.init('http-bind/', {
			core: {
				debug: false,
			view: {
						assets: '../res/',
						language: 'es'
			}
		});

		Candy.Core.connect('mailfarma.perizia.es');

You can submit a pull request correcting the translation, or provide the correct translation here so we can correct it. I don't think any committers speak Spanish ;)

Hi again...
The correct translation for this context is "Alias"
But we can help checking the full spanish translation text... Where is this file? is separate text file?
thx

https://github.com/candy-chat/candy/blob/dev/src/view/translation.js#L32

Thx Again i have submit a pull request...

Hey @wildfandango, I don't see that pull request anywhere. Did you have trouble with it?


Refactor utils.py

utils.py file started to get really big and lots of functions could have been in separate files. This PR aims at creating new files to refactor utils.py. This will break retro compatibility.
fix #490

Pull Request Test Coverage Report for Build 336281920

308 of 346 (89.02%)  changed or added relevant lines in 18 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 91.227%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ivadomed/training.py
2
4
50.0%

ivadomed/uncertainty.py
89
91
97.8%

ivadomed/inference.py
127
140
90.71%

ivadomed/visualize.py
11
32
34.38%

Totals

Change from base Build 332653891:
0.05%

Covered Lines:
5657

Relevant Lines:
6201

💛  - Coveralls


Integrate leak tracking with testWidgets and stop using testWidgetsWithLeakTracking in flutter/test.

https://flutter.dev/go/clean-up-not-disposed-disposables-in-ff

[ ] Update leak_tracker:

[x] Define adjustable settings: https://github.com/dart-lang/leak_tracker/pull/152
[x] https://github.com/dart-lang/leak_tracker/pull/159
[x] Use adjustable settings: https://github.com/dart-lang/leak_tracker/pull/158
[x] https://github.com/dart-lang/leak_tracker/pull/160
[ ] Separate 'memory_usage'
[ ] Update G3 to mirror 'memory_usage' with SDK
[ ] Update analyzer to use 'memory_usage' instead of leak_tracker
[ ] Clean up memory usage in leak_tracker
[ ] Update G3 to mirror 'leak_tracker' and 'leak_tracker_testing' from github

[ ] Update flutter_test:

[x] Take dependency on leak_tracker: https://github.com/flutter/flutter/pull/137646
[ ] Add parameter: https://github.com/flutter/flutter/pull/137655
[ ] Update testWidgets to track leaks

[x] Update testWidgetsWithLeakTracking to explicitly set leak tracking off in invoked testWidgets.
[ ] Update flutter tests:

[ ] Explicitly turn off leak tracker for all testWidgets and enable leak tracker by default
[ ] Convert testWidgetsWithLeakTracking to testWidgets.

[ ] Remove testWidgetsWithLeakTracking from leak_tracker.

G3 specific information: https://docs.google.com/document/d/1gSfOSI61d01bhCUnXcPTsrGyBKQ7CN4lqHim7hzWCNw/edit

test to add to leak_tracker after integration:
  testWidgets(
    _test6TrackingOnWithPath = 'test6, tracking-on, with path',
  experimentalLeakTesting: LeakTesting.settings.withRetainingPath(),
    (WidgetTester widgetTester) async {
      expect(LeakTracking.isStarted, true);
      expect(LeakTracking.phase.name, _test6TrackingOnWithPath);
      expect(LeakTracking.phase.ignoreLeaks, false);
      await widgetTester.pumpWidget(StatelessLeakingWidget());
    },
  );

  Validation in tear down should be:

  _verifyLeaks(
     reportedLeaks,
     _test6TrackingOnWithPath,
     notDisposed: 1,
     notGCed: 1,
     expectedContextKeys: <LeakType, List<String>>{
       LeakType.notGCed: <String>['path'],
       LeakType.notDisposed: <String>[],
     },
  );


WIP Schedule reconcile even when service is updating

Don't reject reconcile request when the service is in updating-active state. It makes it race condition prone for this scenario:

service reconcile is finished, but the state of the service wasn't updated yet
during this time, instance gets stopped/removed
but the reconcile request gets rejected as service wasn't put into active state

So we end up having degraded service in active state.

https://github.com/rancher/rancher/issues/5556
https://github.com/rancher/rancher/issues/6092
https://github.com/rancher/rancher/issues/5775


terraform-graph-beautifier: autoupdate issues

terraform-graph-beautifier: 0.3.1 (scoop version is 0.2.0) autoupdate available...
https://github.com/brave-simpletons/scoop-the-business/actions/runs/3833011235/jobs/6523989191#step:3:422
The manifest may need to be updated

related #128 and fixed by #143


watchlog.sh no output when downloading dota 2 updates

I am testing this steamcache but not getting any output from watchlog.sh even already downloading dota 2 updates. I run both steamcache and steamcache dns on same server but if i open the ip address of of the server from local lan where the steamcache is running. I, got an error page coming from nginx server and there is log output on watchlog.sh but not when downloading dota 2 updates. btw newbie running docker.

Actually there is a bug in the config for the new cdn domain *.steampipe.steamcontent.com.
See my PR https://github.com/steamcache/steamcache-dns/pull/5
You can use my fork from the repo https://github.com/Robby12345/steamcache-dns and build the docker image yourself with docker build -t fixed-steamcache-dns steamcache-dns/

@Robby12345's PR has now been merged, and the Docker image on the hub has been updated. Give the updated DNS image a go (docker pull steamcache/steamcache-dns, then recreate your container) and see if that resolves your issue.


fix: remove width from pageSize selectList box

What
Fixes the size of the Page Size selector by removing the width attribute sent to it.
Media
Page size selector with not broken size:

Why
There is a bug where the page size selector is too small and does not fully display the number of the selected page size. By removing the set width="4.5em" it displays the selected page size correctly.
Closes #331

How
Remove the width attribute from the PageSize selector box.

Have you considered setting minWidth here to restrict the minimum size?

hey @nlopin, I didn't do that since the Box position is absolute its size doesn't really seem to change with different screen sizes 🤔
I just tried with '5em' instead of the '4.5em' that we had before and it was too small, it doesn't seem to affect the size at all

I don't understand why we set position to absolute for this element. I suspect it could be because the popup is cut. Could you check that? if we can get rid of the absolute positioning and use flexbox to properly place the element

sure, let me try to do that. I believe the absolute value for the pagesize is there to set it to left while having the pagination navigation buttons right in the middle, but let me try to check what can be done with flex


testGlobalVariableInitWithInvocationNegative is failing intermittently.

This test-case is failing intermittently. Shall I disable it for now? Can you create an issue for this?
Originally posted by @hasithaa in https://github.com/ballerina-platform/ballerina-lang/pull/22818/review_comment/create

Enabled in https://github.com/ballerina-platform/ballerina-lang/pull/23215.


Changed return value of window based event listeners

For "beforeunload" events the return value must be "undefined" instead of "true" to prevent the appearance of a dialog box.

tested on IE8 , to bad I cannot think of any reliable way to automate the test but it's already in (I've patched locally).
The reason it's returning true or false is because dispatchEvent is supposed to return that.
However, it's true that within generic direct methods it shouldn't return anything unless it's false.
Will be out this evening as 0.6.0
Cheers


Dry Out Jira-V2 Output

to: @ryandeivert @chunyong-lin @Ryxias
cc : @blakemotl
related to: https://github.com/airbnb/streamalert/pull/1311
Background
The following change was discussed on https://github.com/airbnb/streamalert/pull/1311 where the original Jira-v2 was just a heavy cut/paste job with some slight modifications, which is not ideal.
https://streamalert.slack.com/archives/C3BHE2Z0S/p1610399094191300
This is cleaning up all of that tech debt.
Changes

Dry Out the config.
_api_key is now password and we use the existing credentials helper.

Contentious points

This will break existing Jira-V2 users as the credential for api_key has changed to password , I can add a small helper to pull from this field if password is none etc but curious thoughts on that one.
This overloads self._cookie which is now holding the base64 encoded authorization bearer token.

Testing
This was tested in conjunction with https://github.com/airbnb/streamalert/pull/1311 against a live environment.

@chunyong-lin jira-cloud SGTM I would like to see what #1311 and v4 look like before a major overhaul, however building and introducing before a major breaking change and removing old Outputs like PD v1, Jira, etc may make sense.


bug??

https://github.com/envoyproxy/envoy/blob/52668550a903d528cb4f7ee2eb815e76e44363c5/envoy/registry/registry.h#L181

I think so：
static absl::flat_hash_map<std::string, Base*>  factories；
if (!factories)
factories = new absl::flat_hash_map<std::string, Base>;

the local static declaration of factories in that function effectively only initializes it once. e.g. it's essentially the code you wrote.


Reading and writing to the same hardware interface

To implement a joint position controller (which accepts a topic input), we need to be able to read the current state of the robot. To do this, I added the "/position" interface to the configure_state_interfaces method, as shown here. When I do so, I get the following error.
If we cannot read and write to the same hardware interfaces, I think we can add one extra topic input to the controller which accepts the published robot state. Still, I think the optimal solution is reading the state directly from the hardware interface. Is this supported?

Launch Output
$ ros2 launch franka_bringup joint_position_example_controller.launch.py robot_ip:=${IP}

[spawner-5] [INFO] [1711125035.965050119] [spawner_franka_robot_state_broadcaster]: Configured and activated franka_robot_state_broadcaster
[spawner-7] [INFO] [1711125035.969229936] [spawner_joint_position_example_controller]: Configured and activated joint_position_example_controller
[spawner-4] [INFO] [1711125035.971297980] [spawner_joint_state_broadcaster]: Configured and activated joint_state_broadcaster
[ros2_control_node-3] terminate called after throwing an instance of 'franka::ControlException'
[ros2_control_node-3]   what():  libfranka: Move command aborted: motion aborted by reflex! ["joint_motion_generator_acceleration_discontinuity"]
[ros2_control_node-3] Stack trace (most recent call last) in thread 845:
[ros2_control_node-3] #19   Object "", at 0xffffffffffffffff, in
[ros2_control_node-3] #18   Object "/usr/lib/x86_64-linux-gnu/libc.so.6", at 0x7ff0ad13f84f, in
[ros2_control_node-3] #17   Object "/usr/lib/x86_64-linux-gnu/libc.so.6", at 0x7ff0ad0adac2, in
[ros2_control_node-3] #16   Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30", at 0x7ff0ad33e252, in
[ros2_control_node-3] #15   Object "/opt/ros/humble/lib/controller_manager/ros2_control_node", at 0x55c0f40f7800, in
[ros2_control_node-3] #14   Object "/opt/ros/humble/lib/libcontroller_manager.so", at 0x7ff0ad74a2d4, in controller_manager::ControllerManager::read(rclcpp::Time const&, rclcpp::Duration const&)
[ros2_control_node-3] #13   Object "/opt/ros/humble/lib/libhardware_interface.so", at 0x7ff0acf4e69c, in hardware_interface::ResourceManager::read(rclcpp::Time const&, rclcpp::Duration const&)
[ros2_control_node-3] #12   Object "/opt/ros/humble/lib/libhardware_interface.so", at 0x7ff0acf6be8f, in hardware_interface::System::read(rclcpp::Time const&, rclcpp::Duration const&)
[ros2_control_node-3] #11   Object "/workspaces/bdai/_build/build/franka_hardware/libfranka_hardware.so", at 0x7ff092f27cb8, in franka_hardware::FrankaHardwareInterface::read(rclcpp::Time const&, rclcpp::Duration const&)
[ros2_control_node-3] #10   Object "/workspaces/bdai/_build/build/franka_hardware/libfranka_hardware.so", at 0x7ff092f441a4, in franka_hardware::Robot::readOnce()
[ros2_control_node-3] #9    Object "/workspaces/bdai/_build/build/franka_hardware/libfranka_hardware.so", at 0x7ff092f4557f, in franka_hardware::Robot::readOnceActiveControl()
[ros2_control_node-3] #8    Object "/usr/lib/libfranka.so.0.13.2", at 0x7ff092c91527, in franka::ActiveControl::readOnce()
[ros2_control_node-3] #7    Object "/usr/lib/libfranka.so.0.13.2", at 0x7ff092c8fde2, in franka::Robot::Impl::throwOnMotionError(franka::RobotState const&, unsigned int) [clone .cold]
[ros2_control_node-3] #6    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30", at 0x7ff0ad3104d7, in __cxa_throw
[ros2_control_node-3] #5    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30", at 0x7ff0ad310276, in std::terminate()
[ros2_control_node-3] #4    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30", at 0x7ff0ad31020b, in
[ros2_control_node-3] #3    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30", at 0x7ff0ad304b9d, in
[ros2_control_node-3] #2    Object "/usr/lib/x86_64-linux-gnu/libc.so.6", at 0x7ff0ad0417f2, in abort
[ros2_control_node-3] #1    Object "/usr/lib/x86_64-linux-gnu/libc.so.6", at 0x7ff0ad05b475, in raise
[ros2_control_node-3] #0    Object "/usr/lib/x86_64-linux-gnu/libc.so.6", at 0x7ff0ad0af9fc, in pthread_kill
[ros2_control_node-3] Aborted (Signal sent by tkill()<PHONE_NUMBER>74)

when the controller first start, we calculate need to calculate the trajectory based on the initial_q that we get in the beginning. This is partially a bug from our side. You can see an example of this in the libfranka as well https://github.com/frankaemika/libfranka/blob/master/examples/generate_joint_position_motion.cpp#L51.
So you need to keep the initial_q for the first calculation for your trajectory. You could still add another state_interface which has the position interface.
Try this sample:
controller_interface::InterfaceConfiguration
JointPositionExampleController::state_interface_configuration() const {
  controller_interface::InterfaceConfiguration config;
  config.type = controller_interface::interface_configuration_type::INDIVIDUAL;
  for (int i = 1; i <= num_joints; ++i) {
    config.names.push_back(arm_id_ + "_joint" + std::to_string(i) + "/" + k_HW_IF_INITIAL_POSITION);
    config.names.push_back(arm_id_ + "_joint" + std::to_string(i) + "/position");
  }
  return config;
}

controller_interface::return_type JointPositionExampleController::update(
    const rclcpp::Time& /*time*/,
    const rclcpp::Duration& /*period*/) {
  if (initialization_flag_) {
    for (int i = 0; i < num_joints; ++i) {
      initial_q_.at(i) = state_interfaces_[2 * i].get_value();
    }
    initialization_flag_ = false;
  }
  for(int i =0; i< num_joints; ++i){
    q_.at(i) = state_interfaces_[2*i + 1].get_value();
  }

  elapsed_time_ = elapsed_time_ + trajectory_period;
  double delta_angle = M_PI / 16 * (1 - std::cos(M_PI / 5.0 * elapsed_time_)) * 0.2;

  for (int i = 0; i < num_joints; ++i) {
    if (i == 4) {
      command_interfaces_[i].set_value(initial_q_.at(i) - delta_angle);
    } else {
      command_interfaces_[i].set_value(initial_q_.at(i) + delta_angle);
    }
  }

  return controller_interface::return_type::OK;
}

Thanks for your replies & explanation! I've tried a few iterations of the code you sent above. You do have to read from state_interfaces_[2*i] before you read from state_interfaces_[2*i+1]; if you don't you get a discontinuity ControlError.
When writing to hardware interfaces in a ROS2 controller, I typically don't think about the motion generator running "under the hood" in the arm's embedded system. My understanding of ROS2 control is that all of the implementation details below the hardware interface should be abstracted away from the controller level. Is there any way for this behavior to change? As it stands, when writing to the position interface, it looks like every controller needs to read from a hardware interface it doesn't explicitly need to satisfy the embedded system running underneath the hardware interface. If you are looking for some open-source support in the form of PRs, please let me know.

sorry I didn't it get it completely. Did what I send you satisfy what you needed?

sorry I didn't it get it completely. Did what I send you satisfy what you needed?

The instruction to read from the initial_joint_position interface if you want to write to the position interface, even if you don't need the initial_joint_position in your controller, does fix the issue I was experiencing. I could be wrong of course, but I think that this behavior is a slightly incorrect implementation of the ROS2 hardware interface, though. I don't think controllers should have to read from a state interface they don't need; all command interfaces should be ready to be written to after on_configure.

No you don't always need the initial_joint_position unless you command the robot. You can remove the commanding section and just read the state part.
controller_interface::InterfaceConfiguration
JointPositionExampleController::state_interface_configuration() const {
  controller_interface::InterfaceConfiguration config;
  config.type = controller_interface::interface_configuration_type::INDIVIDUAL;
  for (int i = 1; i <= num_joints; ++i) {
    config.names.push_back(arm_id_ + "_joint" + std::to_string(i) + "/position");
  }
  return config;
}

controller_interface::return_type JointPositionExampleController::update(
    const rclcpp::Time& /*time*/,
    const rclcpp::Duration& /*period*/) {

  for(int i =0; i< num_joints; ++i){
    q_.at(i) = state_interfaces_[i ].get_value();
  }

  return controller_interface::return_type::OK;
}

Yes agreed. I think being required to read from initial_joint_position if you want to write to position is an incorrect implementation of the ROS2 control / hardware interfaces.

when the controller first start, we calculate need to calculate the trajectory based on the initial_q that we get in the beginning. This is partially a bug from our side

You are correct, I mentioned this here.

Sorry, I'm surprised this issue was closed. Does the team plan to fix the issue so that franka_ros2 complies with ROS2's controller and hardware interfaces? If so, should I make a separate issue for the interface bug?

Sorry for not being clear. This bug is not on the franka_ros2 or in the FCI side. And this should not prevent you from writing your joint position controller. If you need more help, you could share your code. We can try to fix your issue.

Btw you can always activate the rate limiter and low pass filter to avoid  ["joint_motion_generator_acceleration_discontinuity"] erros -> https://github.com/frankaemika/franka_ros2/blob/40cf08b6f0c2d66fa568b2a3336f1ac7971995ed/franka_hardware/include/franka_hardware/robot.hpp#L316


Problem with TypeScript 3.1.1 and style properties

There is a type error in the new TypeScript 3.1.1 with all native-base Component style properties:
Type 'RegisteredStyle<ViewStyle | TextStyle | ImageStyle>' is not assignable to type 'ViewStyle | ViewStyle[]'.
  Type 'RegisteredStyle<ViewStyle | TextStyle | ImageStyle>' is not assignable to type 'ViewStyle[]'.
    Property 'length' is missing in type 'Number & { __registeredStyleBrand: ViewStyle | TextStyle | ImageStyle; }'.

I think #2123 would be a potential fix for this.
Noticed this because 3.1.1 is now the default version shipping with the update to VS Code. Changing typescript back to 3.0.3 gets rid of this error.

+1

I'm experiencing the same issue when trying to apply some styles to Content:
<Content contentContainerStyle={styles.content}>
Using this dependencies:
"native-base": "^2.8.1",
"react": "16.6.0-alpha.8af6728",
"react-native": "0.57.4",
"typescript": "^3.1.3"

Same here. Would be nice to have that fixed

#2562


Incorporate 1.7.2 changes

Updates adapter to 1.7.2

One piece here about two tests related to the full refresh of seeds.
It doesn’t seem to want to drop the table to pass that materializations test.
Not sure if tests want to be revisited to see if there is any tests that are covered in the parent adapter. Kept the existing tests here and they passed (calling the fabric macros where not otherwise defined).

@cody-scott :
Thanks for the hard work!
What is pending the merge of the code? Reviews? Fixing the full refresh of seeds? Additional tests?

I believe we are waiting on the repo maintainers to take a look.
Further work is needed to add the full suite of tests that DBT provides, and to see if that full-refresh failure can be corrected (or ignored) for now.

@cody-scott : can you tag the maintainers as reviewers or is that not possible ?

Hey @cody-scott !!! I believe I have maintainer status on the repo -- I volunteered a couple months ago to help this along. really happy to see an attempt here -- i've been hacking away at my own fixes but it seems like we can start from yours!!
Leaving a comment in a review about some tests that you commented out but overall as soon as we get that addressed I can run CI on this and merge if it passes!
also, my dev container crashed on startup so i might be suggesting some changes there.
Thanks for the help!

one more thing... on my machine i'm getting failures for the 3 test_docs tests in addition to the two i believe you mentined for test_seed... dont have time to dig in tonight but i'm attaching test report logs:
test_results.json

@sdebruyn and @dataders : Could you have a look? We are waiting for this update

@sdebruyn and @dataders : Could you have a look? We are waiting for this update

sdebruyn is no longer maintaining this repo and I believe dataders is on parental leave until march... I believe I am your point of contact for now :)

Ok, i'm seeing 5 failed @schlich from your json file.

TestBasicSeedTestsSQLServer.test_simple_seed_full_refresh_flag
TestBasicSeedTestsSQLServer.test_simple_seed_full_refresh_flag
TestDocsGenReferencesSQLServer.test_references
TestDocsGenerateSQLServer.test_run_and_generate
TestDocsGenerateSQLServer.test_run_and_generate_no_compile

In terms of some of the failing azure tests, I think most of that should pull from fabric, but not positive here (might need to look closer). We aren't using azure so i don't have a reliable way to test on my side.
Is there an appetite to add some of the other tests that dbt has introduced since 1.4? I believe there is a number more in their suite now.
Next steps i'm seeing:

Sort out why the full refresh seeds aren't working
See if there is a link to the docs and full-refresh issue; if not look at that
Sort out the azure auth component for those using service principals/entra

Two questions here:

The behaviour of the default seed full refresh test seems to be expecting the table to not exist. This is not the case as its dropping + creating right away in the log file for that step. The default implementation then won't pass.
In the fabric adapter they have over-riden most (or all, i haven't checked the full set) of the tests to have it expecting the table to exist https://github.com/microsoft/dbt-fabric/blob/main/tests/functional/adapter/test_seed.py#L599

The fabric adapter seems to have re-written
many of the tests and not implemented the default test suite from dbt; same problem they're having?
I am puzzled here; it seems like we should be expecting the table to exist (like what the fabric one does)
The default implementation doesn't seem to have changed, so unless something has changed on the seed/full refresh side then the way forward would be updating those tests that are failing to pass, as the full refresh is recreating the tables.
@schlich what are you thinking here?
second step of test dbt.log
Log file for only the second step (run_dbt seed full refresh) where its pretty clear its dropping + creating.

One approach here would be to re-align with the same test set of fabric or try and get the tests in line with the current dbt suite + any one-off modifications as required.

Ok, i think i've got the issue; the downstream view isn't being dropped as part of the full refresh. Not sure exactly what changed but that seems to be the issue here. Maybe its something fabric is doing that isn't aligning...

Alright I think this is the state.
The base tests are expecting that it performs like postgres and should perform a 'drop view/table cascade', which would explain why the test is expected to have no view on a full refresh.
Since sql server doesn't support this I see two options

Implement a similar cascade drop by determining the downstream views with this sys.sql_expression_dependencies. This would be the closest representation to the expected DBT behaviour. 2. Ignore this and pass the tests with it expecting the tables, don't drop the views until that step is run in the build.

Upside of the first is its closest to the expected DBT, downside is it's going to drop all downstream tables and views. If you have anything that relies on them in build then it's going to remove them until it hits that step. relevant discussion.
Other piece is non dbt controlled views will also get dropped.
Fabric is going for option 2.
@schlich What's your thoughts? It's tied to full refresh so that's probably why those particular items are failing (I think).

I also would like to volunteer to help if I can. Give me a task and I'll make a run at it. Thanks so much for your work on this @cody-scott !

I am making an effort at getting the functional tests running. It may take me some time to get up to speed on the code.

@prescode FWIW with the whole test ecosystem in the state its in i genuinely don't think its worth your mental effort to wrap your mind around the architecture.  All you really need to know is that we opt-in to tests by subclassing them in a tests file and then the good lord knows what happens during test prep and execution while god knows what is being tested.  Its a really peculiar structure that i have a really long forum post halfway typed up about. The whole suite needs to be burned down and implemented with proper pytest fixtures.  ANYWAYS...
The Make instructions should be fairly simple i think.  having just boostrapped my own env i just had to make a virtual environment, pip install ., copy the example .env to a live copy, and then make server and make test.  Let me know if that helps.

Test environment is up and I'm able to run the test suite. I've made some progress but I need some sleep. I'll try finish up tomorrow.

Ok, i'm seeing 5 failed @schlich from your json file.

TestBasicSeedTestsSQLServer.test_simple_seed_full_refresh_flag
TestBasicSeedTestsSQLServer.test_simple_seed_full_refresh_flag
TestDocsGenReferencesSQLServer.test_references
TestDocsGenerateSQLServer.test_run_and_generate
TestDocsGenerateSQLServer.test_run_and_generate_no_compile

In terms of some of the failing azure tests, I think most of that should pull from fabric, but not positive here (might need to look closer). We aren't using azure so i don't have a reliable way to test on my side.
Is there an appetite to add some of the other tests that dbt has introduced since 1.4? I believe there is a number more in their suite now.
Next steps i'm seeing:

Sort out why the full refresh seeds aren't working
See if there is a link to the docs and full-refresh issue; if not look at that
Sort out the azure auth component for those using service principals/entra

The doc errors

TestDocsGenerateSQLServer.test_run_and_generate
TestDocsGenerateSQLServer.test_run_and_generate_no_compile

are related to the time_type data type in the test fixture:
    @pytest.fixture(scope="class")
    def expected_catalog(self, project):
        return base_expected_catalog(
            project,
            role=os.getenv("DBT_TEST_USER_1"),
            id_type="int",
            text_type="varchar",
            time_type="datetime",
            view_type="VIEW",
            table_type="BASE TABLE",
            model_stats=no_stats(),
        )

The fixture in dbt-fabric uses datetime2.
Updating to datetime2 results in a pass
    @pytest.fixture(scope="class")
    def expected_catalog(self, project):
        return base_expected_catalog(
            project,
            role=os.getenv("DBT_TEST_USER_1"),
            id_type="int",
            text_type="varchar",
            time_type="datetime2",
            view_type="VIEW",
            table_type="BASE TABLE",
            model_stats=no_stats(),
        )

I'm fairly certain this is the correct fix but being unfamiliar with the code I'm looking for confirmation. Any insight into this update?

I had hoped to get further along but I'm struggling to figure out this testing scheme and trace the tests. I've overridden some of the test fixtures but I'm still getting failures. I'll not have much time in the next couple of days to continue but I'll pick it up again on the weekend if needed.

Ok, i'm seeing 5 failed @schlich from your json file.

TestBasicSeedTestsSQLServer.test_simple_seed_full_refresh_flag
TestBasicSeedTestsSQLServer.test_simple_seed_full_refresh_flag
TestDocsGenReferencesSQLServer.test_references
TestDocsGenerateSQLServer.test_run_and_generate
TestDocsGenerateSQLServer.test_run_and_generate_no_compile

In terms of some of the failing azure tests, I think most of that should pull from fabric, but not positive here (might need to look closer). We aren't using azure so i don't have a reliable way to test on my side.
Is there an appetite to add some of the other tests that dbt has introduced since 1.4? I believe there is a number more in their suite now.
Next steps i'm seeing:

Sort out why the full refresh seeds aren't working
See if there is a link to the docs and full-refresh issue; if not look at that
Sort out the azure auth component for those using service principals/entra

The doc errors

TestDocsGenerateSQLServer.test_run_and_generate
TestDocsGenerateSQLServer.test_run_and_generate_no_compile

are related to the time_type data type in the test fixture:
    @pytest.fixture(scope="class")
    def expected_catalog(self, project):
        return base_expected_catalog(
            project,
            role=os.getenv("DBT_TEST_USER_1"),
            id_type="int",
            text_type="varchar",
            time_type="datetime",
            view_type="VIEW",
            table_type="BASE TABLE",
            model_stats=no_stats(),
        )

The fixture in dbt-fabric uses datetime2. Updating to datetime2 results in a pass
    @pytest.fixture(scope="class")
    def expected_catalog(self, project):
        return base_expected_catalog(
            project,
            role=os.getenv("DBT_TEST_USER_1"),
            id_type="int",
            text_type="varchar",
            time_type="datetime2",
            view_type="VIEW",
            table_type="BASE TABLE",
            model_stats=no_stats(),
        )

I'm fairly certain this is the correct fix but being unfamiliar with the code I'm looking for confirmation. Any insight into this update?

I've run into the same error in other contexts, I can confirm this fix.
Can you push up a PR of your WIP against this branch so i can examine and potentially merge?

@schlich it looks like you beat me to it. We don't need to merge my changes anymore, correct? I also made a change to the devcontainer.json file to update the path to the test.env file based on our above conversation. Let me know if there is anything else I can do to help.

@mikaelene SOS if you are around.  We need an organization owner to remove the dependency on Python 3.7 in the required checks.  Will see if anyone has a hotline to @dataders otherwise, or we will have to wait until he returns from parental leave and explore an unofficial pypi release in the meantime.  Unless anyone else is seeing anything i'm not!
But we're almost there!!!!

SOS
@alieus
@b-per
@sdebruyn
@timdenouden

Hi @schlich , I might be able to help while Anders is out.
Can you tell me where you see the dependency on Python 3.7 in the required checks?

Hi @b-per it was a busy day yesterday! I was able to obtain admin perms to the repo to remove the 3.7 check myself.  Today we are stuck with the pyPI release.  Do you have access there?

No, I don't have access to this one.
Looking at the git blame the release action was originally set by @sdebruyn and there a few maintainers on PyPi but I am not in the list

I updated the token in the GH secrets, I don't have access to add other folks myself.


INSTALLLEVEL=3 inclusion of IcedTea-Web fails to set JNLP MIME type in registry

Hi folks, apologies, AdoptOpenJDK seems to replicate a known issue that was resolved in the IcedTea-Web standalone installer, issue # 371. This issue is failure to create registry key HKEY_CLASSES_ROOT\MIME\Database\Content Type\application/x-java-jnlp-file, which in turn means that JNLP web content is downloaded without OS/browser capacity to translate to a known file extension. This then in turn prevents group policies for Edge Chromium to auto-open by filetype on trusted domains as there is no file extension.
Happy to elaborate on this request as needed. Thank you for the consideration!

issue placed in wait state as we don't include ITW in new Temurin build for now

@douph1 We see similar issue with Semeru JDK8 build which has ITW shipped. Could you please check on this. Thank you

Since this was bumped, I suppose I'll add a question - was ITW ever re-added to new Adoptium Temurin builds for JRE 8? Thank you!

Since this was bumped, I suppose I'll add a question - was ITW ever re-added to new Adoptium Temurin builds for JRE 8? Thank you!

In short no - but you can follow the blog post on how to add it from the blog.adopopenjdk.net site.

@douph1 Semeru JDK8 has ITW with it and we see issue with JNLP registry keys, could you please check this.

Raised a PR with changes
https://github.com/adoptium/installer/pull/547


[UI] Overlap button in mobile view

Description
In the mobile view, the image with "before" and "after" text overlaps the "View Docs" button.
Expected Behavior
There should be a top margin for the image in the mobile view to fix this overlap.
Screenshots

Enviroment:

OS:  Linux
Browser:  Firefox
Version:
Device: Desktop Mobile

Additional Information
If you find this issue valid, I can fix this issue.

Contributor Guides and Handbook
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Closing this issue because it is a duplicate of #1822.

@amitamrutiya Opening this as we haven't heard back from @rahulrana701. You can proceed with the PR. Let's discuss it in our next Monday call.

Fixes #1822

Sure, I will work on it shortly.

@amitamrutiya Please include the steps to reproduce the issue or the URL of the page where the problem occurs. This will help others replicate the issue more easily.

@Aviral0702 Refer: #1822


CVE-2021-44716 (go net/http)

This CVE was published on 01/01/2022: https://nvd.nist.gov/vuln/detail/CVE-2021-44716
The Go net/http package has a vulnerability for non-gRPC HTTP/2 endpoints. This vulnerability affects all HTTP endpoints in Antrea as HTTP/2 is enabled by default for Go HTTP servers. It can cause increased memory consumption in the Antrea processes until they are OOM-killed.
All Go versions prior to 1.16.12 and 1.17.5 (released in December) suffer from this vulnerability.
This vulnerability has already been addressed in upstream K8s and patch releases built with recent Go versions are already out.
We must also release new Antrea patch releases for all supported minor versions, namely 1.4, 1.3 and 1.2.
For Antrea 1.4 and 1.3, these release trains already use Go 1.17.x, so simply releasing a new patch will be enough.
Antrea v1.4.0 -> go1.17.3
Antrea v1.3.0 -> go1.17
For Antrea 1.2, we can either update the Go version from 1.15 to 1.16, or we can set this environment variable at runtime in the Docker image to disable HTTP/2: GODEBUG=http2server=0. I would lean towards the first solution.
Antrea v1.2.3 -> go1.15.15

All Antrea minor releases >= 1.2 have a patch release built with Go 1.17


Default Password Issue

The default password (EC2 Instance ID) does not seem to work with the new longer form IDs.

Chris - Thanks for notifying about the issue. Can you let us know whether you used the marketplace version or the one from the github and also the instance id that you used for our records.

The AMI we're using is from GitHub: ami-fd838b97. The instance ID for my EC2 instance is similar to: i-0440832b5e2ef4dc2
And thanks for the quick reply. :+1:

Chris - Did you launch it from the market place as the cloud formation stack or used the AMI option? The AMI option requires the IAM role es-admin role created prior to the launching of EC2 instance using AMI. We tested the long instance id a few times and did not encounter the same issue, that's why some insight will be helpful.

We tried the CloudFormation deployment twice with no success, which is why we ended up trying the AMI. We have not created the es-admin role yet, as it was our understanding it was only required to prevent an error within the app configuration.
We'll create the role and let you know the outcome. One more item of note is that our VPC is configured for dedicated instances, but I don't know how that'd affect the instance.

(1) Instance created directly must have an IAM role equivalent of es-admin attached to it before launch otherwise the initialization will fail as it needs to created S3 bucket, DynamoDB tables etc..
(2)  VPC settings do have an impact on the ESS tool.. For eg.: VPCs used for the ess the setting  DNS hostnames: yes (If this setting is NO then the system will fail with the unknown exception);
(3) catalina.out in the apache-tomcat log files folder will have the actual issue, that will help in troubleshooting the actual issue.

Thanks for your help. Creating the role resolved the login issue. My fault for misinterpreting the intent of it.
As far as VPC settings, we use internal DNS which is setup in our DHCP scope. Will that be sufficient for  this app?

Please check whether you are able to backup and restore volumes successfully. If that looks fine the VPC settings are fine. Otherwise send us a screenshot or text the VPC settings to review.

@ChrisJones75 the application runs entirely against the AWS API, so it will need outbound access to the public AWS endpoints (it will not work in a private only subnet).  As long as a public route exists the internal DNS should not interfere with that.
Since the original scope is resolved, I will close this issue.  I would like to know what did not work with the CloudFormation build.  If you have some more data you can provide for that, please open another issue so that we can take a look.


infer_tensorrt_imagenet.py: Not Predicting The Correct Classes

Hi @rmccorm4 ,
I am using the infer_tensorrt_imagenet.py file to infer the images of imagenet  with the int8 engine created by TensorRT.
Here is the way that I am using the code:
python3 infer_tensorrt_imagenet.py --engine resnet18.int8.engine
-d /home/hassan/Datasets/ImageNet/ -b 1 -n 5
Here are the results:
[TensorRT] WARNING: Current optimization profile is: 0. Please ensure there are no enqueued operations pending in this context prior to switching profiles
[TensorRT] WARNING: Explicit batch network detected and batch size specified, use execute without batch size instead.
Allocating buffers ...
 Please ensure there are no enqueued operations pending in this context prior to switching profiles
[TensorRT] WARNING: Explicit batch network detected and batch size specified, use execute without batch size instead.
Allocating buffers ...
Input image: /home/hassan/Datasets/ImageNet/ILSVRC2012_val_00000073.JPEG
Prediction: wall clock                     Probability: 0.06
Prediction: matchstick                     Probability: 0.06
Prediction: switch                         Probability: 0.04
Prediction: screw                          Probability: 0.03
Prediction: envelope                       Probability: 0.02
[TensorRT] WARNING: Current optimization profile is: 0. Please ensure there are no enqueued operations pending in this context prior to switching profiles
[TensorRT] WARNING: Explicit batch network detected and batch size specified, use execute without batch size instead.
Allocating buffers ...
Input image: /home/hassan/Datasets/ImageNet/ILSVRC2012_val_00000117.JPEG
Prediction: wing                           Probability: 0.07
Prediction: spotlight                      Probability: 0.02
Prediction: lampshade                      Probability: 0.02
Prediction: matchstick                     Probability: 0.02
Prediction: wall clock                     Probability: 0.02
[TensorRT] WARNING: Current optimization profile is: 0. Please ensure there are no enqueued operations pending in this context prior to switching profiles
[TensorRT] WARNING: Explicit batch network detected and batch size specified, use execute without batch size instead.
Allocating buffers ...
Input image: /home/hassan/Datasets/ImageNet/ILSVRC2012_val_00000113.JPEG
Prediction: wall clock                     Probability: 0.06
Prediction: envelope                       Probability: 0.06
Prediction: matchstick                     Probability: 0.04
Prediction: lampshade                      Probability: 0.03
Prediction: refrigerator                   Probability: 0.03
There are certain classes popping up (like wall clock). Can you kindly help?
Thank you.

Hi @Hassan313 ,
Sorry for the delay.
Few questions come to mind:

Are the inference results correct on fp32/fp16 engines? If yes, then probably an int8 calibration issue. If not, then probably an issue with the model/conversion.

Was your int8 calibration data similar/representative of the data you're testing with inference?

Are the image already pre-processed?

Does using a different pre-processing function give better results?