Fix cfn_nag security warnings / errors

deployment/media-insights-test-operations-stack.yaml
Failures count: 0
Warnings count: 0
deployment/string.yaml
Failures count: 0
Warnings count: 0
deployment/media-insights-dataplane-streaming-stack.template
Failures count: 0
Warnings count: 0
deployment/media-insights-stack.yaml
| WARN W74
|
| Resources: ["SystemTable", "WorkflowTable", "StageTable", "OperationTable", "HistoryTable", "WorkflowExecutionTable", "DataplaneTable"]
| Line Numbers: [583, 600, 617, 634, 651, 672, 708]
|

DynamoDB table should have encryption enabled using a CMK stored in KMS

FAIL F3

Resources: ["MieHelperExecutionRole"]

Line Numbers: [133]

IAM role should not allow * action on its permissions policy

| WARN W84
|
| Resources: ["MieLogGroup"]
| Line Numbers: [127]
|

CloudWatchLogs LogGroup should specify a KMS Key Id to encrypt the log data

WARN W28

Resources: ["SystemTable", "WorkflowTable", "StageTable", "OperationTable", "HistoryTable", "WorkflowExecutionTable", "DataplaneTable"]

Line Numbers: [583, 600, 617, 634, 651, 672, 708]

Resource found with an explicit name, this disallows updates that require replacement of this resource

| WARN W47
|
| Resources: ["WorkflowExecutionEventTopic"]
| Line Numbers: [814]
|

SNS Topic should specify KmsMasterKeyId property

WARN W48

Resources: ["WorkflowExecutionEventQueue", "WorkflowExecutionLambdaDeadLetterQueue", "StageExecutionDeadLetterQueue", "StageExecutionQueue"]

Line Numbers: [841, 876, 885, 894]

SQS Queue should specify KmsMasterKeyId property

Failures count: 1
Warnings count: 20


hotfix: change default RUN_AS_DEVIN to true and change some network setting

Quick fix the problem #887 introduced in #847. Firstly change the RUN_AS_DEVIN: 'true'.
After changing also meet problem like
pexpect.pxssh.ExceptionPxssh: Could not establish connection to host

After trying locally with ssh -p 2222 opendevin@localhost still will meet.
So do little change to the docker network setting. (not sure this change from my local env setting, or a wrong docker network configruation)

same problem, met
pexpect.pxssh.ExceptionPxssh: Could not establish connection to host

same problem, met
pexpect.pxssh.ExceptionPxssh: Could not establish connection to host

Do my new change about netwrok setting can fix it? Or you still meed the problem after my change?

After.
Should I merge xingyaoww's commits too?

@Luckytiger666
Can you try running on #891, too? I didn't encounter any issues with my local setup. Can you try first running docker ps to see if there's a container named sandbox-XXX created by opendevin, then try to docker stop these containers? After this, try rerun the whole thing?

restart the container, and it works fine now

It's better to first check with ssh -p 2222 opendevin@localhost. I found that there is an old host key.

Offending RSA key in ~/.ssh/known_hosts:13

Delete line 13 from the known_hosts file, save, and restart to fix the issue.


Can CloudStorageTools be used on php app engine flexible?

I'm interesting on using the image tools but so far I've only seen documentation on the standard environment.

@mgallegos It only works on the App Engine Standard Environment.


What is the criteria of graduation from corfxlab?

Microsoft.Experimental.Collections has a useful implementation of MultiValueDictionary, but it now appears abandoned in alpha state. A discussion on corefx indicates corefxlab is a good place for it, but what is the process to bring it to release from here?

Good question. I have not thought about it. @terrajobst, @richlander, @joshfree, any opinions?

@ianhays

@ianhays is going to be open sourcing Microsoft.Expermiental.Collections to /dotnet/corefxlab very soon.

Heya @codekaizen, I wrote this last summer! Now that I'm back at Microsoft I'm planning on moving this along closer to the core repo but there's been some discussion as to where it should go. Our options are to put it either:

In the dotnet/corefxlab repo.
In a dev/MultiDictionary branch off of the main dotnet/corefx repo.

The home for the MultiDictionary ultimately depends on how out of the park it is; corefxlab was designed for ideas that were may not make it to the main repo and that are in the more distant future. @terrajobst and I discussed this and were leaning towards just branching it off of master as an addition to System.Collections.Generic, but that decision isn't set yet.
Regardless of where it will be, you can expect to see it somewhere soon :)

@ianhays - glad to see you back! I'd agree with the sentiment that MultiValueDictionary doesn't seem too far astride of core collection classes, and having it in core would be unremarkable. A branch seems reasonable, but then my question becomes - "what becomes of the branch"? Even if it is merged to master at some point, the current availability of it as a separate package, which has good value for users not running Core, will be lost.

@codekaizen Sorry for the delay; it's been real busy around here! I decided to put it into CoreFXLab for now and just pushed a PR dotnet/corefxlab#370 where we can continue iterating on it until it's ready for CoreFX. For now it is in it's own assembly: System.Collections.Generic.MultiValueDictionary. I tested it with some console apps running on the core framework and it works as expected.

Even if it is merged to master at some point, the current availability of it as a separate package, which has good value for users not running Core, will be lost.

It's been months but I'm honestly still not sure that I have a good answer to this. In it's current home in CoreFXLab it can easily be built as a desktop NuGet package since it is standalone, but once it is merged into CoreFX it will be jumbled together with the other Collections classes. We could always keep a desktop copy of the nupkg that only contains the MVD and push package updates that way. Although that would be the simplest solution it would require effort to maintain two copies of the same MVD code and subsequently be prone to error or stale versions. Another concern is if the CoreFX MVD evolves to depend on something that doesn't exist in the Desktop framework - what do we do then? How do we prioritize changes and updates to the MultiValueDictionary between Desktop and Core if they diverge and what does that look like?
To answer the original question: the members of CoreFXLab are primarily focused on eventual inclusion into .NET Core so for now I'm going to keep with that focus and consider the "graduation" to be merging it into CoreFX as a part of System.Collections.Generic.

We could always keep a desktop copy of the nupkg that only contains the MVD and push package updates that way

@ianhays Doesn't the same apply to System.Collections.Immutable? That one is in CoreFx and the nupkg works on Desktop.

Yes, but it is slightly different since Immutable is a standalone library whereas MultiValueDictionary would be built in to System.Collections.Generic. Of course I suppose I could just add a System.Collections.Generic.MultiValueDictionary.Desktop.csproj that only pulls in the MVD files from Open to build the Desktop version and nupkg that only contains the MVD.

Hi, are there any plans to include the MultiValueDictionary in the BCL or as a (non-prerelease) nuget?

There are no plans to do that. It's archived. See https://github.com/dotnet/corefxlab/pull/2245#issuecomment-386102595.
@ahsonkhan @KrzysztofCwalina This issue probably should be closed.

Oh well, thanks.

Closing this old issue now that MVD has been archived.
https://github.com/dotnet/corefxlab/blob/master/README.md#archived-projects
https://github.com/dotnet/corefxlab/tree/master/archived_projects/src/System.Collections.Generic.MultiValueDictionary


Feature detection modules update

This update adds info on:

GridMass
Target Feature detection
Recursive IMS Builder (quire rudimentary at the moment)

&

Data import/export
Raw data filtering
File merging

Also, the license information is added to the footer


Fix typo - remove duplicate bind of addParticipants()

Details

Removed the duplicate of this.addParticipants = this.addParticipants.bind(this);
Fixed Issues

NA
Note
Tiny issue. Doesn't need to go through upwork etc.
For reference
https://expensify.slack.com/archives/C01GTK53T8Q/p1625098788311200

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Problem with Swift 5, problem raising from Stevia fillContainer()

Hi,
I got a problem with Swift 5, and Problem raising from Stevia fillContainer()

My Issue is solved by updating with latest Stevia.framework

@shopno111 This will be fixed in next (swift 5) version coming soon, thanks for your patience :)

This is now solved in https://github.com/Yummypets/YPImagePicker/releases/tag/4.0.0


Authorization Spike (custom)

Codecov Report

Merging #1418 (12fa831) into main (e914dfe) will decrease coverage by 9.55%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1418      +/-   ##
==========================================
- Coverage   36.91%   27.36%   -9.56%
==========================================
  Files         157      158       +1
  Lines       11525    11565      +40
==========================================
- Hits         4255     3165    -1090
- Misses       6638     7935    +1297
+ Partials      632      465     -167

Flag
Coverage Δ

acceptance-apps
24.71% <50.00%> (-0.05%)
:arrow_down:

acceptance-cli
?

unittests
8.22% <87.50%> (+0.51%)
:arrow_up:

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

Impacted Files
Coverage Δ

internal/api/v1/router.go
100.00% <ø> (ø)

internal/api/v1/auth.go
100.00% <100.00%> (ø)

internal/cli/server/server.go
54.54% <100.00%> (-7.73%)
:arrow_down:

internal/api/v1/application/importgit.go
0.00% <0.00%> (-67.70%)
:arrow_down:

helpers/tar.go
0.00% <0.00%> (-66.67%)
:arrow_down:

internal/api/v1/appchart/show.go
0.00% <0.00%> (-64.71%)
:arrow_down:

internal/api/v1/appchart/create.go
0.00% <0.00%> (-61.30%)
:arrow_down:

internal/api/v1/service/delete.go
0.00% <0.00%> (-60.00%)
:arrow_down:

internal/api/v1/env/show.go
0.00% <0.00%> (-59.10%)
:arrow_down:

internal/api/v1/application/exec.go
0.00% <0.00%> (-57.90%)
:arrow_down:

... and 50 more

Continue to review full report at Codecov.

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


Remove version: Jackett.Jackett version 0.21.1217

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.21.1217/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)

URL: https://github.com/Jackett/Jackett/releases/download/v0.21.1217/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


Maintainer/contributor documentation required

As a maintainer/contributor I would like do find some detailed documentation how to get started with changes, in particular if it comes to frequent tasks:

When a new JDK version is released, either

As new major JDK release,
As an update to an existing JDK;

When the current version of a Linux distro (or other supported OS) is at the end of its support window, of if a new version comes up;
When a new OS is added, or an existing one will no longer be supported.

@gdams (and others), please add more frequent use case scenarios for maintenance.
@smlambert feel free to assign this to me, I already have some ideas.

Unfortunately the maintenance docs as demonstrated in todays community meeting do not (yet) render nicely on GitHub due to github/markup#1095


Using mount + find with a class selector in 3.x returns an extra element

Current behaviour
Using .find to locate a class on a mounted react element returns 1 extra element than expected: wrapper.find('.class').
class Icon extends React.Component {
  render(){
    return ()
  }
}

const wrapper = mount(<Icon className='whatever-name' />)
expect( wrapper.html() ).to.equal('')
expect( wrapper.find('.whatever-name').length ).to.eql(1)

wrapper.find('.whatever-name').length is equal to 2 though.
An mcve is here: https://github.com/deployable/issue-enzyme3-find-react15
Using .find with the selector span and span.whatever-name works as expected, as demonstrated in the mcve's additional test.   Using .find('.class') with shallow also works as expected.
Reading the migration guide alludes to this type of behaviour but I don't understand how it can apply to this specific case of finding a class that should only exist once.
Expected behaviour
wrapper.find('.class') returns the elements with that class applied
Your environment
node v8.9.4  on darwin
API

[ ] shallow
[x] mount
[ ] render

Version

library
version

Enzyme
3.3.0

React
15.6.2

jsdom
11.6.2

Adapter

[x] enzyme-adapter-react-16
[x] enzyme-adapter-react-15
[ ] enzyme-adapter-react-15.4
[ ] enzyme-adapter-react-14
[ ] enzyme-adapter-react-13
[ ] enzyme-adapter-react-helper
[ ] others ( )

This is expected behavior; it's finding both the Icon component and the rendered span. You can use hostNodes to filter the results down to only the host (DOM) nodes that match the query.
The docs and migration guide should probably be updated. Hope that helps!

Thanks, yeah not obvious at first glance but that explains it.
Which is shallow finding then? I was expecting it to be the same for a component.

shallow only finds the rendered html span

A shallow wrapper is what the element renders; a mount wrapper is the component itself, and is children are what it renders.

gotcha, thanks!
So using .hostNodes() at the end of any .find() for a css class selector when using mount to limit the results to only html nodes gets it working as it did in 2.x.
expect( wrapper.find('.whatever-name').hostNodes().length ).to.equal(1)

I'll just add a note that my first steps to debug this test after the upgrade to 3.x were to print each matching element and then print the.html() of each element. In both cases the results were exactly the same for the component and html node. It might be useful include the type, or subclass ReactWrapper for each.
wrapper.find('.whatever-name').map((el,i) => debug(i, el, el.html()))

  test:unit:component:Icon 0 ReactWrapper { length: 1 }  +2ms
  test:unit:component:Icon 1 ReactWrapper { length: 1 }  +2ms

It didn't occur to me that a css selector would match a component.  I see now that .debug() would have got me there.


delay project system init to avoid solution update race

I've been getting this error intermittently:
https://github.com/OmniSharp/omnisharp-roslyn/blob/8f3b6ea9915c4e692ca324a1e2e58e394a6cac75/src/OmniSharp.MSBuild/ProjectManager.cs#L375
I tracked it down to a race between TryApplyChanges calls.
Adding the project happens on a worker thread, and is queued on the main thread inside:
https://github.com/OmniSharp/omnisharp-roslyn/blob/8f3b6ea9915c4e692ca324a1e2e58e394a6cac75/src/OmniSharp.Host/WorkspaceInitializer.cs#L43
I believe AddProject can be called on a worker thread any time after this.
The other call is on the main thread via:
https://github.com/OmniSharp/omnisharp-roslyn/blob/8f3b6ea9915c4e692ca324a1e2e58e394a6cac75/src/OmniSharp.Host/WorkspaceInitializer.cs#L59
https://github.com/OmniSharp/omnisharp-roslyn/blob/8f3b6ea9915c4e692ca324a1e2e58e394a6cac75/src/OmniSharp.Host/WorkspaceInitializer.cs#L91
This change rearranges workspace init to avoid this particular race.  It doesn't seem like anything attempts to retry solution changes, so if there are other races it may be a more serious problem.

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

@JoeRobich @david-driscoll @mholo65 do you have any comments on this?

@JoeRobich @david-driscoll @mholo65 do you have any comments on this?

thanks!

thanks!


Add ability to append any params to the request

This is incredibly useful for us. Our use case is as follows:
Hitting our Fields (Paddocks) Api with this:
UserApi::Field.find(123)

(with some other transformation I've removed) yields this:
GET "/user_api/v1/fields/123"

which returns data attributes for that field (paddock).
Although, if we want paddock data attributes for a specific season of farming, e.g. 2015, then with this change, we can now run:
UserApi::Field.with_params(season_id: 456).find(123)

which yields this:
GET "/user_api/v1/fields/123?&season_id=456"

which will return us attributes for paddock 123 that are specific to season 456.
.with_params can be appended at any point to any scope e.g. find or all etc.
Thanks for reading.

Thanks for this feature! Could you change it to merge the additional params so you could potentially chain together more than one .with_params? The other scope like builders can be chained together.

Yep, great call @chingor13. All done. Builds are all green too.

:+1:

Cheers


connect oracle error

I connect to oracle find error
[2022-09-15T09:10:38Z ERROR r2d2] DPI Error: DPI-1047: Cannot locate a 64-bit Oracle Client library: "dlopen(libclntsh.dylib, 1): image not found". See https://oracle.github.io/odpi/doc/installation.html#macos for help
import connectorx as cx
url = f'oracle://xxx:xx@xxxx:1521/dx'
query = "select * from region"
cx.read_sql(url, query)

os: macos Bigsur
python:3.97
connector-x: 0.3.1a6

Dear @heyuqi1970, I had a similar issue. I installed the Oracle Client  and it worked fine then. Otherwise you can use oracledb, but it won't be as efficient I guess...

@djfrancesco
Thanks for your help！ As you suggested，it worked.

Hello!
Are you able to use oracledb thin mode driver with connector-x without installing the Oracle Client? Any suggestions are appreciated!
import connectorx as cx

ENGINE_PATH = "oracle+oracledb://username:password@host:post/service_name"
query = "select * from table"  # query string

cx.read_sql(ENGINE_PATH, query)

Getting this error:
[2023-11-01T02:17:30Z ERROR r2d2] DPI Error: DPI-1047: Cannot locate a 64-bit Oracle Client library:
"dlopen(libclntsh.dylib, 0x0001): tried: 'libclntsh.dylib' (no such file),
'/System/Volumes/Preboot/Cryptexes/OSlibclntsh.dylib' (no such file), '/usr/lib/libclntsh.dylib'
'(no such file, not in dyldcache), 'libclntsh.dylib' (no such file), '/usr/lib/libclntsh.dylib'
(no such file, not in dyld cache)". See https://oracle.github.io/odpi/doc/installation.html#macos for help


Allow Themes to feature Specified Background Image Files instead of Colors

Honestly, everything about this is amazing.
The only thing I can request is being able to add background Images to themes to override background colors. It's the only thing really missing from this. (Either that or have an option to default to Terminal BG)
Thanks so much for working on this project!

hi @ForeignExchangeZtudent, thanks for the kind words. Hope u enjoy using spotify-player.
I don't think adding background image to override background color is possible. The app needs an allocated space to render the image. If that space is the whole application's window, the rendered image will hide the display text and other things.
I think what you want is a dim background image, which should be handled by your terminal. For example, in iterm2, you can set the terminal's background image by "Preferences > Profiles > Window > Background Image"

Ah, that's unfortunate. I usually prefer themeing with Transparency in mind around my Terminal windows and considering the ease of themeing and switching themes. It just feels a bit less on the customizable side to not allow for transparency color code, at least if background-image is impossible.
But, eh it is whatever I guess.

Figured this one out, as well. No need for any additions! (Not that it was possible due to working in RGB Space (256colors))
Thanks again for this project and keeping minimalist spotify alive in the best way possible.


Drag abd Drop directives

This change will help to handle drag and drop events.
Example at http://plnkr.co/edit/yFTetlPuxCAZuHzPj9BE?p=preview

I signed it!

This might be a bit niche to live in core, have you considered releasing this as a standalone library?

I think this is not a bit nichem, rather it is very common to use drag and drop. But anyway I will publish it as standalone library.
Thanks

of course it's very common, but the requirements for different applications D&D behaviours can differ dramatically, as can the browser support and performance --- these things make it very hard to justify living in core. Thank you for publishing this externally =)


Segfault in Binder after running compiled query

Summary:
There are appears to be an issue with exception handling after a query has been compiled to native code. I've seen this on Ubuntu 18.04 and 20.04 both locally and on EC2. I cannot reproduce the issue on macOS.
Steps to reproduce:
I found this while benchmarking TPC-C that throws an expected exception in the Binder, but can reproduce it more succinctly.

Change this line to ExecutionMode::Compiled to force compilation to machine code rather than TPL interpretation of queries.
Build the tpl and terrier targets. The former is necessary to generate the bytecode file. We should add it as a proper dependency of terrier in the future because if you forget to build tpl first you get a segfault on the server.

matt@Matts-MBP ~ % psql -h <IP_ADDRESS> -p 15721 -d terrier
psql (12.3, server 9.5devel)
Type "help" for help.

terrier=# create table foo (id int);
CREATE TABLE
Time: 4.249 ms
terrier=# select bar from foo;  --throws exception just fine because no DML yet
ERROR:  binding failed
Time: 1.340 ms
terrier=# insert into foo values (1),(2),(3); --DML query that invoked and linked in LLVM
INSERT 0 3
Time: 299.403 ms
terrier=# select bar from foo; --segfault on throwing exception
server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
Time: 6842.192 ms (00:06.842)
!>

My suspicion is that LLVM links in incompatible exception handling code after compilation, either due to a version mismatch or some other issue. I tried changing from building terrier with GCC to the same version of clang that tpl uses to generate the bytecode handlers but it didn't help.

Initial impressions before I go back to cramming for a midterm.
Some very confused debugging later, and I'm pretty sure that the issue is on LLVM 8's end. This may or may not be fixed in newer versions.
LLVM seemingly creates an exception handling frame when you call into LLVM code. If you throw an exception and LLVM 8 ends up having to abort from a function--at least in our case--it will may not properly deregister its exception handling frame. Valgrind might be losing track here, or I may be missing something, but I believe (even though Valgrind cannot find a relevant "recent free") LLVM is also freeing the exception handling frame. So there could be some UAF-related corruption here, but it's hard to tell.
Regardless, the contents of the exception handling frame are no longer relevant to any executing code after the JITed code aborts, even though the frame is still registered. The next time an exception is thrown (in this case, it happens in schema.h:GetColumn) libunwind tries to traverse the exception handling frames. But the exception thrown by the JIT has the frames corrupted, and we end up segfaulting in libunwind.
Supporting this idea is that the issue isn't reproducible when using Apple's fork of LLVM and Clang, which is considerably more up to date.

So this is absolutely an LLVM issue. A known one, at that: http://llvm.1065342.n5.nabble.com/llvm-dev-New-ORC-v2-LLJIT-global-variables-tp130449p130629.html
I don't see any obvious workarounds besides patching LLVM or managing exception frames ourselves. Neither of which seem practical, trivial, or portable.
It is, in fact, a linker error. It's just not the trivial kind. RuntimeDyld (which is implemented differently for for MachO/MacOS binaries than it is for Linux/ELF binaries) has really poor exception handling frame support. It's completely broken on master, actually.
LLVM is ditching RuntimeDyld for JITLink, but they only JUST got preliminary elf support working in a dev branch. I wouldn't be surprised if we didn't see it until May. As of right now, we can only use it for MacOS, which doesn't have this problem anyway.

...and, fixed? https://github.com/gonzalezjo/terrier/commit/cbddc669cb7af85bb638fa1b0fd24d0270dd8f2b
Fairly anticlimactic solution if that works for others and doesn't introduce any new bugs.


Add Versioned API and Antctl for NetworkPolicyEvaluation (effective policy rule prediction)

Added antctl support for querying effective policy rule by networkpolicyevaluation
antctl query networkpolicyevaluation -S ns1/pod1 -D ns2/pod2
Added versioned API for NetworkPolicy evaluation POST call
curl -d "@<test json file>" -H "Content-Type: application/json" -X POST <k8s-apiserver>:8001/apis/controlplane.antrea.io/v1beta2/networkpolicyevaluation

Adds the above APIs and antctl queriers that returns the predicted effective NetworkPolicy rule, which affects traffic from ns1/pod1 to ns2/pod2. The solution picks the highest priority rule that satisfies the query.

Depends on #5989

@jianjuns @antoninbas do you have other comments?

@tnqn I took another quick look, LGTM

/test-all


Updated 'simdjson' to v0.8.2

Updates simdjson to v0.8.2
Changelog:
https://github.com/simdjson/simdjson/releases/tag/v0.8.2

Just waiting on the gsoap regression fix from PR #16270

/azp run

Thanks for the update!


User gets to blank page "Sample Services" after pressing the logo (bug)

Testing Environment:
Windows 10, Google Chrome 73.0.3683.86 (64bit), 15.6", 1920х1080
Steps to reproduce:

Navigate to http://rfai.singularitynet.io.s3-website-us-east-1.amazonaws.com/
Press SingularityNET logo
Observe the result

EXPECTED RESULT:
User gets to Home Page
ACTUAL RESULT:
User gets to blank page with such URL
http://rfai.singularitynet.io.s3-website-us-east-1.amazonaws.com/SampleServices
Please see the video below

Note:
Same behavior is actual for the case when user tries to "Add more funds", gets to "Account" page and then presses SingularityNET logo so it's important to fix this

Updated the link to SigularityNet Site.
Issue is fixed.

@ksridharbabuus we should take the user to the view requests page and not the website

I will suggest to take it to the web site rather than request list. That's
the std behaviour for most of the sites. Any way we have link to the
request list page.
On Tue 16 Apr, 2019, 13:48 raamb<EMAIL_ADDRESS>wrote:

@ksridharbabuus https://github.com/ksridharbabuus we should take the
user to the view requests page and not the website
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/singnet/snet-rfai-dapp/issues/20#issuecomment-483560046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHFW3PH_soLH7EfZtoWpbnUVzYtGoLqAks5vhYdWgaJpZM4ceCVf
.

Going with the Std Approach by taking to main site.

@ksridharbabuus what do you think about changing the logo link to the RFAI homepage and maybe add a link on the menu to the foundation's homepage?

Better to keep it to the main site and we can look at some other place to
it to Foundation Page once we have it.
On Thu, Apr 25, 2019 at 1:39 AM smbss<EMAIL_ADDRESS>wrote:

@ksridharbabuus https://github.com/ksridharbabuus what do you think
about changing the logo link to the RFAI homepage and maybe add a link on
the menu to the foundation's homepage?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/singnet/snet-rfai-dapp/issues/20#issuecomment-486406104,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYVNXCIN3Q3XM4YJURBTCTPSC47XANCNFSM4HDYEVPQ
.

--
Thanks,
Sri
Blog: http://sridharbabuk.blogspot.com/

Discussed with @ksridharbabuus we will have the logo take us to the main page of the DApp itself

Completed as per the request. Thanks!


[FLINK-9941][ScalaAPI] Flush in ScalaCsvOutputFormat before close

What is the purpose of the change
This pull request update scala api ScalaCsvOutputFormat to add flush method before close to avoid inconsistent result with java CsvOutputFormat when auto flush not call in some io streams.
Brief change log
Add flush method before close method in ScalaCsvOutputFormat for scala API.
Verifying this change
Add ScalaCsvOutputFormatTest and test passed.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no/ don't know)
The runtime per-record code paths (performance sensitive): (yes /  no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes /  no / don't know)
The S3 file system connector: (yes /  no / don't know)

Documentation

Does this pull request introduce a new feature? (yes /  no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot attention @yanghua @buptljy

lgtm.

@flinkbot approve until architecture

@flinkbot run travis

@flinkbot run travis

@flinkbot approve-until architecture

Looks good, merging this.


WIP: [AMQ-8320] Add JMS 2.0 JMSProducer deliveryDelay support

[ ] Improve Message object reuse
[ ] Add unit test to confirm

ref: #982

Seems like the same code as the old PR, so same comment from before:

Since message objects can be reused/resent, and might already have an existing value for JMSDeliveryTime, it should always be setting the JMSDeliveryTime value on send even if there isnt a delay, to ensure the JMSDeliveryTime value on the message after send reflects behaviour of that send and not some previous send or receive.
That doesnt mean it has to transit a delivery time on the wire...ideally it wouldnt if there is no delay being requested for this send...just that after send the local message object should report the delivery time for that send. Elsewhere I added an internal message method to set the value and note whether it is for transmission.
It doesnt feel like it should be setting a message property at all, only a header. I don't expect the TCK tests which check additional properties arent being added to the messages are using delivery-delay at the time..but they could. I know the older 'message property extension' scheduling stuff uses one, but its not clear to me this needs to. They could just be treated as separate mechanisms, which they kind of are already as you have to choose to respect the new value on the producer or the old one on the message. Theres no reason the broker couldnt do the same, and this new mechanism essentially ignore that old prop.

It also now occurs to me it may not handle foreign providers Message properly since it seemingly doesnt call setJMSDeliveryTime at all on send (unless thats being done elsewhere already...though doesnt seem obvious it could know the value to use).
Although the PR title makes it clear that it does, it also seems weird this change only covers the JMSProducer API related code, and misses out the MessageProducer related API, when delivery delay support applies equally to both (and the underlying send code is used for both).


How to add custom license that cannot be generated?

AckGen is unable to generate the License details for https://github.com/cozality/Thrift-Swift package. I guess the reason is because it does not have a LICENSE file in it, but rather the license is in readme and in comments of Package.swift. How can I manually add the license details for this package if AckGen cannot pull it from the SPM resolve file.

Hello @alizainc!
Thank you for reaching out!
You're right. The reason is that the package doesn't contain a LICENSE file at the root.
Aside from the adding the license manually, I would actually recommend that you file an issue or create a PR for that package to add the license file.
Btw, I think you linked a fork of Thrift-Swift. The original package seems to be here: https://github.com/apocolipse/Thrift-Swift
There are several method to do it manually, depending on how you use AckGen.
You could

add the information as another entry to the Acknowledgements.plist after it's created by AckGen.

use the otherAcknowledgements parameter of AcknowledgementsList

AcknowledgementsList(
    otherAcknowledgements: [
        .init(
            title: "Thrift-Swift",
            license: "Licensed to the Apache Software Foundation (ASF) under..."
        )
    ]
)

Please let me know if this doesn't help!
Cheers,
Martin

To solve this for font awesome, I create my own dummy package and added their policy etc.

Thank you @MartinP7r for the quick response. I have updated our project to use the original package by apocolipse, but it seems like even that package does not have a LICENSE file. I have create an issue to the project to create a LICENSE file, instead of adding the LICENSE in readme.
For the first solution you provided, if I just add another entry in the Acknowledgements.plist wouldn't it be overwritten when we re-run the build for the package? Or will it be able to somehow handle that and keep the extra added entry? Thanks.

For the first solution you provided, if I just add another entry in the Acknowledgements.plist wouldn't it be overwritten when we re-run the build for the package? Or will it be able to somehow handle that and keep the extra added entry?

You're right. This would be overwritten every time you run ackgen. For example in your run script, if you followed the normal installation instructions. If you have the plist generated automatically, it would make sense to add other licenses also automatically.
The 2. option (adding an Acknowledgement manually in code is maybe easiest to implement. Especially if you don't have many licenses that need adding manually.
But for completeness, one approach you could take is to have the additional license's information in a separate plist and merge that after running swift run ackgen in your build script (PlistBuddy should be able to do that).

Create a separate plist (e.g. OtherLicense.plist) with the same content format
Add merge command to your run script after swift run ackgen

I haven't tried it myself, but something like below might work (would need to set correct paths)
DIR=$PROJECT_TEMP_DIR/../../../SourcePackages/checkouts/AckGen
if [ -d "$DIR" ]; then
  cd $DIR
  SDKROOT=(xcrun --sdk macosx --show-sdk-path)
  swift run ackgen
  /usr/libexec/PlistBuddy -x -c "Merge /path/to/OtherLicense.plist" /path/to/Acknowledgements.plist
fi

@alizainc let me close this for now, but feel free to reopen if you have further questions.


Type guard failures that become an intersection type

TypeScript Version:  2.0.0
Code
class A<T> {
  private _: T;
}
class B<T> {
  private _: T;
}
function f() {
  var o: A<void> | B<void> = new B<void>();
  if (o instanceof A) return o; // B<void> & A<any>, should be A<void>
}

Expected behavior:
A type of o narrowed by type guard is A<void>.
Actual behavior:
A type of o narrowed by type guard is B<void> & A<any>.

I'd say this follows from #8911/#9016.
o is narrowed to B<void> when you assign new B<void> to o. Then the compiler sees the o instanceof A as further narrowing and comes up with the intersection type.
I suspect the A & B type, which seems impossible in terms runtime behaviour, seems fine to the compiler which is just concerned about the structural intersection of the A and B types.

Note this comment in particular: https://github.com/Microsoft/TypeScript/issues/8911#issuecomment-224672366

then options here are either `never

This problem caused by declared type internal overwriting. This behavior should be a bug because following code works correctly.
class A<T> {
  private _: T;
}
class B<T> {
  private _: T;
}
function f() {
  var o: A<void> | B<void>;
  if (o instanceof A) return o; // A<void>
}

I am not sure i understand what you meant there. but the important difference between the two samples is the assignment...
var o: A<void> | B<void> = new B<void>();

// here o can only be `B<void>` and nothing else. no assignments has happened to o since it got `new B<void>()`

if (o instanceof A) return o;  /// now how can we narrow B into A?

@mhegazy why do you think "working as intended" about that difference? The two samples should be a same narrowed type by type guard.

@falsandtru assignments cause narrowing as per #8010. Then subsequent narrowing to an unrelated type   narrows to the intersection of the two narrowed types as per #9031. According to those two rules, your example is indeed working as intended.
Your sample is a bit like the following, which produces the same intersection narrowed type:
class A<T> {
  private _: T;
}
class B<T> {
  private _: T;
}
function f() {
  var o: A<void> | B<void>;
  if (o instanceof B) {
      if (o instanceof A) return o; // B<void> & A<any>, should be A<void>
  }
}

I understood that behavior, but I'm not sure that which is a spec, or a bug.

Why would it be a bug? Control flow analysis can infer:

That o is a B throughout the body of f, since a B is assigned to o and there are no subsequent assignments that could change it to something else.
That the only way we could reach the guarded return o statement is if o is an A. And since o is already known to be a B, then o must be an A & B in that guarded clause.

Merging #9861.
class A<T> {
  private _: T;
}
class B<T> {
  private _: T;
}
function f() {
  var o: A<void> | B<void> = new B<void>();
  if (!(o instanceof B)) return o; // B<void>, should be A<void>
  o; // B<any>, should be B<boid>
}

Merging #9862.
class A<T> {
  private _: T;
}
class B<T> {
  private _: T;
}
function f() {
  var o: A<void> | B<void> = new A<void>();
  o instanceof A || o instanceof B;
  o; // A<any>, should be A<void> | B<void>
}

the first case is again because of the initialization. there is no way for o to be any thing but B. so checking !(o instanceof B) is really not meaningful here. so you have B, you take out B, what are you left with..

I see, I think we can close this issue. However, a compiler option for detection of this assignment type mismatch is helpful to avoid these confusing. A declared type shouldn't be wider than an assigned type in these CFA behaviors.

A declared type shouldn't be wider than an assigned type

A wider declared type allows for re-assignment later on:
let a: string | number = 'foo';
a; // a is narrowed to string here
a = 42;
a; // a is narrowed to number here

It case seems an anti-pattern.

@falsandtru why an anti-pattern?

It should be
const a: string = 'foo';
const b: number = 42;

Also see #9886.

There's plenty of discussion about this in #8513. Note the realistic motivating example involves modelling an Optional<T> type as a union of Some<T> and None, and some control flow that initialises an Optional to None and then possibly reassigns it with a Some value.
I don't think you can simply say

It should be
const a: string = 'foo';
const b: number = 42;

in light of legitimate examples where people are trying to model runtime-valid code using TypeScript, where union variables with initializers occur naturally as a result.

My example is based on immutable programing. So I suggested as optional in #9886.

OK, then if you make the variable in your first example immutable:
function f() {
  const o: A<void> | B<void> = new B<void>();
  if (o instanceof A) return o; // B<void> & A<any>, should be A<void>
}

...then it seems an even stronger case for the current compiler behaviour being correct, doesn't it? Or have I misunderstood what you mean by immutable?

It example is a bad case. So I said "But this operation is a mistake, should be removed." in #9886. My suggestion is useful for finding mistakes like this.


Confirm quit

Accidentally hitting esc/q and losing the flow of what you are doing isn't the end of the world, but atm it seems a little too easy to accidentally do.
As it stands those keybinds insta-quit the dashboard, even in circumstances where instincts from other UIs  & general expectations suggest it shouldn't.
Most notably, when you have hit ? and have the 'help' (cheatsheet?) open, it is quite easy to absent mindedly expect at least esc to just close that, not exit the entire program.
I'd propose hitting those keys when you most recently opened up a kinda sub-window like that, it should close those in reverse order before attempting to quit the whole dashboard.
I think perhaps a 'really quit?' prompt would be a nice QoL improvement. Imo having quick and easy options to confirm the quit (e.g. hitting esc or q again, hitting y, hitting return, etc.)  should mean the nag is outweighed by avoiding the flow-breaking drop back to the terminal.

There is now the confirmQuit setting, but it should default to true so you don't have to dig around to get this expected behavior.
Also, the app still quits if you hit escape again (as per the prompt: "Really quit? (press q/esc again to quit)").
I think the prompt should be a y/N thing, and escape is considered an N.

I had a quick try at fixing that, but it looks like you can only bind keys once (or rather, when hitting a key, it seems to match the first binding which might have other keys combined o be named awkwardly in the new context).

I think the prompt should be a y/N thing, and escape is considered an N.

Hm, I suppose it could be considered equally 'intuitive' behaviour either way, though I think on reflection I'm more inclined to agree with you that Esc has a strong connotation of 'cancel' rather than 'confirm'.
The prompt probably should be y/n, though I do still think a 'double tap' of the q key should also work, for the sake of ergonomics.
Actually, to really drill down into the UX design on something like this, it would probably best be presented as a modal confirmation popup with 'yes/no' buttons, with (default?) bindings y & q for yes, n & Esc for no, and ofc. enter/return for the selected option (heck, even mouse support is an option then, for those Osu players outlier users who are big mouse fans).

I remembered localisation is a thing, so there's also that for even something as simple seeming as a y/n prompt....
'Y/N has long transcended the yes/no origins in computing' is probably a valid counter for those specific keys, but, arbitrary named virtual keys for such things is worth considering is strong localisation is desirable...


Fixed failing compile

This addresses both issues #1 and #2
However,  I wonder why the tests don't use the golang testing framework (I have to use go run ./tests/tmsp/main.go to check the code)?  I would happily port if if that is desired. (Probably a separate pull request).

Already fixed in master


list-like methods for seashore.executor._PreparedCommand?

Specifically I'm trying to do docker-compose-in-docker:
    docker run -v "$(pwd)":"$(pwd)" \
             -v /var/run/docker.sock:/var/run/docker.sock \
             -e COMPOSE_PROJECT_NAME=$(basename "$(pwd)") \
             --workdir="$(pwd)" \
             -ti --rm \
             dduportal/docker-compose:latest --help

I guess I'll use command() for now and do a raw list of strings.  It might be nice if there was some way to still leverage the executor.
executor.command(executor.docker.run(compose_image, volume=[], env={}, workdir='...')._cmd + ['--help']) is a convenient escape hatch that involves less manual intervention than doing the whole thing from scratch; not sure if this is overall a good API or not

A cleaner version of that API that might work well:
executor.docker.run(...).extend(['--help'])
Add extend() to _PreparedCommand which just takes a list of strings and adds it to the end.  Maybe in general _PreparedCommand could have some list-like methods?  (Item assignment, insert, pop?)

Or maybe tuple is the better analogy than list, since the command should be immutable.

Another possibility: instead of build list or tuple-like the API is the same as the root executor:
executor.command(['docker', 'run', 'foo']) --> ['docker', 'run', 'foo']
executor.docker.run.command(['foo']) -> ['docker', 'run', 'foo']


CT ultra lite config sample

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tested with fresh CT deployment.

Seems you deleted your source branch :-(.  PR needs a couple of additional tweaks - I'll open a new parallel PR to replace this one.


Release tags mess

Description
There is a big confusion with the release tags:
Here is what the various resources says is the latest tag
https://api.github.com/repos/dotnet/core/tags => "name": "v8.0.0-rc.1",
https://api.github.com/repos/dotnet/sdk/tags => "name": "v8.0.100-rc.1.23462.41",
https://api.github.com/repos/dotnet/aspnetcore/tags => "name": "v8.0.0-rc.1.23421.29",
https://api.github.com/repos/dotnet/installer/tags => "name": "v8.0.100-rc.1.23463.5",
https://api.github.com/repos/dotnet/runtime/tags => "name": "v8.0.0-rc.1.23419.4",
https://api.github.com/repos/dotnet/dotnet/tags => "name": "v8.0.100-preview.3.23178.7",
https://github.com/dotnet/dotnet/releases => v8.0.0-rc.1.23419.4
https://github.com/dotnet/core/blob/main/release-notes/8.0/preview/8.0.0-rc.1.md => .NET SDK 8.0.100-rc.1.23463.5
.\dotnet-install.ps1 -Quality preview -Channel 8.0 -DryRun => 8.0.100-rc.1.23455.8

Hi @davhdavh - Each repo has its own set of tags. What particular problem are you trying to solve?


ostree-based artifacts are not supported on CentOS Stream

build a RHEL for Edge Installer and
build ostree image
In My env, centos8 stream x86 and aarch64
$ sudo composer-cli compose
ami
openstack
qcow2
tar
It has not rhel-edge-container and fedora-iot-commit image types, How I config?
the version are:
$ rpm -qa | grep osbuild
osbuild-27.2-1.el8.noarch
osbuild-ostree-27.2-1.el8.noarch
osbuild-composer-core-28.4-1.el8.0.1.aarch64
osbuild-selinux-27.2-1.el8.noarch
osbuild-composer-worker-28.4-1.el8.0.1.aarch64
osbuild-composer-28.4-1.el8.0.1.aarch64
python3-osbuild-27.2-1.el8.noarch

Hi, building ostree-based artifacts isn't currently supported on CentOS Stream. We do plan to add very soon though. If you want to try it, you can use Fedora or the free RHEL Developer Subscription (you may want to use 8.4 Beta, it has better support for building ostree-based artifacts).

Oh, thanks. Have some roadmap for support  CentOS Stream?

I'm not able to come up with any estimates but we're already working on the groundwork for ostree support on CS, see https://github.com/osbuild/osbuild-composer/pull/1391 and https://github.com/osbuild/osbuild-composer/pull/1351


company-go can not complete golang third party package ?

like fmt, string  work well, but glog, mux ... can not complete.

Gocode is no longer maintained, please consider switching to https://github.com/mdempsky/gocode.
It could complete third party packages, however, due to recent changes in Go packages architecture it no longer works for recent Go versions (1.10 maybe and 1.11+ for sure).

OK, I got it.


Update lazy.nvim instruction in README.md

First of all, thank you for such an amazing project! I want to contribute to the README.md file.
It's usual to have a listing of just a Lua table item as an install snippet. Because many people use a rather structural approach to the configuration of lazy.nvim. So, the require is already called by them in a separate file.
Also, I removed the config because the official documentation of lazy.nvim suggests using opts instead of it. It will do the same. It will just call require('kulala').setup({}) but with less code.
I've tested the change and it works.

Thanks for the great addition!


Bring back Gulp with refactor

build-test is removed because it makes piping harder (I didn't find a way to pipe a task's output to another).
This still contains copy pasted part, so beware typos.
I'm planning to do error handling refactor too, but feel free to merge this before that and I will open another PR to do that.

I'll have to run it locally to see if this takes care of the issues I was encountering with the source mapping for coverage.
Will be traveling for ~2wks so I'll be slow to review for a bit.

Sourcemaps actually seem to be working this time in the coverage report, bravo!
I won't miss build-test; building the tests separately seems somewhat useless.


CI: Bump ansys actions version

As title say.
We've been left behind with ansys/actions due to various reasons - the biggest one being the artifact compatibility issue.
Now that all the issues that slowed us down are solved, we can update our CICD !
Notable changes:

To be compatible with ansys/actions/doc-build I'm removing the name of the pdf in conf.py. This should lead to the creation of a pdf named pyaedt.pdf. In the process we lose the version in the pdf file name but this is a requirement for the doc-build action. I don't think this is a problem though.
Meilisearch is being deprecated so I dropped the indexing jobs. I'll update our documentation to remove meilisearch and leverage static search in another PR.

In the process we lose the version in the pdf file name but this is a requirement for the doc-build action. I don't think this is a problem though.
This is absolutely fine. Thanks @SMoraisAnsys


Optimizations and improvements to Trello to Asana importer

This pull request introduces several optimizations and improvements to the Trello to Asana importer tool:
Optimizations:

Simplified and inlined some utility functions for better performance
Moved shared functionality (like JSON parsing) to a central Importer object for better organization
Added more robust error handling to provide better error messages when issues occur during import

Improvements:

Added KDoc comments to improve the code documentation
Ensured naming conventions are consistent throughout the codebase
Made data classes immutable where possible to improve thread-safety

These changes should make the importer more efficient, maintainable, and user-friendly without changing the core functionality. Please review the changes and let me know if you have any feedback or questions.

This PR is clearly fully LLM-generated, and most of the changes don't make a whole lot of sense (in fact, they even break the build).


Adding arduino uno serial support

I'm a beginner in arduino, but since I had an arduino uno, which had no wifi, I decided to try a serial approach. Related to #52
Changes

Altered the ws2812_controller_esp8266.ino code in arduino_serial.ino to use a buffer to store the serial data instead of udp data.
After experimentation, I noticed that the buffer needs at least 16 bytes to pass the ledstrand test and can hold maximum of 64 bytes.
Added serial support in led.py. Just need to match your serial port and baudrate
Added arduino_serial to CONFIG.DEVICES
I don't know how the FPS counter would work in the serial implementation so I left that out.

Problem
I think the serial communication is way too slow for the visualization to work properly. The strip just seemingly lights up randomly. I'm guessing this is because every udp packet can send a lot more information about more pixels at faster rate than serial?
However if someone can actually make this work, that would be cool. Just wanted to share my investigation @joeybab3  :)

Sorry for the super late response, I'm glad to see a PR for this as I know it's been a long-requested feature!


NVM use x.x.x 32 Error

Hi - Running into a small error on a Windows 7 machine.
Can install any version of node but when it comes to creating the link from ..\nodejs with nvm use 6.3.1 32 to the version of node you wish to use it fails with a fork/exec error from elevate.cmd. See below:

Any idea how to fix it? Have tried manually creating the link with:
C:\Users\...\AppData\Roaming\nvm\elevate.cmd cmd /C mklink /D "C:\Program Files\nodejs" C:\Users\...\AppData\Roaming\nvm\v6.3.1 but that fails too.

Is this from a fresh install (i.e. the first time the command prompt was opened)?

Hi @coreybutler sorry for the delay, this was post reboot after a fresh install.

@rustyb - dumb question.... C:\.....\elevate.cmd actually exists, right? I'm wondering if something got botched in the install. Perhaps the file never got copied to the proper location. If it's not there, you'll need the elevate.cmd and elevate.vbs from here.

They definitely exist, but will try copy them over from the repo directly to see if that has any effect on it.

@rustyb - Are there any special characters or spaces in your username (i.e. the red part of your image)?

Seems I had a similar problem on Win 10 x64 with nvm 1.1.1: My user home contains a space resulting in an error when running nvm use. The fix was to change the root path in settings.txt from

C:\Users\User Name\AppData\Roaming\nvm

to

C:\Users\USERNA~1\AppData\Roaming\nvm

I think found the solution : I had the same problem on my colleague's computer (Win10 x64 with nvm 1.1.1). His name is Léo so nvm was broken because of the special character "é" in his username.
I converted the settings.txt file to UTF8 (without BOM) with notepad++ and it solved the problem ! 😄
Maybe it would also solve the space issue...

Hum I must actually go back and check that i'm 99% sure there actually was a space!

Hi, maybe the problem is because windows username is using space  and special character.
To fix:

You change root path which doesn't any space using nvm root your_path and
copy file elevate.cmd and elevate.vbs ( download it from here ).
After that install again your node version using nvm install 6.9.1 ( whatever version  do you want)
Last, type nvm use 6.9.1 64 (if your windows 64 bit)

I ended up just uninstalling everything with a fresh start. Then I used the installer and threw it in a path at the root of my drive for both nvm and nodejs.

spaces and encodings are supported in https://github.com/coreybutler/nvm-windows/releases/tag/1.1.8


Issue triying transcoding h265 to h254

Hi.
I need to transcode the video from my camera. I'm using the next config but didnt work
streams:
  camera_1:
  - rtsp://XXX.XXX.XXXX.XXXX:554/stream1
  - ffmpeg:camera_1=#video=h264#audio=aac#hardware=vaapi

If I take out the "video" parameter it works but go2rtc stream in h265, I need it in h264...
streams:
  camera_1:
  - rtsp://XXX.XXX.XXXX.XXXX:554/stream1
  - ffmpeg:camera_1=#audio=aac#hardware=vaapi

Any suggestions?

I can see unnecessary = after stream name

Thanks for that... But I still having the issue... I updated the config file...
streams:
 camera_1:
 - rtsp://XXX.XXX.XXXX.XXXX:554/stream1
 - ffmpeg:camera_1#video=h264#audio=aac

And nothing...
Could be the camera??? or my CPU that dont support h254?
here the ffprobe of the camera:
ffprobe version 4.4.2-0ubuntu<IP_ADDRESS> Copyright (c) 2007-2021 the FFmpeg developers
  built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)
  configuration: --prefix=/usr --extra-version=0ubuntu<IP_ADDRESS> --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  libavutil      56. 70.100 / 56. 70.100
  libavcodec     58.134.100 / 58.134.100
  libavformat    58. 76.100 / 58. 76.100
  libavdevice    58. 13.100 / 58. 13.100
  libavfilter     7.110.100 /  7.110.100
  libswscale      5.  9.100 /  5.  9.100
  libswresample   3.  9.100 /  3.  9.100
  libpostproc    55.  9.100 / 55.  9.100
Input #0, rtsp, from 'rtsp://XXX.XXX.XXX.XXX:554/stream1':
  Metadata:
    title           : HTMS
    comment         : stream1
  Duration: N/A, start: 0.015625, bitrate: N/A
  Stream #0:0: Video: hevc (Main), yuv420p(tv), 2560x1440, 25 fps, 25 tbr, 90k tbn, 90k tbc
  Stream #0:1: Audio: pcm_mulaw, 8000 Hz, 1 channels, s16, 64 kb/s

And here some errors on the go2rtc logs that call my atenttion...
2023-06-20 15:27:19.802684749  15:27:19.802 DBG [webrtc] new consumer url=camera_1
2023-06-20 15:27:19.841231299  15:27:19.840 DBG [streams] probe producer url=rtsp://XXX.XXX.XXX.XXX:554/stream1
2023-06-20 15:27:19.858864777  15:27:19.858 DBG [streams] probe producer url=ffmpeg:camera_1#audio=aac#video=h264
2023-06-20 15:27:19.858881688  15:27:19.858 DBG [exec] run url="exec:ffmpeg -hide_banner -v error -fflags nobuffer -flags low_delay -timeout 5000000 -user_agent go2rtc/ffmpeg -rtsp_transport tcp -i rtsp://localhost:8554/camera_1?video&audio -c:v libx264 -g 50 -profile:v high -level:v 4.1 -preset:v superfast -tune:v zerolatency -c:a aac -user_agent ffmpeg/go2rtc -rtsp_transport tcp -f rtsp rtsp://localhost:8554/49b1c20bdcc3a0e037ad577dba25c468"
2023-06-20 15:27:19.884125693  15:27:19.883 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:27:19.891065422  15:27:19.890 DBG [streams] start producer url=rtsp://XXX.XXX.XXX.XXX:554/stream1
2023-06-20 15:27:20.860426211  [hevc @ 0x56322131cf40] Could not find ref with POC 21
2023-06-20 15:27:20.966462643  15:27:20.966 DBG [exec] run launch=1.107934865s
2023-06-20 15:27:20.967138005  15:27:20.966 DBG [streams] start producer url=ffmpeg:camera_1#audio=aac#video=h264
2023-06-20 15:27:24.798987556  15:27:24.798 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:27:29.922817609  15:27:29.922 DBG [rtsp] handle=read tcp <IP_ADDRESS>:8554-><IP_ADDRESS>:39776: read: connection reset by peer
2023-06-20 15:27:29.922826196  15:27:29.922 DBG [rtsp] disconnect stream=camera_1
2023-06-20 15:27:34.936037247  15:27:34.935 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:27:40.091295628  15:27:40.091 DBG [rtsp] handle=read tcp <IP_ADDRESS>:8554-><IP_ADDRESS>:32856: read: connection reset by peer
2023-06-20 15:27:40.091994025  15:27:40.091 DBG [rtsp] disconnect stream=camera_1
2023-06-20 15:27:44.988947317  15:27:44.988 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:27:52.708233655  15:27:52.708 DBG [rtsp] handle=read tcp <IP_ADDRESS>:8554-><IP_ADDRESS>:52616: read: connection reset by peer
2023-06-20 15:27:55.147523775  15:27:55.147 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:27:55.920202352  15:27:55.920 DBG [rtsp] disconnect stream=camera_1
2023-06-20 15:27:59.737072567  15:27:59.736 DBG [rtsp] handle=read tcp <IP_ADDRESS>:8554-><IP_ADDRESS>:42276: read: connection reset by peer
2023-06-20 15:28:05.207422391  15:28:05.205 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:28:05.559211593  15:28:05.558 DBG [rtsp] disconnect stream=camera_1
2023-06-20 15:28:12.041848078  15:28:12.041 DBG [rtsp] handle=read tcp <IP_ADDRESS>:8554-><IP_ADDRESS>:48426: read: connection reset by peer
2023-06-20 15:28:15.219800942  15:28:15.219 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:28:17.023612962  15:28:17.021 DBG [rtsp] disconnect stream=camera_1
2023-06-20 15:28:23.393765110  15:28:23.393 DBG [rtsp] handle=read tcp <IP_ADDRESS>:8554-><IP_ADDRESS>:44060: read: connection reset by peer
2023-06-20 15:28:25.359818011  15:28:25.359 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:28:29.382825468  15:28:29.381 DBG [rtsp] disconnect stream=camera_1
2023-06-20 15:28:36.008776249  15:28:36.008 DBG [rtsp] handle=read tcp <IP_ADDRESS>:8554-><IP_ADDRESS>:45682: read: connection reset by peer
2023-06-20 15:28:41.028783656  15:28:41.028 WRN [streams] json locked
2023-06-20 15:28:41.737260055  15:28:41.735 DBG [rtsp] disconnect stream=camera_1
2023-06-20 15:28:45.403555234  15:28:45.403 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:28:54.209169413  15:28:54.208 DBG [rtsp] handle=read tcp <IP_ADDRESS>:8554-><IP_ADDRESS>:57494: read: connection reset by peer
2023-06-20 15:28:55.498971591  15:28:55.498 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:29:01.371432545  15:29:01.371 DBG [rtsp] disconnect stream=camera_1
2023-06-20 15:29:01.371557626  15:29:01.371 WRN github.com/AlexxIT/go2rtc/cmd/rtsp/rtsp.go:221 > error=EOF
2023-06-20 15:29:05.533994528  15:29:05.533 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:29:10.917607259  15:29:10.917 WRN github.com/AlexxIT/go2rtc/cmd/rtsp/rtsp.go:221 > error=EOF
2023-06-20 15:29:15.557168854  15:29:15.556 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:29:20.991782405  15:29:20.991 WRN github.com/AlexxIT/go2rtc/cmd/rtsp/rtsp.go:221 > error=EOF
2023-06-20 15:29:25.576335137  15:29:25.576 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:29:39.620224237  15:29:39.620 DBG [rtsp] handle=EOF
2023-06-20 15:29:40.291300236  15:29:40.291 DBG [rtsp] disconnect stream=camera_1
2023-06-20 15:29:45.637484947  15:29:45.637 DBG [rtsp] new consumer stream=camera_1
2023-06-20 15:29:59.729986447  15:29:59.729 DBG [rtsp] handle=EOF
2023-06-20 15:30:05.153470827  15:30:05.153 DBG [rtsp] disconnect stream=camera_1

Any CPU should support H265 because you using hardware transcoding.
What about if you try to get RTSP from go2rtc via VLC. Can you see something?

 Maybe it has buggy H265 stream. Try to use ffmpeg source for this source.

I'm using a chinese camera from Aliexpress branded by Asecam.
I Tested the camera with VLC via RTSP and the main source in H265 and looks very smooth...
How slould I set the config to test it with ffmpeg? something like this?
streams:
   camera_1_h265:
      rotate: ffmpeg:rtsp://{ip-camera}:554/stream1#video=h264#rotate=90

Another question, could the resolution affect something? because in general the cctv cameras come in 1 or 2 megapixeles but mine are in 8mp.

Noname Chinese cameras often has buggy RTSP realisations. VLC and FFmpeg can handle some kind buggy streams.

Please let me know if the problem is relevant


use finishEvent instead of setting pubkey/id/sig separately

We can use the finishEvent function to calculate and set pubkey/id/sig all at once.
I removed getSignedEvent entirely since it seems unnecessary at all.
(including validation part: validateEvent is already applied in finishEvent,
and if finishEvent is implemented correctly, verifySignature applied to its result should always return true)

Looks good to me!


Add support for nested objects (in schema or otherwise)

Here is my code:
<template name="myForm">
    {{#defaultFormBlock schema=schema action=action data=data}}
        {{> myInput field='field1'}}
        {{> myInput field='nested.field2'}}
        <button type="submit" disabled="{{#if context.invalidCount}}disabled{{/if}}">Submit</button>
    {{/defaultFormBlock}}
</template>

schema: function ()
	{
	return new SimpleSchema(
		{
		field1: { type: String, max: 3 },
		nested: { type: Object },
		'nested.field2': { type: String, max: 3 }
		});
	},

data: function()
	{
	return { field1: '111', nested: { field2: '222' } };
	},

First issue is that data does not initialize nested.field2.
Second issue is that nested.field2 input is validated erratically: the latest error message seems to remain even if input is ok, until a new error is detected and replace the previous one.

This makes sense. I'll have to add this functionality.

I just ran into the same issue. May I ask, if you already have an estimate, by when this could be fixed?

I can probably do end of week on this. Thanks!

Made progress on this and will publish the changes once I finish more testing.

I tested this a bunch and it seems to be working. Please let me know how it goes for you. Thanks!

I will test this today.

It works like a charm, thanks a lot!

Just tested it - works flawless in my app. Thank you very much!


(under review) feature/lcp

WIP
This PR contains many changes. There is a breakdown in the comments below (scroll down pass the auto-generated code comments).

Android
https://github.com/readium/SDKLauncher-Android/compare/develop...feature/lcp
Adopt changes in the following build files (but remove LCP-specific bits):
SDKLauncher-Android/app/build.gradle
SDKLauncher-Android/app/build_epubReadingSystem.gradle
SDKLauncher-Android/app/build_experimental.gradle
SDKLauncher-Android/build.gradle
SDKLauncher-Android/gradle/wrapper/gradle-wrapper.properties
SDKLauncher-Android/project.properties

iOS
https://github.com/readium/SDKLauncher-iOS/compare/develop...feature/lcp
No change required.

OSX
https://github.com/readium/SDKLauncher-OSX/compare/develop...feature/lcp
No change required, but this code diff is worth back-porting into the develop branch (fixes originally brought-in / inspired from iOS):
LauncherOSX/CocoaHTTPServer/Core/HTTPConnection.m
LauncherOSX/CocoaHTTPServer/Core/Mime/MultipartFormDataParser.m
LauncherOSX/CocoaHTTPServer/Core/Responses/HTTPFileResponse.m
LauncherOSX/LOXWebViewController.mm
LauncherOSX/PackageResourceServer.mm

libXML pointer management
See: https://github.com/readium/readium-sdk/pull/190#commitcomment-19606152
Commits (in this feature/lcp branch):
Adopted memory leaks fixes:
https://github.com/readium/readium-sdk/commit/efc71c244e5969de979589732f795967377d0da3
Adopted "node wrapper" changes, albeit behind a deactivated preprocessor directive (condition):
https://github.com/readium/readium-sdk/commit/a33c979e01d3bc7fbbfb9235e54a42a3110146d1

New pre-processor directive to exclude writable zip archive functionality (not used in any apps we know of): ENABLE_ZIP_ARCHIVE_WRITER

New pre-processor directive to allow in-memory document parsing (libxml): ENABLE_XML_READ_DOC_MEMORY
(disabled by default)

New pre-processor directive to enable std::future (and friends, async promises / function returns): FUTURE_ENABLED
(disabled by default)

Successfully tested with SDKLauncher-Android on the develop branch.

Successfully tested with SDKLauncher-OSX on the develop branch.

Successfully tested with SDKLauncher-iOS on the develop branch.


Candidate list

Clean up backend, use store pattern effectively, and add some UI signposts for detect and select screen.

How we doing with this PR? :) What are the next steps here?

I still need to fix the mysteriously failing JS tests.

:bow:


TRAMP broken on OS X

May be broken in general.

This is caused by tramp-backup-directory-alist being set to (".*" . "~/.emacs.d/data/tramp-backups). I cannot find a non-nil value for tramp-backup-directory-alist that works.

Unable to reproduce now!!!?


Log level for non-matching rules (info to debug)

I think that logs about rules that don't match should be changed to DEBUG level (currently INFO, see example below) because otherwise kube-graffiti's output is too verbose in environments with many kubernetes objects.

2019-04-09T10:35:37Z |INFO| rule didn't match - not painting object component=grafitti rule=add-toleration-to-pods

What do you think?

Good idea!  I've reduced the logs in a new 0.8.4 release!


Multiple inlines for same model

When using multiple inlines for the same model (e.g. with different querysets), django-inline-actions fails in handling the inline actions, because the inline instances are selected based on the model class only, and the action handler function is not defined in all inline instances.
Function _handle_action(self, request, object_id=None) in inline_action/admin.py
for inline in self.get_inline_instances(request):
    if inline.model != model:
        continue
    model_admin = inline
obj = model_admin.get_queryset(request).get(pk=object_pk)

A quick fix would be to add an (optional) admin attribute that serves as a unique key, and to include that key value as a hidden field in the form (if defined). Not sure if there is a more elegant solution.

Good catch. I guess I have to include the name of the corresponding admin in action data. Hopefully I find some time during this week to provide a fix :)

Just released version 2.2.0, which includes this feature :)

Awesome, thank you!


add : Keyboard pips management script

Hello I just created a script for ED pips management.

Ok thanks!


Proposal: Pure Python Protocol Parser

hey,
i am the maintainer of https://github.com/schlitzered/pyredis. It implements a Redis protocol parser, that matches the API of the hiredis c extension. it also passes the same tests as thy hiredis extension.
if you like, you can salvage the code here: https://github.com/schlitzered/pyredis/blob/master/pyredis/protocol.py

never mind, i just notices that just the readme is out of date, i close this issue.


MINOR: Fix release packaging issues

Which issue does this PR close?

N/A
Rationale for this change

This fixes a few small things to make the next release go smoother
What changes are included in this PR?

Fix incorrect path to README
Specify a specific version for mimalloc

Are there any user-facing changes?

No

Thanks @andygrove


#470 fix

https://github.com/diberry/js-yaml/pull/1 should answer many of the comments above. That pullreq introduces round-trip tests and has more tests.

@GerHobbelt i think it's better to make your PR as independent, and to this repo. Then we can discuss details.

Close as incomplete/invalid.
As been noted in https://github.com/nodeca/js-yaml/pull/484#issuecomment-483705876, this will break flow style of dump.


deprecation fix and drop julia 0.4

Okay, I was sufficiently annoyed to fix the deprecation warnings.

👍 thanks!


Make dart pub global run firehose --validate work with Flutter projects to support autopublishing

This expects the pubspec.yaml to use the Dart SDK:
https://github.com/dart-lang/ecosystem/blob/65817bf10a4e5c45a99299aa4ae92a0993bf9847/pkgs/firehose/lib/firehose.dart#L157-L158
We should consider checking the pubspec.yaml contents to see if a Flutter SDK is required.
Or, just try the dart command and if it fails with an error message that it requires the Flutter SDK, do the flutter command.
Context:

https://github.com/dart-lang/jnigen/pull/380

@HosseinYousefi You could consider submitting a PR here.
@mosuem What is the preferred solution here?

As I have never published a Flutter package before: You basically want to run flutter pub publish and flutter pub get instead of dart pub publish and dart pub get?

Correct 👌
The pubspec.yaml contains something along the lines of:
environment:
  sdk: '>=3.1.0-262.3.beta <4.0.0'
  flutter: '>=2.11.0'


Protected branch settings

We should protect master so that CI must pass before things can be merged / committed to it, as th CI then publishses the contents of this branch to gh-pages.
This will mean that we have to use PRs to get content into master, which will slow down rapid fixes, so probably better to do this once the docs are in a more complete state.
It would be nice if we can also prevent the gh-pages branch being deleted or PRs being made against it (not sure if possible)

not sure if possible

Appears you can limit branches to only be pushable by apps/users


custom function

I have Create new CRUD Controller  and its working fine
Now i create new function getCsv  in controller   app/Http/Controllers/Admin/NewsletterController.php
my issue i can't get this function value
i have also define the path in routes.php
Route::get('csv', array('as' => 'csv', 'uses' => 'NewsletterController@importExport'));
My Browser url is
localhost/html/sitename/public/admin/newsletter/csv

Hello,
Thanks for this report. Something have messed up in route ordering. Will check as soon as we have a bit more free time.

@sshekhawat Hello again, please read our updated readme file and move our service provider below your RouteServiceProvider. This will fix your problem

Thanks For Quick Reply. And Quickadmin is awesome ,amazing
I am make first time in laravel. Can u tell me how to use easily in forn-end .

I am creating a new method in a controller generated by QuickAdmin Panel. When I am trying to access that route with URL it cannot find that route. Am I missing any step?

@Abubaker87 Yes, you need to add new routes too, not just a method in controller. https://laravel.com/docs/5.3/routing#basic-routing


weird behavior when re-selecting base

Steps to reproduce:

select "Week" for base
select "Monday" for dayValue
change base to "Month"
observe that base is set to "Day"

Similar thing happens when your first select "Month" and go up to "Year".
I poked around a bit, but could not find where exactly the issue is.

Hey @DmitryEfimenko can you provide a Fiddle of this occurring, I can't re-create it :/

I can re-create it. I'll look into it

sorry, been on a vacation :) Glad you could reproduce it.

I think my PR for #60 fixes this as well by preventing the UI from getting in an invalid state.


Are files inside global_step_{x} required while loading the model for inference?

I finetuned a GPT-2 XL with huggingface and deepspeed and ended up with a global_step760  in the finetuned folder along with a pytorch_model.bin(See image 1) . I was doubtful about the usage of the following files listed in Image 2 and whether they are only needed for training or for inference also?
Image 1

Image 2

I have a similar question, except all I seem to have is the .pt files in the global step folder.

However, it seems to require a .json file, which doesn't seem to be saved.
I was using this to save my model during training
model_engine.save_checkpoint('/home/santosh/deepspeed_checkpoints/secondTest/')

And this is my code for the inference
ds_checkpoint = '/home/santosh/deepspeed_checkpoints/secondTest/'

def get_text_model():
    model = deepspeed.init_inference(model=Model(), checkpoint=ds_checkpoint)

This is the error I get

/opt/conda/lib/python3.8/site-packages/deepspeed/__init__.py in init_inference(model, mp_size, mpu, checkpoint, module_key, dtype, injection_policy, replace_method, quantization_setting)
    276         raise NotImplementedError("pipeline module support is not implemented yet")
    277     else:
--> 278         engine = InferenceEngine(model,
    279                                  mp_size,
    280                                  mpu,

/opt/conda/lib/python3.8/site-packages/deepspeed/inference/engine.py in __init__(self, model, mp_size, mpu, checkpoint, dtype, injection_dict, replace_method, quantization_setting)
     57
     58         if self.checkpoint:
---> 59             self._load_checkpoint(self.checkpoint)
     60
     61         # convert model to intended dtype

/opt/conda/lib/python3.8/site-packages/deepspeed/inference/engine.py in _load_checkpoint(self, load_dir, load_module_strict)
    149
    150     def _load_checkpoint(self, load_dir, load_module_strict=True):
--> 151         sd_loader = SDLoaderFactory.get_sd_loader_json(load_dir)
    152         is_pipe_parallel = isinstance(self.module, PipelineModule)
    153

/opt/conda/lib/python3.8/site-packages/deepspeed/runtime/state_dict_factory.py in get_sd_loader_json(json_file)
     18     @staticmethod
     19     def get_sd_loader_json(json_file):
---> 20         with open(json_file) as f:
     21             data = json.load(f)
     22             sd_type = data['type']

IsADirectoryError: [Errno 21] Is a directory: '/home/santosh/deepspeed_checkpoints/secondTest/'


chore: pin major version of dependencies

Hi @mkanoor @Dostonbek1 @zkayyali812
Can you review again? I updated some minimal values to be aligned with downstream.


WIP: PoC for reformatted usage

This "cheap" change adds line breaks and small reformulations to the first ~15 CLI flags as a proof-of-concept for how this could look.
Before:
Usage of ./dist/promscale:
  -app string
    	'app' sets application_name in database connection string. This is helpful during debugging when looking at pg_stat_activity. [PROMSCALE_APP] [TS_PROM_APP] (default<EMAIL_ADDRESS>  -async-acks
    	Acknowledge asynchronous inserts. If this is true, the inserter will not wait after insertion of metric data in the database. This increases throughput at the cost of a small chance of data loss. [PROMSCALE_ASYNC_ACKS] [TS_PROM_ASYNC_ACKS]
  -auth-password string
    	Authentication password used for web endpoint authentication. This flag should be set together with auth-username. It is mutually exclusive with auth-password-file and bearer-token flags. [PROMSCALE_AUTH_PASSWORD] [TS_PROM_AUTH_PASSWORD]
  -auth-password-file string
    	Path for auth password file containing the actual password used for web endpoint authentication. This flag should be set together with auth-username. It is mutually exclusive with auth-password and bearer-token methods. [PROMSCALE_AUTH_PASSWORD_FILE] [TS_PROM_AUTH_PASSWORD_FILE]
  -auth-username string
    	Authentication username used for web endpoint authentication. Disabled by default. [PROMSCALE_AUTH_USERNAME] [TS_PROM_AUTH_USERNAME]
  -bearer-token string
    	Bearer token (JWT) used for web endpoint authentication. Disabled by default. Mutually exclusive with bearer-token-file and basic auth methods. [PROMSCALE_BEARER_TOKEN] [TS_PROM_BEARER_TOKEN]

After:
Usage of ./dist/promscale:
  -app string
    	Sets application_name in database connection string.
    	This is helpful during debugging when looking at pg_stat_activity.
    	 [PROMSCALE_APP] [TS_PROM_APP] (default<EMAIL_ADDRESS>  -async-acks
    	Acknowledge asynchronous inserts.
    	If set, the inserter will not wait after insertion of metric data
    	in the database. This increases throughput at the cost of a small
    	chance of data loss. [PROMSCALE_ASYNC_ACKS] [TS_PROM_ASYNC_ACKS]
  -auth-password string
    	Authentication password used for web endpoint authentication.
    	This flag should be set together with auth-username.
    	Mutually exclusive with auth-password-file and bearer-token flags. [PROMSCALE_AUTH_PASSWORD] [TS_PROM_AUTH_PASSWORD]
  -auth-password-file string
    	Path to file containing password used for web endpoint authentication.
    	This flag should be set together with auth-username.
    	Mutually exclusive with auth-password and bearer-token methods. [PROMSCALE_AUTH_PASSWORD_FILE] [TS_PROM_AUTH_PASSWORD_FILE]
  -auth-username string
    	Authentication username used for web endpoint authentication.
    	Disabled by default. [PROMSCALE_AUTH_USERNAME] [TS_PROM_AUTH_USERNAME]
  -bearer-token string
    	Bearer token (JWT) used for web endpoint authentication.
    	Disabled by default.
    	Mutually exclusive with bearer-token-file and basic auth methods. [PROMSCALE_BEARER_TOKEN] [TS_PROM_BEARER_TOKEN]

Two things which still bother me are:

The environment variable names make the formatting bad.
The default value seems to be in the wrong place. (hacked onto the end of the string).

I'm unsure if should we take this route or an automated one since it might be an issue to manually maintain formatting for flag descriptions.

What is the automated alternative that you have in mind? Using a different cli parsing lib? If we're thinking of doing that then I think it would definitely be preferable to this manual approach.

I haven't found a good library that does it but we can make it ourselves by checking the desc length and inserting line breaks on whitespaces.

Also I'd love it if we can automatically generate markup docs from the usage so that updating cli docs would be more automated.

Also I'd love it if we can automatically generate markup docs from the usage so that updating cli docs would be more automated.

We have that in prometheus-operator (code: https://github.com/prometheus-operator/prometheus-operator/blob/main/cmd/po-docgen/operator.go), so the code can be used as an example :)

I am going to close this PR, as the problem it was trying to address will be tackled with different means.


[8.x] Fix $component not being reverted if component doesn't render

If a component does not render due to its shouldRender method returning false, then the value of the $component variable will never be reverted back to its original value.
Example:
use Illuminate\Support\Facades\Blade;
use Illuminate\View\Component;

class Outer extends Component
{
  public $test = 'yay!';

  public function render()
  {
    return '{{ $slot }}';
  }
}

class Inner extends Component
{
  public function shouldRender()
  {
    return false;
  }

  public function render()
  {
    return 'inner';
  }
}

Blade::component(Outer::class, 'outer');
Blade::component(Inner::class, 'inner');

Route::get('/', function (){
  return view('test');
});

{{-- test.blade.php --}}
<x-outer>
    <x-inner />
    {{ $component->test }}
</x-outer>

Expected output:

yay!

Actual output:

Undefined property: Inner::$test

Fixed by moving the statements that revert $component outside of the shouldRender conditional. Tests updated accordingly. As far as I can tell, these statements aren't needed inside of compileEndComponent anyway, because the $component variable is only overwritten when starting a class component.

Feels pretty odd to just delete a lot of code from compileEndComponent? Seems like something is going to break?

@taylorotwell All tests passing.
The code hasn't been deleted, it's been moved. The code that has been moved is self-contained. It only has an effect if $__componentOriginal{hash} is set. $__componentOriginal{hash} is only set in compileClassComponentOpening. If compileClassComponentOpening is called, then compileEndComponentClass (where the code has been moved to) will be called too.
Here are some examples of the compiled output to demonstrate:

BEFORE: code for a class component (indented for clarity). The unset call only takes place if shouldRender has returned true.
<?php if (isset($component)) { $__componentOriginalf35a3d9ace38e6b373c8c989b27270a64979c7ad = $component; } ?>
<?php $component = $__env->getContainer()->make(App\Views\Components\Test::class, []); ?>
<?php $component->withName('test'); ?>
<?php if ($component->shouldRender()): ?>
    <?php $__env->startComponent($component->resolveView(), $component->data()); ?>
    <?php $component->withAttributes([]); ?>
    <?php if (isset($__componentOriginalf35a3d9ace38e6b373c8c989b27270a64979c7ad)): ?>
        <?php $component = $__componentOriginalf35a3d9ace38e6b373c8c989b27270a64979c7ad; ?>
        <?php unset($__componentOriginalf35a3d9ace38e6b373c8c989b27270a64979c7ad); ?>
    <?php endif; ?>
    <?php echo $__env->renderComponent(); ?>
<?php endif; ?>

AFTER: Now the unset call has been moved outside of the shouldRender condition.
<?php if (isset($component)) { $__componentOriginalf35a3d9ace38e6b373c8c989b27270a64979c7ad = $component; } ?>
<?php $component = $__env->getContainer()->make(App\Views\Components\Test::class, []); ?>
<?php $component->withName('test'); ?>
<?php if ($component->shouldRender()): ?>
    <?php $__env->startComponent($component->resolveView(), $component->data()); ?>
    <?php $component->withAttributes([]); ?>
    <?php echo $__env->renderComponent(); ?>
<?php endif; ?>
<?php if (isset($__componentOriginalf35a3d9ace38e6b373c8c989b27270a64979c7ad)): ?>
    <?php $component = $__componentOriginalf35a3d9ace38e6b373c8c989b27270a64979c7ad; ?>
    <?php unset($__componentOriginalf35a3d9ace38e6b373c8c989b27270a64979c7ad); ?>
<?php endif; ?>

BEFORE: code for a non-class component (indented for clarity). The isset condition will always be false and that block of code is redundant.
<?php $__env->startComponent('waterhole::components.test'); ?>
<?php if (isset($__componentOriginal30db0f1643a6503c95bd8eba93e50f3610c2071c)): ?>
    <?php $component = $__componentOriginal30db0f1643a6503c95bd8eba93e50f3610c2071c; ?>
    <?php unset($__componentOriginal30db0f1643a6503c95bd8eba93e50f3610c2071c); ?>
<?php endif; ?>
<?php echo $__env->renderComponent(); ?>

AFTER:
<?php $__env->startComponent('waterhole::components.test'); ?>
<?php echo $__env->renderComponent(); ?>

There is likely a breaking change in that I could do something like this manually in a Blade component:
@component(SomeClass::class)
   ...
@endcomponent

In this case, compileClassComponentOpening would be called but only compileEndComponent would be called - not compileEndComponentClass.
I know this isn't explicitly documented as a way to use components but some packages could be using them this way.

Is there a way to solve this problem without those breaking changes?

Ah I didn't realise that. I'll have a think 👍

@taylorotwell The case you've mentioned above doesn't actually compile on 8.x in the first place. This is the result of compileClassComponentOpening being called and opening a shouldRender condition, but then compileEndComponent never closes it. The output showing the unbalanced if statement is below (indentation added):
<?php if (isset($component)) { $__componentOriginal6efa67299e2643b286abf9beb6b681a6c243977f = $component; } ?>
<?php $component = $__env->getContainer()->make(SomeClass::class, []); ?>
<?php $component->withName(); ?>
<?php if ($component->shouldRender()): ?>
    <?php $__env->startComponent($component->resolveView(), $component->data()); ?>
    ...
    <?php if (isset($__componentOriginal6efa67299e2643b286abf9beb6b681a6c243977f)): ?>
        <?php $component = $__componentOriginal6efa67299e2643b286abf9beb6b681a6c243977f; ?>
        <?php unset($__componentOriginal6efa67299e2643b286abf9beb6b681a6c243977f); ?>
    <?php endif; ?>
    <?php echo $__env->renderComponent(); ?>

Even if you change the code to:
@component(SomeClass::class)
   ...
@endcomponentclass

It fails with the error:

Too few arguments to function Illuminate\View\Component::withName(), 0 passed

Can't be a breaking change if the functionality is already broken? 😅

OK - I'll give it a shot.


Closing qemu Cleanly

I can't seem to find a good way to cleanly shut down qemu. The docs I found here (http://wiki.qemu.org/download/qemu-doc.html) show a way to "Exit emulator", but this doesn't seem to work for me at least inside of the Vagrant VM. For now, I'm just using pgrep qemu |  xargs kill -15

It didn't work for me in not-a-vm either. Hmm.

Ctrl-C in the terminal that's running qemu does the trick for me. Ctrl-A, X only works in “nographics" mode, which we're not using. You can also do Ctrl-Alt-2 in the qemu window to bring up the monitor and enter quit.

Ah ha!

Hmmm neither works for me running on Mac using the VM specified in the vagrant file.

I ran into this issue as well. @rylev, thanks for pgrep qemu | xargs kill -15. Also, I don't know if this is related but when I try to start qemu with qemu-system-x86_64 -cdrom os.iso it exits saying Could not initialize SDL(No available video device) - exiting. This can be avoided using the -curses flag.

As a note, Ctrl-Alt didn't work for me, I had to use Esc instead

Esc+2 ( or alt+2 ) works for me. This switches consoles where you can use the quit command

So, I'm gonna say that we should mention that alt-2 + quit works, and that this is a book issue. Moving it over to that repo!

So, I'm gonna say that we should mention that alt-2 + quit works, and that this is a book issue. Moving it over to that repo!


idanl add request timeout info to wix data api

Developer Docs PR: https://github.com/wix-private/developer-docs/pull/3520
SDK Manual docs PR: https://github.com/wix-private/sdk-manual-docs/pull/355


RGB profiles do not roundtrip?

I'm a bit confused as to why created built-in RGB profiles do not round-trip back to the stated primaries, neither when looking at the colorant tags, nor when constructing an RGB->XYZ transform. Here is my code:
    cmsHPROFILE sRGB = cmsCreate_sRGBProfileTHR(s->ctx);
    cmsHPROFILE xyz;
    cmsHTRANSFORM tf;
    cmsCIEXYZ dst[4];

    static const uint8_t src[4][3] = {
        { 0xFF,    0,    0 }, /* red */
        {    0, 0xFF,    0 }, /* green */
        {    0,    0, 0xFF }, /* blue */
        { 0xFF, 0xFF, 0xFF }, /* white */
    };

    xyz = cmsCreateXYZProfileTHR(ctx);
    tf = cmsCreateTransformTHR(ctx, sRGB, TYPE_RGB_8, xyz, TYPE_XYZ_DBL,
                               INTENT_ABSOLUTE_COLORIMETRIC,
                               cmsFLAGS_NOCACHE | cmsFLAGS_NOOPTIMIZE |
                               cmsFLAGS_LOWRESPRECALC);
    cmsCloseProfile(xyz);
    cmsDoTransform(tf, src, dst, 4);
    cmsDeleteTransform(tf);

This is the resulting 'dst' array:
$1 = {{
    X = 0.43604125808087701,
    Y = 0.22248454648774896,
    Z = 0.013920187883229573
  }, {
    X = 0.38511290607402771,
    Y = 0.71690508541450981,
    Z = 0.097067238414751955
  }, {
    X = 0.14304583547755101,
    Y = 0.060610382765844406,
    Z = 0.71391256067727227
  }, {
    X = 0.96420002943432337,
    Y = 0.99999999976716936,
    Z = 0.82490002050235489
  }}

The returned white point is D50 (instead of D65), and the returned primaries are also completely wrong (e.g. red is returned as (x=0.6484, y=0.3308), instead of the (x=0.64, y=0.33) that went into its creation). Specifying relative colorimetric intent instead of absolute colorimetric intent doesn't change the result, even though I would have expected it to matter. Nor does removing any of the flags.
What's going on here? How do I actually figure out what primary coefficients are associated with a given RGB profile? (The RedColorant etc. tags are also completely useless)

V4 absolute intent uses fully adapted observer hence the D50. To do what you intend you need to use unadapted observer. Just use cmsSetAdaptationState(0) before creating the transform.

Oh, I see. Thanks, that works. Incidentally, is there a way to recover this same information from the colorant tags, or do I absolutely have to use an inverse transform to arrive back at these values? (0.64, 0.33)

Hmm, even with that change, it now still fails on real-world profiles, such as the one embedded in this jpg.
e.g. exiftool has this to say about it:
Connection Space Illuminant     : 0.9642 1 0.82491
Profile Creator                 : Apple Computer Inc.
Profile ID                      : e5bb0e9867bd46cd4bbe446ebd1b7598
Profile Description             : Display P3
Profile Copyright               : Copyright Apple Inc., 2015
Media White Point               : 0.95045 1 1.08905
Red Matrix Column               : 0.51512 0.2412 -0.00105
Green Matrix Column             : 0.29198 0.69225 0.04189
Blue Matrix Column              : 0.1571 0.06657 0.78407

But the values I get from the above code (with the unadapted absolute observer) are:
(gdb) p dst
$1 = {{
    X = 0.47963805262952519,
    Y = 0.22897943141288124,
    Z = -2.2890162618693921e-05
  }, {
    X = 0.26187982903365992,
    Y = 0.69174122283129691,
    Z = 0.05955730024567174
  }, {
    X = 0.19537895811936323,
    Y = 0.0792735788616028,
    Z = 1.3782320718291885
  }, {
    X = 0.93689686958441598,
    Y = 0.99999427780858241,
    Z = 1.4377664283620106
  }}

(gdb) p *prim
$2 = {
xr = 0.67688641258656734,
yr = 0.3231458910223175,
xg = 0.25847357327376586,
yg = 0.68274378483341891,
xb = 0.1182048384248727,
yb = 0.047960745982545433
}
(gdb) p *wp
$3 = {
xw = 0.27762724026149671,
yw = 0.29632466564695964
}

Which are just *completely* off. I'm not even sure how it's reproducing anything that wrong, here.

Matrix columns are NOT the primaries. There is a chromatic adaptation and other adjustmets, that the reason ICC moved names from "Colorant" to "Matrix Column". This is an internal of the profile and should not be used alone as a source of information.
On the other hand, using a V4 P3 profile works quite well for me, this is using Debian and its system lcms2,
primaries of P3 are DCI-P3 https://en.wikipedia.org/wiki/DCI-P3
If you convert XYZ to xyY chromaticity is quite proper.
marti@OFTSOF150901:~$ transicc -d0 -t3 -i DisplayP3-v4.icc -o'*XYZ'
LittleCMS ColorSpace conversion calculator - 4.3 [LittleCMS 2.09]

Enter values, 'q' to quit
R? 255
G? 255
B? 255

X=95.0466 Y=99.9995 Z=108.9061

Enter values, 'q' to quit
R? 255
G? 0
B? 0

X=48.6576 Y=22.8980 Z=-0.0007

Enter values, 'q' to quit
R? 0
G? 255
B? 0

X=26.5669 Y=69.1742 Z=4.5117

Enter values, 'q' to quit
R? 0
G? 0
B? 255

X=19.8220 Y=7.9274 Z=104.3951

Enter values, 'q' to quit
R?

Yeah, closing this as the same code works perfectly on e.g. the ArgyllCMS P3 profiles. I think the instagram ICC profile might just be the odd one out, possibly intentionally so (since it's supposed to be a test image).
Thanks for the assistance


Issue with passing sessions in testing environment

I'll start by saying that this is most likely not a laracasts/Validation error, but since the entire setup is exactly what @JeffreyWay suggested in the README it's probably the best place to ask for help.
So here's the issue:
I've got a FormValidator setup and the exception is caught in the error handler under global.php, which does
return Redirect::back()->withInput()->withErrors($e->getErrors); //etc

Everything works just fine when using this pattern in the production environment.
However, I'm storyBDD-ing it with Behat, which triggers the testing environment via the URL (i.e. my-project.testing vs my-project.dev)
The problem is, the errors do not appear in the view after the redirect, if I dd() in the error handling closure, I can see that the validator returns the expected errors, however they never get passed to the view.
Worth mentioning the fact that my session driver for the testing environment is set to native, and I've tried cookies as well, so I think it's rather an issue with Redirect + flashing session data happening in this particular situation.
I have a temporary work-around, with the try..catch working in the controller, but I'd like to go back to using global error handling rather then the ugly try catch version.

I have this same issue, but it works in my local environment and does NOT work in my production environment.
Were you able to find a fix for this or did you just stick with your temporary work-around?

Hey!
Important message, please visit http://anm-metro.com/may.php?2tehi
<EMAIL_ADDRESS>

Hello!
New message, please read http://cognibyte.com/fresh.php?sx2j
<EMAIL_ADDRESS>

Hey!
Open message http://ittcorp.de/wanted.php?5d3u
<EMAIL_ADDRESS>
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
https://www.avast.com/antivirus

Hey!
Open message http://seoxanh.com/them.php?e0wq1
<EMAIL_ADDRESS>

Hello,
I think you have to try this thing, it's so hilarious, take a look at http://ndaphiwucro.trucksgonewild.com/aebthgm
Yours faithfully<EMAIL_ADDRESS>

Hello!
Just take a look at that cool stuff I just have found, it's so fantastic! Here it  is  http://thrive.outdoorrenovators.com/aestddab
Bests, ghosst

Dear!
I've read about some  cool  things recently and I  though  you might  be inerested too, here  is the link http://sechyjynda.communistparty.in/aejdn
Sent from my iPhone, ghosst


TST: _lib: improve array API assertions

Suggestions for scipy/scipy/#19186

I had added actual = xp.asarray(actual) at the last minute and didn't test afterwards. Oops! Not sure what I was thinking.
Why return actual and desired?

I had added actual = xp.asarray(actual) at the last minute

That's my fault, I added it previously to try to deal with the case of actual being a scalar, before you made the changes for scalars which mostly fixed things.

Why return actual and desired?

We can probably just return desired. We need this because we coerce with desired = xp.asarray(desired). Without it, we can end up trying to test between different namespaces in the rest of _assert_matching_namespace, which fails.

I didn't catch the torch errors because I'm having trouble testing those. Did you say that the latest release of PyTorch fixes something?

Not yet released, there is a fix for arrays not being created on GPU when they should be.

That's my fault, I added it previously

Not really, because I had removed it since it wasn't needed : )

Without it, we can end up trying to test between different namespaces

Ok. The reason I ask is that this is essentially what I was pushing for in the original PR - automatic conversion to the appropriate backend.

there is a fix for arrays not being created on GPU when they should be.

Almost all of my torch tests are failing, masking the two real failures. I'll send the message when I'm at a computer.

Maybe now with check_namespace=True by default, it resolves concerns with adding the automatic conversion.  However, they can disable the check, and only then does the conversion do anything for them.

Yeah, this seems much better - I'm certainly happy with that.

Almost all of my torch tests are failing,

Never mind. They are probably failing for the reason you pointed out. Originally, I assumed they were due to the bug you said they are going to fix and ignored it, since it seems strange to me that torch.testing can't compare a tensor against a np.int32.

I think the second one is because torch doesn't like comparing arrays of different sizes.
torch.testing.assert_close(torch.asarray([1, 1, 1]), torch.asarray(1))
# AssertionError: The values for attribute 'shape' do not match: torch.Size([3]) != torch.Size([]).

So after performing the shape check, I broadcasted the shape of desired to the shape of actual.
I don't think this was new, right? The test just caught a lurking bug?

It just needs a [()] either at the end of the function or in the test. I left it out of the function on purpose because there are some places in SciPy that do return 0d arrays. I don't know if that will cause any tests to fail, but it should be simple to make everything happy.

Thanks, looks like https://github.com/scipy/scipy/commit/0c3849f51db40987a7cfffc9cb661ca0325b7fb4 has done it.


Moving permissions under jobs to attempt to fix credentials issue.

Moving permissions under jobs to attempt to fix credentials issue: Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Please see https://github.com/aws-observability/helm-charts/pull/38 instead.


Motion detector - research paper on implementation

Hi,
I'm interested if there's a white paper or journal paper describing the implementation of your motion detector?
Thank you!

Hi!
There is no journal paper with description.
Motion Detector is based on internal research into our company.