ElasticSearch Sink not keeping up

Hi, I'm trying to tune the configuration for large rates of log events but I can't seem to find a sweet spot were this sink would keep up. My current rate is at ~1.8k / 30 seconds (This might actually be the problem but I've already trimmed down and ideally I wouldn't have to trim the verbosity further).
After looking into the code I can see that only 1 instance can ship a single batch at a time.
https://github.com/serilog/serilog-sinks-elasticsearch/blob/dev/src/Serilog.Sinks.Elasticsearch/Sinks/ElasticSearch/ElasticSearchLogShipper.cs#L141
I understand why the bookmark was implemented like this but it seems like that's becoming a bottleneck.
My current config is the following
{...
              "bufferBaseFilename": "./Logs/elasticbuffer",

              // The maximum number of events to post in a single batch.
              // https://www.elastic.co/guide/en/elasticsearch/guide/current/bulk.html#_how_big_is_too_big
              // Assuming every event is ~400 bytes, 25000 events would equal ~10MB
              "batchPostingLimit": 25000, // Passed to PeriodicBatchingSink

              // The time (in seconds) to wait between checking for event batches.
              "period": 1, // Passed to PeriodicBatchingSink

              // The interval (in milliseconds) between checking the buffer files.
              "bufferLogShippingInterval": 100,

              "bufferFileSizeLimitBytes":<PHONE_NUMBER> // 2GB, Passed to RollingFile Sink
... }

Now obviously there are other bottlenecks that might be at play but can someone recommend the next step in improving my config / setup?

One option, not sure how palatable, is to just use non-durable shipping. It should easily sustain this rate, though of course there are trade-offs.
A (possibly hacky) option is to use Serilog.Sinks.Map to distribute events over several instances of the sink, using different buffer files. Writes to the buffer file are still going to be a problem at some point, but you might improve throughput a bit.
    // Spread events over five sinks/buffers
    .WriteTo.Map(le => le.Timestamp.Millisecond % 5,
        (ms, wt) => wt.Elasticsearch(..., "/Logs/elasticbuffer-{ms}"))

;-)

I've thought about removing durability all together as it will at least fix the keeping up issue, but I'me going to test out Map first.
Will let you know how it goes, thanks @nblumhardt :)

Map does not have good support with Serilog.Configuration thus I won't work for me. I'm going to switch off durable mode until I find a better way. The possibility of losing some logs is better than having none.
Thanks @nblumhardt for your help.


Add udev rules for Azure disks

Fixes: https://github.com/coreos/bugs/issues/2481
This change allows to use proper Azure disk paths in ignition.

The linked issue mentions AWS, too.  Does this also need to add 90-cloud-storage.rules?

If we pull in the aws rules we also need to pull in the helper script (which is fine). I'm fine taking this with or without the AWS fix (but leave the bug open if we don't include the AWS rules).

I didn't check if all the utilies needed by the AWS script are in the initramfs. I'd say we land this to unblock @r7vme and then we check if there other bits we should pull in too.

Okay, then I'll merge it as is.
@r7vme This also needs to be updated in the coreos-overlay repo to be included in the OS.  If you'd like to do it, the process is to take the latest commit ID in bootengine's master branch and update sys-kernel/bootengine in the overlay with it, then bump the symlink's version number.  See its Git log for details.


Request: Please consider not excluding ./scripts/build in .npmignore

It seems to me that this functionality should really be included in the npm package so that one can generate a custom, truly minified build of Ramda just using the npm package.

I'm curious as to why you feel that way.  I've always thought of NPM as supplying packages.  I would assume those who want to build custom versions would clone the project from GitHub.
Are there many projects delivered that way?

I'm curious as to why you feel that way

Sure.
We have a production build step that introspects our code to find all references to Ramda symbols and then generate a command line invocation of the Ramda build script to create the corresponding minimal build of Ramda which, is then bundled with the rest of our JS code.
This is in effect our sort of our poor-man tree-shaking step similar to what rollup / jspm / webpack 2 provide for code base that use ES2015 modules.
During development we just use the regular Ramda npm package and only generate the minimal build automatically for production builds of our apps.
Having the build script in the npm package would allow us to manage Ramda just like any other JS dependency.
You can imagine how much more cumbersome it is to use a git clone repository instead of the npm package to manage a JS dependency...

I've always thought of NPM as supplying packages. I would assume those who want to build custom versions would clone the project from GitHub.
Are there many projects delivered that way?

I don't know 😃.
I'm not aware of many package that have such as clean modular implementation and that also provide a clever build script enabling automatic tree-shaking.
On the other hand, with the advent of ES2015 modules, more packages are taking advantage of the pkg.module field to allow for automatic tree-shaking.
I would submit that this may be something worth considering for Ramda too.

I'm certainly willing to consider it.  I've never had a similar need, but of course, I generally have the Ramda source/build at hand.  I'm wondering what others think.
@buzzdecafe? @davidchambers? @raine?

It seems reasonable to include this file in the tarball. Given the huge number of dependencies most projects require, the prospect of adding a few kilobytes to the npm install ramda payload doesn't bother me.

Please disregard my request. I didn't realized that Ramda was implemented in such a way that I  could just require individual function (also someone already implemented a rollup plugin to essentially rewrites import {<foo>} from 'ramda' to  var  <foo> = require('ramda/src/<foo>' which fit exactly our original need.


FFmpegBuilder!!!

Hi! You in library in the class FFmpegBuilder, have such line:
args.add (" - v", "error");//TODO make configurable
Here take and transfer it a line, and better generally delete because in ffmpeg there is no such option! And because of this error it isn't written stry to the file because ffmpeg tries to understand that for an option such. When manually I take request which collected your class and I insert into the linux console and I clean parameter - v error, everything works.

sorry, I was mistaken, - v error is, but it very strongly hinders me, you couldn't correct as soon as possible it?

You are welcome to send a patch to make it configurable.

You are able to do it? It is very important as operability of my program depends on this library

This was fixed by 387c599be33b5af9d1b16f47fff5be06c2f1e4b0


Python writes source .../.venv/bin/activate to existing terminals

Have an remote SSH connection to a workspace where there's a Python .venv. Write some command you might want to run later in a terminal, but don't send it.
Disconnect and reconnect to the remote.
⚠ Python will automatically write source <path>/.venv/bin/activate to all existing terminals and submit it, resulting in the command being executed

This is a really sharp edge, I had this mess up a notable chunk of work on a remote machine because my unsent command was a destructive action 😞

There is a setting to disable activation in existing terminals.

I think we should still never write the 'activate' command to terminals on reconnection though to avoid others hitting this.


Display secondary parent first_name and last_name

_form.html.erb

    <%= form_for(@parent, :html => {class: "form-horizontal", role: "form"}) do |f| %>

    	<%= f.label :parent_1_firstname %>

        <%= f.text_field :parent_1_firstname, class: "form-control", placeholder: "Parent 1 first name",
      autofocus:true %>

             <%= f.label :parent_1_lastname %>

             <%= f.text_field :parent_1_lastname, class: "form-control", placeholder: "Parent 1 last name",
           autofocus:true %>

Add Secondary Parents or Guardians

        <%= f.fields_for :secondaryparents do |builder| %>
        <%= render 'secondaryparent_fields', :f => builder %>
        <% end %>
        <%= link_to_add_association 'Add Secondary Parent', f, :secondaryparents %>

      	<%= f.submit class: 'btn btn-primary btn-lg' %>

<% end %>

_secondaryparent_fields.html.erb

             <%= f.label :parent_first_name %>

             <%= f.text_field :parent_first_name, class: "form-control", placeholder: "Parent First Name",
             autofocus:true %>

             <%= f.label :parent_last_name %>

             <%= f.text_field :parent_last_name, class: "form-control", placeholder: "Parent Last Name",
            autofocus:true %>

        <%= link_to_remove_association "Remove Parent", f %>

show.html.erb

Family Information

Primary Parent or Guardian in the home

First Name: <%= @parent.parent_1_firstname %>

Last name:<%= @parent.parent_1_lastname %>

Secondary Parents or Guardians

First Name:<%= @secondaryparent.first_name %>

Last Name:<%= @secondaryparent.last_name %>

please help
How to display the secondary parent first name and last name?

I fixed your formatting.
I prefer if questions like this are asked on stackoverflow, where there are more people watching.
The question is completely unclear. In the show.html.erb you show the  parent and secondary parent, and that works? It does not work? How are @parent and @secondaryparent set in the controller? Or do you want to show the secondaryparents in the _form ?
How are the associations? I am guessing a family has parent_1 and has_many secondaryparents.
Should you not iterate over all @family.secondaryparents in the view, or are you only interested in the first? Like @secondaryparent= family.secondaryparents.first ?

there is parent table which includes the parent_1. there is a secondaryparent table which includes all the secondaryparent, if someone adds them in the _form. parent has_many association with secondary_parents. what I want is when someone ends the name of secondary parents it displays in show.html.erb. I dont know how to figure that out

def new
@parent = Parent.new
@parent.secondaryparents.build
end
def edit

end

def create
	@parent = Parent.new(parent_params)
	@parent.family = current_user
	if @parent.save
		flash[:success] = "Family details were added"
	redirect_to parent_path(@parent)
else
	render 'new'
end

end
def update
	if @parent.update(parent_params)
		flash[:success] = "Family details were updated"
	redirect_to parent_path(@parent)
else
	render 'edit'
end

end
def show

end
def destroy

	@parent.destroy
	flash[:danger] = "Family details were successfully deleted"
	redirect_to parents_path
end

private
def set_parent
		@parent = Parent.find(params[:id])
end
def parent_params
		params.require(:parent).permit(:parent_1_firstname, :parent_1_lastname, :address, :city, :province, :telephone_number, :postal_code, :email, :family_type, :family_size, :family_situation, secondaryparents_attributes: Secondaryparent.attribute_names.map(&:to_sym).push(:_destroy))
end

Hi @sidhunavroop this is a very basic question, it is not related to cocoon at all, so please ask this question on stackoverflow.com.
Please attempt to use the editor to 1) correctly indicate a piece of text is code, and 2) make sure you have proper indentation (ruby standard indents by 2 spaces, see style guide )
Post the link to the question on stackoverflow here, and I will answer there if nobody has had a look yet.

okay
thank you @nathanvda


Update command-line completion docs

File: compose/completion.md
Linked files currently result in 404s.
Also it seems that despite GA announcement there is no cli completion for docker compose yet.

Thanks for sharing the issue. Please see the discussion in https://github.com/docker/docker.github.io/issues/14692


update docu after stboot redesign

Signed-off-by: Jens Drenhaus<EMAIL_ADDRESS>

A pretty huge improvement when compared to the earlier README! =)
Here are some comments from a top-to-bottom read:

What is the intended target audience? It would be good to state that early on. Right now I think it is "firmware expert". For example, I don't understand the difference between the MBR bootloader and EFI application modes.
I think the part around host and security configuration is too brief. It needs some additional explaining in addition to just listing the involved fields.
What is XOR? If it is notation for "or", consider dropping the "X" and just write "or". E.g., "dhcp" or "static".
"false XOR false" looks odd. Should "use_ospkg_cache" be a boolean?
I like the feature list. In fact, maybe it should be presented earlier on in one form or another. Right now there are features that the reader sort of have to figure out on their own if they read from top-to-bottom. Network boot is one example.
Are the figures in doc/ up-to-date? If so, maybe some of them would be a good fit for the README.
The README is becoming larger. To help the reader navigate efficiently it might be a good idea to provide a roadmap early on.
There are many typos. Unless someone else takes a pass over the README to fix them I can do it with a PR at some point.

A pretty huge improvement when compared to the earlier README! =)
Here are some comments from a top-to-bottom read:

What is the intended target audience? It would be good to state that early on. Right now I think it is "firmware expert". For example, I don't understand the difference between the MBR bootloader and EFI application modes.
I think the part around host and security configuration is too brief. It needs some additional explaining in addition to just listing the involved fields.
What is XOR? If it is notation for "or", consider dropping the "X" and just write "or". E.g., "dhcp" or "static".
"false XOR false" looks odd. Should "use_ospkg_cache" be a boolean?
I like the feature list. In fact, maybe it should be presented earlier on in one form or another. Right now there are features that the reader sort of have to figure out on their own if they read from top-to-bottom. Network boot is one example.
Are the figures in doc/ up-to-date? If so, maybe some of them would be a good fit for the README.
The README is becoming larger. To help the reader navigate efficiently it might be a good idea to provide a roadmap early on.
There are many typos. Unless someone else takes a pass over the README to fix them I can do it with a PR at some point.

Re target audience: Very good point to let the reader know at the beginning... OR to further improve the docu. Any suggestions?
Re installation options and configuration files: I'm going to extend the docu.
Re feature list: What would be your suggestion of the order?
Re length of the document. I'll add a TOC once it is nearly ready.

Merged as part of #115


Non-root user support for REX-Ray client

REX-Ray should both create a group named rexray upon installation as well as check to see if that group exists, and if so, ensure that any sock files created for an embedded libStorage server are set to allow members of that group access.

I don't know we should require users and groups, but this certainly should be an option.
Consider a case where a machine is managed by NIS, LDAP, etc and that user/group may have to be created at a higher level, or cause some conflict.
Presumably, we could configure REX-Ray to use user/group pair other then root?

Hi @koensayr,
This issue is more to do with enabling a RR CLI client that's not running as root to connect to a RR server that's running a root, not to enable the RR server to run as something other than root. That would complicate matters for attaching new devices to the host. Thoughts?


Detect if process is closed during migration in phaul using pidfd

This allows detection if a process was closed during migration reliably using pidfds if pidfd_open syscall is supported.
CRIU already detects PID reuse using task's creation time internally, this further enforces the detection through P.Haul during migration using pidfds.
One short coming of this approach is that there might be a race condition between the call to isPidClosed() and criu.PreDump() which would happen if the process was closed exactly after the check and right before the pre-dump, if a process managed to reuse that pid in this duration it should be detected in CRIU using task's creation time, it is very rare but might happen.
Related issue: https://github.com/checkpoint-restore/criu/issues/717

You only check that root process in the dumped process tree is still the same. But that's not enough.

You should check it for each process of the dumped process tree.

You should not just fail if you've detected pid-reuse.

You should make criu know about it and make it skip memory images of this pid from previous iterations.

You should not just skip non-working pid reuse like "(skipping pidfd based pid reuse detection)"

If pid-reuse does not work there is a risk of memory corruption or exploit activity due to migration, we should just fail in this case.


feat(warehouse): 497-refact-warehouse-based-on-catalog

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Docker Services error: New path
https://github.com/AntonioFalcaoJr/EDA.CleanArch.DDD.CQRS.EventSourcing/blob/ccc84bc90c0cffb8dd580fbc9cbf3567915a50ce/docker-compose.Staging.Services.yaml#L289


Codly 0.2.0

Update to 0.2.0 when it's merged into the package distro
https://github.com/typst/packages/pull/314

It's merged. :)


Docs: Clearer demonstration of when/why to Take various tools

It's a bit difficult to know which features/tools require you to Take something, versus which ones are "built-in". It'd be nice to have a section of the docs with a table showing which things you can Take, and what features those things provide.

Still needed. This caused an issue for Nathan this morning.

Bump.

N/A. There will be a standard list of takes that all Symbols will use, or some sugar like SVGA.foo.


Add option to auto-release maven artifacts from Staging to Prod

Signed-off-by: Rishabh Singh<EMAIL_ADDRESS>Description
Add option to auto-release maven artifacts from Staging to Prod
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/2786
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2960 (0634dc6) into main (a65a754) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2960   +/-   ##
=======================================
  Coverage   93.17%   93.17%
=======================================
  Files         167      167
  Lines        4602     4602
=======================================
  Hits         4288     4288
  Misses        314      314

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@rishabh6788 Can we close this PR?

Closing this PR as feature is already in


github: rewrite the scheduler loop to ensure that rate-limiting is re…

…spected
All operations should be done in same GitHub monad to ensure that rate-limiting
headers are actually read and obeyed by the libary.
Signed-off-by: Thomas Gazagnaire<EMAIL_ADDRESS>

/cc @dsheets

This is the first application to use the rate-limiting functionality in anger. Please report any issues. Thanks!

@talex5 the logs say:
# File "ci/src/cI_web_templates.mli", line 32, characters 34-56:
# Error: Unbound module Tyxml

Any idea what could have caused this?

Missing version contraint on Tyxml (should be >= "4.0.0" I think).


[Request] Use semver rules when incrementing ambar versions

From the 1.0.0 => 1.3.0 jump introduces non-backwards compatible changes. This is in reality a major version bump and should be labeled as a 2.0 change since it requires a full data reset on the instance.
I was caught off guard by this when issuing python ambar.py update and it happily upgraded my docker containers, but failed to inform me the indexes had changed which I observed in #92.
I attempted a rollback and found no success. This broke around 1TB of indexed and "archived" content in my CE instance which damages my trust in the ambar project progression because a breaking change was introduced at a non-major version barrier.
I'm sorry to relay this as an issue but I didn't find a mailing list to broach this topic, and I'd love to regain some trust in the ambar project, as it really is great stuff. I just need to know my data is mostly safe in the hands of the project maintainers, and that dropping -all- data wont be required without a major revision upgrade so I can watch for and ensure i only pull updates prior to that happening since the management script is the recommended method to installation/operation.

@chuckbutler you're right, will keep that in mind and change update script.
P.s. as for now you can check update instructions in changelog.md

Thank you for the response and acknowledgement. :)


Feat/storybook

Codecov Report
Attention: 29 lines in your changes are missing coverage. Please review.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

src/components/Footer.tsx
100.00% <100.00%> (ø)

src/components/Tag.tsx
100.00% <100.00%> (ø)

src/components/buttons/IconBoxButton.tsx
100.00% <100.00%> (ø)

src/pages/404.tsx
100.00% <100.00%> (ø)

src/pages/about.tsx
100.00% <100.00%> (ø)

src/pages/blog/[slug].tsx
73.33% <100.00%> (ø)

src/pages/blog/index.tsx
93.18% <100.00%> (ø)

src/pages/index.tsx
76.92% <100.00%> (ø)

src/pages/project/[slug].tsx
75.00% <100.00%> (ø)

src/pages/project/index.tsx
81.81% <100.00%> (ø)

... and 5 more

:loudspeaker: Thoughts on this report? Let us know!.


Properly handle undefined and null in merging methods.

Description
When something called event.mergeXdm, event.mergeMeta, or event.mergeQuery with undefined or null (this would happen in Personalization), it would wipe out the previous state. Instead, we want to make these method calls a no-op.

Related Issue
None

Motivation and Context
Ensure that we get the expected merge result.

Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] I have signed the Adobe Open Source CLA or I'm an Adobe employee.
[x] I have made any necessary test changes and all tests pass.
[x] I have run the Sandbox successfully.

Good catch and very simple change. How did you find this behavior? Manual testing?

Yeah, manual testing. It may be that a functional test would have caught it, but I'm still working through updating the functional tests for activities we've set up on the new org.
As part of some cleanup, I changed the notification-mixin branch in a way that it's calling event.mergeXdm with a value of undefined. The old createEvent properly ignored our undefined value, but then I merged main (which contains the recent createEvent changes) into the notification-mixin branch, I started noticing that some personalization click collection XDM wasn't making it into the request and then I pinned it down to this. I don't know if anything in main is calling these merge methods with undefined or null, but it's good to handle that case regardless.


500 Internal Server Error when creating new pull request

Gitea version (or commit ref): 1.7.3
Git version: 2.20.1
Operating system: mac
Database : mysql
Can you reproduce the bug at https://try.gitea.io: NO
Log gist:

Description
[Macaron] 2019-03-02 09:59:20: Completed POST /hotbain/spring_cloud/compare/master...test_branch 404 Not Found in 175.311212ms
[Macaron] 2019-03-02 09:59:21: Started GET /serviceworker.js for [::1]
Screenshots

We're also getting
Completed GET /org/proj/compare/master...fork:master 404 Not Found in 91.186937ms

Are there are any error in gitea.log?

No errors. But if I go to /org/proj/pulls and press "New Pull Request" it goes to /org/proj/compare/master...fork:master which gives 404.

Still an issue with 1.7.4

Are there schema changes between 1.7.2 and 1.7.4 or would downgrade be safe?

@ptman I'm sorry to see this. I've not been following this so I don't completely understand the issue. Are you able to work out what the url should be?
Having seen two PRs touch this endpoint in quick succession because one completely broke I think this endpoint is fairly poorly described. I'm able get 404s on my rather pathological repos on try.

The URL should show the diff between the base and the branch to be merged, not 404. I could look closer at the SQL differences if I knew for sure that downgrading to 1.7.2 doesn't break anything.

OK it looks like that compare urls are a bit of mess:
Try comparing any branch with % in it.  https://try.gitea.io/arandomer/pathological/compare/master...foo%25foo
https://try.gitea.io/arandomer/pathological/compare/master...foo%2525foo
https://try.gitea.io/arandomer/pathological/compare/master...foo%252525foo
In particular try thinking about what happens with %2F:
https://try.gitea.io/arandomer/pathological/compare/path%252Fpath...path/path
It's not just %, preceding - is particularly broken:
https://try.gitea.io/arandomer/pathological/compare/--heads...foo%2525foo
https://try.gitea.io/arandomer/pathological/compare/foo%2525foo...--heads
Get the branches the wrong way round causes a 500:
https://try.gitea.io/arandomer/pathological/compare/notsubpath...master
vs:
https://try.gitea.io/arandomer/pathological/compare/master...notsubpath
There is a bug in the diff generation where escaping filenames with quotes in diff generation breaks:
https://try.gitea.io/arandomer/pathological/compare/master...quotebreak
Which is the same one that affects:
https://try.gitea.io/arandomer/test-perry123/commit/08c5f2e47bda90002aca34b46906d04a414c5a97

For reference here is some discussion of why it can 404 when there is a double quote in the filename: https://github.com/go-gitea/gitea/issues/6309. Basic testing says gitea will break on any situation where the diff includes the diff --git section inside double quotes like diff --git "a/file" "b/file". This includes having a backslash in the file name which is perhaps more common (Windows?).
I think this might be one of a few issues that lead to bad compare/pull/etc...

In my case the branch names don't contain anything that needs to be encoded. Is it safe to downgrade from 1.7.4 to 1.7.2 or have there been DB schema changes?

@ptman that's downgrade should be safe.

Ok, here are some sanitized logs from both 1.7.2 and 1.7.4. It seems that after 1.7.2 (i.e. 1.7.3 & 1.7.4) there's a missing join. You can diff the files side by side to see the difference, but I've also added newlines to point it out: https://gist.github.com/ptman/f76b398d0503e5c50424c1ea8cbfafec

Ok @ptman it looks like your issue is different from the initial issue reported by @hotbain. I'm not certain what's causing that issue as we need more information from @hotbain - If I had to guess, it's likely they're affected by the issue fixed by @mrsdizzie, it's unlikely that they're affected by the remaining branch escaping and preceding hyphen branch issues.
In any case your issue is related to:
https://github.com/go-gitea/gitea/commit/5c30817b5fa1fdeedc8d4fc02cf228dc0e6dc556
Which was reverted by:
https://github.com/go-gitea/gitea/commit/fe99c9901d302921eb1e4a67ba687ca3fe543425
Now, you appear to be in the subset for whom the original commit worked and it's reversion breaks.
This is #6302
Ok, so the revision did two things - one was change the url and the other was the permissions change.
So first of all, are the permissions correct - can the proposer read pulls on the base?
And I need to know where you click pull request and what you expect the URL to be. Can you hand change the URL to make it work?

so let's take this to #6302

I am also experiencing this kinds of errors when creating pull requests and accepting pull requests.
I have not been able to pinpoint exactly how to produce an error, I tried using the PR url given on the console during the push or manually getting to the pull request page. Sometimes one way gives a 500, sometimes it is the other way around.
My setup is using gitea 1.7.3 built with go1.11.5 : tidb, sqlite3
git version : 2.18.1
Usually when the error 500 appears I have the following error in gitea.log :
/var/log/gitea/gitea.log:2019/03/26 08:55:12 [...user/notification.go:33 GetNotificationCount()] [E] GetNotificationCount: database table is locked: notification

Do you need more informations ?

@nicovince that's another issue. It caused by your sqlite database and which version are you using?

@lunny I am using sqlite-3.25.3

@nicovince please open another issue for this. I suspect we will need to move to a pure Gitea serv as client of Gitea web to prevent this.

opened #6435

@hotbain could you confirm that this has been resolved on v1.8.0

I think this has been resolved. Please feel free to reopen it.

Still happens in Gitea Version: 1.9.0+dev-376-ge07ff2f89
logs show:
2019/06/25 11:01:14 .../xorm/session_get.go:99:nocacheGet() [I] [SQL] SELECT "id", "user_id", "issue_id", "is_watching", "created_unix", "updated_unix" FROM "issue_watch" WHERE (user_id = $1) AND (issue_id = $2) LIMIT 1 []interface {}{2, 6}
2019/06/25 11:01:14 .../xorm/session_get.go:99:nocacheGet() [I] [SQL] SELECT "id", "user_id", "repo_id" FROM "watch" WHERE "user_id"=$1 AND "repo_id"=$2 LIMIT 1 []interface {}{2, 2}
2019/06/25 11:01:14 routers/repo/pull.go:302:PrepareMergedViewPullInfo() [E] GetCompareInfo: exit status 128 - fatal: ambiguous argument 'b568d59d88af7ea7393d6ae2c9da09794a3c136d...refs/pull/4/head': unknown revision or path not in the working tree.
        Use '--' to separate paths from revisions, like this:
        'git <command> [<revision>...] -- [<file>...]'

This is not the same bug as the original.
It has the same overall effect but it is not the same.
@jeansergegagnon how did you cause this?

I'm experiencing the same issues as @jeansergegagnon on Gitea version 1.9.2, a simple installation with an sqlite database.
Steps to reproduce:

create a new branch
push branch
create a new pull request, it will be available to be merged automatically according to Gitea
clicking the "Merge Pull Request" button results in a 500 error

Log:
2019/08/28 15:30:20 routers/repo/pull.go:629:MergePullRequest() [E] Merge: getDiffTree: git diff-tree [/opt/gitea/data/tmp/local-repo/merge-911475386.git base:master head:head_repo/remove_readme]: fatal: ambiguous argument 'head_repo/remove_readme': unknown revision or path not in the working tree.
	Use '--' to separate paths from revisions, like this:
	'git <command> [<revision>...] -- [<file>...]'

If you need me to open a separate issue for this let me know.

OK. Could you reproduce this follow the steps:
1 fork A to B
2 push -f to B
3 click pull request on B
4 500

OK. Could you reproduce this follow the steps:
1 fork A to B
2 push -f to B
3 click pull request on B
4 500

Dear All,
I found the same issue. After a good installation, simply stop to work.
Please, kindly ask any newer reference. Update the git version is not an option for me.
Thanks!

this should be fixed if there is a new issue feel free to open a new issue for it :)


API fails searching tracks

I successfully get an access token and was able to show my user information.
But I've some problems to make a search for tracks:
private void searchTracks() {
Api api = Api.builder().accessToken(accessToken).build();
try {
Paging page = api.searchTracks("example").build().get();
List items = page.getItems();
for (Track track : items) {
  String artistString = "";
  List<ArtistSimplified> artists = track.getArtists();
  for (ArtistSimplified artist : artists) {
    artistString += ", " + artist.getName();
  }
  artistString = artistString.substring(2);

  System.out.println("Name: " + track.getName());
  System.out.println("Artist: " + artistString);
  System.out.println("Album: " + track.getAlbum().getName());
  System.out.println("ID: " + track.getId());
  System.out.println("URI: " + track.getUri());
}

} catch (Exception e) {
e.printStackTrace();
}
}
The only error I get is:
com.wrapper.spotify.exceptions.BadRequestException: 400
which is not so meaningful.
And my scopes during authorization flow were:
Arrays.asList("user-read-private", "user-read-email", "user-modify-playback-state",	"user-read-currently-playing", "user-read-playback-state");

I think it's a bug, no enhancement because the functionality is broken.

Could well be, but that's not verified yet. Until then you're currently asking for a more specific error message.
I'll have a look into this and change the labels as needed. Thanks for reporting!


10     done

Describe the results you received:
No block.
Describe the results you expected:
The script gets block within 10 seconds, it blocks at L8.
Additional information you deem important (e.g. issue happens only occasionally):
After containerd/containerd #1111, kill shim of a paused container will first resume this container, then this container is killed. But when the the script blocks, I find the container is still paused. handleSigkilledShim() returns at https://github.com/containerd/containerd/blob/v0.2.x/runtime/process.go#L306, so the following p.container.Resume() is not reached.
That is to say, when exit pipe is closed since shim is killed, we can still see shim for a while. I have tried to add a sleep(10 milliseconds) before e := unix.Kill(p.cmd.Process.Pid, 0), then the above script won't block for a long time.
@mlaventure @coolljt0725 Any ideas about this issue?

Are the following codes essential?  @mlaventure
diff --git a/runtime/process.go b/runtime/process.go
index f5dd3ee..7b29b91 100644
--- a/runtime/process.go
+++ b/runtime/process.go
@@ -300,12 +300,6 @@ func (p *process) handleSigkilledShim(rst uint32, rerr error) (uint32, error) {
                return rst, rerr
        }

-       // Possible that the shim was SIGKILLED
-       e := unix.Kill(p.cmd.Process.Pid, 0)
-       if e != syscall.ESRCH {
-               return rst, rerr
-       }
-
        // The shim was SIGKILLED
        // We should get the container state first
        // to make sure the container is not in


Wrong x Axis display when the data points>80K

Please see the code at Sine Wave
When set loop=2e3, this shows as below:

When set loop>8e4, the plot area in X direction becomes less and less.
Expected Behavior
The plot area in X direction shouldn't be change, because the maximum X isn't changed.
Current Behavior
When set loop=2e5, it becomes about one third in X direction:

Steps to Reproduce
set loop=2e2,2e3,2e4,2e5 to see the difference
Environment

pixi.js version: 5.2.0
Browser & Version: Chrome 78.0.3904.108
OS & Version: Windows 10X64 1803
Running Example: _https://github.com/rubyzhao/Pixi_MyChart_Line_

maybe its 64k vertices limit?
https://github.com/pixijs/pixi.js/wiki/v5-Hacks#pixigraphics

Thanks for your help. I follow the suggestion and add below, but the issue is still there.
//PIXI.settings.PREFER_ENV = PIXI.ENV.WEBGL; PIXI.settings.PREFER_ENV = PIXI.ENV.WEBGL2;
...
line.geometry.updateBatches(); //try commenting that to see Uint16 overflow line.geometry._indexBuffer.update(new Uint32Array(line.geometry.indices));
Please see the video for loop=2e5. Initially looks right, then the area become less automatically.
Pixi Line - Google Chrome 11_24_2019 12_58_23 PM.zip

Oh, that's interesting. OK, I'm trying to debug it here: https://www.pixiplayground.com/#/edit/ub6F36aWoMfw0o7ebnu8o
It can be a real bug. I just want to remind that real app shouldn't do that kind of input,
That's what I call 100 thousands bunnies problem - you need high-level algorithm to complement pixi low-level or it can have all kind of interesting side effects.

OK, found that finishPoly() is needed because line wasnt closed and it awaits input. render() method has that line just in case. That's a protected method, but I see more and more cases that we need something like that to be public.
line.finishPoly();
line.geometry.updateBatches();
line.geometry._indexBuffer.update(new Uint32Array(line.geometry.indices));

Great. Appreciate your help.
I know I shouldn't challenge this again. But when set loop=2e7,  it initially shows right as basic canvas, after while disappear again.

There are no breaks on plot train. I'll look up later :)


02_IPA 05-Dec-2021/Question-2 is not passing the test cases

https://github.com/harshitg123/TCS-Xplore-Python/tree/d04105e9fe17855d3373cdee80677b8cea1fea52/02_IPA 05-Dec-2021/Question-2

First of all, I'm very sorry to reply this late to your issue.
I read the question once again it is mentioned there to show the count of the first object only and right now I'm showing the count of all the objects.
I've now removed the loop and shown the count of the first object only.
Thanks for pointing out that issue.


(WIP) Parallelize / asynchronize some AWS cp calls

execute_command is blocking so for the appropriate "aws s3 cp" calls (mostly uploads) we can use a thread handler pattern instead.

"with iostream" wraps the call in a semaphore / basically just limits the number of concurrent IO calls currently running.

How does this look so far? If it's reasonable I'll change more calls in other files.

Now that i've reflected on this more, I think we only need the joining functionality if we are checking the result status of the uploads.   And this code never checks the result status.  Let's have it do that.  May be have the join function raise an exception if something didn't go well with some upload.

Looks like a test run for this hung stage 2.   https://github.com/chanzuckerberg/idseq-pipeline/issues/171

@boris-dimitrov would you recommend adding back a "results = {}", "results[run_name] = 'blah'" sort of pattern to support checking the run status?
Or perhaps something like:
class MyThread(Thread):
def run(self):
try:
Thread.run(self)
except Exception as self.err:
pass # or raise
else:
self.err = None

May roll this into Boris's uploader changes since it's similar but saving the AsyncHandler class for usage.
Main conclusion from the test runs is to be careful about doing it in run_in_subprocess.
Also for some reason the stage is not marked as completed once you change the semaphore and the 'thread' to multiprocessing.semaphore and multiprocessing.process. Some values are not being changed/shared properly?


Merge pull request #1 from OU-PhD-Econometrics/master

update my forked repo

update

This looks like a failed push to your own fork, so I'm closing it.


Regression : Truncated line points when min or max option is present on scale

Expected Behavior
Line points should be fully displayed when min and max option in scale are provided.
Current Behavior
Points are cutted when they exceed chart bounds.
Steps to Reproduce
The bug is reproductible on the live page :  https://www.chartjs.org/docs/latest/samples/line/line.html
Below is the configuration and the data to use to reproduce the bug:
const config = {
type: 'line',
data: data,
options: {
responsive: true,
scales : {
y:{
min:0
}
},
plugins: {
legend: {
position: 'top',
},
title: {
display: true,
text: 'Chart.js Line Chart'
}
}
},
};
and the data
const DATA_COUNT = 7;
const NUMBER_CFG = {count: DATA_COUNT, min: -100, max: 100};
const labels = Utils.months({count: 7});
const data = {
labels: labels,
datasets: [
{
label: 'Dataset 1',
data: [0,0,0,0,0],
borderColor: Utils.CHART_COLORS.red,
backgroundColor: Utils.transparentize(Utils.CHART_COLORS.red, 0.5),
pointRadius: 50
},
{
label: 'Dataset 2',
data: Utils.numbers(NUMBER_CFG),
borderColor: Utils.CHART_COLORS.blue,
backgroundColor: Utils.transparentize(Utils.CHART_COLORS.blue, 0.5),
}
]
};
Context
I used v2.9.4 and migrate to v 3.6.0.
In v2.9.4, points were fully displayed.
Thanks to the team for this great tool.

Duplicate of #9372


Add log fields for Go messages

Currently does not contain tests, will be implemented when #2 is done

Performance of type assertions

I think having a working, flexible MVP is more important than performance at the moment. We can always benchmark and optimize this later. I can live with being a couple of nanoseconds slower. Also, this way we save quite some development time, because we don't have to implement this for every field/message (and maintain it if we make changes).


Add Metal3 website link in README

as title says

This might improve clomonitor score a bit.
cc @tuminoid @Rozzii @elfosardo

/lgtm


Updated community descriptions for changed videos

Updated community descriptions for videos that have been re-cropped or have had their start or stop times changed.

Thanks a lot for this !


Jesse: Watch blumen.in

Jesse requests the watch of the watch_keyword blumen\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

blumen\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Tracking: inviting people to the team

[ ] TWiR

Please suggest anyone else we should invite that produces Rust related content or has an interest in this area by commenting on this thread.

Opened because of #6

How about Chris Krycho, of the New Rustacean podcast?

I've started work on chronicle.rs which seeks to delve more into Rust's history as a resource for people to look at as well as answer interesting questions such as "Why do we call libraries crates?"


Update chessmarkable to 0.7.0-1

This change integrates a requested feature to add savestates (more on the release page).
Since the changes don't really affect anything to do with models, just testing on one model is enough.
Testplan:

Start a game (mode doesn't matter). Remember the chosen slot.
Make at least one move
Hit "Save & Quit"
Check that the file /home/root/chessmarkable/savestates.yml was created and your chosen slot contains a string
Start a game from your chosen slot
The game should have remembered the piece locations

I'm not really sure that /home/root/chessmarkable is the correct location for savestates. Following the XDG Base Directory specification (https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html), I would expect it to live in $XDG_DATA_HOME, or $HOME/.local/share.
That said, I've run through the test steps and while the game does save and recall properly, including across launches, there is no folder/files at /home/root/chessmarkable. After a quick search I was able to find it in /home/root/.config/chessmarkable/savestates.yml

Thanks. I think I failed copy&paste there. It is indeed intended to be in /home/root/.config/chessmarkable/.


missing framework UIKit CoreGraphics

New Issue Checklist

[ v] I have read and understood the CONTRIBUTING guide
[ v] I have read the Documentation or CocoaDocs
[ v] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
ios

Platform Version
14

CocoaLumberjack Version
latest (3.6.2)

Integration Method
cocoapods

Xcode Version
Xcode 12

Repro rate
all the time (100%)

Issue Description and Steps
use CocoaLumberjack with cocoapods then build
Undefined symbols for architecture x86_64:
  "_CGBitmapContextCreate", referenced from:
      +[DDTTYLogger getRed:green:blue:fromColor:] in DDTTYLogger.o
  "_CGColorSpaceCreateDeviceRGB", referenced from:
      +[DDTTYLogger getRed:green:blue:fromColor:] in DDTTYLogger.o
  "_CGColorSpaceRelease", referenced from:
      +[DDTTYLogger getRed:green:blue:fromColor:] in DDTTYLogger.o
  "_CGContextFillRect", referenced from:
      +[DDTTYLogger getRed:green:blue:fromColor:] in DDTTYLogger.o
  "_CGContextRelease", referenced from:
      +[DDTTYLogger getRed:green:blue:fromColor:] in DDTTYLogger.o
  "_CGContextSetFillColorWithColor", referenced from:
      +[DDTTYLogger getRed:green:blue:fromColor:] in DDTTYLogger.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

@yishuiliunian
Thanks for your opening issue.
But this seems to be a duplicated issue. https://github.com/CocoaLumberjack/CocoaLumberjack/pull/1139#pullrequestreview-410897173 https://github.com/CocoaLumberjack/CocoaLumberjack/pull/1071
Could you try this?
platform :ios, '9.0'

target 'SampleIOSApp' do
  use_frameworks!

  pod 'CocoaLumberjack'

  post_install do |installer|
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        # config.build_settings['CLANG_ENABLE_MODULES'] = 'NO'
        # e.g. Sets Build Settings to use `ccache`.
        # config.build_settings['CC'] = '$(PODS_ROOT)/../ccache-clang'
      end

      target.add_system_framework(['CoreGraphics', 'UIKit'])
    end
  end

end

yes, it works

I'm going to close this issue because the issue has been resolved.
Please feel free to reopen it if you have any questions.

this does not work on SPM

there is a line missing in the target:
                linkerSettings: [.linkedFramework("UiKit"), .linkedFramework("CoreGraphics")]

@sisoje We cannot add that line since the package also needs to build for macOS.
However, I've never had issues with SPM in that regards. Can you provide a sample project that is integrating CocoaLumberjack with SPM and fails to build?


Add an ability to add comments

Especially when collaborating, the ability to comment elements on a whiteboard would rock!
I'm thinking of comments like it's done in Google Docs or Nuclino. For the latter see here and here for a good description.

Would be so useful to use as a description for specific drawn ui elements
(what is this button suppose to do?, :clicks it:, "This button will add a new entry into the todo list")

We will be adding commenting to Excalidraw Plus since this is something that will if not require, at least heavily benefit from things like authentication.

+1 - for offline reviews in global orgs having a Google Docs style commenting would be huge for me in my org.  Thank you.

+1 it would really help with async collaboration on docs

+1

Comments will very soon be available on Excalidraw+ 😊

Forgot to update — comments launched last week https://twitter.com/excalidrawPlus/status/1552670831402225664!

Is there a way to allow shared links to be commentable? I shared a read-only link (with no edit permissions) but there was no comment button.

@CMCDragonkai not currently, but on the roadmap!

Is it also possible to attach/link a comment to a particular drawn element/text, would be super helpful when rearranging elements

Comments should be allowed by anonymous users! What's the status?

Use cases for commenting for me:

eg: Inviting other team members for collaboration on a user journey review, currently this is a blocker for our team

For those interested in this feature, I think https://github.com/excalidraw/excalidraw/issues/6227 might be the open issue for adding comments to shared links.


improve get_version_of_tools

@twaugh PTAL

Other than the docstring it looks great!

Good catch, fixed, thanks!

LGTM


wip: try print env

感觉现在这么设置不对，测试一下。

Codecov Report

Merging #378 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #378   +/-   ##
=======================================
  Coverage   72.74%   72.74%
=======================================
  Files          74       74
  Lines        2656     2656
=======================================
  Hits         1932     1932
  Misses        724      724

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 19cce65...b7b9720. Read the comment docs.


Upgrade eslint-* packages

Closes #35.
I have also replaced eslint-config-airbnb with eslint-config-airbnb-base (same but without jsx related rules/plugins) and removed all react related rules from config.

Coverage remained the same at 93.525% when pulling 6abb95765c20817df54a13b5d93d0ba0db358e80 on Mistereo:master into 60d2019a00395dcbd6ce0ff571b3191b2e5e9079 on grofers:master.

Looks good to me.
Approved 👍
@dash1291 @vaidik can you please also have a look.

LGTM. I think we can merge this one.


Traitors should be selected before roles are assigned

Description

Yes, this should be an upstream issue. I can't open those. It can get fixed here and then upstreamed, though.
Right now, roles are assigned before traitors. This discentivizes people from having preferences for sec or heads set, because it reduces their change of being an antagonist. It seems this is also the reverse of the norm in most SS13 servers.
The current method allows a very minor increase in metagaming if you know some static's job prefs, but it has much bigger benefits in ensuring antag-disabled roles get filled at the start of the round.

I can see no problem with changing how this works. I can't say when I'll get around to this, but it's worth doing eventually.

I can probably write it. I've written most of the other traitor refactors


added custom completion

basic idea is to somehow enable registration of custom completers which are invoked and passed the current command line up to cursor position to then return completions as json (or similar)

uses reedline with Suggestion struct for descriptions during completion
uses dialoguer with added paging to fuzzy_select (still some issues with line removal)
still hardcoded call instead of configuration which command to invoke for completion (should be sth. like https://github.com/rsteube/nushell/blob/0.38.0-a986de8ad_carapace2/crates/nu-completion/src/custom.rs)
still quite a mess

this currently works with carapace-bin after adding the binary to PATH
related: https://github.com/nushell/reedline/pull/167
related: https://github.com/mitsuhiko/dialoguer/compare/master...rsteube:fuzzy-paging

this was cool to play with, thanks for allowing us to play and test with it. however, it's quite out of date now so it's probably time to close it. thanks!


[BUG] load project crash , when i have scaled model.

this is output when i have launched godot engine with terminal, system is linux manjaro 64bit:
VBoxContainer: 144,108
ERROR: get_edited_scene_root: Index current_edited_scene out of size (edited_scene.size()).
At: tools/editor/editor_data.cpp:479.
ERROR: get_edited_scene_root: Index current_edited_scene out of size (edited_scene.size()).
At: tools/editor/editor_data.cpp:479.
bind toptions
ERROR: get_edited_scene_root: Index current_edited_scene out of size (edited_scene.size()).
At: tools/editor/editor_data.cpp:479.
ERROR: set_current_tab: Index p_current out of size (get_tab_count()).
At: scene/gui/tabs.cpp:296.

I have used dev version of godot of 4-5 days ago, and I have try with 1.1 and this is output
: /usr/lib/libssl.so.1.0.0: no version information available
: /usr/lib/libcrypto.so.1.0.0: no version information available
freed code id 1

Im having the same issue.
When starting from command line with "godot -e -path my/project/" it starts, but doesnt open any scene. When I open my main scene it crashes with "ERROR: set_current_tab: Index p_current out of size (get_tab_count())."

I can tell that both crashes occur in the same line (link to line with diff). It's related with the new update that allow collisions being visible during the game.

+1 crash on creating a new CollisionShape2D - master branch

Can you still reproduce it with the current master branch?

CollisionShape2D - looks fixed
Output still there.
ERROR: get_edited_scene_root: Index current_edited_scene out of size (edited_scene.size()).
At: tools/editor/editor_data.cpp:500.
ERROR: set_current_tab: Index p_current out of size (get_tab_count()).
At: scene/gui/tabs.cpp:500.

Thanks. So you get the error output, but no crash? I guess I'll fork this into a new issue then, maybe the initially reported crash did come from the CollisionShape2D issue, and has nothing to do with the error message.

@AlexHolly Can you open a new issue specifically for this set_current_tab error message? The first error message is a known issue (#2731). Also please add details about your environment, exact Godot version (nightly build date or commit), how you start Godot and when the error appears, etc., since I can't seem to reproduce the issue.

@godotengine/bugsquad: This issue was hijacked by the CollisionShape2D bug that happened afterwards, since the error messages in the console are the same, even though they're not related to the bug. The original issue was about scaled models and it was open before the collision debugging was added and hence before the CollisonShape2D bug was introduced. So we should check if the original issue (about scaled models) is still valid and open another ticket for it.


Redact environment variable values by default in cf env

Please provide details on the following items. Failure to do so may result in deletion of your feature request.
I think it would be worthwhile to redact environment variable values whenever they are visible especially in the output of cf env. I think the default behavior should be to redact with a command line option like '--no-redact' required to display the values.
What's the user value of this feature request?
A lot of apps keep sensitive credentials in environment variables (not to mention service binding credentials in VCAP_APPLICATION). Redacting by default would prevent accidental exposure in scenarios such as a screen sharing session.
Who is the functionality for?
Platform end users especially application developers.
How often will this functionality be used by the user?
As often as the cf env command which I'd imagine is used very frequently.
Who else is affected by the change?
It is possible that automation scripts that read output from the cf env command would be broken by this change and would need to be updated to use the --no-redact option.
Is your feature request related to a problem? Please describe.
Yes and no, it comes from the realization that I (and many others) screen share often and its easy to run cf env in passing, forgetting that it just dumped a bunch secrets for all to see.
Describe the solution you'd like

The cf env command redacts environment variable values in its output.
The cf env has a --no-redact option which will override the redaction of environment variable values.

(Nice to have: environment variable values are also redacted in CF_TRACE output.)
Describe alternatives you've considered
No reliable alternatives come to mind. The obvious thing is to "be careful" but that's guaranteed to fail.

Hey @xtreme-jesse-malone!
Thanks for filing this feature request! I am curious how you would feel about a potential flag for redacting values being optional, rather than the default being redacted, alternatively a way to query for only a specific env value such as cf env database_url?
Thanks!
Jenna

I think the most benefit would come from changing the default behavior. A flag to redact values at least makes it easier to be careful. But it would be best for the easiest command to also be the safest, and to require extra effort in order to take an unsafe action (where "unsafe" means potentially displaying secrets).
A query for specific environment variable values could also be useful provided there is a safe way to list the available variable names.
Thanks,
Jesse

Thank you for your submission. If you still run into this issue with the latest CLI v8,  please open a new ticket.


Postgres proxy random connection error

Hello,
I'm using cloud_proxy from docker image with this command:
CMD ["/cloud_sql_proxy", "-instances=my-project:europe-west1:my-database-replica=tcp:<IP_ADDRESS>:5432"]

I call it from PHP using named service postgres.
I'm using GCE Cloud API access scopes - Cloud SQL -> "Enabled" to access the database.
It woks must of times. Some connections get dropped, like 1/3. I'm not getting any output from the container logs but New/closed connections.
I'm neither using cpu or memory limits. Is there any way from I can debug this?
Thanks.

Seems solved.


uses_mkl fails sometimes

I am compiling scipy on a linux computer.
I am untaring blas and lapack into directories, and then setting up LAPACK_SRC and BLAS_SRC variables.
However, this fails when I try and build scipy.
...
  File "scipy/lib/blas/setup.py", line 39, in configuration
    sources += get_g77_abi_wrappers(lapack_opt)
  File "/tmp/foo/scipy-0.15.1/scipy/_build_utils/_fortran.py", line 64, in get_g77_abi_wrappers
    if needs_g77_abi_wrapper(info):
  File "/tmp/foo/scipy-0.15.1/scipy/_build_utils/_fortran.py", line 50, in needs_g77_abi_wrapper
    elif uses_mkl(info) and sys.platform == "darwin":
  File "/tmp/foo/scipy-0.15.1/scipy/_build_utils/_fortran.py", line 39, in uses_mkl
    if r_mkl.search(library):
TypeError: expected string or buffer

I can fix this error by ignoring the failures in uses_mkl by a try execpt block like:
def uses_mkl(info):
    r_mkl = re.compile("mkl_core")
    libraries = info.get('libraries', '')
    for library in libraries:
      try:
        if r_mkl.search(library):
            return True
      except:
        pass

    return False

Sounds like Python 3, is this the case?

I have had this happen with both python 3 and python 2.7.

and if I change it to
except:
   print type(library)

it will print out
<type 'tuple'>
several times.

An example of what library is when it fails:
('fblas_src', {'sources': ['/home/jjc/raven_libs/build/BLAS/caxpy.f',...'/home/jjc/raven_libs/build/BLAS/ztrsm.f'], 'language': 'f77'})
Basically, regular expressions fail when trying to search a tuple.

I think we should deprecate BLAS_SRC and LAPACK_SRC in numpy, and close this. Building BLAS and LAPACK from source should really be out of scope for numpy, seems quite unhealthy.

Indeed, that was what I was wondering the other day. This dependence is not really needed for NumPy.

Done in https://github.com/numpy/numpy/pull/18348. Will close this issue. "don't do this" is the only advice we can give.


Deal with cache signature rules encoding

D'no what we wanna do about the conditional function existence checks there?

remove them and require symfony/polyfill-mbstring and symfony/polyfill-xml

symfony/polyfill-xml

On a side note, that function was actually moved out of ext-xml in either php 7.1, or 7.2.

7.2 is not there, 7.1 is just one version.
sure, so, they are in code in 7.1 ?

ping @GrahamCampbell

ping @GrahamCampbell

ping @GrahamCampbell
really ?

sure, so, they are in core in 7.1 ?

D'no. Don't really care. Doesn't matter.

We have the polyfil anyways. What do I actually need to do here?

@SpacePossum , any concerns here ?

My concerns are about edge cases we won't likely to run into any time soon, nor can I back those concerns up with any real input or test. So for that those should be dismissed.
The changes here look good to me, these do improve what we have now :)
Thanks @GrahamCampbell
I suggest merging this as is (although resolving https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/2463/files#r109024293 would be nice).

Thank you @GrahamCampbell for taking care of this.
As here are 2 commits of yours, I squashed them and picked into original PR.


Chromium bfcache issue

I've searched issues both here and on Stack Overflow, but only found Select2 Dropdown not working after browser back button used which was unanswered.
I believe this is an issue that is related to the bfcache (back-forward cache) in Chrome 79 as this wasn't an issue in Chrome 78.  I don't feel like it's a bug in Select2, but since others may encounter it I thought this would be a good place to raise it.
The code below demonstrates the issue when using the latest version of Chrome on Windows 10.

        <title>Test Page</title>
        <link rel="stylesheet" type="text/css" href="//cdnjs.cloudflare.com/ajax/libs/select2/4.0.12/css/select2.css">

Test Page

        <select id="example" style="width: 300px" multiple data-placeholder="Select Month">
            <option value="1">January</option>
            <option value="2">February</option>
            <option value="3">March</option>
            <option value="4">April</option>
            <option value="5">May</option>
            <option value="6">June</option>
            <option value="7">July</option>
            <option value="8">August</option>
            <option value="9">September</option>
            <option value="10">October</option>
            <option value="11">November</option>
            <option value="12">December</option>
        </select>

        Google

When running you select items in the dropdown and then navigate away from the page using the hyperlink and then returning to the page by pressing the browser back button the previously selected items aren't shown, only the placeholder.  However when you go to make a selection the previously selected items are highlighted in the dropdown (see images in SO question for an example).
The only way I was able to workaround this was to set a short timeout when initializing the select2 (see commented out code).  I initially thought using the pageshow event would work, but that had the same result as onload event.  Anyway I'm hoping someone reading this is able to reproduce in Chrome 79 and if so, suggest the best way to resolve the issue.  Thanks!

Closing issue since further testing has ruled out select2 being involved.

I still seem to be getting this issue, even though I have the latest version of Chrome (80.0.3987.132) 😢

@JonBetts If you're using ready() method with an older version of jQuery try upgrading to 3.x version.

@mguinness thanks for the suggestion! I'll have to see if it's viable for us as we're on the latest version of jQuery 1, so it might be a bit of a job! But good to know there could be a solution 😃

No problem, I had to upgrade from 2.2.4 to get it working.  I found jQuery 3.0 Upgrade Guide helpful resolving any issues I encountered.


Does not work with latest version of immutable.js

I use: "immutable": "~3.8.1"
When trying to add a record using

export const CarInfo = Immutable.Record({
  name:"Car2"
})

const recordTransit = transit.withRecords([CarInfo])

I get an error:
Uncaught Error: Cannot (de)serialize Record() without a name

When checking the code I see it looks for the record name using :
record._name || record.constructor.name

I tested both in my code: _name is undefined, and record.constructor.name always returns Record

Ok never mind, I forgot the descriptive name in the Record


Unable to find parts

The following linked parts seem to have broken/unavailable links at amazon now: Armor Heatsink Case and SSD case.  Are there compatible alternates available?  Can you tell me the manufacturer name for the heatsink so I can look elsewhere?

Seaech the keywords given before the link on any local merchant, your local amazon, aliexpress, ebay etc


[WIP] Nexmark: Enable Query13 for streaming mode

Query13 currently runs only for Batch, this change makes Query13 run under streaming mode. This also replaces the GBK with a Reshuffle transform.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

@arunpandianp
Why do you need to enable the streaming mode for Nexmark? Do you have a typical scenario that you are testing against?


GetService based on Class Type instead of Interface

Hello, I'm not sure if I'm doing something wrong or if it is how AutoRegisterDi should work, but I have the following issue:
ServiceLocator.ServiceContainer.GetService<T>(Type type);

The method above brings me the services I have registered in my service container, basically, it is a proxy for IHttpContextAccessor.
In my project I have some classes like this one (code trimmed):
public class GetAllUseCase : UseCase<IGetAllOutput>
{
    protected override async Task Execute()
    {
        // voodoo
    }
}

public class ForecastUseCase : UseCase<IForecastOutput>
{
    protected override async Task Execute()
    {
        // voodoo
    }
}

Basically I have a bunch of classes with UseCase suffix. The way I register them now is services.AddScoped(typeof(GetAllUseCase));, that is a) in order to avoid long generic interfaces and b) when I inject the class into the needed class it goes like so:
public class Weather : ApiController
{
    private readonly ForecastUseCase _useCase;

    public Weather([FromServices] ForecastUseCase useCase) => _useCase = useCase;

So far so good, what I expected with AutoRegisterDi was something like this:
services.RegisterAssemblyPublicNonGenericClasses(typeof(ForecastUseCase).Assembly)
    .Where(c => c.Name.EndsWith("UseCase"));

I tried also with .AsPublicImplementedInterfaces(), but it didn't work.
To simplify things I have the following:
public interface IFoobar<T>
{ }

public class Foobar : IFoobar<string>
{
    public string Foo { get; } = "Foo";

    public string Bar { get; } = "Bar";
}

Obviously the generic type here has no practical reason, it is just for depo purposes
and I saw that if I try to call by interface like so:
var foobar = ServiceLocator.ServiceContainer.GetService<IFoobar<string>>(
                typeof(IFoobar<string>));

it works, but if I call it by class it doesn't:
var foobar = ServiceLocator.ServiceContainer.GetService<Foobar>(
                typeof(Foobar));

Could you suggest me a way to make it so it will work by calling either the interface or the class directly if that is possible of course?
Thanks!

Hi @panosru,
I'm sorry but NetCore.AutoRegisterDi does't register generic classes. That fact was buried in the readme file, so I have updated the readme with a link to the excluded class types.
You have to manually your generic classes.


docs(README.md): correct URL

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area tests

/area proposals

/area CI

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: vjjmiras
Once this PR has been reviewed and has the lgtm label, please assign jasondellaluce for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, vjjmiras
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 4ac55029905d4789b4d4322c2f38da8606a45df4

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, jasondellaluce, vjjmiras
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


getting 403

I think they are using cloudflare now. So it is not possible anymore to make api calls to their private api.

I fixed the API endpoint. It seems alright even with Cloudflare right now.
Greetings


Allow overriding of plugin paths

Currently the plugin paths are hardcoded in the python code. The deployment location of custom plugins might be different than the deployment location of simoorg, so it would be nice to allow the plugin paths to be overriden. My suggested way of doing this would be to add an optional parameter in the fate book to control the search location for plugins:
plugin_base_path: /my/custom/plugin/deployment/location
topology_plugin: MyTopologyPlugin

Currently, I have it working by starting simoorg inside my custom startup script where I override the relevant atropos.*_PLUGIN_PATH global variable, but I'd rather not do this if simoorg supported custom plugin paths out of the box.

Sounds reasonable to do.

Good to work on it. Feel free to submit a PR when done :)

Hey @srikanth-viswanathan, Just wanted to see if you are actively working on the current issues that you raised with Simoorg. they seem to be really nice suggestions. Let me know :)

Haven't had time to work on these yet. I hope to do a couple next week.


SendSMS doesn't work in provided example

I'm trying to implement Desktop SMS and run into the issue which I was able to replicate on the example page from documentation: https://cdn.branch.io/example.html. When I click SendSMS it gets failed with the following error in console:

Just realized the page in response (which confused me a lot but seems to be not a source of issue) reports an invalid phone number. I was trying to use my Australian number, do you have any restriction on this? Does this restriction (if any) applies to the country or related to the billing?

Just worked out this issue a little bit more. It turned out this page works perfectly for my colleagues in Australia for Australian numbers but doesn't for UAE of Thai numbers. In Thailand it works for Thai numbers only but doesn't work for Australian or UAE. It there any restriction that you should use only numbers for the country you are in?

Hey @mikhailmelnik , I'm sorry to hear you're running into issues with this. We've recently had to implement stricter rules on SMS requests, due to a increase in spam. As such, attempting to send to a number from outside it's country of origin may result in an error message. So long as you are sending to a number in the same country as you, you should not get any errors. The current error message being returned is a generic response, but we are looking at options to make this more descriptive.

@mikhailmelnik feel free to reach out to<EMAIL_ADDRESS>if you've got more questions about this.


Consider moving FreeBSD tests to Cirrus-CI

libc's FreeBSD tests are currently using QEMU on Travis-CI.  This is bad for three reasons:

It's slow
It's complicated
Somebody (@wezm I believe) has to build a new image for every release.

Cirrus-ci.com just launched their new FreeBSD service.  It works much like Travis, but it has the option of using full VMs instead of just containers.  They currently provide images for four different versions of FreeBSD, and building new images is probably easier than with QEMU.  https://cirrus-ci.org/guide/FreeBSD/ .  Here's an example of a Rust project using Cirrus: https://github.com/asomers/tokio-file/pull/6 .

Somebody (@wezm I believe) has to build a new image for every release.

I updated them last time out of need (to get the build to pass with a change I had made) and documented the process. Having Cirrus manage this sounds like it's work trying.

@alexcrichton thoughts ? This requires enabling Cirrus-CI for rust-lang/libc, I don't know exactly which permissions Cirrus-CI would like to have, but as long as they are reasonable it might be worth it to enable it and let those interested send PRs to support it.
The same applies to https://builds.sr.ht/ which offers native FreeBSD and OpenBSD VMs. It's in beta, but they said that if we are interested, we should drop them an email<EMAIL_ADDRESS>. Their "pricing" is extremely reasonable ("as much as we want to pay" with a minimum of 2$ / month...) and they are nice (this is how wlroots is tested on those platforms). I'm sure they would help us set things up.

@alexcrichton it seems that Cirrus-CI requires:

Read access to code
Read access to members, metadata, pull requests, and single file
Read and write access to checks and commit statuses

Seems plausible to me to set up!

@alexcrichton if you're willing, please follow the instructions at https://cirrus-ci.org/guide/quick-start/ to configure the Cirrus CI application on libc's github repo.  Stop when you get to the "Post Installation" step.  I can submit a PR to do the rest.

Ok that's been done! Or at least I'm pretty sure it's done

This would be good to mention in the top-level README.  Currently the tests badge links to appveyor (windows tests only), there's a link further down in the README to the travis-ci bits (Linux, Apple), but none for Cirrus (and I'm not sure what the URL is for the libc tests on the Cirrus site :/).
FWIW the tests are not completing successfully for me on FreeBSD 12 so I'm trying to figure out if they're passing or not on the CI system.

Oh! I missed the travis badge.  At the risk of bikeshedding, would it be worth using a table for the build status?


SVGR Website breaks after switch on light theme

🐛 Bug Report
I open website of SVGR on my macbook pro in Firefox/Chrome and it is crashed (emtyp white page) after load
example:

To Reproduce

open main page https://react-svgr.com (dark theme must be chosen by default)
switch to light theme
reload page
it breaks

Expected behavior
website should not be broken

You are right! I would like to migrate the website to Docusaurus anyway. If someone want to help me to do that I will be happy!

@gregberge i can make pr but there is can be a lot of changes and huge diff

Yeah not a problem, only the result is important and if the website is deployed as a demo on Netlify I can check.

@gregberge in progress here https://github.com/gregberge/svgr/pull/824


[BUG] Doesn't see "Visual editor" option when open flow.dag.yaml in VSCode

Describe the bug
According to the documentation, there should be a "Visual editor" option when open flow.dag.yaml file in VSCode. However, I didn't see "Visual editor" in my VSCode.
How To Reproduce the bug
Steps to reproduce the behavior, how frequent can you experience the bug:

Follow this documentation to create an init flow via pf.
Once the project is created, open the flow.dag.yaml file in VSCode.
Didn't see any "Visual editor" option in the editor.

Expected behavior
See "Visual editor" on the top-left corner of the file editor.
Screenshots

Running Information(please complete the following information):

Promptflow Package Version using pf -v: 0.1.0b5
Operating System: Windows 11
Python Version using python --version: Python 3.11.4
VSCode version: 1.82.0

Additional context
Wonder if it's virtual env related.

Prompt flow VSCode extension is installed.
I use a virtual environment with VSCode workspace. promptflow and promptflow-tools are installed in the virtual env.
I can see the Prompt flow VSCode extension complains about missing promptflow and promptflow-tools. Maybe the extension does not support virtual env?!

@Vivihung can you share the full screen of the "Install dependencies" page?
I've tried virtual env and it worked for me so far.

@Vivihung  if you just update the promptflow SDK, you may need to reload your VSCode window, and then check the install dependecy again to see whether you venv can pickup the latest library, and then you cango to flow.dag.yaml to select the venv you have pf installed, which you should be able to see the visual editor

Thanks for your suggestions. I can see the visual editor on one of my machine (not the repro one though). Will spend a bit more time with the repro machine and share findings here.

Update on my investigation - The problem seems related to the VSCode Python extension. The reason the PF dependencies don't get detected correctly is due to the Python interpreter wasn't set to the right virtual env, and cannot be updated.
An easy way to identify this issue is to open a python file in VSCode. If the Python interpreter in the VSCode status toolbar (in bottom of the VSCode window) shows warning even selecting the right env python from the command bar, then you hit this issue.
My way to resolve it is

Uninstall all VSCode extensions that depends on the Python extension.
Uninstall Python extension.
Close VSCode.
Clean up VSCode caches [ref].
Reinstall VSCode Python extension and the Prompt flow extension.
Open the code in VSCode.


mwc-tab-bar docs: event name is wrong

I'm submitting a:

[x] bug report
[ ] feature request

The new docs for tab-bar say the event name is MDCTab:activated, but it's actually MDCTabBar:activated.
Thanks for getting this documented! Just in time for me to use it :)

oops!


Invalid form=11 for directory index lineHdrOffs=7ded41

I have a binary built on MinGw/Msys with g++ v11.2.0 and I've got the following error when I try to use cv2pdb on it:
$ ./cv2pdb.exe photonEngineer.exe
interpretDWARFLines:386: ERROR: invalid form=11 for directory index lineHdrOffs=7ded41
C:\msys64\home\greg\photonEngineer.pdb: cannot add line number info to module

Here is the executable file: https://drive.google.com/file/d/1BsmJmojMkkdN95nZ4-JU5uX6KikgFbXv/view?usp=sharing
Any idea on the cause of the error ? I tried with a hello world binary and it works correctly (no error).

interpretDWARFLines:386: ERROR: invalid form=11 for directory index lineHdrOffs=7ded41

If parsing up to that point was correct, it means that there is an invalid entry in the debug line number infos. This is part of the DWARF5 debug info format, so maybe switching to an earlier version might help.

Here is the executable file: https://drive.google.com/file/d/1BsmJmojMkkdN95nZ4-JU5uX6KikgFbXv/view?usp=sharing

The file is behind a login and additional security checks, can you make it more easily downloadable?

Thank you for your answer.
I will try soon to build the application with DWARF4 and check if it works.
Is cv2pdb supposed to work with DWARD5 ?
Here is a link to download the file without login request: https://cv2pdb.s3.eu-central-1.amazonaws.com/photonEngineer.exe

DWARF5 support was recently added by some contributors, so I'm not too familiar with it. According to the spec, some data formats were not supported, https://github.com/rainers/cv2pdb/commit/f390ed4c0aef0f0acd3f880c82564558bc2e0786 seems to fix that.

Fix tested and everything is fine. Thank you very much !


add support for template literals

The harmony branch of esprima supports ES6 template strings but when I pass it to escodegen I get:
Error: Unknown expression type: TemplateLiteral

Any update on this?

I have the same problem using the escodegen.browser.js, but the NODEJS version (installed July 2018) worked fine on the exact same input file. My guess is that my escodegen.browser.js copy is an old copy, before the support for TemplateLiteral was put in.
Looking at the GitHub -> escodegen / test / compare-harmony directory, there looks like lots of tests for Literals. Other tests have been updated within the last few months, so this repository still looks active.
The instructions for creating the escodegen.browser.js failed for me, on a new/clean install.
********** Error: Cannot find module "tools/entry-point.js"
unix> find . -name "entry-point.js" -print
yielded no results.
I had to find a copy of escodegen.browser.js floating around somewhere to use (obviously an old version). If anyone has a recent escodegen.browser.js I would appreciate a copy (.min version okay too).

I had to manually create the tools/entry-point.js file (found on this GitHub repository) in my directory. Now it works fine.
If I was a developer and did a full GIT download of this project, this file would have been there. It is not there when just doing a NPM install/init/build.


WIP: Fix version of elasticsearch

Apparently there was a mixup with the elastic search versions. We accidentally switched back to the old one while deploying the redesign branch :(
Can be reviewed but is not yet to be deployed.

Closing this because we don't use Elasticsearch anymore.


"service hdinsight-hbrest restart" command is also restarting RS

As per the document : https://docs.microsoft.com/en-us/azure/hdinsight/hbase/hbase-troubleshoot-rest-not-spending
When you run "sudo service hdinsight-hbrest restart" it restarting Region Server and REST API Server. That command or document need to be update to restart only HBase Rest API Server with " sudo /usr/hdp/current/hbase-master/bin/hbase-daemon.sh restart rest" so that we can avoid restarting RS and restart only Rest API Server.
Please let me know if you need more information

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 375421cb-b19d-87f8-dd5a-7fb69c62ad16
Version Independent ID: 6e1d4a1a-8c38-f333-e6ba-2902c37eb71e
Content: Apache HBase REST not responding to requests in Azure HDInsight
Content Source: articles/hdinsight/hbase/hbase-troubleshoot-rest-not-spending.md
Service: hdinsight
GitHub Login: @JasonWHowell
Microsoft Alias: jasonh

@bandarusridhar
Thanks for the feedback! We have assigned the issue to the content author to further  investigate this and update the document as appropriate.


Add option to specify output format in tsSetup.py.

Thanks for confirming @sssangha. Will merge and close.


sw_engine: fix clang compiler warnings.

[29/73] Compiling C++ object src/libthorvg.a.p/lib_sw_engine_tvgSwStroke.cpp.obj ../src/lib/sw_engine/tvgSwStroke.cpp(258): warning C4244: 'argument': conversion from 'float' to 'int64_t', possible loss of data [32/73] Compiling C++ object src/libthorvg.a.p/lib_sw_engine_tvgSwRaster.cpp.obj ../src/lib/sw_engine/tvgSwRaster.cpp(259): warning C4244: 'initializing': conversion from 'float' to 'uint32_t', possible loss of data ../src/lib/sw_engine/tvgSwRaster.cpp(260): warning C4244: 'initializing': conversion from 'float' to 'uint32_t', possible loss of data

I don't get the these warnings (linux clang 16.0.6) but
LGTM.
I only see some in the gl_engine and webp:
CC=clang CXX=clang++ meson setup --prefix=$prefix \
        -Dlog=true -Dbuildtype=debug \
        -Dengines=sw,gl_beta \
        -Dtools=all -Dbindings=capi -Dexamples=true -Dloaders=svg,png,tvg,jpg,webp_beta, -Dsavers=all -Dtests=true \
        $build_dir $src_dir

----

The Meson build system
Version: 1.1.0
Source dir: /home/mc/develop/godot/thorvg-git
Build dir: /home/mc/develop/godot/tvgexa_sbuild_1
Build type: native build
Project name: thorvg
Project version: 0.9.99
C++ compiler for the host machine: clang++ (clang 16.0.6 "Debian clang version 16.0.6 (++20230710041823+7cbf1a259152-1~exp1~20230710161844.102)")
C++ linker for the host machine: clang++ ld.bfd 2.35.2
Host machine cpu family: x86_64
Host machine cpu: x86_64
Configuring config.h using configuration
Library EGL found: YES
Library GLESv2 found: YES
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Run-time dependency libpng found: YES 1.6.37
Run-time dependency libturbojpeg found: YES 2.0.6
Run-time dependency libwebp found: YES 0.6.1
Library pthread found: YES
Run-time dependency elementary found: YES 1.25.1

Summary:
    ThorVG version:        0.9.99
    Build Type:            debug
    Prefix:                /home/mc/develop/godot/tvgexa_64
    SIMD Instruction:      none
    Raster Engine (SW):    true
    Raster Engine (GL):    true
    Loader (TVG):          true
    Loader (SVG):          true
    Loader (PNG):          true
    Loader (JPG):          true
    Loader (WEBP_BETA):    true
    Saver (TVG):           true
    CAPI Binding:          true
    Log Message:           true
    Tests:                 true
    Examples:              true
    Tool (Svg2Tvg):        true
    Tool (Svg2Png):        true

  User defined options
    buildtype: debug
    prefix   : /home/mc/develop/godot/tvgexa_64
    bindings : capi
    engines  : sw,gl_beta
    examples : true
    loaders  : svg,png,tvg,jpg,webp_beta,
    log      : true
    savers   : all
    tests    : true
    tools    : all

----

[8/183] Compiling C++ object src/libthorvg.so.0.9.99.p/lib_tvgGlCanvas.cpp.o
In file included from ../thorvg-git/src/lib/tvgGlCanvas.cpp:26:
../thorvg-git/src/lib/gl_engine/tvgGlRenderer.h:31:24: warning: suggest braces around initialization of subobject [-Wmissing-braces]
    Surface surface = {nullptr, 0, 0, 0, ColorSpace::Unsupported, true};
                       ^~~~~~~
                       {      }
1 warning generated.
[10/183] Compiling C++ object src/libthorvg.so.0.9.99.p/lib_tvgInitializer.cpp.o
In file included from ../thorvg-git/src/lib/tvgInitializer.cpp:36:
../thorvg-git/src/lib/gl_engine/tvgGlRenderer.h:31:24: warning: suggest braces around initialization of subobject [-Wmissing-braces]
    Surface surface = {nullptr, 0, 0, 0, ColorSpace::Unsupported, true};
                       ^~~~~~~
                       {      }
1 warning generated.
[32/183] Compiling C++ object src/libthorvg.so.0.9.99.p/lib_gl_engine_tvgGlRenderer.cpp.o
In file included from ../thorvg-git/src/lib/gl_engine/tvgGlRenderer.cpp:23:
../thorvg-git/src/lib/gl_engine/tvgGlRenderer.h:31:24: warning: suggest braces around initialization of subobject [-Wmissing-braces]
    Surface surface = {nullptr, 0, 0, 0, ColorSpace::Unsupported, true};
                       ^~~~~~~
                       {      }
1 warning generated.
[34/183] Compiling C++ object src/libthorvg.so.0.9.99.p/lib_gl_engine_tvgGlRenderTask.cpp.o
In file included from ../thorvg-git/src/lib/gl_engine/tvgGlRenderTask.cpp:23:
../thorvg-git/src/lib/gl_engine/tvgGlRenderTask.h:58:17: warning: private field 'propertyFormatSize' is not used [-Wunused-private-field]
    uint32_t    propertyFormatSize;
                ^
1 warning generated.
[122/183] Compiling C++ object src/examples/PictureWebp.p/PictureWebp.cpp.o
../thorvg-git/src/examples/PictureWebp.cpp:38:18: warning: unqualified call to 'std::move' [-Wunqualified-std-cast-call]
    canvas->push(move(bg));
                 ^
                 std::
../thorvg-git/src/examples/PictureWebp.cpp:53:26: warning: unqualified call to 'std::move' [-Wunqualified-std-cast-call]
        if (canvas->push(move(picture)) != tvg::Result::Success) return;
                         ^
                         std::
../thorvg-git/src/examples/PictureWebp.cpp:77:18: warning: unqualified call to 'std::move' [-Wunqualified-std-cast-call]
    canvas->push(move(picture));
                 ^
                 std::
3 warnings generated.
[183/183] Linking target test/capi/capiUnitTests
...
1/2 Capi Unit Tests        OK              0.03s
2/2 Unit Tests             OK              0.76s

@capnm  thanks, I recommend turning it off "gl_raster" in the build, it's useless currently.

@capnm thanks, I recommend turning it off "gl_raster" in the build, it's useless currently.

I think it is currently used as a proof of concept, since it is still included in the examples.
How did you get these warnings, which clang version did you use?


index.pl Generates Malfolmed XML: not well-formed (invalid token)

I had a hard time debugging a "not well-formed (invalid token)" error.
Executing "./index.pl" resulted in the error below
not well-formed (invalid token) at line 3, column 19, byte 75 at /usr/lib/x86_64-linux-gnu/perl5/5.34/XML/Parser.pm line 187.
Running the script in in debugging mode helped in identifying the problematic record: for some strange reason, the record entry below resulted in a malformed XML record immediately following it.
You will notice that the malformed XML record has an attribute linked to the title element, probably because the title has an "@" symbol in it.
## Input CSV Record
legacyId|parentId|qubitParentSlug|levelOfDescription|digitalObjectPath|digitalObjectURI|title|description|creator|date
item|etd2019/etd19-2026-paper.pdf||Accesses to ETDs in Languages Other Than Portuguese @PUC-Rio: a Different View|Portuguese is among the 10 world languages with the most native speakers; it is the third Western language in the ranking. At the same time, it is neither the lingua franca of science and technology, nor of the Internet. In Brazil, in the last decade, many institutions started allowing ETDs to be published in languages other than Portuguese; English is the most used. This work addresses characteristics of the ETD collection of a university in Brazil in terms of the languages of the works. An overview of the numbers/percentages of ETDs in Portuguese and other languages is presented in the time frame 2008-2018. Some aspects of the accesses are discusssed too, but they are from 2016 on since before this year the numbers of ETDs in English were very low. The numbers of ETDs in foreign languages – numbers of institutions and of works – in other Brazilian institutions that contribute to the Brazilian national consortium are presented and discussed too.|Pavani, Ana M B|2019

## Malformed XML
<item>
   <levelOfDescription>item</levelOfDescription>
   <title PUC-Rio: a Different View="">Accesses to ETDs in Languages Other Than Portuguese</title>
   <description>Portuguese is among the 10 world languages with the most native speakers; it is the third Western language in the ranking. At the same time, it is neither the lingua franca of science and technology, nor of the Internet. In Brazil, in the last decade, many institutions started allowing ETDs to be published in languages other than Portuguese; English is the most used. This work addresses characteristics of the ETD collection of a university in Brazil in terms of the languages of the works. An overview of the numbers/percentages of ETDs in Portuguese and other languages is presented in the time frame 2008-2018. Some aspects of the accesses are discusssed too, but they are from 2016 on since before this year the numbers of ETDs in English were very low. The numbers of ETDs in foreign languages – numbers of institutions and of works – in other Brazilian institutions that contribute to the Brazilian national consortium are presented and discussed too.</description>
   <date>2019</date>
   <spreadsheet>/etd2019/etd2019.csv</spreadsheet>
   <creator id="internal112">Pavani, Ana M B</creator>
   <view>
      <title>Accesses to ETDs in Languages Other Than Portuguese PUC-Rio: a Different View</title>
      <file>etd2019/etd19-2026-paper.pdf</file>
   </view>
</item>

This is very strange.  It seems to not be the index script that is the problem but the import script, which sees the @ and interprets it as an XPath expression where @ means tag attribute.  I will have to fix import.

So it seems a long time ago I added an attribute facility so if a field is "x" and the value is "a@b@c", it will import as a.  It works for multiple attributes too (e.g., a@b@c@d@e).
I just put in a fix so you can escape the "@" symbol as "@", and of course "\" for "".
It doesn't seem to have broken anything yet :)

So it seems a long time ago I added an attribute facility so if a field is "x" and the value is "a@b@c", it will import as a.  It works for multiple attributes too (e.g., a@b@c@d@e).
I just put in a fix so you can escape the "@" symbol as "@", and of course "\" for "".
It doesn't seem to have broken anything yet :)

Thank you for the fix!


Release pubsub 0.34.0

This pull request was generated using releasetool.

Should the changelog mention #5256?  Or is that a fix to unreleased code?

Should the changelog mention #5256? Or is that a fix to unreleased code?

Its in the one big note that references a lot of PRs.

Got it. LGTM

Release is at https://github.com/GoogleCloudPlatform/google-cloud-python/releases/tag/pubsub-0.34.0


Create use-case focused tutorials

/cc @ahmetb

Off topic question: is the CA integration the primary use case of this project or is it ACME/LetsEncrypt? If latter, it would be nice to have it's tutorial first.

@ahmetb There isn't really a primary integration, just a choice of integrations and more to come :) but there will be an ACME tutorial very soon as part of this PR

/cc @ahmetb

Oh - can we also refer to cert-manager without backticks? Issuer, Certificate and ClusterIssuer (i.e. resource types) I think we should keep in backticks though.

Can we also update the README/move any parts of it that aren't documented elsewhere into a user guide/docs, and link out to these things from the README 😄  would be good to slim that down so users can easily get to the information they are after.

/release-note-needed

/kind documentation

/lgtm


How to change proxy after client build

client build cost 80ms averagely in my computer，I want to replace proxy of the client，but do not re new a client again. It costs too much time for me。Is there any way to just change the proxy of the client?

what i'm facing is, I need to change proxy value frequently. Now i can only do this by creating a new Client,and it cost too many time.All operations after reset proxy is stuck by this recreateing  a new Client.

I find out the Identity obj create costs 80ms,remove it resolve my problem

Still an actual issue.


turned on flutter_engine_group_performance.dart

issue: https://github.com/flutter/flutter/issues/72026
depends on: https://github.com/flutter/flutter/pull/75374

What's the best way to babysit this to make sure it landed well, since a successful local run doesn't seem to guarantee it will run successfully on the bots?

I suspect results should be showing up at https://flutter-flutter-perf.skia.org/e/?queries=test%3Dflutter_engine_group_performance

Before enabling it in flutter-dashboard, milo dashboard is where we check running status: https://ci.chromium.org/p/flutter/g/devicelab/console


Update Symbol.go

Pre-Checklist
Description
Debug and Error were having same symbol type to updating and differentiating it and more appealing.
Related Issues
#646

@daniel-hutao I am confused about the message format. can you provide the format

@daniel-hutao Thanks!

@shubham-cmyk
If you are using goland, you can select the local branch commit, modify the message, and then run git push -f in the terminal to modify the remote commit message.
You can also use the command line to modify the historical commit message, but it's a little more complicated.

@shubham-cmyk Here's a little trick that might help you, use close #646 to automatically close the issue when the PR is merged.
@daniel-hutao #646 is resolved, please close it, thank you!


Change --group syntax

It would be nice to be able to use --groups a b c  instead of --group a --group b --group c

Fixed in #185


tpl: Add reflect namespace

Adds KindIs, KindOf, TypeIs, TypeIsLike, and TypeOf funcs in a reflect
namespace.
Fixes #4081

Thank you! Can you please also add the docs for these functions?

Hold on with the docs until we decide on the API.

As I said in the other PR, we need to be restrictive about adding new template funcs until we fix the docs setup for it.
But we cannot build an API where the user has to set up conditionals with this hefty list:
* array
 * bool
 * chan
 * complex128
 * complex64
 * float32
 * float64
 * func
 * int
 * int16
 * int32
 * int64
 * int8
 * interface
 * invalid
 * map
 * ptr
 * slice
 * string
 * struct
 * uint
 * uint16
 * uint32
 * uint64
 * uint8
 * uintptr
 * unsafePointer

We need to discuss a simpler API. But that will have to wait.


Spawn multiple items

hello  I want to know spawn ammo Problem   Only one can be produced at a time

And instead of spawning one bullet, why not spawning an ammo pack ?

but  i spawn ammo pack   There's no ammo in there.  if spawn 5.56 sp

I see, I'm going to have a look.

I update the code see https://github.com/sailro/EscapeFromTarkov-Trainer/commit/352f4eaded9d30dff8446239b8731f3b3d2c284b
Now when you spawn magazines or ammo packs, they will be automatically filled with compatible ammunition.
This will only work with the upcoming SPT-AKI 3.10 (I did not backport to the current stable 3.8 given we made a lot of changes regarding the spawn logic).


Update dockerfile setup to use mamba

With packaging updates for different min versions in dask-sql the conda solver fails to solve properly in our dockerfile setup. Switching to mamba seems to resolve this.

Codecov Report

Merging #583 (1c16a30) into main (0db4506) will increase coverage by 0.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #583      +/-   ##
==========================================
+ Coverage   88.45%   88.60%   +0.14%
==========================================
  Files          69       69
  Lines        3500     3500
  Branches      707      707
==========================================
+ Hits         3096     3101       +5
+ Misses        317      308       -9
- Partials       87       91       +4

Impacted Files
Coverage Δ

dask_sql/_version.py
34.00% <0.00%> (+1.44%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

@ayushdg this is marked as a draft but seems ready. Are you ready for a review?

@ayushdg this is marked as a draft but seems ready. Are you ready for a review?
Not yet. The core issues is fixed but I'm also trying to update GitHub actions to test docker changes if those files are touched and I need to resolve some issues there.

This isn't my area of expertise but wanted to say thank you @ayushdg because I will definitely be consuming this and benefiting!

Going through the errors. It looks like docker cloud step still seems to be trying to fetch some image information from docker hub instead of using the image that is present locally (loaded at the previous step). Pinging @jacobtomlinson in case you have any suggestions on how we can use the image generated in the main step for a subsequent step without pushing to docker hub.


Stop macroizing inline in C++

See #279

Build finished. No test results found.

Reviewed and approved for merge.