KeyUtilitiesRunner.java importRSAKey  reproting this error. Attirbutes being specified are imcomplete

Exception in thread "main" com.amazonaws.cloudhsm.jce.jni.exception.AttributeException: Attributes being specified are incomplete: Incomplete template
at com.amazonaws.cloudhsm.jce.jni.RsaPrivateKeyImportBuilder.do_importKey(Native Method)
at com.amazonaws.cloudhsm.jce.jni.RsaPrivateKeyImportBuilder.importKey(RsaPrivateKeyImportBuilder.java:35)
at com.amazonaws.cloudhsm.jce.provider.ImportKey.importRsaPrivateKey(ImportKey.java:168)
at com.amazonaws.cloudhsm.jce.provider.RsaKeyFactory.engineGeneratePrivate(RsaKeyFactory.java:153)
at java.security.KeyFactory.generatePrivate(KeyFactory.java:366)
at com.amazonaws.cloudhsm.examples.KeyUtilitiesRunner.importRsaKey(KeyUtilitiesRunner.java:268)
at com.amazonaws.cloudhsm.examples.KeyUtilitiesRunner.main(KeyUtilitiesRunner.java:147)

We didn't have enough information to investigate this issue. Our example code is building and executing on our side, so maybe the error is fixed. Please re-open if this is still a problem.


Change FROM,TO generics to FROM

Because TO is always Array[Byte]

For producer modifications already made.


Confirm risk is acceptable for release process

Release Process - RM needs to sign off this as he needs to accept the risk of the current

Advised Zane the below, waiting for a response before it is closed.
From: NEWSOME, Christian
Sent: 16 September 2019 10:35
To: OSMAN, Zain<EMAIL_ADDRESS>Cc: MACHEN, Richard<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Outstanding ORR items for F&E
Hi Zane,
Thanks for your patience on Friday, was really useful going through the detail and understanding what you need from us in order to satisfy the ORR process.
I think there were 3 outstanding items that I needed to come back to you on:

Feature list for CAB post Public Beta launch: After we have launched the next features to be developed and released will be:
a.	Shopping Basket – make improvements to the user experience and functionality
b.	Start Page  - improvements to the user experience
c.	Search & Sort – improvements to the functionality
Product Owner to accept the risk around the release process – Richard Machen (cc’ed) as the Product Owner has confirmed that the current release process described on Friday has an acceptable level of risk.
Confirm when testing is complete – I highlighted there was one outstanding bug, missing data items. Richard  has again confirmed that there is an acceptable level of risk associated to this bug and the F&E can go into Public Beta as is. FYI: it will be resolved before launch anyway.

Was there anything else you needed form me, have I missed anything?
If the above is ok, please can you confirm what the next steps are for the ORR process?
Best wishes,
Christian


[FEATURE] Remove Github / from User Rankings

Is this a unique feature?

[X] I have checked "open" AND "closed" issues and this is not a duplicate

Is your feature request related to a problem/unavailable functionality? Please describe.
After navigating to the User Rankings we notice that all users have a prefix GitHub /
Since we are using GitHub OAuth, all users will have this title.
I don't see the point of having the same prefix for all users. It would make for a much cleaner UI if this prefix is omitted.
Proposed Solution
When displaying that part of the card, we can simply truncate that part of the string, and display just the username, as is done in the Activity feed. (See screenshot below)
Screenshots
User Rankings page:

Activity Feed

Do you want to work on this issue?
No
If "yes" to above, please explain how you would technically implement this (issue will not be assigned if this is skipped)
NA

I would like to work on that.
There is a line that i just need to get rid of

Thank you for raising the issue. I would like to keep the prepended github, this was done as part of the design, because in the future we may have other sign in options. So i will close this issue for now


TestMain is unconditionally called with go test -run

Tracking issue so others are aware of this behavior. It's not necessarily a bug, but we might need document this and/or explicitly teach our e2e test framework about the -run flag.
Steps to reproduce:
$ git diff
diff --git a/pilot/pkg/proxy/envoy/v2/xds_test.go b/pilot/pkg/proxy/envoy/v2/xds_test.go
index 2f17ed556..625df42dd 100644
--- a/pilot/pkg/proxy/envoy/v2/xds_test.go
+++ b/pilot/pkg/proxy/envoy/v2/xds_test.go
@@ -415,6 +415,7 @@ func getLocalIP() string {
        return ""
 }
 func TestMain(m *testing.M) {
+       fmt.Println("TestMain called!")
        flag.Parse()
        defer func() {
                if testEnv != nil {

$ go test ./pilot/pkg/proxy/envoy/v2/xds_test.go -run foo -v
TestMain called!
testing: warning: no tests to run
PASS
ok      command-line-arguments  (cached) [no tests to run]

fyi @kuat

fyi @kyessenov

Closing since this is not actionable.


Update IntelliJ IDEA 2017.1 EAP to build 171.2272.14

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

I've also reverted #3124 and #3125 because the changes were made in wrong cask files.

@metyl What is the difference between EAP and EAP Next? They both link to the same dmg, in both Professional and Community Edition. To stay consistent with the naming for other JetBrains-related Casks, I'd prefer the naming without next.

@neutric please take a look at #2508.
IntelliJ IDEA has more than one EAP.

I see! That was not immediately obvious from https://www.jetbrains.com/idea/whatsnew/. On top of that, some of their other IDEs are moving the EAP page from Confluence to "next" pages on jetbrains.com. Apologies, I'll know for next time.


Add fixed-header to table on TableDetail view

fixed-header prop is not working on v-data-table

It turns out you need to set a height on the table in order for fixed-header to work. Here's a codepen illustrating that. I also tried "100vh" for the height value and I think that worked as well. We probably need to play around to figure out the right way to do this for TableDetail.

@waxlamp
It appears that adding height="calc( 100vh - 123px )" to our table works. The 123px comes from the height of the app-bar and the header of the table combined (64px + 59px).

Great! Feel free to open a PR with this change and let's see how it looks.


Add a pointer to the IG for error code 69

Information

JIRA story QPPCT-844.

Checklist

[ ] All JUnit tests pass (mvn clean verify).
[x] New unit tests written to cover new functionality.
[x] Added and updated JavaDocs for non-test classes and methods.
[x] No local design debt. Do you feel that something is "ugly" after your changes?
[x] Updated documentation (README.md, etc.) depending if the changes require it.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 ErrorCode.java#L72: Define a constant instead of duplicating this literal "Please see the Implementation Guide for information on the performance period here: " 3 times.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 ErrorCode.java#L72: Define a constant instead of duplicating this literal "Please see the Implementation Guide for information on the performance period here: " 3 times.

SonarQube analysis reported 3 issues

 3 major

Watch the comments in this conversation to review them.


Duplicate database entries caused by gene-gene-drug guidelines

should probably figure out how to deal with gene-gene-drug guidelines in general first

CPIC has guidelines for all combinations of phenotypes of both drugs
Annotation Server creates duplicate entries, one for each gene for each combination
Sheet data is only annotated to first entry
very likely to be missing in app

Closing since Annotation Server was deleted in #526


How to handle multiple configurations in multiple Service objects ?

Hi,
I have already read similar issues and answers but I have a very specific question regarding Service and its behaviour.
Documentation clearly says that it is better to share one instance of Service to get full benefits of Siesta.

you’ll want to ensure that all the observers of an API share a single instance.

Also configuring services outside constructors is not preferred as stated here http://bustoutsolutions.github.io/siesta/guide/configuration/

Don’t do this! You are creating an ever-growing list of configuration blocks, every one of which will run every time you touch a new resource.

There is also a very good sample project here proving all these correct. https://github.com/bustoutsolutions/siesta/tree/master/Examples/GithubBrowser
So I am trying to stick to these 2 rules in my implementations.
As you can see in GithubAPI.swift Service objects could get messy very quickly. In this example there are only 4-5 requests but the constructor is already too long IMO.
The scale of the project I am working on is much bigger than this so I would like to separate my Services like UserService.Swift PaymentService.Swift, otherwise my one and only Service will be extremely long when you think about all relative paths, custom transformers for parsing etc.
How can we achieve this without going against to those 2 rules ?
I can imagine something like BaseService just for headers or authentication configuration in init() and every subclass will do further service.configure or service.configureTransformer in their init(). This looks clean enough but I will lose the ability to share one and only service since I will have different instances from one shared BaseService and questions like setting auth token for all children are causing more problems.
If I go with singleton BaseService or just a Service then I will lose the flexibility of configuring outside init() in children since this is not suggested as documentation says. (or is this actually not that a big deal)
We are very new to Siesta but we loved it already ! Documentation is very good but maybe we missed the point of applying these kind of things using best practises.
Thanks !

Since there is no absolute right or wrong, I will just write down what kind of solution I have chosen.
Maybe someone with the same issue can benefit.
Somehow singletons are defined as semi-evil in the community. While most of the reasoning is true, there are still very valid cases to use singletons. If you are comfortable with this and Siesta's preferred way of doing this then the only problem is code localization, ease of maintenance, code readability etc.
I have a subclassed Service object which acts like one-and-only base for the same API. Because of configuration lifecycle, this class has to know how to act for all possible endpoints, parsing behaviours etc. beforehand.
I have managed to overcome this with Swift extensions. For now it looks both maintainable and clean.
class myApiClient: Service {
  static func sharedClient() -> myApiClient
   // ...
  private init() {
     generalConfiguration()
     userServiceConfiguration()
     paymentConfiguration()
     .....
  }
}

As seen in the example, singleton ApiClient knows how to configure itself according to the different feature sets. (user, payment etc. in our case). These feature specific configurations live in public extensions under protocols.
protocol ApiUserResourceDispatcher {
  func userData() -> Resource
}

typealias UserServiceClient = myApiClient
extension UserServiceClient: ApiUserResourceDispatcher {
  func userServiceConfiguration() {
    // User service based configuration comes here. Transformers, endpoints etc.
  }

  func userData () -> Resource {
    // return resource to be observed
  }
}

This setup allows me to separate feature based needs without losing one central Service object and polluting the same class.
Any external resource can basically process this data:
UserServiceClient.sharedClient().userData().addObserver .....

Behind the scenes it is only one myApiClient singleton but external resources only reach it via public extensions.
I am not sure if this solution will be valid for complex needs in the future but wanted to share as an alternative.
Siesta is very powerful but it lacks complex architectural examples like this one. Example app is also very clear but again uses only basic MVC approach.
Thanks for creating such a great library !

@erenkabakci, I’d say your solution is a good one if the problem is that your service API surface is getting too large. You’ve managed to keep only a single Service instance per API, but (1) split initialization code into multiple files and (2) not expose all those methods at once. Clever!
I’m not sure the typealias is buying you anything. If you define an extension on a typealias, it also applies to the original type:
class Foo { }

protocol Bar {
  func bar()
}

typealias FooBar = Foo
extension FooBar: Bar {  // extending FooBar, not Foo
  func bar() { }
}

let f = Foo()  // f is a Foo and not a FooBar, but...
f.bar()        // ...this still compiles

I may well be missing something about your approach, but I think you could remove one layer of indirection by keeping your underlying Service subclass internal to an API module…
internal class MyApiClient: Service {
  // Notice that static let is the Swift-preferred way to create singletons.
  // (Unlike Java, this _does_ guarantee unique initialization, even across threads.)
  static let instance = MyApiClient()

  override init() {
    super.init()
    generalConfiguration()
    userServiceConfiguration()
    paymentConfiguration()
    //.....
  }
}

…then adding conformance to a public protocol:
public protocol UserServiceClient {
  func userData() -> Resource
}

extension MyApiClient: UserServiceClient {
  func userServiceConfiguration() { … }
  func userData () -> Resource { … }
}

…and publicly exposing the same singleton via different public protocols:
// Protocols don’t (yet) allow static members, alas,
// so this needs to be a free global function
public func userServiceClient() -> UserServiceClient {
  return MyApiClient.instance
}

(Or just keep things simple and make it a variable instead of a function:)
public let userServiceClient: UserServiceClient = MyApiClient.instance

(Closing this for bookkeeping purposes, but feel free to continue the conversation.)

Hey !
Coming back after a long time. Sorry :) Thanks for the detailed reply and suggestions. I applied what you also suggested.
The only idea behind the typealias was to keep code clean in a way that I define different domains. As you said they already point to the same class anyways. The consumer of the API only knows about the typealias not the hidden service behind. That was just for accessor convenience.


Possible bug in Account.setOrders?

I was using the example scripts, and when trying to use the setOrders method, it populates an empty container. Specifically, Order.class == item.getClass() will return false and never populate newOrders.
public Account setOrders(Collection<?> orders) {
        ArrayList<Order> newOrders = new ArrayList<Order>(orders.size());
        orders.forEach((item) -> {
            if (Order.class == item.getClass())
            {
                newOrders.add((Order) item);
            }
        });
        this.orders = newOrders;
        return this;

Solution could be to replace
 if (Order.class == item.getClass())

with
if (item instanceof Order)

Thanks for identifying this issue -- it will be fixed in the next release of the Java implementation.

This issue is now resolved.


bts prediction website is down

The Singlearity-BTS-prediction page website is down, no way to export prediction details.

It's all star break... my bad


bugfix related to mutex

Running video_test.py, I have faced with a Segfault (python2) and "Attempt to unlock mutex that was not locked" (python3). After fix, video_test.py work on both python versions.

I can confirm that this fixed video_test.py for me and I was able to run the code. (Python 3.5)

Thank you @Hrehory and @KhaledSharif and sorry for the delay
BTW. I read a while ago your CNN backpropagation derivation and it helped me a lot.  Again, thank you :)


time:format::parse::ParseResult is private ? how to use it

for this code :
fn parser_time() -> ParseResult <Time>{
        let hour = "12";
        let minute = "03";
        let second = "56";
        let format = format!("{}:{}:{}", hour, minute, second);
        let time = Time::parse(format.as_str(), "%T")?;
        time
    }

I just want  import time:format::parse::ParseResult ,but find it's private ?
how can I use ParseResult ?

The ParseResult<T> is just to avoid typing out Result<T, ParseError> in tons of places internally. There are a few options available to you:

Use Result<T, ParseError>
Define an identical alias (type ParseResult<T> = Result<T, ParseError>)
Use time::Result<T>, which encompasses any error from the time crate.

@jhpratt tks


Forking or making a degoogled version?

I love the idea of this app and the fact that you've open-sourced it. Unfortunately, you haven't picked a software license, so it's uncertain whether forking and modifying it is allowed. Would you consider either clarifying that, or making a version without the Google trackers and dependencies (or allowing others to make one)?

I've set the license to MIT.


WIP: Test with cert-manager 1.7

Just testing whether the CAS issuer E2E tests will pass with cert-manager 1.7 as a way of kicking the tires before releasing CM 1.7 tomorrow.

E2E tests failed:
• Failure [0.008 seconds]
[jetstack google-cas-issuer] issuers
/home/runner/work/google-cas-issuer/google-cas-issuer/test/e2e/framework/framework.go:82
  Tests ClusterIssuer functionality [It]
  /home/runner/work/google-cas-issuer/google-cas-issuer/test/e2e/suite/issuers/issuers.go:162

  Unexpected error:
      <*errors.errorString | 0xc0007f0e90>: {
          s: "malformed secret key: separator '1' at invalid position: pos=-1, len=0",
      }
      malformed secret key: separator '1' at invalid position: pos=-1, len=0
  occurred

  /home/runner/work/google-cas-issuer/google-cas-issuer/test/e2e/suite/issuers/issuers.go:166

https://github.com/jetstack/google-cas-issuer/runs/4943626523?check_suite_focus=true#step:5:786

@jakexks explained that this is because the PR is from a fork which means that it does not have access to the CI secrets.


Value appears to not be binding properly in compose

https://github.com/PWKad/skeleton-navigation
You see that welcome.html composes a modal and passes in a showing property which should be bound two-way between the two.  What I have noticed -

If I bind to the value of false (a proper boolean) the value is definitely only one-way, unless I use it inside of a repeater.
If I bind to a random string value such as 'blue' and test against that on the modal's show.bind I get an undefined is not a function error, but stepping through the debugger I can't figure out where it is being thrown.

Ok. I believe one issue was in the framework. I just pushed a fix for that. But the other issue is in your code. You can't use compose to compose a custom element. You use that to compose plain view models. Your bug is coming from that. Remove the metadata and the error will go away.


Yell about TypeScript errors more aggressively

Fixes https://github.com/workbenchapp/solana-workbench/issues/75

lets see what docker build . does for me :)

ok, succeeds on local new clone - so its something-something out of sync (DEFER fixing that)

ok, so the expected effect is that the npm exec tsc errors will now also be shown in npm start - no change to npm run lint.
Hopefully there's a way to make them also surface in npm run build (it doesn't seem to happen for me atm)
LGTM


First step in updating dependencies (to Django 1.8), more-complete test coverage, some refactoring

This gigantic set of changes should help set us down the road to having long-outdated dependencies updated. The goal is to have fully updated dependencies (to Django 1.11) and move to Python 3 by 2020. Then we'll work on supporting Django 2.
Merging this into master will create release 1.4.
Django 1.8 and More-recent Dependencies
The supported version of Django is now 1.8, from 1.7. Other dependencies have been updated as far as they can go while still supporting Django 1.8.
Tests, Tests, and More Tests
To ensure the dependency-update process didn't break anything, we've added near-comprehensive test coverage; not necessarily strict unit tests, but tests that at least make sure to touch all of the major end-user-facing functions. The full test suite currently runs ~2300 individual tests. This is the main reason this update took nearly a year—with tests now in place, future dependency updates should be much faster and easier.
Tests were particularly challenging to write due to this system's dependence on a legacy vendor database (Sierra) plus Solr, which doesn't have any existing test-data-generation modules equivalent to model-mommy. Test data and fixtures are included to simulate data flow from Sierra (via a test postgreSQL Sierra database, including fixtures exported from our live catalog) into Solr. I've built modules for generating Solr test data a la model-mommy (utils.test_helpers.solr_factories and utils.test_helpers.solr_test_profiles) and added some helper factories for generating objects that work well as pytest fixtures to clean up Solr test data after each test or after each pytest module, depending on what's needed. This has led to a somewhat more complex test infrastructure than I really wanted, but it works.
Also, the Sierra DB tests that were originally meant to be run via the normal Django test runner have been moved to pytest. This addresses issue #40.
Changes to Sierra Models
Django 1.8 made some changes to models that broke some of the workarounds we'd employed, e.g., to accommodate the lack of single primary keys in some Sierra tables and Django's lack of support for composite keys.  This improves models in the following ways.

Adds base.fields.VirtualCompField — a virtual composite field that works as a proper PK for Sierra models. Notably, it does NOT work in relationships as a foreign key, but the Sierra models don't need to employ it that way.

Adds base.models.ModelWithAttachedName base class for Sierra Property or Type models that have an associated PropertyName or TypeName table containing names or labels for a particular property by language, linked to the IIILanguage table. Previously it was assumed these labels always used the default language, but this base class implements support for multiple languages. A new setting has been added (III_LANGUAGE_CODE) to define the primary language, but the class allows you to request a label using a different language, if it's available in your system.

ForeignKey relations that had a unique=True property have been converted to OneToOne relationship types.

New manage.py Command for Creating APIUsers
Previously, in order to create new APIUsers, you had to use the Python shell and run Python commands manually. This adds the importapiusers management command via the api app to allow you to import a CSV file to generate new APIUsers from the command line.
Refactored Code
This set of changes contains a LOT of refactored code to help break things into more granular units to make them more testable. Although I wasn't really aiming to do consistently granular unit tests, in some cases the methods or functions I wrote originally were awful and needed to be refactored.
Particularly, all exporters have been completely refactored. I've added several new types of base classes for helping compose complex export workflows.
Bug Fixes
There are some fixes for various bugs or issues that came to light while writing tests, particularly surrounding API behavior.

Using API filters that used the utils.solr.Queryset exclude method now work correctly. Previously, in certain circumstances, they would lead to default View querysets losing their default filters.

API filter operators such as gt, gte, lt, etc. now handle queries against string fields that contain spaces. Previously these filters were not escaping the spaces correctly in the underlying Solr query, which led to errors.

Incorrect syntax for API filters often led to 500 server errors if/when Solr raised an error because it couldn't parse the underlying query (which was not useful or informative for end users). Now incorrect API filter syntax raises a proper 400 error with a message explaining the issue.

API filters using the in and range operators can now escape or quote commas to include them as part of a data value. Previously commas were only used as delimiters in the query argument.

Shelflistitem manifests are now created/updated/refreshed for the correct item locations whenever any exporter that utilizes the shelflistitem Haystack index runs. The list of item locations needing a shelflistitem manifest refresh is stored and tracked as items are indexed, whether it's an ItemsToSolr, BibsAndAttachedToSolr, or other type of exporter. (Which addresses #16.)

BibsDownloadMarc Exporter Deprecation

The exporter.basic_exporters.BibsDownloadMarc exporter is now deprecated. All of the Solrmarc-related conversion logic has been moved from exporters down into a lower-level custom Solr backend for Haystack. A separate exporter that converts bibs to MARC and saves them to the filesystem is no longer needed.

Argh. While looking over the updates in this branch already deployed to production, I realized I made an oversight in the shelflist.views.FirstItemPerLocationList API view. In refactoring the api.simpleviews.SimpleGetMixin, I broke what was a monolithic method paginate into several sub-methods. I updated all of the views in the api app (including api.views.FirstItemPerLocationList), but by the time I was adding tests to the shelflist app I had forgotten I still needed to make this change to the overriding version in the shelflist app. Since that class is a subclass of the api version, it doesn't technically generate any errors--it's just missing the extensions that are added in the shelflist app, which means it doesn't work when the Inventory App tries to pull data (specifically a shelflist rowNumber) from that API resource.
Before merging this PR I'm going to go back now and add a test for the shelflist version of this resource that tests to make sure the added fields are there, and then fix the problem. It will take a little while, as I also need to merge the changes into bl-alpha-solrmarc and redeploy to staging to make sure the problem is fixed.


Chunking algorithm should consider actual time of current day

The algorithm should push tasks to other days if there isn't enough time in the current day to complete them.

I actually don't want to do this. There are times where I'll be working and have to go back and complete tasks in retrospect. This isn't necessary and may harm user experience.


Hpctestlib build both gpu dgemm+sgemm executables

Motivation: We have a bunch of RTX6000 devices at our site, which have a large difference in float vs double performance. For others like V100, P100 the TF/s difference is roughly 2x.
The changes to get the sgemm executable compiled:

template the dgemm gpu test code to allow execution of both Dgemm and Sgemm.
the makefiles are modified to define the codepaths through defines (float or double) and produce 2 executables

Note: I was not able to test the makefile.hip , so at this point I'm just assuming it will work
Question: if this is to be accepted, should the 'dgemm' directory be renamed, along with the Dgemm base test?

Can I test this patch?

ok to test

Codecov Report

Merging #2372 (5a4d680) into master (eddf0b2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2372   +/-   ##
=======================================
  Coverage   86.14%   86.14%
=======================================
  Files          56       56
  Lines       10225    10225
=======================================
  Hits         8808     8808
  Misses       1417     1417

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 eddf0b2...5a4d680. Read the comment docs.


Provide a mean to reproduce benchmarks results

Hello,
I am the author of criteo/cassandra_exporter and I would like to be able to reproduce your benchmarks in order to understand where are coming from the differences in performance from the other exporters you compare.
On my side, even on a pretty loaded cluster with a lot of keyspaces/tables the scraping time does not take more than 9sec (the machines have big cpus). But even while, when I switched from jmx_exporter, I haven't noticed a huge performance drop regarding the scrapping time. So I am a bit concerned on how you end-up with those results.
Can you please provide a mean to reproduce your benchmarks and the config you are running them on ?
Thanks in advance :)

Hi,
Thanks for the quick reply :)
I will look into that later in the week and will keep you posted.
As a side note, while performance is nice, you should warn/advertise the downside of running the exporter as an agent, most notably:

You have to restart your cluster if you want to upgrade the exporter plugin (may not be an issue if you are on kubernetes)
You are sharing the same jvm/heap than cassandra itself, so requesting too frequently the endpoint may result in triggering GC that will cause Cassandra to pause

Also if you want to improve further your performance, you can look to add gzip support for you http server, it make a big difference.
https://github.com/prometheus/client_java/blob/master/simpleclient_httpserver/src/main/java/io/prometheus/client/exporter/HTTPServer.java#L71

Hi back,
So indeed my exporter was way slower with a lot of tables.

Thanks for the suggestions of notes/warnings about running an exporter as an agent. I'll consider adding them to the README.

Also if you want to improve further your performance, you can look to add gzip support for you http server, it make a big difference.

GZip and Deflate is already supported -- Netty's HttpContentCompressor is part of the pipeline.
For example, the following request returns GZip encoded content which is successfully decompressed with gunzip:
curl -H "Accept-Encoding: gzip" localhost:29600/metrics | gunzip

... are my calls to mbean.getAttributes in order for the exporter to be able to not export them.

Yes, getAttributes is one of the slowest JMX calls in my experience.

Ok for gzip, I should have missed it :)
Good luck


ModelCheckpoint called before validation

When I set both model checkpoint and validation to happen mid-epoch (at the same interval), it seems that checkpoint is done before validation. Looks like checkpoint happens in the advance function of TraininingEpochLoop
https://github.com/PyTorchLightning/pytorch-lightning/blob/f79d75d4b5e50eb3e37073606eba5ca10d48c99a/pytorch_lightning/loops/epoch/training_epoch_loop.py#L221
whereas validation happens in on_advance_end
https://github.com/PyTorchLightning/pytorch-lightning/blob/f79d75d4b5e50eb3e37073606eba5ca10d48c99a/pytorch_lightning/loops/epoch/training_epoch_loop.py#L245
Is this expected? Is there a way to specify the same time interval but do validation first, so that the checkpoint (at least its file name) reports the correct metrics?

Hello
See the argument save_on_train_epoch_end in the model checkpoint docs. Try to set it to false, save_on_train_epoch_end=False.

I did. I have two ModelCheckpoint callbacks, one for end-of-epoch checkpoints (with save_on_train_epoch_end=True), and one for mid-epoch checkpoints (with save_on_train_epoch_end=False and every_n_train_steps set to the validation interval). The checkpoint in question is the second one, which seems to be called before mid-epoch validation.

hey @ZhaofengWu for the second one you don't need to set the every_n_train_steps because by default checkpoint callback is called after each validation loop, so setting save_on_train_epoch_end=False would do the job.

Thanks! This seems to work for me. And actually I lied -- I didn't set save_on_train_epoch_end for the second checkpoint callback. I thought it defaults to False but apparently it defaults to None. Anyway, I guess the original behavior that I described is slightly unintuitive, but it's good enough for me that there is a configuration of flags that works.


Add missing import statements.

We recently added flake8 to lint for these kinds of errors.
The config for flake8 will be added in PR #4798 .

R: @aaltay

CC: @cclauss

LGTM


/"What are OpenAI Codex and GitHub Copilot?": glossary item underlining bug

https://redesign.aprillion.workers.dev/questions/6628/What-are-OpenAI-Codex-and-GitHub-Copilot

what's this issue with this?

The words "Language Model" seem to be doubly underlined. If I were to guess, the issue is that both "Large language models" and "language models" are in the glossary, we want the longest hit only to be underlined


fixed-icons-size

I've take a look on editor, and find what icons very big. So this little fix for this.

Thank you for taking your time to submit a PR 👍 However i do not think we should do this. We had uniform icon sizes previously. It breaks spectacularly in big scenes where many of such icons are present, especially when objects are close to one another. Could you make a screenshot without a fix? I wonder how big they are that they prompted a fix.
Icons have other problems though. In 2D mode they are actually quite small and panning skews them.

Without fixing size, icons looks like this

Maybe Editor should look at DPI here?

@MonkeyFirst whats your screen resolution?

4К but I set 150% scale in win10 settings, without this scale all looks very smallest on screen.

@MonkeyFirst could you test latest master and see if issue is resolved?

sure, here is picture

I think it's looks the same

Could you select light/camera? It is hard to tell how far they are from editor camera. Maybe you are very close to them..? Saying this because i tested my patch on wife's PC which also has 4k monitor with extra scaling and icons looked ok to me.

Extra scaling do not affect on veiwport's stuff at all, only on editor's UI.
here is a new picture with selected light

I am deferring fix for this for bit later. I will be working on HDPI handling in imgui and that is pretty closely tied to this issue. Once HDPI support is worked out it will be clear how we can tackle this issue.


[pwm,dv] Remove lots of dead code from the environment and do some tidying

This builds on #24929, which should be merged first. Only the last 5 commits are unique to this PR:

a379082dec [pwm,dv] Remove set_reg_en from pwm_base_vseq
ebc2609c82 [pwm,dv] Remove duration_cycles from the vseqs
870fb50c98 [pwm,dv] Remove get_pwm_mode and pwm_mode_e from pwm_env_pkg
40b73b899d [pwm,dv] Rewrite pwm_env_cfg using out-of-block declarations
d267b5ca87 [pwm,dv] Rewrite pwm_scoreboard using out-of-block declarations

Thanks for the review, @hcallahan-lowrisc. I've just force-pushed with your proposed comment change and a final commit that re-indents the scoreboard task that was a bit of a mess!


Decide about final backend Framework

I have heard that Django is also popular and its language is python. You might want to consider.

Some further info in regards to this:

In terms of Backend, I suggest using .net Core because it brings frameworks for everything we need (API controllers, database, security authentication etc.) and it's very easy to host this app on a cloud provider like Azure. I know that Siemens themselves heavily use Azure and even the API that we got to work with is hosted on Azure.

@MartinDuersch

For backend, I prefer to remain on JavaScript
@gandompm


[feat] 재료 리스트 화면에 단위 가격 추가하기

From heuristic,
Major, i think it is important to user showing the unit cost for each items on the main list.

구현된것같네요


Add a Flutter command that builds an APK using a local build of the e…

…ngine
Example:
cd flutter/examples/stocks
flutter --engine-src-path /path/to/engine/src apk -o Stocks.apk -m apk/AndroidManifest.xml

LGTM.  Note: Travis is mad.

LGTM, just some minor nits.


fix(wallet): Removing notice about creating new wallet

:tada: This PR is included in version 3.1.9 :tada:
Your semantic-release bot :package::rocket:


fix(cli): docs errors

fix some bugs in the cli section

Hi @heappynd, please click here to fix ci error.

the CI error has been fixed


Inline stem macros inside AsciiDoc table cells are generated without considering to_dir

Steps to Reproduce
sample.adoc
based on sample.adoc
= Precompiled Math
:math:
:stem: latexmath

== Equations in normal blocks

[latexmath]
++++
k_{n+1} = n^2 + k_n^2 - k_{n-1}
++++

Some useful text! Formula for quadratic root:

[stem]
++++
x = \frac{-b \pm \sqrt{b^2 - 4ac}}{2a}
++++

Inline equation works too! latexmath:[a^2+b^2=c^2]. Or as stem
stem:[a^2+b^2=c^2]. Pretty nice, huh?

== Equations in table cells

Equations in asciidoc style table cells work, too!

[%header]
|===
| Demo | Contents
| Inline Equation in *Asciidoc* Cells
a|

This is an *inline* equation: latexmath:[E=m \cdot c^2].

| Block Equation in *Asciidoc* Cells
a| The following is a stem block:
[stem]
++++
a^2+b^2=c^2+d^2
++++

|===

asciidoctor invocation
pwd is /doc
asciidoctor  --destination-dir=/doc/build -a imagesdir=images -r asciidoctor-mathematical /doc/sample.adoc

Expected Result
All generated images should got into /doc/build/images
Actual Result
$ find ./ -name 'stem-*'
./images/stem-e21aaf56997f76dcc4584ad75fd32494.png
./images/stem-f5419604efe38ee8591c30c2a37fe800.png
./build/images/stem-560f2ca395ac37caca2a4729e62691d2.png
./build/images/stem-e1affc0a43f89ae2da953b789d29e42c.png
./build/images/stem-0b241139835e83278d5b9e608a543ce0.png

However, there are relative paths to images in the generated HTML for all generated images:
 $ grep 'stem-' sample.html

Inline equation works too! . Or as stem
. Pretty nice, huh?

This is an inline equation: .

Remarks
If I remove the a attribute from the table cell to test with non-adoc cells, asciidoctor fails with:
asciidoctor: FAILED: /doc/sample.adoc: Failed to load AsciiDoc document - undefined method `lines=' for #<Asciidoctor::Table::Cell:0x0000564584ebe888>
Did you mean?  lines
               lineno
  Use --trace for backtrace

This is bug #73?

I've noticed that the behavior is like expected if using asciidoctor-pdf instead of asciidoctor.

Which version is used in this issue?

asciidoctor-2.0.10
asciidoctor-pdf-1.5.3
asciidoctor-mathematical-0.3.1

Is there any progress, this also bothers me


serverengine v2.0.0 breaks permission changing on linux

Hello,
In looking to start fluentd, which uses serverengine, we were getting an EPERM error when trying to change privileges for the user/group running the fluentd agent.
https://github.com/fluent/serverengine/blob/4f15a3a3ecfe93ccb0eb95b6915d263e6bb37e9a/lib/serverengine/privilege.rb#L38
My guess is that the GID needs to be set before the UID. Once you change the effective UID, the process no longer has the permissions to modify its GID. Simply changing the order should fix this.
Some testing directly with ruby:
#!/usr/bin/env ruby

def show_permissions(msg)
  puts "#{msg}"
  puts "\t" << `id`
  puts
end

uid="fluentd"
gid="fluentd"

puts

show_permissions "current process privileges ..."

puts "changing uid to #{uid} ...\n"
Process::UID.change_privilege("fluentd")
show_permissions "new effective process privileges ..."

puts "changing gid to #{gid} ...\n"
Process::GID.change_privilege("fluentd")
show_permissions "new effective process privileges ..."

and the results with
~ $ sudo ./change_privilege_uid_first.rb

current process privileges ...
        uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),26(tape),27(video)

changing uid to fluentd ...
new effective process privileges ...
        uid=999(fluentd) gid=0(root) groups=994(fluentd),0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),26(tape),27(video)

changing gid to fluentd ...
./change_privilege_uid_first.rb:21:in `change_privilege': Operation not permitted (Errno::EPERM)
        from ./change_privilege_uid_first.rb:21:in `<main>'

~ $ sudo ./change_privilege_gid_first.rb

current process privileges ...
        uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),26(tape),27(video)

changing gid to fluentd ...
new effective process privileges ...
        uid=0(root) gid=994(fluentd) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),26(tape),27(video)

changing uid to fluentd ...
new effective process privileges ...
        uid=999(fluentd) gid=994(fluentd) groups=994(fluentd),0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),26(tape),27(video)

#75 was merged.d


Support shorthand property compression.

This reduces CSS properties to their shorthand form when possible during inlining.

No blocker so I merged it. Feel free to follow up with those comments.


Background research

We need to understand the requirements of what is needed to build a complete Messaging system from the ground up to completion. Do research on the background and requirements to develop this

Noted. This can work around cron-job

cron jobs are tricky since they are specific schedule

am thinking of something like a queue data structure  such that each app creates its own queue that consumes the current one waiting for it to be completed then start the next one until there's nothing on the queue

am thinking of something like a queue data structure such that each app creates its own queue that consumes the current one waiting for it to be completed then start the next one until there's nothing on the queue

This can work, so we need to figure out when the request has been completed successfully

am thinking of something like a queue data structure such that each app creates its own queue that consumes the current one waiting for it to be completed then start the next one until there's nothing on the queue

This can work, so we need to figure out when the request has been completed successfully

Phases/Steps of use by any project:

Initialise the queue :- this creates a new queue data structure for the project
Use - this involves managing the queue, adding and removing items in queue. The queue will remain empty if not used
destroy - only destroy the queue of deleting/destroying the initialization

Architecture:

Message broker - handles message flow between producers and consumers
Queues - hold messages, we can use enqueue and dequeue operations
Exchange - routes messages to queues based on certain rules
Bindings - defines how messages should be routed
Producers & Consumers - send and receive message

Implementation Tools:

TypeScript
NodeJS
Redis- storage for Queues, although MongoDB might also be good
WebSockets/HTTP

@Nicholas-Kipkoech what do you think?

Architecture:

Message broker - handles message flow between producers and consumers
Queues - hold messages, we can use enqueue and dequeue operations
Exchange - routes messages to queues based on certain rules
Bindings - defines how messages should be routed
Producers & Consumers - send and receive message

Implementation Tools:

TypeScript
NodeJS
Redis- storage for Queues, although MongoDB might also be good
WebSockets/HTTP

@Nicholas-Kipkoech what do you think?

This is good, I didn't of storage upto now, so we also need to store queues right? I think Redis can work since a user can install it on their machine or even on their server.

Can we have a call tomorrow at 10:00 am? We can plan on how we be working on this?

lunchtime, 1:30 - 2pm tomorrow is fine


add Ariake Dark color theme

Hi @viatsko!
I've added the Ariake Dark color theme — it's minimalistic dark ui scheme and I think, it's really awesome:)

Is there any things I should do to get this PR merged?

@viatsko ping:)

Please add this! Used the theme for Atom, very much like it for VSCode


flatpickr@2.5.8:390 Uncaught DOMException: Failed to execute 'dispatchEvent' on 'EventTarget': The event is already being dispatched.

When using just the time picker, if you click up when seconds are at 55 or if you click down, when seconds are at 00 this error is thrown in the JS console:

flatpickr@2.5.8:390 Uncaught DOMException: Failed to execute 'dispatchEvent' on 'EventTarget': The event is already being dispatched.

Reproduction Link
https://jsfiddle.net/tripflex/of4kwhLo/
Wanted to post this issue before heading out for the day as i'm sure i will forget about it tomorrow, just in case 😛

Already fixed #784
The bugfix is out now in v2.5.9

Awesome, thanks for the quick replies, it's amazing how active you are on here, wish all projects were like that lol! Thanks again!


use clap for the command line argument parsing

It is at this point basically the standard library for reading the command line arguments

assign this one to me


Hugging Face integration of BLIP

Dear authors,
We have a working implementation of BLIP and 3 of its variants in huggingface transformers (image captioning, visual question answering, image text retrieval): https://github.com/huggingface/transformers/pull/20716 that is not merged yet
The license of the repository and model states that:
3. Neither the name of [Salesforce.com](http://salesforce.com/) nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

We would like to promote the addition of this architecture to transformers library. Therefore I would like to ask you the permission for promoting this contribution
Thank you very much in advance

Hi @younesbelkada, thanks a lot for this.
I don't see any issue myself. Please allow us a few days to have an internal discussion. Will get back soon.

Hi @younesbelkada , thanks for the patience.
We have an internal discussion and would be happy to see BLIP supported on HF. Please go ahead with the integration with acknowledging the publication, authors and our organization.
Thanks for your interest in our work.

Thanks so much for this great news
The integration has been announced through various medias:
Twitter: https://twitter.com/younesbelkada/status/1605489647395540992?s=20&t=b9XNjRBW1o-Mu2NkERvrLw
LI: https://www.linkedin.com/posts/younes-belkada-b1a903145_deeplearning-multimodal-api-a[…]721751482368-T49x?utm_source=share&utm_medium=member_desktop
Thanks again for sharing this great model! Let's collaborate more whenever we can


[Website] update check-links

update check-links.sh script
add func to find absolute links, leading to prod and staging
add manually verified list with links that should be ignored
sort invalid links by error code status

before:

after:

checking absolute production links

checking staging links

invalid links sorted by error status code

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @aromanenko-dev, could you kindly help with review?

Please, check the naming of methods and variable names.
Do we run this script automatically? What is an example of he output?

Yes, script is run automatically
Example of the output:

Example of the output is also provided in the description of the PR.


Support retry 0.7

#54 was apparently fixed by adding an upper bound on the retry package. This issue is a request to support building against the new version of retry.
See also: https://github.com/fpco/stackage/issues/975

Ok, will do as soon as possible
On 2015年11月23日(月) at 6:24 Dan Burton<EMAIL_ADDRESS>wrote:

#54 https://github.com/guillaume-nargeot/hpc-coveralls/issues/54 was
apparently fixed by adding an upper bound on the retry package. This
issue is a request to support building against the new version of retry.
See also: fpco/stackage#975 https://github.com/fpco/stackage/issues/975
—
Reply to this email directly or view it on GitHub
https://github.com/guillaume-nargeot/hpc-coveralls/issues/56.

Fixed by #55

Sweet, thanks!


Tighten up Market right side panel

This is mostly my fault but it's an easy fix. We need some consistency on the Market/Trade page in the right panel. Currently it's:

Let's change it to:
Notes:

My Markets matches My History both on left tab
horizontal lines dividing items
mm/dd added to date column
Proposing a more obvious contrast for the inactive tab (compare MY HISTORY to MY MARKETS on the UI below) I think MY HISTORY better represents and inactive tab.
This has been added to the December 2 milestone

I agree with the contrast for inactive/active tabs, matching all/my tabs and the lines between rows.
But the day/month is left out for a reason: lack of space.. There are already issues with overflow in this column. There's a tooltip though when you hover over the date that shows the full date.


Added burn instruction to transaction

With this commit we correct the wrong behavior when burning NFTs under certain conditions, where burn instruction was not finally included in the transaction.
Apparently, this behavior was introduced with commit https://github.com/cryptoloutre/solana-tools/commit/598722001359be35e206fd919dfcf6b83dae9a19
Closes #6

Thanks a lot for the PR :)


centos ssh timeout on podvm image build

During release build testing I've noticed that the centos image build is not able to complete.
Extract from the packer logs which might be relevant
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 	0-...!: (0 ticks this GP) idle=4268/0/0x0 softirq=173/173 fqs=0 (false positive?)
	(detected by 1, t=60005 jiffies, g=-1119, q=6021 ncpus=2)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at default_idle+0xb/0x10
rcu: rcu_preempt kthread timer wakeup didn't happen for 60002 jiffies! g-1119 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: 	Possible timer handling issue on cpu=0 timer-softirq=15
rcu: rcu_preempt kthread starved for 60005 jiffies! g-1119 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
rcu: 	Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt     state:I stack:0     pid:17    ppid:2      flags:0x00004000
Call Trace:
 <TASK>
 __schedule+0x20a/0x550
 ? __pfx_rcu_gp_kthread+0x10/0x10
 schedule+0x2d/0x70
 schedule_timeout+0x88/0x160
 ? __pfx_process_timeout+0x10/0x10
 rcu_gp_fqs_loop+0x114/0x460
 rcu_gp_kthread+0xfb/0x190
 kthread+0xe0/0x100
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x2c/0x50
 </TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at default_idle+0xb/0x10

Hi, running PODVM_DISTRO=centos make podvm-image on a Fedora machine at main (098d5be692d0e3de0ac5995f61c1d692b3a88be5) worked for me.
Something unusual in your environment?
packer 1.9.4
qemu 7.0.0

Hi, running PODVM_DISTRO=centos make podvm-image on a Fedora machine at main (098d5be) worked for me. Something unusual in your environment?
packer 1.9.4
qemu 7.0.0

We see this issue with the github runners, which are ubuntu runners. But we run it all in containers now which should be based on quay.io/centos/centos:stream9
See https://github.com/confidential-containers/cloud-api-adaptor/actions/runs/6747125672/job/18342551362 as an example

CentOS disallow root ssh access by default. See /etc/ssh/sshd_config.
sed -i "s/#PermitRootLogin yes/PermitRootLogin yes/g" /etc/ssh/sshd_config

Interesting that locally I am able to have it working.
On CI I could reproduce  the issue in my forked tree: https://github.com/wainersm/cc-cloud-api-adaptor/actions/runs/6826220976/job/18565665943#step:4:897
I will test your @lysliu to see if it make any difference

Initially I thought the problem was the cpu model ("Skylake-Client") being passed to qemu. I switched to Nehalem but it still does not work.
Then I tried to build the image locally but using sudo. This time it indeed failed. So @lysliu seems right, it seems related with CentOS 9 Stream guest not allowing root access, however his fix does not work because it changes the ssh configuration in the container, rather than on the guest VM launched by packer:
$ sudo -E PATH=$PATH:/home/wmoschet/.local/bin make ARCH=amd64 PODVM_DISTRO=centos CLOUD_PROVIDER=generic podvm-image
...
...
#0 1137.5 2023/11/10 22:05:39 packer-builder-qemu plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp <IP_ADDRESS>:2382: connect: connection refused
#0 1142.5 2023/11/10 22:05:44 packer-builder-qemu plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp <IP_ADDRESS>:2382: connect: connection refused
#0 1147.5 2023/11/10 22:05:49 packer-builder-qemu plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp <IP_ADDRESS>:2382: connect: connection refused
#0 1152.5 2023/11/10 22:05:54 packer-builder-qemu plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp <IP_ADDRESS>:2382: connect: connection refused
#0 1157.5 2023/11/10 22:05:59 packer-builder-qemu plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp <IP_ADDRESS>:2382: connect: connection refused
#0 1162.5 2023/11/10 22:06:04 packer-builder-qemu plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp <IP_ADDRESS>:2382: connect: connection refused
#0 1167.5 2023/11/10 22:06:09 packer-builder-qemu plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp <IP_ADDRESS>:2382: connect: connection refused
#0 1171.9 ==> qemu.centos: Timeout waiting for SSH.
#0 1171.9 2023/11/10 22:06:13 packer-builder-qemu plugin: [DEBUG] SSH wait cancelled. Exiting loop.
#0 1171.9 2023/11/10 22:06:13 packer-builder-qemu plugin: failed to unlock port lockfile: close tcp <IP_ADDRESS>:5962: use of closed network connection
#0 1171.9 2023/11/10 22:06:13 packer-builder-qemu plugin: failed to unlock port lockfile: close tcp <IP_ADDRESS>:2382: use of closed network connection
#0 1171.9 ==> qemu.centos: Deleting output directory...
#0 1172.1 2023/11/10 22:06:14 [INFO] (telemetry) ending qemu.centos
#0 1172.1 ==> Wait completed after 17 minutes 38 seconds
#0 1172.1 2023/11/10 22:06:14 machine readable: error-count []string{"1"}
#0 1172.1 ==> Some builds didn't complete successfully and had errors:
#0 1172.1 2023/11/10 22:06:14 machine readable: qemu.centos,error []string{"Timeout waiting for SSH."}
#0 1172.1 ==> Builds finished but no artifacts were created.
#0 1172.1 2023/11/10 22:06:14 [INFO] (telemetry) Finalizing.
#0 1172.1 Build 'qemu.centos' errored after 17 minutes 38 seconds: Timeout waiting for SSH.
#0 1172.1
#0 1172.1 ==> Wait completed after 17 minutes 38 seconds
#0 1172.1
#0 1172.1 ==> Some builds didn't complete successfully and had errors:
#0 1172.1 --> qemu.centos: Timeout waiting for SSH.
#0 1172.1
#0 1172.1 ==> Builds finished but no artifacts were created.
#0 1172.9 2023/11/10 22:06:14 waiting for all plugin processes to complete...
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 2023/11/10 22:06:14 /usr/bin/packer: plugin process exited
#0 1172.9 make: *** [Makefile:78: podvm-48c5352-dirty-amd64.qcow2] Error 1
------
Dockerfile.podvm.centos:50
--------------------
  49 |
  50 | >>> RUN cd cloud-api-adaptor/podvm && \
  51 | >>>     PACKER_LOG=1 LIBC=gnu make image
  52 |
--------------------
ERROR: failed to solve: process "/bin/sh -c cd cloud-api-adaptor/podvm &&     PACKER_LOG=1 LIBC=gnu make image" did not complete successfully: exit code: 2
make: *** [Makefile:226: podvm-image] Error 1

One possible solution seems to be passing a cloud-init script to packer to enable ssh root access permission. But I don't know how yet.... @snir911 any idea?

@wainersm I think you can set it in podvm/qcow2/userdata.cfg , however, I still couldn't reproduce this locally, i.e. it works for me without root...


Change netci to be open version

Hi @mmitche, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

test ci please

test ci please


Git diff of too large image file: Unsupported text encoding and NaNTB

VSCode Version: 1.23.1
OS Version: mac OS 10.13.4 High Sierra

Steps to Reproduce:

Create git repo
Create an image file that is larger than the limit for the built-in image preview and commit it to the repo
Replace it with a smaller image and look at the diff from the source control view
It shows "The file is not displayed in the editor because it is either binary or uses an unsupported text encoding." instead of the preview of the large image. Furthermore it shows NaNTB as file size of the previous image in the status bar.

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

@mjbvz for the status bar bug

Actually, giving it to you @mjbvz because it seems to me that also the left-hand binary view should read this instead: The file is not displayed in the editor because it is too large

I pushed a fix to not draw NanTB in the status bar if the size is not known.

I've confirmed that we no longer show the NaN TB in the status bar.
We still do not show anything helpful on the left side of the editor for large image however. This root cause is that for the left side resource, VS Code uses a uri such as "data:%3Blabel%3Abig.png%3Bdescription%3AHEAD%2C". I believe that these uris are created here by the git extension: https://github.com/microsoft/vscode/blob/1cd6bd6096da2d62cdc56296f0de0fd75237b4c5/extensions/git/src/commands.ts#L350
@joaomoreno Do you have ideas on if or how we could handle this case better? Should we use the label in the data uri to try to detect that the file is an image?

Would this be solved by using an FS provider for git resources and moving away from the TextDocumentContentProvider?

Since the 1MB is a known limitation of the current approach, I'm removing myself from this October issue. FS Provider might be a solution, but definitely not for October.

@joaomoreno my understanding is that this data is flowing around via data-URIs, no?
I think, yes, a file system provider for Git is ideal for all cases :+1:

Yes, but that's because Git still uses the once-only-available TextDocumentContentProvider... if we were to switch to the FS Provider, couldn't we send binary files as well?

@mjbvz should comment on that, since he rewrote the binary viewer as extension, I am not sure how binary data is shown.

@joaomoreno Yes, if git returned a uri that points to a custom file system provider, it could provide binary data as well

#55110

Ok, closing this as a duplicate of #55110 then


BuildWebHost Errs on Internal IDictionary

From @rchrismon on May 11, 2018 5:51
Not sure where to post this, perhaps you can tell me.
Core 2.1 Web MVC App, Program.cs is stock out of the box. When I debug the app, it errs at
public static IWebHost BuildWebHost(string[] args) => 			WebHost.CreateDefaultBuilder(args) 				   .UseStartup<Startup>() 				   .Build();
The error is:

Method not found: 'System.Collections.IDictionary Internal.Runtime.Augments.EnvironmentAugments.GetEnvironmentVariables()'.

FWIW, poking into the error details, I saw many errors around System.Reflection. One in particular caught my eye.

((System.Reflection.RuntimeAssembly)((System.RuntimeType)((System.RuntimeType)((System.Reflection.RuntimeMethodInfo)($exception).TargetSite).DeclaringType).BaseType).Assembly).CodeBase

Any insight, or a better place to ask, I'd greatly appreciate.
Thanks,
Randy Chrismon
Copied from original issue: dotnet/sdk#2236

What version of the .NET Core SDK you are using? What are you using to debug it? If you are not debugging it, does the app run normally?

From @rchrismon on May 11, 2018 19:54
dotnet is 2.1.200 (haven't been able to get my project to use 2.1.4 -- but that's another problem).
SDK is 2.0.7
I was thinking there might be something in my code, but it literally breaks in Main(). Oh, one more thing, I'm using msbuild, NOT JetBrains build. ;-)

From @muratg on May 12, 2018 0:23
That stack does not look familiar.
I'm curious about your exact runtime you're using which caused this MissingMethodException.

what do you mean by dotnet is 2.1.200 and the SDK is 2.0.7? They should be the same.
Also, I assume this is VS and msbuild vs. jetbrains build, you mean the setting to switch those?
@muratg is the stack above in ASP.NET?
What version of VS are you using?

From @muratg on May 12, 2018 0:24
@rchrismon also, if you haven't done already, I recommend asking over at stackoverflow.com as well.

From @rchrismon on May 13, 2018 20:53
Hi,
The dotnet runtime is 2.1.200. I meant to say the Windows runtime is 2.0.7 (probably doesn't have anything to do with this problem).
To reiterate, the project builds without error, whether from within VS 2017 (<IP_ADDRESS>), or from the command line using dotnet or msbuilid. When starting the app with debug, it breaks on the second method in Program.cs. Several of my colleagues also tried to run the app without success. I have not, however, tried to run the app without debugging. I'll do that first thing tomorrow. I can't run the app from a web-server because I don't have an available non-production server available right now.
Also, I haven't asked the question on StackOverflow. I'll do that later this afternoon.
As always, thank you for your help.
Randy

From @rchrismon on May 21, 2018 14:59
Tried running the app from the command line -- dotnet run, so no debugging, but get the same error as running in VS. JetBrains Ultimate is latest version (2018.1) and VS is VS 2017 v15.8.0 Preview 1.1 professional. (I also get the error on my other computer when running from latest VS 2017 commercial release.
I have removed every NuGet package not essential to the operation of the app, and the same with VS tools and extensions. Finally, for grins and giggles, I tried opening the solution in JetBrains Rider. Same error, same place, except the stack trace says the error originated in the Main method with BuildWebHost(args).Run().
Is it at all possible that this is a NullReferenceException without yielding that message? There are no command-line arguments so "args" is null on application startup. OTOH, I don't know why this app would bork here when so many others do not.
Thanks.

From @rchrismon on May 13, 2018 20:55
I forgot to mention, my teammates run from their branches without problem, but they can't run my branch (same error). So, I'm guessing it has to be something in my code, or something in the additional dll packages I included with my build. I'm going to explore tomorrow what packages I have that they don't, or vise versa.
Thanks!
Randy

I am moving this issue to asp.net, where it may get better traction. This is not looking like an SDK issue right now.

Do you have a minimal project you can share that reproduces this error?

I created a minimal .netcore 2.1 project, adding only the latest MySQL dlls, since that's a required part of the project. That project runs just fine. So, no help there.
FWIW, I can't run any branch of the application, including those done by my team members. All the same error.

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


slim image size

Codecov Report

Merging #92 (e0f4dca) into main (81c060d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #92   +/-   ##
=======================================
  Coverage   10.90%   10.90%
=======================================
  Files          11       11
  Lines        1119     1119
=======================================
  Hits          122      122
  Misses        994      994
  Partials        3        3

Flag
Coverage Δ

unittests
10.90% <ø> (ø)

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

Continue to review full report at Codecov.

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


Update Composer dependencies (2024-07-22-00-10)

Visual regression test passed!
View the visual regression test report


upgrade sk,others to latest version

Purpose

Upgrade SK and other packages in the ai-service to latest version and made code modifications required to make it work
Does this introduce a breaking change?

[ ] Yes
[X ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ X] Other... Please describe: package upgrade

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Overall LTGM.
I did need to make a small change to init AzureChatCompletion for AAD auth. Also noticed the ai-service needs more memory now so bumped its limit to 85MB in ai-service.yaml files. This also requires changes in our docs so will merge this change after https://github.com/MicrosoftDocs/azure-docs-pr/pull/262737 has been merged.


How to test my fix for doom-emacs?

I want to submit pull request, but surely I should test in my own emacs.
So I do the following:
diff --git a/modules/config/default/+bindings.el b/modules/config/default/+bindings.el
index 7cbfee74..2abacf6d 100644
--- a/modules/config/default/+bindings.el
+++ b/modules/config/default/+bindings.el
@@ -103,6 +103,8 @@
       :n  "g@" #'+evil:apply-macro
       ;; repeat in visual mode (FIXME buggy)
       :v  "."  #'evil-repeat
+      ;; line mode in visual mode
+      :v  "V"  #'evil-visual-line
       ;; don't leave visual mode after shifting
       :v  "<"  #'+evil/visual-dedent  ; vnoremap < <gv
       :v  ">"  #'+evil/visual-indent  ; vnoremap > >gv

Then I reopen emacs, but my new codes does not take effect.
I run make/make compile/make clean etc, still don't work.

I don't understand why that doesn't work for you. It does for me. But I suspect the problem exists elsewhere in your code.
Can you pastebin or link the whole file? Or make the PR anyway? I won't be able to tell without seeing more of it.

Got it. because "V" is mapped later in https://github.com/hlissner/doom-emacs/blob/develop/modules/config/default/%2Bbindings.el#L296.


Document --set-high-watermark and --remove-high-watermark

Document the new watermark-repair options, --set-high-watermark and --remove-high-watermark, on this page. See https://github.com/Consensys/web3signer/pull/912 for more info.

Hey @alexandratran, can work on this issue if you're not already working on it.

@ATREAY assigned to you. Thanks!

Hey @alexandratran, I've included the necessary subcommands. Please take a look whenever you have time, and tell me if any changes are needed.


Debug ControlMessage::wait() errors on Theta

Very rarely, I'm seeing these messages in my job logs on Theta at job start:
Error: <geopm> Runtime error: ControlMessage::wait(): Timed out waiting for status 1: at geopm/src/ControlMessage.cpp:87
Error: <geopm> Runtime error: ControlMessage::wait(): Timed out waiting for status 4: at geopm/src/ControlMessage.cpp:87
...
<the error message for status 4 is repeated many times, once for each rank on each node I believe>

Once this happens, the job hangs indefinitely.  It will eventually be killed by the resource manager when it times out.  The app appears to run to completion, but the Controller is hung.
The last job I have that reproduced this problem is 262202.  Here are the relevant docs:
/projects/intel/geopm-home/shared/output/262202.output
/projects/intel/geopm-home/shared/output/262202.error
/projects/intel/geopm-home/shared/output/262202.cobaltlog
/projects/intel/geopm-home/shared/output/262202-nekbone-256node-1rank-62thread-2018-08-15_1011```

The following jobs have had this issue to date:
257494.error
257781.error
257830.error
260629.error
261980.error
262202.error
262604.error
262854.error
262858.error

The following jobs have had the issue to date:
257494
261980
262202
262604
262854
262858

grep "Timed out waiting for status 1" *error | cut -d: -f1 | xargs ls -la

New failures over the weekend:
262863
262877
262884
262945
262946

These issues persist, but only for Nekbone.  @dianarg is not having problems with AMG or MiniFE.
I'm trying to get this up in DDT.  I can't make progress on this presently because of #344.  I must use the pthread launch method because of DDT.  DDT hangs at launch on Theta with the process launch method.

The issues around launching in pthread mode have been fixed on Mr. Fusion.  The issue about OMP process masks being zeroed (#346) remains.  It must be resolved before DDT can be utilized with the pthread launch mechanism.

Turns out DDT is a no-go since this is a problem that occurs within MPI_Init.  printf is the only way to go...
https://github.com/cmcantalupo/geopm/commit/46b2a96
https://github.com/cmcantalupo/geopm/commit/66a9e266c6c9cd1017a6c34a0d9742b3fba76a3a
https://github.com/cmcantalupo/geopm/commit/c018e48dc7f5fa4d58234e692afe4cff93beb102

Chris and I have been suspecting there's some sort of race that happens with the creation of the SharedMemory region that's used between the app and the Controller.  What should happen is that the Controller starts up, creates a shmem region, calls ftruncate() to grow the region, then proceed onward.
The app should first wait until the region is created, then wait for the region to be grown (i.e. fstat() should not return size 0), then proceed onward.  After some digging yesterday, it appears as though ftruncate is not atomic and simply having the app wait for fstat() to return a non-zero size is not enough to ensure the region is ready.
The ftruncate() code on the Controller side is here:
https://github.com/geopm/geopm/blob/bdddc85e03dcd0a1a4073ed63bd581ed885ae95a/src/SharedMemory.cpp#L59-L65
The fstat() code on the app size is here:
https://github.com/geopm/geopm/blob/bdddc85e03dcd0a1a4073ed63bd581ed885ae95a/src/SharedMemory.cpp#L164-L170
I've been testing a workaround that sleeps for a period of time after the fstat() call returns non-zero.  It's in commit 6325a82a9662ec1b3173d587818a65016a66a434, presently on my bgeltz-theta branch.  It appears to resolve the race in my long job that ran last night.
If this is indeed the culprit, then we need to introduce some sort of lock bit/ready value that the Controller writes into the shmem region.  That way, the app would continue to wait until this known value appears in the region.

https://review.gerrithub.io/#/c/geopm/geopm/+/426122/