Failed to set ntp: NTP not supported.

Tried to install on CentOS 7 using the interactive script. script was giving this error Failed to set ntp: NTP not supported. and exiting.
Installing ntp package resolved the issue. yum install ntp
ntp should be added to prerequisite packages.

This is strange, because what script does is that it tries to disable ntp service and use systemd-timesyncd:
https://gist.github.com/seriyps/dc00ad91bfd8a2058f30845cd0daed83#file-mtp_install-sh-L142-L149
Do you have script's output available before it failed? I'm interested in the last INFO message it printed before it failed (basically, want to find which command crashed)

Unfortunately I dont have the output. but I know exactly where it was failing as I debugged it.
systemctl is-active ntp was returning unknown and timedatectl set-ntp on was giving Failed to set ntp: NTP not supported. error and crashing the script.

So this command was crashing the script timedatectl set-ntp on

Ok, thanks! That's interesting.. I found this https://bugzilla.novell.com/show_bug.cgi?id=869336 but will investigate further later

Also this: https://unix.stackexchange.com/questions/317346/ntp-not-enabled-according-to-timedatectl-centos-7

It seems that, while Ubuntu uses systemd-timesyncd for time synchronization, CentOS 7 uses ntp or chrony.
I will update setup script to install chrony package.

Well I dont know about chrony, but installing ntp resolved the issue for me.

yep, timedatectl can work with both ntp and chrony. It checks which one is installed and uses it. And if none installed, then you'll get this error: Failed to set ntp: NTP not supported.

sudo ntpdate -qu 1.ro.pool.ntp.org
timedatectl set-timezone "your loc"

I tried few thing but it doesn't work because "ntpd.service" doesn't exist/missing from.
so i reinstall "ntp"
& also install "systemd-timesyncd"
Which synced with my system automatically. ANd now ntp is active without "timedatectl set-ntp on".
may be it occurs because of some packet downloading issue while installing. It worked for me, I Hope this will work for you guys too.


Clean up API for better web support via JPro

Using JPro tech we can port FXGL to web. There are some API not supported by jpro, e.g. setCursor or multiple stages. In addition, it might actually be easier overall to use just a single stage (including the preloading scene) to simplify architecture. We simply need to know the size of the stage on open, or simplify startup routines

[X] Use single stage (preloading + rest)
[X] initStyle in MainWindow will fail (as stage is shown)
[X] setCursor
[ ] Error dialog show and wait not supported

What is the problem with setCursor? setCursor should work fine with jpro.
If you have any further questions or need help, you can contact us at<EMAIL_ADDRESS>.
Soon, I would like to add some fxgl-samples to the jpro-demo-page! :)

Re: setCursor, I don't know, I haven't done much testing, just wrapped code that was failing during my first experiments with isDesktop(). Eventually, I'll investigate the errors.
Cool, thanks!


[terra-clinical-detail-view] Fixed IE10 wrapping issue for label-value-views

Summary
Fixed IE10 wrapping issue for label-value-views inside of detail-view-list, by adding max-width: 100% in DetailListItem css
Additional Details
Verified this in IE11, IE10, Chrome and Mozilla
fixes #516
Thanks for contributing to Terra.
@cerner/terra

@avinashg1994 can you add screenshots to verify this change in IE10 and IE11.

@avinashg1994 can you add screenshots to this PR summary to verify this change in IE10 and IE11.

I have added the screenshots for IE10 and IE11


Greenkeeper/ember cli babel 7.7.3

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Too similar bounding boxes with different classes

Hi, I do object detection on medical images. I have 2 similar classes. No matter which model I try, I always get too similar bounding boxes for different classes. The models are capable of finding superclass but for all objects, it gives too similar bounding box coordinates. How to handle it? Should I change the loss function then how to do it? Thank you.

It is expected. If the detector predicts two classes with scores higher than a threshold, then we leave both.

How to resolve it. I want to change the loss function. Is there any easy way to do it otherwise I need to train a Siamese network after trainining detection model on the superclass.

You can do a NMS across different classes or just keep the bbox with highest scores among all classes.


Travis CI sporadically fails in control.tests.convert_test.TestConvert

Travis CI tests are failing in semi-random ways and generating the following error:
FAIL: testConvert (control.tests.convert_test.TestConvert)
Test state space to transfer function conversion.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/python-control/python-control/control/tests/convert_test.py", line 86, in testConvert
    ssTransformed = matlab.ss(tfOriginal)
  File "/home/travis/build/python-control/python-control/control/statesp.py", line 1149, in ss
    return tf2ss(sys)
  File "/home/travis/build/python-control/python-control/control/statesp.py", line 1223, in tf2ss
    return _convertToStateSpace(sys)
  File "/home/travis/build/python-control/python-control/control/statesp.py", line 779, in _convertToStateSpace
    num, den = sys._common_den()
  File "/home/travis/build/python-control/python-control/control/xferfcn.py", line 821, in _common_den
    % quad.imag.max()
AssertionError: Quadratic has a nontrivial imaginary part: 1.06581e-14

The error is not always present and re-running the build sometimes fixes it.  It appears the problem may be due to the way that random test cases are generated (although the seed is fixed in the unit test => not sure how we are getting different results on rebuild).

Two reasons I can think of for different results given the same inputs are:

tests were run on different hardware, e.g., CPUs with and without AVX2,
and uninitialized variables.

However, neither seems all that likely.
Besides that, for the assertion to be triggered (BTW, shouldn't that be assert all(quad.imag < 10 * eps) be assert all(abs(quad.imag) < 10 * eps) ?), I think a complex conjugate pairs would have to be mismatched (that is, not exactly conjugate) -- can that happen?
If this is due to round-off, why not dodge the problem with quad = np.array([1, -2*poles[n].real, poles[n].real**2 + poles[n].imag**2]) ?

@stanmoon it would be great if we could reproduce this error.  Could you let us know your CPU, OS and version, and also Python, Numpy, Scipy, and python-control versions?  If you need help figuring any of that out, let us know.

In case this was due to Scipy or Numpy updates I just retried this, but I can't reproduce it on my system, Ubuntu 18.04 64-bit running on a Intel i5-5200U.
I tried the following two setups:

Using system Python, Numpy, etc.:
Python 3.6.5
Numpy 1.13.1
Scipy 0.19.1

This probably uses "plain old" BLAS and LAPACK for linear algebra.  Not sure if
that's relevant for this test anyway.

Up-to-date Conda Python 3-based system:
Python 3.6.5
Numpy 1.14.3
Scipy 1.10

This had MKL installed (it was a default Conda setup).

Fixed in PR #206.


unix: use QUEUE_MOVE when iterating over lists

Replace uses of QUEUE_FOREACH when the list can get modified while
iterating over it, in particular when a callback is made into the
user's code.  This should fix a number of spurious failures that
people have been reporting.
R=@saghul or @piscisaureus
@indutny There are two QUEUE_FOREACH statements in src/unix/fsevents.c.  They look safe to me (as in: the list isn't mutated concurrently) but can you confirm?

LGTM. Maybe we can close that issue about foreach being unsafe? Since basically now it's defined as unsafe so there would be nothing to fix, right?

LGTM

Landed in 26917dd...822969a, thanks for the review.
@saghul I know the issue you mean but I can't find it anymore.  Maybe that was over at joyent/libuv?

Landed in 26917dd...822969a, thanks for the review.

Wow, very elegant solution!

@saghul I know the issue you mean but I can't find it anymore. Maybe that was over at joyent/libuv?

The issue @saghul was likely talking about is #557.
However, there are other changes that worth merging.
In particular, there is a test-case for the issue you've fixed.
After your change my queue_foreach_delete test fails with
src/unix/linux-inotify.c:244: uv_fs_event_stop: Assertion `w != ((void *)0)' failed
which will be a segfault in case of NDEBUG build.
I think this is because QUEUE_EMPTY(&w->watchers) returned true while all watchers were stashed into a local queue inside uv__inotify_read(), which lead to removing the watcher_list from the RB tree (and freeing it).
Simplest test case for this:

create and start two uv_fs_event_t for the same path;
in the callback for the first one, call uv_close() on it;
assert/segfault while accessing the second uv_fs_event_t from uv__inotify_read().

So, maybe it's worth taking my foreach_safe() approach for linux-inotify.c.
Another side-effect of your changes is that calling uv_smth_start() from a user's callback will insert the new element in the middle of the queue instead of the beginning/end as it was before.

On Friday, October 9, 2015, Andrey Mazo<EMAIL_ADDRESS>wrote:

Landed in 26917dd...822969a
https://github.com/libuv/libuv/compare/26917dd...822969a, thanks for
the review.
Wow, very elegant solution!
@saghul https://github.com/saghul I know the issue you mean but I can't
find it anymore. Maybe that was over at joyent/libuv?
The issue @saghul https://github.com/saghul was likely talking about is
#557 https://github.com/libuv/libuv/pull/557.
However, there are other changes that worth merging.
In particular, there is a test-case for the issue you've fixed.

I was referring to  https://github.com/joyent/libuv/issues/646, which was
indeed in joyent/libuv.

After your change my queue_foreach_delete test fails with
src/unix/linux-inotify.c:244: uv_fs_event_stop: Assertion `w != ((void
*)0)' failed
which will be a segfault in case of NDEBUG build.
I think this is because QUEUE_EMPTY(&w->watchers) returned true while all
watchers were stashed into a local queue inside uv__inotify_read(), which
lead to removing the watcher_list from the RB tree (and freeing it).
Simplest test case for this:

create and start two uv_fs_event_t for the same path;
in the callback for the first one, call uv_close() on it;
assert/segfault while accessing the second uv_fs_event_t from
uv__inotify_read().

So, maybe it's worth taking my foreach_safe() approach for linux-inotify.c.
Another side-effect of your changes is that calling uv_smth_start() from a
user's callback will insert the new element in the middle of the queue
instead of the beginning/end as it was before.
—
Reply to this email directly or view it on GitHub
https://github.com/libuv/libuv/pull/565#issuecomment-146919343.

--
/Saúl
bettercallsaghul.com

I was referring to  https://github.com/joyent/libuv/issues/646, which was
indeed in joyent/libuv.

Oh, sorry, I shouldn't be speaking for you.
However, it's the same issue as I brought up again in #557.

No worries! (Sorry for the brevity, I'm traveling and don't get much
internet)
On Friday, October 9, 2015, Andrey Mazo<EMAIL_ADDRESS>wrote:

I was referring to joyent/libuv#646
https://github.com/joyent/libuv/issues/646, which was
indeed in joyent/libuv.
Oh, sorry, I shouldn't be speaking for you.
However, it's the same issue as I brought up again in #557
https://github.com/libuv/libuv/pull/557.
—
Reply to this email directly or view it on GitHub
https://github.com/libuv/libuv/pull/565#issuecomment-146956931.

--
/Saúl
bettercallsaghul.com


Allow style control for "de-emphasized" nodes (or their mask)

What problem does this feature solve?
I would like to use focusNodeAdjacency, but the "non-focused" nodes are too transparent. I can currently specify itemStyles for 'emphasis' nodes; it would be great if I could also specify itemStyles for 'deemphasis' (downplay?) nodes (or the mask that goes over them).
What does the proposed API look like?
series: [{
  name: 's1',
  ...
  itemStyle: {
    emphasis: { ... } // exists
    downplay: { // proposed
      maskOpacity: 0.4 // could either allow specifying the opacity of the mask over the non-focused nodes
      color: 'rgba(0, 0, 0, 0.4)' // or setting the node color/styles directly (though this would be less helpful on its own, as node colors may vary across the series)
    }
  }
}]

I think echarts 5.0 will resolve this issue. See #12911

@100pah So how would this be done in v5?


Added R4 specific tests.

Description
Added R4 specific tests.

Test to validate CapabilityStatement FHIR version.
Test to validate a new resource type in R4 can be created and searched.
Test to validate resource type that was renamed can no longer be searched.

Related issues
Addresses #521. Work item: AB#69210.
Testing
E2E tests.

Test resources were in a bad state. Will abandon this PR and send a new one.


fix linking accounts

Linking your account wasn't working anymore. Thanks @coverbeck for the fix.

@garyluu semicolons for the links.model.ts get added automatically when you commit, but then the tslint complains about them and fails the lint test. Don't know about how you'd want to fix it longterm, but disabled the lint rule for that file

(with passing builds)


Feature Request: Check all checklists

Thank you so much for this! I can't believe it's not a stock feature and I'm glad you made it happen.
Feature request: any chance of adding a command for the opposite -- checking all checklists in a document? Both are very handy for recurring task lists -- "Yes, I finished all this stuff" or "Yes, time to do all this again"

Hey again @michaelzemba, that feature is now available in version 1.2.0


[SPARK-31326][SQL][DOCS] Create Function docs structure for SQL Reference

What changes were proposed in this pull request?
Create Function docs structure for SQL Reference...
Why are the changes needed?
so the Function docs can be added later, also want to get a consensus about what to document for Functions in SQL Reference.
Does this PR introduce any user-facing change?
Yes

How was this patch tested?
Manually build and check

Test build #120715 has started for PR 28099 at commit 257f78a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25413/
Test PASSed.

cc @maropu @gatorsmile

Test build #120715 has finished for PR 28099 at commit 257f78a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120715/
Test PASSed.

Thanks! Merged to master/3.0

Thanks you all!


Preview 0.4 asset fails to install (hangs on 'Installing required frameworks 16%')

Environment
Windows build number: Microsoft Windows [Version 10.0.18362.295]
Windows Terminal version (if applicable): 0.4.2382.0

Any other software? N/A

Steps to reproduce
Download and run https://github.com/microsoft/terminal/releases/download/v0.4.2382.0/Microsoft.WindowsTerminal_0.4.2382.0_8wekyb3d8bbwe.msixbundle
Expected behavior
Install should complete
Actual behavior
Installer window appears but hangs at:

There is no commentary to say why it has hung.
The PC is behind a corporate proxy server.
Terminal v.0.3 previously installed successfully using Github asset in similar environment.

I had that same problem with preview 0.3, being behind a corporate proxy too.
I was able to get a few directions on the installation log when I tried to install the package on PowerShell with the command Add-AppxPackage -Path <path-to-the-msixbundle-file>
Back then, the problem was related with a dependency on the package VCLibs.140, that couldn't be downloaded from the store because of the proxy.
I ended up downloading the VCLibs.140 package in another PC and installed it using the Add-AppxPackage cmdlet on PowerShell.
After this I was able to install both Windows Terminal Preview 0.3 and 0.4 on using PowerShell.

@DavidA2014 As @rogenaro points out, looks like you're struggling to download dependencies (probably the VCLibs.140 package which is required by all Centennial apps), likely due to your corporate proxy. Please try manually downloading and installing VCLibs.140 from the link provided part way down this article.
Closing for now, but please re-open if this does not solve your installation problems.

@bitcrazed Thanks for your reply. I tried installing the VCLibs.140 package (from https://www.microsoft.com/en-us/download/details.aspx?id=53175) but the Terminal install still hangs at 16%.  So I would like to reopen this issue.  Is there an installation log that would help identify where it is hanging?

Thanks @DavidA2014. Reopening.
Did you restart your machine after installing VCLibs.140?
I've asked the app install team to take a look at this thread too - hopefully they can provide guidance / log collection instructions.

@bitcrazed Sorry, I hadn't restarted the machine. I have now done so and the Terminal installer ran successfully. Thanks for your help.
I wonder if something could be added to the instructions at https://github.com/microsoft/terminal about the possible requirement to install the package manually if behind a proxy?

Great suggestion. I’ll be revising readme next week and will incorporate.
Rich.
From: DavidA2014<EMAIL_ADDRESS>Sent: Wednesday, September 11, 2019 01:06
To: microsoft/terminal<EMAIL_ADDRESS>Cc: Rich Turner<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/terminal] Preview 0.4 asset fails to install (hangs on 'Installing required frameworks 16%') (#2647)
@bitcrazedhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbitcrazed&data=02|01|richturn%40microsoft.com|e7d803c68a6947eba6c608d7368ed700|72f988bf86f141af91ab2d7cd011db47|1|0|637037859425890001&sdata=Z%2F%2FEAd04RGCw5aiIpK5%2BcFFwYZaREUPj8PdexNKldHM%3D&reserved=0 Sorry, I hadn't restarted the machine. I have now done so and the Terminal installer ran successfully. Thanks for your help.
I wonder if something could be added to the instructions at https://github.com/microsoft/terminalhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal&data=02|01|richturn%40microsoft.com|e7d803c68a6947eba6c608d7368ed700|72f988bf86f141af91ab2d7cd011db47|1|0|637037859425890001&sdata=cr7RxH4oFTHN%2BjU%2F3eAjFRmzsCKf2BC8l3B3xtIRh7Y%3D&reserved=0 about the possible requirement to install the package manually if behind a proxy?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fissues%2F2647%3Femail_source%3Dnotifications%26email_token%3DAAHK3HS7CX6TWDD76WIOUVTQJCRFLA5CNFSM4ITFCKT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6NUP4A%23issuecomment-530270192&data=02|01|richturn%40microsoft.com|e7d803c68a6947eba6c608d7368ed700|72f988bf86f141af91ab2d7cd011db47|1|0|637037859425899995&sdata=eX9Wlr7iLLbZuth1Ats5t9Ei%2BYL2U%2FAGsXHCVAtEGeA%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAHK3HV6HFDFYKFRCLIZ2B3QJCRFLANCNFSM4ITFCKTQ&data=02|01|richturn%40microsoft.com|e7d803c68a6947eba6c608d7368ed700|72f988bf86f141af91ab2d7cd011db47|1|0|637037859425899995&sdata=hIX75SON%2B73tD41v8IxvkjtYS2On27sWczKPlFrSRS4%3D&reserved=0.

You know, I don't think we do this at all anymore. I'm gonna close this.


Remove encoding writing stuff

Q
A

Bug fix?
no

New feature?
no

BC breaks?
yes

Deprecations?
no

License
MIT

What's in this PR?
This PR removes all stuff related with write filters in the Http\Message\Encoding namespace.
Why?
The abstract class Http\Message\Encoding\FilteredStream defines an abstract method named getWriteFilter that is not called anywhere and produces dead code not being tested. IMO this code must be removed or at least deprecated.
Example Usage
You can run the tests to see that this code is not being used nor tested.
$composer test

Checklist

[ ] Updated CHANGELOG.md to describe BC breaks / deprecations | new feature | bugfix
[ ] Documentation pull request created (if not simply a bugfix)

To Do

[ ] If the PR is not complete but you want to discuss the approach, list what remains to be done here

As far as I can see it's being called here: https://github.com/php-http/message/blob/master/src/Encoding/FilteredStream.php#L55

Yes, but the writeFilterCallback is not being called anywhere

That's true, but technically the methods you removed are still called.

Ping @joelwurtz

My intent was to propose a method to write into a filtered stream which is the reverse filter of the encoding one.
This can be useful on server side or library manipulating stream (like transfering data from a FilteredStream to another FilteredStream should result in the same data, which is not the case actually as it would only decode multiple times but never reencode)
However i nerver implemented the method as ATM there was no need for that, removing this is not a problem as like you said it's never used (and it's not a BC break).
But there should be more to that, the filtered stream should only be readable and not writable (so isWritable should return false, and write method should throw an exception) and also it should not be seekable (but not the purpose of this PR, can be reported as a separate Issue or write as a separate PR)

Well, the fact that we don't use it is enough for removal?
Also, IMO it's a BC break, no matter if it's used by US or not, it's a public API change.

this is a massive BC break in our public API. if we decide we don't need this we should deprecate the methods and remove them in version 2 only. if they are useful as is, we should instead write some tests that make sure they work as intended.

Ah yes didn't see the public visibility, i think it's a mistake in the original code as user never need to get the encoding or decoding filter it's only an implementation detail, they should be deprecated then and removed in 2.0.

so we can keep this PR open but mark it to be version 2 only, and do
another one to deprecate the methods? should we also trigger a
deprecation warning like symfony does?

@dbu I've already modified the PR to deprecate the methods.

@sagikazarmark ready for review

LGTM


Provide extensions a way to localize their messages

Hi there,
after publishing a well-known extension, we want to reach even more people, even them, who don't know English that well(like me). So, after all, we want that everybody understands how they can make there dreams come true with icons they like and how they contribute with there own icon-mapping. And the way, obviously, is: Having any message in there first language, but we need the help of you.
In fact, we are in need of the language settings. Could you provide us any way how we can determine which language the UI is?(in the best way via package.json, because the commands are just supporting one language)
Thanks

Actually what @jens1o want to say is that we request that the command titles in the package.json of an extension can support i18n.

This is all supported :-) but not well documented. Best you take a look at one of our extensions to see how this is done. A good example can be found here: https://github.com/Microsoft/vscode/tree/master/extensions/php
The trick in the package.json is to use a %key% instead of a string and to provide package.nls.*.json files with the translations.
I will close the issue since the support is there. If you have further questions please ping me in this issue and I am glad to help.

@dbaeumer The lack of documentation surely is to blame cause I've looked into it and couldn't find a solution. Thanks for the info.

@dbaeumer Do the package.nls.*.json files need to be in the root folder?

Yes, they must be siblings to the package.json file right now.

@dbaeumer we're trying to deploy the extension via vsce publish but we've found that package.json file gets modified and the placeholders get replaced by the English translations (my system is in English).
How we should proceed here? Is this supposed to be the expected behavior? Because this is not what we expected and it breaks our tests just before deploying as we check the integrity of the package.json file before the publication process.

Note here that vsce package works as expected.

Looks like @robertohuertasm has identified a bug in vsce.

Yes, I think I did. You can take a look at the details:

issue: vscode-vsce#158.
PR: vscode-vsce#159

@joaomoreno can you comment on vscode-vsce#158


Static rackapp

Serve the static files using the rack app rather than compiling each time.

Closing as merging to wrong branch.


Meanings of "align_corrected", "ff_corrected" and "uncorrected"

I apologize, but I do not have permission to access your paper, and the meanings of "pred_align_corrected," "pred_ff_corrected," and "pred_uncorrected" poses generated for each molecule are not entirely clear to me.
Based on the results I have reproduced from PDBBind, it appears that "pred_uncorrected" has the highest accuracy and success rate. Does this imply that the "pred_uncorrected" pose is the best, and can I only consider the "pred_uncorrected" pose for my subsequent analysis?

Uncorrected: Pose predicted from model, without any modification
FF: Ligand pose post-processed with MMFF94 optimization in RDKit (ignoring protein)
Aligned: RDKit-generated conformations transformed and aligned to model prediction using Kabsch algorithm

While raw poses might be the best in terms of RMSD, they might exhibit unwanted physical characteristics such as dubious bond lengths, angles, etc.. https://arxiv.org/abs/2308.05777 suggests a number of additional metrics in this direction.

Uncorrected: Pose predicted from model, without any modification
FF: Ligand pose post-processed with MMFF94 optimization in RDKit (ignoring protein)
Aligned: RDKit-generated conformations transformed and aligned to model prediction using Kabsch algorithm

While raw poses might be the best in terms of RMSD, they might exhibit unwanted physical characteristics such as dubious bond lengths, angles, etc.. https://arxiv.org/abs/2308.05777 suggests a number of additional metrics in this direction.

Hi, Yueming-Yin
Thank you for your query. I'd like to provide some clarifications:

I appreciate the answer given by isty2e; he's essentially right in his response.
The "aligned" conformations, in addition to being aligned in terms of overall orientation using the Kabsch algorithm, also align the torsion angles between the RDKit conformations and the predicted conformations.
I hope this addresses your concerns.

Best regards,
Xujun


"Luica" is listed in the drop-down menu

Description:
"Luica" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Luica" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Luica, CĂLĂRAȘI (Luica)".


Parse links in description

Links from description should be placed to comment into @see property.
Example: https://core.telegram.org/bots/api#forcereply
/**
  * Upon receiving a message with this object,
  * Telegram clients will display a reply interface to the user
  * (act as if the user has selected the bot‘s message and tapped ’Reply').
  * This can be extremely useful if you want to create user-friendly step-by-step
  * interfaces without having to sacrifice privacy mode.
  * @see https://core.telegram.org/bots#privacy-mode
  */
export type ForceReply = {
}

target.querySelectorAll('a').map(e => e.href)

https://github.com/sergeysova/telegram-typings/commit/09163bbb830b9f55f1b0c92826aee2093207baa4

So, what about a commit. Does it need to be redone?
Also, don't you think we should ignore those generated files from the repository and put their parts in the readme like examples?

Not. Files is needed when install package to project


Spectre tables (enhancement/ update)

You should try this for spectre tables.
https://css-tricks.com/molten-leading-css/

Do you mean the font sizes that depend on window width?

Yes


Feature Request: Prevent Banner Ad Reload on Widget Tree Changes

Feature Description
Description:
Currently, when a MaxAdView for a banner ad is removed and then added back to the widget tree, it reloads the ad. This is particularly problematic for banner ads used in overlay or scrollable views, where the ad might frequently disappear and reappear. On slower devices, this can result in longer wait times and negatively impact the user experience. It's crucial to have an option to retain the banner ad's state and prevent it from reloading when the widget tree changes.
Use Case:
In our application, we display banner ads as overlays that disappear upon user scrolling. When the same widget is displayed again, the ad reloads, which is inefficient. This is especially critical on lower-performance devices where ad reload times are significant.
Proposed Solution:
Similar to AdMob's implementation in Flutter, we propose separating the advertisement object from the advertisement widget. This would allow the ad to maintain its state independently of the widget lifecycle.
AdMob Implementation Reference:
AdMob allows creating a BannerAd object separately from the AdWidget that displays it. Once the ad is loaded, it can be displayed in any widget without needing to be reloaded, as exemplified in their documentation: AdMob Flutter Banner.
Example API Proposal:
// Create a BannerAd object
final BannerAd myBanner = BannerAd(
  adUnitId: 'YOUR_BANNER_AD_UNIT_ID',
  size: AdSize.banner,
  request: AdRequest(),
  listener: BannerAdListener(),
);

// Load the banner ad
myBanner.load();

// Use the BannerAd object in a widget
Widget bannerWidget = AdWidget(ad: myBanner);

Expected Behavior:
Provide a configuration to retain the banner ad state when the widget is removed and added back to the widget tree.
The state of the banner ad should be preserved, avoiding unnecessary reloads and displaying the ad instantly upon re-adding.
Benefit:
Reduces redundant network requests and improves performance, particularly on slower devices.
Provides a smoother user experience by ensuring that banner ads do not require reloading when navigating through different parts of the app.

@yo1106, thank you for filing an RFE to avoid reloading banner widgets. We will consider adding it to our queue.


Bug in Custom Validation

I found the following problem:
I have the following class
class Booking {
  DateTime Start {get;set;}
  DateTime End {get;set;}
  CustomBehaviour Behaviour {get;set;}
}

The CustomBehaviour Class looks like the following:
public class CustomBehaviour {
  public Booking booking;
  public CustomBehaviour(Booking b){
    this.booking = b;
  }

  DateTime Start {
    get { return booking.Start; }
    set { booking.Start = value;}
  }
  ...
}

So essentially the CustomBehaviour also has those Start and End DateTimes. I use a PartialView with the CustomBehaviour as model to update these Data.
Then I added a Custom ValidationAttribute to the Booking "Start" Property to ensure that Start is always before End.
Now I ran into the following problem: when I generate a new Booking, everything works fine. But I have some old data which are incorrect (Start is after End). If I try to save it, I get the Validation Error 2 times: one for the "Booking.Start" itself, and the other for "CustomBehaviour.Booking.Start". And when I enter correct data, there is always 1 ErrorMessage displayed (the Booking.Start one).
Could it be, that the Annotation or Validation has a problem to see that "Booking" and "CustomBehaviour.Booking" are the same object in this case?

Please provide your exact model, including the applied validation attribute(s). May also help to see the exact content of the ModelState (the keys and associated error messages) when the error message is displayed twice. And where, exactly, is the error message displayed twice?

ddddddd


Incorrect switch option in help

While testing this, I noticed --bzip2, --bz2, -j in the man page.  Change the -j to -b instead?

I was puling -j from tar --help's output, see here:
  -j, --bzip2                filter the archive through bzip2
  -J, --xz                   filter the archive through xz
      --lzip                 filter the archive through lzip
      --lzma                 filter the archive through xz
      --lzop                 filter the archive through lzop
      --no-auto-compress     do not use archive suffix to determine the
                             compression program
      --zstd                 filter the archive through zstd
  -z, --gzip, --gunzip, --ungzip   filter the archive through gzip
  -Z, --compress, --uncompress   filter the archive through compress

So I'll change -b to -j in the compressdoc options

Fixed! see 58eacac02


[Question]

I have installed Harvester/rancher from ISO file and the cluster tools are still not available.
the above screenshot shows that the "Containers with unready status: [httpd] "..
your help/advice would be appreciated.

I think u may hit the image load timeout issue https://github.com/harvester/harvester/issues/2651#issuecomment-1641386407, please check if you can host the ISO image locally with faster network speed, this problem will get addressed in the upcoming new v1.2.0 release.

Thanks for your reply, but I assume this is not the issue based on following results:

Hi @AminGR, could you tell us what environment you use to deploy Harvester? Is it a bare-metal server or a VM? Also, the specs of the machines, especially the disk size, are also of interest.
From the screenshot it seems the container image for the harvester-cluster-repo Pod is missing. Could you help us verify if the image exists on the node with the following command?
# Need to execute it on the Harvester nodes
$ sudo -i
$ ctr -n k8s.io i ls | grep harvester-cluster-repo

And if you could access the Harvester dashboard, please help collect the support bundle file for us to investigate the issue further. Thank you.

Hi @starbops, thanks for your reply.
Tested environments was as follow:
bare-metal installations on : HPE DL360P Gen10 / HPE DL360P Gen9 / HPE DL360P Gen8
Virtualization on ESXi 7.x ( I will give it a shot on Proxmox soon )
"ctr -n k8s.io i ls | grep harvester-cluster-repo"    returns nothing
I have tried the installation in none-UEFI mode/ GPT and MBR as well, and it was the same.
The only successful scenario for me (until now) was the deployment on Ubuntu which worked like a charm.
Thanks again!


[REQUEST] Sorry if this is misuse of issue report / misplaced - Looking for guide breakdown of all added features as every link provided sends me in circles

Apologies in advance, I am someone who puts down and picks up MC once every like 2 years, and only for a few weeks or so. I am playing using these mods, and am just trying to get a breakdown on how/what each thing does in this mod, how to power it, transport stuff, etc. The wiki points to the github, the github has the Readme, the Readme points to the main page, and the main page points to the github. So Im all sorts of lost haha.

Nevermind - realized you can search all listed items with "@Industrial" and found the book you can craft in-game which breaks it all down. Sorry!

Hi! xD


kernel: Move to virtiofs kernel tag

virtiofs-dev is a branch, now there is a tag
based in kernel 5.6 move patches to use the tag name.
Depends-on: github.com/kata-containers/runtime#2843
Fixes: #1095
Signed-off-by: Jose Carlos Venegas Munoz<EMAIL_ADDRESS>

/test

/AzurePipelines

/AzurePipelines run

@jcvenegas we need to bump kata_config_version here

@jcvenegas we need to bump kata_config_version here

/test

/AzurePipelines run

@jcvenegas To have a reference of our discuss over slack:
It looks like we are only carrying one custom kernel path, a.k.a fix race condition for virtio_vsock. Does it mean the other custom kernel patches we had are already in the updated kernel (e.g. the patch to enable evged)? The previous commits have three custom kernel patches: https://github.com/kata-containers/packaging/commit/8abf130d29c383781ad0588db505b76f87583fda.


pull out angular adapter code and publish independently

expose core as the main entry point instead

done, published at grid-angular-adapter


Qwik City Cloudflare starter does not build

Qwik Version
0.0.39
Operating System (or Browser)
Win11
Node Version (if applicable)
18.6.0
Which component is affected?
Starters / CLI
Expected Behaviour

npm init qwik@latest - select Qwik City with Cloudflare deployment
npm install
npm run build

Expected: build without errors
Actual Behaviour
Partial output:
src/entry.cloudflare.tsx:6:25 - error TS2304: Cannot find name 'PagesFunction'.

6 export const onRequest: PagesFunction = async ({ request, next, waitUntil }) => {
                          ~~~~~~~~~~~~~

src/entry.cloudflare.tsx:28:33 - error TS2345: Argument of type '{ url: any; }' is not assignable to parameter of type 'RenderToStreamOptions'.
  Property 'stream' is missing in type '{ url: any; }' but required in type 'RenderToStreamOptions'.

28     const result = await render({
                                   ~
29       url: request.url,
   ~~~~~~~~~~~~~~~~~~~~~~~
30     });
   ~~~~~`

src/routes/api/[org]/[user].json/index.ts:2:16 - error TS2307: Cannot find module 'os' or its corresponding type declarations.

2 import os from 'os';
                 ~~~~

src/routes/api/[org]/[user].json/index.ts:12:11 - error TS2591: Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.

12     node: process.versions.node,
             ~~~~~~~

Additional Information
Several of the TypeScript compiler errors can be handled with config:

In the default tsconfig.json, there is types: ["vite/client"]. This causes TS to ignore all the type defs in the node_modules/@types dir, including the node types, which account for a few of the build errors.
Setting "noImplicitAny": "false" gets rid of a bunch more errors. Obviously not the ideal solution but fixing those properly should be pretty easy.

Other errors are not so obvious:

I've got no idea where the  PagesFunction type is supposed to come from.
Per the Qwik type defs, this render function needs a stream property rather than url:// Generate Qwik SSR HTML
const result = await render({
  url: request.url,
});

Related to #850
You should be able to copy the Cloudflare Middleware from here
https://github.com/BuilderIO/qwik/blob/main/packages/qwik-city/middleware/cloudflare-pages/index.ts
Into your entry.cloudflare file. The middlewares should be set up with the renderToStream options.

Actually, changing my answer.
Changing the entry.cloudflare.tsx file to this
import render from './entry.ssr';
import { qwikCity } from<EMAIL_ADDRESS>import qwikCityPlan from '@qwik-city-plan';

/**
 * Cloudflare Pages Request Handler
 */
export const onRequest = async (args: any) => {
  const handler = qwikCity(render, qwikCityPlan);
  return await handler(args)
};

Gets everything building for me.

Same problem here, but the above from @nnelgxorz does not work, because qwik-city-plan can't be found.
[vite]: Rollup failed to resolve import "@qwik-city-plan" from "src/s_3yhhhhxufdw.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`

@kylecordes What version of Qwik City are you on? I got a Netlify site working with a similar setup on 0.0 29 this morning.

Should be fixed in the next release, thanks for opening the issue.

https://github.com/BuilderIO/qwik/pull/938
https://github.com/BuilderIO/qwik/pull/937


How can I capitalize the first letter of sentence ?

Hi,
When using react-moment with fromNow, I would like to capitalize the first letter of sentence.
Do you provide some way to do it ? If yes how ?
Thanks.

I was trying to solve the same issue. First I tried to do it by changing the <time> element's innerText but I ended up using plain moment.js not react-moment.
So in the component (functional in my case) I  just do
const [dateStr]= React.useState(moment(new Date(date)).calendar());


I want wechaty puppet padpro token to create a wechat bot

I have connected with botorange2 on wechat. As per the suggestion I got from him, I am creating this issue to get a token with the template information as follows:

Introduce Yourself(who you are): developer of a startup
Explain the Problem You Want to Solve:(what you do): Message listening for Some companies
Your Email<EMAIL_ADDRESS>Your Wechat: meghal_132
I Had Joined the Wechaty Developers' Home Wechat Room: YES
I understand that the Wechaty v0.15 is in very Early Alpha Stage, and I have the necessary engineering technics to deal with the bugs instead of just asking for support: YES

Goal: To monitor messages of wechat for my organization.

We have received your email, and will have a meeting with you at 2 p.m. tomorrow.
Please close this issue and see you tomorrow, thank you.

Sure, Can you please confirm your timezone for the meeting?
I am in India and my timezone is IST.

OK, the meeting time: 06:00:00(UTC), are you free at that time?

I am confirming the timing as 6 a.m. (UTC) which will be 11:30 a.m IST. I am comfortable with this timings.
Please confirm it from your side so that I can close the issue.

Confirmed! Thank you.

See you in the meeting.
Will use the meeting ID which I got after registration on Calendly.
Thanks.


BUG: plot cumulative costs in plot_returns

when plotting cumulative returns, cost should be cumulative as well.
plot negative cost

@yankees714 mind taking another look?

@yankees714 sorry didn't see your request for a test, added that now


[bazelw] Use arm64 binary on darwin-arm64

Now that we've pulled in https://github.com/envoyproxy/envoy/pull/20852, I'm no longer seeing linker errors when running Swift tests for iOS as reported in https://github.com/envoyproxy/envoy-mobile/issues/2101.
Risk Level: Low to the libraries, Moderate to local development on an M1 Mac.
Testing: ./bazelw test //test/swift:test --config=ios passes
Docs Changes: N/A
Release Notes: N/A

Verified with a few common build+test targets: ios_dist, android_dist, /test/cc/..., //test/swift:test
The only thing I know to be broken is ./bazelw test //test/swift:test --config=ios --ios_multi_cpus=x86_64 due to https://github.com/google/xctestrunner/pull/40, but that's not something I've ever needed in my local development.
Something else may be broken, but I haven't seen it.


fix(setprops): allowed for setProps to be synced with nextTick intervals

setProps in certain cases was being blown away by nextTick intervals. If the property is not up to
date, setProps will be called again to sync the changes.
fix #1419

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[ ] It's submitted to the dev branch.
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Kinda hacky but many things are here :)

If you can get the rest of the tests to pass, I think we should be good.

@lmiller1990 It looks like the tests are timing out? I was able to get them to pass locally so I am unsure of the issue

Looks like this test is hanging?

I will take a look at the hanging test.
I think we should drop support for < Vue 2.5 sometime.

Heh nice. I would not have thought about this :D

@dobromir-hristov I almost wish I didn't think of this 😆 . It's pretty hacky, but wasn't sure of another way, especially since Watcher doesn't seem to do anything with the immediate option, except execute the callback 'immediately'

@lmiller1990 any luck with that hanging test? Let me know if I can help in any way!

I spent a bit of time but I am not sure why is is hanging.
There is some way to skip tests for old Vue versions, you could give that a shot (if that's the reason it's hanging).

I spent a bit of time but I am not sure why is is hanging.
There is some way to skip tests for old Vue versions, you could give that a shot (if that's the reason it's hanging).

@lmiller1990 is there a config val in CI that handles that? Otherwise, I could just use xdescribe on a commit for that particular test and push it up, if that is alright with you

@AtofStryker sorry, I mean you can use this helper: https://github.com/vuejs/vue-test-utils/blob/1e3f7fbf7970b0e23715dac6a6cf2a468b0e6e3c/test/specs/wrapper/trigger.spec.js#L112

@lmiller1990 I figured out why the test was hanging. I completely forgot the $attrs use case, which was causing the test to go into an infinite recursion loop, which is bad :grimacing: . I have added an additional check here to compare for $attrs if the key doesn't exist on vm here. That should make the tests pass and not introduce breaking changes :smile:

Haha, so the test was actually correctly helping us out and catching the attrs edge case. Awesome! Great job on this, I will merge and do a release in the next week (probably with your babel dependencies ones that is merged).

@AtofStryker if I may, did you happen to figure out why the next tick caused the setProps call to fail?

Not sure if this is the culprit, but we have a test that appears to succeed, but never finishes.  i.e the test reports success, but jest never exits.  This was not a problem on 1.0.3 but is a problem on every version since.
Not a full repro, but the test is something like
    it('should use foo\'s dates when bar hasn\'t been set', () => {
      expect.assertions(2);
      wrapper.setProps({
        a: {
          ...a,
          endTime: '2020-01-02',
          startTime: '2020-01-01',
        },
        b: {
          endTime: '2020-01-02',
          startTime: '2020-01-01',
        },
      });
      expect(wrapper.vm.bar).toBeTruthy();

      wrapper.setProps({
        a: {
          ...a,
          endTime: '2020-01-02',
          startTime: '2020-01-01',
        },
        b: {
          endTime: '2020-01-01',
          startTime: '2020-01-01',
        },
      });
      expect(wrapper.vm.bar).toBeFalsy();
    });

This test passes very quickly (about one second), but 10 minutes later and jest is still doing...something.
This is fixed by doing
    it('should use foo\'s dates when bar hasn\'t been set', async () => {
      expect.assertions(2);
      await wrapper.setProps({
        a: {
          ...a,
          endTime: '2020-01-02',
          startTime: '2020-01-01',
        },
        b: {
          endTime: '2020-01-02',
          startTime: '2020-01-01',
        },
      });
      expect(wrapper.vm.bar).toBeTruthy();

      await wrapper.setProps({
        a: {
          ...a,
          endTime: '2020-01-02',
          startTime: '2020-01-01',
        },
        b: {
          endTime: '2020-01-01',
          startTime: '2020-01-01',
        },
      });
      expect(wrapper.vm.bar).toBeFalsy();
    });

We should update the docs to encourage people to always do await setProps - would that solve the problem?
Actually instead of using setProps I just write two tests - I find that easier to debug anyway. But we should make sure setProps still works well

Well for me, using await setProps solved my problem 🤷♀

@vegerot, I can't solve the same issue with awaiting. Does anyone know more about this weird issue and why it's happening?


Cannot build bzip2:x64-windows-static in visual studio 2019

When attempting to build boost with vcpkg using Visual Studio 2019 I get the following error:
-- CHECK_LIB_bz2_RELEASE:CHECK_LIB_bz2_RELEASE-NOTFOUND
CMake Error at scripts/cmake/vcpkg_fixup_pkgconfig.cmake:232 (message):
Library "bz2" was not found! If it is a system library use the
SYSTEM_LIBRARIES parameter for the vcpkg_fixup_pkgconfig call! Otherwise,
correct the *.pc file
Call Stack (most recent call first):
scripts/cmake/vcpkg_fixup_pkgconfig.cmake:297 (vcpkg_fixup_pkgconfig_check_files)
ports/bzip2/portfile.cmake:43 (vcpkg_fixup_pkgconfig)
scripts/ports.cmake:79 (include)
Error: Building package bzip2:x64-windows-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: bzip2:x64-windows-static
Vcpkg version: 2020.06.15-nohash

@dahubley, does the vcpkg path with a space? it looks same issue with https://github.com/microsoft/vcpkg/issues/13103, and would fix by PR https://github.com/microsoft/vcpkg/pull/13126

@PhoebeHui looks to the same. I moved the vcpkg directory to C:// and it works fine. Had to be something to do with the vcpkg location.

Good to know, thanks!
Duplicated to https://github.com/microsoft/vcpkg/issues/13103.

I have same title, different problem:
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a\_temp\70730c63-1d64-4e9f-a9d1-d0283ac330c6.cmd" Computing installation plan... The following packages will be built and installed: bzip2[core]:x64-windows-static -> 1.0.8#1 Detecting compiler hash for triplet x64-windows-static... Could not locate cached archive: C:\Users\VssAdministrator\AppData\Local\vcpkg\archives\cf\cf0f4a1478b0809f582900653988b3668f8a97c1.zip Starting package 1/1: bzip2:x64-windows-static Building package bzip2[core]:x64-windows-static... -- Fetching https://sourceware.org/git/bzip2.git... Make Error at scripts/cmake/vcpkg_execute_required_process.cmake:91 (file): file failed to open for reading (No such file or directory): C:/vcpkg/buildtrees/bzip2/git-init-x64-windows-static-out.log Call Stack (most recent call first): scripts/cmake/vcpkg_from_git.cmake:85 (vcpkg_execute_required_process) ports/bzip2/portfile.cmake:1 (vcpkg_from_git) scripts/ports.cmake:142 (include) Error: Building package bzip2:x64-windows-static failed with: BUILD_FAILED Please ensure you're using the latest portfiles with.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: bzip2:x64-windows-static
Vcpkg version: 2021-01-13-d67989bce1043b98092ac45996a8230a059a2d7e
`

@unusual-aspect, please open a new issue to track.


Default input model

Do not merge until  e2e testing has been pulled into develop

@andrewphilipsmith I'm just handling this merge now. I see there's some changes to the test_all_components.yaml file. Some parameters mostly. Is this all still okay?
I'll continue with merging on the assumption that the newer commits are the correct ones. But can always revert if need be.

@James-Thompson-724 I noticed the tests fail here because Scenarios/Global/data/country_data.csv is missing. Are we removing a lot of these scenario files? If so, let me know what would be best. Im going to add back that one file for now, as it keeps the tests running!

See 11112a6 for readding of Global scenarios

The test config test_global_config.yaml references Scenarios/Global/data/country_data.csv, and some other files inside Global, but this folder now should be called Homogeneous, so I think that may be the problem


Update the parameter documentation to be much more comprehensive.

Signed-off-by: Chris Lalancette<EMAIL_ADDRESS>This PR adds a lot more information to the documentation about Parameters.  In particular, it expands the Concept document about Parameters pretty substantially, and adds in a How-To Guide on how to use ros2 param.  It also adds a release note about the change in https://github.com/ros2/ros2cli/pull/684 which allows us to handle "!!str mystr".

I've responded to all review comments; please take another look when you get a chance!


RateLimiter.withCost combinator + Rate Limiter composition tests

Type

[ ] Refactor
[x] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description
This patch updates the RateLimiter module to include another constructor which includes a sub-constructor which allows us to specify a cost while maintaining composability with other RateLimiter instances. This enables the use of this module to rate limit for the following cases :

Accessing resources with an "API Credit" limit over a time window.

With composition, accounting for multiple "credit" limits. ( eg: Github API )

Accounting for different "costs" per api per provider within a single credit limit.

Many providers have different API costs for different endpoints within their ecosystem.

Usage Example
import { Effect, RateLimiter } from "effect";
import { compose } from "effect/Function";

const program = Effect.scoped(
  Effect.gen(function* ($) {
    // Create a rate limiter that has an hourly limit of 1000 credits
    const rateLimiter = yield* $(RateLimiter.make(1000, "1 hours"));
    // Query API costs 1 credit per call ( 1 is the default cost )
    const queryAPIRL = compose(rateLimiter, RateLimiter.withCost(1));
    // Mutation API costs 5 credits per call
    const mutationAPIRL = compose(rateLimiter, RateLimiter.withCost(5));
    // ...
    // Use the pre-defined rate limiters
    yield* $(queryAPIRL(Effect.log("Sample Query")));
    yield* $(mutationAPIRL(Effect.log("Sample Mutation")));

    // Or set a cost on-the-fly
    const history = yield* $(
      rateLimiter(Effect.log("Another query with a different cost")).pipe(
        RateLimiter.withCost(3)
      )
    );
  })
);

@hsubra89 - apologies for the back-and-forth with the RateLimiter. We discovered the updated implementation was utilizing the fixed-window algorithm for token replenishment instead of the token-bucket algorithm.
The fix is in #2097. Please update this MR once the bugfix is merged.

@hsubra89 - apologies for the back-and-forth with the RateLimiter. We discovered the updated implementation was utilizing the fixed-window algorithm for token replenishment instead of the token-bucket algorithm.
The fix is in #2097. Please update this MR once the bugfix is merged.

No problem. I did notice that when the implementation was changed but didn't look into it too deeply.

Depends on #2097


Add branch alias for 1.0

Instead of requiring dev-master, you can require 1.0@dev to test the current dev version. dev-master is usually not a good idea.

done

Great, thanks for the contribution!


nprogress uses useTransition, should it use useNavigation instead?

https://github.com/remix-run/examples/tree/main/nprogress
nprogress uses useTransition, should it use useNavigation instead?
looks like the readme link to useTransition redirect to useNavigation

Yes, this example should be updated to use the useNavigation hook. Thanks!

oh I see already has PR https://github.com/remix-run/examples/pull/338


Updated version to 0.1.1

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (dd90b7b) 78.94% compared to head (5a8f676) 78.94%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   78.94%   78.94%
=======================================
  Files           5        5
  Lines         152      152
  Branches       11       11
=======================================
  Hits          120      120
  Misses         32       32

Impacted Files
Coverage Δ

tonereader/_version.py
100.00% <100.00%> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Create iepscf-uccle.txt

Hello, here is the file for IEPSCF Uccle, in Belgium.
School's official website : http://www.iepscf-uccle.be
Page for our 3 year courses :
http://www.iepscf-uccle.be/formation-bachelier-informatique-gestion (development orientation)
http://www.iepscf-uccle.be/formation-bachelier-informatique-systemes (systems orientation)
Unfortunately, we do not have a page where it is stated that students receive a school email address because we have lots of courses in languages, for instance, where students have no reason to get one . We reserve the school's email addresses only for some groups like those involved in the IT sections.
Thanks a lot.

@Raymakers I am sorry for a delay with processing your request. It is now merged.. Thank you!


Update webview view's urls to contain the extension id like normal webviews

Testing #107626
I was using the following in my launch.json:
"debugWebviews": true,
"rendererDebugOptions": {
	"urlFilter": "*eamodio.gitlens*",
	"webRoot": "${workspaceFolder}/src/webviews/apps"
},

And was unable to get js-debug to debug my new webview view (although normal webviews worked fine). @connor4312 pointed out the urlFilter and when I removed that everything worked.
Looking at the urls attached, you can see the difference between a normal webview and the webview view:

We should probably add the extension id into the webview view's url, so that we can consistently only attach to the webviews we want.

Thanks, I was just about to open this issue 🙂

I hacked it in in the linked commit; not very familiar with this part of the code. Let me know if you think it's worth PRing @mjbvz

I don't think so -- I pushed a tentative commit to a branch but didn't merge it


[Snyk] Upgrade @mui/icons-material from 5.4.4 to 5.10.6

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @mui/icons-material from 5.4.4 to 5.10.6.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 12 versions ahead of your current version.
The recommended version was released a month ago, on 2022-09-19.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
Base: 94.02% // Head: 94.02% // No change to project coverage :thumbsup:

Coverage data is based on head (3f5aab3) compared to base (7db429a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #227   +/-   ##
=========================================
  Coverage     94.02%   94.02%
  Complexity      475      475
=========================================
  Files            96       96
  Lines          1607     1607
  Branches        122      122
=========================================
  Hits           1511     1511
  Misses           56       56
  Partials         40       40

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Unable to merge lora into base model properly?

System Info
py3.11
Who can help?
@BenjaminBossan @sayakpaul
Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder
[X] My own task or dataset (give details below)

Reproduction
        from transformers import AutoModelForCausalLM
	from peft import PeftModel
	base_model = AutoModelForCausalLM.from_pretrained("Qwen/Qwen2.5-7B")
	model = PeftModel.from_pretrained(base_model, loraname)
	model = model.merge_and_unload()#untested prob should be in training code direct save as a new mdl
	model.save_pretrained(NEW_MODELBASENAME+"mergedwbase_bf16", tokenizer)
	tokenizer.save_pretrained(NEW_MODELBASENAME+"mergedwbase_bf16", legacy_format=False)
	print("done")

Expected behavior
I expect to have a folder named xxxx_mergedwbase_bf16 but it's not there
It also have not load the model or do any loading,i do not see progress bar>python xx.py
2024-11-10 23:03:13.070822: I tensorflow/core/util/port.cc:153] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-11-10 23:03:13.984027: I tensorflow/core/util/port.cc:153] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.

Anyone have any idea,or stuff that I need to take note,like compatibility or something?

Hey :)
Can you tell us a bit more about in which environment you are running this? The code looks fine (except that you're passing tokenizer as positional argument to save_pretrained which doesn't make sense).

hug thanks my friend,it worked after removing the tokenizer and tweaking a bit,I honestly don't know how But I will save the script for future use.


docs getting-started instructions should be windows friendly

added some windows specific cmd-line examples, commit e824e7a


Pup pack patcher

Lots of pup pack with file name casing issues, adjust the indices to the actual file names

I think this is no longer needed as there is some case-insensitive file loading in place now. Not 100% sure. Will re-open if I find an example where this is still required.


Add sequence.

Add Sequences.

Could you please rebase and also make sure to run make assets ?

I executed rebase and make assets. please confirm.

Pardon me, i meant squash not rebase. Just wanted to make sure there's a single commit with all your changes.

I was aware . It is all of my change to the minute that are currently committed .


Add a shortcut to redo last command

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
It is common that we need to check something repeatedly. In the standard terminal, using up arrow can help get the last command we use. I think it will be nice if navi supports the feature so that it can save the typing time.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Please consider using the shell widget
With it, you can simply press the up arrow key.

Thanks for your reply. The up arrow key only shows the navi command instead of the select command.
> navi
# select command, for example `apt update`,  and run
# press the up arrow key
> navi

What I hope is
> navi
# select command, for example `apt update`,  and run
# press the up arrow key
> apt update

I see.
If you install the shell widget and invoke navi by pressing Ctrl+G instead of typing navi, the up arrow key will work as you expect.

Got it. Thanks for your help!


Support writing strikethrough text in markdown using text

Strikethrough

The markdown is properly parsed but not properly displayed.

According to my tests the latest release version sends tildes as-is. I will test the latest develop build tomorrow.

Okay, I confirm that the 5 october f-droid build now properly parses ~~ when sending messages.
I recommend this bug to be closed since it's working, and #544 to be reopened, since that one is about the rendering issue.

It could be solved by inserting U+0336 after every symbol inside tildes, like t̶h̶i̶s̶.

pleeeeeease

Parsing works, so closing this. See #544 for the rendering issue.

Hello,
This feature does not work in Riot web 1.5.13
And according to my simple test, it's the markdown that is not parsed at all:

Could someone please re-open this issue?

@mlaily strike works

@mlaily strike works

Thanks for the tip, indeed it does.
But this is not user-friendly at all. This issue is about supporting the standard (?) markdown way with "~~".

This feature does not work in Riot web 1.5.13
[...]
Could someone please re-open this issue?

That would now be vector-im/element-web/issues/10444, I guess.


client.on("message") has been renamed.

Describe the bug
As of v13, the message event has been renamed to messageCreate, and should be changed in app.js
https://discordjs.guide/additional-info/changes-in-v13.html#client-message
As of now it still works but according to documentation throws a deprecation warning.

My apologies, I was looking at the wrong branch 🤦♂
I'll close this...


VSCode crashes when parsing deep JSON strings in an extension

VSCode Version: Latest public
OS Version: MacOS latest, happens on other OS' as well

Steps to Reproduce:

Create a simple extension and try to JSON.parse the string below

{"name":"test","fields":{"test2":{"name":"test2","fields":{"test3":{"name":"test","fields":{"test4":{"name":"test","fields":{"test5":{"name":"test","fields":{"test6":{"name":"test","fields":{"test7":{"name":"test","fields":{"test8":{"name":"test","fields":{"test9":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

VSCode crashes with
[2020-03-24 14:19:17.617] [main] [error] [VS Code]: render process crashed!

Try again with

{"name":"test","fields":{"test2":{"name":"test2","fields":{"test3":{"name":"test","fields":{"test4":{"name":"test","fields":{"test5":{"name":"test","fields":{"test6":{"name":"test","fields":{}}}}}}}}}}}}

Works just fine.
Wrapping the parse in try/catch did not help, nothing is caught.

Does this issue occur when all extensions are disabled?: Yes

@Foxhoundn I could not reproduce. I have tried with the following extension:

package.json:

{
    "publisher": "alex",
    "name": "93310",
    "version": "0.0.0",
    "engines": {
        "vscode": "^1.0.0"
    },
    "activationEvents": [
        "*"
    ],
    "main": "index.js"
}

index.js:

const vscode = require('vscode');

exports.activate = function(context) {

	const x = `{"name":"test","fields":{"test2":{"name":"test2","fields":{"test3":{"name":"test","fields":{"test4":{"name":"test","fields":{"test5":{"name":"test","fields":{"test6":{"name":"test","fields":{"test7":{"name":"test","fields":{"test8":{"name":"test","fields":{"test9":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{"name":"test","fields":{"test2":{}}}}}}}}}}}}}}}}}}}}}}}}}}}}}`

	const y = JSON.parse(x);

	console.log(`I have parsed it!`);

}

And I am able to execute the extension and I see the message.

Hi @alexdima, yeah sorry, you're right. There's a few more steps.
The error only happens when you try postMessage to a webview
So if you create a webview and do webview.postMessage({ foo: JSON.parse(*...the json*) }), the whole extension window crashes.


Fix: Changed order of ble and bleu

Issue: Bleu instruction was interpreted as Ble and was expecting whitespace after it

Thank you for investigation and report, but I make more complete solution & test in this commit https://github.com/ryukzak/wrench/pull/15/commits/31ecd7ded779db7f98658a000bb986fb071ac52e


Issue with image links with special character

I'm having issues downloading some images from a fairly long-running (Swedish) Wordpress site.
We are using WP Offload Media and uploading images to AWS/DO buckets, where a working link is generated as file url. Although this plugin seems to fetch another URL instead.
Original filename
nyttigt-mellanmål_proteinkakor.jpg
WP Offload Media
nyttigt-mellanma%CC%8Al_proteinkakor.jpg
Source plugin
nyttigt-mellanma%25CC%258Al_proteinkakor.jpg
There are quite a few occurrences with åäö and it seems that something is up with the encoding translation. I'm not sure what we can do about it (I haven't encountered a lot of this stuff before), but maybe some light can be shed on the issue here.
EDIT:
As pointed out by @chip2n, it seems that decoding nyttigt-mellanma%25CC%258Al_proteinkakor.jpg twice results in nyttigt-mellanmål_proteinkakor.jpg. Could it be that something happened when fixing #7 ?

@patrikarvidsson , it could be indeed. Perhaps WPGraphQL is handling this in later versions. Are you able to share your /graphql api url so I can easily reproduce this? Or is it enough for me to upload an image with nyttigt-mellanmål_proteinkakor.jpg as a filename?
I'll get this fixed asap and add a test for this to prevent future regressions.
Thanks!

@TylerBarnes No problems. I'll send you a mail at your<EMAIL_ADDRESS>There are more than this occurrence so you might benefit from the actual api for testing.

This is fixed in<EMAIL_ADDRESS>Needed to check if the URL was already encoded before attempting to encode it. Your build still isn't succeeding because you have some images that legitimately 404. Once you update and run a build you should see errors about those. For now the build can't succeed past 404's so you'll have to fix those. Follow #70 if you're interested in allowing 404's. Cheers!

PS 404 images no longer fail the build in develop 🙌

PS 404 images no longer fail the build in develop 🙌

Fantastic! Thank you so much for looking into this so quickly!


Imports benbjohnson/testing and use it in web package

This PR refers to #3242
In this PR I:

[x] Imported benbjohnson/testing helpers in the util/testutil pacakage
[x] Used those helpers in the web package testsuite

This is a quick PR just to make sure I'm in the right direction. Feel free to comment.
ping @Gouthamve

Travis complains because the new file util/testutil/testing.go has no license text at the beginning.
The project benbjohnson/testing is MIT, so I think just adding the text in https://github.com/benbjohnson/testing/blob/master/LICENSE as a comment at the beginning will be OK.

Thanks 👍  :)


pip install assumes django-mssql 2.x.x -- that's bad for SQL2005/8

this package wraps django-mssql. the README says it was tested on django-mssql 1.6.x and MSSQL 2012 but should work on 2005/8. If you just pip install django-pymssql, the most recent version of django-mssql installs (2.x.x) . However, 2.x.x does not support MSSQL 2005/8, 1.6.x does. It would be helpful to add a comment to clarify this to the README as well as to specify the version in setup.py and/or add a requirements.txt. Something as simple as:
Note: MSSQL 2005/8 requires django-mssql 1.6.x

Yes, that makes sense. django-mssql 2.x.x didn't exist when I wrote that sentence.

django-mssql 2.x.x still doesn't exist. The latest stable release is 1.7. Django-mssql 1.8 will have a beta release very soon. The published version's MAJOR.MINOR will match the Django version it supports.

my mistake. django-mssql 1.7.x does not work for MSSQL 2005, not 2.x.x. I
noticed in your change log for version 1.6 it states 2005 is no longer
supported and at https://bitbucket.org/Manfre/django-mssql you state "SQL
2008/2008r2 are support by django-mssql 1.6.x.". 1.6.x seems to work for
accessing my 2005 server so far but I am querying only. The main issue was
with the use of OFFSET/FETCH for slicing. thanks
On Wed, Jul 8, 2015 at 3:39 PM, Michael Manfre<EMAIL_ADDRESS>wrote:

django-mssql 2.x.x still doesn't exist. The latest stable release is 1.7.
Django-mssql 1.8 will have a beta release very soon. The published
version's MAJOR.MINOR will match the Django version it supports.
—
Reply to this email directly or view it on GitHub
https://github.com/aaugustin/django-pymssql/issues/8#issuecomment-119582200
.

I don't think I removed all of the special logic for SQL Server 2005 from django-mssql 1.6; it mostly involved microseconds. The dropped support statement in that release was to notify that I don't test it anymore and won't fix any issues that crop up. Slicing and things involving the date/time data types are where things are likely to not work between different versions of django-mssql.

I'm going to close this issue because I don't see any action to be taken in django-pymssql. Let me know if I missed something.


Add Flyway to handle database schema migration

Currently, the backend is using typerom synchronize to true option to do database migration which is not ideal in production environments, so need to create a more robust pattern that should be production ready. Flyway seems to be a good candidate.

Agreed!  :)

On old growth I used a similar approach, but instead of baking the migration inside flyway, I just added the migrations as part of a config map. This way the init container is just a "template" and the migration will be tied to the application itself, making it easier to be copied/replicated by other projects.


scripts/pluginupdate: fix fetchgit indentation

Description of changes
see discussion in #195927
coc-spell-checker was removed since it was left out in #189788
nixpkgs-fmt --check pkgs/applications/editors/vim/plugins/generated.nix shows no diff

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

looks good to my eyes


What is the sampling frequency of trajectory data?

What is the sampling frequency of trajectory data?

The sampling frequency of the original (i.e., before preprocessing) trajectotry data is 1 second.


Use theme for thumbnail background

Description

The background color for thumbnails is hard-coded as black. This PR uses the theme to get the background color.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

Resolves https://github.com/napari/napari/issues/5498
How has this been tested?

[ ] all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

Based on my conversation with @psobolewskiPhD (here), this use of the UI setting needs to change because it may be different from what the Viewer is currently set on. However, I don't see how I can access what the viewer is currently set at. I could use some direction there.

I should also say that in its current state, this seems to be working for Labels and Points. Although for points, I think it just colors one pixel in the 32x32 thumbnail which is so small I can't see it.

I don't see how I can access what the viewer is currently set at. I could use some direction there.

@andy-sweet Can you provide any insight here?

I'd like to bring attention to the fact that we've been planning to remove the theme/canvas color connection, and instead have the canvas color be a Canvas field (once we have a proper canvas mode). Might not be relevant here, as the functionality here is still needed, but I just wanted to point it out :)

This should also respect background overwrite. The best option is to query canvas for background.
Also, if the layer is not additive, then the layer background should be used

I'd like to bring attention to the fact that we've been planning to remove the theme/canvas color connection, and instead have the canvas color be a Canvas field (once we have a proper canvas mode). Might not be relevant here, as the functionality here is still needed, but I just wanted to point it out :)

@brisvag  This will make it easier to make that change when the times since it will no longer be hard coded. Once a Canvas class exists, then we can swap it for the theme in this PR.

This should also respect background overwrite. The best option is to query canvas for background. Also, if the layer is not additive, then the layer background should be used

@Czaki what is the "background overwrite"? The best option is to query canvas - that doesn't exist yet, right? Layers have backgrounds? I didn't know this - where is that located?

Layers have backgrounds

If you select translucent blending on the Image or Labels layer, then you should use the value of colormap for 0 as the background (also if the bottom-most layer has such then you should use background from this layer).
As I think We need to change the thumbnail from property to the get_thumbnail(bg_color) method.


Merge Installation page with Quick Start page?

There is a lot of overlapping content from both pages, I believe we could merge them both in a way that we can have the "quick start" followed by the rest of the "installation" content.
I believe this should be done after these two PR's are completed so that no content is missed or we have double work.

https://github.com/snowpackjs/astro-docs/pull/32
https://github.com/snowpackjs/astro-docs/pull/16

@FredKSchott @itskitto @aFuzzyBear @jgil-r

The only difference is that the installation page briefly mentions node.js as a dependency. I can just add that to the top of quick-start page and completely get rid of installation page. Currently we have very similar information in /, /installation, and /quick-start pages. I mentioned in #32 that we can avoid repetitive information by making the sidebar headings just be headings or links that route to the first link of that specific group. For example, instead of Basic Concepts having its own page, it should just link to Project Structure.

@jgil-r I agree with the sidebar, but for the installation page, I believe it would be better to check PR #16, since @aFuzzyBear changed a lot of the page content.

Yeah, I'm not sure if we need a distinction between Installation and Quick Start, they seem to be one in the same. I think we can merge them in a way that's concise and to the point and then break out @aFuzzyBear's extended information into a "Deep Dives" section and link it in the Quick Start/Installation merge

Hey guys thats me made the changes to the install and in the index page, If we can merge them, idk what the best way for that would be, whatever you guys think is best, Once they are merged there is a few link adding that I need to do just to link them to other doc pages for reference,
thanks for your support team =)

Docs improved in https://github.com/snowpackjs/astro-docs/commit/d2027d928ee04d2af38bab39878c38f0681f422c to make this separation more clear


Trying to contribute

Hi @NathanWalker ,
I need your module to work with angular-cli but it doesn't work with the last version, i modified the module that i made, largely inspired by yours, to make it work with latest version of angular. You can find it here:
https://github.com/rhanbIT/nativescript-ng2-cli-magic
There is also a problem with the template you were using to create the nativesript project so i created a new one:
https://github.com/rhanbIT/nativescript-ng2-cli-magic-template
I would like to include tests and everything to make it right but following your contributing's guideline npm test doesn't work, any steps actually worked.
Could i have some guidenance?
I propose myself to maintain the module i created which is yours but only for angular-cli (i unfortunately don't have enough time to maintain for all types of projects).
Cheers from France

Forget to tell you about my config:
Node v6.6.0
Npm v3.10.3
I also implemented the auto installation of nativescript-sass if the file angular-cli.json specify that the project use sass. But i still change the extension file in StyleUrls to .css since NativeScript doesn't support .sass directly.

Is this project still live?

Hi @rhanbIT thank you so much helping here.
I had paused some developments here mainly because I hope some tighter integrations can occur with angular cli soon per: https://github.com/angular/angular-cli/issues/698#issuecomment-271227616
However it's hard to say how soon that may happen so it would probably be worth updating a few things to make sure it's compliant with latest cli. I am very busy at moment while also preparing to move from OR > CA so won't be much help for another month, but could definitely entertain some PR's.
@Jonatthu please take the above into consideration; definitely still live if a PR could be provided allowing it to be compliant with latest cli version with hopes that within a couple months the issue stated above will provide more direct integration with angular cli (which was my hope all along before I created this plugin).

Fixed here, note new repo and install:
https://github.com/wwwalkerrun/nativescript-ngx-magic


applyMiddleware corrupts schema with Apollo federation stub types

We are using Apollo federation https://www.apollographql.com/docs/federation/federation-spec/ where gateway combines two graphql schemas into one unified schema.
We have vanilla ordinary setup for it
We have type user in service A
@ObjectType()
@Directive('@key(fields: "id")')
export class User {
  @Field(() => Int)
  public id: number;

  @Field()
  public firstname: string;

  @Field()
  public lastname: string;
}

And we have type stub type User in service B
@ObjectType()
@Directive('@extends')
@Directive('@key(fields: "id")')
export class User {
  @Directive('@external')
  @Field(() => Int)
  id: number;
}

And we have type Equipment in service B that refers to the user
import { User } from './User';

@ObjectType()
export class Equipment {
  @Field(() => ID)
  id: number;

  // external type
  @Type(() => User)
  @Field({ nullable: true })
  owner?: User;

  @Field(() => Date)
  createdAt: Date;
}

By applying this trivial middleware in the service A
const doNothing: IMiddlewareResolver = async (
  resolve,
  root,
  args,
  context,
  info
) => {
  return resolve(root, args, context, info);
};

GraphQL will be unable to resolve external fields for the User. i.e.
This will work
query {
  equipments {
    id
    name
    owner {
      id
    }
  }
}

But this will start to fail
query {
  equipments {
    id
    name
    owner {
      id
      lastname
    }
  }
}

with error message
Cannot return null for non-nullable field User.lastname.
I was unable to pinpoint what is going on, but I see that the schemas ar slightly different after running applyMiddleware(doNothing)

@jekabs-karklins have you found solution?
I have similar schema design to yours and getting similar error. I was using v4.0.2 everything was working expected but recently I have update to latest version(v6.0.10) and then started getting this issue. I have also tested v4.0.3 seems like working everything as expected but not working in 5.0.0 and above

I have also tested v4.0.3 seems like working everything as expected but not working in 5.0.0 and above

Well, I tested and yes, the last working version is v4.0.3. I would like to know if there will be a solution, because working with a 2 years outdated version isn't ideal.
Also huge thanks, this lib is awesome.

hi guys have anyone found a solution?
it is been bugging me with graphql-sheild, resolveRefrence never get called in User service if applyMiddleware is used,
but if  removed everything working again.

I tried to applyMiddleware before adding the reference resolvers to the schema and I think that worked without any issues. So it could be a potential/workaround solution to our specific problem. So here is some example code:
 let federatedSchema = buildSubgraphSchema({
    typeDefs: gql(printSubgraphSchema(schema)),
    resolvers: createResolversMap(
      schema
    ) as GraphQLResolverMap<ResolverContext>,
  });

 federatedSchema = applyMiddleware(federatedSchema, logger);

 addResolversToSchema(federatedSchema, referenceResolvers);

if you try to applyMiddleware after adding the resolvers it ends up messing the federation schema and it doesn't resolve the referenceResolvers correctly.

@jekabs-karklins have you found solution?
I have similar schema design to yours and getting similar error. I was using v4.0.2 everything was working expected but recently I have update to latest version(v6.0.10) and then started getting this issue. I have also tested v4.0.3 seems like working everything as expected but not working in 5.0.0 and above

You can try out what @martin-trajanovski is suggesting

I found a solution. You need to check whether the resolver is one of the type fields for the Apollo Federation spec, and simply make your middleware a no-op when it matches.
(TypeScript)

function isFederationIntrospectionQuery({
  prev,
  key,
  typename,
}: GraphQLResolveInfo['path']): boolean {
  if (prev) {
    return isFederationIntrospectionQuery(prev);
  } else {
    return (key == '_entities' || key == '_service') && typename == 'Query';
  }
}

// ...

applyMiddleware(
      schema,
      async (resolve, root, args, context, info) => {
        if (isFederationIntrospectionQuery(info.path)) {
          // no-op
          return resolve(root, args, context, info);
        }

        // etc...

Could this logic get rolled into graphql-middleware, or some utility or option be added to make this easier?


scripts fail in download ?

failed: 1024 at download_archaea.pl line 49,  line 412.
failed: 1024 at download_bacteria.pl line 49,  line 3824.
failed: 1024 at download_viral.pl line 49,  line 854.
Thanks in advance ............

Do you have wget on your system?
Do you have write access to the folder you're in?

I am facing the same issue with bacteria.pl script where out of 2 million genomes I could only download 46K. Besides Protozoan genomes are only 96.
55.1_ASM1421705v1, , , naGCF_014217075.1, PRJNA224116, SAMN14342459, , na, 562, 562, Escherichia coli, strain=RM-103-CS, , latest, Chromosome, Major, Full, 2020/08/17, ASM1421707v1, icddr,b, GCA_014217075.1, identical, https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/014/217/075/GCF_014217075.1_ASM1421707v1, , , naGCF_014217095.1, PRJNA224116, SAMN14342460, , na, 562, 562, Escherichia coli, strain=RM-103-MS, , latest, Chromosome, Major, Full, 2020/08/17, ASM1421709v1, icddr,b, GCA_014217095.1, identical, https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/014/217/095/GCF_014217095.1_ASM1421709v1, , , naGCF_014217115.1, PRJNA224116, SAMN14342461, , na, 562, 562, Escherichia coli, strain=RM-103-WU, , latest, Chromosome, Major, Full, 2020/08/17, ASM1421711v1, icddr,b, GCA_014217115.1, identical, https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/014/217/115/GCF_014217115.1_ASM1421711v1, , , naGCF_014219485.1, PRJNA224116, SAMN15746396, JACLFO000000000.1, na, 562, 562, Escherichia coli, strain=EC4, , latest, Scaffold, Major, Full, 2020/08/17, ASM1421948v1, The Hong Kong Polytechnic University, GCA_014219485.1, identical, https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/014/219/485/GCF_014219485.1_ASM1421948v1, , , naGCF_014219525.1, PRJNA224116, SAMN15746395, JACLFN000000000.1, na, 562, 562, Escherichia coli, strain=EC3, , latest, Scaffold, Major, Full, 2020/08/17, ASM1421952v1, The Hong Kong Polytechnic University, GCA_014219525.1, identical, https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/014/219/525/GCF_014219525.1_ASM1421952v1, , , naGCF_014219545.1, PRJNA224116, SAMN15746393, JACLFL000000000.1, na, 562, 562, Escherichia coli, strain=EC1, , latest, Scaffold, Major, Full, 2020/08/17, ASM1421954v1, The Hong Kong Polytechnic University, GCA_014219545.1, identical, https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/014/219/545/GCF_014219545.1_ASM1421954v1, , , nafailed: 1024 at download_bacteria.pl line 62, <IN> line 46255.

I have enough space on my system I can assure you that and writing permission with wget as well
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       7.3T  4.2T  2.8T  61% /home

anyone @mw55309 @bergeycm @xgnusr @sjaenick ?


Implement chapman_oai_dc

Make mapping dictionary more explicit, including in helper methods. This includes adding collate_values() and source_metadata_values() to break apart the collation from the fetching of values that was previously contained in collate_fields(). In this way source_metadata values can be collated with values returned from functions.
We're returning to the convention of prepending map_ on all function names that return a value that will be set in the mapping dictionary.

Hi @timfrazee! Take a look here and tell me if you think this passes muster. And then pass the mustard.


Problem with japanese characters

When running my app with japanese language all LabelStyle.Text display texts changed to squares. Here is a text string: "Mapsuiは最高です". Chinese (Simplified and Traditional) and Korean are also affected. Bulgarian, Russisn and Ukrainian on the other hand work. So only asia languages seems to be affected. Does Mapsui not use UTF-8? Or is just the Font not able to display these characters? Is there a way to change the Font within Mapsui to test this?

Not sure if this applies but here is a stackoverflow answer related to Japanese characters from @Sebastian1989101 https://stackoverflow.com/questions/76389602/how-to-get-sktypeface-fromfamilyname-to-return-a-font-for-japanese-korean-chin

Not sure if this applies but here is a stackoverflow answer related to Japanese characters from @Sebastian1989101 https://stackoverflow.com/questions/76389602/how-to-get-sktypeface-fromfamilyname-to-return-a-font-for-japanese-korean-chin

Yep, that’s my own reply after a bunch of thinkering with it that solved it.

@Sebastian1989101 ah, thanks for you quick reply. So, could this issue be closed or does Mapsui need to improve something as well?

I think it won’t be an issue with 4.0 anymore anyway as the code for the font loading is different when I compare it to the implementation in 3.x. However it might be useful for some folks when trying to include these languages.
But yes, the issue can be closed. :)


[9.x] Include validation errors in ValidationException::$message

This is a re-submit of #35496 against master rather than the 8.x branch.
The default exception message for validation exceptions is "The given data was invalid." which is not particularly descriptive. There are lots of times when I'm running tests with exception handling turned off and I find I need to either dd() the validation messages or turn on exception handling and add a call to assertSessionHasNoErrors() to find the issue.
This PR adds a summarize() static method to the validation exception that includes the first error message, and if there are more than one, a count of the additional errors. That way, instead of "The given data was invalid." the message will look something like:
"The first name field is required (and 2 more errors)"

The summarize method could still be added to 8.x IMO, just modified to return the same thing it always used to.

The summarize method could still be added to 8.x IMO

I'm not really sure what the benefit of adding that in 8.x would be, though. The value really comes from having a more descriptive error message by default… I think it's fine to just wait for 9.x.

The benefit would be the ability to customize the message, as is possible in this PR.

Would you do something like pass it a callback? I don't see how having a summarize() method on the existing exception does much without having to subclass a bunch of things, in which case you can just add your own logic to the constructor…
To be clear, the summarize() method is just there to set the string that is passed up to the parent constructor. It's not meant to be public-facing.

I like this change, but I feel it should have been mentioned in the upgrade guide for 9.0. All my feature tests started failing because they were checking for the old exception message. Pretty low impact, but there are smaller changes than this in the upgrade guide.

@miken32 can you PR that to the Laravel 9 upgrade guide?

Also, in general I suggest to never rely on exception messages because they're suppose to be fluid and not part of any public API. Instead check on the exception class type itself.

@driesvints I'll give it a shot. I don't use the value for public consumption, just in feature testing where I expect a certain JSON response to my requests. For unit testing, agreed; I just check for a ValidationException being thrown.

This change break our tests where we were expecting message not to be dynamic.
$test = fn($body, $errors) => $this
    ->actingAs($user)
    ->postJson("api/...", $body)
    ->assertStatus(422)
    ->assertExactJson([
        'message' => 'The given data was invalid.',
        'errors' => $errors,
    ]);

Would be nice if PR had included ability to disable this feature.

Please do not rely on asserting exception messages as these don't fall under any BC promise.


Please add these options

I really sloppily added (or attempted to add) the prodigy optimizer and also auraloss here.
Would you mind taking a look at the changes and adding the option to use prodigy and auraloss a better way in the official repo? I apologize as my coding knowledge is limited and I am not much help.
I would love to have these two things officially added as config options!

Do prodigy and auraloss help with training? In your experiments, were they able to effectively improve performance?

Prodigy basically handles the learning rate for you, and I've heard that it greatly improves performance. Auraloss doesnt necessarily improve training performance but it is more akin to human hearing and can give much better results than MSE or L1 loss functions. It can sort of repair the instrumental after the vocal removal to an extent.

never mind they are already added in zfturbos training repo which has scnet so Ill close this.


Potential API Bug

knowledge database API
**
I got a knowledge database API got with 403 {"message":"Forbidden"}. I have check endpoint restriction, header and payload respectively and still got the bug. Would you mind if you can help me out please? My apology if the issue format is in a mess.

@dezhouc2 Thank you for reporting the bug. Could you check whether the API info shown in bedrock claude chat indicates the same values as the values shown in AWS management console?

Would you mind if you can be a bit more specific? Is there a jupyternote book to demonstrate the interaction with amazon bedrock knowledge database using API as above? thank you

Currently we don't have it. I'd just like to know whether the settings shown in bedrock-claude-chat and management console are the same or not because I cannot reproduce the issue.

Thanks for quick response. I apology for my confusion. What settings within bedrock-claude-chat? For each bot console, I have its own API Endpoint and API key respectively generating from bot console. How this relates to management console?(May you be more specific?) I have google a lot and still hard-stuck.

Currently we don't have it. I'd just like to know whether the settings shown in bedrock-claude-chat and management console are the same or not because I cannot reproduce the issue.

Thanks for quick response. I apology for my confusion. What settings within bedrock-claude-chat? For each bot console, I have its own API Endpoint and API key respectively generating from bot console. How this relates to management console?(May you be more specific?) I have google a lot and still hard-stuck.

Hi t

@dezhouc2 Thank you for reporting the bug. Could you check whether the API info shown in bedrock claude chat indicates the same values as the values shown in AWS management console?

Yes, it's the same. However, I still got 403 bug while implementing API.

ID in the above image matches my knowledge database URL

Could you check the api key value is the same as the one can be fetched from management console (API Gateway)?
Or you can check debug logs (cloudwatch logs)

Could you check the api key value is the same as the one can be fetched from management console (API Gateway)?
Or you can check debug logs (cloudwatch logs)

I have checked api key value which is the same from API Gateway. I also check cloudwatch but do not find anything useful. Thank you again for your response


bug: Regular classes that inherit dataclass do not get dataclass parameters

Here is failing test case
from griffe.tests import temporary_visited_module

code = """
from dataclasses import dataclass

@dataclass
class Base:
    a: int
    b: str

@dataclass
class Derived1(Base):
    c: float

class Derived2(Base):
    d: float
"""

with temporary_visited_module(code) as module:
    params1 = list(module["Derived1"].parameters)
    params2 = list(module["Derived2"].parameters)
    assert [p.name for p in params1] == ["a", "b", "c"]
    assert [p.name for p in params2] == ["a", "b"] # failing

Thanks, nice catch. The new approach will fix that too.