use plug-in for colorschemes

possible solution for bar chart with one dataset:
https://github.com/nagix/chartjs-plugin-colorschemes/issues/11#issuecomment-513446623
Based on a workaround from this reply to another issue:
#7 (comment)
It is possible to access the underlying arrays of colours in the plugin. So you can directly apply the colours to a single dataset.
For example this simple bar graph has a single dataset with each bar being coloured using the 'Tableau10' palette.
var myChart = new Chart(document.getElementById('myChart'), {
type: 'bar',
data: {
labels: ['One', 'Two', 'Three', 'Four', 'Five', 'Six', 'Seven'],
datasets: [{
label: '# of things',
data: [12, 19, 3, 5, 2, 3, 4],
backgroundColor: Chart['colorschemes'].tableau.Tableau10,
}]
},
options: {
scales: {
yAxes: [{
ticks: {
beginAtZero: true
}
}]
}
}
});
As the palettes are simple arrays of hex strings they can be manipulated and extended to suit your data.

A plug-in for color schemes is used.
Added properties "ColorSchemaSource", "ColorSchemaCDN" and "ColorSchemaFilePath".
Added property "ColorSchema".
Released as version 1.13.28.


Default Configuration Should Respect Application Root

This is similar to #139 but the suggested workaround is not sufficient in my case.  We typically code our applications to be agnostic of the folder structure they are deployed.  That means that we aren't able to hardcode a base URL in the startup method.  Previously in 5x I was able to use the RootUrl configuration method to inspect the incoming request to generate the correct Swagger URL.
c.RootUrl(req => {
var pathBase = req.GetOwinContext().Get<string>("owin.RequestPathBase");
          return new Uri(
              req.RequestUri.ToString().Replace(
              req.RequestUri.PathAndQuery, string.Empty)
              + pathBase).ToString();
});

In the overload the UseSwaggerUi() method only accepts a static string.  If it was possible to provide it a lambda to generate the URL on request then I could recreate my previous workaround.
That being said, is there a reason the generated UI application has to default to the website root instead of the application root (~/)?  Seems like the latter supports both scenarios and does not introduce any unnecessary coupling between the UI app and the hosting application.

The first thing to note, if you haven't already, is that the semantics (and package name) have changed quite a bit in the most recent release - Swashbuckle.AspNetCore.1.0.0-rc1. Now, you're REQUIRED to specify one or more SwaggerEndpoints when enabling the swagger-ui middleware:
app.UseSwaggerUi(c =>
{
    c.SwaggerEndpoint("/swagger/v1/swagger.json", "My API V1");
})

It's worth noting that the first argument is a URL and not a "route". The value is passed down to the swagger-ui JavaScript client and used by that client to access Swagger JSON. It can be fully qualified or relative to the swagger-ui page.
"Application root" is a .NET, server-side concept and wouldn't make sense on a client. I could change this to accept a "route" instead and have the middleware construct the URL before passing down to the client. But then I'm introducing unwanted coupling between the Swagger JSON and SwaggerUi middleware - namely that they're always on the same host and same virtual directory.
I want to avoid this but I also want to optimize for the more common case - i.e. when they are part of the same app. So, I do have one idea that might achieve this. Consider the following configuration:

// By default - UseSwagger exposes Swagger JSON at /swagger/v1/swagger.json
app.UseSwagger();

// By default - UseSwaggerUi exposes swagger-ui page at /swagger/index.html
app.UseSwaggerUi(c =>
{
    c.SwaggerEndpoint("../v1/swagger.json", "My API V1");
})

As I mentioned, the argument to SwaggerEndpoint can be fully-qualified or relative to the current page. So, you could provide a value that is relative to "swagger/index.html" and agnostic of virtual directories as shown above. This actually works and I believe it will solve your problem. However, it has the downside of displaying your Swagger JSON URL in the UI as follows:
swagger/index.html/../v1/swagger.json
Not ideal but it could be fixed by updating SB to serve the UI page at "/swagger/" instead of "swagger/index.html". This would be cleaner anyway and it would also allow Swagger endpoints to be expressed relative to the swagger-ui page in a way that' agnostic of virtual directories. But, it would be a significant breaking change. Let me know if this makes sense - I'd be interested to get your thoughts ...

This change is now committed to master - 36c25c925bb18865abd04f0aa216f140f0cddd5b. Check out the preview package on myget - https://www.myget.org/feed/domaindrivendev/package/nuget/Swashbuckle.AspNetCore/1.0.0-preview-0101


ci: add codeowners

Adding codeowners to require reviews from the TSC.
@tasn we need to make the team public to be able to add the codeowners feature.

Nevermind, I figured it out. Done!


Update to Lambda v8.10

We just rolled out an update to the serverless portion of the guide to use Lambda Node v8.10. We also updated the Add support for ES6/ES7 JavaScript chapter to use the serverless-nodejs-starter. Here are the change sets for the update:

Tutorial changes
API

If you are looking to update your current project; change 6.10 to 8.10 in your serverless.yml and your .babelrc. You can also read about the benefits of Node v8.10 here - https://serverless.com/blog/aws-lambda-node-8-support-what-changes-serverless-developers/

Hey Jayair
Both links point to the same page - https://github.com/AnomalyInnovations/serverless-stack-demo-api/compare/v2.1...v2.2
Feel free to remove my comment once you update it. Regards!

Hi, I build an application using this guide. I started doing the tutorial end of last year and once it was done carried on building the app. Only now have I come back to see the updates and changes that the new version of the tutorial suggests. One of the main changes is using serverless-nodejs-starter but I am -a little bit confused. If I never used serverless-nodejs-starter to build my app how can I implement it now once it is already built. Because installing it adds a lot more plugins than the previous tutorial version had. How do I ensure I make the changes with an existing app? Just make the changes to suggested files or install the serverless-nodejs-starter? Thanks :)


Adding back storage.lookup_bucket.

This was originally removed in #588.
@tseaver I'd like to remove all the bucket functions from Connection and move them into api. WDYT?
Also it seems we'd eventually want to add a _require_connection as in datastore.api. It would be nice to come with a re-factor for re-usability (the Batch is the part which needs to be package specific).

FWIW: I came across this while trying to make implicit auth work in storage. Importing Connection in _implicit_environ creates a cycle, essentially because Connection imports Bucket.

Changes Unknown when pulling f50d036f2cc1fdf70a74dac6c3edf788863015b5 on dhermes:add-back-storage-bucket-lookup into ** on GoogleCloudPlatform:master**.

Moving the bucket-related functions to storage.api SGTM.

I'm not sure what the motivation is for re-adding the lookup_bucket() API.

@tseaver We don't need to add it back, but in the discussion in #588 you asked that we add it back, so I was trying to get the ball rolling with the storage.api module with something simple.

facepalm I should have gone back to look at #588.
LGTM.

Cool. I'll rebase #716 now.


⚠ Bofrost.es has degraded performance

In 571b053, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1487 ms

Resolved: Bofrost.es performance has improved in 7d987ea after 20 minutes.


Attributes for External Links Not Indexed

It's great that we can now associate page attributes with external links. Unfortunately, though, there doesn't seem to be an entry created in the CollectionSearchIndexAttributes table, which limits the utility. Case in point... I created an is_featured attribute for an external link so that it would appear in a page list. It didn't work. Manually adding the entry in the CollectionSearchIndexAttributes table fixed the issue.
Is there any reason this couldn't/shouldn't be allowed? I guess it means that external links would be treated a bit more like pages than aliases. This would have to be taken into account on deletion as well.
-Steve

This seems to be solved by PR https://github.com/concrete5/concrete5/pull/2911.
-Steve


[Spike] Specify pain points and explore other solutions in the market

AC:

Draft a doc on what specifically doesn't firebase serve our experimentation needs, what are we looking for in a new exp platform
Come up with 3 solutions in the market and compare pros and cons

Some exp platforms folks has mentioned/recommended: launchdarkly, split.io, stagsig


Use setf instead of set=

:setf[iletype] {filetype}                       :setf :setfiletype
                        Set the 'filetype' option to {filetype}, but only if
                        not done yet in a sequence of (nested) autocommands.
                        This is short for:
                                :if !did_filetype()
                                :  setlocal filetype={filetype}
                                :endif
                        This command is used in a filetype.vim file to avoid
                        setting the 'filetype' option twice, causing different
                        settings and syntax files to be loaded.

FYI this change exposes a bug that lies within Vim/Neovim. It wrongly detect Slim files starting with doctype html as HTML and thus setting the filetype to html. Since will in turn make this plugin not setting the filetype accordingly.
I've created an issue https://github.com/neovim/neovim/issues/4776 going into the problem in greater detail and hopefully we will see a fix for this within Vim/Neovim soon.
In the mean time, you can just explicitly set the filetype to slim for problematic files.


Problems viewing notebook diffs

FuseMachines are reporting multiple issues with the notebook diff view breaking, eg https://cloud.dotscience.com/project/229bf822-d3cb-403e-af6d-fde9a5c07218/runs/file/audio-tag%252Fnotebooks%252FCNN.ipynb/cf2d5227-61a0-4e51-85c3-cfd30f867e12?page=0
Seems to be a problem with the S3 interface used to fetch the notebook files; the FSMs are going into the backoff state and we're not sure why.

Gotcha:
time="2019-10-14T09:19:09Z" level=info msg="<transition> 66429de2-487e-4df3-839e-3e1c7a1f7a66 to active waiting (from active waiting, 0.83s ago)"
time="2019-10-14T09:19:09Z" level=info msg="entering active state for 66429de2-487e-4df3-839e-3e1c7a1f7a66"
time="2019-10-14T09:19:09Z" level=debug msg="[activeState] moving to next state" from=fileOutputIO
time="2019-10-14T09:19:09Z" level=info msg="<transition> 66429de2-487e-4df3-839e-3e1c7a1f7a66 to backoff pausing (from active waiting, 0.00s ago)"
2019/10/14 09:19:09 entering backoff state for 66429de2-487e-4df3-839e-3e1c7a1f7a66

Further logging reveals the next stage in the problem:
time="2019-10-14T15:04:40Z" level=error msg="[readFile] Error statting" error="stat<EMAIL_ADDRESS>no such file or directory" filename=audio-tag/notebooks/CNN.ipynb<EMAIL_ADDRESS>

The directory is there, but no CNN.ipynb inside it.
...is the problem that we're comparing the snapshot that CREATED CNN.ipynb to the snapshot before, when it didn't exist?
It seems so! There's two snapshots mounted:

6ef5e876-bddf-44ee-bbb7-7ed3cbfeae78 HAS CNN.ipynb
3965e857-246c-4e8a-931a-6860000dd80a does not have CNN.ipynb

The diff URL that's showing the 500 error is:
https://cloud.dotscience.com/diff?
base=%2Fv2%2Fprojects%2F229bf822-d3cb-403e-af6d-fde9a5c07218%2Ffiles%2Fsnapshot%2F3965e857-246c-4e8a-931a-6860000dd80a%2Faudio-tag%252Fnotebooks%252FCNN.ipynb%3FshortLivedToken%3DeyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2NvdW50X2lkIjoiOGE5ODA4MjAtOTM5MS00NTdlLTkyMDktZjczZTRjOGU5MjM3IiwiZW1haWwiOiJrc2hpdGl6Lm1hbmRhbEBmdXNlbWFjaGluZXMuY29tIiwiZXhwIjoxNTcxMTUxODc3LCJpYXQiOjE1NzEwNjU0NzcsInN1YiI6IjhhOTgwODIwLTkzOTEtNDU3ZS05MjA5LWY3M2U0YzhlOTIzNyIsInVzZXJuYW1lIjoia3NoaXRpem1hbmRhbCJ9._fiA2Ym4bxd5OtC0Iy5WFj36tHWZPtD3kjzJnaI_61MRTx0q1BhQIQLSNNXA95vJ36qALjMGFFwxN8c47ASJyg
&remote=%2Fv2%2Fprojects%2F229bf822-d3cb-403e-af6d-fde9a5c07218%2Ffiles%2Fsnapshot%2F6ef5e876-bddf-44ee-bbb7-7ed3cbfeae78%2Faudio-tag%252Fnotebooks%252FCNN.ipynb%3FshortLivedToken%3DeyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2NvdW50X2lkIjoiOGE5ODA4MjAtOTM5MS00NTdlLTkyMDktZjczZTRjOGU5MjM3IiwiZW1haWwiOiJrc2hpdGl6Lm1hbmRhbEBmdXNlbWFjaGluZXMuY29tIiwiZXhwIjoxNTcxMTUxODc3LCJpYXQiOjE1NzEwNjU0NzcsInN1YiI6IjhhOTgwODIwLTkzOTEtNDU3ZS05MjA5LWY3M2U0YzhlOTIzNyIsInVzZXJuYW1lIjoia3NoaXRpem1hbmRhbCJ9._fiA2Ym4bxd5OtC0Iy5WFj36tHWZPtD3kjzJnaI_61MRTx0q1BhQIQLSNNXA95vJ36qALjMGFFwxN8c47ASJyg
...and those are the snapshot IDs embedded in that URL.
Suggestions:

We probably don't need to go into backoff state when a file is not found in this case, but it's probably not doing any harm (now we have readFile logging). I'll remove the moving to next state logging but propose the readFile logging for master, and add the same sort of logging in saveFile.

We also need to return a useful 404 error when we request a nonexistant file via S3, to help spot this kind of problem faster in future. I'll see if I can do that too.

We need to think about the desired UX for looking at a diff that creates (or deletes?) a file and implement that!

Product feedback on point 3: https://dotscience.slack.com/archives/C7PHSRL82/p1571070744378500

PR for point 1: https://github.com/dotmesh-io/dotmesh/pull/758

PR for point 2: https://github.com/dotmesh-io/dotmesh/pull/759

Point 3 is to be resolved by:

Adding HEAD support to the S3 API so we can cheaply check for nonexistant files
Making the nbdiff proxy in the gateway use the S3 HEAD support to detect when a diff will fail in this case (see https://github.com/dotmesh-io/gateway/compare/dotmesh-757?expand=1 for the code implementing this)
Changing the frontend to detect the 400 status code returned by the nbdime proxy and displaying something else (TBD)


This project is very useful, hope to continue to update

This project is very useful, hope to continue to update

https://github.com/ollama-webui/ollama-webui-lite/pull/31


Adds support to filepath_from_url to support non-encoded URLs

filepath_from_url works for encoded URLs but not for URLs that are not encoded. I encountered this when working with URLs from both .xml and .aaf files.
The .xml file came from Premiere and encoded the URL while the .aaf came from Avid and the URL was not encoded.
Examples:

"file://localhost/S%3a/path/file.ext" -> "S:/path/file.ext"
"file://S:/path/file.ext" -> "/path/file.ext"

My PR updates the code to return the same result with both of the example URLs:

"file://localhost/S%3a/path/file.ext" -> "S:/path/file.ext"
"file://S:/path/file.ext" -> "S:/path/file.ext"

I tested and dev-ed this on Windows with OTIO 0.15.0 and 0.16.0.dev1. Admittedly, I am not sure if this approach is valid for Linux paths but I am open to feedback and updating the approach further.

Codecov Report

Merging #1664 (9617fb0) into main (5e27e78) will increase coverage by 0.88%.
Report is 29 commits behind head on main.
The diff coverage is 33.33%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1664      +/-   ##
==========================================
+ Coverage   78.94%   79.82%   +0.88%
==========================================
  Files         200      197       -3
  Lines       21743    21756      +13
  Branches     4401     4352      -49
==========================================
+ Hits        17164    17367     +203
+ Misses       2350     2234     -116
+ Partials     2229     2155      -74

Flag
Coverage Δ

py-unittests
79.82% <33.33%> (+0.88%)
:arrow_up:

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

Files Changed
Coverage Δ

src/py-opentimelineio/opentimelineio/url_utils.py
77.77% <33.33%> (-22.23%)
:arrow_down:

... and 63 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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

Looking at the documentation (https://docs.python.org/3/library/urllib.request.html) , and searching error reports, it seems pretty clear that the urllib has not had a lot of attention around aspects such as drive letters and windows specific encodings. It's disappointing that we need to do this, but I think it's necessary.
Have you filed any issues with urllib around this, as the problem does seem to lie at their end. We should not gate merging this PR on such resolution, but it seems like something needs to happen upstream for the benefit of all.

Now that we've left python 2 behind I think we could start using pathlib for some of this as well.

Have you filed any issues with urllib around this, as the problem does seem to lie at their end. We should not gate merging this PR on such resolution, but it seems like something needs to happen upstream for the benefit of all.

@meshula, now that you mention it you're right this is a urllib issue and not OTIO's`. The motivation for this PR was to offload the responsibility of maintaining this code in a custom hook I made and help future developers looking to use OTIO on WIndows. Incorporating this into OTIO seems like the quicker route for now.
I looked through the cpython repo and found these open tickets that seem to relate to this very issue:

https://github.com/python/cpython/issues/90812, which led to this proposal: https://discuss.python.org/t/file-uris-in-python/15600
https://github.com/python/cpython/issues/85168

Since this issue is known on the cypthon that is still being debated I'm not sure if there is any benefit opening a new issue that is similar to existing ones.

Now that we've left python 2 behind I think we could start using pathlib for some of this as well.

@apetrynet, what were you thinking about using pathlib here? I also found this closed PR about generating Path from a URL, https://github.com/python/cpython/issues/91504.

Now that we've left python 2 behind I think we could start using pathlib for some of this as well.

@apetrynet, what were you thinking about using pathlib here? I also found this closed PR about generating Path from a URL, python/cpython#91504.

I was thinking about some windows path handling, but looking at it I'm not sure it'll help in this case.

@douglascomet Could you please look at the failed CI task? It looks like a simple fix removing the unused "re" import


windows doesnt support habitat...

as title

We tested our method in Ubuntu 20.04. If you would like to use habitat on Windows, you can install a virtual machine on Windows to get the Ubuntu environment.


PowerShell.exe crash on 2012r2

Running jobs on Windows Server 2012r2 results in a crash after the job has executed.

Stack trace points to gRPC charp DLL.

Resolved in 1.0


Dev | Enable strict null checks in Azure Core extension

Opening this issue to track code improvement based on feedback: https://github.com/microsoft/azuredatastudio/pull/20516#discussion_r959843417
cc @Charles-Gagnon

This has been done


I added a new library to e2e that builds and parses PGP/MIME messages.

The original library was built by Yan Zhu from yahoo.
I've ported the library to e2e and made a number of changes to the original code.
The library will require some more work before it's finished, but I'd appreciate any advice/feedback at this point.
As of now, the library only supports the building of an outgoing PGP/MIME message.
Next week I'll add the parsing of incoming messages.

Hi Yan,
The primary changes I've made are:

Mime nodes are more generalized (see mimenode.js), so they can suit a broader range of purposes.
pgpmail.js takes in an encrypted, ascii-armored text and inserts it into a PGP/MIME format. The encryption and signing of the text is handled externally (for now).
This current release doesn't include the code for parsing an incoming PGP/MIME message. I will add that in later this week.

Please let me know what you think.
Thanks,
Yoni

Cool, very glad this is being worked on again. One general comment - this would be easier to review if you had preserved commit history (i.e., add commits on top of my pgp/mime branch instead of putting changes in a single commit). Also so that people can git-blame me for bugs. :)

Closing since it has been replaced by #323


datadog: honor extracted sampling decisions

Commit Message: honor extracted sampling decisions in the datadog tracer
Additional Description: See below.
Risk Level: low
Testing: See below.
Docs Changes: N/A
Release Notes (under bug fixes): honor extracted sampling decisions in the datadog tracer
Platform Specific Features: N/A
The Issue and Its Solution
Envoy users within Datadog noticed another bug caused by the migration of the Datadog tracer from OpenTracing to dd-trace-cpp that was released in Envoy 1.27.
Sometimes the Envoy spans are missing from the flame graphs of traces, and sometimes the entire subtree starting at the Envoy span is missing from the flame graphs of traces.
Datadog tracing in Envoy used to use the OpenTracing driver, but it has not since Envoy v1.27.
The OpenTracing driver sets the "sampling priority" to zero ("drop the trace") whenever bool Envoy::Tracing::Decision::traced is false. It does this regardless of whether a sampling decision was extracted from incoming request headers (e.g. x-b3-sampled or x-datadog-sampling-priority).
I followed suit in the non-OpenTracing Datadog tracer, but I missed something. The OpenTracing-based Datadog tracer, dd-opentracing-cpp, ignores sampling changes whenever a sampling decision has already been extracted from an incoming request.
So, in the OpenTracing-based code, when a sampling decision is extracted from an incoming request, here's what happened:

The trace's sampling decision is set to whatever was extracted.
If Envoy's sampling decision was "drop," then that decision is ignored even through the OpenTracing code tries to set the trace's decision accordingly.

The result is that extracted sampling decisions are always honored.
With the newer dd-trace-cpp based code, when a sampling decision is extracted from an incoming request, here's what happens:

The trace's sampling decision is set to whatever was extracted.
If Envoy's sampling decision was "drop," then the trace is dropped regardless of what was extracted.

So, if Envoy's configured sampling rate is less than 100%, users will see incomplete traces whenever Envoy is not the "root service." In some such traces, Envoy spans and possibly its descendants are missing.
This is a bug.
This revision restores the logic from the OpenTracing-based tracer: An Envoy decision of "drop" forces a dropped trace only if we haven't extracted a decision from an incoming request.
Testing
I added a unit test that checks a table of possiblities.
I also built Envoy and configured it to reverse proxy httpbin.org/headers with 1% sampling. Then I hit it with curl using a variety of propagation headers, such as x-datadog-sampling-priority and traceparent, and verified that the resulting sampling decision was consistent with what I sent.
When I don't send sampling information in the request headers, the resulting sampling decisions are consistent with Envoy's configured 1% rate.
Bug Fix
Please consider this PR as a bug fix so that it might be backported onto the v1.27 and v1.28 release branches.

@cgilmour, my teammate who figured out what the problem was.

/assign-from @envoyproxy/envoy-maintainers

/assign-from https://github.com/orgs/envoyproxy/teams/envoy-maintainers

/assign-from @envoyproxy/envoy-maintainers

Thanks for the kind words, @RyanTheOptimist. I'll update the changelog.
Also, what is the process for having this PR considered for backporting onto v1.27 and v1.28 as a bug fix?

Also, what is the process for having this PR considered for backporting onto v1.27 and v1.28 as a bug fix?

Good question. @phlax, how do we usually handle bugfix backports?

/backport

Good question. @phlax, how do we usually handle bugfix backports?

mark it for backport and then if a pr hasnt been raised already i look at when raising backports
@dgoffredo if you are up for doing the backports the target branches are:

release/v1.28
release/v1.27
etc

@dgoffredo if you are up for doing the backports the target branches are [...]

Will do.

I'm working on the backport PRs for release/v1.27 and release/v1.28 now.
Should we first merge these changes into main to finalize the behavior before I propose the backports?

I've created two additional pull requests, one for backporting these changes to the v1.27 release branch, and another for the v1.28 release branch:

PR for release/v1.27: https://github.com/envoyproxy/envoy/pull/30750
PR for release/v1.28: https://github.com/envoyproxy/envoy/pull/30751

@phlax are we OK to merge this PR or is there any addition process we need to follow?

Matt merged the backports onto release/v1.27 and release/v1.28.
@phlax Are we good to merge this into main?


Travis CI for Build/Test & Docs

Use Travis to build, test and docs. Add the Travis badge of success/shame to the README

Build is running. I've included the stable and beta channels, even though they don't build because I intend to support them eventually.
Windows would also be good to add.

Appveyor is now in for Windows build. This isn't using the .sln because it needs a lot more setup to get going.
The version numbers now need to be synced.


Scala flaky test: testObjectDetectionExample and GanExampleSuite

- testObjectDetectionExample

[ScalaTest-main-running-GanExampleSuite] INFO org.apache.mxnetexamples.gan.GanExampleSuite - GPU test only, skipped...

[ScalaTest-main-running-DiscoverySuite] INFO org.apache.mxnetexamples.profiler.ProfilerSuite - Running profiler test...

[ScalaTest-main-running-DiscoverySuite] INFO org.apache.mxnetexamples.profiler.ProfilerSuite - profile file save to /tmp

terminate called after throwing an instance of 'dmlc::Error'

GanExampleSuite:

- Example CI: Test GAN MNIST

  what():  [06:41:27] src/c_api/c_api_profile.cc:141: Check failed: !thread_profiling_data.calls_.empty():

Stack trace:

  [bt] (0) /work/mxnet/scala-package/native/target/libmxnet-scala.so(dmlc::LogMessageFatal::~LogMessageFatal()+0x64) [0x7f3cbd6f7a44]

  [bt] (1) /work/mxnet/scala-package/native/target/libmxnet.so(mxnet::on_exit_api()+0x514) [0x7f3bc7355624]

  [bt] (2) /work/mxnet/scala-package/native/target/libmxnet.so(MXNDArrayFree+0x2a) [0x7f3bc73a83fa]

  [bt] (3) [0x7f3d7103f740]

http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-17057/1/pipeline/

Another one - http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-17482/4/pipeline
#17482

Another one - http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-17487/13/pipeline #17487

This seems to be a general bug with the scala API, as it happens for random test cases (just observed in "Example CI: Test CustomopRtc MNIST" http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-17984/32/pipeline/372 )
cc @lanking520 @zachgk

Again http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-18553/1/pipeline
#18553


[Feature] Support for ZTE zxhn H1600

Description of new feature
e.g. I would like the zte zxhn h1600 router to be supported. My ISP (OTE GR) uses them and would be nice to extract / edit their config
Describe alternatives you've considered
I have tried using --try-all-known-keys & --serial , it would recognize the config file comes from a H1600 but it wouldnt decript it
Attach config.bin for your device
config.zip
Fresh config out of a RTFDed CPE .
im awaiting a EEPROM reader (CH341) to dump its flash , could be useful .
i do not have a firmware file from my isp they dont give them out but i found this firmware from a foreign isp
Exetel.zip

the ZTE H3600 mention on #76 has the same HW minus the DSL modem as the h1600 i mention here

This router uses a per-device encryption key stored in the tag partition of the NAND. It is impossible to decrypt them without those keys.


Audio isses - Oculus Go casting

I am currently using scrcpy to cast from 4 Oculus Go's during a one-on-one performance piece. Each performance runs for about 45-50 minutes during which 2 headsets are connected to 1 Macbook pro. One of the headsets loses audio quite suddenly during casting on multiple occasions. Is there any reason this could be connected to using scrcpy? It doesn't really happen outside of casting and we're using Skybox VR player to run the videos. Please help!

Is there any reason this could be connected to using scrcpy?

Hmmm, no. Scrcpy does not even play audio (for now).


typo: Microsoft.Fabric.Admin

requestd -> requested
visiblity -> visibility
sftware -> software

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

Automation for azure-sdk-for-js

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java


[SPARK-23888][CORE] speculative task should not run on a given host where another attempt is already running on

What changes were proposed in this pull request?
There's a bug in:
/** Check whether a task is currently running an attempt on a given host */
 private def hasAttemptOnHost(taskIndex: Int, host: String): Boolean = {
   taskAttempts(taskIndex).exists(_.host == host)
 }

This will ignore hosts which only have finished attempts, so we should check whether the attempt is currently running on the given host.
And it is possible for a speculative task to run on a host where another attempt failed here before.
Assume we have only two machines: host1, host2.  We first run task0.0 on host1. Then, due to  a long time waiting for task0.0, we launch a speculative task0.1 on host2. And, task0.1 finally failed on host1, but it can not re-run since there's already  a copy running on host2. After another long time waiting, we launch a new  speculative task0.2. And, now, we can run task0.2 on host1 again, since there's no more running attempt on host1.
How was this patch tested?
Added.

Can one of the admins verify this patch?

ping @pwendell @kayousterhout . pls help review, thanks :)

Can one of the admins verify this patch?

Jenkins, ok to test

sounds fair, but shouldn't this be up to the scheduler backend? multiple tasks/attempts can run simultaneously on the same physical host?

Test build #89026 has started for PR 20998 at commit 3584a09.

Hi, @felixcheung , thank for trigger a task and your comments.

shouldn't this be up to the scheduler backend?

Actually, it is TaskSchedulerImpl who holds a thread to check whether there are any speculative tasks need to be scheduled periodically. If any, then, call backend.reviveOffers to offer resources  . But, it's TaskSetManager who decides whether we need to launch a speculative task for a certain task.

multiple tasks/attempts can run simultaneously on the same physical host?

I think multiple task attempts(actually, speculative tasks) can run on the sam physical host, but not simultaneously, as long as there's no running attempt on it. In PR description, I illustrate a case which a speculative task chose to run on a host, where a previous task attempts have been run on, but failed finally. I think if the task's failure is not relevant to the host, 'run on the same host' can be acceptable.

Test build #89026 has finished for PR 20998 at commit 3584a09.

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

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

Merged build finished. Test PASSed.

Adding isRunning can cause a single 'bad' node (from task pov - not necessarily only bad hardware: just that task fails on node) can keep tasks to fail repeatedly causing app to exit.
Particularly with blacklist'ing, I am not very sure how the interactions will play out .. @squito might have more comments.
In general, this is not a benign change imo and can have non trivial side effects.
In the specific usecase of only two machines, it is an unfortunate side effect.

Hi, @mridulm, thank for your comment. Actually, I have the same worry with you. May be we can make this change as a second choice for hasAttemptOnHost , in case of there's really no other hosts to select.

Hi, @squito . Thank for review and comments.

Test build #89164 has started for PR 20998 at commit 2ed9584.

Test build #89164 has finished for PR 20998 at commit 2ed9584.

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

Merged build finished. Test PASSed.

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

@mridulm more thoughts?  I think this is the right change but I will leave open for a bit to get more input

@squito My concern is, in large workloads, some nodes simply become bad for some tasks (transient env or hardware issues, colocating containers, etc) while being fine for others; speculative tasks should alleviate performance concerns and not increase chances of application failure due to locality preference affinity. For cluster sizes which are very small, speculative execution is less relevant than for those which are large - and here we are tuning for the former.

Test build #89228 has started for PR 20998 at commit 5901728.

Merged build finished. Test PASSed.

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

I'm not even really concerned about the case for two hosts -- I agree its fine if we do something sub-optimal.  I'm more concerned about code-clarity and the behavior in general.  It seems cleaner to me if speculation doesn't worry about where its failed before, and those exclusions are left to the blacklist.
But it sounds like you're saying the prior behavior was really desirable -- you think its better if speculation always excludes hosts that task has ever failed on?  I'm happy to defer to your opinion on this, I haven't really stressed speculative execution yet.  Then lets just change that comment in the code to be consistent.

@squito I completely agree that the comment is inaccurate.
Note that this is for a specific taskset, so impact is limited to that taskset (w.r.t using executors for spec exec)

@Ngone51 can you instead leave the behavior as is, and just update the comment?
Sorry that its going to be a small change in the end, and all the extra work the bad comments led you to do, but still appreciate you noticing this and fixing.  a good PR with a quality test too.

Will do, and it's okay.
My view limited in the source code yet, but you guys have more practical experience. So I learned from your points. It's beneficial.

Test build #89460 has started for PR 20998 at commit 0c6f305.

Test build #89460 has finished for PR 20998 at commit 0c6f305.

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

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

Merged build finished. Test PASSed.

LGTM

Test build #89728 has started for PR 20998 at commit e44d80b.

Test build #89728 has finished for PR 20998 at commit e44d80b.

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

Merged build finished. Test PASSed.

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

merged to master, thanks @Ngone51  .  I also updated the commit msg some before committing, I thought it best to focus on the eventual change, figured it wasn't worth bugging you for another update cycle.

Agree and thank you @squito .
And thanks for all of you. @felixcheung @mridulm @jiangxb1987 @srowen


Fix for Frame's level=-1

When frame's level=-1, make it 0 since it is represented by uint
Fix spelling error

Fix for #144
@paulmaybee @gregg-miskelly

This feels like the wrong fix to me -- we use the frame id to control what frame we use in subsequent evaluations. So if we handle it this way we will wind up switching back to the root frame and issuing evaluations there. Seems like we should instead change this to a 'uint?' and implicitly fail any call that requires frame affinity.

Can you reproduce this bug?  I have only seen it occur when the architecture of gdb was not matched with the architecture of gdbserver (for example trying to use an x86 gdb to debug remotely to an arm device).

@paulmaybee yes, that is the exact instance I kept running into it.

Then this in not the right fix. The right fix is to use the arm gdb.

And by that I mean one compiled for x86 but targeting arm.

We should probably also behave better by looking at Gregg's suggestion about uint? as the option. I will abandon this for now and might take a look again when I have time.


Update very old version of qpOASES library

Bundled version is 1.3
https://github.com/commaai/openpilot/blob/devel/phonelibs/qpoases/VERSIONS.txt
Latest version is 3.1
https://projects.coin-or.org/qpOASES/browser/trunk/VERSIONS

Unfortunately version 1.3 is the only version supported by the code generation part of Acado, our Non-Linear Model Predictive Control library.
Unfortunately it looks like acado is no longer being developed. However, there is not much choice in NPMC libraries that can run real-time on embedded hardware. At some point I might decide to write a subset of acado functionality for use in openpilot, but that is a huge undertaking.

FYI Acado does support the C version of qpOASES 3.1.
Just use:
mpc.set(QP_SOLVER, QP_QPOASES3);

Good catch, I'll check it out!


MDC: Adding 2024-07-01-preview version to SecurityConnectors API [Introducing new Docker-Hub Environment]

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

NOTE
This Pull Request already reviewed in the private repo (i.e., azure-rest-api-specs-pr), you can see it here
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[X] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[X] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[X] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

/azp run

/azp run

/azp run


Added ability to return a promise from an app's index.js function

Implements #131

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

As discussed via Slack: startApp.js mimicks the Metrological App Platform during local development. So while this change works locally, it won't work in the context of the App store.
In the case of DIY hosting a likewise solution can be custom added to the index.html (created via lng dist-command).


add txt2stix variables into .env

OPENAI_MODEL=gpt-4 # [REQUIRED IF USING AI MODES] choose an OpenAI model of your choice. Ensure the input/output token count meets requirements (and adjust INPUT_TOKEN_LIMIT accordingly). List of models here: https://platform.openai.com/docs/models
INPUT_TOKEN_LIMIT=50

I don't underdtand, this is alresdy env variable

stale ticket. closing


Script storage resets on every reload

Hello, thanks for writing this script.
I am having the problem that I want to select the prices to be shown in euros. Selecting Germany as the region works fine, and the price is displayed correctly. However, if I reload the site, the region is reset to US and US dollars are shown again.
From a quick look at the code, it seems like this line is the problem. If the collapsed value is set to false the entire condition evaluates to false and the else-block is executed, which resets the settings to default.
https://github.com/kevinfiol/enhanced-gog/blame/ca5fdb08302b184bc93279eae179948e932a26db/src/index.js#L93

@jarikmarwede Thank you for opening the issue and finding the root cause.
I pushed up an update (1.5.1) that should fix this.


By sending a "garbage" byte we're keeping the socket open to hostedgr…

…aphite.

It should not be a problem now, because we don't maintain a persistent TCP connection to Graphite anymore in 3.1.1 and 3.2.0. But the idea is good, I believe the Apache HTTP Client does something similar to detect dead connections in the pool.

@arteam PickledGraphite is maintains a persistent socket in 3.2 development branch?

No. PickledGraphite is just an implementation of GraphiteSender, which is supplied to a GraphiteReporter. GraphiteReporter invokes the connect method on the sender, send metrics, flushes them, and the invokes the close method. So a new TCP connection opens every time.

@arteam Is that the intended design? Because that's not how Druid graphite extension is doing which is using this library[1] from what I can understand. Nor does it seem to be with given these two tickets #664 #694. Am I missing something here?
[1] https://github.com/druid-io/druid/blob/master/extensions-contrib/graphite-emitter/src/main/java/io/druid/emitter/graphite/GraphiteEmitter.java

No, it's not the original design. The mechanism was changed in the 3.1.3 and 3.2.0 versions (they were released last week), because many users reported issues with persistent connections; a connection could become broken and there were no reliable approach, how to detect it. The new approach leads to bigger latencies during sending metrics (3-way handshake is rather expensive), but on the other hand guards against halted reporters.

I think the Druid database could try to use this approach as well or try to maintain a pool of renewable PickledGraphite instances.

Thanks! I'll keep it in mind when discussing it with Druid guys. I wasn't planning on creating a PR to dropwizard but rather our own forked version of it but thanks for commenting!

Glad to help.


"Amazon Web Services filtered by OpenShift" forecast

Added the "Amazon Web Services filtered by OpenShift" forecast
https://issues.redhat.com/browse/COST-825

Codecov Report

Merging #1781 (0da59a4) into master (94d74e0) will increase coverage by 1.06%.
The diff coverage is 47.82%.

@@            Coverage Diff             @@
##           master    #1781      +/-   ##
==========================================
+ Coverage   77.00%   78.06%   +1.06%
==========================================
  Files         295      296       +1
  Lines        4761     5225     +464
  Branches      906     1190     +284
==========================================
+ Hits         3666     4079     +413
- Misses        993     1127     +134
+ Partials      102       19      -83

Impacted Files
Coverage Δ

...rd/awsCloudDashboard/awsCloudDashboardSelectors.ts
50.00% <ø> (ø)

src/api/forecasts/forecastUtils.ts
30.00% <25.00%> (-5.72%)
:arrow_down:

...oard/awsCloudDashboard/awsCloudDashboardActions.ts
32.00% <25.00%> (-3.30%)
:arrow_down:

...board/awsCloudDashboard/awsCloudDashboardCommon.ts
35.29% <50.00%> (-2.64%)
:arrow_down:

src/api/forecasts/awsCloudForecast.ts
66.66% <66.66%> (ø)

src/api/forecasts/forecast.ts
100.00% <100.00%> (ø)

...oard/awsCloudDashboard/awsCloudDashboardWidgets.ts
100.00% <100.00%> (ø)

src/components/i18n/i18nProvider.tsx
57.14% <0.00%> (-9.53%)
:arrow_down:

src/pages/state/maintenance/maintenanceState.tsx
66.66% <0.00%> (-8.34%)
:arrow_down:

src/store/common.ts
81.81% <0.00%> (-7.08%)
:arrow_down:

... and 102 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 94d74e0...0da59a4. Read the comment docs.


Regression with right click on blue objects

Type
Incorrect behavior
Operating System
Windows
OS Version
No response
Bug description
There seems to be a regression due to https://github.com/runelite/runelite/commit/9aabc88058fc61e53ae757a143682ce2309e9b09. When right clicking blue objects (e.g., bank chest) the menu is no longer shown by default. This means that it is not possible to collect from the chest only use it.
Enabling Right click objects in the camera settings fixes this.
Screenshots or videos
Without right click objects, cannot interact with the menu:

With right click objects you can:

RuneLite version
Runelite: <IP_ADDRESS>
Oldschool: Rev 215
Launcher 2.1.0
Logs
No response

Can confirm. Saw the same on MacOS and got really confused. After resetting the plugin's default settings, the problem was fixed for me.

The default behavior of the plugin was changed, with Right click objects being added to use the previous behavior. So this is working as intended.

Would it be possible to have right click objects enabled by default? By being disabled by default it means there are a few places with issues. For example, the inability to use the teleport option on GWD altars.

By default right click moves camera is off, and so this isn't a problem normally. You must have had right click moves camera on, and with the new changes it becomes right click moves camera on + right click objects off. The thought was people prefer to remap mmb to right click using "Middle-button opens menu". But maybe that is not true. I honestly was not aware so many people used this right clicking camera behavior.

Ah that explains it, I do use left click to rotate camera. I wouldn't say there is a lot of us, this might just be a case of xkcd 1172. I'm happy for the issue to be closed as there is a way to re-enable the old behaviour.

This behavior change was unexpected and I had to search here to find out how to enable the legacy behavior. Please consider rolling back this change.

Okay. I've changed the default behavior back to right clicks move camera=off right click objects=on bc4bb30dde0025860a4eb75a9ce505b16f64548c and then also included players/npcs/items in "right click objects".


Add Jekyll Paginate Gem

Building off the following image: https://hub.docker.com/r/jekyll/jekyll/
With this in the _config:
gems: [jekyll-paginate]

Leads to this:
Configuration file: /Users/jhabdas/Developer/technologyadvice.github.io/_config.yml
/usr/local/lib/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- jekyll-paginate (LoadError)
	from /usr/local/lib/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/lib/jekyll/plugin_manager.rb:30:in `block in require_gems'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/lib/jekyll/plugin_manager.rb:27:in `each'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/lib/jekyll/plugin_manager.rb:27:in `require_gems'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/lib/jekyll/plugin_manager.rb:19:in `conscientious_require'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/lib/jekyll/site.rb:97:in `setup'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/lib/jekyll/site.rb:49:in `initialize'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/lib/jekyll/commands/build.rb:30:in `new'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/lib/jekyll/commands/build.rb:30:in `process'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/lib/jekyll/commands/serve.rb:26:in `block (2 levels) in init_with_program'
	from /usr/lib/ruby/gems/2.2.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `call'
	from /usr/lib/ruby/gems/2.2.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `block in execute'
	from /usr/lib/ruby/gems/2.2.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `each'
	from /usr/lib/ruby/gems/2.2.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `execute'
	from /usr/lib/ruby/gems/2.2.0/gems/mercenary-0.3.5/lib/mercenary/program.rb:42:in `go'
	from /usr/lib/ruby/gems/2.2.0/gems/mercenary-0.3.5/lib/mercenary.rb:19:in `program'
	from /usr/lib/ruby/gems/2.2.0/gems/jekyll-3.0.1/bin/jekyll:17:in `<main>'

This is a common plugin. Why is it not included in the Current Gems?

:+1:

Looks like the paginate gem is available with the :pages docker image. It'd be nice to see this more clearly defined in the README.

I do not keep track or list Github's dependencies, I leave that to them to do.  If you would like it to be included on all tags then ask that, I don't think you want the answer to your current question.


Delete feature.textproto

This proposes to deprecate the feature.textproto data from this repository, at least temporarily.
These files were intended to assert some list of paths that were convenient for people to refer to when describing some feature of a network device.  These would in turn guide the organization of functional/ondatra tests to be created.
In practice, we document the intended OC paths to be tested in README.  The feature.textprotos are sometimes maintained and other times not so they are not kept up to date.  Having two places in the repository which are maintained by hand leads to problems with keeping things in sync.
A proposed step to aid in ensuring the OC paths specified in README are formatted properly and are valid is to use a YAML format embedded in the readme which could be automatically parsed and checked.   See https://github.com/openconfig/featureprofiles/pull/2746 for an example work in progress.

Pull Request Functional Test Report for #2793 / 38057ab810d34b93aeaf08fb17c08a18dfc79c32
No tests identified for validation.
Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 54.484%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1847

Relevant Lines:
3390

💛  - Coveralls

Personal opinion: The FeatureProfile is useful for explicitly identifying the branch points for features / subfeatures / sub-subfeatures etc, as well as providing metadata about each given Feature. This use is separable from whether or not the FeatureProfile is also used for tracking OC paths.

I generally think it sounds less than ideal for the official mechanism for determining if a path is covered by a test is "parse the readme markdown, look for section X, parse the body of the section as yaml, marshal it into proto paths, and validate the paths exist".
Regardless, the contents of feature.textproto is actively validated against OC models.  The tooling around this would need to be removed if this is being deprecated:
https://github.com/openconfig/featureprofiles/blob/8856fd89b1b3f9ff0c1f7430741dabe6a3a9ad1b/Makefile#L17-L24
https://github.com/openconfig/featureprofiles/blob/8856fd89b1b3f9ff0c1f7430741dabe6a3a9ad1b/README.md?plain=1#L178-L181
https://github.com/openconfig/featureprofiles/blob/8856fd89b1b3f9ff0c1f7430741dabe6a3a9ad1b/.github/workflows/protobufs.yml#L87-L123
And the validation code in tools/validate_paths.go

It seems to me that test authors should document a subset of the total paths exercised in a test, as a way to indicate which paths are specific to the Feature (vs setting up context for the test). I believe there is no good way to know that programmatically, unless the author specifies it.
It's also true that, in many cases, configuration of a Feature requires a set of paths which is greater than any one test might exercise. (example: BGP, counter-example: NTP) And, like tests, there is no good way to know programmatically which paths are essential to the Feature, unless they are specified by somebody who is an expert in the Feature. (If it were possible to say something simple like "Feature X requires all paths in this branch / model / whatever" then that might not be true, but that doesn't seem to be the case for many features today.)
So, I think that a) we need feature.textproto to include a set of paths that are essential to the Feature, and b) we need a PR check to ensure that all paths in a README are also included in the feature.textproto for the Feature being tested. It's possible to use (b) to automatically add paths to feature.textproto, and perhaps thus auto-generate it. But if that's the only way that paths are populated in feature.textproto then it wouldn't necessarily possess the quality that I described in the 2nd paragraph.

If the goal of featureprofiles is to document the set of paths that belongs to a feature, then that is necessarily manually curated.
As Brandon pointed out validate_paths.go and any existing tooling that depends on feature.textproto will break, and so deleting feature.textproto will mean we need to migrate all such tooling to parse YAML.
I think an easier way to have a single SoT for features is to have a tool that parses the proposed YAML and auto-populates feature.textproto so that no tooling will break. A CI check can be created to make sure feature.textproto is kept up-to-date.
So I think the right steps are 1. Decide where to store the manual SoT (source-of-truth) for feature paths, 2. Start creating them (e.g. README/YAML), 3. Start to auto-gen feature.textproto where the new SoT has been defined for feature paths.
On the other hand, if the longer proposal is rather to move the proto-format documentation of feature paths to a different place (metadata.textproto?), then we would still need to migrate such tooling, but I don't see a significant advantage to doing that because at the end of the day the difference is two proto files vs. one proto file.

@wenovus proposal seems reasonable, with one caveat: if feature.textproto paths are populated by merging the paths from all subtending tests (e.g. READMEs) then it's unclear whether feature.textproto can be reliable as a Feature definition; feature.textproto would only be complete if the Feature has complete path coverage by subtending tests.
I think you're correct to say that CI should verify that README paths are also in feature.textproto, and it's probably reasonable to say that missing paths should be auto-added to feature.textproto. But I would stop short of saying that feature.textproto is completely autogenerated. Rather, it should be seen as a curated list, with some human ownership.

Following up on my previous comment, and proposing details in response to this:

So I think the right steps are 1. Decide where to store the manual SoT (source-of-truth) for feature paths, 2. Start creating them (e.g. README/YAML), 3. Start to auto-gen feature.textproto where the new SoT has been defined for feature paths.

SoT for a Feature is feature.textproto and SoT for a Test is README.md

Workflow for a Test developer is to add Covered Paths to README.md
Workflow for a "Feature Maintainer" is to curate feature.textproto, ensuring it includes all paths that are required to exercise the Feature

We should agree on the YAML structure first, and then update all READMEs to move the Covered Paths (etc) to that format; structure details TBD
Rather than "auto-gen feature.textproto" I was say "auto-add Test's Covered Paths and RPCs to feature.textproto"

Hmm thanks for pointing out the caveat, I agree with your analysis. If we want to manually curate the overall list of paths within a feature so that it's independent of whether test coverage is complete, then your revised proposal and its details makes sense to me.
However, I want to see if I can challenge this: do we want to manually curate the overall list, or should it simply be the union of "intended Covered Paths" listed by all READMEs within a feature? Such that we implicitly have the following policy: "if a test is not defined, then its covered paths are not part of the featureprofile."?
Doing this means we guarantee that each featureprofile path is mapped to a test, whether proposed or implemented. It also avoids the maintenance burden of having to manually maintain the overall list of feature paths -- only the covered paths in each constituent test needs to be maintained as proposed by OP.

Thanks for your response @wenovus.
First, I would assert that we do need a single list of mandatory paths for any given Feature, so that implementations (e.g. vendors) have a clear definition of compliance. Eventually that compliance may be described as "just pass all the tests", but that would be inadequate until we know that the tests are completely covering a Feature's paths. And how do we know that a Feature has all of its paths covered by Tests? Today, feature.textproto is that definition of coverage compliance.
More specifically responding to your challenge, I would ask: what is the roadmap for Test coverage (Test development)? I think that the desired end-state is for a collection of subtending Tests to exercise all of the paths that are required to implement a Feature, but initially there are no tests...
In my view, a human-curated feature.textproto might be used as a roadmap which indicates all of the paths that MUST be implemented for a Feature and SHOULD be covered by subtending Tests. If we adopt the policy that you described ("if a test is not defined, then its covered paths are not part of the featureprofile") then would we, instead, need to have all of those paths defined in a "roadmap README" for each Feature until they are included in specific test READMEs? That seems to be effectively the same as just documenting them in the feature.textproto in the first place. 🤓

Thanks @bensons, having feature.textproto partially manually-maintained in order to record paths in the roadmap makes sense to me. Having a roadmap README to maintain would create a similar maintenance burden until the roadmap README can be deleted. I think all my questions are addressed, so I'll let the author and other reviewers chime in.

@dplore - this looks like can be merged. Any concerns with doing so?


Evaluation guide

Dear authors,
I read your paper 'Multilingual ColBERT-X' and the evaluation and test on CLEF are very impressed. But there isn't any description in README.
Could you update the detailed instructions for inference and PRF?
Thanks!

Oops, sorry for missing your issue.
We put together a tutorial on how to use the package here.
https://github.com/hltcoe/clir-tutorial with a pretty nice notebook.
Hope this would help.
And for the PRF part, we currently don't have that ability in our codebase.
But you can use the version in pyterrier: https://github.com/terrierteam/pyterrier_colbert


feat: implement error-conditions

We are using aiven-operator in an argocd-setup where we heavily rely on status conditions for synchronization and monitoring purposes. After evaulating the operator we found two major issues:

In the case of failed preconditions, actual conditions never get written to kube-api
In the case of error, no condition is ever set on kube-api level to indicate that something failed

Changes this PR introduces:

defer function was moved to a higher level in order to consistently trigger status-updates
new status conditions in the case of an error during find, create, update, delete were added
a new event was introduced sent out when preconditions are not met

This pr builds on top of some of the work done in https://github.com/aiven/aiven-operator/pull/101
I was reading the full discussion there as well as on the issue and i might not that i think it is not a good idea
to remove status conditions in the case the status resolves. I don't find this a standard practice in the whild and there
are good reasons for it. We would only hide that an error happened in the past and for everyone looking at the current
object it would still be clear that the object is healthy because we have a newer status condition then signaling that
the current state is indeed healthy.
Resolves: https://github.com/aiven/aiven-operator/issues/66

hey, @atarax! 👋
thank you for your contribution!
it looks like a major change to me, so I'd like to ask @byashimov to check it out

Hey @atarax
Thanks for the contribution.
There are known issues with the events. In particular, the RUNNING event might be lost by some reason. Moving the defer to the beginning of the function did not work for me. There must be some race or something. Though, I will carefully test you PR, I believe this is not the end. It might require deeper changes.
And if I may ask, would you use crossplane solution instead of this operator if we had one?

@byashimov thanks for the quick response! I have no issues with this version which were visible to me regarding events but i was mainly focused on the status conditions. Give it a try and if there is still a problem i can look into that. :)
Regarding crossplane-provider, i would really prefer using a provider instead of a full-fledged operator for many reasons. The most important ones are:

obviously the whole backend with resolving dependencies, management policies doesn't need to be maintained in a second place and it's of course a lot more active and matrue
ability to use crossplane compositions
current operator has a pitfall in terms of security as it needs the secret to be present in the same namespace

I think it shouldn't be that hard to create a provider on the base what you already have :)


[4.5] fix: DEBUG-VIEW comments are not output

Description
Follow-up #8053
Fix a bug that DEBUG-VIEW comments are not output.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

@michalsn Thank you for reviews!


Promise is undefined - Failing and crashing on IE 11 windows 7

Please see below snap of JS console log, IE 11 on windows 7.

thx @cfry2 .
It's tricked for me !


Urls for mirror of model zoo on Aliyun

The doc of model zoo said '
We use AWS as the main site to host our model zoo, and maintain a mirror on aliyun. You can replace https://s3.ap-northeast-2.amazonaws.com/open-mmlab with https://open-mmlab.oss-cn-beijing.aliyuncs.com in model urls.
'
However, the download url I got from model zoo looks like 'https://open-mmlab.s3.ap-northeast-2.amazonaws.com/mmdetection/v2.0/faster_rcnn/faster_rcnn_r50_fpn_1x_coco/faster_rcnn_r50_fpn_1x_coco_20200130-047c8118.pth'. There is no https://s3.ap-northeast-2.amazonaws.com/open-mmlab in the url.
So, what is the corresponding aliyun url?

Hi @fly2leoo ,
Thanks for your remind.
We have not finished mirror models from AWS to aliyun. We will let you know once the mirroring process is done.

Same question.

Same question.


Tenant delete fails with Aurora database configuration

Deleting a tenant through the UI when the application has been configured to run an Aurora database fails because the IAM role of the delete functionality does not have permissions to create a snapshot prior to removing the database instance/cluster.
Reproduction Steps

Configure SaaS Boost to use an Aurora database of either type
Onboard a tenant
Delete the tenant from the tenant detail page

What did you expect to happen?
Tenant removed and onboarding CloudFormation stacks deleted without error.
What actually happened?
The tenant RDS nested CloudFormation stack fails to delete because the Onboarding Service IAM role does not have permission to execute rds:CreateDBClusterSnapshot
Environment

AWS Region  :
AWS SaaS Boost Version :
Workload OS  (Linux or Windows) :

Other

This is :bug: Bug Report

Fixed with b6b170431599c73370bbd6f7a884d81ccd94ff6f
Sorry Hari - didn't see your commit here -- also need rds:DescribeDBClusterSnapshots


Updates, Removals, Config 10/10

^ Archex, Drogtor, Ears, EBE, Pehkui, Starlight, Visible Barriers, Yttr [No iris update - smunnel incompat]
^ Beamforming (Adventure perms), pridestrips (QMJ), Succ (Adventure perms), Yardwork (QMJ)
- MoreCulling (caused issues with modded blocks, and config doesn't work)
% Disable EBE for signs (for picturesign). Disable Iris update message.

note: no actual updates for ears, archex, EBE, starlight, visible barriers - just a URL change.


Ch-1 Subtitle Updates

Updated the first five text files.  Pay special attention to 5.txt since I modified the timestamp for one of the subtitles to start.

Thanks so much @theangellmethod These are the kinds of changes I was looking for. Feel free to batch up the PRs to do a chapter at a time if that's easier.


Test with tox and travis

Use tox to run tests for multiple Python versions
Enable automated testing via Travis-CI
Update setup.py to reflect all supported Python versions

@seme0021 Yes, I can merge these. Can you enable tests for this project on travis-ci.org before I do so? Only project owners can enable integrations.


cannot create patch

Steps to reproduce:

I clone heartwood.
I create a new branch.
I create a new commit on the branch.
I push the branch to the rad remote.
I press the + to create a new patch.

I get:
Radicle CLI Error:

There was an error while fetching information for commits contained in the patch proposal. Unable to create timeline

this is on 0.9.2 version of the plugin, with rc9

We've spotted the problem in a debugging section with @JChrist .
I can work around the problem by first git fetching, before trying to create the patch.


hydrus: 591 -> 592

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for hydrus is: Danbooru-like image tagging and searching system for the desktop
meta.homepage for hydrus is: https://hydrusnetwork.github.io/hydrus/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 592 with grep in /nix/store/csps3kwxzvaz6mr57zm93q4mjryax1fz-python3.12-hydrus-592
found 592 in filename of file in /nix/store/csps3kwxzvaz6mr57zm93q4mjryax1fz-python3.12-hydrus-592

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

hydrus

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/csps3kwxzvaz6mr57zm93q4mjryax1fz-python3.12-hydrus-592 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A hydrus https://github.com/r-ryantm/nixpkgs/archive/7269a16533513a2db3906c12fcff85cca73d525d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7269a16533513a2db3906c12fcff85cca73d525d#hydrus

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/csps3kwxzvaz6mr57zm93q4mjryax1fz-python3.12-hydrus-592
ls -la /nix/store/csps3kwxzvaz6mr57zm93q4mjryax1fz-python3.12-hydrus-592/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

hydrus
hydrus.doc

Maintainer pings
cc @dali99 @evanjs for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Merge conflict, please open a new PR.


Cannot find module 'react-native-keyboard-aware-scroll-view' or its corresponding type declarations.

Inside file "index.d.ts" import of import { KeyboardAwareScrollViewProps } from "react-native-keyboard-aware-scroll-view";
dependency typescript throw error Cannot find module 'react-native-keyboard-aware-scroll-view' or its corresponding type declarations.ts(2307)
When i try to change it to 	import { KeyboardAwareScrollViewProps } from "@codler/react-native-keyboard-aware-scroll-view"; everything seems like ok

October 2021 stiil have the same issue !!!
How do you fixed this issue?


pip error when installing

I'm getting an error during pip install:
urllib.error.URLError: <urlopen error [Errno 8] nodename nor servname provided, or not known>
I'd appreciate the help! :)
console output:
(openl3_venv) hugoffg is at openl3: >:-)  pip3 install openl3
Collecting openl3
  Using cached openl3-0.3.1.tar.gz (16 kB)
    ERROR: Command errored out with exit status 1:
     command: /Users/hugoffg/Documents/notebooks/openl3_venv/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/vl/n_1wx0vx41s979274z7hctnr0000gn/T/pip-install-bg57tw39/openl3/setup.py'"'"'; __file__='"'"'/private/var/folders/vl/n_1wx0vx41s979274z7hctnr0000gn/T/pip-install-bg57tw39/openl3/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /private/var/folders/vl/n_1wx0vx41s979274z7hctnr0000gn/T/pip-pip-egg-info-jle_emrm
         cwd: /private/var/folders/vl/n_1wx0vx41s979274z7hctnr0000gn/T/pip-install-bg57tw39/openl3/
    Complete output (55 lines):
    Downloading weight file openl3_audio_linear_music-v0_2_0.h5.gz ...
    Traceback (most recent call last):
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1317, in do_open
        encode_chunked=req.has_header('Transfer-encoding'))
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1252, in request
        self._send_request(method, url, body, headers, encode_chunked)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1298, in _send_request
        self.endheaders(body, encode_chunked=encode_chunked)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1247, in endheaders
        self._send_output(message_body, encode_chunked=encode_chunked)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1026, in _send_output
        self.send(msg)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 966, in send
        self.connect()
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1414, in connect
        super().connect()
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 938, in connect
        (self.host,self.port), self.timeout, self.source_address)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/socket.py", line 707, in create_connection
        for res in getaddrinfo(host, port, 0, SOCK_STREAM):
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/socket.py", line 748, in getaddrinfo
        for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
    socket.gaierror: [Errno 8] nodename nor servname provided, or not known

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/vl/n_1wx0vx41s979274z7hctnr0000gn/T/pip-install-bg57tw39/openl3/setup.py", line 35, in <module>
        urlretrieve(base_url + compressed_file, compressed_path)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 247, in urlretrieve
        with contextlib.closing(urlopen(url, data)) as fp:
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 222, in urlopen
        return opener.open(url, data, timeout)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 531, in open
        response = meth(req, response)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 641, in http_response
        'http', request, response, code, msg, hdrs)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 563, in error
        result = self._call_chain(*args)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
        result = func(*args)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 755, in http_error_302
        return self.parent.open(new, timeout=req.timeout)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 525, in open
        response = self._open(req, data)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 543, in _open
        '_open', req)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
        result = func(*args)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1360, in https_open
        context=self._context, check_hostname=self._check_hostname)
      File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1319, in do_open
        raise URLError(err)
    urllib.error.URLError: <urlopen error [Errno 8] nodename nor servname provided, or not known>
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

Do you solve this issue?

I just tested pip install openl3 (on macOS 10.14.6) and it worked fine for me, so the issue isn't with openl3, at least not on macOS.
Looking at the logs it appears there's some issue with downloading a model file. I'm not sure if this could be caused due to networking issues, or some other problem. Please try installing on a different network to confirm.
Also please report operating system version and python version, otherwise it's very hard to provide help.
You may also want to try installing into a conda environment over a venv.

win10 python3.6, the same error,can you help me？Thanks.

the same error
problem:
https://github.com/marl/openl3/raws
404
can you open this website?


Messenger: update meta data on PATCH db/frame

Description
The PATCH db/frame command is updating the meta data on the local node, but those changes aren't being propagated to other nodes in the cluster. Currently we only have CreateDB and CreateFrame message types, but we should probably introduce something like UpdateDBMessage.
Note: this work is currently only on the pilosa/messenger branch, so this issue can be iceboxed at least until that branch gets merged to master.
Success criteria (What criteria will consider this ticket closeable?)
PATCHing a frame's TimeQuantum on one node is recognized by all nodes in the cluster.

made unnecessary by #1218


Started to get ORA-27103: internal error consistently with latest-faststart

Started to get ORA-27103: internal error consistently with latest-faststart since this Monday (Dec 9th) morning. Things were still running smoothly last Friday. Noticed a new version was published over the weekend on Docker Hub. Did some regression slip in?
Got things working with 23.5-faststart for now.
Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for log output matching '.*DATABASE IS READY TO USE!.*\s'
	at org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)
	at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
	at org.testcontainers.oracle.OracleContainer.waitUntilContainerStarted(OracleContainer.java:81)
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:490)
	... 91 common frames omitted
09:19:12.089 [Test worker] ERROR tc.gvenzl/oracle-free:latest-faststart -- Log output from the failed container:
CONTAINER: starting up...
CONTAINER: first database startup, initializing...
CONTAINER: starting up Oracle Database...

LSNRCTL for Linux: Version <IP_ADDRESS>.0 - for Oracle Cloud and Engineered Systems on 09-DEC-2024 09:09:12

Copyright (c) 1991, 2024, Oracle.  All rights reserved.

Starting /opt/oracle/product/23ai/dbhomeFree/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version <IP_ADDRESS>.0 - for Oracle Cloud and Engineered Systems
System parameter file is /opt/oracle/product/23ai/dbhomeFree/network/admin/listener.ora
Log messages written to /opt/oracle/diag/tnslsnr/81aa229c35db/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC_FOR_FREE)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_FREE)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version <IP_ADDRESS>.0 - for Oracle Cloud and Engineered Systems
Start Date                09-DEC-2024 09:09:12
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Default Service           FREE
Listener Parameter File   /opt/oracle/product/23ai/dbhomeFree/network/admin/listener.ora
Listener Log File         /opt/oracle/diag/tnslsnr/81aa229c35db/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC_FOR_FREE)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))
The listener supports no services
The command completed successfully
ORA-27103: internal error
Additional information: 16878
Additional information: 1

I'm sorry to hear that and apologize for the inconvenience!
The error shown occurs during database startup and is generated by the database itself.
Could you please provide the output from docker exec <container name> cat /opt/oracle/diag/rdbms/*/*/trace/alert*log and upload it here?

File: /opt/oracle/diag/rdbms/*/*/trace/alert*log
[oracle@37a841c0123b ~]$ cat /opt/oracle/diag/rdbms/*/*/trace/alert*log
2024-12-11T12:39:36.960155+00:00
Adjusting the default value of parameter "parallel_max_servers" from 0 to 1.
Starting ORACLE instance (normal) (OS id: 73)
2024-12-11T12:39:36.973203+00:00
****************************************************
 Sys-V shared memory will be used for creating SGA
 ****************************************************
2024-12-11T12:39:36.974441+00:00
**********************************************************************
2024-12-11T12:39:36.974529+00:00
Dump of system resources acquired for SHARED GLOBAL AREA (SGA)

2024-12-11T12:39:36.974689+00:00
 Domain name: docker/37a841c0123b49c58af7fc4151a9d72eebe8c5d96a7fa8bd939d12046f2ea716
2024-12-11T12:39:36.974786+00:00
 Per process system memlock (soft) limit = 64K
2024-12-11T12:39:36.974871+00:00
 Expected per process system memlock (soft) limit to lock
 instance MAX SHARED GLOBAL AREA (SGA) into memory: 1532M
2024-12-11T12:39:36.975036+00:00
 Available system pagesizes:
  4K, 2048K
2024-12-11T12:39:36.975205+00:00
 Supported system pagesize(s):
2024-12-11T12:39:36.975288+00:00
  PAGESIZE  AVAILABLE_PAGES  EXPECTED_PAGES  ALLOCATED_PAGES  ERROR(s)
2024-12-11T12:39:36.975372+00:00
        4K       Configured               5           391555        NONE
2024-12-11T12:39:36.975507+00:00
     2048K                0             766                0        NONE
2024-12-11T12:39:36.975611+00:00
RECOMMENDATION:
2024-12-11T12:39:36.975700+00:00
 1. For optimal performance, configure system with expected number
 of pages for every supported system pagesize prior to the next
 instance restart operation.
2024-12-11T12:39:36.975952+00:00
 2. Increase per process memlock (soft) limit to at least 1532MB
 to lock 100% of SHARED GLOBAL AREA (SGA) pages into physical memory
2024-12-11T12:39:36.976113+00:00
**********************************************************************
Using an SGA granule size of 16MB
Memory protection keys enabled.
Hugetlbfs Dynamic SGA NOT enabled.
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Using LOG_ARCHIVE_DEST_1 parameter default value as /opt/oracle/product/23ai/dbhomeFree/dbs/arch
.... (PID:): Enable RFS client   [kcrlc.c:609]
Memory protection keys enabled on shared strand buffers
Autotune of undo retention is turned on.
Log buffer boundaries=(0xc0000000, 0xc0452000)
IMODE=BR
ILAT =35
NOTE: Using default ASM root directory ASM
Oracle Database 23ai Free Release <IP_ADDRESS>.0 - Develop, Learn, and Run for Free
Version <IP_ADDRESS>.10.
ORACLE_HOME:    /opt/oracle/product/23ai/dbhomeFree
System name:	Linux
Node name:	37a841c0123b
Release:	5.4.17-2136.327.2.el7uek.x86_64
Version:	#2 SMP Fri Jan 5 14:53:41 PST 2024
Machine:	x86_64
VM name:	KVM CPUID feature flags: 0x01003afb
Using parameter settings in server-side spfile /opt/oracle/product/23ai/dbhomeFree/dbs/spfileFREE.ora
System parameters with non-default values:
  processes                = 200
  cpu_count                = "2"
  nls_language             = "AMERICAN"
  nls_territory            = "AMERICA"
  sga_target               = 1536M
  control_files            = "/opt/oracle/oradata/FREE/control01.ctl"
  control_files            = "/opt/oracle/oradata/FREE/control02.ctl"
  db_block_size            = 8192
  compatible               = "23.6.0"
  _instance_recovery_bloom_filter_size= 1048576
  undo_tablespace          = "UNDOTBS1"
  fast_start_parallel_rollback= "FALSE"
  remote_login_passwordfile= "EXCLUSIVE"
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=FREEXDB)"
  shared_servers           = 0
  local_listener           = ""
  job_queue_processes      = 1
  db_name                  = "FREE"
  open_cursors             = 300
  pga_aggregate_target     = 512M
  _dmm_blas_library        = "libora_netlib.so"
  control_management_pack_access= "DIAGNOSTIC+TUNING"
  spatial_vector_acceleration= FALSE
  diagnostic_dest          = "/opt/oracle"
  enable_pluggable_database= TRUE
  common_user_prefix       = ""
  mle_prog_languages       = "OFF"
2024-12-11T12:39:37.145967+00:00
Errors in file /opt/oracle/diag/rdbms/free/FREE/trace/FREE_ora_73.trc:
ORA-27180: failed to create memory protection key
Linux-x86_64 Error: 1: Operation not permitted
Additional information: 16720

File: opt/oracle/diag/rdbms/free/FREE/trace/FREE_ora_73.trc
[oracle@37a841c0123b ~]$ cat /opt/oracle/diag/rdbms/free/FREE/trace/FREE_ora_73.trc
Trace file /opt/oracle/diag/rdbms/free/FREE/trace/FREE_ora_73.trc
Oracle Database 23ai Free Release <IP_ADDRESS>.0 - Develop, Learn, and Run for Free
Version <IP_ADDRESS>.10
Build label:    RDBMS_<IP_ADDRESS>.10DBRU_LINUX.X64_241017.LA
ORACLE_HOME:    /opt/oracle/product/23ai/dbhomeFree
System name:	Linux
Node name:	37a841c0123b
Release:	5.4.17-2136.327.2.el7uek.x86_64
Version:	#2 SMP Fri Jan 5 14:53:41 PST 2024
Machine:	x86_64
Storage:	?
CLID:	U
Instance name: FREE
Instance number: 0 <none>
Database name: N/A
Database unique name: N/A
Database id: N/A
Redo thread mounted by this instance: 0 <none>
Oracle process number: 0
Unix process pid: 73, NID:<PHONE_NUMBER>, image:

*** 2024-12-11T12:39:36.960201+00:00
SGA (id: 1) creation time at startup: 3 ms
I:2024-12-11 12:39:36.985 : [    GPNP][    GPNP]  clsgpnp_Init init failed. Error: CLSGPNP_ERR (1) .
I:2024-12-11 12:39:36.988 : [ CLSINET][ CLSINET]  Failed to initialize clsgpnp context grv 1
I:2024-12-11 12:39:36.989 : [    GPNP][    GPNP]  clsgpnp_Init init failed. Error: CLSGPNP_ERR (1) .
I:2024-12-11 12:39:36.990 : [ CLSINET][ CLSINET]  Failed to initialize clsgpnp context grv 1
Lockdown sysfs /sys/kernel/security/lockdown doesn't exist. Set to default KSCXCAPTYPEKERNELSEC_NONE
KSIPC: KSIPC SERVICE ENV 0x0
KSIPC SERVICE MASK MGAON:[INETOFF]:[IPCLWON]:[GRPAM]:[PRON]:[TOPOON]:[DLLON]:[KSGLOFF][RSTFWOFF]:[RDMAPINGON]:[SHREGON]:MEMCBON:[STATSFWON]:[SNOFF]:[DGOFF]:[ORDNFY]:[RDSTCPBSON][SHREGODPON]:[SIGSAFEON]:[THRPOOLON]:[VNICOFF]
KSNMON: Initial Config: enable=0x7fffffff, maxflow=65535, minstsint=5000
KSNMON: Runtime Config: service enabled=0x3ff
kcrlnfy: Enable RFS client   [kcrlc.c:609]
kcrfwy: minimum sleep (disk) is 1058 usecs (overhead is 58 usecs)
init table done
Running with 1 strand for Non-Enterprise Edition
Running without dynamic strands for Non-Enterprise Edition
NOTE: Cluster configuration type = NONE [2]
sskgm_mpkey_create failed: 1
kcrfw_mpkey_init: Failed to initialize memory protection key
ORA-27180: failed to create memory protection key
Linux-x86_64 Error: 1: Operation not permitted
Additional information: 16720
<error barrier> at 0x7ffe3628a0b0 placed kcrfw.c@39186
sskgm_mpkey_set_prot invalid key:0
Protecting shared strand buffer via memory protection key failed
KJHA:2phase 010 opi_error:27103

Thank you, @europ!
As you have probably already deduced yourself, this is a regression in Oracle Database Free itself. I have contacted Oracle Development for further help with this - stay tuned!

Hey @europ, hey @ipsips,
I spoke with Oracle Database Development and they have informed me that the memory protection key kernel feature can be disabled with the underscore parameter "_enable_memory_protection_keys"=FALSE.
Not yet knowing exactly what causes the failure in some environments (the 23.6 containers build and run successfully in my x86_64 and aarch64 environments), I have rolled out this parameter change across all 23.6 images and re-uploaded them.
You should be able to use them now, please do let me know whether that is the case.

I just spotted a bug that this parameter still doesn't get set for the full image. Fixing that now.

All fixed and uploaded

Hey @europ,
Great, I'm glad to hear it!
Thanks again for using these images and Happy Holidays!


Start doing things!!

I added future imports, because I think we should use Python 3.x.  I forgot to branch, oops.

Yes that is a good idea. Have you thought about design an more? We should have another meeting ASAP. @stevertaylor will be out of town next week, maybe we can chat tomorrow?


Attempt to invoke virtual method 'java.util.List android.bluetooth.BluetoothGattService.getCharacteristics()

I'm trying to follow this tutorial -  https://www.snip2code.com/Snippet/667137/Cordova-BLE-Notify-Test-using-bleno-s-Te
So my confirguration is as follows :
IONIC2 / BLE lib  for the frontend and
PI Zero W / NodeJS 6.10.3 / NPM 3.10.10
On PI I manage to get the test.js up and running and I can connect with the IONIC 2 app to it.
On my IONIC2 after connection, I receive this from PI on my console :
Object
  advertising: ArrayBuffer
  characteristics: Array[3]
   0: Object
        characteristic: "2a00"
        properties: Array[1]
           0: "Read"
           length: 1
           __proto__: Array[0]
        service:"1800"
        __proto__ : Object
   1: Object
        characteristic: "2a01"
        properties: Array[1]
           0: "Read"
           length: 1
           __proto__: Array[0]
        service: "1800"
        __proto__: Object
   2: Object
       characteristic: "34cd"
       properties: Array[2]
           0: "Read"
           1: "Write"
            length: 2
            __proto__: Array[0]
        service: "12ab"
        __proto__:Object
   length: 3
  id: "B8:27:EB:9C:36:E1"
  name:"raspberrypi"
  rssi:-61
  services: Array[3]
   0: "1800"
   1: "1801"
   2: "12ab"

In your tutorial you say we must interogate ffffffff-ffff-ffff-ffff-fffffffffff5 characteristic ... so on my code i have :
this.ble.startNotification(this.device.id, 'ffffffff-ffff-ffff-ffff-fffffffffff0','ffffffff-ffff-ffff-ffff-fffffffffff5').subscribe(
      dataOK => {
        var data = new Uint32Array(dataOK);
        console.log(data);
      },
      dataKO => {
        console.log(dataKO);
      }
    );

On console I get this error : Attempt to invoke virtual method 'java.util.List android.bluetooth.BluetoothGattService.getCharacteristics()' on a null object reference , which is kind of normal since I see only 1800,1801, 12ab services.
In the test.js file I see clearly fffffffffffffffffffffffffffffff0 and fffffffffffffffffffffffffffffff5 but when I run the code i get what i described above.

Couldn't let this error like that so I downloaded BLE Scanner on my android, discovered quickly my PI's ble connection and after connection, got for the first time same 3 services as my IONIC2 app.
Fortunatelly I've unpaired my test device and connected again, and voila ... this time I get the good characteristics : ffffffff-ffff-ffff-ffff-fffffffffff1, ffffffff-ffff-ffff-ffff-fffffffffff2 ... ffffffff-ffff-ffff-ffff-fffffffffff6
I subscribe on ffffffff-ffff-ffff-ffff-fffffffffff5 characteristic and by magic my nodejs app comes alive and starts incrementing each 5 seconds ... great news. So now I have to replicate this on my IONIC2 app. I now i connect successfully with test.js, also I know the nodejs does well its incrementing so i'm on the good path.
I have some questions though :

at this moment test.js accepts connections and sends notifications from/to any client. Is there a way to connect / send connection only to my IONIC2 app ? How can I implement that and where ?

for the moment test.js sends only an integer value corresponding to a incremention. Can I send a file to my app ?

@arizona2014

at this moment test.js accepts connections and sends notifications from/to any client. Is there a way to connect / send connection only to my IONIC2 app ? How can I implement that and where ?

Nope

or the moment test.js sends only an integer value corresponding to a incremention. Can I send a file to my app ?

You can only send up to a maxValueSize byte per notification.


Show the description of the reported disease in the map.

Currently, the user can add a description before submitting the map location. The description is saved in the DB.
We need to show that description with the marker in the map. Better if the description is visible only when we hover the marker in the map.

hi @ravinduramesh I want to work on this issue,kindly assign me.


Update README-zh.md

错别字
Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

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

LGTM


Add the student database management system by Parmesh Bhatt

Student Database management system is a beginner-level project. In this project, students can add tasks, modify them and also delete it.
This is the project that is made to deliver and students can learn the OOPs concepts and about C++ and expand their knowledge.
I am working on this issue.

Do not raise a PR without getting it assigned to you


fix #252 : EventEmitter memory leak

Set defaultMaxListeners to infinity. May be risky?

Set defaultMaxListeners to infinity. May be risky?

Yes I think it's not how we want to solve that as this warning is useful, it's just that the default value doesn't fit for AresRPG and we are not really able to have a good default.
Thinking at it we have two big event listeners where we need to fix that:

The mob event listener, one event is added for each player that sees the mob + a fixed number of listeners. As this was causing some spam since the warning was printed for each mob before it was set to Infinity. But we might be able to remove it today, as before it was not for "each player that sees the mob" but for "each player" so adding a lot of event listeners.
The player event listener, one event is added for each "observer" and it should not move much

The solutions that I see for those two are:

For the mob event listener, we could set the limit dynamically based on the number of players that sees the mob. We can implement that by increasing and decreasing the limit when a player sees the mob
For the player event listener I think we could set it to Infinity, let the "observe" functions register their event listeners and after some time/ticks reset the limit to the current number of listeners + a fixed number (to allow for some space, 10 seems right)


defineProps - Error If a const is declared before

Describe the bug
If I declare a constant before defineProps an error is thrown:
const msg = 'Hello';
withDefaults(defineProps<HelloWorldProps>(), {
  msg,
});

Error: [@vue/compiler-sfc] type argument passed to defineProps() must be a literal type, or a reference to an interface or literal type.

Reproduction
https://stackblitz.com/edit/vitejs-vite-bcwnrm?file=src/components/HelloWorld.vue
System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
    Memory: 6.23 GB / 31.87 GB
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.16.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (108.0.1462.76)
    Internet Explorer: 11.0.19041.1566

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

I noticed I get this error simply adding const msg = 'Hello'; before or after defineProps
withDefaults(defineProps<HelloWorldProps>(), {
  msg: 'Hello',
});
const msg = 'Hello';


Undefining a function should remove associated symbol

I have a bndb with some code I'm trying to understand. As part of this process, I'm moving a function boundary between two chunks of code. For example, if I have:
0x1000: func_a
...
0x2000: func_b

If I want to move func_b to start at 0x1800, my workflow is to create a new function at 0x1800, undefine func_b, then rename sub_1800 to func_b. This mostly works, except it sometimes leaves the old symbol for func_b, (especially if I've modified the argument list/type?) in my bv.symbols. If I'm moving function boundaries around a lot, these can build up and be annoying.
As a workaround, they can be manually deleted with bv.undefine_user_symbol(bv.symbols['sym_name']), but they should probably be deleted automatically with function undefine?

I've implemented this as a change to both API and core, as well as UI (with a setting to toggle it, defaulting to off).
For now, I'm leaving it on a test branch test_remove_user_symbols_with_functions, and I'll submit a PR for it.
Since it affects the C API, it needs further review.

We decided to reject the PR on this for the API because we didn't want to complicate things. But, we still feel this is important to do through the UI, so we're keeping this ticket open to track that.