infracost comment gitlab - 404

I followed this but the job fails with

time="2022-09-22T12:11:16Z" level=info msg="Estimate uploaded to organization 'xxx' in Infracost Cloud"
time="2022-09-22T12:11:16Z" level=info msg="Finding matching comments for tag infracost-comment"
time="2022-09-22T12:11:17Z" level=info msg="Found 0 matching comments"
time="2022-09-22T12:11:17Z" level=info msg="Creating new comment"
Error: The pull request comment was generated successfully but could not be posted:
Error creating comment: 404 Not Found
See https://infracost.io/docs/troubleshooting/#5-posting-comments for help.

Infracost-wise everything looks good so far

Here's the debug output when I reproduce this locally:
[
{
  "currency": "USD",
  "enable_cloud_org": false,
  "file": "/app/internal/config/run_context.go:196",
  "func": "github.com/infracost/infracost/internal/config.(*RunContext).IsCloudEnabled",
  "is_cloud_enabled": false,
  "level": "debug",
  "msg": "IsCloudEnabled inferred from Config.EnabledDashboard",
  "sync_usage": false,
  "time": "2022-09-22T12:24:17Z"
},
{
  "currency": "USD",
  "enable_cloud_org": false,
  "file": "/app/cmd/infracost/main.go:251",
  "func": "main.loadCloudSettings",
  "level": "debug",
  "msg": "Successfully loaded settings from Infracost Cloud",
  "result": "{CloudEnabled:false}",
  "sync_usage": false,
  "time": "2022-09-22T12:24:17Z"
},
{
  "currency": "USD",
  "enable_cloud_org": false,
  "file": "/app/internal/config/run_context.go:196",
  "func": "github.com/infracost/infracost/internal/config.(*RunContext).IsCloudEnabled",
  "is_cloud_enabled": false,
  "level": "debug",
  "msg": "IsCloudEnabled inferred from Config.EnabledDashboard",
  "sync_usage": false,
  "time": "2022-09-22T12:24:17Z"
},
{
  "file": "/app/internal/comment/handler.go:99",
  "func": "github.com/infracost/infracost/internal/comment.(*CommentHandler).matchingComments",
  "level": "info",
  "msg": "Finding matching comments for tag infracost-comment",
  "time": "2022-09-22T12:24:17Z"
},
{
  "file": "/app/internal/comment/handler.go:109",
  "func": "github.com/infracost/infracost/internal/comment.(*CommentHandler).matchingComments",
  "level": "info",
  "msg": "Found 0 matching comments",
  "time": "2022-09-22T12:24:18Z"
},
{
  "file": "/app/internal/comment/handler.go:155",
  "func": "github.com/infracost/infracost/internal/comment.(*CommentHandler).UpdateComment",
  "level": "info",
  "msg": "Creating new comment",
  "time": "2022-09-22T12:24:18Z"
},
Error: The pull request comment was generated successfully but could not be posted:
Error creating comment: 404 Not Found

See https://infracost.io/docs/troubleshooting/#5-posting-comments for help.,

Image used: infracost/infracost:ci-0.10@sha256:488b5a249fa21dfb820bff13e734f2412bab067904eb6b716c32976aeb30d170

@black-snow Hello! Thank you for creating the issue and providing the debug output! :)
The infracost comment gitlab performs two API requests to GitLab:

Check the existing comment on the merge request (using GitLab's GraphQL)
Post a new/update comment (using GitLab's REST API)

It seems like the first request worked fine as it showed 0 comments, but the second one failed with 404 status, which could mean it didn't find the target MR. This is odd because both requests use the same values.
Could you please try to make a manual cURL request described in our troubleshooting guide to see if everything is in place:
export GITLAB_TOKEN=mytoken

# If you're not using GitLab.com, set this to your server URL
export CI_SERVER_URL=https://gitlab.com

# Your repo path in the form of namespace/project with encoded slash character. If your repo path has a group, try the curl with and without the group, e.g. also try my-org%2my-group%2my-repo
export CI_PROJECT_PATH=my-org%2my-repo

# Set this to your merge request ID
export CI_MERGE_REQUEST_IID=123

curl -i -X POST \
  --header "PRIVATE-TOKEN: $GITLAB_TOKEN" \
  --data-urlencode "body=testcomment" \
  $CI_SERVER_URL/api/v4/projects/$CI_PROJECT_PATH/merge_requests/$CI_MERGE_REQUEST_IID/notes

If everything is alright, it will create a new comment on MR. This would mean that something missing from the command in the pipeline.

Thanks for the quick reply @vdmgolub !
The slash in CI_PROJECT_PATH should not be urlencoded.
HTTP/2 404
date: Fri, 23 Sep 2022 08:08:44 GMT
content-type: application/json
content-length: 25
cache-control: no-cache
content-security-policy: default-src 'none'
vary: Origin
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-request-id: f6cabf789568d36075e75849fbc642d6
x-runtime: 0.021685
strict-transport-security: max-age=31536000
referrer-policy: strict-origin-when-cross-origin
ratelimit-observed: 1
ratelimit-remaining: 1999
ratelimit-reset:<PHONE_NUMBER>
ratelimit-resettime: Fri, 23 Sep 2022 08:09:44 GMT
ratelimit-limit: 2000
gitlab-lb: fe-22-lb-gprd
gitlab-sv: localhost
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=lYAMjUwcvcsJbFbvqnDKDzejRWJBrSXtVgWVGiyDv3ISPO8SMcMjfB3Z0wAIUlHYDBvLzEfpNACEhEIpjanF3W9C2usuXkc6sXEoSl7pb9dwh7C%2FaV%2F34KPGGYk%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0.01,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 74f1cb4cdffdb7a3-AMS

{"error":"404 Not Found"}

Tested again with a public test project - posting comments works there.

I created a project access token with api scope but the guest role ... works with more privileged roles 🤦
Maybe you could add a hint to the docs ;) @vdmgolub

@black-snow Great job on solving this! 👏
We don't use GitLab's premium/ee features, so I guess the guest role was overlooked as it's not mentioned in their docs. Thanks for the tip! I'll play with their EE setup and update our docs 👍


Fix unterminated quoted string error when running podman v4

I'm not sure why you closed the other pull request and opened this one. As I said in the other pull request, I'm not taking this patch until we have a https://github.com/containers/podman issue to reference in the commit message. Would you like me to file the issue? If so, can you provide your "rpm -q podman". Thanks!

Sorry, I messed up with rebasing, still learning how forking and contributing works :sweat_smile:
That would be wonderful if you could open the issue.
podman-4.0.0-0.6.rc4.fc36.x86_64

Thanks for the updated commit message! One more fix needed - can you update tests/test-basic.sh so that ./run-tests.sh passes (there are three copies of the 'podman inspect' command in that file)? Thanks!


[Event Request] Codeunit 7311 Whse. Worksheet-Create - procedure CreateWhseWkshLine - OnCreateWhseWkshLineOnBeforeGetWhseItemTrkgSetup

Please add the following Event OnCreateWhseWkshLineOnBeforeGetWhseItemTrkgSetup to procedure CreateWhseWkshLine in Codeunit 7311 Whse. Worksheet-Create
[Event Request] Codeunit 7311 Whse. Worksheet-Create - procedure CreateWhseWkshLine
local procedure CreateWhseWkshLine(var WhseWkshLine: Record "Whse. Worksheet Line") Created: Boolean
var
    Item: Record Item;
    ItemTrackingMgt: Codeunit "Item Tracking Management";
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeCreateWhseWkshLine(WhseWkshLine, Created, IsHandled);
    if IsHandled then
        exit(Created);

    with WhseWkshLine do begin
        if "Shelf No." = '' then begin
            Item."No." := "Item No.";
            Item.ItemSKUGet(Item, "Location Code", "Variant Code");
            "Shelf No." := Item."Shelf No.";
        end;
        OnCreateWhseWkshLineOnBeforeInsert(WhseWkshLine);
        if Insert() then begin
            Created := true;

            IsHandled := false; // <-- ADDED
            OnCreateWhseWkshLineOnBeforeGetWhseItemTrkgSetup(WhseWkshLine, IsHandled); // <-- NEW EVENT
            if not IsHandled then // <-- ADDED

                if ItemTrackingMgt.GetWhseItemTrkgSetup("Item No.") then
                    ItemTrackingMgt.InitTrackingSpecification(WhseWkshLine);

            OnCreateWhseWkshLineOnAfterInsert(WhseWkshLine);
        end;
    end;
end;

[IntegrationEvent(false,false)]
local procedure OnCreateWhseWkshLineOnBeforeGetWhseItemTrkgSetup(var WhseWkshLine: Record "Whse. Worksheet Line"; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10820.


Can we have multiple spdm contexts at the same time for multiple devices?

Is the spdm context somehow associated with a specific device we are talking to? The problem is this, if the OS and the BMC are both acting as requestor, then each can send any spdm command at any time.
So that both requesters will fail if the messages get intermingled.
What happens if we do get version, then get capabilities from one device say D1 to broadcom, and then do get version from rasp pi, and then do neg algo from D1, in that order?

If a Responder expects to communicate with multiple Requesters where the messages are intermingled then the Responder should have multiple contexts. If the Requesters can sort it out amongst themselves, say Requester 1 only talks to the Responder during boot stage 1, and Requester 2 only talks to the Responder during boot stage 2, and the messages never intermingle, then the Responder can probably get away with having only one context.


Add note to README about no else-if's

Can't do
if (x == 0) {
} else if (x == 1) {
} else {
}

Have to nest, like so:
if (x == 0) {
} else {
  if (x == 1) {
  }
  else {
  }
}

Done in https://github.com/DylanSp/wheel-lang/commit/a3e62dd286c626e88cd93513c5061c7d4be73d09.


cannot open file ~/.cache/oh-my-earth/momentumdash.random.jpg

OS: Ubuntu 16.04.3
Unity
have installed dependencies .....
and run:
oh-my earth
Updating momentumdash image...
Traceback (most recent call last):
  File "/usr/local/bin/oh-my-earth", line 34, in <module>
    main()
  File "/usr/local/bin/oh-my-earth", line 28, in main
    MomentumdashManager().run()
  File "/media/zh/SharedFiles/git/oh-my-earth/manage_momentum.py", line 48, in run
    self.get_bg_picture()
  File "/media/zh/SharedFiles/git/oh-my-earth/manage_momentum.py", line 39, in get_bg_picture
    urllib.urlretrieve(imgurl, momentumdash_output_file)
  File "/usr/lib/python2.7/urllib.py", line 98, in urlretrieve
    return opener.retrieve(url, filename, reporthook, data)
  File "/usr/lib/python2.7/urllib.py", line 249, in retrieve
    tfp = open(filename, 'wb')
IOError: [Errno 2] No such file or directory: '/home/zxj5470/.cache/oh-my-earth/momentumdash.random.jpg'

先创建目录 ~/.cache/oh-my-earth


300% Scaling @ 4K Renders UI Useless

I've install HASS.Agent on my PC in my living room, as IoTLink has been discontinued. However, I am using a 300% scaling on a 4k screen, and this is how my application looks...
Welcome screen

Taskbar context menu

Configuration screen

I'm going to drop down to 1080p so that I can get everything configured, but I'm really hoping I don't have to go back and change anything. All I really need is system stats reported to HA.

Yea that is messed up.. Could you please try this beta, it has (somewhat) improved DPI handling:
https://github.com/LAB02-Research/HASS.Agent/releases/download/2022.13.0-beta2/HASS.Agent.Installer.exe

Much better!

It looks like the changes mentioned in #99 were effective. I've gone ahead and updated to beta4 and it also looks fine now.

I'll go ahead and close this issue, as it looks like the next release will resolve the UI scaling issues.


Issue with constrained() method used after foreignIdFor(), instead of table name when $table parameter is not passed uses column name

When constrained() is used after foreignIdFor() then on the migration query for the constrained instead of the table name uses column name and pluralise it.
$table->foreignIdFor(User::class, 'assigned_at')->nullable()->constrained();

Query produced to add the constrain:
alter table `tasks` add constraint `tasks_assigned_at_foreign` foreign key (`assigned_at`) references `assigned_ats` (`id`);

so instead of references users it produces references assigned_ats pluralised name of the column.

This pr broke our migrations.

This pr broke our migrations.

Can you submit a bug report with reproducing code.


Pomodoro Timer

@roamhacker here's a list of potential feature enhancements with the Pomodoro Timer.

Have a sound even for when the break ends. Currently, the chime is only for when the 25 minutes are up.
Have adjustable times for the Pomodoro.
A way for it to compute the number of Pomodoro cycles I should do if I tell it the number of hours I want to work as well as the minutes per cycle.
Similarly, if I could know the number of hours I would work if I tell it the number of cycles and minutes per cycle.
A deadline randomiser would be nice (Not sure if this should be a separate enhancement). But something that allows me to set a deadline for a task dependencies permitting, which is non-negotiable.

These are probably far too many for one enhancement. Choose as you like. :)

Hey @roamhacker!
When you create the clocks feature. Consider using the astrolabe as the icon for the clock. It would look cool, I think.

Roam42 Issue Log Audit - Moved to Timer Extension


Add pubsub sink (close #41)

Is this failiing anything to be worried about @istreeter ? https://github.com/snowplow-incubator/snowplow-event-generator/actions/runs/4562576083/jobs/8050019979?pr=42
Looks like a dependency conflict but it doesn't seem to come up for the docker release

Fixed now.
Those kind of conflicts only happen when building a fat jar.  It didn't happen with the docker release, because we don't build a fat jar in the docker image -- we add each 3rd party library as an individual jar file.


Take photo crashes app

When i try to take photo from camera crashes app... Problem in this line
Uri contentUri = FileProvider.getUriForFile(context, context.getPackageName() + ".provider", result);
in RealPathUtil file.. and mobile center crash report is : Tried to access a JS module before the React instance was fully set up. Calls to ReactContext#getJSModule should only happen once initialize() has been called on your native module.

I am also getting this issue. @bahadircivelek any workaround?

I also ran into this issue. After a fresh installation, when I try to take a photo or record a video, it asks me permission whether I am going to allow access to my photo album, which is great. However, after recording, when I press "Use Photo / Video", it crashes.

I found that the accessing photo permission is not set and it never asked. I solved my issue by asking the photo permission before I use the image-picker component.
Try this one: https://github.com/yonahforst/react-native-permissions

I think the cause is Android FileProvider, we need to fix the code in this repo. https://stackoverflow.com/questions/43175014/possible-to-use-multiple-authorities-with-fileprovider.


Can't rotate or resize groups with text

Repro

Create multiple objects including text
Rotate individually works
Group objects
Try to rotate

Expected behavior

Handles for rotation and resize show up and can be used

Actual behavior

No handles show up at all

Probably going to be fixed by #1726

Resize, yes. Rotation won't be.


[Feature]: Typescript - Add typings to both

Describe the bug
Whenever I use both the <Template> and <Story> components, it would be great to be able to set the expected type of let:args.
Ex:
<script lang="ts">
  import Choice from './Choice.svelte';
  import choiceProps from './choiceProps.ts';
</script>

<Template let:args id="ChoiceTemplate">
  // Ideally I would have the option to set that args has the choiceProps type
  <Choice {...args} />
</Template>

<Story
  id="ChoiceStory"
  name="Choice"
  template="ChoiceTemplate"
  args={{
    choiceText: 'Choice 1',
    value: 'choice-1',
    name: 'choice-1'
  }} // Same thing here
/>

I'm not sure this is solveable within svelte-csf; svelte doesn't have support for typescript outside of the script tags, which has been an open issue for several years. See the issue at @sveltejs/svelte #4701

I'm not sure what this is really requesting to change in addon-svelte-csf as it seems like something that would need to be addressed in Svelte itself as @Masstronaut suggested. His suggestion seems like a reasonable one in the meantime. Given that, I'm going to close this in favor of https://github.com/sveltejs/svelte/issues/4701

@benmccann in case it's not on your roadmap, svelte 5 adds typescript support in the svelte markup sveltejs/svelte#9482, so I believe this should be possible now (and greatly appreciated! 🙏)
Not sure if it makes more sense to re-open here or spin up a new issue for it. It would require svelte 5, making it a potentially breaking change for svelte 4 users.


feat: update to eye v3.4.0

feat: update to eye v3.4.0

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

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

Your semantic-release bot :package::rocket:


DEP: execute sparse array API deprecations

Follow-up to #18507

Two seemingly unrelated warnings in the doc build:
Running Sphinx v7.3.2
WARNING: The config value `nb_execution_excludepatterns' has type `list'; expected `Any'.
SciPy (VERSION pull/20499)
[...]
reading sources... [ 97%] tutorial/interpolate/1D
<string>:19: DeprecationWarning: invalid escape sequence '\s'
reading sources... [ 97%] tutorial/interpolate/ND_regular_grid

and another unrelated test failure in Linux Meson tests / Linux - 32 bit:
scipy/sparse/linalg/_isolve/iterative.py:842: in gmres
    x += y @ v[:col+1, :]
E   RuntimeWarning: invalid value encountered in matmul
[...]
=========================== short test summary info ============================
FAILED scipy/sparse/linalg/_eigen/arpack/tests/test_arpack.py::test_hermitian_modes
= 1 failed, 48288 passed, 2230 skipped, 14574 deselected, 567 xfailed, 13 xpassed in 823.38s (0:13:43) =

The benchmark failures are real though...

CC @perimosocordiae, in case you want to double check that this has been done correctly.


[Bug] [web] Devops abnormal time display

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

What you expected to happen
Time display is normal
How to reproduce
As shown in figure
Anything else
No response
Version
dev
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

[Fix][web] fix devops duration parse error #1473


No checksum validation error on blob upload

Which service(blob, file, queue, table) does this issue concern?
Blob
Which version of the Azurite was used?
latest and 3.16.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
Dockerhub
What's the Node.js version?
See docker image
What problem was encountered?
When uploading a blob and passing locally calculated MD5 hash, the API should throw an error. Azure Storage Emulator returns the expected HTTP error, Azureite returns no error (but calculates the correct hash).
It is not a huge thing, but conflicts with this:

Azurite tries to align with Azure Storage error handling logic, and provides best-efforts alignment based on Azure Storage online documentation. But CANNOT provide 100% alignment, such as error messages (returned in error response body) maybe different (while error status code will align).

Steps to reproduce the issue?
Using nuget Azure.Storage.Blobs

string _ConnectionString = "UseDevelopmentStorage=true";
BlobServiceClient _blobClient = new BlobServiceClient(_ConnectionString);

using var stream = new MemoryStream(new byte[] { 0, 1, 0, 1, 0, 1 });

var container = _blobClient.GetBlobContainerClient("test");
await container.CreateIfNotExistsAsync();

var blockBlob = container.GetBlockBlobClient("myfile");
try
{
	var x = await blockBlob.UploadAsync(stream,
		new BlobUploadOptions
		{
			HttpHeaders = new BlobHttpHeaders
			{
				//ContentHash = Convert.FromBase64String("9V+R+Ra60Erbh/oKA1AA+g==") // Correct
				ContentHash = Convert.FromBase64String("0V+R+Ra60Erbh/oKA1AA+g==") // Incorrect
			}
		}).ConfigureAwait(false);
}
catch (RequestFailedException ex) when (ex.Status == 400 && ex.ErrorCode == BlobErrorCode.Md5Mismatch)
{
        // Azureite does not throw here, storage emulator does
	throw new Exception("The checksum of the uploaded file does not match the checksum of the request");
}

var blob = container.GetBlockBlobClient("myfile");
var props = blob.GetProperties();
Debug.Assert(props.Value.ContentLength == 6, "blob size should be the same as the input stream");
Console.WriteLine("Saved MD5 value: " + Convert.ToBase64String(props.Value.ContentHash));

Have you found a mitigation/solution?

@LXBdev
Thanks for raising this issue!
It looks the error is not throw since the header send by your code is "x-ms-blob-content-md5: 0V+R+Ra60Erbh/oKA1AA+g=="
But Azurite will only try to get content md5 from header "content-md5"，see https://github.com/Azure/Azurite/blob/d9d480a44980d1bb46437d9cd6cdb0aa5becf377/src/blob/handlers/BlockBlobHandler.ts#L47
So the hash is not get by Azurite, and not checked.
Besides that, the azurite return code 400 is correct , but the return errorCode match server (Azure server return: Md5Mismatch, Azurite return: InvalidOperation) . To make above code work, this also need be fixed.
And need to check all API has content upload like: upload blob, stage block, upload page, appendblock.
@LXBdev
Azurite welcome contribution.
It would be great is your can raise a PR to fix it.


docs: add prom per_consumer option and update example

Summary

Add per_consumer to Prometheus plugin docs
Update Prometheus plugin docs example with new options and remove legacy ones

Reason

per_consumer exists in Kong code since https://github.com/Kong/kong/commit/7e205b0fb3c1536526943e856e38943dfc8b9a10
updated example contains outdated informations

Testing
Changes have been locally tested using make run and new doc preview in browser.

@fffonion The field description looks ok to me. Could you review the changes in metrics introduced by this?


Build failed. Path or pattern "bower_components/lodash/lodash.js" did not match any files

This problem occurs for versions 0.0.28 and 0.0.29 of ember-cli-mirage
Run ember build and get error of "Build failed. Path or pattern "bower_components/lodash/lodash.js" did not match any files".
Run bower install lodash and ember build then works as expected.
Saw https://github.com/samselikoff/ember-cli-mirage/issues/114 but it still doesn't seem to be working as expected.

it's not mirage, it's your version of ember cli, it's not running ember g ember-cli-mirage after install
what version of CLI?

Oh yeah...that would do it.  What I'm actually doing is I bumped up the version of the library in package.json but am never re-running the install command and/or running the generator.
When I ran ember g ember-cli-mirage all now works correctly.  Sorry about that and thanks!
The app is currently running 0.1.15 of Ember CLI

glad to hear :)


Create Post “dva-c01-studying-ec2”

Automatically generated by Netlify CMS

👷 Deploy Preview for dazzling-dieffenbachia-448a02 processing.

Name
Link

🔨 Latest commit
aaf292705265cc9e97354e33e21ba7681bae07b1

🔍 Latest deploy log
https://app.netlify.com/sites/dazzling-dieffenbachia-448a02/deploys/62c494e86f54070008ee1509


Add wget and curl to remote_file_copy_binaries

What type of PR is this?
/kind rule-update

Any specific area of the project related to this PR?
/area rules

What this PR does / why we need it:
Added additional binaries that are capable of remote file copy. These binaries are commonly used as a prerequisite to command and control.
Which issue(s) this PR fixes:

N/A
Special notes for your reviewer:
N/A
Does this PR introduce a user-facing change?:

rule(Launch Remote File Copy Tools in Container): add additional binaries: curl and wget.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

5247dd0 Add wget and curl to remote_file_copy_binaries

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Welcome @ec4n6! It looks like this is your first PR to falcosecurity/falco 🎉

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ec4n6
To complete the pull request process, please assign mstemm after the PR has been reviewed.
You can assign the PR to them by writing /assign @mstemm in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

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

@ec4n6: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

5247dd0 Add wget and curl to remote_file_copy_binaries
e098dd0 Merge branch 'add-wget-curl-rules' of https://github.com/ec4n6/falco into add-wget-curl-rules

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Opening a new PR due to commit and merge fails.


pose question

Hi,
It's not an error.
I wanna to know why the image_seq's shape is looking like that.
For a 5-sequence case,
(128, 416, 3) => np.hstack => (128, 832, 3) => np.hstack => ... => (128, 2080, 3)
I thought that it would be (5, 128, 416, 3) for the image_seq!
pred = sfm.inference(image_seq[None, :, :, :], sess, mode='pose')
Is there any help?
THANKS

These lines (https://github.com/tinghuiz/SfMLearner/blob/master/SfMLearner.py#L283-L285) will unpack the image sequence into a target image (i.e. central frame) and a stack of source images (concatenated along the color channels). The target is further concatenated with the source image stack later for pose network inference (https://github.com/tinghuiz/SfMLearner/blob/master/nets.py#L19).


Documentation on security implications and use of phone numbers in Keybase

I was surprised to see the message "Add your phone number so your friends can find you." on my Keybase Android app today. But I see no way to search by phone number. And the only options are "Add number" (by default) and "Later".
I searched high and low for documentation on the intended use of this, what Keybase would do with it, how it could be used by me and my friends, what the privacy policy was, etc etc.
I found nothing in the blog, and only a smattering of mentions here in issues. That's very distressing for a privacy-focused app.
The most interesting hit was Stop nagging about email verification and allow disabling unwanted features · Issue #18903 · keybase/client with its link to Why Apple’s Notification Bubbles Are so Stressful - OneZero. And I agree. Having that red highlite of "1" on the bottom left of my app is very distracting even though I'm colorblind so red is not very bright.
I also found a bunch of PRs but no design document or the like.
So what's up? Why would this feature be helpful? What are the security issues? And how do I get that "1" to go away without suggesting I'm interested in seeing this request again, until I know what's in it for me?

you can search by phone number by just typing in the number in user search

you can search by phone number by just typing in the number in user search

but what if i don't WANT to be discoverable by phone, email or other methods?
Like @nealmcb says, I want the simple feature to say "don't ask me again about this"

@nealmcb We'll have a doc out soon.
You can get rid of the badge by clicking "later", the app won't ask you again unless you go to the settings page yourself to add a phone number.

We wrote some docs at https://keybase.io/docs/chat/phones_and_emails. Let us know if there's anything else you want to know that's missing, we'll add it. Thanks!

I think the information from that handy document, and tips on privacy implications, should be part of the client documentation. There are no tips in the client on how to search for phone numbers, and it is counter-intuitive at least for me that you'd just search "people" e.g. in the Keybase filter.
The "Import phone contacts" option in Settings should link to the document or provide related info in a popup or the like.
Better clarity on this will help both attract some people to use the feature via your guarantees of not abusing the information, and also give more confidence in Keybase in general to other people who might otherwise see this as a big deviation from their expectations.
Can you re-open this until this sort of info is more discoverable in the client?

I think the information from that handy document, and tips on privacy implications, should be part of the client documentation.

Agree, we will link to this page from within the client in the next release.

There are no tips in the client on how to search for phone numbers, and it is counter-intuitive at least for me that you'd just search "people" e.g. in the Keybase filter.

This will be clearer in the next release.

Can you re-open this until this sort of info is more discoverable in the client?

Okay

I may have missed it when skimming the conversation—could you please add "phone number and email verifications are only verified by the Keybase server" to your privacy policy and also clarify that contact information provided for finding other users does not go through any third-party services?

Please consider not requiring me to provide my personal contact info at all to Keybase. I find this abhorrent for a supposedly pro-privacy company to require this information.
See also https://github.com/keybase/client/issues/18903

It's considered and it currently works. Please check again. If it's actually requiring an email or phone number, it's a bug.

Thank you so much @maxtaco! Removing the email was the solution I was seeking.  It no longer has the orange dot now and I am happy!

We wrote some docs at https://keybase.io/docs/chat/phones_and_emails. Let us know if there's anything else you want to know that's missing, we'll add it. Thanks!

That link is (now) 404 - the correct URL is https://book.keybase.io/docs/chat/phones-and-emails.

Also navigation to that page is broken; submitted as https://github.com/keybase/book-content/issues/52

I think the information from that handy document, and tips on privacy implications, should be part of the client documentation.

Agree, we will link to this page from within the client in the next release.

This link is now broken for the same reason as listed in https://github.com/keybase/book-content/issues/52.
Also, you only added it to the mobile client, and missed the desktop client.  Filed as #24262.

Can you re-open this until this sort of info is more discoverable in the client?

Okay

Please re-open again until the above is fixed.  Thanks!


"{取得 | 、 | を設定。" needs to be replaced with "{ Get | Let | Set }"

https://docs.microsoft.com/ja-jp/office/vba/language/concepts/getting-started/writing-a-property-procedure

Working on fix

(related issue: #846 )


PR: Conform tutorial to docs style guide and further minor improvements

Pull Request Checklist

[x] Read and followed this repo's Contributing Guidelines
[x] Based your PR on the latest version of the correct branch (master or 3.x)
[x] Followed PEP8 for code style
[x] Ensured your pull request hasn't eliminated unrelated blank lines/spaces,
modified the spyder/defaults directory, or added new icons/assets
[x] Described your changes and the motivation for them below
[x] Noted what issue(s) this pull request resolves, creating one if needed

Description of Changes

A follow-on to #7641 / #7643 with the primary purpose of conforming the tutorial to our doc style guide to further enhance its appearance and external consistency, and also improve maintainability and internal consistency between them. Also, fixed some minor typos and refined the prose and formatting. See #7652 for the full list of what was done.
The final version was built with Sphinx in nitpicky mode, with no issues reported and the result was examined to confirm everything rendered well; also, it was run through Sphinx linkcheck with all green. Finally, it was examined as it will appear to users in Spyder itself reading through all sections, and no issues were found except for an issue where if ref tags (.. _section-ref:) were placed before section headers, that header would no longer collapse once expanded. Presumably, this is a bug in Spyder's help viewer (likely whatever custom HTML/CSS/JS is used for the collapsible sections), but to work around it with minimal consequences, the reference tags were simply placed after the section headers, which worked just fine (since the links were already named manually).
Overall, while the style guide changes approved in spyder-ide/spyder-docs#13 was implemented as in that issue, minimal content changes were made (compared to the previous PR); only typo fixes and minor language and format refinements, so hopefully this should be an easy review.
Thanks!
Issue(s) Resolved

Fixes #7652

it was examined as it will appear to users in Spyder itself reading through all sections, and no issues were found

Ok, I'll trust you in this one because I don't have time to test it locally.

This is a great pull request, improving the quality of the tutorial and Spyder. Many thanks for doing this; it looks good to me!

Thanks so much for your kind words, Professor @fangohr .
@ccordoba12 Since the changes are small but noticeable (2 single-word typos, 2 tiny consistency tweaks, updating the URL and rewriting a sentence) any chance we can merge it to both 3.x and master or would it be too much work for you (since the file path of the tutorial was changed)? Either way I'll submit a PR with the changes against the appropriate branch as soon as you give me the word. Thanks!

+This tutorial was originally based on notes <https://fangohr.github.io/blog/spyder-the-python-ide-spyder-23.html>__ by Hans Fangohr <https://fangohr.github.io/>, that are used at the University of Southampton <https://www.southampton.ac.uk/> to teach Python for computational modelling <https://www.southampton.ac.uk/~fangohr/teaching/python.html>__ to undergraduate engineers and postgraduate PhD students for the Next Generation Computational Modelling <http://www.ngcm.soton.ac.uk/>__ doctoral training centre.
Sure, of course.
FYI, on that updated page itself you link back to the Southampton version of the tutorial rather than the one on your site.
Thanks, yes, this will change at some point, but if you point to the github.iohttp://github.io page now, then we don’t need to update the spyder site anymore.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/spyder-ide/spyder/pull/7659#discussion_r212129507, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AER_nxJaDhfpfAElq8QyRivusLRG4PQwks5uTdn0gaJpZM4V0_EL.

@fangohr Yes, of course. Just wanted to point that out, heh.

any chance we can merge it to both 3.x and master

Sure, the fixes suggested by @fangohr can go to 3.x instead of master.


cleos system delegatebw in some case requires the auth of the receiver

So in this case I have 2 accounts called andrianto and andri. Details are the following
$ cleos get account andrianto
privileged: false
permissions:
     owner     1:    1 EOS8kE63z4NcZatvVWY4jxYdtLg6UEA123raMGwS6QDKwpQ69eGcP
        active     1:    1 EOS8kE63z4NcZatvVWY4jxYdtLg6UEA123raMGwS6QDKwpQ69eGcP
memory:
     quota:     60.32 Mb     used:     4.016 Kb

net bandwidth: (averaged over 3 days)
     staked:   25000150.0000 SYS           (total stake delegated from account to self)
     delegated:      10.0000 SYS           (total staked delegated to account from others)
     used:             6.832 Kb
     available:        13.04 Tb
     limit:            13.04 Tb

cpu bandwidth: (averaged over 3 days)
     staked:   25000150.0000 SYS           (total stake delegated from account to self)
     delegated:      10.0000 SYS           (total staked delegated to account from others)
     used:             71.98 ms
     available:    3.982e+05 hr
     limit:        3.982e+05 hr

producers:     <not voted>

and
cleos get account andri
privileged: false
permissions:
     owner     1:    1 EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
        active     1:    1 EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
memory:
     quota:     59.44 Mb     used:     3.498 Kb

net bandwidth: (averaged over 3 days)
     staked:       1000.0000 SYS           (total stake delegated from account to self)
     delegated: 1000010.0000 SYS           (total staked delegated to account from others)
     used:               810 bytes
     available:        534.6 Gb
     limit:            534.6 Gb

cpu bandwidth: (averaged over 3 days)
     staked:       1000.0000 SYS           (total stake delegated from account to self)
     delegated: 1000010.0000 SYS           (total staked delegated to account from others)
     used:             8.857 ms
     available:    1.594e+04 hr
     limit:        1.594e+04 hr

producers:
     andrianto

Calling cleos system delegatebw eosio andrianto "10.0000 SYS" "10.0000 SYS" --transfer success without any problem. However, when I tried to call cleos system delegatebw eosio andri "10.0000 SYS" "10.0000 SYS" --transfer, it fails with the following error

Saying that andri auth is required which is kinda weird since andri is the receiver in this case.
Without --transfer, everything is fine
My wallet has the private keys of eosio, andrianto, and andri.

Strangely this is fine in local node but not in the testnet

Okay. I think I got the condition to trigger this.
For the above condition, it seems that andrianto didn't cast a vote while andri cast a vote. When andri removed his vote, the above (delegatebw andri) action can be executed successfully. While when andrianto cast his vote, the above (delegatebw andrianto) action fails.
This explains why in my local node, I didn't see that problem since I didn't cast a vote yet...

resolved by #3679


Fix a bunch of places we forget to aws_raise_error()

Our error handling strategy is simple to explain, but easy to get wrong. Inspired by this PR that fixed some obviously-incorrect-code, I decided to search for more easy-to-spot accidents:

cmd-shift-f (case sensitive) return AWS_(?!OP_): look for places we accidentally return error codes, instead of raising them
cmd-shift-f AWS_ERROR_SUCCESS: look for places we misuse AWS_ERROR_SUCCESS, returning it instead of AWS_OP_SUCCESS. This doesn't cause bugs (they're both 0) but it's not right either.
cmd-shift-f return AWS_OP_ERR: UGH this had 1200+ hits. Gave a quick eyeball scan to catch places we return AWS_OP_ERR without one having been raised beforehand. I found A LOT of these mistakes, but I'm sure there are more.

TODO in the future:

cmd-shift-f return NULL (there are 1500+ of these)
Give more attention to the following files. Which I know have way more problems, but I gave up:

json.c in aws-c-common
darwin_pki_utils.c in aws-c-io
secure_tunneling.c in aws-c-iot
serializer.c in aws-c-iot

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

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

Comparison is base (7f55a9c) 83.23% compared to head (fbb4e2d) 83.15%.

Files
Patch %
Lines

source/json.c
0.00%
2 Missing :warning:

source/logging.c
0.00%
2 Missing :warning:

source/log_formatter.c
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1089      +/-   ##
==========================================
- Coverage   83.23%   83.15%   -0.08%
==========================================
  Files          56       56
  Lines        5808     5813       +5
==========================================
  Hits         4834     4834
- Misses        974      979       +5

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


e2e: Don't fail test on transient recoverable API lookup

Before this commit, calls to WaitForConditionsOnHostedControlPlane() could
fail a test if an API lookup fails even though that lookup is recoverable and
retried automatically. This made the test flaky.
This commit fixes the code so that these retriable errors are logged but do
not fail the test.
This commit also moves a log message which was intended to emit during retries
but was instead placed at the exit point.

/lgtm


xFailOverCluster: Updating README.md, adding CHANGELOG.md, adding GitHub templates

Changes to xFailOverCluster

Added 'Code of Conduct' text to the README.md (issue #44).
Added TOC for all resources in the README.md (issue #43).
Fixed typos and lint errors in README.md.
Fixed style issue in example in README.md.
Removed 'Unreleased' "tag" from the resources xClusterQuorum and xClusterDisk (issue #36)
Added new sections to each resource (Requirements, Parameters and Examples) in the README.md. Some does not yet have any examples, so they are set to 'None.'.
Added GitHub templates PULL_REQUEST_TEMPLATE, ISSUE_TEMPLATE and CONTRIBUTING.md (issue #45).
Split the change log from README.md to a seperate file CHANGELOG.md (issue #48).
Added the resource xClusterPreferredOwner to README.md (issue #51).
Added the resource xClusterNetwork to README.md (issue #56).

Fixes #44
Fixes #43
Fixes #36
Fixes #45
Fixes #48
Fixes #51
Fixes #56

This change is

@johlju,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@bgelens or @RichardSiddaway Can anyone of you review this when you got a chance?
I can send in an other PR that fixes the tests before we merge this one. But it's gonna take a few days (probably this weekend).

Nice! I think I'll adopt some of those templates pretty soon!

Reviewed 4 of 5 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 10 unresolved discussions, some commit checks failed.

README.md, line 28 at r2 (raw file):

## Change log

A full list of changes in each version can be found in the [change log](CHANGELOG.md).

Is this a general approach for all resources?

README.md, line 124 at r2 (raw file):

#### Parameters

* **IsSingleInstance** Always set to `Yes` to prevent multiple quorum settings per cluster.

Technically, this is actually to ensure this resource can only be used once in the configuration so ping/pong behavior is blocked.
A cluster can only have one quorum, so this is used to prevent on and on change behavior of the quorum.
(I do see it is a copy paste issue from your side so maybe an issue to change this later?)

README.md, line 125 at r2 (raw file):

* **IsSingleInstance** Always set to `Yes` to prevent multiple quorum settings per cluster.
* **Type** Quorum type to use: *NodeMajority*, *NodeAndDiskMajority*, *NodeAndFileShareMajority*, *DiskOnly*.

Again, probably a fix for another issue but the resources above have the property types specified and these don't (not repeating this remark for other occurrences )

README.md, line 169 at r2 (raw file):

        [ValidateNotNullorEmpty()]
        [PsCredential]
        $domainAdminCredential

Parameters should be PascalCase. https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.md#parameter-names-use-pascal-case

README.md, line 171 at r2 (raw file):

        $domainAdminCredential
    )

Missing an Import-DscResource of xFailOverCluster module. Example won't work

README.md, line 184 at r2 (raw file):

            Ensure = 'Present'
            Name   = 'RSAT-Clustering-PowerShell'

Unnecessary white space (not repeating for other occurrences)

README.md, line 188 at r2 (raw file):

        }

        WindowsFeature RSATClusteringCmdInterface

Casing consistency on resource names?

README.md, line 193 at r2 (raw file):

            Name   = 'RSAT-Clustering-CmdInterface'

            DependsOn = '[WindowsFeature]RSATClusteringPowerShell'

'=' alignment ? (not repeating for other occurrences)

README.md, line 196 at r2 (raw file):

        }

        xCluster ensureCreated

Casing consistency on resource names?

README.md, line 202 at r2 (raw file):

            DomainAdministratorCredential = $domainAdminCredential

           DependsOn = “[WindowsFeature]RSATClusteringCmdInterface”

Indentation issue? (I see a couple but could be Reviewable?)

Comments from Reviewable

I will get to this changes later tonight.

Review status: all files reviewed at latest revision, 10 unresolved discussions, some commit checks failed.

README.md, line 28 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
Is this a general approach for all resources?

It is not. The PSDscResource uses README.md https://github.com/PowerShell/PSDscResources#versions
But the README.md tend to be long, and the version history is at the end, so it not easy to find. Also, I feel it's easier to tell contributors to 'update Unreleased section in the CHANGELOG.md', than 'update the Unreleased section under the Version section  at the bottom of the README.md' :)
If you feel we should keep it in README.md I happy to move it back.

README.md, line 124 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
Technically, this is actually to ensure this resource can only be used once in the configuration so ping/pong behavior is blocked.
A cluster can only have one quorum, so this is used to prevent on and on change behavior of the quorum.
(I do see it is a copy paste issue from your side so maybe an issue to change this later?)

Actually I did not change that description, that was there prior to this PR. I did not even read it. :smile:  But I will update the description!
Also added an issue yesterday to fix descriptions; https://github.com/PowerShell/xFailOverCluster/issues/59. I will comment on that to verify so the descriptions are also correct. :smile:

Comments from Reviewable

Review status: all files reviewed at latest revision, 10 unresolved discussions, some commit checks failed.

README.md, line 28 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
It is not. The PSDscResource uses README.md https://github.com/PowerShell/PSDscResources#versions
But the README.md tend to be long, and the version history is at the end, so it not easy to find. Also, I feel it's easier to tell contributors to 'update Unreleased section in the CHANGELOG.md', than 'update the Unreleased section under the Version section  at the bottom of the README.md' :)
If you feel we should keep it in README.md I happy to move it back.

I think it's a good idea to split up. Probably a good idea to raise an issue at DscResources to have this standardized?

Comments from Reviewable

I added a bunch to this commit. Added comments to the example. Sorry for the additions, but hard not to try to improve something when you see something. :smile:

Review status: 3 of 5 files reviewed at latest revision, 10 unresolved discussions, some commit checks failed.

README.md, line 28 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
I think it's a good idea to split up. Probably a good idea to raise an issue at DscResources to have this standardized?

Done. Brian has already done that; https://github.com/PowerShell/DscResources/issues/167

README.md, line 124 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Actually I did not change that description, that was there prior to this PR. I did not even read it. :smile:  But I will update the description!
Also added an issue yesterday to fix descriptions; https://github.com/PowerShell/xFailOverCluster/issues/59. I will comment on that to verify so the descriptions are also correct. :smile:

Done. Used the text from the best practice article, which is also used in other resources in other modules.
https://msdn.microsoft.com/en-us/powershell/dsc/singleinstance

README.md, line 125 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
Again, probably a fix for another issue but the resources above have the property types specified and these don't (not repeating this remark for other occurrences )

Done. Got to late yesterday, so submitted an issue, but I fixed now.

README.md, line 169 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
Parameters should be PascalCase. https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.md#parameter-names-use-pascal-case

Done.

README.md, line 171 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
Missing an Import-DscResource of xFailOverCluster module. Example won't work

Done.

README.md, line 184 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
Unnecessary white space (not repeating for other occurrences)

Done.

README.md, line 188 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
Casing consistency on resource names?

Done. I over clarified them, let's try to avoid abbreviations.

README.md, line 193 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
'=' alignment ? (not repeating for other occurrences)

Done. I removed all aligned '=' since we don't have a guideline to either use or not use, and I feel most of the code in DSC Resource Kit does not align equal signs.

README.md, line 196 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
Casing consistency on resource names?

Done.

README.md, line 202 at r2 (raw file):
Previously, bgelens (Ben Gelens) wrote…
Indentation issue? (I see a couple but could be Reviewable?)

Done. Reviewable was correct.

Comments from Reviewable

When PR #63 is merged, then we can merge this one (after I rebased this one). And after review is finished of course 😄

 Great job!!

Reviewed 2 of 2 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from Reviewable

@bgelens Rebased. Please verify in Reviewable that nothing changed. I did change the CHANGELOG.md to move the entries from the recently merged PR.

 Exactly as planned ;)

Reviewed 1 of 1 files at r5.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Corrects issue preventing unit tests from displaying in VS Test Runner.

Migrates test project to .NET Core 1.1.
Adds compatible dependency.

Before

After

Nice! Thanks!


Expose types and functions of package

I'm very grateful for this project, and I really like it. Thanks for all your effort :)
The reason behind this PR is that I want a more pkg.go.dev like experience, i.e. a sidebar/ navbar that updates based on the position on the page, etc.

Thanks for the PR, @l0nax. It makes sense to expose this information in the front matter data—I assume you're using this information somehow to fill a TOC?
That said, I don't think the raw godoc.Types should be exposed.
Those include a lot of the information needed to render the HTML, and don't necessarily have a stable shape.
For example, none of the decl-rendering or comment rendering logic will work in the frontmatter template.
If we could instead create a copy of a subset of that information for frontmatterData, that would be much better.
For example, for the types, we would probably have:
type frontmatterType struct {
  Name string

  Constants, Variables []*frontmatterValue
  // ..
}

type frontmatterValue struct {
  Names []string
}

It'll need a little boilerplate to build this mirror subset, but it'll be a stable API for the frontmatter templates that I can commit to not breaking in the future.


Lucee 5 references and updating the README

Updated the install script to look at Lucee 5, and a more recent version of Java.
Also changed the README to download to ~/ instead of /root/

@andyj thanks for all the work here -- one thing that is holding me back from merging, besides doing some testing is that it appears to be using the viviotech installer which includes a bundled version of Tomcat. While the installer is great, I don't like that I have to update tomcat manually. That is why this repo uses the Ubuntu tomcat7 package, so you can update it using apt-get

Bin this pull request. I like your approach about different branches for
different setups I.e 16.04 LTS support.
Happy to help test new development out though.
On 7 June 2016 at 17:33:26, Pete Freitag<EMAIL_ADDRESS>wrote:

@andyj https://github.com/andyj thanks for all the work here -- one
thing that is holding me back from merging, besides doing some testing is
that it appears to be using the viviotech installer which includes a
bundled version of Tomcat. While the installer is great, I don't like that
I have to update tomcat manually. That is why this repo uses the Ubuntu
tomcat7 package, so you can update it using apt-get
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/foundeo/ubuntu-nginx-lucee/pull/10#issuecomment-224337788,
or mute the thread
https://github.com/notifications/unsubscribe/AAD-LOoEiW5TFliqlszrE7DN8u5wRffpks5qJZ1WgaJpZM4IvX1i
.

Closing this as requested.


Add files via upload

Ah, looking at the branch name maybe the whole point was to overwrite bundle.js to avoid git change warnings.  I'll get back to you about how we should handle compiled files, ideally they aren't in git at all.


FEATURE: Sovler

Solve for any unknown (for example payment amount or interest rate) when given value on maturity date is 0 (for example closing balance)

Implemented in 0.2.0


drt: Fix a number of integer overflow issues

There are a number of places we compute distance squared, and on
larger designs this can overflow an frCoord which is a signed 32
bit integer.  Create a uint64_t datatype called frSquaredDistance
to store these values without overflow.
Also create pt2ptDistSquare() to square the distance between
two points safely.

This patch ended up larger than I was expecting, so it could do with a close review.

The original PR had a bug in it which led it to being reverted.  I've fixed that and un-reverted it.  It will show up in the next public push.

@maliberty Thank you


Error: Error building CPLEX: │ ERROR: LoadError: Unable to locate CPLEX installation.

This is a Windows 10 64-bit Machine.

I have Julia ver 1.1.0
This is my Windows ENV variable for CPLEX:

CPLEX_STUDIO_BINARIES129=C:\Program Files\IBM\ILOG\CPLEX_Studio129\opl\bin\x64_win64;C:\Program Files\IBM\ILOG\CPLEX_Studio129\opl\oplide;C:\Program Files\IBM\ILOG\CPLEX_Studio129\cplex\bin\x64_win64;C:\Program Files\IBM\ILOG\CPLEX_Studio129\cpoptimizer\bin\x64_win64
This is my error:
julia> Pkg.add("CPLEX")
 Resolving package versions...
 Installed CPLEX ─ v0.5.0
  Updating `C:\Users\gost_\.julia\environments\v1.1\Project.toml`
  [a076750e] + CPLEX v0.5.0
  Updating `C:\Users\gost_\.julia\environments\v1.1\Manifest.toml`
  [a076750e] + CPLEX v0.5.0
  Building CPLEX → `C:\Users\gost_\.julia\packages\CPLEX\NzxB3\deps\build.log`
┌ Error: Error building `CPLEX`:
│ ERROR: LoadError: Unable to locate CPLEX installation. Note this must be downloaded separately. See the CPLEX.jl README for further instructions.
│ Stacktrace:
│  [1] error(::String) at .\error.jl:33
│  [2] top-level scope at C:\Users\gost_\.julia\packages\CPLEX\NzxB3\deps\build.jl:67
│  [3] include at .\boot.jl:326 [inlined]
│  [4] include_relative(::Module, ::String) at .\loading.jl:1038
│  [5] include(::Module, ::String) at .\sysimg.jl:29
│  [6] include(::String) at .\client.jl:403
│  [7] top-level scope at none:0
│ in expression starting at C:\Users\gost_\.julia\packages\CPLEX\NzxB3\deps\build.jl:66
└ @ Pkg.Operations C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.1\Pkg\src\Operations.jl:1075

I also checked my Cplex folder (C:\Program Files\IBM\ILOG\CPLEX_Studio129\cplex\bin\x64_win64) and these are the files:
cplex.exe
cplex1290.dll
cplex1290processtransport.dll
cplex1290processworker.dll
cplex1290remote.dll
cplex1290remotejni.dll
cplex1290tcpiptransport.dll
cplex1290tcpipworker.dll
cplexamp.exe
ILOG.Concert.dll
ILOG.Concert.xml
ILOG.CPLEX.dll
ILOG.CPLEX.xml

I was able to fix this for myself. I have Julia open while I installed CPLEX, so Julia was not reading the newly created ENV variable. After I closed Julia and restarted it, I was able to build CPLEX.


Remove error print from XRServer.find_interface

This PR removes the error print from the XRServer.find_interface() method. It is a valid (and expected?) workflow to check if an interface exists by running this method, so we should not print an error, just return null.
Also, this PR simplifies the logic, since int idx is not needed.

Thanks!


Error while tracking cells in ensemble mode

Hi,
When I tried to track my volumes series using ensemble mode, I run into the following error(see attached).
error_ensemblemode.txt
I thought the original volume data contained missing values, so I checked it, but it seems there aren't any. Please let me know if you have any clues, thanks!

Could you share the values of t and confirmed_coord_t1.real? You can check them with %debug

Thank you for your reply. Here is what I got,
t_confirmed_coord.txt

Uhmm, this is strange. It seems the cell coordinates at t=2 extracted during StarDist segmentation contain NaN values. I can't explain the reason without testing it with the actual data.

I see.
Looks like I don't get this type of error while using some other volume data.
Is it possible that there were missing values in the raw data pixels?
Or should I retrain another data for StarDist segmentation?

It is strange that StarDist generates NaN values for the segmented cells. I am not sure of the reason. Perhaps you could test whether the segmentation results contain NaN values for time points other than t=2. To do this, you can run the following code:
t = 1
coords_at_t = np.load(str(tracker.results_dir / "track_results" / "coords_real" / f"coords{str(t).zfill(6)}.npy"))

Try changing the value of t to see what happens.

I only got coords000001.npy and it also contained NaN values.

Hi,
It turned out that I made the manual label so small that gaussian filtering erased it.
I guess that is why the segmentation results contained NaN values after coords2image.interpolate(interpolation_factor=interpolation_factor) .
Apologies for the trouble.
Thank you.


Make this a module for go 1.11 and above.

The use of the GO111MODULE environment variable will be unavailable in go 1.17, requiring that this be migrated to a module. This solves that issue, setting the minimum go version for module use at 1.11.

@phayes any plans to merge this? I see you aren't actively maintaining this package, but trying to understand whether it's fully defunct.


Comparison with AFNOR AZERTY layout?

Hello,
It is an open-question, very subjective, but I would love to know why you didn't consider the AFNOR AZERTY layout? Maybe this layout is intended for people already using a qwerty layout? Perhaps your project precedes this norm?
I am curious about your motivations, because after having tried all layouts and their variants (qwerty, qwerty-intl, bepo) I finally found the afnor layout better for both writing and programming.
Anyway, the more the better, it's always nice to have more choice. Thank you for this project.

Related: https://github.com/qwerty-fr/qwerty-fr/issues/12
I firmly believe that AZERTY (NF Z71-300) is a step in the right direction, but it has very significant shortcomings that make it a less appealing option for most people. I'll write another comment when I'm on my PC to lay out my thoughts. 😊

No problem. And as I stated before, I am sure there is also a lot of personal reason to prefer one layout over another :)

Superseded by https://github.com/qwerty-fr/qwerty-fr/issues/12


Memoizes range for efficiency

This breaks determinism, but only because the order of cells in agents' cellsInRange changes. I'm looking into why, because the order should really be the same. Also, a good next step to optimize findNeighborhood would be to make cellsInRange a set and find its intersection with Sugarscape's self.agents list.
If the memoization takes up too much storage, we can instead store the difference between the current range and the previous range (the additional cells added) rather than storing the whole list for every distance.

The order was different because self.cellsInRange was a reference to cell.ranges[distance] instead of a copy, which was then shuffling cell.ranges[distance] in findBestCell. This has been fixed and determinism is now maintained with the current repo.

Finding 50 different radial ranges for 50x50 cells in the environment takes exponentially too long. Thoughts?

If cell X can see cell Y at range 10, then cell Y can also see cell X at range 10, etc. See if that provides a useful reduction?

Ready for testing.

Initial testing (50 seeds out to 2k timesteps) shows a significant time reduction:
Current repo head:
real	15m38.914s
user	231m6.808s
sys	0m10.446s

This branch:
real	11m14.852s
user	166m25.475s
sys	0m7.853s

Will test more thoroughly before merge, but I will be checking style and general fit and finish first.

Let me know if any of the readability changes I made accidentally broke any logic.

No, everything looks good. In terms of other optimizations, I'm eyeing findNeighborhood to see if I can use set intersection with an agent's cells in range and a set of all cells with agents on them. I'm not sure if it would actually be faster with larger numbers of agents.
As for this PR, there might be a way to speed up radial range calculations when the max distance is smaller. Currently, even when the max distance is less than the environment size, every cell combination has to be checked (2500 choose 2). I'm going to keep thinking about this for now, but barring any further breaks or issues, the current implementation can be merged.

Testing 20 seeds with radial vision and movement and moore neighborhoods:
Current repo head:
real	60m26.204s
user	229m56.582s
sys	0m2.806s

This branch:
real	8m40.028s
user	75m46.485s
sys	0m5.386s

Even with the same seeds and configs, the outcomes between the two branches are different due to when random events happen. However, the societal outcomes are more or less the same.


Replace existing Mongo Driver

The current Mongo driver we use is no longer supported and we need to look at replacing it. Potentially the best candidate for replacement is the community supported fork of the mgo driver provided by globalsign. Lenny from Intel says his team has done a replacement similar to what we need and it was relatively painless.
An attempt has already been made to investigate Mongo's official Go driver implementation but it is in very early alpha, and we encountered problems with it.

Does it make sense to make this part of the Mongo implementation of the DB abstraction?

Best case scenario, for any code found in the db/mongo package we can just find/replace the import statements. If there are corrections based on the new library's API, they should be contained there -- other than the glide.yaml changes of course.

@greenrobot I did a POC attempting to integrate that driver before the Edinburgh F2F and it was in no way ready for prime time. The other advantage to using the globalsign.mgo driver is that it's a community supported fork of the driver we use now. According to the Intel team, it will be a drop-in replacement whereas the MongoDB driver would require rework.

Updates merged into master


More consistent API

Actual
/test.js
browser.saveDocumentScreenshot('file.png', options);
browser.checkDocument(options)

/config.js
{
	visualRegression: {
		compare: new VisualRegressionCompare.LocalCompare({
			referenceName : screenshot('/expected/file.png'),
			screenshotName: screenshot('/actual/file.png'),
			diffName      : screenshot('/diff/file.png')
		})
	}
}

Expected
1

let file = 'file.png';

let options = {
     output: {
         actual: '/actual',
         expected: '/expected',
         diff: '/diff'
     }
};

browser.saveDocumentScreenshot(file, options);
browser.checkDocument(file, options)

2
let file = 'file.png';

let options = {
     output: {
          actual ({ test }) {
               return path.join('/actual', test, 'file.png');
          },

          expected ({ test }) {
               return path.join('/expected', test, 'file.png');
          }

           diff ({ test }) {
               return path.join('/diff', test, 'file.png');
          }
     }
};

browser.saveDocumentScreenshot(options);
browser.checkDocument(options);

The second variant is more universal

What do you mean with consistent API?
wdio-screenshot has nothing to do with this library. It's just an internally used lib. What confuses me, that you use both libraries in your test.js. For regression testing it's just enough to use this library. There is no need to save screenshots before checking them. So your test.js should just look like
browser.checkDocument(options)

Expected
1

let file = 'file.png';

let options = {
     output: {
         actual: '/actual',
         expected: '/expected',
         diff: '/diff'
     }
};

browser.checkDocument(file, options)

Prodiving a file parameter does not make any sense for this library. I build this with the idea that it is easily extendable with a plugin system for comparison methods. You can build your own screenshot method and pass a filename into the options to build the file path. Have a look into LocalCompare.js as a base to build something that satisfies your expectations.

There is no need to save screenshots before checking them.

Oh, I got it, thanks!


Add filter-event to ArticlesDbAdapter

Adding event to configure select-statements of attribute-values

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/PT-8331.
Please use this issue to track the state of your pull request.

thanks for your contribution @KMUdoKlest :+1: :tada:


getSSRProps return value does not pass down innerHTML as dom props

Environment

Operating System: Darwin
Node Version:     v16.14.2
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      nitro, css, components, vite
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-fvfobb?file=app.vue,plugins%2Finnerhtml.ts
Describe the bug
I'm currently working rewriting some parts of our codebase from Nuxt 2 to Nuxt 3. Previously we made use of directives which had a specific part to allow for SSR rendering by passing our own bit of code to the Nuxt 2 config:
 bundleRenderer: {       directives: {         customDirective: (vnode, directiveMeta) => {             vnode.data = {                 ...vnode.data,                 domProps: {                 // transforms value before putting it in innerHTML                     innerHTML: transform(directiveMeta.value),                 },              };           },       },     },
This bit of config allowed us to render sanitized content in an SSR manner before. Now in Nuxt 3 this no longer works since we should pass our directives via a plugin. I tried in the stackblitz example to write some content to innerHTML via getSSRProps, but this doesn't provide the same value as domProps (nuxt 2) anymore. I'm not sure if this is a bug or intended behaviour, or perhaps there is a different way to modify innerHTML in getSSRProps?
Additional context
No response
Logs
No response

I believe this difference is attributable to the upgrade from Vue 2 to Vue 3.
Reproduction without Nuxt: https://stackblitz.com/edit/github-c1z4a8.

Ah I was under the impression that getSSRProps was a Nuxt specific thing, my bad


Add Matcher type and To.Pass to accept it

There is now a very simple Matcher type.  The To type has a corresponding Pass method which
takes a Matcher.
Resolves #14

Looks great!
Thank you for your contribution @nelsam


Switch to new microservice template

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 14 (0.0%)  changed or added relevant lines in 11 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-91.0%) to 0.0%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/auth_service/auth_adapter/api/basic.py
0
1
0.0%

src/auth_service/auth_adapter/api/headers.py
0
1
0.0%

src/auth_service/auth_adapter/api/main.py
0
1
0.0%

src/auth_service/user_management/claims_repository/core/claims.py
0
1
0.0%

src/auth_service/user_management/claims_repository/core/seed.py
0
1
0.0%

src/auth_service/user_management/claims_repository/core/utils.py
0
1
0.0%

src/auth_service/user_management/claims_repository/models/dto.py
0
1
0.0%

src/auth_service/user_management/claims_repository/router.py
0
1
0.0%

src/auth_service/user_management/user_registry/utils.py
0
1
0.0%

src/auth_service/init.py
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-91.0%

Covered Lines:
0

Relevant Lines:
930

💛  - Coveralls


Scope not clear on question

Customers are under impression that Guest users can't be added into Security groups:

There for when a privilege user adds a guest, they misinterpret that behavior like an issue.
In this other Article clearly state that guest users could be add to group by Groups owner and user with privileged role over group management
https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/users-default-permissions#compare-member-and-guest-default-permissions

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

ID: 04380f76-b771-d79c-c58a-0704cccfebc6
Version Independent ID: 9075450a-ca6b-a68a-550a-61b9aefb1d65
Content: Secure external access with groups in Azure Active Directory and Microsoft 365 - Microsoft Entra
Content Source: articles/active-directory/fundamentals/4-secure-access-groups.md
Service: active-directory
Sub-service: fundamentals
GitHub Login: @janicericketts
Microsoft Alias: jricketts

@Wibusts
Thanks for your feedback! We will investigate and update as appropriate.

@Wibusts
Thanks for pointing this out. I tried to repro the issue and I am able to add guest users in a security Group.

@Wibusts
I have performed the required changes, once approved by the Author it will reflect in the document itself. I am closing this thread. Please feel free to reach out for further assistance.
for reference: https://github.com/MicrosoftDocs/azure-docs/issues/98910


fixed exception in mitmproxy -c fix #535

Not much to add: path was already a list

Coverage remained the same at 92.61% when pulling e6a8863c51f2e2f5809ae0a42fc874afc3c7f908 on tekii:master into b0f60cf1f293a19c7f87782a3ad762b77cb2a5a7 on mitmproxy:master.

Coverage remained the same at 92.61% when pulling c5f153f8d0e50e12b9c9cd6ab0988a1294bcd4be on tekii:master into b0f60cf1f293a19c7f87782a3ad762b77cb2a5a7 on mitmproxy:master.

Coverage increased (+0.03%) to 92.64% when pulling fb17eea5e0adcbe8d0dc5c2f029b10b172d5a3e7 on tekii:master into b0f60cf1f293a19c7f87782a3ad762b77cb2a5a7 on mitmproxy:master.

Good work. Thanks!


False positives

Hi,
I tried to analyze https://github.com/firehol/netdata with infer.
I get 2 false positives:
src/url.c:50: error: MEMORY_LEAK
   memory dynamically allocated to buf by call to mallocz() at line 49, column 17 is not reachable after line 50, column 5
  48.
  49.       char *buf = mallocz(size);
  50. >     return url_decode_r(buf, str, size);
  51.   }
  52.
  53.

src/web_client.c:1920: error: NULL_DEREFERENCE
  pointer 0 could be null and is dereferenced by call to gettimeofday() at line 1920, column 5
  1918.
  1919.       // start timing us
  1920. >     gettimeofday(&w->tv_in, NULL);
  1921.
  1922.       if(unlikely(!hash_api)) {
  1923.

Summary of the reports

       MEMORY_LEAK: 1
  NULL_DEREFERENCE: 1

The first is false positive, since url_decode_r() returns the supplied buf: https://github.com/firehol/netdata/blob/2fffb74cab6bfe7d6b8e212afcfaf8f74113a07f/src/url.c#L76
The second is false positive, since tv_in is a static member of w: https://github.com/firehol/netdata/blob/2fffb74cab6bfe7d6b8e212afcfaf8f74113a07f/src/web_client.h#L72 and w is passed properly to this function.

Both of these warnings have disappeared with infer 0.15.0 and netdata version 2fffb74cab6bfe7d6b8e212afcfaf8f74113a07f.


The DDL generator need not add grants to ADMIN for a Cloud database.

Solved in db/app/ddl/src/full/R__14.ORACLE_TOOLS.PACKAGE_BODY.SCHEMA_OBJECTS_API.sql


Setting executable bits on three files in sandbox Fix/798

“fixes issue #798 ”

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

[ ] Is it mergeable?
[ ] Did it pass the tests?
[ ] If it introduces new functionality in scripts/ is it tested?
Check for code coverage with make clean diff-cover
[ ] Is it well formatted? Look at make pep8, make diff_pylint_report,
make cppcheck, and make doc output. Use make format and manual
fixing as needed.
[ ] Did it change the command-line interface? Only additions are allowed
without a major version increment. Changing file formats also requires a
major version number increment.
[ ] Is it documented in the ChangeLog?
http://en.wikipedia.org/wiki/Changelog#Format
[ ] Was a spellchecker run on the source code and documentation after
changes were made?

Looks good; merging.  Thank you!


operator kove-operator (v2.1.0)

New operator bundle
Name: kove-operator
Version: v2.1.0
Certification project: 615d2d4d2d5a5137e913e4ff
Test result URL: https://catalog.redhat.com/api/containers/v1/projects/certification/test-results/id/
Test logs URL: https://catalog.redhat.com/api/containers/v1/projects/certification/artifacts/id/662fe8486d8db6071233c36c

/pipeline restart operator-hosted-pipeline

I found the new bundle index was not created https://quay.io/repository/operator-pipeline-prod/kove-operator-index?tab=tags, so re-trigger it to see

I found the new bundle index was not created https://quay.io/repository/operator-pipeline-prod/kove-operator-index?tab=tags, so re-trigger it to see

@jinhli Images are no longer stored there, they are in a single namespace now, if you can see the pipeline created the below image and it's avilable.
quay.io/operator-pipeline-prod/catalog:v4.15-2a50da38d3cfcc794eab7709038fd92dce0a567c
This operator is failing  DeployableByOLM did anyone verify that it actually works?

@acornett21
This was our description from the Partner Acceleration Desk support case we opened (03805511)

The Preflight check DeployableByOLM is consistently passing when running the certification test suite locally and failing in the Red Hat Hosted Pipeline. The DeployableByOLM check has passed in the Red Hat Hosted Pipeline when certifying previous operator versions.
The DeployableByOLM check does not provide enough debug output to determine why it is failing. There are no significant changes in this operator version that could plausibly cause this check to fail only in the Red Hat Hosted Pipeline.
Our best guess is that the Red Hat Hosted Pipeline might be failing to pull the operator image when the DeployableByOLM check creates the subscription. The operator image is in a private repository on quay.io, and the pull secret for this private repository has been added to the OpenShift Object YAML in the Operator Bundle configuration in the Certification Portal.

@kove-development I think I see the issue, the Hosted pipeline is running because you are running the CI pipeline, but with an older version of preflight, so there are no successful results in our system for you CI run.
[upload-artifacts : upload-test-results] 2024-04-29 18:34:55,450 [operator-cert] ERROR Pyxis POST query failed with https://catalog.redhat.com/api/containers/v1/projects/certification/id/615d2d4d2d5a5137e913e4ff/test-results - 400 - {"detail": "Validation error: 'github.com/redhat-openshift-ecosystem/openshift-preflight' version '1.8.0' is not supported. Supported versions are: ['1.9.1', '1.9.2']", "status": 400, "title": "Bad Request", "type": "about:blank", "trace_id": "0x657dcb11453e2179be758e634a2523f1"}

Can you update the  CI pipeline tasks in your cluster with the latest release? I'm going to close this PR, so a new CI run will re-create a new PR.


Question: Pre-selected track-by

How can I bind a variable to key? The currencyList object is being delivered by the Rest Api but I need to bind just the key so that I can pre-select and send back to Rest for an update.
currencyList: [
            {key: 1, value: 'First Country'},
            {key: 2, value: 'Second Country'},
            {key: 3, value: 'Third Country'}
          ]

multiselect
            v-model="vm.selectedCurrencyId"
            track-by="key" label="value" placeholder="Select one"
            :options="currencyList"
          >

Use a computed value passed to :value together with @input handler, instead of v-model.
https://github.com/monterail/vue-multiselect/issues/194 this might be helpful as it is basically the same case.

I tried this, but does not work (using Vue 2.0)

It doesn't work for me too, so I created the most basic component using bootstrap. But, I would like to replace vue-multiselect at some point.

Me too, I can't make it work. @shentao, according to your available time, could you please provide a working example? (e.g. fiddler)
Thank you

Could you provide some more details?
@coderabsolute the vm.selectedCurrencyId object must contain the key and value properties to be properly preselected. Updating the currencyList should work out of the box.

I have written a tiny component, so I think we can close this issue for now. Thanks!

@coderabsolute if it solves your problem, how about showing it here, so others might find it useful? :)

@shentao for the single select, I got the same issue, until I read your comment here, got it solved.
"the vm.selectedCurrencyId object must contain the key and value properties to be properly preselected"
I think it should pick only the value which is defined by the track-by.


chore(*) prevent lua_pack from leaking to globals

Summary
lua_pack is especially bad as it monkey patches the string in Lua. This means that whenever you require the lua_pack the string is modified. We don't want this to happen, thus we have this special construct there. We should replace lua_pack or modify lua_pack at some point.

A good example of this leakage is that with this PR the grpc-web doesn't anymore pass as it was depending on the leakage.

Sister PRs that need to be merged prior this:
https://github.com/Kong/kong-plugin-grpc-gateway/pull/14
https://github.com/Kong/kong-plugin-grpc-web/pull/15

Closing this as we agreed to fix this better.


Is there any way to store the chosen random term in the workflow

This node works like a charm when it comes to explore random variations of a prompt. What I am deeply missing is the chance to see which term of a random list was picked when reloading a workflow. The "show text"-node by phytongosssss does display the prompt the way it was used e.g. "A blue duck in a lake", based on the original  "A {blue|red} duck in a lake". Sadly this information is stored, but not accessible (readable)  in the workflow, making it necessary to rerun the workflow to get this info. While it is easy to distinguishing red and blue ducks, it becomes tricky if the random terms are synonyms like {retro|vintage}. TIA :)

Thanks for the feed back. I have made a quick update to store the resulting text into the "extra" section of the workflow. This however does not show up in the UI, you will need to use another tool to read the data. Ex: https://pngchunk.com/

I will need some time to figure out how to read that data back and display it in the UI, but for now the data will be saved for future use.

Brilliant. Thanks a million for the quick fix. Would be perfect to have an additional info field for the extra, (like the seed that was in action)so not to hop back and forth between the chunk reader and comfy. Btw, till about two month ago this storing of the random term worked in Comfy (even so it removed all the bracket-lists in a prompt). So maybe there´s some abandoned line of code in ComfyUI itself, that might be of help. But this comes from a complete noob in terms of code. Thanks again :)

New feature for you:
Hovering over the text area will display the processed prompt. If the prompt was saved in the file, it will be read back as is. If it was not, it will be re-processed and displayed anyway. I wanted to keep the result saved in the metadata just in case it needs to be recovered without the source code.
The hover text will continue to stay updated as the prompt is changed. The caveat to that is that it will not update when the seed is changed. The result will change, but the hover text wont (until the prompt text area is changed again). I'm still looking for a way to get a callback from the seed input changing.
Still a work in progress, feed back is welcome.

Figured it all out :) Everything should stay updated as you are editing prompts and seeds.

Wow, just when I found out that stepping back in history fixes the cached hover-text, you fixed it already. I run everything again, and it works like a charm. Random may sound like an arbitrary thing, but for folks like me you've restored an essential part of playing with pure chance :) You are a hero :)


[S5E7 spoilers] Tree Hugger

We'll obviously need to add Tree Hugger as a pony once an SVG becomes available. Note, however, that she cannot be added in alphabetical order because this will change the IDs of all the existing ponies and change people's save files.
Also I think it should start raining hippie flowers in the background if Tree Hugger is in the displayed ponies.

As for the alphabetical ordering, the following could be done:
  var PonyObj = {
    1:   "Adagio Dazzle",
    2:   "Aloe",
    3:   "Amethyst Star",
    4:   "Applebloom",
    5:   "Applejack",
    // ...
    58:  "Vinyl Scratch",
    57:  "Zecora",
  };
  PonyObj.length = Object.keys(PonyObj).length;
  var PonyList = Array.prototype.slice.call(PonyObj);

Having an object like this would allow for having the ponies in the code alphabetically while maintaining save file compatibility.

The issue here is that you'd have to eventually figure out what the maximum ID value is in a giant list of (essentially randomized) numbers in order to assign a new one. It'd be easier to just give up the ordering.

Correct me if I'm wrong, but wouldn't the maximum ID of that list of numbers be equal to the length of the list? So for any list of length n, the ID of an element inserted into any arbitrary location within that list be n + 1?

Your second sentence is not true at all. If you have a list like this:
var list = [0,1,2,3,4,5,6];

Then adding 7 to an arbitrary location, e.g. after the first element, like this:
var list = [0,7,1,2,3,4,5,6];

Then the number 7 will be on the 7th index, the 5 on the 6th etc.
Also the maximum ID in an n-length list is n-1

The maximum ID would actually be n if you started from 1. You would have to figure this out programmatically, though.

I wrote my questions with the assumption that you are suggesting that "ID" be a reference key for a dictionary rather than the element's corresponding index within a list, and that, based on the list example you gave, the ID numbers start at 1 rather than 0. If the ID system currently implemented is based on element location within a list rather than keys in a dictionary, then blackhole is correct in saying there is no way to maintain alphabetical order without breaking existing save data (without some sort of overhaul, anyway).
Also, would there be any benefit to maintaining alphabetical order other than just having it look nice in the source code?

Not really.

I see two ways, then, of keeping the list alphabetized without breaking save data.
First, as discussed, is to turn the list into a dictionary, and all current ponies be given an ID key corresponding to their current index. That way, new ponies can be added in alphabetically by assigning them the ID equal to the max ID + 1, which would be either the length of the dictionary or the length + 1, depending on if the first ID is 0 or 1, respectively.
Second, there could be a system to "update" save data so that pony IDs from previous versions get updated to the correct index. (For example, if a pony gets inserted into the list at index 22, then all pony IDs in the save data from previous versions that are 22 or higher get incremented by one as part of the update process.) This would be a more tedious method to maintain, though, since it would need to be aware of, and possibly customized for, each version prior to the current, as well as potentially intelligently update save data across multiple versions.
Though yeah, if the only benefit to this is keeping the source looking pretty, then it's probably a decision that needs to be made whether or not this amount of effort would be worth it.

There is no way the second method is going to be implemented.
For right now, this will stay as an array and simply not be alphabetized. In the future, it may be turned into a dictionary and IDs will be assigned, in which case a shuffle would have to operate on indirect indices in order to be efficient.

Since there's already a save version number, save-breaking changes to the
ponylist could increase the version number.


Create 'make:seed' command to speed up the workflow

This command creats a file on 'database/seeds' with the name
'{{name}}TableSeeder'. After file creation composer dump-autoload
command is executed.

I forgot to add the new files: /


[FIX] Chat Issues in Multiple Tabs

Closes https://github.com/WideChat/Rocket.Chat/issues/1149
@ear-dev This also fixes old chat remains in the chat in the multiple tabs case. We need to test all the scenarios after this, timeout as well

Thanks @Shailesh351 I'll load this up today and give it a try.

@bhardwajaditya can you do a quick review on this PR please if you have a minute?  Thanks.

@ear-dev sure doing it

So far I see one small issue:

Open chat in two tabs
Close chat with 'X' in tab2, then minimize the widget in the same tab.  At this point it looks good, both tabs appear in sync.
Click the widget in tab1 and the transcript is visible, but we expect the 'New Chat' screen.  If you click the widget in tab2 then you do get the 'New Chat' screen as expected, and now both tabs are in sync again.

Is this something easy to fix?  Thanks.....

@ear-dev It will need sometime debugging. We can fix it separately. Looks like all the major issues are now gone.

Thanks @bhardwajaditya
@Shailesh351 ready to merge this then?

Yup @ear-dev All good!


print(card.def) does not work

The title says it all, i dont know why it does not work, cause anything else works perfect.
Help please.
ps: thank you for this awesome tool :D

Sorry for the late reply, but I made a workaround in the latest push by using Card.def_ instead of Card.def, hopefully solves the issue


Update data-box-portal-customer-managed-shipping.md

Adding India and South Africa to the list supported regions

@ansubram : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @ansubram - This PR was opened in the public repository. PMs should work in the private repo. We’ll leave this PR for review in the public repo, but would you make future article updates in the private repo? Thanks!

#sign-off Looks good.

@alkohli: I'm sorry - only the author of this article, @priestlg, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off Looks good.

@alkohli: I'm sorry - only the author of this article, @priestlg, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Shutdown feature branch site on Gatsby Cloud & remove feature branch

https://observabilitypacks.gatsbyjs.io/instant-observability/

feature branch site should be taken down
remove feature branch from the repo

Done


fix Fix compile error in meta tool

Proposed changes
Fix compile error in meta tool
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Bump requirements and restrict grpcio and grpcio-status

TL;DR
We have to restrict grpcio in setup.py otherwise we won't be able to bump requirements in plugins
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
Two main changes:

regenerate requirements
move restriction to grpcio and grpcio-status to setup.py so that we can regenerate requirements in plugins (otherwise plugins try to pull in latest grpcio, which has a restriction on protobuf>=4.21.6 (and it's incompatible with flyteidl)

Tracking Issue
https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/

this goes away with buf right?

Correct. Once we move to buf we'll be able to remove https://github.com/flyteorg/flyteidl/blob/master/setup.py#L18 (or at least relax it to the accommodate the next major version of protobuf).


Nondimensionalizing a nondimensional variable leads to locking

I sometimes forget attaching a unit to a variable and if I then try to nondimensionalize the variable, the code locks instead of throwing an error. Can we introduce an error message for this common user mistake where the input to nondimensionalize has no unit?
Example:
using GeoParams
CD = GEO_units(length=10km, temperature=600C, stress=1000MPa, viscosity=1e20Pas)
m = 5 # forgot to add kilogram here
nondimensionalize(m, CD) # the code will hang here for eternity

For some reason, throwing when the number is unitless breaks some internal stuff. Would it be ok for you to instead of throwing, to return the unitless number instead? Could add a warning in this case.

For some reason, throwing when the number is unitless breaks some internal stuff. Would it be ok for you to instead of throwing, to return the unitless number instead? Could add a warning in this case.

Ah that's a bummer. I think in this case, it is better for it to lock than continue with a wrong value because warnings can easily be overlooked in the output. At least in my case, this always happens because I forgot to add the unit and not because I used it on an already dimensionless parameter. So I want it to not run.
So, if error message won't work, can we add the warning and keep the locking behavior? Then, you would always see the warning at the bottom of the output and know why it is stuck.

I guess a warning + hanging is not too far from crashing if you are running the job interactively. But if for example you are submitting a job in a cluster, you may not notice immediately that the job is actually hanging. So throwing/crashing sounds like the safest option.
@boriskaus any ideas? If I add the throwing error, the Perplex tests don't pass anymore.

Not sure if you had time for this yet, but another trap is if you accidentally pass an empty vector to nondimensionalize(). This will also hang instead of crashing

Sorry forgot about this issue... I'm taking a look again to find a workaround

By empty vector, do you mean something like Float64[] or the more generic []?


Feature request: hide tags and page.summary

Hi, first of all thanks for creating this theme, it looks great. Here are a few features I would like to see in this theme.

[ ] Option to justify blog text. Iiuc this needs something like this https://github.com/rhazdon/hugo-theme-hello-friend-ng/issues/20#issuecomment-488144749. EDIT: I don't need it anymore. I realized that I can @import "../theme/serene/sass/main.scss" so after updating serene I won't need to copy new css anymore.
[ ] Option to hide tags even if they are present. I like to tag but not show. I can just comment them out in the markup, but if I have 20 posts and suddenly realize I want to show the tags, it's going to take a long time.
[ ] Option to not include page.summary in a blog post. This will be useful if you want to add a summary for rss and don't want to remove this text from the beginning of a post. In the future page.summary can be used under post name on the blog page.

EDIT: I've done it locally, waiting to hear from you if you want it in serene.

For 'justify', I agree to this post: https://ruitina.com/dont-justify-text-on-websites-and-apps/ and will not add an option for that.

Add a display_tags would be nice, PR welcomed.

I'm not following the idea of removing page.summary, could you explain it a bit more.

For 'justify', I agree to this post: https://ruitina.com/dont-justify-text-on-websites-and-apps/ and prefer not to add an option for that.

text-align: justify + hyphens: auto; looks not bad. I saw it on https://matklad.github.io/. Anyway, yea, it can be easily changed on client side.

I'm not following the idea of removing page.summary, could you explain it a bit more.

I want to write descriptions for articles, but description will not be just the beginning of the article, but a short description of the entire article (summary). Therefore, it is not appropriate to show it at the beginning. At the same time, the description is useful for the rss feed and later it would be nice to show summary under post title on the blog page. For example look at the card generetaed by openring

and the article itself. As you can see, description is not included in the blog post. Hope you understand what I mean.

Now I get it, this involves updating docs, I'm working on it.
For display_tags, seems trivial, open a pr if you want.


collector: discuss alternative protocols for receiving measurements

We should discuss this with @bassosimone @ainghazal and whoever else is interested

It would be cool if Outline clients could report success/failure of server connections to OONI. That way we could better understand what protocols and strategies are working where.

After @fortuna suggested it, I've been looking at NEL and the reporting api draft. I have a draft for a OONI experiment spec that defines quasi-compatible format - a collector compatible with a NEL policy would then be ~easy to implement. I will open a PR in the coming days.
alas, the nel-collector package has been marked as archived - we're still not clear about the reasons (vinicius suggested it might not support the latest versions of the spec).
other points to consider are whether the semantics of the errors understood by OONI are totally compatible with the known errors for the reporting API - they should be, but perhaps there are corner cases to review.
the only part that feels like a stretch is how to specify errors related to the initialization of the tunnel (we need to account for handshake and handshake-less protocols), and checking of initial tunnel "health" (i.e., is it enough to have proof that the tunnel gateway routes to the internet, or do we want to impose any sort of more strict criteria?)