training no convergence, why?

@bgshih I create 6400 training images with 4 letters or digits, whose resolution is 274*74. Then I train 100 epochs with batch_size of 64. However, it shows no convergence. The following log tells in detail.
would u pls tell me what's wrong with it? thanks
2017-08-23 18:22:11,993 - root - DEBUG - [epoch:100/100 batch:10/100 batch_size:64] Loss: 21.5575119019
2017-08-23 18:22:12,519 - root - DEBUG - [epoch:100/100 batch:20/100 batch_size:64] Loss: 19.4152982712
2017-08-23 18:22:13,048 - root - DEBUG - [epoch:100/100 batch:30/100 batch_size:64] Loss: 21.3406339645
2017-08-23 18:22:13,595 - root - DEBUG - [epoch:100/100 batch:40/100 batch_size:64] Loss: 21.8175168991
2017-08-23 18:22:14,140 - root - DEBUG - [epoch:100/100 batch:50/100 batch_size:64] Loss: 24.2895008087
2017-08-23 18:22:14,677 - root - DEBUG - [epoch:100/100 batch:60/100 batch_size:64] Loss: 18.8902362823
2017-08-23 18:22:15,221 - root - DEBUG - [epoch:100/100 batch:70/100 batch_size:64] Loss: 22.1881462097
2017-08-23 18:22:15,761 - root - DEBUG - [epoch:100/100 batch:80/100 batch_size:64] Loss: 23.4686908722
2017-08-23 18:22:16,299 - root - DEBUG - [epoch:100/100 batch:90/100 batch_size:64] Loss: 24.4427461624
2017-08-23 18:22:16,839 - root - DEBUG - [epoch:100/100 batch:100/100 batch_size:64] Loss: 19.2434511185
2017-08-23 18:22:16,839 - root - DEBUG - Start val
2017-08-23 18:22:17,521 - root - DEBUG - -------------------------- => , gt: vbys
2017-08-23 18:22:17,522 - root - DEBUG - -------------------------- => , gt: p7ug
2017-08-23 18:22:17,522 - root - DEBUG - -------------------------- => , gt: schy
2017-08-23 18:22:17,522 - root - DEBUG - -------------------------- => , gt: vmts
2017-08-23 18:22:17,522 - root - DEBUG - -------------------------- => , gt: x7dk
2017-08-23 18:22:17,522 - root - DEBUG - -------------------------- => , gt: kiyz
2017-08-23 18:22:17,522 - root - DEBUG - -------------------------- => , gt: y9cz
2017-08-23 18:22:17,522 - root - DEBUG - -------------------------- => , gt: vdre
2017-08-23 18:22:17,522 - root - DEBUG - -------------------------- => , gt: hoxs
2017-08-23 18:22:17,522 - root - DEBUG - -------------------------- => , gt: etkc
2017-08-23 18:22:17,522 - root - DEBUG - Test loss: 20.130669, accuracy: 0.000000

@white2018can you share how to solved it?


test: Always wipe the test-build dir for aomdec

That should make sure that stray defaults won't get in the way (assuming it is a problem at it is for the cmake crate).

It is. This looks OK, though we could be a bit more clever and check if the git rev changed.

https://github.com/xiph/rav1e/pull/193/files#diff-0b83f9dedf40d7356e5ca147a077acb4L33 would do but it does not right now because of a leading space.


[CI] Adding github actions for pinot tests

Description
Considering the slowness experienced recently from Travis, Github Action is an alternative CI framework. Also its Usage Limits is much larger than what Travis provides(20 vs 5 Concurrent jobs) and single container is faster than Travis (Based on time used on unit test, it's about 20%+ faster, 30min vs 38min).
This PR:

Add Pinot Tests/Quickstart in Github Action as a replacement of Travis.
Only triggered by PR, not by any branch push

Followup PR:

Once fully tested, we can remove PR tests in Travis and use Github Actions for  PR tests.
For Branch deploy related stuffs, we can still keep them in Travis.

+1 on 20 concurrent jobs.
@jackjlli Can you review this PR and make sure that our CRON job is also correctly migrated to Github Action?

Let's keep both Github Action and Travis running for a while until we feel Github Action is stable enough to kill Travis completely.

Agreed, we can let both run for a while then decide.

Let's keep both Github Action and Travis running for a while until we feel Github Action is stable enough to kill Travis completely.

Agreed, we can let both run for a while then decide.

As long as both don't push binaries to bintray


Add health check support for Qdrant client

Description
This PR Adds health check support for Aspire.Qdrant.Client.
We need to import Testcontainers for ConformanceTests.
Fixes #5768
Checklist

Is this feature complete?

[X] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[X] Yes
[ ] No

Did you add public API?

[X] Yes

If yes, did you have an API Review for it?

[X] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[X] No

[ ] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[X] No

Does the change require an update in our Aspire docs?

[X] Yes

Link to aspire-docs issue:

[ ] No

Microsoft Reviewers: Open in CodeFlow

/azp run

I still have this problem https://github.com/dotnet/aspire/pull/6432#issuecomment-2429935302
@eerhardt can you help me fix that?

I still have this problem #6432 (comment) @eerhardt can you help me fix that?

From the root of your repo, run the following and ensure you get the same output:
❯ dotnet nuget list source
Registered Sources:
  1.  dotnet-public [Enabled]
      https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json
  2.  dotnet-eng [Enabled]
      https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json
  3.  dotnet9 [Enabled]
      https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json
  4.  dotnet-libraries [Enabled]
      https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-libraries/nuget/v3/index.json
  5.  dotnet9-transport [Enabled]
      https://dnceng.pkgs.visualstudio.com/public/_packaging/dotnet9-transport/nuget/v3/index.json

If any of those are disabled, make sure you enable them, usually in VS: Tools => NuGet Package Manager => Package Manager Settings => Package Sources.

Thanks a lot.


Use ResourcesApplied condition of ManagedResource to check ControllerInstallation Installed condition

What this PR does / why we need it:
With this PR the gardenlet uses the ResourcesApplied condition of the ManagedResource to determine the Installed condition for a given ControllerInstallation.
Also a column HEALTHY is added to the ControllerInstallation table converter.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Depends on gardener-resource-manager#32
Release note:

The gardenlet now uses the `ResourcesApplied` condition of the ManagedResource to determine the `Installed` condition for a given ControllerInstallation.

PR is merged, please rebase/revendor :)

Done, PTAL.
I guess, we should also do a release of gardener-resource-manager and use the new version in seed-bootstrap/images.yaml to incorporate the changes of https://github.com/gardener/gardener-resource-manager/pull/31, right?

Yes, agreed, can you trigger it?

Yes, will do

I released<EMAIL_ADDRESS>revendored the release and rebased onto master.
Please take another look :)


Feedback backend plugin - fix the feedback url in mail and jira description

Describe the bug
The feedback url in mail body and jira description is coming as undefined when created via api

Expected Behavior
The feebback url should contain the proper hostname so that the link could be formed.
What are the steps to reproduce this bug?

Send a post request to create a feedback using api
In mail check the url of View on Backstage link, it is having undefined in hostname

I am working on fix for this


Cufflinks produces very strange output when MicroRNA is annotated inside a intronic region of a gene

I first posted this problem on the cufflinks mailing list but no replies yet ( https://groups.google.com/forum/#!topic/tuxedo-tools-users/_E94jkdvMak )
The problem we are experiencing is that in GRCH38 annotation from refseq the gene HLA-B is annotated on chromosome 6 and in between its exons 4,5 there is an MiRNA annotated called MIR6891. The quantification with Cuffquant goes terribly wrong here as the table below will show:

HLA-B 1340.16 994.534<PHONE_NUMBER>.58 1266.27 2167.43 2692.21
MIR6891<PHONE_NUMBER>27<PHONE_NUMBER>91<PHONE_NUMBER>7.6 114646

As you can see i got counts for the MIR which go through the roof while the HLA-B gene is relatively low expressed compared to the MIR. When checking in IGV or UCSC genome browser i see that there is not a single read aligning to the MIR but a lot of split reads cover the region. Our current guess is now that these split reads are all asigned to the MIR as well, while the actual bases are aligned to exon 4 and 5 of the HLA-B gene. I know this is probably not easy to fix, but maybe a good idea to distribute a GTF file containing only MRNAs and LINCRNA. Or something like that, i wonder if other users experienced the same issue and how they circumvented the issue. Thanks already!

yes, I found this too. When the genes are short (shorter than reads' length), cuffnorm given a  VERY VERT VERT large FPKM. Hope fixing this.


legend in the wrong order in bar chart

Hi there,
Sometime, the legend order does not match the bar order.  For instance, in http://jsfiddle.net/7wwccrbe/ the legend shows the order "Hypermarkets Supermarkets" and the bars are presented in the "Supermarkets Hypermarkets" order.
Is there a workaround for this very small issue?
Fantastic library by the way.
didier amyot

Hi didier. I just submitted a pull request that fixes the legend order to match the bar order. Hopefully that solves your problem!

Many thanks joannekoong, I am a little bit a shame not fixing the issue myself but I did not have time to do it.
thousands thanks again,
didier

Hello! Has this issue been resolved (or has a workaround been found)? I am running into the same problem with a stacked bar chart.
@didiercrunch @joannekoong

I'm pretty sure there's no one maintaining this project at the moment. Development seems to have stopped.

@jeffcj  Ahh, yes, I see that now on the main page. Thanks for the heads-up. That's unfortunate.


typo, page 232, line 6, the 2nd -' should be +'

for version Oct 16, 2022
btw, noticing p(z|x,y) = p(z|x) is very helpful to make CEB intuitive, otherwise eq I(x;z|y) = I(x;z) - I(y;z) may be false.

thanks, fixed


Add option to heat_control component to set min cycle duration

Description:
This commit adds a new config option min_cycle_duration which when specified will add a minimum duration that the thermostat must keep the switch in each state prior to switching it either off or on. The motivation is primarily for AC mode, because window and in-wall AC units are not nearly as efficient during the first few minutes of operation. This gives users a tunable to fine tune exactly how frequently heat control can power cycle their devices.
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#733
Example entry for configuration.yaml (if applicable):
thermostat:
  platform: heat_control
  name: Study
  heater: switch.study_heater
  target_sensor: sensor.study_temperature
  min_temp: 15
  max_temp: 21
  target_temp: 15
  min_cycle_duration:
     days: 2
     hours: 1
     minutes: 10
     seconds: 5
     milliseconds: 20

Checklist:
If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.io

If code communicates with devices, web services, or a:

[X] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[X] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

This commit adds a new config option to the heat_control thermostat
component, min_cycle_duration. Some heaters and/or ACs don't like
being constantly cycled on and off. Prior to this patch the
heat_control component can end up cycling the switch quite
frequently. (depending on how quickly the temperature changes) The
new option added is used for setting a minimum duration that must
have elapsed in either the on or off state before the thermostat will
send the service call to cycle the switch. This should enable users to
hand tune how frequently heat_control can switch the device on or off
to best suit the device being used.

Looks good. One minor comment but then it's ready to go.

The latest revision just updated the logic to return if not long_enough instead of adding it to all the checks later.

This would be a very welcome pull for heaters as well, had mine toggling on and off in a loop every few minutes yesterday.


It would be great to load private key from an environment variable

It would be horrifying to have a private key in an an evironment variable.


Commands from operationId

Restish generates convenient command names such as "messaging-email-address-status-get".
However, our OpenAPI spec defines operationId for all the operations. Is it possible to have Restish use those instead?

@ServerlessArchitect the name should be getting set from the operation ID, via this code: https://github.com/danielgtaylor/restish/blob/main/openapi/openapi.go#L214
Do you have a short example which exhibits the incorrect behavior that I could debug?

@ServerlessArchitect

Just to confirm, are you saying the command names are still based on my operationIds, just normalised?

Yes, it is based on the operationId if present. It is also possible to override it via x-cli-name.


MacOSX creates background threads during tests

Left-over thread detected (and terminated): Thread[Poller SunPKCS11-Darwin,1,] (stack trace is a snapshot location).

com.carrotsearch.randomizedtesting.ThreadingError: Left-over thread detected (and terminated): Thread[Poller SunPKCS11-Darwin,1,] (stack trace is a snapshot location).
at __randomizedtesting.SeedInfo.seed([3E43D452F3275FF6:E80645A9BFCFEBF6]:0)
at java.lang.Thread.sleep(Native Method)
at sun.security.pkcs11.SunPKCS11$TokenPoller.run(SunPKCS11.java:692)
at java.lang.Thread.run(Thread.java:680)

There is a useful list of classes and methods spawning their own background daemon threads in Tomcat's JreMemoryLeakPreventionListener class.


BUG: Series.copy() with empty series loses dtype

Modin version checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest released version of Modin.

[X] I have confirmed this bug exists on the main branch of Modin. (In order to do this you can follow this guide.)

Reproducible Example
import modin.pandas as pd

ser =  pd.Series(range(3))

res = ser[:0].copy()
assert res.dtype == ser.dtype  # <- nope!

Issue Description
dtype should be preserved
Expected Behavior
NA
Error Logs

Replace this line with the error backtrace (if applicable).

Installed Versions

Replace this line with the output of pd.show_versions()

Our current implementation defaults to pandas on empty dataframes/series.
So this bug boils down to ser[:0]._to_pandas() always producing object dtypes, which in turn is caused by Modin DataFrame object producing an empty pandas DataFrame without specifying any dtypes (and internal query compiler in that case seems to have wrong dtypes, too).


global pip (--system ...) doesn't work in GitHub Codespaces

Bug
global pip (--system ...) doesn't work in GitHub Codespaces
System

VSCode:
Version: 1.89.0
Commit: b58957e67ee1e712cebf466b995adf4c5307b2bd
Date: 2024-05-01T02:15:54.732Z
Browser: Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
uv 0.1.39

Reproduce

Open a GitHub Codespace

.devcontainer/devconainer.json:{
	"name": "Python 3 on Debian 12",
	"image": "mcr.microsoft.com/devcontainers/python:1-3-bookworm",
	"features": {
		"ghcr.io/va-h/devcontainers-features/uv:1": {}
}

Terminal input: uv pip install prettytable --system
Note: prettytable is just an exemple

Logs
@Malix-off ➜ /workspaces/Fork (master) $ uv pip install prettytable --system
Resolved 2 packages in 2ms
error: Failed to install: prettytable-3.10.0-py3-none-any.http.whl (prettytable==3.10.0)
  Caused by: failed to create directory `/usr/local/lib/python3.12/site-packages/prettytable-3.10.0.dist-info`
  Caused by: Permission denied (os error 13)

Note: prettytable is just an exemple

Hi! It looks you don't have the necessary permissions to write to the system packages?

Probably works in pip because pip falls back to installing with --user if the site-packages directory isn't writeable.

Hi! It looks you don't have the necessary permissions to write to the system packages?

Indeed, probably like that in GitHub Codespaces, you're right.

--user

Is that an equivalent for sync?
@Malix-off ➜ /workspaces/Fork (master) $ uv pip sync requirements.txt --user
error: pip-sync's `--user` is unsupported.

No, we don't support --user right now, since it can generally be replaced by a virtual environment. There are some open issues tracking it but we haven't committed to adding it.

So what would be the workaround to pip sync without virtual environment (devcontainer is a good example)

I think you basically need to use a virtualenv in that case with uv right now. I believe you can use virtual environments in devcontainers? Like it is possible, right?

I think you basically need to use a virtualenv in that case with uv right now. I believe you can use virtual environments in devcontainers? Like it is possible, right?

Yep, currently you need a venv to do that, and yep, it is definitely possible, but adds an unnecessary virtual environment bloat (since we're already in a containerized environment)

No, we don't support --user right now, since it can generally be replaced by a virtual environment. There are some open issues tracking it but we haven't committed to adding it.

I didn't find any issue about it containing "user" "-u" "--user", do you know if it has been deleted?

GitHub Codespaces probably doesn't let you access to the devcontainer system (immutability)
In the case of devcontainers, you probably indeed would want to use the --user flag (#2077)


combo Line and Bar (with two Y axes) ?

Is it possible to combine XYChart and CategoryChart in one Chart?

Sorry, no it's not possible. The closest thing is a category chart with line style rendering for one of the series. See BarChart09.


Implementing Padding support

I've added nice paddings for the demo dashboard too, makes it look a little better.

There have been large changes to the codebase since we started (moving of files) and it would be unfair to expect you to rebase and resolve the conflicts.
Therefore I have taken what you started and implemented it in #166
Thank you again for getting this started!

Thank you!
Sorry, I totally forgot about my open pull-requests on github. Im deep in my finals right now and might resume work on github after them :)

That is no problem at all @infinytum, best of luck with the finals! I will be more than happy to resume working with you once you pass all your exams ;)


First implementation of best location for legends

Hi,
Here is a first trial to implement the "best" legend location. If you are interested... Any improvements are most welcome.

Two tests are failing:

the one I have created to test different legend locations png pdf
text_overlay png pdf

@nschloe What do you think of this implementation?

Don't worry about linthub too much, it's not a required check anyways.

The code looks good otherwise. Perhaps two lines of documentation would help, something along the lines of

To determine the actual position of the legend, check which corner (or center) of the legend is closest to the corresponding corner (or center) of the axes box.

I have corrected what you propose. Thanks.
What do you think of my remark on the anchors of the center left and the center right legend positions? I think when the legend is at the center left position, the anchor should be west.

Yes, I think you're right there. Would you fix that?

Also, can you check what changed with the text_overlay test?

Yes, of course, I will. I do it tomorrow.

The difference in text_overlay is (obviously) the legend position. The selected legend position is best in the example so before my update, the legend was upper right by default and now, it is upper left as matplotlib does.
Here the old version of the text_overlay example (acid_old_version.pdf) and here the new version
(acid_new_version.pdf).

Two examples fail:

the best_legend_location: here the reference plot and here the new PDF plot.
the legends2: here the reference plot and here the new PDF plot

The first one looks good but the second one is ugly with the legend location 5 (right). I suggest to change the anchor 'west' to 'east' for this position too.

I suggest to change the anchor 'west' to 'east' for this position too.

I agree.
(Also, I've just merged another PR that changed many phashes. Sorry for the conflict, but hopefully it's easily resolved.)

No problem for the other PR. :-)
Here is the new legend2 test with the new anchor position. It looks much better so I change the hashes.

Finally, it works! :+1: I have squashed my commits into three commits.

Thanks for the nice contribution!


How to start at a specific directory?

When you open the directory picker using the method described, I want it to open at a specific place, not wherever the user left it the last time. The default behavior is inappropriate and unintuitive. I'm not going to ask my users to traverse the entire directory tree over and over to get where they want to go. I can't put this in production.
How to start at a specific directory?
https://stackoverflow.com/questions/30115263/open-specific-directory-using-storage-access-framework

This is quite possibly the single worst API I've ever had to deal with, right up there with fragments, content resolver and alarm manager. Why must you make my life harder, Google?

This sample has been deprecated/archived (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests.


Is JAMI able to read PSI-MI XML3.0?

I recall being told my Marine that it could, but this needs tested.
I see ftp://ftp.ebi.ac.uk/pub/databases/intact/current/psi30/ now exists, I will test using this.

Yes, confirmed by Marine and tests on IntAct data.


provide phantomjs via rubygem

this removes the obs dependency for the deb package and also
enables running local rspec without having to care about providing
phantomjs
Signed-off-by: Maximilian Meister<EMAIL_ADDRESS>

failing travis will be fixed by https://github.com/SUSE/Portus/pull/1120


Error from 'dynamic-config-client-updater' updater: Field 'USERVER_HTTP_PROXY' is of a wrong type. Expected: stringValue, actual: objectValue

Hey guys,
when connecting a dynamic-config-client-updater to a config server that's configured to use a postgresql db this error appears:
tskv    timestamp=2022-08-26T17:33:41.127367    level=ERROR     module=DoRun ( third_party/userver/core/src/components/run.cpp:164 ) task_id=0       thread_id=0x00007F1E59D55AC0    text=Loading failed: Error from 'dynamic-config-client-updater' updater: Field 'USERVER_HTTP_PROXY' is of a wrong type. Expected: stringValue, actual: objectValue (std::runtime_error) tskv    timestamp=2022-08-26T17:33:41.129100    level=ERROR     module=DaemonMain ( third_party/userver/core/src/utils/daemon_run.cpp:72 )   task_id=0       thread_id=0x00007F1E59D55AC0    text=Unhandled exception in components::Run: Error from 'dynamic-config-client-updater' updater: Field 'USERVER_HTTP_PROXY' is of a wrong type. Expected: stringValue, actual: objectValue Unhandled exception in components::Run: Error from 'dynamic-config-client-updater' updater: Field 'USERVER_HTTP_PROXY' is of a wrong type. Expected: stringValue, actual: objectValue
It's expecting a string but config_value is a json column.
The error doesn't happen if switching to the dynamic_config_fallback.json file there the value of USERVER_HTTP_PROXY is correctly a string.
Thanks

Thanks for the bug report! Looks like we also need to change the tests of the service, to catch such errors early

Added a test and fixed the invalid values in DB. The test is not perfect, but does the job.
Once again, many thanks for the bugreport!


ntr: decreased protein localization to mitotic spindle during anaphase

PMID:16920624
decreased protein localization to mitotic spindle during anaphase

decreased protein localization to mitotic spindle during anaphase FYPO:0007729

just so you know, this wasn't a child of
decreased protein localization to mitotic spindle
also we could add a synonym to
FYPO:0007729
decreased protein localization to elongating mitotic spindle

moved it (one of these days I'll figure out what does and doesn't get inferred ...)
synonym will be related because spindle elongation isn't restricted to anaphase


fix proxy timeout

Codecov Report

Merging #50 (6d7f636) into main (da87e39) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #50   +/-   ##
=======================================
  Coverage   22.52%   22.52%
=======================================
  Files          10       10
  Lines         657      657
=======================================
  Hits          148      148
  Misses        493      493
  Partials       16       16

Flag
Coverage Δ

macos-latest
22.52% <ø> (ø)

ubuntu-latest
22.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Feature request: Check for probes at same position during calculation

Hi!
I've run into this problem a couple of times. When running a local bake it ends up failing at the end since two probes are at the same position. This happens because either the probe layout adds a probe where there's a pinned probe already (unlucky) or I accidentally e.g added two dynamic openings at the same place (I think the layout might place probes at dynamic openings as well if you're unlucky?).
It would be nice if you could get a warning if this problem would occur after the calculation in UE since it's a bit time-consuming to get it after an entire bake.

Thanks for the report! I agree this is really annoying behavior.
In the interim, if you're willing to write a little XML parsing code, you could detect this duplicate probe problem on your own by parsing through the probe list inside and removing any duplicate entries you find before submitting the bake.

Yes, I'll do that. Thank you!


[BUG] Accepting prereleases as valid python version

Reference Issues/PRs
Fixes: https://github.com/sktime/sktime/issues/7517
Make "rc" python version recognizable during python version checking.
Introducing a parameter prereleases=True
The following code snipped now returns true:
"3.11.0rc1" in SpecifierSet(">3.8", prereleases=True)

Does your contribution introduce a new dependency? If yes, which one?
No
What should a reviewer concentrate their feedback on?
On the tests regarding checking python versions.
PR checklist
For all contributions

[x] I've reviewed the project documentation on contributing
[x] I've added myself to the list of contributors.
[x] The PR title starts with either [ENH], [CI/CD], [MNT], [DOC], or [BUG] indicating whether
the PR topic is related to enhancement, CI/CD, maintenance, documentation, or a bug.

For code contributions

[ ] Unit tests have been added covering code functionality
[x] Appropriate docstrings have been added (see documentation standards)

I added a super minor change to mirror the exact code of sktime. (it was just an improved error message)

Could you kindly add the tests here that are also present in the sktime mirror of this?
Given that we will deduplicate with this as the ultimate location.

Solved :)


ID of new FAQ not rendered in Popup

Describe the bug
After creating a new FAQ as a tutor, the ID of the new FAQ is not rendered inside the Popup, instead the template placeholder "{{ id }}" is shown.
To Reproduce
Follow the steps provided in PR #9477 and notice the popup after creating a new FAQ as a tutor.
Expected behavior
The template placeholder "{{ id }}" should be replaced by a valid ID of the corresponding FAQ
Screenshots

Which version of Artemis are you seeing the problem on?
Artemis v7.6.1 with PR #9477
What browsers are you seeing the problem on?
Chrome
Additional context
No response
Relevant log output
No response

This issue was already fixed in the PR #9477, so i close this issue


Large file rdamsa fuzzing azcopy issue

Information

Onefuzz version: 4.0.0
OS: Windows

Provide detailed reproduction steps (if any)

Submit onefuzz radamsa job with an input folder containing large file ~75mb.
rdp into generator_generator task
open event viewer to see below error

Expected result
fuzz successfully.
Actual result
got and error in event viewer, below is the log.

Sometimes of these errors are transient. Can you post the console output when the upload fails?


Docs: Keep Ghost running

We need to update the install documentation to cover the steps of keeping Ghost running.
There are loads of ways to do this, so our guide should cover one simple way.
I think we ought to also cover how to get Ghost running on a domain name.
So the most straight forward configuration to setup ghost to respond to my-ghost-blog.com and run after SSH exit... whatever that may be.

It doesn't works for me :/
And I tried with pm2, forever, ghost as service...

@roadev, for support please use the forum :)


[BUG]: model-configuration from document

Not really sure where this came from. In the GoLLM logs I see:
2024-06-07 15:51:32 [INFO] [67fe2b03-e8e0-4388-bb82-ee1c7f4ea4d6] stdout: Reading model config from research paper:  [software.uncharted.terarium.taskrunner.service.Task:371]
2024-06-07 15:51:32 [WARN] [67fe2b03-e8e0-4388-bb82-ee1c7f4ea4d6] stderr: Error: Error decoding JSON: Expecting property name enclosed in double quotes: line 1 column 11 (char 10) [software.uncharted.terarium.taskrunner.service.Task:384]
2024-06-07 15:51:32 [INFO] [67fe2b03-e8e0-4388-bb82-ee1c7f4ea4d6] stdout: Modelling the COVID-19 epidemic and [software.uncharted.terarium.taskrunner.ser

While the follow errors were propagated into the HMI:

Failed: /usr/local/lib/python3.10/site-packages/pydantic/_internal/fields.py:149: UserWarning: Field "model_cards" has conflict with protected namespace "model". You may be able to resolve this warning by setting model_config['protected_namespaces'] = (). warnings.warn( Error: Error decoding JSON: Expecting property name enclosed in double quotes: line 1 column 11 (char 10) from text { { "conditions": { "no_intervention": "No social-distancing countermeasures were applied", "mild_intervention": "Social-distancing countermeasures had a mild effect", "strong_intervention": "Social-distancing countermeasures were stronger", "very_strong_intervention": "Social-distancing countermeasures were very strong", "loss_of_immunity": "Recovered individuals can become susceptible again after day 50", "increased_testing": "A wider testing campaign is launched after day 38" }, "parameters": [{ "id": "alpha", "value": { "no_intervention": 0.422, "mild_intervention": 0.285, "strong_intervention": 0.200, "very_strong_intervention": 0.057, "loss_of_immunity": null, "increased_testing": null } }, { "id": "beta", "value": { "no_intervention": 0.0057, "mild_intervention": 0.0057, "strong_intervention": 0.0057, "very_strong_intervention": 0.0057, "loss_of_immunity": null, "increased_testing": null } }, { "id": "gamma", "value": { "no_intervention": 0.285, "mild_intervention": 0.171, "strong_intervention": 0.086, "very_strong_intervention": 0.057, "loss_of_immunity": null, "increased_testing": null } }, { "id": "delta", "value": { "no_intervention": 0.0057, "mild_intervention": 0.0057, "strong_intervention": 0.0057, "very_strong_intervention": 0.0057, "loss_of_immunity": null, "increased_testing": null } }, { "id": "epsilon", "value": { "no_intervention": null, "mild_intervention": null, "strong_intervention": null, "very_strong_intervention": null, "loss_of_immunity": null, "increased_testing": 0.200 } }, { "id": "theta", "value": { "no_intervention": null, "mild_intervention": null, "strong_intervention": null, "very_strong_intervention": null, "loss_of_immunity": null, "increased_testing": null } }, { "id": "zeta", "value": { "no_intervention": null, "mild_intervention": null, "strong_intervention": null, "very_strong_intervention": null, "loss_of_immunity": null, "increased_testing": null } } ] }

Unreproducible


[Observable tasks] add netty related indicators

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Describe the proposal
Observable tasks add netty related indicators
At present, the latest version of micrometer has added Netty related monitoring indicators. The Java version of Dubbo uses the Netty framework at the bottom, which can be explored and developed to improve monitoring indicators.
可观测任务增加netty相关指标
目前最新版本的micrometer新增了netty相关的监控指标，Java版本的Dubbo底层使用的是Netty框架，可以尝试调研，兼容开发，来完善监控指标
https://github.com/micrometer-metrics/micrometer/releases/tag/v1.11.0

Network related metrics is important. BTW, can we trace some network time usage in one call.

I would like to give this task a try. Please assign it to me


Feature use service

I'd like to "start over" with this PR. It is correctly targeted to the 3.1 branch.
The 'metadata' endpoints have not yet been implemented
/v1/metadata/estimation_year_ids
/v1/metadata/estimation_age_group_ids
/v1/metadata/age_bins

Small, non-design changes added. Design changes to go in upcoming PR;s


Possible race condition in SpiDma transfers

https://github.com/esp-rs/esp-hal/blob/main/esp-hal-common/src/spi/master.rs#L1340
The DMA sets the GDMA_OUT_EOF_CHn_INT_ENA bit after the peripheral starts the transmission. This may result in the future never resolving, if some other code is executed between transmission start and listen start.
Or at least I think this is the case.

I think I've seen problem caused by this pattern with the AES peripheral which is faster (with small amounts of data) than we get to creating the future - so it's not just a hypothetical thing

I think I'm hitting this issue or something related with esp-wifi and a spidma-driven display; the display's DmaTxFuture often stops resolving if my mobile is connected to the device's AP.


Updates to articles for spelling, accuracy, and other edits

I removed a few repetitive android debugging recipes that didn't seem to belong, fixed a bunch of typos and some readability issues/grammar, and made some of the code more clear for an external audience.

Nice! Thanks again for looking through everything @markrickert


update linkml to 1.6.2

poetry update linkml linkml-runtime

Updating dependencies
Resolving dependencies... (3.4s)
Package operations: 0 installs, 1 update, 0 removals
• Updating linkml (1.6.1 -> 1.6.2)
Writing lock file

poetry show linkml-runtime | grep version

version      : 1.6.2

poetry show linkml | grep version

version      : 1.6.2

poetry run gen-project \
        --exclude excel \
        --exclude graphql \
        --exclude jsonld \
        --exclude markdown \
        --exclude proto \
        --exclude shacl \
        --exclude shex \
        --exclude sqlddl \
        --include jsonldcontext \
        --include jsonschema \
        --include owl \
        --include python \
        --include rdf \
        -d project src/schema/nmdc.yaml && mv project/*.py nmdc_schema

ALL_SCHEMAS = ['src/schema/nmdc.yaml']
INFO:root:Skipping graphql as not in inclusion list: ['jsonldcontext', 'jsonschema', 'owl', 'python', 'rdf']
INFO:root:Generating: jsonldcontext
INFO:root: SCHEMA: src/schema/nmdc.yaml
INFO:root: PARENT=project/jsonld
INFO:root: jsonldcontext ARGS: {'mergeimports': True}
INFO:root:  WRITING TO: project/jsonld/nmdc.context.jsonld
INFO:root:Skipping jsonld as not in inclusion list: ['jsonldcontext', 'jsonschema', 'owl', 'python', 'rdf']
INFO:root:Generating: jsonschema
INFO:root: SCHEMA: src/schema/nmdc.yaml
INFO:root: PARENT=project/jsonschema
INFO:root:Using SchemaView with im=None
INFO:root: jsonschema ARGS: {'mergeimports': True}
INFO:root:Importing workflow_execution_activity as workflow_execution_activity from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing core as core from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing prov as prov from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing basic_slots as basic_slots from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing external_identifiers as external_identifiers from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing sample_prep as sample_prep from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing portal/sample_id as portal/sample_id from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing linkml:types as /home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml_runtime/linkml_model/model/schema/types from source src/schema/nmdc.yaml; base_dir=None
INFO:root:Importing portal/mixs_inspired as portal/mixs_inspired from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing portal/jgi_metatranscriptomics as portal/jgi_metatranscriptomics from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing portal/jgi_metagenomics as portal/jgi_metagenomics from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing portal/emsl as portal/emsl from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing mixs as mixs from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing annotation as annotation from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:  WRITING TO: project/jsonschema/nmdc.schema.json
INFO:root:Skipping markdown as not in inclusion list: ['jsonldcontext', 'jsonschema', 'owl', 'python', 'rdf']
INFO:root:Generating: owl
INFO:root: SCHEMA: src/schema/nmdc.yaml
INFO:root: PARENT=project/owl
INFO:root:Using SchemaView with im=None
INFO:root: owl ARGS: {'mergeimports': True}
INFO:root:Importing workflow_execution_activity as workflow_execution_activity from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing core as core from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing prov as prov from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing basic_slots as basic_slots from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing external_identifiers as external_identifiers from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing sample_prep as sample_prep from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing portal/sample_id as portal/sample_id from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing linkml:types as /home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml_runtime/linkml_model/model/schema/types from source src/schema/nmdc.yaml; base_dir=None
INFO:root:Importing portal/mixs_inspired as portal/mixs_inspired from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing portal/jgi_metatranscriptomics as portal/jgi_metatranscriptomics from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing portal/jgi_metagenomics as portal/jgi_metagenomics from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing portal/emsl as portal/emsl from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing mixs as mixs from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing annotation as annotation from source src/schema/nmdc.yaml; base_dir=src/schema
INFO:root:Importing linkml:units as /home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml_runtime/linkml_model/model/schema/units from source None; base_dir=None
INFO:root:Importing linkml:mappings as /home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml_runtime/linkml_model/model/schema/mappings from source None; base_dir=None
INFO:root:Importing linkml:types as /home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml_runtime/linkml_model/model/schema/types from source None; base_dir=None
INFO:root:Importing linkml:annotations as /home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml_runtime/linkml_model/model/schema/annotations from source None; base_dir=None
INFO:root:Importing linkml:extensions as /home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml_runtime/linkml_model/model/schema/extensions from source None; base_dir=None
WARNING:root:from_schema not populated for element has_input
WARNING:root:from_schema not populated for element has_output
WARNING:root:from_schema not populated for element id
WARNING:root:from_schema not populated for element has_input
WARNING:root:from_schema not populated for element has_output
WARNING:root:from_schema not populated for element id
WARNING:root:from_schema not populated for element has_input
WARNING:root:from_schema not populated for element has_output
WARNING:root:from_schema not populated for element id
WARNING:root:from_schema not populated for element id
WARNING:root:from_schema not populated for element has_input
WARNING:root:from_schema not populated for element has_output
WARNING:root:from_schema not populated for element id
WARNING:root:from_schema not populated for element description
WARNING:root:from_schema not populated for element id
WARNING:root:from_schema not populated for element name
WARNING:root:from_schema not populated for element dna_cont_well
WARNING:root:from_schema not populated for element dna_cont_type
WARNING:root:from_schema not populated for element dna_cont_type
WARNING:root:from_schema not populated for element dna_cont_well
WARNING:root:from_schema not populated for element rna_cont_well
WARNING:root:from_schema not populated for element rna_cont_type
WARNING:root:from_schema not populated for element rna_cont_type
WARNING:root:from_schema not populated for element rna_cont_well
WARNING:root:from_schema not populated for element al_sat
WARNING:root:from_schema not populated for element al_sat_meth
WARNING:root:from_schema not populated for element alternative_identifiers
WARNING:root:from_schema not populated for element annual_precpt
WARNING:root:from_schema not populated for element climate_environment
WARNING:root:from_schema not populated for element cur_vegetation
WARNING:root:from_schema not populated for element cur_vegetation_meth
WARNING:root:from_schema not populated for element elev
WARNING:root:from_schema not populated for element env_broad_scale
WARNING:root:from_schema not populated for element env_local_scale
WARNING:root:from_schema not populated for element env_medium
WARNING:root:from_schema not populated for element extreme_event
WARNING:root:from_schema not populated for element fire
WARNING:root:from_schema not populated for element flooding
WARNING:root:from_schema not populated for element gaseous_environment
WARNING:root:from_schema not populated for element gold_biosample_identifiers
WARNING:root:from_schema not populated for element heavy_metals
WARNING:root:from_schema not populated for element heavy_metals_meth
WARNING:root:from_schema not populated for element id
WARNING:root:from_schema not populated for element lat_lon
WARNING:root:from_schema not populated for element oxy_stat_samp
WARNING:root:Multiple owl types {rdflib.term.URIRef('http://www.w3.org/2002/07/owl#Thing'), rdflib.term.URIRef('http://www.w3.org/2000/01/rdf-schema#Literal')}
WARNING:root:from_schema not populated for element part_of
WARNING:root:from_schema not populated for element ph_meth
WARNING:root:from_schema not populated for element salinity_meth
WARNING:root:from_schema not populated for element season_precpt
WARNING:root:from_schema not populated for element sieving
WARNING:root:from_schema not populated for element slope_aspect
WARNING:root:from_schema not populated for element slope_gradient
WARNING:root:from_schema not populated for element source_mat_id
WARNING:root:from_schema not populated for element tot_carb
WARNING:root:from_schema not populated for element tot_nitro_cont_meth
WARNING:root:from_schema not populated for element tot_nitro_content
WARNING:root:from_schema not populated for element tot_org_c_meth
WARNING:root:from_schema not populated for element tot_org_carb
WARNING:root:from_schema not populated for element water_cont_soil_meth
WARNING:root:from_schema not populated for element water_content
WARNING:root:from_schema not populated for element watering_regm
Traceback (most recent call last):
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/bin/gen-project", line 8, in
sys.exit(cli())
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/click/core.py", line 1078, in main
rv = self.invoke(ctx)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/projectgen.py", line 243, in cli
gen.generate(yamlfile, project_config)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/projectgen.py", line 145, in generate
gen_dump = gen.serialize(**serialize_args)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/owlgen.py", line 199, in serialize
self.as_graph()
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/owlgen.py", line 185, in as_graph
self.add_class(cls)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/owlgen.py", line 352, in add_class
pre_node = condition_to_bnode(rule.preconditions)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/owlgen.py", line 344, in condition_to_bnode
ixn_listnode = self.transform_class_expression(expr, quantifier_predicate=OWL.someValuesFrom)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/owlgen.py", line 428, in transform_class_expression
x = self.transform_class_slot_expression(cls, slot, slot)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/owlgen.py", line 494, in transform_class_slot_expression
self._union_of([self.transform_class_slot_expression(cls, x, main_slot) for x in slot.any_of])
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/owlgen.py", line 871, in _union_of
return self._boolean_expression(exprs, OWL.unionOf, **kwargs)
File "/home/mark/.cache/pypoetry/virtualenvs/nmdc-schema-_1824IzR-py3.9/lib/python3.9/site-packages/linkml/generators/owlgen.py", line 894, in _boolean_expression
raise ValueError(f"None in exprs: {exprs}")
ValueError: None in exprs: [None, None]
make: *** [Makefile:102: gen-project] Error 1

works when owl generation is excluded


Can you help and provide a script for user own input ? like genomic ranges

HI,
Thanks for providing this powerful tools.
I am some sites and I want to predict via deepSRAMP.
can you help and provide the code for predict for genomic ranges ?
Thanks!

BTW, the db link in setup_inference is wrong, it should be  https://github.com/zhfanrui/deepSRAMP/releases/download/Database/db_hg38_mature.tgz


Refector Apigateway update_usage_plan and add all replace operation.

Codecov Report

Merging #3942 (8a29e28) into master (79792db) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #3942   +/-   ##
=======================================
  Coverage   94.86%   94.86%
=======================================
  Files         454      454
  Lines       49380    49388    +8
=======================================
+ Hits        46844    46854   +10
+ Misses       2536     2534    -2

Flag
Coverage Δ

servertests
55.78% <9.52%> (-0.01%)
:arrow_down:

unittests
94.74% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/apigateway/models.py
93.83% <100.00%> (+0.06%)
:arrow_up:

moto/iam/models.py
95.27% <0.00%> (+0.14%)
:arrow_up:

Continue to review full report at Codecov.

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

@bblommers - kindly bless this pull request.


Logic gate broken

Description
When trying to block the gateway at the beginning of the round (using Logic gate (using NOR)), I ran into a very interesting problem - when initializing the card, Logic gate does not check its state. As an example, NOR gives 1 at 0 0 (Below is a screenshot for clarity). But either it issues this signal during card initialization, or it does not check its status after card initialization. Because of this, it is almost impossible to use them - you must give a signal to them so that they start working.
Reproduction
Create any logical element on the map (for example, XOR) and make sure. that he is obliged to give a signal at the very beginning. connect it to something that should switch the state (light bulb). When initializing the card, Logic gate will not change its state until any signal is given to it (for example, from a button).
Screenshots

Additional context
Below is a link to a video from Google Drive where the bug is being played.
Link

i have a pr that does just this

can be closed

pro


HTTPS SSL TLS Using websockets doesnt work

Line 381 in Websocket.jl:

sock = WebSocket(client.id, client.sock)

Receives a MbedTLS SSLContext in the client.sock value as per HttpServer.jl:
     sess = MbedTLS.SSLContext()
        MbedTLS.setup!(sess, ssl_config)
        # set_priority_string!(sess)
        # set_credentials!(sess, cert_store)
        client = accept(server.http.sock)
        try
            MbedTLS.set_bio!(sess, client)
            MbedTLS.handshake(sess)
            # associate_stream(sess, client)
            # handshake!(sess)
        catch e
            println("Error establishing SSL connection: ", e)
            close(client)
            continue
        end
        client = Client(id_pool += 1, sess)
        client.parser = ClientParser(message_handler(server, client, websockets_enabled))
        @async process_client(server, client, websockets_enabled)`

https://github.com/JuliaWeb/HttpServer.jl/issues/87
As I'm not sure which project is better to help massage the socket into, I'm looking for help on this one. Please let me know what to do! Thanks
PS Here's more interesting debug info:

HttpServer.Client{MbedTLS.SSLContext}(14,MbedTLS.SSLContext(Ptr{Void} @0x0000000003245910,MbedTLS.SSLConfig(Ptr{Void} @0x0000000002dff880,MbedTLS.CtrDrbg(Ptr{Void} @0x0000000002ca2f00,Nullable(MbedTLS.Entropy(Ptr{Void} @0x0000000002e54c90,Any[]))),#undef,(anonymous function),cert. version     : 3
serial number     : DB:7E:D8:55:3E:F1:AB:AC
issuer name       : C=US, ST=CA, L=San Francisco, O=BXI, CN=bxi.io<EMAIL_ADDRESS>subject name      : C=US, ST=CA, L=San Francisco, O=BXI, CN=bxi.io<EMAIL_ADDRESS>issued  on        : 2016-02-21 07:47:43
expires on        : 2017-02-20 07:47:43
signed using      : RSA with SHA-256
RSA key size      : 2048 bits
basic constraints : CA=true
,MbedTLS.PKContext(Ptr{Void} @0x0000000002cf1160)),true,TCPSocket(open, 0 bytes waiting)),HttpServer.ClientParser(HttpParser,HttpParser.ParserSettings(Ptr{Void} @0x00007fcb39e9ffc0,Ptr{Void} @0x00007fcb39ea35d0,Ptr{Void} @0x00007fcb39ea3810,Ptr{Void} @0x00007fcb39ea3850,Ptr{Void} @0x00007fcb39ea3a80,Ptr{Void} @0x00007fcb39ea4c80,Ptr{Void} @0x00007fcb39ea50a0,Ptr{Void} @0x00007fcb39ea5210)))WARNING: both Patchwork and Base export "Text"; uses of it in module Main must be qualified
ERROR (unhandled task failure): MethodError: convert has no method matching convert(::Type{TCPSocket}, ::MbedTLS.SSLContext)
This may have arisen from a call to the constructor TCPSocket(...),
since type constructors fall back to convert methods.
Closest candidates are:
TCPSocket(::Any)
call{T}(::Type{T}, ::Any)
convert{T}(::Type{T}, ::T)
...
in call at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:57
in handle at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:387
in on_message_complete at /home/a/.julia/v0.4/HttpServer/src/HttpServer.jl:393
in on_message_complete at /home/a/.julia/v0.4/HttpServer/src/RequestParser.jl:104

PPS This is what I tried (using client.sock.bio):
https://github.com/dioptre/WebSockets.jl/commit/3bb92d7b09cfc19ff392edd8bb11d3b3e6e99cbf
...and new error

handling websocket connection:
write: broken pipe (EPIPE)
in yieldto at ./task.jl:71
in wait at ./task.jl:371
in stream_wait at ./stream.jl:60
in uv_write at stream.jl:944
in flush at stream.jl:979
in locked_write at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:154
in write at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:168
in start_updates at /home/a/projects/bxi/server/www.jl:213
in anonymous at /home/a/projects/bxi/server/www.jl:274
in anonymous at /home/a/.julia/v0.4/Mux/src/Mux.jl:15
in anonymous at /home/a/.julia/v0.4/Mux/src/Mux.jl:8
in splitquery at /home/a/.julia/v0.4/Mux/src/basics.jl:28
in anonymous at /home/a/.julia/v0.4/Mux/src/Mux.jl:8
in wcatch at /home/a/.julia/v0.4/Mux/src/websockets_integration.jl:12
in anonymous at /home/a/.julia/v0.4/Mux/src/Mux.jl:8
in todict at /home/a/.julia/v0.4/Mux/src/basics.jl:21
in anonymous at /home/a/.julia/v0.4/Mux/src/Mux.jl:12 (repeats 2 times)
in anonymous at /home/a/.julia/v0.4/Mux/src/Mux.jl:8
in anonymous at /home/a/.julia/v0.4/Mux/src/server.jl:38
in handle at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:394
in on_message_complete at /home/a/.julia/v0.4/HttpServer/src/HttpServer.jl:393
in on_message_complete at /home/a/.julia/v0.4/HttpServer/src/RequestParser.jl:104ERROR (unhandled task failure): write: broken pipe (EPIPE)
in yieldto at ./task.jl:71
in wait at ./task.jl:371
in stream_wait at ./stream.jl:60
in uv_write at stream.jl:944
in flush at stream.jl:979
in locked_write at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:154
in close at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:197
in handle at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:395
in on_message_complete at /home/a/.julia/v0.4/HttpServer/src/HttpServer.jl:393
in on_message_complete at /home/a/.julia/v0.4/HttpServer/src/RequestParser.jl:1

Here's more interesting debug info:

HttpServer.Client{MbedTLS.SSLContext}(14,MbedTLS.SSLContext(Ptr{Void} @0x0000000003245910,MbedTLS.SSLConfig(Ptr{Void} @0x0000000002dff880,MbedTLS.CtrDrbg(Ptr{Void} @0x0000000002ca2f00,Nullable(MbedTLS.Entropy(Ptr{Void} @0x0000000002e54c90,Any[]))),#undef,(anonymous function),cert. version     : 3
serial number     : DB:7E:D8:55:3E:F1:AB:AC
issuer name       : C=US, ST=CA, L=San Francisco, O=BXI, CN=bxi.io<EMAIL_ADDRESS>subject name      : C=US, ST=CA, L=San Francisco, O=BXI, CN=bxi.io<EMAIL_ADDRESS>issued  on        : 2016-02-21 07:47:43
expires on        : 2017-02-20 07:47:43
signed using      : RSA with SHA-256
RSA key size      : 2048 bits
basic constraints : CA=true
,MbedTLS.PKContext(Ptr{Void} @0x0000000002cf1160)),true,TCPSocket(open, 0 bytes waiting)),HttpServer.ClientParser(HttpParser,HttpParser.ParserSettings(Ptr{Void} @0x00007fcb39e9ffc0,Ptr{Void} @0x00007fcb39ea35d0,Ptr{Void} @0x00007fcb39ea3810,Ptr{Void} @0x00007fcb39ea3850,Ptr{Void} @0x00007fcb39ea3a80,Ptr{Void} @0x00007fcb39ea4c80,Ptr{Void} @0x00007fcb39ea50a0,Ptr{Void} @0x00007fcb39ea5210)))WARNING: both Patchwork and Base export "Text"; uses of it in module Main must be qualified
ERROR (unhandled task failure): MethodError: convert has no method matching convert(::Type{TCPSocket}, ::MbedTLS.SSLContext)
This may have arisen from a call to the constructor TCPSocket(...),
since type constructors fall back to convert methods.
Closest candidates are:
TCPSocket(::Any)
call{T}(::Type{T}, ::Any)
convert{T}(::Type{T}, ::T)
...
in call at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:57
in handle at /home/a/.julia/v0.4/WebSockets/src/WebSockets.jl:387
in on_message_complete at /home/a/.julia/v0.4/HttpServer/src/HttpServer.jl:393
in on_message_complete at /home/a/.julia/v0.4/HttpServer/src/RequestParser.jl:104

Bump

I haven't looked at this package yet, but I think this should be a relatively simple change of switching out a socket for an MbedTLS context object somewhere.

At a glance I think an adapter buffer might be needed for TLS to work, because I don't think MbedTLS.SSLContext supports byte I/O. That is, when reading a frame and calling read(b, UInt8) you'll get an exception from MbedTLS. It only supports readavailable and readbytes, I think.
If I'm right it would be necessary to make a stream which wraps an MbedTLS.SSLContext stream, and allows calls to read(::IO, ::Type{T}), but only uses readavailable(::IO) on the TLS stream. That can't be very hard though.

https://github.com/JuliaWeb/WebSockets.jl/pull/88 contains changes that support SSLContext 😊

It looks like the SSLContext tests were for SSL Client connections only? @EricForgy

Yeah. Is there some problem with servers? 😅

We should have a look at this again. MbedTLS has been updated. I suspect examples may be easily modified for a secure version.
An example with a secure server should also include a time-limited token for the wsuris.

Can anybody check if this works? Https is extra complicated on windows....


[Hexagon] Add E2E test demonstrating how to apply blocked layout schedule to conv2d via metaschedule

Demonstrates the use of a custom search space generation from a manual written schedule. In this there are no degrees of freedom so tuning will not improve the schedule currently, but the test demonstrates the schedule-time layout transformation of the conv2d primfunc to the 8x8x32 packed layout for convolution ops.

@tvm-bot rerun

Thanks for patience, let us hold off on merging this one for a bit as there are a few issues that arise at the end of a tuning run with this test:

Lack of JSON serialization for tir::IndexMap in src/meta_schedule/database/database_utils.cc::JSONDumps
Metascheduler search workers hang when the search space has only one sample.

Hi Chris, regarding (2) does the worker hang when the search space that has only one sample, and will not terminate by itself even after 5 iterations?

Thanks @zxybazh for following the thread closely. Looks like (2) was a red herring and is not reproducible for me any longer. Furthermore, (1) is coming in a follow up PR and this test is skipped so no harm merging this now.


Plugin tries to push through Obsidian Mobile

Hey,
Obsidian Git plugins seems to try syncing via the mobile app, but is unsuccessful, I cannot specify the path on mobile because the path does not exist on mobile, but on my desktop.

You can't specify a path, because there is no way to install git on a mobile device. The plugin ships it's own git implementation.

Actually, there was an option to "disable on this device" as the very last option in settings which fixed the issue.

You can't specify a path, because there is no way to install git on a mobile device. The plugin ships it's own git implementation.

What I mean by that, by the way, is that the notification implied I need to specify the path. I forgot to include the prompt screenshot so it might have been unclear!


[parser] Compute Local AABB when loading a geometry.

It seems that the method was not called for all the geometry types. Since the AABB is now initialized to infinity, the missing
call has visible effects.

I've proposed an alternative and more robust solution in 2b3c5f5.

The const-cast in @jcarpent proposal feels not very clean. I agree with @jcarpent that the case of manually added geometries should be supported too.
This issue can also be fixed in hpp-fcl:

in the constructor for primitives,
in the model finalization for BVH.

Duplicate with #1418.

* in the constructor for primitives,

In this case, we cannot change the object properties online.
I would rather suggest making computeLocalAABB const

The const-cast in @jcarpent proposal feels not very clean

I do agree. This is because the method is not marked const. But should not be a problem in general ;).
Another solution would be to provide a const method to retrieve this quantity for any CollisionGeometry.

This issue can also be fixed in hpp-fcl:
* in the constructor for primitives,

* in the model finalization for BVH.

and in any method that modifies the geometry.
I think it would be the best solution.

In this case, we cannot change the object properties online.

Yes, it requires you to call computeLocalAABB or to make attributes private and modify them with class methods. But the latter is significantly more work for the developer.

I would rather suggest making computeLocalAABB const

Then either the internal aabb is mutable or the it is const-cast in the class function. You don't change the fact that you break the C++ constness stuff.

Then either the internal aabb is mutable or the it is const-cast in the class function. You don't change the fact that you break the C++ constness stuff.

The minimal intervention is the current one. I let you choose, but I think these two options are the most effective one at the time being, without breaking too much the current API.

Then, go for the const-cast, with a TODO note that points to this thread. Unless someone has some more time to spend on this.

The fix will appear in #1418.


Grpc.Core.RpcException when remote invocation results in BadRequest

Expected Behavior
The client sdk should be able to handle HTTP 400 Bad Request and make the request available to the calling application
Actual Behavior
When the app returns a HTTP400 or BadRequest object the dapr client fails with an exception.
Steps to Reproduce the Problem
Small modification of https://github.com/dapr/dotnet-sdk/blob/master/samples/AspNetCore/ControllerSample/Controllers/SampleController.cs to add the following method
to return a BadRequest
/// Do
[HttpPost("do")]
public IActionResult Do(int value)
{
    Console.WriteLine($"Doing {value}");
    return BadRequest(new
    {
        value = value
    });
}

When calling the method on the client via
var a = await client.InvokeMethodAsync<object, Account>("routing", "do", data, httpExtension);

we are getting an exception
== APP == DepositUsingServiceInvocation

== APP == invoking

== APP == Unhandled exception. Grpc.Core.RpcException: Status(StatusCode=Internal, Detail="Bad Request")
== APP ==    at Dapr.Client.DaprClientGrpc.MakeGrpcCallHandleError[TResponse](Func`2 callFunc, CancellationToken cancellationToken) in /dotnet-sdk/src/Dapr.Client/DaprClientGrpc.cs:line 585

It seems there is no handling in the client sdk https://github.com/dapr/dotnet-sdk/blob/master/src/Dapr.Client/DaprClientGrpc.cs#L584

IMO we need to make sure we return the following information to the caller when invoking HTTP services, uniformly:

Response text
Status code
Headers

The current implementation has already put all these information to Status.Details for rich error handling support.
Regarding gRPC official doc, some of gRPC SDKs support status details. e.g. grpc-dotnet has supported this, but grpc for c# doesn't support it.
This richer error model is already supported in the C++, Go, Java, Python, and Ruby libraries, ...
...
You could use a similar approach (put error details in trailing response metadata) if you’re not using protocol buffers, but you’d likely need to find or develop library support for accessing this data in order to make practical use of it in your APIs.

The official doc recommends to use trailer metadata as @akkie requested, but there is the size limitation of metadata (the limit on the spec 8KiB but it depends on SDK implementation. some SDKs limit 4 KiB for the entire metadata).
Here is the proposal.
For gRPC caller and HTTP callee scenario,

if error-response body size exceeds 4KiB, put 4KiB truncated error-response body to trailer metadata, and populate the original body payload to Status.Details.
if error-response body size does not exceed 4KiB, put the original payload to trailer metadata, but not populate the original body payload to Status.Details

This will reduce the size of response and support all gRPC SDKs.
@amanbha @yaron2 @akkie any thoughts?

IMO we need to make sure we return the following information to the caller when invoking HTTP services, uniformly:

Response text
Status code
Headers

The current implementation has already put all these information to Status.Details for rich error handling support.
Regarding gRPC official doc, some of gRPC SDKs support status details. e.g. grpc-dotnet has supported this, but grpc for c# doesn't support it.
This richer error model is already supported in the C++, Go, Java, Python, and Ruby libraries, ...
...
You could use a similar approach (put error details in trailing response metadata) if you’re not using protocol buffers, but you’d likely need to find or develop library support for accessing this data in order to make practical use of it in your APIs.

The official doc recommends to use trailer metadata as @akkie requested, but there is the size limitation of metadata (the limit on the spec 8KiB but it depends on SDK implementation. some SDKs limit 4 KiB for the entire metadata).
Here is the proposal.
For gRPC caller and HTTP callee scenario,

if error-response body size exceeds 4KiB, put 4KiB truncated error-response body to trailer metadata, and populate the original body payload to Status.Details.
if error-response body size does not exceed 4KiB, put the original payload to trailer metadata, but not populate the original body payload to Status.Details

This will reduce the size of response and support all gRPC SDKs.
@amanbha @yaron2 @akkie any thoughts?

The only issue I see here is that of unclear behavior based on the content size of the message. We probably don't want users to have if/else statements that look for the body in Status.Details and then the trailer metadata.
I would suggest to always store it in Status.Details and never populate the metadata trailers, as it's not a good fit for that type of data.

The only issue I see here is that of unclear behavior based on the content size of the message. We probably don't want users to have if/else statements that look for the body in Status.Details and then the trailer metadata.

I would suggest to always store it in Status.Details and never populate the metadata trailers, as it's not a good fit for that type of data.

We already populated to Status.Details but the problem here is that gRPC for C# doesn't support Status.Details (which is the rich error handling way in gRPC)

The only issue I see here is that of unclear behavior based on the content size of the message. We probably don't want users to have if/else statements that look for the body in Status.Details and then the trailer metadata.

I would suggest to always store it in Status.Details and never populate the metadata trailers, as it's not a good fit for that type of data.

We already populated to Status.Details but the problem here is that gRPC for C# doesn't support Status.Details (which is the rich error handling way in gRPC)

Ok I missed the rich error support being Status.Details.
Now that I think about it, since we are a reverse proxy (albeit with a bridge in this case), we should return the body as the Data payload returned to the caller. This is not a gRPC error. a gRPC error would be returned in case of an internal error or network error. Since Dapr should "only" surface up HTTP responses, Dapr should not treat any HTTP call to the end service as a failure.

We referred to grpc-gateway conversion logic between http and grpc status code and google cloud api error handling when we designed it. please look at this guideline. gRPC rich error handling is designed to describe detail application error.
https://cloud.google.com/apis/design/errors#generating_errors
If we treat http errors as GRPC OK, it will break trace and metrics status result. This is same as what we discuss in pubsub appcallback response code. i.e even if http application returns 4xx or 5xx for failures and grpc caller treats these errors as success (or OK statuscode), grpc caller will record the requests as success.

Yeah I get that, but just because something operates in one way today, doesn't mean it needs to be kept that way.
The following statements are known to be true:

Service to Service invocation is a reverse proxy + service discovery
For HTTP to HTTP, Dapr doesn't do any type of status code conversion. Whatever status code returns from the target app is returned to the caller

Considering that, it only makes sense we do the same thing for gRPC to HTTP. What if a user is writing an HTTP validation app that actually shouldn't treat 400 or 500 as errors?
We need to let users inspect the status code and response text that were returned for them to make an informed decision. I don't think Dapr can assume that some status codes are errors and some are not, especially when we don't do it for HTTP.
You're right that this will break trace and metrics status results, but those probably need to change based on this.

We need to let users inspect the status code and response text that were returned for them to make an informed decision. I don't think Dapr can assume that some status codes are errors and some are not, especially when we don't do it for HTTP.

As I mentioned, status code and the original error body is already given in Status.Details. but the problem here is that grpc for c# cannot extract this given info.
If we change this behavior, then this is going to be bigger work.

I have taken a look at the other SDKs to see how to decode status details (rich error model). It is stored as grpc-status-details-bin trailer metadata(grpc for c# can access this metadata as well). trailer's data will be added to the end of the body. So it doesn't matter with size of body :) Trailer field lengths will be limited 8KiB (on spec), but not for body because Trailer fields are stored in HTTP header.
The official gRPC error handling spec recommends developers to use Status.Details with rich error model to include the detail application errors.
Therefore, we have two options;

Populate status code/content-type/response body/headers to trailer instead of Status.Details.  grpc for c# sdk will extract trailer metadata.
Populate status code/content-type/response body/headers to Status.Details as is, but grpc for c# sdk will decode grpc-status-details-bin metadata.

Even if rich error model is on official spec, not all sdks support it. Also, option 1 implementation in client side is easier than option 2.
cc/ @yaron2 @amanbha @akkie @shalabhms @rynowak

That's good info,. but it doesn't affect the fact that Dapr shouldn't decide which HTTP status codes are considered an error and which are not. Dapr should report back to the client the details that the HTTP call returned, and not decide that status code X == gRPC exception.

That's good info,. but it doesn't affect the fact that Dapr shouldn't decide which HTTP status codes are considered an error and which are not. Dapr should report back to the client the details that the HTTP call returned, and not decide that status code X == gRPC exception.

Then how can we handle http -> grpc case? we agree this conversion when we review the spec long before ago. The current design can handle four cross protocol invocation. Then why grpc gateway project does this conversion? We will discuss it tomorrow. If we change this behavior, it requires lots of change related to trace and metrics. I am not sure this is the right approach.
Even google cloud api error handling doc describes the mapping between http status code and grpc status code.

That's good info,. but it doesn't affect the fact that Dapr shouldn't decide which HTTP status codes are considered an error and which are not. Dapr should report back to the client the details that the HTTP call returned, and not decide that status code X == gRPC exception.

Then how can we handle http -> grpc case? we agreed this conversion when we reviewed the spec long before ago. The current design can handle four cross protocol invocation. Then why grpc gateway project does this conversion? We will discuss it tomorrow. If we change this behavior, it requires lots of change related to trace and metrics. I am not sure this is the right approach.
Even google cloud api error handling doc describes the mapping between http status code and grpc status code.
There is no losing info.

I understand, I'm simply saying that it's the user's app job to decide about how to handle status codes, not Dapr's.
For gRPC gateway, do they handle gRPC client to HTTP server, or HTTP client to gRPC server?

Grpc gateway allows to run grpc server and accept http and grpc clients both.
We referred to this and you reviewed it together. We agreed upon the design, did not we? Again user can handle the original status error code properly without losing data and info. Then what’s your concern?
This is the fundamental design for trace and metrics so the design change can impact both.

Grpc gateway allows to run grpc server and accept http and grpc clients both.
We referred to this and you reviewed it together. We agreed upon the design, did not we? Again user can handle the original status error code properly without losing data and info. Then what’s your concern?
This is the fundamental design for trace and metrics so the design change can impact both.

I get it, I don't want to make far reaching changes. Let's discuss in the maintainers meeting tomorrow.

@yaron2 @youngbupark Do you have any update regarding this topic?

@yaron2 @youngbupark Do you have any update regarding this topic?

We found the bug in gRPC for c# which it populates grpc-status-details-bin to response header instead of trailer metadata. The maintainer of gRPC for c# starts looking at this bug. But unless the bug fix comes soon (by this week or next week), we will provide the workaround which extracts the error from header in Dapr dotnet-sdk by next week.


Fix memory leak, switch to auto managed clients and bug fix

Fix memory leak (#323), switch to auto managed clients where possible and fix dialog hanging around on bad password.

I'm not sure what's going on in the diff here but I already did the fix to dismiss the dialog on bad password, see:
https://github.com/firebase/FirebaseUI-Android/blob/11bc4ceb99ea71b535ced2b9d2e7593db447884c/auth/src/main/java/com/firebase/ui/auth/ui/email/SignInActivity.java#L123
Other than figuring out why you're not seeing that, LGTM and feel free to merge when Travis goes green.

Ah, I hadn't pulled recently enough.  Thanks!


[tvla] Enable passing lists of selected rounds/bytes for byte-specific AES, add new CI job

This PR is related to #287 and contains two commits:

Enable passing lists of selected rounds and bytes for the byte-specific AES TLVA
Add a new CI job to exactly test this as well as other byte-specific TVLA functions

Thanks for your review @nasahlpa . I'll merge this once CI passes.


blog on docker

hey rohit, i had put a blog on docker could you verify once

Blogs can be contributed to blog.devopscommunity.in
Thanks for brining this up, I'll add this in readme.md too.


DEVELOPMENT: Used GETTERS and SETTERS in reporting classes without using the attributes as public attributes.

Htet Aung San - Done using getters and setters in reporting classes


Added run_exports to pin major package releases

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This pull request adds a run_exports to the build to pin major package releases.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@duncanmmacleod does the addition of run_exports to pin the major package release in the meta.yaml look okay to you?


Remove duplicate code

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


final model

cherry-pick

Change pr title content into correct format.
():
type: Feat/fix/ref/hot-fix
task-id: from trello
content: usefull content


Categorize/Declutter Moneropedia Articles

Even though Kovri is going to be integrated into Monero in the future, I feel like having a lot of stub articles about Kovri topics in the Moneropedia is detrimental to it's function as instructional for new users. (Currently 34.9% of articles are Kovri-based.)
I'm not as familiar with I2P or Kovri, so I don't feel equipped to make the change myself. I think a lot of this information can be moved copied over to monero-project/kovri-site eventually, but for now I think we should consolidate it into one article. (Another possibility I've considered is to expand Moneropedia to include categories, and categorize these in a way that it's easier to navigate Monero specific topics seperate from Kovri topics.)
I believe these are all the articles that are currently Kovri related:
Base32-Address
Base64-Address
Canonically Unique Host
Clearnet
Destination
Eeepsite
Floodfill
Garlic Encryption
Garlic Routing
i2np
i2p
i2pcontrol
java-i2p
Jump Service
Kovri
Lease
Network Database
Router Info
SSU
Subscription
Transports
Tunnel
+moneropedia
+enhancement

Bad idea to merge into a single article. Good idea to have top-level categories.

Bad idea to merge into a single article. Good idea to have top-level categories.

I kinda agree with you, but with Kovri having it's own site, I think we don't have to have individual articles for things that could be categorized under a particular article. Wikipedia does this somewhat and uses section headers for each bit of information, so it's still possible to link directly to a particular subject in the article. The articles should have magnet links to jump to each section.
For instance:
Kovri
Top level information of what Kovri is and does. Explaining the difference between it and I2P. (C++ vs Java, etc).
_I2P (subsections explaining each of these things specifically how their implemented in Kovri)
__Tunnel
__Transport
__Jump Service
__Subscription
__Garlic Encryption
__Garlic Routing
__EEP Site

I agree that many of those terms may create confusion, but I also agree that merge everything in one article is not optimal and dispersive. What about make a 'Kovripedia' on getkovri where pull this terms? IMO they are enough and they will increase with time, it would be needed in future anyway

+moneropedia
+enhancement
@danrmiller Any idea why the bot didn't pick up the labels from the OP?

I think monerpedia could use more work and be given more exposure once that works done. I'm agreeing with all the issues here.

This issue is old and was discussed and closed on gitlab. Please reopen if you feel it's still relevant.


[AutoRelease] t2-edgezones-2024-07-05-79075(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/5073
Recording test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=6976

issue link:https://github.com/Azure/sdk-release-request/issues/5073

/check-enforcer override


add option to generate test coverage report without codecov

using the guide here: https://hynek.me/articles/ditch-codecov-python/
This does not create coverage diffs or report to PRs, just creates a markdown summary table
closes #189

I tried this out on sunpy and it seems to explode. https://github.com/sunpy/sunpy/pull/7668

It seems that it's not picking up the coverage.xml to upload here: https://github.com/sunpy/sunpy/actions/runs/9445798095/job/26014155532?pr=7668#step:14:16 :thinking:

tl;dr -- this does not generate patch coverage, right?

Not yet, but I found a way to make it.

tl;dr -- this does not generate patch coverage, right?

Not yet, but I found a way to make it.

For patch coverage we'd need to store the coverage from main somewhere, to compare it to; some people I've seen online have done that by storing it in a hidden page in the repository's wiki, reading and writing it with a github token with ${{ secrets.GITHUB_TOKEN }}

I am trying this out too at https://github.com/spacetelescope/acstools/pull/205 and it still crashes:
https://github.com/spacetelescope/acstools/actions/runs/9463279566/job/26068438067?pr=205

I am trying this out too at spacetelescope/acstools#205 and it still crashes:
https://github.com/spacetelescope/acstools/actions/runs/9463279566/job/26068438067?pr=205

oh whoops, I fixed the artifact issue:

but didn't pass any filenames to coverage combine 😅

Getting late here. @zacharyburnett , feel free to restart the CI over at https://github.com/spacetelescope/acstools/pull/205 to pick up new changes from this PR. Thanks!

Still not working
Run mv .coverage .coverage.ubuntu-latest-py39-test-alldeps
mv: cannot stat '.coverage': No such file or directory

Ah, looks like the test failed, so no coverage file was written. Maybe have the mv command skip if no coverage file is found.

Even when CI passes, it failed with the same error.
Coverage XML written to file coverage.xml
mv: cannot stat '.coverage': No such file or directory

it looks like --cov-report=xml is what's creating the coverage.xml; however, it should still be creating a .coverage database file... I'll so some local testing to see what files it spits out
https://github.com/spacetelescope/acstools/actions/runs/9463279566/job/26118526244#step:10:105
py312-test-devdeps: commands[2] /home/runner/work/acstools/acstools/.tmp/py312-test-devdeps> pytest --pyargs acstools --cov-report=xml --cov=acstools /home/runner/work/acstools/acstools/doc --cov --remote-data -v

running pytest --pyargs acstools --cov-report=xml --cov=acstools --cov --remote-data -v locally does appear to create the .coverage file:
❯ ls -a
.							CITATION.md
..							CODE_OF_CONDUCT.md
.bandit.yaml						LICENSE.md
.coverage						MANIFEST.in
.coverage.urelialia2022.local.stsci.edu.35749.XCMKciAx	README.rst
.git							__pycache__
.github							acstools
.gitignore						acstools.egg-info
.mypy_cache						conftest.py
.pytest_cache						coverage.xml
.readthedocs.yaml					doc
.tmp							pyproject.toml
.tox							tox.ini

What is the difference between .coverage and coverage.xm?

What is the difference between .coverage and coverage.xml?

I'm not intimately familiar with it, but as far as I know .coverage is a SQLite database file with support for parallel-mode (storing coverage for multiple machine configurations / runs) while coverage.xml is report-focused and so is expected to only contain results from a single run

Tried to debug at #209 but no luck. I see the coverage ran but the the upload failed: https://github.com/spacetelescope/acstools/actions/runs/9483014271/job/26134042811?pr=205

Tried to debug at #209 but no luck. I see the coverage ran but the the upload failed: https://github.com/spacetelescope/acstools/actions/runs/9483014271/job/26134042811?pr=205

could you also add -a to the ls?

Ah, yes, added. New log: https://github.com/spacetelescope/acstools/actions/runs/9483014271/job/26138000458?pr=205

testing done at https://github.com/spacetelescope/stpipe/actions/runs/9618208358

I see error in https://github.com/spacetelescope/stpipe/actions/runs/9618208358/job/26531763051 (despite the green status). Is this expected?
##[error]Process completed with exit code 1.

https://github.com/spacetelescope/stpipe/actions/runs/9618208358/job/26531763051

yes it should be, I tested with a run with no coverage at all to make sure it didn't adversely affect the step with a false failure

I think @astrofrog mentioned elsewhere that would be nice if there can be tests for this, but not sure how to add them.

BTW I think this fix #189 but only a maintainer can add that to the original post for auto-close to take effect. cc @Cadair

@zacharyburnett is this ready for re-review or you still working on it? Thanks!

@zacharyburnett is this ready for re-review or you still working on it? Thanks!

This is ready now, thanks!

Alas, still cannot get this to work with acstools. What am I doing wrong there?
https://github.com/spacetelescope/acstools/pull/205
https://github.com/spacetelescope/acstools/actions/runs/9669917380/job/26677517727?pr=205

Alas, still cannot get this to work with acstools. What am I doing wrong there?
spacetelescope/acstools#205
https://github.com/spacetelescope/acstools/actions/runs/9669917380/job/26677517727?pr=205

I'm not sure, this seems to be correct but the .coverage file isn't being created (only coverage.xml)

A lot of CI only outputs coverage.xml. I think this case also has to be handled.

A lot of CI only outputs coverage.xml. I think this case also has to be handled.

It was my belief that coverage always creates a .coverage file, and coverage.xml is an additional report file generated with coverage xml or --cov-report=xml; however, I guess that's wrong

@pllim would you mind rerunning that job now that 1f4a851 is pushed? It should pick it up

Here is the updated error log https://github.com/spacetelescope/acstools/actions/runs/9669917380/job/26717352610?pr=205

Maybe the coverage stuff is inside .tox

Maybe the coverage stuff is inside .tox

ah! You're using pyargs; perhaps that is causing this issue by moving the working dir to somewhere else

astropy also uses pyargs, so it is not uncommon. See https://github.com/astropy/astropy/blob/5519605a3b6ec71e9ddb4c6827b8ac1658647f58/tox.ini#L121-L122

looks like that fixed it https://github.com/spacetelescope/acstools/actions/runs/9683845227/attempts/1#summary-26720539461 thanks for being so patient! 😄

the failing test_conda tests are fixed by https://github.com/OpenAstronomy/github-actions-workflows/pull/123

Awesome, thanks! Now that the simple case of acstools works, I plan to open an experimental PR to astropy with this PR branch, or feel free to do it if you have time now as I cannot until later today.

Awesome, thanks! Now that the simple case of acstools works, I plan to open an experimental PR to astropy with this PR branch, or feel free to do it if you have time now as I cannot until later today.

sure thing, here: https://github.com/astropy/astropy/pull/16619
I don't have permissions to label that PR though

@astrofrog , do you want to take this for a spin on your repos?

pre-commit.ci autofix


⚠ Bofrost.be has degraded performance

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

HTTP code: 200
Response time: 2447 ms

Resolved: Bofrost.be performance has improved in 79b2fa1 after 6 minutes.


Update RepositoryBrowser.tsx

This should fix a bug that prints a duplicate repository ID when rendering an individual object's S3 URI.
Related Issue(s): #
None.
Proposed Changes:
This removes ${repositoryId} from the template used to render the S3 URI for an individual object because the repository ID is returned by {resultState.key}. I have not been able to test this because I haven't created a dev environment, so please test this and run through the PR checklist before accepting.
PR Checklist:

[X] This PR is made against the dev branch (all proposed changes except releases should be against dev, not main).
[ ] This PR has no breaking changes.
[X] This PR contains only one commit.
[ ] I have updated or added new tests to cover the changes in this PR.
[ ] I have updated the version in package.json to follow the Semantic Versioning guidelines.
[ ] All tests are passing.
[ ] I have added my changes to the CHANGELOG
or a CHANGELOG entry is not required.
[ ] This PR affects the Source Cooperative Data Proxy,
and I have opened issue/PR #XXX to track the change.

Oh cool. I was able to see this on the dev deployment in Vercel. Looks like it works, but would appreciate a review before it's accepted @navdeepg2021

Note I think you need us-west-2.opendata.source.coop/ at the front for the s3 url's to work.
On https://source-cooperative-git-fixing-s3-uri-path-radiantearth.vercel.app/vida/google-microsoft-osm-open-buildings/geoparquet/by_country/country_iso=AFG/AFG.parquet it's s3://vida/google-microsoft-osm-open-buildings/geoparquet/by_country/country_iso=AFG/AFG.parquet but that doesn't work. What does work is s3://us-west-2.opendata.source.coop/vida/google-microsoft-osm-open-buildings/geoparquet/by_country_s2/country_iso=AGO/2017612633061982208.parquet


feat: Added features for Preview Embeddings Models

https://cloud.google.com/vertex-ai/generative-ai/docs/embeddings/get-text-embeddings#latest_models

Add Output Dimensionality
Add additional embeddings types

could you extend an integration test, please?


Allow setting an instance creator for the built in types

I would like to use ArrayMap instead of HashMap as default but besides creating a parcel converter for each field I don't see any way of doing this.

You could create a global configuration using the @ParcelClass:
@ParcelClass(value = ArrayMap.class, converter = ArrayMapConverter.class)
class SomeClass{}

Then, every time an ArrayMap is found in an @Parcel class, ArrayMapConverter would be used to serialize it.

I don't like defining a specific implementation of a map in my classes but I guess that is one workaround

Related: #134 #135


empty DataFrame applymap methods returns an empty Series

I have an empty DataFrame which can be empty in some cases, when i cast applymap() and return the value it is a Series object.
v 0.18 and v 0.17.1

Duplicated issue, original one: https://github.com/pydata/pandas/issues/8222
Sorry guys!

@soujiro86 np. that is not too hard to fix, if you want to have a go.


Let users add custom procedures and constraints

Allow users to customize export easily by adding custom operations - GIMP PDB procedures (adjust brightness, scale, ...) or constraints (only chained layers, only layers below given opacity, ...). Users should also be able to adjust the parameters of each operation.
Custom operations should also be invoked if the plug-in is called in non-interactive mode, with the option to disable them.
As a side effect, some advanced features (Ignore layer modes, Export only layers matching file extension, ...) ought to be removed from the UI to reduce clutter in the UI (leading to UI redesign dealt with in issue #37). Instead, users should be able to add these features back as custom operations/constraints.

Custom procedures are implemented. Custom constraints will be implemented in Batcher.


Create ship script to tag and bag

yarn rollup
git add dist/, git commit -m "chore(dist): YYYY-MM-DD"
npm version ...
git push origin master --tags

built into package.json as version and postversion scripts


Differentiate between the different uses of "windows"

Throw in some proper noun and minor typo fixes as well.

Thanks!


Don't restart vite server on every schema change

@jeffsee55 When I save a file and the GQL server restarts I get a white screen and can not view the admin.
https://www.loom.com/share/9aa26c35560b44eaa06026a65d3c6aed

@logan-anderson I think this also needs to not clear out the app/prebuild folders in that reset logic. I'll update this PR on top of main now that that's merged and remove those two from the cleanup logic


Incorrect HTTP/1.1 501 Not Implemented log messge for websocket connection

Hi,
when connecting to BlazeWebSocketExample.scala if I change line 85 to:
.withHttpApp(org.http4s.server.middleware.Logger.httpApp(logHeaders = false, logBody = false)(routes.orNotFound))

then when I connect to WS instead of actual 101 Switching Protocols code:

in logs it prints:
14:45:18.748 [io-compute-3] INFO  org.http4s.server.middleware.Logger - HTTP/1.1 GET /ws?encoding=text
14:45:18.748 [io-compute-3] INFO  org.http4s.server.middleware.Logger - HTTP/1.1 501 Not Implemented

and also afterwards after disconnecting it prints incorrect Unknown type: Close or Unknown type: Close(Array(2)) (but this is example issue)

Ooh, this is tricky.  An implementation detail is that websockets are implemented as an HTTP fallback response (the 501) with an attribute that contains the websocket.  Backends that support web sockets look for this attribute and perform the connection upgrade instead of rendering the fallback response.  But the Logger middleware doesn't know about any of this trickery.
We could:

Special case web sockets in the logging middleware. (Yuck!)
Send back web sockets as a 101 response, and figure out some other way to gracefully degrade them to a 500.  (Yuck!)
???

/cc @ChristopherDavenport for logger expertise
/cc @RaasAhsan for recent work on web sockets in Ember

Yeah this is definitely a tricky one. This may just be a fundamental flaw in how http4s models middleware and web sockets. You see similar problems when isolated to middleware too. Imagine you position a logger middleware to execute before a retry middleware. Whenever an error happens, the logger is going to log the failed response, but then the retry middleware will throw that response away and perform the action again.
Obviously the solution for that example is to position the logger middleware after every other middleware, but it highlights the problem: middleware generally has no post facto context about what happens to a response. Similarly, any manipulation performed on a response by a backend will be hidden to a middleware
Another yucky solution to the problem is to expose backend-level middleware that runs right before a response is written to the socket. Its not composable and its backend-specific, but its general enough that there may be other use cases for it

Yes, I agree with Raas.  A long time ago, I tried to create a general event stream to peer deeper into these things that happen in the backends, but the backends are by nature not very general, and the event system was not particularly functional.  Our logging and metrics approach sacrifice a small slice of accuracy for general composition.  Servlets have their own metrics and logging, but Ember and Blaze, our two most popular, don't.
It has never been my itch, because I've always had some sidecar or cloud gateway in front that does know the "post facto context."  But that's a sorry answer.


Fix ORT training test & update

What does this PR do?

Update ORTTrainer to be compatible with transformers 4.24.0
Update CI to onnxruntime 1.13.0 CUDA 11.6
Fix training test (seq2seq, xsum metric)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Imstretch does not work

Hi
julia> VERSION
v"0.3.7"
julia> using Images

julia> img = imread("/home/elsuizo/Imagenes/galaxy2_gray.jpg")
Gray Image with:
  data: 800x701 Array{Gray{UfixedBase{Uint8,8}},2}
  properties:
    IMcs: Gray
    spatialorder:  x y
    pixelspacing:  1 1

julia> imstretch(img,.3,3)
ERROR: `eps` has no method matching eps(::Type{Gray{UfixedBase{Uint8,8}}})
 in imstretch at /home/elsuizo/.julia/v0.3/Images/src/algorithms.jl:1069

regards

Fixed in f82aa63640068c8a19877d85f555182a591f065b, which you can get with a Pkg.checkout("Images"). I'll tag a new release once I address a few more issues.

Hi Tim now this function does not work:
julia> using Images

julia> img = imread("/home/elsuizo/Optical_flow/Images/hamburg_tax2.jpg")
Gray Image with:
  data: 442x442 Array{Gray{UfixedBase{Uint8,8}},2}
  properties:
    IMcs: Gray
    spatialorder:  x y
    pixelspacing:  1 1

julia> imstretch(img,.3,.3)
ERROR: `+` has no method matching +(::Array{Gray{UfixedBase{Uint8,8}},2}, ::Gray{UfixedBase{Uint8,8}})
 in imstretch at /home/elsuizo/.julia/v0.3/Images/src/algorithms.jl:1069

julia> p = img[1,1]
Gray{Ufixed8}(1.0)

julia> p + img
ERROR: `+` has no method matching +(::Gray{UfixedBase{Uint8,8}}, ::Image{Gray{UfixedBase{Uint8,8}},2,Array{Gray{UfixedBase{Uint8,8}},2}})

but the + method for this case It seems to be well defined in(?):
https://github.com/timholy/Images.jl/blob/master/src/colortypes.jl#L434
Regards

Sorry, I didn't notice this. If I've closed something prematurely, does GitHub allow you to reopen it? If it does, it's a big help to me.

(Should really be fixed now.)

Works fine :smile:
Thanks for your time ¡¡¡
yes i look for reopen but i cant do

Ah, that's too bad. I guess best is to open a new issue, then.


Add check for system installed dart

Feature request
Add a check for the system installed version of DART before calling ament_vendor. For example on macOS the appropriate DART libraries are available from brew:
brew info dartsim
==> dartsim: stable 6.13.2 (bottled)
Dynamic Animation and Robotics Toolkit
https://dartsim.github.io/
Installed
/opt/homebrew/Cellar/dartsim/6.13.2_3 (1,081 files, 48.0MB) *
  Poured from bottle on 2024-05-08 at 23:03:42
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/d/dartsim.rb
License: BSD-2-Clause
==> Dependencies
Build: cmake ✔, pkg-config ✔
Required: assimp ✔, bullet ✔, eigen ✔, fcl ✔, flann ✔, fmt ✔, ipopt ✔, libccd ✔, nlopt ✔, ode ✔, open-scene-graph ✔, spdlog ✔, tinyxml2 ✔, urdfdom ✔

and do not need to be built again as part of the vendor build.
A suggested change (with debug messages) in this branch: https://github.com/srmainwaring/gz_dartsim_vendor/tree/rolling-macos

That looks good to me. Can you create a PR?

@srmainwaring Are you planning on following this up with a PR?


Do we have a function to play animation like Totem Of Undying when items are used?

If have  pls tell me how to use simplely, thx

yarn is for mappings, not for code tips

yarn 用于映射，而不是用于代码提示

ok sir


Change croatia.geojson from LineString to Polygon

Originally posted by @grischard in https://github.com/osmlab/osm-community-index/issues/193#issuecomment-435933479

thanks for flagging @grischard - I just fixed this 👍