The efficiency of dr.elephant  analyse jobs

    Hello, I use dr.elephant  to analyse mapreduce jobs ,But it works too slow ,What should I do to solve thsi proplem. Thank you

Hi @huyt1 , have you try another fetcher - MapReduceFSFetcherHadoop2 ?

@huyt1, please try the MapReduceFSFetcherHadoop2 and let us know if it solves your problem.

sorry,    I've been busy these days. The configuration like this

mapreduce
com.linkedin.drelephant.mapreduce.fetchers.MapReduceFSFetcherHadoop2

<sampling_enabled>false</sampling_enabled>
<history_log_size_limit_in_mb>500</history_log_size_limit_in_mb>

-->

spark
org.apache.spark.deploy.history.SparkFSFetcher
<!--

<event_log_size_limit_in_mb>100</event_log_size_limit_in_mb>
<event_log_dir>/system/spark-history</event_log_dir>
<spark_log_ext>_1.snappy</spark_log_ext>
  #the values specified in namenode_addresses will be used for obtaining spark logs. The cluster configuration will be ignored.
  <namenode_addresses>address1,address2</namenode_addresses>
</params>
-->

I have two cluster one cluster have runned about 300000 jobs another about 70000,The efficiency of dr.elephant analyse jobs in the big cluster is very slow just 7-8 hundred a day .  Contrary  the smaller one can analyse  4000 jobs.  is there any  connection with the cluster configuration or mysql configuration

I think Fetcher is the bottleneck in your case. Dr Elephant tries to fetch all the jobs since time=1, and in your case, I guess there are 300,000 jobs since time = 1. You can either reduce the backlog or speed up the fetcher or both.
To reduce the backlog, you can use the option described in this PR. You can configure how much older applications you want Dr Elephant to fetch.
To speed up the fetcher, you can enable sampling for the MapReduce fetcher. When sampling is enabled, then fetcher will only fetch data for maximum 200 tasks (mappers or reducers) for each MapReduce job. This can significantly increase speed up the fetcher, however, sampling only 200 tasks may produce slightly inaccurate heuristic results.

Hi, @huyt1
Please try to use the following configs In FetcherConf.xml:
  <fetcher>
    <applicationtype>mapreduce</applicationtype>
    <classname>com.linkedin.drelephant.mapreduce.fetchers.MapReduceFSFetcherHadoop2</classname>
    <params>
      <sampling_enabled>false</sampling_enabled>
      <history_log_size_limit_in_mb>500</history_log_size_limit_in_mb>
      <history_server_time_zone>PST</history_server_time_zone>
    </params>
  </fetcher>

We use this fetcher in production environment. It works pretty well.
Make sure the history_server_time_zone is the timezone of your job history server.
Let us know if you has any issues.


[Generic Response Expose Metrics]: token statistics

right now, doing awkwardly in frontend trying different formats, this is fine for now functionally (non breaking), but would ideally need to expose this as a separate field in GenericResponse
      case "total_tokens":
        return item.raw_response.usage?.total_tokens || item.raw_response.response?.body?.usage?.total_tokens || 0;
      case "prompt_tokens":
        return item.raw_response.usage?.prompt_tokens || item.raw_response.response?.body?.usage?.prompt_tokens || 0;
      case "completion_tokens":
        return item.raw_response.usage?.completion_tokens || item.raw_response.response?.body?.usage?.completion_tokens || 0;


Skip documentation build if no docs where changed

What should be done?
We can speed up CI runs if we will skip the documentation build if no documentation files were changed.
How?
It can be done by creating another workflow and job with the same names; see
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks

The solution proposed by GitHub is bad and does not really work with a way we skip and require checks. And the issues itself is not really a problem; Vercel is.

To expand on that: if PR is sent that changes both code and documentation, both workflows will run; the empty one will succeed first and hide potential errors in the other one.


Clarify that verify script doesn't cover Terraform

@richeney : Thanks for your contribution! The author, @yijenj, has been notified to review your proposed change.

@qianw211, as a previous contributor to this article, are you able to approve this PR? I'm unable to reach the author. Thanks.

#sign-off Changes are correct!  Approved!

@qianw211: I'm sorry - only the author of this article, @yijenj, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off yijenj is no long with this team...

@qianw211: I'm sorry - only the author of this article, @yijenj, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Query PI Points Directly

I have been thinking about extending the plugin to allow the capability to query PI Points directly without the need for building an Asset Framework. I don’t know if “Issues” is the best place to submit this “question” or request; but I thought I would ask before beginning my work if this feature existed already but I simply have not been able to figure out how to make it work. If that was the case I would just submit a PR for doc improvement and call it a day.
Again, apologies if this already exists and I’m too ignorant to figure it out.

hi @cluffja. try looking at https://techsupport.osisoft.com/Documentation/PI-Web-API/help/controllers/point.html

hi @cluffja. try looking at https://techsupport.osisoft.com/Documentation/PI-Web-API/help/controllers/point.html

Yeah, I was looking at that. I think I just found what I needed. The piece of code seems to be in the QueryCtrl in the getSegmentPathUpTo function. I think this will work. Seems our server is limiting connection directly to the PI Dataserver. I’m going to close this issue for now. Thanks @coderReview  for trying to help. Once I get this working I’ll submit a PR to help improve the docs for this.

Yeah, I was looking at that. I think I just found what I needed. The piece of code seems to be in the QueryCtrl in the getSegmentPathUpTo function. I think this will work. Seems our server is limiting connection directly to the PI Dataserver. I’m going to close this issue for now. Thanks @coderReview  for trying to help. Once I get this working I’ll submit a PR to help improve the docs for this.

Hi @coderReview, I think I may have found the issue here. The only code to distinguish between a query to the asset server and the data server is this section found in the getWebId() method found in datasource.js:
 var isAf = target.target.indexOf('\\') >= 0
The problem I find is that there is no distinguishing way in the GUI to enter in a dataserver request without the query auto appending \\ to the call. Leaving the element field blank returns

So unless I'm missing something we need to add a means to either prohibit this, improve the detection for the isAf variable, or make a deeper change to allow searching the dataserver.
It's possible that the code does allow for this and I still haven't found it. In that case it's hidden in some completely non-intuitive method. Thoughts?

Hi @coderReview, I think I may have found the issue here. The only code to distinguish between a query to the asset server and the data server is this section found in the getWebId() method found in datasource.js:
 var isAf = target.target.indexOf('\\') >= 0
The problem I find is that there is no distinguishing way in the GUI to enter in a dataserver request without the query auto appending \\ to the call. Leaving the element field blank returns

So unless I'm missing something we need to add a means to either prohibit this, improve the detection for the isAf variable, or make a deeper change to allow searching the dataserver.
It's possible that the code does allow for this and I still haven't found it. In that case it's hidden in some completely non-intuitive method. Thoughts?

@cluffja can you try to explain what data are you trying to fetch?

@cluffja can you try to explain what data are you trying to fetch?

Sure thing! Sorry I'm not more clear.
So using the osisoftpi-grafana plugin in Grafana requires the creation of an Asset Framework within PI in order to query data. Basically you build your query using the Element field in the plugin to select the "path" in the AF until you find the specific attribute you would like to trend.
We would like to be able to query data directly from the PI Point without the need to build the Asset Framework with attributes that map to the PI Points. So for instance say I have a PI Point in my Data Server called equipment_speed and my Data Server is simply called myBusinessDataServer. The actual PI Point in the Data Server would look like this:
\\myBusinessDataServer\equipment_speed
I'd like to be able to enter \\myBusinessDataServer\equipment_speed in Grafana and trend data directly without the need to build the AF. Does that make more sense?
It seems like the plugin quite nearly has this capability but turns itself off at some point.

Sure thing! Sorry I'm not more clear.
So using the osisoftpi-grafana plugin in Grafana requires the creation of an Asset Framework within PI in order to query data. Basically you build your query using the Element field in the plugin to select the "path" in the AF until you find the specific attribute you would like to trend.
We would like to be able to query data directly from the PI Point without the need to build the Asset Framework with attributes that map to the PI Points. So for instance say I have a PI Point in my Data Server called equipment_speed and my Data Server is simply called myBusinessDataServer. The actual PI Point in the Data Server would look like this:
\\myBusinessDataServer\equipment_speed
I'd like to be able to enter \\myBusinessDataServer\equipment_speed in Grafana and trend data directly without the need to build the AF. Does that make more sense?
It seems like the plugin quite nearly has this capability but turns itself off at some point.

got it.

got it.

Just added a pull request that hopefully resolves this issue

I just found a bug where if you exit out of the panel and then come back in it drops the query. I need to debug that before we merge this.

hi @cluffja. thanks. Will check also,

@coderReview , I just pushed a correction to the PR that should resolve the bug I was seeing.

Definitely need this too.  Anyone ready to merge it?

hi @txjmb I will look later this month

Thank you.  In the meantime, I'll just use the PR.

Any progress on this?

Hi I am just going merge this for now :-)

Can the pull request be adjusted? It cannot currently be merged.
Thanks!
Ritchie

It looks like this was commited here:  https://github.com/GridProtectionAlliance/osisoftpi-grafana/commit/42a420e1d592ed326ab8a65ac0426c3ab8d74d68 , is that correct?  Can we close this request?

Closed by #62


Add bmp280 sensor support

The BME280 has been harder for some people to get. Some have
also bought the BMP280 in error, so this commit aims to add
support and help them along.
Signed-off-by: Alex Ellis (OpenFaaS Ltd<EMAIL_ADDRESS>

LGTM.
Sensor is one of those words that when you see it too many times it starts to look foreign

Tested by @agcraggs - thank you 👍


⚠ Bofrost.de has degraded performance

In 9a84e66, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1995 ms

Resolved: Bofrost.de performance has improved in 6fae4f1.


Fix #563 (OP)

Hey Gaetan, good to see you again! This makes the comment situation a bit better. Personally I don't think these comments look great in between the expr and the semicolon though. Could we consider moving them behind the statement? For example:
let x = some_expr() /* comment */;

would become
let x = some_expr(); // comment

@cassiersg Can you make the commit message more descriptive? It should be able to stand alone as an explanation of why the changes were made without refering to the issue tracker.

@cassiersg Can you make the commit message more descriptive? It should be able to stand alone as an explanation of why the changes were made without refering to the issue tracker.

@cassiersg, @marcusklaas should we land this PR as is or wait for something better?

There is no longer inerest (I think) to land this as-is, since it doesn't change the output of rustfmt (the comment doesn't disappear anymore due to another PR already merged).
I think we can leave the formatting as it is now (ie comments just before ; does not disappear but are not "well" formatted either. (I feel this is a very rare case.)


[Bug] Compilation errors appearing for me, whereas for other users it doesn't even if we check out to the same branch

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When I open dbt cloud, I DAG functionality for specific model doesn't work, as Compilation error is displayed. Other users can check out to the same branch and don't have the error.
The problem exists regardless of the branch, I can check out to the master, have everything up to date, and still see the compilation error.
Yesterday it was working,  there was no compilation error.
My dbt:

Another user's:

Expected Behavior
Lack of compilation error, DAG diagram is displayed.
Steps To Reproduce
No response
Relevant log output
No response
Environment
- OS:
- Python:
- dbt: 0.21.0

What database are you using dbt with?
postgres
Additional Context
No response

@AgnieszkaDul Sorry for the delayed response here!
For issues like this one, it's best to write into the Support channel in dbt Cloud. They'll be able to give you much more timely assistance, and dig into what might be causing the Compilation Error you mention. I hope you were able to get this resolved in the meantime!


Latest release doesn't work on UglifyJs

Summary:
You've released a new version of react-modal a couple of hours ago.
As you can see here, you forgot a 'function' keyword for non ES6 class component, and UglifyJs doesn't like this a single bit...
(see definition of removePortal with missing function compared to reset of the functions there).
Steps to reproduce:

Try to uglifyjs this project.

Expected behavior:
For UglifyJs to succeed. It now doesn't.
Additional notes:
Thanks!!!

And this  too.

Can you please fix this ASAP? This is breaking tones of our builds unfortunately. Can you provide ETA and let me know please? Thank you!
CC: @diasbruno @claydiffrient

Backporting problems.
It happens sometimes.  :)

@diasbruno Do we have a high level ETA on this branch going out?

having the same issue as we use react-bootstrap-table which has react-modal as a dependancy. Have had to manually add react-modal and hardcode the version to 1.6.5 to get the build to work.

v1.7.1 was released.

v1.7.1 fixed the problem

Going ahead and closing this since 1.7.1 has been reported to have indeed fixed the problem.


chore: simplify html code

I found that there were some redundancies with the html code. I've tried to simplify it a bit, but please review the changes I made because I don't know if what you have done before is intentional (for more readability).

I don't know if what you have done before is intentional (for more readability).

Nope, I'm just not familiar with html api 😂 Thank you~


add model.summary(*sample_inputs)

Sometimes I want to print shape and parameter counts when I am building the model. However the summary function is now bind to learner object, I have to first construct many things(DataLoaders, Datasets, Transforms, loss_func ...) before using summary(). Not so convenient. So I try to patch summary() function to nn.Module and keep the learn.summary functionality but change its implementation to call model.summary().
Hope this can help.
Usage:
m = nn.Sequential(nn.Linear(1,50), nn.ReLU(), nn.BatchNorm1d(50), nn.Linear(50, 1))
sample_input = torch.randn((16, 1))
m.summary(sample_input)

Output:
Sequential (Input shape: ['16 x 1'])
================================================================
Layer (type)         Output Shape         Param #    Trainable
================================================================
Linear               16 x 50              100        True
________________________________________________________________
ReLU                 16 x 50              0          False
________________________________________________________________
BatchNorm1d          16 x 50              100        True
________________________________________________________________
Linear               16 x 1               51         True
________________________________________________________________

Total params: 251
Total trainable params: 251
Total non-trainable params: 0

It's looking good and useful! I have some minor style issues but I'll push them in a separate commit after merging. Thanks!


Fixes #57

I have written a small method clearMessages that removes all notifications from notification center. For my use case, I am calling this method in onDeviceReady and onResume, so that all app related notifications are cleared when application is launched and/or restored from backgound. I have tested it on both Android and iOS, seems to be working fine. But I have very little experience in Java and Objective C, so please perform a sanity check before accepting the pull. Thank you!

@maxymczech 👍

Published in v4.4.2


Make Failure extractor exhaustive

This makes code like the following compile without an exhaustiveness warning:
parse(...) match {
  case Failure(err, index, extra) =>
    ...
  case Success(p, index) =>
    ...
}

Instead, one currently has to write:
parse(...) match {
  case f: Failure =>
    val Failure(err, index, extra) = f
    ...
  case Success(p, index) =>
    ...
}

@lihaoyi care to merge this? It's very minor.

pushed a dummy commit to retrigger CI

Thanks!


Real World Example for .. in Loops

I am not sold on how I am presenting the relevance of not knowing how long the line is.
I am also not sold on using child as the thing we're iterating through because it doesn't quite map to properties of an object, but for each as a concept is not limited to objects.
Happy to have feedback or change the example per your ideas! :)

@barnes7td maybe @bdougie? maybe @mmaxwell ? Any feedback on this one?

I agree, that length doesn't matter. I also think this may be a bad example. When I think of a line, I think of an array because an array is an ordered list. You use an array when the order matters, and I view the line at a cotton candy truck as a FIFO line. The specs for for...in say that the keys are iterated in an arbitrary order, so the ordering is never guaranteed.
I'm not exactly sure how I would tweak this example, but I think that coupled with the term "length" would encourage someone to think about this in terms of an array instead of an object.
I'm about to hop into a meeting, but I will think about this and provide more thoughts later.

@mmaxwell I appreciate this feedback. I'm going to close this PR because I think I need a different example here.


Adds support for homodyne sampling in default.gaussian

Context:
See this issue: https://github.com/XanaduAI/pennylane/issues/272
Description of the Change:
Adds sampling of quadartures for the default.gaussian plugin
Benefits:
Can use sample to estimate expectation values
Possible Drawbacks:
Related GitHub Issues:

Note: some of the new tests in this PR are failing stochastically - in this case, test_samples_squeezed is failing. You will need to increase the number of samples, or, if taking too long to run, decrease the tolerance.

Good from my point of view! I just would recommend to have less samples in the test.
I'm also very supportive of @co9olguy's point that we should get rid of the stochastic tests and move to tests of the circumstandes (shapes of outputs, correct calls etc). Checking that np.random.normal is called with the correct arguments would be possible by MagicMocking it.

@johannesjmeyer since you already have a good idea how convert stochastic tests to circumstance tests, it would be great if you could help with that (check with @nquesada to confirm he's not doing it at same time though)

@johannesjmeyer it would be great if you could add the code to useMagicMock  for testing shapes and calls. I could review the code and the process and also learn something new in the process.

@johannesjmeyer it would be great if you could add the code to useMagicMock for testing shapes and calls. I could review the code and in the process also learn something new.

I'm happy to do this, but I already have all my hours done for this week and I'm a little bit stressed with other urgent business of mine, so I can't guarantee that I can do it this week.
If you don't want to wait that long to wrap this up, I recommend to have a look at the test test_obs_queue_is_filled_during_execution in test_device.py for the magic mock and the tests in the class TestSample of test_measure.py for the circumstancial tests.

@nquesada, I changed the tests. While on it I also added tests for the error messages.
I also spotted an error in the squeezed state test (a missing sqrt).
It would be nice if you could probably add some test cases to the squeezed state test. For that I think that you have to change the formula that calculates mean and variance, so that it can also handle other test cases than r=1, phi=0.

@nquesada, after looking again I realized it wasn't your error but my confusion, because you used std in one test and var in the other -- sorry! I had to add the sqrt to the calculate the standard deviation in the squeezed state test.

@nquesada @johannesjmeyer, what is the status of this PR? I can see that there is an issue with coverage (the pylint error can be ignored for now)


glTF importer fails loading images for Khronos sample "Box With Spaces"

Godot version:
3.3 RC 8 and master (43f89e7c2ca080168ebf8adc1c23489491320429)
OS/device including version:
Linux
Issue description:
When importing the Khronos sample "Box With Spaces", the materials are not properly imported because we fail to load the images.

Should be:

Import log:
glTF: Importing file res://Box With Spaces/glTF/Box With Spaces.gltf as scene.
glTF: Total buffers: 1
glTF: Total buffer views: 4
glTF: Total accessors: 4
Loading resource: res://Box With Spaces/glTF/Normal%20Map.png
ERROR: _load: Resource file not found: res://Box With Spaces/glTF/Normal%20Map.png.
   At: core/io/resource_loader.cpp:283.
ERROR: get_file_as_array: Can't open file from path 'res://Box With Spaces/glTF/Normal%20Map.png'.
   At: core/os/file_access.cpp:606.
WARNING: _parse_images: glTF: Image index '0' couldn't be loaded as a buffer of MIME type 'image/png' from URI: res://Box With Spaces/glTF/Normal%20Map.png. Skipping it.
   At: editor/import/editor_scene_importer_gltf.cpp:1367.
Loading resource: res://Box With Spaces/glTF/glTF%20Logo%20With%20Spaces.png
ERROR: _load: Resource file not found: res://Box With Spaces/glTF/glTF%20Logo%20With%20Spaces.png.
   At: core/io/resource_loader.cpp:283.
ERROR: get_file_as_array: Can't open file from path 'res://Box With Spaces/glTF/glTF%20Logo%20With%20Spaces.png'.
   At: core/os/file_access.cpp:606.
WARNING: _parse_images: glTF: Image index '1' couldn't be loaded as a buffer of MIME type 'image/png' from URI: res://Box With Spaces/glTF/glTF%20Logo%20With%20Spaces.png. Skipping it.
   At: editor/import/editor_scene_importer_gltf.cpp:1367.
Loading resource: res://Box With Spaces/glTF/Roughness%20Metallic.png
ERROR: _load: Resource file not found: res://Box With Spaces/glTF/Roughness%20Metallic.png.
   At: core/io/resource_loader.cpp:283.
ERROR: get_file_as_array: Can't open file from path 'res://Box With Spaces/glTF/Roughness%20Metallic.png'.
   At: core/os/file_access.cpp:606.
WARNING: _parse_images: glTF: Image index '2' couldn't be loaded as a buffer of MIME type 'image/png' from URI: res://Box With Spaces/glTF/Roughness%20Metallic.png. Skipping it.
   At: editor/import/editor_scene_importer_gltf.cpp:1367.
glTF: Total images: 3
glTF: Total materials: 1
glTF: Parsing mesh: 0
glTF: type vec3 component type: Float stride: 12 amount 24
glTF: accessor offset0 view offset: 0 total buffer len: 840 view len 288
glTF: type vec3 component type: Float stride: 12 amount 24
glTF: accessor offset0 view offset: 288 total buffer len: 840 view len 288
glTF: type vec2 component type: Float stride: 8 amount 24
glTF: accessor offset0 view offset: 576 total buffer len: 840 view len 192
glTF: type float component type: UShort stride: 2 amount 36
glTF: accessor offset0 view offset: 768 total buffer len: 840 view len 72
glTF: Total meshes: 1
glTF: Creating mesh for: Cube
Loading resource: res://Box With Spaces/glTF/Material.material
Saving scene to: res://.import/Box With Spaces.gltf-478c4be1a466d795160f99cce5647671.scn

The .glTF seems to use %20 to encode spaces, apparently we need to convert them ourselves back to actual spaces (likely using uri_decode).
Steps to reproduce:

Load MRP with --verbose

Minimal reproduction project:
gltf-with-spaces.zip

Indeed, from the glTF specification https://github.com/KhronosGroup/glTF/tree/master/specification/2.0#uris
Quote (emphasis mine):

Relative URI paths — or path-noscheme as defined by RFC 3986, Section 4.2 — without scheme, authority, or parameters. Reserved characters must be percent-encoded, per RFC 3986, Section 2.2.

Appears to import correctly now. Fixed by the uri decode in https://github.com/godotengine/godot/commit/aca4b737f107c344151cb8eb859087b1f52fbe35.


Leaderboard should be added

The dashboard should have a list of people leading in the scoreboard. Top three people should be highlighted.
Docs: https://documenter.getpostman.com/view/26244894/2sAXqtbgvt#a9da02bc-4e6b-4dd6-9c6e-503e243d8c6a

go ahead


Add patch to disable suspending animation

Refs https://github.com/atom/electron/issues/4317#issuecomment-192619978.
(I'm not sure whether it would work.)

Not working. :(


Migrate command refactored within an ImportService.php

Commands regarding export/import of EMS specific stuff should live in the EMSMakerBundle (cfr. the functionning ContentTypeCommand)

This PR is too big. I have still some remarks, but they are maybe solved in your other PRs. Next time I will not validate this size of PR and will ask to "restart" in smaller PRs.
So this is the last one that I accept #306 will be used as a reference if this kind of PR size is given in the future. Thank you.


Segmentation Fault

I am having an error while trying to generate gifs.

Can you add me on discord
Ace_#5831

can u send me the screenshot of ur main.cpp file?

Feel free to reopen

Hey. Whats ur discord name


The ErrorTrigger firing too many times, when multiple messages are received.

If a single message is sent., the expected behaviour happens.  The error trigger is fired once per sent message.
If I send 10 messages at the same time, the error trigger is fired 3 times per message. Total 30 times.
1 message = 1 ErrorTrigger fired.
2 messages =  6 ErrorTriggers fired
5 messages = 15 ErrorTriggers fired
10 messages = 30 ErrorTriggers fired
Repro steps
Using Service Bus explorer send 10 messages at once.
Expected behavior
The ErrorTrigger should be fired 10 times.
Actual behavior
The ErrorTrigger is fired 30 times.
Related information
I have tried version 1.0.1 and 2.0.0-beta1 WebJobs.extensions.
I have tried numerous different message amounts and it always multiplys by 3.
I have turned off retrying of failed messages.
The correct number of messages are going in and the correct amount are going on the dead letter queue.
The EventSubscriptionToNotificationTopic method is called the correct number of times.
If I send one message:
Exception thrown: 'System.Exception' in WebJob.exe
Error 94591d32-e94f-4232-ae60-a643af47fc22
If i send 1 message then straight away another message:
Exception thrown: 'System.Exception' in WebJob.exe
Error 020c1fb6-614b-46fb-8077-d5286db19577
Exception thrown: 'System.Exception' in WebJob.exe
Error 966514bb-933d-44ce-af31-28435d84050d
Error 3e802d0b-e9c2-45f8-81b3-c11fce93dc2d
Error c1a8d762-0336-4c2b-9833-0f74c370ef92
The second message has fired ErrorTriggert 3 times.
Executing: 'WebJob.EventSubscriptionToNotificationTopic' - Reason: 'New ServiceBus message detected on 'eventtopic/Subscriptions/NotificationSub'.'
Executed: 'ErrorTrigger.HandleError' (Succeeded)
Executing: 'ErrorTrigger.HandleError' - Reason: 'Error trigger fired'
Executed: 'ErrorTrigger.HandleError' (Succeeded)
Executing: 'ErrorTrigger.HandleError' - Reason: 'Error trigger fired'
Executed: 'ErrorTrigger.HandleError' (Succeeded)
Executing: 'ErrorTrigger.HandleError' - Reason: 'Error trigger fired'
If i remove the ErrorTrigger and replace it witha  try catch then i get the correct number of erros logged.
Exception thrown: 'System.Exception' in WebJob.exe
Error 6203dc14-7294-48cb-b7ae-84a1896c9c0a
Exception thrown: 'System.Exception' in WebJob.exe
Error 9cf0c0c6-d00b-4967-9765-dbfb66e9ab02
Exception thrown: 'System.Exception' in WebJob.exe
Error 7fd1d966-00f8-41ba-afd7-62e5ac9008ac
Sample code attached.
Code.txt

ErrorTrigger lives in the extensions repo. Moved:
https://github.com/Azure/azure-webjobs-sdk-extensions/issues/166


Provide Maven BOM for OSGi Specs

It would be nice to have a Maven BOM per OSGi specification (Core and Compendium) that lists all most recent individual OSGi chapter spec dependencies. Often OSGi container are fully compliant with Core R7 or Compendium R7 so reusing an official BOM for doing the dependency management would be beneficial.

Often OSGi container are fully compliant with Core R7 or Compendium R7 so reusing an official BOM for doing the dependency management would be beneficial.

I don't think this is true. Having a BOM is useful when a set of artifacts must be used together at prescribed versions. This can be true for the Jakarta EE platform,  the MicroProfile platform, Spring Framework, JUnit, etc. But OSGi is not like that. We do not define a platform. We publish a collection of specifications of which you are free to use in mixed and matched versions as desired.
Furthermore, the OSGi build is not a maven build, so we have no way to ensure that any BOM we produce is a valid maven pom file and is even correct where the declared artifact versions match the versions of the actual artifacts produced by the build.

I will follow up by also noting that a BOM would have the same issues as the osgi.cmpn artifact that OSGi no longer publishes. It creates an implicit coupling between the OSGi specs in the BOM/osgi.cmpn when there is no actual coupling.

All bundles from ASF Sling or ASF Felix which implement more than one spec use either Core R6, R7 or R8. Same for Compendium.

OK, but they do not implement every compendium spec. Just the ones they care about and even some of this may have had little attention recently.

Do you have examples of OSGi bundles mixing different spec versions?

I have seen the issues with the implicit coupling caused by using osgi.cmpn. It caused the bundle to uplevel its use of any OSGi spec it touched. So if I have a bundle that uses Config Admin and also Promises, just because I need to use the latest Config Admin spec (to use some new feature) does not mean I want to use the latest Promise spec. I only use the features of the older Promise spec and want to maintain my import range on the older Promise API for maximum deployment flexibility.
Using a BOM or osgi.cmpn causes me to use the latest Promise API at compile time which causes me to have a higher import range than I desire.
So I don't see that a BOM is a good thing when there is no actual version coupling between all the elements in the BOM. For JUnit it makes sense, you want to use all the desired JUnit artifacts at the matching versions prescribed by the BOM.
I recently went through a whole effort in the OSGi build to remove the use of osgi.cmpn so that each spec API project uses the individual API artifacts for any dependencies on other OSGi specs at the lowest versions needed by the spec. This means that, for example, the org.osgi.service.component spec API project uses the org.osgi.util.promise API at version 1.0 even though the latest org.osgi.util.promise API is version 1.2.
This is how people should develop: compile low, run high. And a BOM (or osgi.cmpn) does not support compile low as people will tend to use the latest BOM to get access to some new spec version they need and then compile against higher versions of other OSGi specs when the really do not need to. When this happens it makes resolving a system much harder since you may not be able to deploy a bundle without also updating all dependencies since the bundle compiled high.

OK, but they do not implement every compendium spec. Just the ones they care about and even some of this may have had little attention recently.

Exactly, that is also why a BOM only defines dependencyManagement (i.e. you still need to reference the needed chapter dependencies, just without version)

Exactly, that is also why a BOM only defines dependencyManagement (i.e. you still need to reference the needed chapter dependencies, just without version)

And this is dangerous as it create implicit version coupling. Felix SCR needs to implement the DS spec at the latest version. The DS spec uses the Promise spec but only at the 1.0 version. The BOM will expose Felix SCR to the latest version (1.2) of the Promise spec which means that Felix SCR will import the highest version of the Promise spec when it only needs the 1.0 version of the Promise spec. So Felix SCR will not be able to be deployed when the Promise API is only available at version 1.0.
The best choice for Felix SCR is to use the oldest version of Promise consistent with its actual needs not just that latest version because the BOM specifies the latest version.

So Felix SCR will not be able to be deployed when the Promise API is only available at version 1.0.

Right, but isn't this a very theoretical case? Which OSGi container has DS 1.5 but Promise 1.0?

The best choice for Felix SCR is to use the oldest version of Promise consistent with its actual needs not just the latest version because the BOM specifies the latest version.

I agree with that principle, still managing all spec chapters versions individually is often painful, therefore developers stay with the worse aggregate dependencies. A BOM would not prevent anyone from defining versions themselves. I rather see it as vehicle to migrate from aggregate to individual spec dependencies.

Which OSGi container has DS 1.5 but Promise 1.0?

You keep saying "OSGi container" like it is a defined platform. OSGi usage is a framework plus whatever bundles you want.

Right, but isn't this a very theoretical case?

In my experience it is not theoretical and is the reason OSGi retired the osgi.cmpn artifact.

I rather see it as vehicle to migrate from aggregate to individual spec dependencies with less effort.

I don't see how it does that since one must still specify the dependency in their POM. The BOM only removes the need to include the version. And my argument is that this is a problem. The developer needs to choose the lowest version that is necessary and not the latest version specified in the BOM.

Right, but isn't this a very theoretical case?

In my experience it is not theoretical and is the reason OSGi retired the osgi.cmpn artifact.

In fact the osgi-test project deals with this in regard to the Promise API version:
https://github.com/osgi/osgi-test/blob/ad65c29d0eddb15f6b5a40f6b40bbb734516ea4e/pom.xml#L54-L57
The project needs to support users with Promise 1.0 and so it compiles against Promise 1.0, but it also needs to test against the latest version.


uv sync --no-install-package without pyproject.toml

On the same theme as #6685 and #6573, but easier to solve?
Since the package name is provided on the CLI and also present in uv.lock, there should be no need to read pyproject.toml at all?

Since the package name is provided on the CLI...

Do you mean, if you use uv sync --package?

Similar to #6573, part of the complexity is that we use the pyproject.toml to determine the root directory of the workspace. We'd need to use the uv.lock to encode this instead, just in this case?

I think the thought is --no-install-package my-root-package

Ohh I see. I think I'd rather that we put the workspace root in uv.lock, and then allow uv sync or uv sync --package.

Honestly it would be easy to support uv sync --package, and users could pass the workspace root, but I know that's a little tedious.

To clarify, my use case is still the dependencies-only layer of a Dockerfile.
It sill itches me a little bit to have to copy pyproject.toml in addition to uv.lock.
uv sync --no-install-package my-root-package --frozen seemed quite close to it: as you mentioned in https://github.com/astral-sh/uv/issues/6573#issuecomment-2308381467 that pyproject.toml is used only to obtain the package name, I assumed it was not necessary since in the case of --no-install-package, the package name is known upfront from the CLI.

Yeah it bothers me too. I think we can fix it holistically.

I guess one challenging case is: you're workspace is rooted at root, and you're at root/packages/foo. Normally, if you ran uv sync, we'd sync foo. But if we don't have any pyproject.toml etc., we have no way of knowing that you're in that workspace member. So uv sync --frozen would have to sync the workspace root instead.

The other strange piece is that you lose any configuration defined in pyproject.toml. (Just documenting things I notice as I work on this.)

Ah, and extras may also influence the design. What if, for instance, I want to seed the dependencies of my root package but only some of it's optional dependencies?

Ah, and extras may also influence the design. What if, for instance, I want to seed the dependencies of my root package but only some of it's optional dependencies?

This would work as expected, I think, since we store this information in the lock.

that seems particularly problematic :/ we don't really want to copy all those into the lock do we?

No, I don't think so. The situation we're at now is we still require the root pyproject.toml but none of the members (as of my PR last night).
I think we can support not requiring the pyproject.toml at all, but users would need to copy it over if they had configuration defined in there.

To add to @sbidoul usecase:

To clarify, my use case is still the dependencies-only layer of a Dockerfile. It sill itches me a little bit to have to copy pyproject.toml in addition to uv.lock.

Because we need to copy the pyproject.toml over alongside the uv.lock in the Dockerfile
COPY ./pyproject.toml ./pyproject.toml
COPY ./uv.lock ./uv.lock
RUN uv sync --no-install-package --no-cache --frozen --no-dev

every time we update the version number, the previous cached layer containing the dependencies is invalidated, even though uv.lock hasn't changed.
This is not that big deal for projects that are light on dependencies, but for projects that use ML workloads, re-installing and duplicating ~5GBs of dependencies every time the version changes is wasteful.

For anyone looking for a solution in the meantime, export the dependencies to requirement.txt via uv export and use that.
echo "--extra-index-url https://{...}/simple" > requirements.txt
uv export --format requirements-txt --no-hashes --no-editable --no-dev >> requirements.txt

COPY ./requirements.txt ./requirements.txt
RUN pip install --no-cache-dir -r ./requirements.txt


Remove autoscroll_forever option.

We have discussed removing the autoscroll_forever option, which fewer than 1% of users use, and which causes confusion for users, and which may be prone to bugs (since few devs use it or even know about it).
Removing this feature should be fairly easy for any developer with a little bit of experience doing full-stack features for Zulip.
On a high level we want this to happen:

communicate on chat that you're making this change, so we can start warning people this is going away
remove UI code related to this experimental feature (including settings)
remove backend support for flipping the setting
write a migration to remove the column
update the changelog and any other relevant documentation

Is this feature documented anywhere? I was curious, but I'm not sure what is expected to happen, and that discussion is inaccessible to me.

It's not super documented.

@zulipbot claim


cleaned OnUnitEnterLeave and separated from UnitIndexer

I hope it's tested, but looks simple enough to work :D

Thanks!

@peq i writed a few tests, please look at this: https://github.com/peq/WurstScript/issues/345
@Frotty you're welcome good sir.


fix(clusterpools): cluster-pool-ipv4-cidr/cluster-pool-ipv6-cidr

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Thanks for contributing!

`cluster-pool-ipv4-cidr` and `cluster-pool-ipv6-cidr` should be string slices and not string

Thanks for the contribution.
I believe however changing this value breaks upgrades. If users use "--reuse-values" when performing "helm upgrade", Helm will likely fail trying to apply join to a string, no?
My proposal therefore would be to introduce a new Helm value (e.g. operator.clusterPoolIPv6PodCIDRList), modify the chart such that it prefers the new list-based one (if set), but fails back to the old string-based one if not. And then we can deprecate the old one eventually. At least we should mention this change it the update notes.
While less elegant, there is also an option where we don't change the Helm value at all. I believe if you only changed flags.String to flags.StringSlice that you can specify multiple CIDRs via Helm by just comma-separating them, e.g. "ipam.operator.clusterPoolIPv4PodCIDR=<IP_ADDRESS>/8,<IP_ADDRESS>/12" should work too.

clusterPoolIPv6PodCIDRList

Thanks for the contribution.
I believe however changing this value breaks upgrades. If users use "--reuse-values" when performing "helm upgrade", Helm will likely fail trying to apply join to a string, no?
My proposal therefore would be to introduce a new Helm value (e.g. operator.clusterPoolIPv6PodCIDRList), modify the chart such that it prefers the new list-based one (if set), but fails back to the old string-based one if not. And then we can deprecate the old one eventually. At least we should mention this change it the update notes.
While less elegant, there is also an option where we don't change the Helm value at all. I believe if you only changed flags.String to flags.StringSlice that you can specify multiple CIDRs via Helm by just comma-separating them, e.g. "ipam.operator.clusterPoolIPv4PodCIDR=<IP_ADDRESS>/8,<IP_ADDRESS>/12" should work too.

Thank you very much, I agree with you. I'll think about how to modify it

Thanks for the contribution.
I believe however changing this value breaks upgrades. If users use "--reuse-values" when performing "helm upgrade", Helm will likely fail trying to apply join to a string, no?
My proposal therefore would be to introduce a new Helm value (e.g. operator.clusterPoolIPv6PodCIDRList), modify the chart such that it prefers the new list-based one (if set), but fails back to the old string-based one if not. And then we can deprecate the old one eventually. At least we should mention this change it the update notes.
While less elegant, there is also an option where we don't change the Helm value at all. I believe if you only changed flags.String to flags.StringSlice that you can specify multiple CIDRs via Helm by just comma-separating them, e.g. "ipam.operator.clusterPoolIPv4PodCIDR=<IP_ADDRESS>/8,<IP_ADDRESS>/12" should work too.

done

/test

I suspect that some of the failures in CI are because this PR has not been rebased against the latest master branch recently. Could you also rebasing against master while addressing the above feedback?

ABC was deprecated in favor of BBC

Thanks for the PR. At a glance this seems like it should be safe for upgrades from existing clusterpool configuration, although I have not tested it out.
There's a few references to the old name for this field in the docs, could you fix them up?
$ git grep clusterPoolIPv4
Documentation/gettingstarted/ipam-cluster-pool.rst:   * ``--set ipam.operator.clusterPoolIPv4PodCIDR=<IPv4CIDR>``
Documentation/gettingstarted/ipam-cluster-pool.rst:   * ``--set ipam.operator.clusterPoolIPv4MaskSize=<IPv4MaskSize>``
Documentation/gettingstarted/k8s-install-openshift-okd.rst:reflect those changes. Namely ``clusterNetwork`` should match ``nativeRoutingCIDR``, ``clusterPoolIPv4PodCIDR`` and ``clusterPoolIPv4MaskSize``.
...

Also, should this be added into the Documentation/operations/upgrade.rst upgrade guide to inform users that they should migrate their configurations to the new settings?

Thx, updated

/test

Hi, Is there anything else I need to do next?

Hi, Is there anything else I need to do next?

Let's give @errordeveloper some time to re-review. Other than that, this should be good to go.
I'll also re-run CI again to in-cooperate the last changes.

/test

Hi, Is there anything else I need to do next?

Let's give @errordeveloper some time to re-review. Other than that, this should be good to go.
I'll also re-run CI again to incooperate the last changes.

thank you

Hi, do I need to do something to solve this CI can not succeed?

/test

Hi, do I need to do something to solve this CI can not succeed?

Pushing new commits unfortunately invalidates previous CI runs and their links, so I can't tell you what went wrong the last time besides one known-flaky test that got flagged (which is unrelated to your changes) here: https://github.com/cilium/cilium/pull/17780#issuecomment-972692672
I'll run the tests again (this can only be done by team members with commit access unfortunately), please avoid pushing to the branch after the tests have run to keep the result validated.

/test

Hi, do I need to do something to solve this CI can not succeed?

Pushing new commits unfortunately invalidates previous CI runs and their links, so I can't tell you what went wrong the last time besides one known-flaky test that got flagged (which is unrelated to your changes) here: #17780 (comment)
I'll run the tests again (this can only be done by team members with commit access unfortunately), please avoid pushing to the branch after the tests have run to keep the result validated. There is usually no need to rebase.

Thank you very much

/test
Job 'Cilium-PR-K8s-GKE' hit: #17353 (88.79% similarity)
Job 'Cilium-PR-K8s-1.21-kernel-4.19' hit: #17881 (98.18% similarity)

Sorry, it seems that the rebase is a past commit, I need to fix it.

/test

Can you retrigger it? Thank you

/test

Can you retrigger it? Thank you

Yes, will re-trigger it as soon as the Image CI Build stage has finished. Please note that it is usually fine if your branch is not up to date with the master branch, there is no need to rebase, unless there is a known bug somewhere.

/test


feat: add shebang to Ace template

Proposed changes
Execute Ace directly without typing node. This requires Ace to be executable (x flag).
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

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

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary documentation (if appropriate)

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Does this work fine for Windows too? I believe, the path is specific for Linux

Closing since not actionable


JSON-LD parser

Adds a separate commandline program that takes json-ld as input and outputs compressed turtle. Useful for discussing different json-ld formats

Split into a separate project


Skeleton w/ArgoCD for cluster-as-a-service component

This component has a dependency on ArgoCD much like the gitops service does. v1.9 of the openshift-gitops operator isn't sufficient, however, because it provides ArgoCD v2.7 when v2.10 is required for PostDelete hooks. This conflict is resolved by excluding the gitops component when EaaS is enabled since the former is expected to be discontinued soon.

@jgwest please review as well since a lot of this is working around the chicken and egg issue with installing ArgoCD and I've had to disable the gitops component to use a required newer version.

/test appstudio-hac-e2e-tests

Moved to draft state. The gitops component is being removed from dev and staging in #3760. I'll wait for that to be merged as it'll help simplify this change.

/retest-required

/test appstudio-hac-e2e-tests
/test appstudio-upgrade-tests

All tests are passing with the upgraded ArgoCD :tada:. Awaiting some reviews.


Enable Quiet Processing

Hi,
I'm using Augmentor in an automated process for 1000s of images. Would it be possible to add a new kwarg to process() so that it does not print anything while processing?
Currently, in my logs, it looks like this, for 1000s of images, which clogs up the logs:

Hi @nseidl, thanks for making the issue. Yes I can do that, it is a good idea so I think I will just add it as a global option actually for those who are using Augmentor in situations where no progress updates are required.

I was having the same problem. For people who are also getting overflowing logs, you can do a quick fix by adding disable=True option where tqdm is called in Pipeline.py.
It would be really nice to have a built-in option for quiet output though :)

This is quite an old issue, but still important in some cases.
Will this feature be implemented some time?

Hey everyone, is this still being actively developed?

Hey everyone, is this still being actively developed?

Hi there, at the moment only bugs are being fixed, and no new features are really being added. However, because a few more urgent bugs need to be fixed and this will be done in the next week or so, I'll make sure to add this feature in that update.

Sounds great, thanks!
On Mon, 1 Mar 2021 at 09:22, Marcus D. Bloice<EMAIL_ADDRESS>wrote:

Hey everyone, is this still being actively developed?
Hi there, at the moment only bugs are being fixed, and no new features are
really being added. However, because a few more urgent bugs need to be
fixed and this will be done in the next week or so, I'll make sure to add
this feature in that update.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mdbloice/Augmentor/issues/176#issuecomment-787754269,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSTT6C3WCCGG4TGEZMTFOLTBNFFNANCNFSM4HKBO7AA
.

--
Matthias F. Brandstetter
<EMAIL_ADDRESS>


Cop to check for .gitignore'd files

There is a note regarding Gemfile.lock, but it is under "Rails Style Guide". I think it is not only rails specific.
Imo, we could at least check for

Gemfile.lock
db/schema.db (supporting multi databases)
db/structure.sql (supporting multi databases)
some other examples?
TO NOT BE ignored.

We can check for some files TO BE ignored:

like .env related files
rails credentials related files
something else?

Make those lists configurable.

Make those lists configurable

Yes :-) For example Gemfile.lock is no longer officially recommended by rubygems in gitignore and it isn't anymore by default for bundle gem my_new_gem for example. I disagree with this, but a cop must be configurable for this. Autocorrection would be cool; I have to manually add it when I create a gem (which is often these days, playing with Ractor).
I'm also adding .rubocop-http* until #9181 is resolved.


README.md and LICENSE

Create a README file with all technical details and the project description and usage. Also add on an MIT License file. @Nancy-30

Completed

Issue completed


calculate the angles between robotpose and global plan point pose

in ftc_planner.cpp,lin239,when you calculate the angles between robotpose and global plan point pose, should the x_pose be transformed_global_plan_.at(i) or transformed_global_plan_.at(point)?
double FTCPlanner::calculateGlobalPlanAngle(tf::Stampedtf::Pose current_pose, const std::vector<geometry_msgs::PoseStamped>& plan, int point)
{
if(point >= (int)plan.size())
{
point = plan.size()-1;
}
double angle = 0;
double current_th = tf::getYaw(current_pose.getRotation());
for(int i = 0; i <= point; i++)
{
geometry_msgs::PoseStamped x_pose;
x_pose=transformed_global_plan_.at(point);
        //Calculate the angles between robotpose and global plan point pose
        double angle_to_goal = atan2(x_pose.pose.position.y - current_pose.getOrigin().getY(),
                                     x_pose.pose.position.x - current_pose.getOrigin().getX());
        angle += angle_to_goal;
    }

    //average
    angle = angle/(point+1);

    return angles::shortest_angular_distance(current_th, angle);
}

Hi,
yes this is a failure. It should be x_pose be transformed_global_plan_.at(i) and not  transformed_global_plan_.at(point)


Unable to exclude directories when running the CLI

Describe the bug
When trying to run Bandit using the CLI and providing a ini, pyproject or yaml file for the configuration the exclude option is not working.
Reproduction steps

Create a .bandit or pyproject.toml or bandit.yaml
Run a scan with the created config

In all situations the exclude is not functioning.
file: .bandit
[bandit]
exclude = tests

Run using bandit -r .
file: pyproject.toml
[tool.bandit]
exclude_dirs = ["tests"]

Run using bandit -c pyproject.toml -r .
file: bandit.yaml
exclude_dirs: ["tests"]

Run using bandit -c bandit.yaml -r .
In my case due to the use of assert statements i need to process all the tests and provide a # nosec argument.
Expected behavior
When providing a config with the exclude option i would expect that the exclude option is working. And the correct directory is ignored by Bandit for further processing.
Bandit version
1.7.4 (Default)
Python version
3.9
Additional context
See also #499
No response

Currently running bandit 1.7.5 and this is still a problem. I have to just skip B101 to be able to commit any tests.

Are you using pre-commit? I ran into this problem with several libraries. Pre-commit ignores the excludes in the toml file for some reason, so you have add exclude to the pre-commit-config.yaml.
      - id: bandit         name: Lint Python security with bandit         exclude: "^app/tests/"


issue setting up backups (new to this stuff)

Hello, I'm pretty new to this, but I have a basic understanding of what's going on. I have a server using OMV that has docker installed on it. I can access docker through Portainer.io. I set up the bedrock server using stacks. The server is running fine, but the world doesn't save when I restart the stack. I was hoping that the backups would solve this issue. I've tried to map everything correctly, but I'm not sure what I am doing wrong. This is the message I am getting in the container logs for the backups container:
time="2021-09-12T18:09:41-06:00" level=debug msg="Using /backups to match uid and gid"
time="2021-09-12T18:09:41-06:00" level=debug msg="Resolved 0 from environment variable UID"
time="2021-09-12T18:09:41-06:00" level=debug msg="Resolved 100 from environment variable GID"
The operation could not be completed. No such file or directory
This is the stack:

version: "2"
services:
minecraftbedrock-server:
image: itzg/minecraft-bedrock-server
container_name: minecraftbedrock-server
network_mode: host
environment:
- PUID=998
- PGID=100
- EULA=TRUE
- VERSION=<IP_ADDRESS>
- MEMORY=15G
- SERVER_NAME:Stenzilone
- ONLINE_MODE=false
- LEVEL_NAME=NoMamesWay
- ALLOW_CHEATS=true
- OPS=2535469741104124
- LEVEL_SEED=1595425848
ports:
- 19132:19132/udp
volumes:
- /srv/dev-disk-by-label-DigitalStorage01/MinecraftBedrock:/data
stdin_open: true
restart: unless-stopped
backup:
image: kaiede/minecraft-bedrock-backup
container_name: MinecraftBackup
restart: always
depends_on:
- "minecraftbedrock-server"
environment:
UID: 0
GID: 100
BACKUP_INTERVAL: "1h"
TZ: "America/Denver"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /srv/dev-disk-by-label-DigitalStorage01/MinecraftBedrock:/minecraftbedrock-server
- /srv/dev-disk-by-label-DigitalStorage01/MinecraftBackups/backups:/backups
- /srv/dev-disk-by-label-DigitalStorage01/MinecraftBackups/config.json
stdin_open: true
I'm not sure if the UID and GID are correct
Thanks for your help!

Running backups will eventually be helpful, but that's not needed for your initial scenario. The persistent /data volume is what is important.
The volume config for minecraftbedrock-server looks right with:
volumes:
- /srv/dev-disk-by-label-DigitalStorage01/MinecraftBedrock:/data

however, maybe the path /srv/dev-disk-by-label-DigitalStorage01/MinecraftBedrock is not valid on your OMV  host. I'm pondering that knowing little about what OMV is. Can you provide the logs from the minecraftbedrock-server service?

So I just figured out right before I saw this post that the /data was what was needed. As soon as I put that in and updated the stack, the "MinecraftBedrock" file populated with all the files that it should have had from the beginning. Now, the world actually saves in the world folder.

Good to close the issue?

I think for the bedrock server part, but I still need help with the backups part. If I can get it figured out right now, I don't have to worry about it later.

You'll need to open an issue with kaiede, since it's their backup image.

I thought I had. Just realized I didn't. Thanks for the help!

if you want to do a live backup you'll need to send to the console a
"save hold" and run "save query" until it tells you it's ready to take the backup otherwise you'll be missing all the changes that are still on memory
after you do the actual backup you need to finally run "save resume"
for non live backups just stop the container and backup the files of the volume.

I'm having issues with persistent world loading.
I have a service that launches a docker-compose file.
ExecStartPre copies the server files from a backup location to a RAM drive.
ExecStopPost rsyncs the server files from the RAM drive to a backup location.
I have an hourly cron job to restart the service to prevent accidental data loss and to have a history of incremental backups.
When the service launches on boot it starts a fresh world.  If I manually stop the container, rsync world files to the ram drive, then start the container, then the world shows up.
I've spent a good number of hours trying to figure out what the issue is.  I don't think there are permission issues.  My best guess is an order of operations issue.  rsync makes destination folders and does not return until it's finished, so I'm not sure why the service is misbehaving.

I got it sorted.  There were a few issues, all related to the rsync calls.  Firstly, rsync does not make destination folders if they are not already present.  Second, I think the way the folders were transferred originally did not result in them being placed in the correct level.  Everything now works with the service pre and post execs calling these scripts:
sudo mkdir -p /mnt/ram/mcbe
sudo rsync -av /mnt/servers/mcbe/* /mnt/ram/mcbe

sudo mkdir -p /mnt/servers/mcbe
sudo rsync -av /mnt/ram/mcbe/* /mnt/servers/mcbe


Cargo does not use output of build.rs for the bin target in projects containing both bin and lib

Problem
I have a project that was originally an application and recently I've decided to make it I also a library. The project uses a build script to link with libpcap. After I added src/lib.rs, the project stopped building.
When I run cargo with the -v option, I can see that the lib target gets build just fine but the bin target fails because the linker cannot find some symbols (contents of libpcap). I can also see that the rustc command for the lib target contains arguments -l static=net_devices -l dylib=pcap but these arguments are not present for the bin target.
I'd expect all targets to use the output of build.rs.

Steps

Clone https://github.com/angelcam/arrow-client
Make sure that libpcap is installed on your system
Add src/lib.rs and
Run cargo build --features all

Notes
Output of cargo version:
cargo 1.38.0 (23ef9a4ef 2019-08-20)

This is expected and intended, otherwise you would get duplicate symbols. To work with this, the code using the libraries needs to be in lib.rs, and main.rs should just use arrow_client.

@ehuss Good to know! Thank you for the explanation.

This is expected and intended, otherwise you would get duplicate symbols. To work with this, the code using the libraries needs to be in lib.rs, and main.rs should just use arrow_client.

Is this true only for static libs? Could it be relaxed when dynamic linking is explicitly specified?

See also #5881.


Kiali ERR  is not found as Job, Empty Graph

Bug Description
deployed Kiali recent bundle from https://github.com/istio/istio.git along with all other add-on components
Kiali UI doesnt show any graph "Empty Graph", This setup was working fine in 1.6 and 1.8.1
Please advise
Version
m-c02zd2yvlvdq:bin s0r04i4$ ./istioctl version
client version: 1.11.0
control plane version: 1.11.0
data plane version: 1.11.0 (87 proxies)

Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7", GitCommit:"4966fd0dded6419fd23233a38c8905c67a3ea78e", GitTreeState:"clean", BuildDate:"2021-08-17T02:06:07Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}

Additional Information
Kiali Empty Graph

ERR Workload  is not found as Job

meshConfig:
enablePrometheusMerge: true
disabled this flag in operator, but enabling it back solve the problem. Now I see graph and animated traffic flow in Kiali.!! Please Close the ticket


Fixed network namespace leak

when libcontainer's netlink.NetworkSetNsPid is called, the network
namespace is created and attached with the pid. But this network
namespace persists even after the pid is killed. So we need to
explicitly delete these network namespaces, otherwise they get
piled up over time.

Hi @shashidharatd - thank you for spotting and letting us know about this leak.
I think the root cause is actually our use of ip netns exec in hook-parent-after-clone rather than NetworkSetNSPid (NetworkSetNSPid only moves an interface in to a namespace, it doesn't create one - the namespace is created by wshd when we create the container). Specifically, we create a symbolic link from /var/run/netns/$PID to /proc/$PID/ns/net which has the effect of keeping the network namespace in the list of namespaces even after the final pid using it exits (see http://man7.org/linux/man-pages/man8/ip-netns.8.html).
We're actually already planning to avoid using ip netns exec altogether: our plan is to remove the ip netns exec logic entirely and instead execute the network setup during the in-container hook. This way the network namespace should get automatically cleaned up by the last process using it exiting. This would also mean we can avoid adding extra code to the shell scripts - and actually it'd let us remove a fair bit (we're currently working quite hard to reduce the amount of shell scripting in garden and move more logic to go code). Since we're planning to do this anyway this should have the side effect of avoiding the problem you see above (although we might like to pull in your test case to be sure when we do this).
In the meantime a simpler tactical solution may be to remove the symbolic link created in hook-parent-after-clone.sh after ip netns exec returns (after which it should no longer be needed). This should - I believe - also cause the namespace to be properly cleaned up while minimising the amount of new shell scripting. What do you think?

Hi @julz,
Thanks for clarifying my understanding and for a very clear expaination of stuff arund it.
I would agree with you and would be happy to contribute in any way possible. I would modify the code and test as you suggested to fix the problem.

Hi @julz,
As you said, removing the link /var/run/netns/$PID after ip netns exec usage would solve the problem and this fix should be ok until the shell script is replaced by go code.
Now coming to the testcase, ip netns list will not list the namespace if there is no fd in /var/run/netns. i am not finding any other method to list network namespaces which are created during clone. so i have modified test case to only verify after container delete that no network namespace is leaked.
Can you plz review and see if it is appropriate.

Thanks @shashidharatd!


design: Upgrade the UI

#8  fixed
I have made the Ui good than previous one and additionally I have added CopyLink feature so we can  invite the user to use our tool or learn more about it.

@Aabiskar-dhenga can you add a video or screenshots showing the changes.

wait i will do that

here it is

@Aabiskar-dhenga, the previous one was looking better, just change the colour code  to the previous and send a screenshot.

@Aabiskar-dhenga, the previous one was looking better, just change the colour code to the previous and send a screenshot.

ok

seee hereee :

@Aabiskar-dhenga  the changes have been made, so closing your pr for now. Star the repo and keep and eye on the new issues.
Dont mind buddy but ui was not appealing much, sorry for not merging your pr


[Wiki] Add article about Windows indexing options for PT Run

📝 Provide a description of the new feature
We should have an article in the Wiki (chapter: PT Run) that describes (including an image) how an user has to adjust indexing options to search files on other drives too.
Btw: This article then can be referenced in issues.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

@saahmedm this is a good idea as well :)

@saahmedm did you ever get this done?

here's the page: https://github.com/microsoft/PowerToys/wiki/Triaging-Issue-Backlog

So


The path ${OSH_PATH}/tools/kubeadm-aio/assets/opt/rbac/dev.yaml does not exsit.

the path ${OSH_PATH}/tools/kubeadm-aio/assets/opt/rbac/dev.yaml does not exsit.
error:
~/contrail-helm-deployer$ kubectl replace -f ${OSH_PATH}/tools/kubeadm-aio/assets/opt/rbac/dev.yaml
error: the path "/home/helm/openstack-helm/tools/kubeadm-aio/assets/opt/rbac/dev.yaml" does not exist

fixed now


Update cafewelcome

Should mostly work okay. May need some adjustments in the future for font size per length on user names and guild names.

Thank you for your time on this. I'm really gonna learn alot


Add caseSensitive to Table constructor to schema field names validation

Base on the bug reported by @paulboony  at https://github.com/frictionlessdata/tableschema-js/issues/185 I implemented the option to load a table passing an argument caseSensitive, that will make the check between the table data header names and the field names on the schema case sensitive. For now I left the default as case sensitive, because this is the current tableschema-js behavior.
You can now load a schema for a table not case sensitively as:
const table = await Table.load('data.csv', { schema: 'schema.json', caseSensitive: false })

Thank, @aivuk. Can you also add this new caseSensitive option to index.d.ts for typescript support, please? https://github.com/frictionlessdata/tableschema-js/blob/37f02247e0ce35f382ad815121bd64877e9718af/index.d.ts#L16

@aivuk Who can review this PR to move this along?

@aivuk Who can review this PR to move this along?

@roll is the one, but this week can be a bit complicate for him to do it.


Access request for suchismith1993

NOTE: THIS ISSUE SHOULD NOT BE CLOSED BY THE ORIGINATOR IF ACCESS IS GRANTED.
When the access is no longer needed please add a comment and a member
of the infrastructure team will revoke it and close the issue.
Required access level (Delete as appropriate). Note that you should only
request the minimum level that is required to solve your problem

[ ] Non-privileged
[ ] jenkins user
[ ] root/Administrative
[ ] other (Please specify):

System for which access is needed:
Please explain why you need this access including whether it is a temporary or permanent request:
Need to debug AIX builds for Adoptium

@sxa  How i can install git here ? Not familiar with package installation on AIX.

git is already on the machine in the standard location when installing things from the IBM toolkit - /opt/freeware/bin

Hi Stewart
Can i get root access to the machine.
Would need to increase the ulimit which would be required to run the temurin builds.
[SUCCESS] Executing local file at /home/suchiroy/temurin-build/build-farm/platform-specific-configurations/aix.sh
WARNING: MAXIMUM USER FILE SIZE (ulimit -n) IS 1048575 (<2097150) - GIT MAY HAVE PROBLEMS CLONING
Using default /tmp for temporary files as /ramdisk0/build/tmp does not exist

Need to increase maximum size beyond 2097150

Can i get root access to the machine.

Done


Support use of custom YOLO weights for a standard Docker installation

For v2.0.0 release we support this only for a non-docker install of Opendatacam, in order to support it for a standard docker install of opendatacam we should:

Add a way to mount custom .cfg .weights .data inside the docker container darknet folder when starting the docker container: https://github.com/opendatacam/opendatacam/blob/master/docker/run-jetson/run-docker.sh ( as we do for the opendatacam_videos/ folder )

Document how to update the config.json file accordingly

It is not hard but it adds too much overhead right now for v2 release for benefits.. People using custom YOLO weights should be able to install opendatacam without docker

why not to have a folder like configs and have there the config.json and all the yolo files and if the files exist then copy them to docker container?

Yes, we will do that, it is indeed pretty simple, but do not have time to to it properly for v2 release.
I want to simplify a bit this mess of install that pulls lots of stuff to something a bit more understandable

OK this is finally documented: https://github.com/opendatacam/opendatacam/blob/development/documentation/CONFIG.md#use-custom-neural-network-weights


Databricks name length restriction not correct

Restriction of length of Databricks is incorrect.
Azure Portal says max length is 30 while page says its 64

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 374ec8eb-64d4-3766-5c5e-39137a262ffd
Version Independent ID: 3abeeae9-6854-651a-483c-a1673eea9f9f
Content: Resource naming restrictions - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/resource-name-rules.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@YvesMentens
Thanks for your feedback! We will investigate and update as appropriate.

@YvesMentens - thanks for the feedback. The portal is incorrectly enforcing the limit of 30 characters. The issue has been forwarded to the portal team. When using APIs, the name can be 64 characters.
#please-close


Can Swift invoke C++ library directly?

Motivation

I know Swift can invoke C directly, but when invoked C++ library, it always need bridge head file using Objective-C, I know someone is doing this job, but two years was passed, I reviewed the blog about the release , cannot find the feature .
Solution

Alternatives considered

Hey Marc, maybe I don't understand some subtlety in your question but according to swift.org using C++ libraries is supported: https://swift.org/documentation/cxx-interop/

@icanzilb  I know  in order for Swift code to consume C++ code we must create an Objective-C wrapper or bridging code earlier. You mean it can support C++ libraries without bridge header......


gap between toolbar and grid in edit data editor

Azure Data Studio Version:
latest master
Steps to Reproduce:
open edit data for any table

there shouldn't be a huge gap between the toolbar and grid

no longer reproducible


Parse drag-dropped folders and subfolders in Chrome

This change allows resumable to parse through folders that are dragged and dropped into the drop zone if the browser supports it (just Chrome for now).  It still handles them in pretty much the usual fashion for other browsers.
In the interest of full disclosure, the general algorithm for this was found in a blog post at http://code.flickr.net/2012/12/10/drag-n-drop/
In addition to simply parsing the directories, I also add a property of .relativePath to files found inside a folder and use that to set the resumableFile.relativePath if file.webkitRelativePath is nothing.

Looks great -- but would you be able to add a few more lines of comments to the code? Mainly notes about the method for folder support and about the current Chrome-only status?

I added several more comments as well as function headers (I can remove these if you think they add too much clutter).
I also did more testing with more complicated sub folder structures and fixed a couple of bugs I found.

Awesome! Merging with thanks!


Streams are no longer closed by terminal operations

This is no longer true, according to H6 migration guide, so undocument it.
@sebersole is this right?

Folks, is this change correct? Because according to what I understand from the migration guide, what's currently written in the docs is wrong and has changed. But I don't know how any of this stuff works.

Yeah, the docs need to be updated. The change, to not automatically close the underlying resources on terminal operations, was done on purpose as you figured through the migration guide.

Sorry, I only asking whether the change to the docs proposed here was correct.
I wasn't questioning the underlying change.

I'd say the doc change is correct, but I prefer deleting stuff instead of commenting it out.

Fine.


Fix: Releasing request twice

closes #1006

Codecov Report

Merging #1046 (7ee5068) into main (9f2fa84) will increase coverage by 0.98%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1046      +/-   ##
==========================================
+ Coverage   57.01%   57.99%   +0.98%
==========================================
  Files          73       73
  Lines        2261     2445     +184
  Branches       62       66       +4
==========================================
+ Hits         1289     1418     +129
- Misses        972     1027      +55

Impacted Files
Coverage Δ

...la/zhttp/service/client/ClientInboundHandler.scala
71.42% <100.00%> (-14.29%)
:arrow_down:

...io-http/src/main/scala/zhttp/service/Handler.scala
72.72% <0.00%> (-7.28%)
:arrow_down:

zio-http/src/main/scala/zhttp/service/Server.scala
44.08% <0.00%> (-2.07%)
:arrow_down:

...http/service/server/ServerChannelInitializer.scala
92.85% <0.00%> (-0.90%)
:arrow_down:

zio-http/src/main/scala/zhttp/http/Http.scala
73.17% <0.00%> (-0.88%)
:arrow_down:

...erver/content/handlers/ServerResponseHandler.scala
97.61% <0.00%> (+5.61%)
:arrow_up:

Continue to review full report at Codecov.

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


Tidy init.py by using itertools.product

Previously we used a naive implementation of itertools.product to
generate all possible statepoints to examine.
However, there were concerns with that setup since a lot of our
statepoint variables depended on other statepoint variables, so a simple
product would not work properly. This was remedied by using dictionaries
to store this info based on other statepoint keys.
As @jennyfothergill pointed out, we can now use itertools.product again,
since the dictionary representation all use lists which are varaible
length based on the other statepoint information. Namely, the molecule
name and the simulation engine.

when you're at this, can you also change the "Trappe-UA" to "trappe-ua" (match with the name used in foyer Forcefield)? it makes the loading forcefield from by name a bit easier

Oh, and another thought--in case we want to use
signac view

we should change the statepoint waterSPC/E to waterSPCE. Otherwise we'll get this error:
Error: In order to use view, statepoints should not contain ['/', ' ', '*']

Great catches @daico007 and @jennyfothergill !
I will make those now

Ok I think i fixed all the issues. When i re-generated the statepoints, i had no warnings!


min-turnup: implement a phase 1 for GCE using deployment manager

https://cloud.google.com/deployment-manager/docs/

Closing this issue as min-turnup moved to the kubernetes-anywhere repo.


Initialize Memory Module with Space for Z-Machine Header

One of the first things that has to be provided as part of the Z-Machine memory is the header, which is the first 64 bytes of memory from a story file.
This much memory must be allocated right at the start. That amount of bytes must then be read in from the story file. If the first 64 bytes cannot be read in, that indicates a problem with the story file itself.

The implementation of this is fairly simple: allocating the first 64 bytes of the file read into memory. The idea here is that the memory module will have a pointer to its own state. That state will be updated by reading aspects into it.


How to declare another Maven repository?

Unfortunately, I did not find this point in the documentation. If this is not possible, please make it possible.

The MavenAdditionalRepositories MSBuild property should be available to add additional repository specifications to. The format of this property is a series of semicolon separated values. Each value is in the following pattern: {Id}={Url}. The ID of the central repository is 'central' inline with standard Maven convention.
Authentication information is not supported within the MSBuild files. But because we internally use the Maven Aether library for resolution, standard ~/.m2/settings.xml information should apply.
NuGet packages which rely on Maven packages do not include repository information, and thus it's inappropriate to publish a NuGet package that relies on artifacts outside of central on nuget.org.

Hi, have a question on that
This way it should be correct?
    <ItemGroup>
        <PackageReference Include="IKVM.Maven.Sdk" Version="1.4.1"/>

        <MavenReference Include="com.sumsub.sns:idensic-mobile-sdk" Version="1.23.1">
            <MavenAdditionalRepositories>sumsub=https://maven.sumsub.com/repository/maven-public/</MavenAdditionalRepositories>
        </MavenReference>
    </ItemGroup>


Setting to disable indicator icon if disconnected from VPN

Adds a new setting to disable the indicator icon when not connected to the VPN.
This makes it a bit easier for me to realize that the VPN is disabled, instead of using a greyed out icon which is, perhaps, a bit harder to distinguish from the connected icon for the untrained eyes.
Doesn't change defaults, so the disconnected icon is still show by default if the show-icon is enabled.
Another option would be to make this behavior default and avoid the extra setting. A personal preference I guess.

This LGTM but I'm away for a few days for the US Holiday, will test and merge as soon as I'm back at my desktop.
I think switching this behavior to default actually makes sense, it'd be more in line with the WiFi/Ethernet/BT indicators.

I just tested this and it doesn't seem to work on my machine, I'm not exactly sure why. Does it work for you?

I think it might be being overridden by the Display indicator icon setting, which is forcing the icon to visible even though your code is trying to hide it.

Thanks for the 👀, I'll have a closer look. It's working here, but Im a javascript n00b, so it's certainly possible I missed something.

Closed by https://github.com/Pobega/gnome-shell-extension-mullvad-indicator/pull/35


Enhancement/754 swap nvd3 for highcharts

Looks good, you'll need to merge in master and resolve conflicts though.
If the issue is in index.html, accept theirs or merge if you've made changes (outside of wiredep).


Change RawGestureDetector API to be better for strong mode Dart.

Fixes https://github.com/flutter/flutter/issues/7173

This seems like a good change, the code that uses raw gesture detectors is easier to read for it.
LGTM although Travis has found a test failure.

Fixed. Will check in on green.


fix: CSP problem in Safari

This fix: Refused to load blob because it appears in neither the child-src directive nor the default-src directive of the Content Security Policy:
Something went wrong...

The operation is insecure.
Stack trace
[native code]
https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:80:108229
https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:94:33533
e@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:94:33534
e@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:94:83796
https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:88:66420
https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:88:67371
Fa@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:64:70125
cl@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:64:96962
sl@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:64:96887
Zs@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:64:93917
Zs@[native code]
https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:64:45558
https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:72:4087
Yo@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:64:45504
Vo@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:64:45439
Gs@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:64:90702
enqueueSetState@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:64:49224
https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:56:1551
https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:88:66996
https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:22:2578
a@https://cdn.jsdelivr.net/npm/redoc/bundles/redoc.standalone.js:22:1422
promiseReactionJob@[native code]

ReDoc Version: 2.0.0-rc.45
Commit: aa53416d

This problem appears latest Safari

Merged, thanks!
Releasing to npm asap


Will updates be available?

a) Would you publish in github or wherever future updates?
b) is current version working ok with 1903?
(as website is down...)

a) I think you should ask @mingkuang-Chuyu
b) Yes

Closed temporarily, we will reopen again if have response.

Please goto #717


Is this library alive and maintIable?

@warting
Hi! Nice lib you have. Is this project neglected or I can rely on it?
Just checking.
Hope you answer asap. Sorry to messed up your issues here.

Hi, I'm using it myself in various apps and maintaining it due to lack of official simple APIs for requesting background location permissions.

Thanks!

So, I found the culprit of the but.
Adding this to manifest

@warting Any ideas how to fix this?


Can't make it work with the new changes in unrar library

I followed the instructions and downloaded the source from the RARLab Download page, I then ran make lib and make install-lib and of course pip install unrar, but when I run comictagger.py it gives a LookupError "Couldn't find path to unrar library".
Then I tried to install unrar with MacPorts sudo port install unrar with no changes.
What is the proper method to set UNRAR_LIB_PATH in the environment?
And should it point to the path where the binary is installed?

I noticed that make install-lib installs a file named libunrar.so in the path /usr/lib/ but unrarlib.py looks for a file named unrar (like the binary):
# find and load unrar library
unrarlib = None
if platform.system() == 'Windows':
### CUT
else:
    # assume unix
   ### CUT
    lib_path = lib_path or find_library("unrar")
    if lib_path:
        unrarlib = ctypes.cdll.LoadLibrary(lib_path)

if unrarlib is None:
    raise LookupError("Couldn't find path to unrar library.")

I think that find_library uses a platform specific search algorithm, even on linux the name unrar resolves to libunrar.so, don't know how does it on the mac. Try starting comictagger with:
  $ UNRAR_LIB_PATH=/usr/lib/libunrar.so comictagger.py

and see what it does.

Right, as @davide-romanini pointed out, find_library takes a name and automatically tries to find the library (in the expected paths, system dependent), as stated in the linked documentation. You can also force a specific path by setting the UNRAR_LIB_PATH env variable (as shown above).
So the real issue seems to be libunrar.so is not located in a path where dynamic libraries are being searched for.

According to the ctypes documentation find_library searches by prefixing lib in the given name and postfixing the proper extension for the os in use, that's .so for Linux and .dylib for OS X.
But the unrar makefile installs using the linux ext no matter what's the system being used.
I believe renaming my installed file to libunrar.dylib should be safe in this case.
Thanks for the tips!

Ok, so it seems more an issue for the unrar source makefile, that sadly isn't on github :-( I'll update the readme adding the tip, while thinking of a better way to package this stuff in a more practical way.

I noticed that requirements.txt is using -e git+https://github.com/matiasb/python-unrar.git@1010cf5f6fcf09a9b1fe7c958faf0167fafaa7d9#egg=unrar-master instead of the standard $ pip install unrar reported in the package page (which I used), why using the repository instead?

It was temporary, now it should point to last 0.3 version of unrar.
Il giorno 22/Feb/2015 14:33, "fcanc"<EMAIL_ADDRESS>ha scritto:

I noticed that requirements.txt is using -e git+
https://github.com/matiasb/python-unrar.git@1010cf5f6fcf09a9b1fe7c958faf0167fafaa7d9#egg=unrar-master
instead of the standard $ pip install unrar reported in the package page
https://pypi.python.org/pypi/unrar/ (which I used), why using the
repository instead?
—
Reply to this email directly or view it on GitHub
https://github.com/davide-romanini/comictagger/issues/72#issuecomment-75435607
.

Updated in 68030a102433035b6e72b0e573e62efcb75d07f0

I note that this is closed, but have just installed on Fedora and this error still seems present.  I installed libunrar using the instructions from python-unrar, and I now have libunrar.so in /usr/lib but comictagger can't find it.  If I specify the library in the command line comictagger works... is this still on the list to be fixed?

Mmh, I still run using the env variable in development. I think we shouldn't rely on a system level installation of the library, but decide a known place at build time and use it. I'd like to integrate the full compilation step in the various platform-specific build script but still didn't have much time for improvements in this area..

You can also do the follow command:
export UNRAR_LIB_PATH=/usr/local/bin/libunrar.so
(Can be: /usr/lib/libunrar.so  too, verify your path)
And after execute the Python File


Add listCollections as alias of getCollections

I can't seem to find any docs for this API. Can you show it to me?

@mikkopaderes Here it is:
https://github.com/googleapis/nodejs-firestore/blob/master/types/firestore.d.ts#L154-L170
As you can see, getCollections is marked as deprecated. The documentation is pretty disappointing.


Added upload progressbar to the LTI upload tool

Adding a simple uploadprogress to the upload form when uploading via LTI

This might just be me failing to resolve the conflicts properly, but I can't build the lti module with this PR.
[INFO] Failed to compile.
[INFO]
[INFO] ./src/components/Series.tsx
[INFO] Cannot find module: '/home/arnewilken/IdeaProjects/opencast9/modules/lti/node_modules/babel-preset-react-app/node_modules/@babel/runtime/helpers/esm/objectSpread2'. Make sure this package is installed.

@Arnei I fixed the merge conflicts and you should be able to build it now.

I talked to Arne and he was fine with the current state if it can't be easily changed. So I'm gonna go ahead and merge this. :)


make build now returns build errors

@sjezewski could you take a look at this when you have a chance

Minor bash feedback, otherwise

Also this is perfect timing, as this would've fixed a confusing pattern of CI failures I was just wrestling with.


Does a Docker container need to use the same exact libcuda version as the host's driver?

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: no
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.4.1
Python version: 3.7
Bazel version (if compiling from source): no
GCC/Compiler version (if compiling from source): no
CUDA/cuDNN version: libcuda reported version is: 450.142.0 kernel reported version is: 450.66.0
GPU model and memory: GeForce RTX 2080 SUPER

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
I'm trying to run an application that uses torch and tensorflow inside a docker container but I'm getting this error message:
"kernel version 450.66.0 does not match DSO version 450.142.0 -- cannot find working devices in this configuration"
The cuda-compat-11-0 version inside the container is 450.142.0 but the host driver version is 450.66.0.
As I can't find cuda-compat-11-0 version 450.66.0, I tried other versions around it but I got the same error.
I'm not able to change the Host driver, so my question is:
Do I really have to install the exact same version on the docker container in order to make it work, or am I doing something wrong?
Please help me understand this issue. Thanks in advance!
Describe the expected behavior
Contributing

Do you want to contribute a PR? (yes/no):
Briefly describe your candidate solution(if contributing):

Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

Hi @ricardofunke , Could you please look into answers of following similar issue.


Range of scanner desc of FixtureStore is different from other stores

In the implementation of Store for FixtureStore, the range of scanner is given by below codes:
let lower = lower_bound.as_ref().map_or(Bound::Unbounded, |v| {
    if !desc {
        Bound::Included(v)
    } else {
        Bound::Excluded(v)
    }
});
let upper = upper_bound.as_ref().map_or(Bound::Unbounded, |v| {
    if desc {
        Bound::Included(v)
    } else {
        Bound::Excluded(v)
    }
});

So with desc, it uses left open right close closure. However, BackwardScanner (used by SnapshotStore to implement scan method) scans key only lower than upper bound.
And in dag coprocessor, key was restricted lower than end of range, no matter desc or not.
if self.range.start > key || self.range.end <= key {
    set_panic_mark();
    panic!(
        "key: {} out of range, start: {}, end: {}",
        escape(&key),
        escape(self.range.get_start()),
        escape(self.range.get_end())
    );
}

Maybe we will never use dag coprocessor on FixtureStore, but keeping the range (especially the bound)  consistent with all stores is better and cleaner.

/cc @breeswish PTAL


AUTH-323: separate the cluster-distributed client-ca from the rootCA

This PR sets up multiple signers in order to match the OCP trust bundle described in https://github.com/openshift/api/blob/master/tls/docs/kube-apiserver Client Certificates/README.md#kube-apiserver-total-client-ca.
This, along with https://github.com/openshift/hypershift/pull/1831, changes of which are also included here, will cause the rootCA-signed certificates to no longer be trusted for client-certificate authentication towards the API.
This PR implements much of the changes proposed in https://github.com/openshift/enhancements/blob/master/enhancements/hypershift/trust-chain-separation.md.

Note that the EKUs of the aggregator and the admin client certs were wrong.

/test verify

/test e2e-aws
I dare say this is already starting to look quite ok. The log scraping wasn't 100% successful so I'm going to try to rerun the test and see if we can get a somewhat better insight.

good catch, I'll look into it

@csrwng very good catch, I have no idea how that happened! It should be all fixed now :+1:

/test e2e-aws

It seems that the e2e-aws got broken outside this PR

Yes we're working to fix it

/test e2e-aws

/retest-required
just to see if there is a pattern in the pods that suddenly started failing

/hold would also like to do an indepth review and ack before we merge

/unhold looks good
However would be good to get the list of delta new ones on this change
AKA:
new configmaps/secrets

/retest-required

/unhold
(removed in https://github.com/openshift/hypershift/pull/1837#issuecomment-1316280891)
I'll try to summarize the diff below, I hope I did not forget anything
delta:
ConfigMaps
- combined-ca
+ client-ca                       # a bundle of signers for cluster client cert verification
+ aggregator-client-ca            # a bundle of signers for kube API aggregation layer client cert verification
Secrets
+ kube-apiserver-to-kubelet-signer
+ kas-aggregator-client-signer
+ kube-scheduler-client
+ kube-controller-manager
+ system-admin-signer
- kas-admin-client
+ system-admin-client

/lgtm
/approve
/retest-required
(only expecting the cp upgrade test to fail)

/label tide/merge-method-squash

Verified that only the control plane upgrade test failed with crashing pods, otherwise everything passed
/override ci/prow/e2e-aws

/override ci/prow/e2e-aws


UI: Fix the style action button

Description
The button and the search part are different on the list view page

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
Before:

After:

How Has This Been Tested?

@blueorangutan ui

@utchoang a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4856 (SL-JID-49)

Did a quick test - lgtm.


Avoid problems with circular reference in object over responsive layout

This change avoid issues with circular reference in objects. A issue very common working with chartjs.

The only change I see on this PR is on a compiled file. Where the modified sources?

You have right, I am new and eager to contribute.
Sorry for my english too.
I will find the source and do the changes.
Thanks for your time.


[split layer] Initialize class member bugfix

Split layer has class member leading_helper_dim
which remains uninitialized and results in bugs
when setBatchSize() is called before initialization of the layer.
This patch fixes the bug.
Resolves #1279
Self evaluation:

Build test: [x]Passed [ ]Failed [ ]Skipped
Run test: [x]Passed [ ]Failed [ ]Skipped

Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>cc. @zhoonit

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1278. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

Wonder how it sneaked through the ci test

Wonder how it sneaked through the ci test

setBatchSize() is called with inference/train. The error only happens when the uninitialized is zero (which is rare) and setTensorDim() throws in that case.

Thank you for the fix :)


Ajustment to load outputs with same Ids saved

When some output is removed, the order of outputs affect correct render os connectors when flow is reloaded.

Hi @danieldvc
Thanks for PR.
Can you elaborate more on the problem that it corrects?
For example in node with 3 outputs.
Using:
/*
Node 13
output_1
output_2
output_3

*/
editor.removeNodeOutput(13,'output_2');

/*
When using the removeNodeOutput function the numbers are corrected
Node 13
output_1
output_2 // (output_3 is renamed)

*/

The export always exports in order, is it removing the output in another way?


Is there any function to change the C2WTS Account?

Details of the scenario you try and problem that is occurring:
I would like to change the Service Account for the Claims to Windows Token Service. Are there any plans to provide a functionality like this?
I think it could be accomplished like described here: How to reset the Claims to Windows Token Service account
The DSC configuration that is using the resource:
N/A
Version of the Operating System and PowerShell the DSC Target Node is running:
N/A
Version of the DSC module you're using:
1.6

There are now, I'll tag this so it's on our backlog and we'll see when someone can get to it. Thanks for reporting the idea!

I have some code that does this, just need to clean it up and write the tests. I'll try to have a PR ready next week.

Change included in PR #642