XGBoost is 10x slower when the index of sparse data is 10x larger

It may be the issue about performance.
We have tried XGBoost with the official example code and data. Here is the script of training.
import xgboost as xgb
# read in data
dtrain = xgb.DMatrix('demo/data/agaricus.txt.train')
dtest = xgb.DMatrix('demo/data/agaricus.txt.test')
# specify parameters via map
param = {'max_depth':2, 'eta':1, 'silent':1, 'objective':'binary:logistic' }
num_round = 2
bst = xgb.train(param, dtrain, num_round)
# make prediction
preds = bst.predict(dtest)

And we modify the training data by adding the much larger index, just like this.
1 1:1 10:1 11:1 21:1 30:1 34:1 36:1 40:1 41:1 53:1 58:1 65:1 69:1 77:1 86:1 88:1 92:1 95:1 102:1 105:1 117:1 124:1 10000000:1
0 3:1 10:1 20:1 21:1 23:1 34:1 36:1 39:1 41:1 53:1 56:1 65:1 69:1 77:1 86:1 88:1 92:1 95:1 102:1 106:1 116:1 120:1
0 1:1 10:1 19:1 21:1 24:1 34:1 36:1 39:1 42:1 53:1 56:1 65:1 69:1 77:1 86:1 88:1 92:1 95:1 102:1 106:1 116:1 122:1

It took ~20 seconds when the index was up to 10000000 and took ~200 seconds when the index was 100000000:1. Because the data is sparse and we don't expect it will be much slower when the index is larger.
Environment info
Operating System:
Mac OSX
If installing from source, please provide

The commit hash (git rev-parse HEAD)
Logs will be helpful (If logs are large, please upload as attachment).

2d9052bc7dfc4d40e915820e0bede05c626b588d
If you are using python package, please provide

The python version and distribution
The command to install xgboost if you are not installing from source

Python 2.7.13
Steps to reproduce

Clone the xgboost project.
Edit the training data by adding 10000000:1 at the end of the first line.
Copy the training script above and run.

xgboost doesn't do feature hashing. So it has dense vectors in a few places which are storing all feature ids in the range. Constructing, initializing and manipulating 100M vectors multiple times is not cheap.

That makes sense. Thanks @khotilov 😃
It would be great if XGBoost can support this later.


System Error when running Ganache 2.5.4 on win32

I opened the ganache GUI, and then I clicked events - and boom this error message pops up, it has been doing since every time I click on events.
PLATFORM: win32
GANACHE VERSION: 2.5.4
EXCEPTION:
TypeError: Cannot read property 'stack' of undefined
    at IpcMainImpl.<anonymous> (C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\app.asar\webpack:\src\integrations\ethereum\index.js:76:29)

Hey can you please try this in the latest release? We fixed this in v2.7.1 https://github.com/trufflesuite/ganache-ui/releases/tag/v2.7.1
Thanks!


[FEA] Support to_json function

I wish we can support the function to_json.
For example:
from pyspark.sql.functions import struct, to_json
data = [("John", "Doe", 21), ("Jane", "Doe", 25), ("Sam", "Smith", 30)]
df = spark.createDataFrame(data, ["first_name", "last_name", "age"])
df = df.withColumn("person", struct("first_name", "last_name", "age"))
df = df.withColumn("person_json", to_json("person"))
df.show()

Not-Supported-messages:
 ! <StructsToJson> to_json(struct(first_name, first_name#0, last_name, last_name#1, age, age#2L), Some(UTC)) cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.catalyst.expressions.StructsToJson

This is fairly close to being able to write out JSON to a file in the JSON lines format.  We might want to try supporting both because the only real difference is going to be inserting in a \n between the lines at the end and writing it to a file.
First off are there any non-default JSON options that we need to support?

ignoreNullFields
locale
dateFormat
timestampFormat
timestampNTZFormat
pretty
timeZone
writeNonAsciiCharactersAsCodePoint
encoding/charset- probably not supported here
spark.sql.jsonGenerator.writeNullIfWithDefaultValue - note sure this one is supported
spark.sql.legacy.timeParserPolicy

Do we know what are the input types that they want to support? At the top level Spark supports Struct, and Array (Although most of the code looks like it could support map as well. Not 100% sure what is happening with that we should test it.
What are the required child types? Do they include CalendarIntervalType or any interval type? UserDefinedTypes? Maps that don't have a string as the key?
It mostly comes down to casting things to strings. Doing some escaping if needed and other string manipulation. Not sure how fast it will be with all of the variable length string manipulation that would need to happen, but it should be doable.

We can hold on to this feature request for a few days since customers have other higher priorities todo.
CC @viadea


Artifacts in query result

In aggregation queries over longer time we see artifacts where result graphs are briefly interrupted.
This probably happens at block boundaries but is not current caught by PromQL tests even if spanning multiple blocks.
This is probably a minor bug that just need to be tracked down. Finding a PromQL test that can reproduce the behavior would be a good first step.

Dummy regression identified and fixed.


Dockerfile : clone this repo only to get nerc model+ jar = necessary?

For the ixa-pipe-nerc module to run smoothly (without compiled version mismatch) it is necessary to use a specific combination of jar and trained model. For that reason, cloning ixa-pipe-nerc is not a solution. But is it necessary to clone this (!) entire repo to obtain the jar and model?

I was thinking of making the Dockerfile download the whole ixa-pipes-1.1.1 package, extracting the necessary exec-jars + models, and removing the rest. That would allow for a single download and avoid version mismatches. Do you agree?

Sure !
On Fri, Mar 30, 2018, 15:36 Wouter Kouw<EMAIL_ADDRESS>wrote:

I was thinking of making the Dockerfile download the whole ixa-pipes-1.1.1
package http://ixa2.si.ehu.es/ixa-pipes/download.html, extracting the
necessary exec-jars + models, and removing the rest. That would allow for a
single download and avoid version mismatches. Do you agree?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ADAH-EviDENce/NewsReader/issues/19#issuecomment-377525471,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABad_-S-GeGX4vHxEWvCKli4zGDD-MtMks5tjjTEgaJpZM4TAANf
.


require openssl if url is https

Prior to this change, the generated code would throw
uninitialized constant OpenSSL NameError
closes #97
The CI tests will fail because of unrelated errors out of scope of this PR.

Seems good to me. Can you update test/fixtures/output/ruby/native/https.rb to have the require statement and run the tests locally to make sure they succeed?
e.g.
node_modules/.bin/mocha test/targets.js

And then look for the autogenerated ruby test:
should generate https snippet

We're currently overhauling the repo and looking to get the tests passing soon, which would make it easier to verify, so bear with us!

@JPrevost our tests are stable on our master! lemme know if you have any bandwidth to rebase or if I need to cherry pick these commits and push it through.

@darrenjennings I've rebased and then addressed a linting issue in a new commit. Let me know if this needs anything else.


Config self reference fix

builds on #462 fixing the remaining issues discussed in BROOKLYN-329
immediate eval could be improved yet further but this fixes scope/resolution issues and in general makes immediate things much more reliable, as well as fixing recursive references in config settings, and helping to debug bad task traces

@ahgittin This is way too hard to review until #462 is merged (which requires rebasing and a bunch of PR comments to be addressed; as I asked there, will you have time to address those or would you like one of us to pick it up)?
This PR also looks like it has a bunch of other commits that could (and should) be extracted into their own PRs (e.g. "solve problem with map eval" perhaps? Definitely "slow tests moved to integration group"? "cleanup, and allow TaskFactory to be supplied as a config..." perhaps?). I presume they are not all related to the title "Config self reference fix"?
Including many changes in a single PR makes the reviewers job much harder, and makes it take much much longer to get things merged.

Rebased, and once #462 is merged this should be easier to review.  Cherry-picking my "slow tests" meant it automatically left this PR which was nice.

Re TaskFactory being a separate PR, that would mean massaging the tests and other places so there is a clean state where TF isn't supported, and a clean state where TF is supported.  Agree in general PRs should be split up, but where something is trivial (integration tests), or where things are entangled (TaskFactory) it should be a judgment call.  We should avoid hypothetical problem-spotting:  "Your PR includes things not 100% related.  That's scientifically proven to make it much harder to review."  If in the course of a review it is actually hard, then ask for a tidy-up.  I might get the balance wrong sometimes but I think here my atrocities are limited to having neglected #462 for months and months.

Pretty sure the failures reported here are unrelated:
* org.apache.brooklyn.launcher.CleanOrphanedLocationsIntegrationTest.testCleanedCopiedPersistedState
* org.apache.brooklyn.launcher.CleanOrphanedLocationsIntegrationTest.testSelectionWithOrphanedLocationsInData

Both pass for me locally.  (Incidentally @aledsage none of the tests in that class are marked "Integration".)

Unrelated test failures in penultimate jenkins build are discussed at https://github.com/apache/brooklyn-server/pull/560

thanks @aledsage -- have done most of them.  a few more will require more thought from me, marked them so i can find them easily.

All should be fixed now @aledsage
https://github.com/apache/brooklyn-server/pull/480/commits/99ccc0f6c8703e924c5fff5197bf1a0c6e39bc81 adds comments and assertions for the cancellation behaviour.  TL;DR, TaskFactory config values should have their tasks cancelled, but Task values should not.  The last commit fixes one thing which had been causing a failure in integration tests.
The remaining messy/broken tests seem to be mainly around immediate not having any guarantees due to timing.  I'd like to try to switch most/all to use the interrupting-immediate pattern, but that'll be another PR :) .

@aledsage Thanks for thorough comments.  I'll review this afternoon and revert with whether to merge or not.
One high level comment:  Task instances should be left running, even if immediate execution is requested, because someone else might subsequently ask for that value in a non-immediate context.  If we cancelled after immediate execution then the subsequent request would fail.  This isn't a leak but an implication of supporting Task evaluation (and for that reason I think we want to prefer TaskFactory evaluation).  I think this addresses many of your comments; will look closer after lunch.

@aledsage I think I've addressed these comments, TY; but now merge conflicts with #155 are hurting; as noted there I think we should revert that.

@aledsage minor changes addressing your comments, and fixed conflicts; would like your confirmation that an immediate Task "leaking" is the right behaviour (and longer term moving away from tasks as these values!) and anything else on your mind, but feels like it may be good to merge now :)

@ahgittin agreed - we should not cancel the task, so "leaking" it is right behaviour.
The build failure is real, until we commit to switching to Java 8 - please give your opinion on that email thread :-)
[ERROR] /home/jenkins/jenkins-slave/workspace/brooklyn-server-pull-requests/core/src/main/java/org/apache/brooklyn/util/core/task/BasicExecutionContext.java:[31,25] error: package java.util.function does not exist

That package was added in Java 8.
I think it's just the wrong import (should be guava's; it's only used for the javadoc).
Can you fix that, and then merge?

thanks @aledsage - fixed, if these tests pass, then good to merge

Excellent, thanks @ahgittin - merging now.


contiguous_iterator should be constexpr

std::views::join on beman::optional26::optional doesn't work in constexpr context in my code https://godbolt.org/z/Ed11G66s3 (switch preprocessor if 1 to see error)
This code doesn't work in constexpr:
auto range_result = view_of_optionals | std::views::join | std::views::take(100);

I expected it work like this C++23 code:
auto range_result = view_of_optionals
        | std::views::filter([](const optional26<int>& opt) { return opt.has_value(); })
        | std::views::transform([](const optional26<int>& opt) { return *opt; })
        | std::views::take(100);

Filtering out all nullopt from view
With std::views::join compiler gives error that contiguous_iterator is not constexpr, so I simply tried editing it's declaration - marking everything I could as constexpr and afterwards this code worked as expected. So solely based on this I think it should be constexpr.

Will also check if draft standard has the bug.

Will also check if draft standard has the bug.

[optional.iterators]/1 is already requiring the iterator types meeting the contexpr iterator requirements. Such requirements are correctly copied into [optionalref.iterators]/1 in P2988R7.
So we should just add lacked constexpr...


Sort rows by column

I'm thinking to add a sortable flag to the column definition, and sortedBy and onSortClicked parameters and leave it to the user to supply the data sorted.

This is completed by 06c6393


New Term - eventType

New term

Submitter: John Wieczorek
Efficacy Justification (why is this term necessary?): The hierarchical Event structure is not currently capable of distinguishing what different Events are for.
Demand Justification (name at least two organizations that independently need this term): The need for an eventType to distinguish distinct kinds of activities has been promoted in the Interactions Interest Group (https://github.com/tdwg/interaction/issues/22), the Camera Trap Data Package repository (https://github.com/tdwg/camtrap-dp/issues/169#issuecomment-931487715 and https://github.com/tdwg/camtrap-dp/issues/169#issuecomment-931504444), in discussions about the vocabulary for basisOfRecord (https://github.com/tdwg/dwc/issues/302), and in the design of conceptual and data publishing models in Diversifying the GBIF Data Model Project (https://tinyurl.com/diversifying-gbif-data).
Stability Justification (what concerns are there that this might affect existing implementations?): The addition of this term will affect the definition of the GBIF Event Core, but this addition is already anticipated (see https://github.com/gbif/vocabulary/issues/107).
Implications for dwciri: namespace (does this change affect a dwciri term version)?: Yes, an equivalent term in the dwciri: namespace will be required.

Proposed attributes of the new term:

Term name (in lowerCamelCase for properties, UpperCamelCase for classes): eventType
Organized in Class (e.g., Occurrence, Event, Location, Taxon): Event
Definition of the term (normative): The nature of the Event.
Usage comments (recommendations regarding content, etc., not normative): Recommended best practice is to use a controlled vocabulary.
Examples (not normative): sample, observation, biotic interaction
Refines (identifier of the broader term this term refines; normative): None
Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): None
ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): Not in ABCD

I believe this would also resolve an OBIS issue in wanting to identify the type of event and previously using type https://github.com/iobis/obis-issues/issues/172

Some more clarification, perhaps in the examples, would help define what an event consists of. Would it include a bioblitz or an expedition for example? From the examples you might think not, but it would be better to be clear.
It might also be worth explicitly stating that an event span should be detailed in dwc:eventDate.

I don't see the need for an "event span". The event span could be determined based on the first and last eventDate in the dataset.

@qgroom  It would be a little odd to make the recommendation about the other term just for eventType. What about eventType would be special that it would merit the suggestion to put the date in the eventDate field? We don't do that anywhere else in Darwin Core definitions or commentaries unless the dependency is absolute, such as with a value and its units.
The question of examples to include is extremely important for this term, I think. People will be tempted to use the examples that get shared, so we should spend some effort to get it right enough not to regret what goes in there. Ideally, the formal construction of a vocabulary to go with this term would be advisable, as was done for degreeOfEstablishment, for example, but the range of possible event types is enormous and with complex relationships. A pragmatic way forward, knowing that the term is so badly needed, might be to implement the term with conservative examples that are very broad terms and let the community build up the vocabulary in practice via the GBIF vocabulary service (https://github.com/gbif/vocabulary/issues/107).

The question of examples to include is extremely important for this term, I think.

I agree completely!  I also agree that a pragmatic approach is best, as an exhaustive list would be unwieldy.   Perhaps a few examples from a wide range of different categories?
To the proposed list of originally included examples, I would add things like:
expedition
exhibition
imaging process
If you want to cast a broader net, you might include things like:
transaction [e.g., acquisition/loan/borrow/disposal]
preparation [or curation] process
translocation [an event where items are moved from one storage location to another]
geologic
And if you really wanted to go wide you could add things like publication, and other such things bounded in place and time.
There are many other kinds of events that instances of DwC classes participate in, and each of them could have dozens and dozens of "flavors"/children.  But the point is, it might be good to use the examples to help convey some sense of the scope of what dwc:Event (potentially) encompasses.
I tend to err on the inclusive (i.e., broad) scoping of these things, so I would allow for any action bounded in space/time (which is consistent with the current definition of dwc:Event)

I don't see the need for an "event span".

I was not suggesting a new term, only that dwc:eventDate can legitimately hold a data span and this should be used to indicate the length of the event.

The event span could be determined based on the first and last eventDate in the dataset.

This is exactly the issue. dwc:eventDate is normally viewed as an observation level term, so if expedition and bioblitz are legitimate entries in this field there is potential crossover between dataset level information and record level information.
The current examples are suitable for observation level eventTypes and if longer term event types are not the intended usage of this term we should say so, as it is not currently clear. If longer term events are intended usage for eventType then it tends to imply that dwc:eventDate can also be used for dataset level dates.

I agree with @qgroom:  There is definitely a need for eventDate to accommodate a range (span).  ALL events span some period of time (even if it's just milliseconds). In pretty-much any database I develop, date data are captured with startDate and endDate (or, as appropriate, startTime and endTime).
That's a topic of discussion better suited for a dedicated issue in GitHub, but in the context of eventType, adding this term sort of elevates instances of dwc:Event to their own standing -- not just playing the role of an intersection of Location+Time to support other DwC classes. As such, I think it's important that each instance of dwc:Event be self-reliant on its own properties, and not dependent on properties inherited from related records (be they child events or occurrences or whatever).

I agree with @qgroom: There is definitely a need for eventDate to accommodate a range (span).

eventDate already accommodates a range.
I think my concern is with the language "...event span should be detailed..." and "this should be used to indicate the length of the event.". The use of should makes it sound like a requirement and I don't think it is. It's something you might consider doing but in my mind it's not something you have to do. Maybe it's as simple as changing to "consider detailing event span in eventDate".

I draw your attention to Issue #140 in the Data Quality Interest Groups Tests and Assertions (https://github.com/tdwg/bdq/issues/140) where we have developed a test for dwc:eventDate Duration in Seconds (we don't go below seconds)

eventDate already accommodates a range.

Yes, but in a somewhat clunky way. Also, the "Not suitable for a time in a geological context" qualifier in the definition precludes defining events on such timescales.  Maybe those should not be represented as dwc:Event instances; but in other contexts we have discussed the notion of an organism based on fossil material (e.g., dinosaur) being represented through an occurrence instance associated with the time and location (i.e., Event) of its death.  Obviously, such values for eventDate would not conform well to the recommended best practice of formatting in accordance with ISO 8601-1:2019; but it seems to me that dwc:Event should accommodate instances where the value of eventType implies timescales outside the range of the Gregorian calendar.
Or, maybe not -- maybe the scope of dwc:Event instances should be explicitly confined to smaller timescales (as eventDate already implies) -- such as representation through terms organized with the dwc:GeologicalContext class. If so, this would inform what sorts of examples should be included (and, perhaps, explicitly excluded) for values of eventType.

For times the correct terminology for a time entity with a distinct beginning and end is Interval or Period (not 'range').
The beginning and end each occurs at an Instant.
The separation of the beginning and end (i.e. the size of the interval) is its duration, which is a quantity of seconds/days/years etc.
Perhaps looks nit-picky but it is helpful to keep the terminology clean.

@deepreef wrote:

ALL events span some period of time (even if it's just milliseconds)

Yes. This is a key part of Allen's theory
[af-97]
Actions and events in interval temporal logic In: Spatial and Temporal Reasoning. O. Stock, ed., Kluwer, Dordrecht, Netherlands, pp. 205-245.. J.F. Allen; G. Ferguson. 1997. URL: http://dx.doi.org/10.1007/978-0-585-28322-7_7
[al-84]
Towards a general theory of action and time. Artificial Intelligence 23, pp. 123-154.. J.F. Allen. 1984. URL: http://dx.doi.org/10.1016/0004-3702(84)90008-0

@albenson-usgs wrote:

Maybe it's as simple as changing to "consider detailing event span in eventDate".

Yes, that is all that is needed. It makes the explicit connection between the eventType and the eventDate. Then it makes it more clear that, for example, if they write biotic interaction in the eventType they should be detailing the or interval of the interaction in eventDate, not the whole period of the expedition. Obviously, few people measure the time interval of an interaction, but if this connection isn't made some events will be recorded with their actual interval and some not, but you will not be able to tell the difference between the two.
It needs to be clear that eventType and eventDate are observation level terms at the bottom of the hierarchy of potential dates and intervals  that could be used to describe a dateset.

This proposal has been updated to accommodate all comments thus far.


Default peer address is hard-coded in chaincode shim

From fabric/core/chaincode/shim at line 129:
func getPeerAddress() string {
	if peerAddress != "" {
		return peerAddress
	}

	if peerAddress = viper.GetString("peer.address"); peerAddress == "" {
		// Assume docker container, return well known docker host address
		peerAddress = "<IP_ADDRESS>:30303"
	}

	return peerAddress
}

The hard-coded default peer address is a very bad assumption. The Docker ".1" address is the Docker bridge itself, not any peer, and there is no guarantee that Docker is bridged at <IP_ADDRESS>. The Start() call should fail explicitly if the peer address is unknown, as using this address will lead to a certain, more obscure failure.

@bcbrock good catch, and yes, very bad assumption.  Does this apply here?

@christo4ferris I'm not sure what you mean  re: peer/config.go, Cache.Configuration.getLocalAddress. I don't see any hard-coded addresses in there.

@gennadylaventman  - can you add this to the list of issue around connection management?

@mastersingh24 - I will.

There is a similar hard-coded default in fabric/core/chaincode/chaincode_support.go
const (
	// DefaultChain is the name of the default chain.
	DefaultChain ChainName = "default"
	// DevModeUserRunsChaincode property allows user to run chaincode in development environment
	DevModeUserRunsChaincode       string = "dev"
	chaincodeStartupTimeoutDefault int    = 5000
	chaincodeInstallPathDefault    string = "/opt/gopath/bin/"
	peerAddressDefault             string = "<IP_ADDRESS>:30303"
)

@bcbrock This issue was addressed by PR #1520 and can now be closed.

Thanks Arnaud @lehors


⚠ ClamAV has degraded performance

In 7e0168e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 93 ms

Resolved: ClamAV performance has improved in f1c724f.


Checkbox text is bold

Rancher Version: master 8/5
Steps to Reproduce:

Go to Add Service
Go to Networking tab

Results:  the text after checkboxes is bold now.  You can see the Always pull image, and the Retain IP.  This is just two instances, there are others.

Expected:  Should not be bold

https://github.com/rancher/ui/pull/809

Hey lauren, the networking one is fixed but the DNS, Always pull image before creating and volumes from are still not fixed.  Sorry I though they were a single class that would be fixed if you fixed one of them.  Below are images from other places that need to be fixed.

[ ] Main Add page - Always pull image

[ ] Volumes tab - Volumes from

[ ] Networking tab - DNS, the text is bold and on line below checkbox

Version - master 8/25
Verified fixed


buffrs publish refuses to publish when the proto/vendor/ is dirty

When publishing, Buffrs populates the proto/vendor/ directory. If one attempts to publish again, Buffrs then complains that the repository is dirty. I think Buffrs should either:

clear proto/vendor/ before checking that the repository is clean
ignore proto/vendor/ when checking that the repository is clean

I'm not sure if this was intended and if it is wanted to ignore/filter the messages that lead to buffrs complaining about dirty proto files under vendor. Anyhow since this was a quick one: https://github.com/helsing-ai/buffrs/pull/224
The PR does only include dirty statuses of the files actually being packaged. Should one wanted to add a subdirectory under proto (e.g. submodule that contains additional *.proto files) this solution wouldn't cover that but I'm not sure how much this is relavant as of now.

I think we should get #224 over the line!


Backport the current state of master to the v3 branch

Please merge #40 before reviewing/merging this PR
This PR is intended to back port the current features from master to the Vapor 3.x branch. It has not undergone extensive testing, and I am not confident that I've correctly handled the differences between the two Vapor versions.
I am particularly concerned about the changes I made to bring back JobsCommand - not sure I did that right.

Thanks for your work on this, @tonyarnold. Once we get approval from @tanner0101 on #40 we can take a look at this!


Use requestFramework

See this: https://github.com/meteor-velocity/velocity/pull/129
mocha-web should now request a mirror and wait for the returned requestId to be returned. See here for more details
something like:
Meteor.call('requestMirror', {framework: 'mocha-web', port: 5000}, function(error,requestId) {
    VelocityMirrors.find({requestId: requestId}).observe({
        added: runTests, changed: runTests
    });
});

or your preferred reactive method

Mocha is now using /velocity/mirrors/request, see https://github.com/mad-eye/meteor-mocha-web/blob/master/server.js#L63


added Quadratic Weighted Kappa to the metrics list

Quadratic Weighed Kappa is a metric that is heavily used to compare the agreement between two raters. For example, it is currently the evaluation metric for one of the competitions on Kaggle. There was no native implementation in Keras so I  implemented one for the same.

Nagging Reviewer @pavithrasv: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 14 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @pavithrasv: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 29 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @pavithrasv: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 44 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @pavithrasv: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 59 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @pavithrasv: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 74 days with no activity and the awaiting review label has been applied.

I think we should add this to add-ons for now and and merge into core based on how widely it is used. https://github.com/tensorflow/addons/tree/master/tensorflow_addons

Sure. When I submitted this PR, addons wasn't there but yeah it makes sense to add it to addons first. I would open a PR there then. Thanks. Closing this one for now


Update logback to 1.5.6

Update logback to 1.5.6

@mneethiraj can you please take a look?

@kokosing - mvn clean install fails in the following tests. Can you please investigate? Also, there was no log file generated in Ranger admin server with this patch. Can you please review this as well? Instructions to build and start Ranger services in docker containers are available under directory dev-support/ranger-docker.
[ERROR] Failures:
[ERROR]   TestKMSAudit.testAggregation:104 expected: <true> but was: <false>
[ERROR]   TestKMSAudit.testAggregationUnauth:140 expected: <true> but was: <false>
[ERROR]   TestKMSAudit.testAuditLogFormat:164 expected: <true> but was: <false>
[INFO]
[ERROR] Tests run: 24, Failures: 3, Errors: 0, Skipped: 0

@kokosing  - updating slf4j version to 2.0.13 resolved the issue I posted earlier.
logback version 1.4 and above require JDK11 - see https://logback.qos.ch/dependencies.html. Ranger currently supports JDK8, hence updating logback to 1.5.6 wouldn't work. The latest version that can be upgraded to is 1.3.14. Sounds good?

Updated patch, to move to logback 1.3.14 is merged in master and ranger-2.5 branches.

Thank you @mneethiraj ❤

Ranger currently supports JDK8

@mneethiraj Are you aware of any plans for Ranger project to migrate to java 11?  Are there any blockers for that endavour?

Are you aware of any plans for Ranger project to migrate to java 11?  Are there any blockers for that endavour?
I think moving Ranger to JDK 11 wouldn't be much work. However, many services that use Ranger plugin still run on JDK8; hence it may not be the right time to move to a higher JDK version. This should be planned for the next release - 2.6 or 3.0.


Provide clearer relationships between concepts

Currently, when using LLMs to convert text to RDF statements, only "skos:related" is used to describe the relationship between concepts. Doing so simplifies the task of LLMs but should provide stronger relationships in the final knowledge graph. SKOS provides more explicit relationships, such as "skos:broader" and "skos:narrower". We can always give concepts clearer relationships by post-processing, but it's worth trying to introduce more complex relationships when annotating the data. Therefore, these text-RDF pairs can be fed into LLMs as part of the prompt, thus providing LLMs with instructions for generating more complicated relationships.

Agrontology is now used to better express the relationships between concepts, but the problem then becomes whether to introduce more general relation ontologies, such as Relation Ontology. The advantage of doing this is that Agrontology is limited in its ability to express relationships; it only has 170 properties. But RO can express almost any relationship. However, because Agrontology has few properties, it is easier to find the most suitable ones when labeling text to RDF triples and subsequently using LLMs. RO has more properties; finding the most appropriate one is very time-consuming and conceivably not easy when using LLMs later on.
So the current strategy is to use Agrontology wherever possible and to use RO only when inevitable, or to avoid it outright.

Ontologies used to express relationships:

Agrontology
OBO Relation Ontology
Semanticscience Integrated Ontology


Remove default coordinator and help to find one

This is the concept I mentioned monday.
This removes wasabiwallet.<i/c>o as default coordinator for Main and Testnet, and replaces it with api.example.com
Then, if the CoordinatorURI set up is either:
https://api.wasabiwallet.io
https://api.wasabiwallet.io
https://api.example.com

the CoinjoinManager catches that no coordinator are configured and display a new message in the MusicBox A coordinator must be configured
If we are in this case, the MusicBox Menu will include a new item, Find a Coordinator, that would be an hyperlink to a doc article with sources to find a coordinator. In this PR, it redirects to the main page of the doc, as no such article exists.
If a custom coordinator has been set up, this new MenuItem doesn't appear anymore.

This PR is ready. It makes the CoordinatorURI nullable, which should be correct as if no coordinator is configured then it should be null to avoid requests.
I focused on reducing amount of changes. For example, I could have made the CoinjoinManager null but it would have produced a lot of changes.

When I try "https://api.wasabiwallet.io/" or "https://api.example.com/" I still see "Awaiting Coinjoin" in the music box. But if I try "https://api.wasabiwallet.co/" it begins the awaiting other participants coinjoin countdown (even though I'm on mainnet).

Thanks this was an issue an introduced while implementing the nullable

It may be good to add the "Find a coordinator" item to the search bar.

Done

I tried clearing all the text in the coordinator box and leaving it blank. When I reloaded the client, it places a single / in the box. Maybe this case should also trigger the music box message and menu item.

@lontivero everything was addressed

I tried clearing all the text in the coordinator box and leaving it blank. When I reloaded the client, it places a single / in the box. Maybe this case should also trigger the music box message and menu item.

Not sure what you did here because I did the same and didn't experience this behavior but anyway catching any correct URI other than wasabiwallet.io or .co that is not a coordinator is out of the scope for this PR.

@lontivero 4e13303
However, as I mentioned in the community calls, doc has to be deployed for this PR to be mergeable.
After that we can release.

doc has to be deployed for this PR to be mergeable.

the docs are live.
And the relevant FAQ is there

However it doesn't accept null anymore?

Nope

Thanks everyone for their help on this PR.


Fix greps

what

update grep slightly.

why

additional testing.

references
N/A

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:cb9d1adb8598235161e815738c30915880fefbd1

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:8b766a047b202b91b07fd077a7dd43b173f26ee4

#84

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:24ed261ac01f3c5f09b71c89c9bdbf80eda60115


Adding additional styling options for wrapper elements and existent entities

Hey, I've added support to passing attributes to entity wrappers "IMAGE and LINK" as well as to list wrappers.
I needed this in the project of mine for passing appropriate classNames when generating markup.
I think it will be a good addition to the package and also will solve issues:
https://github.com/sstur/draft-js-export-html/issues/46
https://github.com/sstur/draft-js-export-html/issues/39

Hi @vnovick. Thanks for your contribution.
I believe entityStyleFn will do what you need for the styling part and I think blockStyleFn does what you need for the ul/ol part (plz correct me if I'm wrong). I'm closing this for now.

Could you give and example of how to style wrapper elements using blockStylFn? I'm having trouble adding a custom class to my custom ul block. Seems I can only modify the individual li items using blockStylFn.

@sstur there is currently no way to add styles or attributes to the wrapperTags
https://github.com/sstur/draft-js-utils/blob/fd9582cfaaa72dc9d06686151a2864f11d7499a7/packages/draft-js-export-html/src/stateToHTML.js#L321-L326


community: Add Bedrock chat_model async methods #11668

Description: Add async methods for Bedrock chat_model and complete the earlier work in https://github.com/langchain-ai/langchain/pull/12477. Does not yet remove duplication so that might need to be addressed later.
Issue: https://github.com/langchain-ai/langchain/issues/11668
Dependencies:
Twitter handle: @villekr

I'm using the following test code (modified from https://github.com/langchain-ai/langchain/pull/12477#issuecomment-1898612350)
If you run it with the current langchain version (0.1.5 in pypi) the BedrockChat variant will not progress concurrently. But with this PR version it does.
import asyncio

from langchain_community.llms import Bedrock
from langchain_community.chat_models import BedrockChat
from langchain.schema.output_parser import StrOutputParser
from langchain.prompts import ChatPromptTemplate

llm_model = Bedrock(model_id="anthropic.claude-v2:1")
chat_model = BedrockChat(model_id="anthropic.claude-v2:1")
prompt = ChatPromptTemplate.from_template("Tell me a story about {topic}.")
parser = StrOutputParser()

async def main():
    await asyncio.gather(
        primary_task(llm_model),
        secondary_task("with Bedrock"),
    )

    await asyncio.gather(
        primary_task(chat_model),
        secondary_task("with BedrockChat"),
    )

async def primary_task(model):
    chain = prompt | model | parser
    async for chunk in chain.astream({"topic": "bears"}):
        print(chunk)

async def secondary_task(name: str):
    print(f"- secondary_task {name} start")
    for i in range(10):
        await asyncio.sleep(1)
        print(f"-- secondary_task {name} increment {i}")

if __name__ == "__main__":
    asyncio.run(main())

@baskaryan, @eyurtsev, @hwchase17 Just let me know if there's anything that keeps this PR awaiting for review & merge.

cc @3coins

Hi, is there any updates here, as of right now, bedrock streaming is not working as expected, it's using the invoke model method that aws provided, not the InvokeModelWithResponseStream

Looks like there are some workflows that require approvals before merge is possible. @jaswanth8888 how to proceed?

@baskaryan, @eyurtsev, @hwchase17, @jaswanth8888 please advice how to get this change merged. Workflows are awaiting approval (and there's no way to merge) although the PR is approved.

Sorry to repeat. Please take care of merging as this has been ready for quite a long time and is approved. @baskaryan, @eyurtsev, @hwchase17, @jaswanth8888.

It's almost a month since this PR was opened. I know we all are busy but keeping ready and approved improvements pending such a long time is just frustrating. @baskaryan, @eyurtsev, @hwchase17, @3coins, @jaswanth8888.

Here's the updated code I used to test this PR.
import asyncio

from langchain_community.llms import Bedrock
from langchain_community.chat_models import BedrockChat
from langchain.schema.output_parser import StrOutputParser
from langchain.prompts import ChatPromptTemplate

llm_model = Bedrock(model_id="anthropic.claude-v2:1")
chat_model = BedrockChat(model_id="anthropic.claude-v2:1")
prompt = ChatPromptTemplate.from_template("Tell me a story about {topic}.")
parser = StrOutputParser()

async def main():
    # langchain 0.1.11: raises ValueError: Streaming must be set to True for async operations.
    # PR: works as expected
    await asyncio.gather(
        primary_task_ainvoke(llm_model),
        secondary_task("Async invoke with Bedrock", 3),
    )

    # langchain 0.1.11: works as expected
    # PR: works as expected
    await asyncio.gather(
        primary_task_ainvoke(chat_model),
        secondary_task("Async invoke with BedrockChat", 3),
    )

    # langchain 0.1.11: works as expected
    # PR: works as expected
    await asyncio.gather(
        primary_task_astream(llm_model),
        secondary_task("Async stream with Bedrock"),
    )

    # langchain 0.1.11: produced output but is not async
    # PR: works as expected
    await asyncio.gather(
        primary_task_astream(chat_model),
        secondary_task("Async stream with BedrockChat"),
    )

async def primary_task_ainvoke(model):
    chain = prompt | model | parser
    response = await chain.ainvoke({"topic": "bears"})
    print(response)

async def primary_task_astream(model):
    chain = prompt | model | parser
    async for chunk in chain.astream({"topic": "bears"}):
        pass
        print(chunk)

async def secondary_task(name: str, delay: int = 1):
    print(f"- secondary_task {name} start")
    for i in range(10):
        await asyncio.sleep(delay)
        print(f"-- secondary_task {name} increment {i}")

if __name__ == "__main__":
    asyncio.run(main())

Here's the summary of the subset of Bedrock operations' status based on my testin:

Operation
Langchain 0.1.11
This PR

llm ainvoke
❌ NOK(1)
✅ OK

chat-model ainvoke
✅ OK
✅ OK

llm astream
✅ OK
✅ OK

chat-model astream
❌ NOK (2)
✅ OK

1 - raises ValueError: Streaming must be set to True for async operations.
2 - produced output but is not async

I modified the Bedrock._call function, which was mentioned here.
There would still be some room for cleaning up the code and remove duplicate but I'd leave that later.

Latest update contains:

Resolved merge conflicts. There seems to have some recent changes for bedrock in master-branch.
Refactored to remove some code duplication

Updated also my test code snippet to include calls for sync-methods. Here are the results with PR vs. master-branch/published version.
| Operation                   | Langchain 0.1.11  | This PR |

master-branch

llm invoke
✅ OK
✅ OK

chat-model invoke
✅ OK
✅ OK

llm stream
✅ OK
✅ OK

chat-model stream
✅ OK
✅ OK

llm ainvoke
❌ NOK(1)
✅ OK

chat-model ainvoke
✅ OK
✅ OK

llm astream
✅ OK
✅ OK

chat-model astream
❌ NOK (2)
✅ OK

1 - raises ValueError: Streaming must be set to True for async operations.
2 - produced output but is not async

import asyncio

from langchain.prompts import ChatPromptTemplate
from langchain.schema.output_parser import StrOutputParser
from langchain_community.chat_models import BedrockChat
from langchain_community.llms import Bedrock

llm_model = Bedrock(model_id="anthropic.claude-v2:1")
chat_model = BedrockChat(model_id="anthropic.claude-v2:1")
prompt = ChatPromptTemplate.from_template("Tell me a story about {topic}.")
parser = StrOutputParser()

async def main():
    # Sync operations

    primary_task_invoke(llm_model, "Sync invoke with llm_model")
    primary_task_invoke(chat_model, "Sync invoke with chat_model")
    primary_task_stream(llm_model, "Sync stream with llm_model")
    primary_task_stream(chat_model, "Sync stream with chat_model")

    # Async operations

    # langchain 0.1.11: raises ValueError: Streaming must be set to True for async operations.  # noqa: B950
    # langchain master: (above)
    # PR: works as expected
    try:
        await asyncio.gather(
            primary_task_ainvoke(llm_model, "Async invoke with llm_model"),
            secondary_task("Async invoke with llm_model", 3),
        )
    except Exception as e:
        print(e)

    # langchain 0.1.11: works as expected
    # langchain master: (above)
    # PR: works as expected
    await asyncio.gather(
        primary_task_ainvoke(chat_model, "Async invoke with chat_model"),
        secondary_task("Async invoke with chat_model", 3),
    )

    # langchain 0.1.11: works as expected
    # langchain master: (above)
    # PR: works as expected
    await asyncio.gather(
        primary_task_astream(llm_model, "Async stream with llm_model"),
        secondary_task("Async stream with llm_model", 3),
    )

    # langchain 0.1.11: produced output but is not async
    # langchain master: (above)
    # PR: works as expected
    await asyncio.gather(
        primary_task_astream(chat_model, "Async stream with chat_model"),
        secondary_task("Async stream with chat_model", 3),
    )

def primary_task_invoke(model, name: str):
    print(f"* primary_task_invoke {name} start")
    chain = prompt | model | parser
    response = chain.invoke({"topic": "bears"})
    print(response)

def primary_task_stream(model, name: str):
    print(f"* primary_task_stream {name} start")
    chain = prompt | model | parser
    for chunk in chain.stream({"topic": "bears"}):
        print(chunk)

async def primary_task_ainvoke(model, name: str):
    print(f"* primary_task_ainvoke {name} start")
    chain = prompt | model | parser
    response = await chain.ainvoke({"topic": "bears"})
    print(response)

async def primary_task_astream(model, name: str):
    print(f"* primary_task_astream {name} start")
    chain = prompt | model | parser
    async for chunk in chain.astream({"topic": "bears"}):
        pass
        print(chunk)

async def secondary_task(name: str, delay: int = 1):
    print(f"- secondary_task {name} start")
    for i in range(10):
        await asyncio.sleep(delay)
        print(f"-- secondary_task {name} increment {i}")

if __name__ == "__main__":
    asyncio.run(main())

Fixed format and lint issues as well as merge conflicts with master. Based on my testing also works ok.

@baskaryan can you help review and merge this finally? It's quite important to have async chat_model methods available.

I fixed merge conflicts once again.
Code quality checks are ok as well as my own tests from Bedrock llm and chat-model sync and async requests. Please proceed for review and hopefully this gets merged soon.

Hi Thanks for this PR. 👍
When I use this PR code, still got some error multiple requests below:
WARNING [langchain_core.callbacks.manager._ahandle_event_for_handler:381] Error in CharacterAsyncHandler.on_llm_new_token callback: ClosedResourceError()

Pleasr provide example code where this warning is visible and reproducible.

Pleasr provide example code where this warning is visible and reproducible.
Do you get that warning only with this PR code and not with master-branch version?

Here's your translation:
Thank you for your reply. I am not using the bedrock code on master, as the online environment does not support asynchronous operations and cannot function. After discovering the warning mentioned, I tried to adjust the synchronous to asynchronous code as follows:
with ThreadPoolExecutor() as executor:
    response = await loop.run_in_executor(
        executor,
        lambda: self.client.invoke_model_with_response_stream(
            **request_options
        ),
    )

Even so, when the code runs in the online environment, it causes the pod resources to increase very rapidly. I am not sure if it is the synchronous-to-asynchronous conversion causing this. Other than this change, all other code is from the code in this PR.
Thank you for your work.

I did a bit of testing and memory profiling comparing Bedrock and OpenAI async streaming. With my own test code I'm not able to reproduce the issue you refer. Also I don't see any specific issues with memory usage, which might cause increased resource usage you mention. What's the online environment you refer to?
I don't know how to approach your problem without code I can use to replicate the issue.
Here's the code I used in my test.
import asyncio
from typing import Any

from langchain.callbacks.base import AsyncCallbackHandler
from langchain.prompts import ChatPromptTemplate
from langchain.schema.output import LLMResult
from langchain.schema.output_parser import StrOutputParser
from langchain_community.chat_models import BedrockChat
from langchain_community.llms import Bedrock
from langchain_openai import ChatOpenAI, OpenAI
from memory_profiler import profile

class AsyncHandler(AsyncCallbackHandler):
    async def on_llm_new_token(self, token: str, *args, **kwargs: Any) -> None:
        # print(token)
        pass

    async def on_llm_end(self, response: LLMResult, *args, **kwargs: Any) -> None:
        # print(response)
        pass

    async def on_llm_error(self, *args, **kwargs: Any) -> None:
        pass

async_callback_handler = AsyncHandler()

bedrock_chat_model = BedrockChat(
    model_id="anthropic.claude-v2:1", streaming=True, callbacks=[async_callback_handler]
)
openai_chat_model = ChatOpenAI(
    model_name="gpt-4", streaming=True, callbacks=[async_callback_handler]
)

prompt = ChatPromptTemplate.from_template("Tell me a story about {topic}.")
parser = StrOutputParser()

async def main():
    await astream(openai_chat_model, "OpenAI Chat")
    await astream(bedrock_chat_model, "Bedrock Chat")

@profile(precision=4)
async def astream(model, name: str):
    print(f"{name} start")
    chain = prompt | model | parser
    async for _ in chain.astream({"topic": "bears"}):
        pass

if __name__ == "__main__":
    asyncio.run(main())

> poetry run python langchain_11668/langchain_11668_memory_profile.py
OpenAI Chat start
Filename: /.../langchain_11668_memory_profile.py

Line #    Mem usage    Increment  Occurrences   Line Contents
=============================================================
    45 100.8125 MiB 100.8125 MiB           1   @profile(precision=4)
    46                                         async def astream(model, name: str):
    47 100.8125 MiB   0.0000 MiB           1       print(f"{name} start")
    48 100.8125 MiB   0.0000 MiB           1       chain = prompt | model | parser
    49 102.9531 MiB -32699.1719 MiB        1210       async for _ in chain.astream({"topic": "bears"}):
    50 102.9531 MiB -16322.1719 MiB         604           pass

Bedrock Chat start
Filename: /...langchain_11668_memory_profile.py

Line #    Mem usage    Increment  Occurrences   Line Contents
=============================================================
    45  46.9062 MiB  46.9062 MiB           1   @profile(precision=4)
    46                                         async def astream(model, name: str):
    47  46.9062 MiB   0.0000 MiB           1       print(f"{name} start")
    48  47.3125 MiB   0.4062 MiB           1       chain = prompt | model | parser
    49  66.9844 MiB -826.5469 MiB         346       async for _ in chain.astream({"topic": "bears"}):
    50  66.9844 MiB -419.7500 MiB         172           pass

Thanks your reply. I will try to streamline the code and post it, thank you.

There is no _aprepare_input_and_invoke_stream method in the class ChatBedrock :(

any update on this one?

@3coins would you mind taking a look at this? Possible the issue exists in langchain-aws as well.

Hey team! This touches the deprecated community bedrock integration, which has been replaced by the langchain-aws package (co-managed with the bedrock team)
This only runs the sync methods in an executor, which the BaseChatModel should be doing anyways, and if that's not the case, please include reproduction code in the issue
I'm going to move the issue to their repo for review there and reference this PR.


Error when trying to update version info

I get an error as soon as I press the menu item to update the version info.
I am using:
Visual Studio 2017 with a couple of important plugins that may possibly affect the world.
ReSharper
Vsvim
Supercharger
I have tried it on three solutions and get the same problem:
Solution 1

Two csproj projects
Both projects are class library projects
Both projects are .NET Framework 4.6.1
Both project names have periods in the name like "x.y.z"

Solution 2

Several csproj project projects
Some projects are nested under solution folders
All projects are .NET Framework 4.6.1
All project files are named similar to Solution 1

Solution 3

Three csproj projects
Simple names in the projects (no periods in the name)
.NET Framework 4.6.1

The code is proprietary so, unfortunately, I can not make it available. :(
I really want this to work so I can try to do different things to help.  If you can provide a version with lots of debug lines or something, I will be more than happy to install it and get some output for you.  I have done that before to help plugin developers.

Thank you for the offer, troubleshooting advice, and problem detail. I will try to get a debugable version posted to you in the next 24 hours.

Attached is a zip file containing an updated VSIX file to install a debug version of the extension. If a message shows prior to showing the edit form, please let me know what type of project is listed and how it fits in the hierarchy (under a project, solution folder, etc.). The only place in the code there is a dictionary add is when enumerating all the projects where I've added the handler.
IntentionalSolutionVersion.zip

I have attached three screen shots from one project (same thing happens on others)

Your new screen that says a problem exists
The next screen, from your tool
The third screen is my solution explorer for the same solution that gave me this error message.

I hope this helps get some useful information for you and let me know if there is more you want me to do.  Am always happy to help.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: David Hall<EMAIL_ADDRESS>Sent: Sunday, February 18, 2018 12:43 PM
To: dahall/IntentionalSolutionVersion<EMAIL_ADDRESS>Cc: Jerry Nothstine<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [dahall/IntentionalSolutionVersion] Error when trying to update version info (#2)
Attached is a zip file containing an updated VSIX file to install a debug version of the extension. If a message shows prior to showing the edit form, please let me know what type of project is listed and how it fits in the hierarchy (under a project, solution folder, etc.). The only place in the code there is a dictionary add is when enumerating all the projects where I've added the handler.
IntentionalSolutionVersion.ziphttps://github.com/dahall/IntentionalSolutionVersion/files/1735037/IntentionalSolutionVersion.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dahall/IntentionalSolutionVersion/issues/2#issuecomment-366541661, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAvlI16tkJYIql-aX9I0FOeO_dohZId7ks5tWH1MgaJpZM4SJmAe.

Just noticed an enhancement request.  ☺  I frequently set beta versions in my solutions until something is ready to push to production.  We set version numbers like:  1.2.3-beta01.  That is where I do the most change sets (probably a couple of times a day) where this would be the most beneficial.  Of course, the AssemblyInfo.cs AsseeblyVersion and AssemblyFileVersion would stay as 1.2.3 but the nuspec file would need 1.2.3-beta01.  Here is an example from a screen shot from your tool.  Note the first line is from AssemblyInfo.cs and the highlighted line is from my nuspec file.  When updating, this I will go to 4.6.1-WebApi-Phase203 and leave the AssemblyFileVersion alone.  When it goes to production, both files will become 4.7.0.
<EMAIL_ADDRESS>From: Jerry Nothstine
Sent: Monday, February 19, 2018 3:57 PM
To: 'dahall/IntentionalSolutionVersion'<EMAIL_ADDRESS>Subject: RE: [dahall/IntentionalSolutionVersion] Error when trying to update version info (#2)
I have attached three screen shots from one project (same thing happens on others)

Your new screen that says a problem exists
The next screen, from your tool
The third screen is my solution explorer for the same solution that gave me this error message.

I hope this helps get some useful information for you and let me know if there is more you want me to do.  Am always happy to help.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: David Hall<EMAIL_ADDRESS>Sent: Sunday, February 18, 2018 12:43 PM
To: dahall/IntentionalSolutionVersion <IntentionalSolutionVersion<EMAIL_ADDRESS>Cc: Jerry Nothstine <Jerry.Nothstine<EMAIL_ADDRESS>Author <author<EMAIL_ADDRESS>Subject: Re: [dahall/IntentionalSolutionVersion] Error when trying to update version info (#2)
Attached is a zip file containing an updated VSIX file to install a debug version of the extension. If a message shows prior to showing the edit form, please let me know what type of project is listed and how it fits in the hierarchy (under a project, solution folder, etc.). The only place in the code there is a dictionary add is when enumerating all the projects where I've added the handler.
IntentionalSolutionVersion.ziphttps://github.com/dahall/IntentionalSolutionVersion/files/1735037/IntentionalSolutionVersion.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dahall/IntentionalSolutionVersion/issues/2#issuecomment-366541661, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAvlI16tkJYIql-aX9I0FOeO_dohZId7ks5tWH1MgaJpZM4SJmAe.

The images didn’t come through in the email or on the issues page. Will you reply to this with them? BTW, thanks for your help.
David
From: jnothstine<EMAIL_ADDRESS>Sent: Monday, February 19, 2018 3:57 PM
To: dahall/IntentionalSolutionVersion<EMAIL_ADDRESS>Cc: David Hall<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [dahall/IntentionalSolutionVersion] Error when trying to update version info (#2)
I have attached three screen shots from one project (same thing happens on others)

Your new screen that says a problem exists
The next screen, from your tool
The third screen is my solution explorer for the same solution that gave me this error message.

I hope this helps get some useful information for you and let me know if there is more you want me to do. Am always happy to help.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: David Hall<EMAIL_ADDRESS>Sent: Sunday, February 18, 2018 12:43 PM
To: dahall/IntentionalSolutionVersion<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Cc: Jerry Nothstine<EMAIL_ADDRESS><EMAIL_ADDRESS>>; Author<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [dahall/IntentionalSolutionVersion] Error when trying to update version info (#2)
Attached is a zip file containing an updated VSIX file to install a debug version of the extension. If a message shows prior to showing the edit form, please let me know what type of project is listed and how it fits in the hierarchy (under a project, solution folder, etc.). The only place in the code there is a dictionary add is when enumerating all the projects where I've added the handler.
IntentionalSolutionVersion.ziphttps://github.com/dahall/IntentionalSolutionVersion/files/1735037/IntentionalSolutionVersion.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dahall/IntentionalSolutionVersion/issues/2#issuecomment-366541661, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAvlI16tkJYIql-aX9I0FOeO_dohZId7ks5tWH1MgaJpZM4SJmAe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/dahall/IntentionalSolutionVersion/issues/2#issuecomment-366821998 , or mute the thread https://github.com/notifications/unsubscribe-auth/ANr2d1m-6O6llCWZXuQ-MR05FYoAMH9pks5tWfwvgaJpZM4SJmAe .  https://github.com/notifications/beacon/ANr2dywB5KKsBp_EJkWpehdvldZczLsSks5tWfwvgaJpZM4SJmAe.gif

I think if you go to the site https://github.com/dahall/IntentionalSolutionVersion/issues/2 and edit or repost, the images will come through. Email seems to be the problem.

Here are the three images for the first message.

Here is the image from my request to add beta versions

Will you describe what is in the .nuget folder in your solution?

Just one file is in that folder.  Nuget.config.  Here is the contents of that file.

From: David Hall<EMAIL_ADDRESS>Sent: Tuesday, February 20, 2018 9:22 AM
To: dahall/IntentionalSolutionVersion<EMAIL_ADDRESS>Cc: Jerry Nothstine<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [dahall/IntentionalSolutionVersion] Error when trying to update version info (#2)
Will you describe what is in the .nuget folder in your solution?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dahall/IntentionalSolutionVersion/issues/2#issuecomment-367032154, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAvlI4WGV1rkNO2MidFbj006I0kV81Soks5tWvFAgaJpZM4SJmAe.

Good news. I believe I found and corrected the error. It had to do with improper handling of solution folders with only files in them. Give this attached version a try: IntentionalSolutionVersion.zip. You will have to manually uninstall the prior VSIX under "Tools | Extensions and Updates", restart VS17, and install this one. I have also, to partially answer your enhancement request, made the extension only search and replace the first 3 digit pairs leaving the 4th alone. If I'm reading your request correctly, this should allow you to update all the major.minor.build sequences using the tool and then set the revision value manually. Right-clicking on the file in the dialog will allow you to open the corresponding file directly to make this edit.

Just did a quick test and that seems to have fixed the problem.
The change for the enhancement request is a nice step and will help.  I have one solution that has five projects with nuspec files that I have to keep in sync.  This is where your tool will be most beneficial is when I can easily update the nuspec version numbers in one place.
Thanks for jumping on the issue and enhancement request so fast.  I love that kind of support for a tool!
Jerry.
From: David Hall<EMAIL_ADDRESS>Sent: Tuesday, February 20, 2018 1:45 PM
To: dahall/IntentionalSolutionVersion<EMAIL_ADDRESS>Cc: Jerry Nothstine<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [dahall/IntentionalSolutionVersion] Error when trying to update version info (#2)
Good news. I believe I found and corrected the error. It had to do with improper handling of solution folders with only files in them. Give this attached version a try: IntentionalSolutionVersion.ziphttps://github.com/dahall/IntentionalSolutionVersion/files/1741798/IntentionalSolutionVersion.zip. You will have to manually uninstall the prior VSIX under "Tools | Extensions and Updates", restart VS17, and install this one. I have also, to partially answer your enhancement request, made the extension only search and replace the first 3 digit pairs leaving the 4th alone. If I'm reading your request correctly, this should allow you to update all the major.minor.build sequences using the tool and then set the revision value manually. Right-clicking on the file in the dialog will allow you to open the corresponding file directly to make this edit.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dahall/IntentionalSolutionVersion/issues/2#issuecomment-367112714, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAvlI56KTQtx_iuZ7aI8BTGik6XWPDRQks5tWy6BgaJpZM4SJmAe.

Thanks for your testing. I am updating the releases with this new code then. If possible, would you mind updating your 1-star rating on Visual Studio Marketplace so that others will be less deterred to try it?

Done.  I also added some text about the great response you have given me on working through the problem.
From: David Hall<EMAIL_ADDRESS>Sent: Wednesday, February 21, 2018 9:11 AM
To: dahall/IntentionalSolutionVersion<EMAIL_ADDRESS>Cc: Jerry Nothstine<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [dahall/IntentionalSolutionVersion] Error when trying to update version info (#2)
Thanks for your testing. I am updating the releases with this new code then. If possible, would you mind updating your 1-star rating on Visual Studio Marketplace so that others will be less deterred to try it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dahall/IntentionalSolutionVersion/issues/2#issuecomment-367378262, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAvlI-_PltRdg3HRMaXxIjcnfhCViZ53ks5tXEACgaJpZM4SJmAe.


The font of the navbar menu does not match with the rest of the font

The font used is Open Sans and the font used for the rest of body in most parts in Rubik, this may cause inconsistency.

@ishitakapoor26

@Aniket-508 Attach screenshot of suggested changes.

the font family of  navbar is open sans which does not go with rest of the font which is rubik
@ishitakapoor26

Good to go! @Aniket-508 create a PR for the same.


Update of adapter does not preserve locallink value

If the adapter is updated, it always changes the locallink value back to its default. This means after every update i need to set this value again. This should not happen. Is it possible to preserve the value during update process?

Why and to what you mondify the value? And how? Do you edit the object?

I need to modify this value because i have 2 url's one for vis/web and another for admin. Both URLs are served by port 443, no port forwarding for the special ports of iobroker. Therefore i modify the value in system.adapter.vis.0 to the needed locallink value of https://sub.domain.com

Then this would be a general feature request for the js-controler because all "field preserving during updates" is handled there. Right now "localLink" is none of the fields to be preserved because else we have no chance ever to fix a broken link there or change one.
This would need a discussion.
please open as Featrue Request in js.controller project. Thank you!


uncaughtException: fix double EVENT_RUN_END events

Description
Per default Mocha tries to recover from uncaughtException and to map the exception to the correct test case. It's not possible to recover gracefully if a Runnable has already passed successfully and then fails asynchronously.
Bailing the runner out of a suite other than the root suite is wrong and will result in the emission of double EVENT_RUN_END events. The first event will not abort the runner and the second one will be emitted by the root suite. To prevent double test epilogues the reporters have been "fixed" in the past by using runner.once(EVENT_RUN_END, ...).
Description of the Change
Applicable issues

Coverage remained the same at 92.483% when pulling e4f5383e6098cb941b813406b4f75f0fea72f0de on juergba/uncaught-bail into 6ec07d6d7f0cf5d76558fd64a6b70b2934148b58 on master.


New package (11.0+) brings Apollo Client into Browser bundle when not used in Client Components

My project uses CommonJS (no "type": "module").
I found an issue.The new version of @apollo/experimental-nextjs-app-support have been added to a bundle, on pages where there is no ApolloProvider, only RSC calls of apollo client.
Steps to reproduce:

install "@apollo/experimental-nextjs-app-support": "0.11.2"
use const {data} = await(await getClient()).query({query: MyQuery}); on any nextjs page.tsx
check the result bundle. There is an @apollo/experimental-nextjs-app-support in browser bundle, and all it deps (like Apollo Client)

Hi there @lionskape 👋
What you're describing indeed sounds very strange. My first instinct is that a question of including server code in a client bundle would be best asked of the framework/bundler.
What version of Next.js are you using? Did you notice this change after this package, or multiple dependencies? Any additional information you can provide would be very helpful in determining where this issue would be best directed. Thanks!

@alessbell hi!
I believe that it is just apollo client, which can be used on SSR (but I do not need it).
I'm using<EMAIL_ADDRESS>with webpack (without customizations).
My case:
app/my-page/page.tsx (server page, no "use client") -> const {data} = await(await getClient()).query({query: MyQuery});. No more queries, no ApolloProvider.
"@apollo/experimental-nextjs-app-support": "0.10.1"
Everything works fine. "@apollo/experimental-nextjs-app-support": "0.10.1" does not contains apollo client.
"@apollo/experimental-nextjs-app-support": "0.11.2"
Everything works, but in client bundle there is a lot of new unused code - @apollo/client and something extra from @apollo/experimental-nextjs-app-support

Hey @lionskape 👋
0.11 added a new shared entry point that now uses export conditions in order to determine the right bundle to use (assuming you're importing from the top-level entry point). This should work well with Next.js and the app router as this is the bundling strategy React recommends for RSC architecture, though the sub imports (i.e. the /rsc, /ssr entry points) remained unchanged.
Can you put together a reproduction for us? A reproduction would go a long way to figuring out why you're seeing the bundle increase.

I can reproduce it here: https://github.com/phryneas/apollo-client-nextjs-reproduction-341/commit/8b39385ac546e1e3d5b5921bd758ef3bbe237724
This is clearly a bug in Next.js. It should not bundle any library that's only referenced in RSC - no matter how we build, no matter how we bundle, it should not have any influence on that.

https://github.com/vercel/next.js/issues/68972

@phryneas I believe they will not include a fix in 14th release. May be it is possible to make workaround in this integration library? Something like additional dedicated @apollo/experimental-nextjs-app-support/rsc export point, with only rsc parts?

Hey @phryneas just a heads-up, we had this same issue at Payload and turns out it's a tough problem to solve.
https://github.com/vercel/next.js/issues/50285
If you have any files marked with use client then they're going to show up in the client side bundle regardless of intent. Is that what's happening in your case I wonder?

Yeah, I had similar thoughts occur to me over the weekend - we have a RSC call that creates a component that references a client component.
I could reduce the impact with a well-placed and lazily executed React.lazy over in #345, so while I still believe that this is a bundling problem on the Next.js side, we can work around it now.

@lionskape could you please verify if this fixes the issue for you?
npm i<EMAIL_ADDRESS>

@phryneas sorry for being late. Thank you, great job!
I have validated your variant, so:

most of code gone from chunks loaded on page
now I have separate chunk with apollo (but it is never loaded)
small amount of code in the bundle. I believe it is a stub for lazy "SimulatePreloadedQuery"

Maybe you can just create a separate entrypoint for rsc, without any "use client" imports in the import graph?
Looks like NextJS team does not treat this as a bug.

@lionskape we're probably not going to get around that stub unless Next.js does something on their side.

Maybe you can just create a separate entrypoint for rsc, without any "use client" imports in the import graph?

We had separate entry points, and it has confused users a lot.
I fear that the moment we have that entrypoint, even if we don't recommend using it, a lot of users will pick it up - in large parts because LLMs just recommend bonkers code that "looks right" to users, but lacks nuance.
I think having that separate entrypoint would do more harm than good - especially since we want most users that use RSC to use the PreloadQuery component, and we'd have to drop that from that separate entrypoint.
It's good to know that this already brings a significant improvement, so I'm going to merge and ship that PR, it will benefit a lot of users. Thank you for bringing this up!


ci: update reference docs

This PR is auto-generated by a nightly GitHub action to update the reference docs from source code in withastro/astro.

This one should have no link problems if it's merged AFTER #5536

Merging because these links will work after #5526 is merged


Support glyphs icons

Hello,
How can I add some feature to your plugin to be able to use Fontawesome or Glyphicon Glyphs in the mardown syntax?
I've seen mardown-it-icon plugin which provide this ability (with some rewrite) but it's a fork of your plugin based on an old version, and the logic seems different...
Thanks in advance

You can define any mapping you wish. You question is too abstract. I'd suggest to look into code, it's very simple.


Issues getting environment properly installed on M1 Mac

Any help you'd be able to offer to get the development environment setup and working on an M1 Mac would be greatly appreciated.
The log of the conda command is attached.
Thanks.
conda_error.log

These dependency errors are notoriously hard to figure out. One way to try and resolve is to unpin versions in the conda file one by one.
for instance:
Try changing statsforecast==0.6.0  to statsforecast>=0.6.0
and python-kaleido==0.1.0 to python-kaleido>=0.1.0
And if that's also not working,
- u8darts<=0.19.0 to - u8darts==0.19.0 or - u8darts>=0.19.0
While this can resolve the conda dependency issues, there is a small risk that some code may not work.

I have followed the instructions for statsforecast and python-kaleido. Seems to work, but then:
Executing transaction: done
Installing pip dependencies: | Ran pip subprocess with arguments:
['/opt/homebrew/anaconda3/envs/modern_ts/bin/python', '-m', 'pip', 'install', '-U', '-r', '/Users/.../Modern-Time-Series-Forecasting-with-Python/condaenv.3kbl5r_a.requirements.txt', '--exists-action=b']
Pip subprocess output:
Collecting git+https://github.com/manujosephv/pytorch_tabular.git@76e83fb (from -r /Users/.../Modern-Time-Series-Forecasting-with-Python/condaenv.3kbl5r_a.requirements.txt (line 8))
  Cloning https://github.com/manujosephv/pytorch_tabular.git (to revision 76e83fb) to /private/var/folders/wy/v6f0ncw16k58dwlsf1jjph7c0000gq/T/pip-req-build-_6pcpbj7
  Resolved https://github.com/manujosephv/pytorch_tabular.git to commit 76e83fb
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'error'

Pip subprocess error:
  Running command git clone --filter=blob:none --quiet https://github.com/manujosephv/pytorch_tabular.git /private/var/folders/wy/v6f0ncw16k58dwlsf1jjph7c0000gq/T/pip-req-build-_6pcpbj7
  WARNING: Did not find branch or tag '76e83fb', assuming revision or ref.
  Running command git checkout -q 76e83fb
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [3 lines of output]
      error in pytorch_tabular setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; Expected end or semicolon (after version specifier)
          protobuf<=3.20.*
                  ~~~~~~^
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

failed

CondaEnvException: Pip failed

fancyimpute also does not install

...

WARNING: Did not find branch or tag '76e83fb', assuming revision or ref.
Running command git checkout -q 76e83fb
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [3 lines of output]
error in pytorch_tabular setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; Expected end or semicolon (after version specifier)
protobuf<=3.20.*
~~~~~~^
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
failed
CondaEnvException: Pip failed

I got exactly the same error

@koen-dejonghe I think you can safely skip fancyimpute. It is a problematic package. The other error, let me dig into and figure out.

As of 22.0, pip has made some changes which might be causing this issue. I've seen this for other libraries as well.
Issue on packaging
So, this is the solution:
I have removed timesynth and fancyimpute from the anaconda env. That along with the changes to statsforecast and python-kaleido make it working in my M1 Pro. (I haven't checked in statsforecast and python-kaleido changes because it seems to be Mac specific. I'll probably add it to the Readme as well.
Let me know if this works for you so that I can pin the issue and add it to readme.

With the new anaconda_env.yml , the conda environment installs without issues on my machine.
Thank you very much.

Mac M2/M1 problem:  AssertionError: Torch not compiled with CUDA enabled
I did the version corrections for statsforecast and python-kaleido and used mamba

Trying to install the environment on a M2 Macbook Air with the latest anaconda_env.yml and statsforecast>=0.6.0 and
python-kaleido>=0.1.0 leads to the below error message.
Any help with resolving this would be much appreciated.
Pip subprocess error:
  Running command git clone --filter=blob:none --quiet https://github.com/manujosephv/pytorch_tabular.git /private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-req-build-kdxixgmy
  Running command git checkout -b modern_ts_freeze --track origin/modern_ts_freeze
  Switched to a new branch 'modern_ts_freeze'
  branch 'modern_ts_freeze' set up to track 'origin/modern_ts_freeze'.
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [62 lines of output]
      /private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
      !!

              ********************************************************************************
              The license_file parameter is deprecated, use license_files instead.

              By 2023-Oct-30, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.

              See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
              ********************************************************************************

      !!
        parsed = self.parsers.get(option_name, lambda x: x)(value)
      running egg_info
      writing lib3/PyYAML.egg-info/PKG-INFO
      writing dependency_links to lib3/PyYAML.egg-info/dependency_links.txt
      writing top-level names to lib3/PyYAML.egg-info/top_level.txt
      Traceback (most recent call last):
        File "/Users/daniels/anaconda3/envs/modern_ts/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/Users/daniels/anaconda3/envs/modern_ts/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/Users/daniels/anaconda3/envs/modern_ts/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 341, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 323, in _get_build_requires
          self.run_setup()
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 338, in run_setup
          exec(code, locals())
        File "<string>", line 271, in <module>
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/__init__.py", line 107, in setup
          return distutils.core.setup(**attrs)
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/dist.py", line 1234, in run_command
          super().run_command(command)
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 314, in run
          self.find_sources()
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 322, in find_sources
          mm.run()
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 551, in run
          self.add_defaults()
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 589, in add_defaults
          sdist.add_defaults(self)
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/command/sdist.py", line 104, in add_defaults
          super().add_defaults()
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/sdist.py", line 251, in add_defaults
          self._add_defaults_ext()
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/sdist.py", line 336, in _add_defaults_ext
          self.filelist.extend(build_ext.get_source_files())
        File "<string>", line 201, in get_source_files
        File "/private/var/folders/mm/55vl94nd119gsfty5_1q66q40000gn/T/pip-build-env-pk92viix/overlay/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 107, in __getattr__
          raise AttributeError(attr)
      AttributeError: cython_sources
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

failed

CondaEnvException: Pip failed


Http service invocation in verion 1.12.3.

In what area(s)?

/area runtime
What version of Dapr?
1.12.3
Expected Behavior

When HttpResponse is httpstatus  != 200 then ResponseHeader contains duplicities -> it's wrong.
When HttpResponse is httpstatus  = 200 then  ResponseHeader contains no duplicity items.
Actual Behavior

When I call EndPoint (REST API c# over http service invocation http://localhost/3500/v1.0/invoke/test/method/test) and response HttpStatus != 200 then ResponseHeader cointains duplicities.

Steps to Reproduce the Problem
Create basic RestApi Endpoint and return anything else but httpStatus=200.
Release Note

RELEASE NOTE:

Thanks for the report. Taking a look


Restore xAxisConfig change

Accidentally reverted c47acb6 in my merge conflict resolution for #1633. Spotted by @iain-buclaw-sociomantic.

Current coverage is 65.48% (diff: 100%)

Merging #1636 into master will not change coverage

@@             master      #1636   diff @@
==========================================
  Files            52         52
  Lines          5925       5925
  Methods           0          0
  Messages          0          0
  Branches       1163       1163
==========================================
  Hits           3880       3880
  Misses         1838       1838
  Partials        207        207

Powered by Codecov. Last update 2f0172f...72f457e


Add Clear Block for Data Components

Clear Values block for Data components should be added. This also means that all data importing methods should not override the data (except maybe setting the elements manually)

Handled in #70


Could component Select support an attribute [nz-title] to show the too long words?

What problem does this feature solve?
Too long words in the select can not show perfectly
What does the proposed API look like?
nz-title="label"

use ng-template can resolve it.


Four is mapped to $

Hi
When I install Karabiner Elements, suddenly the 4-key in the numbers row is mapped to $. All other number keys work fine, but not 4. I use Danish keyboard layout.
Any suggestions?
Best regards,
Patrick

@patrkris Please share your karabiner.json and logs.

I have this in my karabiner.json:
{
    "profiles": [
        {
            "name": "Default profile",
            "selected": true,
            "simple_modifications": {
                "caps_lock": "escape"
            }
        }
    ]
}

I have attached the log.
karabiner.txt

It helped restarting my computer. I swear I tried that before, but for some reason it now works.


Cancel select new image

If I click 'select new image', the previous one is disappearing. So, if i will cancel image upload, i will see an empty space instead of previously uploaded image. Why the previous image being removed and how do i put it back?
UPDATE: sorry, my bad:
.cropit({
			imageState: {
				src: this.props.image,
				imageBackground: true,
			},
			exportZoom: exportZoom
		});

imageState.src was incorrect

Seems like you solved it.


add extension point for custom StringMatcher, and lua implementation

Commit Message: Add an extension point for custom StringMatcher implementations, with a Lua extension
Additional Description:
Risk Level: Low
Testing: New tests
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

Note: I pulled one commit into a separate PR (#32587) to make it easier to review.

Hmmm, there also a xds.type.matcher.v3.StringMatcher in xds repo, should we also update it?

@wbpcode this is a really good point. When we mirror types into the xds package namespace, we then have the challenge of forcing canonical evolution of those types to take place there and need a systematic way to bring them back into the legacy types for cases where features like this matter.
This is actually pretty messy today as this example shows. I think for this reason, I'd discourage this pattern in the future - regardless of the repository where a proto lives, we should stick to ODR and not replicate across package namespaces, at least if that type has some material amount of usage in the API already.

/retest

/retest

/retest


ensure same validations are run whether collecting errors or not

validate_destination only occurred in one branch of the validate method. This change refactors to ensure the validations are defined only once and then called appropriately.

@s01ipsist can you extend your PR and apply your solution at slo_logoutrequest.rb and logoutresponse.rb ?

@pitbulk done.

Thanks for contribute!


fix: Disable caching Secrets

Description

Changes proposed in this pull request:

Disable caching Secrets in controller-runtime client

Related Issues and Documents

Closes:
Related issues:
https://github.com/kyma-project/telemetry-manager/issues/464
Traceability

[x] The PR is linked to a GitHub Issue.
[x] New features have a milestone label set.
[ ] New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
[x] The corresponding GitHub Issue has a respective area label.
[ ] The follow-up issues (if any) are linked in the Related Issues section.

Testability
The feature is unit-tested:

[ ] Yes.
[x] No, because unit tests are not needed.
[ ] No, because of ...

The feature is e2e-tested:

[ ] Yes.
[ ] No, because e2e-tests are not needed.
[x] No, because behaviour of the operator should not change

Tests conducted for the PR:

Codebase

[ ] My code follows the Effective Go style guidelines.
[ ] The code was planned and designed following the defined architecture and the separation of concerns.
[ ] The code has sufficient comments, particularly for all hard-to-understand areas.
[ ] This PR adds value and shows no feature creep.
[ ] I have augmented the test suite that proves my fix is effective or that my feature works.
[ ] Adjusted the documentation if the change is user-facing.

/test all

/test all

/test all

/test all


MDE Module - Simplify entities parsing

The current logic is very cumbersome. It can be redone with the foolowing assumption:

There are nearly never account entities with only the aadUserId
Most of account entities will have an AccountName

But we could make it a dependancy for the deployment, can't we? If it was already imported with the same version, then it will not reimport it (I think?). Or maybe the general strategy would be to deploy everything anyways.

I think we would only ever deploy from the main deployment template so we would just need the parameter for the resourceId... If you did deploy a module directly then it would just be a matter of populating that string.


Feature request: Convert actions into IRC /me actions

It would be appreciated if it were possible -- perhaps as a configurable option, for discord-irc to automatically convert statements which have *star actions from start to finish* into /me actions.

PRIVMSG #channel :\001ACTION message

This is a duplicate of #143, so I'm closing it in favor of that.
There were some problems with figuring out how to implement this feature. For one – CTCP actions are often displayed by clients with the bot's name at the start. We could just send it as an action message directly, in which case something like this would happen:
<BridgeBot> <Throne3d> Hey there!
* BridgeBot waves

when really what we want is for it to somehow show that Throne3d is (I am) waving – it's ambiguous who's doing it, because it could have been someone else waving in response to me.
We could just append the username? But then you get something like this:
<BridgeBot> <Throne3d> Hey there!
* BridgeBot Throne3d waves

That looks weird, in my opinion, and would probably confuse me.
Alternatively, we could just send it as a regular message but format it differently:
<BridgeBot> <Throne3d> Hey there!
<BridgeBot> Throne3d waves

This seems (to me) like it's probably the best of the options, and it should be a configurable format, but I'm not actually sure if you could configure it from this to be a CTCP action. (Probably, if you can just insert \001ACTION  at the start of the custom format, and I think end it with \001.)
The main other problem I can see would be detecting a message as an action. Discord literally sends actions (e.g. /me waves) with underscores wrapped around them (e.g. _waves_), though this looks identical to with asterisks. We'd need to make sure the whole message is covered in the italics, with no breaks at any point, and that it's actually parsed as italics. We can probably do this with simple-markdown, which we use at the moment to parse markdown and convert it to IRC formatting.
(Responses should go on the other issue, #143, to consolidate this all.)


[WIP] add a console demo

Add a console which:

[x] takes in file name
[ ] takes in console input
[x] writes QR code to specified file ( in png format)
[ ] writes stream to console output

Hi @mishfit ,
Thanks for your support. I merged your changes. Is there a reason why you didn't added a parameter for file formats and console ouput? Otherwise I'll implement it during the next days.
Best regards,
Raffael

Oh, hey, I'm glad you liked it.
I labeled the PR '[WIP]' as in "work in progress" (I kind of took some cues from this article (see number 4).
I also, added some tasks to the PR (I haven't finished two of them).
I was hoping to get some criticism/review so I created the PR before everything was ready (I probably should have created an issue first).

D'Oh! I didn't see the WIP...sorry!
Nevertheless, if you sync with the master branch, you'll see that I already have implemented multiple filetype support.

Cool, I'll take a look at it.
Also, I took a dependency on the NDesk.Options package. I didn't know if you'd like that. It is entirely possible to pull the specific OptionSet code in if you'd prefer to limit the nuget package dependencies.

As long as those dependencies are only inside the demo apps and not inside the main library, it's no problem for me. Writing a new demo, because one of the dependencies drops support is not that problematic, than seeing the main library crashing, because someone dropped his lib.


changes related to bug 181 & bug 182

Fixes for following bug
181: Pre-deployment script does not perform imput validation for all parameters
182: If 'admin' is provided as the admin username during the pre-deployment script, the deployment fails

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


Questions about the data augmentation of MVX-Net

When the point cloud is augmented, how is the corresponding RGB image augmented, can you tell me where the corresponding code is?

For example, a RandomFlip3D  data augmentation pipeline is used while training, you can find the code here, it will flip points, 3D bboxes and 2D images and bboxes at the same time.

For example, a RandomFlip3D  data augmentation pipeline is used while training, you can find the code here, it will flip points, 3D bboxes and 2D images and bboxes at the same time.

Thanks for your answer, but how about GlobalRotScaleTrans? It seems that doesn't process 2D images and points at the same time.

For GlobalRotScale and Resize in pipeline, 2D and 3D data augmentation are done independently.

For GlobalRotScale and Resize in pipeline, 2D and 3D data augmentation are done independently.

Could you tell me where they are specifically?

GlobalRotScale is in pipelines/transforms_3d.py, Resize is directly used from mmdet package

Could you tell me where the MOCA(Multi-modality cut and paste) code is?

The final conversation is a duplicated version of #1143 . Close this issue because the original problem is resolved primarily.


Pieces are invisible/transparent

Changes done in ui v4.5.0 are causing the pieces to go missing.

my bad, the bug was a version mismatch on my end, not a bug.


Custom Voetlab tournament system

I'm sorry, didn't mean to make a PR on this repo, but on the master of my fork instead.