PUT list of dicts

Hey,
According to http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DataModel.html it should be possible to PUT a list of dicts to data store. Currently it does not seem to work for me:
var item = { one: 'test2',
               two: 'Kapow',
               usr: 'spolu',
               lng: ['node', 'c++'],
               mew: [
                 {'foo': 'blue', 'w': 1, 't': 2},
                 {'foo': 'red', 'w': 11, 't': 22}
               ]
  };

ddb.putItem('foobar', item, {}, function(err, res, cap) {});

i get the error:
ERR { [Error: PutItem [400]: One or more parameter values were invalid: An number set  may not be empty]

  statusCode: 400,

  requestId: 'MUFRMIPBFI6VVAR1R408KLGS0RVV4KQNSO5AEMVJF66Q9ASUAAJG',

  code: 'ValidationException',

  data:

   { __type: 'com.amazon.coral.validate#ValidationException',

     message: 'One or more parameter values were invalid: An number set  may not be empty' } }

This is duplicate question from google groups that I posted.

Hi @Katafalkas  how did you resolve this issue? Im currently facing the same thing


feat(es): es with random password service

关联研发信息
dev_branch: feat/bigdata_password_service/#1493
target_branch: random_password_merged


Add converter script for sqlite database files.

This script can convert back and forward between auth.sqlite and sauth.sqlite formats. It creates a new sqlite file (never overwriting an existing output file) and copies the auth entries over from the input format to the output format.

The python script isn't pretty(semicolons, always returns 0 even with errors, concatenation instead of f-strings ) although it is functional, I actually gave up after 4 hours of processing my 148MB sauth database on a SSD drive, so its usage is realistically going to be for db's with less than 50k of entries or some hair pulling will occur. To that end I'll create a sql file to process the db quicker than this script when I code the shift in databases, so offline time is reduced to a minimum. See https://github.com/shivajiva101/sauth/issues/16#issuecomment-1451761953. Meantime any way to speed the script up?

Yeah, We can make a very large INSERT statement, with multiple values, and that'll be a single DB commit, instead of one per ID. Or one insert per $some_large_number or something.

Also, python is like dead last on my list of skills when it comes to programming languages, so, treat it as the garbage pile that it is :)

Can you take a look at https://github.com/shivajiva101/sauth/tree/dev-0.5 and more specifically https://github.com/shivajiva101/sauth/blob/dev-0.5/tools/auth-convert.py
then let me know what you want to do about this pr in light of that?

I'll take the lack of response as validation to close the pr. It's under baked and has poor performance unfortunately.


Slack proxy option support

Description of Problem:
The slack channel does not currently support the slack client proxy option. This was discussed on the forum.
Overview of the Solution:
Add the client library proxy option to the slack channel here and expose in the credentials.yml.
Definition of Done:

[ ] Feature described the docs
[ ] Feature mentioned in the changlog

So is there any more todo on my side ?


Setup Ubuntu as default distro

Proposed changes
If we have more then one WSL distro installed, Ubuntu has do be the default distro in order to be reconnoitred by WSL2 preview prerequisites check

Deploy preview for docsdocker ready!
Built with commit dabffc2c82b6408333d9cbc4733075d04771659b
https://deploy-preview-9201--docsdocker.netlify.com

Jenkins error seems unrelated?

@helge000 - Thanks for your feedback. This issue was fixed in #9248.


Regular Expression Denial of Service (ReDoS) [High Severity]

Description
✗ Regular Expression Denial of Service (ReDoS) [High Severity][https://snyk.io/vuln/SNYK-JS-ANSIREGEX-1583908] in<EMAIL_ADDRESS>lint-staged ><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>and 5 other path(s)
This issue was fixed in versions: 6.0.1, 5.0.1

@iiroj can we get this ticket reopened or a new ticket created? listr2 has a vulnerability on the most recent version of lint-staged. I tried updating the dependency myself, but unfortunately, there are several test failures.

How does this vulnerability affect lint-staged? The only usage of log-update by Listr2 is  through the simple renderer here:
https://github.com/cenk1cenk2/listr2/blob/bd5a4a08c5c441d41ad1bb1f2344226b980879fd/src/renderer/simple.renderer.ts#L72
We are only using the update, verbose or silent renderers:
https://github.com/okonet/lint-staged/blob/e035b80e39da355da57c02db6565b55271ab1afa/lib/getRenderer.js#L8

I'm not familiar with the internals of this library, but every project that has lint-staged as a dependency now has an unfixable npm audit issue.

@att14 yeah, it's too bad npm audit works this way. There's not really a way to mark a vulnerability as invalid or unaffected. It's bad especially in cases where the vulnerability is multiple transitive dependencies deep, and not even used.

For this to be fixed, I have to move listr2 to ESM, which will render cjs applications unusable with this library. My plan is to drop this log-update, but since the last couple of months, I have not found any time to do so. There is multiple open branches that are not finalized for this, working on getting the keindev/stdout-update working but there is many behavioural differences, that causes the tests to be overhauled.


"/" in layer id

Warm greetings.
Today, I found an issue.
If there is a "/" in any layer id, we see "the permission denied" and the "convert" command does not work. (See attached image.)

I think this is because the layer "id" will be the name of each layer's yml file.
But, if we look at the style file from ArcGIS series, we may see a lot of "/" in layers' id.
Do you think is there any way to overcome this issue?
Otherwise, the charites will not be used to import a style file from ESRI sometimes.
Thank you for your kind attention and kind advice!
(FYI) An default style of Esri Living Atlas
https://basemaps.arcgis.com/arcgis/rest/services/OpenStreetMap_v2/VectorTileServer/resources/styles/root.json

Tentatively, I replaced "/" with "(slash)" using the text editor. Then, we can import the style.json into yaml files.

This is how I tentatively avoid this issue.
https://qiita.com/T-ubu/items/e6794b81e45dea34548c
Then, I close this issue.

@naogify I think this issue should be solved by source code. What do you think?

@JinIgarashi @ubukawa
Yes, I agree with your opinion. I think we can solve the problem by source code.


Incorrect Module appended to reference list endpoint

When a Reference List, such as SheshaEnterprise.SalesOrderStatuses, is created and exists in a different module, such as Shesha Enterprise, but is used in the Sales Order Module, the getByName endpoint incorrectly appends the SalesOrderManagement module to the payload as if it exists within that module.

While the reference that exists on the system is the below example

Hi @hlayisanimazuze. If the Module is not specified for a reference list property we search reference list in the entity owning module. I've made changes in the pd-enterprise and it should work after update of your project. Please create a separate card for code clean-up and documenting of the reference lists functionality.


fix: handle unknown mime

If mime type not in default mime type object, let browser determine how to handle response.
Fix navigation to other file types than HTML (or extensionless (base) route), when using view transitions

Looks good. At some point we want a configuration option for pretty URL's so that blog/foo.md translates to blog/foo

Yes. I have an issue for that: #282


Feature extraction tutorial error

python3 data/create_video_db.py --list_file sample_videos.csv --output_file my_lmdb_data --use_list 1 --use_video_id 1 --use_start_frame 1
yields
TypeError
'/home/dario/temp/datasets/ADD/Anomaly-Videos/Abuse/Abuse001_x264.mp4' has type str, but expected one of: bytes

at  https://github.com/facebookresearch/VMZ/blob/master/c2/data/create_video_db.py#L86
                if not use_list:
                    with open(file_name, mode='rb') as file:
                        video_data = file.read()
                else:
                    video_data = file_name

                tensor_protos = caffe2_pb2.TensorProtos()
                video_tensor = tensor_protos.protos.add()
                video_tensor.data_type = 4  # string data
>>              video_tensor.string_data.append(video_data)

video_data is indeed a str, since video_data = file_name given use_list
I'm uncertain what to do now. Do you need more information? Can you reproduce this?

this is an error by python3 vs python 2 incompatible in term of string data type.

Oh.. I didn't realize this repo used python2..
Is there an updated version of this repo for python3 @dutran ?

We plan to have an update on that. For not a simple fix should be video_data.encode('utf-8')


fix: change ibm provider version requirement to v1.62

Description
Changes the IBM provider required version to >= 1.62.0 to support submodule requirements used in this module.
Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

:tada: This PR is included in version 1.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[chore] updated swift 5.7.0

Summary of changes
Changes introduced in this pull request:
updated swift 5.7.0
Reference issue to close (if applicable)

Other information and links

@ktoso cc


Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I am not looking for support or already pursued the available support channels without success.

Version
1.0.3
Installation Type
Official Docker Compose
Service Name
DongTai-OpenAPI
Describe the details of the bug and the steps to reproduce it

修改了请求内容重新发包后，调用链展示不刷新！
Additional Information
No response
Logs
No response

Thanks for the feedback, the test recurrence has been arranged.

fixe


Implemented additional health checks

Added health checks for zookeeper, kafka, rest proxy, and the mongodb and hdfs connectors.

These will be very useful. I have a question. Is there any way to send a notification (like an email) when a container is not healthy? Because it will be helpful to know immediately when something fails.

@blootsvoets can we also add heathchecks for MP app, postgres and kafka-manager.

I'll check the mongodb connector again. I'll take a look at postgres, MP and kafka as well. There are two ways to respond to unhealthy containers:

via docker events, in that case a daemon needs to be continuously listening
via docker inspect, in that case you can poll the status whenever you like.

I'm implementing a script for the second option to restart unhealthy services.

This sounds great. I will also look into Puppet for our stack and integrating it. But this should be more than enough for now. Thanks

@yatharthranjan I've added the check-health.sh script and added health checks for the remaining services.

@blootsvoets Okay great. I will check in a moment. And do we need to start this script in the background and leave it running for monitoring?

It should be run as a cron job

closes #69


Add support for AWS Kinesis Firehose

Type: AWS::KinesisFirehose::DeliveryStream

Hi @matthewa24,
This should now be supported that 0.13.0 and the AWS Cloudformation schema are supported.
Please let us know if this is not the case.
Thanks.


[YouTube] Half the universe was missing... until now

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2020.07.28
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://youtu.be/Kp_kqamkYpw?t=193']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2020.07.28
[debug] Python version 3.8.5 (CPython) - Linux-5.7.11-1-MANJARO-x86_64-with-glibc2.2.5
[debug] exe versions: ffmpeg 4.3.1, ffprobe 4.3.1, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] Kp_kqamkYpw: Downloading webpage
ERROR: Unable to download webpage: <urlopen error [Errno -2] Name or service not known> (caused by URLError(gaierror(-2, 'Name or service not known')))
  File "/usr/lib/python3.8/site-packages/youtube_dl/extractor/common.py", line 627, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 2238, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python3.8/urllib/request.py", line 525, in open
    response = self._open(req, data)
  File "/usr/lib/python3.8/urllib/request.py", line 542, in _open
    result = self._call_chain(self.handle_open, protocol, protocol +
  File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.8/site-packages/youtube_dl/utils.py", line 2734, in https_open
    return self.do_open(functools.partial(
  File "/usr/lib/python3.8/urllib/request.py", line 1353, in do_open
    raise URLError(err)

Description

It happens a lot recently.

It seems to be my DNS setting problem, after I re-enable the internet, it works again.


Minimal HW manifest support need for FMUv5

Platforms that provide HW versioning tend to have more FLASH and can have a PX4IO as an option.
(E.G.) FMUv5. This change provides run time  decision to control the safety switch on
platforms that have BOARD_HAS_VERSIONING and support a manifest. (FMUv5)
On platforms with no versioning and have BOARD_HAS_STATIC_MANIFEST defined as a 1
The decision is compile time only. When a PX4IO is present the fmu control of the safety is
not built.

tested with pixhawk 4 (V5).
safety switch working well.
https://review.px4.io/plot_app?log=533ab0d1-2a87-48e9-bb79-d09d5b33cdd7

test on pixhawk mini v3 work well.
https://review.px4.io/plot_app?log=af81d7ab-4917-4168-8981-f2064890d43d
pixhawk pro v4 work well
https://review.px4.io/plot_app?log=eb3abd98-b9e6-4320-b9f7-ef44932f406a


fix: simplify cache handling

Checklist

[ ] I have read the coding guide.
[ ] My change requires a documentation update, and I have done it.
[ ] I have added tests to cover my changes.
[ ] I have filled out the description and linked the related issues.

Description
Simplifying cache component. Having a simpler timestamp index to iterate makes things much simpler and less error prone. The linked list is very error prone and leaves the cache useless if we hit any issues.

it's not part of the changes but is db.lock.Lock(cacheAccessLockKey) is needed still ?

it's not part of the changes but is db.lock.Lock(cacheAccessLockKey) needed still ?

So right now it is needed, but it can be removed if we move the cache size handling into storer pkg. Right now as it's in the internal cache, we can remove the lock. It can be done as a follow up change.


No drop shadow on thumbnails

No drop shadow when following installation instructions, compare with PNG.
See https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/cc144118(v=vs.85)#thumbnail-adornments

It's a personal preference, but yes, I can add that.

Fixed with d1625c8.
Thanks!


New Feature : polyline/polygone

I've just developped a new feature : polylines and polygones. the function is available under the line button. Draw edges by click or mouse down. To finish, click next to the last vertex.
Undo will remove the last segment and will allow to resume from there.
ppInkTst.zip
Waiting for your feed before introducing this commit into main branch.

It can only be a quadrilateral, including the lines inside.
Cannot draw lines inside triangles.
https://user-images.githubusercontent.com/24859526/102861844-323d4e00-446b-11eb-98a7-5f9408f17130.mp4

you are only on line tool : to activate polyline and then polygone(filled), click many times on line button to engage

Features released in 1.4 alpha1

Features released in 1.4 alpha1


README example for transferFrom

I've been doing NFT bulk transfers using https://marketplace.kalao.io/ because the original NFT contract does not have such functionality (only standard transferFrom).
I wanted to script these transfers and also avoid kalao contract and I ended up bumping into this contract.
I got it working with web3.py (web3.py directly has no multicall method support, like the ape example in the repo) for read operations/functions which seems to be the most common use for multicall.
Now that I wanted to try to call transferFrom, I'm a little worried about all the warnings about people spending our own tokens. Looking at the contract (in my ignorant eyes), as there is no specific aggregate for transactions, it does seem that there is no check that msg.sender is the actual from address.
Is that why, if approved, it would mean anyone could just use our address in their own transferFrom calls?
What is the correct way to do these batch transfers then?
I saw batch contract writes, but it seems oriented for contracts calling multicall rather than a private-key entity calling it.

I'm not familiar with kalao so I don't fully understand what you're trying to do, but here's some information that might help:

I'm assuming you're using an EOA, because if you had a contract wallet you can just batch call transferFrom. But it sounds like Kalao might hold your NFTs in some type of proxy contract for you, so you can do batch operations.
Batch transfers of NFTs from an EOA are not possible: Each NFT is a different token contract, and from an EOA you'd have to call transferFrom on each NFT. You can of course script this, but you'll still send 1 tx per NFT transfer
To clarify the risk of warnings:

No one can transferFrom tokens on your behalf unless you approve that address to do so
Approving an address lets them call transferFrom to move tokens for you.
 This is why you should not approve Multicall3 to spend your tokens from an EOA

If any of that helps or answers your question, let me know which parts in particular so I can update the README

I think those are the things I either already knew or understood from the risk of warnings section.
Though I don't understand why you say each NFT is a different token contract (as I meant to bulk transfer tokens of the same contract) I do know I cannot bulk transfer them unless the contract explicitly supports them.
But I thought I could use leverage multicall contract for that, wasn't it designed for people to save also on fees rather than just save on infura API calls for read operations?
Or was it originally thought for contracts to use multicall themselves?
In short, my doubt was:

is there any safe way to use multicall to transfer tokens without approving access to all tokens (from an EOA)?
if not, would it be easy to add a different method for it? such as the one I mention and would have msg.sender == from check on top? that would make it enough to approveAll on the contract right? I suppose it'd have to be on a different contract as aggregate in this one would still skip it :)

Maybe this is clear for everyone else getting to this repository, but maybe adding this to the batch write warning section would make sense. Instead of saying never approve multicall to use your tokens, just say never do writes using multicall from an EOA. The first statement makes it sound like there's a possibility to use batch writes without approving... (imo)

Though I don't understand why you say each NFT is a different token contract (as I meant to bulk transfer tokens of the same contract) I do know I cannot bulk transfer them unless the contract explicitly supports them.

Ah ok, I didn't realize you were doing batch transfers from the same contract, though, the second bullet in my above comment still is true in that case (unless the token contract explicitly supports it like you said)

But I thought I could use leverage multicall contract for that, wasn't it designed for people to save also on fees rather than just save on infura API calls for read operations?
Or was it originally thought for contracts to use multicall themselves?

An EOA cannot leverage this multicall contract to batch transfer NFTs, unless you gave approval to the multicall contract to transfer your NFTs, then use multicall to batch various transferFrom calls. But you almost certainly should not do that from an EOA, because someone can spot your approval then frontrun you to steal the tokens. A contract wallet could use the multicall contract to do this atomically in a single transaction so there is no risk.

is there any safe way to use multicall to transfer tokens without approving access to all tokens (from an EOA)?

There is not, this is a limitation of EOAs. Batch calls from an EOA for any contract are only supported if that contract bakes in support for batch actions.

if not, would it be easy to add a different method for it? such as the one I mention and would have msg.sender == from check on top? that would make it enough to approveAll on the contract right? I suppose it'd have to be on a different contract as aggregate in this one would still skip it :)

Yea, you should be able write an application-specific version of this multicall contract with a single aggregate method that requires msg.sender == from (where from is the from arg in transferFrom) and that would protect you.

just say never do writes using multicall from an EOA.

This is not true though, not all write-operations rely on msg.sender, and the ones that don't are safe. For example I can use multicall with an EOA to batch-claim airdrops that take a proof and send tokens to the proved address, or batch-poke contracts for some maintenance action

Ah true, claims are a good example as they do apply to the contract I'm using as well. Though this one doesn't take any wallet as parameter and uses msg.sender for the claim, so it cannot be used via multicall.
Anyway, good point so I don't have anything to add to the README unless you want to add that last comment that did make it clear to me why it could still be used for an EOA 🙇
Closing it then and thanks once again for the clarification. I'll try to debug that marketplace contract and just use the same method they use there (as I already approved for the website, I hope it is indeed safe haha)

@mds1 I still have to digest better the gas golfing techniques you describe and link, but if you have some free minutes, feel free to recommend any low hanging fruit you can spot in BulkTransfer (as they're somewhat related) 😄
First contract I'm trying to write, went through apeworx and then foundry to pick a framework and the whole testing setup 🤯


Does tunneling support seeking to the end of content?

We are using ExoPlayer 2.18.7 and Android API level 30.
Our application sometimes requires calling ExoPlayer.seekTo  with the positionMs equal to the duration of the content.
When we use non-tunneling mode this works as we expect it to, i.e. player gets into STATE_ENDED and the playback stops.
However, when the same is done in the tunneling mode the playback gets stuck forever.
Analysis of what is causing this shows that under such conditions ExoPlayer starts feeding video decoder samples starting from the the last keyframe, but it does not feed any samples  to the audio decoder. So the video decoder accepts several samples and then dequeueInputBuffer starts failing. It is failing because this is tunneling mode ate there are no audio samples to associate the video sample with.
The question is is such seeking to the content duration a valid operation? If "yes" then how should it work with tunneling mode?
Or should ExoPlayer the call to seekTo fail?
A similar question is: let's assume we have a content which does not have any audio for the few last seconds (but does have video) and let's say the app is seeking to such a position with video but without audio. How should such a seek work in the tunneling mode (given that video cannot be synchronized without audio)?

Tunneling is known to be a bit unreliable in some cases because it forwards a lot of the implementation details to OEM specific code Android cannot verify or control. This sounds like one of these cases. In theory, the end of the audio track should be sufficient to signal that all remaining video samples should be output. If you build locally, could you try enabling this workaround to see if it makes a difference? We had previous issues with end-of-stream signaling on some devices.

@tonihei
My understanding of CodecNeedsEosPropagation is that some decoders do not propagate BUFFER_FLAG_END_OF_STREAM (EOS) from the input buffer to the output buffer and need ExoPlayer's help in doing so.
However, I am talking about a situation when the playback never reaches the state in which ExoPlayer submits a buffer with EOS neither to video nor to audio decoder.
When in tunneling mode seekTo(duration) is called ExoPlayer submits no input buffers (including no EOS buffer) to the audio decoder but does submit video buffers starting from the last keyframe. Video decoder gives ExoPlayer all the available input buffers, ExoPlayer feels them and submits back to the decoder and at this point the video decoder gets stuck and everything stops because the video decoder does not have any more input buffers and the ones which are submitted already are not being processed because in tunneling mode the buffers are waiting for the timing coming from the audio side.
When I repeat the same but with seekTo(duration - 20 msec) ExoPlayer submits the same video buffers to the video decoder as in the previous case but it also submits the last audio buffer and an EOS buffer to the audio decoder and in this case video decoder is not getting stuck and continues to process the video buffers up to EOS as expected.
Maybe the problem is that ExoPlayer needs to send EOS to the audio decoder even in the case when there is no more audio in the stream, i.e. when seekTo(duration) is called.

Interesting, the CodecNeedsEosPropagation was just a quick attempt to see if your issue can be solved by a similar approach. Thanks for debugging it further to see what's actually happening.

When in tunneling mode seekTo(duration) is called ExoPlayer submits no input buffers (including no EOS buffer) to the audio decoder

I think the audio decoder is actually irrelevant for this setup and only what happens in DefaultAudioSink (or rather the platform AudioTrack) really matters for the A/V sync behavior. If you have a reproducible setup, could you check whether DefaultAudioSink.playToEndOfStream is called and whether isAudioTrackInitialized returns true in there?
If yes, it will be a shortcoming of how tunneling is designed and there is probably not much we can do realistically. If no, we may be able to workaround it by ensuring the AudioTrack is initialized and stopped even if there is no actual audio data to play.

@tonihei
Yes, I checked this.
After the seek DefaultAudioSink.playToEndOfStream is called in a loop and isAudioTrackInitialized always returns false.

Thanks for the confirmation. I think the best thing to try out is creating the audio track (and then stopping it immediately), as this may signal the end of playback to the video codec as well.
Could you add
if (tunneling && !isAudioTrackInitialized()) {
  try {
    initializeAudioTrack();
  } catch (InitializationException e) {
    throw new WriteException(/* errorCode= */ 0, e.format, e.isRecoverable);
  }
}

to the beginning of playToEndOfStream()?  Not fully sure it helps, but at least it's worth a try.
Aside: Did you observe this problem on specific devices only or multiple devices?

Hmm, okay, thanks for trying this out in any case! I believe this may mean it's not possible to handle this case nicely in a simple way (=with showing the last frame) when tunneling is enabled.
I can imagine some more involved fixes that could help, for example:

Sending the last few milliseconds of audio to play as well (although this may be not the ideal user experience either)
Artificially playing silence to for a short duration.
Not attempting to play the last frame at all in this case and forcing the player to move to the ENDED state immediately.

In your app, do you control the UI implementation? If so, do you think it's feasible to 'solve' this by never truly seeking to the end of the media but slightly before? This is similar to my first suggested fix in the list above, but can be implemented on your side.
I'll leave the issue open to acknowledge the problem, but we are not very likely to get around looking into more complicated fixes very soon I'm afraid.


fix: added missing dependencies

PR Type

[  x ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] CI-related changes
[ ] Documentation content changes
[ ] Application / infrastructure changes
What Is the Current Behavior?

Issue Number: Closes #
What Is the New Behavior?
Does this PR Introduce a Breaking Change?

[ ] Yes
[ x ] No
Other Information

These depended tgz files do not have to be added. They will already be available in the release tgz as well (after you release). For local development you always need to execute helm dependency update . as you also wrote in your Chart.yml.


Resource parameter data types have inconsistent casing

Not a functional issue but a weird visual one that should be investigated.

Resolved in mentioned PR


[Feature]: Crater for the shuttle runtime

Describe the feature
From the rust-crater README:

Crater is a tool to run experiments across parts of the Rust ecosystem. Its primary purpose is to detect regressions in the Rust compiler, and it does this by building a large number of crates, running their test suites and comparing the results between two versions of the Rust compiler.

This seems like the sort of tool which would be useful for the shuttle runtime for the same reasons as crater is useful for the rustc. Namely:

Many, many free and real-world test cases. Even the best devs can't write as much code as exist in the thousands of shuttle projects.
Provide a guarantee to shuttle projects that minor-version releases won't break your build. I imagine this would be a hard requirement for people wanting to use shuttle for production.

While running every shuttle project might take too long and slow down development, compiling and deploying the top X% of shuttle projects would likely catch bugs and regressions before they make it to a minor version release. The exact percentage can be adjusted based on the delay this causes to the development cycle.
If there's interest in this, I'd be keen to open a PR/create a new repo to explore the idea.
Suggestion or Example of how the feature would be used
This should be integrated with CI, and it might be possible to fork the existing infrastructure from rust-lang/crater so that shuttle can benefit from the prior work done there.
Duplicate declaration

[X] I have searched the issues and this feature has not been requested before.

Hey, wondering if there's any comment on this?

Hey, thanks for the suggestion! I think the end-result sounds great, but to me this seems like a very large undertaking, and I'm not sure we'd want to commit to it at this point. That said I can't immediately think of a reason that this wouldn't be possible, we do have metrics for project proxy hits, and it should be possible to extract the build files for these projects. In the near future (:crossed_fingers:) however, we will quite radically change how projects are built and deployed. There will no longer be one deployer container per project that builds, deploys and stores logs for projects. There will be an external build service that builds an image and sends them to another service to run and manage them.
So I think the idea is worth considering, but I think we should wait either way until this refactor is complete. In the meantime, we do have a hole in our test suite when it comes to end-to-end testing. We have end-to-end tests in the e2e directory that are not ran regularly and they are often out-of-date. We also have some QA scripts for our CI, which don't work (you can see the runs of them in the production branch). We'll likely need to rethink/refactor both of these, so if you have any thoughts on that, we'd appreciate it (if you're interested, I know it's a bit of a segue from your issue :smile:)!

Yup definitely would be a large undertaking, totally understand that you're all focused on building out the core product at the moment. Definitely not worth building out infrastructure on top of something that's planned to change in the near future.
With regards to the e2e testing, I'm interested and will take a look, but the other issue seems like a better introduction to the shuttle codebase/architecture right now so I think I'll focus on that one for the moment.
I'll close the issue since it doesn't look like there'll be shuttle-crater in the near future. I've seen other projects use a GH label like revisit-after-2023-11 to mark issues which aren't going to be looked at until after some dependency is met, in case you want the issue to be "partially" closed.


dist_train keep waiting when filter_empty_gt=False

Environment:

pytorch 1.3.1
cuda 10.0
cudnn 7
mmdetection 1.1.0

My config file:  cascade_rcnn_dconv_c3-c5_r50_fpn_1x.py,  with only the ann path modified.

When i set filter_empty_gt=False (20% of my images are background only.),  there are not any error messages, but the trainning process are always waiting..., so I have to keyboardinterupt it:

When i set filter_empty_gt=True, every thing is ok.

Hi @PanJianning ,
Just to confirm the problem, you are training cascade_rcnn_dconv_c3-c5_r50_fpn_1x.py on your own dataset, but meet bug when setting filter_empty_gt=False? Do you implement the logic to deal with empty gt in your customed dataset? The bug might result from your implementation.

Hi @PanJianning ,
Just to confirm the problem, you are training cascade_rcnn_dconv_c3-c5_r50_fpn_1x.py on your own dataset, but meet bug when setting filter_empty_gt=False? Do you implement the logic to deal with empty gt in your customed dataset? The bug might result from your implementation.
,
thanks for your reply.  I use CocoDataset and change nothing except the annotation path.

@ZwwWayne I print gt_labels in forward_train method of cascade_rcnn detector, and notice that the trainning hangs when a batch contains only background images.

@ZwwWayne  @hellock  When a batch contains only background images, the return losses of cascade rcnn misses keys s_i.bbox_loss,  i=0,1,..,num_stages-1 , this is a expected behavior, since we can't do bbox regression when there are no gt_bboxes.  But It causes my distributed trainning process hanging.

After I add this row in cascade_rcnn.py, the bug disapeared. Though not a good solution, but it works.

I also tried filter_empty_gt=False but it seems not work. Hope you can get a better score in the leaderboard. @PanJianning

Maybe it has something to do with this issue and this line

Maybe it has something to do with this issue and this line

I can add negative sample to train, and I'm sure the training dataset becomes more, but the mAP seems just soso. @PanJianning

Maybe it has something to do with this issue and this line

I can add negative sample to train, and I'm sure the training dataset becomes more, but the mAP seems just soso. @PanJianning

I only meet the issue when I use distributed trainning.  It gives me a better score in first round so I always set it to false in the second round.

When I set filter_empty_gt=False in config files, I ran into same error
I think this is caused by the all_reduce operations in parse_losses function in main.py:
    for loss_name, loss_value in log_vars.items():
        # reduce loss when distributed training
        if dist.is_available() and dist.is_initialized():
            # loss_value: tensor(0.6956, device='cuda:0', grad_fn= < AddBackward0 >)
            # loss_value.data: tensor(0.6956, device='cuda:0')
            # loss_value.data.item: 0.6956
            loss_value = loss_value.data.clone()
            dist.all_reduce(loss_value.div_(dist.get_world_size()))
        log_vars[loss_name] = loss_value.item()

When some batch has no gt, the 'loss_bbox' and 'loss_mask' in

@hellock @ yhcao6
When I set filter_empty_gt=False in config files,  the distributed training came across the following error:
transforms.py: "need at least one array to stack"
This is caused by Resize._resize_masks() and RandomFlip.call when there are no gts in annotation,
I modified some code in Resize._resize_masks() as following:
# original code:
# results[key] = np.stack(masks)
if masks:
results[key] = np.stack(masks)
else:
if self.keep_ratio:
mask_size = (int(results['ori_shape'][1] * results['scale_factor'] + 0.5),
int(results['ori_shape'][0] * results['scale_factor'] + 0.5))
results[key] = np.empty((0,) + mask_size, dtype=np.uint8)
, and modified some code in  RandomFlip.call  as following:
# original code:
# results[key] = np.stack([
#     mmcv.imflip(mask, direction=results['flip_direction'])
#     for mask in results[key]
# ])
masks = [
mmcv.imflip(mask, direction=results['flip_direction'])
for mask in results[key]
]
if len(masks) != 0:
results[key] = np.stack(masks)
else:
mask_size = (results['img_shape'][1], results['img_shape'][0])
results[key] = np.empty((0,) + mask_size, dtype=np.uint8)
The modification solved the "need at least one array to stack" error, but the training still crash with some message: " RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one."
So I set find_unused_parameters=True，NCCL_LL_THRESHOLD=0 as mentioned in some discussions,  the training seems good, but after several iterations, the training stuck again,  and some GPU occupation is 100%. Some deadlock happed. I think this is caused by the all_reduce operations in parse_losses function in main.py:
for loss_name, loss_value in log_vars.items():
    # reduce loss when distributed training
    if dist.is_available() and dist.is_initialized():
        # loss_value: tensor(0.6956, device='cuda:0', grad_fn= < AddBackward0 >)
        # loss_value.data: tensor(0.6956, device='cuda:0')
        # loss_value.data.item: 0.6956
        loss_value = loss_value.data.clone()
        dist.all_reduce(loss_value.div_(dist.get_world_size()))
    log_vars[loss_name] = loss_value.item()

When some batch has no gt, the 'loss_bbox' and 'loss_mask' in log_vars on some GPU may not exist, but other GPUs with gts may still perform all_reduce with 'loss_bbox' and 'loss_mask' across all GPUs, this operation will make the GPUs with gts wail permanently...
I think setting "find_unused_parameters=True，NCCL_LL_THRESHOLD=0" just hide the problem instead of solving the problem in some discussions.
I fixed it with the following modification:
if len(log_vars) == 7:
for loss_name, loss_value in log_vars.items():
# reduce loss when distributed training
if dist.is_available() and dist.is_initialized():
# loss_value: tensor(0.6956, device='cuda:0', grad_fn= < AddBackward0 >)
# loss_value.data: tensor(0.6956, device='cuda:0')
# loss_value.data.item: 0.6956
loss_value = loss_value.data.clone()
dist.all_reduce(loss_value.div_(dist.get_world_size()))
log_vars[loss_name] = loss_value.item()
elif len(log_vars) == 5:
# 默认7个属性
loss_names = list(log_vars.keys())
loss_values = list(log_vars.values())
# 先处理共有的5个属性
for i in range(7):
if i <= 3:
loss_name = loss_names[i]
loss_value = loss_values[i]
elif i == 4:
loss_name = 'loss_bbox'
loss_value = torch.tensor(0.)
if dist.is_available() and dist.is_initialized():
loss_value = loss_value.cuda()
elif i == 5:
loss_name = 'loss_mask'
loss_value = torch.tensor(0.)
if dist.is_available() and dist.is_initialized():
loss_value = loss_value.cuda()
else:
loss_name = loss_names[-1]
loss_value = loss_values[-1]
# print(f'lossname:{loss_name}, lossvalue:{loss_value}')
if dist.is_available() and dist.is_initialized():
loss_value = loss_value.data.clone()
dist.all_reduce(loss_value.div_(dist.get_world_size()))
log_vars[loss_name] = loss_value.item()
else:
raise Exception('Not possible...')
The above modification is just temporary expedient, because the code in train.py is shared by all kinds of detectors. I think this should be fixed by modification the detectors class to make the classes return zeros when there are no gts in batch, also all_reduce performed on different groups should work too(I think...)

@hellock
When I set filter_empty_gt=False in config files,  the distributed training came across the following error:
transforms.py: "need at least one array to stack"
This is caused by Resize._resize_masks() and RandomFlip.call when there are no gts in annotation,
I modified some code in Resize._resize_masks() as following:
            # original code:
            # results[key] = np.stack(masks)
            if masks:
                results[key] = np.stack(masks)
            else:
                if self.keep_ratio:
                    mask_size = (int(results['ori_shape'][1] * results['scale_factor'] + 0.5),
                                 int(results['ori_shape'][0] * results['scale_factor'] + 0.5))
                results[key] = np.empty((0,) + mask_size, dtype=np.uint8)

, and modified some code in  RandomFlip.call  as following:
	# original code:
                # results[key] = np.stack([
                #     mmcv.imflip(mask, direction=results['flip_direction'])
                #     for mask in results[key]
                # ])
                masks = [
                    mmcv.imflip(mask, direction=results['flip_direction'])
                    for mask in results[key]
                ]
                if len(masks) != 0:
                    results[key] = np.stack(masks)
                else:
                    mask_size = (results['img_shape'][1], results['img_shape'][0])
                    results[key] = np.empty((0,) + mask_size, dtype=np.uint8)

The modification solved the "need at least one array to stack" error, but the training still crash with some message: " RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one."
So I set find_unused_parameters=True，NCCL_LL_THRESHOLD=0 as mentioned in some discussions,  the training seems good, but after several iterations, the training stuck again,  and some GPU occupation is 100%. Some deadlock happed. I think this is caused by the all_reduce operations in parse_losses function in main.py:
for loss_name, loss_value in log_vars.items():
    # reduce loss when distributed training
    if dist.is_available() and dist.is_initialized():
        # loss_value: tensor(0.6956, device='cuda:0', grad_fn= < AddBackward0 >)
        # loss_value.data: tensor(0.6956, device='cuda:0')
        # loss_value.data.item: 0.6956
        loss_value = loss_value.data.clone()
        dist.all_reduce(loss_value.div_(dist.get_world_size()))
    log_vars[loss_name] = loss_value.item()

When some batch has no gt, the 'loss_bbox' and 'loss_mask' in log_vars on some GPU may not exist, but other GPUs with gts may still perform all_reduce with 'loss_bbox' and 'loss_mask' across all GPUs, this operation will make the GPUs with gts wail permanently...
I think setting "find_unused_parameters=True，NCCL_LL_THRESHOLD=0" just hide the problem instead of solving the problem in some discussions.
I fixed it with the following modification:
    if len(log_vars) == 7:
        for loss_name, loss_value in log_vars.items():
            # reduce loss when distributed training
            if dist.is_available() and dist.is_initialized():
                # loss_value: tensor(0.6956, device='cuda:0', grad_fn= < AddBackward0 >)
                # loss_value.data: tensor(0.6956, device='cuda:0')
                # loss_value.data.item: 0.6956
                loss_value = loss_value.data.clone()
                dist.all_reduce(loss_value.div_(dist.get_world_size()))
            log_vars[loss_name] = loss_value.item()
    elif len(log_vars) == 5:
        # 默认7个属性
        loss_names = list(log_vars.keys())
        loss_values = list(log_vars.values())
        # 先处理共有的5个属性
        for i in range(7):
            if i <= 3:
                loss_name = loss_names[i]
                loss_value = loss_values[i]
            elif i == 4:
                loss_name = 'loss_bbox'
                loss_value = torch.tensor(0.)
                if dist.is_available() and dist.is_initialized():
                    loss_value = loss_value.cuda()
            elif i == 5:
                loss_name = 'loss_mask'
                loss_value = torch.tensor(0.)
                if dist.is_available() and dist.is_initialized():
                    loss_value = loss_value.cuda()
            else:
                loss_name = loss_names[-1]
                loss_value = loss_values[-1]
            # print(f'lossname:{loss_name}, lossvalue:{loss_value}')
            if dist.is_available() and dist.is_initialized():
                loss_value = loss_value.data.clone()
                dist.all_reduce(loss_value.div_(dist.get_world_size()))
            log_vars[loss_name] = loss_value.item()
    else:
        raise Exception('Not possible...')

The above modification is just temporary expedient, because the code in train.py is shared by all kinds of detectors. I think this should be fixed by modification the detectors class to make the classes return zeros when there are no gts in batch, also all_reduce performed on different groups should work too(I think...)

Update
My NCCL version is 2.5.7. After setting the following env variable, the dead lock disapeared, but I got negative loss...
export NCCL_LL_THRESHOLD=0

@ZwwWayne @hellock When a batch contains only background images, the return losses of cascade rcnn misses keys s_i.bbox_loss, i=0,1,..,num_stages-1 , this is a expected behavior, since we can't do bbox regression when there are no gt_bboxes. But It causes my distributed trainning process hanging.

After I add this row in cascade_rcnn.py, the dead lock disapeared. But will it mess up the backpropagation?

so will it mess up the backpropagation?

Update
My NCCL version is 2.5.7. After setting the following env variable, the dead lock disapeared, but I got negative loss...
export NCCL_LL_THRESHOLD=0

@ZwwWayne @hellock When a batch contains only background images, the return losses of cascade rcnn misses keys s_i.bbox_loss, i=0,1,..,num_stages-1 , this is a expected behavior, since we can't do bbox regression when there are no gt_bboxes. But It causes my distributed trainning process hanging.

After I add this row in cascade_rcnn.py, the dead lock disapeared. But will it mess up the backpropagation?

so will it mess up the backpropagation?

I got worse score with this modification.

This should be fixed by https://github.com/open-mmlab/mmdetection/pull/2280.
Feel free to reopen it.


Change multiday fullDay Event behaviour

Hey!
This PR should change the behaviour of starting fullDay events that last several days. The goal was to change the behavior of the "Starting today, ends T" (T=Tomorrow) event, so it should show how many days it will occur from the first day on
Before situation:
a fullDay event that started 'today' and ends several days later showed Today on the first day. The rest of the days it showed X days left.

Y => Yesterday
T => Tomorrow
Target situation with this commit:
a fullDay event that started 'today' shows 'X days left' from the first day on and 'Today' on the last day.

Thanks for the PR. Makes sense for me, but the tests are failing for it :-(

Okay.. they were green before and as far as I see, nothing changed in the Code. Would you be fine that I edit the tests to only assert that the text "ends in" is contained, no matter how many days are following? That's the main goal of the PR.


A "work" section that has titled images of the developer's applications

The image of my first application should be larger than the others


Unhelpful Error Exporting From Commandline Without Build Templates

Godot version:
3.1.2 stable
OS/device including version:
Ubuntu Linux 18.04
Issue description:
When exporting from the command line without proper build templates downloaded a generic os file error is displayed without any indication that it is related to the build templates.
Steps to reproduce:
Download a version of godot onto a machine that does not have the build templates for that version, or delete the build templates for that version.
Then attempt to run a command line export such as:
./Godot_v3.1.2-stable_x11.64 --export "Linux/X11" output.x86_64
see the printout of:
Godot Engine v3.1.2.stable.official - https://godotengine.org
OpenGL ES 3.0 Renderer: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2
ERROR: copy: Failed to open
   At: core/os/dir_access.cpp:300.
ERROR: _fs_changed: Project export failed with error code 12.
   At: editor/editor_node.cpp:495.

Minimal reproduction project:

Duplicate of #18470.


feat: Added computed property CameraComponent.visibleWorldRect

Description
The new property camera.visibleWorldRect gives the Aabb of the world region visible through the camera. This can be useful for culling the render pipeline, or similar purposes.
(Still need to add docs & tests).
Checklist

[x] I have followed the Contributor Guide when preparing my PR.
[ ] I have updated/added tests for ALL new/updated/fixed functionality.
[ ] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[x] I have updated/added relevant examples in examples or docs.

Breaking Change?

[x] No, this PR is not a breaking change.

Related Issues

Not sure whether it's better to have it as Aabb2 or as a Rect.

Awesome stuff! I'll test this out tomorrow, I have a good usecase for this on the Sashimi engine that I made.

Not sure whether it's better to have it as Aabb2 or as a Rect.

The Aabb2 is a bit easier to work with, except when you have to compare with a Rect, which we get from the PositionComponents currently, so maybe we should have it as a Rect for now and then convert both for v2, if we feel the need for it?


Add failing test for Delete with a where clause evaluating to false

The Delete method fails with a System.Data.SqlClient.SqlException when the where clause evaluates to false. Obviously, it would be better not to call the Delete method at all if the expression is known to evaluate to false but I think it should not fail nonetheless.
I would love to propose a solution to this issue but unfortunately, I'm not yet familiar enough with LINQ to Entities.

Thank you for reporting this issue.
We will merge your tests and release a fix for the beginning of next week

The v1.3.9 has fixed this issue.
Please open an issue if you still have the same problem after downloading the latest version.


Lite 23308 add command to list the locales

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: qarlosh:x: Jonathan RiosJonathan Rios seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


never inject script/css into page

If content script (include style) is dynamically injected,all of them will appear in the network tab.


Fix stale props reference when sCU returns false

Adds +3 bytes. Fixes #1345 .

thanks! isn't it necessary to update state? maybe causes a similar problem.

Good point! I'll check if the same issue applies for state

Seems like we'll want state as well, yeah.

Coverage remained the same at 100.0% when pulling 33618f51c2c6b75137662ca0540f294df48c52e4 on stale_props_scu into c66ec75176ac5df60824adbe6152ed577fa7b74f on master.

Can confirm: The state is updated but is never referentially equal https://codesandbox.io/s/j00kl29rv

hold on I somehow messed up the history.


Package size info

Since I only need very basic lightbox functionality I'm looking for as lightweight a solution as possible, and I didn't notice anything on the documentation stating the package's additional size without the Bootstrap components. How big are the additional dependencies in KB?

it's listed in readme and on bundlephobia.

that said, this library does require bootstrap to work

it's listed in readme and on bundlephobia.

that said, this library does require bootstrap to work

perfect, thank you. My reasoning was that since I'm already using and loading in Bootstrap the only additional overhead would be the package itself.


example: intialization of InvenioOAuth2ServerREST

Initializes the InvenioOAuth2ServerREST extension when the example
application is created. (closes #62)

Signed-off-by: PaulinaLach<EMAIL_ADDRESS>

@PaulinaLach can you please have a look at #68 and if it's fine please rebase on top. Thanks


#112 Get rid of Vue dependency in the code.

Improve output bundle size by removing Vue dep and using moment.min.js
Reduced bundle size from 402kb to 176kb.
I think it's better to check if vue-multi-select is registered globally rather than checking if it's present in the window. Most of the time you register vue components with Vue.component... globally and don't necessarily put them in the window.

Nice PR. I did't know the this.$root stuff :)

I'm going to repeat myself from #114

I don't agree with the changes for moment.js.
By using the already minified version of moment, we reduce the chance of the minifier of vfg to do it's best job. It has to minify normal code with minified code, and I don't claim to know how it work, but I think that's not the best.
Also, we loose the sourcemap of moment.js.

I guess it I'm really nitpicking, but since the code will be minified at some point, why not wait for that moment (no pun intended). Or maybe minifying already minified code make it even more minified, and if it is the case, I'm sorry for my ignorance.
And I might add, the use of this.$root is super neat. Really well done ! 👍


Is it possible to use with apollo-client and react

Is it possible to use type-graphql in react with apollo-client?

No, Apollo Client is for fetching GraphQL data to client, while TypeGraphQL is for building the GraphQL server.
However, you might be interested in apollo-link-state (#197) or [apollo-link-schema](https://www.apollographql.com/docs/link/links/schema.html) - it should work using the type-graphql@next version.

Closing this for a housekeeping purposes 🔒

xdddssdsdsdsd


Fixed point scheme

Rebased version of #207. Initial results are promising going from 77% -> 55% LUT on tinyfpgabx.
TODO:

[ ] docs
[ ] Expose full fixed point values under "status" register group
[ ] Parametrics/constraints and assert cleanups

Will merge this as is, since it has been extensively tested on my bench here. Changes suggested in #218 would be better made on top of this. Also #218 would change documentation anyway, so easier to do it all at once.


flutter-devicelab-linux-4 test bed in bad state

flutter-devicelab-linux-4 is in a bad state and failing most of the tasks.
[backdrop_filter_perf__e2e_summary] [STDOUT] Executing: /opt/s/w/ir/cache/android/platform-tools/adb devices -l in /opt/s/w/ir/k/recipe_cleanup/tmpGHVZHD/flutter sdk/dev/benchmarks/macrobenchmarks
[backdrop_filter_perf__e2e_summary] [STDOUT] "/opt/s/w/ir/cache/android/platform-tools/adb" exit code: 0
[backdrop_filter_perf__e2e_summary] [STDOUT] stdout: List of devices attached
[backdrop_filter_perf__e2e_summary] [STDOUT] stdout: ZY22465WKN             device usb:1-4 product:athene model:Moto_G__4_ device:athene transport_id:1
[backdrop_filter_perf__e2e_summary] [STDOUT] stdout:
[backdrop_filter_perf__e2e_summary] [STDOUT]
[backdrop_filter_perf__e2e_summary] [STDOUT] Executing: /opt/s/w/ir/cache/android/platform-tools/adb -s ZY22465WKN shell getprop ro.bootimage.build.fingerprint ; getprop ro.build.version.release ; getprop ro.build.version.sdk in /opt/s/w/ir/k/recipe_cleanup/tmpGHVZHD/flutter sdk/dev/benchmarks/macrobenchmarks
[backdrop_filter_perf__e2e_summary] [STDOUT] Device chosen: ZY22465WKN
[backdrop_filter_perf__e2e_summary] [STDOUT]
[backdrop_filter_perf__e2e_summary] [STDOUT] Executing: /opt/s/w/ir/cache/android/platform-tools/adb -s ZY22465WKN shell dumpsys power in /opt/s/w/ir/k/recipe_cleanup/tmpGHVZHD/flutter sdk/dev/benchmarks/macrobenchmarks
[backdrop_filter_perf__e2e_summary] [STDOUT] stderr: Can't find service: power
[backdrop_filter_perf__e2e_summary] [STDOUT] "/opt/s/w/ir/cache/android/platform-tools/adb" exit code: 0
[backdrop_filter_perf__e2e_summary] [STDERR] Task failed: Bad state: No element

To prevent this type of problems in the future we need a mechanism to manually put a device on maintenance to prevent it from taking more tasks: https://github.com/flutter/flutter/issues/75277

We also need a health check for this use case to quarantine the device as soon as it detects power service is not up and running.

test bed is running tests well for a while. Closing this one.
Created https://github.com/flutter/flutter/issues/76130 to track health check.

Did we do something to fix it? I had to manually block it several times during the weekend and yesterday?

I didn't make any changes from my side. Thought you fixed something to bring it back to normal.
The bot seemed to get back to normal since 2/15/2021, 10:07:11 PM
What have you tried to block it manually?

I manually leased the bot for 24h twice during the weekend. Maybe a reboot fixed the problem did you try running the command manually? it was failing to find the power service.
If it is working know we should prioritize adding the health check as this single bot was causing tens of tasks to fail in a single commit.

Tested the command worked before closing hours ago.
Will implement the healthcheck.

Sounds good, thanks for the info. Let's close this one and follow up on the bug for the health check.


all: Add encoder params

This PR adds params needed for changing between "free" capture mode (aka period) and "line" capture mode (aka convert).
The PR #15 should be merged first, and then this PR rebased.

Thank you for review @bjornsundmannv now merging.


Switch to a different Geolocation API provider

Kinda of a quick fix for #22, might want to restructure/rewrite the Geocode struct/responses from the manual geocode request.

Sorry things are crazy w Dockercon for the time being you can pass location to not hit this old api but will take a look soon thanks
On Sun, Nov 15, 2015 at 11:56 PM -0800, "Vlad C."<EMAIL_ADDRESS>wrote:
Kinda of a quick fix, might want to restructure/rewrite the Geocode struct/responses from the manual geocode request.
You can view, comment on, or merge this pull request online at:
https://github.com/jfrazelle/weather/pull/23
Commit Summary
Switch to a different Geolocation API provider
File Changes
M
geocode/geocode.go
(24)

Patch Links:
https://github.com/jfrazelle/weather/pull/23.patch
https://github.com/jfrazelle/weather/pull/23.diff
—
Reply to this email directly or view it on GitHub.

ended up fixing via https://github.com/jfrazelle/weather/commit/90c77de96ff7991257a2b9881ee49260148c540f hostinng own server, thanks!


Discord Link In Documentation Is Invalid / Expired

Discord Link In Documentation Is Invalid / Expired

I don't have a channel on Discord.
The link is for Homebridge channel.

Ah ok, thanks.

Ah, ok thanks.

On Jun 9, 2022, at 11:43 AM, Yossi Hillali @.***> wrote:

I don't have a channel on Discord.
The link is for Homebridge channel.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


German lemmatization: Definite articles

Hi @adbar,
thanks for providing this really cool (and capable) library.
Currently, all German definite articles ("der", "die", "das") are lemmatized to "der", which is wrong.
import simplemma
simplemma.lemmatize("Das", lang=('de',))
# Output: 'der'
simplemma.lemmatize("Die", lang=('de',))
# Output: 'der'
simplemma.lemmatize("Der", lang=('de',))
# Output: 'der'

Normally, I would not be too picky about wrong lemmatization (this happens all the time). But since these are among the most common German words, this should be correct. Their respective lemma should be the same word each: "Das" -> "Das", "Die" -> "Die", "Der" -> "Der". The lemma should be lowercase, if the original token is lowerecased, too.

Hi @GrazingScientist, there are reasons for this behavior: In most treebanks the definite articles are reduced to a single version, mostly "der" or "d". That why I opted for this form, it's a choice, even if it's questionable.
As a side note, writing lang=('de') (i.e. string instead of tuple) should be fine.

☹ Okay! Thanks for clarifying this. ❤


Room description hides chat when new lines are spammed

Describe the bug
When room description has a lot of newlines, it is possible to essentially block the chat using the room description.
To Reproduce
Steps to reproduce the behavior:

Edit the room description, add a bunch of new lines (enter) in the end.

Expected behavior
Either:

trim excessive new lines.
have the room description be with maximum height\scrollable.
have the "see more" thing trigger when reaching a number of newlines.

Screenshots

What device are you on?
chrome on win10 pc
Additional context

Glad to report this was merged and is now working according to expectations.


Nondeterministic compilation. Sometimes fails, sometimes succeeds.

I am trying to compile some example program from Cursive on macOS 10.12.1 with
cargo 0.16.0-nightly (ddb5c32 2016-12-16) and I am having some problems.
I am using macos branch from Cursive project, and I've declared this in my Cargo.toml file like this:
[dependencies.cursive]
git = "https://github.com/gyscos/Cursive"
branch = "macos"

When I try to build with cargo build sometimes compilation is successful, and sometimes not. Here is my output:
MacBook-Air-Micha:terminal-tests mhl$ cargo clean
MacBook-Air-Micha:terminal-tests mhl$ cargo build
   Compiling unicode-segmentation v0.1.3
   Compiling cursive v0.3.5 (https://github.com/gyscos/Cursive?branch=macos#451d0522)
   Compiling odds v0.2.25
   Compiling libc v0.2.18
   Compiling unicode-width v0.1.3
   Compiling rustc-serialize v0.3.22
   Compiling ncurses v5.84.0
   Compiling toml v0.2.1
   Compiling terminal-tests v0.1.0 (file:///Users/mhl/Sources/terminal-tests)
error: linking with `cc` failed: exit code: 1
  |
  = note: "cc" "-m64" "-L" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib" "/Users/mhl/Sources/terminal-tests/target/debug/deps/terminal_tests-d163a702128509ba.0.o" "-o" "/Users/mhl/Sources/terminal-tests/target/debug/deps/terminal_tests-d163a702128509ba" "-Wl,-dead_strip" "-nodefaultlibs" "-L" "/Users/mhl/Sources/terminal-tests/target/debug/deps" "-L" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib" "/Users/mhl/Sources/terminal-tests/target/debug/deps/libcursive-589ffaec46642e7b.rlib" "/Users/mhl/Sources/terminal-tests/target/debug/deps/libunicode_segmentation-1400e9f38485b222.rlib" "/Users/mhl/Sources/terminal-tests/target/debug/deps/libncurses-64b8ed169553261c.rlib" "/Users/mhl/Sources/terminal-tests/target/debug/deps/libtoml-5130c1b472bb88f9.rlib" "/Users/mhl/Sources/terminal-tests/target/debug/deps/libunicode_width-a8b627b65c290dac.rlib" "/Users/mhl/Sources/terminal-tests/target/debug/deps/liblibc-73c6422e7b19c2f3.rlib" "/Users/mhl/Sources/terminal-tests/target/debug/deps/librustc_serialize-03b62901d97343ea.rlib" "/Users/mhl/Sources/terminal-tests/target/debug/deps/libodds-798c90752ba21e6f.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libstd-713ad88203512705.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libpanic_unwind-8db31eff4f3f5d1c.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libunwind-9d903f075d9d1ed3.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/librand-15da1025aec585ac.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libcollections-eba7f19f0aae5f37.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/liballoc-0fa051c7d0594505.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/liballoc_jemalloc-9dddbb08233542f3.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/liblibc-72ccf8e77ba91924.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libstd_unicode-d3fcdc16d2a25b3a.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libcore-407db9a296a50c43.rlib" "/Users/mhl/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libcompiler_builtins-dfc954c33c85abed.rlib" "-l" "ncursesw" "-l" "System" "-l" "pthread" "-l" "c" "-l" "m"
  = note: ld: library not found for -lncursesw
clang: error: linker command failed with exit code 1 (use -v to see invocation)

error: aborting due to previous error

error: Could not compile `terminal-tests`.

To learn more, run the command again with --verbose.
MacBook-Air-Micha:terminal-tests mhl$ cargo build
   Compiling ncurses v5.84.0
   Compiling cursive v0.3.5 (https://github.com/gyscos/Cursive?branch=macos#451d0522)
   Compiling terminal-tests v0.1.0 (file:///Users/mhl/Sources/terminal-tests)
    Finished debug [unoptimized + debuginfo] target(s) in 6.41 secs

I can type cargo build couple of times, and cursive v0.3.5 would be recompiled every time, sometimes failing like I've shown before, sometimes being successful.
When completion is reported as successful I am able to run resulting binary without any problems.

I debugged this a bit and found it was related to the feature set of a crate changing. This I suspect is due to target-specific features being used which in turn makes me think that this is a dupe of https://github.com/rust-lang/cargo/issues/2524. I haven't seen the nondeterministic behavior here before, though, so that's good to know!
For now I'm going to close this in favor of https://github.com/rust-lang/cargo/issues/2524, but I'll give that issue another stab at fixing.


pip install -r ~/devel/my_ocrd_workflow/requirements-ppn2ocr.txt seems to need scikit-build

@cneud reports:

Ich notiers nur kurz hier als Erinnerung...damit für https://github.com/mikegerber/my_ocrd_workflow#ppn2ocr opencv-headless gebaut wird musste ich noch scikit-build per pip installieren

Collecting opencv-python-headless (from ocrd->-r /home/cnd/tmp/dev/qurator/my_ocrd_workflow/requirements-ppn2ocr.txt (line 4))
  Downloading https://files.pythonhosted.org/packages/2f/b4/2ddaaecc332e6ddafb7726abb6139955a99282afe5f370930890bb572707/opencv-python-headless-<IP_ADDRESS>.tar.gz (88.9MB)
    100% |████████████████████████████████| 88.9MB 18kB/s
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-wx36s1mb/opencv-python-headless/setup.py", line 9, in <module>
        import skbuild
    ModuleNotFoundError: No module named 'skbuild'
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-wx36s1mb/opencv-python-headless/

It's this issue from the opencv-python FAQ:

Q: Pip install fails with ModuleNotFoundError: No module named 'skbuild'?
Since opencv-python version 4.3.0.*, manylinux1 wheels were replaced by manylinux2014 wheels. If your pip is too old, it will try to use the new source distribution introduced in <IP_ADDRESS> to manually build OpenCV because it does not know how to install manylinux2014 wheels. However, source build will also fail because of too old pip because it does not understand build dependencies in pyproject.toml. To use the new manylinux2014 pre-built wheels (or to build from source), your pip version must be >= 19.3. Please upgrade pip with pip install --upgrade pip.

TL&DR: Always upgrade pip first because otherwise bad things happen. In this case, both the binary and the source install fails because of an old pip.

Side note: This was probably triggered using Ubuntu's system pip, so not in a venv. Always use a venv unless you know what you're doing. (And if not, upgrade pip!)

https://github.com/mikegerber/my_ocrd_workflow/blob/master/README.md now mentions this issue and the fix (upgrade pip)!


Parameterize preprocessing scripts

In reference to question on generalization of scripts/server_downloading_prep.slurm:

Yes, it'd need another bash script (e.g. something like submit_server_downloading_prep.sh) to submit this Slurm job with parameterized account info.
I think parameterizing preprocessing scripts like this could be added as another issue.

Originally posted by @thompsonmj in https://github.com/Imageomics/distributed-downloader/pull/4#discussion_r1617780675

May also want to consider option to set batch size in .env as noted here.


allow pass 'delay' props into TouchableOpacity

allow pass delayPress... props in.
all in ms.
delayPressIn default in RN is 0
delayPressOut default in RN is 0
delayLongPress default in RN is 500

Published in 2.1.0.


Two-layer shallow water equations

This adds an implementation for the two-layer shallow water equations with entropy conservative and entropy stable fluxes in 1D and 2D. The changes include:

1D equations for Tree mesh
2D equations for Tree mesh & Unstructured mesh
Initial condition & source terms for a manufactured solution
A slip-wall boundary condition (for Tree mesh in 1D & Unstructured mesh in 2D)
Example elixirs for convergence, well-balancedness and a dam break
Test files for the new features

I am still working on my full review. But these two suggestions I believe will fix the broken tests due to the breaking changes introduced with Trixi v0.5. Is that right @ranocha ?

Yes, looks correct :+1:

@andrewwinters5000 Please feel free to request a review from me once your comments are adressed

Does this also work for P4estMesh2D? Or is it "in general yes, but we haven't tried it yet"?


implement set_sample_rate for seq/reset/resetV/ramp

ah resetv and seq and select and all those (copies net into itself) also need to set sr of those nets

okay this just needs testing now to make sure nothing weird happened, but i think we're in good shape. grace works fine with sr() meaning at least seq/resetV/select work as expected

pd works too, that covers ramp and trig_reset


Disable request signing when basic auth is enabled

Description
Disabled request signing when basic auth is enabled so that AWS request signing doesn't have to be explicitly enabled.
Issues Resolved
#116
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Just tested this locally and it works fine for basic auth workflows.

Thanks @Sovietaced for your contribution, is this a similar problem https://github.com/opensearch-project/terraform-provider-opensearch/issues/102 that can be solved with this PR?

Thanks @Sovietaced for your contribution, is this a similar problem https://github.com/opensearch-project/terraform-provider-opensearch/issues/102 that can be solved with this PR?
@bbarani

Possibly. I'm not sure if #102 has been root caused

Thanks @Sovietaced, Can you please add some unit tests to test this change? Thanks

I see one of your another PR https://github.com/opensearch-project/terraform-provider-opensearch/pull/114 (~ same subject), any co-relation between these 2 PR's?

I assume this PR https://github.com/opensearch-project/terraform-provider-opensearch/pull/117 is to disable sigv4 (signAWSRequests) automatically when basic auth is enabled and this one https://github.com/opensearch-project/terraform-provider-opensearch/pull/114 is to tell the user to disable the signAWSRequests manually ?

I see one of your another PR #114 (~ same subject), any co-relation between these 2 PR's?

They are related. I made them separate pull requests because I wasn't sure how receptive you would be to a code change while a doc change is pretty straightforward.

Thanks @Sovietaced, Can you please add some unit tests to test this change? Thanks

I had looked into adding unit tests but I don't see any existing coverage for basic authentication. I'm not even sure how I would observe that the options have been set on an HTTP client (besides setting up a mock HTTP server) which seems like quite a bit of work.

Looks to me like if this PR goes in we dont have to explicitly disable the request signing right ? This PR https://github.com/opensearch-project/terraform-provider-opensearch/pull/114 mentions to disable it.
@Sovietaced

Looks to me like if this PR goes in we dont have to explicitly disable the request signing right ? This PR #114 mentions to disable it.
@Sovietaced

That is correct. If the documentation PR merges I will rebase this. If we'd like to merge this (and close the documentation PR), I can update the documentation accordingly.

I will just prepare this pull request to remove the option to disable request signing.

Thanks @Sovietaced I will go ahead and merge the documentation PR https://github.com/opensearch-project/terraform-provider-opensearch/pull/114, please try to add some unit tests for this PR and then we can proceed to merge this. WDYT?
Thanks

Thanks @Sovietaced I will go ahead and merge the documentation PR #114, please try to add some unit tests for this PR and then we can proceed to merge this. WDYT?
Thanks

Sounds good. Taking a look at things now.

@prudhvigodithi I took a look at the test code here and I don't think there is much I can really do. There exists zero unit test code that targets basic authentication, and it makes sense because provider.getClient is not very testable. The return value of provider.getClient is a struct that we have no visibility into. The area where I am modifying code is reasoning about ClientOptionFuncs which are not even comparable as far as I know so I cannot refactor that into a method that is callable from unit tests.
It looks like the existing code had resorted to one of the following:

Implicitly testing basic authentication with every single acceptance test that runs against an ElasticSearch domain setup with basic auth.
Factoring out subsets of the logic of provider.getClient into functions like awsSession that can be called within unit tests and reasonable asserted against.

If we really care about preventing regressions against AWS Opensearch, there should be a way to run integration tests against AWS Opensearch. Given that AWS Opensearch is closed source and cannot be run locally by the public, the only reasonable way to do integration tests is to run actual integration tests against an ephemeral instance of AWS Opensearch on AWS, IMO. And that is something I don't think I should be responsible for.
Please let me know if you had any other ideas around unit testing.

@prudhvigodithi The changes are working for me, the following terraform code worked using this PR
https://github.com/rblcoder/terraform-opensearch-samples/blob/main/aws_opensearch_basic_auth_auto_PR117/main.tf

@prudhvigodithi Can we merge this PR?

Hey @Sovietaced can you please take care of the conflicts, we can proceed to merge this PR.
Thanks


TestCase querying issue

Hi,
Based on the ETMSample, I wrote a query that should retrieve all the test cases of a given project area.
The result of this query is always an empty array, although there is actually 3 test cases in this project area.
Did I missed something ?

String catalogUrl = new RootServicesHelper(<My QM URL>, OSLCConstants.OSLC_QM_V2, client).getCatalogUrl();
String serviceProviderUrl = client.lookupServiceProviderUrl(catalogUrl, <My QM project area>);
String queryCapability = client.lookupQueryCapability(serviceProviderUrl, OSLCConstants.OSLC_QM_V2, OSLCConstants.QM_TEST_CASE_QUERY);
OslcQueryParameters queryParams = new OslcQueryParameters();
queryParams.setPrefix("rdf=<http://www.w3.org/1999/02/22-rdf-syntax-ns#>");
queryParams.setWhere("rdf:type=<http://open-services.net/ns/qm#TestCase>");
OslcQuery query = new OslcQuery(client, queryCapability, -1, queryParams);
OslcQueryResult result = query.submit();
Assertions.assertNotNull(result);
Assertions.assertEquals(3, result.getMembersUrls().length);

Sorry, I didn't mentionned that the Lyo oslc-client version being used is the 4.0.0.
I also created a post on jazz.net (https://jazz.net/forum/questions/277030/testcase-querying-issue)
Thanks

@j-barata I have no working experience with OSLC Query specifics on Jazz tools. I will close this ticket for now but if you find that Lyo caused the query to be prepared incorrectly, please feel free to reopen the ticket. Also, if you find a mistake in your code, we will be happy to update the samples.

I will try to answer on your post on Jazz form.
I also suggest you post to Lyo community on https://forum.open-services.net/.
Otherewise agree that we open this issue here once we know there is a bug for Lyo to solve.


[JSON viewer] Make JSON data editable

From @BenClist-BC2  in https://github.com/MicrosoftEdge/DevTools/issues/238#issuecomment-2083635047:

we use browser extensions to take JSON data and make it editable. One example of this allows administrators to make easy updates and fixes to records in Microsoft Dataverse on data that isn't necessarily displayed on the frontend.

@benClist Can you explain how you make the data editable exactly? Does the extension you use have a way to save the data back to disk? Which extension is it?

@captainbrosset It's writing back to Dataverse directly, it's not something you want to build into Edge. There's a public example that uses the same approach here https://chromewebstore.google.com/detail/prettifymywebapi-for-micr/pcgbnpkpijlcjeleijaaahlonafdlfno


Support direct reference of includes types in mapping sourcepaths

Due to legacy reasons for how includes types are represented in paths in SHR FHIR export, the way you reference them in the mapping file is different than how you might reference them in a data elements file.
In short, you replace the original identifier with the new includes type identifier.  For example, if in your definition you had:
Components.ObservationComponent
  includes 0..1 SystolicPressure
  includes 0..1 DiastolicPressure

You would reference those in mappings as:
Components.SystolicPressure maps to ...
Components.DiastolicPressure maps to ...

This works with a corresponding branch / PR on shr-fhir-export and the bp_component_mapping branch of shr_spec.

Please do not merge.  Only approve (if appropriate).


reduce complexity of send_read_receipt based on scroll position

Implemented: Start a 5-second timeout timer whenever scrolling stops, and then after the timer has reached its timeout deadline, send the read receipts for the last visible event.
https://github.com/project-robius/robrix/pull/152#discussion_r1782110627

To add:

Need to scroll pass read maker, in order to send fully read receipt. need to save the position of read marker VirtualTimelineItem::ReadMarker

Combine PR here: https://github.com/project-robius/robrix/pull/206


Using Custom Templates

How can I use this plugin with custom templates? I have tried highlighter and render. But they did not work. Thanks in advance.

my bad. highlighter does exactly what I need. This plugin is the easiest among counterparts. Thanks.


⚠ Bofrost.be has degraded performance

In eccf91e, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1477 ms

Resolved: Bofrost.be performance has improved in c29c42e after 6 minutes.


pyopae: Fix definition of fpga_interface enum

Signed-off-by: Tim Whisonant<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
13141

Relevant Lines:
19919

💛  - Coveralls


Improving interface.

Hello @Spandan-Bhattacharya
I wish to make the interface  look better of 4x4 sudoku page and insert a back button which returns to the homepage.
Please assign me this under JWoC'24.

This issue has already been assigned as per the issue #9 . If the issue in not closed in the given time, it will be re assigned.

Everyone if you have not joined the Discord server yet, please do so, as I will be sharing instructions on the solve-it! channel under projects.
Link to the server:
https://discord.gg/bcgZ9RZZ8r


Runtime API to expose log message metadata

Description:
In the current Log API design, the Log message doesn’t contain the exact code line the log message is printed. It is useful if this information could be added to every log message.
At the moment, the only way to extract this information is through the stack trace. However, this is not a proper solution and has an adverse performance impact. There needs to be a Runtime API to support this requirement.
More information regarding this requirement can be found in the discussion here[1].
[1] https://github.com/ballerina-platform/ballerina-standard-library/discussions/772

Blocker for https://github.com/ballerina-platform/ballerina-standard-library/issues/900

Blocker for https://github.com/ballerina-platform/ballerina-standard-library/issues/900

removing priority tag as per the discussion with Danesh

removing priority tag as per the discussion with Danesh

@MadhukaHarith92 What are the exact metadata required for log api from runtime?

@warunalakshitha we need the code line number. It would be meaningful if you could provide, the module name, file name, and then line number.


mpsc: add owned refs

Currently, the SendRef and RecvRef types returned by thingbuf::mpsc's senders and receivers contain a borrowed reference to the channel's queue. This means that a Ref from a channel cannot live for the 'static lifetime. However, because the channel's queue is either internally reference counted (in the case of the dynamically allocated MPSCs) or lives in a static variable (in the case of the static MPSCs), it should also be possible to create a reference to a queue slot that is 'static.
We could add an API like tokio::sync::mpsc's Sender::reserve_owned, which clones the internal Arc around the channel's shared data and returns a permit whose lifetime is not bound to a borrow of the Sender handle that produced it.
This could potentially enable some neat stuff, like using a thingbuf mpsc::Receiver of Vec<u8>s as a http_body::Body without having to copy data out of the thingbuf --- in this case, an OwnedRecvRef type could be passed directly into hyper or another HTTP library, and when the library finishes sending the body chunk, that ref is dropped, returning the buffer to the pool.

This should be pretty straightforward but may require a bit of refactoring internally.


Server enchanting

Vanilla Tweaks Version:1.12.2
MinecraftForge Version:<IP_ADDRESS>38
Minecraft Version:1.12.2
(Optional) Just Enough Items (JEI) Version:<IP_ADDRESS>8
(Optional) Baubles Version: 1.5.2
Client or Server?:

[ ] Client
[X ] Server

Crash Report (via. Hastebin):
What happens / happened?:When I try to apply the vanilla tweaks enchants like "Vigor", "Nimble", and "Hops" (Only 3 ive found so far) it doesnt work. It acts like it will but when I pick it up it vanishes and the book and armor goes back into the anvil slots.
 Reloaded (by BeetoGuy)
Better Questing (by Funwayguy)
Better Questing - Standard Expansion (by Funwayguy)
Project: Vibrant Journeys (by solis_nova123)
OpenModsLib (by OpenMods)
OpenBlocks (by OpenMods)
Straw Golem (by fradige9512794)
Dynamic Surroundings (by OreCruncher)
[ANGRY PIXEL] The Betweenlands (by oily_oli)
JourneyMap (by techbrew)
Hwyla (by TehNut)
GottschCore (by gottsch)
Phosphor (by jellysquid_)
FTB Utilities: Backups (by LatvianModder)
Extra Utilities (by RWTema)
Comforts (by theillusivec4)
ViesCraft - Airships! (by Viesis_Gaming)
The Beneath (by Shinoow)
Colossal Chests (by kroeser)
AppleCore (by squeek502)
The Eight Fabled Blades (by shelterrin)
Better Advancements (by Way2muchnoise)
InGame Info XML (by Lunatrius)
LunatriusCore (by Lunatrius)
Reborn Core (by modmuss50)

There exists no  VanillaTweaks verson as 1.12 .2 can you provide the correct version (can be seen under VanillaTweaks in mods)

Also if you are using RAD i would recommend you update the VanillaTweaks version alone as yesterday i released an version which fixed server crash related to enchantments.

This is also happening to me, only on a server, in version 1.5.3 of Vanilla Tweaks. Though I've only seen it with nimble (haven't tested the others).

Update to 1.5.4 version of vanillatweaks


Add support for point collision to the spatial partitioning algorithm.

Currently the collision algorithm is designed to work with polylines, expand it to work also with points.

What does that mean? Can we filter now by all the lines that fall only inside the TimeBox? AND vs OR?

No, it was a previous step for the feature of filtering all polylines that fall only inside the timebox (which has not yet been implemented). However, I have found another way to do it that instead of being based on points, it is based on the polylines themselves which is more accurate.
The method requires the polyline to cut the TimeBox only on its vertical lines, without cutting the horizontal lines. In this way only the polylines that are inside the TimeBox for the interval in X defined by the TimeBox will be selected. It would be necessary to take into account some special cases, but that would be the idea.
What do you think?


Add alpha and beta references to README.rst.

Towards #2820.

Hey guys. So the Beta/Alpha links you gave was a good attempt! But these apply to the Services in Google Cloud (and doesn't apply to client libraries really). So for now the idea is to just add what "Beta" and "Alpha" means in the Versioning section. We can always change later or have a centralized location in gcloud-common or something. But at least it gives a succinct explanation. You can see the PR for PHP as a reference: https://github.com/GoogleCloudPlatform/google-cloud-php/pull/274 (which you probably already have).
High Priority: Pub/Sub is NOT Beta. Please we need to put in the Alpha section!

@omaray I moved Pub/Sub to the Alpha section and put the Version section back.
Let me know if this looks good to you?

@omaray Out of curiousity, what is the rationale for holding Pub/Sub as "alpha"?  I don't recall any discussion of it, and we've been talking about the "fab five" for months.

@daspecster @omaray FWIW, whether Pub/Sub is part of some big picture or not, we are treating it (local to Python) like it is "beta" quality.

@dhermes @omaray what if we changed the verbage to something like...
+ This client supports the following Google Cloud Platform services which are at a Beta_ quality level
- This client supports the following Google Cloud Platform services at a Beta_ quality level


Added support to momentjs in amd and commonjs environments.

This code will load momentjs when and if needed.
I tested this with Webpack and everything is working as expected. I'm pretty confident this works also with CommonJs and I hope it works also with AMD.
This is the best I can achieve with my little experience.
This completes #356.

Hi,
Instead of multiple call for loadMoment(); you should call it only once if date/range_date filters are being defined in setup of yadcf, so I'd day you better call the loadMoment(); once in the function init(oTable, options_arg, params) {  above the if ($(instance.selector).length === 1) { line, add there something like loadMomentIfNeeded(); inside which you will iterate over filters and see if  date/range_date filter was used and if so, then call the if (!moment && ((typeof define === 'function' &&.... code, that way it will be cleaner and more efficient, also, please update only the yadcf js file inside the src folder , the yadcf .js in the root is a stable version while the src is for beta versions
Thanks

I will do those changes asap. Meanwhile you can reopen this pull request because I will continue to work on the same branch amending this pull request's commit.

I've fixed this pull request finally, sorry for the delay. My IDE has automagically deleted some tabs/spaces, I hope it is not a problem.

Hi,
Instead of the loadMomentIfNeeded I will provide you to call your own function that will be provided to the yadcf and will be invoked right away, after my commit you will add some more code related to the moment module, so stay tuned.
Thanks,
Daniel.


refactor: move callToParameterValue into NodeMapper

Summary of Changes
Move the method callToParameterValue to SafeDsNodeMapper. Previously, it was private in SafeDsAnnotations. Given a call and a parameter (or its name), it returns the value assigned to the parameter in the call. It also takes default values into account.

:tada: This PR is included in version 0.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.4.0
GitHub release

Your semantic-release bot :package::rocket:


MachineLearning.EstimateClassificationProbability and EstimateClassificationProbabilities needlessly divide tolerance by model size

The functions EstimateClassificationProbability and EstimateClassificationProbabilities in Microsoft.Quantum.MachineLearning namespace divide the passed tolerance by model size. There are multiple problems with this:

Firstly, doing this is unnecessary. It is possible to bound the probability error in terms of encoding error, and this bound doesn't depend on model size. To put it in simple terms, longer models are no more sensitive to encoding errors, so this division makes no sense.
When using EstimateClassificationProbabilities, the division is done twice: once in EstimateClassificationProbabilities and once more in EstimateClassificationProbability.
Thanks to #274, EstimateClassificationProbabilities now handles the special case of model length being 0. Unfortunately, EstimateClassificationProbability still doesn't handle this case properly.

@cgranade, would an easy solution be to simply remove said division? What are your thoughts?


JFrog CLI - upload command throwing time out error

When trying to upload a heavy weight artifact of 3 GB's to a repository using CLI , facing a time out issue. Is there any settings that can be explicitly defined on the CLI config to control the time out or the file upload size limit ?

@srini289,
After starting to upload the file, how long does it take for the CLI to throw the timeout?
Also, are you uploading the large file to Artifactory or Bintray?

I am trying to upload a 3GB .zip archive file to Artifactory. The time out happens when the upload process runs more than an hour(just an approximate interval)

@eyalbe4,
The artifact is getting uploaded when using curl command with out any time out. The artifact got uploaded to artifactory in ~160 minutes
Tried uploading the same artifact using the jfrog cli with the below command and it gets timed out after ~130 minutes
jfrog.exe rt u "Path/*.zip" "generic-release-local/../../.zip"
Size of artifact is 3.4 GB

@srini289,
We're trying to figure out why this happens. We actually don't set any timeouts for uploads, so golang's default http timeouts should be used.
A clue that may help us pinpoint the cause:
Does it always fail after about 130 minutes? What do you see if you attempt to run the commands a few times?

The time out is not consistent , some time it times out after  150 minutes / 90 minutes when tried uploading the artifact a couple of times back to back. I see that the issue happens even on an artifact that is of 1 GB size.
Could it be the a setting / input buffer that is restricting to support heavy weight artifacts?

@srini289,
We looked into this further. The CLI's code does not include any limit or buffer that should block the client from uploading large files.
Maybe the Artifactory or proxy logs include a hint as for the root cause of this timeout.

@srini289,
Are you still experiencing this issue?

@eyalbe4 we are now facing this same issue trying to upload to our local Artifactory instance


[pritunl] Add feature to expose multiple ports to pritunl

what

[pritunl] exposing multiple ports via variable that accepts comma delimited list of ports
[pritunl] fix variable without default, otherwise it was failing with

could not deduce `environment:` block, configuring only .Environment.Name. error: failed to read pritunl.yaml.part.0: reading document at index 1: yaml: line 95: did not find expected key
failed to read pritunl.yaml: reading document at index 1: yaml: line 95: did not find expected key

why

so pritunl can serve multiple vpn configurations

Those changes are tested when PRITUNL_VPN_PORT was not configured, when it had the same value as default and for two ports.
Only change is that we need to enumerate services added.

Why we need default value for UI external host?

[pritunl] fix variable without default, otherwise it was failing with
could not deduce `environment:` block, configuring only .Environment.Name. error: failed to read pritunl.yaml.part.0: reading document at index 1: yaml: line 95: did not find expected key
failed to read pritunl.yaml: reading document at index 1: yaml: line 95: did not find expected key

This is part of monochart that expand this variable:
  rules:
{{- range $host, $path := $ingress.hosts }}
    - host: {{ $host }}
      http:
        paths:
          - path: {{ $path }}
            backend:
              serviceName: {{ $serviceName }}
              servicePort: {{ hasKey $ingress "port" | ternary $ingress.port "default" }}
{{- end -}}

Without default it breaks syntax

@Nuru @osterman I have reverted changes that require helmfile update with this commit
https://github.com/cloudposse/helmfiles/pull/247/commits/471fcb24abe080aa521afd362e85f39ea6e21f6d
Please approve so I can proceed


Revert "Bump sphinx from 7.4.7 to 8.1.3"

Reverts ImperialCollegeLondon/virtual_ecosystem#610
Still need to get dependabot to leave sphinx alone. I've now got develop and main to require docs_build to pass

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.18%. Comparing base (e690579) to head (d9884c5).
Report is 8 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #611      +/-   ##
===========================================
- Coverage    95.25%   95.18%   -0.07%
===========================================
  Files           74       74
  Lines         4380     4380
===========================================
- Hits          4172     4169       -3
- Misses         208      211       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.