Please, document environment variables

Please, document the variables below:

MONGO_INITDB_DATABASE
MONGO_INITDB_ROOT_USERNAME
MONGO_INITDB_ROOT_PASSWORD

Why is this not documented?
As devops we keep telling others to "RTFM", at this point it's "RTFS".

It's not documented yet both because we haven't gotten to writing good docs
for it yet, and because it doesn't work as well as we'd like it to yet (so
we still consider it somewhat experimental).  For example, it has very
annoying edge behavior when folks attempt to use it together with a
configuration file.

@tianon how can we help?

@imaia thanks for any help!  Any documentation would go in the content.md file over here.
I think the best option we thought to improve the reliability of these variables was to add a small yaml parser to the image to parse the MongoDB config file and use it with our cli flag parsing to ensure we properly detect ssl usage and other conflicting config.  I don't recall what @tianon had found when searching for a small yaml parser. We just haven't been able to get back to give the MongoDB image more attention.
Here is the section that we have to ensure certain config flags are set for mongod.  It all is a little hacky, and I'd love a better way to do it.  The biggest annoyance is mongod handling of config; it just fails if config options exist twice (two flags or one flag and one in the config file); it can't handle allowSSL if there is no ssl config, or disabled sslMode when there are ssl certs.
Have any ideas where you would like to help?

Has the actual OP issue been resolved yet? Still can't find doco for setting the auth in environment variables

Parsing the config file was added in https://github.com/docker-library/mongo/pull/225, which was the main driver for considering this functionality to still be experimental, so we're definitely ready to document this.
It looks like there's been a stab taken at doing so in https://github.com/docker-library/docs/pull/1127, but we haven't had a chance to review it in depth yet.

Closing in favor of https://github.com/docker-library/docs/pull/1127 (since this is really a documentation issue, not an image issue). :+1:


Add indices to ElementIndices to speed up queries

I'd like to suggest additional indices on ElementInstance.
That table is queried from the monitor, and if you have some amount of data in the table, the query would run ages.
This PR adds some indices.
Fixes https://github.com/camunda-community-hub/zeebe-simple-monitor/issues/583, supersedes #584.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm sorry. The CLA is signed, I cannot do anything about the issue with the CLA assistant.
FTR: I accept the CLA.

Any news about this?
AFAICS the CLA tool blocks me from signing the CLA correctly, I see no option to correct, update or re-sign the CLA.
I don't know if you as maintainers can reject or revoke my CLA, so that I'm able to sign it again with hopefully correct name, but I cannot solve this issue on my own.
As mentioned in #584  I even do not see my signature on https://cla-assistant.io/my-cla. There is an open issue in CLA assistant which sounds related https://github.com/cla-assistant/cla-assistant/issues/380.
Maybe my not on https://github.com/camunda-community-hub/zeebe-simple-monitor/pull/585#issuecomment-1794221491 is enough to proceed with this PR?


chore: bump production version to v5.0.6 for ocis_full

Release v5.0.6 is done, now updating the deployment example ocis_full for production demo.

do we need Forward port stable-5.0 changelog? https://github.com/owncloud/ocis/pull/9629/files#diff-43ed9d31bea2a6d518d69836bcd1a8e6bd81bf4df96c4745792c220ca5aa549c
to have changelog/5.0.6_

superseded by https://github.com/owncloud/ocis/pull/9660

do we need port changelog from stable-5.0? https://github.com/owncloud/ocis/pull/9629/files
to have changelog/5.0.6_

don't know. @micbar how do you handle this here?

We need to copy that to the master branch.


Also check priors when doing PE tests

A good point raised by @AntoniRamosBuades today:
When looking at PE results, it's also important to check what happens to the priors.
This would need: finding out what priors were used in the original analysis.
Draw samples from the prior, and repeat exactly what you do for the posterior samples: generate waveforms, compute ecc/mean_ano. Then compare the priors on the measured ecc/mean_ano with the priors on the model's ecc/mean_ano.
We may even want to reweight the posteriors so that the effective prior in the measured params are flat.

Something to keep in mind when converting posterior to standard definition but no longer need it to be open.


Updating for new JHU data stream

Hi Hamel,
Hopefully this works this time! Thanks so much! I am truly appreciative.
Thanks,
Adrian

Please remove _posts/2020-03-23-cumulative-outstanding.md from this PR


Hi, where can I download the cardiac MRI dataset and the fetal brain ultrasound MRI

Unfortunately these data are private, but the code should be working similarly for any other public dataset.

Unfortunately these data are private, but the code should be working similarly for any other public dataset.


RuntimeError: expected backend CPU and dtype Double but got backend CPU and dtype Float

Hello,
Thank for providing the code !
I am trying to your code on Pytorch 1.1.0 and I receive this error.
Do you have this kind of error on other Pytorch version ?

I fixed this myself by changing the source code of Pytorch1.1.0. Seems like this is a bug for the new version. The easy fix is to convert the tensor type as the original dtype:
dtype = tensor.dtype     mean = torch.as_tensor(mean, dtype=dtype, device=tensor.device)     std = torch.as_tensor(std, dtype=dtype, device=tensor.device)     tensor.sub_(mean[:, None, None]).div_(std[:, None, None])     return tensor
Path to the source file : /usr/local/lib/python3.6/dist-packages/torchvision/transforms/functional.py


Sync to prometheus/main 37f3f3f2db95539a9c84242936018908ffb3dd50

This brings main to the commit previous to enable errorf rule from perfsprint linter · prometheus/prometheus@af1a19f (https://github.com/prometheus/prometheus/pull/15318), which is a noisy change in 60+ files making it hard to review.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.6 out of 10 committers have signed the CLA.:white_check_mark: wuast94:white_check_mark: aknuds1:white_check_mark: roidelapluie:white_check_mark: bboreham:white_check_mark: beorn7:white_check_mark: colega:x: yeya24:x: juliusv:x: ahurtaud:x: simonpasquierYou have signed the CLA already but the status is still pending? Let us recheck it.


Issue with images. Space reserved, though no picture

having an issue with images not loading. believe it's a bug/issue with compatibility (on their part). For the latter, feed validation passed, but with reccomendations. Regardless, the images show up in other feed aggregators and I've checked the options, everything seems to be enabled. oddly, the reserved space seems to be there, as if it knew the size of the picture, just not load. Refer to examples for this
Source:
https://forum.warthunder.com/index.php?/forum/26-project-news-read-only.xml
Examples:
https://i.imgur.com/DwthIjq.png
https://i.imgur.com/czx5Ajw.png

That embed (box) is unrelated to the bot - copy and paste the link yourself and you'll probably see the same thing happen to your message because Discord automatically generates it based on page metadata.

I got you, think it has something to do with them embedding the images inside the RSS description tag rather than having it within the proper image tag
<image>
  <url>https://www.w3schools.com/images/logo.gif</url>
  <title>W3Schools.com</title>
  <link>https://www.w3schools.com</link>
</image>

Like I mentioned, other RSS services/programs I used seemed to be able to spot the embedded image; is this outside limitations of the bot or rather something that just needed to be implemented. If the latter, would this be something to look into implementing?

As I have just said, this is unrelated to the bot. Discord automatically generates the embed based on the link's metadata. Copy the link yourself and paste it in Discord and you will see that Discord automatically creates it, not the bot. All it did is post a link.

Discord reads the metadata off the link to generate the embed - in this case, the metadata from that link is

You can blame the website owners for generating such metadata that Discord then reads to automatically put under any messages that has that link. To provide more examples of what I mean by an automatically generated embed that Discord creates:

Okay I misunderstood, this clarified it for me:

Copy the link yourself and paste it in Discord and you will see that Discord automatically creates it, not the bot.

Yeah I figured it was because they didn't put the image in rss standards, I will message them eventually, thanks


  I have vcf files. Could you explain the process?

Read the README.md
This command:
python manage.py load_variants_file
calls the load_variants_file function in exac.py
(https://github.com/konradjk/exac_browser/blob/master/exac.py#L147)
which calls the parse_tabix_file_subset function which in turn calls
the get_variants_from_sites_vcf function in parsing.py
which parses the VEP annotated VCF files
The get_variants_from_sites_vcf function is the one that does the
actual parsing of the VCF file so you should read it to understand what is the
expected format.
The ExAC team can give you more information about this.
On 21 July 2016 at 18:01, sacha schutz<EMAIL_ADDRESS>wrote:

I want to load my own data. I have vcf files. Could you explain the process?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Do you have any suggested tools to calculate the coverage, given bam files or a merged vcf file?


Port changes of [#17390] to branch-2.8

What changes are proposed in this pull request?
Port changes of [#17390] to branch-2.8.
Support range copy in copyObject and copyPart

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to enterprise-2.8-4.x please


x/exp/shiny: error on Ubuntu 14.04

Here is the error I've got when trying to run golang.org/x/exp/shiny/example/tile with go version go1.5.1 linux/amd64:
# golang.org/x/exp/shiny/driver/x11driver
../../driver/x11driver/screen.go:356: cannot use int32(width) (type int32) as type uint16 in argument to xproto.CreateWindow
../../driver/x11driver/screen.go:356: cannot use int32(height) (type int32) as type uint16 in argument to xproto.CreateWindow

I was able to get it to work properly by changing the int32 type used driver/x11driver/screen.go:356 to uint16.
Will submit fix soon.

Fixed by https://golang.org/cl/16552


Show umami version

Describe the feature or enhancement
It would be nice to see Umami's version listed somewhere on the website.
Perhaps in a footer?

We do have a footer component that displays the version, but it's currently only visible when using a share URL. You can see it at the bottom of the Live Demo. Need to check why it was decided to be restricted to just share links.

If for some reason it needs to be restricted, can we at least make it a compile time option?

Need to check why it was decided to be restricted to just share links.

I think it was displayed in former umami version. Should be great having it at least in the admin area to compare version number with new release.


master-service-namespace is removed from kubelet in v1.27

On this page https://kubernetes.io/blog/2023/03/17/upcoming-changes-in-kubernetes-v1-27/#removal-of-master-service-namespace-command-line-argument and source https://github.com/kubernetes/website/blob/main/content/en/blog/_posts/2023-03-17-kubernetes-1.27-deprecations-and-removals.md#removal-of---master-service-namespace-command-line-argument it's mentioned that the master-service-namespace cli flag is removed, but as per https://github.com/kubernetes/kubernetes/pull/116015 (from the 1.27-beta.0 changelog), the kubelet cli flag is removed and the api server flag was removed way back in v1.7.
I could do a PR once this issue is confirmed

correction, the flag was removed from apiserver in 1.26, i misread the mentioned pull requests in https://github.com/kubernetes/kubernetes/pull/114446 this says 1.26 :thinking:

https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/ doesn't have the master-service-namespace but 1.25 has https://v1-25.docs.kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/ so seems this was removed already i 1.26

/area blog
/language en
/sig api-machinery


Memcache 8.2

Memcache extension was released yesterday.
https://pecl.php.net/package/memcache
I don't know Ruby, but now default version is 8.0
https://github.com/shivammathur/homebrew-extensions/blob/master/Formula/memcache%408.2.rb#L11
Could you add the newest version or tell me what I need to do to upgrade?

@xepozz
Updated

Thanks a lot

@xepozz Please create an issue with the details about your workflow here


Add a No-Op function

Add a No-Op function. Along with a session idle timeout and session
renew time, we can ensure that closed browsers (which will stop
performing no-op operations) will be logged out.
Change-Id: Ibdd1a55b172fc2aad2c8bed012ae86508d1d025b

@halatmit @ewpatton @afmckinney Please Review

I didn't test this, but made a comment about time units.   Maybe it's just my confusion.

They are in minutes. That is documented in appinventor-web.xml, where they
are set.
-Jeff
On Tue, Aug 9, 2016 at 10:02 AM, hal<EMAIL_ADDRESS>wrote:

I didn't test this, but made a comment about time units. Maybe it's just
my confusion.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mit-cml/appinventor-sources/pull/834#issuecomment-238562562,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhdOKI4uN5Ehh0Ma1xqzUmij1EBLmEZks5qeIh8gaJpZM4Jerb4
.

--

Jeffrey I. Schiller
Information Systems and Technology – MIT App Inventor
Massachusetts Institute of Technology
77 Massachusetts Avenue  Room 32-386
Cambridge, MA 02139-4307
617.910.0259 - Voice
<EMAIL_ADDRESS>http://jis.qyv.name
http://appinventor.mit.edu

Oh, OK.   I guess I was confused by the millis method.
== Hal
Hal Abelson
<EMAIL_ADDRESS>Prof. of Comp. Sci. and Eng.
MIT Dept. of Elec. Eng. and Comp. Sci.
On Tue, Aug 9, 2016 at 11:10 AM, Jeffrey Schiller<EMAIL_ADDRESS>wrote:

They are in minutes. That is documented in appinventor-web.xml, where they
are set.
-Jeff
On Tue, Aug 9, 2016 at 10:02 AM, hal<EMAIL_ADDRESS>wrote:

I didn't test this, but made a comment about time units. Maybe it's just
my confusion.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<https://github.com/mit-cml/appinventor-sources/pull/834#
issuecomment-238562562>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhdOKI4uN5Ehh0Ma1xqzUmij1EBLmEZks5qeIh8gaJpZM4Jerb4>
.

--

Jeffrey I. Schiller
Information Systems and Technology – MIT App Inventor
Massachusetts Institute of Technology
77 Massachusetts Avenue Room 32-386
Cambridge, MA 02139-4307
617.910.0259 - Voice
<EMAIL_ADDRESS>http://jis.qyv.name
http://appinventor.mit.edu

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mit-cml/appinventor-sources/pull/834#issuecomment-238584601,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAwLt3AAAAIAzF4ed5k9ZbyPkd5zbI7kks5qeJh_gaJpZM4Jerb4
.


[feature]: add daemon flag to set no_new_priv as default for unprivileged containers

[feature]: add daemon flag to set no_new_priv as default for unprivileged containers #29951
Signed-off-by: Daniel Zhang<EMAIL_ADDRESS>

As commented previously, we need to also support the old syntax without =true if possible, and have tests for both. A test for disabling on the daemon (and another for re-enabling) is also needed.

Actually old usage is still supported. I don't remove here.

Ok, if you could add the tests then with the old and new forms, and a test of the daemon flag that would be great

Sure, have done, please let me know if there is any problem.

The test failure is
12:17:31 # github.com/docker/docker/daemon
12:17:31 daemon/daemon_unix_test.go:14: imported and not used: "github.com/docker/docker/volume/drivers" as volumedrivers
12:17:31 daemon/daemon_unix_test.go:283: undefined: drivers in drivers.volumedrivers

which needs fixing (maybe changed at the time you rebased?)

Have updated, please review again.

This one: https://github.com/docker/docker/issues/29951
Cleared up now, thanks.
On 01/09/2017 06:29 PM, Daniel Zhang wrote:

jmzwcn commented on this pull request.

@@ -89,6 +90,7 @@ func (config *Config) InstallFlags(flags *pflag.FlagSet) {
flags.Int64Var(&config.CPURealtimePeriod, "cpu-rt-period", 0, "Limit the CPU real-time period in microseconds")
flags.Int64Var(&config.CPURealtimeRuntime, "cpu-rt-runtime", 0, "Limit the CPU real-time runtime in microseconds")
flags.StringVar(&config.SeccompProfile, "seccomp-profile", "", "Path to seccomp profile")

flags.BoolVar(&config.NoNewPrivileges, "no-new-privileges", false, "Disable container processes from gaining new privileges")

which link? I think It is false by default.

Any help about this conflict(integration-cli/docker_cli_run_unix_test.go)?

Any review?

Sorry, its a bit hectic with getting 1.13 released, I will take a look
again soon...
On 12 Jan 2017 2:50 p.m., "Daniel Zhang"<EMAIL_ADDRESS>wrote:

Any review?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/29984#issuecomment-272182283, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdcPH-3l4KTVb44FFr-nykK6mTRRxaLks5rRj2xgaJpZM4Ld3rr
.

Could we please have a review ASAP? I am afraid there will be conflict again.

Two minor comments but otherwise this looks fine, tested it thoroughly and it is working fine.  Thanks very much for doing this.

Any question?

LGTM cc @jessfraz @runcom @mrunalp

@cpuguy83
Seems it is a bit hard to pass daemon.configStore.NoNewPrivileges, because it only exist in unix, but our parseAndSetSecurityOpt is across platform...

I have restored the previous version. Please let me know if there is any problem.

ping @cpuguy83 were your comments addressed?

omg my dreams are coming trueeeeeee

might be nice to also add an integration test for the daemon where no_new_privs is true but a container is run with privileged and then one where you override no_new_privs to false on the container. :innocent:

@cpuguy83 ,
func(d *Daemon) parseSecurityOpt(...) { //Actually this method exist in container.go, because this setting is specified to daemon_unix.go
// do stuff--will have to make OS condition, it be best-practice?
parseSecurityOpt(...)
}

@jmzwcn It can go in a platform file, just that it will need to be defined on each platform.

@cpuguy83, already update, please let me know if any problem.
@jessfraz , seems TestParseNNPSecurityOptions has covered that scenario.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "issueNNP" git@github.com:jmzwcn/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842353432008
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

The conflict happen again. If possible, please merge ASAP. Thanks!

ping @justincormack

The actual flag to set this got lost in a rebase, and was added again in https://github.com/moby/moby/pull/32944


Design question: Semicolons and import statements

I was surprised when writing some bebop schemas that:
import "./example.bop";

struct Test {
    string Field;
}

... did not compile -- Expected Enum or Struct or Message or Union or Service, but found ';' of kind Semicolon.
And
import "./example.bop"

struct Test {
    string Field
}

Also did not compile -- Expected Semicolon, but found '}' of kind CloseBrace
The rules are, in one way, consistent -- top level definitions do not use semicolons and field definitions do use semicolons -- but why care? Why enforce the use of semicolons at all? It's been demonstrated by compilers in the past (Javascript + Typescript)(Go) that you can remove the need for semicolons as above entirely by injecting a semicolon if they are required and not provided.
An additional point of inconsistency: based on the theoretical rule I stated above, this should compile, as it is a top level statement:
const bool boolconst = true

But we get: Expected Semicolon, but found '' of kind EndOfFile
Were bebop to remove the need for semicolons but still support their presence, it would be a backwards compatible change, and formatters could automatically remove all of them (or place them where they are allowed, if that's your preferred style).

@lynn I don't think this is technically a bug, but I do agree with @200sc, when I started writing bebop for the first time the semicolons confused me a bit. I could see making them optional since (correct me if I am wrong) there is no case where we actually need it.

This is up next on my TODO


Update dict_pt-BR.po

Changed some translation based in its use-contexts

Thank you for contributing to the translation.


Panic on some png images

Yes, it's strange. But what if user named png image with jpeg extension, or there is just a broken data.
gopath\src\edwvee\jpegq>go run main.go
2018/06/03 23:37:00 length 3965
2018/06/03 23:37:00 Quantization table
2018/06/03 23:37:00   Precision=15; Table index=4 (chrominance)
2018/06/03 23:37:00 total 8576
panic: runtime error: index out of range

goroutine 1 [running]:
github.com/liut/jpegquality.(*jpegReader).readQuality(0xc042002480, 0xc04200e0c8, 0x2, 0x2)
        gopath/src/github.com/liut/jpegquality/jpegquality.go:111 +0xcb0
github.com/liut/jpegquality.New(0x4e3940, 0xc042004028, 0x0, 0x0, 0x0)
        gopath/src/github.com/liut/jpegquality/jpegquality.go:44 +0x12f
main.main()
        gopath/src/edwvee/jpegq/main.go:17 +0xc2
exit status 2

Attached an example of code + image.
jpegq.zip

Sorry for tooooo late reply. I'll check it and PRs is welcome.


Re-modularization

Methods in the Module traits now no longer require type class instances characterizing the context. This makes the test setup a little more complex, but usage is simpler.
Part of the motivation is that this approach makes the addition of the new FileModule a little cleaner.

[Current coverage][cc-pull] is 95.15%

Merging [#81][cc-pull] into [master][cc-base-branch] will increase coverage by -3.33%

@@           master        #81   diff @@
========================================
  Files          16         40    +24
  Lines         528        557    +29
  Methods         0        522   +522
  Branches       59         17    -42
========================================
+ Hits          520        530    +10
- Misses          8         27    +19
  Partials        0          0

2 files (not in diff) in ...ala/io/iteratee/task were created. more
2 files (not in diff) in ...la/io/iteratee/files were created. more
4 files (not in diff) in ...io/iteratee/internal were created. more
11 files (not in diff) in ...in/scala/io/iteratee were created. more
1 files (not in diff) in ...travisbrown/iteratee were created. more
3 files (not in diff) in ...in/scala/io/iteratee were modified. more

Misses -1
Hits +1

[][cc-pull]

Powered by Codecov. Last updated by 0831812
[cc-base-branch]: https://codecov.io/gh/travisbrown/iteratee/branch/master?src=pr
[cc-pull]: https://codecov.io/gh/travisbrown/iteratee/pull/81?src=pr


[HUDI-2369] Blog on bulk_insert sort modes

What is the purpose of the pull request
Blog on bulk_insert sort modes
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

I have addressed the feedback.

@vinothchandar : this patch is also good to review. updated based on our discussion.

Thank you for writing this blog @nsivabalan . Quite useful! :)


Specify min windows version as Vista for Python

This should fix the C++ build issue.  It can be changed separately.

Awesome! Thanks for looking into this!

[trickle] No significant performance differences

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[microbenchmarks] No significant performance differences

Issues
#12747
#12428


Ensure that measures can be associated to more than one sensor_type

It is possible to specify sensor measures at the same time as defining a new sensor type.   However, if a new sensor type reuses an existing measure, we need to make sure that it is associated with it, i.e. /sensor/list_sensor_types  should have all sensor types with all their associated measures...

I'm pretty confident this now works as intended, but needs to be checked thoroughly still before this can be closed.


GCC choice

Made GCC version dependency clear in INSTALL and README
Added simple GCC version check to Makefile, triggered when compiling on Linux
Made default GCC/GCC_MAC choice overrideable by user through use of environment variable

Just to add to this: using GCC 4.4.7 we run into at least two problems
cc1plus: error: unrecognized command line option "-std=c++11"

which could be addressed in versions >-=4.3 and <=4.7 as described here http://stackoverflow.com/questions/14674597/cc1plus-error-unrecognized-command-line-option-std-c11-with-g
and we also get
g++: unrecognized option '-static-libstdc++'

which requires at least GCC 4.5, see http://stackoverflow.com/questions/16017959/g-unrecognized-option-static-libstdc
Easiest is to require 4.7. Pull request prints warning if GCC < 4.7


Add License

Could we add a license file?
License model could be
https://www.apache.org/licenses/LICENSE-2.0

Added license with the commit https://github.com/wacken89/hetzner-load-balancer-prometheus-exporter/commit/42ff7111989cae7dc9633cfa3a6155ea126673e5


SWIFT_VERSION not set correctly for Cocoapods

Using Xcode 8.2 when building my targets I get the following issue on OHTTPStubs:
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.

That's an issue on CocoaPods, not on OHHTTPStubs.
Basically, what CocoaPods does when you run pod install is that it uses the value of SWIFT_VERSION you have set on your own app project and set the same SWIFT_VERSION value for the Pods.xcodeproj targets.
So be sure to have set the right SWIFT_VERSION on your host project before running pod install (that's true for any Swift pod, not just OHHTTPStubs)
If the problem persists and you still have at least one target in the Pods.xcodeproj that doesn't have its SWIFT_VERSION build setting set, hence generating that Xcode prompt you're talking about:

Ensure that you use the latest CocoaPods version
Try to comment the line of the pod in your Podfile, run pod install (so it uninstalls the pod from your project), uncomment the pod line in your Podfile and run pod install again. This will force CocoaPods to regenerate the target for this pod in its Pods.xcodeproj. That's because if the SWIFT_VERSION wasn't set at the time of the first pod install or have changed since then, sometimes CocoaPods doesn't realize that the Pod target should change and leaves the pod target untouched.

If you still have an issue after all that, please file a bug on the CocoaPods repository, as it's an issue more related to CocoaPods not properly configuring the Pods project rather than specific to OHHTTPStubs itself.

It's aThis is confirmed with a lot of feedback from Twitter, Slack and the Dev forums, it's actually a regression also coming from Xcode 8.2, because Xcode 8.2 set back the SWIFT_VERSION to 3.0 but the "Use Legacy Swift Version" corresponding human readable settings in the Xcode GUI shows No for both values.
Th solution is to force-change the "Use Legacy Swift Version" for example by changing it to YES then back to NO again, to force Xcode to re-set it.
See also:

https://twitter.com/arekholko/status/809120209491623936
Confirmed here by an Apple engineer working on Xcode

Closing this bug, as it has nothing to do with OHHTTPStubs.

I'm sorry, mistook :bow:

Hi @AliSoftware thanks for the feedback. I noticed the same thing but forgot to follow up here. I think it can also help to have the .swift-version file which might prevent this situation if Apple decides to cause this problem again.
See:
https://github.com/Alamofire/Alamofire/blob/master/.swift-version

Might be a good idea, but not sure that .swift-version would change anything. This file is used by CocoaPods to know which Swift version to lint & push your pod against, but doesn't affect the pod installation process.
See our Blog Post here:

In CocoaPods 1.1.0, setting the version of Swift when linting and pushing your pod is supported in following ways:
[…]

It uses the setting from your .swift-version file if present (inspired by swiftenv).

pod install always use the same SWIFT_VERSION that is set on your application target when installing and generating the Pods target, and doesn't use .swift-version; .swift-version is only used during pod lib lint / pod spec lint and pod trunk push / pod repo push


Should cabal file be included in source control?

I noted in the README you mention that it would be nice to not have to include generated code in git for this repo (but it seems unavoidable at this point). I'm wondering if the same can be said for the .cabal file which seems to be generated from package.yaml.
Here's my thinking: this project isn't a complete mapping of cloudformation resources yet. As a user, I'm happy to add those and submit a PR and wait for a release, but in the interim I typically vendor the project via git submodule into mine, set to point at my patched version. If I'm in a stack project it seems like everything "just works" (no surprise) and the cabal file gets generated on project build. However, on regular cabal projects, I can't build this project as a dependency because the cabal file isn't generated, so I would either have to manually go in and generate the cabal file when its updated or I'd have to clone the project elsewhere, build it, build an sdist and then unpack that into my project on every change.
I do see the problem with committing the .cabal file as they could go out of sync. I'm not positive committing it is the best solution but given that this project is especially prone to users vendoring it, its worth considering the workflow for non stack-ready projects.

Good point. Is it possible for you to run hpack manually as part of some build process? That would generate the .cabal file for you.
You're right that the only real danger is them getting out of sync. Maybe I could add a CI command to ensure that the committed .cabal file matches the one generated by hpack.

Yeah a build process would probably be reasonable. The trick there is you need to get used to going from funnelling all your dev tasks through cabal to a higher level tool (like shake, for example) that will run the project build tasks for you and create any necessary files. Its mainly a question of inertia, but its probably the right thing to do.

The "build process" could be as simple as a shell script that first runs hpack, and then runs cabal. hpack is very quick, so I don't think you need something like shake.

Yeah, I was mostly speaking of my case: I already have other assets I have to build like javascript stuff that is a more compelling argument for shake. Hooking something like shake into the cabal build (which you can do) is way more painful and sketchy than inverting that and hooking the cabal build into the build tool (be it shake or a shell script).

Sounds good. I'll close this then. Let me know if it's super painful still without the .cabal file.
The other solution is to keep stratosphere more up to date and not wait weeks for a release after a change :smile: I have no problem with making tiny, incremental releases, so feel free to badger me to make a release if we merge a PR.


CI: Remove duplicate test runs

Working on the dev failure now.
https://github.com/scikit-learn/scikit-learn/pull/10280 is the probable cause.
I can't reproduce locally yet.


Migrate the remaining TIBS tests to the new testing infrastructure that defines sources inline

With this PR in, there are only main files test remaining that still use the TIBS test infrastructure. These tests are currently disabled because of rebranch failures. I’d like to fix them first before migrating them, which I’ll do in another PR.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

Testing found a request ordering race condition that I’m fixing in https://github.com/apple/sourcekit-lsp/pull/920/commits/96a9a05b08f8917504eb495490a6b79578bd4ccb. If you could review that commit, I’d appreciate it.

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test Windows

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test Windows

@swift-ci Please test

@swift-ci Please test Windows


Patching common-files/package.json

What does this implement/fix? Explain your changes.
It changes the on-pull-request-master workflow to push common-files/package.json changes to the base branch when a change in this file is detected.
Does this close any currently open issues?
No
What commands can I run to test the change?
No, only after merging it is possible to verify the outcome.
Any other comments?
The option Read and write permissions on the Workflow section should be selected on the page https://github.com/EYBlockchain/nightfall_3/settings/actions.

Hi.
The package-lock.json file should also be updated for:

apps/challenger
apps/proposer
apps/synchrinizer
cli
nightfall-administrator
nightfall-client
nightfall-deployer
nightfall-optimist
zokrates-worker


Update benchmark implementations

Use the tokio runtime for sqlx/sea-orm as requested here: https://github.com/launchbadge/sqlx/issues/1481#issuecomment-947025316
Update quaint to a version that uses tokio 1.0 and reenable it in the
metrics job

cc @billy1624 and @abonander

Thanks!! @weiznich

Thanks for incorporating my feedback! It looks like it actually was a pretty good improvement for SQLx across the board. The SQLite driver is still abysmally slow of course but that's something I've actually been working on over the last couple weeks.

@abonander The plots for sqlite are from the results from august, as the current sqlx version segfault while running the benchmarks.:
Benchmarking bench_insert/sqlx/1
Benchmarking bench_insert/sqlx/1: Warming up for 3.0000 s
error: process didn't exit successfully: `/home/runner/work/diesel/diesel/diesel_bench/target/release/deps/benchmarks-6af3c2993455c1b2 --bench` (signal: 11, SIGSEGV: invalid memory reference)

Do you want me to fill an issue for that in the SQLx issue tracker?

Don't worry about it, that's part of what I've been working on.


Postpone masternode expiry/removal on node start

This should preserve all non-spent mns loaded from cache in mn list on node start if this node was offline longer than an hour. All active mns should be able to send pings in MASTERNODE_MIN_MNP_SECONDS interval since node start (masternode list sync) saving their place in the list, all inactive will expire/be marked for removal after this interval expires as usual.
This should help to further lower cpu/bandwith usage and sync time for such nodes by avoiding full mn list re-sync on every start.

utACK

That was included in #1066, closing


style fixups

:+1:

this is an unnecessary risk.

Hi Scott, is there something that I can do to make this less risky?
I can open this up as several PRs (less commits in each one)

you can phone me if you want to talk about it.


Add comment pagination

Closes #527

Replace "Load more comments" with "More" (due to available translations)

Other than that, I only noticed a few minor issues. Fix them if they are easy, otherwise let's create issues and defer them to later:

When you press "Load more comments", add an anchor to the newest revealed comment (so you don't have to scroll down the entire page)?
When you reply to a comment that's only gets revealed after pressing "Load more comments", you won't see your comment (nor the comment you replied to) after replying until you press "Load more comments" again
You display 5 root level comments, regardless of how many children they have, so even the first page could contain a lot of comments.

When you press "Load more comments", add an anchor to the newest revealed comment (so you don't have to scroll down the entire page)?

I think it's better if we add a new issue for the first issue.

When you reply to a comment that's only gets revealed after pressing "Load more comments", you won't see your comment (nor the comment you replied to) after replying until you press "Load more comments" again

Fixing the second issue

You display 5 root level comments, regardless of how many children they have, so even the first page could contain a lot of comments.
What do you suggest for the third point?


Support Vivado design flow without a host runtime

Is it currently possible to package and export Xilinx IP from TAPA C++ source to be used in Vivado? Would Vitis HLS commands
csynth_design
export_design -format ip_catalog

work?
I cannot use XRT or libfrt-dev on my system. The former doesn't work with my kernel, and the latter conflicts with the CUDA installation. I'm following a simpler Vivado design flow in which I use IP cores made with Vitis HLS that have AXI Stream input-output interfaces. Communication with the card is via Xilinx DMA driver character devices. If this is possible with TAPA then it could be a drop-in replacement for Vitis HLS libraries.

Hi @vkomenda,
Thanks for your interests to our project! Currently, TAPA only generates .xo files for the Vitis flow. We do keep all the RTL files in the --work-dir (if you specify one), so it's not hard to generate Vivado IP blocks out of those files. I'll add this to our to-do list. Meanwhile, since we don't actually use the Vivado flow ourselves, it'll be good if you could provide some template simulation scripts so that we can verify if it works.

Thanks a lot for your reply, @Blaok! Compiling to RTL will take some time since I haven't managed to finish installing TAPA yet on my system with CUDA. Do you think it might be technically possible to compile (parts of?) TAPA from source without the XRT dependency and making it depend on NVidia OpenCL libraries instead of ocl-icd-libopencl1? Both XRT and FRT depend on that latter library, which conflicts with CUDA.

Hi @vkomenda , regarding the Vivado IP flow: the easiest way is to generate RTL using TAPA, then separately create a Vivado project and pack the RTL into an IP.

Thanks a lot for your reply, @Blaok! Compiling to RTL will take some time since I haven't managed to finish installing TAPA yet on my system with CUDA. Do you think it might be technically possible to compile (parts of?) TAPA from source without the XRT dependency and making it depend on NVidia OpenCL libraries instead of ocl-icd-libopencl1? Both XRT and FRT depend on that latter library, which conflicts with CUDA.

@vkomenda I see. TAPA does not depend on XRT or OpenCL directly, so you don't actually need to compile TAPA from source. FRT does recommend XRT, but it can work without it, so it's safe to remove or block XRT. I guess the tricky thing is that FRT does depend on OpenCL. I tagged a new FRT release (0.0.20220316.1) that depends on a virtual package opencl-dev instead of ocl-icd-opencl-dev, which should fix the compatibility issue with CUDA's OpenCL. Could you try again?

Thanks. On my system opencl-dev is provided only by ocl-icd-opencl-dev. The CUDA version of the conflicting package is called nvidia-libopencl1 which provides libopencl1:
$ sudo apt-file list nvidia-libopencl1
nvidia-libopencl1: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1
nvidia-libopencl1: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0.0
nvidia-libopencl1: /usr/share/bug/nvidia-libopencl1/control
nvidia-libopencl1: /usr/share/bug/nvidia-libopencl1/script
nvidia-libopencl1: /usr/share/doc/nvidia-libopencl1/changelog.Debian.gz
nvidia-libopencl1: /usr/share/doc/nvidia-libopencl1/changelog.gz
nvidia-libopencl1: /usr/share/doc/nvidia-libopencl1/copyright
nvidia-libopencl1: /usr/share/lintian/overrides/nvidia-libopencl1

So this is a conflict at a deeper level.
I can install older versions of libfrt from 2020. However corresponding tapa versions require older clang, which would require older GCC and would be a real pickle to install.

The CUDA version of the conflicting package is called nvidia-libopencl1 which provides libopencl1:

@vkomenda Cool, I made libfrt-dev depend on libopencl1 instead. Can you try 0.0.20220317.1?

That solved the XRT missing symbols, thanks! Now we have the mismatch of libboost_context.so. TAPA is linked against 1.65.1 and my system has only one installation candidate, 1.74.0. The mismatch came undetected by the package manager because it installed the meta-package libboost-context-dev as requested.

@vkomenda Boost libraries are not well known for compatibility :) We try to solve this problem by building binary packages for each supported distribution and release. Currently, our build pipeline only builds binary packages for current Ubuntu LTS releases (18.04 and 20.04). Which Linux distribution and release are you using? We can see if current Debian releases can be included in the future. Ubuntu 22.04 will be added when it is officially released and added to GitHub actions.
For now, you can see if changing -ltapa to -l:libtapa.a helps. This would force linking against the static library. If the boost library did not introduce breaking ABI changes for that symbol, you should be able to build it. Note that you'll need to manually specifiy the indirect dependencies, like -lboost_context. Otherwise, you'll need to build tapa from source. You don't have to build everything; building the tapa_shared or tapa_static target should be sufficient. You can overwrite the installed libtapa.so with the one built from source.

Thanks for the advice. It does look like I need to compile from source. There further errors.
$ g++ -o vadd -O2 vadd.cpp vadd-host.cpp -l:libtapa.a -lfrt -lglog -lgflags -lOpenCL -lpthread -ldl
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libtapa.a(tapa.cpp.o): in function `std::__cxx11::_List_base<tapa::internal::(anonymous namespace)::worker, std::allocator<tapa::internal::(anonymous namespace)::worker> >::_M_clear()':
tapa.cpp:(.text+0x9f8): undefined reference to `ontop_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0xa99): undefined reference to `ontop_fcontext'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libtapa.a(tapa.cpp.o): in function `void boost::context::detail::context_entry<boost::context::detail::record<boost::context::continuation, boost::context::basic_fixedsize_stack<boost::context::stack_traits>, boost::coroutines2::detail::push_coroutine<void>::control_block::control_block<boost::context::basic_fixedsize_stack<boost::context::stack_traits>, tapa::internal::(anonymous namespace)::worker::worker()::{lambda()#1}::operator()() const::{lambda(boost::coroutines2::detail::pull_coroutine<void>&)#2}&>(boost::context::preallocated, boost::context::basic_fixedsize_stack<boost::context::stack_traits>, tapa::internal::(anonymous namespace)::worker::worker()::{lambda()#1}::operator()() const::{lambda(boost::coroutines2::detail::pull_coroutine<void>&)#2}&)::{lambda(boost::context::continuation&&)#1}> >(boost::context::detail::transfer_t)':
tapa.cpp:(.text+0x111a): undefined reference to `jump_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x116a): undefined reference to `jump_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x12c5): undefined reference to `jump_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x1303): undefined reference to `ontop_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x136b): undefined reference to `ontop_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x13e3): undefined reference to `ontop_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x13fa): undefined reference to `ontop_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x1415): undefined reference to `ontop_fcontext'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libtapa.a(tapa.cpp.o):tapa.cpp:(.text+0x149c): more undefined references to `ontop_fcontext' follow
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libtapa.a(tapa.cpp.o): in function `tapa::internal::yield(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
tapa.cpp:(.text+0x16a8): undefined reference to `jump_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x187a): undefined reference to `ontop_fcontext'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libtapa.a(tapa.cpp.o): in function `std::thread::_State_impl<std::thread::_Invoker<std::tuple<tapa::internal::(anonymous namespace)::worker::worker()::{lambda()#1}> > >::_M_run()':
tapa.cpp:(.text+0x1df3): undefined reference to `make_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x1dfe): undefined reference to `jump_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x1e08): undefined reference to `jump_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x2067): undefined reference to `jump_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x2144): undefined reference to `ontop_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x2252): undefined reference to `ontop_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x22d1): undefined reference to `ontop_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x2354): undefined reference to `ontop_fcontext'
/usr/bin/ld: tapa.cpp:(.text+0x251d): undefined reference to `ontop_fcontext'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libtapa.a(tapa.cpp.o):tapa.cpp:(.text._ZNSt10_HashtableIbSt4pairIKbNSt7__cxx114listIN5boost11coroutines26detail14push_coroutineIvEESaIS8_EEEESaISB_ENSt8__detail10_Select1stESt8equal_toIbESt4hashIbENSD_18_Mod_range_hashingENSD_20_Default_ranged_hashENSD_20_Prime_rehash_policyENSD_17_Hashtable_traitsILb0ELb0ELb1EEEED2Ev[_ZNSt10_HashtableIbSt4pairIKbNSt7__cxx114listIN5boost11coroutines26detail14push_coroutineIvEESaIS8_EEEESaISB_ENSt8__detail10_Select1stESt8equal_toIbESt4hashIbENSD_18_Mod_range_hashingENSD_20_Default_ranged_hashENSD_20_Prime_rehash_policyENSD_17_Hashtable_traitsILb0ELb0ELb1EEEED5Ev]+0x99): more undefined references to `ontop_fcontext' follow
collect2: error: ld returned 1 exit status

@vkomenda You'll need to manually specify the indirect dependencies, like -lboost_context.

Also, XRT is not a build dependency for TAPA. You don't need XRT to build TAPA.

@vkomenda You'll need to manually specify the indirect dependencies, like -lboost_context.

I missed that, thanks. Adding that library works:
g++ -o vadd -O2 vadd.cpp vadd-host.cpp -l:libtapa.a -lfrt -lglog -lgflags -lOpenCL -lpthread -ldl -lboost_context
I've only tried running HLS for the Varium C1100 platform, and that doesn't finish correctly:
$ export PLATFORM=xilinx_u55n_gen3x4_xdma_1_202110_1

$ tapac -o vadd.$PLATFORM.hw.xo vadd.cpp --platform ~/Xilinx/platforms/$PLATFORM --top VecAdd --work-dir vadd.$PLATFORM.hw.xo.tapa
I0321 13:53:33.110 tapa.tapac:238] logging level set to INFO
I0321 13:53:33.693 tapa.core:163] extracting HLS C++ files
I0321 13:53:33.709 tapa.core:179] running HLS
I0321 13:53:41.527 tapa.core:214] extracting RTL files
I0321 13:53:41.545 tapa.core:237] writing basic auxiliary RTL files
I0321 13:53:41.547 tapa.core:257] parsing RTL files and populating tasks
I0321 13:53:42.218 tapa.core:274] instrumenting upper-level RTL
I0321 13:53:42.218 tapa.core:346] instrumenting top-level RTL
Traceback (most recent call last):
  File "/home/vk/.local/bin/tapac", line 33, in <module>
    sys.exit(load_entry_point('tapa', 'console_scripts', 'tapac')())
  File "/home/vk/src/blaok/tapa/backend/python/tapa/tapac.py", line 417, in main
    program.instrument_rtl(
  File "/home/vk/src/blaok/tapa/backend/python/tapa/core.py", line 347, in instrument_rtl
    self._instrument_task(self.top_task)
  File "/home/vk/src/blaok/tapa/backend/python/tapa/core.py", line 865, in _instrument_task
    self._connect_fifos(task)
  File "/home/vk/src/blaok/tapa/backend/python/tapa/core.py", line 482, in _connect_fifos
    wire_width = self.get_task(task_name).module.get_port_of(
  File "/home/vk/src/blaok/tapa/backend/python/tapa/verilog/xilinx/module.py", line 194, in get_port_of
    raise ValueError(f'module {self.name} does not have port {fifo}.{suffix}')
ValueError: module Add does not have port a._dout

Does this mean that the HDL in vadd.$PLATFORM.hw.xo.tapa may be incorrect? Or is it enough to be converted to a Vivado IP package, in your opinion?

vadd.xilinx_u55n_gen3x4_xdma_1_202110_1.hw.xo.tapa.zip

Hi @vkomenda, which HLS version are you using? I found that your HLS version has changed the format of the output RTL, which causes this bug. We need to add something to specifically handle this HLS version. Thanks!

Hi Licheng. I'm using vitis_hls version 2021.2.
On Mon, 21 Mar 2022, 18:21 Licheng Guo, @.***> wrote:

Hi @vkomenda https://github.com/vkomenda, which HLS version are you
using? I found that your HLS version has changed the format of the output
RTL, which causes this bug. We need to add something to specifically handle
this HLS version. Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/Blaok/tapa/issues/6#issuecomment-1074259612, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKF7IMIUE2ZSPSVEMOJ2CLVBC4ZTANCNFSM5QQJ5EJA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Supporting the latest Vitis versions is an ongoing effort. We have finished testing for 2021.1. 2021.2 should be able to work without too much trouble, too, but the testing is still not finished yet. I expect to tag a new release with support for 2021.1 and 2021.2 by the end of this week.

@vkomenda FYI I tagged 0.0.20220327.1 which supports 2021.2.

The same step fails, although with different errors. There is an additional compile warning. After upgrading TAPA and its Python backend:
$ g++ -o vadd -O2 vadd.cpp vadd-host.cpp -l:libtapa.a -lfrt -lglog -lgflags -lOpenCL -lpthread -ldl -lboost_context
/usr/bin/ld: warning: libglog.so.0, needed by /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libfrt.so, may conflict with libglog.so.1

$ tapac -o vadd.$PLATFORM.hw.xo vadd.cpp --platform ~/Xilinx/platforms/$PLATFORM --top VecAdd --work-dir vadd.$PLATFORM.hw.xo.tapa
Traceback (most recent call last):
  File "/home/vk/.local/bin/tapac", line 33, in <module>
    sys.exit(load_entry_point('tapa', 'console_scripts', 'tapac')())
  File "/home/vk/.local/bin/tapac", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 86, in load
    module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/home/vk/src/blaok/tapa/backend/python/tapa/tapac.py", line 17, in <module>
    import tapa.core
  File "/home/vk/src/blaok/tapa/backend/python/tapa/core.py", line 22, in <module>
    from tapa.floorplan import get_floorplan
  File "/home/vk/src/blaok/tapa/backend/python/tapa/floorplan.py", line 17, in <module>
    from autobridge.main import annotate_floorplan
ModuleNotFoundError: No module named 'autobridge.main'

The simulation host executable doesn't work though.
$ ./vadd --bitstream=vadd.$PLATFORM.hw_emu.xclbin 1000
ERROR: something wrong with flag 'logtostderr' in file './src/logging.cc'.  One possibility: file './src/logging.cc' is being linked both statically and dynamically into this executable.

The simulation host executable doesn't work though.

@vkomenda This warning message is very suspicious. You should be linking against libglog.so.0, not libglog.so.1. Their ABIs are probably incompatible.

/usr/bin/ld: warning: libglog.so.0, needed by /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libfrt.so, may conflict with libglog.so.1

A separate issue is, xclbin won't work without XRT. You may need to use the latest XO cosim feature (yet to be documented), which does not rely on XRT or OpenCL. You can try to replace vadd.$PLATFORM.hw_emu.xclbin with the .xo file to use it.

I made a correction to link against libglog.so.0:
$ g++ -o vadd -O2 vadd.cpp vadd-host.cpp -l:libtapa.a -lfrt -l:libglog.so.0 -lgflags -lOpenCL -lpthread -ldl -lboost_context

The warning is gone. I also have different simulation errors.
$ ./vadd --bitstream=vadd.$PLATFORM.hw_emu.xclbin 1000
INFO: Loading vadd.xilinx_u55n_gen3x4_xdma_1_202110_1.hw_emu.xclbin
terminate called after throwing an instance of 'std::runtime_error'
  what():  unexpected bitstream file
Aborted

$ ./vadd --bitstream=vadd.$PLATFORM.hw.xo 1000
INFO: Loading vadd.xilinx_u55n_gen3x4_xdma_1_202110_1.hw.xo
/usr/bin/python3: Error while finding module specification for 'tapa_fast_cosim.main' (ModuleNotFoundError: No module named 'tapa_fast_cosim')
WARNING: Logging before InitGoogleLogging() is written to STDERR
F0329 12:15:23.908768 13148 tapa_fast_cosim_device.cpp:176] TAPA fast cosim failed
*** Check failure stack trace: ***
Aborted

A separate issue is, xclbin won't work without XRT. You may need to use the latest XO cosim feature (yet to be documented), which does not rely on XRT or OpenCL. You can try to replace vadd.$PLATFORM.hw_emu.xclbin with the .xo file to use it.

Is it possible to go without the cosim feature? I cannot install XRT due to its conflict with the NVidia OpenCL libs.

Can you try
git clone https://github.com/UCLA-VAST/tapa-fast-cosim.git
python3 -m pip install --editable tapa_fast_cosim

and then re-run cosim with the xo object?

This looks promising! The part number is incorrect though. Could this be the reason for these failures?
$ ./vadd --bitstream=vadd.$PLATFORM.hw.xo 1000
INFO: Loading vadd.xilinx_u55n_gen3x4_xdma_1_202110_1.hw.xo
rm: cannot remove '/tmp/tapa-fast-cosim.ZJ7Cpw/output/*.bin': No such file or directory
WARNING:root:Waveform is not saved. Use --save_waveform to save the simulation waveform.
INFO:root:Vivado command: cd /tmp/tapa-fast-cosim.ZJ7Cpw/output/run/; vivado -mode batch -source run_cosim.tcl  | grep -v DEBUG
INFO:root:Starting Vivado...

****** Vivado v2021.2 (64-bit)
  **** SW Build 3367213 on Tue Oct 19 02:47:39 MDT 2021
  **** IP Build 3369179 on Thu Oct 21 08:25:16 MDT 2021
    ** Copyright 1986-2021 Xilinx, Inc. All Rights Reserved.

source run_cosim.tcl
# create_project -force tapa-fast-cosim ./vivado -part xc7vx485tffg1157-1
# set ORIG_RTL_PATH "/tmp/tapa_fast_cosim_1000//ip_repo/haoda_xrtl_VecAdd_1_0/src"
# set rtl_files [glob -nocomplain ${ORIG_RTL_PATH}/*.v]
# if {$rtl_files ne ""} {add_files -norecurse -scan_for_includes ${rtl_files} }
# set rtl_files [glob -nocomplain ${ORIG_RTL_PATH}/*/*.v]
# if {$rtl_files ne ""} {add_files -norecurse -scan_for_includes ${rtl_files} }
# set rtl_files [glob -nocomplain ${ORIG_RTL_PATH}/*.sv]
# if {$rtl_files ne ""} {add_files -norecurse -scan_for_includes ${rtl_files} }
# set rtl_files [glob -nocomplain ${ORIG_RTL_PATH}/*/*.sv]
# if {$rtl_files ne ""} {add_files -norecurse -scan_for_includes ${rtl_files} }
wrong # args: should be "glob ?switches? name ?name ...?"
    while executing
"glob -nocomplain "
    invoked from within
"set tcl_files [glob -nocomplain ]"
    (file "run_cosim.tcl" line 11)
INFO: [Common 17-206] Exiting Vivado at Tue Mar 29 17:31:01 2022...
elapsed time: 20.9826 s
expected: 3, actual: 0
expected: 6, actual: 0
expected: 9, actual: 0
expected: 12, actual: 0
expected: 15, actual: 0
expected: 18, actual: 0
expected: 21, actual: 0
expected: 24, actual: 0
expected: 27, actual: 0
expected: 30, actual: 0
... (+989 more errors)
FAIL!

Could you share your xo file?

vadd.xilinx_u55n_gen3x4_xdma_1_202110_1.hw.xo.zip

Fixed. Could you git pull and try again?

Fixed another issue. Could you pull again?

Fixed another issue. Could you pull again?

Which repository should I pull? There are no new commits in this one in main.

Sorry, having commuted the update to another repo. Now the repos are synced
and you should be able to pull.
On Wed, Mar 30, 2022 at 8:44 AM Vladimir Komendantskiy <
@.***> wrote:

Fixed another issue. Could you pull again?
Which repository should I pull? There are no new commits in this one in
main.
—
Reply to this email directly, view it on GitHub
https://github.com/Blaok/tapa/issues/6#issuecomment-1083309135, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHXOD27MGSE6V5BWKTWMTILVCRZHFANCNFSM5QQJ5EJA
.
 Otherwise the latest change may not
be reflected?
On Wed, Mar 30, 2022 at 9:00 AM Vladimir Komendantskiy <
@.***> wrote:

I switched the remote to @.***:UCLA-VAST/tapa.git. Installed the
python backend from the latest master. Recompiled. Got the same error.
—
Reply to this email directly, view it on GitHub
https://github.com/Blaok/tapa/issues/6#issuecomment-1083326514, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHXOD25CKB6K6PULAQ2PDTTVCR3CPANCNFSM5QQJ5EJA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Licheng-Guo sorry I didn't know you were referring to tapa-fast-cosim. I thought you were talking about this repo. I pulled your changes and the cosimulation passed!


Forward port of the LRU size fix

Forward port of https://github.com/grafana/beyla/pull/526

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (90ae223) 79.47% compared to head (c3226a3) 80.16%.

Files
Patch %
Lines

pkg/internal/export/otel/traces.go
25.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #539      +/-   ##
==========================================
+ Coverage   79.47%   80.16%   +0.69%
==========================================
  Files          69       69
  Lines        5778     5779       +1
==========================================
+ Hits         4592     4633      +41
+ Misses        967      924      -43
- Partials      219      222       +3

Flag
Coverage Δ

integration-test
69.07% <50.00%> (+0.95%)
:arrow_up:

unittests
45.14% <16.66%> (+0.02%)
:arrow_up:

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

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


In FA3, which specific Layout_K SW is used for smemO?

In FA3, which specific Layout_K SW is used for smemO?

Typically Layout_K_SW128


bugtool: deprecate flag k8s-mode

Historically, the bugtool has support for fetching system information from a Cilium Agent via Kubernetes API. In these cases, the bugtool is running outside of the agent and the flag k8s-mode=true is set.
Nowadays, Cilium CLI (e.g. cilium sysdump) is used to gather information from Cilium running in a K8s cluster. In this case, the bugtool is always running within the agent.
Therefore, this commit deprecates the flag k8s-mode (and it's related flags cilium-agent-container-name, k8s-namespace & k8s-label). It will be completely removed with Cilium 1.18.

/test


[3.0-Triple] Add health service cancel handler

What is the purpose of the change

Add health service cancel handler for release resource

Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #9004 (e17def6) into 3.0 (f561138) will decrease coverage by 0.22%.
The diff coverage is 7.14%.

@@             Coverage Diff              @@
##                3.0    #9004      +/-   ##
============================================
- Coverage     63.38%   63.16%   -0.23%
+ Complexity      314      313       -1
============================================
  Files          1186     1186
  Lines         50358    50369      +11
  Branches       7525     7505      -20
============================================
- Hits          31920    31814     -106
- Misses        14957    15061     +104
- Partials       3481     3494      +13

Impacted Files
Coverage Δ

.../dubbo/rpc/protocol/tri/service/TriHealthImpl.java
27.02% <7.14%> (-6.31%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
62.06% <0.00%> (-27.59%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
46.15% <0.00%> (-15.39%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
75.00% <0.00%> (-12.50%)
:arrow_down:

...in/java/org/apache/dubbo/common/utils/JVMUtil.java
81.13% <0.00%> (-11.33%)
:arrow_down:

.../remoting/transport/netty4/NettyServerHandler.java
58.13% <0.00%> (-9.31%)
:arrow_down:

.../common/threadpool/serial/SerializingExecutor.java
70.37% <0.00%> (-7.41%)
:arrow_down:

.../remoting/transport/netty4/NettyClientHandler.java
58.62% <0.00%> (-6.90%)
:arrow_down:

...e/dubbo/remoting/transport/netty4/NettyClient.java
68.05% <0.00%> (-5.56%)
:arrow_down:

... and 36 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 f561138...e17def6. Read the comment docs.


reduce cost-of-modules footprint

Move npm and typescript to devDependencies. Additionally, one apparently unused import is removed.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


 Received [ '/Users/lironshmuel/Workspace/hwmarket/app',
'/Users/lironshmuel/Workspace/hwmarket/test' ]
At path.js:7

TypeError: Path must be a string. Received [ '/Users/lironshmuel/Workspace/hwmarket/app',
  '/Users/lironshmuel/Workspace/hwmarket/test' ]
    at assertPath (path.js:7:11)
    at Object.join (path.js:1253:7)
    at /Users/lironshmuel/.atom/packages/autocomplete-modules/src/completion-provider.js:169:53
    at Array.map (native)
    at CompletionProvider.lookupWebpack (/Users/lironshmuel/.atom/packages/autocomplete-modules/src/completion-provider.js:168:42)
    at CompletionProvider.getSuggestions (/Users/lironshmuel/.atom/packages/autocomplete-modules/src/completion-provider.js:60:26)
    at /Users/lironshmuel/.atom/packages/autocomplete-plus/lib/autocomplete-manager.coffee:197:45
    at Array.forEach (native)
    at AutocompleteManager.module.exports.AutocompleteManager.getSuggestionsFromProviders (/Users/lironshmuel/.atom/packages/autocomplete-plus/lib/autocomplete-manager.coffee:177:15)
    at AutocompleteManager.getSuggestionsFromProviders (/Users/lironshmuel/.atom/packages/autocomplete-plus/lib/autocomplete-manager.coffee:1:1)
    at AutocompleteManager.module.exports.AutocompleteManager.findSuggestions (/Users/lironshmuel/.atom/packages/autocomplete-plus/lib/autocomplete-manager.coffee:171:6)
    at /Users/lironshmuel/.atom/packages/autocomplete-plus/lib/autocomplete-manager.coffee:1:1

Commands
     -0:36.4.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:33.6.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -0:33.6.0 core:cancel (atom-text-editor.editor.is-focused)
  4x -0:33.5.0 core:move-down (atom-text-editor.editor.is-focused)
     -0:32.3.0 core:cut (atom-text-editor.editor.is-focused)
     -0:32 core:backspace (atom-text-editor.editor.is-focused)
  2x -0:30.8.0 core:move-up (atom-text-editor.editor.is-focused)
  2x -0:30.2.0 core:move-down (atom-text-editor.editor.is-focused)
  3x -0:29.6.0 core:move-up (atom-text-editor.editor.is-focused)
     -0:28.1.0 core:move-down (atom-text-editor.editor.is-focused)
     -0:27.9.0 core:paste (atom-text-editor.editor.is-focused)
  2x -0:27.3.0 core:move-up (atom-text-editor.editor.is-focused)
     -0:26.5.0 editor:select-to-end-of-line (atom-text-editor.editor.is-focused)
  2x -0:23 core:move-down (atom-text-editor.editor.is-focused.autocomplete-active)
     -0:22.7.0 autocomplete-plus:confirm (atom-text-editor.editor.is-focused.autocomplete-active)
     -0:05.9.0 core:backspace (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "customFileTypes": {
      "source.ini": [
        ".buckconfig",
        ".flowconfig"
      ],
      "source.json": [
        ".arcconfig",
        "BUCK.autodeps"
      ],
      "source.python": [
        "BUCK"
      ]
    },
    "disabledPackages": [
      "git-difftool",
      "nuclide"
    ],
    "themes": [
      "nucleus-dark-ui",
      "atom-dark-fusion-syntax"
    ]
  },
  "autocomplete-modules": {
    "webpack": true
  }
}

Installed Packages
# User
advanced-open-file, v0.16.4 (inactive)
atom-beautify, v0.29.12 (active)
atom-dark-fusion-syntax, v1.2.4 (active)
atom-ternjs, v0.15.0 (active)
autocomplete-modules, v1.6.3 (active)
autocomplete-plus, v2.31.3 (active)
hyperclick, v0.0.38 (active)
js-hyperclick, v1.5.0 (active)
linter, v1.11.16 (active)
linter-eslint, v7.3.2 (active)
linter-jsonlint, v1.3.0 (active)
merge-conflicts, v1.4.4 (active)
nucleus-dark-ui, v0.9.5 (active)
nuclide, v0.168.0 (inactive)
pigments, v0.34.0 (active)
project-plus, v0.9.0 (active)
react, v0.16.0 (active)
split-diff, v1.0.4 (inactive)
Sublime-Style-Column-Selection, v1.7.2 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.5.0 (inactive)
one-light-ui, v1.5.0 (inactive)
one-dark-syntax, v1.3.0 (inactive)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.3 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.3 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.39.0 (active)
find-and-replace, v0.201.0 (active)
fuzzy-finder, v1.3.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.2 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v0.53.1 (active)
notifications, v0.65.0 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.100.2 (active)
timecop, v0.33.2 (active)
tree-view, v0.208.2 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

I believe this was resolved by #60.

@nkt can be closed as mentioned above.


ubuntu 11.04 ->  error enif_send: env==NULL on non-SMP VMAborted

on fresh ubuntu 11.04 (32bit) install
with erlang builded from source
http://www.erlang.org/download/otp_src_R14B04.tar.gz
tereska@DEV1104:~/dev/beamjs$ ./beamjs
enif_send: env==NULL on non-SMP VMAborted
strace -s 1024 ./beamjs
[...]
getcwd("/home/tereska/dev/beamjs", 8191) = 25
poll([{fd=15, events=POLLIN}], 1, 0)    = 1 ([{fd=15, revents=POLLIN}])
gettimeofday({1318069382, 66979}, NULL) = 0
gettimeofday({1318069382, 67097}, NULL) = 0
read(20, "\205\177\242/\226\346\373\363}\330\256\232BM\233\306", 16) = 16
gettid()                                = 13281
recv(15, "\0", 1, 0)                    = 1
poll([{fd=15, events=POLLIN}], 1, 0)    = 0 (Timeout)
send(18, "\0", 1, 0enif_send: env==NULL on non-SMP VM <unfinished ...>
+++ killed by SIGABRT +++
Aborted
what could be wrong?

You have to build erlang with SMP supported
2011/10/8 Sławomir Janecki
<EMAIL_ADDRESS>
on fresh ubuntu 11.04 install
tereska@DEV1104:~/dev/beamjs$ ./beamjs
enif_send: env==NULL on non-SMP VMAborted
strace -s 1024 ./beamjs
[...]
getcwd("/home/tereska/dev/beamjs", 8191) = 25
poll([{fd=15, events=POLLIN}], 1, 0)    = 1 ([{fd=15, revents=POLLIN}])
gettimeofday({1318069382, 66979}, NULL) = 0
gettimeofday({1318069382, 67097}, NULL) = 0
read(20, "\205\177\242/\226\346\373\363}\330\256\232BM\233\306", 16) = 16
gettid()                                = 13281
recv(15, "\0", 1, 0)                    = 1
poll([{fd=15, events=POLLIN}], 1, 0)    = 0 (Timeout)
send(18, "\0", 1, 0enif_send: env==NULL on non-SMP VM <unfinished ...>
+++ killed by SIGABRT +++
Aborted
what could be wrong?
--
Reply to this email directly or view it on GitHub:
https://github.com/beamjs/beamjs/issues/47

can you tell me one more thing... is there a way to run beamjs on one cpu core (with erlang ./configure --enable-smp-support)
i need to somehow pass the force SMP support to erl. (-smp [enable|auto|disable])

There is no way I know of to run beamjs on an erlang with disabled
SMP, because of enif_send function that it uses
2011/10/8 Sławomir Janecki
<EMAIL_ADDRESS>
can you tell me one more thing... is there a way to run beamjs on one cpu core (with erlang ./configure --enable-smp-support)
i need to somehow pass the force SMP support to erl. (-smp [enable|auto|disable])
--
Reply to this email directly or view it on GitHub:
https://github.com/beamjs/beamjs/issues/47#issuecomment-2333315

ok thanks


warn on ssr if routes doesnt exists

this PR send a warning to the user if she / he forget to set up routing with can-route

Closes #153


Added mobile responsiveness

Looking great!
just a small nit, on mobile the title page is missing:


Refactor the function getLatestRelease and add the correct error message

Proposed Changes

The func getLatestRelease returns spec.version, if spec.version is not available.
Add error message into the CR, if the manifest is not available.

/test pull-knative-operator-upgrade-tests

/test pull-knative-operator-upgrade-tests


Xcode 9, Provisioning Profiles in simplest possible case doesn't work despite following docs

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
bundle exec fast lane beta fails (message below). I have read every open issue on the problem. It seems to be an XCode 9 thing? Match appears to be working just fine, and my fastfile is very simple. I get the feeling I'm not writing something where I should be. I specified the provisioning profiles for release and debug in Xcode 9 in accordance with the docs.
Fastfile:
default_platform(:ios)

platform :ios do
  desc "Push a new beta build to TestFlight"
  lane :beta do
    ensure_git_status_clean
    increment_build_number(xcodeproj: "FastDeployPush.xcodeproj")
    commit_version_bump(xcodeproj: "FastDeployPush.xcodeproj")
    add_git_tag
    push_to_git_remote
    match(
      type: "appstore",
      git_url: "git@github.com:Rob117/m3prot_cert_test.git"
    )
    build_app(
      scheme: "FastDeployPush",
    )
    upload_to_testflight
  end
end

Complete output when running fastlane, including the stack trace and command used
installed via ruby gem
bundle exec fast lane beta
-- note -> The --capture_output command returns a rocket and a checkmark. :(

[18:24:25]: ▸ Running script 'Bundle React Native code and images'
[18:24:28]: ▸ the transform cache was reset.
[18:24:45]: ▸ Touching FastDeployPush.app
[18:24:45]: ▸ Signing /Users/r-sherling/Library/Developer/Xcode/DerivedData/FastDeployPush-cjefjkvkhdneficbpwhhfjrtkysp/Build/Intermediates.noindex/ArchiveIntermediates/FastDeployPush/InstallationBuildProductsLocation/Applications/FastDeployPush.app
[18:24:54]: ▸ Touching FastDeployPush.app.dSYM
[18:24:55]: ▸ Archive Succeeded
[18:24:55]: Generated plist file with the following values:
[18:24:55]: ▸ -----------------------------------------
[18:24:55]: ▸ {
[18:24:55]: ▸   "provisioningProfiles": {
[18:24:55]: ▸     "com.m3career.FastDeployPush": "match AppStore com.m3career.FastDeployPush"
[18:24:55]: ▸   },
[18:24:55]: ▸   "method": "app-store",
[18:24:55]: ▸   "signingStyle": "manual"
[18:24:55]: ▸ }
[18:24:55]: ▸ -----------------------------------------
[18:24:55]: $ /usr/bin/xcrun /Users/r-sherling/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/fastlane-2.95.0/gym/lib/assets/wrap_xcodebuild/xcbuild-safe.sh -exportArchive -exportOptionsPlist '/var/folders/n6/p2zt93fd67l_p0cyzvkllqnh0000gp/T/gym_config20180518-47071-hlg5k8.plist' -archivePath /Users/r-sherling/Library/Developer/Xcode/Archives/2018-05-18/FastDeployPush\ 2018-05-18\ 18.22.40.xcarchive -exportPath '/var/folders/n6/p2zt93fd67l_p0cyzvkllqnh0000gp/T/gym_output20180518-47071-rrqxfj'
rbenv detected, removing env variables
rbenv: no such command `shell'
+ xcodebuild -exportArchive -exportOptionsPlist /var/folders/n6/p2zt93fd67l_p0cyzvkllqnh0000gp/T/gym_config20180518-47071-hlg5k8.plist -archivePath '/Users/r-sherling/Library/Developer/Xcode/Archives/2018-05-18/FastDeployPush 2018-05-18 18.22.40.xcarchive' -exportPath /var/folders/n6/p2zt93fd67l_p0cyzvkllqnh0000gp/T/gym_output20180518-47071-rrqxfj
2018-05-18 18:24:55.939 xcodebuild[50011:2709699] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/n6/p2zt93fd67l_p0cyzvkllqnh0000gp/T/FastDeployPush_2018-05-18_18-24-55.938.xcdistributionlogs'.
2018-05-18 18:24:56.155 xcodebuild[50011:2709699] [MT] IDEDistribution: Step failed: : Error Domain=IDEDistributionSigningAssetStepErrorDomain Code=0 "Locating signing assets failed." UserInfo={NSLocalizedDescription=Locating signing assets failed., IDEDistributionSigningAssetStepUnderlyingErrors=(
"Error Domain=IDEProvisioningErrorDomain Code=9 \"\"FastDeployPush.app\" requires a provisioning profile.\" UserInfo={NSLocalizedDescription=\"FastDeployPush.app\" requires a provisioning profile., NSLocalizedRecoverySuggestion=Add a profile to the \"provisioningProfiles\" dictionary in your Export Options property list.}"
)}
error: exportArchive: "FastDeployPush.app" requires a provisioning profile.
Error Domain=IDEProvisioningErrorDomain Code=9 ""FastDeployPush.app" requires a provisioning profile." UserInfo={NSLocalizedDescription="FastDeployPush.app" requires a provisioning profile., NSLocalizedRecoverySuggestion=Add a profile to the "provisioningProfiles" dictionary in your Export Options property list.}
** EXPORT FAILED **
[18:24:56]: Exit status: 70
[18:24:56]: No provisioning profile provided
[18:24:56]: Make sure to pass a valid provisioning for each required target
[18:24:56]: Check out the docs on how to fix this: https://docs.fastlane.tools/actions/gym/#export-options
+---------------+-------------------------+
|            Build environment            |
+---------------+-------------------------+
| xcode_path    | /Applications/Xcode.app |
| gym_version   | 2.95.0                  |
| export_method | app-store               |
| sdk           | iPhoneOS11.2.sdk        |
+---------------+-------------------------+
[18:24:56]: ▸     cd /Users/r-sherling/test_projects/FastDeployPush/ios
[18:24:56]: ▸     export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/r-sherling/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/bin:/Users/r-sherling/.rbenv/versions/2.2.4/bin:/Users/r-sherling/homebrew/Cellar/rbenv/1.1.1/libexec:/Users/r-sherling/.rbenv/shims:/Users/r-sherling/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/munki:/Users/r-sherling/Library/Android/sdk/tools:/Users/r-sherling/Library/Android/sdk/platform-tools"
[18:24:56]: ▸     /usr/bin/touch -c /Users/r-sherling/Library/Developer/Xcode/DerivedData/FastDeployPush-cjefjkvkhdneficbpwhhfjrtkysp/Build/Intermediates.noindex/ArchiveIntermediates/FastDeployPush/BuildProductsPath/Release-iphoneos/FastDeployPush.app.dSYM
[18:24:56]: ▸ ** ARCHIVE SUCCEEDED **
[18:24:56]:
[18:24:56]: ⬆  Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error
[18:24:56]: 📋  For the complete and more detailed error log, check the full log at:
[18:24:56]: 📋  /Users/r-sherling/Library/Logs/gym/FastDeployPush-FastDeployPush.log
[18:24:56]:
[18:24:56]: Looks like fastlane ran into a build/archive error with your project
[18:24:56]: It's hard to tell what's causing the error, so we wrote some guides on how
[18:24:56]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[18:24:56]: Before submitting an issue on GitHub, please follow the guide above and make
[18:24:56]: sure your project is set up correctly.
[18:24:56]: fastlane uses xcodebuild commands to generate your binary, you can see the
[18:24:56]: the full commands printed out in yellow in the above log.
[18:24:56]: Make sure to inspect the output above, as usually you'll find more error information there
[18:24:56]:
+------------------------------------+--------------------------------------------------+
|                                     Lane Context                                      |
+------------------------------------+--------------------------------------------------+
| DEFAULT_PLATFORM                   | ios                                              |
| PLATFORM_NAME                      | ios                                              |
| LANE_NAME                          | ios beta                                         |
| GIT_REPO_WAS_CLEAN_ON_START        | true                                             |
| BUILD_NUMBER                       | 10                                               |
| SIGH_PROFILE_TYPE                  | app-store                                        |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"com.m3career.FastDeployPush"=>"match AppStore  |
|                                    | com.m3career.FastDeployPush"}                    |
+------------------------------------+--------------------------------------------------+
[18:24:56]: Error packaging up the application
+------+-------------------------+-------------+
|               fastlane summary               |
+------+-------------------------+-------------+
| Step | Action                  | Time (in s) |
+------+-------------------------+-------------+
| 1    | default_platform        | 0           |
| 2    | ensure_git_status_clean | 0           |
| 3    | increment_build_number  | 0           |
| 4    | commit_version_bump     | 0           |
| 5    | add_git_tag             | 0           |
| 6    | push_to_git_remote      | 8           |
| 7    | match                   | 22          |
| 💥   | build_app               | 143         |
+------+-------------------------+-------------+
[18:24:56]: fastlane finished with errors
[!] Error packaging up the application

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.6

Ruby
2.2.4

Bundler?
false

Git
git version 2.14.3 (Apple Git-98)

Installation Source
~/.rbenv/versions/2.2.4/bin/fastlane

Host
Mac OS X 10.12.6 (16G1212)

Ruby Lib Dir
~/.rbenv/versions/2.2.4/lib

OpenSSL Version
OpenSSL 1.0.2n  7 Dec 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
default_platform(:ios)

platform :ios do
  desc "Push a new beta build to TestFlight"
  lane :beta do
    ensure_git_status_clean
    increment_build_number(xcodeproj: "FastDeployPush.xcodeproj")
    commit_version_bump(xcodeproj: "FastDeployPush.xcodeproj")
    add_git_tag
    push_to_git_remote
    match(
      type: "appstore",
      git_url: "git@github.com:Rob117/STUFF"
    )
    build_app(
      scheme: "FastDeployPush",
    )
    upload_to_testflight
  end
end

`./fastlane/Appfile`
app_identifier("EMAIL") # The bundle identifier of your app
apple_id("EMAIL") # Your Apple email address

itc_team_id("STUFF") # iTunes Connect Team ID
team_id("STUFF") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.95.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.2

CFPropertyList
3.0.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.5

xcodeproj
1.5.9

rouge
2.0.7

xcpretty
0.2.8

terminal-notifier
1.8.0

unicode-display_width
1.3.2

terminal-table
1.8.0

plist
3.4.0

public_suffix
2.0.5

addressable
2.5.2

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.62.0

faraday
0.15.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.3

gh_inspector
1.1.3

mini_magick
4.5.1

multi_json
1.13.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.4.0

bundler
1.16.1

faraday_middleware
0.12.2

naturally
2.1.0

simctl
1.6.4

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.1

mime-types-data
3.2016.0521

mime-types
3.1

little-plugger
1.1.4

logging
2.2.2

jwt
2.1.0

memoist
0.16.0

os
0.9.6

signet
0.8.1

googleauth
0.6.2

httpclient
2.8.3

google-api-client
0.13.6

emoji_regex
0.1.1

json
2.1.0

generated on: 2018-05-18

@fastlane-bot yes, yes I have.

Solved with #12309


Update Backend Models to reflect new volunteer flow

New flow: User authenticates with Google, creates a User Profile (basic bio info), submits volunteer app.

[x] User Creds model created
[x] User Creds REST endpoints created
[ ] User Creds tests written
[x] User Data model created/update
[x] User Data REST endpoints created/update
[ ] User Data tests written
[x] Temporarily comment out all Event related endpoints

@nareddyt  can you confirm the status of the User Cred action items.

Just checked off the boxes above!
Currently all user data is in a model called User Data. I imagine you want to break it up into User Profile and Volunteer Application, correct?
Are there any pros/cons of doing so?

Hmmmmm, this was my initial reasoning because I was thinking that not every user (namely admins) would need to submit the volunteer app. Admins would just be instantly promoted to admin...
But I realize that if we did it that way, we'd need a separate UI to display these people before they're promoted to admin.... so it seems it's simpler to just force everyone to fill out the application and then people can be promoted to admin from the volunteer list page.
So in that case I don't see a reason to split it up!
Except maybe you consider that when the volunteer signs in we don't necessarily need all their application data to be sent to the frontend every time? The application data is only useful before they're approved?
Idk it seems I'm talking myself out of uniting them now... What are your thoughts?

I think the performance gains of not sending back that data would be minimal. If we split that data, then we'd have to make two DB calls and "join" them to retrieve a single user's data.
I agree that it would be inconvenient for Admins to have to input all that info for no reason. Like you said, you'd have to change the frontend. Do you think you'd have time to do that before the deadline?
Perhaps we could make this a low-priority feature and work on it if we have time towards the end? Do you think admin UX would be acceptable if we keep the model the same for now?

Updated UserData models/routes and frontend to be in sync.

Moved all Testing requirements to #179


Publish core module

The "core" module exposes the base helpers required to interact with publisher, app, and release NFTs.
One example of how this can be used will be the cli module. The core module is intended to operate in a web-based context, too.

https://www.npmjs.com/package/@solana-mobile/dapp-store-publishing-tools


Fix show-env subcommand bug

This fixes the problem that the readme example does not work.
This probably fixes the remaining problem reported in #115.
cc #93
cc @davidhewitt

bors r+


[TRI-1794] Digital Ocean self-hosting docs

A customer kindly provided this information when they got Trigger.dev working on Digital Ocean:

Everything is the exact same as fly except for needing to have your own dockerhub image (perhaps fixed in the future) and needing to set NODE_TLS_REJECT_UNAUTHORIZED='0'. Without that env var, you get the following error from graphile:

[2023-12-22 10:08:56] Error: self-signed certificate in certificate chain
[2023-12-22 10:08:56]     at TLSSocket.onConnectSecure (node:_tls_wrap:1600:34)
[2023-12-22 10:08:56]     at TLSSocket.emit (node:events:517:28)
[2023-12-22 10:08:56]     at TLSSocket._finishInit (node:_tls_wrap:1017:8)
[2023-12-22 10:08:56]     at ssl.onhandshakedone (node:_tls_wrap:803:12) {
[2023-12-22 10:08:56]   code: 'SELF_SIGNED_CERT_IN_CHAIN'
[2023-12-22 10:08:56] }

TRI-1794

I have same question for v3 projects, I am trying to host it locally with a self signed cert chain (local issuer for hardened security)
How do I add this to my tasks so that they trust my cert in fetch. Presumably they are going to be built into a container, can i add a step to add a custom cert?


Convert opencv's mat to tfgo's tensor

I'm using gocv to read an image from file and apply some preprocessing steps. The result of these steps is a variable of type gocv.Mat. Now I want to feed this image to my model using tfgo. However, when I try to create a new tensor, I get the error that it's an unsupported type. I'm wondering how one could convert a gocv.Mat variable to a tfgo.NewTensor?
Any help is much appreciated.

Hi, I'm not familiar with gocv, but I guess you just need a way to extract the raw byte representation from the gocv.Mat type, and create the new tensor. Be careful, that you want to extract not the RGB representation, but a compressed representation (e.g. the PNG image, thus the png headers + the png content).
Anyway, I do recommend to user the TensorFlow primitives instead of mixing gocv with tfgo.

Thanks. gocv is basically the OpenCV in Go. I have the following preprocessing steps using gocv in Go and cv2 in python. Doing these, the r_imgs in both cases are exactly the same. Do you think these steps are reproducible using tfgo?
img := gocv.IMRead(filename, gocv.IMReadColor)
defer img.Close()

c_img := gocv.NewMat()
defer c_img.Close()
gocv.CvtColor(img, &c_img, gocv.ColorBGRToRGB)

r_img := gocv.NewMat()
defer r_img.Close()
gocv.Resize(c_img, &r_img, image.Point{112, 112}, 0, 0, gocv.InterpolationLinear)

and the python equivalent:
img = cv2.imread(filename)
c_img = cv2.cvtColor(img, cv2.COLOR_BGR2RGB)
r_img = cv2.resize(c_img, (112, 112))

Yes, have a look at the example code in the README.
Using the "github.com/galeone/tfgo/image" package, you can read the image, resize it, get a tensor out of it, and save it

Great. Thanks for the help.

Using the Value() from the galeone/tfgo/image package, I'm getting the following error:
Cannot use 'r_img.Value()' (type tf.Output) as the type *tf.Tensor
This is how I feed the image to the model:
root := tg.NewRoot()
img := image.Read(root, filename, 3)
r_img := img.CropAndResize(image.Box{Start: image.Point{X: 0.0, Y: 0.0},
	End: image.Point{X: 1.0, Y: 1.0}},
	image.Size{Height: 112, Width: 112})

model := tg.LoadModel("./model_pb", []string{"serve"}, nil)

qmf_results := model.Exec([]tf.Output{
	model.Op("PartitionedCall", 0),
		}, map[tf.Output]*tf.Tensor{
	qmf_model.Op("serving_default_input.1", 0): r_img.Value(),
})

Hey @galeone :)
Any idea about the above error?

The Cannot use 'r_img.Value()' (type tf.Output) as the type *tf.Tensor has already been discussed in #27, so closing this one.


Download a portion of a video with embedded Youtube-dl

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.06.18. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.06.18

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

#############################################################################
Hello everybody,
I am trying to extract only a portion of a video thanks to embedded Youtube-dl.
I didn't find any option to do this. I have tried with this type of line:
" with youtube_dl.YoutubeDL(ydl_opts) as ydl:
ydl.download(['http://www.youtube.com/v/--4gqARaEJE?start=0&end=10']) "
but it doesn't seem to work.
Is something possible with the Youtube-dl library ?
Thanks in advance for your help !

Not possible.


Can't import pdftotext in my Mac Apple Silicon M1

Hi,
I changed my mac to the new Apple M1 Pro and now I can't import pdftotext in python, so I can't make my previous code work.
Are you experiencing the same problem?
I opened a question in stackexchange with details:
https://stackoverflow.com/questions/71371871/cant-import-pdftotext-in-python-in-my-mac-m1

How are you installing python, poppler, and pdftotext? I think most people use brew these days, in which case I believe everything works on M1 Macs, thanks to #86. But I don't have an M1 Mac to do any testing.

This is what I do:

Install python 3.10
Install command line developer tools
pip3 install pdftotext from terminal
Open IDLE, type import pdftotext
I get this error:
Traceback (most recent call last): File "<pyshell#9>", line 1, in import pdftotext ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/pdftotext.cpython-310-darwin.so, 0x0002): symbol not found in flat namespace '_ZN7poppler24set_debug_error_functionEPFvRKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEEPvES9'

I'm not super expert, and I don't understand the difference with using brew or not. With my previous mac I ended up with multiple versions of packages.  I'll try though

I have the same issue as well on an intel macbook

Folks, if you're going to post here at all, please post details that might help someone to help you. Or at least answer my questions when I ask for details about how you have installed each component.
As an example, if the question is "How are you installing python, poppler, and pdftotext?", then "I install python 3.10" is not really answering the question, is it?

Hi jalan,
Let me be more specific:
I installed python 3.10, by downloading it from the official page (https://www.python.org/downloads/) and just executing. Nothing more.   Mostly I use IDLE to develop.
I installed Command Line tools, from the apple store.
I don't use brew, that's why I mentioned I install pdftotext as "pip3 install pdftotext from terminal".
There is no more to it.  It just does not work.   Maybe with brew does, but I don't like that option.
I finally ended up using an alternative, Tika parser. Its output it's similar to pdftotext.
I'm not an advanced developer, so I cannot say anything more unless the question is more specific.  Maybe other M1 users with more experience have the same problem and can help.

I was able to to do it by upgrading my python to 3.10. I went to the link https://www.python.org/downloads/ and proceeded to install pdftotext using pip3 install pdftotext and it worked!

I don't think there's anything to fix here. See #100 for an example of everything working on an M1 Mac.