text:
Reproducing results for QM9

Hi! I have recently been trying to reproduce your results for QM9 and have some questions. I forked your code this week and started a run on QM9 for predicting the HOMO energy. I only changed dataset-arg and log-dir, otherwise everything is identical to the latest version of your code I think. The command I used is:
CUDA_VISIBLE_DEVICES=0,1 python scripts/train.py --conf examples/ET-QM9.yaml --dataset QM9 --log-dir output/ --dataset-arg homo
I matched the GPU type and count to your paper: I launched over two RTX 2080 Ti's.
However, I only seem to achieve 26 meV for the HOMO test MAE. Do you have any suggestions for what might be differing in my setup compared to yours? Do I need to change any of the other configs in examples/ET-QM9.yaml to train on HOMO? How much variance should I expect across seeds?
Thank you for your help! :slightly_smiling_face:
Sheh

Hi, thank you for the interest in reproducing the results! The HOMO label does not have atomic reference values but the examples/ET-QM9.yaml defines Atomref as the prior model. You can replace this with null to not use any priors. We also set standardize to true for predicting HOMO, which helps the model with convergence. The model's output y is multiplied with the training set's standard deviation and added to its mean as y * std + mean.
Let me know if this resolves the problem!

Closing this for now, feel free to reopen if the problem was not resolved.

Thanks, Philipp! After making those two changes, I do get performance in the right ballpark :slightly_smiling_face:
For the other targets in QM9, when do you use standardization and the prior model? Just wondering what the precise configs need to be to reproduce the results on all QM9 targets.

Perfect! The idea is to make the magnitude of output values "easier" for the network by centering around 0 and having a reasonably small standard deviation. For those targets in QM9 that have atomic reference values, this already does the job and it's even more powerful than our standardization as we can basically have the mean target for each atom type. Therefore, wherever there is an atom ref in QM9, we use that instead of standardizing manually. For the dipole moments and electronic spatial extent, we are using specialized output networks, which do not require standardization. For all other targets (those with default scalar output networks and no atom refs) we use standardization.
That makes:

atom ref prior: energy_U0, energy_U, enthalpy_H, free_energy
standardization: isotropic_polarizability, homo, lumo, gap, zpve, heat_capacity
neither (but special output network): dipole_moment, electronic_spatial_extent

You can set the output network  by setting output_model to something other than Scalar. Currently implemented are the following output modules: Scalar, DipoleMoment, ElectronicSpatialExtent as also indicated when you run python scripts/train.py --help.

authors: PhilippThoelke shehzaidi

repo: torchmd/torchmd-net


text:
volume_type = "standard"

volume_type = "standard"
type should be gp3 or flexible to choose volume_type

This should be fixed after release v1.0.0

source: gharchive/issue

authors: rahulttn rajeshyadavttn

repo: tothenew/terraform-aws-mongodb

license_type: permissive

license_source: github-api


text:
🛑 MSP-Trust is down

In 8c3fb4d, MSP-Trust (https://www.hanatrust.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-Trust is back up in 8091a42 after 8 minutes.

repo: touguy/uptime

license: MIT


text:
Is this repo maintained?

Is there an existing issue for this?

[X] I have searched the existing issues

What kind of documentation would you like added or changed?
It's been a while since the last commit. Just want to understand if this is still being actively maintained.
Why is this needed?
This helps in deciding if we should go ahead with using this repo or look for alternatives that are actively maintained.
Anything else?
That'

hi @pranavchaturved , towhee is still under maintenance, but no new features are being developed.

Thanks for the information.

authors: junjiejiangjjj pranavchaturved

repo: towhee-io/towhee


text:
🛑 Client Setup is down

In cc62814, Client Setup (https://setup.banland.xyz/) was down:

HTTP code: 521
Response time: 131 ms

Resolved: Client Setup is back up in aab7a2a after 26 minutes.

repo: tp-link-extender/status

license: Unlicense


text:
download does not progress

Enviroment:

LanCache 192.168.1.30 running on Unraid
LanCacheDNS 192.168.1.33 running on Unraid
LanCachePrefill running on Unraid

What works:

Steam Prefill works fine
Battle.net Prefill works fine
All gamelaunchers (Epic, steam, EA, battlenet, GoG) work fine on my windows machines and use the LanCache. In the image below you can see the Epic Launcher download Fortnite which goes through the LanCache at the maximum speed of my internet connection (Fornite was not in the LanCache yet)

What does not work:
While I can completelly configure EpicPrefill in both the Unraid Docker as well as the standanlone windows application, the prefill download does not progress and stays at 0% with no network traffic.
The bandwitdh value shown in the Unraid Docker version is "broken" as it shows several Gbps which my internet connection is not capable of - also there is no progress and no drive activity on my LanCache nvme.

The bandwitdh indicator in the windows build is more accurate as there is no traffic.

LanCache Logs:
These are the logs from an attempt to prefill City Skylines
upstream-error.log
error.log
access.log
LanCache_access.log
Games tested with Unraid Prefill docker as well as the windows build:

Cities Skylines - fails/no progress
Fortnite - fails/no progress
Doom 64 - fails/no progress
Enter the Gungeon - fails/no progress
Rise of the Tomb Raider: 20 Year Celebration - fails/no progress

With the Epic Launcher I can download these games, even on the same machine where the EpicPrefill.exe does not produce any download traffic.
Use EpicPrefill on a game that is already in the LanCache

I used the Epic Launcher to download Cities Skylines through the LanCache
then I launched epicprefill.exe selected Cities Skylines and choose Yes to prefill

Result: EpicPrefill.exe "downloads" everything that the EpicLauncher put in the lancache.

This is a firewall/threat detection "problem".
When LanCache prefill is used it connects through "fastly-download.epicgames.com" (as seen in the LanCache prefill logs), this triggers my Firewall and Thread Protection in the UDR Pro SE.

ET USER_AGENTS Suspicious User-Agent (USERAGENT)

When the normal EPIC Client is used to install the exact same game through the LanCache then this does not trigger the Firewall and Threat Detection which I guess is down to the client connecting to a different CDN than "fastly-download.epicgames.com"?
I have now excluded the IP of the LanCache in the Firewall & Threat Detection of my UDM Pro SE and now LanCache prefill works

To add to this, it looks like the user agent defined here might be triggering the filter https://github.com/tpill90/epic-lancache-prefill/blob/master/EpicPrefill/Handlers/DownloadHandler.cs#L21

Released in v1.1.0


text:
Unreal Engine still downloading multiple versions when doing --all

Describe the bug
This is a follow-up to #16. I'm seeing several Unreal Engines being downloaded when doing --all.
Additional Details

Platform you are running EpicPrefill on: docker on linux
Region : EU

Released in v2.0.0


text:
Errors In IntelliJ

Followed the instructions but there are errors in intelliJ I believe they have to do with chromium and selenium

Download Chromium and unzip the .exe in the NVIDIA-RTX-HERO folder.

Also after looking at this again, it looks like the .jars for selenium were not properly imported. There should be two-three jars in the top-level selenium folder that you need to imports, as well as all the jars in the /bin folder.

Oh thanks that was able to resolve most of the errors. Afterwards, I'm supposed to run it right? it gave me a webdriver error, am I supposed to map something?

should i try this?: System.setProperty("webdriver.chrome.driver", "E:\chromedriver.exe");

Put the chromium .exe that you downloaded in the top level rtx-hero folder. That's all you need.

I did, that didnt work
On Fri, Oct 9, 2020 at 4:11 PM tpollard64 notifications@github.com wrote:

Put the chromium .exe that you downloaded in the top level rtx-hero
folder. That's all you need.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tpollard64/Nvidia-RTX-Hero/issues/1#issuecomment-706404174,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE6MANOHOFFTRRONPYPJVLDSJ537NANCNFSM4SJU2CKA
.


text:
Armor status flashing while in First Person mode

The armor status (next to the food bar) is flashing in first person mod, look in record
https://github.com/tr7zw/FirstPersonModel/assets/48128391/87c3e272-fd95-44d1-b97b-607a148b1bce

Am somewhat able to replicate it. It's weird since that would mean the UI gets rendered while the player gets rendered which is never the case. Will have to look into it.


text:
Add "save custom commands" option,show stationary time and create sensors

Hello.
It would be great to be able to save custom commands to the list, for later usage.
Also it would be nice to show in the unit's status windows, for how long is stationary. I believe that this can be accomplished by adding some options for each unit like: Minimum Parking Time, so that you can differ parking from regular stops.
Another option would be to be able to create sensors for units based on incoming parameters. For example Teltonika devices + lv-can, to be able to create mileage sensors, fuel level sensors.....etc.

Saving custom commands is definitely a good idea. I have heard this suggestion before.
Stationary time is probably lower priority.
As for the sensors, if I understand correctly, it's the feature that @Abyss777 is working on. Basically converting incoming raw IO data into something useful.

Yes, is what @Abyss777 is doing. Maybe this will also be useful for adding sensor data to reports, like for example if you have a mileage sensor, you can add Initial and Final Mileage for reports. Or fuel sensors, initial and final...etc.

Currently, for Trip Report odometer and fuel attributes are already used. You'll see not initial/final but difference.

We have had saved commands for a while now.

repo: traccar/traccar-web


text:
Wrong usage of unsafe Vec::from_raw_parts in TensorData

https://github.com/tracel-ai/burn/blob/b29367c1b8763f0e7d81a32c574259d21b33a1f5/crates/burn-tensor/src/tensor/data.rs#L84
This unsafe line has an incorrect usage of Vec::from_raw_parts due to re-interpreting a pointer to some E as a pointer to u8. Note that the docs state in the safety requirements:

T needs to have the same alignment as what ptr was allocated with.

This is because some allocators care about the alignment of these types, hence the buffer that was initially allocated with alignment for the arbitrary (even possibly user-defined) type E will be deallocated with alignment of 1. Some allocators do not care about alignment where this bug does not surface. In any case, miri will complain about this minimal test case:
#[cfg(test)]
#[test]
fn bug() {
    let _ = burn::tensor::TensorData::new(vec![0xdeadu32], [1]);
}

incorrect layout on deallocation: alloc80436 has size 4 and alignment 4, but gave size 4 and alignment 1

Comment: The asserts at the top of the function is pointless, since size_of::<u8>() is guaranteed to return 1.
Comment2: The unconditional truncation of the input vector was a bit surprising - instead of an error due to length mismatch as in the case when the input vector is too short - and made me look closer into the function in the first place ;)

bytemuck has a BoxBytes struct that could contain the allocation in an erased form, but it doesn't implement Clone and Debug.

For now I think all Element types are valid in terms of alignment, making the checks quite useless and confusing.

Wrestling with a fix to this (and being stuck on incompatible serialization), there is one insight: the check does guard against size_of::<E> == 0.

authors: WorldSEnder nathanielsimard

repo: tracel-ai/burn


text:
removed redundant object key definition

an object key that defines "itself" can be written like this:
var pkg = require('./package.json');
{ pkg }

instead of:
var pkg = require('./package.json');
{ pkg : pkg }

This package is quite old and maybe some project which uses it is still on Node version < 4.8.4 (as per node.green, property shorthands are supported from 4.8.4).

Ooohhh. Okay. Good to know. I didn't know property shorthands were a new thing, haha. :D
Well, okay, so I guess this would only cause problems, even if it's just in the readme.
I'll close it.

source: gharchive/pull-request

authors: devfive nnmrts

license: mit

license_source: bigquery


text:
[MB-15409] add a verifyPeerCertificate method to the tlsConfig

DO NOT MERGE

Messages

:book:
:link: MB-15409

  Generated by :no_entry_sign: dangerJS against 26d0f99598c7af80d7feaeb5fc54cb58be09a8c8

authors: chtakahashi robot-mymove

repo: transcom/mymove


text:
Fix issues with go vet with Golang 1.10

Description
When upgrading to Golang 1.10, go vet will fail if identifiers are declared outside the file being "vetted". The correct approach is to use go tool vet against single files. This is explained in more detail here: https://github.com/golang/go/issues/23916
I've forked and patched the pre-commit repo and updated the pre-commit config in this PR.
Additionally, I submitted an upstream patch. Once accepted, we can revert to using that repository.
https://github.com/dnephin/pre-commit-golang/pull/6
Verification Steps

[ ] If you don't have Go 1.10 installed, test that this works by running pre-commit on master:
pre-commit run --all-files
[ ] Upgrade to Go 1.10 and then test the same.

References

go vet issue explained in detail
my pull request to the upstream pre-commit hook provider

@akostibas Is this moot given your PR was accepted on the upstream project?

@brainsik not moot, but I've changed the repo back to the original, with an updated SHA (they haven't cut a new version yet)

authors: akostibas brainsik


text:
Add refresh button to office queue

Description
As office user
I want to be able to refresh my queue
So that I see latest information without reloading whole application
Setup

make server_run
make client_run

Code Review Verification Steps

[x] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] User facing changes have been reviewed by design.
[x] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

Screenshots

Also, probably worth making sure that the dotted-line border is intentional and not just an artifact from design.

@Igarfinkle, I made the adjustment you suggested and I'm also confirming the dotted border with Jenny in design review.


text:
MB-8493-add-search-to-offices-page

Description
Added a search feature to the offices page in the Admin console. An admin user can now log into the console and search for offices by name in the admin page.
Additionally an integration test was created to test the page.
Finally, offficeList.jsx was moved into the pages folder in the codebase to as was the convention for the other pages in the Admin console.
Setup
To run the cypress test
make e2e_test

Select the Offices folder in the popup window and watch the test run.T

To test the feature locally, run the server make server_run and the client make admin_client_run. Then login using the Local Login, and navigate to the Offices page.
References

Jira story for this change

Screenshots

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

Messages

:book:
:link: MB-8493

  Generated by :no_entry_sign: dangerJS against 696b64960b971da2651746ef385747355f31d9c7

LGTM! Thanks for making those changes!

Absolutely! I learned a lot because of your feedback. Thank you!

authors: NamibiaTorres robot-mymove


text:
[MB-14210] adding ppm closeout param to BE

I don't think this works right yet, and will probably want to rename the query param
Jira ticket for this change
Summary
Is there anything you would like reviewers to give additional scrutiny?
this article explains more about the approach used.
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Access the
Login as a

Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-14210

  Generated by :no_entry_sign: dangerJS against d7dc60e0c1b88a4bd435c128927884a94a0f2e00

authors: mboren robot-mymove


text:
Context menu button to translate some element

Usage:

Open context menu and press button "Translate element" (also this button available in popup)
Enabled picker mode on page
When user pick element, it start translates
Page status changed to "partial translation" which is sub status of "translation"
When user pick translated element, it stop translation
When user press button "Disable page translation", all elements translations are reset
This feature must have a hotkey

Maybe if user click context menu by element, we should render option to translate selected element.

repo: translate-tools/linguist


text:
🛑 TechinAsia_WordPress_API is down

In 938e7e9, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 231 ms

Resolved: TechinAsia_WordPress_API is back up in 3358118 after 9 minutes.

repo: traqy/upptime


text:
🛑 TechinAsia is down

In ac1c443, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 988 ms

Resolved: TechinAsia is back up in 0108c48 after 7 minutes.


text:
🛑 TechinAsia is down

In 9751198, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 998 ms

Resolved: TechinAsia is back up in 1b30249 after 8 minutes.


text:
🛑 TechinAsia_WordPress_API is down

In eda2f0a, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 172 ms

Resolved: TechinAsia_WordPress_API is back up in 7d09454 after 7 minutes.


text:
🛑 TechinAsia_WordPress_API is down

In d1c0741, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 172 ms

Resolved: TechinAsia_WordPress_API is back up in 594e6a7 after 7 minutes.


text:
🛑 TechinAsia_Laravel_API is down

In f73458b, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 230 ms

Resolved: TechinAsia_Laravel_API is back up in 4a1e34b after 14 minutes.


text:
🛑 TechinAsia is down

In f030eb4, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 928 ms

Resolved: TechinAsia is back up in 5d45ba7 after 10 minutes.


text:
🛑 TechinAsia is down

In daad4af, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 747 ms

Resolved: TechinAsia is back up in 33309bc after 9 minutes.


text:
Update repository URL for Crystal shards

The repository moved and Github issues no redirect here.
closes travis-ci/travis-ci#5712
/cc @asterite @waj @will

Looks good

Definitely :+1:

authors: asterite jhass will

repo: travis-ci/travis-build


text:
Fix some jsonDouble unlawfulness

For example, before this change:
scala> import io.circe.{ Json, JsonNumber }
import io.circe.{Json, JsonNumber}

scala> import io.circe.optics.JsonOptics.jsonDouble
import io.circe.optics.JsonOptics.jsonDouble

scala> jsonDouble.getOption(jsonDouble.reverseGet(Double.NaN))
res0: Option[Double] = None

scala> val json = Json.fromJsonNumber(JsonNumber.fromString((BigDecimal(Double.MaxValue) + 1).toString).get)
json: io.circe.Json = ...

scala> jsonDouble.getOrModify(json).fold(identity, jsonDouble.reverseGet)
res1: io.circe.Json = 1.7976931348623157E308

scala> json == res1
res2: Boolean = false

This is another issue turned up by #400, but I've also added two tests specifically for the corner cases that previously broke the laws.

Current coverage is 81.05% (diff: 100%)

Merging #406 into master will increase coverage by 0.19%

@@             master       #406   diff @@
==========================================
  Files            63         63
  Lines          1996       2001     +5
  Methods        1841       1845     +4
  Messages          0          0
  Branches        155        156     +1
==========================================
+ Hits           1614       1622     +8
+ Misses          382        379     -3
  Partials          0          0

Powered by Codecov. Last update 947ba2e...ed3ea5b

authors: codecov-io travisbrown

repo: travisbrown/circe


text:
YAML export escapes newlines

Using 0.1.1:
@ YamlConverter.toYamlString(parse(""" { a = "\n" } """).normalize())
res15: String = """a: \n
"""

@ JsonConverter.toCompactString(parse(""" { a = "\n" } """).normalize())
res16: String = "{\"a\":\"\\n\"}"

THe JSON output is correct, but in the YAML output, the value does not contain a newline (without quotes, \n is not an escape sequence).

Thanks, taking a look now!

I really need to just go ahead and address #11 properly. Sorry you're running into these issues—thanks for reporting them.

authors: amesgen travisbrown

repo: travisbrown/dhallj


text:
腾讯劈谣网页版微信不停止服务

腾讯劈谣网页版微信不停止服务

http://epaper.bjbusiness.com.cn/site1/bjsb/html/2017-11/28/content_386122.htm
帮你补个链接，是我能找到的新闻源。但是只有简单的一句话：
“不过，腾讯方面对北京商报记者表示，微信网页版没有关闭。”

还以为要GG呢，那就继续搞了😂

@sxft1978 我的号就被封了不能用网页版，打电话找了客服，客服说要下架，逐步下架，莫非我问了个假客服？这网页版不能用真的是非常影响工作:rage:

authors: Iamanorange aforwardz sxft1978 trazyn

repo: trazyn/weweChat


text:
JS报错找不到todayDate()

BUG描述
配置禁用某一天之前/之后的所有日期时，JS报错找不到todayDate()，自行研究后发现components\calendar\utils\index.js内确无此函数，而todayFMD()似乎可以起到应有的效果
calendarConfig: {       theme: 'elegant',       multi: true,       firstDayOfWeek: 'Mon',       disableMode: {         // 禁用某一天之前/之后的所有日期         type: 'before', // [‘before’, 'after']         date: false// 无该属性或该属性值为假，则默认为当天       },     },
即将components\calendar\index.js中setDefaultDisableDate()部分的dateUtil.todayDate()更改为dateUtil.todayFMD()，问题解决
截图

对了是V2版本

不好意思，迁移过程中遗漏了这个，造成了错误，我修复一下

authors: cqlicheng treadpit


text:
Pin Node version to 11

See https://github.com/tree-sitter/node-tree-sitter/issues/46#issuecomment-497458521
and https://github.com/mads-hartmann/bash-language-server/issues/131#issuecomment-504308706

🎩 @KevOrr for this: much appreciated!

Fixed the build errors… now we’re getting some test failures of uncertain provenance.

Okay, the issue here is that on my macOS install, the .phpt tests are not recognized if there’s a file extension .001.phpt. We have to change that leading dot to an underscore. I have no idea why this is happening.

repo: tree-sitter/tree-sitter-php


text:
Access control credentials GUI sort

Currently, the credentials under the GUI Administration tab are sorted alphabetically by their ID.
It should be possible to choose how the credentials are sorted, and the default should probably be by date.

Hi @Jonathan-Rosenberg,
I'd like to take this up!
Is the expectation to sort the credentials from earliest to oldest?

Hey @rishiravikumar-tul-scm , thanks for taking this one!
I agree with your suggestions, the newer creds should be on top.

repo: treeverse/lakeFS


text:
3141- fixing the why section to include more descriptive

3141

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Adi Polak seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks! Updated according to suggestions :)

authors: CLAassistant adipolak


text:
Update README.md

Addition of table of content and contributing section

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks!
Our main page lakefs.io should already include a table of contents. It gets auto-generated from this file. So for the time being we shall not be accepting changes that manually add a table of contents.

authors: CLAassistant arielshaqed rishabh710


text:
Lab_isaacparada.md

Isaac Parada's lab report for CIS 411
@trevordbunch
@hallienicholas

This is my redone assignment @trevordbunch


text:
New google api

This fixes #4
@trevore Before merging this request, please test the branch I created. I think the functionality is complete and correct, but it needs more testing.
In order to fully test, you'll need a valid client_secrets.json file. I'll put it up on Drive and email it to you, but the documentation needs to be updated on how to get the file. We can discuss here.
Also, before merge, the user/password options need to be removed.

I've done some additional testing and documentation. Since the old API has officially been cut off as of now, I'm going to merge this.

repo: trevore/galias


text:
Keep the sort in edit source mode

Is your feature request related to a problem? Please describe.
When I sort by a column, the sort is not preserved into the original table in edit mode (source mode).
Describe the solution you'd like
make the sort permanent across views

Completely fixed in 1.0.0

repo: trey-wallis/obsidian-notion-like-tables


text:
Fix running command line with more than a single word under MSW

Split command line into arguments when passing it to cmd.exe, respecting
quotes (but not anything else for now).
Closes #18.

Sorry for my baby Nim, I'm pretty sure this could be done in some better way, but at least this works for me (in fact, I'm writing this text in Vim, opened from Firefox) and is already an improvement.

Thanks for this.
I'm really reluctant to merge this because I can see loads of edge cases - escaped quotes, nested quotes - that will cause weird behaviour.
I don't think it should be too difficult to do it "properly", e.g. with os.quoteShell or the dumb "prepend command with cmd /c and then do the same as we do in Linux" I suggested.
If we can't do that then, yeah, I agree that this is better than the current situation for users.

Thanks for this.
I'm really reluctant to merge this because I can see loads of edge cases - escaped quotes, nested quotes - that will cause weird behaviour.
I don't think it should be too difficult to do it "properly", e.g. with os.quoteShell or the dumb "prepend command with cmd /c and then do the same as we do in Linux" I suggested.
If we can't do that then, yeah, I agree that this is better than the current situation for users.

I presume this would break with things like somecommand "foo """bar"""". While I think you're just asking to suffer once you start trying to fight cmd's quoting rules, this still wouldn't be backwards compatible with the old messenger, then.
On another note, I did some googling again and I think poEvalCommand doesn't mean "shell" to refer to cmd, but the thing that pre-processes and constructs argv, which has another different set of rules. I think that's what os.quoteShell is meant for and what startProcess directly passes its command to when poEvalCommand is used.
All of this is of course under the assumption that I even understand anything here correctly, which I'm not sure about.

I presume this would break with things like somecommand "foo """bar"""". While I think you're just asking to suffer once you start trying to fight cmd's quoting rules, this still wouldn't be backwards compatible with the old messenger, then.
On another note, I did some googling again and I think poEvalCommand doesn't mean "shell" to refer to cmd, but the thing that pre-processes and constructs argv, which has another different set of rules. I think that's what os.quoteShell is meant for and what startProcess directly passes its command to when poEvalCommand is used.
All of this is of course under the assumption that I even understand anything here correctly, which I'm not sure about.

I'm really reluctant to merge this because I can see loads of edge cases - escaped quotes, nested quotes - that will cause weird behaviour.

I could add support for using backslashes to escape quotes, if it could help.

I don't think it should be too difficult to do it "properly", e.g. with os.quoteShell or the dumb "prepend command with cmd /c and then do the same as we do in Linux" I suggested.

quoteShell() seems to work in the other direction, i.e. it takes a single argument and quotes it if necessary. We need to split a string into arguments here and AFAICS Nim doesn't provide any support for this. As for cmd /c, isn't this what we already do? If not, could you please explain what do you mean?
Anyhow, I'd just like to emphasize that the current version, which passes the entire string of the command as a single elements of args is broken. This string must be split into individual arguments in some way.

I'm really reluctant to merge this because I can see loads of edge cases - escaped quotes, nested quotes - that will cause weird behaviour.

I could add support for using backslashes to escape quotes, if it could help.

I don't think it should be too difficult to do it "properly", e.g. with os.quoteShell or the dumb "prepend command with cmd /c and then do the same as we do in Linux" I suggested.

quoteShell() seems to work in the other direction, i.e. it takes a single argument and quotes it if necessary. We need to split a string into arguments here and AFAICS Nim doesn't provide any support for this. As for cmd /c, isn't this what we already do? If not, could you please explain what do you mean?
Anyhow, I'd just like to emphasize that the current version, which passes the entire string of the command as a single elements of args is broken. This string must be split into individual arguments in some way.

On Linux we use poEvalCommand which doesn't do any escaping. I'm suggesting that we do the same thing on Windows, which is what we did initially, but add cmd /c to the start of the command.
The reason we stopped using it on Windows is because poEvalCommand dumps you in a shell without any built-ins (e.g. which).
With poEvalCommand you give startProcess a single string and don't use the arguments array.
I think you're probably right and quoteshell does the opposite of what we want...
PGP - 2BB8 C36B B504 BFF3 - https://keybase.io/bovine3dom/key.asc
On 24 January 2021 14:58:56 CET, VZ notifications@github.com wrote:

I'm really reluctant to merge this because I can see loads of edge
cases - escaped quotes, nested quotes - that will cause weird
behaviour.

I could add support for using backslashes to escape quotes, if it could
help.

I don't think it should be too difficult to do it "properly", e.g.
with os.quoteShell or the dumb "prepend command with cmd /c and then
do the same as we do in Linux" I suggested.

quoteShell() seems to work in the other direction, i.e. it takes a
single argument and quotes it if necessary. We need to split a string
into arguments here and AFAICS Nim doesn't provide any support for
this. As for cmd /c, isn't this what we already do? If not, could you
please explain what do you mean?
Anyhow, I'd just like to emphasize that the current version, which
passes the entire string of the command as a single elements of args
is broken. This string must be split into individual arguments in some
way.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tridactyl/native_messenger/pull/20#issuecomment-766352447

On Linux we use poEvalCommand which doesn't do any escaping. I'm suggesting that we do the same thing on Windows, which is what we did initially, but add cmd /c to the start of the command.
The reason we stopped using it on Windows is because poEvalCommand dumps you in a shell without any built-ins (e.g. which).
With poEvalCommand you give startProcess a single string and don't use the arguments array.
I think you're probably right and quoteshell does the opposite of what we want...
PGP - 2BB8 C36B B504 BFF3 - https://keybase.io/bovine3dom/key.asc
On 24 January 2021 14:58:56 CET, VZ notifications@github.com wrote:

I'm really reluctant to merge this because I can see loads of edge
cases - escaped quotes, nested quotes - that will cause weird
behaviour.

I could add support for using backslashes to escape quotes, if it could
help.

I don't think it should be too difficult to do it "properly", e.g.
with os.quoteShell or the dumb "prepend command with cmd /c and then
do the same as we do in Linux" I suggested.

quoteShell() seems to work in the other direction, i.e. it takes a
single argument and quotes it if necessary. We need to split a string
into arguments here and AFAICS Nim doesn't provide any support for
this. As for cmd /c, isn't this what we already do? If not, could you
please explain what do you mean?
Anyhow, I'd just like to emphasize that the current version, which
passes the entire string of the command as a single elements of args
is broken. This string must be split into individual arguments in some
way.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tridactyl/native_messenger/pull/20#issuecomment-766352447

If all else fails, we could use _popen or _wpopen – probably the latter, for Unicode support –, but that'd mean more and even uglier platform-specific code.

If all else fails, we could use _popen or _wpopen – probably the latter, for Unicode support –, but that'd mean more and even uglier platform-specific code.

OK, I can confirm that using poEvalCommand works as well, please see #21, thanks for the idea.

OK, I can confirm that using poEvalCommand works as well, please see #21, thanks for the idea.

authors: Rummskartoffel bovine3dom vadz


text:
bug: TypeScript type reduced to 'never' (GitHub integration)

Provide environment information
System:
OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700K
Memory: 6.85 GB / 9.71 GB
Container: Yes
Shell: 5.8 - /usr/bin/zsh
Binaries:
Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
Yarn: 1.22.19 - ~/.yarn/bin/yarn
npm: 9.6.7 - ~/.nvm/versions/node/v18.17.1/bin/npm
pnpm: 8.10.4 - ~/.local/share/pnpm/pnpm
bun: 1.0.0 - ~/.bun/bin/bun
Describe the bug
Trying to use the GitHub integration and saw this error appear.  This happens when trying to access anything on the issue property.

Property 'number' does not exist on type 'never'.
  The intersection 'Issue & { state: "open"; closed_at: null; }' was reduced to 'never' because property 'closed_at' has conflicting types in some constituents.

Reproduction repo
N/A
To reproduce
Create a new job with a GitHub integration, and attempt to use a method that relies on Issue type.
Additional information
No response

Thanks for reporting this!
Your tsconfig needs to have strict or at the very least strictNullChecks enabled for types to work as they should. They come straight from Octokit.
Reproduction:

Fails with strictNullChecks disabled
Works with strictNullChecks enabled

Thanks for reporting this!
Your tsconfig needs to have strict or at the very least strictNullChecks enabled for types to work as they should. They come straight from Octokit.
Reproduction:

Fails with strictNullChecks disabled
Works with strictNullChecks enabled

Ah, that did it! Yeah, I had stricky: true but strictNullChecks: false. Flipping that did the job 🎉

authors: jaaneh nicktrn


text:
Add possibility to configure AWS endpoint in SQS source

Closes #235
Allows overriding the default AWS API endpoint (http://...amazonaws.com) with a custom endpoint URL, which allows users of this event source to target alternative API-compatible implementations such as ElasticMQ or Localstack.

Demo
Prerequisite: Localstack running in the same Kubernetes cluster as the source. (I used their Helm chart)
Create a queue:
$ aws sqs create-queue --queue-name foo --endpoint=http://host.docker.internal:31566
{
    "QueueUrl": "http://localhost:31566/000000000000/foo"
}

Create a source instance for this queue:
apiVersion: sources.triggermesh.io/v1alpha1
kind: AWSSQSSource
metadata:
  name: sample
spec:
  arn: arn:aws:sqs:eu-central-1:000000000000:foo

  credentials:
    accessKeyID:
      value: admin
    secretAccessKey:
      value: hunter2

  # This was added in this PR
  endpoint:
    url: http://localstack.localstack:4566

  sink:
    ref:
      apiVersion: v1
      kind: Service
      name: event-display

Ensure it becomes Ready:
$ kubectl get awssqssource/sample
NAME     READY   REASON   SINK                                             AGE
sample   True             http://event-display.default.svc.cluster.local   19m

Send a message:
$ aws sqs send-message --queue-url http://localhost:31566/000000000000/foo --endpoint http://localhost:31566 --message-body test
{
    "MD5OfMessageBody": "098f6bcd4621d373cade4e832627b4f6",
    "MessageId": "3b0db203-468f-f081-83a6-428523f4a028"
}

WIN:
☁  cloudevents.Event
Context Attributes,
  specversion: 1.0
  type: com.amazon.sqs.message
  source: arn:aws:sqs:eu-central-1:000000000000:foo
  id: 3b0db203-468f-f081-83a6-428523f4a028
  time: 2021-11-04T15:56:39.3001906Z
  datacontenttype: application/json
Data,
  {
    "Attributes": {
      "ApproximateFirstReceiveTimestamp": "1636041399269",
      "ApproximateReceiveCount": "1",
      "SenderId": "AIDAIT2UOQQY3AUEKVGXU",
      "SentTimestamp": "1636041399268"
    },
    "Body": "test",
    "MD5OfBody": "098f6bcd4621d373cade4e832627b4f6",
    "MD5OfMessageAttributes": null,
    "MessageAttributes": null,
    "MessageId": "3b0db203-468f-f081-83a6-428523f4a028",
    "ReceiptHandle": "tliyexekijnvvxscuaoefvbsmgzydwgskceytntklpgaajkebzemdauxchkoufmwnvfbqbiahpgvrmjqgrxyqjyzsxxalrncsyppejazmtpjikarwysuwrodvgngblagxsagzaqertdpfzfkfozjssnrgdzecuxtvsktjyiabdeibbwxqairvnqtb"
  }

Very cool! Nice addition!

authors: JeffNeff antoineco

repo: triggermesh/triggermesh


text:
Item class refactoring to avoid object slicing

Using Q_DISABLE_COPY

Download:
Environment: QT=5.12, ARCH=32, CONFIGURATION=release, QTIFW=C:\Qt\Tools\QtInstallerFramework\3.1

Download:
Environment: QT=5.12, ARCH=32, CONFIGURATION=release, QTIFW=C:\Qt\Tools\QtInstallerFramework\3.1

authors: AppVeyorBot khodand

repo: trikset/trik-studio


text:
Add lunarvim

Added Lunarvim since it feels like it belongs here.

@Ogioer
It says you approved the request but this PR is still blocked pending review.

repo: trimstray/the-book-of-secret-knowledge


text:
Recharge at the end of turn feature disappeared with 2.0

The previously implemented feature that allowed you to recharge abilities (like a dragon's breath weapon or a mind flayer's mind blast) appears to be gone, or at least inaccessible via the settings.

Fixed in 2.0.1


text:
Why the outputTokensPerSecond is much smaller than Fastertransformer?

I have used Triton Server + FT in the past, and now I use Triton Server + TensorRT-LLM with inflight-batching, but the  outputTokensPerSecond between them  having a big gap.
max_new_tokens: 256
tp: 4
model: codeLlama-7b

The Triton Server of TensorRT-LLM is:
nvcr.io/nvidia/tritonserver:23.10-trtllm-python-py3

The configurations of TensorRT-LLM is:
https://github.com/triton-inference-server/tensorrtllm_backend/tree/release/0.5.0/all_models/inflight_batcher_llm

Builds TensorRT engine(s) from HF is:
python build.py --model_dir ./META-CodeLlama-7b-hf/  \
                --dtype float16 \
                --remove_input_padding \
                --use_gpt_attention_plugin float16 \
                --paged_kv_cache \
                --use_inflight_batching \
                --enable_context_fmha \
                --use_gemm_plugin float16 \
                --output_dir /tensorrtllm_backend/trt_llama_7b_fp16/4-gpu/  \
                --world_size 4 \
                --tp_size 4

and the outputTokensPerSecond is as following:
FT: 1800
TensorRT-LLM: 470

This difference is so weird, I don’t know what the problem is.

Can you share how to reproduce the performance number you get? Which file do you use and what script do you use? It would be helpful to provide clear reproduced steps to help reproducing the issue.

Can you share how to reproduce the performance number you get? Which file do you use and what script do you use? It would be helpful to provide clear reproduced steps to help reproducing the issue.

@byshiue OK, I will try to give more details soon, but one key point is that the "batch_size" I use is 1.
In fact, I also use benchmark of TensorRT-LLM to test, but the result is even worse.
https://github.com/NVIDIA/TensorRT-LLM/blob/release/0.5.0/benchmarks/python/README.md

And I use the flowing command for test:
mpirun --allow-run-as-root -n 4 python benchmark.py \
    -m llama_7b \
    --mode plugin \
    --batch_size "1" \
    --input_output_len "500,200"

The tokenPerSecond is only 91. Is there sth wrong?

I am not sure is tokenPerSecond 91 reasonable or not because I am not sure how do you compute the tokenPerSecond (is it including the input + output? or is it only including output), and I don't understand your network topology and hardward settings, which are important for tensor parallelism.

I am not sure is tokenPerSecond 91 reasonable or not because I am not sure how do you compute the tokenPerSecond (is it including the input + output? or is it only including output), and I don't understand your network topology and hardward settings, which are important for tensor parallelism.

@byshiue

Thank you for the response. The tokens_per_sec in benchmark.py is computed by bs * output_len / second. In such scenario, tokens_per_sec 95 looks reasonable for me under batch size 1.
You can try using larger batch size to increase the throughput.

Thank you for the response. The tokens_per_sec in benchmark.py is computed by bs * output_len / second. In such scenario, tokens_per_sec 95 looks reasonable for me under batch size 1.
You can try using larger batch size to increase the throughput.

@byshiue Thanks for your quick reply, in fact, I have tested with larger batch size, and the largest one of tokens_per_sec is 1129.

But I have a question, when I use endpoint to request with inflight-batching mode, just like this
curl -X POST localhost:8000/v2/models/${MODEL_NAME}/generate -d '{"{PARAM1_KEY}": "{PARAM1_VALUE}", ... }'

and the max_batch_size is 128, tp is 4, will the throughput increase as expected?

I expect. Do you have any concern?

I expect. Do you have any concern?

@byshiue I will just do more tests then, but I found that when building engines, there is a parameter named "max_batch_size", in my opinion, it is so wired, why we have to set a value now?
And if I set "max_batch_size" value to 8, but in config.pbtxt the value is 128, what will happen? Will the real "max_batch_size" is 8?
What's more, if I set "max_batch_size" value to 128, but in config.pbtxt the value is 64, what will happen? Will the real "max_batch_size" is 64? Or it will be error?
https://github.com/NVIDIA/TensorRT-LLM/blob/11e14500f35dd781b535ba009c906f55ecfee3b5/examples/llama/build.py#L158C6-L158C6

The max_batch_size in config.json is a hyper-parameter for the engine, which means the maximum batch size supported by this engine. It is used to compute the workspace we need during inference.
The max_batch_size in config.pbtxt of backend means the maximum batch size of request you will recieve and send to server.
So, when the batch_size you send to server is larger than the max_batch_size of config.json of engine, it is invalid and should be throw error.

The max_batch_size in config.json is a hyper-parameter for the engine, which means the maximum batch size supported by this engine. It is used to compute the workspace we need during inference.
The max_batch_size in config.pbtxt of backend means the maximum batch size of request you will recieve and send to server.
So, when the batch_size you send to server is larger than the max_batch_size of config.json of engine, it is invalid and should be throw error.

@byshiue Thank u so much for your detailed answer, I learnt a lot.
I just set max_batch_size value to 64 in config.json, and I test the tokens_per_sec in our own way, and the current indicator seems to be on par with vLLM, it's about 1,000, which I think is within expectations.
Thank u again for help.

@activezhao Thank you for the update. It looks your issue is solved. Close this bug. Feel free to repoen it if needed.

authors: activezhao byshiue


text:
Boundary integration of viscous forces

Building upon #1812 this PR adds the viscous drag and lift coefficients due to shear stress.
For the viscous NACA0012 test (changed elixir) we match the values given in https://doi.org/10.1016/j.amc.2017.07.020
for the viscous drag coefficient very well:
Reference: 1.275e−01, Trixi: 1.24758705e-01
For viscous lift:
Reference: −3.945e−03 Trixi: -5.66376473e-03
@Arpit-Babbar please have a look!

Hm, Aqua.jl errors with
Unbound type parameters detected:
[1] analyze(quantity::Union{typeof(enstrophy), AnalysisSurfaceIntegral{Semidiscretization, Variable}}, du, u, t, semi::SemidiscretizationHyperbolicParabolic) where {Semidiscretization, Variable<:VariableViscous}
@ Trixi ~/work/Trixi.jl/Trixi.jl/src/callbacks_step/analysis.jl:685
Unbound type parameters: Test Failed at /home/runner/.julia/packages/Aqua/9p8ck/src/unbound_args.jl:28
  Expression: isempty(unbounds)
   Evaluated: isempty(Method[analyze(quantity::Union{typeof(enstrophy), AnalysisSurfaceIntegral{Semidiscretization, Variable}}, du, u, t, semi::SemidiscretizationHyperbolicParabolic) where {Semidiscretization, Variable<:VariableViscous}
@ Trixi ~/work/Trixi.jl/Trixi.jl/src/callbacks_step/analysis.jl:685])

See
https://docs.juliahub.com/Aqua/Hav67/0.8.4/unbound_args/#Unbound-Type-Parameters

I added CI tests. Ready to go from my side, the open comments are meant to be explanatory for the reviewers.

Hm, I do not understand why the testcase does not do the timestepping: https://github.com/trixi-framework/Trixi.jl/actions/runs/8569475328/job/23485450223?pr=1893#step:8:7498 :thinking:
Locally this runs perfectly fine, but in the CI not a single timestep is taken

Could it be the same issue as this - #1812 (review)
The solution is given by Joshua below.

Ah yeah good idea, let's see what happens!


text:
WIP: Merge Taal into master

This PR will track the overall development of Taal (Trixi as a library). Separate work packages will be implemented in PRs into the dev branch until we're ready to merge into master.
Here is our TODO list from #187
TODO

[x] basic infrastructure, semidiscretizations etc.
[x] Euler + gravity
[x] weak form
[x] split form
[x] shock capturing
[x] boundary conditions
[x] non-conservative terms (MHD)
[x] restarts (tracked in #271)
[x] SummaryCallback
[x] AMRCallback
[x] AMRCallback for Euler + gravity
[x] StepsizeCallback
[x] AnalysisCallback
[x] SaveSolutionCallback
[x] AliveCallback
[ ] make it easier to create new callbacks by hiding some DiffEq-specific stuff? (tracked in #261)
[ ] add a "default I/O" callback (or method that returns something like it) that creates a SummaryCallback, AliveCallback, AnalysisCallback, and SaveSolutionCallback with sane defaults and keyword arguments for all relevant arguments (tracked in #261)
[x] positivity preservation (tracked in #270, implemented in #274)
[x] SteadyStateCallback stuff for hyperbolic diffusion
[x] trixi_include with the ability to modify stuff in the REPL via keyword arguments
[ ] make polydeg an explicit parameter in order to be able to modify it via keyword arguments in trixi_include
[x] move definitions of abstract types to abstract_types.jl to enable dispatch on them throughout Trixi.jl
[ ] allow different real types for the mesh and all other data structures
[ ] ensure that we have enough flexibility in the caches to enable AD (tracked in #260)
[x] elixir: linear structure
[x] elixir: Jacobian using FD (#262)
[ ] elixir: fluctuation stuff (tracked in #269)
[x] elixir: convtest
[ ] migrate every test case (tracked in #219)
[ ] update docs and README
[x] more inline documentation and explanations
[x] consistent naming of Vector-like u from DiffEq.jl and "our" solution array u and documentation/explanation of wrap_array
[ ] consistent use of return, update the dev docs accordingly
[x] consistent  and descriptive naming of the examples; elixir_eqs_specification.jl in general, e.g. elixir_advection_basic.jl instead of parameters.jl.
[ ] We need to rename parameters_file (and everything else where parameters occurs) to elixir or something similar.
[x] Add one non-DiffEq implemention for a RK scheme (e.g. Carpenter/Kennedy LSRK45) for easy experimenting/prototyping (#272)
[ ] fix all remaining # TODO: Taal
[x] 1D
[x] 2D
[x] 3D (#255)
[x] Merge MPI from master into dev and resolve conflicts, make everything work, ...
[ ] remove all old code not needed in Taal anymore

Connections to issues
Xref #185 #161 #150 #70 #19
Closes #197; closes #177; closes #176; closes #173; closes #142 (obsolete); closes #139; closes  #136 (obsolete); closes #98; closes #83; closes #74 (obsolete); closes #73; closes #10
Blocked by #207, #219, ~#233~, #236, ~#240~, #243, #267, #287 (i.e., do not merge before these are resolved or removed from this list).

examples/2d/elixir_mhd_rotor_shockcapturing_amr.jl fails again - why?


text:
🛑 TronFlix is down

In 21d04b6, TronFlix (https://tronflix.app) was down:

HTTP code: 520
Response time: 244 ms

Resolved: TronFlix is back up in c685650.

repo: tronyx/upptime


text:
🛑 Bazarr is down

In 4a04b95, Bazarr (https://tronflix.app/bazarr/system/status) was down:

HTTP code: 302
Response time: 227 ms

Resolved: Bazarr is back up in 05106f5 after 10 minutes.


text:
🛑 XBackBone is down

In 9117b88, XBackBone (https://sharex.tronflix.app) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XBackBone is back up in dbcc7a1.


text:
Copy 001_configure_ipfs.sh in Dockerfile

As there is only one config file used for both daemons, it can be considered the default configuration? That said... can we make a COPY instruction for the file in Dockerfile?

The second daemon uses another config file.
The configuration applied via the first file really only works in the given docker-compose setup, because it references the AMQP server. Also, setting kubo to have unlimited connection capacity is not what most people want. Maybe not even what most people using this plugin want: We have functionality to broadcast requests on Bitswap, which does not work with large nodes anymore (unfortunately).
So, that being said, I don't think I'd want that as the default config. We provide stock kubo with our plugin as an image, and as such I'd want it to behave like stock kubo.

Hmm okay. I wanted to find a way to work around having to carry those config files/ a git submodule to your repo. But now I see there are even more to configure to RabbitMQ. So it doesn't matter anyway.

repo: trudi-group/ipfs-metric-exporter


text:
chlamydate, apotelesmatic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,c]

/trunk merge

repo: trunk-io/mergequeue-staging


text:
erymanthian, cellarets

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,e]

/trunk merge


text:
floretum, duci

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,f]

/trunk merge


text:
callouses, appropriate

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,c]

/trunk merge


text:
arcticologist, canzonets

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,c]

/trunk merge


text:
coiled, emphatic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,e]

/trunk merge


text:
desulphur, gravitative

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,g]

/trunk merge


text:
evulgate, appurtenance

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,e]

/trunk merge


text:
dents

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d]

/trunk merge


text:
collaborationist, butted

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,c]

/trunk merge


text:
dilutor, entad

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,e]

/trunk merge


text:
floatiest, aletocyte

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,f]

/trunk merge


text:
archive, foetalism

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,f]

/trunk merge


text:
cogware, erstwhiles

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,e]

/trunk merge


text:
gulonic, doorjamb

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,g]

/trunk merge


text:
correption, frankheartedness

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,f]

/trunk merge


text:
elargement, dicrotous

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,e]

/trunk merge


text:
aberia, epigamic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,e]

/trunk merge


text:
fluidize

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[f]

/trunk merge


text:
craves, dogblow

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,d]

/trunk merge


text:
bejewels

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b]

/trunk merge


text:
electrophilically, chinas

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[c,e]

/trunk merge


text:
buggery, capillarectasia

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,c]

/trunk merge


text:
filmmake, archtyrant

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,f]

/trunk merge


text:
fermata, ascidiate

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,f]

/trunk merge


text:
cohering, deoxidation

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,d]

/trunk merge


text:
antimystically, collossians

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,c]

/trunk merge


text:
ferroinclave, deputed

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,f]

/trunk merge


text:
deemed, eyehook

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,e]

/trunk merge


text:
aphanites, forelouper

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,f]

/trunk merge

repo: trunk-io/mergequeue


text:
asporous, dimensioned

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,d]

/trunk merge


text:
basiated, france

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,f]

/trunk merge


text:
cairds, forcipal

This pull request was generated by the 'mq' tool

/trunk merge


text:
boussingaultia, aspirations

This pull request was generated by the 'mq' tool

/trunk merge


text:
dysgonic

This pull request was generated by the 'mq' tool

/trunk merge


text:
discretiveness, crystallogeny

This pull request was generated by the 'mq' tool

/trunk merge


text:
flashlamps, blackish

This pull request was generated by the 'mq' tool

/trunk merge


text:
fireboats, buffalofishes

This pull request was generated by the 'mq' tool

/trunk merge


text:
acclaims, diazenithal

This pull request was generated by the 'mq' tool

/trunk merge


text:
fontinalis, daughterhood

This pull request was generated by the 'mq' tool

/trunk merge


text:
balkanizing

This pull request was generated by the 'mq' tool

/trunk merge


text:
dropper, echeneid

This pull request was generated by the 'mq' tool

/trunk merge


text:
baryphony

This pull request was generated by the 'mq' tool

/trunk merge


text:
espichellite, anisalcohol

This pull request was generated by the 'mq' tool

/trunk merge


text:
gallicola, febres

This pull request was generated by the 'mq' tool

/trunk merge


text:
benzoate, cribber

This pull request was generated by the 'mq' tool

/trunk merge


text:
cack, glaces

This pull request was generated by the 'mq' tool

/trunk merge


text:
duckbills

This pull request was generated by the 'mq' tool

/trunk merge


text:
enamellist, flubdubberies

This pull request was generated by the 'mq' tool

/trunk merge


text:
ensnarling, asiatical

This pull request was generated by the 'mq' tool

/trunk merge


text:
capillarimeter, followed

This pull request was generated by the 'mq' tool

/trunk merge


text:
astrobiologically

This pull request was generated by the 'mq' tool

/trunk merge


text:
belauder, germicides

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b,g]

/trunk merge


text:
acutilinguae, gcd

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,g]

/trunk merge


text:
blather

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b]

/trunk merge


text:
formfeeds, gentlewomanliness

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[f,g]

/trunk merge


text:
electrodialysis, arrested

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,e]

/trunk merge


text:
chromoscopic, gaullism

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,g]

/trunk merge


text:
conformation, etuvee

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,e]

/trunk merge


text:
gloiopeltis, eyelid

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[e,g]

/trunk merge


text:
demoniacs

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[d]

/trunk merge


text:
disilicate, cocoanuts

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,d]

/trunk merge


text:
geochronometry, diallelon

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[d,g]

/trunk merge


text:
dicyandiamide, cammocky

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,d]

/trunk merge


text:
dehusk, bufidin

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,d]

/trunk merge


text:
fluctisonant, americanizer

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,f]

/trunk merge


text:
caliperer, exceptant

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,e]

/trunk merge


text:
dysprosium, agrege

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,d]

/trunk merge


text:
crystallophobia, blaeness

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,c]

/trunk merge


text:
conjurors, guffy

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,g]

/trunk merge


text:
ganda, braying

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,g]

/trunk merge


text:
adulterer, chocker

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,c]

/trunk merge


text:
brollies, derepress

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,d]

/trunk merge


text:
barras, glyster

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,g]

/trunk merge


text:
Accept next Fractal tokens until they are received

This lets the user:

"Connect to Fractal" while not logged in
Log in
Extension is connected when loading the Fractal page

Let me submit this. I need to think through implications.

Let me submit this

I'm not sure what you mean with this. Happy to talk through whenever!

I'm used to the pattern of the author submitting PRs. Some people have recently submitted my PRs for me, without me explicitly telling them to. That's just me saying "Don't do that", as I'm not sure if I'm good to submit it.

🤔 submit as in merge?

authors: juliosantos shelbyd

repo: trustfractal/wallet


text:
bip 49 address derivation via HD Wallet

I want to derive a test net address for bip 49 something like mg8PDfcsUZAPKyTgtmrnfpWhiFD4EqLSCy
but for any derivation path i use i get the same address with sequence starting with bc1
here are some example
E/BTC: m/0'/0/0 ----bc1qjwl0nemk5xl34d9jmy352c0k9vvem6h0g0cg3j
E/BTC: m/44'/0'/0'/0/0 ----bc1qkgsv8w9nfdfrjspf9dnsn3u9wzefz4mfjwwj4p
E/BTC: m/49'/0'/0'/0/0 ----bc1qgnldvv2tv785afg5ful9jt2zkdqdv07czstsva
E/BTC: m/84'/0'/0'/0/0 ----bc1qcg0080d2p4vc62atq7el9aguaryt505dq79zml
could anyone help me out please as while going through some issues /discussion i found out that trust has removed testing environment.

we don't support testnet addresses, but can take a look at this method (https://github.com/trustwallet/wallet-core/blob/master/swift/Sources/Extensions/BitcoinAddress%2BExtension.swift#L19) to create bip49 addresses

repo: trustwallet/wallet-core


text:
TwoFactor

How can I use the two factor with forms??

If only you had searched the previous issues as the same question has already been asked and answered: WinForm #391.

repo: trydis/FIFA-Ultimate-Team-Toolkit


text:
Photino doesn't work with Blazorise

Problem: When trying to use Blazorise, we get: Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/plain". Strict MIME type checking is enforced for module scripts per HTML spec.
Steps to reproduce:

open Photino.Blazor.Sample
add Blazorise https://blazorise.com/docs/start
Install-Package Blazorise.Bootstrap
Install-Package Blazorise.Icons.FontAwesome
add Blazorise to index.html

	<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/bootstrap@4.6.1/dist/css/bootstrap.min.css" integrity="sha384-zCbKRCUGaJDkqS1kPbPd7TveP5iyJE0EjAuZQTgFLD2ylzuqKfdKlfG/eSrtxUkn" crossorigin="anonymous">
	<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.15.4/css/all.css">

	<link href="_content/Blazorise/blazorise.css" rel="stylesheet" />
	<link href="_content/Blazorise.Bootstrap/blazorise.bootstrap.css" rel="stylesheet" />

add @using Blazorise to _Imports.razor
add Blazorise to Program.cs

using Blazorise;
using Blazorise.Bootstrap;
using Blazorise.Icons.FontAwesome;

builder.Services
    .AddBlazorise( options =>
    {
        options.Immediate = true;
    } )
    .AddBootstrapProviders()
    .AddFontAwesomeIcons();

add Blazorise.Button to Index.razor

<Button Color="Color.Primary" Clicked="@OnButtonClicked">Click me</Button>

    Clicked @counter times

@code {
    int counter;

    Task OnButtonClicked()
    {
        counter++;

        return Task.CompletedTask;
    }
}

If we run the app, we get:

Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/plain". Strict MIME type checking is enforced for module scripts per HTML spec.
Failed to fetch dynamically imported module: http://localhost/_content/Blazorise/button.js?v=1.0.7.0
TypeError: Failed to fetch dynamically imported module: http://localhost/_content/Blazorise/button.js?v=1.0.7.0
   at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, Object[] args)
   at Blazorise.Modules.BaseJSModule.InvokeSafeVoidAsync(String identifier, Object[] args)
   at Blazorise.Button.<OnInitialized>b__12_0()
   at Blazorise.BaseAfterRenderComponent.OnAfterRenderAsync(Boolean firstRender)
   at Blazorise.BaseComponent.OnAfterRenderAsync(Boolean firstRender)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

You could use the .net instance that photino runs on, to start a server, that proxies the script, adding the required MIME type to the response.

Thank you for the advice, but that sounds way too complicated for a functionality that Microsoft.AspNetCore.Components.WebView.Wpf, MAUI, ElectronNET and Chromely have no problem with. This should work out of the box.
The reason I want to work with Photino is because Microsoft.AspNetCore.Components.WebView.Wpf and MAUI don't work on Linux, ElectronNET is too bloated and Chromely has many problems on Linux.

authors: Jinjinov mykeels


text:
Starter documentation?

Hey, I'm looking to improve our overall coherence in projects and our back-end team is thinking of using archunit, as such I found your project.
It seems like a great tool! I just have one problem, I have no experience with your tool and next to no experience with jest. What do I have to do to get started?
The documentation doesn't really cover getting started afaics.
Your docs here state npm install --save-dev tsarch. Cool straightforward enough.
Then under it, it gives an example of a spec file. Ok, cool, so I copy this as an experiment and create arch.spec.js.
Play around a bit to create arch.spec.js;
import "tsarch/dist/jest.js"; // << appended '.js' here as node was complaining about it.
import { filesOfProject } from "tsarch";

describe("Architecture tests", () => {
  it("N00b's first dummy test", async () => {
    const rule = filesOfProject()
      .inFolder("some folder")
      .shouldNot()
      .dependOnFiles()
      .inFolder("someotherfolder");

    const violations = await rule.check;
    expect(violations).toEqual([]);
  });
});

But what do I do from here? Do I install jest and create an npm run jest script? In that case if complains about a malformed spec file. Or do I run something like node arch.spec.js? If I do that, it throws errors such as

Is there anywhere where this is documented? I couldn't find anything on so, google, or youtube either. If this isn't documented anywhere, I can open a PR with our own internal documentation backported once I've written it to help out.

Ah, I think I might have figured it out. Found a older project here which showed me what I was doing wrong.
Will work it out further next week and might write a getting started document.

repo: ts-arch/ts-arch


text:
Forward verbose option to build function when building for Node 16

When building for Node 16, the verbose option wouldn't be forwarded, so the logging output was different than Node 10.

authors: Mrtenz Nattaworn

repo: ts-bridge/ts-bridge