Update gazebo keys.

Remove key for gazebo5.
Remove key for gazebo7.
Update key for gazebo9.

Remove definition for out-of-support Ubuntu Artful.
Add definition for Ubuntu Focal.

Update key for gazebo11.

Change Gentoo key to unversioned gazebo.
Add definition for Debian Bullseye.
Add definition for Ubuntu Jammy.

Update key for gazebo.

Drop definition for Debian Jessie.
Drop definition for Debian Stretch.
Remove archlinux definition as it is no longer packaged.
Add definition for Debian Bullseye.
Add definition for Ubuntu Jammy.

@chapulina would you mind providing an extra set of eyes on this one?

Pulled this change back into draft for now.

This has been superseded by https://github.com/ros/rosdistro/pull/32481


Contains Duplicate

Added solution for 217. Contains Duplicate

Added the JAVA solution for leetcode 217. Contains Duplicate


Add connection-manager

Due to a more and more occuring problem with stalled connections we need a connection-handler that does the following:

modularize ajax-calls including better error-handling and removing the redundant code
prioritize tasks (i.e. market-listings are more important than retrieving API-Data for your accounts)
slots for community and store (max. 6 per domain)

modularization added
needs additional error-handling


Add type hints to src/microprobe/model folder

This commit is stacked on top of #47. Once merged, this change can be rebased to remove the extra commit.
This adds types and enables mypy type checking for src/microprobe/model.

Rebased to only contain 1 commit

CI failure is flaky/appears unrelated to this change. The issue is microprobe is trying to put 4096 into a 12 bit register (0-2095 range). I'll send a follow-up PR to fix this.


Error

I m facing some error while running a command on console.

@ishagpt
Hi! What kind of error did you get?

Closing because this is a stale issue. Please re-open if issue persists.


Constant Name Change in AuthenticationRealm

Changed the name of a private internal constant of the AuthenticationRealm class to match it's purpose.

👍 Thanks!

Fixed by https://github.com/apache/shiro/pull/120


Stats page: Error Loading Chart: No charting library found for t

The upgrade to Ruby 2.5.0 has produced a new problem; chart displays instead show:

Error Loading Chart: No charting library found for t

This problem does NOT occur on local execution (which works fine).

Updating the chartkick gem (which just got released) appears to fix the problem.
This is exactly why we delay updating key infrastructure components like Ruby - we want to let other people find and fix the problems first.

Having this same issue while running Rails 5.2.3, Chartkick 3.3.0 specifically for the Timeline.
I noticed the site http://sir5.webvision.co.kr/sample_plugin/chartkick.js-master/examples/ is having the same issue with the Timeline, and no other graphs. Could you confirm whether this is a bug?


[ICD] Add skeleton logic for check-in send

Partial fix for #24243

Closing PR since out of date. Real fix will be coming up before end of week


Array#union and Array#difference

I have implemented an Array#union and Array#difference in C and I sent some months ago two PRs to Ruby core:

https://github.com/ruby/ruby/pull/1747
https://github.com/ruby/ruby/pull/1758

Although array1 | array2 is already available in Ruby, array1.union array2 is much more readable and elegant, following the easy to use and to read Ruby principle. It also supports more than two arrays, and for more than two arrays this C implementation is more efficient than |. It is also coherent with Array#concat
Although I would really like to see this code in Ruby core, it seems that this won't happen. There is an issue in Ruby: https://bugs.ruby-lang.org/issues/14097 Here someone against having this method in Ruby suggested that I create my own gem for that. I really don't see the point in creating a gem only for that, but this project may be a good place for it. :blush:
I could send a PR if you want the methods here. That would imply having C code in this gem.

@Ana06 Sorry for the slow response!
I like those suggestions, I'm just wary of using C extensions - we'd always need to have some fallback to pure Ruby, so those methods would work on alternative runtimes.
PR welcome!

It got merged in Ruby: https://github.com/ruby/ruby/pull/1747! :tada: So there is no need to add it here anymore. Thanks anyway :kissing_heart:

Great news!
A problem that solves itself - sounds like a job for me! 🤣


Import .json

Thank you very much for making this tool, but I have a doubt, how do I import the extracted .json file!
I exported all dialogs, but I don't know how to import them all at once!

You can import UAssetAPI .json files in UAssetGUI by going to File --> Open and selecting the respective .json file


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 10:42:29 on 2023.07.25
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 3, errors out: 0
Original problem ID: 33073
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=33073

Problem has been resolved in 6m 0s at 10:48:29 on 2023.07.25
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 33073


Hints show regardless of selected item

Examples

Facing water shows a hint for water even though you're not carrying a bucket
Facing trees shows a hint to chop them down even if you don't have the axe selected

Hints are removed so this isn't an issue


Encoding json data using guzzle 'json' option does not preserve float values.

Guzzle version(s) affected: 6.3.3
PHP version: 7.3.6
cURL version: 7.64.0 (hint: php -i | grep cURL)
Description
Guzzle allows for a 'json' parameter to be passed to a request in order to easily upload JSON encoded data as the body of a request.
This encodes the data in https://github.com/guzzle/guzzle/blob/db9e56915c44625a19fad8b5948f7ca039673fc5/src/Client.php#L378 without specifying JSON_PRESERVE_ZERO_FRACTION option (see: https://www.php.net/manual/en/json.constants.php).
This results in PHP values: (float)5.0 and (int)5 being represented identically in the transferred JSON data.
As a result, when I retrieve the guzzle encoded string in another PHP script and decode the data using json_decode() in both situations I end up with integer values.
How to reproduce
$data = file_get_contents('php://input');
if ($data) {
    var_dump($data, json_decode($data, true));
} else {
    $client = new GuzzleHttp\Client();
    $response = $client->request('POST', "http://{$_SERVER['HTTP_HOST']}/", [
        'json' => ['string' => "5", 'integer' => 5, 'float' => 5.0]
    ]);
    echo $response->getBody()->getContents();
}

will return:
string '{"string":"5","integer":5,"float":5}' (length=36)
array (size=3)
  'string' => string '5' (length=1)
  'integer' => int 5
  'float' => int 5

Possible Solution
add JSON_PRESERVE_ZERO_FRACTION to json_encode (or an option to do so).

In Guzzle json is very simple, it's translated to a json_encode() call with default options set (as you already noticed). If you want a more complex, specific behaviour, just use json_encode() directly with the body option:
$response = $client->request('POST', "http://{$_SERVER['HTTP_HOST']}/", [
    'body' => json_encode(['string' => "5", 'integer' => 5, 'float' => 5.0], JSON_PRESERVE_ZERO_FRACTION),
    'headers' => ['Content-Type' => 'application/json']
]);

The issue was already discussed in #2343, and until now we haven't found a solution that is flexible and (at the same time) doesn't add unwanted complexity. Maybe the best solution is to remove json option at all, because the same question is being asked again and again... Not sure.

To be clear: we are not going to add configurable options for json_encode() (at least now), so I'm closing the issue.
I also don't think that the default options set for json_encode() should be changed (to include JSON_PRESERVE_ZERO_FRACTION). If other maintainers think differently, feel free to reopen.


Add Google-style NRQL calculated latency SLO option

Summary
Currently, the 'Latency' SLO type is calculated based on alert violation duration. I want to change or add an option to calculate Latency with NRQL similar to how the 'Error' SLO type already works.
Desired Behaviour
I want to define Latency SLOs as "The proportion of requests that were faster than some threshold." The threshold should be configurable. In many cases, I would like to define a p95 and p99 SLO against the same SLI.
In general, the user experience should be the same as creating an 'Error' SLO type, except with an additional field for threshold duration.
Possible Solution
I believe generating a NRQL query similar to the one below from the GUI wizard will accomplish this goal. This query returns the percentage of requests with a duration under 5 seconds from a list of transactions provided by the user. The duration threshold and transactions should both be configurable by the user.
SELECT (filter(count(*)), WHERE eventtype() = 'Transaction' AND duration < 5) / filter(count(*), WHERE eventtype() = 'Transaction'))*100 FROM Transaction WHERE {transactionNamesGoHere}
(If this doesn't do what I think it does, please let me know!)
Additional context
I can probably do the PR on this, but I wanted to open up discussion first to make sure I'm on the right track (and also to decide what to name the new SLO type). Any thoughts, concerns, or conflicts with other planned items I should be aware of?
@gem-wang This is the issue I referenced in our conversation this afternoon.
@kaprah, @t-morgan Please add any additional context or requirements I've missed.

I've been familiarizing myself with the code today, and it looks like there are two options for implementing this.

Copy the code already written for error budget SLOs and modify it to support latency SLOs. If the two are likely to diverge in the future, this might be cleaner, at the cost of repeating ourselves.

Modify the error budget code to accept 'duration > $variable' as a defect, and re-use the existing error budget code. Since I don't see any real difference between 'HTTP 500' and 'duration > $variable' when it comes to calculations and alerting, this seems like a better option.

Any thoughts? If not, I'll start working on the second option later this week.

@andrewseling I don't think I fully understand your second option. I think first option is good. We can parameterize the error budget calculation logic, and then provide an option to call that from latency SLO calculation as well. That way, we are not repeating ourselves, just provide another way of calculating latency.

Hey @andrewseling - I was just testing the PR and ran into a couple of issues with the SLO definition. I am going to schedule some more time to review but it might be a couple of days before it gets merged. Just wanted to give you the the heads up.

and thanks fort this submission, this is awesome!

@ricegi, not sure if you saw my comment on the PR - there are some calculation issues I haven't figured out yet. I'll mark the PR as ready to review when they are fixed. Thanks!


#144937457 Game landing page

What does this PR do?

Users should see a landing page with effective UI/UX

Description of Task to be completed?

As a user, I want to see an attractive UI design of the landing page, with an effective UX experience

How should this be manually tested?

N/A

Any background context you want to provide?

N/A

What are the relevant pivotal tracker stories?

#144937457 Users should see a landing page with effective UI/UX

Screenshots (if appropriate)

Questions:

Coverage remained the same at 0.0% when pulling cbd2e28cb580446cdc6daceb2cc704a1a097f279 on feature/144937457/design-game-landing-page into 4953b41b76f5955f966b99ae536fbcbca3959547 on staging.


Added Shell Sort

Please star this repository to show your support, in the meantime I am reviewing your code.


feat: update applications:list to newer ListApplicationsV2 endpoint

Added filters in applications:list according to the new applicationsList Mix API

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Move non-core DNS zones outside network module

What is being addressed
We create many objects in the network module that cause delays on its completion but aren't really required to be provisioned there.
How is this addressed

Split out all DNS zones not required for the core applications, and move them out of the network module. This allows TF to better manage dependencies and on some scenarios expedite deployment (as many things are waiting for the network module).

/test

/test

/test

/test

/test


Add .editorconfig for contributors

This helps contributors keep consistent with the project style. For now it's just tabs, but it helped with my latest PR :smile:

Thanks

Yay! :+1:


Update card-section-images.mdx

update intro and add design spec file link
Related Ticket(s)
{{Provide url(s) to the related ticket(s) that this pull request addresses}}
Description
{{Add a human-readable description / detail summary of what the PR is changing and any details around how and why}}
{{If applicable, include a screenshot indicating an example or examples of what the PR is changing in the application}}
Changelog
New

{{new thing}}

Changed

{{changed thing}}

Removed

{{removed thing}}

@jeffchew Ready for review. ;-D


Blake

Merged Blake and master all the migrations are in line with the table designs for users. Now will run the migrations to check and see if the tables are created and used in the expected manner"


Added PreparedStatement parameter functionality

Extended PreparedJdbcStatement funcitonality to actually allow parameters to be passed in the SQL string.
Modified a number of methods such that rather than returning null or performing a no-op, a NotImplementedException would be thrown to better inform of the current implementations limitations in some areas.

Apologies for not adding more integration tests with a real instance

Hi Chris - thanks for the merge request! We will review it shortly!


There is a problem with window closure

@Type: Bug
After I clicked on the "Settings Selection" button to open the "Settings Synchronization" function, the pop-up "Settings Synchronization" window did not click to close this function. Moreover, you are not the only one who has this feature, but many pop-up windows have not closed this option. Every time you need to close the VScode software, it is very troublesome and inhumane. I hope you can consider optimizing this aspect after seeing this message, thank you
VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:59:02.252Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.80GB (6.66GB free)

Process Argv
--crash-reporter-id f4e02fb5-e064-4755-8bbc-24acc15b496c

Screen Reader
no

VM
0%

Extensions (19)

Extension
Author (truncated)
Version

codesnap
adp
1.3.4

path-intellisense
chr
2.8.4

prettier-vscode
esb
9.12.0

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

React-JS-Snippet
Gaj
3.0.54

html-snippets
gey
0.2.3

vue-snippets
hol
1.0.4

vscode-language-pack-zh-hans
MS-
1.74.12140931

vscode-vue2-snippets
Nic
1.3.2

LiveServer
rit
5.7.9

px-to-rem
sai
1.3.1

easysass
spo
0.0.6

code-spell-checker
str
2.20.3

open-in-browser
tec
2.0.0

vscode-icons-mac
way
7.25.3

vue
Wsc
1.0.26

axios-snippets
Ygg
1.0.0

vscode-preview-server
yui
1.3.0

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vscaac:30438847
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
282f8724:30602487
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
showlangstatbar:30737416
azdwalk:30721579
pythonms35:30701012
pythonfmttext:30731395
fixhidewlkth:30730051
showsbindicator:30730056

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thank you for your suggestion, but my friend is already the latest version and still has this issue. Therefore, I don't think it's a version issue. I hope you can try this issue again because vscode is indeed a great programming software and many people around me are using it. If this issue can be improved, I think the user experience will be greatly improved. Finally, thank you very much for your reply to me.
------------------ 原始邮件 ------------------
发件人:                                                                                "microsoft/vscode"                                                                                @.>;
发送时间: 2023年5月11日(星期四) 中午11:26
@.>;
<EMAIL_ADDRESS>主题: Re: [microsoft/vscode] There is a problem with window closure (Issue #182146)
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

dfhfghdfgh

dfghdfghdfg

Hi, does pressing the Escape key work instead?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Computing mutual information in loss function looks impossible to me with current library

Hi everyone. I would like to ask if there is anyone around who can help me with this problem. I would like to create a custom loss to implement the mutual information of y_true and y_pred, i.e.
I(y_true; y_pred) = H(y_true) - H(y_true|y_pred) = I(y_pred; y_true).
H is the Shannon entropy and H( | ) is the conditional Shannon entropy. y_true is a one hot tensor and y_pred is a tensor output by a softmax layer (4 classes classification problem).
Now this is pretty straightforward with python but, when it comes to using the functions for tensors provided by tensorflow, I always get stuck.
In particular if I compute the entropies I don't know how to represent the conditional probabilities (not even if I try to switch to the joint probability or better frequency since I am working with classes and we could count the occurrences).
I have also tried to switch to the Kullback–Leibler divergence formulation of the mutual information https://en.wikipedia.org/wiki/Mutual_information#Relation_to_Kullback–Leibler_divergence. But once again I got stuck. I wish there was a more straightforward way to understand how to use the tensorflow functions. Sometimes the man pages are not enough for me to fully understand things. I have been stuck on this for a few days and I really don't see any real way to overcome the obstacle. Any hint is very much appreciated.
Don't hesitate to ask if you need further details.

Hi!
This issue isn't related to a bug/enhancement/feature request or other accepted types of issue.
To ask questions, please see the following resources :
StackOverflow
Keras Slack channel
Keras.io support
Gitter
Thanks!
If you think we made a mistake, please open another issue explaining your request in detail.


chore: remove call to git at every submethod

Let's catch up with @kumarabd on this. The git command is being invoked to facilitate realistic responses to the mesheryctl version command while developing. Before removing entirely, a short discussion on alternative approaches would be good.

This runs the git command at every make command from which it is removed, I
dont suppose we need to show the version details unless user wants to know.
On Tue, 14 Jul, 2020, 20:47 Lee Calcote<EMAIL_ADDRESS>wrote:

Let's catch up with @kumarabd https://github.com/kumarabd on this. The
git command is being invoked to facilitate realistic responses to the mesheryctl
version command while developing. Before removing entirely, a short
discussion on alternative approaches would be good.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/layer5io/meshery/pull/1258#issuecomment-658240611,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLQJPL7A4AZVPAJXRFLR3RZIHANCNFSM4OX3XR7Q
.

This may be a conversation we should pick up on in Slack or on Wednesday’s dev call, as I suspect, a verbal discussion may help.
In essence, the git routine was included by Abishek to improve the developer experience in particular for the mesheryctl version command. This was a recent need for Abishek when he was creating the server-side version lookup.

@kushthedude  In which scenario do you not want the version to be displayed? Because I had added the git command to inject client version for every build, on the idea that any binary that is been built should be associated with a version so that it will be easier to figure out which one we are using.

@kushthedude  In which scenario do you not want the version to be displayed? Because I had added the git command to inject client version for every build, on the idea that any binary that is been built should be associated with a version so that it will be easier to figure out which one we are using.

Does this mean that call on every make action like make run-local, make run-cloud etc is just added to inject the client version?
We would just want to to show these details when mesheryctl -v is invoked.

Yes, this needs to be done during the build time because once the binary is out we won't be able to fetch the git details. Also this needs to run on every make command because we consider each of them as an independent build, meaning each make produces it's own binary version of it. @kushthedude  if you have a better suggestion on handling this please pitch in.

Can we invoke it in the dockerfile ? As for Meshery Users, the version output will not give server-version.

@kushthedude I can put it in the dockerfile however it will be needed for non-docker builds. Let me make some quick changes for this.

@kushthedude I can put it in the dockerfile however it will be needed for non-docker builds. Let me make some quick changes for this.

non-docker as if development binary created for development or testing purpose on local, right @kumarabd ?

@kushthedude  yes that's correct. Or if someone doesn't want a  docker build instead they are using a different container orchestration.

@kushthedude yes that's correct. Or if someone doesn't want a docker build instead they are using a different container orchestration.

Then we need to have a discussion on this rather than moving forward with this PR

Then we need to have a discussion on this rather than moving forward with this PR
Sure, Lets catchup sometime to discuss on this.

Not required now!


 fallbacks cause Content Security Policy to report

The following ASP code to provide a CDN fallback causes script-src CSP to block loading of the resource
		@*Font Awesome*@ 		<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css" 			  asp-fallback-href="~/lib/font-awesome/css/font-awesome.min.css" 			  asp-fallback-test-class="sr-only" asp-fallback-test-property="position" asp-fallback-test-value="absolute"/>
Which upon HTTP request produces;
<meta name="x-stylesheet-fallback-test" content="" class="sr-only" /><script>!function(a,b,c,d){var e,f=document,g=f.getElementsByTagName("SCRIPT"),h=g[g.length-1].previousElementSibling,i=f.defaultView&&f.defaultView.getComputedStyle?f.defaultView.getComputedStyle(h):h.currentStyle;if(i&&i[a]!==b)for(e=0;e<c.length;e++)f.write('<link href="'+c[e]+'" '+d+"/>")}("position","absolute",["\/lib\/semantic\/dist\/font-awesome.min.css"], "rel=\u0022stylesheet\u0022 ");</script>
The web browser console;
Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src https://<somesubdomain>.azurewebsites.net https://cdnjs.cloudflare.com https://ajax.cloudflare.com https://ajax.aspnetcdn.com https://www.google-analytics.com”).  <PageName>:15
Is there a way to include a nonce, or would the only work around for this be to add inline-unsafe?
Thanks.
Boz.

This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain spinthemoose.com has exceeded the max emails per hour (203/200 (101%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from o11.sgmail.github.com ([<IP_ADDRESS>]:33864)
by cp1164.blacksun.ca with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89_1)
(envelope-from<EMAIL_ADDRESS>id 1eVQfD-0000AJ-Vi
for<EMAIL_ADDRESS>Sat, 30 Dec 2017 17:35:40 -0600
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=Xdn3reMAgva9p2wKZi2aUdQ88XA=; b=MkFH7TxSD041PScp
Osmw2RGW2wsdt+VSE6HFp/XgdVq+BVnXl+Shh0FYsgmUslfk5MVTeLjh3glyFBTs
gSfvO9xZ7EOs/yG39fGhFKz2oUFv+wzsUdqQMQLByDV3uMGXwRUtbccZRNrEPDY2
npHiSi+0GNDuUMlzaJHPqK5DyS4=
Received: by filter0945p1mdw1.sendgrid.net with SMTP id filter0945p1mdw1-16289-5A4822B7-10
2017-12-30 23:35:19.632122686 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id 1lB25qFOSVSbT_hZ7XtwCQ
for<EMAIL_ADDRESS>Sat, 30 Dec 2017 23:35:19.598 +0000 (UTC)
Date: Sat, 30 Dec 2017 23:35:19 +0000 (UTC)
From: "ASP.NET Hello Bot"<EMAIL_ADDRESS>Reply-To: aspnet/Home<EMAIL_ADDRESS>To: aspnet/Home<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [aspnet/Home]  fallbacks cause Content Security Policy to
report (#1951)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5a4822b778d76_24893fb62e086f282203419";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: aspnet-hello
X-GitHub-Recipient: davidalpert
X-GitHub-Reason: subscribed
List-ID: aspnet/Home <Home.aspnet.github.com>
List-Archive: https://github.com/aspnet/Home
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AACpRIxY5_lKr7MtpCBwaS72QzwqcLXtks5tFsi3gaJpZM4MUFlS
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: rlj3t9ahcX0BZUzAOlajQ3VmBXo43xFJc4M1ImIDJhFBjWI4SneNBZKk8phmRU4QFhVhB50FUYWIum
qOwcE2h5GWtX3CxRuNdM2/k0ZivkQGtteDjAxQ1Q3gg82ygDgdHIhtM4DrA3lHrqJjj7V/zyMVy+fD
mmiqPgQneH1bwzLBd4YPbrhw4OtaLqeRyAvzCY88ul7fozXpLr036YW15Yxll4CgBZMpLYJoj8klup
0z08ffXlvOB9RgPIrcpbeu
----==_mimepart_5a4822b778d76_24893fb62e086f282203419
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/aspnet/Home/issues/1951#issuecomment-354574872
----==_mimepart_5a4822b778d76_24893fb62e086f282203419
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
This issue is being closed because it has not been updated in 3 months.<=
/p>
We apologize if this causes any inconvenience. We ask that if you are st=
ill encountering this issue, please log a new issue with updated informatio=
n and we will investigate.
&mda=
sh;You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, view it on GitHub, or mute the thread.

=
----==_mimepart_5a4822b778d76_24893fb62e086f282203419--

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain spinthemoose.com has exceeded the max emails per hour (202/200 (101%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from github-smtp2-ext2.iad.github.net ([<IP_ADDRESS>]:36218 helo=github-smtp2b-ext-cp1-prd.iad.github.net)
by cp1164.blacksun.ca with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.89_1)
(envelope-from<EMAIL_ADDRESS>id 1eVQfD-0000AI-9Y
for<EMAIL_ADDRESS>Sat, 30 Dec 2017 17:35:39 -0600
Date: Sat, 30 Dec 2017 15:35:19 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1514676919;
bh=nLaudiXYF5SBY/AdfEtHVe/ZR1gz8YexpD2av7/158w=;
h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=H03UoaPpLIf2zP4qamQNha4S5eRksAQvilUaWd9LzKSuBjZ3nukiUfn4I+Ne0e7Cc
ot95UfjqysnZ1k1DEvw/a6dNXoIbFgD1w2/tS7KiS68DLZrjErhjs/hIU5/7B3ZHCj
nqeXodLIa01dM3WhiLd14aILAfFKkx1XctN+Soso=
From: "ASP.NET Hello Bot"<EMAIL_ADDRESS>Reply-To: aspnet/Home<EMAIL_ADDRESS>To: aspnet/Home<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [aspnet/Home]  fallbacks cause Content Security Policy to
report (#1951)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5a4822b75b4aa_4e263fcebbd0ef343870a5";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: aspnet-hello
X-GitHub-Recipient: davidalpert
X-GitHub-Reason: subscribed
List-ID: aspnet/Home <Home.aspnet.github.com>
List-Archive: https://github.com/aspnet/Home
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AACpRIxY5_lKr7MtpCBwaS72QzwqcLXtks5tFsi3gaJpZM4MUFlS
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>----==_mimepart_5a4822b75b4aa_4e263fcebbd0ef343870a5
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #1951.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/aspnet/Home/issues/1951#event-1405207936
----==_mimepart_5a4822b75b4aa_4e263fcebbd0ef343870a5
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #1951.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a4822b75b4aa_4e263fcebbd0ef343870a5--


Integrate with Stream Settings

Fixes #213
Changes

Additionally to the Settings in Account -> Account Settings -> BTTV, this PR adds a subset of the settings to the Stream Settings menu.
Checklist

[x] My change builds
[x] I tested my change
[x] I use the "bttv_" prefix for all resources I propose
[x] When adding a string I also added it to the bttv.Res.strings Enum and res/values/strings.xml (in mod) and res/values/public.xml (in disass)
[x] If my change is significant enough, I added it to the CHANGELOG.md under master
[ ] I'll add myself and everyone else who contributed to this change to the contributors list using all-contributors
[x] I license my changes acording to the MIT License.

@all-contributors please add @Jfamig for Ideas


Textline Prediction Fine Tuning

Firstly, thank you for this project! It's really cool.
I see in your README that you fine-tuned a previously trained textline detection model resulting in your final "newspaper textline" model. After digging into DH Segment's references, I believe the original model came from READ-BAD/ARU-Net by Grüning et el. Correct? Given this information, could you give me some tips on how I might now be able to fine tune your textline detection model with my own dataset? Do you have any code you might be willing to share?
Thanks!

Dear Olivia,
"newspaper textline" model use a similar model structure as Dhsegment [https://github.com/dhlab-epfl/dhSegment ] but ours is deeper. And the encoder part is benefited from pre-computed weights. So in fact it is not fine-tuned from an older textline model..
You can train your own model or fine-tune our model using pixelwise segmentation [https://github.com/qurator-spk/sbb_pixelwise_segmentation].

Dear Olivia,
"newspaper textline" model use a similar model structure as Dhsegment [https://github.com/dhlab-epfl/dhSegment ] but ours is deeper. And the encoder part is benefited from pre-computed weights. So in fact it is not fine-tuned from an older textline model..
You can train your own model or fine-tune our model using pixelwise segmentation [https://github.com/qurator-spk/sbb_pixelwise_segmentation].[](Dear Olivia,
"newspaper textline" model use a similar model structure as Dhsegment https://github.com/dhlab-epfl/dhSegment  but ours is deeper. And the encoder part is benefited from pre-computed weights. So in fact it is not fine-tuned from an older textline model.
You can train your own model or fine-tune our model using https://github.com/qurator-spk/sbb_pixelwise_segmentation .

Thank you!!


Smallest React example?

So I'm a bit new to React and am probably wrong about this. That's why I'm creating an issue instead of straight up making a PR.
But isn't the smallest React example technically this:
ReactDOM.render(

Hello, world!
,
  document.querySelector('body')
);

Instead of this:
https://github.com/reactjs/reactjs.org/blob/77d3c2fa8e7f8bd26336b652d21336b3d13f682d/content/docs/hello-world.md  (the first paragraph).
I'm not talking about querySelector being 1 character shorter than getElementById, that's a bit of a technicality and can even be shortened to document.body.
What I mean is that you don't expect anything to be in the DOM. You just render everything in the body.

Hi! I think it is a good idea, but react has context. So if you render your app in body you will not paste a container for context content as there will not be a space.

Typically you don't want to render into the root node because portals and other things can be appended as children of document.body, as well as script tags that you don't want to put into the document head.

will not paste a container for context content as there will not be a space.

Hi! I think it is a good idea, but react has context. So if you render your app in body you will not paste a container for context content as there will not be a space.

I made a mistake:) not context, portals, of course


unhashable type using python 3.10.7 trying to compile pokestadium repo

File "/usr/local/lib/python3.10/dist-packages/spimdisasm/mips/symbols/MipsSymbolFunction.py", line 173, in analyze
funcSym.referenceFunctions.add(self.contextSym)
TypeError: unhashable type: 'ContextSymbol'
make: *** [Makefile:74: split] Error 1
is there a required python version to use or is there plans to update to work with newer versions

I released a new version (1.6.2) which in my local testing fixed the issue, could you confirm if it fixes the issue for you too?
You should be able to install it with either of this two commands:
pip install spimdisasm -U

pip install spimdisasm==1.6.2

pip install spimdisasm==1.6.0
that did work with the pokestadium repo! :)
I also tried the newer versions you suggested, but they seem to not resolve the issue yet so newer versions and possible certain older versions break functionality. would be something to look into for sure.

I'm not able to reproduce the problem with 1.6.3, I just tested 1.6.3 on pokemon stadium and it seems to work fine

1.6.3 now works i verified as well. very interesting! i dont know what could have caused that to be honest maybe the environment didnt update properly after switched versions all i can think of. but it seems to be resolved now!

Happy to hear that!

thank you for responding so fast and being active! always good to see and very helpful too!


Screen flashing

<IP_ADDRESS>8~9d99c25
Does anybody notice the screen flashing a little?
Seems to start after you queue a picture, and doesn't even stop even after you finally upload it.
Flashes about once per second.

Sure, WAI perhaps. However many users will take their cell phones to the repair shop asking if there's something wrong with their battery.

It happens sometimes to me too @jidanni , thanks for reporting it

It happens to me all the time too.
It might or might not be related to #3959.

@nicolas-raoul  @neslihanturan  @jidanni Can you give some more details on how to reproduce this issue?

@gouri-panda Just install the app and open it.
I guess it only happens with accounts that have uploaded already 10 or more pictures. Feel free to upload 10 or 20 of these pictures, using their filename (without the extension) as a title and "Tokyo" as category: https://drive.google.com/drive/u/1/folders/1T5wfM16qb78XCvnf1Zunww4neg8BXJj6

Hey, @nicolas-raoul
Can I work on this issue ?

@4D17Y4 Yes, thanks :-)
Can you see the issue happening? You might have to upload a few pictures before that happens, please see my comment above.

Yes, I can see it.
@nicolas-raoul
There are two thinks playing there part here.
First one is the recycler view whose default animation on uploading is making the screen flash.
Secondly its the SimpleDraweeView used for image which flickers on upload.
So, I was wondering if we want no flickering at all or only the image to flicker on upload.
According to me the flicker on image looks good, suggesting that the image is being loaded.
What to go for ?

Thanks for the investigation and for confirming, great way to proceed!
We want no flicker at all :-)
The progress bar is there to indicate that the image is being uploaded.

@4D17Y4 Thousands of thanks, the scrolling is so nice now! :-)


Attach env variable to sub commands and don't change the current environment

Hopefully will help for Unregistered driver: libvirt errors in crc CI.

This cannot be the solution. Giving up on this PR which was a nice to have.


[Question]: mixture of Agents inside React Agent

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
Hello,
How can we include mixture of Agents inside the React agents??
Please if any body knows let me know.

You could implement a CustomLLM that implements the mixture of agents. Then you can use that LLM in react (or anywhere else)

https://docs.llamaindex.ai/en/stable/module_guides/models/llms/usage_custom/?h=customllm#example-using-a-custom-llm-model-advanced


It seem this fencing agent does not support China Azure

I tried to setup the fencing agent and always failed. there is Azure 90002 error of 'cannot find my tenantId'.  I found an interesting log as "INFO: Starting new HTTPS connection (1): login.microsoftonline.com", but login address of China Azure is https://login.partner.microsoftonline.cn/. I'm wandering if this is supported in China Azure.

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

ID: 4944388b-d40b-5b9f-0ff0-da3cba634113
Version Independent ID: f1c5a805-79ac-4f16-3aa2-83d0080b01a5
Content: Configure availability groups for SQL Server on RHEL virtual machines in Azure - Linux Virtual Machines
Content Source: articles/virtual-machines/linux/sql/sql-server-linux-rhel-ha-stonith-tutorial.md
Service: virtual-machines-linux
Sub-service: ****
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@Joe-TJ
Thanks for the feedback! We are currently investigating and will get back on this.

Hi @Joe-TJ! Thanks for bringing up this issue. Unfortunately, we don't list whether certain regions are supported in individual docs, and this will need to be taken up with the Azure team. I have redirected Vikas to follow-up internally. I will close this issue for now, as this is not a Documentation issue. We're sorry for the inconvenience.
@VikasPullagura-MSFT - Please follow-up internally if you have any questions.
#please-close


[Feature Request] Add planes

Is your feature request related to a problem? Please describe.
We have land transport (trains), water transport (boats), and air transport (kinda, with cable cars). I feel like air transport could be expanded on with planes. Also, it helps with the progression of transportation (walking, boats, horses, trains, planes)
Describe the solution you'd like
We should add planes too!
Additional Information
N/A

Already Done

When was the update including this released? I don't seem to have it.

Ah, I found it, thanks!


FIX: [CADT] Investigate memory usage on observer node deployment

Let's check again before xmas break and determine if this is still happening on observer node with new sync

Current memory usage is 938 MB.  Checking again in a week.


CLA Manager/CLA Signatory is able to sign for a company a project with only ICLA template

Background

Launch Project Console

Login as Project Manager

Click on Foundation/External Project

Add CLA Group with only ICLA enabled and other required configuration for e.g Issue666

Logout

Launch Corporate Console

Login as CLA Manager/ CLA Signatory

Click on the Company

Click on SIGN NEW CLA

Search and Select the project (for e.g Issue666)

Sign CLA

CLA Manager/CLA Signatory is able to sign a project with only ICLA enabled for the company

@wanyaland can you please review and diagnose the issue and formulate a solution?

@deelako During the signing process only unsigned projects for the company are returned and this can be filtered down to projects that have the project_ccla_enabled flag set to true

@nirupamav Could you verify ?

Verified and observed that only ICLA enabled projects are not displayed in project list in Corporate Console to Sign a CLA for a project

Also verified that projects with only CCLA or projects with both CCLA and ICLA are displayed in the projects list


[Regression][ffmpeg-qsv][DG2]Many cases fail by "4bb7c228"

System information

CPU information(cat /proc/cpuinfo | grep "model name" | uniq):
GPU information(lspci -nn | grep -E 'VGA|isplay):
Display server if rendering to display (X or wayland):
Good VPL runtime version?
Bad VPL runtime version?
Underlying media stack (libva/libgmm/media-driver) version?
libva:97cbc87c9435
gmmlib:3c41a692b68d
media-driver:929866c80d13

Issue behavior
Describe the current behavior
We have caught a large number of failure cases in BAT, including part of encode and almost all Vpp on DG2.
such as :
ffmpeg -hwaccel qsv -init_hw_device qsv=qsv,child_device=/dev/dri/renderD128 -hwaccel_output_format qsv -v verbose -f rawvideo -pix_fmt nv12 -s:v 1280x720 -i input.yuv -vf 'format=nv12|qsv,hwupload=extra_hw_frames=16,vpp_qsv=detail=0,hwdownload,format=nv12' -pix_fmt nv12 -f rawvideo -fps_mode passthrough -an -vframes 10 -y output.yuv
log:
graph 0 input from stream 0:0 @ 0x556dc2ff0100] w:1280 h:720 pixfmt:nv12 tb:1/25 fr:25/1 sar:0/1
[AVHWDeviceContext @ 0x556dc2ff03c0] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 23.1.3 ().
[AVHWDeviceContext @ 0x556dc2ff03c0] Driver not found in known nonstandard list, using standard behaviour.
[Parsed_vpp_qsv_2 @ 0x556dc2fedf40] qsv vpp pass through mode.
[AVHWFramesContext @ 0x556dc2ff55c0] Use Intel(R) Media SDK to create MFX session, API version is 1.35, the required implementation version is 1.255
[AVHWFramesContext @ 0x556dc2ff55c0] Initialize MFX session: implementation version is 1.255
[AVHWFramesContext @ 0x556dc2ff55c0] Use Intel(R) Media SDK to create MFX session, API version is 1.35, the required implementation version is 1.255
[AVHWFramesContext @ 0x556dc2ff55c0] Initialize MFX session: implementation version is 1.255
Segmentation fault (core dumped)
Describe the expected behavior

FBC link: 4bb7c228af570a5d29dbea4604eddcea4ee2339e

@fenhu could you take a look for this issue?

I am look for it. Need test env. you just provie the test cmd, not have install steps . I still don't know how to reproduce it.

Auto Created VSMGWL-63155 for further analysis.

sorry. I am already fix it. and PR merge to opensource. How to close it?

fixed PR: https://github.com/intel-innersource/drivers.gpu.media.sdk.lib/pull/6788
which was merged [VPL] master-1.0.3714

Opensource Link: https://github.com/oneapi-src/oneVPL-intel-gpu/commit/c32d57a8412a279d23b6502eca32a6bfb36c118f
would you help to verify and close it?
Thanks
Molly


Update code generation scripts with k8s v1.30 libraries

Maybe (if we continue upgrading k8s deps along Cilium) during Cilium v1.16 dep update.

Commit https://github.com/cilium/tetragon/commit/a9c509f1f7c738bbeb1565f83eb9da70941a22ba replaced execution of deprecated scripts with k8s.io/code-generator/kube_codegen.sh. However, kube_codegen.sh doesn't generate code on its own, but rather defines helper functions. To migrate to kube_codegen.sh we'll need to call these functions from another script. Additionally, it'll change with version 1.30 of k8s libraries - that's why I opted to simply revert the change for now. When k8s libraries are updated to 1.30, the code generation scripts should be updated too.

_Originally posted by @lambdanis in https://github.com/cilium/tetragon/issues/2339

Just for reference, PR adding k8s 1.30 support to Cilium: https://github.com/cilium/cilium/pull/31687 Tetragon will need similar changes in the code generation scripts.


Sign text NPE

I'm getting a null pointer exception when I try to get the sign text of a sign.
[result] => error
[error] => The server is offline right now. Try again in 2 seconds.
[source] => world.getSignText

In the minecraft server console, it's just
[SEVERE] Exception in thread "Thread-81
Am I running the right version of Craftbukkit?
(Implementing API version 1.1-R1)```

This appears to be Spout related, so closing.


ImagineApi failed with status 400

the code that reproduces this issue or a replay of the bug
const { Midjourney } = require("midjourney");

const client = new Midjourney({
  ServerId: process.env.SERVER_ID,
  ChannelId: process.env.CHANNEL_ID,
  SalaiToken: process.env.SALAI_TOKEN,
  Debug: true,
  Ws: true, //enable ws is required for remix mode (and custom zoom)
});

const imagine = async (prompt) => {
  await client.init();

  const Imagine = await client.Imagine(
    prompt,
    (uri, progress) => {
      console.log("loading", uri, "progress", progress);
    }
  );

  if (!Imagine) {
    throw new Error('Unable to imagine.');
  }

  return Imagine;
};

module.exports = {
  imagine
}

Describe the bug
Imagine API is throwing the error: ImagineApi failed with status 400
error log
ImagineApi failed with status 400

It's related to the prompt version ID changing. when they release new version of API
see this
https://github.com/erictik/midjourney-api/commit/a15e8c70c78d7116af28092c49ad6bec99f000fd#diff-eb2670564ae072c1d316a239d83b7e1ff892808d117e9e232d9d98db4be6fdd4


Allow nullable fields in PackageMetadataConfig

Discogapic generator doesn't need package configs for protoc, grpc, etc, so allow those fields to be null.

PTAL

Codecov Report

Merging #1936 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##             master   #1936      +/-   ##
===========================================
- Coverage     85.71%   85.7%   -0.01%
  Complexity     4794    4794
===========================================
  Files           441     441
  Lines         19210   19212       +2
  Branches       2010    2011       +1
===========================================
  Hits          16466   16466
- Misses         2057    2058       +1
- Partials        687     688       +1

Impacted Files
Coverage Δ
Complexity Δ

...ogle/api/codegen/config/PackageMetadataConfig.java
94.16% <0%> (-1.4%)
32 <0> (ø)

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 8b09d6e...5ec1136. Read the comment docs.


feat: range() with single-argument

This raises enough issues on its own not to go with anything more complex! (I can follow-up with a custom compiler/checker if we want, that does work)
The worst is probably that we now have constants and functions from builtins.py compiled into every Hugr, which throws out a lot of tests (looking for single nodes of some Hugr Op and then checking that these are as expected). The "right" solution might well be to add metadata to every Hugr FuncDefn saying which source file it's from so we can filter better....but that's another PR? Or is there something like this already?

Codecov Report
Attention: Patch coverage is 65.30612% with 17 lines in your changes missing coverage. Please review.

Project coverage is 92.58%. Comparing base (2199b48) to head (ab96665).

Files with missing lines
Patch %
Lines

guppylang/definition/struct.py
42.10%
11 Missing :warning:

guppylang/prelude/builtins.py
76.00%
6 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #452      +/-   ##
==========================================
- Coverage   92.70%   92.58%   -0.13%
==========================================
  Files          49       49
  Lines        5525     5555      +30
==========================================
+ Hits         5122     5143      +21
- Misses        403      412       +9

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


update golang.org/x/net to v0.23.0

Fixing https://pkg.go.dev/vuln/GO-2024-2687
Full scan output of govulncheck:
Scanning your code and 817 packages across 113 dependent modules for known vulnerabilities...

=== Symbol Results ===

Vulnerability #1: GO-2024-2687
    HTTP/2 CONTINUATION flood in net/http
  More info: https://pkg.go.dev/vuln/GO-2024-2687
  Module: golang.org/x/net
    Found in<EMAIL_ADDRESS>    Fixed in<EMAIL_ADDRESS>    Example traces found:
      #1: internal/services/executor/driver/k8s.go:107:41: driver.NewK8sDriver calls kubernetes.NewForConfig, which eventually calls http2.ConfigureTransports
      #2: internal/services/runservice/api/api.go:896:26: api.RunTaskActionsHandler.ServeHTTP calls http2.ConnectionError.Error
      #3: internal/services/executor/executor.go:1473:31: executor.NewExecutor calls fmt.Sprintf, which eventually calls http2.ErrCode.String
      #4: internal/services/executor/executor.go:1473:31: executor.NewExecutor calls fmt.Sprintf, which eventually calls http2.FrameHeader.String
      #5: internal/services/executor/executor.go:1473:31: executor.NewExecutor calls fmt.Sprintf, which eventually calls http2.FrameType.String
      #6: internal/services/runservice/api/api.go:896:26: api.RunTaskActionsHandler.ServeHTTP calls http2.GoAwayError.Error
      #7: internal/services/executor/executor.go:1473:31: executor.NewExecutor calls fmt.Sprintf, which eventually calls http2.Setting.String
      #8: internal/services/executor/executor.go:1473:31: executor.NewExecutor calls fmt.Sprintf, which eventually calls http2.SettingID.String
      #9: internal/services/runservice/api/api.go:896:26: api.RunTaskActionsHandler.ServeHTTP calls http2.StreamError.Error
      #10: internal/gitsources/github/github.go:106:23: github.TokenTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls http2.Transport.NewClientConn
      #11: internal/gitsources/github/github.go:106:23: github.TokenTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls http2.Transport.RoundTrip
      #12: internal/sqlg/manager/export.go:54:34: manager.DBManager.Export calls bufio.Writer.Flush, which calls http2.chunkWriter.Write
      #13: internal/services/runservice/api/api.go:896:26: api.RunTaskActionsHandler.ServeHTTP calls http2.connError.Error
      #14: internal/services/runservice/api/api.go:896:26: api.RunTaskActionsHandler.ServeHTTP calls http2.duplicatePseudoHeaderError.Error
      #15: internal/services/gateway/api/run.go:624:2: api.LogsHandler.ServeHTTP calls http2.gzipReader.Close
      #16: internal/gitsources/github/github.go:209:22: github.Client.GetFile calls io.ReadAll, which calls http2.gzipReader.Read
      #17: internal/services/runservice/api/api.go:896:26: api.RunTaskActionsHandler.ServeHTTP calls http2.headerFieldNameError.Error
      #18: internal/services/runservice/api/api.go:896:26: api.RunTaskActionsHandler.ServeHTTP calls http2.headerFieldValueError.Error
      #19: internal/gitsources/github/github.go:106:23: github.TokenTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls http2.noDialH2RoundTripper.RoundTrip
      #20: internal/services/runservice/api/api.go:896:26: api.RunTaskActionsHandler.ServeHTTP calls http2.pseudoHeaderError.Error
      #21: internal/sqlg/manager/export.go:54:34: manager.DBManager.Export calls bufio.Writer.Flush, which calls http2.stickyErrWriter.Write
      #22: internal/services/gateway/api/run.go:624:2: api.LogsHandler.ServeHTTP calls http2.transportResponseBody.Close
      #23: internal/gitsources/github/github.go:209:22: github.Client.GetFile calls io.ReadAll, which calls http2.transportResponseBody.Read
      #24: internal/services/executor/executor.go:1473:31: executor.NewExecutor calls fmt.Sprintf, which eventually calls http2.writeData.String

Your code is affected by 1 vulnerability from 1 module.
This scan also found 3 vulnerabilities in packages you import and 3
vulnerabilities in modules you require, but your code doesn't appear to call
these vulnerabilities.
Use '-show verbose' for more details.

I don't think we are using http2 from golang.org/x/net but from the stdlib. So it's fixed by using an updated go version.

This is NOT fixed by upgrading the stdlib.  You can run that locally in your dev environment and will get the exact same error.
Check out your go.mod, which states that x/net is a transitive dependency of yours:
https://github.com/agola-io/agola/blob/20f80cd29814e66e69b5b57f8fe33d037e4789eb/go.mod#L131
You can use go mod graph | grep 'x/net' | grep -v -E '^golang.org/x/net' to figure out which of your dependencies is requiring x/net:
agola.io/agola<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Take a look at the vuln report and how go vendors in the stdlib the golang.org/x/net http2 part. So you'll discover that a package using the net/http package uses the code provided by the stdlib and not the golang.org/x/net module code.
Anyway I'll update the dependencies in a future PR.

Take a look at the vuln report and how go vendors in the stdlib the golang.org/x/net http2 part. So you'll discover that a package using the net/http package uses the code provided by the stdlib and not the golang.org/x/net module code.
Anyway I'll update the dependencies in a future PR.

I can't find x/net/http2 vendored in my 1.22.2 stdlib. There is x/net/http2/hpack, but that's not the package in question.
https://github.com/golang/go/blob/dddf0ae40fa0c1223aba191d73a44425a08e1035/src/vendor/modules.txt

h2_bundle.go is a bundle file generated from x/net source files: https://github.com/golang/go/blob/a3eb55cea95b5894e97f311be981cda0e87bd465/src/net/http/http.go#L5
This is the backport of the fix for go 1.22: https://github.com/golang/go/commit/e55d7cf8435ba4e58d4a5694e63b391821d4ee9b
As you can see h2_bundle.go is updated.
This is the fix in x/net/http2: https://github.com/golang/net/commit/ba872109ef2dc8f1da778651bd1fd3792d0e4587
As you can see this is the same code but a different files that is used to generate the h2_bundle.go.
I created a PR #512  to update all dependencies, BUT it's important to know that the built binaries won't be vulnerable only when compiled with an updated go version.

h2_bundle.go is a bundle file generated from x/net source files: https://github.com/golang/go/blob/a3eb55cea95b5894e97f311be981cda0e87bd465/src/net/http/http.go#L5

Thanks for the explanation! Just to understand this right, how do you know that none of your transitive dependencies is doing manual configuration of http2 transport, which would lead to x/net/http2 being used instead of the bundled http2 support?
https://pkg.go.dev/net/http#hdr-HTTP_2:

Manually configuring HTTP/2 via the golang.org/x/net/http2 package takes precedence over the net/http package's built-in HTTP/2 support.

I created a PR #512 to update all dependencies, BUT it's important to know that the built binaries won't be vulnerable only when compiled with an updated go version.

So would you say this is a false positive of govulncheck, which should be aware of the toolchain version?


GitHub Actions Polishing

Coverage remained the same at 100.0% when pulling 814a7c9d3f5a6b660039db324b6d7ed8d79763c1 on jeffgbutler:master into 8f47cd1034b4a18b1e3787d8258452619efaf17a on mybatis:master.


Crash fix

Teleporting to this coordinates may affect the server. Use RemoveActorPacket instead:
/** @var Player $player */
$player->getNetworkSession()->sendDataPacket(RemoveActorPacket::create($player->getId()));

Feel free to do PRs. :)
These coordinates are a 32 bit integer limit. Minecraft can't take it. But since PocketMine is x64, I doubt it'd affect it.


watch the ays repo using inotify

we also need to handle the templateRepo : https://github.com/Jumpscale/jumpscale_core8/blob/8.2.0/lib/JumpScale/baselib/atyourservice81/lib/TemplateRepo.py#L6
and the templates themself:
https://github.com/Jumpscale/jumpscale_core8/blob/8.2.0/lib/JumpScale/baselib/atyourservice81/lib/TemplateRepo.py#L202

pyinotify is forked here: https://github.com/gigforks/PyInotify


Standardize on Helm templates for yaml generation

At present istio has two ways to generate istio.yaml and other artifacts.

UpdateVersion.sh and home grown templates
Helm 2.7.2

Standardize on helm template command as the only way of producing istio artifacts.
helm is only used as a templating system.

[x] Ensure that helm and non-helm yamls are equivalent.
[x] Use helm generated yamls in all tests
[ ] Remove updateVersion

first 2 steps done via #4001

+1 for generating install artifacts in the go code than consuming already generated yaml and using different yaml files example as in here:
https://github.com/istio/istio/blob/de9f2dee56ed14bfbd56ae2a28296c92c25ac583/tests/e2e/framework/kubernetes.go#L40
	nonAuthInstallFile          = "istio.yaml"
	authInstallFile             = "istio-auth.yaml"
	nonAuthInstallFileNamespace = "istio-one-namespace.yaml"
	authInstallFileNamespace    = "istio-one-namespace-auth.yaml"

All these can be generated from a single template but feeding different values. I have experimented using helm api in go code and it looks ok to me.

I don't want to make the test setup even more complicated - having a separate step to generate the config also allows more flexibility.  I would simplify the test - to use only 'istio-test.yaml' file, since we no longer run both auth and no-auth in the same job/cluster.
Also having a shared environment, even with more components than needed for a specific test, ends up faster, since a single cluster setup (matching real user deployment) can be reused, and tests can be run against a pre-installed istio (with skip-setup).
I would go the opposite direction - and just remove the istio setup from the test, making skip-setup the only option and having the istio install done before the test.s

...  remove the istio setup from the test, making skip-setup the only option and having the istio install done before the test.

My understanding is that we wanted developers to be able to "express test environment requirements and constraints in integration/e2e tests", e.g. isolation, versions, features (see here)
cc @hklai from Istio testing SWAT team
Real user's may disable optional features at the component level, e.g. sidecar-injector, config validation. We probably ought to test the same.

...  since a single cluster setup (matching real user deployment) can be reused, and tests can be run against a pre-installed istio (with skip-setup).

We've had a lot issues in the past with reusing/sharing clusters across top-level tests, e.g. quota limits, stale global config state.

Not blocking for 1.0.

We have different objectives for our helm work.  We still need to delete updateVersions.sh (1 AUD to the individual that ultimately deletes udpateVersion.sh from the repo.. 👍
As such moving to P2+

@sdake feel free to send the 1 AUD :slightly_smiling_face: https://github.com/istio/istio/pull/18028


(SR-8830) implement generic packing/unpacking in irgen using TensorGroup protocol

Adds a TensorGroup protocol, and teaches IRGen to use it for packing and unpacking.
This is the beginning of the generic packing/unpacking plan described in https://bugs.swift.org/browse/SR-8830.
Plus a few other tangential things:

Makes TensorHandle.cTensorHandle and TensorHandle.init(owning cTensorHandle) public so that conformances to TensorGroup can be implemented. Prepends some underscores to the names.
Yet another fix to the SILFunction.processedByDeabstraction flag. The problem I encountered is that the optimizer specializes deabstracted functions, and does not know to set the flag on the resulting specialized functions. This makes IRGen incorrectly bail out when IRGen'ing the specialized functions.
Replaced our createStringValAddr function with an existing getAddrOfGlobalString that does the same thing except with deduplication.

Do you want to link to https://bugs.swift.org/browse/SR-8830 in the PR description?

@swift-ci please test tensorflow

@swift-ci please test tensorflow


Extend decoder to accept longs

Hello! Thank you for this work. It was my pleasure to read through your paper.
I just wonder, is it possible to extend this approach to accept not only ints but longs as well?
Per my understanding, we don't need any new states because we've already covered all byte position cases, but we have to take into account that we might stay in state Q3/R3 several times, correct?
And probably some other adjustments for the math for c,d and m...
Did you have any thoughts or, maybe, some POC for longs?
I'll be more than happy if you share any information about that. Thank you in advance!

Thank you for your interest. It is in fact the other way around. If we apply this approach based on longs, then it is more likely that we visit Q7/R7 states provided that an optimal Golomb parameter is used. This is because the alignment would be based on fixed 64-bit words, and Q/R parts would be relatively shorter. For the R part to exceed 64 bits, for example, the distribution of integers must be quite flat so that it may produce very large integers. On the other side, the Q part is expected to be much shorter if the Golomb parameter is properly selected. Or course, I do not know much about your use case. But, I suspect that an implementation based on longs would be more advantageous than byte-based implementation.
Still, it is easy to adapt the current model to be applied on longs. All you need to do is to initialize c as 64 instead of 8 and change the other assignments accordingly. For instance, based-2 logarithm of a current byte must be calculated at certain states, and this operation must be applied to a long instead of a byte. In this implementation, it is simply done by an array lookup as there are only 256 possible byte values. For longs, an efficient on-the-fly logarithm calculation is needed, as it won't be wise to store an array of size 2^64. Likewise, you also need to update modular arithmetic operations changing byte_i mod 2^(8-d) to long_i mod 2^(64-d), and so on. Also, 7's must be changed to 63's.
Hope this helps!

thank you for this work and for merging my PR #2!


deal with unknown json-ld schema

ref #640 this implements a remote schema loader with a tiny in-memory cache for not-built-in contexts, and also returns an empty schema when one can't be loaded (or is not valid json) from the remote server. This entirely eliminated the largest source of errors in my sentry monitoring even without #643.
Introduces a new dependency with httpx-cache. A simpler version of this fix would be to just replace the JsonLdError in builtin_document_loader with a return {}, since nothing depends on not canonicalizing schema which hasn't been built-in.

Yeah, to be honest I'd rather go with the return {}, since ActivityStreams specifically says that messages should adhere to an exact main context and that you don't need a full JSON-LD parser to decode them; the less network requests we can do for things we're not going to use, the better.

yeah, I haven't noticed any benefit to pulling these remote schemas - quite the contrary, many AP messages apparently have context references to 404 URLs.

Yes, I suspect that some of them are just used as flags for internal parsers or similar. Want to flip this PR to just return empty context, or open a new one for that?

context loader and cache reverted, blank schema added to the builtins, returning that instead of raising exception

Lovely, thanks for that!


Docker service ps shows odd ordering

Description
When inspecting the history of containers for a service, the ordering is confusing, or I just don't understand what is going on.
Steps to reproduce the issue:
I haven't been able to reproduce, but this is what I did.

Update a running service to an image that doesn't exist.
Update the same service to an image that DOES exist.

Describe the results you received:
2/3 of the new containers either died or were shutdown. 1 of the new containers successfully started. The odd thing is that in docker service ps kong, the service that is running is not the one that is left-most or at the top of the list.

Describe the results you expected:
I expected 1 service running, with it being at the top of the list.
Additional information you deem important (e.g. issue happens only occasionally):
To reproduce this, we might need to have a container that has an occasional failure on startup--I'm not sure.
Output of docker version:
Client:
 Version:      1.12.1
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   23cf638
 Built:        Thu Aug 18 05:33:38 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.1
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   23cf638
 Built:        Thu Aug 18 05:33:38 2016
 OS/Arch:      linux/amd64

Output of docker info:
root@swarmdev:/home/ubuntu# docker info
Containers: 14
 Running: 14
 Paused: 0
 Stopped: 0
Images: 12
Server Version: 1.12.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 146
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null bridge host overlay
Swarm: active
 NodeID: 5hiqzkjsb1jbkny1vuvh6bh7w
 Is Manager: true
 ClusterID: 0d17s2mvdj4i4w6j6eyj06ob2
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-36-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.359 GiB
Name: swarmdev
ID: TSZI:POAG:YCAO:L37D:ISMX:M2NE:B2HE:EZJF:W3CR:JMIM:MEEE:TURK
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: odysseyops
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
This on an Azure VM and I cannot access the previously failed-to-start containers since we are using docker-cleanup to cleanup old containers/images.
The custom kong image is just an image with custom plugins installed. The command at container init is exactly the same as the public, official kong image.

Ping @aluzzardi @aaronlehmann

I think the tasks are ordered by the timestamp of the most recent change. The "shutdown" task has a timestamp that's more recent than the "running" task (4 minutes ago vs. 5 minutes ago), so it gets displayed above. It's not obvious to me why this would happen. I'd expect a task to only be restarted after the previous incarnation finishes shutting down. If there are multiple nodes involved, this could be clock skew between the nodes.
It probably makes sense to change the way we sort these lines so that "running" tasks (and tasks on the way to running) appear before failed, rejected, and shutdown tasks from the same slot. I'll try to put together a PR for this.

Obviously not the most important thing on the planet, but thank you for the response!
If it helps to know, this was on a single machine, so there shouldn't be any time clock skew issues.

Thanks for the followup. It's probably something else then.


0x: init at unstable-2022-07-11

Description of changes

0x is a colorful, configurable xxd written in Rust.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 186235 run on x86_64-darwin 1

1 package built:

_0x


add events.ledger.submit

Adds async def submit(self, commands: 'Sequence[Command]') -> 'Awaitable[None]' to events.ledger. This can be used by an integration to manually submit commands and allows for catching and handling errors that occur when submitting.

Decided to use an error handling callback instead: https://github.com/digital-asset/daml-dit-if/pull/34


TypeError: Cannot read property 'addEventListener' of null

Hi Peter,
Compliments for the player, nice work!
I am using react-player inside my react component but getting the following error while running jest tests:
TypeError: Cannot read property 'addEventListener' of null
at FilePlayer.addListeners (node_modules/react-player/lib/players/FilePlayer.js:144:19)
at FilePlayer.componentDidMount (node_modules/react-player/lib/players/FilePlayer.js:109:12)
....
Any ideas?
Thanks!

See #427. You need to mock the window global when testing FilePlayer.


Introducing a Vue port of Sonner

the repo: https://github.com/xiaoluoboding/vue-sonner
the docs: https://vue-sonner.vercel.app/

Thank you so much for doing this bro!

Thank you, I've added it to the readme!


Battery sensor unavailable (Tapo C420)

Description
Hi,
since the last update, the battery sensor and several other memory-related sensors have become consistently unavailable (see attached image).
The problem occurs on Tapo c420 cameras.
Reproduction Steps
/
Expected behavior
The sensors described above should be available.
If applicable, add error logs.
home-assistant_tapo_control_2024-01-23T12-35-21.657Z.log

-21.657Z.log)
Device Firmware
1.2.15 Build 20231013 rel.73743
Integration Version
5.4.14
Using stream component
Yes
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
No
HASS Environment
HASSIO on Raspberry Pi 4
Search for similar issues
Yes
Additional information
No response

Please fix the link to logs. Also try migrating back to previous version to confirm the issue is caused by the update.

Please fix the link to logs. Also try migrating back to previous version to confirm the issue is caused by the update.

Done! But...
Something unexpected happened with the previous version (5.4.13): the battery level sensor disappeared... it doesn't even appear among the hidden entities.

Can confirm the issue

I checked the logs for SD card as well as tapoBatterySensor entities, and they are added properly according to logs. So there must be some other error going on which I can't really tell from the logs.
Does this happen consistently - it never comes up?

Hi,
yes, I can confirm that the battery sensor is completely absent and does not appear among the camera entities.

I have lost the battery sensor on my doorbell

Had came to terms with it thinking a feature was removed, until stumbling across this. Having the same issue. It used to work, but can't tell when it stopped (have been using the entity in a dashboard monitoring battery levels for all devices).

Fixed in https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/releases/tag/5.4.18.


Quote generator

Zero To Mastery - Webblocks 2022 📦📦
PR contains:

An online quote generator that randomly generates motivation quotes.  Fetching quotes from an API.

Breaking changes

None

Screenshots

Rules for this repo:

Please make sure that the code is your own, and not copied from somewhere else

That looks awfully the same as the original quote generator project from the "20 Javascript projects ZTM course" except a slightly different background image: https://github.com/JacintoDesign/quote-generator
Can you please eloborate on your contribution?


Add OriginTag to Command

Summary of the Pull Request
As outlined in #16816 , adding OriginTag to Command is one of the prerequisites to implementing Action IDs. This PR does that.
Validation Steps Performed
Actions/Commands still get parsed and work
PR Checklist

[ ] Closes #xxx
[ ] Tests added/passed
[ ] Documentation updated

If checked, please file a pull request on our docs repo and link it here: #xxx

[ ] Schema updated (if necessary)

@zadjii-msft @lhecker could you re-approve? It says the reviews are stale


chore: fuzz consensus item de/encoding

One of the most interesting types to fuzz.
Re #287 , a quite old issue.

needs rebase :(

@elsirion Rebased.


[OpenAI] Enable stream-style-serialization Inference

OpenAI Inference:

We disable stream-style-serialization because
we still have customization with Jackson or bug in emitter/core that not able to do this at present.
Other PR reference: https://github.com/Azure/azure-sdk-for-java/pull/39287

OpenAI Assistant:
WIP: https://github.com/Azure/azure-sdk-for-java/issues/38725#issuecomment-2019464594

I updated the title of the issue just to reflect that this is specific to the Inference SDK :)


pack_unpack: List first unrecognized key in strict unpacking

Otherwise figuring out what's wrong with your JSON can be tricky,
especially if you're using a single fmt string to validate a large,
complicated schema.
This just shows the first unrecognized key, because assembling a list
of all unrecognized strings seemed like too much work.  Humans who are
supplying invalid JSON can always remove the listed key and
re-validate.  Programs seeking an API listing unrecognized keys are
out of luck.

This is an interesting patch and I believe it would be useful to many users.
Using strbuffer_t in src/strbuffer.h it would be quite easy to list all unrecognized keys. Testing it is a bit harder, though, as you cannot depend on getting the keys in the same order every time.

Here's a quick patch on top of your changes that implements listing all unrecognized keys. I'd appreciate if you incorporate it into your branch, check that it's a sane thing to do, and perhaps add some more tests.
diff --git a/src/pack_unpack.c b/src/pack_unpack.c
index d2118cf..617b3c0 100644
--- a/src/pack_unpack.c
+++ b/src/pack_unpack.c
@@ -435,7 +435,9 @@ static int unpack_object(scanner_t *s, json_t *root, va_list *ap)

     if(root && strict == 1) {
         /* We need to check that all non optional items have been parsed */
-        const char *key, *unrecognized_key;
+        const char *key;
+        int have_unrecognized_keys = 0;
+        strbuffer_t unrecognized_keys;
         json_t *value;
         long unpacked = 0;
         if (gotopt) {
@@ -443,7 +445,14 @@ static int unpack_object(scanner_t *s, json_t *root, va_list *ap)
             json_object_foreach(root, key, value) {
                 if(!hashtable_get(&key_set, key)) {
                     unpacked++;
-                    unrecognized_key = key;
+
+                    if (!have_unrecognized_keys) {
+                        strbuffer_init(&unrecognized_keys);
+                        have_unrecognized_keys = 1;
+                    } else {
+                        strbuffer_append_bytes(&unrecognized_keys, ", ", 2);
+                    }
+                    strbuffer_append_bytes(&unrecognized_keys, key, strlen(key));
                 }
             }
         } else {
@@ -455,14 +464,20 @@ static int unpack_object(scanner_t *s, json_t *root, va_list *ap)
                 /* Find the first unrecognized key */
                 json_object_foreach(root, key, value) {
                     if(!hashtable_get(&key_set, key)) {
-                        unrecognized_key = key;
-                        break;
+                        if (!have_unrecognized_keys) {
+                            strbuffer_init(&unrecognized_keys);
+                            have_unrecognized_keys = 1;
+                        } else {
+                            strbuffer_append_bytes(&unrecognized_keys, ", ", 2);
+                        }
+                        strbuffer_append_bytes(&unrecognized_keys, key, strlen(key));
                     }
                 }
             }
             set_error(s, "<validation>",
-                      "%li object item(s) left unpacked, including %s",
-                      unpacked, unrecognized_key);
+                      "%li object item(s) left unpacked: %s",
+                      unpacked, strbuffer_value(&unrecognized_keys));
+            strbuffer_close(&unrecognized_keys);
             goto out;
         }
     }
diff --git a/test/suites/api/test_unpack.c b/test/suites/api/test_unpack.c
index 87caaf6..babe0dd 100644
--- a/test/suites/api/test_unpack.c
+++ b/test/suites/api/test_unpack.c
@@ -298,10 +298,16 @@ static void run_tests()
     json_decref(j);

     /* Unpack the same item twice */
-    j = json_pack("{s:s, s:i}", "foo", "bar", "baz", 42);
+    j = json_pack("{s:s, s:i, s:b}", "foo", "bar", "baz", 42, "quux", 1);
     if(!json_unpack_ex(j, &error, 0, "{s:s,s:s!}", "foo", &s, "foo", &s))
         fail("json_unpack object with strict validation failed");
-    check_error("1 object item(s) left unpacked, including baz", "<validation>", 1, 10, 10);
+    {
+        const char *possible_errors[] = {
+            "2 object item(s) left unpacked: baz, quux",
+            "2 object item(s) left unpacked: quux, baz"
+        };
+        check_errors(possible_errors, 2, "<validation>", 1, 10, 10);
+    }
     json_decref(j);

     j = json_pack("[i,{s:i,s:n},[i,i]]", 1, "foo", 2, "bar", 3, 4);
@@ -335,7 +341,7 @@ static void run_tests()
     j = json_pack("{s{snsn}}", "foo", "bar", "baz");
     if(!json_unpack_ex(j, &error, 0, "{s{sn!}}", "foo", "bar"))
         fail("json_unpack nested object with strict validation failed");
-    check_error("1 object item(s) left unpacked, including baz", "<validation>", 1, 7, 7);
+    check_error("1 object item(s) left unpacked: baz", "<validation>", 1, 7, 7);
     json_decref(j);

     /* Error in nested array */
@@ -395,6 +401,6 @@ static void run_tests()
     i1 = i2 = i3 = 0;
     if(!json_unpack_ex(j, &error, 0, "{sis?i!}", "foo", &i1, "bar", &i2))
         fail("json_unpack failed for optional values with strict mode and compensation");
-    check_error("1 object item(s) left unpacked, including baz", "<validation>", 1, 8, 8);
+    check_error("1 object item(s) left unpacked: baz", "<validation>", 1, 8, 8);
     json_decref(j);
 }
diff --git a/test/suites/api/util.h b/test/suites/api/util.h
index 1bc4c9c..c25f4eb 100644
--- a/test/suites/api/util.h
+++ b/test/suites/api/util.h
@@ -61,6 +61,45 @@
     } while(0)

+/* Assumes json_error_t error */
+#define check_errors(texts_, num_, source_, line_, column_, position_)  \
+    do {                                                                \
+        int i_, found_ = 0;                                             \
+        for(i_ = 0; i_ < num_; i_++) {                                  \
+            if(strcmp(error.text, texts_[i_]) == 0) {                   \
+                found_ = 1;                                             \
+                break;                                                  \
+            }                                                           \
+        }                                                               \
+        if (!found_) {                                                  \
+            failhdr;                                                    \
+            fprintf(stderr, "text: \"%s\" does not match\n", error.text); \
+            exit(1);                                                    \
+        }                                                               \
+        if(strcmp(error.source, source_) != 0) {                        \
+            failhdr;                                                    \
+                                                                        \
+            fprintf(stderr, "source: \"%s\" != \"%s\"\n", error.source, source_); \
+            exit(1);                                                    \
+        }                                                               \
+        if(error.line != line_) {                                       \
+            failhdr;                                                    \
+            fprintf(stderr, "line: %d != %d\n", error.line, line_);     \
+            exit(1);                                                    \
+        }                                                               \
+        if(error.column != column_) {                                   \
+            failhdr;                                                    \
+            fprintf(stderr, "column: %d != %d\n", error.column, column_); \
+            exit(1);                                                    \
+        }                                                               \
+        if(error.position != position_) {                               \
+            failhdr;                                                    \
+            fprintf(stderr, "position: %d != %d\n", error.position, position_); \
+            exit(1);                                                    \
+        }                                                               \
+    } while(0)
+
+
 static void run_tests();

 int main() {

On Mon, Dec 21, 2015 at 12:14:28AM -0800, Petri Lehtinen wrote:

Here's a quick patch on top of your changes that implements listing
all unrecognized keys. I'd appreciate if you incorporate it into
your branch, check that it's a sane thing to do, and perhaps add
some more tests.

Incorporated with e444516 → bc0f787.  The only change I made vs. your
patch was to redefine check_error in terms of the more general
check_errors to keep things DRYer.  In the new commit message, I point
out possible confusion with comma-containing keys (which I don't think
we need to worry about, since I haven't seen such keys in the wild)
and my preference for using unrecognized_keys.value == NULL instead of
a separate have_unrecognized_keys.  I'm happy to reroll to use value
== NULL if that approach sounds acceptable to you.

On Mon, Dec 21, 2015 at 12:14:28AM -0800, Petri Lehtinen wrote:

… and perhaps add some more tests.

And the current coverage seems sufficient to me.  If you have any
use-cases you feel need more testing, just let me know what they are.

strbuffer_close isn't called, and that causes the memory leak seen by the CI tests.

On Tue, Dec 22, 2015 at 03:00:40AM -0800, Petri Lehtinen wrote:

strbuffer_close isn't called, and that causes the memory leak seen
by the CI tests.

Ah, that was another change I made vs. your suggested patch :p.  In
hindsight, needing a separate free after strbuffer_steal_value makes
sense.  Fixed in bc0f787 → 1d513d0.

Merged, thanks a lot!


Report Grid Bug

Description
It seems that there is a bug in the report grid section. After creating the report grid, I am no longer able to edit the report grid. There is a lock icon present in the column editor and the people editor section which says that I am not an owner of this report, even though I am the owner of this report. Not sure why this is coming.

Waltz Version
1.62
Steps to Reproduce

Create a report grid and save it
Navigate to a different page and then go back to the report grid section again
Check whether you're able to edit the report grid using "Column Editor" or "People Editor"

Expected Result
No response
Actual Result
No response

Could you check the permissions assigned to the grid in the database ?  You can use the external id (shown on the grid overview) with the following query to check the database:
select rg.name, rgm.user_id, rgm.role
from report_grid rg
inner join report_grid_member rgm on rg.id = rgm.grid_id
where rg.external_id = 'a01269ae-9f4e-45cd-8355-c9ef0ccb50be'

e.g.

The user id should match your logged in user_id, e.g. whatever is shown in the profile menu:

Yes I checked it.
I am the owner and the user id is also matching. Sharing few more snapshots.

The issue remains the same even when both the user_ids are same.

Have you checked my above comment @davidwatkins73 ?


AsciiDoc: Add support for global document attributes

I'm helping to migrate the Okta developer blog from Jekyll to Hugo. We're using both Markdown and AsciiDoc and Jekyll renders AsciiDoc using the following plugins:
group :jekyll_plugins do
  gem 'jekyll-asciidoc'
  gem 'asciidoctor-rouge'
end

We have most things working in Hugo, but we've discovered (with the help of @mojavelinux) that Hugo doesn't provide a way to pass configuration to an external helper command, like asciidoctor. Here's the code that executes Asciidoctor: https://github.com/gohugoio/hugo/blob/master/helpers/content.go#L626-L650
This means I have to define global attributes in every .adoc file. For example:
:page-liquid:
:source-highlighter: rouge
:icons: font

It'd be great if Hugo had a way to pass attributes from the Hugo configuration to the asciidoctor command. According to Dan, we're losing a lot of power without that ability.

Being able to pass global attributes is essential for using Asciidoctor properly (the -a flag). Related to this is the ability to specify extensions to load (the -r flag).
One option is to simply allow extra arguments for the asciidoctor to be specified in the Hugo configuration. This would give the user maximum flexibility while only requiring a very small change to Hugo. There are many such options a user may want to specify. See https://asciidoctor.org/man/asciidoctor/

Resolved with https://github.com/gohugoio/hugo/pull/7281


Would this work for ESMFold?

Hi
Thank you for doing this - adding the latest improvements to popular ESM2 will save everyone a lot of compute 👍
Do you think these benefits could be transferred to ESMfold?

LOL Not sure how much of a bottleneck the ESM2 part is, but it def saves something

Would be interesting to see how much! About 80% of parameters of ESMFold is in the ESM2 (3B) part, so for saving memory and better scaling, it could make a big difference🤞Not sure how this translates to inference speeds, though.
A paper tried to optimize ESMFold using quantization - it's not directly comparable, but has some details:
https://arxiv.org/abs/2310.19624
They saw big gains when trying to optimize ESM2, while optimizing the folding trunk and structure module was more difficult.

Good catch! saving memory might be the ultimate gain


Removed xfail.

Updated fail to match compiler change.

Please test with following pull request:
https://github.com/apple/swift/pull/60756
@swift-ci please test

Cross-repo testing didn't seem to take, but the project UPASSed over on that PR.  Testing again.

@swift-ci please test

cc: @shahmishal @justice-adams-apple


Serialize and parse XML as UTF-8

This fixes a bug where the lib is unable to list channels with non-ascii names and change to these channels.

@wokar please apply


Twig_TokenParserBroker is deprecated

I get the following message while running this tool:

Deprecated: The Twig_TokenParserBroker class is deprecated since version 1.12 and will be removed in 2.0. in vendor/twig/twig/lib/Twig/TokenParserBroker.php on line 36

@jyggen Are you up for sending a pull request? :)


Bad error for "location not found"

getAllLineagesByLocation(location = "US")
Retrieving data...
invalid subscript type 'list'
 Error in value[[3L]](cond) :
  Could not connect to API. Please check internet connection and try again.

Ideal error: something like Location not found.  Did you mean "United States"?

Fix in https://github.com/outbreak-info/R-outbreak-info/commit/8fdce3646dcd1d8d5e7f69898d4e3ebe8b17ed3f.
Location not found should be logged.


Scanning multiple times causes "MaxListenersExceededWarning: Possible EventEmitter memory leak detected."

const {createBluetooth} = require('node-ble')
const {bluetooth, destroy} = createBluetooth()

async function main(){
  const adapter = await bluetooth.defaultAdapter()
  async function search(){

    if (! await adapter.isDiscovering()){
      await adapter.startDiscovery()
    }
    const devices = await adapter.devices()

    devices.forEach(async mac => {
      const device = await adapter.waitDevice(mac)
      let rssi;
      try {
        rssi = await device.getRSSI()
      } catch (error) {
        //console.error(error)
      }

      console.log(mac, rssi)
      device.disconnect()
    });
    //destroy()
    //await device.disconnect()
  }

setInterval(() => {
  search()
}, 5000);

}
main()

When I run this code it works for a minute and prints mac addresses and their RSSI value
Then i start getting warnings
(node:2234) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 {"path":"/org/bluez/hci0/dev_CC_98_8B_A7_XX_XX","interface":"org.freedesktop.DBus.Properties","member":"PropertiesChanged"} listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
After about 10 minutes it crashes with the following error message
/home/compulab/projects/newNode-ble/node_modules/node-ble/src/Adapter.js:158
        reject(new Error('operation timed out'))
               ^

Error: operation timed out
    at Timeout._onTimeout (/home/compulab/projects/newNode-ble/node_modules/node-ble/src/Adapter.js:158:16)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)

Node.js v18.15.0

I'm running Debian 11 with kernel version 5.15.5 on a board manufactured by Compulab
Any suggestions?

Fixed with 1.10


Problems with blank-masking

The code chunking iterator works in terms of byte offsets. But the mask_comments function (and ´mask_sub_scopes` too, probably) construct a new string based on differences of byte offsets.
That means that if a comment or string contains non-ASCII characters, the "masked-out" string will have more characters than the original source, since multi-byte characters got replaced by multiple single-byte characters (spaces).
I can't say if this causes problems such as wrong indices in the matches...
A related problem is that if a character literal contains an escape sequence, the "masked-out" version of the code is not valid Rust anymore, since e.g. '\'' gets masked to '  ' (with two spaces). Again, I can't say if that causes an actual problem.

Good catch.
I think internally it makes sense if we hold the byte offset in the file, so replacing a multibyte char with the same number of spaces is the right thing to do from the perspective of masking.
I'm not sure what is best to do about character literals with an escape sequence - I assume the parser balks at multi space char literals (I haven't tested). Maybe we should replace with a 1 space char literal and an extra space after the closing quote?.


tests fail all of a sudden: non-matching feature IDs

introduced with the latest commit to master (https://github.com/fedarko/rankratioviz/commit/399e4647b91272dc102c6f84d910e67fe238c71e).
Through some judicious print statements, it looks like midway through iterating through the main data in the rank plot JSON the ranked_features_iterator gets ahead by one, throwing the comparison off.
Commenting out just this assertion solves the problem. Which is a little weird -- you'd think other things (or at least the x check) would get thrown off by this, not just this one check.
I'd expect I'm missing something obvious here, so I can probably get this solved soon.

Weirdly enough, the places where this fails (and this fails at different places when I rerun the tests) seem to have one thing in common: the two ranks that get "conflated" have (as reported in the JSON) identical rank values. Like, even to 16ish decimal points of precision. That seems... wrong. Maybe something I introduced caused this to occasionally do this weird overwriting thing?
Ranks of interest in pseudomonas DEICODE dataset: x: 245 and x: 246; x:259 and x:260.

From inspecting the original ordination file: it looks like the rank values are the same between these pairs, too -- look at lines 267 and 268 in ordination.txt. This indicates that this isn't a problem with rankratioviz, at least not entirely -- what I think happened here is that, since these few rank values are literally identical, the order of these ranks can get switched around, and this causes problems in how the test 'expects' the data to be formatted (because the test just assumes the input ordination file is sorted by its first rank -- which it is, in this case -- but there are multiple valid sortings since there are equal first-rank values).

The solution here is either removing the non-rank-0-data (ID, other ranks, etc) check from the main loop over both the JSON features and reference features (not desirable), or adding some code to: first check that the rank 0s are monotonically increasing, then verify that inconsistencies in ID order are due to rank 0 equalities, then go through and check everything.
gonna be a bit of an overhaul, so I'll work on that later this week. not sure why this issue is only coming up now -- my guess is it's due to using the dataframe approach instead of the dict approach for storing data, but it's still sorta odd. The multiple identical rank values between adjacent features in the DEICODE output also seems really weird.

@fedarko  It is not impossible to have ranks with the same values repeated. One easy solution might be to check that the order of the rank values is the same instead of the IDs in the unittest?

That's a solid idea, thanks! I'll get this test knocked out ASAP.


Interactivity: Handle mouse events in a better way

Tests are failing, only clicks implemented properly for the moment. Here for the review.

@skavish @kirillk when the Travis build will be finished (tests should pass), it's OK to review and merge

@kirillk renamed mouseover -> mouseenter, mouseout -> mouseexit


cancel function is missing on promises.

Description
the cancel function is missing, causing programs to hang even an exception is thrown. Despite Promises/A+ does not mention .cancel, many promise capable libraries (i.e GUZZLE, REACTPHP) provides such feature.
Example
$promise.cancel();

to make things optional, we could add a CancellablePromise interface and implement that in the guzzle adapter promise to expose the guzzle promise cancel method.