m.room.aliases is broken and here's how to fix it:

The room aliases system has several fundamental defects which render it unusable. These include security weaknesses. This issue will proffer two remedies to be applied in stages which will repair these defects and allow the system to be used as intended.
Background
The room aliases system is fundamental to the operation of the entire Matrix communication protocol. Aliases provide human-readable addressing for Matrix chat rooms. Without aliases, rooms can only be addressed by a single globally unique opaque identifier, the room_id. As an analogy, if the room_id was a networked computer's IP address, then room aliases would be the domain names pointing to the IP address. Contrary to an IP address on the internet, the Matrix protocol lacks any means by which to provide routing for room_id's, for example, by failing to provide an overlaying DHT. Due to this limitation, room aliases are required for finding rooms within the Matrix system.
How they work
The specification for room aliases is spread out over many places. They are first found in the Matrix Introduction, section 2.5.1. Their grammar is further detailed in the Matrix Appendix materials. They are stored and federated through a "state event" with the type m.room.aliases specified in the Client-Server protocol r0.3.0 section 10.5.1. Additionally, a suite of endpoints has been made available in the Client-Server protocol r0.3.0 section 7.2.
Example of the m.room.aliases event content:
"content":
{
    "aliases":
    [
        "#somewhere:localhost",
        "#another:localhost"
    ]
}

Defects
Poor key selection and value typing
The key of the m.room.aliases event (the state_key) is a homeserver domain and the value (content) an array of the aliases. With the key of the event being a homeserver domain, only one event can be used to query the aliases provided by a specific homeserver. To provide multiple aliases, an array type was selected for the content.
This immediately confuses client developers. Developers are accustomed to modifying the state of the room through the 6.4.1 rooms/state PUT endpoint. Intuitively, developers assume that they should faithfully copy the existing event content, update it with changes, and then submit it to that endpoint. This may or may not be the case depending on the implementation, but the 7.2 suite is also redundantly provided to perform these operations.
Lack of authority over the homeserver's specific key
Ideally, homeservers choose the aliases they believe best describe the room. For example, one homeserver may choose #wines:foo.com while another homeserver chooses #sommeliers:bar.fr. The chosen names are how users of their homeserver may find the room. If those aliases are changed or disappear, their users may no longer be able to find the room. The problem here is that an operator of any server with access to change one m.room.aliases event has access to change all of the other aliases events for other servers apart from their own.
Related work
A similar issue focusing specifically on the security implication was brought up by #625 over two years ago and it remains open with zero ideas. Not long after, #654 mentions an endpoint which is used by Riot but has remained unspecified for over three years as evidenced by #417. Overall, no substantive attempts have been made to solve this problem. Instead, its brokenness is assumed as gospel and more is built on top of the error rather than solving it.
Solution
By resolving this issue here, this effort hopes to:

Close all of the above issues and make the aliases system work as intended without all of the cautionary caveats and warnings.
Eliminate the secret endpoints used by Riot.
Eliminate the Client-Server 7.2 endpoint section.

Stage One
The first phase to address this problem is simple: implementations deny homeservers from updating m.room.aliases events which don't belong to them. In other words, the room's state machine denies a transition from an m.room.aliases event where state_key != origin.
Stage Two
The m.room.aliases event is replaced with an m.room.alias event. The new event is appropriately keyed and valued. As an example, consider the following form:
"origin": "foo.com",
"type": "m.room.alias",
"state_key": "#sommeliers:foo.com",
"content":
{
    /* available for discussion */
}

Conclusions
This problem exists because Matrix.org believes room state cannot be deleted. This is an erroneous belief. Room state is de facto deleted when it is the target of an m.room.redaction event.
The fact that Matrix.org has failed to implement deletions has leaked into the specification by building on this error by designing the content of the m.room.aliases event as an array such that it allows for aliases to be removed. This error has then lead matrix.org to the realizations of the above defects and has lead to further errors by way of the unspecified directory endpoints.
Matrix.org will have to implement proper behavior of their room state machine when a state event is the target of a redaction. Whether or not the specification should be updated to indicate this behavior de jure may be a matter for another issue.

oh thank goodness you came to our rescue.

Rescues are a speciality of mine.

alternatively expressed with slightly less snark: you have been banned from multiple Matrix rooms for continually shouting about how you would have designed Matrix better. Good for you, but shouting about it here isn't any more appreciated.

This problem exists because Matrix.org believes room state cannot be deleted.

I fail to see how you have reached the conclusion that the problems you refer to are anything to do with state deletion.

Room state is de facto deleted when it is the target of an m.room.redaction event.

No, room state is reset to an empty content on a redaction event. You can also do that without a redaction event.

The fact that Matrix.org has failed to implement deletions has leaked into the specification by building on this error by designing the content of the m.room.aliases event as an array such that it allows for aliases to be removed.

really, no.

You're not helping people take your protocol seriously by sabotaging attempts to address the issues and stifling discussion this way. You're also not making any attempt to fix it.

I'll address your response on the merits anyway

alternatively expressed with slightly less snark: you have been banned from multiple Matrix rooms for continually shouting about how you would have designed Matrix better. Good for you, but shouting about it here isn't any more appreciated.

This is an inappropriate and unprofessional ad hominem attack merely because you don't like what I have to say. Not cool.

This problem exists because Matrix.org believes room state cannot be deleted.

I fail to see how you have reached the conclusion that the problems you refer to are anything to do with state deletion.

Perhaps I didn't make this clear before you closed the issue but room state deletion is required for an effective implementation of the phase two solution.

Room state is de facto deleted when it is the target of an m.room.redaction event.

No, room state is reset to an empty content on a redaction event. You can also do that without a redaction event.

No, that's what your implementation does. The redaction event is a logical delete indication, out of fact.

The fact that Matrix.org has failed to implement deletions has leaked into the specification by building on this error by designing the content of the m.room.aliases event as an array such that it allows for aliases to be removed.

really, no.

The design of the array value is clearly because deletions are not supported (perhaps redactions didn't even exist at that point) -- so really, yes.

ok, I'm sorry I was hasty. I saw assumptions about the design of the protocol which I (still) feel are incorrect, and closed the issue on that basis rather than stopping to consider the whole of your proposal. I'll reopen this so that we can discuss the issues you raise, should you so wish.
The design of the m.room.aliases event as an array predates my involvement with the project, but, looking at the evolution of the implementation, I believe it just felt like the natural structure for listing the aliases supported by a server. I don't think it was anything to do with support or otherwise for removing state from a room. It may also be worth noting that a number of the directory endpoints predated the existence of the m.room.aliases event.
I understand your proposal for "stage one" and agree that it is one potential solution to solving the current byzantine split of alias information. Indeed it is rather elegant, though would require a bump in the event authorisation rules, which is non-trivial to achieve in practice.
However, to be honest, I don't understand why "stage two" is necessary or even particularly helpful. Can you explain further?

I believe it just felt like the natural structure for listing the aliases supported by a server.

Indeed, multiple aliases for a domain may exist. Therefor it may feel natural to organize this data by:

Selecting the domain as the key.
Selecting a list (array) as the value.

I don't think it was anything to do with support or otherwise for removing state from a room.

By selecting the aforementioned state_key and content list value, the room can feature support for both adding and deleting room aliases by replacing the m.room.aliases state event entirely. Because removing state from a room is not supported, this is the only way to feature the deleting of aliases.

It may also be worth noting that a number of the directory endpoints predated the existence of the m.room.aliases event.

I should also correct a word choice from my original post. The specified endpoints at present are not truly redundant. Their purpose appears to add atomicity for updating the m.room.aliases list content. Consider when two clients attempt to update that event through the state endpoint: each will acquire the existing content, modify the list, and release the new content. One of those clients will overwrite the other's changes. The endpoints provide transactionality to avoid this.

However, to be honest, I don't understand why "stage two" is necessary or even particularly helpful. Can you explain further?

"Stage one" may address the second defect, the security weakness, but it does not address both defects. "Stage two" is comprehensive because it solves the problem the way most problems in computer science and engineering are tackled: by breaking it down into smaller parts. The m.room.alias event introduces granularity. The current list value in the m.room.aliases content lacks granularity. This is a pitfall. Its detrimental effects are seen with an exception for this event being made where clients must use REST endpoints to modify it. Other state events are directly updated as events. This is an inelegance.
There is no benefit for the specification to designate aliases content as a list merely because multiple aliases are in play. There is already implementation precedent for collections of state events by type. Consider that the m.room.member events are granular. There is not a single m.room.member state event listing all of the members in a content array type. Implementations are tasked with managing collections of state: the m.room.alias is just another collection.
In fact, state deletion support is not truly necessary for an m.room.alias event, though it would be preferred. Instead, the content can contain a key such as {"active":true}. Existing implementations redacting this event, destroying its content, would actually deactivate the alias; even if the state_key remains present in the implementation's mapping. I don't find this to be elegant. It would be ideal if implementations treated redactions of a state event as a de-mapping. As the maintenance of state mappings are an implementation issue, I stand by my conclusion that implementations are at fault for allowing a state_key to remain in their mapping which points to an empty content. That is useless.

Right, so tldr: the reason for stage 2 is to provide atomicity. Fair enough.

to follow up on part of this, jevolk defined stage one as:

The first phase to address this problem is simple: implementations deny homeservers from updating m.room.aliases events which don't belong to them. In other words, the room's state machine denies a transition from an m.room.aliases event where state_key != origin.

As far as I can tell, this has always been the case in practice, though it only made it into the written specification as of https://github.com/matrix-org/matrix-doc/pull/1591.

Given that stage one of the original proposal is redundant (as it has always been the case in practice), I have split stage two out to #2259 and will close this.


Allow "UNPROTECTED" to be set for the "Do Not Protect" SLA domain...

… and make sure that the SLA Domain name passed in resolves a valid SLA Domain ID
Description
Allow UNPROTECTED to be passed in as the SLA Domain name, and error out if the provided SLA domain name does not exist.
Related Issue
#11
Motivation and Context
Currently you cannot set "Do Not Protect" with this plugin via any means I could locate. Also passing in an SLA domain name that does not exist results in an infinite loop until the workflow is cancelled.
How Has This Been Tested?
This has been validated in our vRealize environment during automated deployments of virtual machines. A manual test with an invalid SLA domain name was used to trigger the failure to resolve the SLA ID path.
Screenshots (if appropriate):
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

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

Checklist:
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x] My code follows the code style of this project (as far as I can tell it does)
[x] My change requires a change to the documentation (I didn't see any relevant documentation for this plugin going over Do Not Protect)
[x] I have updated the documentation accordingly. (See above)
[x] I have read the CONTRIBUTION document.
[x] I have updated the CHANGELOG file accordingly for the version that this merge modifies (What changelog file?)
[x] I have added tests to cover my changes (vRO doesn't really allow for unit testing in the traditional sense, but I did test this change)
[x] All new and existing tests passed (I tested with valid SLA domain names, the UNPROTECTED special case for "Do Not Protect", and nonexistant SLA domain names for failing on a nonexistant SLA domain.

I just realized this is sourced from a copy of the packagye from 4/8, but was last updated on 5/22. Let me update our plugin and redo this change and I'll update my master branch.

Hi @bender-the-greatest - is this PR ready for review?

@rfitzhugh Sorry, I got pulled into something else and haven't had the time to update our version of the plugin and see if my changes work with the latest.

Closing due to inactivity. Please re-open if PR is ready for review.


Fix typo in RabbitBinderConfigurationProperties

Substitute adminAdresses with adminAddresses.

Thanks @detached - do you have a CLA on file?
As a note, we should leave the old property in (at least for 1.0.x) and mark it as deprecated - to be removed in the future, as current applications that use the incorrect form and upgrade will break.

@mbogoevici - yes I have.
May I create a issue for keeping track?

Sure - please create an issue - thanks!

Rebased, merged w/https://github.com/spring-cloud/spring-cloud-stream/commit/c1f4ba66d3f2d51d257304ed86192a3590f30f01 and additional corrections in https://github.com/spring-cloud/spring-cloud-stream/commit/daf454410cedf73f059ecfc71bd012627a2e79df
Also cherry-picked for 1.0.x


Makefile: fix embedding gitCommit

Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

LGTM assuming happy tests.  Thanks @AkihiroSuda !

/approve

/lgtm


Search toggle defaults to active by default

Who is this for?
new search
What is it doing for them?
This has already been deployed, this keeps the toggles up to date.

I did wonder, but I thought keeping this up to date would give whoever is looking at the codebase an easy way of knowing what's currently widely available.


libdoc tool support reStructuredText format output

Now we use a web service that can render html to show all test libraries documentation, because all the documentations must be convert to html format.
i hope we can use directly gitlab or github to display all test libraries dcoumentation. so there are two solutions:

gitlab or github support to render html
libdoc can support reStructuredTextformat output, and gitlab or github now support render reStructuredText format as html

Could you please explain a bit more thoroughly how this should work in practice?
Notice that Libdoc already now supports reST as input format. Couldn't you just use that and let your external tools render reST docs directly?

@pekkaklarck Thanks for your reply.
I use gitlab for my test libraries source code management, issue tracking, code reviews.
I want to publish my test libraries documentation on gitlab, unfortunately, gitlab can render reST but can not render html.
So I have to install another web server to show libraries documentation, just as apache http server.
A test library documentation can output a html file by libdoc tool, and i think it can output a reST file easily.

I'm not sure have I understood this correctly, but I don't think Libdoc could realistically convert docs e.g. in Robot's own documentation format to reST. If docs already are in reST, the we obviously could just output them as-is, but I don't know how much benefits what would give. Most of the value in Libdoc outputs is in its HTML formatting, and I don't see how we could change that to reST.
Do you have a concrete idea how reST output should work in practice? Would you be willing to implement such functionality yourself and provide a pull request.

I don't think implementing this enhancement is feasible.


denv.it

(my personal website)
https://denv.it
68.07 KB transferred (70.97 KB)

Wow, you're loading 70kb just to show your name and mail address. It looks great but that is so not the purpose of 250kb.club.
But I will add your blog URL which can offer much more with even a bit less transferred data.

I'll fix ot someday. It's just because of Google fonts unfortunately :(


Address status of pylti1.3

Due to other time commitments, the maintainer of pylti1p3 is unable to maintain that library beyond occasional bugfixes. Since pylti1p3 is a crucial dependency of django-lti it's worth considering how to address this moving forward.
A few possibilities that have been raised:

Asking the maintainer of pylti1p3 if he would be willing to transfer or share ownership
Creating a fork of pylti1p3
Pulling pylti1p3 code directly into django-lti

These all sound like good solutions, in that order of preference, too.
pylti1p3 hasn't been updated for at least two years.  It's been a long time since the last bugfix.
If UMich (either @academic-innovation or @tl-its-umich-edu) has the cycles available to maintain the module, I'm sure other organizations that depend on it would be appreciative.  Accepting ownership or maintaining a fork would accomplish that.
Pulling pylti1p3 code into django-lti would work, but UMich would miss an opportunity to give back to the open source community.  That is, unless the pulling in would also allow others to use pylti1p3 from the django-lti package independent of the Django features.  (IOW, like making a pylti1p3 fork with django-lti "grafted" onto it.)

Pulling pylti1p3 code into django-lti would work, but UMich would miss an opportunity to give back to the open source community. That is, unless the pulling in would also allow others to use pylti1p3 from the django-lti package independent of the Django features. (IOW, like making a pylti1p3 fork with django-lti "grafted" onto it.)

I think the long term goal under this scenario would be to gradually remove all of the parts of pylti1p3 that make it framework agnostic. I've found that building on top of abstractions like MessageLaunch, LaunchDataStorage, and ToolConf add a lot of complexity to a Django specific library like django-lti, and I'd love to get the value that pylti1p3 provides without paying that cost 😅


[SPARK-41765][SQL] Pull out v1 write metrics to WriteFiles

What changes were proposed in this pull request?

Pull out the metrics which is in InsertIntoHiveTable and InsertIntoHadoopFsRelationCommand to WriteFiles.
Why are the changes needed?

Move metrics to the right place.
Does this PR introduce any user-facing change?

yes, the SQL UI metrics changed from V1WriteCommand to WriteFiles
with spark.sql.optimizer.plannedWrite.enabled disable and enable:

How was this patch tested?

fix and improve test

cc @cloud-fan

The commit related metrics should still belong to the insert command

Seems task commit time is not related to insert command, driver side only do job commit. But if we split them, the UI will seem confused. That's why I moved both of them to WriteFiles. Any idea ?

thanks, merging to master/3.4 (for the to-be-released planned write feature)!


[Bug] [seatunnel-connectors-v2] [connector-clickhouse]   import data only to   one machine  where the host has  multiple hosts[ host1:8123,host2:8123]]

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
import data only to   one machine  where the host has  multiple hosts[ host1:8123,host2:8123]]
where  the   table in  clickhouse-sink  config   which engine is  not  set  to   the type of  'Distributed'  。 the data   import  only to the one machine  , in  this case  the machine  is  host1 。  the machine nameed host2 have not any data
SeaTunnel Version
seatunnel 2.3.1
SeaTunnel Config
{
    "filter" : {},
    "transform" : [],
    "sink" : [
       {
             "database" : "damaiX",
             "password" : "",
             "save_mode" : "overwrite",
             "clickhouse.socket_timeout" : 100000,
             "host" : "host1:8123,host2:8123",
             "bulk_size" : 5000000,
       "fields" : [
                 "id",
                 "gazj",
                 "dt"
              ],
             "plugin_name" : "clickhouse",
             "table" : "adm_dmp_user_id_replica",
             "username" : ""
     }
    ],
     "source" : [
        {
            "result_table_name" : "table_name",
            "pre_sql" : "select id,gazj, dt from table ",
             "plugin_name" : "hive"
         }
        ],
    "env" : {
       "spark.executor.memory" : "28g",
       "spark.sql.catalogImplementation" : "hive",
       "spark.default.parallelism" : 72,
       "spark.streaming.batchDuration" : 5,
       "spark.app.name" : "XXXXX.app.name",
       "spark.ui.port" : 13000,
       "spark.executor.cores" : 4,
       "spark.executor.instances" : 9,
       "spark.sql.shuffle.partitions" : 72,
       "spark.dynamicAllocation.enabled" : false
   }
 }

Running Command
sh ~/bin/setart-seatunnel-spark.sh --master yarn --deploy-mode client -config  xxx.config

Error Exception
function error

Zeta or Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@wuxizhi777 This is probably as expected,Similar problem link #5435

ok. I  will close the issue


Issue on using moment type

On creating option for min/maxDate
Default: false
Accepts: date, moment, string

This is my code:
const DATE_PICKER_OPTIONS = {
    useCurrent: true,
    format: 'Do MMM',
    minDate: moment()
};

function initDatePicker() {
    $('.datetimepicker-input').datetimepicker(DATE_PICKER_OPTIONS);
}

But I have a weird effect is that when click in the input, the date picker not open.
Only after I click again, the date picker show up.
Same problem when I'm using moment([]) or  moment({});

You should probably ask this question over at https://github.com/tempusdominus/bootstrap-4


Build a Business Application Using CAP for Node.js

Mission URL: https://developers.sap.com/mission.cp-starter-extensions-cap.html
In the Home page, the total time displayed for executing the scenario is incorrect.
Actual result : 1hr is displayed.

Expected result : 1hr 20mins should be displayed.

Regards,
Nidhi

Fixed in the Tutorial Navigator. In the Starter Scenarios, don;t know if it takes some time.
@AnnikaGonnermann Can you look at this?

Hi @thecodester:
changes show in the Cockpit: https://cockpit.hanatrial.ondemand.com/cockpit/#/home/trial


Revert "[TypeRecontruction] Remove handling of InOutTypes."

This reverts commit 751550be1a8e556d3cedfbb51c81c762a6d50b20.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci smoke test and merge


add version into consolidated commit message

only if all packages have the same version
Fixes #222

I'm assuming our including the version when shared-version = true supersedes this.


way to navigate back from puzzle screen

I'm thinking adding a logo on the header bar and tap to go back to home
Or, swipe from left to right to go back

Added logo to the header bar.  Works for dad, so we're good for now.  I might add swipe later but that has its own issues.


Update MediaPlayer.java

A little bug here : when the mediaplayer's reset() method is called while playing, the value of mCurrentPosition would not be reset, I need to update the progress of seekbar by the callback of mediaplayer's state change event, so I add one line of code and my problem is sloved.
Thanks for this wonderful implementation!

Thank you very much! Can you tell me why you put it into stop() although you mention reset()? Do you know if Android's MediaPlayer also resets the playback position on stop()? And from which "state change event" do you update your progress bar?

Android's MediaPlayer does not reset the playback position on stop(), i.e. getPlaybackPosition() returns the position at which the player was stopped, not 0. After release() it throws an IllegalStateException.
This means merging this request would lead to different behavior between the API MediaPlayer and MediaPlayer-Extended, which is not desired.


Write filter for TorBrowser

oh dear, the browser actually discovered the tor circuit's exit relay ip address. this seems very wrong. this is way more authority than the browser needs.
here's the log output from roflcoptor running in watch mode during the browser startup:
{{{
ROFLCopTor 2016/04/21 16:48:44 INFO/tor: New ctrl connection from: <IP_ADDRESS>:42134
ROFLCopTor 2016/04/21 16:48:44 A->T: [authenticate xxx]
ROFLCopTor 2016/04/21 16:48:44 A->T: [setevents stream]
ROFLCopTor 2016/04/21 16:48:44 A<-T: [250 OK]
ROFLCopTor 2016/04/21 16:48:44 A<-T: [250 OK]
ROFLCopTor 2016/04/21 16:48:44 INFO/tor: New ctrl connection from: <IP_ADDRESS>:42138
ROFLCopTor 2016/04/21 16:48:44 A->T: [AUTHENTICATE xxx]
ROFLCopTor 2016/04/21 16:48:44 A<-T: [250 OK]
ROFLCopTor 2016/04/21 16:48:44 A->T: [GETINFO net/listeners/socks]
ROFLCopTor 2016/04/21 16:48:44 A<-T: [250-net/listeners/socks="<IP_ADDRESS>:9050"]
ROFLCopTor 2016/04/21 16:48:44 A<-T: [250 OK]
ROFLCopTor 2016/04/21 16:48:44 A<-T: [650 STREAM 8564 NEW 0 www.torproject.org:443 SOURCE_ADDR=<IP_ADDRESS>:44260 PURPOSE=USER]
ROFLCopTor 2016/04/21 16:48:46 A<-T: [650 STREAM 8564 SENTCONNECT 5880 www.torproject.org:443]
ROFLCopTor 2016/04/21 16:48:46 A<-T: [650 STREAM 8564 REMAP 5880 <IP_ADDRESS>:443 SOURCE=EXIT]
ROFLCopTor 2016/04/21 16:48:46 A<-T: [650 STREAM 8564 SUCCEEDED 5880 <IP_ADDRESS>:443]
ROFLCopTor 2016/04/21 16:48:47 A<-T: [650 STREAM 8565 NEW 0 ocsp.digicert.com:80 SOURCE_ADDR=<IP_ADDRESS>:44264 PURPOSE=USER]
ROFLCopTor 2016/04/21 16:48:47 A<-T: [650 STREAM 8565 SENTCONNECT 5881 ocsp.digicert.com:80]
ROFLCopTor 2016/04/21 16:48:47 A<-T: [650 STREAM 8565 REMAP 5881 <IP_ADDRESS>:80 SOURCE=EXIT]
ROFLCopTor 2016/04/21 16:48:47 A<-T: [650 STREAM 8565 SUCCEEDED 5881 <IP_ADDRESS>:80]
ROFLCopTor 2016/04/21 16:48:48 A<-T: [650 STREAM 8566 NEW 0 dist.torproject.org:443 SOURCE_ADDR=<IP_ADDRESS>:44268 PURPOSE=USER]
ROFLCopTor 2016/04/21 16:48:48 A<-T: [650 STREAM 8566 SENTCONNECT 5882 dist.torproject.org:443]
ROFLCopTor 2016/04/21 16:48:48 A<-T: [650 STREAM 8566 REMAP 5882 <IP_ADDRESS>:443 SOURCE=EXIT]
ROFLCopTor 2016/04/21 16:48:48 A<-T: [650 STREAM 8566 SUCCEEDED 5882 <IP_ADDRESS>:443]
ROFLCopTor 2016/04/21 16:48:50 A<-T: [650 STREAM 8568 NEW 0 <IP_ADDRESS>.$9CD77810A49B52A333666689B334447DCAD40591.exit:9001 PURPOSE=DIR_FETCH]
ROFLCopTor 2016/04/21 16:48:50 A<-T: [650 STREAM 8568 SENTCONNECT 5883 <IP_ADDRESS>.$9CD77810A49B52A333666689B334447DCAD40591.exit:9001]
ROFLCopTor 2016/04/21 16:48:50 A<-T: [650 STREAM 8530 CLOSED 5859 <IP_ADDRESS>:443 REASON=DONE]
ROFLCopTor 2016/04/21 16:48:50 A<-T: [650 STREAM 8561 CLOSED 5879 check.torproject.org:443 REASON=DONE]
ROFLCopTor 2016/04/21 16:48:50 A<-T: [650 STREAM 8568 SUCCEEDED 5883 <IP_ADDRESS>.$9CD77810A49B52A333666689B334447DCAD40591.exit:9001]
ROFLCopTor 2016/04/21 16:48:50 INFO/tor: Closed client connection from: <IP_ADDRESS>:42134: EOF
}}}
here's watch mode again when the browser's new identity feature is selected:
{{{
ROFLCopTor 2016/04/21 16:48:00 INFO/tor: New ctrl connection from: <IP_ADDRESS>:42126
ROFLCopTor 2016/04/21 16:48:00 A->T: [AUTHENTICATE xxx]
ROFLCopTor 2016/04/21 16:48:00 A<-T: [250 OK]
ROFLCopTor 2016/04/21 16:48:00 A->T: [SIGNAL NEWNYM]
ROFLCopTor 2016/04/21 16:48:00 A<-T: [250 OK]
}}}

ok... i've tricked tor browser into thinking everything is ok.
in this dev branch:
https://github.com/david415/roflcoptor/tree/13.add_multi_oz_listener.0
this rule set right here:
https://github.com/david415/roflcoptor/blob/13.add_multi_oz_listener.0/filters/tbb.json
however it requires that issue #13 be resolved first... that would be this pull request pending review and merge:
https://github.com/subgraph/roflcoptor/pull/14

@leif pointed out that my Tor Browser filter rules were too restrictive in not letting the browser see the circuit building info messages that contain the IP addresses of each tor relay hop in the circuit built.... so I fixed that. And I also noticed I had previously forced TBB to do NULL auth so I changed it to allow any authentication.


Toggle menu bar problem.

VSCode Version: 1.30.0 insider
OS Version: win 10 enterprise insider preview, build 18282

Steps to Reproduce:

View -> Appearance -> Toggle menu bar  only make text in this bar disappear, but the bar itself remains.
I have tried in settings file about window.menuBarVisibility and no difference made.
This is different with sublime which will give the editor an extra line.

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

@OpenWaygate The menu bar in VS Code is already inline with the title bar giving you that extra line. Toggling the menu bar does as intended, remove it from view. The title bar should not be hidden just because the menu bar is hidden. If you want even more editor space, you can try full screen mode (F11) which removes the title bar and menu bar by default.

I had the same issue using i3wm. In order to fix it, I had to go into Settings and search for window.titleBarStyle and set it to native. Just in case anyone runs into the same issue after upgrading VSCode.


DND disabled when Dragging in same element twice or more at a time.

I have used dndkit in my project, I am facing a big issue that when I am moving a draggable element from one droppable container to another droppable container its working fine but when I am trying to move that same element again into another container whole dnd is disabled and its not working. This is a major issue I can't find out this problem. If there is any solution can anyone help me out. Also sometime draggable element is moved in new container and also have in same container too. I mean its getting duplicate and then when i am moving one of them another one is moving. its really bad.
https://www.loom.com/share/531beb5706e340ca85fb20ee5c2d1e2e?sharedAppSource=personal_library

@tarequl143 I am facing a very similar issue using the useSortable hook to order items in a list.
I am passing the items of the list into my component as prop an items prop. And I noticed that this bug would occur whenever this items prop changes (eg after reload from server). Similar to your video, the items would still show the :hover state on mouseover but dragging them has no effect at all.
Help very much appreciated :)

@tarequl143 / @whytspace can you share a reproduction case of the issue on CodeSandbox?

I had a similar issue. My problem was not paying careful attention to the following line in the <DragOverlay /> docs

make sure that the components rendered within the drag overlay do not use the useDraggable hook.

@whytspace The issue was in our code. Disabled issue only happen when 2 Draggable elements has same reference or same ID. I have solved the issue and now there is no disabled issue. You can check if you have any render issue or state change issue. In my case when I was dragging and dropping an element another container I was updating my local file state and after getting success result from API. I was updating my global state based on Dragged and Dropped container ID. My purpose was to make less API request. But it was making same element in another container with same reference.

@clauderic I have solved the issue so you can closed the issue. But there is few more problem in dndkit I faced but that is not in React dnd. Like When I am dragging an element into another container its just blinking within 2 containers. Its getting same result for 2 container collision detection. Also Overflow container has a big issue. Like a container has so many items and few items is overflow and When i am dragging an element from one container to another container the overflow conatiner's overflow items are catching dragggin element. It should not be happend like that.

Here is a video for both problem. Blinking between 2 container and overflow items catching Dragging element. If you notice when I was dragging Paypal and Skrill it should be detected in test container as test container was near of Dragging element but it was detecting overflow items container and overflowed items also.
https://www.loom.com/share/44e422764121426b8026cb433d4adc08

@whytspace if you couldn't solve the disabled issue yet. You can contact me I will be happy to help you.

Going to close this issue, feel free to re-open more specific issues @tarequl143

@tarequl143 Can you please share or give a reference about the code? I am facing the same issue. I have more than one tab whose ids are the same.


Azure Function Multi Documents Input

modified MiniSDK for Custom Text and response to handle more than a document per call as was mentioned in the issue #65

you need to rebase your branch
@ZulaMostafa


Extracting BERT features throws out_of_bounds exceptions

When I run extract_bert_features.sh I get many of the following out of bounds exceptions. Here are more details:
Data.py exception  51 index 1126 is out of bounds for axis 0 with size 1041 exceptions while trying to access bert_to_orig and orig_to_bert maps. here is some debugging output that I generated:
orig_to_bert_map.shape, orig_to_bert_end_map.shape, bert_to_orig_map.shape, self.gold_starts.shape=
(1041,) (1041,) (2192,) (266,)

I added requirements.txt file, please update if the issue persists with the correct library versions.


Update CODE_OF_CONDUCT.md

Separated the last sentence from it's preceding sentence.
referred to issue #2898

@Arkaroy147  Thank you for PR 🚀

@alicanerdurmaz thanks for accepting my pr
Sorry for being greedy, but is this pr eligible for your hacktoberfest refine swag?😅


feature request: dynamic related options

I am wondering if it is possible to have something like
"vscodeGitCommit.template": ["{type}({scope}{sub}): {message}"],
"vscodeGitCommit.variables": {
    "scope": [
      {
        "label": "worker",
        "detail": "individual worker"
      },
      {
        "label": "srv",
        "detail": "support service for all workflows"
      }
    ],
    "sub": "*scope",
    "worker": [
      {
        "label": "worker1"
      },
      {
        "label": "worker2"
      }
    ],
    "srv": [
      {
        "label": "srv1"
      },
      {
        "label": "srv2"
      }
    ],
}

So people can select scope and select related sub based on the scope they selected.

Hmmm, I see what you want, at this time it's not possible, but that's interesting, I have to think about how to do it, it add conditionnal to the settings


Method to destroy streams

Feature Request
Checklist
[x] I've searched the bugtracker for similar feature requests including closed ones.
[x] I will add the enhancement label to the issue.
Description
The use case is for the execution of tests using pytest. For any particular session, there may be hundreds of tests. For each test, I'd like to generate a log file.
logger = Logger("mylogger", log_path="log1.txt", format="{message}")
logger.info("Just printing an info message from the test logger")
logger.update_disable_file(True)
logger = Logger("mylogger", log_path="log2.txt, format="{message}")
logger.info("Just printing another info message from the test logger")

I noticed that I need to disable the previous logger's file stream using logger.update_disable_file(True) or it will result in duplicated messages. However, if I do this 100 times for each session, I've noticed that there are 100 streams being kept in memory.
Can we have a method to destroy streams? Or is there another way to do this?

@chinghwayu As of now there is not method to do that. I think that's a necessary feature and I will add a dedicated method for that.
As for now, you can use the following workaround:
from simber import Logger

logger = Logger("new-logger", log_path="test")
logger.info("Just a test")

# Now in order to remove the file stream.
file_stream = list(logger._streams)[0]

# Remove the stream from the set of streams and delete it after that
logger._streams.remove(file_stream)
del file_stream.stream

# Now add more streams to here accordingly.

Later on, I'll probably add a method that will accept an OutputStream instance and it will remove that from the logger.

@chinghwayu Also if you want to log to different files, you shouldn't create a new instance everytime? Just remove the old file stream instance and add a new file stream and log using the same logger.

@chinghwayu Please consider taking a look at 574e6784069d8b70d1f53bd29b3ea373bf113a22. I added a method named remove_stream that expects an OutputStream object.
Moreover, also added a streams property to get the list of OutputStreams connected to the logger.
You can clone the unstable repo and test out the changes, if you find any issues, you can comment here!

@chinghwayu Added a new release with the changes. You would be able to use that instead. Use the remove_stream method.
The equivalent to remove a stream from the above code would be something like this:
from simber import Logger

logger = Logger("new-logger", log_path="test")
logger.info("Just a test")

file_stream = logger.streams[0]
logger.remove_stream(file_stream)

# Now add more streams to here accordingly.


Create elastic-agent-project-board.yml

Will add the issue to the Elastic Agent project board as soon as one of the team label is used (Control plane or data plane)

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-04-13T13:43:28.176+0000

Duration: 9 min 24 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
92

Skipped
1

Total
93

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

@jlind23 Can you create the same automation for https://github.com/elastic/elastic-agent-client


Visual Studio seems not to have all min() function versions

Needed to change the line 8972 if the current version to:
std::string(start + offset, min(length, max_length - offset));
in order to make it compile

It should still be std::min, but yeah, I don't see any reason to use the initializer_list version instead of the two parameter version here.

I did not know that MSVC does not support the initializer-list version - according to cppreference it is C++11. Anyway, I shall replace it with the other version.

@j-k Could you please check if the fix works for you?

I didn't know that it wouldn't support it either until this issue was posted.  :)

cloned today, had the same issue, the suggested fix in the first post worked.
VS2015 community V. 14.0.25420.1 compiling x86

Thanks!

I should have added the error msgs and line number:
Error	C2589	'(': illegal token on right side of '::'	[...]\json.hpp	8936
Error	C2059	syntax error: '::'	LibSonarProc	[...]\json.hpp	8936
it compiled for me when I changed std::min ->min
Wish I was using g++

I don't understand: I fixed this with commit 9b764ee5d671b41255d390ab9089f12036b2d38a. Does it still not work?

Line 8936:
return std::string(start + offset, std::min(length, max_length - offset));
This fails to compile in VS2015 with the errors I show above.
If I change to this, it will compile:
return std::string(start + offset, min(length, max_length - offset));

Which version of MSVC is this?

C:\Program Files (x86)\Microsoft Visual Studio 14.0>cl
Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24210 for x86
Copyright (C) Microsoft Corporation.  All rights reserved.

This version is not supported, see https://github.com/nlohmann/json#supported-compilers.

OK, thank you.

No worries. :)

Just to be clear,
Version 19.00.24210  is the MS command-line compiler version,
as I posted above,  the Visual Studio version is 2015, V. 14.0.25420.1

This is strange - this version is supported. But AppVeyor has no issues building and executing the tests.

I had another look: AppVeyor compiles the code without issues with Microsoft (R) Build Engine version 14.0.25420.1: https://ci.appveyor.com/project/nlohmann/json/build/job/74yfdd5tjwk0i7s1
Maybe this is related: #603


Api key not found

Even though I pasted the correct api key in the config file. Any help?

Same for me

You need to restart the app once so the key can load. If it's still broken, please show me what your log says.

I don't know what else to add, it's working for me even though I've reinstalled Windows since making this script. Read this again then try redownloading: README#obtaining-a-steamgriddb-api-key Hope you can get it to work.

Working now, thx.


Multi threading debug not working

Dear Developers,
I am currently trying to debug a QT multi-threaded application. I use the qt_thread module for the multithreading. However, the visual code debugger won't stop at my breakpoint when they are inside the thread code. Is there a way to enable this?
Thanks in advance,
Greetings,

This should work, please provide the following info:

Python version
Python environment type (venv, virtual env, pyenv, conda, etc)
OS Version
Steps to repro the issue (please provide a simple sample that we can use at our end)
Any errors you may have encountered (please see the Python output channel) or the console window (go into Help -> Toggle Developer Tools menu).

Dear @DonJayamanne,
Thanks a lot for looking into the problem. Here the requested information:

python 3.7.2
miniconda enviroment
Windows 10 Pro (10.0.17763 Build 17763)
Visual studio code - Insider (V1.32.0-insider)
Anaconda extension pack (v1.0.1)
ms.python.python (v2019.1.0)

Steps to reproduce:

Open code example below in visual studio code insider build.
Place debug point inside execute_this_fn.
Start debugger and click on the DANGER! buton on the pyqt GUI.
See the debugger pass the bullet point without stopping.

Example code:
Provided by the blog of Martin Fitzpatrick
from PyQt5.QtGui import *
from PyQt5.QtWidgets import *
from PyQt5.QtCore import *

import time
import traceback, sys

class WorkerSignals(QObject):
    '''
    Defines the signals available from a running worker thread.

    Supported signals are:

    finished
        No data

    error
        `tuple` (exctype, value, traceback.format_exc() )

    result
        `object` data returned from processing, anything

    progress
        `int` indicating % progress

    '''
    finished = pyqtSignal()
    error = pyqtSignal(tuple)
    result = pyqtSignal(object)
    progress = pyqtSignal(int)

class Worker(QRunnable):
    '''
    Worker thread

    Inherits from QRunnable to handler worker thread setup, signals and wrap-up.

    :param callback: The function callback to run on this worker thread. Supplied args and
                     kwargs will be passed through to the runner.
    :type callback: function
    :param args: Arguments to pass to the callback function
    :param kwargs: Keywords to pass to the callback function

    '''

    def __init__(self, fn, *args, **kwargs):
        super(Worker, self).__init__()

        # Store constructor arguments (re-used for processing)
        self.fn = fn
        self.args = args
        self.kwargs = kwargs
        self.signals = WorkerSignals()

        # Add the callback to our kwargs
        self.kwargs['progress_callback'] = self.signals.progress

    @pyqtSlot()
    def run(self):
        '''
        Initialise the runner function with passed args, kwargs.
        '''

        # Retrieve args/kwargs here; and fire processing using them
        try:
            result = self.fn(*self.args, **self.kwargs)
        except:
            traceback.print_exc()
            exctype, value = sys.exc_info()[:2]
            self.signals.error.emit((exctype, value, traceback.format_exc()))
        else:
            self.signals.result.emit(result)  # Return the result of the processing
        finally:
            self.signals.finished.emit()  # Done

class MainWindow(QMainWindow):

    def __init__(self, *args, **kwargs):
        super(MainWindow, self).__init__(*args, **kwargs)

        self.counter = 0

        layout = QVBoxLayout()

        self.l = QLabel("Start")
        b = QPushButton("DANGER!")
        b.pressed.connect(self.oh_no)

        layout.addWidget(self.l)
        layout.addWidget(b)

        w = QWidget()
        w.setLayout(layout)

        self.setCentralWidget(w)

        self.show()

        self.threadpool = QThreadPool()
        print("Multithreading with maximum %d threads" % self.threadpool.maxThreadCount())

        self.timer = QTimer()
        self.timer.setInterval(1000)
        self.timer.timeout.connect(self.recurring_timer)
        self.timer.start()

    def progress_fn(self, n):
        print("%d%% done" % n)

    def execute_this_fn(self, progress_callback):
        for n in range(0, 5):
            time.sleep(1)
            progress_callback.emit(n*100/4)

        return "Done."

    def print_output(self, s):
        print(s)

    def thread_complete(self):
        print("THREAD COMPLETE!")

    def oh_no(self):
        # Pass the function to execute
        worker = Worker(self.execute_this_fn) # Any other args, kwargs are passed to the run function
        worker.signals.result.connect(self.print_output)
        worker.signals.finished.connect(self.thread_complete)
        worker.signals.progress.connect(self.progress_fn)

        # Execute
        self.threadpool.start(worker)

    def recurring_timer(self):
        self.counter +=1
        self.l.setText("Counter: %d" % self.counter)

app = QApplication([])
window = MainWindow()
app.exec_()

Closing as the issue has been resolved upstream


QOS != 0 gives exception

Hello,
When publishing with QOS of 1 or 2 I get the following stack trace
Traceback (most recent call last):
File "e:\code\python\pythontest\venv\lib\site-packages\uvicorn\protocols\http\h11_impl.py", line 396, in run_asgi
result = await app(self.scope, self.receive, self.send)
File "e:\code\python\pythontest\venv\lib\site-packages\uvicorn\middleware\proxy_headers.py", line 45, in call
return await self.app(scope, receive, send)
File "e:\code\python\pythontest\venv\lib\site-packages\fastapi\applications.py", line 199, in call
await super().call(scope, receive, send)
File "e:\code\python\pythontest\venv\lib\site-packages\starlette\applications.py", line 111, in call
await self.middleware_stack(scope, receive, send)
File "e:\code\python\pythontest\venv\lib\site-packages\starlette\middleware\errors.py", line 181, in call
raise exc from None
File "e:\code\python\pythontest\venv\lib\site-packages\starlette\middleware\errors.py", line 159, in call
await self.app(scope, receive, _send)
File "e:\code\python\pythontest\venv\lib\site-packages\starlette\exceptions.py", line 82, in call
raise exc from None
File "e:\code\python\pythontest\venv\lib\site-packages\starlette\exceptions.py", line 71, in call
await self.app(scope, receive, sender)
File "e:\code\python\pythontest\venv\lib\site-packages\starlette\routing.py", line 566, in call
await route.handle(scope, receive, send)
File "e:\code\python\pythontest\venv\lib\site-packages\starlette\routing.py", line 227, in handle
await self.app(scope, receive, send)
File "e:\code\python\pythontest\venv\lib\site-packages\starlette\routing.py", line 41, in app
response = await func(request)
File "e:\code\python\pythontest\venv\lib\site-packages\fastapi\routing.py", line 201, in app
raw_response = await run_endpoint_function(
File "e:\code\python\pythontest\venv\lib\site-packages\fastapi\routing.py", line 148, in run_endpoint_function
return await dependant.call(**values)
File ".\main.py", line 60, in func
await fast_mqtt.publish("test", "Hello from Fastapi", qos=1) #publishing mqtt topic
File "e:\code\python\pythontest\venv\lib\site-packages\fastapi_mqtt\fastmqtt.py", line 226, in publish
return await self.loop.run_in_executor(self.executor, func)
File "C:\Python38\lib\concurrent\futures\thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "e:\code\python\pythontest\venv\lib\site-packages\gmqtt\client.py", line 291, in publish
self._persistent_storage.push_message_nowait(mid, package)
File "e:\code\python\pythontest\venv\lib\site-packages\gmqtt\storage.py", line 12, in push_message_nowait
return asyncio.ensure_future(self.push_message(mid, raw_package))
File "C:\Python38\lib\asyncio\tasks.py", line 660, in ensure_future
loop = events.get_event_loop()
File "C:\Python38\lib\asyncio\events.py", line 639, in get_event_loop
raise RuntimeError('There is no current event loop in thread %r.'
RuntimeError: There is no current event loop in thread 'ThreadPoolExecutor-0_0'.
C:\Python38\lib\asyncio\base_events.py:1860: RuntimeWarning: coroutine 'HeapPersistentStorage.push_message' was never awaited
handle = None  # Needed to break cycles when an exception occurs.

Using QOS of 0 works fine
I took the example on the site and change the config to my server and managed to reproduce it.  Here it is:
from fastapi_mqtt.fastmqtt import FastMQTT
from fastapi import FastAPI
from fastapi_mqtt.config import MQQTConfig
import ssl
mqtt_config = MQQTConfig()
def config():
server_cert =
client_cert =
client_key =
context = ssl.create_default_context(ssl.Purpose.SERVER_AUTH, cafile=server_cert)
context.load_cert_chain(certfile=client_cert, keyfile=client_key)

mqtt_config.ssl = context
mqtt_config.password = <MY PASSWORD>
mqtt_config.username = <MY USERNAME>
mqtt_config.host = <MY SERVER>
mqtt_config.port = 8883

config()
fast_mqtt = FastMQTT(
config=mqtt_config
)
app = FastAPI()
fast_mqtt.init_app(app)
@fast_mqtt.on_connect()
def connect(client, flags, rc, properties):
fast_mqtt.client.subscribe("/mqtt") #subscribing mqtt topic
print("Connected: ", client, flags, rc, properties)
@fast_mqtt.subscribe("mqtt/+/temperature", "mqtt/+/humidity")
async def home_message(client, topic, payload, qos, properties):
print("temperature/humidity: ", topic, payload.decode(), qos, properties)
return 0
@fast_mqtt.on_message()
async def message(client, topic, payload, qos, properties):
print("Received message: ",topic, payload.decode(), qos, properties)
return 0
@fast_mqtt.on_disconnect()
def disconnect(client, packet, exc=None):
print("Disconnected")
@fast_mqtt.on_subscribe()
def subscribe(client, mid, qos, properties):
print("subscribed", client, mid, qos, properties)
@app.get("/")
async def func():
await fast_mqtt.publish("test", "Hello from Fastapi", qos=1) #publishing mqtt topic
return {"result": True,"message":"Published" }

@alanaquilina Thank you for the report. I have used QOS 0,1,2 everything was perfectly working. Could we figure out what broker do you use for testing? As I see you are using windows for testing, can try to check this on Linux machine to see if the error still raises.
Interesting error raises from asyncio library of python.

Hello,
First of all thanks for your reply!
I am using Mosquito 1.5.7 on a pi 4.
I tried the same code on my PI and got the same error.
I removed the SSL and got the same error
Might be worth noting that the connection is downgrading to MQTT 3.11
Thanks
Alan

Hi,
This might be the version of Mosquito you are using. is there are any possibility you can upgrade it?  I have used the version above 2 works fine.
Also, one more thing to test, can you change the version in config parameter to 4. fastapi-mqtt uses gmqtt module on top of it.
https://github.com/wialon/gmqtt/blob/master/gmqtt/mqtt/constants.py#L53

I upgraded Mosquitto to 2.0.10 and used both v5 and v4 in the client version.  Same error on QOS != 0 .

I am trying to produce the solution, let me I will update you.

I have found very the issue occurs. Actually, I have tested QoS with client subscribe not publish.
I have submitted PR to gmqtt-PR. Once it is merged will release it with the new version.
Thanks for finding this.

Thank you for fixing!
On Saturday, 3 April 2021, 19:22:53 CEST, Sabuhi @.***> wrote:
I have found very the issue occurs. Actually, I have tested QoS with client subscribe not publish.
I have submitted PR to gmqtt-PR. Once it is merged will release it with the new version.
Thanks for finding this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

This should now work at the latest version, could please check and let me know.I have updated documentation as well.

Confirmed Working!  Thanks a lot!
On Tuesday, 6 April 2021, 19:27:10 CEST, Sabuhi @.***> wrote:
This should now work at the latest version, could please check and let me know.I have updated documentation as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


[P4] Allow private plugins

User might desire plugin-type processing that is hyper-specific and not much help to the community.  Implement a mechanism for user to create plug-ins that are private
https://discord.com/channels/1192313062041067520/1246638931857113150/1250991753524281426

I love this idea, it would be helpful to test some ideas before you make them public as well -- similar to GPTs in ChatGPT where you can make your own but then share them with the community as well.


Code dnd API

get API key and fetch data
place response into input boxes

we have this and the random name and number generator


AMQP-697: CorrelationAwareMessagePostProcessor [1.7.x]

JIRA: https://jira.spring.io/browse/AMQP-697
Add support for modifying publisher confirms CorrelationData during message post processing.
Change AsyncRabbitTemplate to use a stateless MPP, move all state to the CorrelationData.
Conflicts:
spring-amqp/src/main/java/org/springframework/amqp/core/MessagePostProcessor.java
spring-rabbit/src/main/java/org/springframework/amqp/rabbit/AsyncRabbitTemplate.java
spring-rabbit/src/test/java/org/springframework/amqp/rabbit/AsyncRabbitTemplateTests.java
spring-rabbit/src/test/java/org/springframework/amqp/rabbit/core/RabbitTemplatePublisherCallbacksIntegrationTests.java
Resolved.
cherry-pick to 1.6.x

... and cherry-picked as https://github.com/spring-projects/spring-amqp/commit/8a468846942935009cd40748a91d551194199196


MSID: 97229 Version: 2 DOI: 10.1101/2<IP_ADDRESS>5073

MSID: 97229
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>5073
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=97229
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>5073

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/97229v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>5073
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/97229/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: [journal-ref-article-title] This journal reference (id c80) has no article-title element.
warn: [journal-ref-text-content] This journal reference (id c95) has untagged textual content - M S, . Is it tagged correctly?
warn: [journal-ref-text-content] This journal reference (id c96) has untagged textual content - J Y, N M, TL M, JM O. . Is it tagged correctly?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c26) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c89) has a publication-type='other'. Is that correct?
warn: [empty-parentheses-presence] p element contains empty parentheses ('[]', or '()'). Is there a missing citation within the parentheses? Or perhaps this is a piece of code that needs formatting?
warn: [empty-parentheses-presence] p element contains empty parentheses ('[]', or '()'). Is there a missing citation within the parentheses? Or perhaps this is a piece of code that needs formatting?


New version: calibre.calibre version 7.4.0

Pull request has been created with Komac v1.11.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Hi @pxwiz please be aware that the InstallerUrl you have included is unstable and likely to break upon the next release (#133004).

A similar change should be made to all calibre.calibre packages.


IZPACK-1640 - fix panel processors not being visited in console mode

IZPACK-1640 - fix panel processors not being visited in console mode

Looks like this feature has been merged back into master.  When do you all think there will be a new version released with this patch in it?

Looks like this feature has been merged back into master.  When do you all think there will be a new version released with this patch in it?

@jlanzarotta You can try to use the current SNAPSHOT that is deployed to Sonatype Snapshot Repo.

@jlanzarotta You can try to use the current SNAPSHOT that is deployed to Sonatype Snapshot Repo.

I ended up building from source and installing locally.  Unfortunately, it looks as if the fix, at least in my case, did not work...  I ended up getting around the issue by writing my own ProcessHandler since I needed to get this fix out quickly...

I ended up building from source and installing locally.  Unfortunately, it looks as if the fix, at least in my case, did not work...  I ended up getting around the issue by writing my own ProcessHandler since I needed to get this fix out quickly...

@jlanzarotta Ok, maybe you can provide a PR or a test that shows the problem?

@jlanzarotta Ok, maybe you can provide a PR or a test that shows the problem?


[icu:x64-windows-static] build failure

Host Environment

OS: Windows 10
Compiler: Visual Studio 2019?

To Reproduce
Steps to reproduce the behavior:
./vcpkg install icu:x64-windows-static
Failure logs
-- Using msys root at D:/vcpkg/downloads/tools/msys2/20befe66cf35bf25
-- Configuring x64-windows-static-rel
-- Configuring x64-windows-static-rel done
-- Configuring x64-windows-static-dbg
-- Configuring x64-windows-static-dbg done
-- Package x64-windows-static-rel
-- Restarting Build without parallelism because memory exceeded
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:146 (message):
    Command failed: D:/vcpkg/downloads/tools/msys2/20befe66cf35bf25/usr/bin/bash.exe --noprofile --norc -c "make -j 5"
    Working Directory: D:/vcpkg/buildtrees/icu/x64-windows-static-rel
    See logs for more information:
      D:\vcpkg\buildtrees\icu\make-build-x64-windows-static-rel-out.log
      D:\vcpkg\buildtrees\icu\make-build-x64-windows-static-rel-err.log
      D:\vcpkg\buildtrees\icu\make-build-x64-windows-static-rel-out-1.log
      D:\vcpkg\buildtrees\icu\make-build-x64-windows-static-rel-err-1.log

Call Stack (most recent call first):
  ports/icu/portfile.cmake:164 (vcpkg_execute_build_process)
  scripts/ports.cmake:142 (include)

Error: Building package icu:x64-windows-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: icu:x64-windows-static
  Vcpkg version: 2021-01-13-d67989bce1043b98092ac45996a8230a059a2d7e

Additional context
I already reinstalled vcpkg completely, but it still fails

Please provide the following logs:
D:\vcpkg\buildtrees\icu\make-build-x64-windows-static-rel-out.log
D:\vcpkg\buildtrees\icu\make-build-x64-windows-static-rel-err.log

make-build-x64-windows-static-rel-err.log
make-build-x64-windows-static-rel-out.log

Thanks for posting this issue @Nightloewe
I cannot reproduce this on my machine.
From make-build-x64-windows-static-rel-out.log, we get the error info:
LINK.EXE -subsystem:console -DEBUG -INCREMENTAL:NO -OPT:REF -OPT:ICF  -nologo -out:../../bin/gencfu.exe gencfu.o ../../lib/sicutu.lib ../../lib/sicuin.lib ../../lib/sicuuc.lib ../../stubdata/sicudt.lib advapi32.lib
LINK : fatal error LNK1104: cannot open file '..\..\bin\gencfu.exe'
config.status: creating tools/gencfu/gencfu.1

Could you please check if gencfu.exe exists in /cygdrive/d/vcpkg/buildtrees/icu/x64-windows-static-rel/bin/gencfu.exe?

@NancyLi1013 I checken it and the file does not exist.

@Nightloewe
Could you please help confirm if you installed Virus software and also disabled it on your machine?

@NancyLi1013 You mean Antivirus software? Yes, I have installed Bitdefender Antivirus. I tried again and now the compilation works, I did not change anything on my system.

@NancyLi1013 You mean Antivirus software? Yes, I have installed Bitdefender Antivirus. I tried again and now the compilation works, I did not change anything on my system.

Yes, Antivirus software. So you can build it successfully now, right?

@NancyLi1013 You mean Antivirus software? Yes, I have installed Bitdefender Antivirus. I tried again and now the compilation works, I did not change anything on my system.

Yes, Antivirus software. So you can build it successfully now, right?

Yes, it worked without disabling antivirus software.

Thanks for your feedback. I'm closing this issue since it cannot be reproduced now.


How to find AppVersion, RscVersion, MstVersion?

I try to review the code to mod for JP use.
I found these variable [AppVersion, RscVersion, MstVersion]
I'm not sure it's up to date or not and how to find them
@serenitygrant  @OGVENDETTA  or anyone can you guide me?

check with packetdecoder,
if you want to check with ur phone or emulator
you must same network, ex wifi setting http proxy to your ip packetdecoder ... or try to check raw data with fiddler

Thank you, I got it and mod the program.
for JP ver now the data are
AppVersion = 1032
RscVersion = 664
MstVersion = 1943


Server is down:  Error 522

Server is down since morning, please look into this.

Could you share your output of: https://images.weserv.nl/cdn-cgi/trace
This can help us identify which Cloudflare location is causing problems.

Hi @andrieslouw ,
I checked this morning, issue has been resloved.
Here is output of: https://images.weserv.nl/cdn-cgi/trace
fl=49f101
h=images.weserv.nl
ip=2405:201:4014:2003:bd86:dace:a036:9ffb
ts=1604566887.823
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36
colo=MRS
http=http/2
loc=IN
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off

I have started facing some connectivity issue again. Please suggest some solution

@finesofttech It seems that you were banned today by our rate limiter at 11:16:04 and automatically unbanned at 12:16:10 (UTC). You can check your current rate limit quota here: https://images.weserv.nl/quota.

I am also experiencing this issue; here's the trace output from https://images.weserv.nl/cdn-cgi/trace
fl=137f19
h=images.weserv.nl
ip=<IP_ADDRESS>
ts=1605207251.84
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:82.0) Gecko/20100101 Firefox/82.0
colo=PIT
http=http/2
loc=US
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off

I also get a 522 trying to load https://images.weserv.nl/quota

We have reports of multiple locations with 522-errors, on multiple sites provided through Cloudflare. Thank you all for the reports, it seems there are some issues with some transit-providers.


MA death data seems odd

Hi,
MA death data
2020-03-22 -> 5
2020-03-21 -> 51
My understanding is that all numbers are cumulative. So MA can't be right

Good catch! We fixed the typo, thank you


AeroDyn14 Driver

AeroDyn14 driver contains USE AeroDyn_Types instead of USE AeroDyn14_Types. Looks like the code needs to be updated to reflect the changes since introduction of AeroDyn v15.

For future reference, I've updated cmake to include aerodyn14_driver in the build and I've updated AD_Driver to use the aerodyn14 types and function calls. However, it looks like updates need to be made to the registry
Scanning dependencies of target aerodyn14_driver
[ 95%] Building Fortran object modules-local/aerodyn14/CMakeFiles/aerodyn14_driver.dir/src/AD_Driver.f90.o
/Users/rmudafor/Development/openfast/modules-local/aerodyn14/src/AD_Driver.f90:68:23:

    InitInData%ADOptions%ADFile = 'MyInputFileName.inp'
                       1
Error: 'adoptions' at (1) is not a member of the 'ad14_initinputtype' structure
/Users/rmudafor/Development/openfast/modules-local/aerodyn14/src/AD_Driver.f90:77:67:

    CALL AD14_Init( InitInData, u(1), p,  x, xd, z, OtherState, y, m, TimeInterval, InitOutData, ErrStat, ErrMsg )
                                                                   1
Error: Symbol 'm' at (1) has no IMPLICIT type
/Users/rmudafor/Development/openfast/modules-local/aerodyn14/src/AD_Driver.f90:106:85:

       CALL AD14_CalcOutput( Time, u(1), p, x, xd, z, OtherState, y, ErrStat, ErrMsg )
                                                                                1
Error: Type mismatch in argument 'm' at (1); passed INTEGER(4) to TYPE(ad14_miscvartype)
/Users/rmudafor/Development/openfast/modules-local/aerodyn14/src/AD_Driver.f90:115:84:

       call AD14_UpdateStates( Time, u(1), p, x, xd, z, OtherState, ErrStat, ErrMsg )
                                                                                1
Error: Type mismatch in argument 'n' at (1); passed TYPE(ad14_inputtype) to INTEGER(4)
/Users/rmudafor/Development/openfast/modules-local/aerodyn14/src/AD_Driver.f90:127:69:

    CALL AD14_End( u(1), p, x, xd, z, OtherState, y, ErrStat, ErrMsg )
                                                                     1
Error: Type mismatch in argument 'm' at (1); passed INTEGER(4) to TYPE(ad14_miscvartype)

This is available at https://github.com/rafmudaf/openfast/tree/bugfix/aerodyn14_driver

I would be surprised if anyone ever used AD14's driver. I'm pretty sure it was just there to help John compile when he converted AD13 to the FAST modularization framework. It doesn't do anything useful does it? Other than verify that AD14 can compile and possibly run without seg faults?
ADOptions is probably left over from AD13.

@bjonkman no, it doesn't do much. It just calls the AD14 init, calc output and update states over three time steps, and the end method. It doesn't actually read an input file.
In fact, looking at this driver in more detail I'm wondering was it ever actually used to drive a working AD14? It looks if John used it in development he stopped pretty early as the InitInData variable which is passed to AD14_Init isn't actually initialized at all.

I personally would just delete the AD14 driver. AD14 is supposed to be phased out anyway, right?

@bjonkman I completely agree.
@michaelasprague @jjonkman @ghaymanNREL any objection to this? I've created a pull request for this at https://github.com/OpenFAST/openfast/pull/92.
On the question of phasing out AD14, I think that deserves its own issue.

ps new issue created for ad14 phase out #93


[SUPPORT] typo on website https://hudi.apache.org/docs/deployment.html#deploying

"In a singe run mode" on https://hudi.apache.org/docs/deployment.html#deploying

Open a PR ? :)

also for this one it has true and off, maybe it should show false
autoTuneInsertSplits(true)Permalink
Property: hoodie.copyonwrite.insert.auto.split
Should hudi dynamically compute the insertSplitSize based on the last 24 commit’s metadata. Turned off by default.

also for this one it has true and off, maybe it should show false
autoTuneInsertSplits(true)Permalink
Property: hoodie.copyonwrite.insert.auto.split
Should hudi dynamically compute the insertSplitSize based on the last 24 commit’s metadata. Turned off by default.

@tooptoop4 This is turned ON by default. We should fix the doc. Interested in opening a PR for these two changes?

Added jira : https://issues.apache.org/jira/browse/HUDI-1100 @tooptoop4 : if you are interested, please assign yourself.


Cleanup ACT event names and docstrings

Events are now prefixed by memory/network depending on their source, as well as unused for events that are defined but not used. The internal events have been left alone. All missing events have been added, and a consistency pass was run over the major class docstrings. I'll do a few more passes of docs including the native nari events in a later PR.

Thanks for the review. Changes are addressed, but I think we need to rethink our exceptions at some point as they're spread between actlogutils and nari.utils, with some duplication, and little naming consistency.


Make pybuilder Unicode safe

When writing unit tests that contain Unicode strings pybuilder fails with an error:
BUILD FAILED - 'ascii' codec can't encode character u'\xe4' in position 118: ordinal not in range(128)

Running the same build with -X showed that pybuilder fails to display a message containing Unicode strings:
  File ".../venv/local/lib/python2.7/site-packages/pybuilder/plugins/python/unittest_plugin.py", line 70, in addFailure
    self.failed_test_names_and_reasons[test] = '{0}: {1}'.format(exception_type, exception).replace('\'', '')
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 118: ordinal not in range(128)
------------------------------------------------------------
BUILD FAILED - 'ascii' codec can't encode character u'\xe4' in position 118: ordinal not in range(128)

Manually adding u in front of the string literal in unittest_plugin.py solved the problem.
In this test I used assertEquals to compare two Unicode strings and they where different so that pybuilder wanted to show print the difference and failed.

Nice catch, thanks for the report.

Thanks a lot! Is this already released? If not, can you say when?

I'll release it immediately once I have fixed the issues on python3 (see travis :-/).

I just release pybuilder==0.10.56 with the fix. Thanks for your bug report!

Thanks a lot. I was not aware of the future import solution.
What do you think about the issues explained in http://stackoverflow.com/questions/809796/any-gotchas-using-unicode-literals-in-python-2-6?

Since PyBuilder is python 3 compatible in theory there should be no problems when adding the unicode_literals pragma anywhere.
But we don't have that pragma on every file, so the mix of both (which is one of the problems described) could very well hurt us on python2.
But I'm not really a fan of adding a ton of boilerplate code in every file (in theory we would also need the real division and print function pragmas everywhere).
We never really discussed how we want to tackle this problem actually. I rather tend to add the future imports as required, and would expect the tests to catch problems like mixing up unicode and non-unicode strings on python2 due to the future import.
Does this answer your question? What do you think?

This is the first time that I dig into Python and Unicode at this level, I
am just learning here :-)
The main question I am asking myself is if we should start to use future
imports as the basis for our work or keep working with Python2 "best
practice" for Unicode.
I am afraid that the Unit Tests do not give complete coverage in this case
as Python automatically determines the encoding for stdin and stdout.
On 16 March 2015 at 11:37, Maximilien Riehl<EMAIL_ADDRESS>wrote:

Since PyBuilder is python 3 compatible in theory there should be no
problems when adding the unicode_literals pragma anywhere.
But we don't have that pragma on every file, so the mix of both (which is
one of the problems described) could very well hurt us on python2.
But I'm not really a fan of adding a ton of boilerplate code in every file
(in theory we would also need the real division and print function pragmas
everywhere).
We never really discussed how we want to tackle this problem actually. I
rather tend to add the future imports as required, and would expect the
tests to catch problems like mixing up unicode and non-unicode strings on
python2 due to the future import.
Does this answer your question? What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/pybuilder/pybuilder/issues/121#issuecomment-81569986.

Python3 is the only way forward, so we should definitely be using the future imports where applicable (which is mostly everywhere for unicode_literals, since all strings are unicode by default).
There's no way to turn the future stuff on globally, unfortunately (except for command line flags).


Update development practices

Update development practices
Address:

Immutable collections and Java 9 unmodifiable collections
using var
stress keeping good quality of test code

See:

https://prestosql.slack.com/archives/CP1MUNEUX/p1596307579355300
https://prestosql.slack.com/archives/CP1MUNEUX/p1596193971338400
https://prestosql.slack.com/archives/CP1MUNEUX/p1596109740319900
https://prestosql.slack.com/archives/GKZ8GS0SK/p1596318373040200

@sopel39 updated

@martint @electrum @dain Can any of you please review it and possibly approve it. I would like to have two sides of ocean kind of approval for this.

Maybe squash last two commits.

Addressed @losipiuk comments


Panic when compiling invalid wasm with bad element segment count

Extract invalid-segment-count.tar.gz to crates/fuzzing/tests/regressions/invalid-elem-segment-count.wasm
Append this to crates/fuzzing/tests/regression.rs:
#[test]
fn compile_invalid_elem_segment_count() {
    let data = include_bytes!("./regressions/invalid-elem-segment-count.wasm");
    oracles::compile(data, wasmtime_jit::CompilationStrategy::Cranelift);
}

Run cargo test -p wasmtime-fuzzing and get this panic:
test compile_invalid_elem_segment_count ... FAILED

failures:

---- compile_invalid_elem_segment_count stdout ----
thread 'compile_invalid_elem_segment_count' panicked at 'element items', src/libcore/option.rs:1187:5
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:84
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:61
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1030
   5: std::io::Write::write_fmt
             at /rustc/f1b882b55805c342e46ee4ca3beeef1d1fa2044b/src/libstd/io/mod.rs:1412
   6: std::io::impls::<impl std::io::Write for alloc::boxed::Box<W>>::write_fmt
             at src/libstd/io/impls.rs:141
   7: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:65
   8: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:50
   9: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:188
  10: std::panicking::default_hook
             at src/libstd/panicking.rs:202
  11: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:464
  12: std::panicking::continue_panic_fmt
             at src/libstd/panicking.rs:373
  13: rust_begin_unwind
             at src/libstd/panicking.rs:302
  14: core::panicking::panic_fmt
             at src/libcore/panicking.rs:82
  15: core::option::expect_failed
             at src/libcore/option.rs:1187
  16: core::option::Option<T>::expect
             at /rustc/f1b882b55805c342e46ee4ca3beeef1d1fa2044b/src/libcore/option.rs:347
  17: wasmparser::parser::Parser::read_element_entry_body
             at /home/fitzgen/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmparser-0.42.1/src/parser.rs:445
  18: wasmparser::parser::Parser::read_wrapped
             at /home/fitzgen/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmparser-0.42.1/src/parser.rs:917
  19: <wasmparser::parser::Parser as wasmparser::parser::WasmDecoder>::read
             at /home/fitzgen/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmparser-0.42.1/src/parser.rs:1055
  20: <wasmparser::validator::ValidatingParser as wasmparser::parser::WasmDecoder>::read
             at /home/fitzgen/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmparser-0.42.1/src/validator.rs:670
  21: <wasmparser::validator::ValidatingParser as wasmparser::parser::WasmDecoder>::read_with_input
             at /home/fitzgen/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmparser-0.42.1/src/validator.rs:689
  22: wasmparser::validator::validate
             at /home/fitzgen/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmparser-0.42.1/src/validator.rs:885
  23: wasmtime_fuzzing::oracles::compile
             at crates/fuzzing/src/oracles.rs:57
  24: regressions::compile_invalid_elem_segment_count
             at crates/fuzzing/tests/regressions.rs:19
  25: regressions::compile_invalid_elem_segment_count::{{closure}}
             at crates/fuzzing/tests/regressions.rs:17
  26: core::ops::function::FnOnce::call_once
             at /rustc/f1b882b55805c342e46ee4ca3beeef1d1fa2044b/src/libcore/ops/function.rs:223
  27: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
             at /rustc/f1b882b55805c342e46ee4ca3beeef1d1fa2044b/src/liballoc/boxed.rs:942
  28: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:81
  29: std::panicking::try
             at /rustc/f1b882b55805c342e46ee4ca3beeef1d1fa2044b/src/libstd/panicking.rs:265
  30: std::panic::catch_unwind
             at /rustc/f1b882b55805c342e46ee4ca3beeef1d1fa2044b/src/libstd/panic.rs:395
  31: test::run_test_in_process
             at src/libtest/lib.rs:570
  32: test::run_test::run_test_inner::{{closure}}
             at src/libtest/lib.rs:473
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

failures:
    compile_invalid_elem_segment_count

test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out

cc @yurydelendik -- this seems to originate inside wasmparser

This got fixed upstream in wasmparser -- is there anything blocking the update in Wasmtime? Do we have to coordinate an update with cranelift as well?


Adding revpi connect 4 support

In this PR we are adding support for revpi-connect-4. This is very similar to what we did for the revpi-connect-s here https://github.com/balena-os/balena-raspberrypi/pull/1016
@floion is there a way you can run the tests for this? This seems to be working on our devices but we are happy to fix issues that might arise during testing.
@nbuchwitz would be great if you can have a look at this.

Can one of the admins verify this patch?

@floion just spoke with Kenna last week. We will ship you the hardware (afaik to a partner in UK). If it will help I can reroute the shipment to you. Just let me know.

Thanks @wickywaka we'll review it.
@nbuchwitz great, thanks. No need to have it rerouted here, for the moment we want to have the boards with our partner in the UK.

@floion I think this is ready for testing. Anyway we can get this merged quickly so that we can continue with testing our devices.

For now I will just try to create a working with changes proposed by @nbuchwitz and once we have a working image, then I will squash all the commits.
@floion Why don't you guys squash the commits automatically from a PR (may be with a template message) so that all the PR is just one commit. That way the contributor does not have to do all the rebases manually and can focus on final result.

@resin-jenkins test this please

@resin-jenkins test this please

Some of the tests seems to be failing. Can you check the logs and see what is missing?

@resin-jenkins test this please

@resin-jenkins test this please

@wickywaka the failures are not related to this PR

@floion test-raspberrypi will always fail until https://github.com/balena-os/balena-raspberrypi/pull/1081 merges

@floion test-raspberrypi will always fail until #1081 merges

Any idea when would it be merged?

@resin-jenkins test this please

@floion Can you see why are these tests failing? Is there a way for us to run these tests so that we can reduce the iteration time.

@wickywaka looking into it. The failure seem to be related to flaky network issues. The tests need to be ran on the automated test rig, so it would not help if you run the tests on your side.

@floion now that #1083 is merged, can we get this device type released?


Chapter 8 BigGAN error in Orthogonal

When I run the cell with the OrthogonalRegularizer, I always get this error message.

It works fine with Tensorflow 2.2.0. What version did you use?
Blas is linear algebra library but I'd expect Nvidia's cuBLAS to be used. It may be that cublas has not been installed correctly.
One thing you can try is to disable GPU by changing this line on top of the notebook
tf.config.experimental.set_visible_devices(gpus[0], 'GPU')
to
tf.config.experimental.set_visible_devices([], 'GPU')
Alternatively, try this on Google Colab but be sure to install the correct Tensorflow version.


[autocomplete][table] How to insert an Autocomplete in a table row?

Steps to reproduce
Here is the code : https://codesandbox.io/p/sandbox/cold-sun-wpw9j6

Current behavior
I am gonna use <Autocomplete> in the <Table>. All things are looking fine. But I found this warning from console.

Warning: validateDOMNesting(...): <div> cannot appear as a child of <tr>

.
How can I fix this? Is there any other way to solve this?
Expected behavior
No warning.
Context
I need to use <Autocomplete> in <Table> with no warning.
Your environment
Google Chrome Version 121.0.6167.162 (Official Build) (64-bit)
Windows 10 Enterprise N
Search keywords: Autocomplete

@Gao990 Your sandbox doesn't have any console errors! This is the right way to do it:
<TableRow>
  <TableCell>
    <Autocomplete />
  </TableCell>
<TableRow>


Made EnableThrottlingAttribute.GetLimit() a virtual method so that it can be overridden in subclasses

Having the GetLimit() method in EnableThrottlingAttribute be virtual really helps with creating subclasses that inherit EnableThrottlingAttribute.
I created class that inherited EnableThrottlingAttribute, where I defined a throttling policy at compile time. At runtime, it pulls the throttling policy from the web.config file. In order to make this work, I had to make GetLimit() virtual and override it, reading the limit settings from the configuration.

@stefanprodan can ypu please approve this PR?
will help me a lot :)
i have the same problem as @Maultasche


HotBackup download timouts

My Environment

ArangoDB Version:        3.7.12
Deployment Mode:       Cluster
Deployment Strategy:   Docker Compose
Configuration:               Single Machine lots of containers
Infrastructure:               own
Operating System:        WSL2
Total RAM in your machine:        32 GB
Disks in use:        SSD

Component, Query & Data
Affected feature:
HotBackup Download
Problem:
I need to evalutate HotBackup -> Upload -> Download -> Restore cycle. For that I have a local docker compose cluster
docker-compose.txt
Eval License + secrets removed
Now uploading works as expected with (total size in minio 2 MiB)
{
  "config": {
    "S3": {
      "type": "s3",
      "provider": "minio",
      "env_auth": "false",
      "access_key_id": "minio",
      "secret_access_key": "minio123",
      "endpoint": "http://minio:9000",
      "region": "us-east-1"
    }
  },
  "id": "2021-07-23T00.30.43Z_string",
  "remoteRepository": "S3://arango/"
}

now I kill the arango containers and volume to simulate total cluster destruction:
then I initiate the backup download with the same config as above resulting in the following status:
{
    "error": false,
    "code": 200,
    "result": {
        "Timestamp": "2021-07-23T01:41:17Z",
        "BackupId": "2021-07-23T00.30.43Z_string",
        "DBServers": {
            "PRMR-9597c24c-b413-4992-80ab-7dae45c75e3e": {
                "Progress": {
                    "Total": 1,
                    "Time": "2021-07-23T01:41:17Z",
                    "Done": 1
                },
                "Status": "COMPLETED"
            },
            "PRMR-ba03b134-6afd-4e91-ad3b-d8607ce7f7fb": {
                "Progress": {
                    "Total": 1,
                    "Time": "2021-07-23T01:41:17Z",
                    "Done": 1
                },
                "Status": "COMPLETED"
            },
            "PRMR-aa1332c5-8f0f-46bf-a5b2-bc411c2d8b1b": {
                "Progress": {
                    "Total": 1,
                    "Time": "2021-07-23T01:41:17Z",
                    "Done": 1
                },
                "Status": "COMPLETED"
            }
        }
    }
}

yet when I call backup list its empty
{
    "error": false,
    "code": 200,
    "result": {
        "list": {}
    }
}

and list with "2021-07-23T00.30.43Z_string" gives the following error after a minute or so
    "code": 400,
    "error": true,
    "errorMessage": "timeout waiting for all db servers to report backup list",
    "errorNum": 1457

update:
the same thing happens if i don't kill the cluster but just delete the local backup and then download it again.
and ofcourse restore fails aswell - not just the list op
{
  "code": 500,
  "error": true,
  "errorMessage": "read failed for file '/var/lib/arangodb3/backups/2021-07-24T00.13.27Z_string/META': No such file or directory",
  "errorNum": 7001
}

update2:
Problem retested with 3.8.0 and it  behaves exactly the same

Thanks, @coronabytes for your detailed write-up on this issue. We'll repro this on our side and will review the output in detail. Once we have more to share regarding tips, fixes or anything else we will of course be in touch.

Hi @coronabytes,
To follow up with you on the troubleshooting of this issue we would like to ask you to perform the following steps and retry the action so we have all the logs/output we can use to properly investigate the issue:

On all coordinators/dbservers set the log level to 'debug'
Once the action has been retried, please add/send us all related logs (for all components (arangod/coordinator/dbserver/agent/hotbackup).
While running the action again, please generate a tcpdump and add the output/send the output to us.

Thanks in advance!

 After you delete the containers, the backup would be empty until you download the remote backup in to the local -
arangobackup download --identifier <backup-id> --remote-path <remote-path> --rclone-config-file remote.json

// list backups
{
    "error": false,
    "code": 200,
    "result": {
        "list": {
            "2021-09-16T02.29.58Z_test": {
                "id": "2021-09-16T02.29.58Z_test",
                "version": "3.8.1",
                "datetime": "2021-09-16T02:29:58Z",
                "keys": [],
                "sizeInBytes": 699138,
                "nrFiles": 70,
                "nrDBServers": 3,
                "available": true,
                "nrPiecesPresent": 3,
                "potentiallyInconsistent": false
            }
        }
    }
}

// upload

{
  "config": {
    "S3": {
      "type": "s3",
      "provider": "minio",
      "env_auth": "false",
      "access_key_id": "minio",
      "secret_access_key": "minio123",
      "endpoint": "http://minio:9000",
      "region": "us-east-1"
    }
  },
  "id": "2021-09-16T02.29.58Z_test",
  "remoteRepository": "S3://arango/"
}

// upload status

{
    "error": false,
    "code": 200,
    "result": {
        "Timestamp": "2021-09-16T02:34:13Z",
        "BackupId": "2021-09-16T02.29.58Z_test",
        "DBServers": {
            "PRMR-c7fc701b-e738-426f-a94b-008ac361e1f5": {
                "Progress": {
                    "Done": 9,
                    "Total": 9,
                    "Time": "2021-09-16T02:34:13Z"
                },
                "Status": "COMPLETED"
            },
            "PRMR-34ecc990-4e37-4d03-8cbd-1480c0262761": {
                "Progress": {
                    "Done": 8,
                    "Total": 8,
                    "Time": "2021-09-16T02:34:13Z"
                },
                "Status": "COMPLETED"
            },
            "PRMR-5adedfd8-7526-4606-a960-115f28bac18f": {
                "Progress": {
                    "Done": 9,
                    "Total": 9,
                    "Time": "2021-09-16T02:34:13Z"
                },
                "Status": "COMPLETED"
            }
        }
    }
}

// DELETE BACKUP !!!

// download

{
  "config": {
    "S3": {
      "type": "s3",
      "provider": "minio",
      "env_auth": "false",
      "access_key_id": "minio",
      "secret_access_key": "minio123",
      "endpoint": "http://minio:9000",
      "region": "us-east-1"
    }
  },
  "id": "2021-09-16T02.29.58Z_test",
  "remoteRepository": "S3://arango/"
}

// download status

{
    "error": false,
    "code": 200,
    "result": {
        "Timestamp": "2021-09-16T02:37:43Z",
        "BackupId": "2021-09-16T02.29.58Z_test",
        "DBServers": {
            "PRMR-c7fc701b-e738-426f-a94b-008ac361e1f5": {
                "Progress": {
                    "Done": 1,
                    "Total": 1,
                    "Time": "2021-09-16T02:37:43Z"
                },
                "Status": "COMPLETED"
            },
            "PRMR-34ecc990-4e37-4d03-8cbd-1480c0262761": {
                "Progress": {
                    "Done": 1,
                    "Total": 1,
                    "Time": "2021-09-16T02:37:43Z"
                },
                "Status": "COMPLETED"
            },
            "PRMR-5adedfd8-7526-4606-a960-115f28bac18f": {
                "Progress": {
                    "Done": 1,
                    "Total": 1,
                    "Time": "2021-09-16T02:37:43Z"
                },
                "Status": "COMPLETED"
            }
        }
    }
}

Please try to remove the slash at the end of the "remote repository": Just use S3://arango instead of S3://arango/. In our experiments the trailing slash leads to a double // slash in the paths and that seems to produce the "Odd name received" messages, which confuse the downloader. This might be an artifact between rclone and minio, but it might also happen with normal S3, I do not know at this stage. What happens then is that the downloader sees the wrong name (including lots of spaces and "Odd name received") and tries to download the wrong file. Since rclone does not report a non-zero exit code if a remote file does not exist, the downloader does not notice and in the end the backup isn't there.
We will fix this behaviour in a future version, the details are not yet decided, though. For now, removing the trailing slash did make it work for me.

Yup, that works...
Thank you.
Auto removing trailing slashes or throwing an error on upload/download seems like a godd idea.
Confirming that the download succeeded is quite misleading

Thanks @coronabytes for reporting the issue and confirming the solution worked for you. Closing this ticket as the original reported issue has been resolved and we will have a follow up ticket to handle the trailing slash automatically.


Allow upload relative to current directory

Upload relative to current directly works automatically since using "./" gives the address relative to home to the program.


ModuleNotFoundError: No module named 'velocyto.speedboosted'

Hi! I've successfully installed velocyto.py and velocyto.R (after 12+ hours of troubleshooting). Now, when I try and run velocyto --help, I get the following:
(base) $ velocyto --help
Traceback (most recent call last):
File "/opt/anaconda3/bin/velocyto", line 11, in
load_entry_point('velocyto', 'console_scripts', 'velocyto')()
File "/opt/anaconda3/lib/python3.7/site-packages/pkg_resources/init.py", line 490, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/opt/anaconda3/lib/python3.7/site-packages/pkg_resources/init.py", line 2855, in load_entry_point
return ep.load()
File "/opt/anaconda3/lib/python3.7/site-packages/pkg_resources/init.py", line 2446, in load
return self.resolve()
File "/opt/anaconda3/lib/python3.7/site-packages/pkg_resources/init.py", line 2452, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/Users/NMBaker/velocyto.py/velocyto/init.py", line 13, in
from .estimation import fit_slope, _fit1_slope, clusters_stats
File "/Users/NMBaker/velocyto.py/velocyto/estimation.py", line 7, in
from .speedboosted import _colDeltaCor, _colDeltaCorLog10, _colDeltaCorSqrt
ModuleNotFoundError: No module named 'velocyto.speedboosted'
I'm working in a conda environment. I git cloned the repo and did cd velocyto.py pip install -e . I also tried installing the gcc compiler (https://anaconda.org/anaconda/gcc), openMP (https://anaconda.org/conda-forge/openmp), and llvm (https://anaconda.org/anaconda/llvm) through conda (I had already installed using brew for the .R install). I also installed libgcc and cython using conda.
I upgraded to the latest python, anaconda, R, Xcode, and operating system (Catalina). I've reviewed all related posts to this issue, and saw that the last post said it might have something to do with the compatibility of the compiler with openMP. I looked into this issue here (http://openmp.llvm.org/) but not being fully familiar with if/how velocyto uses different compilers, I wasn't sure what to make of this or how to move forward. My compiler should be openMP enabled, according to http://openmp.llvm.org/.
I would really really appreciate any insight you might have to offer.

I am having the same issue

I am also having the same issue

I think I found the solution. I've have been doing some research and have found that Mac computer use Apple's compiler Clang by default. As a result, clang is used as the compiler even when you installed the compiler gcc. This is important because clang does not support openMP while gcc does and openMP is needed to install velocyto. Thus, in order to have pip use gcc instead of clang you can do the following.

Find out what your version and directory are for gcc.
gcc --version
which gcc
Run the following command:
CC=PATH/TO/gcc-VERSION pip install velocyto
I hope this helps. :)

@alexanderlewis99 How where you able to install a working version of gcc? gcc --version returns "Apple clang version 11.0.3 (clang-1<IP_ADDRESS>)", which likely is the reason why I get "unsupported option '-fopenmp'".

I think I found the solution. I've have been doing some research and have found that Mac computer use Apple's compiler Clang by default. As a result, clang is used as the compiler even when you installed the compiler gcc. This is important because clang does not support openMP while gcc does and openMP is needed to install velocyto. Thus, in order to have pip use gcc instead of clang you can do the following.

Find out what your version and directory are for gcc.
gcc --version
which gcc
Run the following command:
CC=PATH/TO/gcc-VERSION pip install velocyto
I hope this helps. :)

Done but the same


Converting circular structure of JSON

Hi,
I've tried to use it on my app, but at the start it show in console this error

installHook.js:59 Uncaught TypeError: Converting circular structure to JSON
at JSON.stringify ()
at getData (installHook.js:59)
at window.addEventListener (installHook.js:189)

Same here .. but this project looks very promising!

I'm also experiencing this bug, cannot get it to work. Excited to test this tool in my project.

Finally fixed this - https://github.com/React-Sight/React-Sight/pull/202